<?tei:SOF p2stba.odd ?>
<!-- $Id: p2stba.odd,v 1.4 1994/04/08 18:54:36 msmcq Exp $ -->
<!-- $Log: p2stba.odd,v $
# Revision 1.4  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.3  1994/04/08  01:36:34  msmcq
# Last-round changes before publication of P3
#
# Revision 1.2  1994/03/24  22:20:40  msmcq
# typos found by David Barnard et al. corrected
# -->
<!-- P2STba: Base Tag Sets and Additional Tag Sets            -->
<!-- was:  P2.132                                             -->
<!-- Revisions:                                               -->
<!-- 94-04-08 : MSM : fix typo / invalid tag                  -->
<!-- 94-04-07 : MSM : typos from MSM                          -->
<!-- 94-03-22 : MSM : typos from DB, JLav, EBr                -->
<!-- 94-03-22 : MSM : retag some TERMs, Qs, as CODE, IDENT    -->
<!-- 94-03-21 : MSM : typos and stylistic changes from WWP    -->
<!--                  team, to whom thanks                    -->
<!-- 93-04-06 : MSM : cosmetic, stylistic, and one typo fixed -->
<!-- 3 apr 93 : LB revise for publication                     -->
<!--  further revamping for clarity  -->
<!-- 93-03-30 : MSM : late changes before giving to LB        -->
<!-- 93-03-29 : MSM : correct ref:  AH to CC                  -->
<!-- 93-03-16 : MSM : revamp for clarity:                     -->
<!--                  list all tagset-related entities        -->
<!--                  include and list only used entities     -->
<!--                  add sec on user-defined tag sets        -->
<!--                    (despite its effect on clarity!)      -->
<!-- 93-03-06 : MSM : minor stylistic changes for clarity     -->
<!-- 93-03-06 : MSM : some additions for completeness         -->
<!-- 93-03-04 : MSM : change lists to type=gloss              -->
<!-- 93-03-01 : MSM : vicious shortening of intro (to 115)    -->
<!-- 93-02-02 : MSM : add marked section mechanism            -->
<!-- 93-02-02 : MSM : merge PC and VM versions                -->
<!-- 93-02-01 : MSM : revision, add detail                    -->
<!-- 93-01-27 : MSM : add more DTD fragments                  -->
<!-- 25 Jan 93 : CMSMcQ : revise, fill out a bit.             -->
<!-- 21 Oct 92 : CMSMcQ : new name new id, add mix, gen       -->
<!-- 26 May 92 : CMSMcQ : add file names                      -->
<!-- 26 May 92 : CMSMcQ : draft prose (begin)                 -->
<!-- 17 May 92 : CMSMcQ : began draft (outline)               -->
 
<div2 id=STBA><head>Core, Base, and Additional Tag Sets</head>
 
<!-- definition of base and additional                        -->
<!-- arbitrary combination of additionals                     -->
<!-- list of each type in this draft (sec. 3, 4)              -->
<!-- 'core' tags an 'additional' set you get free             -->
<!-- how you specify which base and which toppings?           -->
<!--         see invocations...                               -->
 
<p>The main TEI DTD is constructed by selecting an appropriate
combination of smaller tag sets, each containing some set of tags likely
to be used together.  These building blocks include:
 
<list type=gloss>
 
<label><term>core tag sets</term> <item>standard components of the TEI
main DTD in all its forms; these are always included without any special
action by the encoder;
 
<label><term>base tag sets</term> <item>basic
building blocks for specific text types; exactly one base must be
selected by the encoder (unless one of the <soCalled>combined</soCalled>
bases is used);
 
<label><term>additional tag sets</term> <item>extra
tags useful for particular purposes. All additional tag sets are
compatible with all bases and with each other; an encoder may therefore
add them to the selected base in any combination desired.
 
</list>
 
Each tag set is contained in one or more system files, which are
defined by appropriate SGML <term>parameter entity declarations</term>
and invoked as a unit by appropriate SGML
<term>parameter entity references</term>.
<note>A <term>parameter entity</term> is an SGML entity used only in
markup declarations; references to parameter entities are delimited by a
percent sign and a semicolon rather than the ampersand and colon used
for <term>general entity</term> references.  The entity <ident
type=pe>TEI.core.ent</ident>, for example, would be referred to using
the string <code>%TEI.core.ent;</code>.  Parameter entities can also be
used to control the inclusion or exclusion of <term>marked
sections</term> of the document or DTD; the &tei; DTD uses marked
sections to handle the selection of different base and additional tag
sets.</note>
Several such declarations may be needed to invoke all parts of a given
tag set, since as well as defining elements or attributes, a tag set may
(for example) add new items to the set of global attributes or add
classes to the system of element classes.  Consistent naming principles
are applied throughout the TEI scheme for these and other entities.
Thus, assuming a tag set named <ident type=class
rend=noindex>xxx</ident>, the following parameter entities may be
encountered:
 
<list type=gloss>
 
<label>TEI.xxx <item>used to enable or disable tag set <ident type=class
rend=noindex>xxx</ident>; must have the value <code
type=kw>INCLUDE</code> (tag set is enabled) or, by default, <code
type=kw>IGNORE</code> (tag set not enabled).
 
<label>TEI.xxx.ent <item>refers to a system file containing any
parameter entity declarations unique to tag set <ident type=class
rend=noindex>xxx</ident>.
 
<label>TEI.xxx.dtd <item>refers to a system file containing the element
and attribute list declarations for tag set <ident type=class
rend=noindex>xxx</ident>.
 
<label>a.xxx <item>contains definitions of attributes which are to be
added to the set of global attributes when tag set <ident type=class
rend=noindex>xxx</ident> is enabled.
 
<label>m.comp.xxx <item>if <ident type=class rend=noindex>xxx</ident> is
a base tag set, this contains a list of any component-level elements
unique to it (for a definition of component-level elements, see section
<xref target=STEC>).
 
<label>mix.xxx <item>a special entity for use in defining the set of
component-level elements when the mixed base tag set is in use.
 
<label>gen.xxx <item>a special entity for use in defining the set of
component-level elements when the general base tag set is in use.
 
<!--  < label > tagset.seq  < item > contains a list of all   -->
<!-- chunk- and inter-level elements legal in a base tag      -->
<!-- set (both those unique to it, and those defined in the   -->
<!-- core)                                                    -->
 
</list>
 
Few tag sets declare all of these entities; only those actually used are
declared.
 
<p>The interpretation of the parameter entity declarations, and the
inclusion of the appropriate tag sets, are handled by a single
<soCalled>driver file</soCalled> for the main TEI DTD.  This file,
<ident type=file>tei2.dtd</ident>, is described in detail below in
section <xref target=STOV>.  The remainder of the present section
identifies the files in which each tag set is contained, and the
parameter entities associated with them.
 
<div3 id=STBACO><head>The Core Tag Sets</head>
 
<p>Two <soCalled>core</soCalled> tag sets are always included in every
invocation of the main TEI DTD.  The tags and attributes that they
contain are therefore available to any TEI document.  The parameter
entities used for this purpose, and the files they refer to, are:
 
<list type=gloss>
 
<label><ident type=pe>TEI.core.dtd</ident> <item>refers to the file
<ident type=file>teicore2.dtd</ident>, which declares the core tags
defined in chapter <xref target=CO>
 
<label><ident type=pe>TEI.header.dtd</ident> <item>refers to the file
<ident type=file>teihdr2.dtd</ident>, which declares the tags of the TEI
header defined in chapter <xref target=HD>
 
</list>
 
Together with these tag sets, part II also documents a tag set for
default text structure and front and back matter.  This tag set is
embedded by the base tag set selected, and may vary with the base; it is
therefore described in the next section.
 
<div3 id=STBABA><head>The Base Tag Sets</head>
 
<p>The base tag sets are those which define the basic building blocks of
different text types.  The basic structures of verse (line, stanza,
canto, etc.), for example, are not those of prose (paragraph, section,
chapter, etc.), while dictionaries use yet another set of basic
structures.  Each base corresponds to one chapter of Part III of this
document.
 
<p>In general, exactly one base tag set must be selected for any
TEI-conformant document.  Errors will result if none, or more than one,
is selected, because the same elements may be differently defined in
different base tag sets.  For documents which mingle structurally
dissimilar elements and require elements from more than one base,
however, either the <term>mixed base</term> or the <term>general
base</term> may be used; see section <xref target=STCO>.
 
<!-- see chapter <xref target=CB>.                            -->
 
These bases require the encoder to specify which of the other bases are
to be combined.
 
<p>The encoder selects a base tag set by declaring the appropriate SGML
parameter entity with the replacement text <code type=kw>INCLUDE</code>.
To invoke the base tag set for prose, for example, the encoder must
ensure that the DTD subset in the document contains the declaration:
 
<eg>
<![ CDATA [
 <!ENTITY % TEI.prose 'INCLUDE' >
]]>
</eg>
 
<p>The entities used to select the different base tag sets, and the
files containing the SGML declarations for each base, are listed below.
 
<list type=gloss>
 
<label><ident type=pe>TEI.prose</ident> <item>selects the base tag set
for prose, contained in <ident type=file>teipros2.dtd</ident>.
 
<!-- and < term >teipros2.ent< /term >                        -->
 
<label><ident type=pe>TEI.verse</ident> <item>selects the base tag set
for verse, contained in <ident type=file>teivers2.dtd</ident> and
<ident type=file>teivers2.ent</ident>.
 
<label><ident type=pe>TEI.drama</ident> <item>selects the base tag set
for drama, contained in <ident type=file>teidram2.dtd</ident> and <ident
type=file>teidram2.ent</ident>.
 
<label><ident type=pe>TEI.spoken</ident> <item>selects the base tag set
for transcriptions of spoken texts, contained in
<ident type=file>teispok2.dtd</ident> and
<ident type=file>teispok2.ent</ident>.
 
<!-- <label><ident type=pe>TEI.letters</ident> <item>selects  -->
<!-- the base tag set for letters and memos, contained in     -->
<!-- <ident type=file>teilett2.dtd</ident> and <ident         -->
<!-- type=file>teilett2.ent</ident>                           -->
 
<label><ident type=pe>TEI.dictionaries</ident> <item>selects the base
tag set for print dictionaries, contained in
<ident type=file>teidict2.dtd</ident> and
<ident type=file>teidict2.ent</ident>.
 
<label><ident type=pe>TEI.terminology</ident> <item>selects the base tag
set for terminological data files, contained in
<ident type=file>teiterm2.dtd</ident>,
<ident type=file>teiterm2.ent</ident>,
<ident type=file>teite2n.dtd</ident>, and
<ident type=file>teite2f.ent</ident>.
 
<label><ident type=pe>TEI.general</ident> <item>selects the generic
mixed-mode base base tag set, contained in
<ident type=file>teigen2.dtd</ident>.
 
<!-- and < term >teigen2.ent< /term >                         -->
 
<label><ident type=pe>TEI.mixed</ident> <item>selects the base tag set
for free mixed-mode texts, contained in
<ident type=file>teimix2.dtd</ident>.
 
<!-- and < term >teimix2.ent< /term >                         -->
 
</list>
 
<p>As shown in the list, each base tag set is normally contained in one
or two system files:  a required one (with the extension
<cited>dtd</cited>) defining the elements in the tag set and their
attributes, and an optional one (with the file extension
<cited>ent</cited>) defining any global attributes or specialized
element classes enabled by that tag set.  The parameter entities for
these files have the same name as the enabling parameter entity for the
base, with the suffixes <cited>ent</cited> and <cited>dtd</cited>
respectively:  the prose base, for example, is enabled by declaring the
parameter entity <ident type=pe>TEI.prose</ident> as <code
type=kw>INCLUDE</code>; this in turn enables declarations of <ident
type=pe>TEI.prose.ent</ident> and <ident type=pe>TEI.prose.dtd</ident>
as the system files <ident type=file>teipros2.ent</ident> and
<ident type=file>teipros2.dtd</ident>.  For further details, see
section <xref target=STOV>.
 
<!-- cut, because too detailed for this overview (LB) -->
 
<!-- < p > The base tag set for terminology defines two       -->
<!-- styles of tagging for terminological data, the  <        -->
<!-- soCalled > flat < /soCalled >  and the < soCalled >      -->
<!-- nested < /soCalled > .  As described further in          -->
<!-- chapter  < xref target=TE > , the choice between these   -->
<!-- is indicated by the definition of the parameter entity   -->
<!-- < term > termtags < /term > :                            -->
<!--                                                          -->
<!--  < list type=gloss >                                     -->
<!--  < label >  < term > termtags < /term >   < item >       -->
<!-- selects either the nested form for terminological data   -->
<!-- files ( < term > teite2n.dtd < /term > ) or the flat     -->
<!-- form ( < term > teite2f.dtd < /term > )                  -->
<!--  < /list >                                               -->
 
<p>Most base tag sets (but not necessarily all) embed common definitions
of text structure, front matter, and back matter, by referring to three
standard parameter entities; these are:
 
<list type=gloss>
 
<label><ident type=pe>TEI.structure.dtd</ident> <item>refers to the file
<ident type=file>teistr2.dtd</ident>, with default definitions for
<gi>text</gi>, <gi>div</gi>, etc.
 
<label><ident type=pe>TEI.front.dtd</ident> <item>refers to the file
<ident type=file>teifron2.dtd</ident>, with tags for front matter
 
<label><ident type=pe>TEI.back.dtd</ident> <item>refers to the file
<ident type=file>teiback2.dtd</ident>, with tags for back matter
 
</list>
 
These default-structure tags are documented in chapter <xref target=DS>.
 
<div3 id=STBAAD><head>The Additional Tag Sets</head>
 
<p>The additional tag sets define optional tags required by different
encoders for different types of analysis and processing; each
corresponds to a chapter in part IV of this document.  In any TEI
encoding, any or all of these additional tag sets may be made available,
as they are all compatible with each other and with every base tag set.
They are invoked in the same way as base tag sets, by defining the
appropriate parameter entity as <code type=kw>INCLUDE</code>; the
relevant parameter entities, and the files containing the additional tag
sets, are these:
 
<list type=gloss>
 
<label><ident type=pe>TEI.linking</ident> <item>embeds the files
<ident type=file>teilink2.dtd</ident> and
<ident type=file>teilink2.ent</ident>, with tags for linking,
segmentation, and alignment (chapter <xref target=SA>)
 
<label><ident type=pe>TEI.analysis</ident> <item>embeds the files
<ident type=file>teiana2.dtd</ident> and
<ident type=file>teiana2.ent</ident>,
with tags for simple analytic mechanisms (chapter <xref target=AI>)
 
<label><ident type=pe>TEI.fs</ident> <item>embeds the file
<ident type=file>teifs2.dtd</ident>,
with tags for feature structure analysis (chapter <xref target=FS>)
 
<label><ident type=pe>TEI.certainty</ident> <item>embeds the file
<ident type=file>teicert2.dtd</ident>,
with tags for indicating uncertainty and
probability in the markup (chapter <xref target=CE>)
 
<label><ident type=pe>TEI.transcr</ident> <item>embeds the files
<ident type=file>teitran2.dtd</ident> and
<ident type=file>teitran2.ent</ident>,
with tags for manuscripts, analytic bibliography, and transcription of
primary sources (chapter <xref target=PH>)
 
<label><ident type=pe>TEI.textcrit</ident> <item>embeds the files
<ident type=file>teitc2.dtd</ident> and
<ident type=file>teitc2.ent</ident>,
with tags for critical editions (chapter <xref target=TC>)
 
<label><ident type=pe>TEI.names.dates</ident> <item>embeds the files
<ident type=file>teind2.dtd</ident> and
<ident type=file>teind2.ent</ident>,
with specialized tags for names and dates (chapter <xref target=ND>)
 
<label><ident type=pe>TEI.nets</ident> <item>embeds the file <ident
type=file>teinet2.dtd</ident>, with tags for graphs, digraphs, trees,
and other networks (chapter <xref target=GD>) --- not to be confused
with the graphics markup of <ident type=pe>TEI.figures</ident>
 
<label><ident type=pe>TEI.figures</ident> <item>embeds the files
<ident type=file>teifig2.dtd</ident> and
<ident type=file>teifig2.ent</ident>,
with tags for graphics, figures,
illustrations, tables, and formulae (chapter <xref target=FT>) --- not
to be confused with the graph-theoretic markup of <ident
type=pe>TEI.nets</ident>
 
<!-- <label><ident type=pe>TEI.formulas</ident> <item>embeds  -->
<!-- the file <ident type=file>teiform2.dtd</ident>, with     -->
<!-- tags for formul&aelig; and tables (chapter <xref         -->
<!-- target=FT>)                                              -->
 
<label><ident type=pe>TEI.corpus</ident> <item>embeds the file <ident
type=file>teicorp2.dtd</ident>, with tags for additional tags for
language corpora (chapter <xref target=CC>)
 
</list>
 
<p>Like the base tag sets, the additional tag sets are each contained in
one or two system files:  a required one (with the file extension
<cited>dtd</cited>) defining the elements in the tag set and their
attributes, and an optional one (with the file extension
<cited>ent</cited>) defining any global attributes or specialized
element classes enabled by that tag set.  The parameter entities for
these files have the same name as the enabling parameter entity for the
tag set, with the suffixes <cited>ent</cited> and <cited>dtd</cited>
respectively:  the additional tag set for linking, segmentation, and
alignment, for example, is enabled by declaring the parameter entity
<ident type=pe>TEI.linking</ident> as <code type=kw>INCLUDE</code>;
this in turn
enables declarations of <ident type=pe>TEI.linking.ent</ident> and
<ident type=pe>TEI.linking.dtd</ident> as the system files
<ident type=file>teilink2.ent</ident> and
<ident type=file>teilink2.dtd</ident>.
 
<div3 id=STBAUS><head>User-Defined Tag Sets</head>
 
<p>As described in chapter <xref target=MD>, users may modify the markup
language defined here by renaming elements, suppressing elements, adding
new elements, or modifying element or attribute-list declarations.  In
general, local modifications will be most conveniently grouped into two
files:  one containing the local modifications to parameter entities
used in the DTDs, and the other containing new or modified
declarations of elements and their attributes.  These files will be
embedded in the TEI DTD if they are associated with the following two
parameter entities:
 
<list type=gloss>
<label><ident type=pe>TEI.extensions.ent</ident>
<item>local modifications to parameter entities
<label><ident type=pe>TEI.extensions.dtd</ident>
<item>declarations of new elements and modified
declarations for existing elements
</list>
 
<p>In some cases, users may wish to provide completely new base or
additional tag sets, to be invoked in the same way as those defined in
this document; such tag sets should also be divided into
<soCalled>entity files</soCalled> and <soCalled>DTD files</soCalled> in
the same way as the standard tag sets.  Such modifications should be
undertaken only with a thorough understanding of the interface among
core, base, and additional tag sets as documented in the final sections
of this chapter; see in particular section <xref target=STOVLO>.
 
<p>Further recommendations for the creation of user-defined extension or
modification are provided in chapters <xref target=MD> and <xref
target=CF>.
 
<!-- cut following scarey stuff -->
 
<!-- The notes which follow may be of interest to those       -->
<!-- undertaking this task, but do not constitute a guide     -->
<!-- to the process.  Other readers should ignore them.       -->
<!--                                                          -->
<!-- < p > If locally defined base or additional tag sets     -->
<!-- are to be used, local driver files must be constructed   -->
<!-- to define the necessary parameter entities and perform   -->
<!-- the selection of the local tag sets; they must be        -->
<!-- associated with the parameter entities  < term >         -->
<!-- TEI.extensions.ent < /term > and  < term >               -->
<!-- TEI.extensions.dtd < /term > , and should be modeled     -->
<!-- on the appropriate sections of the  < term > tei2.dtd    -->
<!-- < /term >  file described in section  < xref             -->
<!-- target=STOV > .  Since the standard TEI extension        -->
<!-- mechanisms are thus in use, users of such a locally      -->
<!-- extended scheme will not be able to use them for         -->
<!-- extensions unique to a document.  It is a good idea to   -->
<!-- implement a  < soCalled > second-level < /soCalled >     -->
<!-- extension mechanism, to allow the extended local         -->
<!-- scheme to support further extensions; this               -->
<!-- second-level scheme may be modeled on the first-level    -->
<!-- scheme found in < term > tei2.dtd < /term > . < note     -->
<!-- place=foot > Local bases and additional tag sets may     -->
<!-- be more simply implemented by modifying the < term >     -->
<!-- tei2.dtd < /term >  file to refer to them.   < emph >    -->
<!-- Such modifications are not, however, TEI conformant. <   -->
<!-- /emph >  < /note >                                       -->
<?tei:EOF p2stba.odd ?>
