<!-- $Id: p2ts.odd,v 1.11 1998/02/01 17:38:08 tei Exp $ -->
<!--*
    * $Log: p2ts.odd,v $
    * Revision 1.11  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.10  94/04/01  16:39:21  msmcq
    * Changes during validation of DTD
    *
    * Revision 1.9  1994/03/28  18:16:08  msmcq
    * add TYPE attribute to IDENT
    *
    * Revision 1.8  1994/03/27  21:46:39  msmcq
    * Correction of typos reported by DB, EB.
    *
    * Revision 1.7  1994/03/21  14:12:00  lou
    * second mass typo clearup
    *
    * Revision 1.5  1994/02/17  20:29:04  msmcq
    * revision for SC review
    * -->
<!-- Revisions:                                               -->
<!-- 94-03-31 : MSM : protect teistr invocation               -->
<!-- 94-03-31 : MSM : define tsmix                            -->
<!-- 94-03-29 : MSM : clarify class usage (or try to)         -->
<!-- 94-03-29 : MSM : suppress reference to 'spoken' class, use compspok -->
<!-- 94-03-27 : MSM : correct error tagging IDENT             -->
<!-- 94-03-26 : MSM : typos, changes from EBr, DB             -->
<!-- 94-02-14 : MSM : minor cleanup                           -->
<!-- 94-02-14 : MSM : Added RCS id                            -->

<!-- Opening sections really need a complete rewrite to       -->
<!-- conform to P2 housestyle, but I can't face it just now   -->
<!-- (lb)                                                     -->
<!-- 16 sep 93: LB: gritted teeth; hacked out a lot -->
<!-- 27-8 Aug: LB : added examples -->
<!-- 9 aug: LB: fixed AH and other cross refs;
                replaced discussion of decls with xref to CCas  -->
<!-- 27 jul 93: LB added credit at start -->
<!-- 93-07-21 : DTL : minor corrections                       -->
<!-- 93-07-15 : DTL : references to TSsa changed to SA, etc   -->
<!--  9  Feb 93 : WP  : Changed P222 refs to P2HD refs        -->
<!--  9  Feb 93 : WP  : Changed 34 to 10                      -->
<!--  4  Feb 93 : WP  : Changed P234 to P2TS                  -->
<!-- 22f Apr 92 : MSM : final changes for release             -->
<!-- 18 Apr 92 : LB : various minor changes:                  -->
<!--          further fiddling with wording of first section  -->
<!--          mentioned nestable div                          -->
<!--          clarified rule on start/end/dur attribs         -->
<!--          added eg. for trans attrib                      -->
<!-- 17 Apr 92 : CMSMcQ : changes for release to LB           -->
<!-- 17 Apr 92 : WP     : spellcheck and make changes         -->
<!-- 16 Apr 92 : CMSMcQ : clean up for release.  rename stext -->
<!--  3 Apr 92 : CMSMcQ : add n value on div1                 -->
<!--  2 Apr 92 : CMSMcQ : reformat multi-line comments        -->
<!--  2 Apr 92 : CMSMcQ : suppress blank lines (format better)-->
<!--  2 Apr 92 : CMSMcQ : add /eg at line 415 or so           -->
<!-- *******************************************************  -->
<!--           TEI P2 : CHAPTER 10 : SPOKEN TEXTS             -->
<!-- *******************************************************  -->
<div1 id="TS" n="11"><head>Transcriptions of Speech</head>

<p>The base tag set for transcriptions of spoken language described in
this chapter is intended for use with a wide variety of transcribed
spoken material.  It should be stressed, however, that the present
proposals are not intended to support unmodified every variety of
research undertaken upon spoken material now or in the future; some
discourse analysts, some phonologists, and doubtless others may wish
to extend the scheme presented here to express more precisely the set
of distinctions they wish to draw in their transcriptions.  Speech
regarded as a purely acoustic phenomenon may well require different
methods from those outlined here, as may speech regarded solely as a
process of social interaction.

<!-- <note>This chapter was prepared by TEI work group AI 2 -->
<!-- (spoken texts), chaired by Stig Johansson, of the University -->
<!-- of Oslo.  The membership of the work group is given in the -->
<!-- front matter.  Major contributions to the ideas here -->
<!-- presented came from A. Rosta (University College, London) -->
<!-- and J. Edwards (University of California). The scheme is -->
<!-- based on a survey of about twenty widely used and documented -->
<!-- systems for the transcription of spoken materials taken from -->
<!-- such diverse fields as journalism, large reference corpora, -->
<!-- language-acquisition studies, and dialect studies.</note> --></p>

<p>This chapter begins with a discussion of some of the problems
commonly encountered in transcribing spoken language (section <ptr
target="TSov">).  Section <ptr target="TSba"> describes the basic
structural elements of this tag set.  Finally, section <ptr
target="TSsa"> of this chapter reviews further problems specific to the
encoding of spoken language, demonstrating how mechanisms and elements
discussed elsewhere in these Guidelines may be applied to them.</p>

<p>The overall structure of a TEI spoken text is identical to that of
any other TEI text:  the <gi>TEI.2</gi> element for a spoken text
contains a <gi>teiHeader</gi> element, followed by a <gi>text</gi>
element.  Even texts primarily composed of transcribed speech may also
include conventional front and back matter, and may even be organized
into divisions like printed texts. For simplicity's sake, therefore, the
base tag set for spoken text uses the default text structure, as defined
in chapter <ptr target="DS">; this tag set is embedded automatically by
the spoken base tag set.</p>

<p>To enable the base tag set for spoken texts, a parameter entity
<ident type="pe">TEI.spoken</ident> must be declared within the document
type declaration subset, the value of which is <code>INCLUDE</code>, as
further described in section <ptr target="STin">.  A document using this
base tag set 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.spoken 'INCLUDE' >
 ]>
]]>
</eg>

This declaration makes available all of the elements and attributes
discussed in the present chapter, in addition to the core elements
described in chapter <ptr target="CO">.  If other elements are needed (in
particular, those needed for synchronization or segmentation),
additional tag sets may also be enabled in a similar way.</p>

<p>Two additional classes are defined by this tag set.  Elements which
appear only within transcribed speech constitute the <ident
type="class">comp.spoken</ident> element class.  Elements with a
specificable temporal duration constitute the <ident type="class">timed</ident> element class.  These classes are defined in
the file <ident type="file">teispok2.ent</ident> using the following
parameter entities:

<eg id=dtscla>
<![ CDATA [
<!-- 11:  Class declarations for Transcribed Speech           -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->
<!ENTITY % x.comp.spoken ''                                     >
<!ENTITY % m.comp.spoken '%x.comp.spoken event | kinesic | 
           pause | shift | u | vocal | writing'                 >
<!ENTITY % a.timed '
          dur                CDATA               #IMPLIED
          end                IDREF               #IMPLIED
          start              IDREF               #IMPLIED'      >
<!ENTITY % mix.spoken '| %m.comp.spoken'                        >
]]>
</eg>


The elements of the base tag set for transcribed speech are declared in
the file <ident type="file">teispok2.dtd</ident>, which is organized as
follows:

<eg id=dts>
<![ CDATA [
<!-- 11:  Base tag set for Transcribed Speech                 -->
<!-- Text Encoding Initiative: Guidelines for Electronic      -->
<!-- Text Encoding and Interchange. Document TEI P3, 1994.    -->

<!-- Copyright (c) 1994 ACH, ACL, ALLC. Permission to copy    -->
<!-- in any form is granted, provided this notice is          -->
<!-- included in all copies.                                  -->

<!-- These materials may not be altered; modifications to     -->
<!-- these DTDs should be performed as specified in the       -->
<!-- Guidelines in chapter "Modifying the TEI DTD."           -->

<!-- These materials subject to revision. Current versions    -->
<!-- are available from the Text Encoding Initiative.         -->

<!-- ... declarations from section 11.2.7                     -->
<!--     (Components of Transcribed Speech)                   -->
<!--     go here ...                                          -->

<!-- The base tag set for transcriptions of speech 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>


<!-- $Id: p2tsov.odd,v 1.8 1998/02/05 17:14:35 tei Exp $ -->
<!--*
    * $Log: p2tsov.odd,v $
    * Revision 1.8  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.6  1994/03/27  21:46:39  msmcq
    * Correction of typos reported by DB, EB.
    *
    * Revision 1.5  1994/02/17  20:29:04  msmcq
    * revision for SC review
    * -->
<!-- Revisions:                                               -->
<!-- 18 jan 98 : LB : fix div example-->
<!-- 94-03-26 : MSM : typos, changes from EBr, DB             -->
<!-- 94-02-14 : MSM : minor cleanup                           -->
<!-- 94-02-14 : MSM : Added RCS id                            -->
<!-- 93-12    : LB : delete introductory comments -->
<div2 id=TSov type='subsection'>
<head>General Considerations and Overview</head>

<p>There is great variation in the ways different researchers have
chosen to represent speech using the written medium.<note>For a
discussion of several of these see <bibl>J.  A. Edwards and M. D.
Lampert, eds., <title>Talking Language:  Transcription and Coding of
Spoken Discourse</title> (Hillsdale, N.J.:  Lawrence Erlbaum Associates,
1993)</bibl>; <bibl>Stig Johansson, <title>Encoding a Corpus
in Machine-Readable Form,</title> in <title>Computational Approaches
to the Lexicon:  An Overview,</title> ed.  B. T. S. Atkins et al.
(Oxford:  Oxford University Press, forthcoming)</bibl>; and
<bibl>Stig Johansson et al.  <title>Working Paper on Spoken
Texts,</title> document TEI AI2 W1, 1991</bibl>.</note> This
reflects the special difficulties which apply to the encoding or <term
rend=noindex>transcription</term> of speech.  Speech varies according to
a large number of dimensions, many of which have no counterpart in
writing (for example, tempo, loudness, pitch, etc.).  The audibility of
speech recorded in natural communication situations is often less than
perfect, affecting the accuracy of the transcription.  Spoken material
may be transcribed in the course of linguistic, acoustic,
anthropological, psychological, ethnographic, journalistic, or many
other types of research.  Even in the same field, the interests and
theoretical perspectives of different transcribers may lead them to
prefer different levels of detail in the transcript and different styles
of visual display.  The production and comprehension of speech are
intimately bound up with the situation in which speech occurs, far more
so than is the case for written texts.  A speech transcript must
therefore include some contextual features; determining which are
relevant is not always simple.  Moreover, the ethical problems in
recording and making public what was produced in a private setting and
intended for a limited audience are more frequently encountered in
dealing with spoken texts than with written ones.

<p>Speech also poses difficult structural problems.  Unlike a written
text, a speech event takes place in time.  Its beginning and end may be
hard to determine and its internal composition difficult to define.
Most researchers agree that the utterances or <term>turns</term> of
individual speakers form an important structural component in most kinds
of speech, but these are rarely as well-behaved (in the structural
sense) as paragraphs or other analogous units in written texts:
speakers frequently interrupt each other, use gestures as well as words,
leave remarks unfinished and so on.  Speech itself, though it may be
represented as words, frequently contains items such as vocalized pauses
which, although only semi-lexical, have immense importance in the
analysis of spoken text.  Even non-vocal elements such as gestures may
be regarded as forming a component of spoken text for some analytic
purposes.
<!-- LB added following sentence -->
Below the level of the individual utterance, speech may be segmented
into units defined by phonological, prosodic, or syntactic phenomena;
no clear agreement exists, however, even as to appropriate names for
such segments.

<p>Spoken texts transcribed according to the guidelines presented here
are organized as follows.  As noted above, speech is regarded as being
composed of arbitrary high-level units called
<term rend=noindex>texts</term>.
<index level1='texts' level2='as organizing unit for spoken material'>
A spoken <gi>text</gi> might typically be a conversation between a small
number of people, a lecture, a broadcast TV item, or a similar event.
Each such unit has associated with it a <gi>teiHeader</gi> providing
detailed contextual information such as the source of the transcript,
the identity of the participants, whether the speech is scripted or
spontaneous, the physical and social setting in which the discourse
takes place and a range of other aspects.  For details of the header in
general, refer to chapter <ptr target=HD>; for details of additional
elements for the documentation of participant and contextual
information, see section <ptr target=CCah>.

<p>Defining the bounds of a spoken text is frequently a matter of
arbitrary convention or convenience.  In public or semi-public contexts,
a text may be regarded as synonymous with, for example, a <term
rend=noindex>lecture</term>, a <term rend=noindex>broadcast item</term>,
a <term rend=noindex>meeting</term>, etc.  In informal or private
contexts, a text may be simply a conversation involving a specific group
of participants.  Alternatively, researchers may elect to define spoken
texts solely in terms of their duration in time or length in words.  By
default, these Guidelines assume of a text only that:

<list>
<item>it is internally cohesive,
<item>it is describable by a single header, and
<item>it represents a single stretch of time with no significant
discontinuities.
</list>

Deviation from these assumptions may be specified (for example, the
<att>org</att> attribute on the <gi>text</gi> element may take the value
<code type=value>compos</code> to specify that the components of the
text are discrete) but is not recommended.

<p>Within a <gi>text</gi> it may be necessary to identify subdivisions
of various kinds, if only for convenience of handling.  The neutral
<gi>div</gi> element discussed in section <ptr target=DSdiv> is
recommended for this purpose.  It may be found useful also for
representing subdivisions relating to discourse structure, speech act
theory, transactional analysis, etc., provided that these divisions are
hierarchically well-behaved.
<!-- Reference changed to SA and SAsy (DTL) -->
<!-- LB moved out of note and into text -->
<!-- note -->
Where they are not,
as is often the case, the mechanisms discussed in chapters
<ptr target=SA> and
<ptr target=NH> may be used. <!-- /note-->


<p>A spoken text may contain any of the following components:
<list>
<item>utterances
<item>pauses
<item>vocalized but non-lexical phenomena such as coughs
<item>kinesic (non-verbal, non-lexical) phenomena such as gestures
<item>entirely non-linguistic events occurring during and possibly
influencing the course of speech
<item>writing, regarded as a special class of event in that it can
be transcribed, for example captions or overheads displayed during
a lecture
<item>shifts or changes in vocal quality
</list>

<p>Elements to represent all of these features of spoken language are
discussed in section <ptr target=TSba> below.

<p>An utterance (tagged <gi>u</gi>) may contain lexical items
interspersed with pauses and non-lexical vocal sounds; during an
utterance, non-linguistic events may occur and written materials may be
presented.  The <gi>u</gi> element can thus contain any of the other
elements listed, interspersed with a transcription of the lexical items
of the utterance; the other elements may all appear between utterances
or next to each other, but except for <gi>writing</gi> they do not
contain any other elements nor any data.

<!-- paras removed here: too repetitious -->

<div3 id=TSosdc><head>Divisions</head>

<p>A spoken text itself may be without substructure, that is, it may
consist simply of units such as utterances or pauses, not grouped
together in any way, or it may be subdivided into one or more divisions
as described in this section.

<p>If the notion of what constitutes a <soCalled>text</soCalled> in
spoken discourse is inevitably rather an arbitrary one, the notion of
formal subdivisions within such a <soCalled>text</soCalled> is even more
debatable.  Nevertheless, such divisions may be useful for such types of
discourse as debates, broadcasts, etc., where structural subdivisions
can easily be identified, or more generally wherever it is desired to
aggregate utterances or other parts of a transcript into units smaller
than a complete <soCalled>text</soCalled>.  Examples might include
<q>conversations</q> or <q>discourse fragments</q>, or more narrowly,
<q>that part of the conversation where topic x was discussed</q>,
provided only that the set of all such divisions is coextensive with the
text.

<p>Each such division of a spoken text should be represented by the
numbered or un-numbered <gi>div</gi> elements defined in chapter <ptr
target=DS>.  For some detailed kinds of analysis a hierarchy of such
divisions may be found useful; nested <gi>div</gi> elements may be used
for this purpose, as in the example below.

<p>The <gi>div</gi> element is a member of the <ident
type=class>divn</ident> class of structural elements, and therefore has
the following attributes in common with other members of the class:

<list type=gloss>
<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>
<label><att>org</att></label>
<item>specifies how the content of the division is organized.
Legal values are:
<list type=gloss>
<label><term>composite</term></label>
<item>composite content: i.e. no claim is made about the sequence 
in which the immediate contents of this division are to be 
processed, or their inter-relationships.</item>
<label><term>uniform</term></label>
<item>uniform content: i.e. the immediate contents of this 
element are regarded as forming a logical unit, to be 
processed in sequence.</item>
</list></item>
<label><att>sample</att></label>
<item>indicates whether this division is a sample of the original 
source and if so, from which part.
Legal values are:
<list type=gloss>
<label><term>final</term></label>
<item>division lacks material at start.</item>
<label><term>complete</term></label>
<item>division is not a sample.</item>
<label><term>medial</term></label>
<item>division lacks material at start and end.</item>
<label><term>unknown</term></label>
<item>position of sampled material within original unknown.</item>
<label><term>initial</term></label>
<item>division lacks material present at end in source.</item>
</list></item>
<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>
</list>

<p>The <att>type</att> attribute may be used to characterize divisions
in any way that is convenient; no specific recommendations are made in
these Guidelines.  For example, a collection made up of transcribed
<soCalled>sound bites</soCalled> taken from speeches given by a
politician on different occasions, might encode each extract as a
distinct <gi>div</gi>, nested within a single composite <gi>div</gi> as
follows:

<eg rend=skel>
<![ CDATA [
<div type='soundbites' org='composite'>

   <div sample=medial>
   <!-- ... -->
   </div>
   <div sample=medial>
   <!-- ... -->
   </div>
   <div sample=initial>
   <!-- ... -->
   </div>
</div>
]]>
</eg>

<!-- removed dur attribute on div                             -->
<!-- The <att>dur</att> attribute may specify temporal        -->
<!-- duration in any units convenient; for further            -->
<!-- discussion of temporal alignment, see section <ptr      -->
<!-- target=SAsy>.                                            -->

<p>As a member of the class <ident type=class>declaring</ident>, the
<gi>div</gi> element may also carry a <att>decls</att> attribute, for
use where the divisions of a text do not all share the same set of the
contextual declarations specified in the TEI header.  (See further
section <ptr target=CCas>).

<!-- example would be nice here too -->




<!-- $Id: p2tsba.odd,v 1.8 1998/01/28 11:09:58 cmsmcq Exp $ -->
<!-- $Log: p2tsba.odd,v $
# Revision 1.8  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.7  1994/03/28  14:56:39  lou
# fix dud xref
#
# Revision 1.6  1994/03/27  21:46:39  msmcq
# Correction of typos reported by DB, EB.
#
# Revision 1.5  1994/02/17  20:29:04  msmcq
# revision for SC review
# -->
<!-- Revisions:                                               -->
<!-- 18 jan 98: LB : fix egs -->
<!-- 4 Jan 94 : LB : participant/group changed to person/grp -->
<!-- 94-03-26 : MSM : typos, changes from EBr and DB          -->
<!-- 94-02-14 : MSM : more cleanup                            -->
<!-- 94-02-14 : MSM : cosmetic, spelling                      -->
<!-- 94-02-14 : MSM : Added RCS id                            -->

<div2 id=TSba><head>Elements Unique to Spoken Texts</head>

<p>The following elements characterize spoken texts, transcribed
according to these Guidelines:

<list type=gloss>
<label><gi>u</gi></label>
<item>a stretch of speech usually preceded and followed by

silence or by a change of speaker.</item>
<label><gi>pause</gi></label>
<item>a pause either between or within utterances.</item>
<label><gi>vocal</gi></label>
<item>any vocalized but not necessarily lexical phenomenon, for 
example
voiced pauses, non-lexical backchannels, etc.</item>
<label><gi>kinesic</gi></label>
<item>any communicative phenomenon, not necessarily vocalized, 
for
example a gesture, frown, etc.</item>
<label><gi>event</gi></label>
<item>any phenomenon or occurrence, not necessarily vocalized or

communicative, for example incidental noises or other 
events affecting
communication.</item>
<label><gi>writing</gi></label>
<item>a passage of written text revealed to participants in the 
course
of a spoken text.</item>
<label><gi>shift</gi></label>
<item>marks the point at which some paralinguistic feature of a 
series of
utterances by any one speaker changes.</item>
</list>


<p>Each of these is further discussed and specified below in sections
<ptr target=TSbaut> to <ptr target=TSbawr>.

<p>We can show the relationship between four of these constituents of
speech using the features <ident type=feature>eventive</ident>, <ident
type=feature>communicative</ident>, <ident
type=feature>anthropophonic</ident> (for sounds produced by the human
vocal apparatus), and <ident type=feature>lexical</ident>:

<eg rend=fig>
<![ CDATA [
         eventive  communicative  anthropophonic  lexical

event       +             -              -           -
kinesic     +             +              -           -
vocal       +             +              +           -
utterance   +             +              +           +
]]>
</eg>

The differences are not always clear-cut.  Among
<term rend=noindex>events</term> might be included actions like
slamming the door, which can certainly be communicative.
<term rend=noindex>Vocals</term> include coughing and sneezing, which are
<index level1='vocal events' level2='in transcription of speech'>
usually involuntary noises.  Equally, the distinction between utterances
and vocals is not always clear,

<!-- (as implied by our use of the term <q>semi-lexical</q>) -->

although for many analytic purposes it will be convenient to regard them
as distinct.  Individual scholars may differ in the way borderlines are
drawn and should declare their definitions in the <gi>editorialDecl</gi>
element of the header (see <ptr target=HD53>).

<p>The following short extract exemplifies several of these elements. It
is recoded from a text originally transcribed in the CHILDES
format.<note>The original is a conversation between two children and
their parents, recorded in 1987, and discussed in
<bibl><author>Brian MacWhinney,</author>
<title>CHAT Manual</title>
([Pittsburgh]:  Dept of Psychology, Carnegie-Mellon University,
1988), pp. 87ff.

</bibl>
</note>
Each utterance is encoded using a <gi>u</gi> element (see section <ptr
target=TSbaut>).  Pauses marked by the transcriber are indicated using
the <gi>pause</gi> element (see section <ptr target=TSbapa>).
Non-verbal vocal effects such as the child's meowing are indicated
either with orthographic transcriptions or with the <gi>vocal</gi>
element, and entirely non-linguistic but significant events such as the
sound of the toy cat are represented by the <gi>event</gi> elements
(see section <ptr target=TSbavo>).

<eg>
<![ CDATA [
<u who=MAR>you never <pause> take this cat for show&sp;and&sp;tell
  <pause> meow meow</u>
<u who=ROS>yeah well I dont want to</u>
<event desc=
  'toy cat has bell in tail which continues to make a tinkling sound'>
<vocal who=MAR desc='meows'>
<u who=ROS>because it is so old</u>
<u who=MAR>how <reg orig="bout">about</reg> your&stress; cat <pause>
   yours is  new &stress;
  <kinesic desc='shows Father the cat'></u>
<u who=FAT trans=pause>thats <pause> darling</u>
<u who=MAR><s>no mine&stress; isnt old</s>
           <s>mine is just um a little dirty</s></u>
]]>
</eg>

<!-- from MacWhinney 88, 87, cited by SJ -->

<p>This example also uses some elements common to all TEI texts,
notably the <gi>reg</gi> tag for editorial regularization.  Special
purpose entity references have been used to indicate non-separating
spaces (<code type=frag>&amp;sp</code>) and unusually stressed syllables
(<code type=frag>&amp;stress</code>); an alternative to the latter might
have been to use the core <gi>emph</gi> element.  The <gi>s</gi> element
has also been used to segment the last utterance.  Further discussion of
all of these options is provided in section <ptr target=TSsa>.

<p>Contextual information is of particular importance in spoken texts,
and is usually provided by the TEI header of a text.  In general, all
of the information in a header is understood to be relevant to the whole
of the associated text.  The elements <gi>u</gi> and <gi>writing</gi>
are however members of the <ident type=class>declaring</ident> class,
and may therefore specify a different context from that of the
surrounding elements within a given division or text by means of the
<att>decls</att> attribute (see further section <ptr target=CCas>).

<div3 id=TSbaut><head>Utterances</head>

<p>Each distinct <term>utterance</term> in a spoken text is represented
by a <gi>u</gi> element, described as follows:

<list type=gloss>
<label><gi>u</gi></label>
<item>a stretch of speech usually preceded and followed by

silence or by a change of speaker.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies an identifier for the speaker or group of 
speakers. Its value is the identifier of a 
<tag>participant</tag> or <tag>participantGrp</tag> element 
in the TEI header.</item>
<label><att>trans</att></label>
<item>indicates the nature of the transition between this 
utterance and the previous one.
Sample values include:
<list type=gloss>
<label><term>latching</term></label>
<item>this utterance begins with a markedly shorter pause than 
normal.</item>
<label><term>smooth</term></label>
<item>this utterance begins without unusual pause or 
rapidity.</item>
<label><term>overlap</term></label>
<item>this utterance begins before the previous one has 
finished.</item>
<label><term>pause</term></label>
<item>this utterance begins after a noticeable pause.</item>
</list></item>
</list>
</item>
<!-- decided against part attribute for now -->
</list>


<p>Use of the <att>who</att> attribute to associate the utterance with a
particular speaker is recommended but not required.  Its use implies as
a further requirement that all speakers be identified by a
<gi>person</gi> or <gi>personGrp</gi> element in the TEI
header (see section <ptr target=ccahpa>).  Where utterances cannot be
attributed with confidence to any particular participant or group of
participants, the encoder may choose to define
<soCalled>participants</soCalled> such as <ident type=var>all</ident> or
<ident type=var>various</ident>.  For example:

<eg>
<![ CDATA[
<u who=A>     <!-- utterance by speaker A -->
<u who='A B'> <!-- utterance by speakers A and B -->
<u who='ALL'> <!-- utterance by speaker group ALL -->
]]>
</eg>

<p>The <att>trans</att> attribute is provided as a means of
characterizing the transition from one utterance to the next at a
simpler level of detail than that provided by the temporal alignment
mechanism discussed in section <ptr target=SAsy>.  The value specified
applies to the transition from the preceding utterance into the
utterance bearing the attribute.  For example:<note place=foot>For
the most part, the examples in this chapter use no sentence punctuation
except to mark the rising intonation often found in interrogative
statements; for further discussion, see section <ptr target=TSreg>.
</note>

<eg>
<![ CDATA[
   <u id=A1 who=A>Have you heard the</u>
   <u id=B1 who=B trans=latching>the election results? yes</u>
   <u id=A2 who=A trans=pause>it's a disaster</u>
   <u id=B2 who=B trans=overlap>it's a miracle</u>
]]>
</eg>

In this example, utterance B1 latches on to utterance A1, while there is
a marked pause between B1 and A2.  B2 and A2 overlap, but by an
unspecified amount.  For ways of providing a more precise indication of
the degree of overlap, see section <ptr target=TSsapa>.

<p>An utterance may contain either running text, or text within which
other basic structural elements are nested.  Where such nesting occurs,
the <att>who</att> attribute is considered to be inherited for the
elements <gi>pause</gi>, <gi>vocal</gi>, <gi>shift</gi> and
<gi>kinesic</gi>; that is, a pause or shift (etc.) within an utterance
is regarded as being produced by that speaker only, while a pause
between utterances applies to all speakers.

<p>Occasionally, an utterance may contain other utterances, for example
where there is a change in the script associated with it.  This may
occur when a speaker changes script in mid-utterance.  For example:

<eg>
<![ CDATA[
    <!-- breakfast table conversation ... -->
    <u who=A>Listen to this
       <u who=A decls=S1>The government is confident, he
       said, that the current economic problems will be
       completely overcome by June</u>
    what nonsense</u>
]]>
</eg>

Here speaker A's own utterance contains a second nested utterance, which
is read from a newspaper.  The <att>decls</att> attribute on the nested
utterance is used to indicate that its script is S1, rather than the
default.  Alternatively, the embedded utterance might be regarded as a
new (non-nested) one.  It might also be encoded using the
<gi>writing</gi> element described in section <ptr target=TSbavo>
below, or the <gi>event</gi> element described in section <ptr
target=TSbavo>, without transcribing the read material:

<eg>
<![ CDATA[
    <u who=A>Listen to this <event desc='reads'>
    what nonsense</u>
]]>
</eg>


<div3 id=TSbapa><head>Pause</head>

<p>The <gi>pause</gi> empty element is used to indicate a perceived
pause, either between or within utterances.

<list type=gloss>
<label><gi>pause</gi></label>
<item>a pause either between or within utterances.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies an identifier for the person or group pausing. Its 
value is the identifier of a <tag>participant</tag> or 
<tag>participant.grp</tag> element in the TEI header.</item>
<label><att>type</att></label>
<item>categorizes the pause in some respect.</item>
</list>
</item>
</list>


A pause contained by an utterance applies to the speaker of that
utterance.  A pause between utterances applies to all speakers.  The
<att>type</att> attribute may be used to categorize the pause, for
example as short, medium or long; alternatively the attribute
<att>dur</att> may be used to indicate its length more exactly, as in
the following example:

<eg><![ CDATA [
<u>Okay <pause dur=200>U-m<pause dur=75>the s the scene
opens up <pause dur=50> with <pause dur=20> um <pause dur=145>
you see a tree okay? </u>
]]>
</eg>

<!-- example recoded from Chafe  -->

If detailed synchronization of pausing with other vocal phenomena is
required, the alignment mechanism defined at section <ptr target=SAsy>
and discussed informally below should be used.  Note that the
<att>trans</att> attribute mentioned in the previous section may also be
used to characterize the degree of pausing between (but not within)
utterances.

<div3 id=TSbavo><head>Vocal, Kinesic, Event</head>

<p>These three empty elements are used to indicate the presence of
non-transcribed semi-lexical or non-lexical phenomena either between or
within utterances.

<list type=gloss>
<label><gi>vocal</gi></label>
<item>any vocalized but not necessarily lexical phenomenon, for 
example
voiced pauses, non-lexical backchannels, etc.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies an identifier for the vocalist(s). Its value is 
the identifier of a <tag>participant</tag> or 
<tag>participant.grp</tag> element in the TEI header.</item>
<label><att>desc</att></label>
<item>supplies a conventional representation for the phenomenon.</item>
<label><att>iterated</att></label>
<item>indicates whether or not the phenomenon is repeated.
Sample values include:
<list type=gloss>
<label><term>u</term></label>
<item>unknown or unmarked.</item>
<label><term>y</term></label>
<item>the phenomenon is repeated.</item>
<label><term>n</term></label>
<item>the phenomenon is atomic.</item>
</list></item>
</list>
</item>
<label><gi>kinesic</gi></label>
<item>any communicative phenomenon, not necessarily vocalized, 
for
example a gesture, frown, etc.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies an identifier for the participant performing the 
gesture. Its value is the identifier of a 
<tag>participant</tag> or <tag>participant.grp</tag> 
element in the TEI header.</item>
<label><att>desc</att></label>
<item>supplies a conventional representation for the phenomenon.</item>
<label><att>iterated</att></label>
<item>indicates whether or not the phenomenon is repeated.
Sample values include:
<list type=gloss>
<label><term>u</term></label>
<item>unknown or unmarked.</item>
<label><term>y</term></label>
<item>the phenomenon is repeated.</item>
<label><term>n</term></label>
<item>the phenomenon is atomic.</item>
</list></item>
</list>
</item>
<label><gi>event</gi></label>
<item>any phenomenon or occurrence, not necessarily vocalized or

communicative, for example incidental noises or other 
events affecting
communication.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies an identifier for the agent of the event 
described, if any. Its value is the identifier of a 
<tag>participant</tag> or <tag>participant.grp</tag> 
element in the TEI header.</item>
<label><att>desc</att></label>
<item>supplies a conventional representation for the phenomenon.</item>
<label><att>iterated</att></label>
<item>indicates whether or not the phenomenon is repeated.
Sample values include:
<list type=gloss>
<label><term>u</term></label>
<item>unknown or unmarked.</item>
<label><term>y</term></label>
<item>the phenomenon is repeated.</item>
<label><term>n</term></label>
<item>the phenomenon is atomic.</item>
</list></item>
</list>
</item>
</list>


<p>The <att>who</att> attribute should be used to specify the person or
group responsible for a vocal, kinesic or event which is contained
within an utterance, if this differs from that of the enclosing
utterance.  The attribute must be supplied for a vocal, kinesic or event
which is not contained within an utterance.

<p>The <att>iterated</att> attribute may be used to indicate that the
vocal, kinesic or event is repeated, for example <code
type=val>laughter</code> as opposed to <code type=val>laugh</code>.
These should both be distinguished from <code type=val>laughing</code>,
where what is being encoded is a shift in voice quality.  For this last
case, the <gi>shift</gi> element discussed in section <ptr
target=TSsash> should be used.

<p>The <att>desc</att> attribute may be used to supply a conventional
representation for the phenomenon, for example:

<list type=gloss>
<label>non-lexical <item>burp, click, cough, exhale, giggle, gulp,
    inhale, laugh, sneeze, sniff, snort, sob, swallow, throat, yawn
    </item>
<label>semi-lexical <item>ah, aha, aw, eh, ehm, er, erm, hmm, huh,
    mm, mmhm, oh, ooh, oops, phew, tsk, uh, uh-huh, uh-uh, um, urgh,
    yup</item>
</list>

Researchers may prefer to regard some semi-lexical phenomena as
<soCalled>words</soCalled> within the bounds of the <gi>u</gi> element.
See further the discussion at section <ptr target=TSreg> below.  As
for all basic categories, the definition should be made clear in the
<gi>encodingDesc</gi> element of the TEI header.

<p>Some typical examples follow (recoded from
<bibl><author>J. Maxwell Atkinson and John Heritage, eds.,</author>
<title>Transcript notation.  Structures of social action:  Studies in
conversation analysis,</title> Cambridge University Press,
1984</bibl>).

<eg>
<![ CDATA [
<u who=Jan>This is just delicious</u>
<event desc='telephone rings'>
<u who=Kim>I'll get it</u>

<u who=Tom>I used to <vocal desc=cough> smoke a lot</u>
<u who=Bob><vocal desc=sniff>He thinks he's tough</u>
<vocal who=Ann desc=snorts>
]]>
</eg>

Note that Ann's snorting could equally well be encoded as follows:

<eg>
<![ CDATA [
<u who=Ann><vocal desc=snorts></u>
]]>
</eg>

<p>The extent to which encoding of events or kinesics is included in a
transcription will depend entirely on the purpose for which the
transcription was made.  As elsewhere, this will depend on the
particular research agenda and the extent to which their presence is
felt to be significant for the interpretation of spoken interactions.

<!-- <p>It is not envisaged that events or kinesics should    -->
<!-- be included in any transcription, except where their     -->
<!-- presence is felt to be of potential significance for     -->
<!-- the interpretation of the interaction.                   -->
<!--                                                          -->

<!-- delete following section? -->
<!-- added an example anyway  (LB dec 93)-->

<div3 id=TSbawr><head>Writing</head>

<p>Written text may also be encountered when speech is transcribed, for
example in a television broadcast or cinema performance, or where one
participant shows written text to another.  The <gi>writing</gi> element
may be used to distinguish such written elements from the spoken text in
which they are embedded.

<list type=gloss>
<label><gi>writing</gi></label>
<item>a passage of written text revealed to participants in the 
course
of a spoken text.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies an identifier for the participant who reveals or 
creates the writing, if any. Its value is the identifier of 
a <tag>participant</tag> or <tag>participant.grp</tag> 
element in the TEI header.</item>
<label><att>gradual</att></label>
<item>indicates whether the writing is revealed all at once or 
gradually.
Sample values include:
<list type=gloss>
<label><term>u</term></label>
<item>unknown or unmarked.</item>
<label><term>y</term></label>
<item>the writing is revealed gradually.</item>
<label><term>n</term></label>
<item>the writing is revealed all at once.</item>
</list></item>
<label><att>type</att></label>
<item>categorizes the kind of writing in some way, for example as 
a subtitle, noticeboard etc.</item>
</list>
</item>
</list>


<!-- example needed -->

For example, if speaker A in the breakfast table conversation in section
<ptr target=TSbaut> above had simply shown the newspaper passage to her
interlocutor instead of reading it, the interaction might have been
encoded as follows:

<eg>
<![ CDATA [
    <u who=A>look at this</u>
    <writing who=A gradual=N type=newspaper>
      The government is confident, he said, that the
      current economic problems will be completely overcome
      by June</writing>
    <u who=A>what nonsense!</u>
]]>
</eg>

<div3 id=TSbati><head>Temporal Information</head>

<p>In addition to the global attributes <att>n</att>, <att>id</att>, and
<att>lang</att>, utterances, vocals, pauses, kinesics, events and
writing elements may all take a common set of attributes providing
information about their position in time.  For this reason, these
elements are regarded as forming a <term>class</term>, referred to here
as <ident type=class>timed</ident>.  The following attributes are common
to all elements in this class:

<list type=gloss>
<label><att>start</att></label>
<item>indicates the location within a temporal alignment at which 
this element begins.</item>
<label><att>end</att></label>
<item>indicates the location within a temporal alignment at which 
this element ends.</item>
<label><att>dur</att></label>
<item>indicates the length of this element in time, using either 
specific units or the units specified on the associated 
temporal alignment.</item>
</list>

Note that if <att>start</att> and <att>end</att> point to <gi>when</gi>
elements whose temporal distance from each other is specified in a
timeline, then <att>dur</att> is ignored.

<p>The <gi>anchor</gi> element (see <ptr target=SAcs>) may be used as
an alternative means of aligning the start and end of timed elements,
and is required when the temporal alignment involves points within an
element.

<div3 id=TSsash><head>Shifts</head>

<p>A common requirement in transcribing spoken language is to mark
positions at which a variety of prosodic features change.  Many
paralinguistic features (pitch, prominence, loudness, etc.) characterize
stretches of speech which are not co-extensive with utterances or any of
the other units discussed so far.  One simple method of encoding such
units is simply to mark their boundaries.  An empty element called
<gi>shift</gi> is provided for this purpose.

<list type=gloss>
<label><gi>shift</gi></label>
<item>marks the point at which some paralinguistic feature of a 
series of
utterances by any one speaker changes.
Attributes include:
<list type=gloss>
<label><att>feature</att></label>
<item>a paralinguistic feature.
Sample values include:
<list type=gloss>
<label><term>tension</term></label>
<item>tension or stress pattern.</item>
<label><term>pitch</term></label>
<item>pitch range.</item>
<label><term>loud</term></label>
<item>loudness.</item>
<label><term>voice</term></label>
<item>voice quality.</item>
<label><term>tempo</term></label>
<item>speed of utterance.</item>
<label><term>rhythm</term></label>
<item>rhythmic qualities.</item>
</list></item>
<label><att>new</att></label>
<item>specifies the new state of the paralinguistic feature 
specified.</item>
</list>
</item>
</list>


A <gi>shift</gi> element may appear within an utterance or a segment to
mark a significant change in the particular feature defined by its
attributes, which is then understood to apply to all subsequent
utterances for the same speaker, unless changed by a new shift for the
same feature in the same speaker.  Intervening utterances by other
speakers do not normally carry the same feature.

For example:

<eg><![ CDATA[
    <u who=LB><shift feature=loud new=f>Elizabeth</u>
    <u who=EB>Yes</u>
    <u who=LB><shift feature=loud>Come and try this <pause>
         <shift feature=loud new=ff>come on</u>
]]>
</eg>

In this example, the word <mentioned>Elizabeth</mentioned> is spoken loudly, the
words <mentioned>Yes</mentioned> and <mentioned>Come and try this</mentioned> with
normal volume, and the words <mentioned>come on</mentioned> very loudly.

<p>The values proposed here for the <att>feature</att> attribute are
based on those used by the Survey of English Usage;
<note>For details see <bibl>S. Boase, <title>London-Lund
    Corpus:  Example Text and Transcription Guide</title> (London:
    Survey of English Usage, University College London,
    1990)</bibl>.
</note>
this list may be revised or supplemented using the methods outlined in
section <ptr target=MD>.

<p>The <att>new</att> attribute specifies the new state of the feature
following the shift.  If no value is specified, it is implied that the
feature concerned ceases to be remarkable at this point:  the special
value <code type=val>normal</code> may be specified to have the same
effect.

<!-- this rather abstruse point suppressed for now -->
<!--                                                          -->
<!-- < p>A <gi>shift</gi> itself can be aligned with other    -->
<!-- elements only by being pointed at from an alignment.     -->
<!-- If therefore alignment is expressed by pointing from     -->
<!-- the text, rather than into it, a <gi>ptr</gi> element    -->
<!-- following the < gi>shift</gi> should be used.  See       -->
<!-- further < xref target=TSsapa>.                           -->
<!--                                                          -->

<p>A list of suggested values for each of the features proposed follows:

<list>
<item>tempo
<list type=gloss>
<label>a    <item>allegro (fast)</item>
<label>aa   <item>very fast</item>
<label>acc  <item>accelerando (getting faster)</item>
<label>l    <item>lento (slow)</item>
<label>ll   <item>very slow</item>
<label>rall <item>rallentando (getting slower)</item></list>
</item>
<item>loud (for loudness):
<list type=gloss>
<label>f     <item>forte (loud)</item>
<label>ff    <item>very loud</item>
<label>cresc <item>crescendo (getting louder)</item>
<label>p     <item>piano (soft)</item>
<label>pp    <item>very soft</item>
<label>dimin <item>diminuendo (getting softer)</item>
</list></item>
<item>pitch (for pitch range):
<list type=gloss>
<label>high  <item>high pitch-range</item>
<label>low   <item>low pitch-range</item>
<label>wide  <item>wide pitch-range</item>
<label>narrow<item>narrow pitch-range</item>
<label>asc   <item>ascending</item>
<label>desc  <item>descending</item>
<label>monot <item>monotonous</item>
<label>scand <item>scandent, each succeeding syllable higher than
                   the last, generally ending in a falling tone</item>
</list></item>
<item>tension:
<list type=gloss>
<label>sl  <item>slurred</item>
<label>lax <item>lax, a little slurred</item>
<label>ten <item>tense</item>
<label>pr  <item>very precise</item>
<label>st  <item>staccato, every stressed syllable being doubly
                 stressed</item>
<label>leg <item>legato, every syllable receiving more or less equal
                 stress</item>
</list></item>
<item>rhythm:
<list type=gloss>
<label>rh   <item>beatable rhythm</item>
<label>arrh <item>arrhythmic, particularly halting</item>
<label>spr  <item>spiky rising, with markedly higher unstressed
                  syllables</item>
<label>spf  <item>spiky falling, with markedly lower unstressed
                  syllables</item>
<label>glr  <item>glissando rising, like spiky rising but the
                  unstressed syllables, usually several, also rise
                  in pitch relative to each other</item>
<label>glf  <item>glissando falling, like spiky falling but with the
                  unstressed syllables also falling in pitch relative
                  to each other</item>
</list></item>
<item>voice (for voice quality):
<list type=gloss>
<label>whisp   <item>whisper</item>
<label>breath  <item>breathy</item>
<label>husk    <item>husky</item>
<label>creak   <item>creaky</item>
<label>fals    <item>falsetto</item>
<label>reson   <item>resonant</item>
<label>giggle <item>unvoiced laugh or giggle</item>
<label>laugh  <item>voiced laugh</item>
<label>trem   <item>tremulous</item>
<label>sob    <item>sobbing</item>
<label>yawn   <item>yawning</item>
<label>sigh   <item> sighing</item>
</list>
</item>
</list>

<p>A full definition of the sense of the values provided for each
feature should be provided in the encoding description section of the
text header (see section <ptr target=HD5>).

<div3 id=TSbafd><head>Formal Definition</head>

<p>The components of the tag set for transcribed speech are formally
defined as follows:

<eg id=dtscomp>
<![ CDATA [
<!-- 11.2.7:  Components of Transcribed Speech                -->
<!ELEMENT u             - -  ((%phrase | %m.comp.spoken)+)      >
<!ATTLIST u                  %a.global;
                             %a.declaring;
                             %a.timed;
          who                IDREFS              %INHERITED
          trans              (smooth | latching | overlap | 
                             pause)              smooth         >
<!ELEMENT pause         - O  EMPTY                              >
<!ATTLIST pause              %a.global;
                             %a.timed;
          who                IDREF               #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT vocal         - O  EMPTY                              >
<!ATTLIST vocal              %a.global;
                             %a.timed;
          desc               CDATA               #IMPLIED
          who                IDREF               %INHERITED
          iterated           (y | n | u)         n              >
<!ELEMENT kinesic       - O  EMPTY                              >
<!ATTLIST kinesic            %a.global;
                             %a.timed;
          desc               CDATA               #IMPLIED
          who                IDREF               %INHERITED
          iterated           (y | n | u)         n              >
<!ELEMENT event         - O  EMPTY                              >
<!ATTLIST event              %a.global;
                             %a.timed;
          desc               CDATA               #IMPLIED
          who                IDREF               %INHERITED
          iterated           (y | n | u)         n              >
<!ELEMENT writing       - -  (%paraContent;)                    >
<!ATTLIST writing            %a.global;
          who                IDREF               %INHERITED
          script             IDREF               #IMPLIED
          gradual            (y | n | u)         #IMPLIED
          type               CDATA               #IMPLIED       >
<!ELEMENT shift         - O  EMPTY                              >
<!ATTLIST shift              %a.global;
          who                IDREF               #IMPLIED
          new                CDATA               normal
          feature            (tempo | loud | pitch | tension | 
                             rhythm | voice)     #REQUIRED      >
<!-- This fragment is used in sec. 11                         -->
]]>
</eg>




<!-- $Id: p2tssa.odd,v 1.10 1998/02/05 17:18:04 tei Exp $ -->
<!--**
    * $Log: p2tssa.odd,v $
    * Revision 1.10  1998/02/05 17:18:04  tei
    * *** empty log message ***
    *
    * Revision 1.9  98/02/05  17:14:35  tei
    * make examples parse
    *
    * Revision 1.8  98/02/01  17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.6  1994/03/27  21:46:39  msmcq
    * Correction of typos reported by DB, EB.
    *
    * Revision 1.5  1994/02/17  20:29:04  msmcq
    * revision for SC review
    * -->

<!-- Revisions:                                               -->
<!-- 18 jan 98 : LB : fix errors in egs -->
<!-- 4 Jan 98 : LB : it's <gap>, not <omit> stupid!           -->
<!-- 94-03-26 : MSM : typos, changes from EBr and DB          -->
<!-- 94-02-14 : MSM : more cleanup                            -->
<!-- 94-02-14 : MSM : minor cleanup                           -->
<!-- 94-02-14 : MSM : Added RCS id                            -->
<!-- 11 nov : LB : add material on segmentation, Pixi example -->
<!-- 20 aug : LB re-revise; rejig order somewhat              -->
<!-- 93-07-15 : DTL : revise in light of SAsy                 -->
<!-- 93-02-10 : MSM : correct typos in two xrefs              -->
<!-- 93-02-10 : MSM : suppress illegal EOF character          -->
<!-- 10 Feb 93 : WP : Changed 34 to 10.                       -->
<!--  4 Feb 93 : WP : Changed P234 to P2TS                    -->
<!-- 22f Apr 92 : CMSMcQ : final changes before release       -->
<!-- 18 Apr 92 : LB : fiddled with suggested value names for SHIFT -->
<!-- 18 Apr 92 : CMSMcQ : further changes, largely cosmetic -->
<!-- 17 Apr 92 : WP     : spellcheck & make changes         -->
<!-- 16 Apr 92 : CMSMcQ : repunctuate, prettify, clean      -->

<div2 id="TSsa"><head>Elements Defined Elsewhere</head>

<p>This section describes the following features characteristic of
spoken texts for which elements are defined elsewhere in these
Guidelines:

<list>
<item>segmentation below the utterance level</item>
<item>synchronization and overlap</item>
<item>regularization of orthography</item>
</list>

The elements discussed here are not provided by the base tag set for
spoken texts.  Some of them are included in the core tag set available
to all TEI documents, but others are contained in the TEI additional
tag sets for linking and for analysis respectively.  To enable these tag
sets, the appropriate parameter entities must be declared in the
document type declaration subset, as described in section <ptr
target="STin">.  For example, if a transcript using the base tag set
defined in this chapter additionally wishes to make use of the
<gi>timeLine</gi> element, then the following declarations would be
necessary:

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

If the complex segmentation elements defined in the additional tag set
for analysis were also required, the following declarations would be
needed:

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

<!-- I still think it's completely bonkers not to define timeline here. LB --></p>

<div3 id="TSsase"><head>Segmentation</head>

<p>For some analytic purposes it may be desirable to subdivide the
divisions of a spoken text into units smaller than the individual
utterance or turn.  Segmentation may be performed for a number of
different purposes and in terms of a variety of speech phenomena.
Common examples include units defined both prosodically (by intonation,
pausing, etc.) and syntactically (clauses, phrases, etc.)  The term
<term>macrosyntagm</term> has been used by a number of researchers to
define units peculiar to speech transcripts.  <note>The term was
apparently first proposed by <bibl><author>Bengt Loman and Nils
J&oslash;rgensen</author>, in <title>Manual for analys och beskrivning
av makrosyntagmer</title> (Lund:  Studentlitteratur, 1971)</bibl>,
where it is defined as follows:  <q>A text can be analysed as a sequence
of segments which are internally connected by a network of syntactic
relations and externally delimited by the absence of such relations with
respect to neighbouring segments.  Such a segment is a syntactic unit
called a macrosyntagm</q> (trans.  S. Johansson).</note></p>

<p>These Guidelines propose that such analyses be performed in terms of
neutrally-named <term>segments</term>, represented by the <gi>seg</gi>
element, which is discussed more fully in section <ptr target="SAse">.
This element may take a <att>type</att> attribute to specify the kind of
segmentation applicable to a particular segment, if more than one is
possible in a text.  A full definition of the segmentation scheme or
schemes used should be provided in the <gi>segmentation</gi> element of
the <gi>editorialDecl</gi> element in the TEI header (see <ptr
target="HD53">).</p>

<p>In the first example below, an utterance has been segmented according
to a notion of syntactic completeness not necessarily marked by the
speech, although in this case a pause has been recorded between the two
sentence-like units.  In the second, the segments are defined
prosodically (an entity reference <code type="frag">&amp;stress;</code>
has been used to mark the position immediately following the syllable
bearing the primary accent or stress), and may be thought of as
<socalled>tone units</socalled>.

<eg>
<![ CDATA [
<u who=M1><seg>we went to the pub yesterday</seg>
    <pause><seg>there was no one there</seg>
</u>
<u who=F1><seg>although its an old ide&stress;a</seg>
    <seg>it hasnt been on the mar&stress;ket very long</seg>
</u>
]]>
</eg>

<!-- examples from J Payne NERC Report -->

In either case, the <gi>segmentation</gi> element in the header of the
text should specify the principles adopted to define the segments marked
in this way.</p>

<p>When utterances are segmented end-to-end in the same way as the
s-units in written texts, the <gi>s</gi> element discussed in chapter
<ptr target="AI"> may be used, either as an alternative or in addition to
the more general purpose <gi>seg</gi> element.  The <gi>s</gi> element
is available without formality in all texts, but does not allow segments
to nest within each other.

<!-- need more specific xref --></p>

<p>Where segments of different kinds are to be distinguished within the
same stretch of speech, the <att>type</att> attribute may be used, as in
the following example.  The example also shows the use of a
user-specified extension to the TEI tag sets, for specifying
paraphasia.

<eg>
<![ CDATA [
<text><body>
<u who=T1>
<seg type=C>I think </seg>
<seg type=C>this chap was writing </seg>
<seg type=C>and he <del type=repeated>said hello</del> said </seg>
<seg type=M>hello </seg>
<seg type=C>and he said </seg>
<seg type=C>I'm going to a <paraphasia>gate</paraphasia>
            at twenty past seven </seg>
<seg type=C>he said </seg>
<seg type=M>ok </seg>
<seg type=M>right away </seg>
<seg type=C>and so <gap desc=unclear extent='1'> on they went </seg>
<seg type=C>and they were <gap desc=unclear extent='3'>
            writing there </seg>
</u>
</body></text>
]]>
</eg>
<!-- <note>Reference needed!</note>                           -->

In this example, recoded from a corpus of language-impaired speech
prepared by Fletcher and Garman, the speaker's utterance has been fully
segmented into clausal (<code type="frag">type=C</code>) or minor (<code
type="frag">type=M</code>) units.  An additional element <gi tei="no">paraphasia</gi> has been used to define a particular
characteristic of this corpus for which no element exists in the TEI
scheme.

<!--  removed because would need to put these into two separate -->
<!-- files (TEI.extensions.ent, TEI.extensions.dtd) and it would -->
<!-- take too long to explain here why. Probably. But should remember -->
<!-- to refer back to this e.g. in p2MD . (LB) -->
<!-- The following declarations might be added to the doctype subset -->
<!-- to effect the declaration of this element:  -->
<!-- ELEMENT paraphasia - - (%phraseSeq) -->
<!-- ENTITY % x.phrase "paraphasia|" -->

See further chapter <ptr target="MD"> for a discussion of the way in
which this kind of user-defined extension of the TEI scheme may be
performed and chapter <ptr target="ST"> for the mechanisms on which it
depends.</p>

<p>This example also uses the core elements <gi>gap</gi> and
<gi>del</gi> to mark editorial decisions concerning matter completely
omitted from the transcript (because of inaudibility), and words which
have been transcribed but which the transcriber considers may be
deleted, respectively.  See further section <ptr target="COed"> for a
discussion of these and related elements.</p>

<p>It is often the case that the desired segmentation does not respect
utterance boundaries; for example, syntactic units may cross utterance
boundaries.  For a detailed discussion of this problem, and the various
methods proposed by these Guidelines for handling it, see chapter
<ptr target="NH">.  Methods discussed there include these:

<list>
<item>a concurrent DTD may be defined</item>
<item><socalled>milestone</socalled> tags may be used;
the special-purpose <gi>shift</gi> tag discussed
in section <ptr target="TSsash"> is an extension of this method</item>
<item>where several discontinuous segments are to be grouped
together to form a syntactic unit (e.g. a phrasal verb with interposed
complement), the <gi>join</gi> element may be used</item>
</list></p></div3>

<div3 id="TSsapa"><head>Synchronization and Overlap</head>

<p>A major difference between spoken and written texts is the importance
of the temporal dimension to the former.  As a very simple example,
consider the following, first as it might be represented in a
playscript:

<eg>
<![ CDATA[
    Jane: Have you read Vanity Fair?
    Stig: Yes
    Lou: (nods vigorously)
]]>
</eg>

Let us assume that Stig and Lou respond to Jane's question before she
has finished asking it --- a fairly normal situation in spontaneous
speech.  The simplest way of representing this <term>overlap</term>
would be to use the <att>trans</att> attribute previously discussed:

<eg>
<![ CDATA[
<u who=Jane>have you read Vanity Fair</u>
<u who=Stig trans=overlap>yes</u>
<!-- ... -->
]]>
</eg>

However, this does not allow us to indicate either the extent to which
Jane's utterance is overlapped, nor does it show that there are in
fact three things which are synchronous:  the end of Jane's utterance,
Stig's whole utterance, and Lou's kinesic.  To overcome these problems,
more sophisticated techniques, employing the mechanisms for pointing and
alignment discussed in detail in section <ptr target="Sasy">, are needed.
If the additional tag set for linking has been enabled (as described in
section <ptr target="TSsase"> above), one way to represent the simple
example above would be as follows:

<eg>
<![ CDATA[
<text><body>
<u id=u1 who=Jane>have you read Vanity
   <anchor id=a1 synch='u2 k1'> Fair</u>
<u who=Stig id=u2>yes</u>
<kinesic id=k1 who=Lou iterated=Y desc=nod>
</body></text>
]]>
</eg></p>

<p>For a full discussion of this and related mechanisms, section <ptr
target="SAsymp"> should be consulted.  The rest of the present section,
which should be read in conjunction with that more detailed discussion,
presents a number of ways in which these mechanisms may be applied to
the specific problem of representing temporal alignment, synchrony or
overlap in transcribing spoken texts.</p>

<p>In the simple example above, the first utterance (that with
identifier u1) contains an <gi>anchor</gi> element, the function of
which is simply to mark a point within it.  The <att>synch</att>
attribute associated with this anchor point specifies the identifiers of
the other two elements which are to be synchronized with it:
specifically, the second utterance (u2) and the kinesic (k1).  Note that
one of these elements has content and the other is empty.</p>

<p>This example demonstrates only a way of indicating a point within one
utterance at which it can be synchronized with another utterance and a
kinesic.  For more complex kinds of alignment, involving possibly
multiple synchronization points, an additional element is provided,
known as a <gi>timeLine</gi>.  This consists of a series of
<gi>when</gi> elements, each representing a point in time, and bearing
attributes which indicate its exact temporal position relative to other
elements in the same timeline, in addition to the sequencing implied by
its position within it.</p>

<p>For example:

<eg>
<![ CDATA[
<timeLine unit=dsec>
   <when id=P1 absolute="12:20:01:01 BST">
   <when id=P2 interval=45 since=P1>
   <when id=P6>
   <when id=P3 interval=15 since=P6>
</timeLine>
]]>
</eg>

This timeline represents four points in time, named P1, P2, P6, and P3
(as with all attributes named <att>id</att> in the TEI scheme, the
names must be unique within the document but have no other
significance).  P1 is located absolutely, at 12:20:01:01 BST.  P2 is 4.5
seconds (i.e. 45 deci-seconds) later than P2 (i.e. at 12:20:46).  P6 is
at some unspecified time later than P2 and previous to P3 (this is
implied by its position within the timeline, as no attribute values have
been specified for it).  The fourth point, P3, is 1.5 seconds (15 dsec)
later than P6.</p>

<p>One or more such timelines may be specified within a spoken text, to
suit the encoder's convenience.  If more than one is supplied, the
<att>origin</att> attribute may be used on each to specify which other
<gi>timeLine</gi> element it follows.  The <att>unit</att> attribute
indicates the units used for timings given on <gi>when</gi> elements
contained by the alignment map.  Alternatively, to avoid the need to
specify times explicitly, the <att>interval</att> attribute may be used
to indicate that all the <gi>when</gi> elements in a time line are a
fixed distance apart.</p>

<p>Three methods are available for aligning points or elements within a
spoken text with the points in time defined by the <gi>timeLine</gi>:
<list> <item>The elements to be synchronized may specify the identifier
of a <gi>when</gi> element as the value of one of the <att>start</att>,
<att>end</att> or <att>synch</att> attributes</item> <item>The <gi>when</gi>
element may specify the identifiers of all the elements to be
synchronized with it using the <att>synch</att> attribute</item> <item>A
free-standing <gi>link</gi> element may be used to associate the
<gi>when</gi> element and the elements synchronized with it by
specifying their identifiers as values for its <att>target</att>
attribute.</item>  </list></p>

<p>For example, using the timeline given above:

<eg>
<![ CDATA[
<text><body>
     <u id=U1 start=P2 end=P3>
         This is my <anchor id=P6A synch=P6> turn
      </u>
</body></text>
]]>
</eg>

The start of this utterance is aligned with P2 and its end with P3.  The
transition between the words <mentioned>my</mentioned> and <mentioned>turn</mentioned>
occurs at point P6A, which is synchronous with point P6 on the timeline.</p>

<p>The synchronization represented by the preceding examples could
equally well be represented as follows:

<eg>
<![ CDATA[
<text><body>
    <timeLine unit=dsec origin=P1>
     <when id=P1 absolute="12:20:01:01 BST">
     <when id=P2 interval=45 since=P1 synch=U1>
     <when id=P6 synch=X1>
     <when id=P3 interval=15 since=P6 synch=U1>
    </timeLine>
    <!-- ... -->
    <u id=U1>This is my <anchor id=X1> turn</u>
</body></text>
]]>
</eg>

Here, the whole of the object with identifier U1 (the utterance) has
been aligned with two different points, P2 and P3.  This is interpreted
to mean that the utterance spans at least those two points.</p>

<p>Finally, a <gi>linkGrp</gi> may be used as an alternative to the
<att>synch</att> attribute:

<eg>
<![ CDATA[
<text><body>
    <timeLine unit=dsec origin=P1>
      <when id=P1 absolute="12:20:01:01 BST">
      <when id=P2 interval=45 since=P1>
      <when id=P6>
      <when id=P3 interval=15 since=P6>
    </timeLine>
   <!-- ... -->
    <u id=U1><anchor id=U1start>
             This is my <anchor id=X1> turn
             <anchor id=U1end>
   </u>
    <linkGrp type=synchronous>
        <link targets='U1start P1'>
        <link targets='U1end P2'>
        <link targets='X1 P6'>
    </linkGrp>
</body></text>
]]>
</eg></p>

<p>As a further example of the three possibilities, consider the
following dialogue, represented first as it might appear in a
conventional playscript:

<eg>
<![ CDATA[
  Tom: I used to smoke - -
  Bob: (interrupting) You used to smoke?
  Tom: (at the same time) a lot more than this.  But I never
       inhaled the smoke
]]>
</eg>
<!-- Atkinson and Heritage (1984) ix-xvi -->

A commonly used convention might be to transcribe such a passage as
follows:

<eg>
<![ CDATA[
  <1> I used to smoke [ a lot more than this ]
  <2>                 [ you used to smoke ]
  <1> but I never inhaled the smoke
]]>
</eg>

Such conventions have the drawback that they are hard to generalize or
to extend beyond the very simple case presented here.  Their reliance on
the accidentals of physical layout may also make them difficult to
transport and to process computationally.  These Guidelines recommend
one of the courses described in what follows:</p>

<p>Where the whole of one or another utterance is to be synchronized,
the <att>start</att> and <att>end</att> attributes may be used:

<eg>
<![ CDATA[
<text><body>
  <u who=TOM>I used to smoke <anchor id=P1> a lot more than this
       <anchor id=P2>but I never inhaled the smoke</u>
  <u who=BOB start=P1 end=P2>You used to smoke</u>
</body></text>
]]>
</eg>

Note that the second utterance above could equally well be encoded as
follows with exactly the same effect:

<eg>
<![ CDATA[
<u who=BOB><anchor synch=P1>You used to smoke<anchor synch=P2></u>
]]>
</eg></p>

<p>If synchronization with specific timing information is required, a
<gi>timeLine</gi> must be included:

<eg>
<![ CDATA[
<text><body>
  <timeLine origin=T1>
     <when id=T1>
     <when id=T2>
  </timeLine>
  <!--  .... -->
  <u who=TOM>I used to smoke
       <anchor synch=T1>a lot more than this
       <anchor synch=T2>but I never inhaled the smoke</u>
  <u who=BOB>
       <anchor synch=T1>You used to smoke<anchor synch=T2>
  </u>
</body></text>
]]>
</eg></p>

<p>As above, since the whole of Bob's utterance is to be aligned, the
<att>start</att> and <att>end</att> attributes may be used as an
alternative to the second pair of <gi>anchor</gi> elements:

<eg>
<![ CDATA [
<!-- ... -->
<u who=BOB start=T1 end=T2>You used to smoke</u>
]]>
</eg></p>

<p>An alternative approach is to mark the synchronization by pointing
from the <gi>timeLine</gi> to the text:

<eg>
<![ CDATA[
<text><body>
  <timeLine origin=T1>
     <when id=T1 synch='N1 U2'>
     <when id=T2 synch='N2 U2'>
  </timeLine>
  <!-- .... -->
  <u who=TOM>I used to smoke
       <anchor ID=N1> a lot more than this
       <anchor ID=N2>but I never inhaled the smoke</u>
  <u id=U2 who=BOB>You used to smoke</u>
</body></text>
]]>
</eg>

To avoid deciding whether to point from the timeline to the text or vice
versa, a <gi>linkGrp</gi> may be used:

<eg>
<![ CDATA[
<text><body>
  <timeLine origin=T1>
     <when id=T1>
     <when id=T2>
  </timeLine>
  <!-- ... -->
  <u who=TOM>I used to smoke
       <anchor ID=N1> a lot more than this
       <anchor ID=N2>but I never inhaled the smoke</u>
  <u id=U2 who=BOB>You used to smoke</u>
  !--- ... -->
  <linkGrp type=synchronize>
     <link targets='T1 N1 U2'>
     <link targets='T2 N2 U2'>
   </linkGrp>
</body></text>
]]>
</eg></p>

<p>Note that in each case, although Bob's utterance follows Tom's
sequentially in the text, it is aligned temporally with its middle,
without any need to disrupt the normal syntax of the text.</p>

<p>As a final example, consider the following exchange, first as it
might be represented using a musical-score-like notation, in which
points of synchronization are represented by vertical alignment of the
text:

<eg rend="fig">
<![ CDATA[
A : This is |my  |turn
B :         |Balderdash
C :         |No, |it's mine

]]>
</eg>

All three speakers are simultaneous at the words <mentioned>my</mentioned>,
<mentioned>Balderdash</mentioned>, and <mentioned>No</mentioned>; speakers A and C are
simultaneous at the words <mentioned>turn</mentioned> and <mentioned>it's</mentioned>.
This could be encoded as follows, using pointers from the alignment map
into the text:

<eg>
<![ CDATA [
<text><body>
<timeLine origin=P1>
    <when id=P1 synch='A1 B1 C1'>
    <when id=P2 synch='A2 C2'>
</timeLine>
   <!-- ... -->
<u who=A>this is <anchor id=A1> my <anchor id=A2> turn</u>
<u who=B id=B1>balderdash</u>
<u who=C id=C1> no <anchor id=C2> it's mine</u>
</body></text>
]]>
</eg></p></div3>

<div3 id="TSreg"><head>Regularization of Word Forms</head>

<p>When speech is transcribed using ordinary orthographic notation, as
is customary, some compromise must be made between the sounds produced
and conventional orthography.  Particularly when dealing with informal,
dialectal or other varieties of language, the transcriber will
frequently have to decide whether a particular sound is to be treated as
a distinct vocabulary item or not.  For example, while in a given
project <mentioned>kinda</mentioned> may not be worth distinguishing as a
vocabulary item from <mentioned>kind of</mentioned>, <mentioned>isn't</mentioned> may
clearly be worth distinguishing from <mentioned>is not</mentioned>; for some
purposes, the regional variant <mentioned>isnae</mentioned> might also be worth
distinguishing in the same way.</p>

<p>One rule of thumb might be to allow such variation only where a
generally accepted orthographic form exists, for example, in published
dictionaries of the language register being encoded; this has the
disadvantage that such dictionaries may not exist.  Another is to
maintain a controlled (but extensible) set of normalized forms for all
such words; this has the advantage of enforcing some degree of
consistency among different transcribers.  Occasionally, as for example
when transcribing abbreviations or acronyms, it may be felt necessary to
depart from conventional spelling to distinguish between cases where the
abbreviation is spelled out letter by letter (e.g.  <mentioned>B B C</mentioned>
or <mentioned>V A T</mentioned>) and where it is pronounced as a single word
(<mentioned>VAT</mentioned> or <mentioned>RADA</mentioned>).  Similar considerations
might apply to pronunciation of foreign words
(e.g. <mentioned>Monsewer</mentioned> vs. <mentioned>Monsieur</mentioned>).</p>

<p>In general, use of punctuation, capitalization, etc., in spoken
transcripts should be carefully controlled.  It is important to
distinguish the transcriber's intuition as to what the punctuation
should be from the marking of prosodic features such as pausing,
intonation, etc.</p>

<p>Whatever practice is adopted, it is essential that it be clearly and
fully documented in the editorial declarations section of the header.
It may also be found helpful to include normalized forms of
non-conventional spellings within the text, using the elements for
simple editorial changes described in section <ptr target="COed"> (see
further section <ptr target="TStpsm">).</p></div3>

<div3 id="TStppr"><head>Prosody</head>

<p>In the absence of conventional punctuation, the marking of prosodic
features assumes paramount importance, since these structure and
organize the spoken message.  Indeed, such prosodic features as points
of primary or secondary stress may be represented by specialized
punctuation marks.  Pauses have already been dealt with in section
<ptr target="TSbapa">; while tone units (or intonational phrases) can be
indicated by the segmentation tag discussed in section <ptr
target="TSsase">.  The shift tag discussed in section <ptr
target="TSsash">
may also be used to encode some prosodic features, for example where all
that is required is the ability to record shifts in voice quality.</p>

<p>For more detailed work, involving a detailed phonological transcript
including representation of stress and pitch patterns, it is probably
best to maintain the prosodic description in parallel with the
conventional written transcript, rather than attempt to embed detailed
prosodic information within it.  The two parallel streams may be aligned
with each other and with other streams, for example an acoustic
encoding, using the general alignment mechanisms discussed in section
<ptr target="TSsash">.</p>

<p>Where only a small number of phonetic or phonemic aspects are
included in a transcript, it may be convenient to provide a simple set
of entity declarations for the particular set of features marked.  The
entity references in the text may then be redefined to produce simple
punctuation marks (as in the following example), or as references to
bundles of phonological features, in the same way as is proposed for
part of speech tags (see section <ptr target="AIla">).</p>

<p>In the following example, a small set of prosodic features are
recorded throughout the transcript using a user-defined entity set such
as the following:

<eg>
<![ CDATA [
<!ENTITY lf ".">    <!-- low fall intonation -->
<!ENTITY fr ",">    <!-- fall rise intonation -->
<!ENTITY lr "?">    <!-- low rise intonation -->
<!ENTITY rf "!">    <!-- rise fall intonation -->
<!ENTITY trunc "-"> <!-- truncated syllable -->
<!ENTITY long ":">  <!-- lengthened syllable -->
]]>
</eg>

This set of entity definitions may be included directly within the
document type declaration subset for the file, or more conveniently
along with any other extensions or modifications within the user
extensions file defined by the entity <ident type="pe">TEI.extensions.ent</ident>, as discussed in section <ptr
target="STin">.  For convenience of reading on the screen, these entity
declarations will map the mnemonic entity names used in the text below
to a conventional punctuation mark.

<eg>
<![ CDATA [
<text><body>
<div type=exchange n="Lod E-03">
<note>C is with a friend</note>
<u who=Cwn>
   <unclear>Excuse me&lf;</unclear><pause>
   You dont have some aesthetic&trunc;
   <pause><unclear>specially on early</unclear>
   aesthetics terminology &lr;</u>
<u who=AJ>No&lf; <pause>No&lf;
   <gap extent='2'> I'm afraid&lf;</u>
<u who=Cwn trans=latching>No&lr;
    <unclear>Well</unclear> thanks&lr; <pause>
    Oh&trunc; <unclear>you couldnt&trunc can we</unclear>
    kind of&long; <pause>I mean ask you to order
    it for us&long;&fr;</u>
<u who=AJ trans=latching>Yes&fr;
   if you know the title&lf; Yeah&lf;</u>
<u who=Cwn>
   <gap extent='3'>
   <gap extent='4'></u>
<u who=AJ>Yes thats fine.
    <unclear>just as soon as it comes in we'll send you
    a postcard&lf</unclear></u>
</div></body></text>
]]>
</eg>

<!-- Recoded from Gavioli and Mansfield: The PIXI Corpora     -->
<!-- (Bologna, 1990, CLUEB), p74                              --></p>

<p>This example, which is taken from a corpus of bookshop service
encounters<note><bibl><author>Laura Gavioli and Gillian
Mansfield</author>, <title>The Pixi Corpora</title> (Bologna:
Cooperativa Libraria Universitaria Editrice, 1990), p. 74.
</bibl></note>
also demonstrates the use of the <gi>unclear</gi> and <gi>gap</gi>
elements discussed in section <ptr target="COed">.  Where words are so
unclear that only their extent can be recorded, the empty <gi>gap</gi>
element may be used; where the encoder can identify the words but wishes
to record a degree of uncertainty about their accuracy, the
<gi>unclear</gi> element may be used.  More flexible and detailed
methods of indicating uncertainty are discussed in chapter <ptr
target="CE">.</p>

<p>Where a transcript includes many phonetic or phonemic aspects, it
will generally be convenient to use a specialized writing system, as
defined in chapters <ptr target="CH"> and <ptr target="WD">.  For
representation of phonemic information, the use of the International
Phonetic Alphabet is recommended.</p></div3>

<div3 id="TStpsm"><head>Speech Management</head>

<p>Phenomena of <term>speech management</term> include disfluencies such
as filled and unfilled pauses, interrupted or repeated words,
corrections, and reformulations as well as interactional devices asking
for or providing feedback.  Depending on the importance attached to such
features, transcribers may choose to adopt conventionalized
representations for them (as discussed in section <ptr target="TSreg">
above), or to transcribe them using IPA or some other transcription
system.  To simplify analysis of the lexical features of a speech
transcript, it may be felt useful to <socalled>tidy away</socalled> many
of these disfluencies.  Where this policy has been adopted, these
Guidelines recommend the use of the tags for simple editorial
intervention discussed in section <ptr target="COed">, to make explicit
the extent of regularization or normalization performed by the
transcriber.</p>

<p>For example, false starts, repetition, and truncated words might all
be included within a transcript, but marked as editorially deleted, in
the following way:

<eg>
<![ CDATA [
<del type=truncation>s</del>see
<del type=repetition>you you</del>you know
<del type=falseStart>it's</del>he's crazy
]]>
</eg></p>

<p>As previously noted, the <gi>gap</gi> element may be used to mark
points within a transcript where words have been omitted, for example
because they are inaudible:

<eg>
<![ CDATA [

<gap extent='approx 10 sylls'
      reason='passing truck'>

]]>
</eg></p>

<p>The <gi>unclear</gi> element may be used to mark words which have
been included although the transcriber is unsure of their accuracy:

<eg>
<![ CDATA [

and then <unclear reason='passing truck'>marbled queen</unclear>

]]>
</eg></p>

<p>Where a transcriber is believed to have incorrectly identified a
word, the elements <gi>corr</gi> or <gi>sic</gi> may be used to indicate
both the original and a corrected form of it:

<eg>
<![ CDATA [
<sic corr="SCSI" resp=DD>skuzzy</sic>
<corr sic="skuzzy" resp=AGB>SCSI</corr>
]]>
</eg>

As discussed in section <ptr target="COedcor">, the first of these would
be appropriate where faithfulness to the transcribers' intuition is
paramount, and the second where the editorial interpretation is felt
more significant.  In either case, the user of the text can perceive the
basis of the choice being offered.

<!-- delete following scandinavian para? --></p></div3>

<div3 id="TStpac"><head>Analytic Coding</head>

<p>The recommendations made here only concern the establishment of a
basic text.  Where a more sophisticated analysis is needed, more
sophisticated methods of markup will also be appropriate, for example,
using concurrent markup streams to indicate multiple segmentation of the
stream of discourse, or complex alignment of several segments within it.
Where additional annotations (sometimes called
<socalled>codes</socalled> or <socalled>tags</socalled>) are used to
represent such features as linguistic word class (noun, verb, etc.),
type of speech act (imperative, concessive, etc.), or information status
(theme/rheme, given/new, active/semi-active/new), etc., a selection from
the general purpose analytic tools discussed in chapters <ptr
target="SA">, <ptr target="AI">, and <ptr target="FS">, may be used to
advantage.
</p>
<!-- As yet, however, we have been unable to find any         -->
<!-- consensus in the field as to what kinds of units should  -->
<!-- be identified at this level, and cannot therefore make   -->
<!-- more specific recommendations.  It is hoped however      -->
<!-- that the basic building blocks offered here will be      -->
<!-- serviceable in the expression of such a consensus when   -->
<!-- it is achieved.                                          -->

</div3>
</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:
-->

</div1>
<!-- 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:
-->
             <!-- 11 Spoken Texts -->
<!-- &p2.lm;             Letters and Memoranda -->

