<!-- $Id: p2ccdef.odd,v 1.8 1998/02/01 17:55:08 tei Exp $ -->
<!--*
    * $Log: p2ccdef.odd,v $
    * Revision 1.8  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    *
    * Revision 1.6  1994/03/27  16:28:39  lou
    * semifinal check
    *
    * Revision 1.4  1994/03/01  15:26:36  lou
    * typos spotted by terry
    *
    * Revision 1.3  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * -->
<!-- draft new text for CC section Varieties of Composite Text -->
<!-- Revisions:                                               -->
<!-- 14 jan 98 : LB : fix egs -->
<!-- 4 jan 98: LB: TEI.corpus shd be  teiCorpus               -->
<!-- 26 mar: modified discussion of CB a bit -->
<!-- 9 jan : teiHeader, not TeiHeader -->
<!-- 93-03-11 : MSM : last minute changes as per LB           -->
<!-- 93-03-10 : MSM : correct xrefs                           -->
<!-- 1993-03-10 : MSM : redraft from LB's version             -->

<div2 id=CCdef><head>Varieties of Composite Text</head>

<p>Both unitary and composite texts may be encoded using these
Guidelines; composite texts, including corpora, will typically make use
of the following tags for their top-level organization.

<list type=gloss>
<label><gi>teiCorpus.2</gi></label>
<item>contains the whole of a TEI encoded corpus, comprising a

single corpus header and one or more TEI.2 elements, each 
containing
a single text header and a text.</item>
<label><gi>TEI.2</gi></label>
<item>contains a single TEI-conformant document, comprising a

TEI header and a text, either in isolation or as part of a

<gi>teiCorpus</gi> element.</item>
<label><gi>teiHeader</gi></label>
<item>supplies the descriptive and declarative information making 
up an
<q>electronic title page</q> prefixed to every

TEI-conformant text.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies the kind of document to which the header is 
attached.
Legal values are:
<list type=gloss>
<label><term>corpus</term></label>
<item>the header is attached to a corpus.</item>
<label><term>text</term></label>
<item>the header is attached to a single text.</item>
</list></item>
<label><att>status</att></label>
<item>indicates whether the header is new or has been 
substantially revised.
Sample values include:
<list type=gloss>
<label><term>new</term></label>
<item>the header is a new header.</item>
<label><term>update</term></label>
<item>the header is an update (has been revised).</item>
</list></item>
<label><att>creator</att></label>
<item>identifies the creator of the TEI Header.</item>
<label><att>date.created</att></label>
<item>indicates when the first version of the header was created.</item>
<label><att>date.updated</att></label>
<item>indicates when the current version of the header was 
created.</item>
</list>
</item>
<label><gi>text</gi></label>
<item>contains a single text of any kind, whether unitary or

composite, for example a poem or drama, a collection of 
essays, a novel,
a dictionary, or a corpus sample.</item>
<label><gi>group</gi></label>
<item>contains the body of a composite text, grouping together a

sequence of distinct texts (or groups of such texts) which 
are regarded
as a unit for some purpose, for example the 
collected works of an
author, a sequence of prose essays, 
etc.</item>
</list>


Full descriptions of these may be found in chapter <ptr target=ST> (for
<gi>teiCorpus.2</gi> and <gi>TEI.2</gi>), chapter <ptr target=HD> (for
<gi>teiHeader</gi>), and chapter <ptr target=DS> (for <gi>text</gi> and
<gi>group</gi>); this section discusses their application to composite
texts in particular.

<p>In these Guidelines, the word <term>text</term> refers to any stretch
of discourse, whether complete or incomplete, unitary or composite,
which the encoder chooses (perhaps merely for purposes of analytic
convenience) to regard as a unit.  The term <term>composite text</term>
refers to texts within which other texts appear; the following common
cases may be distinguished:

<list type=bullets>
<item>language corpora
<item>collections or anthologies
<item>poem cycles and epistolary works (novels or essays written
in the form of collections or series of letters)
<item>otherwise unitary texts, within which one or more subordinate
texts are embedded
</list>

The tags listed above may be combined to encode each of these
varieties of composite text in different ways.

<p>In corpora, the component samples are clearly distinct texts, but the
systematic collection, standardized preparation, and common markup of
the corpus often make it useful to treat the entire corpus as a unit,
too.  Some corpora may become so well established as to be regarded as
texts in their own right; the Brown and LOB corpora are now close to
achieving this status.

<p>The <gi>teiCorpus.2</gi> element is intended for the encoding of
language corpora, though it may also be useful in encoding newspapers,
electronic anthologies, and other disparate collections of material.
The individual samples in the corpus are encoded as separate
<gi>TEI.2</gi> elements, and the entire corpus is enclosed in a
<gi>teiCorpus.2</gi> element.  Each sample has the usual structure for
a <gi>TEI.2</gi> document, comprising a <gi>teiHeader</gi> followed by a
<gi>text</gi> element.  The corpus, too, has a corpus-level
<gi>teiHeader</gi> element, in which the corpus as a whole, and encoding
practices common to multiple samples may be described.  The overall
structure of a TEI-conformant corpus is thus:

<eg rend=skel>
<![ CDATA [
 <teiCorpus.2>
    <teiHeader type=corpus> ...
    <!-- TEI header for corpus-level information -->
    </teiHeader>

    <TEI.2 id=T1>
         <teiHeader type=text> ... </teiHeader>
         <text> ... </text>
    </TEI.2>
    <TEI.2 id=T2>
         <teiHeader type=text> ... </teiHeader>
         <text> ... </text>
    </TEI.2>
    <!-- ... etc. -->
 </teiCorpus.2>
]]>
</eg>

<p>Header information which relates to the whole corpus rather than to
individual components of it should be factored out and included in the
<gi>teiHeader</gi> element prefixed to the whole.  This two-level
structure allows for contextual information to be specified at the
corpus level, at the individual text level, or at both.  Discussion of
the kinds of information which may thus be specified is provided below,
in section <ptr target=CCah>, as well as in chapter <ptr
target=HD>.  Information of this type should in general be specified
only once:  a variety of methods are provided for associating it with
individual components of a corpus, as further described in section <ptr
target=CCas>.

<p>In some cases, the design of a corpus is reflected in its internal
structure.  For example, a corpus of newspaper extracts might be
arranged to combine all stories of one type (reportage, editorial,
reviews, etc.) into some higher-level grouping, possibly with sub-groups
for date, region, etc.  The <gi>teiCorpus.2</gi> element provides no
direct support for reflecting such internal corpus structure in the
markup:  it treats the corpus as an undifferentiated series of
components, each tagged <gi>TEI.2</gi>.

<p>If it is essential to reflect a single permanent organization of a
corpus into sub- and sub-sub-corpora, then the corpus or the high-level
subcorpora may be encoded as composite texts, using the <gi>group</gi>
element described below and in section <ptr target=DSgrp>.  The
mechanisms for corpus characterization described in this chapter,
however, are designed to reduce the need to do this.  Useful groupings
of components may easily be expressed using the text classification and
identification elements described in section <ptr target=CCahtd>,
and those for associating declarations with corpus components described
in section <ptr target=CCas>.  These methods also allow several
different methods of text grouping to co-exist, each to be used as
needed at different times.  This helps minimize the danger of
cross-classification and mis-classification of samples, and helps
improve the flexibility with which parts of a corpus may be
characterized for different applications.

<p>Anthologies and collections are often treated as texts in their own
right, if only for historical reasons.  In conventional publishing, at
least, anthologies are published as units, with single editorial
responsibility and common front and back matter which may need to be
included in their electronic encodings.  The texts collected in the
anthology, of course, may also need to identifiable as distinct
individual objects for study.

<p>Poem cycles, epistolary novels, and epistolary essays differ from
anthologies in that they are often written as single works, by single
authors, for single occasions; nevertheless, it can be useful to treat
their constituent parts as individual texts, as well as the cycle
itself.  Structurally, therefore, they may be treated in the same way
as anthologies: in both cases, the body of the text is composed
largely of other texts.

<p>The <gi>group</gi> element is provided to simplify the encoding of
collections, anthologies, and cyclic works; as noted above, the
<gi>group</gi> element can also be used to record the potentially
complex internal structure of language corpora.  For full description,
see chapter <ptr target=DS>.

<p>Some composite texts, finally, are neither corpora, nor anthologies,
nor cyclic works:  they are otherwise unitary texts within which other
texts are embedded.  In general, they may be treated in the same way as
unitary texts, using the normal <gi>TEI.2</gi> and
<gi>body</gi> elements.  The embedded text itself may be encoded using
the <gi>text</gi> element, which may occur within quotations or between
paragraphs or other chunk-level elements inside the sections of a larger
text.  For further discussion, see chapter <ptr target=DS>.
<!-- The discussion of embedded texts really belongs in CO.  -MSM -->

<p>All composite texts share the characteristic that their different
component texts may be of structurally similar or dissimilar types.  If
all  component texts may all be encoded using the same base tag set,
then no problem arises. If however they require
different base tag sets, then either the general or the mixed base tag
set must be used, in addition to all relevant base tag sets. This
process is described in more detail in section <ptr target=STco>.








<!-- $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 <ptr 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 <ptr
target="CCas"> below.</p>

<p>Chapter <ptr 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 <ptr target="HD2">);
information about the encoding practices followed with the corpus, for
example its design principles, editorial practices, reference system
etc.  (see section <ptr 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 <ptr target="HD4">); and version information documenting any
changes made in the electronic text (see section <ptr target="HD6">).</p>

<p>In addition to the elements defined by chapter <ptr 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:

<list type=gloss>
<label><gi>textDesc</gi></label>
<item>provides a description of a text in terms of its

<term>situational parameters</term>.</item>
<label><gi>particDesc</gi></label>
<item>describes the identifiable speakers, voices or other 
participants
in a linguistic interaction. </item>
<label><gi>settingDesc</gi></label>
<item>describes the setting or settings within which a language

interaction takes place, either as a prose description or 
as a
series of <gi>setting</gi> elements.</item>
</list>


These elements form an optional extension to the <gi>profileDesc</gi>,
defined in section <ptr target="HD4"> and are further described in the
remainder of this section. They are formally defined as follows:

<eg id=dcchdr>
<![ CDATA [
<!-- 23.2:  Header extensions for Corpus Texts                -->
<!ELEMENT textDesc      - o  (channel, constitution, 
                             derivation, domain, factuality, 
                             interaction, preparedness, 
                             purpose+)                          >
<!ATTLIST textDesc           %a.global;
                             %a.declarable;                     >
<!ELEMENT particDesc    - o  (p+ | ( (person | personGrp)+, 
                             particLinks?) )                    >
<!ATTLIST particDesc         %a.global;
                             %a.declarable;                     >
<!ELEMENT settingDesc   - o  (p+ | setting+)                    >
<!ATTLIST settingDesc        %a.global;
                             %a.declarable;                     >
<!-- (continued in sec. 23.2.1, 23.2.2, 23.2.3)               -->
]]>
</eg>


<!-- 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 <ptr
target="HD43">, and section <ptr 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:

<list type=gloss>
<label><gi>channel</gi></label>
<item>describes the medium or channel by which a text is 
delivered or
experienced. For a written text, this might 
be print, manuscript, e-mail, etc.;
for a spoken one, 
radio, telephone, face-to-face, etc.
Attributes include:
<list type=gloss>
<label><att>mode</att></label>
<item>specifies the mode of this channel with respect to speech 
and writing.
Legal values are:
<list type=gloss>
<label><term>sw</term></label>
<item>spoken to be written (e.g. dictation)</item>
<label><term>m</term></label>
<item>mixed modes</item>
<label><term>x</term></label>
<item>unknown or inapplicable</item>
<label><term>s</term></label>
<item>spoken</item>
<label><term>ws</term></label>
<item>written to be spoken (e.g. a script)</item>
<label><term>w</term></label>
<item>written</item>
</list></item>
</list>
</item>
<label><gi>constitution</gi></label>
<item>describes the internal composition of a text or text 
sample,
for example
as fragmentary, complete, etc.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies how the text was constituted.
Legal values are:
<list type=gloss>
<label><term>composite</term></label>
<item>a text made by combining several smaller items, each 
individually complete</item>
<label><term>single</term></label>
<item>a single complete text</item>
<label><term>frags</term></label>
<item>a text made by combining several smaller, not necessarily 
complete, items</item>
<label><term>unknown</term></label>
<item>composition unknown or unspecified</item>
</list></item>
</list>
</item>
<label><gi>derivation</gi></label>
<item>describes the nature and extent of indebtedness or 
derivativeness
of this text with respect to others.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the derivation of the text.
Sample values include:
<list type=gloss>
<label><term>traditional</term></label>
<item>text has no obvious source but is one of a number derived 
from some common ancestor</item>
<label><term>revision</term></label>
<item>text is a revision of some other text</item>
<label><term>plagiarism</term></label>
<item>text is plagiarized from some other text</item>
<label><term>original</term></label>
<item>text is original</item>
<label><term>abridgment</term></label>
<item>text is an abridged version of some other text</item>
<label><term>translation</term></label>
<item>text is a translation of some other text</item>
</list></item>
</list>
</item>
<label><gi>domain</gi></label>
<item>describes the most important social context in which the 
text was
realized or for which it is intended, for example 
private vs. public,
education, religion, etc.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the domain of use.
Sample values include:
<list type=gloss>
<label><term>domestic</term></label>
<item>domestic and private</item>
<label><term>religious</term></label>
<item>religious and ceremonial</item>
<label><term>public</term></label>
<item>other forms of public context</item>
<label><term>education</term></label>
<item>education</item>
<label><term>art</term></label>
<item>art and entertainment</item>
<label><term>business</term></label>
<item>business and work place</item>
<label><term>govt</term></label>
<item>government and law</item>
</list></item>
</list>
</item>
<label><gi>factuality</gi></label>
<item>describes the extent to which the text may be regarded as

imaginative or non-imaginative, that is, as describing a 
fictional
or a non-fictional world. 
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the factuality of the text.
Legal values are:
<list type=gloss>
<label><term>fact</term></label>
<item>the text is to be regarded as entirely informative or 
factual</item>
<label><term>fiction</term></label>
<item>the text is to be regarded as entirely imaginative</item>
<label><term>mixed</term></label>
<item>the text contains a mixture of fact and fiction</item>
<label><term>inapplicable</term></label>
<item>the fiction/fact distinction is not regarded as helpful or 
appropriate to this text</item>
</list></item>
</list>
</item>
<label><gi>interaction</gi></label>
<item>describes the extent, cardinality and nature of any 
interaction
among those producing and experiencing the 
text, for example in the
form of response or interjection, 
commentary etc.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies whether or not there is any interaction between 
active and passive participants in the text.
Legal values are:
<list type=gloss>
<label><term>none</term></label>
<item>no interaction of any kind, e.g. a monologue</item>
<label><term>complete</term></label>
<item>complete interaction, e.g. a face to face conversation</item>
<label><term>inapplicable</term></label>
<item>this parameter is inappropriate or inapplicable in this 
case</item>
<label><term>partial</term></label>
<item>some degree of interaction, e.g. a monologue with set 
responses</item>
</list></item>
<label><att>active</att></label>
<item>specifies the number of active participants (or 
<term>addressors</term>) producing parts of the text.
Legal values are:
<list type=gloss>
<label><term>corporate</term></label>
<item>a corporate addressor</item>
<label><term>singular</term></label>
<item>a single addressor</item>
<label><term>plural</term></label>
<item>many addressors</item>
<label><term>unknown</term></label>
<item>number of addressors unknown or unspecifiable</item>
</list></item>
<label><att>passive</att></label>
<item>specifies the number of passive participants (or 
<term>addressees</term>) to whom a text is directed or in 
whose presence it is created or performed.
Suggested values include:
<list type=gloss>
<label><term>single</term></label>
<item>text is addressed to one other person e.g. a personal 
letter</item>
<label><term>self</term></label>
<item>text is addressed to the originator e.g. a diary</item>
<label><term>many</term></label>
<item>text is addressed to a countable number of others e.g. a 
conversation in which all participants are identified</item>
<label><term>group</term></label>
<item>text is addressed to an undefined but fixed number of 
participants e.g. a lecture</item>
<label><term>world</term></label>
<item>text is addressed to an undefined and indeterminately large 
number e.g. a published book</item>
</list></item>
</list>
</item>
<label><gi>preparedness</gi></label>
<item>describes the extent to which a text may be regarded as

prepared or spontaneous. 
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>a keyword characterizing the type of preparedness.
Sample values include:
<list type=gloss>
<label><term>scripted</term></label>
<item>follows a script</item>
<label><term>formulaic</term></label>
<item>follows a predefined set of conventions</item>
<label><term>none</term></label>
<item>spontaneous or unprepared</item>
<label><term>revised</term></label>
<item>polished or revised before presentation</item>
</list></item>
</list>
</item>
<label><gi>purpose</gi></label>
<item>characterizes a single purpose or communicative function of 
the
text.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>specifies a particular kind of purpose.
Suggested values include:
<list type=gloss>
<label><term>express</term></label>
<item>self expression, confessional, etc.</item>
<label><term>entertain</term></label>
<item>amuse, entertain, etc.</item>
<label><term>persuade</term></label>
<item>didactic, advertising, propaganda, etc.</item>
<label><term>inform</term></label>
<item>convey information, educate, etc.</item>
</list></item>
<label><att>degree</att></label>
<item>specifies the extent to which this purpose predominates.
Legal values are:
<list type=gloss>
<label><term>medium</term></label>
<item>this purpose is intermediate</item>
<label><term>low</term></label>
<item>this purpose is weak</item>
<label><term>unknown</term></label>
<item>extent unknown</item>
<label><term>high</term></label>
<item>this purpose is predominant</item>
</list></item>
</list>
</item>
</list>
</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 <bibl> <author>M. Kyt&ouml; and
M. Rissanen,</author> <title>The Helsinki Corpus of English
Texts,</title> in <title>Corpus Linguistics: hard and soft</title>,
ed.  <editor>M. Kyt&ouml;, O. Ihalainen, and M. Rissanen</editor>
(Amsterdam: Rodopi, 1988).  </bibl> </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 <ptr target="HD43">, and elements for defining or
declaring such classification schemes in section <ptr 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 <ptr target="FS"> and
<ptr 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 <ptr
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 <ptr
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:
<eg id=dccahtd>
<![ CDATA [
<!-- 23.2.1:  Header extensions for Corpus Texts (cont'd)     -->
<!-- (continuation of sec. 23.2)                              -->
<!ELEMENT channel       - o  (%phrase.seq)                      >
<!ATTLIST channel            %a.global;
          mode               (s | w | ws | sw | m | x) 
                                                 x              >
<!ELEMENT constitution  - o  (%phrase.seq)                      >
<!ATTLIST constitution       %a.global;
          type               (single | composite | frags | 
                             unknown)            single         >
<!ELEMENT derivation    - o  (%phrase.seq)                      >
<!ATTLIST derivation         %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT domain        - o  (%phrase.seq)                      >
<!ATTLIST domain             %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT factuality    - o  (%phrase.seq)                      >
<!ATTLIST factuality         %a.global;
          type               (fiction | fact | mixed | 
                             inapplicable)       #IMPLIED       >
<!ELEMENT interaction   - o  (%phrase.seq;)                     >
<!ATTLIST interaction        %a.global;
          passive            CDATA               #IMPLIED
          type               (none | partial | complete | 
                             inapplicable)       #IMPLIED
          active             CDATA               #IMPLIED       >
<!ELEMENT preparedness  - o  (%phrase.seq)                      >
<!ATTLIST preparedness       %a.global;
          type               CDATA               #IMPLIED       >
<!ELEMENT purpose       - o  (%phrase.seq)                      >
<!ATTLIST purpose            %a.global;
          type               CDATA               #IMPLIED
          degree             (high | medium | low | unknown) 
                                                 #IMPLIED       >
]]>
</eg>


<!-- 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:

<list type=gloss>
<label><gi>person</gi></label>
<item>describes a single participant in a language interaction. 
Attributes include:
<list type=gloss>
<label><att>role</att></label>
<item>specifies the role of this participant in the group.</item>
<label><att>sex</att></label>
<item>specifies the sex of the participant.
Sample values include:
<list type=gloss>
<label><term>m</term></label>
<item>male</item>
<label><term>f</term></label>
<item>female</item>
<label><term>u</term></label>
<item>unknown or inapplicable</item>
</list></item>
<label><att>age</att></label>
<item>specifies the age group to which the participant belongs.</item>
</list>
</item>
<label><gi>personGrp</gi></label>
<item>describes a group of individuals treated as a single person 
for
analytic purposes.
Attributes include:
<list type=gloss>
<label><att>role</att></label>
<item>specifies the role of this group of participants in the 
interaction.</item>
<label><att>sex</att></label>
<item>specifies the sex of the participant group.
Sample values include:
<list type=gloss>
<label><term>m</term></label>
<item>male</item>
<label><term>x</term></label>
<item>mixed</item>
<label><term>f</term></label>
<item>female</item>
<label><term>u</term></label>
<item>unknown</item>
</list></item>
<label><att>age</att></label>
<item>specifies the age group of the participants.</item>
<label><att>size</att></label>
<item>specifies the size or approximate size of the group.</item>
</list>
</item>
<label><gi>particLinks</gi></label>
<item>describes the relationships or social links existing 
between
participants in a linguistic interaction. </item>
</list>


<!-- 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 <ptr 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 <ptr 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>:

<list type=gloss>
<!-- removed  name, persname, placename now that ND is back -->
<label><gi>birth</gi></label>
<item>contains information about a person's birth, such as its 
date
and place.
Attributes include:
<list type=gloss>
<label><att>date</att></label>
<item>specifies the date of birth in an ISO standard form 
(yyyy-mm-dd).</item>
</list>
</item>
<label><gi>firstLang</gi></label>
<item>specifies the first language of a participant.</item>
<label><gi>langKnown</gi></label>
<item>contains an informal description of a person's competence 
in
different languages, dialects, etc.</item>
<label><gi>residence</gi></label>
<item>describes a person's present or past places of residence.</item>
<label><gi>education</gi></label>
<item>contains a brief prose description of the
educational 
background of a participant.</item>
<label><gi>affiliation</gi></label>
<item>contains an informal description of a person's present
or 
past affiliation with some
organization, for example an 
employer or sponsor.</item>
<label><gi>occupation</gi></label>
<item>contains an informal description of a person's trade,

profession or occupation.
Attributes include:
<list type=gloss>
<label><att>scheme</att></label>
<item>identifies the classification system or taxonomy in use by 
supplying the identifier of a <gi>taxonomy</gi> element 
elsewhere in the header.</item>
<label><att>code</att></label>
<item>identifies an occupation code defined within the 
classification system or taxonomy defined by the 
<att>scheme</att> attribute.</item>
</list>
</item>
<label><gi>socecStatus</gi></label>
<item>contains an informal description of a person's perceived 
social or
economic status.
Attributes include:
<list type=gloss>
<label><att>scheme</att></label>
<item>identifies the classification system or taxonomy in use.</item>
<label><att>code</att></label>
<item>identifies a status code defined within the classification 
system or taxonomy defined by the <att>source</att> 
attribute.</item>
</list>
</item>
</list>
</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 <ptr 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 <ptr target="COna">, or the more specialised and detailed
elements provided by chapter <ptr 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 <ptr
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:

<list type=gloss>
<label><gi>relation</gi></label>
<item>describes any kind of relationship or linkage amongst a 
specified
group of participants.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>categorizes the relationship in some respect, e.g. as 
social, personal or other.
Suggested values include:
<list type=gloss>
<label><term>social</term></label>
<item>relationship concerned with social roles</item>
<label><term>personal</term></label>
<item>relationship concerned with personal roles, e.g. kinship, 
marriage, etc.</item>
<label><term>other</term></label>
<item>other kinds of relationship</item>
</list></item>
<label><att>desc</att></label>
<item>briefly describes the relationship.</item>
<label><att>active</att></label>
<item>identifies the <q>active</q>participants in a non-mutual 
relationship, or all the participants in a mutual one.</item>
<label><att>passive</att></label>
<item>identifies the <q>passive</q> participants in a non-mutual 
relationship.</item>
<label><att>mutual</att></label>
<item>indicates whether the relationship holds equally amongst 
all the participants.
Legal values are:
<list type=gloss>
<label><term>Y</term></label>
<item>the relationship is mutual</item>
<label><term>N</term></label>
<item>the relationship is directed</item>
</list></item>
</list>
</item>
</list>
</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 <mentioned>is X of</mentioned> or <mentioned>is X to</mentioned>.  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
<mentioned>is parent of</mentioned>); the employer is <q>active</q>, the
employee <q>passive</q>, in the relationship <mentioned>employs</mentioned>.
These relationships can be inverted: parents are <q>passive</q> and
children <q>active</q> in the relationship <mentioned>is child of</mentioned>;
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 -->
<eg id=dccahpa>
<![ CDATA [
<!-- 23.2.2:  Header extensions for Corpus Texts (cont'd)     -->
<!-- (continuation of sec. 23.2)                              -->
<!ENTITY % x.demographic ''                                     >
<!ENTITY % m.demographic '%x.demographic affiliation | birth | 
           education | firstLang | langKnown | occupation | 
           persName | residence | socecStatus'                  >
<!ELEMENT person        - o  (p+ | (%m.demographic)* )          >
<!ATTLIST person             %a.global;
          role               CDATA               #IMPLIED
          sex                (m | f | u )        #IMPLIED
          age                CDATA               #IMPLIED       >
<!ELEMENT personGrp     - o  (p+ | (%m.demographic)* )          >
<!ATTLIST personGrp          %a.global;
          role               CDATA               #IMPLIED
          sex                (m | f | u | x)     #IMPLIED
          size               CDATA               #IMPLIED
          age                CDATA               #IMPLIED       >
<!ELEMENT birth         - -  (%phrase.seq)                      >
<!ATTLIST birth              %a.global;
          date               %ISO-date           #IMPLIED       >
<!ELEMENT firstLang     - o  (%phrase.seq)                      >
<!ATTLIST firstLang          %a.global;                         >
<!ELEMENT langKnown     - -  (%phrase.seq)                      >
<!ATTLIST langKnown          %a.global;                         >
<!ELEMENT residence     - o  (%phrase.seq)                      >
<!ATTLIST residence          %a.global;                         >
<!ELEMENT education     - o  (%phrase.seq)                      >
<!ATTLIST education          %a.global;                         >
<!ELEMENT affiliation   - -  (%phrase.seq)                      >
<!ATTLIST affiliation        %a.global;                         >
<!ELEMENT occupation    - -  (%phrase.seq)                      >
<!ATTLIST occupation         %a.global;
          scheme             IDREF               #IMPLIED
          code               IDREF               #IMPLIED       >
<!ELEMENT socecStatus   - o  (%phrase.seq)                      >
<!ATTLIST socecStatus        %a.global;
          scheme             IDREF               #IMPLIED
          code               IDREF               #IMPLIED       >
<!ELEMENT particLinks   - o  (p+ | relation+)                   >
<!ATTLIST particLinks        %a.global;                         >
<!ELEMENT relation      - o  EMPTY                              >
<!ATTLIST relation           %a.global;
          desc               CDATA               #IMPLIED
          passive            IDREFS              #IMPLIED
          type               CDATA               personal
          active             IDREFS              #IMPLIED
          mutual             (Y | N)             Y              >
]]>
</eg>


<!-- 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 <ptr 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:

<list type=gloss>
<label><gi>setting</gi></label>
<item>describes one particular setting in which a language 
interaction
takes place.
Attributes include:
<list type=gloss>
<label><att>who</att></label>
<item>supplies the identifiers of the participants at this 
setting.</item>
</list>
</item>
<label><gi>name</gi></label>
<item>contains a proper noun or noun phrase.
Attributes include:
<list type=gloss>
<label><att>type</att></label>
<item>indicates the type of the object which is being named by 
the phrase.</item>
</list>
</item>
<label><gi>date</gi></label>
<item>contains a date in any format.
Attributes include:
<list type=gloss>
<label><att>value</att></label>
<item>gives the value of the date in some standard form, usually 
yyyy-mm-dd.</item>
</list>
</item>
<label><gi>time</gi></label>
<item>contains a phrase defining a time of day in any format.
Attributes include:
<list type=gloss>
<label><att>value</att></label>
<item>gives the value of the time in a standard form.</item>
</list>
</item>
<label><gi>locale</gi></label>
<item>contains a brief informal description of the nature of a

place for example a room, a restaurant, a park bench etc.</item>
<label><gi>activity</gi></label>
<item>contains a brief informal description of what a participant 
in a
language interaction is doing other than speaking, if 
anything.</item>
</list>
</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 <ptr 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:

<eg id=dccahse>
<![ CDATA [
<!-- 23.2.3:  Header extensions for Corpus Texts (cont'd)     -->
<!-- (continuation of sec. 23.2)                              -->
<!ELEMENT setting       - -  (p+ | (name | time | date | locale 
                             | activity)* )                     >
<!ATTLIST setting            %a.global;
          who                IDREFS              #IMPLIED       >
<!ELEMENT locale        - o  (%phrase.seq)                      >
<!ATTLIST locale             %a.global;                         >
<!ELEMENT activity      - o  (%phrase.seq)                      >
<!ATTLIST activity           %a.global;                         >
]]>
</eg>


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

<!--* $Id: p2ccas.odd,v 1.6 1998/01/28 11:44:14 cmsmcq Exp $ *-->
<!--*
    * $Log: p2ccas.odd,v $
# Revision 1.6  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *-->
<!-- Revisions:                                               -->
<!-- 17 jan 98 : LB : fix egs; remove erroneous ref to        -->
<!--        Samplingdecl within editdecl                      -->
<!-- 4 jan 98: LB: TEI.corpus shd be  teiCorpus               -->
<!-- 3 jan 94: LB: analysis becomes interptn                  -->
<!-- 93-06-05 : MSM : suppress dot in col 1                   -->
<!-- 93-06-03 : MSM : LB changed id from bibllist to listbibl -->
<!-- 93-03-11 : MSM : last minute changes as per LB           -->
<!-- 93-03-10 : MSM : revise for publication:                 -->
<!--                  some changes for clarity, some cosmetic -->
<!--                  new IDs in large example and discussion -->
<!--                  change phrasing of last summary rule    -->
<!-- 93-03-08 : MSM : correct IDREF from listbibl to bibllist -->
<!-- Date: Sat, 06 Mar 1993 22:00:51 +0000                    -->
<!-- From: Lou Burnard < lou@vax.ox.ac.uk >                   -->
<!-- To: U35395@UICVM.UIC.EDU                                 -->
<!-- CC: lou@vax.ox.ac.uk                                     -->
<!-- Subject: CCas.odd (5 of 10)                              -->

<div2 id=CCas><head>Associating Contextual Information with a Text</head>

<p>This section discusses the assocation of the contextual information
held in the header with the individual elements making up a TEI text or
corpus.  Contextual information is held in elements of various kinds
within the TEI header, as discussed elsewhere in this section and in
chapter <ptr target=HD>.  Here we consider what happens when different
parts of a document need to be associated with different contextual
information of the same type, for example when one part of a document
uses a different encoding practice from another, or where one part
relates to a different setting from another.  In such situations, there
will be more than one instance of a header element of the relevant type.

<p>The TEI DTDs allow for the following possibilities:

<list>
<item>A given element may appear in the corpus header only, in the
header of one or more texts only, or in both places
<item>There may be multiple occurrences of certain elements in either
corpus or text header.
</list>

<p>To simplify the exposition, we deal with these two possibilities
separately in what follows; however, they may be combined as
desired.

<div3 id=CCas1><head>Combining Corpus and Text Headers</head>

<p>A TEI conformant document may have more than one header only in the
case of a TEI corpus, which must have a header in its own right, as well
as the obligatory header for each text.  Every element specified in a
corpus-header is understood as if it appeared within every text header
in the corpus.  An element specified in a text header but not in the
corpus header supplements the specification for that text alone.  If any
element is specified in both corpus and text headers, the corpus header
element is over-ridden for that text alone.

<p>The <gi>titleStmt</gi> for a corpus text is understood to be
prefixed by the <gi>titleStmt</gi> given in the corpus header.  All
other optional elements of the <gi>fileDesc</gi> should be omitted from
an individual corpus text header unless they  differ from those
specified in the corpus header.  All other header elements behave
identically, in the manner documented below.

<!-- NB this implies that publication stmt should become      -->
<!-- optional (LB).  ouch.  -msm                              -->

This facility makes it possible to state once for all in the corpus
header each piece of contextual information which is common to the whole
of the corpus, while still allowing for individual texts to vary from
this common denominator.

<p>For example, the following schematic shows the structure of a corpus
comprising three texts, the first and last of which share the same
encoding declaration.  The second one has its own encoding declaration

<eg rend=skel> <![ CDATA [
<teiCorpus.2>
<TeiHeader>
    <!-- contains declarations common to the whole corpus -->
    <fileDesc> ... </>
    <encodingDesc> ...
        <!-- for example, this encodingDesc is common to
             whole corpus. --> ... </>
    <revisionDesc> ... </>
</TeiHeader>

<TEI.2>
<TeiHeader>
   <fileDesc>
        <!-- details peculiar to this text --> ... </>
</TeiHeader>
<text>
 ...
</TEI.2>

<TEI.2>
<TeiHeader>
   <fileDesc>
        <!-- details peculiar to this text --> ... </>
   <encodingDesc>
        <!-- encoding description
             peculiar to this text --> ... </>
</TeiHeader>
<text>
 ...
</TEI.2>

<TEI.2>
<TeiHeader>
   <fileDesc><!-- details peculiar to this text --> ... </>
</TeiHeader>
<text>
 ...
</TEI.2>
</teiCorpus.2>

]]>
</eg>

<div3 id=CCas2><head>Declarable Elements</head>

<p>Certain of the elements which can appear within a TEI Header are
known as <term>declarable elements</term>. These elements have in
common the fact that they may be linked explicitly with a particular
part of a text or corpus by means of a <att>decls</att> attribute. This
linkage is used to over-ride the default association between
declarations in the header and a corpus or corpus text. The only header
elements which may be associated in this way are those which would not
otherwise be meaningfully repeatable.

An alphabetically ordered list of declarable elements follows:

<!-- I have done this as a taglist, but I'm not sure -->
<!-- whether this is really necessary or advisable   -->

<list type=gloss>
<label><gi>bibl</gi></label>
<item>contains a loosely-structured bibliographic citation of 
which
the sub-components may or may not be explicitly 
tagged. </item>
<label><gi>biblFull</gi></label>
<item>contains a fully-structured bibliographic citation, in 
which all
components of the TEI file description
are 
present.
<!-- except maybe the source.desc? --></item>
<label><gi>biblStruct</gi></label>
<item>contains a structured bibliographic citation, in which only
bibliographic subelements appear and in a specified order. </item>
<label><gi>broadcast</gi></label>
<item>describes a broadcast used as the source of a spoken text.</item>
<label><gi>correction</gi></label>
<item>states how and under what circumstances corrections have 
been
made in the text.</item>
<label><gi>editorialDecl</gi></label>
<item>provides details of editorial principles and practices 
applied
during the encoding of a text.</item>
<label><gi>equipment</gi></label>
<item>provides technical details of the equipment and media used 
for
an audio or video recording used as the source for a 
spoken text.</item>
<label><gi>hyphenation</gi></label>
<item>summarizes the way in which hyphenation in a source text 
has been
treated in an encoded version of it.</item>
<label><gi>interpretation</gi></label>
<item>describes the scope of any analytic or interpretive 
information
added to the text in addition to the 
transcription. </item>
<label><gi>langUsage</gi></label>
<item>describes the languages, sublanguages, registers, dialects 
etc.
represented within a text.</item>
<label><gi>listBibl</gi></label>
<item>contains a list of bibliographic citations of any kind. </item>
<label><gi>normalization</gi></label>
<item>indicates the extent of normalization or regularization of 
the
original source carried out in converting it to 
electronic form.</item>
<label><gi>particDesc</gi></label>
<item>describes the identifiable speakers, voices or other 
participants
in a linguistic interaction. </item>
<label><gi>projectDesc</gi></label>
<item>describes in detail the aim or purpose for which an 
electronic
file was encoded, together with any other 
relevant information
concerning the process by which it 
was assembled or collected.</item>
<label><gi>quotation</gi></label>
<item>specifies editorial practice adopted with respect to 
quotation
marks in the original. </item>
<label><gi>recording</gi></label>
<item>details of an audio or video recording event
used as the 
source of a spoken text, either directly or from
a public 
broadcast. </item>
<label><gi>samplingDecl</gi></label>
<item>contains a prose description of the rationale and methods 
used
in sampling texts in the creation of a corpus or 
collection.</item>
<label><gi>scriptStmt</gi></label>
<item>contains a citation giving details of the script used for

a spoken text.</item>
<label><gi>segmentation</gi></label>
<item>describes the principles according to which the text has 
been
segmented, for example into sentences, tone-units, 
graphemic strata,
etc.</item>
<label><gi>sourceDesc</gi></label>
<item>supplies a bibliographic description of the copy text(s) 
from
which an electronic text was derived or generated.</item>
<label><gi>stdVals</gi></label>
<item>specifies the format used when standardized date or number

values are supplied.</item>
<label><gi>textClass</gi></label>
<item>groups information which describes the nature or topic of a 
text
in terms of a standard classification scheme, 
thesaurus, etc.</item>
<label><gi>textDesc</gi></label>
<item>provides a description of a text in terms of its

<term>situational parameters</term>.</item>
</list>


All of the above elements may be multiply defined within a single
header, that is, there may be more than one instance of any declarable
element type at a given level.  When this occurs, the following rules
apply:

<list type=bullets>
<item>every declarable element must bear a unique identifier
<item>for each different type of declarable element which occurs more
than once within the same parent element, exactly one element must be
specified as the default
</list>

<p>In the following example, an editorial declaration contains two
possible <gi>correction</gi> policies, one identified as C1 and the
other as C2.  Since there are two, one of them (in this case C1) must be
specified as the default:

<eg>
<![ CDATA [
 <editorialDecl>
     <correction id=C1 default=YES><p> ... </correction>
     <correction id=C2><p> ... </correction>
     <normalization id=N1>
     <p> ...
     <p> ...
 </editorialDecl>
]]>
</eg>

For texts associated with the header in which this declaration appears
correction method C1 will be assumed, unless they explicitly state
otherwise.  Here is the structure for a text which does state otherwise:

<eg rend=skel>
<![ CDATA [
 <text><body>
   <!--  ... -->
     <div1 n=d1> ... </div1>
     <div1 n=d2 decls=C2> ... </div1>
     <div1 n=d3> ... </div1>
   <!--  ... -->
 </body></text>
]]>
</eg>

In this case, the contents of the divisions D1 and D3 will both use
correction policy C1, and those of division D2 will use correction
policy C2.

<p>The <att>decls</att> attribute is defined for any element which is a
member of the class <term>declaring</term>.  This includes the major
structural elements <gi>text</gi>, <gi>group</gi>, and <gi>div</gi>, as
well as smaller structural units, down to the level of paragraphs in
prose, individual utterances in spoken texts, and entries in
dictionaries.  However, TEI recommended practice is to limit the number
of multiple declarable elements used by a document as far as possible,
for simplicity and ease of processing.

<p>The identifier or identifiers specified by the <att>decls</att>
attribute are subject to two further restrictions:

<list type=bullets>
<item>An identifier specifying an element which contains multiple
instances of one or more other elements should be interpreted as if it
explicitly identified the elements identified as the default in each
such set of repeated elements
<item>Each element specified, explicitly or implicitly, by the list of
identifiers must be of a different type.
</list>

<p>To demonstrate how these rules operate, we now expand our earlier
example slightly:

<eg>
<![ CDATA [
 <encodingDesc>
   <!--     ...  -->
        <editorialDecl  id=ED1 default=YES>
            <correction id=C1a default=YES>
            <correction id=C1b>
            <normalization id=N1>
            <p> ...
            <p> ...
        </editorialDecl>
        <editorialDecl id=ED2>
            <correction id=C2a default=YES>
            <correction id=C2b>
            <normalization id=N2a>
            <normalization id=N2b default=YES>
            <p>
        </editorialDecl>
   <!--  ... -->
</encodingDesc>
]]>
</eg>

<p>This encoding description now has two editorial declarations,
identified as ED1 (the default) and ED2.  For texts not specifying
otherwise, ED1 will apply.  If ED1 applies, correction method C1a and
normalization method N1 apply, since these are the specified defaults
within ED1.  In the same way, for a text specifying <att>decls</att> as
<q>ED2</q>, correction C2a, <!-- sampling SAMP2--> and normalization N2b will
apply.

<p>A finer grained approach is also possible.  A text might specify
<tag>text decls='C2b N2a'</tag>, <!-- or even <tag>text decls='C1a N2a
SAMP2'</tag>, --> to <soCalled>mix and match</soCalled> declarations as
required.  A tag such as <tag>text decls='ED1 ED2'</tag> would
(obviously) be illegal, since it includes two elements of the same type;
a tag such as <tag>text decls='ED2 C1a'</tag> is also illegal, since in
this context <q>ED2</q> is synonymous with the defaults for that
editorial declaration, namely <q><!-- SAMP2 -->C2a N2b</q>, resulting in a list
that identifies two correction elements (C1a and C2a).

<div3 id=CCas3><head>Summary</head>

<p>The rules determing which of the declarable elements are applicable
at any point may be summarized as follows:

<list type=ordered>
<item>If there is a single occurrence of a given declarable
element in a corpus header, then it applies by default to all elements
within the corpus.
<item>If there is a single occurrence of a given declarable
element in the text header, then it applies by default to all elements
of that text irrespective of the contents of the corpus header.
<item>Where there are multiple occurrences of declarable elements
within either corpus or text header,
<list>
<item>each must have a unique value specified as the value
of its <att>id</att> attribute;
<item>one only must bear a <att>default</att> attribute with
the value <code type=kw>YES</code>.
</list>
<item>It is a semantic error for an element to be associated
with more than one occurrence of any declarable element.
<item>Selecting an element which contains multiple occurrences of a
given declarable element is semantically equivalent to selecting only
those contained elements which are specified as defaults.
<item>An association made by one element applies by default
to all of its descendants.
<!-- < item >An association once made is inherited by all     -->
<!-- descendants of the element concerned, unless explicitly  -->
<!-- overridden.                                              -->
</list>


<!-- Revisions:                                               -->
<!-- 29 may LB : minor changes post Eynsham; moved CLAWs eg to AI -->
<!-- 93-03-11 : MSM : delete indented version of CLAWS output -->
<!-- 93-03-10 : MSM : correct constit. analysis               -->
<!-- 93-03-10 : MSM : bowdlerize bibl citation                -->
<!-- 93-03-10 : MSM : revise for publication:                 -->
<!--                  change stenstrom:  oelig or oslash ?    -->
<!-- 93-03-08 : MSM : put sgml comments around ellipses       -->
<!-- 93-03-08 : MSM : put citn DATE into IMPRINT              -->
<!-- Date: Sat, 06 Mar 1993 22:01:14 +0000                    -->
<!-- From: Lou Burnard < lou@vax.ox.ac.uk >                   -->
<!-- To: U35395@UICVM.UIC.EDU                                 -->
<!-- CC: lou@vax.ox.ac.uk                                     -->
<!-- Subject: CCan.odd (6 of 10)                              -->
<!--                                                          -->

<div2 id=CCan><head>Linguistic Annotation of Corpora</head>

<p>Language corpora often include analytic encodings or annotations,
designed to support a variety of different views of language.  The
present Guidelines do not advocate any particular approach to linguistic
annotation (or <soCalled>tagging</soCalled>); instead a number of
general analytic facilities are provided which support the
representation of most forms of annotation in a standard and
self-documenting manner.  Analytic annotation is of importance in many
fields, not only in corpus linguistics, and is therefore discussed in
general terms elsewhere in the Guidelines.<note>
See in particular chapters <ptr target=SA>,
<ptr target=AI>, and <ptr target=FS>.
</note>
The present section presents informally some particular applications of
these general mechanisms to the specific practice of corpus linguistics.

<div3 id=CCan1><head>Levels of Analysis</head>

<p>By <term>linguistic annotation</term> we mean here any annotation
determined by an analysis of linguistic features of the text, excluding
as borderline cases both the formal structural properties of the text
(e.g. its division into chapters or paragraphs) and descriptive
information about its context (the circumstances of its production, its
genre or medium).  The structural properties of any TEI-conformant text
should be represented using the structural elements discussed elsewhere
in this chapter and in chapters <ptr target=CO>, <ptr target=DS>, and
the various chapters of Part III (on base tag sets).  The contextual
properties of a TEI text are fully documented in the TEI Header, which
is discussed in chapter <ptr target=HD>, and in section <ptr
target=CCah> of the present chapter.

<p>Other forms of linguistic annotation may be applied at a number of
levels in a text.  A code (such as a word-class or part-of-speech
code) may be associated with each word or token, or with groups of such
tokens, which may be continuous, discontinuous or nested.  A code may
also be associated with relationships (such as cohesion) perceived as
existing between distinct parts of a text.  The codes themselves may
stand for discrete non-decomposable categories, or they may represent
highly articulated bundles of textual features.  Their function may be
to place the annotated part of the text somewhere within a narrowly
linguistic or discoursal domain of analysis, or within a more general
semantic field, or any combination drawn from these and other domains.

<p>The manner by which such annotations are generated and attached to
the text may be entirely automatic, entirely manual or a mixture.  The
ease and accuracy with which analysis may be automated may vary with the
level at which the annotation is attached.  The method employed should
be documented in the <gi>interpretation</gi> element within the encoding
description of the TEI Header, as described in section <ptr
target=HD53>.  Where different parts of a corpus have used different
annotation methods, the <att>decls</att> attribute may be used to
indicate the fact, as further discussed in section <ptr target=CCas>.

<p>An extended example of one form of linguistic analysis commonly
practised in corpus linguistics is given in section <ptr target=AIla>.





<!-- Revisions:                                               -->
<!-- 1993-03-10 : MSM : cosmetic changes for publication      -->
<!-- Date: Sat, 06 Mar 1993 22:01:39 +0000                    -->
<!-- From: Lou Burnard  < lou@vax.ox.ac.uk >                  -->
<!-- To: U35395@UICVM.UIC.EDU                                 -->
<!-- CC: lou@vax.ox.ac.uk                                     -->
<!-- Subject: CCrec.odd (7 of 10)                             -->


<div2 id=CCrec><head>Recommendations for the Encoding of Large Corpora</head>

<p>These Guidelines include proposals for the identification and
encoding of a far greater variety of textual features and
characteristics than is likely to be either feasible or desirable in
any one language corpus, however large and ambitious.  The reasoning
behind this catholic approach is further discussed in chapter <ptr
target=AB>.  For most large scale corpus projects, it will therefore
be necessary to determine a subset of TEI recommended elements
appropriate to the anticipated needs of the project.  Mechanisms for
tailoring the TEI dtd to implement such a subset are described in
chapter <ptr target=ST> and chapter <ptr target=MD>; they include
the ability to exclude selected element types, add new element types,
and change the names of existing elements.  A discussion of the
implications of such changes for TEI conformance is provided in
chapter <ptr target=CF>.

<p>Because of the high cost of identifying and encoding many textual
features, and the difficulty in ensuring consistent practice across very
large corpora, encoders may find it convenient to divide the set of
elements to be encoded into the following three categories:

<list type=gloss>
<label>required<item>texts included within the corpus will always
encode textual features in this category, should they exist in the
text
<label>recommended<item>textual features in this category will be
encoded wherever economically and practically feasible; where present
but not encoded, a note in the header should be made.
<label>optional<item>textual features in this category may or may not
be encoded; no conclusion about the absence of such features can be
inferred from the absence of the corresponding element in a given text.
</list>


<!-- hmm, is that all? -->


             <!-- 23 Corpora -->
<!>
</div1>
