<?tei:SOF p2ccah.odd ?>
<!-- $Id: p2ccah.odd,v 1.9 1998/01/31 19:50:52 tei Exp $ -->
<!--*
    * $Log: p2ccah.odd,v $
    * Revision 1.9  1998/01/31 19:50:52  tei
    * Change system 'tei2.dtd' to public identifier
    * fix log keyword (if not already fixed)
    * normalize the sgml
    *
    * Revision 1.8  1998/01/29 17:05:51  tei
    * lowercase DTD filename
    * normalize SGML
    *
    * Revision 1.7  1998/01/28 11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.6  1994/04/01  16:16:14  msmcq
    * cosmetic, and add RCS id
    * -->
<!-- Revisions:                                               -->
<!-- 98-01-29 : MSM : lowercase DTD file name, normalize      -->
<!-- 17 jan 98 : LB : fix egs                                 -->
<!--  4 jan 98 : LB : TEI.corpus shd be  teiCorpus            -->
<!--  3 jan 98 : LB : fix broken xrefs to partic/particgrp    -->
<!--                  (now person/persgrp) -->
<!-- 30 jan 94 : LB : define persName here pro tem; rename participant -->
<!-- 93-06-05 : MSM : supply xref to DRsp (was DRx)           -->
<!-- 93-06-03 : MSM : replace place with placeName            -->
<!-- 93-06-03 : MSM : replace person with persname            -->
<!-- 93-03-11 : MSM : delete dup partdesc, setdesc tagdecls   -->
<!-- 93-03-11 : MSM : remove duplicate textdesc decl          -->
<!-- 93-03-11 : MSM : last minute changes as per LB           -->
<!-- 93-03-10 : MSM : reset dtdFrags as contins               -->
<!-- 93-03-10 : MSM : change ids to begin CCah not AH         -->
<!-- 93-03-10 : MSM : revise for publication:                 -->
<!--                  recast some transitions, overviews      -->
<!--                  give full Doctype decl, using tei.corp  -->
<!--                  add note on classifcn of lit texts      -->
<!--                  provide explicit end-tags in most exx   -->
<!--                  add subj/obj distinction for relations  -->
<!--                  add birth to DTD                        -->
<!--                  add DATE to settingDesc, retag example  -->
<!-- 93-03-08 : MSM : suppress ABBREV around 'DTD'            -->
<!-- 93-03-08 : MSM : supply end-tags for HEAD elements       -->
<!-- Date: Sat, 06 Mar 1993 22:00:31 +0000                    -->
<!-- From: Lou Burnard < lou@vax.ox.ac.uk >                   -->
<!-- To: U35395@UICVM.UIC.EDU                                 -->
<!-- CC: lou@vax.ox.ac.uk                                     -->
<!-- Subject: CCah.odd (4 of 10)                              -->
<!--                                                          -->
<div2 id="CCAH"><head>Contextual Information</head>
 
<p>Contextual information is of particular importance for collections
or corpora composed of samples from a variety of different kinds of
text. Examples of such contextual information include:  the age, sex
and geographical origins of participants in a language interaction, or
their socio-economic status; the cost and publication data of a
newspaper; the topic, register or factuality of an extract from a
textbook. Such information may be of the first importance, whether as
an organizing principle in creating a corpus (for example, to ensure
that the range of values in such a parameter is evenly represented
throughout the corpus, or represented proportionately to the population
being sampled), or as a selection criterion in analysing the corpus
(for example, to investigate the language usage of some particular
vector of social characteristics).</p>
 
<p>Such contextual information is potentially of equal importance for
unitary texts, and these Guidelines accordingly make no particular
distinction between the kinds of information which should be gathered
for unitary and for composite texts.  In either case, the information
should be recorded in the appropriate section of a TEI Header, as
described in chapter <xref target="HD">.  In the case of language corpora,
such information may be gathered together in the overall corpus header,
or split across all the component texts of a corpus, in their individual
headers, or divided between the two.  The association between an
individual corpus text and the contextual information applicable to it
may be made in a number of ways, as further discussed in section <xref
target="CCAS"> below.</p>
 
<p>Chapter <xref target="HD">, which should be read in conjunction with
the present section, describes in full the range of elements available
for the encoding of information relating to the electronic file itself,
for example its bibliographic description and those of the source or
sources from which it was derived (see section <xref target="HD2">);
information about the encoding practices followed with the corpus, for
example its design principles, editorial practices, reference system
etc.  (see section <xref target="HD5">); more detailed descriptive
information about the creation and content of the corpus, such as the
languages used within it and any descriptive classification system used
(see section <xref target="HD4">); and version information documenting any
changes made in the electronic text (see section <xref target="HD6">).</p>
 
<p>In addition to the elements defined by chapter <xref target="HD">,
several other elements can be used in the TEI header if the additional
tag set defined by this chapter is invoked.  These additional tags make
it possible to characterize the social or other situation within which a
language interaction takes place or is experienced, the physical setting
of a language interaction, and the participants in it.  Though this
information may be relevant to, and provided for, unitary texts as well
as for collections or corpora, it is more often recorded for the
components of systematically developed corpora than for isolated texts,
and thus the additional tag set is referred to as being <q>for language
corpora</q>.  Included in this tag set are the following elements:
 
<tagList>
<tagDesc tagDoc="TEXTDESC">
<tagDesc tagDoc="PARTDESC">
<tagDesc tagDoc="SETTDESC">
</tagList>
 
These elements form an optional extension to the <gi>profileDesc</gi>,
defined in section <xref target="HD4"> and are further described in the
remainder of this section. They are formally defined as follows:
 
<dtdFrag id="DCCHDR" n="Header extensions for Corpus Texts"
file="teicorp2">
<tagDecl tagDoc="TEXTDESC">
<tagDecl tagDoc="PARTDESC">
<tagDecl tagDoc="SETTDESC">
</dtdFrag>
 
<!-- any other header extensions here -->
<!-- err, more stuff to go in here --></p>
 
<p>The additional tag set for language corpora will be invoked, thus
enabling the use of these elements, if a parameter entity called
<ident type="pe">TEI.corpus</ident> is declared with the value <code
type="kw">INCLUDE</code>, somewhere within the DTD subset.  If the
document is structured as a TEI corpus (that is, using the
<gi>teiCorpus.2</gi> element), its document type declaration will
resemble this:
 
<eg>
<![ CDATA [
 <!DOCTYPE teiCorpus.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
   "tei2.dtd" [
     <!ENTITY % TEI.corpus 'INCLUDE' >
 ]>
]]>
</eg>

<!-- 27 jan 93: LB extracted from old p2224.odd and revised  --></p>
 
<div3 id="CCAHTD"><head>The Text Description</head>
 
<p>The <gi>textDesc</gi> element provides a full description of the
situation within which a text was produced or experienced, and thus
characterizes it in a way relatively independent of any <foreign>a
priori</foreign> theory of text-types.  It is provided as an alternative
or a supplement to the common use of descriptive taxonomies used to
categorize texts, which is fully described in section <xref
target="HD43">, and section <xref target="HD55">.  The description is
organized as a set of values and optional prose descriptions for the
following eight <term>situational parameters</term>, each represented by
one of the following eight elements:
 
<tagList>
<tagDesc tagDoc="CHANNEL" atts="mode">
<tagDesc tagDoc="CONSTITN" atts="type">
<tagDesc tagDoc="DERIVATN" atts="type">
<tagDesc tagDoc="DOMAIN" atts="type">
<tagDesc tagDoc="FACTUAL" atts="type">
<tagDesc tagDoc="INTERACT" atts="type active passive">
<tagDesc tagDoc="PREPNESS" atts="type">
<tagDesc tagDoc="PURPOSE" atts="type degree">
</tagList></p>
 
<p>A TEI-conformant text description contains each of the above
elements, supplied in the order specified. Except for the
<gi>purpose</gi> element, which may be repeated to indicate multiple
purposes, no element may appear more than once within a single text
description.  Each element may be empty, or may contain a brief
qualification or more detailed description of the value expressed by
its attributes.  It should be noted that some texts, in particular
literary ones, may resist unambiguous classification in some of these
dimensions; in such cases, the situational parameter in question
should be given the content <q>not applicable</q> or an equivalent
phrase.
 
<!-- Added last sentence, to soothe the literati.  Delete if  -->
<!-- it will only inflame them.  -MSM                         --></p>
 
<p>Texts may be described along many dimensions, according to many
different taxonomies.  No generally accepted consensus as to how such
taxonomies should be defined has yet emerged, despite the best efforts
of many corpus linguists, text linguists, sociolinguists,
rhetoricians, and literary theorists over the years.  Rather than
attempting the task of proposing a single taxonomy of
<term>text-types</term> (or the equally impossible one of enumerating
all those which have been proposed previously), the closed set of
<term>situational parameters</term> described above can be used in
combination to supply useful distinguishing descriptive features of
individual texts, without insisting on a system of discrete high-level
text-types.  Such text-types may however be used in combination with
the parameters proposed here, with the advantage that the internal
structure of each such text-type can be specified in terms of the
parameters proposed.  This approach has the following analytical
advantages:<note>Schemes similar to that proposed here were developed
in the 1960s and 1970s by researchers such as Hymes, Halliday, and
Crystal and Davy, but have rarely been implemented; one notable
exception being the pioneering work on the Helsinki Diachronic Corpus
of English, on which see <citation> <author>M. Kyt&ouml; and
M. Rissanen,</author> <title.p>The Helsinki Corpus of English
Texts,</title.p> in <title>Corpus Linguistics: hard and soft</title>,
ed.  <editor>M. Kyt&ouml;, O. Ihalainen, and M. Rissanen</editor>
(Amsterdam: Rodopi, 1988).  </citation> </note>
 
<list type="bullets">
<item> it enables a relatively continuous characterization of texts (in
contrast to discrete categories based on type or topic)</item>
<item>it enables meaningful comparisons across corpora</item>
<item>it allows analysts to build and compare their own text-types
based on the particular parameters of interest to them</item>
<item>it is equally applicable to spoken and written texts</item>
</list></p>
 
<p>Two alternative approaches to the use of these parameters are
supported by these Guidelines.  One is to use pre-existing taxonomies
such as those used in subject classification or other types of text
categorization.
 
<!-- NOT descriptive cataloguing -msm -->
 
Such taxonomies may also be appropriate for the description of the
topics addressed by particular texts.  Elements for this purpose are
described in section <xref target="HD43">, and elements for defining or
declaring such classification schemes in section <xref target="HD55">.  A
second approach is to develop an application-specific set of
<term>feature structures</term> and an associated <term>feature system
declaration,</term> as described in chapters <xref target="FS"> and
<xref target="FD">.
 
<!-- However, in particular where a pre-existing descriptive  -->
<!-- typology of this kind was used as the organizing         -->
<!-- principle of a corpus or collection, these Guidelines    -->
<!-- recommend that its components be additionally            -->
<!-- re-expressed in terms of the parameters listed here.     --></p>
 
<p>Where the organizing principles of a corpus or collection so permit,
it may be convenient to regard a particular set of values for the
situational parameters listed in this section as forming a
<term>text-type</term> in its own right; this may also be useful where
the same set of values applies to several texts within a corpus.  In
such a case, the set of text-types so defined should be regarded as a
<term>taxonomy</term>.  The mechanisms described in section <xref
target="HD55"> may be used to define hierarchic taxonomies of such
text-types, provided that the <gi>catDesc</gi> component of the
<gi>category</gi> element contains a <gi>textDesc</gi> element rather
than a prose description.  Particular texts may then be associated with
such definitions using the mechanisms described in sections <xref
target="HD43">.
 
<!-- These subcomponents provide information about the        -->
<!-- context within which the text is produced or situated    -->
<!-- which, taken together, are felt to characterize it in    -->
<!-- analytically helpfulway.  Information about the          -->
<!-- participants in a language interaction and their         -->
<!-- physical or temporal setting are provided by two other   -->
<!-- components of the < gi >profile.desc< /gi > element      -->
<!-- (see sections < xref target=AHPA > and < xref            -->
<!-- target=AHSE > below).                                    --></p>
 
<p>Using these situational parameters, an informal domestic
conversation might be characterized as follows:
 
<eg><![ CDATA[
<textDesc id=T1 n='Informal domestic conversation'>
  <channel mode=s>informal face-to-face conversation</channel>
  <constitution type=single>each text represents a continuously
        recorded interaction among the specified participants
        </constitution>
  <derivation type=original>
  <domain type=domestic>plans for coming week, local affairs</domain>
  <factuality type=mixed>mostly factual, some jokes</factuality>
  <interaction type=complete active=plural passive=many>
  <preparedness type='spontaneous'>
  <purpose type=entertain degree=high>
  <purpose type=inform degree=medium>
 </textDesc>
]]>
</eg>
 
<!-- Content of sit parms added. Please check. -MSM --></p>
 
<p>The following example demonstrates how the same situational
parameters might be used to characterize a novel:
 
<eg><![ CDATA[
   <textDesc n='novel'>
     <channel mode=w>print; part issues</channel>
     <constitution type=single>
     <derivation type=original>
     <domain type=art>
     <factuality type=fiction>
     <interaction type=none>
     <preparedness type=prepared>
     <purpose type=entertain degree=high>
     <purpose type=inform degree=medium>
  </textDesc>
]]>
</eg>
 
 
<!-- need more examples -->
 
The formal declarations for these elements are given below:
<dtdFrag id="DCCAHTD" n="Text description" contin="DCCHDR">
<tagDecl tagDoc="CHANNEL">
<tagDecl tagDoc="CONSTITN">
<tagDecl tagDoc="DERIVATN">
<tagDecl tagDoc="DOMAIN">
<tagDecl tagDoc="FACTUAL">
<tagDecl tagDoc="INTERACT">
<tagDecl tagDoc="PREPNESS">
<tagDecl tagDoc="PURPOSE">
</dtdFrag>
 
<!-- Not sure if this para is necessary or advisable. -LB     -->
<!-- < p >The content model for the < gi >textDesc< /gi >     -->
<!-- element is defined by the parameter entity %tdModel.     -->
<!-- If so desired, the encoder may change the set of         -->
<!-- parameters used to define < gi >textDesc< /gi > by       -->
<!-- altering the definition of this entity, as further       -->
<!-- described in chapter < xref target=MD >.                 -->
 
<!-- some change along these lines is desirable for P4 (LB) --></p></div3>
 
<div3 id="CCAHPA"><head>The Participants Description</head>
 
<p>The <gi>particDesc</gi> element in the <gi>profileDesc</gi> element
provides additional information about the participants in a spoken text
or, where this is judged appropriate, the persons named or depicted in a
written text.  Individual speakers or groups of speakers may be named or
identified by a code which can then be used elsewhere within the encoded
text, for example as the value of a <att>who</att> attribute.
Demographic and descriptive information may be supplied about their
individual characteristics and the relationships between them.</p>
 
<p>It should be noted that although the terms <term>speaker</term> or
<term>participant</term> are used throughout this section, it is
intended that the same mechanisms may be used to characterize fictional
person&aelig or <soCalled>voices</soCalled> within a written text, except
where otherwise stated.  For the purposes of analysis of language usage,
the information specified here should be equally applicable to written
and spoken texts.</p>
 
<p>The element <gi>particDesc</gi> contains one or more
<gi>person</gi> or <gi>personGrp</gi> elements, followed by an
optional <gi>particLinks</gi> element, as described below:
 
<tagList>
<tagDesc tagDoc="PERSON" atts="role sex age">
<tagDesc tagDoc="PERSGRP" atts="role sex age size">
<tagDesc tagDoc="PARTIREL">
</tagList>
 
<!-- I have now removed members attrib :  It unnecessarily    -->
<!-- complicates notion of partic.group Would be better done  -->
<!-- by nesting participants if we really wanted to do it.    -->
<!-- Best define partic.grp as simply a partic which happens  -->
<!-- to have several legs (LB)                                --></p>
 
<p>Both <gi>person</gi> and <gi>personGrp</gi> elements have the same
substructure.  This may be a prose description, or, more formally, a
series of specialized subelements providing more specific details.
Such details will vary enormously for different kinds of analysis; the
set of demographic characteristics presented here as sub-elements
should therefore be regarded as providing only an indication of the
kinds of descriptive information which have been found to be generally
useful, for example in socio-linguistics.  Users of these Guidelines
are free to extend or modify this set of demographic characteristics,
by redefining the parameter entity <term>m.demographics</term>,
associated with the class <term>demographics</term>, as further
described in chapter <xref target="MD">.  Where well-known
classification schemes exist, e.g. for socio-economic class or
occupation, these should be used and may be documented in the same way
as for text classification (see section <xref target="HD55">)
 
<!-- Though I havent the faintest idea how.                   -->
<!-- Should we allow for a catRef within partic/partic.grp? (LB) -->
<!-- No, just use SCHEME and CODE attributes on OCCUPATION    -->
<!-- and SOCECSTATUS.  -MSM                                   --></p>
 
<p>The following elements are the default members of the class
<ident type="class">demographics</ident>:
 
<tagList>
<!-- removed  name, persname, placename now that ND is back -->
<tagDesc tagDoc="BIRTH" atts="date">
<tagDesc tagDoc="FRSTLANG">
<tagDesc tagDoc="LANGKNOW">
<tagDesc tagDoc="RESIDENC">
<tagDesc tagDoc="EDUCN">
<tagDesc tagDoc="AFFILIAT">
<tagDesc tagDoc="OCCUPAT" atts="scheme code">
<tagDesc tagDoc="SOCECSTA" atts="scheme code">
</tagList></p>
 
<p>For example, an individual might be described informally by the
following <gi>person</gi> element:
 
<eg><![ CDATA[
<person id=P1 sex=F age='mid'>
  <p>Female informant, well-educated, born in Shropshire
   UK, 12 Jan 1950, of unknown occupation.
   Speaks French fluently. Socio-Economic status B2
   in the PEP classification scheme.
</person>
]]>
</eg>
 
Provided that the <q>PEP classification scheme</q> has been defined
elsewhere in the heading (as a <gi>taxonomy</gi> element within the
<gi>textClass</gi> element; see <xref target="HD55">), the same individual
might more formally be described as follows:
 
<eg><![ CDATA[
<person id=P1 sex=F age='mid'>
  <birth date='1950-01-12'>
     <date>12 Jan 1950</date>
     <name type=place>Shropshire, UK</name>
  </birth>
  <firstLang>English</firstLang>
  <langKnown>French</langKnown>
  <residence>Long term resident of Hull</residence>
  <education>University postgraduate</education>
  <occupation>Unknown</occupation>
  <socecstatus scheme=PEP code=B2>
</person>
]]>
</eg></p>
 
<p>Dates and names of persons or places, if included in the prose
description, may be encoded using either the general purpose
<gi>date</gi>, <gi>name</gi> or <gi>rs</gi> elements discussed in
section <xref target="CONA">, or the more specialised and detailed
elements provided by chapter <xref target="ND">. In the latter case, the
additional tag set for names and dates must be enabled together with
that for language corpora.</p>
 
<p>An identified character in a drama or a novel might be defined using
a subset of the same tags as follows:<note>It is particularly useful to
define participants in a dramatic text in this way, since it enables the
<att>who</att> attribute to be used to link <gi>sp</gi> elements to
definitions for their speakers; see further section <xref
target="DRSP">.
</note>
 
<eg><![ CDATA[
  <person id=EM01 sex=F age=young>
  <p><name>Emma Woodhouse</name>
  </person>
]]>
</eg></p>
 
<p>As noted above, the <gi>particLinks</gi> element is used to document
personal or social relationships between individual participants, where
this is felt to be of importance in the analysis.  This may be done
either as an informal prose description, or more formally using the
special purpose <gi>relation</gi> element, as described below:
 
<tagList>
<tagDesc tagDoc="RELATION" atts="type desc active passive mutual">
</tagList></p>
 
<p>A <term>relationship</term>, as defined here, may be any kind of
describable link between specified participants, for example a social
relationship (such as employer/employee), a personal relationship
(such as sibling, spouse, etc.) or something less precise such as
<q>possessing shared knowledge</q>.  A relationship may be
<term>mutual</term>, in that all the participants engage in it on an
equal footing (for example the <q>sibling</q> relationship); or it may
not be if participants are not identical with respect to their role in
the relationship (for example, the <q>employer</q> relationship).  For
non-mutual relationships, only two kinds of role are currently
supported; they are named <term>active</term> and
<term>passive</term>.  These names are chosen to reflect the fact that
non-mutual relations are <term>directed</term>, in the sense that they
are most readily described by a transitive verb, or a verb phrase of
the form <cited>is X of</cited> or <cited>is X to</cited>.  The
subject of the verb is classed as <term>active</term>; the direct
object of the verb, or the object of the concluding preposition, as
<term>passive</term>.  Thus parents are <q>active</q> and children
<q>passive</q> in the relationship <q>parent</q> (interpreted as
<cited>is parent of</cited>); the employer is <q>active</q>, the
employee <q>passive</q>, in the relationship <cited>employs</cited>.
These relationships can be inverted: parents are <q>passive</q> and
children <q>active</q> in the relationship <cited>is child of</cited>;
similarly <q>works for</q> inverts the active and passive roles of
<q>employs</q>.
 
<!-- ... in the sense that one group of participants is seen  -->
<!-- as active in the relationship, and another as passive,   -->
<!-- for example, parents are seen as < q >active< /q > in    -->
<!-- the < q >parent< /q > relationship, and children as < q  -->
<!-- >passive< /q >.                                          -->
 
<!--   Is this enough? Is it too much? I considered defining -->
<!--   a role relationship within relation but couldnt face it --></p>
 
<p>For example:
<eg><![ CDATA[
<particLinks>
  <relation desc='parent' active='P1 P2'
         passive='P3 P4' mutual=N>
  <relation desc='spouse' active='P1 P2'>
  <relation type='social' desc='employer'
          active=P1 passive='P3 P5 P6 P7' mutual=N>
</particLinks>
]]></eg>
 
<!-- I hate these names too, especially 'relation' but I      -->
<!-- cant think of any better ones.  'socrel' 'link.social'   -->
<!-- ???  (LB)                                                -->
 
This example defines the following three relationships among
participants P1 through P7:
 
<list type="simple">
<item>P1 and P2 are parents of P3 and P4.</item>
<item>P1 and P2 are linked in a mutual relationship called <q>spouse</q>
--- i.e.  P2 is the spouse of P1, and P1 is the spouse of P2.</item>
<item>P1 has the social relationship <q>employer</q> with respect to P3,
P5, P6, and P7.</item>
</list></p>
 
<p>The elements discussed in this section are formally defined as
follows:
<!-- add persname since person is not available in the core   -->
<!-- and name is not a member of demogs                       -->
<!-- removed persname: if required, can nest name within person -->
<dtdFrag id="DCCAHPA" n="Participants description" contin="DCCHDR">
<claDecl classDoc="DEMOG" type="model">
<tagDecl tagDoc="PERSON">
<tagDecl tagDoc="PERSGRP">
<tagDecl tagDoc="BIRTH">
<tagDecl tagDoc="FRSTLANG">
<tagDecl tagDoc="LANGKNOW">
<tagDecl tagDoc="RESIDENC">
<tagDecl tagDoc="EDUCN">
<tagDecl tagDoc="AFFILIAT">
<tagDecl tagDoc="OCCUPAT">
<tagDecl tagDoc="SOCECSTA">
<tagDecl tagDoc="PARTIREL">
<tagDecl tagDoc="RELATION">
</dtdFrag>
 
<!-- shouldnt the cladecl go into teiclas2 somewhere? --></p></div3>
 
<div3 id="CCAHSE"><head>The Setting Description</head>
 
<p>The <gi>settingDesc</gi> element is used to describe the setting or
settings in which language interaction takes place.  It may contain a
prose description, analogous to a stage description at the start of a
play, stating in broad terms the locale, or a more detailed description
of a series of such settings.  Individual settings may be associated
with particular participants by means of the optional <att>who</att>
attribute if, for example, participants are in different places.  This
attribute identifies one or more individual participants or participant
groups, as discussed earlier in section <xref target="CCAHPA">.  If this
attribute is not specified, the setting details provided are assumed to
apply to all participants represented in the language interaction.
<note place="foot">The present proposals do not support the encoding of
different settings for the same participant.  This is a subject for
further work.</note></p>
 
<p>Each distinct setting is described by means of a <gi>setting</gi>
element, which contains either a prose description or a combination of
the other elements listed below:
 
<tagList>
<tagDesc tagDoc="SETTING" atts="who">
<tagDesc tagDoc="NAME" atts="type">
<tagDesc tagDoc="DATE" atts="value">
<tagDesc tagDoc="TIME" atts="value">
<tagDesc tagDoc="LOCALE">
<tagDesc tagDoc="ACTIVITY">
</tagList></p>
 
<p>The following example demonstrates the kind of background information
often required to support transcriptions of language interactions, first
encoded as a simple prose narrative:
 
<eg><![ CDATA[
 <settingDesc>
 <p>The time is early spring, 1989.  P1 and P2 are
  playing on the rug of a suburban home in Bedford.
  P3 is doing the washing up at the sink.  P4 (a
  radio announcer) is in a broadcasting studio in London.
 </settingDesc>
]]>
</eg>
 
The same information might be represented more formally in the following
way:
 
<eg><![ CDATA[
 <settingDesc>
 <setting who="P1 P2">
  <name type=city>Bedford</>
  <name type=region>UK: South East</>
  <date value=1989>early spring, 1989</>
  <locale>rug of a suburban home</>
  <activity>playing</>
 </setting>
 <setting who=P3>
  <name type=city>Bedford</>
  <name type=region>UK: South East</>
  <date value=1989>early spring, 1989</>
  <locale>at the sink</>
  <activity>washing-up</>
 </setting>
 <setting who=P4>
  <name type=place>London, UK</>
  <time>unknown</>
  <locale>broadcasting studio</>
  <activity>radio performance</>
 </setting>
</settingDesc>
]]></eg></p>
 
<p>For more detailed encoding of names of persons and places, the
additional tag set described in chapter <xref target="ND"> may
additionally be used; if used, however, these elements may appear only
within a <gi>p</gi> element. The above examples assume that only the
general purpose <gi>name</gi> element supplied in the core tag set is
available.
 
<!-- to avoid repetition, should a who-less setting be        -->
<!-- assumed to specify defaults for all subelements in same  -->
<!-- settingDesc ?                                            -->
 
<!-- another, more literary, example needed                   -->
 
The elements discussed in this section have the following formal
definitions:
 
<dtdFrag id="DCCAHSE" n="Setting description" contin="DCCHDR">
<tagDecl tagDoc="SETTING">
<tagDecl tagDoc="LOCALE">
<tagDecl tagDoc="ACTIVITY">
</dtdFrag>
 
</p></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:
-->
<?tei:EOF p2ccah.odd ?>
