<?tei:SOF p2stec.odd ?>
<!-- $Id: p2stec.odd,v 1.14 1998/01/31 18:32:23 tei Exp $ -->
<!--*
    * $Log: p2stec.odd,v $
    * Revision 1.14  1998/01/31 18:32:23  tei
    * add fmchunk
    *
    * Revision 1.13  98/01/28  11:05:29  cmsmcq
    * LB's changes of January 1998
    * 
    * Revision 1.12  1994/08/29  15:43:52  cmsmcq
    * Fixes for unreachability problems
    * 
    * Revision 1.11  1994/04/08  01:36:34  msmcq
    * Last-round changes before publication of P3
    * 
    * Revision 1.10  1994/04/01  16:36:47  msmcq
    * changes / fixes during validation of DTD
    * 
    * Revision 1.9  1994/03/28  15:23:18  lou
    * fix duff xrefs
    * 
    * Revision 1.8  1994/03/24  22:20:40  msmcq
    * typos found by David Barnard et al. corrected
    * 
    * Revision 1.7  1994/03/16  03:27:47  msmcq
    * minor interim changes (PH, typo)
    * 
    * Revision 1.6  1994/03/01  03:49:01  msmcq
    * first cut at restoring consistency, while checking FT
    * 
    * Revision 1.5  1994/01/04  13:02:04  lou
    * add verse attrib classes etc; reorder cladecls
    * 
    * Revision 1.3  1993/09/15  22:51:45  msmcq
    * Changes for publication of TD
    * 
    * Revision 1.2  1993/06/22  14:29:49  msmcq
    * Changes a propos of DTD generation
    * -->
<!-- P2STec :  Element Classes                                -->
<!-- Revisions:                                               -->
<!-- 31 Jan 98: LB : add fmchunk class -->
<!-- 8 Jan 98: LB : add typed class; revise clseg accordingly -->
<!-- 4 Jan 98 : LB  : add editincl as further child of globincl -->
<!-- 94-08-04 : MSM : make refsys a child of globincl         -->
<!-- 94-03-31 : MSM : declare default mix-dot entities here   -->
<!-- 94-03-31 : MSM : add ref to names.dates.ent              -->
<!-- 94-03-30 : MSM : suppress readings again (in TC)         -->
<!-- 94-03-30 : MSM : add ref to TEI.textcrit.ent             -->
<!-- 94-03-30 : MSM : add clseg to atts classes               -->
<!-- 94-03-30 : MSM : suppress ref to lmgenxx                 -->
<!-- 94-03-29 : MSM : add readings                            -->
<!-- 94-03-29 : MSM : work toward sorting out class problems  -->
<!-- 94-03-22 : MSM : typos, etc. from DB, JLav               -->
<!-- 94-03-22 : MSM : retag some TERMs, Qs, as CODE, IDENT    -->
<!-- 94-03-22 : MSM : typos, stylistic changes from Team WWP  -->
<!-- 94-03-14 : MSM : add clinterp                            -->
<!-- 94-03-07 : MSM : add tei.transcr.ent                     -->
<!-- 94-02-28 : MSM : add clloc model class                   -->
<!-- 94-02-28 : MSM : suppress pointer, xpointer, ptrgrp      -->
<!-- 94-02-28 : MSM : (which are no longer model classes)     -->
<!-- 94-02-25 : MSM : suppress pname, plname classes          -->
<!-- 94-02-25 : MSM : suppress CE ent, add FT ent             -->
<!-- 29 dec LB: add cladecls for vephr.cla et al              -->
<!-- 20 dec 93 : LB : change name of seg class to avoid nameclash -->
<!-- 93-09-14 : MSM : dictionar-ies not -y                    -->
<!-- 93-09-13 : MSM : add agent class                         -->
<!-- 93-09-13 : MSM : add stagedir, sgmlkw, drfront, clfront  -->
<!-- 93-09-13 : MSM : add default component decl              -->
<!-- 93-09-13 : MSM : change ref to conana to conars          -->
<!-- 93-06-21 : MSM : suppress reference to flatterm          -->
<!-- 93-06-21 : MSM : add plname, pname, tempexp              -->
<!-- 93-06-21 : MSM : (di and tc classes *not* added yet)     -->
<!-- 93-06-21 : MSM : add cladecls for a-classes              -->
<!-- 93-06-21 : MSM : correct typo in termologg.ent           -->
<!-- 93-06-21 : MSM : clean up dtdfrag refs                   -->
<!-- 93-04-07 : MSM : some changes for clarity, consistency   -->
<!--                  cosmetic changes                        -->
<!-- 93-04-06 : MSM : distinguish phrase (cla), pephrase (pe) -->
<!-- 3 apr 93 : LB revise for publication                     -->
<!--    added ref to divn class; various changes of wording   -->
<!-- 93-03-30 : MSM : cleanup for LB                          -->
<!-- 93-03-29 : MSM : correct ref to TSbati                   -->
<!-- 93-03-29 : MSM : change id to teflne was teflattm        -->
<!-- 93-03-27 : MSM : ids on dummy dtdfrags                   -->
<!-- 93-03-23f : MSM : revise for clarity, correctness        -->
<!-- 93-03-06 : MSM : correct duplicat id                     -->
<!-- 93-03-06 : MSM : correct ref:  for copb read cors        -->
<!-- 93-03-06 : MSM : finish work-through                     -->
<!-- 93-03-06 : MSM : fill in dtd fragments (all but misc)    -->
<!-- 93-03-06 : MSM : add general section on m. and x. ents   -->
<!-- 93-03-06 : MSM : add section on inheritance              -->
<!-- 93-03-05 : MSM : rev toward pub                          -->
<!-- 93-03-05 : MSM : revise dtdfrags                         -->
<!-- 93-03-01 : MSM : remove other parameter entities         -->
<!-- 93-02-02 : MSM : add dtd fragments                       -->
<!-- 93-02-02 : MSM : merge VM and PC changes                 -->
<!-- 25 Jan 93 : CMSMcQ : first revision for publication      -->
<!-- 21 Oct 92 : CMSMcQ : new id new name quick full draft    -->
<!-- 17 May 92 : CMSMcQ : began draft                         -->
 
<div2 id=STEC><head>Element Classes</head>
 
<p>The TEI DTD contains over four hundred element types.  To aid
comprehension, modularity and modification, the majority of these
elements are formally classified in some way.  This section describes
the various <term>element classes</term> recognized in the TEI DTD.
Element classes are used to express two distinct kinds of commonality
among elements.  The elements of a class may share some set of SGML
attributes, or they may appear in the same locations in the content
models of the TEI DTDs, or both.  A class is known as an
<term>a-class</term> if its members share attributes, and as an
<term>m-class</term> if its members appear at the same locations in the
content models of other TEI elements.  An element is said to
<term>inherit</term> attributes, or the ability to appear at a given
point in a document, from any classes of which it is a member.  Classes
may have subclasses and superclasses, and the characteristics of a
superclass are inherited by all members of its subclasses.
 
<p>Both types of element classes are represented in the TEI DTDs by
parameter entities.  For other uses of parameter entities in the TEI
DTDs, see section <xref target=STPE>.
 
<p>This section describes the major element classes of each type
together with the formal declarations for their parameter entities,
which are contained in the file <ident type=file>teiclas2.ent</ident>.
All element classes are documented in the alphabetical reference section
in Part VII.
 
<div3 id=STECAT><head>Classes Which Share Attributes</head>
 
<p>An attribute class (a-class) groups together elements which share
some set of common attributes.  For example, the members of the class
<ident type=class>names</ident> are all elements which contain proper
nouns: e.g.  <gi>name</gi>, <gi>placeName</gi>, or <gi>persName</gi>.
All of these elements use the same attributes (<att>key</att> and
<att>reg</att>) to record information about the referent or the
regularized form of the proper nouns.  Similarly, the members of the
<ident type=class>pointer</ident> class share a set of attributes
useful for managing cross-reference links and other pointers.<note
place=foot>Because the details of their pointing mechanism differ, the
members of the <ident type=class>pointer</ident> class do not,
however, share their pointing attributes.</note>
 
<p>The attributes shared by the members of an a-class are defined in a
parameter entity; member elements inherit the attributes by referring to
the parameter entity within their attribute-list declaration (examples
below).  This practice helps ensure that if the attribute definitions
for the class change, all members of the class will automatically
inherit the new definitions.  Parameter entities used for this purpose
form their names by taking the name of the class they define and
prefixing the string <cited>a.</cited>; we refer to these entities as
<term>a-dot entities.</term>
 
<p>For example, the declaration for the <ident type=class>names</ident>
class includes attribute definitions for its two attributes
<att>reg</att> and <att>key</att>:
 
<dtdFrag file=dummy id=DSTECX1
    n='Sample class declaration'>
<claDecl classDoc=NAMES type=atts>
</dtdFrag>
 
Members of the class typically inherit these definitions by referring to
<ident type=class>a.names</ident>:
 
<dtdFrag file=dummy id=DSTECX2
    n='Sample element declarations'>
<commDecl>The members of a class refer to its a-dot entity in their
attribute-list declaration, as shown here.</commDecl>
<tagDecl tagDoc=NAME>
</dtdFrag>
 
<p>Subclasses of a-classes inherit the attributes of their superclass
similarly, by referring to the a-dot entity of the superclass in
defining their own a-dot entity.  For example, the class <ident
type=class>xPointer</ident> is a subclass of the class <ident
type=class>pointer</ident>, as shown implicitly by the declaration of
its a-dot entity:
 
<dtdFrag file=dummy id=DSTECX3
    n='Sample subclass declaration, with inheritance from superclass'>
<claDecl classDoc=XPOINTER type=atts>
</dtdFrag>
 
(For an explanation of the parameter entity <ident
type=pe>extptr</ident> used in the above example, see section <xref
target=STPEKW>.)
 
<p>The a-classes declared in the core tag sets of these Guidelines are:
 
<!-- <note place=foot>This list includes all a-classes        -->
<!-- defined at the time this chapter was being completed;    -->
<!-- others may be added as the current draft is being        -->
<!-- completed.  -Ed.</note>                                  -->
 
<list type=gloss>
 
<label><ident type=class>declaring</ident> <item>elements which have a
<att>decls</att> attribute for specifying which declarations in the
header apply to the element, as described in section <xref target=CCAS>
 
<label><ident type=class>declarable</ident> <item>header elements
containing declarations, which can be pointed at by the <att>decls</att>
attribute, as described in section <xref target=CCAS>
 
<label><ident type=class>divn</ident> <item>structural elements which
behave in the same way as divisions, as described in section <xref
target=DSDIV>
 
<label><ident type=class>enjamb</ident> <item>elements which carry the
<att>enjamb</att> attribute for indicating metrical enjambement
 
<!-- < label > flatterm  < item > elements used in the        -->
<!-- < soCalled > flat < /soCalled >  style of terminological -->
<!-- data, which take specialized attributes for              -->
<!-- indicating logical dependencies, as described in         -->
<!-- section  < xref target=TEFLNE >                          -->
 
<label><ident type=class>interpret</ident> <item>elements which contain
overtly interpretive or extra-textual analysis or commentary on a text
or some portion of it.
 
<label><ident type=class>metrical</ident> <item>elements which carry
metrical information (metrical pattern, realization of the pattern,
rhyme)
 
<label><ident type=class>names</ident> <item>elements which contain
proper nouns and share attributes for identifying their referents and
regularizing their spelling (section <xref target=CONARS>)
 
<label><ident type=class>personPart</ident> <item>elements which contain
personal names or parts of them
 
<label><ident type=class>placePart</ident> <item>elements which contain
place names or parts of them
 
<label><ident type=class>pointer</ident> <item>elements which point from
one location in the document to another (section <xref target=COXR>)
 
<label><ident type=class>seg</ident> <item>elements for the systematic
or arbitrary segmentation of the text
 
<label><ident type=class>temporalExpr</ident> <item>elements which
contain temporal expressions
 
<label><ident type=class>timed</ident> <item>elements (in the base tag
set for spoken texts) which have a duration in time expressible with the
attributes, as described in section <xref target=TSBATI>

<label><ident type=class>typed</ident> <item>elements which carry
an additional semantic or functional classification
 
<label><ident type=class>xPointer</ident> <item>elements which point
from one location in the document to other locations within or outside
the current document (section <xref target=SAXR>)
 
</list>
 
<p>All elements are considered members of the class <ident
type=class>global</ident> and thus include a reference to <ident
type=pe>a.global;</ident> in their attribute definition list
declaration.  Some tag sets add specialized attributes to the set of
global attributes; these additions are declared in the
<soCalled>ent</soCalled> file of each tag set, using the following
entity names.  If the tag set does not define new global attributes, no
entity of this type is declared.
 
<list type=gloss>
 
<!-- <label><ident type=pe>a.spoken</ident>                   -->
<!-- <item>additional global attributes for the spoken-text   -->
<!-- base                                                     -->
 
<label><ident type=pe>a.analysis</ident> <item>additional global
attributes for the analysis tag set
 
<label><ident type=pe>a.linking</ident> <item>additional global
attributes for the linking tag set
 
<label><ident type=pe>a.terminology</ident> <item>additional global
attributes for the terminology base
 
<!-- <label><ident type=pe>a.fs</ident> <item>additional      -->
<!-- global attributes for the feature structure tag set      -->
 
<!-- <label><ident type=pe>a.certainty</ident>                -->
<!-- <item>additional global attributes for the uncertainty   -->
<!-- tag set                                                  -->
 
</list>
 
<p>These entities are included in the <ident
type=file>teiclas2.ent</ident> file indirectly, when the
entity-declaration files of each tag set are embedded, as shown below in
section <xref target=STECMK>.  For purposes of documentation, these
attributes are treated as if inherited by the class <ident
type=class>global</ident> from superclasses called
<ident type=class>terminology</ident>, etc.,
and are documented under the class name.
<!-- suppress class 'spoken' (vacuous)                        -->
 
<p>One further complication to the inheritance mechanism should be
mentioned here.  In rare cases, a member of an a-class may override the
definition of an inherited attribute.  For example, the element
<gi>anchor</gi> inherits the global <att>id</att> attribute from the
class <ident type=class>global</ident> --- as does every other element.
On <gi>anchor</gi> elements, however, <att>id</att> is not optional but
required.  The declaration of <gi>anchor</gi> therefore does not refer
to the class <ident type=class>global</ident>, but instead defines all
the inherited attributes explicitly, using its own declaration for
<att>id</att> and the default inherited declarations for the other
global attributes:
 
<dtdFrag file=dummy id=DSTECX4
    n='Sample of local declaration overriding inherited attributes'>
<commDecl>ANCHOR overrides the default ID, but uses the default
declarations for the other global attributes.</commDecl>
<tagDecl tagDoc=ANCHOR>
</dtdFrag>
 
Because this declaration does not use the parameter entity <ident
type=pe>a.global</ident>, clearly any change in the definition for that
entity will not be reflected in this declaration.  Consequently, any
changes made to the global attributes as such will not be inherited by
the <gi>anchor</gi> element.  Instead, such changes must be replicated
manually.  Care must thus be taken in modifying attribute definitions
for a-classes if any members of the class override the inherited
definitions, to ensure that all members of the class really do get the
modified definitions.
 
<dtdFrag id=DSTECAT n='Attribute classes'>
<claDecl type=atts classDoc=DECLING>
<claDecl type=atts classDoc=DECLABL>
<claDecl type=atts classDoc=DIVN>
<claDecl type=atts classDoc=ENJAMB>
<claDecl type=atts classDoc=CLINTERP>
<claDecl type=atts classDoc=METRICAL>
<claDecl type=atts classDoc=NAMES>
<claDecl type=atts classDoc=PERSPART>
<claDecl type=atts classDoc=PLACPART>
<claDecl type=atts classDoc=POINTER>
<claDecl type=atts classDoc=CLSEG>
<claDecl type=atts classDoc=TEMPEXP>
<claDecl type=atts classDoc=TIMED>
<claDecl type=atts classDoc=TYPED>
<claDecl type=atts classDoc=XPOINTER>
</dtdFrag>
<!-- claDecl type=atts classDoc=FLATTERM -->
<!-- <claDecl type=atts classDoc=PNAME>                       -->
<!-- <claDecl type=atts classDoc=PLNAME>                      -->
<!-- <claDecl type=atts classDoc=READINGS>                    -->
 
<div3 id=STECCM><head>Classes Used in Content Models</head>
 
<p>When the members of a class are structurally similar and can appear
at the same kinds of structural locations in the document, they are
grouped together into an m-class (or
<soCalled>model-class</soCalled>).  M-classes are implemented by
defining a parameter entity for use in the formal declaration of element
content models.  The parameter entity takes the name of the class it
defines, and prefixes the string <cited>m.</cited>, which can be
interpreted as <gloss>model</gloss> or as <gloss>members</gloss>.  The
replacement text of the entity is a list of the members of the class,
separated by <cited>|</cited>, the SGML symbol for alternation.
 
<p>For each class an additional entity is defined, which also takes the
name of the class, this time prefixed by the string <cited>x.</cited>
(for extension); the default value of these <term>x-dot entities</term>
is always the empty string.  A reference to the corresponding x-dot
entity is always included within the replacement string for each m-dot
entity.  This enables an encoder to add new members to a class simply by
declaring a new value for an x-dot entity.
 
<p>For example, the class <ident type=class>bibl</ident> has the three
members <gi>bibl</gi>, <gi>bibl.full</gi>, and <gi>bibl.struct</gi>.
Its content-model entity is defined thus:
 
<eg>
<![ CDATA [
 <!ENTITY % x.bibl '' >
 <!ENTITY % m.bibl '%x.bibl bibl | bibl.full | bibl.struct' >
]]>
</eg>
 
With the default value of the x-dot entity, this is the same as defining
<ident type=pe>m.bibl</ident> with the replacement text <code
type=frag>bibl | bibl.full | bibl.struct</code>.  If an encoder wishes
to add a new bibliographic element called <gi tei=no>myBib</gi>, it can
be added to the <ident type=class>bibl</ident> class by redefining the
x-dot entity thus:
 
<eg>
<![ CDATA [
 <!ENTITY % x.bibl 'myBib |' >
]]>
</eg>
 
This changes the replacement text of <ident type=pe>m.bibl</ident> from
its default value to <code type=frag>myBib | bibl | bibl.full |
bibl.struct</code>.  If more than one element is to be added to a class,
the x-dot entity for the class should be redefined as a list of the new
generic identifiers, each one <emph>(including the last)</emph> followed
by a vertical bar.  The same effect could be achieved simply by
redefining the whole of the new <ident type=pe>m.bibl</ident> entity
directly, but the x-dot method requires no repetition of the already
existing members of the class and thus minimizes the chance of error.
 
<p>Like a-classes, m-classes may have subclasses or superclasses.  Just
as elements inherit from a class the ability to appear in certain
locations of a document (wherever the class can appear), so all members
of a subclass inherit the ability to appear wherever any superclass can
appear.  Superclasses transmit their location characteristics to their
subclasses by referring, in declaring their m-dot entity, to the m-dot
entities of the subclasses.
 
<p>For example, the class <ident type=class>phrase</ident> includes the
classes <ident type=class>data</ident>, <ident type=class>edit</ident>,
<ident type=class>hqphrase</ident>, <ident type=class>loc</ident>, and
<ident type=class>seg</ident> as members, as can be seen in the
declaration for its m-dot entity:
 
<dtdFrag file=dummy id=DSTECX5
    n='Sample class declaration with inclusion of subclasses'>
<claDecl classDoc=PHRASE type=model>
</dtdFrag>
 
When the entity <ident type=pe>m.phrase</ident> is referred to in
content models, all members of all subclasses are included in the model.
 
<div3 id=STECOV><head>The TEICLAS2.ENT File</head>
 
<p>The most important element classes used in TEI content models are
declared in the DTD file <ident type=file>teiclas2.ent</ident>, which
is the default replacement text for the entity <ident
type=pe>TEI.elementClasses</ident> and is embedded by the <ident
type=file>tei2.dtd</ident> file.  These element classes are described,
and their declarations reproduced, in the following sections.
 
<p>The class system is structured around the following threefold
division of elements:
 
<list type=gloss>
<label><term>chunks</term> <item>elements such as paragraphs and other
paragraph-level elements, which can appear directly within texts or
within text subdivisions (i.e. <gi>div</gi> elements), but not within
other chunks
<label><term>phrase-level elements</term> <item>elements such as
highlighted phrases, book titles, or editorial corrections which can
occur only within chunks (paragraphs or paragraph-level elements), but
not between them (and thus cannot appear directly within a <gi>div</gi>)
<note place=foot>Note that in this context, <term>phrase</term> means
any string of characters, and can apply to individual words, parts of
words, and groups of words indifferently; it does not refer only to
linguistically motivated phrasal units.  This may cause confusion for
readers accustomed to applying the word in a more restrictive sense.
</note>
<label><term>inter-level elements</term> <item>elements such as lists,
notes, quotations, etc. which can appear either between chunks (as
children of a <gi>div</gi>) or within them
</list>
 
<p>Together the two sets of <term>chunks</term> and <term>inter-level
elements</term> make up the set of:
<list type=gloss>
<label><term>text components</term> <item>elements which can appear
directly within texts or text divisions; also called simply
<term>components</term> or <soCalled>component-level elements</soCalled>
</list>
In general, the body of any text comprises a series of components,
optionally grouped into <gi>div</gi> elements.
 
<p>Some elements belong to none of these classes; these include
high-level structural elements like <gi>tei.2</gi> and
<gi>group</gi> as well as some specialized elements which appear only
within particular structures (like <gi>analytic</gi>,
<gi>monographic</gi>, and <gi>series</gi>).  The majority of elements
found in normal running text, however, are assigned by the TEI DTDs to
one or the other of these classes.
 
<p>Some <term>component</term> elements (e.g. <gi>p</gi> or
<gi>note</gi>) are common to all base tag sets, while others are unique
to individual tag sets.  This distinction is reflected in the parameter
entity declarations, as shown below.
 
<p>The <ident type=file>teiclas2.ent</ident> file has the following
overall structure:
 
<dtdFrag id=DSTECOV
         n='Element classes for TEI DTDs'
         file='teiclas2.ent'>
&dtdstart;
 
<commDecl>First, we declare the 'low-level' core classes:  these are
classes of semantically and structurally similar elements declared as
part of the core tag set, e.g. the classes 'data' or 'edit'.
</commDecl>
 
<dtdRef dtdFrag=DSTECLO>
<dtdRef dtdFrag=DSTECMI>
 
<commDecl>Next, we declare the 'high-level' classes:  these group
together all phrase-level elements, all inter-level elements, and all
chunk-level elements in the core, and identify the 'common' component
elements (chunks and inter-level elements), as opposed to the
tagset-specific components.</commDecl>
 
<dtdRef dtdFrag=DSTECHI>
 
<commDecl>Next, we embed the portions of each base and additional tag
set which declare relevant parameter entities.  Only those files are
embedded which have been selected by the user in the DTD subset.  These
files will declare parameter entities for their component-level
elements, as well as for any global attributes they define.</commDecl>
 
<dtdRef dtdFrag=DSTECMK>
 
<commDecl>We can now declare the standard content models; one of these
varies with the base selected.</commDecl>
<dtdRef dtdFrag=DSTECST>
 
<commDecl>Finally, we declare the attribute classes, including
the global attributes.</commDecl>
<dtdRef dtdFrag=DSTECAT>
<dtdRef dtdFrag=DSTGA>
 
</dtdFrag>
 
<div3 id=STECLO><head>Low-Level Element Classes</head>
 
<p>The following low-level classes group together sets of semantically
or structurally similar elements.  These classes may include both
elements in the core and elements declared in particular tag sets; a
reference is given at least to the relevant section on the core tags.
 
<p>The following are phrase-level element classes:
 
<list type=gloss>
 
<label><ident type=class>hqphrase</ident> <item>elements for highlighted
phrases or material marked by quotation marks, including those defined
in section <xref target=COHQ>
 
<label><ident type=class>data</ident> <item>elements for recording
information about the referents of a text, including those defined in
section <xref target=CONA>
 
<label><ident type=class>date</ident> <item>elements for recording
dates, including those defined in
section <xref target=CONADA>
 
<label><ident type=class>edit</ident> <item>elements for recording
simple editorial interventions in a text, including those defined in
section <xref target=COED>
 
<label><ident type=class>loc</ident> <item>elements for recording
location information in a text, including those defined in section <xref
target=CORS>
 
<label><ident type=class>seg</ident><item>elements for marking arbitrary
segments at the level of individual characters or phrases, including
those documented in section <xref target=SASE> and <xref target=AILC>
 
<label><ident type=class>sgmlKeywords</ident><item>elements for marking
generic identifiers, attribute names, SGML tags, and sample attribute
values, when they occur in the text (used in tag set documentation, for
which see chapter <xref target=TD>)
 
<label><ident type=class>versePhrases</ident><item>phrase-level elements
specific to verse, documented in section <xref target=VESE>
 
<label><ident type=class>formPointers</ident><item>elements for
referring, within a dictionary entry, to the orthographic form or
pronunciation of the headword, documented in section <xref target=DIHW>
 
</list>
 
<p>The following are inter-level element classes:
 
<list type=gloss>
 
<label><ident type=class>hqinter</ident> <item>elements for highlighted
phrases or material marked by quotation marks, including those defined
in section <xref target=COHQ>
 
<label><ident type=class>bibl</ident> <item>elements for bibliographic
citations; see section <xref target=COBI>
 
<label><ident type=class>lists</ident> <item>elements for lists; see
section <xref target=COLI>
 
<label><ident type=class>notes</ident> <item>general-purpose annotation
elements; see section <xref target=CONO>
 
<label><ident type=class>stageDirection</ident><item>elements for
specialized stage-direction elements documented in section <xref
target=DRSTA>
 
</list>
 
<p>The following classes of elements may appear anywhere within the
<gi>text</gi> element:
 
<list type=gloss>
<label>metadata</label><item>elements which convey non-textual
information about the text (meta-information, as it were)
<label>refsys</label><item>milestone elements used in
reference systems
<label>editincl</label><item>elements marking arbitrary  spans
of text which has been added, deleted, or omitted from a transcription
</list>

These three classes together form the <ident type=class>globincl</ident>
class, comprising elements which may appear anywhere within
the <gi>text</gi> element (because the class is used in an inclusion
exception on that element).

 
<p>The entity declarations for these classes are these:
<dtdFrag id=DSTECLO n='Low-level classes'>
<commDecl>Most of these elements are in the core tag set, but
some may be from other tag sets.</commDecl>
 
<commDecl>Phrase-level classes</commDecl>
<claDecl classDoc=HQPHRASE type=model>
<claDecl classDoc=CLDATE   type=model>
<claDecl classDoc=DATA     type=model>
<claDecl classDoc=EDIT     type=model>
<claDecl classDoc=CLLOC    type=model>
<claDecl classDoc=CLSEG    type=model>
<claDecl classDoc=SGMLKW   type=model>
<claDecl classDoc=VEPHR    type=model>
<claDecl classDoc=FORMPTRS type=model>
<claDecl classDoc=METADATA type=model>
<claDecl classDoc=REFSYS   type=model>
<claDecl classDoc=EDITINCL type=model>
<claDecl classDoc=GLOBINCL type=model>
 
<commDecl>Inter-level classes</commDecl>
<claDecl classDoc=HQINTER  type=model>
<claDecl classDoc=CLBIBL   type=model>
<claDecl classDoc=LISTS    type=model>
<claDecl classDoc=NOTES    type=model>
<claDecl classDoc=STAGEDIR type=model>
</dtdFrag>
 
<div3 id=STECHI><head>High-Level Element Classes</head>
 
<p>The following element classes are used to implement the threefold
structural distinction among phrases, chunks, and intermediate elements
discussed above in section <xref target=STECOV>.  In this terminology,
<term>chunk</term>s (or <term>chunk elements</term> are elements which
can occur only in chunk-level sequences (e.g. between but not within
paragraphs); <term>inter-level elements</term> can occur either within
chunks (at phrase-level) or between chunks (e.g. at paragraph-level),
and <term>phrase-level elements</term> can occur only at phrase level,
within chunks (e.g. within but not between paragraphs).
 
<p>The element class <ident type=class>common</ident> includes all
component-level (chunk- and inter-level) elements common to more than
one base.  It is used in implementing the combined bases described in
section <xref target=STCO>.
 
<!-- in chapter <xref target=CB>.                             -->
 
<p>The relevant portion of the DTD looks like this:
<dtdFrag id=DSTECHI n='Common high-level classes'>
<commDecl>These are the three fundamental element classes.</commDecl>
<claDecl classDoc=PHRASE type=model>
<claDecl classDoc=INTER    type=model>
<claDecl classDoc=CHUNK    type=model>
 
<commDecl>This class isolates all the common
component-level elements.</commDecl>
<claDecl classDoc=COMMON   type=model>
</dtdFrag>
 
<div3 id=STECMK><head>Elements Marked for Text Type</head>
 
<p>The following element classes are used to group together
component-level elements which are allowed only in texts of a particular
type (i.e. texts using a specific base).
 
<list type=gloss>
 
<label><ident type=class>comp.verse</ident> <item>elements unique to
verse
 
<label><ident type=class>comp.drama</ident> <item>elements unique to
drama
 
<label><ident type=class>comp.spoken</ident> <item>elements unique to
spoken texts
 
<!-- <label><ident type=class>comp.letters</ident>            -->
<!-- <item>elements unique to letters and memoranda           -->
 
<label><ident type=class>comp.dictionaries</ident> <item>elements unique
to dictionaries
 
<label><ident type=class>comp.terminology</ident> <item>elements unique
to terminological data
 
</list>
 
<p>Declarations for these base-specific element classes are included in
the <term>entity file</term> of each base, which is in turn embedded by
the <ident type=file>teiclas2.dtd</ident> file in the DTD fragment shown
below.  If the tag set defines additions to the set of global
attributes, or declares a class of component-level elements unique to
the tag set, then it has an entity file which is embedded here;
otherwise not.
 
<dtdFrag id=DSTECMK
         n='Embedding tag-set-specific entity definitions'>
 
<msection keywords='%TEI.verse'>
<entDecl entDoc=VEENT>
<peRef n='TEI.verse.ent'>
</msection>
 
<msection keywords='%TEI.drama'>
<entDecl entDoc=DRENT>
<peRef n='TEI.drama.ent'>
</msection>
 
<msection keywords='%TEI.spoken'>
<entDecl entDoc=TSENT>
<peRef n='TEI.spoken.ent'>
</msection>
 
<msection keywords='%TEI.dictionaries'>
<entDecl entDoc=DIENT>
<peRef n='TEI.dictionaries.ent'>
</msection>
 
<msection keywords='%TEI.terminology'>
<entDecl entDoc=TEENT>
<peRef n='TEI.terminology.ent'>
</msection>
 
<msection keywords='%TEI.linking'>
<entDecl entDoc=SAENT>
<peRef n='TEI.linking.ent'>
</msection>
 
<msection keywords='%TEI.analysis'>
<entDecl entDoc=AIENT>
<peRef n='TEI.analysis.ent'>
</msection>
 
<msection keywords='%TEI.transcr'>
<entDecl entDoc=PHENT>
<peRef n='TEI.transcr.ent'>
</msection>
 
<msection keywords='%TEI.textcrit'>
<entDecl entDoc=TCENT>
<peRef n='TEI.textcrit.ent'>
</msection>
 
<msection keywords='%TEI.names.dates'>
<entDecl entDoc=NDENT>
<peRef n='TEI.names.dates.ent'>
</msection>
 
<msection keywords='%TEI.figures'>
<entDecl entDoc=FTENT>
<peRef n='TEI.figures.ent'>
</msection>
 
</dtdFrag>
 
<!-- <msection keywords='%TEI.letters'>                       -->
<!-- <entDecl entDoc=LMENT>                                   -->
<!-- <peRef n='TEI.letters.ent'>                              -->
<!-- </msection>                                              -->
<!-- <msection keywords='%TEI.fs'>                            -->
<!-- <entDecl entDoc=FSENT>                                   -->
<!-- <peRef n='TEI.fs.ent'>                                   -->
<!-- </msection>                                              -->
 
<div3 id=STECST><head>Standard Content Models</head>
 
<p>As far as possible, the TEI DTDs use the following set of
frequently-encountered content models, to help achieve consistency among
different elements.
 
<list type=gloss>
 
<label><ident type=pe>phrase</ident> <item>a single sequence of
character data or single phrase-level element
 
<label><ident type=pe>phrase.seq</ident> <item>sequence of character
data and phrase-level elements
 
<label><ident type=pe>component</ident> <item>a single chunk- or
inter-level element
 
<label><ident type=pe>component.seq</ident> <item>sequence of chunk- and
inter-level elements; this is the usual content of a <gi>div</gi>
element
 
<label><ident type=pe>paraContent</ident> <item>sequence of character
data, phrase-level elements, and inter-level elements; this is the usual
content of chunks (including, most prominently, paragraphs)
 
<label><ident type=pe>specialPara</ident> <item>specialized content
model, allowing <emph>either</emph> a sequence of chunks <emph>or</emph>
the same content as <ident type=pe>paraContent</ident>; this is used for
elements such as notes and list items, which can behave either as
chunk-level elements, or else as containers for groups of
component-level elements.
 
</list>
 
<p>The relevant portion of the DTD looks like this:
 
<dtdFrag id=DSTECST n='Standard Content Models'>
 
<commDecl>Here we declare the parameter entities phrase, phrase.seq,
component, component.seq, paraContent, and specialPara, for use in the
content models of element declarations.</commDecl>
 
<commDecl>The entities phrase and phrase.seq are the same in all bases.
They may include elements specific to single tag sets; if the tag set is
not selected, these elements are undefined and have no effect.</commDecl>
 
<entDecl entDoc=PEPHRASE>
<entDecl entDoc=PHRSEQ>
 
<commDecl>The entity component varies with the base.  The
versions for the combined bases are declared first (so as to
take precedence over the declarations in the individual
bases).</commDecl>
 
<dtdRef dtdFrag=DSTECMX>
 
<msection keywords='%TEI.prose'>
<entDecl entDoc=PRCOMP>
<entDecl entDoc=MIXNO>
</msection>
 
<msection keywords='%TEI.verse'>
<entDecl entDoc=VECOMP>
<entDecl entDoc=MIXNO>
</msection>
 
<msection keywords='%TEI.drama'>
<entDecl entDoc=DRCOMP>
<entDecl entDoc=MIXNO>
</msection>
 
<msection keywords='%TEI.spoken'>
<entDecl entDoc=TSCOMP>
<entDecl entDoc=MIXNO>
</msection>
 
<msection keywords='%TEI.dictionaries'>
<entDecl entDoc=DICOMP>
<entDecl entDoc=MIXNO>
</msection>
 
<msection keywords='%TEI.terminology'>
<entDecl entDoc=TECOMP>
<entDecl entDoc=MIXNO>
</msection>
 
<commDecl>Default declaration.</commDecl>
<entDecl entDoc=PRCOMP>
<entDecl entDoc=MIXNO>
 
<commDecl>The entity component.seq is always a starred sequence of
component elements.  Its definition does not vary with the base (unless
we are using the general base, in which case it has already been defined
above), but the meaning of the definition does.</commDecl>
<entDecl entDoc=COMPSEQ>
 
<commDecl>The following entities do not vary with the base.</commDecl>
<entDecl entDoc=PEPARAC>
<entDecl entDoc=PESPECP>
</dtdFrag>
 
<!-- <msection keywords='%TEI.letters'>                       -->
<!-- <entDecl entDoc=LMCOMP>                                  -->
<!-- </msection>                                              -->
 
 
<div3 id=STECMX><head>Components in Mixed and General Bases</head>
 
<p>When the mixed or general base is in use, the definitions of the
entities <ident type=pe>component</ident> and
<ident type=pe>component.seq</ident> are rather more complex.
The relevant portion of the DTD is this:
 
<dtdFrag id=DSTECMX n='Definition of components for combined bases'>
 
<commDecl>Default declarations for the 'mix.' entities used for mixed
and general bases.</commDecl>
<entDecl entDoc=VEMIXXX>
<entDecl entDoc=DRMIXXX>
<entDecl entDoc=TSMIXXX>
<entDecl entDoc=DIMIXXX>
<entDecl entDoc=TEMIXXX>
<msection keywords='%TEI.mixed'>
<entDecl entDoc=MIXYES>
<commDecl>The mixed base allows components from any base; it does so by
defining 'component' as including both common components and those
specific to one tag set.</commDecl>
<entDecl entDoc=CBCOMP>
</msection>
 
<msection keywords='%TEI.general'>
<commDecl>The general base uses the same definition of component as the
mixed base.</commDecl>
<entDecl entDoc=MIXYES>
<entDecl entDoc=CBCOMP>
<commDecl>But it defines a special version of component.seq, which
restricts each div of the text to a single base:  bases can shift only
in embedded divs or at div boundaries.  This entity is constructed out
of a series of smaller entities, one for each tag set.  If the tag set
is not in use, its entity will expand to the empty string.
</commDecl>
 
<msection keywords='%TEI.verse'>
<commDecl>If the verse base is in use, ...</commDecl>
<entDecl entDoc=VEGEN>
</msection>
 
<msection keywords='%TEI.drama'>
<commDecl>If the drama base is in use, ...</commDecl>
<entDecl entDoc=DRGEN>
</msection>
 
<msection keywords='%TEI.spoken'>
<commDecl>If the spoken base is in use, ...</commDecl>
<entDecl entDoc=TSGEN>
</msection>
 
<msection keywords='%TEI.dictionaries'>
<commDecl>If the dictionary base is in use, ...</commDecl>
<entDecl entDoc=DIGEN>
</msection>
 
<msection keywords='%TEI.terminology'>
<commDecl>If the terminology base is in use, ...</commDecl>
<entDecl entDoc=TEGEN>
</msection>
 
<commDecl>Default declarations for all the entities gen.verse,
etc.</commDecl>
<entDecl entDoc=VEGENXX>
<entDecl entDoc=DRGENXX>
<entDecl entDoc=TSGENXX>
<entDecl entDoc=DIGENXX>
<entDecl entDoc=TEGENXX>
 
<commDecl>Now we are ready to declare component.seq and
component.plus for use in general base tag set.</commDecl>
<entDecl entDoc=CBGESEQ>
<entDecl entDoc=CBGEPLUS>
 
<commDecl>(End of marked section for general base.)</commDecl>
</msection>
 
</dtdFrag>
 
<!-- <msection keywords='%TEI.letters'>                       -->
<!-- <commDecl>If the letters base is in use, ...</commDecl>  -->
<!-- <entDecl entDoc=LMGEN>                                   -->
<!-- </msection>                                              -->
 
<!-- <entDecl entDoc=LMGENXX>                                 -->
 
<div3 id=STECMI><head>Miscellaneous Content-Model Classes</head>
 
<p>The following element classes occupy specific places in content
models; some are relevant only when certain tag sets are selected
 
<list type=gloss>
 
<label><ident type=class>agent</ident> <item>elements which denote an
individual or organization to whom or which responsibility for an action
can be assigned
 
<label><ident type=class>addrPart</ident> <item>elements which can occur
as part of an address
 
<label><ident type=class>biblPart</ident> <item>elements which can occur
in bibliographic citations
 
<label><ident type=class>demographic</ident> <item>elements which record
demographic characteristics of the participants in a text or language
interaction (used in tag set for corpora and collections)
 
<label><ident type=class>divbot</ident> <item>elements which can occur
as part of the closing material of a text division or body
 
<label><ident type=class>divtop</ident> <item>elements which can occur
as part of the opening material of a text division or body
 
<label><ident type=class>dramafront</ident> <item>elements which can
occur in the front matter of drama and other performance texts
 
<label><ident type=class>front</ident> <item>elements which can occur
(at the level of text divisions) in front matter only
 
<label><ident type=class>personPart</ident> <item>elements which contain
parts of a personal name
 
<label><ident type=class>placePart</ident> <item>elements which contain
parts of a place name
 
<label><ident type=class>tpParts</ident> <item>elements which occur
within title pages

<label><ident type=class>fmchunk</ident> <item>elements which can
occur in place of a title page in front matter only

 
</list>
 
<p>They are declared in the following DTD fragment:
 
<dtdFrag id=DSTECMI n='Misc. Element Class Models'>
<claDecl classDoc=AGENT    type=model>
<claDecl classDoc=ADDRPART type=model>
<claDecl classDoc=BIBLPART type=model>
<claDecl classDoc=DEMOG    type=model>
<claDecl classDoc=DIVBOT   type=model>
<claDecl classDoc=DIVTOP   type=model>
<claDecl classDoc=DRFRONT  type=model>
<claDecl classDoc=CLFRONT  type=model>
<claDecl classDoc=PERSPART type=model>
<claDecl classDoc=PLACPART type=model>
<claDecl classDoc=TPPARTS  type=model>
<claDecl classDoc=FMCHUNK  type=model>
</dtdFrag>
 
<!-- < note place=inline > [CO says  < gi > lb < /gi >  and   -->
<!-- < gi > pb < /gi >  are part of class loc, not of class   -->
<!-- refsys.  Is this an error?  Should they be moved to      -->
<!-- loc? -MSM] < /note > I believe this is an error. (LB)    -->
<!-- ... and have duly moved them to refsys -->
<?tei:EOF p2stec.odd ?>
