<?xml version="1.0"?>
<?tei:SOF p2.odd ??><TEI.1><header><filDescr><citation>Association for Computers in the Humanities (ACH),
Association for Linguistic Computing (ACL),
Association for Literary and Linguistic Computing (ALLC).
<title>Guidelines for Machine-Readable Text Encoding and
Interchange.</title>
Version 2.
Chicago, Oxford:  Text Encoding Initiative, 1992.</citation><source><citation>No source; created in m-r form.</citation></source></filDescr><revHist><list type="simple"><item>21 Dec 93 : LB : revised for P3</item><item>28 Dec 91 : MSM : Made this driver file.</item></list></revHist></header><text><front><?tei:SOF p2tp.odd ??><!-- Revisions:                                               --><!-- 93-02-10 : MSM : made Odd file from Script file          --><!-- P2.tp:  title page for TEI P2                            --><tPage><tp.part>The Association for Computers and the Humanities (ACH)</tp.part><tp.part>The Association for Computational Linguistics (ACL)</tp.part><tp.part>The Association for Literary and Linguistic Computing (ALLC)
.sp 5 a</tp.part><tp.title n="TEI P2, Partial Draft">Guidelines for Electronic</tp.title><tp.title>Text Encoding and Interchange
 </tp.title><tp.auth n="Edited by">C. M. Sperberg-McQueen and Lou Burnard
 </tp.auth><tp.part>TEI P2, Partial Draft
Text Encoding Initiative
Chicago, Oxford</tp.part><tp.part>Copyright (c) 1990, 1992 ACH, ACL, ALLC</tp.part><tp.date>10 February 1993</tp.date></tPage><?tei:EOF p2tp.odd ??><?tei:SOF p2pref.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2pref.odd,v $
# Revision 1.2  1994/04/01  16:31:21  msmcq
# new text from NI, tagged by LB
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : new version from NI, tagged by LB       --><!-- 94-03-31 : MSM : restore credit to Ohio State            --><!-- 93-02-10 : MSM : add text                                --><!-- 93-02-10 : MSM : made file                               --><!-- P2pf.odd:  Preface to TEI P2.  --><!-- dummy file made 10 Feb 93 --><!-- Revisions:                                               --><!--  9 Dec 92 : MSM : add acks to univs and s/w vendors      --><!-- 18 May 92 : MSM : add financial acknowledgements         --><!-- 23 Apr 92 : MSM : correct typos, some further revisions  --><!-- 23 Apr 92 : LB : suggested rewrites                      --><!-- 22 Apr 92 : MSM : drafted                                --><div1 name="Preface" ref="Y"><head>Preface</head><!-- Revisions:                                               --><!-- 15 Mar 94: LB : junk everything except last para and     --><!--            add material from NI final draft of 10 Mar 94 --><!-- 93-02-10 : MSM : add text                                --><!-- 93-02-10 : MSM : made file                               --><!-- P2pf.odd:  Preface to TEI P2.  --><!-- dummy file made 10 Feb 93 --><!-- Revisions:                                               --><!--  9 Dec 92 : MSM : add acks to univs and s/w vendors      --><!-- 18 May 92 : MSM : add financial acknowledgements         --><!-- 23 Apr 92 : MSM : correct typos, some further revisions  --><!-- 23 Apr 92 : LB : suggested rewrites                      --><!-- 22 Apr 92 : MSM : drafted                                --></div1><div1 id="PF" name="Preface" ref="Y"><head>Note</head><p>These Guidelines are the result of over five years' effort by
members of the research and academic community within the
framework of an international cooperative project called the Text
Encoding Initiative (TEI), established in 1987 under the joint
sponsorship of the Association for Computers and the Humanities,
the Association for Computational Linguistics, and the Association
for Literary and Linguistic Computing.
 </p><p>The impetus for the project came from the humanities computing
community, which sought a common encoding scheme for complex textual
structures in order to reduce the diversity of existing encoding
practices, simplify processing by machine, and encourage the sharing of
electronic texts. It soon became apparent that a sufficiently flexible
scheme could provide solutions for text encoding problems generally. The
scope of the TEI was therefore broadened to meet the varied encoding
requirements of any discipline or application. Thus, the TEI became the
only systematized attempt to develop a fully general text encoding model
and set of encoding conventions based upon it, suitable for processing
and analysis of any type of text, in any language, and intended to serve
the increasing range of existing (and potential) applications and use.
 </p><p>What is published here is a major milestone in this effort. It
provides a single, coherent framework for all kinds of text encoding
which is hardware-, software- and application-independent. Within this
framework, it specifies encoding conventions for a number of key text
types and features. The ongoing work of the TEI is to extend the
scheme presented here to cover additional text types and features, as
well as to continue to refine its encoding recommendations on the
basis of extensive experience with their actual application and use.
 </p><p>We therefore offer these Guidelines to the user community for use in
the same spirit of active collaboration and cooperation with which
they have so far been developed. The TEI is committed to actively
supporting the wide-spread and large-scale use of the Guidelines
which, with the publication of this volume, is now for the first time
possible. In addition, we anticipate that users of the TEI Guidelines
will in some instances adapt and extend them as necessary to suit
particular needs; we invite such users to engage in the further
development of the Guidelines by working with us as they do so.
 </p><p>Like any standard which is actually used, these Guidelines do not
represent a static finished work, but rather one which will evolve
over time with the active involvement of its community of users. We
invite and encourage the participation of the the user community in
this process, in order to ensure that the TEI Guidelines become and
remain useful in all sorts of work with machine-readable texts.
 </p><p>This document was made possible in part by financial support from
the U.S. National Endowment for the Humanities, an independent federal
agency; Directorate General XIII of the Commission of the European
Communities; the Andrew W. Mellon Foundation; and the Social Science
and Humanities Research Council of Canada.  Direct and indirect support
has also been received from the University of Illinois at Chicago,
the Oxford University Computing Services, the University of Arizona,
the University of Oslo and Queen's University (Kingston, Ont.),
and Ohio State University.
 </p><p>The production of this document has been greatly facilitated by the
willingness of many software vendors to provide us with evaluation
versions of their products. Most parts of this text have been processed
at some time by almost every currently available SGML-aware software
system. In particular, we gratefully acknowledge the
assistance of the following vendors:
<list type="simple"><item>Berger-Levrault AIS s.a. (for Balise).</item><item>E2S n.v. (for E2S Advanced SGML Editor)</item><item>Electronic Book Technology (for DynaText),</item><item>SEMA Group and Yard Software (for Mark-It and Write-It),</item><item>Software Exoterica (for CheckMark and Xtran),</item><item>SoftQuad, Inc., (for Author/Editor and RulesBuilder),</item><item>WordPerfect Corporation (for Intellitag)</item><item>Xerox Corporation (for Ventura Publisher)</item></list><!-- also DARC ? kill Xerox? -->
 </p><p>Details of the software actually used to produce the current document
are given in the colophon at the end of the work.<?tei:EOF p2pref.odd ??>
<?tei:SOF p2ack.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ack.odd,v $
    * Revision 1.6  1998/02/01 17:51:31  tei
    * fix some mixed-content problems
    * fix Log keyword
    *
    * Revision 1.5  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.4  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.3  1994/04/07  03:01:58  msmcq
    * some stylistic changes (names not yet checke3d)
    * 
    * Revision 1.2  1994/03/31  18:12:35  lou
    * Revisions for P3
    * 
    * Revision 1.1  1994/02/17  20:29:04  msmcq
    * Initial revision
    * --><!-- Revisions:                                               --><!-- 5 Jan 98 : LB : change type of first committee list from --><!--                         ordered to gloss                 --><!-- 4 Jan 98 : LB : apply corrections from 1996-05-13 CMSMCW --><!-- 94-04-08 : MSM : suppress stray list start               --><!-- 94-04-08 : MSM : change list type from glossary to gloss --><!-- 94-04-07 : MSM : cosmetics, punctuate ...                --><!-- 94-04-01 : MSM : add David Durand, recast some prose     --><!-- 30 Mar 94 : LB : general tidyup; add flowing prose --><!-- 94-02-16 : MSM : revise AB list                          --><!-- 94-02-16 : MSM : add wg members                          --><!-- 94-02-16 : MSM : Added RCS id                            --><!-- 94-02-16 : MSM : make ODD form                           --><!-- 28 May 93 : MSM : separate out the acknowledgements      -->
 </p></div1><div1 id="WG" name="Section" ref="Y"><head>Acknowledgments</head><!-- <p>Many people have given of their time, energy,         --><!-- expertise and support in the creation of this            --><!-- document.  We list here all those who have served on     --><!-- the &tei;'s Work Groups and Working Committees           --><!-- throughout its six-year history, conscious as we do so   --><!-- that we risk offending some who have contributed much    --><!-- without being officially so enfranchised, as perhaps     --><!-- we offend others who have born more than their fair      --><!-- share of the labours involved in bringing to fruition    --><!-- the ideas presented here.  Our debt as editors to        --><!-- those who have patiently endured and corrected our       --><!-- misunderstandings of their work is immense, and we       --><!-- hope that they will feel the wait has not been in        --><!-- vain.  For any errors and inconsistencies remaining,     --><!-- we must accept responsibility; any virtue in what is     --><!-- here presented, we gladly ascribe to the energies of     --><!-- the keen intellects listed below.                        --><p>Many people have given of their time, energy, expertise, and support
in the creation of this document; it is unfortunately not possible to
thank them all adequately.  Below are listed those who have served as
formal members of the TEI's Work Groups and Working Committees during
its six-year history; others not so officially enfranchised also
contributed much to the quality of the result.</p><p>The editors take this opportunity to acknowledge our debt to those
who have patiently endured and corrected our misunderstandings of their
work; we hope that they will feel the wait has not been in vain.  For
any errors and inconsistencies remaining, we must accept responsibility;
any virtue in what is here presented, we gladly ascribe to the energies
of the keen intellects listed below.</p><p>C. M. Sperberg McQueen and Lou Burnard</p><div2 ref="Y"><head>TEI Working Committees (1990-1993)</head><note source="auth" place="inline" anchored="Y">Not all members listed were able to serve throughout the development
of the Guidelines.</note><list type="gloss"><label>Committee on Text Documentation:</label><item><p>Chair:  Dominik Wujastyk (Wellcome Institute for the History of
Medicine)</p><p>Members 1990-1992:  J. D. Byrum (Library of Congress);
Marianne Gaunt (Rutgers University);
Richard Giordano (Manchester University);
Barbara Ann Kipfer (Independent Consultant);
Hans J&oslash;rgen Marker (Danish Data Archive, Odense);
Marcia Taylor (University of Essex);</p></item><label>Committee on Text Representation</label><item><p>Chair:  Stig Johansson (University of Oslo)</p><p>Members 1990-1992:  Roberto Cencioni (Commission of the European
Communities);
David R. Chesnutt (University of South Carolina);
Robin C. Cover (Dallas Theological Seminary);
Steven J. DeRose (Electronic Book Technology Inc);
David G. Durand (Boston University);
Susan M. Hockey (Oxford University Computing Service);
Claus Huitfeldt (University of Bergen);
Francisco Marcos-Marin (University Madrid);
Elli Mylonas (Harvard University);
Wilhelm Ott (University of T&uuml;bingen);
Allen H. Renear (Brown University);
Manfred Thaller (Max-Planck-Institut f&uuml;r Geschichte,
G&ouml;ttingen)</p></item><label>Committee on Text Analysis and Interpretation</label><item><p>Chair:  D. Terence Langendoen (University of Arizona)</p><p>Members 1990-1992:
Robert Amsler (Bell Communications Research);
Stephen Anderson (Johns Hopkins University);
Branimir Boguraev (IBM T. J. Watson Research Center);
Nicoletta Calzolari (University of Pisa);
Robert Ingria (Bolt Beranek Newman Inc);
Winfried Lenders (University of Bonn);
Mitch Marcus (University of Pennsylvania);
Nelleke Oostdijk (University of Nijmegen);
William Poser (Stanford University);
Beatrice Santorini (University of Pennsylvania);
Gary Simons (Summer Institute of Linguistics);
Antonio Zampolli, University of Pisa.</p></item><label>Committee on Metalanguage and Syntax</label><item><p>Chair:  David T. Barnard (Queen's University);</p><p>David G. Durand (Boston University);
Jean-Pierre Gaspart (Associated Consultants and
Software Engineers sa/nv);
Nancy M. Ide (Vassar College);
Lynne A. Price (Software Exoterica / Xerox PARC);
Frank Tompa (University of Waterloo);
Giovanni Battista Varile (Commission of the European Communities).</p></item></list><p>In addition, the two TEI editors served ex officio on each
committee.</p><p>Following publication of the first draft of the TEI Guidelines (P1)
in November 1990, a number of specialist work groups were charged with
responsibility for drafting revisions and extensions, which, together
with material already presented in P1, constitute the basis of the
present work.</p><p>In addition, many members of the work groups listed below met on
three occasions to review the emerging proposals in detail at
technical review meetings convened by the TEI Steering Committee.
These meetings, held in Myrdal Norway (November 1991), Chicago (May
1992) and Oxford (May 1993), were largely responsible for the
technical content and organization of the present work.  Attendants at
these meetings are starred in the list below.
 
 
<list type="gloss"><label>TR1 Character sets</label><item>Chair:  Harry Gaylord* (University of Groningen);
Syun Tutiya* (Chiba University).</item><label>TR2 Text Criticism</label><item>Chair:  Peter Robinson* (Oxford University);
David Chesnutt* (University of South Carolina);
Robin Cover* (Dallas Theological Seminary);
Robert Kraft (University of Pennsylvania);
Peter Shillingsburg (Mississippi State University).</item><label>TR3 Hypertext and hypermedia</label><item>Chair:  Steven J. DeRose* (Electronic Book Technologies Inc);
David Durand (Boston University);
Edward A. Fox (Virginia State University); Eve Wilson (University of
Kent).</item><label>TR4 Formul&aelig;, Tables, Figures, and Graphics</label><item>Chair:  Paul Ellison* (University of Exeter);
Anders Berglund (Independent Consultant); Dale Waldt (Thompson
Professional Publishing).</item><label>TR6 Language corpora</label><item>Chair:  Douglas Biber* (University of Northern Arizona);
Jeremy Clear (Birmingham University);
Gunnel Engwall (University of Stockholm).</item><label>TR9 Manuscripts and Codicology</label><item>Chair:  Claus Huitfeldt* (University of Bergen);
Dino Buzzetti (University of Bologna);
Jacqueline Hamesse (University of Louvain);
Mary Keeler (Georgetown University);
Christian Kloesel (Indiana University);<!-- Ole Letnes (University of Bergen);                       --><!-- <item>Alois Pichler, observer                            -->
Allen Renear* (Brown University);
Donald Spaeth (Glasgow University).</item><label>TR10 Verse</label><item>Chair:  David Robey* (University of Manchester);
Elaine Brennan* (Brown University);
David Chisholm (University of Arizona);
Willard McCarty (University of Toronto).</item><label>TR11 Drama and performance texts</label><item>Chair:  Elli Mylonas* (Harvard University);
John Lavagnino* (Brandeis University);
Rosanne Potter (University of Iowa).</item><label>TR12 Literary prose</label><item>Chair Thomas N. Corns* (University of Wales);
Christian Delcourt (University of Li&egrave;ge;).<!-- item>Paul Fortier                                        --><!-- <item>Donald Ross                                        --></item><label>AI1 Linguistic Description</label><item>Chair:  D. Terence Langendoen* (University of Arizona);
Stephen R. Anderson (Johns Hopkins University);
Nicoletta Calzolari (University of Pisa);
Geoffrey Sampson* (University of Sussex);
Gary Simons* (Summer Institute of Linguistics).</item><label>AI2 Spoken text</label><item>Chair:  Stig Johansson* (University of Oslo);
Jane Edwards (University of California at Berkeley);
Andrew Rosta (University College London).</item><label>AI3 Literary studies</label><item>Chair:  Paul Fortier* (University of Manitoba);
Christian Delcourt  (University of Li&egrave;ge;);
Ian Lancashire  (University of Toronto);
Rosanne Potter (University of Iowa);
David Robey* (University of Manchester).</item><label>AI4 Historical studies</label><item><note source="auth" place="display" anchored="Y">This Workgroup was jointly sponsored by the Association for
History and Computing.</note>
Chair:  Daniel Greenstein* (University of Glasgow);
Peter Denley (Queen Mary Westfield College, London);
Ingo Kropac (University of Graz);
Hans J&oslash;rgen Marker (Danish Data Archive, Odense);
Jan Oldervoll (University of Troms&oslash;);
Kevin Schurer (University of Cambridge);
Donald Spaeth (Glasgow University);
Manfred Thaller (Max-Planck-Institut f&uuml;r Geschichte,
G&ouml;ttingen).</item><label>AI5 Print dictionaries</label><item>Chairs:  Robert Amsler* (Bell Communications Research) and
Nicoletta Calzolari (University of Pisa);
Susan Armstrong-Warwick (University of Geneva);
John Fought (University of Pennsylvania);
Louise Guthrie (University of New Mexico);
Nancy M. Ide* (Vassar College);
Frank Tompa (University of Waterloo);
Carol Van Ess-Dykema (Department of Defense);
Jean Veronis (University of Aix-en-Provence).</item><label>AI6 Machine Lexica</label><item>Chair:  Robert Ingria* (Bolt Beranek Newman Inc);
Susan Armstrong-Warwick (University of Geneva);
Nicoletta Calzolari (University of Pisa).<!-- <item>James Pustejovsky --></item><label>AI7 Terminological data</label><item>Chair:  Alan Melby* (Brigham Young University)
Gerhard Budin (University of Vienna);
Gregory Shreve (Kent State University);
Richard Strehlow (Oak Ridge National Laboratory);
Sue Ellen Wright (Kent State University).</item></list></p></div2><div2 name="Section" ref="Y"><head>Advisory Board</head><!-- Short list of AB members                                 --><p>Members of the TEI Advisory Board during the life time of the
project are listed below, grouped under the name of the organization
represented.
<list rend="compact=0" type="gloss"><label>American Anthropological Association:</label><item>Chad McDaniel (University of Maryland).</item><label>American Historical Association:</label><item>Elizabeth A. R. Brown (Brooklyn College, CUNY).</item><label>American Philological Association:</label><item>Jocelyn Penny Small (Rutgers University).</item><label>American Philosophical Association:</label><item>Allen Renear (Brown University).</item><label>American Society for Information Science:</label><item>Clifford A. Lynch (University of California).</item><label>Association for Computing Machinery, Special Interest Group for
Information Retrieval:</label><item>1989-93:  Scott Deerwester (University of Chicago); 1993- :
Martha Evens (Illinois Institute of Technology).</item><label>Association for Documentary Editing:</label><item>David Chesnutt (University of South Carolina).</item><label>Association for History and Computing:</label><item>1989-91:  Manfred Thaller, Max-Planck-Institut f&uuml;
Geschichte, G&ouml;ttingen; 1991- :  Daniel Greenstein (Glasgow
University).</item><label>Association Internationale Bible et Informatique</label><item>1989-93:  Wilhelm Ott (University of T&uuml;bingen); 1993- :
Winfried Bader (University of T&uuml;bingen).</item><label>Canadian Linguistic Association:</label><item>Anne-Maria di Sciullo (Universit&eacute; du Qu&eacute;bec
&agrave; Montr&eacute;al)</item><label>Dictionary Society of North America:</label><item>Barbara Ann Kipfer (independent consultant).</item><label>AAP Electronic Publishing Special Interest Group:</label><item>1989-92:  Betsy Kiser (OCLC); 1992- :
Deborah Bendig and Andrea Keyhani (OCLC).</item><label>International Federation of Library Associations and
Institutions:</label><item>J. D. Byrum Jr. (The Library of Congress).</item><label>Linguistic Society of America:</label><item>Stephen Anderson (The Johns Hopkins University)</item><label>Modern Language Association:</label><item>Randall Jones (Brigham Young University) and
Ian Lancashire (University of Toronto).</item></list></p></div2><div2 name="Section" ref="Y"><head>Steering Committee Membership</head><p>Members of the Steering Committee of the TEI during the preparation
of this work were:
<list type="gloss"><label>Association for Computational Linguistics:</label><item><list type="bullets"><item>1987-1993:  Robert A. Amsler (Bell Communications Research);</item><item>1987-1993:  Donald E. Walker (Bell Communications Research);</item><item>1993- :  Susan Armstrong-Warwick (University of Geneva);</item><item>1994- :  Judith Klavans (Columbia University).</item></list></item><label>Association for Computers and the Humanities:</label><item><list type="bullets"><item>1987- :  Nancy M. Ide (Vassar College);</item><item>1987-1994:  C. M. Sperberg-McQueen (University of Illinois at
Chicago);</item><item>1994- :  David Barnard (Queen's University).</item></list></item><label>Association for Literary and Linguistic Computing:</label><item><list type="bullets"><item>1987- :  Susan M. Hockey (Center for Electronic Texts in the
Humanities);</item><item>1987- :  Antonio Zampolli (University of Pisa).</item></list></item></list></p></div2></div1><!-- wot, no mention for Lou? Typical. --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ack.odd ??></front><body><div0 n="1" name="Part" ref="Y"><head>Introduction</head><div1 name="Chapter" ref="Y"><div2 name="Section" ref="Y"><div3 name="Section" ref="Y"><div4 name="Section" ref="Y"></div4></div3></div2></div1><?tei:SOF p2ab.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ab.odd,v $
    * Revision 1.11  1998/01/29 17:48:49  tei
    * Normalize SGML, fix log keyword
    *
    * Revision 1.10  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.9  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.8  1994/03/28  17:30:26  msmcq
    * suppress stray end-tag for P
    * 
    * Revision 1.7  1994/03/24  22:19:17  msmcq
    * Typographic errors found by David Barnard et al. corrected,
    * some stylistic changes, perhaps improvements.
    * 
    * Revision 1.6  1994/03/21  14:12:07  lou
    * second mass typo clearup
    * 
    * Revision 1.5  1994/01/21  18:06:47  lou
    * Revised and fixed up version
    * 
    * Revision 1.3  1993/09/15  22:48:30  msmcq
    * new file, revised by NI and CH
    * 
    * Revision 1.2  1993/07/29  21:04:15  msmcq
    * 1.2 is new version from CH, NI
    *--><!-- Subject: P2 chapter(s) AB                                --><!-- Revisions:                                               --><!-- 7 Jan 98 : LB : removed "draft" --><!-- 94-04-07 : MSM : minor stylistic fixes                   --><!-- 94-04-07 : MSM : cosmetic change to heading              --><!-- 94-03-27 : MSM : delete stray end-tag for P              --><!-- 93-03-21 : MSM: tidied up after the tidying up, fixed    --><!--                 typos and formatting glitches found by   --><!--                 DB, SJ, CH, EB                           --><!--                 and Paul, Susie, Carole, Elizabeth       --><!--                     and Caleb, at the WWP                --><!-- 4 jan 94: LB : tidied up, deleted unassimilated stuff --><!-- 19 dec 93: LB : fixd a cross ref --><!-- 93-09-13 : MSM : Some changes to avoid dup ids           --><!-- 93-09-13 : MSM : numerous SGML corrections               --><!-- 93-07-29 : MSM : minor cleanup of file as sent by CH     --><!--                  add RCS id, log                         --><!-- 02.06.93 : CH: Made file from P2 13.04.93 version,       --><!--            added comments from Eynsham, added changes    --><!--             made by NI and CH                            --><!-- 05.06.93 : NI: Further revisions                         --><!-- 11.06.93 : CH: Further revision, extensive rearrangement --><!-- 20.06.93 : CH: Further revision after talk with NI       --><!-- 21.07.93 : CH: Final revision, last changes from NI      --><div1 id="AB" n="1" name="Chapter" ref="Y"><head>About These Guidelines</head><!-- <div3 id=ABWHO><head>Who These Guidelines Are For</head> --><!-- <note place=inline ed=CH>New heading, not quite happy    --><!-- with it.  Other possibilities:  "Status of this          --><!-- Document", "Use of this Document", ... or perhaps we     --><!-- need no headline here?</note> CUT HEADING (lb)           --><p>These Guidelines have been developed by the Text Encoding Initiative
(TEI); see <xref target="ABTEI"/>.  They are addressed to anyone who
works with any text in electronic form.</p><p>They provide means of representing those features of a text which
need to be identified explicitly in order to facilitate processing of
the text by computer programs.  In particular, they specify a set of
markers (or <term>tag</term>s) which may be inserted in the electronic
representation of the text, in order to mark the text structure and
other textual features of interest.  Without such explicit markers, many
important features remain difficult to locate by mechanical means such
as computer programs, and thus difficult to process effectively.  The
process of inserting such explicit markers for implicit textual features
is often called <soCalled>markup</soCalled> or
<soCalled>tagging</soCalled>, and the term <term>encoding scheme</term>
or <term>markup language</term> denotes the rules which govern the use
of markup in a set of encodings.
 <!-- <note ed=NI> I made Claus' change </note> <note          --><!-- ed=CH>On second thought:  Perhaps delete "otherwise      --><!-- implicit" in the first sentence?  </note> </p>           --></p><p>The Guidelines formulated in this document are intended for use in
interchange between individuals and research groups using different
programs and computer systems over a broad range of applications.  Since
they contain an inventory of the features most often found useful for
text processing, the Guidelines also provide help to those creating
texts in electronic form.
 <!--      <note ed=CH>Was: "help to those creating electronic --><!--      texts."</note> Reverted (LB -->
 
They can also be used for the local storage of text which is to be
processed with multiple software packages requiring different input
formats.  </p><p>The Guidelines apply to texts in any natural language, of any date,
in any literary genre or text type, without restriction on form or
content.  They treat both continuous materials (<soCalled>running
text</soCalled>) and discontinuous materials such as dictionaries and
linguistic corpora.  Though principally directed to the needs of the
scholarly research community, the Guidelines are not restricted to
esoteric academic applications.  They should also be useful for
librarians who maintain and document electronic materials, as well as
for publishers and others creating or distributing electronic texts.
Although they focus on problems of representing in electronic form texts
which already exist in traditional media, these Guidelines should also
be useful for the creation of electronic texts.
 <!-- <note ed=NI> I tried to incorporate Claus' comment but   --><!-- have a problem, since it ends with exactly the same      --><!-- point as that at the end of the preceding paragraph.     --><!-- Cannot think of a solution at the moment.  Also tried    --><!-- to fix this paragraph generally.</note>                  -->
 <!-- <note ed=CH>Think I solved the problem.  Divided the     --><!-- para into two different paras, and revised further.      --><!-- Recent postings on TEI-L (or was it TEI-TECH), e.g. by   --><!-- Craig Ogg, Origami Ltd, confirmes the importance of the  --><!-- last point about creation of "new" texts vs. capture or  --><!-- representation of texts in traditional media.  </note>   -->
 <!-- <note ed=CH>Should we add a para here saying that there  --><!-- are some problems not addressed by these Guidelines      --><!-- which will be pursued in future developments, with       --><!-- reference to that section?</note> </p>                   -->
 
They are adequate to, but not limited by, existing practices.</p><p>The rules and recommendations made in the these Guidelines conform to
ISO 8879, which defines the Standard Generalized Markup Language (SGML),
and make reference to ISO 646, which defines a standard seven-bit
character set in terms of which the recommendations on character-level
interchange are formulated.  For more information on SGML see chapter<xref target="SG" type="div1"/>
.  </p><p>This document provides the authoritative statement of the
requirements and usage of the TEI encoding scheme.  Although it
includes numerous small examples, it must be stressed that it is
intended as a reference manual and that readers unfamiliar with SGML or
text markup in general will find it difficult to learn the encoding
scheme by reading this document alone.</p><!-- <note ed=CH>Was:  "is intended to provide an"</note> --><p>This document will be complemented by a series of tutorials in text
encoding (document TEI U1 et seq.) and a case book of extended examples
with discussion of the rationale for various markup choices (TEI T1).
<note source="auth" place="foot" anchored="Y">TEI documents bear identifying numbers which indicate
the provenance of the document (here simply <q>TEI</q>, in other cases
the TEI work group number, e.g.  <q>TEI AI5</q>), the type of document
(here <q>U</q> and <q>T</q>, meaning <gloss>users' guide</gloss> or
<gloss>users' manual</gloss> and <gloss>sample text(s)</gloss>), and a
sequential number.  The TEI document number of the document in hand is
TEI P3 (for <gloss>TEI public proposal number 3</gloss>).</note>
Readers seeking an introduction to text markup and the use of the TEI
encoding scheme in a specific area should consult an appropriate
tutorial; those already familiar with the scheme and interested in
seeing examples of its application should consult the case book.</p><!-- following para is new (LB) --><p>The remainder of this chapter comprises three sections.  The first
gives an overview of the structure and notational conventions used
throughout the document.  The second enumerates the design principles
underlying the TEI scheme and the application environments in which it
may be found useful.  Finally, the third section gives a brief account
of the origins and development of the Text Encoding Initiative itself.</p><div2 name="Section" ref="Y"><head>Structure and Notational Conventions of this Document</head><div3 id="ABSUM" name="Section" ref="Y"><head>Structure</head><p>Part I provides some relevant background information about the
Guidelines themselves (in this chapter); a brief technical
review of SGML (chapter <xref target="SG" type="div1"/>); and a description
of how the TEI document type definition (DTD) is organized (chapter<xref target="ST" type="div1"/>
).
 <!-- <note ed=CH> This is the first time the term 'document   --><!-- type declaration' occurs.  Next para mentions            --><!-- 'definition for default structure', two paras below the  --><!-- abbrev 'DTD' occurs for the first time.  In one of       --><!-- these places the clarificatory note about document type  --><!-- definitions, document type declarations, and DTDs        --><!-- (suggested by MSMQ) should be added.  </note> </p>       --></p><p>Part II provides a systematic treatment of issues common to all
text types: character representation (chapter<xref target="CH" type="div1"/>
); in-file documentation of the text
(chapter <xref target="HD" type="div1"/>); tags for text features found
in all sorts of text: lists, notes, emphasis, quotations,
cross-references, technical terms, names, dates, numbers, etc.
(chapter <xref target="CO" type="div1"/>); and a definition for the
default structure of all TEI documents (chapter<xref target="DS"/>
).</p><p>Part III documents various <term>base tag sets</term>: these
include specialized tags for prose, for verse, for drama and other
performance materials, for spoken materials, as well as for letters
and memoranda, printed dictionaries, and terminological data.
Additional sections discuss user-defined and mixed base tag sets. An
instance of the TEI DTD must use one and only one base tag set,
unless one of the <soCalled>mixed</soCalled> bases is used.</p><p>Part IV documents various <term>additional tag sets</term>, which
may be included or excluded, as appropriate. Topics covered include
a variety of approaches to the analysis and interpretation of texts,
and include representations for hypertextual links and other
non-hierarchic structures, as well as specialized tags for the
encoding of critical editions and language corpora.
 <!-- <note ed=CH>Was:  "for the encoding of physical description, --><!-- critical editions, and language corpora."  </note> </p> --></p><p>Part V defines certain specialized <term>auxiliary document
types</term>, used to encode information about the way that texts have
been encoded, specifically:  the TEI header regarded as a distinct
document; the TEI Writing System Declaration; the Feature System
declaration; and the Tag Set Documentation.</p><p>Part VI contains a number of technical discussions of a more
specialist interest.  Topics covered include the notion of formal
<term>conformance</term> to the TEI Guidelines; the controlled
user-modification of the TEI DTD; practical aspects of the use of
TEI markup both in local processing and in interchange; and the
relationship of TEI markup to other markup standards.</p><p>Part VII consists of an alphabetical reference list of all elements
and element classes defined in the TEI encoding scheme.</p><p>Part VIII provides further reference material:  specifically, a
description of how to obtain current versions of the full TEI DTDs and
the set of standard Writing System Declarations, a sample Feature System
Declaration for basic grammatical annotation, sample tag documentation,
and a formal grammar for the subset of SGML used in the TEI
interchange format.</p><p>In the back matter, a bibliography lists works cited in the text of
the Guidelines.  A mechanically generated index is also provided, which
can serve, it is hoped, as a finding aid for the use of the Guidelines.</p></div3><div3 id="ABNOT" name="Section" ref="Y"><head>Notational Conventions</head><!-- <note place=inline ed=CH>Was:  "Notational Conventions   --><!-- Used in This Draft"</note>                               --><p>This section describes the typographic and stylistic conventions used
throughout this document.  The use of many terms and concepts which have
not yet been defined is unavoidable in this section.  All such terms and
concepts will be explained in later chapters of Part I.
 <!--      <note ed=CH> Remark in parantheses suggested by JL --><!--      </note> </p> --></p><p>When SGML elements are mentioned in the text, the mentions take the
form <gi tei="no">name</gi>, where <q>name</q> is the <term>generic
identifier</term> of the element.  Sample tags mentioned in the text are
displayed in the form <tag compl="full" tei="no">name att=value att2='value two'</tag>.
References to SGML attributes take the form <att tei="no">attname</att>,
where <q>attname</q> is the name of the attribute.
Where the elements and attributes
thus mentioned are part of the TEI encoding scheme,
they are included in the index.</p><p>These Guidelines distinguish encoding practices, and SGML elements,
which are required, recommended, or optional.  The phrases <q>must</q>,
<q>is required to</q>, etc., mark practices and tags which are required
for TEI conformance.  The phrases <q>should</q>, <q>it is recommended
that</q>, <q>it is preferable to ...</q>, etc., are used in describing
practices which are recommended but not required for TEI conformance.
Modal verbs like <q>may</q>, <q>might</q>, etc., mark practices which
are strictly optional.  Qualifying phrases like <q>if desired</q>,
<q>where appropriate</q>, or <q>under some circumstances</q> are used
when some tag or practice described may be desirable or acceptable under
some circumstances and not under others.</p><p>In the reference section in Part VII, elements and their
attributes are all classed as one of:
 
<list type="gloss"><label>required</label><item>unconditionally required in a TEI-conformant document</item><label>mandatory when applicable</label><item>required under the appropriate conditions; may be
omitted if not applicable</item><label>recommended</label><item>recommended unless there are good reasons, in the given
circumstances, against it</item><label>recommended when applicable</label><item>recommended under some circumstances (which should be
clear from context)</item><label>optional</label><item>strictly optional </item></list>
 <!-- <note ed=CH> I, for one, had such a hard time            --><!-- understanding what was meant by 'required', 'mandatory   --><!-- when applicable', ... etc., that I would strongly        --><!-- recommend the inclusion of a short paragraph explaining  --><!-- the terms by means of concrete examples.  </note> </p>   --></p><p>This reference section includes cross-references to the chapter or
section of the main text within which each element is discussed.  Most
sections of the main text in which elements are defined begin with a
descriptive list of the elements concerned in the following format:
 
<list type="gloss"><label><gi tei="no">tag</gi></label><item>short description of the
element marked by <tag compl="full" tei="no">tag</tag>.  Where appropriate this is
followed by a list of significant non-global attributes for
the element as follows:
<list type="gloss"><label><att tei="yes">attribute</att></label><item>description of the attribute's meaning or usage,
optionally followed by a list of suggested or legal values:
<list type="gloss"><label>value1</label><item>meaning of value1</item><label>value2</label><item>meaning of value2</item></list></item></list></item></list></p><p>Not all attributes are always included in these lists; those which
are shared with other elements in a class are usually listed separately,
and those of relatively specialized interest are usually listed only in
the reference section.  The values of the attribute are introduced with
one of the following formulaic phrases:
 
<list type="gloss"><label><q>Legal values include:</q></label><item>The attribute cannot take values other than those given.  Other
values will cause SGML parsing errors.  (This is used relatively rarely
in these Guidelines.)</item><label><q>Suggested values include:</q></label><item>The values listed constitute a set which should suffice for most
purposes, and they should be used where appropriate.  Developers of
TEI-aware software should ensure that their software can process these
values appropriately.  In some cases, however, it is conceivable that
other values might be necessary, so the SGML declaration for the
attribute does not restrict legal values to those given.  TEI-aware
software should have reasonable fallback processing for values not in
the list.</item><label><q>Sample values include:</q></label><item>The attribute can take any value; those listed are provided simply
as examples of the kind of value possible.  </item></list></p><p>Each list of elements is followed by some discussion of its
semantics and usage, followed by one or more examples, taken
wherever possible from real texts, and presented in the following
format:
 
<eg><![CDATA[ <p>This paragraph contains an <hi rend=it>italicized phrase</hi>]]></eg>
 
All the examples are (or should be) legal SGML, but, because they are
fragmentary, may not be parseable by SGML parsers without the required
context.  They also frequently make liberal use of white space to
exhibit the logical structure of the SGML coding more clearly.  Although
this does not affect the SGML conformance of the examples, some users
will prefer not to follow it in practice, since not all processors will
ignore the extra white space.  Examples may:
 
<list type="bullets"><item>show full start- and end-tags for all elements </item><item>use empty end-tags (of the form
<tag compl="full" tei="no">/</tag>) to close the most recently
opened element</item><item>omit end-tags (never start-tags) where they may legally be
omitted; where this is done, it is normally mentioned in the
accompanying text</item></list>
 <!-- <note ed=CH> Last list item (end-tag omission) removed   --><!-- </note>                                                  -->
 
Attribute values are given indifferently in single quotes or double
quotes; unquoted attribute values are sometimes used where SGML requires
no quotation marks.</p><p>It should be noted that the examples demonstrate a variety of tagging
styles, mostly aimed at making the tagging legible while also showing
fairly explicitly where all elements begin and end.  No claim is made or
implied as to the appropriateness of the style adopted here for other
purposes; in particular, those using SGML for local processing may often
prefer to use empty end-tags more frequently than is shown in the
examples, or to omit end-tags.
 <!-- <note ed=CH>Was:  "may often prefer to use empty         --><!-- end-tags or to omit tags more frequently than is shown   --><!-- in the examples."  </note> </p>                          --></p><p>After the examples and usage notes, each section typically concludes
with a DTD fragment containing the formal declarations for the elements
described.  Each DTD fragment is given a heading, and may contain
element and attribute list declarations, entity declarations, parameter
entity references, comments, and references to DTD fragments in other
sections.  The DTD fragments of a single chapter almost invariably
belong to the same DTD file, the structure of which is typically
described (with references to the included fragments) in one of the
first or last sections of the chapter.</p><p>The DTD fragments are identical to the DTDs distributed with
these Guidelines, with the following exceptions:
 
<list type="bullets"><item>In the text, the DTD fragments appear in an order dictated by
organization of this document; the actual DTD files may re-order the
material slightly.  This is indicated in the text by references from one
DTD fragment to another.</item><item>The DTD fragments in the text show the generic identifiers of all
elements using the standard English names assigned in this document; the
actual DTD files use parameter entities for all generic identifiers, so
that elements can be conveniently renamed, as described in chapter<xref target="MD"/>
.  </item><item>The actual DTD files include conditional marked sections
surrounding the element and attribute list declaration for each element,
to ensure that elements can conveniently be suppressed or redefined, as
described in chapter <xref target="MD"/>.  The fragments in the text
suppress the marked-section-open and marked-section-close markup.</item></list></p><p>What appears in the text, therefore, as:
<eg><![CDATA[  <!ELEMENT blort - O (farble+)>]]></eg>
will appear thus in the actual DTD file:
<eg>  &lt;![ %blort [
  &lt;!ELEMENT %n.blort - O ((%n.farble)+)&gt;
  ]]&gt;</eg> </p><p>For further discussion, see chapter <xref target="ST"/>, or chapter<xref target="MD"/>
.</p></div3></div2><div2 id="ABDPIU" name="Section" ref="Y"><head>Underlying Principles and Intended Use</head><div3 id="ABTEI2" name="Section" ref="Y"><head>Design Principles of the TEI Scheme</head><p>The planning conference held at Vassar College in November, 1987 (see
section <xref target="ABTEI"/>) agreed on a number of principles concerning
the basic design goals of the Text Encoding Initiative.  These
principles are expounded in various documents of the TEI (notably TEI
ED P1 and TEI ED P2) and the interested reader is directed to those
documents for further discussion.
 <!-- <note ed=CH>Nancy:  Perhaps a sentence here explaining   --><!-- the relationship between the Vassar principles and the   --><!-- text below, - if anyone feels the need for it.  I        --><!-- don't.</note></p>                                        --></p><p>Because of its roots in the humanistic research community, the TEI
scheme is driven by its original goal of serving the needs of research,
and is therefore committed to providing a maximum of comprehensibility,
flexibility, and extensibility.  More specific design goals of the TEI
have been that the Guidelines should:
 
<list type="simple"><item>provide a standard format for data interchange</item><item>provide guidance for encoding of texts in this
format</item><item>support the encoding of all kinds of features of all
kinds of texts studied by researchers</item><!-- <note ed=CH>Nancy, need a shorter and better formulation for --><!-- this, - all kinds of (features of all kinds of) texts in all --><!-- languages, and all kinds of scholarly work with --><!-- those.</note>--><item>be application independent</item></list>
 
This has led to a number of important design decisions, such as:
 
<list type="simple"><item>the choice of SGML and ISO 646</item><item>the provision of a large predefined tag set</item><item>a distinction between required, recommended, and optional encoding
practices</item><!-- , with relatively few encodings being required --><!--      <note ed=CH>Someone has to fix this --><!--      sentence</note></item> --><item>encodings for different views of text</item><item>alternative encodings for the same text features</item><item>mechanisms for user-defined extensions to the scheme</item></list>
 
These goals and principles are expounded in more detail below.</p><p>The goals of creating a common interchange format which is
application independent require the definition of a specific markup
syntax as well as the definition of a large predefined tag set.  The
syntax of the recommendations made in this document conforms to the
international standard ISO 8879, which defines the Standard Generalized
Markup Language; reference is also made to ISO 646, which defines a
standard seven-bit character set.  Full SGML document type declarations
are provided for the scheme described in these Guidelines.  </p><p>The goal of providing guidance for text encoding requires that
recommendations be made as to what textual features should be recorded
in various situations.  This mandate is fulfilled by the explicit
specification, in the reference section for each tag, that the tag is
<term>required</term>, <term>mandatory when applicable</term> but
otherwise omissible, <term>recommended</term> generally,
<term>recommended when applicable</term> but not always applicable, or
<term>optional</term>.</p><p>However, the TEI Guidelines make (with relatively rare exceptions)
no suggestions or restrictions as to the relative importance of textual
features.  The philosophy of the Guidelines is <q>if you want to encode
this feature, do it this way</q> --- but very few features are
mandatory.
 <!-- <note ed=CH>This still appears a bit self-contradictory  --><!-- to me.  If one makes recommendations as to what          --><!-- features are 'required, recommended, and optional', it   --><!-- seems one does thereby make suggestions as to their      --><!-- relative importance.  Perhaps the para should go like    --><!-- this instead:  "Nevertheless, since very few parts of    --><!-- the &tei; scheme are required, the Guidelines do not     --><!-- impose restrictions against other views as to the        --><!-- relative importance of textual features.  The            --><!-- philosophy of the Guidelines is...."</note></p>          --></p><p>The Guidelines have been written largely with a focus on text capture
(i.e. the representation in electronic form of an already existing copy
text in another medium) rather than text creation (where no such copy
text exists).  Hence the frequent use of terms like
<soCalled>transcription</soCalled>, <soCalled>original</soCalled>,
<soCalled>copy text</soCalled>, etc.  However, the Guidelines should be
equally applicable to text creation, and the two terms <term>text
creation</term> and <term>text capture</term> are often used
interchangeably.</p><p>Concerning text capture the TEI Guidelines do not specify a
particular approach to the problem of fidelity to the source text and
recoverability of the original; such a choice is the responsibility of
the text encoder.  The current version of these Guidelines, however,
provides a more fully elaborated set of tags for markup of rhetorical,
linguistic, and simple typographic characteristics of the text than for
detailed markup of page layout or for fine distinctions among type fonts
or manuscript hands.
 <!-- <note ed=CH>Nancy: Should we delete the last --><!-- sentence?</note></p> --></p><p>In these Guidelines, no hard and fast distinction is drawn between
<soCalled>objective</soCalled> and <soCalled>subjective</soCalled>
information or between <soCalled>representation</soCalled> and
<soCalled>interpretation</soCalled>.  These distinctions, though widely
made and often useful in narrow well defined contexts, are perhaps best
interpreted as distinctions between issues on which there is a scholarly
consensus and issues where no such consensus exists.  Such consensus
has been, and no doubt will be, subject to change.  The TEI
Guidelines do not make suggestions or restrictions as to which of these
features should be encoded.  The use of the terms
<term>descriptive</term> and <term>interpretive</term> about different
types of encoding in the Guidelines is not intended to support any
particular view on these theoretical issues, but reflects a purely
practical division of responsibility between the two committees called
Committee on Text Representation and Committee on Text Interpretation
and Analysis.  </p><!-- (see < xref target=???>.                                 --><p>In general, the accuracy and the reliability of the encoding and the
appropriateness of the interpretation is for the individual user of the
text to determine.  The Guidelines provide a means of documenting the
encoding in such a way that a user of the text can know the reasoning
behind that encoding, and the general interpretive decisions on which it
is based.  It is strongly recommended that the TEI header be used to
give an account of these aspects of the encoding.  The TEI header is
described in chapter <xref target="HD"/>.</p><p>In many situations more than one view of a text is needed.  No
absolute recommendation to embody one specific view of text can apply to
all texts and all approaches to them.  The syntax of SGML ensures that
some encodings can be ignored for some purposes.  To enable encoding
multiple views, these Guidelines not only treat a variety of text
features, but they sometimes provide several alternative encodings for
what appear to be identical textual phenomena.  These Guidelines
therefore offer the possibility of encoding many different views of the
text, simultaneously if necessary.</p><p>However, the Guidelines are built on the assumption that there is a
common core of textual features shared by virtually all texts and
virtually all serious work on texts.  This core set of tags is defined
in Chapter <xref target="CO" type="div1"/>.  Beyond this core, many different
elements can be encoded.</p><p>In brief, the TEI Guidelines define a general-purpose encoding
scheme which makes it possible to encode different views of text,
possibly intended for different applications, serving the majority of
scholarly purposes of text studies in the humanities.  However, no
predefined encoding scheme can serve all research purposes.  Therefore,
the TEI also provides means of modifying and extending the encoding
scheme defined by the Guidelines (see chapter <xref target="MD"/>).</p></div3><div3 id="ABAPP" name="Section" ref="Y"><head>Intended Use</head><p>We envisage three primary functions for these Guidelines:
 
<list type="bullets"><item>guidance for individual or local practice in text
creation and data capture;</item><item>support of data interchange;</item><item>support of application-independent local processing.</item></list>
 
These three functions are so thoroughly interwoven in practice that it
is hardly possible to address any one without addressing the others.
However, the distinction provides a useful framework for discussing the
possible role of the Guidelines in work with electronic texts.</p><div4 id="ABAPP1" name="Section" ref="Y"><head>Use in Text Capture and Text Creation</head><p>The description of textual features found in the chapters which
follow should provide a useful checklist from which scholars planning to
create electronic texts should select the subset of features suitable
for their project.  </p><p>Problems specific to text creation or text
<soCalled>capture</soCalled> have not been considered explicitly in this
document.  For purposes of the TEI interchange format and for use of
SGML, it does not matter how a text is created or captured:  it can be
typed by hand, scanned from a printed book or typescript, read from a
typesetter's tape, or acquired from another researcher who may have used
another markup scheme (or no explicit markup at all).</p><p>We include here only some general points which are often raised about
SGML and the process of data capture.</p><p>SGML can appear distressingly verbose, particularly when (as in these
Guidelines) the names of tags and attributes are chosen for clarity and
not for brevity.  Editor macros and keyboard shorthands can allow a
typist to enter frequently used tags with single keystrokes.
Special-purpose software may be purchased which scans word-processor or
scanner data and inserts SGML tags.  SGML-aware software can help with
maintaining the hierarchical structure of the document, and display the
document with visual formatting rather than raw tags.</p><p>The techniques described in chapter <xref target="MD" type="div1"/> may be
used to give shorter names to the tags being used most often.  It should
also be noted that the examples in this text are chosen to exhibit the
markup as compactly as possible, and thus have denser markup than will
be typical in many texts.</p><p>The SGML standard provides ways of abbreviating, omitting, or
otherwise <term>minimizing</term> the amount of markup which need be
explicitly provided in a text.  They are all forbidden in the TEI
interchange format because their use complicates processing; this does
not however preclude their use in local processing, where this is felt
appropriate or desirable.</p></div4><div4 id="ABAPP2" name="Section" ref="Y"><head>Use for Interchange</head><p>When the TEI Guidelines are used for interchange, it is expected
that researchers using other encoding schemes in their work will
translate outgoing data from such schemes into the scheme described by
these Guidelines, and similarly translate incoming data from the scheme
described here into those used internally.  For such translations to be
carried out without loss of information, the scheme proposed here must
be as expressive (in a formal sense) as any encoding scheme now known to
be in wide use for textual research.  To ensure that this is the case, a
set of extension techniques is provided (see chapter <xref target="MD" type="div1"/>) which makes possible the addition of extra tags, the
renaming of existing tags and certain kinds of redefinition.  Although
the intention is to minimize the need for recourse to such extensions,
they may be used to accommodate the encoding of new or unanticipated
textual features.
 <!-- It is important, however, to be sure that a textual      --><!-- feature that appears to be missing from the Guidelines   --><!-- is indeed not there, otherwise the extended DTDs will    --><!-- be needlessly redundant and the converted documents      --><!-- needlessly diverse, making comparative work difficult.   -->
 <!-- <note ed=CH> Last two sentences suggested by AHR.  Was:  --><!-- "However the intention has been to minimize any need     --><!-- for recourse to such extensions."  </note>               -->
 <!-- <note ed=NI> I do not like the last sentence, since my   --><!-- first reaction is to ask, how do I ensure that it is     --><!-- not there?  More generally it seems a bit insulting to   --><!-- the user's intelligence.</note>                          -->
 <!-- I vote with NI. (msm)                                    -->
 
To translate between any pair of encoding schemes implies:
 
<list type="ordered"><item>identifying the sets of textual features distinguished
by the two schemes;</item><item>determining where the two sets of features correspond;</item><item>creating a suitable set of mappings.</item></list> </p><p>For example, to translate from encoding scheme X into the TEI
scheme:
 
<list type="ordered"><item>Make a list of all the textual features distinguished in
X. </item><item>Identify the corresponding feature in the TEI scheme.
There are three possibilities for each feature:
<list type="ordered"><item>the feature exists in both X and the TEI scheme;</item><item>X has a feature which is absent from the TEI scheme;</item><item>X has a feature which corresponds with more than one
feature in the TEI scheme.</item></list>
 
The first case is unproblematic.  The second requires an extension to
the TEI scheme, as described in chapter <xref target="MD"/>.  The third
requires that a consistent choice be made.  The algorithm used to make
that choice should be documented in the TEI header.  </item><item>Using the table of equivalences so generated, a simple
translation can be carried out between X and the TEI. </item></list></p><!-- following para added by LB to try to meet points raised below --><p>The ease with which this translation can be carried out will of
course depend on the clarity and explicitness with which scheme X
represents the features it encodes.</p><p>Translating from the TEI into scheme X follows the same pattern,
except that if a TEI feature has no equivalent in X, and X cannot be
extended, information must be lost in translation.</p><p>Similar procedures may be followed where the TEI scheme is to be
used as an interlanguage for interchange among several different sites
or applications, although the degree of TEI-conformance may vary.</p><!-- <note ed=CH> AHR: The translation section seems nice and --><!-- simple. Maybe too simple. Should it say anything about eg --><!-- overlapping elements or procedural code in the source --><!-- document? CH: I have no problem with what this section --><!-- explicitly says, but isn't it a gross oversimplification? It --><!-- seems to presuppose that all other encoding schemes have a --><!-- syntax which allows for a relatively straightforward (one- --><!-- to-one or many-to-one) mapping from tags in that scheme to --><!-- tags in SGML/TEI. This is simply not the whole truth. --><!-- Other encoding schemes may have syntactic structures so --><!-- different from SGML that translation into TEI requires not --><!-- only more or less complex remapping of tags and delimiters, --><!-- but also a complete restructuring of entire chunks of text. --><!-- Not that I think this should be discussed in any detail, but --><!-- we should not conceal the fact that translation to and from --><!-- TEI-SGML *may* occasionally require *very heavy programming*. --><!-- This is precisely one of the reasons why people should keep --><!-- their attention fixed on TEI/SGML also when designing --><!-- local formats. Sorry, I have no suggestion exactly how to put --><!-- this... </note> --><!-- <note ed=NI> Frankly I like the simplicity. This chapter --><!-- suffers from our trying to make every conceivable --><!-- qualification and cover every conceivable possibility. If the --><!-- point can be made in a sentence (or a footnote), then it could --><!-- be added, but otherwise I would vote for the straightforward --><!-- approach. </note> --><p>In the simplest case, where two sites or individuals exchanging texts
know each other and know or can inquire what equipment the other is
using, these Guidelines serve primarily as documentation for a file
format, which can be referred to without actually being transmitted
together with the file.  In the general case, where sender and recipient
cannot communicate such information, a stricter degree of <term>TEI
conformance</term> will be required for loss-free interchange.</p><p>The rules defining such strict conformance to the Guidelines are
given in some detail in chapter <xref target="CF" type="div1"/>.  The
<term>interchange format</term> defined there requires that an
electronic text:
 
<list type="ordered"><item>adhere to the SGML declaration and the SGML document type
declarations defined in these Guidelines, unless modified or extended as
described in chapter <xref target="MD" type="div1"/>.  These SGML constructs
are further discussed in chapter <xref target="SG"/>.</item><!-- The concepts of the SGML --><!-- declaration and the SGML document type declaration are --><!-- explained in section <xref type=div1 target=SG>. The --><!-- provisions of the SGML declaration to be used for TEI files --><!-- are discussed in section <xref type=div1 target=SG>.) </item> --><item>provide external documentation as described in chapter<xref target="TD" type="div1"/>
 for all elements not defined in these
Guidelines, specifying a formal name (generic identifier) and a
corresponding full natural-language name, describing its meaning and
usage, specifying its legal content and also any attributes it may use.</item><item>adhere to the requirements of the TEI header in providing
bibliographic identification of the text and description of the encoding
practices used (as described in chapter <xref target="HD"/>).  </item></list> </p><p>Note that the interchange format makes no formal restriction on the
character set to be used in interchange, as this will depend on the
medium of interchange and the local character sets in use by sender and
receiver.  For further information, refer to chapter <xref target="IN" type="div1"/>.</p></div4><div4 id="ABAPP3" name="Section" ref="Y"><head>Use for Local Processing</head><p>Machine-readable text can be manipulated in many ways; some users:
 
<list type="bullets"><item>edit texts (e.g. word processors, syntax-directed
editors) </item><item>edit, display, and link texts in hypertext systems</item><item>format and print texts using desktop publishing systems,
or batch-oriented formatting programs </item><item>load texts into free-text retrieval databases or
conventional databases </item><item>unload texts from databases as search results or for
export to other software </item><item>search texts for words or phrases </item><item>perform content analysis on texts </item><item>collate texts for critical editions </item><item>scan texts for automatic indexing or similar purposes</item><item>parse texts linguistically </item><item>analyze texts stylistically </item><item>scan verse texts metrically </item><item>link text and images </item></list> </p><p>These applications cover a wide range of likely uses but are by no
means exhaustive.  The aim has been to make the TEI Guidelines useful
for encoding the same texts for different purposes.  We have avoided
anything which would restrict the use of the text for other
applications.  We have also tried not to omit anything essential to any
single application.</p></div4></div3></div2><div2 id="ABTEI" name="Section" ref="Y"><head>Historical Background</head><!-- <p>These Guidelines are the result of several years'     --><!-- development by the an international co-operative         --><!-- research project known as the Text Encoding Initiative   --><!-- (&tei;).  This section outlines the progress of that     --><!-- project and its likely future development.</p>           --><!-- suppressed at CH's suggestion. this is almost identical  --><!-- to first para of preface, in any case (msm)              --><p>The Text Encoding Initiative grew out of a planning conference
sponsored by the Association for Computers and the Humanities (ACH) and
funded by the U.S.  National Endowment for the Humanities (NEH), which
was held at Vassar College in November 1987.  At this conference some
thirty representatives of text archives, scholarly societies, and
research projects met to discuss the feasibility of a standard encoding
scheme and to make recommendations for its scope, structure, content,
and drafting.  During the conference, the Association for Computational
Linguistics and the Association for Literary and Linguistic Computing
agreed to join ACH as sponsors of a project to develop the Guidelines.
The outcome of the conference was this set of principles, which
determined the further course of the project.</p><list type="ordered"><item>The guidelines are intended to provide a standard format
for data interchange in humanities research. </item><item>The guidelines are also intended to suggest principles
for the encoding of texts in the same format. </item><item>The guidelines should
<list type="ordered"><item>define a recommended syntax for the format, </item><item>define a metalanguage for the description of
text-encoding schemes, </item><item>describe the new format and representative existing
schemes both in that metalanguage and in prose. </item></list></item><item>The guidelines should propose sets of coding conventions
suited for various applications. </item><item>The guidelines should include a minimal set of
conventions for encoding new texts in the format. </item><item>The guidelines are to be drafted by committees on
<list type="ordered"><item>text documentation </item><item>text representation </item><item>text interpretation and analysis </item><item>metalanguage definition and description of existing and
proposed schemes, </item></list>
coordinated by a steering committee of representatives of the principal
sponsoring organizations.  </item><item>Compatibility with existing standards will be maintained
as far as possible. </item><item>A number of large text archives have agreed in principle
to support the guidelines in their function as an interchange
format. We encourage funding agencies to support development
of tools to facilitate this interchange. </item><item>Conversion of existing machine-readable texts to the new
format involves the translation of their conventions into the
syntax of the new format. No requirements will be made for the
addition of information not already coded in the texts.</item></list><p>In the course of the work, some of these goals assumed greater, some
lesser importance; some proved easier, some harder to achieve.  The
document in hand does define a standard form for the interchange of
textual material, and adumbrate principles for the creation of new
electronic texts.  The only metalanguage used, however, is that of SGML,
and no formal definitions are given of other common encoding schemes.
These Guidelines do define a minimal set of conventions for text
encoding (i.e. those SGML elements classed as recommended or required),
though few researchers will be satisfied to encode <emph>only</emph>
what is required or recommended here, since the set of required and
recommended SGML elements is rather small.  This document does not,
however, define --- at least not explicitly --- <q>sets of coding
conventions suited for various applications</q>, since consensus on
suitable conventions for different applications proved elusive; this
remains a goal for future work.</p><div3 id="ABTEI1" name="Section" ref="Y"><head>Origin and Development of the TEI</head><p>The Text Encoding Initiative proper began in June 1988 with funding
from the NEH, soon followed by further funding from the Commission of
the European Communities, the Andrew W. Mellon Foundation, and the
Social Science and Humanities Research Council of Canada.  Four working
committees, composed of distinguished scholars and researchers from both
Europe and North America, were named to deal with problems of text
documentation (resulting largely in chapter <xref target="HD" type="div1"/>),
text representation, text analysis and interpretation (together
responsible for most of what has become parts II, III, and IV), and
metalanguage and syntax issues (largely responsible for part VI).</p><p>A first draft version (1.0) of the Guidelines was distributed in July
1990 under the title <title>Guidelines for the Encoding and Interchange
of Machine-Readable Texts</title>, with the TEI document number TEI
P1.  With minor changes and corrections, this version was reprinted as
version 1.1 in November 1990.</p><p>Extensive public comment and further work on areas not covered in
version 1 resulted in the drafting of a revised version, TEI P2,
distribution of which began in April 1992.  This version includes
substantial amounts of new material, resulting from work carried out by
several specialist working groups, set up in 1990 and 1991 to propose
extensions and revisions to the text of P1.  The overall organization,
both of the draft itself and of the scheme it describes, was entirely
revised and reorganized in response to public comment on the first
draft.</p><p>In June, 1993, the Advisory Board of the Text Encoding Initiative met
to review the current state of the Guidelines, and recommended the
formal publication of the work done to that time.  The present version
of the TEI Guidelines, TEI P3,
represents a further revision of all chapters
published under the document number TEI P2, and the addition of further
chapters.  Although it will be subject to revision and amendment on the
basis of practical experience and public discussion, this version of the
Guidelines is published without the label <cited>draft</cited>, and
marks the conclusion of the initial development work.
<!-- statement on status of revised draft needed here --></p></div3><div3 id="ABTEI4" name="Section" ref="Y"><head>Future Developments</head><p>Work on areas still not satisfactorily covered in this manual will
continue, and resulting recommendations will be issued as supplements to
the published Guidelines.  Work is expected to continue in at least the
following areas:
 
<list type="simple"><item>linguistic description and grammatical annotation</item><item>historical analysis and interpretation </item><item>base tag sets for further document types </item><item>manuscript analysis and physical description of text</item></list></p><p>The encoding recommended by this document may be used without fear
that future versions of the TEI scheme will be inconsistent with it in
fundamental ways.  The TEI will be sensitive, in revising these
Guidelines, to the possible problems which revision might pose for those
who are already using this version of the Guidelines.  
Wherever consistent with the
long-term goals of the project, consistency with this version will be
preserved in future revisions.  </p><!-- 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:
--></div3></div2></div1><?tei:EOF p2ab.odd ??><!-- 1 About These Guidelines  --><?tei:SOF p2sg.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sg.odd,v $
    * Revision 1.12  1998/01/31 17:17:18  tei
    * Add discussion of formal public identifiers, ancillary files,
    * and SGML Open catalog files.
    *
    * Revision 1.11  1998/01/28 11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.10  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.9  1994/03/29  17:49:27  msmcq
    * add /note tag before xmp
    * 
    * Revision 1.8  1994/03/28  15:20:26  lou
    * fix minor typo in <code>
    * 
    * Revision 1.7  1994/03/24  22:19:53  msmcq
    * typos and errors found by David Barnard, the team of
    * proofreaders at WWP, and others corrected.  Brief
    * discussions of parameter entities and marked sections added.
    * 
    * Revision 1.6  1993/12/20  10:41:57  lou
    * correected ID on first div
    * 
    * Revision 1.5  1993/09/09  23:02:54  msmcq
    * final typo corrections before publication
    * 
    * Revision 1.4  1993/08/25  15:04:59  lou
    * final revisions for publication
    * 
    * Revision 1.3  1993/08/24  16:15:45  msmcq
    * revise for publication in P2
    * 
    * Revision 1.2  1993/07/29  21:07:45  msmcq
    * correct Script problem in first para
    *--><!-- Revisions:                                               --><!-- 7 jan 98 : LB : deleted a definitely redundant "however"  --><!-- 94-04-07 : MSM : minor stylistic fixes                   --><!-- 94-03-22 : MSM : typos and improvements from DB, RC      --><!-- 94-03-22 : MSM : retag many terms and q as cited, ident, --><!--                  code                                    --><!-- 94-03-22 : MSM : add section on marked sections (fast)   --><!-- 94-03-21 : MSM : typos and stylistic revisions, as per:  --><!--                  WWP team                                --><!-- 93-08-26 : MSM : trivial typos                           --><!-- 93-08-25 : MSM : typos for publication                   --><!-- 93-08-24 : MSM : add N value                             --><!-- 93-08-24 : MSM : minor revisions for publication in P2   --><!-- 93-07-29 : MSM : add RCS id, log                         --><!-- 93-07-21 : MSM : suppress space at start of para 1       --><!-- 93-06-05 : MSM : format attlist examples as in later dtd frags --><!-- 93-06-05 : MSM : de-fang a comment                       --><!-- 93-06-05 : MSM : expand empty end-tag                    --><!-- 93-06-02 : WP : Spellchecked, moved , outside of for.lang.tag. --><div1 id="SG" n="2" name="Chapter" ref="Y"><head>A Gentle Introduction to SGML</head><p>The encoding scheme defined by these Guidelines is formulated as an
application of a system known as the Standard Generalized Markup
Language (SGML).
<note source="auth" place="display" anchored="Y">International Organization for Standardization, <title>ISO
    8879:  Information processing---Text and office systems---Standard
    Generalized Markup Language (SGML),</title> ([Geneva]:  ISO, 1986).<!-- Although widely said to be short for the surnames of its --><!-- progenitors, the official expansion of this abbreviation --><!-- is <q>Standard Generalized Markup Language.</q>          -->
    </note>
SGML is an international standard for the definition of
device-independent, system-independent methods of representing texts in
electronic form.  This chapter presents a brief tutorial guide to its
main features, for those readers who have not encountered it before.
For a more technical account of TEI practice in using the SGML standard,
see chapter <xref target="CF"/>; for a more technical description of the
subset of SGML used by the TEI encoding scheme, see chapter<xref target="GR"/>
.</p><p>SGML is an international standard for the description of marked-up
electronic text.  More exactly, SGML is a <term>metalanguage</term>,
that is, a means of formally describing a language, in this case, a
<term>markup language</term>.<!-- MSM adds the following sentence and paragraphs -->
Before going any further we should define these terms.</p><p>Historically, the word <term>markup</term> has been used to describe
annotation or other marks within a text intended to instruct a
compositor or typist how a particular passage should be printed or laid
out.  Examples include wavy underlining to indicate boldface, special
symbols for passages to be omitted or printed in a particular font and
so forth.  As the formatting and printing of texts was automated, the
term was extended to cover all sorts of special
<term>markup codes</term> inserted into electronic texts to govern
formatting, printing, or other processing.</p><p>Generalizing from that sense, we define markup, or (synonymously)
<term>encoding</term>, as any means of making explicit an interpretation
of a text.  At a banal level, all printed texts are encoded in this
sense:  punctuation marks, use of capitalization, disposition of letters
around the page, even the spaces between words, might be regarded as a
kind of markup, the function of which is to help the human reader
determine where one word ends and another begins, or how to identify
gross structural features such as headings or simple syntactic units
such as dependent clauses or sentences.  Encoding a text for computer
processing is in principle, like transcribing a manuscript from
<foreign lang="LA">scriptio continua</foreign>, a process of making
explicit what is conjectural or implicit, a process of directing the
user as to how the content of the text should be interpreted.</p><p>By <term>markup language</term> we mean a set of markup conventions
used together for encoding texts.  A markup language must specify what
markup is allowed, what markup is required, how markup is to be
distinguished from text, and what the markup means.  SGML provides the
means for doing the first three; documentation such as these
Guidelines is required for the last.</p><p>The present chapter attempts to give an informal introduction---much
less formal than the standard itself---to those parts of SGML of which a
proper understanding is necessary to make best use of these Guidelines.</p><div2 id="SG11" name="bar" ref="Y"><head>What's Special about SGML?</head><p>There are three characteristics of SGML which distinguish it from
other markup languages:  its emphasis on descriptive rather than
procedural markup; its <term>document type</term> concept; and its
independence of any one system for representing the script in which a
text is written.  These three aspects are discussed briefly below, and
then in more depth in sections <xref target="SG13"/> and <xref target="SG17"/>.</p><div3 id="SG111" name="burp" ref="Y"><head>Descriptive Markup</head><p>A descriptive markup system uses markup codes which simply provide
names to categorize parts of a document.  Markup codes such as <tag compl="full" tei="no">para</tag> or <code tei="yes" type="frag">\end{list}</code> simply identify
a portion of a document and assert of it that <q>the following item is
a paragraph,</q> or <q>this is the end of the most recently begun
list,</q> etc.  By contrast, a procedural markup system defines what
processing is to be carried out at particular points in a document:
<q>call procedure PARA with parameters 1, b and x here</q> or <q>move
the left margin 2 quads left, move the right margin 2 quads right,
skip down one line, and go to the new left margin,</q> etc.  In SGML,
the instructions needed to process a document for some particular
purpose (for example, to format it) are sharply distinguished from the
descriptive markup which occurs within the document.  Usually, they
are collected outside the document in separate procedures or programs.</p><p>With descriptive instead of procedural markup the same document can
readily be processed by many different pieces of software, each of
which can apply different processing instructions to those parts of it
which are considered relevant.  For example, a content analysis program
might disregard entirely the footnotes embedded in an annotated text,
while a formatting program might extract and collect them all together
for printing at the end of each chapter. Different sorts of processing
instructions can be associated with the same parts of the file.  For
example, one program might extract names of persons and places from a
document to create an index or database, while another, operating on
the same text, might print names of persons and places in a distinctive
typeface.</p></div3><div3 id="SG112" name="burp" ref="Y"><head>Types of Document</head><p>Secondly, SGML introduces the notion of a <term>document type</term>,
and hence a <term>document type definition</term> (DTD).  Documents are
regarded as having types, just as other objects processed by computers
do.  The type of a document is formally defined by its constituent parts
and their structure.  The definition of a report, for example, might be
that it consisted of a title and possibly an author, followed by an
abstract and a sequence of one or more paragraphs.  Anything lacking a
title, according to this formal definition, would not formally be a
report, and neither would a sequence of paragraphs followed by an
abstract, whatever other report-like characteristics these might have
for the human reader.</p><p>If documents are of known types, a special purpose program (called a
<term>parser</term>) can be used to process a document claiming to be
of a particular type and check that all the elements required for that
document type are indeed present and correctly ordered.  More
significantly, different documents of the same type can be processed in
a uniform way. Programs can be written which take advantage of the
knowledge encapsulated in the document structure information, and which
can thus behave in a more intelligent fashion.</p></div3><div3 id="SG113" name="burp" ref="Y"><head>Data Independence</head><p>A basic design goal of SGML was to ensure that documents encoded
according to its provisions should be transportable from one hardware
and software environment to another without loss of information.  The
two features discussed so far both address this requirement at an
abstract level; the third feature addresses it at the level of the
strings of bytes (characters) of which documents are composed.  SGML
provides a general purpose mechanism for <term>string
substitution</term>, that is, a simple machine-independent way of
stating that a particular string of characters in the document should be
replaced by some other string when the document is processed.  One
obvious application for this mechanism is to ensure consistency of
nomenclature; another, more significant one, is to counter the notorious
inability of different computer systems to understand each other's
character sets, or of any one system to provide all the graphic
characters needed for a particular application, by providing descriptive
mappings for non-portable characters.  The strings defined by this
string-substitution mechanism are called <term>entities</term> and they
are discussed below in section <xref target="SG17"/>.</p></div3></div2><div2 id="SG12" name="bar" ref="Y"><head>Textual Structure</head><p>A text is not an undifferentiated sequence of words, much less of
bytes. For different purposes, it may be divided into many different
units, of different types or sizes.  A prose text such as this one
might be divided into sections, chapters, paragraphs, and sentences.  A
verse text might be divided into cantos, stanzas, and lines.  Once
printed, sequences of prose and verse might be divided into volumes,
gatherings, and pages.</p><p>Structural units of this kind are most often used to identify specific
locations or reference points within a text (<q>the third sentence of
the second paragraph in chapter ten</q>; <q>canto 10, line 1234</q>;
<q>page 412,</q> etc.) but they may also be used to subdivide a text
into meaningful fragments for analytic purposes (<q>is the average
sentence length of section 2 different from that of section 5?</q>
<q>how many paragraphs separate each occurrence of the word
<cited>nature</cited>?</q> <q>how many pages?</q>).  Other
structural
units are more clearly analytic, in that they characterize a section of
a text.  A dramatic text might regard each speech by a different
character as a unit of one kind, and stage directions or pieces of
action as units of another kind.  Such an analysis is less useful for
locating parts of the text (<q>the 93rd speech by Horatio in Act 2</q>)
than for facilitating comparisons between the words used by one
character and those of another, or those used by the same character at
different points of the play.</p><p>In a prose text one might similarly wish to regard as units of
different types passages in direct or indirect speech, passages
employing different stylistic registers (narrative, polemic,
commentary, argument, etc.), passages of different authorship and so
forth.  And for certain types of analysis (most notably textual
criticism) the physical appearance of one particular printed or
manuscript source may be of importance:  paradoxically, one may wish to
use descriptive markup to describe presentational features such as
typeface, line breaks, use of white space and so forth.</p><p>These textual structures overlap with each other in complex and
unpredictable ways.  Particularly when dealing with texts as
instantiated by paper technology, the reader needs to be aware of both
the physical organization of the book and the logical structure of the
work it contains.  Many great works (Sterne's <title>Tristram
Shandy</title> for example) cannot be fully appreciated without an
awareness of the interplay between narrative units (such as chapters or
paragraphs) and page divisions.  For many types of research, it is the
interplay between different levels of analysis which is crucial:  the
extent to which syntactic structure and narrative structure mesh, or
fail to mesh, for example, or the extent to which phonological
structures reflect morphology.</p></div2><div2 id="SG13" name="bar" ref="Y"><head>SGML Structures</head><p>This section describes the simple and consistent mechanism for the
markup or identification of structural textual units which is
provided by SGML.  It also describes the methods SGML provides for
the expression of rules defining how combinations of such
units can meaningfully occur in any text.</p><div3 id="SG131" name="burp" ref="Y"><head>Elements</head><p>The technical term used in the SGML standard for a textual unit,
viewed as a structural component, is <term>element</term>.  Different
types of elements are given different names, but SGML provides no way
of expressing the meaning of a particular type of element, other than
its relationship to other element types.  That is, all one can say
about an element called (for instance) <gi tei="no">blort</gi> is that
instances of it may (or may not) occur within elements of type <gi tei="no">farble</gi>, and that it may (or may not) be decomposed into
elements of type <gi tei="no">blortette</gi>.  It should be stressed that
the SGML standard is entirely unconcerned with the semantics of textual
elements:  these are application dependent.<note source="auth" place="display" anchored="Y">Work is currently going
on in the standards community to create (using SGML syntax) a definition
of a standard <q>document style semantics and specification language</q>
or DSSSL.</note>
It is up to the creators of SGML conformant tag sets (such as these
Guidelines) to choose intelligible names for the elements they identify
and to document their proper use in text markup.  That is one purpose of
this document.  From the need to choose element names indicative of
function comes the technical term for the name of an element type, which
is <term>generic identifier</term>, or GI.</p><p>Within a marked up text (a <term>document instance</term>), each
element must be explicitly marked or tagged in some way.  The standard
provides for a variety of different ways of doing this, the most
commonly used being to insert a tag at the beginning of the element (a
<term>start-tag</term>) and another at its end (an
<term>end-tag</term>).  The start- and end-tag pair are used to bracket
off the element occurrences within the running text, in rather the same
way as different types of parentheses or quotation marks are used in
conventional punctuation.  For example, a quotation element in a
text might be tagged as follows:
 
<eg><![CDATA[    ...  Rosalind's remarks <quote>This is the silliest stuff
     that ere I heard of!</quote> clearly indicate ...]]></eg>
 
As this example shows, a start-tag takes the form
<tag compl="full" tei="no">name</tag>, where the opening angle bracket indicates
the start of the start-tag, <q>name</q> is the generic identifier
of the element which is being delimited, and the closing angle bracket
indicates the end of a tag.  An end-tag takes an identical form, except
that the opening angle bracket is followed by a solidus (slash)
character, so that the corresponding end-tag would be
<tag compl="full" tei="no">/name</tag>.
<note source="auth" place="display" anchored="Y">The actual characters used for the delimiting characters (the angle
brackets, exclamation mark and solidus)<!-- < q ><,< / q > < q ></,< / q > and < q >>< / q > -->
may be redefined, but it is
conventional to use the characters used in this description.</note></p></div3><div3 id="SG132" name="burp" ref="Y"><head>Content Models:  An Example</head><p>An element may be <term>empty</term>, that is, it may have no
content at all, or it may contain simple text.  More usually, however,
elements of one type will be <term>embedded</term> (contained entirely)
within elements of a different type.
 <!-- This is one reason why an end-tag needs to specify       --><!-- which element it is closing.                             -->
 <!-- suppressed by msm.  DB points out that it's inaccurate,  --><!-- and me, I have never quite understood what the           --><!-- connection was.                                          --></p><p>To illustrate this, we will consider a very simple structural model.
Let us assume that we wish to identify within an anthology only poems,
their titles, and the stanzas and lines of which they are composed.  In
SGML terms, our document type is the <term>anthology</term>, and it
consists of a series of <term>poem</term>s.  Each poem has embedded
within it one element, a title, and several occurrences of another, a
stanza, each stanza having embedded within it a number of line elements.
Fully marked up, a text conforming to this model might appear as
follows:
<note source="auth" place="display" anchored="Y">The example is taken from William Blake's <title>Songs of
innocence and experience</title> (1794).  The markup is designed for
illustrative purposes and is not TEI-conformant.</note>
 
<eg><![CDATA[    <anthology>
      <poem><title>The SICK ROSE</title>
         <stanza>
              <line>O Rose thou art sick.</line>
              <line>The invisible worm,</line>
              <line>That flies in the night</line>
              <line>In the howling storm:</line>
         </stanza>
         <stanza>
              <line>Has found out thy bed</line>
              <line>Of crimson joy:</line>
              <line>And his dark secret love</line>
              <line>Does thy life destroy.</line>
         </stanza>
      </poem>
 
              <!-- more poems go here    -->
 
    </anthology>
 ]]></eg></p><p>It should be stressed that this example does <emph>not</emph> use
the same names as are proposed for corresponding elements elsewhere
in these Guidelines: the above is <emph>not</emph> a valid TEI document.
It will however serve as an introduction to the basic notions of SGML.<!-- Added (cautious) note on white space. -lb --><!-- Added note on SGML comments. -msm -->
White space and line breaks have been added to the example for the
sake of visual clarity only; they have no particular significance in the
SGML encoding itself.  Also, the line
 
<eg><![CDATA[              <!-- more poems go here    -->]]></eg>
 
is an SGML <term>comment</term> and is not treated as part of the text.</p><p>This example makes no assumptions about the rules governing,
for example, whether or not a title can appear in places other
than preceding the first stanza, or whether lines can appear
which are not included in a stanza:  that is why its markup
appears so verbose.  In such cases, the beginning and end of
every element must be explicitly marked, because there are no
identifiable rules about which elements can appear where.  In
practice, however, rules can usually be
formulated to reduce the need for so much
tagging.  For example, considering our greatly over-simplified
model of a poem, we could state the following rules:
 
<list type="ordered"><item id="I0">An anthology contains a number of poems and nothing else.</item><item id="I1">A poem always has a single title element
which precedes the first stanza and contains no other elements.</item><item id="I5">Apart from the title, a poem consists only of stanzas.</item><item id="I2">Stanzas consist only of lines
and every line is contained by a stanza.</item><item id="I3">Nothing can follow a stanza
except another stanza or the end of a poem.</item><item id="I4">Nothing can follow a line
except another line or the start of a new stanza.</item></list></p><p><!-- Rephrased inferences -msm -->From these rules, it may be inferred that we do not need to mark the
ends of stanzas or lines explicitly.  From rule
2<!-- liref target=I1 -->
it
follows that we do not need to mark the end of the title---it is implied
by the start of the first stanza.  Similarly, from rules
3 and 1<!-- liref target=I5 --><!-- and --><!-- liref target=I0 -->
it follows that we need not mark the end
of the poem:  since poems cannot occur within poems but must occur
within anthologies, the end of a poem is implied by the start of the
next poem, or by the end of the anthology.<!-- From rule                                                     --><!-- 4                                                             --><!-- liref target=I2 --><!-- it follows that we do not need to mark the start of the first --><!-- line in each stanza:  it is implied by the start of a stanza. -->
Applying these
simplifications, we could mark up the same poem as follows:
 
<eg><![CDATA[    <anthology>
         <poem><title>The SICK ROSE
         <stanza>
              <line>O Rose thou art sick.
              <line>The invisible worm,
              <line>That flies in the night
              <line>In the howling storm:
         <stanza>
              <line>Has found out thy bed
              <line>Of crimson joy:
              <line>And his dark secret love
              <line>Does thy life destroy.
 
         <poem>
              <!-- more poems go here    -->
 
    </anthology>
 ]]></eg></p><p>The ability to use rules stating which elements can be nested
within others to simplify markup is a very important
characteristic of SGML.  Before considering these rules<!-- further, you may like to consider how text marked up in the -->
further, you may wish to consider how text marked up in the
form above could be processed by a computer for very many
different purposes.  A simple indexing program could extract
only the relevant text elements in order to make a list of
titles, or of words used in the poem text; a simple formatting
program could insert blank lines between stanzas, perhaps
indenting the first line of each, or inserting a stanza
number.  Different parts of each poem could be typeset in
different ways.  A more ambitious analytic program could<!-- determine how many stanzas or lines begin with lower-case --><!-- letters and thus (perhaps) in mid-sentence.               -->
relate the use of punctuation marks to stanzaic and metrical divisions.
<note source="auth" place="display" anchored="Y">Note that this simple example has not addressed the problem of marking
elements such as sentences explicitly; the implications of this are
discussed below in section <xref target="SG152"/>.</note>
Scholars wishing to see the implications of changing
the stanza or line divisions chosen by the editor of this poem
can do so simply by altering the position of the tags.  And of
course, the text as presented above can be transported from
one computer to another and processed by any program (or
person) capable of making sense of the tags embedded within it
with no need for the sort of transformations and translations
needed to move word processor files around.</p></div3></div2><div2 id="SG14" name="bar" ref="Y"><head>Defining SGML Document Structures:  The DTD</head><p>Rules such as those described above are the first stage in the
creation of a formal specification for the structure of an SGML
document, or <term>document type definition</term>, usually abbreviated
to <term>DTD</term>.  In creating a DTD, the document designer may be
as lax or as restrictive as the occasion warrants.  A balance must be
struck between the convenience of following simple rules and the
complexity of handling real texts. This is particularly the case when
the rules being defined relate to texts which already exist:  the
designer may have only the haziest of notions as to an ancient text's
original purpose or meaning and hence find it very difficult to specify
consistent rules about its structure.  On the other hand, where a new
text is being prepared to an exact specification, for example for entry
into a textual database of some kind, the more precisely stated the
rules, the better they can be enforced.  Even in the case where an
existing text is being marked up, it may be beneficial to define a
restrictive set of rules relating to one particular view or hypothesis
about the text---if only as a means of testing the usefulness of that
view or hypothesis.  It is important to remember that every document
type definition is an interpretation of a text.  There is no single DTD
which encompasses any kind of absolute truth about a text, although it
may be convenient to privilege some DTDs above others for particular
types of analysis.</p><p>At present, SGML is most widely used in environments where uniformity
of document structure is a major desideratum.  In the production of
technical documentation, for example, it is of major importance that
sections and subsections should be properly nested, that cross
references should be properly resolved and so forth.  In such
situations, documents are seen as raw material to match against
pre-defined sets of rules.  As discussed above, however, the use of
simple rules can also greatly simplify the task of tagging accurately
elements of less rigidly constrained texts.  By making these rules
explicit, the scholar reduces his or her own burdens in marking up and
verifying the electronic text, while also being forced to make explicit
an interpretation of the structure and significant particularities of
the text being encoded.</p><div3 id="SG141" name="burp" ref="Y"><head>An Example DTD</head><p>A DTD is expressed in SGML as a set of declarative statements, using
a simple syntax defined in the standard.  For our simple model of a
poem, the following declarations would be appropriate:
 
<eg><![CDATA[    <!ELEMENT anthology      - -  (poem+)>
    <!ELEMENT poem           - -  (title?, stanza+)>
    <!ELEMENT title          - O  (#PCDATA) >
    <!ELEMENT stanza         - O  (line+)   >
    <!ELEMENT line           O O  (#PCDATA) >]]></eg>
 
These five lines are examples of formal SGML element declarations.  A
declaration, like an element, is delimited by angle brackets; the first
character following the opening bracket must be an exclamation mark,
followed immediately by one of a small set of SGML-defined keywords,
specifying the kind of object being declared.  The five declarations
above are all of the same type:  each begins with an <code tei="yes" type="kw">ELEMENT</code> keyword, indicating that it declares an element,
in the technical sense defined above.  Each consists of three parts:  a
name or group of names, two characters specifying <term>minimization
rules</term>, and a <term>content model.</term> Each of these parts is
discussed further below.  Components of the declaration are separated by
white space, that is one or more blanks, tabs or newlines.</p><p>The first part of each declaration above gives the generic identifier
of the element which is being declared, for example <cited>poem</cited>,
<cited>title</cited>, etc.  It is possible to declare several elements
in one statement, as discussed below.</p></div3><div3 id="SG142" name="burp" ref="Y"><head>Minimization Rules</head><p>The second part of the declaration specifies what are called
<term>minimization rules</term> for the element concerned.  These rules
determine whether or not start- and end-tags must be present in every
occurrence of the element concerned.  They take the form of a pair of
characters, separated by white space, the first of which relates to the
start-tag, and the second to the end-tag.  In either case, either a
hyphen or a letter O (for <q>omissible</q> or <q>optional</q>) must be
given; the hyphen indicating that the tag must be present, and the
letter O that it may be omitted.  Thus, in this example, every element
except <gi tei="no">line</gi> must have a start-tag.  Only the
<gi tei="no">poem</gi> and <gi tei="no">anthology</gi> elements must have
end-tags as
well.
 <!-- If no minimization rules are given for an element,    --><!-- then neither start nor end-tags may be omitted.       --></p></div3><div3 id="SG143" name="burp" ref="Y"><head>Content Model</head><p>The third part of each declaration, enclosed in parentheses, is
called the <term>content model</term> of the element, because it
specifies what element occurrences may legitimately contain.  Contents
are specified either in terms of other elements or using special
reserved words.  There are several such reserved words, of which by far
the most commonly encountered is #PCDATA, as in this example.  This is an
abbreviation for <gloss>parsed character data,</gloss> and it means that the
element being defined may contain any valid character data.  If an SGML
declaration is thought of as a structure like a family tree, with a
single ancestor at the top (in our case, this would be <tag compl="full" tei="no">anthology</tag>), then almost always, following the branches of
the tree downwards (for example, from <gi tei="no">anthology</gi> to <gi tei="no">poem</gi> to <gi tei="no">stanza</gi> to <gi tei="no">line</gi> and
<gi tei="no">title</gi>) will lead eventually to #PCDATA. In our example,
<gi tei="no">title</gi> and <gi tei="no">line</gi> are so defined. Since
their content models say #PCDATA only and name no embedded elements, they
may not contain any embedded elements.</p></div3><div3 id="SG144" name="burp" ref="Y"><head>Occurrence Indicators</head><p>The declaration for <gi tei="no">stanza</gi> in the example above
states that a stanza consists of one or more lines.  It uses an
<term>occurrence indicator</term> (the plus sign) to indicate how many
times the element named in its content model may occur.  There are three
occurrence indicators in the SGML syntax, conventionally represented by
the plus sign, the question mark, and the asterisk or star.
<note source="auth" place="display" anchored="Y"><!-- Added footnote. -msm -->Like the delimiters, these are assigned formal names by
the standard and may be redefined with an appropriate SGML
declaration.</note>
The plus
sign means that there may be one or more occurrences of the element
concerned; the question mark means that there may be at most one and
possibly no occurrence; the star means that the element concerned may
either be absent or appear one or more times.  Thus, if the content
model for <gi tei="no">stanza</gi> were <code tei="yes" type="frag">(LINE*)</code>,
stanzas with no lines would be possible as well as those with more than
one line.  If it were <code tei="yes" type="frag">(LINE?)</code>, again empty
stanzas would be countenanced, but no stanza could have more than a
single line.  The declaration for <gi tei="no">poem</gi> in the example
above thus states that a <gi tei="no">poem</gi> cannot have more than one
title, but may have none, and that it must have at least one <gi tei="no">stanza</gi> and may have several.
 <!-- It uses an                                                 --><!-- occurrence indicator (the plus sign) to                    --><!-- indicate how many times the element named in its           --><!-- content model may occur.  There are three occurrence       --><!-- indicators, known in the standard as                       --><!-- X     plus       ,       opt        and                    --><!--     m>rep    rm>.  Plus, which is usually represented      --><!-- by a plus sign, means that there may be one or more        --><!-- occurrences of the element concerned; opt, usually         --><!-- represented by a question mark, means that there may       --><!-- be at most one and possibly no occurrence; rep,            --><!-- usually represented by a star, means that the element      --><!-- concerned may either be absent or appear one or more       --><!-- times.  Thus, if the content model for STANZA were         --><!-- (LINE*), stanzas with no lines would be possible as        --><!-- well as those with more than one line.  If it were         --><!-- (LINE?), again empty stanzas would be countenanced,        --><!-- but no stanza could have more than a single line.          --></p></div3><div3 id="SG145" name="burp" ref="Y"><head>Group Connectors</head><p>The content model <code tei="yes" type="frag">(TITLE?, STANZA+)</code> contains
more than one component, and thus needs additionally to specify the
order in which these elements (<gi tei="no">title</gi> and <gi tei="no">stanza</gi>) may appear.  This ordering is determined by the
<term>group connector</term> (the comma) used between its components.
There are three possible group connectors, conventionally represented by
comma, vertical bar, and ampersand.
<note source="auth" place="display" anchored="Y"><!-- Added footnote. -msm -->What are here called <q>group connectors</q> are referred to by the SGML
standard simply as <q>connectors</q>; the longer term is preferred here
to stress the fact that these connectors are used only in SGML model
groups and name groups.  Like the delimiters and the occurrence
indicators, group connectors are assigned formal names by the standard
and may be redefined with an appropriate SGML declaration.</note>
The comma means that the components it connects must both appear in the
order specified by the content model. The ampersand indicates that the
components it connects must both appear but may appear in any order.
The vertical bar indicates that only one of the components it connects
may appear.  If the comma in this example were replaced by an
ampersand, a title could appear either before the stanzas of a <gi tei="no">poem</gi> or at the end (but not between stanzas).  If it were
replaced by a vertical bar, then a <gi tei="no">poem</gi> would consist of
either a title or just stanzas---but not both!</p></div3><div3 id="SG146" name="burp" ref="Y"><head>Model Groups</head><p>In our example so far, the components of each content model have been
either single elements or #PCDATA.  It is quite permissible however to
define content models in which the components are lists of elements,
combined by group connectors.  Such lists, known as <term>model
groups</term>, may also be modified by occurrence indicators and
themselves combined by group connectors.  To demonstrate these
facilities, let us now expand our example to include non-stanzaic types
of verse.  For the sake of demonstration, we will categorize poems as
one of <term>stanzaic</term>, <term>couplets</term>, or
<term>blank</term> (or <term>stichic</term>).  A blank-verse poem
consists simply of lines (we ignore the possibility of verse paragraphs
for the moment)
<note source="auth" place="display" anchored="Y">It will not have escaped the astute reader that the fact that verse
paragraphs need not start on a line boundary seriously complicates the
issue; see further section <xref target="SG152"/>.</note>
so no additional elements need be defined for it.  A couplet is defined
as a <gi tei="no">line1</gi> followed by a <gi tei="no">line2</gi>.
 
<eg><![CDATA[<!ELEMENT couplet O O (line1, line2) >]]></eg>
 <!-- Can't believe it's a good idea to use as an example --><!-- something we would never do ourselves.              --><!-- Why not define SONNET, OCTET, QUATRAIN, SESTET?     --></p><p>The elements <gi tei="no">line1</gi> and <gi tei="no">line2</gi> (which
are distinguished to enable studies of rhyme scheme, for example) have
exactly the same content model as the existing <gi tei="no">line</gi>
element.  They can therefore share the same declaration.  In this
situation, it is convenient to supply a <term>name group</term> as the
first component of a single element declaration, rather than give a
series of declarations differing only in the names used.  A name group
is a list of GIs connected by any group connector and enclosed in
parentheses, as follows:
 
<eg><![CDATA[<!ELEMENT (line | line1 | line2) O O (#PCDATA) >]]></eg>
 
The declaration for the <gi tei="no">poem</gi> element can now be changed
to include all three possibilities:
 
<eg><![CDATA[<!ELEMENT poem - O (title?, (stanza+ | couplet+ | line+) ) >]]></eg>
 
That is, a poem consists of an optional title, followed by one or
several stanzas, or one or several couplets, or one or several lines.
Note the difference between this definition and the following:
 
<eg><![CDATA[<!ELEMENT poem - O (title?, (stanza | couplet | line)+ ) >]]></eg>
 
The second version, by applying the occurrence indicator to the group
rather than to each element within it, would allow for a single poem to
contain a mixture of stanzas, couplets or blank verse.</p><p>Quite complex models can easily be built up in this way, to match
the structural complexity of many types of text.  As a further example,
consider the case of stanzaic verse in which a refrain or chorus
appears.  A refrain may be composed of repetitions of the line element,
or it may simply be text, not divided into verse lines.  A refrain can
appear at the start of a poem only, or as an optional addition
following each stanza.  This could be expressed by a content model such
as the following:
 
<eg><![CDATA[ 
<!ELEMENT refrain - - (#PCDATA | line+)>
<!ELEMENT poem    - O (title?,
                      ( (line+)
                      | (refrain?, (stanza, refrain?)+ ) )) >]]></eg>
 
That is, a poem consists of an optional title, followed by either
a sequence of lines, or an un-named group, which starts with an
optional refrain, followed by one of more occurrences of another group,
each member of which is composed of a stanza followed by an optional
refrain.  A sequence such as <cited>refrain - stanza - stanza - refrain</cited>
follows this pattern, as does the sequence <cited>stanza - refrain -
stanza
- refrain</cited>.  The sequence <cited>refrain - refrain - stanza -
stanza</cited>
does not, however, and neither does the sequence <q>stanza - refrain -
refrain - stanza.</q>  Among other conditions made explicit by this
content model are the requirements that at least one stanza must appear
in a poem, if it is not composed simply of lines, and that if there is
both a title and a stanza they must appear in that order.</p></div3></div2><div2 id="SG15" name="bar" ref="Y"><head>Complicating the Issue:  More on Element Declarations</head><p>In the simple cases described so far, it has been assumed that one
can identify the immediate constituents of every element defined in a
textual structure.  A poem consists of stanzas, and an anthology
consists of poems.  Stanzas do not float around unattached to poems or
combined into some other unrelated element; a poem cannot contain an
anthology.  All the elements of a given document type may be arranged
into a hierarchic structure, arranged like a family tree with a single
ancestor at the top and many children (mostly the elements containing
#PCDATA) at the bottom.  This gross simplification turns out to be
surprisingly effective for a large number of purposes.  It is not
however adequate for the full complexity of real textual structures.  In
particular, it does not cater for the case of more or less freely
floating elements that can appear at almost any hierarchic level in the
structure, and it does not cater for the case where different elements
overlap or several different trees may be identified in the same
document.  To deal with the first case, SGML provides the
<term>exception</term> mechanism; to deal with the second, SGML permits
the definition of <soCalled>concurrent</soCalled> document structures.</p><div3 id="SG151" name="burp" ref="Y"><head>Exceptions to the Content Model</head><p>In most documents, there will be some elements
that can occur at any level of its structure.  Annotations, for
example, might be attached to the whole of a poem, to a
stanza, to a line of a stanza or to a single word within it.
In a textual critical edition, the same might be true of
variant readings.  In this simple case, the complexity of
adding an annotation element as an optional component of every
content model is not particularly onerous; in a more
realistically complex model perhaps containing some ten or
twenty levels such an approach can become much more difficult.<!-- It would not make much sense to include optional         --><!-- annotation elements explicitly as a component of every   --><!-- element in even a moderately complex DTD.                --><!-- Suppressed above on grounds that since the TEI does      --><!-- it, we probably shouldn't say it makes no sense.         --><!-- (msm)                                                    --></p><p>To cope with this, SGML allows for any content model to be
further modified by means of an <term>exception</term> list.
There are two types of exception:  <term>inclusions</term>,
that is, additional elements that can be included at any point
in the model group or any of its constituent elements; and
<term>exclusions</term>, that is, elements that cannot be
included within the current model.</p><p>To extend our declarations further to allow for annotations
and variant readings, which we will assume can appear anywhere
within the text of a poem, we first need to add declarations
for these two elements:
 
<eg><![CDATA[<!ELEMENT (note | variant) - - (#PCDATA)>]]></eg>
 
The note and variant elements must have both start- and end-tags,
since they can appear anywhere.  Rather than add them to
the content model for each type of poem, we can add them in
the form of an inclusion list to the poem element, which now
reads:
 
<eg><![CDATA[<!ELEMENT poem - O (title?, (stanza+ | couplet+ | line+) )
                                         +(note | variant) >]]></eg>
 
The plus sign at the start of the (NOTE | VARIANT) name list
indicates that this is an inclusion exception.  With this
addition, notes or variants can appear at any point in the
content of a poem element---even those (such as <gi tei="no">title</gi>)
for which we have defined a content model of #PCDATA.  They can thus also
appear within notes or variants!</p><p>If we wanted for some reason to prevent notes or variants appearing
within titles, we could add an exclusion exception to the declaration
for <gi tei="no">title</gi> above:
 
<eg><![CDATA[<!ELEMENT title  - O  (#PCDATA)  -(note | variant) >]]></eg>
 
The minus sign at the start of the (NOTE | VARIANT) name list indicates
that this is an exclusion exception.  With this addition, notes and
variants will be prohibited from appearing within titles,
notwithstanding their potential inclusion implied by the previous
addition to the content model for <gi tei="no">poem</gi>.</p><p>In the same way, we could prevent notes and variants
from nesting within notes and variants by modifying the
definition above to read
 
<eg><![CDATA[<!ELEMENT (note | variant) - - (#PCDATA)  -(note | variant) >]]></eg>
 
The meticulous reader will note that this precludes both
variants within notes and notes within variants.  Inclusion and
exclusion exceptions should be used with care as their
ramifications may not be immediately apparent.</p></div3><div3 id="SG152" name="burp" ref="Y"><head>Concurrent Structures<!-- this section should probably be killed --></head><p>All the structures we have so far discussed have been simply
hierarchic:  that is, at every level of the tree, each node is entirely
contained by a parent node.  The figure below represents the structure
of a document conforming to the simple DTD we have so far defined as a
tree (drawn on its side through exigencies of space).  We have already
seen how Blake's poem can be divided into a title and two stanzas, each
of four lines.  In this diagram, we add a second poem, consisting of
one stanza and a title, to make up an instance of an anthology:
 
<eg><![CDATA[                         |-------------------title
                         |
                         |              |----line1
                         |              |----line2
          |------POEM1---|----stanza1---|----line3
          |              |              |----line4
          |              |
          |              |              |----line5
          |              |----stanza2---|----line6
          |                             |----line7
          |                             |----line8
anthology-|
          |
          |              |-------------------title
          |              |
          |              |              |----line1
          |              |              |----line2
          |------POEM2---|----stanza1---|----line3
                                        |----line4
                                        |----line5]]></eg></p><p>Clearly, there are many such trees that might be drawn to describe
the structure of this or other anthologies.  Some of them might be
representable as further subdivisions of this tree:  for example, we
might subdivide the lines into individual words, since no word crosses a
line boundary.  But equally clearly there are many other trees that
might be drawn which do <emph>not</emph> fit within this tree.  We
might, for example, be interested in syntactic structures --- which
rarely respect the formal boundaries of verse.  Or, to take a simpler
example, we might want to represent the pagination of different editions
of the same text.</p><p>One way of doing this would be to group the lines and titles of our
current model into pages.  A declaration for such an element is simple
enough:
 
<eg><![CDATA[<!ELEMENT page - - ((title?, line+)+)   >]]></eg>
 
That is, a page consists of one or more unnamed groups, each of which
contains an optional title, followed by a sequence of lines.  (Note,
incidentally, that this model prohibits a title appearing on its own at
the foot of a page).  However, simply inserting the element <tag compl="full" tei="no">page</tag> into the hierarchy already defined is not as easy as
it might seem.  Some poems are longer than a single page, and other
pages contain more than one poem.  We cannot therefore insert the
element <gi tei="no">page</gi> between <gi tei="no">anthology</gi> and <gi tei="no">poem</gi> in the hierarchy, nor can it go between <gi tei="no">poem</gi> and <gi tei="no">stanza</gi>, nor yet in both places at
once!  What is needed is the ability to create a separate hierarchy,
with the same elements at the bottom (the stanzas, lines and titles),
but combined into a different superstructure.  This is the ability which
the CONCUR feature of SGML gives.</p><p>A separate document type definition must be created for each
hierarchic tree into which the text is to be structured.  The
definition we have so far built up for the anthology looks, in
full, like this:
 
<eg><![CDATA[    <!DOCTYPE anthology [
    <!ELEMENT anthology      - -  (poem+)             >
    <!ELEMENT poem           - -  (title?, stanza+)   >
    <!ELEMENT stanza         - O  (line+)             >
    <!ELEMENT (title | line) - O  (#PCDATA)           >
    ]>]]></eg>
 
As this example shows, the name of a document type must always be
the same as the name of the largest element in it, that is the
element at the top of the hierarchy.  The syntax used is discussed
further below (see section <xref target="SG182"/>).  Let us now add to
this declaration a second definition for a concurrent document
type, which we will call a paged anthology, or <tag compl="full" tei="no">p.anth</tag>
for short:
 
<eg><![CDATA[    <!DOCTYPE p.anth [
    <!ELEMENT p.anth         - -  (page+)               >
    <!ELEMENT page           - -  ((title?, line+)+)    >
    <!ELEMENT (title|line)   - O  (#PCDATA)             >
    ]>]]></eg></p><p>We have now defined two different ways of looking at the same basic
text---the PCDATA components grouped by both these document type
definitions into lines or titles.  In one view, the lines are
grouped into stanzas and poems; in the other they are grouped into
pages only.  Notice that it is exactly the same text
which is visible in both views:  the two hierarchies simply allow
us to arrange it in two different ways.</p><p>To mark up the two views, it will be necessary to indicate which
hierarchy each element belongs to.  This is done by including the name
of the document type (the view) within parentheses immediately before
the identifier concerned, inside both start- and end-tags.  Thus, pages
(which are only visible in the <gi tei="no">p.anth</gi> document type)
must be tagged with a <tag compl="full" tei="no">(p.anth)page</tag> tag at their start
and a <tag compl="full" tei="no">/(p.anth)page</tag> at their end. In the same way, as
poems and stanzas appear only in the <gi tei="no">anthology</gi> document
type, they must now be tagged using <tag compl="full" tei="no">(anthology)poem</tag>
and <tag compl="full" tei="no">(anthology)stanza</tag> tags respectively.  For the
line and title elements, however, which appear in both hierarchies, no
document type specification need be given:  any tag containing only a
name is assumed to mark an element present in every active document
type.</p><p>As a simple example, let us assume that Blake's poem appears in
some paged anthology, with the page break occurring half way
through the first stanza.  The poem might then be marked up as
follows:
 
<eg><![CDATA[    <(anthology)anthology>
    <(p.anth)p.anth>
    <(p.anth)page>
 
    <!--      other titles and lines on this page here -->
 
         <(anthology)poem><title>The SICK ROSE
         <(anthology)stanza>
              <line>O Rose thou art sick.
              <line>The invisible worm,
    </(p.anth)page>
    <(p.anth)page>
              <line>That flies in the night
              <line>In the howling storm:
         <(anthology)stanza>
              <line>Has found out thy bed
              <line>Of crimson joy:
              <line>And his dark secret love
              <line>Does thy life destroy.
         </(anthology)poem>
 
    <!--      rest of material on this page here    -->
    </(p.anth)page>
 
    </(p.anth)p.anth)
    </(anthology)anthology>]]></eg></p><p>It is now possible to select only the elements concerned with a
particular view from the text, even though both are
represented in the tagging.  A processor concerned only with the
pagination will see only those elements whose tags include the
P.ANTH specification, or which have no specification at all.  A
processor concerned only with the ANTHOLOGY view of things will
not see the page breaks.  And a processor concerned to inter-relate
the two views can do so unambiguously.</p><p>A note of caution is appropriate:  CONCUR is an optional feature of
SGML, and not all available SGML software systems support it, while
those which do, do not always do so according to the letter of the
standard.  For that reason, if for no other, wherever these Guidelines
have identified a potential application of CONCUR, they also invariably
suggest alternative methods as well.
For fuller discussion of these issues, see chapter <xref target="NH"/>.
 <!-- For an alternative, and possibly --><!-- simpler, way of dealing with the problems of marking page --><!-- boundaries and similar concurrent hierarchies, see section --><!-- xref target=>. --></p><p>Note also that we cannot introduce a new element, a page number for
example, into the <gi tei="no">p.anth</gi> document type, since there is
no existing data in the <gi tei="no">anthology</gi> document type which
could be fitted into it. One way of adding that extra information is
discussed in the next section.</p></div3></div2><div2 id="SG16" name="bar" ref="Y"><head>Attributes</head><p>In the SGML context, the word <cited>attribute</cited>, like some other
words, has a specific technical sense.  It is used to describe
information which is in some sense descriptive of a specific element
occurrence but not regarded as part of its content. For example, you
might wish to add a <att tei="no">status</att> attribute to occurrences of
some
elements in a document to indicate their degree of reliability, or to
add an <att tei="no">identifier</att> attribute so that you could refer to
particular element occurrences from elsewhere within a document.
Attributes are useful in precisely such circumstances.</p><p>Although different elements may have attributes with the same name,
(for example, in the TEI scheme, every element is defined as having an
<att tei="yes">id</att> attribute), they are always regarded as different, and
may have different values assigned to them.  If an element has been
defined as having attributes, the attribute values are supplied in the
document instance as <term>attribute-value pairs</term> inside the
start-tag for the element occurrence. An end-tag may not contain an
attribute-value specification, since it would be redundant.</p><p>For example
 
<eg><![CDATA[<poem id=P1 status="draft"> ... </poem>]]></eg>
 
The <tag compl="full" tei="no">poem</tag> element has been defined as having two
attributes:  <att tei="yes">id</att> and <att tei="yes">status.</att> For the instance of a
<tag compl="full" tei="no">poem</tag> in this example, represented here by an ellipsis,
the <att tei="yes">id</att> attribute has the value <code tei="yes" type="val">P1</code> and
the <att tei="yes">status</att> attribute has the value <code tei="yes" type="val">draft.</code> An SGML processor can use the values of the
attributes in any way it chooses; for example, a formatter might print a
poem element which has the status attribute set to <code tei="yes" type="val">draft</code> in a different way from one with the same
attribute set to <code tei="yes" type="val">revised</code>; another processor might
use the same attribute to determine whether or not poem elements are to
be processed at all.  The <att tei="yes">id</att> attribute is a slightly special
case in that, by convention, it is always used to supply a unique value
to identify a particular element occurrence,<!-- added next line.  -msm -->
which can be used for cross reference purposes, as discussed further
below.<!-- N.B. ID is allowed to have other functions. -msm --></p><p>Like elements, attributes are declared in the SGML document type
declaration, using rather similar syntax.  As well as specifying its
name and the element to which it is to be attached, it is possible to
specify (within limits) what kind of value is acceptable for an
attribute and a default value.</p><p>The following declarations could be used to define the two attributes
we have specified above for the <gi tei="no">poem</gi> element:
 
<eg><![CDATA[<!ATTLIST poem
          id       ID                              #IMPLIED
          status   (draft | revised | published)   draft        >]]></eg></p><p>The declaration begins with the symbol <code tei="yes" type="kw">ATTLIST</code>,
which introduces an <term>attribute list specification</term>.  The
first part of this specifies the element (or elements) concerned.  In
our example, attributes have been declared only for the <gi tei="no">poem</gi> element.  If several elements share the same
attributes, they may all be defined in a single declaration; just as
with element declarations, several names may be given in a parenthesized
list.  Following this name (or list of names), is a series of rows, one
for each attribute being declared, each containing three parts.  These
specify the name of the attribute, the type of value it takes, and a
default value respectively.</p><p>Attribute names (<att tei="no">id</att> and <att tei="no">status</att> in
this example) are subject to the same restrictions as other names in
SGML; they need not be unique across the whole DTD, however, but only
within the list of attributes for a given element.</p><p>The second part of an attribute specification can take one of two
forms, both illustrated above.  The first case uses one of a number of
special keywords to declare what kind of value an attribute may take.
In the example above, the special keyword <code tei="yes" type="kw">ID</code> is
used to indicate that the attribute <att tei="no">ID</att> will be used to
supply a unique identifying value for each poem instance (see further
the discussion below).  Among other possible SGML keywords are
 
<list type="gloss"><label>CDATA</label><item>The attribute value may contain any valid character
data; tags may be included in the value, but they will not be recognized
by the SGML parser, and will not be processed as tags normally are</item><label>IDREF</label><item>The attribute value must contain a pointer to some
other element (see further the discussion of ID below)</item><label>NMTOKEN</label><item>The attribute value is a <term>name token</term>,
that is, (more or less) any string of alphanumeric characters</item><label>NUMBER</label><item>The attribute value is composed only of numerals</item></list>
 <!-- changed def of NUMBER above from math to graphics. -msm --><!-- replaced NMTOKEN with NAME                         -msm --><!-- restored NMTOKEN since I was wrong                 -msm --></p><p>In the example above, a list of the possible values for the <att tei="no">status</att> attribute has been supplied.  This means that a
parser can check that no <gi tei="no">poem</gi> is defined for which the
<att tei="yes">status</att> attribute does not have one of <code tei="yes" type="val">draft</code>, <code tei="yes" type="val">revised</code>, or <code tei="yes" type="val">published</code> as its value.  Alternatively, if the declared
value had been either CDATA or NAME, a parser would have accepted almost
any string of characters (<code tei="yes" type="frag">status=awful</code> or <code tei="yes" type="frag">status=12345678</code> if it had been a <code tei="yes" type="kw">NMTOKEN</code>; <code tei="yes" type="frag">status="anything goes"</code> or
<code tei="yes" type="frag">status = "well, ALMOST anything"</code> if
it were <code tei="yes" type="kw">CDATA</code>).  Sometimes, of course, the set of
possible values cannot be pre-defined.  Where it can, as in this case,
it is generally better to do so.
 <!-- <code type=frag>status = "well, <emph>almost</emph>      --><!-- anything"</code>                                         -->
 <!-- DB objects to having the EMPH tag inside a literal.      --><!-- So does RC, who thinks it will mislead novices.          --><!-- Joke doesn't seem so funny to me anymore either, so      --><!-- have deleted it.  (msm)                                  --></p><p>The last piece of each information in each attribute definition
specifies how a parser should interpret the absence of the
attribute concerned.  This can be done by supplying one of the
special keywords listed below, or (as in this case) by supplying
a specific value which is then regarded as the value for every
element which does not supply a value for the attribute concerned.
Using the example above, if a poem is simply tagged
<tag compl="full" tei="no">poem</tag>, the parser will treat it exactly as if it were
tagged <tag compl="full" tei="no">poem status=draft</tag>.  Alternatively, one of the
following keywords may be used to specify a default value for an
attribute:
 
<list type="gloss"><label>#REQUIRED</label><item>A value must be specified.</item><label>#IMPLIED</label><item>A value need not be supplied (as in the case of
<att tei="yes">ID</att> above).</item><label>#CURRENT</label><item>If no value is supplied in this element
occurrence, the last specified value should be used.</item></list></p><p>For example, if the attribute definition above were rewritten as
 
<eg><![CDATA[<!ATTLIST poem
          id       ID                             #IMPLIED
          status   (draft | revised | published)  #CURRENT      >]]></eg>
 
 
then poems which appear in the anthology simply tagged <tag compl="full" tei="no">poem</tag> would be treated as if they had the same status as the
preceding poem.  If the keyword were #REQUIRED rather than #CURRENT, the
parser would report such poems as erroneously tagged, as it would if any
value other than <code tei="yes" type="val">draft,</code> <code tei="yes" type="val">published,</code> or <code tei="yes" type="val">revised</code> were
supplied.  The use of #CURRENT implies that whatever value is specified
for this attribute on the first poem will apply to all subsequent poems,
until altered by a new value.  Only the status of the first poem need
therefore be supplied, if all are the same.</p><p>It is sometimes necessary to refer to an occurrence of one textual
element from within another, an obvious example being phrases such as
<q>see note 6</q> or <q>as discussed in chapter 5.</q>  When a text is
being produced the actual numbers associated with the notes or chapters
may not be certain.  If we are using descriptive markup, such
things as page or chapter numbers, being entirely matters of
presentation, will not in any case be present in the marked up text:
they will be assigned by whatever processor is operating on the text
(and may indeed differ in different applications).  SGML therefore
provides a special mechanism by which any element occurrence may be
given a special identifier, a kind of label, which may be used to refer
to it from anywhere  else within the same text.  The cross-reference
itself is regarded as an element occurrence of a specific kind, which
must also be declared in the DTD.  In each case, the identifying label
(which may be arbitrary) is supplied as the value of a special
attribute.</p><p>Suppose, for example, we wish to include a reference within
the notes on one poem that refers to another poem.  We will
first need to provide some way of attaching a label to each
poem:  this is done by defining an attribute for the
<gi tei="no">poem</gi> element, as suggested above.
 
<eg><![CDATA[<!ATTLIST poem
          id       ID     #IMPLIED >]]></eg></p><p>Here we define an attribute <att tei="yes">id</att>, the value of which must be
of type <code tei="yes" type="kw">ID</code>.  It is not required that any attribute
of type <code tei="yes" type="kw">ID</code> have the name <att tei="no">id</att> as
well; it is however a useful convention almost universally observed.
Note that not every poem need carry an <att tei="yes">id</att> attribute and the
parser may safely ignore the lack of one in those which do not.  Only
poems to which we intend to refer need use this attribute; for each such
poem we should now include in its start-tag some unique identifier, for
example:
 
<eg><![CDATA[         <poem id=ROSE>
              Text of poem with identifier 'ROSE'
         </poem>
 
         <poem id=P40>
              Text of poem with identifier 'P40'
         </poem>
 
         <poem>
              This poem has no identifier
         </poem>
 ]]></eg></p><p>Next we need to define a new element for the cross reference
itself.  This will not have any content---it is only a
pointer---but it has an attribute, the value of which will be
the identifier of the element pointed at.  This is achieved by
the following declarations:
 
<eg><![CDATA[    <!ELEMENT poemref - O EMPTY                  >
    <!ATTLIST poemref     target IDREF #REQUIRED >]]></eg></p><p>The <gi tei="no">poemref</gi> element needs no end-tag because it has
no content.  It has a single attribute called <att tei="yes">target</att>.  The
value of this attribute must be of type IDREF (the keyword used for
cross reference pointers of this type) and it must be supplied.</p><p>With these declarations in force, we can now encode a reference to
the poem with id <code tei="yes" type="val">Rose</code> as follows:
 
<eg><![CDATA[    Blake's poem on the sick rose <poemREF target=ROSE> ...]]></eg></p><p>When an SGML parser encounters this empty element it will simply
check that an element exists with the identifier <code tei="yes" type="val">Rose</code>.  Different SGML processors could take any number
of additional actions:  a formatter might construct an exact page and
line reference for the location of the poem in the current document and
insert it, or just quote the poem's title or first lines.  A hypertext
style processor might use this element as a signal to activate a link to
the poem being referred to.  The purpose of the SGML markup is simply to
indicate that a cross reference exists:  it does not determine what the
processor is to do with it.</p></div2><div2 id="SG17" name="bar" ref="Y"><head>SGML Entities</head><p>The aspects of SGML discussed so far are all concerned with the
markup of structural elements within a document.  SGML also provides a
simple and flexible method of encoding and naming arbitrary parts of
the actual content of a document in a portable way.  In SGML the word
<term>entity</term> has a special sense:  it means a named part of a
marked up document, irrespective of any structural considerations.  An
entity might be a string of characters or a whole file of text.  To
include it in a document, we use a construction known as an
<term>entity reference</term>.  For example, the following declaration
 
<eg><![CDATA[<!ENTITY tei "Text Encoding Initiative">]]></eg>
 
defines an entity whose name is <ident rend="noindex" tei="yes" type="ge">tei</ident> and whose value is the string <q>Text Encoding
Initiative.</q> <note source="auth" place="display" anchored="Y">By convention case is significant in entity
names, unlike element names.</note> This is an instance of an
<term>entity declaration</term>, which declares an <term>internal
entity</term>.  The following declaration, by contrast, declares an
<term>external entity</term> (sometimes called, loosely, a
<term>system entity</term>):
 
<eg><![CDATA[<!ENTITY ChapTwo SYSTEM "sgmlmkup.txt">]]></eg>
 
This defines an external entity whose name is <ident rend="noindex" tei="yes" type="ge">ChapTwo</ident> and whose value is the text associated
with the system identifier --- in this case, the system identifier is
the name of an operating system file and the replacement text of the
entity is the contents of the file.<note source="auth" place="display" anchored="Y">Strictly speaking, SGML does
not require system identifiers to be operating-system file names,
nor need external entities be files at all; they can in principle be
any data source available to the SGML processor:  files, results of
database queries, results of calls to system functions, Web pages ---
anything at all.  System identifiers can be any method of naming
the entity which the SGML parser's interface to its operating
environment can use to elicit the data from the environment.
It is simpler, however, when first learning SGML, to
think of external entities as referring to files, and this discussion
therefore ignores the other possibilities.  All existing SGML
processors do support the use of external entities to refer to files;
fewer support the other possible uses of external entities.</note></p><p>System identifiers are, by their nature, system dependent; in
the interests of data portability, therefore, SGML provides another
way of naming external entities:
<eg><![CDATA[<!ENTITY p3.sg PUBLIC "-//TEI//TEXT Guidelines Chapter on SGML//EN" >]]></eg>
The <code tei="yes" type="kw">SYSTEM</code> has been replaced by
<code tei="yes" type="kw">PUBLIC</code>, and the system identifier
has been replaced by a <term>public identifier</term>.
Public identifiers can (in principle) take virtually any form;
it is usual to use the form shown above (also known as a
<term>formal public identifier</term>), in which the delimiters
<cited>//</cited> divide the identifier into the following
parts:
<list type="simple"><label>TEI</label><item>indicates the owner of this public identifier (often
but not necessarily the owner of the data in question); the
preceding <cited>-</cited> signals that this particular
owner identifier is not registered with ISO (a <cited>+</cited>
would imply that one could find out the full name and address
of the owner from the official registry of owner identifiers)</item><label>TEXT</label><item>is a keyword indicating the nature of the entity:  other
legal values are <code tei="yes" type="frag">DOCUMENT</code> (for full SGML documents),
<code tei="yes" type="frag">DTD</code> (for document type definitions),
<code tei="yes" type="frag">ELEMENTS</code> (for sets of element declarations),
<code tei="yes" type="frag">ENTITIES</code> (for sets of entity declarations), 
and a number of others which are less frequently needed and
will not be discussed here.</item><label>Guidelines Chapter on SGML</label><item>gives a descriptive name to the entity.</item><label>EN</label><item>is the ISO language code for the language in which
the entity is written.</item></list>
Public identifiers do help make SGML documents less dependent
on particular computer systems, but they do require SGML systems
to provide mechanisms
for mapping from the public identifiers to file identifiers or other
system identifiers.  (The most widely used such mechanism at
this time is the SGML Open Catalog format described briefly
below in section <xref target="SGPATANC"/>.</p><p>Once an entity has been declared, it may be referenced anywhere
within a document.  This is done by supplying its name prefixed with
the ampersand character and followed by the semicolon.  The semicolon
may be omitted if the entity reference is followed by a space or record
end.</p><p>When an SGML parser encounters such an <term>entity
reference,</term> it immediately substitutes the value declared for
the entity name. Thus, the passage <q>The work of the &amp;amp;tei has
only just begun</q> will be interpreted by an SGML processor exactly
as if it read <q>The work of the Text Encoding Initiative has only
just begun</q>. In the case of an external entity, it is, of course,
the contents of the operating system file which are substituted, so
that the passage <q>The following text has been suppressed:
&amp;amp;ChapTwo;</q> will be expanded to include the whole of whatever
the system finds in the file <ident rend="noindex" tei="yes" type="file">sgmlmkup.txt</ident>.</p><p>This obviously saves typing, and simplifies the task of maintaining
consistency in a set of documents.  If the printing of a complex
document is to be done at many sites, the document body itself might use
an entity reference, such as <code tei="yes" type="frag">&amp;amp;site;</code>, wherever
the name of the site is required.  Different entity declarations could
then be added at different sites to supply the appropriate string to be
substituted for this name, with no need to change the text of the
document itself.</p><p>This <term>string substitution</term> mechanism has many other
applications.  It can be used to circumvent the notorious inadequacies
of many computer systems for representing the full range of graphic
characters needed for the display of modern English (let alone the
requirements of other modern scripts or of ancient languages).
So-called <soCalled>special characters</soCalled> not directly
accessible from the keyboard (or if accessible not correctly
translated when transmitted) may be represented by an entity
reference.</p><p>Suppose, for example, that we wish to encode the use of ligatures in
early printed texts.  The ligatured form of <cited>ct</cited> might be
distinguished from the non-ligatured form by encoding it as <code tei="yes" type="frag">&amp;amp;ctlig;</code> rather than <code tei="yes" type="frag">ct.</code>
Other special typographic features such as leafstops or rules could
equally well be represented by mnemonic entity references in the text.
When processing such texts, an entity declaration would be added giving
the desired representation for such textual elements.  If, for example,
ligatured letters are of no interest, we would simply add a declaration
such as
 
<eg><![CDATA[<!ENTITY ctlig "ct" >]]></eg>
 
and the distinction present in the source document would be removed.
If, on the other hand, a formatting program capable of representing
ligatured characters is to be used, we might replace the entity
declaration to give whatever sequence of characters such a program
requires as the expansion.</p><p>A list of entity declarations is known as an <term>entity set</term>.
Standard entity sets are provided for use with most SGML processors, in
which the names used will normally be taken from the lists of such names
published as an annex to the SGML standard and elsewhere, as mentioned
above.</p><p>The replacement values given in an entity declaration are, of course,
highly system dependent.  If the characters to be used in them cannot be
typed in directly, SGML provides a mechanism to specify characters by
their numeric values, known as <term>character references</term>.  A
character reference is distinguished from other characters in the
replacement string by the fact that it begins with a special symbol,
conventionally the sequence <cited>&amp;#</cited>, and ends with the
normal semicolon.  For example, if the formatter to be used represents
the ligatured form of ct by the characters c and t prefixed by the
character with decimal value 102, the entity declaration would read:
 
<eg><![CDATA[<!ENTITY ctlig "&#102;ct" >]]></eg>
 
Note that character references will generally not make sense if
transferred to another hardware or software environment:  for this
reason, their use is only recommended in situations like this.</p><p>Useful though the entity reference mechanism is for dealing with
occasional departures from the expected character set, no one would
consider using it to encode extended passages, such as quotations in
Greek or Russian in an English text.  In such situations, different
mechanisms are appropriate.  These are discussed elsewhere in these
Guidelines (see chapter <xref target="CH"/>).
 <!-- expand on following to show how ST works in simple terms --></p><p>A special form of entities, <term>parameter entities</term>, may be
used within SGML markup declarations; these differ from the entities
discussed above (which technically are known as
<term>general entities</term>) in two ways:
 
<list type="bullets"><item>Parameter entities are used <emph>only</emph> within SGML markup
declarations; with some special exceptions which will not be
discussed here, they will normally not be found within the document
itself.</item><item>Parameter entities are delimited by percent sign and semicolon,
rather than by ampersand and semicolon.</item></list>
 
Declarations for parameter entities take the same form as those for
general entities, but insert a percent sign between the keyword <code tei="yes" type="kw">ENTITY</code> and the name of the entity itself.  White space
(blanks, tabs, or line breaks) must occur on both sides of the percent
sign.  An internal parameter entity named <ident tei="yes" type="pe">TEI.prose</ident>, with an expansion of <code tei="yes" type="frag">INCLUDE</code>,
and an external parameter entity named <ident tei="yes" type="pe">TEI.extensions.dtd</ident>, which refers to the system file
<ident tei="yes" type="file">mystuff.dtd</ident>, could be declared thus:<note source="auth" place="display" anchored="Y">Such
entity declarations might be used in extending the TEI base tag set for
prose using the declarations found in <ident tei="yes" type="file">mystuff.dtd</ident>.</note>
 
<eg><![CDATA[ <!ENTITY % TEI.prose 'INCLUDE'>
 <!ENTITY % TEI.extensions.dtd SYSTEM 'mystuff.dtd'>]]></eg></p><p>The TEI document type definition makes extensive use of parameter
entities to control the selection of different tag sets and to make it
easier to modify the TEI DTD.  Numerous examples of their use may
thus be found in chapter <xref target="ST"/>.</p></div2><div2 id="SG17BIS" name="bar" ref="Y"><head>Marked Sections</head><p>It is occasionally convenient to mark some portion of a text for
special treatment by the SGML parser.  Certain portions of legal
boilerplate, for example, might need to be included or omitted
systematically, depending on the state or country in which the document
was intended to be valid.  (Thus the statement <q>Liability is limited
to $50,000.</q> might need to be included in Delaware, but excluded in
Maryland.)  Technical manuals for related products might share a great
deal of information but differ in some details; it might be convenient
to maintain all the information for the entire set of related products
in a single document, selecting at display or print time only those
portions relevant to one specific product.  (Thus, a discussion of how
to change the oil in a car might use the same text for most steps, but
offer different advice on removing the carburetor, depending on the
specific engine model in question.)</p><p>SGML provides the <term>marked section</term> construct to handle
such practical requirements of document production.  In general, as the
examples above are intended to suggest, it is more obviously useful in
the production of new texts than in the encoding of pre-existing texts.
Most users of the TEI encoding scheme will never need to use marked
sections, and may wish to skip the remainder of this discussion.
The TEI
DTD makes extensive use of marked sections, however, and this section
should be read and understood carefully by anyone wishing to follow in
detail the discussions in chapter <xref target="ST"/>.</p><p>The <soCalled>special processing</soCalled> offered for marked
sections in SGML can be of several types, each associated with one of
the following keywords:
 
<list type="gloss"><label>INCLUDE</label><item>The marked section should be included in the
document and processed normally.</item><label>IGNORE</label><item>The marked section should be ignored entirely; if
the SGML application program produces output from the document, the
marked section will be excluded from the document.</item><label>CDATA</label><item>The marked section may contain strings of
characters which look like SGML tags or entity references, but which
should not be recognized as such by the SGML parser.  (These Guidelines
use such CDATA marked sections to enclose the examples of SGML tagging.)</item><label>RCDATA</label><item>The marked section may contain strings of characters
which look like SGML tags, but which should not be recognized as such by
the SGML parser; entity references, on the other hand, may be present
and should be recognized and expanded as normal.</item><label>TEMP</label><item>The passage included in the marked section is a
temporary part of the document; the marked section is used primarily to
indicate its location, so that it can be removed or revised conveniently
later.</item></list></p><p>When a marked section occurs in the text, it is preceded by a
<term>marked-section start</term> string, which contains one or more
keywords from the list above; its end is marked by a
<term>marked-section close</term> string.  The second and
last lines of the following example are the start and close of a
marked section to be ignored:
 
<eg> In such cases, the bank will reimburse the customer for all losses.
 &lt;![ IGNORE [
 Liability is limited to $50,000.
 ]]&gt;</eg>
 
Of the marked section keywords, the most important for understanding the
TEI DTD are <code tei="yes" type="kw">INCLUDE</code> and <code tei="yes" type="kw">IGNORE</code>; these can be used to include and exclude portions
of a document --- or a DTD --- selectively, so as to adjust it to
relevant circumstances (e.g. to allow a user to select portions of the
DTD relevant to the document in question).</p><p>The literal keywords <code tei="yes" type="kw">INCLUDE</code> and <code tei="yes" type="kw">IGNORE</code>, however, are not much use in adjusting a DTD or a
document to a user's requirements.  (To change the text above
to include the excluded sentence, for example, a user would have to edit
the text manually and change <code tei="yes" type="kw">IGNORE</code> to <code tei="yes" type="kw">INCLUDE</code>.  It might be thought just as easy to add and
delete the sentence manually.)  But the keywords need not be given as
literal values; they can be represented by a parameter entity reference.
In a document with many sentences which should be included only in
Maryland, for example, each such sentence can be included in a marked
section whose keyword is represented by a reference to a parameter
entity named <ident tei="yes" type="pe">Maryland</ident>.  The earlier example would
then be:
 
 
<eg> In such cases, the bank will reimburse the customer for all losses.
 &lt;![ %Maryland; [
 Liability is limited to $50,000.
 ]]&gt;</eg>
 
When the entity <ident tei="yes" type="pe">Maryland</ident> is defined as <code tei="yes" type="fragment">IGNORE</code>, the marked sections so marked will all be
excluded.  If the definition is changed to the following, the marked
sections will be included in the document:
 
<eg><![CDATA[ <!ENTITY % Maryland 'INCLUDE'>]]></eg>
 
When parameter entities are used in this way to control marked sections
in a DTD, the external DTD file normally contains a default declaration.
If the user wishes to override the default (as by including the Maryland
sections), adding an appropriate declaration to the DTD subset suffices
to override the default.<note source="auth" place="display" anchored="Y">This is so because the declarations in the
DTD subset are read before those in the external DTD file, and the first
declaration of a given entity is the one which counts.  This was
described briefly in section <xref target="SG17"/>.</note></p><p>The examples of parameter entity declarations at the end of the
preceding section can now be better understood.  The declarations
 
<eg><![CDATA[ <!ENTITY % TEI.prose 'INCLUDE'>
 <!ENTITY % TEI.extensions.dtd SYSTEM 'mystuff.dtd'>]]></eg>
 
have the effect of <emph>including</emph> in the DTD all the sections
marked as relevant to prose, since in the external DTD files such
sections are all included in marked sections controlled by the parameter
entity <ident tei="yes" type="pe">TEI.prose</ident>.  They also override the default
declaration of <ident tei="yes" type="pe">TEI.extensions.dtd</ident> (which declares
this entity as an empty string), so as to include the file <ident tei="yes" type="file">mystuff.dtd</ident> in the DTD.</p></div2><div2 id="SG18" name="bar" ref="Y"><head>Putting It All Together</head><p>An SGML conformant document has a number of parts, not all of which
have been discussed in this chapter, and many of which the user of these
Guidelines may safely ignore.  For completeness, the following summary
of how the parts are inter-related may however be found useful.</p><p>An SGML document consists of an SGML <term>prolog</term> and a
<term>document instance</term>.  The prolog contains an <term>SGML
declaration</term> (described below)
and a <term>document type definition</term>, which
contains element and entity declarations such as those described above.
Different software systems may provide different ways of associating the
document instance with the prolog; in some cases, for example, the
prolog may be <soCalled>hard-wired</soCalled> into the software used, so that it is
completely invisible to the user.</p><div3 id="SG181" name="burp" ref="Y"><head>The SGML Declaration</head><p>The SGML declaration specifies basic facts about the dialect of SGML
being used such as the character set, the codes used for SGML
delimiters, the length of identifiers, etc.  Its content for
TEI-conformant document types is discussed further in chapters <xref target="GR"/> and <xref target="CF"/>. Normally the SGML declaration will be
held in the form of compiled tables by the SGML processor and will thus
be invisible to the user.</p></div3><div3 id="SG182" name="burp" ref="Y"><head>The DTD</head><p>The document type definition specifies the document type
definition against which the document instance is to be validated.
Like the SGML declaration it may be held in the form of compiled
tables within the SGML processor, or associated with it in some
way which is invisible to the user, or requires only that the name
of the document type be specified before the document is validated.</p><p>At its simplest the document type definition consists simply of
a base document type definition (possibly also one or
more concurrent document type definitions) which is prefixed to the
document instance.  For example:
 
<eg><![CDATA[<!DOCTYPE my.dtd [
    <!-- all declarations for MY.DTD go here -->
    ...
]>
<my.dtd>
    This is an instance of a MY.DTD type document
</my.dtd>]]></eg></p><p>More usually, the document type definition will be held in a
separate file and invoked by reference, as follows:
 
<eg><![CDATA[    <!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN">
    <tei.2>
         This is an instance of an unmodified TEI type document
    </tei.2>]]></eg>
 
Here, the text of the TEI.2 document type definition is not given
explicitly, but the SGML processor is told that it may be read from the
file with the system identifier given in quotation marks.  The square
brackets may still be supplied, as in this example, even though they
enclose nothing.</p><p>The part enclosed by square brackets is known as the <term>document
type declaration subset</term> or <soCalled>DTD subset</soCalled>.  Its
purpose is to specify any modification to be made to the DTD being
invoked, thus:
 
<eg><![CDATA[    <!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN" [
         <!ENTITY tla "Three Letter Acronym">
         <!ELEMENT my.tag - - (#PCDATA)>
         <!-- any other special-purpose declarations or
              re-definitions go in here -->
    ]>
    <tei.2>
         This is an instance of a modified TEI.2 type document,
         which may contain <my.tag>my special tags</my.tag> and
         references to my usual entities such as &tla;.
    </tei.2>]]></eg><!-- this whole chunk needs rewriting: it sucks -->
 
In this case, the document type definition in force includes first the
contents of the DTD subset, and then the contents of the file specified
after the keyword <code tei="yes" type="kw">SYSTEM</code>.  The order is important,
because in SGML only the first declaration of an entity counts.  In the
above example, therefore, the declaration of the entity <ident tei="yes" type="ent">tla</ident> in the DTD subset would take precedence over any
declaration of the same entity in the file
<ident tei="yes" type="file">tei2.dtd</ident>.  It is perfectly legal SGML for
entities to be declared twice; this is the usual method for allowing
user modification of SGML DTDs.  (Elements, by contrast, may not be
declared more than once; if a declaration for <gi tei="no">my.tag</gi>
were contained in file <ident tei="yes" type="file">tei.dtd</ident>, the SGML parser
would signal an error.)  Combining and extending the TEI document type
definitions is discussed further in chapter <xref target="ST"/>.</p></div3><div3 id="SG183" name="burp" ref="Y"><head>The Document Instance</head><p>The document instance is the content of the document itself.  It
contains only text, markup and general entity references, and thus may
not contain any new declarations.<!--  < note >                                                --><!-- Except for SUBDOC entities; see example in  < xref       --><!-- target=Z69 > .                                           --><!--  < /note >                                               -->
 
A convenient way of building up large documents in a modular fashion
might be to use the DTD subset to declare entities for the individual
pieces or modules, thus:
 
<eg><![CDATA[    <!DOCTYPE tei.2 [
         <!ENTITY chap1 system "chap1.txt">
         <!ENTITY chap2 system "chap2.txt">
         <!ENTITY chap3 "-- not yet written --">
    ]>
    <tei.2>
    <teiHeader> ... </teiHeader>
    <text>
        <front> ... </front>
        <body>
         &chap1;
         &chap2;
         &chap3;
         ...
    </body>
    </text>
    </tei.2>
 ]]></eg></p><p>In this example, the DTD contained in file <ident tei="yes" type="file">tei2.dtd</ident> has been extended by entity declarations for
each chapter of the work.  The first two are external entities referring
to the file in which the text of particular chapters is to be found; the
third a dummy, indicating that the text does not yet exist
(alternatively, an entity with a null value could be used).  In the
document instance, the entity references &amp;amp;chap1; etc. will be
resolved by the parser to give the required contents.  The chapter files
themselves will not, of course, contain any element, attribute list, or
entity declarations---just tagged text.</p></div3><div3 id="SGPATANC" name="burp" ref="Y"><head>Ancillary Files</head><p>In practice, working SGML systems use a number of ancillary files
to hold configuration information.  Style sheets (now still commonly
using software-specific formats, though standard formats should become
more widespread with time), files with specialized processing
instructions, files with setup information for specific programs, will
all be needed in practical use of SGML.  Many programs also use
environment variables for some parts of their setup (e.g. to tell the
program where to find its configuration files). The details of the
files needed, and how they affect the actions of an SGML system, vary
with the system and cannot be described here.</p><p>Most recent SGML software does use a standard format called the
<term>SGML Open Catalog</term> format<note source="auth" place="display" anchored="Y">The SGML Open catalog
format described here  is documented in <citation>SGML Open Technical
Resolution 9401:1997, <title>Entity Management</title>, which is
available from the SGML Open Web site at
<code tei="yes" type="frag">http://www.sgmlopen.org</code>.</citation> </note> for the
<term>catalog files</term> they use to help the SGML parser locate the
files (or network resources) corresponding to public and system
identifiers used in declarations of entities (and of other
SGML constructs).  A catalog file using that format
may contain entries for each public identifier in a DTD in a form
like the following:
<eg><![CDATA[PUBLIC "-//TEI P3//DTD Main Document Type//EN"
       "teifpi2.dtd"]]></eg>
Each entry has three parts: the keyword <code tei="yes" type="kw">PUBLIC</code>,
the public identifier, and the system identifier under which 
SGML parsers can find the entity named by the public identifier.</p><p>An SGML Open Catalog file with entries for each part of the
TEI DTD is available from the TEI.  See chapter<xref target="DT"/>
 for more information.</p></div3></div2><div2 id="SG19" name="bar" ref="Y"><head>Using SGML</head><p>A variety of software is available to assist in the tasks of
creating, validating and processing SGML documents.  Only a few basic
types can be described here. At the heart of most such software is an
SGML <term>parser</term>:  that is, a piece of software which can take
a document type definition and generate from it a software system
capable of validating any document invoking that DTD.  Output from a
parser, at its simplest, is just <q>yes</q> (the document instance is
valid) or <q>no</q> (it is not).  Most parsers will however also
produce a new version of the document instance in <term>canonical
form</term> (typically with all end-tags supplied and entity references
resolved) or formatted according to user specifications.  This
form can then be used by other pieces of software (loosely or tightly
coupled with the parser) to provide additional functions, such as
structured editing, formatting and database management.</p><p>A <term>structured editor</term> is a kind of intelligent
word-processor.  It can use information extracted from a processed DTD
to prompt the user with information about which elements are required
at different points in a document as the document is being created.  It
can also greatly simplify the task of preparing a document, for example
by inserting tags automatically.</p><p>A <term>formatter</term> operates on a tagged document instance to
produce a printed form of it.  Many typographic distinctions, such as
the use of particular typefaces or sizes, are intimately related to
structural distinctions, and formatters can thus usefully take
advantage of descriptive markup.  It is also possible to define the
tagging structure expected by a formatting program in SGML terms, as a
concurrent document structure.</p><p>Text-oriented database management systems typically use inverted
file indexes to point into documents, or subdivisions of them.  A
search can be made for an occurrence of some word or word pattern
within a document or within a subdivision of one.  Meaningful
subdivisions of input documents will of course be closely related to
the subdivisions specified using descriptive markup.  It is thus simple
for textual database systems to take advantage of SGML-tagged
documents.  Much research work is also currently going into ways of
extending the capabilities of existing (non-text) database systems to
take advantage of the structuring information made explicit by SGML
markup.</p><p><term>Hypertext</term> systems improve on other methods of handling
text by supporting associative links within and across documents.
Again, the basic building block needed for such systems is also a
basic building block of SGML markup:  the ability to identify and
to link together individual document elements comes free as a part
of the SGML way of doing things.  By tagging links explicitly,
rather than using proprietary software, developers of hypertexts
can be sure that the resources they create will continue to be
useful.  To load an SGML document into a hypertext system requires
only a processor which can correctly interpret SGML tags such as
those discussed in chapter <xref target="SA"/>.</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2sg.odd ??><!-- 2 Concise Summary of SGML --><?tei:SOF p2st.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2st.odd,v $
    * Revision 1.4  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.3  94/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
    * --><!-- P2.213 : Structure of TEI DTDs                           --><!-- Revisions:                                               --><!-- 94-03-21f : MSM : typos and stylistic improvements       --><!--                   from DB, the WWP team, JLav, EBr       --><!-- 93-04-06 : MSM : cosmetic changes                        --><!-- 3 apr 93 : LB : revise for publication                   --><!--       stylistic changes consequent on singularization    --><!--       moved govt health warning about techno-detail here --><!-- 1993-03-16 : CMSMcQ : reorder sections to segregate      --><!--                       techno-detail at end of chapter    --><!--                       only.  Revise overview to match.   --><!-- 25 Jan 93 : CMSMcQ : revise lightly for publication      --><!-- 26 May 92 : CMSMcQ : draft intro paragraph               --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><div1 id="ST" n="3" name="Chapter" ref="Y"><head>Structure of the TEI Document Type Definition</head><!-- goal of this chapter:  make it possible to understand    --><!-- how all this fits together.  Some conceptual and         --><!-- some technical details need covering, mostly:            --><!-- what we are trying to do, and then how we are doing      --><!-- it in SGML.                                              --><p>This chapter describes the overall structure of the encoding scheme
defined by these Guidelines.  It introduces the conceptual framework
within which the following chapters are to be understood, and describes
the technical means by which that conceptual framework is implemented in
SGML.  It assumes some familiarity with SGML; see chapter <xref target="SG"/>.
 <!--  < p > The TEI encoding scheme provides a number of      --><!-- modules, which function either as complete independent   --><!-- < term > document type declarations < /term > ( < term   --><!-- > DTDs < /term > ), or as  < term > DTD fragments <      --><!-- /term > ; both full and fragmentary DTDs we call         --><!-- indifferently  < term > tag sets < /term > .  We         --><!-- distinguish:                                             --></p><p>The TEI encoding scheme consists of number of modules or <term>DTD
fragments</term> which we refer to below as <term>tag sets</term>.
Selected tag sets may be combined in many different ways, according to
principles described in this chapter, within the framework of the TEI
<term>main DTD</term>.  Auxiliary tag sets are also defined for specific
purposes independent of the TEI main DTD.
 <!--  < list type=bullets >                                   --><!--  < item > main DTDs                                      --><!--  < item > auxiliary DTDs                                 --><!--  < /list >                                               --><!--                                                          --><!-- Main DTDs in turn are made up of:                        --></p><p>The DTD fragments from which the main TEI DTD is constructed may be
classified as follows:
 
<list type="bullets"><item>core DTD fragments</item><item>base DTD fragments</item><item>additional DTD fragments</item></list></p><p>The first two sections of this chapter discuss these distinctions and
list the specific tag sets included in each category.  Section <xref target="STIN" type="div2"/> describes how to invoke the TEI document type
declaration, and how to specify which of the various base tag sets and
optional additional tag sets are used in a document.</p><p>The <term>global attributes</term>, characteristics postulated of
every element or tag in the encoding scheme, are defined in section<xref target="STGA" type="div2"/>
.</p><p>The remainder of the chapter contains a more technical description of
the SGML mechanisms used to implement the encoding scheme.  It may be
skipped at a first reading, but a proper understanding of the topics
addressed here is essential for anyone planning to modify or extend the
TEI encoding scheme in any way (see also chapter <xref target="MD"/>), and
also highly desirable for those wishing to take full advantage of its
modular nature.  The structure of the main TEI DTD file itself is
outlined in section <xref target="STOV"/>.  The <term>element
classes</term> used to define smaller groups of elements and their
characteristics are described in section <xref target="STEC" type="div2"/>.
Both global attributes and element classes are implemented using SGML
<term>parameter entities</term>; various other uses of parameter
entities in the TEI DTDs are discussed in section <xref target="STPE"/>.</p><?tei:SOF p2stma.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2stma.odd,v $
# 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
# --><!-- P2.131 : Main and Auxiliary DTDs                         --><!-- Revisions:                                               --><!-- 1994-03-22 : MSM : typos, corrections, improvements from --><!--                    DB, EBr, JLav                         --><!-- 1994-03-22 : MSM : retag filenames from TERM to IDENT    --><!-- 3 apr 93 : LB revise for publication                     --><!--   expand discussion of auxiliaries a bit                 --><!-- 1993-03162 : MSM : stylistic, suppress xref to IN        --><!-- 1993-02-02 : MSM : stylistic revisions                   --><!-- 1993-01-27 : MSM : correct SGML typo                     --><!-- 25 Jan 93 : CMSMcQ : reverse labels and items in gl      --><!-- 12 Jan 93 : CMSMcQ : revise for clarity                  --><!-- 21 Oct 92 : CMSMcQ : new name new id                     --><!-- 26 May 92 : CMSMcQ : drafted prose                       --><!-- 17 May 92 : CMSMcQ : began draft (outline)               --><div2 id="STMA" name="bar" ref="Y"><head>Main and Auxiliary DTDs</head><!-- document itself in a main DTD, of which TEI has          --><!--         several flavors                                  --><!-- other information in auxiliary documents                 --><!-- list of auxiliary dtds                                   --><!-- tei interchange basically the main doc, plus any         --><!--         relevant additional things.                      --><p>These Guidelines define a large number of SGML tags for marking up
documents, all of which are formally defined within the <term>document
type declaration</term> (<term>DTD</term>) files provided by the TEI
and documented in the remainder of the present document.   The tags are
grouped into <term>tag sets</term> or <term>DTD fragments</term>, each
comprising a set of declarations for tags which belong together in some
respect, typically related to their intended application area.
 </p><p>All tags used to transcribe documents are available for use within
the <term>main DTD</term> of the TEI and are  defined in Parts III and
IV of these Guidelines.  There are DTD fragments for prose and mixed
matter, verse and verse collections, drama, dictionaries, analysis and
interpretation of text, text criticism, etc. A full list, including the
files in which they are defined, and the rules determining their
selection and combination, is given in section <xref target="STBA"/>.
 </p><p>A number of <term>auxiliary DTDs</term> are also defined in these
Guidelines. These are used for  the encoding of ancillary descriptive
information useful when processing electronic documents.  Part V of
these Guidelines describes several such auxiliary document types,
specifically:
 
<list type="gloss"><label>independent header</label><item>for use with sets of TEI headers regarded
as documents in their own right, for example by libraries or archives
exchanging details of their holdings (see chapters <xref target="HD"/> and<xref target="SH"/>
).
 </item><label>writing system declaration</label><item>used to define and document
character sets or transliteration schemes (see chapters <xref target="CH"/>
and <xref target="WD"/>).
 </item><label>feature system declaration</label><item>used to define and document sets
of analytic features (see chapters <xref target="FS"/> and <xref target="FD"/>).
 </item><label>tag set declaration</label><item>used to define and document descriptive
documentation for TEI-conformant tag sets (see chapter <xref target="TD"/>).
 <!-- shd also cross ref CF? --></item></list>
 
 </p><p>An independent header typically describes the encoding of a
specific document, but in the case of a planned corpus or collection, it
may define a set of encoding practices common to all texts in the
collection.  The other auxiliary document types provide information
likely to be relevant to many documents, rather than to individual
documents.
 </p><p>When individual TEI documents are exchanged between sites, they
should be accompanied by whatever auxiliary documents apply to them.
When larger groups of documents are exchanged, the relevant auxiliary
documents need be exchanged only once. For further information see
chapter <xref target="IN"/>.
 </p><p>The DTD files containing these auxiliary DTDs are:
<list type="gloss"><label><ident tei="yes" type="file">teishd2.dtd</ident></label><item>independent header</item><label><ident tei="yes" type="file">teiwsd2.dtd</ident></label><item>writing system declaration</item><label><ident tei="yes" type="file">teifsd2.dtd</ident></label><item>feature system declaration</item><label><ident tei="yes" type="file">teitsd2.dtd</ident></label><item>tag set declaration</item></list>
 </p><p>Some of these auxiliary DTDs also make use of the core tag set
defined as part of the main TEI DTD; this is described in the relevant
chapters of part V.<?tei:EOF p2stma.odd ??><!-- 1 Main and Aux DTDs      --><?tei:SOF p2stba.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $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)               -->
 </p></div2><div2 id="STBA" name="bar" ref="Y"><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> </label><item>standard components of the TEI
main DTD in all its forms; these are always included without any special
action by the encoder;
 </item><label><term>base tag sets</term> </label><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);
 </item><label><term>additional tag sets</term> </label><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.
 </item></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 source="auth" place="display" anchored="Y">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 tei="yes" type="pe">TEI.core.ent</ident>, for example, would be referred to using
the string <code tei="yes" type="frag">%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 rend="noindex" tei="yes" type="class">xxx</ident>, the following parameter entities may be
encountered:
 
<list type="gloss"><label>TEI.xxx </label><item>used to enable or disable tag set <ident rend="noindex" tei="yes" type="class">xxx</ident>; must have the value <code tei="yes" type="kw">INCLUDE</code> (tag set is enabled) or, by default, <code tei="yes" type="kw">IGNORE</code> (tag set not enabled).
 </item><label>TEI.xxx.ent </label><item>refers to a system file containing any
parameter entity declarations unique to tag set <ident rend="noindex" tei="yes" type="class">xxx</ident>.
 </item><label>TEI.xxx.dtd </label><item>refers to a system file containing the element
and attribute list declarations for tag set <ident rend="noindex" tei="yes" type="class">xxx</ident>.
 </item><label>a.xxx </label><item>contains definitions of attributes which are to be
added to the set of global attributes when tag set <ident rend="noindex" tei="yes" type="class">xxx</ident> is enabled.
 </item><label>m.comp.xxx </label><item>if <ident rend="noindex" tei="yes" type="class">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"/>
).
 </item><label>mix.xxx </label><item>a special entity for use in defining the set of
component-level elements when the mixed base tag set is in use.
 </item><label>gen.xxx </label><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)                                                    -->
 </item></list>
 
Few tag sets declare all of these entities; only those actually used are
declared.
 </p><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 tei="yes" 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.
 </p><div3 id="STBACO" name="burp" ref="Y"><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 tei="yes" type="pe">TEI.core.dtd</ident> </label><item>refers to the file
<ident tei="yes" type="file">teicore2.dtd</ident>, which declares the core tags
defined in chapter <xref target="CO"/>
 </item><label><ident tei="yes" type="pe">TEI.header.dtd</ident> </label><item>refers to the file
<ident tei="yes" type="file">teihdr2.dtd</ident>, which declares the tags of the TEI
header defined in chapter <xref target="HD"/>
 </item></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.
 </p></div3><div3 id="STBABA" name="burp" ref="Y"><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><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><p>The encoder selects a base tag set by declaring the appropriate SGML
parameter entity with the replacement text <code tei="yes" 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><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 tei="yes" type="pe">TEI.prose</ident> </label><item>selects the base tag set
for prose, contained in <ident tei="yes" type="file">teipros2.dtd</ident>.
 <!-- and < term >teipros2.ent< /term >                        -->
 </item><label><ident tei="yes" type="pe">TEI.verse</ident> </label><item>selects the base tag set
for verse, contained in <ident tei="yes" type="file">teivers2.dtd</ident> and
<ident tei="yes" type="file">teivers2.ent</ident>.
 </item><label><ident tei="yes" type="pe">TEI.drama</ident> </label><item>selects the base tag set
for drama, contained in <ident tei="yes" type="file">teidram2.dtd</ident> and <ident tei="yes" type="file">teidram2.ent</ident>.
 </item><label><ident tei="yes" type="pe">TEI.spoken</ident> </label><item>selects the base tag set
for transcriptions of spoken texts, contained in
<ident tei="yes" type="file">teispok2.dtd</ident> and
<ident tei="yes" 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>                           -->
 </item><label><ident tei="yes" type="pe">TEI.dictionaries</ident> </label><item>selects the base
tag set for print dictionaries, contained in
<ident tei="yes" type="file">teidict2.dtd</ident> and
<ident tei="yes" type="file">teidict2.ent</ident>.
 </item><label><ident tei="yes" type="pe">TEI.terminology</ident> </label><item>selects the base tag
set for terminological data files, contained in
<ident tei="yes" type="file">teiterm2.dtd</ident>,
<ident tei="yes" type="file">teiterm2.ent</ident>,
<ident tei="yes" type="file">teite2n.dtd</ident>, and
<ident tei="yes" type="file">teite2f.ent</ident>.
 </item><label><ident tei="yes" type="pe">TEI.general</ident> </label><item>selects the generic
mixed-mode base base tag set, contained in
<ident tei="yes" type="file">teigen2.dtd</ident>.
 <!-- and < term >teigen2.ent< /term >                         -->
 </item><label><ident tei="yes" type="pe">TEI.mixed</ident> </label><item>selects the base tag set
for free mixed-mode texts, contained in
<ident tei="yes" type="file">teimix2.dtd</ident>.
 <!-- and < term >teimix2.ent< /term >                         -->
 </item></list>
 </p><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 tei="yes" type="pe">TEI.prose</ident> as <code tei="yes" type="kw">INCLUDE</code>; this in turn enables declarations of <ident tei="yes" type="pe">TEI.prose.ent</ident> and <ident tei="yes" type="pe">TEI.prose.dtd</ident>
as the system files <ident tei="yes" type="file">teipros2.ent</ident> and
<ident tei="yes" 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><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 tei="yes" type="pe">TEI.structure.dtd</ident> </label><item>refers to the file
<ident tei="yes" type="file">teistr2.dtd</ident>, with default definitions for
<gi tei="yes">text</gi>, <gi tei="yes">div</gi>, etc.
 </item><label><ident tei="yes" type="pe">TEI.front.dtd</ident> </label><item>refers to the file
<ident tei="yes" type="file">teifron2.dtd</ident>, with tags for front matter
 </item><label><ident tei="yes" type="pe">TEI.back.dtd</ident> </label><item>refers to the file
<ident tei="yes" type="file">teiback2.dtd</ident>, with tags for back matter
 </item></list>
 
These default-structure tags are documented in chapter <xref target="DS"/>.
 </p></div3><div3 id="STBAAD" name="burp" ref="Y"><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 tei="yes" type="kw">INCLUDE</code>; the
relevant parameter entities, and the files containing the additional tag
sets, are these:
 
<list type="gloss"><label><ident tei="yes" type="pe">TEI.linking</ident> </label><item>embeds the files
<ident tei="yes" type="file">teilink2.dtd</ident> and
<ident tei="yes" type="file">teilink2.ent</ident>, with tags for linking,
segmentation, and alignment (chapter <xref target="SA"/>)
 </item><label><ident tei="yes" type="pe">TEI.analysis</ident> </label><item>embeds the files
<ident tei="yes" type="file">teiana2.dtd</ident> and
<ident tei="yes" type="file">teiana2.ent</ident>,
with tags for simple analytic mechanisms (chapter <xref target="AI"/>)
 </item><label><ident tei="yes" type="pe">TEI.fs</ident> </label><item>embeds the file
<ident tei="yes" type="file">teifs2.dtd</ident>,
with tags for feature structure analysis (chapter <xref target="FS"/>)
 </item><label><ident tei="yes" type="pe">TEI.certainty</ident> </label><item>embeds the file
<ident tei="yes" type="file">teicert2.dtd</ident>,
with tags for indicating uncertainty and
probability in the markup (chapter <xref target="CE"/>)
 </item><label><ident tei="yes" type="pe">TEI.transcr</ident> </label><item>embeds the files
<ident tei="yes" type="file">teitran2.dtd</ident> and
<ident tei="yes" type="file">teitran2.ent</ident>,
with tags for manuscripts, analytic bibliography, and transcription of
primary sources (chapter <xref target="PH"/>)
 </item><label><ident tei="yes" type="pe">TEI.textcrit</ident> </label><item>embeds the files
<ident tei="yes" type="file">teitc2.dtd</ident> and
<ident tei="yes" type="file">teitc2.ent</ident>,
with tags for critical editions (chapter <xref target="TC"/>)
 </item><label><ident tei="yes" type="pe">TEI.names.dates</ident> </label><item>embeds the files
<ident tei="yes" type="file">teind2.dtd</ident> and
<ident tei="yes" type="file">teind2.ent</ident>,
with specialized tags for names and dates (chapter <xref target="ND"/>)
 </item><label><ident tei="yes" type="pe">TEI.nets</ident> </label><item>embeds the file <ident tei="yes" 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 tei="yes" type="pe">TEI.figures</ident>
 </item><label><ident tei="yes" type="pe">TEI.figures</ident> </label><item>embeds the files
<ident tei="yes" type="file">teifig2.dtd</ident> and
<ident tei="yes" 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 tei="yes" 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>)                                              -->
 </item><label><ident tei="yes" type="pe">TEI.corpus</ident> </label><item>embeds the file <ident tei="yes" type="file">teicorp2.dtd</ident>, with tags for additional tags for
language corpora (chapter <xref target="CC"/>)
 </item></list>
 </p><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 tei="yes" type="pe">TEI.linking</ident> as <code tei="yes" type="kw">INCLUDE</code>;
this in turn
enables declarations of <ident tei="yes" type="pe">TEI.linking.ent</ident> and
<ident tei="yes" type="pe">TEI.linking.dtd</ident> as the system files
<ident tei="yes" type="file">teilink2.ent</ident> and
<ident tei="yes" type="file">teilink2.dtd</ident>.
 </p></div3><div3 id="STBAUS" name="burp" ref="Y"><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 tei="yes" type="pe">TEI.extensions.ent</ident></label><item>local modifications to parameter entities</item><label><ident tei="yes" type="pe">TEI.extensions.dtd</ident></label><item>declarations of new elements and modified
declarations for existing elements</item></list>
 </p><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><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 ??><!-- 2 Base Sets and Addtnls  --><?tei:SOF p2stin.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2stin.odd,v $
    * Revision 1.4  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.3  94/04/08  01:36:34  msmcq
    * Last-round changes before publication of P3
    *  --><!-- P2.STin:  Invocation of the TEI DTD                      --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : typo / wording changes from MSM         --><!-- 94-03-22 : MSM : typo / wording changes from JLav        --><!-- 94-03-22 : MSM : retag some TERMs, Qs, as CODE, IDENT    --><!-- 3 apr 93 : LB revise for publication                     --><!--       stylistic changes consequent on singularization    --><!-- 93-03-30 : MSM : cosmetic change only                    --><!-- 93-03-16 : MSM : move mixed bases to STco, add drama ex  --><!-- 93-03-06 : MSM : revise selection of mixed bases         --><!-- 17 May 92 : CMSMcQ : began draft                         -->
 </p></div3></div2><div2 id="STIN" name="bar" ref="Y"><head>Invocation of the TEI DTD</head><p>Like any other SGML document, a TEI document must begin with a
document type definition (DTD).  Local systems may allow the DTD to be
implicit, but for interchange purposes it <emph>must</emph> be
explicit. Because of its highly modular nature, it may in any case be
desirable for the component parts of the TEI DTD to be made  explicit
even for local processing.</p><p>The simplest version of the TEI DTD names the main TEI DTD file as
an external file, and specifies a single base tag set for use in the document,
using the parameter entity names specified in section <xref target="STBA"/>.  For example, a document using the base tag set for prose
will begin with a document type declaration something like this:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.prose 'INCLUDE' >
 ]>]]></eg>
 
A document using the base tag set for drama will define a different
parameter entity:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.drama 'INCLUDE' >
 ]>]]></eg></p><p>If one or more of the <term>additional tag sets</term> described in
Part IV are to be used, they are invoked in the same way as the base tag
set.  A document using the base tag set for prose, with the additional
tag sets for text criticism and for linking, segmentation, and
alignment, for example, will begin with a document type declaration
something like this:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
 <!-- TEI base tag set specified here: ... -->
      <!ENTITY % TEI.prose 'INCLUDE' >
 
 <!-- TEI additional tag sets optionally specified here: ... -->
      <!ENTITY % TEI.textcrit 'INCLUDE' >
      <!ENTITY % TEI.linking 'INCLUDE' >
 ]>]]></eg></p><p>If local modifications are used, they may be stored in separate
files and pointed to using the parameter entities <ident tei="yes" type="pe">TEI.extensions.ent</ident> and <ident tei="yes" type="pe">TEI.extensions.dtd</ident>.  If such local modifications are
added to the example just given, this is the result:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
 <!-- Local modifications to the TEI DTD declared here.  They
      will be embedded at an appropriate point in the main
      DTD. ... -->
      <!ENTITY % TEI.extensions.ent system 'project.ent' >
      <!ENTITY % TEI.extensions.dtd system 'project.dtd' >
 
 <!-- TEI base tag set specified here: ... -->
      <!ENTITY % TEI.prose 'INCLUDE' >
 
 <!-- TEI additional tag sets specified here: ... -->
      <!ENTITY % TEI.textcrit 'INCLUDE' >
      <!ENTITY % TEI.linking 'INCLUDE' >
 ]>]]></eg>
 <!-- changed following para to reflect fact that mixed base needed when --><!-- different bases are mixed, not just when prose and verse are needed -->
 <!-- <p>If the document has a mixture of different text types (e.g. prose and --><!-- verse) or embeds smaller texts of different text types, one of the --><!-- mixed-type bases must be used.  Their proper invocation is described --><!-- below in section <xref target=STCO>. --></p><p>If the document requires tags which are defined in different base
tag sets (e.g. prose and drama) or embeds smaller texts which use
different base tag sets, then one of the mixed-type bases must be used.
Their proper invocation is described below in section <xref target="STCO"/>.</p></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2stin.odd ??><!-- 3 Invocation of TEI DTDs --><?tei:SOF p2stco.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2stco.odd,v $
    * Revision 1.6  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.5  94/04/08  01:36:34  msmcq
    * Last-round changes before publication of P3
    * 
    * Revision 1.4  1994/04/01  16:36:47  msmcq
    * changes / fixes during validation of DTD
    * 
    * Revision 1.3  1994/03/24  22:20:40  msmcq
    * typos found by David Barnard et al. corrected
    * --><!-- P2.136 :  Combining TEI DTD fragments                    --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : minor changes                           --><!-- 94-03-31 : MSM : define files teimix2, teigen2           --><!-- 94-03-22 : MSM : typos and wording changes from JLav     --><!-- 94-03-22 : MSM : retag some TERMs, Qs, as CODE, IDENT    --><!-- 94-03-21 : MSM : typos, suppress xref to CB              --><!-- 93-09-14 : MSM : dictionar-ies not dictionar-y           --><!-- 93-04-06 : MSM : one minor fix for clarity               --><!-- 3 apr 93 : LB revise for publication                     --><!--       changed title                                     --><!--      stylistic changes consequent on singularization    --><!--      simplified discussion/examples at end               --><!-- 93-03-30 : MSM : minor cosmetic changes for LB           --><!-- 93-03-06 : MSM : light revision, notes for more revision --><!-- 17 May 92 : CMSMcQ : began draft                         --><div2 id="STCO" name="bar" ref="Y"><head>Combining TEI Base Tag Sets</head><p>The TEI DTD has been designed to simplify the task of choosing an
appropriate set of tags for the text in hand.  The core tag set includes
tags appropriate to the majority of simple tagging requirements for
prose, verse and drama, irrespective of the base tag set chosen.  For
more detailed tagging, the encoder may choose the prose base for prose
texts, the verse base for verse, and so on.</p><p>In discussing these base tag sets elsewhere in these Guidelines, it
is generally assumed for clarity of exposition that a text will fall
into one, not several, of these types.  It is not uncommon, however, for
a text to combine prose and verse, or other forms treated by the TEI as
different bases.  Examples include:
 
<list type="bullets"><item>when the text is a collection of other texts, which do not all use
the same base:  e.g. an anthology of prose, verse, and drama</item><item>when the text contains other smaller, embedded texts:  e.g. a poem
or song included in a prose narrative</item><item>when some sections of the text are written in one form, and others
in a different form:  e.g. a novel where some chapters are in prose,
others take the form of dictionary entries and still others the form of
scenes in a play</item><item>when the text moves back and forth among forms not between
sections but within a single section:  e.g. mixed prose-and-verse forms
like many pastorals or like some portions of the Poetic Edda</item></list></p><p>The TEI DTD provides the following mechanisms to handle these cases:
 
<list type="bullets"><item>a definition of a corpus or collection as a series of
<gi tei="yes">tei.2</gi>
documents, sharing a common TEI header (see chapter <xref target="CC"/>)</item><item>a definition of composite texts which comprise front matter, a
group or several possibly nested groups of collected texts,
themselves possibly composite (see section <xref target="DSGRP"/>)</item><item>a notion of <term>embedded text</term>
which allows one text to be embedded within another (that is,
<gi tei="yes">text</gi> is defined as a component-level element, as described
briefly at the conclusion of section <xref target="DSGRP"/>)</item></list></p><p>Whichever mechanism is adopted, if the whole of the resulting
document is to be parseable by the main TEI DTD it may need to combine
elements from different TEI base tag sets.  Two special-purpose base
tag sets are defined for this purpose:
 
<list type="simple"><item>the <term>general</term> base, which allows different sections of a
text to use different bases, but ensures that each section uses
only one base</item><item>the <term>mixed</term> base, which allows chunk- and
inter-level elements from any base to mix within any text division</item></list></p><p>When either of these <soCalled>combined</soCalled> bases is used, the
user must specify all of the other bases to be included in the mix as
well as either the general or the mixed base.  This is the only
exception to the general rule that no more than one base tag set may be
enabled in a TEI document.
 <!-- it's an error to specify both mixed and general, tho we can't --><!-- stop you -->
 
The following set of declarations for example allows for any mixture of
the low level structural tags defined in the prose, drama and dictionary
base tag sets:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
   <!ENTITY % TEI.mixed 'INCLUDE' >
   <!ENTITY % TEI.prose 'INCLUDE' >
   <!ENTITY % TEI.drama 'INCLUDE' >
   <!ENTITY % TEI.dictionaries 'INCLUDE' >
   <!-- Structurally, Moby Dick is not your
    everyday common or garden variety novel ... -->
 ]>]]></eg>
 
The following set of declarations has the same effect, but with the
additional restriction that each text division (i.e. each member of the
element class <ident tei="yes" type="class">divn</ident>) must be homogenous with
respect to the mixture of available bases.  Because in a
<soCalled>general</soCalled> base, each <gi tei="yes">div</gi> of the text may use
a different base, the divisions of the text prefixed by this set of
declarations will each be composed of elements taken solely from one of
the prose, verse or dictionary base tag sets:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
   <!ENTITY % TEI.general 'INCLUDE' >
   <!ENTITY % TEI.prose 'INCLUDE' >
   <!ENTITY % TEI.drama 'INCLUDE' >
   <!ENTITY % TEI.dictionaries 'INCLUDE' >
 ]>]]></eg>
 <!-- <p>For further discussion of mixing TEI bases, see       --><!-- chapter <xref target=CB>.                                --></p><p>The actual DTD fragments for the combined bases do nothing but
embed the default tag set for overall text structure.
The mixed-base tag set is in file <ident tei="yes" type="file">teimix2.dtd</ident>:
 
<dtdFrag id="DSTCBMX" n="Mixed-Base Tag Set" file="teimix2.dtd"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></dtdFrag>
 
The general-base tag set is in file
<ident tei="yes" type="file">teigen2.dtd</ident>:
<dtdFrag id="DSTCBGN" n="General-Base Tag Set" file="teigen2.dtd"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></dtdFrag></p></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2stco.odd ??><!-- 4 Combining TEI DTDfrags --><?tei:SOF p2stga.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2stga.odd,v $
    * Revision 1.9  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.8  94/04/08  01:36:34  msmcq
    * Last-round changes before publication of P3
    * 
    * Revision 1.7  1994/03/28  16:34:42  msmcq
    * back out version 1.6, which once more overwrites msm changes in error
    * 
    * Revision 1.5  1994/03/27  23:03:43  msmcq
    * restore changes made in version 1.3, overwritten by 1.4 in error.
    * 
    * Revision 1.3  1994/03/24  22:20:40  msmcq
    * typos found by David Barnard et al. corrected
    * --><!-- P2.133 :  Global Attributes                              --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : typos, minor fixes from MSM             --><!-- 94-03-22 : MSM : typos from DB, EBr, JLav                --><!-- 94-03-22 : MSM : retag some TERMs, Qs, as CODE, IDENT    --><!-- 94-03-21 : MSM : typos, corrections, stylistic changes   --><!--                  as suggested by WWP proofreading team   --><!--                  Including new paras on TEIform att      --><!-- 93-09-13 : MSM : add default declarations of inherited global atts --><!-- 93-04-06 : MSM : mostly cosmetic changes                 --><!-- 3 apr 93 : LB revise for publication                     --><!--     cut some kindergarten stuff; tried to obscure probs  --><!--   w. rendition and teiform; plus minor changes in wording --><!-- 93-03-30 : MSM : minor changes for LB                    --><!-- 93-03-16 : MSM : minor fixes for clarity, from J.Lav.    --><!-- 93-03-06 : MSM : fix xrefs to CO, HD                     --><!-- 93-03-06 : MSM : minor fixes for clarity                 --><!-- 93-03-06 : MSM : minor changes for pedantry              --><!-- 93-03-04 : MSM : trivial sgml fix                        --><!-- 93-01-27 : MSM : correct ref to ccedil                   --><!-- 21 Oct 92 : CMSMcQ : new name new id some text.          --><!-- 17 May 92 : CMSMcQ : began draft                         --><div2 id="STGA" name="bar" ref="Y"><head>Global Attributes</head><p>The following attributes are defined for every TEI element.<note source="auth" place="display" anchored="Y">More
exactly, these are the attributes of the element class
<ident tei="yes" type="class">global</ident>, to which all elements belong; for
further discussion of attribute classes and ways in which attributes
may be inherited and over-ridden, see section <xref target="STECAT"/>.</note>
 
<adList classDoc="GLOBAL" atts="id n lang rend"/>
 </p><p>Some tag sets (e.g. those for terminology, linking, and analysis)
define other global attributes; these are documented in the appropriate
chapters of Part III and Part IV.  See also section <xref target="STECAT"/>.
 </p><p>An additional attribute, <att tei="yes">TEIform</att>, is also defined
for every TEI element.  Unlike the other attributes defined for every
element, <att tei="yes">TEIform</att> is not defined by class <ident tei="yes" type="class">global</ident> because its default value is different in
every case and must be defined individually for each element.<note source="auth" place="foot" anchored="Y">A dummy element class <ident tei="yes" type="class">TEIform</ident> is
defined in the reference section, solely for documentary purposes.</note>
 
<adList classDoc="TEIFORM" atts="TEIform"/>
 </p><p>Any TEI element may be given values for <att tei="yes">id</att>, <att tei="yes">n</att>,
<att tei="yes">lang</att>, <att tei="yes">rend</att>, or <att tei="yes">TEIform</att>, simply by
specifying values for these attributes.
 <!-- not sure if this is not too obvious here, but left it in for now -->
 
The following two examples convey the same information about the text:
that the material transcribed occurs within a <gi tei="yes">p</gi> element
(paragraph).  They differ only in that the second provides an identifier
for the paragraph, to which other elements (e.g. notes or hypertext
links) can conveniently refer.
 
<eg><![CDATA[<p>If to do were as easy as to know what were
good to do, chapels had been churches and poor men's cottages
princes' palaces.  It is a good divine that follows his own
instructions ...</p>]]></eg>
 
<eg><![CDATA[<p id='MV1.2.5'>If to do were as easy as to know what were
good to do, chapels had been churches and poor men's cottages
princes' palaces.  It is a good divine that follows his own
instructions ...</p>]]></eg><!-- Merchant of Venice, I.ii, speech 5 (Portia)              -->
 </p><p>ID values must be legal SGML names; by default, this means they must
begin with a letter from A to Z or a to z and contain no characters
other than the letters A to Z or a to z, the digits 0 to 9, the full
stop, and the hyphen.  Furthermore, by default upper and lower case
letters are not distinguished:  thus, the strings <cited>a23</cited> and
<cited>A23</cited> are identical, and may not be used to identify two
distinct elements.
 <!-- delete from here .... -->
 <!--                                                          --><!-- Under the reference concrete syntax of SGML, ID values   --><!-- do not distinguish between upper and lower case.  The    --><!-- following are thus legal names and thus legal values     --><!-- for  < att > id < /att > , of which the first two pairs are --><!-- synonyms:                                                --><!--                                                          --><!--  < list type=simple >                                    --><!--  < item > A                                              --><!--  < item > a                                              --><!--  < item > e23                                            --><!--  < item > E23                                            --><!--  < item > init.                                          --><!--  < item > Chapter.1                                      --><!--  < item > Ovid.Met.9.10-11                               --><!--  < item > x78y                                           --><!--  < /list >                                               --><!--                                                          --><!-- while the following are  < emph > not < /emph >  legal   --><!-- names in the default SGML syntax (though the SGML        --><!-- declaration might be modified to make some of them       --><!-- legal): < note place=foot > The first three are          --><!-- illegal because they do not begin with a letter; the     --><!-- last four because they contain non-name characters. <    --><!-- /note >                                                  --><!--                                                          --><!--  < list type=simple >                                    --><!--  < item > 23                                             --><!--  < item > 35mm                                           --><!--  < item > .init                                          --><!--  < item > a_name_with_underscores                        --><!--  < item > a name with spaces                             --><!--  < item > fran&ccedil;ais                                --><!--  < item > x*#$@!                                         --><!--  < /list >                                               --><!--                                                          --><!--  < p > ID values must be unique within the SGML          --><!-- document; if two elements                                --><!-- to here -->
 
If two elements are given the same identifier, the SGML parser will
signal a syntax error.  The following example, therefore, is
<emph>not</emph> valid:
 
<eg><![CDATA[<p id=PAGE1><q>What's it going to be then, eh?</q></p>
<p id=PAGE1>There was me, that is Alex, and my three droogs,
that is Pete, Georgie, and Dim, ... </p>]]></eg><!-- Clockwork Orange, opening -->
 </p><p>For a discussion of methods of providing unique identifiers for
elements, see section <xref target="CORS2"/>.
 </p><p>The <att tei="yes">n</att> attribute allows identifying information (e.g.
chapter numbers, etc.) to be encoded even if it would not be a legal
<att tei="yes">id</att> value.  Its value may be any string of characters;
typically it is a number or other similar enumerator or label.  For
example, the numbers given to the items of a numbered list may be
recorded with the <att tei="yes">n</att> attribute; this would make it possible to
record errors in the numeration of the original, as in this list of
chapters, transcribed from a faulty original in which the number 10 is
used twice, and 11 is omitted:
 
<eg><![CDATA[<list type=ordered>
<item n=1>About These Guidelines
<item n=2>A Gentle Introduction to SGML
<!-- ... -->
<item n=9>Verse
<item n=10>Drama
<item n=10>Spoken Materials
<!-- sic:  original has '10' twice! -->
<item n=12>Printed Dictionaries
<!-- ... -->
</list>]]></eg>
 
The <att tei="yes">n</att> attribute may also be used to record non-unique names
associated with elements in a text, possibly together with a unique
identifier as in the following examples:
 
<eg><![CDATA[  <div type=chap n='One' id='TXT0101'>]]></eg>
 
<eg><![CDATA[  <div type=stanza n='xlii'>]]></eg>
 </p><p>The <att tei="yes">lang</att> attribute indicates the language, writing system,
and character set associated with a given element and all its contents.
If it is not specified, the value is inherited from that of the
immediately enclosing element.  As a rule, therefore, it is simplest to
specify the base language of the text on the <gi tei="yes">tei.2</gi> element, and
allow most elements to take the default value for <att tei="yes">lang</att>; the
language of an element then need be explicitly specified only for
elements in languages other than the base language.
 </p><p>The following two encodings convey the same information about the
language of the text, since in the first the <att tei="yes">lang</att> attributes
on the <gi tei="yes">emph</gi> elements specify the same value as that on the
parent <gi tei="yes">p</gi> element, while in the second they inherit that value
without specifying it.
 
<eg><![CDATA[ <p lang=en> ... Both parties deprecated war, but one of
 them would <emph lang=en>make</emph> war rather than let
 the nation survive, and the other would <emph lang=en>accept
 </emph> war rather than let it perish, and the war came.</p>]]></eg>
 
<eg><![CDATA[ <p lang=en> ... Both parties deprecated war, but one of
 them would <emph>make</emph> war rather than let
 the nation survive, and the other would <emph>accept</emph>
 war rather than let it perish, and the war came.</p>]]></eg>
 <!-- Lincoln's Second Inaugural Address, 4 March 1865, rpt.   --><!-- (from Richardson, ed., Messages and Papers, 6:276ff) in  --><!-- H. S. Commager, ed., Documents of American History, 5th  --><!-- ed.  (New York:  Appleton-Century-Crofts, 1949), p.      --><!-- 442.                                                     -->
 </p><p>In the following example, by contrast, the <att tei="yes">lang</att> attribute
on the <gi tei="yes">term</gi> element must be given if we wish to record the fact
that the technical terms used are Latin rather than English; no
<att tei="yes">lang</att> attribute is needed on the <gi tei="yes">q</gi> element, by
contrast, because it is in the same language as its parent.  It is
strongly recommended that all language shifts in the source be
explicitly identified by use of the <att tei="yes">lang</att> attribute, as
described in chapter <xref target="CH"/>.
 <!-- Choose one?  i vote to keep both. -MSM --><!-- I chose one. --><!-- < eg > --><!-- < ! [ CDATA [ --><!--  < p lang=en > ... If they do afford him a remedy, is it --><!--  a < term lang=la >mandamus< /term> issuing from this court? ... --><!--  < / p > --><!-- ] ]> --><!-- < / eg > --><!-- Marbury v. Madison, 1 Cranch, 137 (1803), rpt. in H. S.  --><!-- Commager, ed., Documents of American History, 5th ed.    --><!-- (New York:  Appleton-Century-Crofts, 1949), p. 191.      -->
 
<eg><![CDATA[ <p lang=en>The constitution declares <q>that no bill of
 attainder or <term lang=la>ex post facto</term> law shall
 be passed.</q> ... </p>]]></eg>
 <!-- Marbury v. Madison, 1 Cranch, 137 (1803), rpt. in H. S.  --><!-- Commager, ed., Documents of American History, 5th ed.    --><!-- (New York:  Appleton-Century-Crofts, 1949), p. 192.      -->
 </p><p>Formally, the <att tei="yes">lang</att> attribute is an
<code tei="yes" type="kw">IDREF</code>; a reference
to the <att tei="yes">id</att> value of a <gi tei="yes">language</gi> element in the TEI
header.<note source="auth" place="foot" anchored="Y">SGML validation checks that all
<code tei="yes" type="kw">IDREF</code> values
exist as <att tei="yes">id</att> values on elements somewhere in the current SGML
document.  It is a requirement of the TEI scheme, not of SGML, that the
<att tei="yes">lang</att> attribute point to a <gi tei="yes">language</gi> element.</note>
This means that each language used in the document should be declared in
the TEI header using the <gi tei="yes">language</gi> element defined in section<xref target="HD41"/>
.
 </p><p>The <att tei="yes">rend</att> attribute is used to give information about the
physical presentation of the text in the source.  In the following
example, it is used to indicate that both the emphasized word and the
proper name are printed in italics:
 
<eg><![CDATA[ <p> ... Their motives <emph rend='italics'>might</emph> be
 pure and pious; but he was equally alarmed by his knowledge
 of the ambitious <name rend='italics'>Bohemond</name>, and
 his ignorance of the Transalpine chiefs: ...</p>]]></eg>
 <!-- Gibbon, Decline and Fall, chapter 58, para beginning     --><!-- 'In some Oriental tale I have read ...', p. 391 of       --><!-- Britannica edition.                                      --><!--  ... played fast and loose with by LB for pedagogic purposes --><!-- Shame, shame.                                            -->
 
If all or most <gi tei="yes">emph</gi> and <gi tei="yes">name</gi> elements are rendered in
the text by italics, it will be more convenient to register that fact in
the TEI header once and for all and specify a <att tei="yes">rend</att> value
only for any elements which deviate from the usual rendition.
 </p><p>The contents of the <att tei="yes">rend</att> attribute are free text.  In any
given project, encoders are advised to settle on a standard vocabulary
with which to describe typographic or manuscript rendition of the text,
and to document their usage of that vocabulary in the <gi tei="yes">rendition</gi>
element of the TEI header.
 <!-- Although no consensus exists in practice, however, to    --><!-- allow for standardization of such vocabularies for all   --><!-- projects. The standard vo                                --><!--                                                          --><!-- < note place=foot >  [However, the < gi >                --><!-- encodingDesc < /gi >  or the  < gi > profileDesc < /gi   --><!-- >  does need to be able to document the language used,   --><!-- somehow.  Formal facilities for language definition      --><!-- would be useful but are out of the question:  no one     --><!-- knows how best to construct a rendition language.  It    --><!-- would be nice to be able at least to include prose or    --><!-- a bibliographic reference, though.  -MSM]  <  /note  >   -->
 </p><p>The <att tei="yes">TEIform</att> attribute is used to allow application
programs to handle TEI-encoded documents correctly even if some or all
elements have been renamed.  Most users can ignore this attribute
entirely; it is only relevant when the TEI DTDs are modified.  <note source="auth" place="foot" anchored="Y">The <att tei="yes">TEIform</att> attribute is based on the notion of
<term>architectural forms</term> developed for HyTime (ISO 10744).<!-- The details, however, vary. --></note>
 </p><p>The default value of <att tei="yes">TEIform</att> for any element is the
generic identifier of that element, as described in this document.  The
value for <gi tei="yes">p</gi> is <cited>p</cited>, the value for <gi tei="yes">div1</gi> is
<cited>div1</cited>, etc.  When elements are renamed, as described in
chapter <xref target="MD"/>, the declaration of <att tei="yes">TEIform</att> is not
modified.  If <gi tei="yes">div1</gi> is renamed <gi tei="no">chapter</gi>, for
example, the default value of <att tei="yes">TEIform</att> remains
<cited>div1</cited>.  An application program which does not recognize
the new generic identifier can check to see whether the attribute
<att tei="yes">TEIform</att> exists, and examine its value if it does to find out
which TEI element, if any, is being used.
 </p><p>Modifications of DTDs, however, may involve more than simple renaming
of elements:  sometimes elements are given not just new names, but
complete new definitions.  In such cases, the <att tei="yes">TEIform</att>
attribute may be used to indicate the standard TEI element
corresponding to the modified element.  For example, if a local
modification of a DTD renamed the <gi tei="yes">div1</gi> element as <gi tei="no">chapter</gi> and also modified its formal declarations (e.g. to
change its content model), then the <att tei="yes">TEIform</att> attribute on the
modified element should be given the default value <code tei="yes" type="val">div1</code>, in order to indicate that the local <gi tei="no">chapter</gi> element is a modification of the standard TEI
<gi tei="yes">div1</gi>.
 </p><p>When new elements are introduced, they may be identified as
specialized variants of existing TEI elements by giving them the
appropriate default value for <att tei="yes">TEIform</att>.  For example, if a
local element called <gi tei="no">quatrain</gi> were introduced, as a
specialized variant of the <gi tei="yes">lg</gi> (line group) element which must
contain exactly four lines, then its declaration might give its
<att tei="yes">TEIform</att> as <code tei="yes" type="val">lg</code>, to signify that a
quatrain is a particular type of line group, thus:
 
<eg><![CDATA[ <!ELEMENT quatrain - O (l, l, l, l)            >
 <!ATTLIST quatrain     %a.global
           TEIform      (lg)            'lg'    >]]></eg>
 
 <!-- Following paragraph deleted as being, alas, not true.    --><!-- It should be made true for P4.  (msm)                    -->
 <!-- <p>Constraints on the use of <att>TEIform</att> (rules   --><!-- determining when it is legitimate, and when not, to      --><!-- identify a new element as corresponding to a given TEI   --><!-- element) are given in chapter <xref target=MD>.          --><!-- Further discussion of the relationship between the TEI   --><!-- DTD and other standard DTDs is given in chapter <xref    --><!-- target=OS>.                                              -->
 
 <!-- < p >N.B. Future versions of the TEI encoding scheme     --><!-- may add new global attributes to relate TEI elements     --><!-- to the architectural forms of HyTime and the DTD being   --><!-- prepared by ICADD (International Committee on            --><!-- Accessible Document Design) to aid in the automatic      --><!-- conversion of electronic text to level-2 Braille.        --><!-- Would have been this version if their draft had been ready. -->
 </p><p>The formal definition of the global attributes is as follows:
 
<dtdFrag id="DSTGA" n="Global attributes"><commDecl>The global attributes are defined for every element in the TEI
tag set; individual declarations may be overridden by local declarations
for individual elements.</commDecl><commDecl>If the tag sets invoked by the user define extra global
attributes (they do this in their .ent file), then they are inherited by
GLOBAL; otherwise the parameter entities referred to expand to the empty
string, as shown here.  </commDecl><claDecl classDoc="DFTANA" type="atts"/><claDecl classDoc="DFTLINK" type="atts"/><claDecl classDoc="DFTTERM" type="atts"/><claDecl classDoc="GLOBAL" type="atts"/><commDecl>The TEIform attribute is also global, but is declared
individually for each element, not in a parameter entity
declaration.</commDecl></dtdFrag><!-- <claDecl type=atts classDoc=DFTSPOK>                     --><!-- <claDecl type=atts classDoc=DFTCERT>                     --><!-- <claDecl type=atts classDoc=DFTFS>                       --><?tei:EOF p2stga.odd ??><!-- 5 Global Attributes      --><?tei:SOF p2stov.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2stov.odd,v $
    * Revision 1.8  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.7  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.6  1994/04/08  01:36:34  msmcq
    * Last-round changes before publication of P3
    * 
    * Revision 1.5  1994/04/01  16:36:47  msmcq
    * changes / fixes during validation of DTD
    * 
    * Revision 1.4  1994/03/24  22:20:40  msmcq
    * typos found by David Barnard et al. corrected
    * 
    * Revision 1.3  1994/03/16  03:28:24  msmcq
    * changes a propos of PH
    * --><!-- Revisions:                                               --><!-- 94-04-08 : MSM : use ftdtd, not gfdtd ent                --><!-- 94-04-07 : MSM : confuse discussion of conformance       --><!-- 94-03-30 : MSM : suppress ref to lmdtd                   --><!-- 94-03-22 : MSM : retag some TERMs, Qs, as CODE, IDENT    --><!-- 94-03-22 : MSM : typos from WWP team, EBr, JLav          --><!-- 94-03-07 : MSM : rename physical as transcr              --><!-- 93-09-14 : MSM : move IGNORE keywords to dSTpekw         --><!-- 93-09-14 : MSM : dictionar-ies not -y                    --><!-- 93-04-06 : MSM : minor changes:  style, typos, slips     --><!-- 3 apr 93 : LB revise for publication                     --><!--       stylistic changes consequent on singularization    --><!--       extended discussion of example a bit (and fixed typo) --><!-- 93-03-30 : MSM : changes, cleanup for LB                 --><!-- 93-03-24 : MSM : remove dup decls for XXtop entities     --><!-- 93-03-23 : MSM : fill out dtd frags, misc rev            --><!-- 93-03-16 : MSM : add health warning at beginning, add    --><!--                  discussion of user tag sets             --><!-- 93-03-06 : MSM : add initial overview                    --><!-- 93-03-06 : MSM : break out local mods into separate section --><!-- 93-03-04 : MSM : change p2st- ids to ST                  --><!-- 93-03-04 : MSM : trivial sgml fix                        --><!-- 93-03-04 : MSM : remove TERM gi from inside commdecl     -->
 </p></div2><div2 id="STOV" name="bar" ref="Y"><head>The TEI2.DTD File</head><p>All TEI-encoded documents use the same top-level DTD file, which
refers to a number of other DTD files, the exact set of other files
referred to depending on which base and which additional tagsets are in
use.  The remainder of this chapter describes in some detail the
organization and function of this file and those it embeds; it is
necessarily of a rather technical and specialized nature.
 <!--                                                          --><!-- Most readers can skip or skim these sections:  they      --><!-- document the precise usage of SGML marked sections and   --><!-- parameter entities to perform various operations         --><!-- behind the scenes with which most users need not         --><!-- concern themselves.  Those who do need to know exactly   --><!-- what is happening at a detailed level should study the   --><!-- following description carefully.                         --><!--                                                          --><!--                                                          --><!-- < p > In addition to the files for core, base, and       --><!-- additional tag sets described in section  < xref         --><!-- target=STBA > , the TEI DTD uses the following files:    --><!--                                                          --><!--   < list type=gloss >                                    --><!--   < label >  < term > tei2.dtd < /term >   < item >      --><!-- main, top-level DTD driver file                          --><!--   < label >  < term > teigis2.ent < /term >   < item >   --><!-- declares parameter entities for                          --><!--  TEI generic identifiers; see section  < xref            --><!-- target=STPEGI >                                          --><!--   < label >  < term > teiclas2.ent < /term >   < item    --><!-- > declares parameter entities for                        --><!--  TEI element classes; see section  < xref                --><!-- target=STECOV >                                          --><!--   < /list >                                              --><!--                                                          --><!--  Fragments of these files are included in other          --><!-- sections of this chapter;                                --><!--  this section provides the top-level overview of the     --></p><p>The main TEI DTD is always invoked by specifying the file
<ident tei="yes" type="file">tei2.dtd</ident>.  This file:
 
<list type="ordered"><item>takes care of certain necessary preliminaries:
 
<list type="ordered"><item>embeds any locally defined changes to the standard TEI
parameter entities, so that local modifications can take precedence
over default declarations;</item><item>declares TEI-specific keywords used in other declarations and
declares default values of <code tei="yes" type="kw">IGNORE</code> for all the
parameter entities used to select base and additional tag sets (see
section <xref target="STPEKW"/>);</item><item>declares parameter entities for TEI generic identifiers (by
embedding the file <ident tei="yes" type="file">teigis2.ent</ident>; see section<xref target="STPEGI"/>
);</item></list></item><item>declares parameter entities for element classes, content models,
and global attributes (by embedding <ident tei="yes" type="file">teiclas2.ent</ident>; see section <xref target="STECOV"/>);</item><item>declares the top-level elements <gi tei="yes">tei.2</gi> and
<gi tei="yes">teiCorpus.2</gi>;</item><item>embeds DTD files containing local modifications (if any),
the core tag sets, the base tag set, and the additional tag sets.</item></list></p><div3 id="STOVOV" name="burp" ref="Y"><head>Structure of the TEI2.DTD File</head><p>Each parameter entity associated with a tag set controls several
marked sections in the main DTD file <ident tei="yes" type="file">tei2.dtd</ident>.
If the entity has been declared in the DTD subset with the text <code tei="yes" type="kw">INCLUDE</code>, then the marked sections it controls will be
parsed; otherwise, they will be ignored.  The marked sections controlled
by each entity:
 
<list type="ordered"><item>declare and refer to the entity file for the tag set,
which defines its global attributes and element classes</item><item>declare and refer to the DTD file for the tag set,
which defines its elements and their attributes</item><item>declare the parameter entity <ident tei="yes" type="pe">component</ident>) in
a form suitable for texts using that base</item></list></p><p>The <ident tei="yes" type="file">tei2.dtd</ident> file has the following
structure:
 
<dtdFrag id="DSTTEI2" n="File tei2.dtd:  Main document type declaration file" file="tei2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>This file first defines some useful entities, then defines the
element TEI.2 and includes files with the various specialized parts of
the document type declaration.  It also declares the top-level TEI.2
and TEI.2.corpus elements.</commDecl><commDecl>I.  Preliminaries.</commDecl><commDecl>Embed any local modifications to TEI entities.</commDecl><dtdRef dtdFrag="DSTOVLE"/><commDecl>Embed entities for TEI generic identifiers.</commDecl><entDecl entDoc="TEIGIS"/><peRef n="TEI.elementNames"/><commDecl>Define entities for TEI keywords.</commDecl><commDecl>This includes defining the default for each base and additional
tag set as 'IGNORE'.</commDecl><dtdRef dtdFrag="DSTPEKW"/><commDecl>II. Define element classes for content models, shared
attributes for element classes, and global attributes.  (This all
happens within the file TEIclas2.ent.)</commDecl><entDecl entDoc="TEIECGA"/><peRef n="TEI.elementClasses"/><commDecl>III.  Define the top-level TEI elements:  one for individual
texts, one for composites with a collective header.</commDecl><commDecl>A TEI document is a text preceded by a TEI header.</commDecl><tagDecl tagDoc="TEI2"/><commDecl>A TEI corpus is a series of TEI.2 documents, preceded by a
corpus-level TEI header.</commDecl><tagDecl tagDoc="TEICORP2"/><commDecl>IV.  Embed the actual tag sets.  First embed any local
modifications and extensions.  Then embed the core tag sets, the
(single) base tag set, and the (optional) additional tag sets specified
by the user.</commDecl><dtdRef dtdFrag="DSTOVLO"/><dtdRef dtdFrag="DSTOVCO"/><dtdRef dtdFrag="DSTOVBA"/><dtdRef dtdFrag="DSTOVAD"/></dtdFrag></p><p>A TEI-conformant document <emph>must</emph> use the <ident tei="yes" type="file">tei2.dtd</ident> file, or one derived from it in the manner
described in chapter <xref target="MD"/>.
It must also specify which base and
which additional tag sets are to be invoked, using the mechanisms
described in section <xref target="STIN"/>.</p></div3><div3 id="STOVLO" name="burp" ref="Y"><head>Embedding Local Modifications</head><p>As noted above in section <xref target="STBAUS"/>, local modifications
to the DTD are most conveniently grouped into two files, one containing
modifications to the TEI parameter entities, and the other new or
changed declarations of elements and their attributes.  These files
should be associated with the parameter entities
<ident tei="yes" type="pe">TEI.extensions.ent</ident> and
<ident tei="yes" type="pe">TEI.extensions.dtd</ident> by declarations included in
the document's DTD subset.</p><p>For example, if the relevant files are called <ident rend="noindex" tei="yes" type="file">project.ent</ident> and <ident rend="noindex" tei="yes" type="file">project.dtd</ident>, then declarations like the following
would be appropriate:
 
<eg><![CDATA[ <!ENTITY % TEI.extensions.ent SYSTEM 'project.ent' >
 <!ENTITY % TEI.extensions.dtd SYSTEM 'project.dtd' >]]></eg></p><p>When an SGML entity is declared more than once, the first declaration
is binding and the others are ignored.  The local modifications to
parameter entities should therefore be handled before the standard
parameter entities themselves are declared in <ident tei="yes" type="file">tei2.dtd</ident>.  The entity <ident tei="yes" type="pe">TEI.extensions.ent</ident> is referred to before any TEI
declarations are handled, to allow the user's declarations to take
priority.  If the user does not provide a <ident tei="yes" type="pe">TEI.extensions.ent</ident> entity, the entity will be expanded
to the empty string.</p><p>For example the encoder might wish to add two phrase-level elements
<gi tei="no">it</gi> and <gi tei="no">bd</gi>, perhaps as synonyms for
<tag compl="full" tei="yes">hi rend='italics'</tag> and <tag compl="full" tei="yes">hi rend='bold'</tag>.  As
described in chapter <xref target="MD"/>, this involves two distinct steps:
one to define the new elements, and the other to ensure that they are
placed into the TEI document structure at the right place.  We deal with
the second first, by specifying the element class to which the new
elements should be attached.  To do this, the standard parameter entity
<ident tei="yes" type="pe">x.phrase</ident> should be modified to include the two
new generic identifiers.  The file containing local declarations of the
standard parameter entities will thus contain a declaration of the
following form:
 
<eg><![CDATA[ <!ENTITY % x.phrase 'it | bd |' >]]></eg></p><p>The relevant fragment of the DTD is this:
 
<dtdFrag id="DSTOVLE" n="Local modifications to parameter entities"><commDecl>Embed local modifications to TEI parameter entities.  Declare
entity as empty string first, in case user has no mods and has not
declared it.</commDecl><entDecl entDoc="TEIEXTE"/><peRef n="TEI.extensions.ent"/></dtdFrag></p><p>The second type of modification needed is most conveniently performed
after all the standard TEI parameter entities have been declared; this
allows the element declarations provided by the user to make use of the
parameter entities which define standard TEI content models and
attribute definitions.  To facilitate this, the parameter entity
<ident tei="yes" type="pe">TEI.extensions.dtd</ident> is used to embed local element
declarations <emph>before</emph> any of the TEI tag sets are embedded by
the file <ident tei="yes" type="file">tei2.dtd</ident>, but <emph>after</emph> all
the TEI element classes and other parameter entities have been declared.</p><p>The task of declaring the non-standard <gi tei="no">it</gi> and <gi tei="no">bd</gi> elements is thus simplified:  they can, for example, use
the same parameter entities as the <gi tei="yes">hi</gi> element.  A suitable
local DTD-modifications file might look like the following (note that
the standard parameter-entity reference for phrase sequence is used):
 
<eg><![CDATA[ <!ELEMENT it           - -  (%phrase.seq)                      >
 <!ATTLIST it
           id                ID             #IMPLIED
           lang              IDREF          %INHERITED
           n                 CDATA          #IMPLIED
           rend              CDATA          #FIXED 'italics'    >
 <!ELEMENT bd           - -  (%phrase.seq)                      >
 <!ATTLIST bd
           id                ID             #IMPLIED
           lang              IDREF          %INHERITED
           n                 CDATA          #IMPLIED
           rend              CDATA          #FIXED 'boldface'   >]]></eg></p><p>For further examples of local modifications to both parameter
entities and element declarations, see chapter <xref target="MD"/>.</p><p>The relevant fragment of the DTD is this:
<dtdFrag id="DSTOVLO" n="Embed local element declarations, etc."><commDecl>Embedding local modifications here allows user modifications
to use all the standard TEI element classes and parameter entities.</commDecl><entDecl entDoc="TEIEXTD"/><peRef n="TEI.extensions.dtd"/></dtdFrag></p></div3><div3 id="STOVCO" name="burp" ref="Y"><head>Embedding the Core Tag Sets</head><p>The core tag sets are embedded by the file <ident tei="yes" type="file">tei2.dtd</ident> using the parameter entities <ident tei="yes" type="pe">TEI.header</ident> and <ident tei="yes" type="pe">TEI.core</ident>.  The
relevant fragment of the DTD is this:
 
<dtdFrag id="DSTOVCO" n="Embed the core tag sets"><commDecl>These occur in all documents and are therefore defined
unconditionally.</commDecl><entDecl entDoc="TEIHDR"/><peRef n="TEI.header.dtd"/><entDecl entDoc="TEICORE"/><peRef n="TEI.core.dtd"/></dtdFrag></p><p>The default text structure tags, which are also documented as part of
the core, are embedded by the base tag set, unless the base defines its
own text structure tags; see the chapters on the individual bases.</p></div3><div3 id="STOVBA" name="burp" ref="Y"><head>Embedding the Base Tag Set</head><p>The <ident tei="yes" type="file">tei2.dtd</ident> file embeds the appropriate
files for the base tag set previously selected by means of the parameter
entities described in section <xref target="STBA"/>.  A parameter entity
for the file containing the relevant DTD fragment is declared and
referred to inside a conditional marked section controlled by the
appropriate parameter entity.  The relevant fragment of <ident tei="yes" type="file">tei2.dtd</ident> is this:
 
<dtdFrag id="DSTOVBA" n="Embed base tag set"><commDecl>A different base will be embedded, depending on which
parameter entity has been declared by the user
with the value 'INCLUDE'.</commDecl><msection keywords="%TEI.prose"><entDecl entDoc="PRDTD"/><peRef n="TEI.prose.dtd"/></msection><msection keywords="%TEI.verse"><entDecl entDoc="VEDTD"/><peRef n="TEI.verse.dtd"/></msection><msection keywords="%TEI.drama"><entDecl entDoc="DRDTD"/><peRef n="TEI.drama.dtd"/></msection><msection keywords="%TEI.spoken"><entDecl entDoc="TSDTD"/><peRef n="TEI.spoken.dtd"/></msection><msection keywords="%TEI.dictionaries"><entDecl entDoc="DIDTD"/><peRef n="TEI.dictionaries.dtd"/></msection><msection keywords="%TEI.terminology"><entDecl entDoc="TEDTD"/><peRef n="TEI.terminology.dtd"/></msection><msection keywords="%TEI.general"><entDecl entDoc="CBGEDTD"/><peRef n="TEI.general.dtd"/></msection><msection keywords="%TEI.mixed"><entDecl entDoc="CBMXDTD"/><peRef n="TEI.mixed.dtd"/></msection></dtdFrag><!-- <msection keywords='%TEI.letters'>                       --><!-- <entDecl entDoc=LMDTD>                                   --><!-- <peRef n='TEI.letters.dtd'>                              --><!-- </msection>                                              --></p></div3><div3 id="STOVAD" name="burp" ref="Y"><head>Embedding the Additional Tag Sets</head><p>The <ident tei="yes" type="file">tei2.dtd</ident> file embeds the appropriate
files for any additional base tag set previously enabled by means of the
parameter entities described in section <xref target="STBA"/>.  A parameter
entity for the file containing the relevant DTD fragment is declared and
referred to, inside a conditional marked section controlled by the
appropriate parameter entity.  The relevant fragment of <ident tei="yes" type="file">tei2.dtd</ident> is this:
 
 
<dtdFrag id="DSTOVAD" n="Embed additional tag sets"><commDecl>These entities are declared and embedded only when the user
has overridden the default declaration of IGNORE for a specific
additional tag set.</commDecl><msection keywords="%TEI.linking"><entDecl entDoc="SADTD"/><peRef n="TEI.linking.dtd"/></msection><msection keywords="%TEI.analysis"><entDecl entDoc="AIDTD"/><peRef n="TEI.analysis.dtd"/></msection><msection keywords="%TEI.fs"><entDecl entDoc="FSDTD"/><peRef n="TEI.fs.dtd"/></msection><msection keywords="%TEI.certainty"><entDecl entDoc="CEDTD"/><peRef n="TEI.certainty.dtd"/></msection><msection keywords="%TEI.transcr"><entDecl entDoc="PHDTD"/><peRef n="TEI.transcr.dtd"/></msection><msection keywords="%TEI.textcrit"><entDecl entDoc="TCDTD"/><peRef n="TEI.textcrit.dtd"/></msection><msection keywords="%TEI.names.dates"><entDecl entDoc="NDDTD"/><peRef n="TEI.names.dates.dtd"/></msection><msection keywords="%TEI.nets"><entDecl entDoc="GDDTD"/><peRef n="TEI.nets.dtd"/></msection><msection keywords="%TEI.figures"><entDecl entDoc="FTDTD"/><peRef n="TEI.figures.dtd"/></msection><msection keywords="%TEI.corpus"><entDecl entDoc="CCDTD"/><peRef n="TEI.corpus.dtd"/></msection></dtdFrag>
 <!-- <msection keywords='%TEI.formulas'>                      --><!-- <entDecl entDoc=FTDTD>                                   --><!-- <peRef n='TEI.formulas.dtd'>                             --><!-- </msection>                                              --></p></div3></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2stov.odd ??><!-- 6 The TEI2.DTD File      --><?tei:SOF p2stec.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $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" name="bar" ref="Y"><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><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><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 tei="yes" type="file">teiclas2.ent</ident>.
All element classes are documented in the alphabetical reference section
in Part VII.
 </p><div3 id="STECAT" name="burp" ref="Y"><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 tei="yes" type="class">names</ident> are all elements which contain proper
nouns: e.g.  <gi tei="yes">name</gi>, <gi tei="yes">placeName</gi>, or <gi tei="yes">persName</gi>.
All of these elements use the same attributes (<att tei="yes">key</att> and
<att tei="yes">reg</att>) to record information about the referent or the
regularized form of the proper nouns.  Similarly, the members of the
<ident tei="yes" type="class">pointer</ident> class share a set of attributes
useful for managing cross-reference links and other pointers.<note source="auth" place="foot" anchored="Y">Because the details of their pointing mechanism differ, the
members of the <ident tei="yes" type="class">pointer</ident> class do not,
however, share their pointing attributes.</note>
 </p><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><p>For example, the declaration for the <ident tei="yes" type="class">names</ident>
class includes attribute definitions for its two attributes
<att tei="yes">reg</att> and <att tei="yes">key</att>:
 
<dtdFrag id="DSTECX1" n="Sample class declaration" file="dummy"><claDecl classDoc="NAMES" type="atts"/></dtdFrag>
 
Members of the class typically inherit these definitions by referring to
<ident tei="yes" type="class">a.names</ident>:
 
<dtdFrag id="DSTECX2" n="Sample element declarations" file="dummy"><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><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 tei="yes" type="class">xPointer</ident> is a subclass of the class <ident tei="yes" type="class">pointer</ident>, as shown implicitly by the declaration of
its a-dot entity:
 
<dtdFrag id="DSTECX3" n="Sample subclass declaration, with inheritance from superclass" file="dummy"><claDecl classDoc="XPOINTER" type="atts"/></dtdFrag>
 
(For an explanation of the parameter entity <ident tei="yes" type="pe">extptr</ident> used in the above example, see section <xref target="STPEKW"/>.)
 </p><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 tei="yes" type="class">declaring</ident> </label><item>elements which have a
<att tei="yes">decls</att> attribute for specifying which declarations in the
header apply to the element, as described in section <xref target="CCAS"/>
 </item><label><ident tei="yes" type="class">declarable</ident> </label><item>header elements
containing declarations, which can be pointed at by the <att tei="yes">decls</att>
attribute, as described in section <xref target="CCAS"/>
 </item><label><ident tei="yes" type="class">divn</ident> </label><item>structural elements which
behave in the same way as divisions, as described in section <xref target="DSDIV"/>
 </item><label><ident tei="yes" type="class">enjamb</ident> </label><item>elements which carry the
<att tei="yes">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 >                          -->
 </item><label><ident tei="yes" type="class">interpret</ident> </label><item>elements which contain
overtly interpretive or extra-textual analysis or commentary on a text
or some portion of it.
 </item><label><ident tei="yes" type="class">metrical</ident> </label><item>elements which carry
metrical information (metrical pattern, realization of the pattern,
rhyme)
 </item><label><ident tei="yes" type="class">names</ident> </label><item>elements which contain
proper nouns and share attributes for identifying their referents and
regularizing their spelling (section <xref target="CONARS"/>)
 </item><label><ident tei="yes" type="class">personPart</ident> </label><item>elements which contain
personal names or parts of them
 </item><label><ident tei="yes" type="class">placePart</ident> </label><item>elements which contain
place names or parts of them
 </item><label><ident tei="yes" type="class">pointer</ident> </label><item>elements which point from
one location in the document to another (section <xref target="COXR"/>)
 </item><label><ident tei="yes" type="class">seg</ident> </label><item>elements for the systematic
or arbitrary segmentation of the text
 </item><label><ident tei="yes" type="class">temporalExpr</ident> </label><item>elements which
contain temporal expressions
 </item><label><ident tei="yes" type="class">timed</ident> </label><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"/>
</item><label><ident tei="yes" type="class">typed</ident> </label><item>elements which carry
an additional semantic or functional classification
 </item><label><ident tei="yes" type="class">xPointer</ident> </label><item>elements which point
from one location in the document to other locations within or outside
the current document (section <xref target="SAXR"/>)
 </item></list>
 </p><p>All elements are considered members of the class <ident tei="yes" type="class">global</ident> and thus include a reference to <ident tei="yes" 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 tei="yes" type="pe">a.analysis</ident> </label><item>additional global
attributes for the analysis tag set
 </item><label><ident tei="yes" type="pe">a.linking</ident> </label><item>additional global
attributes for the linking tag set
 </item><label><ident tei="yes" type="pe">a.terminology</ident> </label><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                                                  -->
 </item></list>
 </p><p>These entities are included in the <ident tei="yes" 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 tei="yes" type="class">global</ident> from superclasses called
<ident tei="yes" type="class">terminology</ident>, etc.,
and are documented under the class name.<!-- suppress class 'spoken' (vacuous)                        -->
 </p><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 tei="yes">anchor</gi> inherits the global <att tei="yes">id</att> attribute from the
class <ident tei="yes" type="class">global</ident> --- as does every other element.
On <gi tei="yes">anchor</gi> elements, however, <att tei="yes">id</att> is not optional but
required.  The declaration of <gi tei="yes">anchor</gi> therefore does not refer
to the class <ident tei="yes" type="class">global</ident>, but instead defines all
the inherited attributes explicitly, using its own declaration for
<att tei="yes">id</att> and the default inherited declarations for the other
global attributes:
 
<dtdFrag id="DSTECX4" n="Sample of local declaration overriding inherited attributes" file="dummy"><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 tei="yes" 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 tei="yes">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 classDoc="DECLING" type="atts"/><claDecl classDoc="DECLABL" type="atts"/><claDecl classDoc="DIVN" type="atts"/><claDecl classDoc="ENJAMB" type="atts"/><claDecl classDoc="CLINTERP" type="atts"/><claDecl classDoc="METRICAL" type="atts"/><claDecl classDoc="NAMES" type="atts"/><claDecl classDoc="PERSPART" type="atts"/><claDecl classDoc="PLACPART" type="atts"/><claDecl classDoc="POINTER" type="atts"/><claDecl classDoc="CLSEG" type="atts"/><claDecl classDoc="TEMPEXP" type="atts"/><claDecl classDoc="TIMED" type="atts"/><claDecl classDoc="TYPED" type="atts"/><claDecl classDoc="XPOINTER" type="atts"/></dtdFrag><!-- claDecl type=atts classDoc=FLATTERM --><!-- <claDecl type=atts classDoc=PNAME>                       --><!-- <claDecl type=atts classDoc=PLNAME>                      --><!-- <claDecl type=atts classDoc=READINGS>                    -->
 </p></div3><div3 id="STECCM" name="burp" ref="Y"><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><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><p>For example, the class <ident tei="yes" type="class">bibl</ident> has the three
members <gi tei="yes">bibl</gi>, <gi tei="yes">bibl.full</gi>, and <gi tei="yes">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 tei="yes" type="pe">m.bibl</ident> with the replacement text <code tei="yes" 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 tei="yes" 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 tei="yes" type="pe">m.bibl</ident> from
its default value to <code tei="yes" 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 tei="yes" 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><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><p>For example, the class <ident tei="yes" type="class">phrase</ident> includes the
classes <ident tei="yes" type="class">data</ident>, <ident tei="yes" type="class">edit</ident>,
<ident tei="yes" type="class">hqphrase</ident>, <ident tei="yes" type="class">loc</ident>, and
<ident tei="yes" type="class">seg</ident> as members, as can be seen in the
declaration for its m-dot entity:
 
<dtdFrag id="DSTECX5" n="Sample class declaration with inclusion of subclasses" file="dummy"><claDecl classDoc="PHRASE" type="model"/></dtdFrag>
 
When the entity <ident tei="yes" type="pe">m.phrase</ident> is referred to in
content models, all members of all subclasses are included in the model.
 </p></div3><div3 id="STECOV" name="burp" ref="Y"><head>The TEICLAS2.ENT File</head><p>The most important element classes used in TEI content models are
declared in the DTD file <ident tei="yes" type="file">teiclas2.ent</ident>, which
is the default replacement text for the entity <ident tei="yes" type="pe">TEI.elementClasses</ident> and is embedded by the <ident tei="yes" type="file">tei2.dtd</ident> file.  These element classes are described,
and their declarations reproduced, in the following sections.
 </p><p>The class system is structured around the following threefold
division of elements:
 
<list type="gloss"><label><term>chunks</term> </label><item>elements such as paragraphs and other
paragraph-level elements, which can appear directly within texts or
within text subdivisions (i.e. <gi tei="yes">div</gi> elements), but not within
other chunks</item><label><term>phrase-level elements</term> </label><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 tei="yes">div</gi>)
<note source="auth" place="foot" anchored="Y">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></item><label><term>inter-level elements</term> </label><item>elements such as lists,
notes, quotations, etc. which can appear either between chunks (as
children of a <gi tei="yes">div</gi>) or within them</item></list>
 </p><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> </label><item>elements which can appear
directly within texts or text divisions; also called simply
<term>components</term> or <soCalled>component-level elements</soCalled></item></list>
In general, the body of any text comprises a series of components,
optionally grouped into <gi tei="yes">div</gi> elements.
 </p><p>Some elements belong to none of these classes; these include
high-level structural elements like <gi tei="yes">tei.2</gi> and
<gi tei="yes">group</gi> as well as some specialized elements which appear only
within particular structures (like <gi tei="yes">analytic</gi>,
<gi tei="yes">monographic</gi>, and <gi tei="yes">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><p>Some <term>component</term> elements (e.g. <gi tei="yes">p</gi> or
<gi tei="yes">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><p>The <ident tei="yes" type="file">teiclas2.ent</ident> file has the following
overall structure:
 
<dtdFrag id="DSTECOV" n="Element classes for TEI DTDs" file="teiclas2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><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>
 </p></div3><div3 id="STECLO" name="burp" ref="Y"><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><p>The following are phrase-level element classes:
 
<list type="gloss"><label><ident tei="yes" type="class">hqphrase</ident> </label><item>elements for highlighted
phrases or material marked by quotation marks, including those defined
in section <xref target="COHQ"/>
 </item><label><ident tei="yes" type="class">data</ident> </label><item>elements for recording
information about the referents of a text, including those defined in
section <xref target="CONA"/>
 </item><label><ident tei="yes" type="class">date</ident> </label><item>elements for recording
dates, including those defined in
section <xref target="CONADA"/>
 </item><label><ident tei="yes" type="class">edit</ident> </label><item>elements for recording
simple editorial interventions in a text, including those defined in
section <xref target="COED"/>
 </item><label><ident tei="yes" type="class">loc</ident> </label><item>elements for recording
location information in a text, including those defined in section <xref target="CORS"/>
 </item><label><ident tei="yes" type="class">seg</ident></label><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"/>
 </item><label><ident tei="yes" type="class">sgmlKeywords</ident></label><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"/>)
 </item><label><ident tei="yes" type="class">versePhrases</ident></label><item>phrase-level elements
specific to verse, documented in section <xref target="VESE"/>
 </item><label><ident tei="yes" type="class">formPointers</ident></label><item>elements for
referring, within a dictionary entry, to the orthographic form or
pronunciation of the headword, documented in section <xref target="DIHW"/>
 </item></list>
 </p><p>The following are inter-level element classes:
 
<list type="gloss"><label><ident tei="yes" type="class">hqinter</ident> </label><item>elements for highlighted
phrases or material marked by quotation marks, including those defined
in section <xref target="COHQ"/>
 </item><label><ident tei="yes" type="class">bibl</ident> </label><item>elements for bibliographic
citations; see section <xref target="COBI"/>
 </item><label><ident tei="yes" type="class">lists</ident> </label><item>elements for lists; see
section <xref target="COLI"/>
 </item><label><ident tei="yes" type="class">notes</ident> </label><item>general-purpose annotation
elements; see section <xref target="CONO"/>
 </item><label><ident tei="yes" type="class">stageDirection</ident></label><item>elements for
specialized stage-direction elements documented in section <xref target="DRSTA"/>
 </item></list>
 </p><p>The following classes of elements may appear anywhere within the
<gi tei="yes">text</gi> element:
 
<list type="gloss"><label>metadata</label><item>elements which convey non-textual
information about the text (meta-information, as it were)</item><label>refsys</label><item>milestone elements used in
reference systems</item><label>editincl</label><item>elements marking arbitrary  spans
of text which has been added, deleted, or omitted from a transcription</item></list>

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

 </p><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>
 </p></div3><div3 id="STECHI" name="burp" ref="Y"><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><p>The element class <ident tei="yes" 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><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>
 </p></div3><div3 id="STECMK" name="burp" ref="Y"><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 tei="yes" type="class">comp.verse</ident> </label><item>elements unique to
verse
 </item><label><ident tei="yes" type="class">comp.drama</ident> </label><item>elements unique to
drama
 </item><label><ident tei="yes" type="class">comp.spoken</ident> </label><item>elements unique to
spoken texts
 <!-- <label><ident type=class>comp.letters</ident>            --><!-- <item>elements unique to letters and memoranda           -->
 </item><label><ident tei="yes" type="class">comp.dictionaries</ident> </label><item>elements unique
to dictionaries
 </item><label><ident tei="yes" type="class">comp.terminology</ident> </label><item>elements unique
to terminological data
 </item></list>
 </p><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 tei="yes" 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>                                              -->
 </p></div3><div3 id="STECST" name="burp" ref="Y"><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 tei="yes" type="pe">phrase</ident> </label><item>a single sequence of
character data or single phrase-level element
 </item><label><ident tei="yes" type="pe">phrase.seq</ident> </label><item>sequence of character
data and phrase-level elements
 </item><label><ident tei="yes" type="pe">component</ident> </label><item>a single chunk- or
inter-level element
 </item><label><ident tei="yes" type="pe">component.seq</ident> </label><item>sequence of chunk- and
inter-level elements; this is the usual content of a <gi tei="yes">div</gi>
element
 </item><label><ident tei="yes" type="pe">paraContent</ident> </label><item>sequence of character
data, phrase-level elements, and inter-level elements; this is the usual
content of chunks (including, most prominently, paragraphs)
 </item><label><ident tei="yes" type="pe">specialPara</ident> </label><item>specialized content
model, allowing <emph>either</emph> a sequence of chunks <emph>or</emph>
the same content as <ident tei="yes" 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.
 </item></list>
 </p><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>                                              -->
 
 </p></div3><div3 id="STECMX" name="burp" ref="Y"><head>Components in Mixed and General Bases</head><p>When the mixed or general base is in use, the definitions of the
entities <ident tei="yes" type="pe">component</ident> and
<ident tei="yes" 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>                                 -->
 </p></div3><div3 id="STECMI" name="burp" ref="Y"><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 tei="yes" type="class">agent</ident> </label><item>elements which denote an
individual or organization to whom or which responsibility for an action
can be assigned
 </item><label><ident tei="yes" type="class">addrPart</ident> </label><item>elements which can occur
as part of an address
 </item><label><ident tei="yes" type="class">biblPart</ident> </label><item>elements which can occur
in bibliographic citations
 </item><label><ident tei="yes" type="class">demographic</ident> </label><item>elements which record
demographic characteristics of the participants in a text or language
interaction (used in tag set for corpora and collections)
 </item><label><ident tei="yes" type="class">divbot</ident> </label><item>elements which can occur
as part of the closing material of a text division or body
 </item><label><ident tei="yes" type="class">divtop</ident> </label><item>elements which can occur
as part of the opening material of a text division or body
 </item><label><ident tei="yes" type="class">dramafront</ident> </label><item>elements which can
occur in the front matter of drama and other performance texts
 </item><label><ident tei="yes" type="class">front</ident> </label><item>elements which can occur
(at the level of text divisions) in front matter only
 </item><label><ident tei="yes" type="class">personPart</ident> </label><item>elements which contain
parts of a personal name
 </item><label><ident tei="yes" type="class">placePart</ident> </label><item>elements which contain
parts of a place name
 </item><label><ident tei="yes" type="class">tpParts</ident> </label><item>elements which occur
within title pages
</item><label><ident tei="yes" type="class">fmchunk</ident> </label><item>elements which can
occur in place of a title page in front matter only

 </item></list>
 </p><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 ??><!-- 7 Elem Classes           --><?tei:SOF p2stpe.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2stpe.odd,v $
# Revision 1.4  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.3  1994/04/01  16:36:47  msmcq
# changes / fixes during validation of DTD
# --><!-- P2STpe :  Parameter Entities in TEI DTDs                 --><!-- Revisions:                                               --><!-- 94-04-08 : MSM : suppress reference to GFtop             --><!-- 94-04-08 : MSM : (it was renamed FTtop some time ago)    --><!-- 94-03-31 : MSM : add mention of TEI.singlebase           --><!-- 94-03-30 : MSM : suppress ref to lmtop                   --><!-- 94-03-30 : MSM : Added RCS id                            --><!-- 93-09-14 : MSM : move keyword defs to sep file           --><!-- 93-09-11 : MSM : rename teigis.ent as teigis2.ent        --><!-- 93-04-07 : MSM : cosmetic changes                        --><!--                  supply more info on ISO 8601            --><!--                  tag entities as terms (temporarily)     --><!-- 3 apr 93 : LB revise for publication                     --><!--   removed typo; added bib ref for ISO-date (ta, Domo)    --><!-- 93-03-30 : MSM : revise for LB                           --><!-- 93-03-16 : MSM : move technoid warning to STov.          --><!-- 93-03-06 : MSM : quick check before distribution to tei-tech --><!-- 93-03-01 : MSM : extract p2STpe from p2STec              --><!-- 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                         -->
 </p></div3></div2><div2 id="STPE" name="bar" ref="Y"><head>Other Parameter Entities in TEI DTDs</head><!-- point:  you need to know what the pe's are to read the DTDs. --><!-- uses of p.e.'s in TEI DTDs:                              --><!--         - identify base, toppings                        --><!--         - specify groups of attributes common to several --><!--           elements                                       --><!--         - specify groups of elements which appear in     --><!--           content models                                 --><!--         - include or exclude each element                --><!--         - specify name for each element                  --><!-- notion of element class:  common locations or atts       --><!-- Major p.e.'s of the TEI DTDs:                            --><!--         soup                                             --><!--         broth                                            --><!--         chunks                                           --><!--         p.e.s for bases and toppings                     --><p>The TEI DTDs use SGML parameter entities for several purposes:
 
<list type="bullets"><item>to define sets of attributes shared by given classes of elements</item><item>to define classes of elements which can occur at the same
locations in content models</item><item>to identify what base tag set should be used for a document</item><item>to identify what additional tag sets should be included</item><item>to include or exclude the declaration of each element</item><item>to specify the name of each element</item></list>
 
The first two applications of parameter entities are described above in
section <xref target="STEC"/>.  This chapter describes the other uses of
parameter entities in the TEI DTDs.
 </p><p>The parameter entities used to specify which base tag
set and which additional tag sets are to be used in a given document
are listed in section <xref target="STBA"/>.  Their default definition is
always <q>IGNORE</q>:  the encoder selects the TEI base and additional
tag sets by declaring the appropriate parameter entities with the
entity text <q>INCLUDE</q>.
 </p><p>The DTD and entity files are listed in section <xref target="STBA"/>; if
the standard TEI entities are modified to point at locally developed DTD
files containing local modifications or extensions to the TEI DTDs, the
use of the standard parameter entity names ensures that the modification
will be obvious upon examination of the document's DTD.
 </p><p>The following entities are referred to by the main
<ident tei="yes" type="file">tei2.dtd</ident> file to embed portions of the TEI DTDs
or locally developed extensions.
 
<list type="gloss"><label><ident tei="yes" type="pe">TEI.extensions.ent</ident></label><item>identifies a local file containing
extensions to the TEI parameter entities; see section<xref target="STOVLO"/></item><label><ident tei="yes" type="pe">TEI.extensions.dtd</ident></label><item>identifies a local file containing
extensions to the TEI tag set; see section <xref target="STOVLO"/></item><label><ident tei="yes" type="pe">TEI.elementNames</ident></label><item>identifies a file containing parameter
entity declarations for names of TEI elements; see section<xref target="STPEGI"/></item><label><ident tei="yes" type="pe">TEI.keywords</ident></label><item>identifies a file containing parameter
entity declarations for TEI keywords, including the default
declaration (<q>IGNORE</q>) of the marked-section keyword for
each tag set; see section<xref target="STPEKW"/></item><label><ident tei="yes" type="pe">TEI.elementClasses</ident> </label><item>identifies a file
containing definitions of parameter entities used in content models; see
section <xref target="STECOV"/></item><label><ident tei="yes" type="pe">TEI.singleBase</ident> </label><item>defined as
<code tei="yes" type="frag">INCLUDE</code>
(for normal bases) or <code tei="yes" type="frag">IGNORE</code> (for mixed and general base);
used to prevent multiple definitions of the default text structure.</item></list>
 </p><div3 id="STPEEX" name="burp" ref="Y"><head>Inclusion and Exclusion of Elements</head><p>The TEI DTDs use marked sections and parameter entity references to
allow users to exclude the definitions of individual elements, in order
either to make the elements illegal in a document or to allow the
element to be redefined, as further described in chapter<xref target="MD"/>
.
 </p><p>Parameter entities used for this purpose have exactly the same name
as the generic identifier of the element concerned.  The default
definition for these parameter entities is <q>INCLUDE</q> but they may
be changed to <q>IGNORE</q> in order to exclude the standard element and
attribute definition list declarations from the DTD.
 </p><p>The declarations for the element <gi tei="yes">p</gi>, for example, are
preceded by a definition for a parameter entity with the name
<ident rend="noindex" tei="yes" type="ge">p</ident> and contained within a marked
section whose keyword is
given as <q>%p;</q>:
 
<eg> &lt;!ENTITY % p 'INCLUDE' &gt;
 &lt;![ %p; [
        &lt;!-- element and attlist declaration for p here --&gt;
 ]]&gt;</eg>
 </p><p>These parameter entities are defined immediately preceding the
element whose declarations they control; because their names are
completely regular, they are not documented individually in the
reference section of this document.
 </p></div3><div3 id="STPEGI" name="burp" ref="Y"><head>Parameter Entities for Element Generic Identifiers</head><p>In the TEI DTDs, elements are not referred to directly by their
generic identifiers; instead, the DTDs refer to parameter entities which
expand to the standard generic identifiers.
This allows users to rename elements by redefining the appropriate
parameter entity (as described more fully in chapter <xref target="MD"/>).
Parameter entities used for this purpose are formed
by taking the standard name (generic identifier) of the element and
attaching the string <q>n.</q> as a prefix.  Thus the standard generic
identifiers for paragraphs, notes, and quotations, <gi tei="yes">p</gi>,
<gi tei="yes">note</gi>, and <gi tei="yes">q</gi> are defined by declarations of the
following form:
 
<eg><![CDATA[ <!ENTITY % n.p    'p' >
 <!ENTITY % n.note 'note' >
 <!ENTITY % n.q    'q' >]]></eg>
 </p><p>Since by default parameter entities are case-sensitive, the specific
mix of upper and lower case letters in the standard name must be
preserved in the entity name.
 </p><p>The formal declarations of the parameter entities used for generic
identifiers are contained in the
file <ident tei="yes" type="file">teigis2.ent</ident>; since
their names and replacement texts are fully predictable, these parameter
entities are not individually documented in the reference section of
these Guidelines.
The parameter entity <ident tei="yes" type="pe">TEI.elementNames</ident> is
used to embed the file <ident tei="yes" type="file">teigis2.ent</ident> in the DTD.
A full set
of alternate generic identifiers can be substituted for the standard set
by defining <ident tei="yes" type="pe">TEI.elementNames</ident> to point at a
different
file.<note source="auth" place="foot" anchored="Y">It is expected that after completion of the full
text of these Guidelines, the TEI will prepare alternate sets of generic
identifiers in languages other than English.  It should be noted,
however, that in the interests of simplicity parameter entities are
used only for generic identifiers; attribute names, standard attribute
values, and parameter entity names are less easily modified.</note>
 </p></div3><div3 id="STPEKW" name="burp" ref="Y"><head>Parameter Entities for TEI Keywords</head><p>The TEI uses the following parameter entities to signal
information which cannot be expressed using SGML keywords:
 
<list type="gloss"><label>INHERITED </label><item>indicates that an attribute value is inherited
from the enclosing element, if not specified</item><label>ISO-date </label><item>indicates that an attribute value should be a
legal ISO date in the form yyyy-mm-dd (e.g. 1993-06-28).</item><label>extptr </label><item>indicates that an attribute value should be a legal
expression in the TEI extended-pointer notation</item></list>
 
In addition, the parameter entities which control the selection of
base and additional tag sets may be regarded as a keyword.
 <!-- no % for consistency with other p.e. names --></p><p>The parameter entity <ident tei="yes" type="pe">INHERITED</ident> is used
to signal that the default value for an attribute should be inherited
from an enclosing element.
The definition for <ident tei="yes" type="pe">INHERITED</ident> is
the string <q>#IMPLIED</q>; as for all implied defaults, the application
program is responsible for deducing the default attribute value when no
value is specified in the element start-tag.  Since the parameter entity
is resolved by the SGML parser, the application program will see no
difference between attributes whose default is <q>%INHERITED</q> and
those whose default is <q>#IMPLIED</q> --- information about which
attribute values are inherited and which are inferred in some other way
must be built into the application in advance.
 </p><p>The parameter entity <ident tei="yes" type="pe">ISO-date</ident> is used to
signal that
the value for an attribute should be an ISO-standard date value; in
this notation,<note source="auth" place="display" anchored="Y">Defined by ISO 8601: 1988,<!-- < title > Codes for the representation of dates          --><!-- and times < /title >                                     -->
<title>Data elements and interchange formats --- Information
interchange ---  Representation of dates and times</title>
([Geneva]:  International Organization for Standardization, 1988).</note>
a date like <q>September 22, 1968</q> would be written
<q>1968-09-22</q>.  The parameter entity <ident tei="yes" type="pe">ISO-date</ident>
expands to <q>CDATA</q>.
 </p><p>The keywords controlling the selection of base and additional tag
sets (described in section <xref target="STBA"/>) all have the default
value <q>IGNORE</q>; the user can override this by a local declaration,
as described in section <xref target="STIN"/>.
 </p><p>The parameter entities for TEI keywords are included in file
<ident tei="yes" type="file">teikey2.dtd</ident>, which is the default replacement
text for the entity <ident tei="yes" type="pe">TEI.keywords</ident> and is embedded
by the file <ident tei="yes" type="file">tei2.dtd</ident>.
 </p><p>The file <ident tei="yes" type="file">teikey2.dtd</ident> has the following
contents:
 
<dtdFrag id="DSTKEYS" n="TEI Keywords" file="teikey2.ent"><commDecl>I.  Declare TEI keywords for data types.</commDecl><commDecl>These parameter entities are used as keywords to express
rules or constraints which cannot be fully expressed in SGML; their
expansions show the nearest SGML equivalent.</commDecl><entDecl entDoc="INHERIT"/><entDecl entDoc="ISODATE"/><entDecl entDoc="EXTPTR"/><commDecl>II.  Declare keywords for tag-set selection.</commDecl><commDecl>Declare all bases and additional tag sets as 'IGNORE'.  The
user can override this default by declaring the same entity with the
replacement text 'INCLUDE', in the document's DTD subset.</commDecl><commDecl>Base tag sets first.</commDecl><entDecl entDoc="PRTOP"/><entDecl entDoc="VETOP"/><entDecl entDoc="DRTOP"/><entDecl entDoc="TSTOP"/><entDecl entDoc="DITOP"/><entDecl entDoc="TETOP"/><commDecl>Now the mixed bases.</commDecl><entDecl entDoc="CBGETOP"/><entDecl entDoc="CBMXTOP"/><commDecl>Now additional tag sets.</commDecl><entDecl entDoc="SATOP"/><entDecl entDoc="AITOP"/><entDecl entDoc="FSTOP"/><entDecl entDoc="CETOP"/><entDecl entDoc="PHTOP"/><entDecl entDoc="TCTOP"/><entDecl entDoc="NDTOP"/><entDecl entDoc="GDTOP"/><entDecl entDoc="FTTOP"/><entDecl entDoc="CCTOP"/></dtdFrag>
 </p><p>The relevant portion of the main DTD looks like this:
<dtdFrag id="DSTPEKW" n="TEI Keywords"><commDecl>We declare and immediately embed the TEI keywords file.</commDecl><entDecl entDoc="TEIKW"/><peRef n="TEI.keywords.ent"/></dtdFrag><!-- <entDecl entDoc='LMTOP'>                                 --><?tei:EOF p2stpe.odd ??><!-- 8 Other Parameter Ents   --></p></div3></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2st.odd ??><!-- 3 Structure of TEI DTDs   --></div0><div0 n="2" name="Part" ref="Y"><head>Core Tags and General Rules</head><?tei:SOF p2ch.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2ch.odd,v $
# Revision 1.4  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *--><!-- apologies: I have been unable to track down correct      --><!-- bibliographic references for Unicode, ISO 10646 or       --><!-- for the AFII.        (LB)                                --><!-- P2 chapter 4:  Characters and Character Sets             --><!-- (id=CH, file=P2ch, LB)                                   --><!-- Revisions:                                               --><!-- 17 jan 98: LB : fix egs --><!-- 3 mar : typos from DTB --><!-- 93-05-31 : MSM : changes after Eynsham                   --><!-- 93-02-15 : MSM : suppress P at start of ITEM, NOTE       --><!-- 13 Jan 93:  WP     : changed P2.21 IDs to CH             --><!-- 17 Jul 92 : CMSMcQ : some changes from HG, but *not*:    --><!--          change title to Chars, Char Sets, and Entities  --><!--          mention double quotes (Mac users will insist    --><!--               double quotes are standard)                --><!--          'SGML entities' not changed to 'SGML or TEI     --><!--               public entities':  not all ents public     --><!--          21.2 does not xref to the discussion of LANG.   --><!--               This *is* the discussion of LANG.          --><!--          21.4 does not go into details of declaring ents --><!--               in WSDs, or not declaring them ...         --><!-- 15 Jul 92 : CMSMcQ : final revision for publication      --><!--  7 Jul 92 : LB : minor revisions in light of ST's comments  --><!-- 17 May 92 : CMSMcQ : add para about iso 2022 controls.   --><!--  6 May 92 : CMSMcQ, HG : revise                          --><!--  5 May 92 : CMSMcQ : draft for work with Harry Gaylord   --><div1 id="CH" n="4" name="Chapter" ref="Y"><head>Characters and Character Sets</head><p>Computer systems vary greatly in the sets of characters they make
available for use in electronic documents; this variety enables users
with widely different needs to find computer systems suitable to their
work, but it also complicates the interchange of documents among
systems; hence the need for a chapter on this topic in these Guidelines.
 </p><p>Four character-set problems arise for the encoder of electronic
texts:<!-- reordered as suggested by Syun -->
<list type="ordered"><item>selecting a character set to use in creating, processing, or
storing the electronic text</item><item>preparing documents for interchange so that the characters
within them are not corrupted in transit</item><item>encoding characters which are not provided by the character
set available on the computer system in use</item><item>signaling shifts from one character set to another, e.g. from
the Latin alphabet to Greek and back, or to a special symbol character
set and back</item></list>
 
This chapter describes the recommended solutions to these problems, in
enough detail to satisfy the needs of most users.  More detail and more
technical information can be found in chapters<xref target="CF" type="div1"/>
,<xref target="IN" type="div1"/>
,<xref target="WD" type="div1"/>
, and<xref target="XW" type="div1"/>
.
 </p><div2 id="CHLO" name="bar" ref="Y"><head>Local Character Sets</head><p>No single character set is prescribed for use in TEI-encoded
documents.  Users may use any character set available to them, subject
to the character set restrictions imposed by the SGML declaration.  It
is recommended that the character set used be documented by one or more
<term>writing system declarations</term> (WSD), on which see below.  In
most cases, a predefined writing system declaration should be suitable.
For writing system declarations provided as part of the TEI Guidelines,
see chapter <xref target="XW" type="div1"/>.
 </p><p>In general, it is most convenient to use a character set readily
available on one's computer system, though for special purposes it may
be preferable to customize the character set using software specialized
for the purpose.  Whether to use the usual character set or create a
custom set depends on the documents being encoded, the staff support and
tools available for customizing the character set, the user's technical
facility, etc.  A choice must be made between the perceived relative
convenience of living with an existing character set and the effort of
modifying it to suit one's documents more closely.  Care should be
taken, in particular where multi-byte character sets are used, that the
syntactic distinctions required by an SGML processor are preserved.
Where a suitable character set is defined by a national or international
standard, local customization should implement the standard rather
than inventing yet another non-standard character set.  The
choice must be made by each individual according to individual
circumstances; no general recommendations are made here as to whether
locally customized character sets should be used.  In principle, however,
for local processing, encoders should use whatever character set they
find convenient.
 </p><div3 id="CHLOA" name="burp" ref="Y"><head>Characters Available Locally</head><p>When the characters in a text exist in the local character set, the
appropriate character codes should be used to represent them.  Virtually
all computer systems provide at least the 52 letters of the standard
Latin alphabet, the ten decimal digits, and some basic punctuation
marks.
 </p><p>Other characters, such as Latin characters with diacritics (e.g.
&auml; or &eacute;) or non-Latin characters (e.g. Greek, Hebrew, Arabic,
Cyrillic) are less universally provided. Oriental scripts pose
particular problems because of the size of their character repertoires.
If the
local character set provides an <cited>&auml;</cited> however, there is
normally no reason not to use it where that character appears in the
text, unless the electronic text is to be moved frequently among
machines, in which case one may wish to restrict the electronic text to
characters known to translate well among machines.  (For more
information on moving characters among machines, see section <xref target="CHIN" type="div2"/> below.)
 </p><p>As noted above, full use of a local character set may require that
the SGML declaration be modified to define all the characters used as
legal SGML characters.  <!-- For further information see chapter <xref type=div1 target=LO>. -->
 </p></div3><div3 id="CHLON" name="burp" ref="Y"><head>Characters Not Available Locally</head><p>Characters not available in the local character set should usually be
encoded using SGML <term>entity references</term>.  In SGML terms, an
<term>entity</term> (described in more detail in section <xref target="SG17"/>) is any named string of characters, from a single
character to an entire system file.  Entities are included in SGML
documents by <term>entity references</term>. Lists of suggested names
for all the characters and printers' symbols used by most modern European
languages have been published by ISO and others. <note source="auth" place="display" anchored="Y">The most
widely used such entity set is to be found in Annex D to ISO 8879; it
is also reproduced or summarized in most SGML textbooks, notably
<citation>Charles F. Goldfarb, <title>The SGML Handbook</title>
(Oxford:  Clarendon Press, 1990)</citation>.  A list of some frequently
used standard entity names may be found in chapter <xref target="XW" type="div1"/>.  Extensive entity sets are being developed by the TEI
and others are being documented in the fascicles of ISO/TR 9573:
<citation><title>Technical Report:  Information processing ---
SGML support facilities --- Techniques for using SGML</title>
([Geneva]:  ISO, 1988 et seq.).</citation></note>
 </p><p>For example, the standard entity name for the character
<cited>&auml;</cited> is <cited>auml</cited>; a reference to the entity
gives the name of the entity, preceded by an ampersand and followed by a
semicolon.
<note source="auth" place="foot" anchored="Y">Strictly speaking the semicolon is not always required; for
        details see any full treatment of SGML.</note>
For example, consider the following German sentence:
<q rend="display">Trotz dieser langen Tradition 
 sekund&auml;ranalytischer
 Ans&auml;tze wird man die Bilanz tats&auml;chlich
 durchgef&uuml;hrter sekund&auml;ranalytischer Arbeiten
 aber in wesentlichen Punkten als unbefriedigend
 empfinden m&uuml;ssen.</q>
Using the standard names for a-umlaut and u-umlaut, one
could transcribe this sentence thus:
<eg><![CDATA[ Trotz dieser langen Tradition sekund&auml;ranalytischer
 Ans&auml;tze wird man die Bilanz tats&auml;chlich
 durchgef&uuml;hrter sekund&auml;ranalytischer Arbeiten
 aber in wesentlichen Punkten als unbefriedigend
 empfinden m&uuml;ssen.]]></eg><!-- Manfred Thaller, Vor&uuml;berlegungen ..., in           --><!-- Datenbanken und Datenverwaltungssysteme als Werkzeuge   --><!-- historischer Forschung, p. 9.                           -->
 </p><p>As noted above, standard entity names have been defined for most
characters used by languages written in the Latin alphabet, and for some
other scripts, including Greek, Cyrillic, Coptic, and the International
Phonetic Alphabet.  A useful subset of these may be found in chapter<xref target="XW" type="div1"/>
.
 </p><p>Before an entity can be referred to, it must be declared.  Standard
public entity names can be declared en masse, by including within the
DTD subset of the SGML document a reference to the standard public
entity which declares them.  The German document quoted above, for
example, would have the following lines, or their equivalent, in its
DTD subset:
<eg><![CDATA[ <!ENTITY % ISOLat1 
        PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN">
 %ISOLat1;]]></eg>
 </p><p>Where no standard entity name exists, or where the standard name is
felt unsuitable for some reason, the encoder may declare non-standard
entities, using the normal SGML syntax.<!-- LB added following to try to clarify example a bit -->
The replacement string for such entities may vary for different
purposes, as in the following extended example.
 </p><p>In transcribing a manuscript, it might be desirable to distinguish
among three distinct forms of the letter <cited>r</cited>. In the
transcript, each of these forms will be encoded by an entity
reference, for example: <code lang="sgml" tei="yes" type="frag">&amp;amp;, &amp;amp;r2;</code>, and
<code lang="sgml" tei="yes" type="frag">&amp;amp;r3;</code>.  Entity declarations must then be
provided, within the DTD subset of the SGML document, to define these
entities and specify a substitute string.
</p><p>One possible set of declarations would be as follows:
 
<eg><![CDATA[ <!ENTITY r  'r[1]'><!-- most common form of 'r'  -->
 <!ENTITY r2 'r[2]'><!-- secondary form of 'r'    -->
 <!ENTITY r3 'r[3]'><!-- third form of 'r'        -->]]></eg>
 
The expansions shown above will simply flag each occurrence with a
number in brackets to indicate which form of <cited>r</cited> appears in
the manuscript.
 </p><p>Another (imaginary) set of declarations might use some
printer-specific codes to produce visually distinct versions of the
three letters in output:
 
<eg><![CDATA[ <!ENTITY so '&#27;I&#12;'><!-- shift to alternate printer font -->
 <!ENTITY si '&#27;I&#8;'> <!-- shift to basic printer font -->
 <!ENTITY r  'r'>             <!-- most common form of 'r'  -->
 <!ENTITY r2 '&so;r&si;'>     <!-- secondary form of 'r'    -->
 <!ENTITY r3 '&so;&#113;&si;'><!-- third form of 'r'        -->]]></eg><!-- for verisimilitude, changed &#0;&#04;r and &#0;&#6;r to  --><!-- specific codes of the IBM ProPrinter (for old time's     --><!-- sake; I used to work with them).  113 is 'q',            --><!-- assumption is that designer has placed variants of R     --><!-- adjacent in downloaded set, for no particular reason.    --><!-- -msm                                                     -->
 
Here the replacement strings for each entity contain <term>character
references</term>, for example <code lang="sgml" tei="yes" type="frag">&amp;amp;#27;</code>,
indicating the decimal value (or <term>code point</term>) of the
character to be generated by the SGML processor.  The assumption is
that the sequence of bytes generated will drive a printer to produce a
distinctive form of the letter.  Such printer instructions are of
their nature highly machine- and software-dependent; by allowing them
to be confined to a single place (the entity declarations), SGML makes
it easier to adapt such device-specific information to new
environments.
 </p><p>Alternatively, the declarations can give all three forms the same
appearance in the output:
 
<eg><![CDATA[ <!ENTITY r  'r'><!-- most common form of 'r'  -->
 <!ENTITY r2 'r'><!-- secondary form of 'r'    -->
 <!ENTITY r3 'r'><!-- third form of 'r'        -->]]></eg>
 </p><p>And finally, to ensure that the SGML output uses the same entity
references for these characters as does the SGML input, one could use
the following declarations.
 <!-- < eg >                                                  --><!-- < ![ CDATA [                                            --><!-- < !ENTITY amp '&' >                                     --><!-- < !ENTITY r  '&amp;r;'  >  < ! - most common form of 'r' - > --><!-- < !ENTITY r2 '&amp;r2;' >  < ! - secondary form of 'r'   - > --><!-- < !ENTITY r3 '&amp;r3;' >  < ! - third form of 'r'       - > --><!-- ]] >                                                     --><!--  < /eg >                                                 -->
 <!-- Example above abandoned in favor of next one.  Not all   --><!-- processors handle the entity end the same one; the       -->
 
<eg><![CDATA[ <!ENTITY r  CDATA '&r;' ><!-- most common form of 'r'  -->
 <!ENTITY r2 CDATA '&r2;'><!-- secondary form of 'r'    -->
 <!ENTITY r3 CDATA '&r3;'><!-- third form of 'r'        -->]]></eg>
 </p><p>Wherever locally defined entities are used for the representation of
characters in the text, whether to record presentational variants as
in this example or to represent special symbols not present in standard
character sets or public entity sets, it is recommended that the
entities be documented in a writing system declaration; for details
see chapter <xref target="WD"/>.
 </p><p>For transcriptions in scripts not supported by the local character
set, entity references may prove unwieldy.  In such cases, it is also
possible to transliterate the material from its original script into
the script of the local character set; like a customized local
character set, a transliteration scheme should be documented with a
writing system declaration.  To avoid information loss, a
<term>reversible</term> transliteration scheme (i.e. one in which it
is possible to reconstruct the original writing from the
transliteration) should be preferred; wherever possible, standard
schemes should be preferred to ad hoc schemes.<!-- deleted following sentence : too vague --><!-- Great care must be exercised, however, in developing --><!-- or selecting transliteration schemes, as many schemes, even standard --><!-- ones, developed for general use are  emph>not /emph> reversible. -->
<note source="auth" place="foot" anchored="Y">Reversible transliteration schemes are defined by
national and international standards too numerous to list here; another
useful source is <citation><title>ALA-LC Romanization Tables:
Transliteration Schemes for Non-Roman Scripts</title>, approved by the
Library of Congress and the American Library Association, tables
compiled and edited by Randall K. Barry (Washington:  Library of
Congress, 1991).</citation>  Many of these schemes, however, use
diacritics which are themselves not always available in standard
electronic character sets and thus may require careful adaptation for
use in electronic work.</note>
 </p><p>For example, using the Beta code transcription developed for ancient
Greek by the Thesaurus Lingu&aelig; Gr&aelig;c&aelig;,<note source="auth" place="foot" anchored="Y"><citation>Thesaurus Lingu&aelig; Gr&aelig;c&aelig;,
<title>Beta Manual</title>
(Irvine:  TLG, [1988]).</citation>
See also
<citation><author>Luci Berkowitz and Karl A.
Squitier,</author>
<title>Thesaurus Lingu&aelig; Gr&aelig;c&aelig; Canon of Greek
Authors and Works</title>
2nd edition (Oxford:  Oxford University Press,
1986).</citation></note>
one would transcribe the start of the <title>Iliad</title> of Homer thus:
 
<eg><![CDATA[ <l>*MH=NIN A)/EIDE QEA\ *PHLHI+A/DEW *)AXILH=OS
 OU)LOME/NHN, H(\ MURI/' *)AXAIOI=S A)/LGE' E)/QHKE,]]></eg><!-- Homer, Iliad, I.1-2, from OCP file demo4.txt. --><!-- stripped line number. -->
 </p><p>Some standard transliteration schemes for commonly encoded languages
are included in chapter <xref target="XW" type="div1"/>.<!-- viz. Beta code and PhonASCII --><!-- would be nice to have example with PhonASCII or some such. -->
 </p></div3></div2><div2 id="CHSH" name="bar" ref="Y"><head>Shifting Among Character Sets</head><p>Many documents contain material from more than one language: loan
words, quotations from foreign languages, etc.  Since languages use a
variety of <term>writing systems</term>, which in turn use a variety
of <term>character repertoires</term>, shifts in language frequently
go hand in hand with shifts in character repertoire and writing
system.  Since language change is frequently of importance in
processing a document, even when no character set shift is needed, the
encoding scheme defined here provides a global attribute
<att tei="yes">lang</att> to make it possible to mark language shifts
explicitly.  This attribute may also be used to trigger character-set
shifting by application programs.
 <!-- it possible to mark language shifts explicitly.  This    --><!-- attribute is also used to trigger character-set          --><!-- shifting by application programs.                        -->
 </p><p>Some languages use more than one writing system.  For example, some
Slavic languages may be written either in the Latin or in the Cyrillic
alphabet; some Turkic languages in Cyrillic, Latin, or Arabic script.
In such cases, each writing system must be treated separately, as a
separate <soCalled>language</soCalled>.  Each distinct value of the
<att tei="yes">lang</att> attribute, therefore, represents a single natural
language, a single writing system, and a single coded character set.
 <!-- < p > It is strongly recommended that each value used    --><!-- for the < att > lang < /att >  attribute correspond to   --><!-- a writing system declaration suitable for the            --><!-- character set and writing system being used.  The        -->
 </p><p>Each value used for the
<att tei="yes">lang</att> attribute must correspond to a writing system declaration
suitable for the character set and writing system being used.  The
values should where possible be taken from the standard two- and
three-letter language codes defined by the international standard ISO
639.<note source="auth" place="foot" anchored="Y"><citation>ISO 639: 1988, <title>Code for the representation of names
of languages</title>  ([Geneva]:  International Organization for
Standardization, 1988).  The most recent version of this standard 
supplies three-letter codes as well as the earlier system of
two-letter codes.  Either may be used in TEI documents.</citation></note><!-- In the rare event that -->
When more than one writing system is used for the same
language in the same document, suffixes should be added to the values
from ISO 639.  A selection of standard language codes, as well as a
number of standard writing system declarations, are provided in chapter<xref target="XW" type="div1"/>
; other writing system declarations may be
provided locally.
 </p><p>Like any global attribute, the <att tei="yes">lang</att> attribute may be used
on any element in the SGML document.  To mark a technical term, for
example, as being in a particular language, one may simply specify the
appropriate language on the <tag compl="full" tei="yes">term</tag> tag (for which see<xref target="TE" type="div2"/>
):
 
<eg><![CDATA[<p lang=EN> ...
But then only will there be good ground of hope for the
further advance of knowledge, when there shall be received
and gathered together into natural history a variety of
experiments, which are of no use in themselves, but simply
serve to discover causes and axioms, which I call
<term lang=LA>Experimenta lucifera</term>, experiments of
<term>light</term>, to distinguish them from those which I
call <term lang=LA>fructifera</term>, experiments of
<term>fruit</term>.
<p>Now experiments of this kind have one admirable
property and condition:  they never miss or fail. ...]]></eg><!-- Bacon, New Organon, XCIX, p. 361 of pocket ed. --><!-- need snappier example. -->
 </p><p>The form in which materials in different writing systems are
processed or displayed is not specified by these Guidelines; if
appropriate characters are not available locally, application software
may choose to display the material in an appropriate transliteration, as
a series of entity references, or in other forms.  If the local system
requires explicit escape sequences or locking-shift control functions to
signal shifts to alternate character sets, these escape sequences may be
embedded directly in the content of the appropriate element or may be
supplied by the application software upon recognition of the language
shift.  However, escape sequences are <!-- extremely -->
vulnerable to loss or
misinterpretation when documents are sent from site to site.  For this
reason, the method of embedding them directly in the document, while
allowed within TEI-conformant interchange, is not recommended for
general use.<note source="auth" place="foot" anchored="Y">    Standard methods for character-set shifting are defined in
    ISO 2022: 1986, <title>Information processing --- ISO 7-bit and
    8-bit coded character sets --- Code extension techniques</title>,
    3d ed. ([Geneva]:  International Organization for Standardization,
    1986).
    A standard set of control functions, including methods of specifying
    script direction (left-right, right-left, top-down, etc.), is
    defined by ISO 6429: 1992, <title>Information processing --- Control
    functions for 7-bit and 8-bit coded character sets</title>,
    ([Geneva]:  ISO, 1992).  These and related standards are recommended
    to the notice of those designing systems to handle multiple
    character sets.</note>
 </p></div2><div2 id="CHIN" name="bar" ref="Y"><head>Character Set Problems in Interchange</head><p>Electronic texts may be exchanged over electronic networks, through
exchange of magnetic media (e.g. disk or tape), or by other means.  In
every case except the transmission of storage media from one machine to
another machine of the same hardware type running the same operating
system and using the same coded character set, the characters are
subject to translation and interpretation, and hence to
misinterpretation and corruption, by utility software working somewhere
on the interchange path.  Network gateways, tape-reading software, and
disk utilities routinely translate from one character set to another
before passing the data on.  If the utility errs in identifying the
character set, or if several utilities translate back and forth among
character sets using non-reversible translations, the chances are good
that characters will be garbled and information lost.
 </p><p>At this time (1994), it is recommended that in texts subject to
<soCalled>blind</soCalled> interchange (that is, interchange between
parties who do not or cannot make explicit agreements over the character
set to be used in interchange) no characters should be used other than
those in the international reference version (IRV) of ISO
646.<note source="auth" place="foot" anchored="Y"><citation>ISO (International Organization for Standardization).
<title>ISO 646:  1991.  Information processing --- ISO 7-bit coded
character set for information interchange.</title>  ([Geneva]:
International Organization for Standardization, 1991.)<!-- need to check date on this new version of 646. (MSM) --></citation></note>
Other characters should be represented by SGML entity references.  For
scripts (such as those of East Asia) which require a character
repertoire larger than 255 characters, regional proposals for character
and entity sets to be used in non-negotiated interchange must be
developed and published internationally.
 </p><p>In some cases, even the characters in ISO 646 IRV are corrupted in
transit; where interchange takes place over links not reliable for the
full IRV character set, the characters subject to misinterpretation and
corruption should be replaced by standard entities.  At present, the
characters least susceptible to loss or misinterpretation in transit
among systems are those shown below, which represent a subset of the
characters in IRV and may thus be called the <term>ISO 646
subset</term>.
 
<eg rend="literal">a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9
" % &amp; ' ( ) * + , - . / : ; &lt; = &gt; ? _</eg>
 </p><p>In interchange over any transmission link, the transmitted document
should contain only those characters which safely survive transmission
over the link; others should be represented with entity references, or
with transliterations, as described above.
 </p><p>In blind interchange by means of magnetic or optical media, it is
recommended that the document be encoded using some well documented and
widely used standard character set.
 </p><p>In blind interchange over networks, it is recommended that the
transmitted document contain only characters known to travel safely over
the networks involved.  In the most general case, those characters are
the ISO 646 subset given above.
 </p><p>The problem of character data loss in document interchange is in
principle a temporary one; eventually, it should disappear as
improvements are made in network handling of character data and as more
networks support larger character sets such as ISO
10646.<note source="auth" place="foot" anchored="Y"><citation>ISO (International Organization for Standardization), and IEC
(International Electrotechnical Commission), <title>ISO/IEC 10646-1:
1993.  Information technology --- Universal Multiple-Octet Coded
Character Set (UCS) --- Part 1:  Architecture and Basic Multilingual
Plane.</title>  ([Geneva]:  International Organization for
Standardization, 1993.)  </citation> The Basic Multilingual Plane of ISO
10646 is identical to the sixteen-bit character set known as Unicode:
<citation>The Unicode Consortium, <title>The Unicode Standard:
Worldwide Character Encoding</title> Version 1.0, Volume 1 (Reading,
Mass.:  Addison-Wesley, 1991).  </citation> Version 1.0 of Unicode has
been superseded by later work incorporated into ISO/IEC 10646; these
changes are be reflected in the official published standard, and will be
documented in version 1.1 of Unicode.</note>
The need for backward compatibility with older systems is likely,
however, to ensure that care must be taken in blind interchange for the
foreseeable future.
 </p><p>For further discussion of negotiated and non-negotiated interchange,
see chapter <xref target="IN"/>.
 </p></div2><div2 id="CHWS" name="bar" ref="Y"><head>The Writing System Declaration</head><p>Each language and writing system used in a document should be
documented in a Writing System Declaration (WSD), which specifies:
<list type="simple"><item>a formal name for the writing system and language, for use as a
<att tei="yes">lang</att> attribute value on elements encoded in it</item><item>a specification for the meaning of each character available
in the writing system</item></list>
The characters available in a writing system may be specified in the
WSD for that writing system in one or more of the following ways:
<list type="simple"><item>by reference to an international, national, or TEI-registered coded
character set or entity set</item><item>by reference to such a standard followed by formal declaration of
all exceptions</item><item>by providing a formal declaration for each character used</item></list>
Individual characters within a WSD are formally declared, where
necessary, by providing the following information:
<list type="simple"><item>the unique code used to represent the character</item><item>special properties such as whether the character is a diacritic
mark or not</item><item>brief textual description of the character</item><item>standard or local entity name used for the character in
interchange</item><item>other standard identifiers for the character, if available, such
as its code in the <soCalled>Universal Character Set</soCalled> of ISO
10646 or Unicode
and its standard number in the Association for Font Information
Interchange registry.<!-- We need a bibliographic reference for AFII. --></item><item>optionally, some specification of a suitable graphic rendition for
the character in a suitable notation (e.g. graphic image, Metafont
program, etc.)</item></list>
 </p><p>The writing system declaration is one of a set of
<term>auxiliary</term> documents which provide documentation relevant to
the processing of TEI texts.  Auxiliary documents are themselves SGML
documents, for which document type declarations are provided.  The DTD
for the Writing System Declaration is discussed in detail in chapter<xref target="WD" type="div1"/>
.  Standard Writing System Declarations are
provided in chapter <xref target="XW" type="div1"/>.
 <?tei:EOF p2ch.odd ??>
            <!-- 4 Character Sets --><?tei:SOF p2hd.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd.odd,v $
# Revision 1.4  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.3  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
#
# Revision 1.2  1993/06/23  01:41:20  msmcq
# add keywords at top
# --><!-- Revisions:                                               --><!-- 4 jan 98 : LB : added explanatoryu sentence about computer file --><!-- 94-03-22 : CMSMcQ : wording changes from DB              --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!-- 93-06-02 : MSM : add ref to SH                           --><!-- 93-06-01 : MSM : post-Eynsham:  normalize teiHeader      --><!-- 93-06-01 : MSM : post-Eynsham:  suppress AH refs         --><!-- 93-02-11 : MSM : change N value on div1                  --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 93-02-10 : MSM : comment out reference to hdtags (refer in p2hddriv) --><!-- 93-02-10 : MSM : put entity refs for subfiles on own lines --><!-- 92-08-18 : MSM : replace separate tag files with hdtags  --><!-- 92-08-18 : MSM : Changes to xrefs                        --><!-- 14 Aug 92 : MSM : more changes                           --><!-- 5 Aug 92: LB : last check: fixed xrefs                   --><!-- 1 Aug 92 : LB : Further revisions; adding xrefs and final para  --><!-- 22 Jul 92 : MSM : Redivide, recast slightly.             -->
</p></div2></div1><div1 id="HD" n="5" name="Chapter" ref="Y"><head>The TEI Header</head><p>This chapter addresses the problems of describing an encoded work so
that the text itself, its source, its encoding, and its revisions are
all thoroughly documented.  Such documentation is equally necessary for
scholars using the texts, for software processing them, and for
cataloguers in libraries and archives.  Together these descriptions and
declarations provide an electronic analogue to the title page attached
to a printed work.  They also constitute an equivalent for the content
of the code books or introductory manuals customarily accompanying
electronic data sets.
</p><p>Every TEI-conformant text must carry such a set of descriptions,
prefixed to it and encoded as described in this chapter.  The set is
known as the <term>TEI header</term>, tagged <gi tei="yes">teiHeader</gi>,
and it has four major parts:

<list type="bullets"><item>a <term>file description</term>, tagged <gi tei="yes">fileDesc</gi>,
containing a full bibliographical description of the computer file
itself, from which a user of the text could derive a proper
bibliographic citation, or which a librarian or archivist could use in
creating a catalogue entry recording its presence within a library or
archive.  The term <term>computer file</term> here is to be understood
as referring to the whole entity or document described by the header, 
even when this is stored in several distinct operating system files.
The file description also includes information about the
source or sources from which the electronic document was derived.  The TEI
elements used to encode a file description are described in section<xref target="HD2"/>
 below.
</item><item>an <term>encoding description</term>, tagged <gi tei="yes">encodingDesc</gi>,
which describes the relationship between an electronic text and its
source or sources.  It allows for detailed description of whether (or
how) the text was normalized during transcription, how the encoder
resolved ambiguities in the source, what levels of encoding or analysis
were applied, and similar matters. The TEI elements used to encode the
encoding description are described in section <xref target="HD5"/> below.
</item><item>a <term>text profile</term>, tagged <gi tei="yes">profileDesc</gi>,
containing classificatory and contextual information about the text,
such as its subject matter, the situation in which it was produced, the
individuals described by or participating in producing it, and so forth.
Such a text profile is of particular use in highly structured composite
texts such as corpora or language collections, where it is often highly
desirable to enforce a controlled descriptive vocabulary or to perform
retrievals from a body of text in terms of text type or origin.  The
text profile may however be of use in any form of automatic text
processing.  The TEI elements used to encode the profile description
are described in section <xref target="HD4"/> below.
</item><item>a <term>revision history</term>, tagged <gi tei="yes">revisionDesc</gi>,
which allows the encoder to provide a history of changes made during the
development of the electronic text.  The revision history is important
for <term>version control</term> and for resolving questions about the
history of a file.  The TEI elements used to encode the revision
description are described in section <xref target="HD6"/> below.</item></list>
</p><p>A TEI header can be a very large and complex object, or it may be a
very simple one.  Some application areas (for example, the construction
of language corpora and the transcription of spoken texts) will require
more specialized and detailed information than others.  The present
proposals therefore define both a <term>core</term> set of elements,
(all of which may be used without formality in any TEI header) and
<term>additional tagsets</term>, which may be invoked as extensions as
needed.  For more details of this extension mechanism, see chapter <xref target="STBA"/>; the header extensions are fully described in chapter <xref target="CC"/>, which should be read in conjunction with the present
chapter.
</p><p>The next section of the present chapter briefly introduces the
overall structure of the header, and the kinds of data it may contain.
This is followed by a detailed description of all the constituent
elements which may be used in the core header.  Section <xref target="HD7"/>, at the end of the present chapter, discusses the
recommended content of a minimal TEI header, and its relation to
standard library cataloguing practices.  Recommendations relevant to the
use of TEI headers as free-standing documents, for interchange among
libraries, data archives, and similar institutions may be found in
chapter <xref target="SH"/>.
<?tei:SOF p2hd1.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd1.odd,v $
# Revision 1.4  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.3  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
# --><!-- Revision:                                                --><!-- 10 jan 98 : LB : tweak egs to disappear --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!-- 93-06-04 : MSM : replace ref to PR3 with ref to DSfront  --><!-- 93-06-02 : MSM : use std dtdstart entity in dtdfrag      --><!-- 93-06-01 : MSM : normalize teiHeader                     --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-18 : MSM : fixed xrefs                             --><!-- 92-08-14 : MSM : more changes, typos, ...                --><!-- 5 Aug 92 : LB : last check: to UIC                       --><!-- 1 Aug 92 : LB  : further revisions                       --><!-- 22 Jul 92 : MSM : Redivide, recast slightly.             --><!-- 25 Jul 92 : MSM : rigorous application of ML name rules  --><!--                   the results seem odd, either because   --><!--                   unfamiliar or because ML rules need    --><!--                   revision.  See how they wear.          -->
</p><div2 id="HD1" name="bar" ref="Y"><head>Organization of the TEI Header</head><div3 id="HD11" name="burp" ref="Y"><head>The TEI Header and Its Components</head><p>The <gi tei="yes">teiHeader</gi> element should be clearly distinguished both
from the <term>SGML prolog</term>, which comprises the SGML declaration
and the document type declaration (see chapter <xref target="SG"/>), and
from the <term>front matter</term> of the text itself (for which see
section <xref target="DSFRONT"/>).  A composite text, such as a corpus or
collection, may contain several headers, as further discussed below.  In
the usual case however, a TEI-conformant text will contain a single
<gi tei="yes">teiHeader</gi> element, followed by a single <gi tei="yes">text</gi> element.
</p><p>The header element has the following description:

<tagList style="one-line"><tagDesc tagDoc="TEIHEAD" atts="type"/></tagList>
</p><p>As discussed above, the <gi tei="yes">teiHeader</gi> element has four principal
components:

<tagList style="one-line"><tagDesc tagDoc="FILDESC"/><tagDesc tagDoc="ENCDESC"/><tagDesc tagDoc="PROFDESC"/><tagDesc tagDoc="REVDESC"/></tagList>
</p><p>Of these, only the <gi tei="yes">fileDesc</gi> element is required in all TEI
headers; the others are optional.  The full form of a TEI header is
thus:

<eg rend="skel"><![CDATA[<teiHeader>
    <fileDesc> ... </fileDesc>
    <encodingDesc> ... </encodingDesc>
    <profileDesc> ... </profileDesc>
    <revisionDesc> ... </revisionDesc>
</teiHeader>]]></eg>

while a minimal header takes the form:

<eg rend="skel"><![CDATA[<teiHeader>
    <fileDesc> ... </fileDesc>
</teiHeader>]]></eg>
</p><p>In the case of language corpora or collections, it may be
desirable to record header information either at the level of individual
components in the corpus or collection, or once for all at the level of
the corpus or collection itself, or at both levels.  More details
concerning the tagging of composite texts are given in section <xref target="CC"/>, which should be read in conjunction with the current
chapter.  An optional <att tei="yes">type</att> attribute may also be supplied on
the <gi tei="yes">teiHeader</gi> element to indicate whether the header applies
to a corpus or a single text.  A corpus may thus take the form:

<eg rend="skel"><![CDATA[<tei.2>
    <teiHeader type=corpus> ...
    <!-- header for corpus-level information -->
    </teiHeader>
    <tei.2>
         <teiHeader type=text> ...
         <!-- header for text-level information -->
         </teiHeader>
         <text> ... </text>
    </tei.2>
    <tei.2>
         <teiHeader type=text> ... </teiHeader>
         <text> ... </text>
    </tei.2>
    <!-- etc. -->
</tei.2>]]></eg>
<!-- left this in for now, but I dont think it's very helpful (LB) --><!-- that's cause you already know it.  the reader don't. -msm     -->
</p><p>The tags required for the TEI header are defined in the DTD file
<ident tei="yes" type="file">teihdr2</ident> which first defines the
<gi tei="yes">teiHeader</gi> element:

<dtdFrag id="D221" n="The TEI Header" file="teihdr2"><commDecl>teihdr2.dtd  Tags for TEI Header.</commDecl><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><tagDecl tagDoc="TEIHEAD"/></dtdFrag>
</p><p>Then it defines the rest of the header elements, embedding the
DTD fragments found later in this chapter:

<dtdFrag id="D221B" contin="D221"><dtdRef dtdFrag="D222"/><dtdRef dtdFrag="D223"/><dtdRef dtdFrag="D225"/><dtdRef dtdFrag="D224"/><dtdRef dtdFrag="D226"/></dtdFrag>
</p></div3><div3 id="HD12" name="burp" ref="Y"><head>Types of Content in the TEI Header</head><p>The elements occurring within the TEI header may contain several
types of content; the following list indicates how these types of
content are described in the following sections:

<list type="gloss"><label>free prose </label><item>Most elements contain simple running prose at
some level.  Many elements may contain either prose (possibly organized
into paragraphs) or more specific elements, which themselves contain
prose.  In this chapter's descriptions of element content, the phrase
<cited>prose description</cited> should be understood to imply a series of
paragraphs, each marked with the <tag compl="full" tei="yes">p</tag> tag.  The word
<cited>phrase</cited>, by contrast, should be understood to imply
character data, interspersed as need be with phrase-level elements, but
not organized into paragraphs.  For more information on paragraphs,
highlighted phrases, lists, etc., see section <xref target="COPA"/>.<!-- or target=COPARA -->
</item><label>grouping elements </label><item>Elements whose names end with the
suffix <cited>Stmt</cited> (e.g. <gi tei="yes">editionStmt</gi>,
<gi tei="yes">situationStmt</gi>) usually enclose a group of specialized elements
recording some structured information.  In the case of the bibliographic
elements, the suffix <cited>Stmt</cited> is used in names of elements
corresponding to the <soCalled>areas</soCalled> of the International
Standard Bibliographic Description.
<note source="auth" place="display" anchored="Y"><!-- need bibliographic reference for ISBD -->On the relation between the TEI proposals and other standards for
bibliographic description, see further section <xref target="HD8"/>.</note><!-- or target=P2.228 -->

In most cases grouping elements may contain prose descriptions as an
alternative to the set of specialized elements, thus allowing the
encoder to choose whether or not the information concerned should be
presented in a structured form or in prose.
</item><label>declarations </label><item>Elements whose names end with the suffix
<cited>Decl</cited> (e.g.  <gi tei="yes">subjectDecl</gi>, <gi tei="yes">refsDecl</gi>)
enclose information about specific encoding practices applied in the
electronic text; often these practices are described in coded form.
Typically, such information takes the form of a series of declarations,
identifying a code with some more complex structure or description.  A
declaration which applies to more than one text or division of a text
need not be repeated in the header of each such text.  Instead, the
<att tei="yes">decls</att> attribute of each text (or subdivision of the text) to
which the sampling declaration applies may be used to supply a cross
reference to it, as further described in section <xref target="CCAS"/>.<!-- was:  target=P2.3431>. --><!-- was:  target=SP31>. -->
</item><label>descriptions </label><item>Elements whose name end with the suffix
<cited>Desc</cited> (e.g.  <gi tei="yes">settingDesc</gi>, <gi tei="yes">projectDesc</gi>)
contain a prose description, possibly organized under some specific
headings by suggested sub-elements, but not necessarily so.
</item></list><?tei:EOF p2hd1.odd ??>
<?tei:SOF p2hd2.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd2.odd,v $
# Revision 1.5  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.4  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
# --><!-- Revisions:                                               --><!-- 11 jan 98 : LB : fix egs, first pass --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!--                     typos from DB                        --><!-- 28 dec 93: LB: change CITY to PUBPLACE passim --><!-- 93-08-18 : MSM : suppress respStmt, resp (resp, role)    --><!-- 93-08-18 : MSM : decls:  they go in core not here        --><!-- 93-06-03 : MSM : replace PLACE tag by CITY               --><!-- 93-06-01 : MSM : normalize citn, teihead, xrefs to ah    --><!--                  give example of copyright claim         --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-18 : MSM : minor punctuation, typo fixes           --><!-- 92-08-18 : MSM : revisions                               --><!-- 92-08-18 : MSM : fix some xrefs                          --><!-- 92-08-18 : MSM : provide citn for AACR 2                 --><!-- 92-08-14 : MSM : revise, fix details                     --><!-- 5 Aug 92 : LB : fixed up xrefs                           --><!-- 1 Aug 92 : LB : further revision                         --><!-- 23-6 Jul 92 : CMSMcQ : revision                          --><!-- 28 May 92 : CMSMcQ : changed all simple lists to bullets -->
</p></div3></div2><div2 id="HD2" name="bar" ref="Y"><head>The File Description</head><p>This section describes the <gi tei="yes">fileDesc</gi> element, which is the
first component of the <gi tei="yes">teiHeader</gi> element.
</p><p>The bibliographic description of a machine-readable text
resembles in structure that of a book, an article, or any other kind of
textual object.  The file description element of the TEI header has
therefore been closely modelled on existing standards in library
cataloguing; it should thus provide enough information to allow users
to give standard bibliographic references to the electronic text, and
to allow cataloguers to catalogue it.  Bibliographic citations
occurring elsewhere in the header, and also in the text itself, are
derived from the same model (on bibliographic citations in general, see
further section <xref target="COBI"/>).  See further section <xref target="HD8"/>.
<!-- or target='COBIBL' -->
</p><p>The bibliographic description of the electronic text (not its
source) is given in the mandatory <gi tei="yes">fileDesc</gi> element:
<tagList style="one-line"><tagDesc tagDoc="FILDESC"/></tagList>
</p><p>The <gi tei="yes">fileDesc</gi> element contains three mandatory elements and
four optional elements, each of which is described in more detail in
sections <xref target="HD21"/> to <xref target="HD27"/> below. These elements
are listed below in the order in which they must be given within the
<gi tei="yes">fileDesc</gi> element.
<tagList style="one-line"><tagDesc tagDoc="TITSTMT"/><tagDesc tagDoc="EDSTMT"/><tagDesc tagDoc="EXTENT"/><tagDesc tagDoc="PUBSTMT"/><tagDesc tagDoc="SERSTMT"/><tagDesc tagDoc="NOTSTMT"/><tagDesc tagDoc="SOUSTMT"/></tagList>
</p><p>A file description containing all possible subelements has the
following structure:

<eg rend="skel"><![CDATA[<teiHeader>
    <fileDesc>
         <titleStmt> ... </titleStmt>
         <editionStmt> ... </editionStmt>
         <extent> ... </extent>
         <publicationStmt> ... </publicationStmt>
         <seriesStmt> ... </seriesStmt>
         <notesStmt> ... </notesStmt>
         <sourceDesc> ... </sourceDesc>
    </fileDesc>
    <!-- remainder of TEI Header here -->
</teiHeader>]]></eg>

Several of these elements may be omitted; a minimal file description has
the following structure:

<eg rend="skel"><![CDATA[<teiHeader>
    <fileDesc>
         <titleStmt> ... </titleStmt>
         <publicationStmt> ... </publicationStmt>
         <sourceDesc> ... </sourceDesc>
    </fileDesc>
    <!-- remainder of TEI Header here -->
</teiHeader>]]></eg>
</p><p>The <gi tei="yes">fileDesc</gi> itself has the following formal definition:

<dtdFrag id="D222" n="The file description" file="teihdr2"><tagDecl tagDoc="FILDESC"/><dtdRef dtdFrag="D2221"/><dtdRef dtdFrag="D2222"/><dtdRef dtdFrag="D2223"/><dtdRef dtdFrag="D2224"/><dtdRef dtdFrag="D2225"/><dtdRef dtdFrag="D2226"/></dtdFrag>
</p><div3 id="HD21" name="burp" ref="Y"><head>The Title Statement</head><p>The <gi tei="yes">titleStmt</gi> element is the first component of the
<gi tei="yes">fileDesc</gi> element, and is mandatory:
<tagList style="one-line"><tagDesc tagDoc="TITSTMT"/></tagList>
It contains the title given to the electronic work, together with
optionally one or more <term>statements of responsibility</term> which
identify the encoder, author, compiler, or other parties responsible
for it:

<tagList style="one-line"><tagDesc tagDoc="TITLE"/><tagDesc tagDoc="AUTHOR"/><tagDesc tagDoc="SPONSOR"/><tagDesc tagDoc="FUNDER"/><tagDesc tagDoc="PRINCIPL"/><tagDesc tagDoc="RESP"/><tagDesc tagDoc="ROLE"/><tagDesc tagDoc="NAME"/></tagList>
<!-- < div4 id=HD211>< head>Title< /head>                     -->
</p><p>The <gi tei="yes">title</gi> element contains the chief name of the
file, including any alternative title or subtitles it may have.
It may be repeated, if the file has more than one title,
(perhaps in different languages) and takes whatever form is
considered appropriate by its creator.  Where the electronic work
is derived from an existing source text, it is strongly
recommended that the title for the former should also be derived
from the latter, but that it should be clearly distinguishable
from it.  For example, do not call the computer file <q>A
Sanskrit-English Dictionary, based upon the St. Petersburg
Lexicons</q>.  Call it, rather, <q>Sanskrit-English Dictionary,
based upon the St. Petersburg Lexicons: a machine readable
transcription</q>.  If you wish to retain some or all of the
title of the source text in the title of the computer file, then
introduce one of the following phrases:

<list type="bullets"><item>[title of source]:  a machine readable transcription.</item><item>[title of source]:  electronic edition.</item><item>A machine readable version of:  [title of source].</item></list>

This will distinguish the computer file from the source text in
citations and in catalogues which contain descriptions of both types of
material.
</p><p>The computer file will almost certainly have an external name (its
<soCalled>filename</soCalled> or <soCalled>data set name</soCalled>) or reference number on the
computer system where it resides at any time.  This name is likely to
change frequently, as new copies of the file are made on the computer
system.  Its form is entirely dependent on the particular computer
system in use and thus cannot always easily be transferred from one
system to another.  For these reasons, these Guidelines strongly
recommend that such names should <emph>not</emph> be used as the title
for any computer file.
</p><p>Helpful guidance on the formulation of useful descriptive titles in
difficult cases may be found in the Anglo-American Cataloguing Rules
(AACR 2), chapter 25, or in equivalent national-level bibliographical
documentation.<note source="auth" place="foot" anchored="Y"><citation>Michael Gorman and Paul W. Winkler, eds.,
<title>Anglo-American Cataloguing Rules</title>, Second Edition
(Chicago:  American Library Association; London:  Library Association;
Ottawa:  Canadian Library Association, 1978).</citation></note>
<!-- < div4 id=HD212>< head>Statements of responsibility< /head> -->
</p><p>The specialized elements <gi tei="yes">author</gi>, <gi tei="yes">sponsor</gi>,
<gi tei="yes">funder</gi>, and <gi tei="yes">principal</gi>, and the more general
<gi tei="yes">respStmt</gi> provide the <term>statements of responsibility</term>
which identify the persons responsible for the intellectual or artistic
content of an item and any corporate bodies from which it emanates.
</p><p>Any number of statements of responsibility may occur within the title
statement.  At a minimum, identify the author of the text and the
creator of the machine-readable file.  If the bibliographic description
is for a corpus, identify the creator of the corpus.  These
identifications are mandatory when applicable, though not enforceable by
the SGML parser.  Optionally include also names of others involved in
the transcription or elaboration of the text, sponsors, and funding
agencies.  The name of the person responsible for physical data input
need not normally be recorded, unless that person is also intellectually
responsible for some aspect of the creation of the file.
</p><p>Where the person whose responsibility is to be documented is not an
author, sponsor, funding body or principal researcher, the <gi tei="yes">respStmt</gi>
element should be used.  This has two subcomponents: a <gi tei="yes">name</gi>
element identifying a responsible individual or organization, and a
<gi tei="yes">resp</gi> element indicating the nature of the responsibility.  No
specific recommendations are made at this time as to appropriate content
for the <gi tei="yes">resp</gi>:  it should make clear the nature of the
responsibility concerned, as in the examples below.
</p><p>Names given may be personal names or corporate names.  Give all names
in the form in which the persons or bodies wish to be publicly cited.
This would usually be the fullest form of the name, including first
names.  <note source="auth" place="foot" anchored="Y">Agencies compiling catalogues of
machine-readable files are recommended to use available authority lists,
such as the Library of Congress Name Authority List, for all common
personal names.<!-- bib ref needed here -->
 </note>
</p><p>Examples:

<eg><![CDATA[<titleStmt>
  <title>Capgrave's Life of St. John Norbert:  a
     machine-readable transcription</title>
  <respStmt>
      <resp>compiled by</resp> <name>P.J. Lucas</name>
  </respStmt>
</titleStmt>]]></eg>
<eg><![CDATA[<titleStmt>
  <title>Two stories by Edgar Allen Poe:
           electronic version</title>
  <author>Poe, Edgar Allen (1809-1849)
  <respStmt><resp>compiled by</resp>
  <name>James D. Benson</name></respStmt>
</titleStmt>]]></eg>
<eg><![CDATA[<titleStmt>
  <title>Yogadar&sacute;anam (arth&amacr;t
         yogas&umacr;trap&macr;&tdot;ha&hdot;):
         a machine readable transcription.</title>
  <title>The Yogas&umacr;utras of Pata&ntilde;jali:
         a machine readable transcription.</title>
  <funder>Wellcome Institute for the History of Medicine
  </funder>
  <principal>Dominik Wujastyk</principal>
  <respStmt><name>Wieslaw Mical</name>
        <resp>data entry and proof correction</resp>
  </respStmt>
  <respStmt><name>Jan Hajic</name>
        <resp>conversion to TEI-conformant markup</resp>
  </respStmt>
</titleStmt>]]></eg>
</p><p>The formal definition of the <gi tei="yes">titleStmt</gi> element and its
constituents is as follows:

<dtdFrag id="D2221" n="The title statement" file="teihdr2"><tagDecl tagDoc="TITSTMT"/><tagDecl tagDoc="SPONSOR"/><tagDecl tagDoc="FUNDER"/><tagDecl tagDoc="PRINCIPL"/><commDecl>The TITLE, AUTHOR, NAME, RESPSTMT, and RESP elements are
declared in file teicore2.dtd, not here.</commDecl></dtdFrag>

</p></div3><div3 id="HD22" name="burp" ref="Y"><head>The Edition Statement</head><p>The <gi tei="yes">editionStmt</gi> element is the second component of the
<gi tei="yes">fileDesc</gi> element.  It is optional but recommended.
<tagList style="one-line"><tagDesc tagDoc="EDSTMT"/></tagList>

It contains either phrases or more specialized elements identifying the
edition and those responsible for it:

<tagList style="one-line"><tagDesc tagDoc="EDITION"/><tagDesc tagDoc="RESP"/><tagDesc tagDoc="NAME"/><tagDesc tagDoc="ROLE"/></tagList>
</p><p>For printed texts, the word <cited>edition</cited> applies to the set
of all the identical copies of an item produced from one master copy and
issued by a particular publishing agency or a group of such agencies.  A
change in the identity of the distributing body or bodies does not
normally constitute a change of edition, while a change in the master
copy does.
</p><p>For electronic texts, the notion of a <soCalled>master copy</soCalled> is not
entirely appropriate, since they are far more easily copied and modified
than printed ones; nonetheless the term <cited>edition</cited> may be used
for a particular state of a machine-readable text at which substantive
changes are made and fixed.  Synonymous terms used in these Guidelines
are <cited>version,</cited> <cited>level,</cited> and <cited>release</cited>.  The words
<cited>revision</cited> and <cited>update</cited>, by contrast, are used for minor
changes to a file which do not amount to a new edition.
</p><p>No simple rule can specify how <soCalled>substantive</soCalled>
changes have to be before they are regarded as producing a new edition,
rather than a simple update.  The general principle proposed here is
that the production of a new edition entails a significant change in the
intellectual content of the file, rather than its encoding or
appearance.  The addition of analytic coding to a text would thus
constitute a new edition, while automatic conversion from one coded
representation to another would not.  Changes relating to the character
code or physical storage details, corrections of misspellings, simple
changes in the arrangement of the contents and changes in the output
format do not normally constitute a new edition.  The addition of new
information (e.g. a linguistic analysis expressed in part-of-speech
tagging, sound or graphics, referential links to external datasets)
almost always does constitute a new edition.
</p><p>Clearly, there are always border line cases and the matter is
somewhat arbitrary.  The simplest rule is:  if you think that your file
is a new edition, then call it such.
An edition statement is optional for the first release of a
machine-readable file; it is mandatory for each later release,
though this requirement cannot be enforced by the SGML parser.
</p><p>Note that <emph>all</emph> changes in a file, whether or not they are
regarded as constituting a new edition or simply a new revision, should
be independently noted in the revision description section of the file
header (see section <xref target="HD6"/>).<!-- was target='P2.226' -->
<!-- drop this paragraph, move to a tutorial? -LB.            --><!-- Maybe. -MSM                                              --><!-- definitely! (LB)                                         --><!--                                                          --><!-- To avoid independent creation of multiple versions of    --><!-- a single source file, all called identically < q>second  --><!-- edition,< /q> it is recommended that < term>edition       --><!-- numbers< /term> be incremented only by the original      --><!-- creator of a computer file:  the person or body          --><!-- responsible for the first edition.  Others should        --><!-- either retain the base edition number and add a <        --><!-- q>revision< /q> or < q>update< /q> number only (as well  --><!-- as an appropriate statement of responsibility for the    --><!-- changes they have made), or else give their new          --><!-- edition a non-numeric name (< q>revised, corrected       --><!-- edition by N.N.< /q>) If someone other than the          --><!-- original creator makes substantial changes in the        --><!-- file, they may wish to regard the new version as a <     --><!-- q>derivative work< /q> (in a non-pejorative sense) and   --><!-- assign it a new title, beginning the edition numbering   --><!-- again from 1. In this case, the bibliographic            --><!-- description of the old edition may be embedded within    --><!-- the source description of the new file.  See section <   --><!-- xref target=HD4>.  was target='P2.224'                   -->
</p><p>The <gi tei="yes">edition</gi> element should contain phrases describing the
edition or version, including the word <cited>edition</cited>,
<cited>version</cited>, or equivalent, together with a number or date,
or terms indicating difference from other editions such as <cited>new
edition</cited>, <cited>revised edition</cited> etc.  Any dates that
occur within the edition statement should be marked with the
<gi tei="yes">date</gi> element.  The <att tei="yes">n</att> attribute of the
<gi tei="yes">edition</gi> element may be used as elsewhere to supply any formal
identification (such as a version number) for the edition.
</p><p>One or more <gi tei="yes">respStmt</gi> elements may also be used to supply
statements of responsibility for the edition in question.  These may
refer to individuals or corporate bodies and can indicate functions such
as that of a reviser, or can name the person or body responsible for the
provision of supplementary matter, of appendices, etc., in a new
edition.  For further detail on the <gi tei="yes">respStmt</gi> element, see section<xref target="COBI"/>
.
</p><p>Some examples follow:

<eg><![CDATA[<editionStmt>
  <edition n='P2'>Second draft, substantially
       extended, revised, and corrected.</edition>
</editionStmt>]]></eg>

<eg><![CDATA[<editionStmt>
<edition>Student's edition, <date>June 1987</date></edition>
<respStmt>
  <resp>New annotations by</resp> <name>George Brown</name>
</respStmt>
</editionStmt>]]></eg>

The formal definition of the <gi tei="yes">editionStmt</gi> element is as follows:

<dtdFrag id="D2222" n="The edition statement" file="teihdr2"><tagDecl tagDoc="EDSTMT"/><tagDecl tagDoc="EDITION"/></dtdFrag>
</p></div3><div3 id="HD23" name="burp" ref="Y"><head>Type and Extent of File</head><p>The <gi tei="yes">extent</gi> element is the third component of the
<gi tei="yes">fileDesc</gi> element.  It is optional.
<tagList style="one-line"><tagDesc tagDoc="EXTENT"/></tagList>
</p><p>For printed books, information about the carrier, such as the kind of
medium used and its size, are of great importance in cataloguing
procedures.  The print-oriented rules for bibliographic description of
an item's medium and extent need some re-interpretation when applied to
electronic media.  An electronic file exists as a distinct entity quite
independently of its carrier and remains the same intellectual object<!-- same intell. object, but not nec. same bibliographic item -->
whether it is stored on a magnetic tape, a CD-ROM, a set of floppy disks
or as a file on a mainframe computer.  Since, moreover, these Guidelines
are specifically aimed at facilitating transparent document storage and
interchange, any purely machine-dependent information should be
irrelevant as far as the file header is concerned.
</p><p>This is particularly true of information about <term>file-type</term>
although library-oriented rules for cataloguing often distinguish two
types of computer file:  <q>data</q> and <q>programs</q>.  This
distinction is quite difficult to draw in some cases, for example,
hypermedia or texts with built in search and retrieval software.
However, since all files covered by these Guidelines are of the same
kind, SGML representations, it is unnecessary to specify the file type
separately.
<!-- commented this out:  SGML tries to make graphics         --><!-- linkage system-independent, so this sounds like          --><!-- confession of an Achilles heel.  -MSM  OK -LB            --><!-- When non-textual data (for example, encoded graphics or  --><!-- sounds) are included with a TEI text, this will          --><!-- necessarily be done in a highly system-dependent manner, --><!-- and is therefore not recommended for inclusion in the    --><!-- TEI-header.                                              -->
</p><p>Although it is equally system-dependent, some measure of the size of
the computer file may be of use for cataloguing and other practical
purposes.  Because the measurement and expression of file size is
fraught with difficulties, only very general recommendations are
possible; the element <gi tei="yes">extent</gi> is provided for this purpose.  It
contains a phrase indicating the size or approximate size of the
computer file in one of the following ways:

<list type="bullets"><item>in bytes of a specified length (e.g. <q>4000 16-bit bytes</q>)</item><item>as falling within a range of categories, for example:
<list type="bullets"><item>less than 1 Mb</item><item>between 1 Mb and 5 Mb</item><item>between 6 Mb and 10 Mb</item><item>over 10 Mb</item></list></item><item>in terms of any convenient logical units (for example,
words or sentences, citations, paragraphs)</item><item>in terms of any convenient physical units (for example,
blocks, disks, tapes)</item></list>
</p><p>Examples:

<eg><![CDATA[<extent>between 1 16-bit Mb and 2 16-bit Mb</extent>
<extent>4532 bytes</extent>
<extent>3200 sentences</extent>
<extent>5 3.5" High Density Diskettes</extent>]]></eg>

The <gi tei="yes">extent</gi> element has the following formal declaration:
<dtdFrag id="D2223" n="The extent statement" file="teihdr2"><tagDecl tagDoc="EXTENT"/></dtdFrag>
</p></div3><div3 id="HD24" name="burp" ref="Y"><head>Publication, Distribution, etc.</head><!-- Tags defined:  publicationStmt, publisher, distributor,  --><!-- authority, city, address, idno, availability.            --><!-- Tags described:  date.                                   --><p>The <gi tei="yes">publicationStmt</gi> element is the fourth component of the
<gi tei="yes">fileDesc</gi> element and is mandatory.

<tagList style="one-line"><tagDesc tagDoc="PUBSTMT"/></tagList>

It may contain either a simple prose description, or groups of the
elements described below:

<tagList style="one-line"><tagDesc tagDoc="PUBLISHR"/><tagDesc tagDoc="DISTRIB"/><tagDesc tagDoc="AUTHORTY"/></tagList>
</p><p>The <term>publisher</term> is the person or institution by whose
authority a given edition of the file is made public.  The
<term>distributor</term> is the person or institution from whom copies
of the text may be obtained.  Where a text is not considered formally
published, but is nevertheless made available for circulation by some
individual or organization, this person or institution is termed the
<term>release authority</term>.
</p><p>At least one of these three elements must be present, unless the
entire publication statement is given as prose.  Each may be followed by
one or more of the following elements, in the following order:

<tagList style="one-line"><tagDesc tagDoc="PUBPLACE"/><tagDesc tagDoc="ADDRESS"/><tagDesc tagDoc="IDNO" atts="type"/><tagDesc tagDoc="AVAIL" atts="status"/><tagDesc tagDoc="DATE"/></tagList>
</p><p>Note that the dates, places, etc., given in the publication statement
relate to the publisher, distributor, or release authority most recently
mentioned.  If the text was created at some date other than its date of
publication, its date of creation should be given within the
<gi tei="yes">profileDesc</gi> element, not in the publication statement.  Give
any other useful dates (e.g., dates of collection of data) in a note.
</p><p>Additional detailed tagsets may be used for the encoding of names,
dates and addresses, as further described in section <xref target="CONA"/>
and chapter <xref target="ND"/>.
</p><p>Examples:

<eg><![CDATA[<publicationStmt>
     <publisher>Oxford University Press</publisher>
     <pubPlace>Oxford</pubPlace> <date>1989</date>
     <idno type=ISBN>0-19-254705-4</idno>
     <availability><p>Copyright 1989, Oxford University Press
     </availability>
</publicationStmt>]]></eg>

<eg><![CDATA[<publicationStmt>
    <authority>James D. Benson</authority>
    <pubPlace>London</pubPlace> <date>1984</date>
</publicationStmt>]]></eg>
<eg><![CDATA[<publicationStmt>
     <publisher>Sigma Press</publisher>
     <date>1991</date>
     <address>
        <addrLine>21 High Street,</addrLine> 
        <addrLine>Wilmslow,</addrLine>  
        <addrLine>Cheshire M24 3DF</addrLine> 
     </address>
     <distributor>Oxford Text Archive</distributor>
     <idno type='ota'>1256
     <availability><p>Available with prior consent of depositor for
        purposes of academic research and teaching only.
</publicationStmt>]]></eg>
</p><p>The publication statement and its components are formally defined as
follows:

<dtdFrag id="D2224" n="The publication statement" file="teihdr2"><tagDecl tagDoc="PUBSTMT"/><tagDecl tagDoc="DISTRIB"/><tagDecl tagDoc="AUTHORTY"/><tagDecl tagDoc="IDNO"/><tagDecl tagDoc="AVAIL"/><commDecl>The PUBLISHER, PUBPLACE, and ADDRESS elements
are defined in file teicore2.dtd.</commDecl></dtdFrag>

</p></div3><div3 id="HD26" name="burp" ref="Y"><head>The Series Statement</head><p>The <gi tei="yes">seriesStmt</gi> element is the fifth component of the
<gi tei="yes">fileDesc</gi> element and is optional.

<tagList style="one-line"><tagDesc tagDoc="SERSTMT"/></tagList>
</p><p>In bibliographic parlance, a <term>series</term> may be defined in
one of the following ways:

<list type="bullets"><item>A group of separate items related to one another by the fact
that each item bears, in addition to its own title proper, a
collective title applying to the group as a whole.  The
individual items may or may not be numbered.</item><item>Each of two or more volumes of essays, lectures, articles,
or other items, similar in character and issued in sequence.</item><item>A separately numbered sequence of volumes within a series or
serial.</item></list>

The <gi tei="yes">seriesStmt</gi> element may contain a prose description or one
or more of the following more specific elements:

<tagList style="one-line"><tagDesc tagDoc="TITLE"/><tagDesc tagDoc="IDNO"/><tagDesc tagDoc="RESP"/><tagDesc tagDoc="ROLE"/><tagDesc tagDoc="NAME"/></tagList>
</p><p>The <gi tei="yes">idno</gi> may be used to supply any identifying number
associated with the item, including both standard numbers such as an
ISSN and particular issue numbers.<note source="auth" place="display" anchored="Y">Arabic numerals separated by
punctuation are recommended for this purpose (e.g., 6.19.33, not
VI/xix:33).</note> Its <att tei="yes">type</att> attribute is used to categorize
the number further, taking the value <code tei="yes" type="value">ISSN</code> for an ISSN for
example.
</p><p>Examples:

<eg><![CDATA[<seriesStmt>
    <title level="S">Machine-Readable Texts for the Study of
    Indian Literature</title>
    <respStmt>
         <resp>ed. by</resp> <name>Jan Gonda</name>
     </respStmt>
     <idno type="vol">1.2</idno>
     <idno type ='ISSN'>0 345 6789</idno>
</seriesStmt>]]></eg>

The series statement has the following formal definition:

<dtdFrag id="D2225" n="The series statement" file="teihdr2"><tagDecl tagDoc="SERSTMT"/></dtdFrag>

Its components are all defined elsewhere.
</p></div3><div3 id="HD27" name="burp" ref="Y"><head>The Notes Statement</head><p>The <gi tei="yes">notesStmt</gi> element is the sixth component of the
<gi tei="yes">fileDesc</gi> element and is optional.  If used, it contains one or
more <gi tei="yes">note</gi> elements, each containing a single piece of
descriptive information of the kind treated as <soCalled>general
notes</soCalled> in traditional bibliographic descriptions.

<tagList style="one-line"><tagDesc tagDoc="NOTSTMT"/><tagDesc tagDoc="NOTE"/></tagList>
</p><p>Some information found in the notes area in conventional bibliography
has been assigned specific elements in these Guidelines; in particular
the following items should be tagged as indicated, rather than as
general notes:

<list type="bullets"><item>the nature, scope, artistic form or purpose of the file; also
the genre or other intellectual category to which it may belong:
e.g. <q>Text types:  newspaper editorials and reportage, science
fiction, westerns, and detective stories</q>. These should be
formally described within the <gi tei="yes">profileDesc</gi> element
(section <xref target="HD4"/>).<!-- was target='P2.224'>) --></item><item>summary description providing a factual, non-evaluative
account of the subject content of the file.  E.g. <q>Transcribes
interviews on general topics with native speakers of English in
17 cities during the spring and summer of 1963.</q> These should
also be formally described within the <gi tei="yes">profileDesc</gi> element
(section <xref target="HD4"/>).<!-- was target='P2.224'>) --></item><item>bibliographic details relating to the source or sources of
an electronic text: e.g. <q>Transcribed from the Norton
facsimile of the 1623 Folio</q>. These should be formally
described in the <gi tei="yes">sourceDesc</gi> element
(section <xref target="HD3"/>).<!-- was target='P2.223'>). --></item><item>further information relating to publication, distribution
or release of the text, including sources from which the text
may be obtained, any restrictions on its use or formal terms on
its availability.  These should be placed in the appropriate
division of the <gi tei="yes">publicationStmt</gi> element
(section <xref target="HD24"/>).<!-- was target='P2.2224'>). --></item><item>publicly documented numbers associated with the file:  e.g.
<q>ICPSR study number 1803</q> or <q>Oxford Text Archive text
number 1243</q>.  These should be placed in an <gi tei="yes">idno</gi>
element within the appropriate division of the
<gi tei="yes">publicationStmt</gi> element.  International Standard
Serial Numbers (ISSN), International Standard Book Numbers
(ISBN), and other internationally agreed upon standard numbers
that uniquely identify an item, should be treated in the same
way, rather than as specialized bibliographic notes.</item></list>
</p><p>Nevertheless, the <gi tei="yes">notesStmt</gi> element may be used to record
potentially significant details about the file and its features, e.g.:

<list type="bullets"><item>dates, when they are relevant to the content or condition of the
computer file:  e.g.  <q>manual dated 1983,</q> <q>Interview wave I:
Apr. 1989; wave II: Jan. 1990</q></item><item>names of persons or bodies connected with the technical production,
administration or consulting functions of the effort which produced
the file, if these are not named in statements of responsibility in
the title or edition statements of the file description:
e.g. <q>Historical commentary provided by Mark Cohen</q></item><item>availability of the file in an additional medium or information not
already recorded about the availability of documentation:
e.g. <q>User manual is loose-leaf in eleven paginated sections</q></item><item>language of work and abstract:  e.g. <q>Text in English with
summaries in French and German</q></item><item>The unique name assigned to a serial by the International Serials
Data System (ISDS)</item><item>lists of related publications, either describing the source itself,
or concerned with the creation or use of the machine-readable file, e.g.
<q>Texts used in <citation><title>Computation into Criticism</title>
(Oxford, 1987)</citation></q></item></list>
</p><p>Each such item of information should be tagged using the
general-purpose <gi tei="yes">note</gi> element, which is described in section<xref target="CONO"/>
.  Groups of notes are contained within the
<gi tei="yes">notesStmt</gi> element, as in the following example:
<eg><![CDATA[<notesStmt>
  <note>Historical commentary provided by Mark Cohen.</note>
  <note>OCR scanning done at University of Toronto.</note>
</notesStmt>]]></eg>
The notes statement has the following formal definition:

<dtdFrag id="D2226" n="The notes statement" file="teihdr2"><tagDecl tagDoc="NOTSTMT"/><commDecl>The NOTE element is defined with the core tags.</commDecl></dtdFrag>
<?tei:EOF p2hd2.odd ??>
<?tei:SOF p2hd3.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd3.odd,v $
# Revision 1.7  1994/04/01  16:23:58  msmcq
# Misc. changes/fixes while validating DTDs
#
# Revision 1.6  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
#
# Revision 1.5  1994/01/04  13:02:03  lou
# fix examples
#
# Revision 1.3  1993/08/18  21:31:24  msmcq
# name shift (role/resp, resp/respStmt) on account of DR role
#
# Revision 1.2  1993/06/22  14:29:49  msmcq
# Changes post Eynsham and for DTD generation
# --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : explicitly embed d2231                  --><!-- 94-03-29 : MSM : suppress supererogatory file att on dtdfrags --><!-- 94-03-24 : CMSMcQ : one more typo                        --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!--                     notes from DB                        --><!-- 93-08-18 : MSM : new names for respStmt, role/resp       --><!-- 93-06-02 : MSM : rename listbibl from bibllist           --><!-- 93-06-01 : MSM : normalize citn, teihead, xrefs to ah    --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-18 : MSM : some points of style and detail         --><!-- 92-08-14 : MSM : revisions, restore recording stmt       --><!-- 1 aug 92: LB: some juggling with ids and ordering        --><!--     also, gritted teeth and moved recording and script stmts --><!--     to aux header. You can explain to Stig!              --><!-- 26 Jul 92 : MSM : very light revision, almost nothing    --><!--                   except in 22.3.2 (reordering)          --><!-- 25 Jul 92 : MSM : names updated, ids updated             -->
 </p></div3><div3 id="HD3" name="burp" ref="Y"><head>The Source Description</head><!-- was div2: demoted for consistency with structure of dtd (LB) --><!--   (maybe its id should change too ; left as is for now )     --><p>The <gi tei="yes">sourceDesc</gi> element is the seventh and final component of
the <gi tei="yes">fileDesc</gi> element.  It is a mandatory element, and is used to
record details of the source or sources from which a computer file is
derived.  This might be a printed text or manuscript, another computer
file, an audio or video recording of some kind, or a combination of
these.  An electronic file may also have no source, if what is being
catalogued is an original text created in electronic form.
<tagList style="one-line"><tagDesc tagDoc="SOUSTMT"/></tagList>
 </p><p>The <gi tei="yes">sourceDesc</gi> element may contain a simple prose
description, or, more usefully, a bibliographic citation of some kind
specifying the provenance of the text.  For written or printed sources,
the source should be described in the same way as any other
bibliographic citation, using one of the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="BIBL"/><tagDesc tagDoc="BIBLSTRU"/><tagDesc tagDoc="BIBLFULL"/><tagDesc tagDoc="LISTBIBL"/></tagList>
 
These elements are described in more detail in section<xref target="COBI"/>
.<!-- or:  target=COBIBL>. --></p><p>When the header describes a transcription of spoken material, the
<gi tei="yes">sourceDesc</gi> element may also include the following
special-purpose elements, intended for cases where an electronic text
is derived from a spoken text rather than a written one:
<tagList style="one-line"><tagDesc tagDoc="SCRSTMT"/><tagDesc tagDoc="RECSTMT"/></tagList>
Full descriptions of these elements and their contents are given in
section <xref target="HD32"/>.</p><p>The <gi tei="yes">sourceDesc</gi> element may contain a mixture of one or more
of the above elements, as in the following examples:
 
<eg><![CDATA[<sourceDesc>
   <bibl>The first folio of Shakespeare, prepared by
   Charlton Hinman (The Norton Facsimile, 1968)</bibl>
</sourceDesc>]]></eg>
<eg><![CDATA[<sourceDesc>
   <p>No source: created in machine-readable form.</p>
</sourceDesc>]]></eg>
<eg><![CDATA[<sourceDesc>
   <biblStruct lang=FR>
   <monogr>
    <author>Eug&egrave;ne Sue</>
    <title>Martin, l'enfant trouv&eacute;</>
    <title type=sub>M&eacute;moires d'un valet de chambre</>
    <imprint>
         <pubPlace>Bruxelles et Leipzig</>
         <publisher>C. Muquardt</>
         <date>1846</>
    </imprint>
   </monogr></biblStruct>
</sourceDesc>]]></eg>
 </p><p>The source description itself has the following formal definition:
<dtdFrag id="D223" n="The source description"><tagDecl tagDoc="SOUSTMT"/><dtdRef dtdFrag="D2231"/></dtdFrag>
 </p></div3><div3 id="HD31" name="burp" ref="Y"><head>Computer Files Derived from Other Computer Files
 </head><p>If a machine-readable text (call it B) is based not on a
printed source but upon another machine-readable text (call it
A) which includes a TEI file header, then the source text of
computer file B is another computer file, A.  The four sections
of A's file header will need to be incorporated into the new
header for B in slightly differing ways, as listed below:
 
<list type="gloss"><label>fileDesc</label><item>A's file description should be copied into the
<gi tei="yes">sourceDesc</gi> section of B's file description, enclosed
within a <gi tei="yes">biblFull</gi> element
(see section <xref target="COBI"/>).<!-- was:  target='P2.235'>). --><!-- was:  target='COBIBL'>). -->
 </item><label>profileDesc</label><item>A's <gi tei="yes">profileDesc</gi> should be
copied into B's, in principle unchanged.
 </item><label>encodingDesc</label><item>A's coding practice may or (more likely) may not be the
same as B's. Since the object of the coding description is to
define the relationship between the current file and its source,
in principle only changes in encoding practice between A and B
need be documented in B. The relationship between A and its
source(s) is then only recoverable from the original header of
A. In practice it may be more convenient to create a new
complete <gi tei="yes">encodingDesc</gi> for B based on A's.
 </item><label>revisionDesc</label><item>B is a new electronic file, and should therefore have a
new revision description. If, however, it is felt useful to
include some information from A's <gi tei="yes">revisionDesc</gi>, for
example dates of major updates or versions, such information
must be clearly marked as relating to A rather than to B.
 </item></list>
 </p></div3><div3 id="HD32" name="burp" ref="Y"><head>Computer Files Composed of Transcribed Speech
 </head><p>Where an electronic text is derived from a spoken text rather than a
written one, it will usually be desirable to record additional
information about the recording or broadcast which constitutes its
source.  Several additional elements are provided for this purpose
within the source description element:
 
<tagList style="one-line"><tagDesc tagDoc="SCRSTMT"/><tagDesc tagDoc="RECSTMT"/><tagDesc tagDoc="RECORDIN" atts="type dur"/><tagDesc tagDoc="EQUIPMEN"/><tagDesc tagDoc="BROADCAS"/></tagList>
 </p><p>Note that detailed information about the participants or setting of
an interview or other transcript of spoken language should be recorded
in the appropriate division of the profile description, discussed in
chapter <xref target="CC"/>, rather than as part of the source
description.  The source description is used to hold information only
about the source from which the transcribed speech was taken, for
example, any script being read and any technical details of how the
recording was  produced.  If the source was a previously-created
transcript, it should be treated in the same way as any other source
text.
 </p><p>The <gi tei="yes">scriptStmt</gi> element should be used where it is known that
one or more of the participants in a spoken text is speaking from a
previously prepared script.  The script itself should be documented in
the same way as any other written text, using one of the three citation
tags mentioned above.  Utterances or groups of utterances may be linked
to the script concerned by means of the <att tei="yes">decls</att> attribute,
described in section <xref target="CCAS"/>.<!-- was:  target='P2.3431'>. --><!-- or :  target='SP31'>. -->
 
<eg><![CDATA[<sourceDesc>
  <scriptStmt id=CNN12>
  <bibl><author>CNN Network News</>
     <title>News headlines</>
     <date>12 Jun 1991</>
  </bibl>
  </scriptStmt>
  <!-- this script statement might be used to document
       the parts of a spoken transcript which included
       a news broadcast -->
  <!-- possibly other script statements or recording
       statements follow -->
</sourceDesc>]]></eg>
 </p><p>The <gi tei="yes">recordingStmt</gi> is used to group together information
relating to the recordings from which the spoken text was transcribed.
The element may contain either a prose description or, more helpfully,
one or more <gi tei="yes">recording</gi> elements, each corresponding with a
particular recording.  The linkage between utterances or groups of
utterances and the relevant recording statement is made by means of the
<att tei="yes">decls</att> attribute, described in section <xref target="CCAS"/>.<!-- was:  target=P2.3431>. --><!-- was:  target=SP31>. -->
 </p><p>The <gi tei="yes">recording</gi> element should be used to provide a
description of how and by whom a recording was made.  This information
may be a prose description, within which such items as statements of
responsibility, names, places and dates should be identified using the
appropriate phrase level tags.  The <gi tei="yes">recording</gi> element takes two
additional attributes, as indicated above:  <att tei="yes">type</att> is used to
specify the kind of recording concerned and <att tei="yes">dur</att> to specify
its length.
 </p><p>In addition, descriptive information relating to the kind of
recording equipment used should be specified using the
<gi tei="yes">equipment</gi> element.  Where a recording is taken from a public
broadcast, details of the broadcast should be given using the
<gi tei="yes">broadcast</gi> element described further below.  Specialized
collections may wish to add further sub-elements to these major
components.  Note however that this element should be used only for
information relating to the recording process itself; information about
the setting or participants (for example) is recorded elsewhere:  see
sections <xref target="CCAHSE"/> and <xref target="CCAHPA"/> below.<!-- was:  xref target=HD44 and xref target=HD45 -->
 
<eg><![CDATA[  <recording type=video>
  <p>U-matic recording made by college audio-visual
    department staff,available as PAL-standard VHS
    transfer or sound-only casssette
  </recording>]]></eg>
 
<eg><![CDATA[  <recording type=audio dur="30 mins">
  <respStmt>
     <resp>Location recording by</resp>
     <name>Sound Services Ltd.</name>
  </respStmt>
  <equipment>
     <p>Multiple close microphones mixed down to stereo Digital
     Audio Tape, standard play, 44.1 KHz sampling frequency
  </equipment>
  <date>12 Jan 1987</date>
  </recording>]]></eg>
 </p><p>When a recording has been made from a public broadcast, details of
the broadcast itself should be supplied within the <gi tei="yes">recording</gi>
element, as a nested <gi tei="yes">broadcast</gi> element.  A broadcast is closely
analogous to a publication and the <gi tei="yes">broadcast</gi> element should
therefore contain one or the other of the bibliographic citation
elements <gi tei="yes">bibl</gi>, <gi tei="yes">biblStruct</gi> or <gi tei="yes">biblFull</gi>.  The
broadcasting agency responsible for a broadcast is regarded as its
author, while other participants (for example interviewers,
interviewees, directors, producers, etc.) should be specified using the
<gi tei="yes">respStmt</gi> or <gi tei="yes">editor</gi> element with an appropriate
<gi tei="yes">resp</gi> (see further section <xref target="COBI"/>).<!-- was:  target='P2.235'>). --><!-- was:  target=COBIBL>). -->
 
<eg><![CDATA[<recording type=audio dur="10 mins">
  <equipment><p>Recorded from FM Radio to digital tape</>
  <broadcast>
     <bibl><title>Interview on foreign policy</>
              <author>BBC Radio 5</>
       <respStmt><resp>interviewer</><name>Robin Day</></>
       <respStmt><resp>interviewee</><name>Margaret Thatcher</></>
       <series><title>The World Tonight</></>
       <note>First broadcast on <date>27 Nov 1989</></note>
    </bibl>
  </broadcast>
</recording>]]></eg>
 </p><p>When a broadcast contains several distinct recordings (for example a
compilation), additional <gi tei="yes">recording</gi> elements may be further
nested within the <gi tei="yes">broadcast</gi> element.
 
<eg><![CDATA[    <recording dur=100>
       <broadcast>
         <!-- details of broadcast -->
         <recording>
            <!-- details of broadcast recording -->
         </recording>
      </broadcast>
   </recording>]]></eg><!-- need a real example here --><!-- damn straight.  -msm     -->
 </p><p>Formal definitions for the elements discussed in this section are as
follows:
<dtdFrag id="D2231" n="Script statement and recording statement"><tagDecl tagDoc="SCRSTMT"/><tagDecl tagDoc="RECSTMT"/><tagDecl tagDoc="RECORDIN"/><tagDecl tagDoc="EQUIPMEN"/><tagDecl tagDoc="BROADCAS"/></dtdFrag></p><p>This concludes the discussion of the <gi tei="yes">fileDesc</gi> element and
its contents.<?tei:EOF p2hd3.odd ??>
<!-- &p2.hd4; &p2.hd5; --><!-- swopped these two around as per Chicago meeting  --><!-- (also needed extensive changes to text and dtd)  --><!-- but left ids unchanged for now  --><?tei:SOF p2hd5.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2hd5.odd,v $
    * Revision 1.10  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.9  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.8  1994/04/01  16:23:58  msmcq
    * Misc. changes/fixes while validating DTDs
    * 
    * Revision 1.7  1994/03/24  22:14:56  msmcq
    * typo corrections from David Barnard, Peter Robinson, and others
    * 
    * Revision 1.6  1994/01/28  18:04:57  lou
    * add fsdDecl and metDecl
    * 
    * Revision 1.2  1993/06/22  14:29:49  msmcq
    * Changes post Eynsham and for DTD generation
    * --><!-- Revisions:                                               --><!-- 10 jan 98 : LB : fixing egs --><!-- 4 Jan 98 : LB : changed wsd to fsd in eg --><!-- 94-03-29 : MSM : suppress supererogatory file att on dtdfrags --><!-- 94-03-29 : MSM : add varencod                            --><!-- 94-03-24 : CMSMcQ : more typos, from Peter R             --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!-- 22 jan 94 : LB : add metdecl and fsdDecl --><!-- 9 jan : LB: samplingDecl, not Desc --><!-- 28 dec 93: LB: INTERP changed to INTERPTN  --><!-- 93-06-21 : MSM : change file id on dtdfrags              --><!-- 93-06-01 : MSM : add dtdfrag for tagsdecl                --><!-- 93-06-01 : MSM : add tagsDecl section (from LB)          --><!--                  add example of samplingDecl to show     --><!--                  documentation of systematic omissions   --><!-- 93-06-01 : MSM : misc normalizations                     --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-19 : MSM : Change straggling refs to ANALYSIS      --><!-- 92-08-18 : MSM : revisions as per LB talk                --><!-- 92-08-18 : MSM : change -isa- -ise- to -iza- -ize-       --><!-- 92-08-17 : MSM : Change ANALYSIS to INTERP               --><!-- 92-08-14 : MSM : revisions, clarifications               --><!-- 2 Aug 92: further revisions for consistency (LB) --><!-- 25 Jul 92 : MSM : names updated, ids updated             -->
</p></div3></div2><div2 id="HD5" name="bar" ref="Y"><head>The Encoding Description</head><p>The <gi tei="yes">encodingDesc</gi> element is the second major subdivision of
the TEI header.  It specifies the methods and editorial principles which
governed the transcription or encoding of the text in hand and may also
include sets of coded definitions used by other components of the
header.  Though not formally required, its use is highly recommended.
<tagList style="one-line"><tagDesc tagDoc="ENCDESC"/></tagList>
The content of the encoding description may be a prose description, or
it may contain elements from the following list, in the order given:
<tagList style="one-line"><tagDesc tagDoc="PROJDESC"/><tagDesc tagDoc="SAMPDECL"/><tagDesc tagDoc="EDDECL"/><tagDesc tagDoc="TAGSDECL"/><tagDesc tagDoc="REFSDECL"/><tagDesc tagDoc="CLASDECL"/><tagDesc tagDoc="FSDDECL"/><tagDesc tagDoc="METDECL"/><tagDesc tagDoc="VARENCOD"/></tagList>
 
Each of these elements is further described and formally defined
in the appropriate section below. The encoding description itself
is defined as follows:
 
<dtdFrag id="D225" n="The encoding description"><tagDecl tagDoc="ENCDESC"/><dtdRef dtdFrag="D2251"/><dtdRef dtdFrag="D2252"/><dtdRef dtdFrag="D2253"/><dtdRef dtdFrag="DHD57"/><dtdRef dtdFrag="D2254"/><dtdRef dtdFrag="D2255"/><dtdRef dtdFrag="D2256"/><dtdRef dtdFrag="D2258"/><dtdRef dtdFrag="DHDVAR"/></dtdFrag></p><div3 id="HD51" name="burp" ref="Y"><head>The Project Description</head><p>The <gi tei="yes">projectDesc</gi> element is the first of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It may be used to
describe, in prose, the purpose for which the electronic file was
encoded, together with any other relevant information concerning the
process by which it was assembled or collected.  This is of particular
importance for corpora or miscellaneous collections, but may be of use
for any text, for example to explain why one kind of encoding practice
has been followed rather than another.
<tagList style="one-line"><tagDesc tagDoc="PROJDESC"/></tagList></p><p>For example:
<eg><![CDATA[ <encodingDesc>
 <projectDesc><p>Texts collected for use in the
    Claremont Shakespeare Clinic, June 1990.
 </encodingDesc>]]></eg></p><p>This element has the following formal declaration:
<dtdFrag id="D2251" n="The project description"><tagDecl tagDoc="PROJDESC"/></dtdFrag></p></div3><div3 id="HD52" name="burp" ref="Y"><head>The Sampling Declaration</head><p>The <gi tei="yes">samplingDecl</gi> element is the second of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It contains a prose
description of the rationale and methods used in sampling texts, for
example to create a representative corpus.
<tagList style="one-line"><tagDesc tagDoc="SAMPDECL"/></tagList>
It should include information about such matters as
 
<list type="bullets"><item>the size of individual samples</item><item>the method or methods by which they were selected</item><item>the underlying population being sampled</item><item>the object of the sampling procedure used</item></list>
 
but is not restricted to these.<!-- should attributes be used for sample size, etc? -LB --><!-- if it would help automatic processing yes.  but i   --><!-- doubt it.  so no.  -msm                             -->
 
<eg><![CDATA[<samplingDecl>
  <p>Samples of 2000 words taken from the beginning of the text.
</samplingDecl>]]></eg></p><p>It may also include a simple
description of any parts of the source text included or excluded.
 
<eg><![CDATA[<samplingDecl>
  <p>Text of stories only has been transcribed.
     Pull quotes, captions, and advertisements have been
     silently omitted.  Any mathematical expressions
     requiring symbols not present in the ISOnum or
     ISOpub entity sets have been omitted, and their
     place marked with a GAP element.
</samplingDecl>]]></eg></p><p>A sampling declaration which applies to more than one text or
division of a text need not be repeated in the header of each such text.
Instead, the <att tei="yes">decls</att> attribute of each text (or subdivision of
the text) to which the sampling declaration applies may be used to
supply a cross reference to it, as further described in section <xref target="CCAS"/>.<!-- was:  target=P2.3431>. --><!-- was:  target=SP31>. -->
This element has the following formal declaration:
 
<dtdFrag id="D2252" n="The sampling declaration"><tagDecl tagDoc="SAMPDECL"/></dtdFrag></p></div3><div3 id="HD53" name="burp" ref="Y"><head>The Editorial Practices Declaration</head><p>The <gi tei="yes">editorialDecl</gi> element is the third of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It is used to
provide details of the editorial practices applied during the encoding
of a text.
<tagList style="one-line"><tagDesc tagDoc="EDDECL"/></tagList>
It may contain a prose description only, or one or more of the following
specialized elements:
 
<tagList style="one-line"><tagDesc tagDoc="CORRECTN" atts="status method"/><tagDesc tagDoc="NORMALZN" atts="source method"/><tagDesc tagDoc="QUOTN" atts="marks form"/><tagDesc tagDoc="HYPHEN" atts="eol"/><tagDesc tagDoc="SEGMENTN"/><tagDesc tagDoc="STDVALS"/><tagDesc tagDoc="INTERPTN"/></tagList>
 <!-- PR urges for P4 a clearer distinction between            --><!-- proofreading and editorial correction.                   -->
 
Some of these elements carry attributes to support automated processing
of certain well-defined editorial decisions; all of them contain a prose
description of the editorial principles adopted with respect to the
particular feature concerned.  Examples of the kinds of questions which
these descriptions are intended to answer are listed below, in the same
order as the list above.
 
<list type="gloss"><label><gi tei="yes">correction</gi></label><item>Was the text corrected during or after data capture?  If
so, were corrections made silently or are they marked using the
tags described in section <xref target="COED"/>?  What principles<!-- was:  target='P2.47' --><!-- was:  target='COEDIT'-->
have been adopted with respect to omissions, truncations, dubious
corrections, alternate readings, false starts, repetitions, etc.?</item><label><gi tei="yes">normalization</gi></label><item>Was the text normalized, for example by regularizing any
non-standard spellings, dialect forms, etc.?  If so, were normalizations
performed silently or are they marked using the tags described in
section <xref target="COED"/>?<!-- was:  target='P2.47' --><!-- was:  target='COEDIT' -->
What authority was used for the regularization?  Also, what principles
were used when normalizing dates or numbers to provide the standard
values for the <att tei="yes">value</att> attribute described in sections <xref target="CONANU"/> and <xref target="CONADA"/><!-- was:  target='P2.23a'  and target='P2.23b'  --><!-- was:  target='CONUMS'  and target='CODATE'  -->
and what format used for them?</item><label><gi tei="yes">quotation</gi></label><item>How were quotation marks processed?  Are apostrophes and quotation
marks distinguished?  How?  Are quotation marks retained as content in
the text or replaced by markup?  Was the <att tei="yes">rendition</att> attribute
used to record the specific appearance of any quotation marks removed
from the text?  Are there any special conventions regarding for example
the use of single or double quotation marks when nested?  Is the file
consistent in its practice or has this not been checked?</item><label><gi tei="yes">hyphenation</gi></label><item>Does the encoding distinguish <soCalled>soft</soCalled> and
<soCalled>hard</soCalled> hyphens?
What principle has been adopted with respect to end-of-line hyphenation
where source lineation has not been retained?  Have soft hyphens been
silently removed, and if so what is the effect on lineation and
pagination?</item><label><gi tei="yes">segmentation</gi></label><item>How is the text segmented?  If
<gi tei="yes">s</gi> or <gi tei="yes">seg</gi> segmentation units have been used to divide
up the text for analysis, how are they marked and how was the
segmentation arrived at?</item><label><gi tei="yes">stdVals</gi></label><item>What standardization methods underly any standardized values
supplied for numeric values or dates?  If the <att tei="yes">value</att> attribute
described in section <xref target="CONADA"/> has been used,<!-- was:  target='P2.23b' --><!-- was:  target='CODATE' -->
in what format are its values presented?</item><label><gi tei="yes">interpretation</gi></label><item>Has any analytic or <soCalled>interpretive</soCalled> information
been provided --- that is, information which is felt to be non-obvious,
contentious, or subject to disagreement? If so, how was it generated?
How was it encoded? If feature-structure analysis has been used, are
<gi tei="yes">fsdDecl</gi> elements (section <xref target="HDFSD"/>) present?</item></list></p><p>Any information about the editorial principles applied not falling
under one of the above headings should be recorded in a distinct list
of items.  Experience shows that a full record should be kept of
decisions relating to editorial principles and encoding practice,
both for future users of the text and for the project which produced
the text in the first instance.
 <!-- Need at least one example!  But I don't have time to     --><!-- to add one.   in haste, -msm                             -->
A simple example follows:
<eg><![CDATA[<editorialDecl id=E2>
<interpretation>
  <p>The part of speech analysis applied throughout section 4 was
  added by hand and has not been checked.
<correction><p>Errors in transcription controlled by using the
    WordPerfect spelling checker.
<normalization source=W9>
  <p>All words converted to Modern American spelling using
    Websters 9th Collegiate dictionary.
<quotation marks=all form=std>
  <p>All opening quotation marks converted to &odq; all closing
    quotation marks converted to &cdq;.
</editorialDecl>]]></eg><!-- an unresolved problem: where do I store the full citation --><!-- to which 'W9' is meant to be pointing at? --><!-- DB objects to '&amp;odq;' as "indecipherable" (msm)      --></p><p>These elements are formally defined as follows:
<dtdFrag id="D2253" n="The editorial practices declaration"><tagDecl tagDoc="EDDECL"/><tagDecl tagDoc="CORRECTN"/><tagDecl tagDoc="NORMALZN"/><tagDecl tagDoc="QUOTN"/><tagDecl tagDoc="HYPHEN"/><tagDecl tagDoc="SEGMENTN"/><tagDecl tagDoc="STDVALS"/><tagDecl tagDoc="INTERPTN"/></dtdFrag>
 
An editorial practices declaration which applies to more than one text
or division of a text need not be repeated in the header of each such
text.  Instead, the <att tei="yes">decls</att> attribute of each text (or
subdivision of the text) to which it applies may
be used to supply a cross reference to it, as further described in
section <xref target="CCAS"/>.<!-- was:  target=P2.3431>. --><!-- was:  target=SP31>. --></p></div3><div3 id="HD57" name="burp" ref="Y"><head>The Tagging Declaration</head><p>The <gi tei="yes">tagsDecl</gi> element is the fourth of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It is used to record
the following information about the tagging used within a particular
text:
<list type="simple"><item>how often particular SGML elements appear within the text, so that
a recipient can validate the integrity of a text during interchange.</item><item>any comment relating to the usage of particular elements not
specified elsewhere in the header.</item><item>a definition for the default rendition applying to all instances
of an element, unless otherwise stated by the global <att tei="yes">rend</att>
attribute.</item></list></p><p>This information is conveyed by the following elements:
<tagList style="one-line"><tagDesc tagDoc="RENDITN"/><tagDesc tagDoc="TAGUSAGE" atts="occurs ident render"/></tagList></p><p>The <gi tei="yes">tagsDecl</gi> element consists of an optional sequence of
<gi tei="yes">rendition</gi> elements, each of which must bear a unique
identifier, followed by a sequence of <gi tei="yes">tagUsage</gi> elements, one
for each distinct element occurring within the outermost
<gi tei="yes">text</gi> element of a TEI document.</p><p>The <gi tei="yes">rendition</gi> element defined in this version of the TEI
Guidelines is a preliminary proposal only, intended to provide a hook
for more detailed specifications of default rendition in later versions.
 <!-- Or think of it as the VAL attribute on MSM's --><!-- proposed SETREND element... --></p><p>The present proposal allows the encoder to enter an informal
description of a rendition, or style, as running prose only. This
rendition will be assumed to apply, by default, to all occurrences of
an element which names its identifier as the value of the
<att tei="yes">render</att> attribute of the appropriate <gi tei="yes">tagUsage</gi>
element. For element occurrences to which this default rendition does
not apply, the encoder should specify an explicit description using the
global <att tei="yes">rend</att> attribute on the elements concerned.</p><p>For example, the following schematic shows how an encoder might
specify that <gi tei="yes">p</gi> elements are by default to be rendered using one
set of specifications identified as <code tei="yes" type="value">style1</code>,
while <gi tei="yes">hi</gi>
elements are to use a different set, identified as <code tei="yes" type="value">style2</code>:
 
<eg><![CDATA[<tagsDecl>
 <rendition id=STYLE1>
   <!-- description of one default rendition here -->
 <rendition id=STYLE2>
   <!-- description of another default rendition here -->
 <tagUsage gi=p render=style1>
 <tagUsage gi=hi render=style2>
</tagsDecl>]]></eg></p><p>No detailed proposals for the content of the <gi tei="yes">rendition</gi>
element have as yet been formulated.  It is probable that subsequent
work will incorporate specifications derived from, or compatible with,
the properties currently being standardized as part of the draft
Document Style and Semantics Specification Language (ISO DIS 10179).</p><p>A <gi tei="yes">tagsDecl</gi> need not specify any <gi tei="yes">rendition</gi> element.
If present, it must however contain exactly one occurrence of a
<gi tei="yes">tagUsage</gi> element for each distinct element marked within the
outermost <gi tei="yes">text</gi> element associated with the <gi tei="yes">teiHeader</gi>
in which it appears.<note source="auth" place="display" anchored="Y">This implies that the <gi tei="yes">tagsDecl</gi> will
normally only appear in the header of individual texts in a
<gi tei="yes">teiCorpus</gi>.</note> The <gi tei="yes">tagUsage</gi> element is used to
supply a count of the number of occurrences of this element within the
text, which is given as the value of its <att tei="yes">occurs</att> attribute.
It may also be used to hold any additional usage information, which is
supplied as running prose within the element itself.</p><p>For example:
 
<eg><![CDATA[  <tagUsage gi=hi occurs=28>
      Used only to mark English words italicised in the copy text.
  </tagUsage>]]></eg>
 
This indicates that the <gi tei="yes">hi</gi> element appears a total of 28 times
in the <gi tei="yes">text</gi> element in question, and that the encoder has used
it to mark italicised English phrases only.</p><p>The <att tei="yes">ident</att> attribute may optionally be used to specify how
many of the occurrences of the element in question bear a value for the
global <att tei="yes">id</att> attribute, as in the following example:
 
 
<eg><![CDATA[  <tagUsage gi=pb occurs=321 ident=321>
      Marks page breaks in the York (1734) edition only
  </tagUsage>]]></eg>
 
This indicates that the <gi tei="yes">pb</gi> element occurs 321 times, on each
of which an identifier is provided.</p><p>The content of the <gi tei="yes">tagUsage</gi> element is not susceptible of
automatic processing.  It should not therefore be used to hold
information for which provision is already made by other components of
the encoding description.  A TEI conformant document is not required
to contain a <gi tei="yes">tagsDecl</gi> element, but if one is present, it must
contain <gi tei="yes">tagUsage</gi> elements for each distinct element marked in
the associated text, and the counts specified by their <att tei="yes">usage</att>
elements must correspond with the number of such elements present in the
document, as identified by some conforming SGML processor.
 <!-- the document's Element Structure Information Set, that   --><!-- is, as identified by any conforming SGML processor.      -->
 <!-- OK? YHBW! --><!-- I don't think we should refer to ESIS without defining it. --><!-- I don't think we should get into defining ESIS here.     --><!-- Therefore I don't think we should refer to it here.      --><!-- But how else do we say it?  -msm                         --><!-- without mentioning ESIS. -msm                            -->
 
<dtdFrag id="DHD57" n="Tag usage and rendition declarations"><tagDecl tagDoc="TAGSDECL"/><tagDecl tagDoc="TAGUSAGE"/><tagDecl tagDoc="RENDITN"/></dtdFrag></p></div3><div3 id="HD54" name="burp" ref="Y"><head>The Reference System Declaration</head><p>The <gi tei="yes">refsDecl</gi> element is the fifth of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element. It is used to
document the way in which any standard referencing scheme built into
the encoding works, either as a series of prose paragraphs or by
using the following specialized elements:
 
<tagList style="one-line"><tagDesc tagDoc="REFSDECL" atts="doctype"/><tagDesc tagDoc="STEP"/><tagDesc tagDoc="STATE"/></tagList>
 
Note that not all possible referencing schemes are equally easily
supported by current software systems.  A choice must be made between
the convenience of the encoder and the likely efficiency of the
particular software applications envisaged, in this context as in many
others.  For a more detailed discussion of referencing
systems supported by these Guidelines, see section <xref target="CORS"/> below.<!-- was:  target=CORSYS> --><!-- was:  target=P2.232> --></p><p>A referencing scheme may be described in one of three ways using this
element:
 
<list type="bullets"><item>as a prose description</item><item>as a series of <term>steps</term> expressed in the TEI
extended pointer notation (documented in section <xref target="SAXR"/>)</item><item>as a concatenation of sequentially organized
<term>milestones</term></item></list>
 
Each method is described in more detail below.  Only one method can be
used within a single <gi tei="yes">refsDecl</gi> element.</p><p>More than one <gi tei="yes">refsDecl</gi> element can be included in the header
if more than one canonical reference scheme is to be used in the same
document, but the current proposals do not check for mutual
inconsistency.  A reference declaration can only describe the
referencing system applicable to a single document type; if therefore
concurrent document types are in use (as discussed in section <xref target="CORS"/>), a <gi tei="yes">refsDecl</gi> element must be supplied for each;
the <att tei="yes">doctype</att> attribute should be used to specify the document
type to which the declaration relates.</p><div4 id="HD54P" name="Section" ref="Y"><head>Prose Method</head><p>The referencing scheme may be specified within the <gi tei="yes">refsDecl</gi>
by a simple prose description.  Such a description should indicate which
elements carry identifying information, and whether this information is
represented as attribute values or as content.  Any special rules about
how the information is to be interpreted when reading or generating a
reference string should also be specified here.  Such a prose
description cannot be processed automatically, and this method of
specifying the structure of a canonical reference system is therefore
not recommended for automatic processing.</p><p>For example:
 
<eg><![CDATA[ <refsDecl>
 <p>The N attribute of each text in this corpus carries
 a unique identifying code for the whole text. The title
 of the text is held as the content of the first HEAD
 element within each text. The N attribute on each DIV1
 and DIV2 contains the canonical reference for
 each such division, in the form 'XX.yyy', where XX
 is the book number in Roman numerals, and yyy the section
 number in arabic. Line breaks are marked by empty LINEBREAK
 tags, each of which includes the through line number
 in Casaubon's edition as the value of its N attribute.
 <p>The through line number and the text identifier
 uniquely identify any line. A canonical reference
 may be made up by concatenating the the N values from the
 text, div1 or div2 and calculating the line number within
 each part.
 </refsDecl>]]></eg></p></div4><div4 id="HD54S" name="Section" ref="Y"><head>Stepwise Method</head><p>This method defines each reference as a series of <term>steps</term>,
each of which corresponds to a single pair of expressions in the TEI
extended pointer notation (for which see section <xref target="SAXR"/>).
Often, but not always, each step will also correspond to one portion of
the canonical reference itself; in many common forms of canonical
reference, each step will narrow the scope within which the next step
can be taken.  The <gi tei="yes">refsDecl</gi> element must specify the steps,
delimiters and lengths to be used by an application program, both when
constructing references for a given location and when interpreting
canonical references within a given document hierarchy.  It does so by
supplying one or more <gi tei="yes">step</gi> elements, each of which identifies
the type of <soCalled>reference unit</soCalled> handled by the step and
uses a pair of extended-pointer expressions to indicate the starting and
ending pointers of the portion of the document which corresponds to a
given portion of the reference string.  The element may also give either
a delimiter or a length for use in breaking the corresponding reference
string up into units.
 
<tagList style="one-line"><tagDesc tagDoc="STEP" atts="refunit from to delim length"/></tagList></p><p>For example, the reference <q>Matthew 5:29</q> might be constructed
by stepping down the tree to find an element labelled as the
<q>Matthew</q> node, then within that to the <q>5</q> node, and finally,
within that, to the <q>29</q> node.  The following declarations would be
required; the special values <code tei="yes" type="value">%1</code>, <code tei="yes" type="value">%2</code>, and <code tei="yes" type="value">%3</code> refer here to the
strings <cited>Matthew</cited>, <cited>5</cited>, and <cited>29</cited>,
respectively.
 
<eg><![CDATA[<refsDecl>
    <step refunit='book' delim=' '
          from='DESCENDANT (1 DIV1 N %1)'>
    <step refunit='chapter' delim=':'
          from='DESCENDANT (1 DIV2 N %2)'>
    <step refunit='verse'
          from='DESCENDANT (1 DIV3 N %3)'>
</refsDecl>]]></eg>
 
As this example also shows, the steps of such a reference are typically
separated by fixed character sequences, called <term>delimiters</term>.
In this example, the delimiters are a space (following <q>Matthew</q>)
and a colon (following the chapter number).  A processor for canonical
references would use the delimiters specified by the <att tei="yes">delim</att>
attributes to break the reference string up into pieces; the pieces
would then be used to interpret the <code tei="yes" type="value">%1</code>, etc., in
the extended pointer expressions of the <att tei="yes">from</att> and
<att tei="yes">to</att> attributes.</p><p>An alternative to the use of delimiters is to specify a fixed length
for each step of the reference:  for example, the same reference might
be given as <q>MAT05029</q>, assuming a fixed length of 3 for the first
step, 2 for the second and 3 for the third.
 
<eg><![CDATA[<refsDecl>
    <step length=3
          from='DESCENDANT (1 DIV1 N %1)'>
    <step length=2
          from='DESCENDANT (1 DIV2 N %2)'>
    <step length=3
          from='DESCENDANT (1 DIV3 N %3)'>
</refsDecl>]]></eg>
 
The order in which the <gi tei="yes">step</gi> elements are supplied corresponds
here with the order of elements within the reference, with the largest
(that is, the one nearest the top of the document hierarchy) item first
and the smallest last.</p><p>For a description of the processing required when a canonical
reference defined by <gi tei="yes">step</gi> elements is to be recognized,
and examples of its use, see chapter <xref target="CR"/>.
 <!-- following material deleted (regretfully) as too detailed: should --><!-- all go to section CREF --></p></div4><div4 id="HD54M" name="Section" ref="Y"><head>Milestone Method</head><p>This method is appropriate when only <soCalled>milestone</soCalled>
tags (see section <xref target="CORS5"/>) are available to provide the
required referencing information.  It does not provide any abilities
which cannot be mimicked by the stepwise referencing method discussed in
the previous section, but in the cases where it applies, it provides a
somewhat simpler notation.</p><p>A reference based on milestone tags concatenates the values specified
by one or more such tags.  Since each tag marks the point at which a
value changes, it may be regarded as specifying the <term>state</term>
of a variable.  A reference declaration using this method therefore
specifies the individual components of the canonical reference as a
sequence of <gi tei="yes">state</gi> elements:
 
<tagList style="one-line"><tagDesc tagDoc="STATE" atts="ed unit delim length"/></tagList></p><p>For example, the reference <q>Matthew 12:34</q> might be thought of
as representing the state of three variables:  the <q>book</q> variable
is in state <q>Matthew</q>; the <ident tei="yes" type="var">chapter</ident> variable
is in state <q>12</q>, and the <ident tei="yes" type="var">verse</ident> variable is
in state <q>34</q>.  If milestone tagging has been used, there should be
a tag marking the point in the text at which each of the above
<soCalled>variables</soCalled> changes its state.<note source="auth" place="foot" anchored="Y">On the
milestone tag itself, what are here referred to as
<soCalled>variables</soCalled> are identified by the combination of the
<att tei="yes">ed</att> and <att tei="yes">unit</att> attributes.</note>
To find <q>Matthew 12:34</q> therefore an application must scan left to
right through the text, monitoring changes in the state of each of these
three variables as it does so.  When all three are simultaneously in the
required state, the desired point will have been reached.  There may of
course be several such points.</p><p>The <att tei="yes">delim</att> and <att tei="yes">length</att> attributes are used to
specify components of a canonical reference using this method in exactly
the same way as for the stepwise method described in the preceding
section.  The other attributes are used to determine which instances of
<gi tei="yes">mileStone</gi> tags in the text are to be checked for state-changes.
A state-change is signalled whenever a new <gi tei="yes">mileStone</gi> tag is
found with <att tei="yes">unit</att> and, optionally, <att tei="yes">ed</att> attributes
identical to those of the <gi tei="yes">state</gi> element in question.  The value
for the new state may be given explicitly by the <att tei="yes">n</att> attribute
on the <gi tei="yes">mileStone</gi> element, or it may be implied, if the
<att tei="yes">n</att> attribute is not specified.</p><p>For example, for canonical references in the form <cited>xx.yyy</cited> where
the <cited>xx</cited> represents the page number in the first edition, and
<cited>yyy</cited> the line number within this page, a reference system
declaration such as the following would be appropriate:
 
<eg><![CDATA[ <refsDecl>
   <state ed='first' unit='page' delim='.' length=2>
   <state ed='first' unit='line' length=4>
 </refsDecl>]]></eg>
 
This implies that milestone tags of the form
 
<eg><![CDATA[ <mileStone ed='first' unit=page n='II'>
 <mileStone ed='first' unit=line>]]></eg>
 
will be found throughout the text, marking the positions at which page
and line numbers change. Note that no value has been specified for the
<att tei="yes">n</att> attribute on the second milestone tag above; this implies
that its value at each state change is monotonically increased.
For more detail on the use of milestone tags, see section<xref target="CORS5"/>
.<!-- was:  target=P2.232ms> --><!-- was:  target=CORSYS5 > --><!-- following algorithm should also be moved to CREF --></p><p>The milestone referencing scheme, though conceptually simple, is not
and cannot be supported by an SGML parser.  Its use places a
correspondingly greater burden of verification and accuracy on the
encoder.</p><p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id="D2254" n="The reference scheme declaration"><tagDecl tagDoc="REFSDECL"/><tagDecl tagDoc="STEP"/><tagDecl tagDoc="STATE"/></dtdFrag></p><p>A reference system declaration which applies to more than one text or
division of a text need not be repeated in the header of each such text.
Instead, the <att tei="yes">decls</att> attribute of each text (or subdivision of
the text) to which the declaration applies may be used to supply a cross
reference to it, as further described in section <xref target="CCAS"/>.<!-- was:  target=SP31>. --><!-- was:  target=P2.3431>. -->
 </p></div4></div3><div3 id="HD55" name="burp" ref="Y"><head>The Classification Declaration</head><p>The <gi tei="yes">classDecl</gi> element is the sixth of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It is used to group
together definitions or sources for any descriptive classification
schemes used by other parts of the header.  Each such scheme is
represented by a <gi tei="yes">taxonomy</gi> element, which may contain either a
simple bibliographic citation, or a definition of the
descriptive typology concerned; the following elements are used
in defining a descriptive classification scheme:
 
<tagList style="one-line"><tagDesc tagDoc="CLASDECL"/><tagDesc tagDoc="TAXONOMY"/><tagDesc tagDoc="CATEGORY"/><tagDesc tagDoc="CATDESC"/></tagList>
 
The <gi tei="yes">taxonomy</gi> element has two slightly different, but related,
functions. For well-recognized and documented public classification
schemes, such as Dewey or other published descriptive thesauri, it
contains simply a bibliographic citation indicating where a full
description of a particular taxonomy may be found.
<eg><![CDATA[<taxonomy id=DDC12>
  <bibl><title>Dewey Decimal Classification</title>
    <edition>Abridged Edition 12</edition>
    <!-- etc. -->
  </bibl>
</taxonomy>]]></eg>
 
For less easily accessible schemes, the <gi tei="yes">taxonomy</gi> element
contains a description of the taxonomy itself as well as an optional
bibliographic citation.  The description consists of a number of
<gi tei="yes">category</gi> elements, each defining a single category within the
given typology.  The category is defined by the contents of a nested
<gi tei="yes">catDesc</gi> element, which may contain either a phrase describing
the category, or a <gi tei="yes">textDesc</gi> element defining it in terms of the
situational parameters discussed in section <xref target="CCAHTD"/>.  If the
category is subdivided, each subdivision is represented by a nested
<gi tei="yes">category</gi> element, having the same structure.  Categories may be
nested to an arbitrary depth in order to reflect the hierarchical
structure of the taxonomy.  Each <gi tei="yes">category</gi> element bears a
unique <att tei="yes">id</att> attribute, which is used as the target for
<gi tei="yes">catRef</gi> elements referring to it.
 
<eg><![CDATA[ 
<taxonomy id=B>
   <bibl>Brown Corpus</bibl>
   <category id=B.A><catDesc>Press Reportage
      <category id=B.A1><catDesc>Daily</category>
      <category id=B.A2><catDesc>Sunday</category>
      <category id=B.A3><catDesc>National</category>
      <category id=B.A4><catDesc>Provincial</category>
      <category id=B.A5><catDesc>Political</category>
      <category id=B.A6><catDesc>Sports</category>
    <!-- ... -->
   </category>
   <category id=B.D><catDesc>Religion
      <category id=B.D1><catDesc>Books</category>
      <category id=B.D2><catDesc>Periodicals and tracts</category>
   </category>
<!-- ... -->
</taxonomy>]]></eg></p><p>Linkage between a particular text and a category within such a
taxonomy is made by means of the <gi tei="yes">catRef</gi> element within the
<gi tei="yes">textClass</gi> element, as described in section <xref target="HD43"/>.  Where the taxonomy permits of classification along more
than one dimension, more than one category will be referenced by a
particular <gi tei="yes">catRef</gi>, as in the following example, which
identifies a text with the sub-categories <q>Daily</q>, <q>National</q>
and <q>Political</q>, within the category <q>Press Reportage</q> as
defined above.
 
<eg><![CDATA[ <catRef target="B.A1 B.A3 B.A5">]]></eg></p><p>The elements discussed in this section are defined as follows:
 
<dtdFrag id="D2255" n="The classification declaration"><tagDecl tagDoc="CLASDECL"/><tagDecl tagDoc="TAXONOMY"/><tagDecl tagDoc="CATEGORY"/><tagDecl tagDoc="CATDESC"/></dtdFrag></p></div3><div3 id="HDFSD" name="burp" ref="Y"><head>The Feature System Declaration</head><p>The <gi tei="yes">fsdDecl</gi> element is the seventh of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It is used to
associate a <term>feature system declaration</term>  (as defined in
chapter <xref target="FD"/>) with any analytic <term>feature
structures</term> (as defined in chapter <xref target="FS"/>) present in
the text documented by this header.</p><p>It has the following description and attributes:
 
<tagList style="one-line"><tagDesc tagDoc="FSDDECL" atts="type fsd"/></tagList>
 
Note that one <gi tei="yes">fsdDecl</gi> element must be specified for each
distinct type of feature structure used in the markup.  The
<att tei="yes">fsd</att> element supplies the name of an external entity
containing the actual declaration for that type of feature structure.
This entity will typically be defined in the document type subset for
the document, as in the following example:
 
<eg rend="skel"><![CDATA[<!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
   <!-- declare an external entity for the FSD -->
   <!ENTITY myFeatures  SYSTEM 'myfeat.fsd' SUBDOC >
]>
<tei.2>
<!-- ... -->
</tei.2>]]></eg>
 
This associates the name <ident rend="noindex" tei="yes" type="ge">myFeatures</ident>
with an external <code tei="yes" type="kw">SUBDOC</code> entity<note source="auth" place="display" anchored="Y">The <code tei="yes" type="kw">SUBDOC</code> keyword indicates to an SGML parser that this
entity contains SGML data which must be parsed using some other DTD than
the current one:  in this case, the DTD defined in chapter <xref target="FD"/> rather than the view of the TEI DTD defined for the
document itself.</note> held in this example within a system file called
<ident rend="noindex" tei="yes" type="file">myfeat.wsd</ident>.  This entity name may
then be specified within a <gi tei="yes">fsdDecl</gi> element in the header to
inform a processor of the location of the feature system declaration
corresponding to a given type of feature structure used within the text,
as follows:
 
<eg rend="skel"><![CDATA[   <teiHeader>
      <fileDesc> ... </fileDesc>
      <encodingDesc>
           <!-- ... -->
           <fsdDecl type=myA1 fsd=myFeatures>
           <fsdDecl type=myA2 fsd=myFeatures>
           <!-- ... -->
      </encodingDesc>]]></eg>
 
This header would be attached to a text in which feature structures of
types <code tei="yes" type="value">myA1</code> and <code tei="yes" type="value">myA2</code> are
used.</p><p>Further details and examples of the use of feature structure analyses
and feature system declarations are provided in chapters <xref target="FS"/> and <xref target="FD"/> respectively.</p><p>The <gi tei="yes">fsdDecl</gi> element is declared as follows:
 
<dtdFrag id="D2256" n="The FSD declaration"><tagDecl tagDoc="FSDDECL"/></dtdFrag></p></div3><div3 id="HDMN" name="burp" ref="Y"><head>The Metrical Declaration Element</head><p>The <gi tei="yes">metDecl</gi> element is the eighth of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It is used to
document any metrical notation scheme used in the text, as further
discussed in section <xref target="VEME"/>. It consists either of
a prose description or a series of <gi tei="yes">symbol</gi> elements.
 
<tagList style="one-line"><tagDesc tagDoc="METDECL" atts="pattern"/><tagDesc tagDoc="SYMBOL" atts="value terminal"/></tagList></p><p>As with other components of the header, metrical notation may be
specified either formally or informally. In a formal specification,
every symbol used in the metrical notation must be documented by a
corresponding <gi tei="yes">symbol</gi> element; in an informal one, only a brief
prose description of the way in which the notation is used need be
given. In either case, the optional <att tei="yes">pattern</att> attribute may be
used to supply a regular expression which a processor can use to
validate expressions in the intended notation. The following
constraints apply:
 
<list type="simple"><item>if <att tei="yes">pattern</att> is supplied, any notation used which does
not conform to it should be regarded as invalid</item><item>if any <gi tei="yes">symbol</gi> is defined, then any notation using
undefined symbols should be regarded as invalid</item><item>if both pattern and symbol are defined, then every symbol
appearing explicitly within pattern must be defined</item><item>symbols may be defined within a <gi tei="yes">metDecl</gi> element which are
not matched by <att tei="yes">pattern</att></item></list></p><p>As a simple example, consider the case of the notation in which
metrical prominence, foot and line boundaries are all to be encoded.
Legal specifications in this notation may be written for any sequence of
metrically prominent or non-prominent features, optionally separated by
foot or metrical line boundaries at arbitrary points.  Assuming that the
symbol <cited>1</cited> is used for metrical prominence,
<cited>0</cited> for non-prominence, <cited>|</cited> for foot boundary
and <cited>/</cited> for line boundary, then the following declaration
achieves this object:
 
<eg><![CDATA[<metDecl pattern= '((1|0)+\|?/?)*' >
   <symbol value='1'>metrical promimence
   <symbol value='0'>metrical non-prominence
   <symbol value='|'>foot boundary
   <symbol value='/'>metrical line boundary
</metDecl>]]></eg></p><p>The same notation might also be specified less formally, as follows:
 
<eg><![CDATA[<metDecl>
 <p>Metrically prominent syllables are marked '1' and other
    syllables '0'. Foot divisions are marked by a vertical bar,
    and line divisions with a solidus.
 <p>This notation may be applied to any metrical unit, of any
    size (including, for example, individual feet as well as
    groups of lines).
</metDecl>]]></eg>
 
Note that in this case, because the <att tei="yes">pattern</att> attribute has not
been supplied, no processor can validate <att tei="yes">met</att> attribute values
within the text which use this metrical notation.</p><p>For more complex cases, it will often be more convenient to define a
notation incrementally.  The <att tei="yes">terminal</att> attribute should be
used to indicate for a given symbol whether or not it may be re-defined
in terms of other symbols used within the same notation.  For example,
here is a notation for encoding classical metres, in which symbols are
provided for the most common types of foot.  These symbols are
themselves documented within the same notation, in terms of more
primitive long and short syllables:
 
<eg><![CDATA[<metDecl pattern='[DTIS3A]+'>
 <symbol value='D' n='dactyl'   terminal=N>-oo
 <symbol value='T' n='trochee'  terminal=N>-o
 <symbol value='I' n='iamb'     terminal=N>o-
 <symbol value='S' n='spondee'  terminal=N>--
 <symbol value='3' n='tribrach' terminal=N>ooo
 <symbol value='A' n='anapaest' terminal=N>oo-
 <symbol value='o'>short syllable
 <symbol value='-'>long syllable
</metDecl>]]></eg>
 
Note here the use of the global <att tei="yes">n</att> attribute to supply an
additional name for the symbols being documented.</p><p>For further discussion of this metrical notation and its use in the
encoding of verse, see section <xref target="VEME"/>.</p><p>The elements discussed in this section are defined as follows:
 
<dtdFrag id="D2258" n="Metrical Notation Declaration"><tagDecl tagDoc="METDECL"/><tagDecl tagDoc="SYMBOL"/></dtdFrag></p></div3><div3 id="HDVAR" name="burp" ref="Y"><head>The Variant-Encoding Method Element</head><p>The <gi tei="yes">variantEncoding</gi> element is the last of the nine optional
subdivisions of the <gi tei="yes">encodingDesc</gi> element.  It is used to
document the method used to encode textual variants in the text, as
discussed in section <xref target="TCAPLK"/>.
 
<tagList style="one-line"><tagDesc tagDoc="VARENCOD" atts="method location"/></tagList></p><p>Its formal declaration is as follows:
 
<dtdFrag id="DHDVAR" n="Variant-Encoding Declaration"><tagDecl tagDoc="VARENCOD"/></dtdFrag></p></div3></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2hd5.odd ??><?tei:SOF p2hd4.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2hd4.odd,v $
    * Revision 1.6  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.5  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.4  1994/04/01  16:23:58  msmcq
    * Misc. changes/fixes while validating DTDs
    * 
    * Revision 1.3  1994/03/24  22:14:56  msmcq
    * typo corrections from David Barnard, Peter Robinson, and others
    * 
    * Revision 1.2  1993/06/22  14:29:49  msmcq
    * Changes post Eynsham and for DTD generation
    * --><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : fix quebecois eg : no <p> allowed --><!-- 94-03-29 : MSM : suppress supererogatory file att on dtdfrags --><!-- 94-03-29 : MSM : change CITY to rs type=city             --><!-- 94-03-24 : CMSMcQ : more typos, from PR                  --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!--                     typos noted by DB                    --><!-- 93-06-03 : MSM : replace PLACE tag by CITY               --><!-- 93-06-01 : MSM : misc normalizations                     --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-18 : MSM : revisions, cosmetic changes             --><!-- 92-08-17 : MSM : further revisions as per LB discussion  --><!-- 2 Aug 92 : LB  : minor tweaks and tidying up             --><!-- 25 Jul 92 : MSM : names updated, ids updated             --><div2 id="HD4" name="bar" ref="Y"><head>The Profile Description</head><p>The <gi tei="yes">profileDesc</gi> element is the third major subdivision of
the TEI Header. It is an optional element, the purpose of which is to
enable information characterizing various descriptive aspects of a text
or a corpus to be recorded within a single unified framework.
 
<tagList style="one-line"><tagDesc tagDoc="PROFDESC"/></tagList>
 
In principle, almost any component of the header might be of
importance as a means of characterizing a text.  The author of a written
text, its title or its date of publication, may all be regarded as
characterizing it at least as strongly as any of the parameters
discussed in this section.  The rule of thumb applied has been to
exclude from discussion here most of the information which generally
forms part of a standard bibliographic style description,
if only because such information has already been included
elsewhere in the TEI header.
 <!-- forms part of a standard bibliographic style             --><!-- description, < note>with the exception of topic          --><!-- classification< /note> if only because such criteria     --><!-- are rarely used as the organizing principle for          --><!-- linguistic corpora or collections.                       --><!-- say WHAT?  you have got to be kidding.  date and author  --><!-- are passably common as defining criteria for collectns.  --><!-- ... not for corpora they aint  --><!-- ... Brown, LOB, and BNC don't count, I gather?           --><!-- Also topic description is not 'bibliographic desc' but   --><!-- 'subject classification' and not at all the same.        --><!-- Say the professionals.                                   --><!-- well, I spose it depends which professionals you talk to --><!-- it hasn't so far; neither the cataloguers nor the subj   --><!-- classifiers want anything to do with each other.         --></p><p>The core <gi tei="yes">profileDesc</gi> element has three optional components,
represented by the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="CREATN"/><tagDesc tagDoc="LANGUSG"/><tagDesc tagDoc="TEXTCLAS"/></tagList>
These elements are further described in the remainder of this section.</p><p>Three other elements may also appear within the <gi tei="yes">profileDesc</gi>
element, when the
additional tag set for the TEI header is in use:
 
<tagList style="one-line"><tagDesc tagDoc="TEXTDESC"/><tagDesc tagDoc="PARTDESC"/><tagDesc tagDoc="SETTDESC"/></tagList>
 
For descriptions of these elements, see section<xref target="CCAH" type="div1"/>
.</p><p>Finally, the following element can appear in the <gi tei="yes">profileDesc</gi>
element, when the additional tag set for transcription of primary
sources is selected:
 
<tagList style="one-line"><tagDesc tagDoc="HANDLIST"/></tagList>
 
For a description of this element, see section <xref target="PHDH"/>.</p><p>The profile description itself has the following formal definition:
 
<dtdFrag id="D224" n="The profile description"><tagDecl tagDoc="PROFDESC"/><dtdRef dtdFrag="D224C"/><dtdRef dtdFrag="D2241"/><dtdRef dtdFrag="D2243"/></dtdFrag></p><div3 id="HD4C" name="burp" ref="Y"><head>Creation</head><p>The <gi tei="yes">creation</gi> element contains phrases describing the
origin of the text, e.g. the date and place of its composition.
 
<tagList style="one-line"><tagDesc tagDoc="CREATN"/></tagList>
 
The date and place of composition are often of particular importance for
studies of linguistic variation; since such information cannot be
inferred with confidence from the bibliographic description of the copy
text, the <gi tei="yes">creation</gi> element may be used to provide a consistent
location for this information:
 
<eg><![CDATA[ <creation>
    <date value='1992-08'>August 1992</date>
    <rs type=city>Taos, New Mexico</rs>
 </creation>]]></eg></p><p>The formal declaration of <gi tei="yes">creation</gi> is as follows:
<dtdFrag id="D224C" n="Creation"><tagDecl tagDoc="CREATN"/></dtdFrag></p></div3><div3 id="HD41" name="burp" ref="Y"><head>Language Usage</head><p>The <gi tei="yes">langUsage</gi> element is used within the
<gi tei="yes">profileDesc</gi> element to describe the languages, sublanguages,
registers, dialects, etc. represented within a text.  It contains one or
more <gi tei="yes">language</gi> elements, each of which takes attributes
specifying the <term>writing system</term> used (see section<xref target="CH"/>
)<!-- was:  target='P2.21'>) --><!-- or:   target='CH'>) -->
and the quantity of that language present in the text.  Following the
<gi tei="yes">language</gi> elements, prose description may also be added to
specify further relevant information.
 
<tagList style="one-line"><tagDesc tagDoc="LANGUSG"/><tagDesc tagDoc="LANGUAGE" atts="id wsd usage"/></tagList></p><p>Each <gi tei="yes">language</gi> element links the document to the formal
writing system declaration defining that language and its script; for
that reason, its use is recommended.
The <att tei="yes">wsd</att> attribute must give the name of an entity containing a
writing system declaration; typically, this will be an external file
declared in the document type declaration.  For example,
<eg><![CDATA[<!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
  <!ENTITY mhd system 'mhd.wsd'>
  <!ENTITY nhd system 'nhd.wsd'>
]>
<tei.2>
<teiHeader> ...
    <profileDesc>
         <langUsage>
              <language id=GMH wsd=mhd>Middle High German
              <language id=DEU wsd=nhd>Modern standard German
         </langUsage>
     ...
</tei.2>]]></eg></p><p>When two sublanguages share the same language code and writing
system declaration but are distinguished in the <gi tei="yes">langUsage</gi>
element, only one of the <gi tei="yes">language</gi> elements should bear the
<att tei="yes">id</att> attribute:<!-- I'm a bit hazy about the implications of that too: presumably --><!-- all will be made clear in the wsd chapter? --><!-- if not clear here, i doubt it will be clearer then. -msm --><!-- The only implications I see are 1 that nothing in the    --><!-- declarations can point at an individual sublanguage,     --><!-- only to something that has its own WSD, 2 that any       --><!-- processor which cares about identifying languages        --><!-- (wsds) in use must be aware that some LANGUAGE           --><!-- elements don't have IDs, and these must be ignored or    --><!-- 'merged' somehow with LANGUAGE elements which do have    --><!-- IDs and which use the same wsd.  -msm                    -->
 
<eg><![CDATA[<langUsage>
   <language id=FR wsd=wsd.fr usage=60>Qu&eacute;becois
   <language id=EN wsd=wsd.en usage=20>Canadian business English
   <language       wsd=wsd.en usage=20>British English
</langUsage>]]></eg>
 
or, less formally,
 
<eg><![CDATA[   <langUsage>
   <language id=FR wsd=wsd.fr>
   <language id=EN wsd=wsd.en>
     Approximately two-thirds of the text is in
     Qu&eacute;becois, the remainder being equally
     divided between Canadian business English and
     British English.
   </langUsage>]]></eg></p><p>The <gi tei="yes">langUsage</gi> and <gi tei="yes">language</gi> elements have the
following formal definitions:
<dtdFrag id="D2241" n="Language usage"><tagDecl tagDoc="LANGUSG"/><tagDecl tagDoc="LANGUAGE"/></dtdFrag></p></div3><div3 id="HD43" name="burp" ref="Y"><head>The Text Classification</head><p>The second component of the core <gi tei="yes">profileDesc</gi> element is the
<gi tei="yes">textClass</gi> element. This element is used to classify a text
according to one or more of the following methods:
 
<list type="bullets"><item>by reference to a recognized international classification such as
the Dewey Decimal Classification, the Universal Decimal Classification,
the Colon Classification, the Library of Congress Classification, or any
other system widely used in library and documentation work</item><item>by providing a set of keywords, as provided for example by British
Library or Library of Congress Cataloguing in Publication data</item><item>by referencing any other taxonomy of text categories recognized in
the field concerned, or peculiar to the material in hand; this may
include one based on recurring sets of values for the situational
parameters defined in section <xref target="CCAHTD"/>, or the demographic
elements described in section <xref target="CCAHPA"/></item></list>
 
The last of these may be particularly important for dealing with
existing corpora or collections, both as a means of avoiding the expense
or inconvenience of reclassification and as a means of documenting
the organizing principles of such materials.</p><p>The following tags are provided for this purpose:
<tagList style="one-line"><tagDesc tagDoc="KEYWORDS" atts="scheme"/><tagDesc tagDoc="CLASSCOD" atts="scheme"/><tagDesc tagDoc="CATREF" atts="target"/></tagList></p><p>The <gi tei="yes">keywords</gi> element simply categorizes an individual text
by supplying a list of keywords which may describe its topic or subject
matter, its form, date, etc.  In some schemes, the order of items in the
list is significant, for example, from major topic to minor; in others,
the list has an organized substructure of its own.  No recommendations
are made here as to which method is to be preferred.  Wherever possible,
such keywords should be taken from a recognized source, such as the
British Library/Library of Congress Cataloguing in Publication data in
the case of printed books, or a published thesaurus appropriate to the
field.</p><p>The <att tei="yes">scheme</att> attribute should be used to indicate the source
of the keywords used.  This is done by supplying the value used for the
<att tei="yes">id</att> attribute of a <gi tei="yes">taxonomy</gi> element within which
further details of the source concerned may be found.  The
<gi tei="yes">taxonomy</gi> element occurs in the <gi tei="yes">classDecl</gi> part of the
encoding declarations within the TEI Header and is described in section<xref target="HD55"/>
.  For example:
 
<eg><![CDATA[ <keywords scheme=LCSH>
   <list><item>Data base management</item>
         <item>SQL (Computer program language)</item>
   </list>
 </keywords>]]><!-- LC subject tracings on C J Date, A Guide to the SQL      --><!-- Standard 2d ed. (Reading:  Addison-Wesley, 1989), from   --><!-- CIP data on overleaf.                                    --></eg>
<eg><![CDATA[ <keywords scheme=LCSH>
   <list>
   <item>English literature -- History and criticism --
         Data processing.</item>
   <item>English literature -- History and criticism --
         Theory, etc.</item>
   <item>English language -- Style -- Data processing.</item>
   <item>Style, Literary -- Data processing.</item>
   </list>
 </keywords>]]></eg><!-- LC subject tracings on R Potter, ed., Literary           --><!-- Computing and Literary Criticism:  Theoretical and       --><!-- Practical Essays on Theme and Rhetoric (Philadelphia,    --><!-- U Penn, 1989), from CIP data on title overleaf.          --></p><p>The <gi tei="yes">classCode</gi> element also categorizes an individual text,
by supplying a numerical or other code used in a recognized
classification scheme, such as the Dewey Decimal Classification.  The
<att tei="yes">scheme</att> attribute is used to indicate the source of the
classification scheme, in the same way as for the <gi tei="yes">keywords</gi>
element, as in the following example:
 
<eg><![CDATA[ <classCode scheme=DDC19>005.756</>
 <classCode scheme=LC>QA76.9</>]]></eg><!-- subject classifications from Date, Guide to SQL Std      -->
<eg><![CDATA[ <classCode scheme=DDC19>820.285</>
 <classCode scheme=LC>PR21</>]]></eg><!-- subject classifications from Potter, Lit Comp & Lit Crit --></p><p>The <gi tei="yes">catRef</gi> element categorizes an individual text by
pointing to one or more <gi tei="yes">category</gi> elements.  The
<gi tei="yes">category</gi> element (which is fully described in section <xref target="HD55"/>) holds information about a particular classification or
category within a given taxonomy.  Each such category must have a unique
identifier, which may be supplied as the value of the <att tei="yes">target</att>
attribute for <gi tei="yes">catRef</gi> elements which are regarded as falling
within the category indicated.</p><p>A text may, of course, fall into more than one category, in which
case more than one identifier will be supplied as the value for
the <att tei="yes">target</att> attribute on the <gi tei="yes">catRef</gi> element, as
in the following example:
 
<eg><![CDATA[ <catRef target="B1 B2 B5">]]></eg></p><p>Where more than one descriptive taxonomy is used to characterize the
texts in a corpus or collection, the <att tei="yes">scheme</att> attribute
should be supplied to specify the taxonomy to which the categories
identified by the target attribute belong. For example,
 
<eg><![CDATA[ <catRef scheme='Brown' target='B12 B15'>
 <catRef scheme='SUC' target='A45'>]]></eg>
 
Here the same text has been classified as of categories <q>B12</q> and
<q>B15</q> within the Brown classification scheme, and as of category
<q>A45</q> within the SUC classification scheme.</p><p>The distinction between the <gi tei="yes">catRef</gi> and <gi tei="yes">classCode</gi>
elements is that the values used as identifying codes <emph>must </emph>
be defined somewhere within the header for the former, but not the
latter.</p><p>The elements described in this section have the following formal
definitions:
<dtdFrag id="D2243" n="Text Classification"><tagDecl tagDoc="TEXTCLAS"/><tagDecl tagDoc="KEYWORDS"/><tagDecl tagDoc="CLASSCOD"/><tagDecl tagDoc="CATREF"/></dtdFrag></p></div3></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2hd4.odd ??><?tei:SOF p2hd6.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd6.odd,v $
# Revision 1.5  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
#
# Revision 1.4  1994/01/04  13:02:04  lou
# change resp to respstmt
#
# Revision 1.3  1993/08/18  21:31:24  msmcq
# name shift (role/resp, resp/respStmt) on account of DR role
#
# Revision 1.2  1993/06/22  14:29:49  msmcq
# Changes post Eynsham and for DTD generation
# --><!-- Revisions:                                               --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!-- 93-08-18 : MSM : new names for respStmt, role/resp       --><!-- 93-06-01 : MSM : change change log post Eynsham          --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-17 : MSM : change BY to NAME                       --><!-- 25 Jul 92 : MSM : names updated, ids updated             --><div2 id="HD6" name="bar" ref="Y"><head>The Revision Description</head><p>The final subelement of the TEI header, the <gi tei="yes">revisionDesc</gi>
element, provides a detailed change log in which each change made to a
text may be recorded.  Its use is optional but highly recommended.
It provides essential information for the administration of large
numbers of files which are being updated, corrected, or otherwise
modified as well as extremely useful documentation for files being
passed from researcher to researcher or system to system. Without
change logs, it is easy to confuse different versions of a file, or to
remain unaware of small but important changes made in the file by some
earlier link in the chain of distribution.  No change should be made in
any TEI-conformant file without corresponding entries being made in the
change log.

<tagList style="one-line"><tagDesc tagDoc="REVDESC"/><tagDesc tagDoc="CHANGE"/></tagList>
</p><p>The log consists of a list of entries, one for each change.  This
may be encoded using either the regular <gi tei="yes">list</gi> element,
as described in section <xref target="COLI"/> or as a series of<!-- was:  target='P2.233'> --><!-- or :  target='COLIST'> -->
special purpose <gi tei="yes">change</gi> elements, each of which has
the following constituents:
<tagList style="one-line"><tagDesc tagDoc="DATE"/><tagDesc tagDoc="RESP"/><tagDesc tagDoc="ITEM"/></tagList>
The <gi tei="yes">date</gi> element indicates the date of the change.
The <gi tei="yes">respStmt</gi> element indicates who made the change, and in what
role.
The <gi tei="yes">item</gi> element indicates what change was made; it can
range from a simple phrase to a series of paragraphs.
If a number is to be associated with one or more changes (for
example, a revision number), use the global <att tei="yes">n</att>
attribute on the <gi tei="yes">change</gi> element to supply it.
</p><p>It is recommended to give changes in reverse chronological order,
most recent first.
<!-- if i had time i'd replace by, what, date with            --><!-- name, date, item.  perhaps in p3.  -msm                  --><!-- i agree that BY could usefully be replaced by NAME. Less clear --><!-- about ITEM, since this is already implied by use of LIST -lb --></p><p>For example:<!-- is this example perhaps not a bit over long? --><!-- possibly, i just took a real one from a file -->
<eg><![CDATA[<revisionDesc>
<change><date>6/3/91:</date>
        <respStmt><name>EMB</name><resp>ed.</></respStmt>
        <item> < > changes completed.</item>
<change><date>5/25/91:</date>
        <respStmt><name>EMB</name><resp>ed.</></respStmt>
        <item>File format updated.</item>
<change><date>9/3/90:</date>
        <respStmt><name>EMB</name><resp>ed.</></respStmt>
        <item>Changes to make a prettier printed version.</item>
<change><date>5/25/90:</date>
        <respStmt><name>EMB</name><resp>ed.</></respStmt>
        <item>Stuart's corrections entered</item>
<change><date>2/90: </date>
        <respStmt><name>N.N.</name><resp>admin.</></respStmt>
        <item>Sent to Stuart Curran for proofreading.</item>
<change><date>1/22/90:</date>
        <respStmt><name>N.N.</name><resp>data entry</></respStmt>
        <item>Corrections made to file;</item>
<change><date>10/89:</date>
        <respStmt><name>John G. Fitzgerald, Julia M. Deisler
            and Deborah Hirsch.</name><resp>staff</></respStmt>
        <item>Proofread.</item>
<change><date>8/89:</date>
        <respStmt><name>Amy E. Frisch</><resp>data entry</></respStmt>
        <item>Input begun</item>
</revisionDesc>]]></eg>
</p><p>The formal definition of the <gi tei="yes">revisionDesc</gi> element is thus as
follows:

<dtdFrag id="D226" n="The Revision Description" file="teihdr2"><tagDecl tagDoc="REVDESC"/><tagDecl tagDoc="CHANGE"/><commDecl>respStmt, item, and date are declared in teicore2.</commDecl></dtdFrag><?tei:EOF p2hd6.odd ??>
<?tei:SOF p2hd7.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd7.odd,v $
# Revision 1.5  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.4  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.3  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
# --><!-- Revisions:                                               --><!-- 10 jan 98 : LB : correcting egs --><!-- 94-04-08 : MSM : change id of ref sectino                --><!-- 94-03-29 : MSM : change CITY to pubPlace                 --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!-- 93-08-18 : MSM : new names for respStmt, role/resp       --><!-- 93-06-01 : MSM : normalize teiHeader, citn               --><!-- 93-02-10 : MSM : update xref targets                     --><!-- 92-08-19 : MSM : correct error in long example           --><!-- 92-08-19 : MSM : modify full header example              --><!-- 92-08-18 : MSM : check ]]                                --><!-- 92-08-17 : MSM : major additions to recommended hdr      --><!-- 3 Aug 92 : LB : one or two trivial changes               --><!-- 25 Jul 92 : MSM : names updated, ids updated             --></p></div2><div2 id="HD7" name="bar" ref="Y"><head>Minimal and Recommended Headers
 </head><p>The TEI header allows for the provision of a very large amount of
information concerning the text itself, its source, encodings
and revisions of it, as well as a wealth of descriptive information
such as the languages it uses and the situation within which it
was produced, the setting and identity of participants within it.
This diversity and richness reflects the diversity of uses to which
it is envisaged that electronic texts conforming to these Guidelines
will be put. It is emphatically <emph>not</emph> intended that all of the
elements described above should be present in every TEI Header.
 </p><p>The amount of encoding in a header will depend both on the nature
and the intended use of the text. At one extreme, an encoder may
expect that the header will be needed only to provide a bibliographic
identification of the text adequate to local needs. At the other,
wishing to ensure that their texts can be used for the widest
range of applications, encoders will want to document as explicitly as
possible both bibliographic and descriptive information, in such a
way that no prior or ancillary knowledge about the text is needed
in order to process it. The header in such a case will be very
full, approximating to the kind of documentation often supplied
in the form of a manual. Most texts will lie somewhere between
these extremes; textual corpora in particular will tend more
to the latter extreme.
 </p><p>For each element discussed above, an indication is given in the
general alphabetical index (section <xref target="P2REFS"/>) as to whether
its encoding is regarded in general as required, recommended or
optional.  Clearly, all elements relating to descriptive matters such as
text classification or description must be optional in the general case,
though for certain kinds of analysis their presence will be mandatory.
This section therefore confines itself to demonstrating the minimal and
recommended levels of encoding of the bibliographic information held by
the TEI header.
 </p><p>Supplying only the minimal level of encoding required, the
TEI header of a single printed text might look like the following
example:
 
<eg><![CDATA[<teiHeader>
  <fileDesc>
    <titleStmt>
        <title>Thomas Paine: Common sense, a
            machine-readable transcript</title>
        <respStmt><resp>compiled by</resp>
             <name>Jon K Adams</name>
        </respStmt>
     </titleStmt>
     <publicationStmt>
        <distributor>Oxford Text Archive</distributor>
     </publicationStmt>
     <sourceDesc>
        <bibl>The complete writings of Thomas Paine,
           collected and edited by Phillip S. Foner
           (New York, Citadel Press, 1945)
        </bibl>
      </sourceDesc>
   </fileDesc>
</teiHeader>]]></eg>
 </p><p>The only mandatory component of the TEI Header is the
<gi tei="yes">fileDesc</gi> element.  Within this, <gi tei="yes">titleStmt</gi>,
<gi tei="yes">publicationStmt</gi> and <gi tei="yes">sourceDesc</gi> are all required
constituents.  Within the title statement, a title is required, and an
author should be specified, even if it is <code tei="yes" type="frag">unknown</code>, as
should some additional statement of responsibility, here given by the
<gi tei="yes">respStmt</gi> element.  Within the <gi tei="yes">publicationStmt</gi>, a
publisher, distributor or other agency responsible for the file must be
specified.  Finally, the source description should contain at the least
a loosely structured bibliographic citation identifying the source of
the electronic text if (as is usually the case) there is one.
 </p><p>We now present the same example header, expanded to include
additionally recommended information, adequate to most bibliographic
purposes, in particular to allow for the creation of an AACR2-conformant
bibliographic record.  We have also added information about the
encoding principles used in this (imaginary) encoding, about the
text itself (in the form of Library of Congress subject headings),
and about the revision of the file.
 <!-- Bibliographic reference to a real OTA text.              --><!-- EncodingDesc mostly from description of                  --><!-- that text, but improvised in part.                       --><!-- Revision desc is imaginary                               -->
<eg><![CDATA[<teiHeader>
<fileDesc>
    <titleStmt>
         <title>Common sense, a machine-readable transcript</title>
         <author>Paine, Thomas (1737-1809)</author>
         <respStmt><resp>compiled by</resp>
               <name>Jon K Adams</name>
         </respStmt>
    </titleStmt>
    <editionStmt>
         <edition><date>1986</date></edition>
    </editionStmt>
    <publicationStmt>
         <distributor>Oxford Text Archive.</distributor>
         <address><addrLine>Oxford University Computing Services,</addrLine>
             <addrLine>13 Banbury Road,</addrLine> 
             <addrLine>Oxford OX2 6RB,</addrLine> 
              <addrLine>UK</addrLine>
         </address>
    </publicationStmt>
    <notesStmt>
         <note>Brief notes on the text are in a
               supplementary file.</note>
    </notesStmt>
    <sourceDesc>
         <biblStruct>
         <monogr><editor>Foner, Philip S.</editor>
              <title>The collected writings of Thomas Paine</title>
              <imprint>
                   <pubPlace>New York</pubPlace>
                   <publisher>Citadel Press</publisher>
                   <date>1945</date>
              </imprint>
         </monogr></biblStruct>
    </sourceDesc>
</fileDesc>
<encodingDesc>
    <samplingDecl><p>Editorial notes in the Foner edition have not
         been reproduced.
         <p>Blank lines and multiple blank spaces, including paragraph
         indents, have not been preserved.
    <editorialDecl>
         <correction status=high method=silent><p>The following errors
              in the Foner edition have been corrected:
              <list>
              <item>p.  13 l.  7 cotemporaries   contemporaries
              <item>p.  28 l. 26 [comma]         [period]
              <item>p.  84 l.  4 kin             kind
              <item>p.  95 l.  1 stuggle         struggle
              <item>p. 101 l.  4 certainy        certainty
              <item>p. 167 l.  6 than            that
              <item>p. 209 l. 24 publshed        published
              </list>
         <normalization><p>No normalization beyond that performed
              by Foner, if any.
         <quotation marks=all form=std><p>All double quotation marks
              rendered with ", all single quotation marks with
              apostrophe.
         <hyphenation eol=none><p>Hyphenated words that appear at the
              end of the line in the Foner edition have been reformed.
         <stdVals><p>Standard date values are given in ISO form:
              yyyy-mm-dd.
         <interpretation><p>Compound proper names are marked.
              <p>Dates are marked.
              <p>Italics are recorded without interpretation.
    </editorialDecl>
    <classDecl>
         <taxonomy id='LCSH'>
              <bibl>Library of Congress Subject Headings</></>
         <taxonomy id='LC'>
              <bibl>Library of Congress Classification</></>
    </classDecl>
</encodingDesc>
<profileDesc>
    <creation><date>1774</date></creation>
    <langUsage>
         <language id=EN wsd='english' usage=100>English.</language>
    </langUsage>
    <textClass>
         <keywords scheme='LCSH'>
              <list>
                   <item>Political science</item>
                   <item>United States -- Politics and government --
                         Revolution, 1775-1783</item>
              </list>
         </keywords>
         <classCode scheme='LC'>JC 177</>
    </textClass>
</profileDesc>
<revisionDesc>
<change><date>1996-01-22</date>
    <respStmt><resp>ed</resp><name>CMSMcQ</name></respStmt>
    <item>finished proofreading</item>
</change>
<change><date>1995-10-30</date>
    <respStmt><resp>ed</resp><name>L.B. </name></respStmt>
    <item>finished proofreading</item>
</change>
<change><date>1995-07-20</date>
    <respStmt><resp>ed</resp><name>R.G. </name></respStmt>
    <item>finished proofreading</item>
</change>
<change><date>1995-07-04</date>
    <respStmt><resp>ed</resp><name>R.G. </name></respStmt>
    <item>finished data entry</item>
</change>
<change><date>1995-01-15</date>
     <respStmt><resp>ed</resp><name>R.G. </name></respStmt>
     <item>began data entry</item>
</change>
</revisionDesc>
</teiHeader>]]></eg>
 <!-- this is what Rich suggested: me, I think the  --><!-- contents of the supplementary file should be  --><!-- decanted into the encodingDesc  (LB)          --><!-- Do we agree that this really is an acceptable --><!-- minimal recommendation?                       --><!-- Not at all:  it ought to have encodingDesc,   --><!-- profileDesc, and revisionDesc too.            --><!-- Which I have now added.  -msm                 -->
 </p><p>Many other examples of recommended usage for the elements discussed
in this chapter are provided here, in the reference index and in the
associated tutorials.
 <?tei:EOF p2hd7.odd ??>
<?tei:SOF p2hd8.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2hd8.odd,v $
# Revision 1.2  1994/03/24  22:14:56  msmcq
# typo corrections from David Barnard, Peter Robinson, and others
# --><!-- P2HD8 : Note for cataloguers                             --><!-- Revisions:                                               --><!-- 94-03-22 : CMSMcQ : typos, TEI - &tei, code, ident tags  --><!-- 25 Jul 92 : CMSMcQ : separated from p2.226               --><!-- 25 Jul 92 : MSM : names updated, ids updated             -->
</p></div2><div2 id="HD8" name="bar" ref="Y"><head>Note for Library Cataloguers</head><!-- was id='P2.228' --><p>A strong motivation in preparing the material in this chapter was to
provide in the TEI file header a viable chief source of information
for cataloguing the machine-readable data file.  The file header is not
a library catalogue record, and so will not make all of the distinctions
essential in standard library work.  It also includes much information
generally excluded from standard bibliographic descriptions.  It is the
intention of the developers, however, to ensure that the information
required for a catalogue record be retrievable from the TEI file
header, and moreover that the mapping from the one to the other be as
simple and straightforward as possible.  Where the correspondence is not
obvious, it may prove useful to consult one of the works which were
influential in developing the content of the TEI file header.  These
include:

<list type="gloss"><label>ISBD(G) </label><item>The International Standard Book Description
(General) is an international standard setting out what information
should be recorded in a description of a bibliographical item.  There
are also separate ISBDs covering different types of material, e.g.
ISBD(M) for monographs, ISBD(CF) for computer files.  These separate
ISBDs follow the same general scheme as the main ISBD(G), but provide
appropriate interpretations for the specific materials under
consideration.
</item><label>AACR2 </label><item>The Anglo-American Cataloguing Rules (second edition)
were published in 1978, with a revision appearing in 1988.  The AACR2
provides guidelines for the construction of catalogues in general
libraries.  AACR2 is explicitly based on the general framework of the
ISBD(G), and the subsidiary ISBDs.  It gives a description of how to
catalogue items according to the ISBDs, and how to construct indexes and
catalogue cross references.
</item><label>ANSI Z.39.29 </label><item>ANSI Z.39.29 is an American national standard
governing bibliographic references for use in bibliographies,
end-of-work lists, references in abstracting and indexing publications,
and outputs from computerized bibliographic data bases.  This standard
has however now been withdrawn, pending substantial revision.  The
international standard which covers the same area is ISO 690:  1987.
Other relevant standards include BS 1629:  1989, BS 5605:  1978, and BS
6371:1983.
</item></list><?tei:EOF p2hd8.odd ??>
<!-- &p2.hdt1; &p2.hdt2; &p2.hdt3; &p2.hdt4;                  --><!-- &hdtags; --><?tei:EOF p2hd.odd ??>
            <!-- 5 The TEI Header --><?tei:SOF p2co.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2co.odd,v $
    * Revision 1.8  1998/01/30 16:38:43  tei
    * fix Log keyword.
    *
    * Revision 1.7  1994/03/27 21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * 
    * Revision 1.6  1994/03/01  03:53:06  msmcq
    * suppress decls of pointer, xpointer :  these are now
    * att classes only, not model classes.  Add clloc decl.
    *--><!-- P2 chapter 23:  Tags Available in All TEI DTDs           --><!-- (id=p2.23, file=P223, mixed)                             --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 94-03-24 : MSM : typos, etc. from the proofreading team  --><!--                  suppress class decls, etc.:  these are  --><!--                  done in teiclas2.ent, and doing them    --><!--                  again in teicore2.dtd is only confusing --><!-- 94-02-28 : MSM : suppress pointer as *model* class       --><!-- 94-02-25 : MSM : suppress xpointer class for now         --><!-- 94-02-25 : MSM : Added RCS id                            --><!-- 93-12-20 : LDB : seg class has id clseg not seg          --><!-- 93-02-11 : MSM : loc class has id clloc not loc          --><!-- 92-12-10 : MSM : correct cladecl:  clbibl, not bibl      --><!-- 92-12-10 : MSM : revamp toplevel dtd frags               --><!-- 92-12-09 : MSM : touchup for publication                 --><!-- 92-12-06 : MSM : comment comi out                        --><!-- 92-12-06 : MSM : minor changes to text                   --><!-- 92-12-06 : MSM : exclude concurrent dtd from dtd         --><!-- 92-11-09 : MSM : set N on DIV                            --><!--                  add references to subparts              --><!--                  remove leading spaces in P elements     --><!-- 18-19 Oct 92 : LB :  revised slightly                    --><!--                      reordered pace Chicago  TRC         --><!-- 26 May 92 : CMSMcQ : add p2.23tag (LB ref crystals)      --><!-- 24 Apr 92 : CMSMcQ : add 23.e                            --><!-- 21 Apr 92 : CMSMcQ : made this file                      --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->
 <!-- changed name : Documents not dtds(LB) --><!-- changed name : elements not tags (LB) -->
 </p></div2></div1><div1 id="CO" n="6" name="Chapter" ref="Y"><head>Elements Available in All TEI Documents</head><p>This chapter describes elements which may appear in any kind of text
and the tags used to mark them in all TEI documents.  Most of these
elements are freely floating phrases, which can appear at any point
within the textual structure, although they must generally be contained
by a higher-level element of some kind (such as a paragraph).  A few of
the elements described in this chapter (for example, bibliographic
citations and lists) have a comparatively well-defined internal
structure, but most of them have no consistent inner structure of their
own.  In the general case, they contain only a few words, and are often
identifiable in a conventionally printed text by the use of typographic
conventions such as shifts of font, use of quotation or other
punctuation marks, or other changes in layout.
 </p><p>To use the terminology introduced in section <xref target="STECOV"/>,
most of the elements described in this chapter are members of the class
<ident tei="yes" type="class">phrase</ident>, and a small number are members of the
classes <ident tei="yes" type="class">chunk</ident> or
<ident tei="yes" type="class">inter</ident>.
 </p><p>This chapter begins by describing the <gi tei="yes">p</gi> tag used to mark
paragraphs, which serve as the fundamental formal unit for running text
in many base tag sets, and are available in all.  This is followed, in
section <xref target="COPU"/>, by a discussion of some specific problems
associated with the interpretation of conventional punctuation, and the
methods proposed by the current Guidelines for resolving ambiguities
therein.
 </p><p>The next section (section <xref target="COHQ"/>) describes a number of
phrase-level elements commonly marked by typographic features (and thus
well-represented in conventional markup languages).  These include
features commonly marked by font shifts (section <xref target="COHQH"/>) and features commonly marked by quotation marks (section<xref target="COHQQ"/>
) as well as such features as terms, cited
words, and glosses (section <xref target="COHQU"/>).
 </p><p>The next section (section <xref target="CONA"/>) describes several
phrase-level and inter-level elements which, although often of interest
for analysis or processing, are rarely explicitly identified in
conventional printing.  These include names (section <xref target="CONARS" type="div2"/>), numbers and measures (section <xref target="CONANU" type="div2"/>), dates and times (section <xref target="CONADA" type="div2"/>), abbreviations (section <xref target="CONAAB" type="div2"/>),
and addresses (section <xref target="CONAAD"/>).
 </p><p>Section <xref target="COED"/> introduces some phrase-level elements
which may be used to record simple editorial emendation or correction of
the encoded text.  The tags described here constitute a simple subset of
the full mechanisms for encoding such information (described in full in
chapter <xref target="PH"/>), which should be adequate to most commonly
encountered situations.
 <!-- changed target from TC to PH -->
 </p><p>In the same way, the following section (section <xref target="COXR"/>)
presents only a subset of the facilities available for the encoding
of cross-references or text-linkage.  The full story may be found in
chapter <xref target="SA"/>; the tags presented here are intended to
be usable for a wide variety of simple applications.
 </p><p>Sections <xref target="COLI"/>, and <xref target="CONO"/>, describe two
kinds of quasi-structural elements, lists and notes, which may appear
either within chunk-level elements such as paragraphs, or between them.
Several kinds of lists are catered for, of an arbitrary complexity.  The
section on notes discusses both notes found in the source and simple
mechanisms for adding annotations of an interpretive nature during
the encoding; again, only a subset of the facilities described in full
elsewhere (specifically, in chapter <xref target="AI"/>) is discussed.
 </p><p>Next, section <xref target="CORS" type="div2"/>, describes methods of
encoding within a text the conventional system or systems used when
making references to the text.  Some reference systems have attained
canonical authority and must be recorded to make the text useable in
normal work; in other cases, a convenient reference system must be
created by the creator or analyst of an electronic text.
 </p><p>Like lists and notes, the bibliographic citations discussed in
section <xref target="COBI"/>, may be regarded as structural elements in
their own right.  A range of possibilities is presented for the encoding
of bibliographic citations or references, which may be treated as
simple phrases within a running text, or as highly-structured
components suitable for inclusion in a bibliographic database.
 </p><p>Additional elements for the encoding of passages of verse or drama
(whether prose or verse) are discussed in section <xref target="CODV"/>.
 <!-- , and a simple method of segmenting any kind of text     --><!-- into <soCalled>orthographic sentences</soCalled> is      --><!-- discussed in section <xref target=COSE>.                 -->
 </p><p>The chapter concludes with a technical overview of the structure and
organization of the tag set described here. This should be read in
conjunction with chapter <xref target="ST"/>, describing the structure of
the TEI document type definition.
 <!-- moved overview of tagset structure to end of chapter -->
 
 <!-- COpa Paragraphs (P1 5.3.1)                               --><?tei:SOF p2copa.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2copa.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# --><!-- P2COpa : Paragraphs                                      --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-25 : MSM : corrections from John Lavagnino         --><!-- 94-03-24 : MSM : disambiguation of term, q (null)        --><!-- 92-12-09 : MSM : cosmetic copy editing                   --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-06 : MSM : revisions for publication               --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 17 oct 92 : LB  revised initial discussion               --><!-- 2 oct 92  : LB checked; revised order slightly           --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->
 </p><div2 id="COPA" name="section" ref="Y"><head>Paragraphs</head><p>The paragraph is the fundamental organizational unit for all prose
texts, being the smallest regular unit into which prose can be divided.
Prose can appear in all TEI texts, not simply in those using the prose
base (section <xref target="PR"/>); the paragraph is therefore described
here, as an element which can appear in any kind of text.
 </p><p>Paragraphs can contain any of the other elements described within
this chapter, as well as some other elements which are specific to
individual text types.  We distinguish <term>phrase-level</term>
elements, which must be entirely contained within a paragraph and cannot
appear except within one, from <term>chunks</term>, which can appear
between, but not within, paragraphs, and from <term>inter-level</term>
elements, which can appear either within a single paragraph or between
paragraphs.  The class of phrases includes emphasized or quoted phrases,
names, dates, etc.  The class of inter-level elements includes
bibliographic citations, notes, lists, etc.  The class of chunks
includes the paragraph itself.
 </p><p>Because paragraphs may appear in different base or additional tag
sets, their possible contents may differ in different kinds of
documents.  In particular, additional elements not listed in this
chapter may appear in paragraphs in certain kinds of text.  However, the
elements described in this chapter are always by default available in
all kinds of text.
 </p><p>The paragraph is marked using the <gi tei="yes">p</gi> element:
 
<tagList style="one-line"><tagDesc tagDoc="P"/></tagList>
 </p><p>If a consistent internal subdivision of paragraphs is desired, the
<gi tei="yes">s</gi> or <gi tei="yes">seg</gi> (<soCalled>segment</soCalled>) elements may
be used, as discussed in chapters <xref target="SA"/> and <xref target="AI"/>
respectively.  More usually, however, paragraphs have no firm internal
structure, but contain prose encoded as a mix of characters, entity
references, phrases marked as described in the rest of this chapter, and
embedded elements like lists, figures, or tables.
 </p><p>Since paragraphs are usually explicitly marked in Western texts,
typically by indentation,  the application of the <gi tei="yes">p</gi> tag
usually presents few problems.
 </p><p>In some cases, the body of a text may comprise but a single
paragraph:
 
<eg><![CDATA[<body>
<p>I fully appreciate Gen. Pope's splendid achievements with their
invaluable results; but you must know that Major Generalships in the
Regular Army, are not as plenty as blackberries.
</body>]]></eg>
 <!-- A. Lincoln to Richard Yates and William Butler, 10 Apr 1862, --><!-- Library of America, Lincoln, v. 2 p. 315.                -->
 </p><p>This news story shows typically short journalistic paragraphs:
 
<eg><![CDATA[<head>SARAJEVO, Bosnia and Herzegovina, April 19</head>
<p>Serbs seized more territory in this struggling new
country today as the United States Air Force ended a
two-day airlift of humanitarian aid into the capital,
Sarajevo.
<p>International relief workers called on European
Community nations to step up their humanitarian aid to
the former Yugoslav republic, in conjunction with new
American aid flights if necessary.
<p>A special envoy from the European Community, Colin
Doyle, harshly condemned the decision by Serbs to shell
Sarajevo on Saturday night during a visit to the Bosnian
capital by a senior American official, Deputy Assistant
Secretary of State Ralph R. Johnson.
<p>...]]></eg>
 </p><p>The following extract from a Russian fairy tale demonstrates
how other phrase level elements (in this case <gi tei="yes">q</gi> elements
representing direct speech; see section <xref target="COHQQ"/>)
may be nested within, but not across, paragraphs:
 <!-- < citation>< title>Russian Fairy Tales,< /title>         --><!-- translated by Norbert Guterman from the collections of   --><!-- Aleksandr Afanas'ev, illustrations by Alexander          --><!-- Alexeieff, folkloristic commentary by Roman Jakobson     --><!-- (New York:  Pantheon Books, 1947, rpt.  [n.d.]).< />     --><!-- opening paragraphs of < title.p>The Castle of the        --><!-- Fly< /title.p>, p. 25                                    -->
 <!-- WWP proofer objects to the fact that "I, the             --><!-- Languishing Fly, and I the Crawling Louse" makes only    --><!-- one Q element instead of two.  Though not perfectly      --><!-- logical, this is the structure indicated by the          --><!-- punctuation of the source text, so the example was not   --><!-- changed.  (msm)                                          -->
 
<eg><![CDATA[<p>A fly built a castle, a tall and mighty castle.
There came to the castle the Crawling Louse.  <q>Who,
who's in the castle?  Who, who's in your house?</q>
said the Crawling Louse.  <q>I, I, the Languishing Fly.
And who art thou?</q> <q>I'm the Crawling Louse.</q>
 
<p>Then came to the castle the Leaping Flea.  <q>Who,
who's in the castle?</q> said the Leaping Flea.  <q>I,
I, the Languishing Fly, and I, the Crawling Louse.  And
who art thou?</q> <q>I'm the Leaping Flea.</q>
 
<p>Then came to the castle the Mischievous Mosquito.
<q>Who, who's in the castle?</q> said the Mischievous
Mosquito.  <q>I, I, the Languishing Fly, and I, the
Crawling Louse, and I, the Leaping Flea.  And who art
thou?</q> <q>I'm the Mischievous Mosquito.</q>]]></eg>
 </p><p>The <gi tei="yes">p</gi> element is formally declared as follows:
<dtdFrag id="DCOPA" n="Paragraph"><tagDecl tagDoc="P"/></dtdFrag>
 <?tei:EOF p2copa.odd ??>

 <!-- COpu Ambiguous Punctuation                               --><?tei:SOF p2copu.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2copu.odd,v $
# Revision 1.4  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-26 : MSM : corrections from DB                     --><!-- 94-03-25 : MSM : corrections from JL                     --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 14 mar 94 : change ref to AIse to point to SAse --><!-- 2 jan 94: LB: change title following DTL, provide hook for PAREN --><!-- 92-12-09 : MSM : cosmetic copy editing                   --><!-- 92-12-09 : MSM : bring remark about SHY into text        --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-09 : MSM : add reference to teipunc2               --><!-- 92-12-06 : MSM : correct typo                            --><!-- 92-12-06 : MSM : revise for publication                  --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 5 Oct 92  : LB made new file from old P223d; redo IDs   -->
 </p></div2><div2 id="COPU" name="section" ref="Y"><head>Treatment of Punctuation</head><p>Punctuation marks cause problems for text markup because they may
not be available in the character set used and because they are often
ambiguous.  In the former case entity names should be used to render
the punctuation mark (see <xref target="CH" type="div1"/>).  In the latter
case, ambiguous punctuation may be treated as described below.
 </p><p><term rend="noindex">Full stop (period)</term><indexed level1="full stop" level2="functions"/><indexed level1="period" level2="functions"/>
may mark (orthographic) sentence boundaries, abbreviations, decimal
points, or serve as a visual aid in printing numbers.  These usages can
be distinguished by tagging S-units, abbreviations, and numbers, as
described in sections <xref target="SASE"/>, <xref target="CONAAB"/>, and<xref target="CONANU"/>
.  There are independent reasons for tagging these,
whether or not they are marked by full stops.  Alternatively, the
following TEI-specific entity names may be used to distinguish stops
(and other characters) used for these purposes:
 
<list type="gloss"><label>stop.abbr </label><item>a stop used to end an abbreviation</item><label>stop.sent </label><item>a stop used to end a sentence</item><label>stop.abse </label><item>a stop used both to end an abbreviation
                        and to end a sentence</item><label>stop.dec  </label><item>a stop used as a decimal point</item><label>comma.dec </label><item>a comma used as a decimal point</item><label>middot.dec </label><item>a midline dot used as a decimal point</item><label>stop.space </label><item>a stop used as a numeric space character</item><label>comma.space </label><item>a comma used as a numeric space character</item></list>
 
These entities are defined in the file <ident tei="yes" type="file">teipunc2</ident>, which is documented in chapter <xref target="XW"/>.
 </p><p><term rend="noindex">Question mark</term><indexed level1="question mark" level2="functions"/>
and <term rend="noindex">exclamation mark</term><indexed level1="exclamation mark" level2="functions"/>
typically mark the end of orthographic sentences, but may also be used
as a mid-sentence comment by the author (<cited>!</cited> to express
surprise or some other strong feeling, <cited>?</cited> to query a word
or expression or mark a sentence as dubious in linguistic discussion).
These uses may be distinguished by marking S-units, in which case the
mid-sentence uses of these punctuation marks may be left unmarked.
 </p><p><term rend="noindex">Hyphens</term><indexed level1="hyphen" level2="functions"/><indexed level1="hyphen" level2="soft and hard"/>
 
at line-end may or may not indicate permanent
(<soCalled>hard</soCalled>) hyphens in the word.  Where the lineation of
the machine-readable text differs from the original, the editor may
eliminate soft (line-end) hyphens or replace them by a reference to the
entity <ident tei="yes" type="ge">shy</ident> (<soCalled>soft hyphen</soCalled>),
which is defined in the standard public entity set <ident tei="yes" type="entset">ISOnum</ident> defined in ISO 8879 (which should be
invoked in the DTD subset
if the entity <ident tei="yes" type="ge">shy</ident> is to be used).  The solution
chosen should be reported in the <tag compl="full" tei="yes">hyphenation</tag> tag of the
encoding declarations in the TEI header.  See chapter <xref target="HD" type="div1"/> for discussion of the TEI header and encoding declarations.
 </p><p>Creators of machine-readable texts are recommended to avoid soft
hyphens, as one cannot tell whether the hyphens are soft or hard in the
case of compounds or prefixed words which might or might not be
hyphenated in mid-sentence.
 </p><p><term rend="noindex">Dashes</term><indexed level1="dash" level2="functions"/>
are best distinguished in form by using the entity names provided in the
public entity set <ident tei="yes" type="entset">ISOpub</ident>, defined in ISO
8879:  <ident tei="yes" type="ge">mdash</ident>, <ident tei="yes" type="ge">ndash</ident>, and
<ident tei="yes" type="ge">dash</ident> (the <soCalled>true</soCalled> hyphen).
Dashes are used for a variety of purposes:  insertion, interruption, new
speaker (in dialogue), list item.  In the latter two cases it is
preferable to mark the underlying feature using the elements
<tag compl="full" tei="yes">q</tag> or <tag compl="full" tei="yes">item</tag>, on which see section <xref target="COHQQ" type="div2"/>, and section <xref target="COLI" type="div2"/>, respectively.
 </p><p><term rend="noindex">Quotation marks</term><indexed level1="quotation marks" level2="functions"/>
should generally be replaced by the tags <tag compl="full" tei="yes">q</tag> or
<tag compl="full" tei="yes">quote</tag>, especially as quotations are not always marked by
quotation marks (notably long quotations) or may be marked in a variety
of ways; see the discussion of quotation and related features in section<xref target="COHQQ" type="div1"/>
.
 </p><p><term rend="noindex">Apostrophes</term><indexed level1="apostrophe" level2="functions"/>
must be distinguished from single quote marks.  This is best done by
tagging quotations or other uses of quotation marks (see above).
However, apostrophes have a variety of uses.  In English they mark
contractions, genitive forms, and (occasionally) plural forms.  Full
disambiguation of these uses belongs to the level of linguistic analysis
and interpretation.
 </p><p><term rend="noindex">Parentheses</term><indexed level1="parentheses" level2="functions"/>
and other marks of suspension such as dashes or ellipses are often used
to signal information about the syntactic structure of a text fragment.
Full disambiguation of their uses also belongs to the level of
linguistic analysis and interpretation, and is therefore discussed in
chapter <xref target="AI"/>.
 <!-- could point to paren element here? -->
 </p><p>Where punctuation marks are disambiguated by tagging the underlying
feature they signal, it may be debated whether they should be excluded
or left as part of the text.  In the case of quotation marks, it may
sometimes be more convenient to distinguish opening from closing marks
simply by using the appropriate entity reference, rather than using the
<gi tei="yes">q</gi> element, with or without a <att tei="yes">rend</att> attribute.  The
solution chosen will vary depending upon the feature and depending upon
the purpose of the project.
 <?tei:EOF p2copu.odd ??>

 <!-- COhq Highlighting and Related Features (P1 5.3.2,5.3.4)  --><?tei:SOF p2cohq.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2cohq.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# -->
 </p></div2><div2 id="COHQ" name="section" ref="Y"><head>Highlighting and Quotation</head><!-- Revisions:                                               --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-26 : MSM : corrections from DB                     --><!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 92-12-10 : MSM : change xref to SP (now TS)              --><!-- 92-12-09 : MSM : retag new citn using toy tag, not new tag --><!-- 92-12-09 : MSM : spellcheck for publication              --><!-- 92-12-09 : MSM : touchups for publication                --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-09 : MSM : fixes as per LB, MSM agreements         --><!-- 92-12-07 : MSM : suppress Q/Free attribute               --><!-- 92-12-07 : MSM : correct syntax error in OED gloss       --><!-- 92-12-07 : MSM : come down handsomely with OED citation  --><!-- 92-12-06 : MSM : revise for publication                  --><!-- 92-11-09 : MSM : retag two EGs as Qs                     --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 25-7 Oct  LB : introduce quote, reorder                  --><!-- 19 Oct 92 LB : change ids to match EDW23                 --><!--           changed marked to distinct                     --><!-- 26 May 92 : MSM : fix div levels                         --><!-- 15 May 92 : LB : finish, check out to MSM                --><p>This section deals with a variety of textual features, all of
which have in common that they are frequently realized in conventional
printing practice by the use of such features as underlining, italic
fonts, or quotation marks, collectively referred to here as
<term>highlighting</term>.  After an initial discussion of this
phenomenon and alternate approaches to encoding it, this section
describes ways of encoding the following textual features, all
of which are conventionally rendered using some kind of highlighting:
<list type="simple"><item>emphasis, foreign words and other linguistically distinct uses
of highlighting</item><item>representation of speech and thought, quotation, etc.</item><item>technical terms, glosses, etc.</item></list>
 </p><div3 id="COHQW" name="burp" ref="Y"><head>What Is Highlighting?</head><p>By <cited>highlighting</cited> we mean the use of any combination of<indexed level1="highlighting"/>
 typographic features (font, size, hue,
etc.) in a printed or written text in order to distinguish some passage
of a text from its surroundings.<note source="auth" place="display" anchored="Y">Although the way in which a spoken
text is performed, (for example, the voice quality, loudness, etc.)
might be regarded as analogous to <soCalled>highlighting</soCalled> in
this sense, these Guidelines recommend distinct elements for the
encoding of such <soCalled>highlighting</soCalled> in spoken texts.  See
further section <xref target="TSSASH"/>.</note> The purpose of highlighting
is generally to draw the reader's attention to some feature or
characteristic of the passage highlighted; this section describes the
elements recommended by these Guidelines for the encoding of such
textual features.
 </p><p>In conventionally printed modern texts, highlighting is often
employed to identify words or phrases which are regarded as being one or
more of the following:
 
<list type="bullets"><item>distinct in some way --- as foreign, dialectal,
archaic, technical, etc.</item><item>emphatic, and which would for example be stressed when spoken</item><item>not part of the body of the text, for example cross references,
titles, headings, labels, etc.</item><item>identified with a distinct narrative stream, for example an
internal monologue or commentary.</item><item>attributed by the narrator to some other agency, either within the
text or outside it:  for example, direct speech or quotation.</item><item>set apart from the text in some other way:  for example,
proverbial phrases, words mentioned but not used, names of persons and
places in older texts, editorial corrections or additions, etc.</item></list>
 </p><p>The textual functions signalled by highlighting may not be rendered
consistently in different parts of a text or in different texts.  (For
example, a foreign word may appear in italics if the surrounding text is
in roman, but in roman if the surrounding text is in italics.)  For this
reason, these Guidelines distinguish between the encoding of rendering
itself and the encoding of the underlying feature expressed by it.
 </p><p>Highlighting as such may be encoded by using the global
<att tei="yes">rend</att> attribute which can be specified for any element in the
TEI scheme.  This allows the encoder both to specify the function of a
highlighted phrase or word, by selecting the appropriate element
described here or elsewhere in the Guidelines, and to further describe
the way in which it is highlighted, by means of the <att tei="yes">rend</att>
attribute.  If the encoder wishes to offer no interpretation of the
feature underlying the use of highlighting in the source text, then the
<gi tei="yes">hi</gi> element may be used, which indicates only that the text so
tagged was highlighted in some way.
 </p><p>The possible values carried by the <att tei="yes">rend</att> attribute are not
formally defined in this version of the Guidelines.  Since the
<att tei="yes">rend</att> attribute may be used to document any peculiarity of the
way a given segment of text was rendered in the original source text, it
may need to express a very large range of typographic features, by no
means restricted to type face, type size, etc.
 <!-- For more discussion see the chapter on physical          --><!-- rendition (section <xref target=PH>).                    -->
 </p><p>Where it is both appropriate and feasible, these Guidelines recommend
that the textual feature marked by the highlighting should be encoded,
rather than just the simple fact of the highlighting.  This is for the
following reasons:
 
<list type="simple"><item>the same kind of highlighting may be used for different purposes
in different contexts</item><item>the same textual function may be highlighted in different ways in
different contexts</item><item>for analytic purposes, it is in general more useful to know the
intended function of a highlighted phrase than simply that it is
distinct.</item></list>
 </p><p>In many, if not most, cases the underlying function of a highlighted
phrase will be obvious and non-controversial, since the distinctions
indicated by a change of highlighting correspond with distinctions
discussed elsewhere in these Guidelines.  It should be recognized,
however, that cases do exist in which is it not economically feasible to
mark the underlying function of highlighting (e.g. in the preparation of
large text corpora), as well as cases in which it is not intellectually
appropriate (as in the transcription of some older materials, or in the
preparation of material for the study of typographic practice).  In such
cases, the <gi tei="yes">hi</gi> element should be used, as further discussed
below.
 </p><p>Elements which are sometimes realized by typographic distinction but
which are not discussed in this section include <gi tei="yes">title</gi>
(discussed in section <xref target="COBI"/>) and <gi tei="yes">name</gi> (discussed
in section <xref target="CONARS"/>).
 </p></div3><div3 id="COHQH" name="burp" ref="Y"><head>Emphasis, Foreign Words, and Unusual Language</head><p>This subsection discusses the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="FOREIGN" atts="lang"/><tagDesc tagDoc="EMPH"/><tagDesc tagDoc="HI" atts="rend"/><tagDesc tagDoc="DISTINCT" atts="type time space social"/></tagList>
 </p><div4 id="COHQHF" name="Section" ref="Y"><head>Foreign Words or Expressions</head><p>Words or phrases which are not in the main language of the text
should be tagged as such, at least where the fact is indicated in the
text.  Where the word or phrase concerned is already distinguished from
the rest of the text by virtue of its function (for example, because it
is a name, a technical term, a quotation, a mentioned word, etc.) then
the global <att tei="yes">lang</att> attribute should be used to specify
additionally that its language distinguishes it from the surrounding
text.  Any element in the TEI scheme may take a <att tei="yes">lang</att>
attribute, which specifies both the writing system and the language used
by its content (see section <xref target="CHSH"/> for discussion of this
attribute).  Where there is no other applicable element, the tag
<tag compl="full" tei="yes">foreign</tag> may be used to provide a peg onto which the
<att tei="yes">lang</att> may be attached.
 
<eg> <![CDATA[
<q>Aren't you confusing <foreign lang=la>post hoc</foreign>
with <foreign lang=la>propter hoc</foreign>?</q> said the
Bee Master.  <q>Wax-moth only succeed when weak bees let
them in.</q>]]></eg><!-- R Kipling 'The mother hive' in Actions and Reactions, 1909 --><!-- these could be tagged as TERM, of course. -MSM -->
 </p><p>The <tag compl="full" tei="yes">foreign</tag> tag should not be used to encode foreign words
which are mentioned or glossed within the text:  for these use the
appropriate element from section <xref target="COHQU"/> below.  Compare the
following example sentences:
 
<eg> <![CDATA[
John eats a <foreign lang=fr>croissant</foreign> every morning.]]></eg>
 
<eg> <![CDATA[
<mentioned lang=fr>Croissant</mentioned> is difficult to
pronounce with your mouth full.]]></eg>
 
<eg> <![CDATA[
A <term lang=fr>croissant</term> is a crescent-shaped piece
of light, buttery, pastry that is usually eaten for
breakfast, especially in France.]]></eg>
 <!-- Collins COBUILD English Language Dictionary, ed. John    --><!-- Sinclair (London and Glasgow:  Collins, 1987), p. 337    --><!-- s.v. croissant.                                          -->
 </p><p>The <gi tei="yes">foreign</gi> element is formally defined as follows:
 
<dtdFrag id="DCOHQ" n="Highlighted phrases"><tagDecl tagDoc="FOREIGN"/></dtdFrag>
 </p></div4><div4 id="COHQHE" name="Section" ref="Y"><head>Emphatic Words and Phrases</head><p>The <gi tei="yes">emph</gi> element is provided to mark words or phrases which
are <emph>linguistically</emph> emphatic or stressed.  Text which is
only typographically <soCalled>emphasized</soCalled> falls into the
class of highlighted text, and may be tagged with the <gi tei="yes">hi</gi>
element.  In printed works, emphasis is generally indicated by devices
such as the use of an italic font, a large typeface or extra wide letter
spacing; in manuscripts and typescripts, it is usually indicated by the
use of underlining.
 
As the following examples demonstrate, an encoder may choose whether or
not to make explicit the particular type of rendition associated with
the emphasis, by use of the <att tei="yes">rend</att> attribute.  If a source text
consistently renders a particular feature (e.g. emphasis or words in
foreign languages) in a particular way, the rendering associated with
that feature may be described in the TEI header and the <att tei="yes">rend</att>
attribute used only to describe examples which deviate from the norm.
 
<eg><![CDATA[<q>Sex, sir, is <emph>purely</emph> a question of appetite!</q>
   Tarr exclaimed.]]></eg><!-- Wyndham Lewis, Tarr (1928), Jupiter ed 1968, p.17 -->
 
<eg><![CDATA[<q>What it all comes to is this,</q> he said.
<q><emph rend=italic>What does Christopher
Robin do in the morning nowadays?</emph></q>]]></eg><!-- Milne, House at Pooh Corner (1928), p83 -->
 
<eg><![CDATA[<l>Here Thou, great <name rend=italics>Anna</name>!
      whom three Realms obey,
<l>Doth sometimes Counsel take &mdash;
      and sometimes <emph rend=italic>Tea</emph>.]]></eg><!-- Pope, Rape of the Lock (1744) III.8 -->
 </p><p>The <gi tei="yes">hi</gi> element is used to mark words or phrases which are
highlighted in some way, but for which identification of the intended
distinction is difficult, controversial or impossible.  It enables an
encoder simply to record the fact of highlighting, possibly describing
it by the use of a <att tei="yes">rend</att> attribute, as discussed above,
without however taking a position as to the function of the
highlighting.  This may also be useful if the text is to be processed in
two stages:  representing simply typographic distinctions during a first
pass, and then replacing the <tag compl="full" tei="yes">hi</tag> tags with more specific tags
in a second pass.
 </p><p>Some simple examples:
 
<eg><![CDATA[<hi rend=gothic>And this Indenture further witnesseth</hi>
that the said <hi rend=italic>Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...]]></eg><!-- Sterne, Tristram Shandy (1760), p.82 -->
 
In this example, the first highlighted phrase uses black letter or
gothic print to mimic the appearance of a legal document, and italic to
mark <cited>Walter Shandy</cited> as a name.  In a second pass, the
elements <gi tei="yes">head</gi> or <gi tei="yes">label</gi> might be appropriate for the
first use, and the element <gi tei="yes">name</gi> for the second.
 
<eg><![CDATA[The heaviest rain, and snow, and hail, and sleet, could
boast of the advantage over him in only one respect.  They
often <hi rend=quoted>came down</hi> handsomely, and
Scrooge never did.]]></eg><!-- Dickens Xmas Carol  p 12 -->
 
In this example, the phrase <cited>came down</cited> uses inverted
commas to indicate a play on words.<note source="auth" place="display" anchored="Y">The Oxford English Dictionary
documents the phrase <cited>to come down</cited> in the sense <gloss>to
bring or put down; <hilited rend="it">esp.</hilited> to lay down money; to
make a disbursement</gloss> as being in use, mostly in colloquial or
humorous contexts, from at least 1700 to the latter half of the 19th
century.<!-- In early Victorian English slang,                        --><!-- < q >to come down handsomely< / q >                      --><!-- might be glossed as < q >to pay out                      --><!-- handsomely< / q >.                                       --></note><!-- a ref to OED would be handy here if you have time to find one -->
In a second pass, the element <gi tei="yes">soCalled</gi> might be preferred.
 <!-- WWP proofer asks why. (msm)                              -->
 </p><p>The <gi tei="yes">emph</gi> and <gi tei="yes">hi</gi> elements are formally defined as
follows:
 
<dtdFrag id="DCOHQ1" contin="DCOHQ"><tagDecl tagDoc="EMPH"/><tagDecl tagDoc="HI"/></dtdFrag>
 </p></div4><div4 id="COHQHD" name="Section" ref="Y"><head>Other Linguistically Distinct Material</head><p>For some kinds of analysis, it may be desirable to encode the
linguistic distinctiveness of words and phrases with more delicacy than
is allowed by the <gi tei="yes">foreign</gi> element.  The <gi tei="yes">distinct</gi>
element is provided for this purpose.  Its attributes allow for
additional information characterizing the nature of the linguistic
distinction to be made in two distinct ways:  the <att tei="yes">type</att>
attribute simply assigns a user-defined code of some kind to the word or
phrase which assigns it to some register, sub-language, etc.  No
recommendations as to the set of values for this attribute are provided
at this time, as little consensus exists in the field.
 </p><p>Alternatively, the remaining three attributes may be used in
combination to place a word or phrase on a three-dimensional scale
sometimes used in descriptive linguistics.<note source="auth" place="display" anchored="Y">See, for example,
<citation><title>Sociolinguistics/Soziolinguistik (An international
handbook of the science of language and society.  Ein internationales
Handbuch zur Wissenschaft von Sprache und Gesellschaft)</title> (Berlin,
New York:  De Gruyter, 1988), I, pp. 271 and 274.</citation></note>
The <att tei="yes">time</att> attribute places a word
<term rend="noindex">diachronically</term>,<indexed level1="diachronic information"/>
for example as archaic, old-fashioned, contemporary, futuristic, etc.;
the <att tei="yes">space</att> attribute places a word
<term rend="noindex">diatopically</term>,<indexed level1="diatopic information"/>
that is, with respect to a geographical classification, for example as
national, regional, international, etc.; the <att tei="yes">social</att> attribute
places a word <term rend="noindex">diastatically</term>,<indexed level1="diastatic information"/>
that is, with respect to a social classification, for example as
technical, polite, impolite, restricted, etc.  Again, no recommendations
are made for the values of these attributes at this time; the encoder
should provide a description of the scheme used in the appropriate
section of the header (see section <xref target="HD5"/>).
 </p><p>Examples:
 
<eg><![CDATA[Next morning a boy in that dormitory confided to his
bosom friend, a <distinct type=psSlang>fag</distinct> of
Macrea's, that there was trouble in their midst which
King <distinct type=archaic>would fain</distinct> keep
secret.]]></eg><!-- Kipling, Stalky & Co. (1899), Library ed 1950, p.83) -->
 
<eg><![CDATA[Next morning a boy in that dormitory confided to his
bosom friend, a
<distinct time=1900 social=publicschool space=GB>fag</distinct>
of Macrea's, that there was trouble in their midst which
King <distinct time=archaic>would fain</distinct> keep
secret.]]></eg>
 
Where more complex (or more rigorous) interpretive analyses of the
associations of a word are required, the more detailed and general
mechanisms described in chapter <xref target="FS"/> should be preferred to
these simple characterizations.  It may also be preferable to record the
kinds of analysis suggested here by means of the simple annotation
element <gi tei="yes">note</gi> described in section <xref target="CONO"/>, or the
<gi tei="yes">span</gi> element described in section <xref target="AISP"/>.
 </p><p>The <gi tei="yes">distinct</gi> element has the following formal definition:
 
<dtdFrag id="DCOHQ3" contin="DCOHQ"><tagDecl tagDoc="DISTINCT"/></dtdFrag>
 <!-- P2, ch 23, sec 7.                                        --><!-- Revisions:                                               --><!-- 19 Oct 92 : LB change xrefs and div levels again        --><!-- 26 May 92 : MSM : fix div levels                         --><!-- 15 May 92 : LB : check out to MSM                        -->
 </p></div4></div3><div3 id="COHQQ" name="burp" ref="Y"><head>Quotation</head><p>This section discusses the following elements, all of which are often
rendered by the use of quotation marks:
 
<tagList style="one-line"><tagDesc tagDoc="Q" atts="who type direct"/><tagDesc tagDoc="QUOTE"/><tagDesc tagDoc="CIT"/><tagDesc tagDoc="SOCALLED"/></tagList>
 </p><p>One form of presentational variation found particularly frequently in
written and printed texts is the use of quotation marks.  As with the
typographic variations discussed in the preceding section, it is
generally helpful to separate the encoding of the underlying textual
feature (for example, a quotation or a piece of direct speech) from the
encoding of its rendering (for example, the use of a particular style of
quotation marks).
 </p><p>The most common and important use of quotation marks is, of course,
to mark <term>quotation</term>, by which we mean simply any part of the
text attributed by the author or narrator to some agency other than the
narrative voice.  Typical examples include passages cited from other
works, for which the element <gi tei="yes">quote</gi> may be used, and words or
phrases attributed to other voices within the current work, for which
the element <gi tei="yes">q</gi> may be used.  If this distinction between
intra-textual and inter-textual voices cannot be made reliably, or is
not of interest, then all quoted matter may simply be marked using the
<gi tei="yes">q</gi> tag.  The editorial policy in this respect should be stated
in the encoding description of the TEI Header.  The <gi tei="yes">soCalled</gi>
element is used for cases where the author or narrator distances him or
herself from the words in question without however attributing them to
any other voice in particular.
 <!-- The following discussion of rendering seems rather long-winded --><!-- to me, but I am not sure where else it goes. Maybe some of it  --><!-- should migrate to PH?                                          -->
 </p><p>Quotation may be rendered by changes in type face, by special
punctuation marks (single or double or angled quotes, dashes, etc.) and
by layout (indented paragraphs, etc.).  If these characteristics are of
interest, an appropriate value for the <att tei="yes">rend</att> attribute should
be given, to record how the <gi tei="yes">q</gi> or <gi tei="yes">quote</gi> element is
rendered.  For discussion of suggested values for this attribute, see
below.
 <!-- , and also chapter <xref target=PH>.                     -->
 </p><p>Quotation marks themselves may, like other punctuation marks, be felt
for some purposes to be worth retaining within a text, quite
independently of their description by the <att tei="yes">rend</att> attribute.
Where this is done, an appropriate entity reference should be chosen
from the standard entity sets listed in chapter <xref target="XW"/>;<!-- not sure if this is the right target: somewhere we should --><!-- reference the standard entity sets -->
this has the advantage that the entity may be redefined as null when the
punctuation is to be ignored for some analytic purpose.  Well-known
ambiguities, such as whether the character ' represents an apostrophe or
a closing single quotation mark, or whether the character " represents
an opening or closing double quotation mark may all be resolved by the
use of appropriate entity references, as discussed in section <xref target="COPU"/>.<!-- This is not true.                                        -->
 </p><p>Alternatively, the encoder may suppress all quotation marks, possibly
recording their form using the <att tei="yes">rend</att> attribute.  Where this is
done, the following list of entity names (taken from the public entity
sets <ident tei="yes" type="entset">ISOpub</ident> and <ident tei="yes" type="entset">ISOnum</ident>) may be found useful to describe
quotation-mark styles common in European and American typesetting:
 <!-- list restored under (mild) protest and with one necessary  --><!-- addition                                     LB, oct 92    -->
 
<list type="gloss"><label>ldquo  </label><item>double inverted comma (shaped like 66, superscript)</item><label>lsquo  </label><item>single inverted comma (shaped like 6, superscript)</item><label>rdquo  </label><item>double apostrophe (shaped like 99, superscript)</item><label>rsquo  </label><item>single apostrophe (shaped like 9, superscript)</item><label>ldquor </label><item>double comma (shaped like 99, printed on base line)</item><label>lsquor </label><item>single comma (shaped like 9, printed on base line)</item><label>laquo  </label><item>double guillemet open to the right</item><label>lsaquo </label><item>single guillemet open to the right</item><label>raquo  </label><item>double guillemet open to the left</item><label>rsaquo </label><item>single guillemet open to the left</item><label>mdash  </label><item>dash the width of a lowercase <cited>m</cited></item></list>
 <!-- J.Lavagnino suggests revisiting the issue of mdash in    --><!-- P4:  perhaps this is too print-centered?  (msm)          -->
 
These may be used in the <att tei="yes">rend</att> attribute to show how the
quotation was opened and closed.  For example, if the words
<cited>pre</cited> and <cited>post</cited> are used to indicate
preceding and following punctuation, then the following example would
describe a conventional American book printed using single quotation
marks:
 
<eg><![CDATA[<q rend='PRE lsquo POST rsquo'>Who-e debel you?</q>
&mdash he at last said &mdash <q
rend='PRE lsquo POST rsquo'>you no speak-e,
damme, I kill-e.</q>  And so saying,
the lighted tomahawk began flourishing
about me in the dark.]]></eg><!-- Melville, Moby Dick (but where?) -->
 
The following example demonstrates alternative policies which may be
adopted with respect to encoding of the punctuation used to mark
quotation:
 
<eg><![CDATA[ 
Adolphe se tourna vers lui :
<q>&mdash Alors, Albert, quoi de neuf?</q>
<q>&mdash Pas grand-chose.</q>
<q>&mdash Il fait beau,</q> dit Robert.]]></eg><eg><![CDATA[ 
Adolphe se tourna vers lui :
<q rend='PRE mdash'>Alors, Albert, quoi de neuf ?</q>
<q rend='PRE mdash'>Pas grand-chose.</q>
<q rend='PRE mdash'>Il fait beau,</q> dit Robert.]]></eg><!-- Queneau, Exercices de style (1947) p.192 -->
 
To make explicit who is speaking, which is not always stated in the
above example, the <att tei="yes">who</att> attribute should be used:
 
<eg><![CDATA[Adolphe se tourna vers lui :
<q who='Adolphe'>&mdash Alors, Albert, quoi de neuf?</q>
<q who='Albert'>&mdash Pas grand-chose.</q>
<q who='Robert'>&mdash Il fait beau,</q> dit Robert.]]></eg><!-- should show QUOTATION declarations for these -->
 
The <att tei="yes">who</att> attribute is also useful as a means of supplying a
normalized form of the speaker's name, to facilitate selection of text
by particular speakers.  As indicated above, it may be supplied whether
or not an indication of the speaker is given explicitly in the text.
 </p><p>Where investigation of <soCalled>narrative voice</soCalled> is the
primary object of the encoding, it may be convenient to identify each
speaker as a <term rend="noindex">participant</term> in the work, and to
associate individual speeches with them by means of SGML's ID/IDREF
mechanism.  See section <xref target="CCAHPA"/> for discussion of the
<term>participant description</term> component of the TEI Header.
 </p><p>For such analyses, it may also be useful to distinguish
representations of speech from representations of thought, in modern
printed texts often indicated by a change of typeface.  The
<att tei="yes">type</att> attribute should be used for this purpose, as in this
example:
 
<eg><![CDATA[<q type=speech>Oh yes,</q> said Henry, <q type=speech>I mean
Gordon Macrae, for example...</q>
<q type=thought>Jungian Analyst with Winebox! That's what you
called him, you callous bastard, didn't you? Eh? Eh?</q>]]></eg><!-- N Williams, The Wimbledon Poisoner, p 204 -->
 </p><p>Quoted matter may be embedded within quoted matter, as when one
speaker reports the speech of another:
 
<eg><![CDATA[<q who=Wilson>Spaulding, he came down into the office just this
day eight weeks with this very paper in his hand, and he
says:&mdash;<q who=Spaulding>I wish to the Lord, Mr. Wilson, that
I was a red-headed man.</q></q>]]></eg><!-- A C Doyle, Red headed league (but where?) -->
 </p><p>Direct speech nested in this way is treated in the same way as
elsewhere:  a change of rendition may occur, but the same
element should be used.  An encoder may however choose to distinguish
between direct speech which contains quotations from extra-textual
matter and direct speech itself, as in the following example:
 
<eg><![CDATA[<p><q>The Lord! The Lord! It is Sakya Muni himself,</q> the
lama half sobbed; and under his breath began the wonderful
Buddhist invocation:-
<q><quote><l>To Him the Way -- the Law -- Apart --
<l>Whom Maya held beneath her heart
<l>Ananda's Lord -- the Bodhisat
</quote>
And He is here! The Most Excellent Law is here also.  My
pilgrimage is well begun.  And what work! What work!</q>]]></eg> <!-- R.Kipling, Kim, Macmillan, 1917(1901) p9 -->
 </p><p>Quotations from other works are often accompanied by a reference to
their source.  The <gi tei="yes">cit</gi> element may be used to group together
the quotation and its associated bibliographic reference, which should
be encoded using the elements for bibliographic references discussed in
section <xref target="COBI"/>, as in the following example.
 
<eg><![CDATA[<div id=MM01 type=chapter><head>Chapter 1</head>
<epigraph>
  <cit><quote><l>Since I can do no good because a woman
  <l>Reach constantly at something that is near it.</quote>
  <bibl><title>The Maid's Tragedy</title>
        <author>Beaumont and Fletcher</author></bibl>
  </cit>
</epigraph>
<p>Miss Brooke had that kind of beauty which seems to be thrown into
relief by poor dress...]]></eg><!-- G. Eliot, Middlemarch, p 1 --><!-- apostrophe added to "Maid's" as per J. Lav, who says     --><!-- Penguin has it. (msm)                                    -->
 
Like other bibliographic references, the citation attached to a
quotation may be represented simply by a pointer, as in this example:
 
<eg><![CDATA[Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized
in his slogan, <cit><quote>You shall know a word by the company it
keeps.</quote> <ref target=FI57>(Firth, 1957)</ref></cit>]]></eg><!-- Hanks, in Looking Up, ed Sinclair, (1987) p.121 -->
 
Unlike most of the other elements discussed in this chapter, direct
speech and quotations may frequently contain other high-level elements
such as paragraphs or verse lines, as well as being themselves contained
by such elements.  Three possible solutions exist for this well-known
structural problem:
 
<list type="bullets"><item>the quotation is broken into segments, each of which
is entirely contained within a paragraph</item><item>the quotation is marked up as part of a concurrent but
independent hierarchy</item><item>the quotation boundaries are represented by empty milestone
tags</item></list>
 
For further discussion, and several examples, see chapter <xref target="NH"/>.
 </p><p>Finally, in this section, the element <gi tei="yes">soCalled</gi> is provided
for all cases in which quotation marks are used to distance the quoted
text from the narrator or speaker.  Common examples include the
<soCalled>scare</soCalled> quotes often found in newspaper headlines and
advertising copy, where the effect is to cast doubts on the veracity of
an assertion:
 
<eg><![CDATA[<head>PM dodges <soCalled>election threat</soCalled>
in interview</head>]]></eg><!-- The Guardian, p2, 26 Oct 1992  -->
 </p><p>The same element should be used to mark a variety of special ironic
usages.  Some further examples follow:
 
<eg><![CDATA[He hated <soCalled>good</soCalled> books.
 
<soCalled>Croissants</soCalled> indeed! toast not good enough for you?]]></eg><!-- some "real" examples would be better -->
 
<eg><![CDATA[Although Chomsky's decision that all NL sentences are finite
objects was never justified by arguments from the attested
properties of NLs, it did have a certain
<soCalled>social</soCalled> justification.  It was
commonly assumed in works on logic until fairly recently
that the notion <mentioned>language</mentioned> is
necessarily restricted to finite strings.]]></eg><!-- Langendoen and Postal, Vastness of NLs, p. 24 note 12.        -->
 </p><p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id="DCOHQQ" n="Quotation" contin="DCOHQ"><tagDecl tagDoc="Q"/><tagDecl tagDoc="QUOTE"/><tagDecl tagDoc="CIT"/><tagDecl tagDoc="SOCALLED"/></dtdFrag>
 <!-- P2, ch 23, sec 8                                         --><!-- Revisions                                                --><!-- 24-27 Oct LB     reorganise slightly                     --><!-- 26 May 92 : MSM : fix div levels                         --><!-- 15 May 92 : LB : check out to MSM                        --></p></div3><div3 id="COHQU" name="burp" ref="Y"><head>Terms, Glosses, and Cited Words</head><p>This section describes the following textual elements, all of which
have in common that they may be variously realized using italics,
quotation marks or other devices:
 
<tagList style="one-line"><tagDesc tagDoc="TERM"/><tagDesc tagDoc="GLOSS"/><tagDesc tagDoc="MENTIOND"/></tagList>
 </p><p>Technical terms are often italicized or emboldened upon first mention
in printed texts; an explanation or gloss is sometimes given in
quotation marks.  Linguistic analyses conventionally cite words in
languages under discussion in italics, providing a gloss immediately
following marked with single quotation marks.  Other texts in which
individual words or phrases are <term rend="noindex">mentioned</term> (for<indexed level1="mention" level2="vs. use"/><indexed level1="use" level2="vs. mention"/>
example, as examples) rather than <term rend="noindex">used</term> may
mark them either with italics or with quotation marks, and will gloss
them less regularly.
 </p><p>A <gi tei="yes">term</gi> may appear with or without a gloss, as may a
<gi tei="yes">mentioned</gi> element.  Where the <gi tei="yes">gloss</gi> is present, it may
be linked to the term it is glossing by means of SGML's ID/IDREF
mechanism.  To establish such a link, the encoder should give an
<att tei="yes">id</att> value to the <gi tei="yes">term</gi> or <gi tei="yes">mentioned</gi> element
and provide that id as the value of the <att tei="yes">target</att> attribute on
the <gi tei="yes">gloss</gi> element.  The following examples demonstrate this
facility:  for more discussion of this and other kinds of linkage within
TEI documents, see chapter <xref target="SA"/>.
 </p><p>Examples:
<eg><![CDATA[We may define <term rend=sc id=TDPV>discoursal point of view</term>
as <gloss target=TDPV>the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>]]></eg><!-- Leech, Style in Fiction, (1981) p272 -->
 
<eg><![CDATA[<gloss target=T1 rend=unmarked>A computational device
that infers structure from grammatical strings of words</gloss>
is known as a <term id=T1>parser</term>, and much of the
history of NLP over the last 20 years has been occupied with
the design of parsers.]]></eg><!-- Gazdar and Mellish, NLP in Prolog, p. 5   -->
 
<eg><![CDATA[There is thus a striking accentual difference between a
verbal form like <mentioned lang=grc
id=cw234>eluthemen</mentioned> <gloss target=CW234>we
were released,</gloss> accented on the second
syllable of the word, and its participial derivative
<mentioned id=CW235 lang=grc>lutheis</mentioned>
<gloss target=CW235>released,</gloss> accented on the last.]]></eg><!-- Sapir, Language (HBJ paperback), p. 79                        -->
 </p><p>The elements discussed in this section have the following formal
definitions:
<dtdFrag id="DCOHQU" n="Terms, glosses, etc." contin="DCOHQ"><tagDecl tagDoc="TERM"/><tagDecl tagDoc="MENTIOND"/><tagDecl tagDoc="GLOSS"/></dtdFrag>
 </p></div3><div3 id="COHQHEG" name="burp" ref="Y"><head>Some Further Examples</head><p>As a simple example of the elements discussed here, consider the
following sentence:
 <!-- Theodore M. Andersson, Preface to the Nibelungenlied, p. 3 -->
<q rend="display">On the one hand the <title>Nibelungenlied</title> is
associated with the new rise of romance of twelfth-century
France, the <foreign>romans d'antiquit&eacute;</foreign>,
the romances of Chr&eacute;tien de Troyes, and the German
adaptations of these works by Heinrich van Veldeke,
Hartmann von Aue, and Wolfram von Eschenbach.</q>
A first approximation to the encoding of this sentence, might be simply
to record the fact that the phrases printed above in italics are
highlighted, as follows:
<eg><![CDATA[On the one hand the <hi rend=italic>Nibelungenlied</hi> is
associated with the new rise of romance of twelfth-century
France, the <hi rend=italic lang=fr>romans
d'antiquit&eacute;</hi>, the romances of Chr&eacute;tien de
Troyes, ...]]></eg>
This encoding would however lose the important distinction between
an italicized title and an italicized foreign phrase.  Many other
phrases might also be italicized in the text, and a retrieval
program seeking to identify foreign terms (for example) would not
be able to produce reliable results by simply looking for italicized
words.  Where economic and intellectual constraints permit, therefore,
it would be preferable to encode both the function of the
highlighted phrases and their appearance, as follows:
<eg><![CDATA[On the one hand the <title
rend=italic>Nibelungenlied</title> is associated with the
new rise of romance of twelfth-century France, the <foreign
rend=italic>romans d'antiquit&eacute;</foreign>, the
romances of Chr&eacute;tien de Troyes, ...]]></eg></p><p>In this example, the decision as to which textual features
are distinguished by the highlighting is relatively
uncontroversial.  As a less straightforward example, consider the
use of italic font in the following passage
from Samuel Richardson's <title>Clarissa</title> (1747).<!-- NB this is NOT a P2 example!! --><!-- replaced < ital > by < hilited rend=it > added entity ref -->
<q rend="display">A pretty common case, I believe; in all
<hilited rend="it">vehement</hilited> debatings.  She says I am
<hilited rend="it">too witty</hilited>; Anglic&eacute;,
<hilited rend="it">too pert</hilited>; I, that she is
<hilited rend="it">too wise</hilited>; that is to say, being
likewise put into English, <hilited rend="it">not so young as
she has been</hilited>:  in short, she is grown so much into
a <hilited rend="it">mother</hilited>, that she had forgotten
she ever was a <hilited rend="it">daughter</hilited>. ...</q>
 </p><p>Clearly, the word <cited>vehement</cited> is not italicized for the
same reason as the phrase <cited>not so young as she has been</cited>;
the former is emphasized, while the latter is proverbial.  It also
provides an ironic gloss for the words <cited>too wise</cited>, in the
same way as <cited>too pert</cited> glosses <cited>too witty</cited>.
The glossed phrases are not however technical terms or cited words, but
quoted phrases, as if Clarissa were putting words into her own and her
mother's mouths.  Finally, the words <cited>mother</cited> and
<cited>daughter</cited> are apparently italicized simply to oppose them
in the sentence; certainly they do not fit into any of the categories so
far proposed as reasons for italicizing.  Note also that the word
<cited>Anglic&eacute;</cited> is not italicized although it is not
generally considered an English word.
 </p><p>The following sample encoding for the above passage attempts to take
into account all the above points:
 
<eg><![CDATA[A pretty common case, I believe; in all
<emph>vehement</emph> debatings.  She says I am
<q rend=italic>too witty</q>; <foreign lang=la
rend=roman>Anglic&egrave;</foreign>, <gloss rend=italic>too
pert</gloss>; I, that she is <q rend=italic>too wise</q>;
that is to say, being likewise put into English, <gloss
rend=italic>not so young as she has been</gloss>:  in short,
she is grown so much into a <hi rend=italic>mother</hi>,
that she had forgotten she ever was a
<hi rend=italic>daughter</hi>.]]></eg>
 <!-- WWP proofer points out inconsistency between tagging     --><!-- and commentary.  "too witty" and "too wise" retagged     --><!-- from TERM (which the prose says they are *not*) to Q     --><!-- (which the prose says they *are*).  WWP proofer also     --><!-- suggests EMPH for 'mother' and 'daughter', but our       --><!-- imaginary interpretation says we don't understand the    --><!-- italics there, so we leave it undisambiguated.  (msm)    --><?tei:EOF p2cohq.odd ??>

 <!-- COna Names (P1 5.3.6)                                    --><?tei:SOF p2cona.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2cona.odd,v $
# Revision 1.7  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.6  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# --><!-- Revisions:                                               --><!-- 10 jan 98 : LB : fix eg --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 3 jan 94: fixed up address again --><!-- 27 dec 93:LB: moved address section                      --><!-- 93-06-05 : MSM : fix type:  eg had no end-tag, two starts --><!-- 2 Jun 93: LB : incorporate and tidy up DG's Eynsham revisions --><!-- 92-12-09 : MSM : introduce NAMES class                   --><!--                  correct typo in 'practical' Chaucer     --><!-- 92-12-09 : MSM : spellcheck for publication              --><!-- 92-12-09 : MSM : cosmetic copy editing                   --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-07 : MSM : change date/type to date/calendar       --><!-- 92-12-07 : MSM : finish run-through for publication      --><!-- 92-12-06 : MSM : begin revising for publication          --><!-- 92-12-06 : MSM : include addr in title, correct abbr div --><!-- 92-12-06 : MSM : include new p2conaad div                --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 92-11-09 : MSM : indent ellipsis for WGML's sake         -->
 </p></div3></div2><div2 id="CONA" name="section" ref="Y"><head>Names, Numbers, Dates, Abbreviations, and Addresses</head><p>This section describes a number of  textual features which it is
often convenient to distinguish from their surrounding text.  Names,
dates and numbers are likely to be of particular importance to  the
scholar treating a text as source for a database; distinguishing such
items from the surrounding text is however equally important to the
scholar primarily interested in lexis.
 </p><p>The treatment of these textual features proposed here is not
intended to be exhaustive: fuller treatments for names, numbers,
measures and dates are provided in the additional tag set for
names and dates (see chapter <xref target="ND"/>).
 <!-- fuller treatment of addresses in the base tag set for    --><!-- letters and memoranda (see chapter <xref target=LM>).    -->
 <!-- P2.239 : Referring Strings                                --><!-- Revisions:                                               --><!-- 16 May 92 : DG further revision                         --><!-- 13 oct 92 : LB further revision                          --><!-- 5-7 Oct 92 : (LB) reassemble; extensively revise; redo IDs  --><!-- 25 May 92 : CMSMcQ : drop components, add note on them   --><!-- 24 May 92 : CMSMcQ : add component parts for names       --><!-- 14 May 92 : CMSMcQ : revise.                             --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->
 </p><div3 id="CONARS" name="subsection" ref="Y"><head>Referring Strings</head><p>A <term>referring string</term> is a phrase which refers to some
person, place, object etc. Two elements are provided to mark such
strings:
 
<tagList style="one-line"><tagDesc tagDoc="RS" atts="type"/><tagDesc tagDoc="NAME" atts="type"/></tagList>
 
Where it is thought useful to do so, the kind of object referred to may
be specified using the <att tei="yes">type</att> attribute.
 </p><p>Examples include:
 
<eg><![CDATA[<q>My dear <rs type=person>Mr. Bennet</rs>, </q>
said his lady to him one day, <q>have you heard
that <rs type=place>Netherfield Park</rs> is let
at last?</q>]]></eg><!-- Austen Pride and Prejudice, chap 1 -->
 
<eg><![CDATA[Collectors of water-rents were appointed by the
<rs type=organization>Watering Committee</rs>.
They were paid a commission not exceeding four per
cent, and gave bond.]]></eg><!-- Allinson and Penrose, Philadelphia 1681-1887, p138 -->
 
<eg> <![CDATA[
It being one of the principles of the
<rs type=org>Circumlocution Office</rs> never, on any
account whatsoever, to give a straightforward answer,
<rs type=person>Mr Barnacle</rs> said, <q>Possibly.</q>]]></eg><!-- Little Dorrit, peng ed, p 153 -->
 </p><p>As the following example shows, the <gi tei="yes">rs</gi> element may be used
for any reference to a person, place, etc., not only to references in
the form of a proper noun or noun phrase.
 
<eg><![CDATA[<q>My dear <rs type=person>Mr. Bennet</rs>,</q>
said <rs type=person>his lady</rs> to him
one day...]]></eg>
 
 </p><p>The <gi tei="yes">name</gi> element by contrast is provided for the special
case of referencing strings which consist only of proper nouns; it may
be used synonymously with the <gi tei="yes">rs</gi> element, or nested within it
if a referring string contains a mixture of common and proper nouns.
The following example shows an alternative way of encoding the short
sentence from <title>Pride and Prejudice</title> quoted above:
 
<eg><![CDATA[<q>My dear <name type=person>Mr. Bennet</name>,</q>
said <rs type=person>his lady</rs> to him one day,
<q>have you heard that <name type=place>Netherfield
Park</name> is let at last?</q>]]></eg>
 
The following example shows how a proper name may be nested within a
referring string:
 
<eg><![CDATA[<rs>His Excellency the Life President,
<name>Ngwazi Dr H. Kamuzu Banda</name></rs>
<!-- ... -->]]></eg><!-- any issue of the Malawi Daily Times -->
 
 </p><p>Simply tagging something as a name is generally not enough to enable
automatic processing of personal names into the canonical forms usually
required for reference purposes. The name as it appears in the text may
be inconsistently spelled, partial, or vague.  Moreover, name prefixes
such as <cited>van</cited> or <cited>de la</cited>,  may or may not be
included as part of the reference form of a name, depending on the
language and country of origin of the bearer.
 </p><p>The following attributes, common to all members of the
<ident tei="yes" type="class">names</ident>
element class, are provided to help overcome these difficulties:
 
<adList classDoc="NAMES" atts="key reg"/>
 </p><p>Either or both of these attributes may be specified, as appropriate.
The <att tei="yes">key</att> attribute may be useful as a means of gathering
together all references to the same individual or location scattered
throughout a document:
 
 
<eg><![CDATA[<q>My dear <rs type=person key=BENM1>Mr. Bennet</rs>,
</q> said <rs type=person key=BENM2>his lady</rs>
to him one day, <q>have you heard that
<rs type=place key=NETP1>Netherfield Park</rs>
is let at last?</q>]]></eg>
 </p><p>This use should be distinguished from the case of the
<att tei="yes">reg</att> (regularization) attribute, which provides a
means of marking the standard form of a referencing string as
demonstrated below:
 
<eg><![CDATA[My personal life during the administration of
<rs type=person key=POJA1 reg='Polk, James K.'>Col. Polk</rs>
has but poorly compensated me for the suspended
enjoyments and pursuits of private and professional spheres]]></eg><!-- From the papers of George Mifflin Dallas, cited in --><!-- Philadelphia: A 300 Year History, p349 -->
 
<eg><![CDATA[<name type=person key=VOM1 reg='Volanges, Mme de'>
Mme. de Volanges</name>
marie sa fille: c'est encore un secret; mais elle m'en
a fait part hier.]]></eg>  <!-- de Laclos: Les Liaisons dangereuses, 1963, p.13 -->
 
<eg><![CDATA[<name type=person key=WADLM1 reg='de la Mare, Walter'>
Walter de la Mare
</name>
was born at
<name key=Ch1 type=place>Charlton</name>, in
<name key=KT1 type=county>Kent</name>, in 1873.]]></eg><!-- Frank Swinnerton, The Georgian Literary Scene, 1938, p. 195 -->
 
<eg><![CDATA[<name type=place>Montaillou</name> is not a large parish.
At the time of the events which led to
<name type=person reg='Benedict XII, Pope of Avignon
(Jacques Fournier)'>Fournier's</name> investigations,
the local population consisted of between 200 and
250 inhabitants.]]></eg>
 <!-- E.L Ladurie: Montaillou, Penguin 1980, p3 --><!-- but should we quote the French? (LB) -->
 </p><p>This method is adequate for many simple applications. For more
complex applications, such as onomastics, or wherever a detailed
analysis of the component parts of a name is needed, the specialized
elements described in chapter <xref target="ND"/> or the analytical
tools described in chapter <xref target="FS"/> should be used.
 </p><p>These elements are formally declared as follows:
<dtdFrag id="DCONA" n="Proper Nouns"><tagDecl tagDoc="NAME"/><tagDecl tagDoc="RS"/></dtdFrag>
 <!-- <claDecl type=atts classDoc=NAMES>                       -->
 </p></div3><div3 id="CONAAD" name="subsection" ref="Y"><head>Addresses</head><p>The simplest way of encoding an address is to regard it as a series
of distinct lines, just as they might be printed on an envelope. The
following elements support this view:
 
<tagList style="one-line"><tagDesc tagDoc="ADDRESS"/><tagDesc tagDoc="ADDRLINE"/></tagList>
 </p><p>Alternatively, an address may be encoded as a structure composed of
the following elements, which constitute the <ident tei="yes" type="class">addrPart</ident> element class:
 
<tagList style="one-line"><tagDesc tagDoc="STREET"/><tagDesc tagDoc="NAME" atts="type"/><tagDesc tagDoc="POSTCODE"/><tagDesc tagDoc="POSTBOX"/></tagList>
 
Any number of <ident tei="yes" type="class">addrPart</ident> elements may appear
within an address and in any order.  None of them is required.  Where
code letters are commonly used in addresses (for example, to identify
regions or countries) a useful practice is to supply the full name of
the region or country as the content of the element, but to supply the
abbreviatory code as the value of the global <att tei="yes">n</att> attribute, so
that (for example) an application preparing formatted labels can readily
find the required information.  Other components of addresses should be
represented using the general-purpose <gi tei="yes">name</gi> element.
 </p><p>Some examples follow:
<eg><![CDATA[<address>
<addrLine>110 Southmoor Road, </>
<addrLine>Oxford, OX2 6RB,</>
<addrLine>UK</>
</address>]]></eg>
 </p><p>The above address could also be represented as follows :
 
<eg><![CDATA[<address>
<street>110 Southmoor Road</street>
<name type=city n=OX>Oxford</name>
<postCode>OX2 6RB</postCode>
<name type=country n=UK>United Kingdom</name>
</address>]]></eg>
 </p><p>The order of elements within an address is highly culture-specific,
and is therefore unconstrained:
 
<eg><![CDATA[<address>
<name type=org>Universit&agrave; di Bologna</name>
<name type=country n=I>Italy</name>
<postCode>40126</postcode>
<name type=city>Bologna</name>
<street>via Marsala 24</street>
</address>]]></eg>
 </p><p>For further discussion of ways of regularizing the names of places,
see section <xref target="CONA"/>.  A full postal address may also include
the name of the addressee, tagged as above using the general purpose
<gi tei="yes">name</gi> element.  When the additional tag set for names and dates
is enabled, more specific elements such as <gi tei="yes">publisher</gi> or
<gi tei="yes">org</gi> may be used, as further discussed in chapter <xref target="ND"/>.
 <!-- <p>A more detailed encoding of addresses is provided by  --><!-- the elements described in the base tag set for letters   --><!-- and memoranda described in chapter <xref target=LM>,     --><!-- which also includes elements for the encoding of         --><!-- electronic mail addresses and other telecommunications   --><!-- facilities.                                              -->
 </p><p>The <gi tei="yes">address</gi> element and its components are formally
described as follows:
 
<dtdFrag id="DCOAD" n="Addresses and their components"><tagDecl tagDoc="ADDRESS"/><tagDecl tagDoc="ADDRLINE"/><tagDecl tagDoc="STREET"/><tagDecl tagDoc="POSTCODE"/><tagDecl tagDoc="POSTBOX"/><commDecl>Other components of addresses should be represented
using the general purpose NAME element</commDecl></dtdFrag>
 <!-- P2.23a : Numbers                                         --><!-- Revisions:                                               --><!-- 25 May 92 : CMSMcQ : revise                              -->
 </p></div3><div3 id="CONANU" name="subsection" ref="Y"><head>Numbers and Measures</head><!-- h3 id=Z63A>Numbers and Dates --><p>This section describes two elements provided for the simple encoding
of numbers and measures and gives some indication of circumstances in
which this may usefully be done.  The following phrase level elements
are provided for this purpose:
 
<tagList style="one-line"><tagDesc tagDoc="NUM" atts="type value"/><tagDesc tagDoc="MEASURE" atts="type"/></tagList>
 </p><p>Like names or abbreviations, numbers can occur virtually anywhere in
a text.  Numbers are special in that they can be written with either
letters or digits (<cited>twenty-one</cited>, <cited>xxi</cited>, and
<cited>21</cited>) and their presentation is language-dependent (e.g.
English <cited>5th</cited> becomes Greek <cited>5.</cited>; English
<cited>123,456.78</cited> equals French <cited>123.456,78</cited>).
 </p><p>For many kinds of application, e.g. natural-language processing or
machine translation, numbers are not regarded as
<soCalled>lexical</soCalled> in the same way as other parts of a text.
For these and other applications, the <gi tei="yes">num</gi> element provides a
convenient method of distinguishing numbers from the surrounding text.
For other kinds of application, numbers are only useful if normalized:
here the <gi tei="yes">num</gi> element is useful precisely because it provides a
standardized way of representing a numerical value.
 </p><p>For example:
<eg><![CDATA[<num value='33'>xxxiii</num>
<num type=cardinal value='21'>twenty-one</num>
<num type=percentage value='10'>ten percent</num>
<num type=percentage value='10'>10%</num>
<num type=ordinal value='5'>5th</num>]]></eg>
 
<eg><![CDATA[<num type=fraction value='0,5'>one half</num>
<num type=fraction value='0,5'>1/2</num>]]></eg>
 
 </p><p>The word <cited>measure</cited> is used here to refer to a special
kind of referring string, the referent of which is a <soCalled>virtual
object</soCalled>.  In its fullest form, a measure consists of a number,
a phrase expressing units of measure and a phrase expressing the
commodity being measured.  Not all of these components need be present
in every case.  For some applications, particularly quantitative ones,
the internal components of measure need to be marked so that their
values can be calculated.  Thus, in order to evaluate a monetary measure
according to some standard, it is necessary to mark its currency unit
(e.g.  US dollars, pounds sterling).  Similarly, the expression <cited>2
ounces</cited> will have a different meaning when it is associated with
<cited>flour</cited> from that which it has when associated with
<cited>water</cited>.
 </p><p>Such applications will require the elements discussed in chapter<xref target="ND"/>
, or the more powerful analytical tools discussed in
chapter <xref target="FS"/>.  Elsewhere, it may be sufficient simply to
encode measures as such, perhaps also indicating their numeric content
with the <gi tei="yes">num</gi> element, as in the following examples:
 
<eg><![CDATA[<l>I've measured it from side to side
<l>'Tis
<measure type=length reg='0.924m'>
    <num value=3>three</num>
    feet
</measure>
long, and
<measure type=length reg='0.616m'>
   <num value=2>two</num>
   feet
</measure>
wide.
</l>]]></eg><!-- Wordsworth: The Thorn: Lyrical Ballads (1798) -->
 
As the above example also demonstrates, the <gi tei="yes">measure</gi> element is
a member of the class <ident tei="yes" type="class">names</ident> like other
referencing strings, and may thus bear a <att tei="yes">reg</att> attribute to
indicate a normalized value.  It may also carry a <att tei="yes">key</att>
attribute to indicate a database key value as in the following example:
 
 
<eg><![CDATA[<list>
<item><measure key=BH2 type=volume>
         <num value=2>ii</num>
          bags hops
       </measure>
<item> <measure key=TW6 type=volume>
         <num value=6>six</num>
        trusses Woolen and linen goods
       </measure>
<item><measure  key=WC5 type=weight>
        5 tonnes coale
      </measure>
<!-- ... -->
</list>]]></eg><!-- Gloucester Port Books -->
 </p><p>These elements are formally defined as follows:
 
<dtdFrag id="DCONU" n="Numbers and measures"><tagDecl tagDoc="NUM"/><tagDecl tagDoc="MEASURE"/></dtdFrag>
 <!-- P2.23c : Dates                                           --><!-- Revisions:                                               --><!-- 25 May 92 : CMSMcQ : revise                              --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->
 </p></div3><div3 id="CONADA" name="subsection" ref="Y"><head>Dates and times</head><p>Dates and times, like numbers, can appear in widely varying
culture- and language-dependent forms, and can pose similar problems
in automatic language processing.  The following elements are provided
to identify them:
 <!--  certainty attributes replaced by exact   --><!-- added time, on advice of Chicago meeting, but with reservns -->
 
<tagList style="one-line"><tagDesc tagDoc="DATE" atts="calendar value"/><tagDesc tagDoc="TIME" atts="value"/><tagDesc tagDoc="DATERANG" atts="calendar from to exact"/><tagDesc tagDoc="TIMERANG" atts="from to exact"/></tagList>
 </p><p>Dates can occur virtually anywhere in a text, but in some contexts
(e.g. bibliographic citations) their encoding is recommended or
required rather than optional.  Times can also appear anywhere but
are generally optional.
 </p><p>Partial dates or times (e.g. <cited>1990</cited>, <cited>September
1990</cited>, <cited>twelvish</cited>) can be expressed in the
<att tei="yes">value</att> attribute by simply omitting a part of the value
supplied.  Imprecise dates or times (for example <cited>early
August</cited>, <cited>some time after ten and before twelve</cited>)
may be expressed as date or time ranges.  If either end of the date or
time range is known to be accurate (for example, <cited>at some time
before 1230</cited>, <cited>a few days after Hallowe'en</cited>), the
<att tei="yes">exact</att> attribute may be used to specify this.
 </p><p>Where the certainty (i.e. reliability) of the date or time itself is
in question, rather than its precision, the encoder should record this
fact using the mechanisms discussed in chapter <xref target="CE"/>.
 </p><p>These mechanisms are useful primarily for fully specified dates or
times known with certainty.  If component parts of dates or times are to
be marked up, or if a more complex analysis of the meaning of a temporal
expression is required, the techniques described in chapter <xref target="ND"/> should be used in preference to the simple method outlined
here.
 </p><p>Examples:
 
<eg><![CDATA[<date value='1980-02-21'>21 Feb 1980</date>]]></eg>
 
<eg><![CDATA[Given on the <date value='1977-06-12'>Twelfth Day of June
in the Year of Our Lord One Thousand Nine Hundred and
Seventy-seven of the Republic the Two Hundredth and first
and of the University the Eighty-Sixth.</date>]]></eg>
 
<eg><![CDATA[<date value='1990'>1990</date>
<date value='1990-09'>September 1990</date>]]></eg>
 
<eg><![CDATA[Those five years &mdash; <dateRange from=1918 to=1923>
1918 to 1923</dateRange> &mdash had been, he suspected,
somehow very important.]]></eg><!-- Woolf, Mrs Dalloway, p. 65 -->
<eg><![CDATA[The Eddic poems are preserved in a unique
manuscript (Codex Regius 2365) from
<dateRange from=1250 to=1300>
the second half of the thirteenth
century</dateRange>, and <title>Hervarar
saga</title> dates from <date value=1300>
around 1300</date>.]]></eg><!-- T. M. Andersson, A Preface to the Nibelungenlied         --><!-- (Stanford:  Stanford University Press, 1987) p. 4        -->
 </p><p>These elements are formally defined as follows:
 
<dtdFrag id="DCODA" n="Dates and times"><tagDecl tagDoc="DATE"/><tagDecl tagDoc="DATERANG"/><tagDecl tagDoc="TIME"/><tagDecl tagDoc="TIMERANG"/></dtdFrag>
 
 </p></div3><div3 id="CONAAB" name="subsection" ref="Y"><head>Abbreviations and Their Expansions</head><p>It is sometimes desirable to mark abbreviations in the copy text,
whether to trigger special processing for them, to provide the full form
of the word or phrase abbreviated, or to allow for different possible
expansions of the abbreviation.  Abbreviations may be transcribed as
they stand, or expanded; they may be left unmarked, or marked using
these tags:
 
<tagList style="one-line"><tagDesc tagDoc="ABBR" atts="expan resp type cert"/><tagDesc tagDoc="EXPAN" atts="abbr resp type cert"/></tagList>
 <!-- resp and cert bearing elements should become a class before p3 -->
 </p><p>The <gi tei="yes">abbr</gi> element is useful as a means of distinguishing
semi-lexical items such as acronyms or jargon:
 
<eg><![CDATA[We can sum up the above discussion as follows:  the identity of a
<abbr>CC</abbr> is defined by that calibration of values which
motivates the elements of its <abbr>GSP</abbr>; ...]]></eg><!-- Halliday and Hassan, Language, context, and text:        --><!-- aspects of language in a social-semiotic perspective     --><!-- (OUP, 1990), p 104                                       -->
 
<eg><![CDATA[Every manufacturer of <abbr>3GL</abbr> or <abbr>4GL</abbr>
languages is currently nailing on <abbr>OOP</abbr> extensions.]]></eg> <!-- .EXE magazine Editorial, 6.11, (May 1992) p2 -->
 </p><p>The <att tei="yes">type</att> attribute may be used to distinguish types
of abbreviation by their function, and the <att tei="yes">expan</att> attribute
may be used to supply an expansion:
 
<eg><![CDATA[ <abbr type=title>Dr.</abbr> <abbr type=initial>M.</abbr> Deegan
 is the Director of the <abbr expan='Computers in Teaching Initiative'
 type=acronym>CTI</abbr> Centre for Textual Studies.]]></eg>
 </p><p>Abbreviations such as <cited>Dr M</cited> above may be treated as two
abbreviations, as above, or as one:
 
<eg><![CDATA[ <abbr>Dr. M.</abbr> Deegan is the Director of the
 <abbr>CTI</abbr> Centre for Textual Studies.]]></eg>
 </p><p>This element is particularly useful where manuscript materials
in which abbreviation is very frequent are being transcribed.  For
example:
 
<eg><![CDATA[<l>Ex<abbr type=brevigraph expan='per'
           Resp=PG>&per;</abbr>ience, thogh noon auctoritee
<l>Were in this world, is right ynogh for me
<l>To speke of wo that is in mariage;]]></eg>
 </p><p>Here an entity reference <ident tei="yes" type="ge">per</ident> has been used to
represent the common manuscript symbol <cited>crossed-p</cited>, and its
expansion supplied in the associated <gi tei="yes">abbr</gi> tag.  The same lines
might be transcribed, expanded, as follows:
 
<eg><![CDATA[<l>Ex<expan type=brevigraph abbr='&per;'
          resp=PG>per</expan>ience, thogh noon auctoritee
<l>Were in this world, is right ynogh for me
<l>To speke of wo that is in mariage;]]></eg>
 </p><p>In practice, it may be most convenient to transcribe the abbreviation
as an entity reference; this allows the entity reference itself to be
expanded either as an <gi tei="yes">abbr</gi> or as an <gi tei="yes">expan</gi> element,
depending on the processing to be done at the moment.  (For further
discussion of such documentation, see section <xref target="WDCSCC"/>.)
The text shown here:
 
<eg><![CDATA[<l>Ex&per;ience, thogh noon auctoritee
<l>Were in this world, is right ynogh for me
<l>To speke of wo that is in mariage;]]></eg>
 
may be expanded as desired by providing the appropriate choice between
the two entity declarations:
 
<eg rend="decl"><![CDATA[<!ENTITY per "<abbr type=brevigraph expan='per'
              Resp=PG>&p.crossed;</abbr>" >
<!ENTITY per "<expan type=brevigraph abbrev='&p.crossed;'
              Resp=PG>per</expan>" >]]></eg>
 
For further discussion of manuscript abbreviations, see chapter <xref target="PH"/>.
 </p><p>These elements are formally defined as follows:
<dtdFrag id="DCOAB" n="Abbreviations"><tagDecl tagDoc="ABBR"/><tagDecl tagDoc="EXPAN"/></dtdFrag><?tei:EOF p2cona.odd ??>

 <!-- COed Editorial Interventions                             --><?tei:SOF p2coed.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2coed.odd,v $
    * Revision 1.7  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.6  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.5  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * --><!-- Revisions:                                               --><!-- 10 jan 98 : LB : fix eg errors --><!-- 4 Jan 98 : LB : restored missing > preceding tagdesc for ADD --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-26 : MSM : corrections from DB                     --><!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 3 jan 94: LB : rename omit/gap; remove SUPPLIEd; add UNCLEAR --><!-- 21 dec Lb : removed cert from OMIT (not in tagdoc) --><!-- 93-06-05 : MSM : remove dot from col 1                   --><!-- 1 jun 93 : LB implement PR's suggestions of 28 may --><!-- 92-12-09 : MSM : normalize sentence-end spacing          --><!-- 92-12-09 : MSM : spellcheck for release                  --><!-- 92-12-09 : MSM : correct bad /gi and /att tags           --><!-- 92-12-09 : MSM : correct typo as per LB                  --><!-- 92-12-07 : MSM : revise for publicatn, add examples      --><!-- 92-11-09 : MSM : suppress leading blanks after some tags --><!-- 92-11-09 : MSM : change COedcorr to COedcor              --><!-- P2 CO edit:  core tags for editorial interventions       --><!-- Revisions:                                               --><!-- 5-8 Oct 92 : LB changed xrefs; fiddled with prose somewhat;  --><!--              completed examples at end                   --><!-- 13 Sep 92 : MSM : made file, extract text from P247.doc  -->
 </p></div3></div2><div2 id="COED" name="section" ref="Y"><head>Simple Editorial Changes</head><p>As in editing a printed text, so in encoding a text in electronic
form, it may be necessary to accommodate editorial comment on the text
and to render account of any changes made to the text in preparing it.
The tags described in this section may be used to record such editorial
interventions, whether made by the encoder, by the editor of a printed
edition used as a copy text, by earlier editors, or by the copyists of
manuscripts.
 </p><p>The tags described here handle most common types of editorial
intervention and stereotyped comment; where less structured
commentary of other types is to be included, it should be marked using
the <gi tei="yes">note</gi> element described in section <xref target="CONO"/>.
Systematic interpretive annotation is also possible using the
various methods described in chapter <xref target="SA"/>.  The examples
given here illustrate only simple cases of editorial intervention; in
particular, they permit economical encoding of two alternative
readings of a text only.  To encode more than two views of any one
segment of text, the mechanisms described in chapters <xref target="SA"/>
and <xref target="TC"/> must be used.
 </p><p>The first two pairs of elements here discussed (<gi tei="yes">sic</gi> and
<gi tei="yes">corr</gi>, <gi tei="yes">reg</gi> and <gi tei="yes">orig</gi>) may both be used to
record simultaneously a text in its <soCalled>original</soCalled>,
uncorrected and unaltered form and also in an
<soCalled>edited</soCalled> form.  In this way they resemble the pair
<gi tei="yes">abbr</gi> and <gi tei="yes">expan</gi>, described in section <xref target="CONAAB"/>.  Such paired elements enable software to move
automatically from one <soCalled>view</soCalled> of the text to the
other.
 </p><p>Three categories of editorial intervention are discussed in this
section:
<list type="bullets"><item>correction (or non-correction) of apparent errors</item><item>regularization (or non-regularization) of variant, irregular,
non-standard, or eccentric forms</item><item>editorial additions, suppressions, and omissions</item></list>
 </p><p>A more extended treatment of the use of these tags in
transcriptional and editorial work is given in chapter<xref target="PH"/>
.
 </p><div3 id="COEDCOR" name="subsection" ref="Y"><head>Correction of Apparent Errors</head><p>When the copy text is manifestly faulty, an encoder or transcriber
may elect simply to correct it without comment.  For scholarly purposes,
it will often be more generally useful to record both the correction and
the original state of the text.  The elements described here enable this
to be done is such a way as not to distract the reader.
 
<tagList style="one-line"><tagDesc tagDoc="SIC" atts="corr resp cert"/><tagDesc tagDoc="CORR" atts="sic  resp cert"/></tagList>
 </p><p>The following examples show alternative treatment of the same
material.  The copy text reads:
 
<q rend="display">Another property of computer-assisted historical
research is that data modelling must permit any one textual feature or
part of a textual feature to be a part of more than one information
model and to allow the researcher to draw on several such models
simultaneously, for example, to select from a machine-readable text
those marginal comments which indicate that the date's mentioned in the
main body of the text are incorrect.</q>
 <!-- Daniel I. Greenstein, "Encoding Standards for            --><!-- Computer-Aided Historical Research", in Modeling         --><!-- Historical Data, p. 101.                                 -->
 </p><p>An encoder may choose to correct the typographic error, either
silently or with an indication that a correction has been made, as
follows:
 
<eg><![CDATA[ ... marginal comments which indicate that the
 <corr>dates</corr> mentioned in
 the main body of the text are incorrect.]]></eg>
 </p><p>Alternatively, the encoder may simply record the typographic
error without correcting it, either without comment or with a
<gi tei="yes">sic</gi> element to indicate the error is not a transcription error
in the encoding:
<eg><![CDATA[ ... marginal comments which indicate that the
 <sic>date's</sic> mentioned in
 the main body of the text are incorrect.]]></eg>
 </p><p>If the encoder elects both to record the original source text
and to provide a correction for the sake of word-search
and other programs, either <gi tei="yes">sic</gi> or <gi tei="yes">corr</gi> may be used
with the appropriate attribute:
 
<eg><![CDATA[ ... marginal comments which indicate that the
 <sic corr='dates' resp=MSM>date's</sic> mentioned in
 the main body of the text are incorrect.]]></eg>
 
<eg><![CDATA[ ... marginal comments which indicate that the
 <corr sic="date's" resp='MSM'>dates</corr> mentioned in
 the main body of the text are incorrect.]]></eg>
 
If both readings are given, the choice between <gi tei="yes">sic</gi> and
<gi tei="yes">corr</gi> is largely a question of individual preference; since
both record the same information, either may be mechanically
transformed into the other.  If the original reading contains SGML
tags, it will prove more convenient to use <gi tei="yes">sic</gi> than
<gi tei="yes">corr</gi> (and vice versa if there are tags within the corrected
reading), since SGML tags are not recognized in attribute values.  If
both readings contain subordinate tags, then recourse <!-- may --> must
be had to the methods described in chapter <xref target="TC"/>.
 <!-- new material from PR replaces following para -->
 <!-- < p>The <gi>sic</gi> and <gi>corr</gi> tags imply a      --><!-- degree of editorial certainty about error and its        --><!-- correction and should be strictly limited in use to      --><!-- cases where such certainty exists.  They are not         --><!-- intended for use in cases where emendation is            --><!-- conjectural; for these cases, the mechanisms proposed    --><!-- in chapter <xref target=TC> are recommended.             -->
 </p><p>The <att tei="yes">cert</att> attribute on the <gi tei="yes">sic</gi> and
<gi tei="yes">corr</gi> elements permits a statement of the degree of editorial
confidence in a particular correction.  For example, using a
confidence scale of one to ten, an editor may indicate the
conjectural status of a correction by assigning a value to this
attribute of less than ten.  In the following instance, some
uncertainty is expressed concerning a commonly-accepted emendation:
 
<eg><![CDATA[An <corr sic='Antony' cert=8>Autumn</corr> it was,
That grew the more by reaping]]></eg><!-- Antony and Cleopatra, Act 5, scene 2 -->
See further the discussion in section <xref target="PHCC"/>.
 </p><p>Where the correction takes the form of adding text, the encoder
must choose whether to use the <gi tei="yes">corr</gi> (or <gi tei="yes">sic</gi>)
tag, the <gi tei="yes">add</gi> tag (see section <xref target="COEDADD"/> below),
or the more detailed facilities provided by the additional tag set for
primary source description. The following discussion may be helpful
when making this decision:
 <!-- described in chapter the <gi>supplied</gi> tag,          --><!-- available when using the additional tagset for primary   --><!-- source transcription described in chapter <xref          --><!-- target=PH>.  The following rules may be given to aid     --><!-- this choice:                                             -->
 
<list type="simple"><item>where the correction is an addition by a scribe or author
in a manuscript or other primary source (typescript, proof or galley,
etc.) then either <gi tei="yes">corr</gi> (or <gi tei="yes">sic</gi>) or <gi tei="yes">add</gi> might be
appropriate, depending on the circumstances.  The <gi tei="yes">add</gi> tag is
more expressive, and may convey information on just how the addition
was performed (hand, place, etc.) which the <gi tei="yes">corr</gi> tag cannot.
See further the discussion in section <xref target="PHSU"/>.
 </item><item>where the correction is an addition by a transcriber or editor,
correcting a perceived deficiency in the text but in circumstances where
there is no clearly assertable reason for the deficiency (as a
manuscript lacuna, or damage to the page) the <gi tei="yes">corr</gi> tag should
be used.  The <gi tei="yes">add</gi> tag should not be used in this case.
 </item><item>where the correction is an addition by a transcriber or editor,
correcting a perceived deficiency in the text and where there is a
clearly assertable reason for the deficiency (as a manuscript lacuna, or
damage to the page) which the encoder wishes to record, or when
supplying text from a parallel version of the text, the
<gi tei="yes">supplied</gi> element provided by the additional tag set for primary
source description should be used (see section <xref target="PHCC"/>).
 <!-- the <gi>supplied</gi> tag should be used with the        --><!-- <att>reason</att> attribute carrying the reason for the  --><!-- deficiency and hence the supplying of text.  The         --><!-- <gi>supplied</gi> tag should also be used when           --><!-- supplying text from a parallel version of the text.      --><!-- Neither the <gi>add</gi> nor <gi>corr</gi> tag should    --><!-- be used in these cases.                                  -->
 </item></list>
 <!-- (also removed first example since it didn;t seem to add  --><!-- very much                                                -->
 <!-- <p>In this example, an editor corrects the source text   --><!-- by supplying a word omitted apparently by mistake:       -->
 <!-- <eg><![ CDATA [ --><!--  ...and a very great <corr sic='' resp=DW>slaughter</corr> of the --><!-- Danes was made, and the part that escaped were saved by flight. --><!-- ]]> --><!-- </eg> -->
 <!-- Here, a passage omitted from one source but present in another, --><!-- <q>A</q>, is supplied: -->
 <!-- <eg><![ CDATA [ --><!--  ...they went both together up along the Thames, and a great --><!-- reinforcement came up to them both from the East Angles and the --><!-- Northumbrians.  <supplied resp=DW source=A>They then went up along --><!-- the Thames until they reached the Severn, then up along the --><!-- Severn</supplied> --><!-- ]]> --><!-- </eg> -->
 </p><p>The formal definition of these elements is as follows:
 
<dtdFrag id="DCOEDC" n="Editorial tags for correction"><tagDecl tagDoc="SIC"/><tagDecl tagDoc="CORR"/></dtdFrag>
 </p></div3><div3 id="COEDREG" name="subsection" ref="Y"><head>Regularization and Normalization</head><p>When the source text makes extensive use of variant forms or
non-standard spellings, it may be desirable for a number of reasons to
<term rend="noindex">regularize</term> it:  that is, to provide<indexed level1="regularization"/>
<soCalled>standard</soCalled> or <soCalled>regularized</soCalled> forms
equivalent to the non-standard forms.<note source="auth" place="display" anchored="Y">In some contexts, the term
<cited>regularization</cited> has a narrower and more specific
significance than that proposed here:  the <gi tei="yes">reg</gi> element may be
used for any kind of regularization, including normalization,
standardization, and modernization.</note>
 </p><p>As with other such changes to the copy text, the changes may be made
silently (in which case the TEI header should specify the types of
silent changes made) or may be explicitly marked using the following
elements:
 
<tagList style="one-line"><tagDesc tagDoc="REG" atts="orig resp"/><tagDesc tagDoc="ORIG" atts="reg  resp"/></tagList>
 </p><p>Typical applications for these elements include the production of
editions intended for student or lay readers, linguistic research in
which spelling or usage variation is not the main question at issue,
production of spelling dictionaries, etc.
 </p><p>Consider this 16th-century text:
<q rend="display">how godly a dede it is to overthrowe so wicked a race
the world may judge:  for my part I thinke there canot
be a greater sacryfice to God.</q>
 </p><p>An encoder may choose to preserve the original spelling of this
text, but simply flag it as nonstandard by using the <gi tei="yes">orig</gi>
element with no attributes specified, as follows:
 
<eg><![CDATA[how godly a <orig>dede</orig> it is to
<orig>overthrowe</orig> so wicked a race the
world may judge:  for my part I <orig>thinke</orig>
there <orig>canot</orig> be a greater
<orig>sacryfice</orig> to God.]]></eg>
 </p><p>Alternatively, the encoder may simply indicate that certain words
have been modernized by using the <gi tei="yes">reg</gi> element with no
attributes specified, as follows:
 
<eg><![CDATA[how godly a <reg>deed</reg> it is to
<reg>overthrow</reg> so wicked a race the
world may judge:  for my part I <reg>think</reg>
there <reg>cannot</reg> be a greater
<reg>sacrifice</reg> to God.]]></eg>
 </p><p>More usefully, the encoder may elect to record both old and new
spellings, so that (for example) the same electronic text may serve as
the basis of an old- or new-spelling edition:
 
<eg><![CDATA[how godly a <reg orig='dede'>deed</reg> it is to
<reg orig='overthrowe'>overthrow</reg> so wicked a race the
world may judge:  for my part I <reg orig='thinke'>think</reg>
there <reg orig='canot'>cannot</reg> be a greater
<reg orig='sacryfice'>sacrifice</reg> to God.]]></eg>
 </p><p>Or the <gi tei="yes">orig</gi> tag might be preferred
<eg><![CDATA[how godly a <orig reg='deed'>dede</orig> it is to
<orig reg='overthrow'>overthrowe</orig> so wicked a race the
world may judge:  for my part I <orig reg='think'>thinke</orig>
there <orig reg='cannot'>canot</orig> be a greater
<orig reg='sacrifice'>sacryfice</orig> to God.]]></eg><!-- Edward Barkley, describing how Essex drove the Irish     --><!-- from the plains into the woods to freeze or famish in    --><!-- winter; quoted by Nicholas P. Canny, "The Ideology of    --><!-- English Colonization:  From Ireland to America," in      --><!-- *Colonial America:  Essays in Politics and Social        --><!-- Development*, 3d edition, ed.  Stanley N. Katz and John  --><!-- M. Murrin (New York:  Knopf, 1983), p. 53; Canny's       --><!-- footnote reads "See Devereux, *Lives of Devereux*, I,    --><!-- 30-31, for Essex to Burghley, July 20, 1573, and         --><!-- *ibid*, 37-39, for Essex to Privy Council, Sept. 29,     --><!-- 1573.  Barkley to Burghley, May 14, 1574, S.P. 63/46,    --><!-- no. 15, P.R.O."                                          -->
 </p><p>The <att tei="yes">resp</att> attribute should be used to specify the agency
responsible for the regularization.  This may be an identifiable
individual, for example an editor, or a descriptive phrase such as
<cited>copyist</cited>.  For example, in the first stanza of the Old
Norse poem <title>Gr&oacute;galdr</title>, the manuscript form
<cited>dura</cited> is usually regularized in modern editions to
<cited>dyra</cited> <gloss>doors</gloss>.  The manuscript's <q>vek ek
&thorn;ik dau&eth;ra dura</q> might thus be recorded together with its
regularization in two ways, as follows:
 
<eg><![CDATA[ vek ek &thorn;ik dau&eth;ra <reg orig='dura' resp=ed>dyra</reg>]]></eg>
or:
<eg><![CDATA[ vek ek &thorn;ik dau&eth;ra <orig reg='dyra' resp=ed>dura</orig>]]></eg>
 </p><p>These elements are formally defined as follows:
 
<dtdFrag id="DCOEDR" n="Editorial tags for regularization"><tagDecl tagDoc="REG"/><tagDecl tagDoc="ORIG"/></dtdFrag>
 </p></div3><div3 id="COEDADD" name="subsection" ref="Y"><head>Additions, Deletions and Omissions</head><p>The following elements are used to indicate when words or phrases
have been omitted from, added to, or marked for deletion from, a text.
Like the other editorial elements, they allow for a wide range of
editorial practices:
 
<tagList style="one-line"><tagDesc tagDoc="GAP" atts="desc reason extent resp "/><tagDesc tagDoc="UNCLEAR" atts="reason resp"/><tagDesc tagDoc="ADD" atts="place resp hand cert"/><tagDesc tagDoc="DEL" atts="type status resp hand cert"/></tagList>
 </p><p>Encoders may choose to omit parts of the copy text for reasons
ranging from illegibility of the source or impossibility of transcribing
it, to editorial policy, e.g. a systematic exclusion of poetry or prose
from an encoding.  The full details of the policy decisions concerned
should be documented in the TEI Header (see section <xref target="HD5"/>).
Each place in the text at which omission has taken place should be
marked with a <gi tei="yes">gap</gi> element, with optionally further information
about the reason for the omission, its extent and the person or agency
responsible for it, as in the following examples:
 
<eg><![CDATA[ <gap desc="Prose commentary" reason="sampling"
       extent="120 lines" resp=PR>]]></eg>
 
<eg><![CDATA[ ... Their arrangement with respect to Jupiter and to each
 other was as follows:
 <gap desc="diagram" reason="sampling" extent="2 cm x 1 col">
 That is, there were two starts on the easterly side and one
 to the west; ...]]></eg><!-- Galileo, The Starry Messenger, quoted by Tufte,          --><!-- Envisioning Information, p. 97.  Siderevs Nuncivs ...    --><!-- (Venetiis:  Apud Thomam Baglionum, 1610).                --><!-- Figure looks like this:                                  --><!--                                                          --><!-- East         *        *  O      *                   West --><!--                                                          -->
 
<eg><![CDATA[ <gap reason="illegible" desc="ink blot" extent="two words">]]></eg>
 
<eg><![CDATA[ <gap reason='overwriting, illegible'
       resp='H1'
       extent='8 chars'>]]></eg>
 </p><p>The <gi tei="yes">add</gi> and <gi tei="yes">del</gi> elements may be used to record
where words or phrases have been added or deleted in the copy text.
They are not appropriate where longer passages have been added or
deleted, which span several SGML elements; for these, the elements
<gi tei="yes">addSpan</gi> and <gi tei="yes">delSpan</gi>, or other mechanisms described in
section <xref target="PH"/> must be used.
 </p><p>Additions to a text may be recorded for a number of reasons.
Sometimes they are marked in a distinctive way in the source text, for
example by brackets or insertion above the line
(<term rend="noindex">supralinear</term> insertion),<indexed level1="additions" level2="supralinear"/><indexed level1="insertions" level2="supralinear"/><indexed level1="supralinear insertions"/>
as in the following example, taken from a 19th century manuscript:
 
<eg><![CDATA[The story I am going to relate is true as to its main
facts, and as to the consequences <add
place='supralinear' resp='auth'>of these facts</add>
from which this tale takes its title.]]></eg><!-- Mrs Gaskell, The Grey Woman, MS -->
 </p><p>The <gi tei="yes">add</gi> element should not be used to mark editorial
changes, such as supplying a word omitted by mistake from the source
text or a passage present in another version.  In these cases, either
the <gi tei="yes">corr</gi> or <gi tei="yes">supplied</gi> tags should be used, as discussed
above in section <xref target="COEDCOR"/>, and in section <xref target="PHCC"/>, respectively.
 <!-- LB added following discussion of unclear -->
 </p><p>The <gi tei="yes">unclear</gi> element is used to mark passages in the original
which cannot be read with confidence, or about which the transcriber is
uncertain for other reasons, as for example when transcribing a
partially inaudible or illegible source.  Its <att tei="yes">reason</att> and
<att tei="yes">resp</att> attributes are used, as with the <gi tei="yes">gap</gi> element,
to indicate the cause of uncertainty and the person responsible for the
conjectured reading.
 </p><p>For example:
 
<eg><![CDATA[<l>And where the sandy mountain Fenwick scald</>
<l><unclear reason="ink blot" resp=LB>The</unclear> sea between
   yet hence his pray'r prevail'd</>]]></eg><!-- Marvell, Horatian ode, ms pages from Bod MS Eng Poet d.49 -->
 
or from a spoken text:
 
<eg><![CDATA[ 
and then <unclear reason='passing truck'>marbled queen</unclear>
 ]]></eg>
 
Where the material affected is entirely illegible or inaudible, the
<gi tei="yes">gap</gi> element discussed above should be used in preference.
 <!-- material here cut at PR's suggestion -->
 </p><p>The <gi tei="yes">del</gi> element is used to mark material which is deleted in
the source but which can still be read with some degree of confidence,
as opposed to material which has been omitted by the encoder or
transcriber either because it is entirely illegible or for some other
reason.  This is of particular importance in transcribing manuscript
material, though deletion is also found in printed texts, sometimes for
humorous purposes:
 
<eg><![CDATA[<l>One day I will sojourn to your shores</>
<l>I live in the middle of England</>
<l>But!</>
<l>Norway! My soul resides in your watery
   <del type='overstrike'>fiords fyords fiiords</del></>
<l>Inlets.</>]]></eg> <!-- S. Townsend: The growing pains of Adrian Mole (1984) p.43 -->
 </p><p>The <att tei="yes">type</att> attribute may be used to distinguish different
methods of deletion in manuscript or typescript material, as in this
line from the typescript of Eliot's <title>Waste Land</title>:
 
<eg><![CDATA[<l><del type=overtyped>Mein</del> Frisch
   <del type=overstrike>schwebt</del> weht der Wind</>]]></eg></p><p>Deletion in manuscript or typescript is often associated with
addition:
 
<eg><![CDATA[<l><del type=overstrike>Inviolable</del>
   <add place=infralinear>Inexplicable</add>
   splendour of Corinthian white and gold</>]]></eg> <!-- The Waste Land. a facsimile and transcript... edited by -->
      <!-- Valerie Eliot. Faber, 1971. p.37 -->
 
 </p><p>The <gi tei="yes">del</gi> element should not be used where the deletion is
such that material cannot be read with confidence, or read at all, or
where the material has been omitted by the transcriber or editor for
some other reason.  Where the material cannot be read with confidence
following deletion, the <gi tei="yes">unclear</gi> tag should be used with the
<att tei="yes">reason</att> attribute indicated that the difficulty of
transcription is due to deletion.  Where material has been omitted by
the transcriber or editor, this may be indicated by use of the
<gi tei="yes">corr</gi> (or <gi tei="yes">sic</gi>) and <gi tei="yes">gap</gi> elements.  Observe that
the distinction between recommended uses of the <gi tei="yes">del</gi>,
<gi tei="yes">corr</gi> and <gi tei="yes">gap</gi> tags parallels the distinction drawn
between the <gi tei="yes">add</gi>, <gi tei="yes">corr</gi> and <gi tei="yes">supplied</gi> tags in
section <xref target="COEDCOR"/> and section <xref target="PHCC"/>:
 
<list type="simple"><item>where the correction is a deletion by a scribe or author in a
manuscript or other primary source (typescript, proof or galley, etc.)
then either <gi tei="yes">corr</gi> (or <gi tei="yes">sic</gi>) or <gi tei="yes">del</gi> might be
appropriate, depending on the circumstances.  The <gi tei="yes">del</gi> tag is
more expressive, and may convey information on just how the deletion
was performed (hand, place, etc.) which the <gi tei="yes">corr</gi> tag cannot.
See further the discussion in section <xref target="PHSU"/>.
 </item><item>where the correction is a deletion by a transcriber or editor,
correcting a perceived superfluity in the text but in circumstances
where there is no clearly assertable reason for the superfluity (as a
spurious addition) the <gi tei="yes">corr</gi> tag should be used.  The
<gi tei="yes">del</gi> tag should not be used in this case.
 </item><item>where the correction is a deletion by a transcriber or editor,
correcting a perceived superfluity in the text where there is a
clearly assertable reason for the superfluity (as a spurious
addition) the <gi tei="yes">gap</gi> tag should be used with the
<att tei="yes">reason</att> attribute carrying the reason for the superfluity
and hence the deletion of text.  Neither the <gi tei="yes">del</gi> nor
<gi tei="yes">corr</gi> tag should be used in these cases.</item></list>
 
 </p><p>For any detailed transcription of a manuscript or typescript with
more than trivial amounts of alteration, the reader should consult
chapter <xref target="TC"/>, and chapter <xref target="PH"/>.
 </p><p>These elements are formally defined as follows:
 
<dtdFrag id="DCOEDA" n="Other editorial tags"><tagDecl tagDoc="GAP"/><tagDecl tagDoc="ADD"/><tagDecl tagDoc="DEL"/><tagDecl tagDoc="UNCLEAR"/></dtdFrag><?tei:EOF p2coed.odd ??>

 <!-- COxr Cross References                                    --><?tei:SOF p2coxr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2coxr.odd,v $
# Revision 1.3  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.2  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# --><!-- Revisions:                                               --><!-- 94-03-25 : MSM : typos corrected as per J. Lavagnino     --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 92-12-10 : MSM : correct references to Loc, now pointer  --><!-- 92-12-09 : MSM : introduce class Loc explicitly          --><!-- 92-12-09 : MSM : cosmetic copy editing                   --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-09 : MSM : add (vacuous!) example of targOrder     --><!-- 92-12-07 : MSM : complete run-through for publication    --><!-- 92-12-07 : MSM : begin cleanup for publication           --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --></p></div3></div2><div2 id="COXR" name="section" ref="Y"><head>Simple Links and Cross References</head><p>Cross-references or links between one location in a document and
another, or between one location and several others, may be encoded
using the elements <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi>, as discussed in this
section.  These elements both <soCalled>point</soCalled> from one
location in a document, the place that the element itself appears, to
another (or to several), specified by the <att tei="yes">target</att> attribute.
Linkages of several other kinds are also provided for in these
guidelines; see further chapter <xref target="SA"/>.
 </p><p>The pointing facility of these elements depends on the ability to
supply a unique identifier for any element in the TEI scheme, using the
global <att tei="yes">id</att> attribute.  Where the object or objects of a
cross-reference are not identifiable in this way, either because they
are located in a distinct SGML document or because no <att tei="yes">id</att>
attribute is available, the elements <gi tei="yes">xptr</gi> or <gi tei="yes">xref</gi> may
be used instead.<note source="auth" place="display" anchored="Y">See chapter <xref target="SA"/>, for a discussion of
these elements and the extended syntax they provide for <soCalled>hypertext</soCalled> links.</note> Alternatively, if no explicit link is
to be encoded, but it is simply required to mark the phrase as a
cross-reference, the <gi tei="yes">ref</gi> element may be used without a
<att tei="yes">target</att> attribute.
 
<tagList style="one-line"><tagDesc tagDoc="PTR" atts="target"/><tagDesc tagDoc="REF" atts="target"/></tagList>
 </p><p>The elements <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi> share, as members of the
element class <ident tei="yes" type="class">pointer</ident>, the following
attributes:
 
<adList classDoc="POINTER" atts="type resp crdate targType targOrder evaluate"/>
 </p><p>The shared attributes of the two elements may be used in the same
way; the difference between the elements is that while the <gi tei="yes">ptr</gi>
element is empty, the <gi tei="yes">ref</gi> element may contain phrases
specifying, or defining more exactly, the target of a cross reference,
which form the content of the element.  Since its content thus serves as
a human-readable pointer, in the simplest case a <gi tei="yes">ref</gi> element
need not identify its target in any other way.  For example:
 
<eg><![CDATA[    See <ref>section 12 on page 34</ref>.]]></eg>
 </p><p>More usually, it will be desirable to identify the target of the
cross-reference using the <att tei="yes">target</att> attribute, so that
processing software can access it directly, for example to implement a
linkage or to generate an appropriate reference.  Assuming that section
12 in the previous example has been tagged <tag compl="full" tei="yes">div1 id=SEC12</tag>, the
same cross reference might more exactly be encoded as
 
<eg><![CDATA[    See especially <ref target=SEC12>section 12 on page 34</ref>.]]></eg>
 </p><p>If the text for the cross reference is to be generated according to a
fixed pattern, or if no text is to appear in the body of the cross
reference, the <gi tei="yes">ptr</gi> element would be used as follows:
 
<eg><![CDATA[    See in particular <ptr target=SEC12>.]]></eg>
 </p><p>A cross-reference may point to any number of locations simultaneously,
simply by giving more than one identifier as the value of its
<att tei="yes">target</att> attribute.  This may be particularly useful where
an analytic index is to be encoded, as in the following example:
<eg><![CDATA[    <list>
    <item>Saints aid rejected in mel. <ptr target=P299></item>
    <item>Sallets censured <ptr target="P143 p144"></item>
    <item>Sanguine mel. signs <ptr target="P263 p312 p332"></item>
    <item>Scilla or sea onyon, a purger of mel. <ptr target=P442></item>
   <!-- ... -->
    </list>]]></eg><!-- Burton: Anatomy of Melancholy, 16th ed 1651, reprinted   --><!-- 1846, p743                                               -->
 
Here the targets of the cross references are simply page numbers; it is
assumed that corresponding elements with identifiers <code tei="yes" type="val">p299</code> <code tei="yes" type="val">p143</code>, etc. have been provided
in the body of the text.  If it is desired to check that the target
elements are of a particular type, the <att tei="yes">targType</att> (target type)
attribute may be specified:
 
<eg><![CDATA[    <list>
    <item>Saints aid rejected in mel <ptr target=P299 targType=pb></item>
    <item>Sallets censured <ptr target="P143 p144" targType=pb></item>
    <!-- ... -->
    </list>]]></eg>
 
Here, a processing application can check that the elements with
identifiers <code tei="yes" type="val">p299</code>, <code tei="yes" type="val">p143</code>, and
<code tei="yes" type="val">p144</code> are all <gi tei="yes">pb</gi> (page-break) elements.
It is a semantic error in a text if the targets given do not match the
values specified on a <att tei="yes">targType</att> attribute.
 </p><p>The <att tei="yes">type</att> and <att tei="yes">resp</att> attributes may be used, as
elsewhere, to categorize the cross reference according to any system of
importance to the encoder and to supply a code identifying the person or
agency responsible for the cross reference.  If bibliographic references
require special processing (e.g. in order to provide a consistent
short-form reference), they might be tagged thus:
 
<eg><![CDATA[ Similar forms, often called <term rend='ldquo
 rdquo'>rewriting systems</term>, have a long
 history among mathematicians, but the specific form
 of <ptr targType=fig target=FIG22> was first
 studied extensively by Chomsky <ptr type=bibliog
 targType='bibl bibl.struct bibl.full' target=CHOM59>.]]></eg>
 <!-- Dick Grune and Ceriel J. H. Jacobs, Parsing              --><!-- Techniques:  A Practical Guide (New York, London:        --><!-- Ellis Horwood, 1990), p. 24.                             -->
 
Here <code tei="yes" type="frag">type=bibliog</code> signals for the processing
appropriate to a bibliographic reference, while <q>targType='bibl
bibl.struct bibl.full'</q> restricts the legal targets to bibliographic
elements, and <code tei="yes" type="frag">target=Chom59</code> indicates which
bibliographic element actually is being referred to.  For further
discussion of bibliographic references, see section <xref target="COBIXR"/>.
 </p><p>If the order in which the objects of a multi-headed cross reference
are specified is of importance, the <att tei="yes">targOrder</att> (target order)
attribute should be specified.
 <!-- example needed -->
 
<eg><![CDATA[<p>The following discussions of this topic should
be consulted for further information:
<ptr target='CH3 sec332 sec45 sec722' targOrder=Y>]]></eg>
 </p><p>The <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi> tags have many applications in
addition to the simple cross-referencing facilities illustrated in this
section.  In conjunction with the analytic tools discussed in chapters<xref target="SA"/>
, <xref target="AI"/>, and <xref target="FS"/>, they may be
used to link analyses of a text to their object, to combine
corresponding segments of a text, or to align segments of a text with a
temporal or other axis or with each other.
 </p><p>These elements are formally defined as follows:
<dtdFrag id="DCOXR" n="Simple cross references"><claDecl classDoc="POINTER" type="atts"/><tagDecl tagDoc="PTR"/><tagDecl tagDoc="REF"/></dtdFrag>
 <?tei:EOF p2coxr.odd ??>

 <!-- COli Lists (P1 5.3.8)                                    --><?tei:SOF p2coli.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2coli.odd,v $
# Revision 1.3  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
# --><!-- P2.COli: Lists                                           --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 92-12-09 : MSM : cosmetic copy editing                   --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-07 : MSM : revise for release                      --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 92-11-09 : MSM : defang < note > in comment              --><!-- 20 oct : LB:   add some examples; reorder somewhat       --><!-- 1-7 oct 92 : LB : change ids to new scheme               --><!-- 24 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0 sec. 5.3.8       -->
 </p></div2><div2 id="COLI" name="section" ref="Y"><head>Lists</head><p>The following elements are provided for the encoding of lists,
their constituent items, and the labels or headings associated
with them:
 
<tagList style="one-line"><tagDesc tagDoc="LIST" atts="type"/><tagDesc tagDoc="ITEM" atts="n"/><tagDesc tagDoc="LABEL"/><tagDesc tagDoc="HEAD"/><tagDesc tagDoc="HEADLAB"/><tagDesc tagDoc="HEADIT"/></tagList>
 </p><p>The <gi tei="yes">list</gi> element should be used to mark any kind of
<term rend="noindex">list</term>:
numbered, lettered, bulleted, or unmarked.  Lists formatted as such in
the copy text should in general be encoded using this element, with an
appropriate value for the <att tei="yes">type</att> attribute.  Lists given as
run-on text may also be encoded using this element, where this is felt
to be appropriate.
 </p><p>Each distinct item in the list should be encoded as a distinct
<gi tei="yes">item</gi> element.  If the numbering or other identification for the
items in a list is unremarkable and may be reconstructed by any
processing program, no enumerator need be specified.  If however an
enumerator is retained in the encoded text, it may be supplied either by
using the <att tei="yes">n</att> attribute on the <gi tei="yes">item</gi> element, or by
using a <gi tei="yes">label</gi> element.  The following examples are thus
equivalent:
 
<eg><![CDATA[I will add two facts, which have seldom occurred in
the composition of six, or at least of five quartos.
<list type=ordered rend=runon>
<label>(1)</><item>My first rough manuscript, without any
intermediate copy, has been sent to the press.</item>
<label>(2)</><item>Not a sheet has been seen by any human
eyes, excepting those of the author and the printer:
the faults and the merits are exclusively my own.</item>
</list>]]></eg>
<eg><![CDATA[I will add two facts, which have seldom occurred in
the composition of six, or at least of five quartos.
<list type=ordered rend=runon>
<item n='1'>My first rough manuscript, without any
intermediate copy, has been sent to the press.</>
<item n='2'>Not a sheet has been seen by any human
eyes, excepting those of the author and the printer:
the faults and the merits are exclusively my own.</>
</list>]]></eg>
 
The two styles may not be mixed in the same list:  if one item is
preceded by a label, all must be.
 </p><p>A list need not necessarily be displayed in list format.  For
example,
 
<eg><![CDATA[On those remote pages it is written that animals are
divided into <list><item n='a'>those that belong to the
Emperor,</><item n='b'> embalmed ones, </><item n='c'> those
that are trained, </><item n='d'> suckling pigs, </><item n='e'>
mermaids,  </><item n='f'> fabulous ones, </><item n='g'> stray
dogs, </><item n='h'> those that are included in this
classification, </><item n='i'> those that tremble as if they
were mad, </><item n='j'> innumerable ones, </><item n='k'> those
drawn with a very fine camel's-hair brush, </><item n='l'>
others, </><item n='m'> those that have just broken a flower
vase, </><item n='n'> those that resemble flies from a
distance.</></list>]]></eg><!-- Borges, tr. R. Simms 'The analytical language of John Wilkins' --><!-- in Monegal & Reid, Borges: a reader, (Dutton, 1981), p 141 -->
 </p><p>A list may be given a heading or title, for which the <gi tei="yes">head</gi>
element should be used, as in the next example, which also demonstrates
simple use of the <gi tei="yes">label</gi> element to mark a tabular or glossary
list in which each item is associated with a word or phrase rather than
a numeric or alphabetic enumerator:
 
<eg><![CDATA[<list type=gloss>
<head>Report of the conduct and progress of Ernest Pontifex.
Upper Vth form &mdash half term ending Midsummer 1851</head>
<label>Classics</><item>Idle listless and unimproving</>
<label>Mathematics</><item>ditto</>
<label>Divinity</><item>ditto</>
<label>Conduct in house</><item>Orderly</>
<label>General conduct</><item>Not satisfactory, on account
of his great unpunctuality and inattention to duties</>
</list>]]></eg><!-- S Butler, Way of all Flesh, -->
 </p><p>In such a list, the individual items have internal structure.  In
complex cases, where list items contain many components, the list is
better treated as a <term rend="noindex">table</term>, <indexed level1="tables" level2="and lists"/> on which see chapter <xref target="FT" type="div1"/>.  A particularly important instance of the simple two-column
table is the <soCalled>glossary list</soCalled>, which should be marked
by the tag <tag compl="full" tei="yes">list type=gloss</tag>.  In such lists, each
<gi tei="yes">label</gi> element contains a term and each <gi tei="yes">item</gi> its gloss;
it is a semantic error for a list tagged with <code tei="yes" type="frag">type=gloss</code> not to have labels.  For example:
 <!-- Moreland and Fleischer, Latin:  An Intensive Course, 53. -->
 
<eg><![CDATA[<list type=gloss>
<head>Unit Three -- Vocabulary</head>
<label lang=la>acerbus, -a, -m       </><item>bitter, harsh</>
<label lang=la>ager, agr&imacr;, M.  </><item>field</>
<label lang=la>audi&omacr;, &imacr;re,
       &imacr;v&imacr;, &imacr;tus   </><item>hear, listen (to)</>
<label lang=la>bellum, -&imacr;, N.  </><item>war</>
<label lang=la>bonus, -a, -um        </><item>good</>
<!-- etc. -->
</list>]]></eg>
 
Additionally, the  <gi tei="yes">term</gi> and <gi tei="yes">gloss</gi> elements discussed
in section <xref target="COHQU"/> might be used to make explicit the role
that each column in the glossary list has, as follows:
 
<eg><![CDATA[<list type=gloss>
<head>Unit Three -- Vocabulary</head>
<label><term lang=la>acerbus, -a, -m</term></>
<item><gloss>bitter, harsh</gloss></item>
<label><term lang=la>ager, agr&imacr;, M. </term></>
<item><gloss>field</gloss></item>
<label><term lang=la>audi&omacr;, &imacr;re,
       &imacr;v&imacr;, &imacr;tus  </term></>
<item><gloss>hear, listen (to)</gloss></item>
<label><term lang=la>bellum, -&imacr;, N. </term></>
<item><gloss>war</gloss></item>
<label><term lang=la>bonus, -a, -um</term></>
<item><gloss>good</gloss></item>
<!-- etc. -->
</list>]]></eg>
 
Note in the above examples the use of the global <att tei="yes">lang</att>
attribute to specify on the <gi tei="yes">label</gi> (or <gi tei="yes">term</gi>) element
what language the term is from.  For further discussion of the
<att tei="yes">lang</att> attribute see section <xref target="STGA" type="div2"/>, and
section <xref target="CHSH" type="div2"/>.  A more elaborate markup for this
glossary would distinguish the headword forms from the grammatical
information (principal parts and gender), using tags described more
fully in chapters <xref target="TE" type="div1"/> or <xref target="DI" type="div1"/>.
 </p><p>In addition to the <gi tei="yes">head</gi> element used to supply
a title or heading for the whole list, headings for the two
columns of a glossary-style list may be specified using
the two special elements <gi tei="yes">headLabel</gi> and <gi tei="yes">headItem</gi>:
 
<eg><![CDATA[The simple, straightforward statement of an idea is
preferable to the use of a worn-out expression.
<list type=gloss>
<headLabel>TRITE</>
<headItem>SIMPLE, STRAIGHTFORWARD</>
<label>bury the hatchet  </><item>stop fighting, make peace</>
<label>at loose ends     </><item>disorganized</>
<label>on speaking terms </><item>friendly</>
<label>fair and square   </><item>completely honest</>
<label>at death's door   </><item>near death</>
</list>]]></eg><!-- Warriner's English Composition p. 280                    -->
 </p><p>The elements <gi tei="yes">label</gi>, <gi tei="yes">head</gi>, <gi tei="yes">headLabel</gi>, and
<gi tei="yes">headItem</gi> may contain only phrase-level elements.  The
<gi tei="yes">item</gi> element however may contain paragraphs or other
<soCalled>chunks</soCalled>, including other lists.  In this example, a
glossary list contains two items, each of which is itself a simple list:
 
<eg><![CDATA[<list type=gloss><label>EVIL</label>
<item><list type=simple>
   <item>I am cast upon a horrible desolate island, void
          of all hope of recovery.</item>
   <item>I am singled out and separated as it were from
         all the world to be miserable.</item>
   <item>I am divided from mankind &mdash a solitaire; one
           banished from human society.</item>
     </list> <!-- end of first nested list --></item>
<label>GOOD</label>
<item><list type=simple>
     <item>But I am alive; and not drowned, as all my
              ship's company were.</item>
     <item>But I am singled out, too, from all the ship's
             crew, to be spared from death...</item>
     <item>But I am not starved, and perishing on a barren place,
            affording no sustenances....</item>
     </list><!-- end of second nested list --></item>
</list><!-- end of glossary list -->]]></eg><!-- D Defoe,  Robinson Crusoe  -->
 </p><p>Lists of different types may be nested to arbitrary depths in this
way.
 </p><p>The formal declarations for lists and list items are as follows.
<dtdFrag id="DCOLI" n="Lists and List Items"><tagDecl tagDoc="LIST"/><tagDecl tagDoc="ITEM"/><tagDecl tagDoc="LABEL"/><tagDecl tagDoc="HEAD"/><tagDecl tagDoc="HEADLAB"/><tagDecl tagDoc="HEADIT"/></dtdFrag><?tei:EOF p2coli.odd ??>

 <!-- COno Notes (P1 5.3.9)                                    --><?tei:SOF p2cono.odd ??><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2cono.odd,v $
# Revision 1.9  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.8  1994/08/29  15:43:52  cmsmcq
# Fixes for unreachability problems
#
# Revision 1.7  1994/04/01  16:18:13  msmcq
# Suppress SPAN (moved to AI)
#
# Revision 1.6  1994/03/27  21:45:15  msmcq
# Correction of typos from DB, JL, HG, and WWP
#
# Revision 1.5  1994/03/01  03:53:49  msmcq
# suppress FILE attribute (was causing double declarations)
# --><!-- P2.234 : Notes                                           --><!-- Revisions:                                               --><!-- 10 jan 98 : LB : fix egs --><!-- 94-08-04 : MSM : add note that INDEX is member of        --><!-- 94-08-04 : MSM : METADATA class.                         --><!-- 94-03-30 : MSM : suppress span (has moved to AI)         --><!-- 94-02-28 : MSM : suppress FILE att on dCOno              --><!-- 21 dec : LB : change target /target.end on span to from/to --><!-- 93-06-02 : L B : rename div.gen as divGen                --><!-- 92-12-10 : MSM : correct typo in level3/level4 on index  --><!-- 92-12-09 : MSM : marginalia are not all notes            --><!-- 92-12-09 : MSM : spell check for publication             --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-09 : MSM : add documentation of divGen            --><!-- 92-12-06 : MSM : add index tags                          --><!-- 92-11-17 : MSM : remove non-SGML eof character           --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 5 Oct 92: LB : change IDs, move taglist to start, add eg --><!-- 14 May 92 : CMSMcQ : revise.                             --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->
 </p></div2><div2 id="CONO" name="section" ref="Y"><head>Notes, Annotation, and Indexing</head><div3 id="CONONO" name="subsection" ref="Y"><head>Notes and Simple Annotation</head><p>The following elements are provided for the encoding of
discursive notes, either already present in the copy text or
supplied by the encoder:
 
<tagList style="one-line"><tagDesc tagDoc="NOTE" atts="n type resp place anchored target targetEnd"/></tagList><!-- <tagDesc tagDoc=SPAN                                     --><!--          atts='resp type value from to'>                 -->
 </p><p>A <term rend="noindex">note</term><indexed level1="notes"/>
is any additional comment found in a text, marked in some way as being
out of the main textual stream.  All notes should be marked using the
same tag, <gi tei="yes">note</gi>, whether they appear as block notes in the main
text area, at the foot of the page, at the end of the chapter or volume,
in the margin, or in some other place.
 </p><p>Notes may be in a different hand or typeface, may be authorial or
editorial, and may have been added later.  Attributes may be used to
specify these and other characteristics of notes, as detailed below.
 </p><p>Where possible, the body of a note should be inserted in the text at
the point at which its identifier or mark first appears.  This may not
be possible for example with marginal notes, which may not be anchored
to an exact location.  For simplicity, it may be adequate to position
marginal notes before the relevant paragraph or other element.  In some
cases, however, it may be desirable to transcribe notes not at their
point of attachment to the text but at their point of appearance (at the
end of the volume, or the end of the chapter --- not, in general, when
the notes appear at the foot of the page); in this case the
<att tei="yes">target</att> and <att tei="yes">targetEnd</att> attributes should be used to
specify the point of attachment.  In some cases, the note is explicitly
attached not to a point but to a span of text; for a full discussion of
pointing to points and spans in the text, see section <xref target="COXR" type="div1"/>.
 
 </p><p>Examples:
<eg><![CDATA[<l>The self-same moment I could pray
<l>And from my neck so free
<l>The albatross fell off, and sank
<l>Like lead into the sea.
<note type=auth place=margin>The spell begins to break</note>]]></eg><!-- STC, Anc Mar -->
 
<eg><![CDATA[Collections are ensembles of distinct entities or objects
of any sort.<note place=foot n=1>We explain below why we use
the uncommon term <mentioned>collection</mentioned>
instead of the expected <mentioned>set</mentioned>.
Our usage corresponds to the <mentioned>aggregate</mentioned> of many
mathematical writings and to the sense of <mentioned>class</mentioned>
found in older logical writings.
</note>
The elements ...]]></eg>
 </p><p>In addition to transcribing notes from the copy text, researchers may
wish to annotate the electronic text itself, by attaching analytic notes
in some structured vocabulary to particular passages of text, e.g. to
specify the topics or themes of a text.  The empty <gi tei="yes">span</gi> element
is provided for such applications; it is available only when the
additional tag set for simple analysis is selected (see section<xref target="AISP"/>
).
 <!-- <p>The <gi>span</gi> tag may be used to mark any span    --><!-- of text; for example, the structural divisions           --><!-- assigned to a narrative by an interpreter:               -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              -->
 <!-- <p id=P1><anchor id=A1>Sigmund, the son of Volsung,      --><!-- was a king in Frankish country.  Sinfiotli was the       --><!-- eldest of his sons ...  <anchor id=A2> <s id=S4A>But     --><!-- Sinfiotli ... wooed the same woman</s> <s id=S4B> and    --><!-- Sinfiotli killed him over it.</s> <anchor id=A4>And      --><!-- when he came home, Borghild asked him to go away, but    --><!-- Sigmund offered her weregild, and she was obliged to     --><!-- accept it.  At the funeral feast Borghild was serving    --><!-- beer.  She took poison, a big drinking horn full, and    --><!-- brought it to Sinfiotli.  ...  Sinfiotli drank it off    --><!-- and at once fell dead.  <anchor=A5>                      -->
 <!-- <p id=P2>Sigmund carried him a long way in his arms      --><!-- and came to a long, narrow fjord, and there was a        --><!-- small boat there and a man in it.  ...                   --><!--                                                          --><!-- <p id=P3>King Sigmund lived a long time in Denmark ...   --><!--                                                          --><!-- <p id=P4>Sigmund and all his sons were tall ...          --><!--                                                          --><!-- <s id=NIL></s>                                           -->
 <!-- <span resp=TMA type='structural unit' value='introduction' --><!--         from=A1 to=A2>                                   --><!-- <span resp=TMA type='structural unit' value='conflict'   --><!--         from=s4a>                                        --><!-- <span resp=TMA type='structural unit' value='climax'     --><!--         from=s4b>                                        --><!-- <span resp=TMA type='structural unit' value='revenge'    --><!--         from=A4 to=A5>                                   --><!-- <span resp=TMA type='structural unit' value='reconciliation' --><!--         from=nil>                                        --><!-- <span resp=TMA type='structural unit' value='aftermath'  --><!--         from=P2 to=P4>                                   --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p><p>The formal declarations for the <gi tei="yes">note</gi> element is this:
 
<dtdFrag id="DCONO" n="Annotation"><tagDecl tagDoc="NOTE"/><dtdRef dtdFrag="DCONOIX"/></dtdFrag><!-- <tagDecl tagDoc=SPAN>                                    -->
 <!-- P2.23e : Other stuff                                     --><!-- Revisions:                                               --><!-- 92-12-06 : MSM : move to p2cono from p2comi              --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 92-10-23 : MSM : new name                                --><!-- 25 May 92 : CMSMcQ : revise                              --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2, add tag docs.     --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0                  -->
 </p></div3><div3 id="CONOIX" name="subsection" ref="Y"><head>Index Entries</head><p>Machine-readable versions of existing texts rarely reproduce any
index published with the copy text.  Should a printed index be
transcribed, the <gi tei="yes">div1</gi> tag or a <gi tei="yes">div</gi> tag at an
appropriate level should be used to demarcate the index, and the index
itself may be transcribed as a structured list or table.
 </p><p>It is convenient, however, to be able to generate a new index
from a machine-readable text, whether the text is being written for the
first time with the tags here defined or was transcribed from some other
source.  The <gi tei="yes">index</gi> tag is provided for this purpose; it
may be useful for marking points of particular interest for whatever
reason, and not merely for generating printed indexes for a printed
version of the text.  The <gi tei="yes">divGen</gi> element indicates the
point at which an index, or any other generated text (e.g. a table
of contents), is to appear in the output of a text production process.
<tagList style="one-line"><tagDesc tagDoc="INDEX" atts="level1 level2 level3 level4 index"/><tagDesc tagDoc="DIVGEN" atts="type"/></tagList>
 </p><p>The tag <tag compl="full" tei="yes">index</tag> associates up to four levels of index
terms with a specific point in the text.  The index terms are supplied
in attributes named <att tei="yes">level1</att>, <att tei="yes">level2</att>,
<att tei="yes">level3</att>, and <att tei="yes">level4</att>.  An <att tei="yes">index</att>
attribute associates the entry with a particular index, so multiple
indices are possible.
 </p><p>All index terms must be supplied as attribute values; no part of the
text itself is taken as a term.  This may require words or phrases to be
repeated, as illustrated below; it also allows spelling to be
normalized, as the example shows:
 
<eg> <![CDATA[
The students understand procedures for Arabic lemmatisation
<index level1='Arabic lemmatization'>and are beginning
to build parsers.]]></eg>
 </p><p>The <gi tei="yes">divGen</gi> element marks the place at which an index
generated from the <gi tei="yes">index</gi> elements should be inserted into the
output of a processing program; typically, this will be at some point
within the back matter of the document; its <att tei="yes">type</att> attribute
should be used to specify which index is to be generated, and its
<att tei="yes">n</att> attribute to specify a name for the index:
 
<eg><![CDATA[<back>
<div><head>Examples</head>
<p> ...
</div>
<div><head>Bibliography</head>
<listBibl>
  <bibl> ... </bibl>
</listBibl>
</div>
<divGen type='index 1' n='Index Nominum'>
<divGen type='index 2' n='Index Rerum'  >
</back>]]></eg>
 </p><p>The formal declaration for these elements is as follows.
The <gi tei="yes">index</gi> element is a member of the element class
<ident tei="yes" type="class">metadata</ident> and may thus be used
anywhere within the <gi tei="yes">text</gi> element.
<dtdFrag id="DCONOIX" n="Index Entries"><tagDecl tagDoc="INDEX"/><tagDecl tagDoc="DIVGEN"/></dtdFrag>
 <?tei:EOF p2cono.odd ??>

 <!-- COrs Reference Systems (P1 5.6)                          --><?tei:SOF p2cors.odd ??><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2cors.odd,v $
    * Revision 1.10  1998/01/30 16:41:14  tei
    * Fix log format.
    *
    * Revision 1.9  1998/01/30 15:54:50  tei
    * more eg typos
    * 
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.7  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.6  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * 
    * Revision 1.5  1994/02/17  20:31:08  msmcq
    * revision for SC review
    *--><!-- P2COrs : Reference Systems                               --><!-- Revisions:                                               --><!-- 10 jan 98 : LB : fix egs --><!-- 94-04-07 : MSM : trivial typos                           --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-26 : MSM : corrections from DB                     --><!-- 94-03-26 : MSM : typos from JL et al.                    --><!-- 94-02-17 : MSM : Added RCS id                            --><!-- 94-02-15 : MSM : supply missing /eg                      --><!-- 25 dec 93: LB: change milestone tags; add exx.           --><!-- 92-12-09 : MSM : correct two typos, one important        --><!-- 92-12-09 : MSM : cosmetic copy editing                   --><!-- 92-12-09 : MSM : add space after some end-tags           --><!-- 92-12-07 : MSM : revise for publication                  --><!-- 92-11-09 : MSM : suppress leading blanks in some elements --><!-- 19 Oct 92 : LB some stylistic changes                    --><!-- 1 oct 92 : LB : change IDs to new scheme                 --><!-- 14 May 92 : CMSMcQ : assign numeric IDs to sections.     --><!-- 29-30 Apr 92 : CMSMcQ : reorder, revise somewhat.        --><!-- 21 Apr 92 : CMSMcQ : retag for TEI P2.                   --><!-- 16 Oct 90 : CMSMcQ : TEI P1 version 1.1                  --><!-- 17 Jul 90 : CMSMcQ : TEI P1 version 1.0 (z69, sec. 5.6)  --><!-- Mar-Apr 89 : EM : drafted                                -->
 </p></div3></div2><div2 id="CORS" name="section" ref="Y"><head>Reference Systems</head><p>By <cited>reference system</cited> we mean the system by which names
or references are associated with particular passages of a text (e.g.
<cited>Ps. 23:3</cited> for the third verse of Psalm 23 or <cited>Amores
2.10.7</cited> for Ovid's <title>Amores</title>, book 2, poem 10, line
7).  Such names make it possible to mark a place within a text and
enable other readers to find it again.  A reference system may be based
on structural units (chapters, paragraphs, sentences; stanza and verse),
typographic units (page and line numbers), or divisions created
specifically for reference purposes (chapter and verse in Biblical
texts).  Where one exists, the traditional reference system for a text
should be preserved in an electronic transcript of it, if only to make
it easier to compare electronic and non-electronic versions of the text.
 </p><p>Reference systems may be recorded in TEI-encoded texts in any of the
following ways:
 
<list type="bullets"><item>where a reference system exists, and is based on the same
logical structure as that of the text's SGML markup, the reference for
a passage may be recorded as the value of the global <att tei="yes">id</att> or
<att tei="yes">n</att> attribute on an appropriate tag, or may be constructed by
combining attribute values from several levels of tags, as described
below in section <xref target="CORS1" type="div3"/>.
 </item><item>where there is no pre-existing reference system, the global
<att tei="yes">id</att> or <att tei="yes">n</att> attributes may be used to construct one
(e.g. collections and corpora created in electronic form), as described
below in section <xref target="CORS2" type="div3"/>.
 </item><item>where a reference system exists which is not based on the same
logical structure as that of the text's SGML markup, (for example, one
based on the page and line numbers of particular editions of the text
rather than on the structural divisions of it), then a distinct logical
structure representing the reference system may be encoded as a
concurrent markup stream, as described in section <xref target="NHRS"/>.
 </item><item>where a reference system exists which does not correspond to any
particular logical structure, or where the logical structure concerned
is of no interest to the encoder except as a means of supporting the
referencing system, then references may be encoded by means of
<gi tei="yes">mileStone</gi> elements, which simply mark points in the text at
which values in the reference system change, as described below in
section <xref target="CORS5" type="div3"/>.
 </item></list>
 
The specific method used to record traditional or new reference systems
for a text should be declared in the TEI header, as further described in
section <xref target="CORS6" type="div3"/> and in chapter <xref target="CR"/>.
 </p><p>When a text has no pre-existing associated reference system of any
kind, these Guidelines recommend as a minimum that at least the page
boundaries of the source text be marked using one of the methods
outlined in this section.  Retaining page breaks in the markup is also
recommended for texts which have a detailed reference system of their
own.  Line breaks in prose texts may be, but need not be, tagged.
<note source="auth" place="foot" anchored="Y">Many encoders find it convenient to retain the line breaks of
the original during data entry, to simplify proof-reading,
but this may be done without inserting a tag for each line
break of the original.<!-- For further discussion of tagging for pagination,        --><!-- lineation, and other physical characteristics of the     --><!-- copy text, see chapter <xref type=div1 target=PH >.      --></note>
 </p><div3 id="CORS1" name="subsection" ref="Y"><head>Using the ID and N Attributes</head><p>When traditional reference schemes represent a hierarchical
structuring of the text which mirrors that of the SGML document, the
<att tei="yes">n</att> attribute defined for all elements may be used to indicate
the traditional identifier of the relevant structural units.  The
<att tei="yes">n</att> attribute may also be used to record the numbering of
sections or list items in the copy text if the copy-text numbering is
important for some reason, for example because the numbers are out of
sequence.
 </p><p>For example, a traditional reference to Ovid's <title>Amores</title>
might be <cited>Amores 2.10.7</cited>---book 2, poem 10, line 7. Book,
poem, and line are structural units of the work and will therefore be
tagged in any case.  (See chapter <xref target="VE" type="div1"/> for a
discussion of structural units in verse collections.)  In such cases, it
is convenient to record traditional reference numbers of the structural
units using the <att tei="yes">n</att> attribute.  The relevant tags for our
example would be:
 
<eg><![CDATA[<div0 n=Amores type=volume>
    <div1 n='2' type=book>
         <div2 n='10' type=poem>
              <l n='7'> ...]]></eg>
 </p><p>One may also place the entire standard reference for each portion of
the text into the appropriate value for the <att tei="yes">n</att> attribute,
though for obvious reasons this takes more space in the file:
 
<eg><![CDATA[<div0 n=Amores type=volume>
    <div1 n='Amores 2' type=book>
         <div2 n='Amores 2.10' type=poem>
              <l n='Amores 2.10.7'> ...]]></eg>
 </p><p>If the names used by the traditional reference system can be
formulated as SGML identifiers, then the references can be given as
values for the <att tei="yes">id</att> attribute; this requires that the reference
be given without internal spaces, begin with a letter, and contain no
characters other than letters, digits, hyphens, and full
stops.<note source="auth" place="foot" anchored="Y">The legal form of identifiers depends in part on the SGML
declaration.  With appropriate modifications in the declaration,
other characters may be made legal in identifiers; this is allowed
though not encouraged in TEI-conformant documents.</note>
Unlike values for the <att tei="yes">n</att> attribute, values for the
<att tei="yes">id</att> attribute must be unique throughout the document.
Our example then looks like this:
 
<eg><![CDATA[<div0 id=AMORES type=volume>
    <div1 id='AM.2' type=book>
         <div2 id='AM.2.10' type=poem>
              <l id='AM.2.10.7'> ...]]></eg>
 </p><p>To document the usage and to allow automatic processing of these
standard references, it is recommended that the TEI header be used to
declare whether standard references are recorded in the <att tei="yes">n</att> or
<att tei="yes">id</att> attributes and which elements may carry standard
references or portions of them.  For examples of declarations for the
reference systems just shown, see section <xref target="CORS6" type="div3"/>.
 </p><p>Using the <att tei="yes">n</att> attribute one can specify only a single
standard referencing system, a limitation not without problems, since
some editions may define structural units differently and thus create
alternative reference systems.  For example, another edition of the
<title>Amores</title> considers poem 10 a continuation of poem 9, and
therefore would specify the same line as <cited>Amores 2.9.31</cited>.
In order to record both of these reference systems, one must either use
the <att tei="yes">id</att> or <att tei="yes">n</att> attribute for one, with competing
systems in concurrent markup hierarchies, as discussed below in section<xref target="NHRS" type="div3"/>
, or else use the <gi tei="yes">mileStone</gi> tags
described in section <xref target="CORS5" type="div1"/>.
 </p></div3><div3 id="CORS2" name="subsection" ref="Y"><head>Creating New Reference Systems</head><p>If a text has no canonical reference system of its own, a reference
system, if needed, may be derived from the structure of the electronic
text, specifically from the SGML markup of the text.  As with any
reference system intended for long-term use, it is important to see the
reference as an established, unchanging point in the text.  Should the
text be revised or rearranged, the reference-system identifiers
associated with any bit of text must stay with that bit of text, even if
it means the reference numbers fall out of sequence.  (A new reference
system may always be created beside the old one if out-of-sequence
numbers must be avoided.)
 </p><p>The global attributes <att tei="yes">n</att> and <att tei="yes">id</att> may be used to
assign reference identifiers to segments of the text.  Identifiers
specified by either attribute apply to the entire element for which they
are given.  SGML enforces uniqueness on ID attributes within a single
document, and ID values must begin with a letter.  No such restrictions
are made on the values of <att tei="yes">n</att> attributes.
 <!-- <p>A convenient method of mechanically generating        --><!-- unique values for <att>id</att> or <att>n</att>          --><!-- attributes, based on the SGML structure of the document  --><!-- is to use the <soCalled>typed path</soCalled> or         --><!-- <term>untyped path</term> methods described in section   --><!-- <xref type=div1 target=SA> to identify elements within   --><!-- the <gi>text</gi> segment of a TEI document.             -->
 <!-- The discussion referred to no longer exists; following   --><!-- paragraphs (through example) added as substitute.        --><!-- (msm)                                                    -->
 </p><p>A convenient method of mechanically generating unique values for
<att tei="yes">id</att> or <att tei="yes">n</att> attributes based on the SGML structure of
the document is to construct, for each element, a <term>domain-style
address</term> comprising a series of components separated by full
stops, with one component for each level of the SGML document hierarchy.
Two methods may be used.  In the <term>typed path</term> form of
identifier, each component in the identifier takes the form <ident tei="yes" type="var">element-type</ident> <cited>-</cited> <ident tei="yes" type="var">number</ident>.  The element name specifies what type of
element to be sought, and the number specifies which occurrence of that
element type is to be selected.  (The hyphen and number may be omitted
if there is only one element of the given type.)  In the <term>untyped
path</term> form of identifier, each component consists of a number,
indicating which element in the sequence of nodes at each level is to be
selected.  A fixed prefix beginning with a letter may be used to make
the untyped path legal as an SGML <code tei="yes" type="kw">ID</code> value.
 </p><p>Identifiers generated with these methods should use the <gi tei="yes">text</gi>
element as their starting point, rather than the <gi tei="yes">tei.2</gi> or
<gi tei="yes">body</gi> elements. The <gi tei="yes">tei.2</gi> element may be taken
as a starting point only if identifiers need to be generated for the
<gi tei="yes">teiHeader</gi>, which is not usually the case;  using the
<gi tei="yes">body</gi> element as a root would prevent assignment of identifiers
for the front and back matter.  The component corresponding to the root
element can be omitted from identifiers, if no confusion will result.
In collections and corpora, the component corresponding to the root may
be replaced by the unique identifier assigned to the text or sample.
 </p><p>In the following example, each element within the <gi tei="yes">text</gi>
element has been given a typed-path identifier as its <att tei="yes">id</att>
value, and an untyped-path identifier as its <att tei="yes">n</att> value; the
latter are prefixed with the string <cited>AB</cited>, which may be
imagined to be the general identifier for this text.
 
<eg><![CDATA[   <text id='TEXT-1' n='AB'>
     <front id='FRONT' n='AB.1'>
       <div       id='FRONT.div-1'     n='AB.1.1'><p> ... </div>
       <titlePage id='FRONT.titlePage' n='AB.1.2'>
                 <titlePart> ... </titlePart>       </titlePage>
       <div       id='FRONT.div-2'     n='AB.1.3'><p> ... </div>
     </front>
     <body id='BODY' n='AB.2'>
       <p id='BODY.p-1' n='AB.2.1'> ... </p>
       <p id='BODY.p-1' n='AB.2.2'> ... </p>
       <div id='BODY.div-1' n='AB.2.3'>
         <head id='BODY.div-1.head' n='AB.2.3.1'> ... </head>
         <p    id='BODY.div-1.p-1'  n='AB.2.3.2'> ... </p>
         <p    id='BODY.div-1.p-2'  n='AB.2.3.3'> ... </p>
         </div>
       <div id='BODY.div-2' n='AB.2.4'>
         <head id='BODY.div-2.head' n='AB.2.4.1'> ... </head>
         <p    id='BODY.div-2.p-1'  n='AB.2.4.2'> ... </p>
         <p    id='BODY.div-2.p-2'  n='AB.2.4.3'> ... </p>
         </div>
     </body>
  </text>]]></eg>
 
 
The typed and untyped path methods are convenient, but are in no way
required for anyone creating a reference system.
 </p><p>If the <att tei="yes">id</att> attribute is used to record the reference
identifiers generated, each value should record the entire path.  If the
<att tei="yes">n</att> attribute is used, each value may record either the entire
path or only the subpath from the SGML parent element.  The attribute
used, the elements which can bear standard reference identifiers, and
the method for constructing standard reference identifiers, should all
be declared in the header as described in section <xref target="HD54"/>.
 </p><p>When the hierarchy of the SGML-encoded document and that of the
reference system differ (e.g. for reference systems based on page and
line numbers) or when more than one reference system is to be encoded,
the encoder may choose to represent the alternative reference system(s)
as elements in one or more concurrent document hierarchies.  For an
introduction to the concept of concurrent hierarchies, see the
discussion of the <code tei="yes" type="kw">CONCUR</code> feature in section <xref target="SG152" type="div1"/>.  For further discussion of this and other
mechanisms, see chapter <xref target="NH"/>.
 </p></div3><div3 id="CORS5" name="subsection" ref="Y"><head>Milestone Tags</head><p>If concurrent markup is not desired (e.g. because the available SGML
parser does not support the CONCUR feature), or if the desired reference
system does not correspond to any particular structural hierarchy, it
may be more convenient to mark up changes in the reference system by using
one or more of the following <term>milestone</term> elements:
 
<tagList style="one-line"><tagDesc tagDoc="MILEST" atts="ed n unit"/><tagDesc tagDoc="PAGEBR" atts="ed n"/><tagDesc tagDoc="LINEBR" atts="ed n"/><tagDesc tagDoc="COLBR" atts="ed n"/></tagList>
 </p><p>These elements simply mark the points in a text at which some
category in a reference system changes.  They have no content but
subdivide the text into regions, rather in the same way as milestones
divide a road into segments.  The elements <gi tei="yes">pb</gi>, <gi tei="yes">cb</gi>,
and <gi tei="yes">lb</gi> are provided to mark specific types of milestone,
namely page, column, and line boundaries, as further described in
chapter <xref target="PH" type="div1"/>.  No SGML validation of a reference
system based on <gi tei="yes">mileStone</gi> tags is possible, so it will be the
responsibility of the encoder or the application software to ensure
that milestone tags occur in a correct order.
 </p><p>Milestone tags may be useful where a text has two competing
structures. For example, many English novels were first published as
serial works, individual parts of which do not always contain a whole
number of chapters. An encoder may decide to represent the
chapter-based  structure using <gi tei="yes">div1</gi> elements, with
<gi tei="yes">mileStone</gi> elements to mark the points at which individual
parts end; or the reverse. Thus, an encoding in which chapters are
regarded as more important than parts might encode some work in which
chapter three begins in part one and is concluded in part two as
follows:
 
<eg rend="skel"><![CDATA[<text><body>
  <mileStone unit=part>
  <div1 n=1 type=chapter>
  <!-- text of chapter 1 here -->
  </div1>
  <div1 n=2 type=chapter>
  <!-- text of chapter 2 here -->
  </div1>
  <div1 n=3>
  <!-- part of text of chapter 3 here -->
  <mileStone unit=part>
  <!-- remainder of text of chapter 3 here -->.
  </div1>
</body></text>]]></eg>
 
An encoding of the same work in which parts are regarded as more
important than chapters might begin as follows:
 
<eg> <![CDATA[
<text><body>
  <div1 n=1 type=part>
  <mileStone unit=chapter>
  <p><!-- text of chapter 1 here -->
  <mileStone unit=chapter>
  <p><!-- text of chapter 2 here -->
  <mileStone unit=chapter>
  <p><!-- part of text of chapter 3 here -->
  </div1><div1 n=2 type=part>
  <p><!-- remainder of text of chapter 3 here -->
  <mileStone unit=chapter>
  <!-- ... -->
</body></text>]]></eg>
 </p><p>Milestone tags also make it possible to record the reference systems
used in a number of different editions of the same work. The reference
system of any one edition can be recreated from a text in which all are
marked by simply ignoring all elements that do not specify that edition
on their <att tei="yes">ed</att> attribute.
 </p><p>As a simple example, assuming that edition E1 of some collection of
poems regards the first two poems as constituting the first book, while
edition E2 regards the first poem as prefatory, a markup scheme like
the following might be adopted:
 
<eg><![CDATA[ 
 <mileStone ed=E1 unit=work>
 <mileStone ed=E2 unit=work>
 <mileStone ed=E1 unit=book>
 <mileStone ed=E1 unit=poem>
 <mileStone ed=E2 unit=poem>
  <!-- text of first poem here -->
 <mileStone ed=E2 unit=book>
 <mileStone ed=E1 unit=poem>
 <mileStone ed=E2 unit=poem>
  <!-- text of second poem here -->
 ]]></eg>
 </p><p>In this case no <att tei="yes">n</att> value is specified, since the numbers
rise predictably and the application can keep a count from the start of
the document, if desired.
 </p><p>The value of the <att tei="yes">n</att> attribute may but need not include the
identifiers used for any larger sections.  That is, either of the
following styles is legitimate:
<eg><![CDATA[ <mileStone ed=E1 unit=work n='Amores'>
 <mileStone ed=E1 unit=book n=1>
 <mileStone ed=E1 unit=poem n=1>
  <!-- text of Amores 1.1 -->
 <mileStone ed=E1 unit=poem n=2>
  <!-- text of Amores 1.2 -->
 <mileStone ed=E1 unit=book n=3>]]></eg>
or
<eg><![CDATA[ <mileStone ed=E1 unit=work n='Amores'>
 <mileStone ed=E1 unit=book n=1>
 <mileStone ed=E1 unit=poem n='1.1'>
 <!-- text of Amores 1.1 -->
 <mileStone ed=E1 unit=poem n='1.2'>
  <!-- text of Amores 1.2 -->
 <mileStone ed=E1 unit=book n='1.3'>]]></eg>
 </p><p>When using <gi tei="yes">mileStone</gi> tags, line numbers may be supplied for
every line or only periodically (every fifth, every tenth line).  The
latter may be simpler; the former is more reliable.
 </p><p>The style of numbering used in the values of <att tei="yes">n</att> is
unrestricted:  for the example above, <code tei="yes" type="val">I.i</code>, <code tei="yes" type="val">I.ii</code>, and <code tei="yes" type="val">I.iii</code> could have been
used equally well if preferred.  The special value <code tei="yes" type="val">unnumbered</code> should be reserved for marking sections of
text which fall outside the normal numbering system (e.g. chapter heads,
poem numbers, titles, or speaker attributions in a verse drama).
 <!-- dropped second reference pace Eynsham --><!-- p>No automatic validation of any hierarchical ordering   --><!-- can be defined for the various types of <                --><!-- gi>milestone</ gi> tag; it is the encoder's              --><!-- responsibility to ensure that milestone values are       --><!-- valid.                                                   -->
 </p><p>Because the <att tei="yes">ed</att> attribute is unrestricted, no change need be
made to the document type declaration of a file before adding tags to
describe a new reference system.  (The value of <att tei="yes">ed</att> may be
restricted to a defined set of edition symbols by using the techniques
described in chapter <xref target="MD" type="div1"/>.)
 </p><p>See below, section <xref target="CORS6" type="div3"/>, for examples of
declarations for the reference systems just shown.
 </p><p>The milestone elements are formally defined
as follows:<!--  tag has the following formal declaration: -->
<dtdFrag id="DCORSM" n="Milestone tags"><tagDecl tagDoc="MILEST"/><tagDecl tagDoc="PAGEBR"/><tagDecl tagDoc="LINEBR"/><tagDecl tagDoc="COLBR"/></dtdFrag>
 </p></div3><div3 id="CORS6" name="subsection" ref="Y"><head>Declaring Reference Systems</head><p>Whatever kind of reference system is used in an electronic text, it
is recommended that the TEI header contain a description of its
construction in the <gi tei="yes">refsDecl</gi> element described in section <xref target="HD54" type="div3"/>.  As described there, the declaration may consist
either of a formal declaration using the <gi tei="yes">step</gi> tag or an
informal description in prose.  The former is recommended because unlike
prose it can be processed by software.
 </p><p>The three examples given in section <xref target="CORS1" type="div3"/>
would be declared as follows.  The first example encodes the standard
references for Ovid's <title>Amores</title> one level at a time, using
the <att tei="yes">n</att> attribute on the <gi tei="yes">div0</gi>, <gi tei="yes">div1</gi>,
<gi tei="yes">div2</gi>, and <gi tei="yes">l</gi> tags.  The header for such an encoding
should look something like this:
 
<eg rend="skel"><![CDATA[<teiHeader>
    <fileDesc> ...
    </fileDesc>
    <encodingDesc>
         ...
         <refsDecl>
              <step refunit='work' delim=' '
                    from='DESCENDANT (1 DIV0 N %1)' to='DITTO' >
              <step refunit='book' delim='.'
                    from='CHILD (1 DIV1 N %1)' to='DITTO' >
              <step refunit='poem' delim='.'
                    from='CHILD (1 DIV2 N %1)' to='DITTO' >
              <step refunit='line'
                    from='CHILD (1 L N %1)' to='DITTO' >
         </refsDecl>
         ...
    </encodingDesc>
</teiHeader>]]></eg>
 </p><p>The second example encodes the same reference system, again using the
<att tei="yes">n</att> attribute on the <gi tei="yes">div0</gi>, <gi tei="yes">div1</gi>,
<gi tei="yes">div2</gi>, and <gi tei="yes">l</gi> tags, but giving the reference string in
full on each tag.  If canonical references are made only to lines, the
reference system could be declared as follows:
 
<eg><![CDATA[ <refsDecl>
   <step refunit='line'
         from='DESCENDANT (1 L N %1)' to='DITTO' >
 </refsDecl>]]></eg>
 
Since no delimiter is specified, the entire canonical reference string
is sought as the value of the <att tei="yes">n</att> attribute on an <gi tei="yes">l</gi>
element.
 </p><p>In order to handle references to works, books, and poems as well as
to individual lines, the declaration for the reference system must be
more complicated:
 
<eg><![CDATA[ <refsDecl>
   <step from='DESCENDANT (1 (DIV[012]|L) N %1)' to='DITTO' >
 </refsDecl>]]></eg>
 
This declaration indicates that the entire reference string must be
sought as the value of the <att tei="yes">n</att> attribute on a <gi tei="yes">div0</gi>,
<gi tei="yes">div1</gi>, <gi tei="yes">div2</gi>, or <gi tei="yes">l</gi> element.
 </p><p>The third example encodes the same reference system, this time giving
the entire reference string as the value of the <att tei="yes">id</att> attribute
on the relevant tags.  The reference system declaration for such an
encoding would be:
 
<eg><![CDATA[<refsDecl>
    <step from="ID (%1)" to="DITTO">
</refsDecl>]]></eg>
 </p><p>As in the previous example, no single value can be given for the
<att tei="yes">refunit</att> attribute in this declaration, as the single step
handles references to works, books, and poems, as well as to lines.  The
<att tei="yes">type</att> attribute on the <gi tei="yes">div0</gi>, <gi tei="yes">div1</gi>, and
<gi tei="yes">div2</gi> elements may be used, however, to indicate the type of the
result returned from a match.
 <!-- , or the declaration can be expanded:                    --><!--                                                          --><!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <refsDecl>                                               --><!--     <step refunit='work' from="ID (%1)" to="DITTO">      --><!--     <step refunit='book' from="ID (%1)" to="DITTO">      --><!--     <step refunit='poem' from="ID (%1)" to="DITTO">      --><!--     <step refunit='line' from="ID (%1)" to="DITTO">      --><!-- </refsDecl>                                              --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p><p>Reference systems recorded by means of milestone tags can also be
declared; the following prose description could be used to declare
the example given in section <xref target="CORS5" type="div3"/>.
 
<eg><![CDATA[<refsDecl>
    <p>Standard references to work, book, poem, and line may be
    constructed from the Milestone tags in the text.
</refsDecl>]]></eg>
 
Or in this way, using a formal declaration for this reference scheme
derived from edition <code tei="yes" type="value">E1</code>.
 
<eg><![CDATA[<refsDecl>
    <state delim=' ' unit=work ed='E1'>
    <state delim='.' unit=book ed='E1'>
    <state delim=':' unit=poem ed='E1'>
    <state unit=line ed='E1'>
</refsDecl>]]></eg>
 </p><p>This is synonymous with the following declaration using the
<gi tei="yes">step</gi> element:
 
<eg><![CDATA[<refsDecl>
    <step refunit='work' delim=' '
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT work N %1)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT work)' >
    <step refunit='book' delim='.'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT book N %2)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT book)' >
    <step refunit='poem' delim='.'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT poem N %3)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT poem)' >
    <step refunit='line'
          from='DESCENDANT (1 MILESTONE EDITION E1 UNIT line N %4)'
          to=  'FOLLLOWING (1 MILESTONE EDITION E1 UNIT line)' >
</refsDecl>]]></eg>
 <!-- JL:  question for P4:  can we specify the edition in     --><!-- some way as a parameter?                                 --><?tei:EOF p2cors.odd ??>

 <!-- CObi Bibliographic Citations (P1 5.5)                    --><?tei:SOF p2cobi.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    *
    * $Log: p2cobi.odd,v $
    * Revision 1.13  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.12  98/01/28  11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    * 
    * Revision 1.11  1994/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * 
    * Revision 1.10  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * --><!-- ******************************************************** --><!-- P2 Cobi (old P2235)                                      --><!-- ******************************************************** --><!-- Revision History (add lines at top)                      --><!-- 10 jan 98 : LB : fix egs --><!-- 94-03-26 : MSM : corrections, changes from WWP team      --><!-- 94-03-26 : MSM : corrections from DB                     --><!-- 94-03-26 : MSM : typos from JL et al.                    --><!-- 9 jan: fixed spurious <items> element; change TeiH to teiH  --><!-- 29 dec 93 : fixed many erroneous  examples               --><!-- 27 dec 93: LB : removed individual, org etc --><!-- 25 dec 93: LB : resp/respstmt, city/pubPlace fixes       --><!--            added meeting, doubtfully                     --><!-- 92-12-09 : MSM : spelling corrections                    --><!-- 92-12-09 : MSM : date takes VALUE att, not STDVAL        --><!-- 92-12-07 : MSM : clean dtdFrag ids, contins              --><!-- 92-12-06 : MSM : clean up dtdfrag ids, refs              --><!-- 92-12-06 : MSM : correct minor syntax errors             --><!-- 92-12-06 : MSM : correct ref to fileDesc, TeiHeader      --><!-- 92-12-05 : MSM : finish (hard slog), add equiv list      --><!-- 92-12-03 : MSM : further changes, in part as per LB      --><!-- 92-12-02 : MSM : continued revisions                     --><!-- 92-12-01 : MSM : revise for release of CO                --><!-- 92-11-17 : MSM : change IDs to CObi*                     --><!-- 92-11-09 : MSM : suppress leading blanks in some elems   --><!-- 92-11-09 : MSM : rename BIBL from CITN                   --><!-- 26 May 92 MSM make comments all one line long for Script --><!--               modify dtdfrag ids                         --><!--  2 May 92 LB  added loadsa discussion; killed some tags; --><!--               added citn.full, address and its parts     --><!-- 26 Feb 92 LB     ODDified from TEI P1, sec.  6.6         --><!--       (last revision: 16 Oct 90 CMSMcQ  for Version 1.1) -->
 </p></div3></div2><div2 id="COBI" name="section" ref="Y"><head>Bibliographic Citations and References</head><p>Bibliographic references (that is, full descriptions of bibliographic
items such as books, articles, films, broadcasts, songs, etc.) or
pointers to them may appear at various places in a TEI text.  They are
required at several points within the TEI Header's source description,
as discussed in section <xref target="HD3"/>; they may also appear within
the body of a text, either singly, (for example within a footnote), or
collected together in a list as a distinct part of a text.
 </p><p>In printed texts, the individual constituents of a bibliographic
reference are conventionally marked off from each other and from the
flow of text by such features as bracketing, italics, special
punctuation conventions, underlining, etc.  In electronic texts, such
distinctions are also important, whether in order to produce acceptably
formatted output or to facilitate intelligent retrieval processing,<note source="auth" place="foot" anchored="Y">For example, to distinguish <cited>London</cited> as an
author's name from <cited>London</cited> as a place of publication or as
a component of a title.</note> quite apart from the need to distinguish
the reference itself as a textual object with particular linguistic
properties.
 </p><p>It should be emphasized that for references as for other textual
features, the primary or sole consideration is not how the text should
be formatted when it is printed.  The distinctions permitted by the
scheme outlined here may not necessarily be all that particular
formatters or bibliographic styles require, although they should prove
adequate to the needs of many such commonly used software systems.<note source="auth" place="foot" anchored="Y" ed="MSM">Among the bibliographic software systems and
subsystems consulted in the design of the <gi tei="yes">biblStruct</gi> structure
were BibTeX, Scribe, and ProCite.  The distinctions made by all three
may be preserved in <gi tei="yes">biblStruct</gi> structures, though the nature of
their design prevents a simple one-to-one mapping from their data
elements to TEI elements.  For further information, see section <xref target="COBIOT"/>.</note> The features distinguished and described below
(in section <xref target="COBICO"/>) constitute a set which has been useful
for a wide range of bibliographic purposes and in many applications, and
which moreover corresponds to a great extent with existing bibliographic
and library cataloguing practice.  For a fuller account of that practice
as applied to electronic texts see section <xref target="HD3"/>; for a
brief mention of related library standards see section <xref target="HD8"/>.
 </p><div3 id="COBITY" name="subsection" ref="Y"><head>Elements of Bibliographic References</head><p>The following elements are used to mark individual bibliographic
references as wholes, or in groups:
 
<tagList style="one-line"><tagDesc tagDoc="BIBL"/><tagDesc tagDoc="BIBLSTRU"/><tagDesc tagDoc="BIBLFULL"/><tagDesc tagDoc="LISTBIBL"/></tagList>
 
These elements all share a number of possible component sub-elements.
For the <gi tei="yes">bibl</gi> and <gi tei="yes">biblStruct</gi> elements, exactly the
same sub-elements are concerned, and they are described together in
section <xref target="COBICO"/>; for the <gi tei="yes">biblFull</gi> element, the
sub-elements concerned are fully described in section <xref target="HD2"/>.
 </p><p>Different levels of specific tagging may be appropriate in different
situations.  In some cases, it may be felt necessary to mark just the
extent of the reference itself, with perhaps a few distinctions being
made within it (for example, between the part of the reference which
identifies a title or author and the rest).  Such references, containing
a mixture of text with specialized bibliographic elements, are regarded
as <gi tei="yes">bibl</gi> elements, and tagged accordingly.  For example:
 
<eg><![CDATA[<p>A book which had a great influence on him
was <bibl>Tufte's <title>Envisioning
Information</title></bibl>, although he may
never have actually read it.]]></eg>
 
Indeed, some encoders may find it unnecessary to mark the bibliographic
reference at all:
 
<eg><![CDATA[<p>A book which had a great influence on him
was Tufte's <title>Envisioning Information</title>,
although he may never have actually read it.]]></eg>
 </p><p>Some bibliographic references are extremely elliptical, often only a
string of the form <cited>Baxter, 1983</cited>.  If no further details of
Baxter's book are given in the source text and none are supplied by the
encoder, then the reference thus given should be tagged as a
<gi tei="yes">bibl</gi>:
 
<eg><![CDATA[All of this is of course much more fully treated
in <bibl>Baxter, 1983</bibl>.]]></eg>
 
In general, however, normal modern bibliographic practice, and these
Guidelines, distinguish between a bibliographic
<term rend="noindex">reference</term>,<indexed level1="references" level2="bibliographic"/><indexed level1="bibliographic references"/>
 
which is a self-sufficient description of a bibliographic item, and a
bibliographic <term rend="noindex">pointer</term>,<indexed level1="bibliographic pointers"/><indexed level1="pointers" level2="bibliographic"/>
 
which is a short-form citation (such as <cited>Baxter, 1983</cited>)
which serves usually as a place-holder or pointer to a full long-form
reference found elsewhere in the text.  The usual encoding of short-form
references such as <cited>Baxter, 1983</cited> is not as <gi tei="yes">bibl</gi>
elements but as cross-references to such elements; see section <xref target="COBIXR"/> below.
 </p><p>In cases where the encoder wishes to impose more structure on the
bibliographic information, for example to make sure it conforms to a
particular style-sheet or retrieval processor, the <gi tei="yes">biblStruct</gi>
element should be used.  Note that several of the features in this and
later examples are explained later in the current section.
 
<eg><![CDATA[<biblStruct>
    <monogr>
    <author>Edward R. Tufte</>
    <title>Envisioning Information</>
    <imprint>
         <pubPlace>Cheshire, Conn.</>
         <publisher>Graphics Press</>
         <date>1990</>
    </imprint></monogr>
</biblStruct>]]></eg>
 </p><p>The highest level of detail and the most complex structure supported
by the current proposals is provided by the <gi tei="yes">biblFull</gi> element,
which closely resembles the <gi tei="yes">fileDesc</gi> element of the TEI Header
(section <xref target="HD2"/>).
 <!-- biblFull needs an analytic level. -MSM -->
 <!-- titstmt requires title first -->
<eg><![CDATA[<biblFull>
    <titleStmt>
         <title>Envisioning Information</title>
         <author>Tufte, Edward R[olf]</author>
      </titleStmt>
    <extent>126 pp.</extent>
    <publicationStmt>
         <publisher>Graphics Press</publisher>
         <pubPlace>Cheshire, Conn. USA</pubPlace>
         <date>1990</date>
    </publicationStmt>
</biblFull>]]></eg><!-- MSM! please check/expand on these details: you have the book!  --><!-- Done.  Robinson corrected to Rolf, bracketed (titlep has R.)   -->
 </p><p>A list of bibliographic items, of whatever kind, may be treated in
the same way as any other list (see section <xref target="COLI"/>).
Alternatively, the specialized <gi tei="yes">listBibl</gi> element may be used.
The difference between the two is that a <gi tei="yes">list</gi> contains
<gi tei="yes">item</gi> elements, within which bibliographic elements (<gi tei="yes">bibl</gi>,
<gi tei="yes">biblStruct</gi> or <gi tei="yes">biblFull</gi>) may appear, as well as other
phrase- and paragraph-level elements, whereas the <gi tei="yes">listBibl</gi> may
contain only bibliographic elements, optionally preceded by a heading and a
series of introductory paragraphs.  The former would be appropriate
for a list of bibliographic elements in which descriptive prose
predominated, and the latter for a more formal bibliography.  The
following are thus both legal encodings of a list of bibliographic
entries:  a <gi tei="yes">listBibl</gi>:
 <!-- <note place=foot>In these examples, white space has      --><!-- been liberally used to help indicate the structure of    --><!-- the entries; it is not required and is not necessarily   --><!-- used in practice.  </note>                               -->
 
<eg><![CDATA[<listBibl>
<head>Bibliography</head>
<biblStruct id=NEL80>
    <analytic>
         <author>Nelson, T. H.</>
         <title>Replacing the printed word:
                a complete literary system.</>
    </analytic>
    <monogr>
         <title>Information Processing '80:  Proceedings of the IFIPS
                Congress, October 1980</>
         <editor>Simon H. Lavington</>
         <imprint>
              <publisher>North-Holland</>
              <pubPlace>Amsterdam</>
              <date>1980</>
         </imprint>
         <biblScope>pp 1013-23
    </monogr>
    <note>Apparently a draft of section 4 of <title>Literary
          Machines</title>.</note>
</biblStruct>
<bibl id=NEL88>Ted Nelson:  <title>Literary Machines</title>
    (privately published, 1987)</bibl>
<bibl id=BAX88>
    <author>Baxter, Glen</author>
    <title>Glen Baxter His Life: the years of struggle</title>
    London: Thames and Hudson, 1988.
    </bibl>
</listBibl>]]></eg>
or a simple <gi tei="yes">list</gi>:
<eg><![CDATA[<list><head>Bibliography</>
<item><bibl id=NEL80>
        <author>Nelson, T. H.</>
        <title level=a>Replacing the printed word:
             a complete literary system.</>
        <title level=m>Information Processing '80:
             Proceedings of the IFIPS Congress, October 1980</>
        <editor>Simon H. Lavington</>
        <publisher>North-Holland</>
        <pubPlace>Amsterdam</>
        <date>1980</>
        <biblScope>pp 1013-23
        <note>Apparently a draft of section 4 of <title>Literary
         Machines</title>.</note>
    </bibl></item>
<item><bibl id=NEL88>Ted Nelson:  <title>Literary Machines</title>
    (privately published, 1987)</bibl></item>
<item><bibl id=BAX88>
    <author>Baxter, Glen</author>
    <title>Glen Baxter His Life: the years of struggle</title>
    London: Thames and Hudson, 1988.
    </bibl></item>
</list>]]></eg>
 </p><p>The formal declarations for these elements are as follows:
 
<dtdFrag id="DCOBI" n="Tags for Bibliographic References"><tagDecl tagDoc="BIBL"/><tagDecl tagDoc="BIBLSTRU"/><tagDecl tagDoc="BIBLFULL"/><tagDecl tagDoc="LISTBIBL"/></dtdFrag>
 </p></div3><div3 id="COBICO" name="subsection" ref="Y"><head>Components of Bibliographic References</head><p>This section discusses a number of very commonly occurring component
elements of bibliographic references.  They fall into four groups:
<list type="bullets"><item>elements for grouping components of the
 
<term rend="noindex">analytic</term>,
<term rend="noindex">monographic</term>,
and <term rend="noindex">series</term><indexed level1="analytic level" level2="bibliographic"/><indexed level1="monographic level" level2="bibliographic"/><indexed level1="series level" level2="bibliographic"/><indexed level1="bibliographic references" level2="analytic level"/><indexed level1="bibliographic references" level2="monographic level"/><indexed level1="bibliographic references" level2="series level"/>
levels in a structured bibliographic reference</item><item>titles of various kinds, and statements of intellectual
responsibility (authorship, etc.)</item><item>information relating to the publication, pagination, etc. of an
item</item><item>annotation, commentary and further detail</item></list>
 
The following sections describe the elements which may be used to
represent such information within a <gi tei="yes">bibl</gi> or
<gi tei="yes">biblStruct</gi> element.  Within the former, any or all of these
may be used and in any order.  Within the latter, such of these elements
as exist for a given reference must be distinguished, and must also be
presented in a specific order, discussed further below (section <xref target="COBICOO"/>).
 </p><div4 id="COBICOL" name="Section" ref="Y"><head>Analytic, Monographic, and Series Levels</head><p>In common library practice a clear distinction is made between an
individual item within a larger collection and a free-standing book,
journal, or collection.  Similarly a book in a series is distinguished
sharply from the series within which it appears.  An article forming
part of a collection which itself appears in a series thus has a
bibliographic description with three quite distinct levels of
information:
 
<list type="ordered"><item>the <term rend="noindex">analytic</term><indexed level1="analytic level" level2="bibliographic"/>
level, giving the title, author, etc., of the article;
 </item><item>the <term rend="noindex">monographic</term><indexed level1="monographic level" level2="bibliographic"/>
level, giving the title, editor, etc., of the collection;
 </item><item>the <term rend="noindex">series</term><indexed level1="series level" level2="bibliographic"/>
level, giving the title of the series, possibly the names of its
editors, etc., and the number of the volume within that series.
 </item></list>
 
In the same way, an article in a journal requires at least two levels of
information:  the analytic level describing the article itself, and the
monographic level describing the journal.
 </p><p>These three levels may be distinguished within a <gi tei="yes">bibl</gi>
element, and must be distinguished within a <gi tei="yes">biblStruct</gi> element
if present, by means of the following tags:
 
<tagList style="one-line"><tagDesc tagDoc="ANALYTIC"/><tagDesc tagDoc="MONOGR"/><tagDesc tagDoc="SERIES"/></tagList>
 </p><p>For purposes of TEI encoding, journals and anthologies are both
treated as monographs; a journal title will thus be tagged <tag compl="full" tei="yes">title
level=j</tag> or <tag compl="full" tei="yes">monogr</tag><tag compl="full" tei="yes">title</tag> ...
<tag compl="full" tei="yes">/title</tag> ...  <tag compl="full" tei="yes">/monogr</tag>.  Individual articles in the
journal or collected texts should be treated at the
<soCalled>analytic</soCalled> level.  When an article has been printed
in more than one journal or collection, the bibliographic reference may
have more than one <gi tei="yes">monogr</gi> element, each possibly followed by
one or more <gi tei="yes">series</gi> elements.  A <gi tei="yes">series</gi> element always
relates to the most recently preceding <gi tei="yes">monogr</gi> element.
(Whether reprints of an article are treated in the same bibliographic
reference or a separate one varies among different styles.  Library
lists typically use a different entry for each publication, while
academic footnoting practice typically treats all publications of the
same article in a single entry.)
 </p><p>For example, the article cited in this example has been published
twice, once in a journal and once in a collection which appeared in a
series:
 
<eg><![CDATA[    <biblStruct>
         <analytic>
              <author>Thaller, Manfred</author>
              <title level=a>A Draft Proposal for a Standard for the
                     Coding of Machine Readable Sources</>
         </analytic>
         <monogr>
              <!-- In -->
              <title level=j>Historical Social Research</title>
              <imprint>
                    <biblScope type=vol>40</>
                    <date>October 1986</>
                    <biblScope type=pages>3-46</>
              </imprint>
         </monogr>
         <monogr>
              <!-- Rpt. in -->
              <title level=m>Modelling Historical Data:
                     Towards a Standard for Encoding and Exchanging
                     Machine-Readable Texts</title>
              <editor>Daniel I. Greenstein</editor>
              <imprint>
                   <pubPlace>St. Katharinen</pubPlace>
                   <publisher>Max-Planck-Institut f&uuml;r Geschichte
                         In Kommission bei
                         Scripta Mercaturae Verlag</publisher>
                   <date>1991</date>
              </imprint>
         </monogr>
         <series>
              <title level=s>Halbgraue Reihe
                   zur Historischen Fachinformatik</title>
              <respStmt><resp>Herausgegeben von</resp>
                    <name type=person>Manfred Thaller</>
                    <name type=org>Max-Planck-Institut f&uuml;r
                        Geschichte</>
              </respStmt>
              <title level=s>Serie A:  Historische Quellenkunden</>
              <biblScope>Band 11</biblScope>
         </series>
    </biblStruct>]]></eg>
 </p><p>Punctuation may not appear between the elements within a structured
bibliographic entry; if punctuation is to be given explicitly in the
encoding, it must be contained within the elements it delimits.  As the
example shows, it is possible to encode the entry without any
inter-element punctuation:  this facilitates use of the
<gi tei="yes">biblStruct</gi> element in systems which can render bibliographic
references in any of several styles.
 </p><p>The formal declarations for the elements defined in this section are
as follows:
 
<dtdFrag id="DCOBILV" n="Levels of bibliographic information" contin="DCOBI"><tagDecl tagDoc="ANALYTIC"/><tagDecl tagDoc="MONOGR"/><tagDecl tagDoc="SERIES"/></dtdFrag>
 </p></div4><div4 id="COBICOR" name="Section" ref="Y"><head>Authors, Titles, and Editors</head><p>Bibliographic references typically begin with a statement of the
title being cited and the names of those intellectually responsible for
it.  For articles in journals or collections, such statements should
appear both for the analytic and for the monographic level.  The
following elements are provided for tagging such elements:
 
<tagList style="one-line"><tagDesc tagDoc="TITLE" atts="level type"/><tagDesc tagDoc="AUTHOR"/><tagDesc tagDoc="EDITOR"/><tagDesc tagDoc="RESP"/><tagDesc tagDoc="ROLE"/><tagDesc tagDoc="NAME"/><tagDesc tagDoc="MEETING"/></tagList>
 <!-- some discussion of meeting shd be added but not sure where -->
 </p><p>In bibliographic references, all titles should be tagged as such,
whether analytic, monographic, or series titles.  The single element
<gi tei="yes">title</gi> is used for all these cases.  When it appears directly
within an <gi tei="yes">analytic</gi>, <gi tei="yes">monogr</gi>, or <gi tei="yes">series</gi>
element, <gi tei="yes">title</gi> is interpreted as belonging to the appropriate
level.  When it appears elsewhere, its <att tei="yes">level</att> attribute should
be used to signal its bibliographic level.  It is a semantic error to
give a value for the <att tei="yes">level</att> attribute which is inconsistent
with the context; such values may be ignored.  The <att tei="yes">level</att>
value <code tei="yes" type="val">a</code> implies the analytic level; the values
<code tei="yes" type="val">m</code>, <code tei="yes" type="val">j</code>, and <code tei="yes" type="val">u</code> imply the monographic level; the value <code tei="yes" type="val">s</code> implies the series level.  Note, however, that the
semantic error occurs only if the nested title is directly enclosed by
the <gi tei="yes">analytic</gi>, <gi tei="yes">monogr</gi>, or <gi tei="yes">series</gi> element; if
it is enclosed only indirectly, no semantic error need be present.  For
example, the analytic title may contain a monographic title:
 
<eg><![CDATA[<biblStruct>
    <analytic><author>Lucy Allen Paton</>
              <title>Notes on Manuscripts
                   of the <title level=m>Proph&eacute;cies
                   de Merlin</title></title>
    </analytic>
    <monogr><title level=j>PMLA</>
          <imprint><biblScope type=vol>8</>
            <date>1913</date>
            <biblScope type=pages>122</>
      </imprint>
    </monogr>
</biblStruct>]]></eg>
 
In this case, the analytic title <q>Notes on Manuscripts of the
<title>Proph&eacute;cies de Merlin</title></q> needs no <att tei="yes">level</att>
attribute because it is directly contained by the <gi tei="yes">analytic</gi>
level; the monographic title contained within it, <q>Proph&eacute;cies
de Merlin,</q> does not create a semantic error because it is not
directly contained by the <gi tei="yes">analytic</gi> element.
 </p><p>In some bibliographic applications, it may prove useful to
distinguish main titles from subordinate titles, parallel titles, etc.
The <att tei="yes">type</att> attribute is provided to allow this distinction to
be recorded.
 </p><p>The following reference, from a national standard for bibliographic
references,<note source="auth" place="foot" anchored="Y"><citation>American National Standard for
Bibliographic References, ANSI Z39.29-1977 (New York:  American
National Standards Institute, 1977), p. 34 (sec.
A.2.2.1).</citation></note>
illustrates this type of analysis with its distinction between main
and subordinate titles.
 
<eg><![CDATA[<bibl>Saarikoski, Pirkko-Liisa, and Paavo Suomalainen,
<title level=a type=main>Studies on the physiology of
the hibernating hedgehog, 15</title>
<title level=a type=subordinate>Effects of seasonal
and temperature changes on the in vitro
glycerol release from brown adipose tissue</>
<title level=j>Ann. Acad. Sci. Fenn., Ser. A4</>
<date>1972</> <biblScope type='vol: pp'>187: 1-4</>
</bibl>]]></eg><!-- example from ANSI Z39.29, sec. A.2.2.1, p.34 -->
 </p><p>Slightly more complex is the distinction made below among main,
subordinate, and parallel titles, in an example from the same source (p.
63).  The punctuation and the bibliographic analysis are those given in
ANSI Z39.29-1977; the punctuation is in the style prescribed by the
International Standard Bibliographic Description (ISBD).<note source="auth" place="foot" anchored="Y">The analysis is not wholly unproblematic:  as the text of the
standard points out, the first subordinate title is subordinate only to
the parallel title in French, while the second is subordinate to both
the English main title and the French parallel title, without this
relationship being made clear, either in the markup given in the example
or in the reference structure offered by the standard.</note>
 
<eg><![CDATA[<bibl>Tchaikovsky, Peter Ilich.
<title level=m type=main>The swan lake ballet</>
= <title level=m type=parallel>Le lac des cygnes</>
: <title level=m type=subordinate>grand ballet en 4 actes</>
: <title level=m type=subordinate>op. 20</>
[Score].
New York:  Broude Brothers; [1951] (B.B. 59). vi, 685 p.
</bibl>]]></eg><!-- example from ANSI Z39.29, sec. A.12.2, p.63 -->
 </p><p>The elements <gi tei="yes">author</gi> and <gi tei="yes">editor</gi> have, for printed
books and articles, a fairly obvious significance; for other kinds of
bibliographic items their proper usage may be less obvious.  The
<gi tei="yes">author</gi> element should be used for the person or agency with
primary responsibility for a work's intellectual content, and the
element <gi tei="yes">editor</gi> for an editor of the work.  Thus an organization
such as a radio or television station is usually accounted
<soCalled>author</soCalled> of a broadcast, for example, while the
author of a Government report will usually be the agency which produced
it.
 </p><p>For anyone else with responsibility for the work, the
<gi tei="yes">respStmt</gi> element should be used.  The nature of the
responsibility is indicated by means of a <gi tei="yes">resp</gi> element, and the
person, organization etc. responsible by a <gi tei="yes">name</gi> element.  At
least one of each of these must be given within the <gi tei="yes">respStmt</gi>
element, followed optionally by any number of either.  Examples of
secondary responsibility of this kind include the roles of illustrator,
translator, editor, annotator.  The <gi tei="yes">respStmt</gi> element may also
be used for editors, if it is desired to record the specific terms in
which their role is described.
 </p><p>Examples of <gi tei="yes">author</gi> and <gi tei="yes">editor</gi> may be found in
sections <xref target="COBITY"/>, and <xref target="COBICOL"/>; wherever
<gi tei="yes">author</gi> and <gi tei="yes">editor</gi> may occur, the <gi tei="yes">respStmt</gi>
element may also occur.  When one of these elements precedes or
immediately follows a title, it applies to that title; when it follows
an <gi tei="yes">edition</gi> element or occurs within an edition statement, it
applies to the edition in question.
 </p><p>In this example, the <gi tei="yes">respStmt</gi> elements apply to the work as
a whole, not merely to the first edition:
 
<eg><![CDATA[ <bibl>
    <author>Lominadze, D. G.</>
    <title level=m>Cyclotron waves in plasma.</title>
    <respStmt><resp>translated by</> <name>A. N. Dellis;</name>
              <resp>edited by</> <name>S. M. Hamberger.</name>
    </respStmt>
    <edition>1st ed.</>
    <imprint><pubPlace>Oxford:</> <publisher>Pergamon Press,</>
       <date>1981.</></imprint>
    <extent>206 p.</>
    <title level=s>International series in natural philosophy.</>
    <note place=inline>Translation of:
      <title level=m lang=RU>Ciklotronnye volny v plazme.</></>
</bibl>]]></eg><!-- from ISO 690: 1987, clause 4.1, p. 2. -->
 </p><p>In this example, by contrast, the <gi tei="yes">respStmt</gi> element applies
to the edition, and not to the collection per se (Moser and Tervooren
were not responsible for the first thirty-five printings); the elements
of the reference have been reordered from their appearance on the title
page of the volume in order to ensure the correct relationship of the
collection title, the edition statement, and the statement of
responsibility.
 
<eg><![CDATA[<biblStruct>
<monogr>
    <title>Des Minnesangs Fr&uuml;hling</title>
    <note place=inline>Mit 1 Faksimile</note>
    <edition>36., neugestaltete und erweiterte Auflage</edition>
    <respStmt>
         <resp>Unter Benutzung der Ausgaben
         von <name>Karl Lachmann</> und <name>Moriz Haupt</>,
         <name>Friedrich Vogt</> und <name>Carl von Kraus</>
         bearbeitet von
         </resp>
         <name>Hugo Moser</>
         <!-- und -->
         <name>Helmut Tervooren</>
    </respStmt>
    <imprint>
         <biblScope type=volume>I</>
         <biblScope type='volume title'>Texte</>
         <pubPlace>Stuttgart</>
         <publisher>S. Hirzel Verlag</>
         <date>1977</>
    </imprint>
</monogr>
</biblStruct>]]></eg>
 <!-- reference taken from book in hand by MSM. --><!-- note that from the book it is impossible to --><!-- tell whether this is the 36th edition of --><!-- MF or of Moser/Tervooren's edition.  -->
 <!-- <p>The formal definition of the <gi>name</gi>,           --><!-- <gi>person</gi>, <gi>individual</gi>, <gi>org</gi>, and  --><!-- <gi>organization</gi> elements may be found in section   --><!-- <xref target=CONA>.  Definitions for the                 --><!-- <gi>respStmt</gi> and <gi>role</gi> elements are         --><!-- provided in section <xref target=HD6>.                   --><!-- This is a fat lie! (LB)                                  -->
 
With the exception of the <gi tei="yes">name</gi> element (for which see section<xref target="CONA"/>
), the elements described in this section are defined
as follows:
 
<dtdFrag id="DCOBICOR" n="Author, title, etc." contin="DCOBI"><tagDecl tagDoc="AUTHOR"/><tagDecl tagDoc="EDITOR"/><tagDecl tagDoc="RESP"/><tagDecl tagDoc="ROLE"/><tagDecl tagDoc="TITLE"/><tagDecl tagDoc="MEETING"/></dtdFrag>
 </p></div4><div4 id="COBICOI" name="Section" ref="Y"><head>Imprint, Pagination, and Other Details</head><p>By <cited>imprint</cited> is meant all the information relating to the
publication of a work:  the person or organization by whose authority
and in whose name a bibliographic entity such as a book is made public
or distributed (whether a commercial publisher or some other
organization), the place of publication, and a date.  It may also
include a full address for the publisher or organization.
Full bibliographic references usually specify either the number of pages
in a print publication (or equivalent information for non-print
materials), or the specific location of the material being cited within
its containing publication.  The following elements are provided to hold
this information:
 
<tagList style="one-line"><tagDesc tagDoc="IMPRINT"/><tagDesc tagDoc="ADDRESS"/><tagDesc tagDoc="PUBPLACE"/><tagDesc tagDoc="PUBLISHR"/><tagDesc tagDoc="DATE"/><tagDesc tagDoc="IDNO" atts="type"/><tagDesc tagDoc="EXTENT"/><tagDesc tagDoc="BIBLSCOP" atts="type"/></tagList>
 </p><p>For bibliographic purposes, usually only the place (or places) of
publication are required, possibly including the name of the country,
rather than a full address; the element <gi tei="yes">pubPlace</gi> is provided
for this purpose.<!-- for this reason, the element <gi>city</gi> may be supplied on --><!-- its own (outside of an <gi>address</gi> element) in this context.  -->
Where however the full postal address is likely to be of importance in
identifying or locating the bibliographic item concerned, it may be
supplied and tagged using the <gi tei="yes">address</gi> element described in
section <xref target="CONAAD"/>.  Alternatively, if desired, the<!-- <gi>place</gi> element described in section <xref target=CONANA> may be -->
<gi tei="yes">rs</gi> or <gi tei="yes">name</gi> elements described in section <xref target="CONARS"/> may be used; this involves no claim that the information
given is either a full address or the name of a city.
 <!-- <p>The name of the publisher of an item may be marked    --><!-- using the <gi>publisher</gi> tag; if the item is made    --><!-- public (<soCalled>published</soCalled>) by an            --><!-- organization other than a conventional publisher, it     --><!-- may be preferable to identify that organization using    --><!-- the <gi>org</gi> or <gi>organization</gi> element.       --><!-- This is frequently the case with technical reports:      -->
 </p><p>The name of the publisher of an item should be marked using the
<gi tei="yes">publisher</gi> tag even if the item is made public
(<soCalled>published</soCalled>) by an organization other than a
conventional publisher, as is frequently the case with technical
reports:
 
<eg><![CDATA[<biblStruct>
<monogr>
    <author>Nicholas, Charles K.</author>
    <author>Welsch, Lawrence A.</author>
    <title>On the interchangeability of SGML and ODA</title>
    <imprint>
         <pubPlace>Gaithersburg, MD</pubPlace>
         <publisher>National Institute of Standards and Technology
         </publisher>
         <date value='1992-01'>January 1992</date>
    </imprint>
    <extent>19 pp.</extent>
</monogr>
<idno type='NIST'>NISTIR 4681</idno>
</biblStruct>]]></eg>
 
and with dissertations:
 
<eg><![CDATA[<biblStruct>
<monogr>
    <author>Hansen, W.</>
    <title level=u>Creation of hierarchic text
         with a computer display</>
    <note place=inline>Ph.D. dissertation</>
    <imprint>
         <publisher>Dept. of Computer Science, Stanford Univ.</>
         <pubPlace>Stanford, CA</>
         <date value='1971-06'>June 1971</>
    </imprint>
</monogr>
</biblStruct>]]></eg>
 <!-- reference is from p. 304, bibliography, of Reps and       --><!-- Teitelbaum, The Synthesizer Generator:  A system for     --><!-- constructing language-based editors.                     --><!-- or could maybe use a respStmt - if this were allowed in imprint -->
 </p><p>When an item has been reprinted, especially reprinted without change
from a specific earlier edition, the reprint may appear in a
<gi tei="yes">monogr</gi> element with only the <gi tei="yes">imprint</gi> and other details
of the reprint.  In the following example, a microform reprint has been
issued without any change in the title or authorship.  The series
statement here applies only to the second <gi tei="yes">monogr</gi> element.
 
<eg><![CDATA[<biblStruct>
<monogr>
    <author>Shirley, James</>
    <title type=main>The gentlemen of Venice</>
    <title type=subordinate>a tragi-comedie presented at
         the private house in Salisbury Court by
         Her Majesties servants</>
    <note place=inline>[Microform]</>
    <imprint>
         <pubPlace>London</>
         <publisher>H. Moseley</>
         <date>1655</>
    </imprint>
    <extent>78 p.</>
</monogr>
<monogr>
    <imprint>
         <pubPlace>New York</>
         <publisher>Readex Microprint</>
         <date>1953</>
    </imprint>
   <extent>1 microprint card, 23 x 15 cm.</>
</monogr>
<series>
    <title>Three centuries of drama:  English, 1642-1700</>
</series>
 </biblStruct>]]></eg><!-- example from ANSI Z39.29, sec. A.3.12.1, p.41 -->
 </p><p>A bibliographic description, particularly for an analytic title, will
often include some additional information specifying its location, for
example as a volume number, page number, range of page numbers, or name
or number of a subdivision of the host work.  The element
<gi tei="yes">biblScope</gi> may be used to identify such information if it is
present.  Where it is desired to distinguish different classes of such
information (volume number, page number, chapter number, etc.), the
<att tei="yes">type</att> attribute may be used with any convenient typology.
 </p><p>When the item being cited is a journal article, the <gi tei="yes">imprint</gi>
element describing the issue in which it appeared will typically contain
<gi tei="yes">biblScope</gi> elements for volume and page numbers, together with a
<gi tei="yes">date</gi> element.
 </p><p>For example:
 
<eg><![CDATA[<biblStruct>
<analytic>
    <author>Wrigley, E. A.</>
    <title>Parish registers and the historian</>
</analytic>
<!-- in -->
<monogr>
    <editor>Steel, D. J.</>
    <title>National index of parish registers</>
    <imprint>
         <pubPlace>London</pubPlace>
         <publisher>Society of Genealogists</>
         <date value='1968'>1968</>
    </imprint>
    <biblScope type=volume>vol. 1</>
    <biblScope type=pages>pp. 155-167.</>
</monogr>
</biblStruct>]]></eg>
 </p><p>The <att tei="yes">type</att> attribute on <gi tei="yes">biblScope</gi> is optional:
both the following are legal examples:
 
<eg><![CDATA[<biblStruct>
<analytic>
    <author>Boguraev, Branimir</>
    <author>Neff, Mary</>
    <title>Text Representation, Dictionary Structure,
         and Lexical Knowledge</>
</analytic>
<!-- in -->
<monogr>
    <title level=j>Literary & Linguistic Computing</>
    <imprint>
         <biblScope type=volume>7</>
         <biblScope type=issue>2</>
         <date>1992</>
         <biblScope type=pages>110-112</>
    </imprint>
</monogr>
</biblStruct>]]></eg>
 
<eg><![CDATA[<biblStruct>
<analytic>
    <author>Chesnutt, David</>
    <title>Historical Editions in the States</>
</analytic>
<!-- in -->
<monogr>
    <title level=j>Computers and the Humanities</>
    <imprint>
         <biblScope>25.6</>
         <date value='1991-12'>(December, 1991):</>
         <biblScope>377-380</>
    </imprint>
</monogr>
</biblStruct>]]></eg>
 <!-- TYPE attribute dropped from biblScope in Chesnutt        --><!-- example, as per WWP suggestion (otherwise lead-in makes  --><!-- no sense) (msm)                                          -->
 </p><p>Formal definitions for the elements described in this section are as
follows:
 
<dtdFrag id="DCOPUB" n="Bibliographic subelements" contin="DCOBI"><tagDecl tagDoc="IMPRINT"/><tagDecl tagDoc="PUBLISHR"/><tagDecl tagDoc="BIBLSCOP"/><tagDecl tagDoc="PUBPLACE"/><commDecl>Note and date are defined elsewhere, as are extent, address,
and idno.</commDecl></dtdFrag>
 </p></div4><div4 id="COBICOS" name="Section" ref="Y"><head>Series Information</head><p>Series information may (in <gi tei="yes">bibl</gi> elements) or must (in
<gi tei="yes">biblStruct</gi> elements) be enclosed in a <gi tei="yes">series</gi> element
or (in a <gi tei="yes">biblFull</gi> element) a <gi tei="yes">seriesStmt</gi> element.  The
title of the series may be tagged <tag compl="full" tei="yes">title level=s</tag>, the
volume number <tag compl="full" tei="yes">biblScope type=volume</tag>, and responsibility
statements for the series (e.g. the name and affiliation of the editor,
as in the example in section <xref target="COBICOL"/>) may be tagged
<tag compl="full" tei="yes">editor</tag> or <tag compl="full" tei="yes">respStmt</tag>.
 </p></div4><div4 id="COBICON" name="Section" ref="Y"><head>Notes and Other Additional Information</head><p>Explanatory notes about the publication of unusual items, the form of
an item (e.g.  <cited>[Score]</cited> or <cited>[Microform]</cited>), or
its provenance (e.g.  <cited>translation of ...</cited>) may be tagged
using the <gi tei="yes">note</gi> element.  The same element may be used for any
descriptive annotation of a bibliographic entry in a database.
 
<tagList style="one-line"><tagDesc tagDoc="NOTE" atts="type place"/></tagList>
 </p><p>For example:
 
<eg><![CDATA[<bibl><author>Coombs, James H., Allen H. Renear,
       and Steven J. DeRose.</author>
       <title level=a>Markup Systems and the Future of Scholarly
       Text Processing.</title>
       <title level=j>Communications of the ACM</title>
       <biblScope>30.11 (November 1987):  933-947.</biblScope>
       <note>Classic polemic supporting descriptive over procedural
            markup in scholarly work.</note>]]></eg>
 </p></div4><div4 id="COBICOO" name="Section" ref="Y"><head>Order of Components within References</head><p>The order of elements in <gi tei="yes">bibl</gi> elements is not constrained.
 </p><p>In <gi tei="yes">biblStruct</gi> elements, the <gi tei="yes">analytic</gi> element, if
it occurs, must come first, followed by one or more <gi tei="yes">monogr</gi> and
<gi tei="yes">series</gi> elements, which may appear intermingled (as long as a
<gi tei="yes">monogr</gi> element comes first).  Within <gi tei="yes">analytic</gi>, the
title(s), author(s), editor(s), and other statements of responsibility
may appear in any order; it is recommended that all forms of the title
be given together.  Within <gi tei="yes">monogr</gi>, the author, editor, and
statements of responsibility may either come first or else follow the
monographic title(s).  Following these, the elements must appear in the
following order:
 
<list type="simple"><item><gi tei="yes">note</gi>s on the publication (and <gi tei="yes">meeting</gi> elements
describing the conference, in the case of a proceedings volume)</item><item><gi tei="yes">edition</gi> elements, each followed by any related
<gi tei="yes">editor</gi> or <gi tei="yes">respStmt</gi> elements</item><item><gi tei="yes">imprint</gi></item><item><gi tei="yes">biblScope</gi></item></list>
Within <gi tei="yes">imprint</gi>, the elements allowed may appear in any
order.</p><p>Finally, within the <gi tei="yes">series</gi> information in a
<gi tei="yes">biblStruct</gi>, the sequence of elements is not constrained.
 </p><p>If more detailed structuring of a bibliographic description is
required, the <gi tei="yes">biblFull</gi> element should be used.  This is not
further described here, as its contents are essentially equivalent to
those of the <gi tei="yes">fileDesc</gi> element in the <gi tei="yes">teiHeader</gi>, which
is fully described in section <xref target="HD2"/>.
 </p></div4></div3><div3 id="COBIXR" name="subsection" ref="Y"><head>Bibliographic Pointers </head><p>References which are pointers to bibliographic items, of whatever
kind, should be treated in the same way as other cross-references (see
section <xref target="COXR"/>).  As discussed in that section, cross
referencing within TEI texts is in general represented by means of
<gi tei="yes">ptr</gi> or <gi tei="yes">ref</gi> elements.  A <att tei="yes">target</att> attribute on
these elements is used to supply an identifying value for the target of
the cross reference, which should be, in the case of bibliographic
elements, a bibliographic reference of some kind.  Where the form of the
reference itself is unimportant, or may be reconstructed mechanically,
or is not to be encoded, the <gi tei="yes">ptr</gi> element is used, as in the
following example:
 
<eg><![CDATA[As shown above (<ptr target=NEL80>)...]]></eg>
 </p><p>Where the form of the reference is important, or contains additional
qualifying information which is to be kept but distinguished from the
surrounding text, the <gi tei="yes">ref</gi> element should be used, as in the
following example:
 
<eg><![CDATA[Nelson claims <ref target=NEL80>(ibid, passim)</ref> ...]]></eg>
 <!--Following suggestion is only possible if <biblScope> becomes a phrase. --><!--Which it currently isnt.  -->
 
 <!--<p>When it is desired to distinguish the short form of the reference --><!--itself from the additional qualifying information added to it, the --><!--additional information may be marked as a <gi>biblScope</gi> element: --><!--  --><!--<eg><![ CDATA[ --><!--Nelson claims (<ref target=NEL80>Nelson [1980], <biblScope>especially --><!--pages 13-37</ref>) ... --><!--]]> --><!--</eg> --><!--  --><!--(This distinction between the short form and the qualifying information --><!--may be useful in the context of document production or normalization of --><!--bibliographic references.) -->
 
It may be important to distinguish between the short form of a
bibliographic reference and some qualifying or additional information.
The latter should not appear within the scope of the <gi tei="yes">ref</gi>
element when this is the case, as for example in an application
concerned to normalize bibliographic references:
 
<eg><![CDATA[Nelson claims (<ref target=NEL80>Nelson [1980]</ref>, pages 13-37) ...]]></eg>
 </p></div3><div3 id="COBIOT" name="subsection" ref="Y"><head>Relationship to Other Bibliographic Schemes</head><p>The bibliographic tagging defined here can capture the distinctions
required by most bibliographic encoding systems; for the benefit of
users of some commonly used systems, the following lists of equivalences
are offered, showing the relationship of the markup defined here to the
fields defined for bibliographic records in the Scribe, BibTeX, and
ProCite systems.
 </p><p>The various bibliographic fields defined for use in the Scribe and
BibTeX systems of bibliographic databases have the following equivalents
in the scheme presented here:<note source="auth" place="foot" anchored="Y">The BibTeX scheme is
intentionally compatible with that of Scribe, although it omits some
fields used by Scribe.  Hence only one list of fields is given
here.</note><!-- need bibliographic references for Scribe and BibTeX. -msm -->
Elements and structures available in the tag set defined here which
have no analogues in Scribe and BibTeX are not noted.
 
<list type="gloss"><label>address     </label><item>tag as <tag compl="full" tei="yes">city</tag>, <tag compl="full" tei="yes">place</tag>,
or <tag compl="full" tei="yes">address</tag></item><label>annote      </label><item>tag as <tag compl="full" tei="yes">note</tag></item><label>author      </label><item>tag as <tag compl="full" tei="yes">author</tag></item><label>booktitle   </label><item>tag as <tag compl="full" tei="yes">title level=m</tag>
or <tag compl="full" tei="yes">title</tag> within <tag compl="full" tei="yes">monogr</tag></item><label>chapter     </label><item>tag as <tag compl="full" tei="yes">biblScope type=chapter</tag></item><label>date        </label><item>used only to record date entry was made in the
bibliographic database; not supported</item><label>edition     </label><item>tag as <tag compl="full" tei="yes">edition</tag></item><label>editor      </label><item>tag as <tag compl="full" tei="yes">editor</tag> or <tag compl="full" tei="yes">respStmt</tag></item><label>editors     </label><item>tag as multiple <tag compl="full" tei="yes">editor</tag>
or <tag compl="full" tei="yes">respStmt</tag> elements</item><label>fullauthor  </label><item>use the <att tei="yes">reg</att> attribute
on <tag compl="full" tei="yes">author</tag> or <tag compl="full" tei="yes">name</tag></item><label>fullorganization </label><item>use the <att tei="yes">reg</att> attribute
on <tag compl="full" tei="yes">name type=org</tag></item><label>howpublished  </label><item>tag as <tag compl="full" tei="yes">note</tag>, possibly using
the form <tag compl="full" tei="yes">note place=inline</tag></item><label>institution </label><item>used only for issuer of technical reports;
tag as <tag compl="full" tei="yes">publisher</tag><!-- , <tag>org</tag>,  or <tag>organization</tag> --></item><label>journal     </label><item>tag as <tag compl="full" tei="yes">title level=j</tag>
or <tag compl="full" tei="yes">title</tag> within <tag compl="full" tei="yes">monogr</tag></item><label>key         </label><item>used to specify an alternate sort key for
the bibliographic item, for use instead of
author's or editor's name; not supported</item><label>meeting     </label><item>tag as <tag compl="full" tei="yes">meeting</tag> or as <tag compl="full" tei="yes">note</tag></item><label>month       </label><item>use <tag compl="full" tei="yes">date</tag>; if the date is not in a
trivially parseable form, use the <att tei="yes">value</att>
attribute to provide an ISO-format equivalent</item><label>note        </label><item>tag as <tag compl="full" tei="yes">note</tag></item><label>number      </label><item>tag as <tag compl="full" tei="yes">biblScope type=issue</tag>
or <tag compl="full" tei="yes">biblScope type=number</tag>; for
technical report numbers, use <tag compl="full" tei="yes">idno
type=docno</tag></item><label>organization </label><item>used only for sponsor of conference;
use <tag compl="full" tei="yes">name type=org</tag>
within <tag compl="full" tei="yes">respStmt</tag>
within <tag compl="full" tei="yes">meeting</tag> element</item><label>pages       </label><item>tag as <tag compl="full" tei="yes">biblScope type=pages</tag></item><label>publisher   </label><item>tag as <tag compl="full" tei="yes">publisher</tag></item><label>school      </label><item>used only for institutions at which
thesis work is done; tag as <tag compl="full" tei="yes">publisher</tag><!-- org</tag>  or <tag>organization</tag> --></item><label>series      </label><item>tag as <tag compl="full" tei="yes">title level=s</tag>
or <tag compl="full" tei="yes">title</tag> within <tag compl="full" tei="yes">series</tag></item><label>title       </label><item>tag as <tag compl="full" tei="yes">title</tag> in appropriate
context or with appropriate <att tei="yes">level</att>
value</item><label>volume      </label><item>tag as <tag compl="full" tei="yes">biblScope type=volume</tag></item><label>year        </label><item>tag as <tag compl="full" tei="yes">date</tag>; if the date is not in a
trivially parseable form, use the <att tei="yes">value</att>
attribute to provide an ISO-format equivalent</item></list><!-- need similar list for ProCite --><?tei:EOF p2cobi.odd ??>

 <!-- COdv Verse and Drama elements (new)                      --><?tei:SOF p2codv.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2codv.odd,v $
    * Revision 1.9  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.8  98/02/01  17:51:31  tei
    * No changes made; this is a vacuous checkin
    * 
    * Revision 1.7  94/03/27  21:45:15  msmcq
    * Correction of typos from DB, JL, HG, and WWP
    * --><!-- Revisions:                                               --><!-- 94-03-24 : MSM : disambiguation of term, q (code, ident) --><!-- 93-11-18 : MSM : Change titles on divs for Verse, Drama  --><!-- 92-12-10 : MSM : add fix for partial LGs, from LB        --><!-- 92-12-09 : MSM : add clarifying comment on LB            --><!-- 92-12-09 : MSM : normalize sentence-end spacing          --><!-- 92-12-09 : MSM : rename metre as met                     --><!-- 92-12-09 : MSM : add blank after /speaker                --><!-- 92-12-07 : MSM : correct botched /eg                     --><!-- 92-12-07 : MSM : revise for publication                  --><!-- 92-12-07 : MSM : add example from Q1                     --><!-- 92-12-07 : MSM : do not change PCDATA in Tempest         --><!-- 92-12-06 : MSM : change dtdfrag ids, scan for long lines in eg --><!-- 92-12-06 : MSM : correct xref to COrs, idref in dtdfrags -->
 </p></div3></div2><div2 id="CODV" name="section" ref="Y"><head>Passages of Verse or Drama</head><p>The following elements are included in the core tag set for the
convenience of those encoding texts which include mixtures of prose,
verse and drama.
 
<tagList style="one-line"><tagDesc tagDoc="L" atts="part"/><tagDesc tagDoc="LG"/><tagDesc tagDoc="SP"/><tagDesc tagDoc="SPEAKER"/><tagDesc tagDoc="STAGE" atts="type"/></tagList>
 </p><p>Full details of other, more specialized, elements for the encoding of
texts which are predominantly verse or drama are described in the
appropriate chapter of part three (for verse, see the verse base
described in chapter <xref target="VE"/>; for performance texts, see the
drama base described in chapter <xref target="DR"/>).  In this section, we
describe only the elements listed above, all of which can appear in any
text, whichever of the three modes prose, verse, or drama may predominate
in it.
 </p><div3 id="COVE" name="subsection" ref="Y"><head>Core Tags for Verse</head><p>Like other written texts, verse texts or poems may be hierarchically
subdivided, for example into books or cantos.  These structural
subdivisions should be encoded using the general purpose <gi tei="yes">div</gi>
or <gi tei="yes">div1</gi> (etc.) elements described below in chapters <xref target="PR"/> and <xref target="VE"/>.  The fundamental unit of a verse text
is the verse line rather than the paragraph, however.
 </p><p>The <gi tei="yes">l</gi> element is used to mark up verse lines, that is
metrical rather than typographic lines.  Where a metrical line is
interrupted by a typographic line break, the encoder may choose to
ignore the fact entirely or to use the empty <gi tei="yes">lb</gi> (line break)
element discussed in <xref target="CORS"/>.  In the copy text, the
following example is printed on four typographic lines, beginning with
the words <cited>There</cited>, <cited>From</cited>, <cited>The</cited>,
and <cited>the</cited>.
 
<eg><![CDATA[<l>There they lie, in the largest, in an
   open space in the woods,
<l>From 500 to 600 poor fellows &mdash; the groans
   and screams &mdash;
<l>The odor of blood, mixed with the fresh scent
   of the night, <lb>the grass, the trees &mdash;
   that Slaughter-house!]]></eg><!-- Walt Whitman, 1863, cited by Daniel Aaron, The           --><!-- Unwritten War:  American Writers and the Civil War       --><!-- (London:  OUP, 1973).  Aaron doesn't give any more       --><!-- detailed citation.  Need to replace this with an         --><!-- example from a more important edition, one about whose   --><!-- line breaks one might reasonably care.                   -->
 </p><p>Where verse lines are not properly nested within the enclosing
hierarchy (for example where verse lines cross larger boundaries such
as verse paragraphs or speeches) the encoder may choose to use one of
the techniques discussed in chapter <xref target="NH"/>, or to use the
<att tei="yes">part</att> attribute to indicate that the verse line is
incomplete, as in the following example:
 
<eg><![CDATA[ <l>Thou fumblest <name>Eros</>, and my Queenes a Squire
 <l>More tight at this, then thou:  Dispatch. O Loue,
 <l>That thou couldst see my Warres to day, and knew'st
 <l>The Royall Occupation, thou should'st see
 <l part=i>A Workeman in't.
 <stage>Enter an Armed Soldier.</stage>
 <l part=f>Good morrow to thee, welcome. ...]]></eg><!-- Better example needed here --><!-- W. Shakespeare, Antony and Cleopatra, 4.4.14-21, cited   --><!-- from A New Variorum Edition of Shakespeare:  A & C,      --><!-- ed. Martin Spevack (NY:  MLA, 1990), p. 242.             --><!-- I have not had time to find a better example.  -MSM      -->
 </p><p>In some verse forms, regular groupings of lines are regarded as units
of some kind, often identified by a regular verse scheme.  In stichic
verse and couplets, groups of lines analogous to paragraphs are often
indicated by indentation.  In other verse forms, lines are grouped into
irregular sequences indicated simply by white space.  The neutral
<gi tei="yes">lg</gi> or line group element may be used to mark any such grouping
of lines; the <att tei="yes">type</att> is available to further categorize the
line group where this is felt desirable, as in the following example.
This example also demonstrates the <att tei="yes">rend</att> attribute to indicate
whether or not a line is indented.
 <!-- rhyme is only enabled if you have the verse base   -->
 
<eg><![CDATA[<lg type=stanza>
<l>Come fill up the Glass,
<l rend=indent>Round, round let it pass,
<l>'Till our Reason be lost in our Wine:
<l rend=indent>Leave Conscience's Rules
<l rend=indent>To Women and Fools,
<l>This only can make us divine.
</lg>
<lg type=refrain n='Chorus'>
<l>Then a Mohock, a Mohock I'll be,
<l>No Laws shall restrain
<l>Our Libertine Reign,
<l>We'll riot, drink on, and be free.
</lg>]]></eg><!-- from Gay's Beggars Opera -->
 </p><p>For some kinds of analysis, it may be useful to identify different
kinds of line group within the same piece of verse.  Such line groups
may self-nest, in much the same way as the un-numbered <gi tei="yes">div</gi>
element described in chapter <xref target="PR"/>.  For example:
 <!-- quote stanza from Sir Gawayn -->
 </p><p>The <att tei="yes">part</att> attribute may also be attached to a <gi tei="yes">lg</gi>
element to indicate that it is incomplete, for example because it forms
part of a group that is divided between two speakers, as in the
following example:
 
<eg><![CDATA[<sp><speaker>First Voice</>
<lg type=stanza part=I>
<l>But why drives on that ship so fast
<l>Withouten wave or wind?
</lg>
<sp><speaker>Second Voice</speaker>
<lg part=F>
<l>The air is cut away before,
<l>And closes from behind.
</lg>]]></eg><!-- Rime of the Ancient Marynere from Lyrical Ballads 1798 -->
 </p><p>For alternative methods of aligning groups of lines which do not form
simple hierarchic groups, or which are discontinuous, see the more
detailed discussion in chapter <xref target="SA"/>.  For discussion of
other elements and attributes specific to the encoding of verse, see
chapter <xref target="VE"/>.
 </p><p>These elements are defined as follows:
<dtdFrag id="DCOVE" n="Verse"><tagDecl tagDoc="L"/><tagDecl tagDoc="LG"/></dtdFrag>
 </p></div3><div3 id="CODR" name="subsection" ref="Y"><head>Core Tags for Drama</head><p>Like other written texts, dramatic and other <term>performance
texts</term> such as cinema or TV scripts are often hierarchically
organized, for example into acts and scenes.  These structural
subdivisions should be encoded using the general purpose <gi tei="yes">div</gi> or
<gi tei="yes">div1</gi> (etc.) elements described below in chapters <xref target="PR"/> and <xref target="DR"/>.  Within these divisions, the body of a
performance text typically consists of <term rend="noindex">speeches</term>, often prefixed by a phrase indicating
who is speaking, and occasionally interspersed with stage directions of
various kinds.
 </p><p>In the following simple example, each speech consists of a single
paragraph:
 
<eg><![CDATA[<div2 type=scene n='I.2'>
<head>Scene 2.</head>
<stage type=setting>Peachum, Filch.</stage>
<sp><speaker>FILCH.</speaker><p>Sir, Black Moll hath sent word her
Trial comes on in the Afternoon, and she hopes you will order Matters
so as to bring her off.
<sp><speaker>PEACHUM.</speaker><p>Why, she may plead her Belly
at worst; to my Knowledge she hath taken care of that Security.
But, as the Wench is very active and industrious, you may satisfy
her that I'll soften the Evidence.
<sp><speaker>FILCH.</speaker><p>Tom Gagg, sir, is found guilty.]]></eg><!-- Gay's Beggars Opera -->
 </p><p>In the following example, each speech consists of a sequence of verse
lines, some of them being marked as metrically incomplete:
 
<eg><![CDATA[<div1 type='Act' n='I'><head>ACT I</>
<div2 type='Scene' n='1'><head>SCENE I</head>
<stage rend=italic>
Enter Barnardo and Francisco, two Sentinels, at several doors</stage>
<sp><speaker>Barn</><l part=Y>Who's there?
<sp><speaker>Fran</><l>Nay, answer me.  Stand and unfold yourself.
<sp><speaker>Barn</><l part=i>Long live the King!
<sp><speaker>Fran</><l part=m>Barnardo?
<sp><speaker>Barn</><l part=f>He.
<sp><speaker>Fran</><l>You come most carefully upon your hour.
<sp><speaker>Barn</><l>'Tis now struck twelve.  Get thee to bed,
 Francisco.
<sp><speaker>Fran</><l>For this relief much thanks.'Tis bitter cold,
<l part=i>And I am sick at heart.]]></eg><!-- Wells & Taylor, Hamlet I.i -->
 </p><p>In some cases, as here in the First Quarto of <title>Hamlet</title>,
the printed speaker attributions need to be supplemented by use of the
<att tei="yes">who</att> attribute; again, the lines are marked as complete or
incomplete:
 
<eg><![CDATA[<stage>Enter two Centinels.
<add place=right resp=ms>
Now call'd Bernardo & Francesco.
</add></stage>
<sp who='Francisco'><speaker>1.</>
    <l part=y>STand:  who is that?</sp>
<sp who='Barnardo'><speaker>2.</>
    <l part=y>Tis I.</sp>
<sp who='Francisco'><speaker>1.</>
    <l>O you come most carefully vpon your
       watch,</sp>
<sp who='Barnardo'><speaker>2.</>
    <l>And if you meete Marcellus and Horatio,
    <l>The partners of my watch, bid them make haste.</sp>
<sp who='Francisco'><speaker>1.</>
    <l part=y>I will:  See who goes there.</sp>
<stage>Enter Horatio and Marcellus.</>
<sp who='Horatio'><speaker>Hor.</>
    <l part=i>Friends to this ground.</sp>
<sp who='Marcellus'><speaker>Mar.</>
    <l part=f>And leegemen to the Dane,
    <l>O farewell honest souldier, who hath
    releeued you?</sp>
<sp who='Francisco'><speaker>1.</>
    <l>Barnardo hath my place, giue you good night.</sp>]]></eg><!-- Hamlet I.i, Q1 (edited, from old file) -->
 </p><p>By contrast with the preceding examples, the following encodes an
early printed edition without making any assumption about which parts
are prose or verse:
 
<eg><![CDATA[<div1 type=act n='I'>
<div2 type=scene n='1'>
<head rend=italic>Actus primus, Scena prima.</head>
<stage type=setting rend=italic>
A tempestuous noise of Thunder and Lightning heard:  Enter
a Ship-master, and a Boteswaine.</stage>
<sp><speaker>Master.</speaker><p> Bote-swaine.</sp>
<sp><speaker>Botes.</speaker><p> Heere Master: What cheere?</sp>
<sp><speaker>Mast.</speaker><p> Good: Speake to th' Mariners: fall
too't, yarely, or we run our selues a ground,
bestirre, bestirre.  <stage type=move>Exit.</stage></sp>
<stage type=move>Enter Mariners.</stage>
<sp><speaker>Botes.</speaker>
<p>Heigh my hearts, cheerely, cheerely my harts:
yare, yare: Take in the toppe-sale: Tend to th' Masters
whistle: Blow till thou burst thy winde, if roome e-nough.</sp>]]></eg><!-- Tempest first folio -->
 </p><p>The <gi tei="yes">sp</gi> and <gi tei="yes">stage</gi> elements should also be used to
mark parts of a text otherwise in prose which are presented as if they
were dialogue in a play.  For example:
 
<eg><![CDATA[<sp><speaker>The reverend Doctor Opimiam</speaker>
<p>I do not think I have named a single unpresentable
fish. </sp>
<sp><speaker>Mr Gryll</speaker><p>Bream, Doctor: there
is not much to be said for bream.</sp>
<sp><speaker>The Reverend Doctor
Opimiam</speaker><p>On the contrary, sir, I think
there is much to be said for him.  In the first
place....
<p>Fish, Miss Gryll -- I could discourse to you on
fish by the hour:  but for the present I will
forbear...
</sp>]]></eg><!-- Peacock, Gryll Grange, p 778 -->
 
<eg><![CDATA[<sp><speaker>Lord Curryfin</speaker>
<stage>(after a pause).</stage>
<p><q>Mass</q> as the second grave-digger
says in <title>Hamlet</title>,
<q>I cannot tell.</q>
</sp>
<p>A chorus of laughter dissolved the sitting.]]></eg><!-- ib. p 885 -->
 </p><p>These elements are defined as follows:
<dtdFrag id="DCODR" n="Drama"><tagDecl tagDoc="SP"/><tagDecl tagDoc="SPEAKER"/><tagDecl tagDoc="STAGE"/></dtdFrag>
 <?tei:EOF p2codv.odd ??>

 <!-- COse Arbitrary Segments (P1 5.8.1 plus)                  --><!-- &p2.COse;  -->
 <!-- 23e Other Tags for all Text Types                        --><!-- (id=p2.23E, file=P223E, MSM) (index)                     --><!-- &p2.COmi; -->
 
 </p></div3></div2><div2 id="COOV" name="section" ref="Y"><head>Overview of the Core Tag Set
 </head><p>Except for those tags designed to be used in concurrent markup
streams, all the elements described in this chapter occur in the
<term>core</term> of TEI tags, defined by the following DTD fragment.
 <!-- First, the DTD defines a number of element classes used  --><!-- in the content models:                                   -->
 <!-- <dtdFrag id=DCO                                          --><!--          file=teicore2                                   --><!--          n='Elements available in all TEI dtds'>         -->
 <!-- <commDecl>TEIcore2:  Core Elements Available in All TEI  --><!-- DTDs</commDecl> &dtdstart;                               -->
 <!-- <commDecl>Definition of useful element classes, for use  --><!-- in defining content models.</commDecl>                   -->
 <!-- <claDecl classDoc=HQINTER  type=model>                   --><!-- <claDecl classDoc=HQPHRASE type=model>                   --><!-- <claDecl classDoc=DATA     type=model>                   --><!-- <claDecl classDoc=EDIT     type=model>                   --><!-- <claDecl classDoc=REFSYS   type=model>                   --><!-- <claDecl classDoc=LISTS    type=model>                   --><!-- <claDecl classDoc=NOTES    type=model>                   --><!-- <claDecl classDoc=CLBIBL   type=model>                   --><!-- <claDecl classDoc=CLSEG    type=model>                   --><!-- <claDecl classDoc=CLLOC    type=model>                   --><!--                                                          --><!-- <claDecl classDoc=PHRASE   type=model>                   --><!-- <claDecl classDoc=INTER    type=model>                   --><!-- <claDecl classDoc=CHUNK    type=model>                   --><!-- </dtdFrag>                                               -->
 <!-- <p>Next, some useful basic content models are defined;   --><!-- these will be used in the formal declaration of many     --><!-- elements:                                                -->
 <!-- <dtdFrag id=DCO2                                         --><!--          file=teicore2                                   --><!--          contin=DCO>                                     -->
 <!-- <commDecl>Definition of useful content                   --><!-- models.</commDecl>                                       -->
 <!-- <entDecl entDoc=PHRSEQ>                                  --><!-- <entDecl entDoc=CHKSEQ>                                  --><!-- <entDecl entDoc=PEPARAC>                                 --><!-- <entDecl entDoc=PESPECP>                                 --><!-- </dtdFrag>                                               -->
 <!-- <p>Finally, the elements of the TEI core are themselves  --><!-- defined:                                                 -->
 
<dtdFrag id="DCO" n="Elements available in all forms of the TEI main DTD" file="teicore2"><commDecl>Definition of elements, sub-group by sub-group.</commDecl><dtdRef dtdFrag="DCOPA"/><dtdRef dtdFrag="DCOHQ"/><dtdRef dtdFrag="DCONA"/><dtdRef dtdFrag="DCONU"/><dtdRef dtdFrag="DCODA"/><dtdRef dtdFrag="DCOAB"/><dtdRef dtdFrag="DCOEDC"/><dtdRef dtdFrag="DCOEDR"/><dtdRef dtdFrag="DCOEDA"/><dtdRef dtdFrag="DCOAD"/><dtdRef dtdFrag="DCOXR"/><dtdRef dtdFrag="DCOLI"/><dtdRef dtdFrag="DCONO"/><dtdRef dtdFrag="DCORSM"/><dtdRef dtdFrag="DCOBI"/><dtdRef dtdFrag="DCOVE"/><dtdRef dtdFrag="DCODR"/></dtdFrag>
 <!-- dtdRef dtdFrag=DCOSE --><?tei:EOF p2co.odd ??>
            <!-- 6 Tags in All TEI DTDs --><?tei:SOF p2ds.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2ds.odd,v $
    * Revision 1.4  1998/01/28 11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    *
    *--><!-- Revisions:                                               --><!-- 12 jan 98 : LB : fix egs --><!-- 93-06-03 : MSM : rename entities                         --><!-- 93-03-26 : MSM : one last typo corrected                 --><!-- 93-03-25 : MSM : final revision for publication          --><!--                  make new top file                       --><!-- 26 mar 93 : LB : added divn class                        --><!-- 14 Mar 93 : LB : added material on divtop elements       --><!--  9 Mar 93 : LB : cannibalized from old PR, CCGrp         -->
 </p></div2></div1><div1 id="DS" n="7" name="chapter" ref="Y"><head>Default Text Structure</head><p>This chapter describes the default high level structure for all TEI
documents.  The majority of the different base tag sets described in
part II simply embed the framework defined in this chapter while a few
redefine it with some minor modifications.  This chapter is therefore
relevant to every kind of TEI document.  For further details on the
overall structure of the TEI document type definitions, in particular
the use of base and additional tag sets, see chapter <xref target="ST"/>.
 </p><p>TEI texts may be regarded either as <term>unitary</term>, that is,
forming an organic whole, or as <term>composite,</term> that is,
consisting of several components which are in some important sense
independent of each other.  The distinction is not always entirely
obvious:  for example a collection of essays might be regarded as a
single item in some circumstances, or as a number of distinct items in
others.  In such borderline cases, the encoder must choose whether to
treat the text as unitary or composite; each may have advantages and
disadvantages in a given situation.
 </p><p>Whether unitary or composite, the text is marked with the
<gi tei="yes">text</gi> tag and may contain front matter, a text body, and back
matter.  In unitary texts, the text body is tagged <gi tei="yes">body</gi>; in
composite texts, where the text body consists of a series of subordinate
texts or groups, it is tagged <gi tei="yes">group</gi>.  The overall structure of
any text, unitary or composite, is thus defined by the following
elements:
 
<tagList style="one-line"><tagDesc tagDoc="TEXT"/><tagDesc tagDoc="FRONT"/><tagDesc tagDoc="BODY"/><tagDesc tagDoc="GROUP"/><tagDesc tagDoc="BACK"/></tagList>
 </p><p>The overall structure of a unitary text is:
<eg rend="skel"><![CDATA[ <tei.2>
 <teiHeader> ... </teiHeader>
 <text>
     <front>
        <!-- front matter of copy text goes here. -->
     </front>
     <body>
        <!-- body of text goes here. -->
     </body>
     <back>
        <!-- back matter of text, if any, here. -->
     </back>
 </text>
 </tei.2>]]></eg></p><p>The overall structure of a composite text made up of two unitary
texts is:
<eg rend="skel"><![CDATA[ <tei.2>
 <teiHeader> ... </teiHeader>
 <text>
    <front>
       <!-- front matter of composite text goes here. -->
    </front>
    <group>
       <text>
          <front>
             <!-- front matter of first unitary text, if any -->
          </front>
          <body>
             <!-- body of first unitary text  -->
          </body>
          <back>
             <!-- back matter of first unitary text, if any -->
          </back>
       </text>
       <text>
          <body>
             <!-- body of second unitary text -->
          </body>
       </text>
    </group>
    <back>
       <!-- back matter of composite text, if any -->
    </back>
 </text>
 </tei.2>]]></eg>
 </p><p>Each of these elements is further described in the following
subsections.  <gi tei="yes">text</gi>, <gi tei="yes">body</gi> and <gi tei="yes">group</gi> are
formally declared as follows:
 
<dtdFrag id="DDSTEXT" n="Top-level parts of default structure"><tagDecl tagDoc="TEXT"/><tagDecl tagDoc="BODY"/><tagDecl tagDoc="GROUP"/></dtdFrag>
 
Elements <gi tei="yes">front</gi> and <gi tei="yes">back</gi> are declared separately, as
further discussed in sections <xref target="DSFRONT"/> and <xref target="DSBACK"/>.  Textual elements, such as paragraphs, lists or phrases,
which nest within these major structural elements, are discussed in
chapter <xref target="CO"/> (for elements common to all kinds of document)
and in part II (for elements specific to a particular base).  The
<gi tei="yes">group</gi> element, used for composite texts, is further discussed
in section <xref target="DSGRP"/>.
 <?tei:SOF p2ds1.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2ds1.odd,v $
# Revision 1.7  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *--><!-- Revisions:                                               --><!-- 12 jan 98 : fixing egs --><!-- 4 Jan 98: remove redundant comma before discussion of opener --><!-- 4 mar: dtb typos --><!-- 28 dec 93: LB : divn attrib is sample, not complete      --><!-- 93-06-05 : MSM : fix ]]>                                 --><!-- 1993-03-26 : MSM,LB : last-minute typos and revisions    --><!-- 1993-03-25 : MSM : light revision for publ               -->
 </p><div2 id="DSDIV" name="section" ref="Y"><head>Divisions of the Body</head><p>In some texts, the body consists simply of a sequence of low-level
structural items, referred to here as <term>components</term> or
<term>component-level elements</term> (see section <xref target="STEC"/>).  Examples in prose texts include paragraphs or lists; in
dramatic texts, speeches and stage directions; in dictionaries,
dictionary entries.  In other cases sequences of such elements will be
grouped together hierarchically into textual divisions and subdivisions,
such as chapters or sections.  The names used for these structural
subdivisions of texts vary with the genre and period of the text, or
even with the whim of the author, editor or publisher.  For example, a
major subdivision of an epic or of the Bible is generally called a
<q>book</q>, that of a report is usually called a <q>part</q> or
<q>section</q>, that of a novel a <q>chapter</q> --- unless it is an
epistolary novel, in which case it may be called a <q>letter</q>.  Even
texts which are not organized as linear prose narratives, or not as
narratives at all, will frequently be subdivided in a similar way:  a
drama into <q>acts</q> and <q>scenes</q>; a reference book into
<q>sections</q>; a diary or day book into <q>entries</q>; a newspaper
into <q>issues</q> and <q>sections</q>, and so forth.
 </p><p>To cater for this variety, these Guidelines propose that all such
textual divisions be regarded as occurrences of the same neutrally named
elements, with an attribute <att tei="yes">type</att> used to categorize elements
independently of their hierarchic level.  Two alternative styles are
provided for the marking of these neutral divisions:
<term>numbered</term> and <term>un-numbered</term>.  Numbered divisions
are named <gi tei="yes">div0</gi>, <gi tei="yes">div1</gi>, <gi tei="yes">div2</gi>, etc., where the
number indicates the depth of this particular division within the
hierarchy, the largest such division being <q>div0</q>, any subdivision
within it being <q>div1</q>, any further sub-sub-division being
<q>div2</q> and so on.  Un-numbered divisions are simply named
<gi tei="yes">div</gi>, and allowed to nest recursively to indicate their
hierarchic depth.  The two styles may <emph>not</emph> be combined
within a single <gi tei="yes">front</gi>, <gi tei="yes">body</gi> or <gi tei="yes">back</gi> element.
 </p><div3 id="DSDIV1" name="subsection" ref="Y"><head>Un-numbered Divisions</head><p>The following element is used to identify textual subdivisions
in the un-numbered style:
<tagList style="one-line"><tagDesc tagDoc="DIV"/></tagList>
 
As a member of the class <term>divn</term>, this element has the
following additional attribute:
 
<adList classDoc="DIVN" atts="type"/>
 </p><p>Using this style, the body of a text containing two parts, each
composed of two chapters, might be represented as follows:
 
<eg rend="skel"><![CDATA[ <body>
 <div type='part' n='1'>
       <div type='chapter' n='1'>
       <!-- text of part 1, chapter 1 -->
       </div>
       <div n='2'>
       <!-- text of part 1, chapter 2-->
       </div>
 </div>
 <div type='part' n='2'>
       <div n='1' type='chapter'>
       <!-- text of part 2, chapter 1 -->
       </div>
       <div n='2'>
       <!-- text of part 2, chapter 2 -->
       </div>
 </div>
 </body>]]></eg>
 </p><p>Note that end-tags are mandatory for un-numbered divisions, to avoid
ambiguity.  Note also that the <att tei="yes">type</att> attribute must be
specified each time its value changes, for reasons discussed in section<xref target="DSDIV3"/>
 below.
 </p><p>The <gi tei="yes">div</gi> element has the following formal definition:
 
<dtdFrag id="DDSDIV" n="Un-numbered divisions"><tagDecl tagDoc="DIV"/></dtdFrag>
 </p></div3><div3 id="DSDIV2" name="subsection" ref="Y"><head>Numbered Divisions</head><p>The following elements are used to identify textual subdivisions
in the numbered style:
<tagList style="one-line"><tagDesc tagDoc="DIV0"/><tagDesc tagDoc="DIV1"/><tagDesc tagDoc="DIV2"/><tagDesc tagDoc="DIV3"/><tagDesc tagDoc="DIV4"/><tagDesc tagDoc="DIV5"/><tagDesc tagDoc="DIV6"/><tagDesc tagDoc="DIV7"/></tagList>
 
As members of the class <term>divn</term> these elements all bear the
following additional attribute:
 
<adList classDoc="DIVN" atts="type"/>
 </p><p>The largest possible subdivision of the body may be regarded either
as a <gi tei="yes">div0</gi> or as a <gi tei="yes">div1</gi> element,
<note source="auth" place="foot" anchored="Y">This convention (corresponding with the idea that a
type-set document may begin either with a <q>level 0</q> or a <q>level
1</q> heading) is provided for convenience and compatibility with some
widely used formatting systems.</note>
and the smallest possible <gi tei="yes">div7</gi>.  If numbered divisions are in
use, a division at any one level (say, <gi tei="yes">div3</gi>), may contain only
numbered divisions at the next lowest level (in this case,
<gi tei="yes">div4</gi>).
 </p><p>Using this style, the body of a text containing two parts, each
composed of two chapters, might be represented as follows:
 
<eg rend="skel"><![CDATA[ <body>
 <div0 type='Part' n='1'>
     <div1 type='Chapter' n='1'>
     <!-- text of part 1, chapter 1 -->
     <div1 n='2'>
     <!-- text of part 1, chapter 2-->
 <div0 n='2'>
     <div1 n='1'>
     <!-- text of part 2, chapter 1 -->
     <div1 n='2'>
     <!-- text of part 2, chapter 2 -->
 </body>]]></eg><!-- Changed example:  the point of the div1/div0             --><!-- alternation in the body is to allow the scheme to        --><!-- handle Chapters at a consistent level with or without    --><!-- surrounding Parts, so the natural way to tag Part and    --><!-- Chapter here is div0 div1, not div1 div2, or at least    --><!-- so it seems to me.  -msm                                 --><!-- tough if you then want sections too (LB) --><!-- Also changed to agree with previous example in N values  --><!-- and comments. -msm                                       -->
 </p><p>Formal definitions for these elements are as follows:
<dtdFrag id="DDSDIVN" n="Numbered divisions"><tagDecl tagDoc="DIV0"/><tagDecl tagDoc="DIV1"/><tagDecl tagDoc="DIV2"/><tagDecl tagDoc="DIV3"/><tagDecl tagDoc="DIV4"/><tagDecl tagDoc="DIV5"/><tagDecl tagDoc="DIV6"/><tagDecl tagDoc="DIV7"/></dtdFrag>
 </p></div3><div3 id="DSDIV3" name="subsection" ref="Y"><head>Numbered or Un-numbered?</head><!-- added following para for clarification --><p>Within the same <gi tei="yes">front</gi>, <gi tei="yes">body</gi> or <gi tei="yes">back</gi>
element, all hierarchic subdivisions must be marked either using
nested <gi tei="yes">div</gi> elements, or using the <gi tei="yes">div0</gi>,
<gi tei="yes">div1</gi>, <gi tei="yes">div2</gi> tag appropriate at each level; the two
styles may <emph>not</emph> be mixed.
</p><p>The choice between numbered and un-numbered divisions will depend to
some extent on the complexity of the material:  un-numbered divisions
allow for an arbitrary depth of nesting, while numbered divisions limit
the depth of the tree which can be constructed.  Where divisions at
different levels should be processed differently (chapters, but not
sections, for example, beginning on new pages), numbered divisions
slightly simplify the task of defining the desired processing for each level.
Some software may find numbered divisions easier to process, as there is
no need to maintain knowledge of the whole document structure in order
to know the level at which a division occurs; such software may however
find it difficult to cope with some other aspects of the TEI scheme.<!-- LB added following sentence -->
On the other hand, in a collection of many works it may
prove difficult or impossible to ensure that the same numbered division
always corresponds with the same type of textual feature: a
<q>chapter</q> may be at level 1 in one work and level 3 in another.
 </p><p>Whichever style is used, the global <att tei="yes">n</att> and <att tei="yes">id</att>
attributes (section <xref target="STGA"/>) may be used to provide
reference strings or labels for each division of a text, where
appropriate. Such labels should be provided for each section
which is regarded as significant for referencing purposes (on
reference systems, see further section <xref target="CORS"/>).  
</p><p>As indicated above, the <att tei="yes">type</att> attribute is used to
provide a name or description for the division.  Typical values might
be <q>book</q>, <q>chapter</q>, <q>section</q>, <q>part</q>, or (for
verse texts) <q>book</q>, <q>canto</q>, <q>stanza</q>, or (for
dramatic texts) <q>act</q>, <q>scene</q>.  This attribute has a
declared value of <code lang="sgml" tei="yes" type="frag">#CURRENT</code>, which implies
that if defaulted, the value used will be that most recently specified
on any element of the same kind, scanning the text left to right.
Hence, if un-numbered divisions are used, the appropriate value must
be specified each time a change of level occurs, both <q>down</q> and
<q>up</q> the document hierarchy.
 </p><p>The following extended example uses numbered divisions to indicate
the structure of a novel, and illustrates the use of the attributes
discussed above.  It also uses some elements discussed in section<xref target="DSDTB"/>
 and the <gi tei="yes">p</gi> element discussed in section<xref target="COPA"/>
.
 <!-- a long example but an irresistible one... -->
 
<eg><![CDATA[<div0 type='book' n='I' id=JA0100>
<head>Book I.</head>
  <div1 type='chapter' n='1' id=JA0101>
  <head>Of writing lives in general, and particularly of
        Pamela, with a word by the bye of Colley
        Cibber and others.</head>
  <p>It is a trite but true observation, that examples work
        more forcibly on the mind than precepts:  ...
 
        <!-- remainder of chapter 1 here -->
 
  <div1 n='2' id=JA0102>
  <head>Of Mr. Joseph Andrews, his birth, parentage,
        education, and great endowments; with a word
        or two concerning ancestors.</head>
  <p>Mr. Joseph Andrews, the hero of our ensuing history,
        was esteemed to be the only son of Gaffar and
        Gammar Andrews, and brother to the illustrious
        Pamela, whose virtue is at present so famous ...
 
        <!-- remainder of chapter 2 here -->
        <!-- remaining chapters of Book 1 here -->
 
<trailer>The end of the first Book
<div0 n='II' id=JA0100>
<head>Book II</head>
  <div1 n='1' id=JA0201>
  <head>Of divisions in authors</head>
  <p>There are certain mysteries or secrets in all
        trades, from the highest to the lowest, from
        that of <term>prime-ministering</term>, to
        this of <term>authoring</term>, which are
        seldom discovered unless to members of
        the same calling ...
  <p>I will dismiss this chapter with the following
        observation: that it becomes an author generally to
        divide a book, as it does a butcher to joint his meat,
        for such assistance is of great help to both the reader
        and the carver. And now having indulged myself a little
        I will endeavour to indulge the curiosity of my reader,
        who is no doubt impatient to know what he will find
        in the subsequent chapters of this book.
  <div1 n='2' id=JA0202>
  <head>A surprising instance of Mr. Adams's short memory, with
        the unfortunate consequences which it brought on Joseph.
        </head>
  <p>Mr. Adams and Joseph were now ready to depart different
        ways ...
 ]]></eg><!--   Fielding, Joseph Andrews (ed Battestin, 1961) --><!-- Again, example changed to use div0, div1 not 1, 2. -msm  -->
 </p></div3><div3 id="DSDIV3X" name="subsection" ref="Y"><head>Partial and Composite Divisions</head><p>In most situations, the textual subdivisions marked by <gi tei="yes">div</gi>
elements will be both complete and identically organized with
reference to the original source.  For some purposes however, in
particular where dealing with unusually large or unusually small
texts, encoders may find it convenient to present as textual divisions
sequences of text which are incomplete with reference to the original
text, or which are in fact an ad hoc agglomeration of tiny texts.
Moreover, in some kinds of texts it is difficult or impossible to
determine the order in which individual subdivisions should be
combined to form the next higher level of subdivision, as noted
below.
 </p><p>To overcome these problems, the following additional attributes are
defined for all elements in the <term>divn</term> class:
 
<adList classDoc="DIVN" atts="org sample part"/>
 </p><p>For example, an encoder might choose to transcribe only the first two
thousand words of each chapter from a novel.  In such a case, each
chapter might conveniently be regarded as a partial division, and tagged
with a <gi tei="yes">div</gi> element in the following form:
<eg><![CDATA[ <div n='xx' sample=initial part=Y type=chapter>
 <p><!-- ... -->
 </div>]]></eg>
where <q>xx</q> represents a number for the chapter.  The
<gi tei="yes">sampling</gi> element in the TEI Header should also be used to
record the principles underlying the selection of incomplete samples, as
further described in section <xref target="HD52"/>.
 </p><p>The following example demonstrates how a newspaper column composed of
very short unrelated snippets may be encoded using these attributes:
 
<eg><![CDATA[ 
<div1 type=storylist org=composite>
<head>News in brief</head>
<div2 type=story>
<head>Police deny <soCalled>losing</soCalled> bomb</head>
<p>Scotland Yard yesterday denied claims in the Sunday
Express that anti-terrorist officers trailing an IRA van
loaded with explosives in north London had lost track of
it 10 days ago.
</div2>
<div2 type=story>
<head>Hotel blaze</head>
<p>Nearly 200 guests were evacuated before dawn
yesterday after fire broke out at the Scandic
Crown hotel in the Royal Mile, Edinburgh.
</div2>
<div2 type=story>
<head>Test match split</head>
<p>Test Match Special next summer will be split
between Radio 5 and Radio 3, after protests this
year that it disrupted Radio 3's music schedule.
</div2>
<!-- other stories here -->
</div1>]]></eg> <!-- Guardian 21 Dec 1992, p 2 -->
 </p><p>The <att tei="yes">org</att> attribute on the <gi tei="yes">div1</gi> element is used
here to indicate that individual stories in this group, marked here as
<gi tei="yes">div2</gi>, are really quite independent of each other, although they
are all marked as subdivisions of the whole group.  They can be read in
any order without affecting the sense of the piece; indeed, in some
cases, divisions of this nature are printed in such a way as to make it
impossible to determine the order in which they are intended to be read.
Individual stories can be added or removed without affecting the
existing components.
 </p><p>This method of encoding composite texts as composite divisions has
some limitations compared with the more general and powerful mechanisms
discussed in section <xref target="DSGRP"/>. However, it may be preferable
in some circumstances, notably where the individual texts are very
small.
 </p></div3></div2><div2 id="DSDTB" name="section" ref="Y"><head>Elements Common to All Divisions</head><p>The divisions of any kind of text may sometimes begin with a brief
heading or descriptive title, with or without a byline, an epigraph or
brief quotation, or a salutation such as one finds at the start of a
letter.  They may also conclude with a brief trailer, byline, or
signature. Elements which may appear in this way, either at the start
or at the end of a text division proper, are regarded as forming a
class, known as <term>divtop</term> or <term>divbot</term>
respectively.
 </p><p>The following special-purpose elements are provided to
mark features which may appear only at the start of a division:
 
<tagList style="one-line"><tagDesc tagDoc="HEAD" atts="type"/><tagDesc tagDoc="EPIGRAPH"/><tagDesc tagDoc="ARGUMENT"/><tagDesc tagDoc="OPENER"/></tagList>
 
For further details of the <gi tei="yes">head</gi> element, see section <xref target="DSHD"/>; for <gi tei="yes">epigraph</gi> and <gi tei="yes">argument</gi>, see section<xref target="DSAE"/>
; for <gi tei="yes">opener</gi>, see section <xref target="DSOC"/>.
 </p><p>The following special-purpose elements are provided to mark features
which may appear only at the end of a division:
 
<tagList style="one-line"><tagDesc tagDoc="TRAILER"/><tagDesc tagDoc="CLOSER"/></tagList>
 
For further details of the <gi tei="yes">trailer</gi> element, see section <xref target="DSHD"/>; for the <gi tei="yes">closer</gi> element, section <xref target="DSOC"/>.
 </p><div3 id="DSHD" name="subsection" ref="Y"><head>Headings and Trailers</head><p>The <gi tei="yes">head</gi> element is used to identify a heading prefixed to
the start of any textual division, at any level. A given division may
of course contain more than one such element, as in the following
example:
 
<eg><![CDATA[ 
<div1 n='Etym'>
<head>Etymology</head>
<head>(Supplied by a late consumptive usher to a
grammar school)</head>
<p>The pale Usher &mdash; threadbare in coat, heart,
body and brain; I see him now. He was ever
dusting his old lexicons and grammars....]]></eg><!-- H Melville, M.Dick -->
 </p><p>Unlike some other markup schemes, the TEI scheme does
<emph>not</emph> require that headings attached to textual subdivisions
at different hierarchic levels have different identifiers. All kinds of
heading are marked identically using the <gi tei="yes">head</gi> tag; the type or
level of heading intended is implied by the immediate parent of the
<gi tei="yes">head</gi> element, which may for example be a <gi tei="yes">div1</gi>,
<gi tei="yes">div2</gi>, etc., an un-numbered <gi tei="yes">div</gi>, or a <gi tei="yes">list</gi>.
 </p><p>In certain kinds of text (notably newspapers), there may be a need
to categorize individual headings within the sequence at the start of a
division,  for example as <q>main</q> headings, or <q>detail</q>
headings. Specific elements are provided for certain kinds of
heading-like features, (notably <gi tei="yes">byline</gi>, <gi tei="yes">dateline</gi> and
<gi tei="yes">salute</gi>; see further section <xref target="DSOC"/>),  but the
<att tei="yes">type</att> attribute must be used to discriminate among other
forms of heading.
 </p><p>In the following example, taken from a British newspaper, the lead
story and its associated headlines have been encoded  as a <gi tei="yes">div</gi>
element, with appropriate <term>divtop</term> elements attached:
 
<eg> <![CDATA[
<div type=story>
<head rend='large underlined' type=sub>
President pledges safeguards for 2,400 British
troops in Bosnia</head>
<head rend='very large bold' type=main>
Major agrees to enforced no-fly zone </head>
<byline>By George Jones, Political Editor, in Washington
</byline>
<p>Greater Western intervention in the conflict in
former Yugoslavia was pledged by President Bush yesterday....]]></eg><!-- Daily Telegraph 21 Dec 1992 -->
 </p><p>In older writings, the headings or <term>incipits</term> may be
longer than in modern works.<!-- Heading-like features which appear in the middle of a    --><!-- text should normally be regarded either as < gi > quote  --><!-- < / gi > elements (if they have no connexion with the    --><!-- immediately surrounding text), or as starting new < gi   --><!-- > div < / gi > elements (if they are more closely        --><!-- connected with the text following than with the text     --><!-- preceding).                                              -->
When heading-like material appears in the middle of a text, the encoder
must decide whether or not to treat it as the start of a new division.
If the phrase in question appears to be more closely connected with what
follows than with what precedes it, then it may be regarded as a
heading and tagged as the <gi tei="yes">head</gi> of a new <gi tei="yes">div</gi> element.
If it appears to be simply inserted or superimposed --- as for example
the kind of <soCalled>pull quotes</soCalled> often found in newspapers
or magazines, then the <gi tei="yes">quote</gi>, <gi tei="yes">q</gi>, or <gi tei="yes">cit</gi>
element may be more appropriate.
 </p><p>The <gi tei="yes">trailer</gi> element, which can appear at the end of a
division only, is used to mark any heading-like feature appearing in
this position, as in this example:
 
<eg><![CDATA[ <div1 type=book n='I'><head>In the name of Christ here begins
 the first book of the ecclesiastical history of Georgius
 Florentinus, known as Gregory, Bishop of Tours.</head>
 <div2><head>Chapter-Headings</head>
 <list>
    <!-- list of chapter heads omitted ...  -->
 </list>
 <div2><head>In the name of Christ here begins Book I of the
 history.</head>
 <p>Proposing as I do ...
 <p>From the Passion of our Lord until the death of Saint Martin
 four hundred and twelve years passed.
 <trailer>Here ends the first Book, which covers five thousand,
 five hundred and ninety-six years from the beginning of the
 world down to the death of Saint Martin.</trailer>
 </div2>
 </div1>]]></eg>
 </p></div3><div3 id="DSOC" name="subsection" ref="Y"><head>Openers and Closers</head><p>In addition to headings of various kinds, divisions sometimes include
more or less formulaic opening or closing passages, typically conveying
such information as the name and address of the person to whom the
division is addressed, the place or time of its production, a salutation
or exhortation to the reader, and so on.  Divisions in epistolary form
are particularly liable to include such features.  
Additional elements for the detailed encoding of personal names, dates
and places are provided in chapter <xref target="ND"/>.<!-- To cater for the full --><!-- variety of such features, the elements described in chapter <xref --><!-- target=LM> should also be used, but for many -->
For simple cases, the following elements should be adequate:
 
<tagList style="one-line"><tagDesc tagDoc="BYLINE"/><tagDesc tagDoc="DATELINE"/><tagDesc tagDoc="SALUTE"/><tagDesc tagDoc="SIGNED"/></tagList>
 
 </p><p>The <gi tei="yes">byline</gi> and <gi tei="yes">dateline</gi> elements are used to encode
headings which identify the authorship and provenance of a division.
Although the terminology derives from newspaper usage, there is no
implication that <gi tei="yes">dateline</gi> or <gi tei="yes">byline</gi> elements apply
only to newspaper texts.  The following example illustrates use of the
<gi tei="yes">dateline</gi> and <gi tei="yes">signed</gi> elements at the end of the
preface to a novel:
 
<eg><![CDATA[<div type=preface>
<head>To Henry Hope.</head>
<p>It is not because this volume was conceived and partly
executed amid the glades and galleries of the Deepdene,
that I have inscribed it with your name.... I shall find a
reflex to their efforts in your own generous spirit and
enlightened mind.
</p>
<closer>
<signed lang=el>D.</signed>
<dateline>Grosvenor Gate, May-Day, 1844</dateline>
</closer>
</div>
 ]]></eg><!-- B Disraeli, Coningsby (Nelson, nd) -->
 </p><p>Where a sequence of such elements appear together, either at the
beginning or end of an element, it may be convenient to group them
together using one of the following elements:

<tagList style="one-line"><tagDesc tagDoc="OPENER"/><tagDesc tagDoc="CLOSER"/></tagList>

The following examples demonstrate the use of the <gi tei="yes">opener</gi> and
<gi tei="yes">closer</gi> grouping elements:
 
<eg><![CDATA[<div type=narrative n='6'>
<head>Sixth Narrative</head>
<head>contributed by Sergeant Cuff</head>
<div type=fragment n='6.1'>
<opener>
  <dateline><name type=place>Dorking, Surrey,</name>
            <date>July 30th, 1849</date>
  </dateline>
  <salute>To <name>Franklin Blake, Esq.</name> Sir, &mdash;
  </salute>
</opener>
<p>I beg to apologize for the delay that has occurred
in the production of the Report, with which I engaged
to furnish you. I have waited to make it a complete
Report ...
<!-- .... -->
<closer>
  <salute>I have the honour to remain, dear sir, your
    obedient servant </salute>
  <signed> <name>RICHARD CUFF</name> (late sergeant in the
     Detective Force, Scotland Yard, London).
  </signed>
</closer>
</div>]]></eg><!-- W. Collins, The Moonstone, Penguin, pp 503, 513 -->
 
 
<eg><![CDATA[<div type=letter n='14'>
<head>Letter XIV: Miss Clarissa Harlowe to Miss Howe</head>
<opener>
   <dateline>Thursday evening, March 2.</dateline>
</opener>
<p>On Hannah's depositing my long letter ...
<p>An interruption obliges me to conclude myself 
in some hurry, as well as fright, what I must ever be,
<closer>
<salute>Yours more than my own,</salute>
<signed>Clarissa Harlowe</signed>
</closer>
</div>]]></eg><!-- S. Richardson 'Clarissa', (Dent, EML, vol 1, p62,64 -->
 </p><p>For further discussion of the encoding of names of persons and places
and of dates, see section <xref target="CONADA"/> and chapter <xref target="ND"/>.
 </p></div3><div3 id="DSAE" name="subsection" ref="Y"><head>Arguments and Epigraphs</head><!-- may have a head --><p>The <gi tei="yes">argument</gi> element may be used to encode the prefatory
list of topics sometimes found at the start of a chapter or
other division.  It is most conveniently encoded as a list, since this
allows each item to be distinguished, but may also simply be presented
as a paragraph.  The following are thus both equally valid ways of
encoding the same argument:
 
<eg><![CDATA[<div type=chap n='6'>
<argument>
<p>Kingston &mdash; Instructive remarks on early English
history &mdash; Instructive observations on carved oak
and life in general &mdash; Sad case of Stivvings,
junior &mdash; Musings on antiquity &mdash; I forget
that I am steering &mdash; Interesting result &mdash;
Hampton Court Maze &mdash; Harris as a guide.
</argument>
<p> It was a glorious morning, late spring or early summer,
as you care to take it...
</div>]]></eg><!-- Jerome, J.K. : Three men in a boat, ch 6 -->
<eg><![CDATA[<div type=chap n='6'>
<argument>
<list type='inline'>
<item>Kingston
<item>Instructive remarks on early English history
<item>Instructive observations on carved oak and life in general
<item>Sad case of Stivvings, junior
<item>Musings on antiquity
<item>I forget that I am steering
<item>Interesting result
<item>Hampton Court Maze
<item>Harris as a guide.
</list>
</argument>
<p> It was a glorious morning, late spring or early summer,
as you care to take it...
</div>]]></eg><!-- Jerome, J.K. : Three men in a boat, ch 6 -->
 </p><p>An <term>epigraph</term> is a quotation from some other work
appearing on a title page, or at the start of a division.  It may be
encoded using the special-purpose <gi tei="yes">epigraph</gi> element.  Its
content will generally be a <gi tei="yes">q</gi> or <gi tei="yes">quote</gi> element,
often associated with a bibliographic reference, as in the
following example:
 
<eg><![CDATA[<div n='19'><head>Chapter 19</head>
 <epigraph>
 <cit><quote>I pity the man who can travel
     from Dan to Beersheba, and say <q>'Tis all
     barren;</q> and so is all the world to him
     who will not cultivate the fruits it offers.
     </quote>
     <bibl>Sterne: Sentimental Journey.</bibl>
 </cit></epigraph>
 <p>To say that Deronda was romantic would be to
 misrepresent him: but under his calm and somewhat
 self-repressed exterior ...]]></eg><!-- G. Eliot, D. Deronda, (1876) III.1 (Penguin, 1967, p. 245)  -->
 </p><p>For discussion of quotations appearing other than as epigraphs refer
to section <xref target="COHQQ"/>.
 
 </p></div3><div3 id="DSCO" name="subsection" ref="Y"><head>Content of Textual Divisions</head><p>Other than its initial sequence of <term>divtop</term> elements,
and its closing sequence of <term>divbot</term> elements, every
textual division (numbered or un-numbered) consists of a sequence of<!-- ungrouped lower-level structural elements, that is, a sequence of -->
 
ungrouped <term>component</term> elements (see <xref target="STEC"/>).  The actual elements available will depend on the base
tag set in use; in all cases, at least the component-level structural
elements defined in the core will be available (paragraphs, lists,
dramatic speeches, verse lines and line groups etc.).  If the drama
base has been selected, then additionally the low level dramatic
structural elements (speeches or stage directions, as defined in
chapter <xref target="DR"/>) will be available.  If the dictionary base
is in use, then dictionary entries, related entries, etc. (as defined
in chapter <xref target="DI"/>) will also be available; if the tag set
for transcribed speech is in use, then utterances, pauses, vocals,
kinesics, etc., as defined in chapter <xref target="TSBA"/> will be
available; and so on.
 </p><p>Where a text contains low level elements from more than one base, two
options are available.  The first option, selected by the
<soCalled>mixed</soCalled> base, allows for low level structural
elements from any or all of the selected bases to appear at any point.
The second option, selected by the <soCalled>general</soCalled> base,
allows for low level structural elements from different bases to appear
in different textual divisions of the same text, but requires that any
one division use elements from only one base.  For further information,
refer to section <xref target="STCO"/>.
 </p><p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id="DDSDIVX" n="Tags for start and end of divisions"><tagDecl tagDoc="TRAILER"/><tagDecl tagDoc="BYLINE"/><tagDecl tagDoc="DATELINE"/><tagDecl tagDoc="ARGUMENT"/><tagDecl tagDoc="EPIGRAPH"/><tagDecl tagDoc="OPENER"/><tagDecl tagDoc="CLOSER"/><tagDecl tagDoc="SALUTE"/><tagDecl tagDoc="SIGNED"/><commDecl>The HEAD element is declared in the core tag set.</commDecl></dtdFrag>
 
 <?tei:EOF p2ds1.odd ??><?tei:SOF p2ds2.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    **
    * $Log: p2ds2.odd,v $
    * Revision 1.6  1998/01/31 19:24:34  tei
    * tidying examples
    *
    * Revision 1.5  98/01/28  11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    * 
    *--><!-- Revisions:                                               --><!-- 12 jan 98 : LB : fixing egs --><!-- 1993-03-26 : LB, MSM : last-minute corrections, revs     --><!-- 1993-03-25 : MSM : revision for publication              -->
 </p></div3></div2><div2 id="DSGRP" name="section" ref="Y"><head>Groups of Texts</head><p>The <gi tei="yes">group</gi> element should be used to represent a collection
of independent texts which is to be regarded as a single unit for
processing or other purposes.  Examples of such composite texts include
anthologies and other collections. The presence of common front matter
referring to the whole collection, possibly in addition to front matter
relating to each individual text, is a good indication that a given text
might usefully be encoded as a <gi tei="yes">group</gi>, though encoders may
choose to use this structure to represent other kinds of composite
texts as well.
 
<tagList style="one-line"><tagDesc tagDoc="GROUP"/></tagList>
 </p><p>For example, the overall structure of a collection of
short stories might be encoded as follows:
 
<eg><![CDATA[ <tei.2>
 <teiHeader>
    <!-- header information for the whole collection -->
 </teiHeader>
 <text>
    <front>
       <docTitle><titlePart>
          The Adventures of Sherlock Holmes
       </titlePart></docTitle>
       <docImprint>First published in <title>The Strand</title>
       between July 1891 and December 1892</docImprint>
       <!-- Any other front matter specific
            to the collection here ... -->
    </front>
    <group>
       <text>
          <front>
             <head rend=italic>Adventures of Sherlock
                   Holmes</head>
             <docTitle><titlePart>Adventure I. &mdash;</titlePart>
                   <titlePart>A Scandal in Bohemia</titlePart></docTitle>
             <byline>By A. Conan Doyle.</byline>
          </front>
          <body>
             <div1 n='I.1'>
             <p>To Sherlock Holmes she is always
             <emph>the</emph> woman.
             <!-- ... -->
          </body>
       </text>
       <text>
          <front>
             <head rend=italic>Adventures
                   of Sherlock Holmes</head>
             <docTitle><titlePart>Adventure II. &mdash;</titlePart>
                   <titlePart>The Red-Headed League</titlePart></docTitle>
             <byline>By A. Conan Doyle.</byline>
          </front>
          <body>
            <p> <!-- text of The Red-Headed League here -->
          </body>
       </text>
 
       <!-- more texts here -->
 
       <text>
          <front>
             <head rend=italic>
                 Adventures of Sherlock Holmes</head>
             <docTitle><titlePart>Adventure XII. &mdash;</titlePart>
                 <titlePart>The Adventure of the Copper Beeches</titlePart>
             </docTitle>
             <byline>By A. Conan Doyle.</byline>
          </front>
          <body>
             <p><q>&odq;To the man who loves art for
             its own sake,&cdq;</q> remarked Sherlock
             Holmes ...
             <!-- rest of the the Copper Beeches here -->
             ... she is now the head of a private school
             at Walsall, where I believe that she has
             met with considerable success.</p>
          </body>
       </text> <!-- end of the Copper Beeches -->
    </group>
 </text>  <!-- end of the Adventures of Sherlock Holmes -->
 </tei.2>]]></eg><!-- Original Illustrated Sherlock Holmes (Castle Books, 1989) -->
 </p><p>A text which is a member of a group may itself contain groups.  This
is quite common in collections of verse, but may happen in any kind of
text.  As an example, consider the overall structure of a typical
collection, such as the <title>Muses Library</title> edition of
Crashaw's poetry (ed. J.R. Tutin, [ca. 1900]).  Following a critical
introduction and table of contents, this work contains the following
major sections:
 
<list type="simple"><item><title>Steps to the Temple</title> (a collection of
verse first published in 1648)</item><item><title>Carmen deo Nostro</title> (a second collection,
published in 1652)</item><item><title>The Delights of the Muses</title> (a third
collection, published in 1648)</item><item><title>Posthumous Poems,</title> I (a collection of
fragments all taken from a single manuscript)</item><item><title>Posthumous Poems,</title> II (a further collection
of fragments, taken from a different manuscript)</item></list>
 </p><p>Each of the three collections published in Crashaw's lifetime has a
reasonable claim to be considered as a text in its own right, and may
therefore be encoded as such.  It is rather more arbitrary as to whether
the two posthumous collections should be treated as two groups,
following the practice of the Muses Library edition.  An encoder might
elect to combine the two into a single group, or simply to treat each
fragment as an ungrouped unitary text.
 </p><p>The Muses Library edition reprints the whole of each of the three
original collections, including their original front matter (title
pages, dedications etc.).  These should be encoded using the
<gi tei="yes">front</gi> element and its constituents (on which see further
section <xref target="DSFRONT"/>), while the body of each collection should
be encoded as a single <gi tei="yes">group</gi> element.  Each individual poem
within the collections should be encoded as a distinct <gi tei="yes">text</gi>
element.  The beginning of the whole collection would thus appear as
follows (for further discussion of the use of the elements <gi tei="yes">div</gi>
and <gi tei="yes">lg</gi> for textual subdivision of verse, see section<xref target="COVE"/>
 and chapter <xref target="VE"/>):
 
<eg><![CDATA[ 
<text>
  <front>
    <titlePage>
      <docTitle><titlePart>The poems of Richard Crashaw</titlePart></docTitle>
      <byline>Edited by J.R. Tutin</byline>
      <!-- ... -->
    </titlePage>
    <div type=preface><head>Editor's Note</head>
      <p>A few words are necessary...
      <!-- ... -->
    </div>
  </front>
  <group>
  <text>
    <front>
      <titlePage>
        <docTitle>
          <titlePart>Steps to the Temple, Sacred Poems</titlePart>
        </docTitle>
        <!-- ... -->
      </titlePage>
      <div type=address><head>The Preface to the Reader
        <p>Learned Reader, The Author's friend will not usurp
        much upon thy eye...
      </div>
    </front>
    <group>
      <text>
        <front><docTitle><titlePart>Sospetto D'Herode</titlePart></docTitle>
        </front>
        <body>
          <div1 type=book n='Herod I'>
          <head>Libro Primo</head>
          <epigraph>
            <l>Casting the times with their strong signs
            <!-- ... -->
          </epigraph>
          <lg n='I.1' type=stanza>
          <l>Muse! now the servant of soft loves no more
          <l>Hate is thy theme and Herod whose unblest
          <l>Hand (O, what dares not jealous greatness?) tore
          <l>A thousand sweet babes from their mothers' breast,
          <l>The blooms of martyrdom...
          <!-- ... -->
      </text> <!-- end of  Sospetto D'Herode -->
      <text>
        <front><docTitle><titlePart>The Tear</titlePart></docTitle></front>
        <body>
          <lg n='I'>
          <l>What bright soft thing is this
          <l>Sweet Mary, thy fair eyes' expense?
          <!-- ... -->
      </text>  <!-- end of The Tear -->

   <!-- the remaining poems of the Steps to the Temple appear -->
    <!-- here, each within its own <text>  element -->   

    </group>  
    <back> <!-- back matter for Steps to the Temple here -->
    </back>
  </text>
  <text> <!-- Carmen deo Nostro -->
    <front> <!-- ... --> </front>
    <group>
      <text><!-- ... --> </text>
      <text><!-- ... --> </text>
      <!-- more texts here -->
    </group>
  </text>
  <text> <!-- The delights of the Muses -->
    <group>
      <text><!-- ... -->  </text>
      <text><!-- ... -->  </text>
      <!-- more texts here -->
     </group>
  </text>
   <!-- ... -->
  </group>
  <back>
    <!-- back matter for the whole collection -->
  </back>
</text>]]></eg>
 </p><p>The <gi tei="yes">group</gi> element may be used in this way to encode any kind
of collection of which the constituents are regarded by the encoder as
texts in their own right.  Examples include anthologies of verse or
prose by multiple authors, collections, florilegia or commonplace books,
journals, day books, etc.  As a fairly typical example, we consider
<title>The Norton Book of Travel</title>, an anthology edited by Paul
Fussell and published in 1987 by W.W. Norton.  This work comprises
the following major sections:
 
<list type="ordered"><item>Front matter (title page, acknowledgments, introductory essay)</item><item>The Beginnings</item><item>The Eighteenth Century and the Grand Tour</item><item>The Heyday</item><item>Touristic Tendencies</item><item>Post Tourism</item><item>Back matter (permissions list, index)</item></list>
 
Each titled section listed above comprises a group of extracts or
complete texts from writers of a given historical period, preceded by an
introductory essay.  For example, the second group listed above
contains, inter alia, the following:
 
<list type="ordered"><item>Prefatory essay</item><item>Five letters by Lady Mary Wortley Montagu</item><item>An extract from Swift's Gullivers Travels</item><item>Two poems by Alexander Pope</item><item>Two extracts from Boswell's Journal</item><item>A poem by William Blake</item></list>
 
Each group of writings by a single author is preceded by a brief
biographical notice.  Some of the extracts are quite lengthy, containing
several chapters or other divisions; others are quite short.  As the
above list indicates, the texts included range across all kinds of
material:  verse, prose, journals and letters.
 </p><p>The easiest way of encoding such an anthology is to treat each
individual extract as a text in its own right.  A sequence of texts by a
single author, together with the biographical note preceding it, can
then be treated as a single <gi tei="yes">group</gi> element within the larger
<gi tei="yes">group</gi> formed by the section.  The sequence of single or
composite texts making up a single section of the work is likewise
treated, together with its prefatory essay, as a single <gi tei="yes">group</gi>
within the work.  Schematically:
 
<eg rend="skel"><![CDATA[<text> <!-- the whole anthology -->
  <front>
      <!-- title page, acknowledgments, introductory
           essay for anthology -->
  </front>
  <group> <!-- 'body' of the anthology -->
    <group><head>The Beginnings</head>
          <!-- sequence of texts or groups -->
    </group>
    <group> <!-- The Eighteenth Century and the Grand Tour -->
       <text> <!-- prefatory essay by editor -->  </text>
       <group><!-- Lady Mary Wortley Montagu -->
          <text> <!-- biographical notice, by
                      editor --> </text>
          <text> <!-- first letter  --> </text>
          <text> <!-- second letter --> </text>
           <!-- ... -->
       </group>  <!-- end of Montagu section -->
       <text>    <!-- single text by Jonathan Swift -->
             <front> <!-- biographical notice,
                          by editor --> </front>
             <body> <!-- ... --> </body>
       </text>  <!-- end of Swift section -->
       <group>  <!-- Alexander Pope -->
          <text> <!-- biographical notice, by
                      editor --> </text>
          <text> <!-- first poem  --> </text>
          <text> <!-- second poem --> </text>
       </group> <!-- end of Pope section -->
       <!-- ... -->
    </group> <!-- end of 18th Century Section -->
    <group><head>The Heyday</head>
        <!-- texts and subgroups ... -->
    </group>
    <!-- ... -->
  </group> <!-- end of 'body' of anthology -->
  <back> <!-- back matter for whole anthology  -->
  </back>
</text>  <!-- end of the anthology -->]]></eg>
 </p><p>Note that the editor's introductory essays on each author may be
treated as texts in their own right, (as the essays on Lady Mary
Wortley Montagu and Alexander Pope have been treated above), or as
front matter to the embedded text, as the essay on Swift has been.
The treatment in the example is intentionally inconsistent, to allow
comparison of the two approaches.  Consistency can be imposed either
by treating the Swift section as a <gi tei="yes">group</gi> containing one text
by Swift and one by the editor, or by treating the Montagu and Pope
sections as <gi tei="yes">text</gi> elements containing the editor's essays as
front matter.  Marked in the second way, the Pope section of the book
would look like this:
 
<eg rend="skel"><![CDATA[    <text><!-- Alexander Pope -->
        <front>
             <!-- biographical notice -->
        </front>
        <group>
             <text>  <!-- first poem  --> </text>
             <text>  <!-- second poem --> </text>
             <!-- ... -->
        </group>
    </text> <!-- end of Pope section -->]]></eg>
 </p><p>The essays on <q>The Eighteenth Century and the Grand Tour</q> and
other larger sections could also be tagged as <soCalled>front</soCalled>
matter in the same way, by treating the larger sections as <gi tei="yes">text</gi>
elements rather than <gi tei="yes">group</gi> elements.
 </p><p>Where, as in this case, an anthology contains different kinds of
text (for example, mixtures of prose and drama, or transcribed speech
and dictionary entries, or letters and verse), the elements to be
encoded may well need to be drawn from more than one of the base tag
sets described in part II.  In such a situation, either the mixed or
the general base should be specified, as further described in section<xref target="STCO"/>
.  The elements provided by the core tag set
described in chapter <xref target="CO"/> should however prove adequate
for most simple purposes, where prose, drama, and verse are combined
in a single collection.
 </p><p>For anthologies of short extracts such as commonplace books, it may
often be preferable to regard each extract not as a text in its own
right but simply as a quotation or <gi tei="yes">cit</gi> element.  The following
component-level elements may be used to encode quotations of this kind:
 
<tagList style="one-line"><tagDesc tagDoc="CIT"/><tagDesc tagDoc="QUOTE"/></tagList>
 
For example, the chapter of <soCalled>extracts</soCalled> which appears
in the front matter of Melville's <title>Moby Dick</title> might be
encoded as follows:
 
<eg><![CDATA[<div type=chap n='2'>
<head>Extracts</head>
<head>(Supplied by a sub-sub-Librarian)</head>
 
<p>It will be seen that this mere painstaking burrower and
grubworm of a poor devil of a Sub-Sub appears to have gone
through the long Vaticans and street-stalls of the earth,
picking up whatever random allusions to whales he could
anyways find...
Here ye strike but splintered hearts together &dash; there,
ye shall strike unsplinterable glasses!</p>
<p><cit>
  <quote>And God created great whales.</quote>
  <bibl>Genesis</bibl>
</cit>
<cit><quote><l>
Leviathan maketh a path to shine after him;
</l><l>
One would think the deep to be hoary.
</l></quote>
<bibl>Job</bibl></cit>
  <!-- ... -->
<cit>
  <quote>By art is created that great Leviathan,
  called a Commonwealth or State &dash (in Latin,
  <mentioned lang=LAT>civitas</mentioned>), which
  is but an artificial man.
  </quote>
  <bibl>Opening sentence of Hobbes's Leviathan</bibl>
</cit>]]></eg>
For more information on the use of the <gi tei="yes">quote</gi> and <gi tei="yes">bibl</gi>
elements, see sections <xref target="COHQQ"/> and <xref target="COBI"/>
respectively.
 </p><p>Where one or more whole texts are embedded within other texts,
without necessarily forming a composite, the encoder may also choose to
represent the nested structure directly.  The <gi tei="yes">text</gi> element is
itself a <term>component</term>  element, and thus can appear
within any division level element in the same way as a paragraph.  For
example, texts such as the <title>Decameron</title> or the
<title>Arabian Nights</title> might be regarded as sequences of discrete
texts embedded within another single text, the framing narrative, rather
than as groups of discrete texts in which the fragments of framing
narrative are regarded as front matter.
 <!-- more detail needed here? -->
 

<?tei:EOF p2ds2.odd ??><?tei:SOF p2ds3.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ds3.odd,v $
    * Revision 1.9  1998/01/31 19:26:04  tei
    * examples fixed
    *
    * Revision 1.7  98/01/31  18:32:23  tei
    * added discussion of FMCHUNK class
    * 
    *
    *--><!-- Revisions:                                               --><!-- 3 jan 94: LB: kill ornament --><!-- 30 dec 93: LB : fix up examples                          --><!-- 93-08-18 : MSM : suppress BYLINE definition              --><!-- 93-08-18 : MSM : add entdecls for front, back            --><!-- 1993-03-26 : LB, MSM : last-minute typos etc.            --><!-- 1993-03-25 : MSM : light revision for publ               -->
 </p></div2><div2 id="DSFRONT" name="section" ref="Y"><head>Front Matter</head><p>By <term>front matter</term> we mean distinct sections of a text
(usually, but not exclusively, a printed one), prefixed to it by way of
introduction or identification as a part of its production. Features
such as title pages or prefaces are clear examples; a less definite
case might be the prologue attached to a play.  The front matter of an
encoded text should not be confused with the TEI header described in
chapter <xref target="HD"/>, which serves as a kind of front matter for
the computer file itself, not the text it encodes.
 </p><p>An encoder may choose simply to ignore the front matter in a text,
if the original presentation of the work is of no interest, or for
other reasons; alternatively some or all components of the front matter
may be thought worth including with the text as components of the
<gi tei="yes">front</gi> element. <note source="auth" place="display" anchored="Y">This decision should be recorded in the
<gi tei="yes">sampling</gi> element of the header.</note>  With the exception of
the title page, (on which see section <xref target="DSTITL"/>), front
matter should be encoded using the same elements as the rest of a text.
As with the divisions of the text body, no other specific tags are
proposed here for the various kinds of subdivision which may appear
within front matter:  instead either numbered or un-numbered
<gi tei="yes">div</gi> elements may be used.  The following suggested values
<note source="auth" place="foot" anchored="Y">As with all lists of <soCalled>suggested
values</soCalled> for attributes, it is recommended that software
written to handle TEI-conformant texts be prepared to recognize and
handle these values when they occur, without limiting the user to the
values in this list.</note>
for the <att tei="yes">type</att> attribute may be used to distinguish various
kinds of division characteristic of front matter:
 
<list type="gloss"><label><term>preface</term></label><item>A foreword or preface addressed to
    the reader in which the author or publisher explains the
    content, purpose or origin of the text.</item><label><term>ack</term></label><item>A formal declaration of
    acknowledgment by the author in which persons and institutions
    are thanked for their part in the creation of a text.</item><label><term>dedication</term></label><item>A formal offering or dedication of
    a text to one or more persons or institutions by the author.</item><label><term>abstract</term></label><item>A summary of the content of a text as
    continuous prose.</item><label><term>contents</term></label><item>A table of contents, specifying the
    structure of a work and listing its constituents.
    The <gi tei="yes">list</gi>
    element should be used to mark its structure.</item><label><term>frontispiece</term></label><item>A pictorial frontispiece,
    possibly including some text.</item></list>
 </p><p>The following extended example demonstrates how various parts of the
front matter of a text may be encoded.  The front part begins with a
title page, which is presented in section <xref target="DSTITL"/> below.
This is followed by a dedication and a preface, each of which is encoded
as a distinct <gi tei="yes">div</gi>:
 
<eg><![CDATA[ 
  <div type='dedication'>
  <p>To my parents, Ida and Max Fish
  </div>
 
  <div type='preface'>
  <head>Preface</head>
  <p>The answer this book gives to its title question is
  <q>there is and there isn't</q>.
    <!-- ... -->
  <p>Chapters 1-12 have been previously published in the
  following journals and collections:
  <list>
  <item>chapters 1 and 3 in <title>New literary
  History</title></item>
  <!--  ... -->
  <item>chapter 10 in <title>Boundary II</title> (1980)</item>
  </list>. I am grateful for permission to reprint.
  <signed>S.F.</signed>
  </div>]]></eg>
 </p><p>The front matter concludes with another <gi tei="yes">div</gi> element, shown
in the next example, this time containing a table of contents, which
contains a <gi tei="yes">list</gi> element (as described in section <xref target="COLI"/>).  Note the use of the <gi tei="yes">ptr</gi> element to provide
page-references:  the implication here is that the target identifiers
supplied (P1, P68 etc.) may correspond with identifiers used either for
<gi tei="yes">div</gi> elements representing chapters of the text, or for
<gi tei="yes">pb</gi> elements marking page divisions of the text.  (For the
<gi tei="yes">ptr</gi> element, see <xref target="COXR"/>.)  Alternatively,
the literal page numbers present in the source text might be
transcribed, but they are likely to be of little direct use in work with
the electronic text.
 
<eg><![CDATA[  <div type='contents'>
  <head>Contents</head>
  <list>
  <item>Introduction, or How I stopped Worrying and Learned
    to Love Interpretation <ptr target=P1>
  </item>
  <item><list><head>Part One: Literature in the Reader</head>
    <item n='1'>Literature in the Reader: Affective
    Stylistics <ptr target=P21>
    <item n='2'>What is Stylistics and Why Are They
    Saying Such Terrible Things About It? <ptr target=P68>
    <!-- ... -->
  </list></list>
  </div>]]></eg>
 </p><p>The following example uses numbered divisions to mark up the front
matter of a medieval text.  (Entity references are used to represent the
characters thorn, yogh, and ampersand, as discussed in section <xref target="CHLON"/>.)  Note that in this case no title page in the modern
sense occurs; the title is simply given as a heading at the start of the
front matter.  Note also the use of the <att tei="yes">type</att> attribute on the
<gi tei="yes">div</gi> elements to indicate document elements comparatively
unusual in modern books such as the initial prayer:
 
 <eg><![CDATA[  <front>
  <div1 type=incipit>
  <p>Here bygynni&th; a book of contemplacyon, &th;e whiche 
  is clepyd  <title>&Th;E CLOWDE OF VNKNOWYNG</title>,
  in &th;e whiche a soule is onyd wi&th; GOD.
  <div1 type='prayer'>
  <head>Here biginne&th; &th;e preyer on &th;e prologe.</head>
  <p>God, unto whom alle hertes ben open, &amp; unto
  whome alle wille speki&th;, &amp; unto whom no priue
  &th;ing is hid: I beseche &th;ee so for to clense &th;e
  entent of myn hert wi&th; &th;e unspekable &yog;ift of
  &th;i grace, &th;at I may parfiteliche loue &th;ee
  &amp; wor&th;ilich  preise &th;ee. Amen.
 
  <div1 type='preface'>
  <head>Here biginne&th; &th;e prolog.</head>
  <p>In &th;e name of &th;e Fader &amp; of &th;e Sone &amp;
  of &th;e Holy Goost.
  <p>I charge &th;ee &amp; I beseeche &th;ee, wi&th; as moche
  power &amp; vertewe as &th;e bonde of charite is sufficient
  to suffre, what-so-euer &th;ou be &th;at &th;is book schalt
  haue in possession ...
 
  <div1 type='contents'>
  <head>Here biginne&th; a table of &th;e chapitres.</head>
  <list>
  <label>&th;e first chapitre </label>
     <item>Of foure degrees of Cristen mens leuing;
      &amp; of &th;e cours of his cleping &th;at &th;is
      book was maad vnto.</item>
  <label>&th;e secound chapitre</label>
     <item>A schort stering to meeknes &amp; to &th;e
       werk of &th;this book</item>
      <!--  ... -->
  <label>&th;e fiue and seuenti chapitre</label>
     <item>Of somme certein tokenes bi &th;e whiche
       a man may proue whe&th;er he be clepid of God
       to worche in &th;is werk.</item>
  </list>
  <trailer>&amp here eende&th; &th;e table of &th;e chapitres.
  </trailer>
  </front>]]></eg><!-- Cloud of Unknowing, ed Phyllis Hodgson, EETS, 1944 -->
 </p></div2><div2 id="DSTITL" name="section" ref="Y"><head>Title Pages</head><p>Detailed analysis of the title page and other
<term>preliminaries</term> of older printed books and manuscripts is of
major importance in descriptive bibliography and the cataloguing of
printed books; such analysis may require a rather more detailed tag set
than that proposed here. <note source="auth" place="display" anchored="Y">Definition of such a tag set remains
a work item for the TEI; such tag sets for contemporary printed matter
already exist or are being created within the publishing industry, for
example the Majour (Modular Application for Journals) Project of the
European Workgroup on SGML.  See for example <citation><title>MAJOUR:
Modular Application for Journals:  DTD for Article Headers</title>
([n.p.]:  EWS, 1991).</citation></note> The following elements are
therefore proposed as an interim measure; they constitute a useful
descriptive tag set for the major features of most title pages:
 
<tagList style="one-line"><tagDesc tagDoc="TITLEPA"/><tagDesc tagDoc="DOCTITLE"/><tagDesc tagDoc="TITLEPT" atts="type"/><tagDesc tagDoc="ARGUMENT"/><tagDesc tagDoc="BYLINE"/><tagDesc tagDoc="DOCAUTH"/><tagDesc tagDoc="EPIGRAPH"/><tagDesc tagDoc="IMPRIMAT"/><tagDesc tagDoc="DOCEDITN"/><tagDesc tagDoc="DOCIMPRT"/><tagDesc tagDoc="DOCDATE"/></tagList>
 </p><p>Together with the <gi tei="yes">figure</gi> element described in chapter<xref target="FT"/>
, these elements constitute the element class
<ident tei="yes" type="unknown">tpParts</ident>, which is defined by the parameter entity
<ident tei="yes" type="unknown">m.tpParts</ident>. Any number of elements from this class can
appear grouped together within a <gi tei="yes">titlePage</gi> element. (The
<gi tei="yes">figure</gi> element is included so as to enable encoders to
record the presence of printers' ornaments or other illustrative
material found within a title page; its use implies that the TEI
tagset for figures and tables has been selected, as discussed in
chapter <xref target="FT"/>).
</p><p>The elements listed above, together with the <gi tei="yes">head</gi> element,
also constitute the element class <ident tei="yes" type="unknown">fmchunk</ident>, which is
defined by the parameter entity <ident tei="yes" type="unknown">m.fmchunk</ident>. The elements
in this class can appear within a <soCalled>minimal</soCalled>
<gi tei="yes">front</gi> element without any need to group them together and
encode a complete title page.
</p><p>Encoders wishing to add new elements to either class may do so by
modifying or redefining this parameter entity, as further described in
chapter <xref target="MD"/>.  Two examples of the use of these elements
follow.  First, the title page of the work discussed earlier in this
section:
 
<eg><![CDATA[  <front>
  <titlePage>
  <docTitle>
  <titlePart type=main>Is There a Text in This Class?</>
  <titlePart type=sub>The Authority of Interpretive Communities</>
  </docTitle>
  <docAuthor>Stanley Fish</>
  <docImprint><publisher>Harvard University Press</>
    <pubPlace>Cambridge, Massachusetts</>
    <pubPlace>London, England</>
  </docImprint>
  </titlePage>]]></eg>
 </p><p>Second, a characteristically verbose 17th century example:
<eg><![CDATA[<titlePage>
<docTitle>
 <titlePart type=main>  THE
  Pilgrim's Progress
  FROM
  THIS WORLD,
  TO
  That which is to come:</>
<titlePart type=sub>
  Delivered under the Similitude of a
  DREAM</>
<titlePart type=desc>  Wherein is Discovered,
  The manner of his setting out,
  His Dangerous Journey; And safe
  Arrival at the Desired Countrey.</>
</docTitle>
<epigraph>
  <cit><q>I have used Similitudes,</q><bibl>Hos. 12.10</bibl></cit>
</epigraph>
<byline>
  By <docAuthor>John Bunyan</>.</byline>
<imprimatur>Licensed and Entred according to Order.</>
<docImprint>
  <pubPlace>LONDON,</>
  Printed for <name>Nath. Ponder</>
  at the <name>Peacock</> in the <name>Poultrey</>
  near <name>Cornhil</>, <docDate>1678</>.
</docImprint>]]></eg>
 </p><p>Those elements in the above list which are not defined elsewhere have
the following formal declarations:
 
<dtdFrag id="DDSTPAGE" n="Tags for title pages"><tagDecl tagDoc="TITLEPA"/><tagDecl tagDoc="DOCTITLE"/><tagDecl tagDoc="TITLEPT"/><tagDecl tagDoc="DOCAUTH"/><tagDecl tagDoc="IMPRIMAT"/><tagDecl tagDoc="DOCEDITN"/><tagDecl tagDoc="DOCIMPRT"/><tagDecl tagDoc="DOCDATE"/></dtdFrag>
 <!-- ornament and imprimat ought to go somewhere else, as     --><!-- they can occur outside the title page.  --><!-- Not sure that I agree about imprimat. It can't appear within --><!-- a div. It constitutes a kind of title page. So I propose to --><!-- leave it here. (LB)-->
<!-- ornament can      --><!-- occur anywhere and ought to be defined in PH or          --><!-- somewhere. left to fix later.  -msm                      -->
 <!-- I agree;    (LB)                -->
 </p><p>Where title pages are encoded, their physical rendition is
often of considerable importance.  One approach to this requirement
would be to use the <gi tei="yes">seg</gi> tag, described in chapter <xref target="SA"/>, to segment the typographic content of each part of the
title page, and then use the global <att tei="yes">rend</att> attribute to specify
its rendition.  Another would be to use a tag set specialized for the
description of typographic entities such as pages, lines, rules, etc.,
bearing special-purpose attributes to describe line height, leading,
degree of kerning, font, etc. Further discussion of these problems is
provided in chapter <xref target="PH"/>.

 </p><p>Front matter elements are defined in a distinct DTD file
called <term>TEIfron2.dtd</term>.
 
<dtdFrag id="DDSFRONT" n="Additional Tag Set for Front Matter" file="teifron2"><tagDecl tagDoc="FRONT"/><claDecl classDoc="TPPARTS" type="model"/><dtdRef dtdFrag="DDSTPAGE"/></dtdFrag>
 </p></div2><div2 id="DSBACK" name="section" ref="Y"><head>Back Matter</head><p>Conventions vary as to which elements are grouped as back matter and
which as front.  For example, some books place the table of contents at
the front, and others at the back.  Even title pages may appear at the
back of a book as well as at the front.  The content model for
<gi tei="yes">back</gi> and <gi tei="yes">front</gi> elements are therefore identical.
 </p><p>The following suggested values may be used for the <att tei="yes">type</att>
attribute on all division elements, in order to distinguish various
kinds of division characteristic of back matter:
<list type="gloss"><label><term>appendix</term></label><item>An ancillary self-contained section of
a work, often providing additional but in some sense extra-canonical
text.</item><label><term>glossary</term></label><item>A list of terms associated with definition texts
(<q>glosses</q>): this should be encoded as a <gi tei="yes">list type=gloss</gi>
(see section <xref target="COLI"/>).</item><label><term>notes</term></label><item>A section in which textual or
other kinds of notes are gathered together.</item><label><term>bibliogr</term></label><item>A list of bibliographic citations: this should be encoded
as a <gi tei="yes">listBibl</gi> (see section <xref target="COBI"/>).</item><label><term>index</term></label><item>Any form of index to the work.</item><label><term>colophon</term></label><item>A statement appearing at the end of a book describing the
conditions of its physical production.</item></list>
 </p><p>No additional elements are proposed for the encoding of back matter
at present.  Some characteristic examples follow; first, an index (for
the case in which a printed index is of sufficient interest to merit
transcription):
 
<eg><![CDATA[<back>
  <div type=index>
  <head>Index</head>
  <list type=index>
  <item>Actors, public, paid for the contempt attending
    their profession, <ptr target=P209>
  <item>Africa, cause assigned for the barbarous state of
    the interior parts of that continent, <ptr target=P125>
  <item>Agriculture
    <list type=indexentry>
    <item>ancient policy of Europe unfavourable to, <ptr target=P371>
    <item>artificers necessary to carry it on, <ptr target=P481>
    <item>cattle and tillage mutually improve each other,
         <ptr target=P325>
    <!-- ... -->
    <item>wealth arising from more solid than that which proceeds
    from commerce <ptr target=P520>
    </list>
  <item>Alehouses, not the efficient cause of drunkenness,
       <ptr target=P461>
  <!-- ... -->
  </list>
  </div>
  <!-- ... -->
</back>]]></eg><!-- Smith, Wealth of Nations, 1776; index to vol 1 -->
 </p><p>Next, a back-matter division in epistolary form:
 
<eg><![CDATA[<back>
  <div type=letter>
  <head>A letter written to his wife, founde with this booke
  after his death.</head>
  <p>The remembrance of the many wrongs offred thee, and thy
  unreproued vertues, adde greater sorrow to my miserable state,
  than I can utter or thou conceiue....
  ... yet trust I in the world to come to find mercie, by the
  merites of my Saiuour to whom I commend thee, and commit
  my soule.
  <signed>Thy repentant husband for his disloyaltie,
  <name>Robert Greene.</name></signed>
  <epigraph lang=LA><p>Faelicem fuisse infaustum</epigraph>
  <trailer>FINIS</trailer>
  </div>
  <!-- ... -->
</back>]]></eg><!-- Greene, Groatsworth of witte, 1592 -->
 </p><p>And finally, a list of corrigenda and addenda with pseudo-epistolary
features:
 
<eg><![CDATA[  <back>
  <div type=corrigenda>
  <head>Addenda</head>
  <salute lang=LA>M. Scriblerus Lectori</salute>
  <p>Once more, gentle reader I appeal unto thee, from the
  shameful ignorance of the Editor, by whom Our own Specimen
  of <name>Virgil</> hath been mangled in such miserable
  manner, that scarce without tears can we behold it. At the
  very entrance, Instead of <q lang=GR>prolego/mena</q>,
  lo! <q lang=GR>prolegw/mena</q> with an Omega!
  and in the same line <q lang=LA>consul&acirc;s</q>
  with a circumflex! In the next page thou findest <q lang=LA>
  leviter perlabere</>, which his ignorance took to be the
  infinitive mood of <q lang=LA>perlabor</> but ought to
  be <q lang=LA>perlabi</> ... Wipe away all these monsters,
  Reader, with thy quill.</p>
  </div>
  </back>]]></eg><!-- Pope, Dunciad Variorum, 1729 --><!--  end of draft -->
 </p><p>The <gi tei="yes">back</gi> element is defined in file
<term>TEIback2.dtd</term>; since there are no other specialized
back-matter tags, nothing else is defined there.
 
<dtdFrag id="DDSBACK" n="Tags for Back Matter" file="teiback2"><tagDecl tagDoc="BACK"/></dtdFrag>
 <!-- check filenames! -->
 </p></div2><div2 id="DSSTRUC" name="section" ref="Y"><head>DTD Fragment for Default Text Structure</head><p>The DTD fragment described by the present chapter is found in file
<term>teistr2.dtd</term>; it has the following overall structure:
 
<dtdFrag id="DDS" n="Default text structure" file="teistr2"><commDecl>This definition of the basic text structure is used by most
TEI base tag sets; some bases, however, use slight variations
upon it.</commDecl><claDecl classDoc="DIVTOP" type="model"/><claDecl classDoc="DIVBOT" type="model"/><dtdRef dtdFrag="DDSTEXT"/><dtdRef dtdFrag="DDSDIV"/><dtdRef dtdFrag="DDSDIVN"/><dtdRef dtdFrag="DDSDIVX"/><commDecl>Front matter is defined in TEI.front file.</commDecl><entDecl entDoc="TEIFRONT"/><peRef n="TEI.front.dtd"/><commDecl>Back matter is defined in TEI.back file.</commDecl><entDecl entDoc="TEIBACK"/><peRef n="TEI.back.dtd"/></dtdFrag>

 <!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ds3.odd ??><?tei:EOF p2ds.odd ??>
            <!-- 7 Default structure --></p></div2></div1></div0><div0 n="3" name="Part" ref="Y"><head>Base Tag Sets</head><?tei:SOF p2pr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2pr.odd,v $
    * Revision 1.5  1998/02/01 16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    *
    * Revision 1.4  98/02/01  16:34:20  tei
    * vacuous changes
    * i.e. no changes, this is a bum rap
    * 
    * Revision 1.3  94/04/01  16:31:33  msmcq
    * protect reference to teistr2.dtd within a marked section
    *  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : protect teistr invocation               --><!-- 93-05-31 : MSM : change ref to teistr (correct id)       --><div1 id="PR" n="8" name="chapter" ref="Y"><head>Base Tag Set for Prose</head><p>This chapter describes the base tag set for prose texts, the simplest
of the base tag sets defined by these Guidelines.  It should be used for
all texts in prose, whether fiction or non-fiction, novel or technical
manual.</p><p>Prose material can appear in the front and back matter of virtually
any text type, even where the body may be composed of very different
component elements. Consequently, the elements needed to encode
conventional prose are all included in the core tag set described in
chapter <xref target="CO"/>) and the base tag set for prose itself
defines no elements at all: it merely invokes the tag set for default
text structure.  When this base tag set is used, all the elements
defined in the core tag sets are available, as are those in the
default text structure described in chapter <xref target="DS"/>.  No
other elements are available, unless one or more of the additional tag
sets is also enabled.</p><p>The base tag set for prose should be invoked by defining the
parameter entity <term>tei.prose</term> with the value <q>INCLUDE</q>.
A document using this base tag set and no other will thus being as
follows:
<eg><![CDATA[ <!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY % tei.prose 'INCLUDE' >
 ]>]]></eg></p><p>The base tag set for prose is formally defined by the following DTD
fragment:
 
<dtdFrag id="DPR" n="Base Tag Set for Prose" file="teipros2.dtd"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>This base tag set does nothing but declare and embed the
default text structure.  When it is selected, therefore,
the only tags available are those in the core and those
defined in other selected tag sets.</commDecl><msection keywords="%TEI.singleBase"><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></msection></dtdFrag></p></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2pr.odd ??><!-- 8 Prose --><?tei:SOF p2ve.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ve.odd,v $
    * Revision 1.6  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.5  94/04/08  00:07:00  msmcq
    * changes to make DTD parse right
    * 
    * Revision 1.4  1993/11/26  18:14:11  msmcq
    * MSM revisions for publication, as published
    * --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : protect teistr invocation               --><!-- 94-03-31 : MSM : define vemix                            --><!-- 93-11-18 : MSM : Minor mostly cosmetic revisions         --><!-- 93-11-18 : MSM : Move enjamb class into ENT file\        --><!-- 93-11-13 : MSM : add N att on div1                       --><!-- 93-09-23 : MSM : cosmetic revisions                      --><!-- 29 jul - 11 aug 93: LB : redrafted from DR Eynsham draft --><!--                          making more P2ish               --><div1 id="VE" n="9" name="chapter" ref="Y"><head>Base Tag Set for Verse</head><p>This base tag set is intended for use when encoding texts which are
entirely or predominantly in verse, and for which the elements for
encoding verse structure already provided by the core tag set are
inadequate.</p><p>The tags described in section <xref target="COVE"/> include elements for
the encoding of verse lines and line groups such as stanzas: these are
available for any TEI document, irrespective of the base tag set it
uses. Like the base tag sets for prose and for drama, the base tag set
for verse additionally makes use of the tag set defined in
chapter <xref target="DS"/> to define the basic formal structure of a text,
in terms of <gi tei="yes">front</gi>, <gi tei="yes">body</gi> and <gi tei="yes">back</gi> elements and
the text-division elements into which these may be subdivided.</p><p>The base tag set for verse extends the facilities provided by these
two tag sets in the following ways:
<list type="simple"><item><q>numbered</q> <gi tei="yes">lg</gi> elements are provided, by analogy
with the <q>numbered</q> <term>divn</term> class elements discussed in
section <xref target="DSDIV"/> (see section <xref target="VEST"/>)</item><item>a special purpose <gi tei="yes">caesura</gi> element is provided, to
allow for segmentation of the verse line
(see section <xref target="VESE"/>)</item><item>a set of attributes is provided for the encoding of rhyme scheme
and metrical information (see sections <xref target="VEME"/> and<xref target="VERH"/>
)</item></list></p><p>To enable the base tag set for verse texts, a parameter entity
<term>TEI.verse</term> must be declared within the document type subset,
the value of which is <q>INCLUDE</q>, as further described in section<xref target="STIN"/>
. A document using this base tag set and no additional
tag sets will thus begin as follows:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.verse 'INCLUDE' >
 ]>]]></eg>
 
This declaration makes available the elements and attributes described
in this chapter, in addition to those described in chapters<xref target="CO"/>
 and <xref target="DS"/>.</p><div2 id="VESTR" name="section" ref="Y"><head>Structure of the Base Tag Set for Verse</head><p>The base tag set for verse contains the following entity
declarations:
 
<dtdFrag id="DVEE" n="Base Tag Set for Verse: entities" file="teivers2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>First, declare the class of
components specific to verse </commDecl><claDecl n="Component level items for verse" classDoc="COMPVERS" type="model"/><entDecl entDoc="VEMIX"/><commDecl>Next define attributes common to metrical elements</commDecl><claDecl n="Attributes for metrical elements" classDoc="METRICAL" type="atts"/><claDecl n="Enjambement attribute for L element" classDoc="ENJAMB" type="atts"/><commDecl>Now, we define the class of elements which can appear
only within metrical elements</commDecl><claDecl n="Phrase level elements for verse" classDoc="VEPHR" type="model"/></dtdFrag></p><p>The base tag set for verse contains the following element
declarations:
 
<dtdFrag id="DVE" n="Base Tag Set for Verse" file="teivers2.dtd"><commDecl>First, declare the default text structure, which
is the same for verse as it is for other kinds of text.  (But declare
it only if verse is the only base.)</commDecl><msection keywords="%TEI.singleBase"><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></msection><commDecl>Finally, declare the elements specific to this base
tag set</commDecl><dtdRef dtdFrag="DVEST"/><dtdRef dtdFrag="DVESE"/></dtdFrag></p></div2><?tei:SOF p2vest.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2vest.odd,v $
# Revision 1.4  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *--><!-- Revisions:                                               --><!-- 11 jan 98 : LB : eg typos --><!-- 93-11-22 : MSM : purely cosmetic                         --><!-- 93-11-21 : MSM : label LG as stanza in FQ example        --><!-- 93-11-18 : MSM : fix examples to parse right             --><!-- 93-11-18 : MSM : minor mostly cosmetic changes           --><!-- 93-11-18 : MSM : revert to TYPE=BODY from TYPE=QUATRAINS --><div2 id="VEST" name="section" ref="Y"><head>Structural Divisions of Verse Texts</head><p>Like other kinds of text, texts written in verse may be of widely
differing lengths and structures. A complete poem, no matter how short,
may be treated as a free-standing text, and encoded in the same way as
a distinct prose text. A group of poems functioning as a single unit
may be encoded either as a <gi tei="yes">group</gi> or as a <gi tei="yes">text</gi>,
depending on the encoder's view of the text. For further discussion,
including an example encoding for a verse anthology, see chapter <xref target="DS"/>.
 </p><p>Many poems consist only of ungrouped lines.<!-- This short poem by Ezra Pound is a simple case:          --><!--                                                          --><!-- < eg>                                                    --><!-- < ![ CDATA [                                             --><!-- < text>                                                  --><!-- < body>                                                  --><!-- < head>In a Station of the Metro< /head>                 --><!-- < l>The apparition of those faces in the crowd;< /l>     --><!-- < l>Petals on a wet, black bough.< /l>                   --><!-- < /body>                                                 --><!-- < /text>                                                 --><!-- ] ] >                                                    --><!-- < /eg>                                                   --><!-- E.Pound in Imagist Poetry ed Jones, Penguin 1972, p.95 --><!--                                                          -->
 <!-- The chances of our being allowed to reprint this         --><!-- copyright poem IN ITS ENTIRETY are minuscule.  We would  --><!-- do better with Strickland Gilliland, On the Antiquity    --><!-- of Fleas (which is probably out of copyright):           --><!--                                                          --><!-- Adam                                                     --><!-- Had 'em.                                                 --><!--                                                          --><!-- Or Emily Dickinson:                                      -->
This short poem by Emily Dickinson is a simple case:
 
<eg><![CDATA[<text>
<front><head>1755</head></front>
<body>
<l>To make a prairie it takes a clover and one bee,</l>
<l>One clover, and a bee,</l>
<l>And revery.</l>
<l>The revery alone will do,</l>
<l>If bees are few.</l>
</text>]]></eg>
 <!-- Emily Dickinson, transcribed from the Norton Anthology   --><!-- of Poetry, ed.  Arthur Eastman et al., NY:  W.W.Norton,  --><!-- 1970, p. 859, ED no. 1755.                               -->
 </p><p>Often, however, lines are grouped, formally or informally, into
stanzas, verse paragraphs, etc.  The <gi tei="yes">lg</gi> element defined in the
core tag set (in section <xref target="COVE"/>) may be used for all such
groupings.  It may thus serve for informal groupings of lines such as
those of the following example from Allen Ginsberg:
 
<eg><![CDATA[<text><body><head>My Alba</head>
 
<lg type=free>
<l>Now that I've wasted</l>
<l>five years in Manhattan</l>
<l>life decaying</l>
<l>talent a blank</l>
</lg>
<lg>
<l>talking disconnected</l>
<l>patient and mental</l>
<l>sliderule and number</l>
<l>machine on a desk</l>
</lg>
<!-- ... -->
</text>]]></eg><!-- A Ginsberg 'My alba', Reality Sandwiches, 1963 (City Lights) -->
 <!-- Since this one does not appear in its entirety, this     --><!-- extract ought to qualify as fair use.  -msm              -->
 </p><p>It may also be used to mark the verse paragraphs into which longer
poems are often divided, as in the following example from Samuel Taylor
Coleridge's <title.p>Frost at Midnight</title.p>:
<eg><![CDATA[<lg type=para>
<l>The Frost performs its secret ministry,
<l>Unhelped by any wind....
<!-- ... -->
<l>Whose puny flaps and freaks the idling Spirit
<l>By its own moods interprets, every where
<l>Echo or mirror seeking of itself,
<l part=i>And makes a toy of Thought.
</lg><lg>
<l part=f>But O! how oft,
<l>How oft, at school, with most believing mind
<l>Presageful, have I gazed upon the bars,
<l>To watch that fluttering <hi>stranger</hi>! ...
<!-- ... -->
</lg>
<lg>
<l>Dear Babe, that sleepest cradled by my side,
<!-- ... -->]]></eg><!-- STC, Frost at Midnight (ed EH Coleridge, OUP, p.240 -->
 
Note, in the above example, the use of the <att tei="yes">part</att> attribute on
the <gi tei="yes">l</gi> element, where a verse line is broken between two line
groups, as discussed in section <xref target="COVE"/>.  (Note also that
here and in some other examples in this chapter the end-tags for the
<gi tei="yes">l</gi> element, being redundant, have been omitted, as is allowed
when the SGML feature OMITTAG is enabled.)
 </p><p>Most typically, however, the <gi tei="yes">lg</gi> element is used to mark the
highly regular line groups which characterize stanzaic and similar verse
forms, as in the following example from Chaucer:
 
<eg> <![CDATA[
<lg>
<l>Sire Thopas was a doghty swayn;
<l>White was his face as payndemayn,
<l>His lippes rede as rose;
<l>His rode is lyk scarlet in grayn,
<l>And I yow telle in good certayn,
<l>He hadde a semely nose.
</lg><lg>
<l>His heer, his ber was lyk saffroun,
<l>That to his girdel raughte adoun;
<!-- ... -->
</lg>
 ]]></eg><!-- Chaucer, CT, B 1914 ff, ed Robinson p 164 -->
 </p><p>Like other text-division elements, <gi tei="yes">lg</gi> elements may be nested
hierarchically.  For example, one particularly common English stanzaic
form consists of a quatrain or sestet followed by a couplet.  The
<gi tei="yes">lg</gi> element may be used to encode both the stanza and its
components, as in the following example from Byron:
 
<eg><![CDATA[<lg type=stanza>
   <lg type=sestet>
     <l>In the first year of Freedom's second dawn
     <l>Died George the Third; although no tyrant, one
     <l>Who shielded tyrants, till each sense withdrawn
     <l>Left him nor mental nor external sun:
     <l>A better farmer ne'er brushed dew from lawn,
     <l>A worse king never left a realm undone!
   </lg>
   <lg type=couplet>
     <l>He died &mdash; but left his subjects still behind,
     <l>One half as mad &mdash; and t'other no less blind.
   </lg>
</lg>]]></eg><!-- Byron, Vision of Judgment viii ed EH Coleridge 1922) -->
 </p><p>Note the use of the <att tei="yes">type</att> attribute to name the type of
unit encoded by the <gi tei="yes">lg</gi> element; this attribute is common to all
members of the <term>divn</term> class
(see section <xref target="DSDIV1"/>).<note source="auth" place="display" anchored="Y">For discussion of other
attributes of this class, see <xref target="DSDIV3X"/>.</note>
<q>Sestet</q> and <q>couplet</q> might conceivably also be used as the
values of the <att tei="yes">met</att> attribute in a metrical analysis, for which
see below, section <xref target="VEME"/>.  The <att tei="yes">type</att> attribute is
intended solely for conventional names of different classes of text
block; the <att tei="yes">met</att> attribute is intended for systematic metrical
analysis.
 </p><p>The above example uses <soCalled>un-numbered</soCalled> line groups
which can nest within each other to any depth. When the base tag set for
verse is in use, <soCalled>numbered</soCalled> line groups may also be
used as an alternative.
<tagList style="one-line"><tagDesc tagDoc="LG1"/><tagDesc tagDoc="LG2"/></tagList>
 
The base tag set for verse defines up to five such numbered line group
elements, <gi tei="yes">lg1</gi> to <gi tei="yes">lg5</gi> inclusive.  These function in
exactly the same way as the numbered <term>divn</term> class elements
discussed in section <xref target="DSDIV"/>.
 </p><p>As an example of their use, consider the Shakespearean
sonnet. This may be divided into two parts: a concluding couplet, and
a body of twelve lines, itself subdivided into three quatrains:<!-- any suggestions for a better name than 'body' to         --><!-- describe the twelve lines gratefully accepted ... (lb)   --><!-- done.  At least, *I* think it's better ... (msm)         --><!-- But LB preferred 'body' to 'quatrains'     (msm)         -->
<eg><![CDATA[<text><body>
<lg1 type=body>
<lg2 type=quatrain>
<l>My Mistres eyes are nothing like the Sunne,
<l>Currall is farre more red, then her lips red
<l>If snow be white, why then her brests are dun:
<l>If haires be wiers, black wiers grown on her head:
</lg2>
<lg2>
<l>I have seene Roses damaskt, red and white,
<l>But no such Roses see I in her cheekes,
<l>And in some perfumes is there more delight,
<l>Then in the breath that from my Mistres reekes.
</lg2>
<lg2>
<l>I love to heare her speake, yet well I know,
<l>That Musicke hath a farre more pleasing sound:
<l>I graunt I never saw a goddesse goe,
<l>My Mistres when shee walkes treads on the ground.
</lg2>
</lg1>
<lg1 type=couplet>
<l>And yet by heaven I think my love as rare,
<l>As any she beli'd with false compare.
</lg1>
</text>]]></eg><!-- Shakespeare, Sonnets 1609, no 130 -->
 </p><p>Particularly lengthy poetic texts are often subdivided into units
larger than stanzas or paragraphs, which may themselves be
subdivided. Spenser's <title>Faery Queene</title>, for example,
consists of twelve <soCalled>books</soCalled> each of which contains a
prologue followed twelve <soCalled>cantos</soCalled>. Each prologue
and each canto consists of nine-line <soCalled>stanzas</soCalled>,
each of which follows the same regular pattern. Other examples in the
same tradition are easy to find.
 </p><p>Large structures of this kind are most conveniently represented by
the <term>divn</term> class elements such as <gi tei="yes">div</gi> or
<gi tei="yes">div1</gi> described in section <xref target="DSDIV"/>.  Thus the start
of the <title>Faery Queene</title> might be encoded as follows:
 
<eg><![CDATA[ <body>
 <div1 type=book n='I'>
   <div2 type=canto n='1'>
      <lg type=stanza n='I.1.1'>
        <l>A noble knight was pricking on the plain
        <l>Ycladd in mightie armes and silver shielde,
   <!-- ... -->
 </body>]]></eg>
 
The encoder must choose at which point in the hierarchy of structural
units to introduce <gi tei="yes">lg</gi> elements rather than a yet smaller
<gi tei="yes">div</gi> element:  it would (for example) also be possible to encode
the above example as follows:
 
<eg><![CDATA[ <body>
 <div1 type=book n=I>
   <div2 type=canto n=I.1>
      <div3 type=stanza n=I.1.1>
        <l>A noble knight was pricking on the plain
        <l>Ycladd in mightie armes and silver shielde,
        <!-- ... -->
 </body>]]></eg>
 </p><p>One reason for preferring the former version is that not all of
Spenser's stanzaic verse is organized into both cantos and books.  In a
corpus containing other works as well as the <title>Faery
Queene</title>, it would be inconvenient for stanzas to appear in one
part as <gi tei="yes">div3</gi> elements, and in another as <gi tei="yes">div2</gi>
elements.<note source="auth" place="display" anchored="Y">Another way of avoiding this problem would be to use
un-numbered <gi tei="yes">div</gi> elements; see further <xref target="DSDIV"/>.</note>
 </p><p>The numbered line group elements have the following formal
definition:
<dtdFrag id="DVEST" n="Numbered line groups" file="teivers2.dtd"><tagDecl tagDoc="LG1"/><tagDecl tagDoc="LG2"/><tagDecl tagDoc="LG3"/><tagDecl tagDoc="LG4"/><tagDecl tagDoc="LG5"/></dtdFrag><?tei:EOF p2vest.odd ??>
<?tei:SOF p2vese.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2vese.odd,v $
    * Revision 1.7  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.6  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.5  1994/03/28  17:10:48  lou
    * fix seg attlist error
    * 
    * Revision 1.4  1994/03/15  10:08:12  lou
    * Typos etc.
    * 
    * Revision 1.3  1993/11/26  18:14:11  msmcq
    * MSM revisions for publication, as published
    * --><!-- Revisions:                                               --><!-- 11 jan 98 : LB : killed numbered segs pro tem --><!-- 93-11-22 : MSM : purely cosmetic                         --><!-- 93-11-21 : MSM : accept changes from David Robey         --><!-- 93-11-18 : MSM : fix some problems in exx                --><!-- 93-11-18 : MSM : Revisions as per LB for clarity         --><!-- 93-11-13 : MSM : correct references to SEG               --><!-- 93-11-13 : MSM : Added RCS id                            --></p></div2><div2 id="VESE" name="section" ref="Y"><head>Components of the Verse Line</head><p>It is often convenient for various kinds of analysis to encode
subdivisions of verse lines.  The general purpose <gi tei="yes">seg</gi> element
defined in the tag set for segmentation and alignment (section <xref target="SASE"/>) is provided for this purpose:
 
<tagList style="one-line"><tagDesc tagDoc="SEG" atts="part"/></tagList></p><p>To use this element together with the base tag set for verse, the
tag set for segmentation and alignment must also be enabled, by an
additional declaration in the document type subset, as further
described in section <xref target="STIN"/>.  A document using the base
tag set for verse and this additional tag sets will thus begin as
follows:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
 <!ENTITY % TEI.verse 'INCLUDE' >
 <!ENTITY % TEI.linking 'INCLUDE' >
 ]>]]></eg></p><p>In Old and Middle English alliterative verse, individual verse lines
are typically split into half lines. The <gi tei="yes">seg</gi> element may be
used to mark these explicitly, as in the following example from
Langland's <title>Piers Plowman</title>:
 
<eg><![CDATA[<l><seg>In a somer seson,</seg>
   <seg>whan softe was the sonne,</seg></l>
<l><seg>I shoop me into shroudes</seg>
   <seg>as I a sheep were,</seg></l>
<l><seg>In habite as an heremite </seg>
   <seg>unholy of werkes,</seg></l>
<l><seg>Went wide in this world </seg>
   <seg>wondres to here.</seg></l>
<!-- ... -->]]></eg><!-- Langland: The Vision of Piers Plowman B-text ed Schmidt --></p><p>The <gi tei="yes">seg</gi> element can be nested hierarchically, in the same
way as the <gi tei="yes">lg</gi> element, down to whatever level of detailed
structure is required.  In the following example, the line has been
divided into <term>feet</term>, each of which has been further
subdivided into into syllables.  (The eccentric formatting ensures that
no spaces are introduced within words unless they are within SGML tags
and thus not significant.)
 
<eg><![CDATA[   <l><seg type=foot>
         <seg type=syll>Ar</><seg
              type=syll>ma</>
         <seg type=syll>vi</></seg><seg
      type=foot><seg
              type=syll>rum</><seg
              type=syll>que</>
         <seg type=syll>ca</></seg><seg
      type=foot><seg
              type=syll>no</>
         <seg type=syll>Tro</></seg><seg
      type=foot><seg
              type=syll>iae</>
         <seg type=syll>qui</>
      </seg>
      <seg type=foot>
         <seg type=syll>pri</><seg
              type=syll>mus</>
         <seg type=syll>ab</>
      </seg>
      <seg type=foot>
         <seg type=syll>or</><seg
              type=syll>is</>
      </seg>
</l>]]></eg></p><p>The <gi tei="yes">seg</gi> element may be used to identify any subcomponent of
a line which has content; its type attribute may characterize such units
in any way appropriate to the needs of the encoder.  For the specific
case of labeling each foot with its formal type (<q>dactyl</q>,
<q>spondee</q>, etc.), and each syllable with its metrical or prosodic
status (syllables bearing primary or secondary stress, long syllables,
short syllables), however, the specialized attributes <att tei="yes">met</att> and
<att tei="yes">real</att> are defined, which provide a more systematic framework
than the <att tei="yes">type</att> attribute; see section <xref target="VEME"/>
below.</p><p>In classical verse, a hexameter like that above may also be formally
divided into two <soCalled>hemistiches</soCalled>.  This example
provides an interesting case, in that the boundary of the first
hemistich falls in the middle of one of the feet (between the syllables
<q>no</q> and <q>Tro</q>).  If both kinds of segmentation are required,
the <att tei="yes">part</att> attribute might be used to mark the overlapping
structure as follows.  (This example uses the slightly artificial
convention that word space is included within the syllable segments, and
all other white space is to be ignored; though convenient for visual
clarity in presentations like this one, this convention is not
recommended for normal use.)
 
<eg><![CDATA[   <l><seg type=hemistich>
         <seg type=foot>
           <seg type=syll> Ar</>
           <seg type=syll>ma </>
           <seg type=syll>vi</>
         </seg>
         <seg type=foot>
           <seg type=syll>rum</>
           <seg type=syll>que </>
           <seg type=syll>ca</>
           </seg>
         <seg type=foot part=I>
           <seg type=syll>no </>
         </seg>
      </seg>
      <seg type=hemistich>
         <seg type=foot part=F>
           <seg type=syll>Tro</>
         </seg>
         <seg type=foot>
            <seg type=syll>iae </>
            <seg type=syll>qui </>
         </seg>
      </seg>
   </l>]]></eg>
 <!-- <p>Numbered <gi>seg</gi> elements may also be used; these have the --><!-- disadvantage &mdash; or advantage &mdash; of requiring a --><!-- consistent, layer-by-layer analysis, and the advantage of providing a--><!-- useful</item> default for the <att>type</att> attribute, which must be--><!-- specified only once for each level, as well as allowing the omission--><!-- of many end-tags, which makes the presentation more compact.-->
 <!--   <l><seg1 type=hemistich>--><!--          <seg2 type=foot>--><!--                <seg3 type=syll> Ar<seg3>ma <seg3>vi</>--><!--          <seg2><seg3>rum<seg3>que <seg3>ca</>--><!--          <seg2 part=I><seg3>no </>--><!--       <seg1>--><!--          <seg2 part=F><seg3>Tro</>--><!--          <seg2><seg3>iae <seg3>qui </>-->
<!--     </l>--><!-- ]]>-->
<!--     </l>-->
  <!-- ... --><!-- ]]>--><!-- </eg>--><!--     < l >  < seg1 type=hemistich >                       --><!--           < seg2 type=foot >                             --><!--             < seg3 type=syll >  Ar < / >                 --><!--             < seg3 > ma  < / >                           --><!--             < seg3 > vi < / >                            --><!--           < /seg2 >                                      --><!--           < seg2 >                                       --><!--             < seg3 > rum < / >                           --><!--             < seg3 > que  < / >                          --><!--             < seg3 > ca < / >                            --><!--             < /seg >                                     --><!--           < seg2 part=I >                                --><!--             < seg3 > no  < / >                           --><!--           < /seg >                                       --><!--        < /seg >                                          --><!--        < seg1 >                                          --><!--           < seg2 part=F >                                --><!--             < seg3 > Tro < / >                           --><!--           < /seg >                                       --><!--           < seg2 >                                       --><!--             < seg3 > iae  < / >                          --><!--             < seg3 > qui  < / >                          --><!--           < /seg >                                       --><!--    < !    ....    >                                      --></p><p>Instead of using the <att tei="yes">part</att> attribute on the <gi tei="yes">seg</gi>
element, it might be simpler just to mark the point at which the caesura
occurs.  An additional element is provided for analyses of this kind, in
which what is to be marked are points <q>between the words</q>, which
have some significance within a verse line:
 
<tagList style="one-line"><tagDesc tagDoc="CAESURA"/></tagList>
 
In classical prosody, the <term>caesura</term>, which occurs within a
foot, is distinguished from a <term>diaeresis</term>, which occurs on a
foot boundary (not to be confused with the division of a diphthong into
two syllables, or the diacritic symbol used to indicate such division,
each of which is also termed <term>diaeresis</term>).  This distinction
is rarely made nowadays, the term <cited>caesura</cited> being used for
any division irrespective of foot boundaries.  No special-purpose <gi tei="no">diaeresis</gi> element is therefore provided.</p><p>As an example of the <gi tei="yes">caesura</gi> element, we refer again to the
example from Langland.  An encoder might choose simply to record the
location of the caesura within each line, rather than encoding each
half-line as a segment in its own right, as follows:
 
<eg><![CDATA[<l>In a somer seson, <caesura> whan softe was the sonne, </l>
<l>I shoop me into shroudes <caesura> as I a sheep were, </l>
<l>In habite as an heremite <caesura> unholy of werkes, </l>
<l>Went wide in this world <caesura> wondres to here. </l>]]></eg><!-- Langland: The Vision of Piers Plowman B-text ed Schmidt --></p><p>Logically, the opposite of caesura might be considered to be
enjambement.  The base tag set for verse defines an <att tei="yes">enjamb</att>
attribute for the <gi tei="yes">l</gi> element, which alllows the presence or
absence of enjambement to be signaled.  The following lines demonstrate
the use of the <att tei="yes">enjamb</att> attribute to mark places where there is
a discrepancy between the boundaries of the <gi tei="yes">l</gi> elements and the
syntactic structure of the verse (a discrepancy of some significance in
some schools of verse):
 
<eg><![CDATA[<l enjamb=y>Un astrologue, un jour, se laissa choir</l>
<l>Au fond d'un puits.]]></eg><!-- La Fontaine, somewhere (Larousse) -->
 <!-- There's no way of constraining enjamb to end of line.    --><!-- I think it wd be better as an attribute of l - like      --><!-- latching att on u (lb)                                   --><!-- I agree, but it seems rather late to change it now.      --><!-- But better late than never.  Changed! (msm)              --></p><p>The elements discussed in this section are formally defined as
follows:
<dtdFrag id="DVESE" n="Caesura" file="teivers2.dtd"><tagDecl tagDoc="CAESURA"/></dtdFrag></p></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2vese.odd ??><?tei:SOF p2veme.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2veme.odd,v $
# Revision 1.8  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.7  1994/03/28  18:19:41  msmcq
# add TYPE attribute to CODE.
# --><!-- Revisions:                                               --><!-- 11 jan 98 : LB : remove seg1 --><!-- 94-03-19 : MSM : add required TYPE att to CODE elements  --><!-- 21 jan 94: LB: name change: metNotation to metDecl --><!-- 19 dec 93 : LB : fixed xref to span --><!-- 93-11-23 : MSM : last changes by LB on RHYME att         --><!-- 93-11-22 : MSM : cosmetic only                           --><!-- 93-11-22 : MSM : changes from LB (final compromises?)    --><!-- 93-11-21 : MSM : accept David Robey's changes            --><!--                  notably, add a section on in-line tagging --><!-- 93-11-18 : MSM : fix commiato example                    --><!-- 93-11-18 : MSM : Cosmetic changes (and SLOW LENGTH prosody) --><div2 id="VEME" name="section" ref="Y"><head>Rhyme and Metrical Analysis</head><p>When the base tag set for verse is in use, the following additional
attributes are available to record information about rhyme and metrical
form:
 
<adList classDoc="METRICAL" atts="met real rhyme"/>
 </p><p>These attributes may be attached to the <gi tei="yes">lg</gi> element, to any
of its numbered equivalents <gi tei="yes">lg1</gi>, <gi tei="yes">lg2</gi>, etc., to the
higher-level text-division elements <gi tei="yes">div</gi>, <gi tei="yes">div1</gi>, etc.,
or to the <gi tei="yes">body</gi> element itself if the whole of a text is in
verse.  In general, the attributes should be specified at the highest
level possible; they may not however be specifiable at the highest level
if some of the subdivisions of a text are in prose and others in verse.
All these attributes may also be attached to the <gi tei="yes">l</gi> and
<gi tei="yes">seg</gi> elements, but the default notation for the <att tei="yes">rhyme</att>
attribute has no defined meaning when specified on <gi tei="yes">l</gi> or
<gi tei="yes">seg</gi>.  The value for these attributes may take any form desired
by the encoder; the nature of the notation used will determine how well
the attribute values can be processed by automatic means.
 </p><p>The primary function of the metrical attributes is to encode the
conventional metrical or rhyming structure within which the poet is
working, rather than the actual prosodic realization of each line; the
latter can be recorded using the <att tei="yes">real</att> attribute, as further
discussed below.  There is no provision at this time, however, for
encoding the particular realization of a rhyme pattern.
 </p><div3 name="subsection" ref="Y"><head>Sample Metrical Analyses</head><p>As a simple example of the use of these attributes, consider the
following lines from Pope's <title.p>Essay on Criticism</title.p>:
 
<eg> <![CDATA[
  <text>
    <front> ... </front>
    <body met='-+|-+|-+|-+|-+/' rhyme='aa'>
      <lg1 n=1 type="verse paragraph">
        <l>'Tis hard to say, if greater Want of Skill</l>
        <l>Appear in <hi>Writing</> or in <hi>Judging</hi> ill;</l>
        <l>But, of the two, less dang'rous is th'Offence,</l>
        <l>To tire our <hi>Patience</hi>, than mis-lead
           our <hi>Sense</hi>:</l>
      <!-- ... -->
    </body>
  </text>]]></eg><!-- Pope, Essay on Criticism, 1734?-->
 </p><p>The body of this text is written entirely in <term>heroic
couplets</term>; each line is iambic pentameter (which, using a common
notation, can be described with the formula
<code tei="yes" type="val">-+|-+|-+|-+|-+/</code>, each <code tei="yes" type="val">-</code> denoting a
metrically unstressed syllable, each <code tei="yes" type="val">+</code> a metrically
stressed one, each <code tei="yes" type="val">|</code> a foot boundary, and the
<code tei="yes" type="val">/</code> a line-end), and the couplets rhyme (which can be
represented with the conventional formula <code tei="yes" type="val">aa</code>).
 </p><p>Because both rhyme pattern and metrical form are consistent
throughout the poem, they may be most conveniently specified on the
<gi tei="yes">body</gi> element; the values given for the attributes will be
inherited by any metrical unit contained within this <gi tei="yes">body</gi>
element, and must be interpreted in the appropriate way.
 </p><p>Since the notation used in the <att tei="yes">met</att>, <att tei="yes">real</att>,<!-- LB objects to next phrase --><!-- but MSM insists, and persuades LB to let the abab        --><!-- notation be the default, but to allow user-specified     --><!-- alternative notations (with the consequence that RHYME   --><!-- must become legal on L as well as LG).                   -->
and <att tei="yes">rhyme</att>
attributes is user-defined, no binding description can be given of its
details or of how its interpretation must proceed.  (A default notation
is provided for the <att tei="yes">rhyme</att> attribute, which however the
encoder can replace with another; see section <xref target="VERH"/>.)  It
is expected, however, that software should be able to support these
attributes in useful ways; the more intelligent the software is, and the
more knowledge of metrics is built into it, the better it will be able
to support these attributes.  In the extract given above, for example,
the <att tei="yes">met</att> and <att tei="yes">rhyme</att> attribute values specified on
the <gi tei="yes">body</gi> element are inherited directly by the <gi tei="yes">lg</gi>
elements nested within the body.  Since the <att tei="yes">met</att> value
specifies the metrical form of a single verse line, the structure of the
<gi tei="yes">lg</gi> as a whole is understood to involve as many repetitions of
the pattern as there are lines in the verse paragraph.  The same
attribute value, when inherited in turn by the <gi tei="yes">l</gi> element, must
be understood <emph>not</emph> to repeat.  With sufficiently
sophisticated software, segments within the line might even be
understood as inheriting precisely that portion of the formula which
applies to the segment in question; this will, however, be easier to
accomplish for some languages than for others.
 <!-- LB objects to the following paragraph --><!-- but has gradually improved it enough make it almost bearable. -->
 </p><p>The <att tei="yes">rhyme</att> attribute in this example uses the default
notation to specify a rhyme scheme applicable only to pairs of lines.
As elsewhere, the default notation for the <att tei="yes">rhyme</att> attribute
has no meaning for metrical units at the line level or below.  In verse
forms where line-internal rhyme is structurally significant, e.g. in
some skaldic poetry, the default notation is incapable of expressing the
required information, since the rhyme pattern may need to be specified
for units smaller than the line.  In such cases, a user-specified rhyme
notation must be substituted for the default notation, or else the rhyme
pattern must be described using some alternative method (e.g. by using
the <gi tei="yes">link</gi> mechanism described below).<!-- < att > rhyme < /att >  attribute would have to be       --><!-- understood as applying potentially to lines or even to   --><!-- smaller units, and a user-specified rhyme notation       --><!-- would have to be substituted for the default notation.   -->
 </p><p>The precise semantics of the <att tei="yes">met</att> attribute and the
inferences which software is expected or able to draw from it, are
implementation-dependent; so are the semantics and processing of the
<att tei="yes">rhyme</att> attribute, when user-specified notations are used.
 </p><p>A formal definition of the significance of each component of the
pattern given as the value of the <att tei="yes">met</att> attribute may be
provided in the <gi tei="yes">metDecl</gi> element within the
<gi tei="yes">encodingDecl</gi> element in the TEI header (see section <xref target="HDMN"/>).  The encoder is free to invent any notation appropriate
to his or her analytic needs, provided that it is adequately documented
in this element.  The notation may define metrical components using
invented or traditional names (such as <q>iamb</q> or <q>hexameter</q>)
or in terms of basic units such as codes for stressed or unstressed
syllables, or a combination of the two.
 </p><p>The <att tei="yes">real</att> (for <q>realization</q>) attribute may optionally
be specified to indicate any deviation from the pattern defined by the
<att tei="yes">met</att> attribute which the encoder wishes to record.  By
default, the <att tei="yes">real</att> attribute has the same value as the
<att tei="yes">met</att> attribute on the same element; it is only necessary to
provide an explicit value when the realization differs in some way from
the abstract metrical pattern.  The tension between conventional
metrical pattern and its realization may thus be recorded explicitly.
For example, many readers of the above passage would stress the word
<q>But</q> at the beginning of the third line rather than the word
<q>of</q> following it, as the metrical pattern would normally require.
This variation might be encoded as follows:
 
<eg> <![CDATA[
<l real='+-|-+|-+|-+|-+'>But of the two...]]></eg>
 </p><p>Where the <att tei="yes">real</att> attribute is used to over-ride the default
or conventional metrical pattern, it applies only to the element on
which it is specified.  The default pattern for any subsequent lines is
unaffected.
 </p><p>As it happens, this particular kind of variation is very common in
the English iambic pentameter;<note source="auth" place="display" anchored="Y">It even has a name:
<term>anapaestic substitution</term>.</note> an encoder might therefore
choose to regard this not as an instance of a variant realization, but
as an instance of a variant metrical form:
 
<eg><![CDATA[<l met='+-|-+|-+|-+|-+'>But of the two...]]></eg>
 
Alternatively, a different metrical notation might be defined, in which
this kind of variation was permitted throughout the text.
 </p><p>In choosing whether to over-ride a metrical specification in this
way or by using the <att tei="yes">real</att> attribute, the encoder is required
to determine whether the change is a systematic or conventional one (as
in this example) or an occasional variation, perhaps for local effect.
In the following example, from Goethe's <title.p>Auf dem See</title.p>,
the variation is a matter of local realization:<!-- DR suspects title.  He is right:  dem not den. (msm)     --><!-- Corrected typos in title, final punctuation. (msm)       -->
 
<eg> <![CDATA[
  <lg1 type="chevy-chase-stanza"
       met="-+-+-+-+/-+-+-+"
       rhyme='ababcdcd'>
  <l n=1>                  Und frische Nahrung, neues Blut
  <l n=2 real="+--+-+">    Saug' ich aus freier Welt;
  <l n=3 real="+--+-+-+">  Wie ist Natur so hold und gut,
  <l n=4 real="---+-+">    Die mich am Busen haelt!
  <l n=5>                  Die Welle wieget unsern Kahn
  <l n=6>                  Im Rudertakt hinauf,
  <l n=7>                  Und Berge, wolkig himmelan,
  <l n=8>                  Begegnen unserm Lauf.]]></eg>
 
On the other hand, the famous inserted alexandrine in Pope's <q>Essay on
Criticism</q>, might be encoded as follows:
 
<eg><![CDATA[     <l n=356> A needless alexandrine ends the song,
     <l n=357 met='-+|-+|-+|-+|-+|-+' real='++|-+|-+|+-|++|-+'>
     That, like a wounded snake, drags its slow length along.
     </l>]]></eg><!-- slow changed from - to + on David Chisholm's             --><!-- suggestion (msm)                                         -->
 
Here the <att tei="yes">met</att> attributes indicates that a different metrical
convention (the alexandrine) is in force, while the <att tei="yes">real</att>
attribute indicates that there is a variation from that
convention.  As with many other aspects of metrical analysis, however,
this is of necessity an entirely interpretive judgment.
 </p></div3><div3 name="subsection" ref="Y"><head>Segment-Level versus Line-level Tagging</head><p>The examples given so far have encoded information about the
realization of metrical conventions at the level of the whole
verse-line.  This has obvious advantages of simplicity, but the
disadvantage that any deviation from metrical convention is not
marked at its precise point of occurrence in the text.  Greater
precision may be achieved, but only at the cost of marking deviant
metrical units explicitly.  This may be done
with the <gi tei="yes">seg</gi> element, giving the
variant realization as the value of the <att tei="yes">real</att> attribute on
that element.  Using this method, the example given immediately above
might be encoded as follows:
 
<eg><![CDATA[<l n=356> A need<seg type=foot n=2 real='--'>less
   a</seg>lexandrine ends the song,
<l n=357 met='-+|-+|-+|-+|-+|-+'>
   <seg n=1 real='++'> That, like </seg> a wounded snake,
   <seg n=4 real='++'> drags its </seg>
   <seg n=5 real='++'> slow length </seg>
   along.
</l>]]></eg>
 
The marking of the foot boundaries with the symbol <code tei="yes" type="val">|</code> in the
<att tei="yes">met</att> attribute value of the <gi tei="yes">l</gi> element allows the
human reader, or a sufficiently intelligent software program, to isolate
the correct portion of that attribute value as the default value for the
same attribute on the <gi tei="yes">seg</gi> elements for feet, namely <code tei="yes" type="val">-+</code>.
It is of course up to the encoder to decide whether or not to include
the <att tei="yes">n</att> attribute of <gi tei="yes">seg</gi> here, and whether or not also
to tag the feet in the line in which there is no deviation from the
metrical convention.  The ability of software to infer which foot is
being marked, if not all are tagged, will depend heavily on the language
of the text and the knowledge of prosody built into the software; the
fuller and more explicit the markup, the easier it will be for software
to handle it.  It may prove useful, however, to mark metrical deviations
in the manner shown, even if the available software is not sufficiently
intelligent to scan lines without aid from the markup.  Human readers
who are interested in prosody may well be able to exploit the markup in
useful ways even with less sophisticated software.
 </p><p>There are circumstances where it may also be useful to use the
<att tei="yes">met</att> attribute of <gi tei="yes">seg</gi>.  If we wish to identify the
exact location of the different types of foot in the first line of
Virgil's <title>Aeneid</title>, the text could be encoded as follows
(for simplicity's sake the caesura has been omitted):
 
<eg><![CDATA[<l><seg type=foot met='+--'>Arma vi</>
   <seg met='+--'>rumque ca</>
   <seg met='++'>no Tro</>
   <seg met='++'>iae qui </>
   <seg met='+--'>primus ab</>
   <seg met='++'> oris</>
</l>]]></eg>
 
An appropriate value of the <att tei="yes">met</att> attribute might also be
encoded on the enclosing <gi tei="yes">div</gi> or <gi tei="yes">body</gi> element, to
indicate that each foot may be made up of a dactyl or a spondee, so that
the values given here for <att tei="yes">met</att> at the level of the foot may be
considered a series of local variations on this fundamental pattern; in
cases like this, of course, the local variations may also be considered
aspects of realization rather than of convention, in which case the
<att tei="yes">real</att> attribute may be used instead of <att tei="yes">met</att>, if
desired.
 <!-- Previous paragraph a substitute for the following,       --><!-- which appears to contain a slip:  Vergil wrote           --><!-- distichs, but not, surely, in the Aeneid?  (msm)         --><!-- An appropriate value of the  < att > met < /att >        --><!-- attribute might also be encoded at the level of the      --><!-- whole poem, as an attribute for instance of  < gi >      --><!-- div0 < /gi > , to indicate that the overall metrical     --><!-- scheme is that of alternating hexameters and             --><!-- pentameters, of which the values given here for met at   --><!-- the level of the foot ( < gi > seg1 < /gi > )            --><!-- constitute a series of local variations.  In cases       --><!-- such as this, of course, the local variations could be   --><!-- considered aspects of realization rather than            --><!-- convention, so that the real attribute could if          --><!-- desired be used instead.                                 --><!--                                                          --><!-- [Michael: I appreciate this is rather cumbersome, and    --><!-- you'll in any case have to check the tagging.  For       --><!-- simplicity I have left the caesura out of the Virgil,    --><!-- but you might feel it has to be included, in which       --><!-- case I leave the necessary encoding to you.  I am also   --><!-- not sure whether the last foot of the Virgil line is     --><!-- '+-' or '++'.  But I think there is an important point   --><!-- to be made here] (dr) ********************************   -->
 
 </p></div3><div3 name="subsection" ref="Y"><head>Metrical Analysis of Stanzaic Verse</head><p>The method described above may be used to encode quite complex verse
forms, for instance various kinds of fixed-form stanzas.  Let us take
one of Dante's canzoni, in which each stanza except the last has the
same combination of eleven-syllable and seven-syllable lines, and the
same rhyme scheme:
 
<eg><![CDATA[<div0 type=canzone
      met='E/E/S/E/S/E/E/S/E/S/E/S/S/E/S/E/E/S/S/E/E'
      rhyme="abbcdaccbdceeffghhhgg">
<lg1 n=1 type=stanza>
<l n=1>Doglia mi reca nello core ardire
  <!-- ... -->]]></eg><!-- ref needed: D Robey says any book on Dante will provide one  -->
 </p><p>Here the <att tei="yes">met</att> attribute specifies a metrical pattern for
each of the twenty-one lines making up a stanza of the
<term>canzone</term>.  Each stanza inherits this definition from the
parent <gi tei="yes">div0</gi> element.  The <att tei="yes">rhyme</att> attribute specifies
a rhyme scheme for each stanza, in the same way.
 </p><p>In the metrical notation used here, the letter <code tei="yes" type="val">E</code>
represents a line containing nine syllables which may or may not be
metrically prominent, a tenth which is prominent and an optional
non-prominent eleventh syllable.  The letter <q>S</q> is used to
represent a line containing five syllables which may or may not be
metrically prominent, a sixth which is prominent and an optional
non-prominent seventh syllable.  A suitable definition for this
notation might be given by a <gi tei="yes">metDecl</gi> element like the
following:
 
<eg><![CDATA[<metDecl type='met' pattern='((E|S)/)+)'>
  <symbol value='E' terminal=n>xxxxxxxxx+o
  <symbol value='S' terminal=n>xxxxx+o
  <symbol value='x'>metrically prominent or non-prominent
  <symbol value='+'>metrically prominent
  <symbol value='o'>optional non prominent
  <symbol value='/'>line division
</metDecl>]]></eg>
 </p><p>As noted above, the metrical pattern specified on the <gi tei="yes">div0</gi>
applies to each <gi tei="yes">lg</gi> (stanza) element contained within the
<gi tei="yes">div0</gi>.  In fact however, after seven stanzas of this type, there
is a final stanza, known as a <term>commiato</term> or envoi, which
follows a different metrical and rhyming scheme.  The solution to this
problem is simply to specify a new <att tei="yes">met</att> attribute on the
eighth stanza itself, which will override the default value inherited
from parent <gi tei="yes">div0</gi>, as follows:
 
<eg><![CDATA[  <div0 met='.....'>
  <!-- ... -->
  <lg1>
    <!-- This line group inherits its met value -->
    <!-- from the containing <div0>             -->
    <l> ...
  </lg1>
  <lg1 type='commiato'
      met='E/S/S/E/S/E/E/S/S/E/E'
      rhyme="abbccdeeedd">
    <l n=1> Canzone, presso di qui
     <!-- ... -->
  </lg1>
  </div0>]]></eg>
 </p><p>Note that, in the same way as for the <att tei="yes">real</att> attribute,
over-riding of this kind does not affect subsequent elements at the same
hierarchic level.  Any <gi tei="yes">lg1</gi> element following the
<term>commiato</term> above would be assumed to use the same metrical
and rhyming scheme as the one preceding the <term>commiato</term>.
Moreover, although it is quite regular (in the sense that the last
stanza of each <term>canzone</term> is a <term>commiato</term>), the
over-riding must be specified for each case.
 </p></div3></div2><div2 id="VERH" name="section" ref="Y"><head>Rhyme</head><p>The <att tei="yes">rhyme</att> attribute is used to specify the rhyme pattern
of a verse form.  Like the <att tei="yes">met</att> attribute, it can be used with
a user-specified notation documented by the <gi tei="yes">metDecl</gi> element
in the TEI header.  Unlike <att tei="yes">met</att>, however, the <att tei="yes">rhyme</att>
attribute has a default notation; if this default notation is used, no
<gi tei="yes">metDecl</gi> element need be given.
 </p><p>The default notation for rhyme offers the ability to record
patterns of rhyming lines, using the traditional notation in which
distinct letters stand for rhyming lines.  For a work in rhyming
couplets, like the Pope example above, the <att tei="yes">rhyme</att> attribute
simply specifies <code tei="yes" type="val">aa</code>, indicating that pairs of adjacent
lines rhyme with each other.  For a slightly more complex scheme,
applicable to groups of four lines, in which lines 1 and 3 rhyme, as
do lines 2 and 4, this attribute would have the value
<code tei="yes" type="val">abab</code>.  The traditional Spenserian stanza has the pattern
<code tei="yes" type="val">ababbcbcc</code>, indicating that within each nine line stanza,
lines 1 and 3 rhyme with each other, as do lines 2, 4, 5 and 7, and
lines 6, 8 and 9.
 </p><p>Non-rhyming lines within such a group may be represented using a
hyphen or an x, as in the following example:
 
<eg><![CDATA[<lg rhyme='AB-BBA'>
<l>The sunlight on the garden
<l>Hardens and grows cold,
<l>We cannot cage the minute
<l>Within its nets of gold
<l>When all is told
<l>We cannot beg for pardon.
</lg>]]></eg><!-- from Louis MacNeice, Collected Poems, ed Dodds (1966)  -->
 
Note however that the default notation includes no specific way of
recording <soCalled>internal</soCalled> rhyme, such as that between the
end of the first line and the start of the second in this particular
poem.  For this, a special user-defined notation would need to be
declared using the <gi tei="yes">metDecl</gi> element in the header.
Alternatively, rhyme, like alliteration or assonance, may be considered
as a special form of <soCalled>correspondence</soCalled>, and hence
encoded using the mechanisms defined for that purpose in section <xref target="SACS"/>.
 </p><p>To use the correspondence mechanisms to represent the complex rhyming
pattern of the above example, we first need to delimit and identify each
rhyming sequence within the text:  the <gi tei="yes">seg</gi> element may be used
for this purpose, as follows:
 
<eg><![CDATA[<lg rhyme='AB-BBA'>
<l>The sunlight on the <seg id=A1>garden</seg>
<l><seg id=A2>Harden</seg>s and grows <seg id=B1>cold,</seg>
<l>We cannot cage the <seg id=C1>minute</seg>
<l>Wi<seg id=C2>thin it</seg>s nets of <seg id=B2>gold</seg>
<l>When all is <seg id=B3>told</seg>
<l>We cannot beg for <seg id=A3>pardon</seg>.
</lg>
 ]]></eg>
 
Now that each rhyming word, or part-word, has been tagged and allocated
an arbitrary identifier, the general purpose <gi tei="yes">link</gi> element may
be used to indicate which of the <gi tei="yes">seg</gi> elements share the same
rhyme, as follows:
 
<eg><![CDATA[ 
<linkGrp type=rhyme>
<link targets='A1 A2 A3'>
<link targets='B1 B2 B3'>
<link targets='C1 C2'>
</linkGrp>
 ]]></eg>
 </p><p>For further discussion of the <gi tei="yes">link</gi> and <gi tei="yes">linkGrp</gi>
element, see section <xref target="SACS"/>.
 </p></div2><div2 id="VEETC" name="section" ref="Y"><head>Encoding Procedures For Other Verse Features</head><p>A number of procedures that may be of particular concern to encoders
of verse texts are dealt with elsewhere in these guidelines.  Some
aspects of layout and physical appearance, especially important in the
case of free verse, are dealt with in chapter <xref target="PH"/>.  Some
initial recommendations for the encoding of phonetic or prosodic
transcripts, which may be helpful in the analysis of sound structures in
poetry, are to be found in chapter <xref target="TS"/>; it may also be
found convenient to use standard entity names (those proposed for the
International Phonetic Alphabet suggest themselves) to mark positions of
suprasegmentals such as primary and secondary stress, or other aspects
of accentual structure.
 </p><p>As already indicated, chapter <xref target="SA"/> contains much which
will be found useful for the aligning of multiple levels of commentary
and structure within verse analysis.  Encoders of verse (as of other
types of literary text) will frequently wish to attach identifying
labels to portions of text that are not part of a system of hierarchical
divisions, may overlap with one another, and/or may be discontinuous;
for instance passages associated with particular characters, themes,
images, allusions, topoi, styles, or modes of narration.  Much of the
computerized analysis of verse seems likely to require dividing texts up
into blocks in this way.  The <gi tei="yes">span</gi> element discussed in <xref target="AISP"/> provides the means for doing this.  Finally, the
procedures for the tagging of feature structures, described in chapter<xref target="FS"/>
, provide a powerful means of encoding a wide variety of
aspects of verse literature, including not only the metrical structures
discussed above, but also such stylistic and rhetorical features as
metaphor.
 </p><p>For other features it must for the time being be left to encoders to
devise their own terminology.  Elements such as <tag compl="full" tei="yes">metaphor tenor= ...
vehicle= ...</tag> ...  <tag compl="full" tei="yes">/metaphor</tag> might well suggest
themselves; but given the problems of definition involved, and the great
richness of modern metaphor theory, it is clear that any such format, if
pre-defined by these Guidelines, would have seemed objectionable to some
and excessively restrictive to many.  Leaving the choice of tagging
terminology to individual encoders carries with it one vital corollary,
however:  the encoder must be utterly explicit, in the TEI header, about
the methods of tagging used and the criteria and definitions on which
they rest.  Where no formal elements are currently proposed, such
information may readily be given as simple prose description within the
<gi tei="yes">encodingDesc</gi> element defined in section <xref target="HD5"/>.<?tei:EOF p2veme.odd ??>
</p></div2></div1><!-- &hdmn  included here pro tem --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ve.odd ??><!-- 9 Verse --><?tei:SOF p2dr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2dr.odd,v $
    * Revision 1.11  1998/02/01 16:18:53  tei
    * change system to public identifier (again)
    *
    * Revision 1.10  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.9  94/04/01  16:20:38  msmcq
    * Changes to class declarations and teistr reference
    * --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : protect teistr                          --><!-- 94-03-31 : MSM : define drmix                            --><!-- 94-03-30 : MSM : suppress declaration of perf cla (=comp.drama) --><!-- 94-03-29 : MSM : declare comp.drama                      --><!-- 93-08-20 : MSM : cosmetology                             --><!-- 93-08-19 : MSM : add def and ref to teistr               --><!-- 93-08-19 : MSM : add class stagedir                      --><!-- 93-08-16 : MSM : cosmetic fixes                          --><!-- 93-08-16 : MSM : suppress ref to dDRcast                 --><!-- 93-06-03 : MSM : add refs to div2 elements               --><!-- 21 May : replaced this file from P2X version     --><!-- 2 May 93 : rewrote section on front; splitup       --><!-- 28 Apr 93: further changes following discussion w JL --><!--          speech -> sp                  --><!--          removed section on header for now         --><!-- 18 jan: checked IDs and reformat --><div1 id="DR" n="10" name="chapter" ref="Y"><head>Base Tag Set for Drama</head><p>This base tag set is intended for use when encoding printed dramatic
texts, screen plays or radio scripts, and written transcriptions of any
form of performance.
 <!-- Because its chief focus is on the high level structural  --><!-- features of such texts, the spoken text base tag set     --><!-- described in chapter < xref target=TS > may be more      --><!-- appropriate if an encoder wishes to focus on the         --><!-- temporal and speech based aspects of a dramatic          --><!-- performance.                                             --></p><p>Section <xref target="DRFAB"/> discusses elements, such as cast lists,
which can appear only in the front or back matter of printed dramatic
texts.  Section <xref target="DRBOD"/> discusses the structural
components of performance texts: these include major structural
divisions such as acts or scenes (section <xref target="DRDIV"/>);
individual speeches (section <xref target="DRSP"/>); stage directions
(section <xref target="DRSTA"/>); and the elements making up individual
speeches (section <xref target="DRPAL"/>).  Section <xref target="DREMB"/>
discusses ways of encoding units which cross the simple hierarchic
structure so far defined, such as embedded songs or other masques.
Finally, section <xref target="DROTH"/> discusses a small number of
additional elements characteristic of screen plays and radio or
television scripts, as well as some elements for representing
technical stage directions such as lighting or blocking.</p><p>To enable the base tag set for performance texts, the parameter
entity <term>TEI.drama</term> must be declared within the document
type subset with the value <code lang="sgml" tei="yes" type="frag">INCLUDE</code>, as further
described in section <xref target="STIN"/>.  A document using the base
tag set for drama and no additional tag sets will thus begin as
follows:
 
<eg><![CDATA[<!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
<!ENTITY % TEI.drama 'INCLUDE' >
]>]]></eg>
 
This declaration makes available all of the elements described in this
chapter, in addition to the core elements described in chapter <xref target="CO"/>.  The default structure for dramatic texts is similar to that
defined by chapter <xref target="DS"/>, as further discussed in section<xref target="DRDIV"/>
.</p><p>Three additional element classes are defined by this base tag set.
The <term>dramafront</term> class contains elements which can
appear only in the front or back matter of performance texts.
The <term>stageDirection</term> class contains a set of elements
for specialized stage directions, which can occur between or within
speeches.
The <term>comp.drama</term> class contains all elements which may appear
as components of performance texts, in addition to those defined in the
core.
The classes are defined using parameter entities as shown below:
 
<dtdFrag id="DDRCLA" n="Class declarations for Performance Texts" file="teidram2.ent"><claDecl classDoc="DRFRONT" type="model"/><claDecl classDoc="STAGEDIR" type="model"/><claDecl classDoc="COMPDRAM" type="model"/><entDecl entDoc="DRMIX"/></dtdFrag><!-- <claDecl type=model classDoc=PERF>                       -->
 
The remainder of the DTD fragment defining the base tag set for drama
has the following overall shape:
 
<dtdFrag id="DDR" n="Base tag set for Performance texts" file="teidram2"><dtdRef dtdFrag="DDRFAB"/><dtdRef dtdFrag="DDRSTA"/><dtdRef dtdFrag="DDROTH"/><commDecl>The base tag set for drama uses the standard default
text-structure elements, which are embedded here:</commDecl><msection keywords="%TEI.singleBase"><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></msection></dtdFrag></p><?tei:SOF p2drfab.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2drfab.odd,v $
# Revision 1.10  1998/01/28  11:44:14  cmsmcq
# LB changes of Jan 1998 and RCS keywords added.
#
    *--><!-- Revisions:                                               --><!-- 11 jan 98 : LB : tidy up egs --><!-- 93-08-20 : MSM : cosmetics                               --><!-- 93-08-19 : MSM : clean Peer Gynt title page (typo)       --><!--                  (and titlePart missing)                 --><!--                  close date in Godot performance element --><!-- 93-08-16 : MSM : last-minute tweaks                      --><!-- 93-08-16 : MSM : clean ID problem on dDRcast             --><div2 id="DRFAB" name="section" ref="Y"><head>Front and Back Matter
 </head><p>In dramatic texts, as in all TEI conformant documents, the header
element is followed by a <gi tei="yes">text</gi> element, which contains optional
front and back matter, and either a <gi tei="yes">body</gi> or else a
<gi tei="yes">group</gi> of nested <gi tei="yes">text</gi> elements.  For more information
on these, see chapter <xref target="DS"/>.
 </p><p>The <gi tei="yes">front</gi> and <gi tei="yes">back</gi> elements are most likely to be
of use when encoding preliminary materials in published performance
texts.  These often contain specific textual elements not generally
found in other forms of text.  These include:
 
<tagList style="one-line"><tagDesc tagDoc="PERFORM"/><tagDesc tagDoc="PROLOGUE"/><tagDesc tagDoc="EPILOGUE"/><tagDesc tagDoc="SET"/><tagDesc tagDoc="CASTLIST"/></tagList>
 </p><p>Elements for encoding each of these specific kinds of front matter
are discussed in the remainder of this section, in the order given
above.  In addition, the front matter of dramatic texts may include the
same elements as that of any other kind of text, notably title pages and
various kinds of text division, as discussed in section<xref target="DSFRONT"/>
.  The encoder may choose to ignore the
specialized elements discussed in this section and instead use
constructions of the type <tag compl="full" tei="yes">div type=performance</tag> or
<tag compl="full" tei="yes">div1 type=set</tag>.
 </p><p>Most other material in the front matter of a performance text will be
marked with the default text structure elements described in chapter<xref target="DS"/>
.  For example, the title
page, dedication, other commendatory material, preface, etc., in a
printed text should be encoded using <gi tei="yes">div</gi> or <gi tei="yes">div1</gi>
elements, containing headings, paragraphs, and other core tags.
 </p><p>The specialized elements for front and back matter of performance
texts are defined as follows:
 
<dtdFrag id="DDRFAB" n="Specialized front and back matter for performance texts"><dtdRef dtdFrag="DDRSET"/><dtdRef dtdFrag="DDRPRO"/><dtdRef dtdFrag="DDRPERF"/><dtdRef dtdFrag="DDRCAST"/></dtdFrag>
 </p><div3 id="DRSET" name="subsection" ref="Y"><head>The Set Element</head><p>A special form of note describing the setting of a dramatic text
(that is, the time and place of its action) is sometimes found in the
front matter.
 
<tagList style="one-line"><tagDesc tagDoc="SET"/></tagList>
 
Descriptions of the setting may also appear as initial stage directions
in the body of the play, but such descriptions should be marked as stage
directions, not <gi tei="yes">set</gi>.  The <gi tei="yes">set</gi> element should be used
only where the description forms part of the front matter, as in the
following examples:
 
<eg><![CDATA[<front>
  <castList>
   <castItem>  <!-- ... --> </castItem>
  </castList>
  <set>The action of the play is set in Chicago's
       Southside, sometime between World War II and the
       present.</set>
</front>]]></eg>
 
<eg rend="skel"><![CDATA[<front>
  <titlePage> ... </titlePage>
  <div type='copyright page'> ... </div>
  <div type='Contents'> ... </div>
  <div type='Introduction'> ... </div>
  <div type=''><head>Note on the Translation</head> <!--...--> </div>
  <titlePage type='half-title'>
  <docTitle><titlePart>Peer Gynt</></docTitle>
  </titlePage>
  <div type='Dramatis Personae'><head>Characters</> <!--...--> </div>
  <set>The action, which opens in the early years of the
       last century and closes about fifty years later,
       takes place partly in the Gudbrand Valley in Norway
       and on the mountains around it, partly on the
       Moroccan coast, partly in the Sahara Desert,
       the asylum in Cairo, at sea, etc.</set>
   <performance> <!-- ...  --> </performance>
</front>]]></eg>
 </p><p>The <gi tei="yes">set</gi> element is formally defined as follows:
 
<dtdFrag id="DDRSET" n="The Set element"><tagDecl tagDoc="SET"/></dtdFrag>
 </p></div3><div3 id="DRPRO" name="subsection" ref="Y"><head>Prologues and Epilogues</head><p>Many plays in the Western tradition include in their front matter a
prologue, spoken by an actor, generally not in character.  Similar
speeches often also occur at the end of the play, as epilogues.  The
elements <gi tei="yes">prologue</gi> and <gi tei="yes">epilogue</gi> are provided for the
encoding of such features within the front or back matter, where
appropriate.
 
<tagList style="one-line"><tagDesc tagDoc="PROLOGUE"/><tagDesc tagDoc="EPILOGUE"/></tagList>
 
A prologue may be encoded just like a distinct poem, as in the following
example:
 
<eg><![CDATA[<front>
<prologue>
<head>Prologue, spoken by <name>Mr. Hart</name></head>
<l>Poets like Cudgel'd Bullys, never do
<l>At first, or second blow, submit to you;
<l>But will provoke you still, and ne're have done,
<l>Till you are weary first, with laying on:
<!-- ... -->
<l>We patiently you see, give up to you,
<l>Our Poets, Virgins, nay our Matrons too.
</prologue>
<castList>
<head>The Persons</head>
   <castItem>  <!-- ... --> </castItem>
</castList>
<set><head>The SCENE</>
London</set>
</front>]]></eg><!-- Wycherley, Country Wife, 1675 -->
 </p><p>A prologue or epilogue may also be encoded as a speech, using the
<gi tei="yes">sp</gi> element described in section <xref target="CODR"/>.  This is
particularly appropriate where stage directions, etc., are involved, as
in the following example:
 
<eg><![CDATA[<epilogue>
<head>Written by <name>Colley Cibber, Esq</name>
and spoken by <name>Mrs. Cibber</name></head>
<sp>
<lg type=stanza>
<l>Since Fate has robb'd me of the hapless Youth,</l>
<l>For whom my heart had hoarded up its truth;</l>
<l>By all the Laws of Love and Honour, now,</l>
<l>I'm free again to chuse, &mdash; and one of you</l>
</lg>
<!-- ... -->
<lg>
<l>Suppose I search the sober Gallery; &mdash; No,</l>
<l>There's none but Prentices &mdash; &amp; Cuckolds all a row:</l>
<l>And these, I doubt, are those that make 'em so.</l></lg>
<stage>Pointing to the Boxes.</stage>
<lg>
<l>'Tis very well, enjoy the jest:</l>
<!-- ... -->
</sp>
</epilogue>]]></eg><!-- G. Lillo, The London Merchant  (1731) -->
 </p><p>In cases where the prologue or epilogue is clearly a significant part
of the dramatic action, it may be preferable to include it in the body
of a text, rather than in the front or back matter.  In such cases, the
encoder (and theatrical tradition) will determine whether or not to
regard it as a new scene or division, or simply the final speech in the
play.  In the First Folio version of Shakespeare's
<title>Tempest</title>, for example, Prospero's final speech is clearly
marked off as a distinct textual unit by the headings and layout of the
page, and might therefore be encoded as back matter:
 
<eg><![CDATA[<body>
<div1 type=scene>
<!-- ... -->
<sp who=PR>
<l part=y>I'le deliver all,</l>
<l>And promise you calme Seas, auspicious gales,</l>
<!-- ... -->
<l>Be free and fare thou well: please you, draw neere.</l>
<stage>Exeunt omnes.</stage>
</div1>
</body>
<back>
<epilogue>
<head>Epilogue, spoken by Prospero.</head>
<sp>
<l>Now my Charmes are all ore-throwne,</l>
<l>And what strength I have's mine owne</l>
<!-- ... -->
<l>As you from crimes would pardon'd be,</l>
<l>Let your Indulgence set me free.</l></sp>
<stage>Exit</stage>
</epilogue>

<set>The Scene, an un-inhabited Island.</set>

<castList>
<head>Names of the Actors.</head>
<castItem>Alonso, K. of Naples</castItem>
<castItem>Sebastian, his Brother.</castItem>
<castItem>Prospero, the right Duke of Millaine.</castItem>
<!-- ... -->
</castList>
<!-- <trailer>FINIS</trailer> -->
</back>
]]></eg><!-- The Tempest, first folio -->
 </p><p>In many more modern editions, the editors have chosen to regard
Prospero's speech as a part of the preceding scene:
 
<eg><![CDATA[<sp who=PR><speaker>Prospero</speaker>
<l part=y>I'll deliver all,</l>
<l>And promise you calm seas, auspicious gales,</l>
<!-- ... -->
<l>Be free and fare thou well. <stage>Exit Ariel</stage>
Please you, draw near.
<stage>Exeunt all but Prospero</stage>
<note place=margin>Epilogue</note></l>
<l>Now my charms are all o'erthrown,</l>
<l>And what strength I have's mine own</l>
<!-- ... -->
<l>As you from crimes would pardoned be,</l>
<l>Let your indulgence set me free.</l>
</sp>
<stage>He awaits applause, then exit.</stage>]]><!-- Wells and Taylor OUP 1986 --></eg><!-- In nearly every example I have looked at, the prologue --><!-- precedes the dramatis personae.   (LB) -->
 </p><p>Prologues and epilogues are formally defined as follows:
 
<dtdFrag id="DDRPRO" n="Prologues and Epilogues"><tagDecl tagDoc="PROLOGUE"/><tagDecl tagDoc="EPILOGUE"/></dtdFrag>
 </p></div3><div3 id="DRPERF" name="subsection" ref="Y"><head>Records of Performances</head><p>Performance texts are not only printed in books to be read, they are
also performed.  It is common practice therefore to include within the
front matter of a printed dramatic text some brief account of particular
performances, using the following element:
 
<tagList style="one-line"><tagDesc tagDoc="PERFORM"/></tagList>
 
The <gi tei="yes">performance</gi> element may be used to group any and all
information relating to the actual performance of a play or screenplay,
whether it specifies how the play should be performed in general or how
it was performed in practice on some occasion.
 </p><p>Performance information may include complex structures such as cast
lists, or paragraphs describing the date and location of a performance,
details about the setting portrayed in the performance and so forth.
(See the discussion of these specialized structures in section <xref target="DRFAB"/> above.)  If
information for more than one performance is being recorded, then more
than one <gi tei="yes">performance</gi> element should be used.
 </p><p>Names of persons, places, and dates of particular significance within
the performance record may be explicitly marked using the general
purpose <gi tei="yes">name</gi>, <tag compl="full" tei="yes">rs type=place</tag> and <gi tei="yes">date</gi>
elements described in section <xref target="CONADA"/>.<!-- ; the more detailed tagging for names and dates defined by --><!-- chapter  <xref target=ND> may also be employed. -->
No particular elements for such features as theatres,
directors, etc., are proposed at this time.
 </p><p>For example:
 
<eg><![CDATA[<performance>
<head>Death of a Salesman</head>
<p>A New Play by Arthur Miller</>
<p>Staged by Elia Kazan</>
<castList>
<head>Cast</head>
<note place='inline' rend='small type flush left'>
(in order of appearance)
</note>
<castItem><role>Willy Loman</> <actor>Lee J. Cobb</></>
<castItem><role>Linda</>       <actor>Mildred Dunnock</></>
<castItem><role>Biff</>        <actor>Arthur Kennedy</></>
<castItem><role>Happy</>       <actor>Cameron Mitchell</></>
<!-- ... -->
</castList>
<p>The setting and lighting were designed by <name>Jo Mielziner</>.
<p>The incidental music was composed by <name>Alex North</>.
<p>The costumes were designed by <name>Julia Sze</>.
<p>Presented by <name rend=unmarked>Kermit Bloomgarden</> and
<name rend=unmarked>Walter Fried</> at the <rs type=place>Morosco
Theatre in New York</> on <date>February 10, 1949</>.
</performance>]]></eg><!-- N.B. first two 'p' elements might also be BYLINE?        --><!-- NOTE could be part of title (but is clearly marked by    --><!-- typography as distinct segment ...)                      --><!-- Last series of P elements could be LIST TYPE=SIMPLE      --><!-- -msm                                                     -->
 
Or:
 
<eg><![CDATA[<performance>
<p>La Machine Infernale a &eacute;t&eacute;
repr&eacute;sent&eacute;e pour la premi&egrave;re fois au
<rs type='place (theatre)'>th&eacute;&acirc;tre Louis-Jouvet</rs>
<rs type='place (theatre)'>(Com&eacute;die des
Champs-&Eacute;lys&eacute;es)</rs>
<date>le 10 avril 1934</date>,
avec les d&eacute;cors et les costumes de
<name>Christian B&eacute;rard.</name>
<!-- ... -->
</performance>]]></eg><!-- La Machine Infernale, Jean Cocteau -->
 </p><p>The <gi tei="yes">performance</gi> element is formally defined as follows:
 
<dtdFrag id="DDRPERF" n="The Performance element"><tagDecl tagDoc="PERFORM"/></dtdFrag>
 </p></div3><div3 id="DRCAST" name="subsection" ref="Y"><head>Cast Lists</head><p>A <term>cast list</term> is a specialized form of list,
conventionally found at the start or end of a play, usually listing all
the speaking and non-speaking roles in the play, often with additional
description (<q>Cataplasma, a maker of Periwigges and Attires</q>) or
the name of an actor or actress (<q>Old Lady Squeamish. Mrs
Rutter</q>).  Cast lists may be encoded with the general purpose
<gi tei="yes">list</gi> element described in section <xref target="COLI"/>, but for
more detailed work the following specialized elements are provided:
 
<tagList style="one-line"><tagDesc tagDoc="CASTLIST"/><tagDesc tagDoc="CASTGRP"/><tagDesc tagDoc="CASTITEM" atts="type"/><tagDesc tagDoc="DRROLE"/><tagDesc tagDoc="ROLEDESC"/><tagDesc tagDoc="ACTOR"/></tagList>
 
Cast lists often have an internal structure of their own; it is quite
usual to find, for example, nobility and commoners, or male and female
roles, presented in different groups or sublists.  Roles are also often
grouped together by their function, for example:
 
<list type="simple"><item>Sons of Cato:
<list type="simple"><item>Portius</item><item>Marcus</item></list></item></list>
 </p><p>A cast list relating to a specific performance may be accompanied by
notes about the time or place of that performance, indicating (for
example) the name of the theatre where the play was first presented, the
name of the producer or director, and so forth.  When the cast list
relates to a specific performance, it should be embedded within a
<gi tei="yes">performance</gi> element (see section <xref target="DRPERF"/>), as in
the following example:
 
<eg><![CDATA[<performance>
  <p>The first performance in Great Britain of <title>Waiting for
Godot</title> was given at the Arts Theatre, London, on
<date>3rd August 1955</>. It was directed by <name>Peter Hall</name>,
and the d&eacute;cor was by <name>Peter Snow</name>. The cast
was as follows:</p>
<castList>
   <castItem>Estragon: Peter Woodthorpe
   <castItem>Vladimir: Paul Daneman
   <!--   ... -->
  </castList>
</performance>]]></eg><!-- S Beckett, W for G, Faber, 1956 -->
 </p><p>In this example, the <gi tei="yes">castItem</gi> elements have no substructure.
If desired, however, their components may be more finely distinguished
using the elements <gi tei="yes">role</gi>, <gi tei="yes">roleDesc</gi>, and <gi tei="yes">actor</gi>.
For example, the first cast item above might be encoded as follows:
 
<eg><![CDATA[   <castItem>
     <role id=VLAD>Vladimir</role>:
     <actor>Paul Daneman</actor>
   </castItem>]]></eg>
 </p><p>The global <att tei="yes">id</att> attribute may be used to specify a unique
identifier for the <gi tei="yes">role</gi> element, where it is desired to link
speeches within the text explicitly to the role, using the
<att tei="yes">who</att> attribute, as further discussed in section <xref target="DRSP"/> below.
 </p><p>The occasionally lengthy descriptions of a role sometimes found in
written play scripts may be marked using the <gi tei="yes">roleDesc</gi> element,
as in the following example:
 
<eg><![CDATA[ <castItem>
 <role>Tom Thumb the Great</role>
 <roleDesc>a little hero with a great soul, something
  violent in his temper, which is a little abated
  by his love for Huncamunca</roleDesc>
 <actor>Young Verhuyk</actor>
 </castItem>]]></eg><!-- Fielding, Tragedy of Tragedies (1737) -->
 
For non-speaking or un-named roles, a <gi tei="yes">castItem</gi> may contain a
<gi tei="yes">roleDesc</gi> without an accompanying <gi tei="yes">role</gi>, for example
 
<eg><![CDATA[ <castItem>
  <roleDesc>Costermonger</roleDesc>
 </castItem>]]></eg>
 </p><p>When a list of such minor roles is given together, the
<att tei="yes">type</att> attribute of the <gi tei="yes">castItem</gi> should indicate that
it contains more than one role.  The encoder may or may not elect to
encode each separate constituent within such a composite
<gi tei="yes">castItem</gi>.  Thus, either of the following is acceptable:
 
<eg><![CDATA[  <castItem type=list>Constables, Drawer, Turnkey,  etc.</castItem>
 
  <castItem type=list>
     <roleDesc>Constables,</roleDesc>
     <roleDesc>Drawer,</roleDesc>
     <roleDesc>Turnkey,</roleDesc>
     etc.
   </castItem>]]></eg>
 </p><p>A group of cast items forming a distinct subdivision of a cast list
may be marked as such by using the special purpose <gi tei="yes">castGroup</gi>
element.  The <att tei="yes">rend</att> attribute should be used to indicate
whether this grouping is indicated in the text by layout alone (i.e. the
use of whitespace), by long braces or by some other means.  A
<gi tei="yes">castGroup</gi> consists of an optional heading (represented as
usual by a <gi tei="yes">head</gi> element) followed by a series of
<gi tei="yes">castItem</gi> elements.
 
<eg><![CDATA[ <castGroup rend=braced><head>friends of Mathias</head>
    <castItem>
        <role>Walter</role><actor>Mr Frank Hall</actor>
    </castItem>
    <castItem>
       <role>Hans</role><actor>Mr F.W. Irish</actor>
    </castItem>
 </castGroup>]]></eg><!-- Leopold Lewis, The Bells (1871) -->
 </p><p>The following example demonstrates the use of the <gi tei="yes">castGroup</gi>
element to structure the whole of a <gi tei="yes">castList</gi>, reflecting the
way it is presented on the page:
 
<eg><![CDATA[<castList>
<castGroup>
  <head rend=braced>Mendicants</head>
  <castItem><role>Aafaa</>   <actor>Femi Johnson</></>
  <castItem><role>Blindman</><actor>Femi Osofisan</></>
  <castItem><role>Goyi</>    <actor>Wale Ogunyemi</></>
  <castItem><role>Cripple</> <actor>Tunji Oyelana</></>
</castGroup>
<castItem><role>Si Bero</>
          <roleDesc>Sister to Dr Bero</>
          <actor>Deolo Adedoyin</></>
<castGroup>
  <head rend=braced>Two old women</head>
  <castItem><role>Iya Agba</><actor>Nguba Agolia</></>
  <castItem><role>Iya Mate</><actor>Bopo George</></>
</castGroup>
<castItem><role>Dr Bero</>
          <roleDesc>Specialist</>
          <actor>Nat Okoro</></>
<castItem><role>Priest</>
          <actor>Gbenga Sonuga</></>
<castItem><role>The old man</>
          <roleDesc>Bero's father</>
          <actor>Dapo Adelugba</></>
</castList>]]></eg><!-- Soyinka, Madmen and Specialists, Methuen 1971 -->
 </p><p>The <gi tei="yes">castList</gi> element and its components have the following
formal definitions:
 
<dtdFrag id="DDRCAST" n="The cast list"><tagDecl tagDoc="CASTLIST"/><tagDecl tagDoc="CASTGRP"/><tagDecl tagDoc="CASTITEM"/><tagDecl tagDoc="DRROLE"/><tagDecl tagDoc="ROLEDESC"/><tagDecl tagDoc="ACTOR"/></dtdFrag><?tei:EOF p2drfab.odd ??><?tei:SOF p2drbod.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2drbod.odd,v $
    * Revision 1.13  1998/02/01 16:18:53  tei
    * change system to public identifier (again)
    *
    * Revision 1.12  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.11  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.10  1994/03/07  15:36:11  lou
    * remove ^Z
    * 
    * Revision 1.9  1994/03/07  14:50:48  lou
    * fix typos noted by DTB
    * 
    * Revision 1.8  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * --><!-- Revisions:                                               --><!-- 11 jan 98 : LB : fix egs --><!-- 9 jan: remove spurious <moves> element --><!-- 93-08-20 : MSM : correct bad typo (no tagc on tagdesc for l) --><!-- 93-08-20 : MSM : which caused lg desc to be omitted      --><!-- 93-08-20 : MSM : also cosmetic changes                   --><!-- 93-08-19 : MSM : suppress dot in qu., oph. WHO atts      --><!--                  suppress end-tags of L inside Q         --><!--                  (quick hack for mixed content problem)  --><!--                  add explicit end-tag p in O'Casey       --><!-- 93-08-19 : MSM : comment out ellipsis in Barnardo        --><!--                  change tagging in O'Casey examples      --><!-- 93-08-18 : MSM : cast list must contain cast items, not roles --><!-- 93-08-16 : MSM : last-minute tweaks                      --><!-- 93-06-02 : WP : Spellchecked, added ATT around "next".   -->
</p></div3></div2><div2 id="DRBOD" name="section" ref="Y"><head>The Body of a Performance Text</head><p>The body of a performance text may be divided into structural units,
variously called acts, scenes, stasima, entr'actes, etc.  All such
formal divisions should be encoded using an appropriate text-division
element (<gi tei="yes">div</gi>, <gi tei="yes">div1</gi>, <gi tei="yes">div2</gi>, etc.), as further


discussed in section <xref target="DRDIV"/>.  Whether divided up into such
units or not, all performance texts consist of sequences of speeches
(see <xref target="DRSP"/>) and stage directions (see <xref target="DRSTA"/>).
Speeches will generally consist of a sequence of
<term>chunk</term>-level items:  paragraphs, verse lines, stanzas, or
(in case of uncertainty as to whether something is verse or prose)
<gi tei="yes">seg</gi> elements (see <xref target="DRPAL"/>).</p><p>The boundaries of formal units such as verse lines or paragraphs do
not always coincide with speech boundaries.  Units such as songs may be
discontinuous or shared among several speakers.  As described below in
section <xref target="DREMB"/>, such fragmentation may be encoded in a
relatively simple fashion using the linkage and aggregation mechanisms
defined in chapter <xref target="SA"/>.</p><div3 id="DRDIV" name="subsection" ref="Y"><head>Major Structural Divisions</head><p>Large divisions in drama such as acts, scenes, stasima, or entr'actes
are indicated by numbered or unnumbered <gi tei="yes">div</gi> elements, as
described in section <xref target="DSDIV"/>.  The <att tei="yes">type</att> and
<att tei="yes">n</att> attributes may be used to define the type of division being
marked, and to provide a name or number for it, as in the following
example:
 
<eg><![CDATA[  <body>
    <div1 type=scene n=1>
      <head>Night&mdash;Faust's Study (i)</head>
      <!-- ... -->
    </div1>
    <div1 type=scene n=2>
      <head>Outside the City Gate</head>
      <!-- ... -->
    </div1>
  </body>]]></eg><!-- Goethe, Faust Part 1. Penguin, 1949 --></p><p>Where the largest divisions of a performance text are themselves
subdivided, most obviously in the case of plays traditionally divided
into acts and scenes, further nested text-division elements may be used,
as in this example:
 
<eg><![CDATA[<body>
  <div1 type=act n=1>
     <head>Act One</head>
     <div2 type=scene n='1'>
       <stage>Pa Ubu, Ma Ubu</stage>
       <sp><speaker>Pa Ubu</speaker><p>Pschitt!</p>
       <!-- ... -->
     </div2>
     <div2 type=scene n=2>
        <stage>A room in Pa Ubu's house, where a magnificent
        collation is set out</stage>
        <!-- ... -->
     </div2>
     <!-- ... -->
  </div1>
  <div1 type=act n=2>
    <head>Act Two</head>
    <div2 type=scene n=1>
      <head>Scene One</head>
      <!-- ... -->
    </div2>
    <div2 type=scene n=2>
      <head>Scene Two</head>
      <!-- ... -->
    </div2>
 </div1>
 <!-- ... -->
 </body>]]></eg><!-- Jarry, Ubu Plays (trans C. Connolly & S Watson-Taylor, Methuen 1968 --></p><p>In the example above, the <gi tei="yes">div2</gi> element has been used to
represent the <soCalled>French scene</soCalled> convention, (where the
entrance of each new set of characters is marked as a distinct unit in
the text) and the <gi tei="yes">div1</gi> element to represent the acts into which
the play is divided.  The elements chosen are determined only by the
hierarchic position of these units in the text as a whole.  If the text
had no acts, but only scenes, then the scenes might be represented by
<gi tei="yes">div1</gi> elements.  Equally, if a play is divided only into
<q>acts</q>, with no smaller subdivisions, then the <gi tei="yes">div1</gi>
element might be used to represent acts.  The <att tei="yes">type</att> should be
used, as above, where it is desired to make explicit the name associated
with a particular category of subdivision.</p><p>As an alternative to the use of these <soCalled>numbered</soCalled>
divisions, the encoder may represent all subdivisions with the same
element, the <soCalled>unnumbered</soCalled> <gi tei="yes">div</gi>.  The second
act in the above example would then be represented as follows:
 
<eg><![CDATA[  <div type=act n=2>
    <head>Act Two</head>
    <div type=scene n=1>
      <head>Scene One</head>
      <!-- ... -->
    </div>
    <div type=scene n=2>
      <head>Scene Two</head>
      <!-- ... -->
    </div>
 </div>]]></eg></p><p>For further discussion of the use of numbered and unnumbered
divisions, see section <xref target="DSDIV"/>.</p></div3><div3 id="DRSP" name="subsection" ref="Y"><head>Speeches and Speakers</head><p>The following elements are used to identify speeches and speakers in
a performance text:
 
<tagList style="one-line"><tagDesc tagDoc="SP" atts="who"/><tagDesc tagDoc="SPEAKER"/></tagList></p><p>As noted above, the structure of many performance texts may be
analysed as multiply hierarchic:  a scene of a verse play, for example,
may be divided into speeches and, at the same time, into verse lines.
The end of a line may or may not coincide with the end of a speech, and
vice versa.  Other structures, such as songs, may be discontinuous or
split up over several speeches.  For some purposes it will be
appropriate to regard the verse-structure as the fundamental organizing
principle of the text, and for others the speech structure; in some
cases, the choice between the two may be arbitrary.  The discussion in
the remainder of this chapter assumes that it is the speech-based
hierarchy which most prominently determines the structure of performance
texts, but the same mechanisms could be employed to encode a view of a
performance text in which individual speeches were entirely subordinate
to the formal units of prose and verse.  SGML's CONCUR feature also
allows for two (or more) such conflicting hierarchic views to be
presented in a single document.  For more detailed discussion and
examples of alternative treatments of this fundamental issue, refer to
chapter <xref target="NH"/>.</p><p>The <att tei="yes">who</att> attribute and the <gi tei="yes">speaker</gi> element are
both used to indicate the speaker or speakers of a speech, but in rather
different ways.  The <gi tei="yes">speaker</gi> element is used to encode the word
or phrase actually used within the source text to indicate the speaker:
it may contain any string or prefix, and may be thought of as a highly
specialized form of stage direction.  The value of the <att tei="yes">who</att>
attribute however is a unique code, probably made up by the transcriber,
which will unambiguously identify the character to whom the speech is
assigned.  To enforce this uniqueness, the base tag set for drama
defines the value of this attribute as IDREFS.  This means that the
codes included in it must correspond with codes which are specified
elsewhere in the document as identifiers for particular elements,
typically the <gi tei="yes">role</gi> element in the cast list where the character
is named or described, as discussed in <xref target="DRFAB"/> above.
 
<eg><![CDATA[<!-- in the front matter ... -->
<castList>
<!-- ... -->
<castItem><role id=M2>Menaechmus</></>
<castItem><role id=PEN>Peniculus</></>
<!-- ... -->
</castList>
<!-- ... -->
 
<!-- in the text ... -->
<sp who=M2><speaker>Menaechmus</speaker>
  <l>Responde, adulescens, quaeso, quid nomen tibist?</l></sp>
<sp who=Pen><speaker>Peniculus</speaker>
  <l>Etiam derides, quasi nomen non noveris?</l></sp>
<sp who=M2><speaker>Menaechmus</speaker>
  <l>Non edepol ego te, quot sciam, umquam ante hunc diem</l>
  <l>Vidi neque novi; ...</l></sp>]]></eg><!-- Plautus, Menaechmi, 498-9  --></p><p>If present, a <gi tei="yes">speaker</gi> element may only appear as the first
part of a <gi tei="yes">sp</gi> element.  The distinction between the
<gi tei="yes">speaker</gi> element and the <att tei="yes">who</att> attribute makes it
possible to encode uniformly characters whose names are not indicated in
a uniform fashion throughout the play, or characters who appear in
disguise, as in the following examples:
 
<eg><![CDATA[<castList>
  <!-- ... -->
  <castItem><role id=HH>Henry Higgins</role></castItem>
  <!-- ... -->
</castList>
<!-- ... -->
 
<!-- in the text ... -->
 
<sp who="HH">
<speaker>The Notetaker</speaker>
<p><!-- ... -->
</sp>]]></eg><!-- GB Shaw, Pygmalion --></p><p>If the speaker attributions are completely regular (and may thus be
reconstructed mechanically from the values given for the <att tei="yes">who</att>
attribute), or are of no interest for the encoder of the text (as might
be the case with editorially supplied attributions in older texts), then
the <gi tei="yes">speaker</gi> element need not be used; the former example above
then might look like this:
 
<eg><![CDATA[<!-- in the front matter ... -->
<castList>
<castItem><role id=M2>Menaechmus</></>
<castItem><role id=PEN>Peniculus</></>
<!-- ... -->
</castList>
<!-- ... -->
 
<!-- in the text ... -->
<sp who=M2 ><l>Responde, adulescens, quaeso, quid nomen tibist?</l></sp>
<sp who=Pen><l>Etiam derides, quasi nomen non noveris?</l></sp>
<sp who=M2 ><l>Non edepol ego te, quot sciam, umquam ante hunc diem</l>
            <l>Vidi neque novi; ...</l></sp>]]></eg><!-- Plautus, Menaechmi, 498-9  --></p><p>More than one IDREF may be listed as value for the <att tei="yes">who</att>
attribute if the speech is spoken by more than one person, as in the
following example:
 
<eg><![CDATA[<stage>Nano and Castrone sing</stage>
<sp who="NAN CAS">
<l>Fools, they are the only nation
<l>Worth men's envy or admiration
<!-- ... -->]]></eg><!-- Jonson, Volpone, p.14 --></p><p>The <gi tei="yes">sp</gi> and <gi tei="yes">speaker</gi> elements are both declared
within the core tag set (see section <xref target="CODV"/>).
 <!-- so we don't need this DTD frag here --><!-- dtdfrag id=DDRSP n="Speeches and Speakers" --><!-- tagdecl tagDoc=SP --><!-- tagdecl tagDoc=SPEAKER --><!-- /dtdfrag --></p></div3><div3 id="DRSTA" name="subsection" ref="Y"><head>Stage Directions</head><p>Both between and within the speeches of a written performance text,
it is normal practice to include a wide variety of descriptive
directions to indicate non-verbal action.  The following elements are
provided to represent these:
 
<tagList style="one-line"><tagDesc tagDoc="STAGE" atts="type"/><tagDesc tagDoc="MOVE" atts="who type where perf"/></tagList></p><p>A satisfactory typology of stage directions is difficult to define.
Certain basic types such as <q>entrance</q>, <q>exit</q>,
<q>setting</q>, <q>delivery</q>, are easily identified.  But the list is
not a closed one, and it is not uncommon to mix types within a single
direction.  No closed set of values for the <att tei="yes">type</att> attribute is
therefore proposed at the present time, though some suggested values are
indicated in the list below, which also indicates the range of
possibilities.
 
<eg><![CDATA[<stage type="setting">The throne descends.</stage>
<stage type="setting">Music</stage>
<stage type="entrance">Enter Husband as being thrown off 
       his horse.</stage>
<stage type="exit">Exit pursued by a bear.</stage>
<stage type="business">He quickly takes the stone out.</stage>
<stage type="delivery">To Lussurioso.</stage>
<stage type="delivery">Aside.</stage>
<stage type="delivery">Not knowing what to say.</stage>
<stage type="costume">Disguised as Ansaldo.</stage>
<stage type="location">At a window.</stage>
<stage type="novelistic">Having had enough, and embarrassed
        for the family.</stage>]]></eg></p><p>Where possible, the values used for the <att tei="yes">type</att> attribute on
<gi tei="yes">stage</gi> elements should be defined within the <gi tei="yes">tagUsage</gi>
element of the TEI header (described in section <xref target="HD57"/>).
For example:
 
<eg><![CDATA[<tagUsage gi=stage>This element is used for all stage directions,
editorial or authorial.  The TYPE attribute on this element takes
one or more of the following values:
<list type=gloss>
<label>setting</>   <item>describes the set</>
<label>blocking</>  <item>describes movement across stage,
position, etc.</>
<label>business</>  <item>describes movement other than blocking</>
<label>delivery</>  <item>describes how the line is said</>
<label>motivation</><item>describes character's emotional state
or through line</>
</list>]]></eg></p><p>The <gi tei="yes">stage</gi> element may appear both between and within
<gi tei="yes">sp</gi> elements.  It may contain a mixture of phrase level
elements, possibly combined into paragraphs, as in the following
example:
 
<eg><![CDATA[<div1 type=act n=1>
<stage type=setting><p>
Scene. &mdash A room furnished comfortably and
tastefully but not extravagantly ...
The floor is carpeted and a fire burns in the stove.
It is winter.
<p>A bell rings in the hall; shortly afterwards the
door is heard to open. Enter NORA humming a tune ...
</stage>
<sp><speaker>Nora</speaker>
<p>Hide the Christmas Tree carefully, Helen. Be sure the
children do not see it till this evening, when it is
dressed. <stage type=delivery>To the PORTER taking
out her purse</stage> How much?
</sp>]]></eg><!-- Ibsen, A Dolls House tr Sharp, EML, 1910 --></p><p>The <gi tei="yes">stage</gi> element may also be used in non-theatrical
texts, to mark sound effects or musical effects, etc., as further
discussed in section <xref target="DROTH"/>.</p><p>The <gi tei="yes">move</gi> element is intended to help overcome the fact that
the stage directions of a printed text may often not provide full
information about either the intended or the actual movement of actors
etc. on stage.  It may be used to keep track of entrances and exits in
detail, so as to know which characters are on stage at which time.  Its
attributes permit a relatively formal specification for movements of
characters, using user-defined codes to identify the characters involved
(the <att tei="yes">who</att> attribute), the direction of the movement
(<att tei="yes">type</att> attribute), and optionally which part of the stage is
involved (<att tei="yes">where</att> attribute).  For stage-historical purposes, a
<att tei="yes">perf</att> attribute is also provided; this allows the recording of
different <gi tei="yes">move</gi> elements 
as taken in different performances of the same text.</p><p>The <gi tei="yes">move</gi> element should be located at the position in the
text where the move is presumed to take place.  This will often coincide
with a stage direction, as in the following simple example:
 
<eg><![CDATA[<stage type="entrance">
  <move who=B type="enter">
  Enter Bellafront mad.
</stage>]]></eg></p><p>The <gi tei="yes">move</gi> element can however appear independently of a stage
direction, as in the following example:
 
<eg><![CDATA[<sp>
<speaker>Gent.</speaker>
<p>Neither to you, nor any one; having no witness
to confirm my speech. <move who=LM type=enter where=C>
Lo you! here she comes. This is her very guise; and,
upon my life, fast asleep.</p>]]><!-- Macbeth (arden ed) p 143 --></eg></p><p>The <gi tei="yes">stage</gi> element is defined by the core TEI tag set (see
section <xref target="CODV"/>).  The <gi tei="yes">move</gi> element is defined as
follows:
 
<dtdFrag id="DDRSTA" n="Stage directions"><commDecl>Stage is defined as part of the core.</commDecl><tagDecl tagDoc="MOVE"/></dtdFrag></p></div3><div3 id="DRPAL" name="subsection" ref="Y"><head>Speech Contents</head><p>The actual speeches of a dramatic text may be composed of running
text, which must be formally organized into paragraphs, in the case of
prose (see section <xref target="COPA"/>), verse lines or line groups in
that of verse (see section <xref target="CODV"/>), or <gi tei="yes">seg</gi>
elements, in case of doubt as to whether the material should be treated
as verse or prose.  The following elements, all of which are defined in
the core, are available for marking units of prose or verse within
speeches:
 
<tagList style="one-line"><tagDesc tagDoc="P"/><tagDesc tagDoc="LINEBR" atts="n ed"/><tagDesc tagDoc="L" atts="part"/><tagDesc tagDoc="LG"/><tagDesc tagDoc="SEG"/></tagList></p><p>As members of the class <term>metrical</term>, the elements <gi tei="yes">l</gi>
and <gi tei="yes">lg</gi> share the following attributes:
<adList classDoc="METRICAL" atts="met rhyme"/></p><p>As a member of the class <term>divn</term>, the element <gi tei="yes">lg</gi>
also bears the following attributes:
<adList classDoc="DIVN" atts="part type"/></p><p>In many texts, prose and verse may be inextricably mingled;
particularly in earlier printed texts, prose may be printed as verse or
verse as prose, or it may be impossible to distinguish the two.  In
cases of doubt, an encoder may prefer to tag the dubious material
consistently as verse, to tag it all as prose, to follow the typography
of the source text, or to use the neutral <gi tei="yes">seg</gi>
element to contain the speech itself.  When this question arises, the
<gi tei="yes">tagUsage</gi> element in the <gi tei="yes">encodingDesc</gi> element of the
header should be used to record explicitly what policy has been adopted.</p><p>The <att tei="yes">part</att> attribute of the <gi tei="yes">l</gi> and <gi tei="yes">lg</gi>
elements provides one simple way of indicating where the boundaries of a
speech and of a verse line or line group do not coincide.  The encoder
may simply indicate that a line or line group is incomplete by
specifying the value <code tei="yes" type="frag">Y</code> or <code tei="yes" type="frag">N</code>, as in the following example:
 
<eg><![CDATA[<sp who=VOLP>
<!-- ... -->
<l part=Y>Now, now my clients
<l>Begin their visitation! Vulture, kite,
<l>Raven, and gorcrow, all my birds of prey,
<l>That think me turning carcase, now they come:
<l part=Y>I am not for 'em yet.
<stage>Re-enter MOSCA with the gown, etc.</stage>
<l part=Y>How now? the news?
</sp>]]></eg><!-- Jonson, Volpone, I.1 177ff (ed Bamborough, p 15) --><!-- why not just embed the STAGE in the L? -msm --></p><p>Alternatively, where the fragments of the line or line group are
consecutive in the text (though possibly interrupted by stage
directions), the values <code tei="yes" type="frag">i</code> (initial), <code tei="yes" type="frag">m</code> (medial) and
<code tei="yes" type="frag">f</code> (final) may be used:
 <!-- or first, medial and last? -->
<eg><![CDATA[<sp who='Barnardo'> <!-- ... -->
 <l>If you do meet Horatio and Marcellus,</l>
 <l>The rivals of my watch, bid them make haste.</l></sp>
<stage>Enter Horatio and Marcellus.</>
<sp who='Francisco'>
 <l>I think I hear them. &mdash; Stand! Who's there?</l>
<sp who='Horatio'>
 <l part=i>Friends to this ground.</l>
<sp who='Marcellus'>
 <l part=f>And liegemen to the Dane.</l>
<!-- ... -->]]></eg></p><p>In dramatic texts, the <gi tei="yes">lg</gi> or line group element is most
often of use for the encoding of songs and other stanzaic material, as
further discussed in the next section.  Line groups may be fragmented
across speakers in the same way as individual lines, and the same set of
attributes is available to record this fact.  In the following example,
a <gi tei="yes">lg</gi> element is used to represent one verse of a song, which is
divided between several voices:
 
<eg><![CDATA[<stage type=head>Song &mdash Sir Joseph</stage>
<sp who=JOPO>
<lg part=I>
<l>I am the monarch of the sea,
<l>The ruler of the Queen's Navee.
<l>Whose praise Great Britain loudly chants.
</lg></sp>
<sp who=HE><speaker>Cousin Hebe</speaker>
<lg part=M>
<l>And we are his sisters and his cousins and his aunts!
</lg></sp>
<sp who=REL><speaker>Rel.</speaker>
<lg part=F>
<l>And we are his sisters and his cousins and his aunts!
</lg></sp>]]></eg><!-- W.S. Gilbert: HMS Pinafore p. 11 -->
 
These elements are all defined in the core, and are thus available to
every TEI document without formality.  A more detailed discussion of the
encoding of verse is provided in chapter <xref target="VE"/>.</p></div3><div3 id="DREMB" name="subsection" ref="Y"><head>Embedded Structures</head><p>Although primarily composed of speeches, performance texts often
contain other structural units such as songs or strophes which are
shared among different speakers.  More generally, complex nested
structures of plays within plays, interpolated masques, or interludes
are far from uncommon.  In more modern material, comparably complex
structural devices such as flashback or nested playback are equally
frequent.  In all kinds of performance material, it may be necessary to
indicate several actions which are happening simultaneously.</p><p>A number of different devices are available within the TEI scheme to
support these complexities in the general case.  Texts may be composite
or self-nesting (see section <xref target="DSGRP"/>) and multiple
hierarchies may be defined (see chapter <xref target="NH"/>).  The TEI
encoding scheme provides a variety of linking mechanisms, which may be
used to indicate temporal alignment and aggregation of fragmented
structures.  In this section we provide a few specific examples of the
application of these techniques to performance texts:
 
<list type="bullets"><item>the use of embedded <gi tei="yes">text</gi> elements</item><item>the use of the <att tei="yes">part</att> attribute on fragmentary
<gi tei="yes">lg</gi> elements</item><item>the use of the <att tei="yes">next</att> and <att tei="yes">prev</att> attributes on
fragments of embedded structures to join them into a larger whole</item><item>the use of the <gi tei="yes">join</gi> element to define a
<soCalled>virtual element</soCalled> composed of the fragments
indicated</item></list>
 
Full information and descriptions are provided in other chapters of this
document, as indicated in the individual discussions.</p><p>When a song appears, in its entirety, within a single speech, it may
be treated as an extended quotation or as an embedded <gi tei="yes">text</gi>
element, or both, according to the preference of the encoder.  In the
following example, an embedded song is treated as a self-standing text:
 
<eg><![CDATA[<sp><speaker>Kelly</> <stage>(calmly).</>
  <p>Aha, so you've bad minds along with th' love of gain.
     You thry to pin on others th' dirty decorations that
     may be hangin' on your own coats.
  <stage>(He points, one after the other at Conroy, Bull,
     and Flagonson.  Lilting):</>
  <q><text><body>
     <l>Who were you with last night?</l>
     <l>Who were you with last night?</l>
     <l>Will you tell your missus when you go home</l>
     <l>Who you were with last night?</l>
  </body></text></q></p></sp>
<sp><speaker>Flagonson</> <stage>(in anguished indignation).</>
  <p>This is more than a hurt to us:  this hits at the
     decency of the whole nation!</p></sp>]]></eg>
 
It might, however, also be treated simply as a quotation:
 
<eg><![CDATA[<sp><speaker>Kelly</> <stage>(calmly).</>
  <p>Aha, so you've bad minds along with th' love of gain.
     <!-- ... -->
  <stage>(He points, one after the other at Conroy, Bull,
     and Flagonson.  Lilting):</>
  <q><l>Who were you with last night?
     <l>Who were you with last night?
     <l>Will you tell your missus when you go home
     <l>Who you were with last night?
  </q>
</sp>]]></eg></p><p>When an embedded structure extends across more than one <gi tei="yes">sp</gi>
element, each of its constituent parts must be regarded as a distinct
fragment; the problem then facing the encoder is to reconstitute the
interrupted whole in some way.</p><p>As already noted above, the <att tei="yes">part</att> attribute may be used to
indicate that an <gi tei="yes">l</gi> element contains a partial, not a complete,
verse line.  The same attribute may be used on the <gi tei="yes">lg</gi> element,
to indicate that the line group is partial rather than complete, thus:
 
<eg><![CDATA[<sp><speaker>Kelly</>
    <stage>(wheeling quietly in his semi-dance, as he goes out):</>
    <lg part=i>
        <l>Goodbye to holy souls left here,</l>
        <l>Goodbye to man an' fairy;</l>
    </lg>
</sp>
<sp><speaker>Widda Machree</>
    <stage>(wheeling quietly in her semi-dance, as she goes out):</>
    <lg part=f>
        <l>Goodbye to all of Leicester Square,</l>
        <l>An' the long way to Tipperary.</l>
    </lg>
</sp>]]></eg></p><p>When the fragments of a song are separated by other intervening
dialogue, or even when not, they may be linked together with the
<att tei="yes">next</att> and <att tei="yes">prev</att> attributes defined in section<xref target="SAAG"/>
.  For example, the line groups making up Ophelia's song
might be encoded as follows:
 
<eg><![CDATA[<div1 type="act" n=4>
<!-- ... -->
<div2 type="scene" n=5>
<stage>Elsinore. A room in the Castle.</stage>
<!-- ... -->
<stage type="setting">Enter Ophelia, distracted.</stage>
<sp who="Oph"><speaker>Ophelia</speaker>
    <p>Where is the beauteous Majesty of Denmark?</p>
</sp>
<sp who="Qu"><speaker>Queen</speaker>
    <p>How now, Ophelia?</p>
</sp>
<sp who="Oph"><speaker>Ophelia</speaker>
    <stage>Singing</stage>
    <lg type=song id="TL1" part=Y next=TL2 >
        <l>How should I your true-love know</l>
        <l>From another one?</l>
        <l>By his cockle hat and staff</l>
        <l>And his sandal shoon.</l>
    </lg>
</sp>
<sp who="Qu"><speaker>Queen</speaker>
    <p>Alas, sweet lady, what imports this song?</p>
</sp>
<sp who="Oph"><speaker>Ophelia</speaker>
    <p>Say you? Nay, pray you mark.</p>
    <stage>Sings</stage>
    <lg id="TL2" part=Y prev=TL1>
        <l>He is dead and gone, lady,</l>
        <l>He is dead and gone;</l>
        <l>At his head a grass-green turf,</l>
        <l>At his heels a stone.</l>
    </lg>
    <p>O, ho!</p>
</sp>
<!-- ... -->
</div2>
</div1>]]></eg></p><p>The <att tei="yes">next</att> and <att tei="yes">prev</att> attributes are discussed in
section <xref target="SAAG"/>:  they form part of the additional tag set
for alignment and linking, and are therefore not automatically available
to dramatic texts.  To enable this tag set as well as the base tag set
for drama, the document type declaration of a document might take the
following form:
 
<eg><![CDATA[<!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
  <!ENTITY % TEI.drama   'INCLUDE'>
  <!ENTITY % TEI.linking 'INCLUDE'>
]>]]></eg>
 
See chapter <xref target="ST"/> for general discussion of the way in which
TEI tag sets are enabled.</p><p>The fragments of Ophelia's song might also be linked together using
the <gi tei="yes">join</gi> mechanism described in section <xref target="SAAG"/>.
The <gi tei="yes">join</gi> element is specifically intended to encode the fact
that several discontiguous elements of the text together form one
<soCalled>virtual</soCalled> element.  Using this mechanism, the example
might be encoded as follows:
 
<eg><![CDATA[<text><body><div1 type="act" n=4>
<!-- ... -->
<div2 type="scene" n=5>
<stage type="setting">Elsinore. A room in the Castle.</stage>
<!-- ... -->
<sp who="Qu"><speaker>Queen</speaker>
    <p>How now, Ophelia?</p>
</sp>
<sp who="Oph"><speaker>Ophelia</speaker>
    <stage type="delivery">Singing</stage>
    <lg type=song id="TL1" part=Y>
        <l>How should I your true-love know</l>
        <l>From another one?</l>
        <l>By his cockle hat and staff</l>
        <l>And his sandal shoon.</l>
    </lg>
</sp>
<sp who="Qu">
<speaker>Queen</speaker>
    <p>Alas, sweet lady, what imports this song?</p>
</sp>
<sp who="Oph">
<speaker>Ophelia</speaker>
    <p>Say you? Nay, pray you mark.</p>
    <stage type="delivery">Sings</stage>
    <lg id="TL2" part=Y >
        <l>He is dead and gone, lady,</l>
        <l>He is dead and gone;</l>
        <l>At his head a grass-green turf,</l>
        <l>At his heels a stone.</l>
    </lg>
<p>O, ho!</p>
<join targets='TL1 TL2' type=lg>
</sp>
<!-- ... -->
</div2>
</div1></body></text>]]></eg><!-- Suppressed N att on JOIN on the theory that N is for     --><!-- numbers or similar symbols, and 'True Love Know' does    --><!-- not qualify.  (msm)                                      -->
 
The location of the <gi tei="yes">join</gi> element is not significant; here it
has been placed shortly after the conclusion of the song, in order to
have it close to the fragments it unifies.</p><p>Like the <att tei="yes">next</att> and <att tei="yes">prev</att> attributes, the
<gi tei="yes">join</gi> element requires the additional tag set for linking, which
is selected as shown above.</p></div3><div3 id="DRSIM" name="subsection" ref="Y"><head>Simultaneous Action</head><p>In printed or written versions of performance texts, a variety of
techniques may be used to indicate the temporal alignment of speeches or
actions.  Speeches may be printed vertically aligned on the page, or
braced together; stage directions (e.g. <q>Speaking at the same
time</q>) are also often used.  In operatic or musical works in
particular, the need to indicate timing and alignment of individual
parts of a song may lead to very complex layout.</p><p>One simple method of indicating the temporal alignment of speeches or
actions is to use the <att tei="yes">corresp</att> attribute discussed in section<xref target="SACS"/>
, as in the following example:
 
<eg><![CDATA[<sp who="M"><speaker>Mangan</>
  <stage type="delivery">wildly</stage>
  <p>Look here: I'm going to take off all my clothes.</p>
  <stage type="action">he begins tearing off his coat.</stage>
</sp>
<sp who="LU" id=S1><speaker>Lady Utterword</speaker>
  <p>Mr Mangan!</p>
</sp>
<sp who="CS" id=S2><speaker>Captain Shotover</speaker>
  <p>Whats that?</p>
</sp>
<sp who="H" id=S3><speaker>Hector</speaker>
  <p>Ha! ha! Do. Do.</p>
</sp>
<sp who="E" id=S4><speaker>Ellie</speaker>
  <p>Please dont.</p>
</sp>
<stage id=D1 type="delivery" corresp="S1 S2 S3 S4">
  in consternation</stage>
 
<sp who="MH"><speaker>Mrs. Hushabye</speaker>
  <stage type="action">catching his arm and stopping him</stage>
  <p>Alfred: for shame! Are you mad?</p>
</sp>]]></eg></p><p>In the original, the stage direction <q>in consternation</q> is
printed opposite a brace grouping all four speeches, indicating that all
four characters speak at once, and that the stage direction applies to
all of them.  In the example, the <gi tei="yes">stage</gi> element has been moved
to an arbitrary place, and the four speeches with which it is to be
associated are specified by identifier as the value of the
<att tei="yes">corresp</att> attribute.  This attribute, which is enabled by the
linking tag set, provides the simplest way of indicating the temporal
alignment of speeches or actions in a play.
 <!-- I need help deciding how (or whether) to represent this --><!-- with the ALIGN element                                  --></p><p>More powerful and more precise mechanisms for temporal alignment are
defined in chapter <xref target="TS"/>.  These would be appropriate for
encodings the focus of which is on the actual performance of a text
rather than its structure or formal properties.  The tag set described
in that chapter includes a large number of other detailed proposals for
the encoding of such features as voice quality, prosody, etc., which
might be relevant to such a treatment of performance texts.</p></div3></div2><!-- With any luck, almost all the temporal alignment         --><!-- mechanisms should be moving to tagset SA / TEI.linking,  --><!-- but for now this note is retained. (msm)                 --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2drbod.odd ??><?tei:SOF p2droth.odd ??><!-- Revisions:                                               --><!-- 93-08-20 : MSM : fix typo before publication             --><!-- 93-08-19 : MSM : fix exx after parsing TESTDR.TEI        --><!-- 93-08-16 : MSM : suppress ref to CODE att on TECH (n'existe plus) --><!-- 93-08-16 : MSM : fix MS end problem                      --><div2 id="DROTH" name="section" ref="Y"><head>Other Types of Performance Text</head><p>Most of the elements and structures identified thus far are derived
from traditional theatrical texts.  Although other performance texts,
such as screen plays or radio scripts, have not been discussed
specifically, they can be encoded using the elements and structures
listed above.  Encoders may however find it convenient to use, as well,
the additional specialized elements discussed in this section.  For
scripts containing very detailed technical information, the
<gi tei="yes">tech</gi> element discussed in section <xref target="DRTEC"/> may also
be useful.
 </p><p>Like other texts, screen plays and television or radio scripts may
be divided into text divisions marked with <gi tei="yes">div</gi> or
<gi tei="yes">div1</gi>, etc.  Within units corresponding with the traditional
<q>act</q> and <q>scene</q>, further subdivisions or sequences may be
identified, composed of individual <q>shots</q>, each associated with
a single camera angle and setting.  Shots and sequences should be
encoded using an appropriate text-division element (i.e., a
<gi tei="yes">div3</gi> element if numbered division elements are in use and the
next largest unit is a <gi tei="yes">div2</gi>, or a <gi tei="yes">div</gi> element if
un-numbered divisions are in use) specifying <code tei="yes" type="frag">sequence</code> or
<code tei="yes" type="frag">shot</code> as the value of the <att tei="yes">type</att> attribute, as
appropriate.
 </p><p>It is normal practice in screenplays and radio scripts to distinguish
directions concerning camera angles, sound effects, etc., from other
forms of stage direction.  Such texts also generally include far more
detailed specifications of what the audience actually sees:
descriptions of actions and background, etc.  Scripts derived from
cinema and television productions may also include texts displayed as
captions superimposed on the action.  All of these may be encoded using
the general purpose <gi tei="yes">stage</gi> element discussed in section <xref target="DRSTA"/>, and distinguished by means of its <att tei="yes">type</att>
attribute.  Alternatively, or in addition, the following more specific
elements may be used, where clear distinctions can be made:
 
<tagList style="one-line"><tagDesc tagDoc="VIEW"/><tagDesc tagDoc="CAMERA" atts="type"/><tagDesc tagDoc="CAPTION"/><tagDesc tagDoc="SOUND" atts="type discrete"/></tagList><!-- dd notes that SOUND is not a good name for the tag: proposes SFX --><!-- or how about EFFECT? -->
 </p><p>Some examples of the use of these elements follow:
 
<eg><![CDATA[<camera>Angle on Olivia.</camera>
<view>Ryan's wife, standing nervously alone on the sidelines,
biting her lip. She's scared and she shows it.</view>]]></eg>
 </p><p>Where particular words or phrases within a direction are emphasized
(by change of typeface or use of capital letters), an appropriate
phrase-level element may be used to indicate the fact, as in the
following examples, where certain words in the original are given in
small capitals:
 
<eg><![CDATA[<view>George glances at the window--and freezes.
<camera>New angle--shock cut</camera> Out the window
the body of a dead man suddenly slams into
<hi>frame</hi>. He dangles grotesquely,
held up by his coat caught on a protruding bolt.
George gasps. The train <hi>whistle</hi> screams.
</view>]]></eg><!-- source? -->
 
<eg><![CDATA[<view>Ext. TV control van&mdash;Early morning.
The <name>T.V. announcer</name> from the Ryan interview
stands near the Control Van, the lake in b.g.
</view>
<sp who="announcer">
<speaker>T.V. Announcer</speaker>
<p>Several years ago, Jack Ryan was a highly
successful hydroplane  racer....</p>
</sp>]]></eg><!-- source? -->
 </p><p>All of these elements, like other stage directions, can appear both
within and between speeches.
 
<eg><![CDATA[<sp>
<speaker>TV Announcer VO</speaker>
<p>Working with Ryan are his two coworkers&mdash;
Strut Bowman, the mechanical engineer&mdash;
<view><camera>Angle on Strut</camera>
standing in the tow boat, walkie-talkie in hand,
watching Ryan carefully.</view>
&mdash;and Roger Dalton, a rocket
systems analyst, and one of the scientists
from the Jet Propulsion Lab....</p></sp>]]></eg>
 
<eg><![CDATA[<sp><speaker>Benjy</speaker>
  <p>Now to business.</p></sp>
<sp><speaker>Ford and Zaphod</speaker>
  <p>To business.</p></sp>
  <sound>Glasses clink.</sound>
<sp><speaker>Benjy</speaker>
  <p>I beg your pardon?</p></sp>
<sp><speaker>Ford</speaker>
  <p>I'm sorry, I thought you were
  proposing a toast.</p></sp>]]></eg><!-- Hitch-hikers Guide, p.83 -->
 
<eg><![CDATA[<camera>Zoom in to overlay showing some stock film
  of hansom cabs galloping past.</camera>
<caption>London, 1895.</caption>
<caption>The residence of Mr Oscar Wilde.</caption>
<sound>Suitably classy music starts.</sound>
<view>Mix through to Wilde's drawing room. A crowd of suitably
  dressed folk are engaged in typically brilliant conversation,
  laughing affectedly and drinking champagne.</view>
<sp who=TJ><speaker>Prince of Wales</speaker>
  <p>My congratulations, Wilde. Your latest play is a great success.
  </p></sp>]]></eg><!-- Monty Pythons Flying Circus, vol 2, p 230 -->
 </p><div3 id="DRTEC" name="subsection" ref="Y"><head>Technical Information</head><!-- was: Prop plots and lighting scripts --><p>Traditional stage scripts may contain additional technical
information about such production-related factors as lighting,
<soCalled>blocking</soCalled> (that is, detailed notes on actors'
movements) or props required at particular points.  More technical
information about intended production effects may also appear in
published versions of screen plays or movie scripts.  Where these are
presented simply as marginal notes, they may be encoded using the
general-purpose <gi tei="yes">note</gi> element defined in section <xref target="CONO"/>.  Alternatively, they may be formally distinguished from
other stage directions by using the specialized <gi tei="yes">tech</gi> element:
 
<tagList style="one-line"><tagDesc tagDoc="TECH" atts="type perf"/></tagList>
 </p><p>Like stage directions, <gi tei="yes">tech</gi> elements can appear anywhere
within a speech or between speeches.
 </p><p>The elements discussed in the section are formally defined as
follows:
 
<dtdFrag id="DDROTH" n="Screen plays and other technical matters"><tagDecl tagDoc="VIEW"/><tagDecl tagDoc="CAMERA"/><tagDecl tagDoc="SOUND"/><tagDecl tagDoc="CAPTION"/><tagDecl tagDoc="TECH"/></dtdFrag><?tei:EOF p2droth.odd ??></p></div3></div2></div1><!-- *** end of P2 DR *************************************** --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2dr.odd ??><!-- 10 Drama --><?tei:SOF p2ts.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ts.odd,v $
    * Revision 1.11  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.10  94/04/01  16:39:21  msmcq
    * Changes during validation of DTD
    * 
    * Revision 1.9  1994/03/28  18:16:08  msmcq
    * add TYPE attribute to IDENT
    * 
    * Revision 1.8  1994/03/27  21:46:39  msmcq
    * Correction of typos reported by DB, EB.
    * 
    * Revision 1.7  1994/03/21  14:12:00  lou
    * second mass typo clearup
    * 
    * Revision 1.5  1994/02/17  20:29:04  msmcq
    * revision for SC review
    * --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : protect teistr invocation               --><!-- 94-03-31 : MSM : define tsmix                            --><!-- 94-03-29 : MSM : clarify class usage (or try to)         --><!-- 94-03-29 : MSM : suppress reference to 'spoken' class, use compspok --><!-- 94-03-27 : MSM : correct error tagging IDENT             --><!-- 94-03-26 : MSM : typos, changes from EBr, DB             --><!-- 94-02-14 : MSM : minor cleanup                           --><!-- 94-02-14 : MSM : Added RCS id                            --><!-- Opening sections really need a complete rewrite to       --><!-- conform to P2 housestyle, but I can't face it just now   --><!-- (lb)                                                     --><!-- 16 sep 93: LB: gritted teeth; hacked out a lot --><!-- 27-8 Aug: LB : added examples --><!-- 9 aug: LB: fixed AH and other cross refs;
                replaced discussion of decls with xref to CCas  --><!-- 27 jul 93: LB added credit at start --><!-- 93-07-21 : DTL : minor corrections                       --><!-- 93-07-15 : DTL : references to TSsa changed to SA, etc   --><!--  9  Feb 93 : WP  : Changed P222 refs to P2HD refs        --><!--  9  Feb 93 : WP  : Changed 34 to 10                      --><!--  4  Feb 93 : WP  : Changed P234 to P2TS                  --><!-- 22f Apr 92 : MSM : final changes for release             --><!-- 18 Apr 92 : LB : various minor changes:                  --><!--          further fiddling with wording of first section  --><!--          mentioned nestable div                          --><!--          clarified rule on start/end/dur attribs         --><!--          added eg. for trans attrib                      --><!-- 17 Apr 92 : CMSMcQ : changes for release to LB           --><!-- 17 Apr 92 : WP     : spellcheck and make changes         --><!-- 16 Apr 92 : CMSMcQ : clean up for release.  rename stext --><!--  3 Apr 92 : CMSMcQ : add n value on div1                 --><!--  2 Apr 92 : CMSMcQ : reformat multi-line comments        --><!--  2 Apr 92 : CMSMcQ : suppress blank lines (format better)--><!--  2 Apr 92 : CMSMcQ : add /eg at line 415 or so           --><!-- *******************************************************  --><!--           TEI P2 : CHAPTER 10 : SPOKEN TEXTS             --><!-- *******************************************************  --><div1 id="TS" n="11" name="chapter" ref="Y"><head>Transcriptions of Speech</head><p>The base tag set for transcriptions of spoken language described in
this chapter is intended for use with a wide variety of transcribed
spoken material.  It should be stressed, however, that the present
proposals are not intended to support unmodified every variety of
research undertaken upon spoken material now or in the future; some
discourse analysts, some phonologists, and doubtless others may wish
to extend the scheme presented here to express more precisely the set
of distinctions they wish to draw in their transcriptions.  Speech
regarded as a purely acoustic phenomenon may well require different
methods from those outlined here, as may speech regarded solely as a
process of social interaction.
 <!-- <note>This chapter was prepared by TEI work group AI 2 --><!-- (spoken texts), chaired by Stig Johansson, of the University --><!-- of Oslo.  The membership of the work group is given in the --><!-- front matter.  Major contributions to the ideas here --><!-- presented came from A. Rosta (University College, London) --><!-- and J. Edwards (University of California). The scheme is --><!-- based on a survey of about twenty widely used and documented --><!-- systems for the transcription of spoken materials taken from --><!-- such diverse fields as journalism, large reference corpora, --><!-- language-acquisition studies, and dialect studies.</note> --></p><p>This chapter begins with a discussion of some of the problems
commonly encountered in transcribing spoken language (section <xref target="TSOV"/>).  Section <xref target="TSBA"/> describes the basic
structural elements of this tag set.  Finally, section <xref target="TSSA"/> of this chapter reviews further problems specific to the
encoding of spoken language, demonstrating how mechanisms and elements
discussed elsewhere in these Guidelines may be applied to them.</p><p>The overall structure of a TEI spoken text is identical to that of
any other TEI text:  the <gi tei="yes">tei.2</gi> element for a spoken text
contains a <gi tei="yes">teiHeader</gi> element, followed by a <gi tei="yes">text</gi>
element.  Even texts primarily composed of transcribed speech may also
include conventional front and back matter, and may even be organized
into divisions like printed texts. For simplicity's sake, therefore, the
base tag set for spoken text uses the default text structure, as defined
in chapter <xref target="DS"/>; this tag set is embedded automatically by
the spoken base tag set.</p><p>To enable the base tag set for spoken texts, a parameter entity
<ident tei="yes" type="pe">TEI.spoken</ident> must be declared within the document
type declaration subset, the value of which is <code tei="yes" type="frag">INCLUDE</code>, as
further described in section <xref target="STIN"/>.  A document using this
base tag set and no additional tag sets will thus begin as follows:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.spoken 'INCLUDE' >
 ]>]]></eg>
 
This declaration makes available all of the elements and attributes
discussed in the present chapter, in addition to the core elements
described in chapter <xref target="CO"/>.  If other elements are needed (in
particular, those needed for synchronization or segmentation),
additional tag sets may also be enabled in a similar way.</p><p>Two additional classes are defined by this tag set.  Elements which
appear only within transcribed speech constitute the <ident tei="yes" type="class">comp.spoken</ident> element class.  Elements with a
specificable temporal duration constitute the <ident tei="yes" type="class">timed</ident> element class.  These classes are defined in
the file <ident tei="yes" type="file">teispok2.ent</ident> using the following
parameter entities:
 
<dtdFrag id="DTSCLA" n="Class declarations for Transcribed Speech" file="teispok2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><claDecl classDoc="COMPSPOK" type="model"/><claDecl classDoc="TIMED" type="atts"/><entDecl entDoc="TSMIX"/></dtdFrag>
 
The elements of the base tag set for transcribed speech are declared in
the file <ident tei="yes" type="file">teispok2.dtd</ident>, which is organized as
follows:
 
<dtdFrag id="DTS" n="Base tag set for Transcribed Speech" file="teispok2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><dtdRef dtdFrag="DTSCOMP"/><commDecl>The base tag set for transcriptions of speech uses the
standard default text-structure elements, which are embedded
here:</commDecl><msection keywords="%TEI.singleBase"><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></msection></dtdFrag>
 <?tei:SOF p2tsov.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2tsov.odd,v $
    * Revision 1.8  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.6  1994/03/27  21:46:39  msmcq
    * Correction of typos reported by DB, EB.
    * 
    * Revision 1.5  1994/02/17  20:29:04  msmcq
    * revision for SC review
    * --><!-- Revisions:                                               --><!-- 18 jan 98 : LB : fix div example--><!-- 94-03-26 : MSM : typos, changes from EBr, DB             --><!-- 94-02-14 : MSM : minor cleanup                           --><!-- 94-02-14 : MSM : Added RCS id                            --><!-- 93-12    : LB : delete introductory comments --></p><div2 id="TSOV" name="subsection" ref="Y"><head>General Considerations and Overview</head><p>There is great variation in the ways different researchers have
chosen to represent speech using the written medium.<note source="auth" place="display" anchored="Y">For a
discussion of several of these see <citation>J.  A. Edwards and M. D.
Lampert, eds., <title>Talking Language:  Transcription and Coding of
Spoken Discourse</title> (Hillsdale, N.J.:  Lawrence Erlbaum Associates,
1993)</citation>; <citation>Stig Johansson, <title.p>Encoding a Corpus
in Machine-Readable Form,</title.p> in <title>Computational Approaches
to the Lexicon:  An Overview,</title> ed.  B. T. S. Atkins et al.
(Oxford:  Oxford University Press, forthcoming)</citation>; and
<citation>Stig Johansson et al.  <title.p>Working Paper on Spoken
Texts,</title.p> document TEI AI2 W1, 1991</citation>.</note> This
reflects the special difficulties which apply to the encoding or <term rend="noindex">transcription</term> of speech.  Speech varies according to
a large number of dimensions, many of which have no counterpart in
writing (for example, tempo, loudness, pitch, etc.).  The audibility of
speech recorded in natural communication situations is often less than
perfect, affecting the accuracy of the transcription.  Spoken material
may be transcribed in the course of linguistic, acoustic,
anthropological, psychological, ethnographic, journalistic, or many
other types of research.  Even in the same field, the interests and
theoretical perspectives of different transcribers may lead them to
prefer different levels of detail in the transcript and different styles
of visual display.  The production and comprehension of speech are
intimately bound up with the situation in which speech occurs, far more
so than is the case for written texts.  A speech transcript must
therefore include some contextual features; determining which are
relevant is not always simple.  Moreover, the ethical problems in
recording and making public what was produced in a private setting and
intended for a limited audience are more frequently encountered in
dealing with spoken texts than with written ones.
 </p><p>Speech also poses difficult structural problems.  Unlike a written
text, a speech event takes place in time.  Its beginning and end may be
hard to determine and its internal composition difficult to define.
Most researchers agree that the utterances or <term>turns</term> of
individual speakers form an important structural component in most kinds
of speech, but these are rarely as well-behaved (in the structural
sense) as paragraphs or other analogous units in written texts:
speakers frequently interrupt each other, use gestures as well as words,
leave remarks unfinished and so on.  Speech itself, though it may be
represented as words, frequently contains items such as vocalized pauses
which, although only semi-lexical, have immense importance in the
analysis of spoken text.  Even non-vocal elements such as gestures may
be regarded as forming a component of spoken text for some analytic
purposes.<!-- LB added following sentence -->
Below the level of the individual utterance, speech may be segmented
into units defined by phonological, prosodic, or syntactic phenomena;
no clear agreement exists, however, even as to appropriate names for
such segments.
 </p><p>Spoken texts transcribed according to the guidelines presented here
are organized as follows.  As noted above, speech is regarded as being
composed of arbitrary high-level units called
<term rend="noindex">texts</term>.<indexed level1="texts" level2="as organizing unit for spoken material"/>
A spoken <gi tei="yes">text</gi> might typically be a conversation between a small
number of people, a lecture, a broadcast TV item, or a similar event.
Each such unit has associated with it a <gi tei="yes">teiHeader</gi> providing
detailed contextual information such as the source of the transcript,
the identity of the participants, whether the speech is scripted or
spontaneous, the physical and social setting in which the discourse
takes place and a range of other aspects.  For details of the header in
general, refer to chapter <xref target="HD"/>; for details of additional
elements for the documentation of participant and contextual
information, see section <xref target="CCAH"/>.
 </p><p>Defining the bounds of a spoken text is frequently a matter of
arbitrary convention or convenience.  In public or semi-public contexts,
a text may be regarded as synonymous with, for example, a <term rend="noindex">lecture</term>, a <term rend="noindex">broadcast item</term>,
a <term rend="noindex">meeting</term>, etc.  In informal or private
contexts, a text may be simply a conversation involving a specific group
of participants.  Alternatively, researchers may elect to define spoken
texts solely in terms of their duration in time or length in words.  By
default, these Guidelines assume of a text only that:
 
<list type="simple"><item>it is internally cohesive,</item><item>it is describable by a single header, and</item><item>it represents a single stretch of time with no significant
discontinuities.</item></list>
 
Deviation from these assumptions may be specified (for example, the
<att tei="yes">org</att> attribute on the <gi tei="yes">text</gi> element may take the value
<code tei="yes" type="value">compos</code> to specify that the components of the
text are discrete) but is not recommended.
 </p><p>Within a <gi tei="yes">text</gi> it may be necessary to identify subdivisions
of various kinds, if only for convenience of handling.  The neutral
<gi tei="yes">div</gi> element discussed in section <xref target="DSDIV"/> is
recommended for this purpose.  It may be found useful also for
representing subdivisions relating to discourse structure, speech act
theory, transactional analysis, etc., provided that these divisions are
hierarchically well-behaved.<!-- Reference changed to SA and SAsy (DTL) --><!-- LB moved out of note and into text --><!-- note -->
Where they are not,
as is often the case, the mechanisms discussed in chapters<xref target="SA"/>
 and<xref target="NH"/>
 may be used. <!-- /note-->
 
 </p><p>A spoken text may contain any of the following components:
<list type="simple"><item>utterances</item><item>pauses</item><item>vocalized but non-lexical phenomena such as coughs</item><item>kinesic (non-verbal, non-lexical) phenomena such as gestures</item><item>entirely non-linguistic events occurring during and possibly
influencing the course of speech</item><item>writing, regarded as a special class of event in that it can
be transcribed, for example captions or overheads displayed during
a lecture</item><item>shifts or changes in vocal quality</item></list>
 </p><p>Elements to represent all of these features of spoken language are
discussed in section <xref target="TSBA"/> below.
 </p><p>An utterance (tagged <gi tei="yes">u</gi>) may contain lexical items
interspersed with pauses and non-lexical vocal sounds; during an
utterance, non-linguistic events may occur and written materials may be
presented.  The <gi tei="yes">u</gi> element can thus contain any of the other
elements listed, interspersed with a transcription of the lexical items
of the utterance; the other elements may all appear between utterances
or next to each other, but except for <gi tei="yes">writing</gi> they do not
contain any other elements nor any data.
 <!-- paras removed here: too repetitious -->
 </p><div3 id="TSOSDC" name="subsection" ref="Y"><head>Divisions</head><p>A spoken text itself may be without substructure, that is, it may
consist simply of units such as utterances or pauses, not grouped
together in any way, or it may be subdivided into one or more divisions
as described in this section.
 </p><p>If the notion of what constitutes a <soCalled>text</soCalled> in
spoken discourse is inevitably rather an arbitrary one, the notion of
formal subdivisions within such a <soCalled>text</soCalled> is even more
debatable.  Nevertheless, such divisions may be useful for such types of
discourse as debates, broadcasts, etc., where structural subdivisions
can easily be identified, or more generally wherever it is desired to
aggregate utterances or other parts of a transcript into units smaller
than a complete <soCalled>text</soCalled>.  Examples might include
<q>conversations</q> or <q>discourse fragments</q>, or more narrowly,
<q>that part of the conversation where topic x was discussed</q>,
provided only that the set of all such divisions is coextensive with the
text.
 </p><p>Each such division of a spoken text should be represented by the
numbered or un-numbered <gi tei="yes">div</gi> elements defined in chapter <xref target="DS"/>.  For some detailed kinds of analysis a hierarchy of such
divisions may be found useful; nested <gi tei="yes">div</gi> elements may be used
for this purpose, as in the example below.
 </p><p>The <gi tei="yes">div</gi> element is a member of the <ident tei="yes" type="class">divn</ident> class of structural elements, and therefore has
the following attributes in common with other members of the class:
 
<adList classDoc="DIVN" atts="type org sample part"/>
 </p><p>The <att tei="yes">type</att> attribute may be used to characterize divisions
in any way that is convenient; no specific recommendations are made in
these Guidelines.  For example, a collection made up of transcribed
<soCalled>sound bites</soCalled> taken from speeches given by a
politician on different occasions, might encode each extract as a
distinct <gi tei="yes">div</gi>, nested within a single composite <gi tei="yes">div</gi> as
follows:
 
<eg rend="skel"><![CDATA[<div type='soundbites' org='composite'>
 
   <div sample=medial>
   <!-- ... -->
   </div>
   <div sample=medial>
   <!-- ... -->
   </div>
   <div sample=initial>
   <!-- ... -->
   </div>
</div>]]></eg>
 <!-- removed dur attribute on div                             --><!-- The <att>dur</att> attribute may specify temporal        --><!-- duration in any units convenient; for further            --><!-- discussion of temporal alignment, see section <xref      --><!-- target=SASY>.                                            -->
 </p><p>As a member of the class <ident tei="yes" type="class">declaring</ident>, the
<gi tei="yes">div</gi> element may also carry a <att tei="yes">decls</att> attribute, for
use where the divisions of a text do not all share the same set of the
contextual declarations specified in the TEI header.  (See further
section <xref target="CCAS"/>).
 <!-- example would be nice here too -->
 
<?tei:EOF p2tsov.odd ??>

 <?tei:SOF p2tsba.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2tsba.odd,v $
# Revision 1.8  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.7  1994/03/28  14:56:39  lou
# fix dud xref
#
# Revision 1.6  1994/03/27  21:46:39  msmcq
# Correction of typos reported by DB, EB.
#
# Revision 1.5  1994/02/17  20:29:04  msmcq
# revision for SC review
# --><!-- Revisions:                                               --><!-- 18 jan 98: LB : fix egs --><!-- 4 Jan 94 : LB : participant/group changed to person/grp --><!-- 94-03-26 : MSM : typos, changes from EBr and DB          --><!-- 94-02-14 : MSM : more cleanup                            --><!-- 94-02-14 : MSM : cosmetic, spelling                      --><!-- 94-02-14 : MSM : Added RCS id                            -->
 </p></div3></div2><div2 id="TSBA" name="subsection" ref="Y"><head>Elements Unique to Spoken Texts</head><p>The following elements characterize spoken texts, transcribed
according to these Guidelines:
 
<tagList style="one-line"><tagDesc tagDoc="U"/><tagDesc tagDoc="PAUSE"/><tagDesc tagDoc="VOCAL"/><tagDesc tagDoc="KINESIC"/><tagDesc tagDoc="EVENT"/><tagDesc tagDoc="WRITING"/><tagDesc tagDoc="SHIFT"/></tagList>
 </p><p>Each of these is further discussed and specified below in sections<xref target="TSBAUT"/>
 to <xref target="TSBAWR"/>.
 </p><p>We can show the relationship between four of these constituents of
speech using the features <ident tei="yes" type="feature">eventive</ident>, <ident tei="yes" type="feature">communicative</ident>, <ident tei="yes" type="feature">anthropophonic</ident> (for sounds produced by the human
vocal apparatus), and <ident tei="yes" type="feature">lexical</ident>:
 
<eg rend="fig"><![CDATA[         eventive  communicative  anthropophonic  lexical
 
event       +             -              -           -
kinesic     +             +              -           -
vocal       +             +              +           -
utterance   +             +              +           +]]></eg>
 
The differences are not always clear-cut.  Among
<term rend="noindex">events</term> might be included actions like
slamming the door, which can certainly be communicative.
<term rend="noindex">Vocals</term> include coughing and sneezing, which are<indexed level1="vocal events" level2="in transcription of speech"/>
usually involuntary noises.  Equally, the distinction between utterances
and vocals is not always clear,
 <!-- (as implied by our use of the term <q>semi-lexical</q>) -->
 
although for many analytic purposes it will be convenient to regard them
as distinct.  Individual scholars may differ in the way borderlines are
drawn and should declare their definitions in the <gi tei="yes">editorialDecl</gi>
element of the header (see <xref target="HD53"/>).
 </p><p>The following short extract exemplifies several of these elements. It
is recoded from a text originally transcribed in the CHILDES
format.<note source="auth" place="display" anchored="Y">The original is a conversation between two children and
their parents, recorded in 1987, and discussed in
<citation><author>Brian MacWhinney,</author>
<title>CHAT Manual</title>
<detail>([Pittsburgh]:  Dept of Psychology, Carnegie-Mellon University,
1988), pp. 87ff.</detail></citation></note>
Each utterance is encoded using a <gi tei="yes">u</gi> element (see section <xref target="TSBAUT"/>).  Pauses marked by the transcriber are indicated using
the <gi tei="yes">pause</gi> element (see section <xref target="TSBAPA"/>).
Non-verbal vocal effects such as the child's meowing are indicated
either with orthographic transcriptions or with the <gi tei="yes">vocal</gi>
element, and entirely non-linguistic but significant events such as the
sound of the toy cat are represented by the <gi tei="yes">event</gi> elements
(see section <xref target="TSBAVO"/>).
 
<eg><![CDATA[<u who=MAR>you never <pause> take this cat for show&sp;and&sp;tell
  <pause> meow meow</u>
<u who=ROS>yeah well I dont want to</u>
<event desc=
  'toy cat has bell in tail which continues to make a tinkling sound'>
<vocal who=MAR desc='meows'>
<u who=ROS>because it is so old</u>
<u who=MAR>how <reg orig="bout">about</reg> your&stress; cat <pause>
   yours is  new &stress;
  <kinesic desc='shows Father the cat'></u>
<u who=FAT trans=pause>thats <pause> darling</u>
<u who=MAR><s>no mine&stress; isnt old</s>
           <s>mine is just um a little dirty</s></u>]]></eg>
 <!-- from MacWhinney 88, 87, cited by SJ -->
 </p><p>This example also uses some elements common to all TEI texts,
notably the <gi tei="yes">reg</gi> tag for editorial regularization.  Special
purpose entity references have been used to indicate non-separating
spaces (<code tei="yes" type="frag">&amp;amp;sp</code>) and unusually stressed syllables
(<code tei="yes" type="frag">&amp;amp;stress</code>); an alternative to the latter might
have been to use the core <gi tei="yes">emph</gi> element.  The <gi tei="yes">s</gi> element
has also been used to segment the last utterance.  Further discussion of
all of these options is provided in section <xref target="TSSA"/>.
 </p><p>Contextual information is of particular importance in spoken texts,
and is usually provided by the TEI header of a text.  In general, all
of the information in a header is understood to be relevant to the whole
of the associated text.  The elements <gi tei="yes">u</gi> and <gi tei="yes">writing</gi>
are however members of the <ident tei="yes" type="class">declaring</ident> class,
and may therefore specify a different context from that of the
surrounding elements within a given division or text by means of the
<att tei="yes">decls</att> attribute (see further section <xref target="CCAS"/>).
 </p><div3 id="TSBAUT" name="subsection" ref="Y"><head>Utterances</head><p>Each distinct <term>utterance</term> in a spoken text is represented
by a <gi tei="yes">u</gi> element, described as follows:
 
<tagList style="one-line"><tagDesc tagDoc="U" atts="who trans"/><!-- decided against part attribute for now --></tagList>
 </p><p>Use of the <att tei="yes">who</att> attribute to associate the utterance with a
particular speaker is recommended but not required.  Its use implies as
a further requirement that all speakers be identified by a
<gi tei="yes">person</gi> or <gi tei="yes">personGrp</gi> element in the TEI
header (see section <xref target="CCAHPA"/>).  Where utterances cannot be
attributed with confidence to any particular participant or group of
participants, the encoder may choose to define
<soCalled>participants</soCalled> such as <ident tei="yes" type="var">all</ident> or
<ident tei="yes" type="var">various</ident>.  For example:
 
<eg><![CDATA[<u who=A>     <!-- utterance by speaker A -->
<u who='A B'> <!-- utterance by speakers A and B -->
<u who='ALL'> <!-- utterance by speaker group ALL -->]]></eg>
 </p><p>The <att tei="yes">trans</att> attribute is provided as a means of
characterizing the transition from one utterance to the next at a
simpler level of detail than that provided by the temporal alignment
mechanism discussed in section <xref target="SASY"/>.  The value specified
applies to the transition from the preceding utterance into the
utterance bearing the attribute.  For example:<note source="auth" place="foot" anchored="Y">For
the most part, the examples in this chapter use no sentence punctuation
except to mark the rising intonation often found in interrogative
statements; for further discussion, see section <xref target="TSREG"/>.</note>
 
<eg><![CDATA[   <u id=A1 who=A>Have you heard the</u>
   <u id=B1 who=B trans=latching>the election results? yes</u>
   <u id=A2 who=A trans=pause>it's a disaster</u>
   <u id=B2 who=B trans=overlap>it's a miracle</u>]]></eg>
 
In this example, utterance B1 latches on to utterance A1, while there is
a marked pause between B1 and A2.  B2 and A2 overlap, but by an
unspecified amount.  For ways of providing a more precise indication of
the degree of overlap, see section <xref target="TSSAPA"/>.
 </p><p>An utterance may contain either running text, or text within which
other basic structural elements are nested.  Where such nesting occurs,
the <att tei="yes">who</att> attribute is considered to be inherited for the
elements <gi tei="yes">pause</gi>, <gi tei="yes">vocal</gi>, <gi tei="yes">shift</gi> and
<gi tei="yes">kinesic</gi>; that is, a pause or shift (etc.) within an utterance
is regarded as being produced by that speaker only, while a pause
between utterances applies to all speakers.
 </p><p>Occasionally, an utterance may contain other utterances, for example
where there is a change in the script associated with it.  This may
occur when a speaker changes script in mid-utterance.  For example:
 
<eg><![CDATA[    <!-- breakfast table conversation ... -->
    <u who=A>Listen to this
       <u who=A decls=S1>The government is confident, he
       said, that the current economic problems will be
       completely overcome by June</u>
    what nonsense</u>]]></eg>
 
Here speaker A's own utterance contains a second nested utterance, which
is read from a newspaper.  The <att tei="yes">decls</att> attribute on the nested
utterance is used to indicate that its script is S1, rather than the
default.  Alternatively, the embedded utterance might be regarded as a
new (non-nested) one.  It might also be encoded using the
<gi tei="yes">writing</gi> element described in section <xref target="TSBAVO"/>
below, or the <gi tei="yes">event</gi> element described in section <xref target="TSBAVO"/>, without transcribing the read material:
 
<eg><![CDATA[    <u who=A>Listen to this <event desc='reads'>
    what nonsense</u>]]></eg>
 
 </p></div3><div3 id="TSBAPA" name="subsection" ref="Y"><head>Pause</head><p>The <gi tei="yes">pause</gi> empty element is used to indicate a perceived
pause, either between or within utterances.
 
<tagList style="one-line"><tagDesc tagDoc="PAUSE" atts="who type"/></tagList>
 
A pause contained by an utterance applies to the speaker of that
utterance.  A pause between utterances applies to all speakers.  The
<att tei="yes">type</att> attribute may be used to categorize the pause, for
example as short, medium or long; alternatively the attribute
<att tei="yes">dur</att> may be used to indicate its length more exactly, as in
the following example:
 
<eg><![CDATA[<u>Okay <pause dur=200>U-m<pause dur=75>the s the scene
opens up <pause dur=50> with <pause dur=20> um <pause dur=145>
you see a tree okay? </u>]]></eg>
 <!-- example recoded from Chafe  -->
 
If detailed synchronization of pausing with other vocal phenomena is
required, the alignment mechanism defined at section <xref target="SASY"/>
and discussed informally below should be used.  Note that the
<att tei="yes">trans</att> attribute mentioned in the previous section may also be
used to characterize the degree of pausing between (but not within)
utterances.
 </p></div3><div3 id="TSBAVO" name="subsection" ref="Y"><head>Vocal, Kinesic, Event</head><p>These three empty elements are used to indicate the presence of
non-transcribed semi-lexical or non-lexical phenomena either between or
within utterances.
 
<tagList style="one-line"><tagDesc tagDoc="VOCAL" atts="who desc iterated"/><tagDesc tagDoc="KINESIC" atts="who desc iterated"/><tagDesc tagDoc="EVENT" atts="who desc iterated"/></tagList>
 </p><p>The <att tei="yes">who</att> attribute should be used to specify the person or
group responsible for a vocal, kinesic or event which is contained
within an utterance, if this differs from that of the enclosing
utterance.  The attribute must be supplied for a vocal, kinesic or event
which is not contained within an utterance.
 </p><p>The <att tei="yes">iterated</att> attribute may be used to indicate that the
vocal, kinesic or event is repeated, for example <code tei="yes" type="val">laughter</code> as opposed to <code tei="yes" type="val">laugh</code>.
These should both be distinguished from <code tei="yes" type="val">laughing</code>,
where what is being encoded is a shift in voice quality.  For this last
case, the <gi tei="yes">shift</gi> element discussed in section <xref target="TSSASH"/> should be used.
 </p><p>The <att tei="yes">desc</att> attribute may be used to supply a conventional
representation for the phenomenon, for example:
 
<list type="gloss"><label>non-lexical </label><item>burp, click, cough, exhale, giggle, gulp,
    inhale, laugh, sneeze, sniff, snort, sob, swallow, throat, yawn
    </item><label>semi-lexical </label><item>ah, aha, aw, eh, ehm, er, erm, hmm, huh,
    mm, mmhm, oh, ooh, oops, phew, tsk, uh, uh-huh, uh-uh, um, urgh,
    yup</item></list>
 
Researchers may prefer to regard some semi-lexical phenomena as
<soCalled>words</soCalled> within the bounds of the <gi tei="yes">u</gi> element.
See further the discussion at section <xref target="TSREG"/> below.  As
for all basic categories, the definition should be made clear in the
<gi tei="yes">encodingDesc</gi> element of the TEI header.
 </p><p>Some typical examples follow (recoded from
<citation><author>J. Maxwell Atkinson and John Heritage, eds.,</author>
<title>Transcript notation.  Structures of social action:  Studies in
conversation analysis,</title> <detail>Cambridge University Press,
1984</detail></citation>).
 
<eg><![CDATA[<u who=Jan>This is just delicious</u>
<event desc='telephone rings'>
<u who=Kim>I'll get it</u>
 
<u who=Tom>I used to <vocal desc=cough> smoke a lot</u>
<u who=Bob><vocal desc=sniff>He thinks he's tough</u>
<vocal who=Ann desc=snorts>]]></eg>
 
Note that Ann's snorting could equally well be encoded as follows:
 
<eg><![CDATA[<u who=Ann><vocal desc=snorts></u>]]></eg>
 </p><p>The extent to which encoding of events or kinesics is included in a
transcription will depend entirely on the purpose for which the
transcription was made.  As elsewhere, this will depend on the
particular research agenda and the extent to which their presence is
felt to be significant for the interpretation of spoken interactions.
 <!-- <p>It is not envisaged that events or kinesics should    --><!-- be included in any transcription, except where their     --><!-- presence is felt to be of potential significance for     --><!-- the interpretation of the interaction.                   --><!--                                                          -->
 <!-- delete following section? --><!-- added an example anyway  (LB dec 93)-->
 </p></div3><div3 id="TSBAWR" name="subsection" ref="Y"><head>Writing</head><p>Written text may also be encountered when speech is transcribed, for
example in a television broadcast or cinema performance, or where one
participant shows written text to another.  The <gi tei="yes">writing</gi> element
may be used to distinguish such written elements from the spoken text in
which they are embedded.
 
<tagList style="one-line"><tagDesc tagDoc="WRITING" atts="who gradual type"/></tagList>
 <!-- example needed -->
 
For example, if speaker A in the breakfast table conversation in section<xref target="TSBAUT"/>
 above had simply shown the newspaper passage to her
interlocutor instead of reading it, the interaction might have been
encoded as follows:
 
<eg><![CDATA[    <u who=A>look at this</u>
    <writing who=A gradual=N type=newspaper>
      The government is confident, he said, that the
      current economic problems will be completely overcome
      by June</writing>
    <u who=A>what nonsense!</u>]]></eg>
 </p></div3><div3 id="TSBATI" name="subsection" ref="Y"><head>Temporal Information</head><p>In addition to the global attributes <att tei="yes">n</att>, <att tei="yes">id</att>, and
<att tei="yes">lang</att>, utterances, vocals, pauses, kinesics, events and
writing elements may all take a common set of attributes providing
information about their position in time.  For this reason, these
elements are regarded as forming a <term>class</term>, referred to here
as <ident tei="yes" type="class">timed</ident>.  The following attributes are common
to all elements in this class:
 
<adList classDoc="TIMED" atts="start end dur"/>
 
Note that if <att tei="yes">start</att> and <att tei="yes">end</att> point to <gi tei="yes">when</gi>
elements whose temporal distance from each other is specified in a
timeline, then <att tei="yes">dur</att> is ignored.
 </p><p>The <gi tei="yes">anchor</gi> element (see <xref target="SACS"/>) may be used as
an alternative means of aligning the start and end of timed elements,
and is required when the temporal alignment involves points within an
element.
 </p></div3><div3 id="TSSASH" name="subsection" ref="Y"><head>Shifts</head><p>A common requirement in transcribing spoken language is to mark
positions at which a variety of prosodic features change.  Many
paralinguistic features (pitch, prominence, loudness, etc.) characterize
stretches of speech which are not co-extensive with utterances or any of
the other units discussed so far.  One simple method of encoding such
units is simply to mark their boundaries.  An empty element called
<gi tei="yes">shift</gi> is provided for this purpose.
 
<tagList style="one-line"><tagDesc tagDoc="SHIFT" atts="feature new"/></tagList>
 
A <gi tei="yes">shift</gi> element may appear within an utterance or a segment to
mark a significant change in the particular feature defined by its
attributes, which is then understood to apply to all subsequent
utterances for the same speaker, unless changed by a new shift for the
same feature in the same speaker.  Intervening utterances by other
speakers do not normally carry the same feature.
 
For example:
 
<eg><![CDATA[    <u who=LB><shift feature=loud new=f>Elizabeth</u>
    <u who=EB>Yes</u>
    <u who=LB><shift feature=loud>Come and try this <pause>
         <shift feature=loud new=ff>come on</u>]]></eg>
 
In this example, the word <cited>Elizabeth</cited> is spoken loudly, the
words <cited>Yes</cited> and <cited>Come and try this</cited> with
normal volume, and the words <cited>come on</cited> very loudly.
 </p><p>The values proposed here for the <att tei="yes">feature</att> attribute are
based on those used by the Survey of English Usage;
<note source="auth" place="display" anchored="Y">For details see <citation>S. Boase, <title>London-Lund
    Corpus:  Example Text and Transcription Guide</title> (London:
    Survey of English Usage, University College London,
    1990)</citation>.</note>
this list may be revised or supplemented using the methods outlined in
section <xref target="MD"/>.
 </p><p>The <att tei="yes">new</att> attribute specifies the new state of the feature
following the shift.  If no value is specified, it is implied that the
feature concerned ceases to be remarkable at this point:  the special
value <code tei="yes" type="val">normal</code> may be specified to have the same
effect.
 <!-- this rather abstruse point suppressed for now --><!--                                                          --><!-- < p>A <gi>shift</gi> itself can be aligned with other    --><!-- elements only by being pointed at from an alignment.     --><!-- If therefore alignment is expressed by pointing from     --><!-- the text, rather than into it, a <gi>ptr</gi> element    --><!-- following the < gi>shift</gi> should be used.  See       --><!-- further < xref target=TSSAPA>.                           --><!--                                                          -->
 </p><p>A list of suggested values for each of the features proposed follows:
 
<list type="simple"><item>tempo
<list type="gloss"><label>a    </label><item>allegro (fast)</item><label>aa   </label><item>very fast</item><label>acc  </label><item>accelerando (getting faster)</item><label>l    </label><item>lento (slow)</item><label>ll   </label><item>very slow</item><label>rall </label><item>rallentando (getting slower)</item></list></item><item>loud (for loudness):
<list type="gloss"><label>f     </label><item>forte (loud)</item><label>ff    </label><item>very loud</item><label>cresc </label><item>crescendo (getting louder)</item><label>p     </label><item>piano (soft)</item><label>pp    </label><item>very soft</item><label>dimin </label><item>diminuendo (getting softer)</item></list></item><item>pitch (for pitch range):
<list type="gloss"><label>high  </label><item>high pitch-range</item><label>low   </label><item>low pitch-range</item><label>wide  </label><item>wide pitch-range</item><label>narrow</label><item>narrow pitch-range</item><label>asc   </label><item>ascending</item><label>desc  </label><item>descending</item><label>monot </label><item>monotonous</item><label>scand </label><item>scandent, each succeeding syllable higher than
                   the last, generally ending in a falling tone</item></list></item><item>tension:
<list type="gloss"><label>sl  </label><item>slurred</item><label>lax </label><item>lax, a little slurred</item><label>ten </label><item>tense</item><label>pr  </label><item>very precise</item><label>st  </label><item>staccato, every stressed syllable being doubly
                 stressed</item><label>leg </label><item>legato, every syllable receiving more or less equal
                 stress</item></list></item><item>rhythm:
<list type="gloss"><label>rh   </label><item>beatable rhythm</item><label>arrh </label><item>arrhythmic, particularly halting</item><label>spr  </label><item>spiky rising, with markedly higher unstressed
                  syllables</item><label>spf  </label><item>spiky falling, with markedly lower unstressed
                  syllables</item><label>glr  </label><item>glissando rising, like spiky rising but the
                  unstressed syllables, usually several, also rise
                  in pitch relative to each other</item><label>glf  </label><item>glissando falling, like spiky falling but with the
                  unstressed syllables also falling in pitch relative
                  to each other</item></list></item><item>voice (for voice quality):
<list type="gloss"><label>whisp   </label><item>whisper</item><label>breath  </label><item>breathy</item><label>husk    </label><item>husky</item><label>creak   </label><item>creaky</item><label>fals    </label><item>falsetto</item><label>reson   </label><item>resonant</item><label>giggle </label><item>unvoiced laugh or giggle</item><label>laugh  </label><item>voiced laugh</item><label>trem   </label><item>tremulous</item><label>sob    </label><item>sobbing</item><label>yawn   </label><item>yawning</item><label>sigh   </label><item> sighing</item></list></item></list>
 </p><p>A full definition of the sense of the values provided for each
feature should be provided in the encoding description section of the
text header (see section <xref target="HD5"/>).
 </p></div3><div3 id="TSBAFD" name="subsection" ref="Y"><head>Formal Definition</head><p>The components of the tag set for transcribed speech are formally
defined as follows:
 
<dtdFrag id="DTSCOMP" n="Components of Transcribed Speech"><tagDecl tagDoc="U"/><tagDecl tagDoc="PAUSE"/><tagDecl tagDoc="VOCAL"/><tagDecl tagDoc="KINESIC"/><tagDecl tagDoc="EVENT"/><tagDecl tagDoc="WRITING"/><tagDecl tagDoc="SHIFT"/></dtdFrag>
 <?tei:EOF p2tsba.odd ??>

 <?tei:SOF p2tssa.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--**
    * $Log: p2tssa.odd,v $
    * Revision 1.10  1998/02/05 17:18:04  tei
    * *** empty log message ***
    *
    * Revision 1.9  98/02/05  17:14:35  tei
    * make examples parse
    * 
    * Revision 1.8  98/02/01  17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    * 
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.6  1994/03/27  21:46:39  msmcq
    * Correction of typos reported by DB, EB.
    * 
    * Revision 1.5  1994/02/17  20:29:04  msmcq
    * revision for SC review
    * -->
 <!-- Revisions:                                               --><!-- 18 jan 98 : LB : fix errors in egs --><!-- 4 Jan 98 : LB : it's <gap>, not <omit> stupid!           --><!-- 94-03-26 : MSM : typos, changes from EBr and DB          --><!-- 94-02-14 : MSM : more cleanup                            --><!-- 94-02-14 : MSM : minor cleanup                           --><!-- 94-02-14 : MSM : Added RCS id                            --><!-- 11 nov : LB : add material on segmentation, Pixi example --><!-- 20 aug : LB re-revise; rejig order somewhat              --><!-- 93-07-15 : DTL : revise in light of SAsy                 --><!-- 93-02-10 : MSM : correct typos in two xrefs              --><!-- 93-02-10 : MSM : suppress illegal EOF character          --><!-- 10 Feb 93 : WP : Changed 34 to 10.                       --><!--  4 Feb 93 : WP : Changed P234 to P2TS                    --><!-- 22f Apr 92 : CMSMcQ : final changes before release       --><!-- 18 Apr 92 : LB : fiddled with suggested value names for SHIFT --><!-- 18 Apr 92 : CMSMcQ : further changes, largely cosmetic --><!-- 17 Apr 92 : WP     : spellcheck & make changes         --><!-- 16 Apr 92 : CMSMcQ : repunctuate, prettify, clean      -->
 </p></div3></div2><div2 id="TSSA" name="subsection" ref="Y"><head>Elements Defined Elsewhere</head><p>This section describes the following features characteristic of
spoken texts for which elements are defined elsewhere in these
Guidelines:
 
<list type="simple"><item>segmentation below the utterance level</item><item>synchronization and overlap</item><item>regularization of orthography</item></list>
 
The elements discussed here are not provided by the base tag set for
spoken texts.  Some of them are included in the core tag set available
to all TEI documents, but others are contained in the TEI additional
tag sets for linking and for analysis respectively.  To enable these tag
sets, the appropriate parameter entities must be declared in the
document type declaration subset, as described in section <xref target="STIN"/>.  For example, if a transcript using the base tag set
defined in this chapter additionally wishes to make use of the
<gi tei="yes">timeLine</gi> element, then the following declarations would be
necessary:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.spoken   'INCLUDE' >
      <!ENTITY % TEI.linking  'INCLUDE'>
 ]>]]></eg>
 
If the complex segmentation elements defined in the additional tag set
for analysis were also required, the following declarations would be
needed:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.spoken   'INCLUDE'>
      <!ENTITY % TEI.linking  'INCLUDE'>
      <!ENTITY % TEI.analysis 'INCLUDE'>
 ]>]]></eg>
 <!-- I still think it's completely bonkers not to define timeline here. LB --></p><div3 id="TSSASE" name="subsection" ref="Y"><head>Segmentation</head><p>For some analytic purposes it may be desirable to subdivide the
divisions of a spoken text into units smaller than the individual
utterance or turn.  Segmentation may be performed for a number of
different purposes and in terms of a variety of speech phenomena.
Common examples include units defined both prosodically (by intonation,
pausing, etc.) and syntactically (clauses, phrases, etc.)  The term
<term>macrosyntagm</term> has been used by a number of researchers to
define units peculiar to speech transcripts.  <note source="auth" place="display" anchored="Y">The term was
apparently first proposed by <citation><author>Bengt Loman and Nils
J&oslash;rgensen</author>, in <title>Manual for analys och beskrivning
av makrosyntagmer</title> (Lund:  Studentlitteratur, 1971)</citation>,
where it is defined as follows:  <q>A text can be analysed as a sequence
of segments which are internally connected by a network of syntactic
relations and externally delimited by the absence of such relations with
respect to neighbouring segments.  Such a segment is a syntactic unit
called a macrosyntagm</q> (trans.  S. Johansson).</note></p><p>These Guidelines propose that such analyses be performed in terms of
neutrally-named <term>segments</term>, represented by the <gi tei="yes">seg</gi>
element, which is discussed more fully in section <xref target="SASE"/>.
This element may take a <att tei="yes">type</att> attribute to specify the kind of
segmentation applicable to a particular segment, if more than one is
possible in a text.  A full definition of the segmentation scheme or
schemes used should be provided in the <gi tei="yes">segmentation</gi> element of
the <gi tei="yes">editorialDecl</gi> element in the TEI header (see <xref target="HD53"/>).</p><p>In the first example below, an utterance has been segmented according
to a notion of syntactic completeness not necessarily marked by the
speech, although in this case a pause has been recorded between the two
sentence-like units.  In the second, the segments are defined
prosodically (an entity reference <code tei="yes" type="frag">&amp;amp;stress;</code>
has been used to mark the position immediately following the syllable
bearing the primary accent or stress), and may be thought of as
<soCalled>tone units</soCalled>.
 
<eg><![CDATA[<u who=M1><seg>we went to the pub yesterday</seg>
    <pause><seg>there was no one there</seg>
</u>
<u who=F1><seg>although its an old ide&stress;a</seg>
    <seg>it hasnt been on the mar&stress;ket very long</seg>
</u>]]></eg>
 <!-- examples from J Payne NERC Report -->
 
In either case, the <gi tei="yes">segmentation</gi> element in the header of the
text should specify the principles adopted to define the segments marked
in this way.</p><p>When utterances are segmented end-to-end in the same way as the
s-units in written texts, the <gi tei="yes">s</gi> element discussed in chapter<xref target="AI"/>
 may be used, either as an alternative or in addition to
the more general purpose <gi tei="yes">seg</gi> element.  The <gi tei="yes">s</gi> element
is available without formality in all texts, but does not allow segments
to nest within each other.
 <!-- need more specific xref --></p><p>Where segments of different kinds are to be distinguished within the
same stretch of speech, the <att tei="yes">type</att> attribute may be used, as in
the following example.  The example also shows the use of a
user-specified extension to the TEI tag sets, for specifying
paraphasia.
 
<eg><![CDATA[<text><body>
<u who=T1>
<seg type=C>I think </seg>
<seg type=C>this chap was writing </seg>
<seg type=C>and he <del type=repeated>said hello</del> said </seg>
<seg type=M>hello </seg>
<seg type=C>and he said </seg>
<seg type=C>I'm going to a <paraphasia>gate</paraphasia>
            at twenty past seven </seg>
<seg type=C>he said </seg>
<seg type=M>ok </seg>
<seg type=M>right away </seg>
<seg type=C>and so <gap desc=unclear extent='1'> on they went </seg>
<seg type=C>and they were <gap desc=unclear extent='3'>
            writing there </seg>
</u>
</body></text>]]></eg><!-- <note>Reference needed!</note>                           -->
 
In this example, recoded from a corpus of language-impaired speech
prepared by Fletcher and Garman, the speaker's utterance has been fully
segmented into clausal (<code tei="yes" type="frag">type=C</code>) or minor (<code tei="yes" type="frag">type=M</code>) units.  An additional element <gi tei="no">paraphasia</gi> has been used to define a particular
characteristic of this corpus for which no element exists in the TEI
scheme.
 <!--  removed because would need to put these into two separate --><!-- files (TEI.extensions.ent, TEI.extensions.dtd) and it would --><!-- take too long to explain here why. Probably. But should remember --><!-- to refer back to this e.g. in p2MD . (LB) --><!-- The following declarations might be added to the doctype subset --><!-- to effect the declaration of this element:  --><!-- ELEMENT paraphasia - - (%phraseSeq) --><!-- ENTITY % x.phrase "paraphasia|" -->
 
See further chapter <xref target="MD"/> for a discussion of the way in
which this kind of user-defined extension of the TEI scheme may be
performed and chapter <xref target="ST"/> for the mechanisms on which it
depends.</p><p>This example also uses the core elements <gi tei="yes">gap</gi> and
<gi tei="yes">del</gi> to mark editorial decisions concerning matter completely
omitted from the transcript (because of inaudibility), and words which
have been transcribed but which the transcriber considers may be
deleted, respectively.  See further section <xref target="COED"/> for a
discussion of these and related elements.</p><p>It is often the case that the desired segmentation does not respect
utterance boundaries; for example, syntactic units may cross utterance
boundaries.  For a detailed discussion of this problem, and the various
methods proposed by these Guidelines for handling it, see chapter<xref target="NH"/>
.  Methods discussed there include these:
 
<list type="simple"><item>a concurrent DTD may be defined</item><item><soCalled>milestone</soCalled> tags may be used;
the special-purpose <gi tei="yes">shift</gi> tag discussed
in section <xref target="TSSASH"/> is an extension of this method</item><item>where several discontinuous segments are to be grouped
together to form a syntactic unit (e.g. a phrasal verb with interposed
complement), the <gi tei="yes">join</gi> element may be used</item></list></p></div3><div3 id="TSSAPA" name="subsection" ref="Y"><head>Synchronization and Overlap</head><p>A major difference between spoken and written texts is the importance
of the temporal dimension to the former.  As a very simple example,
consider the following, first as it might be represented in a
playscript:
 
<eg><![CDATA[    Jane: Have you read Vanity Fair?
    Stig: Yes
    Lou: (nods vigorously)]]></eg>
 
Let us assume that Stig and Lou respond to Jane's question before she
has finished asking it --- a fairly normal situation in spontaneous
speech.  The simplest way of representing this <term>overlap</term>
would be to use the <att tei="yes">trans</att> attribute previously discussed:
 
<eg><![CDATA[<u who=Jane>have you read Vanity Fair</u>
<u who=Stig trans=overlap>yes</u>
<!-- ... -->]]></eg>
 
However, this does not allow us to indicate either the extent to which
Jane's utterance is overlapped, nor does it show that there are in
fact three things which are synchronous:  the end of Jane's utterance,
Stig's whole utterance, and Lou's kinesic.  To overcome these problems,
more sophisticated techniques, employing the mechanisms for pointing and
alignment discussed in detail in section <xref target="SASY"/>, are needed.
If the additional tag set for linking has been enabled (as described in
section <xref target="TSSASE"/> above), one way to represent the simple
example above would be as follows:
 
<eg><![CDATA[<text><body>
<u id=U1 who=Jane>have you read Vanity
   <anchor id=A1 synch='u2 k1'> Fair</u>
<u who=Stig id=U2>yes</u>
<kinesic id=K1 who=Lou iterated=Y desc=nod>
</body></text>]]></eg></p><p>For a full discussion of this and related mechanisms, section <xref target="SASYMP"/> should be consulted.  The rest of the present section,
which should be read in conjunction with that more detailed discussion,
presents a number of ways in which these mechanisms may be applied to
the specific problem of representing temporal alignment, synchrony or
overlap in transcribing spoken texts.</p><p>In the simple example above, the first utterance (that with
identifier u1) contains an <gi tei="yes">anchor</gi> element, the function of
which is simply to mark a point within it.  The <att tei="yes">synch</att>
attribute associated with this anchor point specifies the identifiers of
the other two elements which are to be synchronized with it:
specifically, the second utterance (u2) and the kinesic (k1).  Note that
one of these elements has content and the other is empty.</p><p>This example demonstrates only a way of indicating a point within one
utterance at which it can be synchronized with another utterance and a
kinesic.  For more complex kinds of alignment, involving possibly
multiple synchronization points, an additional element is provided,
known as a <gi tei="yes">timeLine</gi>.  This consists of a series of
<gi tei="yes">when</gi> elements, each representing a point in time, and bearing
attributes which indicate its exact temporal position relative to other
elements in the same timeline, in addition to the sequencing implied by
its position within it.</p><p>For example:
 
<eg><![CDATA[<timeLine unit=dsec>
   <when id=P1 absolute="12:20:01:01 BST">
   <when id=P2 interval=45 since=P1>
   <when id=P6>
   <when id=P3 interval=15 since=P6>
</timeLine>]]></eg>
 
This timeline represents four points in time, named P1, P2, P6, and P3
(as with all attributes named <att tei="yes">id</att> in the TEI scheme, the
names must be unique within the document but have no other
significance).  P1 is located absolutely, at 12:20:01:01 BST.  P2 is 4.5
seconds (i.e. 45 deci-seconds) later than P2 (i.e. at 12:20:46).  P6 is
at some unspecified time later than P2 and previous to P3 (this is
implied by its position within the timeline, as no attribute values have
been specified for it).  The fourth point, P3, is 1.5 seconds (15 dsec)
later than P6.</p><p>One or more such timelines may be specified within a spoken text, to
suit the encoder's convenience.  If more than one is supplied, the
<att tei="yes">origin</att> attribute may be used on each to specify which other
<gi tei="yes">timeLine</gi> element it follows.  The <att tei="yes">unit</att> attribute
indicates the units used for timings given on <gi tei="yes">when</gi> elements
contained by the alignment map.  Alternatively, to avoid the need to
specify times explicitly, the <att tei="yes">interval</att> attribute may be used
to indicate that all the <gi tei="yes">when</gi> elements in a time line are a
fixed distance apart.</p><p>Three methods are available for aligning points or elements within a
spoken text with the points in time defined by the <gi tei="yes">timeLine</gi>:
<list type="simple"><item>The elements to be synchronized may specify the identifier
of a <gi tei="yes">when</gi> element as the value of one of the <att tei="yes">start</att>,
<att tei="yes">end</att> or <att tei="yes">synch</att> attributes</item><item>The <gi tei="yes">when</gi>
element may specify the identifiers of all the elements to be
synchronized with it using the <att tei="yes">synch</att> attribute</item><item>A
free-standing <gi tei="yes">link</gi> element may be used to associate the
<gi tei="yes">when</gi> element and the elements synchronized with it by
specifying their identifiers as values for its <att tei="yes">target</att>
attribute.</item></list></p><p>For example, using the timeline given above:
 
<eg><![CDATA[<text><body>
     <u id=U1 start=P2 end=P3>
         This is my <anchor id=P6A synch=P6> turn
      </u>
</body></text>]]></eg>
 
The start of this utterance is aligned with P2 and its end with P3.  The
transition between the words <cited>my</cited> and <cited>turn</cited>
occurs at point P6A, which is synchronous with point P6 on the timeline.</p><p>The synchronization represented by the preceding examples could
equally well be represented as follows:
 
<eg><![CDATA[<text><body>
    <timeLine unit=dsec origin=P1>
     <when id=P1 absolute="12:20:01:01 BST">
     <when id=P2 interval=45 since=P1 synch=U1>
     <when id=P6 synch=X1>
     <when id=P3 interval=15 since=P6 synch=U1>
    </timeLine>
    <!-- ... -->
    <u id=U1>This is my <anchor id=X1> turn</u>
</body></text>]]></eg>
 
Here, the whole of the object with identifier U1 (the utterance) has
been aligned with two different points, P2 and P3.  This is interpreted
to mean that the utterance spans at least those two points.</p><p>Finally, a <gi tei="yes">linkGrp</gi> may be used as an alternative to the
<att tei="yes">synch</att> attribute:
 
<eg><![CDATA[<text><body>
    <timeLine unit=dsec origin=P1>
      <when id=P1 absolute="12:20:01:01 BST">
      <when id=P2 interval=45 since=P1>
      <when id=P6>
      <when id=P3 interval=15 since=P6>
    </timeLine>
   <!-- ... -->
    <u id=U1><anchor id=U1START>
             This is my <anchor id=X1> turn
             <anchor id=U1END>
   </u>
    <linkGrp type=synchronous>
        <link targets='U1start P1'>
        <link targets='U1end P2'>
        <link targets='X1 P6'>
    </linkGrp>
</body></text>]]></eg></p><p>As a further example of the three possibilities, consider the
following dialogue, represented first as it might appear in a
conventional playscript:
 
<eg><![CDATA[  Tom: I used to smoke - -
  Bob: (interrupting) You used to smoke?
  Tom: (at the same time) a lot more than this.  But I never
       inhaled the smoke]]></eg><!-- Atkinson and Heritage (1984) ix-xvi -->
 
A commonly used convention might be to transcribe such a passage as
follows:
 
<eg><![CDATA[  > I used to smoke [ a lot more than this ]
  <2>                 [ you used to smoke ]
  > but I never inhaled the smoke]]></eg>
 
Such conventions have the drawback that they are hard to generalize or
to extend beyond the very simple case presented here.  Their reliance on
the accidentals of physical layout may also make them difficult to
transport and to process computationally.  These Guidelines recommend
one of the courses described in what follows:</p><p>Where the whole of one or another utterance is to be synchronized,
the <att tei="yes">start</att> and <att tei="yes">end</att> attributes may be used:
 
<eg><![CDATA[<text><body>
  <u who=TOM>I used to smoke <anchor id=P1> a lot more than this
       <anchor id=P2>but I never inhaled the smoke</u>
  <u who=BOB start=P1 end=P2>You used to smoke</u>
</body></text>]]></eg>
 
Note that the second utterance above could equally well be encoded as
follows with exactly the same effect:
 
<eg><![CDATA[<u who=BOB><anchor synch=P1>You used to smoke<anchor synch=P2></u>]]></eg></p><p>If synchronization with specific timing information is required, a
<gi tei="yes">timeLine</gi> must be included:
 
<eg><![CDATA[<text><body>
  <timeLine origin=T1>
     <when id=T1>
     <when id=T2>
  </timeLine>
  <!--  .... -->
  <u who=TOM>I used to smoke
       <anchor synch=T1>a lot more than this
       <anchor synch=T2>but I never inhaled the smoke</u>
  <u who=BOB>
       <anchor synch=T1>You used to smoke<anchor synch=T2>
  </u>
</body></text>]]></eg></p><p>As above, since the whole of Bob's utterance is to be aligned, the
<att tei="yes">start</att> and <att tei="yes">end</att> attributes may be used as an
alternative to the second pair of <gi tei="yes">anchor</gi> elements:
 
<eg><![CDATA[<!-- ... -->
<u who=BOB start=T1 end=T2>You used to smoke</u>]]></eg></p><p>An alternative approach is to mark the synchronization by pointing
from the <gi tei="yes">timeLine</gi> to the text:
 
<eg><![CDATA[<text><body>
  <timeLine origin=T1>
     <when id=T1 synch='N1 U2'>
     <when id=T2 synch='N2 U2'>
  </timeLine>
  <!-- .... -->
  <u who=TOM>I used to smoke
       <anchor id=N1> a lot more than this
       <anchor id=N2>but I never inhaled the smoke</u>
  <u id=U2 who=BOB>You used to smoke</u>
</body></text>]]></eg>
 
To avoid deciding whether to point from the timeline to the text or vice
versa, a <gi tei="yes">linkGrp</gi> may be used:
 
<eg><![CDATA[<text><body>
  <timeLine origin=T1>
     <when id=T1>
     <when id=T2>
  </timeLine>
  <!-- ... -->
  <u who=TOM>I used to smoke
       <anchor id=N1> a lot more than this
       <anchor id=N2>but I never inhaled the smoke</u>
  <u id=U2 who=BOB>You used to smoke</u>
  !--- ... -->
  <linkGrp type=synchronize>
     <link targets='T1 N1 U2'>
     <link targets='T2 N2 U2'>
   </linkGrp>
</body></text>]]></eg></p><p>Note that in each case, although Bob's utterance follows Tom's
sequentially in the text, it is aligned temporally with its middle,
without any need to disrupt the normal syntax of the text.</p><p>As a final example, consider the following exchange, first as it
might be represented using a musical-score-like notation, in which
points of synchronization are represented by vertical alignment of the
text:
 
<eg rend="fig"><![CDATA[A : This is |my  |turn
B :         |Balderdash
C :         |No, |it's mine
 ]]></eg>
 
All three speakers are simultaneous at the words <cited>my</cited>,
<cited>Balderdash</cited>, and <cited>No</cited>; speakers A and C are
simultaneous at the words <cited>turn</cited> and <cited>it's</cited>.
This could be encoded as follows, using pointers from the alignment map
into the text:
 
<eg><![CDATA[<text><body>
<timeLine origin=P1>
    <when id=P1 synch='A1 B1 C1'>
    <when id=P2 synch='A2 C2'>
</timeLine>
   <!-- ... -->
<u who=A>this is <anchor id=A1> my <anchor id=A2> turn</u>
<u who=B id=B1>balderdash</u>
<u who=C id=C1> no <anchor id=C2> it's mine</u>
</body></text>]]></eg></p></div3><div3 id="TSREG" name="subsection" ref="Y"><head>Regularization of Word Forms</head><p>When speech is transcribed using ordinary orthographic notation, as
is customary, some compromise must be made between the sounds produced
and conventional orthography.  Particularly when dealing with informal,
dialectal or other varieties of language, the transcriber will
frequently have to decide whether a particular sound is to be treated as
a distinct vocabulary item or not.  For example, while in a given
project <cited>kinda</cited> may not be worth distinguishing as a
vocabulary item from <cited>kind of</cited>, <cited>isn't</cited> may
clearly be worth distinguishing from <cited>is not</cited>; for some
purposes, the regional variant <cited>isnae</cited> might also be worth
distinguishing in the same way.</p><p>One rule of thumb might be to allow such variation only where a
generally accepted orthographic form exists, for example, in published
dictionaries of the language register being encoded; this has the
disadvantage that such dictionaries may not exist.  Another is to
maintain a controlled (but extensible) set of normalized forms for all
such words; this has the advantage of enforcing some degree of
consistency among different transcribers.  Occasionally, as for example
when transcribing abbreviations or acronyms, it may be felt necessary to
depart from conventional spelling to distinguish between cases where the
abbreviation is spelled out letter by letter (e.g.  <cited>B B C</cited>
or <cited>V A T</cited>) and where it is pronounced as a single word
(<cited>VAT</cited> or <cited>RADA</cited>).  Similar considerations
might apply to pronunciation of foreign words
(e.g. <cited>Monsewer</cited> vs. <cited>Monsieur</cited>).</p><p>In general, use of punctuation, capitalization, etc., in spoken
transcripts should be carefully controlled.  It is important to
distinguish the transcriber's intuition as to what the punctuation
should be from the marking of prosodic features such as pausing,
intonation, etc.</p><p>Whatever practice is adopted, it is essential that it be clearly and
fully documented in the editorial declarations section of the header.
It may also be found helpful to include normalized forms of
non-conventional spellings within the text, using the elements for
simple editorial changes described in section <xref target="COED"/> (see
further section <xref target="TSTPSM"/>).</p></div3><div3 id="TSTPPR" name="subsection" ref="Y"><head>Prosody</head><p>In the absence of conventional punctuation, the marking of prosodic
features assumes paramount importance, since these structure and
organize the spoken message.  Indeed, such prosodic features as points
of primary or secondary stress may be represented by specialized
punctuation marks.  Pauses have already been dealt with in section<xref target="TSBAPA"/>
; while tone units (or intonational phrases) can be
indicated by the segmentation tag discussed in section <xref target="TSSASE"/>.  The shift tag discussed in section <xref target="TSSASH"/>
may also be used to encode some prosodic features, for example where all
that is required is the ability to record shifts in voice quality.</p><p>For more detailed work, involving a detailed phonological transcript
including representation of stress and pitch patterns, it is probably
best to maintain the prosodic description in parallel with the
conventional written transcript, rather than attempt to embed detailed
prosodic information within it.  The two parallel streams may be aligned
with each other and with other streams, for example an acoustic
encoding, using the general alignment mechanisms discussed in section<xref target="TSSASH"/>
.</p><p>Where only a small number of phonetic or phonemic aspects are
included in a transcript, it may be convenient to provide a simple set
of entity declarations for the particular set of features marked.  The
entity references in the text may then be redefined to produce simple
punctuation marks (as in the following example), or as references to
bundles of phonological features, in the same way as is proposed for
part of speech tags (see section <xref target="AILA"/>).</p><p>In the following example, a small set of prosodic features are
recorded throughout the transcript using a user-defined entity set such
as the following:
 
<eg><![CDATA[<!ENTITY lf ".">    <!-- low fall intonation -->
<!ENTITY fr ",">    <!-- fall rise intonation -->
<!ENTITY lr "?">    <!-- low rise intonation -->
<!ENTITY rf "!">    <!-- rise fall intonation -->
<!ENTITY trunc "-"> <!-- truncated syllable -->
<!ENTITY long ":">  <!-- lengthened syllable -->]]></eg>
 
This set of entity definitions may be included directly within the
document type declaration subset for the file, or more conveniently
along with any other extensions or modifications within the user
extensions file defined by the entity <ident tei="yes" type="pe">TEI.extensions.ent</ident>, as discussed in section <xref target="STIN"/>.  For convenience of reading on the screen, these entity
declarations will map the mnemonic entity names used in the text below
to a conventional punctuation mark.
 
<eg><![CDATA[<text><body>
<div type=exchange n="Lod E-03">
<note>C is with a friend</note>
<u who=Cwn>
   <unclear>Excuse me&lf;</unclear><pause>
   You dont have some aesthetic&trunc;
   <pause><unclear>specially on early</unclear>
   aesthetics terminology &lr;</u>
<u who=AJ>No&lf; <pause>No&lf;
   <gap extent='2'> I'm afraid&lf;</u>
<u who=Cwn trans=latching>No&lr;
    <unclear>Well</unclear> thanks&lr; <pause>
    Oh&trunc; <unclear>you couldnt&trunc can we</unclear>
    kind of&long; <pause>I mean ask you to order
    it for us&long;&fr;</u>
<u who=AJ trans=latching>Yes&fr;
   if you know the title&lf; Yeah&lf;</u>
<u who=Cwn>
   <gap extent='3'>
   <gap extent='4'></u>
<u who=AJ>Yes thats fine.
    <unclear>just as soon as it comes in we'll send you
    a postcard&lf</unclear></u>
</div></body></text>]]></eg>
 <!-- Recoded from Gavioli and Mansfield: The PIXI Corpora     --><!-- (Bologna, 1990, CLUEB), p74                              --></p><p>This example, which is taken from a corpus of bookshop service
encounters<note source="auth" place="display" anchored="Y"><citation><author>Laura Gavioli and Gillian
Mansfield</author>, <title>The Pixi Corpora</title> <detail>(Bologna:
Cooperativa Libraria Universitaria Editrice, 1990), p. 74.</detail></citation></note>
also demonstrates the use of the <gi tei="yes">unclear</gi> and <gi tei="yes">gap</gi>
elements discussed in section <xref target="COED"/>.  Where words are so
unclear that only their extent can be recorded, the empty <gi tei="yes">gap</gi>
element may be used; where the encoder can identify the words but wishes
to record a degree of uncertainty about their accuracy, the
<gi tei="yes">unclear</gi> element may be used.  More flexible and detailed
methods of indicating uncertainty are discussed in chapter <xref target="CE"/>.</p><p>Where a transcript includes many phonetic or phonemic aspects, it
will generally be convenient to use a specialized writing system, as
defined in chapters <xref target="CH"/> and <xref target="WD"/>.  For
representation of phonemic information, the use of the International
Phonetic Alphabet is recommended.</p></div3><div3 id="TSTPSM" name="subsection" ref="Y"><head>Speech Management</head><p>Phenomena of <term>speech management</term> include disfluencies such
as filled and unfilled pauses, interrupted or repeated words,
corrections, and reformulations as well as interactional devices asking
for or providing feedback.  Depending on the importance attached to such
features, transcribers may choose to adopt conventionalized
representations for them (as discussed in section <xref target="TSREG"/>
above), or to transcribe them using IPA or some other transcription
system.  To simplify analysis of the lexical features of a speech
transcript, it may be felt useful to <soCalled>tidy away</soCalled> many
of these disfluencies.  Where this policy has been adopted, these
Guidelines recommend the use of the tags for simple editorial
intervention discussed in section <xref target="COED"/>, to make explicit
the extent of regularization or normalization performed by the
transcriber.</p><p>For example, false starts, repetition, and truncated words might all
be included within a transcript, but marked as editorially deleted, in
the following way:
 
<eg><![CDATA[<del type=truncation>s</del>see
<del type=repetition>you you</del>you know
<del type=falseStart>it's</del>he's crazy]]></eg></p><p>As previously noted, the <gi tei="yes">gap</gi> element may be used to mark
points within a transcript where words have been omitted, for example
because they are inaudible:
 
<eg><![CDATA[ 
<gap extent='approx 10 sylls'
      reason='passing truck'>
 ]]></eg></p><p>The <gi tei="yes">unclear</gi> element may be used to mark words which have
been included although the transcriber is unsure of their accuracy:
 
<eg><![CDATA[ 
and then <unclear reason='passing truck'>marbled queen</unclear>
 ]]></eg></p><p>Where a transcriber is believed to have incorrectly identified a
word, the elements <gi tei="yes">corr</gi> or <gi tei="yes">sic</gi> may be used to indicate
both the original and a corrected form of it:
 
<eg><![CDATA[<sic corr="SCSI" resp=DD>skuzzy</sic>
<corr sic="skuzzy" resp=AGB>SCSI</corr>]]></eg>
 
As discussed in section <xref target="COEDCOR"/>, the first of these would
be appropriate where faithfulness to the transcribers' intuition is
paramount, and the second where the editorial interpretation is felt
more significant.  In either case, the user of the text can perceive the
basis of the choice being offered.
 <!-- delete following scandinavian para? --></p></div3><div3 id="TSTPAC" name="subsection" ref="Y"><head>Analytic Coding</head><p>The recommendations made here only concern the establishment of a
basic text.  Where a more sophisticated analysis is needed, more
sophisticated methods of markup will also be appropriate, for example,
using concurrent markup streams to indicate multiple segmentation of the
stream of discourse, or complex alignment of several segments within it.
Where additional annotations (sometimes called
<soCalled>codes</soCalled> or <soCalled>tags</soCalled>) are used to
represent such features as linguistic word class (noun, verb, etc.),
type of speech act (imperative, concessive, etc.), or information status
(theme/rheme, given/new, active/semi-active/new), etc., a selection from
the general purpose analytic tools discussed in chapters <xref target="SA"/>, <xref target="AI"/>, and <xref target="FS"/>, may be used to
advantage.</p><!-- As yet, however, we have been unable to find any         --><!-- consensus in the field as to what kinds of units should  --><!-- be identified at this level, and cannot therefore make   --><!-- more specific recommendations.  It is hoped however      --><!-- that the basic building blocks offered here will be      --><!-- serviceable in the expression of such a consensus when   --><!-- it is achieved.                                          --></div3></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2tssa.odd ??></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ts.odd ??><!-- 11 Spoken Texts --><!-- &p2.lm;             Letters and Memoranda --><?tei:SOF p2di.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $
    * --><!--*
    * $Log: p2di.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  94/04/01  16:21:35  msmcq
    * correct typo in bibl ref for Ide et al.
    * 
    * Revision 1.7  1994/03/27  16:29:18  lou
    * semi-hemi-demi final check
    * 
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    * 
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    * 
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    * 
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    * --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : correct typo in bibl entry for ide et al. --><!-- Revisions:                                               --><!-- 27 mar: LB checked all egs and terms --><!-- 94-01-12 : MSM : stylistic fixes                         --><!-- 94-01-12 : MSM : minor stylistic cleanups                --><!-- 94-01-09 : MSM : minor stylistic changes for P3          --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-03-08 : MSM : eliminate null character                --><!-- 93-03-08 : MSM : add entity refs for subsections         --><div1 id="DI" n="12" name="chapter" ref="Y"><head>Print Dictionaries</head><p>This chapter defines a base tag set for encoding human-oriented
monolingual and polyglot dictionaries (as opposed to computational
lexica, which are intended for use by language-processing software).
Dictionaries are most familiar in their printed form; however,
increasing numbers of dictionaries exist also in electronic forms which
are independent of any particular printed form, but from which various
displays can be produced --- e.g. CD-ROM dictionaries.
 <!-- <note place=foot>The primary responsibility for thischapter --><!-- was borne by TEI work group AI5 (print dictionaries); a list --><!-- of members is given in the front matter.  The text was --><!-- originally drafted by Nancy Ide and Jean Veronis; examples --><!-- and revisions were provided by other members of the work --><!-- group, including Nicoletta Calzolari, John Fought, and Carol --><!-- Van Ess-Dykema.</note> --></p><p>Both typographically and structurally, dictionaries are extremely
complex.  In addition, dictionaries interest many communities with
different and sometimes conflicting goals.  As a result, many general
problems of text encoding are particularly pronounced here, and more
compromises and alternatives within the encoding scheme may be required.
<note source="auth" place="foot" anchored="Y">We refer the reader to previous and current discussions
of a common format for encoding dictionaries.  For example,
 
Robert A. Amsler and Frank W. Tompa, <title.p>An SGML-Based Standard for
English Monolingual Dictionaries,</title.p> in <title>Information in
Text:  Fourth Annual Conference of the U[niversity of] W[aterloo] Centre
for the New Oxford English Dictionary</title> October 26-28, 1988,
Waterloo, Canada, pp. 61-79;
 
Nicoletta Calzolari et al., <title.p>Computational Model of the
Dictionary Entry:  Preliminary Report,</title.p> Acquilex:  Esprit Basic
Research Action No. 3030, Six-Month Deliverable, Pisa, April 1990;
 
John Fought and Carol Van Ess-Dykema, <title.p>Toward an SGML Document
Type Definition for Bilingual Dictionaries,</title.p> TEI working paper
TEI AIW20 (available from the TEI);
 
Nancy Ide and Jean Veronis, <title.p>Encoding Print
Dictionaries</title.p>, <title>Computers and the Humanities</title>
(special TEI issue --- to appear);
 
Nancy Ide, Jacques Le Maitre, and Jean Veronis, <title.p>Outline of a
Model for Lexical Databases,</title.p> (Information Processing and
Management, 29, 2, 159-186, 1993);
 
Nancy Ide, Jean Veronis, Susan Warwick- Armstrong, Nicoletta Calzolari,
<title.p>Principles for Encoding machine readable
dictionaries</title.p>, <title>Proceedings of the Fifth EURALEX
International Congress, EURALEX'92</title> (to appear), University of
Tempere, Finland;
 
and
 
The DANLEX Group, <title.p>Descriptive tools for electronic processing
of dictionary data,</title.p> in <title>Lexicographica, Series
Maior</title> (T&uuml;bingen:  Niemeyer, 1987).</note>
 
Two problems are particularly prominent.</p><p>First, because the structure of dictionary entries varies widely both
among and within dictionaries, the simplest way for an encoding scheme
to accommodate the entire range of structures actually encountered is to
allow virtually any element to appear virtually anywhere in a dictionary
entry.  It is clear, however, that strong and consistent structural
principles do govern the vast majority of conventional
dictionaries, as well as many or most entries even in more
<soCalled>exotic</soCalled> dictionaries; ideally, a set of encoding
guidelines should capture these structural principles.  We therefore
define two distinct elements for dictionary entries, one
(<gi tei="yes">entry</gi>) which captures the regularities of most conventional
dictionary entries, and a second (<gi tei="yes">entryFree</gi>) which uses the
same elements, but allows them to combine much more freely.  It is
recommended that <gi tei="yes">entry</gi> be used in preference to
<gi tei="yes">entryFree</gi> wherever the structure of the entry allows it.
 <!-- omitted sentence as redundant. -msm                      --><!-- The flexible but unconstrained encoding allowed by       --><!-- <gi>entryFree</gi> should be used parsimoniously.        -->
 
These elements and their contents are described in sections <xref target="DIEN"/>, <xref target="DIFR"/>, and <xref target="DIHW"/>.</p><p>Second, since so much of the information in printed dictionaries is
implicit or highly compressed, their encoding requires clear thought
about whether it is to capture the precise typographic form of
the source text or the underlying structure of the information it
presents. Since both of these views of the dictionary may be of
interest, it proves necessary to develop methods of recording both, and
of recording the interrelationship between them as well.  Users
interested mainly in the printed format of the dictionary will require
an encoding to be faithful to an original printed version.  However,
other users will be interested primarily in capturing the lexical
information in a dictionary in a form suitable for further processing,
which may demand the expansion or rearrangement of the information
contained in the printed form.  Further, some users wish to encode
<emph>both</emph> of these views of the data, and retain the links
between related elements of the two encodings.  Problems of recording
these two different views of dictionary data are discussed in section<xref target="DIMV"/>
, together with mechanisms for retaining both views
when this is desired.</p><p>Whichever view is adopted, a parameter entity
<ident tei="yes" type="pe">TEI.dictionaries</ident> must be declared within the
document type subset of any document using this base tag set. This
should have the value <code tei="yes" type="frag">INCLUDE</code>, as
further described in section <xref target="STIN"/>. A document using this
base tag set and no other additional tag sets will thus begin as
follows:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
 <!ENTITY % TEI.dictionaries 'INCLUDE' >
 ]>]]></eg>
 <?tei:SOF p2dibo.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2dibo.odd,v $
    * Revision 1.9  1998/01/31 17:17:18  tei
    * Fix log keyword
    *
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.7  1994/04/01  16:21:35  msmcq
    * protect teistr reference in marked section, define dimix
    * 
    * Revision 1.6  1994/03/27  16:29:31  lou
    * *** empty log message ***
    * 
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    * 
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    * 
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    * 
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : add "especially" per 1996-05-13 CMSMCQ --><!-- 94-03-31 : MSM : protect teistr invocation               --><!-- 94-03-31 : MSM : define dimix                            --><!-- 94-01-15 : MSM : change comment in dtd frag              --><!-- 94-01-13 : MSM : correct example:  body not GI body      --><!-- 94-01-12 : MSM : suppress duplicated inclusion of tpde   --><!-- 94-01-12 : MSM : minor stylistic fixes                   --><!-- 94-01-12 : MSM : suppress call to dummy dtdfrag for notes --><!-- 94-01-12 : MSM : clean reference to tei.structure.dtd    --><!-- 94-01-12 : MSM : correct dtdFrag id dDIhw                --><!-- 94-01-09 : MSM : work at cleaning up dtd fragments       --><!-- 94-01-08 : MSM : add commentary to examples              --><!-- 93-10-19 : MSM : preliminary rough cleanup               --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-06-04 : MSM : call class compdict not dicomp          --><!-- 93-03-11 : MSM : make taglists, dtdfrags                 --><!-- 93-03-08 : MSM : correct mkd sectn openings l 81 108     -->
 </p><div2 id="DIBO" name="subsection" ref="Y"><head>Dictionary Body and Overall Structure</head><p>Overall, dictionaries have the same structure of front matter, body,
and back matter familiar from other texts; the base tag set for
dictionaries uses the same front-matter and back-matter elements as
other TEI base tag sets; these are documented in chapter <xref target="DS"/>.  In addition, dictionaries define the elements
<gi tei="yes">entry</gi>, <gi tei="yes">entryFree</gi>, and <gi tei="yes">superEntry</gi> as
component-level elements which can occur directly within a text division
or the text body.
 </p><p>The following tags should be used to mark the gross structure of a
printed dictionary; the dictionary-specific tags are discussed further
in the following section.
 
<tagList style="one-line"><tagDesc tagDoc="TEXT"/><tagDesc tagDoc="FRONT"/><tagDesc tagDoc="BODY"/><tagDesc tagDoc="BACK"/><tagDesc tagDoc="DIV"/><tagDesc tagDoc="DIV0"/><tagDesc tagDoc="DIV1"/><tagDesc tagDoc="ENTRY"/><tagDesc tagDoc="ENTRYFR"/><tagDesc tagDoc="SUPENTRY"/></tagList>
 
The text-division elements <gi tei="yes">div2</gi> through <gi tei="yes">div7</gi> may also
be used, as described in chapter <xref target="DS"/>.
 </p><p>As members of the class <ident tei="yes" type="class">entries</ident>,
<gi tei="yes">entry</gi> and <gi tei="yes">entryFree</gi> share the following attributes:
 
<adList classDoc="ENTRIES" atts="type key"/>
 </p><p>The front and back matter of a dictionary may well contain
specialized material like lists of common and proper nouns, grammatical
tables, gazetteers, a <soCalled>guide to the use of the
dictionary</soCalled>, etc.  These may be tagged as elements defined in
the core tag set (chapter <xref target="CO"/>) or as specialized dictionary
elements as defined in this chapter.
 </p><p>The <gi tei="yes">body</gi> element consists of a set of <term>entries</term>,
optionally grouped into one or several <gi tei="yes">div</gi>, <gi tei="yes">div0</gi>, or
<gi tei="yes">div1</gi> elements.  These text divisions might correspond, for
example, to sections for different languages in bilingual
dictionaries, sections for different letters of the alphabet, etc.<note source="auth" place="foot" anchored="Y">It is unlikely that many conventional dictionaries will
require smaller divisions, but all the usual division elements
<gi tei="yes">div2</gi> through <gi tei="yes">div7</gi> may be used.</note> In print
dictionaries, entries are typically typographically distinct entities,
each headed by some morphological form of the lexical item described
(the <term>headword</term>), and sorted in alphabetical order or
(especially for non-alphabetic scripts) in some other conventional sequence.
Dictionary entries should be encoded as distinct successive items, each
marked as an <gi tei="yes">entry</gi> element.  The <att tei="yes">type</att> attribute may
be used to distinguish different types of entries, for example main
entries, related entries, run-on entries, or entries for
cross-references, etc.
 </p><p>Some dictionaries provide distinct entries for homographs, on the
basis of etymology, part-of-speech, or both, and typically provide a
numeric superscript on the headword identifying the homograph number.
In these cases each homograph should be encoded as a separate entry; the
<gi tei="yes">superEntry</gi> element may optionally be used to group such
successive homograph entries.  In addition to a series of <gi tei="yes">entry</gi>
elements, the <gi tei="yes">superEntry</gi> may contain a preliminary <gi tei="yes">form</gi>
group (see section <xref target="DITPFO"/>) when information about
hyphenation, pronunciation, etc., is given only once for two or more
homograph entries.  If the homograph number is to be recorded, the
global attribute <att tei="yes">n</att> should be used for this purpose.  In
some dictionaries, homographs are treated in distinct parts of the same
entry; in these cases, they may be separated by use of the <gi tei="yes">hom</gi>
element, for which see section <xref target="DIENHI"/>.
 </p><p>A sort key, given in the <att tei="yes">key</att> attribute, is often required
for superentries and entries, especially in cases where the order of
entries does not follow the local character-set collating sequence (as,
for example, when an entry for <q>3D</q> appears at the place where
<q>three-D</q> would appear).
 </p><p>The body of a bilingual dictionary with two parts will thus have an
overall structure resembling the following:
 
<eg><![CDATA[<body>
  <div0 type='dictionary'>
    <!-- English-French -->
    <entry>...</entry>
    <entry>...</entry>
    <entry>...</entry>
  <!-- ... -->
  </div0>
  <div0>
    <!-- French-English -->
    <entry>...</entry>
    <entry>...</entry>
    <entry>...</entry>
  <!-- ... -->
  </div0>
</body>]]></eg>
 </p><p>A dictionary with no internal divisions might have a structure like
the following; a <gi tei="yes">superEntry</gi> is shown grouping two homograph
entries.
 
<eg><![CDATA[<body>
  <entry>...</entry>
  <entry>...</entry>
  <!-- ... -->
  <superEntry>
    <entry type=hom n='1'>...</entry>
    <entry type=hom n='2'>...</entry>
  </superEntry>
  <!-- ... -->
</body>]]></eg>
 </p><p>The base tag set for dictionaries is contained in the files <ident tei="yes" type="file">teidict2.ent</ident> and <ident tei="yes" type="file">teidict2.dtd</ident>.  The first of these defines the class
<ident tei="yes" type="class">comp.dictionaries</ident>, so that the generic
text-division elements <gi tei="yes">div</gi>, <gi tei="yes">div0</gi>, <gi tei="yes">div1</gi>,
etc. can contain <gi tei="yes">entry</gi> elements:
 
<dtdFrag id="DDIENTS" n="Element classes for dictionary base" file="teidict2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>First we define attributes available on all the elements in
this tag set.</commDecl><dtdRef dtdFrag="DEDIMV"/><commDecl>Next we define comp.dictionaries, which will be used in the
declaration of component, within file TEI2.DTD.</commDecl><claDecl classDoc="COMPDICT" type="model"/><entDecl entDoc="DIMIX"/><commDecl>Next, we declare some specialized element
classes, used in various content models in the dictionary
tag set.</commDecl><claDecl classDoc="ENTRIES" type="atts"/><dtdRef dtdFrag="DEDIEN"/><dtdRef dtdFrag="DEDITPFO"/><dtdRef dtdFrag="DEDITPGR"/><dtdRef dtdFrag="DEDIHW"/><dtdRef dtdFrag="DEDIFR"/></dtdFrag>
 
The dictionary-specific elements are all declared in the file
<ident tei="yes" type="file">teidict2.dtd</ident>, which has the following
overall structure.
 
<dtdFrag id="DDIBO" n="Base tag set for printed dictionaries" file="teidict2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>First we embed the default text structure.</commDecl><msection keywords="%TEI.singleBase"><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></msection><commDecl>Now we define the dictionary-specific material.</commDecl><dtdRef dtdFrag="DDIEN"/><dtdRef dtdFrag="DDITPFO"/><dtdRef dtdFrag="DDITPGR"/><dtdRef dtdFrag="DDITPDE"/><dtdRef dtdFrag="DDITPTR"/><dtdRef dtdFrag="DDITPET"/><dtdRef dtdFrag="DDITPEG"/><dtdRef dtdFrag="DDITPUS"/><dtdRef dtdFrag="DDITPXR"/><dtdRef dtdFrag="DDITPRE"/><dtdRef dtdFrag="DDIHW"/></dtdFrag>
 <?tei:EOF p2dibo.odd ??>
<?tei:SOF p2dien.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2dien.odd,v $
# Revision 1.7  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.6  1994/03/27  16:29:37  lou
# *** empty log message ***
#
# Revision 1.5  1994/03/07  15:19:03  lou
# fix ^Z
#
# Revision 1.4  1994/03/07  14:44:05  lou
# apply typos etc. noted by DTB et al.
#
# Revision 1.3  1994/01/15  20:45:31  msmcq
# cmsmcq revision for P3
# see comments for details
#
# Revision 1.2  1994/01/04  19:38:25  msmcq
# first cut at DI revisions
# --><!-- Revisions:                                               --><!-- 7 jan 98 : LB : fix typos from msm --><!-- 94-01-15 : MSM : add biblio info for WNC                 --><!-- 94-01-14 : MSM : explicit end-tag in a SENSE             --><!-- 94-01-13 : MSM : in EGs, replace & in PRONs with &amp    --><!-- 94-01-13 : MSM : add supentry to dtd frag                --><!-- 94-01-12 : MSM : minor stylistic fixes                   --><!-- 94-01-12 : MSM : trans not transl, dieg not eg, diengp   --><!-- 94-01-08 : MSM : attempt to clarify structure,           --><!--                  define classes clearly,                 --><!--                  clean up dtd fragments,                 --><!--                  weed out expendible examples,           --><!--                  explain significance of examples        --><!-- 94-01-05 : MSM : in pronunciation, replace & by amp      --><!-- 93-10-19 : MSM : quick rough cleanup                     --><!-- 93-10-19 : MSM : change hn attribute to n                --><!-- 93-10-19 : MSM : change sn attribute to n                --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-04-12 : MSM : rename gram as digram                   --><!-- 93-03-11 : MSM : make taglists and dtdfrags              --><!-- 93-03-08 : MSM : change C&R to C/R (no entity)           -->
 </p></div2><div2 id="DIEN" name="subsection" ref="Y"><head>The Structure of Dictionary Entries</head><p>A simple dictionary entry may contain information about the form of
the word treated, its grammatical characterization, its definition,
synonyms, or translation equivalents, its etymology, cross-references to
other entries, usage information, and examples.  These we refer to as
the <term>constituent parts</term> or <term>constituents</term> of the
entry; some dictionary constituents possess no internal structure, while
others are most naturally viewed as groups of smaller elements, which
may be marked in their own right.  In some styles of markup, tags will
be applied only to the low-level items, leaving the constituent groups
which contain them untagged.  We distinguish the class of
<term>top-level constituents</term> of dictionary entries, which can
occur directly within entries, from the class of
<term>phrase-level</term> constituents, which can normally occur only
within top-level constituents.  The top-level constituents of dictionary
entries are described in section <xref target="DIENGP"/>, and documented
more fully, together with their phrase-level sub-constituents, in
section <xref target="DITP"/>.
 </p><p>In addition, however, dictionary entries often have a complex
hierarchical structure.  For example, an entry may consist of two or
more sub-parts, each corresponding to information for a different
part-of-speech homograph of the headword.  The entry (or part-of-speech
homographs, if the entry is split this way) may also consist of senses,
each of which may in turn be composed of two or more sub-senses, etc.
Each sub-part, homograph entry, sense, or sub-sense we call a
<term>level</term>; at any level in an entry, any or all of the
constituent parts of dictionary entries may appear.  The hierarchical
levels of dictionary entries are documented in section <xref target="DIENHI"/>.
 </p><div3 id="DIENHI" name="subsection" ref="Y"><head>Hierarchical Levels</head><p>The outermost structural level of an entry is marked with the
elements <gi tei="yes">entry</gi> or <gi tei="yes">entryFree</gi>.  The <gi tei="yes">hom</gi> element
marks the subdivision of entries into part-of-speech homographs.  The
<gi tei="yes">sense</gi> element marks the subdivision of entries and
part-of-speech homographs into senses; this element nests recursively in
order to provide for a hierarchy of sub-senses of any depth.  All of
these levels may each contain any of the constituent parts of an entry.
A special case of hierarchical structure is represented by the
<gi tei="yes">re</gi> (related entry) element, which is discussed in section <xref target="DITPRE"/>.
 
<tagList style="one-line"><tagDesc tagDoc="ENTRY"/><tagDesc tagDoc="ENTRYFR"/><tagDesc tagDoc="HOM"/><tagDesc tagDoc="SENSE" atts="level"/></tagList>
 </p><p>For example, an entry with two senses will have the following
structure:
 
<eg><![CDATA[<entry>
  <!-- ... information common to both senses -->
  <sense n='1'>
     <!-- ... sense number 1 -->
  </sense>
  <sense n='2'>
     <!-- ... sense number 2 -->
  </sense>
</entry>]]></eg>
 </p><p>An entry with two homographs, the first with two senses and the
second with three (one of which has two sub-senses), may have a
structure like this:
 
<eg><![CDATA[<entry>
  <!-- ... information common to both homographs, if any ... -->
  <hom n='1'>
    <sense n='1'>...</sense>
    <sense n='2'>...</sense>
  </hom>
  <hom n='2'>
    <sense n='1'>
      <sense n='a'>...</sense>
      <sense n='b'>...</sense>
    </sense>
    <sense n='2'>...</sense>
    <sense n='3'>...</sense>
  </hom>
</entry>]]></eg>
 
In some dictionaries, homographs typically receive separate entries; in
such a case, as noted in section <xref target="DIBO"/>, the two homographs
may be treated as entries, optionally grouped by a superentry:
 
<eg><![CDATA[<superEntry>
<!-- ... form information common to both
     homographs, if any ... -->
<entry n='1'>
  <sense n='1'>...</sense>
  <sense n='2'>...</sense>
</entry>
<entry n='2'>
  <sense n='1'>
    <sense n='a'>...</sense>
    <sense n='b'>...</sense>
  </sense>
  <sense n='2'>...</sense>
  <sense n='3'>...</sense>
</entry>
</superEntry>]]></eg>
 </p><p>The hierarchical levels of dictionary entries are declared as shown
in the following DTD fragment.  As may be seen, the content model for
<gi tei="yes">entry</gi> specifies that entries do not nest, that homographs nest
within entries, and that senses nest within entries, homographs, or
senses, and may be nested to any depth to reflect the embedding of
sub-senses.  Any of the top-level constituents (<gi tei="yes">def</gi>,
<gi tei="yes">usg</gi>, <gi tei="yes">form</gi>, etc.) can appear at any level (i.e., within
entries, homographs, or senses).
 <!-- Note that elements of class <term>formptrs</term> can    --><!-- appear anywhere (see section <xref target=DIHW>.         -->
 
 
<dtdFrag id="DDIEN" n="Dictionary entries and their structure"><tagDecl tagDoc="SUPENTRY"/><tagDecl tagDoc="ENTRY"/><tagDecl tagDoc="ENTRYFR"/><tagDecl tagDoc="HOM"/><tagDecl tagDoc="SENSE"/></dtdFrag>
 </p></div3><div3 id="DIENGP" name="subsection" ref="Y"><head>Groups and Constituents</head><p>As noted above, dictionary entries, and subordinate levels within
dictionary entries, may comprise several constituent parts, each
providing a different type of information about the word treated.  The
<term>top-level constituents</term> of dictionary entries are:
 
<list type="bullets"><item>information about the form of the word treated (orthography,
pronunciation, hyphenation, etc.)</item><item>grammatical information (part of speech, grammatical
sub-categorization, etc.)</item><item>definitions or translations into another language</item><item>etymology</item><item>examples</item><item>usage information</item><item>cross-references to other entries</item><item>notes</item><item>entries (often of reduced form) for related words,
typically called <term>related entries</term></item></list>
 
Any of the hierarchical levels (<gi tei="yes">entry</gi>, <gi tei="yes">entryFree</gi>,
<gi tei="yes">hom</gi>, <gi tei="yes">sense</gi>) may contain any of these top-level
constituents, since information about word form, particular grammatical
information, special pronunciation, usage information, etc., may apply
to an entire entry, or to only one homograph, or only to a particular
sense.  The examples below illustrate this point.
 </p><p>The following elements are used to encode these top-level
constituents:
<tagList style="one-line"><tagDesc tagDoc="FORM"/><tagDesc tagDoc="GRAMGRP"/><tagDesc tagDoc="DEF"/><tagDesc tagDoc="TRANS"/><tagDesc tagDoc="DIEG"/><tagDesc tagDoc="USG"/><tagDesc tagDoc="XR"/><tagDesc tagDoc="ETYM"/><tagDesc tagDoc="RE"/><tagDesc tagDoc="NOTE"/></tagList>
 </p><p>In a simple entry with no internal hierarchy, all top-level
constituents appear at the <gi tei="yes">entry</gi> level.
 
<note source="auth" place="foot" anchored="Y"> 
Each example taken from a real dictionary indicates its source using
the following abbreviations for dictionary names:
 
<list type="gloss"><label>C/R </label><item>Beryl T. Atkins et al., <title>Collins Robert
French-English English-French Dictionary</title> (London:
Collins, 1978, rpt. 1983)
 </item><label>CED   </label><item>Collins English Dictionary
 </item><label>CP    </label><item>Collins Pocket
 </item><label>DNT   </label><item><title>Le Dictionnaire de Notre Temps 1990</title>,
ed. Franc,,oise Guerard (Paris:  Hachette, 1990).
 </item><label>LDOCE </label><item>Longman Dictionary of Contemporary English
 </item><label>NPEG  </label><item><title>The New Penguin English Dictionary</title>
(London:  Penguin, 1986, rpt. 1987).
 </item><label>OALD  </label><item><title>Oxford Advanced Learner's Dictionary of
Current English</title>, ed. A. S. Hornby with A. P. Cowie and A. C.
Gimson ([Oxford]:  Oxford University Press, 1974).
 </item><label>PLC   </label><item><title>Petit Larousse en Couleurs</title> (Paris:
Larousse, 1990).
 </item><label>PLI   </label><item><title>Peque&ntilde;o Larousse Illustrado</title> por
Ramo''n Garci''a-Pelayo y Gross (Buenos Aires, Me''xico, Paris:
Ediciones Larousse, 1964).
 </item><label>PR    </label><item>Le Petit Robert
 </item><label>SSSE </label><item><title>Simon and Schuster's International Dictionary
English/Spanish Spanish/English</title> ed. Tana de G&aacute;mez (New
York:  Simon and Schuster, 1973).
 </item><label>W7    </label><item>Webster's 7th Collegiate
 </item><label>WNC   </label><item><title>Webster's New Collegiate Dictionary</title>
(Springfield, Mass.:  G. &amp; C. Merriam Co., 1975).
 </item></list>
 
To simplify the electronic presentation of this document on systems with
limited character sets, many of the pronunciations are presented using
the transliteration found in the electronic edition of the <title>Oxford
Advanced Learner's Dictionary</title>.  Also, the middle dot in quoted
entries is rendered with a full stop, while within the sample
transcriptions hyphenation and syllabification points are indicated with
<code tei="yes" type="frag">|</code>, regardless of their rendition in the source text.</note>
 
<q rend="display"> <hilited rend="bold">com.peti.tor</hilited>
<code tei="yes" type="frag">/k@m"petit@(r)/</code> n person who competes. [OALD] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>competitor</orth>
    <hyph>com|peti|tor</hyph>
    <pron>k@m"petit@(r)</pron>
  </form>
  <gramGrp>
    <pos>n</pos>
  </gramGrp>
  <def>person who competes.</def>
</entry>]]></eg>
 
For the elements which appear within the <gi tei="yes">form</gi> and <gi tei="yes">gramGrp</gi>
elements of this example, see below, section <xref target="DITPFO"/>, and
section <xref target="DITPGR"/>.
 </p><p>As mentioned above, any top-level constituent can appear at any level
when the hierarchical structure of the entry is more complex.  The most
obvious examples are <gi tei="yes">def</gi> and <gi tei="yes">trans</gi>, which appear at the
<gi tei="yes">sense</gi> level when several senses or translations exist:
 
<q rend="display"> <hilited rend="bold">disproof</hilited> <code tei="yes" type="frag">(dIs"pru:f)</code> n. 1. facts that disprove something. 2. the act of
disproving. [CED] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>disproof</orth>
    <pron>dIs"pru:f</pron>
  </form>
  <gramGrp><pos>n</></gramGrp>
  <sense n='1'><def>facts that disprove something.</def></sense>
  <sense n='2'><def>the act of disproving.</def></sense>
</entry>]]></eg>
 </p><p>In the following example, <gi tei="yes">gramGrp</gi> is used to distinguish two
homographs:
 
<q rend="display"> <hilited rend="bold">bray</hilited> <code tei="yes" type="frag">/breI/</code> n cry of an ass; sound of a trumpet. &squf; vt [VP2A] make a
cry or sound of this kind.  [OALD] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>bray</orth>
    <pron>breI</pron>
  </form>
  <hom>
    <gramGrp><pos>n</pos></gramGrp>
    <def>cry of an ass; sound of a trumpet.</def>
  </hom>
  <hom>
    <gramGrp>
      <pos>vt</pos>
      <subc>VP2A</subc>
    </gramGrp>
    <def>make a cry or sound of this kind.</def>
  </hom>
</entry>]]></eg>
 </p><p>Information of the same kind can appear at different levels within
the same entry; here, grammatical information occurs both at entry and
homograph level.
 
<q rend="display"> <hilited rend="bold">ca.reen</hilited> <code tei="yes" type="frag">/k@"ri:n/</code> vt,vi 1 [VP6A] turn (a ship) on one side for cleaning,
repairing, etc. 2 [VP6A, 2A] (cause to) tilt, lean over to one side.
[OALD] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>careen</orth>
    <hyph>ca|reen</hyph>
    <pron>k@"ri:n</pron>
  </form>
  <gramGrp>
    <pos>vt</pos>
    <pos>vi</pos>
  </gramGrp>
  <sense n='1'>
    <gramGrp><subc>VP6A</subc></gramGrp>
    <def>turn (a ship) on one side for cleaning,
         repairing, etc.</def>
  </sense>
  <sense n='2'>
    <gramGrp>
      <subc>VP6A</subc>
      <subc>VP2A</subc>
    </gramGrp>
    <def>(cause to) tilt, lean over to one side.</def>
  </sense>
</entry>]]></eg>
 <!-- suppress:  supererogatory
<q rend=display>
conjure <code>("kVndZ@) </code> vb 1. to practice conjuring. 2. to
summon (a spirit or demon) by magic. 3. <code>(k@n"dGU@) </code> to
appeal earnestly to ... [CP] </q>
 
<eg>
<![ CDATA [
<entry>
  <form>
    <orth>conjure</orth>
    <pron>"kVndZ@</pron>
  </form>
  <gramGrp>
    <pos>vb</pos>
  </gramGrp>
  <sense n='1'>
    <def>to practice conjuring.</def>
  </sense>
  <sense n='2'>
    <def>to summon (a spirit or demon) by magic.</def>
  </sense>
  <sense n='3'>
    <form>
      <pron>k@n"dGU@</pron>
    </form>
    <def>to appeal earnestly to</def>
  <! - - ...  - - >
</entry>
 
]]>
</eg>
-->
 </p><p>Alone among the constituent groups, <gi tei="yes">form</gi> can appear at the
<gi tei="yes">superEntry</gi> level as well as at the <gi tei="yes">entry</gi>,
<gi tei="yes">hom</gi>, and <gi tei="yes">sense</gi> levels:
 
<q rend="display"> <hilited rend="bold">a.ban.don</hilited> 1
<code tei="yes" type="frag">/@"b&amp;amp;nd@n/ </code> v [T1] 1 to leave completely and for
ever; desert: The sailors abandoned the burning ship. 2 ...

<hilited rend="bold">abandon</hilited> 2 n [U] the state when one's
feelings and actions are uncontrolled; freedom from control: The
people were so excited that they jumped and shouted with abandon / in
gay abandon.  [LDOCE] </q>
 
<eg><![CDATA[<superEntry>
  <form>
    <orth>abandon</orth>
    <hyph>a|ban|don</hyph>
    <pron>@"b&amp;nd@n</pron>
  </form>
  <entry n='1'>
    <gramGrp> <pos>v</pos> <subc>T1</subc> </gramGrp>
    <sense n='1'><def>to leave completely and for ever ...</def>
      <!-- ... -->
    </sense>
    <sense n='2'>
      <!-- ... -->
    </sense>
  </entry>
  <entry n='2'>
    <gramGrp> <pos>n/pos> <subc>U</subc> </gramGrp>
    <def>the state when one's feelings and actions are
            uncontrolled; freedom from control</def>
    <!-- ... -->
  </entry>
</superEntry>]]></eg>
 </p><p>The class of top-level constituents for dictionary entries is defined
by the following DTD fragment:
 
<dtdFrag id="DEDIEN" n="Class for top-level structure of dictionary entries"><claDecl classDoc="DITOPLEV" type="model"/></dtdFrag>
 </p><p>The individual constituents are declared below, each in the section
which documents it in more detail.
 <?tei:EOF p2dien.odd ??>
<?tei:SOF p2ditp.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2ditp.odd,v $
# Revision 1.9  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.8  1994/04/07  23:55:41  msmcq
# some Script-motivated line breaks
#
# Revision 1.7  1994/03/27  16:29:49  lou
# *** empty log message ***
#
# Revision 1.6  1994/03/07  15:19:03  lou
# fix ^Z
#
# Revision 1.5  1994/03/07  14:44:05  lou
# apply typos etc. noted by DTB et al.
#
# Revision 1.4  1994/02/07  20:39:03  msmcq
# msmcq cumulation end January 1994
#
# Revision 1.3  1994/01/15  20:45:31  msmcq
# cmsmcq revision for P3
# see comments for details
#
# Revision 1.2  1994/01/04  19:38:25  msmcq
# first cut at DI revisions
# --><!-- Revisions:                                               --><!-- 12 jan 98 : LB : add missing </sense> in Corneille eg --><!-- 7 jan 98 : LB : fix typos from MSM --><!-- 94-04-07 : MSM : rebreak some lines (Script problem)     --><!-- 94-02-01 : MSM : suppress triangle entity                --><!-- 94-01-15 : MSM : miscellaneous minor typos               --><!-- 94-01-15 : MSM : change dtdfrag title                    --><!-- 94-01-14 : MSM : correct typo in xref to madrigal.1      --><!-- 94-01-13 : MSM : supply explicit /sense in EGs           --><!-- 94-01-13 : MSM : replace ampersands in PRONs with &amp   --><!-- 94-01-12 : MSM : suppress duplicated declaration of gram --><!-- 94-01-12 : MSM : stylistic fixes                         --><!-- 94-01-12 : MSM : DIeg not EG, add entity dtdfrag for graminfo --><!-- 94-01-12 : MSM : number not num                          --><!-- 94-01-11 : MSM : resume work with gram section, complete --><!-- 94-01-09 : MSM : reorder and attempt to clarify          --><!-- 94-01-05 : MSM : fix entity typos, bad comment           --><!-- 94-01-05 : MSM : replace hi with hilited, & with &amp    --><!-- 94-01-05 : MSM : replace ital, bold with hi              --><!-- 93-10-19 : MSM : rename tgt as te                        --><!-- 93-10-19 : MSM : change sn attribute to n                --><!-- 93-10-19 : MSM : change hn attribute to n                --><!-- 93-10-19 : MSM : clean examples                          --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-04-12 : MSM : rename gram as digram                   --><!-- 93-04-12 : MSM : delete N att on divs                    --><!-- 93-03-08 : MSM : eliminate funny character (check for lost data!) -->
 </p></div3></div2><div2 id="DITP" name="subsection" ref="Y"><head>Top-level Constituents of Entries</head><p>This section describes the top-level constituents of dictionary
entries, together with the phrase-level constituents peculiar to each.
 
<list type="bullets"><item>the <gi tei="yes">form</gi> element, which groups orthographic information
and pronunciations, is described in section <xref target="DITPFO"/>
 </item><item>the <gi tei="yes">gramGrp</gi> element, which groups elements for the
grammatical characterization of the headword, is described in section<xref target="DITPGR"/>
 </item><item>the <gi tei="yes">def</gi> and <gi tei="yes">trans</gi> elements, which describe the
meaning of the headword, are described in section <xref target="DITPSE"/>
 </item><item>the <gi tei="yes">etym</gi> element and its special phrase-level elements
are documented in section <xref target="DITPET"/>
 </item><item>the <gi tei="yes">eg</gi>, <gi tei="yes">usg</gi>, <gi tei="yes">lbl</gi>, <gi tei="yes">xr</gi>, and
<gi tei="yes">note</gi> elements are described in section <xref target="DITPMI"/>
 </item><item>the <gi tei="yes">re</gi> element, which marks nested entries for related
words, is described in section <xref target="DITPFO"/>
 </item></list>
 </p><div3 id="DITPFO" name="subsection" ref="Y"><head>Information on Written and Spoken Forms</head><p>Dictionary entries most often begin with information about the form
of the word to which the entry applies.  Typically, the orthographic
form of the word, sometimes marked for syllabification, is the first
item in an entry.  Other information about the word, including variant
or alternate forms, inflected forms, pronunciation, etc., is also often
given.
 </p><p>The following elements should be used to encode this information:
the <gi tei="yes">form</gi> element groups one or more occurrences of any of the
others; it can also be recursively nested to reflect more complex
sub-grouping of information about word form(s), as shown in the
examples.
 
<tagList style="one-line"><tagDesc tagDoc="FORM" atts="type"/><tagDesc tagDoc="ORTH" atts="type extent"/><tagDesc tagDoc="PRON" atts="extent"/><tagDesc tagDoc="HYPH"/><tagDesc tagDoc="SYLL"/><tagDesc tagDoc="STRESS"/><tagDesc tagDoc="LBL"/></tagList>
 </p><p>In addition to those listed above, the following elements, which
encode morphological details of the form, may also occur within
<gi tei="yes">form</gi> elements:
 
<tagList style="one-line"><tagDesc tagDoc="GRAM" atts="type"/><tagDesc tagDoc="GEN"/><tagDesc tagDoc="NUMBER"/><tagDesc tagDoc="CASE"/><tagDesc tagDoc="PER"/><tagDesc tagDoc="TNS"/><tagDesc tagDoc="MOOD"/><tagDesc tagDoc="ITYPE" atts="type"/></tagList>
 
Of these, the <gi tei="yes">gram</gi> element is most general, and all of the
others are synonymous with <gi tei="yes">gram</gi> elements with appropriate
values (<code tei="yes" type="frag">gen, number, case</code>, etc.) for the
<att tei="yes">type</att> attribute.
 </p><p>Different dictionaries use different means to mark hyphenation,
syllabification, and stress, and they often use special symbols (e.g.,
the <soCalled>middle dot</soCalled> for hyphenation).  Many of these
symbols are defined as entities within standard ISO entity sets (see
chapter <xref target="XW"/>; others may require the definition of new
entities.  For pronunciation transcriptions, the user is referred to the
discussion of TEI definitions for the symbols of the International
Phonetic Alphabet, in chapter <xref target="XW"/>.  When alternative or
additional symbols are used in the encoding, the conventions used should
be fully documented in the header.  (This may occur, for instance, in
cases where pronunciations are not given at all in the original, but are
added in the encoded text, when a simplified pronunciation transcription
is used, when pronunciations in several dictionaries are normalized to a
single scheme, or when pronunciation symbols are transliterated into a
standard character set like ISO 646, as in the scheme used by the OALD
and by some examples here.)
 </p><p>Among the ISO entity sets most likely to be useful in the
transcription of form information are:
<list type="bullets"><item>ISOlat1 (Latin characters and diacritics for Western European
languages)</item><item>ISOlat2 (Eastern European languages)</item><item>ISOpub (miscellaneous publishing and special symbols)</item><item>ISOnum (numeric and related symbols)</item></list><!-- list useful ISO entity sets here:  ISOpub, ISOnum,       --><!-- ISOlat1, ISOlat2                                         -->
 </p><p>In the simplest case, nothing is given but the orthography:
 
<eg><![CDATA[<form>
  <orth>doom-laden</orth>
</form>
<!-- [CED] -->]]></eg>
 </p><p>Often, however, pronunciation is given.
 
<q rend="display"><hilited rend="bold">soucoupe</hilited> [sukup] ...     [DNT]</q>
 
<eg><![CDATA[<form>
  <orth>soucoupe</orth>
  <pron>sukup</pron>
</form>]]></eg>
 </p><p>For a variety of reasons including ease of processing, it may be
desired to split into separate elements information which is collapsed
into a single element in the source text; orthography and
hyphenation may for example be transcribed as separate elements,
although given together in the source text.  For
a discussion of the issues involved, and of methods for retaining both
the presentation form and the interpreted form, see section <xref target="DIMV"/>.
 <!-- supererogatory (msm)
<q rend=display>
gov.ern.ment <code>/"gVv@nm@nt/ </code> ...  [OALD]
</q>
 
<eg>
<![ CDATA [
<form>
   <orth>government</orth>
   <hyph>gov|ern|ment</hyph>
   <pron>"gVv@nm@nt</pron>
</form>
]]>
</eg>
-->
 </p><p>This example splits orthography and hyphenation, and adds
syllabification because it differs from hyphenation:
 
<q rend="display"><hilited rend="bold">ar.ea</hilited>  ...  [W7]</q>
 
<eg><![CDATA[<form>
   <orth>area</orth>
   <hyph>ar|ea</hyph>
   <syll>ar|e|a</syll>
</form>]]></eg>
 <!--
<q rend=display>
<hilited rend=bold>alternating current</hilited>  <code>/,....'../
</code>  ... [LDOCE]
</q>
 
<eg>
<![ CDATA [
<form>
   <orth>alternating current</orth>
   <stress>,....'..</stress>
</form>
]]>
</eg>
-->
 </p><p>Multiple orthographic forms may be given, e.g. to illustrate a word's
inflectional pattern:
 
<q rend="display"><hilited rend="bold">brag</hilited> ... vb. brags, bragging, bragged ...   [CED]</q>
 
<eg><![CDATA[<form>
  <orth>brag</orth>
  <pron>br&amp;g</pron>
</form>
<gramGrp>
  <pos>vb</pos>
</gramGrp>
<form type=infl>
  <orth>brags</orth>
  <orth>bragging</orth>
  <orth>bragged</orth>
</form>
<!-- ... -->]]></eg>
 
Or the inflectional pattern may be indicated by reference to a table of
paradigms, as here:
 
<q rend="display"> <hilited rend="bold">horrifier</hilited> 
<code tei="yes" type="frag">[ORifje]</code> (7) vt ...  [C/R] </q>
 
<eg><![CDATA[<form>
  <orth>horrifier</orth>
  <pron>ORifje</pron>
  <itype type=vbtable>7</itype>
</form>]]></eg>
 </p><p>As noted, <gi tei="yes">itype</gi> etc. are synonymous with appropriately typed
instances of the general <gi tei="yes">gram</gi> element; the last example might
equally be tagged thus:
<eg><![CDATA[<form>
  <orth>horrifier</orth>
  <pron>ORifje</pron>
  <gram type='itype / vbtable'>7</gram>
</form>]]></eg>
 </p><p>Explanatory labels may be attached to alternate forms:
 
<q rend="display"> <hilited rend="bold">MTBF</hilited> <hilited rend="ital">abbrev. for</hilited> mean time between failures.  [CED]</q>
 
<eg><![CDATA[<entry>
  <form type=abbrev>
    <orth>MTBF</orth>
  </form>
  <form type=full>
    <lbl>abbrev. for</lbl>
    <orth>mean time between failures</orth>
  </form>
</entry>]]></eg>
 </p><p>When multiple orthographic forms are given, a pronunciation may be
associated with all of them, as here:
 
<q rend="display"><hilited rend="bold">biryani</hilited> or <hilited rend="bold">biriani</hilited>
<code tei="yes" type="frag">(%bIrI"A:nI) </code>... [CED]</q>
 
<eg><![CDATA[<!-- The pronunciation is associated with both forms. -->
<form>
  <orth>biryani</orth>
  <orth>biriani</orth>
  <pron>%bIrI"A:nI</pron>
</form>]]></eg>
 </p><p>In other cases, different pronunciations are provided for different
orthographic forms; here, the <gi tei="yes">form</gi> element is repeated to
associate the first orthographic form explicitly with the first
pronunciation, and the second orthographic form with the second
pronunciation:
 
 
<q rend="display"> <hilited rend="bold">mackle</hilited>
<code tei="yes" type="frag">("m&amp;amp;k^@l) </code> or macule <code tei="yes" type="frag">("m&amp;amp;kju:l) </code>
... [CED] </q>
 
<eg><![CDATA[<!-- &supschwa is a small superscript schwa -->
<form>
  <orth>mackle</orth>
  <pron>"m&amp;k&supschwa;l</pron>
</form>
<form>
  <orth>macule</orth>
  <pron>"m&amp;kju:l</pron>
</form>]]></eg>
 </p><p>Recursive nesting of the <gi tei="yes">form</gi> element can preserve
relations among elements that are implicit in the text.  For example,
in the CED entry for <q>hospitaller</q>, it is clear that <q>U.S.</q>
is associated only with <q>hospitaler</q>, but that the pronunciation
applies to both forms.  The following encoding preserves these
relations:
 
<q rend="display"> <hilited rend="bold">hospitaller</hilited> or
U.S. hospitaler <code tei="yes" type="frag">("hQspIt@l@) </code> ... [CED] </q>
 
<eg><![CDATA[<form>
  <orth>hospitaller</orth>
  <form>
    <usg type=geo>U.S.</usg>
    <orth>hospitaler</orth>
  </form>
  <pron>"hQspIt@l@</pron>
</form>]]></eg>
 <!-- suppressed; supererogatory (msm) -->
 <!-- <p>In this example, the "pl." specification applies to   --><!-- two orthographic forms, but a pronunciation is           --><!-- associated with only one of them:                        -->
 <!-- <q rend=display>                                         --><!-- pinna ("pIn@) n., pl. -nae (-ni:) or -nas.   ... [CED]   --><!-- </q>                                                     -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <form>                                                   --><!--   <orth>pinna</orth>                                     --><!--   <pron>"pIn@</pron>                                     --><!-- </form>                                                  --><!-- <gramGrp>                                                --><!--   <pos>n</pos>                                           --><!-- </gramGrp>                                               --><!-- <form type=infl>                                         --><!--   <num>pl</num>                                          --><!--   <form>                                                 --><!--     <orth type=lat extent=part>-nae</orth>               --><!--     <pron extent=part>-ni:</pron>                        --><!--   </form>                                                --><!--   <orth type=std extent=part>-nas</orth>                 --><!-- </form>                                                  --><!-- ]]>                                                      --><!-- </eg>                                                    --><!-- ... end suppression (msm)                                -->
 </p><p>The formal declarations for the elements of the <gi tei="yes">form</gi>
group are these:
 
<dtdFrag id="DDITPFO" n="The form group"><tagDecl tagDoc="FORM"/><tagDecl tagDoc="ORTH"/><tagDecl tagDoc="PRON"/><tagDecl tagDoc="HYPH"/><tagDecl tagDoc="SYLL"/><tagDecl tagDoc="STRESS"/><commDecl>(LBL is declared with USG, elsewhere.)</commDecl><commDecl>Elements for morphological information:</commDecl><tagDecl tagDoc="GRAM"/><tagDecl tagDoc="GEN"/><tagDecl tagDoc="NUMBER"/><tagDecl tagDoc="CASE"/><tagDecl tagDoc="PER"/><tagDecl tagDoc="TNS"/><tagDecl tagDoc="MOOD"/><tagDecl tagDoc="ITYPE"/></dtdFrag>
 </p><p>The classes of morphological elements, and of elements allowed within
the <gi tei="yes">form</gi> group, are declared thus:
 
<dtdFrag id="DEDITPFO" n="Classes for morphological and form information"><claDecl classDoc="MORPH" type="model"/><claDecl classDoc="FORMINFO" type="model"/></dtdFrag>
 </p></div3><div3 id="DITPGR" name="subsection" ref="Y"><head>Grammatical Information</head><p>The <gi tei="yes">gramGrp</gi> element groups grammatical information, such as
part of speech, subcategorization information (e.g., syntactic patterns
for verbs, count/mass distinctions for nouns), etc.  It can contain any
of the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="POS"/><tagDesc tagDoc="SUBC"/><tagDesc tagDoc="COLLOC"/></tagList>
 </p><p>In addition, <gi tei="yes">gramGrp</gi> can contain any of the morphological
elements defined in section <xref target="DITPFO"/> for <gi tei="yes">form</gi>:
 
<tagList style="one-line"><tagDesc tagDoc="GRAM"/><tagDesc tagDoc="ITYPE"/><tagDesc tagDoc="GEN"/><tagDesc tagDoc="NUMBER"/><tagDesc tagDoc="CASE"/><tagDesc tagDoc="PER"/><tagDesc tagDoc="TNS"/><tagDesc tagDoc="MOOD"/></tagList>
 
Elements conveying morphological information bear different
interpretations within <gi tei="yes">gramGrp</gi> and <gi tei="yes">form</gi> groups, the
difference being that in the <gi tei="yes">form</gi> group, the morphological
information specified pertains to the specific alternate form in
question, while within <gi tei="yes">gramGrp</gi> it applies to the headword form.
For example, in the entry <q><hilited rend="bold">pinna</hilited> ('pIn@) n., pl. -nae (-ni:) or
-nas</q> [CED], the word defined can be either singular or plural; the
<q>pl.</q> specification applies only to the inflected forms provided.
Compare this with <q>pants (paents) pl. n.</q>, where <q>pl.</q> applies
to the headword itself.
 <!-- suppress as more than enough (msm)                       --><!--                                                          --><!-- <p>Examples:                                             --><!--                                                          --><!-- <q rend=display>                                         --><!-- amass /@"m&amp;s/ vt [VP6A] pile or heap up, collect.   [OALD] --><!-- </q>                                                     --><!--                                                          --><!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--    <form>                                                --><!--       <orth>amass</orth>                                 --><!--       <pron>@"m&amp;s</pron>                                 --><!--    </form>                                               --><!--    <gramGrp>                                             --><!--       <pos>vt</pos>                                      --><!--       <subc>VT6A</subc>                                  --><!--    </gramGrp>                                            --><!--    <def>pile or heap up, collect.</def>                  --><!-- </entry>                                                 --><!-- ]]>                                                      --><!-- </eg>                                                    --><!--                                                          --><!-- ... end suppression (msm)                                -->
 </p><p>As noted above in section <xref target="DITPFO"/>, the elements for
morphological information are simply shorthand for the general purpose
<gi tei="yes">gram</gi> element.  Consider this entry for the French word
<cited>m&eacute;dire</cited>:<!-- no such word, unless you add the accent! (LB -->
<q rend="display"><hilited rend="bold">m&eacute;dire</hilited> v.t. ind. (de) ...   [PLC]</q>
 
This entry can be tagged using specialized grammatical elements:
 
<eg><![CDATA[<form><orth>m&eacute;dire</orth></form>
<gramGrp>
   <pos>v</pos>
   <subc>t ind</subc>
   <colloc type=prep>de</colloc>
</gramGrp>]]></eg>
 
Or using the <gi tei="yes">gram</gi> element:
<eg><![CDATA[<form><orth>m&eacute;dire</orth></form>
<gramGrp>
   <gram type=pos>v</>
   <gram type=subc>t ind</>
   <gram type='colloc / prep'>de</>
</gramGrp>]]></eg>
 </p><p>Like <gi tei="yes">form</gi>, <gi tei="yes">gramGrp</gi> can be repeated, recursively
nested, or used at the <gi tei="yes">sense</gi> level to show relations among
elements.
 
<q rend="display"><hilited rend="bold">isotope</hilited> adj. et n. m.  ... [DNT]</q>
 
<eg><![CDATA[<form><orth>isotope</orth></form>
<gramGrp>
   <pos>adj</pos>
</gramGrp>
<gramGrp>
   <pos>n</pos>
   <gen>m</gen>
</gramGrp>]]></eg>
 <!-- <q rend=display>                                         --><!-- ablaze (@"bleIz) adj.  (postpositive), adv. 1. on fire;  --><!-- burning. 2. brightly illuminated. 3. emotionnally        --><!-- aroused.  [CED]                                          --><!-- </q>                                                     -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--   <form>                                                 --><!--     <orth>ablaze</orth>                                  --><!--     <pron>@"bleIz</pron>                                 --><!--   </form>                                                --><!--   <gramGrp>                                              --><!--     <pos>adj</pos>                                       --><!--     <subc>postpositive</subc>                            --><!--   </gramGrp>                                             --><!--   <gramGrp>                                              --><!--     <pos>adv</pos>                                       --><!--   </gramGrp>                                             --><!--   <sense n='1'>                                          --><!--     <def>on fire; burning.</def>                         --><!--   </sense>                                               --><!--   <sense n='2'>                                          --><!--     <def>brightly illuminated.</def>                     --><!--   </sense>                                               --><!--   <sense n='3'>                                          --><!--     <def>emotionnally aroused.</def>                     --><!--   </sense>                                               --><!-- </entry>                                                 --><!--                                                          --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 
<q rend="display"> <hilited rend="bold">wits</hilited> (wIts)
pl. n. 1. (sometimes sing.) the ability to reason and act,
esp. quickly...  [CED] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>wits</orth>
    <pron>wIts</pron>
  </form>
  <gramGrp>
    <number>pl</number>
    <pos>n</pos>
  </gramGrp>
  <sense n='1'>
    <gramGrp>
      <number>sometimes sing</number>
    </gramGrp>
    <def>the ability to reason and act, esp. quickly...</def>
    <!-- ... -->
  </sense>
</entry>]]></eg>
 <!-- <q rend=display>                                         --><!-- carry ("k&amp;rI) vb.  ...(mainly tr.) 1. (also intr.)   --><!-- to take or bear...  [CED]                                --><!-- </q>                                                     -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--   <form>                                                 --><!--     <orth>carry</orth>                                   --><!--     <pron>"k&amp;rI</pron>                                   --><!--   </form>                                                --><!--   <gramGrp>                                              --><!--     <pos>vb</pos>                                        --><!--     <subc>mainly tr</subc>                               --><!--   </gramGrp>                                             --><!--   <sense n='1'>                                          --><!--     <gramGrp>                                            --><!--       <subc>also intr</subc>                             --><!--     </gramGrp>                                           --><!--     <def>to take or bear...</def>                        --><!-- ...                                                      --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 
 </p><p>The following gives the formal declarations for elements in the
grammatical-information group.
 
<dtdFrag id="DDITPGR" n="The gram group"><tagDecl tagDoc="GRAMGRP"/><tagDecl tagDoc="POS"/><tagDecl tagDoc="SUBC"/><tagDecl tagDoc="COLLOC"/></dtdFrag>
 </p><p>The class of elements allowed within
the <gi tei="yes">gramGrp</gi> element is declared thus.
The class <term>morphInfo</term> is
defined above in section <xref target="DITPFO"/>.
 
<dtdFrag id="DEDITPGR" n="Elements for grammatical information"><claDecl classDoc="GRAMINFO" type="model"/></dtdFrag>
 </p></div3><div3 id="DITPSE" name="subsection" ref="Y"><head>Sense Information</head><p>Dictionaries may describe the meanings of words in a wide variety of
different ways --- by means of synonyms, paraphrases, translations into
other languages, formal definitions in various highly stylized forms,
etc.  No attempt is made here to distinguish all the different forms
which sense information may take; all alike may be tagged using the
<gi tei="yes">def</gi> element described in section <xref target="DITPDE"/>.
 </p><p>Because as a special case it is frequently desired to distinguish the
provision of translation equivalents in other languages from other forms
of sense information, however, the specialized elements <gi tei="yes">tr</gi>
(translation equivalent) and <gi tei="yes">trans</gi> (which groups a translation
equivalent with related information such as its grammatical description)
are defined for this purpose in section <xref target="DITPTR"/>.
 </p><p>Whether sense information in multilingual dictionaries is
consistently tagged using <gi tei="yes">tr</gi> or <gi tei="yes">def</gi> is a matter of the
encoder's choice; no blanket recommendation is made here.
 </p><div4 id="DITPDE" name="Section" ref="Y"><head>Definitions</head><p>Dictionary definitions are those pieces of prose in a dictionary
entry that describe the meaning of some lexical item.  Most often,
definitions describe the headword of the entry; in some cases, they
describe translated texts, examples, etc.; see <gi tei="yes">tr</gi>, section<xref target="DITPTR"/>
, and <gi tei="yes">eg</gi>, section <xref target="DITPEG"/>.
The <gi tei="yes">def</gi> element directly contains the text of the definition;
unlike <gi tei="yes">form</gi> and <gi tei="yes">gramGrp</gi>, that is, it does not serve
solely to group a set of smaller elements.  The close analysis of
definition text, such as the tagging of hypernyms, typical objects,
etc., is not covered by these Guidelines.
 </p><p>Definitions may occur directly within an entry; when multiple
definitions are given, they typically are identified as
belonging to distinct senses, as here:
 
<q rend="display"> <hilited rend="bold">demigod</hilited> (...) n. 1.a. a
being who is part mortal, part god. b.  a lesser deity. 2. a godlike
person.  [CP] </q>
 
<eg><![CDATA[<entry>
<form>
   <orth>demigod</orth>
   <pron> ...</pron></form>
<gramGrp><pos>n</pos></gramGrp>
<sense n='1'>
   <sense n='a'>
      <def>a being who is part mortal, part god.</def>
   </sense>
   <sense n='b'>
      <def>a lesser deity.</def>
   </sense>
</sense>
<sense n='2'>
   <def>a godlike person.</def>
</sense>
</entry>]]></eg>
 </p><p>In multilingual dictionaries, it is sometimes possible to
distinguish translation equivalents from definitions proper; here a
<gi tei="yes">def</gi> element is distinguished from the translation information
within which it appears.
 
<q rend="display"> <hilited rend="bold">r&eacute;moulade</hilited>
<code tei="yes" type="frag">[Remulad] </code> nf remoulade, r&eacute;moulade (<hilited rend="ital">dressing containing mustard and herbs</hilited>).  [C/R]</q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>r&eacute;moulade</orth>
    <pron>Remulad</pron>
  </form>
  <gramGrp>
    <pos>n</pos>
    <gen>f</gen>
  </gramGrp>
  <trans>
    <tr>remoulade</tr>
    <tr>r&eacute;moulade</tr>
    <def>dressing containing mustard and herbs</def>
  </trans>
</entry>]]></eg>
 </p><p>The following gives the formal definition of <gi tei="yes">def</gi>:
 
<dtdFrag id="DDITPDE" n="Definition text"><tagDecl tagDoc="DEF"/></dtdFrag>
 </p></div4><div4 id="DITPTR" name="Section" ref="Y"><head>Translation Equivalents</head><p>Multi-lingual dictionaries contain information about translations of
a given word in some source language for one or more target languages.
Minimally, the dictionary provides the corresponding translation in the
target language; other information, such as morphological information
(gender, case), various kinds of usage restrictions, etc., may also be
given.  If translation equivalents are to be distinguished from other
kinds of sense information, they may be encoded using the <gi tei="yes">tr</gi>
element.
 </p><p>As in monolingual dictionaries, the <gi tei="yes">sense</gi> element is used in
multi-lingual dictionaries to group information (forms, grammatical
information, usage, translation(s), etc.) about a given sense of a word
where necessary, as in monolingual dictionaries.  Information about the
individual translation equivalents within a sense is grouped using
<gi tei="yes">trans</gi> element.  This information may include the translation
text (tagged <gi tei="yes">tr</gi> or <gi tei="yes">def</gi>), morphological information
(<gi tei="yes">gen</gi>, <gi tei="yes">case</gi>, etc.), usage notes (<gi tei="yes">usg</gi>),
translation labels (<gi tei="yes">lbl</gi>), and definitions (<gi tei="yes">def</gi>).
 <!-- [do we need other things in the trans group?  NEEDS      --><!-- WORK.  -JV, NI] <                                        -->
 
<tagList style="one-line"><tagDesc tagDoc="TRANS"/><tagDesc tagDoc="TR"/><tagDesc tagDoc="LBL"/></tagList>
 </p><p>Note how in the following example, different translation equivalents
are grouped into the same or different senses, following the punctuation
of the source and the usage labels:
 
<q rend="display"> <hilited rend="bold">dresser</hilited> ... (a) (Theat)
habilleur m, -euse f; (Comm: window ~) &eacute;talagiste
mf. she's a stylish ~ elle s'habille avec chic; V hair.  (b)
(tool) (for wood) raboteuse f; (for stone) rabotin m. [C/R] </q>
 <!-- < note place=inline > [homograph numbers superscripted   --><!-- in original text; pronunciations have to be fixed -JV,   --><!-- NI] < /note >                                            -->
 
<eg><![CDATA[<entry n='1'>
  <form><orth>dresser</orth><!-- ... --></form>
  <gramGrp> <pos>n</pos> </gramGrp>
  <sense n='a'>
    <sense>
      <usg type=dom>Theat</usg>
      <trans>
        <tr>habilleur</tr>
        <gen>m</gen>
      </trans>
      <trans>
        <tr>-euse</tr>
        <gen>f</gen>
      </trans>
    </sense>
    <sense>
      <usg type=dom>Comm</usg>
      <form type=compound>
        <orth>window <oRef></orth>
      </form>
      <trans>
        <tr>etalagiste</tr>
        <gen>mf</gen>
      </trans>
     </sense>
     <eg>
       <q>she's a stylish <oRef></q>
       <trans><tr>elle s'habille avec chic</tr></trans>
     </eg>
     <xr type=see>V. <ref target=HAIR>hair</ref></xr>
  </sense>
  <sense n='b'>
    <usg type=category>tool</usg>
    <sense>
      <usg type=hint>for wood</usg>
      <trans>
        <tr>raboteuse</tr>
        <gen>f</gen>
      </trans>
    </sense>
    <sense>
      <usg type=hint>for stone</usg>
      <trans>
        <tr>rabotin</tr>
        <gen>m</gen>
     </trans>
    </sense>
  </sense>
</entry>]]></eg>
 </p><p>In this encoding, a distinction is made between the translation
equivalent (<q>OAS</q>) and a descriptive phrase providing
further information for the user of the dictionary.
 
<q rend="display"> <hilited rend="bold">O.A.S.</hilited> ... nf
(abr&eacute;v de <hilited rend="bold">Organisation de l'Arm&eacute;e
secr&egrave;te</hilited>) OAS (<hilited rend="ital">illegal military
organization supporting French rule of Algeria</hilited>).  [C/R] </q>
 
<eg><![CDATA[<entry>
  <!-- ... -->
  <trans>
    <tr>OAS</tr>
    <def>illegal military organization supporting French
         rule of Algeria</def>
  </trans>
</entry>]]></eg>
 
 <!-- <q rend=display>                                         -->
 <!-- canary [k@"nE@rI] 1 n (a) (bird) canari m, serin m.      --><!--   (b) (wine) vin m des Canaries.                         --><!-- 2 cpd (also canary yellow) (de couleur) jaune serin      --><!-- inv, jaune canari inv.  (Bot) canary grass alpiste m;    --><!-- (Geog) Canary Isles, Canaries (&icirc;les fpl) Canaries  --><!-- fpl; (Bot) canary seed millet m. [C/R]                   -->
 <!-- </q>                                                     -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--   <form>                                                 --><!--     <orth>canary</orth>                                  --><!--     <pron>k@"nE@rI</pron>                                --><!--   </form>                                                --><!--   <sense n='1'>                                          --><!--     <gramGrp>                                            --><!--        <pos>n</pos>                                      --><!--     </gramGrp>                                           --><!--     <sense n='a'>                                        --><!--       <usg type=hyper>bird</usg>                         --><!--       <trans>                                            --><!--         <tr>canari</tr>                                  --><!--         <gen>m</gen>                                     --><!--       </trans>                                           --><!--       <trans>                                            --><!--         <tr>serin</tr>                                   --><!--         <gen>m</gen>                                     --><!--       </trans>                                           --><!--     </sense>                                             --><!--     <sense n='b'>                                        --><!--       <usg type=hyper>wine</usg>                         -->
      <!--note use of NEXT and PREV TEI attributes-->
      <!--for discontinous elements               --><!--       <trans id=T1 next=t2>                              --><!--         <tr>vin</tr>                                     --><!--         <gen>m</gen>                                     --><!--       </trans>                                           --><!--       <trans id=T2 prev=t1>                              --><!--         <tr>des canaries</tr>                            --><!--       </trans>                                           --><!--      </sense>                                            --><!--    </sense>                                              --><!--    <sense n='2'>                                         --><!--      <gramGrp>                                           --><!--        <pos>cpd</pos>                                    --><!--      </gramGrp>                                          --><!--      <re type=cmpd>                                      --><!--        <form>                                            --><!--           <orth>canary yellow</orth>                     --><!--        </form>                                           --><!--        <usg type=hint>de couleur</usg>                   --><!--        <trans>                                           --><!--          <tr>jaune serin</tr>                            --><!--          <itype>inv</itype>                              --><!--        </trans>                                          --><!--        <trans>                                           --><!--          <tr>jaune canari</tr>                           --><!--          <itype>inv</itype>                              --><!--        </trans>                                          --><!--      </re>                                               --><!--      <re type=cmpd>                                      --><!--        <usg type=dom>Bot</usg>                           --><!--        <form>                                            --><!--          <orth>canary grass</orth>                       --><!--        </form>                                           --><!--        <trans>                                           --><!--          <tr>alpiste</tr>                                --><!--          <gen>m</gen>                                    --><!--        </trans>                                          --><!--      </re>                                               --><!--      <re type=cmpd>                                      --><!--        <usg type=dom>Geog</usg>                          --><!--        <form>                                            --><!--          <orth>Canary Isles</orth>                       --><!--          <orth>Canaries</orth>                           --><!--        </form>                                           --><!--        <trans id=T1 opt=y next=t2>                       --><!--          <tr>&icirc;les</tr>                             --><!--          <gen>f</gen>                                    --><!--          <num>pl</num>                                   --><!--        </trans>                                          --><!--        <trans id=T2 prev=t1>                             --><!--          <tr>Canaries</tr>                               --><!--          <gen>f</gen>                                    --><!--          <num>pl</num>                                   --><!--        </trans>                                          --><!--      </re>                                               --><!--      <re type=cmpd>                                      --><!--        <usg type=dom>Bot</usg>                           --><!--        <form>                                            --><!--          <orth>canary seed</orth>                        --><!--        </form>                                           --><!--        <trans>                                           --><!--          <tr>millet</tr>                                 --><!--          <gen>m</gen>                                    --><!--        </trans>                                          --><!--      </re>                                               --><!--    </sense>                                              --><!--  </entry>                                                --><!--                                                          --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p><p>Note that <gi tei="yes">tr</gi> may also be used in monolingual dictionaries
when a translation is given for a foreign word:
 <!-- < note place=inline > [headwords are in bold italics     --><!-- intead of just bold; pronunciations to be completed      --><!-- -JV, NI] < /note >                                       -->
 
<q rend="display"> <hilited rend="bold">havdalah</hilited> or <hilited rend="bold">havdoloh</hilited> Hebrew. (Hebrew <code tei="yes" type="frag">hAvdA"lA; </code>
Yiddish <code tei="yes" type="frag">hAv"dOl@) </code> n.  Judaism. the ceremony marking the
end of the sabbath or of a festival, including the blessings over
wine, candles and spices. [literally: separation] [CED] </q>
 
<eg><![CDATA[<entry type=foreign>
  <form>
    <orth>havdalah</orth>
    <orth>havdoloh</orth>
  </form>
  <!-- ... -->
  <usg type=dom>Judaism</usg>
  <def>the ceremony marking the end of the sabbath or of a festival,
       including the blessings over wine, candles and spices.</def>
  <trans>
    <lbl>literally</lbl>
    <tr>separation</tr>
  </trans>
</entry>]]></eg>
 </p><p>The formal definition of these elements is as follows:
 
<dtdFrag id="DDITPTR" n="Translation information"><tagDecl tagDoc="TRANS"/><tagDecl tagDoc="TR"/></dtdFrag>
 </p></div4></div3><div3 id="DITPET" name="subsection" ref="Y"><head>Etymological Information</head><p>The element <gi tei="yes">etym</gi> marks a block of etymological information.
Etymologies may contain highly structured lists of words in an order
indicating their descent from each other, but often also include
related words and forms outside the direct line of descent,
for comparison.  Not infrequently, etymologies include commentary of
various sorts, and can grow into short (or long!) essays with prose-like
structure.  This variation in structure makes it impracticable to define
tags which capture the entire intellectual structure of the etymology or
record the precise interrelation of all the words mentioned.  It is,
however, feasible to mark some of the more obvious phrase-level elements
frequently found in etymologies, using tags defined in the core tag set
or elsewhere in this chapter.  Of particular relevance for the markup of
etymologies are:
 
<tagList style="one-line"><tagDesc tagDoc="ETYM"/><tagDesc tagDoc="LANG"/><tagDesc tagDoc="DATE"/><tagDesc tagDoc="MENTIOND"/><tagDesc tagDoc="GLOSS"/><tagDesc tagDoc="PRON"/><tagDesc tagDoc="USG"/><tagDesc tagDoc="LBL"/></tagList>
 </p><p>As in other prose, individual word forms mentioned in an etymological
description are tagged with <gi tei="yes">mentioned</gi> elements.
Pronunciations, usage labels, and glosses can be tagged using the
<gi tei="yes">pron</gi>, <gi tei="yes">usg</gi>, and <gi tei="yes">gloss</gi> elements defined
elsewhere in these Guidelines.  In addition, the <gi tei="yes">lang</gi> element
may be used to identify a particular language name where it appears, in
addition to using the <att tei="yes">lang</att> attribute of the
<gi tei="yes">mentioned</gi> element.
 </p><p>Examples:
 
<q rend="display"> <hilited rend="bold">abismo</hilited> m. (del gr. a
priv. y byssos, fondo). Sima, gran profundidad. ...  </q>
 
 
<eg><![CDATA[<entry>
  <form><orth>abismo</orth></form>
  <!-- ... -->
  <etym>del <lang>gr.</> <mentioned>a</> priv. y
       <mentioned>byssos</>, <gloss>fondo</>
  </etym>
  <!-- ... -->
</entry>]]></eg>
 
<q rend="display"> <hilited rend="bold">neume</hilited>
<code tei="yes" type="frag">\'n(y)&uuml;m\</code> n [F, fr.  ML pneuma, neuma, fr.  Gk
pneuma breath --- more at <hilited rend="bold">pneumatic</hilited>]: any
of various symbols used in the notation of Gregorian chant ...  [WNC]</q>
 
 
<eg><![CDATA[<entry>
  <!-- ... -->
  <etym><lang>F</> fr. <lang>ML</> <mentioned>pneuma</>
        <mentioned>neuma</> fr. <lang>Gk</>
        <mentioned>pneuma</><gloss>breath</>
        <xr type=etym>more at <ptr target='PNEUMATIC'></xr>
  </etym>
  <def>any of various symbols ...
  <!-- ... -->
</entry>]]></eg>
 
 </p><p>The formal definition for the elements described in this section and
not declared elsewhere is:
 
<dtdFrag id="DDITPET" n="Etymologies"><tagDecl tagDoc="ETYM"/><tagDecl tagDoc="LANG"/></dtdFrag>
 </p></div3><div3 id="DITPMI" name="subsection" ref="Y"><head>Other Information</head><div4 id="DITPEG" name="Section" ref="Y"><head>Examples</head><p>Dictionaries typically include examples of word use, usually
accompanying definitions or translations.  In some cases, the examples
are quotations from another source, and are occasionally followed by a
citation to the author.
 </p><p>The <gi tei="yes">eg</gi> element contains usage examples and associated
information; the example text itself should be enclosed in a
<gi tei="yes">cit</gi> element, if attributed, or a <gi tei="yes">q</gi> or <gi tei="yes">quote</gi>
element otherwise.  The <gi tei="yes">cit</gi> element associates a quotation with
a bibliographic reference to its source.
 
<tagList style="one-line"><tagDesc tagDoc="DIEG"/><tagDesc tagDoc="Q"/><tagDesc tagDoc="QUOTE"/><tagDesc tagDoc="CIT"/></tagList>
 </p><p>Examples frequently abbreviate the headword, and so their
transcription will frequently make use of the <gi tei="yes">oRef</gi> or
<gi tei="yes">oVar</gi> elements described below in section <xref target="DIHW"/>.
 <!-- [NEEDS WORK: what can go in EG?  anything?  -JV, NI]     -->
 </p><p>Examples:
 
<q rend="display"> <hilited rend="bold">multiplex</hilited>
<code tei="yes" type="frag">/.../</code>
adj tech having many parts: the multiplex eye of the fly.
[LDOCE]</q>
 <!-- [Check pron -JV, NI]                                     -->
 
 
<eg><![CDATA[   <eg>
     <q>the multiplex eye of the fly.</q>
   </eg>]]></eg>
 
As the following example shows, <gi tei="yes">eg</gi> can also contain
elements such as <gi tei="yes">pron</gi>, <gi tei="yes">def</gi>, etc.
 
<q rend="display"> <hilited rend="bold">some</hilited> ... 4. (<hilited rend="ital">S~</hilited> and <hilited rend="ital">any</hilited> are
used with <hilited rend="ital">more</hilited>): Give me ~ more
<code tei="yes" type="frag">/s@'mO:(r)/</code> [OALD] </q>
 <!-- <pron> in an example -->
<eg><![CDATA[<sense n='4'>
  <usg type=colloc><oRef type=cap> and <mentioned>any</>
       are used with <mentioned>more</></usg>
  <eg>
    <q>Give me <oRef> more</q>
    <pron extent=part>s@'mO:(r)</pron>
  </eg>
</sense>]]></eg>
 
In multilingual dictionaries, examples may also be accompanied by
translations:
 
<q rend="display"> <hilited rend="bold">horrifier</hilited> ... vt to
horrify. <hilited rend="bold">elle &eacute;tait horrifi&eacute;e par la
d&eacute;pense</hilited> she was horrified at the expense.  [C/R] </q>
 <!-- <trans> in an example -->
<eg><![CDATA[<entry>
  <!-- ... -->
  <trans><tr>to horrify</tr></trans>
  <eg><q>elle &eacute;tait horrifi&eacute;e par la
         d&eacute;pense</q>
      <trans>
        <tr>she was horrified at the expense.</tr>
      </trans>
  </eg>
</entry>]]></eg>
 
 <!-- <q rend=display>                                         --><!-- 1. cent ...  III.  POUR CENT.  B&eacute;n&eacute;fice    --><!-- de trois pour cent (3 %):  B&eacute;n&eacute;fice de 3F  --><!-- sur 100F.  [DNT]                                         --><!-- </q>                                                     -->
 <!-- <def> in an example --><!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <eg>                                                     --><!--   <q>B&eacute;n&eacute;fice de trois pour cent (3 %)</q> --><!--   <def>B&eacute;n&eacute;fice de 3F sur 100F</def>       --><!-- </eg>                                                    --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 
 <!-- <q rend=display> break1 ... 5 ...  <hilited              --><!-- rend=ital>When the bank broke</hilited> (= was unable    --><!-- to carry on business because of lack of funds) <hilited  --><!-- rend=ital>, many people were ruined.</hilited> ...       --><!-- [OALD] </q>                                              -->
 <!-- example interrupted by a partial definition --><!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <eg>                                                     --><!--   <q next=e2 id=E1>When the bank broke</q>               --><!--   <def>was unable to carry on business because           --><!--        of lack of funds</def> --><!--   <q prev=e1 id=E2>, many people were ruined.</q>        --><!-- </eg>                                                    --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 
When a source is indicated, the example should be marked with a
<gi tei="yes">cit</gi> element:
 
<q rend="display"> <hilited rend="bold">valeur</hilited> ... n. f. ...
2. Vx.  Vaillance, bravoure (sp&eacute;cial., au combat).  <q>La
valeur n'attend pas le nombre des ann&eacute;es</q> (Corneille).  ...  [DNT]</q>
 
<eg><![CDATA[  <sense n='2'>
    <usg type=time>Vx.</usg>
    <def>Vaillance, bravoure (sp&eacute;cial., au combat)</def>
      <eg><cit>
            <q>La valeur n'attend pas le nombre des annees</q>
            <bibl><author>Corneille</author></bibl>
          </cit>
      </eg>
  </sense>]]></eg>
 </p><p>The formal definition of <gi tei="yes">eg</gi> is:
 
<dtdFrag id="DDITPEG" n="Examples and citations"><tagDecl tagDoc="DIEG"/></dtdFrag>
 </p></div4><div4 id="DITPUS" name="Section" ref="Y"><head>Usage Information and Other Labels</head><p>Most dictionaries provide restrictive labels and phrases indicating
the usage of given words or particular senses.  Other labels, not
necessarily related to usage, may be attached to forms, translations,
cross references, and examples.  Usage and other labels should be marked
with the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="USG"/><tagDesc tagDoc="LBL"/></tagList>
 
Typical usage labels mark
 
<list type="bullets"><item>temporal use (archaic, obsolete, etc.)</item><item>register (slang, formal, taboo, ironic, facetious, etc.)</item><item>style (literal, figurative, etc.)</item><item>connotative effect (e.g. derogatory, offensive)</item><item>subject field (Astronomy, Philosophy, etc.)</item><item>national or regional use (Australian, U.S., Midland dialect, etc.)</item></list>
 
Many dictionaries provide an explanation and/or a list of such usage
labels in a preface or appendix.  The type of the usage information may
be indicated in the <att tei="yes">type</att> attribute on the <gi tei="yes">usg</gi>
element.  Some typical values are:
 
<list type="gloss"><label><code tei="yes" type="frag">geo</code> </label><item>geographic area</item><label><code tei="yes" type="frag">time</code> </label><item>temporal, historical era
(<q>archaic</q>, <q>old</q>, etc.)</item><label><code tei="yes" type="frag">dom</code> </label><item>domain</item><label><code tei="yes" type="frag">reg</code> </label><item>register</item><label><code tei="yes" type="frag">style</code> </label><item>style (figurative, literal, etc.)</item><label><code tei="yes" type="frag">plev</code> </label><item>preference level (<q>chiefly</q>,
<q>usually</q>, etc.)</item><label><code tei="yes" type="frag">acc</code></label><item>acceptability</item><label><code tei="yes" type="frag">lang</code> </label><item>language for foreign words,
spellings pronunciations, etc.</item><label><code tei="yes" type="frag">gram</code> </label><item>grammatical usage</item></list>
 <!-- why is this list given twice? (LB) -->
 
In addition to this kind of information, multilingual dictionaries
often provide <soCalled>semantic cues</soCalled> to help the user
determine the right sense of a word in the source language (and hence
the correct translation).  These include synonyms, concept subdivisions,
typical subjects and objects, typical verb complements, etc.  These
labels are also marked with the <gi tei="yes">usg</gi> element; sample values for
the <att tei="yes">type</att> attribute in these cases include:
 
<list type="gloss"><label><code tei="yes" type="frag">syn</code> </label><item>synonym given to show use</item><label><code tei="yes" type="frag">hyper</code> </label><item>hypernym given to show usage</item><label><code tei="yes" type="frag">colloc</code> </label><item>collocation given to show usage</item><label><code tei="yes" type="frag">comp</code> </label><item>typical complement</item><label><code tei="yes" type="frag">obj</code> </label><item>typical object</item><label><code tei="yes" type="frag">subj</code> </label><item>typical subject</item><label><code tei="yes" type="frag">verb</code> </label><item>typical verb</item><label><code tei="yes" type="frag">hint</code> </label><item>unclassifiable piece of information to
guide sense choice</item></list>
 </p><p>In this entry, one spelling is marked as geographically restricted:
 
<q rend="display"> <hilited rend="bold">colour</hilited> or U.S. <hilited rend="bold">color</hilited> ...  [CED] </q>
 
<eg><![CDATA[<form>
   <orth>colour</orth>
</form>
<form>
   <usg type=geo>U.S.<usg>
   <orth>color</orth>
</form>]]></eg>
 </p><p>In this example, usage labels are used to indicate domains, register,
and synonyms associated with different senses:
 
<q rend="display"> <hilited rend="bold">palette</hilited>
<code tei="yes" type="frag">[palEt]</code> nf (a) (Peinture: lit, fig) palette. (b)
(Boucherie) shoulder. (c) (aube de roue) paddle; (battoir &agrave;
linge) beetle; (Manutention, Constr) pallet.  [C/R] </q>
 
<eg><![CDATA[<!-- ... -->
  <sense n='a'>
    <usg type=dom>Peinture</usg>
    <usg type=style>lit</usg>
    <usg type=style>fig</usg>
    <trans><tr>palette</tr></trans>
  </sense>
  <sense n='b'>
    <usg type=dom>Boucherie</usg>
    <trans><tr>shoulder</tr></trans>
  </sense>
  <sense n='c'>
    <sense>
      <usg type=syn>aube de roue</usg>
      <trans><tr>paddle</tr></trans>
    </sense>
    <sense>
      <usg type=syn>battoir &agrave; linge</usg>
      <trans><tr>beetle</tr></trans>
    </sense>
    <sense>
      <usg type=dom>Manutention</usg>
      <usg type=dom>Constr</usg>
      <trans><tr>beetle</tr></trans>
    </sense>
  </sense>
<!-- ... -->]]></eg>
 
 <!-- <q rend=display> parabola [p@"r&amp;@l@] n parabole f    --><!-- (Math) [C/R] </q>                                        -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--   <form>                                                 --><!--     <orth>parabola</orth>                                --><!--     <pron>p@"r&amp;@l@</pron>                                --><!--   </form>                                                --><!--   <gramGrp>                                              --><!--     <pos>n</pos>                                         --><!--   </gramGrp>                                             --><!--   <trans>                                                --><!--     <tr>parabole<tr>                                     --><!--     <gen>f</gen>                                         --><!--     <usg type=dom>Math</usg>                             --><!--   </trans>                                               --><!-- </entry>                                                 --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p><p>When the usage label is hard to classify, it may be described as a
<q>hint</q>:
 
<q rend="display"> <hilited rend="bold">rempaillage</hilited> [...] nm
reseating, rebottoming (<hilited rend="ital">with straw</hilited>).
[C/R] </q>
 <!-- [note: tilde on the a in ~a (IPA nasal a) -JV, NI]       -->
 
<eg><![CDATA[<entry>
  <!-- ... -->
  <trans>
    <tr>reseating</tr>
    <tr>rebottoming</tr>
    <usg type=hint>with straw</usg>
  </trans>
</entry>]]></eg>
 </p><p>The following gives the formal definition of <gi tei="yes">usg</gi> and
<gi tei="yes">lbl</gi>:
 
<dtdFrag id="DDITPUS" n="Usage information"><tagDecl tagDoc="USG"/><tagDecl tagDoc="LBL"/></dtdFrag>
 </p></div4><div4 id="DITPXR" name="Section" ref="Y"><head>Cross References to Other Entries</head><p>Dictionary entries frequently refer to information in other entries,
often using extremely dense notations to convey the headword of the
entry to be sought, the particular part of the entry being referred to,
and the nature of the information to be sought there (synonyms,
antonyms, usage notes, etymology, an illustration, etc.)
 </p><p>Cross references may be tagged in dictionaries using the simple
<gi tei="yes">ref</gi> and <gi tei="yes">ptr</gi> elements defined in the core tag set
(section <xref target="COXR"/>), or the <soCalled>extended</soCalled>
pointing elements <gi tei="yes">xref</gi> and <gi tei="yes">xptr</gi> defined in the
additional tag set for linking, segmentation, and alignment (section<xref target="SAXR"/>
).  In addition, the <gi tei="yes">xr</gi> element may be used
to group all the information relating to a cross reference.  The
following elements may be used for tagging cross references within
dictionaries:
 
<tagList style="one-line"><tagDesc tagDoc="XR"/><tagDesc tagDoc="REF"/><tagDesc tagDoc="PTR"/><tagDesc tagDoc="XREF"/><tagDesc tagDoc="XPTR"/><tagDesc tagDoc="LBL"/></tagList>
 </p><p>As in other types of text, the actual pointing element (e.g.
<gi tei="yes">ref</gi> or <gi tei="yes">ptr</gi>) is used to tag the cross-reference target
proper (in dictionaries, usually the headword, possibly accompanyied by
a homograph number, a sense number, or other further restriction
specifiying what portion of the target entry is being referred to); as
usual, a <gi tei="yes">ptr</gi> element may be used when the actual text of the
target description can be reconstructed automatically, and a
<gi tei="yes">ref</gi> element is typically to be preferred when it cannot be
reconstructed automatically.
 <!-- in P4, XR or refPhr should go into core. -msm -->
 
The <gi tei="yes">xr</gi> element is used to group the target with any
accompanying phrases or symbols used to label the cross reference; the
cross reference label itself may be tagged as a <gi tei="yes">lbl</gi> or may
remain untagged.  Both of the following are thus legitimate:
 
<q rend="display"> <hilited rend="bold">glee</hilited> ... Compare
<hilited rend="bold">madrigal</hilited> (sense 1) [CED] </q>
 
<eg><![CDATA[<entry><form><orth>glee</></>
  <!-- ... -->
  <xr>Compare <ptr target='MADRIGAL.1'></xr>
</entry>]]></eg>
 
<q rend="display"> <hilited rend="bold">hostellerie</hilited> Syn. de
h&ocirc;tellerie (sens 1).  [DNT] </q>
 
<eg><![CDATA[<xr type=syn>
  <lbl>Syn. de</lbl> <ref>h&ocirc;tellerie (sens 1)</ref>.
</xr>]]></eg>
 
In addition to using, or not using, <gi tei="yes">lbl</gi> to mark the
cross-reference label, the two examples differ in another way.  The
former assumes that the first sense of <cited>madrigal</cited> has the
SGML identifier <q>madrigal.1</q>, and that the specific form of the
reference in the source volume can be reconstructed, if needed, from
that information.  The latter does not require the first sense of
<q>h&ocirc;tellerie</q> to have an SGML identifier, and retains
the print form of the cross reference; by omitting the <att tei="yes">target</att>
attribute of the <gi tei="yes">ref</gi> element, however, the second example does
assume implicitly either that some software could usefully parse the
phrase tagged as a <gi tei="yes">ref</gi> and find the location referred to, or
else that such processing will not be necessary.
 </p><p>The <att tei="yes">type</att> attribute on the pointing element or on the
<gi tei="yes">xr</gi> element may be used to indicate what kind of cross
reference is being made, using any convenient typology. Since
different dictionaries may label the same kind of cross reference in
different ways, it may be useful to give normalized indications in the
<att tei="yes">type</att> attribute, enabling the encoder to distinguish
irregular forms of cross reference more reliably:
 
<q rend="display"> <hilited rend="bold">rose</hilited>2 ... vb. the past
tense of <hilited rend="bold">rise</hilited>.  [CED] </q>
 
<eg><![CDATA[<entry type='xr, hom' n=2>
  <form><orth>rose</orth><!-- ... --></form>
  <!-- ... -->
  <xr type=pastof>
    <lbl>the past tense of</lbl>
    <ref target='RISE'>rise</ref>
  </xr>
</entry>]]></eg>
 
from cross-references for synonyms and the like:
 
<q rend="display"> <hilited rend="bold">antagonist</hilited> ... syn see
<hilited rend="bold">adverse</hilited> [W7] </q>
 
<eg><![CDATA[<xr type=syn>
  <lbl>syn see</lbl>
  <ref target='ADVERSE'>adverse</ref>
</xr>]]></eg>
 
Strictly speaking, this reference is not to the entry given, but to the
list of synonyms it contains.  Slightly more complicated is this
reference to an illustration accompanying another article:
 
<q rend="display"> <hilited rend="bold">ax, axe</hilited> ... &rarr; see
the illus at <hilited rend="bold">tool</hilited> [OALD] </q>
 
This entry refers to the illustration at the entry for
<cited>tool</cited>, not the entry itself.  The <att tei="yes">target</att>
attribute might give the identifier of the illustration itself, or of
the enclosing entry (in which case the <att tei="yes">type</att> attribute might
be used to infer that the reference is actually to the illustration, not
the entry as a whole).
 
<eg><![CDATA[<xr type='see illustration'>
  <lbl>see the illus at</lbl>
  <ptr target='TOOL.illus'>
</xr>]]></eg>
 
In some cases, the cross reference is to a particular subset of the
meanings of the entry in question:
 
<q rend="display"> <hilited rend="bold">globe</hilited> ...V. <hilited rend="bold">armillaire</hilited> (sph&egrave;re) [PR] </q>
 
<eg><![CDATA[<xr>V. <ref target='ARMILLAIRE'>armillaire</ref>
       <lbl type='sense-restriction'>sph&egrave;re</lbl>
</xr>]]></eg>
 
 </p><p>Cross-references occasionally occur in definition texts, example
texts, etc., or may be free-standing within an entry.  These may
typically be encoded using <gi tei="yes">ref</gi> or <gi tei="yes">ptr</gi>, without an
enclosing <gi tei="yes">xr</gi>.  For example:
 
<q rend="display"> <hilited rend="bold">entacher</hilited> ... <hilited rend="ital">Acte entach&eacute; de nullit&eacute;,</hilited> contenant
un vice de forme ou pass&eacute; par un incapable*.  [DNT] </q>
 
The asterisk signals a reference to the entry for
<cited>incapable</cited>.
 
<eg><![CDATA[<def>contenant un vice de forme ou pass&eacute;
par un <ptr target='INCAPABLE'>.</def>]]></eg><!-- surely this should have been tagged as a <ref> not a <ptr> LB ? -->
 
In some cases, the form in the definition is inflected, and thus
<gi tei="yes">ref</gi> must be used, as here:
 
<q rend="display"> <hilited rend="bold">justifier</hilited> ...4. IMPRIM
Donner a (une ligne) une longeur convenable au moyen de blancs (2,
sens 1, 3).  [DNT] </q>
 
<eg><![CDATA[<sense n='4'>
   <usg type=dom>imprim</usg>
   <def>Donner a (une ligne) une longeur convenable au moyen
        de <ref target='BLANC-2.1 blanc-2.3'>blancs (2, sens
        1, 3)</ref>
   </def>
</sense>]]></eg>
 </p><p>The formal definition for <gi tei="yes">xr</gi> is as follows:
 
<dtdFrag id="DDITPXR" n="Cross References"><tagDecl tagDoc="XR"/></dtdFrag>
 </p></div4><div4 id="DITPNO" name="Section" ref="Y"><head>Notes within Entries</head><!-- [Someone needs to look into this deeply, to find out     --><!-- what can actually appear within such notes.  We have     --><!-- seen domain labels, cross references, examples, and it   --><!-- is likely that grammatical information, related          --><!-- entries etc. can also appear.  We need an inventory in   --><!-- order to know what to do here.  At present we have       --><!-- left this largely unspecified.  -JV, NI]                 --><p>Dictionaries may include extensive explanatory notes about usage,
grammar, context, etc. within entries.  Very often, such notes appear as
a separate section at the end of an entry.  The <gi tei="yes">note</gi> element
should be used for such material.
 
<tagList style="one-line"><tagDesc tagDoc="NOTE"/></tagList>
 </p><p>For example:
 
<q rend="display"> <hilited rend="bold">ain't</hilited>
<code tei="yes" type="frag">(eInt)</code> <hilited rend="ital">Not standard. contraction
of</hilited> am not, is not, are not, have not <hilited rend="ital">or</hilited> has not: <hilited rend="ital">I ain't seen
it.</hilited>
....
<p>&utrif;<hilited rend="bold">Usage.</hilited>
Although the interrogative form <hilited rend="ital">ain't I?</hilited>
would be a natural contraction of <hilited rend="ital">am I
not?</hilited>, it is generally avoided in spoken English and never
used in formal English. [CED] </p></q>
 <!-- note: &triangle; is a small triangle -JV, NI             --><!-- note: &triangle; changed to utrif to avoid name conflict (msm)  -->
 
<eg><![CDATA[<entry>
  <form type=contr>
    <orth>ain't</orth>
    <pron>eInt</pron>
  </form>
  <usg type=reg>Not standard</usg>
  <form type=full>
    <lbl>contraction of</lbl>
    <orth>am not</orth>
    <orth>is not</orth>
    <orth>are not</orth>
    <orth>have not</orth>
    <orth>has not</orth>
  </form>
  <eg>
    <q>I ain't seen it.</q>
  </eg><!-- ... -->
  <note type=usage>
     Although the interrogative form <mentioned>ain't
     I?</> would be a natural contraction of <mentioned>am
     I not?</>, it is generally avoided in spoken English
     and never used in formal English.
  </note>
</entry>]]></eg>
 </p><p>The formal declaration for <gi tei="yes">note</gi> is given in section <xref target="CONO"/>.  It has this form:
 
<dtdFrag id="DDITPNO" n="[Note]" file="dummy"><tagDecl tagDoc="NOTE"/></dtdFrag>
 </p></div4></div3><div3 id="DITPRE" name="subsection" ref="Y"><head>Related Entries</head><p>The <gi tei="yes">re</gi> element encloses a degenerate entry which appears in
the body of another entry for some purpose.  Many dictionaries include
related entries for direct derivatives or inflected forms of the entry
word, or for compound words, phrases, collocations, and idioms
containing the entry word.
 </p><p>Related entries can be complex, and may in fact include any of the
information to be found in a regular entry.  Therefore, the <gi tei="yes">re</gi>
element is defined to contain the same elements as an <gi tei="yes">entry</gi>
element, with the exception that it may not contain any nested
<gi tei="yes">re</gi> elements.
 </p><p>Examples:
 
<q rend="display"> <hilited rend="bold">bevvy</hilited> <code tei="yes" type="frag">("bEvI)</code> Dialect.  ~ n., pl. -vies. 1. a drink, esp. an alcoholic
one: we had a few bevvies last night. 2. a night of drinking.  ~
vb. - vies, -vying, -vied (intr.) 3. to drink alcohol [probably from
Old French vevee, buvee, drinking] --'bevvied adj.  [CED] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth>bevvy</orth>
    <pron>"bEvI</pron>
  </form>
  <usg type=reg>Dialect</usg>
  <hom>
    <gramGrp><pos>n</pos></gramGrp>
    <!-- ... -->
    <sense n='1'>
      <def>a drink, esp. an alcoholic one</def>
      <!-- ... -->
    </sense>
    <!-- ... -->
  </hom>
  <hom>
    <gramGrp><pos>vb</pos></gramGrp>
    <!-- ... -->
    <sense n='3'><def>to drink alcohol</def></sense>
  </hom>
  <etym>probably from <lang>Old French</lang>
       <mentioned>bevee</>, <mentioned>buvee</>
       <gloss>drinking</gloss>
  </etym>
  <re type=derived>
    <form>
      <orth>'bevvied</orth>
    </form>
    <gramGrp>
      <pos>adj</pos>
    </gramGrp>
  </re>
</entry>]]></eg>
 </p><p>The formal definition of <gi tei="yes">re</gi> is
 
<dtdFrag id="DDITPRE" n="Related entries"><tagDecl tagDoc="RE"/></dtdFrag><?tei:EOF p2ditp.odd ??>
<?tei:SOF p2dihw.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2dihw.odd,v $
# Revision 1.6  1994/03/27  16:29:43  lou
# *** empty log message ***
#
# Revision 1.5  1994/03/07  15:19:03  lou
# fix ^Z
#
# Revision 1.4  1994/03/07  14:44:05  lou
# apply typos etc. noted by DTB et al.
#
# Revision 1.3  1994/01/15  20:45:31  msmcq
# cmsmcq revision for P3
# see comments for details
#
# Revision 1.2  1994/01/04  19:38:25  msmcq
# first cut at DI revisions
# --><!-- Revisions:                                               --><!-- 94-01-15 : MSM : typo                                    --><!-- 94-01-14 : MSM : fix oRef, pRef examples:  target= NOT form= --><!-- 94-01-12 : MSM : stylistic fixes                         --><!-- 94-01-12 : MSM : number not num                          --><!-- 94-01-12 : MSM : correct entity:  oelig, not oe          --><!-- 94-01-12 : MSM : fix dashes inside commented-out exx     --><!-- 94-01-11 : MSM : changes for P3, mostly recasting,       --><!--                  pruning examples, commenting            --><!-- 94-01-11 : MSM : rename gram as gramGrp as per Eynsham   --><!-- 94-01-09 : MSM : move class decls into dtdFrag here      --><!-- 93-10-19 : MSM : rename tgt as te                        --><!-- 93-10-19 : MSM : change sn attribute to n                --><!-- 93-10-19 : MSM : change hn attribute to n                --><!-- 93-10-19 : MSM : delete some notes from ni, jv           --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-04-12 : MSM : delete N att on divs                    -->
 </p></div3></div2><div2 id="DIHW" name="subsection" ref="Y"><head>Headword and Pronunciation References</head><!-- oRef, pRef, oVar and pVar                                --><p>Examples, definitions, etymologies, and occasionally other elements
such as cross references, orthographic forms, etc., often contain a
shortened or iconic reference to the headword, rather than repeating the
headword itself.  The references may be to the orthographic form or to
the pronunciation, to the form given or to a variant of that form.  The
following elements are used to encode such iconic references to a
headword:
 
<tagList style="one-line"><tagDesc tagDoc="OREF" atts="type"/><tagDesc tagDoc="PREF"/><tagDesc tagDoc="OVAR" atts="type"/><tagDesc tagDoc="PVAR"/></tagList>
 </p><p>As members of the class <ident tei="yes" type="class">formPointers</ident>, all these
elements share a <att tei="yes">target</att> attribute, which may optionally be
used to resolve any ambiguity about the headword form being referred to.
 
<adList classDoc="FORMPTRS" atts="target"/>
 </p><p>Headword references come in a variety of formats:
 
<list type="gloss"><label>~        </label><item>indicates a reference to the full form of
                      the headword</item><label>pref~    </label><item>gives a prefix to be affixed to the headword</item><label>~suf     </label><item>gives a suffix to be affixed to the headword</item><label>A~       </label><item>gives the first letter in upper case,
                      indicating that the headword is capitalized</item><label>pref~suf </label><item>gives a prefix and a suffix to be affixed to
                      the headword</item><label>a.       </label><item>gives the initial of the word followed by a
                      full stop, to indicate reference to the full form
                      of the headword</item><label>A.       </label><item>refers to a capitalized form of the headword<!-- <label>[font-shifted] <item>some font shift (e.g.,       --><!-- italics) for (e.g.) a suffix, prefix, inflected form,    --><!-- etc.                                                     --></item></list>
 <!-- last item commented out because I do not understand      --><!-- what it is supposed to mean.  (msm)                      -->
 </p><p>The <gi tei="yes">oRef</gi> element should be used for iconic or shortened
references to the orthographic form(s) of the headword itself.  It is an
empty element and replaces, rather than enclosing, the reference.  Note
that the reference to a headword is not necessarily a simple string
replacement.  In the example <q><hilited rend="bold">colour</hilited>1, (US = color) ...~ films; ~ TV;
Red, blue and yellow are ~s.</q> [OALD], the tilde stands for either
headword form (<cited>colour</cited>, <cited>color</cited>).
 </p><p>Examples:
 
<q rend="display"> <hilited rend="bold">colonel</hilited> ... army officer
above a lieutenant-~.  [OALD] </q>
 
<eg><![CDATA[<def>army officer above a lieutenant-<oRef></def>]]></eg>
 <!-- <q rend=display>                                         --><!-- take ...  < I don't &tilde; milk in my tea >                   --><!-- [NPEG]                                                   --><!-- </q>                                                     -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <eg><q>I don't <oRef> milk in my tea</q></eg>            --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 
<q rend="display"><hilited rend="bold">academy</hilited> ... The Royal A~ of Arts [OALD]</q>
 
<eg><![CDATA[<q>The Royal <oRef type=cap> of Arts</q>]]></eg>
 <!-- abeja, f. 1. (ento.) bee. 2. busy bee, hard worker. 3.   --><!-- (astron.)  A., Musca.  &mdash a. albanila, mason bee; a. --><!-- carpintera, carpenter bee; a. reina or maestra, queen    --><!-- bee; a. neutra or obrera, worker bee.  [SSSE]            -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              -->
 <!-- encoding for sense 3 only--><!-- <sense n='3'>                                            --><!--   <usg type=sem>astron</usg>                             --><!--   <form>                                                 --><!--     <orth><oRef type=cap></orth>                         --><!--   </form>                                                --><!--   <trans>                                                --><!--     <tr>Musca</tr>                                       --><!--   </trans>                                               --><!--   <re>                                                   --><!--     <sense>                                              --><!--       <form>                                             --><!--         <orth><oRef> albanila</orth>                     --><!--       </form>                                            --><!--       <trans>                                            --><!--         <tr>mason bee</tr>                               --><!--       </trans>                                           --><!--     </sense>                                             --><!--     <sense>                                              --><!--       <form>                                             --><!--         <orth><oRef> carpintera</orth>                   --><!--       </form>                                            --><!--       <trans>                                            --><!--         <tr>carpenter bee</tr>                           --><!--       </trans>                                           --><!--     </sense>                                             --><!--     <sense>                                              --><!--       <form>                                             --><!--         <orth><oRef> reina</orth>                        --><!--         <orth orig='maestra'><oRef> maestra</orth>       --><!--       </form>                                            --><!--       <trans>                                            --><!--         <tr>queen bee</tr>                               --><!--       </trans>                                           --><!--     </sense>                                             --><!--     <sense>                                              --><!--       <form>                                             --><!--         <orth><oRef> neutra</orth>                       --><!--         <orth orig='obrera'><oRef> obrera</orth>         --><!--       </form>                                            --><!--       <trans>                                            --><!--         <tr>worker bee</tr>                              --><!--       </trans>                                           --><!--     </sense>                                             --><!--   </re>                                                  --><!-- </sense>                                                 --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p><p>The following example demonstrates the use of the <att tei="yes">target</att>
attribute to refer to a specific form of the headword:
 
<q rend="display"> <hilited rend="bold">vag-</hilited> or <hilited rend="bold">vago-</hilited> comb form ... : vagus nerve &lt; <hilited rend="bold">vag</hilited>al &gt; &lt; <hilited rend="bold">vago</hilited>tomy &gt;
[W7] </q>
 
<eg><![CDATA[<entry>
  <form>
    <orth id=O1>vag-</orth>
    <orth id=O2>vago-</orth>
  </form>
  <!-- ... -->
  <def>vagus nerve</def>
  <eg>
    <q><oRef target=O1 type=nohyph>al</q>
    <q><oRef target=O2 type=nohyph>tomy</q>
  </eg>
</entry>]]></eg>
 <!-- <p>In this example the hyphen is retained in the first   --><!-- oRef, and not in the second:                             -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- 1 deuter- or deutero- ... <DEUTERO-genesis>              --><!-- 2 deuter- or deutero- ... <DEUTERated>    [W7]           --><!--                                                          --><!-- <entry n=1>                                              --><!--   <form>                                                 --><!--     <orth id=O11>deuter-</orth>                          --><!--     <orth id=O12>deutero-</orth>                         --><!--   </form>                                                --><!--  ...                                                     --><!--   <eg>                                                   --><!--     <q><oRef target=O12>genesis</q>                        --><!--   </eg>                                                  --><!-- </entry>                                                 --><!--                                                          --><!-- <entry n=2>                                              --><!--   <form>                                                 --><!--     <orth id=O21>deuter-</orth>                          --><!--     <orth id=O22>deutero-</orth>                         --><!--   </form>                                                --><!--  ...                                                     --><!--   <eg>                                                   --><!--     <q><oRef target=O21 type=nohyph>ated</q>               --><!--   </eg>                                                  --><!-- </entry>                                                 --><!--                                                          --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 
 
 <!-- neur- or neuro- comb form [NL, fr.  Gk, nerve, sinew,    --><!-- fr. neuron &mdash more at *nerve*] 1 :  nerve <NEURal>   --><!-- <NEUROlogy> 2 :  neural :  neural and <NEUROmuscular>.   --><!-- [WNC]                                                    -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--   <form>                                                 --><!--     <orth id=O1>neur-</orth>                             --><!--     <orth id=O2>neuro-</orth>                            --><!--   </form>                                                --><!--   <gramGrp>                                              --><!--     <pos>comb form</pos>                                 --><!--   </gramGrp>                                             --><!--   <etym><lang>NL</lang> fr. <lang>Gk</lang> <cited>nerve</cited> --><!--         <gloss>sinew</gloss> fr. <cited>neuron</cited>   --><!--     <xr target=ETYM>                                     --><!--        <xrl>more at</xrl>                                --><!--        <xref path=nerve>                                 --><!--     </xr>                                                --><!--   </etym>                                                --><!--   <sense n='1'>                                          --><!--     <def>nerve</def>                                     --><!--     <eg>                                                 --><!--       <q><oRef target=O1 type=nohyph>al</q>                --><!--     </eg>                                                --><!--     <eg>                                                 --><!--       <q><oRef form=o2 type=nohyph>logy</q>              --><!--     </eg>                                                --><!--   </sense>                                               --><!--   <sense n='2'>                                          --><!--     <def>neural</def>                                    --><!--     <def>neural and</def>                                --><!--     <eg>                                                 --><!--       <q><oRef target=O2 type=nohyph>muscular</q>          --><!--     </eg>                                                --><!--   </sense>                                               --><!-- </entry>                                                 --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p><p>In many cases the reference is not to the orthographic form of the
headword, but rather to another form of the headword --- usually to an
inflected form.  In these cases, the element <gi tei="yes">oVar</gi> should be
used; this element takes as its content the string as it appears in the
text.
 
<q rend="display"> <hilited rend="bold">take</hilited> ... &lt; Mr Burton
<hilited rend="bold">took</hilited> us for French &gt; [NPEG] </q>
 
<eg><![CDATA[<eg>
  <q>Mr Burton <oVar type=pt>took</oVar> us for French</q>
</eg>]]></eg>
 
<q rend="display"> <hilited rend="bold">take</hilited> ... &lt; was quite
<hilited rend="bold">~n</hilited> with him &gt; [NPEG] </q>
 
<eg><![CDATA[<eg>
  <q>was quite <oVar type=pp><oRef>n</oVar> with him</q>
</eg>]]></eg>
 </p><p>Note that, in the example above, tilde and font shift combine.  The
encoding
 
<eg><![CDATA[<q>was quite <oRef>n with him</q>]]></eg>
 
would correspond to <q>was quite ~n with him</q> (no font shift).
 <!-- What? (msm) -->
 </p><p>The next example shows a discontinuous reference, using the attributes
<att tei="yes">next</att> and <att tei="yes">prev</att>, which are defined in the additional
tag set for linking, segmentation, and alignment (see chapter <xref target="SA"/>) and therefore require that that tag set be selected in
addition to that for dictionaries.
 
<q rend="display"> <hilited rend="bold">mix up</hilited>... &lt; it's easy to
<hilited rend="bold">mix</hilited> her <hilited rend="bold">up</hilited>
with her sister &gt; [NPEG] </q>
 
<eg><![CDATA[<eg><q>it's easy to <oVar next=ov2 id=OV1>mix</oVar>
     her <oVar prev=ov1 id=OV2>up</oVar> with her
     sister</q>
</eg>]]></eg>
 </p><p>In addition, some dictionaries make reference to the
pronunciation of the headword in the pronunciation of
related entries, variants, or examples.  The <gi tei="yes">pRef</gi> and
<gi tei="yes">pVar</gi> elements should be used for such references.
 
<q rend="display"> <hilited rend="bold">hors d'oeuvre</hilited>
<code tei="yes" type="frag">/,aw'duhv </code> (Fr O:r d&oelig;vr)/ n, pl hors d'oeuvres also
hors d'oeuvre <code tei="yes" type="frag">/'duhv(z) </code> (Fr ~)/ [NPEG] </q>
 
<eg><![CDATA[<form>
  <orth>hors d'oeuvre</orth>
  <pron>%aU"dUv</pron>
  <form>
    <usg type=lang>Fr</usg>
    <pron id=P2>OR d0vR</pron>
  </form>
</form>
<!-- ... -->
<form type=infl>
  <number>pl</number>
  <orth>hors d'oeuvres</orth>
  <orth>hors d'oeuvre</orth>
  <pron extent=part>"dUv(z)</pron>
  <form>
    <usg type=lang>Fr</usg>
    <pron><pRef target=P2></pron>
  </form>
</form>]]></eg>
 </p><p>Because headword and pronunciaton references can occur virtually
anywhere in an entry, the <gi tei="yes">oRef</gi>, <gi tei="yes">oVar</gi>, <gi tei="yes">pRef</gi>,
and <gi tei="yes">pVar</gi> elements can appear within any other element defined
for dictionary entries.
 </p><p>Since existing printed dictionaries use different conventions for
headword references (swung dash, first letter abbreviated form,
capitalization or italicization of the word, etc.) the exact method used
should be documented in the header.
 </p><p>The class of headword references is defined thus:
 
<dtdFrag id="DEDIHW" n="Classes for headword references"><claDecl classDoc="FORMPTRS" type="model"/><claDecl classDoc="FORMPTRS" type="atts"/></dtdFrag>
 </p><p>The formal declaration for headword reference elements is:
 
<dtdFrag id="DDIHW" n="Headword references"><tagDecl tagDoc="OREF"/><tagDecl tagDoc="OVAR"/><tagDecl tagDoc="PREF"/><tagDecl tagDoc="PVAR"/></dtdFrag>
 
 <?tei:EOF p2dihw.odd ??>
<?tei:SOF p2dimv.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2dimv.odd,v $
    * Revision 1.9  1998/01/30 16:45:57  tei
    * fix log keyword
    *
    * Revision 1.8  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.7  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.6  1994/03/27  16:29:46  lou
    * *** empty log message ***
    * 
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    * 
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    * 
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    * 
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    *--><!-- Revisions:                                               --><!-- 4 jan 98 : LB : minor fixes from 1996-06-13 CMSMCQ --><!-- 94-04-08 : MSM : cosmetic changes to line format in some long qs --><!-- 94-01-15 : MSM : minor lastminute fixes                  --><!-- 94-01-14 : MSM : suppress value in adlist                --><!-- 94-01-14 : MSM : expand= and value= merged into norm=    --><!-- 94-01-14 : MSM : suppress claims that diglobal class is global --><!-- 94-01-14 : MSM : delete ghost endtag for morph           --><!-- 94-01-14 : MSM : fix typo in thyrostimuline example      --><!-- 94-01-14 : MSM : restore name of orig attribute          --><!-- 94-01-14 : MSM : restore opt=y                           --><!-- 94-01-14 : MSM : change OPT usage to solve name clash problems --><!-- 94-01-14 : MSM : fix xref to auricle                     --><!-- 94-01-12 : MSM : stylistic changes                       --><!-- 94-01-12 : MSM : number not num                          --><!-- 94-01-12 : MSM : correct some typos, SGML errors         --><!-- 94-01-11 : MSM : revise for clarity                      --><!-- 94-01-11 : MSM : rename gram as gramGrp as per Eynsham   --><!-- 94-01-09 : MSM : add dtdFrag                             --><!-- 94-01-05 : MSM : replace hi with hilited, & with &amp    --><!-- 94-01-05 : MSM : replace ital, bold with hi              --><!-- 93-10-19 : MSM : rename tgt as te                        --><!-- 93-10-19 : MSM : change sn attribute to n                --><!-- 93-10-19 : MSM : delete some notes from ni, jv           --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-04-12 : MSM : delete N att on divs                    --><!-- 93-03-08 : MSM : change pronunciation of pastel          -->
 </p></div2><div2 id="DIMV" name="subsection" ref="Y"><head>Typographic and Lexical Information in Dictionary Data</head><p>Among the many possible views of dictionaries, it is useful to
distinguish at least the following three, which help to clarify some
issues raised with particular urgency by dictionaries, on account of the
complexity of both their typography and their information structure.
 
<list type="bullets"><item>(a) the <term>typographic view</term>, which is concerned with the
two-dimensional printed page, including information about line and
page breaks and other features of layout
 </item><item>(b) the <term>editorial view</term> --- the one-dimensional
sequence of tokens which can be seen as the input to the typesetting
process; the wording and punctuation of the text and the sequencing of
items are visible in this view, but specifics of the typographic
realization are not
 </item><item>(c) the <term>lexical view</term> --- this view includes the
underlying information represented in a dictionary, without concern for
its exact textual form
 </item></list>
 </p><p>For example, a domain indication in a dictionary entry might be
broken over a line and therefore hyphenated (<q>naut-</q> <q>ical</q>);
the typographic view of the dictionary preserves this information.  In a
purely editorial view, the particular form in which the domain name is
given in the particular dictionary (as <q>nautical</q>, rather than
<q>naut.</q>, <q>Naut.</q>, etc.) would be preserved, but the fact of
the line break would not.  Font shifts might plausibly be included in
either a strictly typographic or an editorial view.  In the lexical
view, the only information preserved concerning domain would be some
standard symbol or string representing the nautical domain (e.g.
<q>naut.</q>) regardless of the form in which it appears in the printed
dictionary.
 </p><p>In practice, publishers begin with the lexical view --- i.e., lexical
data as it might appear in a database --- and generate first the
editorial view, which reflects editorial choices for a particular
dictionary (such as the use of the abbreviation <q>Naut.</q> for
<q>nautical</q>, the fonts in which different types of information are
to be rendered, etc.), and then the typographic view, which is tied to a
specific printed rendering.  Computational linguists and philologists
often begin with the typographic view and analyse it to obtain the
editorial and/or lexical views.  Some users may ultimately be concerned
with retaining only the lexical view, or they may wish to preserve the
typographic or editorial views as a reference text, perhaps as a guard
against the loss or misinterpretation of information in the translation
process.  Some researchers may wish to retain all three views, and study
their interrelations, since research questions may well span all three
views.
 </p><p>In general, an electronic encoding of a text will allow the recovery
of at least one view of that text (the one which guided the encoding);
if editorial and typographic practices are consistently applied in the
production of a printed dictionary, or if exceptions to the rules are
consistently recorded in the electronic encoding, then it is <emph>in
principle</emph> possible to recover the editorial view from an encoding
of the lexical view, and the typographic view from an encoding of the
editorial view.  In practice, of course, the severe compression of
information in dictionaries, the variety of methods by which this
compression is achieved, the complexity of formulating completely
explicit rules for editorial and typographic practice, and the relative
rarity of complete consistency in the application of such rules, all
make the mechanical transformation of information from one view into
another something of a vexed question.
 </p><p>This section describes some principles which may be useful in
capturing one or the other of these views as consistently and completely
as possible, and describes some methods of attempting to capture more
than one view in a single encoding.  Only the editorial and lexical
views are explicitly treated here; for methods of recording the physical
or typographic details of a text, see chapter <xref target="PH"/>.  Other
approaches to these problems, such as the use of repetitive encoding and
links to show their correspondences, or the use of feature structures to
capture the information structure, and of the <att tei="yes">ana</att> and
<att tei="yes">inst</att> attributes to link feature structures to a
transcription of the editorial view of a dictionary, are not discussed
here.  (For feature structures, see chapter <xref target="FS"/>.  For
linkage of textual form and underlying information, see chapter <xref target="AI"/>.)
 </p><div3 id="DIMVTV" name="subsection" ref="Y"><head>Editorial View</head><p>Common practice in encoding texts of all sorts relies on principles
such as the following, which can be used successfully to capture the
editorial view when encoding a dictionary:
 
<list type="ordered"><item>All characters of the source text should be retained, with the
possible exception of <term>rendition text</term> (for which see further
below).
 </item><item>Characters appearing in the source text should typically be given
as character data content in the SGML document, rather than as the value
of an attribute; again, rendition text may optionally be excepted from
this rule.
 </item><item>Apart from the characters or graphics in the source text, nothing
else should appear as content in the SGML document, although it may be
given in attribute values.
 </item><item>The material in the source text should appear in the encoding in
the same order.  Complications of the character sequence by footnotes,
marginal notes, etc., text wrapping around illustrations, etc., may be
dealt with by the usual means (for notes, see section <xref target="CONO"/>).<note source="auth" place="foot" anchored="Y">Complications of sequence caused by
marginal or interlinear insertions and deletions, which are frequent in
manuscripts, or by unconventional page layouts, as in concrete poetry,
magazines with imaginative graphic designers, and texts about the nature
of typography as a medium, typically do not occur in dictionaries, and
so are not discussed here.</note>
 </item></list>
 </p><p>In a very conservative transcription of the editorial view of a text,
<term>rendition characters</term> (e.g. the commas, parentheses, etc.,
used in dictionary entries to signal boundaries among parts of the
entry) and <term>rendition text</term> (for example, conjunctions
joining alternate headwords, etc.) are typically retained.  Removing the
SGML tags from such a transcription will leave all and only the
characters of the source text, in their original sequence.<note source="auth" place="foot" anchored="Y">This is a slight oversimplification.  Even in conservative
transcriptions, it is common to omit page numbers, signatures of
gatherings, running titles and the like.  The simple description above
also elides, for the sake of simplicity, the difficulties of assigning a
meaning to the phrase <q>original sequence</q> when it is applied to the
printed characters of a source text; the <q>original sequence</q>
retained or recovered from a conservative transcription of the editorial
view is, of course, the one established during the transcription by the
encoder.</note>
 </p><p>Consider, for example, the following entry:
 
<q rend="display"><hilited rend="bold">pinna</hilited> ('pIn@) n., pl. -nae (-ni:) <hilited rend="ital">or</hilited> -nas.
1. any leaflet of a pinnate compound leaf. 2. <hilited rend="ital">Zoology</hilited>. a feather, wing, fin, or similarly shaped
part. 3. another name for <hilited rend="bold">auricle</hilited> (sense
2). [C18:  via New Latin from Latin:  wing, feather, fin]      [CED]</q>
 
A conservative encoding of the editorial view of this entry, which
retains all rendition text, might resemble the following:
 
<eg><![CDATA[<entry>
  <form>
    <orth>pinna</orth>
    <pron>("pIn@)</pron>
  </form>
  <gramGrp><pos>n.</pos>, </gramGrp>
  <form type=infl>
    <number>pl.</number>
    <form>
      <orth type=lat extent=part>-nae</orth>
      <pron extent=part>(-ni:)</pron>
    </form>
    or
    <orth type=std extent=part>-nas</orth>
  </form>
  <sense n='1'>
    1. <def>any leaflet of a pinnate compound leaf.</def>
  </sense>
  <sense n='2'>
    2. <usg type=dom>Zoology</usg>
    <def>a feather, wing, fin, or similarly shaped part.</def>
  </sense>
  <sense n='3'>
    3.<xr type=syn>
      <lbl>another name for</lbl>
      <ref target='AURICLE.2'>auricle (sense 2).</ref>
    </xr>
  </sense>
  <etym>
     [<date>C18</date>: via <lang>New Latin</lang> from
     <lang>Latin</lang>: <gloss>wing</gloss>, <gloss>feather</gloss>,
     <gloss>fin</gloss>]
  </etym>
</entry>]]></eg>
 </p><p>A somewhat simplified encoding of the editorial view of this entry
might exploit the fact that rendition text is often systematically
recoverable.  For example, parentheses consistently appear around
pronunciation in this dictionary, and thus are effectively implied by
the start- and end-tags for <gi tei="yes">pron</gi>.<note source="auth" place="foot" anchored="Y">The omission
of rendition text is particularly common in systems for document
production; it is considered good practice there, since automatic
generation of rendition text is more reliable and more consistent than
attempting to maintain it manually in the electronic text.</note>
In such an encoding, removing the tags should exactly reproduce the
sequence of characters in the source, minus rendition text.  The
original character sequence can be recovered fully by replacing tags
with any rendition text they imply.
 </p><p>Encoding in this way, the example given above might resemble the
following.  The <gi tei="yes">tagUsage</gi> element in the header would be used to
record the following patterns of rendition text:
 
<list type="bullets"><item>parentheses appear around <gi tei="yes">pron</gi> elements</item><item>commas appear before inflected forms</item><item>the word <q>or</q> appears before alternate forms</item><item>brackets appear around the etymology</item><item>full stops appear after <gi tei="yes">pos</gi>, inflection information,
and sense numbers</item><item>senses are numbered in sequence unless otherwise specified using
the global <att tei="yes">n</att> attribute</item></list>
 
<eg><![CDATA[<entry>
  <form>
    <orth>pinna</orth>
    <pron>"pIn@</pron>
  </form>
  <gramGrp><pos>n</pos></gramGrp>
  <form type=infl>
    <number>pl</number>
    <form>
      <orth type=lat extent=part>-nae</orth>
      <pron extent=part>-ni:</pron>
    </form>
    <orth type=std extent=part>-nas</orth>
  </form>
  <sense n='1'>
    <def>any leaflet of a pinnate compound leaf.</def>
  </sense>
  <sense n='2'>
    <usg type=dom>Zoology</usg>
    <def>a feather, wing, fin, or similarly shaped part.</def>
  </sense>
  <sense n='3'>
    <xr type=syn>
      <lbl>another name for</lbl>
      <ref>auricle (sense 2).</ref>
    </xr>
  </sense>
  <etym>
     <date>C18</date>: via <lang>New Latin</lang> from
     <lang>Latin</lang>: <gloss>wing</gloss>, <gloss>feather</gloss>,
     <gloss>fin</gloss>
  </etym>
</entry>]]></eg>
 </p><p>When rendition text is omitted, it is recommended that the means to
regenerate it be fully documented, using the <gi tei="yes">tagUsage</gi> element
of the TEI header.
 </p><p>If rendition text is used systematically in a dictionary, with only a
few mistakes or exceptions, the global attribute <att tei="yes">rend</att> may be
used on any tag to flag exceptions to the normal treatment.  The values
of the <att tei="yes">rend</att> attribute are not prescribed, but it can be used
with values such as <code tei="yes" type="frag">no-comma</code>, <code tei="yes" type="frag">no-left-paren</code>, etc.
Specific values can be documented using the <gi tei="yes">rendition</gi> element
in the TEI header.
 </p><p>In the following (imaginary) example, no left parenthesis precedes
the pronunciation:
 
<q rend="display"><hilited rend="bold">biryani</hilited> or
<hilited rend="bold">biriani</hilited> %bIrI"A:nI)
any of a variety of Indian
dishes ... [from Urdu]</q>
 
This irregularity can be recorded thus:
 
<eg><![CDATA[<entry>
  <form>
    <orth>biryani</orth>
    <orth>biriani</orth>
    <pron rend=noleftparen>%bIrI"A:nI</pron>
  </form>
  <def>any of a variety of Indian dishes ... </def>
  <etym>from <lang>Urdu</lang></etym>
</entry>]]></eg>
 </p></div3><div3 id="DIMVLV" name="subsection" ref="Y"><head>Lexical View</head><p>If the text to be interchanged retains only the lexical view of the
text, there may be no concern for the recoverability of the editorial
(not to speak of the typographic) view of the text.  However, it is
strongly recomended that the TEI header be used to document fully the
nature of all alterations to the original data, such as normalization of
domain names, expansion of inflected forms, etc.
 </p><p>In an encoding of the lexical view of a text, there are degrees of
departure from the original data:  normalizing inconsistent forms like
<q>nautical</q>, <q>naut</q>., <q>Naut.</q>, etc., to <q>nautical</q> is
a relatively slight alteration; expansion of <q>delay -ed -ing</q> to
<q>delay, delayed, delaying</q> is a more substantial departure.  Still
more severe is the rearranging of the order of information in
entries --- for example,
 
<list type="bullets"><item>reorganizing the order of elements in an entry to show their
relationship, as in
 
<q rend="display"><hilited rend="bold">clem</hilited> (klEm) or clam vb. clems,
clemming, clemmed
or clams, clammimg, clammed    [CED]</q>
 
where in a strictly lexical view one might wish to group
<q>clem</q> and <q>clam</q> with their respective inflected forms.
 </item><item>splitting an entry into two separate entries, as in
 
<q rend="display"><hilited rend="bold">celi.bacy</hilited> /"selIb@sI/ n [U] state of living
unmmarried, esp as a religious obligation. celi.bate
/"selIb@t/ n [C] unmmarried person (esp a priest who has
taken a vow not to marry).    [OALD]</q>
 
For some purposes, this entry might usefully be split into an entry for
<q>celibacy</q> and a separate entry for <q>celibate</q>.
 </item></list>
 </p><p>An encoding which captures the lexical view of the example given in
the previous section might look something like the following.  In this
encoding,
 
<list type="bullets"><item>abbreviated forms have been silently expanded</item><item>some forms have been moved to allow related forms to be grouped
together</item><item>the part of speech information has been moved to allow all forms
to be given together</item><item>the cross reference to <q>auricle</q> has been simplified</item></list>
 
<eg><![CDATA[<entry>
  <form>
    <orth>pinna</orth>
    <pron>"pIn@</pron>
    <form type=infl>
      <number>pl</number>
      <form>
        <orth type=lat>pinnae</orth>
        <pron>'pIni:</pron>
      </form>
      <orth type=std>pinnas</orth>
    </form>
  </form>
  <gramGrp>
    <pos>n</pos>
  </gramGrp>
  <sense n='1'>
    <def>any leaflet of a pinnate compound leaf.</def>
  </sense>
  <sense n='2'>
    <usg type=dom>Zoology</usg>
    <def>a feather, wing, fin, or similarly shaped part.</def>
  </sense>
  <sense n='3'>
    <xr type=syn><ptr target=AURICLE.2></xr>
  </sense>
  <etym>
     <date>C18</date>: via <lang>New Latin</> from
     <lang>Latin</>: <gloss>wing</>, <gloss>feather</>,
     <gloss>fin</>
  </etym>
</entry>]]></eg>
 </p></div3><div3 id="DIMVBO" name="subsection" ref="Y"><head>Retaining Both Views</head><p>It is sometimes desirable to retain both the lexical and the editorial
view, in which case a potential conflict exists between the two.  When
there is a conflict between the encodings for the lexical and editorial
views, the principles described in the following sections may be
applied.
 </p><div4 name="Section" ref="Y"><head>Using Attribute Values to Capture Alternate Views</head><p>If the order of the data is the same in both views, then both views
may be captured by encoding one <soCalled>dominant</soCalled> view in
the character data content of the document, and encoding the other using
attribute values on the appropriate elements.  If all SGML tags were to
be removed, the remaining characters would be those of the dominant view
of the text.
 </p><p>The attribute class <ident tei="yes" type="class">dictionaries</ident> is used
to provide attributes for use in encoding multiple views of the same
dictionary entry.  These attributes are available for use on all
elements defined in this chapter
when the base tag set for dictionaries is selected.
 </p><p>When the editorial view is dominant, the following attributes may be
used to capture the lexical view:
 
<adList classDoc="DIGLOBAL" atts="norm split"/>
 <!-- <list type=gloss>                                        --><!-- <label><att>expand</att> <item>gives expanded form       --><!-- <label><att>norm</att> <item>gives normalized form       --><!-- <label><att>split</att> <item>gives the list of split    --><!-- values for a merged form                                 --><!-- <label><att>value</att> <item>gives a value which has    --><!-- no print realization                                     --><!-- </list>                                                  -->
 </p><p>When the lexical view is dominant, the following attributes may be
used to record the editorial view:
 
<adList classDoc="DIGLOBAL" atts="orig mergedin"/>
 <!-- <list type=gloss>                                        --><!-- <label><att>orig</att> <item>gives the original          --><!-- string or is the empty string when the element           --><!-- does not appear in original                              --><!-- <label><att>mergedin</att> <item>gives a                 --><!-- reference to another tag with id=XXX where the           --><!-- original appears as a merged form                        --><!-- </list>                                                  -->
 </p><p>One attribute is useful in either view:
 
<adList classDoc="DIGLOBAL" atts="opt"/>
 <!-- <list type=gloss>                                        --><!-- <label><att>opt</att> <item>identifies an optional element --><!-- </list>                                                  -->
 </p><p>For example, if the source text had the domain label <q>naut.</q>, it
might be encoded as follows.  With the editorial view dominant:
 
<eg><![CDATA[  <usg type=dom norm='nautical'>naut.</usg>]]></eg>
 
The lexical view of the same label would transcribe the normalized form
as content of the <gi tei="yes">usg</gi> element, the typographic form as an
attribute value:
 
<eg><![CDATA[  <usg type=dom orig='naut.'>nautical</usg>]]></eg>
 </p><p>If the source text gives inflectional information for the verb
<cited>delay</cited> as <q>delay, -ed, -ing</q>, it might usefully be
expanded to <q>delayed, delayed, delaying</q>.  An encoding of the
editorial view might take this form:
 
<eg><![CDATA[<form>
  <orth>delay</orth>
  <form type=infl>
    <orth norm='delayed' extent=part>-ed</orth>
    <tns norm='pst,pstp'></tns>
  </form>
  <form type=infl>
    <orth norm='delaying' extent=part>-ing</orth>
    <tns norm='prsp'></tns>
  </form>
</form>]]></eg>
 
Note the use of the <gi tei="yes">tns</gi> tag with null content, to enable the
representation of implicit information even though it has no print
realization.
 </p><p>The lexical view might be encoded thus:
 
<eg><![CDATA[<form>
  <orth>delay</orth>
  <form type=infl>
    <orth orig='-ed'>delayed</orth>
    <tns orig=''>pst</tns>
    <tns orig=''>pstp</tns>
  </form>
  <form type=infl>
    <orth orig='-ing'>delaying</orth>
    <tns orig=''>prsp</tns>
  </form>
</form>]]></eg>
 </p><p>A particular problem may be posed by the common practice of
presenting two alternate forms of a word in a single string, by marking
some parts of the word as optional in some forms.  The following entry
is for a word which can be spelled either <q>thyrostimuline</q> or
<q>thyr&eacute;ostimuline</q>:
 
<q rend="display"><hilited rend="bold">thyr(&eacute;)ostimuline</hilited> [tiR(e)ostimylin] ...</q>
 
With the editorial view dominant, this entry might begin thus:
 
<eg><![CDATA[<form>
  <orth split='thyrostimuline,
               thyr&eacute;ostimuline'>
        thyr(&eacute;)ostimuline</orth>
  <pron split='tiRostimylin,
               tiReostimylin'>
        tiR(e)ostimylin</pron>
</form>]]></eg>
 
With the lexical view dominant, however, two <gi tei="yes">orth</gi> and two
<gi tei="yes">pron</gi> elements would be encoded, in order to disentangle
the two forms; the <att tei="yes">orig</att> attribute would be used to record
the typographic presentation of the information in the source.
 
<eg><![CDATA[<form>
  <orth orig='thyr(&eacute;)ostimuline' id=O1>
        thyrostimuline</orth>
  <pron orig='tiR(e)ostimylin' id=P1>
        tiRostimylin</pron>
</form>
<form>
  <orth mergedin=o1>thyr&eacute;ostimuline</orth>
  <pron mergedin=p1>tiReostimylin</pron>
</form>]]></eg>
 </p><p>This example might also be encoded using the <att tei="yes">opt</att>
attribute combined with the attributes <att tei="yes">next</att> and
<att tei="yes">prev</att> defined in chapter <xref target="SA"/>.
 
<eg><![CDATA[<form>
  <orth next=o2 id=O1>thyr</orth>
  <orth prev=o1 next=o3 opt=y id=O2>&eacute;</orth>
  <orth prev=o2 id=O3>ostimuline</orth>
 
  <pron next=p2 id=P1>tiR</pron>
  <pron prev=p1 next=p3 opt=y id=P2>e</pron>
  <pron prev=p2 id=P3>ostimylin</pron>
</form>]]></eg>
 </p><p>Note that this transcription preserves both the lexical and editorial
views in a single encoding.  However, it has the disadvantage that the
strings corresponding to entire words do not appear in the encoding
uninterrupted, and therefore complex processing is required to retrieve
them from the encoded text.  The use of the <att tei="yes">opt</att> attribute is
recomended, however, when long spans of text are involved, or when the
optional part contains embedded tags.
 </p><p>For example, the following gives two definitions in one text:
<q>picture drawn with coloured chalk made into crayons</q>, and
<q>coloured chalk made into crayons</q>:
 
<q rend="display"><hilited rend="bold">pas.tel</hilited> /"p&amp;amp;stl US: p&amp;amp;"stel/ n 1 (picture drawn with) coloured
chalk made into crayons. 2...   [OALD]</q>
 </p><p>A simple encoding solution would be to leave the definition text
unanalysed, but this might be felt inadequate since it does not show
that there are two definitions.  A possible alternative encoding would
be:
 
<eg><![CDATA[<sense n='1'>
  <def>coloured chalk made into crayons</def>
  <def>picture drawn with coloured chalk made into crayons</def>
</sense>]]></eg>
 </p><p>This transcribes some characters of the source text twice, however,
which deviates from the usual practice.  The following encoding records
both the editorial and lexical views:
 
<eg><![CDATA[<sense n='1'>
  <def id=D1 opt=y next=d2>picture drawn with</def>
  <def id=D2 prev=d1>coloured chalk made into crayons</def>
</sense>]]></eg>
 </p><p>A more complex example is the following, in which the optional
element contains additional tags:
 
<q rend="display"><hilited rend="bold">canary</hilited> ...(Geog) Canary Isles, Canaries (&icirc;les fpl) Canaries
fpl...  [C/R]</q>
 
<eg><![CDATA[<re type=cmpd>
  <usg type=dom>Geog</usg>
  <form>
    <orth>Canary Isles</orth>
    <orth>Canaries</orth>
  </form>
  <trans id=T1 opt=y next=t2>
    <tr>&icirc;les</tr>
    <gen>f</gen>
    <number>pl</number>
  </trans>
  <trans id=T2 prev=t1>
    <tr>Canaries</tr>
    <gen>f</gen>
    <number>pl</number>
  </trans>
</re>]]></eg>
 </p></div4><div4 name="Section" ref="Y"><head>Recording Original Locations of Transposed Elements</head><p>The attributes described in the previous section are useful
only when the order of material is the same in both the editorial and
the lexical view.  When the two views impose different orders on the
data, the SGML ID/IDREF mechanism may be used to show the original
location of material transposed in an encoding of the lexical view.
 </p><p>If the original is only slightly modified, the <gi tei="yes">anchor</gi>
element may be used to mark the original location of the material, and
the <att tei="yes">location</att> attribute may be used on the lexical encoding of
that material to indicate its original location(s).  Like those in the
preceding section, this attribute is defined for the attribute class
<ident tei="yes" type="class">dictionaries</ident>:
 
<adList classDoc="DIGLOBAL" atts="opt"/>
 </p><p>For example:
 
<q rend="display"> <hilited rend="bold">pinna</hilited>
<code tei="yes" type="frag">("pIn@)</code> n., pl. -nae (-ni:) or -nas. [CED] </q>
 
<eg><![CDATA[<form>
  <orth>pinna</orth>
  <pron>'pIn@</pron>
  <anchor id=P1>
  <form type=infl>
    <number>pl</number>
    <form>
      <orth extent=part>-nae</orth>
      <pron extent=part>-ni:</pron>
    </form>
    <orth extent=part>-nas</orth>
  </form>
</form>
<gramGrp>
  <pos location=p1>n</pos>         <!-- moved -->
</gramGrp>]]></eg>
 <!-- < p > If the modifications are more drastic (for         --><!-- example, involving several elements), use the  < gi >    --><!-- var < /gi >  and  < gi > rdg < /gi >  tags (see          --><!-- section ???  in Guidelines) to span the duplicated       --><!-- section in the original:                                 --><!--                                                          --><!-- < note place=inline > [ Is this still valid in P2?       --><!-- -JV, NI] < /note >                                       --><!-- no. -msm                                                 -->
 <!-- <eg> <![ CDATA [ clem (klEm) or clam vb. clems,          --><!-- clemming, clemmed or clams, clammimg, clammed ...        --><!-- [CED] ]]> </eg>                                          -->
 <!-- <p>Textual view:                                         -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <entry>                                                  --><!--                                                          --><!-- <var>                                                    --><!--                                                          --><!-- <rdg view=editorial>                                     --><!-- <form>                                                   --><!--   <orth>clem</orth>                                      --><!--   <pron>klEm</pron>                                      --><!-- </form>                                                  --><!-- <form>                                                   --><!--     <orth id=O1>clam</orth>                              --><!-- </form>                                                  --><!-- </form>                                                  --><!-- <gramGrp>                                                --><!--   <pos id=G1>vb</pos>                                    --><!-- </gramGrp>                                               --><!-- <form>                                                   --><!--   <form type=infl>                                       --><!--     <pers value='3'></pers>                              --><!--     <num value='sing'></num>                             --><!--     <tns value='pres'></tns>                             --><!--     <orth>clems</orth>                                   --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <tns value='prsp'></tns>                             --><!--     <orth>clemming</orth>                                --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <tns value='pst,pstp'></tns>                         --><!--     <orth>clemmed</orth>                                 --><!--   </form>                                                --><!-- </form>                                                  --><!-- <form>                                                   --><!--   <form type=infl>                                       --><!--     <pers value='3'></pers>                              --><!--     <num value='sing'></num>                             --><!--     <tns value='pres'></tns>                             --><!--     <orth>clams</orth>                                   --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <tns value='prsp'></tns>                             --><!--     <orth>clamming</orth>                                --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <tns value='pst,pstp'></tns>                         --><!--     <orth>clammed</orth>                                 --><!--   </form>                                                --><!-- </form>                                                  --><!-- </rdg>                                                   --><!--                                                          --><!-- <rdg view=lexical>                                       --><!-- <form>                                                   --><!--   <form>                                                 --><!--     <orth>clem</orth>                                    --><!--     <pron>klEm</pron>                                    --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <pers>3</pers>                                       --><!--     <num>sing</num>                                      --><!--     <tns>pres</tns>                                      --><!--     <orth>clems</orth>                                   --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <tns>prsp</tns>                                      --><!--     <orth>clemming</orth>                                --><!--   </form>                                                --><!--   <form type=infl>                                       --><!--     <tns>pst</tns>                                       --><!--     <tns>pstp</tns>                                      --><!--     <orth>clemmed</orth>                                 --><!--   </form>                                                --><!-- </form>                                                  --><!-- <form>                                                   --><!--   <form>                                                 --><!--     <orth location=o1>clam</orth>  <! - moved - >        --><!--     <form type=infl>                                     --><!--       <pers>3</pers>                                     --><!--       <num>sing</num>                                    --><!--       <tns>pres</tns>                                    --><!--       <orth>clams</orth>                                 --><!--     </form>                                              --><!--     <form type=infl>                                     --><!--       <tns>prsp</tns>                                    --><!--       <orth>clamming</orth>                              --><!--     </form>                                              --><!--     <form type=infl>                                     --><!--       <tns>pst</tns>                                     --><!--       <tns>pstp</tns>                                    --><!--       <orth>clammed</orth>                               --><!--     </form>                                              --><!--   </form>                                                --><!-- </form>                                                  --><!-- <gramGrp>                                                --><!--    <pos location=g1>vb</pos>       <! - moved - >        --><!-- </gramGrp>                                               --><!-- </rdg>                                                   --><!--                                                          --><!-- </var>                                                   --><!--                                                          --><!-- <! - rest of the entry  ->                               --><!--                                                          --><!-- </entry>                                                 --><!--                                                          --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 </p></div4></div3><div3 name="subsection" ref="Y"><head>Attributes for Dictionary Elements</head><p>The attributes provided for all dictionary-specific elements
and documented in
this section are defined thus:
 
<dtdFrag id="DEDIMV" n="Attributes for dictionary work"><claDecl classDoc="DIGLOBAL" type="atts"/></dtdFrag>
 <?tei:EOF p2dimv.odd ??>
<?tei:SOF p2difr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2difr.odd,v $
    * Revision 1.9  1998/02/05 17:14:35  tei
    * correct EG rend type
    *
    * Revision 1.8  1998/01/31 18:50:07  tei
    * fix eg
    *
    * Revision 1.6  94/03/27  16:29:41  lou
    * *** empty log message ***
    * 
    * Revision 1.5  1994/03/07  15:19:03  lou
    * fix ^Z
    * 
    * Revision 1.4  1994/03/07  14:44:05  lou
    * apply typos etc. noted by DTB et al.
    * 
    * Revision 1.3  1994/01/15  20:45:31  msmcq
    * cmsmcq revision for P3
    * see comments for details
    * 
    * Revision 1.2  1994/01/04  19:38:25  msmcq
    * first cut at DI revisions
    * --><!-- Revisions:                                               --><!-- 94-01-15 : MSM : add para introducing dtdfrag., change comment --><!-- 94-01-14 : MSM : mentioned, not cited                    --><!-- 94-01-14 : MSM : note that the oald example is not TEI   --><!-- 94-01-12 : MSM : change examples to use entryFree        --><!-- 94-01-12 : MSM : correct typo                            --><!-- 94-01-11 : MSM : revise                                  --><!-- 94-01-11 : MSM : rename gram as gramGrp as per Eynsham   --><!-- 94-01-09 : MSM : add a dtdFrag                           --><!-- 93-10-19 : MSM : Added RCS id                            --><!-- 93-04-12 : MSM : delete N att on divs                    -->
 </p></div3></div2><div2 id="DIFR" name="subsection" ref="Y"><head>Unstructured Entries</head><p>The content model for the <gi tei="yes">entry</gi> element provides an entry
structure suitable for many average dictionaries, as well as many
regular entries in more exotic dictionaries.  However, the structure of
some dictionaries does not allow the restrictions imposed by the content
model for <gi tei="yes">entry</gi>.  To handle these cases, the <gi tei="yes">entryFree</gi>
element is defined, which allows for much wider variation in entry
structure.  Its content model places no constraints at all upon the
entry:  any element defined in this chapter, as well as all the
phrase-level and inter-level elements defined in the core tag set, can
appear anywhere in an entry.  With the <gi tei="yes">entryFree</gi> element, the
encoder is free to use any element anywhere, as well as to use or omit
grouping elements such as <gi tei="yes">form</gi>, <gi tei="yes">gramGrp</gi>, etc.
 </p><p>The <gi tei="yes">entryFree</gi> element allows the encoding of entries which
violate the structure specified for the <gi tei="yes">entry</gi> element.  For
example, in the following entry from a dictionary already in
electronic form, it is necessary to include a
<gi tei="yes">pron</gi> element within a <gi tei="yes">def</gi>.  This is not permitted in
the content model for <gi tei="yes">entry</gi>, but it poses no problem in the
<gi tei="yes">entryFree</gi> element.
 
<eg rend="other"><![CDATA[<ent h=demigod><hwd>demi|god</hwd><pr><ph>"demIgQd</ph></pr>
<hps ps=n>
<hsn><def>one who is partly divine and partly human</def>
<def>(in Gk myth, etc) the son of a god and a mortal woman,
eg<cf>Hercules</cf><pr><ph>"h3:kjUli:z</ph></pr></def>
</hsn></hps></ent>
 
[OALD electronic]]]></eg>
 
<eg><![CDATA[<entryFree>
  <form>
    <orth>demigod</orth>
    <hyph>demi|god</hyph>
    <pron>"demIgQd</pron>
  </form>
  <gramGrp>
    <pos>n</pos>
  </gramGrp>
  <def>one who is partly divine and partly human</def>
  <def>(in Gk myth, etc) the son of a god and a mortal woman,
       eg <mentioned>Hercules</><pron>"h3:kjUli:z</pron></def>
</entryFree>]]></eg>
 </p><p>The <gi tei="yes">entryFree</gi> element also makes it possible to transcribe a
dictionary using only phrase-level (<soCalled>atomic</soCalled>)
elements---that is, using no grouping elements at all.  This can be
desirable if the encoder wants a completely <soCalled>flat</soCalled>
view, with no indication of or commitment to the association of one
element with another.  The following encoding uses no grouping elements,
and keeps all rendition text:
 
<q rend="display"> <hilited rend="bold">biryani</hilited> or <hilited rend="bold">biriani</hilited> <code tei="yes" type="frag">(%bIrI"A:nI) </code> any of a
variety of Indian dishes...[from Urdu] [CED] </q>
 
<eg><![CDATA[<entryFree>
  <orth>biryani</orth> or
  <orth>biriani</orth>
  <pron>(%bIrI"A:nI)</pron>
  <def>any of a variety of Indian dishes...</def>
  <etym>[from <lang>Urdu</lang>]</etym>
</entryFree>
 ]]></eg>
 </p><p>The declaration of <gi tei="yes">entryFree</gi> is given above in section<xref target="DIEN"/>
.  It allows any elements defined for use within
dictionary entries to appear within it, in any order.
 
<dtdFrag id="DEDIFR" n="Model class for unstructured dictionary entries"><commDecl>This entity declares the class of elements defined
specifically for use in dictionary entries, except those which are
included in the phrase class.   This class
is used in defining the 'free'
dictionary entry.</commDecl><claDecl classDoc="DIPARTS" type="model"/></dtdFrag>





<?tei:EOF p2difr.odd ??>
</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2di.odd ??><!-- 12 Printed Dictionaries --><?tei:SOF p2te.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: p2te.odd,v $
    * Revision 1.11  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.10  98/02/01  17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    * 
    * Revision 1.9  94/04/06  10:32:44  lou
    * kill initial note; revise some titles; add rendering info
    * 
    * Revision 1.8  1994/04/01  16:39:21  msmcq
    * Changes during validation of DTD
    * 
    * Revision 1.7  1994/03/28  14:52:47  lou
    * more typos
    * 
    * Revision 1.6  1994/03/27  16:31:42  lou
    * semiofinal
    * 
    * Revision 1.3  1994/01/04  19:49:17  msmcq
    * make dtd frags produce ent file
    * 
    * Revision 1.2  1993/07/29  21:08:26  msmcq
    * add RCS id, log
    * --><!-- * start of Chapter III.7 * --><!-- TE: TEI P2 chapter for Terminology                       --><!-- Revisions:                                               --><!-- 6 apr: kill note; change titles; add rend info --><!-- 94-03-31 : MSM : protect teistr invocation               --><!-- 94-03-31 : MSM : define temix                            --><!-- 94-03-30 : MSM : four corrections / policy changes from A Melby --><!-- 19 mar: LB:  title change; JL's typos fixed --><!-- 93-10-05 : MSM : fix for DTD                             --><!-- 93-06-03 : MSM : change IDREFs to class docs             --><!-- 20 may 93 : LB : incorporate AM's post-Eynsham comments  --><!-- 92-12-23 : MSM : finish revision for publication         --><!-- 92-12-23 : MSM : rev for pub                             --><!-- 92-12-21 : MSM : eliminate flatterm, I thought I said    --><!-- 92-12-21 : MSM : extensive stylistic changes             --><!-- 92-12-18 : MSM : changes for publication                 --><!-- 92-12-17 : MSM : tag inline tags as tag                  --><!-- 92-12-17 : MSM : correct some format problems in SEW's work --><!-- 92-12-15 : SEW : edit P2X file per AI7 consensus         --><!-- 92-11-23 : MSM : correct typos in xrefs                  --><!-- 92-11-23 : MSM : correct NOTE atts, for peDecl read entDecl --><!-- 92-11-21 : MSM : reorganize, rework, add tagdocs etc     --><!-- 92-11-21 : MSM : change doctype to ODD                   --><!-- 92-11-19 : MSM : change system ids                       --><!-- 92-11-06:  WP : Made changes after seeing output.        --><!-- 92-11-05:  WP : Incorporated MSM's suggestions/cont.d    --><!-- 92-11-04 : MSM : Added comments on retagging, tag usage  --><!-- 92-11-03 : WP : made P2X file from AI7D18 TEI1 file      --><div1 id="TE" n="13" name="chapter" ref="Y"><head>Terminological Databases</head><!-- < div2 id=TENA name='section'>                           --><!-- < head>The Nature of Terminological Data< /head>         --><p>Terminological information generally resides in <term>terminology
databases</term> (<term>TDBs</term>), but for SGML applications, these
collections of data can be viewed as documents.  A document containing
terminological data is made up of <term>terminological entries</term>.
Typically, a terminological entry treats a single concept and contains
information on the assignment of single or multi-word terms to this
concept.  Bilingual and multilingual terminological entries deal with
harmonized or very closely related concepts in two or more languages
that are treated as functional equivalents in the context of a specific
domain or subdomain.  Terminological data can take the form of
terminological databases (TDBs) or can be used to print hardcopy
terminological documents, such as terminological dictionaries,
technical vocabularies, or thesauri.<!--
<note place=foot>
The primary responsibility for this chapter was borne by TEI work
group AI7 (terminological data).  The text was originally drafted
by Alan K. Melby (chair), Sue Ellen Wright, Gerhard Budin, and
Gregory Shreve; the DTD fragments were drafted by Gregory Shreve.
Further revisions were made by the above and by Richard Strehlow.
</note>
--></p><p>The TEI description of terminological data was originally designed
primarily as a <term>terminology interchange format</term>
(<term>TIF</term>) to allow users of terminology databases to exchange
database records.  In this guise it is called the <term>Electronic
Terminology Interchange Format</term> (<term>E-TIF</term>).  The
exchange of database records is especially important in practice
because the structure of terminological records varies considerably
from TDB to TDB, reflecting differences of design and of user needs.
Users of TDBs frequently need to interchange data in order to access
expert information and to prevent the duplication of effort, but
differences in software, hardware, and methodology complicate
interchange.  A universal interchange format is a crucial element in
making interchange easier.</p><p>The tag set defined in this chapter may also be used to mark up
documents for the purpose of printing <term>terminological
dictionaries</term> and <term>vocabularies</term>, or exchanging them
in electronic form.  Printed terminological documents differ from
terminological databases in that they are frequently divided into
sections and subsections and include prose text in introductions, etc.
When used for marking up printed documentation, we can speak of the tag
set defined here as a <term>Print Terminology Interchange Format</term>
(<term>P-TIF</term>).</p><p>Because printed terminological dictionaries differ from
terminological databases, problems may arise if one attempts to use the
same electronic document both for printing and to exchange records
among databases.  A printed terminological dictionary may contain
material not suitably encoded for introduction into database records.
Domain and subdomain information may be implied by the arrangement of
<gi tei="yes">termEntry</gi>s rather than by explicit domain specifications
within the individual entries.</p><p>Other interchange difficulties include differences
between term entry styles used in prescriptive and descriptive
terminology work and problems arising from differences in the degree of
detail used to classify data elements in different databases.
(The term <term>data element</term> is used by terminologists to
refer to <gloss>the smallest defined individual items of
information</gloss>, regardless of whether they are represented as
SGML elements, SGML attributes, or fields or columns in a database.
That is the usage followed here.) Procedures for addressing these
various problems are treated in more detail in another document, the
<citation><title>TEI / LISA / ISO - TIF --- Terminology Interchange
Format --- A Tutorial</title> (1993)</citation>.
<note source="auth" place="foot" anchored="Y"> This document is reprinted in <title>TermNet
News</title>, no 40, 1993, pp 5-64; copies are also available from
Infoterm, z.Hd. Herrn Dr. Gerhard Budin, Heinestra&szlig;e 38, Postfach
No. 130, A-1021 Vienna, Austria.</note></p><div2 id="TEEN" name="subsection" ref="Y"><head>The Terminological Entry</head><p>The basic unit of terminology management is the <term>terminological
entry</term>.  A terminological entry documents information pertaining
to a concept and generally speaking contains at least one
<term>term</term>.  In addition to the term, various kinds of
descriptive and administrative data are recorded concerning the term,
the concept to which it is assigned, and relationships to other terms
and concepts.  Administrative information supports the management of the
terminology database or document.
 <!-- LB revised slightly for consistency with other parts of P2 --><!-- and to avoid need to define table element for this chap only --></p><p>A sample terminological entry consists of a series of entries like
the following:
<list type="gloss"><label>subject field</label><item>appearance of materials</item><label>English term</label><item>opacity</item><label>grammatical information, part of speech, English term</label><item>noun</item><label>definition, English term</label><item>degree of obstruction to the transmission of visible light</item><label>bibliographical source, English term information</label><item>ASTM Standard E284</item><label>responsibility for English term information</label><item>ASTM Technical Committee E12</item><label>German term</label><item>Opazit&auml;t</item><label>grammatical information, part of speech, German term</label><item>noun</item><label>grammatical information, gender, German term</label><item>feminine</item><label>definition, German term</label><item>Ma&szlig; f&uuml;r die Lichtdurchsichtigkeit</item><label>bibliographical source, German term information</label><item>HFdn1983-382</item><label>responsibility, German term information</label><item>DIN Technical Committee for paper products</item><label>French term</label><item>opacit&eacute;</item><label>grammatical information, part of speech, French term</label><item>noun</item><label>grammatical information, gender, French term</label><item>feminine</item><label>definition, French term</label><item>rapport du flux lumineux incident au flux lumineux transmis ou
r&eacute;fl&eacute;chi par un noircissement photographique</item><label>bibliographical source, French term information</label><item>HJdi1986</item><label>responsibility, French term information</label><item>C.I.R.A.D.</item></list>
 <!-- here's the original table in case you disagree -->
 <!-- <table rend='LL'> --><!-- <head>Example 1:  Sample terminological entry</head> --><!-- AM notes that the heading should not be over the right column only --><!-- <r><c>subject field                <c>appearance of materials --><!-- <r><c>English term                 <c>opacity --><!-- <r><c>grammatical information, part of speech, English term <c>noun --><!-- <r><c>definition, English term --><!-- <c>degree of obstruction to the transmission of visible light --><!-- <r><c>bibliographical source, English term information --><!-- <c>ASTM Standard E284 --><!-- <r><c>responsibility for English term information --><!-- <c>ASTM Technical Committee E12 --><!-- <r><c>German term --><!-- <c>Opazit&auml;t --><!-- <r><c>grammatical information, part of speech, German term <c>noun --><!-- <r><c>grammatical information, gender, German term <c>feminine --><!-- <r><c>definition, German term --><!-- <c>Ma&szlig; f&uuml;r die Lichtdurchsichtigkeit --><!-- <r><c>bibliographical source, German term information --><!-- <c>HFdn1983-382 --><!-- <r><c>responsibility, German term information --><!-- <c>DIN Technical Committee for paper products --><!-- <r><c>French term --><!-- <c>opacit&eacute; --><!-- <r><c>grammatical information, part of speech, French term <c>noun --><!-- <r><c>grammatical information, gender, French term <c>feminine --><!-- <r><c>definition, French term --><!-- <c>rapport du flux lumineux incident au flux lumineux transmis ou --><!-- r&eacute;fl&eacute;chi par un noircissement photographique --><!-- <r><c>bibliographical source, French term information --><!-- <c>HJdi1986 --><!-- <r><c>responsibility, French term information --><!-- <c>C.I.R.A.D. --><!-- </table> --></p></div2><div2 id="TETA" name="subsection" ref="Y"><head>Tags for Terminological Data</head><p>The following sections define elements for use in tagging
terminological data.  The elements and attributes listed are based on
empirical studies.  The studies indicated the use of a wide variety of
different data element types (data categories or database field types),
but this variety can be reduced to a relatively small set of SGML
elements and attributes expressing notions common to most, if not all,
TDBs.  Those elements and attributes are defined here.  In addition,
the global TEI attributes defined in section <xref target="STGA"/>, and
the elements and attributes defined in chapter <xref target="CO"/>, can
all be used in terminological applications.</p><p>When tagging terminological data, three elements constitute the set
of <term>non-floating elements</term>:  <gi tei="yes">term</gi>,
<gi tei="yes">otherForm</gi>, and <gi tei="yes">descrip</gi>.  All other elements function
as <term>floating elements</term>, including:  <gi tei="yes">admin</gi>,
<gi tei="yes">note</gi>, <gi tei="yes">gram</gi>, <gi tei="yes">bibl</gi>, <gi tei="yes">biblFull</gi>,
<gi tei="yes">date</gi>, <gi tei="yes">table</gi>, <gi tei="yes">formula</gi>, <gi tei="yes">figure</gi>, and
the linking elements (<gi tei="yes">ptr</gi>, <gi tei="yes">xptr</gi>, <gi tei="yes">ref</gi>, and
<gi tei="yes">xref</gi>). The rules for combining floating with non-floating
elements are spelled out below in section <xref target="TENE"/>, and in
section <xref target="TEFL"/>.
 
<tagList style="one-line"><tagDesc tagDoc="TERM" atts="type"/><tagDesc tagDoc="TERMENTN" atts="type"/><tagDesc tagDoc="TIG" atts="type"/><tagDesc tagDoc="OTHFORM" atts="type"/><tagDesc tagDoc="OFIG" atts="type"/><tagDesc tagDoc="GRAM" atts="type"/><tagDesc tagDoc="DESCRIP" atts="type"/><tagDesc tagDoc="ADMIN" atts="type"/></tagList><!-- need to add reference to gramGrp here when tagdoc available --></p><p>As indicated, these elements all possess a <att tei="yes">type</att> attribute,
used to classify the generic elements so as to match the classifications
used by TDBs.  The <att tei="yes">type</att> attributes allow specific
items of information not defined in the DTD to be tagged as one of
the defined elements with an appropriate <att tei="yes">type</att> value.  The
possible values of <att tei="yes">type</att> thus constitute a sizable open list.</p><p>At the time of publication, work is under way in ISO Technical
Committee 37, Sub-Committee 3, Working Group 1 to compile an official
dictionary of data element types (data categories) for use in
terminology work, which will eventually provide the core for a complete
list of <att tei="yes">type</att> attribute values.  This data element dictionary
will appear as ISO 12 620.  The attribute values that occur in the
examples shown in this chapter represent a subset of those that will be
defined in ISO 12 620.
 <!-- <p>The <gi>ofig</gi> element will only rarely be         --><!-- needed, since detailed information about other form      --><!-- terms will typically be found in another term entry,     --><!-- either pointed to, or contained by, another              --><!-- <gi>tig</gi>.                                            --></p><p>The <gi tei="yes">ofig</gi> and <gi tei="yes">otherForm</gi> elements are not necessary
if each potential <gi tei="yes">otherForm</gi> element is recast as a term in
its own <gi tei="yes">tig</gi>.  For example, a term could be placed in a
<tag compl="full" tei="yes">tig type=synonym</tag>.</p><p>When the base tag set described in this chapter is used, the
following attributes are added to the set
of global attributes:
 
<adList classDoc="CLTERM" atts="group depend grpPtr depPtr"/>
 
For discussion of the usage of these attributes, see below,
section <xref target="TEFL"/>.</p><p>Among the TEI core elements, the following are most likely to be found
necessary in encoding terminological data; for fuller descriptions see
the appropriate sections in chapter <xref target="CO"/>. In the case of the
<gi tei="yes">date</gi> element, it should be noted that the ISO format (<code tei="yes" type="frag">YYYY-MM-DD</code>)
is preferred for terminology entries.
 
<tagList style="one-line"><tagDesc tagDoc="NOTE"/><tagDesc tagDoc="REF"/><tagDesc tagDoc="PTR"/><tagDesc tagDoc="XREF"/><tagDesc tagDoc="XPTR"/><tagDesc tagDoc="DATE"/><tagDesc tagDoc="BIBL"/><tagDesc tagDoc="BIBLSTRU"/><tagDesc tagDoc="BIBLFULL"/><tagDesc tagDoc="TABLE"/><tagDesc tagDoc="FIGURE"/><tagDesc tagDoc="FORMULA"/></tagList></p><p>Like all other elements defined in the TEI DTDs, all elements in the
base tag set for terminology possess the following global attributes:
 
<adList classDoc="GLOBAL" atts="lang n id"/></p><p>Using the tags defined here, the example given above in section<xref target="TEEN"/>
 might be tagged thus:<note source="auth" place="foot" anchored="Y">In this example, as
in the others, white space has been liberally used for the sake of
legibility; in practice most actual encodings would use less white
space.</note>
 
<eg><![CDATA[<!-- Example 2a:  Nested Term Entry -->
<termEntry>
     <admin type='domain'> appearance of materials </admin>
     <tig lang=en>
	  <term> opacity </term>
	  <gram type=pos> n </gram>
	  <descrip type='definition'> degree of obstruction to the
	  transmission of visible light </descrip>
	  <ptr type='bibliographic' target='ASTM.E284'>
	  <admin type='responsibility' resp='ASTM E12'> </admin>
     </tig>
     <tig lang=de>
	  <term> Opazit&auml;t </term>
	  <gram type=pos> n </gram>
	  <gram type=gen> f </gram>
	  <descrip type='definition'> Ma&szlig; f&uuml;r die
	  Lichtdurchsichtigkeit </descrip>
	  <ref type='bibliographic' target='HFDN1983'> p. 383 </ref>
	  <admin type='responsibility' resp='DIN TC for paper
	  products'></admin>
     </tig>
     <tig lang=fr>
	  <term> opacit&eacute; </term>
	  <gram type=pos> n </gram>
	  <gram type=gen> f </gram>
	  <descrip type='definition'> rapport du flux lumineux
	  incident au flux lumineux transmis ou r&eacute;fl&eacute;chi
	  par un noircissement photographique </descrip>
	  <ptr type='bibliographic' target='HJDI1986'>
	  <admin type='responsibility' resp='C.I.R.A.D.'> </admin>
     </tig>
</termEntry>]]></eg></p><p>Both the <tag compl="full" tei="yes">ptr type='bibliographic' target='ASTM.E284'</tag> and
<tag compl="full" tei="yes">ref type='bibliographic' target='HFDN1983'</tag> elements in the
example indicate links to complete bibliographical entries included in
the back matter element of the same document.  <cited>HFdn1983</cited>
is a source reference code for a book, generated according to ISO/TC 37
WI 18, <title>Coding of Bibliographic References in Terminology Work and
Terminography</title> (1991).  Its full bibliographic record would be:
 
<eg><![CDATA[<!-- Example 2b:  Full Bibliographic Entry -->
<biblFull>
       <titleStmt id=HFDN1983>
	      <title> W&ouml;rterbuch technischer Begriffe mit 4300
	      Definitionen nach DIN </title>
	      <editor> Henry G. Freeman </editor>
       </titleStmt>
       <editionStmt>
	      <edition> III </edition>
       </editionStmt>
       <extent> 703 pp </extent>
       <publicationStmt>
	      <publisher> Beuth Verlag GmbH </publisher>
	      <pubPlace> Berlin and K&ouml;ln </pubPlace>
	      <date> 1983 </date>
       </publicationStmt>
       <sourceDesc><p>Compiled for the standards of the DIN (Deutsches
	      Institut f&uuml;r Normung).</p>
       </sourceDesc>
</biblFull>]]></eg></p><p>Further examples, including alternate encodings of this term entry,
are given below in section <xref target="TEFL"/>, and section <xref target="TEFLNE"/>.</p><p>The formal definition of these elements depends on which style of
markup is being used; for discussion of the two styles, see the
following section, <xref target="TEBA"/>.  For the formal declarations for
the two styles, see sections <xref target="TEDTN"/>, and <xref target="TEDTF"/>.</p></div2><div2 id="TEBA" name="subsection" ref="Y"><head>Basic Structure of the Terminological Entry</head><p>A terminological entry is identified with the <gi tei="yes">termEntry</gi> tag
and contains one or more terms marked with the tag <gi tei="yes">term</gi>, which
may appear with associated SGML elements.  A single term and its
associated SGML elements (such as <gi tei="yes">gram</gi>, <gi tei="yes">descrip</gi>,
<gi tei="yes">admin</gi>) constitute a <term>term information group</term>,
<gi tei="yes">tig</gi>.  A <gi tei="yes">termEntry</gi> may be made up of one or more
<gi tei="yes">tig</gi>s.</p><p>There are two structural descriptions for <gi tei="yes">termEntry</gi>s:
<list type="bullets"><item><term>nested</term> <gi tei="yes">termEntry</gi>s</item><item><term>flat</term> <gi tei="yes">termEntry</gi>s</item></list>
The nested structure is preferred, especially for interchange with
unknown partners. The flat structure provides an option that can be
used between interchange partners whose systems exhibit fairly
similar structures. The flat structure may also be used as an intermediate
form for systems making the transition to the nested format.</p><div3 id="TENE" name="subsection" ref="Y"><head>Nested Term Entries</head><p>A nested <gi tei="yes">termEntry</gi> uses SGML to represent the hierarchical
relationships implicit in the terminological entry by utilizing the
following principles of embedding and adjacency.
<list type="bullets"><item>Rule of embedding in nested term entries:
      Elements that constitute a part of another element are embedded
      inside the parent element.</item><item>Rules of adjacency in nested term entries:
<list type="gloss"><label>N1</label><item>Any element that appears in a <gi tei="yes">termEntry</gi>
outside a <gi tei="yes">tig</gi> applies to the entire <gi tei="yes">termEntry</gi>.</item><!-- changed from 'before first TIG':  inclusion exceptions   --><!-- allow admin, note, etc. between tigs, and after the      --><!-- last tig. -MSM					      --><label>N2</label><item>Any element that appears in a <gi tei="yes">tig</gi> before the
<gi tei="yes">term</gi> element applies to the entire <gi tei="yes">tig</gi>.</item><label>N3</label><item>Any floating element that appears after a non-floating
element (i.e., after <gi tei="yes">term</gi>, <gi tei="yes">otherForm</gi> or
<gi tei="yes">descrip</gi>) and before the next non-floating element, refers to
the immediately preceding non-floating element unless otherwise
indicated using the <att tei="yes">depend</att> attribute. (See section <xref target="TEFLNE"/>, for a full discussion of the <att tei="yes">depend</att>
attribute.)</item></list></item></list>
 <!-- <p>As implied above, part-whole relationships are        --><!-- expressed by embedding parts within wholes.  Logical     --><!-- relationships such as super- and subordination, or       --><!-- thematic relationships, are represented by one of the    --><!-- rules of adjacency.                                      --></p><p>The conversion routine that creates the nested entry infers the
language of the <gi tei="yes">tig</gi> from the language of the <gi tei="yes">term</gi>, a
process that can be construed as <soCalled>upward inheritance</soCalled>
from <gi tei="yes">term</gi> to <gi tei="yes">tig</gi>.  Standard TEI <soCalled>downward
inheritance</soCalled> applies for all the elements embedded in the
<gi tei="yes">tig</gi>:  their language is that of the <gi tei="yes">tig</gi>, unless this
default value is overridden by stating a new value.</p><p>An example of a nested term entry was given in section <xref target="TETA"/>.</p></div3><div3 id="TEFL" name="subsection" ref="Y"><head>Flat Term Entries Using Rules of Adjacency</head><p>The flat terminological entry does not use the <gi tei="yes">tig</gi> element
to enclose a term and its associated elements.	Instead, it provides
other mechanisms to express the relationships that occur within and
among entries in a TDB, while at the same time allowing the different
types of entries found in different source TDBs to be represented in
very natural ways.  The difference between the nested and flat
terminological entries is that, while both can express the same
information, the nested structure represents the logical hierarchy
implicit within the entry by embedding elements in one another, while
the flat entry does not represent the logical hierarchy within the entry
in this way.  Since many existing TDBs do not overtly indicate any
hierarchical structure such as that represented in a nested entry, the
flat entry may be more apt to reflect the organization of data elements
within an entry found in the particular source TDB, whereas the nested
entry more obviously characterizes an ideal abstract structure of the
term entry.  In flat entries, terms and their associated elements are
grouped by means of the following rules of adjacency:
 
<list type="gloss"><head>Rules of adjacency in flat <gi tei="yes">termEntry</gi>s:</head><label>F1</label><item>Any element that appears in a <gi tei="yes">termEntry</gi> before
the first <gi tei="yes">term</gi> is assumed to apply to the entire
<gi tei="yes">termEntry</gi>.</item><label>F2</label><item>Any floating element that appears after a non-floating
element (i.e., after <gi tei="yes">term</gi>, <gi tei="yes">otherForm</gi> or
<gi tei="yes">descrip</gi>) and before the next non-floating element refers to
the immediately preceding non-floating element unless otherwise
indicated using the <att tei="yes">depend</att> attribute. (See section <xref target="TEFLNE"/>, for a full discussion of the <att tei="yes">depend</att>
attribute.)</item></list></p><p>Encoded using the flat style, the example given in section <xref target="TETA"/>, might look like this:
 
<eg id="TEEXFL"><![CDATA[<!-- Example 3:  Flat <termEntry>			      -->
<termEntry>
     <admin type='domain'> appearance of materials </admin>
     <term lang=en> opacity </term>
     <gram type=pos> n </gram>
     <descrip type='definition'> degree of obstruction to the
     transmission of visible light </descrip>
     <ptr type='bibliographic' target='ASTM.E284'>
     <admin type='responsibility' resp='ASTM E12'></admin>
     <term lang=de> Opazit&auml;t </term>
     <gram type=pos> n </gram>
     <gram type=gen> f </gram>
     <descrip type='definition'> Ma&szlig; f&uuml;r die
      Lichtdurchsichtigkeit
     </descrip>
     <ref type='bibliographic' target='HFDN1983'> p. 383 </ref>
     <admin type='responsibility' resp='DIN TC for paper products'>
     </admin>
     <term lang=fr> opacit&eacute; </term>
     <gram type=pos> n </gram>
     <gram type=gen> f </gram>
     <descrip type='definition'> rapport du flux lumineux
     incident au flux lumineux transmis ou r&eacute;fl&eacute;chi
     par un noircissement photographique </descrip>
     <ptr type='bibliographic' target='HJDI1986'>
     <admin type='responsibility' resp='C.I.R.A.D.'> </admin>
</termEntry>]]></eg></p></div3><div3 id="TEFLNE" name="subsection" ref="Y"><head>Flat Term Entries Using Group and Depend Attributes</head><p>In practice, there are term entries where elements are ordered in
such a way that the rules of adjacency cannot be used.	For instance, in
Example 3 the <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi> linking elements refer to the
immediately preceding <gi tei="yes">descrip</gi> information.  The <gi tei="yes">admin
type='responsibility'</gi> elements as represented here also refer to the
<gi tei="yes">descrip</gi> element. It may, however, be desirable for the
bibliographic reference to refer not only to the quoted material in the
descriptive element, but also to the term itself. Because the second
rule of adjacency dictates that all floating elements following a non-
floating element refer to that non-floating element, a mechanism is
required to <soCalled>point</soCalled> to the <gi tei="yes">term</gi> if the
floating element depends on the <gi tei="yes">term</gi> itself.</p><p>There are also other exceptions to the adjacency rules: in some term
entries elements are associated with a <gi tei="yes">term</gi> other than the
immediately preceding <gi tei="yes">term</gi>.  Such entries may be called
<term>discontiguous flat term entries</term>, since the constituents of
a term information group may not be adjacent.  In such entries,
information pertaining to the entire terminological entry may not always
appear at the beginning of the entry (i.e., prior to the introduction of
a term).</p><p>Such an entry might be encoded as follows:
 
<eg id="TEEXDI"><![CDATA[<!-- Example 4:  Discontiguous Flat <termEntry>  -->
<termEntry n=texyz>
     <term lang=en n=1> opacity </term>
     <gram type=pos depend=1> n </gram>
     <term lang=de n=2> Opazit&auml;t </term>
     <gram type=pos depend=2> n </gram>
     <gram type=gen depend=2> f </gram>
     <term lang=fr n=3> opacit&eacute; </term>
     <gram type=pos depend=3> n </gram>
     <gram type=gen depend=3> f </gram>
 
     <descrip type='definition' group=1 n=endes1> degree of
	obstruction to the transmission of visible light  </descrip>
     <descrip type='definition' group=2 n=dedes1> Ma&szlig; f&uuml;r die
	Lichtdurchsichtigkeit  </descrip>
     <descrip type='definition' group=3 n=frdes1> rapport du
	flux lumineux incident au flux lumineux transmis ou
	r&eacute;fl&eacute;chi par un noircissement photographique
	</descrip>
     <ptr type='bibliographic' depend=endes1 target='ASTM.E284'>
     <admin type='responsibility' depend=endes1 resp='ASTM E12'> </admin>
     <ref type='bibliographic' depend=dedes1 target='HFDN1983'>
	p. 383 </ref>
     <admin type='responsibility' depend=dedes1
	resp='DIN.TC.for.paper'></admin>
     <ptr depend=frdes1 type='bibliographic' target='HJDI1986'>
     <admin type='responsibility' depend=frdes1
	resp='C.I.R.A.D.'> </admin>
     <admin type='domain' depend=texyz> appearance of materials
     </admin>
</termEntry>]]></eg></p><p>In the above example, <att tei="yes">depend</att> elements indicate that the
material tagged with this attribute is related to the targeted element.
The <att tei="yes">group</att> elements indicate that the information so marked is
part of an implicit <gi tei="yes">tig</gi>, i.e. that it pertains either to the
term or to the entire implicit <gi tei="yes">tig</gi>. Items linked to other
elements by <att tei="yes">depend</att> do not require the <att tei="yes">group</att>
attribute because they are associated with the group already by virtue
of their relation to elements that are themselves associated with the
group.</p><p>So as to describe appropriate relationships in discontiguous flat
<gi tei="yes">termEntry</gi>s, it is necessary to define a pointing mechanism that
allows any non-adjacent element to be related to an implicit term
information group and therefore to the <gi tei="yes">term</gi> with which it is
associated or to some other specific element.
 <!-- LB added following para --></p><p>Two methods are provided to represent this association. For terminology
files in which unique identifiers for all <gi tei="yes">term</gi> elements cannot
be assumed (as will often be the case in interchange), the <att tei="yes">group</att>
and <att tei="yes">depend</att> attributes should be used. For terminology files in
which unique SGML identifiers can be provided, the <att tei="yes">grpPtr</att> and
<att tei="yes">depPtr</att> attributes should be used. The two pairs of attributes
have identical significance as far as the association of elements is
concerned.</p><p>The <att tei="yes">group</att> attribute associates an element with a specific
term, or with an implicit term information group:  its value must be the
same as the <att tei="yes">n</att> attribute on the <gi tei="yes">term</gi> element being
pointed to.  During interchange, the <att tei="yes">group</att> attribute would be
used to extract and assemble all the elements related to a specific term
information group from a discontiguous flat <gi tei="yes">termEntry</gi> by
matching them to the <att tei="yes">n</att> attributes on the terms.<!-- LB deleted following parenthesis as redundant --><!-- (Note:<att>id</att> values must be unique within the document, whereas --><!-- <att>n</att> values need not be unique; within the base tag set defined --><!-- in this chapter, <att>n</att> values are required to be unique only --><!-- within each individual terminological entry.  In other TEI bases, they --><!-- are not constrained at all.)  -->
The <att tei="yes">group</att> pointer accounts for
the kind of relationship represented by the principle of embeddedness
within a <gi tei="yes">tig</gi> in a nested term entry.
 
 <!-- removed footnote LB --><!--  <note place=foot>An --><!-- alternative proposal would make <att>group</att> and <att>depend</att> --><!-- take allowed values of <term>IDREF</term> or <term>IDREFS</term>, and --><!-- thus perform the linkage based on the <att>id</att> attribute, rather --><!-- than the <att>n</att> attribute, of the target element.  This alternative --><!-- is still being explored by the responsible work groups.</note> --></p><p>The <att tei="yes">depend</att> attribute associates an element with some
other specific element: its value must be the same as the <att tei="yes">n</att>
attribute on the element being pointed to.  As shown in the last line
of Example 4, the <att tei="yes">depend</att> attribute can also point to the
entire terminological entry by targeting a value of <att tei="yes">n</att>
indicated in the <gi tei="yes">termEntry</gi> element.  If for any reason the
grammatical information pertaining to a term does not follow the term
immediately, this information must be linked to the term with the
<att tei="yes">depend</att> attribute.
 <!-- LB added following para --></p><p>In terms of the extended pointer notation defined in chapter<xref target="SA"/>
, the specification <code tei="yes" type="frag">group=2</code> is synonymous with
<code tei="yes" type="frag">HERE ANCESTOR  (1 TERMENTRY) DESCENDANT (1 TERM N 2)</code>, and the
specification <code tei="yes" type="frag">depend=3</code> is synonymous with <code tei="yes" type="frag">HERE ANCESTOR
(1 TERMENTRY) DESCENDANT (1 * N 3)</code>.</p><p>To summarize the behavior of <att tei="yes">group</att> and <att tei="yes">depend</att>,
the <att tei="yes">group</att> attribute identifies an implicit <gi tei="yes">tig</gi>,
whereas the <att tei="yes">depend</att> attribute implies relatedness. If there
is any ambiguity with respect to the rules of adjacency, one should use
<att tei="yes">depend</att>.</p><p>In Example 4, the English term <cited>opacity</cited> is identified
as <att tei="yes">n</att>=1, and all other elements associated with this
<gi tei="yes">tig</gi> are marked as <att tei="yes">group</att>=1; in German, the term and
all its associated elements are identified as <att tei="yes">n</att>=2 and
<att tei="yes">group</att>=2, respectively; in French, the term and associated
elements are marked <att tei="yes">group</att>=3.  Since the bibliographical
references are displaced from the descriptive information with which
they are associated, the descriptions are identified with
<att tei="yes">n</att>=endes1, <att tei="yes">n</att>=dedes1, and <att tei="yes">n</att>=frdes1,
respectively. The <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi> elements are then
identified with <att tei="yes">depend</att> attributes that target the
appropriate descriptions.  Even if the elements in the entry were
adjacent to each  other in the entry, this convention would be
essential if one wanted to indicate that the source applied to the
<gi tei="yes">term</gi> and hence to the entire <gi tei="yes">tig</gi>, rather than just to
the <gi tei="yes">descrip</gi> element itself.</p></div3><div3 id="TERE" name="subsection" ref="Y"><head>References between Term Entries</head><p>Terminology documents utilize a variety of cross-references between
<gi tei="yes">termEntry</gi>s, for instance to link to bibliographic entries or
between equivalents in different languages, synonyms and related terms
and concepts.  These references are usually implemented using the TEI
linking elements <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi>, together with a value of
the attribute <att tei="yes">type</att>.  If, as is the case with the reference to
ASTM E284, the total bibliographic source description is contained in
the <soCalled>target</soCalled> element of the linking element, use
<gi tei="yes">ptr</gi>.  If, on the other hand, a page number is included, this
page number must appear as the content of a linking element introduced
by the <gi tei="yes">ref</gi> element.</p><p>Examples:
<eg><![CDATA[ <ptr type='bibliographic' target='ASTM.E284'>]]></eg>
or
<eg><![CDATA[ <ref type='bibliographic' target='HFDN1983'> p. 383 </ref>]]></eg></p><p>If the full bibliographical citation is included in the
<gi tei="yes">termEntry</gi> itself, linking elements are unnecessary and the
citation can be marked using the <gi tei="yes">bibl</gi>, <gi tei="yes">biblStruct</gi>, or
<gi tei="yes">biblFull</gi> elements.  For further discussion of bibliographic
citations and references, see section <xref target="COBI"/>.</p></div3></div2><div2 id="TEDT" name="subsection" ref="Y"><head>Overall Structure of Terminological Documents</head><p>To enable the base tag set for terminology, a parameter entity
<ident tei="yes" type="pe">TEI.terminology</ident> must be declared within the
document type subset, the value of which is <code tei="yes" type="frag">INCLUDE</code>, as
further described in section <xref target="STIN"/>. A document using this
base tag set and no other additional tag sets will thus begin as
follows:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.terminology 'INCLUDE' >
 ]>]]></eg>
 
This declaration makes available all of the elements described in this
chapter, in addition to the core elements described in chapter <xref target="CO"/>. The default structure for terminological documents
is similar to that
defined by chapter <xref target="DS"/>:
within the <gi tei="yes">tei.2</gi> element they
contain a <gi tei="yes">teiHeader</gi> and a <gi tei="yes">text</gi>.  The <gi tei="yes">text</gi>
element, in turn, contains as usual a <gi tei="yes">body</gi> element, optionally
preceded by a <gi tei="yes">front</gi> and followed by a <gi tei="yes">back</gi>.  The
<gi tei="yes">body</gi> may contain a series of <gi tei="yes">termEntry</gi> elements,
which may optionally be grouped into sections tagged with the same
elements (<gi tei="yes">div</gi>, <gi tei="yes">div0</gi>, <gi tei="yes">div1</gi>, etc.) as defined in
section <xref target="DSDIV"/>.
 
<tagList style="one-line"><tagDesc tagDoc="TEXT"/><tagDesc tagDoc="BODY"/><tagDesc tagDoc="DIV"/><tagDesc tagDoc="DIV0"/><tagDesc tagDoc="DIV1"/><tagDesc tagDoc="DIV2"/><tagDesc tagDoc="DIV3"/><tagDesc tagDoc="DIV4"/><tagDesc tagDoc="DIV5"/><tagDesc tagDoc="DIV6"/><tagDesc tagDoc="DIV7"/></tagList>
 <!-- remainder of this section may need revision, but not just now --></p><p>In order to support both the flat and the nested styles of markup,
three distinct DTD fragments for terminology are provided.
<list type="bullets"><item>teiterm2</item><item>teite2n</item><item>teite2f</item></list></p><p>In file <ident tei="yes" type="file">teiterm2.dtd</ident>, the top-level elements for the
terminology base are defined, and a subordinate parameter entity,
<ident tei="yes" type="ent">termtags</ident> is defined and referred to. By
default, this entity refers to file <ident tei="yes" type="file">teite2n.dtd</ident>, which defines the DTD for nested
markup; if the flat style of markup is to be used, the document's DTD
subset should define <ident tei="yes" type="ent">termtags</ident> as referring to
the file <ident tei="yes" type="file">teite2f.dtd</ident>, as shown in the
examples in section <xref target="TEFL"/>.<!-- this is not shown in the examples anywhere in that section (LB) -->

 
<dtdFrag id="DTETOP" n="TEIterm2.DTD:  Base tag set for terminological data" file="teiterm2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>First, embed the default text structure elements.</commDecl><msection keywords="%TEI.singleBase"><entDecl entDoc="TEISTR"/><peRef n="TEI.structure.dtd"/></msection><entDecl entDoc="TERMTN"/><peRef n="termtags"/></dtdFrag><!-- <tagDecl tagDoc=TEXT>                                    --><!-- <tagDecl tagDoc=BODY>                                    --><!-- <tagDecl tagDoc=DIV>                                     --><!-- <tagDecl tagDoc=DIV0>                                    --><!-- <tagDecl tagDoc=DIV1>                                    --><!-- <tagDecl tagDoc=DIV2>                                    --><!-- <tagDecl tagDoc=DIV3>                                    --><!-- <tagDecl tagDoc=DIV4>                                    --><!-- <tagDecl tagDoc=DIV5>                                    --><!-- <tagDecl tagDoc=DIV6>                                    --><!-- <tagDecl tagDoc=DIV7>                                    --></p><p>In file <ident tei="yes" type="file">teiterm2.ent</ident>, terminology-specific
extensions to the TEI element class system are defined, including the
classes <ident tei="yes" type="class">terminology</ident>, <ident tei="yes" type="class">comp.terminology</ident>, <ident tei="yes" type="class">terminologyInclusions</ident>, and <ident tei="yes" type="class">terminologyMisc</ident>.
 
<dtdFrag id="DTEENT" n="TEIterm2.ent:  Base tag set for terminological data" file="teiterm2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><claDecl classDoc="COMPTERM" type="model"/><entDecl entDoc="SEQTE"/><entDecl entDoc="TEMIX"/><claDecl classDoc="TERMINCL" type="model"/><claDecl classDoc="TERMMISC" type="model"/><commDecl>Add attributes to the set of global attributes:</commDecl><claDecl classDoc="CLTERM" type="atts"/></dtdFrag></p><div3 id="TEDTN" name="subsection" ref="Y"><head>DTD Fragment for Nested Style</head><p>In file <ident tei="yes" type="file">teite2n.dtd</ident> the following
definitions are found, which define the elements used in the nested
markup style:
 
<dtdFrag id="DTENE" n="Elements for nested-style terminological data" file="teite2n"><commDecl>The nested structure is used for data interchange and represents a
canonical structured form for terminology entries, which differs
from the less structured forms frequently used to store data in
terminological databases.</commDecl><tagDecl tagDoc="TERMENTN"/><commDecl>Notes, descrip(s) and admin(s) are allowed in the termEntry
to provide documentation that applies to the whole entry.</commDecl><commDecl>tig='term information group'</commDecl><commDecl>ofig='otherform information group'</commDecl><tagDecl tagDoc="TIG"/><commDecl>Order is significant: term, descrip(s), ofig(s) or otherform(s)</commDecl><tagDecl tagDoc="OFIG"/><tagDecl tagDoc="OTHFORM"/><tagDecl tagDoc="DESCRIP"/><tagDecl tagDoc="ADMIN"/><commDecl>We define a.dictionaries as the empty string,
since we are not now using the tag set for
dictionaries.</commDecl><claDecl classDoc="DFTDICT" type="atts"/><tagDecl tagDoc="GRAM"/></dtdFrag></p></div3><div3 id="TEDTF" name="subsection" ref="Y"><head>DTD Fragment for Flat Style</head><p>In file <ident tei="yes" type="file">teite2f.dtd</ident> the following
definitions, which provide support for the flat markup style, are
found:
 
<dtdFrag id="DTEFL" n="Elements for flat-style terminological data" file="teite2f"><commDecl>The flat structure is used to represent a variety of terminology
documents that occur in practice and which do not follow the form
of the nested interchange
format.  The flat representation allows for a less
rigid structure, but provides a rich mechanism for reflecting
inter-element relations.</commDecl><commDecl>The declaration of termEntry enforces appearance of at least one term
element in a termEntry, which may be preceded by descrip, admin, note,
otherform, or gram.  There may be multiple notes, admins, descrips
otherforms, and grams appearing in any order.  xRef, date, biblRef
can appear in all positions in termEntry.</commDecl><tagDecl tagDoc="TERMENTF"/><tagDecl tagDoc="OTHFORM"/><tagDecl tagDoc="DESCRIP"/><tagDecl tagDoc="ADMIN"/><commDecl>We define a.dictionaries as the empty string,
since we are not now using the tag set for
dictionaries.</commDecl><claDecl classDoc="DFTDICT" type="atts"/><tagDecl tagDoc="GRAM"/></dtdFrag></p></div3></div2><div2 id="TEEG" name="subsection" ref="Y"><head>Additional Examples of Term Entries</head><p>The tag set defined in this chapter is designed to accommodate the
variety of structures that occur in TDBs; this section shows the
how the same information may be encoded in different ways, depending
on local convenience or preferences.  Example 5 gives an entry from an
ISO terminological standard.  Example 6 treats this English-French
equivalent pair as a single nested terminological entry, whereas Example
7 splits the information into two nested entries with cross-references.
Example 8 shows the same data as a flat terminological entry with
adjacent elements, whereas Example 9 groups the elements according to
element type, which requires the use of pointers in order to reconstruct
the implicit terminological information group from discontiguous
elements.</p><p>The interchange of terminological data between TDBs requires
an export routine (to E-TIF) and an import routine (from E-TIF).
For interchange between unknown partners, it may be desirable to
normalize the encoding method rather than allow all the options
presented in this section.  The effect of normalization would be that
import routines become easier to implement while export routines
become more difficult to implement.  At the time of this publication,
work is under way in ISO Technical Committee 37, Subcommittee 3,
Working Group 3 on a normalized version of E-TIF called ISO [DIS]
12 200.  Some aspects of normalization under consideration are to use
only the nested representation and avoid the use of the following
options:  divisions within the <gi tei="yes">body</gi>, the <gi tei="yes">otherForm</gi>
element, the <att tei="yes">group</att> and <att tei="yes">depend</att> attributes,
elements before the <gi tei="yes">term</gi> element in a <gi tei="yes">tig</gi>, inclusion
exceptions other than <gi tei="yes">ptr</gi> and <gi tei="yes">xptr</gi>, and paragraph
content other than <code tei="yes" type="kw">#PCDATA</code> in the elements
<gi tei="yes">admin</gi> and <gi tei="yes">gram</gi>.</p><div3 id="TEEG5" name="subsection" ref="Y"><head>Example Term Entry from ISO 472</head><!-- See hard copy to see how SEW used different fonts for    --><!-- different items within definition, below.                --><p>The following term entry is taken from ISO 472:1988, <title>Plastics
--- Vocabulary</title>, Bilingual edition (Geneva:  ISO, 1988), p. 84.
The original uses typographic characteristics to represent different
data element types within the term entry, not all of which have been
retained in the reproduction of this sample.  As prescribed by ISO
layout guidelines,<note source="auth" place="foot" anchored="Y">ISO 10241, <title>Preparation and
layout of international terminology standards</title>, 1993.</note>
the original text is printed in Helvetica, with English and French
information presented in two parallel columns; head terms appear in bold
face, notes in a smaller font size than the main text, and terms
referred to in the cross references are printed in italics.<!-- LB moved paragraphs inside item -->
<list type="gloss"><label>thermal degradation</label><item><p>The entirety of all deleterious chemical modifications of plastic
at elevated temperature.</p><p rend="small">NOTE --- It is essential to report the temperature and other
environmental conditions at which the phenomenon is studied.</p><p>See also <emph rend="it">ageing</emph>, <emph rend="it">degradation</emph> and
<emph rend="it">deterioriation</emph>.</p></item><label>d&eacute;composition thermique</label><item><p>Ensemble
de toutes les modifications chimiques nuisibles d'un plastique &agrave;
temp&eacute;rature &eacute;lev&eacute;e.</p><p rend="small">NOTE --- Il est essentiel d'indiquer la temp&eacute;rature et les
autres conditions d'environnement dans lesquelles le
ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;.</p><p>Voir aussi <emph rend="it">viellissement</emph>, <emph rend="it">d&eacute;gradation</emph>
et <emph rend="it">d&eacute;t&eacute;rioration</emph>.</p></item></list></p></div3><div3 id="TEEG6" name="subsection" ref="Y"><head>The Example Treated as a Single Term Entry in Nested Form</head><p>This treatment assumes that both the English and French terms are
treated together in the same entry. The elements grouped together at
the top of the term entry apply to the entire entry. Only the first of
the three cross-referenced terms is included in this example; it is
represented by a <gi tei="yes">ptr</gi> link which targets a term entry (related
concept) contained in the same document.  The <att tei="yes">id</att> values
used here are purely arbitrary.
 
<eg><![CDATA[<termEntry id=TE84.11>
    <admin type='domain'> plastics </admin>
    <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
    <admin type='creation' date='1988'
           resp='ISO/TC 61, Plastics'> </admin>
    <ptr type='relatedTerm' target='TE04.06'>
 
    <tig lang=en>
          <term> thermal degradation </term>
          <gram type=pos> n </gram>
          <descrip type='definition'> The entirety of all
          deleterious chemical modifications of plastic at
          elevated temperature. </descrip>
          <note> It is essential to report the temperature and
          other environmental conditions at which the phenomenon
          is studied.  </note>
     </tig>
 
     <tig lang=fr>
          <term> d&eacute;composition thermique </term>
          <gram type=pos> n </gram>
          <gram type=gen> f </gram>
          <descrip type='definition'> Ensemble de toutes les
          modifications chimiques nuisibles d'un plastique &agrave;
          temp&eacute;rature &eacute;lev&eacute;e. </descrip>
          <note> Il est essentiel d'indiquer la temp&eacute;rature et
          les autres conditions d'environnement dans lesquelles le
          ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;. </note>
     </tig>
</termEntry>
 
<!-- Referenced term entry: -->
 
<termEntry id=TE04.06>
     <tig lang=en>
          <term> ageing </term>
          <!-- ... -->
     </tig>
 
     <tig lang=fr>
          <term> vieillissement </term>
          <!-- ... -->
     </tig>
 </termEntry>]]></eg></p></div3><div3 id="TEEG7" name="subsection" ref="Y"><head>The Example Treated as Two Separate Term Entries in Nested Form</head><p>This example takes cognizance of the fact that some TDBs treat each
term in a single <gi tei="yes">termEntry</gi> instead of grouping all the
information for a single concept into a single <gi tei="yes">termEntry</gi>. The
rationale behind this approach is frequently that no two languages
truly provide harmonized concepts, although in the case of
standardized terminology it can generally be assumed that concepts
have been harmonized.  The significant difference in encoding that
occurs in this type of system is that <gi tei="yes">ptr</gi> linking elements
are required more frequently to link to term equivalents and related
terms in other entries in the same document. Since there is only one
<gi tei="yes">tig</gi> in each entry, the <gi tei="yes">ptr</gi> element could come at the
beginning, as shown in the previous example, or inside the
<gi tei="yes">tig</gi> as shown below.
 
<eg><![CDATA[<termEntry id=TE84.11.en>
 
     <admin type='domain'> plastics </admin>
     <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
     <admin type='creation' date='1988' resp='ISO/TC 61, Plastics'></admin>
 
     <tig lang=en>
          <term> thermal degradation </term>
          <gram type=pos> n </gram>
          <descrip type='definition'> The entirety of all
          deleterious chemical modifications of plastic at
          elevated temperature. </descrip>
          <note> It is essential to report the temperature and
          other environmental conditions at which the phenomenon
          is studied.  </note>
          <ptr type='relatedTerm' target='TE04.06.en'>
          <ptr type='equivalent' lang=fr target='TE84.11.fr'>
     </tig>
 
</termEntry>
 
<termEntry id=TE84.11.fr>
 
      <admin type='domain'> plastics </admin>
      <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
      <admin type='creation' date='1988'
             resp='ISO/TC 61, Plastics'> </admin>
 
     <tig lang=fr>
          <term> d&eacute;composition thermique </term>
          <gram type=pos> n </gram>
          <gram type=gen> f </gram>
          <descrip type='definition'> Ensemble de toutes les
          modifications chimiques nuisibles d'un plastique &agrave;
          temp&eacute;rature &eacute;lev&eacute;e. </descrip>
          <note> Il est essentiel d'indiquer la temp&eacute;rature et
          les autres conditions d'environnement dans lesquelles le
          ph&eacute;nom&grave;ne est &eacute;tudi&eacute;. </note>
          <ptr type='relatedTerm' target='TE04.06.fr'>
          <ptr type='equivalent' lang=en target='TE84.11.en'>
 
     </tig>
 
</termEntry>
 
<!-- Referenced term entry: -->
 
<termEntry id=TE04.06.en>
     <tig lang=en>
          <term> ageing </term>
          <!-- ... -->
     </tig>
</termEntry>
 
<termEntry id=TE04.06.fr>
     <tig lang=fr>
          <term> vieillissement </term>
          <!-- ... -->
     </tig>
</termEntry>]]></eg></p></div3><div3 id="TEEG8" name="subsection" ref="Y"><head>The Example Treated as a Flat Term Entry Using Adjacency Rules</head><p>This version of Example 5 uses a flat style of encoding, following
the pattern of many existing TDBs; elements associated with a given
term follow it immediately:
 
<eg><![CDATA[<termEntry id=TE84.11>
     <admin type='domain'> plastics </admin>
     <ref type='bibliographic' target='ISO.472-1988'> p. 84 </ref>
     <admin type='creation' date='1988'
            resp='ISO/TC 61, Plastics'> </admin>
     <term lang=en> thermal degradation </term>
     <gram type=pos> n </gram>
     <descrip type='definition'> The entirety of all deleterious
     chemical modifications of plastic at elevated temperature.
     </descrip>
     <note> It is essential to report the temperature and other
     environmental conditions at which the phenomenon is studied.
     </note>
     <term lang=fr> d&eacute;composition thermique </term>
     <gram type=pos> n </gram>
     <gram type=gen> f </gram>
     <descrip type='definition'> Ensemble de toutes les
     modifications chimiques nuisibles d'un plastique &agrave;
     temp&eacute;rature &eacute;lev&eacute;e. </descrip>
     <note> Il est essentiel d'indiquer la temp&eacute;rature et les
     autres conditions d'environnement dans lesquelles le
     ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;. </note>
     <ptr type='relatedTerm' target='TE04.06'>
</termEntry>
 
<!-- Referenced term entry: -->
 
<termEntry id=TE04.06>
     <term lang=en> ageing </term>
     <!-- ... -->
     <term lang=fr> vieillissement </term>
     <!-- ... -->
</termEntry>]]></eg></p></div3><div3 id="TEEG9" name="subsection" ref="Y"><head>The Example Treated as a Flat Term Entry Not Using Adjacency Rules</head><p>Many translation-oriented terminologists who work with half-screen
popup windows
prefer the following layout because it enables them to see the
various <gi tei="yes">term</gi> options at the top part of their display window
without having to scroll into the body of the <gi tei="yes">termEntry</gi>. Note
in this case that the <gi tei="yes">ref</gi> element links the bibliographic
information to the entire entry.
 
<eg><![CDATA[<termEntry id=TE84.11 n=te84.11>
     <term lang=en n=1> thermal degradation </term>
     <gram type=pos depend=1> n </gram>
     <term lang=fr n=2> d&eacute;composition thermique
     </term>
     <gram type=pos depend=2> n </gram>
     <gram type=gen depend=2> f </gram>
 
     <descrip type='definition' group=1> The entirety of all
     deleterious chemical modifications of plastic at elevated
     temperature. </descrip>
     <descrip type='definition' group=2> Ensemble de toutes les
     modifications chimiques nuisibles d'un plastique &agrave;
     temp&eacute;rature &eacute;lev&eacute;e. </descrip>
     <note group=1> It is essential to report the temperature and
     other environmental conditions at which the phenomenon is
     studied. </note>
     <note group=2> Il est essentiel d'indiquer la temp&eacute;rature et
     les autres conditions d'environnement dans lesquelles le
     ph&eacute;nom&egrave;ne est &eacute;tudi&eacute;. </note>
 
     <ptr type='relatedConcept' target='TE04.06'>
     <admin depend=te84.11 type='domain'> plastics </admin>
     <ref type='bibliographic' depend=te84.11 target='ISO.472-1988'>
     p. 84 </ref>
     <admin depend=te84.11 type='creation' date='1988'
     resp='ISO/TC 61, Plastics'>
     </admin>
</termEntry>
 
<!-- Referenced term entry: -->
<termEntry id=TE04.06 n=te04.06>
     <term lang=en n=1> ageing </term>
     <!-- ... -->
     <term lang=fr n=2> vieillissement </term>
     <!-- ... -->
</termEntry>]]></eg></p></div3></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2te.odd ??><!-- 13 Terminological Data --><!-- &p2.cb;             Combined Bases --></div0><div0 n="4" name="Part" ref="Y"><head>Additional Tag Sets</head><?tei:SOF p2sa.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sa.odd,v $
    * Revision 1.11  1998/02/01 16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    *
    * Revision 1.10  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.9  1994/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.8  1994/03/21  14:12:10  lou
    * second mass typo clearup
    * 
    * Revision 1.5  1994/02/12  10:22:43  lou
    * *** empty log message ***
    * 
    * Revision 1.3  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 7 jan 98 : LB : tag xref to sasymp properly --><!-- 1-7 feb: several not so minor changes in wording; add  --><!--         declaration for pointer and pointerGroup   classes --><!-- 19 dec 93 : LB change name of classdoc ANA -> cllink --><!-- 93-09-15 : MSM : merge TL changes of 23 July             --><!-- 93-09-15 : MSM : restore refs to subsections             --><!-- 93-09-15 : MSM : process TDL's changes                   --><!-- 93-07-23 : DTL : order of sections: SA, SApt, SAxr, SAse, --><!--                   SAcs, SAsy, SAie, SAag, SAat, SAan     --><!-- 93-07-15 : DTL : rearrange sections, putting correspondence --><!--                  and synchronization sections right after --><!--                  segment section                         --><!--                  restate definition of alignment         --><!--                  further editing                         --><!-- 93-07-12 : DTL : clarification of global attributes and  --><!--                  tags defined in this chapter            --><!-- 93-07-09 : DTL : yet another title possibility: "Links,  --><!--                  Segments, Correspondences and Alignments" --><!--                  editorial cleanup; put discussion of    --><!--                  correspondence and alignment in same    --><!--                  section                                 --><!-- 93-07-08 : DTL : another title possibility: "Links,      --><!--                  Segments, Alignments and Correspondences" --><!-- 93-07-07 : DTL : change title to "Linkage, Segmentation, --><!--                  Alignment and Correspondence"           --><!--                  elaborate contents of chapter           --><!-- 93-02-10 : MSM : new id for dtdfrag dSA                  --><!-- 93-01-26 : MSM : add resp note                           --><!-- 93-01-26 : MSM : rename dtd file TEIsa2                  --><!-- 93-01-26 : MSM : add entrefs to subsections              --><!--                  correct entity decls in sample invocatn --><!-- 93-01-12 : MSM : stylistic changes for publication       --><!-- 92-12-23 : MSM : strip header                            --><!-- Date: Wed, 23 Dec 1992 14:19:10 +0000                    --><!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- Subject: sa.odd (1 of 9)                                 --><!-- 14 dec 92: LB started draft: defined link, linkGrp tags  --><div1 id="SA" n="14" name="chapter" ref="Y"><head>Linking, Segmentation, and Alignment</head><p>This chapter discusses a number of ways in which encoders may
represent analyses of the structure of a text which are not necessarily
linear or hierarchic.  In this chapter, tag sets and global attributes
are provided for the following common requirements:
 <!-- <note place=foot>The primary responsibility for this     --><!-- chapter was borne by TEI work groups TR3 (hypertext and  --><!-- hypermedia) and AI (analysis and interpretation).  The   --><!-- text was drafted in part by Steven J. DeRose and in      --><!-- part by D. Terence Langendoen.</note>                    -->
 
<list type="bullets"><item>to <emph>link</emph> disparate elements in a single document using
the <att tei="yes">id</att> attribute (section <xref target="SAPT"/>);</item><item>to link disparate elements in a single document without using the
<att tei="yes">id</att> attribute or to link elements in different documents
(section <xref target="SAXR"/>);</item><item>to <emph>segment</emph> text into elements convenient for the
encoder and to mark arbitrary points within documents (section <xref target="SASE"/>);</item><item>to represent <term>correspondence</term> or <term>alignment</term>
among groups of text elements, both those with content and those which
are empty (section <xref target="SACS"/>);<note source="auth" place="display" anchored="Y">We use the term alignment
as a special case of the more general notion of correspondence.  Let A
stand for an element with the attribute <att tei="yes">id=A</att>, and suppose
elements A1, A2 and A3 occur in that order and form one group, while
elements B1, B2 and B3 occur in that order and form another group.  Then
a relation in which A1 corresponds to B1, A2 corresponds to B2 and A3
corresponds to B3 is an alignment.  On the other hand, a relation in
which A1 corresponds to B2, B1 to C2, and C1 to A2 is not an
alignment.</note></item><item>to <term rend="noindex">synchronize</term> elements of a text, that
is to represent temporal correspondences and alignments among text
elements (section <xref target="SASY"/>) and also to align them with
specific points in time (section <xref target="SASYMP"/>);</item><item>to specify that one text element is <emph>identical</emph> to or a
<emph>copy</emph> of another (section <xref target="SAIE"/>);</item><item>to <emph>aggregate</emph> possibly noncontinguous elements
(section <xref target="SAAG"/>);</item><item>to specify that different elements are <emph>alternatives</emph>
to one another and to express <emph>preferences</emph> among the
alternatives (section <xref target="SAAT"/>);</item><item>to associate segments of a text with interpretations or analyses
of their significance (section <xref target="SAAN"/>).</item></list></p><p>These facilities all use the same basic set of techniques, which
depend on the ability to point to an element which has some form of
identifier.  The most convenient such identifier, and that which is
recommended by these Guidelines wherever possible, is provided by the
global <att tei="yes">id</att> attribute, as defined in section <xref target="STGA"/>.  An extension to this mechanism is provided, for elements
which are located in different SGML documents, or to which identifiers
cannot be attached (perhaps because they are held on read-only media),
known as the <term>TEI extended pointer mechanism</term> in section<xref target="SAXR"/>
.  For many of the topics discussed in this chapter, a
choice of methods of encoding is offered, ranging from simple but less
general ones, which use attribute values only, to more elaborate and
more general ones, which use specialized elements.</p><p>The following DTD fragments show the overall organization of the
additional tag set discussed in the remainder of this chapter.  The file
<ident tei="yes" type="file">teilink2.ent</ident> begins by declaring a set of
additional attributes available globally when this tag set is enabled.
This is followed by declarations for the attribute classes <ident tei="yes" type="class">pointer</ident> and <ident tei="yes" type="class">pointerGroup</ident> to
which most of the elements discussed in this chapter belong; these
attributes are all further described in the remainder of the chapter.
 
<dtdFrag id="DSAENTS" n="Global attributes for the TEI.linking tag set" file="teilink2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>When tag set TEI.linking is used, the following attributes
may be attached to any element:</commDecl><claDecl classDoc="CLLINK" type="atts"/><commDecl>The following attributes apply to all pointer
elements:</commDecl><claDecl classDoc="POINTER" type="atts"/><commDecl>The following attributes apply to all pointer group
elements:</commDecl><claDecl classDoc="PTRGROUP" type="atts"/></dtdFrag>
 <!-- These are the following:                                 --><!-- corresp  (SAcs)                                          --><!-- synch    (SAsy)                                          --><!-- sameAs   (SAie)                                          --><!-- copyOf   (SAie)                                          --><!-- next     (SAag)                                          --><!-- prev     (SAag)                                          --><!-- exclude  (SAat)                                          --><!-- select   (SAat)                                          --></p><p>The element declarations for this tag set are contained in the file
<ident tei="yes" type="file">teilink2.dtd</ident>:
 
<dtdFrag id="DSA" n="Linking, Segmentation and Alignment" file="teilink2.dtd"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><dtdRef dtdFrag="DSAPT"/><dtdRef dtdFrag="DSAXR"/><dtdRef dtdFrag="DSASA"/><dtdRef dtdFrag="DSASYMP"/><dtdRef dtdFrag="DSAAG"/><dtdRef dtdFrag="DSAAT"/></dtdFrag></p><p>This tag set is made available by the mechanisms described in section<xref target="STIN"/>
; this implies that the document type subset for a
document using any of the tags or attributes described in this chapter
must define a parameter entity <ident tei="yes" type="pe">TEI.linking</ident> with
the value <code tei="yes" type="kw">INCLUDE</code>.  For example, a document using
this additional tag set and the prose base would begin with a series of
declarations like the following:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY % TEI.prose   'INCLUDE'>
    <!ENTITY % TEI.linking 'INCLUDE' >
 ]>]]></eg></p><?tei:SOF p2sapt.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sapt.odd,v $
    * Revision 1.10  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.9  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.8  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.7  1994/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.6  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.5  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.3  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 94-04-08 : MSM : linkGrp has no TYPE att, but inherits it from POINTER --><!-- 94-04-08 : MSM : change tagdesc and add adlist to show this\ --><!-- 94-04-08 : MSM : .                                       --><!-- 94-03-26 : MSM : typos from HG, DB, SJ                   --><!-- 94-03-26 : MSM : disambiguate TERM, Q (code, ident ...)  --><!-- 4 feb 94 : LB tidied up structure; reverted some changes --><!-- 20 dec 93: LB: changed grouper to ptrgroup --><!-- 93-09-15 : MSM : minor SGML cleanup                      --><!-- 93-07-21 : DTL : add discussion of < ptr> within < linkGrp> --><!--                   in SAptip (per Eynsham suggestion)     --><!--                  change argTypes= to targFunc=           --><!-- 93-07-16 : DTL : use the term "connected" rather than    --><!--                   "linked" to describe the result of     --><!--                   pointing, to avoid confusion between   --><!--                   two senses of "link" noted by LB       --><!--                  make other small corrections and changes --><!-- 93-07-12 : DTL : create grouper class, query editors on  --><!--                   a vexing question                      --><!-- 93-07-08 : DTL : describe < linkGrp> attributes, correct --><!--                   typo in first < linkGrp> example       --><!--                  add targOrder= to first < link> example --><!-- 93-07-07 : DTL : elaborate < linkGrp> definition         --><!--                  clarify distinction between "pointing"  --><!--                   and "pointer"; similarly between       --><!--                   "linking" and "link".                  --><!--                  make numerous other revisions           --><!--                  "Multi-headed" renamed "Intermediate",  --><!--                  rename section and make into a div3     --><!--                  modify tagging of Pope examples         --><!-- 93-01-26 : MSM : last chance revisions                   --><!-- 93-01-22 : MSM : once more lightly                       --><!-- 93-01-18 : MSM : rev more thoroughly                     --><!-- 93-01-12 : MSM : revise for publication                  --><!-- 92-12-23 : MSM : strip header                            --><!-- Date: Wed, 23 Dec 1992 14:25:19 +0000                    --><!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- Subject: sapt.odd (4 of 9)                               --><!-- 21 Dec 92: some changes in wording following comments from SR & MSM --><div2 id="SAPT" name="subsection" ref="Y"><head>Pointers</head><p>We say that one element <term rend="noindex">points</term> to others if
the first has an attribute whose value is a reference to the others:
such an element is called a <term>pointer element</term>, or simply a
<term>pointer</term>.  Among the pointers that have been introduced up
to this point in these Guidelines are <gi tei="yes">note</gi>, <gi tei="yes">ref</gi> and
<gi tei="yes">ptr</gi>.  These elements all indicate an association between one
place in the document (the location of the pointer itself) and one or
more others (the elements whose identifiers are specified by the
pointer's <att tei="yes">target</att> attribute).  This element set defines a
variation on this basic kind of pointer, known as a <term>link</term>
which specifies both <soCalled>ends</soCalled> of an association.  In
addition, we define a syntax for representing locations in a document by
a variety of means not dependent on the use of SGML identifiers.
 </p><div3 id="SAPTL" name="subsection" ref="Y"><head>Pointers and Links</head><p>In section <xref target="COXR"/> we introduced the simplest pointer
elements, <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi>.  Here we introduce additionally
the <gi tei="yes">link</gi> element, which represents an association between two
(or more) locations by specifying each location explicitly.  Its own
location is irrelevant to the intended linkage.
 
<tagList style="one-line"><tagDesc tagDoc="PTR" atts="target"/><tagDesc tagDoc="REF" atts="target"/><tagDesc tagDoc="LINK" atts="targets"/></tagList>
 
The <gi tei="yes">ptr</gi> element may be called a <soCalled>pure
pointer</soCalled>, because its primary function is simply to point.  A
pointer sets up a <term rend="noindex">connection</term> between an
element (which, in the case of a pure pointer, can be thought of simply
as a location in a document), and one or more others, known collectively
as its <term>target</term>.
 <!--Following para deleted by DTL but restored -->
 
The <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi> elements bear a <att tei="yes">target</att>
attribute (in the singular), because they point, conceptually, at a
single target, even if that target may be discontinuous in the document.
The <gi tei="yes">link</gi> element bears a <att tei="yes">targets</att> attribute, with a
plural name, because it specifies at least two targets, each of which is
a unitary object.  It may be thought of as a representing a <term>double
link</term> between the objects specified.
 </p><p>As members of the class <ident tei="yes" type="class">pointer</ident>, these
elements share a common set of attributes:
 
<adList classDoc="POINTER" atts="type resp crdate targType targOrder evaluate"/>
 <!--      Currently the pointer class is:                     --><!--      ptr       (SApt)                                    --><!--      ref       (SApt)                                    --><!--      link      (SApt)                                    --><!--      xptr      (SAxr)                                    --><!--      xref      (SAxr)                                    --><!--      join      (SAag)                                    --><!--      alt       (SAat)                                    -->
 <!-- added following clarification (LB) -->
 </p><p>The <att tei="yes">targType</att> and <att tei="yes">targOrder</att> attributes may be
used to constrain the scope of a link to certain element types.  For
example:
 
<eg><![CDATA[<link type='echo' targets='P1 P2'>]]></eg>
 
This is a complete unconstrained link, of type <code tei="yes" type="value">echo</code>.  It assumes only that there is an element with
identifier <code tei="yes" type="value">P1</code> and another with identifier <code tei="yes" type="value">P2</code> somewhere in the current document.
 
<eg><![CDATA[<link type='echo' targType='p seg note' targets='P1 P2'>]]></eg>
 
This is a slightly more constrained link of the same type.  P1 and P2
must now both identify a <gi tei="yes">p</gi>, a <gi tei="yes">seg</gi>, or a <gi tei="yes">note</gi>,
but there is no requirement as to which is which.  (This may be useful
if, as is often the case, different elements may participate in the same
kind of link.)
 
<eg><![CDATA[<link type='echo' targType='p note' targOrder=Y targets='P1 P2'>]]></eg>
 
In this variation, not only must the link targets be either <gi tei="yes">p</gi>
or <gi tei="yes">note</gi> elements, but the one with identifier <code tei="yes" type="value">P1</code> must be a <gi tei="yes">p</gi>, and that with identifier
<code tei="yes" type="value">P2</code> must be a <gi tei="yes">note</gi>.  Note that the
present Guidelines provide no direct way of saying that <code tei="yes" type="value">P1</code> may identify either a <gi tei="yes">seg</gi> or a <gi tei="yes">p</gi>
and <code tei="yes" type="value">P2</code> must identify a <gi tei="yes">note</gi>.
 </p><p>These attributes are most useful if applied to a group of links, when
additional constraints may also be specified, as further discussed in
section <xref target="SAPTLG"/> below.
 <!-- note from Terry deleted here -->
 </p><p>Double connection among elements could also be expressed by a
combination of pointer elements, for example, two <gi tei="yes">ptr</gi> elements,
or one <gi tei="yes">ptr</gi> element and one <gi tei="yes">note</gi> element.  All that is
required is that the value of the <att tei="yes">target</att> (or other pointing)
attribute of the one be the value of the <att tei="yes">id</att> attribute of the
other.  What the <gi tei="yes">link</gi> element accomplishes is the handling of
double connection by means of a single element.  Thus, in the following
encoding:
 
<eg><![CDATA[  <ptr id=P1 target=P2> .....  <ptr id=P2 target=P1>]]></eg>
 
P1 points to P2, and P2 points to P1.  This is logically equivalent to
the more compact encoding:
 
<eg><![CDATA[  <link targets='P1 P2'>]]></eg>
 </p><p>As noted above, all elements pointed to or linked by these elements
must be identifiable using the global <att tei="yes">id</att> attribute.  This
implies that they must be present in the same document, and that they
must bear unique <att tei="yes">id</att> values.  Pointing or linking to external
documents and pointing or linking where SGML identifiers are not
available is implemented by the external pointing mechanisms discussed
in section <xref target="SAXR"/>, where the <gi tei="yes">xptr</gi> and <gi tei="yes">xref</gi>
elements are discussed.  External links and links involving elements
without identifiers do not require a special element; they may be
represented using the standard <gi tei="yes">link</gi> element, but an
intermediate <gi tei="yes">xptr</gi> element must be provided within the current
document, to bear the <att tei="yes">id</att> attribute used in the target of the
link.
 </p></div3><div3 id="SAPTEG" name="subsection" ref="Y"><head>Using Pointers and Links</head><p>As an example of the use of these mechanisms which establish
connections among elements, consider the practice (common in 18th
century English verse and elsewhere) of providing footnotes citing
parallel passages from classical authors.
<figure id="POPE" rend="float fullpage"><figDesc>The figure shows the original page of Pope's
<title>Dunciad</title> which is discussed in the text.</figDesc></figure>
Such footnotes can of course simply be encoded using the <gi tei="yes">note</gi>
element (see section <xref target="CONO"/>) without a <att tei="yes">target</att>
attribute, placed adjacent to the passage to which the note refers:<note source="auth" place="foot" anchored="Y">The <att tei="yes">type</att> attribute on the note is used to classify
the notes using the typology established in the Advertisement to the
work:  <q>The <term rend="noindex">Imitations</term> of the Ancients are
added, to gratify those who either never read, or may have forgotten
them; together with some of the Parodies, and Allusions to the most
excellent of the Moderns.</q> In the source text, the text of the poem
shares the page with two sets of notes, one headed <q>Remarks</q> and
the other <q>Imitations</q>.</note>
 
<eg><![CDATA[<l>(Diff'rent our parties, but with equal grace</l>
<l>The Goddess smiles on Whig and Tory race,</l>
<note type='imitation' place=foot anchored=no>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.</l></quote>
</note>
<l>'Tis the same rope at sev'ral ends they twist,</l>
<l>To Dulness, Ridpath is as dear as Mist)</l>]]></eg><!-- Pope, Dunciad (1729) III.284 -->
 </p><p>This use of the <gi tei="yes">note</gi> element can be called <term>implicit
pointing</term> (or <term>implicit linking</term>).  It relies on the
juxtaposition of the note to the text being commented on for the
connection to be understood.  If it is felt that the mere juxtaposition
of the note to the text does not make it sufficiently clear exactly what
text segment is being commented on (for example, is it the immediately
preceding line, or the immediately preceding two lines, or what?), or if
it is decided to place the note at some distance from the text, then the
pointing or the linking must be made explicit.  We now consider various
methods for doing that.
 </p><p>First, a <gi tei="yes">ptr</gi> element might be placed at an appropriate point
within the text to link it with the annotation:
 
<eg><![CDATA[<l>(Diff'rent our parties, but with equal grace</l>
<l>The Goddess smiles on Whig and Tory race,
<ptr rend='unmarked' target=N3.284></l>
<l>'Tis the same rope at sev'ral ends they twist,</l>
<l>To Dulness, Ridpath is as dear as Mist)</l>
<!-- elsewhere in the document ... -->
<note id=N3.284 type='imitation' place=foot anchored=no>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.</l></quote>
</note>]]></eg><!-- Pope, Dunciad (1729) III.284 -->
 
The <gi tei="yes">note</gi> element has been given an arbitrary identifier (<code tei="yes" type="value">N3.284</code>) to enable it to be specified as the target of
the pointer element.  Because there is nothing in the text to signal the
existence of the annotation, the <att tei="yes">rend</att> attribute has been
given the value <code tei="yes" type="value">unmarked</code>.
 <!-- I don't understand the need for rend= here.  If there    --><!-- were a marker in the text, such as a footnote number     --><!-- or special sign, surely you wouldn't say, for example    --><!-- <ptr rend=dagger target=N3.284>. (DTL)                   --><!-- why ever not? LB -->
 </p><p>Second, the <att tei="yes">target</att> attribute of the <gi tei="yes">note</gi> element
can be used to point at its associated text, provided that an
<att tei="yes">id</att> attribute has been supplied for the associated text.
Since, in this case, the note itself contains a pointer to the place in
the text which it is annotating, this has also been encoded, using a
<gi tei="yes">ref</gi> element, which bears a <att tei="yes">target</att> attribute of its
own and contains a (slightly misquoted) extract from the text marked as
a <gi tei="yes">quote</gi> element:
 
<eg><![CDATA[<!--  ... -->
<note target=L3.284
    type='imitation' place=foot anchored=no>
    <ref target='L3.284' rend='sc'>
    Verse 283-84.
    <quote><l>&mdash;&mdash;. With equal grace
        </l><l>Our Goddess smiles on Whig and Tory race.
     </l></quote></ref>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote>
    <l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>]]></eg><!-- Pope, Dunciad (1729) III.284 -->
 <!-- SJ asks what rend='sc' means.  no action taken (msm)     --><!-- material deleted --><!-- An SGML identifier has been given to each line, for      --><!-- convenience in transcribing other commentaries, even     --><!-- though in this example the note points only at line      --><!-- L3.284.                                                  --><!-- End material deleted -->
 </p><p>Combining these two solutions gives us the following associations:
 
<list type="simple"><item>a pointer within one line indicates the note</item><item>the note indicates the line</item><item>a pointer within the note indicates the line</item></list>
 
Note that we do not have any way of pointing from the line itself to the
note:  the association is implied by containment of the pointer.  We do
not as yet have a true double link between text and note.
 <!-- deleted DTL's third example -->
 </p><p>Thirdly, therefore, we supply identifiers for both verse line and
annotation, and use a <gi tei="yes">link</gi> element to associate the two.  Note
that the <gi tei="yes">ptr</gi> element and the <att tei="yes">target</att> attribute on the
<gi tei="yes">note</gi> may now be dispensed with:
 
<eg><![CDATA[<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<l id=L3.285>'Tis the same rope at sev'ral ends they twist,</l>
<l id=L3.286>To Dulness, Ridpath is as dear as Mist)</l>
<!-- elsewhere in the document ... -->
<note id=N3.284
    type='imitation' place=foot anchored=no>
    <ref target='L3.284' rend='sc'>
    Verse 283-84.
    <quote><l>&mdash;&mdash;. With equal grace
           </l><l>Our Goddess smiles on Whig and Tory race.
    </l></quote>]</ref>
    <bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
<!-- ... and yet elsewhere in the document ... -->
<link targType='note l' targOrder=Y targets='N3.284 L3.284'>]]></eg><!-- Pope, Dunciad (1729) III.284 -->
 </p><p>The <att tei="yes">targets</att> attribute of the <gi tei="yes">link</gi> element here
bears the identifiers of the note followed by that of the verse line.
The <att tei="yes">targType</att> and <att tei="yes">targOrder</att> attributes may be used
to enable application programs to check that the identifiers in fact
pick out a <gi tei="yes">note</gi> element and an <gi tei="yes">l</gi> element and in that
order.  If <att tei="yes">targOrder</att> has the value <code tei="yes" type="value">N</code>,
then the elements indicated by the <att tei="yes">targets</att> attribute have to
be either <gi tei="yes">note</gi> or <gi tei="yes">l</gi> elements, but are otherwise
unconstrained.  If neither attribute is present, then the only
constraint is that the identifiers given must apply to some element
within the current document.
 </p><p>For completeness, we could also allocate an identifier to the
reference within the note and encode the association between it and the
verse line in the same way:
 
<eg><![CDATA[<!-- ... -->
<note id=N3.284 type='imitation' place=foot anchored=no>
    <ref id=R3.284 rend='sc'>
    <!-- ... -->
    </ref>
</note>
<!-- ... -->
<link targType='ref  l' targOrder=Y targets='R3.284 L3.284'>]]></eg><!-- Pope, Dunciad (1729) III.284 -->
 
Indeed, the two <gi tei="yes">link</gi>s could be combined into one, as follows:
 
<eg><![CDATA[<link targType='note ref l' targOrder=Y
      targets='N3.284 R3.284 L3.284'>]]></eg>
 </p></div3><div3 id="SAPTLG" name="subsection" ref="Y"><head>Groups of Links</head><!-- Material on <linkGrp> moved up from following section (DTL) --><!-- moved back! (LB) --><p>Clearly, there are many reasons for which an encoder might wish to
represent a link or association between different elements.  For some of
them, specific elements are provided in these Guidelines; some of these
are discussed elsewhere in the present chapter.  The <gi tei="yes">link</gi>
element is a general purpose element which may be used for any kind of
association.  The element <gi tei="yes">linkGrp</gi> may be used to group links of
a particular type together in a single part of the document; such a
collection may be used to represent what is sometimes referred to in the
literature of Hypertext as a <term>web</term>, a term introduced by the
Brown University FRESS project in 1969.
 
<tagList style="one-line"><tagDesc tagDoc="LINKGRP"/></tagList>
 
As a member of the class <ident tei="yes" type="class">pointerGroup</ident>, this
element shares the following attributes with other members of that
class:
 
<adList classDoc="PTRGROUP" atts="domains targFunc "/>
 <!-- extendTarg"> killed by LB --><!--      linkGrp   (SApt)                                    --><!--      joinGrp   (SAag)                                    --><!--      altGrp    (SAat)                                    -->
 
It is also a member of the <ident tei="yes" type="class">pointer</ident> class, and
therefore also carries the attributes specified in section<xref target="SAPTL"/>
 above, in particular the <att tei="yes">type</att> attribute:
 
<adList classDoc="POINTER" atts="type"/>
 </p><p>The <gi tei="yes">linkGrp</gi> element provides a convenient way of
establishing a default for the <att tei="yes">type</att> attribute on a group of
links of the same type:  by default, the <att tei="yes">type</att> attribute on a
<gi tei="yes">link</gi> element has the same value as that given for
<att tei="yes">type</att> on the enclosing <gi tei="yes">linkGrp</gi>.
 </p><p>Typical software might hide a web entirely from the user, but use it
as a source of information about links, which are displayed
independently at their referenced locations.  Alternatively, software
might provide a direct view of the link collection, along with added
functions for manipulating the collection, as by filtering, sorting, and
so on.
 <!-- <p>If many <tag>link</tag> tags are used, they may be    --><!-- grouped together within a <tag>linkGrp</tag>, and the    --><!-- attributes of that tag used to make precise how all the  --><!-- links are to be understood.                              -->
 
To continue our previous example, this text contains many other notes,
of a kind similar to the one shown above.  To avoid having to repeat the
<att tei="yes">type=imitation</att> on each <gi tei="yes">note</gi>, we may specify it once
for all on a <gi tei="yes">linkGrp</gi> element containing all links of this type.
The <att tei="yes">targType</att> and <att tei="yes">targOrder</att> attributes can also be
specified for a <gi tei="yes">linkGrp</gi> element:
 
<eg><![CDATA[<l id=L2.79>A place there is, betwixt earth, air and seas</l>
<l id=L2.80>Where from Ambrosia, Jove retires for ease.</l>
<l> ...
<l id=L2.88>Sign'd with that Ichor which from Gods distills.</l>
<l> ...
<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<l id=L3.285>'Tis the same rope at sev'ral ends they twist,</l>
<l id=L3.286>To Dulness, Ridpath is as dear as Mist)</l>
<!-- ... -->
<!-- elsewhere in the document ... -->
<note id=N2.79 place=foot anchored=no><bibl>Ovid Met. 12.</bibl>
    <quote lang=la>
        <l>Orbe locus media est, inter terrasq; fretumq;
        </l><l>C&oelig;lestesq; plagas &mdash;
    </l></quote>
</note>
<note id=N2.88 place=foot anchored=no>
    Alludes to <bibl>Homer, Iliad 5</bibl>
<!-- .... -->
</note>
<!-- ... -->
<note id=N3.284 place=foot anchored=no><bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
<!-- ... -->
<!-- yet elsewhere in the document ... -->
<linkGrp type='imitation' targType='note l' targOrder=Y>
  <link targets='N2.79 L2.79'>
  <link targets='N2.88 L2.88'>
  <!-- ... -->
  <link targets='N3.284 L3.284'>
  <!-- ... -->
</linkGrp>]]></eg>
 </p><p>Additional information for applications that use <gi tei="yes">linkGrp</gi>
elements can be provided by means of special attributes.  First, the
<att tei="yes">domains</att> attribute can be used to identify the text elements
within which the individual targets of the links are to be found.
Suppose that the text under discussion is organized into a <gi tei="yes">body</gi>
element, containing the text of the poem, and a <gi tei="yes">back</gi> element
containing the notes.  Then the <att tei="yes">domains</att> attribute can have as
its value the identifiers of the <gi tei="yes">body</gi> and the <gi tei="yes">back</gi>, to
enable an application to verify that the link targets are in fact
contained by appropriate elements, or to limit its search space:
 
<eg><![CDATA[<body id=DUNCIAD>
<!-- .... -->
<l id=L2.79>A place there is, betwixt earth, air and seas</l>
<l id=L2.80>Where from Ambrosia, Jove retires for ease.</l>
<l> ...
<l id=L2.88>Sign'd with that Ichor which from Gods distills.</l>
<l> ...
<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<l id=L3.285>'Tis the same rope at sev'ral ends they twist,</l>
<l id=L3.286>To Dulness, Ridpath is as dear as Mist)</l>
<!-- ... -->
</body>
<back>
<div type="Notes" id=DUNNOTES><head>Notes to the Dunciad</head>
<!-- ... -->
<note id=N2.79 place=foot anchored=no><bibl>Ovid Met. 12.</bibl>
    <quote lang=la><l>
        Orbe locus media est, inter terrasq; fretumq;
        </l><l>C&oelig;lestesq; plagas &mdash;
    </l></quote>
</note>
<note id=N2.88 place=foot anchored=no>
    Alludes to <bibl>Homer, Iliad 5</bibl>
<!-- .... -->
</note>
<!-- ... -->
<note id=N3.284 place=foot anchored=no><bibl>Virg. &AElig;n. 10.</bibl>
    <quote><l>Tros Rutulusve fuat; nullo discrimine habebo.
    </l><l>&mdash;&mdash; Rex Jupiter omnibus idem.
    </l></quote>
</note>
<!-- ... -->
</back>
<!-- elsewhere in the document ... -->
<linkGrp type='imitation'
         domains='dunciad dunnotes'
         targType='note l'
         targOrder=Y>
  <link targets='N2.79 L2.79'>
  <link targets='N2.88 L2.88'>
  <!-- ... -->
  <link targets='N3.284 L3.284'>
  <!-- ... -->
</linkGrp>]]></eg>
 </p><p>Note that there must be a single parent element for each
<soCalled>domain</soCalled>; if some notes are contained by a section
with identifier <code tei="yes" type="value">dunnotes</code>, and others by a
section with identifier <code tei="yes" type="value">dunimits</code>, an
intermediate pointer must be provided (as described in section <xref target="SAPTIP"/>) within the <gi tei="yes">linkGrp</gi> and its identifier used
instead.
 <!-- and where does the linkGrp go itself? -->
 </p><p>Next, the <att tei="yes">targFunc</att> attribute can be used to provide
further information about the role or function of the various targets
specified for each link in the group.
 <!-- type of link being used in that particular --><!-- gi>linkGrp</gi> tag beyond that which is provided by the --><!-- <att>type</att> and <att>targType</att> attributes.   -->
 
The value of the <att tei="yes">targFunc</att> attribute is a list of names
(formally, SGML name tokens), one for each of the targets in the link;
these names can be chosen freely by the encoder, but their significance
should be documented in the encoding declaration in the header.<note source="auth" place="display" anchored="Y">No
special element is provided for this purpose at present:  the
information should be supplied as a series of paragraphs at the end of
the <gi tei="yes">encodingDesc</gi> element described in section <xref target="HD5"/>.</note>  In the current example, we might think of the note
as containing the <term rend="noindex">source</term> of the imitation and
the verse line as containing the <term rend="noindex">goal</term> of the
imitation.  Accordingly, we can specify the <gi tei="yes">linkGrp</gi> in the
preceding example thus:
 
<eg><![CDATA[<linkGrp type='imitation'
         domains='dunciad dunnotes'
         targType='note l'
         targFunc='source goal'
         targOrder=Y>
  <link targets='N2.79 L2.79'>
  <link targets='N2.88 L2.88'>
  <!-- ... -->
  <link targets='N3.284 L3.284'>
  <!-- ... -->
</linkGrp>]]></eg>
 <!-- extendTarg attribute axed by LB pending further clarification -->
 
 <!-- <p>Finally, the <att>extendTarg</att> attribute can be used --><!-- to combine links which share one or more target --><!-- identifiers.  Suppose that more than one different verse --><!-- line may imitate the same classical source as recorded in a --><!-- single note; in particular suppose that not only line L2.79, --><!-- but also lines 2.302 and L3.154 imitate the Ovid passage --><!-- quoted in note N2.79. -->
 <!-- <note place=foot>For purposes of this illustration, --><!-- assume that the notes are not explicitly tied to the --><!-- verse lines in any way (in particular, that the notes do not --><!-- contain cross-references to the verse lines), as if the --><!-- author of the verse and the notes were challenging the --><!-- reader to discover the links between them.  The encoder in --><!-- this case may be considered to be recording the scholarship --><!-- of the critic NPR in figuring out the links between the text --><!-- and the notes.</note> -->
 <!-- <p>These can be recorded as separate links, thus: -->
 <!-- <eg><![ CDATA [ --><!-- <link resp=NPR targets='N2.79 L2.79'> --><!-- <link resp=NPR targets='N2.79 L2.302'> --><!-- <link resp=NPR targets='N2.79 L3.154'> --><!-- ]]> --><!-- </eg> -->
 <!-- <p>Alternatively, if the <att>extendTarg</att> attribute is --><!-- given the value <term>2</term>, meaning that the second --><!-- target (consisting of pointers to verse lines) can be --><!-- <term>extended</term> with additional values, then the three --><!-- <gi>link</gi> tags can be combined into one: -->
 <!-- <eg><![ CDATA [ --><!-- <linkGrp resp=NPR --><!--          type='imitation' --><!--          domains='dunciad dunnotes' --><!--          targType='note l' --><!--          targFunc='source goal' --><!--          targOrder=Y --><!--          extendTarg=2> --><!--   <link targets='N2.79 L2.79 L2.302 L3.154'> --><!--   <link targets='N2.88 L2.88'> --><!--    ... --><!--   <link targets='N3.284 L3.284'> --><!--    ... --><!-- </linkGrp> --><!-- ]]> --><!-- </eg> -->
 <!-- <p>The default value of the <att>extendTarg</att> --><!-- attribute is 0, which means that the number of targets --><!-- in each <gi>link</gi> element should exactly match the number --><!-- of arguments in the <att>domains</att>, <att>targType</att> --><!-- and <att>targFunc</att> attributes (which should also all --><!-- match each other no matter what the value of the --><!-- <att>extendTarg</att> attribute is). -->
 </p><p>The <gi tei="yes">link</gi> and <gi tei="yes">linkGrp</gi> elements are formally defined
as follows:
 
<dtdFrag id="DSAPT" n="Links"><tagDecl tagDoc="LINK"/><tagDecl tagDoc="LINKGRP"/></dtdFrag>
 </p></div3><div3 id="SAPTIP" name="subsection" ref="Y"><head>Intermediate Pointers</head><p>In the preceding examples, we have shown various ways of linking an
annotation and a single verse line.  However, the example cited in fact
requires us to encode an association between the note and a
<emph>pair</emph> of verse lines (lines 284 and 285).
 </p><p>There are a number of possible ways of correcting this error:  one
could use the <att tei="yes">target</att> and <att tei="yes">targetEnd</att> attributes of
the <gi tei="yes">note</gi> element to delimit the span to which the note applies
(see further section <xref target="CONO"/>).  Alternatively one could
create an element to encode the couplet itself and assign it an
<att tei="yes">id</att> attribute, which can then be linked to the <gi tei="yes">note</gi>
and <gi tei="yes">ref</gi> elements.  This could be done either explicitly by
means of a <gi tei="yes">lg</gi> element, as defined in section <xref target="COVE"/>, or a <gi tei="yes">seg</gi> element, as defined in section <xref target="SASE"/>, or implicitly, by means of the <gi tei="yes">join</gi> element
discussed in section <xref target="SAAG"/>.
 </p><p>A third possibility however, is to use an <soCalled>intermediate
pointer</soCalled> as follows:
 
<eg><![CDATA[<l id=L3.283>(Diff'rent our parties, but with equal grace</l>
<l id=L3.284>The Goddess smiles on Whig and Tory race,</l>
<!-- ... -->
<ptr id=L3.283284 target='L3.283 L3.284' targOrder=Y >]]></eg>
 <!-- sentence deleted by Terry but restored by LB -->
 
When the <att tei="yes">target</att> attribute of a <gi tei="yes">ptr</gi> or <gi tei="yes">ref</gi>
element specifies more than one element, the indicated elements are
always understood to be combined or aggregated in some way to produce
the object of the pointer.
 </p><p>In this example, the <att tei="yes">targOrder</att> attribute should be
specified to indicate that the order in which identifier values are
supplied in the <att tei="yes">target</att> attribute is significant.  The
<att tei="yes">id</att> attribute provides an identifier which can then be linked
to the <gi tei="yes">note</gi> and <gi tei="yes">ref</gi> elements:
 
<eg><![CDATA[<link targets='N3.284 R3.284 L3.283284'
      targType='note ref ptr' evaluate=all>]]></eg><!-- Pope, Dunciad (1729) III.284 -->
 </p><p>The <att tei="yes">evaluate=all</att> attribute value is used on the
<gi tei="yes">link</gi> element to specify that any pointer encountered as a
target of that element is itself evaluated.  If <att tei="yes">evaluate</att> had
the value <code tei="yes" type="value">none</code>, the link target would be the
pointer itself, rather than the objects it points to.
 </p><p>Where a <gi tei="yes">linkGrp</gi> element is used to group a collection of
<gi tei="yes">link</gi> elements, any intermediate pointer elements used by those
<gi tei="yes">link</gi> elements should be included within the <gi tei="yes">linkGrp</gi>.
 </p><p>Intermediate pointers of this kind are particularly important when
extended pointers (discussed in the next section) are in use.
 <!-- material deleted by Terry and not yet restored --><!-- <p>This use of<soCalled>multi-headed< /soCalled>      --><!-- pointing should be carefully distinguished from that     --><!-- used by the<att>targets< /att> attribute of the<     --><!-- gi>link< /gi> element.  As the attribute name            --><!-- suggests, in the latter case, the indicated elements     --><!-- are not simply combined together as if they were a       --><!-- single target, but associated in some respect,           --><!-- specifically, that indicated by the<att>type< /att>    --><!-- attribute.  Crucially, the intended relationship         --><!-- between every item in a list of identifiers must be      --><!-- identical.  To represent the link discussed above as     --><!-- follows would be erroneous:                              -->
 <!-- <eg >                                                   --><!-- <![ CDATA [                                             --><!-- <link type=imitation targets='N3.284 L3.283 L3.284' >   --><!-- ]] >                                                     --><!-- </eg >                                                  -->
 <!-- This is not correct, because the association between     --><!-- N3.284 and L3.284 (the note and one line of text) is     --><!-- not of the same kind as that between L3.283 and L3.284   --><!-- (the two lines of text).  A processor cannot be          --><!-- expected to process this kind of target list             --><!-- correctly.  To represent the link correctly, an          --><!-- intermediate pointer or a virtual element must be        --><!-- introduced as discussed above.                           --><!-- End material deleted -->
 <?tei:EOF p2sapt.odd ??>
<?tei:SOF p2saxr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: p2saxr.odd,v $
    * Revision 1.8  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.7  98/02/01  16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    * 
    * Revision 1.6  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.5  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.4  1994/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.3  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * --><!-- Latex Probs in this file:
  <q>#CDATA</q>
--><!-- Revisions:                                               --><!-- 18 jan 98 : LB : fix xref error from Greg Murphy --><!-- 7 jan 98 : LB : fix typos (circ in cdata) from MSM --><!-- 94-04-08 : MSM : fix a ms close problem?                 --><!-- 94-04-08 : MSM : change tagdesc for xref, xptr           --><!-- 94-04-08 : MSM : discuss doc, from, to as inherited from xpointer --><!-- 94-04-08 : MSM : (not local)                             --><!-- 94-03-27 : MSM : remove terminal semicolon from bnf (DB) --><!-- 94-03-26 : MSM : typos from HG, DB, SJ                   --><!-- 94-03-26 : MSM : disambiguate TERM, Q (into code, ident, --><!--                  etc.  Location term keywords are tagged --><!--                  as CODE TYPE=TEIKW, nonterminals of the --><!--                  grammar as IDENT TYPE=NONTERM           --><!-- 94-03-15 : MSM : change ID for FOLLOWING section (dup)   --><!-- 94-03-15 : MSM : supply TYPE on all IDENT elems          --><!-- 94-03-15 : CMSMcQ : require value for each att in a step --><!-- 12 Mar 94 : CMSMcQ : make John Lavagnino's suggested     --><!--                      changes, for canonical refs         --><!-- 3 feb 94: LB check for funny chars, minor revision of  structure --><!-- 93-06-05 : MSM : suppress dot in col 1                   --><!-- 93-01-26 : MSM : make adList point to Pointer not Loc    --><!-- 93-01-26 : MSM : changes for publication                 --><!-- 93-01-21 : MSM : revise thoroughly, add bnf, exx         --><!-- 92-12-23 : MSM : strip header                            --><!-- Date: Wed, 23 Dec 1992 14:25:57 +0000                    --><!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- Subject: saxr.odd (5 of 9)                               -->
 </p></div3></div2><div2 id="SAXR" name="subsection" ref="Y"><head>Extended Pointers</head><p>Where the object of a link or pointer element is not contained within
the current document, or where it does not bear an <att tei="yes">id</att>
attribute, it is not possible to point at it with a <gi tei="yes">ptr</gi> or
<gi tei="yes">ref</gi> element, nor to link it directly with a <gi tei="yes">link</gi>
element, because no IDREF value can be supplied for the
<att tei="yes">target</att> or <att tei="yes">targets</att> attribute of these elements.  In
such cases, the encoder must indicate the intended element indirectly by
means of the elements discussed in this section.  These elements
identify their target using a special TEI-defined extended pointer
notation, defined in section <xref target="SAXRS"/> below and designed for
compatibility with HyTime.
<note source="auth" place="display" anchored="Y">HyTime is an international standard (ISO 10744) built on SGML.
It provides facilities for representing both static and dynamic
information for processing and interchange by hypertext and multimedia
applications.  See <citation><title> ISO/IEC 10744 Information
Technology --- Hypermedia/Time-based Structuring Language
(HyTime)</title>
([Geneva]:  International Organization for Standardization,
1992)</citation>.</note><!-- For discussion of the relation between TEI proposals  --><!-- and Hytime, see chapter <xref target=OS>. --><!-- ... but not till it gets written ... --></p><div3 id="SAXR1" name="subsection" ref="Y"><head>Extended Pointer Elements</head><p>To point or refer to locations in the current or some other document
<emph>without</emph> requiring that the target bear an SGML identifier,
the following elements should be used:
 
<tagList style="one-line"><tagDesc tagDoc="XPTR"/><tagDesc tagDoc="XREF"/></tagList>
 
These elements are both members of the element class
<ident tei="yes" type="class">pointer</ident>, and therefore carry the same
attributes as other members of that class, listed above (see section<xref target="SAPTL"/>
).
 <!-- adList classDoc=POINTER
        atts="type resp crdate targType targOrder evaluate" -->
 <!-- do targType and targOrder make much sense here? -->
 
They are also members of the class <ident tei="yes" type="class">xPointer</ident>,
from which they inherit the following attributes:
 
<adList classDoc="XPOINTER" atts="doc from to"/></p><p>Unlike the pointer elements discussed in the previous section, these
elements do not specify their target by means of a <att tei="yes">target</att>
attribute.  Instead these elements use one or both of the attributes
<att tei="yes">from</att> and <att tei="yes">to</att> to delimit a portion of some document
specified by the <att tei="yes">doc</att> attribute.  In all other respects, these
elements correspond with the elements <gi tei="yes">ptr</gi> and <gi tei="yes">ref</gi>
discussed in sections <xref target="COXR"/>, and <xref target="SAPT"/>.  Note
that there is no element <gi tei="no">xlink</gi> corresponding with the
<gi tei="yes">link</gi> element; links can be made both within and between
documents using the same syntax, as further discussed below.</p><p>The values of the <att tei="yes">from</att> and <att tei="yes">to</att> attributes on the
<gi tei="yes">xptr</gi> and <gi tei="yes">xref</gi> elements indicate the point or passage
being referred to by showing how to locate it, using one or more special
keywords, as defined below in section <xref target="SAXRS"/>.  Examples are
given there.</p><p>The <gi tei="yes">xptr</gi> and <gi tei="yes">xref</gi> elements are formally defined as
follows:
 
<dtdFrag id="DSAXR" n="Extended pointers"><tagDecl tagDoc="XREF"/><tagDecl tagDoc="XPTR"/></dtdFrag></p></div3><div3 id="SAXRS" name="subsection" ref="Y"><head>Extended Pointer Syntax</head><p>As noted above, the elements <gi tei="yes">xptr</gi> and <gi tei="yes">xref</gi> are used
to represent a link between their own location (the <soCalled>link
origin</soCalled>) and some other location (the
<soCalled>destination</soCalled>), which may or may not be in the same
document.  Software supporting intra- and inter-document links (e.g.
hypertext systems) should provide access from the location of such an
element to the destination.</p><p>This section defines the allowable values for the attributes
<att tei="yes">from</att>, <att tei="yes">to</att>, and <att tei="yes">doc</att> of the <gi tei="yes">xptr</gi>
and <gi tei="yes">xref</gi> elements.</p><p>An <gi tei="yes">xptr</gi> or <gi tei="yes">xref</gi> element with <emph>no</emph>
attributes at all is, by definition, a link to the root (i.e. the
<term rend="noindex">document element</term> --- by default, this is the
<gi tei="yes">tei.2</gi> element) of the document in which it appears.</p><p>The <att tei="yes">doc</att> attribute value must be the name of an entity
declared in the SGML document type declaration.  If only the
<att tei="yes">doc</att> attribute is given a value, then by definition the
destination is the entire entity named by the <att tei="yes">doc</att> value.  A
more specific location within another entity must be specified with the
<att tei="yes">from</att> and the <att tei="yes">to</att> attributes, as described below.
 <!-- Removed requirement that FROM and TO both have values.   --><!-- Maybe wrongly.  -msm                                     --></p><p>The <att tei="yes">from</att> and the <att tei="yes">to</att> attributes indicate the
specific location pointed at, within the entity named by the
<att tei="yes">doc</att> attribute (or within the current document, if no
<att tei="yes">doc</att> value is given).  Their values are referred to below as
<term>location pointer specification</term>s.  When both attributes are
specified, the span pointed at by the element runs from the starting
point of the span indicated by <att tei="yes">from</att> to the ending point of
the string specified by <att tei="yes">to</att>.  If the latter precedes the
former in the document, then the pointer is in error and fails.  If only
the <att tei="yes">from</att> attribute is specified, the <att tei="yes">to</att> attribute
defaults to the same value; the effect is that the element as a whole
points to the span indicated by the <att tei="yes">from</att> attribute.  It is a
semantic error to specify a value for <att tei="yes">to</att> but not for
<att tei="yes">from</att>.</p><div4 id="SAXR11" name="Section" ref="Y"><head>Location Ladders</head><p>Each location pointer specification consists of a sequence of
<term>location term</term>s, each of which consists of a keyword
specifying a <term>location type</term> followed by one or more
parenthesized parameter lists, each of which specifies a <term>location
value</term> via a list of parameters.  Location types and values, and
the parameters within a location value, must be separated by white space
characters.</p><p>Using terms borrowed from <term>HyTime</term>, we say that each TEI
location term in a specification provides the <term>location
source</term> for the next, and the entire specification is equivalent
to a <term>location ladder</term>.  By specifying the entire ladder in a
single attribute value, the TEI extended pointer mechanism greatly
reduces the syntactic and processing complexity of hypertextual
pointers.</p><p>In formal terms:<note source="auth" place="foot" anchored="Y"><!-- The formal grammar specified in this section is          --><!-- reproduced as a unit in the appendix.                    -->The notation used for this formal grammar is that defined in chapter<xref target="GR"/>
.</note>
 
<eg rend="syntax"><![CDATA[ladder   ::=  locterm
         |    ladder locterm]]></eg></p></div4><div4 id="SAXR12" name="Section" ref="Y"><head>Location Terms</head><p>The keywords used in location terms are these; references to <q>the
tree</q> mean the tree representing the SGML document hierarchy.
 
<list type="gloss"><label>root</label><item>points at the root of the target document</item><label>here</label><item>points at the location of the pointer</item><label>id</label><item>points at an ID within the target document</item><label>ref</label><item>gives a <soCalled>canonical reference</soCalled> to a location in
the target document</item><label>child</label><item>indicates an element found by descending one level in the tree</item><label>descendant</label><item>indicates an element found by descending one or more levels in the
tree</item><label>ancestor</label><item>indicates an element found by ascending one or more levels in the
tree</item><label>previous</label><item>indicates an element found by traversing the older siblings of the
current location source</item><label>next</label><item>indicates an element found by traversing the younger siblings of
the current location source</item><label>preceding</label><item>indicates an element found by traversing the entire portion of the
document preceding the current location source</item><label>following</label><item>indicates an element found by traversing the entire portion of the
document which follows the current location source</item><label>pattern</label><item>specifies a regular expression to be located within the existing
location source</item><label>token</label><item>points at one or more <term rend="noindex">tokens</term> in the
character content of the location source</item><label>str</label><item>points at one or more characters in the character content of the
location source</item><label>space</label><item>points at a location using coordinates in some
(application-defined) n-dimensional space</item><label>foreign</label><item>points at a location using some non-SGML method, and gives the
name of the method</item><label>HyQ</label><item>points at a location using the HyQ query language defined by ISO
10744 (HyTime)</item><label>ditto</label><item>(in the <att tei="yes">to</att> attribute only) points at the same span as
was indicated by the <att tei="yes">from</att> attribute</item></list></p><p>In formal terms:
 
<eg rend="syntax"> <![CDATA[
locterm ::=   'ROOT'                        // default first location
         |    'HERE'                        // location of the xptr
         |    'ID' '(' NAME ')'             // only one ID allowed.
         |    'REF' '(' characters ')'      // only one ref allowed
         |    'CHILD' steps
         |    'DESCENDANT' steps
         |    'ANCESTOR' steps
         |    'PREVIOUS' steps
         |    'NEXT' steps
         |    'PRECEDING' steps
         |    'FOLLOWING' steps
         |    'PATTERN' regs                // mult patterns allowed
         |    'TOKEN' '(' range ')'
         |    'STR' '(' range ')'
         |    'SPACE' '(' NAME ')' pointpair
         |    'FOREIGN' parms
         |    'HYQ' parms
         |    'DITTO'                       // valid only in TO att.]]></eg>
 
Note that the keywords, though shown here quoted in uppercase, are not
case sensitive.</p><p>Each location term specifies a location in the target document; this
location may be a single point, more often a span of text (often the
span of a single element) within the target document.  The location
ladder as a whole is interpreted from left to right, and each location
term specifies a location relative to the location specified by the
sequence prior to that point (i.e. to its location source).  Unless
<code tei="yes" type="teikw">here</code> or <code tei="yes" type="teikw">id</code> is specified
as the first location term, the beginning location source is always
<code tei="yes" type="teikw">root</code>.  An empty location sequence thus is the
same as <code tei="yes" type="teikw">root</code> and specifies the entire
destination entity.</p><p>In general, the search for the location specified by a location term
will be conducted only within its location source (i.e. within the
location already identified by preceding location terms).  There are
however several exceptions.  The terms <code tei="yes" type="teikw">root</code>,
<code tei="yes" type="teikw">here</code>, and <code tei="yes" type="teikw">id</code> all ignore
the location source defined by any preceding terms and therefore make
sense only as the first items in the ladder.  The terms <code tei="yes" type="teikw">ancestor</code>, <code tei="yes" type="teikw">next</code>, and <code tei="yes" type="teikw">previous</code> do not ignore the location source, but select
a new span from the adjacent or enclosing portions of the text, and not
from within the location source.  Finally the location terms <code tei="yes" type="teikw">foreign</code>, <code tei="yes" type="teikw">space</code>, and <code tei="yes" type="teikw">HyQ</code> are not defined fully here; they may or may not
ignore the existing location source.</p><p>Some of the location terms make sense only in SGML documents; these
are <code tei="yes" type="teikw">id</code>, <code tei="yes" type="teikw">child</code>, <code tei="yes" type="teikw">ancestor</code>, <code tei="yes" type="teikw">descendant</code>, <code tei="yes" type="teikw">previous</code>, <code tei="yes" type="teikw">next</code>, <code tei="yes" type="teikw">preceding</code>, and <code tei="yes" type="teikw">following</code>.  The
latter six involve traversing the tree representing the SGML document
hierarchy and are most easily understood when their location source is a
single SGML element.  If the location source is not a single SGML
element, the tree-traversal keywords operate upon its beginning
end-point, its <soCalled>front end</soCalled> (in English, this will be
the leftmost point of the location source; in Arabic or Hebrew it will
be the rightmost point).  In this case <code tei="yes" type="teikw">child</code> and
<code tei="yes" type="teikw">descendant</code> have no meaning, since character data
has no descendants in the document tree; the first <code tei="yes" type="teikw">ancestor</code> of such a location source is the element
immediately containing the character data in question, and the siblings
referred to by <code tei="yes" type="teikw">next</code> and <code tei="yes" type="teikw">previous</code> are the other children of that immediately
containing element.</p><p>The details of each keyword are given below, along with definitions
of their syntax and semantics of their results.  Examples are also
provided.  It is strongly recommended that when IDs are available, they
should be used in preference to the other methods for pointing defined
here.</p><p>For all keywords, the description assumes that the target document
does in fact contain a span or element which matches the description;
otherwise, the location term has no referent and is said to
<soCalled>fail</soCalled>.  If any location term fails, the entire
pointer fails.  No backtracking or retrying is performed (and indeed for
the most part the location terms are defined as having only one matching
location, so backtracking would in most cases lead to no better result).</p></div4><div4 id="SAXR1RO" name="Section" ref="Y"><head>The ROOT Keyword</head><p>The location term <code tei="yes" type="teikw">root</code> selects the root of
the destination document tree; in SGML terms, this is the
<soCalled>document element</soCalled>.  Since it ignores any existing
location source, the <code tei="yes" type="teikw">root</code> keyword makes sense
only as the first location term in the ladder.  Since <code tei="yes" type="teikw">root</code> is assumed as the implicit first term in any
ladder, the following two location ladders have the same meaning:
 
<eg rend="syntax"> <![CDATA[
ROOT DESCENDANT (2 DIV1) ]]></eg>
<eg rend="syntax"> <![CDATA[
DESCENDANT (2 DIV1)]]></eg></p></div4><div4 id="SAXR1HE" name="Section" ref="Y"><head>The HERE Keyword</head><p>The keyword <code tei="yes" type="teikw">here</code> designates the location at
which the pointer element itself is situated; it allows extended
pointers to select items like <q>the paragraph immediately preceding the
one within which this pointer occurs</q>.  Since it ignores any existing
location source, this keyword typically makes sense only as the first
location term in a location specification.
 </p><p>To designate <q>the paragraph preceding the current one</q>, the
following location ladder could be used:
 
<eg rend="syntax">HERE ANCESTOR (1 P) PREVIOUS (1 P)</eg>
 
(See below for descriptions of the keywords <code tei="yes" type="teikw">ancestor</code> and <code tei="yes" type="teikw">previous</code>.)
 </p></div4><div4 id="SAXR1ID" name="Section" ref="Y"><head>The ID Keyword</head><p>The resulting location is the element within the destination entity
whose ID attribute has the value specified as the location value.  The
ID location type typically makes sense only as the <emph>first</emph>
location pair in a location specification, but there is no syntactic
requirement that it be so.
 </p><p>For example, the location specification
 
<eg rend="syntax">ID (a27)</eg>
 
chooses the necessarily unique element of the destination entity which
has an attribute of declared value of type ID, whose value is <code tei="yes" type="value">a27</code>.
 </p></div4><div4 id="SAXR1RE" name="Section" ref="Y"><head>The REF Keyword</head><p>The resulting location is an element which can be found by
interpreting the location value in accordance with document-specific
rules for a <term>canonical reference.</term> Such reference systems,
particularly common in documents of interest to classical and biblical
scholars, must also be defined in the TEI header, using the
<gi tei="yes">refsDecl</gi> element (see section <xref target="HD54"/>).  If more
than one element matches the canonical reference, the first one
encountered is chosen.
 <!-- If blanks or any other non-name characters are required  --><!-- within location values, the values must be quoted; use   --><!-- of blanks in canonical references is not TEI             --><!-- recommended practice.                                    --><!-- value is already enclosed in (), quotes unneeded. -msm   -->
 </p><p>For example, the location specification
 
<eg rend="syntax">REF (MT.2.1)</eg>
 
chooses the first element of the destination entity which is identified
by the canonical reference <cited>MT.2.1</cited>
 </p></div4><div4 id="SAXR1CH" name="Section" ref="Y"><head>The CHILD Keyword</head><p>The <code tei="yes" type="teikw">child</code> location type specifies an element
or span of character data in the document hierarchy using a location
value which functions as a <term rend="noindex">domain-style</term>
address.  The value is a series of parenthesized steps, separated by
white space.  Each such step represents one level of the hierarchy
within the location source.  Each step may contain one or more
parameters separated by white space and interpreted in order as follows:
 
<list type="ordered"><item>an instance indicator, which is a signed or unsigned integer or
the special value <code tei="yes" type="kw">ALL</code></item><item>optionally, an expression matching an SGML generic identifier</item><item>optionally, one or more pairs of expressions, the first matching
an SGML attribute name and the second matching an SGML attribute value</item></list>
 </p><p>In formal terms, the location value of <code tei="yes" type="teikw">child</code>
is a series of <ident tei="yes" type="nonterm">steps</ident>:
 
<eg rend="syntax"><![CDATA[steps    ::=  '(' step ')'
         |    steps '(' step ')'
 
step     ::=  instance
         |    instance element
         |    instance element avspecs
 
avspecs  ::=  attribute value
         |    avspecs attribute value
 ]]></eg>
 <!-- alternative grammar, to make last attval optional        --><!-- avspecs  ::=  attribute                                  --><!--          |    attribute value                            --><!--          |    attribute value avspecs                    --><!--          ;                                               --></p><p>Location values of the same form are also used by the keywords
<code tei="yes" type="teikw">descendant</code>, <code tei="yes" type="teikw">ancestor</code>, <code tei="yes" type="teikw">previous</code>, and <code tei="yes" type="teikw">next</code>; details of
the interpretation may vary from keyword to keyword.</p><p>If an instance indicator alone is specified, as a number <ident tei="yes" type="variable">n</ident>, it selects the <ident tei="yes" type="variable">n</ident>th child of the location source.  If the
special value <code tei="yes" type="kw">ALL</code> is given, then <emph>all</emph>
the children of the location source are selected.  If the instance
indicator is specified with following parameters, it selects all, or the
<ident tei="yes" type="variable">n</ident>th, among those children of the location
source which satisfy the other parameters.  If a negative number is
given, the <ident tei="yes" type="variable">n</ident>th child is counted from the
last child of the location source to the first.  The location source
must contain at least <ident tei="yes" type="variable">n</ident> children;<note source="auth" place="foot" anchored="Y">Strictly speaking, |n| (absolute value of n) children.</note>
if it does not, the <code tei="yes" type="teikw">child</code> term fails.</p><p>In formal terms, the first parameter of a <ident tei="yes" type="nonterm">step</ident> is an instance indicator, which in turn is
either the special value <code tei="yes" type="kw">ALL</code> or a signed integer:
 
<eg rend="syntax"><![CDATA[instance ::=  'ALL'
         |    signed
 
signed   ::=  NUMBER                        // default sign is +
         |    '+' NUMBER
         |    '-' NUMBER
 ]]></eg></p><p>If a second parameter is given, it is interpreted as an SGML generic
identifier, and only elements of the type indicated will be selected.
For example, the location specification
 
<eg rend="syntax">CHILD (3 DIV1) (4 DIV2) (29 P)</eg>
 
chooses the 29th paragraph of the fourth sub-division of the third major
division of the initial location source.  The location specification
 
<eg rend="syntax">CHILD (3 DIV1) (4 DIV2) (-2 P)</eg>
 
chooses the next-to-last paragraph of the fourth <gi tei="yes">div2</gi> of the
third <gi tei="yes">div1</gi> in the location source.</p><p>Constraint by generic identifier is strongly recommended, because it
makes links more perspicuous and more robust.  It is perspicuous because
humans typically refer to things by type:  as <q>the second section</q>,
<q>the third paragraph</q>, etc.  It is robust because it increases the
chance of detecting breakage if (due to document editing) the target
originally pointed at no longer exists.</p><p>The generic identifier may be specified as a normal SGML name, as a
(parenthesized) regular expression, or using the reserved values <code tei="yes" type="kw">#CDATA</code> or <code tei="yes" type="kw">*</code>.  Regular expressions
take the form described below; the location term
 
<eg rend="syntax">CHILD (3 (DIV[123])</eg>
 
matches the third element which has a generic identifier of <code tei="yes" type="value">div1</code>, <code tei="yes" type="value">div2</code>, or <code tei="yes" type="value">div3</code>.  If the generic identifier is specified as
<code tei="yes" type="value">*</code>, any generic identifier is matched; this means that
<q>CHILD (2 *)</q> is synonymous with <code tei="yes" type="frag">CHILD (2)</code>.
If the second parameter is <code tei="yes" type="frag">#CDATA</code>, the location
term selects only untagged sub-portions of an element having SGML mixed
content.</p><p>The location ladder
 
<eg rend="syntax">CHILD (3 #CDATA)</eg>
 
thus chooses the third span of character data directly contained by the
current location source.  If the location source is a paragraph
containing
 
<list type="ordered"><item>a sentence (A)</item><item>an embedded quotation, marked as a <gi tei="yes">q</gi></item><item>another sentence (B)</item><item>an embedded note, marked as a <gi tei="yes">note</gi></item><item>another sentence (C)</item><item>a second embedded quotation, marked as a <gi tei="yes">q</gi></item></list>
 
where the three sentences A, B, and C are character data enclosed by no
element smaller than the paragraph itself, then <code tei="yes" type="frag">CHILD (3
#CDATA)</code> selects sentence C, while <code tei="yes" type="frag">CHILD
(3)</code> selects sentence B.</p><p>If specified as a name (i.e. without parentheses), the generic
identifier is case sensitive if and only if the SGML declaration
specifies that generic identifiers are case sensitive (by default they
are not).  If specified as a regular expression, the expression given is
always case sensitive; in the usual case this means the regular
expression should be in uppercase, as in the examples here.</p><p>In formal terms the second parameter of a <ident tei="yes" type="nonterm">step</ident> is defined thus:
 <!-- <note place=foot>If regular expressions need not be      --><!-- parenthesized, then this grammar and the accompanying    --><!-- text must be changed.  Remove this note before           --><!-- publication.-MSM</note>                                  -->
 
<eg rend="syntax"><![CDATA[element  ::=  NAME
         |    '#CDATA'
         |    '*'
         |    '(' regular ')']]></eg>
 <!-- Am uncertain about definition of 'bear' in next para.    --><!-- Alternate:  just include test (a).  This allows us to    --><!-- skirt, slightly longer, the open question:  for atts     --><!-- like LANG, with well defined TEI rules for implied       --><!-- values, is the application supposed to have supplied     --><!-- them before the search is made or not?  -msm             --><!-- I prefer the alternate myself.  And have edited          --><!-- accordingly.  LB                                         -->
 <!-- <p>If a third parameter is specified, it is interpreted  --><!-- as an attribute name, and only elements bearing that     --><!-- attribute for which that attribute is defined and which  --><!-- satisfy the other constraints will be selected.  An      --><!-- element is held to <q>bear</q> an attribute if (a) the   --><!-- attribute is defined for that element type and (b) the   --><!-- value of the attribute is not <q>IMPLIED</q>.  Like the  --><!-- preceding, this parameter may be specified as <q>*</q>   --><!-- in the (unlikely) event that an attribute value          --><!-- constitutes a constraint regardless of what attribute    --><!-- name it is a value for.  The parameter may also be       --><!-- specified as a parenthesized regular expression.         --></p><p>The third and fourth parameters, if given, are interpreted as an
attribute-value pair, and only elements which match that pair in the way
described below will be selected; the fourth and fifth parameters, and
all following pairs of parameters, are interpreted in the same way.
When more than one pair is given, all must be matched.</p><p>The third, fifth, seventh, etc., parameters are interpreted, if
specified, as attribute names.  Like generic identifiers, attribute
names may be specified as <code tei="yes" type="value">*</code> in location ladders
in the (unlikely) event that an attribute value constitutes a constraint
regardless of what attribute name it is a value for.  The attribute name
parameter may also be specified as a parenthesized regular expression.</p><p>For example, the location term
 
<eg rend="syntax">CHILD (1 * TARGET *)</eg>
 
selects the first child of the location source for which the attribute
<att tei="no">target</att> has a value.  The location term
 
<eg rend="syntax">CHILD (1 * (TARGET(S?)) *)</eg>
 
will select the first child of the location source for which an
attribute called either <att tei="no">target</att> or <att tei="no">targets</att> has a value.</p><p>As with generic identifiers, attribute names are case sensitive if
and only if the SGML declaration says they are; regular expressions are
always case sensitive and should usually be uppercased, as shown here.</p><p>In formal terms, the attribute-name parameter of a tree-traversal
step is defined thus:
 
<eg rend="syntax"><![CDATA[attribute ::= NAME
         |    '*'
         |    '(' regular ')']]></eg></p><p>If a fourth, sixth, eighth, etc., parameter is specified, it is
interpreted as an attribute value, and only elements satisfying the
other constraints and also bearing an attribute of the specified name
and value will be selected.  The attribute value may be specified
exactly as in an SGML document; as a consequence, if the attribute value
to be specified contains white space characters, it must be enclosed in
quotation marks.  The attribute value may also be specified as a regular
expression, enclosed in parentheses, or using the two special values
<code tei="yes" type="kw">#IMPLIED</code> and <code tei="yes" type="kw">*</code>.</p><p>For example, the location specification
 
<eg rend="syntax">CHILD (1 * N 2) (1 * N 1)</eg>
 
chooses an element using the global <att tei="yes">n</att> attribute.  Beginning
at the location source, the first child (whatever kind of element it is)
with an <att tei="yes">n</att> attribute having the value <code tei="yes" type="value">2</code> is chosen; then that element's first direct
sub-element having the value <code tei="yes" type="value">1</code> for the same
attribute is chosen.</p><p>The location specification
 
<eg rend="syntax">CHILD (1 FS RESP ((lanc|LANC)(s|S|ashire|ASHIRE)))</eg>
 
selects the first child of the location source which is an <gi tei="yes">fs</gi>
element bearing a <att tei="no">resp</att> attribute with the value
<code tei="yes" type="value">lancs</code>, <code tei="yes" type="value">lancashire</code>, <code tei="yes" type="value">LANCS</code>, or <code tei="yes" type="value">LANCASHIRE</code> (as well
as other possible combinations which are left to the reader's
ingenuity).  If specified with quotation marks or as a regular
expression, the attribute-value parameter is case-sensitive; otherwise
not.
 <!-- how do I say 'if the att value is #IMPLIED' tho?  --></p><p>The location specification
 
<eg rend="syntax">CHILD (1 FS RESP #IMPLIED)</eg>
 
selects the first child of the location source which is an <gi tei="yes">fs</gi>
element for which the <att tei="no">resp</att> attribute has been left
unspecified.  The location ladder
 
<eg rend="syntax">ROOT DESCENDANT (1 (DIV[01234567]) TYPE chapter N 2)</eg>
 
selects the second chapter of a text, regardless of whether chapters are
tagged using <gi tei="yes">div</gi>, <gi tei="yes">div1</gi>, <gi tei="yes">div2</gi>, or some other
text-division element.  It does so by selecting the first text-division
element in the document which is of <att tei="no">type</att> chapter and
has the <att tei="no">n</att> value 2.</p><p>In formal terms, the attribute-value parameter of a tree-traversal
step is defined thus:
 
<eg rend="syntax"><![CDATA[value    ::=  LITERAL                  // i.e. quoted string.
         |    NAME                     // As for attribute values in
         |    NUMBER                   // document, NMTOKENs need not
         |    NUMTOKEN                 // be quoted
         |    '#IMPLIED'               // No value specified, no default
         |    '*'                      // Any value matches.
         |    '(' regular ')']]></eg></p></div4><div4 id="SAXR1DE" name="Section" ref="Y"><head>The DESCENDANT Keyword</head><p>If the <code tei="yes" type="teikw">descendant</code> keyword is used, the
location term selects an element or character-data string which is a
descendant of the current location source.  Like <code tei="yes" type="teikw">child</code>, <code tei="yes" type="teikw">descendant</code> takes as a
value a series of one or more parenthesized steps, which may contain the
same four parameters described above.  The set of elements and strings
which may be selected, however, is the set of all descendants of the
location source (i.e. the set of all elements contained by it), rather
than only the set of immediate children.</p><p>The location specification
 
<eg rend="syntax">ID (a23) DESCENDANT (2 TERM LANG DE)</eg>
 
thus selects the second <gi tei="yes">term</gi> element with a <att tei="yes">lang</att> of
<code tei="yes" type="value">de</code> occurring within the element with an
<att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  The search for matching
elements occurs in the same order as the SGML data stream; in terms of
the document tree, this amounts to a depth-first left-to-right search.</p><p>If the instance number is negative, the search is a depth-first
right-to-left search, in which the right-most, deepest matching element
is numbered -1, etc.  The location specification
 
<eg rend="syntax">DESCENDANT (-1 NOTE)</eg>
 
thus chooses the last <gi tei="yes">note</gi> element in the document, that is,
the one with the rightmost start-tag.</p></div4><div4 id="SAXR1AN" name="Section" ref="Y"><head>The ANCESTOR Keyword</head><p>The <code tei="yes" type="teikw">ancestor</code> location term selects an element
from among the direct ancestors of the location source in the document
hierarchy.  The location value is of the same form as defined for the
<code tei="yes" type="teikw">child</code> and <code tei="yes" type="teikw">descendant</code>
location types.  However, the <code tei="yes" type="teikw">ancestor</code> keyword
selects elements from the list of containing elements or
<soCalled>ancestors</soCalled> of the location source, counting upwards
from the parent of the location source (which is ancestor number 1) to
the root of the document instance (which is ancestor number -1).</p><p>The location source must have at least as many ancestors as the
absolute value of the instance number specified as the first parameter
of the step.  The <code tei="yes" type="teikw">ancestor</code> type thus may not be
specified as the first component of a location specification, because
the initial location source in effect at that point is the root, which
has no ancestors.</p><p>For example, the location term
 
<eg rend="syntax">ANCESTOR (1 * N 1) (1 DIV)</eg>
 
first chooses the smallest element properly containing the location
source and having attribute <att tei="yes">n</att> with value <code tei="yes" type="value">1</code>; and then the smallest <gi tei="yes">div</gi> element properly
containing it.  The location term
 
<eg rend="syntax">ANCESTOR (1)</eg>
 
chooses the immediate parent of the location source, regardless of its
type or attributes.  The location term
 
<eg rend="syntax">ANCESTOR (1 * LANG fr)</eg>
 
selects the smallest ancestor for which the <att tei="yes">lang</att> attribute
has the value <code tei="yes" type="value">fr</code>.  The term
 
<eg rend="syntax">ANCESTOR (-1 * LANG fr)</eg>
 
selects the <emph>largest</emph> ancestor for which the <att tei="yes">lang</att>
attribute has the value <code tei="yes" type="value">fr</code>.  Without the
attribute specification, the term
 
<eg rend="syntax">ANCESTOR (-1)</eg>
 
selects the largest ancestor of the location source and is thus normally
synonymous with the keyword <code tei="yes" type="kw">ROOT</code>.  If the instance
indicator is given as <code tei="yes" type="kw">ALL</code>, then all the ancestor
elements which match the later parameters are selected; since the
largest of these will necessarily include all the others, the value
<code tei="yes" type="kw">ALL</code> is thus synonymous with the value <code tei="yes" type="value">(-1)</code> when used with <code tei="yes" type="kw">ANCESTOR</code>.
 
Finally, the term
 
<eg rend="syntax">ANCESTOR (1 (DIV[0123456789]?))</eg>
 
chooses the smallest <gi tei="yes">div</gi> element of any level which contains
the location source.</p></div4><div4 id="SAXR1PR" name="Section" ref="Y"><head>The PREVIOUS Keyword</head><p>The <code tei="yes" type="teikw">previous</code> keyword selects an element or
character-data string from among those which precede the location source
within the same containing element.  We speak of the elements and
character-data strings contained by the same <code tei="yes" type="teikw">parent</code> element as <term>siblings</term>; those which
precede a given element or string in the document are its <term>elder
siblings</term>; those which follow it are its <term>younger
siblings</term>.</p><p>The instance number in the location value of a <code tei="yes" type="teikw">previous</code> term designates the nth elder sibling of the
location source, counting from most recent to less recent.  The location
ladder
 
<eg rend="syntax">ID (a23) PREVIOUS (1)</eg>
 
thus designates the element immediately preceding the element with an
<att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  Negative instance numbers
also designate elder siblings, counting from the eldest sibling to the
youngest.  The location source must have at least as many elder siblings
as the absolute value of the instance number.  If the location source
has at least one elder sibling, then the location term
 
<eg rend="syntax">PREVIOUS (-1)</eg>
 
designates its eldest sibling and is thus synonymous with the ladder
 
<eg rend="syntax">ANCESTOR (1) CHILD (1)</eg>
 
The value <code tei="yes" type="kw">ALL</code> may be used to select the entire
range of elder siblings of an element:  the location ladder
 
<eg rend="syntax">ID (a23) PREVIOUS (ALL)</eg>
 
thus designates the set of elements which precede the element with an
<att tei="yes">id</att> of <code tei="yes" type="value">a23</code> and are contained by the
same parent.</p></div4><div4 id="SAXR1NE" name="Section" ref="Y"><head>The NEXT Keyword</head><p>The keyword <code tei="yes" type="teikw">next</code> behaves like <code tei="yes" type="teikw">previous</code>, but selects from the younger siblings of the
location source, not the elder siblings.  The location ladder
 
<eg rend="syntax">ID (a23) NEXT (1)</eg>
 
thus designates the element or string immediately following the element
which has an <att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  Negative
instance numbers also designate younger siblings, counting from the
youngest sibling to the location source.  The location source must have
at least as many younger siblings as the absolute value of the instance
number.  If the location source has at least one younger sibling, then
the location term
 
<eg rend="syntax">NEXT (-1)</eg>
 
designates its youngest sibling and is thus synonymous with the ladder
 
<eg rend="syntax">ANCESTOR (1) CHILD (-1)</eg></p></div4><div4 id="SAXR1PC" name="Section" ref="Y"><head>The PRECEDING Keyword</head><p>The <code tei="yes" type="teikw">preceding</code> keyword selects an element or
character-data string from among those which precede the location
source, without being limited to the same containing element.  The set
of elements and strings which may be selected is the set of all elements
and strings in the entire document which occur or begin before the
location source.  (For purposes of the keywords <code tei="yes" type="kw">PRECEDING</code> and <code tei="yes" type="kw">FOLLOWING</code>, elements
are interpreted as occurring where their start-tag occurs.)  The <code tei="yes" type="kw">PRECEDING</code> keyword thus resembles <code tei="yes" type="kw">PREVIOUS</code> but differs in searching a larger set of strings
and elements; its result is not guaranteed to be a subset of its
location source.</p><p>The instance number in the location value of a <code tei="yes" type="teikw">preceding</code> term designates the nth element or
character-data string preceding the location source, counting from most
recent to less recent.  The location ladder
 
<eg rend="syntax">ID (a23) PRECEDING (5)</eg>
 
thus designates the fifth element or string before the element with an
<att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  Negative instance numbers
also designate preceding elements or strings, counting from the eldest
to the youngest; the ladder
 
<eg rend="syntax">ID (a23) PRECEDING (-5)</eg>
 
thus selects the fifth element or string in the document overall,
assuming that it precedes the element with an <att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  It is thus normally synonymous with
 
<eg rend="syntax">ROOT DESCENDANT (5)</eg>
 
differing only in that it fails if four items or fewer precede element
A23.
 
The location source must have at least as many elder siblings as the
absolute value of the instance number; otherwise, the <code tei="yes" type="teikw">preceding</code> term fails.
 
The value <code tei="yes" type="kw">ALL</code> may be used to select the entire
portion of the document preceding the beginning of the location source:
the location ladder
 
<eg rend="syntax">ID (a23) PRECEDING (ALL)</eg>
 
designates the entire portion of the document preceding the start-tag
for element A23.</p></div4><div4 id="SAXR1FW" name="Section" ref="Y"><head>The FOLLOWING Keyword</head><p>The keyword <code tei="yes" type="teikw">following</code> behaves like <code tei="yes" type="teikw">preceding</code>, but selects from the portion of the
document following the location source, not that preceding it.  The
location ladder
 
<eg rend="syntax">ID (a23) FOLLOWING (1)</eg>
 
thus designates the element or string immediately following the element
which has an <att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  Negative
instance numbers select elements or strings counting from the end of the
document to the location source.  There must be at least as many
elements or strings following the location source as the absolute value
of the instance number.  If the location source has at least one
following element or string, then the location term
 
<eg rend="syntax">FOLLOWING (-1)</eg>
 
designates the youngest of these and is thus synonymous with the ladder
 
<eg rend="syntax">ROOT DESCENDANT (-1)</eg></p></div4><div4 id="SAXR1PA" name="Section" ref="Y"><head>The PATTERN Keyword</head><p>The <code tei="yes" type="teikw">pattern</code> keyword selects the
<emph>first</emph> place within the location source which matches a
pattern-matching expression included as the location value.  If more
than one location matches that expression, there is no error, but the
second and later matches are ignored.</p><p>Matching is defined to be case-sensitive, i.e. <cited>abc</cited> is
<emph>not</emph> the same as <cited>ABC</cited>.  The pattern is
expressed as a regular expression in which the following characters have
special meanings, similar to those of many Unix programs (such as
<ident tei="yes" type="prog">grep</ident>) which handle regular expressions:
 
<list id="RECHARS" rend="dl" type="gloss"><label>.</label><item>match any single character (including white
space characters).</item><label>[ ...  ]</label><item>match any character from the set enclosed
within the brackets.  If, however, the first enclosed character is
<cited>&amp;circ;</cited>, then match any character <emph>not</emph> from
the set enclosed within the brackets.  For example,
<cited>[&amp;circ;aeiou]</cited> would match any character except a, e, i,
o, or u.</item><label>\</label><item>If the next character is a, d, n, or s, the
expression matches any character from a pre-defined group, as shown
below; otherwise, the next character is to be taken literally, even if
it would otherwise have a special meaning.  The special character
classes are:
<list type="gloss"><label>\a</label><item>any alphabetic character (as defined in the writing
system declaration)</item><label>\d</label><item>any digit (0 through 9)</item><label>\n</label><item>any line boundary</item><label>\s</label><item>any white-space character (space, tab, record end, record
start)</item></list>
Note that although \n for newline is provided, its use is
discouraged.</item><!-- what DOES this mean? if we find someone using it do we chop  --><!-- their hands off? lock them in a room with Michael Hart? or what? --><label>*</label><item>match zero or more occurrences of the previous
regular expression.</item><label>+</label><item>match one or more occurrences of the preceding
regular expression.</item><label>?</label><item>match zero or one occurrences of the preceding
regular expression.</item><label>&amp;circ;</label><item>match the following regular expression only at
the beginning of the location source.</item><label>$</label><item>match the preceding regular expression only at the
end of the location source.</item><label>|</label><item>match either the regular expression on the left,
or the one on the right.</item><label>(...)</label><item>match the regular expression within the
parentheses.  (Parentheses are used to control application of the *, ?,
+, and | operators, etc.)</item></list></p><p>For example, the location specification
 
<eg rend="syntax">PATTERN (Chapter.8)</eg>
 
chooses the first instance of the content string <cited>Chapter</cited>
which is followed by any single character and then the digit 8, within
the location source.  Various elements which contain that location could
be selected by following the <code tei="yes" type="teikw">pattern</code> location
term with one or more of other types such as <code tei="yes" type="teikw">ancestor</code> (see above).</p><p>It is recommended practice to use structure-oriented location types
to specify the destination element as narrowly as possible, and then to
specify a pattern only within that element context.  If element
boundaries are encountered within the location source, however, they are
ignored and have no effect on the pattern matching operation.</p><p>In formal terms, the location value of the <code tei="yes" type="teikw">pattern</code> keyword is defined thus:
 
<eg rend="syntax"><![CDATA[regs     ::= '(' regular ')'
         |    regs '(' regular ')'
 
regular  ::=  character
         |    '.'                           // match any character
         |    '^' || characters || ']'     // match any char not in list
         |    '[' || characters || ']'      // match any char in list
         |    '\a'                     // match any alphabetic
         |    '\d'                     // match any digit 0-9
         |    '\n'                     // match newline (&#RE;&#RS;)
         |    '\s'                     // match any whitespace character
         |    '\\'                     // match backslash (rev. solidus)
         |    '\' || nonspecial        // match nonspecial character
         |    regular || '*'           // match 0-n of 'regular'
         |    regular || '+'           // match 1-n of 'regular'
         |    regular || '?'           // match 0-1 of 'regular'
         |    '^' || regular           // match at start of loc source
         |    regular || '$'           // match at end of loc source
         |    regular || regular       // match 1st, then 2d regular exp.
         |    regular || '|' || regular // match either 1st or 2d
         |    '(' || regular || ')'    // use parentheses for grouping
 
characters ::= /* empty string */
         |    characters character
 
nonspecial ::= /* any character except a, d, n, or s */]]></eg></p></div4><div4 id="SAXR1TO" name="Section" ref="Y"><head>The TOKEN Keyword</head><p>The <code tei="yes" type="teikw">token</code> keyword selects a sequence of one
or more <term rend="noindex">tokens</term> chosen from within the
character content of the location source, where tokens are counted
exactly as for the corresponding HyTime <code tei="yes" type="kw">tokenloc</code>
form.  The location value must be either a single positive integer, or a
pair of positive integers separated by white space, representing the
first and the last token numbers to be included in the resulting
location.  If two integers are specified, the second must not be less
than the first.  The location source must contain at least as many
tokens as are specified in the location value.</p><p>This location type should not be used to count across element
boundaries.  It is recommended practice to use structure-oriented
location types to specify the destination element as narrowly as
possible, and then to specify a token location only within that element
context.  If element boundaries are encountered within the location
source, they are ignored.</p><p>This location type behaves intuitively only for strings containing an
alternating sequence of SGML name-characters and white space; this is
the type of string found, for example, in SGML attribute values of type
IDREFS, such as <code tei="yes" type="value">a21 z a13</code>.
 <!-- It is not TEI recommended practice to apply TOKENLOC to  --><!-- other string types, in part because it would compromise  --><!-- interconvertibility with HyTime; but if such counting is  --><!-- needed, tokens shall be counted as if all non white space  --><!-- characters (such as punctuation) were added to the class of  --><!-- name characters.  That is, only white space characters  --><!-- separate tokens.< /note>  -->
 
For compatibility with the HyTime standard, all characters not included
in the class of name characters by the current SGML declaration (by
default this includes all punctuation other than the hyphen and full
stop) are treated as white space characters.</p><p>For example, the location specification
 
<eg rend="syntax">ID (a27) TOKEN (3 5)</eg>
 
chooses the 3rd, 4th, and 5th tokens from the content of the element
whose identifier is <code tei="yes" type="value">a27</code>.  If this element
contained the string <cited>This is _not_ a very good idea</cited>, the
target selected would be <cited>not_ a very</cited>.</p><p>In formal terms the location value of the <code tei="yes" type="teikw">token</code> and <code tei="yes" type="teikw">str</code> keywords is
defined as a range:
 
<eg rend="syntax"><![CDATA[range    ::=  NUMBER
         |    NUMBER NUMBER]]></eg></p></div4><div4 id="SAXR1ST" name="Section" ref="Y"><head>The STR Keyword</head><p>The <code tei="yes" type="teikw">str</code> keyword identifies a sequence of one
or more <term rend="noindex">characters</term> chosen from within the
character content of the location source, where characters are counted
exactly as for the HyTime <code tei="yes" type="kw">dataloc</code> form with <code tei="yes" type="frag">quantum=str</code>, which has a corresponding meaning and
usage.  The location value must be either a single positive integer, or
a pair of positive integers separated by white space, indicating the
first and the last characters to be included in the resulting location.
If two integers are specified, the second must not be less than the
first.  The location source must have at least as many characters as are
specified in the larger of the integers.</p><p>This location type should not be used to count across element
boundaries.  The recommended practice is to use structure-oriented
location types to specify the destination element, and then to specify a
character location only within that element context.  If element
boundaries are encountered, however, within the location source, they
have no effect.</p><p>Character offsets in an SGML document must be counted not from the
original source file, but from the output of the SGML parser, (the
<term>element structure information set</term> or <term>ESIS</term>).
This is because the rules of SGML allow certain characters to be deleted
or expanded transparently.</p><p>For example, the location specification
 
<eg rend="syntax">ID (a27) STRLOC (3 5)</eg>
 
chooses the 3rd 4th and 5th characters of the content of the element
having identifier a27.  If this element contained the string <q>This
turned out to be an even worse idea</q>, the result would be the string
<cited>is </cited> (i, s and a space).
 <!-- Not sure whether or not to keep the following one: --><!-- It needs to be checked for consistency with whatever goes --><!-- into graphs, figures etc. --></p><p>In multi-byte character sets it is characters which are counted, not
bytes.  However, in the case of diacritics coded by sequences of bit
combinations rather than having separate code points for every
combination of letter and diacritic, the diacritics are counted.  This
means that the following location ladder may retrieve different strings,
depending on the system character set in use and on the entity
declarations in effect:
 
<eg rend="syntax"><![CDATA[PATTERN (Wagner's\sG&ouml;tterd&aum;mmerung) STR (10 24)]]></eg>
 
In some character sets, where &ouml; and &auml; are encoded as single
characters, it will select the string
<cited>G&ouml;tterd&auml;mmerung</cited>; in others, where they are
encoded with distinct characters for umlaut, a, and o, it will select
the string <cited>G&ouml;tterd&auml;mmeru</cited>, truncating the last
two letters.  If a system-dependent definition is used (containing e.g.
a printer escape sequence), the results are even less predictable.  For
this reason, the <code tei="yes" type="teikw">str</code> keyword must be used with
caution and should be avoided where possible.</p></div4><div4 id="SAXR1SP" name="Section" ref="Y"><head>The SPACE Keyword</head><p>The <code tei="yes" type="teikw">space</code> location term applies to entities
which represent graphical or spatio-temporal data; typically such
entities are not encoded in SGML, but in one of many specialized
graphical formats.  SGML provides standard mechanisms (the NOTATION
declaration and related constructs) for specifying what format such an
entity uses.</p><p>The location value for <code tei="yes" type="teikw">space</code> consists of two
or three parenthesized parameter lists.  The first contains the name of
the co-ordinate space in use.  The second and third each consist of any
number of signed integers.  The numbers in a parameter list represent
locations along each dimension of a Cartesian co-ordinate space with all
axes orthogonal; the length of the list equals the number of
dimensions/axes of the space (usually, but not inevitably, 2, 3, or 4).</p><p>If the third parameter list is not specified, the location is the
single point in the co-ordinate space specified by the second parameter
list.  If all three parameter lists are specified, the location is the
rectangular prism defined by treating corresponding items of the second
and third lists as inclusive bounds along each dimension in turn.</p><p>The mapping from co-ordinates to physical or display space, and the
meaning and ordering of the axes, are not defined by these guidelines.
They should be specified in the TEI header unless they can be determined
by definition from the format in which the referenced entity is known to
be encoded (for example, many graphics formats can only encode locations
in units of pixels, counted in a 3 dimensional left-handed co-ordinate
space).</p><p>Time may be construed as an axis in addition to any others; when it
is, it is TEI recommended practice that it be positioned last.  The
units used must be defined in the TEI header; it is acceptable in
certain media (such as videodiscs) to use frame numbers as a surrogate
axis for time.</p><p>For example,
 
<eg rend="syntax">SPACE (2D) (0 0) (1 1)</eg>
 
specifies the location of the unit square tangent to the origin in
quadrant 1 of a common graph.</p><p>The location value for a <code tei="yes" type="teikw">space</code> location term
is a NAME enclosed in parentheses, followed by a point pair:
 
<eg rend="syntax"><![CDATA[pointpair ::= '(' numbers ')'
         |    '(' numbers ')' '(' numbers ')'
 
numbers  ::=  signed
         |    numbers signed]]></eg>
 <!-- Changed definition of numbers to from the following,     --><!-- which contradicts the prose (NUMBER is unsigned, no?)    --><!-- msm                                                      --><!-- numbers  ::=  NUMBER                                     --><!--          |    numbers NUMBER                             --><!--          ;                                               --></p></div4><div4 id="SAXR1FO" name="Section" ref="Y"><head>The FOREIGN Keyword</head><p>The <code tei="yes" type="teikw">foreign</code> keyword takes any number of
parenthesized parameter lists, and is terminated by the end of the
attribute value, or by the next non-parenthesized token, whichever comes
first.</p><p>The meaning of the <code tei="yes" type="teikw">foreign</code> location term is
not defined by these Guidelines.  It is intended for use in pointing to
special kinds of non-SGML, non-coordinate space data.  That is, it
should be used for making links to data which cannot be specified using
the other mechanisms.  The meaning of any <code tei="yes" type="teikw">foreign</code> location types must be specified in the TEI
header, as a series of paragraphs at the end of the
<gi tei="yes">encodingDesc</gi> element defined in section <xref target="HD5"/>.
 <!-- BUT WHERE? --><!-- encodingDesc.  I think. -msm -->
 
If more than one such type is used, it is TEI recommended practice that
the first parameter list to <code tei="yes" type="teikw">foreign</code> be a name
associated with the particular type by documentation in the TEI header.</p><p>For example, assume that some program uses a proprietary data format
called XFORM, and that the program has supplied an identifier <code tei="yes" type="value">06286208998</code> for some piece of data it owns.  Then the
location specification
 
<eg rend="syntax">FOREIGN (XFORM) (06286208998)</eg>
 
would be one way of expressing a link to that piece of data.</p></div4><div4 id="SAXR1HY" name="Section" ref="Y"><head>The HYQ Keyword</head><p>The <code tei="yes" type="teikw">HyQ</code> keyword takes a single parenthesized
parameter lists, which contains an expression in the <code tei="yes" type="teikw">HyQ</code> query language defined by the HyTime standard.
See documentation on HyTime and HyQ for definitions of HyQ expressions.</p></div4><div4 id="SAXR1DI" name="Section" ref="Y"><head>The DITTO Keyword</head><p>The <code tei="yes" type="teikw">ditto</code> keyword is valid only as the first
location term in a ladder, and only within the <att tei="yes">to</att> attribute
of an extended pointer element.  It designates the location result of
the <att tei="yes">from</att> attribute on the same element.  Thus in the pointer
 
<eg><![CDATA[<xptr from='ID (a23) ANCESTOR (1 DIV[0123]) PATTERN (Wagnerian)'
      to='DITTO PATTERN (Liebestod)'>]]></eg>
 
the <att tei="yes">from</att> attribute designates the first occurrence of the
string <cited>Wagnerian</cited> in the <gi tei="yes">div</gi> containing the
element with an <att tei="yes">id</att> of <code tei="yes" type="value">a23</code>.  The
<att tei="yes">to</att> attribute designates the first occurrence of the string
<cited>Liebestod</cited> which occurs <emph>after</emph>
<cited>Wagnerian</cited>, within the same <gi tei="yes">div</gi>.  Without the
<code tei="yes" type="teikw">ditto</code> keyword, it would be necessary to repeat
the entire location ladder of the <att tei="yes">from</att> attribute in the
<att tei="yes">to</att> attribute, which would be error-prone for complex
expressions.</p></div4></div3><div3 id="SAXR2" name="subsection" ref="Y"><head>Using Extended Pointers</head><p>As noted above, when only the <att tei="yes">from</att> attribute is specified,
the <gi tei="yes">xref</gi> or <gi tei="yes">xptr</gi> element points at the span indicated
by <att tei="yes">from</att>.  When both <att tei="yes">from</att> and <att tei="yes">to</att> are
specified, the element points at the span running from the beginning of
the span indicated by the former to the end of the span indicated by the
latter.  To point at the second, third, and fourth paragraphs of the
second chapter (<gi tei="yes">div1</gi>) in the body of the current document,
therefore, one may specify either of the following:
 
<eg><![CDATA[<xptr from='DESCENDANT (1 body) CHILD (2 div1) (2 p)'
      to = 'DESCENDANT (1 body) CHILD (2 div1) (4 p)' >
<!-- or equivalently: -->
<xptr from='DESCENDANT (1 body) CHILD (2 div1) (2 p)'
      to = 'DITTO NEXT (2 p)'>]]></eg></p><p>To point to <q>the <gi tei="yes">term</gi> occurring in the current
<gi tei="yes">termEntry</gi> with attribute <att tei="yes">n</att> = 2</q>, only the
<att tei="yes">from</att> attribute would be required:
 
<eg><![CDATA[<xptr from='HERE ANCESTOR (1 TERMENTRY) DESCENDANT (1 TERM N 2)'>]]></eg></p><p>The following example demonstrates how elements from two different
documents may be combined
 
<eg><![CDATA[ 
<xptr id=X1 doc=doc1 from='id (d1.1)'>
<xptr id=X2 doc=doc2 from='id (d2.1) tree (2 *)'>
 
<ptr id=P1 target='X1 x2'>
 
<link targets='p1 s1 s2' evaluate=all>]]></eg>
 
The first <gi tei="yes">xptr</gi> indicates the element in doc1 which has
identifier <code tei="yes" type="value">d1.1</code>.  The second indicates the
second subelement of the element in doc2 which has identifier <code tei="yes" type="value">d2.1</code>.  These two elements are pointed to as a single
item by the <gi tei="yes">ptr</gi> element and given the identifier <code tei="yes" type="value">p1</code>.  This aggregation, finally, is linked with two
other elements both in the current document, with identifiers <code tei="yes" type="value">s1</code> and <code tei="yes" type="value">s2</code>.</p><p>An extended pointer, as described above, may specify as its target
only a single destination.  Where the intended destination of a link is
an aggregation or alignment of destinations, possibly in separate
documents, an intermediate pointer of some kind must be used, as
described in section <xref target="SAPTIP"/> elsewhere in this chapter.
Like any other element, an <gi tei="yes">xref</gi> and <gi tei="yes">xptr</gi> may be given
a unique id within the document that contains them.  This id value can
then be supplied as one of the <att tei="yes">target</att> values for an
intermediate <gi tei="yes">ptr</gi> or <gi tei="yes">link</gi> element, to represent
aggregation or linkage respectively.  The <gi tei="yes">join</gi> element
discussed in section <xref target="SAAG"/> may also be used.</p><p>For example, a modern commentary on an older text must frequently
refer to that text, which might well be encoded in a separate SGML
document.  Some discussions will refer to set of discrete passages in
the older text, and will thus require multi-headed pointers.  In such a
case, the document type declaration must contain a declaration for an
SGML entity containing the older text, which might look something like
this:
 
<eg><![CDATA[<!-- the 1729 Dunciad Variorum -->
<!ENTITY dunciad system 'dunc1729.tei' >]]></eg>
 
In the commentary itself, reference will be made to this external
document, using <gi tei="yes">xptr</gi> and <gi tei="yes">xref</gi> elements.  When the
commentary refers to aggregates of discontiguous passages, <gi tei="yes">xptr</gi>
elements are used to point to the individual passage, and a <gi tei="yes">ref</gi>
element may refer to these passages as a group by pointing to the
<gi tei="yes">xptr</gi>s:
 <!-- These examples should be pointing at notes and lines in  --><!-- the Dunciad which really do refer to Theobald and Curl,  --><!-- and it would be nice to have a link for something other  --><!-- than a person named; possibly imitations of Vergil vs.   --><!-- imitations of Ovid, or references to gluttony vs.        --><!-- references to piss vs. references to shit.  I'll work    --><!-- on this this evening.                                    --><!-- These are not at all exhausting, but at least the line   --><!-- numbers given are real ones now.                         -->
 <!-- Perhaps for P3 or for the case book we can get someone   --><!-- to give us a real web from an Intermedia system or       --><!-- something, or maybe Elli can reproduce part of Perseus.  -->
 
<eg><![CDATA[<xptr id='XL2.5'   doc=dunciad from='ID (L2.5)'  >
<xptr id='XN1.48'  doc=dunciad from='ID (N1.48)' >
<xptr id='XN1.68'  doc=dunciad from='ID (N1.68)' >
<xptr id='XN1.104' doc=dunciad from='ID (N1.104)'>
<xptr id='XN1.106' doc=dunciad from='ID (N1.106)'>
 ...
<p>In <ref target='XL2.5 xN1.48 xN1.68 xN1.104 xN1.106'
evaluate=all>the references to Theobald</ref>, Pope's satire
characteristically ...</p>]]></eg>
 
If the same discontiguous target is to be referred to repeatedly, it may
be convenient to give it a single identifier, thus:
 
<eg><![CDATA[<xptr id='XL2.5'   doc=dunciad from='ID (L2.5)'  >
<xptr id='XN1.48'  doc=dunciad from='ID (N1.48)' >
<xptr id='XN1.68'  doc=dunciad from='ID (N1.68)' >
<xptr id='XN1.104' doc=dunciad from='ID (N1.104)'>
<xptr id='XN1.106' doc=dunciad from='ID (N1.106)'>
<ptr id='THEOBALD' target='XL2.5 xN1.48 xN1.68 xN1.104 xN1.106'>
 ...
<p>In <ref target='THEOBALD' evaluate=all>the references to
Theobald</ref>, Pope's satire characteristically ...</p>]]></eg></p><p>A hypertext web might associate passages of the text and notes with
the individuals mentioned, the ancient authors imitated, or thematic
content, thus:
 
<eg><![CDATA[<xptr id='XL2.5'   doc=dunciad from='ID (L2.5)'  >
<xptr id='XN1.48'  doc=dunciad from='ID (N1.48)' >
<xptr id='XN1.68'  doc=dunciad from='ID (N1.68)' >
<xptr id='XN1.104' doc=dunciad from='ID (N1.104)'>
<xptr id='XN1.106' doc=dunciad from='ID (N1.106)'>
<ptr id='THEOREFS' target='XL2.5 xN1.48 xN1.68 xN1.104 xN1.106'>
 
<xptr id='XN2.3'   doc=dunciad from='ID (N2.3)'  >
<xptr id='XN2.46'  doc=dunciad from='ID (N2.46)' >
<xptr id='XN2.54'  doc=dunciad from='ID (N2.54)' >
<xptr id='XN2.66'  doc=dunciad from='ID (N2.66)'>
<xptr id='XN2.78'  doc=dunciad from='ID (N2.78)'>
<xptr id='XN1.104' doc=dunciad from='ID (N1.104)'>
<ptr id='CURLREFS' target='XN2.3 xN2.46 xN2.54 xN2.66 xN2.78 xN1.104'>
 
 <!-- ... -->
<div><head>Individuals Named in the Text</head>
<list type=gloss>
<label id=CURLNAME>Curll, Edmund</label>
<item  id=CURLDESC>A bookseller and publisher ... </item>
 <!-- ... -->
<label id=THEONAME>Theobald, Lewis.</label>
<item  id=THEODESC>Attorney, active also as editor and reviewer ...
</item>
 <!-- ... -->
</list>
 
 <!-- ... -->
<div><head>Ancient Authors Imitated in the Text</head>
<list type=bulleted>
<item id=VIRGIL>Virgil
<item id=HOMER >Homer
<item id=OVID  >Ovid
 <!-- ... -->
</list>
 
<ptr id=CURLL    target='CURLNAME curldesc'>
<ptr id=THEOBALD target='THEONAME theodesc'>
 <!-- ... -->
<linkGrp type=bio>
<link targets='theobald theorefs'>
<link targets='curl     curlrefs'>
 <!-- ... -->
</linkGrp>
<linkGrp type=imitations>
<link targets='virgil   virgrefs'>
<link targets='homer    homerefs'>
 <!-- ... -->
</linkGrp>]]></eg></p></div3></div2><!-- more, and realler, examples needed --><!-- damn straight. -msm                --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2saxr.odd ??><?tei:SOF p2sase.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sase.odd,v $
    * Revision 1.8  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.6  1994/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.5  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.4  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.2  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 8 Jan 98: LB : added ab element --><!-- 94-03-26 : MSM : corrections from SJ                     --><!-- 94-03-26 : MSM : disambiguate TERM, Q (> code, ident...) --><!-- 94-03-15 : MSM : changes as per LB, TL, JL               --><!-- 4 feb LB merged in anchor; revised and expanded          --><!-- 19 dec 93: LB: fixed an xref                             --><!-- 93-09-15 : MSM : minor SGML cleanup                      --><!-- 93-07-22 : DTL : more minor fixes                        --><!-- 93-07-12 : DTL : minor fixes                             --><!-- 93-07-08 : DTL : rewrite material on arbitrary           --><!-- segments from COse; exx from Shields "Dead Languages",   --><!-- refer to Pope ex in SApt, Sigmund ex in AIsp             --><div2 id="SASE" name="subsection" ref="Y"><head>Blocks, Segments and Anchors</head><p>In this section, we define three general purposes elements which may be
used to mark and categorize both a span of text and a point within one.
These elements have several uses, most notably to provide elements which
can be given identifiers for use when aligning or linking to parts of a
document, as discussed elsewhere in this chapter.  They also provide a
convenient way of extending the semantics of the TEI markup scheme in a
theory-neutral manner, by providing for two neutral or <soCalled>anonymous</soCalled> elements to which the encoder can add any meaning not
supplied by other TEI defined elements.
 
<tagList style="one-line"><tagDesc tagDoc="ANCHOR"/><tagDesc tagDoc="SEG" atts="part"/><tagDesc tagDoc="ANONB" atts="part"/></tagList>
 
These elements are all members of the class <ident tei="yes" type="class">typed</ident>, and inherit from it the attributes
<att tei="yes">type</att> and <att tei="yes">subtype</att>:
 
<adList classDoc="TYPED" atts="type subtype"/>
 <!-- Killed following example as insufficiently convincing --><!-- for reasons given in note. --><!-- Substituted references elsewhere and following discussion. -->
 <!-- <p>For example, the <gi>seg</gi> tag may be used to --><!-- delimit the sequence of words at the beginning of a text --><!-- division that are highlighted in some way. -->
 <!-- <note place=foot>The <gi>hi</gi> tag (see <xref --><!-- target=COHQHE>) may, of course, also be used in this case, --><!-- but the <att>type</att> attribute of the <gi>seg</gi> tag --><!-- makes it possible to specify the purpose of the --><!-- highlighting.</note> -->
 <!-- David Shields, Dead Languages, 1990, p56 --><!-- <eg><![ CDATA [ --><!-- <div1 n=8> --><!-- <p><s><seg type='beginning of chapter' rend=caps> --><!-- So father's only</seg> --><!-- glory was the ballfield.</s> --><!-- ]]> --><!-- </eg> -->
</p><p>The <gi tei="yes">anchor</gi> element may be thought of as an empty
<gi tei="yes">seg</gi>, or as an artifice enabling an identifier to be attached
to any position in a text. Like the <gi tei="yes">mileStone</gi> element
discussed in section <xref target="CORS"/>, it is useful where multiple
views of a document are to be combined, for example, when a logical
view based on paragraphs or verse lines is to be mapped on to a
physical view based on manuscript lines.  However, it differs from the
milestone and related elements in that the <gi tei="yes">anchor</gi> element
should not be used to mark the start or end of an arbitrary zone
within a text, but only to mark an arbitrary point used for alignment,
or as the target of a spanning element such as those discussed in
section <xref target="PHAD"/>.
 <!-- I think this is a really bizarro example --><!-- but havent been able to find  a better one (LB) -->
 </p><p>For example, suppose that we wish to mark the end of the fifth word
following each occurrence of some term in a particular text, perhaps to
assist with some collocational analysis.  This can most easily be done
with the help of the <tag compl="full" tei="yes">anchor</tag> tag, as follows:
 <!-- Vladimir Nabokov, Pnin, 1953, p14 of 1967 Avon pb reprinting -->
<eg><![CDATA[<!-- ... -->
English language.  Except for not very<anchor id=ENG1 >
<!-- ... -->
English at all at the time<anchor id=ENG2 >
<!-- ... -->
English was still full of flaws<anchor id=ENG3 >
<!-- ... -->
English.  This was revised by young<anchor id=ENG4>]]></eg>
 
In  section <xref target="SACS1"/> we discuss 
ways in which these <gi tei="yes">anchor</gi>
points might be used to represent an alignment such as one
might get in a keyword-in-context concordance.
<!-- add more examples/ cross references -->
 
 </p><p>The <gi tei="yes">seg</gi> element may be used at the encoder's discretion to
mark almost any segment of the text of interest for processing.  One use
of the element is to mark text features for which no appropriate markup
is otherwise defined, i.e. as a simple extension mechanism.  Another use
is to provide an identifier for some segment which is to be pointed at
by some other element, i.e. to provide a target, or a part of a target,
for a <gi tei="yes">ptr</gi> or other similar element.
 </p><p>Several examples of uses for the <gi tei="yes">seg</gi> element are provided
elsewhere in these Guidelines. For example:
<list type="simple"><item>as a means of marking segments significant in a metrical or
rhyming analysis (see section <xref target="VEME"/>)</item><item>as a means of marking typographic lines in drama (see section<xref target="DRBOD"/>
) or title pages (see section <xref target="DSTITL"/>)</item><item>as a means of marking prosody- or pause-defined units in
transcribed speech (see section <xref target="TSSASE"/>)</item><item>as a means of marking linguistic or other analyses in a
theory-neutral manner (see chapter <xref target="AI"/> passim)</item></list>
 </p><p>In the following simple example, the <gi tei="yes">seg</gi> element simply
delimits the extent of a stutter, a textual feature for which no
element is provided in these Guidelines.
 
<eg><![CDATA[<q>Don't say
<q><seg type=stutter>I-I-I</seg>'m afraid,</q>
Melvin, just say
<q>I'm afraid.</q></q>]]></eg><!-- David Shields, Dead Languages, 1990, p10 --><!-- removed irrelevant tagging LB -->
 
The <gi tei="yes">seg</gi> element is particularly useful for the mark-up of
linguistically significant constituents such as the phrases that may be
the output of an automatic parsing system.  This example also
demonstrates the use of the <att tei="yes">id</att> attribute to carry an
identifier which other parts of a document may use to point to, or align
with:
 
<eg><![CDATA[<seg type=sentence id=BL0034>
  <seg type=phrase id=BL0034.1>Literate and illiterate speech</seg>
  <seg type=phrase id=BL0034.2>in a language like English</seg>
  <seg type=phrase id=BL0034.3>are plainly different.</seg>
</seg>]]></eg><!-- Bloomfield, "Literate and Illiterate Speech", 1927   --><!-- removed irrelevant rend attribute -->
 </p><p>As the above example shows, <gi tei="yes">seg</gi> elements may be nested
directly within one another, to any degree of analysis considered
appropriate.  This is taken a little further in the following example,
where the <att tei="yes">type</att> and <att tei="yes">subtype</att> attributes have been
used to further categorise each word of the sentence (the <att tei="yes">id</att>
attributes have been removed to reduce the complexity of the example):
 
<eg><![CDATA[<seg type=sentence subtype=declarative>
  <seg type=phrase subtype=noun>
    <seg type=word subtype=adjective>Literate</seg>
    <seg type=word subtype=conjunction>and</seg>
    <seg type=word subtype=adjective>illiterate</seg>
    <seg type=word subtype=noun>speech</seg>
    </seg>
  <seg type=phrase subtype=preposition>
    <seg type=word subtype=preposition>in</seg>
    <seg type=word subtype=article>a</seg>
    <seg type=word subtype=noun>language</seg>
    <seg type=word subtype=preposition>like</seg>
    <seg type=word subtype=noun>English</seg>
    </seg>
  <seg type=phrase subtype=verb>
    <seg type=word subtype=verb>are</seg>
    <seg type=word subtype=adverb>plainly  </seg>
    <seg type=word subtype=adjective>different</seg>
    </seg>
  <seg type=punct>.</seg>
  </seg>]]></eg>
 </p><p>(The example values shown are chosen for simplicity of comprehension,
rather than verisimilitude).  It should also be noted that specialized
segment elements are defined in section <xref target="AILC"/> to facilitate
this particular kind of analysis.  These allow for the explicit mark up
of units called <term>s-units</term>, <term>clauses</term>,
<term>phrases</term>, <term>words</term>, <term>morphemes</term> and
<term>characters</term>, which may be felt preferable to the more
generic approach typified by use of the <gi tei="yes">seg</gi> element.  Using
these, the first phrase above might be encoded simply as
 
<eg><![CDATA[  <phr type=noun>
    <w type=adjective>Literate</w>
    <w type=conjunction>and</w>
    <w type=adjective>illiterate</w>
    <w type=noun>speech</w>
  </phr>]]></eg>
 
Note the way in which the <att tei="yes">type</att> attribute of these specialized
elements now carries the value carried by the <att tei="yes">subtype</att>
attribute of the more general <gi tei="yes">seg</gi> element.  For an analysis not
using these traditional linguistic categories however, the <gi tei="yes">seg</gi>
element provides a simple but powerful mechanism.
 </p><p>In language corpora and similar material, the <gi tei="yes">seg</gi> element
may be used to provide an end-to-end segmentation as an alternative to
the more specific <gi tei="yes">s</gi> element proposed in chapter <xref target="AILC"/> for the mark-up of orthographic sentences, or
<term>s-units</term>.  However, it may be more useful to use the
<gi tei="yes">s</gi> element for this purpose, since this means that the
<gi tei="yes">seg</gi> element can then be used to mark both features within
s-units and segments composed of s-units, as in the following example:
<note source="auth" place="foot" anchored="Y">See section <xref target="AISP"/>, where the text from
which this fragment is taken is analyzed.</note>
 
<eg><![CDATA[<seg id=S1S3 type='narrative unit'>
<s id=S1>Sigmund, the
  <seg type=patronymic>son of Volsung</seg>,
   was a king in Frankish country.</s>
<s id=S2>Sinfiotli was the eldest of his sons.</s>
<s id=S3><!-- ... --></s>
</seg>]]></eg>
 </p><p>Like other elements, the <gi tei="yes">seg</gi> tag must be properly enclosed
within other elements.  Thus, a single <gi tei="yes">seg</gi> element can be used
to group together words in different sentences only if the sentences are
not themselves tagged.  The first of the following two encodings is
legal, but the second is not.
 <!-- Made up example -->
<eg rend="erroneous"><![CDATA[Give me <seg type=phrase>a dozen.  Or two or three.</seg>
 
<!-- Illegal! -->
<s>Give me <seg type=phrase>a dozen.</s>
<s>Or two or three.</s></seg>]]></eg>
 </p><p>The <att tei="yes">part</att> attribute may be used as one simple method of
overcoming this restriction:
 
<eg><![CDATA[<s>Give me <seg type=phrase part=I>a dozen.</seg></s>
<s><seg part=F>Or two or three.</seg></s>]]></eg>
 
Another solution is to use the <gi tei="yes">join</gi> element discussed in
section <xref target="SAAG"/>; this requires that each of the <gi tei="yes">seg</gi>
elements be given an identifier.  For further discussion of this generic
encoding problem see also chapter <xref target="NH"/>.
 </p><p>The <gi tei="yes">seg</gi> element has the same content as a paragraph in
prose:  it can therefore be used to group together consecutive sequences
of <ident tei="yes" type="class">inter</ident> class elements, such as lists,
quotations, notes, stage directions etc. as well as to contain sequences
of phrase-level elements.  It cannot however be used to group together
sequences of paragraphs or similar text units such as verse lines; for
this purpose, the encoder should use intermediate pointers, as described
in section <xref target="SAPTIP"/> or the methods described in section<xref target="SAAG"/>
. 
 <!-- deleted (mistagged?) example of how not to do it LB  --><!-- M.F.K. Fisher, "I was really very hungry", As They       --><!-- Were, 1983, p41                                          --><!-- <eg><![ CDATA [ --><!-- Illegal! --><!-- <seg> --><!-- <p> --><!--  --><!-- <q who=MFKF><foreign lang=FR>Mon Dieu!</foreign> All for --><!-- me?</q> I peered at her.  She nodded, her discretion quite --><!-- gone now and a look of ecstatic worry on her pale face and --><!-- eyes and lips.  </p> <p> There were at least eight dishes. --><!-- I felt almost embarrassed, and sat for a minute looking --><!-- weakly at the fork and spoon in my hand.  </p> </seg> ]]> --><!-- </eg> -->
 
 
It is particularly important that the encoder provide a clear
description of the principles by which a text has been segmented, and
the way in which that segmentation is represented.  This should include
a description of the method used and the significance of any
categorization codes.  The description should be provided as a series of
paragraphs within the <gi tei="yes">segmentation</gi> element of the encoding
description in the TEI header, as described in section <xref target="HD53"/>.
 <!-- EDITORS: I can't readily locate where you have said      --><!-- this; please supply any missing details.  This problem   --><!-- also occurs elsewhere.  (DTL)                            --><!-- done. Lou -->
 </p><p>The remainder of this chapter contains a number of examples of the use
of the <gi tei="yes">seg</gi> element simply to provide an element to which an
identifier may be attached, for example so that another segment may be
linked or related to it in some way.</p><p>The <gi tei="yes">ab</gi> (anonymous block) 
element performs a similar function to that of the <gi tei="yes">seg</gi> element, 
but is used for portions of the
text which occur not within paragraphs or other component-level
elements, but at the component level themselves.  It may be used, for
example, to tag the canonical verse divisions of Biblical texts:
<eg><![CDATA[<div1 type='book' n='Gen'>
<head>The First Book of Moses, Called</head>
<head type='main'>Genesis</head>
<div2 type='chapter' n='1'>
<ab n='1'>In the beginning God created the heaven and the
earth.</ab>
<ab n='2'>And the earth was without form, and void; and darkness
<hi>was</hi> upon the face of the deep.  And the Spirit of God
moved upon the face of the waters.</ab>
<ab n='3'>And God said, Let there be light:  and there was
light.</ab>
<!-- ... -->]]></eg><!--* Authorised Version *--></p><p>In other cases, where the text clearly indicates paragraph divisions
containing one or more verses, the <gi tei="yes">p</gi> element may be used to
tag the paragraphs, and the <gi tei="yes">seg</gi> element used to subdivide
them. The <gi tei="yes">ab</gi> element is provided as an alternative to the
<gi tei="yes">p</gi> element; it may <emph>not</emph> be used  within 
paragraphs. The <gi tei="yes">seg</gi> element, by contrast, may appear only
within and not between paragraphs (or anonymous block elements).<eg><![CDATA[<div1 type='book' n='Gen'><head>Das Erste Buch Mose.</head>
<div2 type='chapter' n='1'>
<p>
<seg n='1'>Am Anfang schuff Gott Himel vnd Erden.</seg>
<seg n='2'>Vnd die Erde war w&uuml;st vnd leer / vnd es war
finster auff der Tieffe / Vnd der Geist Gottes schwebet auff
dem Wasser.</seg>
</p>
<p>
<seg n='3'>Vnd Gott sprach / Es werde Liecht / Vnd es ward
Liecht.</seg>
<!-- ... -->]]></eg><!--* Martin Luther [tr].  Die gantze Heilige Schrifft Deudsch.
Wittenberg 1545.  Letzte zu Luthers Lebzeiten erchienene Ausgabe, hsg.
Hans Volz unter Mitarbeit von Heinz Blanke. Textredaktion Friedrich Kur.
M&uuml;nchen:  Rogner & Bernhard, 1972. *--></p><p>The <gi tei="yes">ab</gi> element is also useful for marking dramatic speeches
when it is not clear whether the speech is to be regarded as prose or
verse.  If, for example, am encoder does not wish to express an opinion
as to whether the opening lines of Shakespeare's 
<title>The Tempest</title> are to be
regarded as prose or as verse, they might be tagged as follows:
<eg><![CDATA[<div1 type=act n='I'> <div2 type=scene n='1'> 
<head rend=italic>Actus primus, Scena prima.</head> 
<stage type=setting rend=italic> A tempestuous noise of Thunder and Lightning heard:  Enter a Ship-master, and a Boteswaine.</stage>
<sp><speaker>Master.</speaker>
<ab>Bote-swaine.</ab></sp> 
<sp><speaker>Botes.</speaker>
<ab>Heere Master: What cheere?</ab></sp> 
<sp><speaker>Mast.</speaker>
<ab> Good: Speake to th' Mariners: fall too't, yarely, or 
we run our selues a ground, bestirre, bestirre. 
<stage type=move>Exit.</stage></ab></sp> 
<stage type=move>Enter Mariners.</stage> 
<sp><speaker>Botes.</speaker> 
<ab>Heigh my hearts, cheerely, cheerely my harts: 
yare, yare: Take in the toppe-sale: Tend to th' Masters 
whistle: Blow till thou burst thy winde, if roome e-nough.</ab></sp>   ]]></eg>  See further section  6.11.2, "Core Tags for Drama," on p. 212,
and section 10.2.4, "Speech Contents," on p. 285).</p><p>These elements are formally defined as follows:
 
<dtdFrag id="DSASA" n="Blocks, Segments and Anchors"><tagDecl tagDoc="ANCHOR"/><tagDecl tagDoc="SEG"/><tagDecl tagDoc="ANONB"/></dtdFrag>
 <?tei:EOF p2sase.odd ??>
<?tei:SOF p2sacs.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sacs.odd,v $
    * Revision 1.10  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.9  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.8  1994/04/08  00:00:53  msmcq
    * add figure for Comenius
    * 
    * Revision 1.7  1994/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.6  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.5  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.3  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 94-04-08 : MSM : correct tagging slip in figure element (comenius) --><!-- 94-04-07 : MSM : add figure for Comenius                 --><!-- 94-03-26 : MSM : typos from HG, DB, SJ                   --><!-- 94-03-26 : MSM : disambiguate TERM, Q (> code, ident...) --><!-- 4 feb: LB moved anchor out (to sase); revised parallel  --><!--    text example considerably --><!-- 19 dec 93 : LB change name of classdoc ANA -> cllink --><!-- 93-09-15 : MSM : minor SGML cleanup                      --><!-- 93-07-21 : DTL : change argTypes= to targFunc= passim    --><!--                  remove objection to < xptr> inside      --><!--                   < linkGrp>                             --><!-- 93-07-13 : DTL : change title to "Correspondence"        --><!--                  introduce < anchor> per Eynsham discussion --><!--                   to serve as "pure point" tag           --><!--                  use corresp= as linking attribute for   --><!--                   correspondence                         --><!--                  use < link> as linking element for      --><!--                   correspondence                         --><!--                  create subsection for alignment (SAcsal) --><!--                  distinguish correspondence from alignment --><!--                   by attribute on < linkGrp>             --><!--                  use alignment example from Gale&Church93 --><!--                   instead of Biblical passage            --><!--                  Comenius example attached to SAcsal     --><!--                  < s> changed to < seg>, < corresp> changed  --><!--                   to < link> in that example             --><!-- 93-01-27 : MSM : omit domains attribute from examples    --><!-- 93-01-26 : MSM : changes for publication                 --><!-- 92-12-23 : MSM : strip header                            --><!-- Date: Wed, 23 Dec 1992 14:24:12 +0000                    --><!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- Subject: sacs.odd (3 of 9)                               --><!-- 22 Dec : added discussion and eg of csp; revised         --><!-- John 1.1 example; added Comenius eg                      --><!-- 21 Dec 92: change ref to ptr or xptr; align to corresp   --><!--            (pro tem)                                     --><!-- 15 Dec 92 : LB : very light fiddling with egs; change ids --><!-- 24 Jul 92 :  DTL : Add material on < web>, < link>.      --><!--                    Elaborate on alternative csp= markup. --><!--                    Make other minor changes.             --><!-- 21 Jul 92 :  DTL : Make minor corrections.               --><!-- 15 Jul 92 :  DTL : Add < analysis> tags.                 --><!-- 14 Jul 92 :  DTL : Correct ODD tagging.                  --><!-- 03 Jul 92 :  DTL : Make minor changes, add DTDFRAGs.     --><!-- 02 Jul 92 :  DTL : Complete first draft, including       --><!-- TAGDOCs for < alignGrp> and < align>, and an elaborate   --><!-- parallel text example.                                   --><!-- Changes from ver 1.14 of LING DTD:  < align.grp>         --><!-- becomes < alignGrp>; < align> defined as an empty        --><!-- element; corresp= becomes csp=; target= ON < align>      --><!-- becomes targets=; type= on < align> and < alignGrp>      --><!-- becomes how=; domains= added to ATTLIST of < alignGrp>   --><!-- defined as IDREFS and optional; =centre and =center on   --><!-- how= replaced by =middle; =chunks replaced by =whole.    -->
 </p></div2><div2 id="SACS" name="subsection" ref="Y"><head>Correspondence and Alignment</head><p>In this section we introduce the notions of
<term>correspondence</term>, expressed by the <att tei="yes">corresp</att>
attribute, and of <term>alignment</term>, which is a special kind of
correspondence involving an ordered set of correspondences.  Both cases
may be represented using the <gi tei="yes">link</gi> and <gi tei="yes">linkGrp</gi> elements
introduced in section <xref target="SAPT"/>.  We also discuss the special
case of alignment in time or <term>synchronization</term>, for which
special purpose elements are proposed in section <xref target="SASY"/>.
 </p><div3 id="SACS1" name="subsection" ref="Y"><head>Correspondence</head><p>A common problem in text analysis is to determine correspondences
between two or more parts of a single document, or between places in
different documents.  Provided that SGML elements are available to
represent the parts or places to be linked, then the global linking
attribute <att tei="yes">corresp</att> may be used to encode such correspondence,
once it has been identified.
 
<adList classDoc="CLLINK" atts="corresp"/>
 
This is one of the attributes made available by the mechanism described
in the introduction to this chapter (<xref target="SA"/>).  Correspondence
can also be expressed by means of the <gi tei="yes">link</gi> element introduced
in section <xref target="SAPT"/>.
 </p><p>Where the correspondence is between <emph>spans</emph>, the
<gi tei="yes">seg</gi> element should be used, if no other element is available.
Where the correspondence is between <emph>points</emph>, the
<gi tei="yes">anchor</gi> element should be used, if no other element is
available.
 </p><p>The use of the <att tei="yes">corresp</att> attribute with spans of content is
illustrated by the following example:
 
<eg><![CDATA[<title id=SHIRLEY>Shirley</title>, which made
its Friday night debut only a month ago, was
not listed on <name id=NBC>NBC</name>'s new schedule,
although <seg id=NETWORK corresp=nbc>the network</seg>
says <seg id=SHOW corresp=shirley>the show</seg>
still is being considered.]]></eg><!-- from G Leech. --><!-- commas after 'Shirley' and 'ago' added conjecturally by  --><!-- msm after consultation with lb.                          -->
 
Here the anaphoric phrases <cited>the network</cited> and <cited>the
show</cited> have been associated directly with the elements to which
they refer by means of <att tei="yes">corresp</att> attributes.  This mechanism is
simple to apply, but has the drawback that it is not possible to specify
more exactly what kind of correspondence is intended.  Where this
attribute is used, therefore, encoders are encouraged to specify their
intent in the associated encoding declarations in the TEI Header.
 </p><p>Essentially, what the <att tei="yes">corresp</att> attribute does is to specify
that the element that has the attribute and the element(s) the attribute
points to are doubly linked.  <note source="auth" place="foot" anchored="Y">The <att tei="yes">corresp</att>
attribute is thus distinct from the <att tei="yes">target</att> attribute in that
it is understood to create a double, rather than a single, link.  It is
also distinct from the <att tei="yes">targets</att> attribute in that the latter
lists all the identifiers of the elements that are doubly linked,
whereas the <att tei="yes">corresp</att> doubly links the element that bears the
attribute with the element(s) that make up the value of the
attribute.</note> Therefore, we can also use the <gi tei="yes">link</gi> and
<gi tei="yes">linkGrp</gi> elements defined in section <xref target="SAPT"/> to
indicate correspondence among elements.  Moreover, the use of these
elements provides a convenient place to indicate what kind of
correspondence is intended as in the following retagging of the
preceding example.
 
<eg><![CDATA[<title id=SHIRLEY>Shirley</title>, which made
its Friday night debut only a month ago, was not
listed on <name id=NBC>NBC</name>'s new schedule,
although <seg id=NETWORK>the network</seg> says
<seg id=SHOW>the show</seg> still is being considered.
<!-- ... -->
<linkGrp type='anaphoric link'
        targFunc='antecedent anaphor' targOrder=Y>
  <link targType='title seg' targets='shirley show'>
  <link targType='name seg' targets='nbc network'>
</linkGrp>]]></eg>
 </p><p>In the following example, we use exactly the same mechanism to
express a correspondence amongst the anchors introduced following the
fifth word after <cited>English</cited> in a text:
 
<eg><![CDATA[ 
English language.  Except for not very<anchor id=ENG1>
<!-- ... -->
English at all at the time<anchor id=ENG2>
<!-- ... -->
English was still full of flaws<anchor id=ENG3>
<!-- ... -->
English.  This was revised by young<anchor id=ENG4>
 
<linkGrp type='five-word collocates'
         targType='anchor anchor'
         targOrder=N>
  <link type='collocates of ENGLISH' targets='eng1 eng2 eng3 eng4'>
  <!-- ... -->
</linkGrp>]]></eg>
 </p></div3><div3 id="SACSAL" name="subsection" ref="Y"><head>Alignment of Parallel Texts</head><!-- Changes made by LB:                                      --><!-- Simplified example by using segs for alignment           --><!--   rather than anchors;                                   --><!-- corrected erroneous alignment in last eg.                --><!-- Removed repetitious examples.                            --><!-- Revised introduction slightly.                           --><p>One very important application area for the alignment of parallel
texts is multilingual corpora.  Consider, for example, the need to align
<soCalled>translation pairs</soCalled> of sentences drawn from a corpus
such as the Canadian Hansard, in which each sentence is given in both
English and French.
 <!-- William A. Gale and Kenneth W. Church, "Program for      --><!-- aligning sentences in bilingual corpora".                --><!-- Computational Linguistics 19, 75-102, 1993 (ex appears   --><!-- on p76, from Canadian Hansards)                          -->
 
Concerning this problem, Gale and Church write:<note source="auth" place="display" anchored="Y">See
<citation><author>William A. Gale and Kenneth W. Church</author>,
<title.p>Program for aligning sentences in bilingual corpora</title.p>,
<title>Computational Linguistics</title> 19 (1993):  75-102</citation>,
from which the example in the text is taken.</note>
 
<q rend="display">Most English sentences match exactly one
French sentence, but it is possible for an English sentence
to match two or more French sentences.  The first two
English sentences [in the example below] illustrate a
particularly hard case where two English sentences align to
two French sentences.  No smaller alignments are possible
because the clause <q>...sales...were higher...</q> in the
first English sentence corresponds to (part of) the second
French sentence.  The next two alignments ... illustrate the
more typical case where one English sentence aligns with
exactly one French sentence.  The final alignment matches
two English sentences to a single French sentence.  These
alignments [which were produced by a computer program]
agreed with the results produced by a human judge.</q>
 </p><p>The alignment produced by Gale and Church's program can be expressed
in four different ways.  The encoder must first decide whether to
represent the alignment in terms of points within each text (using the
<gi tei="yes">anchor</gi> element) or in terms of whole stretches of text, using
the <gi tei="yes">seg</gi> element.  To some extent the choice will depend on the
process by which the software works out where alignment occurs, and the
intention of the encoder.  Secondly, the encoder may elect to represent
the actual encoding using either <att tei="yes">corresp</att> attributes attached
to the individual <gi tei="yes">anchor</gi> or <gi tei="yes">seg</gi> elements, or using a
free standing <gi tei="yes">linkGrp</gi> element.
 </p><p>We present first a solution using <gi tei="yes">anchor</gi> elements bearing
only <att tei="yes">corresp</att> attributes:
 
<eg><![CDATA[<text><body> 
<div1 id=E lang=EN>
<p><anchor id=EA1 corresp=FA1>According to our survey, 1988
sales of mineral water and soft drinks were much higher than
in 1987, reflecting the growing popularity of these
products.  Cola drink manufacturers in particular achieved
above-average growth rates.  <anchor id=EA2 corresp=FA2>The
higher turnover was largely due to an increase in the sales
volume.  <anchor id=EA3 corresp=FA3>Employment and
investment levels also climbed.  <anchor id=EA4
corresp=FA4>Following a two-year transitional period, the
new Foodstuffs Ordinance for Mineral Water came into effect
on April 1, 1988.  Specifically, it contains more stringent
requirements regarding quality consistency and purity
guarantees.  </div1>
<!-- ... -->
<div1 id=F lang=FR>
<p><anchor id=FA1 corresp=EA1>Quant aux eaux min&eacute;rales
et aux limonades, elles rencontrent toujours plus
d'adeptes.  En effet, notre sondage fait ressortir des
ventes nettement sup&eacute;rieures &agrave; celles de 1987,
pour les boissons &agrave; base de cola notamment.  <anchor
id=FA2 corresp=EA2>La progression des chiffres d'affaires
r&eacute;sulte en grande partie de l'accroissement du volume
des ventes.  <anchor id=FA3 corresp=EA3>L'emploi et les
investissements ont &eacute;galement augment&eacute;.
<anchor id=FA4 corresp=EA4>La nouvelle ordonnance
f&eacute;d&eacute;rale sur les denr&eacute;es alimentaires
concernant entre autres les eaux min&eacute;rales,
entr&eacute;e en vigueur le 1er avril 1988 apr&egrave;s une
p&eacute;riode transitoire de deux ans, exige surtout une
plus grande constance dans la qualit&eacute; et une garantie
de la puret&eacute;.  </div1></body></text>]]></eg>
 </p><p>There is no requirement that the <att tei="yes">corresp</att> attribute be
specified in both English and French texts, since (as noted above) this
attribute is defined as representing a mutual association.  However, it
may simplify processing to do so, and also avoids giving the impression
that the English is translating the French, or vice versa.  More
seriously, this encoding does not make explicit the fact that it is in
fact the entire stretch of text between the anchors which is being
aligned, not simply the points themselves.  If for example one text
contained material omitted from the other, this approach would not be
appropriate.
 </p><p>We now present the same passage using the alternative
<gi tei="yes">linkGrp</gi> mechanism and marking explicitly the segments which
have been aligned:
 
<eg><![CDATA[<div1 id=E lang=EN>
<p><seg id=E1>According to our survey, 1988 sales of mineral
water and soft drinks were much higher than in 1987,
reflecting the growing popularity of these products.  Cola
drink manufacturers in particular achieved above-average
growth rates.</seg>
<seg id=E2>The higher turnover was largely due to an
increase in the sales volume.</seg>
<seg id=E3>Employment and investment levels also
climbed.</seg>
<seg id=E4>Following a two-year transitional period, the new
Foodstuffs Ordinance for Mineral Water came into effect on
April 1, 1988.  Specifically, it contains more stringent
requirements regarding quality consistency and purity
guarantees.</seg>
</div1>
<!-- ... -->
<div1 id=F lang=FR>
<p><seg id=F1>Quant aux eaux min&eacute;rales et aux limonades,
elles rencontrent toujours plus d'adeptes.  En effet, notre
sondage fait ressortir des ventes nettement
sup&eacute;rieures &agrave; celles de 1987, pour les
boissons &agrave; base de cola notamment.</seg>
<seg id=F2>La progression des chiffres d'affaires
r&eacute;sulte en grande partie de l'accroissement du volume
des ventes.</seg>
<seg id=F3>L'emploi et les investissements ont
&eacute;galement augment&eacute;.</seg>
<seg id=F4>La nouvelle ordonnance f&eacute;d&eacute;rale sur
les denr&eacute;es alimentaires concernant entre autres les
eaux min&eacute;rales, entr&eacute;e en vigueur le 1er avril
1988 apr&egrave;s une p&eacute;riode transitoire de deux
ans, exige surtout une plus grande constance dans la
qualit&eacute; et une garantie de la puret&eacute;.</seg>
</div1>
<!-- ... -->
<linkGrp type=alignment
         domains='E F'
  <link targets='E1 F1'>
  <link targets='E2 F2'>
  <link targets='E3 F3'>
  <link targets='E4 F4'>
</linkGrp>]]></eg>
 </p><p>Note that use of the <gi tei="yes">ab</gi> element allows us to mark up the
orthographic sentences in both languages independently of the alignment:
the first translation pair in this example might be marked up as
follows:
 
<eg><![CDATA[<div1 id=E lang=EN>
<ab id=E1>
  <s>According to our survey, 1988 sales of mineral water and soft
  drinks were much higher than in 1987, reflecting the growing popularity
   of these products.</s>
  <s>Cola drink manufacturers in particular achieved above-average
   growth rates.</s>
</ab>
 
<!-- ... -->
 
<div1 id=F lang=FR>
<ab id=F1>
  <s id=FS1>Quant aux eaux min&eacute;rales et aux limonades, elles
   rencontrent toujours plus d'adeptes.</s>
  <s id=FS2>En effet, notre sondage fait ressortir des ventes nettement
   sup&eacute;rieures &agrave; celles de 1987, pour les boissons &agrave;
   base de cola notamment. </s>
</ab>
 ]]></eg>
 <!-- Continuing previous subsection, rather than introducing new one --><!-- <div3 id=SACSXA><head>Alignment Using External Pointers</head> -->
 </p></div3><div3 id="SACSXA" name="subsection" ref="Y"><head>A Three-way Alignment</head><p>The preceding encoding of the alignment of parallel passages from two
texts requires that those texts and the alignment all be part of the
same SGML document.  If the texts are in separate documents, then
additional <gi tei="yes">xptr</gi> elements must be supplied, as discussed in
section <xref target="SAXR"/>.  These external pointers may appear anywhere
within the document, but if they are created solely for use in encoding
links, they may for convenience be grouped within the <gi tei="yes">linkGrp</gi>
(or other grouping element that uses them for linking).
 </p><p>To demonstrate this facility, we consider how we might encode the
alignments in an extract from Comenius' <title>Orbis Sensualium
Pictus</title>.
<figure id="COMENIUS" rend="float full page"><figDesc>The figure shows the page from the <title>Orbis pictus</title>
of Comenius which is discussed in the text.</figDesc></figure>
Each topic covered in this work has three parts:  a
picture, a prose text in Latin describing the topic, and a
carefully-aligned translation of the Latin into English, German or some
other vernacular.  Key terms in the two texts are typographically
distinct, and are linked to the picture by numbers, which appear in the
two texts and within the picture as well.<note source="auth" place="display" anchored="Y"><p>Our example uses the
English translation of Charles Hoole (1659), and is taken from
<citation><editor>John E. Sadler, ed.</editor>, <title>John Amos
Comenius Orbis Pictus:  a facsimile of the first English edition of
1659</title> (Oxford:  Oxford University Press, 1968) (The Juvenile
Library).</citation></p></note>
 </p><p>First, we present the text portions.  The English and Latin portions
have been encoded as distinct <gi tei="yes">div</gi> elements.  Identifiers have
been attached to each typographic line, but no other encoding added, to
simplify the example.
 <!-- S tag changed to SEG -DTL  -->
 
<eg><![CDATA[<!-- English text -->
 
<div id=E98 lang=EN><head>The Study</head>
<p><seg id=E9801>The Study</seg>
<seg id=E9802>is a place</seg>
<seg id=E9803>where a Student,</seg>
<seg id=E9804>a part from men,</seg>
<seg id=E9805>sitteth alone,</seg>
<seg id=E9806>addicted to his Studies,</seg>
<seg id=E9807>whilst he readeth</seg>
<seg id=E9808>Books,</seg>
<!-- ... -->
</div>
 
<!-- Latin text -->
 
<div id=L98 lang=LA><head>Mus&eacute;um</head>
<p><seg id=L9801>Museum</seg>
<seg id=L9802>est locus</seg>
<seg id=L9803>ubi Studiosus,</seg>
<seg id=L9804>secretus ab hominibus,</seg>
<seg id=L9805>solus sedet,</seg>
<seg id=L9806>Studiis deditus,</seg>
<seg id=L9807>dum lectitat</seg>
<seg id=L9808>Libros,</seg>
<!-- ... -->
</div>]]></eg>
 </p><p>Next we assume that we have stored a digitized image of the picture
itself in some external entity we will call <ident rend="noindex" tei="yes" type="ge">com98</ident> (for further discussion of the handling of
external images and graphics, see section <xref target="FTGRA"/>).  We
further assume that we can address portions of this image as a
two-dimensional co-ordinate space.  The <code tei="yes" type="teikw">SPACE</code>
location method of the <gi tei="yes">xptr</gi> element (discussed in section <xref target="COXR"/> above) can now be used to point to the whole picture and to
two portions of it, one containing the picture of a student and the
other of a book, as follows:
 
<eg><![CDATA[<xptr n='1' id=P981 doc=com98>
<xptr n='2' id=P982 doc=com98 from='space (2d) (75 5) (133 75)'>
<xptr n='3' id=P983 doc=com98 from='space (2d) (55 42) (90 60)'>]]></eg><!-- Redone from                                              --><!-- < xptr n='1' id=X981 doc=com98 >                         --><!-- < xptr n='2' id=X982 doc=com98 from='space (2d) (9 2) (15 10)' > --><!-- < xptr n='3' id=X983 doc=com98 from='space (2d) (8 6) (10 9)'  > --><!-- New values are measured in mm on Lou's fax to me.   --><!-- Original values don't match proportions of picture. -->
 
Note that each external pointer has its own unique identifier, in
addition to the <att tei="yes">n</att> attribute, which last holds the visible
label (or <soCalled>explainer</soCalled>) used for this image portion in
the original.
 </p><p>As printed, the text exhibits three kinds of alignment.
 
<list type="ordered"><item n="1">The English and Latin portions are printed in two parallel
columns, with corresponding phrases, (represented above by <gi tei="yes">seg</gi>
elements), more or less next to each other.
 </item><item n="2">Particular words or phrases are marked as terms in the two
languages by a change of rendition:  the English text, which otherwise
uses black letter type throughout, has the words <cited>The
Study</cited>, <cited>a Student</cited>, <cited>Studies</cited>, and
<cited>Books</cited> in a roman font; in the Latin text, which is
printed in roman, the corresponding words (<cited>Museum</cited>,
<cited>Studiosus</cited>, <cited>Studiis</cited>, and
<cited>Libros</cited>) are all in italic.
 </item><item n="3">Numbered labels appear within the text portions, linking
keywords to each other and to sections of the picture.  These labels,
which have been left out of the above encoding, are attached to the
first third and last segment in each language quoted below, and also
appear (rather indistinctly) within the picture itself.  If it is
desired to transcribe them in the text, they might be encoded using as
<gi tei="yes">ref</gi> elements, <gi tei="yes">anchor</gi> elements, or <gi tei="yes">xptr</gi>s to
the picture; the number itself would be transcribed as the value of the
<att tei="yes">n</att> attribute (or as the content of the <gi tei="yes">ref</gi>).
 </item></list>
 </p><p>The first kind of alignment might be represented by using the
<att tei="yes">corresp</att> attribute on the <gi tei="yes">seg</gi> element.  The second
kind might be represented by using the <gi tei="yes">gloss</gi> and <gi tei="yes">term</gi>
mechanism described in section <xref target="COHQU"/>.  The third kind of
alignment might be represented using pointers embedded within the texts,
although this would involve some duplication.  We choose however to use
the <gi tei="yes">link</gi> element, since this provides an efficient way of
representing the three-way alignment between English, Latin and picture
without redundancy.
 
<eg><![CDATA[<linkGrp type=alignment>
  <link targets='E9801 L9801 p981'>
  <link targets='E9802 L9802     '>
  <link targets='E9803 L9803 p982'>
  <link targets='E9804 L9804     '>
  <link targets='E9805 L9805     '>
  <link targets='E9806 L9806     '>
  <link targets='E9807 L9807     '>
  <link targets='E9808 L9808 p983'>
</linkGrp>]]></eg>
 </p><p>This map, of course, only aligns whole segments and image portions,
since these are the only parts of our encoding which bear identifiers
and can therefore be pointed to.  To add to it the alignment between the
typographically distinct words mentioned above, new elements must be
defined, either within the text itself or externally by using the
extended pointer mechanism.  Encoding these word pairs as <gi tei="yes">term</gi>
and <gi tei="yes">gloss</gi>, although intuitively obvious, requires a non-trivial
decision as to whether the Latin text is glossing the English, or
vice-versa.  Tagging all the marked words as <gi tei="yes">term</gi> avoids the
difficult decision, but might be thought by some encoders to convey the
wrong information about the words in question.  Simply tagging them as
additional embedded <gi tei="yes">seg</gi> elements with identifiers that can be
aligned like the others is also a possibility.  All of these require the
addition of further markup to the text.  This may pose no problems, or
it may be infeasible (e.g. if the text is held on a read-only medium).
If it is not feasible to add more markup to the original text, the
extended pointer mechanism is likely to be the best choice.  For
example, to indicate that the words <cited>Studies</cited> and
<cited>Studiis</cited> correspond, two external pointers might be
defined and aligned as follows:
 
<eg><![CDATA[        <xptr id=XT981  from='id (s E9806) token (4)'>
        <xptr id=XT982  from='id (s L9806) token (1)'>
        <link targets='xt981 xt982'>]]></eg>
 








<?tei:EOF p2sacs.odd ??>
<?tei:SOF p2sasy.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sasy.odd,v $
    * Revision 1.7  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.6  94/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.5  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.4  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.2  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 94-03-27 : MSM : corrections from SJ                     --><!-- 94-03-26 : MSM : disambiguate TERM, Q (> code, ident...) --><!-- 7 feb: tidy up bnc example a bit; combine with sasymp   --><!-- 19 dec 93 : LB change name of classdoc ANA -> cllink --><!-- 93-09-15 : MSM : simple SGML cleanup                     --><!-- 93-07-22 : DTL : exceedingly minor changes               --><!-- 93-07-21 : DTL : change argTypes= to targFunc= passim    --><!--                  supply missing xref to TS chapter       --><!-- 93-07-13 : DTL : complete draft, use ex from LB's        --><!--                  TEI-TECH posting of a BNC spoken text   --><!--            define synch= for temporal correspondence     --><!--            use LINK and LINKGRP for temporal alignment   --><!--            recast old LOC and ALIGN tags as WHEN and     --><!--            WHENGRP tags, but remove pointing ability from --><!--            WHEN.  WHEN tags can only be pointed at or    --><!--            linked.  Mildly revise attributes from the    --><!--            ones given for LOC and ALIGN in TS chapter.   --><!--            See TAGDOC for details.                       -->
 </p></div3></div2><div2 id="SASY" name="subsection" ref="Y"><head>Synchronization</head><p>In the previous section we discussed two particular kinds of
alignment:  alignment of parallel texts in different languages; and
alignment of texts and portions of an image.  In this section we address
another specialized form of alignment:  synchronization.  The need to
mark the relative positions of text components with respect to time
arises most naturally and frequently in transcribed spoken texts, but it
may arise in any text in which quoted speech occurs, or events are
described within a time frame.  The methods described here are also
generalizable for other kinds of alignment (for example, alignment of
text elements with respect to space), and may thus be regarded as
providing a simplified version of the HyTime system of <term>finite
space co-ordinates</term>.
 </p><div3 id="SASYNC" name="subsection" ref="Y"><head>Aligning Synchronous Events
 </head><p>To mark synchronous elements, the <att tei="yes">synch</att> attribute, which
is one of the linking attributes that are available for all text
elements, may be used.
 
<adList classDoc="CLLINK" atts="synch"/>
 
Alternatively, the <gi tei="yes">link</gi> and <gi tei="yes">linkGrp</gi> elements may be
used to make explicit the fact that the synchronous elements are
aligned.
 </p><p>To illustrate the use of these mechanisms for marking synchrony,
consider the following representation of a spoken text:
 <!-- From BNC, via LB, retranscribed without SGML markup -->
<eg><![CDATA[B:   The first time in twenty five years, we've cooked Christmas
     (unclear) for a blooming great load of people.
A: So you're [1] (unclear) [2]
B: [1] It will be [2] nice in a way, but, [3] be strange. [4]
A: [3] Yeah [4], yeah, cos it, it's [5] the [6]
B: [5] not [6]]]>
 </eg>
 </p><p>This representation uses numbers in brackets to mark the points at
which speakers overlap each other.  For example, the <cited>[1]</cited>
in A's first speech is to be understood as coinciding with the
<cited>[1]</cited> in B's second speech.<note source="auth" place="display" anchored="Y">This sample is taken from
a conversation collected and transcribed for the British National
Corpus.</note>
 </p><p>To encode this we use the base tag set for spoken texts, described in
chapter <xref target="TS"/>, together with the additional tag set described
in the present chapter.  First, we transcribe this text, marking the
synchronous points with <gi tei="yes">anchor</gi> elements, and providing a
<att tei="yes">synch</att> attribute on one of each of the pairs of synchronous
anchors.  As noted in the example given above (section <xref target="SACSAL"/>), correspondence, and hence synchrony, is a symmetric
relation; therefore the attribute need only be specified on one of the
pairs of synchronous anchors.
 
<eg><![CDATA[<text><body>
<div id=D1>
<!-- ... -->
<u id=U3A who=A>So you're <anchor id=T1A synch=t1b><unclear>
          <anchor id=T2A synch=t2b></u>
<u id=U3B who=B> <anchor id=T1B>It will be <anchor id=T2B>
          nice in a way, but, <anchor id=T3B>
          be strange.<anchor id=T4B></u>
<u id=U4A who=A>
          <anchor id=T3A synch=t3b>Yeah
          <anchor id=T4A synch=t4b>, yeah, cos it, its
          <anchor id=T5A synch=t5b>the
          <anchor id=T6A synch=t6b></u>
<u id=U4B who=B>
          <anchor id=T5B>not<anchor id=T6B>
</u>
</body></text>]]></eg>
 </p><p>Next, we encode the same example using <gi tei="yes">link</gi> and
<gi tei="yes">linkGrp</gi> elements to make the temporal alignment explicit; the
<att tei="yes">id</att> attributes are provided for the <gi tei="yes">link</gi> and
<gi tei="yes">linkGrp</gi> elements for a reason that is given in the next
section, <xref target="SASYMP"/>. In this example, a <gi tei="yes">back</gi>
element has been used to enclose the <gi tei="yes">linkGrp</gi> element, but the links
may be located anywhere the encoder finds convenient.
 
<eg><![CDATA[<text><body><div id=D1>
<u id=U2B who=B>The first time in twenty five years,
  we've cooked Christmas <unclear> for a blooming great
  load of people.</u>
<u id=U3A who=A>So you're
  <anchor id=T1A><unclear><anchor id=T2A></u>
<u id=U3B who=B>
  <anchor id=T1B>It will be <anchor id=T2B>nice in a way,
  but, <anchor id=T3B>be strange <anchor id=T4B></u>
<u id=U4A who=A>
  <anchor id=T3A>Yeah<anchor id=T4A>, yeah, cos it, it's
<anchor id=T5A>the<anchor id=T6A></u>
<u id=U4B who=B><anchor id=T5B>not<anchor id=T6B></u>
</div>
<!-- ... -->
</body><back>
<linkGrp id=LG1 type='synchronous alignment'
         domains='d1 d1'
         targFunc='speaker.A speaker.B'>
  <link id=L1 targets='t1a t1b'>
  <link id=L2 targets='t2a t2b'>
  <link id=L3 targets='t3a t3b'>
  <link id=L4 targets='t4a t4b'>
  <link id=L5 targets='t5a t5b'>
  <link id=L6 targets='t6a t6b'>
</linkGrp>
</back></text>]]></eg>
 </p><p>As with other forms of alignment, synchronization may be expressed
between stretches of speech as well as between points.  When complete
utterances are synchronous, for example, if one person says
<cited>What?</cited> and another <cited>No!</cited> at the same time,
that can be represented without <gi tei="yes">anchor</gi> elements as follows.
 
<eg><![CDATA[<u id=U1 who=A synch=u2>What?</u>
<u id=U2 who=B>No!</u>]]></eg>
 </p><p>A simple way of expressing <term>overlap</term> (where one speaker
starts speaking before another has finished) is thus to use the
<gi tei="yes">seg</gi> element to encode the overlapping portions of speech.  For
example,
 
<eg><![CDATA[<u who=A> So you're <unclear synch=B1></u>
<u who=B><seg id=B1> It will be </seg> nice in a way, but,
         <seg synch=A3> be strange. </seg></u>
<u who=A><seg id=A3> Yeah </seg>, yeah, cos it,
         its <seg synch=B2> the </seg></u>
<u who=B id=B2> not </u>]]></eg>
 
Note in this encoding how synchronization has been effected between an
empty <gi tei="yes">unclear</gi> element and a <gi tei="yes">seg</gi>, and between an entire
<gi tei="yes">u</gi> element and another <gi tei="yes">seg</gi>, using the <att tei="yes">synch</att>
attribute.  Alternatively, a <gi tei="yes">linkGrp</gi> could be used in the same
way as above.
 </p></div3><div3 id="SASYMP" name="subsection" ref="Y"><head>Placing Synchronous Events in Time</head><p>A synchronous alignment specifies which points in a spoken text occur
at the same time, and the order in which they occur, but does not say at
what time those points actually occur.  If that information is available
to the encoder it can be represented by means of the <gi tei="yes">when</gi> and
<gi tei="yes">timeLine</gi> elements, whose description and attributes are the
following:
 <!-- WHEN = old LOC (but made empty, hence stripped of the    --><!-- ability to point; these elements only available to be    --><!-- pointed at or linked) TIMELINE = old ALIGN               -->
 
<tagList style="one-line"><tagDesc tagDoc="WHEN" atts="absolute interval unit since id"/><tagDesc tagDoc="TIMELINE" atts="origin interval unit"/></tagList>
 </p><p>Each <gi tei="yes">when</gi> element indicates a point in time, either directly
by means of the <att tei="yes">absolute</att> attribute, whose value is a string
which specifies a particular time, or indirectly by means of the
<att tei="yes">since</att> attribute, which points to another <gi tei="yes">when</gi>.  If
the <att tei="yes">since</att> is used, then the <att tei="yes">interval</att> and
<att tei="yes">unit</att> attributes should also be used to indicate the amount of
time that has elapsed since the time specified by the element pointed to
by the <att tei="yes">since</att> attribute; the value <code tei="yes" type="val">-1</code>
can be given to indicate that the interval is unknown.
 </p><p>If the <gi tei="yes">when</gi> elements are uniformly spaced in time, then the
<att tei="yes">interval</att> and <att tei="yes">unit</att> values need be given once in the
<gi tei="yes">timeLine</gi>, and not repeated in any of the <gi tei="yes">when</gi>
elements.  If the intervals vary, but the units are all the same, then
the <att tei="yes">unit</att> attribute alone can be given in the
<gi tei="yes">timeLine</gi> element, and the <att tei="yes">interval</att> attribute given
in the <gi tei="yes">when</gi> element.
 </p><p>The <att tei="yes">origin</att> attribute in the <gi tei="yes">timeLine</gi> element
points to a <gi tei="yes">when</gi> element which specifies the reference or
origin for the timings within the <gi tei="yes">timeLine</gi>; this must, of
course, specify its position in time absolutely.
 </p><p>The following <gi tei="yes">timeLine</gi> might be used to accompany the marked
up conversation shown in the preceding section:
 
<eg><![CDATA[<timeLine id=TL1 origin=w0 unit=centisecond>
  <when id=W0 absolute='sometime Monday morning before Christmas'
  <when id=W1 since=w0 interval="-1">
  <when id=W2 since=w1 interval="10">
  <when id=W3 since=w2 interval="20">
  <when id=W4 since=w3 interval="15">
  <when id=W5 since=w4 interval="25">
  <when id=W6 since=w5 interval="10">
  </timeLine>]]></eg>
 
The information in this <gi tei="yes">timeLine</gi> could now be linked to the
information in the <gi tei="yes">linkGrp</gi> which provides the temporal
alignment (synchronization) for the text, as follows:
 
<eg><![CDATA[<linkGrp type='temporal specification'
         targType='link when'
         targFunc='synch.points when'
         domains='lg1 tl1'>
  <link targets='l1 w1'>
  <link targets='l2 w2'>
  <link targets='l3 w3'>
  <link targets='l4 w4'>
  <link targets='l5 w5'>
  <link targets='l6 w6'>
  </linkGrp>]]></eg>
 </p><p>To avoid the need for two distinct link groups (one marking the
synchronization of anchors with each other, and the other marking their
alignment with points on the time line) it would be better to link the
<gi tei="yes">when</gi> elements with the synchronous points directly:
 
<eg><![CDATA[<linkGrp type='temporal specification'
         targType='anchor anchor when'
         targFunc='speaker.A speaker.B when'
         domains='d1 d1 tl1'>
  <link targets='t1a t1b w1'>
  <link targets='t2a t2b w2'>
  <link targets='t3a t3b w3'>
  <link targets='t4a t4b w4'>
  <link targets='t5a t5b w5'>
  <link targets='t6a t6b w6'>
  </linkGrp>]]></eg>
 </p><p>Finally, suppose that a digitized audio recording is also available.
The extended pointer syntax described in section <xref target="SAXR"/>
could be used to address positions on or portions of this recording
directly.  Assuming that <gi tei="yes">xptr</gi> elements with identifiers <code tei="yes" type="val">X1</code>, <code tei="yes" type="val">X2</code>, etc., have been defined to
do this, these identifiers could also be included as a fourth component
in each of the above <gi tei="yes">link</gi> elements, thus providing a
synchronized audio track to complement the transcribed text.
 <!-- but this is left to the reader as an exercise because I'm --><!-- getting bored with this example -->
 </p><p>For further discussion of this and related aspects of encoding
transcribed speech, refer to chapter <xref target="TS"/>.
 <!-- The <gi>when</gi> elements can also be pointed at by the --><!-- <att>start</att> and <att>end</att> attributes of the <term>timed --><!-- elements</term> described in section <xref target=TSBATI>. -->
 </p><p>The <gi tei="yes">when</gi> and <gi tei="yes">timeLine</gi> elements are defined as
follows:
 
<dtdFrag id="DSASYMP" n="Temporal specification"><tagDecl tagDoc="WHEN"/><tagDecl tagDoc="TIMELINE"/></dtdFrag><?tei:EOF p2sasy.odd ??>
<?tei:SOF p2saie.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2saie.odd,v $
    * Revision 1.6  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.5  94/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.4  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.3  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.2  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : typos from HG, DB, SJ                   --><!-- 94-03-26 : MSM : cosmetics (reformatting, white space)   --><!-- 7 feb: LB reinstated, revised                            --><!-- 93-09-15 : MSM : process TDL's changes                   --><!-- 93-07-08 : DTL : change intro to hide Orwell reference   --><!--                  add Gilbert ex                          --><!--                  move material on mobile div to SAat     --><!-- 93-07-06 : DTL : renumber to SAie; rename section        --><!--                  "Identical Elements and Virtual Copies" --><!--                  Eliminate < echo> tag. Add copyOf= att  --><!--                  change equiv= to sameAs=                --><!-- 30 Mar 93 : LB   : renumber to AI                        --><!-- 02 Aug 92 : DTL  : Change one cross reference.           --><!-- 24 Jul 92 : DTL  : Make minor changes.                   --><!-- 21 Jul 92 : DTL  : Add warning about use of < echo>.     --><!-- 19 Jul 92 : DTL  : Renumber sectn from p2.446 to p2.444. --><!--                    Complete first draft.                 --><!-- 16 Jul 92 : DTL  : Create tagList, dtdFrag, and TAGDOC.  -->
 </p></div3></div2><div2 id="SAIE" name="subsection" ref="Y"><head>Identical Elements and Virtual Copies</head><p>This section introduces the notion of a <term>virtual element</term>,
that is, an element which is not explicitly present in a text, but the
presence of which an application can infer from the encoding supplied.
In this section, we are concerned with virtual elements made by simply
cloning existing elements.  In the next section (<xref target="SAAG"/>), we
discuss virtual elements made by aggregating existing elements.
 </p><p>It is useful to be able to represent the fact that one element of
text is identical to others, for analytical purposes, or (especially if
the elements have lengthy content) to obviate the need to repeat the
content.  For example, consider the repetition of the <tag compl="full" tei="yes">date</tag>
element in the following material:
 <!-- removed <s> and rend  to simplify;  align date not s --><!-- Orwell, Nineteen-Eighty-Four  --><!-- diary recoded as Q, per msm   -->
<eg><![CDATA[<p>In small clumsy letters he wrote:
<q rend='centered italic' id=D1>
<date id=D840404>April 4th, 1984</date>.
</q></p>
<p>He sat back. A sense of complete helplessness had
descended upon him.
<!-- ... -->
<p>His small but childish handwriting straggled up
and down the page, shedding first its capital letters
and finally even its full stops:
<!-- ... -->
<q rend=italic id=D2>
<date>April 4th, 1984</date>. Last night to the flicks.
<!-- ... -->
</q></p>]]></eg>
 
Suppose now that we wish to encode the fact that the second
<gi tei="yes">date</gi> element above has identical content to the first.  The
<att tei="yes">sameAs</att> attribute is provided for this purpose.  Using it, we
can recode the last line of the above example as follows:
 <!-- To encode the identity of the content of the S-units --><!-- identified as <tag>s id=D1.1</tag> and <tag>s id=D1.2</tag>, --><!-- each occurrence of the repeated S-unit may be provided with --><!-- an <att>sameAs</att> attribute which points to the other, as --><!-- follows. -->
 
<eg><![CDATA[<!-- ... -->
<date sameAs=D840404>April 4th, 1984</date>. Last night to the flicks.
<!-- ... -->]]></eg>
 </p><p>The <att tei="yes">sameAs</att> attribute may be used to document the fact that
two elements have identical content.  It may be regarded as a special
kind of link.  It should only be attached to an element with identical
content to that it indicates, or to one the content of which clearly
designates it as a repetition, such as the word <cited>repeat</cited> or
<cited>bis</cited> in the representation of the chorus of a song, the
second time it is to be sung.
 <!-- , as in the following example: --><!-- example needed, if this is really feasible -->
 
The relation specified by the <att tei="yes">sameAs</att> attribute is symmetric:
if a chorus is repeated three times and each repetition bears a
<att tei="yes">sameAs</att> attribute indicating the first occurrence of the
element concerned, it is implied that each chorus is identical, and
there is no need for the first occurrence to specify any of its copies.
 <!-- all but one of --><!-- the <att>sameAs</att> attributes can be omitted without loss of --><!-- information. -->
 </p><p>The <att tei="yes">copyOf</att> attribute is used in a similar way to indicate
that the content of the element bearing it is identical to that of
another.  The difference is that the content is not itself repeated.
The effect of this attribute is thus to create a <term>virtual
copy</term> of the element indicated.
 <!-- of an element that is an exact repetition of another, the --><!-- content of one of those elements can be omitted, and the tag --><!-- provided with a <att>copyOf</att> attribute which points to --><!-- the element for which the content is provided.  We call the --><!-- element bearing the <att>copyOf</att> attribute a --><!-- <term>virtual copy</term> of the tag being pointed at. -->
 
Using this attribute, the repeated date in the first example above could
be recoded as follows:
 
<eg><![CDATA[<!-- ... -->
<date copyOf=D840404></date>]]></eg>
 </p><p>An application program should replace whatever is the actual content
of an element bearing a <att tei="yes">copyOf</att> attribute with the content of
the element specified by it.  If the content of the element specified
includes other elements, these will become embedded within the element
bearing the attribute.  Care must be taken to ensure that the document
is a legal SGML document both before and after this embedding takes
place.  If, for example, the element bearing a <att tei="yes">copyOf</att>
attribute requires a mandatory sub-component, then this component must
be present (though possibly empty), even though it will be replaced by
the content of the targetted element.
 <!-- killed this example. sorry, but it doesnt add anything --><!--    and kills trees --><!-- Samuel Beckett, Molloy, p125, 241 --><!-- The id= VALUES are made up; I do not know the actual     --><!-- number of paragraphs and S-units in the second chapter   --><!-- of Molloy!  -DTL                                         --><!-- <eg> --><!-- <![ CDATA [ --><!-- <p id=C2P1> --><!-- <s id=C2P1S1 sameAs=c2p731s100>It is midnight.</s> --><!-- <s id=C2P1S2 sameAs=c2p731s101>The rain is beating on the
windows.</s> --><!-- <s id=C2P1S3>I am calm.</s> --><!-- ... --><!-- <s id=C2P731S99>Then I went back into the house and wrote,</s> --><!-- <q type=written who=moran> --><!-- <s id=C2P731S100 sameAs=c2p1s1>It is midnight.</s> --><!-- <s id=C2P731S101 sameAs=c2p1s2>The rain is beating on the
windows.</s> --><!-- </q> --><!-- <s id=C2P731S102>It was not midnight.</s> --><!-- <s id=C2P731S103>It was not raining.</s> --><!--   --><!-- <p id=C2P1> --><!-- <s id=C2P1S1>It is midnight.</s> --><!-- <s id=C2P1S2>The rain is beating on the windows.</s> --><!-- <s id=C2P1S3>I am calm.</s> --><!-- ... --><!-- <s id=C2P731S99>Then I went back into the house and wrote,</s> --><!-- <q type=written who=moran> --><!-- <s id=C2P731S100 copyOf=c2p1s1></s> --><!-- <s id=C2P731S101 copyOf=c2p1s2></s> --><!-- </q> --><!-- <s id=C2P731S102>It was not midnight.</s> --><!-- <s id=C2P71S103>It was not raining.</s> --><!-- ]]> --><!-- </eg> -->
 </p><p>The following example demonstrates how the <att tei="yes">copyOf</att>
attribute may be used in conjunction with the <gi tei="yes">seg</gi> element to
highlight the differences between almost identical repetitions:
 <!-- W.S. Gilbert, "A more humane Mikado", The Mikado  -->
<eg><![CDATA[<sp who=Mikado>
<l>My <seg id=L1S>object all sublime</seg></l>
<l>I shall <seg id=L2S>achieve in time</seg>&dash;</l>
<l id=L3>To let
  <seg id=L3S>the punishment fit the crime</seg>,</l>
<l id=L4><seg copyOf=L3s></seg>;</l>
<l id=L5>And make each pris'ner pent</l>
<l id=L6>Unwillingly represent</l>
<l id=L7>A source
  <seg id=L7S>of innocent merriment</seg>,</l>
<l id=L8><seg copyOf=L7s></seg>!</l>
</sp>
<sp who=chorus>
<l>His <seg copyOf=L1s></seg></l>
<l>He will <seg copyOf=L2s></seg></l>
<l copyOf=L3></l>
<l copyOf=L4></l>
<l copyOf=L5></l>
<l copyOf=L6></l>
<l copyOf=L7></l>
<l copyOf=L8></l>
</sp>]]></eg>
 <!-- <p>If a virtual copy has an SGML content model which forbids --><!-- it to have empty content, it should be provided with legal --><!-- <soCalled>dummy</soCalled> content (e.g., a blank character, --><!-- if that is legal).  Application software should be designed --><!-- to ignore the content of any tag with a legal --><!-- <att>copyOf</att> attribute value, and to assign it the --><!-- content of its source. -->
 </p><p>For further examples of the use of this attribute, see chapters <xref target="GD"/> and <xref target="FS"/>, where it is used to reduce the
complexity of formal analytic representations of structure.<?tei:EOF p2saie.odd ??>
<?tei:SOF p2saag.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: p2saag.odd,v $
    * Revision 1.9  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.8  98/02/01  16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    * 
    * Revision 1.7  94/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.6  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.5  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.3  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : typos from HG, DB, SJ                   --><!-- 94-03-26 : MSM : disambiguate TERM, Q (> code, ident...) --><!-- 94-03-15 : MSM : revision of zuigan as per J Lavagnino   --><!-- 5 feb : LB: much tidying up and clarification; took      --><!--             attribs and e.g.s from tagdoc.               --><!-- 19 dec 93 : LB change name of classdoc ANA -> cllink     --><!-- 93-09-15 : MSM : process TDL's revisions                 --><!-- 93-07-21 : DTL : change argTypes= to targFunc= passim    --><!--                  change certain S to SEG in Orwell ex    --><!--                  remove type= from S-units in Fisher,    --><!--                      Orwell exx                          --><!-- 93-07-12 : DTL : make fixes based on new pointer and     --><!--                      grouper class defs                  --><!-- 93-07-08 : DTL : retitle "Aggregations"                  --><!--                  eliminate link= and partOf=             --><!--                  define JOIN as syntactic sugar for      --><!--                      LINK type=join                      --><!--                  add result= on JOIN                     --><!--                  add JOINGRP element                     --><!--                  include JOIN, JOINGRP as members of     --><!--                      class "pointer"                     --><!--                  use Milne ex in COpr                    --><!--                  replace with ex from MFK Fisher         --><!--                  restore Lessing ex in SAag1 subsection  --><!--                  retitle SAag1 "Three Examples"          --><!--                  change analysis of Salinger example,    --><!--                      per JL (?)                          --><!--                  modify S type= values in Orwell example --><!-- 93-01-26 : MSM : last chance revisions                   --><!-- 93-01-22 : MSM : revise for publication                  --><!-- 92-12-23 : MSM : strip header                            --><!-- Date: Wed, 23 Dec 1992 14:23:38 +0000                    --><!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- Subject: saag.odd (2 of 9)                               --><!-- 22 dec LB : introduced simple example at start and       --><!--             other minor changes for P2 conformity        --><!-- 21 dec: LB made from 443.odd                             --><!-- 24 Jul 92 : DTL  : Make other minor changes              --><!-- 21 Jul 92 : DTL  : Make additional minor changes.        --><!-- 18 Jul 92 : DTL  : Change "citn" to "text" in < ref>s    --><!-- in last markup of Salinger example.  Remove equiv=       --><!-- attribute in Orwell example, so that it can be           --><!-- introduced in section p2.444 on virtual copying.         --><!-- 15 Jul 92 : DTL  : Change example in TAGDOC for <        --><!-- join> to extract from Dillard, Black English used in     --><!-- section on < s>.  Add < analysis> tags around < join>s   --><!-- and < ref>s.                                             --><!-- 14 Jul 92 : DTL  : Correct ODD tagging.  Replace <       --><!-- extPtr> with < ref> in last markup of Salinger           --><!-- extract, as described in section on hypertext links      --><!-- and in my TEI-TECH comment of 14 July on that section    --><!-- (suggesting from= instead of target= ATTRIBUTE).         --><!-- 01 Jul 92 : DTL  : Include discussion of prev= and       --><!-- next=.  Rename section "Virtual Elements"; assign        --><!-- section number in accordance with preliminary outline    --><!-- of section; add type= to < join> with semantics as       --><!-- described in a note to CMSMcQ and LB.                    --><!-- 30 Jun 92 : DTL  : Add Lessing example                   --><!-- cross-referenced with section on orthographic            --><!-- sentences.                                               --><!-- 29 Jun 92 : DTL  : Eliminate material on < nonid.ptr>;   --><!-- rewrite discussion of indirect pointing.                 --><!-- 26 Jun 92 : DTL  : Replace link= by equiv= in Orwell     --><!-- example; other minor changes in that example.            -->
 
 </p></div2><div2 id="SAAG" name="subsection" ref="Y"><head>Aggregation</head><p>Because of the strict hierarchical organization of an SGML document,
or for other reasons, it may not always be possible or desirable to
include all the parts of a possibly fragmented text segment within a
single element.  In section <xref target="SAPTIP"/> we introduced the
notion of an intermediate pointer as a way of pointing to discontinuous
segments of this kind.  In this section we first describe another way of
linking the parts of a discontinuous whole, using a set of linking
attributes, which are made available for any tag by following the
procedure described at the beginning of this chapter.
 <!-- Using these attributes obviates the need --><!-- for introducing <tag>ptr</tag> tags into the text, as was --><!-- done in some of the illustrations in section <xref target=SAPT>.-->
 
We then describe how the <gi tei="yes">link</gi> element may be used to aggregate
such segments, and finally introduce the <gi tei="yes">join</gi> element, which is
a special-purpose linking element specifically for representing the
aggregation of parts, and the <gi tei="yes">joinGrp</gi> for grouping
<tag compl="full" tei="yes">join</tag> tags.</p><p>The linking attributes for aggregation are <att tei="yes">next</att> and
<att tei="yes">prev</att>; each of these attributes has a single identifier as its
value:
 
<adList classDoc="CLLINK" atts="next prev"/></p><p>The <gi tei="yes">join</gi> element is also a member of the class of <ident tei="yes" type="class">pointer</ident> elements, and so may carry any of the
attributes of that class; for the list, see section <xref target="SAPT"/>.</p><p>Here is the material on which we base our first illustration of the
use of these mechanisms.  Our problem is to represent the S-units
identified below as qs3 and qs4 as a single (but discontinuous) whole:
 
<eg><![CDATA[<q who=waitress><s id=QS2>
  Monsieur Paul, after he has taken equal
  parts of goose breast and the finest pork, and
  broken a certain number of egg yolks into them,
  and ground them <emph>very</emph>, very fine,
  cooks all with seasoning for some three hours.
</s><s id=QS3><emph>But</emph>,</s>
</q>
<s id=PS2>she pushed her face nearer, and looked with
 ferocious gloating at the p&acirc;t&eacute;
 inside me, her eyes like X rays,
</s><q who=waitress><s id=QS4>
  he never stops stirring it!
</s><s id=QS5>Figure to yourself the work of it &mdash;
</s><s id=QS6>stir, stir, never stopping!
</s></q>]]></eg><!-- M.F.K. Fisher, I was really very hungry, As They Were, p43  --><!-- removed some distracting atts; divided last s-unit at dash (LB)--></p><p>Using the <att tei="yes">prev</att> and <att tei="yes">next</att> attributes, we can link
the s-units with identifiers <code tei="yes" type="val">s1</code> and <code tei="yes" type="val">s2</code>, either singly or doubly as follows:
 
<eg><![CDATA[<s id=QS3 next=qs4><emph>But</emph>,</s>
<!-- intervening material -->
<s id=QS4>he never stops stirring it!</s>
 
<s id=QS3><emph>But</emph>,</s>
<!-- intervening material -->
<s id=QS4 prev=qs3>he never stops stirring it!</s>
 
<s id=QS3 next=qs4><emph>But</emph>,</s>
<!-- intervening material -->
<s id=QS4 prev=qs3>he never stops stirring it!</s>]]></eg>
 
Double linking of the two S-units, as illustrated by the last of these
encodings, is equivalent to specifying a <tag compl="full" tei="yes">link</tag> tag:
 
<eg><![CDATA[<link type=join targType='s s' targOrder=Y targets='qs3 qs4'>]]></eg></p><p>Such a <tag compl="full" tei="yes">link</tag> element must carry <att tei="yes">type=join</att>
attribute value to specify that the link is to be understood as joining
its targets into a single aggregate.</p><p>The <gi tei="yes">join</gi> element is equivalent to a <gi tei="yes">link</gi> element of
type <code tei="yes" type="val">join</code>; unlike a link, the default value for
the <att tei="yes">targOrder</att> attribute which this element also inherits from
the pointer class is <code tei="yes" type="val">Y</code>.
 <!-- LB added following, possibly contentious, clarification -->
 
Also unlike the <gi tei="yes">link</gi> element, the <gi tei="yes">join</gi> element can
additionally specify information about the virtual element which it
represents, by means of its <att tei="yes">result</att> attribute.  And finally,
unlike the <gi tei="yes">link</gi> element, the position of a <gi tei="yes">join</gi>
element within a text is significant:  it must be supplied at a position
where the element indicated by its <att tei="yes">result</att> attribute would be
contextually legal.
 
 <!-- and removed following --><!--   We now define the following equivalence:<eg>           --><!-- <![ CDATA [                                              --><!-- <link type=join> = <join>                                --><!-- ]]>                                                      --><!-- </eg>                                                    --><!--                                                          --><!-- <p>By using the <gi>join</gi> tag for representing       --><!-- element aggregation, another attribute is made           --><!-- available to indicate the nature of the                  --><!-- <term>result</term> of the joining operation.            --><!-- Moreover, we specify the default value for the           --><!-- <att>targOrder</att> attribute to be <term>Y</term>.     -->
 
 
<tagList style="one-line"><tagDesc tagDoc="JOIN" atts="result targets targOrder"/><tagDesc tagDoc="JOINGRP" atts="result"/></tagList>
 
To conclude the above example, we now use a <gi tei="yes">join</gi> element to
represent the virtual sentence formed by the aggregation of <code tei="yes" type="val">s1</code> and <code tei="yes" type="val">s2</code>:
 
<eg><![CDATA[<join result=s targets='qs3 qs4' >]]></eg>
 
As a further example, consider the following list of authors' names.
The object of the <gi tei="yes">join</gi> element here is to provide another list,
composed of those authors from the larger list who happen to come from
Heidelberg:
 
<eg><![CDATA[ <list><head>Authors</head>
   <item id=UF>Figge, Udo
   <item id=CH>Heibach, Christiane
   <item id=GH>Heyer, Gerhard
   <item id=BP>Philipp, Bettina
   <item id=MS>Samiec, Monika
   <item id=SS>Schierholz, Stefan
 </list>
 
<join result=list targets='ch bp ss' >
 ]]></eg></p><p>The following example shows how <gi tei="yes">join</gi> can be used to
reconstruct a text cited in fragments presented out of order.  The poem
being remembered (an unusual translation of a well known poem by Basho)
runs <q>When the old pond / gets a new frog, / it's a new pond.</q> </p><eg><![CDATA[ <sp who='Hughie'><p>How does it go?
   <q><l id=X1>da-da-da
      <l id=L2>gets a new frog
      <l>...
   </q></p>
 <sp who='Louie'><p><q><l id=L1>When the old pond</l> ...</q></p>
 <sp who='Dewey'><p>... <q><l id=L3>It's a new pond.</l></q></p>
 <!-- ... -->
 <join result=lg targets='L1 L2 L3' >]]></eg><!-- Basho translation from memory, Hughie, Louie, and Dewey  --><!-- sequence and imaginary example.                          --><p>As with other forms of link, a grouping element <tag compl="full" tei="yes">joinGrp</tag> is
available for use when a number of <tag compl="full" tei="yes">join</tag> elements of the same
kind co-occur.  This avoids the need to specify the <att tei="yes">result</att>
attribute for each <gi tei="yes">join</gi> if they are all of the same type, and
also allows us to restrict the domain within which their target elements
are to be found, in the same way as for <gi tei="yes">linkGrp</gi> elements (see<xref target="SAPTLG"/>
).  Like a <gi tei="yes">join</gi>, a <gi tei="yes">joinGrp</gi> may
appear only where the elements represented by its contents are legal.
 <!-- attributes.  Moreover, we specify the default value for the --><!-- <att>targFunc</att> attribute to be <term>'first.part --><!-- next.part'</term>.  --><!-- Not much use if we are joining three things then is it? (LB) -->
 
Thus if we had created many <tag compl="full" tei="yes">join</tag> tags of the sort just
described, we could group them together, and require that their
components are all contained by an element with the identifier <code tei="yes" type="val">MFKFhungry</code> as follows:
 
<eg><![CDATA[<joinGrp result=s
         targType=s
         domains=MFKFhungry>
<!-- ... -->
  <join targets='qs3 qs4'>
  <join targets='qs5 qs6'>
  </joinGrp>
<!-- ... -->]]></eg>
 <!-- If <tag>join</tag> tags appear with more than two targets, --><!-- when we would also specify the <att>extendTarg=2</att> --><!-- attribute value in the <tag>joinGrp</tag> tag. -->
 
 <!-- <div3 id=SAAG1><head>Three More Illustrations</head> --></p><p>The <gi tei="yes">join</gi> element is useful as a means of representing
non-hierarchic structures (as further discussed in chapter <xref target="NH"/>).  It may also be used as a convenient way of representing a
variety of analytic units, like the <gi tei="yes">span</gi> and <gi tei="yes">interp</gi>
elements discussed in chapter <xref target="AI"/>.  As an example, consider
the following passage:
 
<q rend="display"><p>Zui-Gan called out to himself every day, <q>Master.</q></p>
<p>Then he answered himself, <q>Yes, sir.</q></p>
<p>And then he added, <q>Become sober.</q></p>
<p>Again he answered, <q>Yes, sir.</q></p>
<p><q>And after that,</q> he continued, <q>do not be deceived by
others.</q></p>
<p><q>Yes, sir; yes, sir,</q> he replied.</p></q>
 <!-- J.D. Salinger, Franny and Zooey p179, 1964 Bantam ed --></p><p>Suppose now that we wish to represent an interpretation of the above
passage in which we distinguish between the various
<soCalled>voices</soCalled> adopted by the character Zui-Gan.  In the
following encoding, the <att tei="yes">who</att> attribute has been used for this
purpose; <att tei="yes">id</att> attributes have also been added:
 
<eg><![CDATA[<text id=ZUITXT>
<body>
<p>Zui-Gan called out to himself every day,
<q id=ZUIQ1 who=zuigan>Master.</q></p>
<p>Then he answered himself,
<q id=ZUIQ2 who=zuigan>Yes, sir.</q></p>
<p>And then he added,
<q id=ZUIQ3 who=master>Become sober.</q></p>
<p>Again he answered,
<q id=ZUIQ4 who=zuigan>Yes, sir.</q>
<p><q id=ZUIQ5 who=master>And after that,</q>
he continued,
<q id=ZUIQ6 who=master>do not be deceived by others.</q>
<p><q id=ZUIQ7 who=zuigan>Yes, sir; yes, sir,</q>
he replied.</p>
</body>
</text>]]></eg></p><p>The <att tei="yes">id</att> values specified now allow us to link the material
spoken by each voice:
 
<eg><![CDATA[<text id=ZUITXT>
<body>
<p>Zui-Gan called out to himself every day,
<q id=ZUIQ1 who=zuigan next=zuiq2>Master.</q></p>
<p>Then he answered himself,
<q id=ZUIQ2 who=zuigan next=zuiq4>Yes, sir.</q></p>
<p>And then he added,
<q id=ZUIQ3 who=master next=zuiq5>Become sober.</q></p>
<p>Again he answered,
<q id=ZUIQ4 who=zuigan next=zuiq7>Yes, sir.</q>
<p><q id=ZUIQ5 who=master next=zuiq6>And after that,</q>
he continued,
<q id=ZUIQ6 who=master>do not be deceived by others.</q>
<p><q id=ZUIQ7 who=zuigan>Yes, sir; yes, sir,</q>
he replied.</p>
</body>
</text>]]></eg></p><p>However, by using the <gi tei="yes">join</gi> element, we can directly
represent the complete speech attributed to each voice:
 
<eg><![CDATA[<joinGrp targType='q' domains='zuitxt' result='q'>
  <join desc="what Zui-Gan said" targets='zuiq1 zuiq2 zuiq4 zuiq7'>
  <join desc="what Master said"  targets='zuiq3 zuiq5 zuiq6'>
  </joinGrp>]]></eg></p><p>Note the use of the global <att tei="yes">n</att> attribute to supply a
descriptive name to distinguish the two virtual <gi tei="yes">q</gi> elements
represented by the <gi tei="yes">join</gi> elements; this is necessary because the
current proposals do not allow for any way of specifying the attributes
to be associated with a virtual element, and hence we cannot specify a
<att tei="yes">who</att> value for them.</p><p>Suppose now that <att tei="yes">id</att> attributes, for whatever reasons, are
not available.  Then <gi tei="yes">xptr</gi> elements may be created using any of
the methods described in section <xref target="SAXR" type="div2"/>.  The
<att tei="yes">id</att> attributes of <emph>these</emph> elements may now be
specified by the <att tei="yes">targets</att> attribute on the <gi tei="yes">join</gi>
elements.
 <!-- comment on need for <att>evaluate=Y<att> ?  -->
 
<eg><![CDATA[<text><body>
<!-- ... -->
<!-- We are in the second DIV0, the sixth DIV1 ... -->
<p>Zui-Gan called out to himself every day,
   <q>Master.</q></p>
<p>Then he answered himself, <q>Yes, sir.</q></p>
<p>And then he added, <q>Become sober.</q></p>
<p>Again he answered, <q>Yes, sir.</q>
<p><q>And after that,</q> he continued,
<q>do not be deceived by others.</q></p>
<p><q>Yes, sir; yes, sir,</q> he replied.</p>
<!-- ... -->
</body></text>
 
<!-- ... -->
 
<xptr id=RZUIQ1 from='DESCENDANT (2 div0) (6 div1) (1 p) (1 q)'>
<xptr id=RZUIQ2 from='DESCENDANT (2 div0) (6 div1) (2 p) (1 q)'>
<xptr id=RZUIQ3 from='DESCENDANT (2 div0) (6 div1) (3 p) (1 q)'>
<xptr id=RZUIQ4 from='DESCENDANT (2 div0) (6 div1) (4 p) (1 q)'>
<xptr id=RZUIQ5 from='DESCENDANT (2 div0) (6 div1) (5 p) (1 q)'>
<xptr id=RZUIQ6 from='DESCENDANT (2 div0) (6 div1) (5 p) (2 q)'>
<xptr id=RZUIQ7 from='DESCENDANT (2 div0) (6 div1) (6 p) (1 q)'>
 
<!-- ... -->
 
<joinGrp targType='xptr' result='q' evaluate=one>
  <join desc="what Zui-Gan said" targets='rzuiq1 rzuiq2 rzuiq4 rzuiq7'>
  <join desc="what Master said"  targets='rzuiq3 rzuiq5 rzuiq6'>
</joinGrp>
 ]]></eg></p><p>For a definition of the syntax used by the <gi tei="yes">xptr</gi> element, see
section <xref target="SAXRS"/> above.  The extended pointer with identifier
<code tei="yes" type="val">rzuiq2</code> (for example) may be read as <q>the first
<gi tei="yes">q</gi> in the first <gi tei="yes">p</gi>, inside the sixth <gi tei="yes">div1</gi>
within the second <gi tei="yes">div0</gi> element of the current document.</q></p><p>As mentioned above, there is no need for the <gi tei="yes">join</gi> and
<gi tei="yes">xptr</gi> elements to be held in the same SGML document as the text;
indeed, if, for example, the text is held on a read-only medium, this
may not be possible.  The <att tei="yes">doc</att> attribute of the <gi tei="yes">xptr</gi>
element may be used to specify the name of the SGML entity within which
its target is to be found.
 
<eg><![CDATA[<!-- ... -->
<!ENTITY fazdoc SYSTEM 'C:\faz.doc'>
<!-- ... -->
<xptr id=RZUIQ1
      doc=fazdoc
      from='DESCENDANT (2 div0) (6 div1) (1 p) (1 q)'>
<!-- ... -->]]></eg>
 <!-- deleted following example. nice though it is, it's too long --><!-- and adds nothing to preceding ones  -->
 <!-- <p>The second example is a possible reconstruction of    --><!-- the fragment of the diary that the main character has    --><!-- been keeping throughout the first chapter of a           --><!-- well-known twentieth-century novel.                      -->
 <!-- George Orwell, Nineteen-Eighty-Four, 1947 --><!-- empty head elements deleted, will be restored on demand. --><!-- diary excerpts retagged as Q not P (discussable).        --><!--  -msm --><!-- OK to both -dtl (93-07-08) --><!-- <eg> --><!-- <![ CDATA [ --><!-- <div1 id=C1><head rend='large caps centered'>one</head> --><!-- <div2 id=C1S1> --><!-- <p> --><!-- <s>It was a bright cold day in April, and the clocks were striking --><!-- thirteen.</s> --><!-- ... --><!-- <s>In small clumsy letters he wrote:</s> --><!-- <q rend='centered italic' id=D1> --><!-- <date id=D1.1 copyOf=d2.1></date> --><!-- </q> --><!-- <p><s>He sat back.</s> --><!-- <s>A sense of complete helplessness had descended upon him.</s> --><!-- ... --><!-- <p> --><!-- <s>Suddenly he began writing in sheer panic, only imperfectly --><!-- aware of what he was setting down.</s> --><!-- <s>His small but childish handwriting straggled up and down the page, --><!-- shedding first its capital letters and finally even its full --><!-- stops:</s> --><!-- <q rend=italic id=D2> --><!-- <date id=D2.1>April 4th, 1984.</date> --><!-- <s id=D2.2>Last night to the flicks.</s> --><!-- ... --><!-- <seg type=sentence id=D2.11.1>then there was a wonderful shot of --><!-- a childs arm going up up up right up into the air</seg> --><!-- ... --><!-- <seg type=phrase id=D2.11.9>typical prole reaction</seg> --><!-- <seg type=fragment id=D2.11.10>they never&mdash;</seg> --><!-- </q> --><!-- <p> --><!-- <s>Winston stopped writing, partly because he was suffering from --><!-- cramp.</s> --><!-- ... --><!-- <p><s>For a moment he was seized by a kind of hysteria.</s> --><!-- <s>He began writing in a hurried untidy scrawl:</s> --><!-- <q rend=italic id=D3> --><!-- <seg type=sentence id=D3.1>theyll shoot me</seg> --><!-- <seg type=sentence id=D3.2>i dont care</seg> --><!-- <seg type=sentence id=D3.3>theyll shoot me in the back of the neck</seg> --><!-- <seg type=sentence id=D3.4>i dont care </seg> --><!-- <seg type=phrase id=D3.5>down with big brother</seg> --><!-- <seg type=sentence id=D3.6>they always shoot you in the back of the --><!-- neck</seg> --><!-- <seg type=sentence id=D3.7>i dont care</seg> --><!-- <seg type=phrase id=D3.8>down with big brother&mdash;</seg> --><!-- </q> --><!-- <p> --><!-- <s>He sat back in his chair, slightly ashamed of himself, and --><!-- laid down the pen.</s> --><!-- ... --><!-- <s>With the feeling that he was speaking to O'Brien, and also --><!-- that he was setting forth an important axiom, he wrote:</s> --><!-- <q rend=italic id=D15> --><!-- <s id=D15.1>Freedom is the freedom to say that two plus two make --><!-- four.</s> --><!-- <s id=D15.2>If that is granted, all else follows.</s> --><!-- </q> --><!-- <div2 id=C1S8><head rend='large caps centered'>viii --><!-- ... --><!-- <div1 id=C2><head rend='large caps centered'>two</head> --><!-- ... --><!-- <joinGrp targType='q q' --><!--          domains='c1 c1' --><!--          extendTarg=2> --><!--   <join  result="Winston Smith's diary" --><!--          targets='d2 d3 d4 d5 d6 d7 d8 d9 d10 d11 d12 d13 d14 d15'> --><!--   </joinGrp> --><!-- ]]> --><!-- </eg> --><!--   -->
 <!-- Also dropped this example because I dont understand it.  --><!-- There's no relevant discussion at end of COse any more   --><!-- either                                                   --><!-- Well, if you wouldn't axe things quite so liberally,     --><!-- you wouldn't find yourself left with no explanations of  --><!-- things, would you?                                       -->
 <!-- <p>Finally, here is a solution to the markup problem     --><!-- discussed at the end of section <xref type=div3          --><!-- target=COSE>, concerning a quotation that is shared      --><!-- between two identification ments.                        -->
 <!-- Doris Lessing, The Four-Gated City, 1976, p257  --><!-- <eg><![ CDATA [ --><!-- <s id=S89235>Martha said, --><!-- <q id=Q89240><s id=S89240>Mark.</s> --><!-- <s id=S89245>He's my employer, after all.</s></q></s> --><!-- <s id=S89250<q id=Q89250><s id=S89255>I suppose,</s></q> she --><!-- added, with a sort of desperation of her own which at least --><!-- hinted at the possibility of a return of the dry, cool, --><!-- irony where Mrs. Quest had never thought she might be able --><!-- to meet her daughter.</s> --><!-- <join rend='PRE ldquo POST rdquo' --><!--       result='full quote' --><!--       targType='q q' --><!--       targets='q89240 q89250'> --><!-- ]]> --><!-- </eg> --></p><p>Here are the formal declarations of the <gi tei="yes">join</gi> and
<gi tei="yes">joinGrp</gi> elements.
 
<dtdFrag id="DSAAG" n="Aggregation"><tagDecl tagDoc="JOIN"/><tagDecl tagDoc="JOINGRP"/></dtdFrag></p></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2saag.odd ??><?tei:SOF p2saat.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2saat.odd,v $
    * Revision 1.6  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.5  94/03/27  21:47:19  msmcq
    * Correction of typos found by SJ, DB et al.
    * 
    * Revision 1.4  1994/03/16  03:29:41  msmcq
    * Changes as per JL, with some LB and TL.
    * 
    * Revision 1.3  1994/02/12  10:22:43  lou
    * reviions for P3
    * 
    * Revision 1.2  1993/09/16  19:01:31  msmcq
    * Minor SGML cleanup, add RCS log keyword
    * --><!-- Revisions:                                               --><!-- 94-03-26 : MSM : typos from HG, DB, SJ                   --><!-- 94-03-26 : MSM : disambiguate TERM, Q (> code, ident...) --><!-- 94-03-15 : MSM : clean up garbage data                   --><!-- 7 feb: LB: sorry, no time to give this the full once-over; --><!-- just deleted refs to copyOf and did some perfunctory tidying. --><!-- I still think it should be axed for now. --><!-- Also had to change attrib names on alt and altGrp to get dtd --><!-- to compile: perc -> wScale, excl->mode               --><!-- 19 dec 93 : LB change name of classdoc ANA -> cllink --><!-- 93-09-15 : MSM : correct typo (SGML detected)            --><!-- 93-07-22 : DTL : correct typos                           --><!--                  remove percent= from ALTgRP tag         --><!-- 93-07-21 : DTL : change argTypes= to targFunc=           --><!-- 93-07-12 : DTL : complete draft, fix to conform with new --><!--                  tag class definitions                   --><!-- 93-07-08 : DTL : start draft                             --><!--                  revise material from SAie on movable div2 --><!--                  revise "Bloody Mary" TEI-TECH posting,  --><!--                  using inclusive alternation, and eliminating --><!--                  need for JOIN tags                      --><div2 id="SAAT" name="subsection" ref="Y"><head>Alternation</head><p>This section proposes elements for the representation of alternation.
We say that two or more elements are in <term>exclusive
alternation</term> if any of those elements could be present in a text,
but one and only one of them is; in addition, we say that those elements
are <term>mutually exclusive</term>.  We say that the elements are in
<term>inclusive alternation</term> if at least one (and possibly more)
of them is present.  The elements that are in alternation may also be
called <term>alternants</term>.
 </p><p>The need to mark exclusive alternation arises frequently in text
encoding.  A common situation is one in which it can determined that
exactly one of several different words appears in a given location, but
it cannot be determined which one.  One way to mark such an exclusive
alternation is to use the linking attribute <att tei="yes">exclude</att>.  Having
marked an exclusive alternation, it can sometimes later be determined
which of the alternants actually appears in the given location.  To
preserve the fact that an alternation was posited, one can add the
linking attribute <att tei="yes">select</att> to a tag which hierarchically
encompasses the alternants, which points to the one which actually
appears.  To assign responsibility and degree of certainty to the
choice, one can use the <gi tei="yes">certainty</gi> tag described in chapter<xref target="CE"/>
.  Also see that chapter for further discussion of
certainty in general.
 </p><p>The <att tei="yes">exclude</att> and <att tei="yes">select</att> attributes may be used
with any element assuming that they have been declared following the
procedure discussed in the introduction to this chapter.
 
<adList classDoc="CLLINK" atts="exclude select"/>
 </p><p>A more general way to mark alternation, encompassing both exclusive
and inclusive alternation, is to use the linking element <gi tei="yes">alt</gi>.
The description and attributes of this tag and of the associated
grouping tag <gi tei="yes">altGrp</gi> are as follows.  These elements are also
members of the <ident tei="yes" type="class">pointer</ident> class and therefore
have all the attributes associated with that class.
 <!-- except that targFunc and targOrder are pretty meaningless -->
 
<tagList style="one-line"><tagDesc tagDoc="ALT" atts="targets weights"/><tagDesc tagDoc="ALTGRP"/></tagList>
 <!-- suppressed ref to mode, and wscale, which don't seem to  --><!-- be in the tagdoc (msm)                                   -->
 </p><p>To take a simple hypothetical example, suppose in transcribing a
spoken text, we encounter an utterance that we can understand either as
<cited>We had fun at the beach today.</cited> or as <cited>We had sun at
the beach today.</cited> We can represent the exclusive alternation of
these two possibilities by means of the <att tei="yes">exclude</att> attribute as
follows.
 
<eg><![CDATA[<div>
<!-- ... -->
<u id=WE.fun exclude=we.sun>We had fun at the beach today.</u>
<u id=WE.sun exclude=we.fun>We had sun at the beach today.</u>
<!-- ... -->
</div>]]></eg>
 </p><p>If it is then determined that the speaker said <cited>fun</cited>,
not <cited>sun</cited>, the encoder could amend the text by deleting the
alternant containing <cited>sun</cited> and the <att tei="yes">exclude</att>
attribute on the remaining alternant.  Alternatively, the encoder could
preserve the fact that there was uncertainty in the original
transcription by retaining the alternants, and assigning the
<att tei="yes">select=we.fun</att> attribute value to the <tag compl="full" tei="yes">div</tag> tag that
encompasses the alternants, as in:
 
<eg><![CDATA[<div select=we.fun>
<!-- ... -->
<u id=WE.fun exclude=we.sun>We had fun at the beach today.</u>
<u id=WE.sun exclude=we.fun>We had sun at the beach today.</u>
<!-- ... -->
</div>]]></eg>
 </p><p>The above alternation (including the <att tei="yes">select</att> attribute)
could be recoded by assigning the <att tei="yes">exclude</att> attributes to tags
that enclose just the words or even the characters that are mutually
exclusive, as in:
 
<note source="auth" place="foot" anchored="Y">See section <xref target="AILC"/> for discussion of the
<tag compl="full" tei="yes">w</tag> and <tag compl="full" tei="yes">c</tag> tags that can be used in the following
examples instead of the <tag compl="full" tei="yes">seg type=word</tag> and <tag compl="full" tei="yes">seg
type=character</tag> tags.</note>
 
<eg><![CDATA[<div>
<!-- ... -->
<u select=fun>We had
<seg type=word id=FUN exclude=sun>fun</seg>
<seg type=word id=SUN exclude=fun>sun</seg>
at the beach today.</u>
<!-- ... -->
</div>
 
<div>
<!-- ... -->
<u>We had
<seg type=word select=f>
<seg type=character id=F exclude=s>f</seg>
<seg type=character id=S exclude=f>s</seg>
un</seg>
at the beach today.
</u>
<!-- ... -->
</div>]]></eg>
 </p><p>Now suppose that the transcriber is uncertain whether the first word
in the utterance is <cited>We</cited> or <cited>Lee</cited>, but is
certain that if it is <cited>Lee</cited>, then the other uncertain word
is definitely <cited>fun</cited> and not <cited>sun</cited>.  The three
utterances that are in mutual exclusion can be encoded as follows.
 
<eg><![CDATA[<div>
<!-- ... -->
<u id=WE.fun exclude='we.sun lee.fun'>
We had fun at the beach today.</u>
<u id=WE.sun exclude='we.fun lee.fun'>
We had sun at the beach today.</u>
<u id=LEE.fun exclude='we.fun we.sun'>
Lee had fun at the beach today.</u>
<!-- ... -->
</div>]]></eg>
 </p><p>The preceding example can also be encoded with <att tei="yes">exclude</att>
attributes on the word segments <cited>We</cited>, <cited>Lee</cited>,
<cited>fun</cited> and <cited>sun</cited>:
 
<eg><![CDATA[<u>
<seg type=word id=WE exclude=lee>We</seg>
<seg type=word id=LEE exclude='we sun'>Lee</seg>
had
<seg type=word id=FUN exclude=sun>fun</seg>
<seg type=word id=SUN exclude='fun lee'>sun</seg>
at the beach today.</u>]]></eg>
 </p><p>The value of the <att tei="yes">select</att> attribute is defined as a list of
identifiers (<code tei="yes" type="kw">IDREFS</code>); hence it can also be used to
narrow down the range of alternants, as in:
 
<eg><![CDATA[<div select='we.fun lee.fun'>
<!-- ... -->
<u id=WE.fun exclude='we.sun lee.fun'>
We had fun at the beach today.</u>
<u id=WE.sun exclude='we.fun lee.fun'>
We had sun at the beach today.</u>
<u id=LEE.fun exclude='we.fun we.sun'>
Lee had fun at the beach today.</u>
<!-- ... -->
</div>]]></eg>
 
This is interpreted to mean that either the first or the third
<tag compl="full" tei="yes">u</tag> tag appears, and is thus equivalent to just the alternation
of those two tags:
 
<eg><![CDATA[<div>
<!-- ... -->
<u id=WE.fun exclude=lee.fun>We had fun at the beach today.</u>
<u id=LEE.fun exclude=we.fun>Lee had fun at the beach today.</u>
<!-- ... -->
</div>]]></eg>
 </p><p>The <att tei="yes">exclude</att> attribute can also be used in case there is
uncertainty about the tag that appears in a certain position.  For
example, the occurrence of the word <cited>May</cited> in the S-unit
<cited>Let's go to May</cited> can be interpreted, in the absence of
other information, either as a person's name or as a date.  The
uncertainty can be rendered as follows, using the <att tei="yes">exclude </att>
attribute.
 
<eg><![CDATA[<s>Let's go to
<name id=MAYD exclude=mayn>May</name>
<date id=MAYN exclude=mayd copyOf=mayd></date>.</s>]]></eg>
 </p><p>Note the use of the <att tei="yes">copyOf</att> attribute discussed in section<xref target="SAIE"/>
; this avoids having to repeat the content of the
element whose correct tagging is in doubt.
 </p><p>The <att tei="yes">copyOf</att> and the <att tei="yes">exclude</att> attributes also
provide for a simple way of indicating uncertainty about exactly where a
particular element occurs in a document.<note source="auth" place="display" anchored="Y">An alternative way of
representing this problem is discussed in chapter <xref target="CE"/>.</note> For example suppose that a particular <gi tei="yes">div2</gi>
element appears either as the third and last of the <gi tei="yes">div2</gi>
elements within the first <tag compl="full" tei="yes">div1</tag> element in the body of a
document, or as the first <gi tei="yes">div2</gi> of the second <gi tei="yes">div1</gi>.
One solution would be to record the <gi tei="yes">div2</gi> in its entirety in the
first of these positions, and a virtual copy of it in the second, and
mark them as excluding each other as follows:
 
<eg rend="skeletal"><![CDATA[<body>
<div1 id=C1>
 
 <div2 id=C1S3 exclude=c2s1>
  <!-- Text of the "movable" div2 appears here.  -->
 </div2>
 
</div1>
 
<div1 id=C2>
 
 <div2 id=C2S1 copyOf=c1s3 exclude=c1s3></div2>
 
</div1>
 
</body>]]></eg>
 
In this case, the <att tei="yes">select</att> attribute, if used, would appear on
the <tag compl="full" tei="yes">body</tag> tag.
 </p><p>Mutual exclusion can also be expressed using a <tag compl="full" tei="yes">link</tag>; the
first example in this section can be recoded by removing the
<att tei="yes">exclude</att> attributes from the <tag compl="full" tei="yes">u</tag> tags, and adding a
<tag compl="full" tei="yes">link</tag> as follows:  <note source="auth" place="foot" anchored="Y">In this example, we have
placed the <tag compl="full" tei="yes">link</tag> next to the tags that represent the
alternants.  It could also have been placed elsewhere in the document,
perhaps within a <tag compl="full" tei="yes">linkGrp</tag>.  </note>
 
<eg><![CDATA[<div>
<!-- ... -->
<u id=WE.fun>We had fun at the beach today.</u>
<u id=WE.sun>We had sun at the beach today.</u>
<link type='exclusive alternation'
      targType='u u'
      targOrder=N
      targets='we.fun we.sun'>
<!-- ... -->
</div>]]></eg>
 </p><p>Now we define the specialized linking element <gi tei="yes">alt</gi>,making it
a member of the pointer class of elements, and assigning it a
<att tei="yes">excl</att> (for <cited>mutually exclusive</cited>) attribute, which
can have either of the values <code tei="yes" type="value">Y</code> or <code tei="yes" type="value">N</code>.  Then the following equivalence holds:
 
<eg rend="formula"><![CDATA[ <alt mode=excl> = <link type='exclusive alternation'>]]></eg>
 </p><p>It is in the nature of alternation that the order of the targets is
irrelevant; hence the <att tei="yes">targOrder</att> attribute of the
<tag compl="full" tei="yes">alt</tag> defaults to the value <code tei="yes" type="value">N</code>.  The
preceding <tag compl="full" tei="yes">link</tag> may therefore be recoded as the following
<tag compl="full" tei="yes">alt</tag> tag.
 
<eg><![CDATA[<alt mode=excl targType='u u' targets='we.fun we.sun'>]]></eg>
 </p><p>Other attributes that are defined specifically for the <gi tei="yes">alt</gi>
element are <att tei="yes">weights</att> and <att tei="yes">percent</att>.  The
<att tei="yes">weights</att> attribute is to be used if one wishes to assign
<term>probabilistic weights</term> to the targets (alternants).  Its
value is a list of numbers, corresponding to the targets, expressing the
probability that each target appears.  The <att tei="yes">percent</att> attribute
is used to indicate whether the weights are stated as percentages
(<att tei="yes">percent=Y</att>, the default) or as the actual probabilities
(<att tei="yes">percent=N</att>).  If the alternants are mutually exclusive, then
the weights must sum to 100% (or 1, if <att tei="yes">percent=N</att> is
specified).
 </p><p>Suppose in the preceding example that it is equiprobable whether
<cited>fun</cited> or <cited>sun</cited> appears.  Then the
<tag compl="full" tei="yes">alt</tag> that represents the alternation may be stated as follows:
 
<eg><![CDATA[<alt mode=excl
     targType='u u'
     targets='we.fun we.sun'
     weights='50 50'>]]></eg>
 </p><p>The assignment of a weight of 100% to one target (and weights of 0%
to all the others) is equivalent to selecting that target.  Thus the
following encoding is equivalent to the second example at the beginning
of this section.
 
<eg><![CDATA[<!-- ... -->
<u id=WE.fun>We had fun at the beach today.</u>
<u id=WE.sun>We had sun at the beach today.</u>
<alt mode=excl
     targType='u u'
     targets='we.fun we.sun'
     weights='100 0'>
<!-- ... -->]]></eg>
 <!-- <p>Inclusive alternation can only be expressed by the    --><!-- use of a linking element, either a <tag>link             --><!-- type='inclusive alternation'</tag> tag, or an <tag>alt   --><!-- excl=N</tag> tag.  For example, suppose in the example   --><!-- concerning the <tag>div2</tag> tag that can appear in    --><!-- two different places, that it is also possible that it   --><!-- appears in both plases.  This situation can be encoded   --><!-- as follows.                                              -->
 <!-- <eg><![ CDATA [ --><!-- <body> --><!-- <div1 id=C1> --><!-- ... --><!-- <div2 id=C1S3> --><!-- Text of the "copyable" div2 appears here. --><!-- </div2> --><!-- <div1 id=C2> --><!-- <div2 id=C2S1 copyOf=c1s3></div2> --><!-- ... --><!-- </div1> --><!-- ... --><!-- </body> --><!-- ... --><!-- <alt excl=N targType='div2 div2' targets='c1s3 c2s1'> --><!-- ]]> --><!-- </eg> -->
 <!-- <p>For inclusive alternation, the <att>weights</att>     --><!-- attribute works as follows:  each weight states the      --><!-- probability that the target appears given that one or    --><!-- more of the other targets appear.  For the current       --><!-- example, suppose that the probability that the           --><!-- <tag>div2</tag> appears in the first position given      --><!-- that it appears in the second position is 20%, but that  --><!-- the probability that it appears in the second position   --><!-- given that it appears in the first position is 0%.       --><!-- Then the preceding <tag>alt</tag> tag can be revised to  --><!-- read:                                                    -->
 <!-- <eg><![ CDATA [ --><!-- <alt excl=N targType='div2 div2' targets='c1s3 c2s1' weights='20 0'> --><!-- ]]> --><!-- </eg> -->
 
The sum of the weights for <tag compl="full" tei="yes">alt excl=N</tag> tags ranges from 0% to
(100 x k)%, where k is the number of targets.  If the sum is 0%, then
the alternation is equivalent to exclusive alternation; if the sum is
(100 x k)%, then all of the alternants must appear, and the situation is
better encoded without an <tag compl="full" tei="yes">alt</tag> tag.
 </p><p>If it is desired, <gi tei="yes">alt</gi> tags may be grouped together in an
<gi tei="yes">altGrp</gi> tag, and attribute values shared by the individual
<tag compl="full" tei="yes">alt</tag> tags may be identified on the <tag compl="full" tei="yes">altGrp</tag> tag.  The
<att tei="yes">targFunc</att> attribute defaults to the value <code tei="yes" type="value">'first.alternant next.alternant'</code>.  Thus, specifying
the <att tei="yes">extendTarg=2</att> attribute value permits the alternants to be
extended indefinitely.
 </p><p>To illustrate, consider again the example of a transcribed utterance,
in which it is uncertain whether the first word is <cited>We</cited> or
<cited>Lee</cited>, whether the third word is <cited>fun</cited> or
<cited>sun</cited>, but that if the first word is <cited>Lee</cited>,
then the third word is <cited>fun</cited>.  Now suppose we have the
following additional information:  if <cited>we</cited> occurs, then the
probability that <cited>fun</cited> occurs is 50% and that
<cited>sun</cited> occurs is 50%; if <cited>fun</cited> occurs, then the
probability that <cited>we</cited> occurs is 40% and that
<cited>Lee</cited> occurs is 60%.  This situation can be encoded as
follows.
 
<eg><![CDATA[<u>
<seg type=word id=WE exclude=lee>We</seg>
<seg type=word id=LEE exclude=we>Lee</seg>
had
<seg type=word id=FUN exclude=sun>fun</seg>
<seg type=word id=SUN exclude=fun>sun</seg>
at the beach today.</u>
<!-- ... -->
<altGrp targType='seg seg'>
  <alt targets='we lee'>
  <alt targets='fun sun'>
  <alt mode=incl targets='we fun'  weights='50  50'>
  <alt mode=incl targets='Lee fun' weights='100 60'>
  </altGrp>]]></eg>
 </p><p>From the information in this encoding, we can determine that the
probability is about 28.5% that the utterance is <q>We had fun at the
beach today</q>, 28.5% that it is <cited>We had sun at the beach
today</cited>, and 43% that it is <cited>Lee had fun at the beach
today</cited>.
 <!-- MSM:  correct details, please!-->
 </p><p>Another very similar example is the following regarding the text of a
Broadway song.  In three different versions of the song, the same line
reads <q>Her skin is tender as a leather glove,</q> <q>Her skin is
tender as a baseball glove,</q> and <q>Her skin is tender as Dimaggio's
glove.</q><note source="auth" place="display" anchored="Y">The variant readings are found in the commercial sheet
music, the performance score, and the Broadway cast recording.</note>
 </p><p>If we wish to express this textual variation using the <gi tei="yes">alt</gi>
element, we can record our relative confidence in the readings
<cited>Dimaggio's</cited> (with probability 50%), <cited>a
leather</cited> (25%), and <cited>a baseball</cited> (25%).
 </p><p>Let us extend the example with a further (imaginary) variation,
supposing for the sake of the argument that the next line is variously
given as <cited>and she bats from right to left</cited> (with
probability 50%) or <cited>now ain't that too damn bad</cited> (with
probability 50%).  Using the <gi tei="yes">alt</gi> element, we can express the
conviction that if the first choice for the second line is correct, then
the probability that the first line contains <cited>Dimaggio's</cited>
is 90%, and each of the others 5%; whereas if the second choice for the
second line is correct, then the probability that the first line
contains <cited>Dimaggio's</cited> is 10%, and each of the others is
45%.  This can be encoded, with an <tag compl="full" tei="yes">altGrp</tag> tag containing a
combination of exclusive and inclusive <tag compl="full" tei="yes">alt</tag> tags, as follows.
 <!-- Bloody Mary, from Rogers & Hammerstein, South Pacific -->
<eg><![CDATA[<div id=BM>
<!-- ... -->
<l>Her skin is tender as
<seg id=DM>Dimaggio's</seg>
<seg id=LT>a leather</seg>
<seg id=BB>a baseball</seg>
glove,</l>
<l id=RL>and she bats from right to left.</l>
<l id=DB>now ain't that too damn bad.</l>
<!-- ... -->
</div>
<!-- ... -->
<altGrp>
  <alt mode=excl targType='seg seg'
       targets='dm lt bb' weights='50 25 25'>
  <alt mode=Excl targType='l l'
       targets='rl db' weights='50 50'>
  </altGrp>
<altGrp mode=incl targType='seg l'>
  <alt targets='dm rl' weights='90 90'>
  <alt targets='lt rl' weights='5 5'>
  <alt targets='bb rl' weights='5 5'>
  <alt targets='dm db' weights='10 10'>
  <alt targets='lt db' weights='45 90'>
  <alt targets='bb db' weights='45 90'>
  </altGrp>]]></eg>
 </p><p>Here are the formal declarations of the <gi tei="yes">alt</gi> and
<gi tei="yes">altGrp</gi> elements.
 
<dtdFrag id="DSAAT" n="Alternation"><tagDecl tagDoc="ALT"/><tagDecl tagDoc="ALTGRP"/></dtdFrag><?tei:EOF p2saat.odd ??>
<?tei:SOF p2saan.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2saan.odd,v $
# Revision 1.3  1994/03/27  21:47:19  msmcq
# Correction of typos found by SJ, DB et al.
#
# Revision 1.2  1993/09/16  19:01:31  msmcq
# Minor SGML cleanup, add RCS log keyword
# --><!-- Revisions:                                               --><!-- 94-03-27 : MSM : typo from SJ                            --><!-- 94-03-26 : MSM : disambiguate TERM, Q (> code, ident...) --><!-- 93-09-15 : MSM : process TDL's changes                   --><!-- 93-07-16 : DTL : complete draft                          -->
 </p></div2><div2 id="SAAN" name="subsection" ref="Y"><head>Connecting Analytic and Textual Markup</head><p>In chapters <xref target="AI"/> and <xref target="FS"/> and elsewhere,
provision is made for analytic and interpretive markup to be represented
outside of textual markup, either in the same document or in a different
document.  The elements in these separate domains can be connected,
either with the pointing attributes <att tei="yes">ana</att> (for
<cited>analysis</cited>) and <att tei="yes">inst</att> (for
<cited>instance</cited>), or by means of <gi tei="yes">link</gi> and
<gi tei="yes">linkGrp</gi> elements.  Numerous examples are given in these
chapters, particularly in sections <xref target="AILA"/>, <xref target="FSFL"/> and <xref target="FSIL"/>.
 <?tei:EOF p2saan.odd ??>
</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2sa.odd ??><!-- 14 Segmentation and Alignmt --><?tei:SOF p2ai.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2ai.odd,v $
    * Revision 1.9  1998/01/31 19:18:50  tei
    * fix log keyword, use public identifier
    *
    *--><!-- Revisions:                                               --><!-- 26 Feb: re-ordered and tidied prose a bit --><!-- 19 dec: added missing </term>, dtdfra->dtdfrag           --><!-- 93-11-26 : MSM : minor revisions, add some text on atts  --><!-- 93-11-23 : MSM : point to ailc, not aila                 --><!-- 93-11-23 : MSM : add section (stub) on attributes        --><!-- 1993-11-23 : CMSMcQ : revision.  Clean up invocation,    --><!--                       restore analysis class             --><!-- 93-07-05 :  DTD :  Remove references to copying          --><!-- mechanisms (moved to SA chapter}.  Move definitions of   --><!-- equiv=, exclude=, and select = attributes to SA chapter  --><!-- (so as to go along with other global attributes defined  --><!-- that chapter).  Change reference to feature-value pair   --><!-- tags to span and interpretation tags (section AIsp).     --><!-- Add reference to simple linguistic analysis tags         --><!-- (section AIla).  Capitalize words in < head >. Add       --><!-- footnote regarding attribution.                          --><div1 id="AI" n="15" name="chapter" ref="Y"><head>Simple Analytic Mechanisms</head><p>This chapter describes a tag set for associating simple analyses and
interpretations with text elements.  We use the term
<term>analysis</term> here to refer to any kind of semantic or
syntactic interpretation which an encoder wishes to attach to all or
part of a text. Examples discussed in this chapter include familiar
linguistic categorizations (such as <q>clause</q>, <q>morpheme</q>,
<q>part-of-speech</q> etc.) and  characterizations of narrative
structure (such as <q>theme</q>, <q>reconciliation</q> etc.). The
mechanisms presented in this chapter offer simpler but less powerful
than those described in chapter <xref target="FS"/>.

<!-- <note place=foot>Most of the material in this chapter was --><!-- first prepared for inclusion in other chapters; the --><!-- <gi>span</gi> tag was originally developed for inclusion in --><!-- chapter <xref target=CO>, and the discussion of simple --><!-- linguistic annotation was written originally for chapter --><!-- <xref target=CC>.  The present chapter was assembled and --><!-- prepared by D. Terence Langendoen.</note> --></p><p>Section <xref target="AILC"/> introduces a tag set for characterizing
text segments according to the familiar linguistic categories of
<term>sentence</term> or <term>s-unit</term>, <term>clause</term>,
<term>phrase</term>, <term>word</term>, <term>morpheme</term>, and
<term>character</term>. These elements represent special cases of the
generic <gi tei="yes">seg</gi> element described in section <xref target="SASE"/>.</p><p>Section <xref target="AIATTS"/> introduces an additional global
attribute  which allows passages of text to be associated with
specialised SGML elements  representing their interpretation. <!-- , by pointing either from the text to --><!-- the interpretation, or from the interpretation to thetext. -->
These <soCalled>interpretative</soCalled> elements (<gi tei="yes">span</gi> and
<gi tei="yes">interp</gi>) are described in detail in section <xref target="AISP"/>.
They  allow the encoder to specify an analysis as a series of names and
associated values,<note source="auth" place="foot" anchored="Y">Or, as they are widely known,
<term>attribute-value pairs</term>; this term should not be confused,
however, with SGML attributes and their values, which are similar in
concept but distinct in their formal definitions.</note> each such pair
being linked to one or more stretches of text, either directly, in the
case of spans, or indirectly, in the case of interpretations.</p><p>Finally section <xref target="AILA"/> revisits the topic of linguistic
analysis, and illustrates how these interpretative mechanisms may be
used to associate simple linguistic analysis with text segments.</p><p>The following DTD fragments show the overall organization of the
class of analytic elements discussed in the remainder of this chapter.
File <term>teiana2.ent</term> defines the additional global attribute
made available by this tag set.
 
<dtdFrag id="DAIENT" n="Modifications to TEI class system for analysis" file="teiana2.ent"><dtdRef dtdFrag="DAIGA"/></dtdFrag>
 <!-- Reference to global analytic attributes omitted.  (why?  --><!-- restored by msm)                                         --></p><p>File <term>teiana2.dtd</term> contains declarations for elements
used to represent simple analyses or interpretations of portions of a
text.
 
<dtdFrag id="DAI" n="Simple analytic mechanisms" file="teiana2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>We declare the various elements, group by group.</commDecl><dtdRef dtdFrag="DAISP"/><dtdRef dtdFrag="DAILC"/></dtdFrag></p><p>This tag set is selected as described in <xref target="STIN"/>; in a
document which uses the markup described in this chapter, the document
type declaration should contain the following declaration of the entity
<term>TEI.analysis</term>, or an equivalent one:
 
<eg><![CDATA[<!ENTITY % TEI.analysis 'INCLUDE'>]]></eg>
 
The entire document type declaration for a document using this
additional tag set together with that for linking and alignment and the
base tag set for prose might look like this:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN" "tei2.dtd" [
    <!ENTITY TEI.prose    'INCLUDE' >
    <!ENTITY TEI.linking  'INCLUDE' >
    <!ENTITY TEI.analysis 'INCLUDE' >
 ]>]]></eg><?tei:SOF p2ailc.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2ailc.odd,v $
    * Revision 1.7  1998/01/29 21:43:46  tei
    * fix typos in eg
    *
    * Revision 1.6  1998/01/28 11:23:15  cmsmcq
    * LB changes of Jan 1998, and add RCS kyewords
    *
    *--><!-- Revisions:                                               --><!-- 5 Jan 98 : LB : fixed typo in eg --><!-- 93-11-26 : MSM :  minor improviements\                   --><!-- 93-11-23 : MSM : fix sgml syntax slips                   --><!-- 93-11-23 : MSM : revise (substantially)                  --><!-- 93-07-05 : DTL : Make file.                              -->
 </p><div2 id="AILC" name="subsection" ref="Y"><head>Linguistic Segment Categories</head><p>In this section we introduce specialized <term>linguistic segment
category</term> elements which may be used to represent the segmentation of
a text into the traditional linguistic categories of
<term>sentence</term>, <term>clause</term>, <term>phrase</term>,
<term>word</term>, <term>morpheme</term>, and
<term>characters</term>. 
 
<tagList style="one-line"><tagDesc tagDoc="S"/><tagDesc tagDoc="CL"/><tagDesc tagDoc="PHR"/><tagDesc tagDoc="W" atts="lemma"/><!-- rename lemma as baseform? --><tagDesc tagDoc="M" atts="baseform"/><tagDesc tagDoc="C"/></tagList>
 </p><p>As members of the <ident tei="yes" type="class">seg</ident> class, these
elements share the following attributes:

<adList classDoc="CLSEG" atts="type function"/>
</p><p>The <gi tei="yes">s</gi> element may be used simply to segment a text
end-to-end  into a series of non-overlapping segments, referred to here
and elsewhere as <term>s-units</term>, or <term>sentences</term>.

<eg> <![CDATA[ 
<p> 
<s>Nineteen fifty-four, when I was eighteen years old,
is held to be a crucial turning point in the history of
the Afro-American  --- for the U.S.A. as a whole --- the
year segregation was outlawed by the U.S. Supreme Court.</s>
<s>It was also a crucial year for me because on June 18,
1954, I began serving  a sentence in state prison for
possession of marijuana.</s>]]></eg><!-- Eldridge Cleaver, Soul on Ice (first para of first    --><!-- letter from prison)                   -->

The <gi tei="yes">s</gi>may be thought of as  providing an abbreviated version of
the tag <tag compl="full" tei="yes">seg type='s-unit'</tag>, with the important additional
proviso that (unlike <gi tei="yes">seg</gi> elements) <gi tei="yes">s</gi> elements may not
be nested within each other. The <att tei="yes">type</att> attribute of the
<gi tei="yes">s</gi> element corresponds to the <att tei="yes">subtype</att> attribute on
the <gi tei="yes">seg</gi> element, that is, a tag <tag compl="full" tei="yes">s type='xxx'</tag> should
be thought of as synonymous with a tag <tag compl="full" tei="yes">seg type='s-unit'
subtype='xxx'</tag>.  Similar considerations apply to the  <gi tei="yes">cl</gi>
and <gi tei="yes">phr</gi> elements , which  can be thought of as short for
<tag compl="full" tei="yes">seg type=clause</tag> and <tag compl="full" tei="yes">seg type=phrase</tag>,
respectively.
</p><p>The <gi tei="yes">s</gi> element may be further subdivided into
<term>clauses</term>, marked with the <gi tei="yes">cl</gi> element,
as in the following example:

<eg><![CDATA[<p>
<s><cl>It was about the beginning of September, 1664,
    <cl>that I, among the rest of my neighbours,
      heard in ordinary discourse
      <cl>that the plague was returned again
        in Holland;
      </cl>
    </cl>
  </cl>
  <cl>for it had been very violent there, and 
    particularly at Amsterdam and Rotterdam,
    in the year 1663,</cl>
  <cl>whither, 
    <cl>they say,</cl>
    it was brought,
    <cl>some said</cl>
    from Italy, others from the Levant,
    among some goods
    <cl>which were brought home
    by their Turkey fleet;</cl>
  </cl>
  <cl>others said it was brought from Candia;
    others from Cyprus.
  </cl>
</s>
<s><cl>It mattered not
    <cl>from whence it came;</cl>
  </cl>
  <cl>but all agreed
    <cl>it was come into Holland again.</cl>
  </cl>
</s>
</p>]]></eg>
<!-- Defoe, Journal of the Plague Year -->
</p><p>Clauses may be further divided into <gi tei="yes">phr</gi> elements in the same
way. A text may be segmented directly into clauses, or into
phrases, with no need to include segmentation at a higher level as well.
 </p><p>For verse texts, the overlapping of metrical and syntactic structure
requires that special care be given to representing both using the SGML
element hierarchy. One simple approach is to split the syntactic phrases
into fragments when they cross verse boundaries, reuniting them either
with the <att tei="yes">part</att> attribute:
 
<eg><![CDATA[<div type=stanza>
<l><cl part=i>Tweedledum and Tweedledee</cl></l>
<l><cl part=f>Agreed to have a battle;</cl></l>
<l><cl part=i>For Tweedledum said
  <cl part=i>Tweedledee</cl></cl></l>
<l><cl part=f><cl part=f>Had spoiled his
  nice new rattle.</cl></cl></l>
<div type=stanza>
<l><cl part=i>Just then flew down a monstrous crow,</cl></l>
<l><cl part=f>As black as a tar barrel;</cl></l>
<l><cl part=i>Which frightened both the heroes so,</cl></l>
<l><cl part=f><cl>They quite forgot their quarrel.</cl></cl></l>
</div>]]></eg><!-- Lewis Carroll, Through the Looking Glass, ch4 -->
 
Another approach is to use the <att tei="yes">next</att> and <att tei="yes">prev</att>
attributes defined in the additional tag set for linking (chapter <xref target="SA"/>):
 
<eg><![CDATA[<div type=stanza>
<l>...
<l><cl id=C3 next=c5 part=i>For Tweedledum said
  <cl id=C4 next=c6 part=i>Tweedledee</cl></cl></l>
<l><cl id=C5 prev=c3 part=f>
  <cl id=C6 prev=c4 part=f>
   Had spoiled his nice new rattle.</cl></cl></l>
</div>]]></eg>
 
Other methods are also possible; for discussion, see chapter <xref target="NH"/>.
 </p><p>The <att tei="yes">type</att> attribute on linguistic segment categories can
be used to provide additional interpretative information about the
category. The <att tei="yes">function</att> attribute on the <gi tei="yes">cl</gi> and
<gi tei="yes">phr</gi> elements can be used to provide additional information
about the function of the category. Legal values for these
two attributes are not defined by these Guidelines, but should be
documented in the <gi tei="yes">segmentation</gi> element of the
<gi tei="yes">encodingDesc</gi> element within the document's header. 
A general approach to the encoding of linguistic categories assigned to
parts of a text is discussed in section <xref target="AILA"/> below.
</p><p>Using traditional terminology, these attributes provide a convenient
way of specifying, for example, that the clause <cited>from whence it
came</cited> is a relative clause modifying another, or that  the
phrase <cited>by the U.S. Supreme Court</cited>  is a prepositional
post-modifier:
	
 
<eg><![CDATA[<cl>It mattered not
  <cl type='relative' function='clause modifier'>
   from whence it came;</cl></cl>
 
<phr type=NP>the year
  segregation</phr>
 <phr>was outlawed</phr>
 <phr type=PP function='postmodifier (agent)'>
  by the U.S. Supreme Court.</phr>]]></eg>
 
 </p><p>Segmentation into clauses and phrases can, of course, be combined.
To make such encodings easier to read,  the segmentation
tags can begin new lines, and be indented according to their degree of
nesting, thus:
 
<eg><![CDATA[<p>
<cl type='finite declarative' function='independent'>
 <phr type=NP function='subject'>Nineteen fifty-four,
  <cl type='finite relative declarative'
    function='appositive'>when
   <phr type=NP function='subject'>I</phr>
   <phr type=VP function='predicate'>was eighteen
                    years old</phr>
  </cl>,
 </phr>
 <phr type=VP function='predicate'>
  <phr type=V function='main verb'>is held</phr>
  <phr type=NP function='complement'> <!-- ? -->
   <cl type='nonfinite' function='predicate nom.'>
    <phr type=V function='copula'>to be</phr>
    <phr type=NP function='predicate nom.'>
     a crucial turning point
     <phr type=PP function='postmodifier'>in
      <phr type=NP function='prep.obj.'>
       the history
       <phr type=PP function='postmodifier'>
        of the Afro-American</phr>
      </phr>
     </phr>
     ---
     <phr type=PP
        function='appositive postmodifier'>for
      <phr type=NP function='prep.obj.'>the U.S.A.
       <phr type=PP function='postmodifier'>
        as a whole</phr>
      </phr>
     </phr>
    </phr>
    ---
    <phr type=NP function='appositive pred.nom.'>
     the year
     <cl type='finite relative'
       function='adjectival'>
      <phr type=NP function='subject'>
       segregation</phr>
      <phr type=VP function='predicate'>
       <phr type=V function='main verb'>
        was outlawed</phr>
       <phr type=PP function='postmodifier'>
        by the U.S. Supreme Court</phr>
      </phr>
     </cl>
    </phr>
   </cl>
  </phr>
 </phr>
  .
</cl>
<cl type='finite declarative' function='independent'>
 <phr type=NP function='subject'>It</phr>
 <phr type=VP function='predicate'>
  <phr type=V function='main verb'>was</phr>
  also
  <phr type=NP function='predicate nom.'>
   a crucial year for me</phr>
 </phr>
 <cl type='finite declarative'
   function='dependent causative'>because
  <phr type=PP function='sentence adverb'>
   on June 18, 1954</phr>,
  <phr type=NP function='subject'>I</phr>
  <phr type=VP function='predicate'>
   <phr type=V function='main verb'>began serving</phr>
   <phr type=NP function='complement'>
    a sentence in state prison
    <phr type=PP function='complement'>
     for possession of marijuana
    </phr>
   </phr>
  </phr>
 </cl>
</cl>
.]]></eg>
 </p><p>This style of markup, however, introduces spurious new lines and
blanks into the text, which could make restoring the text to its
original layout problematic. If the original layout is important, the
original line breaks and font shifts should be recorded using
<gi tei="yes">lb</gi> elements, the global <att tei="yes">rend</att> attribute, etc.
 <!-- I think this still needs further work: it's hard to see why --><!-- we dont merge all this with AIla, and provide more discussion --><!-- e.g. problems in segmenting English; examples in other langs --><!-- Save for P4.....                        (LB)   -->
</p><p>The <gi tei="yes">w</gi>, <gi tei="yes">m</gi> and <gi tei="yes">c</gi> elements are also
identical in meaning to the <gi tei="yes">seg</gi> element with a <att tei="yes">type</att>
attribute of <q>w</q>, <q>m</q>, or <q>c</q>, and may occur wherever
<gi tei="yes">seg</gi> is permitted to occur. However, they have more  restricted
content models than does <gi tei="yes">seg</gi>: for example, the <gi tei="yes">w</gi>
element can only contain <gi tei="yes">w</gi>, <gi tei="yes">m</gi> and <gi tei="yes">c</gi>
elements, and parsed character data; the <gi tei="yes">m</gi> element can only
contain <gi tei="yes">c</gi> elements and parsed character data; the <gi tei="yes">c</gi>
element can only contain parsed character data, and should in fact only
contain a single character. Consequently, while <gi tei="yes">m</gi> et al. can
be translated directly into typed <gi tei="yes">seg</gi> elements, the reverse is
not necessarily the case.
 </p><p>The restriction on the content of the <gi tei="yes">w</gi> attribute in
particular requires that a certain care must be exercised when using it,
especially in relation to the use of other tags that one may think of as
<term>word level</term>, but which are in fact defined as <term>phrase
level</term>. Consider the problem of segmenting an occurrence of the
<gi tei="yes">mentioned</gi> element as a word.
 
<eg><![CDATA[<mentioned>grandiloquent</mentioned>]]></eg>
 
The first of the following two encodings is legitimate; the second is
not, since the <gi tei="yes">mentioned</gi> element is not part of the content
model of the <gi tei="yes">w</gi> element:
 
<eg><![CDATA[<!-- This is all right. -->
<mentioned><w>grandiloquent</w></mentioned>
 
<!-- This is NOT all right! -->
<w><mentioned>grandiloquent</mentioned></w>]]></eg>
 </p><p>On the other hand, both of the following encodings <emph>are</emph>
legitimate:
 
<eg><![CDATA[<mentioned><phr>grandiloquent speech</phr></mentioned>
 
<phr><mentioned>grandiloquent speech</mentioned></phr>]]></eg>
 
The first encoding describes the citing of a phrase. The second
describes a phrase which consists of something mentioned.
 <!-- added following brief plug for otherwise  unsung attributes -->
</p><p>The <gi tei="yes">w</gi> and <gi tei="yes">m</gi> attributes carry additional attributes
which may be of use in many indexing or analytic applications. The 
<att tei="yes">lemma</att> attribute may be used to specify  the
<term>lemma</term>, that is the head- or base- form of an
inflected verb or noun, for example:

<eg><![CDATA[<s lang=LA>
  <w lemma=timeo>timeo</w>
  <w lemma=danaii>Danaos</w>
  <w lemma=et>et</w>
  <w lemma=donum>dona</w>
  <w lemma=fero>ferentes</w>
</s>]]></eg>

Similarly, the <att tei="yes">baseform</att> attribute may be specified for the
<gi tei="yes">m</gi> element, to indicate the <soCalled>base form</soCalled> of
a transformed morpheme:
<eg><![CDATA[<w type=adjective>
  <m type=prefix baseform=con>com</m>
  <m type=root>fort</m>
  <m type=suffix>able</m>
</w>]]></eg>
</p><p>The <gi tei="yes">w</gi>, <gi tei="yes">m</gi> and <gi tei="yes">c</gi> elements can be used
together to give a fairly detailed low-level grammatical analysis of
text. For example, consider the following segmentation of the English
S-unit <cited>I didn't do it</cited>.
 
<eg><![CDATA[<w>I</w>
<w>
 <w>did</w>
 <m>n't</m>
 </w>
<w>do</w>
<w>it</w>
<c>.</c>]]></eg>
 </p><p>This segmentation, crude as it is, succeeds in representing the idea
that <cited>did</cited> occurs as a word inside the word
<cited>didn't</cited>. A further advantage of segmenting the text down
to this level is that it becomes relatively simple to associate each
such segment with a more detailed formal analysis. 
<!-- previous sentence is my rewording of the following wh confused me -->
<!-- In addition, by supplying the words, certain significant --><!-- morphemes (such as <cited>n't</cited> above), and special --><!-- characters (such as punctuation marks) with <att>id</att> --><!-- attributes, one is able to link these elements to other --><!-- elements which represent their analyses and interpretations --><!-- in systematic ways.  -->

This matter is taken up in detail in section <xref target="AILA"/>. 
 </p><p>The <gi tei="yes">s</gi>, <gi tei="yes">cl</gi>, <gi tei="yes">phr</gi>, <gi tei="yes">w</gi>, <gi tei="yes">m</gi>,
and <gi tei="yes">c</gi> elements are formally declared as follows:
 
<dtdFrag id="DAILC" n="Linguistic Segment Categories"><tagDecl tagDoc="S"/><tagDecl tagDoc="CL"/><tagDecl tagDoc="PHR"/><tagDecl tagDoc="W"/><tagDecl tagDoc="M"/><tagDecl tagDoc="C"/></dtdFrag>
 










<?tei:EOF p2ailc.odd ??>
<?tei:SOF p2aisp.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    **
    * $Log: p2aisp.odd,v $
    * Revision 1.7  1998/02/01 17:45:38  tei
    * *** empty log message ***
    *
    * Revision 1.6  98/01/28  11:44:14  cmsmcq
    * LB changes of Jan 1998 and RCS keywords added.
    * 
    *--><!-- Revisions:                                               --><!-- 5 Jan 98 : LB : fix 2 typos in egs --><!-- 26 feb: move description of ANA here --><!-- 93-11-26 : MSM : cosmetic and typos                      --><!-- 93-11-23 : MSM : provide correct pointer to saag for JOIN --><!-- 93-07-04 :  DTL :  Renumber to AIsp.  Change < fvp >     --><!--   to < span > and < fvpGrp > to < spanGrp >. Add         --><!--   < interp > and < interpGrp > tags, the first defined   --><!--   by omitting from= and to= from < span >, the second    --><!--   the corresponding grouping tag.  Change title to       --><!--   "Spans and Interpretations".  < span > has been        --><!--   removed from COnono section. Remove < analysis >       --><!--   tags.  Add Lessing example.                            --><!-- 30 Mar 93 :  LB renumber to AIfvp                        --><!-- 18 Jul 92 :  DTL :  Renumber from p2.444 to p2.445.      --><!-- 15 Jul 92 :  DTL :  Add < analysis > tags.               --><!-- 13 Jul 92 :  DTL :  Correct ODD tagging.                 --><!-- 01 Jul 92 :  DTL :  Define grouping tag < fvpGrp >.      --><!--   Assign section number p2.444.                          --><!-- 30 Jun 92 :  DTL :  Complete draft, modifying text from  --><!--   old section P2.234 on < span >. Change the Sigmund     --><!--   example to eliminate most anchors.  Make other changes --><!--   in the definition of < span > in accordance with an    --><!--   exchange between DTL and CMSMcQ on TEI-TECH in early   --><!--   June.  However, make from= required and to= optional,  --><!--   in conformity with their use in other pointing tags.   --><!--   Change name of tag to < fvp >. Rename type= as         --><!--   feature=.  Write TAGDOC.                               -->
 </p></div2><div2 id="AIATTS" name="subsection" ref="Y"><head>Global Attributes for Simple Analyses</head><p>When the tag set described by this chapter is selected, an
additional attribute is defined for all elements:
 
<adList classDoc="CLANA" atts="ana"/>
 
The <att tei="yes">ana</att> attribute may be specified for  any SGML element.
Its effect is to  associate the element with one or more others
representing an analysis or interpretation of it. Its target should be
one of the elements described in the section <xref target="AISP"/> below,
or some other interpretative element such as <gi tei="yes">note</gi>, on which 
see section <xref target="CONO"/> or <gi tei="yes">fs</gi>, on which see chapter<xref target="FS"/>
.

<!-- interp class should be a subclass of metadata maybe, except --><!-- that if interp includes note and fs their positions in tree --><!-- are constrained -->
<!-- Fixed problem raised by following comment. LB -->
 <!-- Oh, damn.  Just realized this obvious constraint means   --><!-- that INST probably should not be a global attribute at   --><!-- all, but instead a class with members SPAN, SPANGRP,     --><!-- INTERP, INTERPGRP, FS.  Hmm.  If you want to change it   --><!-- now, I'll agree; otherwise, let it wait for P4.  Or      --><!-- maybe we can provide a rationale / rationalization:      --><!-- (msm)                                                    -->
 <!-- deleted following para pending clarification -->
<!-- <p>When used on elements other than the overtly --><!-- interpretive <gi>span</gi>, <gi>interp</gi>, etc., the --><!-- <att>inst</att> attribute serves both to indicate that the --><!-- element bearing it is to be regarded in some sense as an --><!-- interpretive one, as well as serving to provide a link to --><!-- the text being interpreted.  It ought not, however, to be --><!-- used as a substitute for the <att>target</att> attributes --><!-- of <gi>note</gi> and other elements. -->
 <!-- why do we need INST  attribute anyway? I'd kill it if I hadnt --><!-- just spent an hour defining it, dammitall: whats the diff  --><!-- between inst and the various target attributes? I now suspect --><!-- it makes sense *only* as a global - and not much then! -->

 </p><p>The <att tei="yes">ana</att> attribute is formally declared as follows:
 
<dtdFrag id="DAIGA" n="Global attribute for analysis"><claDecl classDoc="CLANA" type="atts"/></dtdFrag>
</p></div2><div2 id="AISP" name="subsection" ref="Y"><head>Spans and Interpretations</head><p>The simplest mechanisms for attaching analytic notes in some
structured vocabulary to particular passages of text are provided by the
empty <gi tei="yes">span</gi> and <gi tei="yes">interp</gi> elements, and their associated
grouping elements <gi tei="yes">spanGrp</gi> and <gi tei="yes">interpGrp</gi>.
 
<tagList style="one-line"><tagDesc tagDoc="SPAN" atts="value from to"/><tagDesc tagDoc="SPANGRP"/><tagDesc tagDoc="INTERP" atts="value"/><tagDesc tagDoc="INTERPGP"/></tagList>
 </p><p>These elements are all members of the class <ident tei="yes" type="class">interpret</ident>, and thus share the following attributes:

<adList classDoc="CLINTERP" atts="resp type inst"/>
</p><p>The <att tei="yes">type</att> and <att tei="yes">value</att> attributes of the
<gi tei="yes">span</gi> and <gi tei="yes">interp</gi> elements may be used to associate an
interpretive name, type, and
value with a specific stretch (or <term>span</term>) of
text.  In the case of the <gi tei="yes">span</gi> element, the span of text being
annotated is indicated by values of the <att tei="yes">from</att> and
<att tei="yes">to</att> attributes, the value of each being a pointer.  If
the optional <att tei="yes">to</att> attribute is omitted, the span consists just
of the element pointed at by the obligatory <att tei="yes">from</att> attribute.
In the case of <gi tei="yes">interp</gi> (see below), the span is indicated by a
pointer from a <gi tei="yes">link</gi> element or some similar mechanism.  Here is
an example of the <gi tei="yes">span</gi> element.
 
<eg><![CDATA[<p id=MQP1S2P114>
<s id=MQP1S2P114S1>There was certainly a definite point
at which the thing began.</s>
 
<s id=MQP1S2P114S2>It was not; then it was suddenly
inescapable, and nothing could have frightened it
away.</s>
 
<s id=MQP1S2P114S3>There was a slow integration,
during which she, and the little animals, and the moving
grasses, and the sun-warmed trees, and the slopes of
shivering silvery mealies, and the great dome of blue
light overhead, and the stones of earth under her feet,
became one, shuddering together in a dissolution
of dancing atoms.</s>
 
<s id=MQP1S2P114S4>She felt the rivers under the ground
forcing themselves pain&shy;fully along her veins,
swelling them out in an unbearable pressure; her flesh
was the earth, and suffered growth like a ferment; and
her eyes stared, fixed like the eye of the sun.</s>
 
<s id=MQP1S2P114S5>Not for one second longer (if the
terms for time apply) could she have borne it; but then,
with a sudden movement forwards and out, the whole
process stopped; and <emph rend=italic>that</emph> was
<soCalled rend=dquo>the moment</soCalled> which it was
impossible to remember afterwards.</s>
 
<span resp=DTL
      value='the moment'
      from=MQp1s2p114s3
      to=MQp1s2p114s5>
 
<s id=MQP1S2P114S6>For during that space of time (which
was timeless) she understood quite finally her
smallness, the unimportance of humanity.</s>
 
<!-- ... -->
</p>]]></eg><!-- Doris Lessing, Martha Quest, 1952, p52-53  -->
 </p><p>The <gi tei="yes">span</gi> element may, as in this example, be placed in the
text near the textual span it is associated with, or it may be placed
outside the text enclosed within a <gi tei="yes">spanGrp</gi> element as follows.
 
<eg><![CDATA[<spanGrp resp=DTL>
  <span value='the moment' from=MQp1s2p114s3 to=MQp1s2p114s5>
</spanGrp>]]></eg>
 
As may be seen, the <att tei="yes">type</att> attribute may be omitted in order to
associate a span of text simply with a descriptive name.
 </p><p>Spans may also be used to represent the structural divisions assigned
to the narrative by an interpreter.  Consider the following narrative:
 
<q rend="display"><p>Sigmund, the son of Volsung, was a king in Frankish country.
Sinfiotli was the eldest of his sons, the second was Helgi, the
third Hamund.
Borghild, Sigmund's wife, had a brother named ----
But Sinfiotli, her stepson, and ---- both wooed the same woman
and Sinfiotli killed him over it.<note source="auth" place="foot" anchored="Y">The rule marks spaces
left for the missing name in the manuscript.</note>
And when he came home, Borghild asked him to go away,
but Sigmund offered her weregild, and she was obliged to accept it.
At the funeral feast Borghild was serving beer.  She took poison, a big
drinking horn full, and brought it to Sinfiotli.  When Sinfiotli looked
into the horn, he saw that poison was in it, and said to Sigmund <q>This
drink is cloudy, old man.</q> Sigmund took the horn and drank it off.
It is said that Sigmund was hardy and that poison did him no harm,
inside or out.  And all his sons could tolerate poison on their skin.
Borghild brought another horn to Sinfiotli, and asked him to drink, and
everything happened as before.  And a third time she brought him a horn,
and reproachful words as well, if he didn't drink from it.  He spoke
again to Sigmund as before.  He said <q>Filter it through your mustache,
son!</q> Sinfiotli drank it off and at once fell dead.
</p><p>Sigmund carried him a long way in his arms and came to a long,
narrow fjord, and there was a small boat there and a man in it.  He
offered to ferry Sigmund over the fjord.  But when Sigmund carried the
body out to the boat, it was fully laden.  The man said Sigmund should
go around the fjord inland.  The man pushed the boat out and then
suddenly vanished.
</p><p>King Sigmund lived a long time in Denmark in the kingdom of
Borghild, after he married her.  Then he went south to Frankish lands,
to the kingdom he had there.  Then he married Hiordis, the daughter of
King Eylimi.  Their son was Sigurd.  King Sigmund fell in a battle with
the sons of Hunding.  And then Hiordis married Alf, the son of King
Hialprec.  Sigurd grew up there as a boy.
</p><p>Sigmund and all his sons were tall and outstanding in their
strength, their growth, their intelligence, and their accomplishments.
But Sigurd was the most outstanding of all, and everyone who knows about
the old days says he was the most outstanding of men and the noblest of
all the warrior kings.</p></q><!-- "Fr&aacute; dau&eth;a Sinfi&otail;tla," in Edda:  Die    --><!-- Lieder des Codex Regius nebst verwandten                 --><!-- Denkm&auml;lern, ed.  Gustav Neckel, Vol.  I, Text, 4th  --><!-- ed. revised by Hans Kuhn (Heidelberg:  Carl Winter,      --><!-- 1962), pp. 162-3.  Tr. CMSMcQ                            -->
 </p><p>A structural analysis of this text, dividing it into narrative units
in a pattern shared with other texts from the same literature, might
look like this:
 
<eg><![CDATA[<p id=P1>
<s id=S1>Sigmund ... was a king in Frankish country.</s>
<s id=S2>Sinfiotli was the eldest of his sons.</s>
<s id=S3>Borghild, Sigmund's wife, had a brother ... </s>
<s id=S4A>But Sinfiotli ... wooed the same woman</s>
<s id=S4B>and Sinfiotli killed him over it.</s>
<s id=S5>And when he came home, ... she was obliged to accept it.</s>
<s id=S6>At the funeral feast Borghild was serving beer.</s>
<s id=S7>She took poison ... and brought it to Sinfiotli.</s>
<!-- ... -->
<s id=S17>Sinfiotli drank it off and at once fell dead.</s>
<anchor id=NIL1>
<p id=P2>Sigmund carried him a long way in his arms ... </p>
<p id=P3>King Sigmund lived a long time in Denmark ... </p>
<p id=P4>Sigmund and all his sons were tall ... </p>
 
<!-- ... -->
 
<span resp=TMA type='structural unit' value='introduction'
      from=S1 to=S3                                             >
<span resp=TMA type='structural unit' value='conflict'
      from=S4a                                                  >
<span resp=TMA type='structural unit' value='climax'
      from=S4b                                                  >
<span resp=TMA type='structural unit' value='revenge'
      from=S5 to=S17                                            >
<span resp=TMA type='structural unit' value='reconciliation'
      from=nil1                                                 >
<span resp=TMA type='structural unit' value='aftermath'
      from=P2 to=P4                                             >]]></eg>
 
Note the use of an empty <gi tei="yes">anchor</gi> element to provide a target for
the <soCalled>reconciliation</soCalled> unit which is normally part of
the narrative pattern but which is not realized in the text shown.
 </p><p>If groups of <gi tei="yes">span</gi> elements with the same <att tei="yes">resp</att> or
<att tei="yes">type</att> are used, as in this example, they may be grouped
together inside a <gi tei="yes">spanGrp</gi> element, with the values of the
common attribute(s) inherited from the higher element, as follows.
 
<eg><![CDATA[<spanGrp resp=TMA type='structural unit'>
 <span value='introduction'   from=S1   to=S3 >
 <span value='conflict'       from=S4a        >
 <span value='climax'         from=S4b        >
 <span value='revenge'        from=S5   to=S17>
 <span value='reconciliation' from=nil1       >
 <span value='aftermath'      from=P2   to=P4 >
 </spanGrp>]]></eg>
 </p><p>The same analysis may be expressed with the <gi tei="yes">interp</gi> element
instead of the <gi tei="yes">span</gi> element; this element provide attributes
for recording an interpretive category and its value, as well as the
identity of the interpreter, but does not itself indicate which passage
of text is being interpreted; the same interpretive structures can thus
be associated with many passages of the text.  The association between
text passages and <gi tei="yes">interp</gi> elements must be made either by
pointing from the text to the <gi tei="yes">interp</gi> element with the
<att tei="yes">ana</att> attribute defined in section <xref target="AIATTS"/>, or by
pointing at both text and interpretation from a <gi tei="yes">link</gi> element,
as described in chapter <xref target="SA" type="div1"/>.
 </p><p>To encode the first example above using <gi tei="yes">interp</gi>, it is
necessary to create a text element which contains --- or corresponds to
--- the the third, fourth, and fifth orthographic sentences (S-units) in
the paragraph.  This can be done either with the <att tei="yes">seg</att> element,
described in <xref target="SASE" type="div2"/>, or the <att tei="yes">join</att>
element, described in <xref target="SAAG" type="div2"/>.  The resulting
element can then be associated with the <gi tei="yes">interp</gi> element using the
<att tei="yes">ana</att> attribute described in section <xref target="AIATTS" type="div1"/>.  We illustrate using the <gi tei="yes">seg</gi> element.
 
<eg><![CDATA[<p id=MQP1S2P114>
<s id=MQP1S2P114S1>There was certainly a definite point ... </s>
<s id=MQP1S2P114S2>It was not; then it was suddenly inescapable ... </s>
<seg id=MQP1S2P114S3-5 ana=moment>
<s id=MQP1S2P114S3>There was a slow integration ... </s>
<s id=MQP1S2P114S4>She felt the rivers under the ground ... </s>
<s id=MQP1S2P114S5>Not for one second longer ... </s>
</seg>
<s id=MQP1S2P114S6>For during that space of time ... </s>
<!-- ... -->
</p>
<!-- ... -->
<interp id=MOMENT resp=DTL value='the moment'>]]></eg>
 </p><p>The second example above can be recoded using <gi tei="yes">interp</gi> and
<gi tei="yes">interpGrp</gi> tags in a similar manner.  The interpretation
itself can be expressed in an <gi tei="yes">interpGrp</gi> element, which would
replace the <gi tei="yes">spanGrp</gi> in the example shown above:
 
<eg><![CDATA[<interpGrp resp=TMA type='structural unit'>
 <interp id=INTRO    value='introduction'   >
 <interp id=CONFLICT value='conflict'       >
 <interp id=CLIMAX   value='climax'         >
 <interp id=REVENGE  value='revenge'        >
 <interp id=RECONCIL value='reconciliation' >
 <interp id=AFTERM   value='aftermath'      >
</interpGrp>]]></eg>
 </p><p>This <gi tei="yes">interpGrp</gi> element would be linked to the text either
by means of the <att tei="yes">ana</att> attribute, or by means of <gi tei="yes">link</gi>
elements.  Using the <att tei="yes">ana</att> attribute (on <gi tei="yes">seg</gi> elements
introduced specifically for this purpose), the text would be encoded as
follows:
 
<eg><![CDATA[ 
<p id=P1>
<seg id=S1-S3 ana=intro>
<s id=S1>Sigmund ... was a king in Frankish country.</s>
<s id=S2>Sinfiotli was the eldest of his sons.</s>
<s id=S3>Borghild, Sigmund's wife, had a brother ... </s>
</seg>
<s id=S4A ana=conflict>But Sinfiotli ... wooed the same woman</s>
<s id=S4B ana=climax>and Sinfiotli killed him over it.</s>
<seg id=S5-S17 ana=revenge>
<s id=S5>And when he came home, ... she was obliged to accept it.</s>
<s id=S6>At the funeral feast Borghild was serving beer.</s>
<!-- ... -->
<s id=S17>Sinfiotli drank it off and at once fell dead.</s>
</seg>
<anchor id=NIL1 ana=reconcil>
<p id=P2>Sigmund carried him a long way in his arms ... </p>
<p id=P3>King Sigmund lived a long time in Denmark ... </p>
<p id=P4>Sigmund and all his sons were tall ... </p>
<!-- ... -->
<join id=P2-P4 targets='P2 P3 P4' ana=afterm>]]></eg>
 </p><p>The linkage may also be accomplished using a <gi tei="yes">linkGrp</gi> element,
whose content is a set of <gi tei="yes">link</gi> elements which point to each
interpretive element and its corresponding text unit.  This method does
not require the use of the <att tei="yes">ana</att> attribute on the text
units.
 
<eg><![CDATA[<linkGrp resp=TMA targFunc='text interpretation'>
  <link targets='intro    S1-S3'>
  <link targets='conflict S4a'>
  <link targets='climax   S4b'>
  <link targets='revenge  S5-S17'>
  <link targets='reconcil nil1'>
  <link targets='afterm   P2-P4'>
</linkGrp>]]></eg>
 </p><p>One obvious advantage of using <gi tei="yes">interp</gi> rather than
<gi tei="yes">span</gi> elements for the Sigmund text is that the <gi tei="yes">interp</gi>
elements can be reused for marking up other texts in the same document,
whereas the <gi tei="yes">span</gi> elements cannot.  Another is that the
<gi tei="yes">interp</gi> element can be used to provide interpretations for
discontinuous text elements (represented by <gi tei="yes">join</gi> elements).  On
the other hand, the use of <gi tei="yes">interp</gi> elements may require the
creation of special text elements not otherwise needed (e.g. the
<gi tei="yes">seg</gi> and the <gi tei="yes">join</gi> in the revised encoding of the text),
whereas the the use of <gi tei="yes">span</gi> elements does not.
 </p><p>The formal declarations for the <gi tei="yes">span</gi>, <gi tei="yes">spanGrp</gi>,
<gi tei="yes">interp</gi> and <gi tei="yes">interpGrp</gi> elements are:
 
<dtdFrag id="DAISP" n="Spans"><tagDecl tagDoc="SPAN"/><tagDecl tagDoc="SPANGRP"/><tagDecl tagDoc="INTERP"/><tagDecl tagDoc="INTERPGP"/></dtdFrag><?tei:EOF p2aisp.odd ??>
<?tei:SOF p2aila.odd ??><!-- Revisions:  --><!-- 9 jan 94: LB: analysis is now called interpretation --><!-- 93-07-05 : DTL : renamed AIla, moved from CC per Eynsham --><!-- decision.  Redone to reconcile with rest of AI chapter.  --><!-- Some details and examples deleted.                       --><!-- 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)                              -->
 </p></div2><div2 id="AILA" name="subsection" ref="Y"><head>Linguistic Annotation</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 <xref target="CO"/>, <xref 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 <xref target="HD"/>, and in section <xref target="CCAH"/>.
 </p><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><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 tei="yes">interpretation</gi> element within the encoding
description of the TEI Header, as described in section <xref target="HD53"/>.<!-- To EDITORS from DTL:  Retain the next sentence here, or  --><!-- move it to CC chapter?                                   --><!-- Seems all right here, as a reminder.  (msm)              -->
Where different parts of a language corpus have used
different annotation methods, the <att tei="yes">decls</att>
attribute may be used to indicate the fact, as further
discussed in section <xref target="CCAS"/>.
 <!-- < div3 id=CCAN2 >< head >An Extended Example< / head> --></p><p>As one example of such types of analysis, consider the following
sentence, taken from the Lancaster/IBM Treebank Project.<note source="auth" place="display" anchored="Y"> 
See <citation> <author>G.  N. Leech and R. G. Garside,</author>
<title.p>Running a Grammar Factory,</title.p> in
<title>English Computer Corpora:
Selected Papers and Research Guide,</title>
ed. <editor>S. Johansson and A.-B. Stenstr&oslash;m</editor>
(Berlin: de Gruyter; New York:  Mouton, 1991),
pp. 15-32.</citation>
 
This sentence and its analysis are reproduced by kind permission of the
University of Lancaster's Unit for Computer Research on the English
Language.
 <!-- Stenstrom's name changed from oelig, on theory that      --><!-- he's Scandinavian not French.  Pls check.  -MSM          -->
 <!-- she's Swedish. Please restore her o-slash (LB) --></note>
 <!-- [N [G The_AT victim_NN1 's_$ G] friends_NN2 N] [V told_VVD  --><!-- [N police_NN2 N] [Fn that_CST [N Krueger_NP1 N] [V [V&   --><!-- drove_VVD [P into_II [N the_AT quarry_NN1 N]P]V&]        --><!-- and_CC [V+ never_RR surfaced_VVD V+]V]Fn]V] ._.          -->
 
<q rend="display">The victim's friends told police that Kruger drove into the quarry
and never surfaced.</q>
 </p><p>Our discussion focuses on the way that this sentence might be
analysed using the Claws system developed at the University of
Lancaster, but exactly the same principles may be applied to a wide
variety of other systems.
 
<note source="auth" place="display" anchored="Y">For the word-class tagging method used by Claws see
 
<citation><author>I. Marshall</author>,
<title.p>Choice of Grammatical Word Class without Global Syntactic
Analysis:  Tagging Words in the LOB Corpus,</title.p>
in
<title>Computers and the Humanities</title>
<detail>17 (1983): 139-50.</detail>.</citation>
 
For an overview of the system see
 
<citation><author>R. G. Garside, G. N. Leech, and G. R. Sampson,</author>
<title>The Computational Analysis of English: a Corpus-Based
Approach</title>
(Oxford:  Oxford University Press, 1991).</citation></note>
 
Output from the system consists of a segmented and tokenized version of
the text, in which word class codes have been associated with each
token.  For our example sentence, we might conveniently represent these
codes using entity references:
 
<note source="auth" place="foot" anchored="Y">We have replaced the Claws code <code tei="yes" type="frag">&dollar;</code>
for the <cited>'s</cited> morpheme by <code tei="yes" type="frag">GEN</code>, as in the tag
set used by the British National Corpus (see <xref target="FSIL"/>), and
the code <code tei="yes" type="frag">.</code> for the final full stop by
<code tei="yes" type="frag">PUN</code>.</note>
 
<eg><![CDATA[<s>The&AT victim&NN1;'s&GEN friends&NN2 told&VVD police&NN2
that&CST Krueger&NP1  drove&VVD into&II the&AT
quarry&NN1  and&CC  never&RR surfaced&VVD;.&PUN
</s>]]></eg>
 
The names used for these entity references have some significance for
the human reader (<code tei="yes" type="frag">AT</code> for <term>article</term>,
<code tei="yes" type="frag">NN1</code> for <term>singular noun</term>, <code tei="yes" type="frag">NN2</code> for
<term>plural noun</term>, etc.), but their representation in the
output from an SGML system processing the document may be adjusted, by
varying the entity declarations, to suit the convenience of whatever
analytic software is to be used.  For example, if the SGML parser
operating on this sentence uses a set of entity declarations in the
following form, then the word class tags will simply disappear from
the output.
 
<eg><![CDATA[<!ENTITY AT "">
<!ENTITY NN1 "">
<!ENTITY GEN "">
<!-- ... -->]]></eg>
 
Alternatively, suppose the entity set in use follows the following
pattern:
 
<eg><![CDATA[<!ENTITY AT  "[definite article]">
<!ENTITY NN1 "[singular noun]">
<!ENTITY GEN "[genitive suffix]">
<!-- ... -->]]></eg>
 
Then the sample sentence will be processed by an SGML-aware processor as
if it began:
 
<eg><![CDATA[The[definite article] victim[singular noun]'s[genitive suffix] ...]]></eg>
 </p><p>It would be more useful if the replacement texts for each entity
were a code of some significance to a particular analysis program.  If
the codes are considered to be <term>atomic</term>, then one of the
mechanisms based on the <gi tei="yes">interp</gi> element described in section<xref target="AISP"/>
 is sufficient.  If the codes are considered to be
compositional (for example that <code tei="yes" type="frag">NN1</code> and <code tei="yes" type="frag">NN2</code>
have something in common, namely their <term>noun-ness</term>, which
they do not share with, say, <code tei="yes" type="frag">VVD</code>), then this
compositionality may be most clearly expressed using a mechanism based
on the <gi tei="yes">fs</gi> element defined in chapter <xref target="FS"/>.  For a
detailed example, see <xref target="FSIL"/>.
 </p><p>One such replacement for the word-class entity references above
is a set of empty <gi tei="yes">ptr</gi> elements bearing <att tei="yes">target</att>
attributes as described in section <xref target="COXR"/>.  The required
entity definitions would look as follows.
 
<eg><![CDATA[<!ENTITY   AT   "<ptr target=AT>" >
<!ENTITY   NN1  "<ptr target=NN1>">
<!ENTITY   GEN  "<ptr target=GEN>">
<!-- ... -->]]></eg>
 
Then the text would be expanded to read:
 
<eg><![CDATA[<s>The<ptr target=AT> victim<ptr target=NN1>'s<ptr target=GEN>
friends<ptr target=NN2> told<ptr target=VVD> police
<ptr target=NN2> that<ptr target=CST> Krueger<ptr target=NP1>
drove<ptr target=VVD> into<ptr target=II> the<ptr target=AT>
quarry<ptr target=NN1 and<ptr target=CC> never<ptr target=RR>
surfaced<ptr target=VVD>.<ptr target=PUN>
</s>]]></eg>
 </p><p>The <gi tei="yes">ptr</gi> elements are designed to point to elements with
unique identifiers.  But we have yet to specify what those elements are.
Suppose we say that they are <gi tei="yes">interp</gi> elements whose values are the
same as their identifiers.  That is, we provide an <gi tei="yes">interpGrp</gi>
element as follows:
 
<eg><![CDATA[<interpGrp type='word classes'>
  <interp id=AT  value=AT>
  <interp id=NN1 value=NN1>
  <interp id=GEN value=GEN>
  <!-- ... -->
</interpGrp>]]></eg>
 </p><p>Although common practice, this (or any similar) method of relating
text to interpretation is seriously flawed.  The interpretations are
related not to text elements, but to points in the text, namely those
that are occupied by the <gi tei="yes">ptr</gi> elements.  In order to relate the
interpretation to the appropriate text units, a uniform convention needs
to be applied; for example, that an interpretation relates to all the
text material preceding the <gi tei="yes">ptr</gi> element that points to it up to
the immediately preceding <gi tei="yes">ptr</gi>, or up to the <gi tei="yes">s</gi> that
delimits the S-unit containing that <gi tei="yes">ptr</gi> element, whichever is
nearer.  While this convention works with texts that are marked up
solely with <gi tei="yes">ptr</gi> elements that point to interpretation elements,
it does not work with texts with additional markup, for example
<gi tei="yes">ptr</gi> elements that are used for some other purpose.  In addition,
the convention fails for any markup in which interpretations are
intended to be associated with nested text elements.
 </p><p>None of these difficulties arise if the text is fully segmented, using
the linguistic segment elements described in section <xref target="AILC"/>,
and the <att tei="yes">ana</att> attribute to point to the interpretations
that are associated with each such segment, as follows:
 
<eg><![CDATA[<s type=sentence>
<w ana=AT >The</w>
<w ana=NN1>victim</w>
<m ana=GEN>'s</m>
<w ana=NN2>friends</w>
<w ana=VVD>told</w>
<w ana=NN2>police</w>
<w ana=CST>that</w>
<w ana=NP1>Krueger</w>
<w ana=VVD>drove</w>
<w ana=II >into</w>
<w ana=AT >the</w>
<w ana=NN1>quarry</w>
<w ana=CC >and</w>
<w ana=RR >never</w>
<w ana=VVD>surfaced</w>
<c ana=PUN>.</c>
</s>]]></eg>
 </p><p>Analysis into phrase and clause elements can be superimposed on the
word and morpheme tagging in the preceding illustration. For example,
Claws provides the following constituent analysis of the sample sentence
(the word class codes have been deleted):
 
<q rend="display">[N [G The victim's G] friends N] [V told [N police N] [Fn that [N
Krueger N] [V [V&amp; drove [P into [N the quarry N]P]V&amp;]
and [V+ never surfaced V+]V]Fn]V]</q>
 </p><p>Treating the labels on the brackets as phrase or clause
interpretations, this analysis of the structure of the example sentence
can be combined with the word class analysis and represented as follows
(the symbol <code tei="yes" type="frag">V&amp;</code> representing the first part of a coordinate
phrase, has been replaced by <code tei="yes" type="frag">V1</code>, and <code tei="yes" type="frag">V+</code>, representing the
second part, has been replaced by <code tei="yes" type="frag">V2</code>).
 
<eg><![CDATA[<s type=sentence>
<phr ana=N>
  <phr ana=G>
    <w ana=AT>The</w>
    <w ana=NN1>victim</w>
    <m ana=GEN>'s</m>
    </phr>
  <w ana=NN2>friends</w>
  </phr>
<phr ana=V>
  <w ana=VVD>told</w>
  <phr ana=N><w ana=NN2>police</w></phr>
  <cl ana=Fn>
    <w ana=CST>that</w>
    <phr ana=N><w ana=NP1>Krueger</w></phr>
    <phr ana=V>
      <phr ana=V1>
        <w ana=VVD>drove</w>
        <phr ana=P>
          <w ana=II>into</w>
          <phr ana=N>
            <w ana=AT>the</w>
            <w ana=NN1>quarry</w>
            </phr>
          </phr>
        </phr>
      <w ana=CC>and</w>
      <phr ana=V2>
        <w ana=RR>never</w>
        <w ana=VVD>surfaced</w>
        </phr>
      </phr>
    </cl>
  </phr>
<c ana=PUN>.</c>
</s>]]></eg>
 </p><p>A representation using the <gi tei="yes">linkGrp</gi> element can be obtained by
supplying each linguistic segment with its own <att tei="yes">id</att> attribute,
removing its <att tei="yes">ana</att> attribute, and putting each
segment-interpretation pair into a <gi tei="yes">link</gi> element inside the
<gi tei="yes">linkGrp</gi> element.
 <!-- < div3 id=CCAN3>< head>Non-nesting Structures< / head> --></p><p>Each linguistic segment so far discussed has been well-behaved with
respect to the basic document hierarchy, having only a single parent.
Moreover, the segmentation has been complete, in that each part of the
text is accounted for by some segment at each level of analysis, without
discontinuities or overlap.  This state of affairs does not of
course apply in all types of analysis, and these Guidelines provide a
number of mechanisms to support the representation of discontinuities or
multiple analyses.  A brief overview of these facilities is provided in
chapter <xref target="NH"/>; also see <xref target="SA"/>.  These mechanisms
all depend to a greater or lesser degree on the ability to associate a
unique identifier with any element in a TEI-conformant text, and then to
specify that identifier as the target of a pointing element of some kind.
 <!-- < div3 id=CCAN4>< head>Further Examples< / head> --></p><p>The mechanisms proposed in this chapter may also be used to encode
analyses of an entirely different kind, for example discourse function.
Here is an application of the span technique to record details of a sales
transaction in a spoken text.
 
<eg><![CDATA[<u who=P1 id=U1>Can I have ten oranges and a kilo of 
    bananas please?</u>
<u who=P2 id=U2>Yes, anything else?</u>
<u who=P1 id=U3>No thanks.</u>
<u who=P2 id=U4>That'll be dollar forty.</u>
<u who=P1 id=U5>Two dollars</u>
<u who=P1 id=U6>Sixty, eighty, two dollars. Thank you.</u>
 
<spanGrp type=transactions>
  <span from=U1 value='sale request'>
  <span from=U2 to=U3 value='sale compliance'>
  <span from=U4 value='sale'>
  <span from=U5 value='purchase'>
  <span from=U6 value='purchase closure'>
  </spanGrp>]]></eg><!-- R. Hasan, Language, context, and text... OUP1989, p 59 -->
 
For further discussion of the <gi tei="yes">u</gi> (utterance) element and other
elements recommended for transcriptions of spoken language, see chapter<xref target="TS"/>
.<?tei:EOF p2aila.odd ??>
</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ai.odd ??><!-- 15 Analysis --><?tei:SOF p2fs.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2fs.odd,v $
    * Revision 1.7  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.6  94/03/27  16:29:54  lou
    * semifinal check
    * 
    * Revision 1.3  1994/01/04  01:39:13  msmcq
    * revision for P3
    * --><!-- Chapter FS : Feature Structures                          --><!-- Revisions:                                               --><!-- 94-01-03 : MSM : Added RCS id                            --><!-- 93-06-28 : DTL : second round of post-Eynsham changes.   --><!-- Add < msr > and < rate > tags with special attributes to --><!-- express measurement and rate values; include in section  --><!-- on symbolic, numeric and string values.  Add valueTo=    --><!-- attribute to < nbr >, < msr > and < rate > tags to       --><!-- express range of numerical values.  Revise examples.     --><!-- Revise other sections, changing examples, etc. Eliminate --><!-- < vTerm > and < fTerm > tags; use < alt > tag to express --><!-- systematic alternation, and alternation of groups of     --><!-- features and values.  Change description of effect of not--><!-- specifying optional features (equivalent to treating them--><!-- as having < uncertain > rather than < default > values). --><!-- Revise treatment of rel=ne regarding presence of < none >--><!-- in equivalent alternation. Remove rel= from < vAlt >,    --><!-- < any >, < none >, < plus >, < minus >. < default >.     --><!-- Remove rel=sb and rel=ns from < sym >, < nbr >.          --><!-- Justify using rel=sb and rel=ns with different           --><!-- interpretations for < str >, < fs > and < f >.           --><!-- Delete section on echoes and remove < echo > from content--><!-- models for feature structure elements.                   --><!-- Make name= attribute required for < f >.                 --><!-- Revise DTD and entity definitions for value tags.        --><!-- See file FS3.dtd                                         --><!-- Add illustration of phobic dog text from the BNC via DD. --><!-- Order of sections:                                       --><!-- FSin Introduction                                        --><!-- FSbi Elementary Feature Structures: Features with Binary --><!--      Values                                              --><!-- FSfl Feature, Feature Structure and Feature Value        --><!--      Libraries                                           --><!-- FSsy Symbolic, Numeric, Measurement, Rate and String     --><!--      Values                                              --><!-- FSst Structured Values                                   --><!-- FSss Singleton, Set, Bag and List Collections of Values  --><!-- FSal Alternative Features and Feature Values             --><!-- FSbo Boolean, Default and Uncertain Values               --><!-- FSrl Indirect Specification of Values using the REL      --><!--      Attribute                                           --><!-- FSil An Extended Illustration                            --><!-- 93-05-25 : DTL : first round of post-Eynsham changes.    --><!-- Add < fvLib > ("feature-value library")                  --><!-- and fVal= attribute on < f >.  Revise BNC classification --><!-- example based on corrections from DD.  Eliminate fsVal=  --><!-- attribute on < f >; use fVal= instead.  Add footnote     --><!-- for attribution of work on chapter.                      --><!-- Add section FSfl, add < fLib > ("feature library") tag;  --><!-- add feats= attribute on < fs >.  Revise examples and add --><!-- examples suggested by DD and DG at Eynsham.  Add omitted --><!-- end tags in examples.                                    --><!-- 93-04-12 : MSM : add N values to dtdfrags                --><!-- 93-04-09 : MSM : change div levels                       --><!-- 93-04-08 : MSM : change idrefs to new values             --><!-- 92-12-18 : MSM : correct some simple tagging problems    --><!-- 92-12-16 : MSM : fixes to tagdocs                        --><!-- 92-12-16 : MSM : muck with comments at top               --><!-- 92-12-10 : DTL : Make minor corrections to previous      --><!-- revisions.  Change title of p2.4468 to "Subsumed and     --><!-- Negated Values".  Change title of p2.4464 (FSss) to      --><!-- "Singleton, Set, Bag and List Values".  Change           --><!-- org=unit to org=single (for "singleton"), per GS.  Add   --><!-- rel=sb and rel=ns to remaining value elements for        --><!-- which rel= is defined.  For those elements, rel=eq and   --><!-- rel=sb are equivalent.  rel=ne and rel=sb are also       --><!-- equivalent for < any > and < none >; they differ for     --><!-- the other tags in this domain in that rel=sb does not    --><!-- include the possibility of < none >, whereas rel=ne      --><!-- does.                                                    --><!-- 92-12-06 : DTL :  Exchange order of sections p2.4464     --><!-- (FSss) and p2.4465 (FSal).  Rename new section p2.4464   --><!-- (FSss) as "Unit, Set, Bag and List Values".  Rename new  --><!-- section p2.4465 (FSal) as "Alternative Values".          --><!-- Exchange order of sections p2.4466 (FSag) and p2.4467.   --><!-- Rename new section p2.4466 (FSag) as "Alternative        --><!-- Feature Groups".  Add =bag to value list for org=;       --><!-- change =atom to =unit as a possible value for org=.      --><!-- Default value for org= is #IMPLIED, so that it can be    --><!-- set in the < fDecl > in the FSD.  Change the content     --><!-- model for < f > to permit any number of occurrences of   --><!-- values.  However, < f org=unit > with more than one      --><!-- value is understood as only having its first value.      --><!-- Allow rel= on < f > to permit subsumption of sets, bags  --><!-- and lists (e.g., < f org=set rel=sb >< v1 >< v2 >...<    --><!-- vn > is understood as any subset of the values < v1 >,   --><!-- < v2 >,...< vn >).                                       --><!-- Eliminate < valGrp > and add the tags < vAlt >, < fAlt   --><!-- >, < vTerm > and < fTerm > on the grounds that the       --><!-- only boolean operator that needs to be separately        --><!-- tagged is alternation (disjunction).  However,           --><!-- alternation of values < vAlt > (discussed in p2.4465 (FSal))    --><!-- needs to be distinguished from alternation of features   --><!-- (discussed in p2.4466).  Moreover, values and features   --><!-- may have to be grouped within these tags, for which <    --><!-- vTerm > and < fTerm > are used.  Exclusive and           --><!-- inclusive alternation can be distinguished               --><!-- contextually, so the distinction does not have to be     --><!-- explicitly indicated.  Restore rel=sb and rel=ns to <    --><!-- fs >, and revise section p2.4468 accordingly.            --><!-- Redefine %fFamily; parameter entity as follows:          --><!-- < !ENTITY % fFamily      " f | fAlt " >                  --><!-- Eliminate %allVal1; and %allVal2; parameter              --><!-- entities, and define %singVal; and %multVal; parameter   --><!-- entities as follows:                                     --><!--   < !ENTITY % singVal      "                             --><!--     %booleanVal; | null | default |                      --><!--     uncertain " >                                        --><!--   < !ENTITY % multVal      "                             --><!--     %binaryVal; | sym | nbr |                            --><!--     str | fs | vAlt " >                                  --><!--                                                          --><!-- 02 Aug 92 : DTL : Add new section p2.4465 on the org=    --><!-- attribute for < f > defined as taking the values         --><!-- =atom, =set and =list.  Add < null > tag to represent    --><!-- the null set and the null list.  Change the content      --><!-- model for < f > to allow for multiple occurrences of <   --><!-- fs >, < sym >, < nbr > and < str >, understood as        --><!-- grouped by < valGrp type=conj >; decision stimulated     --><!-- by GS's desire to be able to leave off top level of      --><!-- such grouping tags in recasting old < unit > and <       --><!-- level > material in terms of < fs > and < f >.           --><!-- Renumber all subsequent sections accordingly.            --><!-- Extensively rewrite material in section p2.4466 on       --><!-- boolean values, reintroduce "underspecification", and    --><!-- mention "subsumption" in that section per GS.  Add       --><!-- discussion of obligatory, optional and obligatorily      --><!-- absent features in feature structures in that section.   --><!-- Eliminate =sb and =ns as possible values of rel= on <    --><!-- fs >, restoring original default =eq, and rewrite        --><!-- material in section p2.4468 on < fs rel=ne >.            --><!-- Eliminate =le, etc. as possible values of rel= on <      --><!-- sym >.  Rename =integer as =int.  Rewrite TAGDOCS and    --><!-- redo parameter entity definitions yet again, as          --><!-- follows.                                                 --><!--  < !ENTITY % booleanVal   " any | none " >               --><!--  < !ENTITY % binaryVal    " plus | minus " >             --><!--  < !ENTITY % simpleVal    " %booleanVal; |               --><!--    %binaryVal; | default | null " >                      --><!--  < !ENTITY % emptyVal     " %simpleVal; | uncertain |    --><!--    sym | nbr "    >                                      --><!--  < !ENTITY % allVal1      " %emptyVal;                   --><!--    | str | fs | valGrp "         >                       --><!--  < !ENTITY % allVal2 " %simpleVal; | uncertain | valGrp | --><!--    (sym)+ | (nbr)+ | (str)+ | (fs)+ "       >            --><!--  < !ENTITY % fFamily      " f | fGrp " >                 --><!-- 26 Jul 92 : DTL : Rename "boolean" as "binary", rename   --><!-- "underspecification" as "boolean".  Add discussion of    --><!-- the difference between the boolean and the binary        --><!-- elements.  Add rel=sb and rel=ns to < fs > per GS, and   --><!-- provide examples and analyses.                           --><!-- 24 Jul 92 : DTL : Renumber section to p2.446.  Expand    --><!-- on description of < fs rel=ne >.  Redo the section on    --><!-- underspecification and uncertainty, after further        --><!-- discussion with GS.  Make other minor changes.           --><!-- 21 Jul 92 : DTL : Define < uncertain > as < valGrp       --><!-- type=excl > < any >< none >< /valGrp >, per GS.          --><!-- Change description of distribution of rel=ne             --><!-- specification on < fs >, based on comments from GS.      --><!-- Make additional corrections and changes.                 --><!-- 18 Jul 92 : DTL : Change cross-references to other       --><!-- sections of part p2.44.  Allow < uncertain > within <    --><!-- valGrp >, per GS.  Refer to < fDecl > rather than to <   --><!-- fDeclarations >, per GS.  Drop use of "simple" and       --><!-- "primitive" as descriptions of certain groups of value   --><!-- tags, per GS.  Correct result of "distributing" rel=ne   --><!-- within < fs >, per GS.  Note (here) that GS suggests     --><!-- using a cert= attribute on value tags to indicate        --><!-- degree of certainty.  This seems like a good idea but    --><!-- perhaps best to defer.                                   --><!-- 16 Jul 92 : DTL : Change < link > to < echo >.  Divide   --><!-- old section p2.4472 into two parts, put material on      --><!-- rel= into separate section and renumber accordingly.     --><!-- Distribute < tagDecl >s among the various sections.      --><!-- Rename some sections.  Change content model of < f >     --><!-- to allow no content.  Add fsVal= attribute to < f >      --><!-- defined as IDREF for pointing at < fs > or < valGrp >    --><!-- made up exclusively of < fs >s.  Add sections on use     --><!-- of < echo > and disambiguation using widely available    --><!-- select= attribute.  Add footnote for references.         --><!-- 14 Jul 92 : DTL : Additional minor changes, including    --><!-- specifying attribute names in example tags even when     --><!-- they can be omitted, e.g. rel=.  Correct the markup of   --><!-- "sinks" example.                                         --><!--                                                          --><!-- 12 Jul 92 : DTL : Change domain= to rel=, and            --><!-- grouping= to type= on < valGrp > and < fGrp > in         --><!-- response to comments from LB.  Change =self to =eq and   --><!-- =cmp to =ne.  Allow values =lt, =le, =ge and =gt for     --><!-- rel= on < sym > and < str >, in addition to < nbr >.     --><!-- Divide into subsections and promote original             --><!-- subsection p2.4471 to new section p2.448, per LB.  Add   --><!-- new examples and discussion.                             --><!-- 08 Jul 92 : DTL : Make additional minor changes.         --><!-- 07 Jul 92 :  LB : Correct ODD tagging.                   --><!-- 07 Jul 92 : DTL : Make minor changes.  Complete draft    --><!-- of section 2.4471.                                       --><!-- 06 Jul 92 : DTL : Disallow < uncertain > in content      --><!-- model of < valGrp > as not meaningful.  Remove < fsGrp   --><!-- > as unnecessary, given < valGrp >.  Redefine            --><!-- parameter entities as follows:                           --><!--  < !ENTITY % boolean.val                                 --><!--  " plus | minus "     >                                  --><!--  < !ENTITY % primitive.val                               --><!--  " any | none | default | %boolean.val; "  >             --><!--  < !ENTITY % simple.val                                  --><!--  " sym | nbr | str | %primitive.val; " >                 --><!--  < !ENTITY % definite.val                                --><!--  " valGrp | fs | %simple.val; " >                        --><!--  < !ENTITY % all.val                                     --><!--  " uncertain | %definite.val; " >                        --><!--  < !ENTITY % f.family                                    --><!--  " f | f.grp " >                                         --><!-- 05 Jul 92 : DTL : Remove < some > and < all >.           --><!-- Replace < unknown > and < noclaim > by < uncertain >,    --><!-- latter not specified for domain=.  Revise text in        --><!-- accordance with these changes.  Change content model     --><!-- of < valGrp > to be any combination of values,           --><!-- including combinations of structured and simple          --><!-- values, per GS.  Change content model of < str > to      --><!-- #PCDATA, per LB.  Change content model of < fsLib > to   --><!-- ((fs | link)*), per GS.  Change default of name= of      --><!-- < f > to #IMPLIED.  Change type of name= of < f > to     --><!-- NMTOKEN.  Add fsType=, with type of CDATA, and fNames=   --><!-- with type of NMTOKENS, to < fsLib >, to provide for      --><!-- inheritance by contained < fs >s of type=, and by        --><!-- their top-level features of name=.  Make other           --><!-- editorial changes.  Write TAGDOCs.  Begin subsection     --><!-- p2.4471 on relating analyses and instances.              --><!-- 03 Jul 92 : DTL : Complete first draft.  Changes from    --><!-- ver 1.14 of LING DTD: < *.grp > become < *Grp > for *    --><!-- = {f, fs, val}; < fs.lib > becomes < fsLib >;            --><!-- < no.claim > becomes < noclaim >.                        --><div1 id="FS" n="16" name="Faisal" ref="Y"><head>Feature Structures</head><div2 id="FSIN" name="Incunabula" ref="Y"><head>Introduction</head><p>A <term>feature structure</term> is a general purpose data structure,
which identifies and groups together individual <term>features</term>,
each of which associates a name with one or more
values.
 <!-- <note place=foot>The fundamental ideas expressed in this --><!-- chapter were formulated by Mitch Marcus and Beatrice --><!-- Santorini of the Analysis and Interpretation committee of --><!-- the Text Encoding Initiative at a meeting of the committee --><!-- at The University of Arizona in March 1990.  Following their --><!-- publication in the first version of the Guidelines, they --><!-- were put into their present form by D. Terence Langendoen, --><!-- with extensive help from Steven Zepp and Gary Simons. --><!-- Dominic Dunlop provided the BNC classification example and, --><!-- together with Daniel Greenstein, inspired the encoding of --><!-- the phobic dog example.</note> -->
 
Because of the generality of feature structures, they can be used to
represent many different kinds of information, and interrelations among
various pieces of information, and their instantiation in SGML in these
guidelines provides a <term>metalanguage</term> for representing text
analysis and interpretation.  Moreover, this instantiation allows
feature values to be of various <term>types</term>, and for restrictions
to be placed on the values for particular features, by means of
<term>feature system declarations</term>, which are discussed in chapter<xref target="FD"/>
.  These restrictions provide the basis for at least
partial validation of the feature-structure encodings that are used.<!--  Following note deleted at DTB's suggestions: "I've said --><!-- before that this seems a very strange reference. I think --><!-- this note should be deleted. We don't cite sources of other --><!-- ideas in these Guidelines." -->
<!-- <note place=foot>The fundamental properties of feature --><!-- structures are discussed by Donald Knuth in <title>The Art --><!-- of Computer Programming, Vol.  I: Fundamental --><!-- Algorithms</title>, 1968, who used the term --><!-- <term>node</term> for feature structure and the term --><!-- <term>field</term> for feature.  More recent treatments in --><!-- the linguistics literature include Stuart Shieber, <title>An --><!-- Introduction to Unification-based Approaches to --><!-- Grammar</title>, 1986, and Fernando Pereira, <title>Grammars --><!-- and Logics of Partial Information</title>, 1987.  For --><!-- justification of the way in which feature structure systems --><!-- have been represented here in these guidelines, see --><!-- D. Terence Langendoen and Gary F. Simons, <title.p>A --><!-- Rationale for the TEI Recommendations for Feature-Structure --><!-- Markup</title.p>, to appear in <title>Computers in the --><!-- Humanities</title>.</note> --></p><p>This chapter is organized as follows.  Following this introduction,
section <xref target="FSBI"/> introduces the <term>binary</term> feature
values, and shows how elementary feature structures using features with
those values may be constructed.  Section <xref target="FSFL"/> introduces
the tags that represent <term>libraries</term> of features, feature
<!-- DTB suggests that fLib and fsLib should be renamed fGrp and --><!-- fsGrp for consistency with other aggregates; I agree (LB) -->

structures and feature values, along with methods for pointing at
features, feature structures and feature values in these libraries.
Section <xref target="FSSY"/>, presents the tags for <term>symbolic</term>,
<term>numeric</term>, <term>measurement</term>, <term>rate</term>, and
<term>string</term> values.  Section <xref target="FSST"/>, shows how to
use feature-structures themselves as values, thus enabling feature
structures to be recursively defined.  Section <xref target="FSSS"/>
demonstrates the use of multiple values for features, for encoding
<term>set</term>, <term>bag</term>, and <term>list</term> collections of
values.  Section <xref target="FSAL"/> presents various methods for
representing alternations (disjunctions) of features and feature values.
Section <xref target="FSBO"/>, presents tags for <term>boolean</term>,
<term>default</term>, and <term>uncertain</term> values, along with
methods for <term>underspecifying</term> feature values.  Section<xref target="FSRL"/>
 shows how to specify various logical relations, such as
negation and subsumption, between the expressed values for a feature and
its actual values.  Finally, section <xref target="FSIL"/>, illustrates how
feature structures may be linked to to text elements.</p><p>This tag set is selected as described in <xref target="STIN"/>; in a
document which uses the markup described in this chapter, the document
type declaration should contain the following declaration of the entity
<ident tei="yes" type="pe">TEI.fs</ident>, or an equivalent one:
 
<eg><![CDATA[<!ENTITY % TEI.fs 'INCLUDE'>]]></eg>
 
The entire document type declaration for a document using this
additional tag set together with the base tag set for prose might look
like this:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY TEI.prose     'INCLUDE' >
    <!ENTITY TEI.fs  'INCLUDE' >
 ]>]]></eg></p><p>The overall document type declaration for this additional tag set
has the following structure:
 
<dtdFrag id="DFS" n="Feature Structures" file="teifs2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><dtdRef dtdFrag="DFSBI"/><dtdRef dtdFrag="DFSFL"/><dtdRef dtdFrag="DFSSY"/><dtdRef dtdFrag="DFSSS"/><dtdRef dtdFrag="DFSAL"/><dtdRef dtdFrag="DFSBO"/></dtdFrag></p></div2><?tei:SOF p2fsbi.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2fsbi.odd,v $
# Revision 1.3  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.2  1994/01/04  01:39:13  msmcq
# revision for P3
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : cosmetic change to heading              --><!-- 94-03-30 : MSM : strip FILE att from dtdfrag             --><!-- 94-01-03 : MSM : Added RCS id                            --><div2 id="FSBI" name="Incunabula" ref="Y"><head>Elementary Feature Structures:  Features with Binary Values</head><p>The fundamental elements of a feature structure system are <gi tei="yes">f</gi>
(for <term>feature</term>) and <gi tei="yes">fs</gi> (for <term>feature
structure</term>).  The <gi tei="yes">fs</gi> element has a <att tei="yes">type</att>
attribute for indicating what type of feature structure it represents,
and may contain any number of <gi tei="yes">f</gi> elements.  An <gi tei="yes">f</gi>
element, in turn, has a required <att tei="yes">name</att> attribute and any
number of associated <term>values</term>.  Feature values may be binary,
numeric, symbolic (i.e. taken from a restricted set of legal values), or
string-valued, or may consist of sets, lists, or bags of binary,
numeric, symbolic, or string values.  Specialized values may also be
given which allow partial underspecification of the feature.  These
possible types of values are described in more detail in this and the
following sections.
 </p><p>This section considers
the special case of feature structures that contain features whose
single value is one of the <term>binary values</term> represented by the
empty elements <gi tei="yes">plus</gi> and <gi tei="yes">minus</gi>.  The elements which are
used for representing feature structures, features and the binary
values, along with their descriptions and attributes, are the following.
 
<tagList style="one-line"><tagDesc tagDoc="FSTAG" atts="type feats rel"/><tagDesc tagDoc="F" atts="name org fVal rel"/><tagDesc tagDoc="PLUS"/><tagDesc tagDoc="MINUS"/></tagList>
 
The attributes not discussed in this section are discussed in following
sections as follows: the <att tei="yes">feats</att> and the <att tei="yes">fVal</att>
attributes in section <xref target="FSFL"/>, the <att tei="yes">rel</att> attribute
in section <xref target="FSRL"/>, and the <att tei="yes">org</att> attribute in
section <xref target="FSSS"/>.
 </p><p>An <gi tei="yes">fs</gi> element containing <gi tei="yes">f</gi> elements with binary
values can be straightforwardly used to encode the <term>matrices</term>
of feature-value specifications for phonetic segments, such as the
following for the English segment [s].
 <!-- Adapted from Noam Chomsky and Morris Halle, The Sound    --><!-- Pattern of English.  New York:  Harper & Row, 1968, p.   --><!-- 415.                                                     -->
 
<eg><![CDATA[+---          ---+
| + consonantal  |
| - vocalic      |
| - voiced       |
| + anterior     |
| + coronal      |
| + continuant   |
| + strident     |
+---          ---+]]></eg>
 </p><p>Using the additional tag set for feature structures, this might be
encoded as follows.  Note that <gi tei="yes">fs</gi> elements may have a
<att tei="yes">type</att> attribute indicating the kind of feature structure in
question.
 
<eg><![CDATA[<fs type='phonological segment'>
  <f name=consonantal><plus></f>
  <f name=vocalic>    <minus></f>
  <f name=voiced>     <minus></f>
  <f name=anterior>   <plus></f>
  <f name=coronal>    <plus></f>
  <f name=continuant> <plus></f>
  <f name=strident>   <plus></f>
  </fs>]]></eg>
 
The restriction of specific features to specific types of values (e.g.
the restriction of the feature <cited>strident</cited> to the values
<tag compl="full" tei="yes">plus</tag> or <tag compl="full" tei="yes">minus</tag>) cannot be validated by an SGML
parser.  To enable an application program to check that only legal
values for particular features appear, one may write a
<term>feature-system declaration</term>; see chapter <xref target="FD"/>.
 </p><p>Here are the formal declarations of the <gi tei="yes">fs</gi>, <gi tei="yes">f</gi>,
<gi tei="yes">plus</gi> and <gi tei="yes">minus</gi> elements.
 
<dtdFrag id="DFSBI" n="Feature structures, binary values"><tagDecl tagDoc="FSTAG"/><tagDecl tagDoc="F"/><tagDecl tagDoc="PLUS"/><tagDecl tagDoc="MINUS"/></dtdFrag><?tei:EOF p2fsbi.odd ??><?tei:SOF p2fsfl.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2fsfl.odd,v $
    * Revision 1.4  1998/01/31 19:56:11  tei
    * remove extendarg from eg
    *
    * Revision 1.3  94/03/21  14:12:04  lou
    * second mass typo clearup
    * 
    * Revision 1.2  1994/01/04  01:39:13  msmcq
    * revision for P3
    * --><!-- Revisions:                                               --><!-- 94-01-03 : MSM : add BODY element to example             --><!-- 94-01-03 : MSM : Added RCS id                            --><!-- 93-12-23 : MSM : in example change ARGS att to targFunc  --><!-- 93-12-22 : MSM : fix a problem in an example             -->
 </p></div2><div2 id="FSFL" name="Incunabula" ref="Y"><head>Feature, Feature-Structure and Feature-Value Libraries</head><p>As the example in the preceding section illustrates, the direct
encoding of features structures can be verbose.  Consequently, the effort
of encoding large numbers of feature structures in this manner could be
enormous, and could result in the creation of enormous files.  To reduce
the size and complexity of the task of encoding feature structures, one
may use the <att tei="yes">feats</att> attribute of the <gi tei="yes">fs</gi> element to point
to one or more of the features of that element.  This indirect method of
encoding feature structures presumes that the <gi tei="yes">f</gi> elements are
assigned unique SGML <att tei="yes">id</att> values, and are collected together in
<gi tei="yes">fLib</gi> elements (<term>feature libraries</term>).  In turn, feature
structures can be collected together in <gi tei="yes">fsLib</gi> elements
(<term>feature-structure libraries</term>).  Finally, one may use the
<att tei="yes">fVal</att> attribute of the <gi tei="yes">f</gi> element to point to its
values.  This indirect method of encoding feature values presumes that
the value elements are assigned <att tei="yes">id</att> specifications, and are
collected together in <gi tei="yes">fvLib</gi> elements (<term>feature-value
libraries</term>).  The elements which are used for representing feature,
feature-structure and feature-value libraries, along with their
descriptions and attributes, are the following.
 
<tagList style="one-line"><tagDesc tagDoc="FLIB" atts="type"/><tagDesc tagDoc="FSLIB" atts="type"/><tagDesc tagDoc="FVLIB" atts="type"/></tagList>
 </p><p>For example, suppose a feature library for phonological feature
specifications is set up as follows.
 
<eg><![CDATA[<fLib type='phonological features'>
  <f id=CNS1 name=consonantal><plus> </f>
  <f id=CNS0 name=consonantal><minus></f>
  <f id=VOC1 name=vocalic>    <plus> </f>
  <f id=VOC0 name=vocalic>    <minus></f>
  <f id=VOI1 name=voiced>     <plus> </f>
  <f id=VOI0 name=voiced>     <minus></f>
  <f id=ANT1 name=anterior>   <plus> </f>
  <f id=ANT0 name=anterior>   <minus></f>
  <f id=COR1 name=coronal>    <plus> </f>
  <f id=COR0 name=coronal>    <minus></f>
  <f id=CNT1 name=continuant> <plus> </f>
  <f id=CNT0 name=continuant> <minus></f>
  <f id=STR1 name=strident>   <plus> </f>
  <f id=STR0 name=strident>   <minus></f>
<!-- ... -->
  </fLib>]]></eg>
 </p><p>Then the feature structures that represent the analysis of the
phonological segments (phonemes) <code tei="yes" type="frag">/t/</code>, <code tei="yes" type="frag">/d/</code>,
<code tei="yes" type="frag">/s/</code> and <code tei="yes" type="frag">/z/</code> can be defined as follows.
 
<eg><![CDATA[<fs feats='cns1 voc0 voi0 ant1 cor1 cnt0 str0'></fs>
<fs feats='cns1 voc0 voi1 ant1 cor1 cnt0 str0'></fs>
<fs feats='cns1 voc0 voi0 ant1 cor1 cnt1 str1'></fs>
<fs feats='cns1 voc0 voi1 ant1 cor1 cnt1 str1'></fs>]]></eg>
 </p><p>The preceding are but four of the 128 logically possible fully
specified phonological segments using the seven binary features listed in
the feature library.  Presumably not all combinations of features
correspond to phonological segments (there are no strident vowels, for
example).  The legal combinations, however, can be collected together in a
<term>feature-structure library</term>, with each element being given a
unique <att tei="yes">id</att> attribute, as in the following example.
 
<eg><![CDATA[<fsLib id=FSL1 type='phonological segment definitions'>
<!-- ... -->
  <fs id=T.df feats='cns1 voc0 voi0 ant1 cor1 cnt0 str0'></fs>
  <fs id=D.df feats='cns1 voc0 voi1 ant1 cor1 cnt0 str0'></fs>
  <fs id=S.df feats='cns1 voc0 voi0 ant1 cor1 cnt1 str1'></fs>
  <fs id=Z.df feats='cns1 voc0 voi1 ant1 cor1 cnt1 str1'></fs>
<!-- ... -->
  </fsLib>]]></eg>
 </p><p>Text elements can be linked to these feature structures in any of the
ways described in section <xref target="AIATTS" type="div2"/>.  In the
following example, a <gi tei="yes">linkGrp</gi> element is used to link selected
characters in the text <cited>Caesar seized control</cited> to their
phonological representations.
 
<eg><![CDATA[<text id=TXT1> <!-- ... -->
<body> <!-- ... -->
<ab id=S1>
  <w id=S1W1>
    <c id=S1W1C1>C</c>ae<c id=S1W1C2>s</c>ar</w>
  <w id=S1W2>
    <c id=S1W2C1>s</c>ei<c id=S1W2C2>z</c>e<c id=S1W2C3>d</c></w>
  <w id=S1W3>
    con<c id=S1W3C1>t</c>rol</w>.
</ab>
<!-- ... -->
</body></text>
 
<fsLib id=FSL1 type='phonological segment definitions'>
<!-- as in previous example -->
  </fsLib>
 
<linkGrp type='phonological identification of characters'
    domains='fsl1 txt1'
    targFunc='phonological.segment character' >
<!-- ... -->
  <link id=LT targets='s.df s1w3c1'>
  <link id=LD targets='z.df s1w2c3'>
  <link id=LS targets='s.df s1w1c1'>
  <link id=LS targets='s.df s1w2c1'>
  <link id=LZ targets='z.df s1w1c2'>
  <link id=LZ targets='z.df s1w2c2'>
 
<!-- ... -->
  </linkGrp>]]></eg>
 </p><p>Because of the simplicity of the binary feature values, there is no
particular gain in pointing at those values rather than specifying them
directly.  However, the mechanism of using the <att tei="yes">fVal</att> attribute
on <gi tei="yes">f</gi> elements is useful for representing more complex feature
values, and can be illustrated using binary values.  Suppose the
<gi tei="yes">plus</gi> and <gi tei="yes">minus</gi> elements are collected together in a
<gi tei="yes">fvLib</gi>, as follows.
 
<eg><![CDATA[<fvLib type='binary values'>
  <plus  id=B1>
  <minus id=B0>
  </fvLib>]]></eg>
 
Then the feature library presented at the beginning of this section can be
represented as follows.
 
<eg><![CDATA[<fLib type='phonological features'>
  <f id=CNS1 name=consonantal fVal=b1></f>
  <f id=CNS0 name=consonantal fVal=b0></f>
  <f id=VOC1 name=vocalic     fVal=b1></f>
  <f id=VOC0 name=vocalic     fVal=b0></f>
  <f id=VOI1 name=voiced      fVal=b1></f>
  <f id=VOI0 name=voiced      fVal=b0></f>
  <f id=ANT1 name=anterior    fVal=b1></f>
  <f id=ANT0 name=anterior    fVal=b0></f>
  <f id=COR1 name=coronal     fVal=b1></f>
  <f id=COR0 name=coronal     fVal=b0></f>
  <f id=CNT1 name=continuant  fVal=b1></f>
  <f id=CNT0 name=continuant  fVal=b0></f>
  <f id=STR1 name=strident    fVal=b1></f>
  <f id=STR0 name=strident    fVal=b0></f>
<!-- ... -->
  </fLib>]]></eg>
 </p><p>Although <gi tei="yes">fs</gi> elements are legitimate feature values (see
section <xref target="FSST"/>), they are not allowed within <gi tei="yes">fvLib</gi>
elements.  They should be placed in <gi tei="yes">fsLib</gi> elements.
 </p><p>Here are the formal declarations of the <gi tei="yes">fLib</gi>, <gi tei="yes">fsLib</gi>
and <gi tei="yes">fvLib</gi> elements.
 
<dtdFrag id="DFSFL" n="Feature libraries" file="teifs2"><tagDecl tagDoc="FLIB"/><tagDecl tagDoc="FSLIB"/><tagDecl tagDoc="FVLIB"/></dtdFrag><?tei:EOF p2fsfl.odd ??><?tei:SOF p2fssy.odd ??><!-- Revisions:                                               --><!-- 94-01-03 : MSM : Added RCS id                            --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2fssy.odd,v $
# Revision 1.3  1994/03/21  14:12:06  lou
# second mass typo clearup
#
# Revision 1.2  1994/01/04  01:39:13  msmcq
# revision for P3
# -->
 </p></div2><div2 id="FSSY" name="Incunabula" ref="Y"><head>Symbolic, Numeric, Measurement, Rate and String Values</head><p>By separating out feature values as content of <gi tei="yes">f</gi> elements, we
are able to classify those values into <term>types</term>.  In section<xref target="FSBI" type="div2"/>
, the two empty elements which represent
binary values are defined.  In this section, we define five more
feature-value elements:  the empty elements <gi tei="yes">sym</gi> for expressing
<term>symbolic values</term>, <gi tei="yes">nbr</gi> for expressing <term>numeric
values</term>, <gi tei="yes">msr</gi> for expressing <term>measurement
values</term>, and <gi tei="yes">rate</gi> for expressing <term>rate values</term>;
and the element <gi tei="yes">str</gi> for expressing <term>string values</term>.
These elements, along with their descriptions and attributes, are the
following.
 
<tagList style="one-line"><tagDesc tagDoc="SYM" atts="value rel"/><tagDesc tagDoc="NBR" atts="value valueTo type rel"/><tagDesc tagDoc="MSR" atts="unit value valueTo type rel"/><tagDesc tagDoc="RATE" atts="unit per value valueTo type rel"/><tagDesc tagDoc="STR" atts="rel"/></tagList>
 </p><p>The <gi tei="yes">sym</gi> element is to be used for the value of a feature when
that feature can have any of a small, finite set of possible values,
representable as character strings.  For example, consider the problem of
specifying the grammatical <term>case</term>, <term>gender</term> and
<term>number</term> features of classical Greek noun forms.  Assuming that
the case feature can take on any of the five values
<code tei="yes" type="frag">nominative</code>, <code tei="yes" type="frag">genitive</code>, <code tei="yes" type="frag">dative</code>,
<code tei="yes" type="frag">accusative</code> and <code tei="yes" type="frag">vocative</code>; that the gender feature
can take on any of the three values <code tei="yes" type="frag">feminine</code>,
<code tei="yes" type="frag">masculine</code>, and <code tei="yes" type="frag">neuter</code>; and that the number
feature can take on either of the values <code tei="yes" type="frag">singular</code> and
<code tei="yes" type="frag">plural</code>, then the following may be used to represent the claim
that noun form <cited>the&aacute;s</cited> <gloss>goddesses</gloss> has
accusative case, feminine gender and plural number.
 
<eg><![CDATA[<fs type='word structure'>
<!-- ... -->
  <f name=case><sym value=accusative></f>
  <f name=gender><sym value=feminine></f>
  <f name=number><sym value=plural></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>Note that instead of using a symbolic value for grammatical number, one
could have named the feature <term>singular</term> or <term>plural</term>
and given it an appropriate binary value, as in the following example.
Whether one uses a binary or symbolic value in situations like this is
largely a matter of taste.
 
<eg><![CDATA[<fs type='word structure'>
<!-- ... -->
  <f name=case><sym value=accusative></f>
  <f name=gender><sym value=feminine></f>
  <f name=singular><minus></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>An SGML validator by itself cannot determine that particular values do
or do not go with particular features; in particular, it cannot
distinguish between the presumably legal encodings in the preceding two
examples and the presumably illegal encoding in the following example.
 
<eg><![CDATA[<!-- *PRESUMABLY ILLEGAL* ... -->
<fs type='word structure'>
<!-- ... -->
  <f name=case><sym value=feminine></f>
  <f name=gender><sym value=accusative></f>
  <f name=number><minus></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>There are two ways of attempting to ensure that only legal combinations
of feature names and values are used.  First, if the total number of legal
combinations is relatively small, one can simply list all of those
combinations in <gi tei="yes">fLib</gi> elements (together possibly with
<gi tei="yes">fvLib</gi> elements), and point to them using the <att tei="yes">feats</att>
attribute in the enclosing <gi tei="yes">fs</gi> element.  This method is suitable in
the situation described above, since it requires specifying a total of
only ten (5 + 3 + 2) combinations of features and values.  Further, to
ensure that the features are themselves combined legally into feature
structures, one can put the legal feature structures inside
<gi tei="yes">fsLib</gi> elements.  A total of 30 feature structures (5 x 3 x 2) is
required to enumerate all the legal combinations of individual case,
gender and number values in the preceding illustration.  Of course, the
legality of the markup requires that the <att tei="yes">feat</att> attributes
actually point at legally defined features, which an SGML validator, by
itself, cannot guarantee.
 </p><p>A more general method of attempting to ensure that only legal
combinations of feature names and values are used is to provide a
feature system declaration which includes a <gi tei="yes">valRange</gi> element
for each feature one uses.  Here is a sample <gi tei="yes">valRange</gi> element
for the <tag compl="full" tei="yes">f name=case</tag> element described above; for further
discussion of the <gi tei="yes">valRange</gi> element, see chapter <xref target="FD"/>; the <gi tei="yes">vAlt</gi> element is discussed in section <xref target="FSAL"/>.
 
<eg><![CDATA[<!-- VALRANGE specification for CASE feature -->
<valRange>
  <vAlt>
    <sym value=nominative>
    <sym value=genitive>
    <sym value=dative>
    <sym value=accusative>
    <sym value=vocative>
    </vAlt>
  </valRange>]]></eg>
 </p><p>Similarly, to ensure that only legal combinations of features are used
as the content of feature structures, one should provide
<gi tei="yes">fsConstraint</gi> elements for each of the types of feature structure
one employs.  For discussion of the <gi tei="yes">fDecl</gi> and
<gi tei="yes">fsConstraint</gi> elements, see <xref target="FD"/>.  Validation of the
feature structures used in a document based on the feature-system
declaration, however, requires that there be an application program that
can use the information contained in the feature-system declaration.
 </p><p>Features with <tag compl="full" tei="yes">sym</tag>, <tag compl="full" tei="yes">plus</tag>, and <tag compl="full" tei="yes">minus</tag>
values may be used to encode highly structured information such as may be
obtained from precoded survey instruments.  We illustrate by means of a
coding scheme based on the one that is used for classifying potential
printed entries in the British National Corpus.  The scheme uses the
following features and associated values.
 
<list type="gloss"><label>medium</label><item>books and magazines; miscellaneous; written to be spoken</item><label>domain</label><item>imaginative; applied science; arts; belief and thought;
commerce and finance; leisure; natural and pure science; social science;
world affairs</item><label>level</label><item>high; medium; low</item><label>sampling range</label><item>beginning; middle; end; whole; whole less ten percent</item><label>date of origination</label><item>1960-1975; 1975-1993</item><label>published (miscellaneous items only)</label><item>yes; no</item><label>selection method (books and periodicals only)</label><item>chosen on grounds of circulation or influence; chosen at random</item></list>
 </p><p>A comprehensive feature library for this scheme is the following; the
<att tei="yes">id</att> specifications are those currently used in the BNC project.
 
<eg><![CDATA[<fLib type='BNC classification features'>
  <f id=CA002 name=medium><sym value=book.or.periodical></f>
  <f id=CA003 name=medium><sym value=miscellaneous></f>
  <f id=CA004 name=medium><sym value=written.to.be.spoken></f>
  <f id=CA005 name=domain><sym value=imaginative></f>
  <f id=CA006 name=domain><sym value=applied.science></f>
  <f id=CA007 name=domain><sym value=arts></f>
  <f id=CA008 name=domain><sym value=belief.and.thought></f>
  <f id=CA009 name=domain><sym value=commerce.and.finance></f>
  <f id=CA00A name=domain><sym value=leisure></f>
  <f id=CA00B name=domain><sym value=natural.and.pure.science></f>
  <f id=CA00C name=domain><sym value=social.science></f>
  <f id=CA00D name=domain><sym value=world.affairs></f>
  <f id=CA00E name=level><sym value=high></f>
  <f id=CA00F name=level><sym value=medium></f>
  <f id=CA00G name=level><sym value=low></f>
  <f id=CA00H name=sample.type><sym value=beginning></f>
  <f id=CA00J name=sample.type><sym value=middle></f>
  <f id=CA00K name=sample.type><sym value=end></f>
  <f id=CA00L name=sample.type><sym value=whole></f>
  <f id=CA00M name=sample.type><sym value=whole.less.ten.percent></f>
  <f id=CA00N name=published.between><sym value=1960.1975></f>
  <f id=CA00P name=published.between><sym value=1975.1993></f>
  <f id=CA00R name=published><plus></f>
  <f id=CA00S name=published><minus></f>
  <f id=CA00T name=selection.method><sym value=principled></f>
  <f id=CA00U name=selection.method><sym value=random></f>
  </fLib>]]></eg>
 </p><p>An entry which is a book or periodical on world affairs, medium level,
sampled from the middle, published between 1975 and 1993, and selected on
a principled basis could then be assigned the following feature-structure
code; this code could also be placed in a feature-structure library that
contains all the possible fully-specified BNC entry classifications.  This
library would have a total of 1620 (3 x 9 x 3 x 5 x 2 x 2) entries.
 
<eg><![CDATA[<fs type='BNC classification for written documents'
    id=CA2DFJPT
    feats='CA002 CA00D CA00F CA00J CA00P CA00T'></fs>]]></eg>
 </p><p>The <gi tei="yes">nbr</gi> element is to be used when the value of a feature is a
number or a range of numbers.  For example, suppose one wishes to encode
information contained in classified advertisements for the sale or rental
of real estate, such as the number of bedrooms and bathrooms in a listed
property, and its advertised selling or rental price.  One way of
representing such information is as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <f name=number.of.bathrooms><nbr value=2></f>
  <f name=number.of.bedrooms><nbr value=3></f>
  <f name=monthly.rent><nbr value=625.00></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>The information that the number of bedrooms is in the range from 3 to 5
and the monthly rent is in the range from 625.00 to 950.00 may be
represented as follows, using the optional <att tei="yes">valueTo</att> attribute.
 
<eg><![CDATA[  <f name=number.of.bedrooms><nbr value=3 valueTo=5></f>
  <f name=monthly.rent><nbr value=625.00 valueTo=950.00></f>]]></eg>
 </p><p>The <gi tei="yes">nbr</gi> (and also the <gi tei="yes">msr</gi> and <gi tei="yes">rate</gi> elements
defined below) element also may have a <att tei="yes">type</att> attribute to
specify whether the values of the <att tei="yes">value</att> and <att tei="yes">valueTo</att>
attributes are to be construed as integer or real numbers.
 </p><p>The <gi tei="yes">msr</gi> element to be used when the value of a feature is a
scalar quantity, essentially a combination of a numeric value and a
symbolic value for identifying the scale on which the numeric value
occurs.  For example, real estate listings often provide the area (in
square feet or meters) of a house or apartment and the area (in acres or
hectares) of land being sold or rented.  One way of representing
information about such areas is as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <f name=interior.area><msr unit=sq.ft value=2000></f>
  <f name=property.area><msr unit=acre value=0.5></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>The value of the <tag compl="full" tei="yes">f name=monthly.rent</tag> feature in the two
examples above might be more accurately analysed as a measurement rather
than as a numeric value, since the amount of the rent in question is to
be understood as payable in a particular currency, such as US or
Canadian dollars or Italian lire.  To make the currency scale explicit,
the first example of this feature might be re-encoded as follows.
 
<eg><![CDATA[  <f name=monthly.rent><msr unit=USD value=625.00></f>]]></eg>
 </p><p>The <att tei="yes">unit</att> and <att tei="yes">value</att> attributes of the
<gi tei="yes">msr</gi> element are both required.  If the <att tei="yes">unit</att>
attribute is not needed (for example, if no confusion would result if
the <att tei="yes">unit</att> attribute is not specified), then the <gi tei="yes">nbr</gi>
element may be used to express the feature value.
 </p><p>The <gi tei="yes">rate</gi> element is to be used when the value of a feature
is a rate.  This element has a required <att tei="yes">per</att> attribute for
expressing the interval over which the rate is measured (typically, but
not necessarily, a temporal interval), and an optional <att tei="yes">unit</att>
attribute for expressing the scalar unit.  For example, one can encode
the wage rate of USD $8.25 per hour as follows.
 
<eg><![CDATA[  <f name=wage.rate><rate value=8.25 unit=USD per=hour></f>]]></eg>
 
Note that the <tag compl="full" tei="yes">f name=monthly.rent</tag> element illustrated above can be
re-encoded as having a rate value, with a <att tei="yes">per=month</att> attribute,
as follows.
 
<eg><![CDATA[  <f name=rent><rate value=625.00 unit=USD per=month></f>]]></eg>
 </p><p>To encode interest, inflation or tax rates, the <att tei="yes">unit</att>
attribute can be used to indicate that the <att tei="yes">value</att> attribute is
to be understood as a percentage.  For example, an interest rate of 8.25%
per year can be encoded in either of the following two ways.
 
<eg><![CDATA[  <f name=interest><rate unit=percent value=8.25 per=year></f>
 
  <f name=interest><rate value=0.0825 per=year></f>]]></eg>
 </p><p>Finally, the <gi tei="yes">str</gi> element is to be used for the value of a
feature when that value is a string drawn from a very large or potentially
unbounded set of possible strings of characters, so that it would be
impractical or impossible to use the <gi tei="yes">sym</gi> element.  These values
are expressed not as the values of the <att tei="yes">value</att> attribute, as in
the case of symbolic, numeric, measurement and rate values, but as the
content of the <gi tei="yes">str</gi> element.  For example, one may encode the
street address of a property in a real estate listing, as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <f name=address><str>3418 East Third Street</str></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>Here are the formal declarations of the <gi tei="yes">sym</gi>, <gi tei="yes">nbr</gi>,
<gi tei="yes">msr</gi>, <gi tei="yes">rate</gi> and <gi tei="yes">str</gi> elements.
 
<dtdFrag id="DFSSY" n="Symbolic, etc. values" file="teifs2"><tagDecl tagDoc="SYM"/><tagDecl tagDoc="NBR"/><tagDecl tagDoc="MSR"/><tagDecl tagDoc="RATE"/><tagDecl tagDoc="STR"/></dtdFrag><?tei:EOF p2fssy.odd ??><?tei:SOF p2fsst.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $log: $
    *
    *--><!-- Revisions:                                               --><!-- 94-01-03 : MSM : correct exx:  join takes targets, not parts --><!-- 93-12-23 : MSM : in example change ARGS att to targFunc  -->
 </p></div2><div2 id="FSST" name="Incunabula" ref="Y"><head>Structured Values</head><p>Features may have <term>structured values</term> as well; these
values are represented by either the <gi tei="yes">fs</gi> element, or the
<att tei="yes">fVal</att> attribute on the <gi tei="yes">f</gi> element, which can point
to an <gi tei="yes">fs</gi> element.  Since an <gi tei="yes">fs</gi> or a pointer to an
<gi tei="yes">fs</gi> is permitted to occur as a value of an <gi tei="yes">f</gi>,
recursion is possible. For example, an <gi tei="yes">fs</gi> element may contain
or point to an <gi tei="yes">f</gi> element, which may contain or point to an
<gi tei="yes">fs</gi> element, which may contain or point to an <gi tei="yes">f</gi>
element, and so on.  To illustrate the use of structured values,
consider the following simple model of a personal record, consisting
of a person's name, date of birth, place of birth, and sex.  Each
personal record is a <tag compl="full" tei="yes">fs type='personal record'</tag> tag,
consisting of the corresponding four features, three of which take
structured values, as in the following example.
 
<eg><![CDATA[<fs type='personal record'>
  <f name=full.name>
    <fs type='name record'>
      <f name=first.name><str>Kathleen</str></f>
      <f name=middle.name><str>Anne</str></f>
      <f name=surname><str>Barnett</str></f>
      </fs>
    </f>
  <f name=date.of.birth>
    <fs type='date record'>
      <f name=year><nbr value=1968></f>
      <f name=month><nbr value=4></f>
      <f name=day><nbr value=17></f>
      </fs>
    </f>
  <f name=place.of.birth>
    <fs type='place record'>
      <f name=city><str>Austin</str></f>
      <f name=state><sym value=TX></f>
      </fs>
    </f>
  <f name=sex><sym value=female>
  </fs>]]></eg>
 </p><p>Now suppose that feature-structure libraries are maintained for name
records and place records, and that the name record in the previous
example is identified with the attribute <att tei="yes">id=Nkab027</att> and the
place record is identified with the attribute <att tei="yes">id=txaustin</att>.
 
<note source="auth" place="foot" anchored="Y">Feature-structure, rather than feature-value, libraries
should be used for housing collections of feature structures.</note><!-- EM says: why is this necessary? Search me, guv. -->
 
Then the preceding example could also be encoded as follows.  (An
identifier is also provided for the personal record.)
 
<eg><![CDATA[<fs id=PKAB027 type='personal record'>
  <f name=full.name fVal=Nkab027></f>
  <f name=date.of.birth>
    <fs type='date record'>
      <f name=year><nbr value=1968></f>
      <f name=month><nbr value=4></f>
      <f name=day><nbr value=17></f>
      </fs>
    </f>
  <f name=place.of.birth fVal=txaustin></f>
  <f name=sex><sym value=female>
  </fs>]]></eg>
 
This representation could be simplified further if a feature library is
maintained for the year, month, day and sex features, so that the
<att tei="yes">feats</att> attribute may be used as follows.
 
<eg><![CDATA[<fs id=PKAB027 type='personal record' feats='sxf'>
  <f name=full.name fVal=Nkab027></f>
  <f name=date.of.birth>
    <fs type='date record' feats='y1968 m04 d17'></fs>
    </f>
  <f name=place.of.birth fVal=txaustin></f>
  </fs>]]></eg>
 </p><p>Next, suppose that a feature-structure library is also maintained
for personal records, and that the library also contains records for
the parents of the individual identified in the previous example.  Suppose
that the father is identified as Pmfb009 and the mother as Parn002.  Then
the personal-record feature structure could be easily augmented to
include pointers to the parents, as follows.
 
<eg><![CDATA[<fs id=PKAB027 type='personal record' feats='sxf'>
  <f name=full.name fVal=Nkab027></f>
  <f name=date.of.birth>
    <fs type='date record' feats='y1968 m04 d17'></fs>
    </f>
  <f name=place.of.birth fVal=austinTX></f>
  <f name=mother fVal=Parn002>
  <f name=father fVal=Pmfb009>
  </fs>]]></eg>
 
If the personal records identified as Parn002 and Pmfb009 also contain
information about the parents of those individuals, then from the present
record, one would have access to that individual's grandparents as well.
 </p><p>Assuming that personal records of the sort described in this
section are being maintained in association with text files, the
records can be linked to those texts in any of the ways described in
chapter <xref target="SA"/>, provided that identifiers are added for
appropriate features, as in the following illustration.
 
<eg><![CDATA[<text id=BFILE><body>
<!-- ... -->
<div id=TKAB027 type='birth certificate'>
<p><name type=person id=T1KAB027>Kathleen Anne Barnett</name>
was born at <time id=T1T0659>6:59 a.m.</time> on
<date id=T1D680417>April 17, 1968</date> in
<name type=org id=T1SETONHSP>Seton Hospital</name> in
<name type=place id=T1TXAUSTIN>Austin</name>
to <seg id=S1>Mr.</seg> and <seg id=S2>Mrs.</seg>
<name type=person id=T1MFB009>Michael F. Barnett</name> of
<name type=place id=T1SANSABATX>San Saba</name>.
<!-- ... -->
<join id=T1ARN002 targets='s2 T1mfb009'>
<join id=T2MFB009 targets='s1 T1mfb009'>
<!-- ... -->
</body></text>
 
<fsLib id=PREC type='personal records'>
<!-- ... -->
<fs id=PKAB027 type='personal record' feats='sxf'>
  <f name=full.name fVal=Nkab027></f>
  <f id=DKAB027 name=date.of.birth>
    <fs type='date record' feats='y1968 m04 d17'></fs>
    </f>
  <f id=BKAB027 name=place.of.birth fVal=txaustin></f>
  <f id=MKAB027 name=mother fVal=Parn002></f>
  <f id=FKAB027 name=father fVal=Pmfb009></f>
  </fs>
<!-- ... -->
</fsLib>
 
<linkGrp  type='record verification'
          domains='Bfile Prec'
          targFunc='source goal'>
<!-- ... -->
  <link targets='T1kab027 Nkab027'>
  <link targets='T1d680417 Dkab027'>
  <link targets='T1txaustin Bkab027'>
  <link targets='T1arn002 Mkab027'>
  <link targets='T2mfb009 Fkab027'>
<!-- ... -->
  </linkGrp>]]></eg>


<?tei:EOF p2fsst.odd ??><?tei:SOF p2fsss.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2fsss.odd,v $
    * Revision 1.5  1998/02/01 17:45:38  tei
    * killing off extendargs
    *
    * Revision 1.4  94/03/21  14:12:05  lou
    * second mass typo clearup
    * 
    * Revision 1.2  1994/01/04  01:39:13  msmcq
    * revision for P3
    * --><!-- Revisions:                                               --><!-- 94-01-03 : MSM : suppress unnamed F in example           --><!-- 94-01-03 : MSM : Added RCS id                            --></p></div2><div2 id="FSSS" name="Incunabula" ref="Y"><head>Singleton, Set, Bag and List Collections of Values</head><p>In the discussion to this point, we have assumed that features have
exactly one simple value.  However, for many purposes, it is useful to be
able to consider the values of certain features to be organized in more
complex ways, for example as sets, bags (or multisets), or lists.
Accordingly, we provide for four different ways in which feature values
may be organized, namely as <term>singletons</term>, <term>sets</term>,
<term>bags</term> and <term>lists</term>.  We do so by means of an
<att tei="yes">org</att> attribute on the <gi tei="yes">f</gi> element, which takes on one of
the designated values <code tei="yes" type="frag">single</code>, <code tei="yes" type="frag">set</code>,
<code tei="yes" type="frag">bag</code>, and <code tei="yes" type="frag">list</code>.  A feature whose value is
organized as a singleton is understood as having exactly one simple value.
If more than one value is specified for it, we assume that only the first
one is considered to be its true value.  A feature whose value is
organized as a set, bag or list may have any positive number of values as
its content.  Sets and bags are distinguished from lists in that the order
in which the values are specified does not matter for the former, but does
matter for the latter.  Sets are distinguished from bags and lists in that
repetitions of values do not count for the former but do count for the
latter.  SGML does not provide a way of validating that values for
features organized as sets are not repeated; such validation would have to
be carried out by an application program.  Our method of representing set,
bag and list values also does not permit such values to be directly
embedded within one another.  In order to embed a set within a set, for
example, one must specify the embedded set as the value of a feature of a
feature-structure value of the including set.
 
<note source="auth" place="foot" anchored="Y">This is not as hard as it sounds.  The embedding of a
list within a list is illustrated in the second example below.</note>
 </p><p>No default value for the <att tei="yes">org</att> attribute is declared in the
DTD; however, a default value for that attribute can be declared for
particular features in the feature-system declaration; see <xref target="FD"/>.  Note that if only one value is specified for a given
<gi tei="yes">f</gi> element, the set, bag and list values of the <att tei="yes">org</att> are
all essentially equivalent to the singleton value, so the omission of the
<att tei="yes">org</att> attribute for such a feature is not problematic.
 
<note source="auth" place="foot" anchored="Y">Unless the value is the <gi tei="yes">null</gi> element; see
below.</note>
 </p><p>To illustrate the use of the <att tei="yes">org</att> attribute, suppose that
the illustration of personal records from the previous section is extended
to include pointers to an individual's siblings.  Suppose also that the
individual identified as <tag compl="full" tei="yes">fs id=PKAB027</tag> has siblings identified
as <tag compl="full" tei="yes">fs id=PANB005</tag>, <tag compl="full" tei="yes">fs id=PMFB010</tag> and <tag compl="full" tei="yes">fs
id=Pzrb001</tag> in the personal records library.  Then we may extend the
personal record for <tag compl="full" tei="yes">fs id=PKAB027</tag> as follows.
 
<eg><![CDATA[<fs id=PKAB027 type='personal record' feats='sxf'>
  <f name=full.name fVal=Nkab027></f>
  <f name=date.of.birth>
    <fs type='date record' feats='y1988 m04 d17'></fs>
    </f>
  <f name=place.of.birth fVal=austinTX></f>
  <f name=mother fVal=Parn002>
  <f name=father fVal=Pmfb009>
  <f name=siblings org=set fVal='Panb005 Pmfb010 Pzrb001'>
  </fs>]]></eg>
 </p><p>A more elaborate illustration of the use of the <att tei="yes">org</att>
attribute is the the following <tag compl="full" tei="yes">f name=career org=list</tag> element which
may be added to the personal records of an individual to record the job
career of that individual.  The feature structures which constitute the
value of this feature document the jobs which the individual has held in
the order in which they were held.  Note that a list has been embedded
within a list by means of intervening <tag compl="full" tei="yes">fs type='employment
record'</tag> and <tag compl="full" tei="yes">f name=promotion.history</tag> elements.
 
<eg><![CDATA[<f name=career org=list>
  <fs type='employment record'>
    <f name=employer><str>Safeway Stores</str></f>
    <f name=hiring.information>
      <fs type='hire structure'>
        <f name=hire.date>
          <fs type='date structure' feats='y1988 m06'></fs>
          </f>
        <f name=job.title><sym value=stocker></f>
        <f name=wage><rate value=6.00 per=hour></f>
        <f name=hours.worked><rate value=40 per=week></f>
        <f name=status.code fVal=sc4A></f>
        </fs>
      </f>
    <f name=promotion.history org=list>
      <fs type='promotion record'>
        <f name=date>
          <fs type='date structure' feats='y1988 m12'></fs>
            </f>
        <f name=job.title><sym value=cashier></f>
        <f name=wage><rate value=7.00 per=hour></f>
        <f name=hours.worked><rate value=40 per=week></f>
        <f name=status.code fVal=sc4A></f>
        </fs>
      <fs type='promotion record'>
        <f name=date>
          <fs type='date structure' feats='y1990 m02'></fs>
          </f>
        <f name=job.title><sym value=supervisor></f>
        <f name=salary><rate value=18000 per=year></f>
        <f name=status.code fVal=sc3C></f>
        </fs>
      </f>
    <f name=termination.information>
      <fs type='termination structure'>
        <f name=termination.date>
          <fs type='date structure' feats='y1991 m04'></fs>
            </f>
        <f name=status.code fVal=sc3C></f>
        <f name=reason.for.termination><sym value=laid.off></f>
        </fs>
      </f>
    </fs>
  <fs type='employment record'>
    <!-- ... -->
    </fs>
  <!-- ... -->
  </f>]]></eg>
 </p><p>The information contained in such features may be linked to textual
references in the usual way.  The <tag compl="full" tei="yes">f name=status.code</tag> feature
has been included to show how evaluative or interpretive information can
be included along with information gleaned from textual records.  The
example presumes that the status code values are maintained in a
designated <gi tei="yes">fvLib</gi>.
 </p><p>Features with values organized as sets, bags or lists can sometimes be
used instead of features organized as singletons, whose values are
individual feature structures.  For example, consider the following
encoding of the English verb form <cited>sinks</cited>, which contains a
<tag compl="full" tei="yes">f name=agreement</tag> element whose value is a feature structure which
contains <tag compl="full" tei="yes">f name=person</tag> and <tag compl="full" tei="yes">f name=number</tag> elements with
symbolic values.
 
<eg><![CDATA[<fs type='word structure'>
<!-- ... -->
  <f name=word.class><sym value=verb></f>
  <f name=tense><sym value=present></f>
  <f name=agreement>
    <fs type='agreement structure'>
      <f name=person><sym value=third></f>
      <f name=number><sym value=singular></f>
      </fs>
    </f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>If one does not care about the names of the features contained within
the <tag compl="full" tei="yes">fs type='agreement structure'</tag> element, the containing
<tag compl="full" tei="yes">f name=agreement</tag> element can be given an <att tei="yes">org</att>
attribute with the value <code tei="yes" type="frag">set</code>, and the contained <gi tei="yes">fs</gi>
element, together with the person and number feature elements it
contained, can be eliminated, as follows.
 
<eg><![CDATA[<fs type='word structure'>
<!-- ... -->
  <f name=word.class><sym value=verb></f>
  <f name=tense><sym value=present></f>
  <f name=agreement org=set><sym value=third><sym value=singular></f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>The encoding in the preceding example presumes that the
<gi tei="yes">fDecl</gi> element for the <tag compl="full" tei="yes">f name=agreement</tag> element
would look something like the following; for further details, see <xref target="FD"/>.
 
<eg rend="aux"><![CDATA[<fDecl name=agreement org=set>
<!-- ... -->
  <valRange>
    <vAlt>
      <sym value=first>
      <sym value=second>
      <sym value=third>
      </vAlt>
    <vAlt>
      <sym value=singular>
      <sym value=plural>
      </vAlt>
    </valRange>
<!-- ... -->
  </fDecl>]]></eg>
 </p><p>The set, bag or list which has no members is known as the null (or
empty) set, bag or list.  To refer to it, the <gi tei="yes">null</gi> element is
provided; its description and attributes are as follows.
 
<tagList style="one-line"><tagDesc tagDoc="NULL"/></tagList>
 </p><p>So, for example, to indicate that the individual identified above
by the <tag compl="full" tei="yes">fs id=PKAB027</tag> element has no siblings, we may specify the
<tag compl="full" tei="yes">f name=siblings</tag> element as follows.
 
<eg><![CDATA[   <f name=siblings org=set><null></f>]]></eg>
 </p><p>The <gi tei="yes">null</gi> element when used with a feature organized as a
singleton is a semantic error; however, its appearance as a value for such
a feature cannot be flagged by SGML.  The <gi tei="yes">null</gi> element, when it
appears as a feature value, must be the only value.
 </p><p>Here is the formal declarations of the <gi tei="yes">null</gi> element.
 
<dtdFrag id="DFSSS" n="Null values" file="teifs2"><tagDecl tagDoc="NULL"/></dtdFrag>







<?tei:EOF p2fsss.odd ??><?tei:SOF p2fsal.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2fsal.odd,v $
    * Revision 1.4  1998/02/01 17:45:38  tei
    * killing off extendargs
    *
    * Revision 1.3  94/03/21  14:12:03  lou
    * second mass typo clearup
    * 
    * Revision 1.2  1994/01/04  01:39:13  msmcq
    * revision for P3
    * --><!-- Revisions:                                               --><!-- 94-01-03 : MSM : change exx:  join, alt use TARGETS=     --><!-- 94-01-03 : MSM : Added RCS id                            --><!-- 93-12-20 : MSM : provide correct idrefs for chapter SA   --></p></div2><div2 id="FSAL" name="Alfalfa" ref="Y"><head>Alternative Features and Feature Values</head><p>In this section, two methods of representing the alternation (ambiguity
or uncertainty) of features and feature values are presented.  The first
of these methods is to be used for nonsystematic or sporadic markup of
alternation of individual features or values; it makes use of the
special-purpose <gi tei="yes">fAlt</gi> and <gi tei="yes">vAlt</gi> elements.  The other is to
be used for systematic markup of alternation and for the alternation of
groups of features or values; it makes use of the general-purpose
<gi tei="yes">alt</gi> element introduced in section <xref target="SAAT" type="div2"/>.
The <gi tei="yes">fAlt</gi> and <gi tei="yes">vAlt</gi> elements have the following
description and attributes.
 
<tagList style="one-line"><tagDesc tagDoc="FALT" atts="mutExcl"/><tagDesc tagDoc="VALT" atts="mutExcl"/></tagList>
 </p><p>To illustrate the use of the <gi tei="yes">fAlt</gi> element to represent the
alternation of features, suppose one is uncertain whether a particular
real estate advertisement describes a house with two bedrooms or with two
bathrooms.  This uncertainty can be represented as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <fAlt>
    <f name=number.of.bathrooms><nbr value=2></f>
    <f name=number.of.bedrooms><nbr value=2></f>
    </fAlt>
<!-- ... -->
  </fs>]]></eg>
 </p><p>This representation leaves unspecified whether or not the alternation
is <term>mutually exclusive</term> (i.e. whether having two bathrooms
excludes the possibility of having two bedrooms and vice versa).  To make
this aspect of the alternation explicit, one can specify a value for the
<att tei="yes">mutExcl</att> attribute, as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <fAlt mutExcl=N>
    <f name=number.of.bathrooms><nbr value=2></f>
    <f name=number.of.bedrooms><nbr value=2></f>
    </fAlt>
<!-- ... -->
  </fs>]]></eg>
 </p><p>The <gi tei="yes">fAlt</gi> element can also be used to represent uncertainty
about whether the number of bathrooms is two or three, as follows; note
that the attribute value <att tei="yes">mutExcl=Y</att> can be inferred for the
<gi tei="yes">fAlt</gi> element in this example.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <fAlt>
    <f name=number.of.bathrooms><nbr value=2></f>
    <f name=number.of.bathrooms><nbr value=3></f>
    </fAlt>
<!-- ... -->
  </fs>]]></eg>
 </p><p>However, the <tag compl="full" tei="yes">f name=number.of.bathrooms</tag> element in this example
can be factored out of the alternation, and a <gi tei="yes">vAlt</gi> element used
instead to represent the alternation of just the feature values, as
follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <f name=number.of.bathrooms>
    <vAlt><nbr value=2><nbr value=3></vAlt>
    </f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>The <gi tei="yes">fAlt</gi> and <gi tei="yes">vAlt</gi> elements can also be used to
indicate certain alternations among values of features organized as sets,
bags or lists.  For example, suppose one uses a <tag compl="full" tei="yes">f name=extras
org=set</tag> element in feature structures for real estate listings to
represent items that are mentioned to enhance a property's sales
value, such as whether it has a pool or a good view.  Now suppose for a
particular listing, the extras include an alarm system and a fenced-in
yard, and either a pool or a jacuzzi (but not both).  This situation could
be represented, using the <gi tei="yes">vAlt</gi> element, as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <f name=extras org=set>
    <str>alarm system</str>
    <str>fenced-in yard</str>
    <vAlt mutExcl=Y>
      <str>pool</str>
      <str>jacuzzi</str>
      </vAlt>
    </f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>Now suppose the situation is like the preceding except that one is
also uncertain whether the property has an alarm system or a fenced-in
yard, or possibly both.  This can be represented as follows.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <f name=extras org=set>
    <vAlt mutExcl=N>
      <str>alarm system</str>
      <str>fenced-in yard</str>
      </vAlt>
    <vAlt mutExcl=Y>
      <str>pool</str>
      <str>jacuzzi</str>
      </vAlt>
    </f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>Finally, suppose that the listing specifies that the property has a
finished basement, and that it also has either an alarm system and a
pool or a fenced-in yard and a jacuzzi.  This situation cannot be
represented using the <gi tei="yes">vAlt</gi> element, because the alternation
holds between subsets of two values each.  It can, however, be
represented using the <gi tei="yes">fAlt</gi> element, as follows; note that the
<gi tei="yes">str</gi> element with the value <code tei="yes" type="frag">finished basement</code>
element must be repeated.
 
<eg><![CDATA[<fs type='real estate listing'>
<!-- ... -->
  <fAlt mutExcl=Y>
    <f name=extras org=set>
      <str>finished basement</str>
      <str>alarm system</str>
      <str>pool</str>
      </f>
    <f name=extras org=set>
      <str>finished basement</str>
      <str>fenced-in yard</str>
      <str>jacuzzi</str>
      </f>
    </fAlt>
<!-- ... -->
  </fs>]]></eg>
 </p><p>If a large number of ambiguities or uncertainties involving a
relatively small number of features and values need to be represented,
it is recommended that the general-purpose <gi tei="yes">alt</gi> element
discussed in section <xref target="SAAT"/> be used, rather than
the special-purpose <gi tei="yes">fAlt</gi> and <gi tei="yes">vAlt</gi> elements.  The use of
the <gi tei="yes">alt</gi> element avoids the need to explictly represent the
alternating elements more than once.
 </p><p>For example, suppose one has set up a <gi tei="yes">fsLib</gi> element
containing feature structures representing the morphological
structures of classical Greek inflected words, along with collections
of individual features and feature values, encoded by <gi tei="yes">fLib</gi>
and <gi tei="yes">fvLib</gi> elements as appropriate.  The following example
shows how one might then represent the morphological structure of a
feminine gender, accusative case, plural number noun form in classical
Greek, such as <cited>the&aacute;s</cited> <gloss>goddesses</gloss>
discussed in section <xref target="FSSY"/>:
 
<eg><![CDATA[<fsLib type='noun structures'>
  <!-- ... -->
  <!-- plural accusative feminine noun -->
  <fs id=WNGFKANP type='noun structure' feats='Wn Gf Ka Np'></fs>
  <!-- ... -->
  </fsLib>
 
<fLib type='morphological features'>
  <f id=WN  name=word.class fVal=nn></f>
  <!-- ... -->
  <f id=GF  name=gender fVal=fe></f>
  <!-- ... -->
  <f id=KA  name=case fVal=ac></f>
  <!-- ... -->
  <f id=NP  name=number fVal=pl></f>
  <!-- ... -->
  </fLib>
 
<fvLib type='morphological feature values'>
  <!-- ... -->
  <sym id=NN value=noun>
  <!-- ... -->
  <sym id=FE value=feminine>
  <!-- ... -->
  <sym id=AC value=accusative>
  <!-- ... -->
  <sym id=PL value=plural>
  <!-- ... -->
  </fvLib>]]></eg>
 </p><p>Now consider the noun form <cited>thea&iacute;</cited>
<gloss>goddesses</gloss>, which is analyzable as a feminine plural
noun form in either the nominative or the vocative case.  We may represent
this ambiguity by adding the following entries to the <gi tei="yes">fsLib</gi>,
<gi tei="yes">fLib</gi>, and <gi tei="yes">fvLib</gi> elements in the preceding example;
assume that appropriate entries for unambiguous nominative and vocative
case forms have already been entered.
 
<eg><![CDATA[<!-- Add the following to the feature-structure library (FSLIB) -->
  <!-- plural nominative-or-vocative feminine noun -->
  <fs id=WNGFKNVNP type='noun structure' feats='Wn Gf Knv Np'></fs>
 
<!-- Add the following to the feature library (FLIB) -->
  <!-- CASE=nominative or vocative -->
  <f id=KNV name=case fVal=novo></f>
 
<!-- Add the following to the feature value library (FVLIB) -->
  <!-- nominative or vocative -->
  <alt id=NOVO targets='no vo'>]]></eg>
 </p><p>If the <gi tei="yes">fvLib</gi> element is not used, and specifications for
particular feature values are entered as content of the <tag compl="full" tei="yes">f
name=...</tag> elements in the <gi tei="yes">fLib</gi> element, then the ambiguity
can be represented as follows.
 
<eg><![CDATA[<fsLib type='noun structures'>
  <!-- ... -->
  <!-- plural nominative-or-vocative feminine noun -->
  <fs id=WNGFKNVNP type='noun structure' feats='Wn Gf Knv Np'></fs>
  <!-- ... -->
  </fsLib>
 
<fLib type='morphological features'>
  <!-- ... -->
  <f id=KN name=case><sym value=nominative>
  <!-- ... -->
  <f id=KV name=case><sym value=vocative>
  <!-- ... -->
  <alt id=KNV targets='Kn Kv'>
  <!-- ... -->
  </fLib>]]></eg>
 </p><p>The <gi tei="yes">alt</gi> element together with the <gi tei="yes">join</gi> element can,
unlike the <gi tei="yes">fAlt</gi> and <gi tei="yes">vAlt</gi> elements, be used to express
alternations between sets of features.  An example of such an
alternation is found in certain feminine gender Greek noun forms ending
in <cited>-as</cited>, such as <cited>pe&iacute;ras</cited>
<gloss>attempt(s)</gloss>, which may be analyzed as having either
genitive case and singular number features or accusative case and plural
number features, as follows (again, assuming the existence of other
elements and identifier attributes for simple features and values).
 
<eg><![CDATA[<!-- Add the following to the FSLIB element -->
  <!-- feminine noun, either genitive singular or accusative plural -->
  <fs id=WNGFKG.NsKa.Np type='noun structure' feats='Wn Gf Kg.NsKa.Np'>
    </fs>
 
<!-- Add the following to the FLIB element  -->
  <join id=KG.Ns targets='Kg Ns'> <!-- genitive singular -->
  <join id=KA.Np targets='Ka Np'> <!-- accusative plural -->
 
  <!-- alternation:  gen. sg. or acc. plural -->
  <alt id=KG.NsKa.Np targets='Kg.Ns KaNp'>]]></eg>
 </p><p>Here are the formal declarations of the <gi tei="yes">fAlt</gi> and
<gi tei="yes">vAlt</gi> elements.
 
<dtdFrag id="DFSAL" n="Alternative features and feature values" file="teifs2"><tagDecl tagDoc="FALT"/><tagDecl tagDoc="VALT"/></dtdFrag><?tei:EOF p2fsal.odd ??><?tei:SOF p2fsbo.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2fsbo.odd,v $
# Revision 1.4  1994/03/21  14:12:03  lou
# second mass typo clearup
#
# Revision 1.3  1994/01/04  01:39:13  msmcq
# revision for P3
#
# Revision 1.2  1993/09/23  16:36:32  msmcq
# change DEFAULT to DFT (name clash with TD)
# --><!-- Revisions:                                               --><!-- 93-09-22 : MSM : change default to dft                   -->
 </p></div2><div2 id="FSBO" name="Alfalfa" ref="Y"><head>Boolean, Default and Uncertain Values</head><p>In this section we define four special empty elements used as feature
values:  the <term>boolean value</term> elements <gi tei="yes">any</gi> and
<gi tei="yes">none</gi>, the <gi tei="yes">dft</gi> element, and the <gi tei="yes">uncertain</gi>
element.
 </p><p>The boolean value elements are used to indicate whether the features
they are associated with have values.  The element <gi tei="yes">any</gi>
corresponds to the boolean value <code tei="yes" type="frag">true</code> (i.e., that the
feature it is associated with has a value --- not the same as the binary
value <code tei="yes" type="frag">plus</code>), and the element <gi tei="yes">none</gi> corresponds to
the boolean value <code tei="yes" type="frag">false</code> (i.e., that the feature it is
associated with has no value).  The <gi tei="yes">dft</gi> element is used to
indicate that the feature it is associated with has its default value in
the feature structure in which it appears.  Finally, the
<gi tei="yes">uncertain</gi> element may be used to indicate uncertainty about
what value, if any, its associated feature has; it is equivalent to the
alternation of the <gi tei="yes">any</gi> and <gi tei="yes">none</gi> elements.  To indicate
uncertainty about which of the possible legal values a particular
feature has, one should use the <gi tei="yes">any</gi> element.
 </p><p>The descriptions and attributes of these elements are as follows.
 
<tagList style="one-line"><tagDesc tagDoc="ANY"/><tagDesc tagDoc="NONE"/><tagDesc tagDoc="DFT"/><tagDesc tagDoc="UNCERT"/></tagList>
 </p><p>The values <gi tei="yes">null</gi> and <gi tei="yes">none</gi> are distinct.  The former is
to be used with a feature organized as a set, bag, or list to indicate
that its value is the null set, bag, or list in a particular feature
structure.
The latter is to be used with such a feature to indicate that it has no
value in a particular feature structure.
 </p><p>The <emph>boolean</emph> values <gi tei="yes">any</gi> and <gi tei="yes">none</gi> are
also distinct from the <emph>binary</emph> values <gi tei="yes">plus</gi> and
<gi tei="yes">minus</gi>.  The latter pair are specific possible values for
features, whereas the former pair represent <emph>ranges</emph> of
possible values, not specific possible values, for features.  For
example, suppose that the <gi tei="yes">valRange</gi> element for the <tag compl="full" tei="yes">f
name=auxiliary</tag> element is declared as follows in the feature structure
declaration, so that either boolean value is legal.
 
<eg><![CDATA[<!-- VALRANGE tag for the AUXILIARY feature -->
<valRange><vAlt><plus><minus></vAlt></valRange>]]></eg>
 
Then the following two pairs of specifications are distinct.
 
<eg><![CDATA[<f name=auxiliary><plus></f>  =/= <f name=auxiliary><any></f>
 
<f name=auxiliary><minus></f> =/= <f name=auxiliary><none></f>]]></eg>
 
In this situation, the <gi tei="yes">any</gi> element is equivalent to the
alternation of the <gi tei="yes">plus</gi> and <gi tei="yes">minus</gi> elements, and the
<gi tei="yes">none</gi> element is equivalent to the negation of that alternation.
 </p><p>However, if the auxiliary feature is declared to take only the
<gi tei="yes">plus</gi> value, then the first pair of the specifications below
are equivalent, but the second is not; in fact, the first member of the
second pair is invalid.
 
<eg><![CDATA[<f name=auxiliary><plus></f>  ==  <f name=auxiliary><any></f>
 
<f name=auxiliary><minus></f> =/= <f name=auxiliary><none></f>]]></eg>
 </p><p>It is even possible to declare that a particular feature can never
have values, as follows for the feature <tag compl="full" tei="yes">f name=impossible</tag>.
 
<eg><![CDATA[<!-- VALRANGE tag for the IMPOSSIBLE feature -->
<valRange></valRange>]]></eg>
 
In this case, the following specifications are equivalent.
 
<eg><![CDATA[<f name=impossible><any></f>  == <f name=impossible><none></f>]]></eg>
 </p><p>The elements <gi tei="yes">any</gi> and <gi tei="yes">dft</gi> are also designed to be
used in conjunction with the <gi tei="yes">fDecl</gi> and <gi tei="yes">valDefault</gi>
elements in the feature system declaration discussed in section <xref target="FD"/>.  First, consider the <gi tei="yes">any</gi> element, and suppose that
the <gi tei="yes">valRange</gi> element in the <gi tei="yes">fDecl</gi> element for the <tag compl="full" tei="yes">f
name=gender</tag> element is specified as follows.
 
<eg><![CDATA[<!-- VALRANGE for the GENDER feature -->
<valRange>
  <vAlt>
    <sym value=feminine>
    <sym value=masculine>
    <sym value=neuter>
    </vAlt>
  </valRange>]]></eg>
 
Then the following two representations are equivalent.
 
<eg><![CDATA[<f name=gender><any></f>
 
<f name=gender>
  <vAlt>
    <sym value=feminine>
    <sym value=masculine>
    <sym value=neuter>
    </vAlt>
  </f>]]></eg>
 </p><p>Second, consider the <gi tei="yes">dft</gi> element, and suppose that the
default value for the <tag compl="full" tei="yes">f name=gender</tag> element is specified in the
<gi tei="yes">valDefault</gi> element of its <gi tei="yes">fDecl</gi> element as having the value
<tag compl="full" tei="yes">sym value=feminine</tag>.  Then the following three representations
are equivalent; note that if a <tag compl="full" tei="yes">f name=...</tag> element appears without
content and without a valid <att tei="yes">fVal</att> attribute, then it is
equivalent to the same element with the <gi tei="yes">dft</gi> element as its content.
 
<eg><![CDATA[<f name=gender></f>
 
<f name=gender><dft></f>
 
<f name=gender><sym value=feminine></f>]]></eg>
 </p><p>Using the <gi tei="yes">any</gi> and <gi tei="yes">dft</gi> elements, together with an
<gi tei="yes">fDecl</gi> element for the corresponding feature in the feature system
declaration, provides a method for <term>underspecifying</term> the
value of that feature.  The <gi tei="yes">any</gi> element means that the
associated feature has a legal value but what value it has is not
specified.  The <gi tei="yes">dft</gi> element means that the associated feature
has the value which the encoder has declared is the normal value of the
feature.
 </p><p>The boolean elements <gi tei="yes">any</gi> and <gi tei="yes">none</gi> also have
specific uses within <gi tei="yes">fsConstraints</gi> and <gi tei="yes">fDecl</gi> elements
in feature system declarations, as described in
chapter <xref target="FD"/>.  For example, the element <gi tei="yes">any</gi> can
appear as the value of a feature contained within an <gi tei="yes">fs</gi> of a
particular type which appears in the <gi tei="yes">cond</gi> element of an
<gi tei="yes">fsConstraints</gi> element, to indicate that the feature must appear
in feature structures of the designated type (i.e., that it is
obligatory) and that when it does appear, it may appear with any of its
legal values.  Similarly, <gi tei="yes">none</gi> can appear in this way to
specify that the feature cannot be present in feature structures of the
indicated type (i.e., that it is obligatorily absent from such feature
structures).  All other features that are declared to have values are
understood to be optional in such feature structures.
 </p><p>For example, the following may appear as part of the
<gi tei="yes">fsConstraints</gi> of a feature system declaration to indicate
that a <tag compl="full" tei="yes">fs type='agreement structure'</tag> must contain a legal
instance of the <tag compl="full" tei="yes">f name=number</tag> element but must not contain a
legal instance of the <tag compl="full" tei="yes">f name=category</tag> element.
 
<eg><![CDATA[<cond><fs type='agreement structure'></fs>
<then><fs>
         <f name=number><any></f>
         <f name=category><none></f>
         </fs>]]></eg>
 </p><p>Further constraints can be imposed on a feature structure of a
particular type in the <gi tei="yes">valRange</gi> elements of features which take
feature structures of that type as values.  For example, suppose that verb
and adjective agreement in German are represented by feature structures of
the following sorts, in which verb forms agree in person and number with
their subjects and adjective forms agree in gender, case, and number
with
their subjects.
 
<eg><![CDATA[<fs type='verb structure'>
<!-- ... -->
  <f name=verbAgreement>
    <fs type='agreement structure'>
      <f name=person><sym value=first></f>
      <f name=number><sym value=plural></f>
      </fs>
    </f>
<!-- ... -->
  </fs>
 
<fs type='adjective structure'>
<!-- ... -->
  <f name=adjAgreement>
    <fs type='agreement structure'>
      <f name=gender><sym value=feminine></f>
      <f name=case><sym value=accusative></f>
      <f name=number><sym value=plural></f>
      </fs>
    </f>
<!-- ... -->
  </fs>]]></eg>
 </p><p>In order to ensure that a <tag compl="full" tei="yes">fs type='agreement structure'</tag>
tag which appears as the value of a <tag compl="full" tei="yes">f name=verbAgreement</tag> element
may be specified for any person and number feature, but for no gender
and case feature, we may provide a <gi tei="yes">valRange</gi> element for the
<code tei="yes" type="frag">verbAgreement</code> feature as follows.
 
<eg><![CDATA[<!--VALRANGE specification for the VERBAGREEMENT feature -->
<valRange>
  <fs type='agreement structure'>
    <f name=person><any></f>
    <f name=case><none></f>
    <f name=gender><none></f>
    <f name=number><any></f>
    </fs>
  </valRange>]]></eg>
 
Similarly, to ensure that a <tag compl="full" tei="yes">fs type='agreement structure'</tag> element
which appears as the value of a <tag compl="full" tei="yes">f name=adjAgreement</tag> element may
be specified for any case, gender, and number feature, but for no person
feature, we may provide a <gi tei="yes">valRange</gi> element for the
<code tei="yes" type="frag">adjAgreement</code> feature as follows.
 
<eg><![CDATA[<valRange>
  <fs type='agreement structure'>
    <f name=person><none>
    <f name=case><any>
    <f name=gender><any>
    <f name=number><any>
    </fs>
  </valRange>]]></eg>
 </p><p>The combination of declarations like these and the principle of
<term>subsumption</term> discussed in <xref target="FSRL"/>, allows feature
structures to be underspecified in text markup.  For example, to
indicate that a given adjective inflection feature (tagged <tag compl="full" tei="yes">f
name=adjInflection</tag>) is a feature structure (tagged <tag compl="full" tei="yes">fs
type='inflection structure'</tag>) specifying plural number and any
gender and case, we can omit the elements for gender and case on the
<gi tei="yes">fs</gi> element, as follows.
 
<eg><![CDATA[<f name=adjInflection>
  <fs type='inflection structure'>
    <f name=number><sym value=plural></f>
    </fs>
  </f>]]></eg>
 
When supplied as the value of a verb inflection feature (tagged <tag compl="full" tei="yes">f
name=verbInflection</tag>), the same feature structure would be
interpreted as an inflection structure specifying plural number and any
person.
 </p><p>If an optional feature is not specified in a feature-structure value,
then it is assumed to occur with the <gi tei="yes">uncertain</gi> value.  For
further discussion, see section <xref target="FSRL"/>.
 </p><p>Here are the formal declarations of the <gi tei="yes">any</gi>, <gi tei="yes">none</gi>,
<gi tei="yes">dft</gi>, and <gi tei="yes">uncertain</gi> elements.
 
<dtdFrag id="DFSBO" n="Boolean, default, uncertainty values" file="teifs2"><tagDecl tagDoc="ANY"/><tagDecl tagDoc="NONE"/><tagDecl tagDoc="DFT"/><tagDecl tagDoc="UNCERT"/></dtdFrag>
 












<?tei:EOF p2fsbo.odd ??><?tei:SOF p2fsrl.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2fsrl.odd,v $
# Revision 1.4  1994/03/21  14:12:05  lou
# second mass typo clearup
#
# Revision 1.2  1994/01/04  01:39:13  msmcq
# revision for P3
# --><!-- Revisions:                                               --><!-- 94-01-03 : MSM : correct end-tag valt in an ex           --><!-- 94-01-03 : MSM : Added RCS id                            -->
 </p></div2><div2 id="FSRL" name="Alfalfa" ref="Y"><head>Indirect Specification of Values Using the
<att tei="yes">rel</att> Attribute</head><p>The <att tei="yes">rel</att> attribute is provided for the feature value
elements <gi tei="yes">sym</gi>, <gi tei="yes">nbr</gi>, <gi tei="yes">msr</gi>, <gi tei="yes">rate</gi>,
<gi tei="yes">str</gi>, <gi tei="yes">fs</gi>, and <gi tei="yes">default</gi> (but not <gi tei="yes">plus</gi>,
<gi tei="yes">minus</gi>, <gi tei="yes">null</gi>, <gi tei="yes">vAlt</gi>, <gi tei="yes">any</gi>,
<gi tei="yes">none</gi>, and <gi tei="yes">uncertain</gi>).  This attribute may be used for
specifying which of various logical relations the given value has to the
actual value of the feature.  For all value elements for which the
<att tei="yes">rel</att> attribute is defined, except for <gi tei="yes">fs</gi>, the default
value for that attribute is <code tei="yes" type="frag">eq</code>, which means that the actual
value is equal (or identical) to the given value.  Accordingly, the
following representations are both interpreted to mean that the value of
the <tag compl="full" tei="yes">f name=case</tag> element is the <tag compl="full" tei="yes">sym value=genitive</tag> element.
 
<eg><![CDATA[<f name=case><sym value=genitive></f>
 
<f name=case><sym rel=eq value=genitive></f>]]></eg>
 </p><div3 name="subsection" ref="Y"><head>The Not-Equals Relation</head><p>The <att tei="yes">rel</att> attribute can also be specified as having the
value <code tei="yes" type="frag">ne</code>, which means that the associated feature has a
value which is not equal to the given value.  For example, the value
<tag compl="full" tei="yes">nbr rel=ne value=1</tag> in the following example denotes any legal
numeric value for the element <tag compl="full" tei="yes">f name=number.of.bathrooms</tag> other
than <code tei="yes" type="frag">1</code>.
 
<eg><![CDATA[<f name=number.of.bathrooms><nbr rel=ne value=1></f>]]></eg>
 </p><p>If an <gi tei="yes">fDecl</gi> element has been provided which defines the
legal values for the associated feature, then the value <code tei="yes" type="frag">ne</code> can be
given a positive interpretation.  For example, suppose that the
<gi tei="yes">valRange</gi> element is declared in the <gi tei="yes">fDecl</gi> element
for the <gi tei="yes">f name=case</gi> element as follows.
 
<eg><![CDATA[<!-- VALRANGE specification in FDECL for CASE feature -->
<valRange>
  <vAlt>
    <sym value=nominative>
    <sym value=genitive>
    <sym value=dative>
    <sym value=accusative>
    <sym value=vocative>
    </vAlt>
  </valRange>]]></eg>
 </p><p>Suppose also that the <tag compl="full" tei="yes">f name=case</tag> element is declared as
obligatory in a particular feature structure.  Then the following
specifications are equivalent in that structure.
 
<eg><![CDATA[<f name=case><sym rel=ne value=genitive></f>
 
<f name=case>
  <vAlt>
    <sym value=nominative>
    <sym value=dative>
    <sym value=accusative>
    <sym value=vocative>
    </vAlt>
  </f>]]></eg>
 
That is, when the <att tei="yes">rel</att> attribute occurs with the value
<code tei="yes" type="frag">ne</code> in the value of an obligatory feature in a feature structure,
the actual value of that feature may be any of its legal values
<emph>other than</emph> the specified value.
 </p><p>On the other hand, if the <tag compl="full" tei="yes">f name=case</tag> feature is declared
as optional in a particular feature structure, then the following
specifications are equivalent in that structure.
 
<eg><![CDATA[<f name=case><sym rel=ne value=genitive></f>
 
<f name=case>
  <vAlt>
    <sym value=nominative>
    <sym value=dative>
    <sym value=accusative>
    <sym value=vocative>
    <none>
    </vAlt>
  </f>]]></eg>
 
That is, when the <att tei="yes">rel</att> attribute has the value
<code tei="yes" type="frag">ne</code> in the value of an optional feature in a feature structure,
the actual value of that feature may be any of its legal values other
than the specified value, or <gi tei="yes">none</gi>.
 </p><p>If the <att tei="yes">rel</att> attribute is specified with the value
<code tei="yes" type="frag">ne</code> for a <gi tei="yes">nbr</gi>, <gi tei="yes">msr</gi>, or <gi tei="yes">rate</gi>
element for which the <att tei="yes">valueTo</att> attribute is also specified,
then the actual range may be any range distinct from that given.  For
example, the following means that the number of bathrooms is a range
distinct from 3 to 5 (e.g., 3 to 4, 3 to 6, 4 to 5, 4 to 6, 0 to 2,
etc.).
 
<eg><![CDATA[<f name=number.of.bathrooms><nbr rel=ne value=3 valueTo=5></f>]]></eg>
 <!-- To express the notion that the number of bedrooms is     --><!-- completely outside the range specified (i.e. less than   --><!-- three or more than five), ... how?                       -->
 </p></div3><div3 name="subsection" ref="Y"><head>Other Inequality Relations</head><p>For the elements <gi tei="yes">nbr</gi>, <gi tei="yes">msr</gi>, <gi tei="yes">rate</gi>, and
<gi tei="yes">str</gi>, the <att tei="yes">rel</att> attribute may also take on the
following values; the use of these values for the <gi tei="yes">str</gi> element
presumes that a particular character and string ordering (or
<term>sorting</term>) convention is understood.
 <!-- From DTL to EDITORS: Where can this convention be referred to?  --><!-- I don't know. (msm)                                      -->
 
<list type="gloss"><label>lt </label><item>The actual value or range is any legal value or range
less than the specified value or range.
 </item><label>le </label><item>The actual value or range is any legal value or range
less than or equal to the specified value or range.
 </item><label>gt </label><item>The actual value or range is any legal value or range
greater than the specified value or range.
 </item><label>ge </label><item>The actual value or range is any legal value or range
greater than or equal to the specified value or range.
 </item></list>
 </p><p>These attribute values may be used as shown in the following
examples.  The first states that the number of bedrooms is less than 5;
the second that an illegal speed is any speed greater than 65 miles per
hour; the third that a lot size is in a range which is less than or
equal to the range of from 5 to 10 acres;
 
<note source="auth" place="foot" anchored="Y">We say that one range is less than or equal to another
if both the <att tei="yes">value</att> and <att tei="yes">valueTo</att> attributes of the
first are less than or equal to the corresponding attributes of the
second.</note>
 
the fourth that the last name is any string greater than the empty
string (i.e., any nonempty string, given normal string-ordering
conventions); and the fifth that for a feature whose value is a list of
two strings, the first precedes the string <cited>M</cited> and the
second is the string <cited>M</cited>, or any string following it.
 
<eg><![CDATA[<f name=number.of.bedrooms><nbr rel=lt value=5></f>
 
<f name=illegal.speed><rate rel=gt value=65 unit=miles per=hour></f>
 
<f name=lot.size><msr rel=le value=5 valueTo=10 unit=acre></f>
 
<f name=last.name><str rel=gt></str></f>
 
<f name=pairs org=list><str rel=lt>M</str><str rel=ge>M</str></f>]]></eg>
 </p></div3><div3 name="subsection" ref="Y"><head>Subsumption and Non-subsumption Relations</head><p>When the <att tei="yes">rel</att> attribute is given the values <code tei="yes" type="frag">sb</code> or
<code tei="yes" type="frag">ns</code>, the markup expresses the claim that the value given
subsumes, or does not subsume, the actual value for the feature in
question.
 </p><p>On the <gi tei="yes">str</gi> element, these values are used to specify that
the string value given in the <gi tei="yes">str</gi> element is or is not a
<term>substring</term> of the actual value of the feature.  The first
example below specifies that the actual feature value may be any string
at all (since the empty string is a substring of every string), the
second that it might be any string in which the string
<cited>the</cited> occurs as a substring, and the third that it might be
any string in which the string <cited>the</cited> does not occur as a
substring.
 
<eg><![CDATA[<str rel=sb></str>
<str rel=sb>the</str>
<str rel=ns>the</str>]]></eg>
 </p><p>On the <gi tei="yes">fs</gi> element, the attribute values <code tei="yes" type="frag">sb</code> and
<code tei="yes" type="frag">ns</code> indicate that the given feature structure does or does not
legally <term>subsume</term> the actual feature structure.  By
definition, one feature structure subsumes another if the second feature
structure is identical to the first or contains more information than
the first.  The default value for the <att tei="yes">rel</att> attribute of the
<gi tei="yes">fs</gi> element is <code tei="yes" type="frag">sb</code>.  The subsumption of feature
structures is illustrated by the following four examples; suppose that
the <tag compl="full" tei="yes">f name=person</tag> and <tag compl="full" tei="yes">f name=number</tag> elements are
either optional or obligatory in these <tag compl="full" tei="yes">fs type='agreement
structure'</tag> example elements.
 
<eg><![CDATA[<fs id=P3NS type='agreement structure'>
  <f name=person><sym value=third></f>
  <f name=number><sym value=singular></f>
  </fs> <!-- 3d person singular -->
 
<fs id=P3NX type='agreement structure'>
  <f name=person><sym value=third></f>
  </fs> <!-- 3d person -->
 
<fs id=PXNS type='agreement structure'>
  <f name=number><sym value=singular></f>
  </fs> <!-- singular -->
 
<fs id=PXNX type='agreement structure'>
  </fs> <!-- -->]]></eg>
 </p><p>The fourth example, <q>pxnx</q>, subsumes all four of the examples,
since each contains at least as much information as does feature
structure <q>pxnx</q>.  Conversely, the first example, <q>p3ns</q>,
subsumes only itself.  Finally, the second and third examples,
identified as <q>p3nx</q> and <q>pxns</q> attributes, subsume themselves
and the first feature structure, but not each other.
 </p><p>If both person and number are obligatory features of agreement
structure elements, then the last three elements in the preceding list
have the same interpretation as their counterparts in the following
list.
 
<eg><![CDATA[<fs id=P3NA type='agreement structure'>
  <f name=person><sym value=third></f>
  <f name=number><any></f>
  </fs> <!-- 3d person -->
 
<fs id=PANS type='agreement structure'>
  <f name=person><any></f>
  <f name=number><sym value=singular></f>
  </fs> <!-- singular -->
 
<fs id=PANA type='agreement structure'>
  <f name=person><any></f>
  <f name=number><any></f>
  </fs> <!-- -->]]></eg>
 </p><p>On the other hand, if both person and number are optional features of
agreement structures, then those three elements have the same
interpretation as their counterparts in the following list.
 
<eg><![CDATA[<fs id=P3NU type='agreement structure'>
  <f name=person><sym value=third></f>
  <f name=number><uncertain></f>
  </fs> <!-- 3d person -->
 
<fs id=PUNS type='agreement structure'>
  <f name=person><uncertain></f>
  <f name=number><sym value=singular></f>
  </fs> <!-- singular -->
 
<fs id=PUNU type='agreement structure'>
  <f name=person><uncertain></f>
  <f name=number><uncertain></f>
  </fs> <!-- -->]]></eg>
 
That is, if an optional feature is omitted from a feature-structure
representation, then that feature may have any of its legal values or
the value <gi tei="yes">uncertain</gi>.
 </p><p>The value <code tei="yes" type="frag">sb</code> is chosen as the default value for the
<att tei="yes">rel</att> attribute of the <gi tei="yes">fs</gi> element, because it provides
for the most economical means for underspecifying them.  One situation
in which it may be preferable to specify <tag compl="full" tei="yes">fs rel=eq</tag> is when
the feature structure has many optional features and it is known that
none of them occur.
 </p><p>The specification <tag compl="full" tei="yes">fs rel=ns</tag> is used to denote the feature
structures that the specified feature structure does not subsume.  This
provides a handy way of saying that a certain combination of features is
not present, for example the combination of third person and singular
number, as in the agreement structure of the English verb form
<cited>sink</cited>, understood as a present tense verb form.  The
following example expresses the claim that third-person and
singular-number features are not both present in the agreement feature,
but makes no further claim about what is present.
 
<eg><![CDATA[<f name=agreement>
  <fs id=NP3NS rel=ns type='agreement structure'>
    <f name=person><sym value=third></f>
    <f name=number><sym value=singular></f>
    </fs>
  </f>]]></eg>
 </p><p>In most real situations, of course, one can infer, from the range of
possible values for person and number, what the remaining possibilities
are.  Suppose, for example, that in the relevant feature system
declaration, the features <cited>person</cited> and
<cited>number</cited> are given the following <gi tei="yes">valRange</gi>
elements:
 
<eg><![CDATA[<!-- VALRANGE for the PERSON feature  -->
<valRange>
  <vAlt>
    <sym value=first>
    <sym value=second>
    <sym value=third>
    </vAlt>
  </valRange>
 
<!-- VALRANGE for the NUMBER feature  -->
<valRange>
  <vAlt>
    <sym value=singular>
    <sym value=plural>
    </vAlt>
  </valRange>]]></eg>
 </p><p>Suppose, further, that the person and number features are obligatory
in feature structures of the type <q>agreement structure</q>.  Then the
element <tag compl="full" tei="yes">fs id=NP3NS</tag> above is equivalent to the following
alternation; the features whose value is <gi tei="yes">any</gi> may be omitted,
since they are implied by the default value of <code tei="yes" type="frag">sb</code> for the
<att tei="yes">rel</att> attribute in the enclosing <gi tei="yes">fs</gi> elements.
 
<eg><![CDATA[<vAlt id=P12NA-panp>
  <fs id=P12NA type='agreement structure'>
    <f name=person>
      <vAlt><sym value=first><sym value=second></vAlt></f>
    <f name=number><any></f>
    </fs>
  <fs id=PANP type='agreement structure'>
    <f name=person><any></f>
    <f name=number><sym value=plural></f>
    </fs>
  </vAlt>]]></eg>
 </p><p>If, on the other hand, the person and number features were optional
in feature structures of type <q>agreement structure</q>, then the
interpretation of an underspecified feature structure will change.  The
element <tag compl="full" tei="yes">fs id=NP3NS</tag> given above is then equivalent to the
following alternation; the features whose value is <gi tei="yes">uncertain</gi>
may be omitted as they are implied by the default subsumption relation
holding between the structure given and the actual structure.
 
<eg><![CDATA[<vAlt id=P120NU-punp0>
  <fs id=P120NU type='agreement structure'>
    <f name=person>
      <vAlt><sym value=first><sym value=second><none></vAlt>
      </f>
    <f name=number><uncertain>
    </fs>
  <fs id=PUNP0 type='agreement structure'>
    <f name=person><uncertain>
    <f name=number>
      <vAlt><sym value=plural><none></vAlt>
      </f>
    </fs>
  </vAlt>]]></eg>
 </p></div3><div3 name="subsection" ref="Y"><head>Relations Holding with Sets, Bags, and Lists</head><p>The <att tei="yes">rel</att> attribute is also provided for the <gi tei="yes">f</gi>
element, but is designed to be used with that element only when its
<att tei="yes">org</att> attribute (see section <xref target="FSSS"/>) is set to
<code tei="yes" type="frag">set</code>, <code tei="yes" type="frag">bag</code>, or <code tei="yes" type="frag">list</code>.  When
associated with the <gi tei="yes">f</gi> element, the <att tei="yes">rel</att> attribute may
take on any of the following four values:  <code tei="yes" type="frag">eq</code>,
<code tei="yes" type="frag">ne</code>, <code tei="yes" type="frag">sb</code>, and <code tei="yes" type="frag">ns</code>.  The default
value is <code tei="yes" type="frag">eq</code>.  Consider first the use of the <att tei="yes">rel</att>
attribute with the <gi tei="yes">f</gi> element when the given value of the
feature is <gi tei="yes">null</gi>.
 
<eg><![CDATA[<f name=extras org=set><null></f>
 
<f name=extras org=set rel=ne><null></f>
 
<f name=extras org=set rel=sb><null></f>
 
<f name=extras org=set rel=ns><null></f>]]></eg>
 </p><p>The first example states that the <cited>extras</cited> feature has
the null set as its value.  The second example states that the
<cited>extras</cited> feature is a set which is not equal to the null
set.  That is, its actual value might be any non-null set.  The third
example states that the <cited>extras</cited> feature has as its value a
set of which the null set is a subset; that is to say, any set at all,
including the null set.  Note that this is not equivalent to the
following, which states that the extras feature has as its value a
single element which is any legal value for the <cited>extras</cited>
feature, including for example a <gi tei="yes">str</gi> element containing the
value <code tei="yes" type="frag">pool</code>.
 
<eg><![CDATA[<f name=extras org=set><any></f>]]></eg>
 </p><p>Finally, the fourth example states that the <cited>extras</cited>
feature has as its value a set of which the null set is not a subset.
Since the null set is a subset of every set, the fourth example in
effect claims that the <cited>extras</cited> feature has no legal value;
it is thus equivalent to the following, which states directly that the
<cited>extras</cited> feature has no value.
 
<eg><![CDATA[<f name=extras org=set><none></f>]]></eg>
 </p><p>Consider next the use of the <att tei="yes">rel</att> attribute with the
<gi tei="yes">f</gi> element when the given value of the feature is a single
<gi tei="yes">str</gi> element with the content <code tei="yes" type="frag">pool</code>:
 
<eg><![CDATA[<f name=extras org=set><str>pool</str></f>
 
<f name=extras org=set rel=ne><str>pool</str></f>
 
<f name=extras org=set rel=sb><str>pool</str></f>
 
<f name=extras org=set rel=ns><str>pool</str></f>]]></eg>
 </p><p>The first example states that the value of the
<cited>extras</cited> feature is a set consisting of a single member,
namely a <gi tei="yes">str</gi> element containing the value <code tei="yes" type="frag">pool</code>.
The second example states that the <cited>extras</cited> feature has
as its value a set which is not equal to the set consisting of this
particular member. It could, however, be a two-membered set, one of
whose members is some other value. This example is thus not equivalent
to the following, which states that the <cited>extras</cited> feature
has as its value a set comprising a single member other than a
<gi tei="yes">str</gi> element with the content <code tei="yes" type="frag">pool</code>:

 
<eg><![CDATA[<f name=extras org=set><str rel=ne>pool</str></f>]]></eg>
 </p><p>The third example states that the <cited>extras</cited> feature has
as its value any set of which the set consisting of the single member
specified is a subset (i.e., any set which contains the element
<gi tei="yes">str</gi> with the value <code tei="yes" type="frag">pool</code>, and possibly
others). Finally, the fourth example states that the
<cited>extras</cited> feature has as its value any set which does not
contain this element as a member.
 </p></div3><div3 name="subsection" ref="Y"><head>Varieties of Subsumption and Non-subsumption</head><p>The <att tei="yes">rel</att> values <code tei="yes" type="frag">sb</code> and <code tei="yes" type="frag">ns</code> have different
meanings depending on whether they occur within a <gi tei="yes">str</gi>,
<gi tei="yes">fs</gi> or <gi tei="yes">f</gi> element.  However, the use of a common name
for the value reflects a fundamental similarity in those meanings.  For
example, the value <code tei="yes" type="frag">sb</code> can be used in all three elements to
indicate that the actual value is any string, any feature structure, or
any set, bag or list, as follows. In the second example below, the
<att tei="yes">rel</att> attribute has not been specified, since it has the value
<code tei="yes" type="frag">sb</code> by default on <gi tei="yes">fs</gi> elements.
 
<eg><![CDATA[<str rel=sb></str>
 
<fs></fs>
 
<f name=... org=set rel=sb><null></f>
 
<f name=... org=bag rel=sb><null></f>
 
<f name=... org=list rel=sb><null></f>]]></eg>
 </p><p>Because the value <code tei="yes" type="frag">sb</code> is not defined for the attribute
<att tei="yes">rel</att> on the <gi tei="yes">nbr</gi>, <gi tei="yes">msr</gi> and <gi tei="yes">rate</gi>
elements, the indication that a value may be any number, measure or rate
is sometimes not quite as simple.  Here is one way of specifying any
positive or negative integer numeric value.
 
<note source="auth" place="foot" anchored="Y">Typically, there will be no need to use an encoding
like this one as the value of a feature, since the <gi tei="yes">any</gi> element
is available for that purpose.  However, in setting up the feature
declaration for that feature, it may be necessary to use such an
encoding, precisely so as to provide an interpretation for the use of
the <gi tei="yes">any</gi> element as the value of that feature.</note>
 
<eg><![CDATA[<vAlt>
  <nbr type=int rel=gt value=0>
  <nbr type=int rel=le value=0>
  </vAlt>]]></eg>
 </p><p>The value <code tei="yes" type="frag">ns</code> also is understood in similar ways in the
different elements in which it may occur.  Above in this section, the
equivalence of the following representations under certain conditions
was shown (the <att tei="yes">id</att> attributes and the redundant features with
<tag compl="full" tei="yes">any</tag> values have been omitted).
 
<eg><![CDATA[<f name=agreement>
  <fs rel=ns type='agreement structure'>
    <f name=person><sym value=third></f>
    <f name=number><sym value=singular></f>
    </fs>
  </f>
 
<f name=agreement>
  <vAlt>
    <fs type='agreement structure'>
      <f name=person>
        <vAlt><sym value=first><sym value=second></vAlt>
        </f>
      </fs>
    <fs type='agreement structure'>
      <f name=number><sym value=plural></f>
      </fs>
    </vAlt>
  </f>]]></eg>
 </p><p>The value <code tei="yes" type="frag">ns</code> has an analogous meaning when the value in
question is a set rather than a feature structure.  Recast in such
terms, the equivalence above still holds good:
 <!-- paragraph above substituted by msm for the following.    --><!-- I *think* they mean the same thing!                      -->
 <!-- < p>If we replace the first of these representations by  --><!-- a comparable one in which a set of symbolic values       --><!-- occurs as the value of the < tag>f name=agreement <      --><!-- /tag> element (see section < xref target=FSSS>), and     --><!-- assign the value < q>ns < /q> for the < att>rel < /att>  --><!-- attribute on that element, then the following            --><!-- equivalence can be shown under comparable conditions,    --><!-- thus revealing the underlying similarity of the value <  --><!-- q>ns < /q> in the two situations.                        -->
 
<eg><![CDATA[<f name=agreement org=set rel=ns>
  <sym value=third><sym value=singular>
  </f>
 
<f name=agreement org=set rel=sb>
  <vAlt>
    <vAlt><sym value=first><sym value=second></vAlt>
    <sym value=plural>
    </vAlt>
  </f>]]></eg>


<?tei:EOF p2fsrl.odd ??><?tei:SOF p2fsil.odd ??>
<!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2fsil.odd,v $
    * Revision 1.7  1998/02/01 17:45:38  tei
    * killing off extendargs
    *
    * Revision 1.6  94/03/27  16:30:05  lou
    * semifinal check
    * 
    * Revision 1.3  1994/01/04  01:39:13  msmcq
    * revision for P3
    * 
    * Revision 1.2  1993/09/23  16:36:48  msmcq
    * fix end of example
    * --><!-- Revisions:                                               --><!-- 19 mar: shortened dogs today a bit, but not enough --><!-- 94-01-03 : MSM : changes to examples for parseability    --><!-- 93-12-20 : MSM : provide correct idrefs for chapter SA   --><!-- 93-09-22 : MSM : fix an end of eg                        -->
 </p></div3></div2><div2 id="FSIL" name="Ilocano" ref="Y"><head>Two Illustrations</head><p>In this section, we present two illustrations based on one text of
how to associate feature structures and their components with textual
elements.  Our example text is the article <title>Memoirs of a Dog
Shrink</title> that appeared in the popular magazine <title>Dogs
Today</title> in August 1991.  This text has been selected for
inclusion in the British National Corpus.  The first illustration
associates the text with a structure that represents a significant
portion of the information contained in the text.  The second marks up
the grammatical structure of the orthographic words and certain other
comparable units in the text.  Here is the text, with markup provided
down to the level of <gi tei="yes">s</gi> elements.  The <att tei="yes">n</att> attribute
values are taken from the BNC markup; the <att tei="yes">id</att> attribute
values have been added for purposes of these illustrations.
 
<eg><![CDATA[<div1 id=DT91MDS type='article'>
<head rend=italic>
<s id=MDS01 n=00732>Memoirs of a Dog Shrink</s></head>
 <head type=sub rend=italic>
<s id=MDS04 n=00735>Cartoonist Russell Jones
takes a ramble through Peter Neville's files</s></head>
<list>
<item><s id=MDS05 n=00736>Case number: 72</s></item>
<item><s id=MDS06 n=00737>Name: Jessie</s></item>
<item><s id=MDS07 n=00738>Breed: Collie</s></item>
<item><s id=MDS08 n=00739>Problem: Light bulb phobia</s></item>
</list>
 
<p><s id=MDS09 n=00740>Jess the collie was a laid-back
sort of hound who spent most of his life stretched out
on a fireside rug in his large Surrey home.</s></p>
<p><s id=MDS10 n=00741>The closest he came to exercise
was to open one eye every so often, if someone entered
the room, or to open both eyes, smile, and wag his
tail as he'd done on one occasion when confronted by a
housebreaker!</s></p>
<p><s id=MDS11 n=00742>This extremely lazy lifestyle
was one long yawn from dawn to dusk.</s>
<s id=MDS12 n=00743>Only the odd bouts of involuntary
twitching in his sleep reassured his owner that Jess
was still safe and sound in the land of the
living!</s></p>
<p><s id=MDS13 n=00744>One winter night, as the mutt
twitched away in front of the fire, his mind somewhere
between Basingstoke and the twilight zone, a 100-watt
light bulb in the standard lamp above his head
suddenly exploded without warning!</s></p>
<p><s id=MDS14 n=00745>According to his owner, who
witnessed the spectacle, Jessie rose gracefully toward
the ceiling like a space shuttle and, after lingering
in mid-air for what seemed an eternity, crashed to the
floor and fled the house with a speed and agility the
owner found quite amazing.</s></p>
<p><s id=MDS15 n=00746>Jessie did not return home for
several hours.</s>
<s id=MDS16 n=00747>When he eventually did show up, it
was obvious to all that he was a changed dog!</s>
<s id=MDS17 n=00748>What plodded through the front door
was not the lovable, lazy hound who had once lived
there but a grim-faced light bulb serial
killer!</s></p>
<p><s id=MDS18 n=00749>Within seconds of his return,
Jessie launched a vicious attack on a table lamp,
popping the bulb and wrecking the shade before
charging into the lounge.</s>
<s id=MDS19 n=00750>There, in a frenzy of violence, he
reduced the standard lamp to a table lamp in 10
seconds flat!</s></p>
<p><s id=MDS20 n=00751>After a room-to-room chase
lasting several minutes, during which every lamp in
the house was turned to sawdust, the dog was finally
caught and wrestled to the ground.</s></p>
<p><s id=MDS21 n=00752>With his house plunged into
darkness, Jessie's owner sought my help.</s></p>
 
<div2 type='part'><head>
<s id=MDS22 n=00753>SIMPLE SOLUTION</s></head>
<p><s id=MDS23 n=00754>When I first saw the dog, it
was quite obvious he'd been deeply affected by the
explosion and had developed a 100-watt phobia for
light bulbs!</s></p>
<p><s id=MDS24 n=00755>By placing his feeding bowl
closer each day to a table lamp the dog gradually
learned to live with his enemy.</s>
<s id=MDS25 n=00756>Within a couple of weeks, his
killer instincts had disappeared and he was back where
he belonged &mdash; twitching away peacefully on the
fireside rug.</s></p>
</div2>
</div1>]]></eg>
 </p><p>The first illustration is based on the observation that from the
example text, it is possible to infer a fairly extensive medical history
for the dog described in it.  Suppose that we have a definition of a
feature structure that represents a canine medical history.  Then we can
fill in feature values in that history from the text, and prepare a
<gi tei="yes">linkGrp</gi> element that specifies the links between the text segments
and the various features specified in the feature structure.  Here is a
hypothetical example of such a filled-in feature structure and associated
link group.
 
<eg><![CDATA[<fs type='canine medical history'id=j37>
  <f name=name id=J37PN><str>Jessie</str></f>
  <f name=called.by org=set id=J37PC>
    <str>Jessie</str>
    <str>Jess</str>
    </f>
  <f name=breed id=J37B><sym value=collie>
  <f name=owner id=J37O>
    <fs type='owner description'>
      <f name=name><uncertain></f>
      <f name=address id=J37OR><str>Surrey</str></f>
      </fs>
  <f name=illness org=list id=J37I>
    <fs type='case history' id=J37I1>
      <f name=name.of.specialist id=J37I1SN>
        <fs type='name structure'>
          <f name=last.name><str>Neville</str></f>
          <f name=first.name><str>Peter</str></f>
          </fs>
      <f name=title.of.specialist><uncertain>
      <f name=case.number id=J37I1N><nbr value=72></f>
      <f name=age.at.incidence><uncertain></f>
      <f name=date.of.incidence><uncertain>
      <f name=baseline.condition org=set id=J37I1B>
        <sym value=lazy>
        <sym value=friendly>
        <sym value=indoor>
        </f>
      <f name=symptoms id=J37I1S>
        <fs type='symptom structure'>
          <f name=behaviors org=set id=J37I1SB>
            <sym value=agitated>
            <sym value=destructive>
            <sym value=unfriendly>
            </f>
          <f name=particulars id=J37I1SP>
             <str>ran off, then returned and
             destroyed every lamp in the house</str></f>
          </fs>
        </f>
      <f name=diagnosis id=J37I1D>
        <fs type='diagnosis structure'>
          <f name=date.of.diagnosis><uncertain>
          <f name=disease id=J37I1DD>
            <str>light bulb phobia</str>
            </f>
          <f name=presumed.cause id=J37I1DC>
            <str>explosion of light bulb over patient's head</str>
            </f>
          </fs>
        </f>
      <f name=treatment id=J37I1T>
        <fs type='treatment history'>
          <f name=medicine><none></f>
          <f name=regime id=J37I1TR><str>positive reinforcement</str></f>
          <f name=particulars id=J37I1TP>
            <str>systematically decreased distance between 
             feeding bowl and table lamp</str></f>
          <f name=duration.of.treatment id=J37I1TD>
            <msr unit=week value=2>
            </f>
          </fs>
        </f>
      <f name=result id=J37I1R>
        <str>return to baseline condition</str>
        </f>
      </fs>
    </f>
  </fs>]]></eg>
 
<eg><![CDATA[<linkGrp domains='j37 DT91mds'
         targFunc='feature segment' >
  <link targets='j37pn    mds06'>
  <link targets='j37pc    mds09'>
  <link targets='j37pc    mds09'>
  <link targets='j37pc    mds11'>
  <link targets='j37pc    mds14'>
  <link targets='j37pc    mds18'>
  <link targets='j37pc    mds21'>
  <link targets='j37b     mds07'>
  <link targets='j37b     mds09'>
  <link targets='j37or    mds09'>
  <link targets='j37i1sn  mds04'>
  <link targets='j37i1n   mds05'>

<!-- ... -->

  <link targets='j37i1dc  mds23'>
  <link targets='j37i1tr  mds24'>
  <link targets='j37i1td  mds25'>
  <link targets='j37r     mds25'>
  </linkGrp>]]></eg>
 </p><p>From this illustration, we see that links can be made not only between
text and feature structure elements, but also between text and feature
elements.  For that matter, links between text and feature value elements
can also be made.
 </p><p>The second illustration takes advantage of the fact that this text,
like others that appear in the BNC, has been provided with detailed
grammatical markup of most of its orthographic words and certain other
comparable structural units.  For example, in an early form of the BNC
markup, the second paragraph of the
above text was  marked up as follows.
 
<eg><![CDATA[<s n=00741>The&AT0; closest&AJS; he&PNP; came&VVD; to&PRP; exercise&NN1;
was&VBD; to&TO0; open&VVI; one&CRD; eye&NN1; every so often&AV0;,&PUN;
if&CJS; someone&PNI; entered&VVD; the&AT0; room&NN1;,&PUN; or&CJC;
to&TO0; open&VVI; both&DT0; eyes&NN2;,&PUN; smile&VVI;,&PUN; and&CJC;
wag&VVI; his&DPS; tail&NN1; as&CJS; he&PNP;'d&VHD; done&VDN; on&PRP;
one&CRD; occasion&NN1; when&AVQ; confronted&VVN; by&PRP; a&AT0;
housebreaker&NN1;!&PUN;</s>]]></eg>
 </p><p>The entities that appear in this fragment may be expanded into
pointers to feature structures that represent grammatical structure by
means of entity definitions as follows.
 
<eg><![CDATA[<!-- ... -->
<!ENTITY   AJS    "<ptr target=AJS>"                              >
<!-- ... -->
<!ENTITY   AT0    "<ptr target=AT0>"                              >
<!-- ... -->]]></eg>
 </p><p>This method of associating feature structures with textual elements
has a number of drawbacks, most important of which is the fact that the
association is implicit, relying on the relative position of pointer
and associated text, rather than being explicit.
A better method therefore (which was subsequently adopted by the BNC
project) is to segment the text into the units under
analysis, and point to the feature structures from within the unit tags,
by means of the <att tei="yes">ana</att> attribute (see sections <xref target="AIATTS"/> and <xref target="AILA"/>).
 
<eg><![CDATA[<s n=00741>
<w ana=AT0>The</w>
<w ana=AJS>closest</w>
<w ana=PNP>he</w>
<w ana=VVD>came</w>
<w ana=PRP>to</w>
<w ana=NN1>exercise</w>
<w ana=VBD>was</w>
<w ana=TO0>to</w>
<w ana=VVI>open</w>
<w ana=CRD>one</w>
<w ana=NN1>eye</w>
<phr ana=AV0>
  <w>every</w>
  <w>so</w>
  <w>often</w>
  </phr>
<c ana=PUN>,</c>
<w ana=CJS>if</w>
<w ana=PNI>someone</w>
<w ana=VVD>entered</w>
<w ana=AT0>the</w>
<w ana=NN1>room</w>

<!-- ... -->

</s>]]></eg>
 </p><p>To provide pointers in both direction between text and structural
analysis, one may supply both the text segments and the feature-structure
tags with identifiers, and associate the segments with their analysis by
means of a <gi tei="yes">linkGrp</gi> (see section <xref target="SAPT"/>), as follows.
 </p><p>First, we define a feature-structure library  to
represent all of the
grammatical structures that are used in the BNC encoding scheme. (For
illustrative purposes, we cite here only the structures needed for the
first six words of the sample sentence):
 
<eg><![CDATA[<fsLib id=BNCGS type='BNC grammatical structures'>
   <!-- ... -->
  <fs type='grammatical structure' id=AJS feats='Wj Ds'></fs>
  <fs type='grammatical structure' id=AT0 feats='Wl'></fs>
  <fs type='grammatical structure' id=PNP feats='Wr Rp'></fs>
  <fs type='grammatical structure' id=VVD feats='Wv Bv Fd'></fs>
  <fs type='grammatical structure' id=PRP feats='Wp Bp'></fs>
  <fs type='grammatical structure' id=NN1 feats='Wn Tc Ns'></fs>
  <!-- ... -->
  </fsLib>
 ]]></eg>

It will be noted that each feature structure in this library bears an
identifier corresponding with the code supplied as the value for the
<att tei="yes">ana</att> attribute in the sample sentence. The component
features of each feature structure are further specified by the
<att tei="yes">feats</att> attribute. These identify one or more <gi tei="yes">f</gi>
elements in the following feature library (again, only a few of the
available features are quoted here):

<eg><![CDATA[
<fLib type='BNC grammatical features'>
<!-- ... -->
  <f name=verbBase  id=BV><sym value=main></f>
  <f name=prepBase  id=BP><sym value=lexical></f>
  <f name=degree    id=DS><sym value=superlative></f>
  <f name=verbForm  id=FD><sym value=ed></f>
  <f name=number    id=NS><sym value=singular></f>
  <f name=pronType  id=RP><sym value=personal></f>
  <f name=nounType  id=TC><sym value=common></f>
  <f name=class     id=WJ><sym value=adjective></f>
  <f name=class     id=WL><sym value=article></f>
  <f name=class     id=WN><sym value=noun></f>
  <f name=class     id=WP><sym value=preposition></f>
  <f name=class     id=WR><sym value=pronoun></f>
  <f name=class     id=WV><sym value=verb></f>
<!-- ... -->
  </fLib>]]></eg>
 </p><p>Next, here is a markup of the start of our sample sentence being
analyzed, with identifiers for each segment; see section <xref target="AILC"/> for discussion of the <gi tei="yes">phr</gi>, <gi tei="yes">w</gi>,
<gi tei="yes">m</gi> and <gi tei="yes">c</gi> elements used here.
 
<eg><![CDATA[<s n=00741 id=MDS09>
<w id=MDS0901>The</w>
<w id=MDS0902>closest</w>
<w id=MDS0903>he</w>
<w id=MDS0904>came</w>
<w id=MDS0905>to</w>
<w id=MDS0906>exercise</w>
<w id=MDS0907>was</w>
<w id=MDS0908>to</w>
<w id=MDS0909>open</w>
<w id=MDS0910>one</w>
<w id=MDS0911>eye</w>
<phr id=MDS0912>
  <w>every</w>
  <w>so</w>
  <w>often</w>
  </phr>
<c id=MDS0913>,</c>
<w id=MDS0914>if</w>
<w id=MDS0915>someone</w>
<w id=MDS0916>entered</w>
<w id=MDS0917>the</w>
<w id=MDS0918>room</w>
<c id=MDS0919>,</c>
<w id=MDS0920>or</w>
<w id=MDS0921>to</w>
<w id=MDS0922>open</w>
<w id=MDS0923>both</w>
<w id=MDS0924>eyes</w>
<c id=MDS0925>,</c>
<w id=MDS0926>smile</w>
<c id=MDS0927>,</c>
<w id=MDS0928>and</w>
<w id=MDS0929>wag</w>
<w id=MDS0930>his</w>
<w id=MDS0931>tail</w>
<w id=MDS0932>as</w>
<w>
  <w id=MDS0933>he</w>
  <m id=MDS0934>'d</m>
  </w>
<w id=MDS0935>done</w>
<w id=MDS0936>on</w>
<w id=MDS0937>one</w>
<w id=MDS0938>occasion</w>
<w id=MDS0939>when</w>
<w id=MDS0940>confronted</w>
<w id=MDS0941>by</w>
<w id=MDS0942>a</w>
<w id=MDS0943>housebreaker</w>
<c id=MDS0944>!</c>
</s>]]></eg>
 </p><p>Finally, here is a <gi tei="yes">linkGrp</gi>, which contains all of the
<gi tei="yes">link</gi> elements that associate the text segments in the example
sentence with their respective grammatical structures.
 
<eg><![CDATA[<linkGrp domains='mds09 BNCgs'
         targFunc='segment analysis'>
  <link targets='mds0901 AT0'>
  <link targets='mds0902 AJS'>
  <link targets='mds0903 PNP'>
  <link targets='mds0904 VVD'>
  <link targets='mds0905 PRP'>
  <link targets='mds0906 NN1'>
  <link targets='mds0907 VBD'>
  <link targets='mds0908 TO0'>
  <link targets='mds0909 VVI'>
  <link targets='mds0910 CRD'>
  <link targets='mds0911 NN1'>
  <link targets='mds0912 AV0'>
  <link targets='mds0913 PUN'>
  <link targets='mds0914 CJS'>
  <link targets='mds0915 PNI'>
  <link targets='mds0916 VVD'>
  <link targets='mds0917 AT0'>
  <link targets='mds0918 NN1'>
  <link targets='mds0919 PUN'>
  <link targets='mds0920 CJC'>
  <link targets='mds0921 TO0'>
  <link targets='mds0922 VVI'>
  <link targets='mds0923 DT0'>
  <link targets='mds0924 NN2'>
  <link targets='mds0925 PUN'>
  <link targets='mds0926 VVI'>
  <link targets='mds0927 PUN'>
  <link targets='mds0928 CJC'>
  <link targets='mds0929 VVI'>
  <link targets='mds0930 DPS'>
  <link targets='mds0931 NN1'>
  <link targets='mds0932 CJS'>
  <link targets='mds0933 PNP'>
  <link targets='mds0934 VHD'>
  <link targets='mds0935 VDN'>
  <link targets='mds0936 PRP'>
  <link targets='mds0937 CRD'>
  <link targets='mds0938 NN1'>
  <link targets='mds0939 AVQ'>
  <link targets='mds0940 VVN'>
  <link targets='mds0941 PRP'>
  <link targets='mds0942 AT0'>
  <link targets='mds0943 NN1'>
  <link targets='mds0944 PUN'>
  </linkGrp>]]></eg>
 </p><p>This grammatical markup represents the text as completely unambiguous,
despite the fact that instances of the same textual unit are associated
with different structure elements (e.g. the word <cited>to</cited>), and at
least one sequence (namely <cited>to exercise</cited>, identified by the
attribute values <att tei="yes">id=mds0905</att> and <att tei="yes">id=mds0906</att>), is in
fact structurally ambiguous in English.  That sequence may be analyzed as
a preposition followed by a singular noun (as this markup asserts) or as
the infinitive marker followed by an uninflected form of a main verb.
 </p><p>To represent the ambiguity of words like <cited>to</cited> and
<cited>exercise</cited>, and of phrases like <cited>to exercise</cited>,
we may use the <gi tei="yes">alt</gi> and <gi tei="yes">join</gi> elements defined in sections<xref target="SAAT"/>
 and <xref target="SAAG"/>, as follows.
First, we define <gi tei="yes">alt</gi> elements for
the ambiguous word classes, and add these to the <gi tei="yes">fsLib</gi>.
 
<eg><![CDATA[<alt id=PRP-TO0 targets='PRP TO0'>
<alt id=NN1-VVI targets='NN1 VVI'>]]></eg>
 
Next, we change the <gi tei="yes">link</gi> elements for the text elements identified
by the <att tei="yes">id=mds0905</att> and <att tei="yes">id=mds0905</att> attribute values.
 
<eg><![CDATA[<link targets='mds0905 PRP-TO0'>
<link targets='mds0906 NN1-VVI'>]]></eg>
 </p><p>As the encoding now stands, the phrase <cited>to exercise</cited> has
four structural analyses associated with it:  preposition followed by
noun, preposition followed by verb, infinitive marker followed by noun
and infinitive marker followed by verb.  To narrow the choices down to
the desired two, namely preposition followed by noun and infinitive
marker followed by verb, we next form <gi tei="yes">join</gi> elements to represent
the desired sequences.
 
<eg><![CDATA[  <join id=PRP.NN1 targets='PRP NN1'>
  <join id=TO0.VVI targets='TO0 VVI'>]]></eg>
 
We then define an <gi tei="yes">alt</gi> element to express the alternation
between the two <gi tei="yes">join</gi> elements.
 
<eg><![CDATA[  <alt id=PRP.NN1-TO0.VVI targets='PRP.NN1 TO0.VVI'>]]></eg>
 
Next, we add a <gi tei="yes">phr</gi> element in the encoding of the text for the
phrase <cited>to exercise</cited>.
 
<eg><![CDATA[<phr id=MDS090506>
  <w id=MDS0905>to</w>
  <w id=MDS0906>exercise</w>
  </phr>]]></eg>
 
Finally, we add to the <gi tei="yes">linkGrp</gi> element a <gi tei="yes">link</gi> element
connecting that phrase to the <gi tei="yes">alt</gi> that represent its two
analyses.
 
<eg><![CDATA[<link targets='mds090506 PRP.NN1-TO0.VVI'>]]></eg>
 </p><p>Note that the technique of forming <gi tei="yes">join</gi> elements for sequences
of structure elements and associating them with textual units can also be
used to provide a complete structural analysis for the complex word
<cited>he'd</cited>.  First, we add an <att tei="yes">id</att> attribute for the
word.
 
<eg><![CDATA[<w id=MDS093334>
  <w id=MDS0933>he</w>
  <m id=MDS0934>'d</m>
  </w>]]></eg>
 
Next, we form a join of the structures associated separately with the
subelements <cited>he</cited> and <cited>'d</cited>.
 
<eg><![CDATA[<join id=PRP.VHD targets='PRP VHD'>]]></eg>
 
Finally, we define a link between the complex word and the new
<gi tei="yes">join</gi> element.
 
<eg><![CDATA[<link targets='mds093334 PRP.VHD'>]]></eg>
 




<?tei:EOF p2fsil.odd ??></p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2fs.odd ??><!-- 16 Feature Structures --><?tei:SOF p2ce.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ce.odd,v $
    * Revision 1.10  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.9  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.8  1994/03/27  16:28:51  lou
    * semifinal check
    * 
    * Revision 1.5  1994/03/07  14:37:11  lou
    * fix typos noted by CH; add ref to SA
    * 
    * Revision 1.4  1994/02/12  21:37:58  msmcq
    * strip ^Z
    * 
    * Revision 1.3  1994/01/21  18:09:59  lou
    *  fix typos (respon for respons; abbrev for abbr)
    * 
    * Revision 1.2  1993/09/22  18:12:55  msmcq
    * As of publication of CE, 17 Sept 93
    *--><!-- CE:  Indications of Certainty and Confidence             --><!-- Revisions:                                               --><!-- 8 jan 98 : LB : fix typos from MSM --><!-- 5 mar:  fix typos noted by Claus; add ref to SAat --><!-- 9 jan 93: LB: fix another typo ; abbrev is now abbr      --><!-- 93-09-17 : MSM : correct a typo                          --><!-- 93-09-17 : MSM : correct example of expan                --><!-- 93-09-17 : MSM : Change xref tctr to PHda                --><!-- 93-05-27 : MSM : remove tagdoc to separate file          --><!-- 93-05-25 : AHR : made file with second draft             --><!-- 93-02-27 : MSM : made file with first draft              --><div1 id="CE" n="17" name="Faisal" ref="Y"><head>Certainty and Responsibility</head><p>Encoders of text often find it useful to indicate that some aspects
of the encoded text are problematic or uncertain, and to indicate who is
responsible for various aspects of the markup of the electronic text.
These Guidelines provide three methods of recording uncertainty about the
text or its markup:
 
<list type="bullets"><item>the <gi tei="yes">note</gi> element defined in section <xref target="CONO"/> may
be used with a value of <code tei="yes" type="frag">certainty</code> for its <att tei="yes">type</att>
attribute.</item><item>the <gi tei="yes">certainty</gi> element defined in this chapter may be used
to record the nature and degree of the uncertainty in a more structured
way.</item><item>the <gi tei="yes">alt</gi> element defined in the additional tag set for
linking and segmentation may be used to provide alternative encodings
for parts of a text, as described in section <xref target="SAAT"/>.</item></list>
 
There are three methods of indicating responsibility for different
aspects of the electronic text:
<list type="bullets"><item>the TEI header records who is responsible for an electronic text
by means of the <gi tei="yes">respStmt</gi> element and other more specific elements
(<gi tei="yes">author</gi>, <gi tei="yes">sponsor</gi>, <gi tei="yes">funder</gi>, <gi tei="yes">principal</gi>,
etc.) used within the <gi tei="yes">titleStmt</gi>, <gi tei="yes">editionStmt</gi>, and
<gi tei="yes">revisionDesc</gi> elements.</item><item>the <gi tei="yes">note</gi> element may be used with a value of <code tei="yes" type="frag">resp</code>
or <code tei="yes" type="frag">responsibility</code> in its <att tei="yes">type</att> attribute.</item><item>the <gi tei="yes">respons</gi> element defined in this chapter may be used
to record fine-grained structured information about responsibility for
individual tags in the text.</item></list>
 
To use the <gi tei="yes">note</gi> and <gi tei="yes">respStmt</gi> elements, no special steps
are needed, since they are defined in the core tag set and header
respectively.  The <gi tei="yes">alt</gi> element is only available when the
additional tag set for linking has been selected, as described in
chapter <xref target="SA"/>. To use the <gi tei="yes">certainty</gi> and
<gi tei="yes">respons</gi> elements, the additional tag set for certainty and
responsibility must be selected; this is done by defining the
parameter entity <ident tei="yes" type="pe">TEI.certainty</ident> with the value
<code tei="yes" type="kw">INCLUDE</code>, as shown in the example below:
 
<eg><![CDATA[ <!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY % TEI.certainty 'INCLUDE' >
 ]>
  ...]]></eg></p><div2 id="CECERT" name="Ilocano" ref="Y"><head>Levels of Certainty</head><p>Many types of uncertainty may be distinguished.  The
<gi tei="yes">certainty</gi> element is designed to encode the following sorts:
 
<list type="bullets"><item>a given tag may or may not correctly apply (e.g. a given word may
be a personal name, or perhaps not)</item><item>the precise point at which an element begins or ends is
uncertain</item><item>the value to be given for an attribute is uncertain</item><item>content supplied by the encoder (such as the expansion of
an abbreviation marked by the <gi tei="yes">abbr</gi> tag) is
uncertain</item><item>the transcription of a source text is uncertain, perhaps
because it is hard to read or hard to hear; this sort of
uncertainty is also handled by the <gi tei="yes">unclear</gi> element in
section <xref target="PHDA"/></item></list></p><p>The following types of uncertainty are <emph>not</emph> indicated
with the <gi tei="yes">certainty</gi> element:
 
<list type="simple"><item>a number or date is imprecise</item><item>the text is ambiguous, so a given passage has several possible
interpretations</item><item>a transcriber, editor, or author wishes to indicate a level of
confidence in a factual assertion made in the text</item><item>an author is not sure if the sentence she has chosen to start a
paragraph is really the one she wants to retain in the final version</item></list>
 
Precision of numbers and dates is discussed in section <xref target="CONA"/><!-- and chapter <xref target=ND> -->
; well-defined ambiguity is handled with
alternations in feature-structure values in chapter <xref target="FS"/>.
Uncertainty about the truth of assertions in the text and other sorts of
authorial and editorial uncertainty about whether the content is
satisfactory are not handled by the <gi tei="yes">certainty</gi> element,
though they may be expressed using <gi tei="yes">note</gi>.</p><div3 id="CECENO" name="subsection" ref="Y"><head>Using Notes to Record Uncertainty</head><p>The simplest way of recording uncertainty about markup is to attach a
note to the element or location about which one is unsure.  In the
following (invented) paragraph, for example, an encoder might be
uncertain whether to mark <q>Essex</q> as a place name or a personal
name, since both might be plausible in the given context:
 
<q rend="display">Elizabeth went to Essex.  She had always liked Essex.</q>
 
Using <gi tei="yes">note</gi>, the uncertainty here may be recorded quite simply:
 
<eg><![CDATA[<persName>Elizabeth</> went to
<placeName>Essex</>.
She had always liked <placeName>Essex</>.
<note type='uncertainty' resp='MSM'>It is not
clear here whether <mentioned>Essex</mentioned>
refers to the place or to the nobleman. -MSM</note>]]></eg></p><p>Using the normal mechanisms, the note may be associated
unambiguously with specific elements of the text, thus:
 
<eg><![CDATA[<persName>Elizabeth</> went to
<placeName id=P1>Essex</>.
She had always liked <placeName id=P2>Essex</>.
<note type='uncertainty' resp='MSM' target='P1 p2'>
It is not clear here whether <mentioned>Essex</mentioned>
refers to the place or to the nobleman.  If the latter,
it should be tagged as a personal name. -MSM</note>]]></eg></p><p>The advantage of this technique is its relative simplicity.  Its
disadvantage is that the nature and degree of uncertainty are not
conveyed in any systematic way and thus are not susceptible to any sort
of automatic processing.</p></div3><div3 id="CECECE" name="subsection" ref="Y"><head>Structured Indications of Uncertainty</head><p>To record uncertainty in a more structured way, susceptible of at
least simple automatic processing, the <gi tei="yes">certainty</gi> element may be
used:
 
<tagList style="one-line"><tagDesc tagDoc="CERTAIN" atts="target locus given degree assertedValue desc"/></tagList></p><p>The <gi tei="yes">certainty</gi> element may be used to record doubts about
the proper encoding of <q>Essex</q> in several ways of varying
precision.  To record merely that we are not certain that <q>Essex</q>
is in fact a place name, as it is tagged, we use the <att tei="yes">target</att>
attribute to identify the element in question, and the <att tei="yes">locus</att>
attribute to indicate what aspect of the markup we are uncertain about
(here:  whether we have used the correct element type):
 
<eg><![CDATA[Elizabeth went to <placeName id=P1>Essex</>.
 
<!-- ... elsewhere in the document ... -->
<certainty target=P1 locus='#gi' desc='possibly not a placename'>]]></eg>
 
Because it is linked to the location of the uncertainty by an IDREF, the
<gi tei="yes">certainty</gi> element will typically be included in the same SGML
document as its target.  It may be placed adjacent to the target
element, or elsewhere in the document.</p><p>To record the further information that we estimate, subjectively,
that there is a 60 percent chance of <q>Essex</q> being a place name here, we
can add a value for our <att tei="yes">degree</att> of confidence (usually a
number between 0 and 1, representing the estimated probability):
 
<eg><![CDATA[Elizabeth went to <placeName id=P1>Essex</>.
 
<!-- ... -->
<certainty target=P1 locus='#gi'
           degree='0.6'
           desc='possibly not a placename'>]]></eg>
 
According to one expert, there is a 60 percent chance of
<q>Essex</q> being a place name here, and a 40 percent chance of its being a
personal name. We use two <gi tei="yes">certainty</gi> elements to indicate the
two probabilities independently. Both elements indicate<!-- , we use the <att>resp</att> attribute to associate the
certainty information with AR.  To specify the second probability, we
use a second <gi>certainty</gi> element, pointing at -->
the same location in the text, but the second provides an alternative
choice of generic identifier (here: <code tei="yes" type="frag">persName</code>) is given as the
value of the <att tei="yes">assertedValue</att> attribute:
 
<eg><![CDATA[Elizabeth went to <placeName id=P1>Essex</>.
 
<!-- ... -->
<certainty target=P1 locus='#gi'
           degree='0.6'
           desc='probably a placename, but possibly not'>
<certainty target=P1 locus='#gi'
           degree='0.4'
           assertedValue='persName'
           desc='may refer to the Earl of Essex'>]]></eg></p><p>Finally, we may wish to make our probability estimates contingent
on some condition.  In the passage <q>Elizabeth went to Essex; she had
always liked Essex,</q> for example, we may feel there is a 60 percent chance
that the county is meant, and a 40 percent chance that the earl is meant.  But
the two occurrences of the word are not independent:  there is (we may
feel) no chance at all that one occurrence refers to the county and one
to the earl.  We can express this by using the <att tei="yes">given</att>
attribute to list the SGML identifiers of <gi tei="yes">certainty</gi> elements.
 
<eg><![CDATA[Elizabeth went to <placeName id=P1>Essex</>.
She had always liked <placeName id=P2>Essex</>.
 
<!-- ... -->
<!-- 60% chance that P1 is a placename,
     40% chance a personal name. -->
<certainty id=CERT-1
           target=P1 locus='#gi' degree='0.6'
           desc='probably a placename, but possibly not'>
<certainty id=CERT-2
           target=P1 locus='#gi' degree='0.4'
           assertedValue='persName'
           desc='may refer to the Earl of Essex'>
 
<!-- 60% chance that P2 is a placename,
     40% chance a personal name.
     100% chance that it agrees with P1. -->
<certainty given=cert-1
           target=P2 locus='#gi' degree='1.0'
           desc='if P1 is a placename, P2 certainly is'>
<certainty given=cert-2
           target=P2 locus='#gi' degree='1.0'
           assertedValue='persName'
           desc='if p1 refers to the Earl of Essex, so does P2'>]]></eg>
 
When <att tei="yes">given</att> conditions are listed, the <gi tei="yes">certainty</gi>
element is interpreted as claiming a given degree of confidence in a
particular markup given the assertional content of the
<gi tei="yes">certainty</gi> elements indicated---that is, <emph>if the markup
described in the indicated <gi tei="yes">certainty</gi> elements is
correct.</emph></p><p>Conditional confidence may be less that 100 percent:  given the sentence
<q>Ernest went to old Saybrook</q>, we may interpret <q>Saybrook</q> as
a personal name or a place name, assigning a 60 percent probability to the
former.  If it is a place name, there may be a 50 percent chance that the
place name actually in question is <q>Old Saybrook</q> rather than
<q>Saybrook</q>, while if it is correctly tagged as a personal name, it
is much more likely (say, 90 percent certain) that the name is <q>Saybrook</q>.
This state of affairs can be expressed using the
<gi tei="yes">certainty</gi> element thus:
 
<eg><![CDATA[Earnest went to <anchor id=A1> old
<persName id=P1>Saybrook</persName>.
 
<certainty id=C1 target=P1 locus='#gi' degree='0.6'>
<certainty given=c1 target=P1 locus=startloc degree='0.9'>
 
<certainty id=C2 target=P1 locus='#gi'
           assertedValue='persName' degree='0.4'>
<certainty given=c2 target=P1 locus=startloc degree='0.5'>
<certainty id=C3
           given=c1 target=P1 locus=startloc
           assertedValue='a1' degree='0.5' >]]></eg>
In this case, the <att tei="yes">assertedValue</att> on <gi tei="yes">certainty</gi> element
c3 is an IDREF to an <gi tei="yes">anchor</gi> element at the alternate starting
point for the element.</p><p>Multiplying the numeric values out, this markup may be interpreted as
assigning specific probabilities to three different ways of
marking up the sentence:
 
<eg><![CDATA[Earnest went to old <persName>Saybrook</>.   (0.6 * 0.9, or 0.54)
Earnest went to old <placeName>Saybrook</>.  (0.4 * 0.5, or 0.20)
Earnest went to <placeName>old Saybrook</>.  (0.4 * 0.5, or 0.20)]]></eg>
 
The probabilities do not add up to 1.00 because the markup indicates
that if <q>Saybrook</q> is (part of) a personal name, there is a
10 percent likelihood that the element should start somewhere other than the
place indicated, without however giving an alternative location; there
is thus a 6 percent chance (0.1 * 0.6) that none of the alternatives given is
correct.</p><p>If an attribute value is uncertain, the <att tei="yes">locus</att> attribute
takes as its value the name of the attribute in question.  In this
example, there is only a 50 percent chance that the question was spoken by
participant A:
 
<eg><![CDATA[<u id=U1 who=A>Have you heard the election results?</u>
<!-- ... -->
<certainty target=U1 locus=who degree='0.5'>]]></eg></p><p>Doubts about whether the transcription is correct may be expressed
by assigning to <att tei="yes">locus</att> the value
<code tei="yes" type="frag">#transcribedContent</code>.  For example, if the source is
hard to read and so the transcription is uncertain:
 
<eg><![CDATA[I have a <emph id=P1>gub</emph>.
<certainty target=P1 locus='#transcribedContent' degree='0.5'>]]></eg></p><p>Degrees of confidence in the proper expansion of abbreviations may
also be expressed, by using the value <code tei="yes" type="frag">#suppliedContent</code>:
 
<eg><![CDATA[You will want to use <expan id=E1 abbr='SGML'>Standard
Generalized Markup Language</expan> ...
 
<!-- ... -->
<certainty target=E1 locus='#suppliedContent' degree='0.9'>]]></eg></p><p>The <att tei="yes">assertedValue</att> attribute should be used to provide an
alternative value for whatever aspect of the markup is in doubt:  an
alternative generic identifier, or the ID of an alternative starting or
ending point, as already shown, an alternative attribute value, or
alternative element content, as in this example:
 
<eg><![CDATA[I have a <emph id=P1>gub</emph>.
 
<certainty target=P1 locus='#transcribedContent'
           assertedValue='gun'
           degree='0.8'
           desc='a gun makes more sense in a holdup'>]]></eg>
 
Since attribute values have no internal substructure, the
<att tei="yes">assertedValue</att> attribute is useful for specifying alternative
transcriptions only in relatively restricted circumstances
(specifically, when the alternate reading has no elements nested within
it).  More robust methods of handling uncertainties of transcription are
the <gi tei="yes">unclear</gi> element and the <gi tei="yes">app</gi> and <gi tei="yes">rdg</gi>
elements described in chapter <xref target="TC"/>.<!-- Parts of this para cut according to Durand's recommendation -->
 <!-- 
<p>There are many subtleties in the indication of uncertainty and the
<gi>certainty</gi> element does not provide a fully general solution, or
even an unproblematic one.  In particular no claim is made that this
mechanism can express every sort of uncertainty that an encoder may wish
to assert, nor that it is wholly free from ambiguities.  However, the
-->
 The
<gi tei="yes">certainty</gi> element allows for indications of uncertainty to
be structured with at least as much detail and clarity as appears to be
currently required in most ongoing text projects.  <!-- Encoders who wish to
disambiguate some use of this element, or to extend the recommended
attribute values, may document these assumptions or special vocabulary.
-->
It is expected that in the future more adequate systems for expressing
uncertainty will be developed.  These may extend the <gi tei="yes">certainty</gi>
element or they may make use of the feature-structure encoding
mechanisms described in chapter <xref target="FS"/>.</p><p>The <gi tei="yes">certainty</gi> element and the other TEI mechanisms for
indicating uncertainty provide a range of methods of graduated
complexity.  Simple expressions of uncertainty may be made by using the
<gi tei="yes">note</gi> element.  This is simple and convenient, and can
accommodate either discursive unstructured indication of uncertainty, or
complex structured project-specific expressions of uncertainty.  In
general, however, unless special steps are taken, the <gi tei="yes">note</gi>
element does not provide as much expressive power as the
<gi tei="yes">certainty</gi> element, and in cases where highly structured
certainty information must be given, it is recommended that the
<gi tei="yes">certainty</gi> element be used.</p><p>The <gi tei="yes">certainty</gi> element may be used for simple unqualified
indications of uncertainty, in which case only the <att tei="yes">locus</att>
and <gi tei="yes">target</gi> might be specified.  In more complex cases, the
other attributes may be used to provide fuller information.  While
they may take any string of characters as value, the recommended
values should be used wherever possible; if they are not appropriate
in a given situation, encoders are should provide their own controlled
vocabulary and document it in the <gi tei="yes">encodingDesc</gi> or
<gi tei="yes">tagUsage</gi> elements of the TEI header.</p><p>The <gi tei="yes">certainty</gi> element has the following formal declaration:
 
<dtdFrag id="DCE" n="Certainty and uncertainty" file="teicert2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><tagDecl tagDoc="CERTAIN"/><dtdRef dtdFrag="DCERESP"/></dtdFrag></p></div3></div2><div2 id="CERESP" name="Ilocano" ref="Y"><head>Attribution of Responsibility</head><p>In general, attribution of responsibility for the transcription and
markup of an electronic text is made by <gi tei="yes">respStmt</gi> elements
within the header: specifically, within the title statement, the
edition statement(s), and the revision history.</p><p>In some cases, however, more detailed element-by-element information
may be desired, in order to distinguish, for example, between the
individuals responsible for transcribing the content and those
responsible for determining that a given word or phrase constitutes a
proper noun.  Where such fine-grained attribution of responsibility is
required, the <gi tei="yes">respons</gi> element may be used:
 
<tagList style="one-line"><tagDesc tagDoc="RESPONS" atts="target locus resp desc"/></tagList></p><p>This element allows one or more aspects of the markup to be
attributed to a given individual.  The <att tei="yes">target</att> and
<att tei="yes">locus</att> attributes function as they do on the
<gi tei="yes">certainty</gi> element described in section <xref target="CECERT"/>:
the <att tei="yes">target</att> attribute points at a particular SGML element (or
set of elements), and <att tei="yes">locus</att> indicates the particular aspect
of the encoding of those elements, for which responsibility is to be
assigned.  The suggested values may be combined as appropriate:  to
indicate, for example, that RC is responsible for transcribing an
illegible word, and that AR is responsible for identifying that word
as a proper noun, the text might be encoded thus:
 
<eg><![CDATA[ Earnest went to old <persName id=P1>Saybrook</persName>.
 <!-- ... -->
 <respons target=P1 locus='#transcribedContent' resp=RC>
 <respons target=P1 locus='#gi #location' resp=AR>]]></eg></p><p>Some elements bear specialized <att tei="yes">resp</att> or <att tei="yes">agent</att>
attributes, which have specific meaning which varies from element to
element; the <gi tei="yes">respons</gi> element should be reserved for the general
aspects of responsibility common to all text transcription and SGML
markup, and should not be confused with the more specific attributes on
individual elements.<!-- oh yeah? which ones? (LB) --></p><p>The formal declaration of the <gi tei="yes">respons</gi> element is this:
 
<dtdFrag id="DCERESP" n="Responsibility for markup"><tagDecl tagDoc="RESPONS"/></dtdFrag></p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ce.odd ??><!-- 17 Certainty      --><?tei:SOF p2ph.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: p2ph.odd,v $
    * Revision 1.17  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.16  98/02/01  16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    * 
    * Revision 1.15  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.14  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.13  1994/04/07  16:59:05  msmcq
    * Typo correction
    * 
    * Revision 1.12  1994/04/01  16:31:57  msmcq
    * changes during validation of DTDs
    * 
    * Revision 1.11  1994/03/28  17:52:51  msmcq
    * correct dtdref error
    * 
    * Revision 1.10  1994/03/28  15:07:51  lou
    * fix ident tags
    * 
    * Revision 1.9  1994/03/27  16:31:02  lou
    * se,mifnal techal
    * 
    * Revision 1.5  1994/03/08  03:42:49  msmcq
    * validation fixes
    * 
    * Revision 1.3  1994/02/11  23:04:12  msmcq
    * add RCS id, log keywords
    * --><!-- Revisions:                                               --><!-- 14 jan 98 : LB : more typos in egs --><!-- 7 jan 98 : LB : typos from MSM; also, revise discussion of HAND --><!-- 4 Jan 98 : LB : correct erroneous eg of damage --><!-- 94-04-07 : MSM : spell Voluspa correctly (NOT an umlaut!) --><!-- 94-03-30 : MSM : suppress ornamentation again (as per lb) --><!-- 94-03-29 : MSM : refer to space and ornament dtdfrags    --><!--                  from main fragment                      --><!-- 94-03-29 : MSM : add section on ornaments                --><!-- 94-03-29 : MSM : add handlist to dtdfrag                 --><!-- 94-03-07 : MSM : supply TYPE on adlist                   --><!-- 94-03-07 : MSM : changes as per CH                       --><!-- 94-03-07 : MSM : CH changes                              --><!-- 94-03-07 : MSM : partway through Claus's changes         --><!-- 94-03-04 : MSM : change edit class reference to editph   --><!-- 94-03-03 : MSM : changes, corrections from RC            --><!-- 94-03-03 : MSM : Robin Cover's fixes                     --><!-- 94-02-11 : MSM : Added RCS id                            --><!-- 94-02-04 : MSM : revisions (msm,pr)                      --><!-- 94-02-03 : MSM : move use-of-app section to TC           --><!-- 94-01-27 : MSM : fix idref problems, hack edit class (temp) --><!-- 94-01-27 : MSM : fix tagging problems                    --><!-- 94-01-27 : MSM : reached end.  Still need exx for skel   --><!-- 94-01-26 : MSM : begin first pass for P3                 --><!--                  rename omit as gap (as agreed w/LB)     --><!--                  correct underscores in ent names        --><!-- 93-06-03 : MSM : add editorial note                      --><!-- 27 May : LB fixed tagging; changed refs to PHce to PHhr  --><!-- 93-05-23 : PR: following Eynsham Hall meeting, ch..      --><!--                  split into two.  Fixes (editorial,      --><!--                  typos etc).  Cert and resp treatment    --><!--                  updated, subvariation added             --><!-- 93-04-12 : MSM : SGML corrections after validating.      --><!-- 93-04-12 : MSM : Addtl. SGML Changes                     --><!-- 93-04-12 : MSM : Addtl SGML changes                      --><!-- 93-04-09 : wp : More SGML corrections, mostly taglists. --><!-- 93-04-09 : wp : Various SGML corr. ( < / > and < / eg >. --><!-- 93-04-08 : MSM : strip mail header                       --><!--                  fix many, many SGML problems            --><!-- 31 MAR 93 : PR : minor changes, following suggestions    --><!--                  by Robin Cover etc, to second part      --><!--                  tidying up of first part                --><!-- 31 MAR 93 : PR : minor changes, following suggestions    --><!--                  by Claus Huitfeldt, to first part       --><!-- 27 MAR 93 : PR : incorporate examples, make changes      --><!--                  and additions re rdg/wit, restore, supplied --><!--                  transcription part given more substance to  --><!--                  incorporate mss group materials         --><!-- 93-03-01 : MSM : change N values on divs                 --><!-- 93-03-01 : MSM : change abbrev tag to abbr               --><!-- Chapter on Textual Criticism for P2                      --><!--                                                          --><!-- 27 Feb 93 : MSM : complete additions, light revision     --><!--                   to line 800                            --><!-- 21 Feb 93 : MSM : add tagdocs, revise very lightly       --><!--    Sep 92 : MSM : remove CO tags, add P2X tagging        --><!--  7 Sep 92 : MSM : received in Chicago                    --><!-- 12 Jun 92 : PR : revised following Chicago meeting.      --><!--                  Xrefs indicated by formula (xref xxx),  --><!--                  except for the one to feature           --><!--                  structures, indicated < xref            --><!--                  target = P2.44 >                        --><!--                  This document not oddified, despite my  --><!--                  good intentions.  Sorry, I quailed.     --><!-- 10 May 92 : PR : revised following discussions with MSMQ --><!--    Nov 91 : PR : draft, circulate to TR2                 --><div1 id="PH" n="18" name="Faisal" ref="Y"><head>Transcription of Primary Sources</head><p>This chapter defines an optional additional tag set intended for use
in the transcription of primary sources, in particular manuscripts,
and describes how some
elements defined in the core tag set should be used for this work.  It
is expected that this tag set will be especially useful in the
preparation of critical editions, but the tag set defined here is
distinct from that defined in chapter <xref target="TC"/>, and may be used
independently of it.
 <!-- <note place=foot>Responsibility for this chapter was borne --><!-- by work groups TR 2 (Textual Criticism), headed by Peter --><!-- Robinson, and TR 9 (Manuscripts and Codicology), headed by --><!-- Claus Huitfeldt; the full membership of the work groups is --><!-- given in the front matter.  The draft was prepared by Peter --><!-- Robinson and Claus Huitfeldt, with extensive assistance from --><!-- Robin Cover.</note> --></p><p>Scholars may wish to record information concerning individual
readings of letters, words or larger units, both within transcriptions
and within editions.  They may also wish to include other editorial
material within transcriptions, such as comments on the status or
possible origin of particular readings, corrections, or text supplied to
fill lacunae, etc.  Further, it is customary in transcriptions to
register certain features of the source, such as ornamentation,
underlining, deletion, areas of damage and lacunae.  This chapter
indicates means to record such information:
 
<list type="bullets"><item>first, the problem of recording editorial or other alterations to
the text, such as expansion of abbreviations, corrections, conjectures,
etc. (section <xref target="PHCH"/>)</item><item>then, methods of describing important extra-linguistic phenomena
in the source: unusual spaces, lines, page and line breaks, change of
manuscript hand, etc. (section <xref target="PHPH"/>)</item><item>finally, a method of recording material such as running heads,
catch-words, and the like (section <xref target="PHSK"/>)</item></list></p><p>These recommendations are not intended to meet every
transcriptional circumstance likely to be faced by any scholar.
Rather, they should be regarded as a base which can be elaborated if
necessary by different scholars in different disciplines, with
distinct scholarly domains eventually developing their own document
types.  In time, the feature structure notation developed in chapter<xref target="FS"/>
, may also permit scholars to tailor the encoding of
complex transcriptional information in ways not here anticipated.  In
particular, this chapter focuses in its current state primarily upon
problems associated with the transcription of manuscript materials;
problems of codicology and problems peculiar to early printed
materials are not treated.  Many of the recommendations presented here
may --- mutatis mutandis --- apply to printed matter, but a great deal
of work remains to done in these areas, and the encoder will need to
take even more individual responsibility than usual in applying the
recommendations of this chapter in these contexts.</p><p>Many of the descriptions below use terms like
<soCalled>scribe</soCalled>, <soCalled>author</soCalled>,
<soCalled>editor</soCalled>,
<soCalled>annotator</soCalled>,
<soCalled>corrector</soCalled>,
<soCalled>transcriber</soCalled>,
and <soCalled>encoder</soCalled>, to make
clear how they apply in cases where these roles are distinct.  To the
extent that these roles are not distinct (for example, in authorial
manuscripts where the author and the scribe are the same person) the
interpretation of the markup should be adjusted appropriately.
Many of the elements defined here apply (within limits) also in
cases of printed materials, so <soCalled>compositor</soCalled>, etc.,
may also be understood as applying where appropriate.</p><p>As a rule, all elements which may be used in the course of a
transcription of a single witness may also be used in a critical
apparatus, i.e. within the elements proposed in chapter <xref target="TC"/>.
This can generally be achieved by nesting a
particular reading containing tagged elements from a particular witness
within the <gi tei="yes">rdg</gi> element in an <gi tei="yes">app</gi> structure.
 <!-- sentence omitted, since I don't understand what is       --><!-- meant and don't think we make good on this claim.        --><!-- (msm)                                                    --><!-- In certain cases, indicated below, such nesting will     --><!-- not be possible, and other means are suggested.          --></p><p>Just as a critical apparatus may contain transcriptional elements
within its record of variant readings in various witnesses, one may
record variant readings in an individual witness by use of the apparatus
mechanisms <gi tei="yes">app</gi> and <gi tei="yes">rdg</gi>.  This is discussed in section<xref target="TCTR"/>
.<!-- suggested addition by CH, with additional addition by    --><!-- MSM.  suppressed by MSM                                  --><!-- Applications of considerable sophistication may be       --><!-- needed to make full use of all the information which     --><!-- can be recorded using the tag set defined here.  In      --><!-- the absence of such applications, some scholars may      --><!-- feel that the present cost of more informative           --><!-- encoding outweighs the potential future benefits:  in    --><!-- such cases it may be preferred to record only the        --><!-- relatively simple information which can be captured      --><!-- with the suggestion applications of the core tag set     --><!-- described below.  It should also be kept in mind,        --><!-- however, that the capabilities of current software       --><!-- will often be wholly irrelevant when projects begun      --><!-- today are completed some years hence.                    --></p><p>The tag set defined in this chapter may be selected using the
mechanisms described in section <xref target="STIN"/>; in a document using
this tag set, the document-type-declaration subset should contain the
following declaration of the parameter
entity <ident tei="yes" type="pe">TEI.transcr</ident>, or the
equivalent:
 
<eg><![CDATA[<!ENTITY % TEI.transcr 'INCLUDE' >]]></eg>
 
In a document using this tag set together with that for textual
criticism and the base tag set for verse, the entire document type
declaration might resemble the following:
 
<eg><![CDATA[<!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
   <!ENTITY % TEI.prose 'INCLUDE' >
   <!ENTITY % TEI.transcr 'INCLUDE' >
   <!ENTITY % TEI.textcrit 'INCLUDE' >
]>]]></eg></p><p>The overall structure of the tag set defined by this chapter is as
follows:
 
<dtdFrag id="DPH" n="Transcription of Primary Sources" file="teitran2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><dtdRef dtdFrag="DTCAD"/><dtdRef dtdFrag="DPHCD"/><dtdRef dtdFrag="DPHOM"/><dtdRef dtdFrag="DPHHD"/><dtdRef dtdFrag="DPHDA"/><dtdRef dtdFrag="DPHSP"/><dtdRef dtdFrag="DTCHD"/></dtdFrag><!-- <dtdRef dtdFrag=DPHORN>                                  --></p><p>This tag set modifies the element class
<ident tei="yes" type="class">edit</ident> by declaring two extra attributes
for members of the class:
 
<dtdFrag id="DPHENT" n="Attributes for Transcription of Primary Sources" file="teitran2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><claDecl classDoc="EDITPH" type="atts"/></dtdFrag></p><div2 id="PHCH" name="Ilocano" ref="Y"><head>Altered, Corrected, and Erroneous Texts</head><p>In the detailed transcription of any source, it may prove necessary
to record various types of actual or potential alteration of the text:
expansion of abbreviations, correction of the text (by the author, by a
scribe, by a later hand, or by the encoder), addition, deletion, or
substitution of material, and the like.  The sections below describe how
such phenomena may be encoded using either elements defined in the core
tag set (defined in chapter <xref target="CO"/>) or specialized elements
available only when the additional tag set described in this chapter is
available.</p><div3 id="PHCO" name="subsection" ref="Y"><head>Use of Core Tags for Transcriptional Work</head><p>In transcribing individual sources (editions, manuscripts, witnesses
of any type), encoders may record their corrections, normalizations,
expansions of abbreviations, additions, and omissions
using the elements described in section <xref target="COED"/>.  Those particularly relevant to this chapter include:
 
<tagList style="one-line"><tagDesc tagDoc="ABBR"/><tagDesc tagDoc="EXPAN"/><tagDesc tagDoc="SIC"/><tagDesc tagDoc="CORR"/><tagDesc tagDoc="ADD"/><tagDesc tagDoc="DEL"/><tagDesc tagDoc="HI"/><tagDesc tagDoc="GAP"/></tagList>
 <!-- 93-04-12 : PR : Removed refs to reg orig etc 27/3/93     --><!-- 93-04-12 :       added add, del, hi, omit tags to list   --></p><p>When the additional tag set for transcription of primary sources
is selected,
these elements all gain two specialized attributes for specifying who is
responsible for certain aspects of the interpretation and markup, and
the certainty attributed to the interpretation:
 
<adList classDoc="EDITPH" atts="cert resp"/>
 
The specific aspect of the markup described by these attributes differs
on different elements; for further discussion, see the relevant sections
below, especially section <xref target="PHHR"/>.</p><p>The following sections describe how the core elements just named may
be used in the transcription of primary source materials.  Examples of
more complex application in scholarly transcriptions of these core
elements are given, and of their extension by linkage with the
<gi tei="yes">note</gi>, <gi tei="yes">respons</gi>, and <gi tei="yes">certainty</gi> elements.  Where the
core elements do not satisfy the needs of scholarly transcription,
additional elements are defined.</p></div3><div3 id="PHAB" name="subsection" ref="Y"><head>Abbreviation and Expansion</head><p>The writing of manuscripts by hand lends itself to the use of
abbreviation to shorten scribal labour.  Commonly occurring letters,
groups of letters, words or even whole phrases, may be represented by
significant marks.  This phenomenon of manuscript abbreviation is so
widespread and so various that no taxonomy of it is here attempted.
Instead, methods are shown which allow abbreviations to be encoded using
the core elements mentioned above.</p><p>A manuscript abbreviation may be viewed in two ways.  One may
transcribe it as a particular sequence of letters or marks upon the
page: thus, a <q>p with a bar through the descender</q>, a
<q>superscript hook</q>, a <q>macron</q>.  One may also interpret the
abbreviation in terms of the letter or letters it is seen as standing
for: thus, <q>per</q>, <q>re</q>, <q>n</q>.  Both of these views are
supported by these Guidelines.  The entity reference system allows the
encoder to declare whatever entities are needed, using entity names
like <ident tei="yes" type="ent">p-underbar</ident>, <ident tei="yes" type="ent">sup-hook</ident>, or <ident tei="yes" type="ent">macron</ident>.
Furthermore, each entity reference may be linked to an image of the
abbreviation itself, so that the reader might see a rendering of the
text's appearance.  Alternatively, the encoder may transcribe the
letter or letters he or she believes the abbreviation stands for, as
the content of an <gi tei="yes">expan</gi> element: thus
<tag compl="full" tei="yes">expan</tag>per<tag compl="full" tei="yes">/</tag>, <tag compl="full" tei="yes">expan</tag>re<tag compl="full" tei="yes">/</tag>,
<tag compl="full" tei="yes">expan</tag>n<tag compl="full" tei="yes">/</tag>.</p><p>These two methods of coding abbreviation may also be combined.  An
encoder may record, for any abbreviation, both
the sequence of letters or marks which constitutes it, and
its sense, that is, the letter or letters for
which it is believed to stand.  For example, the
abbreviations of <cited>euery persone</cited> in the following fragment
<note source="auth" place="foot" anchored="Y">From <q>The Manere of Good Lyuynge</q>, fol 126v of
Bodleian MS Laud Misc. 517, plate 8(ii) in <title>English Cursive Book
Hands 1250-1500</title> by M. B. Parkes (Clarendon Press:  Oxford,
1969).</note>
may be transcribed as follows, using the <gi tei="yes">expan</gi> element, with
the <att tei="yes">abbr</att> attribute to hold an  entity reference for the
brevigraph indicating the abbreviation in the manuscript:
 
<eg><![CDATA[eu<expan abbr="&er;" resp="MP">er</>y
<expan abbr="&p-underbar">per</>sone that
loketh after heuen hath a place in this ladder]]></eg>
 
Alternatively, the abbreviations may be encoded using the <gi tei="yes">abbr</gi>
element.
 
<eg><![CDATA[eu<abbr expan="er" resp=MP>&er;</>y
<abbr expan="per">&p-underbar</>sone that
loketh after heuen hath a place in this ladder]]></eg></p><p>The choice between the <gi tei="yes">expan</gi> and <gi tei="yes">abbr</gi>
elements is left to the encoder.  As a rule, the <gi tei="yes">abbr</gi> element
should be preferred where it is wished to signify that the content of
the element is an abbreviation, without necessarily indicating what the
abbreviation may stand for.  The <gi tei="yes">expan</gi> element should be used
where it is wished to signify that the content of the element is an
expanded text, without necessarily indicating the abbreviation used in
the original.  The decision as to which (<gi tei="yes">abbr</gi> or
<gi tei="yes">expan</gi>) to use may vary from abbreviation to abbreviation; there
is no requirement that the one system be used throughout a
transcription.  However, processing may be simplified if one only of
these is used throughout a transcription.  The choice is likely to be a
matter of editorial policy, which might be applied consistently
throughout.  If the highest priority is to transcribe the text
literatim, while indicating the presence of abbreviations, the choice<!-- "litteratim" is an adverb! -->
will be to use <gi tei="yes">abbr</gi> throughout.  If the highest priority is to
present a reading transcription, while indicating that some letters or
words are expansions of abbreviations, the choice will be to use
<gi tei="yes">expan</gi> throughout.</p><p>Further information may be attached to instances of these elements by
the <gi tei="yes">note</gi> element, on which see section <xref target="CONO"/>, and
by use of the <att tei="yes">resp</att> and <att tei="yes">cert</att> attributes.  In this
instance from the English <title>Brut</title>,<note source="auth" place="foot" anchored="Y">On fol
65v of Bodleian MS. Rawlinson Poetry 32; in Parkes 12(ii).</note>
a note is attached to an editorial expansion of the tail on the final d
of <cited>good</cited> to <cited>goode</cited>:
 
<eg><![CDATA[For alle the while that I had
good<expan id=EXP01 abbr="&tail;">e</>
I was welbeloued]]></eg>
 
Then the note:
 
<eg><![CDATA[<note target=EXP01>The stroke added to the final d could
signify the plural ending (-es, -is, -ys>) but the
singular <hi rend=it>good</> was used with the meaning
<q>property</q>, <q>wealth</q>, at this time (v. examples
quoted in OED, sb. Good, C. 7, b, c, d and 8 spec.)</note>]]></eg>
 
The editor might declare a degree of certainty for this expansion, based
on the OED examples, and state the responsibility for the expansion:
 
<eg><![CDATA[For alle the while that I had
good<expan abbr="&tail;"
           cert=90
           resp="MP">e</>
I was welbeloued]]></eg>
 
Observe that the <att tei="yes">cert</att> and <att tei="yes">resp</att> attributes may be
used with the <gi tei="yes">expan</gi> element only to indicate respectively
confidence in the content of the element, (i.e., the expansion) and the
responsibility for suggesting this expansion.  In the case of the use of
these attributes with the <gi tei="yes">abbr</gi>, the <att tei="yes">cert</att> and
<att tei="yes">resp</att> attributes are defined as indicating respectively
confidence in the expansion held in the <att tei="yes">expan</att> attribute and
the responsibility for suggesting this expansion.  The above example
could be encoded using the <gi tei="yes">abbr</gi> element as follows:
 
<eg><![CDATA[For alle the while that I had
good<abbr expan="e"
          cert=90
          resp="MP">&tail;</>
I was welbeloued]]></eg>
 
If it is desired to express aspects of certainty and responsibility for
some other aspect of the use of these elements, then the mechanisms
discussed in chapter <xref target="CE"/> should be used.  See also <xref target="PHHR"/> for discussion of the issues of certainty and
responsibility in the context of transcription.</p><p>If more than one expansion for the same abbreviation is to be
recorded, it is recommended that the markup for critical apparatus be
used; an example is given in section <xref target="TCTR"/>.</p></div3><div3 id="PHCC" name="subsection" ref="Y"><head>Correction and Conjecture</head><p>The <gi tei="yes">sic</gi> and <gi tei="yes">corr</gi> elements, defined in the core tag
set, may be used to register authorial or scribal corrections within a
witness.  For example, in the manuscript of William James's <title>A
Pluralistic Universe</title>, edited by Fredson Bowers (Cambridge:
Harvard University Press, 1977) a sentence first written
 
<q rend="display">One must have lived longer with this system,
to appreciate its advantages.</q>
 
has been modified by James to begin <q>But one must ...</q>, without the
inital capital O having been reduced to lowercase.  This non-standard
orthography could be recorded and corrected thus:
 
<eg><![CDATA[But <sic corr="one">One</> must have lived ...]]></eg>
 
The same information could be conveyed by the <gi tei="yes">corr</gi> element:
 
<eg><![CDATA[But <corr sic="One">one</> must have lived ...]]></eg>
 
In this example from Albertus Magnus,<note source="auth" place="foot" anchored="Y"><title>De
Nutrimento et Nutribili, Tractatus 1</title>, fol 217r col b of Merton
College Oxford MS O.2.1, (Parkes pl. 16).</note>
both the manuscript error <cited>angues</cited> and its correction
<cited>augens</cited> are registered by the <gi tei="yes">sic</gi> element:
 
<eg><![CDATA[Nos autem iam ostendimus quod nutrimentum
et <sic corr=augens>angues</>.]]></eg>
 
The same information could be conveyed by the <gi tei="yes">corr</gi> element:
 
<eg><![CDATA[Nos autem iam ostendimus quod nutrimentum
et <corr sic="angues">augens</>.]]></eg>
 
In this example, from George Moore's draft of additional materials for
<q>Memoirs of My Dead Life</q><note source="auth" place="foot" anchored="Y">In Pierpont Morgan MA
  3421, from <title>British Literary Manuscripts/Series II:  from 1800
  to 1914</title>, by V. Klinkenborg, H.Cahoon and C. Ryskamp (New York:
  Pierpont Morgan Library, 1981).</note>
the transcriber supplies the word <cited>we</cited> omitted by the author:
 
<eg><![CDATA[You see that I avoid the word create for we
create nothing <sic corr="we"></> develope.]]></eg>
 
Or with reverse use of the <gi tei="yes">corr</gi> element:
 
<eg><![CDATA[You see that I avoid the word create for we
create nothing <corr sic="">we</> develope.]]></eg>
 
(N.B. when the additional tag set defined in this chapter is selected,
the <gi tei="yes">supplied</gi> element should normally be used in preference
to <gi tei="yes">sic</gi> or <gi tei="yes">corr</gi> for such supplied text.)</p><p>As with the choice between <gi tei="yes">expan</gi> and <gi tei="yes">abbr</gi>, the
choice between the synonymous <gi tei="yes">sic</gi> and <gi tei="yes">corr</gi> elements is
left to the encoder.  As a rule, the <gi tei="yes">sic</gi> element allows the
encoding to retain the original text as the content of the element,
while simultaneously signifying that the contents of the element require
correction, but without necessarily indicating what the correction may
be.  The <gi tei="yes">corr</gi> element allows the text to be corrected, possibly
without recording the details of the faulty source, while still marking
explicitly the fact that the contents of the element have been
corrected.  The choice is likely to be a matter of editorial policy,
which might be applied consistently throughout or decided case by case.
If the highest priority is to present an uncorrected transcription while
noting perceived errors in the original, the choice will typically
be to use <gi tei="yes">sic</gi> throughout.  If the highest priority is to
present a reading transcription, while indicating that perceived errors
in the original have been corrected, the choice will be to use
<gi tei="yes">corr</gi> throughout.</p><p>Further information may be attached to instances of these elements by
the <gi tei="yes">note</gi> element and <att tei="yes">resp</att> and <att tei="yes">cert</att>
attributes.  Here, two separate corrections in Dudo of S. Quentin<note source="auth" place="foot" anchored="Y"><title>De moribus et actis primorum Normannie ducum</title>,
in fol 4v of British Library MS Harley 3742, Parkes pl 6(i).</note>
are assigned the same note.  First the corrections, held in the
attribute value of the <gi tei="yes">sic</gi> elements:
 
<eg><![CDATA[quamuis <sic corr=iners id=SIC01>mens</> que nutu dei
gesta sunt ... unde esset uiriliter
<sic corr=uegetata id=SIC02>negata</>]]></eg>
 
then the note, linked to the <att tei="yes">id</att> of the <gi tei="yes">sic</gi> element
for each of the two corrections:
 
<eg><![CDATA[<note target="SIC01 sic02">Substitution of a more
familiar word which resembles graphically what the
scribe should be copying but which
does not make sense in the context.</>]]></eg></p><p>The <att tei="yes">cert</att> attribute may also be used with the <gi tei="yes">corr</gi>
element to signify the conjectural status of a particular editorial
reading, with the <att tei="yes">resp</att> attribute used to identify the scholar
responsible for the conjecture.  In this example, editorial confidence
in E. Talbot Donaldson's emendation of the Hengwrt manuscript reading
<cited>wight</cited> to <cited>wright</cited> in line 117 of Chaucer's
<title>The Wife of Bath's Prologue</title> may be marked as follows:
 
<eg><![CDATA[Telle me also, to what conclusioun
Were membres maad, of generacioun
And of so parfit wis a <corr sic="wight" resp=ETD cert=70
id="c117">wright</> ywroght?]]></eg>
 
The editor might also conveniently add a note referring to Donaldson's
discussion of this passage:
 
<eg><![CDATA[<note target=C117>This emendation of the Hengwrt copy text,
based on a Latin source and on the reading of three late
and usually unauthoritative manuscripts, was proposed
by E. Talbot Donaldson in <title>Speculum</title> 40 (1965)
626-33.</note>]]></eg></p><p>Alternative corrections within a transcription of a single witness
may be held within an <gi tei="yes">app</gi> structure, in the same way that
alternative expansions are so grouped in the example given in section<xref target="TCTR"/>
.  Here, Donaldson's conjectured emendation of the
Hengwrt manuscript may be recorded not only alongside the editorial
transcription but also alongside another conjecture:
 
<eg><![CDATA[And of so parfit wis a
<app>
   <rdg wit=Hg>wight</rdg>
   <rdg resp=ETD wit="Ln Ry2 Ld"><corr>wright</></rdg>
   <rdg resp=PR wit="Gg"><corr>wyf</></rdg>
</app>]]></eg></p><p>Observe that no <att tei="yes">resp</att> attribute is necessary for the base
transcription:  by default, responsibility is assigned to the scholar(s)
responsible for the transcription, as identified in the TEI header.  The
conjectures are held within <gi tei="yes">corr</gi> elements, contained within the
<gi tei="yes">rdg</gi> elements.  The <att tei="yes">resp</att> attribute identifying
responsibility for each correction is attached to the outer
<gi tei="yes">rdg</gi>, and inherited by the inner <gi tei="yes">corr</gi> element.  Note
too that the support for these conjectures in other manuscripts can be
noted in the <att tei="yes">wit</att> attribute in the <gi tei="yes">rdg</gi> element.</p><p>The <att tei="yes">cert</att> and <att tei="yes">resp</att> attributes may be used with
the <gi tei="yes">corr</gi> element only to indicate respectively confidence in
the content of the element, (i.e., the correction) and the
responsibility for suggesting this correction or conjecture.  In the
case of the use of these attributes with the <gi tei="yes">sic</gi> element, the
<att tei="yes">cert</att> and <att tei="yes">resp</att> attributes are defined as indicating
respectively confidence in the conjecture held in the <att tei="yes">corr</att>
attribute and the responsibility for suggesting this conjecture.  The
above example could be encoded using the <gi tei="yes">sic</gi> element as
follows:
 
<eg><![CDATA[And of so parfit wis a
<sic corr="wright" cert=70 resp=ETD>wight</>
ywroght?]]></eg>
 
If it is desired to express aspects of certainty and responsibility for
some other aspect of the use of these elements, then the mechanisms
discussed in chapter <xref target="CE"/> should be used.  See also <xref target="PHHR"/> for discussion of the issues of certainty and
responsibility in the context of transcription.</p></div3><div3 id="PHAD" name="subsection" ref="Y"><head>Additions and Deletions</head><p>Additions and deletions to a text may be described using the
following elements:
 
<tagList style="one-line"><tagDesc tagDoc="ADD"/><tagDesc tagDoc="ADDSPAN" atts="place resp cert hand to"/><tagDesc tagDoc="DEL"/><tagDesc tagDoc="DELSPAN" atts="type status resp cert hand to"/></tagList>
 
Of these, <gi tei="yes">add</gi> and <gi tei="yes">del</gi> are included in the core tag
set, while <gi tei="yes">addSpan</gi> and <gi tei="yes">delSpan</gi> are available only when
using the additional tag set defined in this chapter.</p><p>As described in section <xref target="COED"/>, the <gi tei="yes">add</gi> element
indicating material added may be used to signify manuscript additions or
insertions, be they authorial or scribal.  In the autograph manuscript
of Max Beerbohm's <title>The Golden Drugget</title>,<note source="auth" place="foot" anchored="Y">In
    Pierpont Morgan MA 3391 (Klinkenborg 123).</note>
the author's addition of "do ever" may be recorded as follows, with the
<att tei="yes">hand</att> attribute indicating that the addition was Beerbohm's:
 
<eg><![CDATA[Some things are best at first sight.  Others -- and
here is one of them -- <add hand='MB'>do ever</add>
improve by recognition]]></eg>
 
Similarly, the <gi tei="yes">del</gi> element indicating material deleted may be
used to signify manuscript deletions.  In the autograph manuscript of D.
H. Lawrence's <title>Eloi, Eloi, lama sabachthani</title> (Pierpont
Morgan MA 1892, Klinkenborg 129), the author's deletion of
<cited>my</cited> may be recorded as follows.  As well as the
<att tei="yes">hand</att> attribute indicating that the deletion was Lawrence's,
the <att tei="yes">rend</att> attribute indicates that the deletion was by
strike-through:
 
<eg><![CDATA[For I hate this
<del hand='DHL' rend='strike-through'>my</del> body,
which is so dear to me]]></eg>
 
If deletions are classified systematically, the <att tei="yes">type</att>
attribute should normally
be used to indicate the classification; when they
are classified by the manner in which they were effected, or by their
appearance, however,
this will lead to a certain arbitrariness in deciding
whether to use the <att tei="yes">type</att> or the <att tei="yes">rend</att> attribute
to hold the information.  In general, it is recommended that the
<att tei="yes">rend</att> attribute be used for description of the appearance
or method of deletion, and that the <att tei="yes">type</att> attribute be
reserved for higher level or more abstract classifications.</p><p>Further characteristics of the addition and deletion, e.g. the date,
or ink, may be needed for detailed transcription of manuscripts.  Such
characteristics may conveniently be recorded as attributes of the
<gi tei="yes">add</gi> or <gi tei="yes">del</gi> element.  The specific attributes required
may be added to the formal declaration of these elements by using the
techniques described in chapter <xref target="MD"/>.</p><p>The <gi tei="yes">add</gi> and <gi tei="yes">del</gi> elements defined in the core tag
set available in all TEI documents will suffice for describing typically
brief additions and deletions in the text being transcribed.  On
occasion, it will be necessary to record an addition or deletion which
crosses a structural boundary in the text being encoded, for example the
addition or deletion from a manuscript of a section containing several
distinct structural subdivisions, such as poems or prose items.  These
are most conveniently encoded using the <gi tei="yes">addSpan</gi> and
<gi tei="yes">delSpan</gi> elements, available in the additional tag set defined
in this chapter.  In this example of the use of <gi tei="yes">addSpan</gi>, the
insertion of a gathering containing four neo-Eddic poems into
Landsb&oacute;kasafn (Reykjav&iacute;k, 1562 quarto) by Helgi
&Oacute;lafsson is recorded as follows.  <!-- added clarificatory sentence -->
A <gi tei="yes">hand</gi> element is
first declared, within the header of the document, to associate
the identifier <ident tei="yes" type="unknown">HEOL</ident> with Helgi. In the body of the
text, an <gi tei="yes">addSpan</gi> element
is placed to mark the beginning of the span of added text.  The
<att tei="yes">hand</att> attribute ascribes the responsibility for the addition
to the manuscript to Helgi, and the <att tei="yes">to</att> attribute declares the
identifier for the anchor which marks the end of the added text:
 
<eg><![CDATA[
<hand id=HEOL n="Helgi &Oacute;lafsson">

<!-- text of the original material ... -->
 
<addSpan type="added gathering"
         hand="HEOL"
         to=p025>
<!-- text of the four neo-Eddic poems added... -->
<anchor id=P025>
 
<!-- text of the original material continues... -->]]></eg></p><p>In this example of the use of the <gi tei="yes">delSpan</gi> element, a full
two lines of Thomas Moore's autograph of the second version of
<title>Lalla Rookh</title><note source="auth" place="foot" anchored="Y">In Pierpont Morgan MA 310,
(Klinkenborg 23).</note> are marked for omission by vertical
strike-through.  The two lines cross the structural line division marked
<tag compl="full" tei="yes">l n=2</tag>, so it would not be possible to use a single
<gi tei="yes">del</gi> element, since it would have to span the <gi tei="yes">l</gi> marker.
The lines also themselves include a further deletion and addition.  The
<gi tei="yes">delSpan</gi> element indicates the begining of the span marked for
deletion, with the <att tei="yes">to</att> attribute giving the identifier
(delend01) for an <gi tei="yes">anchor</gi> element which marks the end of the span of text so
marked:
 
<eg><![CDATA[<l n=1>
<delSpan type='vertical strike' to=delend01>
Tis moonlight <del>upon</><add>over</> Oman's sky
<l n=2> Her isles of pearl look lovelily
<anchor id=DELEND01>
</l>]]></eg></p><p>The text deleted must be at least partially legible, in order for the
encoder to be able to transcribe it.  If it is not legible at all, the
<gi tei="yes">gap</gi> element should be used to signal that the text was not
(because it could not be) transcribed; the <att tei="yes">reason</att> attribute
can give the cause of the omission from the transcription as
<q>deletion, illegible</q>.  The <gi tei="yes">gap</gi> element may optionally be
enclosed by a <gi tei="yes">del</gi> element, if it is thought useful to record
the deletion explicitly using this element.  If the deleted text is
partially legible, the <gi tei="yes">unclear</gi> element described in section<xref target="PHDA"/>
 should be used to signal the areas of text which
cannot be read with confidence; it too may be enclosed within a
<gi tei="yes">del</gi> element.  See further section <xref target="PHOM"/> and
section <xref target="PHDA"/>.</p><p>The elements <gi tei="yes">add</gi>, <gi tei="yes">del</gi>, and <gi tei="yes">gap</gi> are defined
in the core tag set and are available in all TEI documents.  The
elements <gi tei="yes">addSpan</gi> and <gi tei="yes">delSpan</gi> have the following formal
declarations:
 
<dtdFrag id="DTCAD" n="Added and Deleted Spans"><tagDecl tagDoc="ADDSPAN"/><tagDecl tagDoc="DELSPAN"/></dtdFrag></p></div3><div3 id="PHSU" name="subsection" ref="Y"><head>Substitutions</head><p>Substitution of one word or phrase for another is
perhaps the most common of all phenomena requiring special treatment
in transcription of primary textual sources.
It may be simply one word overwriting another, or
deletion of one word and its replacement by another written above it by
the same hand at the one time; the deletion and replacement may be done
by different hands at different times; there may be a long chain of
substitutions on the one stretch of text, with uncertainty as to the
order of substitution and as to the final reading.</p><p>Three different methods may be used to express substitution of one
stretch of text by another:
 
<list type="bullets"><item>the <gi tei="yes">sic</gi> and <gi tei="yes">corr</gi> elements, either individually
to encode a single substitution or nested to encode a sequence of
substitutions;</item><item>the <gi tei="yes">del</gi> and <gi tei="yes">add</gi> elements, used in sequence to
show that text was first deleted then other text inserted;</item><item>the <gi tei="yes">del</gi> and <gi tei="yes">add</gi> elements, used within an
<gi tei="yes">app</gi> structure (as defined in chapter <xref target="TC"/>) to
indicate that the deleted and added text within the individual reading
elements making up the <gi tei="yes">app</gi> structure are variants of one
another.</item></list>
 
The use of all three of these is illustrated in the following encodings
of the second line of <title>Eloi, Eloi, lama sabachthani</title> from
the Lawrence manuscript mentioned above.  Lawrence first wrote <q>How it
galls me, what a galling shadow</q>.  Subsequently, he deleted
<cited>galls</cited> and wrote <cited>dogs</cited> above the deletion.</p><p>This substitution could be registered using the first method outlined
above, as a correction using the <gi tei="yes">sic</gi> or <gi tei="yes">corr</gi> elements.
Note the use of the <att tei="yes">resp</att> attribute on the <gi tei="yes">corr</gi>
element to assign the correction to Lawrence.  (For further information
on the <att tei="yes">hand</att> and <att tei="yes">resp</att> attributes, see section<xref target="PHHR"/>
.)
 
<eg><![CDATA[How it <corr resp='DHL' sic='galls'>dogs</corr>
me, what a galling shadow]]></eg>
 
This substitution could be registered using the second method outlined
above, using the <gi tei="yes">del</gi> and <gi tei="yes">add</gi> elements in sequence to
reflect the fact that text was first deleted then other text inserted:
 
<eg><![CDATA[How it <del type=overstrike hand='DHL'>galls</del>
<add place=supralinear hand='DHL'>dogs</add>
me, what a galling shadow]]></eg>
 
This substitution could be registered using the third method outlined
above, using the <gi tei="yes">del</gi> and <gi tei="yes">add</gi> elements within an
<gi tei="yes">app</gi> structure to indicate that the deleted and added texts are
variants of one another.  Note that within the <gi tei="yes">app</gi> structure
the <att tei="yes">hand</att> attribute is moved from the inner <gi tei="yes">del</gi> and
<gi tei="yes">add</gi> elements to the outer <gi tei="yes">rdg</gi> element:
 
<eg><![CDATA[How it
  <app>
     <rdg hand='DHL'><del type=overstrike> galls</del></rdg>
     <rdg hand='DHL'><add place=supralinear> dogs</add> </rdg>
  </app>
me, what a galling shadow]]></eg>
 
Each of these three methods has its particular advantages and
disadvantages.  The first method (use of <gi tei="yes">sic</gi> or <gi tei="yes">corr</gi>)
is compact and indicates clearly that one text is a substitute for
another.  However, it provides no clear means of stating how the
substitution is effected:  whether by deletion through strike-out, or
underdotting, or erasure, followed by interlinear insertion, or marginal
insertion.  (The global <att tei="yes">rend</att> attribute might conceivably be
used, but this may not be thought an obvious place to put such
information.)  In a transcription where this information is not felt to
be important, however, this method will suffice to indicate simple cases
of direct substitution of one text for another.</p><p>The second method (use of a <gi tei="yes">del</gi> and <gi tei="yes">add</gi> sequence)
is also compact and provides means for exact declaration of how the
deletion and insertion are effected.  However, it does not indicate
explicitly that one text is a substitute for another.  It is left for
the reader or the application to infer from the <gi tei="yes">del</gi> and
<gi tei="yes">add</gi> sequence that the insertion is to be taken as a
substitution for the deletion.  In many transcriptions, the inference
may be safely drawn for simple cases of direct substitution of one text
for another.  In other transcriptions, for example of complex authorial
manuscripts, this inference may prove fragile; those who desire
to express clearly that an adjacent addition and deletion are not
independent but constitute a single act of substitution will therefore
wish to avoid this method.  Others, of course, may prefer it for
precisely the same reason, namely that it avoids prejudging the issue of
whether adjacent deletions and additions are independent or joined.</p><p>The third method (use of the <gi tei="yes">del</gi> and <gi tei="yes">add</gi> elements
within an <gi tei="yes">app</gi> structure) provides means both for exact
declaration of how the deletion and insertion are effected and for
explicit indication that one text is a substitute for another.  Further,
the exact sequence of readings may also be declared by use of the
<att tei="yes">varSeq</att> attribute on the <gi tei="yes">rdg</gi> element, as follows:
 
<eg><![CDATA[How it
  <app>
     <rdg hand='DHL' varSeq=1><del>galls</del></rdg>
     <rdg hand='DHL' varSeq=2><add>dogs</add> </rdg>
  </app>
me, what a galling shadow]]></eg>
 
Here, the combination of the <att tei="yes">hand</att> and <att tei="yes">varSeq</att>
attributes suffices to inform the reader of the authorial substitution
of <cited>dogs</cited> for <cited>galls</cited>.</p><p>Similarly, the <att tei="yes">varSeq</att> attribute might be used in a
transcription of the manuscripts of James Joyce's <title>Ulysses</title>
to indicate the sequence of Joyce's corrections which is implicit in
Hans Walther Gabler's reconstruction of the <q>overlay</q> levels of
Joyce's transcriptions.  This third method is the most powerful and
unambiguous of the three methods and enables the widest range of
processing possibilities.  However, it does suffer an apparent
disadvantage.  It introduces more markup into the text, which
can prove a burden to those working without SGML-aware editors.  The
volume of markup may be reduced by markup minimization, as in the
following recoding of the Lawrence example, but some overhead will
remain nevertheless:
 
<eg><![CDATA[How it
  <app>
     <rdg><del>galls</></>
     <rdg><add>dogs</></>
  </app>
me, what a galling shadow]]></eg>
 
A second disadvantage is that applications of considerable
sophistication may be needed to make full use of all the information
that may be held within an <gi tei="yes">app</gi> structure.  In the absence of
such applications, scholars may feel that the present cost of the more
informative coding using <gi tei="yes">app</gi> structures outweighs the future
benefits.  In making such decisions, it should however be kept in mind
that the capabilities of software at the time a project begins will often
be wholly irrelevant when the project is completed some years later.</p><p>The Lawrence example above shows the three methods used for encoding
a single substitution of one reading for another.  The same three
methods may also be used to encode longer sequences of substitutions.
In the example from William James, first written out by James as <q>One
must have lived longer with this system, to appreciate its
advantages</q> the word <cited>this</cited> is first replaced by
<cited>such a</cited> and this is then replaced by <cited>a</cited>.
<note source="auth" place="foot" anchored="Y">The manuscript contains several other substitutions,
ignored here for the sake of clarity.</note> This may be encoded using
the first method, with the sequence of substitutions shown by the
nesting of <gi tei="yes">corr</gi> elements:
 
<eg><![CDATA[One must have lived longer with
<corr sic='this'><corr sic='such a'>a</corr></corr>
system, to appreciate its advantages.]]></eg></p><p>It may be encoded using the second method, with the two changes being
treated as a sequence of additions and deletions:
 
<eg><![CDATA[One must have lived longer with
<del>this</del>
<del><add>such a</add></del>
<add>a</add> system,
to appreciate its advantages.]]></eg>
 
Note the nesting of an <gi tei="yes">add</gi> element within a <gi tei="yes">del</gi> to
record text first added, then deleted in the source.</p><p>It may be encoded using the third method, with each reading in the
series contained in a <gi tei="yes">rdg</gi> element within an <gi tei="yes">app</gi>
structure:
 
<eg><![CDATA[One must have lived longer with
  <app>
     <rdg varSeq=1><del>this</del>
     <rdg varSeq=2><del><add>such a</add></del>
     <rdg varSeq=3><add>a</add>
  </app>
system, to appreciate its advantages.]]></eg>
 
The three encodings of this slightly more complex example illustrate the
general truth that the more information involving substitutions there is
to be encoded, the clearer become the advantages of the use of the
<gi tei="yes">app</gi> method over the other two methods.  As a rule, it is
recommended that the <gi tei="yes">app</gi> method be used for encoding
substitutions of any complexity.  It is also desirable that the one
method be used throughout any one transcription.  Accordingly, the
<gi tei="yes">app</gi> method is recommended for text critical transcription of
primary textual materials requiring encoding of instances of other than
straightforward substitution.</p></div3><div3 id="PHCD" name="subsection" ref="Y"><head>Cancellation of Deletions and Other Markings</head><p>An author or scribe may mark a word or phrase in some way, and then
on reflection decide to cancel the marking.  For example, text may be
marked for deletion and the deletion then cancelled, thus restoring the
deleted text.  Such cancellation may be indicated by the
<gi tei="yes">restore</gi> element:
 
<tagList style="one-line"><tagDesc tagDoc="RESTORE" atts="type desc resp cert hand "/></tagList></p><p>Presume that Lawrence decided to restore <cited>my</cited> to the
phrase of <title>Eloi, Eloi, lama sabachthani</title> first written
<q>For I hate this my body</q>, with the <cited>my</cited> first deleted
then restored by writing <q>stet</q> in the margin.  This may be
encoded:
 
<eg><![CDATA[For I hate this
<restore hand='DHL' desc='marginal "stet"'><del>my</del></restore>
body]]></eg></p><p>The <gi tei="yes">restore</gi> element is defined as follows:
 
<dtdFrag id="DPHCD" n="Cancelled Deletions"><tagDecl tagDoc="RESTORE"/></dtdFrag>
 <!-- Q. What do we do when someone wants to transcribe the    --><!-- word 'stet' as being a word written by Lawrence?  A.     --><!-- (msm).  Tell them to tag the deletion and restoration    --><!-- as shown (which does not, ex hypothesi, involve any      --><!-- mechanically recoverable indication that Lawrence wrote  --><!-- 'stet'.  Then add <note place=margin type='authorial     --><!-- instruction' resp=dhl>stet</note>.                       --></p></div3><div3 id="PHOM" name="subsection" ref="Y"><head>Text Omitted from or Supplied in the Transcription</head><p>Where text is not transcribed, whether because of damage to the
original, or because it is illegible, or because of editorial policy,
the <gi tei="yes">gap</gi> core element should be used to register the omission;
where text not present in the source is supplied (whether
conjecturally or from other witnesses) to fill an apparent gap in the
text, it should be marked using the <gi tei="yes">supplied</gi> element provided
by the tag set defined in this chapter.
 
<tagList style="one-line"><tagDesc tagDoc="GAP" atts="desc reason extent resp hand agent"/><tagDesc tagDoc="SUPPLIED" atts="reason resp hand agent source"/></tagList></p><p>By its nature, the <gi tei="yes">gap</gi> element must have no content.  It
should be used wherever an authorial or scribal erasure is so
successful, or the text is so illegible, that nothing can be read.  In
the Beerbohm manuscript of <title>The Golden Drugget</title> cited
above, for example, the author has erased several passages by inking
them over completely:
 
<eg><![CDATA[Others <gap reason='cancelled' hand='MB' extent='10cm'>--and
here is one of them...]]></eg></p><p>In an autograph letter of Sydney Smith in the Pierpont Morgan library
(Klinkenborg 11), three words in the signature are quite illegible:
 
<eg><![CDATA[I am dr Sr yr <gap reason='illegible'
                   hand='SS'
                   extent='3 words'>Sydney Smith]]></eg>
 
It is possible, but not always necessary, to provide measurements
precise to the millimeter or even to the printer's point.  The degree of
precision attempted will vary with the purpose of the encoding and the
nature of the material.</p><p>In cases where there is damage, or a degree of illegibility, but the
text is nevertheless legible and is transcribed, the <gi tei="yes">gap</gi>
element should not be used.  Instead, the passage should be marked using
one or more of the elements <gi tei="yes">damage</gi> and <gi tei="yes">unclear</gi>, which
are described in section <xref target="PHDA"/>.</p><p>If the source text is completely illegible or missing, and new text
is supplied to fill the gap, it should be marked as <gi tei="yes">supplied</gi>.
If another (imaginary) copy of the letter above preserved the signature
as reading <q>I am dear Sir your very humble Servt Sydney Smith</q>, the
text illegible in the autograph might be supplied in the transcription:
 
<eg><![CDATA[I am dr Sr yr
<supplied reason='illegible'
          resp='RW'
          source='amanuensis copy'>very humble Servt</>
Sydney Smith]]></eg>
 
Both <gi tei="yes">gap</gi> and <gi tei="yes">supplied</gi> may be used in combination with
<gi tei="yes">unclear</gi>, <gi tei="yes">damage</gi>, and other elements; for
discussion, see section <xref target="PHCOMB"/>.</p><p>As noted, <gi tei="yes">gap</gi> is defined in the core tag set.  The
<gi tei="yes">supplied</gi> element is declared thus:
 
<dtdFrag id="DPHOM" n="Supplied Text"><tagDecl tagDoc="SUPPLIED"/></dtdFrag></p></div3></div2><div2 id="PHPH" name="Ilocano" ref="Y"><head>Non-Linguistic Phenomena in the Source</head><p>This section describes methods for recording a number of
non-linguistic characteristics of the source text which are often of
particular interest in the transcription of primary sources:  points at
which one scribe takes over from another, or at which ink, pen, or other
characteristics of the writing change; points at which the source is
damaged or imperfectly legible; and unusual spaces or lines in the
source.  A discussion of the usage of the <att tei="yes">hand</att>,
<att tei="yes">resp</att>, and <att tei="yes">cert</att> attributes is also included.
Methods for recording page breaks, column breaks, and line breaks in the
source are described in section <xref target="COXR"/>.</p><div3 id="PHDH" name="subsection" ref="Y"><head>Document Hands</head><p>For many text-critical purposes it is important to signal the person
responsible (the <q>hand</q>) for the writing of a whole document, a
stretch of text within a document, or a particular feature within the
document.  The hand may be of a known and named scribe or author, as
<q>DHL</q>, or may be described by an anonymous formula, as <q>hand
one</q>.  Where the hand is associated with a particular feature tagged
within a document, this may be indicated by the value of the
<att tei="yes">hand</att> attribute on that feature.  The examples given above of
the use of the <att tei="yes">hand</att> attribute with coding of additions and
deletions illustrate this.</p><p>In other cases, it may be necessary to identify a document hand
without there being any association of that hand with any specific
tagged document feature.  The <gi tei="yes">handList</gi> and <gi tei="yes">hand</gi>
elements are used in the TEI header (in the <gi tei="yes">profileDesc</gi>
element) to define each unique hand or scribe distinguished by the
encoder in the document.  One such element must appear within the header
for each hand distinguished in the text.  Each location where a change
of hands occurs may then be marked in the text by the empty
<gi tei="yes">handShift</gi> element.
 
<tagList style="one-line"><tagDesc tagDoc="HAND" atts="id scribe style lang ink character first resp"/><tagDesc tagDoc="HANDLIST"/><tagDesc tagDoc="HANDSHFT" atts="new old style ink character resp"/></tagList></p><p>The attributes <att tei="yes">old</att> and <att tei="yes">new</att> on the
<gi tei="yes">handShift</gi> element refer to the order of the text in the
transcription:  <q>old</q> is the material before the
<gi tei="yes">handShift</gi>, <q>new</q> the material following.  This will
ordinarily, but not necessarily, be the order in which the material was
originally written.  Neither attribute is required but both are
recommended where there is a new hand, as opposed to a new writing style
in the one hand.  The <att tei="yes">character</att> attribute will be most often
used to encode descriptive shifts which the transcriber perceives within
a manuscript and which may or may not be associated with or denote
changes in scribe or content.  The particular values encoded will depend
upon the needs of the transcriber.  Where many values are to be encoded,
feature structures provide an alternative means of encoding these.</p><p>A single hand may employ different writing styles and inks within a
document, or may change character.  For example, the writing style might
shift from <q>anglicana</q> to <q>secretary</q>, or the ink from blue to
brown, or the character of the hand may change.  Any such changes should
be indicated by assigning a new value to the appropriate attribute
within the <gi tei="yes">handShift</gi> element.  The one hand may employ
different renditions within the one writing style, for example medieval
scribes indicating a structural division by emboldening all the words
within a line.  These should be indicated by use of the <att tei="yes">rend</att>
attribute on an element, in the same manner as underlining, emboldening,
font shifts, etc., in transcription of a printed text, rather than by
introducing a new <gi tei="yes">handShift</gi> element.</p><p>In this example<note source="auth" place="foot" anchored="Y">From the Wiltshire Record Office,
Dean of Sarum Churchwardens' presentments, 1731, Hurst; the
transcription was provided by Donald A. Spaeth.</note> first the
document hands are declared in the header:
 
<eg><![CDATA[<!--
<teiHeader>
 ... 
<profileDesc>
    ... -->
   <handList>
      <hand id=H1 style='copperplate'
                  ink='brown'
                  character='regular'
                  first='yes'
                  resp='das'>
      <hand id=H2 style='print'
                  ink='brown'
                  character='unschooled'
                  resp='das'>
   </handList>
   <!-- 
</profileDesc>
</teiHeader> ... -->]]></eg>
 <!-- teiheader def will need to be modified PR   --></p><p>Then the change of hand is indicated in the text:
 
<eg><![CDATA[<!-- ... -->
and that good Order Decency and regular worship
may be once more introduced and Established in this
Parish according to the Rules and Ceremonies of the
Church of England and as under a good Consciencious
and sober Curate there would and ought to be
<handShift new='h2' old='h1' resp='das'>
and for that purpose the parishioners pray]]></eg></p><p>In this example<note source="auth" place="foot" anchored="Y">From folio 52 recto of the Holkham
manuscript of Chaucer's <title>Canterbury Tales</title>.</note> there is
a change of ink within the one hand.  This is indicated by a new value
for the <att tei="yes">ink</att> attribute on the <gi tei="yes">handShift</gi> element:
 
<eg><![CDATA[<l>When wolde the cat dwelle in his ynne</l>
<handShift ink=black>
<l>And if the cattes skynne be slyk and gaye</l>]]></eg></p><p>These elements are declared as follows:
 
<dtdFrag id="DPHHD" n="Hand Shifts"><tagDecl tagDoc="HAND"/><tagDecl tagDoc="HANDSHFT"/><tagDecl tagDoc="HANDLIST"/></dtdFrag></p></div3><div3 id="PHHR" name="subsection" ref="Y"><head>Hand, Responsibility, and Certainty Attributes</head><p>The <att tei="yes">hand</att> and <att tei="yes">resp</att> attributes have similar, but
not identical, meanings.  Observe their distinctive uses in the
following encoding of the William James passage mentioned above in
section <xref target="PHCC"/>.  In this example, the <cited>But</cited>
inserted by James is tagged as an <gi tei="yes">add</gi>, and the consequent
editorial correction of <cited>One</cited> to <cited>one</cited> treated
separately:
 
<eg><![CDATA[<add place='supralinear' resp=FB hand=WJ>But</add>
<corr sic='One' resp=FB>one</> must have lived ...]]></eg>
 
As in this example, <att tei="yes">hand</att> should be reserved for indicating
the hand of any form of marking---here, addition but also deletion,
correction, annotation, underlining, etc.---within the primary text
being transcribed.  The scribal or authorial responsibility for this
marking may be inferred from the value of the <att tei="yes">hand</att> attribute.
The value of the <att tei="yes">hand</att> attribute should be one of the hand
identifiers declared in the document header (see section <xref target="PHDH"/>).</p><p>As in this example, the <att tei="yes">resp</att> on a particular element
should be used only to indicate the particular aspect of responsibility
defined in these <title>Guidelines</title> as appropriate to the
<att tei="yes">resp</att> attribute for that element.  In the case of the
<gi tei="yes">add</gi> element, the <att tei="yes">resp</att> attribute is defined as
signifying the responsibility for identifying the hand of the
addition:  here, Bowers' identification of the hand as that of William
James.  In the case of the <gi tei="yes">corr</gi> element, the <att tei="yes">resp</att>
attribute is defined as signifying the responsibility for supplying the
intellectual content of the correction reported in the transcription:
here, Bowers' correction of <q>One</q> to <q>one</q>.</p><p>As these examples show, the field of application of the
<att tei="yes">resp</att> attributes varies from element to element.  In some
cases, it applies to the content of the element (<gi tei="yes">corr</gi> and
<gi tei="yes">expan</gi>); in others it applies to the value of a particular
attribute (<gi tei="yes">sic</gi>, <gi tei="yes">abbr</gi>, <gi tei="yes">del</gi>, etc.).  In all
cases where both the <att tei="yes">cert</att> and <att tei="yes">resp</att> attributes are
defined for a particular element, the two attributes refer to the same
aspect of the markup.  The one indicates who is intellectually
responsible for some item of information, the other indicates the degree
of confidence in the information.  Thus, for a
correction, the <att tei="yes">resp</att> attribute signifies the person
responsible for supplying the correction, while the <att tei="yes">cert</att>
attribute signifies the degree of editorial confidence felt in that
correction.  For the expansion of an abbreviation, the
<att tei="yes">resp</att> attribute signifies the person responsible for supplying
the expansion and the <att tei="yes">cert</att> attribute signifies the degree of
editorial confidence felt in the expansion.</p><p>This close definition of the use of the <att tei="yes">resp</att> and
<att tei="yes">cert</att> attributes with each element is intended to provide for
the most frequent circumstances in which encoders might wish to make
unambiguous statements regarding the responsibility for and certainty of
aspects of their encoding.  The <att tei="yes">resp</att> and <att tei="yes">cert</att>
attributes, as so defined, give a convenient mechanism for this.
However, there will be cases where it is desired to state responsibility
for and certainty concerning other aspects of the encoding.  For
example, one may wish in the case of an apparent addition to state the
responsibility for the use of the <gi tei="yes">add</gi> element, rather than the
responsibility for identifying the hand of the addition.  It may also be
that one editor may make an electronic transcription of another editor's
printed transcription of a manuscript text --- here, one will wish to
assign layers of responsibility, so as to allow the reader to determine
exactly what in the final machine-readable transcription was the
responsibility of each editor.  In these complex cases of divided
editorial responsibility for and certainty concerning the content,
attributes and application of a particular element, the more general
mechanisms for representing certainty and responsibility described in
chapter <xref target="CE"/> should be used.</p><p>The fields of reference of the <att tei="yes">resp</att> and <att tei="yes">cert</att>
attributes for each element have been chosen to enable what are felt as
the most frequent likely statements an encoder may wish to make
concerning the areas of responsibility and certainty related to that
element.  It is open to each local transcription scheme to vary the use
of the <att tei="yes">resp</att> and <att tei="yes">cert</att> attributes on particular
elements where it is felt convenient.  This practice should be
documented in the <gi tei="yes">encodingDesc</gi> element in the file header.
Further, it is recommended that before interchange any such local usage
of these attributes be converted to conformancy with the definitions of
the <att tei="yes">resp</att> and <att tei="yes">cert</att> attributes given in these
<title>Guidelines</title>.  Use of the <att tei="yes">resp</att> and
<att tei="yes">cert</att> in interchange documents in ways not here defined may
lead to unpredictable results.</p><p>It should be noted that the certainty and responsibility mechanisms
described in chapter <xref target="CE"/> replicate all the functions of the
<att tei="yes">resp</att> and <att tei="yes">cert</att> attributes on particular elements.
For example, the encoding of Donaldson's conjectured emendation of
<cited>wight</cited> to <cited>wright</cited> in line 117 of Chaucer's
<title>Wife of Bath's Prologue</title>, (see <xref target="PHCC"/>) may be
encoded as follows using the <att tei="yes">resp</att> and <att tei="yes">cert</att>
attributes on the <gi tei="yes">corr</gi> element:
 
<eg><![CDATA[<corr sic="wight" resp=ETD cert=70>wright</>]]></eg>
 
Exactly the same information could be conveyed using the certainty
and responsibility mechanisms, as follows:
 
<eg><![CDATA[<corr sic="wight" id=C117>wright</>
 
<!-- ... certainty and responsibility elements may be elsewhere -->
<certainty target=C117 locus='#gicontent' degree=70>
<respons   target=C117 locus='#gicontent' resp=ETD>]]></eg>
 
The choice of which mechanism to use is left to the encoder.  In
transcriptions where only such statements of responsibility and
certainty are made as can be accommodated within the <att tei="yes">resp</att> and
<att tei="yes">cert</att> attributes of particular elements, it will be economical
to use the <att tei="yes">resp</att> and <att tei="yes">cert</att> attributes of those
elements.  Where many statements of responsibility and certainty are
made which cannot be so accommodated, it may be economical to use the
<gi tei="yes">respons</gi> and <gi tei="yes">certainty</gi> elements throughout.</p><p>The above discussion supposes that in each case an encoder is able to
specify exactly what it is that one wishes to state responsibility for
and certainty about.  Situations may arise when an encoder wishes to
make a statement concerning certainty or responsibility but is unable or
unwilling to specify so precisely the domain of the certainty or
responsibility.  In these cases, the <gi tei="yes">note</gi> element may be used
with the <att tei="yes">type</att> attribute set to <q>cert</q> or <q>resp</q>
and the content of the note giving a prose description of the state of
affairs.</p></div3><div3 id="PHDA" name="subsection" ref="Y"><head>Damage, Illegibility, and Supplied Text</head><p>The <gi tei="yes">gap</gi> and <gi tei="yes">supplied</gi> elements described above
(section <xref target="PHOM"/>) should be used with appropriate attributes
where the degree of damage or illegibility in a text is such that
nothing can be read and the text must be either omitted or supplied
either conjecturally or from other sources.  In many cases, however,
despite damage or illegibility, the text may yet be read with reasonable
confidence.  In these cases, the following elements should be used:
 
<tagList style="one-line"><tagDesc tagDoc="DAMAGE" atts="type resp hand agent degree extent"/><tagDesc tagDoc="UNCLEAR" atts="reason resp cert hand agent"/></tagList></p><p>The following examples refer to the recto of folio 5 of the unique
manuscript of the Elder Edda.<note source="auth" place="foot" anchored="Y">Codex Regius, ed.  L. F.
A. Wimmer and F. J&oacute;nsson (Copenhagen 1891).</note> Here, the
manuscript of <title>V&amp;ohook;lusp&aacute;</title> has been damaged
through irregular rubbing so that letters in various places are obscured
and in some cases cannot be read at all.  The existence of the damage
may be registered in general for this leaf by use of the <gi tei="yes">damage</gi>
element.
 
<eg><![CDATA[<damage agent='rubbing at edges' extent='whole leaf'> ... </>]]></eg>
 
However, in fact the damage crosses structural divisions, so the
<gi tei="yes">damage</gi> element does not nest properly within the containing
<gi tei="yes">div</gi> elements.  The simplest method to solve this problem is to
split the element into two fragments, one within each structural
division:
 
<eg><![CDATA[<div>
  <!-- beginning of division ... -->
  <!-- page break, beginning of damage -->
  <pb n='5r'>
  <damage agent='rubbing at edges' extent='whole leaf'>
  <!-- text continues -->
  </damage>
</div>
<div>
  <damage agent='rubbing at edges, continued' extent='whole leaf'>
  <!-- beginning of new text division ... -->
  <!-- page break, end of this damaged section -->
  </damage>
  <pb n='5v'>
  <!-- text continues ... -->
</div>]]></eg>
 
For other techniques of handling non-nesting information, see chapter<xref target="NH"/>
.</p><p>In the first line of this leaf, the transcriber may believe that the
last three letters of <cited>daga</cited> can be read clearly despite
the damage:
 
<eg><![CDATA[um aldr d<damage>aga</> yndisniota]]></eg></p><p>Alternatively, the letters in question may be only imperfectly
legible on account of the damage; this state of affairs may be indicated
by nesting an <gi tei="yes">unclear</gi> element within the <gi tei="yes">damage</gi>
element.
 
<eg><![CDATA[um aldr d<damage><unclear>aga</></> yndisniota]]></eg></p><p>Alternatively, the transcriber may not feel able to read the last
three letters of <cited>daga</cited> but may wish to supply them by
conjecture.  Note the use of the <att tei="yes">source</att> attribute to assign
the conjecture to Finnur J&oacute;nsson:
 
<eg><![CDATA[um aldr d<supplied reason='rubbing'
                   source=FJ>aga</supplied>
yndisniota]]></eg>
 
The <gi tei="yes">supplied</gi> element may if desired be enclosed within a
<gi tei="yes">damage</gi> element:
 
<eg><![CDATA[um aldr d<damage agent='rubbing'>
<supplied source=FJ>aga</supplied></damage>
yndisniota]]></eg></p><p>Contrast the use of <gi tei="yes">gap</gi> in the next line, where the
transcriber believes that four letters cannot be read at all because
of the damage:
 
<eg><![CDATA[&Thorn;ar k&hook-o;mr inn dimmi dreki fliugandi
na&thorn;r frann ne&thorn;an
<gap reason='rubbing' extent='4'>]]></eg>
 
As with <gi tei="yes">supplied</gi>, this <gi tei="yes">gap</gi> might be enclosed by a
<gi tei="yes">damage</gi> element.</p><p>In these examples, various phenomena of illegibility and conjecture
all result from the one cause, an area of damage to the text --- rubbing
at various points --- which is not continuous in the text, affecting it
at irregular points.  In these cases, the <gi tei="yes">join</gi> element may be
used to indicate which tagged features are part of the same physical
phenomenon.  (See chapter <xref target="SA"/> for more details.)</p><p>The above examples record imperfect legibility due to damage.  When
imperfect legibility is due to some other reason (typically because the
handwriting is ill-formed), the <gi tei="yes">unclear</gi> element should be used
without any enclosing <gi tei="yes">damage</gi> element.  In Robert Southey's
autograph of <title>The Life of Cowper</title>,<note source="auth" place="foot" anchored="Y">In
Pierpont Morgan MA 412, (Klinkenborg 15).</note> the final six letters
of <cited>attention</cited> are difficult to read because of the haste
of the writing, though reasonably certain from the context.
 
<eg><![CDATA[and from time to time invited in like manner his
att<unclear>ention</unclear>]]></eg>
 
The <att tei="yes">cert</att> attribute on the <gi tei="yes">unclear</gi> element may be
used to indicate the level of editorial confidence in the reading
contained within it.</p><p>The <gi tei="yes">damage</gi> element is defined formally as follows:
 
<dtdFrag id="DPHDA" n="Damage and Illegiblity"><tagDecl tagDoc="DAMAGE"/></dtdFrag>
 
The <gi tei="yes">unclear</gi> element is defined in section <xref target="COED"/>.</p></div3><div3 id="PHCOMB" name="subsection" ref="Y"><head>The Use of the Gap, Del, Damage, Unclear and Supplied Tags in Combination</head><p>The <gi tei="yes">gap</gi>, <gi tei="yes">damage</gi>, <gi tei="yes">unclear</gi>,
<gi tei="yes">supplied</gi> and <gi tei="yes">del</gi> elements may be closely allied in
their use.  For example, an area of damage in a primary source might
be encoded with any one of the first four of these elements, depending on
how far the damage has affected the readability of the text.
Further, certain of the elements may nest within one another. The
examples given in the last sections illustrate something of how these
elements are to be distinguished in use.  This may be formulated as
follows:
 
<list type="bullets"><item>where the text has been rendered completely illegible by
deletion or damage and no text is supplied by the editor in place of
what is lost: place an empty <gi tei="yes">gap</gi> element at the point of
deletion or damage.  Use the <att tei="yes">reason</att> attribute to state the
cause (damage, deletion, etc.) of the loss of text.</item><item>where the text has been rendered completely illegible by
deletion or damage and text is supplied by the editor in place of
what is lost: surround the text supplied at the point of deletion or
damage with the <gi tei="yes">supplied</gi> element.  Use the <att tei="yes">reason</att>
attribute to state the cause (damage, deletion, etc.) of the loss of
text leading to the need to supply the text.</item><item>where the text has been rendered partly illegible by deletion
or damage so that the text can be read but without perfect
confidence: transcribe the text and surround it with the
<gi tei="yes">unclear</gi> element.  Use the <att tei="yes">reason</att> attribute to state
the cause (damage, deletion, etc.) of the uncertainty in transcription
and the <att tei="yes">cert</att> attribute to indicate the confidence in the
transcription.</item><item>where there is deletion or damage but the text can be read with
perfect confidence: transcribe the text and surround it with the
<gi tei="yes">del</gi> element (for deletion) or the <gi tei="yes">damage</gi> element (for
damage).  Use appropriate attribute values to indicate the cause and
type of deletion or damage.  Observe that the <att tei="yes">degree</att>
attribute on the <gi tei="yes">damage</gi> element permits the encoding to show
that a letter, word or phrase is not perfectly preserved, though it
may be read with confidence.</item><item>where there is an area of deletion or damage and parts of the
text within that area can be read with perfect confidence, other
parts with less confidence, other parts not at all: in transcription,
surround the whole area  with the <gi tei="yes">del</gi> element (for deletion; or
the <gi tei="yes">delSpan</gi> element where it crosses a structural boundary); or
the <gi tei="yes">damage</gi> element (for damage).  Text within the damaged area
which can be read with perfect confidence needs no further tagging.
Text within the damaged area which can not be read with perfect
confidence may be surrounded with the <gi tei="yes">unclear</gi> element.  Places
within the damaged area where the text has been rendered completedly
illegible and no text is supplied by the editor may be marked with
the <gi tei="yes">gap</gi> element. For each element, one may use appropriate
attribute values to indicate the cause and type of deletion or damage
and the certainty of the reading.</item></list></p><p>The rules for combinations of the <gi tei="yes">add</gi> and <gi tei="yes">del</gi>
elements, and for the interpretation of such combinations, are
similar:
 
<list type="bullets"><item>when one addition (<tag compl="full" tei="yes">add id=A1</tag>) includes another
(<tag compl="full" tei="yes">add id=A2</tag>), it indicates that an addition (a1) was first
made to the text, and later a second addition (a2) was made to the text
already added:
 
<eg><![CDATA[This is the text
<add id=A1>with some added
   <add id=A2>(interlinear!)</add>
material</add>
as written.]]></eg></item><item>when one deletion (<tag compl="full" tei="yes">del id=D1</tag>) nests within another
(<tag compl="full" tei="yes">del id=D2</tag>), it indicates that the author wrote a passage,
deleted part of it (d1), and then later deleted the entire passage (d2).
 
<eg><![CDATA[<del id=D2>This sentence contains
some <del id=D1>redundant</del> unnecessary
verbiage.</del>]]></eg></item><item>when an addition nests within a deletion, the normal
interpretation will be that an addition was made within a passage later
deleted in its entirety.</item><item>when a deletion nests within an addition, it indicates that a
deletion was made within a passage earlier added.</item></list></p></div3><div3 id="PHSP" name="subsection" ref="Y"><head>Space</head><p>The presence of significant space in the text being transcribed may
be indicated by the <gi tei="yes">space</gi> element.  The author or scribe may
have left space for a word, or for an initial capital, and for some
reason the word or capital was never supplied and the space left empty.
This element should not be used to mark normal inter-word space or the
like.
 
<tagList style="one-line"><tagDesc tagDoc="SPACE" atts="dim extent resp"/></tagList></p><p>In line 694 of Chaucer's <title>Wife of Bath's Prologue</title> in
the Holkham manuscript the scribe has left a space for a word where
other manuscripts read <cited>preestes</cited>:
 
<eg><![CDATA[By god if wommen had writen storyes
As <space extent='7'> han within her oratoryes]]></eg>
 
The <gi tei="yes">supplied</gi> element discussed in the previous section may be
used to supply the text presumed missing:
 
<eg><![CDATA[By god if wommen had writen storyes
As <supplied reason='space' resp='ES' source='Hg'>
preestes</supplied> han within her oratoryes]]></eg>
 
Here, the fact of the space within the manuscript is indicated by the
value of the <att tei="yes">reason</att> attribute.  The source of the supplied
text is shown by the value of the <att tei="yes">source</att> attribute as the
Hengwrt manuscript; the transcriber responsible for supplying the text
is ES.
 
The <gi tei="yes">space</gi> element is formally defined thus:
 
<dtdFrag id="DPHSP" n="Spaces in the source"><tagDecl tagDoc="SPACE"/></dtdFrag>
 <!-- <div3 id=PHORN><head>Ornaments</head>                    -->
 <!-- <p>Printers' ornaments in the source may be encoded      --><!-- using the <gi>ornament</gi> element:                     -->
 <!-- <tagList>                                                --><!-- <tagDesc tagDoc=ORNAMENT atts="desc">                    --><!-- </tagList>                                               -->
 <!-- <p>On the title page of Randle Cotgrave's                --><!-- <title>Dictionarie of the French and English             --><!-- Tongues</title> (London, 1611; rpt. Colubmia:            --><!-- University of South Carolina Press, 1950), there         --><!-- appears (among many other things) an elaborate fleur     --><!-- de lys between the title and the imprint, which          --><!-- contains the inscription <q>IN DOMINO CONFIDO</q>.       --><!-- This might be transcribed thus:                          -->
 <!-- <eg>                                                     --><!-- <![ CDATA [                                              --><!-- <titlePage>                                              --><!-- <docTitle>                                               --><!-- <titlePart>A Dictionarie</>                              --><!-- <titlePart>of the French                                 --><!-- and English Tongves.</>                                  --><!-- </docTitle>                                              --><!-- <docAuthor>                                              --><!-- compiled by <name rend=sc>Randle                         --><!-- Cotgrave.</name>                                         --><!-- </docAuthor>                                             --><!-- <ornament desc='fleur de lys'>                           --><!-- <s rend=sc>in domino confido</s>                         --><!-- </ornament>                                              --><!-- <docImprint>                                             --><!-- <pubPlace>London</pubPlace>                              --><!-- <publisher>Printed by Adam I&s;lip</publisher>           --><!-- <docDate>Anno 1611.</docDate>                            --><!-- </docImprint>                                            --><!-- </titlePage>                                             --><!-- ]]>                                                      --><!-- </eg>                                                    -->
 <!-- <figure rend=float desc='title page of Cotgrave'>        --><!-- <figDesc>The title page of Randle Cotgrave's             --><!-- <title>Dictionarie of the French and English             --><!-- Tongues</title> (London, 1611).  </figure>               -->
 
 <!-- The <gi>ornament</gi> element is formally defined        --><!-- thus:                                                    -->
 <!-- <dtdFrag id=DPHORN n='Ornaments in the source'>          --><!-- <tagDecl tagDoc=ORNAMENT>                                --><!-- </dtdFrag>                                               --></p></div3><div3 id="PHLN" name="subsection" ref="Y"><head>Lines</head><p>The most common form of marking of text in manuscripts is by lines
written under, beside or through the text.  The lines themselves may be
of various types:  they may be solid, dashed, or dotted, doubled or
tripled, wavy or straight, or a combination of these and other
renderings.  The line may be used for emphasis, or to mark a foreign or
technical term, or to signal a quotation or a title, etc.:  the elements
<gi tei="yes">emph</gi>, <gi tei="yes">foreign</gi>, <gi tei="yes">term</gi>, <gi tei="yes">mentioned</gi>,
<gi tei="yes">title</gi> may be used for these.  Frequently, a scholar may judge
that a line is used to delete text:  the <gi tei="yes">del</gi> element is
available to indicate this.  In all these cases, the <att tei="yes">rend</att>
attribute may be used on these or other elements to indicate that the
text is marked by a line and the style of the line.  Thus, Lawrence's
deletion by strike-through of <cited>my</cited> in the autograph of
<title>Eloi, Eloi, lama sabachthani</title> is noted:
 
<eg><![CDATA[For I hate this
<del hand='DHL' rend='strikethrough'>my</del> body,
which is so dear to me]]></eg></p><p>There will be instances, however, where a scholar wishes only to
register the occurrence of lines in the text, without making any
judgement as to what the lines signify.  In these the <gi tei="yes">hi</gi>
element may be used, with the <att tei="yes">rend</att> attribute to mark the
style of line.  In the manuscript of a letter by Robert Browning to
George Moulton-Barrett (Pierpont Morgan MA 310, Klinkenborg 23), the
underlining of the phrase <q>had obtained all the letters to Mr Boyd</q>
may be marked:
 
<eg><![CDATA[I have once,--by declaring I would prosecute
by law--, hindered a man's proceedings who
<hi rend=underline>had obtained all the letters
to Mr Boyd</hi>]]></eg></p><p>The above examples presume the common case where a single word or
phrase is marked by a line, with no doubt as to where the marking begins
or ends and with no overlapping of the area of text with other marked
areas of text.  Where there is doubt, the <gi tei="yes">certainty</gi> element may
be used to record the doubt.  In the Browning example cited above the
underlining actually begins half-way under <cited>who</cited>, and this
uncertainty could be remarked as follows:
 
<eg><![CDATA[I have once,--by declaring I would prosecute
by law--, hindered a man's proceedings who
<hi id=CSTART1 rend=underline>had obtained all
the letters to Mr Boyd</hi>
 
<!-- ... -->
<certainty target=CSTART1
           locus='#startloc'
           desc='may begin with previous word'
           degree='0.70'>]]></eg></p><p>Where the area of text marked overlaps other areas of text, for
example crossing a structural division, one of the span mechanisms
outlined in these Guidelines may be used.  Where the line is thought to
mark a deletion, the <gi tei="yes">delSpan</gi> element may be used.  Where it is
desired simply to record the marking of a span of text in circumstances
where it is not possible to surround the text with a <gi tei="yes">hi</gi>
element, the <gi tei="yes">span</gi> element may be used with the <att tei="yes">rend</att>
attribute indicating the style of line-marking.</p><p>More work needs to be done on clarifying the treatment of other
textual features marked by lines which might so overlap or nest.  For
example, in many Middle English manuscripts (e.g. the Jesus and Digby
verse collections) marginal sidebars may indicate metrical structure:
couplets may be linked in pairs, with the pairs themselves linked
into stanzas. Or, marginal sidebars may indicate emphasis, or may
point out a region of text on which there is some annotation: in many
manuscripts of Chaucer's <title>Wife of Bath's Prologue</title> lines
655-8 are marked with nesting parentheses against which the scribe
has written <cited>nota</cited>.</p><p>At the lowest level, all such features could be captured by use of
the <gi tei="yes">note</gi> element, containing a prose description of the
manuscript at this point.  It is not yet clear how best to mark up such
phenomena so as to
obtain more usefully structured encodings.  For example,
in the Chaucer example just cited, one may wish to record that the
<cited>nota</cited> is written in the Hengwrt manuscript in the right
margin against a single large left parenthesis bracketing the four
lines, with two right parentheses in the right margin bracketing two
overlapping pairs of lines:  the first and third, the second and fourth.
The <gi tei="yes">note</gi> element allows us to record that the scribe wrote
<cited>nota</cited>, but is not well-adapted to show that the
<cited>nota</cited> points both at all four lines and at two pairs of
lines within the four lines.  Work will continue in this area.</p></div3></div2><div2 id="PHSK" name="Ilocano" ref="Y"><head>Headers, Footers, and Similar Matter</head><p>As a rule, matter associated with the page break (signature,
catchword, page number) should be drawn into the <gi tei="yes">pb</gi> element
as attributes:  see section <xref target="CORS"/>.  In text-critical
situations where these elements need tagging in their own right (for
instance, when the catch-word presents a variant reading, or spacing
in the header or footer is significant for compositor identification)
the element <gi tei="yes">fw</gi> may be used:
 
<tagList style="one-line"><tagDesc tagDoc="FW" atts="place"/></tagList>
 
The name <cited>fw</cited> is short for <q>forme work</q>. It
may be used  to encode any of
the unchanging portions of a page forme, such as:
 <!-- often referred to as the <term>skeleton</term>.  Since --><!-- running heads are not always part of the skeleton, and --><!-- catchwords almost never are, the use of the term here --><!-- represents, strictly speaking, an extension of its usual --><!-- denotation.  The <gi>fw</gi> element may be used to encode: -->
 
<list type="bullets"><item>running heads (whether repeated on every page, or changing on
every page)</item><item>running footers</item><item>page numbers</item><item>catch-words</item><item>other material repeated from page to page, which falls outside the
stream of the text</item></list>
 
It should not be used for marginal glosses, annotations, or textual
variants, which should be tagged using <gi tei="yes">gloss</gi>, <gi tei="yes">note</gi>, or
the text-critical tags described in chapter <xref target="TC"/>,
respectively.</p><p>For example:
 
<eg><![CDATA[ <fw place=top-centre type=head>Po&euml;ms.</fw>
 <fw place=top-right type=pageno>29</fw>
 <fw place=bot-centre type=sig>E3</fw>
 <fw place=bot-right type=catch>TEMPLE</fw>]]></eg><!-- Donne, Poems 1633, p. 29 -->
 
 <!-- [Need several examples, all fuller than this one.     --><!-- Take from DOSL materials? -MSM]                          --></p><p>The formal declaration for the <gi tei="yes">fw</gi> element is
this:
 
<dtdFrag id="DTCHD" n="Headers and footers"><tagDecl tagDoc="FW"/></dtdFrag></p></div2><div2 id="PHTRXX" name="Ilocano" ref="Y"><head>Other Primary Source Features not Covered in These Guidelines</head><p>We repeat the advice given at the beginning of this chapter, that
these recommendations are not intended to meet every transcriptional
circumstance ever likely to be faced by any scholar.  They are intended
rather as a base to enable encoding of the most common phenomena found
in the course of scholarly transcription of primary source materials.
These guidelines particularly do not address the encoding of physical
description of textual witnesses:  the materials of the carrier, the
medium of the inscribing implement, the layout of the inscription upon
the material, the organisation of the carrier materials themselves (as
quiring, collation, etc.), authorial instructions or scribal markup,
etc.  Some of these issues may be covered in future editions of these
guidelines.</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ph.odd ??><!-- 18 Physical Character --><?tei:SOF p2tc.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: p2tc.odd,v $
    * Revision 1.13  1998/02/05 17:14:35  tei
    * make examples parse
    *
    * Revision 1.12  98/02/01  17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    * 
    * Revision 1.11  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.10  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.9  1994/04/07  16:33:44  msmcq
    * Typos from WWP reader
    * 
    * Revision 1.8  1994/04/01  16:38:10  msmcq
    * changes / fixes during validation of DTD
    * 
    * Revision 1.7  1994/03/27  16:31:35  lou
    * smefinal check
    * 
    * Revision 1.4  1994/03/08  03:13:48  msmcq
    * revision for P3
    * 
    * Revision 1.3  1994/02/11  23:04:12  msmcq
    * add RCS id, log keywords
    * --><!-- Revisions:                                               --><!-- 7 jan 98 : LB : tag "wit" as attribute --><!-- 4 Jan 98 : LB : change "has to" to "need" per MSM        --><!-- 94-04-07 : MSM : remove line break in a div head         --><!-- 94-03-30 : MSM : make .ent file                          --><!-- 94-03-29 : MSM : add TYPE to cladecl for fragment tags   --><!-- 94-03-29 : MSM : add declaration for class fragment(ary) --><!-- 94-03-07 : MSM : changes from CH                         --><!-- 94-03-03 : MSM : changes from RC                         --><!-- 94-02-11 : MSM : Added RCS id                            --><!-- 94-02-04 : MSM : catch wit/ness renaming slip            --><!-- 94-02-04 : MSM : fix tag slip, idref error               --><!-- 94-02-04 : MSM : complete 2d pass                        --><!-- 94-02-03 : MSM : 2d pass                                 --><!-- 94-01-25 : MSM : mess around with ids, idrefs            --><!-- 94-01-25 : MSM : finish first pass for P3                --><!-- 94-01-25 : MSM : fix tagging error                       --><!-- 94-01-23 : MSM : through line 1130 (end of locref meth)  --><!-- 94-01-22 : MSM : begin revision for P3                   --><!-- 93-06-05 : MSM : remove . from col 1                     --><!-- 93-06-03 : MSM : add editorial note                      --><!-- 27 May: LB fixed tagging --><div1 id="TC" n="19" name="Faisal" ref="Y"><head>Critical Apparatus</head><p>Scholarly editions of texts, especially texts of great antiquity or
importance, often record some or all of the known variations among
different <term>witnesses</term> to the text.  Witnesses to a text may
include authorial or other manuscripts, printed editions of the work,
early translations, or quotations of a work in other texts.
Information concerning variant readings of a text may be accumulated in
highly structured form in a critical apparatus of variants.  This
chapter defines an additional tag set for use in encoding such an
apparatus of variants, which may be used in conjunction with any of the
base tag sets defined in these Guidelines.  It also defines an element
class which provides extra attributes for some elements of the core tag
set when this additional tag set is selected.</p><p>This tag set is selected as described in <xref target="STIN"/>; in a
document which uses the markup described in this chapter, the document
type declaration should contain the following declaration of the entity
<ident tei="yes" type="pe">TEI.textcrit</ident>, or an equivalent one:
 
<eg><![CDATA[<!ENTITY % TEI.textcrit 'INCLUDE'>]]></eg>
 
The entire document type declaration for a document using this
additional tag set together with the base tag set for prose might look
like this:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY TEI.prose     'INCLUDE' >
    <!ENTITY TEI.textcrit  'INCLUDE' >
 ]>]]></eg></p><p>The overall document type declaration for this additional tag set
has the following structure.  First, the file
<ident tei="yes" type="file">teitc2.ent</ident> defines some element classes
relevant to this tag set:
 
<dtdFrag id="DTCE" n="Entity classes for text criticism" file="teitc2.ent"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><claDecl classDoc="FRAGMENT" type="model"/><claDecl classDoc="FRAGMENT" type="atts"/><claDecl classDoc="READINGS" type="atts"/></dtdFrag>
 
The file <ident tei="yes" type="file">teitc2.dtd</ident> defines the elements
themselves:
 
<dtdFrag id="DTC" n="Tags for text criticism" file="teitc2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><dtdRef dtdFrag="DTCAPEN"/><dtdRef dtdFrag="DTCAPLR"/><dtdRef dtdFrag="DTCAPSU"/><dtdRef dtdFrag="DTCAPWD"/><dtdRef dtdFrag="DTCSCWL"/><dtdRef dtdFrag="DTCAPLW"/><dtdRef dtdFrag="DTCFW"/></dtdFrag></p><p>Information about variant readings (whether or not represented by a
critical apparatus in the source text) may be recorded in a series of
<term>apparatus entries</term>, each entry documenting one
<term>variation</term>, or set of readings, in the text.  Tags for the
apparatus entry and readings, and for the documentation of the witnesses
whose readings are included in the apparatus, are described in section<xref target="TCAPLL"/>
.  Special tags for fragmentary witnesses are
described in section <xref target="TCAPMI"/>.  The available methods for
embedding the apparatus in the rest of the text, or for linking an
external apparatus to the base text, are described in section <xref target="TCAPLK"/>.  Finally, several extra attributes for some tags of the
core tag set, made available when the additional tag set for text
criticism is selected, are documented in section <xref target="PHCO"/>.
 <!-- <p>An apparatus is composed of a series of apparatus     --><!-- (<gi>app</gi>) elements.  The tags used within           --><!-- apparatus are presented in three sections.  Tags for     --><!-- the low-level elements contained within each             --><!-- <gi>app</gi> element are discussed in section <xref      --><!-- target=TCAPLL>:  lemma (<gi>lem</gi>); reading           --><!-- (<gi>rdg</gi>), reading group (<gi>rdgGrp</gi>),        --><!-- witness (<gi>wit</gi>) and witness detail                --><!-- (<gi>wit.detail</gi>) tags.  The <gi>app</gi> element    --><!-- itself is discussed in section <xref target=TCAPEN>.     --><!-- Finally, in section <xref target=TCAPLK>, mechanisms     --><!-- are presented for relating each variant within an        --><!-- apparatus to other variants within the apparatus and to  --><!-- the base text on which they express variation.           --></p><p>Many examples given in this chapter refer to the following texts
of the opening (usually just line 1) of Chaucer's <title>Wife of
Bath's Prologue</title>:
 
<list type="gloss"><label>El</label><item>Ellesmere, Huntingdon Library 26.C.9:
<q rend="display">Experience though noon Auctoritee /
Were in this world, were right ynogh to me /
To speke of wo that is in mariage; ...</q></item><label>Hg</label><item>Hengwrt, National Library of Wales, Aberystwyth,
Peniarth 392D:
<q rend="display">Experience thogh noon Auctoritee /
Were in this world, is right ynogh for me /
To speke of wo that is in mariage; ...</q></item><label>La</label><item>British Library Lansdowne 851:
<q rend="display">Experiment thouh none auctorite /
Were in this world, is right ynohe for me /
To speke of wo that is in mariage; ...</q></item><label>Ra2</label><item>Bodleian Library Rawlinson Poetic 149:
<q rend="display">Eryment though none auctorite /
Were in this world, it is right ynow for me /
To speke of wo that is in mariage; ...</q></item></list></p><div2 id="TCAPLL" name="Ilocano" ref="Y"><head>The Apparatus Entry, Readings, and Witnesses</head><p>This section introduces the fundamental markup methods used to encode
textual variations:
 
<list type="bullets"><item>the <gi tei="yes">app</gi> element for entries in the critical apparatus:
see section <xref target="TCAPEN"/>.</item><item>elements for identifying individual readings: see section <xref target="TCAPLR"/>.</item><item>ways of grouping readings together: see section <xref target="TCAPSU"/>.</item><item>methods of identifying which witnesses support a particular
reading, and for describing the witnesses included in the
apparatus: see section <xref target="TCAPLW"/>.</item><item>elements for indicating which portions of a text are covered by
fragmentary witnesses: see section <xref target="TCAPMI"/>.</item></list></p><div3 id="TCAPEN" name="subsection" ref="Y"><head>The Apparatus Entry</head><p>Individual textual variations are encoded using the <gi tei="yes">app</gi>
element, which groups together all the readings constituting the
variation.  The identification of discrete textual variations or
apparatus entries is not a purely mechanical process; different editors
may group readings differently.  No rules are given here as to how to
group readings into apparatus entries; the tags given here may be used
to group readings in whatever way the editor finds most perspicuous or
useful.</p><p>The individual apparatus entry is encoded with the <gi tei="yes">app</gi>
element:
<tagList style="one-line"><tagDesc tagDoc="APP" atts="type from to loc"/></tagList></p><p>The attributes <att tei="yes">loc</att>, <att tei="yes">from</att>, and <att tei="yes">to</att>,
are used to link the apparatus entry to the base text.  Several methods
may be used for such linkage, each involving a slightly different usage
for these attributes.  Linkage between text and apparatus is described
below in section <xref target="TCAPLK"/>.</p><p>Each <gi tei="yes">app</gi> element comprises one or more readings, which in
turn are encoded using the <gi tei="yes">rdg</gi> or other elements, as described
in the next section.  A very simple partial apparatus for the first line
of the <title>Wife of Bath's Prologue</title> might take a form
something like this:
 
<eg><![CDATA[<app>
  <rdg wit='El'>Experience though noon Auctoritee</rdg>
  <rdg wit='La'>Experiment thogh noon Auctoritee</rdg>
  <rdg wit='Ra2'>Eryment though none auctorite</rdg>
</app>]]></eg>
 
Of course, in practice the apparatus will be somewhat more complex.
Specifically, it may be desired to
record more obviously that manuscripts El and La agree on the
words <q>noon Auctoritee</q>, to indicate a preference for one
reading, etc.  The following sections on
readings, subvariation, and witness information describe some of the
more important complications which can arise.</p><p>The structure of an <gi tei="yes">app</gi> element is formally defined as
follows:
 
<dtdFrag id="DTCAPEN" n="Apparatus entry"><tagDecl tagDoc="APP"/></dtdFrag></p></div3><div3 id="TCAPLR" name="subsection" ref="Y"><head>Readings</head><p>Individual readings are the crucial elements in any critical
apparatus of variants.  The following elements should be used to tag
individual readings within an apparatus entry:
 
<tagList style="one-line"><tagDesc tagDoc="LEM"/><tagDesc tagDoc="RDG"/></tagList>
 
N.B. the term <term>lemma</term> is used here in the text-critical
sense of <gloss>the reading accepted as that of the original or of the
base text</gloss> --- it is not to be confused with <gloss>the heading
of an entry in a reference book, especially a dictionary,</gloss> or
<gloss>a subsidiary proposition introduced in the proof of some other
proposition; a helping theorem.</gloss></p><p>In recording readings within an apparatus entry, the <gi tei="yes">rdg</gi>
element may always be used; each <gi tei="yes">app</gi> must contain at least one
<gi tei="yes">rdg</gi>.</p><p>The <gi tei="yes">lem</gi> element may also be used, under some circumstances,
to record the base text of the source edition, to mark the readings of a
base witness, to indicate the preference of an editor or encoder for a
particular reading, or to make clear, in cases of ambiguity, precisely
which portion of the main text the variation applies to.  Those who
prefer to work without the notion of a base text may prefer not to use
it at all.  How it is used depends in part on the method chosen for
linking the apparatus to the text; for more information, see section<xref target="TCAPLK"/>
.</p><p>Readings may be encoded individually, or grouped for perspicuity
using the <gi tei="yes">rdgGrp</gi> element described in section <xref target="TCAPSU"/>.</p><p>As members of the attribute class <ident tei="yes" type="class">readings</ident>,
both of these elements inherit the following attributes.  Some of
these attributes are intelligible only if the reading is ascribed to a
single witness; others have no such restriction.
 
<adList classDoc="READINGS" atts="wit type cause varseq hand resp"/></p><p>The <att tei="yes">wit</att> attribute identifies the witnesses which have the
reading in question.  It is required if the apparatus gathers together
readings from different witnesses, but may be omitted in an apparatus
recording the readings of only one witness, e.g. substitutions,
divergent opinions on what is in the witness or on how to expand
abbreviations, etc.  Even in such a one-witness apparatus, however,
the <att tei="yes">wit</att> attribute may still be useful when it is desired to
record the occurrence of a particular reading in some other witness.
For other methods of identifying the witnesses to a reading, see section<xref target="TCAPLW"/>
.
 <!-- For example of wit in single-witness app, see PHcc.      -->
 <!-- <p>The <att>wit</att> attribute is required in an        --><!-- apparatus gathering readings from different witnesses.   --><!-- It is optional in an apparatus gathering variant         --><!-- readings in the transcription of a single witness.       --><!-- Where the transcription records only variant readings    --><!-- within this witness (as substitutions, different         --><!-- editorial expansions, etc) then the <att>wit</att>       --><!-- attribute is redundant.  However, it may still be        --><!-- useful where it is desired to indicate within the        --><!-- transcription the occurrence of a particular reading in  --><!-- another witness (as in the example in section <xref      --><!-- target=PHCC>).                                           --></p><p>The <att tei="yes">type</att> attribute allows the encoder to classify readings
in any convenient way, for example as substantive variants of the lemma:
 
<eg><![CDATA[<app>
<lem wit='El Hg'>Experience</lem>
<rdg wit='La'  type='substantive'>Experiment</rdg>
<rdg wit='Ra2' type='substantive'>Eryment</rdg>
</app>]]></eg>
 
or as orthographic variants:
 
<eg><![CDATA[<app>
  <lem wit='El Ra2'>though</lem>
  <rdg wit='Hg' type='orthographic'>thogh</rdg>
  <rdg wit='La' type='orthographic'>thouh</rdg>
</app>]]></eg></p><p>The <att tei="yes">varSeq</att> and <att tei="yes">cause</att> attributes may be used to
convey information on the sequence and cause of variation.  In the
following apparatus fragment, the reading <cited>Eryment</cited> is
tagged as sequential to (derived from) the reading
<cited>Experiment</cited>, and the cause
is given as loss of the abbreviation for <cited>per</cited>.
 
<eg><![CDATA[<app>
    <rdg varSeq=1 wit='La'>Experiment</rdg>
    <rdg varSeq=2 cause='abbreviation loss'
                  wit='Ra2'>Eryment</rdg>
</app>]]></eg></p><p>If a manuscript is written in several hands, and it is desired to
report which hand wrote a particular reading, the <att tei="yes">hand</att>
attribute should be used.  For example, in the Munich manuscript
containing the <title>Carmina Burana</title>,
the word <cited>alle</cited> has been changed
to <cited>allen</cited>:
 
<eg><![CDATA[<l>Swaz hi g&a;t umbe
<l>daz sint alle megede,
<l>die wellent &a;n man
<l><app>
     <rdg wit='M' hand='m1'
                  varSeq=1>alle</rdg>
     <rdg wit='M' hand='m2'
                  varSeq=2
                  cause='nachgetragen'>allen</rdg>
   </app>
   disen sumer g&a;n.
 
<!-- entity &a; is used here for &acirc; -->]]></eg>
 <!-- Des Minnesangs Fr&uuml;hling, ed.  Hugo Moser and        --><!-- Helmut Tervooren (Stuttgart:  Hirzel, 1977), I, 20.      --><!-- (Anonymous VI).                                          --></p><p>Similarly, if a witness is hard to decipher, it may be desired to
indicate responsibility for the claim that a particular reading is
supported by a particular witness.  In line 2212a of
<title>Beowulf</title>, for example, the manuscript is read in different
ways by different scholars; the editor Klaeber prints one text, and
records in the apparatus two different accounts of the manuscript
reading, by Zupitza and Chambers:
<note source="auth" place="foot" anchored="Y">For the sake of legibility in the example, long marks
over vowels are omitted.  The non-standard entities <cited>ae</cited>,
<cited>d</cited> and <cited>th</cited> refer to a-e ligature, eth, and
thorn respectively.  </note>
 
<eg><![CDATA[<l>se &eth;e on
<app>
  <rdg wit='Kl'>hea(um) h(&ae;&th;)e</rdg>
  <rdg wit='MS' resp='Z'>hea&d;o hl&ae;we</rdg>
  <rdg wit='MS' resp='Cha'>heaum hope</rdg>
</app></l>
<l>hord beweotode,</l>]]></eg>
 <!-- He also records the fact that Holthausen, editions 1-5,  --><!-- and Sch&uuml;cking follow Zupitza's reading of the ms.   --><!-- So in 'real life' this will require a witDetail          --><!-- element, I think.                                        --></p><p>The <att tei="yes">hand</att> and <att tei="yes">resp</att> attributes are intelligible
only on an element recording a reading from a single witness, and should
not be used if more than one witness is given on the same <gi tei="yes">rdg</gi>
or <gi tei="yes">lem</gi> element.  If more than one witness is given for the
reading, they are undefined.  To convey this information when the
witness is one among several, the <gi tei="yes">witDetail</gi> element should be
used; see section <xref target="TCAPLW"/>.</p><p>Where there is a greater weight of editorial discussion and
interpretation than can conveniently be expressed through the attributes
provided on these tags (e.g. multiple causes for a single reading;
multiple editorial responsibility for an emendation) this information
can be attached to the apparatus in a note, or recorded in the feature
structure notation defined in chapter <xref target="FS"/>.  In particular,
such recurring text-critical situations as palaeographic confusion of
particular letters, or homoeoarchy or homoeoteleuton involving specific
character groups, may lend themselves to feature structure treatment.
Information concerning these recurrent situations may be encoded into
database-like fragments within the text which would then be available to
sophisticated computer-assisted analysis.  Further work remains to be
done on such mechanisms, however, and so no examples are given here of
the use of feature structures in text-critical apparatus.</p><p>The <gi tei="yes">note</gi> element may also be used to record the specific
wording of notes in the apparatus of the source edition, as here in
a transcription of Friedrich Klaeber's note on <title>Beowulf</title>
2207a:
 
<eg><![CDATA[<l n='2207a'>sy&d;&d;an Beowulfe
  <note place='app' resp='Kl'>Fol. 179a <mentioned>beowulfe</mentioned>.
Folio 179, with the last page (Fol. 198b), is the worst
part of the entire MS.  It has been freshened up by a
later hand, but not always correctly.  Information on
doubtful readings is in the notes of Zupitza and Chambers.
</note>
</l>
<l n='2207b'>brade rice</l>
<!-- ... -->]]></eg>
 <!-- Klaeber, app. to 2207.                                   -->
 
Notes providing details of the reading of one particular witness should
be encoded using the specialized <gi tei="yes">witDetail</gi> element described in
section <xref target="TCAPLW"/>.</p><p>Encoders should be aware of the distinct fields of use of the
attribute values <att tei="yes">wit</att>, <att tei="yes">hand</att>, and <att tei="yes">resp</att>.
Broadly, <att tei="yes">wit</att> identifies the physical entity in which the
reading is found (manuscript, clay tablet, papyrus, printed edition);
<att tei="yes">hand</att> refers to the agent responsible for inscribing that
reading in that physical entity (scribe, author, inscriber, hand 1, hand
2); <att tei="yes">resp</att> indicates the scholar responsible for asserting the
existence of that reading in that physical entity.  In some cases, the
categories may blur:  a scholar may produce an edition introducing
readings for which he or she is responsible; that edition may itself
become a witness in a later critical apparatus.  Thus, readings
introduced as corrections in the earlier edition will be seen in the
later apparatus as witnessed by the earlier edition.  As observed in the
discussion concerning the discrimination of <att tei="yes">hand</att> and
<att tei="yes">resp</att> in transcription of primary sources in section <xref target="PHHR"/>, the division of layers of responsibility through various
scholars for particular aspects of a particular reading may require the
more complex mechanisms for assigning responsibility described in
chapter <xref target="CE"/>.</p><p>The formal declaration of the <gi tei="yes">rdg</gi> and <gi tei="yes">lem</gi> elements
is this:
 <!-- should these allow %component ? (msm) -->
<dtdFrag id="DTCAPLR" n="Readings"><tagDecl tagDoc="LEM"/><tagDecl tagDoc="RDG"/></dtdFrag></p></div3><div3 id="TCAPSU" name="subsection" ref="Y"><head>Indicating Subvariation in Apparatus Entries</head><p>The <gi tei="yes">rdgGrp</gi> element may be used to group readings, either
because they have identical values on one or more attributes, or because
they are seen as forming a self-contained variant sequence, or for some
other reason.  This grouping of readings is entirely optional:  no such
grouping of readings is required.
 
<tagList style="one-line"><tagDesc tagDoc="RDGGRP"/></tagList></p><p>The <gi tei="yes">rdgGrp</gi> element is a member of class <ident tei="yes" type="class">readings</ident> and therefore can carry the
<att tei="yes">wit</att>, <att tei="yes">type</att>, <att tei="yes">cause</att>, <att tei="yes">varSeg</att>,
<att tei="yes">hand</att>, and <att tei="yes">resp</att> attributes described in the
preceding section.  When values for any of these attributes are given
on a <gi tei="yes">rdgGrp</gi> element, the values given are inherited by the
<gi tei="yes">rdg</gi> or <gi tei="yes">lem</gi> elements nested within the reading group,
unless overridden by a new specification on the individual reading
element.</p><p>To indicate that both Hg and La vary only orthographically from the
lemma, one might tag both readings <tag compl="full" tei="yes">rdg type='orthographic'</tag>,
as shown in the preceding section.  This fact can be expressed more
perspicuously, however, by grouping their readings into a
<gi tei="yes">rdgGrp</gi>, thus:
 
<eg><![CDATA[<app>
    <lem wit='El Ra2'>though</lem>
    <rdgGrp type=orthographic>
         <rdg wit='Hg'>thogh</rdg>
         <rdg wit='La'>thouhe</rdg>
    </rdgGrp>
</app>]]></eg></p><p>Similarly, <gi tei="yes">rdgGrp</gi> may be used to organize the substantive
variants of an apparatus entry.  Editors may need to indicate that each
of a group of witnesses may be taken as all supporting a particular
reading, even though there may be variation concerning the exact form of
that reading in, or the degree of support offered by, those witnesses.
For example:  one may identify three substantive variants on the first
word of Chaucer's <title>Wife of Bath's Prologue</title> in the
manuscripts:  these might be expressed in regularized spelling as
<q>Experience</q>, <q>Experiment</q>, and <q>Eriment</q>.  In fact, the
manuscripts display many different spellings of these words, and a
scholar may wish both to show that the manuscripts have all these
variant spellings and that these variant spellings actually support only
the three regularized spelling forms.  One may term these variant
spellings as <soCalled>subvariants</soCalled> of the regularized
spelling forms.</p><p>This subvariation can be expressed within an <gi tei="yes">app</gi> element by
gathering the readings into three groups according to the normalized
form of their reading.  All the readings within each group may be
accounted subvariants of the main reading for the group, which may be
signaled by tagging it <tag compl="full" tei="yes">lem</tag> or <tag compl="full" tei="yes">rdg type='group
base'</tag>.</p><p>In this example, the different subvariants on <q>Experience</q>,
<q>Experiment</q>, and <q>Eriment</q> are held within three
<gi tei="yes">rdgGrp</gi> elements nested within the enclosing <gi tei="yes">app</gi>
element:
 
<eg><![CDATA[<app type='substantive'>
    <rdgGrp type='subvariants'>
        <lem wit='El Hg'>Experience</lem>
        <rdg wit='Ha4'>Experiens</rdg>
    </rdgGrp>
    <rdgGrp type='subvariants'>
        <lem wit='Cp Ld1'>Experiment</lem>
        <rdg wit='La'>Ex&p-underbar;iment</rdg>
    </rdgGrp>
    <rdgGrp type='subvariants'>
        <lem wit='[unattested]'>Eriment</lem>
        <rdg wit='Ra2'>Eryment</rdg>
    </rdgGrp>
</app>]]></eg>
 
From this, one may deduce that the regularized reading <q>Experience</q>
is supported by all three manuscripts El Hg Ha4, although the spelling
differs in Ha4, and that the regularized reading <q>Eriment</q> is
supported by Ra2, even though the form differs in that manuscript.
Accordingly, an application which recognizes that these apparatus
entries show subvariation may then assign all the witnesses instanced as
attesting the sub-variants on that lemma as actually supporting the
reading of the lemma itself at a higher level of classification.  Thus,
Ha4 here supports the reading <q>Experience</q> found in El and Hg, even
though it is spelt slightly differently in Ha4.</p><p>Reading groups may nest recursively, so that variants can be
classified to any desired depth.  Because apparatus entries may also
nest, the <gi tei="yes">app</gi> element might also be used to group readings in
the same way.  The example above is substantially identical to the
following, which uses <gi tei="yes">app</gi> instead of <gi tei="yes">rdgGrp</gi>:
 
<eg><![CDATA[<app id=A1 type='substantive' >
    <rdg wit='El Hg Ha4'>
        <app id=A2 type='orthographic'>
             <lem wit='El Hg'>Experience</lem>
             <rdg wit='Ha4'>Experiens</rdg>
        </app>
    </rdg>
    <rdg wit='Cp Ld1 La'>
        <app id=A3 type='orthographic'>
             <lem wit='Cp Ld1'>Experiment</lem>
             <rdg wit='La'>Ex&p-underbar;iment</rdg>
        </app>
    </rdg>
    <rdg wit='Ra2'>
        <app id=A4 type='orthographic'>
             <lem wit='[unattested]'>Eriment</lem>
             <rdg wit='Ra2'>Eryment</rdg>
        </app>
    </rdg>
</app>]]></eg>
 
This expresses even more clearly than the previous encoding of this
material that at the highest level of classification (apparatus entry
A1), this variation has three normalized readings, and that the first of
these is supported by manuscripts El, Hg, and Ha4; the second by Cp,
Ld1, and La; and the third by Ra2.  Some encoders may find the use of
nested apparatus entries less intuitive than the use of reading groups,
however, so both methods of classifying the readings of a variation are
allowed.</p><p>Reading groups may also be used to bring together variants which form
an apparent developmental sequence, and to make clear that other
readings are not part of that sequence, as in the following example,
which makes clear that the variant sequence <q>experiment</q> to
<q>eriment</q> says nothing about the relative priority of
<q>experiment</q> and <q>experience</q>:
 
<eg><![CDATA[<app type='substantive'>
    <rdgGrp type='subvariants'>
        <lem wit='El Hg'>Experience</lem>
        <rdg wit='Ha4'>Experiens</rdg>
    </rdgGrp>
    <rdgGrp type='sequence'>
        <rdgGrp varSeq=1 type='subvariants'>
            <lem wit='Cp Ld1'>Experiment</lem>
            <rdg wit='La'>Ex&p-underbar;iment</rdg>
        </rdgGrp>
        <rdgGrp varSeq=2 cause='loss of abbrev for PER' resp=PR>
            <lem wit='[unattested]'>Eriment</lem>
            <rdg wit='Ra2'>Eryment</rdg>
        </rdgGrp>
    </rdgGrp>
</app>]]></eg></p><p>Reading groups are defined formally as follows:
 
<dtdFrag id="DTCAPSU" n="Reading Groups"><tagDecl tagDoc="RDGGRP"/></dtdFrag></p></div3><div3 id="TCAPLW" name="subsection" ref="Y"><head>Witness Information</head><p>A given reading is associated with the set of witnesses attesting it
by listing the witnesses in the <att tei="yes">wit</att> attribute on the
<gi tei="yes">rdg</gi>, <gi tei="yes">lem</gi>, or <gi tei="yes">rdgGrp</gi> element.  Special
mechanisms, described in the following sections, are needed to associate
annotation on a reading with one specific witness among several (section<xref target="TCAPWD"/>
), to transcribe witness information verbatim from a
source edition (section <xref target="TCSCWL"/>), and to identify the
formal lists of witnesses typically provided in the front matter of
critical editions (section <xref target="TCAPWL"/>).</p><div4 id="TCAPWD" name="Section" ref="Y"><head>Witness Detail Information</head><p>When it is desired to give additional information about a particular
witness or witnesses for the reading, the information may be given in a
<gi tei="yes">witDetail</gi> element, pointing to the identifier for that reading
and signalling in the value of its <att tei="yes">wit</att> attribute the
witnesses or witnesses to which the additional information relates.
 
<tagList style="one-line"><tagDesc tagDoc="WITDTL" atts="target wit"/></tagList></p><p>The <gi tei="yes">witDetail</gi> element is a specialized form of
<gi tei="yes">note</gi>, which adds to the attributes of that element the
specialized attribute <att tei="yes">wit</att>, which indicates which witness in
particular is being described.  Like <gi tei="yes">note</gi>, <gi tei="yes">witDetail</gi>
can be included in the text at the point of attachment, or can point to
the reading(s) being annotated with its <att tei="yes">target</att> attribute.  To
indicate, on the authority of editor PR, that the Ellesmere manuscript
has an ornamental capital in the word <cited>Experience</cited>, for
example, one might write:
 
<eg><![CDATA[<app type='substantive'>
    <rdgGrp type='subvariants'>
        <lem id=W026 wit='El Hg'>Experience</lem>
        <rdg wit='Ha4'>Experiens</rdg>
    </rdgGrp>
    <!-- ... -->
</app>
 
<!-- elsewhere in the text, perhaps in a separate section
     of notes ... -->
<witDetail target=W026 resp=PR wit='El'>Ornamental capital.</witDetail>]]></eg>
 
This encoding makes clear that the ornamental capital mentioned is in
the Ellesmere manuscript, and not in Hengwrt or Ha4.</p><p>Like <gi tei="yes">note</gi>, <gi tei="yes">witDetail</gi> may be used to
record the specific wording of information in the source text, even when
the information itself is captured in some more formal way elsewhere.
The example from the Carmina Burana above (section <xref target="TCAPLR"/>), for example, might be extended thus, to record the
wording of the note explaining the variant:
 
<eg><![CDATA[<l>Swaz hi g&a;t umbe
<l>daz sint alle megede,
<l>die wellent &a;n man
<l><app>
     <rdg wit='M' hand='m1'>alle</rdg>
     <rdg id='ANON.6.4' wit='M' hand='m2'>allen</rdg>
   </app>
   disen sumer g&a;n.
 
<!-- ... -->
<witDetail target='ANON.6.4' wit='M'><ref>allen</ref>
   <mentioned>n</mentioned> nachgetragen.</witDetail>
<!-- ... -->]]></eg>
 <!-- Des Minnesangs Fr&uuml;hling, ed.  Hugo Moser and        --><!-- Helmut Tervooren (Stuttgart:  Hirzel, 1977), I, 20.      --><!-- (Anonymous VI).                                          --></p><p>Observe that a single witness detail element may be linked to several
different readings (noting, for example, a recurrent phenomena in a
particular manuscript) by having the <att tei="yes">target</att> attribute point
at all the readings in question.  Similarly, feature structures
containing information about the text in a witness (whether
retroversion, regularization, or other) can also be linked to specific
<gi tei="yes">lem</gi> and <gi tei="yes">rdg</gi> instances.  See chapter <xref target="FS"/>.</p><p>The <gi tei="yes">witDetail</gi> element is formally declared thus:
 
<dtdFrag id="DTCAPWD" n="Witness Details"><tagDecl tagDoc="WITDTL"/></dtdFrag></p></div4><div4 id="TCSCWL" name="Section" ref="Y"><head>Witness Information in the Source</head><!-- delete this section?  added 1994-01-23 CMSMcQ --><p>In the transcription of printed critical editions, it may be
desirable to retain for future reference the exact form in which the
source edition records the witnesses to a particular reading; this is
particularly important in cases of ambiguity in the information, or
uncertainty as to the correct interpretation.  The <gi tei="yes">wit</gi>
element may be used to transcribe such lists of witnesses to a
particular reading.
 
<tagList style="one-line"><tagDesc tagDoc="WIT"/></tagList>
 
The <gi tei="yes">wit</gi> list may appear following a <gi tei="yes">rdg</gi>,
<gi tei="yes">rdgGrp</gi>, or <gi tei="yes">lem</gi> element in any apparatus entry, and
should be used only to transcribe the witness information in the form
found in the source.<!-- In particular, it should not be used as a substitute     --><!-- for the <att>wit</att> attribute:  where present, the    --><!-- information in the <gi>wit</gi> element and the          --><!-- <att>wit</att> attribute should agree, unless the        --><!-- encoder is uncertain about the interpretation of the     --><!-- witness information in the source, or the encoder has    --><!-- corrected an error in the source.                        -->
The advantage of holding witness information in the <att tei="yes">wit</att>
attribute of <gi tei="yes">lem</gi> or <gi tei="yes">rdg</gi> is that this may make it more
convenient for an
SGML application to check that every sigil identifier has been declared
elsewhere in the document.  By giving the <att tei="yes">wit</att> attribute a
declared value of <code tei="yes" type="kw">IDREFS</code>, for example,
one could more easily ensure that readings are
assigned only to witness sigla given as <code tei="yes" type="kw">ID</code> values
for witnesses in a <gi tei="yes">witList</gi> element
(see section <xref target="TCAPWL"/>).  Such checking is somewhat more
difficult for
witness sigla held as the content of a <gi tei="yes">wit</gi> element:  an
application program can check them, but SGML parsers will not.
For this reasons, it is
recommended that encoders always hold witness information in the
<att tei="yes">wit</att> attribute of <gi tei="yes">lem</gi> and <gi tei="yes">rdg</gi>, where
possible.  Thus, as in the examples below, even when a reference to a
witness is exactly reproduced in the <gi tei="yes">wit</gi> element, the
corresponding sigil for that witness can be written into the wit
attribute of the matching <gi tei="yes">rdg</gi> or <gi tei="yes">lem</gi>.  However, in
cases where it is uncertain how the witness reference contained in the
<gi tei="yes">wit</gi> element should be interpreted, the <att tei="yes">wit</att> 
attribute on the
matching <gi tei="yes">rdg</gi> or <gi tei="yes">lem</gi> may be left empty.
 
<eg><![CDATA[<lg type=stanza>
<l id=DIET1.1>Sl&a-;fest du, vriedel ziere?
<l id=DIET1.2>wan wecket uns leider schiere;
<l id=DIET1.3>ein vogell&i-;n s&o-; wol get&a-;n
<l id=DIET1.3>daz ist der linden an daz zw&i-; geg&a-;n.
</lg>
 
<!-- ... -->
<app type='secondary' loc=Diet.1.1>
    <rdg wit='K Ba'>sl&a-;fst</rdg> <wit>K(Ba)</wit>
    </app>
<app type='secondary' loc=Diet.1.2>
    <rdg wit='K V'>Man</rdg> <wit>K(V)</wit>
    <rdg wit='K Wa'>weckt</rdg> <wit>K (Wackernagel 401)</wit>
    <rdg wit='Ju'>Ich waen ez taget uns schiere</rdg>
       <wit><bibl>Jungbluth, Festschr. Pretzel 1963, 122.</bibl></wit>
    </app>
<!-- ... -->
 
<!-- (The non-standard entities &a-; &o-; and &i-; are used   -->
<!-- here to indicate vowels with circumflexes.)              -->
<!-- The edition in question has two apparatus:  one of       -->
<!-- manuscript readings, and one of readings from editions   -->
<!-- and the secondary literature; hence the attribute        -->
<!-- value type='secondary'.                                  -->]]></eg>
 <!-- MF 39,18, ed. Moser/Tervooren, p. 66.                    -->
 
Of course, the sigla used for different witnesses need not be the same
in the source and the <att tei="yes">wit</att> attribute, as shown particularly in
the apparatus for the second line of the poem (Diet.1.2).</p><p>The formal declaration for <gi tei="yes">wit</gi> is as follows:
 
<dtdFrag id="DTCSCWL" n="Source-text Witness Lists in Apparatus"><tagDecl tagDoc="WIT"/></dtdFrag></p></div4><div4 id="TCAPWL" name="Section" ref="Y"><head>The Witness List</head><p>In the front matter of the edition, a list of all witnesses may be
given if desired, in the form of a witness list, held within a
<gi tei="yes">witList</gi> element.  This witness list must contain a series of
<gi tei="yes">witness</gi> elements.  Each <gi tei="yes">witness</gi> element may optionally
contain text describing that witness in detail and must have an
attibute holding as its value the sigil (siglum) or identifier for a
particular witness.
 
<tagList style="one-line"><tagDesc tagDoc="WITLIST"/><tagDesc tagDoc="WITNESS" atts="sigil included"/></tagList></p><p>The minimal information provided by a witness list is thus the set of
sigla for all the witnesses named in the apparatus.  For example, a
simple list of the four Chaucer manuscripts used in the examples of this
chapter could appear thus:
 
<eg><![CDATA[<witList>
    <witness sigil='El'>
    <witness sigil='Hg'>
    <witness sigil='La'>
    <witness sigil='Ra2'>
</witList>]]></eg></p><p>It is common, however, for witness lists to be somewhat
more informative:  each <gi tei="yes">witness</gi> element may contain a prose
description of the witness, or a bibliographic citation:
<eg><![CDATA[<witList>
    <witness sigil='El' >Ellesmere, Huntingdon Library 26.C.9</witness>
    <witness sigil='Hg' >Hengwrt, National Library of Wales, Aberystwyth,
                  Peniarth 392D</witness>
    <witness sigil='La' >British Library Lansdowne 851</witness>
    <witness sigil='Ra2'>Bodleian Library Rawlinson Poetic 149</witness>
</witList>]]></eg>
 
In some cases, the witness list contains a whole paragraph of commentary
for each witness:
 
<eg><![CDATA[<witList>
<witness sigil='A'>die sog. <soCalled>Kleine (oder alte)
        Heidelberger Liederhandschrift</soCalled>.
        <bibl>Universit&auml;tsbibliothek Heidelberg col. pal.
        germ. 357.  Pergament, 45 Fll. 18,5 &times 13,5 cm.</bibl>
        Wahrscheinlich die &ae;lteste der drei gro&ss;en Hss.
        Sie <q>datiert aus dem 123. Jahrhundert, etwa um 1275.
        Ihre Sprache weist ins Elsa&ss;, evtl. nach Stra&ss;burg.
        Man geht wohl nicht fehl, in ihr eine Sammlung aus dem
        Stadtpatriziat zu sehen</q> (<bibl><author>Blank</author>,
        [vgl. <ref>Lit. z. Hss. Bd. 2, S. 39</ref>] S. 14</bibl>).
        Sie enth&ae;lt 34 namentlich genannte Dichter.  <q>Zu
        den Vorz&ue;gen von A geh&oe;rt, da&ss; sie kaum je
        bewu&ss;t ge&ae;ndert hat, so da&ss; sie f&ue;r manche
        Dichter ... oft den besten Text liefert</q> (so wohl
        mit Recht <bibl><author>v. Kraus</author></bibl>).</witness>
<witness sigil='a'>Bezeichnung <bibl><author>Lachmann</author></bibl>s f&ue;r
        die von einer 2. Hand auf bl. 40-43 geschriebenen
        Strophen der Hs. A.</witness>
<witness sigil='B'>die <soCalled>Weingartner (Stuttgarter)
        Liederhandschrift</soCalled>.  <bibl>W&ue;rttembergische
        Landesbibliothek Stuttgart, HB XIII poetae germanici
        1.  Pergament, 156 Bll.  15 &times 11,5 cm; 25 teils
        ganzseitig, teils halbseitige Miniaturen.</bibl>  Kaum
        vor 1306 in Konstanz geschrieben.  Sie enth&ae;lt Lieder
        von 25 namentlich genannten Dichtern.  (Dazu kommen
        Gedichte von einigen ungenannten bzw. unbekannten
        Dichtern, ein Marienlobpreis und eine Minnelehre.)</witness>
<!-- etc. ... -->
</witList>
 
<!-- &ae; &oe; &ue; = a, o, u umlaut. ss = esszett            -->]]></eg></p><p>It is common, in text-critical work, to refer to frequently occurring
groups of witnesses by means of a single common sigil.  Such sigla may
be documented as pseudo-witnesses in their own right by including, in
the witness list, a <gi tei="yes">witness</gi> element giving the sigil for the group
and listing the other witnesses included in the group in the value of
the <att tei="yes">included</att> attribute.  In this example, the group of
manuscripts of the <q>Canterbury Tales</q> which make up <q>Constant
Group c</q> are themselves first allocated sigla in individual
<gi tei="yes">witness</gi> elements, and then those sigla are given as the
<att tei="yes">included</att> value of a further <gi tei="yes">witness</gi> element.  All the
manuscripts of this group may thereafter be referred to as <q>c</q>:
 
<eg><![CDATA[<witList>
    <witness sigil='Cp'>Corpus Christi Oxford MS 198</witness>
    <witness sigil='La'>British Library Lansdowne 851</witness>
    <witness sigil='Sl2'>British Library Sloane MS 1686</witness>
     <witness sigil='c' included='Cp La Sl2'>Constant Group c</witness>
</witList>]]></eg>
 
That the reading <q>Experiment</q> occurs in all three manuscripts
can now be indicated simply as follows:
 
<eg><![CDATA[<rdg wit='c'>Experiment</rdg>]]></eg>
 <!-- What happens if both 'c' and 'La' are given, on two      --><!-- different readings?  Needs clarification for next        --><!-- revision.  Allow single-ms readings to override a        --><!-- group?  What, then, about groups of groups, or about     --><!-- overlapping groups?  Perhaps better to say that 'c'      --><!-- *always* is the same as 'Cp La Sl2', with no             --><!-- exceptions.  (msm)                                       --></p><p>Situations commonly arise where there are many more or less
fragmentary witnesses, such that there may be quite distinct groups of
witnesses for different parts of a text or collection of texts.  One may
treat this with distinct <gi tei="yes">witList</gi> elements for each different
part.  Alternatively, one may have a single <gi tei="yes">witList</gi> element at
the beginning of the file listing all the witnesses, partial and
complete, for the text, with the attestation of fragmentary witnesses
indicated within the apparatus by use of the <gi tei="yes">witStart</gi>
and <gi tei="yes">witEnd</gi> elements described in section <xref target="TCAPMI"/>.</p><p>If a witness list is provided, it may be unnecessary to give, in each
apparatus entry, an exhaustive list of the witnesses which agree with
the base text.  An application program can --- in principle --- compare
the witnesses given for each variant found with those given in the full
list of witnesses, subtracting from this list all the witnesses not
active at this point (perhaps because of lacuna, or because they contain
a variation on a different, overlapping lemma) and thence calculate all
the manuscripts agreeing with the base text.  In practice, encoders may
find it less error-prone to list all witnesses explicitly in each
apparatus entry.</p><p>The formal declaration of <gi tei="yes">witList</gi> and <gi tei="yes">witness</gi> is as
follows:
 
<dtdFrag id="DTCAPLW" n="Witness Lists in Front Matter"><tagDecl tagDoc="WITLIST"/><tagDecl tagDoc="WITNESS"/></dtdFrag></p></div4></div3><div3 id="TCAPMI" name="subsection" ref="Y"><head>Fragmentary Witnesses</head><p>If a witness is incomplete (whether a single fragment, a series of
fragments, or a relatively complete text with one or more lacunae), it
is usually desirable to record explicitly where its preserved portions
begin and end.  The following empty tags, which may occur within any
<gi tei="yes">lem</gi> or <gi tei="yes">rdg</gi> element, indicate the beginning or end of a
fragmentary witness or of a lacuna within a witness:
 
<tagList style="one-line"><tagDesc tagDoc="WITSTART"/><tagDesc tagDoc="WITEND"/><tagDesc tagDoc="LACSTART"/><tagDesc tagDoc="LACEND"/></tagList>
 
All are members of the model class <ident tei="yes" type="class">fragmentary</ident>.</p><p>Suppose a fragment of a manuscript X of the <title>Wife of Bath's
Prologue</title> has a physical lacuna, and the text of the manuscript
begins with <cited>auctorite</cited>.  In an apparatus this might appear
thus, distinguished from the reading of other manuscripts by the
presence of the <gi tei="yes">lacunaEnd</gi> element:
 
<eg><![CDATA[<app>
    <lem wit='El Hg'>Auctoritee</lem>
    <rdg wit='La Ra2'>auctorite</rdg>
    <rdg wit='X'><lacunaEnd>auctorite</rdg>
</app>]]></eg>
 
In some cases, the apparatus in the source may commence recording the
readings for a particular witness without its being clear whether the
previous absence of readings for this witness is due to a lacuna, or to
some other reason.  The <gi tei="yes">witStart</gi> element may be used in this
circumstance:
 
<eg><![CDATA[<app>
    <lem wit='El Hg'>Auctoritee</lem>
    <rdg wit='La Ra2'>auctorite</rdg>
    <rdg wit='X'><witStart>auctorite</rdg>
</app>]]></eg></p><p>The formal declarations for these elements are these:
 
<dtdFrag id="DTCFW" n="Fragmentary witnesses"><tagDecl tagDoc="WITSTART"/><tagDecl tagDoc="WITEND"/><tagDecl tagDoc="LACSTART"/><tagDecl tagDoc="LACEND"/></dtdFrag></p></div3></div2><div2 id="TCAPLK" name="Ilocano" ref="Y"><head>Linking the Apparatus to the Text</head><p>Three different methods may be used to link a critical
apparatus to the text:
 
<list type="bullets"><item>the location-referenced method,</item><item>the double-end-point-attached method, and</item><item>the parallel segmentation method.</item></list></p><p>Both the location-referenced and the double end-point methods may be
used with either <term>in-line</term> or <term>external</term>
apparatus, the former dispersed within the base text, the latter held in
some separate location, within or outside the document with the base
text.  The parallel segmentation method does not use the concept of a
base text and may only be used for in-line apparatus.</p><p>Any document containing <gi tei="yes">app</gi> elements requires a
<gi tei="yes">variantEncoding</gi> declaration in the <gi tei="yes">editorialDecl</gi>
element of its TEI header, thus:
 
<tagList style="one-line"><tagDesc tagDoc="VARENCOD" atts="method location"/></tagList></p><p>For examples of this element, see the following sections.  The formal
declaration is given in section <xref target="HD53"/>.</p><div3 id="TCAPLO" name="subsection" ref="Y"><head>The Location-referenced Method</head><p>The location-referenced method of encoding apparatus provides a
convenient method for encoding printed apparatus; in this method as in
most printed editions, the apparatus is linked to the base text by
indicating explicitly only the block of text on which there is a variant
(noted usually by a canonical reference scheme, or by line number in the
edition, such as <q>A 137</q> or <q>Page 15 line 1</q>).</p><p>If the location-referenced method is used for an apparatus stored
externally to the base text, the TEI header must have the
declaration:
 
<eg><![CDATA[ <variantEncoding method='location-referenced' location='external'>]]></eg></p><p>In the <gi tei="yes">body</gi> of the document, the base text (here El) will
appear:
 
<eg><![CDATA[ <text>
 <body> ...
 <div n=WBP><head>The Prologe of the Wyves Tale of Bathe</head>
 <l n=1>Experience though noon Auctoritee</l>
 <l>Were in this world ...
 </div>
 </body>
 </text>]]></eg></p><p>Elsewhere in the document, or in a separate file, the apparatus will
appear.  On each <gi tei="yes">app</gi> element, the <att tei="yes">loc</att> attribute
should be specified to indicate where the variant occurs in the base
text.
 
<eg><![CDATA[ <app loc="WBP 1">
    <rdg wit='La'>Experiment</rdg>
    <rdg wit='Ra2'>Eryment</rdg>
 </app>]]></eg></p><p>If the same text is encoded using in-line storage, the apparatus is
dispersed through the base text block to which it refers.  In this case,
the location of the variant can be read from the line in which it
occurs.
 
<eg rend="skel"><![CDATA[<tei.2>
<teiHeader>
  <!-- ... -->
  <encodingDesc>
    <!-- ... -->
    <editorialDecl>
      <!-- ... -->
      <variantEncoding method='location-referenced' location='internal'>
      <!-- ... -->
    </editorialDecl>
    <!-- ... -->
  </encodingDesc><!-- ... -->
</teiHeader>
<text>
<body>
  <!-- ... -->
  <div n=WBP><head>The Prologe ... </head>
     <l n=1>Experience
     <app>
          <rdg wit='La'>Experiment</rdg>
          <rdg wit='Ra2'>Eryment</rdg>
     </app>
     though noon Auctoritee</l>
     <l>Were in this world ...
</body>
</text>
</tei.2>]]></eg></p><p>Since the location is not required to be exact, the apparatus for
a line might also appear at the end of the line:
 
<eg><![CDATA[ <l n=1>Experience though noon Auctoritee
 <app>
     <rdg wit='La'> Experiment</rdg>
     <rdg wit='Ra2'> Eryment</rdg>
 </app></l>
 <l>Were in this world ...]]></eg></p><p>When the apparatus is linked to the text by means of location
references, as shown here, it is not possible to find automatically the
precise portion of text varied by the readings.  In order to show
explicitly what portion of the base text is replaced by the variant
readings, the <gi tei="yes">lem</gi> element may be used:
 
<eg><![CDATA[ <l n=1>Experience though noon Auctoritee
 <app>
     <lem wit='El' >Experience</lem>
     <rdg wit='La' >Experiment</rdg>
     <rdg wit='Ra2'>Eryment</rdg>
 </app></l>
 <l>Were in this world ...]]></eg>
 
Often the lemma will have no attributes, being simply the
<soCalled>base-text reading</soCalled> and requiring no qualification,
but it may optionally carry the normal attributes, as shown here.  Some
text critics prefer to abbreviate or elide the lemma, in order to save
space or trouble; such practice is not forbidden by these Guidelines,
but no recommendations are made for conventions of abbreviating the
lemma, whether abbreviation of each word, or suppression of all but the
first and last word, etc.</p><p>Where it is intended that the apparatus be complete enough to allow
the <soCalled>reconstruction</soCalled> of the witnesses (or at least of
their non-orthographic variations), the location-reference method should
be avoided in favor of one of the other two methods, which allow the
unambiguous reconstruction of the lemma from the encoding.</p></div3><div3 id="TCAPDE" name="subsection" ref="Y"><head>The Double End-Point Attachment Method</head><p>In the double end-point attachment method, the beginning and end of
the lemma in the base text are both explicitly indicated.  It thus
differs from the location-referenced method, in which only the larger
span of text containing the lemma is indicated.  Double end-point
attachment permits unambiguous matching of each variant reading against
its lemma.  It or the parallel-segmentation method should be used in all
cases where this is desired, for example where the apparatus is intended
to enable full reconstruction of the text, or of the substantives, of
every witness.</p><p>When the double endpoint attachment method is used, the
<att tei="yes">from</att> and <att tei="yes">to</att> attributes of the <gi tei="yes">app</gi> element
are used to indicate the beginning and ending points of the reading in
the base text:  their values are SGML identifiers which occur at the
locations in question.  If no other markup is present there, the
beginning and ending points should be marked using the <gi tei="yes">anchor</gi>
element defined in chapter <xref target="SA"/>.  In cases where it is not
possible to insert anchors within the base text (e.g. where the text is
on a read-only medium) the beginning and end of the lemma may be
indicated by using the <soCalled>indirect pointing</soCalled> mechanisms
discussed in chapter <xref target="SA"/>.  Explicit anchors are more likely
to be reliable, and are therefore to be preferred.</p><p>The double end-point attachment method may be used with in-line or
external apparatus.  In the latter case, the base text (here El) will
appear with <gi tei="yes">anchor</gi> elements inserted at every place where a
variant begins or ends (unless some element with an SGML identifier
already begins or ends at that point):
 
<eg rend="skel"><![CDATA[<tei.2>
<teiHeader>
    <!-- ... -->
    <variantEncoding method='double-end-point' location='external'>
    <!-- ... -->
</teiHeader>
<text>
<body>
 <!-- ... -->
 <div n=WBP><head>The Prologe ... </head>
 <l n=1 id='WBP.1'>Experience <anchor id=A2> though noon
        Auctoritee</l>
 <l>Were in this world ...
  <!-- ... -->
</text>
</tei.2>]]></eg>
 
The apparatus will be separately encoded:
 
<eg><![CDATA[<app from=wbp.1 to=a2>
    <rdg wit='La'>Experiment</rdg>
    <rdg wit='Ra2'>Eryment</rdg>
</app>]]></eg>
 
No <gi tei="yes">anchor</gi> element is needed at the beginning of the line, since
the <att tei="yes">from</att> attribute can use the SGML identifier for the
line as a whole; the lemma is assumed to run from the beginning of the
element indicated by the <att tei="yes">from</att> attribute, to the end of that
indicated by the <att tei="yes">to</att> attribute.  If no value is
given for <att tei="yes">to</att>, the lemma runs from the beginning to the end of
the element indicated by the <att tei="yes">from</att> attribute.</p><p>When the apparatus is encoded in-line, it is dispersed through the
base text.  Only the beginning of the lemma need be marked with an
<gi tei="yes">anchor</gi>, since the <gi tei="yes">app</gi> is inserted at the end of the
lemma, and itself therefore marks the end of the lemma.
 
<eg rend="skel"><![CDATA[<tei.2>
<teiHeader>
    <!-- ... -->
    <variantEncoding method='double-end-point' location='internal'>
    <!-- ... -->
</tei.Header>
<text>
<body>
<!-- ... -->
<div><head>The Prologe ...</head>
<l n=1 id=WBP.1>Experience
     <app from=WBP.1>
          <rdg wit='La'>Experiment</rdg>
          <rdg wit='Ra2'>Eryment</rdg>
     </app>
though noon Auctoritee
<l>Were in this world ...
<!-- ... -->
</body>
</tei.2>]]></eg></p><p>The lemma need not be repeated within the <gi tei="yes">app</gi> element in
this method, as it may be extracted reliably from the base text.  If an
exhaustive list of witnesses is available, it will also not be necessary
to specify just which manuscripts agree with the base-text to enable
reconstruction of witnesses.  An application will be able to determine
the manuscripts that witness the base reading, by noting which witnesses
are attested as having a variant reading, and inferring the base-text
reading for all others after adjusting for fragmentary witnesses and for
witnesses carrying overlapping variant readings.</p><p>Alternatively, if it is desired to make an explicit record of the
attestation of the base text the <gi tei="yes">lem</gi> element may be embedded
within <gi tei="yes">app</gi>, carrying the witnesses to the base.  Thus
 
<eg><![CDATA[<app  from=wbp.1 to=a2>
    <lem wit='El Hg'>Experience</lem>
    <rdg wit='La'>Experiment</rdg>
    <rdg wit='Ra2'>Eryment</rdg>
</app>]]></eg></p><p>This method is designed to cope with <soCalled>overlapping
lemmata</soCalled>.  For example,  at line 117 of the Wife of Bath's
Prologue, the manuscripts Hg (Hengwrt), El (Ellesmere) and Ha4 (British
Library Harleian 7334) read:
 
<list type="simple"><item>Hg: And of so parfit wys a wight ywroght</item><item>El: And for what profit was a wight ywroght</item><item>Ha4: And in what wise was a wight ywroght</item></list></p><p>In this case, one might wish to record <q>in what wise was</q> in Ha4
as a single variant for <q>of so parfit wys</q> in Hg, and <q>was a
wight</q> in El and H4 as a variant on <q>wys a wight</q> in Hg.  This method
can readily cope with such difficult situations, typically found in
large and complex traditions:
 
<eg><![CDATA[<text><body>
<l n=117 id='WBP.117' > And
   <anchor id='A117.1'> of so parfit
   <anchor id='A117.2'> wys
   <anchor id='A117.3'> a wight
   <anchor id='A117.4'> ywroght
<!-- ... -->
<app from=a117.1 to=a117.3>
     <lem wit='Hg' >of so parfit wys</lem>
     <rdg wit='Ha4'>in what wise was</rdg>
</app>
<app from=a117.2 to=a117.4>
     <lem wit='Hg'>wys a wight</lem>
     <rdg wit='El Ha4'>was a wight</rdg>
</app>
</l>
</body></text>]]></eg>
 
The parallel segmentation method, to be discussed next, cannot handle
overlaps among variants, and would require the individual variants to be
split into pieces.</p><p>Because creation and interpretation of double end-point attachment
apparatus will be lengthy and difficult it is likely that they will
usually be created and examined by scholars only with mechanical
assistance.</p></div3><div3 id="TCAPPS" name="subsection" ref="Y"><head>The Parallel Segmentation Method</head><p>This method differs from the double end-point attachment method in
that all variants at any point of the text are expressed as variants
on one another.  In this method, no two variations can overlap,
although they may nest.  Thus, the concepts of a base text and of a
lemma become unnecessary:  the texts compared are divided into
matching segments all synchronized with one another.  This permits
direct comparison of any span of text in any witness with that in
any other witness.  It is also very easy with this method for an
application to extract the full text of any one witness from the
apparatus.</p><p>This method will (by definition) always be satisfactory when there
are just two texts for comparison (assuming they are in the same
language and script).  It will also be useful where editors do not wish
to privilege a text as the <soCalled>base</soCalled> or when editors
wish to present parallel texts.  It will become less convenient as
traditions become more complex and tension develops between the need to
segment on the largest variation found and the need to express the
finest detail of agreement between witnesses.</p><p>In the parallel segmentation method, each segment of text on which
there is variation is marked by an <gi tei="yes">app</gi> element; each reading is
given in a <gi tei="yes">rdg</gi> element; if it is desired to single out one
reading as preferred, it may be tagged <gi tei="yes">lem</gi>:
 
<eg rend="skel"><![CDATA[<tei.2><teiHeader>
<!-- ... -->
    <variantEncoding method='parallel-segmentation'
                     location='internal'>
    <!-- ... -->
</teiHeader>
<text>
<body>
<!-- ... -->
    <l n=1>
    <app><lem wit='El Hg'>Experience</lem>
         <rdg wit='La'>Experiment</rdg>
         <rdg wit='Ra2'>Eryment</rdg>
    </app>
    though noon Auctoritee</l>
    <l>Were in this world ...]]></eg></p><p>This method cannot be used with external apparatus:  it must be used
in-line.  Note that apparatus encoded with this method may be translated
into the double end-point attachment method and back without loss of
information.  Where double-end-point-attachment encodings have no
overlapping lemmata, translation of these to the parallel segmentation
encoding and back will also be possible without loss of information.</p><p>For economy, the witnesses to the reading most widely attested need
not be stated.  Since all manuscripts must be represented in all
apparatus entries, it will be possible for an application to read a
<gi tei="yes">witList</gi> declaring all the witnesses to the text and then
calculate which witnesses have not been named.  In the example below,
only La and Ra2 are identified explicitly with a reading; an application
might successfully infer from this that <cited>Experience</cited>,
whose witnesses are not given, must be attested by El and Hg.  To avoid
confusion, however, witnesses may be omitted only for a single reading.
 
<eg><![CDATA[    <l n=1>
    <app><lem>Experience</lem>
         <rdg wit='La'>Experiment</rdg>
         <rdg wit='Ra2'>Eryment</rdg>
    </app>
    though noon Auctoritee</l>
    <l>Were in this world ...]]></eg></p><p>Alternatively, the witnesses for every reading may be stated, as in
the first example.</p><p>As noted, apparatus entries may nest in this method:  if an imaginary
fifth manuscript of the text read <q>Auctoritee, though none
experience</q>, the variation on the individual words of the line would
nest within that for the line as a whole:
 
<eg><![CDATA[<l n=1>
<app>
  <rdg wit=Chi3>Auctoritee, though none experience</rdg>
  <rdg>
    <app><rdg wit='El Hg'>Experience</rdg>
         <rdg wit='La'>Experiment</rdg>
         <rdg wit='Ra2'>Eryment</rdg>
    </app>
    <app><rdg wit='El Ra2'>though</rdg>
         <rdg wit='Hg'>thogh</rdg>
         <rdg wit='La'>thouh</rdg>
    </app>
    <app><rdg wit='El Hg'>noon Auctorite</rdg>
         <rdg wit='La Ra2'>none auctorite</rdg>
    </app>
  </rdg>
  </app>
</l>]]></eg></p><p>Parallel segmentation cannot, however, deal very gracefully with
variants which overlap without nesting:  such variants must be broken up
into pieces in order to keep all witnesses synchronized.
 <!-- cut following at PR's suggestion (the imaginary example is --><!-- no longer there) -->
 <!-- The imaginary example at the end of the previous section --><!-- might be tagged thus using this method: -->
 <!-- <eg> --><!-- <![ CDATA [ --><!-- <l n=3 id=WBP.3>To --><!--     <app> --><!--         <rdg>speke</> --><!--         <rdg wit=Chi1>sigh</> --><!--     </app> --><!--     of --><!--     <app> --><!--         <rdg>wo</> --><!--         <rdg wit=Chi1>wailing</> --><!--         <rdg wit=Chi2>blisse</> --><!--     </app> --><!--     that --><!--     <app> --><!--         <rdg>is</> --><!--         <rdg wit=Chi2>wanes</> --><!--     </app> --><!--     in mariage; --><!-- </l> --><!-- ]]> --><!-- </eg> --></p></div3></div2><div2 id="TCTR" name="Ilocano" ref="Y"><head>Using Apparatus Elements in Transcriptions</head><p>It is often desirable to record different transcriptions of the one
stretch of text.  These variant transcriptions may be grouped within a
single <gi tei="yes">app</gi> element.  An application may then construct
different <q>views</q> of the transcription by extraction of the
appropriate variant readings from the apparatus elements embedded in the
transcription.</p><p>For example, alternative expansions can be recorded in several
different <gi tei="yes">expan</gi> elements, all grouped within an <gi tei="yes">app</gi>
element.  Consider, for example, the three different transcriptions
given below of line 105 of the Hengwrt manuscript of Chaucer's
<title>The Wife of Bath's Prologue</title>.  The last word of the line
<q>Virginite is grete perfection</q> is written <q>perfectio</q>
followed by two minims over which a bar has been drawn, which has been
read in different ways by different scholars.  The first
transcription, by Elizabeth Solopova, represents the two minims with
bar above by reference to an entity <ident tei="yes" type="ent">i-i</ident>.  This
transcription notes this as a mark of abbreviation but gives no
expansion for it.  A second transcriber, F. J. Furnivall, regards the
bar as an abbreviation of <cited>u</cited>, reading the two minims as
an <cited>n</cited>.  A third transcriber, P. G. Ruggiers, regards the
bar as an abbreviation of <cited>n</cited>, reading the minims as
<cited>u</cited>.  This information may be held within an <gi tei="yes">app</gi>
structure, as follows:
 
<eg><![CDATA[Virginite is grete
<app>
   <rdg resp=ES >perfectio<abbr>&i-i;</abbr></rdg>
   <rdg resp=FJF>perfectio<expan>u</expan>n</rdg>
   <rdg resp=PGR>perfectiou<expan>n</expan></rdg>
</app>]]></eg>
 
This example illustrates the adaptation of the <gi tei="yes">rdg</gi> element for
use within the transcription of a particular witness.  The
<att tei="yes">wit</att> attribute, which may be compulsory in recording variant
readings of many witnesses within a critical apparatus, is redundant
when recording variant readings relating to a single witness.  However,
it may be desirable to specify the editorial responsibility for a
particular reading within a transcription.  For all three readings, the
<att tei="yes">resp</att> attribute on <gi tei="yes">rdg</gi> assigns this responsibility.
Using this system, it will be straightforward for an application to
extract from the one file the three different transcriptions done by
these scholars.  To do this, the application need look only at the
<att tei="yes">resp</att> attribute on each <gi tei="yes">rdg</gi> element.</p><p>Observe too that in this example the <att tei="yes">resp</att> attribute is
attached to the outer <gi tei="yes">rdg</gi> element and is not repeated for the
inner <gi tei="yes">expan</gi> elements.  There is no need for repetition of the
<att tei="yes">resp</att> attribute values, as the <gi tei="yes">expan</gi> elements
contained within each <gi tei="yes">rdg</gi> element will inherit the value of the
<att tei="yes">resp</att> from the outer <gi tei="yes">rdg</gi> element.  Thus, the
processor will know that the responsibility for the expansion
<q>perfectio<tag compl="full" tei="yes">expan</tag>u<tag compl="full" tei="yes">/</tag>n</q> lies with <q>FJF</q>, as
<q>FJF</q> was responsible for the reading containing this expansion.
This simplifies the processing of the information, as the application
has only to look at the attribute values for each reading in turn and
not for those for elements nested within.</p><p>Editorial notes may also be attached to <gi tei="yes">app</gi> structures
within transcriptions.  Here, editorial preference for Ruggiers'
expansion and an explanation of that preference is given:
 
<eg><![CDATA[Virginite is grete
<app>
   <rdg resp=ES>perfecti<abbr>o&i-i;</abbr></rdg>
   <rdg id=F105 resp=FJF>perfectio<expan>u</expan>n</rdg>
   <rdg id=R105 resp=PGR>perfectiou<expan>n</expan></rdg>
</app>
 
<!-- ... note element appearing elsewhere in the document ... -->
 
<note target="R105 F105">Furnivall's expansion implies
that the bar is an abbreviation for 'u'.  There are no
certain instances of this mark as an abbreviation for 'u'
in these MSS and it is widely used as an abbreviation
for 'n'.  Ruggiers' expansion is to be accepted.</note>]]></eg></p><p>In most cases, elements used to indicate features of a primary
textual source may be represented within an <gi tei="yes">app</gi> structure
simply by nesting them within its readings, just as the <gi tei="yes">abbr</gi>
and <gi tei="yes">expan</gi> elements are nested within the <gi tei="yes">rdg</gi> elements
in the example just given.  However, in cases where the tagged feature
extends across a span of text which might itself contain variant
readings which it is desired to represent by <gi tei="yes">app</gi> structures,
some adaptation of the tagging may be necessary.  For example, a span of
text may be marked in the transcription of the primary source as a
single deletion but it may be desirable to represent just a few words
from this source as individual deletions within the context of a
critical apparatus drawing together readings from this and several other
witnesses.  In this case, the tagging of the span of words as one
deletion may need to be decomposed into a series of one-word deletions
for encoding within the apparatus.  If it is important to record
the fact that all were deleted by the same act, the markup may use
the <gi tei="yes">join</gi> element or the <att tei="yes">next</att> and <att tei="yes">prev</att>
attributes defined by chapter <xref target="SA"/>.</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2tc.odd ??><!-- 19 Text Criticism ... --><?tei:SOF p2nd.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2nd.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/30 12:07:28  tei
    * *** empty log message ***
    *
    * Revision 1.7  1998/01/29 17:05:51  tei
    * lowercase DTD filename
    * normalize SGML
    *
    * Revision 1.6  1994/04/08 18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.5  1994/04/01  16:25:55  msmcq
    * Changes while validating DTDs
    *--><!-- Revisions:                                               --><!-- 98-01-29 : MSM : lowercase DTD file name, normalize      --><!-- 94-04-07 : MSM : trivia                                  --><!-- 94-03-31 : MSM : add declaration for a.names             --><!-- 94-03-31 : MSM : explicitly identify files for this tag set --><!-- 6 mar: killed measure; add para on virtual objects --><!-- 93-06-03 : MSM : add editorial note                      --><!-- 21 May LB : rewrote to go with DG's post-Eynsham version --><!-- 9 apr 93: added tagdecls --><!-- From: Dan Greenstein <digger@uk.ac.glasgow.udcf>   --><!-- Date: Wed, 1 Jul 92 15:20:47 BST   --><div1 id="ND" n="20" name="Faisal" ref="Y"><head>Names and Dates</head><p>This chapter describes an additional tag set which may be used for
the encoding of proper names and other phrases descriptive of persons,
places, organizations, and also of dates and times, in a manner more
detailed than that possible using the elements already provided for
these purposes in the core tag set described in chapter <xref target="CO"/>.</p><p>In section <xref target="CONA"/> it was noted that the elements
provided in the core allow the encoder to specify that a given
text segment is a proper noun, or a <term>referring string</term>, and
to specify the kind of object named or referred to only by supplying a
value for the <att tei="yes">type</att> attribute. The elements provided by the
present tag set allow the encoder both to supply a detailed
sub-structure for such referring strings, and also to distinguish
explicitly between names of persons, places or organizations.</p><p>Similarly, the elements provided here allow the encoder to supply a
detailed analysis of the component parts of any expression which
denotes a date or time, which is not possible using the elements
described in section <xref target="CONADA"/>.</p><p>It should be noted however that no provision is made by the present
tag set for the representation of the abstract structures, or
<soCalled> virtual objects</soCalled> to which names or dates may be
said to refer. In simple terms, where the core tag set allows one to
represent a <term>name</term>, this additional tag set allows one to
represent a <term>personal name</term>, but neither provides for the
direct representation of a <term>person</term>. Appropriate
mechanisms for the encoding of such interpretative gestures may be
found in chapters <xref target="AI"/> and <xref target="FS"/>.</p><p>To enable the additional tag set described in the present chapter,
a parameter entity <term>TEI.names.dates</term> must be declared in
the document type subset with the value <code tei="yes" type="frag">INCLUDE</code>, as
further described in section <xref target="STIN"/>. A document using the
prose base tag set and this additional tag set will thus begin as
follows:
 
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
      <!ENTITY % TEI.prose 'INCLUDE' >
      <!ENTITY % TEI.names.dates 'INCLUDE' >
 ]>]]></eg></p><p>The chapter begins by discussing additional tags for the
encoding of component parts of personal names (section <xref target="NDPER"/>, place names (section <xref target="NDPLAC"/>) and
organizational names (section <xref target="NDORG"/>). Detailed encoding of
dates and times is described in section <xref target="NDDATE"/>.<!-- ) and on measures (section <xref target=NDMEAS>). --></p><p>The additional tag set for names and dates, included in the file
<ident tei="yes" type="file">teind2.dtd</ident>, has the following overall
structure:
 
<dtdFrag id="DND" n="Additional tags for names and dates" file="teind2"><dtdRef dtdFrag="DNDPER"/><dtdRef dtdFrag="DNDPLAC"/><dtdRef dtdFrag="DNDORG"/><dtdRef dtdFrag="DNDDATE"/><!-- <dtdRef dtdFrag=DNDMEAS> --></dtdFrag></p><p>When this tag set is enabled, three additional element classes
called <term>persPart</term>, <term>placePart</term>, and
<term>temporalExpr</term> are declared.  The parameter entities
corresponding with these classes are declared in the file
<ident tei="yes" type="file">teind2.ent</ident>, as follows:
 
<dtdFrag id="DNDENT" n="Additional classes for names and dates" file="teind2.ent"><claDecl classDoc="PERSPART" type="model"/><claDecl classDoc="PLACPART" type="model"/><claDecl classDoc="TEMPEXP" type="model"/><claDecl classDoc="NAMES" type="atts"/><claDecl classDoc="PERSPART" type="atts"/><claDecl classDoc="PLACPART" type="atts"/><claDecl classDoc="TEMPEXP" type="atts"/></dtdFrag></p><?tei:SOF p2ndper.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2ndper.odd,v $
# Revision 1.7  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
    *--><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2ndper.odd,v $
# Revision 1.7  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
# Revision 1.6  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.5  1994/04/01  16:25:55  msmcq
# Changes while validating DTDs
# --><!-- Revisions:                                               --><!-- 5 jan 98 : LB : fix typos in egs; typo from MSM          --><!-- 94-04-07 : MSM : clarify treatment of patronymics        --><!-- 94-03-31 : MSM : disambiguate TERM, Q                    --><!-- 94-03-29 : MSM : include persname in dtdfrag             --><!-- 94-03-29 : MSM : Added RCS id                            --><!-- 93-06-05 : MSM : remove leading blank from P elems       --><!-- 21 may LB made parseable; lightly edited --><div2 id="NDPER" name="Ilocano" ref="Y"><head>Personal Names</head><p>The core <gi tei="yes">rs</gi> and <gi tei="yes">name</gi> elements can distinguish
names in a text but are insufficiently powerful to mark their internal
components or structure. To conduct nominal record linkage or even to
create an alphabetically sorted list of personal names, it is
important to distinguish between a family name, a forename and an
honorary title. Similarly, when confronted with a referencing string
such as <q>John, by the grace of God, king of England, lord of
Ireland, duke of Normandy and Aquitaine, and count of Anjou</q>, the
analyst will often wish to distinguish among components giving some
hint as to the status, occupation or residence of the person to whom
the name belongs.  The following elements are provided for these and
related purposes:
 
<tagList style="one-line"><tagDesc tagDoc="PERSNAME"/><tagDesc tagDoc="SURNAME"/><tagDesc tagDoc="FORENAME"/><tagDesc tagDoc="ROLENAME"/><tagDesc tagDoc="ADDNAME"/><tagDesc tagDoc="NAMELINK"/><tagDesc tagDoc="GENNAME"/></tagList>
 </p><p>As members of the <ident tei="yes" type="class">names</ident> class, all of these
elements share the following attributes:
 
<adList classDoc="NAMES" atts="key reg"/>
 </p><p>Additionally, all of the above elements except for <gi tei="yes">persName</gi>
are members of the class <ident tei="yes" type="class">personPart</ident>, and thus
share the following attributes:
 
<adList classDoc="PERSPART" atts="type full sort"/>
 <!-- key and reg are inherited by pname from name -->
 </p><p>The <gi tei="yes">persName</gi> element may be used in preference to the
general <gi tei="yes">name</gi> element irrespective of whether or not the
components of the personal name are also to be marked. Its
<att tei="yes">key</att> and <att tei="yes">reg</att> attributes are used in exactly the
same way as those on the <gi tei="yes">rs</gi> and <gi tei="yes">name</gi> elements (see
section <xref target="CONA"/>). The tag <gi tei="yes">persName</gi> is synonymous
with the tag <tag compl="full" tei="yes">name type=person</tag>, except that its
<att tei="yes">type</att> attribute allows for further subcategorization of the
personal name for example as a <q>married</q>, <q>maiden</q>,
<q>pen</q>, <q>pseudo</q> or <q>religious</q> name.  Consequently the
following examples are equivalent:
 
<eg> <![CDATA[
 
That silly man <rs key=DPB1 type=person reg='Brown, David
Paul'>David Paul Brown</rs> has suffered the furniture of
his office to be seized the third time for rent.
 
That silly man
<rs key=DPB1 type=person reg='Brown, David Paul'>
<name>David Paul Brown</name>
</rs> has suffered the furniture of
his office to be seized the third time for rent.
 
That silly man
<name key=DPB1 type=person reg='Brown, David Paul'>
David Paul Brown</name> has suffered ...
 
That silly man
<persName key=DPB1 type=person reg='Brown, David Paul'>
David Paul Brown</persName> has suffered ...
 ]]></eg>
 </p><p>The <gi tei="yes">persName</gi> element is more powerful than the
<gi tei="yes">rs</gi> and <gi tei="yes">name</gi> elements because distinctive name
components occurring within it can be marked as such.
 </p><p>Many cultures distinguish between a family or inherited
<term>surname</term> and additional personal names, often known as
<term>given names</term>.  These should be tagged using the
<gi tei="yes">surname</gi> and <gi tei="yes">foreName</gi> elements respectively and may
occur in any order:
 
<eg><![CDATA[<persName key=FDR1>
  <surname>Roosevelt</surname>,
  <foreName>Franklin</foreName>
  <foreName>Delano</foreName>
</persName>
 
<persName key=FDR1>
  <foreName>Franklin</foreName>
  <foreName>Delano</foreName>
  <surname>Roosevelt</surname>
</persName>]]></eg>
 </p><p>The <att tei="yes">type</att> attribute may be used with both
<gi tei="yes">foreName</gi> and <gi tei="yes">surname</gi> elements to provide further
culture- or project- specific detail about the name component, for
example:
 
<eg><![CDATA[ 
<persName key=FDR1>
 <foreName type='first'>Franklin</foreName>
 <foreName type='middle'>Delano</foreName>
 <surname type='last'>Roosevelt</surname>
</persName>
 
<persName key=MRT1>
 <foreName type='Christian'>Margaret</foreName>
 <foreName type='unused'>Hilda</foreName>
 <surname type='maiden'>Roberts</surname>
 <surname type='married'>Thatcher</surname>
</persName>
 
<persName key=MUAL1 type=religious>
 <foreName>Muhammad</foreName>
 <surname>Ali</surname>
</persName>]]></eg>
 
In the following two examples the <att tei="yes">type</att> attribute of the
<gi tei="yes">surname</gi> element is used to indicate so-called
double-barrelled or hyphenated surnames:
 
<eg><![CDATA[<persName key=KHS1>
  <foreName>Kara</foreName>
  <surname type=combine>Hattersley-Smith</surname>
</persName>
 
<persName key=NSJS1>
   <foreName>Norman</foreName>
   <surname type=combine>St John Stevas</surname>
</persName>]]></eg>
 </p><p>In most cases, patronymics should be treated as forenames, thus:
 
<eg><![CDATA[ ... but it remained for
 <persName>
   <foreName>Snorri</>
   <foreName>Sturluson</>
 </persName>
 to combine the two traditions in cyclic form.]]></eg><!-- Carol Clover, The Medieval Saga (Ithaca:  Cornell        --><!-- Univ. Press, 1982), p. 57.                               -->
 
When a patronymic is used as a surname, however (e.g. by an individual
who otherwise would have no surname, but lives in a culture which
requires surnames), it may be tagged as such:
 
<eg><![CDATA[Even <persName><foreName>Finnur</> <surname>Jonsson</>
</persName> acknowledged the artificiality of the
procedure:  <q>As <title>Nj&aacute;la</> now begins,
no original saga ever began.</q>]]></eg><!-- Clover, p. 77.                                           -->
 
In the following example, the <att tei="yes">type</att> attribute is used
to distinguish a patronymic from other forenames:
 
<eg><![CDATA[<persName key=pn9>
  <foreName sort=2>Sergei</foreName>
  <foreName sort=3 type='patronym'>Mikhailovic</foreName>
  <surname sort=1>Uspensky</surname>
</persName>]]></eg>
 </p><p>This example also demonstrates the use of the <att tei="yes">sort</att>
attribute common to all members of the
<ident tei="yes" type="class">personPart</ident> class; its effect is to state the
sequence in which <gi tei="yes">foreName</gi> and <gi tei="yes">surname</gi> elements should
be combined when constructing a sort key for the name.
 </p><p>Some names include generational or dynastic information, such as
<q>Junior</q> or <q>senior</q>, or a number: the <gi tei="yes">genName</gi>
element may be used to distinguish these from other parts of the name,
as in the following examples:
 
<eg><![CDATA[<persName key=HEMA1>
  <surname>Marques</surname>
  <genName>Junior</genName>,
  <foreName>Henrique</foreName>
</persName>
 
<persName>
  <foreName>Charles</foreName>
  <genName>II</genName>
</persName>
 ]]></eg>
 </p><p>It is also often convenient to distinguish phrases (historically
similar to the generational labels mentioned above) used to link parts
of a name together, such as <q>von</q>, <q>of</q>, <q>de</q> etc. It
is often a matter of arbitrary choice whether or not such components
are regarded as part of the surname or not; the <gi tei="yes">nameLink</gi>
element is provided as a means of making clear what the correct usage
should be in a given case, as in the following examples:
 
<eg><![CDATA[<persName key=DUDO1>
 <roleName type=honorific full=abb>Mme</roleName>
 <nameLink>de la</nameLink>
 <surname>Rochefoucault</surname>
</persName>
 
<persName>
  <foreName>Walter</foreName>
   <surname>de la Mare</surname>
</persName>]]></eg>
 </p><p>Finally, the <gi tei="yes">addName</gi> and <gi tei="yes">roleName</gi> elements are
used to mark all name components other than those already listed. The
distinction between them is that a <gi tei="yes">roleName</gi> encloses an
associated name component such as an aristocratic or official title
which exists in some sense independently of its bearer. The
distinction is not always a clear one. As elsewhere, the
<att tei="yes">type</att> attribute may be used with either element to supply
culture- or application- specific distinctions.  Some typical values
for this attribute for names in the Western European tradition follow:
<list type="gloss"><label>nobility</label><item>An inherited or life-time
title of nobility such as Lord, Viscount, Baron, etc.</item><label>honorific</label><item>An academic or other honorific prefixed to a name
e.g.  Dr., Professor, Mrs., etc.</item><label>office</label><item>Membership of some elected or
appointed organization such as President, Governor, etc.</item><label>military</label><item>Military rank such as Colonel.</item><label>epithet</label><item>A traditional descriptive phrase
or nick-name such as The Hammer, The Great, etc.</item></list>
 </p><p>Here are some further examples of the usage of these elements:
 
<eg><![CDATA[<persName key=PGK1>
<roleName type=nobility>Princess</roleName>
<foreName>Grace</foreName>
</persName>
 
<persName key=GRMO1 type=pseudo>
<addName type=honorific>Grandma</addName>
<surname>Moses</surname>
</persName>
 
<persName key=MRSRO1>
<addName type=honorific>Mrs</addName>
<surname>Robinson</surname>
</persName>
 
<persName key=STAU1>
<roleName type=office>Saint</roleName>
<foreName>Augustine</foreName>
</persName>
 
<persName key=SLWICL1>
<roleName type=office>President</roleName>
<foreName>Bill</foreName>
<surname>Clinton</surname>
</persName>
 
<persName key=MOGA1>
<roleName type=military>Colonel</roleName>
<surname>Gaddafi</surname>
</persName>
 
<persName key=FRTG1>
<foreName>Frederick</foreName>
<addName type=epithet>the Great</addName>
</persName>]]></eg>
 </p><p>A name may have any combination of the above elements:
 
<eg><![CDATA[     <persName key=EGBR1>
     <roleName type=office>Governor</roleName>
     <foreName sort=2>Edmund</foreName>
     <foreName sort=3 full=init reg='Gerald'>G</foreName>.
     <addName type=nick>Jerry</addName>
     <addName type=epithet>Moonbeam</addName>
     <surname sort=1>Brown</surname>
     <genName full=abb>Jr</genName>.
     </persName>]]></eg>
 </p><p>Although highly flexible, these mechanisms for marking
personal name components will not cater for every personal name
and processing need. Where the internal structure of personal
names is highly complex or where name components are
particularly ambiguous, feature structures are recommended as
the most appropriate mechanism to mark and
analyze them, as further discussed in chapter <xref target="FS"/>.
 <!-- Earl/Marquis example cut for now. Sorry. -->
 <!--
 
<p>In the following brief example a feature structure is used to
represent an analyis of a personal name that appears twice in a
seventeenth-century Scottish legal document known as a sasine.  In the
sasine, the expressions <q>Archibald late earl of Argyle</q> and
<q>the late Marquis of Argyle</q> occur, but in context which make
apparent that both phrases refer to the same person at different times
in his life.  (Archibald would have remained a Marquis until his
father died at which time he would have become an Earl).  Though
crucial to a prosopographical analysis or a study of land ownership
based partly on the sasine, the interpretation of these two names
would be difficult or even impossible to mark with the elements
described in this section.
 
<p>The feature structure presented below is envisaged as a
collective biography about individuals.  An individual's
biographical detail are represented as features of a feature
structure of type <code type=val>person</code>.  For each feature
structure of type <code type=val>person</code>, features include
<code type=val>persName</code>, <code type=val>date-of-birth</code>,
<code type=val>place-of-birth</code>, etc.  The several feature
structures of type <code type=val>person</code> are then grouped
together in a so-called library of feature structures (<gi>fsLib</gi>)
not dissimilar to a database comprising biographical information on
several individuals.
 
<p>The portion of
the feature structure library shown below refers to Archibald.
It shows that several pieces of information have been collected
for Archibald, amongst them, information pertaining to his
personal name. It is this particular portion of the feature
structure that we are particularly interested in.
 
<p>Notice three things. Firstly, that the value of the feature
<code type=val>persName</code> is itself a feature structure
(<code type=val>name-structure</code>).  This enables the component
parts of the
personal name to be identified.  Secondly, that this feature structure
points to the sasine segment where the nominal expressions referring
to Archibald occur. In this way, secondary analysts can have immediate
access to the information upon which such the analysis was made in the
first place. Thirdly, that the <gi>vAlt</gi> mechanism is used to
indicate the alternate readings of Archibald's names; that is, that he
was either a Marquis or an Earl but not both. For more information
about the use of feature structures, see chapter <xref target=FS>.
 
<eg><![CDATA[
 
<text>
 
<s id=S1 anal=AEA1>
<lb><p>Item ane charter granted by Archibald late earl
<lb>of Argyle to Donald McNeill of Gallachalzie which
<lb>makes mention that the lands &illegible; and
<lb>Isles
<pagebreak header='Gallachalzie' n='141'>
<lb>underwritten were &illegible; by Hector McNeill
<lb> of Gallachalzie of the late Marquis of Argyle and
 
<text>
 
<fsLib>
 
<fs type=person>
 <f name=place-of-birth>
 
 <f name=date-of-birth>
 
 <f name=persName>
  <fs type=name-structure id=AEA1 instance=s1>
   <f name=forename<str>Archibald</str></f>
   <f name=rank>
   <f name=origin><str>Argyle</str></f>
    <vAlt>
     <sym value='earl'>
     <sym>value='marquis'>
     </vAlt>
    </f>
   </fs>
  </f>
 <f name=place-of-birth>
 
  </f>
 </fs>
<fs type=person>
 
 
 </fs>
 
 
</fsLib>
 
  ]]>
</eg>
-->
 <!-- end of deleted section -->
 </p><p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id="DNDPER" n="Personal names" file="teind2"><tagDecl tagDoc="PERSNAME"/><tagDecl tagDoc="SURNAME"/><tagDecl tagDoc="FORENAME"/><tagDecl tagDoc="GENNAME"/><tagDecl tagDoc="NAMELINK"/><tagDecl tagDoc="ADDNAME"/><tagDecl tagDoc="ROLENAME"/></dtdFrag><?tei:EOF p2ndper.odd ??>
<?tei:SOF p2ndplac.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ndplac.odd,v $
    * Revision 1.6  1998/02/01 17:56:37  tei
    * fix log keyword
    *
    * Revision 1.5  98/02/01  17:45:38  tei
    * make examples parse somehow
    * 
    * Revision 1.4  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.3  1994/04/01  16:25:55  msmcq
    * Changes while validating DTDs
    * --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : normalize caps in headings              --><!-- 94-03-31 : MSM : disambiguate TERM, Q                    --><!-- 94-03-28 : MSM : correct xref to ndplr(e)                --><!-- 94-03-28 : MSM : Added RCS id                            --></p></div2><div2 id="NDPLAC" name="Ilocano" ref="Y"><head>Place Names</head><p>Like other proper nouns or noun phrases used as names, place names
can simply be marked up with the <gi tei="yes">rs</gi> element, or with the
<gi tei="yes">name</gi> element.For cartographers and historical geographers,
however, the component parts of a place name provide important
information about the relation between the name and some spot in space
and time. They also provide importance evidence in historical
linguistics.  For such applications and others in which the internal
structure of a place name is to be encoded, the <gi tei="yes">placeName&gt;</gi>
element and its subcomponents should be used.
 
<tagList style="one-line"><tagDesc tagDoc="PLACNAME"/><tagDesc tagDoc="SETTLE"/><tagDesc tagDoc="REGION"/><tagDesc tagDoc="COUNTRY"/><tagDesc tagDoc="BLOC"/><tagDesc tagDoc="GEOGNAME"/><tagDesc tagDoc="GEOG"/><tagDesc tagDoc="DISTANCE"/><tagDesc tagDoc="OFFSET"/></tagList>
 </p><p>As members of the <ident tei="yes" type="class">names</ident> class, all these
elements share the following attributes:
 
<adList classDoc="NAMES" atts="key reg"/>
 </p><p>Additionally, all of the above elements
are members of the class <ident tei="yes" type="class">placePart</ident>, and
thus share the following attributes:
 
<adList classDoc="PLACPART" atts="type full"/>
 <!-- key and reg are inherited by pname from name -->
 </p><p>Like the <gi tei="yes">persName</gi> element discussed in section <xref target="NDPER"/>, the <gi tei="yes">placeName</gi> element may be regarded simply
as an abbreviation for the tags <tag compl="full" tei="yes">name type=place</tag> or <tag compl="full" tei="yes">rs
type=place</tag>. The following encodings are thus equivalent:
<note source="auth" place="display" anchored="Y">Strictly, a suitable value such as <code tei="yes" type="frag">figurative</code> should be
added to the two place names which are presented periphrastically in
the second example here, in order to preserve the distinction
indicated by the choice of <gi tei="yes">rs</gi> rather than <gi tei="yes">name</gi> to
encode them in the first version.</note>
 
<eg><![CDATA[ 
After spending some time in our
<rs type=place key=NY1>modern
  <name type=place key=BA1>Babylon</name>
</rs>,
<name type=place key=NY1>New York</name>,
I have proceeded to the
<rs type=place key=PH1>City of Brotherly Love</rs>.
 
After spending some time in our
<placeName key=NY1>modern
  <placeName key=BA1>Babylon</placeName>
</placeName>,
<placeName key=NY1>New York</placeName>,
I have proceeded to the
<placeName key=PH1>City of Brotherly Love</placeName>.
 ]]></eg><!-- from letter from 'JK' found in Poulson's Daily Advertiser --><!-- 8 October, 1835, -->
 </p><p>As indicated above, the <gi tei="yes">placeName</gi> may simply contain a
character string and its <att tei="yes">type</att> attribute may be used to
provide a sub-categorization of place names. Alternatively, it may
contain more detailed sub components. A place name may be analysed in
several different ways: as a geo-political unit, using a hierarchy of
descriptive names (see section <xref target="NDPLGU"/>); in terms of
geographic features such as mountains and rivers (see section <xref target="NDPLGF"/>); relative to other place names (see section <xref target="NDPLR"/>.
 
 </p><div3 id="NDPLGU" name="subsection" ref="Y"><head>Geo-political Place Names
 </head><p>A place name is sometimes given as sequence of
geo-political or administrative units, often arranged in
ascending sequence according to their size or administrative
importance, for example: <q>Rochester, New York</q>, or as a single
such unit, for example <q>Belgium</q>. The more detailed component
elements listed above (<gi tei="yes">settle</gi> for a settlement, such as a
village, town or city; <gi tei="yes">region</gi> for any administrative unit
such as a county, parish or state; <gi tei="yes">country</gi> for a politically
recognized national entity; or <gi tei="yes">bloc</gi> for any grouping of such
entities) have been chosen for their generality of application. They
may be tailored more closely to project- and
culture-specific needs by specifying appropriate values in their
respective <att tei="yes">type</att> attributes, as in the following example:
 
<eg><![CDATA[<placeName key=RNY1>
  <settlement type=city>Rochester</settlement>,
  <region type=state>New York</region>
</placeName>
 
<placeName key=LSEA1>
  <country type=nation>Laos</country>,
  <bloc type=sub-continent>Southeast Asia</bloc>
</placeName>
 ]]></eg>
 <!-- <p>When place names which are given in terms of a single --><!-- geo-political unit, the lower-level elements --><!-- (<gi>settlement</gi>, <gi>region</gi>, <gi>country</gi>, --><!-- <gi>bloc</gi>) may be used and the <gi>gu</gi> element --><!-- dispensed with as in: --><!-- Not without serious damage to your content model it cant!  -->
 </p><p>Note that, even in the case where only one of these component place
name elements is used, the <gi tei="yes">placeName</gi> element must still be
present.
 
 
<eg><![CDATA[I'd rather be in
<placeName>
<settlement key=RNY1 type=city>Rochester</settlement>
</placeName>
than any other place I know.]]></eg>
 
 </p></div3><div3 id="NDPLGF" name="subsection" ref="Y"><head>Geographic Names
 </head><p>Places may also be named in terms of geographic features such as
mountains, lakes or rivers, independently of geo-political units. The
<gi tei="yes">geogName</gi> is provided to mark up such names, as an alternative
to the <gi tei="yes">placeName</gi> element discussed above. It contains a
sequence of phrase level elements, optionally extended by the following
special element:
<tagList style="one-line"><tagDesc tagDoc="GEOG"/></tagList>
 </p><p>For example:
 
<eg><![CDATA[  <geogName key=MIRI1 type=river>
    Mississippi River
  </geogName>
 ]]></eg>
 </p><p>Where the <gi tei="yes">geog</gi> element is used to characterize the kind of
geographic feature being named, the <gi tei="yes">name</gi> element will generally
also be used to mark the associated proper noun or noun phrase:
 
<eg><![CDATA[  <geogName key=MIRI1 type=river>
    <name>Mississippi</name>
    <geog>River</geog>
  </geogName>]]></eg>
 
A more complex example, showing a variety of practices, follows:
 
<eg><![CDATA[The isolated ridge separates two great corridors which run from
<name key=GLCO1 type=place>Glencoe</name> into
<geogName key=GLET1 type=glen>
  <geog reg='glen'>Glen</geog>
  <name>Etive</name>
</geogName>, the
<geogName key=LAGA1 type=hill>
  <geog lang='gaelic' reg='sloping hill face'>Lairig</geog>
  <name>Gartain</name>
</geogName> and the
<geogName key=LAEI1 type=hill>
  <geog lang='gaelic' reg='sloping hill face'>Lairig</geog>
  <name>Eilde</name>
</geogName>]]></eg>
 
 </p></div3><div3 id="NDPLR" name="subsection" ref="Y"><head>Relative Place Names
 </head><p>All the place name specifications so far discussed are
<term rend="noindex">absolute</term>, in the sense that they define only
one place.  A
place may however be specified in terms of its relationship to another
place, for example <q>10 miles northeast of Paris</q> or <q>near the top
of Mount Sinai</q>. These <term>relative place names</term> will contain
a place name which acts as a referent (e.g. <q>Paris</q> and <q>Mount
Sinai</q>). They will also contain a word or phrase indicating the the
position of the place being named in relation to the referent
(e.g. <q>the top of</q>, <q>north of</q>). A distance, possibly only
vaguely specified, between the referent place and the place being
indicated may also be present (e.g. <q>10 miles</q>, <q>near</q>)
 </p><p>Relative place names may be encoded using the following elements in
combination with either a <gi tei="yes">placeName</gi> or a <gi tei="yes">geogName</gi>
element.
 
<tagList style="one-line"><tagDesc tagDoc="OFFSET"/><tagDesc tagDoc="DISTANCE"/></tagList>
 
 
Some examples of relative place names are:
 
<eg><![CDATA[<placeName key=NRPA1>
 <offset>near the top of
  </offset>
  <geogName>
     <geog>Mount</geog>
     <name>Sinai</name>
  </geogName>
</placeName>
 
<placeName key=NEPA1>
  <distance>10 miles</distance>
  <offset>north of</offset>
  <settlement type=city>Paris
  </settlement>
</placeName>
 ]]></eg>
 <!--
  Where appropriate, the
internal structure of the distance component may be tagged using the
<gi>measure</gi> elements described in  section <xref type='div2'
target=NDMEAS>, as follows:
 
<eg>
<![ CDATA [
<relplace key=NRTA1>
  <distance type=measured>
    <measure type=length>
      <num type=cardinal value='2'>2</num>
      <unit>miles</unit>
    </measure>
  </distance>
  <offset reg='east'>
    east of
  </offset>
  <settlement type=city>
      Tel Aviv
  </settlement>
</relplace>
]]>
</eg>
 
<p>Some place names combine the distinctive place name
types discussed above, for example:
 
<eg>
<![ CDATA[
<relplace key=LIIT1>
  <distance type=measured>
     <measure type='length'>
       <num type='cardinal' value='2'>2</num>
       <unit type=area>blocks</unit>
     </measure>
   </distance>
   <offset reg='west'>west of</offset>
   <name>Little Italy</name>
</relplace>
]]>
</eg>
 
<p>Before concluding, it is worth considering a number of
substantive issues which need to be considered locally before
tagging a particular document. Firstly, the tags provided here
are sufficiently powerful to handle a wide variety of
geographical place names whose internal structure varies
considerably. The same flexibility, however, allows the encoder
to treat the same geographical place name differently. Thus,
the following variations on <q>The Mississippi River</q> are all
valid but might make local processing different or error prone
if all were implemented in the same document. The principal
problem is that the keys which associate the place names with some
particular place all refer to something slightly different:
 
<eg><![CDATA[
 
<rs key=pln15 type='place'>
  The Mississippi River
</rs>
 
<name key=pln15 type='place'>
  The Mississippi River
</name>
 
<rs key=pln15 type='place'>
The
  <name>Mississippi
  </name>
  <geog>River</geog>
</rs>
 
]]>
</eg>
 
Suffice it to say here as elsewhere in this volume, the encoder is urged
to
be as consistent as possible in applying encoding solutions to a
given machine-readable text or project.
-->
 </p><p>The internal structure of place names is like that of
personal names - complex and subject to an enormous amount of variation
across time and different cultures. The recommendations in this section
will be adequate for a majority of users and applications. They may
not, however, satisfy the most specialized inquiries and/or
applications in which case it is recommended that the internal
structure of place names be represented using feature structures<xref target="FS"/>
.
 </p><p>The elements discussed in this section are formally defined as
follows:
 
<dtdFrag id="DNDPLAC" n="Names for places" file="teind2"><tagDecl tagDoc="PLACNAME"/><tagDecl tagDoc="SETTLE"/><tagDecl tagDoc="REGION"/><tagDecl tagDoc="COUNTRY"/><tagDecl tagDoc="BLOC"/><tagDecl tagDoc="OFFSET"/><tagDecl tagDoc="DISTANCE"/><tagDecl tagDoc="GEOGNAME"/><tagDecl tagDoc="GEOG"/></dtdFrag><?tei:EOF p2ndplac.odd ??>
<?tei:SOF p2ndorg.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    **
    * $Log: p2ndorg.odd,v $
    * Revision 1.3  1998/02/01 17:45:38  tei
    * make examples parse somehow
    *
    * Revision 1.2  98/01/28  12:01:27  lou
    * LB changes of Jan 1998 and RCS keywords
    * 
    *--><!-- 5 Jan 95 : LB : corrected typos in egs --></p></div3></div2><div2 id="NDORG" name="Ilocano" ref="Y"><head>Organization names</head><p>Like names of persons or places, organization names can be marked as
referent strings or as proper names with the <gi tei="yes">rs</gi> and
<gi tei="yes">name</gi> elements.  For certain applications it may be desirable
to mark the component parts of an organization. In some historical and
social scientific studies, for example, the component parts of an
organization names may give crucial clues which help to  characterizing
the organization in terms of its geographical location, ownership,
likely number of employees, management structure etc.  The elements
discussed in this section are recommended for this purpose and include:
 
<tagList style="one-line"><tagDesc tagDoc="ORGNAME" atts="type key reg"/><tagDesc tagDoc="ORGTITLE" atts="type reg"/><tagDesc tagDoc="ORGTYPE" atts="type reg"/><tagDesc tagDoc="ORGDIVN" atts="type reg"/></tagList>
 </p><p>The <gi tei="yes">orgname</gi> element should be used when it is desirable to
mark an organization name irrespective of whether or not its components
are also to be marked. In effect the <gi tei="yes">orgname</gi> element is a
special case of a <gi tei="yes">name</gi> and thus of an <gi tei="yes">rs</gi> element.
Consequently, the following examples are synonymous, though the last is
preferred:
 
<eg><![CDATA[About a year back, a question of considerable interest was
agitated in the <rs type=org key=PAS1>Pennsyla. Abolition Society</rs>.
 
About a year back, a question of considerable interest was
agitated in the <rs type=org key=PAS1><name>Pennsyla. Abolition 
Society</name</rs>.
 
About a year back, a question of considerable interest was
agitated in the <name type=org key=PAS1>Pennsyla. Abolition Society</name>.
 
About a year back, a question of considerable interest was
agitated in the <orgname key=PAS1 type=voluntary
reg="Pennsylvania Abolition Society">Pennsyla. Abolition Society</orgname>.]]></eg><!-- From the Diary of Thomas Pym Cope -->
 
Like the <gi tei="yes">rs</gi> and <gi tei="yes">name</gi> elements, the <gi tei="yes">orgname</gi>
element has a <att tei="yes">key</att> attribute with which an external
identifier such as a database key can be assigned to the organization
name. It also has a <att tei="yes">type</att> attribute with which the
organization named in the expression can be described, and a
<att tei="yes">reg</att> attribute with which the organization name can be
presented in a regularized form.
 </p><p>The <gi tei="yes">orgtitle</gi> element is used to mark the expression
which provides the proper name component of an organization name
for example:
 
<eg><![CDATA[ 
Mr Frost will be able to earn an extra fee from 
<orgname type=media key=BSB1>
  <orgtitle type=acronym>BSkyB</orgtitle>
</orgname> 
rather than the 
<orgname type=media key=BBC1>
   <orgtitle type=acronym 
             reg='British Broadcasting Corporation'>
   BBC</orgtitle>
</orgname>
 ]]></eg>
 </p><p>Where personal names are encountered as component parts of an
organization's title, as in <q>Ernst &amp; Young</q>, these may be
tagged with the appropriate personal name elements as discussed
in <xref target="NDPER" type="div2"/>. Examples include:
 
 
<eg><![CDATA[<orgname type='accountancy partnership' key=EY1>
<orgtitle>
  <persName><surname>Ernst</surname></persName> &
  <persName><surname>Young</surname></persName>
</orgtitle>
</orgname>]]></eg>
 </p><p>Organization names may also contain within them place names
which, in some applications, may yield vital clues as to the
organization's location and or sphere of influence. These
components should be tagged with the approprate place name tags<xref target="NDPLAC" type="div2"/>
. Examples include:
 
<eg><![CDATA[A spokesman from 
<orgname type=computers key=IBM1>
  <orgtitle reg='International Business Machines'>IBM</orgtitle> 
  <placeName><country reg='United Kingdom' key=UNKI1>UK
  </country></placeName>
</orgname> said...
 
The feeling in 
<country type=nation key=CAN1>Canada</country>
is one of strong aversion to the 
<orgname type=government key=USG1>
  United States  Government
</orgname>, and of predilection for self-government
under the 
<orgname type=government 
      reg='British monarchy'>English Crown</orgname>
 ]]></eg><!-- Anthony Trollope, North America, Penguin ed., 51 -->
 
 </p><p>The <gi tei="yes">orgtype</gi> element is used to mark those components
of an organization name which indicate something about the
structure or function of the organization. Examples include:
 
<eg><![CDATA[<orgname type='utility company' key=WWPC1>
  <name type=state>Washington</name>
  <orgtype type=function>Water Power</orgtype> 
  <orgtype reg='incorporated' type=structure>Inc.</orgtype>
</orgname>
 
THE TICKET which you will receive herewith has been formed by
the 
<orgname type=political reg='Whig party' key=WHI1>
  <orgtitle>Democratic Whig</orgtitle> 
  <orgtype type=function>Party</orgtype>
</orgname> after the most careful deliberation,
with a reference to all the great objects of NATIONAL, STATE,
COUNTY and CITY concern, and with a single eye to the 
<emph>Welfare and Best Interests of the Community</emph>.
 ]]></eg>
 
 </p><p>Organizational names may also be specified hierarchically
particularly where the named organization is itself a department
or a branch of a larger organizational entity.  <q>The
Department of Modern History, Glasgow University</q> is an
example. The <gi tei="yes">orgdivn</gi> element is recommended wherever
it is desirable to isolate the independent levels of an
organizational hierarchy that are specified in an organization name. 
Examples include:
 
<eg><![CDATA[<orgname type=academic key=DMHGU1>
  <orgdivn type=department>
     Department of Modern History
  </orgdivn>,
  <name type=city>Glasgow</name> 
  <orgtype type=function>University</orgtype>
</orgname>
 ]]></eg>
 </p><p>Although highly flexible, the mechanisms discussed here for
marking the components of organization names will not cater for
every processing need or organizational name that is
encountered. Where the internal structure of organization names
is highly complex, where name components are particularly
ambiguous, or where it is important to indicate the assumptions
made in the evaluation of an organization name, then feature
structure notation is recommended <xref target="FS"/>
 </p><p>The formal declaration of the elements discussed in this section include:
 
<dtdFrag id="DNDORG" n="Organization names" file="teind2"><tagDecl tagDoc="ORGNAME"/><tagDecl tagDoc="ORGTITLE"/><tagDecl tagDoc="ORGTYPE"/><tagDecl tagDoc="ORGDIVN"/></dtdFrag><?tei:EOF p2ndorg.odd ??>
<?tei:SOF p2nddate.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $Log: p2nddate.odd,v $
# Revision 1.4  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
    *--><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2nddate.odd,v $
# Revision 1.4  1998/01/28  12:01:27  lou
# LB changes of Jan 1998 and RCS keywords
#
# Revision 1.3  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
# --><!-- Revisions:                                               --><!-- 5 jan 98 : LB : fix typos in egs --><!-- 94-04-07 : MSM : normalize caps in headings              --><!-- 94-04-07 : MSM : Added RCS id                            --><!-- 94-03-31 : MSM : disambiguate TERM, Q                    --><!-- 94-03-31 : MSM : cosmetics                               --><!-- 6 Mar 94 : LB extensive revision: introduce              --><!--            dateStruct, timeStruct                        --><!-- 93-06-03 : MSM : rename event as relEvent as per DGr     --><!-- Lou, in order for this section to make sense, you need   --><!-- to introduce the <gi>time</gi> and <gi>timerange</gi>    --><!-- elements in the core where you currently discuss         --><!-- dates.  the tags are identical to <gi>date</gi> and      --><!-- <gi>daterange</gi> but for clock time as opposed to      --><!-- calendar dates.                                          -->
 
 </p></div2><div2 id="NDDATE" name="Ilocano" ref="Y"><head>Dates and Time</head><p>The following elements for the encoding of dates and times were
introduced in section <xref target="CONADA"/>:
 
<tagList style="one-line"><tagDesc tagDoc="DATE" atts="calendar value certainty"/><tagDesc tagDoc="TIME" atts="zone value type"/></tagList>
 </p><p>While adequate for many applications, these elements do not allow
for the representation of the internal structure of expressions
indicating dates or times, which may however be of importance for the
correct interpretation of such expressions, or for certain kinds of
analytic applications. In this section, we introduce the following
special-purpose elements, for use when the internal structure of a
temporal expression is to be encoded:
 
<tagList style="one-line"><tagDesc tagDoc="DATESTRU"/><tagDesc tagDoc="TIMESTRU"/></tagList>
 </p><p>Two types of temporal expressions are envisaged for dates and
times: absolute and relative. An <term>absolute temporal
expression</term> is composed of a sequence of the following elements,
possibly interspersed with character data:
 
<tagList style="one-line"><tagDesc tagDoc="DAY"/><tagDesc tagDoc="WEEK"/><tagDesc tagDoc="MONTH"/><tagDesc tagDoc="YEAR"/><tagDesc tagDoc="SECOND"/><tagDesc tagDoc="MINUTE"/><tagDesc tagDoc="HOUR"/><tagDesc tagDoc="OCCASION"/></tagList>
 </p><p>A <term>relative temporal expression</term> describes a date or time
with reference to some other (absolute) temporal expression, and thus
contains the following elements in addition to those listed above:
 
<tagList style="one-line"><tagDesc tagDoc="DISTANCE"/><tagDesc tagDoc="OFFSET"/></tagList>
 </p><p>As members of the class <ident tei="yes" type="class">temporalExpr</ident>
(temporal expression)
these elements all share the following attributes:
 
<adList classDoc="TEMPEXP" atts="value type reg"/>
 
 </p><div3 id="NDDATEA" name="subsection" ref="Y"><head>Absolute Dates and Times
 </head><p>An absolute temporal expression which is a date will contain only a
sequence of <gi tei="yes">day</gi>, <gi tei="yes">month</gi> <gi tei="yes">week</gi>, <gi tei="yes">year</gi>
or <gi tei="yes">occasion</gi> elements, as in the following examples:
 
<eg><![CDATA[The university's view of American affairs produced
a stinging attack by Edmund Burke in the Commons
debate of
<dateStruct value='26-10-1775'>
  <day value='26'>26</day>
  <month value='10'>October</month>
  <year value='1775'>1775</year>
</dateStruct>]]></eg><!-- The History of the University of Oxford, vol v, 178 -->
 
Component elements of a <gi tei="yes">dateStruct</gi> may be repeated, provided
that only a single  temporal expression is intended:
 
<eg><![CDATA[<dateStruct value='14-05-1993'>
  <day type=name>Friday</day>,
  <day type=number>14</day>
  <month>May</month>
  <year>1993</year>
</dateStruct>]]></eg><!-- the headline on the Independent Newspaper on that day -->
 </p><p>The <gi tei="yes">occasion</gi> element may be used for any component of a
temporal expression which is given in terms of a named event, such as
a public holiday for dates, or a named time such as <q>tea time</q> or
<q>matins</q>:
 
<eg><![CDATA[In New York,
  <dateStruct value='1-1'>
    <occasion type=holiday>New Years Day</occasion>
  </dateStruct> is the quietest of holidays,
  <dateStruct value='4 July'>
    <occasion type=holiday>Independence Day</occasion>
  </dateStruct>
the most turbulent.]]></eg>
 </p><p>These components may be applied to dates using any calendar system
using  subcomponents equivalent to those listed above:
<eg><![CDATA[<title>Le Vieux Cordelier:
Journal r&eacute;dig&eacute; par Camille Desmoulins</title>,
<dateStruct type=Revolutionary value='03-02-1794'>
   <day type=name>Quintidi</day>
   <month>Pluviose</month>
   <week value=2>2e d&eacute;cade</week>,
   <year value=2>l'an 2 de la R&eacute;publique Indivisible</year>
</dateStruct>]]></eg><!-- NB put acutes in same example in week.tag --><!-- Date headline from Le Vieux Cordelier of that date --><!-- Thanks to T. Munck for providing the above example -->
 </p><p>Absolute temporal expressions denoting times which are given
in terms of seconds, minutes, hours or of well defined events
(e.g. <q>noon</q>, <q>sunset</q>) may similarly be represented using
the <gi tei="yes">timeStruct</gi> element:
 
<eg><![CDATA[The train leaves for Boston at
  <timeStruct type='24hour' zone=EST>
    <hour>13</hour>:<minute>45</minute>
   </timeStruct>
 
At <timeStruct>
     <occasion>sunset</occasion>
   </timeStruct> we walked to the beach.
 
The train leaves for Boston at
  <timeStruct type='descriptive' zone=EST value='13:45'>
     a quarter of <hour reg='1400'>two</hour>
  </timeStruct>]]></eg><!-- maybe should add lang=AmE to last?! -->
 </p><p>The <att tei="yes">type</att> attribute may be used to distinguish sub-types of
component elements (for example, months or days presented as words or
as numbers) or to provide additional information about the function of
this particular component (for example, to distinguish types of
<gi tei="yes">occasion</gi>).
The <att tei="yes">value</att> and <att tei="yes">reg</att> attributes
are both used to provide a standardized or regularized form of the
content of an element. The distinction is that the value specified by
the <att tei="yes">reg</att> attribute is simply that chosen as a convenient way
of grouping together a number of variant forms, whereas that specified
for the <att tei="yes">value</att> attribute must always be given in some
application-dependent standard form, described in the <gi tei="yes">stdVals</gi>
element of the TEI header.
 </p><p>For example:
 
<eg><![CDATA[<dateStruct value='09-06-1807'>
  <month type=name value=06>June</month>
  <day type=number value=09>9th</day>
</dateStruct>:
The period is approaching which will terminate my
present copartnership. On the
<dateStruct value='01-01-1808'>
  <day type=number value=01>1st</day>
  <month type=name value=01 reg='January'>Jany.</month>
</dateStruct> next, it expires by its own limitation.]]></eg><!-- Philadelphia Merchant: The Diary of TP Cope, 210 -->
 
 </p></div3><div3 id="NDDATER" name="subsection" ref="Y"><head>Relative Dates and Times
 </head><p>As noted above, relative dates and times such as <q>in the Two
Hundredth and First Year of the Republic</q>, <q>twenty minutes before
noon</q>, and, more ambiguously, <q>after the lamented death of the
Doctor</q> or <q>an hour after the game</q> have two distinct
components. As well as the absolute temporal expression or event to
which reference is made (e.g. <q>noon</q>, <q>the game</q>, <q>the
death of the Doctor</q> <q>[the foundation of] the Republic</q>), they
also contain a description of the <soCalled>distance</soCalled>
between the time or date which is indicated and the referent
expression (e.g. <q>the Two Hundredth and First Year</q>, <q>twenty
minutes</q>, <q>an hour</q>); and (optionally) an
<soCalled>offset</soCalled> describing the direction of the distance
between the time or date indicated and the referent expression
(e.g. <q>of</q> implying after, <q>before</q>, <q>after</q>).
 </p><p>The elements <gi tei="yes">distance</gi> (or <gi tei="yes">measure</gi>) and
<gi tei="yes">offset</gi> are used to encode these last two components within a
<gi tei="yes">dateStruct</gi> or <gi tei="yes">timeStruct</gi>. The absolute temporal
expression contained within the relative expression may be encoded
using a <gi tei="yes">occasion</gi> element, or by a nested <gi tei="yes">dateStruct</gi>
or <gi tei="yes">timeStruct</gi>, or by a simple <gi tei="yes">date</gi> or
<gi tei="yes">time</gi>. This allows for endlessly recursive structures such as
<q>the third Sunday after the first Monday before Lammastide in the
fifth year of the King's second marriage ...</q> --- but so does
natural language.
 
In the following examples, the <att tei="yes">reg</att> attribute has been used
to simplify processing of variant forms of expression:
 
<eg><![CDATA[<dateStruct value='11-12-1786'>
     <distance reg='14 days'>A fortnight</distance
     <offset>before</offset>
     <dateStruct>
       <occasion type='holiday'>Christmas</occasion>
       <year>1786</year>
     </dateStruct>
</dateStruct>
 
I reached the station
<timeStruct value='14:15'>
 <distance exact=N reg='30 minutes'>
   about a half hour</distance>
 <offset>after</offset>
 <occasion value='13:45'>
   the departure of the afternoon train to Boston</occasion>
</timeStruct>]]></eg>
 </p><p>In the following example, the <att tei="yes">exact</att> attribute has been
used to indicate a lack of precision in the distance stated:
 
<eg><![CDATA[In practice, festival candles are lit
<timeStruct>
  <distance exact=N>just</distance>
  <offset>before</offset>
  <occasion reg='evening'>sundown</occasion>
</timeStruct>
 ]]></eg>
 
 </p><p>In the following example, a nested <gi tei="yes">dateStruct</gi> element is
used to show that <q>my birthday</q> and the cited date are parts of
the same temporal expression, and hence to disambiguate the phrase
<q>A week before my birthday on 9th December</q>:
 
<eg><![CDATA[<dateStruct value='02-12'>
  <distance>A week</distance>
  <offset>before</offset>
  <dateStruct value='09-12'>
    <occasion>my birthday</occasion>
    on <day>9th</day><month>December</month>
  </dateStruct>
</dateStruct>]]></eg>
 
The alternative reading of this phrase would be encoded as follows:
<eg><![CDATA[<dateStruct value='09-12'>
  <distance>A week</distance>
  <offset>before</offset>
  <occasion>my birthday</occasion>
  on <day>9th</day><month>December</month>
</dateStruct>]]></eg>
 <!-- really dont want to keep distance : shd be same as measure -->
 </p><p>Where more complex or ambiguous expressions are involved, and
where it is desirable to make more explicit  the interpretive
processes required, the feature
structure notation described in chapter  <xref target="FS"/> is
recommended.  Consider, for example, the following
temporal expression which occurs in the <title>Scottish Temperance
Review</title> of August 1850, referring  to the summer  holiday known
in Glasgow simply as <q>the Fair</q>:
 
<eg><![CDATA[Not only is the city, <date ana=GF50>during the Fair</date>, a
horrible nucleus of immorality and wickedness; it sends our
multitudes to pollute and demoralize the country.]]></eg>
 </p><p>For the definition of the <att tei="yes">ana</att> attribute, see chapter<xref target="AI"/>
. It is used here to link the temporal phrase with an
interpretation of it. Like most traditional fairs and market days, the
Glasgow Fair was established by local custom and could vary from year
to year.  Consequently, in order to provide such an interpretation, it
is necessary to drawn upon additional information which may or may not
be located in the particular text in question. In this case, it is
necessary at least to know the spatial and temporal context (year and
place) of the fair referred to.
These and other features required for
the analysis of this particular temporal
expression may be combined together as one feature
structure of type <code tei="yes" type="frag">date-analysis</code>:
 
<eg><![CDATA[<fs type=date-analysis id=GF50>
<f name=event><str>the Fair</str></f>
<f name=place><str>Glasgow</str></f>
<f name=year><nbr value=1850></f>
<f name=from-value><str>08-08-1850</str></f>
<f name=to-value><str>19-09-1850</str></f>
</fs>]]></eg>
 
 
The elements described in this section are formally defined as follows:
 
<dtdFrag id="DNDDATE" n="Date components" file="teind2"><tagDecl tagDoc="DATESTRU"/><tagDecl tagDoc="DAY"/><tagDecl tagDoc="WEEK"/><tagDecl tagDoc="MONTH"/><tagDecl tagDoc="YEAR"/><tagDecl tagDoc="OCCASION"/><tagDecl tagDoc="TIMESTRU"/><tagDecl tagDoc="SECOND"/><tagDecl tagDoc="MINUTE"/><tagDecl tagDoc="HOUR"/><commDecl>offset and distance were defined above</commDecl></dtdFrag>
 <?tei:EOF p2nddate.odd ??>
</p></div3></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/fullodd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2nd.odd ??><!-- 20 Names and Dates ... --><?tei:SOF p2gd.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2gd.odd,v $
    * Revision 1.10  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.9  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.8  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.7  1994/03/27  16:30:14  lou
    * semifinal check
    * 
    * Revision 1.5  1993/12/20  10:03:03  lou
    * fixed id
    * 
    * Revision 1.4  1993/09/22  18:44:59  msmcq
    * Version as of publication of GD
    * --><!-- Revisions:                                               --><!-- 13 jan 98 : LB : fix typos in egs --><!-- 7 jan 98 : LB : VONT shd be VIENNENT --><!-- 94-04-07 : MSM : punctuation in head                     --><!-- 13 mar 94 : LB : applied mods from DTB/DD (twice) --><!-- 19 dec 93: LB : changed id on first dtd frag DAI->Dgd    --><!-- 93-09-17 : MSM : SGML fixes to exx                       --><!-- 93-09-17 : MSM : Expand discussion of Gallachalzie       --><!-- 93-09-17 : MSM : revise for publ                         --><!-- 93-09-16 : MSM : modify Argyll graph                     --><!-- 93-09-15 : MSM : quick revisions                         --><!-- 1 aug 93 : LB: various minor fixes to tagdocs            --><!--            changed title (was just 'Graphs')             --><!--            added DTD overall schema                      --><!-- 93-07-22 : DTL : add Sasine ex from DG                   --><!--                  minor revs based on new TAGDOCs         --><!-- 93-07-20 : DTL : add family tree, transducer exx         --><!--                  add definitions of path, connected      --><!-- 93-07-19 : DTL : change title to "Graphs"                --><!--                  make other changes suggested at Eynsham: --><!--                  single tagset for graphs, digraphs and  --><!--                   networks: GRAPH, NODE, ARC             --><!--                  replace specialized formatting          --><!--                   attributes by rend=                    --><!--                  eliminate LABEL tag, use attributes to  --><!--                   point to feature structures, etc.      --><!--                  use type= attribute to distinguish types --><!--                   of graphs                              --><!--                  change madeup exx to smthg realler      --><!--   8 Mar 93 : CMSMcQ : merge old 44.8 and 44.9, revise    --><!--                       intro, retitle as per chapter ST   --><!--                       ('nets')                           --><!--  29 Jul 92 :  DTL : Corrected ODD tagging, per LB.       --><!--  24 Jul 92 :  DTL : Renumber as p2.448.  Make other      --><!--                     minor changes.                       --><!--  21 Jul 92 :  DTL : Make minor corrections.              --><!--  14 Jul 92 :  DTL : Change ordering= to ord= on < tree > --><!--  Include attribute names (e.g. ord=) in example tags,    --><!-- even when they can be omitted.  Make minor               --><!-- corrections.  Change section numbers to p2.449, etc.     --><!-- Remove TAGDOC for  < label > , and add cross-reference   --><!-- to section on  < list > , in chapter 23, where           --><!--  < label >  is defined.                                  --><!--  10 Jul 92 :  DTL : Complete first draft, except for     --><!-- section on linguistic trees, based on AI1 working        --><!-- paper entitled "Encoding graphs, digraphs and trees",    --><!-- Nov. 1991, and suggestions from CMSMcQ on TEI-TECH in    --><!-- June 1992.                                               --><!--  Changes from ver. 1.14 of LING DTD:                     --><!--  Rename  < i.node >  as  < iNode > .                     --><!--  Rename adjac.to= as adjacTo=.                           --><!--  Rename adjac.from= as adjacFrom=.                       --><!--  Restore order= to ATTLIST of  < graph > ,  < digraph >  --><!--   and  < tree >.                                         --><!--  Restore size= to ATTLIST of < graph > and < digraph >.  --><!--  Restore degree= to ATTLIST of  < vertex >               --><!--  Restore inDegree= and outDegree= to ATTLIST of < node >. --><!--  Restore outDegree= to ATTLIST of < root > and < iNode >. --><!--  Add type= to ATTLIST of  < node >.                      --><!--  Add arity= to ATTLIST of  < tree > .                    --><!--  Add =partial as possible value for ordering= on < tree >. --><!--  Change content model of  < edge >  to permit at most    --><!--   one  < label >;                                        --><!--   add label= to ATTLIST of  < edge >;                    --><!--   change from= and to= to end1= and end2= in ATTLIST     --><!--    of  < edge >.                                 --><!--  Replace  < edge >  with  < arc >  as possible content   --><!--   of  < digraph >;                                       --><!--  ATTLIST of < arc > contains label=, from= and to=.      --><!--  Add attributes for drawing graphs, digraphs and trees   --><!--    as follows:                                           --><!--    vrtxFrame=, edgeSpec= to ATTLIST of  < graph >;       --><!--    nodeFrame=, arcSpec= to ATTLIST of  < digraph >       --><!--     and  < tree >;                                       --><!--    frame= to ATTLIST of < vertex >, < node >,            --><!--     < root >, < iNode > and < leaf >;                    --><!--    spec= to ATTLIST of  < edge >,  < arc >,  < root >    --><!--     and  < iNode >.                                      --><!-- P2.GD :  Networks, Graphs, Digraphs and Trees            --><!-- On title change, see next comment.            (DTL)      --><!-- < div1 id=GD n=23>                                       --><!-- < head>Networks, Graphs, Digraphs, and Trees< /head>     --><!-- EDITORS: How about changing id value to GR? (DTL)        --><!-- Taken already:  GR = grammar (msm)                       --><div1 id="GD" n="21" name="Faisal" ref="Y"><head>Graphs, Networks, and Trees</head><!-- DTB writes: --><!--   This does not introduce the topic sufficiently well. These --><!-- Guidelines are not about encoding general data structures --><!-- primarily (?), they're about encoding (two words illegible) --><!-- text. So why do we have this stuff? We need to say it was --><!-- motivated by the linguistic stuff, I guess. --><p>Graphical representations are widely used for displaying relations
among informational units because they help readers to visualize those
relations and hence to understand them better.  Two general types of
graphical representations may be distinguished.
 <!-- <note place=foot>The primary responsibility for this chapter --><!-- was borne by the working committee for analysis and --><!-- interpretation, whose members are listed in the front --><!-- matter.  It was drafted by D. Terence Langendoen with --><!-- assistance from Steven Zepp.  The Sasine text example and --><!-- suggested markup was provided by Daniel Greenstein.</note> -->
 
<list type="bullets"><!-- I prefer to think of networks as special types of graphs --><!-- rather than the other way around.  (DTL)                 --><!-- Material deleted                                         --><!-- < item>Networks, that is < term>graphs< /term> and <     --><!-- term>digraphs< /term> (or < term>directed graphs<        --><!-- /term>) in the strictly mathematical sense, which        --><!-- consist of points, called < term>vertices< /term> or <   --><!-- term>nodes< /term>, and lines connecting them, called    --><!-- < term>edges < /term> or < term>arcs< /term>.            --><!-- End material deleted                                     --><item>Graphs, in the strictly mathematical sense, consist
of points, often called <term>nodes</term> or
<term>vertices</term>, and connections among them, called
<term>arcs</term>, or under certain conditions,
<term>edges</term>.  Among the various types of graphs are
<term>networks</term> and <term>trees</term>.  Graphs
generally and networks in particular are dealt with
directly below.  Trees are dealt with separately in
sections <xref target="GDTR"/> and <xref target="GDAT"/>.
 
<note source="auth" place="foot" anchored="Y">The treatment here is largely based on the
characterizations of graph types in <citation><author>Gary Chartrand and
Linda Lesniak</author>, <title>Graphs and Digraphs</title>
(<detail>Menlo Park, CA: Wadsworth, 1986).</detail></citation></note></item><item><term>Charts</term>, which typically plot data in two or more
dimensions, including plots with orthogonal or radial axes, bar charts,
pie charts, and the like.  These can be described using the elements
defined in the additional tag set for figures and graphics; see
chapter <xref target="FT"/>.</item></list><!-- LB inserted following --></p><p>The following DTD fragment shows the overall organization of the
tag set discussed in the remainder of this chapter.
 
<dtdFrag id="DGD" n="Graphs, networks and trees" file="teinet2"><dtdRef dtdFrag="DGDGR"/><dtdRef dtdFrag="DGDTR"/><dtdRef dtdFrag="DGDAL"/></dtdFrag></p><p>This tag set is made available as described in <xref target="STIN"/>; in
a document which uses the markup described in this chapter, the document
type declaration should contain the following declaration for the entity
<ident tei="yes" type="pe">tei.nets</ident>:
 
<eg><![CDATA[<!ENTITY % tei.nets 'INCLUDE'>]]></eg>
 
The entire document type declaration for a document using this
additional tag set together with the prose base might look like this:
<eg><![CDATA[ <!DOCTYPE TEI.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY % tei.prose 'INCLUDE' >
    <!ENTITY % tei.nets  'INCLUDE' >
 ]>]]></eg>
 <!-- end of LB insertion --></p><p>Among the types of qualitative relations often represented by graphs
are organizational hierarchies, flow charts, genealogies, semantic
networks, transition networks, grammatical relations, tournament
schedules, seating plans, and directions to people's houses.  In
developing recommendations for the encoding of graphs of various types,
we have relied on their formal mathematical definitions and on the most
common conventions for representing them visually.  However, it must be
emphasized that these recommendations do not provide for the full range
of possible graphical representations, and deal only partially with
questions of design, layout and placement.</p><div2 id="GDGR" name="Ilocano" ref="Y"><head>Graphs and Digraphs</head><p>Broadly speaking, graphs can be divided into two types:
<term>undirected</term> and <term>directed</term>.  An undirected graph
is a set of <term>nodes</term> (or <term>vertices</term>) together with
a set of pairs of those vertices, called <term>arcs</term> or
<term>edges</term>.  Each node in an arc of an undirected graph is said
to be <term>incident</term> with that arc, and the two vertices which
make up an arc are said to be <term>adjacent</term>.  An directed graph
is like an undirected graph except that the arcs are <term>ordered
pairs</term> of nodes.  In the case of directed graphs, the term
<term>edge</term> is not used; moreover, each arc in an directed graph
is said to be <term>adjacent from</term> the node from which the arc
emanates, and <term>adjacent to </term> the node to which the arc is
directed.  We use the element <gi tei="yes">graph</gi> to encode graphs as a
whole, <gi tei="yes">node</gi> to encode nodes or vertices, and <gi tei="yes">arc</gi> to
encode arcs or edges; arcs can also be encoded by attributes on the
<gi tei="yes">node</gi> element.  These elements have the following descriptions
and attributes:
 
<tagList style="one-line"><tagDesc tagDoc="GRAPH" atts="type label order size"/><tagDesc tagDoc="NODE" atts="label label2 value type                            adjFrom adjTo adj inDegree outDegree                            degree"/><tagDesc tagDoc="ARC" atts="label label2 from to"/></tagList></p><p>Before proceeding, some additional terminology may be helpful.  We
define a <term>path</term> in a graph as a sequence of nodes n1, ..., nk
such that there is an arc from each ni to ni+1 in the sequence.  A
<term>cyclic path</term>, or <term>cycle</term> is a path leading from a
particular node back to itself.  A graph that contains at least one
cycle is said to be <term>cyclic</term>; otherwise it is
<term>acyclic</term>.  We say, finally, that a graph is
<term>connected</term> if there is a path from some node to every other
node in the graph; any graph that is not connected is said to be
<term>disconnected</term>.</p><p>Here is an example of an undirected, cyclic disconnected graph, in
which the nodes are annotated with three-letter codes for airports, and
the arcs connecting the nodes are represented by horizontal and vertical
lines, with 90 degree bends used simply to avoid having to draw diagonal
lines.
 <!--      LAX: Los Angeles                                    --><!--      LVG: Las Vegas                                      --><!--      PHX: Phoenix                                        --><!--      TUS: Tucson                                         --><!--      CIB: Seven Cities of Cibola                         -->
 
<eg rend="skel"><![CDATA[          .---LAX---.
          |         |
         LVG-------PHX---TUS    CIB
 
  Airline Connections in Southwestern USA]]></eg></p><p>Next is a markup of the graph, using <gi tei="yes">arc</gi> elements to encode
the arcs.
 
<eg><![CDATA[<graph type=undirected
       id=CUG1
       label='Airline Connections in Southwestern USA'
       order=5
       size=4>
  <node label=LAX id=LAX degree=2>
  <node label=LVG id=LVG degree=2>
  <node label=PHX id=PHX degree=3>
  <node label=TUS id=TUS degree=1>
  <node label=CIB id=CIB degree=0>
  <arc  from=LAX to=LVG>
  <arc  from=LAX to=PHX>
  <arc  from=LVG to=PHX>
  <arc  from=PHX to=TUS>
  </graph>]]></eg></p><p><!-- The <att>rend</att> attribute on the <gi>graph</gi> element may --><!-- be used  here to encode certain information about how the graph --><!-- is to be drawn. -->The <att tei="yes">label</att> attribute on the <gi tei="yes">graph</gi> element records
a
label for the graph; similarly, the <att tei="yes">label</att> attribute on
the <gi tei="yes">node</gi> elements records the labels of those nodes.  The
<att tei="yes">order</att> and <att tei="yes">size</att> attributes on the <gi tei="yes">graph</gi>
element record the number of nodes and number of arcs in the graph
respectively; these values are optional (since they can be computed from
the rest of the graph), but if they are supplied, they must be
consistent with the rest of the encoding.  They can thus be used to help
check that the graph has been encoded and transmitted correctly.  The
<att tei="yes">degree</att> attribute on the <gi tei="yes">node</gi> elements record the
number of arcs that are incident with that node.  It is optional
(because redundant), but can be used to help in validity checking:  if a
value is given, it must be consistent with the rest of the information
in the graph.  Finally, the <att tei="yes">from</att> and <att tei="yes">to</att> attributes
on the <gi tei="yes">arc</gi> elements provide pointers to the nodes connected by
those arcs.  Since the graph is undirected, no directionality is implied
by the use of the <att tei="yes">from</att> and <att tei="yes">to</att> attributes; the
values of these attributes could be interchanged in each arc without
changing the graph.</p><p>The <att tei="yes">adj</att>, <att tei="yes">adjFrom</att>, and <att tei="yes">adjTo</att>
attributes of the <gi tei="yes">node</gi> element provide an alternative method of
representing unlabeled arcs, their values being pointers to the nodes
which are adjacent to or from that node.  The <att tei="yes">adj</att> attribute
is to be used for undirected graphs, and the <att tei="yes">adjFrom</att> and
<att tei="yes">adjTo</att> attributes for directed graphs.  It is a semantic error
for the directed adjacency attributes to be used in an undirected graph,
and vice versa.  Here is a markup of the preceding graph, using the
<att tei="yes">adj</att> attribute to represent the arcs.
 
<eg><![CDATA[<graph type=undirected
       id=CUG2
       label='Airline Connections in Southwestern USA'
       order=5
       size=4>
  <node label=LAX id=LAX degree=2 adj='LVG PHX'>
  <node label=LVG id=LVG degree=2 adj='LAX PHX'>
  <node label=PHX id=PHX degree=3 adj='LAX LVG TUS'>
  <node label=TUS id=TUS degree=1 adj='PHX'>
  <node label=CIB id=CIB degree=0>
  </graph>]]></eg></p><p>Note that each arc is represented twice in this encoding of the
graph.  For example, the existence of the arc from LAX to LVG can be
inferred from each of the first two <gi tei="yes">node</gi> elements in the graph.
This redundancy, however, is not required:  it suffices to describe an
arc in any one of the three places it can be described (either adjacent
node, or in a separate <gi tei="yes">arc</gi> element).  Here is a less redundant
representation of the same graph.
 
<eg><![CDATA[<graph type=undirected
       id=CUG3
       label='Airline Connections in Southwestern USA'
       order=5
       size=4>
  <node label=LAX id=LAX degree=2 adj='LVG PHX'>
  <node label=LVG id=LVG degree=2 adj='PHX'>
  <node label=PHX id=PHX degree=3 adj='TUS'>
  <node label=TUS id=TUS degree=1>
  <node label=CIB id=CIB degree=0>
  </graph>]]></eg></p><p>Although in many cases the <gi tei="yes">arc</gi> element is redundant (since
arcs can be described using the adjacency attributes of their adjacent
nodes), it has nevertheless been included in the tag set, in order to
allow the convenient specification of identifiers, display or
rendition information, and labels for each arc (using the attributes
<att tei="yes">id</att>, <att tei="yes">rend</att>, and <att tei="yes">label</att>).</p><p>Next, let us modify the preceding graph by adding directionality to
the arcs.  Specifically, we now think of the arcs as specifying selected
routes from one airport to another, as indicated by the direction of the
arrowheads in the following diagram.
 
<eg rend="fig"><![CDATA[          +-<-LAX-<-+
          |         |
         LVG--->---PHX--->---TUS   CIB
                    |         |
                    +----<----+
 
  Selected Airline Routes in Southwestern USA]]></eg></p><p>Here is an encoding of this graph, using the <gi tei="yes">arc</gi> element to
designate the arcs.
 
<eg><![CDATA[<graph type=directed
       id=RDG1
       label='Selected Airline Routes in Southwestern USA'
       order=5
       size=5>
   <node label=LAX id=LAX inDegree=1 outDegree=1>
   <node label=LVG id=LVG inDegree=1 outDegree=1>
   <node label=PHX id=PHX inDegree=2 outDegree=2>
   <node label=TUS id=TUS inDegree=1 outDegree=1>
   <node label=CIB id=CIB inDegree=0 outDegree=0>
   <arc  from=LAX to=LVG>
   <arc  from=LVG to=PHX>
   <arc  from=PHX to=LAX>
   <arc  from=PHX to=TUS>
   <arc  from=TUS to=PHX>
   </graph>]]></eg></p><p>Here is another encoding of the graph, using the <att tei="yes">adjTo</att> and
<att tei="yes">adjFrom</att> attributes on nodes to designate the arcs.
 
<eg><![CDATA[<graph type=directed
       id=RDG2
       label='Selected Airline Routes in Southwestern USA'
       order=5
       size=5>
   <node label=LAX id=LAX inDegree=1
         outDegree=1 adjTo=LVG adjFrom=PHX>
   <node label=LVG id=LVG inDegree=1
         outDegree=1 adjFrom=LAX adjTo=PHX>
   <node label=PHX id=PHX inDegree=2
         outDegree=2 adjTo='LAX TUS' adjFrom='LVG TUS'>
   <node label=TUS id=TUS inDegree=1
         outDegree=1 adjTo=PHX adjFrom=PHX>
   <node label=CIB id=CIB inDegree=0 outDegree=0>
   </graph>]]></eg></p><p>If we wish to label the arcs, say with flight numbers, then
<gi tei="yes">arc</gi> elements must be used to carry the <att tei="yes">label</att>
attribute, as in the following example.
 
<eg><![CDATA[<graph type=directed
       id=RDG1
       label='Selected Airline Routes in Southwestern USA'
       order=5
       size=5>
   <node label=LAX id=LAX >
   <node label=LVG id=LVG >
   <node label=PHX id=PHX >
   <node label=TUS id=TUS >
   <node label=CIB id=CIB >
   <arc  from=LAX to=LVG label='SW117'>
   <arc  from=LVG to=PHX label='SW711'>
   <arc  from=PHX to=LAX label='AA218'>
   <arc  from=PHX to=TUS label='AW229'>
   <arc  from=TUS to=PHX label='AW225'>
   </graph>]]></eg><!-- indegree/outdegree removed at DD's suggestion --></p><p>The formal declarations of the <gi tei="yes">graph</gi>, <gi tei="yes">node</gi> and
<gi tei="yes">arc</gi> elements are as follows.
 
<dtdFrag id="DGDGR" n="Graphs" file="teinet2"><tagDecl tagDoc="GRAPH"/><tagDecl tagDoc="NODE"/><tagDecl tagDoc="ARC"/></dtdFrag></p><div3 name="subsection" ref="Y"><head>Transition Networks</head><p>For encoding transition networks and other kinds of directed graphs
in which distinctions among types of nodes must be made, the
<att tei="yes">type</att> attribute is provided for <gi tei="yes">node</gi> elements.  In
the following example, the <term>initial</term> and <term>final</term>
nodes (or <term>states</term>) of the network are distinguished.  It can
be understood as accepting the set of strings obtained by traversing it
from its initial node to its final node, and concatenating the labels.
 <!-- Noam Chomsky, Syntactic Structures, 1957, p19, ex8 -->
<eg rend="fig"><![CDATA[             OLD      MAN      COMES
            +->-+   +-->----o---->---+
            |   |   |                |
            \   /   |                |
        THE  \ /    |                |
(8)   o-->----o-----+                o
                    |                |
                    |                |
                    |                |
                    +-->----o---->---+
                      MEN       COME
 
<graph type='transition network'
       id=SS8
       label='(8)'
       order=5
       size=6>
   <node id=Q0 inDegree=0 outDegree=1 type=initial>
   <node id=Q1 inDegree=2 outDegree=3>
   <node id=Q2 inDegree=1 outDegree=1>
   <node id=Q3 inDegree=1 outDegree=1>
   <node id=Q4 inDegree=2 outDegree=0 type=final>
   <arc  from=q0 to=q1 label=THE>
   <arc  from=q1 to=q1 label=OLD>
   <arc  from=q1 to=q2 label=MAN>
   <arc  from=q1 to=q3 label=MEN>
   <arc  from=q2 to=q4 label=COMES>
   <arc  from=q3 to=q4 label=COME>
   </graph>]]></eg></p><p>A finite state transducer has two labels on each arc, and can be
thought of as representing a mapping from one sequence of labels to
the other.  The following example represents a transducer for
translating the English strings accepted by the network in the
preceding example into French.  The nodes have been annotated with
numbers, for convenience.
 
<eg rend="fig"><![CDATA[ 
         THE         MAN      COMES
      +--->---1------->-----4--->---+
      |   L'  |     HOMME     VIENT |
      |       |                     |
      |    OLD|VIEIL                |
      |       |                     |
      | THE   |                     |
(8)   0-->----2                     6
      |  LE  / \                    |
      |     /   \                   |
      |    /     \                  |
      |    | OLD |                  |
      |    +-->--+                  |
      |     VIEIL                   |
      |  THE        MEN       COME  |
      +--->---3------>----5---->----+
         LES / \   HOMMES   VIENNENT
            /   \
           /     \
           | OLD |
           +-->--+
            VIEUX]]></eg><eg><![CDATA[ 
<graph type='transducer'
       order=7
       size=10>
   <node id=T0 label=0 inDegree=0 outDegree=3 type=initial>
   <node id=T1 label=1 inDegree=2 outDegree=1>
   <node id=T2 label=2 inDegree=2 outDegree=2>
   <node id=T3 label=3 inDegree=2 outDegree=2>
   <node id=T4 label=4 inDegree=1 outDegree=1>
   <node id=T5 label=5 inDegree=1 outDegree=1>
   <node id=T6 label=6 inDegree=2 outDegree=0 type=final>
   <arc  from=t0 to=t1 label=THE label2="L'">
   <arc  from=t0 to=t2 label=THE label2=LE>
   <arc  from=t0 to=t3 label=THE label2=LES>
   <arc  from=t1 to=t4 label=MAN label2=HOMME>
   <arc  from=t2 to=t1 label=OLD label2=VIEIL>
   <arc  from=t2 to=t2 label=OLD label2=VIEIL>
   <arc  from=t3 to=t3 label=OLD label2=VIEUX>
   <arc  from=t3 to=t5 label=MEN label2=HOMMES>
   <arc  from=t4 to=t6 label=COMES label2=VIENT>
   <arc  from=t5 to=t6 label=COME label2=VIENNENT>
   </graph>]]></eg></p></div3><div3 name="subsection" ref="Y"><head>Family Trees</head><p>The next example provides an encoding a portion of a
<soCalled>family tree</soCalled>, in which nodes are used to represent
individuals, and parents of individuals, and arcs are used to
represent common parentage and descent links.  Let us suppose,
further, that information about individuals is contained in feature
structures, which are contained in feature-structure libraries
elsewhere in the document (see <xref target="FSFL"/>).  We can use the
<att tei="yes">value</att> attribute on <gi tei="yes">node</gi> elements to point to those
feature structures.  Assume that, in some particular representation of
the graph, nodes representing females are framed by circles, nodes
representing males are framed by boxes, and nodes representing parents
are framed by diamonds.
 
<eg rend="fig"><![CDATA[                            Mo     Fa
                  Katherine->--K+A--<-Amberley
                                |
                        So      |    Da
                   +----<-------+----->----+
                   |            | So       |
                Bertrand        +->-+    Rachel
                   |                |
                   |              Frank
         Mo     Fa | Fa     Mo
   Peter->--P+B--<-+->--D+B--<-Dora
             |           |
          So |        Da | So
         +-<-+     +--<--+-->--+
         |         |           |
       Conrad     Kate        John]]></eg><eg><![CDATA[ 
<graph type='family tree' order=13 size=12>
  <node id=KATHR  label='Katherine'
        value=kr1 inDegree=0 outDegree=1>
  <node id=AMBER  label='Amberley'
        value=ar1 inDegree=0 outDegree=1>
  <node id=KAR  label='K+A'
        inDegree=2 outDegree=3>
  <node id=BERTR  label='Bertrand'
        value=br1 inDegree=1 outDegree=2>
  <node id=PETER  label='Peter'
        value=pr1 inDegree=0 outDegree=1>
  <node id=DORAR  label='Dora'
        value=dr1 inDegree=0 outDegree=1>
  <node id=PBR  label='P+B'
        inDegree=2 outDegree=1>
  <node id=DBR  label='D+B'
        inDegree=2 outDegree=2>
  <node id=FRANR  label='Frank'
        value=fr1 inDegree=1 outDegree=0>
  <node id=RACHR  label='Rachel'
        value=rr1 inDegree=1 outDegree=0>
  <node id=CONRR  label='Conrad'
        value=cr1 inDegree=1 outDegree=0>
  <node id=KATER  label='Kate'
        value=kr2 inDegree=1 outDegree=0>
  <node id=JOHNR  label='John'
        value=jr1 inDegree=1 outDegree=0>
  <arc label='Mo' from=KathR to=KAR>
  <arc label='Fa' from=AmbeR to=KAR>
  <arc label='So' from=KAR to=BertR>
  <arc label='So' from=KAR to=FranR>
  <arc label='Da' from=KAR to=RachR>
  <arc label='Mo' from=PeteR to=PBR>
  <arc label='Fa' from=BertR to=PBR>
  <arc label='So' from=PBR to=ConrR>
  <arc label='Mo' from=DoraR to=DBR>
  <arc label='Fa' from=BertR to=DBR>
  <arc label='Da' from=DBR to=KateR>
  <arc label='So' from=DBR to=JohnR>
  </graph>]]></eg><!-- Partial family tree for Bertrand Russell, based on       --><!-- Pereira and Shieber, Prolog and Natural Language         --><!-- Analysis, 1987, p22                                      --></p></div3><div3 name="subsection" ref="Y"><head>Historical Interpretation</head><p>For our final example, we represent graphically the relationships
among various geographic areas mentioned in a
seventeenth-century Scottish document.  The document itself is
a <soCalled>sasine</soCalled>, which records a grant of land
from the earl of Argyll to one Donald McNeill, and reads in part
as follows (abbreviations have been expanded silently,
and <q>[...]</q> marks illegible passages):
 <!-- From Dan Greenstein; EDS: can you get more details? --><!-- I think the text is quoted in Dan's contribution to      --><!-- CHum special issue. (DTL)                                -->
 
<q rend="display"><p>Item instrument of Sasine given the said Hector
Mcneil confirmed and dated 28 May 1632
[...] at Edinburgh upon the 15 June 1632</p>
<p>Item ane charter granted by Archibald late earl
of Argyle and Donald McNeill of Gallachalzie wh
makes mention that ...
the said late Earl yields and grants
to the said Donald MacNeill ...</p>
<p>All and hail the two merk land of old extent
of Gallachalzie with the pertinents by and in
the lordship of Knapdale within the sherrifdome
of Argyll</p>
<p>[description of other lands granted follows ...]</p>
<p>This Charter is dated at Inverary the 15th May 1669</p></q></p><p>In this example, we are concerned with the land and pertinents (i.e.
accompanying sources of revenue) described as <q>the two merk land of
old extent of Gallachalzie with the pertinents by and in the lordship of
Knapdale within the sherrifdom of Argyll</q>.</p><p>The passage concerns the following pieces of land:
<list type="bullets"><item>the Earl of Argyll's land (i.e. the lands granted by this clause
of the sasine)</item><item>two mark of land in Gallachalzie</item><item>the pertinents for this land</item><item>the Lordship of Knapdale</item><item>the sherrifdom of Argyll</item></list>
We will represent these geographic entities as nodes in a graph.
Arcs in the graph will represent the following relationships among
them:
<list type="bullets"><item>containment (INCLUDE)</item><item>location within (IN)</item><item>contiguity (BY)</item><item>constituency (PART OF)</item></list>
 
Note that these relationships are logically related: <q>include</q>
and <q>in</q>, for example, are inverses of each other: the Earl of
Argyll's land includes the parcel in Gallachalzie, and the parcel is
therefore in the Earl of Argyll's land.  Given an explicit set of
inference rules, an appropriate application could use the graph we are
constructing to infer the logical consequences of the relationships we
identify.</p><p>Let us assume that feature-structure analyses are available which
describe Gallachalzie, Knapdale, and Argyll.  We will link to those
feature structures using the <att tei="yes">value</att> attribute on the nodes
representing those places.  However, there may be some uncertainty as to
which noun phrase is modified by the phrase <q>within the sheriffdome of
Argyll</q>:  perhaps the entire lands (land and pertinents) are in
Argyll, perhaps just the pertinents are, or perhaps only Knapdale is
(together with the portion of the pertinents which is in Knapdale).  We
will represent all three of these interpretations in the graph; they
are, however, mutually exclusive, which we represent using the
<att tei="yes">excl</att> attribute defined in
chapter <xref target="AI"/>.<note source="auth" place="foot" anchored="Y">That is, the three syntactic
interpretations of the clause are mutually exclusive.  The notion that
the pertinents are in Argyll is clearly not inconsistent with the notion
that both the land in Gallachalzie and the pertinents are in Argyll.
The graph given here describes the possible interpretations of the
clause itself, not the sets of inferences derivable from each syntactic
interpretation, for which it would be convenient to use the facilities
described in chapter <xref target="FS"/>.</note></p><p>We represent the graph and its encoding as follows, where
the dotted lines in the graph indicate the mutually exclusive arcs; in
the encoding, we use the <att tei="yes">exclude</att> attribute to indicate those
arcs.
 
<eg rend="skel"><![CDATA[              Earl of Argyll's land
            (land described in sasine)
                      | | |
      ,-<-INCLUDE--<--' + '->-INCLUDE---> Pertinents
      |                 :                  :  |   |
 Gallachalzie          IN  ...<..IN..<.....:  |   |
                        :  :                  |   |
                        :  :             INCLUDE INCLUDE
                        :  :              |           |
                        :  :   (part of pertinents)  (part)
                        :  :              |           |
                        :  :              BY         PART OF
                        :  :              |           |
                        :  :          Lordship of Knapdale
                        :  :                   :
                        :  :  ...<.IN..<.......:
                        :  :  :
                Sherrifdom of Argyll]]></eg>
 <!-- why are some lines dotted? and no rend even supplied here for --><!-- me to delete! -->
 
The graph formalizes the following relationships:
<list type="bullets"><item>the Earl of Argyll's land <cited>includes</cited> (the parcel of
land in) Gallachalzie</item><item>the Earl of Argyll's land <cited>includes</cited> the pertinents of that parcel</item><item>the pertinents are (in part) <cited>by</cited> the Lordship of Knapdale</item><item>the pertinents are (in part) <cited>part of</cited> the Lordship of Knapdale</item><item>the Earl of Argyll's land, or the pertinents, or
the Lordship of Knapdale, is <cited>in</cited> the Sherrifdom of Argyll</item></list>
We encode the graph thus:
<eg><![CDATA[<graph type=directed order=7 size=9>
  <node id=EARL label="Earl of Argyll's land">
  <node id=GALL label="Gallachalzie" value=gallfs>
  <node id=PERT label="Pertinents">
  <node id=PER1 label="Pertinents part">
  <node id=PER2 label="Pertinents part">
  <node id=KNAP label="Lordship of Knapdale" value=knapfs>
  <node id=ARGY label="Sherrifdome of Argyll" value=argyfs>
  <arc  id=EARLGALL label="INCLUDE" from=earl to=gall>
  <arc  id=EARLARGY label="IN" from=earl to=argy
        exclude="pertargy knapargy">
  <arc  id=EARLPERT label="INCLUDE" from=earl to=pert>
  <arc  id=PERTPER1 label="INCLUDE" from=pert to=per1>
  <arc  id=PERTPER2 label="INCLUDE" from=pert to=per2>
  <arc  id=PERTARGY label="IN" from=pert to=argy
        exclude="earlargy knapargy">
  <arc  id=PER1KNAP label="BY" from=per1 to=knap>
  <arc  id=PER2KNAP label="PART OF" from=per2 to=knap>
  <arc  id=KNAPARGY label="IN" from=knap to=argy
        exclude="earlargy pertargy">
  </graph>]]></eg></p></div3></div2><?tei:SOF p2gdtr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2gdtr.odd,v $
    * Revision 1.7  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.6  94/03/27  16:30:20  lou
    * semifinal check
    * 
    * Revision 1.3  1993/09/22  18:46:17  msmcq
    * Revision as of publication of GD
    * --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : fix exx                                 --><!-- 93-09-17 : MSM : exx changes (quote LABEL values)        --><!-- 93-09-17 : MSM : outdegr[ee], cosmetic changes           --><!-- 93-09-15 : MSM : quick revisions                         --><!-- 93-07-20 : DTL : make changes consistent with GD         --><!--                  change first madeup ex to a realler one --><!--                  align attributes in examples            --><div2 id="GDTR" name="Terry" ref="Y"><head>Trees</head><p>A <term>tree</term> is a connected acyclic graph.  That is, it is
possible in a tree graph to follow a path from any vertex to any other
vertex, but there are no paths that lead from any vertex to itself.  A
rooted tree is a directed graph based on a tree; that is, the arcs in
the graph correspond to the arcs of a tree such that there is exactly
one node, called the <term>root</term>, for which there is a path from
that node to all other nodes in the graph.  For our purposes, we may
ignore all trees except for rooted trees, and hence we shall use the
<gi tei="yes">tree</gi> element for rooted trees, and the <gi tei="yes">root</gi> element
for its root.  The nodes adjacent to a given node are called its
<term>children</term>, and the node adjacent from a given node is called
its <term>parent</term>.  Nodes with both a parent and children are
called <term>internal nodes</term>, for which we use the <gi tei="yes">iNode</gi>
element.  A node with no children is tagged as a <gi tei="yes">leaf</gi>.  If the
children of a node are ordered from left to right, then we say that that
node is <term>ordered</term>.  If all the nodes of a tree are ordered,
then we say that the tree is an <term>ordered tree</term>.  If some of
the nodes of a tree are ordered and others are not, then the tree is a
<term>partially ordered tree</term>.  The ordering of nodes and trees
may be specified by an attribute; we take the default ordering for trees
to be ordered, that roots inherit their ordering from the trees in which
they occur, and internal nodes inherit their ordering from their
parents.  Finally, we permit a node to be specified as following other
nodes, which (when its parent is ordered) it would be assumed to
precede, giving rise to crossing arcs.  <!-- DD writes concerning above sentence:
"  Makes no sense! Is this just another way to specify order
 or does it convert ordered nodes to partially ordered nodes?"
 I dunno. So I'm leaving well alone. (LB) -->
The elements used for the
encoding of trees have the following descriptions and attributes.
 
<tagList style="one-line"><tagDesc tagDoc="TREE" atts="arity ord order"/><tagDesc tagDoc="ROOT" atts="label value children ord outDegree"/><tagDesc tagDoc="INODE" atts="label value children parent ord follow outDegree"/><tagDesc tagDoc="LEAF" atts="label value parent follow"/></tagList></p><p>Here is an example of a tree.  It represents the order in which the
operators of addition (symbolized by <code tei="yes" type="frag">+</code>), exponentiation
(symbolized by <code tei="yes" type="frag">**</code>) and division (symbolized by <code tei="yes" type="frag">/</code>) are
applied in evaluating the arithmetic formula <code tei="yes" type="frag">((a**2)+(b**2))/((a+b)**2) </code>.
In drawing the graph, the root is placed on the far right, and
directionality is presumed to be to the left.
 
<eg><![CDATA[a--,
   |-**-,
2--'    |
        |-+--,
b--,    |    |
   |-**-'    |
2--'         |
             |-/
a--,         |
   |-+--,    |
b--'    |    |
        |-**-'
        |
2-------'
 
<tree n='ex1' arity=2 order=12>
   <root  label='/'  id=DIV1               children='plu1 exp1'>
   <iNode label='+'  id=PLU1   parent=div1 children='exp2 exp3'>
   <iNode label='**' id=EXP1   parent=div1 children='plu2 num2.3'>
   <iNode label='**' id=EXP2   parent=plu1 children='vara1 num2.1'>
   <iNode label='**' id=EXP3   parent=plu1 children='varb1 num2.2'>
   <iNode label='+'  id=PLU2   parent=exp1 children='vara2 varb2'>
   <leaf  label='a'  id=VARA1  parent=exp2>
   <leaf  label='2'  id=NUM2.1 parent=exp2>
   <leaf  label='b'  id=VARB1  parent=exp3>
   <leaf  label='2'  id=NUM2.2 parent=exp3>
   <leaf  label='a'  id=VARA2  parent=plu2>
   <leaf  label='b'  id=VARB2  parent=plu2>
   <leaf  label='2'  id=NUM2.3 parent=exp1>
   </tree>]]></eg></p><p>In this encoding, the <att tei="yes">arity</att> attribute represents the
<term>arity</term> of the tree, which is the greatest value of the
<att tei="yes">outDegree</att> attribute for any of the nodes in the tree.  If, as
in this case, <att tei="yes">arity=2</att>, we say that the tree is a
<term>binary</term> tree.</p><p>Since the left-to-right (or top-to-bottom!) order of the children of
the two <code tei="yes" type="frag">+</code> nodes does not affect the arithmetic result in this
case, we could represent in this tree all of the arithmetically
equivalent formulas involving its leaves, by specifying the attribute
<att tei="yes">ord=N</att> on those two <gi tei="yes">iNode</gi> elements, the attribute
<att tei="yes">ord=Y</att> on the <gi tei="yes">root</gi> and other <gi tei="yes">iNode</gi>
elements, and the attribute <att tei="yes">ord=partial</att> on the <gi tei="yes">tree</gi>
element, as follows.
 
<eg><![CDATA[<tree n='ex2' ord=partial arity=2 order=13>
 <root  label='/'  id=DIV1   ord=Y             children='plu1 exp1'>
 <iNode label='+'  id=PLU1   ord=N parent=div1 children='exp2 exp3'>
 <iNode label='**' id=EXP1   ord=Y parent=div1 children='plu2 num2.3'>
 <iNode label='**' id=EXP2   ord=Y parent=plu1 children='vara1 num2.1'>
 <iNode label='**' id=EXP3   ord=Y parent=plu1 children='varb1 num2.2'>
 <iNode label='+'  id=PLU2   ord=N parent=exp1 children='vara2 varb2'>
 <leaf  label='a'  id=VARA1        parent=exp2>
 <leaf  label='2'  id=NUM2.1       parent=exp2>
 <leaf  label='b'  id=VARB1        parent=exp3>
 <leaf  label='2'  id=NUM2.2       parent=exp3>
 <leaf  label='a'  id=VARA2        parent=plu2>
 <leaf  label='b'  id=VARB2        parent=plu2>
 <leaf  label='2'  id=NUM2.3       parent=exp1>
 </tree>]]></eg></p><p>This encoding represents all of the following:
 
<list type="simple"><item><code tei="yes" type="frag">((a**2)+(b**2))/((a+b)**2)</code></item><item><code tei="yes" type="frag">((b**2)+(a**2))/((a+b)**2)</code></item><item><code tei="yes" type="frag">((a**2)+(b**2))/((b+a)**2)</code></item><item><code tei="yes" type="frag">((b**2)+(a**2))/((a+b)**2)</code></item></list></p><p>Linguistic phrase structure is very commonly represented by trees.
Here is an example of phrase structure represented by an ordered tree
with its root at the top, and a possible encoding.
 
<eg><![CDATA[      ,---PP---,
      |        |
      P    ,--NP--,
      |    |      |
     with Art     N
           |      |
          the periscope
 
<tree n='ex3' arity=2 order=8>
   <root  id=PP1               children='P1 NP1'     label='PP'>
   <iNode id=P1    parent=PP1  children=with1        label='P'>
   <leaf  id=WITH1 parent=P1                         label='with'>
   <iNode id=NP1   parent=PP1  children='the1 peri1' label='NP'>
   <iNode id=ART1  parent=NP1  children=the1         label='Art'>
   <leaf  id=THE1  parent=Art1                       label='the'>
   <iNode id=N1    parent=NP1  children=peri1        label='N'>
   <leaf  id=PERI1 parent=N1                         label='periscope'>
   </tree>]]></eg></p><p>Finally, here is an example of an ordered tree, in which a particular
node which ordinarily would precede another is specified as following
it.  In the drawing, the <code tei="yes" type="frag">xxx</code> symbol indicates that the arc from
VB to PT crosses the arc from VP to PN.
 
<eg><![CDATA[       ,--VP--,
       |      |
   ,--VB-----xxx--,
   |          |   |
   VB         PN  PT
   |          |   |
  look       them up
 
<tree n='ex4' arity=2 order=8>
   <leaf  label='look' id=LOOK1 parent=VB2>
   <leaf  label='them' id=THEM1 parent=PN1>
   <leaf  label='up'   id=UP1   parent=PT1>
   <iNode label='VB'   id=VB2   parent=VB1 children=look1>
   <iNode label='PN'   id=PN1   parent=VP1 children=them1 >
   <iNode label='PT'   id=PT1   parent=VB1 children=up1 follow=PN1>
   <iNode label='VB'   id=VB1   parent=VP1 children='VB2 PT1'>
   <root  label='VP'   id=VP1              children='VB1 PN1'>
   </tree>]]></eg></p><p>The formal declarations of the <gi tei="yes">tree</gi>, <gi tei="yes">root</gi>,
<gi tei="yes">iNode</gi> and <gi tei="yes">leaf</gi> elements are as follows.
 
<dtdFrag id="DGDTR" n="Trees (basic method)" file="teinet2"><tagDecl tagDoc="TREE"/><tagDecl tagDoc="ROOT"/><tagDecl tagDoc="INODE"/><tagDecl tagDoc="LEAF"/></dtdFrag>
 <!-- P2.449 : Another Tree Notation                           --><!-- Revisions                                                --><!-- 93-07-21 : DTL : replace < echo > by < eTree copyOf=xx > --><!--                  correct exs with missing < /eTree >     --><!-- 92-12-14 : MSM : correct forestgrp id value              --><!-- 24 Jul 92 : DTL  : Renumber section to p2.449.  Make     --><!--    other minor changes.                                  --><!-- 21 Jul 92 : DTL  : Make minor corrections.               --><!-- 19 Jul 92 : DTL  : Add ODD tagging and TAGDOCS.          --><!--    Complete draft.  Changes from ver 1.14 of A&I         --><!--    DTD: change < e.tree > and < e.leaf > to < eTree      --><!--    > and < eLeaf > respectively.  Remove name= from      --><!--    ATTLIST of < eTree > and < triangle > (the global     --><!--    n= attribute can be used).  Change content model      --><!--    of < forest > to include the possibility of           --><!--    < triangle >s.  Change content model of <             --><!--    forestGrp > to permit one or more < forest >s,        --><!--    instead of two or more.  Allow < echo > in            --><!--    content model of < forest > and < forestGrp >.        --><!-- 17 Jul 92 : SZ, DTL: Incorporate material from ALLC      --><!--    draft article.                                        --></p></div2><div2 id="GDAT" name="Anthony" ref="Y"><head>Another Tree Notation</head><!-- DD writes: "shouldnt this be swapped with preceding section
    as this is the more natural tree representation? --><p>In this section, we present an alternative to the method of
representing the structure of ordered rooted trees that is given in
section <xref target="GDTR" type="div3"/>, which is based on the observation
that any node of such a tree can be thought of as the root of the
subtree that it dominates.  Thus subtrees can be thought of as the same
type as the trees they are embedded in, hence the designation
<gi tei="yes">eTree</gi>, for <term>embedding tree</term>.  Whereas in a
<gi tei="yes">tree</gi>, the relationship among the parts is indicated by the
<att tei="yes">children</att> attribute, and by the names of the elements
<gi tei="yes">root</gi>, <gi tei="yes">iNode</gi> and <gi tei="yes">leaf</gi>, the relationship among
the parts of an <gi tei="yes">eTree</gi> is indicated simply by the arrangement of
their content.  However, we have chosen to enable encoders to
distinguish the terminal elements of an <gi tei="yes">eTree</gi> by means of the
empty <gi tei="yes">eLeaf</gi> element, though its use is not required; the
<gi tei="yes">eTree</gi> element can also be used to identify the terminal nodes
of <gi tei="yes">eTree</gi> elements.  We also provide a <gi tei="yes">triangle</gi>
element, which can be thought of as an <term>underspecified</term>
<gi tei="yes">eTree</gi>, that is an <gi tei="yes">eTree</gi> in which certain information
has been left out.  In addition, we provide a <gi tei="yes">forest</gi> element,
which consists of one or more <gi tei="yes">tree</gi>, <gi tei="yes">eTree</gi> or
<gi tei="yes">triangle</gi> elements, and a <gi tei="yes">forestGrp</gi> element, which
consists of one or more <gi tei="yes">forest</gi> elements.  The elements used for
the encoding of embedding trees and the units containing them have the
following descriptions and attributes.
 
<tagList style="one-line"><tagDesc tagDoc="ETREE" atts="label value"/><tagDesc tagDoc="TRIANGLE" atts="label value"/><tagDesc tagDoc="ELEAF" atts="label value"/><tagDesc tagDoc="FOREST" atts="type"/><tagDesc tagDoc="FORESTGP" atts="type"/></tagList></p><p>Like the <gi tei="yes">root</gi>, <gi tei="yes">iNode</gi> and <gi tei="yes">leaf</gi> of a
<gi tei="yes">tree</gi>, the <gi tei="yes">eTree</gi>, <gi tei="yes">triangle</gi> and
<gi tei="yes">eLeaf</gi> elements may also have <att tei="yes">label</att> and
<att tei="yes">value</att> attributes.</p><p>To illustrate the use of the <gi tei="yes">eTree</gi> and <gi tei="yes">eLeaf</gi>
elements, here is an encoding of the second example in section <xref target="GDTR" type="div3"/>, repeated here for convenience.
 
<eg><![CDATA[      ,---PP---,
      |        |
      P    ,--NP--,
      |    |      |
     with Art     N
           |      |
          the periscope
 
<eTree n='ex1' label='PP'>
   <eTree label='P'><eLeaf label='with'></eTree>
   <eTree label='NP'>
      <eTree label='Art'><eLeaf label='the'></eTree>
      <eTree label='N'><eLeaf label='periscope'></eTree>
      </eTree>
   </eTree>]]></eg></p><p>Next, we provide an encoding, using the <gi tei="yes">triangle</gi> element, in
which the internal structure of the <gi tei="yes">eTree</gi> labeled <code tei="yes" type="frag">NP</code> is
omitted.
 
<eg><![CDATA[      ,---PP----,
      |         |
      P        NP
      |       /  \
     with    /    \
            /______\
          the periscope
 
<eTree n='ex2' label='PP'>
   <eTree label='P'><eLeaf label='with'></eTree>
   <triangle label='NP'><eLeaf label='the periscope'></triangle>
   </eTree>]]></eg></p><p>Ambiguity involving alternative tree structures associated with the
same terminal sequence can be encoded relatively conveniently using a
combination of the <att tei="yes">exclude</att> and <att tei="yes">copyOf</att> attributes
described in sections <xref target="SAAT"/> and <xref target="SAIE"/>.  In
the simplest case, an <gi tei="yes">eTree</gi> may be part of the content of
exactly one of two different <gi tei="yes">eTree</gi> elements.  To mark it up,
the embedded <gi tei="yes">eTree</gi> may be fully specified within one of the
embedding <gi tei="yes">eTree</gi> elements to which it may belong, and a
virtual copy, specified by the <att tei="yes">copyOf</att> attribute, may appear
on the other.  In addition, each of the embedded elements in question
is specified as excluding the other, using the <att tei="yes">exclude</att>
attribute.  To illustrate, consider the English phrase <cited>see the
vessel with the periscope</cited>, which may be considered to be
structurally ambiguous, depending on whether the phrase <cited>with
the periscope</cited> is a modifier of the phrase <cited>the
vessel</cited> or a modifier of the phrase <cited>see the
vessel</cited>.  This ambiguity is indicated in the sketch of the
ambiguous tree by means of the dotted-line arcs.  The markup using the
<att tei="yes">copyOf</att> and <att tei="yes">exclude</att> attributes follows the
sketch.
 
<eg><![CDATA[      ,--------VP....................
      |        |                    :
      V   ,----NP.......         ,--PP--,
      |   |    |       :         |      |
     see Art   N    ,--PP--,     P    ,-NP-,
          |    |    |      |     |    |    |
         the vessel P    ,-NP-, with Art   N
                    |    |    |       |    |
                   with Art   N      the periscope
                         |    |
                        the periscope
 
<eTree n='ex3' label='VP'>
   <eTree label='V'><eLeaf label='see'></eTree>
   <eTree label='NP'>
      <eTree label='Art'><eLeaf label='the'></eTree>
      <eTree label='N'><eLeaf label='vessel'></eTree>
      <eTree id=PPA exclude=ppb label='PP'>
         <eTree label='P'><eLeaf label='with'></eTree>
         <eTree label='NP'>
            <eTree label='Art'><eLeaf label='the'></eTree>
            <eTree label='N'><eLeaf label='periscope'></eTree>
            </eTree>
         </eTree>
      </eTree>
   <eTree id=PPB copyOf=ppa exclude=ppa label='PP'></eTree>
   </eTree>]]></eg></p><p>To indicate that one of the alternatives is selected, one may specify
the <att tei="yes">select</att> attribute on the highest <gi tei="yes">eTree</gi> as
either <att tei="yes">select=ppa</att> or <att tei="yes">select=ppb</att>; see section<xref target="SAAT"/>
.</p><p>Depending on the grammar one uses to associate structures with
examples like <cited>see the man with the periscope</cited>, the
representations may be more complicated than this.  For example,
adopting a version of the <term>X-bar</term> theory of phrase structure
originated by Jackendoff<note source="auth" place="display" anchored="Y"><citation>R. Jackendoff, 
<title>X-Bar Syntax</title>, 1977</citation></note>, the
attachment of a modifier may require the creation of an intermediate
node which is not required when the attachment is not made, as shown in
the following diagram.  A possible encoding of this ambiguous structure
immediately follows the diagram.
 
<eg><![CDATA[    ..............VP......................
    :                                    :
 ,--V'--,                          ,-----V'------,
 |      |                          |             |
 V    ,-NP--,                   ,--V'--,      ,--PP--,
 |    |     |                   |      |      |      |
see  Spec ,-N'--,               V    ,-NP-,   P    ,-NP-,
      |   |     |               |    |    |   |    |    |
     the  N'  ,-PP---,         see  Spec  N' with Spec  N'
          |   |      |               |    |        |    |
          N   P    ,-NP-,           the   N       the   N
          |   |    |    |                 |             |
      vessel with Spec  N'             vessel        periscope
                   |    |
                  the   N
                        |
                     periscope
 
<eTree n='ex4' label="VP">
   <eTree id=VBARA exclude=vbarb label="V'">
      <eTree id=VA label="V"><eLeaf label="see"></eTree>
      <eTree label="NP">
         <eTree id=SPEC1A label="Spec"><eLeaf label="the"></eTree>
         <eTree label="N'">
            <eTree id=NBAR2A label="N'">
               <eTree label="N"><eLeaf label="vessel"></eTree>
               </eTree>
            <eTree id=PPA label="PP">
               <eTree label="P"><eLeaf label="with"></eTree>
               <eTree label="NP">
                  <eTree label="Spec"><eLeaf label="the"></eTree>
                  <eTree label="N'">
                     <eTree label="N"><eLeaf label="periscope"></eTree>
                     </eTree>
                  </eTree>
               </eTree>
            </eTree>
         </eTree>
      </eTree>
   <eTree id=VBARA exclude=vbarb label="V'">
      <eTree label="V'">
         <eTree id=VB copyOf=va label="V"></eTree>
         <eTree label="NP">
            <eTree id=SPEC1B copyOf=spec1a label="Spec"></eTree>
            <eTree id=NBAR2B copyOf=nbar2a label="N'"></eTree>
            </eTree>
         </eTree>
      <eTree id=PPB copyOf=ppa label="PP"></eTree>
      </eTree>
   </eTree>]]></eg></p><p>A <term>derivation</term> in a generative grammar is often thought
of as a set of trees.  To encode such a derivation, one may use the
<gi tei="yes">forest</gi> element, in which the trees may be marked up using the
<gi tei="yes">tree</gi>, the <gi tei="yes">eTree</gi> or the <gi tei="yes">triangle</gi> element.
The <att tei="yes">type</att> attribute may be used to specify what kind of
derivation it is.  Here is an example of a two-tree forest, involving
application of the <soCalled>wh-movement</soCalled> transformation in
the derivation of <cited>what you do</cited> (as in <cited>this is
what you do</cited>) from the underlying <cited>you do what</cited><note source="auth" place="foot" anchored="Y">The symbols <code tei="yes" type="frag">e</code> and <code tei="yes" type="frag">t</code> denote
special theoretical constructs (<term>empty category</term> and
<term>trace</term> respectively), which need not concern us here.</note>.
 
<eg><![CDATA[     ,--S'--,                 ,--S'--,
     |      |                 |      |
    COMP ,--S--,             COMP ,--S--,
     |   |     |              |   |     |
     e   NP  ,-VP-,           NP  NP  ,-VP-,
         |   |    |           |   |   |    |
        you  V    NP        what you  V    NP
             |    |                   |    |
            do   what                do    t
 
<forest n='ex5' type='syntactic derivation'>
   <eTree n='Stage 1' id=S1SBAR label="S'">
      <eTree id=S1COMP label="COMP"><eLeaf id=S1E label="e"></eTree>
      <eTree id=S1S label="S">
         <eTree id=S1NP1 label="NP"><eLeaf label="you"></eTree>
         <eTree id=S1VP label="VP">
            <eTree id=S1V label="V"><eLeaf label="do"></eTree>
            <eTree id=S1NP2 label="NP">
               <eLeaf id=S1WH label="what">
               </eTree>
            </eTree>
         </eTree>
      </eTree>
   <eTree n='Stage 2' id=S2SBAR corresp=s1sbar label="S'">
      <eTree id=S2COMP corresp=s1comp label="COMP">
         <eTree copyOf=s1np2 corresp=s1e label="NP"></eTree>
         </eTree>
      <eTree id=S2S corresp=s1s label="S">
         <eTree id=S2NP1 copyOf=s1np1 label="NP"></eTree>
         <eTree id=S2VP corresp=s1vp label="VP">
            <eTree id=S2V copyOf=s1v label="V"></eTree>
            <eTree id=S2NP2 corresp=s1np2 label="NP">
              <eLeaf corresp=s1wh label="t">
              </eTree>
            </eTree>
         </eTree>
      </eTree>
   </forest>]]></eg></p><p>In this markup, we have used <att tei="yes">copyOf</att> attributes to provide
virtual copies of elements in the tree representing the second stage of
the derivation that also occur in the first stage, and the
<att tei="yes">corresp</att> attribute (see section <xref target="SACS"/>) to link
those elements in the second stage with corresponding elements in the
first stage that are not copies of them.</p><p>If a group of forests (e.g. a full grammatical derivation including
syntactic, semantic and phonological subderivations) is to be
articulated, the grouping element <gi tei="yes">forestGrp</gi> may be used.</p><p>The formal declarations of the <gi tei="yes">eTree</gi>, <gi tei="yes">triangle</gi>,
<gi tei="yes">eLeaf</gi>, <gi tei="yes">forest</gi> and <gi tei="yes">forestGrp</gi> elements are as
follows.
 
<dtdFrag id="DGDAL" n="Trees (alternate method)" file="teinet2"><tagDecl tagDoc="ETREE"/><tagDecl tagDoc="TRIANGLE"/><tagDecl tagDoc="ELEAF"/><tagDecl tagDoc="FOREST"/><tagDecl tagDoc="FORESTGP"/></dtdFrag></p></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:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2gdtr.odd ??></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2gd.odd ??><!-- 21 Graphs and Digraphs --><?tei:SOF p2ft.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ft.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  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.7  1994/03/21  14:12:08  lou
    * second mass typo clearup
    * 
    * Revision 1.4  1994/03/07  15:31:52  lou
    * apply various typos etc.
    * 
    * Revision 1.3  1994/03/01  03:56:59  msmcq
    * revision during/after SC meeting
    * --><!-- 17 mar: apply MSM's typos of 8 mar --><!-- 13 mar: change id opn dtdfrag to avoid id clash --><!-- To do:                                                   --><!-- biblio for z39.59, iso 12085, iso 9573, cals /milspec 28001 --><!-- biblio for LaTeX, AMS-TeX                                --><!-- rename formula notn att as notation,                     --><!--      make declared value a TEI keyword                   --><!-- biblio for Euromath                                      --><!-- check on FPIs for Euromath, ISO 9573, ISO 12083          --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : normalize caps in headings              --><!-- 94-02-25 : MSM : add top-level DTD fragment              --><!-- 94-02-25 : MSM : comment out list of things to do        --><!-- 94-02-25 : MSM : remove items completed                  --><!-- 22 Feb 94 : MSM : final cleanup for P3 (first pass)     --><!-- 2 feb 94: revised tables extensively: split into chunks --><!-- 12 Nov 93: expanded tables --><!-- Date: Fri, 25 Jun 1993 17:27:07 -0500 --><!-- to: u35395@uicvm.uic.edu, lou@vax.ox.ac.uk, dgd@cs.bu.edu --><!-- From: sjd@ebt.com --><div1 id="FT" n="22" name="Faisal" ref="Y"><head>Tables, Formulae, and Graphics</head><p>Many documents, both historical and contemporary, include not only
text but also graphics, artwork, and other images.  Although such
images could be represented directly within SGML, SGML is not primarily
designed for that purpose, and it is standard practice to include
such information in SGML documents by declaring each image as an
external entity encoded in a suitable non-SGML notation, and then
referring to it from within the document.</p><p>In addition to graphic images, documents often contain material
presented in graphical or tabular format. In such materials, details
of layout and presentation may also be of comparatively greater
significance or complexity than they are for running text. Indeed, it
may often be difficult to make a clear distinction between details
relating purely to the rendition of information and those relating to
the information itself.</p><p>Finally, documents may contain mathematical formul&aelig; or
expressions in other formulaic notations, for which no SGML notation is
defined in these Guidelines.</p><p>These areas (graphics, tabular material, and mathematical or other
formul&aelig;) have in common that they have received considerable
attention from many other standards bodies or similar professional
groups.  In part because of this, they may frequently be most
conveniently encoded and processed using some non-SGML notation, or some
SGML notation not defined by these Guidelines.  For these reasons, and
others, we consider tables, formul&aelig;, and graphics together in this
chapter.</p><p>As with text markup in general, many incompatible formats have been
proposed for the representation of graphics, formulae and tables in
electronic form.  Unfortunately, no single format as effective as SGML
in the domain of text has yet emerged for their interchange, to some
extent because of the difficulty of representing the information these
data formats convey independently of the way it is rendered.</p><p>The additional tag set defined by this chapter defines special
purpose <soCalled>container</soCalled> elements that can be used to
encapsulate occurrences of such data within a TEI-conformant document in
a portable way.  Specific recommendations for the encoding of tables are
provided in section <xref target="FTTAB"/> and recommendations for
mathematical or other formul&aelig; in section <xref target="FTFOR"/>.
Specific recommendations for the encoding of graphic figures may be
found in section <xref target="FTGRA"/>.  The rest of the chapter is
devoted to general problems of encoding graphic information.</p><p>There is at the time of writing no consensus on formats for graphical
images, and such formats vary in many ways.  We therefore provide (in
section <xref target="FTGROV"/>) a brief discussion of the ways in which
images may be represented, and (in section <xref target="FTGRNO"/>) a list
of formal names for those representations most popular at this time.
Each one includes a very brief description and (where known) a reference
to the formal specification of the notation.  These Guidelines recommend
a few particular representations as being the most widely supported and
understood.</p><p>To enable the additional tag set defined by this chapter, the
parameter entity <term>TEI.figures</term> must be defined with the
value <code tei="yes" type="frag">INCLUDE</code>, as shown in the example below:
 
<eg><![CDATA[ <!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                        "tei2.dtd" [
    <!ENTITY % TEI.figures 'INCLUDE' >
 ]>]]></eg>
 
With this declaration in effect, the TEI elements and attributes
described in the following sections are all available.  If any of the
specialized notations described in sections <xref target="FTFOR"/> and<xref target="FTGRA"/>
 are used, then an additional <term>notation
declaration</term> must also be included in the document type
declaration subset, as further illustrated below.
 <!-- is this right? we don't have any way of generating notation      --><!-- declarations in the tagset anyway, so it will have to be!  (LB) --></p><p>The overall structure of the tag set defined in this chapter is
as follows:
<dtdFrag id="DFTFF" n="Tables, Formulae, Figures" file="teifig2"><dtdRef dtdFrag="DFTTAB"/><dtdRef dtdFrag="DFTFOR"/><dtdRef dtdFrag="DFTGRA"/></dtdFrag></p><?tei:SOF p2fttab.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2fttab.odd,v $
# Revision 1.3  1994/03/07  15:31:52  lou
# apply various typos etc.
#
# Revision 1.2  1994/03/01  03:56:59  msmcq
# revision during/after SC meeting
# --><!-- Revisions:                                               --><!-- 1994-02-23 : MSM : cleanup for TEI P3                    --><div2 id="FTTAB" name="Anthony" ref="Y"><head>Tables</head><p>A table is the least <soCalled>graphic</soCalled> of the elements
discussed in this chapter.  Almost any text structure can be presented
as a series of rows and columns:  one might, for example, choose to show
a glossary or other form of list in tabular form, without necessarily
regarding it as a table.  In such cases, the global <att tei="yes">rend</att>
attribute is an appropriate way of indicating that some element is being
presented in tabular format.  When tabular presentation is regarded as
of less intrinsic importance, it is correspondingly simpler to encode
descriptive or functional information about the contents of the table,
for example to identify one column as containing names and another as
containing dates, though the two methods may be combined.
 </p><p>When, however, particular SGML elements are required to encode the
tabular arrangement itself, then one or other of the various
<soCalled>table DTDs</soCalled> now available may be preferable.  The
table DTDs in common use generally view a table as a special text
element, made up of row elements (or, sometimes, column elements),
themselves composed of cells.  Table cells generally appear in row-major
order, with the first row from left to right, then the second row, and
so on.  Details of appearance such as column widths, border lines, and
alignment are generally encoded by numerous attributes.  Beyond this,
however, such DTDs differ greatly.  This section begins by describing a
table DTD of this kind; a brief summary of some other widely available
table DTDs is also provided in section <xref target="FTTAB2"/>.
 </p><div3 id="FTTAB1" name="subsection" ref="Y"><head>The TEI Table DTD</head><p>For encoding tables of low to moderate complexity, these Guidelines
provide the following special purpose elements:
 
<tagList style="one-line"><tagDesc tagDoc="TABLE" atts="rows cols"/><tagDesc tagDoc="ROW" atts="role"/><tagDesc tagDoc="CELL" atts="role cols rows"/></tagList>
 </p><p>The <gi tei="yes">table</gi> element is defined as a member of the class
<term>inter</term>; it may therefore appear both within other components
(such as paragraphs), or between them, provided that the additional tag
set defined in this chapter has been enabled, as described at the
beginning of this chapter.
 </p><p>It is to a large extent arbitrary whether a table should be regarded
as a series of rows or as a series of columns.  For compatibility with
currently available systems, however, these Guidelines require a
row-by-row description of a table.  It is also possible to describe a
table simply as a series of cells; this may be useful for tabular
material which is not presented as a simple matrix.
 </p><p>The attributes <att tei="yes">rows</att> and <att tei="yes">cols</att> may be used to
indicate the size of a table, or to indicate that a particular cell of a
table spans more than one row or column.  For both tables and cells,
rows and columns are always given in top-to-bottom, left-to-right order.
These Guidelines do not require that the size of a table be specified;
for most formatting and many other applications, it will be necessary to
process the whole table in two passes in any case.
 </p><p>Where cells span more than one column or row, the encoder must
determine whether this is a purely presentational effect (in which case
the <att tei="yes">rend</att> attribute may be more appropriate), whether the part
of the table affected would be better treated as a nested table, or
whether to use the spanning attributes listed above.
 </p><p>The <att tei="yes">role</att> attribute may be used to categorize a single
cell, or set a default for all the cells in a given row.  The present
Guidelines distinguish the roles of <term>label</term> and
<term>data</term> only, but the encoder may define other roles, such as
<q>derived</q>, <q>numeric</q>, etc., as appropriate.
 </p><p>The following simple example demonstrates how the data presented as a
labelled list in section <xref target="COLI"/> might be represented by an
encoder wishing to preserve its original appearance as a table:
 
<eg><![CDATA[<table rows=2 cols=2 rend=boxed>
<head rend=it>Report of the conduct and progress
of Ernest Pontifex.  Upper Vth form &mdash; half
term ending Midsummer 1851</head>
<row><cell role=label>Classics</cell>
     <cell>Idle listless and unimproving</cell>
</row>
<row><cell role=label>Mathematics</cell>
     <cell>ditto</cell>
</row>
<row><cell role=label>Divinity</cell>
     <cell>ditto</cell>
</row>
<row><cell role=label>Conduct in house</cell>
      <cell>Orderly</cell>
</row>
<row><cell role=label>General conduct</cell>
     <cell>Not satisfactory, on account of his great
     unpunctuality and inattention to duties</cell>
</row></table>]]></eg><!-- S Butler, Way of all Flesh, -->
 </p><p>Note that this encoding makes no attempt to represent the full
significance of the <q>ditto</q> cells above; these might be regarded as
simple links between the cells containing them and that to which they
refer, or as virtual copies of it.  For ways of representing either
interpretation, see chapter <xref target="SA"/>.
 </p><p>The following example demonstrates how a simple statistical table may
be represented using this scheme:
 
<eg><![CDATA[<table rows=4 cols=4>
<head>Poor Man's Lodgings in Norfolk (Mayhew, 1843)
<row role=label>
  <cell>
  <cell>Dossing Cribs or Lodging Houses
  <cell>Beds
  <cell>Needys or Nightly Lodgers
<row role=data>
  <cell role=label>Bury St Edmund's
  <cell>5<cell>8<cell>128
<row role=data>
  <cell role=label>Thetford
  <cell>3<cell>6<cell>36
<row role=data>
  <cell role=label>Attleboro'
  <cell>3<cell>5<cell>20
<row role=data>
  <cell role=label>Wymondham
  <cell>1<cell>11<cell>22
<!-- ... -->
</table>]]></eg>
 </p><p>Note the use of a blank cell in the first row to ensure that the
column labels are correctly aligned with the data.  Again, this encoding
does not explicitly represent the alignment between column and row
labels and the data to which they apply.  Where the primary emphasis of
an encoding is on the semantic content of a table, a more explicit
mechanism for the representation of structured information such as that
provided by the feature structure mechanism described in chapter <xref target="FS"/> may be preferred.  Alternatively, the general purpose linkage
and alignment mechanisms described in chapter <xref target="SA"/> may also
be applied to individual cells of a table.
 </p><p>The content of a table cell need not be simply character data.  It
may also contain any sequence of the phrase level elements described in
chapter <xref target="CO"/>, thus allowing for the encoding of potentially
more useful semantic information, as in the following example, where the
fact that one cell contains a number and the other contains a place name
has been explicitly recorded:
 
<eg><![CDATA[<table>
   <head>US State populations, 1990</head>
   <row role=data>
        <cell><name>Wyoming</>
        <cell><num>453,588</></row>
   <row><cell><name>Alaska</>
        <cell><num>550,043</></row>
   <row><cell><name>Vermont</>
        <cell><num>562,758</></row>
   <row><cell><name>District of Columbia</>
        <cell><num>606,900</></row>
   <row><cell><name>North Dakota</>
        <cell><num>638,800</></row>
   <row><cell><name>Delaware</>
        <cell><num>666,168</></row>
   <row><cell><name>South Dakota</>
        <cell><num>696,004</></row>
   <row><cell><name>Montana</>
        <cell><num>799,065</></row>
   <row><cell><name>Rhode Island</>
        <cell><num>1,003,464</></row>
  <!-- ... -->
</table>]]></eg>
 </p><p>In syntactic terms this is little more than a name-change; however,
the new names are more useful in that they convey something about the
nature and significance of the information, rather than merely
suggesting how to display it in rows and columns.</p><p>The TEI table elements are defined as follows:
<dtdFrag id="DFTTAB" n="Tables"><tagDecl tagDoc="TABLE"/><tagDecl tagDoc="ROW"/><tagDecl tagDoc="CELL"/></dtdFrag>
 </p></div3><div3 id="FTTAB2" name="subsection" ref="Y"><head>Other Table DTDs</head><p>Many SGML authoring systems now include built-in support for their
own or for public table DTDs.  These often provide an enhanced user
interface and good formatting capabilities, but are often
product-specific, despite their use of SGML.
 </p><p>The SGML DTD developed by the Association of American Publishers
(AAP) and standardized in ANSI Z39.59 provided a very simple encoding
for correspondingly simple tables.  This has been further developed,
together with the table DTD documented in ISO Technical Report 9537, and
now forms part of ISO 12083.  The TEI DTD fragment described above has
functionality very similar to that defined by ISO 12083.
 <!-- need proper bibliog refs for these -->
 </p><p>For more complex tables, the most effective publically-available DTD
is probably that developed by the US Department of Defense CALS project.
This supports vertical and horizontal spanning and various kinds of text
rotation and justification within cells and is also directly supported
by a number of existing SGML software systems.
 </p><p>The CALS table DTD is much too complex to describe fully here;
information on it can be obtained, among other places, from the Graphic
Communications Association in Alexandria, Virginia.  The formal name of
the CALS SGML requirements is MIL-M-28001A.
 <!-- need proper biblio reference here -->
 
Tables conforming to the CALS DTD may be incorporated into documents
conforming to these Guidelines, but this may require substantial
modification of the TEI DTD which should not be undertaken without
expert advice.
 </p></div3></div2><?tei:EOF p2fttab.odd ??><?tei:SOF p2ftfor.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2ftfor.odd,v $
# Revision 1.5  1994/04/08  18:54:36  msmcq
# Last-second fixes for P3
#
# Revision 1.4  1994/03/21  14:12:09  lou
# second mass typo clearup
#
# Revision 1.3  1994/03/07  15:31:52  lou
# apply various typos etc.
#
# Revision 1.2  1994/03/01  03:56:59  msmcq
# revision during/after SC meeting
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : respell heading                         --><!-- 94-02-28 : MSM : refine TeX expressions                  --><!-- 94-02-28 : MSM : Replace sphere with Borges              --><!-- 94-02-28 : MSM : correct other instance of sphere        --><!-- 94-02-25 : MSM : suppress FILE att on dtdfrag            --><!-- 94-02-25 : MSM : fix minor SGML glitches                 --><!-- 1994-02-23 : MSM : revise for style, try to fix FPIs     --><div2 id="FTFOR" name="Anthony" ref="Y"><head>Formulae</head><p>Mathematical and chemical formul&aelig; pose similar problems to
those posed by tables in that rendition may be of great significance and
hard to disentangle from content.  They also require access to a wide
range of special characters, for most of which standard entity names
already exist in the documented ISO entity sets (see further chapters<xref target="CH"/>
 and <xref target="WD"/>).
 </p><p>Formul&aelig; and tables are also similar in that well-researched and
detailed SGML DTD fragments have already been developed for them
independently of the TEI.  They differ in that (for mathematics at
least) there also exists a richly detailed text-based but non-SGML
notation which is very widely used:  this is the TeX system, and the
sets of descriptive macros developed for it such as LaTeX and AMS-Tex.
 <!-- refs for all these are needed -->
 </p><p>The AAP and ISO standards mentioned in section <xref target="FTTAB"/>
above both provide SGML DTDs for equations as well as for tables, which
at the time of writing are being updated and unified to form part of ISO
12083.  There is also also a third and more general-purpose ongoing
mathematical DTD effort known as EuroMath.<note source="auth" place="display" anchored="Y">Reference needed!
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.
FIX THIS NOTE BEFORE PUBLICATION.</note>
 </p><p>As with tables, in all the SGML solutions a tension exists between
the need to encode the way a formula is written (its appearance) and the
need to represent its semantics.  If the object of the SGML encoding is
purely to act as an interchange format among different formatting
programs, then there is no need to represent the mathematical meaning of
an expression.  If however the object is to use the SGML encoding as
input to an algebraic manipulation system (such as Mathematica or Maple)
or a database system, clearly simply representing superscripts and subscripts
will be inadequate.
 </p><p>The present Guidelines make no attempt to add to the number of
available DTDs for representing formul&aelig;.  Instead, we recommend
that the user make an informed choice from those already available.  The
additional tag set described in this chapter makes available only the
following element, which should be used to encode any formula, no matter
what notation is employed:
 
<tagList style="one-line"><tagDesc tagDoc="FORMULA" atts="notation"/></tagList>
 </p><p>The legal content of a <gi tei="yes">formula</gi> is determined by two factors.
The parameter entity <term>formulaContent</term> supplies an SGML
content model for the element; while the <att tei="yes">notation</att> attribute
specifies what SGML <term>notation</term> is employed by the element.
The default value of the <term>formulaContent</term> entity is
<code tei="yes" type="frag">CDATA</code>, but may be redefined in the document's DTD subset, for
example as follows:
 
<eg><![CDATA[<!ENTITY % formulaContent "(#PCDATA)">]]></eg>
 
With this declaration in force, formul&aelig; may contain parsed
character data, (and may thus use SGML entity references for special
symbols and the like).  An alternative might be to embed the elements
defined by some other tag set, such as that of ISO 12083.  <note source="auth" place="foot" anchored="Y">In this case additional redefinitions may also be needed to
avoid name clashes with existing TEI elements.  For further details see
chapter <xref target="MD"/>.</note>
 </p><p>Secondly, when it is necessary to inform an SGML processor that the
content of a <gi tei="yes">formula</gi> should not be treated as ordinary SGML
data, because it uses a different notation, a <term>notation</term> must
be specified.  Each notation used by a document must be declared in its
DTD subset, as in the following example:
 
<eg><![CDATA[ <!DOCTYPE tei.2 [
 <!ENTITY % TEI.graphics "INCLUDE">
 <!NOTATION TeX PUBLIC
   '-//Donald E. Knuth 1983//NOTATION TeX Mathematical Markup//EN'>
 <!ENTITY % formulaContent "(#PCDATA)"  >
 ]>]]></eg>
 </p><p>With these declarations in force, a document may include formul&aelig;
expressed using standard TeX conventions, as in the following example:
 
<eg><![CDATA[<p>Achilles runs ten times faster than the tortoise and
gives the animal a headstart of ten meters.  Achilles runs
those ten meters, the tortoise one; Achilles runs that
meter, the tortoise runs a decimeter; Achilles runs that
decimeter, the tortoise runs a centimeter; Achilles runs
that centimeter, the tortoise, a millimeter; Fleet-footed
Achilles, the millimeter, the tortoise, a tenth of a
millimeter, and so on to infinity, without the tortoise ever
being overtaken. . . Such is the customary version.
<!-- ... -->
The problem does not change, as you can see; but I would
like to know the name of the poet who provided it with a
hero and a tortoise.  To those magical competitors and to
the series
<formula notation=TeX>
$$
{1 \over 10} +
{1 \over 100} +
{1 \over 1000} +
{1 \over 1000} +
{1 \over 10,\!000} +
\dots
$$
</formula>
the argument owes its fame.]]></eg><!-- Jorge Luis Borges, "Avatars of the Tortoise," transl.    --><!-- James E. Irby, in <title>Labyrinths:  Selected Stories   --><!-- and Other Writings</title> ([New York]:  New             --><!-- Directions, 1962), pp. 202-203.                          -->
 
The <att tei="yes">notation</att> attribute supplies the name of a defined SGML
notation (<q>LaTeX</q>), which is associated by its declaration in the
DTD subset with an external public entity.  How that declaration is
resolved will depend on the kind of processor in use, and is outside the
scope of these Guidelines.  The declaration for the
<term>formulaContent</term> parameter entity in the DTD will determine
how the contents of any <gi tei="yes">formula</gi> elements will first be parsed
by the SGML processor before they are handed to whatever procedure is
intended to handle the external notation.  When as here it is declared
with a value of <code lang="sgml" tei="yes" type="fragment">(#PCDATA)</code>, then any
SGML entity references in the content will be resolved.  This may be
useful if the external mechanism uses characters which would otherwise
be regarded as significant to the SGML processor:  for example, the
less-than or greater-than signs.  If a less-than sign or another SGML
delimiter occurs in a context meaningful to SGML (for the most common
delimiters this mean before any letter), the SGML processor will attempt
to interpret it:  For example, in this expression:
 
<eg><![CDATA[<formula notation=tex> a<b </formula>]]></eg>
 
because the less-than sign is followed by a letter, it would be
recognized by SGML as beginning a start-tag (for a presumably
nonexistent element <gi tei="no">b</gi>).  One way of avoiding this
problem is to represent the less-than character by an entity reference:
 
<eg><![CDATA[<formula notation=tex> a&lt;b </formula>]]></eg>
 </p><p>Of course, if the notation permits it (as TeX does), a simpler
solution to this specific problem is to insert a space after the
less-than sign:
 
<eg><![CDATA[<formula notation=tex> a < b </formula>]]></eg>
 
Entity references may only appear in the content of a <gi tei="yes">formula</gi>
element when the entity <term>formulaContent</term> has been redefined
as above.  By default, <term>formulaContent</term> is defined as
<code tei="yes" type="frag">CDATA</code>, which means that the only SGML processing carried
out is to search for an end-tag.  This means that the character sequence
<code tei="yes" type="frag">&lt;/</code> may not be followed by a <code tei="yes" type="frag">&gt;</code> or a letter
anywhere within a formula; outside an SGML context, this sequence is
fairly unlikely.  If it does appear, or if an SGML notation is used,
then the parameter entity must be redefined appropriately.
 </p><p>The following SGML-based notations for encoding formul&aelig; are
recommended by these Guidelines:
 
<eg><![CDATA[<!NOTATION iso12083 PUBLIC
   'ISO 12083:1993//DTD Formulae//EN'>
<!NOTATION euromath PUBLIC
   '-//Euromath 1992//DTD Euromath equations//EN'>]]></eg>
 
 </p><p>In-line versus block placement for an equation can be distinguished
if desired, via the global <att tei="yes">rend</att> attribute.  The global
<att tei="yes">n</att> and <att tei="yes">id</att> attributes may also be used to label or
identify the formula, as in the following (imaginary) example:
 
<eg><![CDATA[<p>The volume of a sphere is given by the formula:
<formula n=12 rend=inline id=F12 notation=tex>
   $$V = {4\over 3} \pi r^3$$
</formula>
which is readily calculated.
</p>
<p>
As we have seen in equation <ptr target=F12>, ....
 ]]></eg>
 
 </p><p>The <term>formulaContent</term> and <term>formulaNotations</term>
parameter entities are defined as follows:
 
<dtdFrag id="DFTPE" n="Formula Content" file="teifig2.ent"><entDecl entDoc="FORMNOTN"/><entDecl entDoc="FORMCONT"/></dtdFrag>
 </p><p>The formula element itself is defined as follows:
 
<dtdFrag id="DFTFOR" n="Formulae"><tagDecl tagDoc="FORMULA"/></dtdFrag>
 </p></div2><?tei:EOF p2ftfor.odd ??><?tei:SOF p2ftgra.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2ftgra.odd,v $
    * Revision 1.6  1998/01/31 19:14:05  tei
    * Use public identifiers, not system identifiers.
    *
    * Revision 1.5  98/01/31  17:17:18  tei
    * Fix log keyword
    * 
    * Revision 1.4  94/03/21  14:12:09  lou
    * second mass typo clearup
    * 
    * Revision 1.3  1994/03/07  15:31:52  lou
    * apply various typos etc.
    * 
    * Revision 1.2  1994/03/01  03:56:59  msmcq
    * revision during/after SC meeting
    *--><!-- Revisions:                                               --><!-- 98-01-31 : MSM : fix owner identifiers in public ids     --><!-- 98-01-30 : MSM : fix references to 'system entities';    --><!--                  make them 'external entities' instead   --><!-- 94-02-28 : MSM : no NOTATION att on FIGURE element       --><!-- 94-02-25 : MSM : upgrade ISO fpis                        --><!-- 94-02-25 : MSM : add example of long caption             --><div2 id="FTGRA" name="Anthony" ref="Y"><head>Specific Elements for Graphic Images</head><p>The following special purpose elements are provided by this
tag set to indicate the presence of graphic images within a document:
 
<tagList style="one-line"><tagDesc tagDoc="FIGURE" atts="entity"/><tagDesc tagDoc="FIGDESC"/></tagList></p><p>Inclusion of a graphic image in an SGML document of any kind
typically requires three distinct steps:
 
<list type="ordered"><item>The <term>notation</term> employed by the image itself must be
defined; this is done with an SGML notation declaration in the document
type definition.</item><item>The external entity in which the image is stored must be defined;
this is done with an SGML entity declaration, which refers to the
notation declared at step one.</item><item>Within the document, the <gi tei="yes">figure</gi> element is used to mark
the position of the image, which is referenced by name, like any other
kind of external entity.</item></list>
 
In the TEI scheme, these three functions are carried out as follows.</p><p>Declarations for all notations used by a document must be provided
within the DTD subset, as described above in section <xref target="FTFOR"/>.  Many such notations are in common use; for details see
section <xref target="FTGRNO"/>.</p><p>Entity declarations for the entities containing the
graphics themselves must be made, using system or public identiifers,
within the document's DTD subset,
either directly or by including them within a suitable file, as in the
example below.
 
<eg><![CDATA[<!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
<!ENTITY % TEI.prose "INCLUDE">
<!ENTITY % TEI.graphics "INCLUDE">
 
<!-- Graphics notations used in this document ... -->
<!NOTATION tiff PUBLIC
    '-//TEI//NOTATION Aldus Tagged Image File Format//EN' >
<!NOTATION cgm PUBLIC
    'ISO 8632-4:1987//NOTATION Clear text encoding//EN' >
<!NOTATION bmp  PUBLIC
    '-//TEI//NOTATION BMP:  Microsoft Bitmapped graphic
               format//EN' >
 
 
<!-- The file 'figures.ent' contains entity declarations -->
<!-- for all external entities needed by this document -->
<!ENTITY % myFigures "figures.ent"> %myFigures;
]>]]></eg>
 
The file <term>figures.ent</term> will contain a series of
declarations like the following:
 
<eg><![CDATA[<!ENTITY Fig1    system  "fig1.cgm"    NDATA cgm>
<!ENTITY Fig1th  system  "fig1.bmp"    NDATA bmp>
<!ENTITY pullman system  "pullman.tif" NDATA tiff>]]></eg>
 
the effect of which is to associate the name <term>Fig1</term> with the
external entity <term>fig1.cgm</term>, and also to declare that that
entity uses the non-SGML notation called <q>CGM</q>, which is declared
in the DTD subset.  In the same way, the external entity
<term>fig1.bmp</term> is defined as using the <q>BMP</q> notation, and
may be referenced by the name <term>Fig1th</term> (see further below).</p><p>Finally, the <gi tei="yes">figure</gi> element is used to indicate the location
of the graphic image in the text.  For example:
 
<eg><![CDATA[<figure entity='Fig1'></figure>]]></eg></p><!-- Use a Tenniel Alice drawing?  Or a Holmes piece.         --><p>Note that an end-tag is always required for this element.  Three
kinds of content may be supplied: the element <gi tei="yes">head</gi> may be
used to transcribe (or supply) a descriptive heading or title for the
graphic itself as in this example:
 
<eg><![CDATA[<figure entity='Fig1'>
<head>Figure One: The View from the Bridge</head></figure>]]></eg></p><p>Figures are often accompanied not only by a title or heading, but
by a paragraph or so of commentary or caption.  One or more <gi tei="yes">p</gi>
elements following the <gi tei="yes">head</gi> may be used to transcribe any
caption or discussion of the figure in the source:
 
<eg><![CDATA[<figure entity=pullman>
<head>Above:</head>
<p>The drawing room of the Pullman house, the white and
gold saloon where the magnate delighted in giving
receptions for several hundred people.</p>
<figDesc>The figure shows an elaborately decorated room,
at least twenty-five feet side to side and fifty feet
long, with ornate mouldings and Corinthian columns
on the walls, overstuffed armchairs and loveseats
arranged in several conversational groupings, and
two large chandeliers.</figDesc>
</figure>]]></eg><!-- David Lowe, Lost Chicago (Boston:  Houghton Mifflin, 1978), --><!-- p. 30 top.  Ex libris Wendy Plotkin.                     -->
 
Here, the paragraph <q>The drawing room ... several hundred people</q>
is transcribed from the source, while the description is provided by
the encoder, for use by applications which cannot display the graphic
directly.  In documents created in electronic form with the needs of
print-handicapped readers in mind, the <gi tei="yes">figDesc</gi> element may be
provided by the author rather than a subsequent encoder.
 
<eg><![CDATA[<figure entity='Fig1'>
<head>Figure One: The View from the Bridge</head>
<figDesc>A Whistleresque view showing four
or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
</figure>]]></eg></p><p>Where the graphic itself contains large amounts of text, perhaps
with a complex structure, and perhaps difficult to distinguish from
the graphic, the encoder should choose whether to regard the graphic
as containing the text (in which case, a nested <gi tei="yes">text</gi> element
may be included within the <gi tei="yes">figure</gi> element) or to regard the
enclosed text as being a separate division of the <gi tei="yes">text</gi>
element in which the graphic appears.  In this latter case, an
appropriate <term>divn</term> class element may be used for the text
represented within the graphic, and the <gi tei="yes">figure</gi> element
embedded within it.  The choice will depend to a large degree on the
encoder's understanding of the relationship between the graphic and
the surrounding text.</p><p>Like any other element in the TEI scheme, figures may be given
identifiers so that they can be aligned with other elements, and linked
to or from them, as described in chapter <xref target="SA"/>.  Some common
examples are discussed briefly here;  full information is provided in
that chapter.</p><p>It is often desirable to maintain two versions of an image in an
electronic file:  one a low resolution or <soCalled>thumbnail</soCalled>
version which, when selected by the user, causes the other, high
resolution, version to be accessed.  In TEI terms, the thumbnail image
acts as a <term>reference</term> to the other.  Referring to the example
above, we will assume that the entity <q>Fig1th</q> contains a thumbnail
version of the full Fig1 entity.  We can now embed a reference to that
image using the simple <gi tei="yes">ref</gi> element discussed in section <xref target="COXR"/>:
 
<eg><![CDATA[ 
<ref target=IM1>Click here
    <figure entity=fig1th></>
     for enlightenment
</ref>
<!-- ... -->
<!-- elsewhere in the document -->
<figure id=IM1 entity=fig1></>
<!-- other figures here -->]]></eg></p><p>Another common requirement is to associate part or the whole of an
image with a textual element not necessarily contiguous to it in the
text; this is sometimes known as a <term>callout</term>. Again, chapter<xref target="SA"/>
 should be consulted for the full details of the
mechanisms available for this purpose. This example assumes that we wish
to associate one portion of the image held as <q>fig1</q> with chapter
two of some text, and another portion of it with chapter three. The
application may be thought of as a hypertext browser in which the user
selects from a graphic image which part of a text to read next, but the
mechanism is independent of this particular application.</p><p>The first requirement is some way of identifying and hence pointing
to sub-parts of a graphic image. This is most easily done using the
extended pointer syntax discussed in section <xref target="SAXR"/>: thus
 
<eg><![CDATA[<xptr id=PD1 doc=Fig1 from='space (0 0 9 9)'>
<xptr id=PD2 doc=Fig1 from='space (40 90 59 119)'>]]></eg></p><p>These <gi tei="yes">xptr</gi> elements identify two areas within the image
<q>Fig1</q> using the TEI extended pointer syntax.  The first (with
identifier <q>pd1</q>) is a square of size 10 by 10, tangent to the
origin.  The second (with identifier <q>pd2</q>) is a rectangle of size
20 by 30, starting at the point with co-ordinates (40,90) in the
co-ordinate system used by this document.</p><p>The next requirement is some way of identifying the parts of the
document to which a link is to be made.  The most obvious way of doing
this is to use the global <att tei="yes">id</att> attribute:
 
<eg><![CDATA[<div1 type=chapter id=C1>
  <!-- text of chapter one here -->
<div1 type=chapter id=C2>
  <!-- text of chapter two here -->
 ]]></eg></p><p>Now, all that is needed to linking these areas to the relevant
chapters is a <gi tei="yes">linkGrp</gi> element, as described in section <xref target="SAPT"/>:
 
<eg><![CDATA[<linkGrp type=callout>
  <link targets='C1 pd1'>
  <link targets='C2 pd2'>
  <!-- ... -->
</linkGrp>
 ]]></eg>
 
Further examples of this technique are provided in chapter <xref target="SA"/>.</p><p>The elements discussed in this section are defined as follows:
 
<dtdFrag id="DFTGRA" n="Figures"><tagDecl tagDoc="FIGURE"/><tagDecl tagDoc="FIGDESC"/></dtdFrag></p></div2><div2 id="FTGROV" name="Anthony" ref="Y"><head>Overview of Basic Graphics Concepts</head><!-- could put in a ref to Peter R's nice book here? --><p>The first major distinction in graphic representation is that between
raster graphics and vector graphics.  A <term>raster image</term> is a
list of points, or dots.  Scanners, fax machines and other simple
devices easily produce digital raster images, and such images are
therefore quite common.  A <term>vector image</term>, in contrast, is a
list of geometrical objects, such as lines, circles, arcs, or even
cubes.  These are much more difficult to produce, and so are mainly
encountered as the output of sophisticated systems such as architectural
and engineering CAD programs.</p><p>Raster images are difficult to modify because by definition they only
encode single points:  a line, for example, cannot grow or shrink as
such, since it is not identified as such.  Only its component parts are
identified, and only they can be manipulated.  Therefore the resolution
or dot-size of a raster image is important, which is not the case with
vector images.  It is also far more difficult to convert raster images
to vector images than to perform the opposite conversion.  Raster images
generally require more storage space than vector images, and a wide
variety of methods exists for compressing them; the variation in these
methods leads to corresponding variations in representations for storage
and transmission of raster images.</p><p>Motion video usually consists of a long series of raster images.
Data compression is even more effective on video than on single raster
images (mainly owing to redundancy which arises from the usual similarity
of adjacent frames).  Notations for representing full-motion video
are hotly debated at this time, and any user of these Guidelines would
do well to obtain up-to-date expert advice before undertaking a project
using them.</p><p>The compression methods used with any of these image types may be
<soCalled>lossy</soCalled> or <soCalled>lossless</soCalled>.  Methods
for <term>lossy compression</term> save space by discarding a small
portion of the image's detail, such as fine distinctions of shading.
When decompressed, therefore, such an image will be only a close
approximation of the original.  In contrast, <term>lossless
compression</term> guarantees that the exact uncompressed image will be
reproducible from the compressed form:  only truly redundant information
is removed.  In general, therefore, lossless compression does not save
quite so much space as lossy compression, though it does guarantee
fidelity to the original uncompressed image.</p><p>Raster images may be characterized by their <term>resolution</term>,
which is the number of dots per inch used to represent the image.
Doubling the resolution will give a more precise image, but also
quadruple the storage requirement (before compression), and affect
processing time for any operations to be performed, such as displaying
an image for a reader.  Motion video also has resolution in time:  the
number of frames to be shown per second.  Encoders should consider
carefully what resolution(s) and frame rate(s) to use for particular
applications; these Guidelines express no recommendation in this matter,
save the universal ones of consistency and documentation.</p><p>Within any image, it is typical to refer to locations via Cartesian
co-ordinate axes:  values for x, y, and sometimes z and/or time.  These
Guidelines provide for this via the <code tei="yes" type="kw">SPACE</code> keyword
of the extended pointing mechanism discussed in section <xref target="SAXR"/>.  However, graphic notations vary in whether co-ordinates
count from left-to-right and top-to-bottom, or another way.  They also
vary in whether co-ordinates are considered real (inches, millimeters,
and so on), or virtual (dots).  These Guidelines do not recommend any of
these methods over another, but all decisions made should be applied
consistently, and documented in the <gi tei="yes">encodingDesc</gi> section of the
TEI header.<note source="auth" place="display" anchored="Y">No special purpose element is provided for this purpose
by the current version of the Guidelines.  The information should be
provided as one or more distinct paragraphs at the end of the
<gi tei="yes">encDecl</gi> element described in section <xref target="HD5"/>.</note></p><p>The way in which the color of an image is rendered also varies
greatly.  In monochrome images every displayed point is either black or
white.  In <term>gray-scale</term> images, each point is rendered in
some shade of gray, the number of shades varying from system to system.
In true polychrome images, points are rendered in different colours,
again with varying limitations affecting the number of distinct shades
and the means by which they are displayed.</p></div2><div2 id="FTGRNO" name="Anthony" ref="Y"><head>Graphic Image Formats</head><p>As noted above, there exists a bewildering variety of different
graphics formats, and the following list is in no way exhaustive.
Moreover, inclusion of any format in this list should not be taken as
indicating endorsement by the TEI of this format or any products
associated with it.  With the exception of CGM, all the formats listed
here are proprietary to a greater or lesser extent and cannot therefore
be regarded as standards in any meaningful sense.  They are however
widely used by many different vendors.</p><p>The following formats are widely used at the present time, and likely to
remain supported by more than one vendor's software:
 
<list type="simple"><item>CGM:  Computer Graphics Metafile</item><item>PICT:  Macintosh drawing format</item><item>TIFF:  Tagged Image File Format</item><item>GIF:  Graphics Interchange Format</item><item>PBM:  Portable Bit Map</item><item>PCX:  IBM PC raster format</item><item>BMP:   Microsoft bitmap format</item><item>JPEG:  Joint Photographic Expert Group</item><item>QuickTime:  Apple real-time image system</item><item>Photo-CD:  Kodak Photo Compact Disk format</item></list></p><p>Brief descriptions of all the above are given below.  Where possible,
current addresses or other contact information are shown for the
originator of each format.  Many formal standards, especially those
promulgated by ISO and many related national organizations (ANSI, DIN,
BSI, and many more), are available from those national organizations.
Addresses may be found in any standard organizational directory for the
country in question.
 <!-- One such source is the American National Standards       --><!-- Institute (ANSI), 11 West 42nd Street, 13th floor, New   --><!-- York, NY 10036 USA, phone 212-642-4900, fax              --><!-- 212-348-0023.</p>                                        --></p><p>For each format, a sample notation declaration is given, using a
formal public identifier constructed from the best information available
at the date of publication.  It is recommended that such formal public
identifiers always be used in the interchange of documents between
sites.  Unless otherwise noted, however, these formal public identifiers
have been formulated by the TEI, and not by the owners of the
notation, as is indicated by the use of <cited>TEI</cited> as the
owner identifier.
If more recent versions of these formal public identifiers, or versions
promulgated by the owners of the notation, are available at the time of
document interchange, they should be used in preference to those shown
here.</p><p>Support for formal public identifiers varies somewhat among existing
SGML systems; for local processing, the notation declaration may
therefore need to include a system identifier in addition to the formal
public identifier.  The documentation for the SGML system in use should
be consulted for details.</p><div3 name="subsection" ref="Y"><head>Vector Graphic Formats</head><list type="gloss"><label>CGM:  Computer Graphics Metafile</label><item>This format is a popular representation for vector graphics
specified by an ISO standard, ISO 8632:1987, amended in 1990.
The standard defines binary, character, and plain-text encodings;
the non-binary forms are safer for blind interchange,
especially over networks.  Documentation on CGM is available from ISO
and from its member national bodies such as AFNOR, ANSI, BSI, DIN, JIS,
etc.  Sample declarations:
 
<eg><![CDATA[<!NOTATION cgm PUBLIC
    'ISO 8632:1987//NOTATION Computer Graphics Metafile//EN'>
 
<!NOTATION cgmchar  PUBLIC
    'ISO 8632-2:1987//NOTATION Character encoding//EN'>
<!NOTATION cgmbin   PUBLIC
    'ISO 8632-3:1987//NOTATION Binary encoding//EN'>
<!NOTATION cgmclear PUBLIC
    'ISO 8632-4:1987//NOTATION Clear text encoding//EN'>]]></eg></item><label>PICT:  Macintosh drawing format</label><item>This format is universally supported on Macintosh(tm) systems, and
readable by a limited range of software for other systems.
Documentation is available from Apple Computer Company, Cupertino,
California USA.
 
<eg><![CDATA[<!NOTATION pict PUBLIC
    '-//TEI//NOTATION PICT:  Macintosh Drawing Format//EN'>]]></eg>
 </item></list></div3><div3 name="subsection" ref="Y"><head>Raster Graphic Formats</head><list type="gloss"><label>TIFF:  Tagged Image File Format</label><item>Currently the most widely supported raster image format,
especially for black and white images, TIFF is also one of the few
formats commonly supported on more than one operating system.  The
drawback to TIFF is that it actually is a wrapper for several formats,
and some TIFF-supporting software does not support all variants.  TIFF
files may use LZW, CCITT Group 4, or PackBits compression methods, or
may use no compression at all.  Also, TIFF files may be monochrome,
greyscale, or color.  All such options should be specified in prose at
the end of the <gi tei="yes">encodingDesc</gi> section of the TEI header for any
document including TIFF images.  TIFF is owned by Aldus Corporation.
Documentation on TIFF is available from them at Craigcook Castle,
Craigcook Road, Edinburgh EH4 3UH, Scotland, or 411 First Avenue
South, Seattle, Washington 98104 USA.
 
<eg><![CDATA[<!NOTATION tiff PUBLIC
   '-//TEI//NOTATION Aldus Tagged Image File Format//EN'>]]></eg></item><label>GIF:  Graphics Interchange Format</label><item>Color raster images are widely available in this form, which was
created by CompuServ Information Services, but has by now been
implemented for many other systems as well.  Documentation on GIF is
copyright by, and is available from, CompuServe Incorporated, Graphics
Technology Department, 5000 Arlington Center Boulevard, Columbus, Ohio
43220 USA.
 
<eg><![CDATA[<!NOTATION gif PUBLIC
  '-//TEI//NOTATION
  Compuserve Graphics Interchange Format//EN' >]]></eg></item><label>PBM:  Portable Bit Map</label><item>PBM files are easy to process, eschewing all compression in favor
of transparency of file format.  PBM files can, of course, be compressed
by generic file-compression tools for storage and transfer.  Public
domain software exists which will convert many other formats to and from
PBM.  Documentation on PBM is copyright by Jeff Poskanzer, and is available
widely on the Internet.
 
<eg><![CDATA[<!NOTATION pbm PUBLIC
  '-//TEI//NOTATION Jeff Poskanzer, Portable Bit Map//EN' >]]></eg></item><label>PCX:  IBM PC raster format</label><item>This format is used by most IBM PC paint programs, and supports
both monochrome and color images.  Documentation is available from
ZSoft Corporation, Technical Support Department, ATTN: Technical
Reference Manual, 450 Franklin Rd. Suite 100, Marietta, GA 30067 USA.
 
<eg><![CDATA[<!NOTATION pcx PUBLIC
  '-//TEI//NOTATION PCX:  ZSoft IBM PC Raster Graphics Format//EN' >]]></eg>
 </item><label>BMP:   Microsoft bitmap format</label><item>This format is the standard raster format for computer using
Microsoft Windows (tm) or Presentation Manager (tm).  Documentation
is available from Microsoft Corporation.
 
<eg><![CDATA[<!NOTATION bmp PUBLIC
  '-//TEI//NOTATION BMP:  Microsoft Bitmap Graphics Format//EN' >]]></eg>
 </item></list></div3><div3 name="subsection" ref="Y"><head>Photographic and Motion Video Formats</head><list type="gloss"><label>JPEG:  Joint Photographic Expert Group</label><item>This standard is sponsored by CCITT and by ISO.  It is ISO/IEC
Draft International Standard 10918-1, and CCITT T.81.  It handles
monochrome and color images with a variety of compression techniques.
JPEG per se, like CCITT Group IV, must be encapsulated before
transmission; this can be done via TIFF, or via the JPEG File
Interchange Format (JFIF).
 
<eg><![CDATA[<!NOTATION JPEG PUBLIC
  'ISO DIS 10918//NOTATION JPEG Graphics Format//EN' >]]></eg>
 </item><label>QuickTime:  Apple real-time image system</label><item>QuickTime is a proprietary method introduced by Apple Computer
Company to synchronize the display of various data.  The data can
include frames of video, sound, lighting control equipment, and other
things.  Viewers for QuickTime productions are available for Apple and
other computers.  Further information is available from Apple Computer
Incorporated, 10201 North de Anza Boulevard MS 23AQ, Cupertino,
California 95014 USA.
 
<eg><![CDATA[<!NOTATION QuickTime PUBLIC
  '-//TEI//NOTATION Apple QuickTime Video Data Format//EN' >]]></eg>
 </item><label>Photo-CD:  Kodak Photo Compact Disk format</label><item>This format was introduced by Kodak for rasterizing photographs
and storing them on CD-ROMs (about one hundred 35mm file images fit on
one disk), for display on televisions or CD-I systems.  Information on
Photo-CD is available from Kodak Limited, Research and Development,
Headstone Drive, Harrow, Middlesex HA1 4TY, UK.
 
<eg><![CDATA[<!NOTATION pcx PUBLIC
  '-//TEI//NOTATION
  Eastman Kodak Photo-CD Raster Graphics Format//EN' >]]></eg>
 </item></list><p>As noted above, the reader will encounter many, many other graphics
formats.  Other formats are not recommended for data interchange
according to the TEI scheme at this time, but may be included in a TEI
document without affecting its conformance in other respects, provided
that a notation declaration is provided.</p></div3></div2><!-- delete remainder for now --><!-- <div3><head>Other (Non-Recommended) Formats</head> --><!-- <div4><head>Vector Graphic Formats</head> <list type=gloss> --><!-- <label>IGES: Initial Graphics Exchange Specification</label> --><!-- <item><p>This format was introduced by the American National --><!-- Bureau of Standards (NBS) and the American National --><!-- Standards Institute (ANSI); versions exists from 1980, 1983, --><!-- 1986, and 1987.  It is used for exchange of some engineering --><!-- and product data, and can include both vector and raster --><!-- representations.  ASCII and binary encodings are defined. --><!-- <p>IGES will likely be superseded by the STEP effort: --><!-- Standard for the Exchange of Product Data.  This effort --><!-- involves a wider range of international expertise, and is --><!-- being developed through ISO as ISO CD 10303.  The American --><!-- effort relating to STEP is called PDES: --><!--  Product Data Exchange using STEP.</item> </list> </div4> --><!-- <div4><head>Raster Graphic Formats</head> <list type=gloss> --><!-- <label>EPS: Encapsulated Postscript</label> <item>This is a --><!-- variant of Postscript, in which each page image program is --><!-- preceded by a bitmapped image that can be displayed via --><!-- software much simpler than a full Postscript --><!-- interpreter.</item> <label>CALS: US Department of Defense --><!-- CALS raster</label> <item><p>These files are compressed --><!-- using CCITT Group 4 compression (the same method used by fax --><!-- machines and some TIFF files.  However, a CALS-specific --><!-- header comes before the data, to specify resolution, --><!-- orientation, and other information.  <p>The header of a CALS --><!-- Group IV raster image is defined in US Department of Defense --><!-- standard MIL-M-28002.  The compression itself is defined in --><!-- CCITT standard T.30, found in Fascicle VII.3: Terminal --><!-- Equipment and Protocols for Telematic Services, published --><!-- 1989 in Geneva by the International Telecommunication --><!-- Union.  It derives from the work of the IXth Plenary --><!-- Assembly of the International Telegraph and Telephone --><!-- Consultative Committee, Melbourne, 14-25 November 1988. --><!--  ISBN 92-61-0361102.</item> <label>SunRaster: Sun --><!-- Microsystems(tm) format</label> <item>This is supported on --><!-- Sun and some other Unix systems.  There are monochrome and --><!-- color variants.  Sun Microsystems owns this formats, and can --><!-- be reached at:</item> <label>DCX:</label><item> A multi-page --><!-- version of PCX</item> <label>MacPaint: Macintosh simple --><!-- raster format <item>A bitmap-only subset of Macintosh PICT --><!-- format, seldom used.  </item> <label>MSPAINT:<item> --><!-- Microsoft paint <label>WPMETA: WordPerfect Metafile</label> --><!-- <item>A format used by the WordPerfect word-processing --><!-- system for raster images embedded within files.  Further --><!-- information is available from WordPerfect --><!-- Corporation,....</item> <label>XWD: X Window Dump --><!-- format</label> <item>A format used on X Windows systems, --><!-- mainly for storing snapshots of windows displayed on screen --><!-- (as for inclusion when writing software --><!-- documentation).</item> </list> </div4> <div4><head>Page --><!-- layout formats</head> <list type=gloss> <label>PostScript: --><!-- Adobe printer image format</label> <item>This is a --><!-- printer-control language supported by most current --><!-- high-resolution printers.  It is actually a programming --><!-- languages, and so can be used to represent either raster or --><!-- vector graphic images of pages, or anything else.  A --><!-- Postscript interpreter is required to interpret its programs --><!-- and produce a displayed image.  It is owned by Adobe Systems --><!-- Incorporated, and exists in two flavors: Level 1 as of 1985, --><!-- and Level 2 as of 1990.  See also EPS, below.</item> --><!-- <label>HPGL</label> <item>A printer control language --><!-- originated by Hewlett-Packard Corporation.  </item> </list> --><!-- </div4></div3> <div3><head>Other Formats</head> <p>The --><!-- reader may encounter a wide variety of other formats.  Some --><!-- are listed here, and none of these are currently recommended --><!-- by these Guidelines.  However, should an encoder find it --><!-- necessary to use such a format the name specified here must --><!-- be used as the notation name. --><!--  Countless other formats are used by particular companies or --><!-- programs; those are omitted as being, by definition, --><!-- unportable and inappropriate for data interchange.</p> --><!-- <p>Vector formats include: <list type=gloss> --><!-- <label>DDES2-IADD:<item>Digital Data Exchange --><!-- Specification-International Association of --><!-- Diecutting-Diemaking.  ANSI IT8.6-1991, used primarily in --><!-- North America for exchanging box-manufacturing data. --><!-- <label>CFF2<item>Common File Format: A European format for --><!-- vector image and text interchange, based on DDES-IADD. --><!-- <label>DXF<item>Drawing Interchange Format: Owned and used --><!-- by AutoDesk Incorporated (a maker of engineering software), --><!-- 2320 Marinship Way, Sausalito, California 94965 USA. --><!-- <label>GKS<item>Graphical Kernel System.  ISO standard 7942 --><!-- (1985), with amendments pending.  Essentially a programming --><!-- library to support displaying two-dimensional graphics; --><!-- supported on a variety of workstations. --><!-- <label>GKS-3D<item>Graphical Kernel System extension for --><!-- 3-dimensions.  ISO standard 8805 (1988).  Can operate on --><!-- 2-dimensional GKS constructs transparently. --><!-- <label>PHIGS<item>Programmers Hierarchical Interactive --><!-- Graphics System: ISO standard 9592 (1990).  Essentially a --><!-- programming library to support interactive graphics. --><!-- PHIGS-PLUS is an extended variant.  <label>SET<item>Standard --><!-- dEchange et de Transfert: Sponsored by Association Francaise --><!-- De Normalisation (AFNOR), Tour Europe, Cedex 7, F-92049 --><!-- Paris la Defense, France.  <label>VDAFS<item>VDA Surface --><!-- Interface: Versions 1.0 (1986) sponsored by DIN (Germany); --><!-- extensions under consideration.  <label> Renderman<item>A --><!-- format used by Pixar Corporation) </list> <p>Raster formats --><!-- include: <list type=gloss> <label>DES<item>Digital Data --><!-- Exchange Specifications: For use with magnetic tapes. --><!-- Sponsored by ANSI IT8.1.  <label>IPI-OOF<item>Image --><!-- Processing and Interchange: Image Interchange Facility.  ISO --><!-- draft standard 12087; this format has apparently not yet --><!-- been implemented.  <label>JBIG<item>Joint Bilevel Image --><!-- Group: ISO draft standard 11544, and CCITT T.82.  Usage --><!-- unknown.  <label>ACR-NEMA <item> Used for exchanging --><!-- uncompressed medical raster images such as CT, MR, --><!-- ultrasound, and PET images.  Provides for extensive --><!-- cataloging information associated with images.  Available as --><!-- ACR-NEMA Standards Publication No 300-1988 from National --><!-- Electrical Manufacturers Association, 2101 L Street, N.W., --><!-- Washington, DC 20037 USA <label>FITS<item>Flexible Image --><!-- Transfer System: A NASA standard (NSDSSO 100-0.1) for --><!-- exchanging astronomical images.  Available from NASA Science --><!-- Data Systems Standards Office, Code 933, NASA Goddard Space --><!-- Flight Center, Greenbelt, MD 20771 USA <label>TARGA <item> --><!-- Apparently a binary image encapsulation format used by AT --><!-- &amp;T.  Information available from Truevision Customer --><!-- Service at (317) 576-8118, or AT&amp;T Electronic --><!-- Photography and Imaging Center, 2002 Wellesley Ave., --><!-- Indianapolis, IN 42619 USA.  </list> </div3> --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ftgra.odd ??></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ft.odd ??><!-- 22 Formulae and Tables --><?tei:SOF p2cc.odd ??><!-- Revisions:                                               --><!-- 26 mar: LB: read thro: title change --><!-- 28 feb: fixed typos noted by DTL --><!-- 93-06-03 : MSM : change entity names for parts           --><!-- 31 may: LB: added credit for stig --><!-- 93-03-11 : MSM : last minute changes as per LB           --><!-- 93-03-10 : MSM : revise:  add refs to CB, DS, recast     --><!-- 93-03-08 : MSM : embed entity refs here, not in driver   --><!--                                                          --><!-- Date: Sat, 06 Mar 1993 21:59:42 +0000                    --><!-- From: Lou Burnard < lou@vax.ox.ac.uk >                   --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- CC: lou@vax.ox.ac.uk                                     --><!-- Subject: CC.odd (2 of 10)                                --><!-- 1 mar 93  split out into CC/CB --><!-- 26 Nov 92 : LB started draft  --><div1 id="CC" n="23" name="Faisal" ref="Y"><head>Language Corpora</head><p>The term <term>language corpus</term> is used to mean a number of
rather different things.  It may refer simply to any collection of
linguistic data (written, spoken, or a mixture of the two), although
many practitioners prefer to reserve it for collections which have
been organized or collected with a particular end in view, generally to
characterize a particular state or variety of one or more languages.
Because opinions as to the best method of achieving this goal differ,
various subcategories of corpora have also been identified.  For our
purposes however, the distinguishing characteristic of a corpus is that
its components have been selected or structured according to some
conscious set of design criteria.
 </p><p>These design criteria may be very simple and undemanding, or very
sophisticated.  A corpus may be intended to represent (in the
statistical sense) a particular linguistic variety or sublanguage, or it
may be intended to represent all aspects of some assumed
<soCalled>core</soCalled> language.  A corpus may be made up
of whole texts or of fragments or text samples.  It may be a
<soCalled>closed</soCalled> corpus, or an <soCalled>open</soCalled> or
<soCalled>monitor</soCalled> corpus, the composition of which may change
over time.  However, since an open corpus is of necessity finite at any
particular point in time, the only likely effect of its expansibility
from the encoding point of view may be some increased difficulty in
maintaining consistent encoding practices (see further section <xref target="CCREC"/>). For simplicity, therefore, our discussion largely
concerns ways of encoding closed corpora, regarded as single but
composite texts.
 <!-- Change intro to next para, modify definition of unitary  --><!-- text (SMALLEST whole).  -MSM                             -->
 </p><p>Language corpora are regarded by these Guidelines as
<term>composite texts</term> rather than <term>unitary texts</term>
(on this distinction, see chapter <xref target="DS"/>).
This is because although
each discrete sample of language in a corpus clearly has a claim to be
considered as a text in its own right, it is also regarded as a
subdivision of some larger object, if only for convenience of analysis.
Corpora share a number of characteristics with other types of composite
texts, including anthologies and collections.  Most notably, different
components of composite texts may exhibit different structural
properties (for example, some may be composed of verse, and others of
prose), thus potentially requiring elements from different TEI bases.
Composite texts are thus especially likely to require the techniques for
combining base tag sets described in section <xref target="STCO"/>.
 </p><p>Aside from these high-level structural differences, and possibly
differences of scale, the encoding of language corpora and the encoding
of individual texts present identical sets of problems.  Any of the
encoding techniques and elements presented in other chapters of these
Guidelines may therefore prove relevant to some aspect of corpus
encoding and may be used in corpora.  However, we do not repeat here the
discusssion of such fundamental matters as the representation of
multiple character sets (see chapter <xref target="CH"/>); nor attempt to
summarize the variety of elements provided for encoding basic structural
features such as quoted or highlighted phrases, cross references, lists,
notes, editorial changes and reference systems (see chapter <xref target="CO"/>).  In addition to these general purpose elements, these
Guidelines offer a range of more specialized sets of tags which may be
of use in certain specialized corpora, for example those consisting
primarily of verse (chapter <xref target="VE"/>), drama (chapter <xref target="DR"/>), transcriptions of spoken text (chapter <xref target="TS"/>),<!-- letters and memoranda (chapter <xref target=LM>)-->
etc.  Chapter <xref target="ST"/> should be reviewed for details of how
these and other components of the Guidelines should be tailored to
create a document type definition appropriate to a given application.
In sum, it should not be asssumed that only the matters specifically
addressed in this chapter are of importance for corpus creators.
 </p><p>This chapter does however include some other material
relevant to corpora and corpus-building, for which no other location
appeared suitable.  It begins with a review of the distinction between
unitary and composite texts, and of the different methods provided by
these Guidelines for representing composite texts of different kinds
(section <xref target="CCDEF"/>).  Section <xref target="CCAH"/> describes a
set of additional header elements provided for the documentation of
contextual information, of importance largely though not exclusively to
language corpora.  This is the additional tag set for language corpora
proper.  Section <xref target="CCAS"/> discusses a mechanism by which
individual parts of the TEI Header may be associated with different
parts of a TEI-conformant text.  Section <xref target="CCAN"/> reviews
various methods of providing linguistic annotation in corpora, with some
specific examples of relevance to current practice in corpus
linguistics.  Finally, section <xref target="CCREC"/> provides some general
recommendations about the use of these Guidelines in the building of
large corpora.
<!-- <note place=foot>Parts of this chapter are derived from --><!-- working papers of the Work Group on Corpora, chaired by --><!-- Douglas Biber, the Work Group on Linguistic Description, --><!-- chaired by D. Terence Langendoen, and the Work Group on --><!-- Spoken Texts, chaired by Stig Johansson.  The membership of --><!-- these work groups is listed in the preface.</note> -->
 <?tei:SOF p2ccdef.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $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             -->
 </p><div2 id="CCDEF" name="Anthony" ref="Y"><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.
 
<tagList style="one-line"><tagDesc tagDoc="TEICORP2"/><tagDesc tagDoc="TEI2"/><tagDesc tagDoc="TEIHEAD" atts="type status creator date.created date.updated"/><tagDesc tagDoc="TEXT"/><tagDesc tagDoc="GROUP"/></tagList>
 
Full descriptions of these may be found in chapter <xref target="ST"/> (for
<gi tei="yes">teiCorpus.2</gi> and <gi tei="yes">tei.2</gi>), chapter <xref target="HD"/> (for
<gi tei="yes">teiHeader</gi>), and chapter <xref target="DS"/> (for <gi tei="yes">text</gi> and
<gi tei="yes">group</gi>); this section discusses their application to composite
texts in particular.
 </p><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><item>collections or anthologies</item><item>poem cycles and epistolary works (novels or essays written
in the form of collections or series of letters)</item><item>otherwise unitary texts, within which one or more subordinate
texts are embedded</item></list>
 
The tags listed above may be combined to encode each of these
varieties of composite text in different ways.
 </p><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><p>The <gi tei="yes">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="yes">tei.2</gi> elements, and the entire corpus is enclosed in a
<gi tei="yes">teiCorpus.2</gi> element.  Each sample has the usual structure for
a <gi tei="yes">tei.2</gi> document, comprising a <gi tei="yes">teiHeader</gi> followed by a
<gi tei="yes">text</gi> element.  The corpus, too, has a corpus-level
<gi tei="yes">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><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 tei="yes">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 <xref target="CCAH"/>, as well as in chapter <xref 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 <xref target="CCAS"/>.
 </p><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 tei="yes">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="yes">tei.2</gi>.
 </p><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 tei="yes">group</gi>
element described below and in section <xref 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 <xref target="CCAHTD"/>,
and those for associating declarations with corpus components described
in section <xref 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><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><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><p>The <gi tei="yes">group</gi> element is provided to simplify the encoding of
collections, anthologies, and cyclic works; as noted above, the
<gi tei="yes">group</gi> element can also be used to record the potentially
complex internal structure of language corpora.  For full description,
see chapter <xref target="DS"/>.
 </p><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="yes">tei.2</gi> and
<gi tei="yes">body</gi> elements.  The embedded text itself may be encoded using
the <gi tei="yes">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 <xref target="DS"/>.<!-- The discussion of embedded texts really belongs in CO.  -MSM -->
 </p><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 <xref target="STCO"/>.

 




<?tei:EOF p2ccdef.odd ??>
<?tei:SOF p2ccah.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $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)                              --><!--                                                          --></p></div2><div2 id="CCAH" name="Anthony" ref="Y"><head>Contextual Information</head><p>Contextual information is of particular importance for collections
or corpora composed of samples from a variety of different kinds of
text. Examples of such contextual information include:  the age, sex
and geographical origins of participants in a language interaction, or
their socio-economic status; the cost and publication data of a
newspaper; the topic, register or factuality of an extract from a
textbook. Such information may be of the first importance, whether as
an organizing principle in creating a corpus (for example, to ensure
that the range of values in such a parameter is evenly represented
throughout the corpus, or represented proportionately to the population
being sampled), or as a selection criterion in analysing the corpus
(for example, to investigate the language usage of some particular
vector of social characteristics).</p><p>Such contextual information is potentially of equal importance for
unitary texts, and these Guidelines accordingly make no particular
distinction between the kinds of information which should be gathered
for unitary and for composite texts.  In either case, the information
should be recorded in the appropriate section of a TEI Header, as
described in chapter <xref target="HD"/>.  In the case of language corpora,
such information may be gathered together in the overall corpus header,
or split across all the component texts of a corpus, in their individual
headers, or divided between the two.  The association between an
individual corpus text and the contextual information applicable to it
may be made in a number of ways, as further discussed in section <xref target="CCAS"/> below.</p><p>Chapter <xref target="HD"/>, which should be read in conjunction with
the present section, describes in full the range of elements available
for the encoding of information relating to the electronic file itself,
for example its bibliographic description and those of the source or
sources from which it was derived (see section <xref target="HD2"/>);
information about the encoding practices followed with the corpus, for
example its design principles, editorial practices, reference system
etc.  (see section <xref target="HD5"/>); more detailed descriptive
information about the creation and content of the corpus, such as the
languages used within it and any descriptive classification system used
(see section <xref target="HD4"/>); and version information documenting any
changes made in the electronic text (see section <xref target="HD6"/>).</p><p>In addition to the elements defined by chapter <xref target="HD"/>,
several other elements can be used in the TEI header if the additional
tag set defined by this chapter is invoked.  These additional tags make
it possible to characterize the social or other situation within which a
language interaction takes place or is experienced, the physical setting
of a language interaction, and the participants in it.  Though this
information may be relevant to, and provided for, unitary texts as well
as for collections or corpora, it is more often recorded for the
components of systematically developed corpora than for isolated texts,
and thus the additional tag set is referred to as being <q>for language
corpora</q>.  Included in this tag set are the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="TEXTDESC"/><tagDesc tagDoc="PARTDESC"/><tagDesc tagDoc="SETTDESC"/></tagList>
 
These elements form an optional extension to the <gi tei="yes">profileDesc</gi>,
defined in section <xref target="HD4"/> and are further described in the
remainder of this section. They are formally defined as follows:
 
<dtdFrag id="DCCHDR" n="Header extensions for Corpus Texts" file="teicorp2"><tagDecl tagDoc="TEXTDESC"/><tagDecl tagDoc="PARTDESC"/><tagDecl tagDoc="SETTDESC"/></dtdFrag>
 <!-- any other header extensions here --><!-- err, more stuff to go in here --></p><p>The additional tag set for language corpora will be invoked, thus
enabling the use of these elements, if a parameter entity called
<ident tei="yes" type="pe">TEI.corpus</ident> is declared with the value <code tei="yes" type="kw">INCLUDE</code>, somewhere within the DTD subset.  If the
document is structured as a TEI corpus (that is, using the
<gi tei="yes">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" name="subsection" ref="Y"><head>The Text Description</head><p>The <gi tei="yes">textDesc</gi> element provides a full description of the
situation within which a text was produced or experienced, and thus
characterizes it in a way relatively independent of any <foreign>a
priori</foreign> theory of text-types.  It is provided as an alternative
or a supplement to the common use of descriptive taxonomies used to
categorize texts, which is fully described in section <xref target="HD43"/>, and section <xref target="HD55"/>.  The description is
organized as a set of values and optional prose descriptions for the
following eight <term>situational parameters</term>, each represented by
one of the following eight elements:
 
<tagList style="one-line"><tagDesc tagDoc="CHANNEL" atts="mode"/><tagDesc tagDoc="CONSTITN" atts="type"/><tagDesc tagDoc="DERIVATN" atts="type"/><tagDesc tagDoc="DOMAIN" atts="type"/><tagDesc tagDoc="FACTUAL" atts="type"/><tagDesc tagDoc="INTERACT" atts="type active passive"/><tagDesc tagDoc="PREPNESS" atts="type"/><tagDesc tagDoc="PURPOSE" atts="type degree"/></tagList></p><p>A TEI-conformant text description contains each of the above
elements, supplied in the order specified. Except for the
<gi tei="yes">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 source="auth" place="display" anchored="Y">Schemes similar to that proposed here were developed
in the 1960s and 1970s by researchers such as Hymes, Halliday, and
Crystal and Davy, but have rarely been implemented; one notable
exception being the pioneering work on the Helsinki Diachronic Corpus
of English, on which see <citation> <author>M. Kyt&ouml; and
M. Rissanen,</author> <title.p>The Helsinki Corpus of English
Texts,</title.p> in <title>Corpus Linguistics: hard and soft</title>,
ed.  <editor>M. Kyt&ouml;, O. Ihalainen, and M. Rissanen</editor>
(Amsterdam: Rodopi, 1988).  </citation> </note>
 
<list type="bullets"><item> it enables a relatively continuous characterization of texts (in
contrast to discrete categories based on type or topic)</item><item>it enables meaningful comparisons across corpora</item><item>it allows analysts to build and compare their own text-types
based on the particular parameters of interest to them</item><item>it is equally applicable to spoken and written texts</item></list></p><p>Two alternative approaches to the use of these parameters are
supported by these Guidelines.  One is to use pre-existing taxonomies
such as those used in subject classification or other types of text
categorization.
 <!-- NOT descriptive cataloguing -msm -->
 
Such taxonomies may also be appropriate for the description of the
topics addressed by particular texts.  Elements for this purpose are
described in section <xref target="HD43"/>, and elements for defining or
declaring such classification schemes in section <xref target="HD55"/>.  A
second approach is to develop an application-specific set of
<term>feature structures</term> and an associated <term>feature system
declaration,</term> as described in chapters <xref target="FS"/> and<xref target="FD"/>
.
 <!-- However, in particular where a pre-existing descriptive  --><!-- typology of this kind was used as the organizing         --><!-- principle of a corpus or collection, these Guidelines    --><!-- recommend that its components be additionally            --><!-- re-expressed in terms of the parameters listed here.     --></p><p>Where the organizing principles of a corpus or collection so permit,
it may be convenient to regard a particular set of values for the
situational parameters listed in this section as forming a
<term>text-type</term> in its own right; this may also be useful where
the same set of values applies to several texts within a corpus.  In
such a case, the set of text-types so defined should be regarded as a
<term>taxonomy</term>.  The mechanisms described in section <xref target="HD55"/> may be used to define hierarchic taxonomies of such
text-types, provided that the <gi tei="yes">catDesc</gi> component of the
<gi tei="yes">category</gi> element contains a <gi tei="yes">textDesc</gi> element rather
than a prose description.  Particular texts may then be associated with
such definitions using the mechanisms described in sections <xref target="HD43"/>.
 <!-- These subcomponents provide information about the        --><!-- context within which the text is produced or situated    --><!-- which, taken together, are felt to characterize it in    --><!-- analytically helpfulway.  Information about the          --><!-- participants in a language interaction and their         --><!-- physical or temporal setting are provided by two other   --><!-- components of the < gi >profile.desc< /gi > element      --><!-- (see sections < xref target=AHPA > and < xref            --><!-- target=AHSE > below).                                    --></p><p>Using these situational parameters, an informal domestic
conversation might be characterized as follows:
 
<eg><![CDATA[<textDesc id=T1 n='Informal domestic conversation'>
  <channel mode=s>informal face-to-face conversation</channel>
  <constitution type=single>each text represents a continuously
        recorded interaction among the specified participants
        </constitution>
  <derivation type=original>
  <domain type=domestic>plans for coming week, local affairs</domain>
  <factuality type=mixed>mostly factual, some jokes</factuality>
  <interaction type=complete active=plural passive=many>
  <preparedness type='spontaneous'>
  <purpose type=entertain degree=high>
  <purpose type=inform degree=medium>
 </textDesc>]]></eg>
 <!-- Content of sit parms added. Please check. -MSM --></p><p>The following example demonstrates how the same situational
parameters might be used to characterize a novel:
 
<eg><![CDATA[   <textDesc n='novel'>
     <channel mode=w>print; part issues</channel>
     <constitution type=single>
     <derivation type=original>
     <domain type=art>
     <factuality type=fiction>
     <interaction type=none>
     <preparedness type=prepared>
     <purpose type=entertain degree=high>
     <purpose type=inform degree=medium>
  </textDesc>]]></eg>
 
 <!-- need more examples -->
 
The formal declarations for these elements are given below:
<dtdFrag id="DCCAHTD" n="Text description" contin="DCCHDR"><tagDecl tagDoc="CHANNEL"/><tagDecl tagDoc="CONSTITN"/><tagDecl tagDoc="DERIVATN"/><tagDecl tagDoc="DOMAIN"/><tagDecl tagDoc="FACTUAL"/><tagDecl tagDoc="INTERACT"/><tagDecl tagDoc="PREPNESS"/><tagDecl tagDoc="PURPOSE"/></dtdFrag>
 <!-- Not sure if this para is necessary or advisable. -LB     --><!-- < p >The content model for the < gi >textDesc< /gi >     --><!-- element is defined by the parameter entity %tdModel.     --><!-- If so desired, the encoder may change the set of         --><!-- parameters used to define < gi >textDesc< /gi > by       --><!-- altering the definition of this entity, as further       --><!-- described in chapter < xref target=MD >.                 -->
 <!-- some change along these lines is desirable for P4 (LB) --></p></div3><div3 id="CCAHPA" name="subsection" ref="Y"><head>The Participants Description</head><p>The <gi tei="yes">particDesc</gi> element in the <gi tei="yes">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 tei="yes">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 tei="yes">particDesc</gi> contains one or more
<gi tei="yes">person</gi> or <gi tei="yes">personGrp</gi> elements, followed by an
optional <gi tei="yes">particLinks</gi> element, as described below:
 
<tagList style="one-line"><tagDesc tagDoc="PERSON" atts="role sex age"/><tagDesc tagDoc="PERSGRP" atts="role sex age size"/><tagDesc tagDoc="PARTIREL"/></tagList>
 <!-- I have now removed members attrib :  It unnecessarily    --><!-- complicates notion of partic.group Would be better done  --><!-- by nesting participants if we really wanted to do it.    --><!-- Best define partic.grp as simply a partic which happens  --><!-- to have several legs (LB)                                --></p><p>Both <gi tei="yes">person</gi> and <gi tei="yes">personGrp</gi> elements have the same
substructure.  This may be a prose description, or, more formally, a
series of specialized subelements providing more specific details.
Such details will vary enormously for different kinds of analysis; the
set of demographic characteristics presented here as sub-elements
should therefore be regarded as providing only an indication of the
kinds of descriptive information which have been found to be generally
useful, for example in socio-linguistics.  Users of these Guidelines
are free to extend or modify this set of demographic characteristics,
by redefining the parameter entity <term>m.demographics</term>,
associated with the class <term>demographics</term>, as further
described in chapter <xref target="MD"/>.  Where well-known
classification schemes exist, e.g. for socio-economic class or
occupation, these should be used and may be documented in the same way
as for text classification (see section <xref target="HD55"/>)
 <!-- Though I havent the faintest idea how.                   --><!-- Should we allow for a catRef within partic/partic.grp? (LB) --><!-- No, just use SCHEME and CODE attributes on OCCUPATION    --><!-- and SOCECSTATUS.  -MSM                                   --></p><p>The following elements are the default members of the class
<ident tei="yes" type="class">demographics</ident>:
 
<tagList style="one-line"><!-- removed  name, persname, placename now that ND is back --><tagDesc tagDoc="BIRTH" atts="date"/><tagDesc tagDoc="FRSTLANG"/><tagDesc tagDoc="LANGKNOW"/><tagDesc tagDoc="RESIDENC"/><tagDesc tagDoc="EDUCN"/><tagDesc tagDoc="AFFILIAT"/><tagDesc tagDoc="OCCUPAT" atts="scheme code"/><tagDesc tagDoc="SOCECSTA" atts="scheme code"/></tagList></p><p>For example, an individual might be described informally by the
following <gi tei="yes">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 tei="yes">taxonomy</gi> element within the
<gi tei="yes">textClass</gi> element; see <xref target="HD55"/>), the same individual
might more formally be described as follows:
 
<eg><![CDATA[<person id=P1 sex=F age='mid'>
  <birth date='1950-01-12'>
     <date>12 Jan 1950</date>
     <name type=place>Shropshire, UK</name>
  </birth>
  <firstLang>English</firstLang>
  <langKnown>French</langKnown>
  <residence>Long term resident of Hull</residence>
  <education>University postgraduate</education>
  <occupation>Unknown</occupation>
  <socecstatus scheme=PEP code=B2>
</person>]]></eg></p><p>Dates and names of persons or places, if included in the prose
description, may be encoded using either the general purpose
<gi tei="yes">date</gi>, <gi tei="yes">name</gi> or <gi tei="yes">rs</gi> elements discussed in
section <xref target="CONA"/>, or the more specialised and detailed
elements provided by chapter <xref target="ND"/>. In the latter case, the
additional tag set for names and dates must be enabled together with
that for language corpora.</p><p>An identified character in a drama or a novel might be defined using
a subset of the same tags as follows:<note source="auth" place="display" anchored="Y">It is particularly useful to
define participants in a dramatic text in this way, since it enables the
<att tei="yes">who</att> attribute to be used to link <gi tei="yes">sp</gi> elements to
definitions for their speakers; see further section <xref target="DRSP"/>.</note>
 
<eg><![CDATA[  <person id=EM01 sex=F age=young>
  <p><name>Emma Woodhouse</name>
  </person>]]></eg></p><p>As noted above, the <gi tei="yes">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 tei="yes">relation</gi> element, as described below:
 
<tagList style="one-line"><tagDesc tagDoc="RELATION" atts="type desc active passive mutual"/></tagList></p><p>A <term>relationship</term>, as defined here, may be any kind of
describable link between specified participants, for example a social
relationship (such as employer/employee), a personal relationship
(such as sibling, spouse, etc.) or something less precise such as
<q>possessing shared knowledge</q>.  A relationship may be
<term>mutual</term>, in that all the participants engage in it on an
equal footing (for example the <q>sibling</q> relationship); or it may
not be if participants are not identical with respect to their role in
the relationship (for example, the <q>employer</q> relationship).  For
non-mutual relationships, only two kinds of role are currently
supported; they are named <term>active</term> and
<term>passive</term>.  These names are chosen to reflect the fact that
non-mutual relations are <term>directed</term>, in the sense that they
are most readily described by a transitive verb, or a verb phrase of
the form <cited>is X of</cited> or <cited>is X to</cited>.  The
subject of the verb is classed as <term>active</term>; the direct
object of the verb, or the object of the concluding preposition, as
<term>passive</term>.  Thus parents are <q>active</q> and children
<q>passive</q> in the relationship <q>parent</q> (interpreted as
<cited>is parent of</cited>); the employer is <q>active</q>, the
employee <q>passive</q>, in the relationship <cited>employs</cited>.
These relationships can be inverted: parents are <q>passive</q> and
children <q>active</q> in the relationship <cited>is child of</cited>;
similarly <q>works for</q> inverts the active and passive roles of
<q>employs</q>.
 <!-- ... in the sense that one group of participants is seen  --><!-- as active in the relationship, and another as passive,   --><!-- for example, parents are seen as < q >active< /q > in    --><!-- the < q >parent< /q > relationship, and children as < q  --><!-- >passive< /q >.                                          -->
 <!--   Is this enough? Is it too much? I considered defining --><!--   a role relationship within relation but couldnt face it --></p><p>For example:
<eg><![CDATA[<particLinks>
  <relation desc='parent' active='P1 P2'
         passive='P3 P4' mutual=N>
  <relation desc='spouse' active='P1 P2'>
  <relation type='social' desc='employer'
          active=P1 passive='P3 P5 P6 P7' mutual=N>
</particLinks>]]></eg>
 <!-- I hate these names too, especially 'relation' but I      --><!-- cant think of any better ones.  'socrel' 'link.social'   --><!-- ???  (LB)                                                -->
 
This example defines the following three relationships among
participants P1 through P7:
 
<list type="simple"><item>P1 and P2 are parents of P3 and P4.</item><item>P1 and P2 are linked in a mutual relationship called <q>spouse</q>
--- i.e.  P2 is the spouse of P1, and P1 is the spouse of P2.</item><item>P1 has the social relationship <q>employer</q> with respect to P3,
P5, P6, and P7.</item></list></p><p>The elements discussed in this section are formally defined as
follows:<!-- add persname since person is not available in the core   --><!-- and name is not a member of demogs                       --><!-- removed persname: if required, can nest name within person -->
<dtdFrag id="DCCAHPA" n="Participants description" contin="DCCHDR"><claDecl classDoc="DEMOG" type="model"/><tagDecl tagDoc="PERSON"/><tagDecl tagDoc="PERSGRP"/><tagDecl tagDoc="BIRTH"/><tagDecl tagDoc="FRSTLANG"/><tagDecl tagDoc="LANGKNOW"/><tagDecl tagDoc="RESIDENC"/><tagDecl tagDoc="EDUCN"/><tagDecl tagDoc="AFFILIAT"/><tagDecl tagDoc="OCCUPAT"/><tagDecl tagDoc="SOCECSTA"/><tagDecl tagDoc="PARTIREL"/><tagDecl tagDoc="RELATION"/></dtdFrag>
 <!-- shouldnt the cladecl go into teiclas2 somewhere? --></p></div3><div3 id="CCAHSE" name="subsection" ref="Y"><head>The Setting Description</head><p>The <gi tei="yes">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 tei="yes">who</att>
attribute if, for example, participants are in different places.  This
attribute identifies one or more individual participants or participant
groups, as discussed earlier in section <xref target="CCAHPA"/>.  If this
attribute is not specified, the setting details provided are assumed to
apply to all participants represented in the language interaction.
<note source="auth" place="foot" anchored="Y">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 tei="yes">setting</gi>
element, which contains either a prose description or a combination of
the other elements listed below:
 
<tagList style="one-line"><tagDesc tagDoc="SETTING" atts="who"/><tagDesc tagDoc="NAME" atts="type"/><tagDesc tagDoc="DATE" atts="value"/><tagDesc tagDoc="TIME" atts="value"/><tagDesc tagDoc="LOCALE"/><tagDesc tagDoc="ACTIVITY"/></tagList></p><p>The following example demonstrates the kind of background information
often required to support transcriptions of language interactions, first
encoded as a simple prose narrative:
 
<eg><![CDATA[ <settingDesc>
 <p>The time is early spring, 1989.  P1 and P2 are
  playing on the rug of a suburban home in Bedford.
  P3 is doing the washing up at the sink.  P4 (a
  radio announcer) is in a broadcasting studio in London.
 </settingDesc>]]></eg>
 
The same information might be represented more formally in the following
way:
 
<eg><![CDATA[ <settingDesc>
 <setting who="P1 P2">
  <name type=city>Bedford</>
  <name type=region>UK: South East</>
  <date value=1989>early spring, 1989</>
  <locale>rug of a suburban home</>
  <activity>playing</>
 </setting>
 <setting who=P3>
  <name type=city>Bedford</>
  <name type=region>UK: South East</>
  <date value=1989>early spring, 1989</>
  <locale>at the sink</>
  <activity>washing-up</>
 </setting>
 <setting who=P4>
  <name type=place>London, UK</>
  <time>unknown</>
  <locale>broadcasting studio</>
  <activity>radio performance</>
 </setting>
</settingDesc>]]></eg></p><p>For more detailed encoding of names of persons and places, the
additional tag set described in chapter <xref target="ND"/> may
additionally be used; if used, however, these elements may appear only
within a <gi tei="yes">p</gi> element. The above examples assume that only the
general purpose <gi tei="yes">name</gi> element supplied in the core tag set is
available.
 <!-- to avoid repetition, should a who-less setting be        --><!-- assumed to specify defaults for all subelements in same  --><!-- settingDesc ?                                            -->
 <!-- another, more literary, example needed                   -->
 
The elements discussed in this section have the following formal
definitions:
 
<dtdFrag id="DCCAHSE" n="Setting description" contin="DCCHDR"><tagDecl tagDoc="SETTING"/><tagDecl tagDoc="LOCALE"/><tagDecl tagDoc="ACTIVITY"/></dtdFrag>
 </p></div3></div2><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:(quote ("/home/tei/P3/Master/Odds/p2.odd" "tei.1" "text" "body" "div1" "div2"))
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2ccah.odd ??><?tei:SOF p2ccas.odd ??><!--* $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ *--><!--*
    * $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" name="Anthony" ref="Y"><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 <xref 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><p>The TEI DTDs allow for the following possibilities:
 
<list type="simple"><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><item>There may be multiple occurrences of certain elements in either
corpus or text header.</item></list>
 </p><p>To simplify the exposition, we deal with these two possibilities
separately in what follows; however, they may be combined as
desired.
 </p><div3 id="CCAS1" name="subsection" ref="Y"><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><p>The <gi tei="yes">titleStmt</gi> for a corpus text is understood to be
prefixed by the <gi tei="yes">titleStmt</gi> given in the corpus header.  All
other optional elements of the <gi tei="yes">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><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>
 </p></div3><div3 id="CCAS2" name="subsection" ref="Y"><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 tei="yes">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   -->
 
<tagList style="one-line"><tagDesc tagDoc="BIBL"/><tagDesc tagDoc="BIBLFULL"/><tagDesc tagDoc="BIBLSTRU"/><tagDesc tagDoc="BROADCAS"/><tagDesc tagDoc="CORRECTN"/><tagDesc tagDoc="EDDECL"/><tagDesc tagDoc="EQUIPMEN"/><tagDesc tagDoc="HYPHEN"/><tagDesc tagDoc="INTERPTN"/><tagDesc tagDoc="LANGUSG"/><tagDesc tagDoc="LISTBIBL"/><tagDesc tagDoc="NORMALZN"/><tagDesc tagDoc="PARTDESC"/><tagDesc tagDoc="PROJDESC"/><tagDesc tagDoc="QUOTN"/><tagDesc tagDoc="RECORDIN"/><tagDesc tagDoc="SAMPDECL"/><tagDesc tagDoc="SCRSTMT"/><tagDesc tagDoc="SEGMENTN"/><tagDesc tagDoc="SOUSTMT"/><tagDesc tagDoc="STDVALS"/><tagDesc tagDoc="TEXTCLAS"/><tagDesc tagDoc="TEXTDESC"/></tagList>
 
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><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</item></list>
 </p><p>In the following example, an editorial declaration contains two
possible <gi tei="yes">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><p>The <att tei="yes">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 tei="yes">text</gi>, <gi tei="yes">group</gi>, and <gi tei="yes">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><p>The identifier or identifiers specified by the <att tei="yes">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><item>Each element specified, explicitly or implicitly, by the list of
identifiers must be of a different type.</item></list>
 </p><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><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 tei="yes">decls</att> as
<q>ED2</q>, correction C2a, <!-- sampling SAMP2--> and normalization N2b will
apply.
 </p><p>A finer grained approach is also possible.  A text might specify
<tag compl="full" tei="yes">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 compl="full" tei="yes">text decls='ED1 ED2'</tag> would
(obviously) be illegal, since it includes two elements of the same type;
a tag such as <tag compl="full" tei="yes">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).
 </p></div3><div3 id="CCAS3" name="subsection" ref="Y"><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><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><item>Where there are multiple occurrences of declarable elements
within either corpus or text header,
<list type="simple"><item>each must have a unique value specified as the value
of its <att tei="yes">id</att> attribute;</item><item>one only must bear a <att tei="yes">default</att> attribute with
the value <code tei="yes" type="kw">YES</code>.</item></list></item><item>It is a semantic error for an element to be associated
with more than one occurrence of any declarable element.</item><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><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.                                              --></item></list>
<?tei:EOF p2ccas.odd ??>
<?tei:SOF p2ccan.odd ??><!-- 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)                              --><!--                                                          -->
 </p></div3></div2><div2 id="CCAN" name="Anthony" ref="Y"><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 source="auth" place="display" anchored="Y">See in particular chapters <xref target="SA"/>,<xref target="AI"/>
, and <xref target="FS"/>.</note>
The present section presents informally some particular applications of
these general mechanisms to the specific practice of corpus linguistics.
 </p><div3 id="CCAN1" name="subsection" ref="Y"><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 <xref target="CO"/>, <xref 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 <xref target="HD"/>, and in section <xref target="CCAH"/> of the present chapter.
 </p><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><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 tei="yes">interpretation</gi> element within the encoding
description of the TEI Header, as described in section <xref target="HD53"/>.  Where different parts of a corpus have used different
annotation methods, the <att tei="yes">decls</att> attribute may be used to
indicate the fact, as further discussed in section <xref target="CCAS"/>.
 </p><p>An extended example of one form of linguistic analysis commonly
practised in corpus linguistics is given in section <xref target="AILA"/>.



<?tei:EOF p2ccan.odd ??>
<?tei:SOF p2ccrec.odd ??><!-- 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)                             -->
 
 </p></div3></div2><div2 id="CCREC" name="Anthony" ref="Y"><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 <xref 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 <xref target="ST"/> and chapter <xref 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 <xref target="CF"/>.
 </p><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</label><item>texts included within the corpus will always
encode textual features in this category, should they exist in the
text</item><label>recommended</label><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.</item><label>optional</label><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.</item></list>
 
 <!-- hmm, is that all? -->
 <?tei:EOF p2ccrec.odd ??><?tei:EOF p2cc.odd ??>
             <!-- 23 Corpora --></p></div2></div1></div0><div0 n="5" name="Part" ref="Y"><head>Auxiliary Document Types</head><?tei:SOF p2sh.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2sh.odd,v $
    * Revision 1.10  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    * --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : change CITY to pubPlace                 --><!-- 93-09-16 : MSM : validated (and fixed) examples          --><!-- 16 Sep : LB minor typos fixed --><!-- 93-09-15 : MSM : second pass started, completed          --><!-- 93-09-10 : MSM : finish first pass at revisions          --><!-- 93-09-10 : MSM : first cut at revisions                  --><!-- 93-06-05 : MSM : correct typo in eg                      --><!-- 93-06-05 : MSM : cap DTD                                 --><!-- 93-06-03 : MSM : change dtdfrag, reformat for legibility --><!-- Date: Thu, 27 May 93 18:33:11 BST --><!-- Lou, I tried my best with the biblStruct elelent, and    --><!-- I added some notes in the MARC discussion.   Has the     --><!-- Chapter 5 (the Header) been revised.  Section 5.2.7      --><!-- still contains <citnStruct> in the example, as does      --><!-- the content model.  Let me know if there's more to do.   --><!-- Date:, Thu, 24 May 93 22:40:01 BST --><!-- From: Richard Giordano <rich@computer-science.manchester.ac.uk> --><div1 id="SH" n="24" name="Faisal" ref="Y"><head>The Independent Header</head><!--  < p >  If you plan to send headers as independent       --><!-- documents to remote locations, then you should follow    --><!-- the recommendations outlined in this chapter as well     --><!-- as Chapter  < xref target=HD > .                         --><p>Many libraries, text repositories, research sites and related
institutions collect bibliographic and documentary information about
machine readable texts without necessarily collecting the texts
themselves.  Such institutions may thus want access to the header of a
TEI document without its attached text in order to build catalogues,
indexes and databases that can be used by people to locate relevant
texts at remote locations, obtain full documentation about those texts,
and learn how to obtain them.  This chapter of the Guidelines describes
a set of practices by which the headers of TEI documents can be
extracted from those documents and exchanged as freestanding independent
TEI documents.  Headers exchanged independently of the documents they
describe are called <term>independent headers</term>.
<!--
<note place=foot>The responsibility for this chapter was borne by --><!-- the Working Committee for Text Documentation, whose members are --><!-- listed in the front matter.  The chapter was drafted by Richard --><!--     Giordano.</note> --></p><p>This chapter outlines practices recommended for encoders (especially
those responsible for the documentation of text) when creating
independent headers to be distributed, and specifies the set of
recommended elements that should be included in the independent header.
Of interest to librarian cataloguers who may receive independent headers
from remote sites, it also discusses the relationship between the
elements of TEI headers and MARC tags, in order to facilitate the
cataloguing of these headers or the loading of independent headers into
local MARC-based bibliographic databases.   This chapter does
<emph>not</emph> describe how to create a header.  Guidance on the
creation of headers and descriptions of each element in the header can
be found in chapter <xref target="HD"/>.</p><div2 id="SHDEF" name="Anthony" ref="Y"><head>Definition and Principles for Encoders</head><p>An <term>independent header</term> is a header extracted from a TEI
text that can be exchanged as an independent document between libraries,
archives, collections, projects, and individuals.  The file description
of the independent header (enclosed by the <gi tei="yes">fileDesc</gi> element)
can be used to generate bibliographic records.  The profile description,
encoding description, and revision history (encoded by the
<gi tei="yes">profileDesc</gi>, <gi tei="yes">encodingDesc</gi>, and <gi tei="yes">revisionDesc</gi>
elements) can form part of a bibliographic description or, more
appropriately, be used as an attached <soCalled>codebook</soCalled> for
full documentation of the analysis of the text and how it was encoded.
Thus, the independent header can serve as the primary means by which
libraries, archives, related repositories, research projects, and
individual researchers can obtain bibliographic, descriptive, and full
documentary information on machine-readable texts that reside in remote
locations.</p><p>The structure of an independent header is exactly the same as that of
a <gi tei="yes">teiHeader</gi> attached to a document, and can therefore be
validated using the same document type definition (DTD).  In practice,
this means that a <gi tei="yes">teiHeader</gi> and its DTD can be extracted from a
TEI document and shipped to a receiving institution with little or no
change.  However, some fields that are listed as <q>optional</q> in the
header are listed as <q>recommended</q> for the independent header.  For
this reason, this chapter should be consulted in connection with any
plan to send headers as independent documents.</p><p>When deciding which information to include in the independent header,
and the format or structure of that information, the following should be
kept in mind:</p><p>The independent header should provide full bibliographic information
on the encoded text, its source, where the text can be located, and any
restrictions governing its use.</p><p>The independent header should contain useful information about the
encoding of the text itself.  In this regard, it is highly recommended
that the encoding description be as complete as possible.  The
Guidelines do not require that the encoding description be included in
the header (since some simple transcriptions of small items may not
require it), but in practice the use of a header without an encoding
description would be severely limited.</p><p>The independent header should be amenable to automatic processing,
particularly for loading into databases and for the creation of
publications, indexes, and finding aids, without undue editorial
intervention on the part of the receiving institution.  For this reason,
two recommendations are made regarding the format or structure of the
header:  first, where there is a choice between a prose content model
and one that contains a formal series of specialized elements,
<emph>wherever possible and appropriate the specialized elements should
be preferred to unstructured prose</emph>.  For instance, the source
description can contain either a free-prose citation (tagged
<gi tei="yes">bibl</gi> or even <gi tei="yes">p</gi>) or a <gi tei="yes">biblStruct</gi> element,
which provides a more rigorous structure for the bibliographic
information (see examples in section <xref target="COBI"/>).  The more
structured <gi tei="yes">biblStruct</gi> element is more suitable for automatic
processing, and is therefore recommended over the less structured
alternatives whenever the header is to be exchanged as an independent
header.  Second, with respect to corpora, information about each of the
texts within a corpus should be included in the overall corpus-level
<gi tei="yes">teiHeader</gi>.  That is, source information, editorial practices,
encoding descriptions, and the like should be included in the relevant
sections of the corpus <gi tei="yes">teiHeader</gi>, with pointers to them from
the headers of the individual texts included in the corpus.  There are
three reasons for this recommendation:  first, the corpus-level header
will contain the full array of bibliographic and documentary information
for each of the texts in a corpus, and thus be of great benefit to
remote users, who may have access only to the independent header;
second, such a layout is easier for the coder to maintain than searching
for information throughout a text; and third, generally speaking, this
practice results in greater overall consistency, especially with respect
to bibliographic citations.</p></div2><div2 id="SHRR" name="Anthony" ref="Y"><head>Required and Recommended Tags</head><p>The richness and size of the header reflect the diversity of uses to
which electronic texts conforming to these Guidelines will be put.  It
is not intended, however, that all of the elements recommended in this
chapter be present in every header.  As described in section <xref target="HD7"/>, the TEI header allows for the provision of a very large
amount of information concerning the text itself, its source, encodings,
and revisions as well as detailed descriptive information that can be
used by researchers in analysing the text.  The amount of encoding will
depend on the nature and intended use of the text.  At one extreme, an
encoder may expect that the header will only provide bibliographic
information about the text adequate to local needs.  At the other,
wishing to ensure that their texts can be used for the widest range of
applications, encoders will want to document as explicitly as possible
both bibliographic and descriptive information in such a way that no
prior or ancillary knowledge about the text is needed in order to
process it.  The header, in the latter case, will be very full,
approximating the kind of documentation often supplied in the form of a
manual.  Most texts will lie somewhere between these extremes; textual
corpora in particular will tend toward the latter extreme.</p><p>The following is a list of the components of the header, in the order
in which they are presented in chapter <xref target="HD"/>, together with
an indication of their importance in constructing an independent header.

<list type="bullets"><item><gi tei="yes">fileDesc</gi> required.  Some subelements are required,
others optional or recommended:
<list type="simple"><item><gi tei="yes">titleStmt</gi> required; subelements are required or
optional:
<list type="simple"><item><gi tei="yes">title</gi> required</item><item><gi tei="yes">author</gi> required, if known</item><item><gi tei="yes">sponsor</gi> optional</item><item><gi tei="yes">funder</gi> optional</item><item><gi tei="yes">principal</gi> required, if known</item><item><gi tei="yes">resp</gi> required, if known</item><item><gi tei="yes">role</gi> and <gi tei="yes">name</gi> required, if known, when the
            responsibility is not an author, sponsor, funding body, or
            principal researcher.  Details may be found in
            section <xref target="HD21"/>.</item></list></item><item><gi tei="yes">editionStmt</gi> recommended
<list type="simple"><item><gi tei="yes">edition</gi> recommended</item><item><gi tei="yes">resp</gi> recommended</item><item><gi tei="yes">role</gi> and <gi tei="yes">name</gi> recommended primarily to
            distinguish editions.</item></list></item><item><gi tei="yes">extent</gi> optional</item><item><gi tei="yes">publicationStmt</gi> required
<list type="simple"><item><gi tei="yes">date</gi> recommended</item><item><gi tei="yes">publisher</gi>, <gi tei="yes">distributor</gi>,
          or <gi tei="yes">authority</gi> required</item><item><gi tei="yes">pubPlace</gi> recommended</item><item><gi tei="yes">address</gi> recommended; prose is sufficient</item><item><gi tei="yes">idno</gi> recommended</item><item><gi tei="yes">availability</gi> recommended</item></list></item><item><gi tei="yes">seriesStmt</gi> optional
<list type="simple"><item><gi tei="yes">title</gi> required</item><item><gi tei="yes">idno</gi> recommended</item><item><gi tei="yes">resp</gi> and <gi tei="yes">name</gi> optional</item></list></item><item><gi tei="yes">notesStmt</gi> recommended</item></list></item><item><gi tei="yes">sourceDesc</gi> required.  As much information as possible
should be provided to identify the source.  The following tags are
either required or recommended, but other tags not listed here should be
used wherever applicable in order to provide an accurate identification
of the source.  In some instances, the <gi tei="yes">biblFull</gi> tag is
preferable to the <gi tei="yes">biblStruct</gi> tag.
<list type="simple"><item><gi tei="yes">biblStruct</gi> recommended.  For a full discussion
        of <gi tei="yes">biblStruct</gi>, see section <xref target="COBI"/>.</item><item><gi tei="yes">analytic</gi> required when the citation describes an item
          within a larger collection, such as an essay within a
          collection or an article in a journal, and is not an
          independent publication.  If used, it should contain the
          following elements in this order:
<list type="simple"><item><gi tei="yes">author</gi> required, if known</item><item><gi tei="yes">title</gi> required</item><item><gi tei="yes">editor</gi> recommended</item></list></item><item><gi tei="yes">monogr</gi> mandatory when applicable; this element should
        contain the following elements in this order:
<list type="simple"><item><gi tei="yes">author</gi> required, if known.</item><item><gi tei="yes">title</gi> required.  The <att tei="yes">level</att> attribute must
              be used to indicate whether this is the title of a book,
              journal, or series.  It is highly
              recommended that the <att tei="yes">type</att> attribute be used
              to distinguish the main title from subordinate, parallel,
              or other titles.  All elements that indicate intellectual
              responsibility for a work, such as <gi tei="yes">editor</gi>, are
              required, if known.</item><item><gi tei="yes">imprint</gi> required.</item><item><gi tei="yes">pubPlace</gi> required, if known.</item><item><gi tei="yes">org</gi> recommended.</item><item><gi tei="yes">date</gi> required.
             If the date is unknown, <code tei="yes" type="frag">n.d.</code> may be used.</item><item><gi tei="yes">idno</gi> recommended.</item><item><gi tei="yes">series</gi> required, if the item is part of a series.</item><item><gi tei="yes">title</gi> required, but <att tei="yes">type</att> attribute
          is optional.</item></list></item><item><gi tei="yes">scriptStmt</gi> required for transcribed speech.
        See section <xref target="HD32"/>.</item><item><gi tei="yes">recordingStmt</gi> mandatory when applicable:
<list type="simple"><item><gi tei="yes">resp</gi> and <gi tei="yes">name</gi> recommended</item><item><gi tei="yes">recording</gi> recommended</item><item><gi tei="yes">equipment</gi> recommended</item><item><gi tei="yes">broadcast</gi> recommended</item><item><gi tei="yes">comment</gi> optional</item></list></item></list></item><item><gi tei="yes">encodingDesc</gi> very highly recommended, especially
      for projects, collections, or corpora.
      If the <gi tei="yes">encodingDesc</gi> element is used, it is recommended
      that it contain one or more of the following elements, rather
      than a prose description.  See section <xref target="HD5"/>.
<list type="simple"><item><gi tei="yes">projectDesc</gi> optional</item><item><gi tei="yes">samplingDecl</gi> optional</item><item><gi tei="yes">editorialDecl</gi> recommended; it is also recommended
          that the editorial declaration make use of the specialized
          elements defined in section <xref target="HD53"/>, rather than
          only consisting of prose paragraphs.
          Prose may of course be used in addition to these
          elements for material otherwise not handled.</item><item><gi tei="yes">tagsDecl</gi> recommended</item><item><gi tei="yes">refsDecl</gi> optional in general, but recommended if
        a standard referencing system is built into the encoded works.
        Section <xref target="HD54"/> describes three different methods
        for documenting the referencing system:  the prose method,
        the stepwise method, and the milestone method.  No preference
        is expressed for one type of method over another, since this
        depends on the convenience of the encoder and the likely
        efficiency of the particular software applications envisaged for
        the text.  Only one method can be used within a
        single <gi tei="yes">refsDecl</gi> element.  If a text uses both
        hierarchical and milestone tagging, this can only be described
        in prose.</item><item><gi tei="yes">classDecl</gi> required where the <att tei="yes">scheme</att>
        attribute has been used to identify the
        classification scheme or taxonomy used by any of the elements
    <gi tei="yes">keywords</gi>, <gi tei="yes">classcode</gi>, <gi tei="yes">occupation</gi> or
    <gi tei="yes">socecstatus</gi>. Even where this is not done, this element
    may usefully document the
    classification employed, either explicitly as a series of
   <gi tei="yes">taxonomy</gi> elements, or implicitly by means of
        bibliographic citation.</item></list></item><item><gi tei="yes">profileDesc</gi> recommended
<list type="simple"><item><gi tei="yes">langUsage</gi> recommended</item><item><gi tei="yes">language</gi> recommended</item></list></item><item><gi tei="yes">textDesc</gi> optional in most instances, but recommended
      when the encoder wants to provide a full description of the
      situation within which a text was produced or experienced,
      characterize it in a relatively continuous manner (in contrast
      to discrete categories based on type or topic), and believes
      that this characterization of the text will be helpful to the
      understanding, analysis, or retrieval of this text by remote
      users.  If a collection or corpus uses a pre-existing descriptive
      typology as its organizing principle, it is recommended that
      its components be re-expressed in terms of the parameters listed
      here.  If the encoder believes that pre-existing text categories
      (such as a standard classification scheme) are sufficient, then
      it is recommended that the <gi tei="yes">textClass</gi> element be used
      instead. See section <xref target="CCAHTD"/> for details and guidance.
<list type="simple"><item><gi tei="yes">channel</gi> required</item><item><gi tei="yes">constitution</gi> required</item><item><gi tei="yes">derivation</gi> required</item><item><gi tei="yes">domain</gi> required</item><item><gi tei="yes">factuality</gi> required</item><item><gi tei="yes">interaction</gi> required</item><item><gi tei="yes">preparedness</gi> required</item><item><gi tei="yes">purposes</gi> required</item><item><gi tei="yes">purpose</gi> required</item></list></item><item><gi tei="yes">textClass</gi> optional in most instances; this element may
  may be used as an alternative or in addition to the <gi tei="yes">textDesc</gi>
  element.  <gi tei="yes">textClass</gi> is recommended in the following
  situations:
<list type="simple"><item>a standard text category, such as the Library of Congress
        List of Subject Headings or a Dewey Decimal Classification
        category, clearly describes the text</item><item>situational parameters (or the demographic elements of
        the <gi tei="yes">particDesc</gi> element) are used and a text category
        can be constructed by the encoder based on a recurring set of
        values for those parameters.</item></list>
  See section <xref target="HD43"/> for details and guidance. One
  or more of the following sub-elements can be used.
<list type="bullets"><item><gi tei="yes">keywords</gi> recommended only if using a standard
        thesaurus such as the Library of Congress List of Subject
        Headings, a discipline-specific thesaurus, or a thesaurus
        defined explicitly in the header. In each case, the source
        should be indicated by the <att tei="yes">scheme</att> attribute and
        defined in the <gi tei="yes">classDecl</gi> element.</item><item><gi tei="yes">classCode</gi> recommended only if the text is
        categorized by an internationally accepted classification
        scheme, such as the Dewey Decimal or Universal Decimal
        classification schemes.  The scheme
        should be indicated by the <att tei="yes">scheme</att> attribute and
        defined in the <gi tei="yes">classDecl</gi> element.</item><item><gi tei="yes">catRef</gi> optional in most instances, but recommended
        when a user-defined classification is in use. The scheme
        should be indicated by the <att tei="yes">scheme</att> attribute and
        defined in the <gi tei="yes">classDecl</gi> element.<!-- many taxonomies defining classification schemes are      --><!-- used (especially with respect to collections or          --><!-- corpora), and the encoder finds that it is easier to     --><!-- group these in the <gi>encodingDesc</gi> and make        --><!-- reference to them using the <gi>catRef</gi> tag,         --><!-- rather than repeating them throughout the header.        --><!-- This element is also recommended when the encoder is     --><!-- using a specific edition of a classification scheme or   --><!-- taxonomy, and it is known, or assumed, that this         --><!-- scheme will change in the future or has changed from     --><!-- the past.  Bio-medical and scientific taxonomies are     --><!-- examples of changing classification schemes.             -->
<!-- deleted above because it doesnt seem to provide any      --><!-- reason for using or not using catref (lb)                --></item></list></item><item><gi tei="yes">particDesc</gi> optional, but recommended for spoken
      text when the encoder judges that such information is useful
      to remote users in the analysis of that text, and for both
      written and spoken text if such information is useful in the
      analysis of language usage.  For details and guidance,
      see section <xref target="CCAHPA"/>.</item><item><gi tei="yes">participant</gi> or <gi tei="yes">particGroup</gi> recommended.
      Though the substructure of both the <gi tei="yes">participant</gi>
      and <gi tei="yes">particGroup</gi> elements can be prose, in independent headers
      one or more of the following sub-elements providing more specific
      details should be used in preference to prose.  Users of these
      Guidelines are free to extend the set of headings listed below.
<list type="simple"><item><gi tei="yes">name</gi> recommended when the information is available</item><item><gi tei="yes">birthDate</gi> recommended when the information is available</item><item><gi tei="yes">birthPlace</gi> recommended when the information is available</item><item><gi tei="yes">firstLang</gi> recommended when the information is available</item><item><gi tei="yes">langKnown</gi> recommended when the information is available</item><item><gi tei="yes">residence</gi> recommended when the information is available</item><item><gi tei="yes">education</gi> recommended when the information is available</item><item><gi tei="yes">affiliation</gi> recommended when the information is available</item><item><gi tei="yes">occupation</gi> it is recommended that, where possible,
        the classification of the trade, occupation, or profession
        be derived from a standard classification or taxonomy, and that
        the source taxonomy be identified in the <att tei="yes">scheme</att>
        attribute.</item><item><gi tei="yes">socecstatus</gi> it is recommended that, where
        possible, the encoding of social and economic status be
        derived from a standard classification or taxonomy, and that
        the source taxonomy be identified in the <att tei="yes">scheme</att>
        attribute.</item></list></item><item><gi tei="yes">particRelations</gi> optional, but recommended where it
is judged by the encoder that such information is important to the
analysis of the text. If the <gi tei="yes">particRelations</gi> tag is used, it
is recommended that the special purpose <gi tei="yes">relation</gi> element
be used.  See section <xref target="CCAHPA"/>.</item><item><gi tei="yes">settingDesc</gi> optional, but recommended when the
encoder judges that this information is useful in the analysis of the
text, particular in the analysis of language usage.</item><item><gi tei="yes">revisionDesc</gi> required in the independent header when
available.  It is recommended that the <gi tei="yes">revisionDesc</gi> be encoded
with a series of special purpose <gi tei="yes">change</gi> elements with grouped
<gi tei="yes">name</gi>, <gi tei="yes">what</gi> and <gi tei="yes">date</gi> tags.</item></list></p></div2><div2 id="SHMARC" name="Anthony" ref="Y"><head>Header Elements and their Relationship to the MARC Record</head><p>This section offers some guidance to both cataloguers and
bibliographic analysts who want to load TEI independent headers into a
MARC-based retrieval system.  Because there are variations in
cataloguing practice across local sites, among bibliographic utilities
(such as OCLC and RLIN), and differences in MARC usage in different
countries, only tentative advice is possible.  Note that the following
examples are based on USMARC, <emph>not</emph> UNIMARC.
<note source="auth" place="display" anchored="Y">For more information on UNIMARC, see <citation>Brian P. Holt,
<title>UNIMARC Manual</title> (London, U.K.: IFLA Universal
Bibliographic Control and International MARC Programme, British Library,
1987)</citation>.  For USMARC, see <citation> Walt Crawford, <title>MARC
for library use:  understanding USMARC</title> (Boston: G.K. Hall,
1989)</citation>, <citation><title>USMARC format for bibliographic data,
including content designation</title> (Washington, D.C.: Library of
Congress, 1987)</citation>, and <citation>Deborah J. Byrne, <title>MARC
manual : understanding and using MARC records</title> (Englewood, Colo.:
Libraries Unlimited, Inc., 1991)</citation>.</note>
UNIMARC offers cataloguers in different countries the opportunity to
combine different national practices in a single MARC format, and is the
preferred variety of MARC records for distribution
across national boundaries.  The implementation of UNIMARC, however,
will be affected by local practice and by guidelines offered by the
bibliographic utilities. Though UNIMARC is a stable format, the
guidelines for its implementation are not sufficiently known or
stabilized to be included in this chapter.</p><p>There are some major differences between the MARC record and the TEI
header that will cause problems for librarians trying to map from the
TEI independent header to the MARC record.  The most important
difference between the MARC record and the TEI header is the function of
each.  Despite the efforts and claims of some members of the library
community, the MARC record remains fundamentally an electronic version
of the catalogue card, with the limitations of its model.
<note source="auth" place="foot" anchored="Y">The primary function of the MARC record when it was
first designed in the mid-1960s was to allow for the electronic
distribution of cataloguing records in support of card production.  See
<citation>Henriette Avram, <title> The MARC Pilot Project</title>
(Washington D.C.:  Library of Congress, 1968), p.  3.</citation> For
discussion of the relationship between the MARC record and the catalogue
card, see <citation>Michael Gorman, "After AACR2R: The Future of the
Anglo-American Cataloging Rules," in Richard Smiraglia, ed.,
<title>Origins, Content and Future of AACR2 Revised</title> (Chicago:
American Library Association, 1992)</citation>.</note>
The catalogue card is a unitary record for a physical object containing
complex <emph>bibliographic data</emph> of varying sorts.  The catalogue
card points to the physical object.  The TEI header provides full
bibliographic information (as would a card), as well as documentary
non-bibliographic information that supports the analysis, either by
humans or machines, of the electronic text documented by header.  Most
of this analytical information, which is found in profile description,
encoding description, and revision history, has little direct provision
for it in the MARC record,<!-- except that they can be stuffed into various notes (5XX) fields. -->
and if retained must be recorded as unstructured notes (55XX) fields.
Notes fields usually do not have the structure to support machine
retrieval and analysis, while properly formatted profile, encoding, and
revision descriptions lend themselves to retrieval, can support machine
processing (including analysis), and point directly to the electronic
text attached to the header.  Moreover, the electronic text points back
to the relevant elements in the header.</p><p>Though this chapter offers some advice on where the profile,
encoding, and revision descriptions might go in a MARC record, for
practical reasons a repository might want create a codebook from these
divisions of the header, and create a MARC record from the file
description only.  The MARC record should contain a reference to the
codebook.</p><p>Subfields (or delimiters) are conventionally indicated by the
dollar sign.</p></div2><div2 id="SHFD" name="Anthony" ref="Y"><head>MARC Fields for the File Description</head><p>Note that there is no provision for the <soCalled>Main
Entry</soCalled> (or USMARC <code tei="yes" type="frag">1XX</code> fields) in the TEI
header.  The main entry should be constructed, using appropriate name
authority control, by the cataloguer from information derived from the
header that indicates who is primarily responsible for the
intellectual content of the work.  There is an <gi tei="yes">author</gi> tag,
but the form of the name will have to be checked by a cataloguer
before the main entry is constructed.

<list type="simple"><item><gi tei="yes">titleStmt</gi> corresponds to title and statement of
responsibility fields in MARC, typically <code tei="yes" type="frag">240</code> (for uniform
title) and <code tei="yes" type="frag">245</code> (for title proper).</item><item><gi tei="yes">title</gi> <code tei="yes" type="frag">240 $a</code> (for uniform titles) or
<code tei="yes" type="frag">245 $a</code> fields.  Put any subtitles in <code tei="yes" type="frag">24X $b</code>.
Insert the constant, <q>[computer file]</q> in the <code tei="yes" type="frag">24X $h gmd</code>
subfield.</item></list></p><p>The following elements belong in the <code tei="yes" type="frag">245 $c</code> subfield:
statement of responsibility.

<list type="simple"><item><gi tei="yes">sponsor</gi></item><item><gi tei="yes">funder</gi></item><item><gi tei="yes">principal</gi></item></list>

Example:
<eg><![CDATA[<titleStmt>
  <title>Two stories by Edgar Allen Poe: electronic
         version</title>
  <author>Poe, Edgar Allen (1809-1849)</author>
  <respStmt><resp>compiled by</resp>
  <name>James D. Benson</name></respStmt>]]></eg>

This might be tagged in MARC as:

<eg>245 Two stories by Edgar Allen Poe :$belectronic version ;
    compiled by $cJames D. Benson.</eg>

<list type="simple"><item><gi tei="yes">edition</gi> <code tei="yes" type="frag">250 $a</code></item><item><gi tei="yes">name</gi> <code tei="yes" type="frag">250 $b</code></item></list>

Example:

<eg><![CDATA[<editionStmt><edition>
    Student's edition,
    <date>June 1987</date>
</edition><respStmt>
    <resp>New annotation by</resp>
    <name>George Brown</name>
</respStmt></editionStmt>]]></eg><!-- N.B. the awkward tagging here is required by the fact    --><!-- that editionStmt *can* contain phrase data.  It ought    --><!-- to be just p instead. (msm)                              -->

This might be tagged in MARC as:

<eg>250  $aStudent's edition, June, 1987, new annotation by
     $bGeorge Brown.</eg>

<list type="simple"><item><gi tei="yes">extent</gi>.  The extent is analogous to the
<soCalled>Physical Description</soCalled> MARC field.  Fields
<code tei="yes" type="frag">256</code> or <code tei="yes" type="frag">3XX</code>, depending on local practice are appropriate.</item><item><gi tei="yes">date</gi> <code tei="yes" type="frag">260 $c</code>, and appropriate fixed fields.</item><item><gi tei="yes">publisher</gi>, <gi tei="yes">distributor</gi>, or <gi tei="yes">authority</gi>
       <code tei="yes" type="frag">260 $b</code></item><item><gi tei="yes">pubPlace</gi> <code tei="yes" type="frag">260 $a</code></item></list>

Example:
<eg><![CDATA[<publicationStmt>
  <publisher>Columbia University Press</publisher>
  <pubPlace>New York</pubPlace>
  <date>1993</date>
</publicationStmt>]]></eg>
This may be tagged in MARC as:
<eg>260 $aNew York :$bColumbia University Press, $c1993.</eg></p><p>Local practice will determine appropriate MARC fields for
<gi tei="yes">address</gi>, <gi tei="yes">idno</gi>, and <gi tei="yes">availability</gi>.
Restrictions on access should normally be placed in the
<code tei="yes" type="frag">506</code> field, while the place where an item may be ordered
will be located in a local notes (<code tei="yes" type="frag">590</code>) field.  If local
practice warrants it, the address of the publisher should be indicated
in the <code tei="yes" type="frag">260</code> field.</p><p>The series <gi tei="yes">title</gi> and the <gi tei="yes">idno</gi> should be placed in
the appropriate <code tei="yes" type="frag">490</code> fields (series untraced), if series
authority checking needs to be done.  Further, because the TEI tags do
not differentiate between name, conference, or title series, there is
no simple mechanical method for determining which MARC tag (<code tei="yes" type="frag">410,
411,</code> etc.)  should be used.  Safe practice would be to load any
series statements into <code tei="yes" type="frag">490</code> fields, and then to conduct
authority work on those fields.

<list type="simple"><item><gi tei="yes">notesStmt</gi> These are usually reserved for general notes
(<code tei="yes" type="frag">500</code>) fields.</item></list></p><p>The <gi tei="yes">sourceDesc</gi> can be mapped to be a <soCalled>source of
data</soCalled> note (<code tei="yes" type="frag">537</code> in RLIN MDF format) with the
print constant <q>Transcribed from:</q> at the beginning of the note.
The <gi tei="yes">biblStruct</gi> itself can be mapped onto a <code tei="yes" type="frag">581</code>
field (note on primary publication) using the ISBD format to separate
each data element.</p><p>The <gi tei="yes">scriptStmt</gi>, <gi tei="yes">recordingStmt</gi>,
<gi tei="yes">recording</gi>, <gi tei="yes">equipment</gi>, and <gi tei="yes">broadcast</gi>
elements do not easily map to existing MARC fields, and should be
put into a local notes field (<code tei="yes" type="frag">590</code>) treating the TEI tag
introducing each component as a print constant at the head of the
field in order to facilitate future local processing and retrieval.

Example:
<eg><![CDATA[<scriptStmt id=CNN12>
  <bibl><author>CNN Network News</author>
    <title>News Headlines</title>
    <date>12 Jun 1991</date>
  </bibl>
</scriptStmt>]]></eg>

This may be tagged in MARC thus:

<eg><![CDATA[590  <scriptStmt id=CNN12>
     <bibl><author>CNN Network News</author>
     <title>News Headlines</title>
     <date> 12 Jun 1991></date></bibl>
     </scriptStmt>]]></eg>

Example:

<eg><![CDATA[<recordingStmt>
   <recording type=video dur="10 mins">
   <equipment><p>Recorded from FM radio to chrome
       tape</p></equipment>
   <broadcast>
      <bibl>
         <title>Britain's pleasure parade</title>
         <author>BBC Radio 4 FM</author>
         <editor role=interviewer>Robin Day</editor>
         <editor role=interviewee>Margaret Thatcher</editor>
         <series><title>The World Tonight</></series>
         <date>27 Nov 89</date>
       </bibl>
    </broadcast>
    </recording>
</recordingStmt>]]></eg>

This can be tagged in MARC as:
<eg><![CDATA[590 <recordingStmt>
    <recording type=video dur="10 mins">
    <equipment><p>Recorded from FM radio to chrome
         tape</p></equipment><broadcast>
    <bibl><title>Britain's pleasure parade</title>
    <author>BBC Radio 4 FM</author>
    <editor role=interviewer>Robin Day</editor>
    <editor role=interviewee>Margaret Thatcher</editor>
    <series><title>The World Tonight</></series>
    <date>27 Nov 89</date>
    </bibl>
    </broadcast>
    </recording>
    </recordingStmt>]]></eg></p></div2><div2 id="SHED" name="Anthony" ref="Y"><head>MARC Fields for the Encoding Description</head><p>The <gi tei="yes">encodingDesc</gi> element provides useful information
documenting the relationship between an electronic text and the source
or sources from which it was derived.  The <gi tei="yes">projectDesc</gi>,
<gi tei="yes">samplingDecl</gi>, <gi tei="yes">editorialDecl</gi>, and <gi tei="yes">refsDecl</gi>
elements provide details of decisions and rationales used about the
process and purposes of the project, how text was sampled, principles
of editorial practice, and how canonical references are constructed.
The <code tei="yes" type="frag">567</code> field (notes on methodology) appears to be the
most appropriate for this sort of information, though this field is
normally intended for methodologies characterizing the social
sciences.  Practically, it would be wise to transcribe the
<gi tei="yes">projectDesc</gi>, <gi tei="yes">editorialDecl</gi>, <gi tei="yes">refsDecl</gi>, and
<gi tei="yes">classDecl</gi> elements directly as one or more 567 fields without
intervention, with the element name at the beginning of each field,
and any TEI tags left intact. This may facilitate any
locally-developed retrieval software.</p><p>Example:

<eg><![CDATA[<encodingDesc>
  <projectDesc><p>Texts were collected to illustrate the
    full range of twentieth-century spoken and written Swedish,
    written by native Swedish authors.</projectDesc>
  <samplingDecl><p>Sample of 2000 words taken from the
    beginning of the text.</p></samplingDecl>
  <editorialDecl>
       <interpretation><p>Errors in transcription controlled
         by using the SUC spell checker, v.2.4</p></interpretation>
  </editorialDecl>
</encodingDesc>]]></eg>

This may be tagged in MARC as:

<eg><![CDATA[567  <projectDesc><p>Texts were collected to illustrate the
      full range of twentieth-century spoken and written
      Swedish, written by native Swedish authors.</p>
567  <samplingDecl><p>Sample of 2000 words taken from the
     beginning of the text.</p>
567  <editorialDecl>
     <interpretation><p>Errors in transcription controlled
      by using the SUC spell checker, v. 2.4</p>
     </interpretation>
     </editorialDecl>]]></eg></p></div2><div2 id="SHPD" name="Anthony" ref="Y"><head>MARC Fields for the Profile Description</head><p>The profile description is the most problematic element in the TEI
header for librarian cataloguers, because it provides a detailed
description of the <emph>non-bibliographic</emph> aspects of the text,
specifically the languages and sublanguages used, the situation in which
it was produced, and the participants and their setting.  This
information can be used for retrieval purposes or in
machine-supported analysis of the text.  The information can be loaded
into a separate <soCalled>codebook</soCalled> and referenced by the MARC
record.  Little guidance can be offered on the appropriate MARC
location for the elements that make up the profile description, except
to suggest that if a site wants to load the profile description into a
MARC record for archival and possibly retrieval purposes, then the
contents of the profile description may be mapped into a locally-defined
notes field (<code tei="yes" type="frag">59X</code>) with its TEI tags intact, as in the examples
above.</p></div2><div2 id="SHRD" name="Anthony" ref="Y"><head>MARC fields for the Revision Description</head><p>The revision history (<gi tei="yes">revisionDesc</gi>) logs all changes to a
machine readable file whether or not these constitute a new edition of
the file.  Aside from the edition area of the MARC record, there are
no MARC fields that deal specifically with changes of this sort.  This
information might be best included in a <soCalled>codebook</soCalled>,
rather than a MARC record. As before, the simplest way of approaching
this problem is to include the material with its TEI tags intact as a
locally-defined note (<code tei="yes" type="frag">59X</code>) in order to support future
local processing.</p></div2><div2 id="SHSTR" name="Anthony" ref="Y"><head>Structure of the DTD for Independent Headers</head><p>The following document type definition is provided in file
<ident tei="yes" type="file">teishd2.dtd</ident> and constitutes the auxiliary DTD for
independent headers as described in this chapter.

<dtdFrag id="DIH" n="File teishd2.dtd:  Auxiliary DTD for Independent Header" file="teishd2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>Embed entities for TEI generic identifiers.</commDecl><entDecl entDoc="TEIGIS"/><peRef n="TEI.elementNames"/><commDecl>Embed entities for TEI keywords.</commDecl><entDecl entDoc="TEIKW"/><peRef n="TEI.keywords.ent"/><commDecl>Define element classes for content models, shared
attributes for element classes, and global attributes.  (This all
happens within the file teiclas2.ent.)</commDecl><entDecl entDoc="TEIECGA"/><peRef n="TEI.elementClasses"/><commDecl>Now declare the IHS element.</commDecl><tagDecl tagDoc="IHS"/><commDecl>Finally, embed the TEI header and core tag sets.</commDecl><entDecl entDoc="TEIHDR"/><peRef n="TEI.header.dtd"/><entDecl entDoc="TEICORE"/><peRef n="TEI.core.dtd"/></dtdFrag></p><p>The overall structure of a set of independent headers, encoded for
interchange as a group, is thus:

<eg><![CDATA[<!DOCTYPE ihs PUBLIC "-//TEI P3//DTD Auxiliary Document Type:  
        Independent TEI Header//EN"
       "teishd2.dtd">
<ihs>
<teiHeader>
  <fileDesc> ...     </fileDesc>
  <encodingDesc> ... </encodingDesc>
  <profileDesc> ...  </profileDesc>
  <revisionDesc> ... </revisionDesc>
</teiHeader>
<teiHeader>
  <fileDesc> ...     </fileDesc>
  <encodingDesc> ... </encodingDesc>
  <profileDesc> ...  </profileDesc>
  <revisionDesc> ... </revisionDesc>
</teiHeader>
<teiHeader> ... </teiHeader>
<!-- ... etc. -->
</ihs>]]></eg></p><p>In practice, headers might be stored in separate operating system
files, to reduce redundant storage requirements; in this case, the
top-level file for a typical document might have the following
structure:
<eg><![CDATA[<!DOCTYPE tei PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                     "tei2.dtd" [
  <!ENTITY txt01 system 'text01.tei' >
  <!ENTITY hdr01 system 'text01.hdr' >
]>
<tei.2>
&hdr01;
&txt01;
</tei.2>]]></eg>

while that for a set of independent headers might have this structure:

<eg><![CDATA[<!DOCTYPE ihs PUBLIC "-//TEI P3//DTD Auxiliary Document Type:  
        Independent TEI Header//EN"
       "teishd2.dtd" [
  <!ENTITY hdr01 system 'text01.hdr' >
  <!ENTITY hdr02 system 'text02.hdr' >
  <!ENTITY hdr03 system 'text03.hdr' >
  <!-- ... etc. -->
]>
<ihs>
&hdr01;
&hdr02;
&hdr03;
<!-- etc. -->
</ihs>]]></eg></p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2sh.odd ??><!-- 24 Structured Header --><?tei:SOF p2wd.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2wd.odd,v $
    * Revision 1.9  1998/02/01 17:38:08  tei
    * fix Log keyword,
    * normalize SGML
    * replace system identifiers with public identifiers.
    *
    * Revision 1.8  94/03/28  15:10:52  lou
    * fix asstd <term> elements
    * 
    * Revision 1.7  1994/03/27  16:31:49  lou
    * *** empty log message ***
    * 
    * Revision 1.4  1993/09/22  18:41:40  msmcq
    * Version as of publication of WD
    * 
    * Revision 1.3  1993/09/17  16:23:41  lou
    * Minor stylistic revisions
    * 
    * Revision 1.2  1993/07/28  21:03:50  msmcq
    * Mostly cosmetic changes
    * regularize formal names
    * --><!-- Revisions:                                               --><!-- 18 mar : applied corrections noted by eagle-eyed gary simons --><!-- 93-09-20 : MSM : last-minute revisions                   --><!-- 93-09-20 : MSM : make wsd names more consistent          --><!-- 93-09-20 : MSM : embed wsdgis.ent                        --><!-- 93-09-17 : MSM : go through checking up on Lou, minor mods --><!-- 3 aug 93 : LB : simplify prose here and there              --><!--                fix dud comment                           --><!-- 93-07-28 : MSM : minor improvements from late May        --><!-- 93-05-31 : MSM : add reference to inherited,  isodate    --><!-- 93-05-31 : MSM : add reference to wsdglob                --><div1 id="WD" n="25" name="Faisal" ref="Y"><head>Writing System Declaration</head><p>The <term>writing system declaration</term> or WSD is an
auxiliary document which provides information on the methods used to
transcribe portions of text in a particular language and script.<!-- <note place=foot>The primary responsibility for this chapter wasborne by work --><!-- group TR 1 (character set issues), chaired by Harry Gaylord.  The --><!-- original design of the writing system declaration and the firstdraft of --><!-- its documentation were created by Steven J. DeRose; revisionshave been --><!-- made by Harry Gaylord and Syun Tutiya, among others.</note> -->
We use the term <term>writing system</term> to mean a given method
of representing a particular language, in a particular script or
alphabet; the WSD specifies one method of representing a given writing
system in electronic form.  A single WSD thus links three distinct
objects:
 
<list type="bullets"><item>the language in question</item><item>the writing system (script, alphabet, syllabary) used to write the
language</item><item>the coded character set, entity names, or transliteration scheme
used to represent the graphic characters of the writing system</item></list>
 
Different natural languages thus have different writing system
declarations, even if they use the same script.  Different methods used
to write the same language (e.g.  Cyrillic or Latin encoding of
Serbo-Croatian), and different methods of representing the same script
in electronic form (e.g. different coded character sets such as ASCII or
EBCDIC, or different transliteration schemes) similarly must use
different writing system declarations.</p><p>This chapter describes first the overall structure of the WSD
(section <xref target="WDOV"/>), and then the specific elements used to
document the natural language, writing system, coded character sets,
SGML entity names, and transliteration schemes united by the WSD.
Section <xref target="WDLK"/> describes how the WSD is associated with
different portions of a document. Predefined TEI writing system
declarations, which should suffice for many uses, are described in
section <xref target="WDXW"/>.  There follows a brief description of how
to create a new WSD on the basis of an existing WSD.  Finally, in
section <xref target="WDSE"/> we provide a formal discussion of the
semantics of the writing system declaration.</p><div2 id="WDOV" name="Anthony" ref="Y"><head>Overall Structure of Writing System Declaration</head><p>A writing system declaration is a distinct auxiliary document,
separate from any transcription for which it is used.  <!-- LB adds -->
A TEI document specifies the writing system declarations applicable to
it by means of declarations in its header, and by means of its use of
the global <att tei="yes">lang</att> attribute, as further specified in section<xref target="WDLK"/>
. Each writing system declaration is itself a
free-standing document, encoded as 
a single <gi tei="yes">writingSystemDeclaration</gi> element, and
containing the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="TEIWSD" atts="name date"/><tagDesc tagDoc="WSDLANG"/><tagDesc tagDoc="SCRIPT"/><tagDesc tagDoc="DIRECTN"/><tagDesc tagDoc="WSDCHARS"/><tagDesc tagDoc="WSDNOTE"/></tagList>
 
All elements in the writing system declaration may bear either of the
following two attributes:
 
<adList classDoc="WSDGLOB" atts="id lang"/></p><p>These attributes function in the same way as the global
<att tei="yes">id</att> and <att tei="yes">lang</att> attributes of the main TEI DTD
(although for technical reasons the latter is declared differently):
the former provides a unique SGML identifier for the element, and the
latter identifies the language in which the contents of the element
are expressed, using a code from ISO 639.</p><p>The overall structure of a writing system declaration is thus as
follows:
 
<eg><![CDATA[<writingSystemDeclaration
          lang='eng'
          name=' ... '
          date='1993-05-29'>
 
<language iso639='...'>
    <!-- name of language here -->
    </language>
<script>
    <!-- description of script here ... -->
    </script>
<direction chars=LR lines=TB>
<characters>
    <!-- description of character inventory here ... -->
    </characters>
</writingSystemDeclaration>]]></eg></p><p>The attributes <att tei="yes">date</att> and <att tei="yes">name</att> are required on
the <gi tei="yes">writingSystemDeclaration</gi> element.  The <att tei="yes">date</att>
attribute is used to specify the date on which the WSD was written or
last changed; this  must be given in the format
<q>yyyy-mm-dd</q>, as defined by ISO 8601: 1988, <title>Data
elements and interchange formats --- Information interchange ---
Representation of dates and times</title>.</p><p>The <att tei="yes">name</att> attribute is used to assign a formal name to the
writing system declaration, for references to it from elsewhere.  It is
recommended, though not required, that the name be constructed as an
SGML formal public identifier; for purposes of writing system
declarations, this means it should follow the pattern of the following
examples:
 
<eg> -//TEI P2: 1993//NOTATION WSD for Modern English//EN
 -//WWP 1993//NOTATION WSD for 17th-century English//EN
 -//OTA 1991//NOTATION WSD for Old English//EN
 -//GLDV 1997//NOTATION WSD Mittelhochdeutsch//DE</eg>
 
That is, the identifier should consist of:
 
<list type="ordered"><item>either the string <code tei="yes" type="frag">-//</code> (indicating that the organization
issuing the WSD is not registered with ISO) or the string <code tei="yes" type="frag">+//</code>
(indicating that the organization is so registered);</item><item>a short string identifying the issuing organization and optionally
the document which defines the WSD (or at least the issuing organization
and the date);</item><item>the separator string <code tei="yes" type="frag">//</code>;</item><item>the keyword <code tei="yes" type="kw">NOTATION</code>, indicating that in SGML terms, the
writing system declaration functions as a non-SGML notation;</item><item>a descriptive phrase indicating the contents of the WSD (which
may, as here, begin <q>WSD for ...</q>);</item><item>the separator string <code tei="yes" type="frag">//</code>;</item><item>the ISO 639 code for the language in which the WSD is written,
for example <code tei="yes" type="frag">EN</code>.</item></list></p><p>The other elements of the WSD are described in the following
sections.</p><p>The DTD for writing system declarations is included in file <ident tei="yes" type="file">teiwsd2.dtd</ident>; a writing system declaration will thus
begin with a document type declaration invoking that file:
 
<eg><![CDATA[ <!DOCTYPE writingSystemDeclaration
           PUBLIC "-//TEI P3//DTD Auxiliary Document Type:  
           Writing System Declaration//EN"
          "teiwsd2.dtd" [
   <!-- entity sets are declared and invoked here -->
  ]>]]></eg>
 <!-- I enter here my firm conviction that                     --><!-- 'writingSystemDeclaration' is a ridiculous name for      --><!-- this element. It doesn't matter how often one is         --><!-- likely to use it. It's just too unwieldy and long.  It   --><!-- should be  < wsd > : that's how one refers to the        --><!-- thing after all.                                         --><!-- LB 1 aug 93 --></p><p>The formal declaration of the writing system declaration is as
follows:
 
<dtdFrag id="DWD" n="Writing System Declaration" file="teiwsd2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><entDecl entDoc="INHERIT"/><entDecl entDoc="ISODATE"/><commDecl>Embed entities for TEI generic identifiers.</commDecl><entDecl entDoc="WDGIS"/><peRef n="TEI.wsdNames"/><claDecl classDoc="WSDGLOB" type="atts"/><tagDecl tagDoc="TEIWSD"/><dtdRef dtdFrag="DWDLA"/><dtdRef dtdFrag="DWDWS"/><dtdRef dtdFrag="DWDCSBA"/><dtdRef dtdFrag="DWDCSEX"/><dtdRef dtdFrag="DWDNO"/></dtdFrag></p></div2><div2 id="WDLA" name="Anthony" ref="Y"><head>Identifying the Language</head><p>The <gi tei="yes">language</gi> element is used to name the language associated
with the WSD.  Its <att tei="yes">iso639</att> attribute gives the ISO standard
code for the language as defined by <title>ISO 639: 1988. Code for the
representation of names of languages</title>.
 
<tagList style="one-line"><tagDesc tagDoc="WSDLANG" atts="iso639"/></tagList><!-- here --></p><p>If the language in question is not included in the list in ISO 639,
the value of the attribute <att tei="yes">iso639</att> should be the
empty string, as in the following example:
<eg><![CDATA[<language iso639=''>Various</language> ]]></eg><!-- this looks completely mad! (LB)  --></p><p>The <gi tei="yes">language</gi> element should not be confused with the global
<att tei="yes">lang</att> attribute; the element identifies the language whose
writing system is being documented, while the attribute identifies the
language in which the description is being written.  A writing system
declaration for classical Greek, for example, which itself is written in
English, would have the value <code tei="yes" type="frag">eng</code> for the <att tei="yes">lang</att>
attribute on the top-level element, and the value <code tei="yes" type="frag">grc</code> for the
<att tei="yes">iso639</att> attribute on the <gi tei="yes">language</gi> element:
 
<eg><![CDATA[<writingSystemDeclaration
          id='GRC.beta'
          lang=eng
          name='-//TEI P2: 1993//NOTATION WSD for TLG Beta Code
               transliteration of ancient greek//EN'
          date='1993-05-29'>
 
<language iso639='grc'>Classical Greek.  This WSD documents the Beta
transcription code for classical Greek developed by the Thesaurus
Linguae Graecae of the University of California, Irvine.</language>
<!-- ... -->
</writingSystemDeclaration>]]></eg></p><p>Normally, the language described is a natural language; in some
cases, however, artificial languages, dialects, or other sublanguages
may be usefully regarded as a language and documented in a writing
system declaration.  When a sublanguage is documented, a description of
the sublanguage should be included in the <gi tei="yes">language</gi> element:
 
<eg><![CDATA[ <language iso639='jpn'>
    Japanese (specialized writing system for waka)
 </language>]]></eg>
 <!-- Syun:  you mentioned 'a particular school' of writers    --><!-- of waka.  Can you refine the wording of this example?    --><!-- Thanks.  -msm                                            --></p><p>When a writing system declaration is prepared solely in order to
document a coded character set or entity set suitable for use with many
natural languages, the content of the <gi tei="yes">language</gi> element should
be <q>Various</q> (or the equivalent in the language of the WSD):
 
<eg><![CDATA[<writingSystemDeclaration
          lang=eng
          name='-//TEI P2: 1993//NOTATION WSD for ISO 646 IRV//FR'
          date='1993-05-29'>
  <language iso639=''>Plusieurs</language>
  <!-- ... -->
</writingSystemDeclaration>]]></eg></p><p>The <gi tei="yes">language</gi> element is formally defined thus:
 
<dtdFrag id="DWDLA" n="Language identification"><tagDecl tagDoc="WSDLANG"/></dtdFrag></p></div2><div2 id="WDWS" name="Anthony" ref="Y"><head>Describing the Writing System</head><p>The writing system itself is described in general terms using the
following elements:
 
<tagList style="one-line"><tagDesc tagDoc="SCRIPT"/><tagDesc tagDoc="DIRECTN" atts="chars lines"/></tagList></p><p>The <gi tei="yes">script</gi> element contains a prose description of the
script, alphabet, syllabary, or other system of writing used to write
the language in question.  The <gi tei="yes">direction</gi> element indicates the
direction(s) in which the script is conventionally written.  Both these
elements are provided for the sake of human readers; neither is likely
to be suited to machine processing without human intervention.</p><p>The Latin alphabet conventionally used to write English, for example,
might be described thus:
 
<eg><![CDATA[<script>Latin alphabet (with diacritics for loan words)</script>
<direction chars=LR lines=TB>]]></eg></p><p>The <att tei="yes">chars</att> and <att tei="yes">lines</att> attributes are used to
indicate the direction in which characters within a line, and lines on
the page, may legitimately be written using the script in question.  If
more than one direction is possible, the <gi tei="yes">direction</gi> element may
repeat or its attributes may be given more complex values.  A script
written vertically top to bottom, with lines arranged either left to
right or right to left, for example, might be declared either thus:
 
<eg><![CDATA[<direction chars=TB lines=LR>
<direction chars=TB lines=RL>]]></eg>
 
or thus:
 
<eg><![CDATA[<direction chars=TB lines='LR RL'>]]></eg></p><p>In very complex cases, the attributes may be given prose values:
 
<eg><![CDATA[ <direction chars='boustrophedon:  LR, then RL, then LR, etc.'
            lines='TB'>]]></eg>
 
or the element may be omitted entirely (in which case experts on the
script should be consulted for advice on proper processing):
 
<eg><![CDATA[ <script>Japanese (mixture of kanji, hiragana, katakana)</script>
 <!-- If you don't already know how Japanese is written,
      no DIRECTION element in the world will help you. -->]]></eg></p><p>It should be noted that the <gi tei="yes">direction</gi> element describes
conventional display only:  all scripts are subject to unusual treatment
for aesthetic or other reasons, and such unusual treatment need not be
foreseen here.  (The Latin alphabet, for example, although
conventionally written left-to-right, top-to-bottom, can be set
vertically in signs or in other special cases.)  Unusual methods of
arranging the text on a page are best documented within the document
instance by means of the global <att tei="yes">rend</att> attribute.</p><p>The <gi tei="yes">script</gi> and <gi tei="yes">direction</gi> elements are declared
thus:
 
<dtdFrag id="DWDWS" n="Script and writing direction"><tagDecl tagDoc="SCRIPT"/><tagDecl tagDoc="DIRECTN"/></dtdFrag></p></div2><div2 id="WDCS" name="Anthony" ref="Y"><head>Documenting the Character Set and Its Encoding</head><div3 id="WDCSBA" name="subsection" ref="Y"><head>Base Components of the WSD</head><p>The characters or graphic symbols of the writing system are
documented in the <gi tei="yes">characters</gi> element of the WSD.  This
documentation can take any of the following forms:
 
<list type="bullets"><item>reference to an international standard, national standard, or
private coded character set</item><item>reference to a public set of SGML entities</item><item>reference to another WSD which documents the same script and
the same methods of representing it electronically</item><item>formal declaration of each graphic unit in the writing system</item><item>a combination of the above:  reference to one or more standard
coded character sets, entity sets, or writing system declarations,
followed by individual declaration of all exceptions</item></list></p><p>The coded character sets, entity sets, and external WSDs referred to
are called the <term>base components</term> of the writing system
declaration.  The base components of a WSD are declared within the
<gi tei="yes">characters</gi> element using the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="WSDCHARS"/><tagDesc tagDoc="WSDCCS"/><tagDesc tagDoc="BASEWSD"/><tagDesc tagDoc="WSDENTS"/></tagList></p><p>The elements <gi tei="yes">codedCharSet</gi>, <gi tei="yes">baseWsd</gi>, and
<gi tei="yes">entitySet</gi> are all members of the class
<term>baseStandard</term> and inherit from it the following attributes:
 
<adList classDoc="BASESTD" atts="name authority"/></p><p>Some simple examples of the use of these elements follow:
 
<eg><![CDATA[ <codedCharSet name='ANSI X3.4' authority='national'>
 <codedCharSet name='ISO 646: 1991' authority='ISO'>
 <baseWsd      name='-//TEI P3: 1994//WSD ISO 8859-1//EN'
               authority='TEI'>
 <entitySet    name='ISO 8879:1986//ENTITIES Added Latin 1//EN'
               authority='ISO'>]]></eg></p><p>The base components identify the set of characters used in the
writing system, and further specify, for each character, the string(s)
of bytes and entity names used to encode it in the text.  This
information may be modified by further information given within the
<gi tei="yes">exceptions</gi> element, as described below in section <xref target="WDCSEX"/>.</p><p>The elements for identifying the base components of the writing
system declaration are declared thus:
 
<dtdFrag id="DWDCSBA" n="Base components"><tagDecl tagDoc="WSDCHARS"/><claDecl classDoc="BASESTD" type="atts"/><tagDecl tagDoc="WSDCCS"/><tagDecl tagDoc="BASEWSD"/><tagDecl tagDoc="WSDENTS"/></dtdFrag></p></div3><div3 id="WDCSEX" name="subsection" ref="Y"><head>Exceptions in the WSD</head><p>The <gi tei="yes">exceptions</gi> element contains definitions for any
character which differs in any respect from the specifications contained
in the base components of the WSD.  If no base components are named,
then every character in the writing system must be defined explicitly.</p><p>The documentation for each character in the writing system indicates
at least the following:
 
<list type="bullets"><item>the string of bytes used to represent the character</item><item>whether the character is a letter, a punctuation mark, a
diacritical mark, or falls into some other class</item><item>a brief conventional name or description of the character</item><item>any standard or local entity names used for the character</item><item>the position of the character in the Universal Character Set (UCS)
defined by ISO 10646, if known</item><item>the position of the character's form in the tables prepared by the
Association for Font Information Interchange</item></list>
 
In addition, images of the character encoded in a graphics format or
other notation may be associated with the character as internal
or external figures.
 
This information is encoded using the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="EXCEPTNS"/><tagDesc tagDoc="WSDCHAR" atts="class"/><tagDesc tagDoc="WSDDESC"/><tagDesc tagDoc="WSDFORM" atts="string codedCharSet                entityStd entityLoc                ucs-4 afiicode"/><tagDesc tagDoc="WSDFIG" atts="notation"/><tagDesc tagDoc="WSDXFIG" atts="notation entity"/></tagList></p><p>The <gi tei="yes">exceptions</gi> element contains a series of
<gi tei="yes">character</gi> elements only, each of which may contain descriptions
of the character (including its name), notes, and a series of
<gi tei="yes">form</gi> elements documenting the different forms the character can
take.  Attributes on the <gi tei="yes">character</gi> and <gi tei="yes">form</gi> elements
are used to convey the information mentioned above:  byte string, entity
names, UCS-4 code, etc.</p><p>A simple example:
 
<eg><![CDATA[<character class=lexical>
  <form string='A' ucs-4='0041' afiicode='0041'>
    <desc>Latin capital letter A</desc>
  </form>
</character>]]></eg></p><p>When transliteration schemes are used, the <att tei="yes">string</att> used to
encode the character will typically be in a different alphabet:
 
<eg><![CDATA[<character class=lexical>
  <form string='*G' entityStd="Ggr" ucs-4='0393' afiicode='260044'>
    <desc>Greek capital letter Gamma</desc>
  </form>
</character>]]></eg></p><p>The UCS-4 code is given as eight hexadecimal digits, one for each
four bits of the thirty-two-bit value. For legibility a hyphen may be
inserted as a separator after the fourth hexadecimal digit:
<code tei="yes" type="frag">00000308</code> has the same meaning as <code tei="yes" type="frag">0000-0308</code>.  Since in
almost all cases at present the leading sixteen bits are zero, however,
by convention the leading four hexadecimal zeros may be dropped
entirely:  the value <code tei="yes" type="frag">0308</code> is identical in meaning to the value
<code tei="yes" type="frag">0000-0308</code>.</p><p>In some cases, the character is represented not as a single UCS
character but as a sequence of such characters; in this case, each
thirty-two-bit value except the last must be followed by a plus sign:
 
<eg><![CDATA[<character class='lexical'>
  <form string='*=+U'
        entityStd="Ucdgr"
        ucs-4='03A5+0302+0308'
        afiicode='F300EC'>
            <desc>Greek capital letter Upsilon with
                  circumflex and diaresis</desc>
  </form>
</character>]]></eg><!-- is this optional? or required? could it be               --><!-- '0000030500000302' etc?  (lb)                            --></p><p>If a given <gi tei="yes">character</gi> element has more than one encoding
using ISO 10646 (e.g. both as <q>a-umlaut</q> and as <q>a</q> plus
<q>umlaut</q>), then both encodings may be given, separated by blanks:
 
<eg><![CDATA[<character class='lexical'>
  <form string=''
        entityStd="Auml"
        afiicode='F127"
        ucs-4='0041+0308 00C4' >
            <desc>Latin capital letter A with umlaut</desc>
  </form>
</character>]]></eg>
 
 <!-- Drop example until we can get appropriate JIS codes to   --><!-- go in here (LB) Right. (MSM)                             --></p><p>In most cases, identifying the character or character form by means
of its UCS-4 and AFII codes will suffice to identify the character for
all later users of the WSD.  In some cases, however, further information
must be provided.<!-- suppress this example when JIS example is used. (msm) -->
This may be provided in a <gi tei="yes">note</gi> attached to the
<gi tei="yes">character</gi> or <gi tei="yes">form</gi> element:
<eg><![CDATA[<character class='lexical'>
  <form string='N'
        entityLoc="nn" >
        ucs-4="0274"   >
            <desc>Standard ms symbol for double n.</desc>
  </form>
  <note>This character has the form of a capital-letter N,
        but is written the same height as a lower-case N.
        Its appearance is thus that of UCS-4 0274, but it
        does not have the same semantics.
  </note>
</character>
 ]]></eg>
 <!-- Use this example when we have real values. (msm) -->
 <!-- < p > The mapping between Han characters in ISO 10646    --><!-- and those in the national character sets of China,       --><!-- Japan, and Korea, for example, is at present not fully   --><!-- documented in ISO 10646; accompanying commentary in      --><!-- prose, identifying the character by its position in      --><!-- one of the national character sets, may therefore be     --><!-- found useful.  This may be done in a < gi > note < /gi   --><!-- >  attached to the  < gi > character < /gi >  or  < gi   --><!-- > form < /gi > element:                                  -->
 <!--  < eg >                                                  --><!--  < ![ CDATA [                                            --><!--  < character class='lexical' >                           --><!--    < form string='ssss'                                  --><!--         entityLoc="JISnnn.nnn"                           --><!--         ucs-4='xxxx'  >                                  --><!--              < desc > Chinese character ccccc < /desc >  --><!--    < /form >                                             --><!--    < note > This character has position nnn/nnn in JIS 0208; --><!--         the UCS-4 code is not completely certain.        --><!--    < /note >                                             --><!--  < /character >                                          --><!--                                                          --><!--  ]] >                                                    --><!--  < /eg >                                                 --></p><p>In some cases, it will be necessary or useful to provide an image of
the character in question, or to refer to a standard reference work for
such an image.  The following <gi tei="yes">character</gi> element might be used
to describe, for example, a common Old French abbreviation for
<q>est</q>, for which the local entity <ident tei="yes" type="ent">est</ident> has been
defined:
 
<eg><![CDATA[<character class='lexical'>
  <form string='' entityLoc="est">
     <desc>Old French abbreviation for 'est':  lowercase
           'e' with a tilde or macron above.</desc>
     <note>For an image of this character, see
           Cappelli, p. 113, column 1, line 4
           (leftmost and rightmost item).</note>
  </form>
</character>]]></eg>
 
Here, <q>Cappelli</q> is the name of a standard reference work which may
be consulted to see what the character in question looks like.<note source="auth" place="foot" anchored="Y"><title>Dizionario di Abbreviature latine ed italiane</title>
per cura di Adriano Cappelli, 6th ed. (Milan:  Ulrico Hoepli, 1979).
This work on Latin abbreviations might be less convenient for the
purpose than one concentrating on Old French, but it is more widely
used than any other.</note></p><p>Where recourse to reference works is impossible, a picture of the
character may be encoded using any standard graphics format, and
associated with the character by standard SGML techniques.  The SGML
document must then have:
<list type="bullets"><item>an SGML notation declaration for the graphics format used</item><item>an external entity declaration for the file containing the image</item><item>an <gi tei="yes">extFigure</gi> element to name the notation and the entity</item></list>
 
For a discussion of graphic images and of the declaration of non-SGML
notations, see chapter <xref target="FT"/>.  If the Old French abbreviation
is encoded using CGM (Computer Graphics Metafile) format in a file
called <ident tei="yes" type="file">est.cgm</ident>, then it may be associated with the appropriate
character declaration as follows.  In the DTD subset of the WSD, the
following declarations are required:
 
<eg><![CDATA[ <!NOTATION cgm PUBLIC 'ISO 8632/2//NOTATION
                        Computer Graphics Metafile
                        Character encoding//EN'>
 <!ENTITY estFigure system 'est.cgm' NDATA cgm>]]></eg>
 
In the body of the WSD itself:
 
<eg><![CDATA[<character class='lexical'>
  <form string=''
        entityLoc="est">
            <desc>Old French abbreviation for 'est':  lowercase
                  'e' with a tilde or macron above.
            </desc>
            <extFigure notation='cgm' entity='estFigure'>
            <note>For an image of this character, see
                  Cappelli, p. 110, column 1, line 4
                  (leftmost and rightmost item).
            </note>
  </form>
</character>]]></eg>
 
Despite now having a picture of the character, we retain the prose
description and reference to Cappelli, for the sake of those without
ready access to the appropriate graphics processors.
 <!-- < p > Figures and detailed descriptions of the           --><!-- character form are particularly important when the       --><!-- encoding is to distinguish different forms or shapes     --><!-- of the same character.  For example, consider the        --><!-- situation described in chapter  < xref target=CH > ,     --><!-- in which the encoder wishes to distinguish among three   --><!-- distinct forms of the letter < cited > r < /cited >      --><!-- because they may help trace the history of the           --><!-- manuscript.  The three forms may be documented thus in   --><!-- the WSD:                                                 -->
 <!--  < eg >                                                  --><!--  < ![ CDATA [                                            --><!--                                                          --><!--   (three-R example here)                                 --></p><p>The <gi tei="yes">exceptions</gi> element and its contents are declared thus:
 
<dtdFrag id="DWDCSEX" n="Exceptions to the base components"><tagDecl tagDoc="EXCEPTNS"/><tagDecl tagDoc="WSDCHAR"/><tagDecl tagDoc="WSDDESC"/><tagDecl tagDoc="WSDFORM"/><tagDecl tagDoc="WSDFIG"/><tagDecl tagDoc="WSDXFIG"/></dtdFrag></p></div3><div3 id="WDCSCC" name="subsection" ref="Y"><head>Documenting Coded Character Sets and Entity Sets</head><p>Public or private coded character sets and entity sets may be
usefully documented using WSDs; the WSD will make explicit some
information (such as the UCS-4 and AFII codes) not normally given
explicitly in character set standards or public entity sets.  The coded
character set or entity set being documented should be included by means
of a <gi tei="yes">codedCharSet</gi> or <gi tei="yes">entitySet</gi> element; the
<gi tei="yes">exceptions</gi> element should include one <gi tei="yes">character</gi>
element for each character included in the character set or the entity
set.  Deciding whether to treat two entities or two bit patterns as
separate characters or as forms of the same character will require
knowledge of the script involved, and different encoders may reach
different decisions.  In cases of doubt, though, it is usually
acceptable practice to treat each bit pattern in a coded character set,
and each entity in an entity set, as a distinct character.</p><p>A non-standard local coded character set (e.g. an EBCDIC character
set) may be documented in a WSD by defining one <gi tei="yes">character</gi>
element for each printable code point in the character set, adding the
names of standard (and local) entities, UCS-4 codes, and AFII codes as
appropriate.  Since this extra information is useful in packing
documents for interchange, and in processing pattern
arguments in the TEI extended-pointer syntax described in section<xref target="SAXR"/>
, those responsible for a
local installation are strongly encouraged to document the local system
character set in a WSD, if it is not already so documented.</p></div3><div3 id="WDCSTR" name="subsection" ref="Y"><head>Documenting Transliteration Schemes</head><p>When a script is encoded not in a character set designed for it,
but in one designed for another script, (e.g. Greek encoded using the
Latin alphabet), a transliteration scheme is necessary.  In
documenting such a transliteration scheme, the coded character set
actually in use should be named as a base component.  An
<gi tei="yes">exceptions</gi> element can then be used to override the normal
meaning of the individual byte strings used in the transliteration.
For example, the following <gi tei="yes">character</gi> element overrides the
usual association of the byte representing <code tei="yes" type="frag">A</code> with the Latin
letter <code tei="yes" type="frag">A</code> and substitutes instead an association with the Greek
letter alpha:
 
<eg><![CDATA[<character class=lexical>
  <form string='A' entityStd="agr" ucs-4='03B1' afiicode='260061'>
    <desc>Greek small letter alpha</desc>
  </form>
</character>]]></eg>
 
Care should be taken in choosing or developing transliteration schemes
to ensure that they are unambiguously reversible.</p></div3></div2><div2 id="WDNO" name="Anthony" ref="Y"><head>Notes in the WSD</head><p>Notes on the WSD, individual characters, or individual character
forms may be included in the <gi tei="yes">note</gi> element at the appropriate
level.
 
<tagList style="one-line"><tagDesc tagDoc="WSDNOTE"/></tagList></p><p>Unlike its counterpart in the main TEI DTD, the <gi tei="yes">note</gi> element
within the writing system declaration may contain no paragraphs and no
phrase-level elements:  only character data.  It is formally declared
thus:
 
<dtdFrag id="DWDNO" n="Notes"><tagDecl tagDoc="WSDNOTE"/></dtdFrag></p></div2><div2 id="WDLK" name="Anthony" ref="Y"><head>Linkage between WSD and Main Document</head><p>The writing system declaration is associated with different portions
of a main document by means of the global <att tei="yes">lang</att> attribute.
This attribute is defined as an SGML IDREF and its value must be the
SGML identifier on a <gi tei="yes">language</gi> element within the TEI header of
the main document.  The <gi tei="yes">language</gi> element in turn provides, in
its <att tei="yes">wsd</att> attribute, the SGML name of the entity (usually an
external file) containing the writing system declaration associated with
that <att tei="yes">lang</att> value. For a more detailed account of this
process, compare the discussion in section <xref target="FDLK"/>.</p><p>At least one writing system declaration must be associated with any
TEI document:  this follows from the requirement that a value be
specified for the <att tei="yes">lang</att> attribute on the outermost element
(<gi tei="yes">tei.2</gi> or <gi tei="yes">teiCorpus.2</gi>) of any TEI document, since the
<att tei="yes">lang</att> attribute is required to point at a <gi tei="yes">language</gi>
element in the TEI header, which in turn is required to indicate an
entity containing the writing system declaration associated with that
language.</p></div2><div2 id="WDXW" name="Anthony" ref="Y"><head>Predefined TEI WSDs</head><p>The Text Encoding Initiative has defined standard writing system
declarations for the following languages and scripts:
 
<list type="bullets"><item>The nine official languages of the European Community ( Danish,
Dutch, English, French, Greek, German, Italian, Portuguese, and
Spanish), encoded using the character set ISO 8859-1</item><item>Hebrew (using ISO 8859-8)</item><item>Russian (using ISO 8859-5)</item><item>classical Greek (using the Thesaurus Linguae
Graecae's Beta Code transliteration scheme)</item></list></p><p>Work is underway on a standard writing system declarations for
Japanese; resources permitting, declarations for Korean and Chinese will
also be made.</p><p>In addition to the language-specific WSDs just mentioned, the TEI has
defined a number of WSDs to document specific public coded character
sets and entity sets.  These are used as components in the
language-specific WSDs, and may be similarly used for locally developed
WSDs.  WSDs for specific ISO standard character sets include:
 
<list type="bullets"><item>ISO 646 (non-national subset)</item><item>ISO 646 (International Reference Version)</item><item>ISO 8859-1 (Latin 1, Western Europe)</item><item>ISO 8859-2 (Latin 2, Eastern Europe)</item><item>ISO 8859-5 (Latin and Cyrillic)</item><item>ISO 8859-7 (Latin and Greek)</item><item>ISO 8859-8 (Latin and Hebrew)</item><item>ISO 8859-9 (Western Europe and Turkey)</item></list></p><p>Writing system declarations are also under preparation for a number
of commercial character sets in wide use:
 
<list type="bullets"><item>IBM Code Page 437 (IBM PC, early models)</item><item>IBM Code Page 850 (IBM PS/2 and later-model IBM PCs)</item><item>IBM Code Page 1014</item><item>Apple Macintosh default system character set</item><item>Adobe Postscript default character set</item></list></p><p>The Text Encoding Initiative has prepared entity sets for use in
transcribing some languages; these are distributed both as SGML entity
sets and as TEI writing system declarations documenting those entity
sets:
 
<list type="bullets"><item>-//TEI P3: 1994//ENTITIES Arabic//EN</item><item>-//TEI P3: 1994//ENTITIES Coptic//EN</item><item>-//TEI P3: 1994//ENTITIES Classical Greek//EN</item><item>-//TEI P3: 1994//ENTITIES International Phonetic Alphabet//EN</item></list>
 
WSDs will also be prepared for other standard entity sets, including:
 
<list type="bullets"><item>ISO 8879: 1986//ENTITIES Added Latin 1//EN</item><item>ISO 8879: 1986//ENTITIES Added Latin 2//EN</item><item>ISO 8879: 1986//ENTITIES Russian Cyrillic/EN</item><item>ISO 8879: 1986//ENTITIES Non-Russian Cyrillic//EN</item><item>ISO 8879: 1986//ENTITIES Greek Letters//EN</item><item>ISO 8879: 1986//ENTITIES Diacritical Marks//EN</item><item>ISO 8879: 1986//ENTITIES Box and Line Drawing//EN</item><item>ISO 8879: 1986//ENTITIES Numeric and Special Graphic//EN</item><item>ISO 8879: 1986//ENTITIES Publishing//EN</item><item>ISO 8879: 1986//ENTITIES General Technical//EN</item></list></p><p>All TEI writing system declarations are distributed with the TEI
document type definitions.
 <!-- div2 id=WSUS > < head > Creating New WSDs < / head --></p><p>The standard TEI writing system declarations are expected to meet the
needs of many encoders; some, however, will need to prepare new WSDs to
describe character-encoding schemes not included in the standard WSDs.<!-- This paragraph needs expansion.  But I'm tired. -msm     --><!-- Me too. This sentence doesnt seem to say very much. LB --></p></div2><div2 id="WDSE" name="Anthony" ref="Y"><head>Details of WSD Semantics</head><p>This section describes the meaning of the WSD in more formal terms
than have been used elsewhere in this chapter; it can be skipped by most
readers, but should be read carefully by those who wish to write complex
writing system declarations or to implement software to process writing
system declarations or to interpret them in the processing of
TEI-conformant documents.</p><div3 id="WDSEGE" name="subsection" ref="Y"><head>WSD Semantics:  General Principles</head><p>A writing system declaration provides a complicated bundle of
mappings:
 
<list type="bullets"><item>a 1:1 partial function from strings in given coded character sets
to character forms</item><item>a function from entity names to character forms, and therefore
derivatively a function from entity names to strings</item><item>a function from character forms to characters, and therefore
derivatively:
<list type="bullets"><item>a function from strings to characters</item><item>a function from entity names to characters</item></list></item><item>a relation between UCS-4 codes and character forms</item><item>a relation between AFII codes and character forms</item><item>a function from UCS-4 codes to characters</item><item>a relation from AFII codes to characters</item></list>
 
To ensure that the relations described as functions are in fact
functional, the following constraints apply on the WSD:
 
<list type="bullets"><item>No two <gi tei="yes">form</gi> elements can have the same values for both
<att tei="yes">codedCharSet</att> and <att tei="yes">string</att>.  Since usually there is
only one <gi tei="yes">codedCharSet</gi> used as a basic component, this usually
means each <att tei="yes">string</att> attribute value must be unique in the WSD.</item><item>No two <gi tei="yes">form</gi> elements can name the same entity in either
<att tei="yes">entityStd</att> or <att tei="yes">entityLoc</att>.  It is legal, though
pointless, for both <att tei="yes">entityStd</att> and <att tei="yes">entityLoc</att> on the
same <gi tei="yes">form</gi> element to name the same entity.</item><item>More than one <gi tei="yes">form</gi> element may have the same
<att tei="yes">UCS-4</att> value, but if so
they must be within the same <gi tei="yes">character</gi> element.
 <!-- n.b. removed the restriction on AFII codes -msm --></item></list>
 
These constraints may be summarized thus:  one
<soCalled>character</soCalled> (however the creator of the WSD defines a
character) can be associated with more than one byte string, entity
name, UCS-4 code, or AFII code, but any single byte string (given a
specific coded character set), any single entity name, and any single
UCS-4 code must be associated with only one single
<gi tei="yes">character</gi>.  One can, for example, associate both
<q>tilde</q> and
<q>logical not</q> with a <gi tei="yes">character</gi> meaning <q>logical
negation</q>, but one cannot associate both a <gi tei="yes">character</gi> called
<q>tilde</q> and one called <q>logical negation</q> with the ASCII
character 7/14:  given a 7/14 in the text, it must be unambiguously
clear whether the character is a <q>tilde</q> or a <q>logical
negation</q>.  If one wishes to retain the ambiguity, one must define a
<gi tei="yes">character</gi> called (for example)
<q>logical-not or tilde or swung-dash</q>.
Similar restrictions apply to entity names and UCS-4 codes:  each must
be associated with a single <gi tei="yes">character</gi> element.</p></div3><div3 id="WDSEBC" name="subsection" ref="Y"><head>Semantics of WSD Base Components</head><p>The effects of naming coded character sets, entity sets, and other
WSDs as base components may now be defined thus:
 
 
<list type="bullets"><item>reference to a coded character set makes available the set of
bit-pattern-to-character mappings defined in the coded character set.
That is, if a WSD refers to a coded character set, then whenever the WSD is
in use, any character in that coded character set may be used with its
standard meaning unless it has been redefined using the
<gi tei="yes">exceptions</gi> element.  It is recommended that a WSD be provided
for each coded character set, to make the mappings fully explicit.</item><item>reference to an entity set makes available the set of
entity-name-to-character mappings defined in the entity set.  It is
assumed that standard public entity sets contain enough information to
count as a valid mapping; for private entity sets, the preferred method
of providing the necessary information is to define the entity set in a
WSD.  If for example a WSD refers to the ISO Latin 1 entity set, then
whenever that WSD is in use, any entity in that set may be used with
its public meaning, unless it has been redefined in the
<gi tei="yes">exceptions</gi> element.</item><item>reference to a WSD makes available the set of mappings declared in
that WSD; the language and writing system direction information given
in the base WSD is ignored.</item></list></p><p>If reference is made only to standard character sets and entity
sets, there is no mechanical method of associating the
<soCalled>characters</soCalled> involved in one mapping with those
involved in another.  E.g. a reference to ISO 646 IRV provides a map
from code point 5/11 to a character one might call <q>left square
bracket</q>.  A reference to entity set <ident tei="yes" type="file">ISOpub1</ident>
provides a map from the entity name <ident tei="yes" type="ent">lbr</ident> to
what should probably be considered the same character.  There is
however no guarantee that any processing software will necessarily be
sufficiently intelligent to make this association of mappings
automatically; it requires hard-coded knowledge of the specifics of
certain character sets and entity sets.</p><p>When, however, base WSDs are used to document important entity sets
and character sets, it does become possible to define mechanical
methods of associating <gi tei="yes">character</gi> elements in different base
components.</p></div3><div3 id="WDSEMB" name="subsection" ref="Y"><head>Multiple Base Components</head><p>When multiple bases of the same type are referred to, the effects are
these:
 
<list type="bullets"><item>if more than one coded character set is named, then it is
expected that character-set shifting as described in ISO 2022 or
some equivalent is in use, and proper shifting is the responsibility
of the user.  All strings in the WSD must specify the ID of
the proper coded-character-set base, using the
<att tei="yes">codedCharSet</att> attribute.</item><item>if more than one entity set is named, then entity names from all
named sets may be used as values of the <att tei="yes">entityStd</att> and
<att tei="yes">entityLoc</att> attributes.  If the same name occurs in more than
one entity set, the assumption is made that it refers each time to the
same character.</item><item>if more than one base WSD is named, then all characters declared
in all the WSDs are available.  For this case, we can define what
happens to merge the different base components more precisely than for
the other types of base component:
 
<list type="bullets"><item>any two <gi tei="yes">form</gi> elements which name the same entity or the
same string in the same coded character set are considered the same
form, and are merged as described below in section <xref target="WDSEME"/>.</item><item>any two <gi tei="yes">form</gi> elements which give the same UCS-4 code are
considered forms of the same <gi tei="yes">character</gi>, and their parent
<gi tei="yes">character</gi> elements are merged.  The forms themselves may be
merged or may remain distinct:  if the forms have conflicting values for
any attribute, they must remain distinct; if they don't conflict, they
may be merged, at the option of the processing software.  In the general
case, there might be more than one way to perform mergers, so merger is
not required.</item></list></item></list></p><p>The result of invoking multiple base WSDs is thus a merged WSD in
which the <gi tei="yes">form</gi> and <gi tei="yes">character</gi> elements have been merged
as prescribed.  If the merger is impossible because the two WSDs are
incompatible, a semantic error occurs.  A set of WSDs is compatible and
may be invoked together if all of the following are true:
 
<list type="bullets"><item>any given entity name is associated with a single string
          (in a given coded character set) and a single character class</item><item>any given string or UCS-4 code is
          associated with a single character class</item></list></p></div3><div3 id="WDSEEX" name="subsection" ref="Y"><head>Semantics of Exceptions</head><p>We can now define the semantics of the <gi tei="yes">exceptions</gi> element.</p><p>The base components provide a preliminary set of mappings, as
described above.  For convenience let us call this the <term>default
map</term>.  The <gi tei="yes">exceptions</gi> element allows the user to modify
the default map by defining further mappings and by overriding parts of
the default map.  There are three cases:  a new <gi tei="yes">character</gi>
element replaces an old one, is merged with an old one, or is added to
the set without affecting any old ones.</p><div4 id="WDSEX1" name="Section" ref="Y"><head>Case 1: replacement</head><p>If a <gi tei="yes">form</gi> element within <gi tei="yes">exceptions</gi> (F-new)
<soCalled>collides</soCalled> with a <gi tei="yes">form</gi> element in the
default map (F-old), then the parent <gi tei="yes">character</gi> element of
F-new replaces the parent element of F-old.  Two <gi tei="yes">form</gi>
elements collide if they have the same values for
<att tei="yes">codedCharSet</att> and <att tei="yes">string</att>.  (N.B. if this
condition occurs within the default map, the two <gi tei="yes">form</gi>
elements are merged.)  </p><p>For example, to define the TLG Beta code transliteration of alpha
as <code tei="yes" type="frag">a</code> we first name ISO 646 IRV as a base component; this has
the effect of creating the following (possibly imaginary)
<gi tei="yes">form</gi> element:
 
 
<eg><![CDATA[          <character id=A class=lexical>
            <form string='a'>
              <desc>lowercase latin letter A</desc>
            </form>
          </character>]]></eg></p><p>We then include the following within the <gi tei="yes">exception</gi> element:
 
<eg><![CDATA[          <character id=ALPHA class=lexical>
            <form string='a' entityStd='gkalpha'>
              <desc>lowercase Greek alpha</desc>
            </form>
          </character>]]></eg></p><p>This overrides the <gi tei="yes">character</gi> element for latin A, and
indicates that in the transliteration scheme documented by this WSD,
character 6/01 represents a Greek alpha, no matter what ISO 646 says.</p></div4><div4 id="WDSEX2" name="Section" ref="Y"><head>Case 2: merger</head><p>If a <gi tei="yes">character</gi> element within <gi tei="yes">exceptions</gi>
<soCalled>overlaps</soCalled> with one in the default map, then the
two <gi tei="yes">character</gi> elements are merged.  Two <gi tei="yes">character</gi>
elements overlap if any of their <gi tei="yes">form</gi> elements name the same
entity or UCS-4 code.  (N.B. if these conditions occur within the
default map, they lead to merger either of the two <gi tei="yes">form</gi>
elements --- for entity name overlap --- or of the two
<gi tei="yes">character</gi> elements.)  </p><p>For example:  suppose we wish to document the three-Rs transcription
described in section <xref target="CHLON"/>.  We name ISO 646 IRV as a base
character set (or WSD) and add the following exceptions:
 
<eg><![CDATA[  <exceptions>
    <character id=R class=lexical>
        <desc>lowercase latin letter r</desc>
        <form string='' entityLoc='r' ucs-4='0072'>
            <desc>'normal' form, similar to modern print r and to
                  Cappelli, p. 318, line 2, items 3, 6, 15.</desc>
        </form>
        <form string='' entityLoc='r2' ucs-4='0072'>
            <desc>'round' form, usually following 'o', similar
                  to a modern Arabic digit 2 (or to Cappelli, p. 318,
                  line 2, items 13 and 14)</desc>
        </form>
        <form string='' entityLoc='r3' ucs-4='0072'>
            <desc>'small-cap' form, like a capital R but
                  same height as lowercase (cf. Cappelli, p. 318,
                  line 1, items 2 and 3)</desc>
        </form>
    </character>
  </exceptions>]]></eg></p><p>As a second example, imagine we wish to document a local entity set
for Old English in which we define local entities t (thorn), d (eth),
and a (aesc).  Assuming the TEI has provided a WSD for the Latin 1
entities, the whole WSD is this:
 
<eg><![CDATA[  <writingSystemDeclaration
         name='-//OTA 1990//NOTATION WSD Old English entities//EN'
         date='1993-05-25'
         lang=eng>
    <language iso639=''>Various</language>
    <script>Latin alphabet, extended</script>
    <direction lines=TB chars=LR>
    <characters>
          <baseWsd name='-//TEI P3: 1994//NOTATION
                         WSD ISO Added Latin 1//EN'
                   authority=TEI>
          <exceptions>
              <character class=lexical>
                  <form entityStd='thorn' entityLoc='t'>
                      <desc>lowercase latin letter thorn</desc>
                      </form></character>
              <character class=lexical>
                  <form entityStd='Thorn' entityLoc='T'>
                      <desc>uppercase latin letter thorn</desc>
                      </form></character>
              <character class=lexical>
                  <form entityStd='eth' entityLoc='d'>
                      <desc>lowercase latin letter eth</desc>
                      </form></character>
              <character class=lexical>
                  <form entityStd='Eth' entityLoc='D'>
                      <desc>uppercase latin letter eth</desc>
                      </form></character>
              <character class=lexical>
                  <form entityStd='aelig' entityLoc='a'>
                      <desc>lowercase latin aesc (= digraph aelig)</desc>
                      </form></character>
              <character class=lexical>
                  <form entityStd='AElig' entityLoc='A'>
                      <desc>uppercase latin aesc (= digraph aelig)</desc>
                      </form></character>
          </exceptions>
    </characters>
    <note>This WSD is just to document the local entities; it should be
          named as a base WSD by the actual writing system declaration.
    </note>
  </writingSystemDeclaration>]]></eg></p><p>This has the effect of merging the <gi tei="yes">character</gi> elements for
<code tei="yes" type="frag">thorn</code>, <code tei="yes" type="frag">eth</code>, and <code tei="yes" type="frag">aesc</code> (or a-e
ligature) defined in the ISO Latin 1 WSD with those given here, which
specify the local entity name.  The <gi tei="yes">form</gi> elements may or may
not be merged, so the software may or may not actually realize that
the local entity <ident tei="yes" type="ent">t</ident> corresponds with the UCS-4
code given in the TEI WSD for ISO Latin 1.</p><p>The full local WSD can then be this:
 
<eg><![CDATA[  <writingSystemDeclaration
         name='-//OTA 1993//NOTATION Old English WSD//EN'
         date='1993-05-25'
         lang=eng>
    <language iso639=ang>Anglo-Saxon / Old English</language>
    <script>Latin alphabet, extended</script>
    <direction lines=TB chars=LR>
    <characters>
          <baseWsd name='-//TEI P3: 1994//NOTATION WSD ISO 646 IRV//EN'
                   authority='TEI'>
          <baseWsd name='-//OTA 1990//NOTATION
                         WSD Old English entities//EN'
                   authority='private'>
          <baseWsd name='-//TEI P3: 1994//NOTATION
                         WSD ISO Added Latin 1//EN'
                   authority='TEI'>
    </characters>
  </writingSystemDeclaration>]]></eg></p><p>We refer explicitly to ISO Latin 1, for clarity, but in theory it
has already been included in <ident tei="yes" type="file">-//OTA 1990//WSD Old English
entities//EN</ident> and need not be repeated.  At this time, the
rules for merger would force our local <gi tei="yes">form</gi> elements to be
merged with the standard <gi tei="yes">form</gi> elements, so the local entity
<ident tei="yes" type="ent">t</ident> would map correctly into the UCS-4 character
set.</p></div4><div4 id="WDSEX3" name="Section" ref="Y"><head>Case 3: expansion</head><p>If a <gi tei="yes">character</gi> element has no <gi tei="yes">form</gi>
children which collide with anything in the default map, and does not
itself overlap with anything in the default map, then it is simply added
to the default map.</p><p>For example, suppose we wish to document an abbreviation used for
Old French <q>est</q> in our manuscript, which resembles e with a
tilde or macron.  Since we expect we may have more abbreviations for
<q>est</q>, we use the local entity name <ident tei="yes" type="ent">est1</ident>
for this one.  Within <gi tei="yes">exceptions</gi>, we declare the abbreviation
thus:
 
<eg><![CDATA[          <character id=EST1 class=lexical>
            <form string='' entityLoc='est1'>
              <desc>abbreviation for 'est', lowercase latin e
                    with a tilde or macron above, similar to
                    Cappelli p. 113, col 1, items 4(a) and 8.</desc>
            </form>
          </character>]]></eg></p></div4></div3><div3 id="WDSEME" name="subsection" ref="Y"><head>Merger of Form and Character Elements</head><p>In some cases, the <gi tei="yes">form</gi> and <gi tei="yes">character</gi> elements
introduced notionally by reference to a coded character set or entity
set, or introduced explicitly by reference to a base WSD, may be
considered as referring to identical objects; this is called
<term>merger</term>.  Two <gi tei="yes">form</gi> elements F1 and F2 can be merged
if they both have the same values for <att tei="yes">codedCharSet</att> and
<att tei="yes">string</att>, or if <att tei="yes">codedCharSet</att> and <att tei="yes">string</att>
are unspecified (implied) in at least one.  When F1 and F2 are merged,
the result is a (possibly imaginary) <gi tei="yes">form</gi> element (F3) the
attributes of which are derived thus:
 
<list type="bullets"><item>if F1 has no value for a <att tei="yes">codedCharSet</att>, then F3 has the
same value for this attribute as does F2.  If both F1 and F2 have
explicit values, the values must be identical.</item><item>if F1 has an empty string for <att tei="yes">string</att>, then F3 has the
same value as F2.  If both have values other than the empty string,
they must be identical.</item><item>for <att tei="yes">entityStd</att>, <att tei="yes">entityLoc</att>, <att tei="yes">ucs-4</att>,
and <att tei="yes">afiiCode</att>, F3 gets a value containing all the entity names
or codes which appear in the corresponding attribute values of either F1
or F2.  I.e. the attribute values are viewed as sets, and F3 gets the
union of F1 and F2.</item></list></p><p>The children of the new element are derived by taking all the
<gi tei="yes">desc</gi> children of F1, then all the <gi tei="yes">desc</gi> children of F2;
all the <gi tei="yes">figure</gi> children of F1, then those of F2; all the
<gi tei="yes">note</gi> children of F1, then all the <gi tei="yes">note</gi> children of F2.
In other words, all the children of the source elements survive as
children of the result element.</p><p>Provided that their forms are compatible, two <gi tei="yes">character</gi>
elements C1 and C2 may be merged unless their values for
<att tei="yes">class</att> differ.  The resulting <gi tei="yes">character</gi> element C3
has the same value for its <att tei="yes">class</att> attribute as C1 and C2,
and all the children of C1 and C2 are made children of C3
(<gi tei="yes">desc</gi> children first, then <gi tei="yes">form</gi> children).</p><p>Note that merger is sometimes required by the semantic rules given
above, and sometimes optional.  If merger is required but not legal
(because the two elements to be merged are incompatible), then a
semantic error has occurred and the two base WSDs which give rise to it
should not be invoked together.</p></div3></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2wd.odd ??><!-- 25 Writing System Decl. --><?tei:SOF p2fd.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2fd.odd,v $
    * Revision 1.13  1998/02/01 16:18:53  tei
    * change system to public identifier (again)
    *
    * Revision 1.12  1998/01/31 19:14:05  tei
    * Use public identifiers, not system identifiers.
    *
    * Revision 1.11  1998/01/31 18:27:01  tei
    * fix log keyword
    *
    * Revision 1.10  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.9  1994/04/07  23:57:46  msmcq
    * revision while validating dtd
    * 
    * Revision 1.8  1994/04/01  16:23:58  msmcq
    * Misc. changes/fixes while validating DTDs
    * 
    * Revision 1.7  1994/03/28  17:31:16  msmcq
    * changes to dtdfrags
    * 
    * Revision 1.6  1994/03/27  21:48:09  msmcq
    * Correction of typos found by WWP, DB
    *--><!-- Revisions:                                               --><!-- 94-04-08 : MSM : correct tagging slip                    --><!-- 94-04-07 : MSM : embed teifs2.dtd                        --><!-- 94-04-07 : MSM : suppress duplicate declaration of THEN  --><!-- 94-04-07 : MSM : create better overall dtdfrag           --><!-- 94-03-29 : MSM : add fsDescr to a dtdfrag                --><!-- 94-03-28 : MSM : add file info to dtdfrags               --><!-- 94-03-27 : MSM : typos from EM, DB                       --><!-- 93-05-31 : MSM : recast two footnotes                    --><!-- 93-05-23 : GS  : revisions following Eynsham review      --><!-- 93-04-09 : MSM : complete update                         --><!-- 1993-04-09 : MSM : complete about half of GS's updates   --><!-- 1993-04-08 : MSM : tag as an Odd, make tagdocs           --><!-- From: gary@sil.org (Gary Simons)                         --><!-- X-Mailer: SCO System V Mail (version 3.2)                --><!-- To: u35395@uicvm.uic.edu                                 --><!-- Subject: Draft of FSD chapter                            --><!-- Date: Wed, 1 Jul 92 7:13:38 CDT                          --><div1 id="FD" n="26" name="Faisal" ref="Y"><head>Feature System Declaration</head><p>The Feature System Declaration (FSD) is an auxiliary file used in
conjunction with a TEI-conforming text that makes use of <gi tei="yes">fs</gi>
(that is, feature structure) elements.
 <!-- <note place=foot><p>The primary responsibility for this --><!-- chapter was borne by work group AI 1, for linguisticstudy, --><!-- whose members are listed in the front matter.  It was --><!-- drafted by Gary F.  Simons.</p></note>  -->
 
The FSD serves three purposes:
 
<list type="simple"><item>It provides a mechanism by which the encoder can list all of the
feature names and feature values and give a prose description as to what
each represents.</item><item>It provides a mechanism by which the encoder can define
constraints on what it means to be a well-formed feature structure.
These constraints may involve constraints on the range of a feature
value, constraints on what features are valid within certain types of
feature structures, or constraints that prevent the co-occurrence of
certain feature-value pairs.</item><item>It provides a mechanism by which the encoder can define the
intended interpretation of underspecified feature structures.  This
involves defining default values (whether literal or computed) for
missing features.</item></list></p><p>As a component of the interchange standard for encoded text, the FSD
serves an important function in documenting precisely what the encoder
intended by the system of feature structure markup used in the encoded
text.  As application software is developed which makes use of encoded
texts, the FSD will also become an important resource that will allow
software to validate the feature structure markup in a text and to infer
the full interpretation of underspecified feature structures.</p><p>This chapter begins by describing how the encoded text uses header
information to make links to any associated FSDs.  The second through
fourth sections describe the overall structure of an FSD and give
details of how to encode its parts.  The final section offers a full
example.
<note source="auth" place="foot" anchored="Y">For a fuller discussion of the reasoning behind FSDs
and for another complete example, see <q>A rationale for the TEI
recommendations for feature-structure markup,</q> by D. Terence
Langendoen and Gary F. Simons (to appear in the special TEI issue of
<title>Computers and the Humanities</title>).</note></p><div2 id="FDLK" name="Anthony" ref="Y"><head>Linking a TEI Text to Feature System Declarations</head><p>In order for application software to use feature system declarations
to aid in the automatic interpretation of encoded texts, or even for
human readers to find the appropriate declarations which document the
feature system used in markup, there must be a formal link from the
encoded texts to the declarations.  As it turns out, the mechanism for
linking texts to FSDs parallels the mechanism for linking texts to
writing system declarations (WSDs).
 <!-- described in chapter <xref target=WD>,--></p><p>The linkage is made in two places.  First, in the DTD subset of the
document type declaration at the beginning of the text file, an external
entity is defined for each FSD that is associated with the encoded text.
That entity declaration associates an entity name with the name of a
file on the host system.  It appends the SUBDOC keyword to tell the
processor that the named file is a self-contained SGML document.  See
the example below for details of syntax.</p><p>The second place in which the linkage from text to FSDs is made is in
the TEI header, as mentioned in section <xref target="HDFSD"/>.  Within the
<gi tei="yes">encodingDesc</gi> element, a special <gi tei="yes">fsdDecl</gi> element may be
used for each distinct feature structure type, as follows:
 
<tagList style="one-line"><tagDesc tagDoc="FSDDECL" atts="type fsd"/></tagList>
 
Note that one <gi tei="yes">fsdDecl</gi> element must be specified for each
distinct type of feature structure used in the markup.  The
<att tei="yes">fsd</att> element supplies the name of the external entity
containing the actual declaration for that type of feature structure.</p><p>There may be multiple <gi tei="yes">fsdDecl</gi> elements for a given FSD; one
for each type of feature structure it defines.  For instance, in the
following example, the file <ident rend="noindex" tei="yes" type="file">lex.fsd</ident> contains an FSD that contains definitions
of feature structures for both lexical entries (<tag compl="full" tei="yes">fs
type=entry</tag>) and lexical subentries (<tag compl="full" tei="yes">fs type=subentry</tag>).</p><p>The following example shows the markup for linking a TEI document to
two WSDs and two FSDs.  The linkage to both WSDs and FSDs is shown in
order to illustrate the parallel nature of the linking mechanisms for
both kinds of auxiliary files.
 
<eg><![CDATA[   <!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                          "tei2.dtd" [
      <!-- In the DTD subset, we declare external
           entities for our FSDs and WSDs.        -->
      <!ENTITY wsd.english system 'en.wsd'   SUBDOC >
      <!ENTITY wsd.french  system 'fr.wsd'   SUBDOC >
      <!ENTITY fsd.gazdar  system 'gpsg.fsd' SUBDOC >
      <!ENTITY fsd.lexicon system 'lex.fsd'  SUBDOC >
   ]>
   <tei.2>
 
   <teiHeader>
      <!-- In the encoding description of the TEI header,
           we link the FSDs to the fs TYPE attribute;
           in the profile description,
           we link the WSDs to the global LANG attribute.
           -->
      <fileDesc> ... </fileDesc>
      <encodingDesc>
           <!-- ... -->
           <fsdDecl type=GPSG     fsd=fsd.gazdar>
           <fsdDecl type=entry    fsd=fsd.lexicon>
           <fsdDecl type=subentry fsd=fsd.lexicon>
           <!-- ... -->
      </encodingDesc>
      <profileDesc>
           <!-- ... -->
           <langUsage>
               <language id=EN wsd=wsd.english>English</>
               <language id=FR wsd=wsd.french >French</>
           </langUsage>
      </profileDesc>
   </teiHeader>
   <!-- The text goes here -->
   </tei.2>]]></eg></p><p>The auxiliary tag set for feature system declarations is contained
in the file <ident tei="yes" type="file">teifsd2.dtd</ident>, which has the
public identifier <code tei="yes" type="frag">-//TEI P3//DTD Auxiliary Document Type:
Feature System Declaration//EN</code> and the overall structure shown
below:
 
<dtdFrag id="DFDDTD" n="Feature System Declaration" file="teifsd2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>First, we declare basic parameter entities and embed
auxiliary files.</commDecl><commDecl>Embed entities for TEI generic identifiers.</commDecl><entDecl entDoc="TEIGIS"/><peRef n="TEI.elementNames"/><commDecl>Embed entities for TEI keywords.</commDecl><entDecl entDoc="TEIKW"/><peRef n="TEI.keywords.ent"/><commDecl>Define element classes for content models, shared
attributes for element classes, and global attributes.  (This all
happens within the file teiclas2.ent.)</commDecl><entDecl entDoc="TEIECGA"/><peRef n="TEI.elementClasses"/><commDecl>Define element classes for feature structure
declarations.</commDecl><claDecl classDoc="BOOLEAN" type="model"/><claDecl classDoc="BINARY" type="model"/><claDecl classDoc="SINGVAL" type="model"/><claDecl classDoc="CPLXVAL" type="model"/><claDecl classDoc="FEATVAL" type="model"/><commDecl>Now, we declare the elements for FSDs proper.</commDecl><dtdRef dtdFrag="DFDFSD2"/><dtdRef dtdFrag="DFDX"/><dtdRef dtdFrag="DFD2"/><commDecl>The elements for feature structures themselves
are declared in teifs2.dtd</commDecl><entDecl entDoc="FSDTD"/><peRef n="TEI.fs.dtd"/><commDecl>Finally, embed the TEI header and core tag sets.</commDecl><entDecl entDoc="TEIHDR"/><peRef n="TEI.header.dtd"/><entDecl entDoc="TEICORE"/><peRef n="TEI.core.dtd"/></dtdFrag></p></div2><div2 id="FDOV" name="Anthony" ref="Y"><head>The Overall Structure of a Feature System Declaration</head><p>A feature system declaration is encoded as a document of type
<gi tei="yes">teiFsd2</gi>.  It has two parts:  an obligatory header (which
provides bibliographic information for the file) and a set of feature
structure declarations (each of which defines one type of feature
structure).  Each feature structure declaration in turn has three parts:
an optional description (which gives a prose comment on what that type
of feature structure encodes), an obligatory set of feature declarations
(which specify range constraints and default values for the features in
that type of structure), and optional feature structure constraints
(which specify co-occurrence restrictions on feature values).  The
header is encoded as a <gi tei="yes">teiHeader</gi>, just as for any TEI.2
document; see chapter <xref target="HD"/>.  The other components listed
above are unique to feature system declarations.  Thus, the following
new elements are involved:
 
<tagList style="one-line"><tagDesc tagDoc="TEIFSD2"/><tagDesc tagDoc="FSDECL" atts="type baseType"/><tagDesc tagDoc="FSDESCR"/><tagDesc tagDoc="FDECL"/><tagDesc tagDoc="FSCONSTR"/></tagList></p><p>Feature declarations and feature structure constraints are described
in the next two sections of this chapter.  Note that the specification
of similar <gi tei="yes">fsDecl</gi> elements can be simplified by devising an
inheritance hierarchy for the feature structure types.  Each
<gi tei="yes">fsDecl</gi> may name a <att tei="yes">baseType</att> from which it inherits
feature declarations and constraints.  For instance, suppose that
<tag compl="full" tei="yes">fsDecl type=Basic</tag> contains <tag compl="full" tei="yes">fDecl name=One</tag> and
<tag compl="full" tei="yes">fDecl name=Two</tag>, and that <tag compl="full" tei="yes">fsDecl type=Derived
baseType=Basic</tag> contains just <tag compl="full" tei="yes">fDecl name=Three</tag>.  Then
any instance of <tag compl="full" tei="yes">fs type=Derived</tag> may include all three
features.  This is because <tag compl="full" tei="yes">fsDecl type=Derived</tag> inherits the
two feature declarations from <tag compl="full" tei="yes">fsDecl type=Basic</tag> when it
specifies a <att tei="yes">baseType</att> of <code tei="yes" type="value">Basic</code>.</p><p>The following sample shows the overall structure of a complete FSD.
Note that as a stand-alone document it begins with a DOCTYPE declaration
which identifies the associated DTD.
 
 
<eg><![CDATA[  <!DOCTYPE teiFsd2 PUBLIC "-//TEI P3//DTD Auxiliary Document Type:  
        Feature System Declaration//EN"
       "teifsd2.dtd" >
  <teiFsd2>
     <teiHeader>
        <!-- The header is as for any TEI.2 document -->
     </teiHeader>
     <fsDecl type=SomeName>
        <fsDescr>Describes what this type of fs represents</>
        <fDecl name=featureOne>
           <!-- The declaration for featureOne -->
        </fDecl>
        <fDecl name=featureTwo>
           <!-- The declaration for featureTwo -->
        </fDecl>
        <fsConstraints>
           <!-- The feature structure constraints go here -->
        </fsConstraints>
     </fsDecl>
     <fsDecl type=AnotherType>
           <!-- Declare another type of feature structure -->
     </fsDecl>
  </teiFsd2>]]></eg></p><p>The formal definition of <gi tei="yes">teiFsd2</gi> and feature structure
declarations is as follows:
 
<dtdFrag id="DFDFSD2" n="Feature System Declaration" file="teifsd2"><tagDecl tagDoc="TEIFSD2"/><tagDecl tagDoc="FSDECL"/><tagDecl tagDoc="FSDESCR"/></dtdFrag></p></div2><div2 id="FDFD" name="Anthony" ref="Y"><head>Feature Declarations</head><p>Each feature is declared in an <gi tei="yes">fDecl</gi> element whose
<att tei="yes">name</att> attribute identifies the feature being declared; this
matches the <att tei="yes">name</att> attribute of the <gi tei="yes">f</gi> elements it
declares.  An <gi tei="yes">fDecl</gi> also has an <att tei="yes">org</att> attribute which
declares the organizing principle for the values of the <gi tei="yes">f</gi>
elements it declares.  That is, the value may be a <code tei="yes" type="value">unit</code> (a single value), a <code tei="yes" type="value">set</code>
(in which the order is not significant and there are no duplicates), a
<code tei="yes" type="value">bag</code> (in which the order is not significant but
duplicates are allowed), or a <code tei="yes" type="value">list</code> (in which the
order is significant).  (See definition of <att tei="yes">org</att> attribute of
<gi tei="yes">f</gi> in section <xref target="FSSS"/>.)  An <gi tei="yes">fDecl</gi> has three
parts:  an optional prose description (which should explain what the
feature and its values represent), an obligatory range specification
(which declares what values the feature is allowed to have), and an
optional default specification (which declares what default value should
be supplied when the named feature does not appear in an <gi tei="yes">fs</gi>).
A single unconditional default value may be specified, or multiple
conditional values.  If no default is specified, or if none of the
conditions is met, then the default value is <gi tei="yes">none</gi>; in other
words, the feature is not applicable (see section <xref target="FSBO"/> for
a discussion of the <gi tei="yes">none</gi> element).</p><p>The tags used in feature declarations are the following:
 
<tagList style="one-line"><tagDesc tagDoc="FDECL" atts="name org"/><tagDesc tagDoc="FDESCR"/><tagDesc tagDoc="VRANGE"/><tagDesc tagDoc="VDFT"/><tagDesc tagDoc="IF"/><tagDesc tagDoc="THEN"/></tagList></p><p>The logic for validating feature values and for matching the
conditions for supplying default values is based on the operation of
subsumption.  Subsumption is a standard operation in
feature-structure-based formalisms.  Informally, a feature structure
<emph>fs</emph> subsumes all feature structures that are at least as
informative as itself; that is, all feature structures that specify at
least as many features as <emph>fs</emph> with values at least as
informative as those given in <emph>fs</emph> (Pereira 1987:6; see also
Shieber 1986:14-16).
<note source="auth" place="foot" anchored="Y"><citation>Fernando C. N. Pereira, <title>Grammars and logics of partial
information</title>, SRI International Technical Note 420 (Menlo
Park, CA: SRI International, 1987)</citation>, and
<citation>Stuart Shieber, <title>An Introduction to Unification-based
Approaches to Grammar</title>, CSLI Lecture Notes 4 (Palo Alto,
CA: Center for the Study of Language and Information,
1986).</citation></note>
A more formal definition requires that we first define the notion of
<q>domain of a feature structure.</q> A feature structure can be viewed
as a partial function that maps features onto values; when viewed in
this way, the domain of a feature structure is the set of top-level
features it contains (that is, excluding features in embedded feature
structures).  We can now offer a more precise definition:
 
<q rend="display">     <emph>fs</emph> subsumes <emph>fs&amp;prime;</emph> if both are
     identical primitive values, or if the domain of <emph>fs</emph>
     is a subset of the domain of <emph>fs&amp;prime;</emph>, and for every
     feature <emph>f</emph> in the domain of <emph>fs</emph>, the
     value of <emph>f</emph> in <emph>fs</emph> subsumes the value
     of <emph>f</emph> in <emph>fs'</emph>.</q></p><p>Following the spirit of the informal definition above, we can extend
subsumption in a straightforward way to cover alternation, negation,
special primitive values, and the use of attributes in the SGML markup.
For instance, a <gi tei="yes">vAlt</gi> containing the value <code tei="yes" type="value">v</code> subsumes <code tei="yes" type="value">v</code>.  The negation
<code tei="yes" type="frag">REL=ne</code> of value <code tei="yes" type="value">v</code>
subsumes any value that is not <code tei="yes" type="value">v</code>.  The value
<gi tei="yes">unknown</gi> subsumes any value.  The value <gi tei="yes">any</gi> subsumes
any value that is in the range of a feature.  <tag compl="full" tei="yes">fs
type=X</tag><tag compl="full" tei="yes">/fs</tag> subsumes any feature structure with TYPE=X.
<tag compl="full" tei="yes">nbr rel=ge value=0</tag> subsumes any <gi tei="yes">nbr</gi> with value
greater than or equal to zero.</p><p>As an example of feature declarations, consider the following extract
from <title>Generalized Phrase Structure Grammar</title> by Gerald
Gazdar, Ewan Klein, Geoffrey Pullum, and Ivan Sag (Harvard University
Press, 1985).  In the appendix to their book (pages 245-247), they
propose a feature system for English of which this is just a sampling:
 
<eg>   feature    value range
 
   INV        {+, -}
   CONJ       {and, both, but, either, neither, nor, or, NIL}
   COMP       {for, that, whether, if, NIL}
   AGR        CAT
   PFORM      {to, by, for, ...}</eg>
<eg>   Feature specification defaults
 
   FSD 1:  [-INV]
   FSD 2:  ~[CONJ]
   FSD 9:  [INF, +SUBJ] --&gt; [COMP for]</eg></p><p>The INV feature, which encodes whether or not a sentence is inverted,
allows only the values plus (+) and minus (-).  If the feature is not
specified, then the default rule (FSD 1 above) says that a value of
minus is always assumed.  The feature declaration for this feature would
be encoded as follows:
 
<eg><![CDATA[        <fDecl name=INV>
           <fDescr>inverted sentence</fDescr>
           <vRange>
               <vAlt><plus><minus></vAlt></vRange>
           <vDefault>
               <minus></vDefault>
        </fDecl>]]></eg></p><p>The value range is specified as an alternation (more precisely, an
exclusive disjunction) of <gi tei="yes">plus</gi> and <gi tei="yes">minus</gi>.  That is,
the value must be one or the other, but not both or neither.</p><p>The CONJ feature indicates the surface form of the conjunction used
in a construction.  The ~ in the default rule (see FSD 2 above)
represents negation.  This means that by default the feature is not
applicable, in other words, no conjunction is taking place.  This
corresponds to the simple value <gi tei="yes">none</gi>; see section <xref target="FSBO"/>.  Note that this is distinct from the NIL value allowed in
the value range.  In their analysis, NIL means that the phenomenon of
conjunction is taking place but there is no explicit conjunction in the
surface form of the sentence.  The feature declaration for this feature
would be encoded as follows:
 
<eg><![CDATA[<fDecl name=CONJ>
   <fDescr>surface form of the conjunction</fDescr>
   <vRange>
      <vAlt>
         <sym value=and>
         <sym value=both>
         <sym value=but>
         <sym value=either>
         <sym value=neither>
         <sym value=nor>
         <sym value=or>
         <sym value=NIL>
      </vAlt></vRange>
   <vDefault>
      <none></vDefault>
</fDecl>]]></eg>
 
Note that the <gi tei="yes">vDefault</gi> is not strictly necessary in this case,
since <gi tei="yes">none</gi> is the value assumed in the absence of a default
specification.</p><p>The COMP feature indicates the surface form of the complementizer
used in a construction.  In value range, it is analogous to CONJ.
However, its default rule (see FSD 9 above) is conditional.  It says
that if the verb form is infinitival (the VFORM feature is not mentioned
in the rule since it is the only feature that can take INF as a value),
and the construction has a subject, then a <cited>for</cited> complement
must be used.  For instance, to make John the subject of the infinitive
in <cited>It is necessary to go,</cited> a <cited>for</cited> complement
must be used; that is, <cited>It is necessary for John to go.</cited>
The feature declaration for this feature would be encoded as follows:
 
<eg><![CDATA[<fDecl name=COMP>
   <fDescr>surface form of the complementizer</fDescr>
   <vRange>
      <vAlt>
         <sym value=for>
         <sym value=that>
         <sym value=whether>
         <sym value=if>
         <sym value=NIL>
      </vAlt></vRange>
   <vDefault>
      <if><fs><f name=VFORM><sym value=INF></f>
              <f name=SUBJ><plus></f></fs>
      <then><sym value=for></if>
      </vDefault>
</fDecl>]]></eg></p><p>The AGR feature stores the features relevant to subject-verb
agreement.  Gazdar et al. specify the range of this feature as CAT.
This means that the value is a <term rend="noindex">category</term>, which
is their term for a feature structure.  This is actually too weak a
statement.  Not just any feature structure is allowable here; it must be
a feature structure for agreement (which is defined in the complete
example at the end of the chapter to contain the features of person and
number).  The following feature declaration encodes this constraint on
the value range:
 
<eg><![CDATA[<fDecl name=AGR>
   <fDescr>agreement for person and number</fDescr>
   <vRange><fs type=Agreement></fs></vRange>
</fDecl>]]></eg>
 
That is, the value must be a feature structure of type <code tei="yes" type="value">Agreement</code>.  The complete example at the end of this
chapter includes the <tag compl="full" tei="yes">fsDecl type=Agreement</tag> which includes
<tag compl="full" tei="yes">fDecl name=PERS</tag> and <tag compl="full" tei="yes">fDecl name=NUM</tag>.</p><p>The PFORM feature indicates the surface form of the preposition used
in a construction.  Since PFORM is specified above as an open set,
<gi tei="yes">str</gi> is used in the range specification below rather than
<gi tei="yes">sym</gi>.
 
<eg><![CDATA[<fDecl name=PFORM>
   <fDescr>word form of a preposition</fDescr>
   <vRange><str rel=ne></str></vRange>
</fDecl>]]></eg>
 
This example makes use of a negation.  <tag compl="full" tei="yes">str
rel=ne</tag><tag compl="full" tei="yes">/str</tag> subsumes any string that is not the empty
string.</p><p>The formal definition for feature declarations follows.  Note that
the class <ident tei="yes" type="class">featureVal</ident> includes all possible
single feature values, including a <gi tei="yes">vAlt</gi>.
 
<dtdFrag id="DFDX" n="Feature definitions"><tagDecl tagDoc="FDECL"/><tagDecl tagDoc="FDESCR"/><tagDecl tagDoc="VRANGE"/><tagDecl tagDoc="VDFT"/><tagDecl tagDoc="IF"/><tagDecl tagDoc="THEN"/></dtdFrag></p></div2><div2 id="FDFS" name="Anthony" ref="Y"><head>Feature Structure Constraints</head><p>Ensuring the validity of feature structures may require much more
than simply specifying the range of allowed values for each feature.
There may be constraints on the co-occurrence of one feature value with
the value of another feature in the same feature structure or in an
embedded feature structure.</p><p>Such constraints on valid feature structures are expressed as a
series of conditional and biconditional tests in the
<gi tei="yes">fsConstraints</gi> part of an <gi tei="yes">fsDecl</gi>.  A particular feature
structure is valid only if it meets all the constraints.  The
<gi tei="yes">cond</gi> element encodes the conventional if-then conditional of
boolean logic which succeeds when both the antecedent and consequent are
true, or whenever the antecedent is false.  The <gi tei="yes">bicond</gi> element
encodes the biconditional (if and only if) operation of boolean logic.
It succeeds only when both antecedent and consequent are true, or both
are false.  In feature structure constraints the antecedent and
consequent are expressed as feature structures; they are considered true
if they <term rend="noindex">subsume</term><indexed level1="subsumption" level2="of feature structures"/>
(see section <xref target="FDFD"/>) the target feature structure.  The
following elements make up the <gi tei="yes">fsConstraints</gi> part of an FSD:
 
<tagList style="one-line"><tagDesc tagDoc="FSCONSTR"/><tagDesc tagDoc="COND"/><tagDesc tagDoc="BICOND"/><tagDesc tagDoc="THEN"/><tagDesc tagDoc="IFF"/></tagList></p><p>For an example of feature structure constraints, consider the
following <soCalled>feature co-occurrence restrictions</soCalled>
extracted from the feature system for English proposed by Gazdar, Klein,
Pullum, and Sag (1985:246-247):
 
<list type="simple"><item>FCR 1:  [+INV] &rarr; [+AUX, FIN]</item><item>FCR 7:  [BAR 0] &amp;equiv; [N] &amp; [V] &amp; [SUBCAT]</item><item>FCR 8:  [BAR 1] &rarr; ~[SUBCAT]</item></list></p><p>The first constraint says that if a construction is inverted, it must
also have an auxiliary and a finite verb form.  That is,
 
<eg><![CDATA[<cond><fs><f name=INV><plus></f></fs>
      <then>
      <fs>
         <f name=AUX><plus></f>
         <f name=VFORM><sym value=FIN></f>
      </fs>
</cond>]]></eg></p><p>The second constraint says that if a construction has a BAR value of
zero (i.e., it is a sentence), then it must have a value for the
features N, V, and SUBCAT.  By the same token, because it is a
biconditional, if it has values for N, V, and SUBCAT, it must have
BAR=0.  That is,
 
<eg><![CDATA[<bicond>
   <fs><f name=BAR><sym value=0></f></fs>
   <iff>
   <fs>
      <f name=N><any></f>
      <f name=V><any></f>
      <f name=SUBCAT><any></f>
   </fs>
</bicond>]]></eg></p><p>The final constraint says that if a construction has a BAR value of 1
(i.e., it is a phrase), then the SUBCAT feature is irrelevant (~).
This is not biconditional, since there are other instances under which
the SUBCAT feature is irrelevant.  That is,
 
<eg><![CDATA[<cond><fs><f name=BAR><sym value=1></f></fs>
      <then>
      <fs><f name=SUBCAT><none></f></fs>
</cond>]]></eg></p><p>The DTD fragment for feature structure constraints is as follows.
Note that <gi tei="yes">cond</gi> and <gi tei="yes">bicond</gi> use the empty tags
<gi tei="yes">then</gi> and <gi tei="yes">iff</gi>, respectively, to separate the antecedent
and consequent.  These are primarily for the sake of enhancing human
readability.
 
<dtdFrag id="DFD2" n="Feature structure constraints"><tagDecl tagDoc="FSCONSTR"/><tagDecl tagDoc="COND"/><tagDecl tagDoc="BICOND"/><tagDecl tagDoc="IFF"/></dtdFrag></p></div2><div2 id="FDEG" name="Anthony" ref="Y"><head>A Complete Example</head><p>To summarize this chapter, the complete FSD for the example that has
run through the chapter is reproduced below:
 
<eg><![CDATA[<!DOCTYPE teiFsd2 SYSTEM "teifsd2.dtd">
<teiFsd2>
<teiHeader>
<fileDesc>
<titleStmt>
   <title>A sample FSD based on an extract from Gazdar
          et al.'s GPSG feature system for English</title>
   <resp>
      <role>encoded by</role>
      <name>Gary F. Simons</name>
   </resp>
</titleStmt>
<publicationStmt>
This sample was first encoded by Gary F. Simons (Summer
Institute of Linguistics, Dallas, TX) on January 28, 1991.
Revised April 8, 1993 to match the specification of FSDs
in version P2 of the TEI Guidelines.
</publicationStmt>
<sourceDesc><p>
This sample FSD does not describe a complete feature
system.  It is based on extracts from the feature system
for English presented in the appendix (pages 245-247) of
Generalized Phrase Structure Grammar, by Gazdar, Klein,
Pullum, and Sag (Harvard University Press, 1985).
</sourceDesc>
</fileDesc>
</teiHeader>
<!-- ************************************************** -->
<fsDecl type=GPSG>
   <fsDescr>Encodes a feature structure for the GPSG analysis
     of English (after Gazdar, Klein, Pullum, and Sag)</fsDescr>
   <fDecl name=INV>
      <fDescr>inverted sentence</fDescr>
      <vRange>
          <vAlt><plus><minus></vAlt></vRange>
      <vDefault>
          <minus></vDefault>
   </fDecl>
   <fDecl name=CONJ>
      <fDescr>surface form of the conjunction</fDescr>
      <vRange>
          <vAlt>
              <sym value=and><sym value=both>
              <sym value=but><sym value=either>
              <sym value=neither><sym value=nor>
              <sym value=or><sym value=NIL>
          </vAlt></vRange>
      <vDefault>
          <none></vDefault>
      </fDecl>
   <fDecl name=COMP>
      <fDescr>surface form of the complementizer</fDescr>
      <vRange>
          <vAlt>
              <sym value=for><sym value=that><sym value=whether>
              <sym value=if><sym value=NIL>
          </vAlt></vRange>
      <vDefault>
          <if><fs><f name=VFORM><sym value=INF></f>
                  <f name=SUBJ><plus></f></fs>
           <then><sym value=for></if>
          </vDefault>
      </fDecl>
   <fDecl name=AGR>
      <fDescr>agreement for person and number</fDescr>
      <vRange><fs type=Agreement></fs></vRange>
      </fDecl>
   <fDecl name=PFORM>
      <fDescr>word form of a preposition</fDescr>
      <vRange><str rel=ne></str></vRange>
      </fDecl>
   <!-- The complete analysis includes additional features -->
   <fsConstraints>
      <cond><fs><f name=INV><plus></f></fs>
         <then>
            <fs>
               <f name=AUX><plus></f>
               <f name=VFORM><sym value=FIN></f>
            </fs></cond>
      <bicond><fs><f name=BAR><sym value=0></f></fs>
         <iff>
            <fs>
               <f name=N><any></f>
               <f name=V><any></f>
               <f name=SUBCAT><any></f>
            </fs></bicond>
      <cond><fs><f name=BAR><sym value=1></f></fs>
         <then>
            <fs><f name=SUBCAT><none></f></fs>
            </cond>
   </fsConstraints>
</fsDecl>
<!-- ************************************************** -->
<fsDecl type=Agreement>
   <fsDescr>This type of feature structure encodes the features
      for subject-verb agreement in English</fsDescr>
   <fDecl name=PERS>
      <fDescr>person (first, second, or third)</fDescr>
      <vRange><vAlt><sym value=1><sym value=2><sym value=3>
         </vAlt></vRange>
   </fDecl>
   <fDecl name=NUM>
      <fDescr>number (singular or plural)</fDescr>
      <vRange><vAlt><sym value=sg><sym value=pl>
         </vAlt></vRange>
   </fDecl>
</fsDecl>
</teiFsd2>]]></eg></p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2fd.odd ??><!-- 26 Feature Struc. Decl. --><?tei:SOF p2td.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2td.odd,v $
# Revision 1.10  1994/04/08  00:02:57  msmcq
# change apropos of validating DTD
#
# Revision 1.9  1994/03/27  21:48:38  msmcq
# Correction of typos found by EM, DB.
#
# Revision 1.8  1994/03/21  14:11:59  lou
# second mass typo clearup
#
# Revision 1.6  1994/02/12  21:37:58  msmcq
# strip ^Z
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : embed tei keywords file                 --><!-- 94-03-27 : MSM : typos from WWP and DB.                  --><!-- 9 jan 94: corrected spelling of tagDoc etc.              --><!-- 28 dec 93: LB : add decl for desc                        --><!-- 93-06-05 : MSM : for eg read tdeg (temp fix)             --><!-- 9-11 apr 93 : LB drafted                                 --><div1 id="TD" n="27" name="Faisal" ref="Y"><head>Tag Set Documentation</head><p>This chapter describes an auxiliary DTD which may be used for the
documentation of new elements, element classes and entities.  It is
primarily intended for use by those wishing to extend or modify the
content of these Guidelines in a conformant manner, as described in
chapters <xref target="MD"/> and <xref target="CF"/>; it may however be of use
for the documentation of any SGML or SGML-like encoding scheme.  The
elements described here are those used to document the TEI scheme
itself, in part VII of the current document.
 </p><p>Three distinct elements are used to document a tag set, the contents
of each of which is described in more detail in the appropriate section
of this chapter.
 
<tagList style="one-line"><tagDesc tagDoc="TAGDOC" atts="usage"/><tagDesc tagDoc="CLASSDOC"/><tagDesc tagDoc="ENTDOC"/></tagList>
 <!-- DB suggests a fileDoc, for P4. (msm)                     -->
 </p><p>In addition to these documentary elements, the following phrase-level
elements may be found useful for marking up occurrences of element names
etc. within the body of running text.
 
<tagList style="one-line"><tagDesc tagDoc="GI" atts="TEI"/><tagDesc tagDoc="ATT" atts="TEI"/><tagDesc tagDoc="VAL"/><tagDesc tagDoc="TAG"/></tagList><!-- on VAL, see remarks in tagDoc -->
 
These four elements are included in the phrase-level elements available
to any document using the auxiliary tag set defined in this chapter; to
make them available to documents using other DTDs, an appropriate
parameter entity should be defined.
 <!-- but I dont have time to tell you how just now -->
 </p><p>As an example of the recommended use of these elements, we quote from
an imaginary TEI working paper:
 <!-- 'n imaginary' restored (msm)                             -->
 
<eg><![CDATA[<p>The <gi>gi</gi> element is used to tag element names when
they appear in the text; the <gi>tag</gi> element however is
used to show how a tag as such might appear. So one might
talk of an occurrence of the <gi>blort</gi> element which had
been tagged <tag>blort type='runcible'</tag>. The <att>type</att>
attribute may take any name token as value; the default value is
<val>spqr</val>, in memory of its creator.]]></eg>
 </p><p>These elements and their components make up the auxiliary DTD for tag
documentation, which is contained in the file <ident tei="yes" type="file">teitsd2.dtd</ident>.  This file has the following overall
structure:
 
<dtdFrag id="DTD" n="File teitsd2.dtd:  Auxiliary DTD for Tag Set Documentation" file="teitsd2"><commDecl>Text Encoding Initiative:
Guidelines for Electronic Text Encoding and Interchange.
Document TEI P3, 1994.</commDecl><commDecl>Copyright (c) 1994 ACH, ACL, ALLC.
Permission to copy in any form is granted,
provided this notice is included in all copies.</commDecl><commDecl>These materials may not be altered;
modifications to these DTDs should be performed as specified
in the Guidelines in chapter "Modifying the TEI DTD."</commDecl><commDecl>These materials subject to revision.
Current versions are available from the Text Encoding Initiative.</commDecl><commDecl>Embed entities for TEI generic identifiers.</commDecl><entDecl entDoc="TEIGIS"/><peRef n="TEI.elementNames"/><commDecl>Define entities for TEI keywords.</commDecl><entDecl entDoc="TEIKW"/><peRef n="TEI.keywords.ent"/><commDecl>Define element classes for content models, shared
attributes for element classes, and global attributes.  (This all
happens within the file TEIclas2.ent.)</commDecl><entDecl entDoc="TEIECGA"/><peRef n="TEI.elementClasses"/><commDecl>Embed the core tag set</commDecl><entDecl entDoc="TEICORE"/><peRef n="TEI.core.dtd"/><commDecl>Define the top-level element for this DTD</commDecl><tagDecl tagDoc="TSD"/><commDecl>Define some additions for the phrase level tags</commDecl><tagDecl tagDoc="GI"/><tagDecl tagDoc="TAG"/><tagDecl tagDoc="ATT"/><tagDecl tagDoc="VAL"/><commDecl>Finally we define the elements specific to this DTD</commDecl><dtdRef dtdFrag="DTDTAG"/><dtdRef dtdFrag="DTDATT"/><dtdRef dtdFrag="DTDCLA"/><dtdRef dtdFrag="DTDENT"/></dtdFrag>
 
 </p><div2 id="TDTAG" name="Anthony" ref="Y"><head>The TagDoc Documentation Element</head><p>The <gi tei="yes">tagDoc</gi> element is used to document an element type,
together with its associated attributes.  A completely specified
<gi tei="yes">tagDoc</gi> may comprise all of the following components in the
order specified:
 
<tagList style="one-line"><tagDesc tagDoc="RS"/><tagDesc tagDoc="GI"/><tagDesc tagDoc="DESC"/><tagDesc tagDoc="ATTLIST"/><tagDesc tagDoc="EXEMPLUM"/><tagDesc tagDoc="TDEG"/><tagDesc tagDoc="REMARKS"/><tagDesc tagDoc="PART"/><tagDesc tagDoc="CLASSES"/><tagDesc tagDoc="FILES"/><tagDesc tagDoc="DATADESC"/><tagDesc tagDoc="PARENTS"/><tagDesc tagDoc="CHILDREN"/><tagDesc tagDoc="ELEMDECL"/><tagDesc tagDoc="ATTLDECL"/><tagDesc tagDoc="PTR"/><tagDesc tagDoc="EQUIV"/></tagList>
 </p><p>As the content model for <gi tei="yes">tagDoc</gi> makes clear, only the
<gi tei="yes">gi</gi>, <gi tei="yes">desc</gi>, <gi tei="yes">exemplum</gi>, <gi tei="yes">dataDesc</gi>,
<gi tei="yes">parents</gi>, <gi tei="yes">children</gi> and <gi tei="yes">elemDecl</gi> elements are
mandatory components.  For elements bearing attributes, the
<gi tei="yes">attList</gi> and <gi tei="yes">attlDecl</gi> components are also required for
TEI conformance.  For compatibility with the TEI system, use of the
<gi tei="yes">classes</gi> and <gi tei="yes">files</gi> elements is strongly recommended.
The only components of the <gi tei="yes">tagDoc</gi> element which can appear more
than once are the <gi tei="yes">exemplum</gi>, <gi tei="yes">ptr</gi> and <gi tei="yes">equiv</gi>
elements.  The order of components may not be changed.
 <!-- <p>Several examples of complete <gi>tagDoc</gi>          --><!-- elements are provided in section <xref target=XT>.       -->
 </p><p>The <gi tei="yes">tagDoc</gi> and its constituents are defined as follows:
 
<dtdFrag id="DTDTAG" n="The TagDoc element"><tagDecl tagDoc="TAGDOC"/><commDecl>RS and PTR are defined in the core</commDecl><commDecl>GI is defined above </commDecl><tagDecl tagDoc="DESC"/><tagDecl tagDoc="ATTLIST"/><tagDecl tagDoc="EXEMPLUM"/><tagDecl tagDoc="TDEG"/><tagDecl tagDoc="REMARKS"/><tagDecl tagDoc="PART"/><tagDecl tagDoc="CLASSES"/><tagDecl tagDoc="FILES"/><tagDecl tagDoc="DATADESC"/><tagDecl tagDoc="PARENTS"/><tagDecl tagDoc="CHILDREN"/><tagDecl tagDoc="ELEMDECL"/><tagDecl tagDoc="ATTLDECL"/><tagDecl tagDoc="EQUIV"/></dtdFrag>
 </p><div3 id="TDATT" name="subsection" ref="Y"><head>The AttList Documentation Element</head><p>The <gi tei="yes">attList</gi> element is used to document information about a
collection of attributes, either within a <gi tei="yes">tagDoc</gi>, or within a
<gi tei="yes">classDoc</gi>.  It consists of a series of <gi tei="yes">attDef</gi> elements,
each documenting a single attribute and each using an appropriate
selection from the following elements:
 
<tagList style="one-line"><tagDesc tagDoc="ATTDEF" atts="usage"/><tagDesc tagDoc="ATTNAME"/><tagDesc tagDoc="RS"/><tagDesc tagDoc="DESC"/><tagDesc tagDoc="DATATYPE"/><tagDesc tagDoc="VALLIST" atts="type"/><tagDesc tagDoc="VAL"/><tagDesc tagDoc="VALDESC"/><tagDesc tagDoc="DEFAULT"/><tagDesc tagDoc="TDEG"/><tagDesc tagDoc="REMARKS"/><tagDesc tagDoc="EQUIV"/></tagList>
 </p><p>It will be noted that several of these elements are used identically
to document both elements and attributes.  Specific to attributes are
<gi tei="yes">dataType</gi>, <gi tei="yes">valList</gi>, <gi tei="yes">valDesc</gi>, <gi tei="yes">val</gi> and
<gi tei="yes">default</gi>.  For any attribute documented in this way, either a
<gi tei="yes">valList</gi> or a <gi tei="yes">valDesc</gi> must be supplied to specify the
range of permitted values for an attribute.  A <gi tei="yes">valList</gi> should
be used if the intended set of values can be enumerated; a
<gi tei="yes">valDesc</gi> if it cannot.  A legal <gi tei="yes">attDef</gi> specification
must contain an <gi tei="yes">attName</gi>, a <gi tei="yes">desc</gi>, a <gi tei="yes">datatype</gi>,
either a <gi tei="yes">valList</gi> or a <gi tei="yes">valDesc</gi>, and a default; the
other elements listed above are all optional.
 </p><p>The <gi tei="yes">attList</gi> within a <gi tei="yes">tagDoc</gi> is used to specify only
the attributes which are specific to that particular element.
Attributes which are shared by other elements, or by all elements,
should be documented by an <gi tei="yes">attList</gi> contained within a
<gi tei="yes">classDoc</gi> element, as described in section <xref target="TDCLA"/>
below.
 </p><p>The following <gi tei="yes">attList</gi> demonstrates some of the
possibilities; for more detailed examples, consult the tagged version of
the reference material in these Guidelines.
 <!-- replace this example if we change the definition of gloss list  -->
<eg><![CDATA[ 
<attDef usage=opt>
<attName>type
<desc>describes the form of the list.
<datatype>CDATA
<valList type=semi>
    <val>ordered<desc>list items are numbered or lettered.
    <val>bulleted<desc>list items are marked with a
       <soCalled>bullet</soCalled> or other typographic device.
    <val>simple<desc>list items are not numbered or bulleted.
    <val>gloss<desc>each list item glosses some term or
      concept, which is given by a <gi>label</gi> element preceding
      the list item.
</valList>
<default>simple
<remarks><p>The formal syntax of the element declarations allows
<gi>label</gi> tags to be omitted from lists tagged <tag>list
type=gloss</tag>; this is however a semantic error.
</attDef>
 ]]></eg>
 </p><p>Those elements from the above list which are unique to attributes are
declared as follows:
 
<dtdFrag id="DTDATT" n="Attribute documentation"><tagDecl tagDoc="ATTDEF"/><tagDecl tagDoc="ATTNAME"/><tagDecl tagDoc="DATATYPE"/><tagDecl tagDoc="VALLIST"/><tagDecl tagDoc="VALDESC"/><tagDecl tagDoc="DEFAULT"/></dtdFrag>
 </p></div3></div2><div2 id="TDCLA" name="Anthony" ref="Y"><head>Element Classes</head><p>The element <gi tei="yes">classDoc</gi> is used to document an <term>element
class</term>, as defined in section <xref target="STEC"/>.  It has the
following components:
 
<tagList style="one-line"><tagDesc tagDoc="CLASSDOC" atts="type"/><tagDesc tagDoc="CLASS"/><tagDesc tagDoc="RS"/><tagDesc tagDoc="DESC"/><tagDesc tagDoc="ATTLIST"/><tagDesc tagDoc="REMARKS"/><tagDesc tagDoc="PART"/><tagDesc tagDoc="CLASSES"/><tagDesc tagDoc="PTR"/><tagDesc tagDoc="EQUIV"/></tagList>
 
Of these elements, only the <gi tei="yes">class</gi> and <gi tei="yes">desc</gi> elements
are required
 <!-- tho the content model for ODD requires others -->
 
components.  If present, the other elements must be given in the order
specified, and only <gi tei="yes">ptr</gi> and <gi tei="yes">equiv</gi> may be repeated.
 </p><p>The attribute <att tei="yes">type</att> is used to distinguish between
<soCalled>model</soCalled> and <soCalled>attribute</soCalled> classes;
for the former, a <gi tei="yes">classDoc</gi> simply exists so that members of the
class it documents may point to it (by specifying the value of its
<att tei="yes">id</att> attribute among the values specified by the
<att tei="yes">names</att> attribute of their <gi tei="yes">classes</gi> component); for the
latter, the <gi tei="yes">classDoc</gi> additionally contains an <gi tei="yes">attList</gi>
which specifies the attributes shared by the members of the class.  A
class may perform both functions, of course.
 </p><p>Where a class inherits properties or attributes from some other
class, the <gi tei="yes">classes</gi> element may be used to indicate this fact.
Membership of an attribute class can be inherited by any class, but
model-only classes may not include attribute-only classes amongst their
members.  For further discussion of the TEI class system, see section<xref target="STEC"/>
.
 <!-- <p>For examples of attribute classes, please refer to    --><!-- chapter <xref target=XT>.                                -->
 </p><p>The <gi tei="yes">classDoc</gi> element and the elements unique to it are
declared as follows:
 
<dtdFrag id="DTDCLA" n="Element classes"><tagDecl tagDoc="CLASSDOC"/><tagDecl tagDoc="CLASS"/><commDecl>all other constituents are defined above</commDecl></dtdFrag>
 </p></div2><div2 id="TDENT" name="Anthony" ref="Y"><head>Entity Documentation
 </head><p>The <gi tei="yes">entDoc</gi> element is used to document any other entity not
otherwise documented by the elements described in this chapter.  Its
chief uses are to provide systematic documentation for parameter
entities used within TEI DTD fragments (for example, those used to
enable different components of the TEI DTD, or to describe common
content models), but it may be used for any purpose.  It has the
following components:
 
<tagList style="one-line"><tagDesc tagDoc="ENTDOC" atts="type"/><tagDesc tagDoc="ENTNAME"/><tagDesc tagDoc="RS"/><tagDesc tagDoc="DESC"/><tagDesc tagDoc="REMARKS"/><tagDesc tagDoc="STRING"/><tagDesc tagDoc="PTR"/><tagDesc tagDoc="EQUIV"/></tagList>
 
Of these, only <gi tei="yes">entName</gi>, <gi tei="yes">desc</gi> and <gi tei="yes">string</gi> are
required components.  If present, the other elements must be given in
the order specified, and only <gi tei="yes">ptr</gi> and <gi tei="yes">equiv</gi> may be
repeated.
 <!-- <p>For examples, please refer to chapters <xref          --><!-- target=XT> and <xref target=ST>.                         -->
 </p><p>The <gi tei="yes">entDoc</gi> element and the elements unique to it are
declared as follows:
 
<dtdFrag id="DTDENT" n="Entity Documentation"><tagDecl tagDoc="ENTDOC"/><tagDecl tagDoc="ENTNAME"/><tagDecl tagDoc="STRING"/><commDecl>All other constituents are defined above</commDecl></dtdFrag>
 <?tei:EOF p2td.odd ??>
             <!-- 27 Tag Set Declaration -->
 </p></div2></div1></div0><div0 n="6" name="Part" ref="Y"><head>Technical Topics</head><?tei:SOF p2cf.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2cf.odd,v $
    * Revision 1.9  1998/01/31 19:14:05  tei
    * finish note on derived DTDs.
    *
    * Revision 1.8  1998/01/31 18:27:01  tei
    * fix log keyword
    * begin changes to allow derived dtds.
    *
    * Revision 1.7  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.6  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    *--><!-- TEI Doc. No:  ml w43                                       --><!-- Title:        TEI Conformance                              --><!-- Drafted:      msm, 22 May 1991                             --><!-- ********************************************************** --><!-- Revision History (add lines at top)                        --><!-- 4 Jan 98 : LB : remove reference to tei1 --><!-- 94-04-07 : MSM : normalize caps in headings              --><!-- 94-04-07 : MSM : Added RCS id                            --><!-- 93-06-02 : WP : Spellchecked, made minor corrections.    --><!-- 93-04-12 : MSM : cosmetic changes                        --><!-- Date      Who    What                                      --><!-- 10 Apr 93 LB: ODDified from                                --><!-- 30 May 91 CMSMcQ minor corrections                         --><!-- 29 May 91 CMSMcQ finished major revision                   --><!-- 28 May 91 CMSMcQ major cuts and reorganization (ver 2)     --><!-- 22 May 91 CMSMcQ made file                                 --><div1 id="CF" n="28" name="Faisal" ref="Y"><head>Conformance</head><p>The notion of <term>TEI conformance</term>
is intended as an aid in describing the
format and contents of a particular document or set of documents.
These concepts are expected to be useful in:
<list type="simple"><item>agreements for the interchange of documents among researchers</item><item>agreements for the deposit of texts in archives and their
distribution from archives</item><item>describing the documents to be produced by or for a given project</item><item>defining the classes of documents accepted or rejected by a given
piece of software</item></list></p><p>This chapter describes the areas in which these terms are defined and
specifies their meaning.  It also proposes other terms for related
concepts and points out some dangers in the careless use or application
of these terms.</p><div2 id="CFDEFNS" name="Anthony" ref="Y"><head>Definitions of Terms</head><p>The terms described here should be considered technical terms for
users and implementors of the TEI Guidelines and should be used only in
the senses given and with the usages described.</p><div3 id="CFDOC" name="subsection" ref="Y"><head>TEI-Conformant Document</head><p>A document is <term>TEI conformant</term> if it is
either in <term>TEI local processing format</term> or in <term>TEI
interchange format</term>.  A full description of the document should
specify which format it is in.</p><p>The term <term>TEI conformance</term> does not apply to software:
programs can be usefully described as <term>accepting</term> or
<term>validating</term> TEI-conformant documents or some subset of
TEI-conformant documents, but the TEI defines no required processing
model against which software could be measured.  Programs are thus not
themselves conformant or non-conformant and should not be so described.</p></div3><div3 id="CFLOCAL" name="subsection" ref="Y"><head>TEI Local Processing Format</head><p>A document is in <term>TEI local processing format</term> if
<list type="simple"><item>it is a conforming SGML document with a legal SGML declaration;</item><item>it uses the document type declarations provided by the TEI, either
without modifications or with all modifications effected by inclusion
in the DTD subset as described in section <xref target="DTDMOD"/>;</item><item>all modifications to meaning or use of defined tags, and all new
tags, are documented in TEI Tag Set Declarations which accompany the
document, as defined in chapter <xref target="TD"/>;<!-- < fn > The components of a tag set declaration are at    --><!-- present defined only in document TEI ED W5; they         --><!-- should receive a fuller definition and documentation     --><!-- as soon as possible.  The ultimate structure of the      --><!-- tag set declaration should agree with the structures     --><!-- used in the TEI's own reference manual for the TEI       --><!-- scheme.                                                  --><!-- < /fn >                                                  --></item><item>it includes, in the TEI header, all the elements required by the
TEI declarations for the TEI header;</item><item>it contains no markup other than SGML or declared notations for
graphics, tables, figures, etc.  That is, unless a declared notation is
in use, the semantics of any content character in the document are
exhausted by its identity as a graphic character.</item></list></p><p>A TEI-local-processing-format document may be described as requiring
<term>DTD extensions</term> if it modifies the TEI-supplied DTDs or
SGML prolog in any of the ways described  under<xref target="DTDMOD"/>
.</p><p>The following terms are synonymous:  <term>document in TEI local
processing format</term>, <term>TEI local-processing document</term>,
and <term>TEI local-processing-conformant document</term>.</p></div3><div3 id="CFINT" name="subsection" ref="Y"><head>TEI Interchange Format</head><p>A document is in <term>TEI interchange format</term> if it conforms
to the TEI local-processing format and if further:
<list type="simple"><item>its SGML declaration is either the predefined SGML
declaration for TEI interchange documents or an SGML declaration
which differs from it only in ways allowed by section <xref target="SGMLMOD"/>;</item><item>it makes no use of any of the following SGML constructs:
<list type="simple"><item>short references</item><item>the RANK feature</item><item>omission of generic identifiers in start- and end-tags
<note source="auth" place="display" anchored="Y">This is one of several abbreviations allowed by the SHORTTAG
feature; the others (omission of attribute names under certain
circumstances and omission of non-required attribute values) are allowed.</note></item><item>keywords other than INCLUDE, IGNORE, and CDATA on a marked
section</item></list></item><item>it includes no SUBDOC subordinate document by means of an entity
reference embedded directly within content data (SUBDOCs must be
included by giving the entity reference as the value of an attribute);<!-- kill this one?: I dont understand it (LB) --></item><item>it does not provide different definitions for the same entity in
different document types.</item></list></p><p>A TEI-interchange-format document may be described as requiring
<term>DTD extensions</term> if its DTD is modified in any of the ways
described in section <xref target="DTDMOD"/>.</p><p>The following terms are synonymous: <term>document in TEI
interchange format</term>, <term>TEI interchange document</term>, and
<term>TEI interchange-conformant document</term>.</p></div3><div3 id="CFEX" name="subsection" ref="Y"><head>TEI Packed Interchange format</head><p>A document is in TEI packed interchange format with a given
<term>transmission character set</term> and a given
<term>transmission entity set</term> if all of the following are true:
<list type="simple"><item>all separate entities in the document are packed into a single
entity (file) in a manner conforming to ISO 9069 (SDIF) or to some
other TEI-authorized form;</item><item>all characters occurring in SGML names (generic identifiers and
attribute names) occur within the transmission character set;<!-- .  (If this is not true, the SGML names must be modified --><!-- so as to make it true.) --></item><item>all characters in the document content and attribute values either
occur within the transmission character set or are represented by an
appropriate entity reference using an entity name included in the
transmission entity set;</item><item>the transmission character and entity sets are named in the header
of the packed file and in any  accompanying paper documentation.</item></list>
Any
pre-transmission processing required to convert a document to meet the
above requirements for conformance to the  TEI-interchange-format  is
called <term>packing</term>.</p><p>With prior agreement between parties to an exchange, interchange
documents may use character code set switching as defined in ISO 2022, its
national analogues, or successor standards.</p><p>A full description of a document in TEI packed interchange format
<emph>must</emph> specify the transmission character set and the
transmission entity set used in the document.</p></div3><div3 id="CFREC" name="subsection" ref="Y"><head>TEI Recommended Practice</head><p>A document follows <term>TEI recommended practice</term> if:
<list type="simple"><item>it is a TEI-conformant document;</item><item>wherever the guidelines say to prefer one encoding practice to
another, the preferred practice is used;</item><item>all textual features which the guidelines recommend be captured
are in fact encoded.<!-- since there are none: follow DD's proposal to drop following --><!-- <item>no textual features which the guidelines recommend not --><!--     be captured are in fact encoded --></item></list></p></div3><div3 id="CFMOD" name="subsection" ref="Y"><head>TEI Abstract Model</head><p>A document follows the <term>TEI abstract model</term> if it tags
the features specified in the TEI documentation and documentation, and
their structural interrelations agree with those specified in the TEI DTDs.
 <!-- end of CF ? --></p></div3></div2><div2 id="SGMLMOD" name="Anthony" ref="Y"><head>Modifications to TEI SGML Declaration</head><p>The SGML declaration for TEI interchange documents may differ
from that provided in TEI documentation in these ways:
<list type="simple"><item>the CHARSET clause must be used to define the transmission character set
(possibly in connection with the SHUNCHAR specification in the SYNTAX clause);</item><item>the CAPACITY clause may  be used to raise (but not lower) capacities;</item><item>the SYNTAX clause may be used to define the SGML syntax used in
      the document.  Notably:
<list type="simple"><item>the SHUNCHAR specification within the SYNTAX clause may be used to
restrict the transmission character set;</item><item>the BASESET and DESCSET specifications within the SYNTAX
clause must be used to describe the transmission character set;</item><item>the DELIM and NAMES specifications may be used to modify the SGML
syntax.</item></list></item><item>in the FEATURES clause, CONCUR may be set to NO if concurrent
markup is not used in the document.</item></list></p><p>The following portions of the SGML declaration may not be modified in
TEI interchange documents:
<list type="simple"><item>the CAPACITY and QUANTITY values may be increased but not decreased;</item><item>the SCOPE clause may not be changed;</item><item>no new FEATURES may be turned on.</item></list></p><p>The SGML declaration for TEI-local-format documents may be modified
without restriction.  Some recommendations for usage are made in
document TEI P1, but these recommendations are not normative.</p></div2><div2 id="DTDMOD" name="Anthony" ref="Y"><head>Modifications to TEI Document Type Declarations</head><p>A TEI-conformant document (whether for local processing or for
interchange) may make any change to the TEI-supplied document type
declarations which is allowed by SGML and the controlling SGML
declaration.  All such changes should be made (or at least it must
be possible to make them) within the SGML DTD subset, by defining TEI
DTD modifications files as described in chapter <xref target="MD"/>,
and embedding the modification files within the DTD subset of a
document whose document type declaration refers to the unmodified TEI
main DTD, as in the following fragment:<!--*
In all TEI-conformant documents, the document type name must be
<gi>tei</gi>, followed by a digit indicating the currently released
version number for the TEI guidelines in use.  The associated public
or system identifier(s) should refer to a file containing the
unmodified TEI main DTD fragment, as in the following example:
*-->
<eg><![CDATA[<!DOCTYPE tei.2 PUBLIC "-//TEI P3//DTD Main Document Type//EN"
                       "tei2.dtd" [
<!ENTITY % TEI.extensions.ent
           PUBLIC "-//ProjectName//ENTITIES Local modifications to
                   TEI main DTD//EN" >
<!ENTITY % TEI.extensions.dtd
           PUBLIC "-//ProjectName//DTD Local element types for
                   TEI main DTD//EN" >
]>]]></eg></p><p>For reasons of convenience, it may be desirable in practice to
create a <term>derived DTD</term> in which the local modifications
have been integrated with the TEI main DTD in a single file.  If such
a  one-file DTD is desired, it should be derived automatically from
the TEI DTD and the local modifications files using appropriate
software, rather than derived by hand-editing the TEI DTD files, as
hand-editing increases the chances of error and inconsistency between
the DTD modifications files and the one-file DTD. Documents in the TEI
interchange format must use the form shown above, with a reference to
the unmodified main TEI DTD and declarations of the local
modifications files.</p><p>The following must remain true of the DTD after modification:
<list type="simple"><item>the overall document must contain a single <gi tei="yes">teiHeader</gi>
element and a single <gi tei="yes">text</gi> element, in that order; in the
case of a corpus or collection the overall collection may have a
<gi tei="yes">teiHeader</gi> followed by a series of <gi tei="yes">tei</gi> documents;</item><item>the <gi tei="yes">teiHeader</gi> element must include elements for:
<list type="gloss"><label>title statement</label><item>the title of the machine-readable work and the names of those
responsible for it;</item><label>publication statement</label><item>place and date of publication or distribution of the machine-readable
document;</item><label>source description</label><item>bibliographic description of the copy text or source of the
electronic text, including at least title, author,
        and edition.</item></list></item></list></p><p>A TEI-conformant document may be said to require <term>DTD
extensions</term> if it:
<list type="simple"><item>defines new elements;</item><item>modifies the content model, declared content, or omissibility of any
element;</item><item>adds or modifies any attribute definitions;</item><item>renames any elements, attributes, or attribute values;</item><item>defines any new document types;</item><item>declares any non-SGML notations.</item></list>
Without requiring DTD extensions, therefore, any TEI document may:
<list type="simple"><item>define entities and parameter entities;</item><item>include processing instructions and comments in its DTD subset.</item></list>
For local-processing purposes, a TEI document may also, without
requiring DTD extension:
<list type="simple"><item>include link type declarations etc. in its SGML prolog;</item><item>define and use short reference mapping in its DTD.</item></list>
 
Note that TEI interchange documents may <emph>not</emph> include link
type or short reference declarations because the SGML declaration for
interchange does not allow them.</p><p>It is expected that the notion of DTD extension will be particularly
useful in describing the classes of documents accepted or
validated by software.</p></div2><div2 id="PROCMOD" name="Anthony" ref="Y"><head>TEI Processing Model</head><p>This section is included for illustrative purposes only; it does
not restrict the processing of TEI or other documents.  It simply
distinguishes a number of typical ways in which a project may choose
to apply the TEI Guidelines to different kinds of processing.</p><div3 id="PMDOC" name="subsection" ref="Y"><head>Document Capture and Reclamation</head><p>First, data might be captured by keyboarding into a locally defined
data capture format, or by scanning into a locally defined scanner-file
format.  From these initial forms, transducers might convert the files
into a standard local storage format.</p></div3><div3 id="PMLOCAL" name="subsection" ref="Y"><head>Local Storage Format and Application Software</head><p>The local storage format might be the input format of some
application program used frequently by the project.  In this case,
transducers might be necessary to prepare data for processing by other
applications.  Alternatively, the local storage format might be
independent of the formats used by application programs; transducers
would be needed to prepare data for any processing.  Such an
independent format is useful if the local storage format needs to
contain more information than any single application can conveniently
handle.</p><p>The local storage format might be SGML-conformant without being
TEI-conformant, e.g. because it uses local DTDs instead of the standard
TEI DTDs, or because it uses a TEI local processing format.  Local
software may be used to validate a TEI
local-processing format, to transduce documents into the input formats
needed by applications, and when appropriate to transform documents
into the TEI interchange format for exchange with other sites.</p><p>Finally, the TEI interchange format may be used as a local storage
format.  It is not expected that this will be a very common practice,
since it is expected that most sites interested in TEI conformance
will eventually acquire SGML-conformant software which allows for a
more compact local storage than does the interchange format.  In the
absence of SGML software, however, some projects may find the TEI
interchange format (or perhaps a restrictive variant of it) useful,
because such a format can be relatively easy to parse with ad hoc
software.</p><p>Whether the local storage format is strictly TEI conformant or not,
it may follow TEI-recommended practice in its selection of textual
features to be marked up, in its tag names, in its documentation
practices, etc.</p></div3><div3 id="PMRICH" name="subsection" ref="Y"><head>Enrichment and Other Processing</head><p>Over the course of the project, analysis and processing may result
in interim results which may be incorporated into the locally stored
copy of the text so that the interim results can be used in later
processing.  This process of enrichment can be carried out either by
manual editing of the documents using conventional text editors, or by
application programs. <!--  which perform (part of) the analysis. --></p></div3><div3 id="PMEXP" name="subsection" ref="Y"><head>Data Export</head><p>When a document is to be exchanged with another site using the TEI
interchange format, it must first be transduced from the local storage
format to TEI interchange form.  If local documents are already
TEI-conformant, this requires either no processing at all, or a
relatively simple normalization which can be handled readily by the
normalization facilities of most SGML parsers.  If the local storage
form is non-SGML conformant, some transducer must be used to transform
it into the TEI interchange format.</p><p>The TEI-interchange-format document must then be packed for shipping
into the TEI packed interchange format, using a packing program.  This
program will gather the constituent parts (files) of a document into a
single file, and ensure that the file contains no characters whose safe
passage to the recipient of the data is endangered by the transmission
path.  If the ultimate recipient of the document is unknown, the set of
safe characters is very small.  The specific <term>transmission
character set</term> however is independent of TEI conformance:  any
convenient set may be used where both parties agree.  The packer will
ensure that the transmission character set is properly identified.</p></div3><div3 id="PMIMP" name="subsection" ref="Y"><head>Data Import</head><p>When a document is received from another site using the TEI packed
interchange format, it must first be unpacked into a TEI
interchange-format document in the local character set.  It may then be
necessary to <term>naturalize</term> it by translating it into the
local storage format; if the local format is TEI- or SGML-conformant,
no processing is needed (although some SGML processors may offer a
facility for suppressing omissible markup).</p></div3><div3 id="CFPM" name="subsection" ref="Y"><head>TEI Conformance in the Processing Model</head><p>The notions of TEI interchange format and TEI packed interchange
format are central to the exchange of documents using the TEI
guidelines, whether the local storage format is TEI-conformant or not.
The TEI interchange format and the TEI local-processing format may each
be used as a local storage format, though the local storage format
might well differ from either of these without materially affecting the
use of TEI formats for interchange.  The TEI interchange format being
less flexible than the local-processing format, it is expected that
sites using SGML-conformant software may use the latter, while sites
without such software may prefer the former.</p><p>The notion of TEI recommended practice, it is hoped, will be
relevant to decisions about what textual features should be recorded
during data capture and will thus affect data-capture formats and the
transducers which render captured files into the local storage format.</p><p>The TEI abstract structure may be useful in developing local
non-SGML markup schemes for data capture or for processing with ad hoc
application programs.  It is strongly recommended that the TEI
recommendations, as well as the TEI abstract structure, be used for
such development as well.</p></div3></div2><div2 id="CFASP" name="Anthony" ref="Y"><head>Aspects of Conformance and Document Description</head><!-- DD asks: Are we back to normative status here? (cf sentence--><!-- at end of first para of previous div2) --><!-- I'm jiggered if I know...    (LB)  --><div3 id="CFCH" name="subsection" ref="Y"><head>Character Sets</head><p>Neither the character sets used for local processing nor those used
for transmission of interchange documents are restricted by the
definition of TEI conformance.  For local processing, users will
typically use the system character set of their local system or some
modification thereof.  For exchange with known partners, users should
choose any convenient character set; typically the most convenient is
the set of all characters which:
<list type="simple"><item>are transmitted successfully over the existing transmission link;</item><item>occur in both sender's and receiver's local coded character sets.</item></list></p><p>For blind exchange with unknown partners a conservative choice of
transmission set is needed to ensure that characters arrive
correctly.  How conservative the choice need be depends on the medium
of transmission.  The <term>ISO 646 subset</term> defined in section<xref target="CHIN"/>
 remains the only guaranteed safe set of characters
for the regional and international networks most widely used, although
larger character sets are increasingly coming into use. This is
largely because silent and not always reversible translation between
character sets remains a feature of transmissions across current
disparate networks.  At the present time (1993) therefore, only the
ISO 646 subset is recommended for fully blind interchange, although
the full complement of ISO character sets may be used successfully in
some subdomains.</p><p>In transmission by disk or tape, however, no silent translation is
likely to occur, and so larger sets may be successfully used in blind
interchange.  The primary danger is a failure of software in the
receiving machine to process the characters correctly; at this time
(1991), ASCII or 94-character U.S. EBCDIC appear to represent the
largest safe choices; other national character sets may of course be
used if good internal documentation is also provided.</p><p>Note that the transmission character set does not associate specific
binary encodings with the characters in the set.  In the technical
senses, it is a character set, not a <emph>coded</emph> character set.
This means that a document may undergo various automatic translations
from one coded character set to another (notably, in the case of
transmission over international networks, from ASCII to EBCDIC or vice
versa) without leaving the <term>transmission character set</term>.<!-- kill this section? it adds nothing --></p><p>For further discussion of the topics addressed in this section, reference
should be made to chapter <xref target="IN"/>.</p></div3><div3 id="CFSD" name="subsection" ref="Y"><head>SGML Declaration</head><p>The utility of various SGML constructs is discussed in section
 2.2 of document TEI P1 version 1.  The restrictions on SGML declarations
and SGML usage in TEI interchange documents discussed above under<xref target="SGMLMOD"/>
 are derived from that discussion.</p><p>No restrictions are made on SGML usage in the local processing
format because such usage is best determined locally and has no impact
on interchange.</p></div3><div3 id="CFDTD" name="subsection" ref="Y"><head>SGML Document Type Declaration</head><p>The document type declaration provided by the TEI is intended to
cover as wide a variety of document types and processing needs as
proved feasible.  It is impossible, however, for any finite list of
text elements to cover every need of textual research and processing.
As a result, extension of the TEI DTD has no effect
on strict TEI conformance, as long as certain restrictions are
observed; these have the effect of ensuring that later users of a file
can easily see what changes have been made to the DTDs and what the new
tags are intended to mean.</p><p>The requirement that all new or modified tags be documented,
however, is formally verifiable only to a limited extent.  It is
possible for a program to verify that for every tag introduced in a DTD
modification, a corresponding record exists in a Tag Set Declaration.
It is impossible, however, to verify using formal means that the entry
in the tag set declaration makes sense.  Purely formal conformance
measures, therefore, must be supplemented with human inspection of the
documentation.</p><p>The concept of DTD extension is introduced to allow the concise
description of software which is designed to handle documents encoded
using the published DTDs but which is not prepared to deal with tags
not included there.
<note source="auth" place="display" anchored="Y">Some will regard such simplifications as useful ways of making it
easier to develop software which accepts TEI-conformant documents;
others will deplore the failure of such software to accept all
TEI-conformant documents including those which extend the TEI DTD.  In
providing the notion of <term>DTD extension</term> for describing what
documents are and are not accepted by such software, the TEI acts in
the belief that such software will in fact be developed; it neither
endorses nor deplores its construction or use.</note></p><p>All sections of the TEI DTD are subject to modification by the
user, except that a documentary header must be provided and
distinguished from the text itself, and that documentary header must
include tagged elements identifying the document encoded and those
responsible for the encoding.  This ensures that all TEI-conformant
documents will have at least this bare minimum of accompanying
documentation.</p></div3><div3 id="CFTAG" name="subsection" ref="Y"><head>Tag Usage and Feature Marking</head><p>The basic design principles of the TEI require the notion of
<term>TEI conformance</term> to be applicable to existing electronic
documents if they are translated into a proper format, without
requiring the insertion of information not captured in the initial
preparation of the text.
<note source="auth" place="display" anchored="Y">See document TEI PC P1 <q>The Preparation of Text Encoding
Guidelines.</q></note></p><p>At the same time, the TEI is charged with formulating advice to
those engaged in the creation of new electronic texts and is required
to distinguish what is actively recommended for general use from what
is merely optional, provided for use by those engaged in a particular
sort of work.</p><p>The notion of <term>TEI recommended practice</term> is introduced to
allow the concise description of documents in which not only the
requirements, but also the recommendations of the Guidelines are
followed.  It is hoped that while projects to convert existing
electronic data may content themselves with achieving TEI conformance,
projects to produce new electronic texts will produce documents
following TEI recommended practice.  To distinguish those projects
which follow the TEI's recommendation to use SGML markup from those
which capture the same underlying textual features but do so using
non-SGML markup, the notion of the <term>TEI abstract model</term> is
introduced; it is this which a non-SGML-based encoding can have in
common with the TEI.</p></div3><div3 id="CFNON" name="subsection" ref="Y"><head>Non-SGML Markup</head><p>In exchanging texts for use by others, the goal of an interchange
format is to ensure that the information encoded in an electronic
version of a text can be correctly understood and processed by the
recipient as well as by the originator of the text.  To assure the
achievement of this goal, the definition offered here of TEI
conformance restricts markup in TEI conformant documents to SGML markup
and to properly declared non-SGML notations.  The latter are explicitly
recommended for the encoding of tables,
figures, etc. and so cannot reasonably be excluded.  Since they do
place a burden on the recipient for proper processing, the use of any
such non-SGML notation is defined to fall within the class of DTD
extensions.</p><p>Because of the escape clause for graphics, etc., it is in principle
possible to create a TEI conformant document by embedding a document
using any arbitrary markup into a driver file containing a TEI header
and a declaration for the appropriate markup as a non-SGML notation.
Though it falls within the letter, such a practice falls outside the
spirit of TEI-conformant document interchange.</p></div3></div2></div1><!-- Following Glossary shd move to back matter or be junked --><!-- OK,  given the choice, I say : junket (LB) --><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2cf.odd ??><!-- 28 TEI Conformance --><?tei:SOF p2md.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2md.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/31 18:27:01  tei
    * fix log keyword
    *
    * Revision 1.7  94/04/07  23:59:05  msmcq
    * uppercase DTD
    * --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : reuppercase 'DTD'                       --><!-- 12 Mar 94: fix typos noted by EM --><!-- 93-05-28 : MSM : change tagging for conformance          --><!--                  cosmetic changes (reformat paragraphs)  --><!--                  light editorial stylistic changes       --><!--                  fix xrefs and remove notes to editors   --><!--  --><!-- Michael:                                                     --><!-- I used these tags as well as what you sent me:               --><!--    OL ... LI  .. /OL for ordered lists and items             --><!-- I left my notes to you about where material should be deleted--><!--    from ST in this chapter as NOTEs                          --><!-- I have some cross-references to other chapters and sections. --><!--    Not knowing how to mark them, I used DTBXREF.             --><!--    (Except in my notes to you, which I expect you to delete.)--><!-- David                                                        --><!--  --><div1 id="MD" n="29" name="Faisal" ref="Y"><head>Modifying the TEI DTD</head><p>These Guidelines provide an encoding scheme suitable for encoding a
wide range of texts, and capable of being extended in well-defined and
documented ways for texts that cannot be conveniently or appropriately
encoded using what is provided.  This chapter describes how the TEI
encoding scheme may be modified and extended.</p><p>The formal mechanisms provided by these Guidelines are syntactic
mechanisms for encoding information in electronic texts.  The semantics
associated with these syntactic mechanisms are described only
informally in the accompanying text.  Although the descriptions have been
written with care, there will inevitably be cases where the intention of
the contributors has not been conveyed with sufficient clarity to
prevent users of the Guidelines from <soCalled>extending</soCalled> them
in the sense of attaching slightly variant semantics to them.</p><p>Beyond this unintentional semantic extension, some of the elements
provided can intentionally be used in a variety of ways; for example,
the element <gi tei="yes">note</gi> has an attribute <att tei="yes">type</att> that
can take on arbitrary string values, depending on how it is used in a
document.  A new type of annotation, therefore, requires no extension to
the TEI document type definition.</p><p>Furthermore, there are several ways for combining and extending the
existing syntactic mechanisms themselves.  Earlier chapters have
identified these:
 
<list type="bullets"><item>Combining the supplied tag sets---the core with one or more base
tag sets and additional tag sets---as described in chapter <xref target="ST"/></item><item>Documenting how languages are represented using character sets in
a document by providing one or more writing system declarations, as
described in chapter <xref target="WD"/></item><item>Extending the intentionally open-ended feature structure mechanism
by providing one or more feature system declarations, as described in
chapter <xref target="FD"/></item></list>
 
This chapter explains how the supplied tag sets can be modified by
suppressing elements, renaming elements, extending syntactic classes,
and adding elements.  The different techniques described here have
different effects on the level of TEI conformance to be ascribed to a
text, as described in chapter <xref target="CF"/>.</p><p>The TEI DTD is designed to support modification of the tag sets
in a documented way that can be validated by an SGML parser.  Those
wishing to modify the tag sets must do so using <emph>only</emph> the
mechanisms described in this chapter if the resulting documents are to
be TEI conformant.</p><p>This approach to modification implies the existence of two versions
of any DTD derived from the TEI tag sets.  The first version is a
fixed human-readable version.  The TEI DTD fragments that have
appeared earlier in these Guidelines are all presented in this
version, save in the few cases where forward pointers to this chapter
appear.  This is the <term>publication version</term> of the DTD.
Applications that do not use any of the modification mechanisms
described in this chapter should use these DTD fragments.</p><p>The second version of a TEI DTD is automatically derived from the
first by the introduction of parameter entities.  These parameter
entities are given values that contain small parts of the definition
of the DTD.  If these parameter entities are not modified, their
default expansion (equivalent to the publication version) is used
within the DTD.  However, their definitions can be easily changed for
a specific application.  This is the <term>modifiable version</term>
of the DTD.  It is also directly usable by an SGML parser.</p><p>In the absence of any modification, the TEI core DTD and
the additions to it embodied in the base and
additional tag sets behave as follows:
 
<list type="ordered"><item>All the elements described in the relevant sections of these
  Guidelines are defined.</item><item>The names of these elements are as given by these Guidelines.</item><item>The content model of each element is as given by these Guidelines.</item><item>The attributes of each element and the names and types of these
  attributes are as given in these Guidelines.</item><item>The membership of element classes, and the resultant inheritance
  of attributes are as given in these Guidelines.</item></list>
 
The modification mechanisms allow the user to override these defaults
in the following ways, while retaining conformance to the TEI
Guidelines:
 
<list type="ordered"><item>The definition of elements may be suppressed, so deleting the
      associated elements from the modified DTD.</item><item>The name (generic identifier) associated with an element may
      be changed, while preserving the semantics of the element.  Note,
      however, that the new name may not clash with the default name of
      any element defined in these Guidelines.</item><item>The global <att tei="yes">teiform</att> attribute should be used to specify
the TEI name for such renamed elements.</item><item>Those parts of the content model of an element which are specified
      by classes may be extended by adding members to the classes.</item><item>Further attributes, together with their names and types, may be
      specified for an individual element and existing attributes for an
      individual element may be
      renamed.  Note that the new names may not clash with names of
      existing attributes for the element.</item><item>Further attributes, together with their names and types, may be
      specified for the elements in a particular class and those
      inheriting characteristics from that class.</item></list>
 <!-- Because of the generality of the modification            --><!-- mechanisms presented in this chapter, they allow more    --><!-- thoroughgoing modification at the cost of sacrificing    --><!-- TEI conformance.                                         -->
 <!-- preceding paragraph paraphrased thus: -msm               -->
 
The modification mechanisms presented in this chapter are quite general,
and may be used to make all the types of changes just listed.  They can
also be used to make more complete modifications of the DTD; if changes
other than those listed above are made, however, the resulting text will
no longer be TEI conformant.
 <!-- cut following para at suggestion of EM --><!--
<p>Users who wish to allow some but not all the types of modification
mentioned above might wish that many more than two DTDs could be
maintained, one to support each possible combination of the various
kinds of modification described later in this chapter, and no others.
(For example, one might wish for a version that allowed only deletion of
elements and renaming of GIs, but not the redefinition of content models
or attributes.)  This wish is comprehensible, but a multiplicity of
versions would severely complicate the preparation and maintenance of
the TEI DTD and on the whole, the benefit which might be achieved
(that is, the prohibition of the unwanted kinds of modification in some
context) seems smaller than the administrative burden such a plan would
impose.  The TEI therefore will provide only two versions of its DTD:
one version disallowing all modifications, and a second version
facilitating any and all of the allowable modifications described in
this chapter, and no others.
--></p><p>These Guidelines provide for user modification of the TEI DTD largely
by using SGML parameter entities at appropriate points in the DTD.  It
is not absolutely essential to understand them in detail to modify the
TEI DTD (the examples later in this chapter can be followed cookbook
fashion), but it will probably prove helpful.</p><p>Parameter entities are an SGML mechanism for allowing string
substitution within markup declarations; they can thus can be used to
effect changes in declarations.
 <!-- For some categories of declaration in SGML it is         --><!-- considered a syntax error if two declarations appear     --><!-- for the same item.  For example, it is an error to give  --><!-- two element declarations for the same generic            --><!-- identifier.  Thus it would be illegal to attempt to      --><!-- replace the definition of an element, say < gi tei=yes   --><!-- > p < / gi > , in one of the TEI DTDs by giving a new    --><!-- definition that was simply included in the document      --><!-- type declaration subset (see chapter < xref target=SG    --><!-- >).                                                      -->
 
A parameter entity, unlike an element, may be declared more than once in
an SGML document type definition; if more than one declaration is given,
the parser uses the first one it encounters.  Since the declaration
subset within the document is read before the external file containing
the predefined DTD, an entity declaration in the DTD subset will take
precedence over one in the external file.  In the TEI DTD, the literal
string which defines the model group for some elements, say <gi tei="yes">p</gi>, is made the value of a parameter entity; the actual
element declaration for <gi tei="yes">p</gi> contains not the literal string
itself, but a reference to the parameter entity (in this case,
<ident tei="yes" type="pe">paraContent</ident>).  If the document's DTD subset contains
a declaration for <ident tei="yes" type="pe">paraContent</ident>, this will be used in
preference to the standard definition within the external
TEI DTD files.  The redefinability of parameter entities accounts both
for the TEI's use of parameter entities as the vehicle for effecting
extensions, and for the separation of entity definitions from other
material (to be defined below) that might be needed for certain
modifications of the TEI DTD.</p><p>Local modifications are most conveniently grouped into two files,
one containing modifications to the TEI parameter entities, and the
other containing new or changed declarations of elements and their
attributes.  Names for these files should be specified by the
parameter entities <ident tei="yes" type="pe">TEI.extensions.ent</ident> and
<ident tei="yes" type="pe">TEI.extensions.dtd</ident>, by declarations such as the
following:
 
<eg><![CDATA[<!ENTITY % TEI.extensions.ent system 'project.ent' >
<!ENTITY % TEI.extensions.dtd system 'project.dtd' >]]></eg>
 
These declarations must be given in the document's DTD subset.  The
first will be needed for all of the modifications discussed below.
The second is only required for the last type of extension
described. The parameter entities thus defined are then referenced at
an appropriate point in the compiling of the TEI DTD, as further
described in section <xref target="STIN"/>.</p><div2 id="MDMD" name="Anthony" ref="Y"><head>Kinds of Modification</head><p>There are several kinds of modification that can be made to the TEI
DTD as follows:
 
<list type="ordered"><item>deletion of elements,</item><item>renaming of elements,</item><item>extension of classes, and</item><item>modification of content models or attribute lists.</item></list>
 
These are described in the remaining sections of this chapter.</p><p>Each kind of modification changes the set of documents that can be
parsed using the DTD. Each combination of the original TEI DTD
fragments may be thought of as defining a certain set of
documents. Each DTD resulting from a modified set of TEI DTD
fragments allows a different set of documents to be parsed.  The set
of documents parsed by the original DTD may be properly contained in
the set of documents parsed by a modified DTD, or vice versa.
Modifications that have either of these two results are called
<term>clean modifications</term> in the remainder of the chapter.
Alternatively, the set of documents parsed by the original DTD might
overlap the set of documents parsed by the modified DTD with neither
being properly contained in the other.  Modifications that have this
result are called <term>unclean modifications</term> in the remainder
of the chapter.</p><div3 id="MDMDSU" name="subsection" ref="Y"><head>Suppressing Elements</head><p>The simplest way to modify the supplied tag sets is to suppress one
or more of the supplied elements.  In the modifiable version of the
DTDs, every element declaration is enclosed by a marked section.  The
marked section is governed by one of the keywords <code tei="yes" type="kw">IGNORE</code> or <code tei="yes" type="kw">INCLUDE</code>, which is
provided indirectly using a parameter entity. This parameter entity
has the same name as the generic identifier of the element.  Thus, the
declaration for the paragraph element, <gi tei="yes">p</gi>, occurs
within a marked section <soCalled>guarded</soCalled> by the parameter
entity <ident tei="yes" type="pe">p</ident>:
 
<eg>&lt;![ %p [
&lt;!-- element and attlist declaration for p goes here   --&gt;
]]&gt;</eg>
 
The declaration given for these <term>guarding entities</term> in the
modifiable version is <code tei="yes" type="kw">INCLUDE</code> in all cases.  The
construct above is interpreted thus: the first of the three lines is
the opening of a marked section; when the parser encounters the
section and sees the keyword <code tei="yes" type="kw">INCLUDE</code> as its guard (more
precisely, sees a parameter entity the value of which is the keyword
<code tei="yes" type="kw">INCLUDE</code>), the content of the marked section is parsed;
the second line of the three is the content of the marked section; and
the third line of the three is the closing of a marked section.  If
the guard is changed to <code tei="yes" type="kw">IGNORE</code>, the SGML parser will
ignore the content of the marked section.</p><p>Thus, to delete the declaration of a generic identifier and thus
suppress the element entirely, the entity that provides the guard on the
marked section wherein the element declaration appears must simply be
set to <code tei="yes" type="kw">IGNORE</code>.  For example, if the <gi tei="yes">note</gi>
element is not to be used in a particular application, the line
 
<eg><![CDATA[<!ENTITY % note 'IGNORE'>]]></eg>
 
must be inserted in the file which has its name given by the entity
<ident tei="yes" type="pe">TEI.extensions.ent</ident>.</p><p>Two different cases of deleting one or more elements from the TEI
DTD can be identified.  The first case involves deleting only elements
that are optional wherever they appear in TEI documents.  Deleting these
is clean in the sense that documents that are parseable with the modified
DTD can also be parsed according to the original TEI DTD.  To say this
another way, the set of documents matching the new DTD is contained in
the set of documents matching the original DTD.</p><p>The second case involves deleting elements that are required in one
or more of their appearances in TEI documents.  Deleting these is
unclean in that some documents that can be parsed according to the new
DTD could not be parsed according to the original TEI DTD.  To say this
another way, the set of documents matching the new DTD neither contains
nor is contained in the set of documents matching the original DTD.</p></div3><div3 id="MDMDNM" name="subsection" ref="Y"><head>Renaming Elements</head><p>In the modifiable version of the TEI DTD, elements are not referred to
directly by their generic identifiers; instead, the modifiable version
of the DTD makes use of parameter entities that expand to the standard
generic identifiers.  This allows renaming of elements by redefining the
appropriate parameter entities.  The names of parameter entities used
for naming are formed by taking the standard generic identifier of the
element and attaching the string <q>n.</q> (for <q>name</q>) as a
prefix.  Thus, the standard generic identifiers for paragraphs, notes
and quotations, <gi tei="yes">p</gi>, <gi tei="yes">note</gi>, and <gi tei="yes">q</gi>, are defined
by declarations of the following form:
 
<eg><![CDATA[<!ENTITY % n.p    'p'>
<!ENTITY % n.note 'note'>
<!ENTITY % n.q    'q'>]]></eg>
 
These parameter entities are all contained within a file (<ident tei="yes" type="file">teigis.ent</ident>) which is embedded during the compilation
of a TEI DTD.  To change the name of an element therefore, all that
is needed is to provide an overriding declaration for the appropriate
parameter entity. For instance, the following declaration converts <gi tei="yes">note</gi> to <gi tei="no">annotation</gi>:
 
<eg><![CDATA[<!ENTITY % n.note 'annotation'>]]></eg>
 
This declaration must be inserted in the file which has its name given
by the entity <ident tei="yes" type="pe">TEI.extensions.ent</ident>.</p><p>Two different cases of renaming can be identified.  The first case
involves replacing existing names with names that are otherwise unused
in the TEI name space.  (This can be easily checked by looking in the
index of the Guidelines.)  Such a modification is clean in that the new
DTD would still accepts any document accepted by the publication DTD
(given the appropriate renaming of elements).  The new name cannot
possibly conflict with the generic identifier of any other element,
since there can be no other occurrences.  To say this another way, the
set of documents matching the new DTD is isomorphic to the set of
documents matching the old DTD.  The example given results in a clean
modification because there is no element <gi tei="no">annotation</gi>
specified in these Guidelines.  It is also true that any document not
using the renamed element which parses under the unmodified DTD will
also parse under the modified DTD.</p><p>The second case involves introducing a name already used somewhere
in a TEI tag set.  This is unclean in that it changes what an existing
generic identifier means.  The name in question could not be declared
by any tag set that is used in the document, as it is syntactically
invalid to provide two declarations for the same element.  The new
generic identifier might occur in some TEI tag set not currently
included in the DTD used to parse the document.  For example, if in
some setting the element <gi tei="yes">note</gi> were assigned the new
name <gi tei="no">fs</gi> (because, say, notes are used in some
technical document to record functional specifications) there might be
no immediate problem.  If however it was later decided to add the
feature structure analysis tag set into the DTD used to parse the
document, though, a name clash would occur. There would also be
problems in interchanging the resulting documents without confusion.</p><p>As a special case, consider translating all of the generic
identifiers for all elements into some other language, L.  It may be,
for example, that the word for <q>paragraph</q> in language L begins
with the letter <q>s</q> and that thus the paragraph element is
renamed as <gi tei="no">s</gi>.  By the definition just given, this
would be an unclean modification because an element <gi tei="yes">s</gi>
already exists in the TEI DTD.  However, this is clearly not a
problem so long as all of the names are redefined at once and that no
collisions occur in the new name space: that is, provided that the TEI
element <gi tei="yes">s</gi> is renamed as some other string.  This can be done
by a total replacement of the file that contains the entity
declarations for the names of the elements.  This systematic
replacement of names in the DTD must be followed by a systematic use
(or replacement) of the new names in the document.  To think about
this in the terms used earlier, the set of documents matching the new
DTD (with all names systematically changed in both the DTD and the
documents) is isomorphic to the set of documents matching the original
DTD with no names changed (in either the DTD or the documents).</p><p>The formal declarations of the parameter entities used for generic
identifiers are contained in the file <ident tei="yes" type="file">teigis.ent</ident>; since their names and replacement texts
are fully predictable, these parameter entities are not individually
documented in the reference section of these Guidelines.  The
parameter entity <ident tei="yes" type="pe">tei.elementNames</ident> is used to
embed the file <ident tei="yes" type="file">teigis.ent</ident> in the DTD. A
re-declaration for this parameter entity may therefore be used to
embed a different version of this file:
 
<eg><![CDATA[<!ENTITY % tei.elementNames system 'OTAgis.ent' >]]></eg></p><p>If an element is renamed using the techniques described here, its
declaration for the global <att tei="yes">TEIform</att> attribute will be left
undisturbed; the default value will therefore still be the standard
TEI name for the element.  TEI-aware application programs can thus
process TEI-conformant documents which rename TEI elements, since by
consulting the <att tei="yes">TEIform</att> attribute value the application can
learn the standard name for the element and process it accordingly.</p><p>In the normal course of events, this value of this attribute will
never be specified in a TEI-conformant document; all occurrences will
have the default value.  In some special circumstances, it can be
useful to specify a non-default value on some instances of an element;
this allows application programs to process correctly a locally
defined element which usually corresponds to one TEI element (which
would be expressed by the default value) but sometimes to another TEI
element (which would be expressed by explicit values attached to the
element instance).</p></div3><div3 id="MDMDCL" name="subsection" ref="Y"><head>Class Extension</head><p>In <xref target="STECCM"/>, the concept of a class of elements that
can appear in the same kinds of structural locations in a document was
introduced.  An entity is associated with each class named by
prefixing the string <q>m.</q> (for <q>model</q>) to the name of the
class.  For example, the value of the parameter entity
<ident tei="yes" type="pe">m.bibl</ident> is a list of the members of the class
<ident tei="yes" type="class">bibl</ident>.</p><p>In the modifiable version of the TEI DTD, an additional entity is
defined for each model class.  This additional entity also takes the
name of the class, this time prefixed by the string <q>x.</q> (for
<q>extension</q>).  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 its associated
x-dot entity.</p><p>For example, the class <ident tei="yes" type="class">bibl</ident> has the three
members <gi tei="yes">bibl</gi>, <gi tei="yes">biblFull</gi>, and <gi tei="yes">biblStruct</gi>.
Its content-model entity is defined thus:
 
<eg><![CDATA[<!ENTITY % x.bibl '' >
<!ENTITY % m.bibl '%x.bibl bibl | biblFull | biblStruct' >]]></eg>
 
With the default value of the x-dot entity, this is the same as
defining <ident tei="yes" type="class">m.bibl</ident> with the replacement text
<code lang="sgml" tei="yes" type="frag">bibl | biblFull | biblStruct</code>.</p><p>An encoder can add an element to the class by providing a new
declaration for the x-dot entity.  For example, to add a new element
called <gi tei="no">myBib</gi>, this definition would be used:
 
<eg><![CDATA[<!ENTITY % x.bibl 'myBibl |' >]]></eg>
 
Note that the specification of an x-dot entity must always end with
the vertical bar character (for alternation).  The definition would be
inserted at the appropriate place in the file associated with the
entity <ident tei="yes" type="pe">TEI.extensions.ent</ident>.  This changes the
replacement text of <ident tei="yes" type="pe">m.bibl</ident> from its default
value to <code tei="yes" type="frag">myBibl | bibl | biblFull |
biblStruct</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.</p><p>Class extension is always clean in that the set of documents matching
the DTD containing the extended class contains all of the documents
matching the original DTD.  Class extension can be by adding an existing
element to a class, or by adding a new element (as described in the next
section) and extending the class with the new element.</p></div3><div3 id="MDMDRM" name="subsection" ref="Y"><head>New content models</head><p>Encoders can modify the content models that specify what is
contained in an element or set of elements defined by the TEI DTD,
modify the attributes of existing elements, or add new elements to the
DTD.</p><p>Content models or attributes for existing elements are modified in
two stages.  First, the existing definition of the element must be
deleted in the manner described in the first section of this chapter.
Second, a new definition of the element is given.  This new definition
must be inserted in the file associated with the entity
<ident tei="yes" type="pe">TEI.extensions.dtd</ident>.</p><p>For example, suppose that symbolic designations to be marked with the
element <gi tei="yes">term</gi> can always be associated with a particular source.
While the content model of the publication version of the TEI DTD is
acceptable, the attribute list needs to be extended.  To perform this
modification, the following steps must be taken.  The declaration
 
<eg><![CDATA[<!ENTITY % term 'IGNORE' >]]></eg>
 
must be inserted into the file associated with the entity <ident tei="yes" type="pe">TEI.extensions.ent</ident>.  Then a new definition must be
inserted into the file associated with the entity <ident tei="yes" type="pe">TEI.extensions.dtd</ident>.  In this example, the definition
will be the same as that given in <xref target="COHQU"/>, save for the
addition of a new attribute.
 
<eg><![CDATA[ <!ELEMENT term          - -  (%phrase.seq;) >
 <!ATTLIST term               %a.global;
           type               CDATA               #IMPLIED
           source             CDATA               #IMPLIED       >]]></eg></p><p>New elements are defined by inserting their definitions into the file
associated with the entity <ident tei="yes" type="pe">TEI.extensions.dtd</ident>.  To be
usable, they must somehow be included in the model for some existing
element.  This can be done either by class extension (which can now be
seen to be a restricted, special case of the process defined here)
or by redefining
the element(s) within which the new element is to be included.</p><p>The set of documents matched by the modified DTD and the set of
documents matched by the original DTD may be related in several
different ways.  It is certainly possible that
the former could properly include the latter or vice versa; either of
these could be said to be clean modifications because the set to be
matched has become strictly larger or strictly smaller.</p><p>It is also possible that the set of documents matched by the modified
DTD is different from the set matched by the original DTD and they may
either contain some common documents or have no documents in common;
either of these is said to be an unclean modification.</p><p>Radical revision is possible.  It would be possible to remodel so
that the <gi tei="yes">teiHeader</gi> is not required, or that it is
required but the minimal components described in chapter <xref target="HD"/>, are no longer required, or that no <gi tei="yes">text</gi>
element is required.  In fact, the mechanism, if used in an extreme
way, permits deletion of the entire set of TEI definitions and their
replacement by an entirely different DTD!  Such revisions would result
in documents that are not TEI conformant in even the broadest sense,
and it is not intended that encoders use the mechanism in this way.</p></div3></div2><div2 id="MDDO" name="Anthony" ref="Y"><head>Documenting the Modifications</head><p>When the modification mechanisms are used, their use must be
documented.  There are two ways in which information about the
modifications is recorded.</p><p>The first record of the modifications is in the use of the extension
files.  The file associated with the entity
<ident tei="yes" type="pe">TEI.extensions.ent</ident> contains the specifications of the
parameter entities that are redefined to accomplish the modifications.
This file should be structured in such a way that readers can easily
identify any modifications that have been made.  The following structure
is recommended.
 
<eg><![CDATA[<!--  The following elements are deleted     -->
<!--  The following elements are renamed     -->
<!--  The following classes are extended     -->
<!--  The following elements are revised   -->]]></eg>
 
The appropriate parameter entity specifications should be entered after
each comment in this file.  The order of the comments corresponds to the
order of the discussion in this chapter (roughly, from simple to
complex).  Setting the appropriate entity to <code tei="yes" type="kw">IGNORE</code> for
each revised element is done in the last section of the file.</p><p>The file associated with the entity <ident tei="yes" type="pe">TEI.extensions.dtd</ident>
should contain the DTD fragments for new and changed element
definitions.  The following structure is recommended.
 
<eg><![CDATA[<!--  The following declarations define new extensions    -->
<!--    (element and attlist specifications for new tags  -->
<!--    introduced in part 3 of the ent file go here)     -->
<!--  ...                                                 -->
<!--  The following declarations define revised tags    -->
<!--    (element and attlist specifications for tags      -->
<!--    mentioned in part 4 of the ent file go here       -->
<!--  ...                                                 -->]]></eg></p><p>These files give an SGML parser sufficient information to implement
the modifications and are also useful in providing human readers with
some indication of the changes made in the TEI DTD.  Full
documentation of any additional or modified elements should also be
provided, using the ancillary tag set described in chapter <xref target="TD"/>.</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2md.odd ??><!-- 29 Modifying TEI DTDs --><!-- &p2.lo; --><!--    Local Installation ... --><?tei:SOF p2in.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2in.odd,v $
# Revision 1.6  1994/03/27  16:30:42  lou
# sem,iinfal check
#
# Revision 1.4  1994/03/01  15:33:47  lou
# fix typos spotted by DTL
#
# Revision 1.3  1994/02/17  20:31:08  msmcq
# revision for SC review
# --><!-- Revisions:                                               --><!-- 94-02-15 : MSM : Added RCS id                            --><!-- 94-02-15 : MSM : correct ID                              --><div1 id="IN" n="30" name="Faisal" ref="Y"><head>Rules for Interchange
 </head><p>This chapter describes how interested parties can determine and agree
on the proper format for the successful interchange of TEI-conformant
documents over a given communications link, and how to translate from
normal TEI form to the transmission format and back.  It also includes
recommendations for formats to be used when private arrangements cannot
be made, in non-negotiated or <soCalled>blind</soCalled> interchange.
 </p><div2 id="NHNEG" name="Anthony" ref="Y"><head>Negotiated Interchange</head><p>When the sender and receiver of a given text know each other's
identity and can make appropriate special arrangements for the
interchange of the text, the following procedures may be used to
ensure the successful interchange of the text without information loss.
 </p><p>The sender and receiver together must first:
 
<list type="ordered"><item>agree on whether to exchange the document in
<term>TEI interchange form</term> or in some other form (e.g.
<term>TEI local-processing form</term>)
 </item><item>identify the <term>communications link</term>:  the method to be
used to transmit and receive the document (transmission over a given
network, physical transmission of a disk, tape, or other medium, etc.)
 </item><item>identify (by experimentation if necessary) the set of characters
which can be transmitted successfully, without corruption, over the
communications link; this is the
<term>transmission character set</term>.
 </item><item>identify the set of characters present in the document which lie
outside the transmission character set; this is the set of
<term>non-transmissible characters</term>.  For each character in this
set, the local writing system declaration should identify an entity name
or a transliteration into the transmission character set, which is to be
used to transmit the character.  The set of entities needed for this
purpose is the <term>transmission entity set</term>.</item></list>
 </p><p>The transmission character set is defined as the set of characters
in the sender's system character set(s) which survive transmission and
are properly recognized in the recipient's system character set.  It is
therefore by definition a subset of both the sender's and the
recipient's system character sets.  The bit patterns used to represent
the characters may differ in the two systems (e.g. one may use ASCII,
the other EBCDIC) if the communications link performs the proper
translations.
 </p><p>Current network standards allow --- indeed, require --- gateway nodes
to translate material passing through the gateway from one coded
character set into another, when the networks joined by the gateway use
different coded character sets.  Since there is no universally
satisfactory translation among all coded character sets in common use,
the transmission character set will normally be the subset which is
satisfactorily translated by the gateways encountered in transit between
the sender and the receiver of the data.
 </p><p>When material is transmitted on a physical storage medium
(e.g. disk or tape), then those exchanging documents have far greater
control over the data.  If both partners use compatible systems, the
transmission character set may be equivalent to their system character
sets; otherwise, the transmission character set will include those
characters which the recipient can successfully read into the local
system character set from the media provided by the sender.  For
example, if a diskette created by an MS-DOS machine can be mailed to a
Macintosh user and read directly by the recipient's system, then the
transmission character set is likely to be ISO 646 IRV (equivalent to
ANSI X3.4, or ASCII), which both machines have in common; if the
recipient's disk-reading utilities are more sophisticated, however,
then it may be possible to include some or all of the two machines'
non-standard extended characters as well.
 </p><p>The mapping from non-transmissible characters to the transmission
entity set may be derived from the writing system declarations in use by
the sender and receiver.
 <!-- <p>The transmission entity set allows all characters in  --><!-- the document to be represented even if they are not      --><!-- included in the transmission character set.  If two      --><!-- interchange partners are expecting to exchange more      --><!-- than one document, the transmission character and        --><!-- entity sets should be defined with respect to the        --><!-- entire set of documents to be exchanged, not with        --><!-- respect to individual documents.                         -->
 </p><p>After the transmission character set and entity character sets
have been defined, the sender must prepare and transmit the document:
 
<list type="ordered"><item>if the document is to be exchanged in TEI interchange format,
translate it from the local-processing form into the TEI interchange
form (e.g. by passing it through an SGML normalizer to supply omitted
SGML tags and interpret all short-reference sequences)
 </item><item>pack the document for transmission by replacing every
non-transmissible character with the appropriate transliteration or
entity reference.  At this point, every character in the document is
represented either by a character in the transmission character set or
by a reference to an entity in the transmission entity set; the document
is in <term>TEI packed format</term>.  If the transmission character set
includes all the SGML delimiter characters, the document will be a
conforming SGML document; otherwise, it may not be SGML-conformant but
will be easily mappable to a conforming document
 </item><item>transmit the document over the agreed link
 </item></list>
 </p><p>The translation of non-transmissible characters into the transmission
entity set may be accomplished under automatic control, by software
which reads the appropriate local writing system declarations, creates
the necessary mapping tables, and packs the document for transmission.
 </p><p>Upon receipt, the receiver must:
 
<list type="ordered"><item>unpack the document by expanding those entities which correspond
to characters in the local system character set(s); at this point, the
document should once more be a SGML-conformant, and should probably be
validated to detect any problems in transmission</item><item>optionally, material transliterated in the document as transmitted
may be translated into the local system character set(s) for more
convenient display, or from the transmission entity set into a local
transliteration scheme</item></list>
 </p><p>It is strongly recommended that when documents are interchanged they
be accompanied by any writing system declarations and feature system
declarations which are applicable.  In TEI-conformant interchange,
it is required that documents be accompanied by any applicable tag-set
documentation files.
 </p></div2><div2 id="NHEG" name="Anthony" ref="Y"><head>Some Simple Examples</head><p>As a first simple example, consider a document containing English,
French, and German, to be transmitted from an IBM-compatible personal
computer to a Macintosh, over a long-distance network connection.
Uploading test files from the PC to the sender's local network node,
sending the file via the network, and downloading the document to the
Macintosh, reveal (let us assume) that while all the characters of ISO
646 IRV survive intact, the accented characters of French and German do not
survive transmission.  In this case, the transmission character set is
composed of all the characters of 7-bit ISO 646.  The entity set
required to handle the non-transmissible characters will include the
following (assuming they actually occur in the document):
 
<list type="simple"><item>agrave</item><item>ccedille</item><item>eacute</item><item>egrave</item><item>ocirc</item><item>oelig</item><item>auml, Auml</item><item>ouml, Ouml</item><item>uuml, Uuml</item><item>szlig</item></list>
 
In <soCalled>packing</soCalled> the file for transmission, the sender
must replace the non-transmissible characters in the document with
references to these entities.  After this subsitution, the document is a
conforming SGML document written entirely in the transmission character
set, which can be sent over the communications link without any garbling
or loss of information.  Upon receipt, the recipient can replace the
entity references with the specific coded characters used on the
Macintosh to write French and German.
 </p><p>As a second example, consider the same document being transmitted
from a VAX running VMS to an IBM mainframe running VM/CMS.  Here, the
accented characters might be represented on the VAX using the coded
character set ISO 8859-1, but since ISO 8859-1 is not always
supported, it may be more likely that entity references will be used
instead.  Let us assume that the network path between the two machines
accepts Latin characters and digits, and most punctuation, but garbles
square brackets, braces, the hash mark, and the pounds-sterling
symbol.  In this case, the accented characters require no special work
by the sender, since they are already in a network-safe form.  Square
brackets, etc., must however be replaced by entity references to
<ident tei="yes" type="ent">lbr</ident>, <ident tei="yes" type="ent">rbr</ident>, etc.  After
this is done, the document is no longer conformant SGML, since the
square brackets used in certain markup declarations will not be
recognized.  (It is important, therefore, for validation to be
performed before the square brackets are replaced by entity
references.)
 </p><p>Upon receipt, the document may be translated into a valid SGML
document by replacing all references to <ident tei="yes" type="ent">lbr</ident>
and <ident tei="yes" type="ent">rbr</ident> with the appropriate square brackets,
etc.  If the local system supports one of the IBM code pages with
support for French and German characters, then the entity references
to those characters may be replaced by the characters in the system
character set.  More commonly, the entities for French and German
characters will be left in place.
 </p><p>As a third example, consider a document containing Greek, as well
as Latin, German, French, and English.  If the sender's system has a
full Greek character set, but the recipient's does not, then the Greek
characters must all be replaced either by references to SGML entities
or by transliterations into Latin characters (e.g. using the beta code
transliteration developed for the Thesaurus Lingu&aelig;
Gr&aelig;c&aelig;).  If the text is later transmitted to another
system which does have a full Greek character set, the transliterated
text or entity references may be translated, under control of the
relevant writing system declarations, into the local Greek character
set.
 </p><p>As a final example, consider a document written in Japanese, to be
transmitted over a network within Japan, or over an international
network to a recipient in Europe.  Since networks within Japan transmit
Japanese text without information loss, and common utilities may be used
to recognize any of the existing coded character sets and translate into
another, the transmission character set for interchange within Japan may
be the same as the system character set.  (If user-defined extensions
are defined, in order to allow the encoding of kanji not present in the
standard character sets, then these non-standard kanji may need to be
replaced either by entity references or by
<soCalled>transliterations</soCalled> into the standard character sets,
and the description of the kanji themselves should accompany the
documents in which they are used; the writing system declaration may be
used for this purpose.)
 </p><p>When transmitting Japanese text outside Japan, the limitations of the
networks at the time of transmission must be taken into account; it may
be necessary to transliterate the text, or to replace non-transmissible
characters with entity references.  
<!-- A set of entity declarations suitable for use in such --><!-- interchange is now being developed and will be available --><!-- from the TEI as soon as it is completed. -->
 
 </p></div2><div2 id="NHNON" name="Anthony" ref="Y"><head>Non-Negotiated Interchange</head><p>In some cases, no negotiation between interchange partners is
possible, because they do not know each other's identities.  Since it is
impossible to discover an appropriate transmission entity set by
experiment, such interchange requires the use of extremely conservative
assumptions about the frailties of network gateways.
 </p><p>Specifically, it is recommended that for non-negotiated interchange
the following practices be adopted:
 
<list type="bullets"><item>The transmission character set should be the International
Reference Version of ISO 646 (commonly known as ASCII).  If the material
is distributed on a physical medium, the material should actually be
encoded in ISO 646; if the material is distributed over a network, the
actual coded character set used at the point of origin is immaterial,
but the data should still be restricted to the repertoire of ISO 646
(IRV).</item><item>The transmission entity set should include only entities
documented in ISO standard entity sets, published TEI writing system
declarations, or writing system declarations made available with the
material.</item><item>All applicable writing system declarations should be distributed
together with the material they describe; in non-negotiated interchange,
all writing system declarations should assume ISO 646 (IRV) as
the system character set.</item><item>The SGML declaration distributed with the material should assume
ISO 646 (IRV) as the system character set. </item><item>If the receiver is not using ISO 646 IRV as the system character
set, then the receiver (or some intervening network node) must translate
from ISO 646 into the receiver's system character set.  The receiver or
the receiver's unpacking software is responsible for rewriting those
parts of the SGML declaration which are dependent on the coded character
set, and ensuring that they work properly on the receiving system.</item><item>As transmitted, the document should be a valid SGML document.</item></list>
 </p><p>By requiring the material to use only the characters of ISO 646
(IRV), and requiring the SGML declaration and accompanying writing
system declarations to assume ISO 646 (IRV) as the system character set,
these recommendations ensure that documents interchanged in this way
will be directly usable on a great variety of systems; moreover, since
ISO 646 is widely known and well documented, users of other systems will
normally be able to adjust the documentation and data stream to their
local systems without difficulty.
 </p><p>It should be noted that ISO 646 imposes a very
restrictive and cumbersome encoding for researchers whose character
sets have a large repertoire; it is strongly recommended, therefore,
that arrangements for interchange of such materials involve explicitly
negotiated interchange formats wherever possible.
 </p><p>The rules given here for non-negotiated interchange are not
guaranteed to succeed, and negotiation of interchange formats is
therefore <emph>required</emph>, if any of the following apply:
 
<list type="bullets"><item>The communications link between the interchange partners garbles
or corrupts any characters of ISO 646 (IRV), (i.e., ISO 646 (IRV) is
not a subset of the transmission character set).</item><item>The communications link maps characters not in the repertoire of
ISO 646 (IRV) onto characters in that repertoire.<!-- (e.g. by translating a TAB character to a control-I)     --><!-- ??? what?  msm                                           -->
 <!-- <item>The text uses characters for which no standard     --><!-- entities are defined by ISO standards or published TEI   --><!-- writing system declarations.                             --><!-- commented out:  I think if originator supplies wsd, all  --><!-- should be all right.  -msm                               -->
 </item><item>The document uses non-standard SGML syntax.
 </item></list>
 </p></div2><div2 id="NHCOMP" name="Anthony" ref="Y"><head>Notes for Implementors</head><p>The descriptions of document interchange in this chapter from time to
time refer to software used to pack documents for interchange, or to
unpack documents upon receipt.  The descriptions do not characterize any
specific existing software, but attempt to make clear how such software
must work, in a general way.  It is hoped that the descriptions will be
useful to implementors of packing and unpacking software, but the full
specification of such packing and unpacking software is beyond the scope
of this chapter.  All that can be attempted here is to describe some
complications which may arise in the packing and unpacking of documents
for interchange, of which implementors of such software should be aware.
 
<list type="bullets"><item>if the sender and receiver use different SGML syntaxes, various
incompatibilities may be encountered which will require one partner or
the other to modify the SGML syntax used for the document, or the
document itself, or both.  In general, unless other arrangements are
made, the responsibility for such modifications falls upon the receiver
of the document.</item><item>in particular, if the SGML syntax has been modified to expand the
set of legal name characters (e.g. to allow characters with diacritic
marks to occur in SGML names), then either the recipient must similarly
modify the local SGML declaration, or the SGML names must be modified
(by sender or receiver) to make them legal under the recipient's SGML
declaration; name collisions must be carefully avoided when this is
done.</item><item>if the transmission character set does not include all characters
with special meaning to SGML (name characters, delimiters, etc.), then
although the packed document will be in a one-to-one relationship with a
conforming SGML document, it will not itself be a conforming SGML
document.  In this case, final SGML validation must be done by the
sender before packing, and the recipient cannot validate the received
document before unpacking it.</item><item>the proper packing of characters for transport may vary from
language to language: in English text, a left square bracket may need
to be packed with an entity reference to <ident tei="yes" type="ent">lbr</ident>,
while the same bracket may have a different meaning, and thus a
different entity replacement, in Greek text.  In general, this means
the packing should be done by an application with enough SGML
awareness to detect element boundaries, read the value of the
<att tei="yes">lang</att> attribute from the start-tag or infer it from context,
and adjust its actions appropriately.  If only one WSD is in use in a
given document and no language shifts are present, then both packing
and unpacking may be done by a much simpler string-replacement
algorithm.  </item></list>
 <?tei:EOF p2in.odd ??>
             <!-- 30 TEI in Interchange --><!-- &p2.os; -->
            <!-- 33 TEI and Other Stds --><?tei:SOF p2nh.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2nh.odd,v $
    * Revision 1.5  1998/02/01 16:52:05  tei
    * change system identifiers to public identifiers
    * fix log keyword
    * normalize SGML
    *
    * Revision 1.4  94/03/27  16:30:55  lou
    * semifinal check
    * 
    * Revision 1.2  1994/02/17  20:29:04  msmcq
    * Merged old drafts
    * --><!-- Revisions:                                               --><!-- 94-02-15 : MSM : drop dot in pl. ids                     --><!-- 94-02-15 : MSM : merge msm new draft, old leavings from CO --><!-- 94-02-15 : MSM : Added RCS id                            --></p></div2></div1><div1 id="NH" n="31" name="Faisal" ref="Y"><head>Multiple Hierarchies</head><p>At various points in these Guidelines, the discussion has mentioned
the problems which arise when using SGML to encode textual features
which do not take a strictly hierarchical form:  features, that is,
which do not necessarily nest within other features.  This chapter
provides an overview of the techniques defined in these Guidelines for
handling such problems, and should be consulted when deciding how to
deal with them.</p><p>The following examples illustrate the type of problem with which this
chapter is concerned:
 
<list type="bullets"><item>in narrative, a speech by a character may begin in the middle of a
paragraph and continue for several more paragraphs</item><item>in a verse text, the encoder may need to tag both the formal
structure of the verse (its stanzas and lines) and its syntactic
structures (which sometimes nest within the metrical structure and
sometimes cross metrical boundaries)</item><item>in any kind of text, the encoder may wish to record the physical
structure of volume, page, column, and line, as well as the formal or
logical structure of chapters and paragraphs or acts and scenes, etc.</item><item>in verse drama, the structure of acts, scenes, and
speeches often conflicts with the metrical structure</item><item>in any kind of text, an embedded text (e.g. a play within a play,
or a song) may be interrupted by other matter; the encoder may wish to
establish explicitly the logical unity of the embedded material (e.g. to
identify the song as a single song, and to mark its internal formal
 structure)</item><item>in a dictionary, different types of information (e.g. orthography,
syllabification, and hyphenation) may be combined within a single
notation; the encoder may wish both to preserve the presentation of the
material in the source text and to disentangle the logically distinct
pieces of information in the interests of more convenient processing of
the lexical information</item></list>
 
Many other examples might be given, but these should suffice to show the
variety of applications where non-hierarchical or non-nesting
information appears, and to illustrate the various methods for
addressing the problem.
 <!-- For P4, we may want to use examples from ML W18 -msm     --></p><p>Non-nesting information poses fundamental problems for any encoding
scheme, and it must be stated at the outset that no solution has yet
been suggested which combines all the desirable attributes of formal
simplicity, capacity to represent all occurring or imaginable kinds of
structures, suitability for formal or mechanical validation, and clear
identity with the notations needed for simpler cases (i.e. cases where
the textual features do nest properly).  The representation of
non-hierarchical information is thus necessarily a matter of choices
among alternatives, of tradeoffs between various sets of different
advantages and disadvantages.</p><p>There are several methods used within these Guidelines to handle
non-nesting information in SGML:
 
<list type="bullets"><item><term>concur</term> : an optional feature of SGML which allows multiple
hierarchies to be marked up concurrently in the same document</item><item><term>milestone elements</term>: empty elements which mark the
boundaries between elements in a non-nesting structure</item><item><term>fragmentation</term> of an item: the division of what
logically is a single element into two or more parts, each of which
nests properly within its context</item><item><term>virtual joins</term>: the recreation of a virtual element
from fragments of text, possibly discontiguous or out of order</item><item>redundant encoding of information in multiple forms</item></list>
 
In the sections which follow, these techniques, their advantages, and
their disadvantages, are briefly described, and instances of their use
within these Guidelines are pointed out.  The examples show various
solutions to the problem of direct speech spanning several paragraphs in
a narrative; the text in question takes the following form:
 
<q rend="display"><p><q>The first thing that
put us out was that advertisement.  Spaulding, he came
down into the office just this day eight weeks with
this very paper in his hand, and he
says:&mdash;</q></p>
<p><q><q>I wish to the Lord, Mr. Wilson, that I was a red-headed
man.</q></q></p>
<p><q><q>Why that?</q> I asks.</q></p></q><!-- this doesnt sound like an exact quote to me! -->
 <!-- <note place=inline>[At the moment, these are just notes  --><!-- in list form.  With enough time, examples of how each    --><!-- technique can be applied to the list of sample problems  --><!-- will also be supplied.  With insufficient time,          --><!-- sporadic examples, or none, will be provided.  Each      --><!-- section now has a temporary list of how to treat each    --><!-- of the example problems.  -msm]</note>                   --></p><div2 id="NHCO" name="Anthony" ref="Y"><head>Concurrent Markup of Multiple Hierarchies</head><p>CONCUR allows us to mark up the document with many different
hierarchical structures, but not to reorder the tree or to have
different content in different views.  Note that the restriction against
having different content in different views is imposed not by SGML but
by the TEI Interchange Format.</p><p>For example, if quotations are marked as part of a distinct markup
stream given the name <q>QD</q>, the outermost speech in our
example need not be broken up into multiple elements:
 
<eg><![CDATA[<(QD)q who=Wilson> ...
<(TEI.2)p>The first thing that put us out was that
advertisement.  Spaulding, he came down into the
office just this day eight weeks with this very paper
in his hand, and he says:&mdash;</(TEI.2)p>
<(TEI.2)p><(QD)q who=Spaulding>I wish to the Lord, Mr.
Wilson, that I was a red-headed man.</(QD)q></(TEI.2)p>
<p><(QD)q who=Wilson>Why
that?</(QD)q> I asks.</(TEI.2)p>
 ... </(QD)q>]]></eg><!-- A C Doyle, Red headed league (but where?) -->
 <!-- <list type=gloss>                                        --><!-- <label>examples <item>                                   --><!-- <list type=bullets>                                      --><!-- <item>Red-Headed League example (Q in a separate hierarchy) --><!-- <item>Tweedledum and Tweedledee (syntax in separate hierarchy) --><!-- <item>vol page col line example (phys struc separate)    --><!-- <item>l vs sp:  with bibliographic reference to Barnard et al. --><!-- <item>embedded-text example (?  separate hierarchy for each level of --><!--         embedding, with does-not-apply tags to filter out the other --><!--         levels)                                          --><!-- <item>dictionary example (omit:  does not apply)         --><!-- </list>                                                  --></p><p>This method has the advantages of cleanly distinguishing among
separate logical hierarchies in the text, using the same structures as
non-concurrent markup and thus requiring no special conventions for use
(as the other methods described in this chapter do).  It has the
disadvantage of using a cumbersome notation, which means it could most
conveniently be used within an SGML-aware editing environment which
masks the complexity of the notation from the user; unfortunately,
CONCUR is an optional feature of SGML and is not supported by all SGML
processors.</p><p>The major use of concurrent markup in the current version of these
Guidelines is in the tag set for concurrent markup for pages, columns,
and lines defined elsewhere in this chapter.</p></div2><div2 id="NHMI" name="Anthony" ref="Y"><head>Boundary Marking with Milestone Elements</head><p>Milestones use empty elements to mark the beginnings and endings of
regions of the text which have something in common; they work like COCOA
tags.  Examples in these Guidelines include the <gi tei="yes">mileStone</gi>
element and the elements <gi tei="yes">pb</gi>, <gi tei="yes">lb</gi>, and <gi tei="yes">cb</gi>.</p><p>For example, if quotations are marked using (user-defined) empty
elements given the names <q>QB</q> and <q>QE</q>, then no element
contains the speeches and they need not be broken up into multiple
elements at the paragraph breaks:
 
<eg><![CDATA[<qb who=Wilson> ...
<p>The first thing that put us out was that
advertisement.  Spaulding, he came down into the
office just this day eight weeks with this very paper
in his hand, and he says:&mdash;</p>
<p><qb who=Spaulding>I wish to the Lord, Mr.
Wilson, that I was a red-headed man.<qe></p>
<p><qb who=Wilson>Why that?<qe> I asks.</p>
 ... <qe>]]></eg><!-- A C Doyle, Red headed league (but where?) --></p><p>This has the drawback that it is difficult to tell which
<gi tei="yes">qe</gi> corresponds with which <gi tei="yes">qb</gi> without a complex
processing of the text. One way to improve on this situation would be
to use the linking attribute <att tei="yes">corresp</att> discussed in chapter<xref target="SA"/>
 to associate the milestone indicating the end of a
given speech with that indicating its start, as follows:

 <!-- further discussion needed! --><!-- Elli notes that we should add id/idrefs to link QE with their --><!-- corresponding QBs in the above example. I agree, but not yet. -->
<!-- and LB obliges... -->

<eg><![CDATA[<qb who=Wilson id=W1> ...
<p>The first thing that put us out was that
advertisement.  Spaulding, he came down into the
office just this day eight weeks with this very paper
in his hand, and he says:&mdash;</p>
<p><qb who=Spaulding id=S1>I wish to the Lord, Mr.
Wilson, that I was a red-headed man.<qe corresp=S1></p>
<p><qb who=Wilson id=W2>Why that?<qe corresp=W2> I asks.</p>
 ... <qe corresp=W1>]]></eg><!-- A C Doyle, Red headed league (but where?) -->
 <!-- <list type=gloss><label>examples <item><list>            --><!-- <item>Red-Headed League example (P boundaries, or Q boundaries) --><!-- <item>Tweedledum and Tweedledee (LB instead of L)        --><!-- <item>vol page col line example (vb, pb, cb, lb)         --><!-- <item>l vs sp:  (lb?)                                    --><!-- <item>embedded-text example (not applicable)             --><!-- <item>dictionary example (not applicable)                --><!-- </list>                                                  --></p><p>This method has the advantage of simplicity; it provides all the
information needed to reconstruct all the competing hierarchical views
of the text.  Many times, the only processing required for an element
occurs at its start and end (or can easily be formulated to do so); this
markup method handles those cases well.  In other cases, however, this
method incurs the disadvantage of cumbersome processing:
since the elements of the analysis (e.g. the direct speech of Wilson)
are not uniformly represented by nodes in the document tree, they must
be reconstituted by software in an ad hoc fashion, which may be
difficult and is likely to be error prone.  Processing elements may
often involve more than specified actions at the start and end of an
element.  Most important for some encoders, this method disguises the
logical relationship between the beginning and the ending of each
logical element, making it impossible for SGML parsers to provide the
same kind of validation possible elsewhere in the encoding.</p></div2><div2 id="NHFR" name="Anthony" ref="Y"><head>Fragmentation of Elements</head><p>Fragmentation breaks up what might be considered a single element
into multiple smaller elements, in order to make it fit within the
hierarchy.  If a passage of direct discourse begins in the middle of one
paragraph and continues for several more paragraphs, for example, one
could encode the passage as a series of <gi tei="yes">q</gi> elements.  This has
the effect that the document contains more <gi tei="yes">q</gi> elements than it
did before; to the extent that one might be interested in counting
<gi tei="yes">q</gi> elements, this is a drawback.  To the extent that the element
being broken up is used primarily to signal some characteristic, (e.g.
that of being spoken by someone other than the narrator) rather than
some countable object, this drawback is rather minor.  Direct discourse
is in fact so frequently interrupted by narrative irruptions, including
but not limited to reporting clauses like <q>he said</q>, that the
number of <gi tei="yes">q</gi> elements is unlikely to correspond precisely to the
number of utterances, speaker turns, or any other observable unit of
conversation.  For that reason, some encoders prefer to solve
the quotation-and-paragraph problem using fragmentation.</p><p>To tag our example with this method, the outermost speech (Wilson's)
can be broken up to fit into the series of paragraphs, using the
<att tei="yes">rend</att> attribute to record the absence of closing quotation
marks at the end of each paragraph.  The inner speeches, being
punctuated conventionally, need not carry <att tei="yes">rend</att> values.
 
<eg><![CDATA[<p><q who=Wilson rend='pre ldquo'>The first thing that
put us out was that advertisement.  Spaulding, he came
down into the office just this day eight weeks with
this very paper in his hand, and he
says:&mdash;</q></p>
<p><q who=Wilson rend='pre ldquo'><q who=Spaulding>I
wish to the Lord, Mr. Wilson, that I was a red-headed
man.</q></q></p>
<p><q who=Wilson rend='pre ldquo'><q who=Wilson>Why
that?</q> I asks.</q></p>]]></eg><!-- A C Doyle, Red headed league (but where?) --></p><p>Among the places where these Guidelines recommend fragmentation as a
solution to the encoding of non-nesting information are the discussion
of fragmentary verse lines, fragmentary stanzas, and fragmentary
embedded texts in drama.</p><p>The advantages of this method are that it is simple, that at least
one of the competing hierarchies can be processed normally, and that
it makes the reconstitution of virtual units much easier, using the
method described in the next section.  Its disadvantages are that some
units are not realized at all in the markup (here, the single long
outermost speech of Wilson), and that automatic processing of these
units is thus impossible when this method is used without further
refinement.</p></div2><div2 id="NHVI" name="Anthony" ref="Y"><head>Reconstitution of Virtual Elements</head><p>Virtual joins may be used to indicate objects in the text which
would, for whatever reason, be difficult to mark using normal SGML
syntax.  In the TEI encoding scheme, virtual joins are most often
expressed by the <gi tei="yes">join</gi> element, the <gi tei="yes">span</gi> element, or
the <gi tei="yes">fs</gi> element.  This technique covers all out-of-line
annotation methods, which involve the construction, out of line, of a
clean structure representing the interpretation, and the virtual join of
the interpretation with the text fragment instantiating it.</p><p>The tagging of our example with this method is almost identical to
that given in the preceding section, with the addition of <gi tei="yes">join</gi>
elements to indicate the component parts of the individual speeches
which have been broken up to fit into the paragraph hierarchy:
 
<eg><![CDATA[<p><q id=QW1 who=Wilson rend='pre ldquo'>The first thing that
put us out was that advertisement.  Spaulding, he came
down into the office just this day eight weeks with
this very paper in his hand, and he
says:&mdash;</q></p>
<p><q id=QW2 who=Wilson rend='pre ldquo'><q who=Spaulding>I
wish to the Lord, Mr. Wilson, that I was a red-headed
man.</q></q></p>
<p><q id=QW3 who=Wilson rend='pre ldquo'><q who=Wilson>Why
that?</q> I asks.</q></p>
 
<!-- ... -->
<join targets='qw1 qw2 qw3' result='q'>]]></eg><!-- A C Doyle, Red headed league (but where?) --></p><p>Alternatively, the <att tei="yes">next</att> and <att tei="yes">prev</att> attributes
defined in chapter <xref target="SA"/> may be used to join the fragmentary
quotations:
 
<eg><![CDATA[<p><q id=QW1 next=qw2
      who=Wilson rend='pre ldquo'>The first thing that
put us out was that advertisement.  Spaulding, he came
down into the office just this day eight weeks with
this very paper in his hand, and he
says:&mdash;</q></p>
<p><q id=QW2 next=qw3 prev=qw1
      who=Wilson rend='pre ldquo'><q who=Spaulding>I
wish to the Lord, Mr. Wilson, that I was a red-headed
man.</q></q></p>
<p><q id=QW3 prev=qw2
      who=Wilson rend='pre ldquo'><q who=Wilson>Why
that?</q> I asks.</q></p>]]></eg><!-- A C Doyle, Red headed league (but where?) -->
 <!-- <list type=gloss><label>examples                         --><!-- <item>(unless otherwise indicated,                       --><!-- these are further refinements of examples in previous section) --><!-- <list>                                                   --><!-- <item>Red-Headed League example (add NEXT, PREV, or PART to Q; or --><!--         use JOIN)                                        --><!-- <item>Tweedledum and Tweedledee (as in chapter AI, use PART, NEXT; or --><!--         JOIN)                                            --><!-- <item>vol page col line example (? or omit?)             --><!-- <item>l vs sp:  fragmentary L elements, rejoined with PART --><!-- <item>embedded-text example (each fragment tagged as an element, --><!--         as in DR examples)                               --><!-- <item>dictionary example (?)                             --><!-- </list>                                                  --></p><p>The major advantage of this method is that it allows all the
hierarchies in the text to be handled explicitly, both
the privileged one directly represented in the SGML and the alternate
hierarchy which has been split up and rejoined.  Its major disadvantages
are that (like most of the other methods described here) it privileges
one hierarchy over the others, and requires special processing to
reconstitute the elements of the other hierarchies.</p><p>Instances of this markup method in these Guidelines include
the <att tei="yes">part</att> attribute on the <gi tei="yes">l</gi>, <gi tei="yes">lg</gi>,
<gi tei="yes">seg</gi>, and numbered-segment elements, the <gi tei="yes">join</gi>,
<gi tei="yes">span</gi>, and <gi tei="yes">fs</gi> elements, and the global <att tei="yes">next</att>
and <att tei="yes">prev</att> attributes available with the additional tag set for
linking and alignment.</p></div2><div2 id="NHRE" name="Anthony" ref="Y"><head>Multiple Encodings of the Same Information</head><p>In some cases, the simplest method of disentangling two conflicting
hierarchical views of the same information is to encode it twice, each
time capturing a single view.  Thus, for example, a dictionary headword
which gives in a single place the orthography, stress pattern,
syllabification, and hyphenation for a word might be encoded several
times:  once with all the information in a single notation (as in the
print dictionary), and once again for each separate piece of information
--- or at least, once more for the orthography, to speed up the common
operation of searching for the article for a given headword in the
electronic dictionary.</p><p>The out-of-line treatment of annotation in the feature structure
notation (defined in chapter <xref target="FS"/>) may also be considered
to fall under this rubric.</p><p>The advantages of this method of markup are that each way of looking
at the information is explicitly represented in the data, and may be
processed in straightforward ways, without requiring complex methods of
disentangling information relevant to one view from information relevant
only to other views.  It has the disadvantage of requiring more space
and of introducing redundant information into the encoding, with the
resulting risk that one view may be updated without corresponding
changes being made to the others, resulting in inconsistencies within
the document.  Excessive use of redundancy may also make it difficult to
reconstruct the exact form of the original source text.</p></div2><div2 id="NHRS" name="Anthony" ref="Y"><head>Concurrent Markup for Pages and Lines</head><p>Where the main purpose for encoding alternative hierarchies in
a text is to represent competing referencing schemes describing the
same basic text, the CONCUR mechanism of SGML provides a very natural
solution.
 <!-- I suggested cutting rest of this section but was overruled (LB) --><!-- ...    but not for long! --></p><p>One common form of traditional reference system specifies the page
and line, or page, column, and line of a passage as it appears in some
standard edition.  Such references may be specified using a concurrent
markup hierarchy which divides the body of a text into pages and lines
or into pages, columns, and lines.  Volumes may also need to be
identified.  The document type name should be a short identifier for the
edition cited.  The following tags may be used:
 
<tagList style="one-line"><tagDesc tagDoc="PLVOL"/><tagDesc tagDoc="PLPAGE"/><tagDesc tagDoc="PLCOL"/><tagDesc tagDoc="PLLINE"/></tagList></p><p>Page and line numbers for an edition by Lachmann, for example, might
be specified thus:
<eg><![CDATA[<(La)page n=37> <!-- Text from Lachmann, p. 37 -->
                ...
<(La)line n=32> <!-- Text from Lachmann, p. 37, line 32 -->
<(La)line n=33> <!-- Text from Lachmann, p. 37, line 33 -->
<(La)line n=34> <!-- Text from Lachmann, p. 37, line 34 -->
<(La)page n=38> <!-- Text from Lachmann, p. 38 -->
<(La)line n=1>  <!-- Text from Lachmann, p. 38, line 1 -->
<(La)line n=2>  <!-- Text from Lachmann, p. 38, line 2 -->
<(La)line n=3>  <!-- Text from Lachmann, p. 38, line 3 -->
 
                <!-- etc. -->
<(La)page n=39> <!-- Text from Lachmann, p. 39 --> ...
<(La)line n=18> <!-- Text from Lachmann, p. 39, line 18 -->
<(La)line n=21> <!-- Text from Lachmann, p. 39, line 21 -->
                <!-- etc. -->
<(La)page n=40> <!-- Text from Lachmann, p. 40 --> ...
                <!-- etc. -->
<(La)page n=41> <!-- Text from Lachmann, p. 41 --> ...
                <!-- etc. -->]]></eg></p><p>The markup shown above would be interleaved with the normal markup
for the document.  Since SGML requires tags in concurrent markup streams
to be labeled with their document type, however, the
<soCalled>normal</soCalled> markup would need to have the notation
<code tei="yes" type="frag">TEI.2</code> inserted before each tag's generic identifier.  The
combined markup might look something like this:
 
<eg><![CDATA[ <(TEI.2)TEI.2>
 <(TEI.2)TEI.Header> ... </(TEI.2)TEI.Header>
 <(TEI.2)text> ...
 <(TEI.2)div0><(TEI.2)head> ... </(TEI.2)head>
 ...
 <(TEI.2)div1>
 <(TEI.2)div2> ...
 <(La)page n=37> <!-- Text from Lachmann, p. 37 -->
                 ...
 <(La)line n=32> <!-- Text from Lachmann, p. 37, line 32 -->
 <(La)line n=33> <!-- Text from Lachmann, p. 37, line 33 -->
 <(La)line n=34> <!-- Text from Lachmann, p. 37, line 34 -->
 <(La)page n=38> <!-- Text from Lachmann, p. 38 -->
 <(La)line n=1>  <!-- Text from Lachmann, p. 38, line 1 -->
 <(La)line n=2>  <!-- Text from Lachmann, p. 38, line 2 -->
 <(La)line n=3>  <!-- Text from Lachmann, p. 38, line 3 -->
 </(TEI.2)div2>
 <(TEI.2)div2>
 <(La)line n=4>  <!-- Text from Lachmann, p. 38, line 4 -->
                 <!-- etc. -->
 </(TEI.2)div2>
 </(TEI.2)div1>
 <(TEI.2)div1><head>... </head>
                 ...
 <!-- Text from Lachmann, p. 39 --> ...
 <(La)page n=39> <!-- Text from Lachmann, p. 39 --> ...
 <(La)line n=18> <!-- Text from Lachmann, p. 39, line 18 -->
 <(La)line n=19> <!-- Text from Lachmann, p. 39, line 19 -->
 <(La)line n=20> <!-- Text from Lachmann, p. 39, line 20 -->
 <(La)line n=21> <!-- Text from Lachmann, p. 39, line 21 -->
                 ... <!-- etc. -->
 <(TEI.2)div1>
 <(TEI.2)div2>
 </(TEI.2)div2>
 <!-- etc. -->
 <!-- Text from Lachmann, p. 40 --> ...
 <!-- etc. -->
 </(TEI.2)text>
 </(TEI.2)TEI.2>]]></eg>
 
The following SGML declarations give the formal specification for the
standard pre-defined document type designed for recording page and line
numbers of a reference edition in a concurrent markup stream.
 
<dtdFrag id="DCORSC" n="Concurrent Document Type for Page and Line References" file="teipl2"><entDecl entDoc="VERSION"/><tagDecl tagDoc="VERNAME"/><tagDecl tagDoc="PLVOL"/><tagDecl tagDoc="PLPAGE"/><tagDecl tagDoc="PLCOL"/><tagDecl tagDoc="PLLINE"/></dtdFrag></p><p>This concurrent hierarchy is enabled as shown below:  after the
document type declaration for the TEI.2 document type, the document
should contain the sequence of lines:
 
<eg><![CDATA[    <!DOCTYPE La PUBLIC "-//TEI P3//DTD Concurrent Document Type:  
        Pages and Lines//EN"
       'teipl2.dtd' [
    <!ENTITY % version "La" >
    ]>]]></eg>
 
which call the document type for page and line references and give it
the name <q>La</q>.  If page and line numbers from more than one standard
edition are to be marked, then the relevant lines may be repeated, each
time using a different value for the document type and entity definition
(where the example has <q>La</q>).  For example, to show page and line
numbers from the editions of Lachmann (La), Kraus (Kr), and
Moser/Tervooren (MT) at the same time, one might use declarations like
the following:
 
 
<eg><![CDATA[    <!DOCTYPE La PUBLIC "-//TEI P3//DTD Concurrent Document Type:  
        Pages and Lines//EN"
       "teipl2.dtd" [
         <!ENTITY % version "La" >
    ]>
    <!DOCTYPE Kr PUBLIC "-//TEI P3//DTD Concurrent Document Type:  
        Pages and Lines//EN"
       "teipl2.dtd" [
         <!ENTITY % version "Kr" >
    ]>
    <!DOCTYPE MT PUBLIC "-//TEI P3//DTD Concurrent Document Type:  
        Pages and Lines//EN"
       "teipl2.dtd" [
         <!ENTITY % version "MT" >
    ]>]]></eg></p><p>To document a referencing system of this kind
the TEI header, a formal declaration should be provided
in the <gi tei="yes">refsDecl</gi> element described in section <xref target="HD54" type="div3"/>. For the above example, a declaration
such as the following would be appropriate:
 
<eg><![CDATA[<refsDecl n=La>
    <step dtd=La gi='page' att='n'>
    <step dtd=La gi='line' att='n'>
</refsDecl>
<refsDecl n=Kr>
    <step dtd=Kr gi='page' att='n'>
    <step dtd=Kr gi='line' att='n'>
</refsDecl>
<refsDecl n=MT>
    <step dtd=MT gi='page' att='n'>
    <step dtd=MT gi='line' att='n'>
</refsDecl>]]></eg></p><p>Hierarchies similar to that defined above can be provided for most
common hierarchical reference systems.  Hierarchies such as act / scene
/ line, for conventional dramatic structure, book / canto / stanza /
line, for longer verse texts, or book / poem / stanza / line, for
collections of verse, may be readily expressed with concurrent SGML
markup.  Since these hierarchical structures can readily be represented
using the base tag sets described in part III of these Guidelines,
however, reference systems with such structures may most readily be
expressed using the <att tei="yes">n</att> or <att tei="yes">id</att> attributes, as
described above in section <xref target="CORS1" type="div3"/>.</p><p>Any text with an idiosyncratic standard reference system will
require its own dtd, so that appropriately named tags can be created
for the reference units.  Such dtds may follow the pattern of those
described in the preceding section; they should also be documented in
an auxiliary tag set description file, using the tags described in
chapter <xref target="TD" type="div1"/>.</p></div2></div1><!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/p2odd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--><?tei:EOF p2nh.odd ??><!-- 31 Non-Hierarchical Phenom --><?tei:SOF p2cr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2cr.odd,v $
# Revision 1.7  1998/01/28  11:09:58  cmsmcq
# LB changes of January 1998
#
# Revision 1.6  1994/04/01  16:19:21  msmcq
# Title on single line (for Script's sake)
#
# Revision 1.5  1994/03/27  16:29:04  lou
# semifinal check
#
# Revision 1.2  1994/02/17  20:29:04  msmcq
# Used John Lavagnino's text.
# --><!-- Date: Thu, 10 Feb 1994 13:46:08 +0000                    --><!-- From: Lou Burnard <lou@vax.ox.ac.uk>                     --><!-- To: U35395@UICVM.UIC.EDU                                 --><!-- Subject: surprise surprise  - JL came thro with CR!      --><!-- P2.CR : Algorithm for Recognizing Canonical References   --><!-- Revisions:                                               --><!-- 17 jan 98 : LB refs.decls should be refsDecl passim --><!-- 94-03-31 : MSM : title on single line!                   --><!-- 94-02-15 : MSM : minor fixes, suppress percnt entity     --><!-- 94-02-15 : MSM : remove cover notes                      --><!-- 94-02-15 : MSM : Added RCS id                            --><!-- 94-02-09 :  JL : completely rewritten                    --><!-- 93-04-08 :  LK : scanned and tagged text                 --><!-- 93-04-07 : MSM : made file                               --><!-- 1993-04-06 : WP : found hard copy of old HD draft        --><div1 id="CR" n="32" name="Faisal" ref="Y"><head>Algorithm for Recognizing Canonical References</head><p>When a canonical reference is to be automatically processed
according to this method, the following occurs:
<list type="ordered"><item>The reference is analysed into a series of component
targets, using the <att tei="yes">delim</att> and <att tei="yes">length</att>
attributes on the <gi tei="yes">step</gi> elements within the relevant
<gi tei="yes">refsDecl</gi>, as described below. The target from the first
<gi tei="yes">step</gi> element is made available for use in the
subsequent pointer processing as %1, that from the second
as %2, and so on. The number of targets N must be noted,
as it will be used in later steps of the algorithm. (Targets
with numbers greater than N may be referenced, but they will be
null strings.)
 </item><item>Starting at the root of the tree (i.e. the <gi tei="yes">text</gi>
element, for a TEI-conformant document), a search is made
following the specifications of the pointer in the first
<gi tei="yes">step</gi> element: its <att tei="yes">from</att> and <att tei="yes">to</att>
attributes are processed exactly as would be done with an
<gi tei="yes">xptr</gi> element.
 </item><item>If there are more targets to be located, the search
continues by following the pointer specifications in the next
<gi tei="yes">step</gi> element, using as location source the span located
by the previous <gi tei="yes">step</gi>. Except for this special location
source, the processing is still identical to that done for an
<gi tei="yes">xptr</gi> element. (Note that this does not prevent an
expansion of the location source at any step, either by using
keywords such as <att tei="yes">previous</att> which search outside the
location source, or by an explicit return to <att tei="yes">root</att>.)
 </item><item>When N <gi tei="yes">step</gi> elements have been processed, the
search is complete. The final result of the reference is a point
or span of text, as with extended pointers.
 </item></list>
Note that there is no backtracking or other attempt at recovery
if a pointer fails. It is instead possible to design the
pointers so that backtracking is not necessary: see the final
example below.</p><p>When analyzing a reference into component targets, the following
procedure is adopted for each <gi tei="yes">step</gi> element that is
used:
<list type="ordered"><item>If only the <att tei="yes">length</att> attribute is specified,
exactly that number of characters is taken from the reference.
Entity references are resolved before characters are counted.
(This implies that references containing entity references may
behave differently on different systems.)
 </item><item>If only the <att tei="yes">delim</att> attribute was specified,
every character up to the next occurrence of the specified
delimiter is taken from the reference, and the delimiter itself
is removed.
 </item><item>If both <att tei="yes">length</att> and <att tei="yes">delim</att> attributes
are specified, a test is made for the presence of the delimiter
in the reference string immediately following the specified
number of characters; if this test fails, the reference fails.
 </item><item>If neither <att tei="yes">length</att> nor <att tei="yes">delim</att>
attribute is specified, the remainder of the reference string is
taken. This should happen only for the last <gi tei="yes">step</gi> in a
<gi tei="yes">refsDecl</gi>.
 </item><item>The number of components resulting from this procedure
must not exceed the number of steps in the associated
declaration, but may be less than it. (For example, a long poem
might be divided into cantos and lines, but a reference can
point to either a line in a canto or to a whole canto; a
reference to a whole canto would not require the <gi tei="yes">step</gi>
for the line number.)
 </item></list></p><p>Here is an example of how a reference system for an encoding of
the Bible could be specified:
<eg><![CDATA[<refsDecl>
 <step refunit="book" delim=" "
       from="CHILD (1 DIV N %1)"     to="DITTO">
 <step refunit="chapter" delim=":"
       from="CHILD (1 DIV N %2)"     to="DITTO">
 <step refunit="verse" delim=""
       from="CHILD (1 DIV N %3)"     to="DITTO">
</refsDecl>]]></eg>
With this reference declaration, a canonical reference of the
form <q>Matt 5:7</q> is processed by first searching for the
<gi tei="yes">div</gi> subelement of the <gi tei="yes">text</gi> element with an
<att tei="yes">n</att> attribute having value <code tei="yes" type="frag">Matt</code>; then searching
within that <gi tei="yes">div</gi> element for a <gi tei="yes">div</gi> subelement
with an <att tei="yes">n</att> attribute having value <code tei="yes" type="frag">5</code>; and
finally for a further nested <gi tei="yes">div</gi> element numbered
<code tei="yes" type="frag">7</code>. This example assumes that the unnumbered <gi tei="yes">div</gi>
elements nevertheless follow a predictable hierarchy: the first
level is always for books, the second for chapters, and the
third for verses. The following reference declaration would
allow intermediate <gi tei="yes">div</gi> elements of any sort, because it
would search at each step not only for the right <att tei="yes">n</att>
attribute but also for a <att tei="yes">type</att> attribute identifying
the structural type of the division:
<eg><![CDATA[<refsDecl>
 <step refunit="book" delim=" "
       from="DESCENDANT (1 DIV N %1 TYPE BOOK)"     to="DITTO">
 <step refunit="chapter" delim=":"
       from="DESCENDANT (1 DIV N %2 TYPE CHAPTER)"  to="DITTO">
 <step refunit=verse delim=""
       from="DESCENDANT (1 DIV N %3 TYPE VERSE)"    to="DITTO">
</refsDecl>]]></eg>
 </p><p>Other reference systems depend on markers such as page and line
numbers which do not correspond to structural divisions of the
text. These will typically be marked in the text by milestone
elements which identify single points in the text, rather than
by structural elements which contain the portion of the text to
be located. It is then necessary to construct extended pointers
in the reference declaration that can locate both the start and
the end of any segment. Here is a reference declaration for a
work whose reference system consists of page and line numbers:
for example, <q>93.3</q>.
<eg><![CDATA[<refsDecl>
 <step refunit=page delim="."
       from="FOLLOWING (1 PB N %1)"
       to="FOLLOWING (1 PB)">
 <step refunit=line delim=""
       from="FOLLOWING (1 LB N %2)"
       to="FOLLOWING (1 LB)">
</refsDecl>]]></eg>
To locate the specified page, the application must first search
for the first <gi tei="yes">pb</gi> element with <att tei="yes">n</att> equal to
<code tei="yes" type="frag">93</code>. It must then find the end of that page, which it does
by searching for the next <gi tei="yes">pb</gi> element after that for the
start of page 93; this should mark the start of page 94. A
similar procedure is used within the page to find the
<gi tei="yes">lb</gi> elements that mark the start and end of the desired
line.</p><p>A reference system may combine elements of the last two
approaches: a reference system based on line numbers is normally
used for early English plays, but because such plays often
combine prose and verse the line numbers sometimes refer to
structural elements (for verse passages) and sometimes to
arbitrary typographical boundaries (for prose). One could simply
fill the entire text with milestones, even in the verse passages
which do not require them; but a reference declaration can also
be constructed which requires no superfluous elements. Here is
such a declaration for a collection of plays, and for canonical
references of the form <q>Changeling 1.2.44</q>.
<eg><![CDATA[<refsDecl>
 <step refunit=work delim=" "
       from="DESCENDANT (1 TEXT N %1)"
       to="DITTO">
 <step refunit=act delim="."
       from="CHILD (1 DIV1 N %2)"
       to="DITTO">
 <step refunit=scene delim="."
       from="CHILD (1 DIV2 N %3)"
       to="DITTO">
 <step refunit=line delim=""
       from="FOLLOWING (1 (L|LB) N %4)"
       to="FOLLOWING (1 (L|LB))">
</refsDecl>]]></eg>
Instead of using the CHILD or DESCENDANT keywords to locate the
<gi tei="yes">l</gi> elements in verse passages, we use FOLLOWING, which
works to locate <gi tei="yes">lb</gi> elements as well.</p><p>The algorithm also allows ambiguity in the reference, as a
substitute for requiring backtracking in the processing.
Consider the following reference declaration for a text
containing several works:
<eg><![CDATA[<refsDecl>
 <step refunit=work delim=" "
       from="DESCENDANT (ALL TEXT N %1)" to="DITTO">
 <step refunit=book delim="."
       from="CHILD (1 DIV1 N %2)"        to="DITTO">
 <step refunit=poem delim="."
       from="CHILD (1 DIV2 N %3)"        to="DITTO">
 <step refunit=line delim=""
       from="CHILD (1 L N %4)"           to="DITTO">
</refsDecl>]]></eg>
Given the canonical reference <code tei="yes" type="frag">Amores I.2</code>, the application
will first search for all <gi tei="yes">text</gi> elements whose
<att tei="yes">n</att> attribute has the value <code tei="yes" type="frag">Amores</code>. This creates
a location source for the second step consisting of one or more
<gi tei="yes">text</gi> elements, possibly discontiguous; at the second
step, all the <gi tei="yes">div1</gi> elements numbered <code tei="yes" type="frag">I</code> within
those <gi tei="yes">text</gi> elements are selected. At the third, the
contained <gi tei="yes">div2</gi> elements numbered <code tei="yes" type="frag">2</code> are selected,
and the search ends because the reference string is exhausted:
it points to a whole poem, not to a single line. This reference
declaration is designed for use with a text that contains
several works, some of which might have the same name, so that
at the first step it is not adequate to search merely for the
first <gi tei="yes">text</gi> called <code tei="yes" type="frag">Amores</code>. It may be that several
works called <code tei="yes" type="frag">Amores</code> exist but only one has a book
numbered <code tei="yes" type="frag">I</code>, so that at the second step the location
source narrows down to the one work desired. In other approaches
to this problem, the works called <code tei="yes" type="frag">Amores</code> would be treated
one at a time, and if one turned out not to be the one desired
backtracking to previous steps of the search would be required;
this reference-processing method uses composite location sources
instead to eliminate the need for backtracking.</p></div1><?tei:EOF p2cr.odd ??><!-- 32 Canonical Refs --></div0><div0 id="P2.refs" n="7" name="Part" ref="Y"><head>Alphabetical Reference List of Tags and Attributes</head><?tei:SOF p2refs.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2refs.odd,v $
    * Revision 1.15  1998/01/31 18:32:23  tei
    * add fmchunk
    *
    * Revision 1.14  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.13  1994/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.12  1994/04/07  23:59:51  msmcq
    * add featureVal, singVal, cplxVal
    * 
    * Revision 1.11  1994/04/07  03:06:17  msmcq
    * alphabetize, add div1 elements.
    * 
    * Revision 1.10  1994/04/01  16:32:37  msmcq
    * changes during validation of DTD
    * 
    * Revision 1.9  1994/03/28  14:42:57  lou
    * add cldate and phent
    * 
    * Revision 1.7  1994/03/15  10:08:09  lou
    * Add globincl, ND etc
    * 
    * Revision 1.5  1994/02/17  20:31:08  msmcq
    * revision for SC review
    * 
    * Revision 1.3.1.1  1994/01/31  16:54:59  msmcq
    * Side branch, apparently the true correct version
    * --><!-- Revisions:                                               --><!-- 31 Jan 98 : LB : add fmchunk class --><!-- 8 Jan 98 : LB : add ab tag, typed class --><!-- 4 Jan 98 : LB : add editincl class --><!-- 94-04-08 : MSM : suppress dftcert, dftspok (dead global classes) --><!-- 94-04-08 : MSM : suppress chkseq (blind alley)           --><!-- 94-04-08 : MSM : suppress fsent (not used)               --><!-- 94-04-08 : MSM : add binary, boolean                     --><!-- 94-04-07 : MSM : merge two versions of this file         --><!-- 94-04-07 : MSM : add featureVal class                    --><!-- 94-04-07 : MSM : add cplxval, singleval                  --><!--               94-04-06 : MSM : alphabetize               --><!--               94-04-06 : MSM : add div1 groupings around classes, entities, elements --><!-- 94-04-06 : MSM : provide correct full names preparatory  --><!--                  to sorting (not done yet)               --><!-- 94-03-31 : MSM : add mixyes, mixno                       --><!-- 94-03-31 : MSM : add mixxx entities                      --><!-- 94-03-31 : MSM : add mix.BASE entities, for mixed base   --><!-- 94-03-31 : MSM : add ndent                               --><!-- 94-03-30 : MSM : add tcent ent                           --><!-- 94-03-30 : MSM : add dftdict                             --><!-- 94-03-30 : MSM : suppress perf class (inadvertent dup of compdram) --><!-- 94-03-30 : MSM : suppress lm classes, entities           --><!-- 94-03-30 : MSM : suppress ornament                       --><!-- 94-03-29 : MSM : suppress spoken.cla, clspoken (both vacuous) --><!-- 94-03-29 : MSM : include compspok                        --><!-- 94-03-29 : MSM : suppress clcert (vacuous)               --><!-- 94-03-29 : MSM : suppress skel                           --><!-- 94-03-29 : MSM : suppress CITY tag                       --><!-- 94-03-28 : MSM : suppress ceent                          --><!-- 28 mar: add cldate and phent --><!-- 94-03-13 : MSM : uppercase PLUS entity for tagdoc       --><!-- 94-03-13 : MSM : (avoid conflict with std entity name)   --><!-- 94-02-15 : MSM : suppress analysis tag                   --><!-- 94-02-03 : MSM : add fragmentary class                   --><!-- 94-02-03 : MSM : rename wits, wit / wit, witness         --><!-- 94-02-03 : MSM : add FT elements                         --><!-- 94-02-03 : MSM : additions to fix some idref gaps        --><!-- 94-02-01 : MSM : uppercase EQUIV entity for tagdoc       --><!-- 94-02-01 : MSM : (avoid conflict with std entity name)   --><!-- 94-02-01 : MSM : add di, expand many tag names properly for sorting --><!-- 94-02-01 : MSM : Add fs, fd                              --><!-- 94-02-01 : MSM : Suppress ditpno, whazzis?               --><!-- All tagdocs used by published chapters dec 93 --><div1 id="REFCLA" n="33" name="Faisal" ref="Y"><head>Element Classes</head><!-- Classes --><!-- &ditpno --><!-- &perf --><!-- &clcert --><!-- clcert class --><!-- &clspoken --><!-- clspoken class --><!-- &spoken  --><!-- spoken class --><?tei:SOF addrpart.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	addrpart.cla,v $
# Revision 1.1  94/01/04  13:18:04  lou
# Initial revision
#  --><!-- ************************************************** addrPart--><classDoc id="ADDRPART" type="model"><class>addrPart</class><name>address part</name><desc>defines a group of elements which may constitute a postal or
other form of address.</desc><attList></attList><remarks></remarks><part type="base" name="core"/><classes/><xref target="CONAAD"/></classDoc><?tei:EOF addrpart.cla ??><!-- addrPart class --><?tei:SOF agent.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	agent.cla,v $
# Revision 1.1  93/08/02  20:48:03  msmcq
# Initial revision
#  --><!-- $Header: //TEI/web/Vault/GL/P4/CanonizedOdds/Odds/p2odd.xml#1 $ --><!-- ************************************************** agent --><classDoc id="AGENT" type="model"><class>agent</class><name>agent (individual or corporate body)</name><desc>defines a group of elements which contain names of individuals
or corporate bodies.</desc><attList></attList><remarks><p>This class is used in the <gi tei="yes">resp</gi> element, to allow
a statement of responsibility to apply to an individual or a body.</p></remarks><part type="base" name="core"/><classes/><xref target="CONA"/></classDoc><?tei:EOF agent.cla ??><!-- agent class --><?tei:SOF dftana.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dftana.cla,v $
# Revision 1.1  93/09/15  23:02:26  msmcq
# Changes as of mid-September
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- ************************************************** clana --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : made DFT version                        --><!-- 93-09-13 : MSM : save under filename clana               --><classDoc id="DFTANA" type="atts"><class>analysis</class><desc>default declaration for class <term>analysis</term>:
when the additional tag set for simple analysis is not selected,
no attributes are defined for this class.</desc><attList></attList><part type="top" name="ling"/><classes/><xref target="STGA"/><xref target="AI"/></classDoc><?tei:EOF dftana.cla ??><!-- analysis class (default) --><?tei:SOF clana.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clana.cla,v $
# Revision 1.5  94/02/27  15:54:58  lou
# Revisions for publication of AI
# 
# Revision 1.4  1994/01/15  20:53:03  msmcq
# recast  DESC in connection with DI revisions.
#
# Revision 1.3  1993/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
#
# Revision 1.2  1993/09/22  18:54:40  msmcq
# suppress private remarks
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- ************************************************** clana --><!-- Revisions:                                               --><!-- 26 feb 94: move interp to clinterp --><!-- 94-01-15 : MSM : change DESC                             --><!-- 93-11-26 : MSM : clarify phrasing                        --><!-- 93-11-23 : MSM : drop old ana attributes, bring in ana, inst --><!-- 93-09-17 : MSM : suppress remark                         --><!-- 93-04-13 : MSM : save under filename clana               --><!-- 93-04-13 : MSM : rename: analysis not arrangement        --><!-- 8 Apr    : LB  drafted on model of cl.ana                --><classDoc id="CLANA" type="atts"><class>analysis</class><desc>defines global attributes for associating specific analyses or
interpretations with appropriate portions of a text, for use when the
additional tag set for simple analysis is selected.</desc><attList><!-- .................................................... ana --><attDef usage="opt"><attName>ana</attName><name>analysis</name><desc>indicates one or more elements containing interpretations of the
element on which the <att tei="yes">ana</att> attribute appears.</desc><datatype>IDREFS</datatype><valDesc>The SGML identifier of one or more interpretive elements
(usually <gi tei="yes">fs</gi> or <gi tei="yes">interp</gi>).</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>When multiple values are given, they may reflect either
multiple divergent interpretations of an ambiguous text, or multiple
mutually consistent interpretations of the same passage in different
contexts.</p></remarks></attDef><!-- inst attribute removed --></attList><part type="top" name="ai"/><classes/><xref target="AISP"/></classDoc><?tei:EOF clana.cla ??><!-- analysis class --><?tei:SOF basestd.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	basestd.cla,v $
# Revision 1.1  93/08/02  21:20:53  msmcq
# Initial revision
#  --><!-- ************************************************ basestd --><classDoc id="BASESTD" type="atts"><class>baseStandard</class><name>base-component standard</name><desc>groups elements in a writing system which refer to some public or
private standard as part of the basis for the writing system declaration</desc><attList><!-- ................................................... name --><attDef usage="req"><attName>name</attName><desc>gives the normal citation form for the standard being referred to.</desc><datatype>CDATA</datatype><valDesc>For national and international standards, the value
should be the normal citation form for the standard; for public entity
sets, it should be the standard public entity text; for private
character sets, WSDs, and entity sets, it is recommended that the
form of SGML <term>public identifiers</term> be used.</valDesc><default>#REQUIRED</default><eg><![CDATA[ < name='ANSI X3.4' authority='national'>
 < name='ISO 646: 1991' authority='ISO'>
 <entitySet    name='ISO 8879:1986//ENTITIES Added Latin 1//EN'
               authority='ISO'>
 <baseWsd      name='-//TEI P2: 1993//WSD ISO 8859-1//EN'
               authority='TEI'>]]></eg><remarks><p></p></remarks></attDef><!-- .............................................. authority --><attDef usage="req"><attName>authority</attName><desc>indicates the authority responsible for issuing the standard being
referred to:  the TEI, the International Organization for
Standardization (ISO), a national body, or a private body.</desc><datatype>(tei | iso | national | private | none)</datatype><valList type="closed"><val>tei </val><desc>the base writing system declaration is a standard WSD
issued by the Text Encoding Initiative</desc><val>iso </val><desc>the character set or entity set was issued by ISO</desc><val>national </val><desc>the character set or entity set was issued by a
national standards body</desc><val>private </val><desc>the writing system declaration, character set, or
entity set was issued publicly by a private organization or project</desc><val>none </val><desc>the writing system declaration, character set, or
entity set has not been publicly issued by any organization; it is
specific to an individual text or project</desc></valList><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><remarks><p></p></remarks><part type="aux" name="wsd"/><classes/><xref target="WDCSBA"/></classDoc><?tei:EOF basestd.cla ??><!-- baseStandard class --><?tei:SOF clbibl.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clbibl.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-06 : MSM : make bibl member of common              --><!-- 92-12-10 : MSM : add class affiliation                   --><classDoc id="CLBIBL" type="model"><class>bibl</class><desc>bibliographic elements. </desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="INTER COMMON"/><xref target="COBI"/></classDoc><?tei:EOF clbibl.cla ??><!-- bibl class --><?tei:SOF biblpart.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	biblpart.cla,v $
# Revision 1.2  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-04-06 : MSM : correct name (no dot)                   --><!-- 92-12-09 : MSM : change id to biblpart                   --><!-- 92-12-09 : MSM : made file                               --><!-- ********************************************** bibl.part --><classDoc id="BIBLPART" type="model"><class>biblPart</class><name>bibliographic citation part</name><desc>elements which can appear within bibliographic citations, but
cannot appear freely in running text outside bibliographic citations.</desc><attList></attList><remarks><p>This class is used in defining the content model of
<gi tei="yes">bibl</gi>.</p></remarks><part type="base" name="core"/><classes/><xref target="COBI"/></classDoc><?tei:EOF biblpart.cla ??><!-- biblPart class --><?tei:SOF binary.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	binary.cla,v $
# Revision 1.1  94/04/08  01:44:01  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : move from multval class to singval      --><!-- 94-04-07 : MSM : made file                               --><!-- ******************************************* binaryValue --><classDoc id="BINARY" type="model"><class>binary</class><name>binary feature-structure values</name><desc>elements which express binary values in feature structures.</desc><attList></attList><part type="top" name="fs"/><classes names="SINGVAL"/><xref target="FD"/></classDoc><?tei:EOF binary.cla ??><!-- binary class --><?tei:SOF boolean.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	boolean.cla,v $
# Revision 1.1  94/04/08  01:44:01  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : made file                               --><!-- ******************************************* booleanValue --><classDoc id="BOOLEAN" type="model"><class>boolean</class><name>Boolean values</name><desc>elements which express Boolean values in feature structures.</desc><attList></attList><part type="top" name="fs"/><classes names="SINGVAL"/><xref target="FD"/></classDoc><?tei:EOF boolean.cla ??><!-- boolean class --><!-- &dftcert --><!-- certainty class (default) --><?tei:SOF chunk.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	chunk.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-06 : MSM : add membership in class COMMON          --><!-- 92-12-10 : MSM : rename as chunk, not chunks             --><!-- 92-12-09 : MSM : revise (chunk <> interlevel)            --><!-- ***************************************************chunk --><classDoc id="CHUNK" type="model"><class>chunk</class><desc>includes all elements which can occur between, but not
within, paragraphs and other chunks.</desc><attList></attList><remarks><p>This element class does not contain all those elements which
can appear between chunks:  the class <term>inter</term> contains a
set of elements which can appear either within or between chunks.
Unlike elements of that class, chunks cannot occur within chunks.
In prose, this means the
elements in this class can appear between but not within paragraphs.</p></remarks><part type="base" name="core"/><classes names="COMMON"/><xref target="STEC"/></classDoc><?tei:EOF chunk.cla ??><!-- chunk class --><?tei:SOF common.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	common.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-06 : MSM : made file                               --><!-- ************************************************* common --><classDoc id="COMMON" type="model"><class>common</class><desc>common chunk- and inter-level elements.</desc><attList></attList><remarks><p>This class defines the set of chunk- and inter-level elements
available in all bases; it is used in defining the standard models
<term>chunk.seq</term> and <term>specialPara</term> in the general and
mixed bases.</p></remarks><part type="base" name="core"/><classes/><xref target="STEC"/></classDoc><?tei:EOF common.cla ??><!-- common class --><?tei:SOF compdict.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	compdict.cla,v $
# Revision 1.2  94/01/15  20:49:30  msmcq
# cmsmcq rev for P3
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-01-05 : MSM : lock                                    --><!-- 93-06-04 : MSM : made file                               --><!-- ******************************************** compdict    --><classDoc id="COMPDICT" type="model"><class>comp.dictionaries</class><desc>component-level elements unique to the base tag set
for dictionaries.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="term"/><classes/><xref target="DIBO"/><xref target="STEC"/></classDoc><?tei:EOF compdict.cla ??><!-- comp.dictionaries class --><?tei:SOF compdram.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	compdram.cla,v $
# Revision 1.2  93/12/20  16:39:03  lou
# changed id to match filename (not a very good idea)
# 
# Revision 1.1  1993/08/16  21:56:29  msmcq
# Initial revision
#
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 1993-08-07 : MSM : rename as comp.drama                  --><!-- ********************************** perf.cla --><classDoc id="COMPDRAM" type="model"><class>comp.drama</class><desc>component-level elements specific to performance texts.</desc><attList></attList><remarks></remarks><part type="base" name="perf"/><classes/><xref target="DR"/></classDoc><?tei:EOF compdram.cla ??><!-- comp.drama class --><?tei:SOF compspok.cla ??><!-- Revisions:                                               --><!-- 94-03-29 : MSM : suppress membership in class inter (testing ...) --><!-- 94-03-29 : MSM : correct ID                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	compspok.cla,v $
# Revision 1.3  94/04/01  17:34:39  msmcq
# Changes during validation of DTD
# 
# Revision 1.2  1993/09/24  08:36:38  lou
# added to inter class
#
# Revision 1.1  1993/09/23  09:34:33  lou
# Initial revision
#
# Revision 1.1  1993/09/21  11:09:12  lou
# Initial revision
# --><!-- 20 sep 93 LB : made file                               --><!-- ************************************************** spoken --><classDoc id="COMPSPOK" type="model"><class>comp.spoken</class><desc>elements appearing in spoken texts only.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="spoken"/><classes/><xref target="TSOV"/></classDoc><?tei:EOF compspok.cla ??><!-- comp.spoken class --><?tei:SOF compterm.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	compterm.cla,v $
# Revision 1.3  93/09/16  15:02:32  msmcq
# change ID to agree with filename
# 
# Revision 1.2  1993/08/13  20:50:31  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : change ID to agree with filename        --><!-- 93-03-29 : MSM : new name:  add 'comp.' to 'terminology' --><!-- 92-12-23 : MSM : correct class name                      --><!-- ******************************************** terminology --><classDoc id="COMPTERM" type="model"><class>comp.terminology</class><desc>component-level elements unique to the base tag set
for terminological data.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="term"/><classes/><xref target="TEBA"/><xref target="STEC"/></classDoc><?tei:EOF compterm.cla ??><!-- comp.terminology class --><?tei:SOF compvers.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $  --><!-- $Log:	compvers.cla,v $
# Revision 1.1  93/08/11  13:00:52  lou
# Initial revision
#  --><!-- 8 Aug 93 : LB : made file                               --><!-- ************************************************* compvers --><classDoc id="COMPVERS" type="model"><class>comp.verse</class><desc>component level elements unique to the base tag set for verse.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="verse"/><classes/><xref target="VEST"/><xref target="STEC"/></classDoc><?tei:EOF compvers.cla ??><!-- comp.verse class --><?tei:SOF cplxval.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cplxval.cla,v $
# Revision 1.1  94/04/08  01:44:01  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class featval                    --><!-- 94-04-07 : MSM : made file                               --><!-- ************************************************ cplxVal --><classDoc id="CPLXVAL" type="model"><class>complexVal</class><name>complex values</name><desc>elements which express complex feature values in feature
structures.</desc><attList></attList><part type="top" name="fs"/><classes names="FEATVAL"/><xref target="FD"/></classDoc><?tei:EOF cplxval.cla ??><!-- complexVal class --><?tei:SOF data.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	data.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : assign to class PHRASE                  --><classDoc id="DATA" type="model"><class>data</class><desc>phrase-level elements containing names, dates, numbers, measures,
and similar data. </desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="PHRASE"/><xref target="CONA"/></classDoc><?tei:EOF data.cla ??><!-- data class --><?tei:SOF cldate.cla ??><!-- Revisions:                                               --><!-- 94-03-28 : MSM : rename from date.cla                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cldate.cla,v $
# Revision 1.2  94/04/01  17:34:39  msmcq
# Changes during validation of DTD
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- *************************************************** date --><classDoc id="CLDATE" type="model"><class>date</class><name>dates and date ranges</name><desc>defines a class of elements containing date specifications.</desc><attList></attList><remarks><p>This class allows certain content models to allow either
a single date or a date-range element.</p></remarks><part type="base" name="core"/><classes/><xref target="CONA"/></classDoc><?tei:EOF cldate.cla ??><!-- date class --><?tei:SOF declabl.cla ??><!-- Revisions:                                               --><!-- 93-11-18 : MSM : fix bad xref break (trivial)            --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	declabl.cla,v $
# Revision 1.2  93/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><classDoc id="DECLABL" type="atts"><class>declarable</class><desc>elements which may be independently selected (using the special
purpose <att tei="yes">decls</att> attribute) from a candidate list of declarations
within a TEI header.</desc><attList><attDef usage="mwa"><attName>default</attName><desc>indicates whether or not this element is selected by default when
its parent is selected.</desc><datatype>(YES|NO)</datatype><valList type="open"><val>YES</val><desc>This element is selected if its parent is selected</desc><val>NO</val><desc>This element can only be selected explicitly, unless it is the
only one of its kind, in which case it is selected if its parent is selected.</desc></valList><default>NO</default></attDef></attList><remarks><p>The rules governing the association of declarable elements
with individual parts of a TEI text are fully defined in
chapter <xref target="CCAS"/>.
Only one element of a particular type may carry the value
<att tei="yes">default=yes</att>.</p></remarks><part type="aux" name="hdr"/><classes/><xref target="CCAS"/></classDoc><?tei:EOF declabl.cla ??><!-- declarable class --><?tei:SOF decling.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	decling.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- ****************************************************decling.cla --><classDoc id="DECLING" type="atts"><class>declaring</class><desc>groups elements which may be independently associated with a
particular declarable element within the header, thus overriding the
inherited default for that element.</desc><attList><attDef usage="mwa"><attName>decls</attName><desc>identifies one or more <term>declarable elements</term> within the
header, which are understood to apply to the element bearing this
attribute and its content.</desc><datatype>IDREFS</datatype><valDesc>must identify a set of declarable elements of different
types. </valDesc><default>#IMPLIED</default></attDef></attList><remarks><p>The rules governing the association of declarable elements
with individual parts of a TEI text are fully defined in chapter <xref target="CCAS"/>.</p></remarks><part type="aux" name="hdr"/><classes/><xref target="CCAS"/></classDoc><?tei:EOF decling.cla ??><!-- declaring class --><?tei:SOF demog.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	demog.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- **************************************CLASSES****************** --><classDoc id="DEMOG" type="model"><class>demographic</class><desc>elements describing demographic characteristics of the participants
in a linguistic interaction.</desc><attList></attList><remarks><p></p></remarks><part type="aux" name="hdr"/><classes/><xref target="CCAHPA"/></classDoc><?tei:EOF demog.cla ??><!-- demographic class --><?tei:SOF diglobal.cla ??><!-- Revisions:                                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: diglobal.cla,v $
    * Revision 1.6  1998/01/31 17:18:34  tei
    * fix log keyword problem
    *
    * Revision 1.5  1998/01/30 16:47:49  tei
    * fix odd comment problems
    *
    * Revision 1.4  98/01/30  16:42:04  tei
    * added LOCATION attribute
    * 
    * Revision 1.3  1994/04/07 02:49:28  msmcq
    * Misc. cleanups (mostly suppressed remarks)
    *
    * Revision 1.2  1994/04/01  17:34:39  msmcq
    * Changes during validation of DTD
    * 
    * Revision 1.1  1993/08/02  21:21:23  msmcq
    * Initial revision
    *--><!-- 30 jan 98: LB : add LOCATION attribute                   --><!-- 94-04-06 : MSM : suppress empty remarks elements         --><!-- 94-04-06 : MSM : suppress non-publishable remarks        --><!-- 94-03-30 : MSM : change DESC (not global anymore)        --><!-- ******************************************* dictionaries --><classDoc id="DIGLOBAL" type="atts"><class>dictionaries</class><desc>defines global attributes available on elements in the base
tag set for dictionaries.</desc><attList><!-- ................................................. expand --><attDef usage="opt"><attName>expand</attName><desc>gives an expanded form of information presented more concisely in
the dictionary</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p></remarks>                                   --></attDef><!-- ................................................... norm --><attDef usage="opt"><attName>norm</attName><desc>gives a normalized form of information given by the source text in
a non-normalized form</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p></remarks>                                   --></attDef><!-- .................................................. split --><attDef usage="opt"><attName>split</attName><desc>gives the list of split values for a merged form</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p></remarks>                                   --></attDef><!-- .................................................. value --><attDef usage="opt"><attName>value</attName><desc>gives a value which lacks any realization in the printed source
text.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p></remarks>                                   --></attDef><!-- ................................................... orig --><attDef usage="opt"><attName>orig</attName><name>original</name><desc>gives the original string or is the empty string when the element
does not appear in the source text.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p>[This name will lead to name conflicts       --><!-- with the core <gi>reg</gi> element; must be changed.     --><!-- Description needs work.  -Ed.]</remarks>                 --></attDef><!-- ............................................... location --><attDef usage="opt"><attName>location</attName><desc>provides a reference to an <gi tei="yes">anchor</gi> element elsewhere in
the
document indicating the original location of this component.</desc><datatype>IDREF</datatype><valDesc>the SGML identifier of an <gi tei="yes">anchor</gi> element</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p>[Description needs work; I don't know what   --><!-- this means. -Ed.]</remarks>                              --></attDef><attDef usage="opt"><attName>mergedin</attName><desc>gives a reference to another element, where the original appears
as a merged form.</desc><datatype>IDREF</datatype><valDesc>the SGML identifier of any element</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p>[Description needs work; I don't know what   --><!-- this means. -Ed.]</remarks>                              --></attDef><!-- .................................................... opt --><attDef usage="opt"><attName>opt</attName><name>optional</name><desc>indicates whether the element is optional or not</desc><datatype>(y | n)</datatype><valDesc>any string of characters</valDesc><default>n</default><eg><![CDATA[<form>
  <orth id=O1 next=o2>thyr</orth>
  <orth id=O2 prev=o1 next=o3 opt=y>&eacute;</orth>
  <orth id=O3 prev=o2>ostimuline</orth>
 
  <pron id=P1 next=p2>tiR</pron>
  <pron id=P2 prev=p1 next=p3 opt=y>e</pron>
  <pron id=P3 prev=p2>ostimylin</pron>
</form>]]></eg><!-- <remarks><p></remarks>                                   --></attDef></attList><!-- <remarks><p>[Proposed <att>rendition</att> attribute     --><!-- suppressed as redundant with global <att>rend</att>.     --><!-- -Ed.]                                                    --><part type="base" name="dict"/><classes/><xref target="DIEN" type="div3"/></classDoc><?tei:EOF diglobal.cla ??><!-- dictionaries class --><?tei:SOF dftdict.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dftdict.cla,v $
# Revision 1.1  94/04/01  17:33:00  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : correct xref target                     --><!-- 94-03-30 : MSM : made file                               --><!-- 94-03-30 : MSM : made file from dftterm                  --><!-- **********************************dft dictionaries class --><classDoc id="DFTDICT" type="atts"><class>dictionaries</class><name>attributes for dictionary elements.</name><desc>default declaration for class <term>dictionaries</term>:
when the base tag set for dictionaries is not selected,
no attributes are defined for this class.</desc><attList></attList><part type="base" name="term"/><classes/><xref target="TEDTF"/></classDoc><?tei:EOF dftdict.cla ??><!-- dictionaries class --><?tei:SOF diparts.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	diparts.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- **************************************** dictionaryParts --><classDoc id="DIPARTS" type="model"><class>dictionaryParts</class><name>dictionary parts</name><desc>groups all elements defined specifically for dictionaries.</desc><attList></attList><remarks><p> (optional)</p></remarks><part type="base" name="dict"/><classes/><xref target="DIBO" type="div3"/></classDoc><?tei:EOF diparts.cla ??><!-- dictionaryParts class --><?tei:SOF ditoplev.cla ??><!-- Revisions:                                               --><!-- 94-04-06 : MSM : suppress project-internal remarks       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ditoplev.cla,v $
# Revision 1.2  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- ************************************* dictionaryTopLevel --><classDoc id="DITOPLEV" type="model"><class>dictionaryTopLevel</class><name>dictionary top-level elements</name><desc>groups elements which can appear at the <soCalled>top
level</soCalled> in dictionary entries.</desc><attList></attList><!-- <remarks><p>[Description may need changing; this was     --><!-- inferred from the name, but in fact these elements       --><!-- appear at any level.  Perhaps name should be changed     --><!-- instead; this appears nearly synonymous with the old     --><!-- <term>dgroups</term> class. -Ed.]                        --><part type="base" name="dict"/><classes/><xref target="DIEN" type="div3"/></classDoc><?tei:EOF ditoplev.cla ??><!-- dictionaryTopLevel class --><?tei:SOF divbot.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	divbot.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- ************************************************* divbot.cla --><classDoc id="DIVBOT" type="model"><class>divbot</class><name>Bottom-of-division elements</name><desc>groups elements which can occur at the end of a
text division; for example, trailer, byline, etc.</desc><attList></attList><part type="base" name="core"/><classes/><xref target="DSDTB"/></classDoc><?tei:EOF divbot.cla ??><!-- divbot class --><?tei:SOF divn.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	divn.cla,v $
# Revision 1.4  94/03/15  11:10:31  lou
# minor typos etc
# 
# Revision 1.3  1993/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
#
# Revision 1.2  1993/08/11  13:01:23  lou
# changes for compatibility with VE
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                                  --><!-- 93-11-18 : MSM : fix Script problem in long deletion     --><!-- 12 aug 93: LB : changed semantics of part; added sample;
                     removed complete                               --><!-- 93-04-06 : MSM : correct desc                               --><!-- ************************************************* divn.cla --><classDoc id="DIVN" type="atts"><class>divn</class><desc>structural elements which behave in the same way as divisions.</desc><attList><attDef usage="rec"><attName>type</attName><desc>specifies a name conventionally used
for this level of subdivision, e.g. <q>act</q>,
<q>volume</q>, <q>book</q>, <q>section</q>, <q>canto</q>, etc.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#CURRENT</default></attDef><attDef usage="opt"><attName>org</attName><desc>specifies how the content of the division is organized.</desc><datatype>(composite | uniform)</datatype><valList type="closed"><val>composite</val><desc>composite content: i.e. no claim is
made about the sequence in which the immediate contents of this
division are to be processed, or their inter-relationships.</desc><val>uniform</val><desc>uniform content: i.e. the immediate contents
of this element are regarded as forming a logical unit,
to be processed in sequence.</desc></valList><default>uniform</default></attDef><attDef usage="opt"><attName>sample</attName><desc>indicates whether this division is a sample of the original source
and if so, from which part.</desc><datatype>(initial | medial | final | unknown | complete)</datatype><valList type="closed"><val>initial</val><desc>division lacks material present at end in source.</desc><val>medial</val><desc>division lacks material at start and end.</desc><val>final</val><desc>division lacks material at start.</desc><val>unknown</val><desc>position of sampled material within original unknown.</desc><val>complete</val><desc>division is not a sample.</desc></valList><default>complete</default><remarks></remarks></attDef><attDef usage="mwa"><attName>part</attName><desc>specifies whether or not the division is fragmented by some other
structural element, for example a speech which is divided between two
or more verse stanzas.</desc><datatype>(Y | N | I | M | F)</datatype><valList type="closed"><val>Y</val><desc>the division is incomplete in some respect</desc><val>N</val><desc>either the division is complete, or no claim is made as to
its completeness.</desc><val>I</val><desc>the initial part of an incomplete division</desc><val>M</val><desc>a medial part of an incomplete division</desc><val>F</val><desc>the final part of an incomplete division</desc></valList><default>N</default><remarks><p>The values I, M, or F should be used only where it is
clear how the division is to be reconstituted.</p></remarks></attDef><!-- LB  revised part and complete                            --><!-- < attdef usage=opt >  < attname > complete               --><!-- < desc > specifies whether or not this division          --><!-- is complete with respect to the original source.         --><!-- < datatype > (YES | NO)                                  --><!-- < vallist type=closed >                                  --><!-- < val > YES < desc > the full text of the original has   --><!-- been transcribed.                                        --><!-- < val > NO < desc > a sample of the original text has    --><!-- been transcribed.                                        --><!-- < /vallist >                                             --><!-- < default > YES                                          --><!-- < /attdef >                                              --><!-- < attdef >                                               --><!-- < attname > part                                         --><!-- < name > part                                            --><!-- < desc > indicates from which part of the original       --><!-- source the division has been extracted in the case of    --><!-- a sampled division.                                      --><!-- < /desc >                                                --><!-- < datatype > (initial | medial | final | unknown | complete) --><!-- < vallist type=closed >                                  --><!-- < val > initial < desc > division lacks material at end. --><!-- < val > medial < desc > division lacks material at       --><!-- start and end.                                           --><!-- < val > final < desc > division lacks material at start. --><!-- < val > unknown < desc > position of sampled material    --><!-- within original unknown.                                 --><!-- < val > complete < desc > division is not a sample.      --><!-- < /vallist >                                             --><!-- < default > #IMPLIED                                     --><!-- < /attDef >                                              --><!--                                                          --></attList><part type="base" name="core"/><classes/><xref target="DS"/></classDoc><?tei:EOF divn.cla ??><!-- divn class --><?tei:SOF divtop.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: divtop.cla,v $
    * Revision 1.3  1998/01/31 19:09:48  tei
    * fix log keyword
    *
    * Revision 1.2  1998/01/31 18:28:30  tei
    * *** empty log message ***
    * 
    * Revision 1.1  93/08/02  21:21:23  msmcq
    * Initial revision
    *--><!-- ************************************************* divtop.cla --><classDoc id="DIVTOP" type="model"><class>divtop</class><name>top-of-div elements</name><desc>groups elements which can occur at the start of a
text block:  head, epigraph, byline, etc.</desc><attList></attList><part type="base" name="core"/><classes/><xref target="DSDTB"/></classDoc><?tei:EOF divtop.cla ??><!-- divtop class --><?tei:SOF drfront.cla ??><!-- DramaFront class --><!-- Revisions:                                               --><!-- 93-08-16 : MSM : part = drama, not front                 --><!-- 93-08-07 : MSM : rename with clearer name                --><!-- 93-06-04 : MSM : parent class is clfront not front       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drfront.cla,v $
# Revision 1.5  93/08/16  21:56:29  msmcq
# tweaks / revisions for publication of DR
# 
# Revision 1.4  1993/08/13  20:50:31  msmcq
# Clean ^Z
#
# Revision 1.3  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.2  1993/08/02  21:32:26  msmcq
# change parent class to clfront, not front
# --><!-- ********************************** drfront.cla --><classDoc id="DRFRONT" type="model"><class>dramafront</class><desc>elements which appear at the level of divisions within front or
back matter of performance texts only.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="perf"/><classes names="CLFRONT"/><xref target="DRFAB"/></classDoc><?tei:EOF drfront.cla ??><!-- dramafront class --><?tei:SOF edit.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	edit.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : assign to class PHRASE                  --><classDoc id="EDIT" type="model"><class>edit</class><desc>phrase-level elements for simple editorial correction and
transcription. </desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="PHRASE"/><xref target="COED"/></classDoc><?tei:EOF edit.cla ??><!-- edit class --><?tei:SOF editincl.cla ??><!-- Revisions: --><!-- 4 Jan 98: LB : Made file  --><!-- ************************************************** editincl --><classDoc id="EDITINCL" type="model"><class>editIncl</class><desc>empty elements which perform a specifically editorial function, for
example by indicating the start of a 
span of text added, deleted, or missing in a source,  
and which may appear at any point in a document.</desc><attList></attList><remarks><p>Members of this class can appear anywhere within a document,
between or within components or phrases. </p></remarks><part type="base" name="core"/><classes names="GLOBINCL"/><xref target="STEC"/><!-- need more precise xref --></classDoc><?tei:EOF editincl.cla ??><?tei:SOF editph.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	editph.cla,v $
# Revision 1.2  94/03/08  03:42:23  msmcq
# correct ID
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-03-07 : MSM : correct ID                              --><!-- 94-03-04 : MSM : add clarifying remarks on duplication of class --><!-- 94-01-27 : MSM : add attributes                          --><!-- 92-12-09 : MSM : assign to class PHRASE                  --><classDoc id="EDITPH" type="both"><class>edit</class><desc>phrase-level elements for simple editorial correction and
transcription. </desc><attList><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for the salient
information conveyed by a particular tag:  the hand of an addition or
deletion, the expansion of an abbreviation, the correction of an
apparent error, the regularization of a non-standard form, the
transcription of unclear material, or the decision not to transcribe
some portion of the text.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg><remarks><p>As noted, the precise type of responsibility exercised by
the individual named in the attribute varies with the particular
element type.  Responsibility for other aspects of the markup may be
recorded using the methods described in chapter <xref target="CE"/>.</p></remarks></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to some specific
aspect of the markup:
the identification of the hand of an addition or deletion,
the correctness of the expansion of an abbreviation, the correction
of an error, or the regularization of a non-standard form; or the
correctness of the transcription of unclear material.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><remarks><p>This version of this class is used only when the
additional tag set for transcription of primary sources is used.</p></remarks><part type="base" name="core"/><classes names="PHRASE"/><xref target="PHCO"/></classDoc><?tei:EOF editph.cla ??><!-- edit class --><?tei:SOF enjamb.cla ??><!-- Revisions:                                               --><!-- 13 mar 94: zap empty exemplum --><!-- 93-11-21 : MSM : change from semi to open                --><!-- 93-11-18 : MSM : change from closed to semi-open list    --><!-- ************************************************* enjamb --><classDoc id="ENJAMB" type="atts"><class>enjamb</class><name>enjambement</name><desc>elements bearing the <att tei="yes">enjamb</att> attribute.</desc><attList><!-- ................................................. enjamb --><attDef usage="opt"><attName>enjamb</attName><name>enjambement</name><desc>indicates that the end of a verse line is marked by enjambement.</desc><datatype>CDATA</datatype><valList type="open"><val>no </val><desc>the line is end-stopped
    </desc><val>yes </val><desc>the line in question runs on into the next
    </desc><val>weak </val><desc>the line is weakly enjambed
    </desc><val>strong </val><desc>the line is strongly enjambed</desc></valList><default>#IMPLIED</default><remarks><p>The usual practice will be to give the value <q>y</q> to
this attribute when enjambement is being marked, or the values
<q>weak</q> and <q>strong</q> if degrees of enjambement are of interest;
if no value is given, however, the attribute does not default to a value
of <q>no</q>; this allows the attribute to be omitted entirely when
enjambement is not of particular interest.</p></remarks></attDef></attList><part type="base" name="verse"/><classes/><xref target="VESE"/></classDoc><?tei:EOF enjamb.cla ??><!-- enjamb class --><?tei:SOF entries.cla ??><!-- Revisions:                                               --><!-- 94-03-30 : MSM : double quote default                    --><!-- 4 mar: changed degenerate to reduced to please stig --><!-- 93-10-19 : MSM : change wording of key                   --><!-- 93-10-19 : MSM : make vallist for type be semi not open  --><!-- 93-10-19 : MSM : remove hn (dup of global n)             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	entries.cla,v $
# Revision 1.4  94/04/01  17:34:39  msmcq
# Changes during validation of DTD
# 
# Revision 1.3  1994/03/15  11:10:33  lou
# minor typos etc
#
# Revision 1.2  1994/01/04  00:19:36  msmcq
# periodic checkin.  DI not finished.
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- ************************************************ entries --><classDoc id="ENTRIES" type="atts"><class>entries</class><name>dictionary entries</name><desc>groups the different styles of dictionary entries.</desc><attList><!-- ................................................... type --><attDef usage="rwa"><attName>type</attName><desc>indicates type of entry, in dictionaries with multiple types.</desc><datatype>CDATA</datatype><valList type="semi"><val>main</val><desc>a main entry (default).</desc><val>hom </val><desc>a homograph with a separate entry.</desc><val>xref</val><desc>a reduced entry whose only function is to point to another main
entry (e.g. for forms of an irregular verb or for variant spellings:
<cited>was</cited> pointing to <cited>be</cited>, or
<cited>esthete</cited> to <cited>aesthete</cited>).</desc><val>affix</val><desc>an entry for a prefix, infix, or suffix.</desc><val>abbr</val><desc>an entry for an abbreviation.</desc><val>supplemental</val><desc>a supplemental entry (for use in dictionaries which issue
supplements to their main work in which they include updated information
about entries).</desc><val>foreign</val><desc>an entry for a <soCalled>foreign</soCalled> word in a monolingual
dictionary.</desc></valList><default>"main"</default></attDef><!-- .................................................... key --><attDef usage="opt"><attName>key</attName><name>sort key</name><desc>contains a (sortable) character sequence reflecting
the entry's alphabetical position in the printed dictionary.</desc><datatype>CDATA</datatype><valDesc>any sequence of characters which, when sorted with the
other values, will produced the desired order; specifics of key
construction are application-dependent.</valDesc><default>#IMPLIED</default><remarks><p>Dictionary order often differs from the collation sequence
of machine-readable character sets; in English-language dictionaries, an
entry for <cited>4-H</cited> will often appear alphabetized under
<q>fourh</q>, and <cited>McCoy</cited> may be alphabetized under
<q>maccoy</q>, while <cited>A1</cited>, <cited>A4</cited>, and
<cited>A5</cited> may all which all appear in numeric order
<soCalled>alphabetized</soCalled> between <q>a-</q> and <q>AA</q>.<!--
<note place=foot>[We should probably refer here to the Canadian standard
on sort order and possibly to the IBM manual on sorting for culturally
expected results.  References in the logs of ISO10646 and ISO8859.
-MSM]</note>
-->
The sort key is required if the orthography of the dictionary entry does
not suffice to determine its location.</p></remarks></attDef><!-- ..................................................... hn --><!--  < attDef usage=opt >                                    --><!--  < attname > hn                                          --><!--  < name > homograph number                               --><!--  < desc > indicates the homograph number (for            --><!-- homograph entries only)                                  --><!--  < datatype > CDATA                                      --><!--  < valdesc > any string of characters, typically one     --><!-- or more numeric digits.                                  --><!--  < default > #IMPLIED                                    --><!--  < eg >  < ![ CDATA [                                    --><!--                                                          --><!-- ]] >                                                     --><!--  < /eg >                                                 --><!-- < remarks >  < p > [This would appear to fill the same   --><!-- function as the global attribute  < att > n < /att > .   --><!-- Is there another expected use for < att > n < /att >     --><!-- which would prevent its use for homograph numbers?  If   --><!-- not, this should perhaps be dropped, with a note that    --><!-- homograph numbers should be encoded using  < att > n <   --><!-- /att > . -MSM]                                           --><!--  < /attDef >                                             --></attList><remarks><p>The global <att tei="yes">n</att> attribute should be used to encode
the homograph numbers attached to entries for homographs.</p></remarks><part type="base" name="dict"/><classes/><xref target="DIBO"/><xref target="DIEN"/></classDoc><?tei:EOF entries.cla ??><!-- entries class --><?tei:SOF featval.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	featval.cla,v $
# Revision 1.1  94/04/08  01:44:01  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : made file                               --><!-- 94-04-07 : MSM : made file                               --><!-- ************************************************ featVal --><classDoc id="FEATVAL" type="model"><class>featureVal</class><name>feature values</name><desc>elements which express feature values in feature structures.</desc><attList></attList><part type="top" name="fs"/><classes/><xref target="FD"/></classDoc><?tei:EOF featval.cla ??><!-- featureVal class --><?tei:SOF forminfo.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	forminfo.cla,v $
# Revision 1.1  94/01/15  20:49:30  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-01-12 : MSM : made file                               --><!-- *********************************************** formInfo --><classDoc id="FORMINFO" type="model"><class>formInfo</class><name>form information</name><desc>elements allowed within a <gi tei="yes">form</gi> element in a dictionary.</desc><attList></attList><part type="base" name="di"/><classes/><xref target="DITPFO"/></classDoc><?tei:EOF forminfo.cla ??><!-- formInfo class --><?tei:SOF fmchunk.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:
    *--><classDoc id="FMCHUNK" type="model"><class>fmchunk</class><name>Front matter chunk elements</name><desc>This class groups elements which can occur as direct constituents
of front matter, when a full title page is not given. </desc><attList></attList><part type="base" name="core"/><classes/><xref target="DSTITL"/></classDoc><?tei:EOF fmchunk.cla ??><!-- fmchunk class --><?tei:SOF formptrs.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	formptrs.cla,v $
# Revision 1.2  94/01/15  20:49:30  msmcq
# cmsmcq rev for P3
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-01-15 : MSM : suppress note on need for clarification --><!-- 94-01-12 : MSM : Expand name                             --><!-- *********************************************** formptrs --><classDoc id="FORMPTRS" type="both"><class>formPointers</class><name>form pointers</name><desc>groups elements in the dictionary base which point at
orthographic or pronunciation forms of the headword.</desc><attList><!-- ................................................. target --><attDef usage="opt"><attName>target</attName><desc>gives the SGML identifier of the orthographic form referred to.</desc><datatype>IDREF</datatype><valDesc>an ID value on some <gi tei="yes">orth</gi> or <gi tei="yes">form</gi> element.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks><!-- [Should this be IDREF or IDREFS? -Ed.  <p>Used in        --><!-- content models, this class replaces the draft's class    --><!-- <term>dfloat</term>.  -Ed.]                              --></attDef></attList><remarks><p> (optional)</p></remarks><part type="base" name="dict"/><classes names="PHRASE"/><xref target="DI"/></classDoc><?tei:EOF formptrs.cla ??><!-- formPointers class --><?tei:SOF fragment.cla ??><!-- Revisions:                                               --><!-- 94-02-04 : MSM : seem to have lost classes element       --><!-- 94-02-04 : MSM : restored it                             --><!-- 94-02-03 : MSM : made file                               --><!-- ******************************************** fragmentary --><classDoc id="FRAGMENT" type="both"><class>fragmentary</class><desc>elements which mark the beginning or ending of a fragmentary
manuscript or other witness.</desc><attList><attDef usage="mwa"><attName>wit</attName><name>witnesses</name><desc>contains a list of one or more sigla indicating the witnesses
which begin or end at this point.</desc><datatype>CDATA</datatype><valDesc>A space-delimited series of sigla; each sigil should correspond
to a witness or witness group and occur as the value of the
<att tei="yes">sigil</att> attribute on a <gi tei="yes">witness</gi> element elsewhere in the
document.</valDesc><default>#IMPLIED</default><eg><![CDATA[  <rdg wit='M N'>Exper<witStart wit='M'>ience</rdg>]]></eg></attDef></attList><remarks><p>These elements may appear only within text-critical
apparatus.</p></remarks><part type="top" name="tc"/><classes/><xref target="TCAPMI"/></classDoc><?tei:EOF fragment.cla ??><!-- fragmentary class --><?tei:SOF clfront.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clfront.cla,v $
# Revision 1.4  93/08/23  16:54:21  msmcq
# version published with DR
# 
# Revision 1.3  1993/08/13  20:50:30  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-08-19 : MSM : part is core, not front                 --><!-- 93-06-04 : MSM : new id and name: clfront                --><!-- 93-06-03 : MSM : this is front, not drfront              --><!-- ********************************** front.cla --><classDoc id="CLFRONT" type="model"><class>front</class><desc>elements which appear at the level of divisions within front or
back matter.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes/><xref target="DRFAB"/></classDoc><?tei:EOF clfront.cla ??><!-- front class --><!-- &dftfs --><!-- fs class (default) --><!-- &clfs  --><!-- fs class --><?tei:SOF wsdglob.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdglob.cla,v $
# Revision 1.2  94/03/15  11:10:48  lou
# minor typos etc
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- ************************************************* global --><classDoc id="WSDGLOB" type="atts"><class>global</class><desc>defines global attributes for the writing system declaration.</desc><attList><!-- ..................................................... id --><attDef usage="opt"><attName>id</attName><desc>gives a unique identifier for the element.</desc><datatype>ID</datatype><valDesc>any valid SGML name unique within the document.</valDesc><default>#IMPLIED</default><remarks><p></p></remarks></attDef><!-- ................................................... lang --><attDef usage="opt"><attName>lang</attName><name>language</name><desc>gives the language in which the content of the element is written.</desc><datatype>CDATA</datatype><valDesc>Should be a language code from ISO 639.</valDesc><default>%INHERITED</default><remarks><p>This attribute functions like the global attribute of the
same name in the main TEI DTD; for technical reasons it is declared
differently.</p></remarks></attDef></attList><remarks><p></p></remarks><part type="aux" name="wsd"/><classes/><xref target="WDOV"/></classDoc><?tei:EOF wsdglob.cla ??><!-- global class (for WSD) --><?tei:SOF global.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	global.cla,v $
# Revision 1.6  94/04/08  01:44:01  msmcq
# suppress clfs
# 
# Revision 1.5  1994/04/05  16:24:16  lou
# remove refs tpo defunct clspoken and clcert classes
# ,
#
# Revision 1.4  1994/03/01  18:11:49  msmcq
# remove bad (for Script) line break within xref
#
# Revision 1.3  1993/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
#
# Revision 1.2  1993/09/17  16:21:39  msmcq
# misc cosmetic changes
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : suppress ref to clfs                    --><!-- 6 apr 94:  LB: remove refs to defunct clspoken and clcert classes --><!-- 93-11-26 : MSM : correct example:  no PERSON tag         --><!-- 93-09-15 : MSM : shorten lines in Ari example            --><!-- 93-09-15 : MSM : lowercase TEI.2                         --><!-- 93-09-11 : MSM : suppress ghost blank line               --><!-- 93-04-06 : MSM : add clcert, clspoken                    --><!-- 93-03-29 : MSM : remove old commented-out classes element --><!-- 93-03-27 : MSM : make classnames legal                   --><!-- 93-03-23 : MSM : add terminology, linking, analysis,     --><!--                  fs classes                              --><!-- 93-02-02 : MSM : temporarily suppress COMMON class       --><!--  2 Feb 93 : MSM : further mods to synchronize versions   --><!--  1 Feb 93 : MSM : change default of LANG to %INHERITED   --><!-- 25 Jan 93 : MSM : add commentary on rend;                --><!--                   add and delete teiform attribute       --><!-- ************************************************* global --><classDoc id="GLOBAL" type="atts"><class>global</class><desc>defines attributes common to all elements in the TEI encoding
scheme.</desc><attList><!-- ..................................................... id --><attDef usage="opt"><attName>id</attName><name>identifier</name><desc>provides a unique identifier for the element bearing the ID value.</desc><datatype>ID</datatype><valDesc>any valid SGML name (in the reference concrete syntax, a name
must begin with a letter and contain only letters, numeric digits,
hyphen, and full stop).</valDesc><default>#IMPLIED</default><eg><![CDATA[  <p id=NAMES>Paragraph with the ID <mentioned>names</>....
  <p id=DATES>Paragraph with the ID <mentioned>dates</>....]]></eg><remarks><p>The <att tei="yes">id</att> attribute may be used to specify a
canonical reference for an element; see section <xref target="CORS"/>.</p></remarks></attDef><!-- ...................................................... n --><attDef usage="opt"><attName>n</attName><name>number, name, etc.</name><desc>gives a number (or other label) for an element, which is not
necessarily unique within the document.</desc><datatype>CDATA</datatype><valDesc>any string of characters; often, but not necessarily, numeric.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The <att tei="yes">n</att> attribute may be used to specify the
numbering of chapters, sections, list items, etc.; it may also be used
in the specification of a standard reference system for the text.</p></remarks></attDef><!-- ................................................... lang --><attDef usage="opt"><attName>lang</attName><name>language</name><desc>indicates the language of the element content, usually using a
two- or three-letter code from ISO 639.</desc><datatype>IDREF</datatype><valDesc>The value must be the identifier specified for a writing system
declaration declared in the TEI header, as described in section<xref target="HD"/>
.<!-- need precise section number for WSD in TEI header --></valDesc><default>%INHERITED</default><eg><![CDATA[<p lang=EN>The only surviving work by <name>Ari</>
(died 1148) is the ten-page <title
lang=IS>&Iacute;slendingab&oacute;k</> (<title
lang=LA>Libellus Islandorum</>), written in the early
twelfth century.]]><!-- Carol J. Clover, The Medieval Saga (Ithaca:  Cornell     --><!-- University Press, 1982), p. 149.                         --></eg><remarks><p>If no value is specified for <att tei="yes">lang</att>, the
<att tei="yes">lang</att> value for the immediately enclosing element is
inherited; for this reason, a value should always be specified on the
outermost element (<gi tei="yes">tei.2</gi>).</p></remarks></attDef><!-- ................................................... rend  --><attDef usage="opt"><attName>rend</attName><name>rendition or presentation</name><desc>indicates how the element in question was rendered or presented in
the source text.</desc><datatype>CDATA</datatype><valDesc>any string of characters; if the typographic rendition of a
text is to be systematically recorded, a systematic set of values for
the <att tei="yes">rend</att> attribute should be defined.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>These Guidelines make no binding recommendations for the
values of the <att tei="yes">rend</att> attribute; the characteristics
of visual presentation vary too much from text to text and the decision
to record or ignore individual characteristics varies too much from
project to project.  Some potentially useful conventions are noted from
time to time at appropriate points in the Guidelines.<!-- and with luck the casebook will have a couple good examples. --></p></remarks></attDef></attList><remarks><p>The global attributes described here are made part of the
attribute definition list declaration of each element by including the
string <q>%a.global</q> in each such declaration.  Some global
attributes are made available when certain base or additional tag sets
are selected; these are incorporated into the global attributes by
references to the appropriate parameter entities.  When the tag sets in
question have not been selected, the parameter entities in question
expand to the empty string.</p></remarks><part type="base" name="core"/><classes names="CLTERM CLLINK CLANA"/><xref target="STGA"/></classDoc><?tei:EOF global.cla ??><!-- global class --><?tei:SOF globincl.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- Revisions:                                               --><!-- 14 mar 94 : LB : made file                               --><!-- ************************************************* globincl --><classDoc id="GLOBINCL" type="model"><class>globincl</class><name>global inclusions </name><desc>empty elements which may appear at any point within a TEI text.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes/><xref target="STEC"/></classDoc><?tei:EOF globincl.cla ??><!-- globincl (globalInclusions?) class --><?tei:SOF graminfo.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	graminfo.cla,v $
# Revision 1.1  94/01/15  20:49:30  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-01-12 : MSM : made file                               --><!-- *********************************************** formInfo --><classDoc id="GRAMINFO" type="model"><class>gramInfo</class><name>grammatical information</name><desc>elements allowed within a <gi tei="yes">gramGrp</gi> element in a dictionary.</desc><attList></attList><part type="base" name="di"/><classes/><xref target="DITPGR"/></classDoc><?tei:EOF graminfo.cla ??><!-- gramInfo class --><?tei:SOF hqinter.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hqinter.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-06 : MSM : add membership in class COMMON          --><!-- 92-12-09 : MSM : assign to class inter                   --><classDoc id="HQINTER" type="model"><class>hqinter</class><desc>intermediate-level elements related to highlighting. </desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="INTER COMMON"/><xref target="COHQ"/></classDoc><?tei:EOF hqinter.cla ??><!-- hqinter class --><?tei:SOF hqphrase.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hqphrase.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : assign to class phrase                  --><classDoc id="HQPHRASE" type="model"><class>hqphrase</class><desc>phrase-level elements related to highlighting. </desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="PHRASE"/><xref target="COHQ"/></classDoc><?tei:EOF hqphrase.cla ??><!-- hqphrase class --><?tei:SOF inter.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	inter.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : class name <> full name                 --><!-- 92-12-09 : MSM : renamed from chunks.tag, add more expl  --><!-- *************************************************inter --><classDoc id="INTER" type="model"><class>inter</class><desc>elements of the intermediate (inter-level) class, which can occur
both within paragraphs and between paragraphs.</desc><attList></attList><remarks><p>This element class contains a subset of those elements which
can appear in the unstructured <soCalled>soup</soCalled> with which
paragraph and other elements at the lowest level of crystal structures
are filled:  specifically all the elements which can also occur as
structural elements in their own right.  In prose, this means the
elements in this class can appear both within and between paragraphs.
This class is thus distinct from the purely phrase-level elements which
can appear only within soup, and not on their own; the latter class, in
keeping with this metaphor, is called <soCalled>broth</soCalled>; it
is represented by the class <term>phrase</term>.  Cf. also the
class <term>chunks</term>.</p></remarks><part type="base" name="core"/><classes/><xref target="STEC"/></classDoc><?tei:EOF inter.cla ??><!-- inter class --><?tei:SOF clinterp.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clinterp.cla,v $
# Revision 1.3  94/03/28  19:29:20  msmcq
# fix rcs log keyword
#  --><!-- ************************************************** clinterp --><!-- Revisions:                                               --><!-- 26 feb 94: made from clana --><classDoc id="CLINTERP" type="atts"><class>interpret</class><desc>defines attributes common to all interpretative elements.</desc><attList><attDef usage="opt"><attName>resp</attName><desc>indicates who is responsible for the interpretation.</desc><datatype>CDATA</datatype><valDesc>Any string of characters, such as the initials of the encoder.</valDesc><default>%INHERITED</default><remarks><p></p></remarks></attDef><attDef usage="rec"><attName>type</attName><desc>indicates what kind of phenomenon is being noted in the passage.</desc><datatype>CDATA</datatype><valList type="open"><val>image</val><desc>identifies an image in the passage.
   </desc><val>character</val><desc>identifies a character associated with the passage.
   </desc><val>theme</val><desc>identifies a theme in the passage.
   </desc><val>allusion</val><desc>identifies an allusion to another text.
   </desc><val>(discourse type)</val><desc>specifies that the passage is of a particular discourse type.</desc></valList><default>%INHERITED</default></attDef><attDef usage="opt"><attName>inst</attName><desc>points to instances of the analysis or interpretation represented
by the current element.</desc><datatype>IDREFS</datatype><valDesc>One or more valid SGML identifiers.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>The current element should be an analytic one.  The element
pointed at should be a textual one.</p></remarks></attDef></attList><part type="top" name="ai"/><classes/><xref target="AIATTS"/></classDoc><?tei:EOF clinterp.cla ??><!-- interpret class --><?tei:SOF dftlink.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dftlink.cla,v $
# Revision 1.1  93/09/15  23:02:26  msmcq
# Changes as of mid-September
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : made DFT version                        --><!-- 93-03-13 : MSM : made file from cllink.cla               --><!-- ************************************************ dftlink --><classDoc id="DFTLINK" type="atts"><class>linking</class><desc>default declaration for class <term>linking</term>:
when the additional tag set for linking is not selected,
no attributes are defined for this class.</desc><attList></attList><part type="top" name="ling"/><classes/><xref target="STGA"/><xref target="SA"/></classDoc><?tei:EOF dftlink.cla ??><!-- linking class (default) --><?tei:SOF cllink.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cllink.cla,v $
# Revision 1.6  94/03/25  15:48:19  msmcq
# add explicit end-tags for attdef compnents
# (fix for a weakness of new oddref)
# 
# Revision 1.5  1994/03/15  11:10:23  lou
# minor typos etc
#
# Revision 1.4  1994/02/12  10:46:51  lou
# revisions for P3
#
# Revision 1.3  1993/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
#
# Revision 1.2  1993/09/22  18:57:09  msmcq
# incorporate TDL changes of July 1993
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 14 mar: LB: kill vacuous exempla --><!-- 5 feb 94: LB kill, then resuscitate copyOf and sameAs --><!-- 93-11-26 : MSM : suppress ANA and INST atts:  they are in CLANA --><!-- 93-09-22 : MSM : incorporate TDL's changes from July     --><!-- 93-03-29 : MSM : rename from ana                         --><!-- 93-01-26 : MSM : alter desc of prev, next atts           --><!-- 93-01-26 : MSM : rename csp as corresp                   --><!-- 93-01-22 : MSM : omit empty name element                 --><!-- 93-01-21 : MSM : change class name                       --><!-- 92-12-23 : MSM : change filename, id                     --><!-- *************************************************cl.link --><classDoc id="CLLINK" type="atts"><class>linking</class><desc>defines additional attributes for hypertext and other linking,
which are enabled for all elements when the additional tag set for
linking is selected.</desc><attList><attDef usage="opt"><attName>corresp</attName><!-- SAcs --><name>correspondents</name><desc>points to elements that correspond to the current element in some
way.</desc><datatype>IDREFS</datatype><valDesc>one or more valid SGML identifiers for elements in the current
document, separated by white space.</valDesc><default>#IMPLIED</default><remarks></remarks></attDef><attDef usage="opt"><attName>synch</attName><!-- SAsy --><name>synchronous</name><desc>points to elements that are synchronous with the current element.</desc><datatype>IDREFS</datatype><valDesc>one or more valid SGML identifiers for elements in the current
document, separated by white space.</valDesc><default>#IMPLIED</default><remarks></remarks></attDef><!-- SAie  attributes suppressed , then reinstated --><attDef usage="opt"><attName>sameAs</attName><desc>points to an element that is the same as the current element.
 </desc><datatype>IDREF
 </datatype><valDesc>a valid SGML identifier.
 </valDesc><default>#IMPLIED
 </default></attDef><attDef usage="opt"><attName>copyOf</attName><desc>points to an element of which the current element is a copy.
 </desc><datatype>IDREF
 </datatype><valDesc>a valid SGML identifier for an element in the current document.
 </valDesc><default>#IMPLIED
 </default><remarks><p>Any content of the current element should be ignored.  Its
 true content is that of the element being pointed at.
 </p></remarks></attDef><attDef usage="opt"><attName>next</attName><!-- SAag --><desc>points to the next element of a virtual aggregate of which the
current element is part.</desc><datatype>IDREF</datatype><valDesc>a valid SGML identifier.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>prev</attName><!-- SAag --><desc>points to the previous element of a virtual aggregate of which the
current element is part.</desc><datatype>IDREF</datatype><valDesc>a valid SGML identifier.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>exclude</attName><!-- SAat --><desc>points to elements that are in exclusive alternation with the
current element.</desc><datatype>IDREFS</datatype><valDesc>a list of valid SGML identifiers.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>select</attName><!-- SAat --><desc>selects one or more alternants; if one alternant is selected, the
ambiguity or uncertainty is marked as resolved.  If more than one
alternant is selected, the degree of ambiguity or uncertainty is marked
as reduced by the number of alternants not selected.</desc><datatype>IDREFS</datatype><valDesc>a list of valid SGML identifiers.</valDesc><default>#IMPLIED</default><remarks><p>This attribute should be placed on an element which is
superordinate to all of the alternants from which the selection is being
made.</p></remarks></attDef></attList><part type="top" name="ling"/><classes/><xref target="SA"/></classDoc><?tei:EOF cllink.cla ??><!-- linking class --><?tei:SOF lists.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lists.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-06 : MSM : add membership in class COMMON          --><!-- 92-12-10 : MSM : add class affiliation                   --><classDoc id="LISTS" type="model"><class>lists</class><desc>list-like elements.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="INTER COMMON"/><xref target="COLI"/></classDoc><?tei:EOF lists.cla ??><!-- lists class --><?tei:SOF clloc.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clloc.cla,v $
# Revision 1.1  93/12/20  14:52:17  lou
# Initial revision
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-02-10 : MSM : new id of clloc: LOC is taken           --><!-- 93-01-26 : MSM : resurrect this version of classdoc      --><!-- 92-12-09 : MSM : assign to class PHRASE                  --><!-- 92-12-09 : MSM : suppress attributes (move them to pointer class) --><!-- 92-12-07 : MSM : allow multiple values for targType      --><!-- 92-12-07 : MSM : add attributes, change type to both     --><classDoc id="CLLOC" type="model"><class>loc</class><desc>elements used for purposes of location and reference</desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="PHRASE"/><xref target="COXR"/></classDoc><?tei:EOF clloc.cla ??><!-- loc class --><?tei:SOF metadata.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- Revisions: --><!-- 12 Mar 94: LB : Made file  --><!-- ************************************************** metadata --><classDoc id="METADATA" type="model"><class>metadata</class><desc>empty elements which describe the status of other elements, for
example by holding groups of links or of abstract interpretations, or
by providing indications of certainty etc., and which may appear at any
point in a document.</desc><attList></attList><remarks><p>Encoders may find it convenient to localize all
metadata elements, for example to contain them within the same divison
as the elements that they relate to; or to locate them all to a
division of their own. They may however appear at any point in a TEI
text.</p></remarks><part type="base" name="core"/><classes names="GLOBINCL"/><xref target="STEC"/><!-- need more precise xref --></classDoc><?tei:EOF metadata.cla ??><!-- metadata class --><?tei:SOF metrical.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	metrical.cla,v $
# Revision 1.3  93/11/26  18:19:55  msmcq
# revision for publication of VE
# 
# Revision 1.2  1993/08/16  21:56:29  msmcq
# tweaks / revisions for publication of DR
#
# Revision 1.1  1993/08/11  13:11:35  lou
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-11-18 : MSM : change remarks on RHYME to allow for    --><!-- 93-11-18 : MSM : use of user-defined alternative notatinos --><!-- 93-11-18 : MSM : recast RHYME desc to avoid implication  --><!--    that only metrical lines rhyme, and free verse cannot --><!-- 17 Jul 93: LB: made file                          --><classDoc id="METRICAL" type="atts"><class>metrical</class><desc>elements carrying metrical information. </desc><attList><attDef usage="rec"><attName>met</attName><desc>contains a user-specified encoding for the conventional
metrical structure of the element.</desc><datatype>CDATA</datatype><valDesc>May contain either a standard term for the kind of metrical
unit (e.g. <q>hexameter</q>) or an encoded representation for the
metrical pattern (e.g. <q>+--+-+-+-+-</q>). In either case, the
notation used should be documented by a <gi tei="yes">metNotation</gi> element
within the <gi tei="yes">encodingDesc</gi> of the associated header.</valDesc><default>%INHERITED</default><remarks><p>Where this attribute is not specified, the metrical
pattern for the element concerned is understood to be inherited
from its parent.</p></remarks></attDef><attDef usage="rwa"><attName>real</attName><desc>contains a user-specified encoding for the actual realization
of the conventional metrical structure applicable to the element.</desc><datatype>CDATA</datatype><valDesc>May contain either a standard term for the kind of metrical
unit (e.g. <q>hexameter</q>) or an encoded representation for the
metrical pattern (e.g. <q>+--+-+-+-+-</q>). In either case, the
notation used should be documented by a <gi tei="yes">metNotation</gi> element
within the <gi tei="yes">encodingDesc</gi> of the associated header.</valDesc><default>#IMPLIED</default><remarks><p>Where this attribute is not specified, the metrical
realization for the element concerned is understood to be identical
to that specified or implied for the <att tei="yes">met</att> attribute.</p></remarks></attDef><attDef usage="rec"><attName>rhyme</attName><desc>specifies the rhyme scheme applicable to a group of verse lines.</desc><datatype>CDATA</datatype><valDesc>By default, the
rhyme scheme is expressed as a string of alphabetic
characters each corresponding with a rhyming line.  Any non-rhyming
lines should be represented by a hyphen or an X.  Alternative notations
may be defined as for <att tei="yes">met</att> by use of the <gi tei="yes">metNotation</gi>
element in the TEI header.</valDesc><default>#IMPLIED</default><eg><![CDATA[    <lg rhyme='ABABABCC'> ... </lg>]]></eg><remarks><p>When the default notation is used, it does not make sense to
specify this attribute on any unit smaller than a line.  Nor does the
default notation provide any way to record internal rhyme, or to specify
non-conventional rhyming practice. These extensions would require
user-defined alternative notations.</p></remarks></attDef></attList><remarks><p></p></remarks><part type="base" name="verse"/><classes/><xref target="VEME"/></classDoc><?tei:EOF metrical.cla ??><!-- metrical class --><?tei:SOF morph.cla ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix MORPH:  define morphinfo as subclass of --><!-- 94-08-04 : MSM : forminfo and graminfo                   --><!-- 94-03-30 : MSM : change name from morph to morphInfo (as --><!--            planned in January, and partially executed)   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	morph.cla,v $
# Revision 1.3  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.2  1994/04/01  17:34:39  msmcq
# Changes during validation of DTD
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- ************************************************** morph --><classDoc id="MORPH" type="model"><class>morphInfo</class><name>morphological elements</name><desc>groups elements for providing morphological information.</desc><attList></attList><remarks><p></p></remarks><part type="base" name="dict"/><classes names="FORMINFO GRAMINFO"/><xref target="DITP" type="div3"/></classDoc><?tei:EOF morph.cla ??><!-- morphInfo class --><?tei:SOF names.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	names.cla,v $
# Revision 1.4  98/01/28  19:23:53  tei
# LB changes of January 1998
# 
    * Revision 1.3  1994/03/15  11:10:36  lou
    * minor typos etc
    * 
    * Revision 1.2  1994/03/07  16:15:00  lou
    * revised for [publicn of ND
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 10 jan 98 : LB : changed description pace Baumann --><!-- 92-12-09 : MSM : made file                               --><!-- ************************************************** names --><classDoc id="NAMES" type="atts"><class>names</class><desc>elements which refer to named persons, places, organizations etc.<!-- was: with proper nouns as content. --><!-- Syd points out that this cannot be said of RS --></desc><attList><attDef usage="opt"><attName>key</attName><desc>provides an alternative identifier for the object being named,
such as a database record key.</desc><datatype>CDATA</datatype><valDesc>any string</valDesc><default>#IMPLIED</default><eg><![CDATA[<name type='place'>Montaillou</name>
is not a large parish.
At the time of the events which led to 
<name type='person' key=BXII>
Fournier's</name> investigations,
the local population consisted of between 200 and
250 inhabitants.]]></eg><remarks><p>The value may be a unique identifier from a database, or
simply a more explicit name for the referent. Its purpose is only to
record an identification; if the analysis leading to the identification
is to be recorded as well, the analytic tags described in chapter<xref target="FS"/>
 should be used in addition or instead.</p></remarks></attDef><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a normalized or regularized form of the name used.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg><![CDATA[At the time of the events which led to
<name type=person reg='Benedict XII, Pope of Avignon
(Jacques Fournier)'>Fournier's</name> investigations,
the local population consisted of between 200 and
250 inhabitants.]]></eg><remarks><p>In providing a <soCalled>regularized</soCalled> form, no
claim is made that the form in the source text is incorrect; the
regularized form is simply that chosen as the main form for purposes
of unifying variant forms under a single heading.</p></remarks></attDef></attList><remarks><p></p></remarks><part type="base" name="core"/><classes/><xref target="CONARS"/></classDoc><?tei:EOF names.cla ??><!-- names class --><?tei:SOF notes.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	notes.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-03-06 : MSM : add membership in class COMMON          --><!-- 92-12-10 : MSM : add class affiliation                   --><classDoc id="NOTES" type="model"><class>notes</class><desc>note-like elements. </desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="INTER COMMON"/><xref target="CONO"/></classDoc><?tei:EOF notes.cla ??><!-- notes class --><?tei:SOF perspart.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	perspart.cla,v $
# Revision 1.2  94/09/09  01:30:41  msmcq
# normalize class name per agreement with LB
# (change originally made 31 Mar 94, lost, refound)
# 
# Revision 1.1  1994/03/07  16:14:26  lou
# Initial revision
#
# Revision 1.3  1994/03/01  04:14:47  msmcq
# fix syntax slip
# (parenthesize name group)
#
# Revision 1.2  1993/08/02  21:35:13  msmcq
# rename this class
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : change name to personPart, as agreed LB+MSM --><!-- 6 mar 94 : revise; renamed (was pname.cla)               --><!-- 94-02-25 : MSM : put parens around name group in FULL    --><!-- 93-06-21 : MSM : rename class                            --><!-- 93-06-05 : MSM : supply missing valdesc                  --><classDoc id="PERSPART" type="both"><class>personPart</class><name>components of personal names</name><desc>groups elements which form part of a personal name.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>provides more culture- linguistic- or application- specific
information used to categorize this name component.</desc><datatype>CDATA</datatype><valDesc>one of a set of codes defined for the application.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>full</attName><desc>indicates whether the name component is given in full, as an
abbreviation or simply as an initial.</desc><datatype>(yes | abb | init)</datatype><valList type="closed"><val>yes</val><desc>the name component is spelled out in full.</desc><val>abb</val><desc>the name component is given in an
abbreviated form.</desc><val>init</val><desc>the name component is indicated only by
one initial.</desc></valList><default>yes</default></attDef><attDef usage="opt"><attName>sort</attName><desc>specifies the sort order of the name component in relation
to others within the personal name.</desc><datatype>NUMBER</datatype><valDesc>A positive number indicating the sort order.</valDesc><default>#IMPLIED</default></attDef></attList><remarks></remarks><part type="top" name="ND"/><classes names="NAMES"/><xref target="NDPER"/></classDoc><?tei:EOF perspart.cla ??><!-- personPart class --><?tei:SOF phrase.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	phrase.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : made file                               --><!-- ************************************************* phrase --><classDoc id="PHRASE" type="model"><class>phrase</class><desc>includes elements which can occur at the level of individual
words or phrases.</desc><attList></attList><remarks><p>This class of elements can occur only within larger
elements of the class <term>inter</term> or <term>chunk</term>.
In prose, this means these elements can occur within paragraphs,
list items, lines of verse, etc.</p></remarks><part type="base" name="core"/><classes/><xref target="STEC"/></classDoc><?tei:EOF phrase.cla ??><!-- phrase class --><?tei:SOF vephr.cla ??><!-- Revisions:                                               --><!-- 93-09-23 : MSM : change name for legibility              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $  --><!-- $Log:	vephr.cla,v $
# Revision 1.3  94/01/04  00:28:30  msmcq
# change name for legibility
# 
# Revision 1.2  1993/09/23  10:27:25  lou
# removed otiose remark
#
# Revision 1.1  1993/08/11  13:12:07  lou
# Initial revision
# --><!-- 8 Aug 93 : LB : made file                               --><!-- ************************************************* vephr --><classDoc id="VEPHR" type="model"><class>phrase.verse</class><desc>phrase-level elements which may appear within verse only.</desc><attList></attList><remarks><p></p></remarks><part type="top" name="verse"/><classes names="PHRASE"/><xref target="VESE"/></classDoc><?tei:EOF vephr.cla ??><!-- phrase.verse class --><?tei:SOF placpart.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: placpart.cla,v $
    * Revision 1.3  1998/02/01 17:47:42  tei
    * *** empty log message ***
    *
    * Revision 1.2  94/09/09  01:30:41  msmcq
    * normalize class name per agreement with LB
    * (change originally made 31 Mar 94, lost, refound)
    * 
    * Revision 1.1  1994/03/07  16:14:47  lou
    * Initial revision
    * 
    * Revision 1.3  1993/09/16  15:02:49  msmcq
    * correct syntax error
    * 
    * Revision 1.2  1993/08/02  21:33:27  msmcq
    * add to class names
    * rename placename
    * --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : change name to placePart, as agreed LB+MSM --><!-- 93-09-13 : MSM : correct syntax error in datatype        --><!-- 93-06-21 : MSM : add to class names                      --><!-- 93-06-21 : MSM : rename placename not placname           --><classDoc id="PLACPART" type="both"><class>placePart</class><name>place name components</name><desc>groups elements which form part of a place name.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>provides more culture- linguistic- or application- specific
information used to categorize this name component.</desc><datatype>CDATA</datatype><valDesc>one of a set of codes defined for the application.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>full</attName><desc>indicates whether the place name component is given in full, as an
abbreviation or simply as an initial</desc><datatype>(yes | abb | init)</datatype><valList type="closed"><val>yes</val><desc>the name component is spelled out in full.</desc><val>abb</val><desc>the name component is given in an
abbreviated form.</desc><val>init</val><desc>the name component is indicated only by
one initial.</desc></valList><default>yes</default></attDef></attList><remarks></remarks><part type="top" name="ND"/><classes names="NAMES"/><xref target="NDPLAC"/></classDoc><?tei:EOF placpart.cla ??><!-- placePart class --><?tei:SOF pointer.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pointer.cla,v $
# Revision 1.3  94/02/12  10:46:23  lou
# revisions for publicn of P3
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-01-26 : MSM : change 'pointered' to 'targeted'        --><!-- 92-12-09 : MSM : made pointer file out of old loc class  --><!-- 92-12-07 : MSM : allow multiple values for targType      --><!-- 92-12-07 : MSM : add attributes, change type to both     --><classDoc id="POINTER" type="atts"><class>pointer</class><desc>elements which point to other elements, using IDREFs.</desc><attList><attDef usage="opt"><attName>type</attName><desc>categorizes the pointer in some respect, using any convenient
     set of categories.</desc><datatype>CDATA </datatype><valDesc>The type should indicate the intended function of the
        pointer, or the rhetorical
    relationship between its source and target. </valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>resp</attName><!-- was author, then ed --><desc>specifies the creator of the pointer.</desc><datatype>CDATA </datatype><valDesc>any string of characters, usually the initials or name
  of the creator.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>crdate</attName><!-- was cre.date --><desc>specifies when the pointer was created.</desc><datatype>CDATA</datatype><valDesc>any string representing a date.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>targType</attName><!-- added by LB --><desc>specifies the kinds of elements to which this pointer may point.
  </desc><datatype>NAMES </datatype><valDesc>A list of names of SGML elements defined in the DTD of the
  current document.</valDesc><default>#IMPLIED</default><remarks><p>If this attribute is supplied, every element specified as a
target must be of one or other of the types specified.  An
application may choose whether or not to report failures to satisfy this
constraint as errors, but may not access an element of the right
identifier but the wrong type.
 </p></remarks></attDef><attDef usage="opt"><attName>targOrder</attName><!-- added by LB --><desc>where more than one identifier is supplied as the value of the
<att tei="yes">target</att> attribute, this attribute specifies whether the order
in which they are supplied is significant.</desc><datatype>(Y | N | U)</datatype><valList type="closed"><val>Y</val><desc>Yes: the order in which IDREFs are
         specified as the value of a <att tei="yes">target</att> attribute
         should be followed when combining the
         targeted elements.
  </desc><val>N </val><desc>No: the order in which IDREFs are
         specified as the value of a <att tei="yes">target</att> attribute
         has no significance when combining the
         targeted elements.
  </desc><val>U </val><desc>Unspecified: the order in which IDREFs are
         specified as the value of a <att tei="yes">target</att> attribute
         may or may not be significant.
  </desc></valList><default>U</default></attDef><attDef usage="opt"><attName>evaluate</attName><!-- added by LB --><desc>specifies the intended meaning
when the target of a pointer is itself a pointer.</desc><datatype>(all | one | none)</datatype><valList type="open"><val>all</val><desc>if the element pointed to is itself a pointer, then
      the target of that pointer will be taken, and so on, until an
      element is found which is not a pointer.
    </desc><val>one </val><desc>if the element pointed to is itself a pointer, then
      its target (whether a pointer or not) is taken as the target of
      this pointer.
    </desc><val>none</val><desc>no further evaluation of targets is carried out beyond
      that needed to find the element specified in the pointer's target.
  </desc></valList><default>#IMPLIED</default><remarks><p>If no value is given, the application program is
          responsible for deciding (possibly on the basis of user
          input) how far to trace a chain of pointers.
 </p></remarks></attDef></attList><remarks><p></p></remarks><part type="base" name="core"/><classes/><xref target="COXR"/></classDoc><?tei:EOF pointer.cla ??><!-- pointer class --><?tei:SOF ptrgroup.cla ??><!-- ******************************************* pointerGroup --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: ptrgroup.cla,v $
    * Revision 1.5  1998/01/31 19:55:27  tei
    * really killed extendTarg
    *
    * Revision 1.4  1994/03/25 15:48:19  msmcq
    * add explicit end-tags for attdef compnents
    * (fix for a weakness of new oddref)
    * Revision 1.3  1994/02/12  10:46:55  lou
    * revisions for P3
    * 
    * Revision 1.2  1993/12/20  17:11:38  lou
    * fixed sgml errors
    * 
    * Revision 1.1  1993/09/15  23:02:26  msmcq
    * Changes as of mid-September
    * --><!-- 5 feb 94: LB:  removed extendTarg attribute; revised desc --><!-- Attributes for GROUPER class of elements                 --><!-- Currently LINKgRP, JOINgRP, ALTgRP                       --><!-- Revisions:                                               --><!-- 94-03-21 : MSM : explicit end-tags for att def components --><!-- 93-09-15 : MSM : made file for ptrgroup class            --><!-- 93-07-23 :  DTL : create without knowing ODD tagging     --><!--                   conventions.  make ATTLIST only for    --><!--                   attributes not defined  for pointer    --><!--                   class (which grouper class shares)     --><!-- ******************************************* pointerGroup --><classDoc id="PTRGROUP" type="atts"><class>pointerGroup</class><desc>elements which enclose groups of pointer elements.</desc><attList><attDef usage="opt"><attName>domains</attName><desc>optionally specifies the identifiers of the elements within which
all elements indicated by the contents of this element lie.<!-- designates the elements from which the values of the  --><!-- <att>targets</att> attribute of   --><!-- the enclosed <gi>link</gi>, <gi>join</gi>  --><!-- or <gi>alt</gi> tags are drawn.  --></desc><datatype>IDREFS</datatype><valDesc>a list of at least two valid SGML identifiers.</valDesc><default>#IMPLIED</default><eg><![CDATA[<linkGrp type='imitation'
         domains='dunciad dunnotes'
         targType='note l'
         targOrder=Y>]]></eg><remarks><p>If this attribute is supplied every element specified as a
target must be contained within the element or elements specified by
it.  An application may choose whether or not to report failures to
satisfy this constraint as errors, but may not access an element of the
right identifier but in the wrong context. If this attribute is not
supplied, then target elements may appear anywhere within the current
document.</p></remarks></attDef><!-- Something like the remark associated with the targType=
      attribute would be appropriate here.                    --><!-- your wish is my command (LB) --><attDef usage="opt"><attName>targFunc</attName><desc>describes the function of each of the values of the
<att tei="yes">targets</att> attribute of the enclosed <gi tei="yes">link</gi>, <gi tei="yes">join</gi>
or <gi tei="yes">alt</gi> tags.</desc><datatype>NMTOKENS</datatype><valDesc>a list of at least two valid SGML name tokens.</valDesc><default>#IMPLIED</default><!-- for LINKgRP only.  This attribute has specific default   --><!-- values for JOINgRP and ALTgRP; currently those appear in --><!-- the TAGDOCs for those tags (DTL)                         --><eg><![CDATA[<linkGrp resp=NPR
         type='imitation'
         domains='dunciad dunnotes dunnotes'
         targType='note ref l'
         targFunc='source reference.to.goal goal'
         targOrder=Y>]]></eg><remarks><p>The number of separate values must match the number of
values in the <att tei="yes">targets</att> attribute in the enclosed <gi tei="yes">link</gi>,
<gi tei="yes">join</gi> or <gi tei="yes">alt</gi> tags (an intermediate <gi tei="yes">xptr</gi>
element may be needed to accomplish this).<!-- (unless the <att>extendTarg</att>  -->
  <!-- attribute allows the <att>targets</att> attributes --><!-- of those tags to have more values). -->
It should also match the number of values in the
<att tei="yes">targType</att> and <att tei="yes">domains</att> attributes of the current tag,
if those have been specified.</p></remarks></attDef><!-- I killed this attribute because of the inherent ambiguity --><!-- noted in remarks: the increase in complexity doesnt seem --><!-- worth adding if it's not going to work all the time. Use --><!-- intermediate pointers instead!     (LB)                  --><!-- <attDef usage=rwa> --><!-- <attName>extendTarg  --><!-- <desc>permits the number of values of the <att>targets</att>  --><!-- attribute of the enclosed <gi>link</gi>, <gi>join</gi> or  --><!-- <gi>alt</gi> tags to be extended beyond the number of values  --><!-- implicitly or explicitly defined for it in the  --><!-- <att>targType</att>, <att>domains</att> or  --><!-- <att>targFunc</att> attributes.  --><!-- <datatype>NUMBERS  --><!-- <valDesc>a list of positive integers, or 0.  The value 0  --><!-- means that the number of targets cannot be extended.  The  --><!-- value 1 means that the first target can be extended; 2 the  --><!-- second target, etc.  The value '1 2' means that both the  --><!-- first and second target can be extended, which creates a  --><!-- potential ambiguity, since if three values are given, it may  --><!-- not be clear whether the second value extends the first  --><!-- target or the second.  This ambiguity is resolvable if the  --><!-- domains of the two targets are different and the  --><!-- <att>domains</att> attribute has been specified.  --><!-- <default>0  --><!-- <eg><![ CDATA [  --><!-- <linkGrp resp=NPR  --><!--          type='imitation'  --><!--          domains='dunciad dunnotes'  --><!--          targType='note l'  --><!--          targFunc='source goal'  --><!--          targOrder=Y  --><!--          extendTarg=2>  --><!-- The second target has been extended in the following LINK tag. --><!--   <link targets='N2.79 L2.79 L2.302 L3.154'>  --><!--   <link targets='N2.88 L2.88'>  --><!--   ...  --><!--   <link targets='N3.284 L3.284'>  --><!--   ...  --><!-- </linkGrp>  --><!-- ]]>  --><!-- </eg>  --><!-- <remarks><p>This attribute should be used in conjunction  --><!-- with the <att>targType</att> attribute (automatic in case of  --><!-- <gi>joinGrp</gi> and <gi>altGrp</gi> elements), or the  --><!-- <att>domains</att> or <att>targFunc</att> attributes, so as  --><!-- to make explicit the basic number of values in the  --><!-- <att>targets</att> attribute of the enclosed <gi>link</gi>,  --><!-- <gi>join</gi> or <gi>alt</gi> tags.  No value of this  --><!-- attribute should exceed that number.  --></attList><remarks></remarks><part type="top" name="link"/><classes names="POINTER"/><xref target="SA"/></classDoc><?tei:EOF ptrgroup.cla ??><!-- pointerGroup class --><?tei:SOF readings.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	readings.cla,v $
# Revision 1.4  94/03/25  15:48:19  msmcq
# correct hereditary error with %INHERITED
# 
# Revision 1.3  1994/02/11  20:59:33  msmcq
# changes in revising TC
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-03-21 : MSM : correct errors in defaults (%INHERITED) --><!-- 94-02-03 : MSM : rename wit element as witness           --><!-- 94-02-03 : MSM : minor cosmetic improvements             --><!-- 94-01-25 : MSM : add WIT att                             --><!-- ENTITY readings system 'readings.cla' --><!-- readings class --><!-- *********************************************** readings --><classDoc id="READINGS" type="atts"><class>readings</class><desc>elements representing variant readings in text critical work.</desc><attList><!-- .................................................... wit --><attDef usage="mwa"><attName>wit</attName><name>witnesses</name><desc>contains a list of one or more sigla indicating the witnesses
which attest to a given reading.</desc><datatype>CDATA</datatype><valDesc>A space-delimited series of sigla; each sigil should correspond
to a witness or witness group and occur as the value of the
<att tei="yes">sigil</att> attribute on a <gi tei="yes">witness</gi> element elsewhere in the
document.</valDesc><default>#IMPLIED</default><eg><![CDATA[  <rdg wit='El Hg'>Experience</rdg>]]></eg><remarks><p>If the apparatus contains readings only for a single
witness, this attribute may be consistently omitted.</p></remarks></attDef><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the reading according to some useful typology.</desc><datatype>CDATA</datatype><valList type="open"><val>substantive</val><desc>the reading offers a substantive variant.</desc><val>orthographic</val><desc>the reading differs only orthographically, not in substance,
from
other readings.</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- accepted MSM's strictures on double classification --></attDef><!-- .................................................. cause --><attDef usage="opt"><attName>cause</attName><desc>classifies the reading as original or non-original, according to
some typology of possible origins.</desc><datatype>CDATA</datatype><valDesc>any word or phrase describing the cause: e.g.
<q>homeoteleuton</q>,
<q>homeoarchy</q>,
<q>paleographic confusion</q>,
<q>haplography</q>,
<q>dittography</q>,
<q>false emendation</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................. varSeq --><attDef usage="opt"><attName>varSeq</attName><name>variant sequence</name><desc>provides a number indicating the position of this reading in a
sequence, when there is reason to presume a sequence to the variants
on any one lemma.</desc><datatype>NUMBER</datatype><valDesc>a positive integer</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>Different variant sequences could be coded with distinct
number trails: 1-2-3 for one sequence, 5-6-7 for another.  More
complex variant sequences, with (for example) multiple branchings
from single readings, may be expressed through the <gi tei="yes">join</gi>
element.</p></remarks></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>identifies the editor responsible for asserting a particular
reading in the witness.</desc><datatype>CDATA</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute is only available within an apparatus
gathering variant readings in the transcription of an individual
witness.  It may not occur in an apparatus gathering readings from
different witnesses.</p></remarks></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>signifies the hand responsible for a particular reading in the
witness.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute is only available within an apparatus
gathering variant readings in the transcription of an individual
witness.  It may not occur in an apparatus gathering readings from
different witnesses.
 </p></remarks></attDef><!-- ................................................... wit --><attDef usage="opt"><attName>wit</attName><name>witness</name><desc>contains a list of one or more sigla of witnesses attesting a
given reading.</desc><datatype>CDATA</datatype><valDesc>the list of sigla.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute may occur both within an apparatus
gathering variant readings in the transcription of an individual
witness and within an apparatus gathering readings from different
witnesses.</p><p>In local encoding schemes, the value of the <att tei="yes">wit</att>
attribute can be enforced as IDREFS, such that only witnesses
referred to in a <gi tei="yes">witList</gi> element may occur as witnesses to a
reading.
 
 </p></remarks></attDef></attList><remarks><p>This element class defines attributes inherited by
<gi tei="yes">rdg</gi>, <gi tei="yes">lem</gi>, and <gi tei="yes">rdg.grp</gi>.</p></remarks><part type="top" name="tc"/><classes/><xref target="TCAPLL"/></classDoc><?tei:EOF readings.cla ??><!-- readings class --><?tei:SOF refsys.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	refsys.cla,v $
# Revision 1.3  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.2  1994/01/04  12:15:10  lou
# fix xrefs
#
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : add to class globincl (global inclusions) --><!-- 25 dec93: LB: added xref to co --><!-- 92-12-10 : MSM : made file                               --><!-- ************************************************* refsys --><classDoc id="REFSYS" type="model"><class>refsys</class><name>reference system elements</name><desc>milestone-style elements used in reference systems</desc><attList></attList><remarks><p></p></remarks><part type="base" name="core"/><classes names="GLOBINCL"/><xref target="STEC"/><xref target="CORS5"/></classDoc><?tei:EOF refsys.cla ??><!-- refsys class --><?tei:SOF clseg.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: clseg.cla,v $
    * Revision 1.6  1998/01/29 21:49:51  tei
    * added PART attribute
    *
    * Revision 1.5  1994/03/28 14:24:09  lou
    * REALLY fix cross reference to AI...
    *
    * Revision 1.4  1994/03/28  13:37:25  lou
    * afix cross references
    * 
    * Revision 1.3  1994/03/08  03:19:06  msmcq
    * minor fix for Script's sake
    * 
    * Revision 1.2  1994/02/27  15:55:50  lou
    * Revisions for publication of AI
    * 
    * Revision 1.1  1993/09/23  16:22:54  msmcq
    * Initial revision
    * 
    * Revision 1.1  1993/08/02  21:21:23  msmcq
    * Initial revision
    * --><!-- Revisions:                                               --><!-- 28 jan 98 : LB : add PART attribute --><!-- 94-03-01 : MSM : trivial change for sake of Script       --><!-- 26 feb : add attributes for type and function --><!-- 93-09-22 : MSM : change id, name to avoid clash with seg tag --><!-- 92-12-10 : MSM : add class affiliation                   --><classDoc id="CLSEG" type="both"><class>seg</class><desc>elements for arbitrary segmentation. </desc><attList><attDef usage="opt"><attName>type</attName><desc>characterizes the type of segment.</desc><datatype>CDATA</datatype><valDesc>For a <gi tei="yes">cl</gi> may take values such as finite, nonfinite,
declarative, interrogative, relative etc. For a <gi tei="yes">phr</gi> or
<gi tei="yes">w</gi>, values such as noun, verb, preposition, etc., may be used. For
an <gi tei="yes">m</gi> element, values such as clitic, prefix, stem will be more
appropriate. For a <gi tei="yes">c</gi> element, values such as letter, punctuation,
digit may be used.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>function</attName><desc>characterizes the function of the segment.</desc><datatype>CDATA</datatype><valDesc>For a <gi tei="yes">cl</gi>, may take values such as
coordinate, subject, adverbial etc. For a <gi tei="yes">phr</gi>, such values as
subject, predicate etc. may be more appropriate.</valDesc><default>#IMPLIED</default></attDef><attDef usage="mwa"><attName>part</attName><desc>specifies whether or not the segment is fragmented by some other
structural element, for example a clause which is divided between two
or more sentences.</desc><datatype>(Y | N | I | M | F)</datatype><valList type="closed"><val>Y</val><desc>the segment is incomplete in some respect</desc><val>N</val><desc>either the segment is complete, or no claim is made as to
its completeness.</desc><val>I</val><desc>the initial part of an incomplete segment</desc><val>M</val><desc>a medial part of an incomplete segment</desc><val>F</val><desc>the final part of an incomplete segment</desc></valList><default>N</default><remarks><p>The values I, M, or F should be used only where it is
clear how the segment is to be reconstituted.</p></remarks></attDef></attList><remarks><p>The principles on which segmentation is carried out, and
any special codes or attribute values used, should be defined explicitly
in the <gi tei="yes">segmentation</gi> element of the <gi tei="yes">encodingDesc</gi> within
the associated TEI header.</p></remarks><part type="base" name="core"/><classes names="PHRASE"/><xref target="SASE"/><xref target="AILC"/></classDoc><?tei:EOF clseg.cla ??><!-- seg class --><?tei:SOF sgmlkw.cla ??><!-- ************************************************* sgmlkw --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	sgmlkw.cla,v $
# Revision 1.3  93/09/15  23:02:26  msmcq
# Changes as of mid-September
# 
# Revision 1.2  1993/09/08  23:43:53  msmcq
# add phrase as parent class
#
# Revision 1.1  1993/09/08  22:52:48  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : rename class                            --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-09-08 : MSM : made file                               --><!-- ************************************************* sgmlkw --><classDoc id="SGMLKW" type="model"><class>sgmlKeywords</class><name>SGML keywords</name><desc>elements whose content is an SGML identifier or tag of some sort
(generic identifier of an element type, name of an attribute, etc.).</desc><attList></attList><remarks><p>These elements are defined in the auxiliary tag set for
tag set documentation; they may be useful in writing SGML documentation
as well.</p></remarks><part type="aux" name="tsd"/><classes names="PHRASE"/><xref target="TD"/></classDoc><?tei:EOF sgmlkw.cla ??><!-- sgmlKeywords --><?tei:SOF singval.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	singval.cla,v $
# Revision 1.1  94/04/08  01:44:01  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class featval                    --><!-- 94-04-07 : MSM : made file                               --><!-- ************************************************ singVal --><classDoc id="SINGVAL" type="model"><class>singleVal</class><name>single values</name><desc>elements which express single feature values in feature structures.</desc><attList></attList><part type="top" name="fs"/><classes names="FEATVAL"/><xref target="FD"/></classDoc><?tei:EOF singval.cla ??><!-- singleVal class --><!-- &dftspok --><!-- spoken class (default) --><?tei:SOF stagedir.cla ??><!-- ***************************************** stageDirection --><!-- Revisions:                                               --><!-- 93-08-19 : MSM : add to class perf                       --><!-- 93-08-19 : MSM : made file                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	stagedir.cla,v $
# Revision 1.3  93/12/20  16:35:05  lou
# changed class name from perf to compdram
# 
# Revision 1.2  1993/08/23  22:54:02  msmcq
# add RCS log keywords
# --><!-- ***************************************** stageDirection --><classDoc id="STAGEDIR" type="model"><class>stageDirection</class><name>stage directions</name><desc>groups elements for specialized
stage directions defined in the additional tag set for performance
texts.</desc><attList></attList><remarks><p>Stage directions are members of class <term>inter</term>:
that is, they can appear between or within component-level elements.</p></remarks><part type="top" name="perf"/><classes names="COMPDRAM INTER"/><xref target="DROTH"/></classDoc><?tei:EOF stagedir.cla ??><!-- stageDirection class --><?tei:SOF teiform.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teiform.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-04-07 : MSM : uppercase TEI                           --><!-- ************************************************ teiform --><classDoc id="TEIFORM" type="atts"><class>TEIform</class><name>TEI name form</name><desc>defines an attribute (<att tei="yes">TEIform</att>) common to all tags in
the TEI scheme, and recommended for all user-defined extensions.</desc><attList><!-- ................................................ TEIform --><attDef usage="mwa"><attName>form</attName><name>TEI form of generic identifier</name><desc>indicates the standard TEI name (generic identifier) for a given
element.</desc><datatype>NAME</datatype><valDesc>must be a valid SGML name; the default is specified in</valDesc><default>#IMPLIED</default><eg><![CDATA[ <fn form=note>This is a footnote; its tag uses a non-standard
  name defined by the user; the attribute TEIform indicates that
  the normal TEI name for the element is NOTE.</fn>]]></eg><remarks><p>In the TEI DTDs, the default value for this attribute is
always the same as the generic identifier of the element.  If an element
is renamed using the techniques described in chapter <xref target="MD"/>,
the attribute declaration for <att tei="yes">TEIform</att> will be left
undisturbed; the default value will thus still be the standard TEI name
for the element.  TEI-aware application programs can thus process
TEI-conformant documents which rename TEI elements, since by consulting
the <att tei="yes">TEIform</att> attribute value the application can learn the
standard name for the element and process it accordingly.
 </p><p>In the normal course of events, this attribute will never be
specified in a TEI-conformant document; all occurrences will have the
default value.  In some special circumstances, it can be useful to
specify a non-default value on some instances of an element; this allows
application programs to process correctly a locally defined element
which usually corresponds to one TEI element (which would be expressed
by the default value) but sometimes to another TEI element (which would
be expressed by explicit values attached to the element instance).
 </p></remarks></attDef></attList><remarks><p>The attribute <att tei="yes">TEIform</att>, though common to all tags
in the TEI encoding scheme, is not defined as part of the
<term>global</term> class for technical reasons.  Since its default
value must be specified separately for each element type, no elements
actually inherit the attribute from the element class
<term>TEIform</term>; each defines the attribute separately.
 </p></remarks><part type="base" name="core"/><classes/><xref target="STGA"/></classDoc><?tei:EOF teiform.cla ??><!-- TEIform class --><?tei:SOF tempexp.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tempexp.cla,v $
# Revision 1.4  94/03/25  15:48:19  msmcq
# add explicit end-tags for attdef parts
# correct error in declared value (add parens)
# 
# Revision 1.3  1994/03/07  16:13:28  lou
# initial check in of ND
#
# Revision 1.2  1993/08/02  21:34:03  msmcq
# change name
# --><!-- Revisions:                                               --><!-- 94-03-21 : MSM : correct error in datatype nm grp        --><!-- 93-06-21 : MSM : change name                             --><classDoc id="TEMPEXP" type="atts"><class>temporalExpr</class><name>temporal expression</name><desc>groups component elements of temporal expressions
involving dates and time.</desc><attList><attDef usage="opt"><attName>value</attName><desc>supplies the value of a date or time in a standard form.</desc><datatype>CDATA</datatype><valDesc>Any string representing a temporal expression in standard
format; recommended form is <q>yyyy-mm-dd</q>, as defined by ISO 8601:
1988, <title>Data elements and interchange formats --- Information
interchange --- Representation of dates and times.</title></valDesc><default>#IMPLIED</default><remarks><p>The standard form used should be described in the
<gi tei="yes">stdVals</gi> element in the TEI header.  Standard forms may be
defined from scratch, or borrowed from existing practice.</p></remarks></attDef><attDef usage="mwa"><attName>type</attName><desc>provides any application-, linguistic- or culture-specific
classication for the component.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg><![CDATA[<dateStruct value='14-05-1993'>
 <day type=nominal>Friday</day>,
 <day type=numeric>14</day>
 <month type=nominal>May</month>
 <year type=nominal value='1993'>
   in the year of our Lord One Thousand
   Nine Hundred and Ninety Three
 </year>
</dateStruct>]]></eg></attDef><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a normalized or regularized form of the temporal expression.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>In providing a <soCalled>regularized</soCalled> form, no
claim is made that the form in the source text is incorrect; the
regularized form is simply that chosen as the main form for purposes
of unifying variant forms under a single heading.
<eg><![CDATA[<dateStruct value='09-06-1807'>
  <month>June</month> <day reg='9'>9th</day>
</dateStruct>:
The period is approaching which will terminate my
present copartnership. On the
  <dateStruct value='01-01-1808'>
     <day reg='1'>1st</day>
     <month reg='January'>Jany.</month>
   </dateStruct>
next, it expires by its own limitation.
 
At <time><event reg='evening'>sunset</event></time> we walked
walked to the beach.]]></eg></p></remarks></attDef><attDef usage="opt"><attName>full</attName><desc>indicates whether the date element is given in full, as an
abbreviation or simply as an initial</desc><datatype>(yes | abb | init)</datatype><valList type="closed"><val>yes</val><desc>the name component is spelled out in full.</desc><val>abb</val><desc>the name component is given in an
abbreviated form.</desc><val>init</val><desc>the name component is indicated only by
one initial.</desc></valList><default>yes</default></attDef></attList><remarks></remarks><part type="top" name="ND"/><classes/><xref target="NDDATE"/></classDoc><?tei:EOF tempexp.cla ??><!-- temporalExpr class --><?tei:SOF dftterm.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dftterm.cla,v $
# Revision 1.1  93/09/15  23:02:26  msmcq
# Changes as of mid-September
# 
# Revision 1.1  1993/08/02  21:21:23  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : make DFT version                        --><!-- 93-06-03 : MSM : new id:  clterm not basete              --><!-- 93-06-03 : MSM : rename class:  terminology not base     --><!-- 20 may 93  : LB add grpPtr and depPtr post Eynsham       --><!-- examples are still needed                                --><!-- 92-12-21 : MSM : rename file from flatterm               --><!-- 92-12-18 : MSM : modify name, description                --><!-- ************************************************* baseTE --><classDoc id="DFTTERM" type="atts"><class>terminology</class><name>global attributes for terminological data.</name><desc>default declaration for class <term>terminology</term>:
when the base tag set for terminological data is not selected,
no attributes are defined for this class.</desc><attList></attList><remarks></remarks><part type="base" name="term"/><classes/><xref target="STGA"/></classDoc><?tei:EOF dftterm.cla ??><!-- terminology class (default) --><?tei:SOF clterm.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clterm.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-06-03 : MSM : new id:  clterm not basete              --><!-- 93-06-03 : MSM : rename class:  terminology not base     --><!-- 20 may 93  : LB add grpPtr and depPtr post Eynsham       --><!-- examples are still needed                                --><!-- 92-12-21 : MSM : rename file from flatterm               --><!-- 92-12-18 : MSM : modify name, description                --><!-- ************************************************* baseTE --><classDoc id="CLTERM" type="atts"><class>terminology</class><name>global attributes for terminological data.</name><desc>defines attributes for all elements in documents which use the
base tag set for terminological data.</desc><attList><!-- .................................................. group --><attDef usage="opt"><attName>group</attName><desc>indicates the group (term and related elements) to which this
element should be associated by specifying a string matching the
<att tei="yes">n</att> attribute value on an appropriate element.</desc><datatype>CDATA</datatype><valDesc>any string matching the <att tei="yes">n</att> attribute value on the
<gi tei="yes">term</gi> element to which the group is attached.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The <att tei="yes">group</att> attribute provides a specialized
pointing mechanism for use within <gi tei="yes">termEntry</gi> elements.</p></remarks></attDef><!-- .................................................. grpPtr --><attDef usage="opt"><attName>grpPtr</attName><desc>indicates the group (term and related elements) to which this
element should be associated by specifying its unique identifier,
where this is available.</desc><datatype>IDREF</datatype><valDesc>the value specified must match a value supplied as the value
for an <att tei="yes">id</att> attribute on some
<gi tei="yes">term</gi> element in the current SGML document.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The <att tei="yes">group</att> attribute provides a specialized
pointing mechanism for use within <gi tei="yes">termEntry</gi> elements.</p></remarks></attDef><!-- ................................................. depend --><attDef usage="opt"><attName>depend</attName><desc>indicates the parent element to which this element should be
associated by specifying a string matching the
<att tei="yes">n</att> attribute value on an appropriate element.</desc><datatype>CDATA</datatype><valDesc>any string matching the <att tei="yes">n</att> attribute value on the
element to which the dependent element is attached.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................. depPtr --><attDef usage="opt"><attName>depPtr</attName><desc>indicates the parent element to which this element should be
associated by specifying its unique identifier, where this is available.</desc><datatype>IDREF</datatype><valDesc>the value specified must match a value supplied as the value
for an <att tei="yes">id</att> attribute on some
<gi tei="yes">term</gi> element in the current SGML document.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks></remarks></attDef></attList><remarks><p>The attributes shared by this element class are used for
linking elements, possibly not adjacent in the record, which are related
(e.g. a grammatical annotation and the term it describes).
If no attribute is specified, the element is assumed to
relate to the most recently specified <gi tei="yes">term</gi> or
<gi tei="yes">otherForm</gi> element.<!-- The usual --><!-- ID/IDREF-based pointing mechanisms are not used, primarily because the --><!-- requirement that SGML ID values be unique within a document places an --><!-- impractical burden on the encoder when terminological data from several --><!-- sources are to be merged. --></p></remarks><part type="base" name="term"/><classes/><xref target="TETA"/><xref target="TEFLNE"/><xref target="TEDT"/></classDoc><?tei:EOF clterm.cla ??><!-- terminology class --><?tei:SOF termincl.cla ??><!-- ********************************** terminologyInclusions --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	termincl.cla,v $
# Revision 1.2  93/12/20  18:08:07  lou
# changed id to match filename
# 
# Revision 1.1  1993/09/15  23:02:26  msmcq
# Changes as of mid-September
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : made file                               --><!-- ********************************** terminologyInclusions --><classDoc id="TERMINCL" type="model"><class>terminologyInclusions</class><desc>elements which may be included at any point within a
terminology entry.</desc><attList></attList><remarks></remarks><part type="base" name="term"/><classes/><xref target="TE"/></classDoc><?tei:EOF termincl.cla ??><!-- terminologyInclusions --><?tei:SOF termmisc.cla ??><!-- **************************************** terminologyMisc --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	termmisc.cla,v $
# Revision 1.1  93/09/15  23:02:26  msmcq
# Changes as of mid-September
#  --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : made file                               --><!-- **************************************** terminologyMisc --><classDoc id="TERMMISC" type="model"><class>terminologyMisc</class><name>miscellaneous terminology-data elements</name><desc>elements which can appear together at various points in
terminological entries.</desc><attList></attList><remarks></remarks><part type="base" name="term"/><classes/><xref target="TE"/></classDoc><?tei:EOF termmisc.cla ??><!-- terminologyMisc --><?tei:SOF timed.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	timed.cla,v $
# Revision 1.1  93/08/02  21:21:23  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************** TIMED --><classDoc id="TIMED" type="atts"><class>timed</class><desc>elements which have a duration in time expressed either absolutely
or by reference to an alignment map.</desc><attList><attDef usage="opt"><attName>start</attName><desc>indicates the location within a temporal alignment
      at which this element begins.</desc><datatype>IDREF</datatype><valDesc>contains the identifier of a previously defined <gi tei="yes">loc</gi>
element</valDesc><default>#IMPLIED</default><remarks><p>If no value is supplied, the element is assumed to follow
   the immediately preceding element at the same hierarchic level.</p></remarks></attDef><attDef usage="opt"><attName>end</attName><desc>indicates the location within a temporal alignment at which
   this element ends.</desc><datatype>IDREF
   </datatype><valDesc>contains the identifier of a previously defined <gi tei="yes">loc</gi>
   element</valDesc><default>#IMPLIED
   </default><remarks><p>If no value is supplied, the element is assumed to
precede the immediately following element at the same hierarchic level.
   </p></remarks></attDef><attDef usage="opt"><attName>dur</attName><name>duration</name><desc>indicates the length of this element in time, using either
         specific units or the units specified on the associated temporal
         alignment.
   </desc><datatype>CDATA
   </datatype><valDesc>contains a number optionally followed by a standard unit
         indicator</valDesc><default>#IMPLIED
  </default><remarks><p>If units are not defaulted, they should be represented
         using standard abbreviations (s for second, m for minute, etc.)</p></remarks></attDef></attList><part type="base" name="spoken"/><classes/><xref target="TSBATI"/></classDoc><?tei:EOF timed.cla ??><!-- timed class --><?tei:SOF tpparts.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: tpparts.cla,v $
    * Revision 1.3  1998/01/31 19:13:36  tei
    * fixed log keyword (!)
    *
    * Revision 1.2  1998/01/31 18:28:30  tei
    * *** empty log message ***
    * 
    * Revision 1.1  93/08/02  21:21:23  msmcq
    * Initial revision
    *--><!-- ************************************************* tpParts.cla --><classDoc id="TPPARTS" type="model"><class>tpParts</class><name>Title page elements</name><desc>This class groups elements which can occur as direct constituents
of a title page (<gi tei="yes">docTitle</gi>, <gi tei="yes">docAuth</gi>,
<gi tei="yes">docImprint</gi>, <gi tei="yes">epigraph</gi>, etc.)</desc><attList></attList><part type="base" name="core"/><classes/><xref target="DSTITL"/></classDoc><?tei:EOF tpparts.cla ??><!-- tpParts class --><?tei:SOF typed.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	typed.cla,v $
# Revision 1.1  98/01/28  19:23:20  tei
# Initial revision
# 
    *--><!-- Revisions:                                               --><!-- 8 Jan 98 : LB : made tagdoc --><classDoc id="TYPED" type="atts"><class>typed</class><desc>elements for arbitrary segmentation. </desc><attList><attDef usage="opt"><attName>type</attName><desc>characterizes the element in some sense, using any convenient
 classification scheme or typology.</desc><datatype>CDATA</datatype><valDesc>any string of characters. The range of permissible values
is application dependent.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>subtype</attName><desc>provides a sub-categorization of the element, if needed</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>The <att tei="yes">subtype</att> attribute may be used to provide any
sub-classification for the element, additional to that provided by its
<att tei="yes">type</att> attribute.</p></remarks></attDef></attList><remarks><p>The typology used may be formally defined using
the  the <gi tei="yes">classification</gi> element of the <gi tei="yes">encodingDesc</gi> within
the associated TEI header, or informally as descriptive prose within
the <gi tei="yes">encodingDesc</gi> element.</p></remarks><part type="base" name="core"/><classes/><xref target="STECAT"/><!-- is that all?--></classDoc><?tei:EOF typed.cla ??><!-- timed class --><?tei:SOF xpointer.cla ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	xpointer.cla,v $
# Revision 1.5  94/04/08  01:44:01  msmcq
# cosmetic
# 
# Revision 1.4  1994/03/16  03:47:37  msmcq
# add health warning about subdoc/non-sgml requirement\
#
# Revision 1.3  1994/01/15  20:53:03  msmcq
# fix missing default value
#
# Revision 1.2  1993/09/22  18:57:37  msmcq
# minor fixes.
#
# Revision 1.2  1993/09/22  18:57:37  msmcq
# minor fixes.
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************************* extPointer --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : shorten line in example                 --><!-- 94-03-15 : MSM : add health warning about DOC att        --><!-- 94-03-15 : MSM : (subdoc or non-sgml entity)             --><!-- 94-01-12 : MSM : provide default att val                 --><!-- 93-09-13 : MSM : double quotes around DITTO              --><!-- 93-09-13 : MSM : case sensitivity of extPtr keyword      --><!-- 1993-03-24 : MSM : made file for publication of ST       --><!--                    (SA needs to be changed to agree)     --><classDoc id="XPOINTER" type="atts"><class>xPointer</class><name>extended-pointer elements</name><desc>groups elements which use the TEI extended pointer mechanism to
point at locations which have no SGML ID.</desc><attList><!-- .................................................... doc --><attDef usage="mwa"><attName>doc</attName><name>document or file</name><desc>specifies the document within which the desired location is to be
found.</desc><datatype>ENTITY</datatype><valDesc>The name of a system entity associated with the document within
which the target of this extended pointer is to be found, by default the
current document.</valDesc><default>#IMPLIED</default><eg><![CDATA[ <xptr doc='Chap2' from='id (e23)'>]]></eg><remarks><p>The system entity named by this attribute must be declared
(as a SUBDOC entity or a non-SGML entity)
in the DTD of the document containing the extended pointer.</p></remarks></attDef><!-- ................................................... from --><attDef usage="mwa"><attName>from</attName><desc>specifies the start of the destination of the pointer, as an
expression in the TEI extended-pointer notation described in section<xref target="SAXR"/>
.</desc><datatype>%extPtr;</datatype><valDesc>The value specified must be a valid expression in the TEI
extended pointer notation defined in section <xref target="SAXR"/>.</valDesc><default>"ROOT"</default><eg><![CDATA[ ]]></eg><remarks><p>If no value is specified, the target is the whole of the
document identified by the <att tei="yes">doc</att> attribute.</p></remarks></attDef><!-- ..................................................... to --><attDef usage="mwa"><attName>to</attName><desc>specifies the endpoint of the destination of the pointer, as an
expression in the TEI extended pointer notation.</desc><datatype>%extPtr;</datatype><valDesc>The value specified must be a valid expression in the TEI
extended pointer notation defined in section <xref target="SAXR"/>.</valDesc><default>"DITTO"</default><eg><![CDATA[ <xptr doc=OrbisPictus from='id (animalia)'
       to='id (aquaticae)'>]]></eg><remarks><p>This attribute may only be supplied if the <att tei="yes">from</att>
attribute is also supplied, in which case the destination is defined to
extend from the beginning of the location specified by the
<att tei="yes">from</att> attribute, up to the end of that specified by the
<att tei="yes">to</att> attribute.  It is an error for the <att tei="yes">to</att>
attribute to specify a location whose end precedes the beginning of the
location specified by <att tei="yes">from</att>; it is not an error for the scopes
to overlap.</p><p>If no value is specified, the target is the location specified by the
<att tei="yes">from</att> attribute.</p></remarks></attDef></attList><remarks><p>This class belongs to the larger class <term>pointer</term>,
which means its elements also inherit the attributes of that class.</p></remarks><part type="top" name="xrefs"/><classes names="POINTER"/><xref target="SAXR"/></classDoc><?tei:EOF xpointer.cla ??><!-- xPointer class --></div1><div1 id="REFENT" n="34" name="Faisal" ref="Y"><head>Entities</head><!-- entities --><!-- &lmcomp  --><!-- component (letters) entity --><!-- &lmgenxx --><!-- gen.lm         entity 2 --><!-- &ceent --><!-- TEI.certainty.ent entity --><!-- &lmgen   --><!-- TEI.letters.         entity --><!-- &lmdtd   --><!-- TEI.letters.dtd entity --><!-- &lment   --><!-- TEI.letters.ent entity --><!-- &lmtop   --><!-- TEI.letters.top entity --><!-- &chkseq  --><!-- chunk.seq entity --><?tei:SOF dicomp.ent ??><!-- Revisions:                                               --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dicomp.ent,v $
# Revision 1.2  93/09/16  14:54:10  msmcq
# Changes at publication of TD:  dictionar-ies
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************** dicomp.ent --><entDoc id="DICOMP" type="pe"><entName>component</entName><name>component for dictionaries</name><desc>defines the set of component-level elements for dictionaries;
these are elements which can appear directly within text bodies or text
divisions.</desc><string>'(%m.common | %m.comp.dictionaries)'</string><xref target="STEC"/></entDoc><?tei:EOF dicomp.ent ??><!-- component (dictionaries) entity --><?tei:SOF drcomp.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drcomp.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ****************************************** drcomp.ent --><entDoc id="DRCOMP" type="pe"><entName>component</entName><name>component for drama</name><desc>defines the set of component-level elements for drama; these are
elements which can appear directly within text bodies or text divisions.</desc><string>'(%m.common | %m.comp.drama)'</string><xref target="STEC"/></entDoc><?tei:EOF drcomp.ent ??><!-- component (drama) entity --><?tei:SOF cbcomp.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbcomp.ent,v $
# Revision 1.3  94/04/01  17:27:23  msmcq
# Changes while validating DTD
# 
# Revision 1.2  1993/09/16  14:51:48  msmcq
# Changes at publication of TD (dictionar-ies)
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : close the paren!                        --><!-- 94-03-31 : MSM : delete %mix.letters (for P3)            --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- **************************************** cbcomp.ent --><entDoc id="CBCOMP" type="pe"><entName>component</entName><name>component for mixed or general base</name><desc>defines the set of component-level elements for use with the mixed
or general base; these are elements which can appear directly within
text bodies or text divisions.
 </desc><string>'(%m.common %mix.verse %mix.drama %mix.spoken
%mix.dictionaries %mix.terminology)'</string><xref target="STEC"/></entDoc><!-- Note:  what we want is some *subset* of                  --><!-- '%m.common | %m.comp.verse | %m.comp.drama |             --><!-- %m.comp.spoken | %m.comp.letters | %m.comp.dictionaries |  --><!-- %m.comp.terminology '                                    --><!--                                                          --><!-- We get this by piecing it together out of perefs:        --><!--                                                          --><!-- %m.common                                                --><!-- %mix.verse         i.e. | %m.comp.verse                  --><!-- %mix.drama              | %m.comp.drama                  --><!-- %mix.spoken             | %m.comp.spoken                 --><!-- %mix.letters            | %m.comp.letters                --><!-- %mix.dictionaries       | %m.comp.dictionaries           --><!-- %mix.terminology        | %m.comp.terminology            --><?tei:EOF cbcomp.ent ??><!-- component (general, mixed) entity --><?tei:SOF prcomp.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	prcomp.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ****************************************** prcomp.ent --><entDoc id="PRCOMP" type="pe"><entName>component</entName><name>component for prose</name><desc>defines the set of component-level elements for prose; these are
elements which can appear directly within text bodies or text divisions.</desc><string>'(%m.common)'</string><xref target="STEC"/></entDoc><?tei:EOF prcomp.ent ??><!-- component (prose) entity --><?tei:SOF tscomp.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tscomp.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ****************************************** tscomp.ent --><entDoc id="TSCOMP" type="pe"><entName>component</entName><name>component for transcription of spoken texts</name><desc>defines the set of component-level elements for spoken texts;
these are elements which can appear directly within text bodies or
text divisions.</desc><string>'(%m.common | %m.comp.spoken)'</string><xref target="STEC"/></entDoc><?tei:EOF tscomp.ent ??><!-- component (spoken) entity --><?tei:SOF tecomp.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tecomp.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ****************************************** tecomp.ent --><entDoc id="TECOMP" type="pe"><entName>component</entName><name>component for terminology</name><desc>defines the set of component-level elements for terminology; these are
elements which can appear directly within text bodies or text divisions.</desc><string>'(%m.common | %m.comp.terminology)'</string><xref target="STEC"/></entDoc><?tei:EOF tecomp.ent ??><!-- component (terminology) entity --><?tei:SOF vecomp.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vecomp.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ****************************************** vecomp.ent --><entDoc id="VECOMP" type="pe"><entName>component</entName><name>component for verse</name><desc>defines the set of component-level elements for verse; these are
elements which can appear directly within text bodies or text divisions.</desc><string>'(%m.common | %m.comp.verse)'</string><xref target="STEC"/></entDoc><?tei:EOF vecomp.ent ??><!-- component (verse) entity --><?tei:SOF cbgeplus.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbgeplus.ent,v $
# Revision 1.3  94/09/09  01:30:41  msmcq
# reformat string (change originally made 31 Mar 94, lost, refound)
# 
# Revision 1.2  1993/09/16  14:51:48  msmcq
# Changes at publication of TD (dictionar-ies)
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : reformat string                         --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- 93-04-07 : MSM : rename tei...endseq as tei...end        --><!-- ****************************************** cbgeplus.ent --><entDoc id="CBGEPLUS" type="pe"><entName>component.plus</entName><name>component sequence</name><desc>defines a sequence of components as needed in the general base tag
set, allowing components from any base to be used, but preventing their
mixing.</desc><remarks><p>When used in a content model, this entity requires at least
one component-level element to occur.</p></remarks><string>'(%gen.verse %gen.drama %gen.spoken %gen.dictionaries %gen.terminology
TEI...end)
|
( (%m.common)+, (%gen.verse %gen.drama %gen.spoken %gen.dictionaries
%gen.terminology TEI...end)?'</string><xref target="STEC"/></entDoc><?tei:EOF cbgeplus.ent ??><!-- component.plus (CB general) entity --><?tei:SOF cbgeseq.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbgeseq.ent,v $
# Revision 1.3  94/04/01  17:27:23  msmcq
# Changes while validating DTD
# 
# Revision 1.2  1993/09/16  14:51:48  msmcq
# Changes at publication of TD (dictionar-ies)
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : reformat string                         --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- 93-06-02 : MSM : suppress tag within NAME                --><!-- 93-04-07 : MSM : add base name to name element           --><!-- 93-04-07 : MSM : rename tei...endseq as tei...end        --><!-- ****************************************** cbgeseq.ent --><entDoc id="CBGESEQ" type="pe"><entName>component.seq</entName><name>component sequence for general combined base</name><desc>defines a sequence of components as needed in the general base tag
set, allowing components from any base to be used, but preventing their
mixing.</desc><remarks><p>When used in a content model, this entity, like other
entities with names of the form <q>x.seq</q>, allows zero or more
occurrences of its content to occur.</p></remarks><string>'(%m.common)*, (%gen.verse %gen.drama %gen.spoken %gen.dictionaries
%gen.terminology TEI...end)?'</string><xref target="STEC"/></entDoc><?tei:EOF cbgeseq.ent ??><!-- component.seq (CB general) entity --><?tei:SOF compseq.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	compseq.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ****************************************** component.seq --><!-- Revisions:                                               --><!-- 1993-03-24 : MSM : made file for ST publication          --><entDoc id="COMPSEQ" type="pe"><entName>component.seq</entName><name>component-sequence</name><desc>defines a sequence of component-level elements (such as paragraphs
or lists) which can occur directly within text divisions and in similar
positions.</desc><remarks><p>This parameter entity is used in each base tag set to
define the content of <gi tei="yes">div</gi> and similar elements.</p></remarks><string>'(%component;)*'</string><xref target="STEC"/></entDoc><?tei:EOF compseq.ent ??><!-- component.seq entity --><?tei:SOF extptr.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	extptr.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************************* extPtr --><!-- Revisions:                                               --><!-- 93-03-29 : MSM : correct ref from saxptr to saxr1        --><!-- 1993-03-24 : MSM : made file for publication of ST       --><!--                    (xptr, xref tagdocs must be changed)  --><entDoc id="EXTPTR" type="pe"><entName>extPtr</entName><name>extended-pointer expression</name><desc>used as the declared value of an attribute, indicates that all
values of that attribute must be valid expressions in the TEI extended
pointer notation defined in section <xref target="SAXR1"/>.</desc><remarks><p></p></remarks><string>'CDATA'</string><xref target="SAXR1"/></entDoc><?tei:EOF extptr.ent ??><!-- extPtr entity (TEI keyword --><?tei:SOF formcont.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- ******************************************** formulaContent --><entDoc id="FORMCONT" type="pe"><entName>formulaContent</entName><desc>defines the content model for the <gi tei="yes">formula</gi> element.</desc><remarks></remarks><string>'CDATA' </string><xref target="FTFOR"/></entDoc><?tei:EOF formcont.ent ??><!-- formulaContent entity --><?tei:SOF formnotn.ent ??><!-- **************************************** formulaNotation --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	formnotn.ent,v $
# Revision 1.1  94/03/01  04:08:00  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-02-28 : MSM : add pluralizing s                       --><!-- 94-02-25 : MSM : change id to agree with filename        --><!-- 94-02-25 : MSM : Added RCS id                            --><!-- **************************************** formulaNotation --><entDoc id="FORMNOTN" type="pe"><entName>formulaNotations</entName><desc>specifies the set of notations which may be used for the
<gi tei="yes">formula</gi> element.</desc><remarks><p>This will normally be defined either as
<code tei="yes" type="kw">CDATA</code> (the default), or as a string such as
<code tei="yes" type="decl">NOTATION (tex | eqn)</code></p></remarks><string>'CDATA'</string><xref target="FTFOR"/></entDoc><?tei:EOF formnotn.ent ??><!-- formulaNotation entity --><?tei:SOF digen.ent ??><!-- Revisions:                                               --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	digen.ent,v $
# Revision 1.2  93/09/16  14:54:10  msmcq
# Changes at publication of TD:  dictionar-ies
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************************** digen.ent --><entDoc id="DIGEN" type="pe"><entName>gen.dictionaries</entName><name>dictionary part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><string>'((%m.comp.dictionaries), (%m.common | %m.comp.dictionaries)*) |'</string><xref target="STEC"/></entDoc><?tei:EOF digen.ent ??><!-- gen.dictionaries entity --><?tei:SOF digenxx.ent ??><!-- Revisions:                                               --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	digenxx.ent,v $
# Revision 1.2  93/09/16  14:54:10  msmcq
# Changes at publication of TD:  dictionar-ies
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************************** digenxx.ent --><entDoc id="DIGENXX" type="pe"><entName>gen.dictionaries</entName><name>dictionary part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><remarks><p>This version of this entity is used if the dictionary base
is not selected.</p></remarks><string>''</string><xref target="STEC"/></entDoc><?tei:EOF digenxx.ent ??><!-- gen.dictionaries entity 2 --><?tei:SOF drgen.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drgen.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** drgen.ent --><entDoc id="DRGEN" type="pe"><entName>gen.drama</entName><name>drama part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><string>'((%m.comp.drama), (%m.common | %m.comp.drama)*) |'</string><xref target="STEC"/></entDoc><?tei:EOF drgen.ent ??><!-- gen.drama entity --><?tei:SOF drgenxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drgenxx.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** drgenxx.ent --><entDoc id="DRGENXX" type="pe"><entName>gen.drama</entName><name>drama part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><remarks><p>This version of this entity is used if the drama base is not
selected.</p></remarks><string>''</string><xref target="STEC"/></entDoc><?tei:EOF drgenxx.ent ??><!-- gen.drama entity 2 --><?tei:SOF tsgen.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsgen.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** tsgen.ent --><entDoc id="TSGEN" type="pe"><entName>gen.spoken</entName><name>spoken-text part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><string>'((%m.comp.spoken), (%m.common | %m.comp.spoken)*) |'</string><xref target="STEC"/></entDoc><?tei:EOF tsgen.ent ??><!-- gen.spoken entity --><?tei:SOF tsgenxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsgenxx.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** tsgenxx.ent --><entDoc id="TSGENXX" type="pe"><entName>gen.spoken</entName><name>spoken-text part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><remarks><p>This version of this entity is used if the spoken base is not
selected.</p></remarks><string>''</string><xref target="STEC"/></entDoc><?tei:EOF tsgenxx.ent ??><!-- gen.spoken entity 2 --><?tei:SOF tegen.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tegen.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** tegen.ent --><entDoc id="TEGEN" type="pe"><entName>gen.terminology</entName><name>terminology part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><string>'((%m.comp.terminology), (%m.common | %m.comp.terminology)*) |'</string><xref target="STEC"/></entDoc><?tei:EOF tegen.ent ??><!-- gen.terminology entity --><?tei:SOF tegenxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tegenxx.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** tegenxx.ent --><entDoc id="TEGENXX" type="pe"><entName>gen.terminology</entName><name>terminology part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><remarks><p>This version of this entity is used if the terminology
base is not selected.</p></remarks><string>''</string><xref target="STEC"/></entDoc><?tei:EOF tegenxx.ent ??><!-- gen.terminology entity 2 --><?tei:SOF vegen.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vegen.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** vegen.ent --><entDoc id="VEGEN" type="pe"><entName>gen.verse</entName><name>verse part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><string>'((%m.comp.verse), (%m.common | %m.comp.verse)*) |'</string><xref target="STEC"/></entDoc><?tei:EOF vegen.ent ??><!-- gen.verse entity --><?tei:SOF vegenxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vegenxx.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** vegenxx.ent --><entDoc id="VEGENXX" type="pe"><entName>gen.verse</entName><name>verse part of general-base component sequence</name><desc>contains a string used in constructing the definition of
component sequence used in the general base tag set.</desc><remarks><p>This version of this entity is used if the verse base is not
selected.</p></remarks><string>''</string><xref target="STEC"/></entDoc><?tei:EOF vegenxx.ent ??><!-- gen.verse entity --><?tei:SOF inherit.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	inherit.ent,v $
# Revision 1.2  94/04/07  16:46:08  lou
# fix CODEs tagged as Qs
# 
# Revision 1.1  1993/12/20  12:27:01  lou
# Initial revision
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-02-02 : MSM : add end tags                            --><!-- 93-02-02 : MSM : shorten ID to legal length              --><!-- 93-02-02 : MSM : modify for clarity, detail              --><!-- 92-12-21 : MSM : made file                               --><!-- ********************************************** INHERITED --><entDoc id="INHERIT" type="pe"><entName>INHERITED</entName><desc>as a default attribute value, indicates that if not specified, the
attribute value is inherited from corresponding attribute of the parent
element.</desc><remarks><p>For the SGML parser, this entity has the same effect as
specifying a default value as <code tei="yes" type="kw">IMPLIED</code>.  For the
user and the application program, however, <code tei="yes" type="kw">INHERITED</code> has a different effect, specifying as it does
exactly how the application program is to infer the correct default
value: the value is to be inherited from the attribute of the same
name on the immediately enclosing element.  If that element, too,
specifies no value, then its value will have been inherited from its
own immediately enclosing element, etc.  (If the attribute is not
declared for all elements, the value is inherited from the nearest
ancestor for which the attribute is declared.)  </p><p>If no ancestor
element has a value specified for the attribute, the value is
undefined.  Encoders are encouraged to provide an explicit value for
inherited attributes on the outermost elements for which they are
declared; it is, however, not an error for the outermost element to
specify no attribute value for an attribute with a default of <code tei="yes" type="kw">%INHERITED</code>.
</p><p>The most prominent example of attribute value inheritance is the TEI
global attribute <att tei="yes">lang</att>.</p></remarks><string>'#IMPLIED'</string><xref target="STEC"/></entDoc><?tei:EOF inherit.ent ??><!-- INHERITED entity --><?tei:SOF isodate.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	isodate.ent,v $
# Revision 1.3  98/01/28  19:23:53  tei
# LB changes of January 1998
# 
    * Revision 1.2  1994/03/21  14:33:08  lou
    * second major typo purge
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : correct reference to ISO 8601           --><!-- 93-03-30 : MSM : add quotes around string                --><!-- 93-03-03 : MSM : make entdoc for isodate                 --><!-- ************************************************ ISODATE --><entDoc id="ISODATE" type="pe"><entName>ISO-date</entName><desc>as the declared value of an attribute, indicates that the
attribute value should be a legal ISO date in the format defined by ISO
8601:1988, viz. yyyy-mm-dd.</desc><remarks><p>For the SGML parser, this entity has the same effect as
specifying a declared value of <q>CDATA</q>.  For the user and the
application program, however, <q>%ISO-date</q> documents a restriction
which SGML is not currently capable of enforcing.</p><p>The most prominent examples of this declared value type are the
<att tei="yes">value</att> attribute of the <gi tei="yes">date</gi> element in the core tag
set, and the
<att tei="yes">date</att> attribute of the <gi tei="yes">admin</gi> element in the base tag
set for terminology.</p></remarks><string>'CDATA'</string><xref target="STPEKW"/></entDoc><?tei:EOF isodate.ent ??><!-- ISO-date entity --><?tei:SOF dimix.ent ??><!-- Revisions:                                               --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dimix.ent,v $
# Revision 1.2  93/09/16  14:54:10  msmcq
# Changes at publication of TD:  dictionar-ies
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************************** dimix.ent --><entDoc id="DIMIX" type="pe"><entName>mix.dictionaries</entName><name>mixed-base dictionary components</name><desc>contains a string used in constructing the definition of
<term>component</term> used in the mixed base tag set.</desc><string>'| %m.comp.dictionaries'</string><xref target="STEC"/></entDoc><?tei:EOF dimix.ent ??><!-- mix.dictionaries   --><?tei:SOF dimixxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dimixxx.ent,v $
# Revision 1.1  94/04/01  17:22:52  msmcq
# A default declaration for a mix. entity
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file                               --><!-- ******************************************** dimixxx.ent --><entDoc id="DIMIXXX" type="pe"><entName>mix.dictionaries</entName><name>mixed-base dictionaries components</name><desc>default declaration of a string used in constructing the
definition of <term>component</term> used in the mixed base tag set.</desc><string>''</string><xref target="STECMX"/></entDoc><?tei:EOF dimixxx.ent ??><!-- mix.dictionaries 2 --><?tei:SOF drmix.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drmix.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** drmix.ent --><entDoc id="DRMIX" type="pe"><entName>mix.drama</entName><name>mixed-base drama components</name><desc>contains a string used in constructing the definition of
<term>component</term> used in the mixed base tag set.</desc><string>'| %m.comp.drama'</string><xref target="STEC"/></entDoc><?tei:EOF drmix.ent ??><!-- mix.drama          --><?tei:SOF drmixxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drmixxx.ent,v $
# Revision 1.1  94/04/01  17:22:52  msmcq
# A default declaration for a mix. entity
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file                               --><!-- ******************************************** drmixxx.ent --><entDoc id="DRMIXXX" type="pe"><entName>mix.drama</entName><name>mixed-base drama components</name><desc>default declaration of a string used in constructing the
definition of <term>component</term> used in the mixed base tag set.</desc><string>''</string><xref target="STECMX"/></entDoc><?tei:EOF drmixxx.ent ??><!-- mix.drama        2 --><?tei:SOF tsmix.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsmix.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** tsmix.ent --><entDoc id="TSMIX" type="pe"><entName>mix.spoken</entName><name>mixed-base spoken-text components</name><desc>contains a string used in constructing the definition of
<term>component</term> used in the mixed base tag set.</desc><string>'| %m.comp.spoken'</string><xref target="STEC"/></entDoc><?tei:EOF tsmix.ent ??><!-- mix.spoken         --><?tei:SOF tsmixxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsmixxx.ent,v $
# Revision 1.1  94/04/01  17:22:52  msmcq
# A default declaration for a mix. entity
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file                               --><!-- ******************************************** tsmixxx.ent --><entDoc id="TSMIXXX" type="pe"><entName>mix.spoken</entName><name>mixed-base spoken components</name><desc>default declaration of a string used in constructing the
definition of <term>component</term> used in the mixed base tag set.</desc><string>''</string><xref target="STECMX"/></entDoc><?tei:EOF tsmixxx.ent ??><!-- mix.spoken       2 --><?tei:SOF temix.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	temix.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** temix.ent --><entDoc id="TEMIX" type="pe"><entName>mix.terminology</entName><name>mixed-base terminology components</name><desc>contains a string used in constructing the definition of
<term>component</term> used in the mixed base tag set.</desc><string>'| %m.comp.terminology'</string><xref target="STEC"/></entDoc><?tei:EOF temix.ent ??><!-- mix.terminology    --><?tei:SOF temixxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	temixxx.ent,v $
# Revision 1.1  94/04/01  17:22:52  msmcq
# A default declaration for a mix. entity
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file                               --><!-- ******************************************** temixxx.ent --><entDoc id="TEMIXXX" type="pe"><entName>mix.terminology</entName><name>mixed-base terminology components</name><desc>default declaration of a string used in constructing the
definition of <term>component</term> used in the mixed base tag set.</desc><string>''</string><xref target="STECMX"/></entDoc><?tei:EOF temixxx.ent ??><!-- mix.terminology  2 --><?tei:SOF vemix.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vemix.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** vemix.ent --><entDoc id="VEMIX" type="pe"><entName>mix.verse</entName><name>mixed-base verse components</name><desc>contains a string used in constructing the definition of
<term>component</term> used in the mixed base tag set.</desc><string>'| %m.comp.verse'</string><xref target="STEC"/></entDoc><?tei:EOF vemix.ent ??><!-- mix.verse          --><?tei:SOF vemixxx.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vemixxx.ent,v $
# Revision 1.1  94/04/01  17:22:52  msmcq
# A default declaration for a mix. entity
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file                               --><!-- ******************************************** vemixxx.ent --><entDoc id="VEMIXXX" type="pe"><entName>mix.verse</entName><name>mixed-base verse components</name><desc>default declaration of a string used in constructing the
definition of <term>component</term> used in the mixed base tag set.</desc><string>''</string><xref target="STECMX"/></entDoc><?tei:EOF vemixxx.ent ??><!-- mix.verse        2 --><?tei:SOF peparac.ent ??><!-- Revisions:                                               --><!-- 94-04-06 : MSM : suppress remarks element                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	peparac.ent,v $
# Revision 1.2  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.1  1993/12/20  12:53:45  lou
# Initial revision
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************** paraContent --><entDoc id="PEPARAC" type="pe"><entName>paraContent</entName><name>paragraph content</name><desc>defines the legal version for paragraphs and similar elements.<!-- <remarks><p>[Dummy version of entdoc.]</remarks>         --></desc><string>'(#PCDATA | %m.phrase | %m.inter)*'</string><xref target="STEC"/></entDoc><?tei:EOF peparac.ent ??><!-- paraContent entity --><?tei:SOF pephrase.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pephrase.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************************* phrase --><!-- Revisions:                                               --><!-- 93-04-06 : MSM : rename pephrase                         --><!-- 93-03-30 : MSM : delete ^z                               --><!-- 1993-03-24 : MSM : made file                             --><entDoc id="PEPHRASE" type="pe"><entName>phrase</entName><desc>defines a phrase as character data or any phrase-level element.</desc><remarks><p>This entity is used in the declaration of
<term>phrase.seq</term>.</p></remarks><string>'(#PCDATA | %m.phrase)'</string><xref target="STEC"/></entDoc><?tei:EOF pephrase.ent ??><!-- phrase entity --><?tei:SOF phrseq.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	phrseq.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-06-03 : MSM : point to ST not PR7                     --><!-- 93-03-30 : MSM : update replacement string               --><!-- 92-12-10 : MSM : suppress FILES element                  --><!-- ********************************************* phrase.seq --><entDoc id="PHRSEQ" type="pe"><entName>phrase.seq</entName><name>phrase sequence</name><desc>defines a sequence of character data and phrase-level elements.<!-- files names='TEI2'> --></desc><string>'(%phrase;)*' </string><xref target="STECST"/></entDoc><?tei:EOF phrseq.ent ??><!-- phrase.seq entity --><?tei:SOF seqte.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	seqte.ent,v $
# Revision 1.2  94/01/04  00:30:40  msmcq
# change m.terminology to m.comp.terminology
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-10-05 : MSM : change string:  refer to comp.terminology --><!-- 93-10-05 : MSM : not m.terminology                       --><!-- 92-12-21 : MSM : made file from SEQ ent                  --><!-- ************************************************** seqte --><entDoc id="SEQTE" type="pe"><entName>seq</entName><name>sequence</name><desc>defines a sequence of elements (such as paragraphs)
which can occur directly within text divisions and in similar
positions.</desc><remarks><p>This parameter entity is used in each base tag set to
define the content of <gi tei="yes">div</gi> and other elements.<!-- files names='TEIPROS2'> --></p></remarks><string>'(%m.common; | %m.comp.terminology;)* ' </string><xref target="TEDT"/></entDoc><?tei:EOF seqte.ent ??><!-- seq entity --><?tei:SOF pespecp.ent ??><!-- Revisions:                                               --><!-- 94-04-06 : MSM : suppress remarks element                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pespecp.ent,v $
# Revision 1.2  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.1  1993/12/20  12:55:09  lou
# Initial revision
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************** specialPara --><entDoc id="PESPECP" type="pe"><entName>specialPara</entName><name>'special' paragraph content</name><desc>defines the content model of elements such as notes or list items,
which either contain a series of component-level elements or else have
the same structure as a paragraph, containing a series of phrase-level
and inter-level elements.<!-- <remarks><p>[Dummy.]</remarks>                           --></desc><string>'(((%m.chunk), (%component.seq)) | (%paraContent))'</string><xref target="STEC"/></entDoc><?tei:EOF pespecp.ent ??><!-- specialPara entity --><?tei:SOF aidtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	aidtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.analysis.dtd --><!-- Revisions:                                               --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><entDoc id="AIDTD" type="pe"><entName>TEI.analysis.dtd</entName><name>TEI analysis-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for simple analysis.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for simple analysis.</p></remarks><string>system 'teiana2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF aidtd.ent ??><!-- TEI.analysis.dtd entity --><?tei:SOF aient.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	aient.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.analysis.ent --><!-- Revisions:                                               --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><entDoc id="AIENT" type="pe"><entName>TEI.analysis.ent</entName><name>TEI analysis-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the base tag set for simple analysis.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for simple analysis.</p></remarks><string>system 'teiana2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF aient.ent ??><!-- TEI.analysis.ent entity --><?tei:SOF aitop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	aitop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.analysis --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="AITOP" type="pe"><entName>TEI.analysis</entName><name>TEI simple analytic mechanisms DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for simple analytic mechanisms.</desc><remarks><p>To include elements and attributes for simple analytic
mechanisms in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF aitop.ent ??><!-- TEI.analysis.top entity --><?tei:SOF teiback.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teiback.ent,v $
# Revision 1.3  93/10/05  11:13:42  lou
# lower case file name
# 
# Revision 1.2  1993/09/16  14:59:12  msmcq
# Update xref target at publ. of TD
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : change xref:  pr5 to dsback             --><!-- 93-03-30 : MSM : add suffix '.dtd'                       --><!-- 92-12-10 : MSM : suppress FILES element                  --><!-- *********************************************** TEI.back --><entDoc id="TEIBACK" type="pe"><entName>TEI.back.dtd</entName><desc>defines the file in which tags for back matter are defined.</desc><remarks><p>This parameter entity is used in each base tag set to
include the back-matter tags, which are common to all bases.<!-- files names='TEI2'> --></p></remarks><string>system 'teiback2.dtd'</string><xref target="DSBACK"/></entDoc><?tei:EOF teiback.ent ??><!-- TEI.back.dtd entity --><?tei:SOF cedtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cedtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.certainty.dtd --><!-- Revisions:                                               --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><entDoc id="CEDTD" type="pe"><entName>TEI.certainty.dtd</entName><name>TEI certainty-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for certainty and uncertainty.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for certainty and uncertainty.</p></remarks><string>system 'teicert2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF cedtd.ent ??><!-- TEI.certainty.dtd entity --><?tei:SOF cetop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cetop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.certainty --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="CETOP" type="pe"><entName>TEI.certainty</entName><name>TEI certainty DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for certainty.</desc><remarks><p>To include elements and attributes for certainty in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF cetop.ent ??><!-- TEI.certainty.top entity --><?tei:SOF teicore.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teicore.ent,v $
# Revision 1.2  93/09/08  18:06:49  msmcq
# lowercase filename
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-03-30 : MSM : add suffix '.dtd', correct repl text    --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************************ TEIcore --><entDoc id="TEICORE" type="pe"><entName>TEI.core.dtd</entName><name>TEI core</name><desc>identifies the file containing element and attribute list
declarations for the TEI core elements.</desc><remarks><p>This entity is included in all TEI DTDs.</p></remarks><string>system 'teicore2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF teicore.ent ??><!-- TEI.core.dtd entity --><?tei:SOF ccdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ccdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.corpus.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="CCDTD" type="pe"><entName>TEI.corpus.dtd</entName><name>TEI corpus-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for corpora.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for corpora.</p></remarks><string>system 'teicorp2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF ccdtd.ent ??><!-- TEI.corpus.dtd entity --><?tei:SOF cctop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cctop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.corpus --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="CCTOP" type="pe"><entName>TEI.corpus</entName><name>TEI corpora DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for the description of corpora.</desc><remarks><p>To include elements and attributes for corpora in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF cctop.ent ??><!-- TEI.corpus.top entity --><?tei:SOF didtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	didtd.ent,v $
# Revision 1.2  93/09/16  14:54:10  msmcq
# Changes at publication of TD:  dictionar-ies
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : dictionar-ies not -y                    --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><!-- *********************************** TEI.dictionaries.dtd --><entDoc id="DIDTD" type="pe"><entName>TEI.dictionaries.dtd</entName><name>TEI dictionary-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for dictionaries.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for dictionaries.</p></remarks><string>system 'teidict2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF didtd.ent ??><!-- TEI.dictionaries.dtd entity --><?tei:SOF dient.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dient.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************* TEI.dictionary.ent --><entDoc id="DIENT" type="pe"><entName>TEI.dictionaries.ent</entName><name>TEI dictionary-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the base tag set for dictionaries.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for dictionaries.</p></remarks><string>system 'teidict2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF dient.ent ??><!-- TEI.dictionaries.ent entity --><?tei:SOF ditop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ditop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-03 : MSM : new ID                                  --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><!-- ***************************************** TEI.dictionary --><entDoc id="DITOP" type="pe"><entName>TEI.dictionaries</entName><name>TEI dictionaries DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for dictionaries.</desc><remarks><p>To include elements and attributes for dictionaries in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF ditop.ent ??><!-- TEI.dictionaries.top entity --><?tei:SOF drdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.drama.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="DRDTD" type="pe"><entName>TEI.drama.dtd</entName><name>TEI drama-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for drama.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for drama.</p></remarks><string>system 'teidram2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF drdtd.ent ??><!-- TEI.drama.dtd entity --><?tei:SOF drent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drent.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.drama.ent --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="DRENT" type="pe"><entName>TEI.drama.ent</entName><name>TEI drama-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the base tag set for drama.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for drama.</p></remarks><string>system 'teidram2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF drent.ent ??><!-- TEI.drama.ent entity --><?tei:SOF drtop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drtop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** TEI.drama --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="DRTOP" type="pe"><entName>TEI.drama</entName><name>TEI drama DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for drama.</desc><remarks><p>To include elements and attributes for drama in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF drtop.ent ??><!-- TEI.drama.top entity --><?tei:SOF teiecga.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teiecga.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.elementClasses --><entDoc id="TEIECGA" type="pe"><entName>TEI.elementClasses</entName><desc>file containing the parameter entity declarations which define
element classes for content models, attributes shared among elements of
a class, and global attributes.</desc><remarks><p></p></remarks><string>system 'teiclas2.ent'</string><xref target="STOV"/><xref target="STEC"/></entDoc><?tei:EOF teiecga.ent ??><!-- TEI.elementClasses entity --><?tei:SOF teigis.ent ??><!-- Revisions:                                               --><!-- 93-09-11 : MSM : change system identifier                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teigis.ent,v $
# Revision 1.2  93/09/16  14:59:45  msmcq
# change system identifier, to reduce confusion
# between this entdoc and the .ent file we are producing.
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************** TEI.elementNames --><entDoc id="TEIGIS" type="pe"><entName>TEI.elementNames</entName><desc>file containing parameter entity declarations for all generic
identifiers of the encoding scheme.
 </desc><remarks><p>The parameter entities in this file all take the same form
as the two shown below:
 
<eg><![CDATA[ <!ENTITY % n.div0 'div0' >
 <!ENTITY % n.div1 'div1' >]]></eg>
 
Element and attribute-list declarations in the DTDs refer to the
parameter entity <term>n.div1</term>, not directly to the generic
identifier <term>div1</term>.  As a result, the declarations will
function as desired even if a new generic identifier is substituted
(e.g. <q>caput</q> for <q>div1</q> and <q>liber</q> for <q>div0</q>:
 
<eg><![CDATA[ <!ENTITY % n.div0 'liber' >
 <!ENTITY % n.div1 'caput' >]]></eg>
 </p><p>This allows generic identifiers to be renamed conveniently, to
provide names in languages other than English, or to provide shorter
names than those documented here.
See further chapter <xref target="MD"/>.
 </p></remarks><string>system 'teigis2.ent'</string><xref target="STPEGI"/></entDoc><?tei:EOF teigis.ent ??><!-- TEI.elementNames entity --><?tei:SOF teiextd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teiextd.ent,v $
# Revision 1.1  93/12/20  15:18:56  lou
# Initial revision
#  --><entDoc id="TEIEXTD" type="pe"><entName>TEI.extensions.dtd</entName><desc>file (if any) containing local modifications to the TEI DTDs.</desc><remarks><p>This entity is embedded in the TEI DTDs after the TEI
element classes are embedded, and immediately before the base tag set
and additional tag sets selected by the user are embedded.  By default,
the entity expands to the empty string; the user can override this
default by declaring the entity with an appropriate value, typically
this will take the form
 
<eg><![CDATA[ <!ENTITY % TEI.extensions.dtd system 'project.dtd' >]]></eg>
 </p></remarks><string>''</string><xref target="STOV"/></entDoc><?tei:EOF teiextd.ent ??><!-- TEI.extensions.dtd entity --><?tei:SOF teiexte.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teiexte.ent,v $
# Revision 1.2  94/03/22  17:11:19  msmcq
# lowercase id (desperate attempt to fix stupide oddp2x error)
# 
# Revision 1.1  1993/12/20  15:18:39  lou
# Initial revision
# --><entDoc id="TEIEXTE" type="pe"><entName>TEI.extensions.ent</entName><desc>file (if any) containing local modifications to the TEI element classes.</desc><remarks><p>This entity is embedded in the TEI DTDs before the TEI
element classes are embedded.  By default,
the entity expands to the empty string; the user can override this
default by declaring the entity with an appropriate value, typically
this will take the form
 
<eg><![CDATA[ <!ENTITY % TEI.extensions.ent system 'project.ent' >]]></eg>
 </p></remarks><string>''</string><xref target="STOV"/></entDoc><?tei:EOF teiexte.ent ??><!-- TEI.extensions.ent entity --><?tei:SOF ftdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ftdtd.ent,v $
# Revision 1.3  94/07/28  20:12:40  msmcq
# last-minute change / fix preparing TEI P3
# 
# Revision 1.2  1994/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ************************************* TEI.formulas.dtd --><!-- Revisions:                                               --><!-- 94-04-08 : MSM : change file name                        --><!-- 94-04-06 : MSM : change full name (figures, was formulas) --><!-- 93-03-27 : MSM : made file                               --><entDoc id="FTDTD" type="pe"><entName>TEI.figures.dtd</entName><name>TEI figures-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for tables, formulas, and graphics.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for formulas and tables.</p></remarks><string>system 'teifig2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF ftdtd.ent ??><!-- TEI.figures.dtd entity --><?tei:SOF gfdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gfdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.figures.dtd --><!-- Revisions:                                               --><!-- 3 apr 93 : LB changed name                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="GFDTD" type="pe"><entName>TEI.figures.dtd</entName><name>TEI graphics-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for graphics and figures.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for graphics and figures.</p></remarks><string>system 'teifig2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF gfdtd.ent ??><!-- TEI.figures.dtd entity --><?tei:SOF ftent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ftent.ent,v $
# Revision 1.1  94/03/01  04:10:39  msmcq
# Initial revision
#  --><!-- ************************************* TEI.figures.ent --><!-- Revisions:                                               --><!-- 94-02-25 : MSM : made from old CEent                     --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><entDoc id="FTENT" type="pe"><entName>TEI.figures.ent</entName><name>TEI figures-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the additional tag set for figures.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for figures, tables, and formulae.</p></remarks><string>system 'teifig2.ent'</string><xref target="STEC"/></entDoc><?tei:EOF ftent.ent ??><!-- TEI.figures.ent entity --><?tei:SOF fttop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fttop.ent,v $
# Revision 1.2  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ***************************************** TEI.figures --><!-- Revisions:                                               --><!-- 94-04-06 : MSM : change full name (figures, was formulas) --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="FTTOP" type="pe"><entName>TEI.figures</entName><name>TEI figures and tables DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for figures and tables.</desc><remarks><p>To include elements and attributes for figures and tables
in the DTD, the user should declare this entity with a value of
<q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF fttop.ent ??><!-- TEI.figures.top entity --><?tei:SOF gftop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gftop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.figures --><!-- Revisions:                                               --><!-- 3 apr 93 : LB changed name                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="GFTOP" type="pe"><entName>TEI.figures</entName><name>TEI graphics and figures DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for graphics and figures.</desc><remarks><p>To include elements and attributes for graphics and
figures in the DTD, the user should declare this entity with a value
of <q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF gftop.ent ??><!-- TEI.figures.top entity --><?tei:SOF teifront.ent ??><!-- ********************************************** TEI.front --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : change xref:  pr3 to dsfront            --><!-- 93-08-18 : MSM : lowercase id                            --><!-- 93-03-30 : MSM : add suffix '.dtd'                       --><!-- 92-12-10 : MSM : suppress FILES element                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teifront.ent,v $
# Revision 1.3  93/10/05  11:13:28  lou
# lower case filename
# 
# Revision 1.2  1993/09/16  14:59:12  msmcq
# Update xref target at publ. of TD
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************************** TEI.front --><entDoc id="TEIFRONT" type="pe"><entName>TEI.front.dtd</entName><desc>defines the file in which tags for front matter are defined.</desc><remarks><p>This parameter entity is used in each base tag set to
include the front-matter tags, which are common to all bases.<!-- files names='TEI2'> --></p></remarks><string>system 'teifron2.dtd'</string><xref target="DSFRONT"/></entDoc><?tei:EOF teifront.ent ??><!-- TEI.front.dtd entity --><?tei:SOF fsdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fsdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.fs.dtd --><!-- Revisions:                                               --><!-- 93-03-02 : MSM : rename entity, new id                   --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><entDoc id="FSDTD" type="pe"><entName>TEI.fs.dtd</entName><name>TEI fs-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for feature structures.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for feature structures.</p></remarks><string>system 'teifs2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF fsdtd.ent ??><!-- TEI.fs.dtd entity --><!-- fsent  --><!-- TEI.fs.ent entity --><?tei:SOF fstop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fstop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.fs --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="FSTOP" type="pe"><entName>TEI.fs</entName><name>TEI feature structures DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for feature structures.</desc><remarks><p>To include elements and attributes for feature structures
in the DTD, the user should declare this entity with a value of
<q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF fstop.ent ??><!-- TEI.fs.top entity --><?tei:SOF cbgetop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbgetop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ******************************************** TEI.general --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="CBGETOP" type="pe"><entName>TEI.general</entName><name>TEI general base DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for the <soCalled>general</soCalled> combined base.</desc><remarks><p>To include elements and attributes for the
<soCalled>general</soCalled> base in the DTD, the user should
declare this entity with a value of <q>INCLUDE</q>; this will override
the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF cbgetop.ent ??><!-- TEI.general entity --><?tei:SOF cbgedtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbgedtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.general.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="CBGEDTD" type="pe"><entName>TEI.general.dtd</entName><name>TEI general-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for the <soCalled>general</soCalled>
base tag set.</desc><remarks><p>This entity is declared with this value when the user
includes the <soCalled>general</soCalled> mixed-base tag set.</p></remarks><string>system 'teigen2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF cbgedtd.ent ??><!-- TEI.general.dtd entity --><?tei:SOF teihdr.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teihdr.ent,v $
# Revision 1.2  93/09/16  14:59:45  msmcq
# change entity name for consistency with others.
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-13 : MSM : add .dtd to entity name                 --><!-- 93-03-30 : MSM : correct system id to .dtd               --><!-- 93-03-16 : MSM : lowercase filename                      --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************************* TEIhdr --><entDoc id="TEIHDR" type="pe"><entName>TEI.header.dtd</entName><name>TEI header</name><desc>identifies the file containing element and attribute list
declarations for the TEI header.</desc><remarks><p>This entity is included in all TEI DTDs.</p></remarks><string>system 'teihdr2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF teihdr.ent ??><!-- TEI.header.dtd entity --><?tei:SOF teikw.ent ??><!-- *************************************** TEI.keywords.ent --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teikw.ent,v $
# Revision 1.1  93/09/15  23:00:57  msmcq
# Changes as of mid-September
#  --><!-- Revisions:                                               --><!-- 93-09-14 : MSM : made file                               --><!-- *************************************** TEI.keywords.ent --><entDoc id="TEIKW" type="pe"><entName>TEI.keywords.ent</entName><desc>file containing the parameter entity declarations for TEI
keywords.</desc><remarks><p>The keywords defined in this file define non-SGML data
types (e.g. ISO dates) and control the selection of base and additional
tag sets.</p></remarks><string>system 'teikey2.ent'</string><xref target="STPEKW"/></entDoc><?tei:EOF teikw.ent ??><!-- TEI.keywords.ent entity --><?tei:SOF sadtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	sadtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-03 : MSM : new id, name                            --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************************* TEIsae --><entDoc id="SADTD" type="pe"><entName>TEI.linking.dtd</entName><name>TEI segmentation and alignment elements</name><desc>identifies the file containing element and attribute list
declarations for the additional tag set for segmentation and alignment.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for segmentation and alignment.</p></remarks><string>system 'teilink2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF sadtd.ent ??><!-- TEI.linking.dtd entity --><?tei:SOF saent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	saent.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-03 : MSM : new name, id                            --><!-- 93-02-02 : MSM : made file                               --><!-- **************************************** TEI.linking.ent --><entDoc id="SAENT" type="pe"><entName>TEI.linking.ent</entName><name>TEI linking-tag-set entities</name><desc>identifies the file containing parameter entity declarations for
the element classes defined in the additional tag set for segmentation
and alignment.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for segmentation and alignment.</p></remarks><string>system 'teilink2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF saent.ent ??><!-- TEI.linking.ent entity --><?tei:SOF satop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	satop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-03 : MSM : new entity name, new id                 --><!-- 93-02-02 : MSM : made file                               --><!-- ******************************************** TEI.linking --><entDoc id="SATOP" type="pe"><entName>TEI.linking</entName><name>TEI DTD fragment for linking tag set</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for linking, segmentation and alignment.</desc><remarks><p>To include elements and attributes for segmentation and
alignment in the DTD, the user should declare this entity with a value
of <q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF satop.ent ??><!-- TEI.linking.top entity --><?tei:SOF cbmxtop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbmxtop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.mixed --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="CBMXTOP" type="pe"><entName>TEI.mixed</entName><name>TEI `mixed' base DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for the <soCalled>mixed</soCalled> combined base.</desc><remarks><p>To include elements and attributes for the
<soCalled>mixed</soCalled> base in the
DTD, the user should declare this entity with a value of
<q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF cbmxtop.ent ??><!-- TEI.mixed entity --><?tei:SOF cbmxdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cbmxdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.mixed.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="CBMXDTD" type="pe"><entName>TEI.mixed.dtd</entName><name>TEI mixed-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for
the <soCalled>mixed</soCalled> base tag set.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for the <soCalled>mixed</soCalled> base.</p></remarks><string>system 'teimix2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF cbmxdtd.ent ??><!-- TEI.mixed.dtd entity --><?tei:SOF nddtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	nddtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.names.dates.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="NDDTD" type="pe"><entName>TEI.names.dates.dtd</entName><name>TEI names.dates-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for detailed analysis of names and
dates.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for names and dates.</p></remarks><string>system 'teind2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF nddtd.ent ??><!-- TEI.names.dates.dtd entity --><?tei:SOF ndent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ndent.ent,v $
# Revision 1.1  94/04/01  17:26:40  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file                               --><!-- ************************************ TEI.names.dates.ent --><entDoc id="NDENT" type="pe"><entName>TEI.names.dates.ent</entName><name>parameter entities for names and dates</name><desc>identifies the file containing parameter entity declarations for
the element classes defined in the additional tag set for names and
dates.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for names and dates.</p></remarks><string>system 'teind2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF ndent.ent ??><!-- TEI.names.dates.ent entity --><?tei:SOF ndtop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ndtop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.names.dates --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="NDTOP" type="pe"><entName>TEI.names.dates</entName><name>TEI names and dates DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for detailed analysis of names and dates.</desc><remarks><p>To include elements and attributes for names and dates in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF ndtop.ent ??><!-- TEI.names.dates.top entity --><?tei:SOF gddtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gddtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.nets.dtd --><!-- Revisions:                                               --><!-- 3 apr 93 : LB changed name                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="GDDTD" type="pe"><entName>TEI.nets.dtd</entName><name>TEI networks-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for graph theory (graphs,
digraphs and other networks).</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for graph theory.</p></remarks><string>system 'teinet2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF gddtd.ent ??><!-- TEI.nets.dtd entity --><?tei:SOF gdtop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gdtop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************** TEI.nets --><!-- Revisions:                                               --><!-- 3 apr 93 : LB changed name                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="GDTOP" type="pe"><entName>TEI.nets</entName><name>TEI graph theoretic DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for graph theory (graphs, digraphs and other networks)</desc><remarks><p>To include elements and attributes for graphs and digraphs
in the DTD, the user should declare this entity with a value of
<q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF gdtop.ent ??><!-- TEI.nets.top entity --><?tei:SOF prdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	prdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-02-05 : MSM : rename entity                           --><!-- 93-02-02 : MSM : made file                               --><!-- ****************************************** TEI.prose.dtd --><entDoc id="PRDTD" type="pe"><entName>TEI.prose.dtd</entName><name>TEI prose-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for prose.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for prose.</p></remarks><string>system 'teipros2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF prdtd.ent ??><!-- TEI.prose.dtd entity --><?tei:SOF prtop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	prtop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-03 : MSM : change ID                               --><!-- 93-02-02 : MSM : made file                               --><!-- *********************************************** TEIprose --><entDoc id="PRTOP" type="pe"><entName>TEI.prose</entName><name>TEI prose DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for prose.</desc><remarks><p>To include elements and attributes for prose in the DTD,
the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STBA"/><xref target="STOV"/></entDoc><?tei:EOF prtop.ent ??><!-- TEI.prose.top entity --><?tei:SOF mixyes.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	mixyes.ent,v $
# Revision 1.1  94/04/01  17:24:37  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file mixyes, mixno                 --><!-- ***************************************** TEI.singleBase --><entDoc id="MIXYES" type="pe"><entName>TEI.singleBase</entName><name>single-base flag</name><desc>controls the inclusion, in the DTD, of the default text structure
elements.  Its value is <code tei="yes" type="frag">IGNORE</code> when the mixed base or
general base is selected.</desc><remarks><p>The user should not redefine this parameter entity.</p></remarks><string>'IGNORE'</string><xref target="STPE"/></entDoc><?tei:EOF mixyes.ent ??><!-- TEI.singleBase (IGNORE)  --><?tei:SOF mixno.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	mixno.ent,v $
# Revision 1.1  94/04/01  17:24:37  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : made file mixyes, mixno                 --><!-- ***************************************** TEI.singleBase --><entDoc id="MIXNO" type="pe"><entName>TEI.singleBase</entName><name>single-base flag</name><desc>controls the inclusion, in the DTD, of the default text structure
elements.  Its value is <code tei="yes" type="frag">INCLUDE</code> when only a single base
tag set is selected.</desc><remarks><p>The user should not redefine this parameter entity.</p></remarks><string>'INCLUDE'</string><xref target="STPE"/></entDoc><?tei:EOF mixno.ent ??><!-- TEI.singleBase (INCLUDE) --><?tei:SOF tsdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.spoken.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="TSDTD" type="pe"><entName>TEI.spoken.dtd</entName><name>TEI spoken-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for spoken texts.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for spoken texts.</p></remarks><string>system 'teispok2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF tsdtd.ent ??><!-- TEI.spoken.dtd entity --><?tei:SOF tsent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsent.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.spoken.ent --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="TSENT" type="pe"><entName>TEI.spoken.ent</entName><name>TEI spoken-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the base tag set for spoken texts.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for spoken texts.</p></remarks><string>system 'teispok2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF tsent.ent ??><!-- TEI.spoken.ent entity --><?tei:SOF tstop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tstop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************* TEI.spoken --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="TSTOP" type="pe"><entName>TEI.spoken</entName><name>TEI spoken texts DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for spoken texts.</desc><remarks><p>To include elements and attributes for spoken texts in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF tstop.ent ??><!-- TEI.spoken.top entity --><?tei:SOF teistr.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teistr.ent,v $
# Revision 1.2  94/04/01  17:27:23  msmcq
# Changes while validating DTD
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : uppercase TEI in name                   --><!-- 93-03-30 : MSM : made file                               --><!-- ************************************** TEI.structure.dtd --><entDoc id="TEISTR" type="pe"><entName>TEI.structure.dtd</entName><desc>defines the file in which the default text structure
used by many base tag sets is defined.</desc><remarks><p></p></remarks><string>system 'teistr2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF teistr.ent ??><!-- TEI.structure.dtd entity --><?tei:SOF tetop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tetop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- **************************************** TEI.terminology --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="TETOP" type="pe"><entName>TEI.terminology</entName><name>TEI terminological data DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for terminological data.</desc><remarks><p>To include elements and attributes for terminological data
in the DTD, the user should declare this entity with a value of
<q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF tetop.ent ??><!-- TEI.terminology entity --><?tei:SOF tedtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tedtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.terminology.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="TEDTD" type="pe"><entName>TEI.terminology.dtd</entName><name>TEI terminology-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for terminological data.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for terminological data.</p></remarks><string>system 'teiterm2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF tedtd.ent ??><!-- TEI.terminology.dtd entity --><?tei:SOF teent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teent.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.terminology.ent --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="TEENT" type="pe"><entName>TEI.terminology.ent</entName><name>TEI terminology-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the base tag set for terminological data.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for terminological data.</p></remarks><string>system 'teiterm2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF teent.ent ??><!-- TEI.terminology.ent entity --><?tei:SOF tcdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tcdtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-03 : MSM : new name, id                            --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************************* TEI.textcrit.dtd --><entDoc id="TCDTD" type="pe"><entName>TEI.textcrit.dtd</entName><name>TEI text criticism base DTD</name><desc>identifies the file containing element and attribute list
declarations for the additional tag set for text criticism.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for text criticism.</p></remarks><string>system 'teitc2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF tcdtd.ent ??><!-- TEI.textcrit.dtd entity --><?tei:SOF tcent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tcent.ent,v $
# Revision 1.2  94/04/01  17:27:23  msmcq
# Changes while validating DTD
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : lowercase filename                      --><!-- 93-03-02 : MSM : change from teitcc to tcent             --><!-- 93-02-02 : MSM : made file                               --><!-- *************************************** TEI.textcrit.ent --><entDoc id="TCENT" type="pe"><entName>TEI.textcrit.ent</entName><name>TEI text criticism entities</name><desc>identifies the file containing parameter entity declarations for
the element classes defined in the additional tag set for text
criticism.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for text criticism.</p></remarks><string>system 'teitc2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF tcent.ent ??><!-- TEI.textcrit.ent entity --><?tei:SOF tctop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tctop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-02-02 : MSM : made file                               --><!-- ******************************************* TEI.textcrit --><entDoc id="TCTOP" type="pe"><entName>TEI.textcrit</entName><name>TEI text criticism DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for text criticism.</desc><remarks><p>To include elements and attributes for text
criticism in the DTD, the user should declare this entity with a value
of <q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STOV"/></entDoc><?tei:EOF tctop.ent ??><!-- TEI.textcrit.top entity --><?tei:SOF phdtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	phdtd.ent,v $
# Revision 1.2  94/04/28  16:44:03  msmcq
# rename phys as transcr
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ************************************* TEI.transcr.dtd --><!-- Revisions:                                               --><!-- 94-03-07 : MSM : rename from physical to transcr         --><!-- 93-03-27 : MSM : made file                               --><entDoc id="PHDTD" type="pe"><entName>TEI.transcr.dtd</entName><name>TEI DTD for transcription of primary sources</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for description of the source
text.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for transcription of primary sources</p></remarks><string>system 'teitran2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF phdtd.ent ??><!-- TEI.transcr.dtd entity --><?tei:SOF phent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	phent.ent,v $
# Revision 1.2  94/03/16  03:46:18  msmcq
# teitran2.ent, not teiphys2.ent
#  --><!-- ************************************* TEI.transcr.ent --><!-- Revisions:                                               --><!-- 94-03-14 : MSM : teitran, not teiphys                    --><!-- 94-03-07 : MSM : made file                               --><!-- 94-03-07 : MSM : made from old ftend                     --><entDoc id="PHENT" type="pe"><entName>TEI.transcr.ent</entName><name>TEI entities for transcription of primary sources</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the additional tag set for
transcription of primary sources.</desc><remarks><p>This entity is declared with this value when the user
includes the additional tag set for transcription of primary sources.</p></remarks><string>system 'teitran2.ent'</string><xref target="STEC"/></entDoc><?tei:EOF phent.ent ??><!-- TEI.transcr.ent entity --><?tei:SOF phtop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	phtop.ent,v $
# Revision 1.2  94/04/28  16:44:03  msmcq
# rename phys as transcr
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ***************************************** TEI.physical --><!-- Revisions:                                               --><!-- 94-03-07 : MSM : rename from physical to transcr         --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="PHTOP" type="pe"><entName>TEI.transcr</entName><name>TEI DTD fragment for transcription of primary sources</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for transcription of the source text.</desc><remarks><p>To include elements and attributes for transcription
in the DTD, the user should declare this entity with a
value of <q>INCLUDE</q>; this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STGA"/><xref target="STOV"/></entDoc><?tei:EOF phtop.ent ??><!-- TEI.transcr.top entity --><?tei:SOF vetop.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vetop.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ********************************************** TEI.verse --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file from DI sample entdoc         --><entDoc id="VETOP" type="pe"><entName>TEI.verse</entName><name>TEI verse DTD fragment</name><desc>controls the inclusion, in the DTD, of element and attribute
declarations for verse.</desc><remarks><p>To include elements and attributes for verse in the
DTD, the user should declare this entity with a value of <q>INCLUDE</q>;
this will override the default.</p></remarks><string>'IGNORE'</string><xref target="STBA"/><xref target="STOV"/></entDoc><?tei:EOF vetop.ent ??><!-- TEI.verse entity --><?tei:SOF vedtd.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vedtd.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.verse.dtd --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="VEDTD" type="pe"><entName>TEI.verse.dtd</entName><name>TEI verse-base DTD</name><desc>identifies the file containing element and attribute list
declarations for the base tag set for verse.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for verse.</p></remarks><string>system 'teivers2.dtd'</string><xref target="STBA"/></entDoc><?tei:EOF vedtd.ent ??><!-- TEI.verse.dtd entity --><?tei:SOF veent.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	veent.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************* TEI.verse.ent --><!-- Revisions:                                               --><!-- 93-03-27 : MSM : made file                               --><entDoc id="VEENT" type="pe"><entName>TEI.verse.ent</entName><name>TEI verse-base entities</name><desc>identifies the file containing parameter entity declarations
for the element classes defined in the base tag set for verse.</desc><remarks><p>This entity is declared with this value when the user
includes the base tag set for verse.</p></remarks><string>system 'teivers2.ent'</string><xref target="STBA"/></entDoc><?tei:EOF veent.ent ??><!-- TEI.verse.ent entity --><?tei:SOF wdgis.ent ??><!-- Revisions:                                               --><!-- 93-09-20 : MSM : make file from tigis.ent                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wdgis.ent,v $
# Revision 1.1  93/09/22  19:02:18  msmcq
# Initial revision
#  --><!-- *************************************** TEI.wsdNames --><entDoc id="WDGIS" type="pe"><entName>TEI.wsdNames</entName><desc>file containing parameter entity declarations for all generic
identifiers used in the writing system declaration
 </desc><remarks><p>The parameter entities in this file all take the same form
as the two shown below:
 
<eg><![CDATA[ <!ENTITY % n.div0 'div0' >
 <!ENTITY % n.div1 'div1' >]]></eg>
 
Element and attribute-list declarations in the DTDs refer to the
parameter entity <term>n.div1</term>, not directly to the generic
identifier <term>div1</term>.  As a result, the declarations will
function as desired even if a new generic identifier is substituted
(e.g. <q>caput</q> for <q>div1</q> and <q>liber</q> for <q>div0</q>:
 
<eg><![CDATA[ <!ENTITY % n.div0 'liber' >
 <!ENTITY % n.div1 'caput' >]]></eg>
 </p><p>This allows generic identifiers to be renamed conveniently, to
provide names in languages other than English, or to provide shorter
names than those documented here.
See further chapter <xref target="MD"/>.
 </p></remarks><string>system 'wdgis2.ent'</string><xref target="WDOV"/></entDoc><?tei:EOF wdgis.ent ??><!-- TEI.wsdNames entity --><?tei:SOF termtn.ent ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	termtn.ent,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- *********************************************** termtags --><entDoc id="TERMTN" type="pe"><entName>termtags</entName><desc>system entity with definitions for basic terminology tags.</desc><remarks><p>The default definition of this entity is used to invoke the
element declarations for the <soCalled>nested</soCalled> style of
terminological markup.  To invoke the alternative
<soCalled>flat</soCalled> style declarations, this entity should be
defined as <q>system 'teite2f.dtd'</q>.</p></remarks><string>system 'teite2n.dtd'</string><xref target="TEDT"/></entDoc><?tei:EOF termtn.ent ??><!-- termtags entity --><?tei:SOF version.ent ??><!-- Revisions:                                               --><!-- 93-09-13 : MSM : xref was cors3, now NHrs                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	version.ent,v $
# Revision 1.2  93/09/16  14:59:12  msmcq
# Update xref target at publ. of TD
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ************************************************ version --><entDoc id="VERSION" type="pe"><entName>version</entName><name>version</name><desc>defines the name to be used for the root element of a concurrent
markup stream for marking pages and lines of some reference edition.</desc><remarks><p>Some name for the edition should be supplied by defining
this parameter entity within the appropriate DTD subset.  If none is
defined, the parameter entity (and thus the document type) default to
<q>ref</q>.</p></remarks><string>'ref'</string><xref target="NHRS" type="div3"/></entDoc><?tei:EOF version.ent ??><!-- version entity --></div1><div1 id="REFTAG" n="35" name="Faisal" ref="Y"><head>Elements</head><!-- tags --><!-- *egword --><!-- egword element --><!-- clloc --><!-- loc class--><!-- &city --><!-- city element --><!-- &ornament --><!-- ornament element --><!-- &skel --><!-- skel element --><?tei:SOF anonb.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- Revisions:                                               --><!-- 7 Jan 98 : LB : Made new tagdoc --><!-- ab already taken by p2ab --><tagDoc id="ANONB" usage="opt"><gi tei="yes">ab</gi><name>anonymous block</name><desc>contains any arbitrary component-level unit of text, acting as
an anonymous container for phrase or inter level elements analogous to, but
without the semantic baggage of, a paragraph.</desc><attList><attDef usage="mwa"><attName>part</attName><desc>specifies whether or not the block is complete. </desc><datatype>(Y | N | I | M | F)</datatype><valList type="closed"><val>Y</val><desc>the block is incomplete</desc><val>N</val><desc>either the block is complete, or no claim is made as to its
completeness</desc><val>I</val><desc>the initial part of an incomplete block</desc><val>M</val><desc>a medial part of an incomplete block</desc><val>F</val><desc>the final part of an incomplete block</desc></valList><default>N</default><remarks><p>The values I, M, or F should be used only where it is
clear how the block is to be reconstituted.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>The <gi tei="yes">ab</gi> element may be used at the encoder's
discretion to mark any component-level elements in a text for which
no other more specific appropriate markup is defined.</p></remarks><part type="top" name="core"/><classes names="CHUNK TYPED"/><dataDesc>May contain anything which may appear within a paragraph.</dataDesc><elemDecl>- -  (%paraContent)</elemDecl><xref target="SASE"/></tagDoc><?tei:EOF anonb.tag ??><!-- ab element --><?tei:SOF abbr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	abbr.tag,v $
# Revision 1.4  94/03/28  19:59:41  msmcq
# punctuations, tyops (i don't know)
# 
# Revision 1.3  1994/01/04  13:13:16  lou
# not #inherited but %inherited dumpkopf
#
# Revision 1.2  1993/11/30  14:27:34  lou
# fixed typo in example
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-05 : MSM : clean up bad comment                    --><!-- 93-05-24 : PR : changes to conform to TC matter          --><!-- 92-12-09 : MSM : suppress membership in edit class       --><!-- 92-11-09 : MSM : supply missing endtag for gi            --><!-- 92-11-05 : MSM : correct spqr, cosmetic chgs to attdefs  --><!-- ******************************************************** abbr --><tagDoc id="ABBR" usage="opt"><gi tei="yes">abbr</gi><name>abbreviation</name><desc>contains an abbreviation of any sort.</desc><attList><!-- .................................................... expan --><attDef usage="opt"><attName>expan</attName><name>expansion</name><desc>gives an expansion of the abbreviation.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ The address is Southmoor <abbr expan='road'>Rd</>.]]></eg><remarks><p>Only one expansion may be given for an abbreviation; if
different expansions are to be proposed, the tags for critical
apparatus
should be used.</p></remarks></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>signifies the editor or transcriber responsible for supplying
the expansion of the abbreviation held as the value of the
<att tei="yes">expan</att> attribute.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ The address is Southmoor <abbr expan='Road' resp=LB>Rd</>.]]></eg><remarks><p>If no expansion is given, the <att tei="yes">resp</att> attribute
has no meaning.</p></remarks></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the expansion of
the abbreviation.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>allows the encoder to classify the abbreviation according to
some
convenient typology.</desc><datatype>CDATA</datatype><valList type="open"><val>suspension     </val><desc>the abbreviation provides the first
       letter(s) of the word or phrase, omitting the remainder.</desc><val>contraction    </val><desc>the abbreviation omits some letter(s) in the middle.</desc><val>brevigraph     </val><desc>the abbreviation comprises a special symbol or mark.</desc><val>superscription </val><desc>the abbreviation includes writing above
the line.</desc><val>acronym        </val><desc>the abbreviation comprises the initial
letters of the words of a phrase.</desc><val>title          </val><desc>the abbreviation is for a title of
address (Dr, Ms, Mr, ...)</desc><val>organization   </val><desc>the abbreviation is for the name of an
organization.</desc><val>geographic     </val><desc>the abbreviation is for a geographic  name.</desc></valList><default>#IMPLIED</default><eg><![CDATA[  <abbr type=acronym>RSVP</abbr>
  <abbr type=organization>SPQR</abbr>
  <abbr type=brevigraph>&per;</abbr>
  <abbr type=contraction>yr hbl servt</abbr>]]></eg><!-- This example removed because I never heard of it         --><!-- ! there are more things in this world, dear Horatio ...  --><!--  < abbr expan='Si vales bene est et valeo'             --><!-- type='acronym' > SVBEEV < / >                            --><remarks><p>The <att tei="yes">type</att> attribute is provided for the sake of
those who wish to classify abbreviations at their point of  occurrence;
this may be useful in some circumstances, though usually the same
abbreviation will have the same type in all occurrences.  As the
sample values make clear, abbreviations may be classified by the method
used  to construct them, the method of writing them, or the referent of
the  term abbreviated; the typology used is up to the encoder and
should be carefully planned to meet the needs of the expected use.</p></remarks></attDef></attList><!-- < exemplum>< eg>< ![ CDATA [                             --><!--   < abbr type=organization                             --><!--     expan='societas populique romanorum'                 --><!--     resp=author>SPQR< /abbr>                           --><!-- ]]>                                                      --><!-- Don't you mean:                                          --><exemplum><eg><![CDATA[  <abbr type=organization
    expan='senatus populusque romanorum'
    resp=author>SPQR</abbr>]]></eg></exemplum><remarks><p>This tag is the mirror image of the <gi tei="yes">expan</gi> tag;
both allow the encoder to transcribe both an abbreviation and its
expansion. In <gi tei="yes">abbr</gi>, however, the original is transcribed as
the content  of the element and the expansion as an attribute value;
<gi tei="yes">expan</gi> reverses this.  The choice between the two is up to the
user.</p><p>The <gi tei="yes">abbr</gi> tag is not required; if appropriate, the encoder
may transcribe abbreviations in the source text silently, without
tagging them.  If abbreviations are not transcribed directly but
<emph>expanded</emph> silently, then the TEI header should so
indicate.</p><p>For a typology of ME abbreviations, see <citation>A. G. Petty,
<title>English literary hands from Chaucer to
Dryden</title> (London:  Edward Arnold, 1977), pp. 22-25.</citation></p></remarks><part type="top" name="core"/><classes names="DATA"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONAAB" type="div2"/></tagDoc><?tei:EOF abbr.tag ??><!-- abbr element --><?tei:SOF activity.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	activity.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* activity --><tagDoc id="ACTIVITY" usage="opt"><gi tei="yes">activity</gi><name>activity</name><desc>contains a brief informal description of what a participant in a
language interaction is doing other than speaking, if anything.</desc><attList></attList><exemplum><eg><![CDATA[    <activity>driving</activity>]]></eg></exemplum><remarks><p>For more fine-grained description of participant
activities during a spoken text, the <gi tei="yes">event</gi> element should
be used.</p></remarks><part type="aux" name="corpora"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHSE"/></tagDoc><?tei:EOF activity.tag ??><!-- activity element --><?tei:SOF actor.tag ??><!-- Actor.tag                                                --><!-- Revisions:                                               --><!-- 93-08-16 : MSM : suppress membership in perfph           --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: actor.tag,v $
    * Revision 1.7  1998/02/09 18:02:36  tei
    * fix egs
    *
    * Revision 1.6  94/02/12  10:44:46  lou
    * JLs comments of 4 feb
    * 
    * Revision 1.5  1993/08/23  16:19:36  msmcq
    * full stop at end of DESC
    * 
    * Revision 1.4  1993/08/16  21:53:15  msmcq
    * Tweaks for publication of DR
    * 
    * Revision 1.3  1993/08/13  20:48:47  msmcq
    * strip control-Z
    * 
    * Revision 1.2  1993/08/12  21:33:20  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ****************************** actor --><!-- 18 jan: changed IDs --><tagDoc id="ACTOR" usage="opt"><gi tei="yes">actor</gi><name>actor</name><desc>Name of an actor appearing within a cast list.</desc><attList><!-- LB killed following attrib: (but forgot to remove it from the eg! --><!-- ) --><!-- < attdef usage=opt>  --><!--  < attname>who --><!--  < desc>provides the unique identifier for the person concerned --><!--  < datatype>IDREF --><!--  < valdesc>the value used should be supplied as value for an --><!--    < att>id</att>  attribute on one of a < gi>participant< /gi>, --><!--    < gi>participant.grp < /gi> or < gi>fs< /gi> element in the header --><!--  < /valdesc> --><!--  < default>#IMPLIED --><!-- < /attdef> --></attList><exemplum><eg><![CDATA[  <castItem>
   <role>Mathias</role><roleDesc>the Burgomaster</roleDesc>
   <actor>Mr. Henry Irving</actor>
  </castItem>]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes/><dataDesc>Contains phrase level elements and character data
only.</dataDesc><elemDecl>- O (%phrase.seq)</elemDecl><xref target="DRCAST" type="div3"/></tagDoc><?tei:EOF actor.tag ??><!-- actor element --><?tei:SOF add.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	add.tag,v $
# Revision 1.3  94/03/08  03:20:58  msmcq
# revision for P3
# 
# Revision 1.2  1993/08/03  01:34:55  msmcq
# DTD fixes
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct INHERITED                       --><!-- 92-12-09 : MSM : remove tabs                             --><!-- 92-12-09 : MSM : punctuation cleanup                     --><!-- 92-12-07 : MSM : change model to specialPara             --><!-- 92-11-09 : MSM : supply missing endtag for gi            --><!-- ********************************************************* add --><tagDoc id="ADD" usage="opt"><gi tei="yes">add</gi><name>addition</name><desc>contains letters, words, or phrases inserted in the text by an
author, scribe, annotator or corrector.</desc><attList><attDef usage="rec"><attName>place</attName><desc>if the the addition is written into the copy text, indicates
where
the additional text is written.</desc><datatype>CDATA</datatype><valList type="semi"><val>inline </val><desc>addition is made in a space left in the
                   witness by an earlier scribe
    </desc><val>supralinear </val><desc>addition is made above the line
    </desc><val>infralinear </val><desc>addition is made below the line
    </desc><val>left </val><desc>addition is made in left margin
    </desc><val>right </val><desc>addition is made in right margin
    </desc><val>top </val><desc>addition is made in top margin
    </desc><val>bottom </val><desc>addition is made in bottom margin
    </desc><val>opposite </val><desc>addition is made on opposite page
    </desc><val>verso </val><desc>addition is made on verso of sheet
    </desc><val>mixed </val><desc>addition is made somewhere, one or more of
                   other values</desc></valList><default>#IMPLIED</default><eg></eg></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for identifying
the hand of the addition.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the
identification of the hand of the addition.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>signifies the hand of the agent which made the addition.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>The <gi tei="yes">add</gi> tag should not be used for additions
made by editors or encoders.  In these cases, either the
<gi tei="yes">corr</gi> tag or the <gi tei="yes">supplied</gi> tag should be used.
 </p></remarks><part type="top" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%specialPara;)</elemDecl><xref target="COEDADD" type="div3"/></tagDoc><?tei:EOF add.tag ??><!-- add element --><?tei:SOF addname.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	addname.tag,v $
# Revision 1.4  94/03/15  11:10:20  lou
# minor typos etc
# 
# Revision 1.3  1994/03/07  16:17:00  lou
# revised for check in of ND
#
# Revision 1.2  1993/08/03  01:37:07  msmcq
# added valdesc
# --><!-- Revisions:                                               --><!-- 6 mar: remove type attrib; improve desc --><!-- 93-06-03 : MSM : add valdesc                             --><!--* *******************************************************addname --><tagDoc id="ADDNAME" usage="opt"><gi tei="yes">addName</gi><name>additional name</name><desc>contains an additional name component, such as a nickname, 
epithet, or alias, or any other descriptive phrase used within a
personal name.</desc><attList></attList><exemplum><eg><![CDATA[<persName>
  <foreName>Frederick</foreName>
  <addName type=epithet>the Great</persName>
  <roleName>Emperor of Prussia</roleName>
</persName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="PERSPART"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF addname.tag ??><!-- addName element --><?tei:SOF address.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: address.tag,v $
    * Revision 1.7  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.6  94/04/01  17:31:08  msmcq
    * misc fixes while checking DTD
    * 
    * Revision 1.4  1994/01/05  16:46:12  lou
    * fix stupid error in content model
    * 
    * Revision 1.3  1994/01/04  12:11:06  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/03  01:37:46  msmcq
    * content model revision
    * --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : move /elemdecl tag to protect weak oddref --><!-- 94-03-28 : MSM : suppress xref to LM                     --><!-- 2 jan 93 : LB : revised content model (quite a lot)  --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : allow name, rs                          --><!-- 93-06-02 : MSM : merge with LM address                   --><!-- 92-12-09 : MSM : add to data class                       --><!-- 92-12-06 : MSM : add org                                 --><!-- 92-12-06 : MSM : tighten content model (no broth)        --><!-- 92-11-09 : MSM : fix xref to CObi                        --><!-- 92-08-19 : MSM : fix xref to chapter HD/22               --><!-- *****************************************************address --><tagDoc id="ADDRESS" usage="opt"><gi tei="yes">address</gi><desc>contains a postal or other address, for example of a
publisher, an organization, or an individual.</desc><attList></attList><exemplum><eg><![CDATA[<address><street>via Marsala 24</street>
        <postCode>40126</postCode>
        <name>Bologna</name>
        <name n=I>Italy</name>
</address>]]></eg></exemplum><exemplum><eg><![CDATA[<address>
<addrLine>Computing Center, MC 135</addrLine>
<addrLine>P.O. Box 6998</addrLine>
<addrLine>Chicago, IL</addrLine>
<addrLine>60680 USA</addrLine>
</address>]]></eg></exemplum><remarks><p>Addresses may be encoded either as a sequence of
lines, or using any sequence of address component elements.</p></remarks><part type="base" name="core"/><classes names="DATA"/><dataDesc>If given as running prose, use a consistent format wherever
possible, for example separating lines of the address by commas, and
including any postal code in the standard form.</dataDesc><elemDecl>- O
  (addrLine+ | (%m.addrPart)*)</elemDecl><!-- (rs | name | --><!-- persName | orgName | locName | aptPos | street | stNum | stName --><!-- | postbox | placeName | city | region | country | postcode)* --><xref target="CONAAD"/><xref target="HD24"/><xref target="COBICOI"/><!-- <xref target='LM'> --></tagDoc><?tei:EOF address.tag ??><!-- address element --><?tei:SOF addrline.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- Revisions:                                               --><!-- *****************************************************addrLine --><tagDoc id="ADDRLINE" usage="opt"><gi tei="yes">addrLine</gi><desc>contains one line of a postal or other address.</desc><attList></attList><exemplum><eg><![CDATA[<address>
<addrLine>Computing Center, MC 135
<addrLine>P.O. Box 6998</>
<addrLine>Chicago, IL</>
<addrLine>60680 USA</>
</address>]]></eg></exemplum><remarks><p>Addresses may be encoded either as a sequence of 
lines, or using any sequence of address component elements.</p></remarks><part type="base" name="core"/><classes/><dataDesc></dataDesc><elemDecl>- o  (%phrase.seq)</elemDecl><xref target="CONAAD"/><xref target="HD24"/><xref target="COBICOI"/></tagDoc><?tei:EOF addrline.tag ??><!-- addrLine element --><?tei:SOF addspan.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	addspan.tag,v $
# Revision 1.6  98/01/28  13:43:23  tei
# cosmetic change to log
# 
    * Revision 1.5  1998/01/28 13:41:23  tei
    * LB changes Jan 98, changed class membership to editincl
    *
    * Revision 1.4  1994/08/29  15:18:45  msmcq
    * fixes for unreachability
    *
    * Revision 1.3  1994/03/25  17:21:51  msmcq
    * cleanup of miscellaneous tagdocs:  some typos,
    * some INHERITED errors, supplied explicit end-tags for many attdef parts
    * to shield a weakness of oddref1 (now fixed)
    *
    * Revision 1.2  1994/03/08  03:20:58  msmcq
    * revision for P3
    *
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- Revisions:                                               --><!-- 4 Jan 98: LB : changed class membership from edit to editincl --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- 94-03-21 : MSM : correct 'inherited' error               --><!-- 94-03-03 : MSM : add TYPE att for // to delSpan          --><!-- 94-03-03 : MSM : change example from add.span            --><!-- *********************************************** addSpan --><tagDoc id="ADDSPAN" usage="opt"><gi tei="yes">addSpan</gi><name>added span of text</name><desc>marks the beginning of a longer sequence of text added by an
author, scribe, annotator or corrector (see also
<gi tei="yes">add</gi>).</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the addition, using any convenient typology.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................. place --><attDef usage="rec"><attName>place</attName><desc>indicates where the addition is made.</desc><datatype>CDATA</datatype><valList type="semi"><val>inline </val><desc>addition is made in a space left in the witness by
an
earlier scribe.</desc><val>supralinear </val><desc>addition is made above the line.</desc><val>infralinear </val><desc>addition is made below the line.</desc><val>marginleft </val><desc>addition is made in left margin.</desc><val>marginright </val><desc>addition is made in right margin.</desc><val>margintop </val><desc>addition is made in top margin.</desc><val>marginbot </val><desc>addition is made in bottom margin.</desc><val>overleaf </val><desc>addition is made on the other side of the leaf.</desc></valList><default>#IMPLIED</default><eg><![CDATA[Then they went back home.
<addSpan place='supralinear marginright overleaf' to=p23>
When they got there, ...]]></eg><remarks><p>Long additions may frequently spill from one location to
another; in this case, more than one value may be given, as shown in
the example above.</p></remarks></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for identifying
the hand of the addition.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the
identification of the hand of the addition.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>signifies the hand of the agent which made the addition.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ..................................................... to --><attDef usage="req"><attName>to</attName><desc>identifies the endpoint of the added passage, by giving the ID
of an <gi tei="yes">anchor</gi> or other empty element placed there.</desc><datatype>IDREF</datatype><valDesc>any valid SGML identifier, used on a later element.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p>Both the beginning and the end of the added material must
be marked; the beginning by the <gi tei="yes">addSpan</gi> element itself, the
end by the <att tei="yes">to</att> attribute.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p> (optional)</p></remarks><part type="top" name="tc"/><classes names="EDITINCL"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="PHAD"/></tagDoc><?tei:EOF addspan.tag ??><!-- addSpan element --><?tei:SOF admin.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	admin.tag,v $
# Revision 1.4  94/03/21  14:33:05  lou
# second major typo purge
# 
# Revision 1.3  1994/01/04  12:13:27  lou
# fix xrefs
#
# Revision 1.2  1993/09/15  23:08:09  msmcq
# Change class membership
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : include in class termmisc               --><!-- 92-12-23 : MSM : expand TC37dd entity                    --><!-- 92-12-18 : MSM : add /p to exemplum                      --><!-- 92-12-18 : MSM : remove FLATTERM class                   --><!-- 92-12-18 : SEW, MSM : incorporate SEW's changes          --><!-- 92-12-15 : MSM : add date, resp attributes               --><!-- 92-12-15 : MSM : change suggested values for type        --><!-- 92-11-23 : MSM : define default                          --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- ************************************************** admin --><tagDoc id="ADMIN" usage="rec"><gi tei="yes">admin</gi><name>administrative information</name><desc>within a <gi tei="yes">termEntry</gi> element, contains administrative
information pertaining to data management and documentation of the
entry.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>identifies the administrative event or information using some
typology, preferably the dictionary of data element types specified in
ISO WD 12 620.</desc><datatype>CDATA</datatype><valList type="semi"><val>responsibility</val><desc>The <gi tei="yes">admin</gi> element identifies the agency
                   or individual responsible for the data element or
                   entry.</desc><val>created </val><desc>The <gi tei="yes">admin</gi> element describes the creation of
                   the data element or entry.</desc><val>updated </val><desc>The <gi tei="yes">admin</gi> element describes the update or
                   modification of the data element or entry.</desc><val>approved </val><desc>The <gi tei="yes">admin</gi> element describes the final
                   approval of the data element or entry.</desc><val>domain </val><desc>The element indicates the subject area to which a
                  concept pertains.</desc><val>subdomain </val><desc>The element indicates the subdomain of the subject
                  area to which the concept pertains.</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>A much fuller list of values for the <att tei="yes">type</att>
attribute may be generated from the dictionary of data element types
under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in
Terminology.  See ISO 12 620 for fuller details.</p></remarks></attDef><!-- ................................................... date --><attDef usage="rwa"><attName>date</attName><desc>indicates the date of the administrative event or information
marked by the element.</desc><datatype>CDATA</datatype><valDesc>a date in ISO standard form (yyyy-mm-dd).</valDesc><default>%ISO-date</default><eg><![CDATA[ ]]></eg><remarks><p>The <att tei="yes">date</att> attribute should be used on the
<gi tei="yes">admin</gi> element to indicate the date of the administrative
process (creation, update, approval, etc.) being recorded, rather than a
separate <gi tei="yes">date</gi> element linked to the <gi tei="yes">admin</gi> element by a
<att tei="yes">depend</att> attribute.</p></remarks></attDef><!-- ................................................... resp --><attDef usage="rwa"><attName>resp</attName><name>responsibility</name><desc>indicates the agency or individual responsible for the entry
or data element on which the <gi tei="yes">admin</gi> element depends, or for
the administrative procedure recorded by the <gi tei="yes">admin</gi> element.</desc><datatype>CDATA</datatype><valDesc>any string of characters (usually the acronym of the agency or
the initials of an individual).</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>Some terminological database systems treat responsibility
as a cross reference to a personnel entry.</p></remarks></attDef></attList><exemplum><p>For domain or other similar information, the <gi tei="yes">admin</gi>
element should be used to provide the domain information as the content
of the element:</p><eg><![CDATA[<admin depend=te84.11
       type='domain'
       resp='ISO/TC 61, Plastics'>plastics</admin>]]></eg></exemplum><exemplum><p>In the case of responsibility information or information
about maintenance of the entry, the <gi tei="yes">admin</gi> element may have no
content at all, its information all having been conveyed by the
attributes <att tei="yes">type</att>, <att tei="yes">date</att>, and <att tei="yes">resp</att>:</p><eg><![CDATA[<admin depend=te84.11
       type='responsibility'
       resp='ISO/TC 61, Plastics'></admin>]]></eg></exemplum><exemplum><eg><![CDATA[<admin depend=te84.11
       type='created'
       date='1991-10-23'
       resp='SEW'></admin>
<admin depend=te84.11
       type='updated'
       date='1992-12-15'
       resp='MSM'></admin>]]></eg></exemplum><remarks><p>Administrative data take widely varying forms in different
terminological databases; the <att tei="yes">type</att> attribute should be used
to indicate the particular class of administrative information involved.
The <gi tei="yes">admin</gi> element should also be used to record dates of
major changes to the term entry, if these are to be recorded.</p></remarks><part type="base" name="term"/><classes names="TERMMISC"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="TEDTF"/><xref target="TEDTN"/><xref target="TETA" type="div1"/></tagDoc><?tei:EOF admin.tag ??><!-- admin element --><?tei:SOF affiliat.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: affiliat.tag,v $
    * Revision 1.3  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.2  94/08/29  15:18:45  msmcq
    * fixes for unreachability
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : x affiliat tag                          --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *********************************************** affiliat --><tagDoc id="AFFILIAT" usage="opt"><gi tei="yes">affiliation</gi><name>affiliation</name><desc>contains an informal description of a person's present
or past affiliation with some
organization, for example an employer or sponsor.</desc><attList></attList><exemplum><eg><![CDATA[    <affiliation>Junior project officer for the US
     <name type=org>National Endowment for the Humanities</name>
    </affiliation>]]></eg></exemplum><remarks><p>If included, the name of the organization may be tagged
using either the <gi tei="yes">name</gi> element as above, or (when the additional
tag set for names and dates is in use) the more specific
<gi tei="yes">orgName</gi> element.</p></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc>May contain character data and phrase-level
elements.</dataDesc><elemDecl> - - (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF affiliat.tag ??><!-- affiliation element --><?tei:SOF alt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	alt.tag,v $
# Revision 1.4  94/08/29  15:18:45  msmcq
# fixes for unreachability
# 
# Revision 1.3  1994/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# --><!-- wont do as it stands: cant have YN as value for 3 attribs! --><!-- *********************************************** alt      --><!-- Revisions: --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 94-04-07 : MSM : add to class cplxval                    --><!-- 7 feb : LB: change attrib names perc to wscale, excl to mode and --><!--   remove special case targfunc --><!-- 93-07-22 : DTL : create                                          --><tagDoc id="ALT" usage="opt"><gi tei="yes">alt</gi><name>alternation</name><desc>identifies an alternation or a set of choices among elements or
passages.</desc><attList><attDef usage="req"><attName>targets</attName><desc>specifies the SGML identifiers of the alternative elements or
passages.</desc><datatype>IDREFS
 </datatype><valDesc>Each value specified must be the same as that specified as
    value for an <att tei="yes">ID</att> attribute for some other element in the
    current SGML document.</valDesc><default>#REQUIRED</default></attDef><attDef usage="rec"><attName>mode</attName><desc>states whether the alternations gathered in this collection are
exclusive or inclusive.</desc><datatype>(excl|incl)</datatype><valList type="open"><val>excl</val><desc>indicates that the alternation is exclusive, i.e. that at
most one of the alternatives occurs.</desc><val>incl</val><desc>indicates that the alternation is not exclusive, i.e. that
one or more of the alternatives occur.</desc></valList><default>%INHERITED</default></attDef><attDef usage="opt"><attName>weights</attName><desc>If <att tei="yes">mode=excl</att>, each weight states the probability that the
corresponding alternative occurs.  If <att tei="yes">mode=incl</att> each weight
states the probability that the corresponding alternative occurs given
that at least one of the other alternatives occurs.</desc><datatype>NUMBERS</datatype><valDesc>a list of numbers, in the range from 0 to 1 if
<att tei="yes">wScale=real</att>, and in the range from 0 to 100 if
<att tei="yes">wScale=perc</att>.</valDesc><default>#IMPLIED</default><remarks><p>If <att tei="yes">mode=excl</att> then sum of weights must be 1 (or 100%).
If <att tei="yes">mode=incl</att>, then sum of weights must be in the range from 0 to
the number of alternants (or 0 to 100% times the number of alternants).</p></remarks></attDef><attDef usage="opt"><attName>wScale</attName><desc>indicates the scale used to express the value of the
<att tei="yes">weights</att> attribute value.</desc><datatype>(perc|real)</datatype><valList type="closed"><val>perc</val><desc>indicates that the weights are expressed as percentages.</desc><val>real</val><desc>indicates that the weights are expressed as values
between 0 and 1.</desc></valList><default>%INHERITED</default></attDef><attDef usage="opt"><attName>targOrder</attName><desc>specifies whether the targets are ordered.</desc><datatype>(Y|N)</datatype><valList type="open"><val>Y </val><desc>indicates that the targets are ordered.</desc><val>N </val><desc>indicates that the targets are not ordered.</desc></valList><default>N</default><remarks><p>This attribute is one of those assigned to elements of the
pointer class.  It is specified here so as to assign it a default value.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<alt excl=Y targType='u u' targets='we.fun we.sun' weights='50 50'>]]></eg></exemplum><remarks><p></p></remarks><part type="top" name="link"/><!-- occurs in altGrp, fsLib, fLib, fvLib, and as inclusion exception
     elsewhere --><classes names="POINTER CPLXVAL METADATA"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="SAAT"/></tagDoc><!-- shd probably kill targorder -its meaningless on this element --><?tei:EOF alt.tag ??><!-- alt element --><?tei:SOF altgrp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	altgrp.tag,v $
# Revision 1.5  94/08/29  15:18:45  msmcq
# fixes for unreachability
#  --><!-- ************************************************ altGrp  --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : Added RCS id                            --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 7 feb 94 : LB  : fix illegal attributes  as per alt      --><!-- 93-07-22 : DTL : create, based on definition of joinGrp  --><tagDoc id="ALTGRP" usage="opt"><gi tei="yes">altGrp</gi><name>alternation group</name><desc>groups a collection of <gi tei="yes">alt</gi> elements and possibly
pointers.</desc><attList><attDef usage="opt"><attName>mode</attName><desc>states whether the alternations gathered in this collection are
exclusive or inclusive.</desc><datatype>(excl|incl)</datatype><valList type="open"><val>excl</val><desc>indicates that the alternation is exclusive, i.e. that at
most one of the alternatives occurs.</desc><val>incl</val><desc>indicates that the alternation is not exclusive, i.e. that
one or more of the alternatives occur.</desc></valList><default>excl</default></attDef><attDef usage="opt"><attName>wScale</attName><desc>indicates the scale used to express the value of the
<att tei="yes">weights</att> attribute value.</desc><datatype>(perc|real)</datatype><valList type="closed"><val>perc</val><desc>indicates that the weights are expressed as percentages.</desc><val>real</val><desc>indicates that the weights are expressed as values
between 0 and 1.</desc></valList><default>perc</default></attDef><!-- <attDef usage=opt> --><!-- <attName>targFunc --><!-- <desc>lists the functions of the individual targets. --><!-- <datatype>NAMES --><!-- <valDesc>descriptions of the functions of the targets. --><!-- <default>'first.alternant next.alternant' --><!-- <remarks><p>The <att>targFunc</att> attribute is one of the --><!-- attributes assigned to elements of the grouper class.  --><!-- It is specifically defined here so that it may be assigned --><!-- a default value. --><!-- </attDef> --></attList><exemplum><eg><![CDATA[<altGrp mode=excl>
  <alt targType='seg seg' targets='dm lt bb' weights='50 25 25'>
  <alt targType='l l' targets='rl db' weights='50 50'>
</altGrp>]]></eg></exemplum><exemplum><eg><![CDATA[<altGrp mode=incl wScale=perc targType='seg l'>
  <alt targets='dm rl' weights='90 90'>
  <alt targets='lt rl' weights='5 5'>
  <alt targets='bb rl' weights='5 5'>
  <alt targets='dm db' weights='10 10'>
  <alt targets='lt db' weights='45 90'>
  <alt targets='bb db' weights='45 90'>
</altGrp>]]></eg></exemplum><part type="top" name="link"/><!-- Where contained?  Part of header?  --><classes names="PTRGROUP METADATA"/><dataDesc>Any number of alternations, pointers or extended pointers.</dataDesc><elemDecl>- - ((alt | ptr | xptr)*)</elemDecl><xref target="SAAT"/></tagDoc><?tei:EOF altgrp.tag ??><!-- altGrp element --><?tei:SOF analytic.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	analytic.tag,v $
# Revision 1.2  94/01/04  12:13:28  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-06 : MSM : correct xref to clbibl                  --><!-- 92-12-06 : MSM : correct xref, tighten content model     --><!-- 92-12-02 : MSM : made file                               --><!-- *********************************************** analytic --><tagDoc id="ANALYTIC" usage="mwa"><gi tei="yes">analytic</gi><name>analytic level</name><desc>contains bibliographic elements describing an item (e.g. an
article or poem) published within a monograph or journal and not as an
independent publication.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The <gi tei="yes">analytic</gi> element may occur only within
bibliographic citation or reference elements; it is mandatory for
description of the analytic level of <gi tei="yes">bibl.struct</gi> elements.</p></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc>May contain titles and statements of responsibility (author,
editor, or other), in any order.</dataDesc><elemDecl>- O  (author | editor | respStmt | title)*</elemDecl><xref target="COBICOL"/></tagDoc><?tei:EOF analytic.tag ??><!-- analytic element --><?tei:SOF anchor.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	anchor.tag,v $
# Revision 1.5  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.4  1994/02/12  22:10:37  msmcq
    * recover version 1.2 changes, overwritten by 1.3 (in error?)
    *
    * Revision 1.2  1994/01/07  20:51:20  msmcq
    * Merge in revisions by DTL, summer 1993
    *
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : change class membership from clseg to globincl --><!-- 94-01-07 : MSM : merge DTL's revisions of summer 1993    --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************* anchor --><tagDoc id="ANCHOR" usage="rec"><gi tei="yes">anchor</gi><name>anchor point</name><desc>attaches an identifier to a
point within a text, whether or not it corresponds with a textual
element.</desc><attList><attDef usage="req"><attName>id</attName><name>identifier</name><desc>supplies an arbitrary name, unique within the document,
      used to identify the point at which this element occurs.</desc><datatype>ID</datatype><valDesc>any valid name</valDesc><default>#REQUIRED</default><remarks><p>IDs may be chosen freely; note in particular that if
they include numeric values there is no requirement for these to be in
sequence.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<s>The anchor is he<anchor id=A234>re somewhere.</s>
<s>Help me find it.<ptr target=A234></s>]]></eg></exemplum><remarks></remarks><part type="top" name="sa"/><classes names="GLOBINCL TYPED"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TSSAPA"/><xref target="SACS"/></tagDoc><?tei:EOF anchor.tag ??><!-- anchor element --><?tei:SOF any.tag ??><!-- ************************************************************ --><!-- TAGDOC for ANY                                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	any.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class boolean                    --><!-- 93-09-22 : MSM : extract from group file                 --><!-- ************************************************************ --><tagDoc id="ANY" usage="rwa"><gi tei="yes">any</gi><name>Any value</name><desc>represents boolean <term>true</term> value variable.</desc><attList></attList><exemplum><eg><![CDATA[<f name=gender><any>]]></eg></exemplum><part type="top" name="fs"/><classes names="BOOLEAN"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSBO" type="div3"/></tagDoc><?tei:EOF any.tag ??><!-- any element --><?tei:SOF app.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- 94-04-06 : MSM : suppress remarks elements as needed     --><!-- 94-03-03 : MSM : allow WIT after rdg, rdgGrp             --><!-- 94-03-03 : MSM : fix GI of rdgGrp                        --><!-- 94-01-25 : MSM : suppress subvar att                     --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	app.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/08/29  15:18:45  msmcq
    * fixes for unreachability
    *
    * Revision 1.4  1994/04/07  02:49:28  msmcq
    * Misc. cleanups (mostly suppressed remarks)
    *
    * Revision 1.3  1994/03/08  03:20:58  msmcq
    * revision for P3
    *
    * Revision 1.2  1994/02/07  20:56:16  msmcq
    * revisions for P3
    *
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- ENTITY app      system 'app.tag' --><!-- app tag --><!-- 4 Jan 98 : LB : change content model per MSM 1996-06-13 --><!-- **************************************************** app --><tagDoc id="APP" usage="mwa"><gi tei="yes">app</gi><name>apparatus entry</name><desc>contains one entry in a critical apparatus, with an optional
lemma and at least one reading.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the variation contained in this element according to
some convenient typology.</desc><datatype>CDATA</datatype><valDesc>Any convenient descriptive word or phrase, describing the
extent of the variation (e.g.  <q>word</q>, <q>phrase</q>,
<q>punctuation</q>, etc.) its text-critical significance (e.g.
<q>significant</q>, <q>accidental</q>, <q>unclear</q>), or the nature
of the variation or the principles required to understand it (e.g.
<q>lectio difficilior</q>, <q>usus auctoris</q>, etc.)</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p>[If this attribute and those on              --><!-- <gi>rdg</gi> are to be useful, we need to distinguish    --><!-- clearly among characteristics of individual readings,    --><!-- characteristics of the variation as a whole, and         --><!-- characteristics of sub-portions of the variation.        --><!-- Being orthographic or substantive is not a               --><!-- characteristic of a reading in isolation, only of a      --><!-- pair of readings; a single variation can involve both    --><!-- substantive and orthographic variation; what is its      --><!-- <att>type</att> then?  If we want a serious typology     --><!-- of variation types, we should work from Greg or          --><!-- Dearing, or possibly from Quentin or Zarri.  Failing     --><!-- that, we should at least take our sample values from     --><!-- them rather than making them up as we do now. -MSM]      --></attDef><!-- ................................................... subvar --><!-- suppressed:  msm --><!-- ................................................... from --><attDef usage="opt"><attName>from</attName><desc>identifies the beginning of the lemma in the base text, if
necessary.</desc><datatype>IDREF</datatype><valDesc>a valid SGML ID.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute is only used when the double-end point
method of apparatus markup is used.</p></remarks></attDef><!-- ..................................................... to --><attDef usage="opt"><attName>to</attName><desc>identifies the endpoint of the lemma in the base text, if
necessary.</desc><datatype>IDREF</datatype><valDesc>a valid SGML ID.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute is only used when the double-end point
method of apparatus markup is used, with the encoded apparatus held
in a separate file rather than being embedded <term>in-line</term> in
the base-text file.</p></remarks></attDef><!-- .................................................... loc --><attDef usage="mwa"><attName>loc</attName><name>location</name><desc>indicates the location of the variation, when the
location-referenced method of apparatus markup is used.</desc><datatype>CDATA</datatype><valDesc>Any string containing a canonical reference for the passage
to which the variation applies.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute is used only when the location-referenced
encoding method is used.<!-- [Suppress it and use <att>from</att> instead?  -MSM]     --></p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="top" name="tc"/><classes names="EDIT"/><dataDesc>May contain an optional lemma and one or more readings or
reading groups.<!-- formerly  (lem?, ((rdg, wit?) | (rdgGrp, wit?))+) --></dataDesc><elemDecl>- O  ((lem, wit?)?, ((rdg, wit?) | (rdgGrp, wit?))+)</elemDecl><xref target="TCAPEN"/></tagDoc><?tei:EOF app.tag ??><!-- app element --><?tei:SOF arc.tag ??><!-- ********** ARC                                           --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	arc.tag,v $
# Revision 1.4  94/01/04  12:13:29  lou
# fix xrefs
# 
# Revision 1.3  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
# --><!-- ********** ARC                                           --><!-- Revisions:                                               --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version                       --><!--                  merge ARC and EDGE tags                 --><!--                  eliminate LABEL content (retain label=) --><!--                  add label2= (for encoding transducers)  --><!--                  eliminate special drawing attributes    --><!--                      (use rend=)                         --><!-- ********** ARC                                           --><tagDoc id="ARC" usage="opt"><gi tei="yes">arc</gi><desc>encodes an arc, the connection from one node to another in a graph.</desc><attList><attDef id="ARLAB" usage="opt"><attName>label</attName><desc>gives a label for an arc.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef id="ARLAB2" usage="opt"><attName>label2</attName><desc>gives a second label for an arc.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default><remarks><p>Use this attribute together with the <att tei="yes">label</att>
attribute if a transducer is being encoded.</p></remarks></attDef><attDef id="ARFROM" usage="req"><attName>from</attName><desc>gives the ID of the node which is adjacent from this arc.</desc><datatype>IDREF</datatype><valDesc>The ID of a node.</valDesc><default>#REQUIRED</default></attDef><attDef id="ARTO" usage="req"><attName>to</attName><desc>gives the ID of the node which is adjacent to this arc.</desc><datatype>IDREF</datatype><valDesc>The ID of a node.</valDesc><default>#REQUIRED</default></attDef></attList><exemplum><eg><![CDATA[<arc from=t3 to=t3 label='OLD' label2='VIEUX'>]]></eg></exemplum><remarks><p>The <gi tei="yes">arc</gi> element must be used if the arcs are
labeled.  Otherwise, arcs can be encoded using the <att tei="yes">adj</att>,
<att tei="yes">adjTo</att> and <att tei="yes">adjFrom</att> attributes on the <gi tei="yes">node</gi>
tags in the graph.  Both <gi tei="yes">arc</gi> tags and adjacency attributes can
be used, but the resulting encoding would be highly redundant.</p></remarks><part type="top" name="graphs"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="GDGR"/></tagDoc><?tei:EOF arc.tag ??><!-- arc element --><?tei:SOF argument.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: argument.tag,v $
    * Revision 1.3  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.2  94/01/04  12:13:30  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- 28 dec 93 : LB : fix cross reference --><!-- ***************************************************argument --><tagDoc id="ARGUMENT" usage="opt"><gi tei="yes">argument</gi><desc>A formal list or prose description of the topics addressed by
a subdivision of a text.</desc><attList></attList><exemplum><eg><![CDATA[<argument>
<p>Monte Video &dash; Maldonado &dash; Excursion
to R Polanco &dash; Lazo and Bolas &dash; Partridges &dash;
Absence of Trees &dash; Deer &dash; Capybara, or River Hog &dash;
Tucutuco &dash; Molothrus, cuckoo-like habits &dash; Tyrant
Flycatcher &dash; Mocking-bird &dash; Carrion Hawks &dash;
Tubes formed by Lightning &dash; House struck
</argument>]]></eg></exemplum><!-- Darwin Voyage of the Beagle --><remarks></remarks><part type="base" name="core"/><classes names="DIVTOP FMCHUNK"/><dataDesc> Often contains either a list or a paragraph</dataDesc><elemDecl>- - (head?, %component.seq;)</elemDecl><xref target="DSCO"/><xref target="DSDTB"/></tagDoc><?tei:EOF argument.tag ??><!-- argument element --><?tei:SOF att.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : close valList for TEI att               --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-09-10 : MSM : suppress remarks                        --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	att.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/08  23:36:12  msmcq
# change desc, add class sgmlkw
#
# Revision 1.2  1993/08/13  20:49:42  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** att --><tagDoc id="ATT" usage="opt"><gi tei="yes">att</gi><desc>contains the name of an attribute appearing within running text.</desc><attList><attDef usage="opt"><attName>TEI
 </attName><desc>indicates whether this attribute is part of the TEI scheme
(i.e., defined in a TEI DTD fragment) or not.
 </desc><datatype>(yes|no)
 </datatype><valList type="closed"><val>yes</val><desc>this attribute is part of the TEI scheme.
    </desc><val>no</val><desc>this attribute is not part of the TEI scheme.
 </desc></valList><default>yes
 </default></attDef></attList><exemplum><eg><![CDATA[    The TEI defines three <soCalled>global</soCalled> attributes;
    their names are <att>id</att>, <att>rend</att> and <att>n</att>.
    <att TEI=NO>type</att> is not among them.]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes names="SGMLKW"/><dataDesc>May contain a valid SGML name only.</dataDesc><elemDecl>- - (#PCDATA)</elemDecl><!-- was #PCDATA, then NAME, in an apparent attempt to  --><!-- restrict contents to SGML names.  Unfortunately,   --><!-- NAME is not a legal keyword in element decls.      --><xref target="TD"/></tagDoc><?tei:EOF att.tag ??><!-- att element --><?tei:SOF attdef.tag ??><!-- Revisions:                                               --><!-- 93-09-11 : MSM : close vallist on USAGE att              --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	attdef.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/08  23:38:20  msmcq
# remove tabs from elemDecl
#
# Revision 1.2  1993/08/13  20:49:42  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** attDef --><tagDoc id="ATTDEF" usage="mwa"><gi tei="yes">attDef</gi><name>attribute definition</name><desc>contains the definition of a single attribute.</desc><attList><attDef usage="opt"><attName>usage
 </attName><desc>specifies the optionality of an attribute or element.
 </desc><datatype>(req|mwa|rec|rwa|opt)
 </datatype><valList type="closed"><val>req</val><desc>required
  </desc><val>mwa</val><desc>mandatory when applicable
  </desc><val>rec</val><desc>recommended
  </desc><val>rwa</val><desc>recommended when applicable
  </desc><val>opt</val><desc>optional
 </desc></valList><default>opt
 </default></attDef></attList><exemplum><eg><![CDATA[ <attDef usage=rec>
<attName>type</attName>
<desc>specifies a name conventionally used
for this level of subdivision, e.g. <q>act</q>,
<q>volume</q>, <q>book</q>, <q>section</q>, <q>canto</q>, etc.</desc>
<datatype>CDATA
<valDesc>any string of characters</valDesc>
<default>#CURRENT
</attDef>]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl> - O (attName, rs?, desc,
(datatype, (valList | valDesc)?),
default, eg?, remarks?, equiv*)</elemDecl><xref target="TDATT"/></tagDoc><?tei:EOF attdef.tag ??><!-- attDef element --><?tei:SOF attldecl.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : revise dataDesc, give new example       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	attldecl.tag,v $
# Revision 1.3  93/09/16  14:50:19  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:49:43  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** attlDecl --><tagDoc id="ATTLDECL" usage="req"><gi tei="yes">attlDecl</gi><name>attList declaration</name><desc>contains the SGML ATTLIST declaration associated with this
element.</desc><attList></attList><exemplum><p>If the opening delimiter is parsed by the SGML parser, an error will
result; it should therefore be represented by an entity reference, thus:</p><eg><![CDATA[<attlDecl>
 &lt;!ATTLIST blort
              id       ID       #REQUIRED
              rend     CDATA    #IMPLIED   >
</attlDecl>]]></eg><p>Alternatively, the entire element content may be enclosed in
a CDATA marked section:
<eg>&lt;attlDecl&gt;
 &lt;![ CDATA [
 &lt;!ATTLIST blort
              id       ID       #REQUIRED
              rend     CDATA    #IMPLIED   &gt;
 ]]&gt;
&lt;/attlDecl&gt;</eg></p></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>contains the full text of an SGML ATTLIST declaration; to
avoid parsing errors, the opening delimiter must be given as an entity
reference, or else the entire content of the element
should be enclosed in a CDATA marked section.</dataDesc><elemDecl>- - (#PCDATA)</elemDecl><xref target="TDTAG"/></tagDoc><?tei:EOF attldecl.tag ??><!-- attlDecl element --><?tei:SOF attlist.tag ??><!-- Revisions:                                               --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-09-14 : MSM : make model attDef* not attDef+          --><!--                  one may want to stress the emptiness    --><!--                  of the local attribute def list         --><!--                  (as we do in Odds and P2X files)        --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	attlist.tag,v $
# Revision 1.5  94/01/04  12:13:31  lou
# fix xrefs
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/08  23:39:03  msmcq
# Cosmetic changes
#
# Revision 1.2  1993/08/13  20:49:44  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** attList --><tagDoc id="ATTLIST" usage="mwa"><gi tei="yes">attList</gi><desc>contains documentation for all the attributes associated with this
element, as a series of <gi tei="yes">attDef</gi> elements.</desc><attList></attList><exemplum><eg><![CDATA[<attList>
   <attDef> ... </attDef>
   <attDef> ... </attDef>
</attList>]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes/><dataDesc>contains a series of <gi tei="yes">attDef</gi> elements only</dataDesc><elemDecl>- O (attDef*)</elemDecl><xref target="TDTAG"/><xref target="TDCLA"/></tagDoc><?tei:EOF attlist.tag ??><!-- attList element --><?tei:SOF attname.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : change dataDesc                         --><!-- 93-09-11 : MSM : change desc                             --><!-- 93-09-11 : MSM : uppercase omissibility sign             --><!-- 93-09-11 : MSM : correct content model                   --><!-- 93-09-10 : MSM : suppress remarks                        --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	attname.tag,v $
# Revision 1.3  93/09/16  14:50:19  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:49:44  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** attName --><tagDoc id="ATTNAME" usage="mwa"><gi tei="yes">attName</gi><name>attribute name</name><desc>contains the name of the attribute being defined by an
<gi tei="yes">attDef</gi> element.</desc><attList></attList><exemplum><eg><![CDATA[    <attName>type</attName>]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes/><dataDesc>must be a valid SGML name.</dataDesc><elemDecl>- O (#PCDATA) </elemDecl><!-- odd has #pcdata --><!-- and right it is, too --><xref target="TDATT"/></tagDoc><?tei:EOF attname.tag ??><!-- attName element --><?tei:SOF author.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	author.tag,v $
# Revision 1.2  94/01/04  12:13:31  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-06-02 : MSM : recast desc                             --><!-- 92-12-09 : MSM : rename class from bibl to biblpart      --><!-- 92-12-09 : MSM : change broth to phrase.seq, add class info --><!-- 92-12-09 : MSM : correct typo in example                 --><!-- 92-11-09 : MSM : fix xref to CObi                        --><!-- 92-08-19 : MSM : fix xref to chapter HD/22               --><!-- ****************************************************** author --><tagDoc id="AUTHOR" usage="opt"><gi tei="yes">author</gi><desc>in a bibliographic reference, contains the name of the author(s),
personal or corporate,
of a work; the primary <term>statement of responsibility</term> for any
bibliographic item. </desc><attList></attList><exemplum><eg><![CDATA[ <author>British Broadcasting Corporation
 <author>La Fayette, Marie Madeleine Pioche de la Vergne,
         comtesse de (1634-1693)]]></eg></exemplum><remarks><p>Particularly where cataloguing is likely to be based on
the content of the header, it is advisable to use generally recognized
authority lists for the exact form of personal names.</p><p>In the case of a broadcast, use this element for the name of the
company or network which broadcasts the program.</p></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc>Any string of characters and phrase-level tags.</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="COBICOR"/><xref target="HD21"/></tagDoc><!-- end of AUTHOR --><?tei:EOF author.tag ??><!-- author element --><?tei:SOF authorty.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	authorty.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- ****************************************************authority --><tagDoc id="AUTHORTY" usage="opt"><gi tei="yes">authority</gi><name>release authority</name><desc>supplies the name of a person or other agency responsible for
making an electronic file available, other than a publisher or
distributor.</desc><attList></attList><exemplum><eg><![CDATA[<authority>John Smith]]></eg></exemplum><remarks><!-- < p>Particularly where cataloguing is likely to be       --><!-- based on the content of the header, it is advisable to   --><!-- use generally recognized authority lists for the exact   --><!-- form of personal names.                                  --></remarks><part type="aux" name="hdr"/><classes/><!-- should point to name crystal? --><dataDesc></dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="HD24"/></tagDoc><?tei:EOF authorty.tag ??><!-- authority element --><?tei:SOF avail.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	avail.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-06-01 : MSM : change default status to IMPLIED from unknown --><!-- 92-08-19 : MSM : delete empty name element               --><!-- *************************************************availability --><tagDoc id="AVAIL" usage="opt"><gi tei="yes">availability</gi><desc>supplies information about the availability of a text, for
example any restrictions on its use or distribution, its copyright
status, etc.</desc><attList><attDef usage="opt"><attName>status
   </attName><desc>supplies a code identifying the current availability of the
text.
   </desc><datatype>(free | unknown | restricted)
   </datatype><valList type="open"><val>free</val><desc>the text is freely available.
    </desc><val>unknown</val><desc>the status of the text is unknown.
    </desc><val>restricted</val><desc>the text is not freely available.
   </desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<availability status=restricted>
    <p>Available for academic research purposes only.
<availability status=free>
<availability status=restricted>
    <p>Available under licence from the publishers.]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc>A consistent format should be adopted</dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD24"/></tagDoc><?tei:EOF avail.tag ??><!-- availability element --><?tei:SOF back.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: back.tag,v $
    * Revision 1.7  1999/02/22 15:46:58  tei
    * fix comments
    *
    * Revision 1.6  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.5  1994/03/15 11:10:21  lou
    * minor typos etc
    *
    * Revision 1.4  1994/01/04  12:11:58  lou
    * fix xrefs
    * 
    * Revision 1.3  1993/08/23  16:21:49  msmcq
    * modify content model
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 13 mar: add example --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-08-19 : MSM : fold titlepage into m.front             --><!-- 93-08-19 : MSM : allow m.front in back                   --><!-- 93-08-18 : MSM : case correction in titlepage            --><!-- *********************************************************back --><tagDoc id="BACK" usage="rec"><gi tei="yes">back</gi><name>back matter</name><desc>contains any appendixes, etc. following the main part of a
text.</desc><attList></attList><exemplum><eg><![CDATA[<back>
<div1 type='appendix'>
<head>The Golden Dream or, the Ingenuous Confession</head>
<p>To shew the Depravity of human Nature..
<!-- ... -->
</div1><div1 type=epistle>
<head>A letter from the Printer, which he desires 
may be inserted</head>
<salute>Sir.</salute>
<p>I have done with your Copy, so you may return 
it to the Vatican, if you please
<!-- ... -->
<div1 type=advert>
<head>The Books usually read by the Scholars 
of Mrs Two-Shoes are these and are sold at Mr 
Newbery's at the Bible and Sun in St Paul's
Church-yard.</head>
<list>
<item n=1>The Christmas Box, Price 1d.
<item n=2>The History of Giles Gingerbread, 1d.
<!-- ... -->
<item n=42>A Curious Collection of Travels, 
selected from the Writers of all Nations, 
10 Vol, Pr. bound 1l.
</list>
<div1 type=advert>
<head><hi rend=center>By the KING's Royal Patent,</hi>
Are sold by J. NEWBERY, at the Bible and Sun in 
St. Paul's Church-Yard.</head>
<list>
<item n=1>Dr. James's Powders for Fevers, the 
Small-Pox, Measles, Colds, &amp;c. 2s. 6d
<item n=2>Dr. Hooper's Female Pills, 1s.
<!-- ... -->
</list></div1></back>]]><!-- Good Two-Shoes, 3rd ed 1766 --></eg></exemplum><remarks><p>The content model of back matter is identical to
that of front matter, reflecting the facts of cultural
history.</p></remarks><part type="base" name="core"/><classes names="DECLING"/><elemDecl>- O (  (%m.front)*,
                 (
                   ( (%m.divtop), (%m.divtop | titlePage)*)
                   |
                   ( (div), (div | (%m.front))*)
                   |
                   ( (div1), (div1 | (%m.front))*)
                 )?
              )</elemDecl><!-- < elemdecl > - O ((%m.divtop;)*, ( (div+ | div1+)        --><!--               | ( %component;+, (div* | div1*))),        --><!--               (%m.divbot;)*)                             --><!-- < / elemdecl>                                            --><xref target="DSBACK"/><xref target="DS"/></tagDoc><?tei:EOF back.tag ??><!-- back element --><?tei:SOF basewsd.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	basewsd.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	basewsd.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ************************************************ baseWsd --><tagDoc id="BASEWSD" usage="opt"><gi tei="yes">baseWsd</gi><name>base writing system declaration</name><desc>identifies a writing system declaration whose mappings among
characters, forms, entity names, and bit patterns are to be incorporated
(possibly with modifications) in this writing system declaration.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Reference in a WSD to a base WSD makes available the set of
mappings among characters, forms, entity names, and bit patterns
declared in the base WSD; the language and writing system (direction)
information given in the base WSD is ignored.
 </p></remarks><part type="aux" name="wsd"/><classes names="BASESTD"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="WDCSBA"/></tagDoc><?tei:EOF basewsd.tag ??><!-- baseWsd element --><?tei:SOF bibl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: bibl.tag,v $
    * Revision 1.4  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.3  94/04/07  02:49:28  msmcq
    * Misc. cleanups (mostly suppressed remarks)
    * 
    * Revision 1.2  1994/01/04  12:13:32  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 94-04-06 : MSM : biblPart not bibl.part                  --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-03-08 : MSM : add to class Declabl                    --><!-- 92-12-10 : MSM : correct class name to clbibl            --><!-- 92-12-09 : MSM : assign to class bibl                    --><!-- 92-12-09 : MSM : use bibl.part in content model          --><!-- 92-12-09 : MSM : revise content model                    --><!-- 92-11-09 : MSM : fix xref to CObi                        --><!-- 92-11-09 : MSM : rename BIBL                             --><!-- 92-08-19 : MSM : strip stray entity ref                  --><!-- ******************************************************** bibl --><tagDoc id="BIBL" usage="opt"><gi tei="yes">bibl</gi><name>bibliographic citation</name><desc>contains a loosely-structured bibliographic citation of which
the sub-components may or may not be explicitly tagged. </desc><attList></attList><exemplum><eg><![CDATA[<bibl>Blain, Clements and Grundy: Feminist Companion to Literature in
English (Yale, 1990)
</bibl>]]></eg></exemplum><exemplum><eg><![CDATA[<bibl><title.piece>The Interesting story of the Children in the
 Wood<title.piece>.
    In <author>Victor E Neuberg</author>,
    <title>The Penny Histories</title>.
    <publisher>OUP</publisher>
    <date>1968</date>.
</bibl>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="CLBIBL DECLABL"/><dataDesc>Contains phrase-level elements, together with
any combination of elements from the <term>biblPart</term> class</dataDesc><elemDecl>- o (#PCDATA | %m.phrase; | %m.biblPart;)*</elemDecl><xref target="COBITY"/><xref target="HD3"/><xref target="TETA"/><xref target="CCAS2"/></tagDoc><?tei:EOF bibl.tag ??><!-- bibl element --><?tei:SOF biblfull.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: biblfull.tag,v $
    * Revision 1.3  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.2  94/01/04  12:13:33  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 28 dec 93 : LB : fix cross reference --><!-- 1 jun 93: changed names: NB header tag names not checked --><!-- 92-12-18 : MSM : change desc (source desc is allowed)    --><!-- 92-12-10 : MSM : correct class name to clbibl            --><!-- 92-12-09 : MSM : assign to class bibl                    --><!-- 92-11-09 : MSM : rename BIBL.*, make source desc optional --><!-- 92-08-19 : MSM : delete stray inclusion of author.tagdoc --><!-- 92-08-19 : MSM : change xref to HD/22                    --><!-- *************************************************** biblFull --><tagDoc id="BIBLFULL" usage="opt"><gi tei="yes">biblFull</gi><desc>contains a fully-structured bibliographic citation, in which all
components of the TEI file description
are present.<!-- except maybe the source.desc? --></desc><attList></attList><exemplum><eg><![CDATA[<biblFull>
        <titleStmt>
           <title>The Feminist Companion to Literature in English:
               women writers from the middle ages to the present</title>
           <author>Blain, Virginia</author>
           <author>Clements, Patricia</author>
           <author>Grundy, Isobel</author>
          </titleStmt>
        <editionStmt>
           <edition>UK edition</edition>
        <extent>1231 pp</extent>
        <publicationStmt>
          <publisher>Yale University Press</publisher>
          <pubPlace>New Haven and London</pubPlace>
          <date>1990</date>
        </publicationStmt>
        <sourceDesc><p>No source: this is an original work</sourceDesc>
</biblFull>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="CLBIBL DECLABL"/><dataDesc></dataDesc><elemDecl>- o (titleStmt,   editionStmt?,
               extent?,      publicationStmt,
               seriesStmt?, notesStmt?,
               sourceDesc*)</elemDecl><xref target="COBITY"/><xref target="HD3"/><xref target="TETA"/><xref target="CCAS2"/></tagDoc><?tei:EOF biblfull.tag ??><!-- biblFull element --><?tei:SOF biblscop.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	biblscop.tag,v $
# Revision 1.2  94/01/04  12:13:34  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-09 : MSM : change broth to phrase.seq              --><!-- 92-12-07 : MSM : supply type default implied             --><!-- 92-12-07 : MSM : add TYPE attribute                      --><!-- 92-11-09 : MSM : fix xref to CObi                        --><!-- 92-11-09 : MSM : rename BIBL from CITN                   --><!-- ***************************************************biblScope--><tagDoc id="BIBLSCOP" usage="opt"><gi tei="yes">biblScope</gi><name>scope of citation</name><desc>defines the scope of a bibliographic reference, for example as a
list of pagenumbers, or a named subdivision of a larger work.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>identifies the type of information conveyed by the element, e.g.
<q>pages</q>, <q>volume</q>.</desc><datatype>CDATA</datatype><valList type="semi"><val>volume </val><desc>the element contains a volume number.</desc><val>issue  </val><desc>the element contains an issue number, or volume and
issue numbers.</desc><val>pages  </val><desc>the element contains a page number or page range.</desc><val>chapter</val><desc>the element contains a chapter indication (number
and/or title)</desc><val>part   </val><desc>the element identifies a part of a book or collection.</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[        <biblScope>pp 12-34]]></eg></exemplum><exemplum><eg><![CDATA[        <biblScope>Volume 2 "My apprenticeship"]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="BIBLPART"/><elemDecl>- o (%phrase.seq)</elemDecl><xref target="COBICOI"/></tagDoc><?tei:EOF biblscop.tag ??><!-- biblScope element --><?tei:SOF biblstru.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: biblstru.tag,v $
    * Revision 1.4  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.3  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.2  1994/01/04  12:13:34  lou
    * fix xrefs
    *
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : fix example --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-03-08 : MSM : add to class Declabl                    --><!-- 92-12-10 : MSM : correct class name to clbibl            --><!-- 92-12-09 : MSM : assign to class bibl                    --><!-- 92-12-06 : MSM : tighten content model                   --><!-- 92-11-09 : MSM : rename biblStru                        --><!-- 92-08-19 : MSM : strip stray entity ref                  --><!-- ************************************************* biblStruct --><tagDoc id="BIBLSTRU" usage="opt"><gi tei="yes">biblStruct</gi><name>structured bibliographic citation</name><desc>contains a structured bibliographic citation, in which only
bibliographic subelements appear and in a specified order. </desc><attList></attList><exemplum><eg><![CDATA[<biblStruct>
    <monogr>
         <author>Blain, Virginia</author>
         <author>Clements, Patricia</author>
         <author>Grundy, Isobel</author>
         <title>The Feminist Companion to Literature in
                English: women writers from the middle ages
                to the present</title>
         <edition>first edition</edition>
         <imprint><publisher>Yale University Press</publisher>
                  <pubPlace>New Haven and London</pubPlace>
                  <date>1990</date>
         </imprint>
</monogr>
</biblStruct>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="CLBIBL DECLABL"/><dataDesc></dataDesc><elemDecl>- o (analytic?, (monogr, series*)+, (note | idno)*)</elemDecl><xref target="COBITY"/><xref target="HD3"/><xref target="TETA"/><xref target="CCAS2"/></tagDoc><?tei:EOF biblstru.tag ??><!-- biblStruct element --><?tei:SOF bicond.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : replace fs.family with literal          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	bicond.tag,v $
# Revision 1.2  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY bicond system   'bicond.tag' --><!-- bicond tag --><!-- ************************************************* bicond --><tagDoc id="BICOND" usage="opt"><gi tei="yes">bicond</gi><name>bi-conditional feature-structure constraint</name><desc>defines a biconditional feature-structure constraint; both
consequent and antecedent are specified as feature structures or groups
of feature structures; the constraint is satisfied if both
<term>subsume</term> a given feature structure, or if both do not.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain two feature structures or feature-structure
groups, separated by an empty <gi tei="yes">iff</gi> element.</dataDesc><elemDecl>- O  ((fs | f | fAlt), iff, (fs | f | fAlt))</elemDecl><xref target="FD"/></tagDoc><?tei:EOF bicond.tag ??><!-- bicond element --><?tei:SOF birth.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: birth.tag,v $
    * Revision 1.4  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.3  94/03/15  11:10:21  lou
    * minor typos etc
    * 
    * Revision 1.2  1994/03/01  17:18:50  lou
    * fix typo noted by terry
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- 93-03-10 : MSM : change declared value:  CDATA / ISO-date --><!-- ********************************************************* birth --><tagDoc id="BIRTH" usage="opt"><gi tei="yes">birth</gi><name>Birth details</name><desc>contains information about a person's birth, such as its date
and place.</desc><attList><attDef usage="opt"><attName>date</attName><desc>specifies the date of birth in an ISO standard form (yyyy-mm-dd).</desc><datatype>%ISO-date</datatype><valDesc>a date in ISO standard form (yyyy-mm-dd).</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<birth>Before 1920, Midlands region.</birth>]]></eg></exemplum><exemplum><eg><![CDATA[<birth date=1960-12-10>In a small cottage near
< name type=place>Aix-la-Chapelle</name>,
early in the morning of <date>10 Dec 1960</date>
</birth>]]></eg></exemplum><remarks><p>Dates and place names, if included in the content of this
element, should in general be tagged using the <gi tei="yes">date</gi> and
<gi tei="yes">namee</gi> elements respectively. If the additional tagset for
Names and Dates is in use, the more specific elements defined by that
tagset may be used as an alternative.</p></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc></dataDesc><elemDecl>- - (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF birth.tag ??><!-- birth element --><?tei:SOF bloc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	bloc.tag,v $
# Revision 1.2  94/03/07  16:17:06  lou
# revised for initial check in of ND
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--********************************************************bloc--><tagDoc id="BLOC" usage="opt"><gi tei="yes">bloc</gi><name>bloc</name><desc>a geo-political unit containing one or more nation states.</desc><attList></attList><exemplum><eg><![CDATA[<bloc type='economic union'>the European Union</bloc>
<bloc type='continent'>Africa</bloc>]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes names="PLACPART"/><elemDecl>- - (%phrase.seq)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF bloc.tag ??><!-- bloc element --><?tei:SOF body.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : correct content model again (don't require two divs) --><!-- 94-08-04 : MSM : remove ambiguity by Swiss method (egads) --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	body.tag,v $
# Revision 1.4  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.3  1994/01/04  12:13:35  lou
# fix xrefs
#
# Revision 1.2  1993/08/18  22:39:21  msmcq
# parenthesize component entity
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *********************************************************body --><tagDoc id="BODY" usage="req"><gi tei="yes">body</gi><name>text body</name><desc>contains the whole body of a single unitary
text, excluding any front or back
matter.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DECLING"/><elemDecl>- O ((%m.divtop;)*,
          (
              ( divGen*, (
              (div, (div|divGen)*) |
              (div0, (div0|divGen)*) |
              (div1, (div1|divGen)*) )
              )
              | ( (%component)+,
                  (divGen*, (
                    (div, (div|divGen)*) |
                    (div0, (div0|divGen)*) |
                    (div1, (div1|divGen)*) )?
                  ))),
              (%m.divbot;)*)</elemDecl><xref target="DS"/><xref target="TEDT"/><!-- multiple declarations --></tagDoc><?tei:EOF body.tag ??><!-- body element --><?tei:SOF broadcas.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	broadcas.tag,v $
# Revision 1.3  94/01/04  12:13:36  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  01:39:35  msmcq
# change old citn to bibl
# --><!-- Revisions:                                               --><!-- 28 dec 93 : LB : fix cross reference --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : change citn to bibl, etc.               --><!-- 93-06-01 : MSM : allow recording in content post Eynsham --><!-- ****************************************************broadcast --><tagDoc id="BROADCAS" usage="opt"><gi tei="yes">broadcast</gi><name>broadcast</name><desc>describes a broadcast used as the source of a spoken text.</desc><attList></attList><exemplum><eg><![CDATA[    <broadcast>
         <bibl>
         <author>Radio Trent
         <title>Gone Tomorrow
         <resp><role>Presenter<name>Tim Maby
         <resp><role>Producer<name>Mary Kerr
         <date>12 June 89, 1230 pm
         </bibl>
    </broadcast>]]></eg></exemplum><!-- why is this a distinct tag, if it just contains a bibl?  --><!--     likewise scriptStmt                                  --><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- - (p+ | bibl | biblStruct | biblFull | recording)</elemDecl><xref target="HD32"/><xref target="CCAS2"/></tagDoc><?tei:EOF broadcas.tag ??><!-- broadcast element --><?tei:SOF byline.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: byline.tag,v $
    * Revision 1.4  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.3  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.2  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- *******************************************************byline --><tagDoc id="BYLINE" usage="opt"><gi tei="yes">byline</gi><desc>contains the primary statement of responsibility given for a work
on its title page or at the head or end of the work.</desc><attList></attList><exemplum><eg><![CDATA[<byline>Written by a CITIZEN who continued all the
while in London. Never made publick before.</byline>]]></eg></exemplum><exemplum><eg><![CDATA[<byline>Written from her own MEMORANDUMS</byline>]]></eg></exemplum><exemplum><eg><![CDATA[<byline>By George Jones, Political Editor, in Washington
</byline>]]></eg></exemplum><exemplum><eg><![CDATA[<dateline>Zagreb:</dateline>
<byline>de notre envoy&eacute; sp&eacute;cial.</byline>]]></eg></exemplum><exemplum><eg><![CDATA[<byline>BY
<docAuthor>THOMAS PHILIPOTT,</docAuthor>
Master of Arts,
(Somtimes)
Of Clare-Hall in Cambridge.
</byline>]]></eg></exemplum><remarks><p>The byline on a title page may include either the name
or a description for the document's author. Where the name is included,
it may optionally be tagged using the <gi tei="yes">docAuthor</gi> element.</p></remarks><part type="base" name="core"/><classes names="DIVTOP DIVBOT TPPARTS FMCHUNK"/><dataDesc></dataDesc><elemDecl>- O (%phrase.seq; | docAuthor)*</elemDecl><xref target="DSOC"/><xref target="DSFRONT"/></tagDoc><?tei:EOF byline.tag ??><!-- byline element --><?tei:SOF c.tag ??><!-- ****************************************************** c --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	c.tag,v $
# Revision 1.3  94/02/27  15:55:55  lou
# Revisions for publication of AI
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 93-09-22 : MSM : change id of seg class to clseg         --><!-- 93-07-22 : DTL : create                                  --><!--                                                          --><!-- ****************************************************** c --><tagDoc id="C" usage="opt"><gi tei="yes">c</gi><name>character</name><desc>represents a character.</desc><attList></attList><exemplum><eg><![CDATA[<c type=punctuation>?</c>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLSEG"/><dataDesc>Character data. Should only contain a single character or an
entity that represents a single character.</dataDesc><elemDecl>- -  (#PCDATA)</elemDecl><xref target="AILC"/></tagDoc><?tei:EOF c.tag ??><!-- c element --><?tei:SOF caesura.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	caesura.tag,v $
# Revision 1.2  93/11/26  18:19:55  msmcq
# revision for publication of VE
# 
# Revision 1.1  1993/08/11  13:00:29  lou
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-11-18 : MSM : fix typo in example                     --><!-- 93-11-18 : MSM : cosmetic:  O for o                      --><!-- 7 Aug 93 : LB : made file                                --><!-- ************************************************ caesura --><tagDoc id="CAESURA" usage="opt"><gi tei="yes">caesura</gi><desc>marks the point at which a metrical line may be divided.</desc><attList></attList><exemplum><eg><![CDATA[<l>Hw&ae;t we Gar-Dena <caesura> in gear-dagum
<l>&t;eod-cyninga <caesura> &t;rym gefrunon,
<l>hy &d;a &ae;&t;elingas <caesura> ellen fremedon.]]></eg><!-- Beowulf, ed Wrenn , 1953 --></exemplum><remarks><p>.</p></remarks><part type="base" name="verse"/><classes names="VEPHR"/><dataDesc>Empty element</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="VESE"/></tagDoc><?tei:EOF caesura.tag ??><!-- caesura element --><?tei:SOF camera.tag ??><!-- Camera tag                                               --><!-- Revisions:                                               --><!-- 93-08-19 : MSM : change class to stagedir                --><!-- 93-08-16 : MSM : cosmetic punctuation change             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	camera.tag,v $
# Revision 1.6  94/01/04  12:13:36  lou
# fix xrefs
# 
# Revision 1.5  1993/08/23  16:23:14  msmcq
# class change for DR publication
#
# Revision 1.3  1993/08/13  20:49:45  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************   CAMERA--><tagDoc id="CAMERA" usage="opt"><gi tei="yes">camera</gi><desc>describes a particular camera angle or viewpoint in a screen play.</desc><attList><attDef usage="opt"><attName>type</attName><desc>characterizes the camera angle in some respect, e.g. as a close-up,
medium shot, etc.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<view>George glances at the window--and freezes.
<camera>New angle--shock cut</camera>
Out the window the body of a dead man suddenly slams into
<hi>frame</hi>
<!-- ... -->
</view>]]></eg></exemplum><remarks></remarks><part type="base" name="perf"/><classes names="STAGEDIR"/><dataDesc>Contains character data and phrase level elements.</dataDesc><elemDecl>- - (%paraContent)</elemDecl><xref target="DRTEC" type="div3"/><xref target="DROTH"/></tagDoc><?tei:EOF camera.tag ??><!-- camera element --><?tei:SOF caption.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: caption.tag,v $
    * Revision 1.8  1999/02/22 15:45:01  tei
    * fix comments
    *
   * Revision 1.7  1998/03/11 18:53:55  tei
   * correcting egs
   *
   * Revision 1.6  1994/01/04 12:13:37  lou
   * fix xrefs
   *
    * Revision 1.5  1993/08/23  16:28:22  msmcq
    * final changes for publication of DR
    * 
    * Revision 1.4  1993/08/13  20:49:46  msmcq
    * Clean ^Z
    * 
    * Revision 1.3  1993/08/12  21:33:20  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.2  1993/08/03  01:41:08  msmcq
    * fix MS end problem
    * --><!-- Revisions:                                               --><!-- 93-08-19 : MSM : change model to paraContent             --><!-- 93-08-19 : MSM : change class to stagedir                --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- ******************************************************   caption--><tagDoc id="CAPTION" usage="opt"><gi tei="yes">caption</gi><desc>contains the text of a caption or other text displayed as part of
a film script or screenplay.</desc><attList></attList><exemplum><eg><![CDATA[<camera>Zoom in to overlay showing some stock film of hansom cabs
galloping past</camera>
<caption>London, 1895.</caption>
<caption>The residence of Mr Oscar Wilde.</caption>
<sound>Suitably classy music starts.</sound>
<view>Mix through to Wilde's drawing room. A crowd of suitably
dressed folk are engaged in typically brilliant conversation,
laughing affectedly and drinking champagne.</view>
<sp who=TJ><speaker>Prince of Wales</speaker>
<p>My congratulations, Wilde. Your latest play is a great success.]]><!-- Monty Pythons Flying Circus, vol 2, p 230 --></eg></exemplum><remarks><p>A specialized form of stage direction.</p></remarks><part type="base" name="perf"/><classes names="STAGEDIR"/><dataDesc>Contains character data and phrase level elements.</dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="DRTEC" type="div3"/><xref target="DROTH" type="div3"/></tagDoc><?tei:EOF caption.tag ??><!-- caption element --><?tei:SOF case.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	case.tag,v $
# Revision 1.3  94/02/12  18:12:57  msmcq
# cosmetic (remove duplicate RCS keywords)
# 
# Revision 1.2  1994/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************* case   --><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : note synonymy with GRAM element         --><!-- 94-01-12 : MSM :                                         --><!-- 94-01-12 : MSM : suppress dleaves class                  --><!-- ************************************************* case   --><tagDoc id="CASE" usage="rec"><gi tei="yes">case</gi><desc>contains grammatical case information given by a dictionary for
a given form.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type=case</tag>.</p></remarks><part type="base" name="dict"/><classes names="DIPARTS MORPH DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.  Typical
values will be of the form <q>nom</q>, <q>acc</q>, <q>dat</q>,
<q>gen</q>, etc.</dataDesc><elemDecl>- -  (%paraContent;)</elemDecl><xref target="DITPFO" type="div2"/></tagDoc><?tei:EOF case.tag ??><!-- case element --><?tei:SOF castgrp.tag ??><!-- CastGroup tag                                            --><!-- Revisions:                                               --><!-- 93-08-20 : MSM : cosmetic                                --><!-- 93-08-20 : MSM : cast list two words                     --><!-- 93-08-16 : MSM : tweak content model                     --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	castgrp.tag,v $
# Revision 1.6  94/02/12  10:44:37  lou
# JL's comments of 4 feb
# 
# Revision 1.5  1993/08/23  16:28:22  msmcq
# final changes for publication of DR
#
# Revision 1.3  1993/08/13  20:49:46  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--****************************** castGrp --><tagDoc id="CASTGRP" usage="opt"><gi tei="yes">castGroup</gi><name>Cast list grouping</name><desc>groups one or more individual <gi tei="yes">castItem</gi>
elements within a cast list.</desc><attList></attList><exemplum><eg><![CDATA[  <castGroup rend=braced><head>friends of Mathias
     <castItem><role>Walter<actor>Mr Frank Hall
     <castItem><role>Hans<actor>Mr F.W. Irish
  </castGroup>]]></eg></exemplum><remarks><p>Use the <att tei="yes">rend</att> attribute to indicate
whether the grouping is indicated by a brace, white space, font change,
etc.</p></remarks><part type="base" name="perf"/><classes/><dataDesc></dataDesc><elemDecl>- - (head?, (castItem | castGroup)+, trailer?)</elemDecl><xref target="DRCAST" type="div3"/></tagDoc><?tei:EOF castgrp.tag ??><!-- castGroup element --><?tei:SOF castitem.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	castitem.tag,v $
# Revision 1.4  93/08/23  16:28:22  msmcq
# final changes for publication of DR
# 
# Revision 1.3  1993/08/13  20:49:47  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:31:15  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-08-20 : MSM : full stop at end of DESC                --><!-- 1993-08-07 : MSM : change content model                  --><!--************************************************ castItem --><tagDoc id="CASTITEM" usage="mwa"><gi tei="yes">castItem</gi><name>Cast list item</name><desc>contains a single entry within a cast list, describing
either a single role or a list of non-speaking roles.</desc><attList><!-- ..................................................  type --><attDef usage="opt"><attName>type
   </attName><desc>characterizes the cast item.
   </desc><datatype>(role | list)
   </datatype><valList type="open"><val>role</val><desc>the item describes a single role.
       </desc><val>list</val><desc>the item describes a list of non-speaking roles.
   </desc></valList><default>role</default></attDef></attList><exemplum><eg><![CDATA[  <castItem><role>Player</><actor>Mr Milward</></castItem>]]></eg></exemplum><exemplum><eg><![CDATA[  <castItem type=list>Constables, Drawer, Turnkey, etc.</castItem>]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes/><dataDesc>Contains character data with phrase-level elements,
<gi tei="yes">role</gi>, <gi tei="yes">roleDesc</gi>, and <gi tei="yes">actor</gi>.</dataDesc><elemDecl>- O (role | roleDesc | actor | (%phrase.seq))*</elemDecl><xref target="DRCAST" type="div3"/></tagDoc><?tei:EOF castitem.tag ??><!-- castItem element --><?tei:SOF castlist.tag ??><!-- CastList tag                                             --><!-- Revisions:                                               --><!-- 11 jan 98 : LB : added to dramafront class as well --><!-- 20 dec 93 : perf changed name to compdram --><!-- 93-08-19 : MSM : allow components before or after list   --><!-- 93-08-16 : MSM : add to class INTER                      --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	castlist.tag,v $
# Revision 1.7  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.6  1994/01/04  12:13:38  lou
    * fix xrefs
    *
    * Revision 1.5  1993/08/23  16:28:22  msmcq
    * final changes for publication of DR
    *
    * Revision 1.3  1993/08/13  20:49:48  msmcq
    * Clean ^Z
    *
    * Revision 1.2  1993/08/12  21:31:15  msmcq
    * Rev. for publication of DR
    *
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!--****************************** castList --><tagDoc id="CASTLIST" usage="mwa"><gi tei="yes">castList</gi><name>cast list</name><desc>contains a single cast list or dramatis personae.</desc><attList></attList><exemplum><eg><![CDATA[<castList>
<castGroup><head rend=braced>Mendicants</head>
  <castItem><role>Aafaa</><actor>Femi Johnson</></>
  <castItem><role>Blindman</><actor>Femi Osofisan</></>
  <castItem><role>Goyi</><actor>Wale Ogunyemi</></>
  <castItem><role>Cripple</><actor>Tunji Oyelana</></>
</castGroup>
<castItem>
  <role>Si Bero</><roleDesc>Sister to Dr Bero</>
  <actor>Deolo Adedoyin</>
</castItem>
<castGroup><head rend=braced>Two old women</head>
  <castItem><role>Iya Agba</><actor>Nguba Agolia</></>
  <castItem><role>Iya Mate</><actor>Bopo George</></>
</castGroup>
<castItem>
  <role>Dr Bero</><roleDesc>Specialist</>
  <actor>Nat Okoro</>
</castItem>
<castItem><role>Priest</><actor>Gbenga Sonuga</></>
<castItem><role>The old man</><roleDesc>Bero's father</>
   <actor>Dapo Adelugba</>
</castItem>
</castList>
<stage>The action takes place in and around the home surgery of
Dr Bero, lately returned from the wars.</stage>]]><!-- W. Soyinka, Madmen and specialists, --></eg></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes names="COMPDRAM INTER DRFRONT"/><dataDesc></dataDesc><elemDecl>- - ((%m.divtop)*, (%component)*,
               (castItem | castGroup)+, (%component)*)</elemDecl><xref target="DRCAST" type="div3"/><xref target="DRFAB" type="div3"/></tagDoc><?tei:EOF castlist.tag ??><!-- castList element --><?tei:SOF catdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	catdesc.tag,v $
# Revision 1.2  94/01/04  12:13:39  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- ******************************************************catDesc --><!-- ******************************************************catDesc --><tagDoc id="CATDESC" usage="opt"><gi tei="yes">catDesc</gi><name>category description</name><desc>describes some category within a taxonomy
or text typology, either in the form of a brief prose description
or in terms of the situational parameters used by the TEI
formal <gi tei="yes">textDesc</gi>.</desc><attList></attList><exemplum><eg><![CDATA[    <catDesc>Prose reportage]]></eg></exemplum><exemplum><eg><![CDATA[<catDesc>
    <textDesc n=novel>
     <channel mode=w>print; part issues
     <constitution type=single>
     <derivation type=original>
     <domain type=art><factuality type=fiction>
     <interaction type=none>
     <preparedness type=prepared>
     <purposes><purpose type=entertain degree=high>
              <purpose type=inform degree=medium>
     </purposes>
    </textDesc>
</catedesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl>- o (%phrase.seq; | textDesc)</elemDecl><xref target="HD55"/></tagDoc><?tei:EOF catdesc.tag ??><!-- catDesc element --><?tei:SOF category.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	category.tag,v $
# Revision 1.2  94/01/04  12:13:39  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *****************************************************category --><tagDoc id="CATEGORY" usage="opt"><gi tei="yes">category</gi><name>category</name><desc>contains an individual descriptive category, possibly nested
within a superordinate category, within a user-defined taxonomy.</desc><attList></attList><exemplum><eg><![CDATA[    <category id=B1><catDesc>Prose reportage</category>]]></eg></exemplum><exemplum><eg><![CDATA[    <category id=B1><catDesc>Prose
    <category id=B11><catDesc>reportage</category>
    <category id=B12><catDesc>fiction</category>
    </category>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl> - - (catDesc, category*)</elemDecl><xref target="HD55"/></tagDoc><?tei:EOF category.tag ??><!-- category element --><?tei:SOF catref.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	catref.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ******************************************************catRef --><tagDoc id="CATREF" usage="opt"><gi tei="yes">catRef</gi><name>category reference</name><desc>specifies one or more defined categories
within some taxonomy or text typology.</desc><attList><attDef usage="req"><attName>target
   </attName><desc>identifies the categories concerned
   </desc><datatype>IDREFS
   </datatype><valDesc>One or more identifiers for <gi tei="yes">category</gi> elements
    defined in the current document.</valDesc><default>#REQUIRED</default></attDef><attDef usage="req"><attName>scheme
   </attName><desc>identifies the classification scheme within which the set of
    categories concerned is defined
   </desc><datatype>IDREF
   </datatype><valDesc>identifier of the associated <gi tei="yes">taxonomy</gi> element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[    <catRef scheme=S1 target="BA C1">]]></eg></exemplum><remarks><p>The scheme attribute need be supplied only if more than
one taxonomy has been declared</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl> - o EMPTY</elemDecl><xref target="HD43"/></tagDoc><?tei:EOF catref.tag ??><!-- catRef element --><?tei:SOF colbr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	colbr.tag,v $
# Revision 1.1  94/01/04  12:13:46  lou
# fix xrefs
#  --><!-- Revisions:                                               --><!-- 25 dec 93: LB clone from pagebr.tag  --><tagDoc id="COLBR" usage="opt"><gi tei="yes">cb</gi><name>column break</name><desc>marks the boundary between one column of a text and the next
in a standard reference system.</desc><attList><attDef usage="rec"><attName>ed</attName><name>edition</name><desc>indicates the edition or version in which the column break is located
at this point</desc><datatype>CDATA</datatype><valDesc>Any string of characters; usually a siglum conventionally used
for the edition.</valDesc><default>#IMPLIED</default><eg><![CDATA[	<cb ed=Riverside n=123>]]></eg></attDef><attDef usage="opt"><attName>n</attName><name>number or name</name><desc>indicates the number or other value associated with the column
which follows the point of insertion of this <gi tei="yes">cb</gi> element.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>Encoders should adopt a clear and consistent policy as to
whether the numbers associated with column breaks relate to the physical
sequence number of the column in the whole text, or whether columns are
numbered within the page. 
By convention, the <gi tei="yes">cb</gi> element is placed at the head of the
column to which it refers.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>Like other forms of milestone tag, <gi tei="yes">cb</gi> tags cannot
be automatically verified by SGML; for better validation, a
concurrent markup stream should be used.</p></remarks><part type="top" name="core"/><classes names="REFSYS"/><elemDecl>- O EMPTY</elemDecl><xref target="CORS5" type="div3"/></tagDoc><?tei:EOF colbr.tag ??><!-- cb element --><?tei:SOF cell.tag ??><!-- Revisions:                                               --><!-- 94-02-28 : MSM : allow end-tag omission                  --><!-- 94-02-28 : MSM : define as paraContent, not phrase.seq   --><!-- 94-02-24 : MSM : full stop after desc                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $Log: --><!-- ************************************************** cell --><tagDoc id="CELL" usage="rwa"><gi tei="yes">cell</gi><desc>contains one cell of a table. </desc><attList><attDef usage="opt"><attName>role</attName><desc>indicates the kind of information held in the cell.</desc><datatype>CDATA</datatype><valList type="semi"><val>label</val><desc>labelling or descriptive information only.</desc><val>data</val><desc>data values.</desc></valList><default>data</default><remarks><p>The value specified overrides any default specified by the
<att tei="yes">role</att> attribute of the parent <gi tei="yes">row</gi> element,
for this cell only.</p></remarks></attDef><attDef usage="opt"><attName>rows</attName><desc>indicates the number of rows occupied by this cell.</desc><datatype>NUMBER</datatype><valDesc>A number; a value greater than one indicates that this cell
spans several rows.</valDesc><default>1</default><remarks><p>Where several cells span several rows, it may be more convenient
to use nested tables.</p></remarks></attDef><attDef usage="opt"><attName>cols</attName><desc>indicates the number of columns occupied by this cell.</desc><datatype>NUMBER</datatype><valDesc>A number; a value greater than one indicates that this cell
spans several columns.</valDesc><default>1</default><remarks><p>Where an initial cell spans an entire row, it should be treated as
a heading.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<row>
  <cell role=label>General conduct</cell>
  <cell role=data>Not satisfactory, on account of his great
       unpunctuality and inattention to duties</cell>
</row>]]></eg></exemplum><remarks><p></p></remarks><part type="top" name="ft"/><classes/><dataDesc></dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="FTTAB1" type="div1"/></tagDoc><?tei:EOF cell.tag ??><!-- cell element --><?tei:SOF certain.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	certain.tag,v $
# Revision 1.5  94/04/07  02:53:52  msmcq
# cosmetic changes only
# 
# Revision 1.4  1994/03/15  11:10:22  lou
# minor typos etc
#
# Revision 1.3  1994/01/04  12:13:40  lou
# fix xrefs
#
# Revision 1.2  1993/09/22  19:03:38  msmcq
# as of publication of CE
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-04-06 : MSM : cosmetics                               --><!-- 12 mar: add to globincl class --><!-- 93-09-17 : MSM : correct examples                        --><!-- 93-06-02 : MSM : revise desc of assertedVal, degree      --><!-- 93-05-27 : MSM : revise for dtd conformance              --><!-- 93-05-27 : MSM : revision received from Allen Renear     --><!-- TEICE2 ********************************** certainty --><tagDoc id="CERTAIN" usage="opt"><gi tei="yes">certainty</gi><desc>indicates the degree of certainty or uncertainty associated with
some aspect of the text markup.
 </desc><attList><!-- ................................ target --><attDef usage="req"><attName>target</attName><desc>points at the elements whose markup is uncertain.</desc><datatype>IDREFS</datatype><valDesc>one or more SGML ID values.</valDesc><default>#REQUIRED</default><eg><![CDATA[Elizabeth went to <persName id=P1>Essex</persName>
<certainty target=P1 locus=gi degree='0.6'>]]></eg><remarks><p>If more than one IDREF is given, the
<gi tei="yes">certainty</gi> element is interpreted as applying to all.
If no ID is present on the element being annotated, the
attribute should give the ID of a <gi tei="yes">ptr</gi> element which
points at the element being annotated; for further discussion
of this indirect pointing mechanism, see chapter <xref target="SA"/>.</p></remarks></attDef><!-- ................................. locus --><attDef usage="req"><attName>locus</attName><desc>indicates the precise location of the uncertainty in the
markup: applicability of the element, precise position of the
start- or end-tag, value of a specific attribute, etc.</desc><datatype>CDATA</datatype><valList type="semi"><val>#gi </val><desc>uncertain whether the element used actually applies
to the passage.</desc><val>#startloc </val><desc>start-tag may not be correctly located.</desc><val>#endloc </val><desc>end-tag may not be correctly located.</desc><val>#location </val><desc>both the start-tag and the end-tag may not
be correctly located.</desc><val>name</val><desc>the value given for the attribute
<att tei="yes">name</att> is uncertain.</desc><val>#transcribedContent </val><desc>the content of the element may
not be a correct transcription of the source text.</desc><val>#suppliedContent </val><desc>the content of the element may not
have been correctly supplied by the reader, e.g. as in the
cases of <gi tei="yes">corr</gi> and <gi tei="yes">abbrev</gi> elements.</desc></valList><default>#REQUIRED</default><remarks><p>The <q>#</q> distinguishes the terms of the
controlled vocabulary from possible collisions with attribute
names.  Extensions to this vocabulary should also use this
prefix.<!-- This is precisely backwards from our conventions elsewhere --><!-- would be better to drop all sharp signs and say *name  (LB) --></p></remarks></attDef><!-- ............................. assertedValue--><attDef usage="rec"><attName>assertedValue</attName><desc>provides an alternative value for the aspect of the markup in
question---an alternative generic identifier, transcription,
or attribute value, or the ID of an <gi tei="yes">anchor</gi> element (to
indicate an alternative starting or ending location).  If an
<att tei="yes">assertedValue</att> is given, the confidence level specified by
<att tei="yes">degree</att> applies to the alternative markup specified by
<att tei="yes">assertedValue</att>; if none is given, it applies to the markup
in the text.</desc><datatype>CDATA</datatype><valDesc>generic identifier, attribute value, location (e.g.
indicated by an IDREF to an <gi tei="yes">anchor</gi> element or to an
<gi tei="yes">xptr</gi> element), or other appropriate alternative
value.</valDesc><default>#IMPLIED</default><eg><![CDATA[Elizabeth went to <persName id=P1>Essex</persName>
<certainty target=P1 locus='#gi'
           assertedValue='place' degree='0.2'>]]></eg><remarks><p>This attribute makes it possible to indicate the
degree of confidence in a specific alternative to some aspect
of the markup. In the example above the encoder is expressing
the likelihood (.2) that the generic identifier should be
<gi tei="yes">place</gi> rather than <gi tei="yes">persName</gi>, which is the coded
element.</p></remarks></attDef><!-- .................................. desc --><attDef usage="rec"><attName>desc</attName><desc>further describes the uncertainty in prose, perhaps
indicating its nature, cause, or the justification for the
degree of confidence asserted.</desc><datatype>CDATA</datatype><valDesc>a prose description of how and why the markup is
uncertain.</valDesc><default>#IMPLIED</default><eg><![CDATA[Elizabeth went to <persName id=P1>Essex</persName>
<certainty target=P1 locus='#gi'  degree='0.2'
desc='As this was written in the Spring
it is probably the Earl, not the town'>]]></eg><remarks><p>In a given project, it may be possible to enumerate
a finite list of recognized types and causes of uncertainty; in
such cases, it will be useful to control the vocabulary used in
this attribute, to aid later mechanical manipulation.  It is
not possible to suggest such a controlled vocabulary for
general use.</p></remarks></attDef><!-- .................................. given --><attDef usage="rec"><attName>given</attName><desc>indicates conditions assumed in the assignment of a
degree of confidence.</desc><datatype>CDATA</datatype><valDesc>a characterization of the conditions which are assumed
in the assignment of a degree of confidence.  This may be in
prose.</valDesc><default>#IMPLIED</default><eg><![CDATA[<!-- in the header, hand 'h1' is
    identified as that of 'msm' ... -->
<hand id=H1 scribe=msm>
 
 <!-- in the text, the scribe has corrected 'Wessex'
     into 'Essex' ... -->
Elizabeth went to <corr id=C1 sic='Wessex' resp=msm>Essex</corr>.
 
<!-- we are 60% certain that hand h1 is 'msm',
     and 90% certain that if h1 is 'msm', then
     it is 'msm' who corrected 'Wessex'
     into 'Essex'.  -->
<certainty id=H1 target=H1 locus=scribe degree='0.6'>
<certainty target=P1 locus=resp given=h1 degree='0.9'>]]></eg><remarks><p>A project may wish to control the vocabulary used
in this attribute.</p><p>The envisioned typical value of this attribute would be the
identifier of another <gi tei="yes">certainty</gi> element or a list of
such identifiers.<!-- this conditional discussion belongs in the chapter, or nowhere -->
It may thus be possible to
construct probability networks by chaining <gi tei="yes">certainty</gi>
elements together.  Such networks would ultimately be grounded
in unconditional <gi tei="yes">certainty</gi> elements (with no value for
<att tei="yes">given</att>).  The semantics of this chaining would be
understood in this way: if a <gi tei="yes">certainty</gi> element is
specified, via an IDREF, as the assumption, then it is not the
attribution of uncertainty that is the assumption, but rather
the assertion itself.  For instance, in the example above,
the first <gi tei="yes">certainty</gi> element indicates that the
confidence in the identification of the new scribe as
<q>msm</q>.  The second indicates the degree of confidence that
<q>Essex</q> is a personal name, given that the new scribe is
<q>msm</q>.  Note that the given in the second <gi tei="yes">certainty</gi>
element is not the assertion that the likelihood that msm is
the new scribe is 0.6, but simply the assertion that msm is the
new scribe; this is a recommended convention to facilitate
building networks.</p><p>The ambitious encoder may wish to attempt complex networks
or probability assertions, experimenting with references to
other elements or prose assertions, and deploying feature
structure connectives such as <gi tei="yes">alt</gi>, <gi tei="yes">join</gi>, and
<gi tei="yes">not</gi>.  However, we do not believe that the
<gi tei="yes">certainty</gi> element gives, at this time, a comprehensive
ambiguity-free system for indicating certainty.<!-- then why are we droning on about it at such length?  (LB)--></p></remarks></attDef><!-- .................................. degree --><attDef usage="opt"><attName>degree</attName><desc>indicates the degree of confidence assigned to the aspect
of the markup named by the <att tei="yes">locus</att> attribute.</desc><datatype>CDATA</datatype><valDesc>Values of <att tei="yes">degree</att> might be yes or no, the
reals between 0 and 1, or traditional characterizations such as
<q>doubtful</q>, <q>circa</q>, etc.  Generally we recommend
decimal numbers between 0 and 1, where  larger  numbers denote
a greater degree of confidence in the assertions; 0
representing <q>certainly false</q> and 1 representing <q>certainly
true</q>.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><p>For discussion of this example, see section <xref target="CECECE"/>.</p><eg><![CDATA[Earnest went to <anchor id=A1> old
<persName id=P1>Saybrook</persName>.
 
<certainty id=C1 target=P1 locus='#gi' degree='0.6'>
<certainty given=c1 target=P1 locus=startloc degree='0.9'>
 
<certainty id=C2 target=P1 locus='#gi'
           assertedValue='persName' degree='0.4'>
<certainty given=c2 target=P1 locus=startloc degree='0.5'>
<certainty id=C3
           given=c1 target=P1 locus=startloc
           assertedValue='a1' degree='0.5' >]]></eg></exemplum><part type="top" name="ce"/><classes names="METADATA"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="CECECE"/></tagDoc><?tei:EOF certain.tag ??><!-- certainty element --><?tei:SOF change.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	change.tag,v $
# Revision 1.2  94/01/04  13:13:39  lou
# resp->respStmt
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-01 : MSM : change model post Eynsham               --><!-- 92-08-19 : MSM : delete empty name element               --><!-- *******************************************************change --><tagDoc id="CHANGE" usage="opt"><gi tei="yes">change</gi><desc>summarizes a particular change or correction made
to a particular version of an electronic text which is
shared between several researchers.</desc><attList></attList><exemplum><eg><![CDATA[<change n="P2.2">
   <date>21 Dec 91 <respStmt><name>LB</><resp>ed.</></respStmt>
   <item>Added examples to section 3</>
</change>
<change>
   <date>11 Nov 91 <respStmt><name>LB</><resp>ed.</></respStmt>
   <item>Deleted chapter 10</>
</change>]]></eg></exemplum><remarks><p>Changes should be recorded in a consistent order, for
example with the most recent first.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- O (date, respStmt+, item)</elemDecl><xref target="HD6"/></tagDoc><?tei:EOF change.tag ??><!-- change element --><?tei:SOF channel.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	channel.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : change ids to begin CCah not AH         --><!-- ************************************************************** channel --><tagDoc id="CHANNEL" usage="opt"><gi tei="yes">channel</gi><name>primary channel</name><desc>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.</desc><attList><attDef usage="opt"><attName>mode
   </attName><desc>specifies the mode of this channel with respect to speech and
         writing.
   </desc><datatype>(s | w | ws | sw | m | x)
   </datatype><valList type="closed"><val>s</val><desc>spoken
   </desc><val>w</val><desc>written
   </desc><val>sw</val><desc>spoken to be written (e.g. dictation)
   </desc><val>ws</val><desc>written to be spoken (e.g. a script)
   </desc><val>m</val><desc>mixed modes
   </desc><val>x</val><desc>unknown or inapplicable
   </desc></valList><default>x</default></attDef></attList><exemplum><eg><![CDATA[   <channel mode=s>face-to-face conversation]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF channel.tag ??><!-- channel element --><?tei:SOF wsdchar.tag ??><!-- Revisions:                                               --><!-- 93-09-20 : MSM : correct datatype of class               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdchar.tag,v $
# Revision 1.3  93/09/22  19:27:31  msmcq
# changes as of publication of WD
# 
# Revision 1.2  1993/09/17  17:00:15  lou
# changed descs for consistency
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ********************************************** character --><tagDoc id="WSDCHAR" usage="opt"><gi tei="yes">character</gi><desc>defines one unit in a writing system, supplementing or overriding
information provided in the base coded character sets, writing system
declarations, and entity sets.</desc><attList><!-- .................................................. class --><attDef usage="req"><attName>class</attName><desc>describes the function of the character using a prescribed
classification.</desc><datatype>(lexical | punc | lexpunc | digit
| space | DL | LD | dia | joiner | other)</datatype><valList type="closed"><val>lexical </val><desc>character is used in writing words (lexical items) of
the language (includes members of syllabaries and ideographic systems,
as well as composite letter-plus-diacritic combinations)</desc><val>punc    </val><desc>character is a punctuation mark which does not appear
within lexical items</desc><val>lexpunc </val><desc>character can appear as a normal punctuation
mark, but can also appear within a lexical item (and should usually,
when occurring between two lexical characters, be treated as
lexical---in English, hyphen and apostrophe are typically treated as
members of this class)</desc><val>digit   </val><desc>character is
an Arabic decimal numeral (0, 1, ... 9) (does not
include superscript numbers, circled numbers, numeric dingbats, etc.)</desc><val>space   </val><desc>character represents  some form of white space
(space character, horizontal or vertical tab, newline, etc.)</desc><val>dl      </val><desc>character is a diacritic applying to the following
lexical character</desc><val>ld      </val><desc>character is a diacritic applying to the preceding
lexical character</desc><val>dia     </val><desc>character is a diacritic which is explicitly joined to
a lexical character by a joiner character</desc><val>joiner  </val><desc>character is used to join a diacritic to the lexical
character to which it applies (in some encoding schemes, the
backspace  control character may be used as a joiner; in others, a
graphic character is used for the same function)</desc><val>other   </val><desc>character does not fall into any of the other classes
(dingbats and other unusual characters fall here)</desc></valList><default>lexical</default><eg><![CDATA[ ]]></eg><remarks><p>The classification of characters provided by this
attribute serves both informative and normative purposes:  it helps
identify the character being described, and the classification is used
to define the meaning of the special character-class codes in the TEI
extended pointer syntax described in chapter <xref target="SA"/>.
 </p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The notion of <soCalled>characters</soCalled> as units in a
writing system is widely spread, but not consistently defined; the
<gi tei="yes">character</gi> element should be used to identify whatever units the
encoder wishes to distinguish as the meaningfully distinct graphic units
of the writing system.  In most cases, these will correspond to the
units of coded character sets, but that this is not a requirement:
a-umlaut, for example, may be treated as one character or two, depending
on the user's preference, regardless of how the coded character set in
use treats it.  In most cases, also, the units distinguished by the
<gi tei="yes">character</gi> element will be the <soCalled>graphemic</soCalled>
units of the writing system in question; however, since experts disagree
on whether items like umlaut (let alone a given set of Chinese
characters with regional variations in China, Korea, and Japan) are best
treated as distinct graphemes or not, the association of
<gi tei="yes">character</gi> elements with the graphemes of a writing system
provides at most a heuristic device for making reasonable decisions,
rather than a definitive unambiguous test.
 </p><p>Different forms of the same <soCalled>character</soCalled> may be
distinguished for whatever reason, as in the three-R example of chapter<xref target="CH"/>
.  In this case the different letter forms are
distinguished by documenting them in different <gi tei="yes">form</gi> elements;
the fact that the different letter shapes do not make a lexical
difference in the text may be expressed by grouping all three letter
forms under the same <gi tei="yes">character</gi> element.  (Alternatively, the
three forms may be treated as three distinct characters, for convenience
or for whatever reason, by defining a distinct <gi tei="yes">character</gi>
element for each.)
 </p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain one or more description elements (optional), a
series of one or more <gi tei="yes">form</gi> elements identifying different forms
of the character, and an optional series of notes.</dataDesc><elemDecl>- O  (desc*, form+, note*)</elemDecl><xref target="WDCSEX"/></tagDoc><?tei:EOF wsdchar.tag ??><!-- character element --><?tei:SOF wsdchars.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdchars.tag,v $
# Revision 1.2  94/01/04  12:15:44  lou
# fix xrefs
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ********************************************* characters --><tagDoc id="WSDCHARS" usage="req"><gi tei="yes">characters</gi><desc>contains a specification of the characters used in a particular
writing system to write a particular language, and of how those
characters are represented in electronic form.</desc><attList></attList><exemplum><eg><![CDATA[<eclaration
    name='-//TEI P2: 1993//WSD ISO 8859-1//en'
    date='1993-06-01'>
    <language iso639=''>various</>
    <direction chars=LR lines=TB>
    <characters>
         < name='ISO 8859-1: 1992' authority='ISO'>
         <exceptions>
              <!-- ... -->
         </exceptions>
    </characters>
</eclaration>
 ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain a series of base components (coded character sets,
writing system declarations, and entity sets) followed by a set of
exceptions to define differences from the base components.</dataDesc><elemDecl>- O  (codedCharSet*, baseWsd*, entitySet*, exceptions?)</elemDecl><xref target="WDCSBA"/><xref target="WDOV"/></tagDoc><?tei:EOF wsdchars.tag ??><!-- characters element --><?tei:SOF children.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : change dataDesc                         --><!-- 93-09-11 : MSM : uppercase omissibility sign             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	children.tag,v $
# Revision 1.3  93/09/16  15:04:39  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:49:48  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** children --><tagDoc id="CHILDREN" usage="req"><gi tei="yes">children</gi><desc>lists the elements which this element may directly contain.</desc><attList></attList><exemplum><eg><![CDATA[   <children>emph, hi, name, address, #PCDATA]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>the list may contain a description or a list of names
separated by commas or spaces.</dataDesc><elemDecl> - O (#PCDATA)</elemDecl><xref target="TDTAG"/></tagDoc><?tei:EOF children.tag ??><!-- children element --><?tei:SOF cit.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cit.tag,v $
# Revision 1.5  94/03/01  04:06:39  msmcq
# replace reference to m.pointer with ref to m.loc
# 
# Revision 1.4  1994/01/15  21:06:26  msmcq
# revisions in connection with DI, for P3.
#
# Revision 1.3  1994/01/04  13:15:23  lou
# change class membership (was divtop), add pointer
#
# Revision 1.2  1993/08/03  01:41:55  msmcq
# correct content model error
# --><!-- Revisions:                                               --><!-- 94-02-28 : MSM : replace m.pointer with m.loc            --><!-- 94-01-15 : MSM : add xref to ditpeg                      --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct reference to m.bibl             --><!-- ***************************************************cit --><tagDoc id="CIT" usage="opt"><gi tei="yes">cit</gi><desc>A quotation from some other document, together with a bibliographic
reference to its source.</desc><attList></attList><exemplum><eg><![CDATA[<cit>
<quote>and the breath of the whale is frequently
attended with such an insupportable smell, as to
bring on disorder of the brain.
</quote>
<bibl>Ulloa's South America</bibl>
</cit>]]></eg></exemplum><!-- Moby Dick, p 5 --><remarks></remarks><part type="base" name="core"/><classes names="HQINTER"/><dataDesc>Must contain a single quote and a single bibliographic
reference in either order</dataDesc><elemDecl>- - ((q | quote) &amp; (%m.bibl; | %m.loc;))</elemDecl><xref target="COHQQ"/><xref target="DSGRP"/><xref target="DITPEG"/></tagDoc><?tei:EOF cit.tag ??><!-- cit element --><?tei:SOF cl.tag ??><!-- ***************************************************** cl --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: cl.tag,v $
    * Revision 1.3  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.2  94/02/27  15:55:52  lou
    * Revisions for publication of AI
    * 
    * Revision 1.1  1993/09/23  02:36:34  msmcq
    * Unpacked TDL changes July 93
    * --><!-- Revisions:                                               --><!-- 93-09-22 : MSM : change id of seg class to clseg         --><!-- 93-07-22 : DTL : use as model for SEG, CL and PHR tags   --><!--                add sample values for type= and function= --><!-- 29 may 93: LB created C tag from old S tag               --><!--                                                          --><!-- ***************************************************** cl --><tagDoc id="CL" usage="opt"><gi tei="yes">cl</gi><name>clause</name><desc>represents a grammatical clause.</desc><attList></attList><exemplum><eg><![CDATA[<cl type=relative function='clause modifier'>
Which frightened both the heroes so,
<cl>They quite forgot their quarrel.</cl></cl>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLSEG"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq)</elemDecl><xref target="AILC"/></tagDoc><?tei:EOF cl.tag ??><!-- cl element --><?tei:SOF class.tag ??><!-- Revisions:                                               --><!-- 93-09-11 : MSM : complete example                        --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	class.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/08  23:39:56  msmcq
# revise desc
#
# Revision 1.2  1993/08/13  20:49:49  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** class --><tagDoc id="CLASS" usage="mwa"><gi tei="yes">class</gi><desc>specifies the name of an element class.</desc><attList></attList><exemplum><eg><![CDATA[<classDoc>
 <class>phrase</class>
 <!-- ... -->
</classDoc>]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>In TEI compatible encoding systems, the class name should be
chosen so that a valid SGML name may be made from it. For attribute
classes, this name is made by prefixing the class name with the string
<q>a.</q>; for model classes, the string <q>m.</q> is used.</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><xref target="TDCLA"/></tagDoc><?tei:EOF class.tag ??><!-- class element --><?tei:SOF classcod.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	classcod.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- ***************************************************classCode --><tagDoc id="CLASSCOD" usage="opt"><gi tei="yes">classCode</gi><name>classCode</name><desc>contains the classification code used for this text in some
standard classification system.</desc><attList><attDef usage="req"><attName>scheme</attName><desc>identifies the classification system or taxonomy in use.</desc><datatype>IDREF</datatype><valDesc>must identify a <gi tei="yes">taxonomy</gi> element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[    <classCode scheme=DDC12>410]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl> - - (%phrase.seq)</elemDecl><xref target="HD43"/></tagDoc><?tei:EOF classcod.tag ??><!-- classCode element --><?tei:SOF clasdecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	clasdecl.tag,v $
# Revision 1.2  94/01/04  12:13:41  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************************classDecl --><tagDoc id="CLASDECL" usage="opt"><gi tei="yes">classDecl</gi><name>classification declarations</name><desc>contains one or more taxonomies defining any classificatory
codes used elsewhere in the text.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl> - - (taxonomy+)</elemDecl><xref target="HD55"/><xref target="HD5"/></tagDoc><?tei:EOF clasdecl.tag ??><!-- classDecl element --><?tei:SOF classdoc.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : allow files element                     --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-09-10 : MSM : ptr* not ptr+                           --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	classdoc.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/04/08  01:52:06  msmcq
    * Last fixes for FD in P3, etc.
    *
    * Revision 1.4  1994/01/04  12:13:43  lou
    * fix xrefs
    *
    * Revision 1.3  1993/09/15  22:56:03  msmcq
    * Changes as of mid-September
    *
    * Revision 1.2  1993/09/08  23:40:12  msmcq
    * cosmetic, remove tabs from elemDecl
    *
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- 4 Jan 98: LB : revised wording of desc slightly --><!-- *************************************************** classDoc --><tagDoc id="CLASSDOC" usage="rwa"><gi tei="yes">classDoc</gi><desc>contains reference information for a TEI <term>element class</term>; 
that is a group of 
  elements which appear together in SGML content models, or 
  which share some common attribute, or both.</desc><attList><attDef usage="req"><attName>type</attName><desc>indicates whether this is a model class, an attribute class,
  or both.</desc><datatype>(model | atts | both)</datatype><valList type="open"><val>model</val><desc>members of this class appear in the same SGML content models</desc><val>atts</val><desc>members of this class share common attributes</desc><val>both</val><desc>members of this class share attributes and also 
appear in the same
  SGML content models</desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[ <classDoc type=model id=SEG>
<class>seg</class>
<desc>elements for arbitrary segmentation.</desc>
<ptr target=COSE>
</classDoc>]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl>- O (class, rs?, desc, attList?, remarks?, part?,
classes?, files?, ptr*, equiv*) </elemDecl><xref target="TDCLA"/><xref target="TD"/></tagDoc><?tei:EOF classdoc.tag ??><!-- classDoc element --><?tei:SOF classes.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : allow content                           --><!-- 94-03-21 : MSM : supply explicit end-tags for attdef components --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : revise desc                             --><!-- 93-09-11 : MSM : change NAMES attribute to CDATA         --><!-- 93-09-11 : MSM : change attDef on NAMES                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	classes.tag,v $
# Revision 1.6  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.5  1994/03/25  17:21:51  msmcq
# cleanup of miscellaneous tagdocs:  some typos,
# some INHERITED errors, supplied explicit end-tags for many attdef parts
# to shield a weakness of oddref1 (now fixed)
#
# Revision 1.4  1994/01/04  12:13:44  lou
# fix xrefs
#
# Revision 1.3  1993/09/16  15:04:39  msmcq
# Publication of TD
#
# Revision 1.2  1993/08/13  20:49:50  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** classes --><tagDoc id="CLASSES" usage="rwa"><gi tei="yes">classes</gi><desc>specifies all the classes of which the documented element or
class is a member or subclass.</desc><attList><attDef usage="opt"><!-- odd has implied but makes element compulsory (lb)       --><!-- Odd is using IDREFS not CDATA, and has to make this     --><!-- attribute IMPLIED, because the empty string is not a    --><!-- legal IDREFS value.  Changed data type to CDATA to      --><!-- allow full class names, not IDs, and to allow empty     --><!-- string as legal value. (msm)                            --><attName>names</attName><desc>lists the identifiers of all classes of which the documented
 element or class is a member or subclass, possibly using parentheses to
 indicate inheritance.
 </desc><datatype>CDATA</datatype><!-- changed from IDREFS to CDATA (msm)                      --><valDesc>a list of class names separated by spaces or commas, and
 optionally enclosed by parentheses; each name should be the class name
 specified for some element class in the scheme being documented or
 modified.
 </valDesc><default>#REQUIRED</default></attDef></attList><exemplum><eg><![CDATA[<classes names="HQINTER (INTER (COMMON))">hqinter
[and indirectly also:] common, inter</classes>]]></eg><p>This <gi tei="yes">classes</gi> element indicates that the element documented
is a member of the class <ident tei="yes" type="class">hqinter</ident>, which is
itself a subclass of the classes
<ident tei="yes" type="class">inter</ident> and thus also of
<ident tei="yes" type="class">common</ident>.  The value of the <att tei="yes">names</att>
attribute and the content are synonymous, two ways of representing the
same information.</p></exemplum><exemplum><eg><![CDATA[   <classes names="HQINTER">hqinter</classes>]]></eg><p>This <gi tei="yes">classes</gi> element indicates that the element documented
is a member of the class <ident tei="yes" type="class">hqinter</ident>, but gives no
indication that
<ident tei="yes" type="class">hqinter</ident> is itself a subclass of <ident tei="yes" type="class">phrase</ident>.</p></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>Empty</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><xref target="TDTAG"/><xref target="TDCLA"/></tagDoc><?tei:EOF classes.tag ??><!-- classes element --><?tei:SOF closer.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: closer.tag,v $
    * Revision 1.5  1999/02/22 15:41:37  tei
    * Comments sorted
    *
 Revision 1.4  1998/03/11 18:53:55  tei
 correcting egs

 Revision 1.3  1994/03/15 11:10:23  lou
 minor typos etc
    *--><!--
# Revision 1.2  1994/01/04  12:13:45  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *******************************************************closer --><tagDoc id="CLOSER" usage="opt"><gi tei="yes">closer</gi><desc>groups together dateline, byline, salutation, and similar
phrases appearing as a final group at the end of a
division, especially of a letter.</desc><attList></attList><exemplum><eg><![CDATA[<div type=letter><p>
<!-- ... -->
perhaps you will favour me with a sight
 of it when convenient.</p>
 <closer><salute>I remain, &amp;c. &amp;c.</salute>
  <signed>H. Colburn</signed>
 </closer>
 </div>]]></eg></exemplum><exemplum><eg><![CDATA[<div type=chapter><p>
<!-- ... -->
and his heart was going like mad and yes
 I said yes I will Yes.</p>
 <closer>
  <dateline>
    <name type=place>Trieste-Z&uuml;rich-Paris,</name>
    <date>1914-1921</date>
  </dateline>
 </closer></div>]]></eg><!-- James Joyce, Ulysses --></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVBOT"/><elemDecl>- O (signed | dateline | salute | %phrase.seq;)* </elemDecl><xref target="DSCO"/><xref target="DSDTB"/></tagDoc><?tei:EOF closer.tag ??><!-- closer element --><?tei:SOF wsdccs.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdccs.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ******************************************* codedCharSet --><tagDoc id="WSDCCS" usage="opt"><gi tei="yes">et</gi><name>base coded character set</name><desc>identifies a public or private coded character set which is used
as a basic component of a writing system declaration.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Reference to a coded character set makes the set
of bit-pattern-to-character mappings defined in the coded character set
available for use in text encoded with the writing system declaration.
Unless the character inventory and mappings are modified by the
<gi tei="yes">exceptions</gi> element, any character in any base coded character
set may be used with its standard meaning within text to which the
writing system declaration applies.</p><p>In order to make the mappings of bit patterns to characters more
explicit than they sometimes are in character-set standards, the TEI
will provide standard writing system declarations which document the
bit-pattern-to-character mappings defined by various commonly used coded
character sets.</p></remarks><part type="aux" name="wsd"/><classes names="BASESTD"/><dataDesc>An empty element.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="WDCSBA"/></tagDoc><?tei:EOF wsdccs.tag ??><!-- codedCharSet element --><?tei:SOF plcol.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	plcol.tag,v $
# Revision 1.2  94/02/17  21:02:12  msmcq
# drop dot
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-02-15 : MSM : drop dot in id                          --><!-- 93-06-05 : MSM : new xref                                --><!-- ******************************************************* plcol --><tagDoc id="PLCOL" usage="opt"><gi tei="yes">col</gi><name>column</name><desc>contains one column of a multi-column reference edition.</desc><attList></attList><exemplum><eg><![CDATA[    <(La)page n=32>
    <(La)col n=a> ...
    <(La)col n=b> ...
    <(La)page n=33> ...]]></eg></exemplum><remarks><p>The <gi tei="yes">col</gi> tag should be used wherever a standard
reference scheme uses references to individual columns of a reference
edition; otherwise it need not be used.</p></remarks><part type="base" name="print"/><classes/><dataDesc>May contain <gi tei="yes">line</gi> elements, or character data.</dataDesc><elemDecl>- O  (#PCDATA | line)*</elemDecl><xref target="NHRS" type="div3"/></tagDoc><?tei:EOF plcol.tag ??><!-- col tag (in PL tag set) --><?tei:SOF colloc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	colloc.tag,v $
# Revision 1.3  94/02/12  18:12:57  msmcq
# cosmetic (remove duplicate RCS keywords)
# 
# Revision 1.2  1994/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************* colloc --><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-13 : MSM : add to class gramInfo                   --><!-- ************************************************* colloc --><tagDoc id="COLLOC" usage="opt"><gi tei="yes">colloc</gi><name>collocate</name><desc>contains a collocate of the headword.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the collocation, using any convenient typology.</desc><datatype>CDATA</datatype><valDesc>any string of characters, e.g. <q>preposition</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DIPARTS GRAMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPGR"/></tagDoc><?tei:EOF colloc.tag ??><!-- colloc element --><?tei:SOF cond.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : replace fs.family with literal          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	cond.tag,v $
# Revision 1.2  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY cond system     'cond.tag' --><!-- cond tag --><!-- *************************************************** cond --><tagDoc id="COND" usage="opt"><gi tei="yes">cond</gi><name>conditional feature-structure constraint</name><desc>defines a conditional feature-structure constraint; the consequent
and the antecedent are specified as feature structures or
feature-structure groups; the constraint is satisfied if both the
antecedent and the consequent <term>subsume</term> a given feature
structure, or if the antecedent does not.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain an antecedent feature structure, an empty
<gi tei="yes">then</gi> element, and a consequent feature structure.</dataDesc><elemDecl>- O  ((fs | f | fAlt), then, (fs | f | fAlt))</elemDecl><xref target="FD"/></tagDoc><?tei:EOF cond.tag ??><!-- cond element --><?tei:SOF constitn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	constitn.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- 93-03-10 : MSM : in desc, say text OR SAMPLE             --><!-- ****************************************************** constitn --><tagDoc id="CONSTITN" usage="opt"><gi tei="yes">constitution</gi><desc>describes the internal composition of a text or text sample,
for example
as fragmentary, complete, etc.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>specifies how the text was constituted.
   </desc><datatype>(single | composite | frags | unknown)
   </datatype><valList type="closed"><val>single</val><desc>a single complete text
    </desc><val>composite</val><desc>a text made by combining several smaller
             items, each individually complete
    </desc><val>frags</val><desc>a text made by combining several smaller, not
             necessarily complete, items
    </desc><val>unknown</val><desc>composition unknown or unspecified
   </desc></valList><default>single</default></attDef></attList><exemplum><eg><![CDATA[    <constitution type=frags>Prologues only.]]></eg></exemplum><remarks><p>The function of this element seems to overlap with both
the ORG attribute on DIVs and the samplingDecl in the encodingDesc.</p></remarks><part type="aux" name="corpora"/><classes/><dataDesc>contains any sequence of phrase level data</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF constitn.tag ??><!-- constitution element --><?tei:SOF corr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	corr.tag,v $
# Revision 1.5  94/03/28  19:59:41  msmcq
# punctuations, tyops (i don't know)
# 
# Revision 1.4  1994/03/08  03:24:27  msmcq
# revision for P3
#
# Revision 1.3  1994/02/07  20:56:16  msmcq
# revisions for P3
#
# Revision 1.2  1993/08/03  01:47:19  msmcq
# correct INHERITED keyword
# --><!-- Revisions:                                               --><!-- 94-03-07 : MSM : add note to RESP attribute              --><!-- 94-02-04 : MSM : suppress irrelevant EXPAN example       --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct INHERITED                       --><!-- 92-12-09 : LB : really correct garbled eg element        --><!-- 92-12-07 : MSM : fix problem at end of EG                --><!-- 92-12-07 : MSM : correct garbled eg element              --><!-- 92-12-07 : MSM : change model to specialPara             --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- 92-11-09 : MSM : change id ref                           --><!-- ******************************************************** corr --><tagDoc id="CORR" usage="opt"><gi tei="yes">corr</gi><name>correction</name><desc>contains the correct form of a passage apparently erroneous in
the
copy text.</desc><attList><attDef usage="opt"><attName>sic</attName><desc>gives the original form of the apparent error in the copy text.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[  for his nose was as sharp as a pen, and
  <corr sic="a Table"> a' babbled</corr>
  of green fields.]]></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>signifies the editor or transcriber responsible for suggesting
the correction held as the content of the <gi tei="yes">corr</gi> element.</desc><datatype>CDATA</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing, or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg><remarks><p>If the correction was made in the source, this attribute
should be used to identify the hand of the corrector.</p></remarks></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the correction
held as the content of the <gi tei="yes">corr</gi> element.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><p>If all that is desired is to call attention to the
fact that the copy text has been corrected, no attributes are
required:</p><eg><![CDATA[I don't know, Juan.  It's so far in the past now &mdash;
how <corr>can we</corr> prove or disprove anyone's theories?]]></eg></exemplum><exemplum><p>It is also possible to provide a correct reading and to
identify
the individual responsible for the correction:</p><eg><![CDATA[I don't know, Juan.  It's so far in the past now &mdash;
how <corr sic='we can' resp='MSM'>can we</corr> prove or
disprove anyone's theories?]]></eg></exemplum><remarks><p>The <gi tei="yes">corr</gi> tag is a mirror of <gi tei="yes">sic</gi>:  the
latter leaves the original text untouched, giving the correction as
an
attribute value; the former substitutes the correction, leaving the
original reading as an attribute value.  The choice between them is
up
to the encoder.</p></remarks><part type="top" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%specialPara;)</elemDecl><xref target="COEDCOR" type="div3"/></tagDoc><?tei:EOF corr.tag ??><!-- corr element --><?tei:SOF correctn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	correctn.tag,v $
# Revision 1.2  94/01/04  12:14:01  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-03-11 : MSM : specify type on vallist                 --><!-- 93-03-08 : MSM : re-synchronize Oxf and Chi copies       --><!-- 93-02-10 : MSM : update xref targets                     --><!-- ***************************************************correction --><tagDoc id="CORRECTN" usage="opt"><gi tei="yes">correction</gi><name>correction principles</name><desc>states how and under what circumstances corrections have been
made in the text.</desc><attList><attDef usage="opt"><attName>status
   </attName><desc>indicates the degree of correction applied to the text.
   </desc><datatype>(high | medium | low | unknown)
   </datatype><valList type="closed"><val>high    </val><desc>the text has been thoroughly checked and
                       proofread.
    </desc><val>medium  </val><desc>the text has been checked at least once.
    </desc><val>low     </val><desc>the text has not been checked.
    </desc><val>unknown </val><desc>the correction status of the text is unknown.
   </desc></valList><default>unknown</default></attDef><attDef usage="opt"><attName>method
   </attName><desc>indicates the method adopted to indicate corrections within the
         text.
   </desc><datatype>(silent | tags)
   </datatype><valList type="closed"><val>silent</val><desc>corrections have been made silently
    </desc><val>tags</val><desc>corrections have been represented using editorial tags
   </desc></valList><default>silent</default></attDef></attList><exemplum><eg><![CDATA[<correction><p>Errors in transcription controlled by using the
WordPerfect spelling checker, with a user defined dictionary of 500
extra words taken from Chambers Twentieth Century Dictionary.]]></eg></exemplum><remarks><p>May be used to note the results of proof reading the
text against its original, indicating (for example) whether
discrepancies have been silently rectified, or recorded using the
editorial tags described in section <xref target="COED"/>.</p></remarks><!-- was:  target='P2.47' --><!-- was:  target=COEDIT --><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/><xref target="CCAS2"/></tagDoc><!-- end of CORRECTION --><?tei:EOF correctn.tag ??><!-- correction element --><?tei:SOF country.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	country.tag,v $
# Revision 1.2  94/03/07  16:16:55  lou
# revised version of ND
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-03 : MSM : class is named plname not plnames       --><!-- 93-05-28 : MSM : revise, merge with older text           --><!-- 92-11-09 : MSM : fix xref to CObi                        --><!-- *****************************************************country --><tagDoc id="COUNTRY" usage="opt"><gi tei="yes">country</gi><name>country</name><desc>in an address, gives the name of the nation, country, colony, or
commonwealth; in a place name given as a hierarchy of geo-political
units, the <gi tei="yes">country</gi> is larger or administratively superior
to the <gi tei="yes">region</gi> and smaller than the <gi tei="yes">bloc</gi>.</desc><attList></attList><exemplum><eg><![CDATA[   <country n=DK>Denmark</>]]></eg></exemplum><remarks><p>If attributes are used to identify the country referred to
(as the <att tei="yes">n</att> is used above), the values should be
taken from recognized lists of abbreviations, e.g. ISO 3166. </p></remarks><part type="base" name="core"/><classes names="PLACPART"/><elemDecl>- o (%paraContent)</elemDecl><!-- xref target=COBI --><xref target="NDPLAC"/></tagDoc><?tei:EOF country.tag ??><!-- country element --><?tei:SOF creatn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	creatn.tag,v $
# Revision 1.2  94/01/04  12:14:02  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- *****************************************************creation --><tagDoc id="CREATN" usage="opt"><gi tei="yes">creation</gi><desc>contains information about the creation of a text.</desc><attList></attList><exemplum><eg><![CDATA[<creation><date>Before 1987</date>
<creation><date value='1988-07-10'>10 July 1988</date>]]></eg></exemplum><remarks><p>The <gi tei="yes">creation</gi> element may be used to record details
of a text's creation, e.g. the date and place it was composed, if these
are of interest; it should not be confused with the
<gi tei="yes">publicationStmt</gi> element, which records date and place of
publication.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc>Character data and phrase-level elements.</dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="HD4C"/><xref target="HD4"/></tagDoc><!-- end of CREATION --><?tei:EOF creatn.tag ??><!-- creation element --><?tei:SOF damage.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: damage.tag,v $
    * Revision 1.6  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.5  94/08/29  15:20:05  msmcq
    * fixes for unreachability
    * (divGen et al.)
    * 
    * Revision 1.4  1994/04/08  01:52:06  msmcq
    * Last fixes for FD in P3, etc.
    * 
    * Revision 1.3  1994/03/25  17:21:51  msmcq
    * cleanup of miscellaneous tagdocs:  some typos,
    * some INHERITED errors, supplied explicit end-tags for many attdef parts
    * to shield a weakness of oddref1 (now fixed)
    * 
    * Revision 1.2  1994/02/07  20:56:16  msmcq
    * revisions for P3
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    * --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- 94-04-07 : MSM : full stop after etc                     --><!-- 94-03-21 : MSM : correct 'inherited' error               --><!-- 94-02-04 : MSM : correct desc on degree att              --><!-- ENTITY damage   system 'damage.tag' --><!-- damage tag --><!-- ************************************************* damage --><tagDoc id="DAMAGE" usage="opt"><gi tei="yes">damage</gi><desc>contains an area of damage to the text witness.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the damage according to any convenient typology.</desc><datatype>CDATA</datatype><valDesc>any phrase describing the damage, e.g. <q>faded</q>,
<q>overbound</q>, <q>water</q>, <q>charred with loss of paper</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................. extent --><!-- was: length.  Necessary where damage tag has no content  --><attDef usage="opt"><attName>extent</attName><desc>indicates approximately how much text is in the damaged area,
in letters, minims, inches, or any appropriate unit, where this
cannot be deduced from the contents of the tag.  For example, the
damage may span structural divisions in the text so that the tag must
then be empty of content.</desc><datatype>CDATA</datatype><valDesc>any measurement phrase, e.g. <q>25 letters</q>, <q>2 x 3
inches</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><desc>indicates the individual responsible for identifying the area
of damage.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>In the case of damage (deliberate defacement, etc.) assignable
to an identifiable hand, signifies the hand responsible for the
damage.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... agent --><attDef usage="opt"><attName>agent</attName><desc>In the case of damage resulting from an identifiable cause,
signifies the causative agent.</desc><datatype>CDATA</datatype><valDesc>any prose description of the agency of damage.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... degree --><!-- The Robin Cover memorial attribute........................ --><attDef usage="opt"><attName>degree</attName><desc>Signifies the degree of damage according to a convenient scale.
The <gi tei="yes">damage</gi> tag with the <att tei="yes">degree</att> attribute should
only be used where the text may be read with some confidence; text
supplied from other sources should be tagged as <gi tei="yes">supplied</gi>.</desc><datatype>CDATA</datatype><valDesc>an alphanumeric categorization of the degree of damage, as
<q>40%</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The <gi tei="yes">damage</gi> tag with the <att tei="yes">degree</att>
attribute should only be used where the text may be read with
confidence despite the damage.  It is appropriate where it is desired
to record the fact of damage, though this has not affected the
readability of the text (as may be the case with weathered
inscriptional materials).  Where the damage has rendered the text
more or less illegible either the <gi tei="yes">unclear</gi> tag (for partial
illegibility) or the <gi tei="yes">omit</gi> tag (for complete illegibility,
with no text supplied) should be used, with the information
concerning the damage given in the attribute values of these tags.
See section <xref target="PHCOMB"/> for discussion of the use of these
tags in particular circumstances.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Since damage to text witnesses frequently makes them
harder to read, the <gi tei="yes">damage</gi> element will often contain an
<gi tei="yes">unclear</gi> element.  If the damaged area is not continuous in
the text (e.g. a stain on one side of a page), the <gi tei="yes">join</gi>
element may be used to indicate which <gi tei="yes">damage</gi> and
<gi tei="yes">unclear</gi> elements are part of the same physical phenomenon.</p><p>The <gi tei="yes">damage</gi>, <gi tei="yes">omit</gi>, <gi tei="yes">del</gi>, <gi tei="yes">unclear</gi>
and <gi tei="yes">supplied</gi> elements may be closely allied in use.  See
section <xref target="PHCOMB"/> for discussion of which element is
appropriate for which circumstance.</p></remarks><part type="top" name="tc"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="PHDA"/></tagDoc><?tei:EOF damage.tag ??><!-- damage element --><?tei:SOF datadesc.tag ??><!-- Revisions:                                               --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	datadesc.tag,v $
# Revision 1.5  94/01/04  12:14:02  lou
# fix xrefs
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/08  23:40:42  msmcq
# minor revisions for clarity.
#
# Revision 1.2  1993/08/13  20:49:50  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** dataDesc --><tagDoc id="DATADESC" usage="opt"><gi tei="yes">dataDesc</gi><desc>specifies the legal content of the element being documented,
noting any semantic or application-dependent constraints, as well
as constraints enforced by the SGML content model.</desc><attList></attList><exemplum><eg><![CDATA[<dataDesc>A declarative sentence, an adjectival phrase, or the word EMPTY.]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>A declarative sentence, an adjectival phrase, or the word EMPTY.</dataDesc><elemDecl>- O (%phrase.seq)</elemDecl><xref target="TDTAG"/></tagDoc><?tei:EOF datadesc.tag ??><!-- dataDesc element --><?tei:SOF datatype.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility O                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	datatype.tag,v $
# Revision 1.3  93/09/16  15:07:52  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:49:51  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** datatype --><tagDoc id="DATATYPE" usage="req"><gi tei="yes">datatype</gi><desc>specifies an SGML <term>declared value</term> for an attribute.</desc><attList></attList><exemplum><eg><![CDATA[  <datatype>CDATA]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>must be a legal SGML keyword, notation name or a name token group.</dataDesc><elemDecl> - O (#PCDATA)</elemDecl><xref target="TDATT"/></tagDoc><?tei:EOF datatype.tag ??><!-- dataType element --><?tei:SOF date.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	date.tag,v $
# Revision 1.6  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.5  1994/03/25  17:21:51  msmcq
# cleanup of miscellaneous tagdocs:  some typos,
# some INHERITED errors, supplied explicit end-tags for many attdef parts
# to shield a weakness of oddref1 (now fixed)
#
# Revision 1.4  1994/03/07  16:16:31  lou
# revised for initial check in of ND
#
# Revision 1.3  1994/01/15  21:06:26  msmcq
# revisions in connection with DI, for P3.
#
# Revision 1.2  1993/09/16  15:06:37  msmcq
# Add to terminologyInclusions class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : rebreak some lines (Script problem)     --><!-- 94-03-21 : MSM : correct ID of DATE class to cldate      --><!-- 6 mar: LB rename certainty attribute to avoid confusion --><!-- 94-01-15 : MSM : correct ref to stdVals                  --><!-- 93-09-15 : MSM : include in class termincl               --><!-- 92-12-22 : MSM : replace iso 2014 by 8601 as per G Budin, SEW --><!-- 92-12-07 : MSM : change TYPE att to CALENDAR             --><!-- 92-12-06 : MSM : add DATE class                          --><!-- ******************************************************** date --><tagDoc id="DATE" usage="opt"><gi tei="yes">date</gi><desc>contains a date in any format.</desc><attList><attDef usage="opt"><attName>calendar</attName><desc>indicates the system or calendar to which the date belongs.</desc><datatype>CDATA</datatype><valDesc>Recommended values include:
<term>Gregorian</term>,
<term>Julian</term>,
<term>Roman</term>,
<term>Mosaic</term>,
<term>Revolutionary</term>,
<term>Islamic</term>.</valDesc><default>#IMPLIED</default><eg><![CDATA[He was born on <date calendar=Gregorian>Feb. 22,
1732</date> (<date calendar=Julian
value='1732-2-22'>Feb. 11, 1731/32, O.S.</date>).]]><!-- Entry on George Washington, Columbia Encyclopedia, 2d ed. --><!-- ed. William Bridgwater and Elizabeth J. Sherwood         --><!-- (Morningside Heights:  Columbia UP, 1950), p. 2111       --></eg></attDef><attDef usage="opt"><attName>value</attName><desc>gives the value of the date in some standard form, usually
yyyy-mm-dd.</desc><datatype>CDATA</datatype><valDesc>Any string representing a date in standard format; recommended
form is <q>yyyy-mm-dd</q>, as defined by ISO 8601: 1988, <title>Data
elements and interchange formats --- Information interchange ---
Representation of dates and times.</title></valDesc><default>#IMPLIED</default><eg><![CDATA[This list begins in the year 1632, more precisely
on Trinity Sunday, i.e. the Sunday after Pentecost,
in that year the <date calendar=Julian value=1632-6-6>
27th of May (old style)</date>.]]></eg><!-- need source for this example --><!-- Appears not to be Leipziger Matrikel                     --><!-- Maybe something in MHD?                                  --><remarks><p>For simple dates, the value should give the Gregorian date
in the form (yyyy-mm-dd) specified by ISO 8601.  More complicated dates
or special applications may require another calendar or another form;
these should be documented in the <gi tei="yes">stdVals</gi> element in the TEI
Header.</p></remarks></attDef><attDef usage="opt"><attName>certainty</attName><desc>indicates the degree of precision to be attributed to the date.</desc><datatype>CDATA</datatype><valDesc>Any appropriate value, e.g.
<term>ca.</term>,
<term>approx</term>,
<term>after</term>,
<term>before</term>.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<date value='1980-02' certainty=approx>early February 1980</date>]]></eg></exemplum><exemplum><eg><![CDATA[Given on the <date value='1977-06-12'>Twelfth Day of June
in the Year of Our Lord One Thousand Nine Hundred and
Seventy-seven of the Republic the Two Hundredth and first
and of the University the Eighty-Sixth.</date>]]></eg></exemplum><!-- diploma of A.B. awarded by Stanford University --><exemplum><eg><![CDATA[<date value='1990-09'>September 1990</date>]]></eg></exemplum><remarks></remarks><part type="top" name="core"/><classes names="DATA CLDATE TERMINCL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONADA" type="div3"/><xref target="HD24" type="div3"/><xref target="HD6" type="div3"/><xref target="COBICOI" type="div3"/><xref target="TETA" type="div3"/><xref target="CCAHSE" type="div3"/><xref target="NDDATE"/></tagDoc><?tei:EOF date.tag ??><!-- date element --><?tei:SOF dateline.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: dateline.tag,v $
    * Revision 1.4  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.3  1998/01/28 19:22:39  tei
    * LB changes of 1998-01
    *
    * Revision 1.2  1994/01/04  12:14:03  lou
    * fix xrefs
    *
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                                 --><!-- 4 Jan 98 : LB : applied DIVTOP fix (added to divtop class) --><!-- 2 jan 93: LB : change placename to name --><!-- 93-06-02 : MSM : revise content model following LM dateline --><!-- *******************************************************dateline --><tagDoc id="DATELINE" usage="opt"><gi tei="yes">dateline</gi><desc>contains a brief description of the place, date, time, etc. of
production of a letter, newspaper story, or other work, prefixed or
suffixed to it as a kind of heading or trailer. </desc><attList></attList><exemplum><eg><![CDATA[<dateline>Walden, this 29. of August 1592</dateline>]]></eg></exemplum><exemplum><eg><![CDATA[<div type=chapter><p>
<!-- ... -->
and his heart was going like mad and yes
 I said yes I will Yes.</p>
 <closer>
  <dateline>
    <name type=place>Trieste-Z&uuml;rich-Paris,</name>
    <date>1914-1921</date>
  </dateline>
 </closer></div>]]></eg><!-- James Joyce, Ulysses --></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVTOP DIVBOT"/><elemDecl>- O (date | time | name | #PCDATA | address)*</elemDecl><xref target="DSCO"/><xref target="DSOC"/></tagDoc><?tei:EOF dateline.tag ??><!-- dateline element --><?tei:SOF daterang.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	daterang.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1994/03/28  20:07:24  msmcq
    * correct ID of date class (cldate, not date)
    *
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : specify type=closed on vallist --><!-- 94-03-28 : MSM : correct class ref to cldate             --><!-- 92-12-07 : MSM : change TYPE att to CALENDAR             --><!-- 92-12-06 : MSM : add DATE class                          --><!-- **************************************************** daterang --><tagDoc id="DATERANG" usage="opt"><gi tei="yes">dateRange</gi><name>date range</name><desc>contains two dates or another phrase delimiting a time period.</desc><attList><attDef usage="opt"><attName>calendar</attName><desc>indicates the system or calendar to which the date belongs.</desc><datatype>CDATA</datatype><valDesc>Recommended values include:
<term>Gregorian</term>,
<term>Julian</term>,
<term>Roman</term>,
<term>Mosaic</term>,
<term>Revolutionary</term>,
<term>Islamic</term>.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>from</attName><desc>indicates the starting point of the period in standard form.</desc><datatype>CDATA</datatype><valDesc>any date in a standard form; recommended form is yyyy-mm-dd.</valDesc><default>#IMPLIED</default><remarks><p>The value should conform to the standard form declared in
the <gi tei="yes">std.vals</gi> element in the TEI header.</p></remarks></attDef><attDef usage="opt"><attName>to</attName><desc>indicates the ending point of the period in standard form.</desc><datatype>CDATA</datatype><valDesc>any date in a standard form; recommended form is yyyy-mm-dd.</valDesc><default>#IMPLIED</default><remarks><p>The value should conform to the standard form declared in
the <gi tei="yes">stdVals</gi> element in the TEI header.</p></remarks></attDef><attDef usage="opt"><attName>exact</attName><desc>indicates the precision to be attached to either or both dates
specified.</desc><datatype>(to|from|both|none)</datatype><valList type="closed"><val>to</val><desc>the <att tei="yes">to</att> date is exact</desc><val>from</val><desc>the <att tei="yes">from</att> date is exact</desc><val>both</val><desc>both dates are exact</desc><val>none</val><desc>both dates are approximate or unspecified</desc></valList><default>#IMPLIED</default><eg><![CDATA[  <dateRange from=1100 to=1120 exact=from>
       Early 12th century</dateRange>]]></eg><remarks><p>date values should conform to the standard form declared in
the <gi tei="yes">stdVals</gi> element in the TEI header.</p></remarks></attDef></attList><exemplum><eg><![CDATA[He edited (<dateRange from=1846 to=1848>1846-48</dateRange>)
the first collection of Hungarian folk poetry.]]></eg></exemplum><part type="top" name="core"/><classes names="DATA CLDATE"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%phrase.seq;)</elemDecl><xref target="CONADA" type="div3"/></tagDoc><?tei:EOF daterang.tag ??><!-- dateRange element --><?tei:SOF datestru.tag ??><!-- Revisions:                                               --><!-- 94-03-28 : MSM : correct class ref to cldate             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: datestru.tag,v $
    * Revision 1.4  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.3  94/03/28  20:07:24  msmcq
    * correct ID of date class (cldate, not date)
    * 
    * Revision 1.2  1994/03/15  11:10:24  lou
    * minor typos etc
    * 
    * Revision 1.1  1994/03/07  16:16:39  lou
    * Initial revision
    * --><!-- ******************************************************** dateStruct --><tagDoc id="DATESTRU" usage="opt"><gi tei="yes">dateStruct</gi><desc>contains an internally structured representation of a date.</desc><attList><attDef usage="opt"><attName>calendar</attName><desc>indicates the system or calendar to which the date belongs.</desc><datatype>CDATA</datatype><valDesc>Recommended values include:
<term>Gregorian</term>,
<term>Julian</term>,
<term>Roman</term>,
<term>Mosaic</term>,
<term>Revolutionary</term>,
<term>Islamic</term>.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>exact</attName><desc>indicates the degree of precision to be attributed to the date.</desc><datatype>CDATA</datatype><valDesc>Any appropriate value, e.g.
<term>ca.</term>,
<term>approx</term>,
<term>after</term>,
<term>before</term>.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<dateStruct value='1990-09'>
  <month>September</month>
  <year>1990</year>
</dateStruct>]]></eg></exemplum><exemplum><eg><![CDATA[Given on the
<dateStruct value='1977-06-12'>
    <day reg=12>  Twelfth</day> Day of
    <month reg=06>June</month>
    <year reg=1977 type=nominal>in the Year of Our Lord
    One Thousand Nine Hundred and Seventy-seven</year>
    <dateStruct>
      <offSet>of</offSet><year reg=1776>the Republic</year>
      <distance>the Two Hundredth and first</distance>
    </dateStruct>and
    <dateStruct>
      <offSet>of</offSet><year reg=1891>the University</year>
      <distance>the Eighty-Sixth.</distance>
    </dateStruct>
</dateStruct>]]></eg></exemplum><!-- diploma of A.B. awarded by Stanford University --><remarks></remarks><part type="top" name="core"/><classes names="DATA CLDATE TERMINCL TEMPEXP"/><dataDesc>May contain character data and temporal expression elements.</dataDesc><elemDecl>- -  ((%m.temporalExpr; | #pcdata)+)</elemDecl><!-- this model precludes date as subcomponent --><xref target="NDDATE"/><xref target="CONADA" type="div3"/><xref target="HD24" type="div3"/><xref target="HD6" type="div3"/><xref target="COBICOI" type="div3"/><xref target="TETA" type="div3"/><xref target="CCAHSE" type="div3"/></tagDoc><?tei:EOF datestru.tag ??><!-- dateStruct element --><?tei:SOF day.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	day.tag,v $
# Revision 1.3  94/03/07  16:16:51  lou
# revised for ND
# 
# Revision 1.2  1993/08/03  01:49:15  msmcq
# fix MS end problem
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- day --><tagDoc id="DAY" usage="opt"><gi tei="yes">day</gi><name>day</name><desc>the day component of a structured date.</desc><attList></attList><exemplum><eg><![CDATA[<dateStruct value='14-05-1993'>
  <day type=name>Friday</day>,
  <day type=number>14</day>
  <month type=name>May</month>
  <year>1993</year></dateStruct>]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF day.tag ??><!-- day element --><?tei:SOF def.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : add to class diparts (!)                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	def.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** def --><tagDoc id="DEF" usage="opt"><gi tei="yes">def</gi><name>definition</name><desc>contains definition text in a dictionary entry.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPDE"/></tagDoc><?tei:EOF def.tag ??><!-- def element --><?tei:SOF default.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	default.tag,v $
# Revision 1.3  93/09/16  15:07:52  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:49:52  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** default --><tagDoc id="DEFAULT" usage="req"><gi tei="yes">default</gi><desc>specifies the default declared value for an attribute.</desc><attList></attList><exemplum><eg><![CDATA[  <default>#IMPLIED]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>any legal SGML declared value or TEI-defined keyword</dataDesc><elemDecl>- O (#PCDATA) </elemDecl><xref target="TDATT"/></tagDoc><?tei:EOF default.tag ??><!-- default element --><?tei:SOF del.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	del.tag,v $
# Revision 1.5  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.4  1994/03/08  03:24:27  msmcq
    * revision for P3
    * 
    * Revision 1.3  1994/01/04  12:14:04  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/03  01:59:34  msmcq
    * fix INHERITED keyword
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : it's <gap>, not <omit> stupid!           --><!-- 94-03-07 : MSM : change DESC as per CH suggestion        --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct INHERITED                       --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- 92-11-09 : MSM : specify datatype on REND                --><!-- ********************************************************* del --><tagDoc id="DEL" usage="opt"><gi tei="yes">del</gi><name>deletion</name><desc>contains a letter, word or passage deleted, marked as deleted,
or otherwise indicated as superfluous or spurious in the copy text by an
author, scribe, annotator or corrector.</desc><attList><attDef usage="opt"><attName>rend</attName><name>rendition</name><desc>indicates how the deletion was indicated in the copy text.</desc><datatype>CDATA</datatype><valList type="open"><val>subpunction</val><desc>dots below the line indicate matter to be
                            deleted.</desc><val>overstrike</val><desc>lines through the text indicated matter to be deleted.</desc><val>erasure</val><desc>material to be deleted has been erased
(but
                            remains legible enough to transcribe).</desc><val>bracketed</val><desc>brackets around the material indicate
that
                            it is spurious or superfluous.</desc></valList><default>#IMPLIED</default><eg></eg></attDef><attDef usage="opt"><attName>type</attName><desc>classifies the type of deletion using any convenient typology.</desc><datatype>CDATA</datatype><valDesc>any string identifying the class of deletion.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>No recommendation of any particular typology is made
here;
to record the manner in which the deletion is signaled, use
<att tei="yes">rend</att>, not <att tei="yes">type</att>.</p></remarks></attDef><attDef usage="opt"><attName>status</attName><desc>may be used to indicate faulty deletions, e.g.
strikeouts which include too much or too little text.</desc><datatype>CDATA</datatype><valDesc>any description of flaws in the marking of a deletion, e.g.
<q>excess left</q>, <q>excess right</q>, <q>short left</q>, <q>short
right</q>.</valDesc><default>'unremarkable'</default><eg></eg><remarks><p>Status information on each deletion is needed rather
rarely
except in critical editions from authorial manuscripts.</p></remarks></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for identifying
the hand of the deletion.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the
identification of the hand of the deletion.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>signifies the hand of the agent which made the deletion.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[<l><del type=overtyped>Mein</del> Frisch
   <del type=overstrike>schwebt</del> weht der Wind]]></eg></exemplum><remarks><p>Cf. <gi tei="yes">gap</gi>.</p><p>Degrees of uncertainty over what can
still be read may be indicated by use of the
<gi tei="yes">certainty</gi> element (see <xref target="CE"/>).</p><p>This element  should be used for deletion of shorter
sequences of text, typically single words or phrases.
The <gi tei="yes">delSpan</gi> element should be used for longer
sequences of text, for those containing structural
subdivisions, and for those containing overlapping
additions and deletions.</p><p>The text deleted must be at least partially legible, in order for
the encoder to be able to transcribe it.  If it is not legible at
all, the <gi tei="yes">del</gi> tag should not be used.  Rather, the
<gi tei="yes">gap</gi> tag should be employed to signal that text cannot be
transcribed, with the value of the <att tei="yes">reason</att> attribute giving
the cause for the omission from the transcription as deletion.  If it
is not fully legible, the <gi tei="yes">unclear</gi> element (available when
using the additional tagset for transcription of primary sources)
should be used to signal the areas of text which cannot be read with
confidence.  See further sections <xref target="PHOM"/> and, for the
close association of the <gi tei="yes">del</gi> tag with the <gi tei="yes">gap</gi>,
<gi tei="yes">damage</gi>, <gi tei="yes">unclear</gi> and <gi tei="yes">supplied</gi> elements (the
latter three tags available when using the additional tagset for
transcription of primary sources), <xref target="PHCOMB"/>.</p><p>The <gi tei="yes">del</gi> tag should not be used for deletions made by
editors or encoders.  In these cases, either the <gi tei="yes">corr</gi> tag or
the <gi tei="yes">gap</gi> tag should be used.</p></remarks><part type="top" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="COEDADD" type="div3"/></tagDoc><?tei:EOF del.tag ??><!-- del element --><?tei:SOF delspan.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	delspan.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/08/29  15:20:05  msmcq
    * fixes for unreachability
    * (divGen et al.)
    * 
    * Revision 1.4  1994/03/25  16:13:30  msmcq
    * restore changes overwritten by version 1.3,
    * change #inherited to %inherited
    * 
    * Revision 1.2  1994/03/08  03:24:27  msmcq
    * revision for P3
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- Revisions:                                               --><!-- 4 Jan 98: LB : changed class membership from edit to editincl --><!-- 4 Jan 98: LB : replaced refs to <omit> by refs to <gap>  --><!-- 94-08-04 : MSM : correct classes element                 --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- 94-03-21 : MSM : correct 'inherited' error               --><!-- 94-03-07 : MSM : change DESC as per CH suggestion        --><!-- 94-03-03 : MSM : fix GI in examples                      --><!-- 94-03-03 : MSM : fix ANCHOR in example                   --><!-- 93-06-05 : MSM : clear up bad comment                    --><!-- ENTITY delspan  system 'delspan.tag' --><!-- delSpan tag --><!-- *********************************************** delSpan --><tagDoc id="DELSPAN" usage="opt"><gi tei="yes">delSpan</gi><name>deleted span of text</name><desc>marks the beginning of a longer sequence of text deleted,
marked as deleted, or otherwise signaled as superfluous or spurious by an
author, scribe, annotator, or corrector.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the deletion, using any convenient typology.</desc><datatype>CDATA</datatype><valList type="open"><val>overstrike</val><desc>deletion indicated by line crossing out the text.</desc><val>erasure</val><desc>deletion indicated by erasure of the text.</desc><val>bracketed</val><desc>deletion indicated by brackets in the text or margin.</desc><val>subpunction</val><desc>deletion indicated by dots beneath the letters deleted.</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for identifying
the hand of the deletion.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the
identification of the hand of the deletion.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>signifies the hand of the agent which made the deletion.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ..................................................... to --><attDef usage="req"><attName>to</attName><desc>identifies the endpoint of the deleted passage, by giving the
ID
of an <gi tei="yes">anchor</gi> or other element placed there.</desc><datatype>IDREF</datatype><valDesc>any valid SGML identifier, used on a later element.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p>Both the beginning and the end of the deleted material
must
be marked; the beginning by the <gi tei="yes">delSpan</gi> element itself, the
end by the <att tei="yes">to</att> attribute.  The element pointed at by
<att tei="yes">to</att> is understood to be included within the deleted
passage.</p></remarks></attDef><!-- ................................................. status --><attDef usage="opt"><attName>status</attName><desc>indicates whether the deletion is faulty, e.g. by including too
much or too little text.</desc><datatype>CDATA</datatype><valList type="open"><val>excess start</val><desc>some text at the beginning of the deletion is marked as
deleted even though it clearly should not be deleted.</desc><val>excess end</val><desc>some text at the end of the deletion is marked as
deleted even though it clearly should not be deleted.</desc><val>short start</val><desc>some text at the beginning of the deletion is not marked as
deleted even though it clearly should be.</desc><val>short end</val><desc>some text at the end of the deletion is not marked as
deleted even though it clearly should be.</desc><val>unremarkable</val><desc>the deletion is not faulty.</desc></valList><default>'unremarkable'</default><eg><![CDATA[ ]]></eg><remarks><p><!-- have replaced 'right' and 'left' with 'start' and 'end',  --><!-- which are less ambiguous in the case of vertical writing.  -MSM --></p><p>Marking a deletion as faulty is inescapably an interpretive act;
the usual test applied in practice is the linguistic acceptability of
the text with and without the letters or words in question.</p></remarks></attDef><!-- ................................................. length --><!-- < remarks >  < p > [Concerning length attribute on       --><!-- delSpan: Not clear to me why this is provided on  < gi   --><!-- > del.span < /gi > instead of on  < gi > omit < /gi >    --><!-- or  < gi > unclear < /gi > .  Suggest dropping it.       --><!-- -MSM                                                     --><!-- I agree.  Have deleted this attribute: it should be on   --><!-- OMIT and by definition cannot appear on DEL or its       --><!-- relatives -PR]                                           --></attList><exemplum><eg><![CDATA[<p>Paragraph partially deleted.  This is the undeleted
portion <delSpan resp=author to=a23>and this the deleted
portion of the paragraph.
<p>Paragraph deleted together with neighboring material.
<p>Second fully deleted paragraph.
<p>Paragraph partially deleted; in the middle of this
paragraph the deletion ends and the anchor point marks
the resumption <anchor id=A23> of the text. ...]]></eg></exemplum><remarks><p>Both the beginning and ending of the deleted sequence
must be marked:  the beginning by the <gi tei="yes">delSpan</gi> element, the
ending by the target of the <att tei="yes">to</att> attribute.</p><p>The text deleted must be at least partially legible, in order for
the encoder to be able to transcribe it.  If it is not legible at
all, the <gi tei="yes">delSpan</gi> tag should not be used.  Rather, the
<gi tei="yes">gap</gi> tag should be employed to signal that text cannot be
transcribed, with the value of the <att tei="yes">reason</att> attribute giving
the cause for the omission from the transcription as deletion.  If it
is not fully legible, the <gi tei="yes">unclear</gi> element should be used to
signal the areas of text which cannot be read with confidence.  See
further sections <xref target="PHOM"/> and, for the close association of
the <gi tei="yes">delSpan</gi> tag with the <gi tei="yes">gap</gi>, <gi tei="yes">damage</gi>,
<gi tei="yes">unclear</gi> and <gi tei="yes">supplied</gi> elements, <xref target="PHCOMB"/>.</p><p>The <gi tei="yes">delSpan</gi> tag should not be used for deletions made by
editors or encoders.  In these cases, either the <gi tei="yes">corr</gi> tag or
the <gi tei="yes">gap</gi> tag should be used.</p></remarks><part type="top" name="tc"/><classes names="EDITINCL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="PHAD"/></tagDoc><?tei:EOF delspan.tag ??><!-- delSpan element --><?tei:SOF derivatn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	derivatn.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* derivatn --><tagDoc id="DERIVATN" usage="opt"><gi tei="yes">derivation</gi><desc>describes the nature and extent of indebtedness or derivativeness
of this text with respect to others.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>categorizes the derivation of the text.
   </desc><datatype>CDATA
   </datatype><valList type="open"><val>original</val><desc>text is original
        </desc><val>revision</val><desc>text is a revision of some other text
        </desc><val>translation</val><desc>text is a translation of some other text
        </desc><val>abridgment</val><desc>text is an abridged version of some other text
        </desc><val>plagiarism</val><desc>text is plagiarized from some other text
        </desc><val>traditional</val><desc>text has no obvious source but is one of a
        number derived from some common ancestor
    </desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[    <derivation type=original>]]></eg></exemplum><remarks><p>For derivative texts, details of the ancestor
may be included in the source description.</p></remarks><part type="aux" name="corpora"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF derivatn.tag ??><!-- derivation element --><?tei:SOF wsddesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsddesc.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- *************************************************** desc --><tagDoc id="WSDDESC" usage="opt"><gi tei="yes">desc</gi><name>description</name><desc>(in a writing system declaration) contains a description of a
character or character form.</desc><attList></attList><exemplum><eg><![CDATA[ <form string='a'>
   <desc>Latin lower-case letter A</desc>
 <form>
 <form string='' entityLoc='infinity'>
   <desc>author's private symbol for infinity:  a parabola open to
         the right, with a dot at its focal point.  In general, the
         character rests on the base line and rises to about the
         height of a typical ascender.</desc>
 </form>]]></eg></exemplum><remarks><p>The <gi tei="yes">desc</gi> element should usually contain the name of
the character or character form; in some cases further information (e.g.
the description of the character's shape) will be useful, as shown in
the example.</p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain character data only.</dataDesc><elemDecl>- O  (#PCDATA)</elemDecl><xref target="WDCSEX"/></tagDoc><?tei:EOF wsddesc.tag ??><!-- desc element (for WSD) --><?tei:SOF desc.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : change model from phrase.seq to paraContent --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	desc.tag,v $
# Revision 1.4  94/01/04  12:14:05  lou
# fix xrefs
# 
# Revision 1.3  1993/09/16  15:07:52  msmcq
# Publication of TD
#
# Revision 1.2  1993/08/13  20:49:52  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** desc --><tagDoc id="DESC" usage="req"><gi tei="yes">desc</gi><name>description</name><desc>contains a brief description of the purpose and application for
an element, attribute, or attribute value.</desc><attList></attList><exemplum><eg><![CDATA[<desc>contains a brief description of the purpose and application for
an element, attribute, attribute value, class, or entity.]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>TEI convention requires that this be expressed as a finite
clause, begining with an active verb.</dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="TDTAG"/><xref target="TDATT"/><xref target="TDCLA"/><xref target="TDENT"/></tagDoc><?tei:EOF desc.tag ??><!-- desc element --><?tei:SOF descrip.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	descrip.tag,v $
# Revision 1.4  94/03/21  14:33:07  lou
# second major typo purge
# 
# Revision 1.3  1994/01/04  12:14:06  lou
# fix xrefs
#
# Revision 1.2  1993/09/15  23:08:09  msmcq
# Change class membership
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : include in class termmisc               --><!-- 92-12-23 : MSM : expand TC37dd entity                    --><!-- 92-12-18 : MSM : remove FLATTERM class                   --><!-- 92-11-23 : MSM : define default                          --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- ************************************************ descrip --><tagDoc id="DESCRIP" usage="rec"><gi tei="yes">descrip</gi><name>description</name><desc>within a <gi tei="yes">termEntry</gi> element, contains a definition,
context or explanation used to explain or define the concept represented
by a <gi tei="yes">term</gi> or an <gi tei="yes">otherForm</gi>.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the description using some convenient typology,
preferably the dictionary of data element types specified in ISO WD 12
620.</desc><datatype>CDATA</datatype><valList type="semi"><val>definition
    </val><desc>The description provides all the information needed to
          differentiate one concept from all other related concepts in
          the given domain.</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>A much fuller list of values for the <att tei="yes">type</att>
attribute may be generated from the dictionary of data element types
under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in
Terminology.  See ISO 12 620 for fuller details.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>(optional)</p></remarks><part type="base" name="term"/><classes names="TERMMISC"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="TEDTF" type="div1"/><xref target="TEDTN" type="div1"/><xref target="TETA" type="div1"/></tagDoc><?tei:EOF descrip.tag ??><!-- descrip element --><?tei:SOF dft.tag ??><!-- **************************************************** dft --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dft.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1994/01/04  00:36:16  msmcq
# correct example (rename DFT from DEFAULT)
#
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 94-01-03 : MSM : correct example                         --><!-- 93-09-22 : MSM : extract from tagdocs file               --><!-- **************************************************** dft --><tagDoc id="DFT" usage="rwa"><gi tei="yes">dft</gi><name>Default value</name><desc>provides default value for a feature.</desc><attList></attList><exemplum><eg><![CDATA[<f name=gender><dft></f>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSBO" type="div3"/></tagDoc><?tei:EOF dft.tag ??><!-- dft            --><?tei:SOF directn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	directn.tag,v $
# Revision 1.2  94/01/04  12:14:06  lou
# fix xrefs
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ********************************************** direction --><tagDoc id="DIRECTN" usage="rec"><gi tei="yes">direction</gi><desc>specifies one or more conventional directions in which a language
is written using a given script.</desc><attList><!-- .................................................. chars --><attDef usage="req"><attName>chars</attName><name>characters</name><desc>indicates the order in which characters within a line are
conventionally presented in this writing system</desc><datatype>CDATA</datatype><valList type="semi"><val>LR </val><desc>left to right</desc><val>RL </val><desc>right to left</desc><val>TB </val><desc>top to bottom</desc><val>BT </val><desc>bottom to top</desc></valList><default>#REQUIRED</default><remarks><p>If the characters follow each other in some order other than
top-to-bottom, bottom-to-top, left-to-right, or right-to-left, then some
value other than those indicated should be used.</p></remarks></attDef><!-- .................................................. lines --><attDef usage="req"><attName>lines</attName><desc>indicates the order in which lines conventionally follow each
other in this writing system.</desc><datatype>CDATA</datatype><valList type="semi"><val>TB </val><desc>top to bottom</desc><val>BT </val><desc>bottom to top</desc><val>LR </val><desc>left to right</desc><val>RL </val><desc>right to left</desc></valList><default>#REQUIRED</default><remarks><p>If the lines follow each other in some order other than
top-to-bottom, bottom-to-top, left-to-right, or right-to-left, then some
value other than those indicated should be used.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<eclaration lang=eng id='DEU'
 name='-//TEI P2: 1993//WSD Modern German//en' date='1993-06-01'>
 <language iso639='deu'>New High German</language>
 <script>Latin script with diacritics.</script>
 <direction chars='LR' lines='TB'>
 <!-- ... -->
</eclaration>]]></eg></exemplum><exemplum><p>If more than one direction is specified, it means that the script in
question may be written in any of the directions named.  In some cases,
the directions may be mixed within a single document, in others not; no
information is given on this point by the writing system declaration, as
it is not usefully formalizable.  Experts on the script must be
consulted for details.  The following example shows one way to declare
that a script may be written in any horizontal or vertical
direction.</p><eg><![CDATA[<eclaration lang=eng id=JPN
 name='-//TEI P2: 1993//WSD JIS 0208//en' date='1993-06-01'>
 <language iso639='jpn'>Modern Japanese</language>
 <script>normal Japanese writing, with mixture of hiragana,
         katakana, and kanji.</script>
 <direction chars='LR' lines='TB'>
 <direction chars='RL' lines='TB'>
 <direction chars='LR' lines='BT'>
 <direction chars='RL' lines='BT'>
 <direction chars='TB' lines='LR'>
 <direction chars='BT' lines='LR'>
 <direction chars='TB' lines='RL'>
 <direction chars='BT' lines='RL'>
 <!-- Japanese can, in effect, be written in any direction. -->
 <!-- Individual documents may, but need not, mix the       -->
 <!-- various directions.                                   -->
 <!-- ... -->
</eclaration>]]></eg></exemplum><exemplum><p>The following example shows another way to specify that a script may
be written in any horizontal or vertical direction.</p><eg><![CDATA[<eclaration lang=eng id=JPN
 name='//TEI P2: 1993//WSD JIS 0208//en' date='1993-06-01'>
 <language iso639='jpn'>Modern Japanese</language>
 <script>normal Japanese, with mixture of hiragana, katakana,
         and kanji.</script>
 <direction chars='LR RL' lines='TB BT'>
 <direction chars='TB BT' lines='LR RL'>
 <!-- Japanese can, in effect, be written in any direction. -->
 <!-- Individual documents may, but need not, mix the       -->
 <!-- various directions.                                   -->
 <!-- ... -->
</eclaration>]]></eg></exemplum><exemplum><p>In some cases, the <att tei="yes">lines</att> and <att tei="yes">chars</att> attributes
may need to take special values.  Some scripts are written in
<soCalled>boustrophedon</soCalled> (turning back and forth):  i.e. one
line is written left to right, the next right to left, and so on.  Such
a writing system might have its direction declared as shown:</p><eg><![CDATA[ <direction chars='boustrophedon:  LR, then RL, then LR, etc.'
            lines='TB'>]]></eg></exemplum><remarks><p>This element describes conventional presentation; all
scripts are subject to unusual treatment in special circumstances, and
such unusual directions need not be described here.  The treatment of
numerals in Latin, Hebrew, and Arabic script, being well understood,
need not be documented separately here.<note source="auth" place="foot" anchored="Y">Although the
scripts run in opposite directions, they write numbers in the same
direction; the usual view is that the numbers in Hebrew and Arabic run
left to right, like those in Latin script, but it is also possible to
claim that the numbers in Latin scripts run right to left, like those in
Arabic and Hebrew.  There is no single satisfactory answer to this
question.</note>
 </p><p>The <gi tei="yes">direction</gi> element is informational only, not normative.
It is intended to alert those responsible for implementing support for a
given writing system to an essential fact of how it is written.  If only
a single direction is specified, it is safe to infer that the script may
legitimately be presented in that direction.  If multiple directions are
specified, it may be legitimate to present text in any one of them, or
it may be necessary to support multiple directions in display of a
single document.  If the latter, then changes of direction should be
given using the global <att tei="yes">rend</att> attribute.
 </p><p>If no direction element is given, the only safe assumption is that
any direction is possible and experts must be consulted before
attempting to implement support for the writing system.
 </p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="WDWS"/><xref target="WDOV"/></tagDoc><?tei:EOF directn.tag ??><!-- direction element --><?tei:SOF distance.tag ??><!-- Revisions:                                               --><!-- 94-03-21 : MSM : supply explicit end-tags for attdef components --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	distance.tag,v $
# Revision 1.3  94/03/25  17:21:51  msmcq
# cleanup of miscellaneous tagdocs:  some typos,
# some INHERITED errors, supplied explicit end-tags for many attdef parts
# to shield a weakness of oddref1 (now fixed)
# 
# Revision 1.2  1994/03/07  16:16:45  lou
# initial check in of nd
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--******************************************************** distance --><!-- 6 Mar : revised somewhat; add to tempexp class --><tagDoc id="DISTANCE" usage="opt"><gi tei="yes">distance</gi><name>distance</name><desc>that part of a relative temporal or spatial expression which indicates
the distance between the place or time denoted by it and the place or
time referred to within it.</desc><attList><attDef usage="mwa"><attName>exact</attName><desc>indicates the degree of accuracy associated with the distance.</desc><datatype>(Y|N|U)</datatype><valList type="open"><val>Y</val><desc>The distance is exact.</desc><val>N</val><desc>The distance is approximate.</desc><val>U</val><desc>Accuracy unavailable or unknown.</desc></valList><default>U</default></attDef><attDef usage="opt"><attName>reg</attName><desc>provides a normalized evaluation of the expression
of relative distance.</desc><datatype>CDATA</datatype><valDesc></valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<relPlace>
<distance>two miles</distance>
<offSet>north east of</offSet>
<placeName> Manchester</placeName>
</relPlace>
 
<dateStruct>
  <distance exact=N reg='14 days'>
     a fortnight</distance>
  <offSet>after</offSet>
  <calEvent>Michaelmas</calEvent>
</dateStruct>
 
<timeStruct>
  <distance>20 minutes</distance>
  <offSet>before</offSet>
  <calEvent>noon</calEvent>.
</timeStruct>]]></eg></exemplum><remarks><p>This is a specialized form of measure, used only within
relative temporal and spatial expressions.</p></remarks><part type="aux" name="ND"/><classes names="TEMPEXP PLACPART"/><elemDecl>- - (%phrase.seq)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF distance.tag ??><!-- distance element --><?tei:SOF distinct.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: distinct.tag,v $
    * Revision 1.3  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.2  94/01/04  12:14:07  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- **************************************************** distinct --><tagDoc id="DISTINCT" usage="opt"><gi tei="yes">distinct</gi><name>distinct</name><desc>identifies any word or phrase which is regarded as linguistically
distinct, for example as archaic, technical, dialectal, non-preferred,
etc., or as forming part of a sublanguage. </desc><attList><attDef usage="opt"><attName>type</attName><desc>specifies the sublanguage or register to which the word or phrase
is being assigned</desc><datatype>CDATA</datatype><valDesc>a semi-open user-defined list</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>time</attName><desc>specifies how the phrase is distinct diachronically</desc><datatype>CDATA</datatype><valDesc>a semi-open user-defined list</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>space</attName><desc>specifies how the phrase is distinct diatopically</desc><datatype>CDATA</datatype><valDesc>a semi-open user-defined list</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>social</attName><desc>specifies how the phrase is distinct diastatically</desc><datatype>CDATA</datatype><valDesc>a semi-open user-defined list</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[Next morning a boy in that dormitory confided to his
bosom friend, a <distinct type="ps_slang">fag</distinct> of
Macrea's, that there was trouble in their midst which
King <distinct type=archaic>would fain</distinct> keep
secret.]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc></dataDesc><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="COHQHD"/><xref target="COHQH"/></tagDoc><?tei:EOF distinct.tag ??><!-- distinct element --><?tei:SOF distrib.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	distrib.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- **************************************************distributor --><tagDoc id="DISTRIB" usage="opt"><gi tei="yes">distributor</gi><desc>supplies the name of a person or other agency responsible for the
distribution of a text.</desc><attList></attList><exemplum><eg><![CDATA[<distributor>Oxford Text Archive
<distributor>Redwood and Burn Ltd]]></eg></exemplum><remarks><!-- < p>Particularly where cataloguing is likely to be       --><!-- based on the content of the header, it is advisable to   --><!-- use generally recognized authority lists for the exact   --><!-- form of personal names.                                  --></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="HD24"/></tagDoc><?tei:EOF distrib.tag ??><!-- distributor element --><?tei:SOF div.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: div.tag,v $
    * Revision 1.7  1999/02/22 15:55:17  tei
    * fix comments
    *
   * Revision 1.6  1998/03/11 18:53:55  tei
   * correcting egs
   *
   * Revision 1.5  1994/08/29 15:20:05  msmcq
   * fixes for unreachability
   * (divGen et al.)
   *
    * Revision 1.4  1994/03/15  11:10:25  lou
    * minor typos etc
    * 
    * Revision 1.3  1994/01/04  12:14:08  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/18  22:47:36  msmcq
    * put parens around %component before +
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- **********************************************************div --><tagDoc id="DIV" usage="rwa"><gi tei="yes">div</gi><name>text division</name><desc>contains a subdivision of the front, body, or back of a text.</desc><attList></attList><exemplum><eg><![CDATA[<body>
<div type=part><head>Fallacies of Authority</head>
<p>The subject of which is Authority in
various shapes, and the object, to repress all
exercise of the reasoning faculty.</p>
  <div type=chapter n=1><head>The Nature of Authority</head>
  <p>With reference to any proposed measures
  having for their object the greatest happiness
  of the greatest number....
     <div type=section n='1.1'><head>Analysis of Authority
      <p>What on any given occasion is the legitimate
      weight or influence to be attached to authority
      <!-- ... -->
     </div>
     <div type=section n='1.2'><head>Appeal to Authority,
        in What Cases Fallacious.
      <p>Reference to authority is open to the charge of
      fallacy when...
      <!-- ... -->
     </div> <!-- end of section 1.2 -->
     <!-- other sections here -->
   </div> <!-- end of chapter 1 -->
 <!-- other chapters here -->
 </div> <!-- end of part A -->
 <!-- other parts here -->
</body>]]><!-- J Bentham: Handbook of Political Fallacies (1824), ed --><!-- Larrabee, Johns Hopkins Pr, 1952 --></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*,
              ((div | divGen)+
              | ((%component;)+, (div | divGen)*)), (%m.divbot;)*)</elemDecl><xref target="DSDIV"/><xref target="TEDT"/><xref target="DSDIV1"/></tagDoc><?tei:EOF div.tag ??><!-- div element --><?tei:SOF divgen.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: divgen.tag,v $
    * Revision 1.5  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.4  98/01/31  17:18:34  tei
    * fix log keyword problem
    * 
    * Revision 1.3  98/01/30  14:52:24  tei
    * clfront, not front, dummy
    * 
    * Revision 1.2  94/08/29  15:20:05  msmcq
    * fixes for unreachability
    * (divGen et al.)
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 94-08-04 : MSM : add to class front (fix DIVGEN)         --><!-- 2 jun 93: LB: change name from div.gen --><!-- 92-12-09 : MSM : correct type                            --><!-- 92-12-09 : MSM : rename from indexdiv                    --><!-- 92-12-07 : MSM : change xref to COnoix                   --><!-- 92-11-09 : MSM : set xref to COmi                        --><!-- ************************************************* divgen --><tagDoc id="DIVGEN" usage="opt"><gi tei="yes">divGen</gi><name>automatically generated text division</name><desc>indicates the location at which a textual division generated
automatically by a text-processing application is to appear.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>specifies what type of generated text division (e.g. index,
table of contents, etc.) is to appear.</desc><datatype>CDATA</datatype><valList type="open"><val>index </val><desc>an index is to be generated and inserted at this point.</desc><val>toc </val><desc>a table of contents</desc><val>figlist </val><desc>a list of figures</desc><val>tablist </val><desc>a list of tables</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>Valid values are application-dependent; those shown are of
obvious utility in document production, but are by no means exhaustive.</p></remarks></attDef></attList><exemplum><p>One use for this element is to allow document preparation
software to generate an index and insert it in the appropriate place in
the output.  The example below assumes that the <att tei="yes">index</att>
attribute on the <gi tei="yes">index</gi> element has been used to specify index
entries for multiple indices, 1 and 2.</p><eg><![CDATA[<back>
<div1 type=backmat>
<head>Bibliography</head>
<listBibl>
 <bibl> <!-- ... --></bibl>
 <!-- ... -->
</listBibl>
</div1>
<div1>
<head>Indices</head>
<divGen type='index 1' n='Index Nominum'>
<divGen type='index 2' n='Index Rerum'>
</div1>
</back>]]></eg></exemplum><exemplum><p>Another use for <gi tei="yes">divGen</gi> is to specify the
location of an automatically produced table of contents:</p><eg rend="skel"><![CDATA[<front>
<titlePage> ... </titlePage>
<divGen type='toc'>
<div><head>Preface</head>
<p> ...
</front>]]></eg></exemplum><remarks><p>This element is intended primarily for use in document
production or manipulation, rather than in the transcription of
pre-existing materials; it makes it easier to specify the location of
indices, tables of contents, etc., to be generated by text preparation
or word processing software.  The <att tei="yes">n</att> attribute should be used
to give a title for the text division being generated.</p></remarks><part type="top" name="core"/><classes names="CLFRONT"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="CONOIX" type="div3"/></tagDoc><?tei:EOF divgen.tag ??><!-- divGen element --><?tei:SOF div0.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	div0.tag,v $
# Revision 1.5  94/08/29  15:20:05  msmcq
# fixes for unreachability
# (divGen et al.)
# 
# Revision 1.4  1994/03/15  11:10:25  lou
# minor typos etc
#
# Revision 1.3  1994/01/04  12:14:08  lou
# fix xrefs
#
# Revision 1.2  1993/08/18  22:54:14  msmcq
# parenthesize %component before +
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *********************************************************div0 --><tagDoc id="DIV0" usage="rwa"><gi tei="yes">div0</gi><name>level-0 text division</name><desc>contains the largest possible subdivision of the body
of a text.</desc><attList></attList><exemplum><eg><![CDATA[<div0 n=I id='LEVI' type=part>
   <head>Part I: Of Man </head>
   <div1 n='1' id='LEVI1' type=chapter>
     <head>Chap. I. Of Sense </head>
     <p>Concerning the Thoughts of man...
   </div1>
    <!-- further chapters here -->
</div0>
<div0 n=II id=LEVII type=part>
   <head>Part II: Of Common-Wealth</head>
   <!-- ... -->
</div0>]]><!-- Hobbes: Leviathan (1651): Penguin, 1968 --></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ( (div1 | divGen)+
              | ( (%component;)+, (div1 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div0.tag ??><!-- div0 element --><?tei:SOF div1.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: div1.tag,v $
    * Revision 1.7  1999/02/22 15:53:38  tei
    * fixed comments
    *
   *Revision 1.6  1998/03/11 18:53:55  tei
   *correcting egs

   *Revision 1.5  1994/08/29 15:20:05  msmcq
   *fixes for unreachability
   *(divGen et al.)

    * Revision 1.4  1994/03/15  11:10:26  lou
    * minor typos etc
    * 
    * Revision 1.3  1994/01/04  12:14:09  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/18  22:54:14  msmcq
    * parenthesize %component before +
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- *********************************************************div1 --><tagDoc id="DIV1" usage="rwa"><gi tei="yes">div1</gi><name>level-1 text division</name><desc>contains a first-level subdivision of the front, body, or back
of a text (the largest, if
<gi tei="yes">div0</gi> is not used, the second largest if it is).</desc><attList></attList><exemplum><eg><![CDATA[<div1 n=I id='LEVI' type=part>
   <head>Part I: Of Man </head>
   <div2 n='1' id='LEVI1' type=chapter>
     <head>Chap. I. Of Sense </head>
     <p>Concerning the Thoughts of man...
   </div2>
    <!-- further chapters here -->
</div1>
<div1 n=II id=LEVII type=part>
   <head>Part II: Of Common-Wealth</head>
   <p><!-- ... -->
</div1>]]><!-- Hobbes: Leviathan (1651): Penguin, 1968 --></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ( (div2 | divGen)+
              | ((%component;)+, (div2 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div1.tag ??><!-- div1 element --><?tei:SOF div2.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--
    * $Log: div2.tag,v $
    * Revision 1.7  1999/02/22 15:51:52  tei
    * fix comments
    *
    * Revision 1.6  1998/03/11 18:53:55  tei
    * correcting egs
    * Revision 1.5  1994/08/29 15:20:05  msmcq
    * fixes for unreachability
    * (divGen et al.)
    * Revision 1.4  1994/03/15  11:10:26  lou
    * minor typos etc
    * 
    * Revision 1.3  1994/01/04  12:14:10  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/18  22:54:14  msmcq
    * parenthesize %component before +
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- *********************************************************div2 --><tagDoc id="DIV2" usage="rwa"><gi tei="yes">div2</gi><name>level-2 text division</name><desc>contains a second-level subdivision of the front, body, or back of a
 text.</desc><attList></attList><exemplum><eg><![CDATA[<div1 n=2 type=part><head>The Second Partition:
              The Cure of Melancholy</head>
  <div2 n=2.1 type=section>
    <div3 n=2.1.1 type=member>
      <div4 n=2.1.1.1 type=subsection>
        <head>Unlawful Cures rejected.</head>
        <p>Inveterate melancholy, howsoever it may seem to
         be a continuate, inexorable disease, hard to be
         cured, accompanying them to their graves most part
         (as <ref target=A>Montanus</ref> observes), yet many
         times it may be helped...	
      <!-- ... -->
      </div4></div3>
  </div2>
  <div2 n=2.2>
   <div3 n=2.2.1><head>Sect. II. Memb. I</head>
      <p><!-- ... -->
   </div3></div2>
  <div2 n=2.3>
   <div3 n=2.3.1><head>Sect. III. Memb. I</head>
     <p><!-- ... -->
  </div3></div2>]]></eg><!-- Burton, Anatomy of Melancholy, 16th ed (1651), Blake, 1836 --></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ( (div3 | divGen)+
              | ((%component;)+, (div3 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div2.tag ??><!-- div2 element --><?tei:SOF div3.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: div3.tag,v $
    * Revision 1.7  1999/02/22 15:48:45  tei
    * fix comments
    *
 *   Revision 1.6  1998/03/11 18:53:55  tei
 *   correcting egs
 *  
 *   Revision 1.5  1994/08/29 15:20:05  msmcq
 *   fixes for unreachability
 *   (divGen et al.)

    * Revision 1.4  1994/03/15  11:10:27  lou
    * minor typos etc
    * 
    * Revision 1.3  1994/01/04  12:14:10  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/18  22:54:14  msmcq
    * parenthesize %component before +
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- *********************************************************div3 --><tagDoc id="DIV3" usage="rwa"><gi tei="yes">div3</gi><name>level-3 text division</name><desc>contains a third-level subdivision of the front, body, or back of a
 text.</desc><attList></attList><exemplum><eg><![CDATA[  <div2 n=2.2 type=section>
   <div3 n=2.2.1 type=member><head>Sect. II. Memb. I</head>
        <p><!-- ... -->
   </div3>
   <div3 n=2.2.2 type=member><head>Memb. II
        Retention and Evacuation rectified.</head>
       <p><!-- ... -->
   </div3>
   <div3 n=2.2.3 type=member><head>Memb. III
        Ayr rectified. With a digression of the Ayr.</head>
       <p><!-- ... -->
   </div3></div2>]]><!-- Burton, Anatomy of Melancholy, 16th ed (1651), Blake, 1836 --></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ( (div4 | divGen)+
              | ((%component;)+, (div4 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div3.tag ??><!-- div3 element --><?tei:SOF div4.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	div4.tag,v $
# Revision 1.5  94/08/29  15:20:05  msmcq
# fixes for unreachability
# (divGen et al.)
# 
# Revision 1.4  1994/03/15  11:10:28  lou
# minor typos etc
#
# Revision 1.3  1994/01/04  12:14:11  lou
# fix xrefs
#
# Revision 1.2  1993/08/18  22:54:14  msmcq
# parenthesize %component before +
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *********************************************************div4 --><tagDoc id="DIV4" usage="rwa"><gi tei="yes">div4</gi><name>level-4 text division</name><desc>contains a fourth-level subdivision of the front, body, or back of a
 text.</desc><attList></attList><exemplum><eg><![CDATA[ 
<div3 n=2.2.1><head>Sect. II. Memb. I</head>
 <div4 n=2.2.1.1 type=subsection>
  <head>Subsect I. -- Dyet rectified in substance.</head>
  <p>Diet, <term lang=GRK>diaitotiku</term>,
  <term lang=LAT>victus</term>  or living
  <!-- ... -->
 </div4>
 <div4 n=2.2.2.1 type=subsection>
  <head>Subsect II. -- Dyet rectified in quantity.</head>
  <p>Man alone, saith Cardan, eates and drinks without
  appetite, and useth all his pleasures without necessity
  <!-- ... -->
 </div4>
</div3>]]><!-- Burton, Anatomy of Melancholy, 16th ed (1651), Blake, 1836 --></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ( (div5 | divGen)+
              | ((%component;)+, (div5 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div4.tag ??><!-- div4 element --><?tei:SOF div5.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	div5.tag,v $
# Revision 1.5  94/08/29  15:20:05  msmcq
# fixes for unreachability
# (divGen et al.)
# 
# Revision 1.4  1994/03/15  11:10:28  lou
# minor typos etc
#
# Revision 1.3  1994/01/04  12:14:12  lou
# fix xrefs
#
# Revision 1.2  1993/08/18  22:54:14  msmcq
# parenthesize %component before +
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *********************************************************div5 --><tagDoc id="DIV5" usage="rwa"><gi tei="yes">div5</gi><name>level-5 text division</name><desc>contains a fifth-level subdivision of the front, body, or back of a
 text.</desc><attList></attList><exemplum><eg><![CDATA[<!-- see examples for higher level divisions -->]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ( (div6 | divGen)+
              | ((%component;)+, (div6 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div5.tag ??><!-- div5 element --><?tei:SOF div6.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : allow divGen (fix DIVGEN)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	div6.tag,v $
# Revision 1.5  94/08/29  15:20:05  msmcq
# fixes for unreachability
# (divGen et al.)
# 
# Revision 1.4  1994/03/15  11:10:29  lou
# minor typos etc
#
# Revision 1.3  1994/01/04  12:14:13  lou
# fix xrefs
#
# Revision 1.2  1993/08/18  22:54:14  msmcq
# parenthesize %component before +
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *********************************************************div6 --><tagDoc id="DIV6" usage="rwa"><gi tei="yes">div6</gi><name>level-6 text division</name><desc>contains a sixth-level subdivision of the front, body, or back of a
 text.</desc><attList></attList><exemplum><eg><![CDATA[<!-- see examples for higher level divisions -->]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, ((div7 | divGen)+
              | ((%component;)+, (div7 | divGen)*)),
              (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div6.tag ??><!-- div6 element --><?tei:SOF div7.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	div7.tag,v $
# Revision 1.4  94/03/15  11:10:30  lou
# minor typos etc
# 
# Revision 1.3  1994/01/04  12:14:13  lou
# fix xrefs
#
# Revision 1.2  1993/08/18  22:54:14  msmcq
# parenthesize %component before +
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *********************************************************div7 --><tagDoc id="DIV7" usage="rwa"><gi tei="yes">div7</gi><name>level-7 text division</name><desc>contains the smallest possible subdivision of the front, body or
back of a text, larger than a paragraph.</desc><attList></attList><exemplum><eg><![CDATA[<!-- see examples for higher level divisions -->]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVN DECLING"/><dataDesc>any sequence of low-level structural elements, possibly grouped
into lower subdivisions.</dataDesc><elemDecl>- O ((%m.divtop;)*, (%component;)+, (%m.divbot;)*)</elemDecl><xref target="DSDIV2"/><xref target="TEDT"/></tagDoc><?tei:EOF div7.tag ??><!-- div7 element --><?tei:SOF docauth.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: docauth.tag,v $
    * Revision 1.3  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.2  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 93-03-20 : MSM : lowercase tpparts                       --><!-- ********************************************** docAuthor --><tagDoc id="DOCAUTH" usage="rec"><gi tei="yes">docAuthor</gi><name>document author</name><desc>contains the name of the author of the document, as given on the
title page (often but not always contained in a <gi tei="yes">byline</gi>).</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The document author's name often occurs within a byline,
but the <gi tei="yes">docAuthor</gi> element may be used whether the
<gi tei="yes">byline</gi> element is used or not.</p></remarks><part type="base" name="core"/><classes names="TPPARTS DIVTOP FMCHUNK"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O (%phrase.seq;)</elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF docauth.tag ??><!-- docAuthor element --><?tei:SOF docdate.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: docdate.tag,v $
    * Revision 1.3  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.2  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- ******************************************************docdate --><!-- Added by MSM as part of campaign to get a title page that can --><!-- be used in document production without contortions.   Good luck!   --><tagDoc id="DOCDATE" usage="rec"><gi tei="yes">docDate</gi><name>document date</name><desc>contains the date of a document, as given
(usually) on a title page.</desc><attList><!-- .................................................. value --><attDef usage="opt"><attName>value</attName><desc>gives the value of the date in a standard form.</desc><datatype>%ISO-date</datatype><valDesc>Any string representing a date in standard format; recommended
form is <q>yyyy-mm-dd</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[This list begins in the year 1632, more precisely
on Trinity Sunday, i.e. the Sunday after Pentecost,
in that year the <date calendar=Julian value=1632-6-6>
27th of May (old style)</date>.]]><!-- Heinz Entner, Paul Fleming (Leipzig:  Reclam, 1989), 69. --><!-- tr. CMSMcQ                                               --><!-- check form of -6-6 or -06-06 with DD                     --></eg><remarks><p>For simple dates, the value should give the Gregorian date
in the form (yyyy-mm-dd) specified by ISO 8601.  More complicated dates
or special applications may require another calendar or another form;
these should be documented in the <gi tei="yes">std.vals</gi> element in the TEI
Header.</p></remarks></attDef><!-- Should all DATE attributes be shared? -msm               --></attList><exemplum><eg><![CDATA[<docImprint>Oxford, Clarendon Press, <docDate>1987</></docImprint>]]></eg></exemplum><remarks><p>Cf. the general <gi tei="yes">date</gi> element in the core tag set.
This specialized element is provided for convenience in marking and
processing the date of the documents, since it is likely to require
specialized handling for many applications.</p></remarks><part type="base" name="core"/><classes names="TPPARTS DIVTOP FMCHUNK"/><dataDesc></dataDesc><elemDecl>- O (%phrase.seq;)</elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF docdate.tag ??><!-- docDate element --><?tei:SOF doceditn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: doceditn.tag,v $
    * Revision 1.2  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- *****************************************************doceditn --><tagDoc id="DOCEDITN" usage="opt"><gi tei="yes">docEdition</gi><name>document edition</name><desc>contains an edition statement as presented on a title page of a
document.</desc><attList></attList><exemplum><eg><![CDATA[<docEdition>The Third edition Corrected</>]]></eg></exemplum><remarks><p>Cf. the <gi tei="yes">edition</gi> element of bibliographic
citation.  As usual, the shorter name has been given to the
more frequent element.</p></remarks><part type="base" name="core"/><classes names="TPPARTS FMCHUNK"/><dataDesc></dataDesc><elemDecl>- O (%paraContent;)</elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF doceditn.tag ??><!-- docEdition element --><?tei:SOF docimprt.tag ??><!-- Revisions:                                               --><!-- 27 aug: LB: fix stupid typo at end --><!-- 93-08-18 : MSM : suppress PLACE element                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: docimprt.tag,v $
    * Revision 1.5  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.4  93/08/27  11:54:26  lou
    * fixed stupid typo
    * 
    * Revision 1.3  1993/08/19  18:11:53  msmcq
    * change rs type=place to pubPlace
    * 
    * Revision 1.2  1993/08/19  00:01:03  msmcq
    * suppress PLACE element (sigh)
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- *****************************************************docimprt --><tagDoc id="DOCIMPRT" usage="opt"><gi tei="yes">docImprint</gi><name>document imprint</name><desc>contains the imprint statement (place and date of publication,
publisher name), as given
(usually) at the foot of a title page.</desc><attList></attList><exemplum><eg><![CDATA[<docImprint>Oxford, Clarendon Press, 1987</docImprint>]]></eg><p>Imprints may be somewhat more complex:
<eg><![CDATA[<docImprint><pubPlace>London</pubPlace>
Printed for <name>E. Nutt</>,
at <pubPlace>Royal Exchange</>;
<name>J. Roberts</> in <pubPlace>wick-Lane</>;
<name>A. Dodd</> without <pubPlace>Temple-Bar</>;
and <name>J. Graves</> in <pubPlace>St. James's-street.</>
<date>1722.</>
</docImprint>]]></eg></p></exemplum><remarks><p>Cf. the <gi tei="yes">imprint</gi> element of bibliographic
citations.  As with title, author, and editions, the shorter name is
reserved for the element likely to be used more often.</p></remarks><part type="base" name="core"/><classes names="TPPARTS FMCHUNK"/><dataDesc></dataDesc><elemDecl>- O (%phrase.seq | pubPlace | docDate | publisher)*</elemDecl><!-- < elemdecl>- O ( (#PCDATA | name | pubPlace)*,           --><!--                (docDate, (#PCDATA | name | pubPlace)*)?) --><!-- /elemdecl --><!-- Why isn't this just phrase.seq?                   (msm)  --><!-- Why dont you parse stuff after you've fiddled with it? (LB) --><xref target="DSTITL"/></tagDoc><?tei:EOF docimprt.tag ??><!-- docImprint element --><?tei:SOF doctitle.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: doctitle.tag,v $
    * Revision 1.3  1998/01/31 19:13:36  tei
    * fixed log keyword (!)
    *
    * Revision 1.2  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    * 
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- ******************************************************docTitle--><tagDoc id="DOCTITLE" usage="rec"><gi tei="yes">docTitle</gi><name>document title</name><desc>contains the title of a document, including all its
constituents, as given on a title page.</desc><attList></attList><exemplum><eg><![CDATA[        <docTitle>
        <titlePart type=main>The DUNCIAD,
        VARIOURVM.
        <titlePart type=sub>WITH THE
        PROLEGOMENA of SCRIBLERUS.
        </docTitle>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="TPPARTS FMCHUNK"/><dataDesc></dataDesc><elemDecl>- o (titlePart+)</elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF doctitle.tag ??><!-- docTitle element --><?tei:SOF domain.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	domain.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *************************************************************** domain --><tagDoc id="DOMAIN" usage="opt"><gi tei="yes">domain</gi><name>Domain of use</name><desc>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.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>categorizes the domain of use.
   </desc><datatype>CDATA
   </datatype><valList type="open"><val>art</val><desc>art and entertainment
    </desc><val>domestic</val><desc>domestic and private
    </desc><val>religious</val><desc>religious and ceremonial
    </desc><val>business</val><desc>business and work place
    </desc><val>education</val><desc>education
    </desc><val>govt</val><desc>government and law
    </desc><val>public</val><desc>other forms of public context
   </desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[        <domain type=dom>
        <domain type=rel>religious broadcast</domain>]]></eg></exemplum><remarks><p>The list presented here is primarily for illustrative
purposes.</p></remarks><part type="aux" name="corpora"/><classes/><dataDesc>Usually empty, unless some further clarification of the type
attribute is needed, in which case it may contain running
prose.</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF domain.tag ??><!-- domain element --><?tei:SOF edition.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	edition.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : change broth to phrase.seq              --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- ******************************************************edition --><tagDoc id="EDITION" usage="opt"><gi tei="yes">edition</gi><name>Edition</name><desc>describes the particularities of one edition of a text.</desc><attList></attList><exemplum><eg><![CDATA[<edition>First edition <date>Oct 1990</date>
<edition n='S2'>Students' edition]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="BIBLPART"/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="HD22"/></tagDoc><?tei:EOF edition.tag ??><!-- edition element --><?tei:SOF edstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	edstmt.tag,v $
# Revision 1.2  94/01/04  12:14:15  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 2 jan 93: LB: change phrase.seq to p+ --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- **************************************************editionStmt --><tagDoc id="EDSTMT" usage="opt"><gi tei="yes">editionStmt</gi><name>edition statement</name><desc>groups information relating to one edition of a text.</desc><attList></attList><exemplum><eg><![CDATA[<editionStmt>
  <edition n=S2>Students' edition</edition>
  <respStmt>
    <resp>Adapted by </resp><name>Elizabeth Kirk</name>
  </respStmt>
</editionStmt>]]></eg></exemplum><exemplum><eg><![CDATA[<editionStmt><p>First edition, <date>Michaelmas Term, 1991.</date>
</editionStmt>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o ( (edition, respStmt*) | p+ )</elemDecl><xref target="HD22"/><xref target="HD2"/></tagDoc><?tei:EOF edstmt.tag ??><!-- editionStmt element --><?tei:SOF editor.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	editor.tag,v $
# Revision 1.2  94/01/04  12:14:15  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-09 : MSM : normaliZe spelling                      --><!-- 92-12-09 : MSM : punctuation cleanup                     --><!-- 92-11-09 : MSM : set xrefs to HD, CObi                   --><!-- ******************************************************editor --><tagDoc id="EDITOR" usage="opt"><gi tei="yes">editor</gi><name>editor</name><desc>secondary <term>statement of responsibility</term> for a
bibliographic item, for example the name of an individual, institution
or organization, (or of several such) acting as editor, compiler,
translator, etc. </desc><attList><attDef usage="opt"><attName>role</attName><desc>specifies the nature of the intellectual responsibility</desc><datatype>CDATA</datatype><valDesc>semi-open list (examples might include: translator, editor,
        compiler, illustrator, etc.)</valDesc><default>editor</default></attDef></attList><exemplum><eg><![CDATA[<editor>Eric Johnson
<editor role=illustrator>John Tenniel]]></eg></exemplum><remarks><p>Particularly where cataloguing is likely to be based on
the content of the header, it is advisable to use generally recognized
authority lists for the exact form of personal names. </p></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc>A consistent format should be adopted</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="COBICOR"/></tagDoc><?tei:EOF editor.tag ??><!-- editor element --><?tei:SOF eddecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	eddecl.tag,v $
# Revision 1.3  94/01/04  12:14:14  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  01:59:34  msmcq
# change content model
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : change content model, normalize names   --><!-- 93-06-01 : MSM : allow trailing ps after special chunks  --><!-- ************************************************editorialDecl --><tagDoc id="EDDECL" usage="opt"><gi tei="yes">editorialDecl</gi><name>editorial practice declaration</name><desc>provides details of editorial principles and practices applied
during the encoding of a text.</desc><attList></attList><exemplum><eg><![CDATA[<editorialDecl id=E2>
  <normalization source=W9>
  <p>All words converted to Modern American spelling using
    Websters 9th Collegiate dictionary
  <quotation marks=all form=std>
  <p>All opening quotation marks converted to &odq; all closing
    quotation marks converted to &cdq;.
</editorialDecl>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o ( p+ | ((correction | normalization
       | quotation | hyphenation | interpretation
       | segmentation | stdVals)+, p*))</elemDecl><xref target="HD53"/><xref target="HD5"/><xref target="CCAS2"/></tagDoc><?tei:EOF eddecl.tag ??><!-- editorialDecl element --><?tei:SOF educn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	educn.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- **************************************************************** educn --><tagDoc id="EDUCN" usage="opt"><gi tei="yes">education</gi><name>Education</name><desc>contains a brief prose description of the
educational background of a participant.</desc><attList></attList><exemplum><eg><![CDATA[  <education>Left school at age 16]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF educn.tag ??><!-- education element --><?tei:SOF tdeg.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tdeg.tag,v $
# Revision 1.3  94/01/04  12:15:30  lou
# fix xrefs
# 
# Revision 1.2  1993/09/16  16:23:53  msmcq
# Publication of TD
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagDoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 93-09-14 : MSM : put a tag inside example                --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-04-12 : MSM : change id, filename                     --><!-- *************************************************** eg --><tagDoc id="TDEG" usage="mwa"><gi tei="yes">eg</gi><desc>contains a single example demonstrating the use of an element or
attribute. If the example contains SGML markup, it must be
enclosed within a marked CDATA section.</desc><attList></attList><exemplum><p>This example shows how an <gi tei="yes">eg</gi> element may contain a
CDATA marked section.</p><eg>  &lt;exemplum&gt;
  &lt;p&gt;The &lt;gi&gt;term&lt;/gi&gt; element may be used to mark any
  technical term:&lt;/p&gt;
  &lt;eg&gt;&lt;![ CDATA [
  This &lt;term&gt;recursion&lt;/&gt; is giving me a headache.
  ]]&gt;
  &lt;/eg&gt;
  &lt;/exemplum&gt;</eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl>- - (#PCDATA)</elemDecl><!-- odd has %soup --><xref target="TDTAG"/><xref target="TDATT"/></tagDoc><?tei:EOF tdeg.tag ??><!-- eg element (for TSD) --><?tei:SOF dieg.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	dieg.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
#  --><!-- Revisions:                                               --><!-- 94-01-15 : MSM : change remarks                          --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-13 : MSM : add formptrs to model                   --><!-- 94-01-12 : MSM : m.dicparts                              --><!-- 94-01-12 : MSM : change content model                    --><!-- ************************************************* eg       --><tagDoc id="DIEG" usage="rec"><gi tei="yes">eg</gi><name>example (exempli gratia)</name><desc>(in a dictionary) contains an example text containing at least one
occurrence of the word form, used in the sense being described; examples
may be quoted from (named) authors or contrived.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>In some dictionaries the quoted example may be followed by a
bibliographic citation for the source; this citation may be tagged with
the tags described in section <xref target="COBI" type="div2"/>.
The quotation and the indication of its source should be enclosed in
a <gi tei="yes">cit</gi> element.</p></remarks><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS DIGLOBAL"/><dataDesc>May contain a quotation, pronunciation, definition, or
translation information.<!--  - -  (#PCDATA | %dleaves; | %dgroups;)*   -(entry)      --></dataDesc><elemDecl>- O  (q | quote | cit)+ +(%m.dictionaryParts | %m.formPointers)</elemDecl><xref target="DITPEG" type="div2"/></tagDoc><?tei:EOF dieg.tag ??><!-- eg element --><?tei:SOF eleaf.tag ??><!-- ********** ElEAF                                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	eleaf.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/09  19:01:42  msmcq
# add RCS id, log
# --><!-- ********** ElEAF                                         --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version:                      --><!--                  replace LABEL and FS content by value=  --><!--                      and label=                          --><!--                  eliminate ECHO from content model       --><!-- ********** ElEAF                                         --><tagDoc id="ELEAF" usage="opt"><gi tei="yes">eLeaf</gi><name>Leaf of an embedding tree.</name><desc>provides explicitly for a leaf of an embedding tree, which may also
be encoded with the <gi tei="yes">eTree</gi> element.</desc><attList><attDef usage="opt"><attName>label</attName><desc>gives a label for a leaf of an embedding tree.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef usage="rwa"><attName>value</attName><desc>provides the value of an embedding leaf, which is a feature
structure or other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier of a feature structure or other analytic
element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<eLeaf label='with' value=fswith>]]></eg></exemplum><remarks><p>The <gi tei="yes">eTree</gi> tag may be used if the encoder does not
wish to distinguish by name between nonleaf  and leaf nodes in
embedding trees; they are distinguished by their arrangement.</p></remarks><part type="top" name="graphs"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="GDAT" type="div2"/></tagDoc><?tei:EOF eleaf.tag ??><!-- eLeaf element --><?tei:SOF elemdecl.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : change dataDesc, give 2d example        --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	elemdecl.tag,v $
# Revision 1.4  94/01/04  12:14:16  lou
# fix xrefs
# 
# Revision 1.3  1993/09/16  15:07:52  msmcq
# Publication of TD
#
# Revision 1.2  1993/08/13  20:49:56  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** elemDecl --><tagDoc id="ELEMDECL" usage="opt"><gi tei="yes">elemDecl</gi><name>element declaration</name><desc>contains the full form of an SGML declaration for the element
documented using the reference concrete syntax.</desc><attList></attList><exemplum><p>The contents of this element are usually surrounded by a CDATA
marked section, which prevents the markup-declaration-open delimiter
(<q>&lt;!</q>) at the beginning of the element content from being
recognized by the SGML parser (and thus causing an error).</p><eg>&lt;elemDecl&gt;
&lt;![ CDATA [
&lt;!ELEMENT list - - (head?, ((item*)
                   | (head.label?, head.item?,
                   (label, item)+)))  &gt;
]]&gt;
&lt;/elemDecl&gt;</eg><p>The markup-declaration-open delimiter can however also be given as
(or be interrupted by) an entity reference:
<eg><![CDATA[<elemDecl>
&lt;!ELEMENT list - - (head?, ((item*)
                   | (head.label?, head.item?,
                   (label, item)+)))  >
</elemDecl>]]></eg></p></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>The declaration must be enclosed with a CDATA marked section,
or else the opening delimiter must be given by an entity reference.</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><xref target="TDTAG"/></tagDoc><?tei:EOF elemdecl.tag ??><!-- elemDecl element --><?tei:SOF emph.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	emph.tag,v $
# Revision 1.3  94/01/04  12:14:18  lou
# fix xrefs
# 
# Revision 1.2  1993/10/29  10:34:58  lou
# Changed content model to %paraContent
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************************** emph --><tagDoc id="EMPH" usage="rwa"><gi tei="yes">emph</gi><name>emphasized</name><desc>marks words or phrases which are stressed or emphasized for
linguistic or rhetorical effect.</desc><attList></attList><exemplum><eg><![CDATA[You took the car and did <emph>what</emph>?!!]]></eg></exemplum><exemplum><eg><![CDATA[<q>What it all comes to is this,</q> he said. <q><emph>What
does Christopher Robin do in the morning nowadays?</emph></q>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc>free prose</dataDesc><elemDecl>- -  (%paraContent;)</elemDecl><xref target="COHQHE"/><xref target="COHQH"/></tagDoc><?tei:EOF emph.tag ??><!-- emph element --><?tei:SOF encdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	encdesc.tag,v $
# Revision 1.4  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.3  1994/01/28  18:59:34  lou
# add metdecl and fsddecl
#
# Revision 1.2  1994/01/04  12:14:19  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : add variantEncoding (fix VARENCOD)      --><!-- 20 Jan 94 : add fsdDecl and metDecl --><!-- 93-06-01 : MSM : allow declarable elements to repeat:    --><!-- 93-06-01 : MSM : projdesc, eddecl, classdecl             --><!-- 93-06-01 : MSM : add p at end of specialized-chunk seq,  --><!--                  then resolve resulting ambiguity by     --><!--                  deleting the leading (p+) |             --><!-- 93-06-01 : MSM : add tagsDecl to content model, post Eynsham --><!-- *************************************************encodingDesc --><tagDoc id="ENCDESC" usage="rec"><gi tei="yes">encodingDesc</gi><name>Encoding description</name><desc>documents the relationship between an electronic text and the
source or sources from which it was derived.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- - (projectDesc*, samplingDecl*, editorialDecl*,
              tagsDecl?, refsDecl*, classDecl*, metDecl*, fsdDecl*,
              variantEncoding*, p*)</elemDecl><xref target="HD5"/><xref target="HD11"/></tagDoc><?tei:EOF encdesc.tag ??><!-- encodingDesc element --><?tei:SOF entdoc.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : close valList on TYPE                   --><!-- 93-09-10 : MSM : valList type closed                     --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	entdoc.tag,v $
# Revision 1.3  94/01/04  12:14:21  lou
# fix xrefs
# 
# Revision 1.2  1993/09/16  15:07:52  msmcq
# Publication of TD
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** entDoc --><tagDoc id="ENTDOC" usage="rwa"><gi tei="yes">entDoc</gi><name>entity documentation</name><desc>formally documents a single SGML entity within an encoding scheme.</desc><attList><attDef usage="req"><attName>type
 </attName><desc>indicates whether this is a general or a parameter entity.
 </desc><datatype>(pe | ge)
 </datatype><valList type="closed"><val>pe</val><desc>parameter entity
  </desc><val>ge</val><desc>general entity
 </desc></valList><default>#REQUIRED
 </default></attDef></attList><exemplum><eg><![CDATA[<entDoc id=EXTPTR type=pe>
<entName>extPtr</entName>
<rs>extended-pointer expression</rs>
<desc>used as the declared value of an attribute, indicates that all
values of that attribute must be valid expressions in the TEI extended
pointer notation.
<string>'CDATA'</string>
<ptr target=SAXR1>
</entDoc>]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl>- - (entName, rs?, desc, remarks?, string, ptr*, equiv*)</elemDecl><xref target="TDENT"/><xref target="TD"/></tagDoc><?tei:EOF entdoc.tag ??><!-- entDoc element --><?tei:SOF wsdents.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdents.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ********************************************** entitySet --><tagDoc id="WSDENTS" usage="opt"><gi tei="yes">entitySet</gi><name>base entity set</name><desc>identifies a public or private entity set whose mappings between
entity names and characters are to be incorporated (perhaps with
modifications) into this writing system declaration.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Reference in a WSD to an entity set makes the set of
entity-name-to-character mappings defined in the entity set available
for use in text to which the WSD applies.  Unless the
character-to-entity-name mappings are modified by the
<gi tei="yes">exceptions</gi> element, any name in the entity set referred to may
be used with its standard meaning in any text to which the WSD applies.
 </p><p>Since standard public entity sets are not always completely explicit
about the distinctions among characters, glyphs, graphemes, and
allographs, the TEI will provide standard writing system declarations
which explicitly document the mappings provided by some commonly used
public entity sets; it is recommended that similar documentation be
provided for locally developed entity sets.
 </p></remarks><part type="aux" name="wsd"/><classes names="BASESTD"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="WDCSBA"/></tagDoc><?tei:EOF wsdents.tag ??><!-- entitySet element --><?tei:SOF entname.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- 93-09-11 : MSM : correct content model to PCDATA         --><!--                  (was (NAME))                            --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	entname.tag,v $
# Revision 1.3  93/09/16  15:07:52  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:49:56  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** entName --><tagDoc id="ENTNAME" usage="mwa"><gi tei="yes">entName</gi><name>entity name</name><desc>contains the full name of an entity, excluding the percent sign in
the case of a parameter entity.</desc><attList></attList><exemplum><eg><![CDATA[<entName>component.seq]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>Must be a valid SGML name.</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><xref target="TDENT"/></tagDoc><?tei:EOF entname.tag ??><!-- entName element --><?tei:SOF entry.tag ??><!-- Revisions:                                               --><!-- 94-01-15 : MSM : allow end-tag omission                  --><!-- 94-01-12 : MSM : add anchor as inclusion exception       --><!-- 94-01-12 : MSM : add to compdict class                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	entry.tag,v $
# Revision 1.3  94/01/18  16:41:59  msmcq
# revisions for P3; see commments for details
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************* entry       --><tagDoc id="ENTRY" usage="mwa"><gi tei="yes">entry</gi><desc>contains a reasonably well-structured dictionary entry.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Like all elements, <gi tei="yes">entry</gi> inherits an <att tei="yes">id</att> attribute
from the class <term>global</term>.  No restrictions are placed on the
method used to construct <att tei="yes">id</att>s; one convenient method is to use
the orthographic form of the headword, appending a disambiguating number
where necessary.  Identification codes are sometimes included on
machine-readable tapes of dictionaries for in-house use.
 </p></remarks><part type="base" name="dict"/><classes names="ENTRIES COMPDICT"/><dataDesc>Like all dictionary grouping tags, <gi tei="yes">entry</gi> may contain
character data mixed with any other elements defined in the dictionary
tag set.</dataDesc><elemDecl>- O (hom | sense | %m.dictionaryTopLevel)+ +(anchor)</elemDecl><xref target="DIBO" type="div2"/><xref target="DIEN" type="div2"/></tagDoc><?tei:EOF entry.tag ??><!-- entry element --><?tei:SOF entryfr.tag ??><!-- Revisions:                                               --><!-- 94-03-30 : MSM : suppress anchor in inclusion exception, --><!-- 94-03-30 : MSM : since anchor is member of phrase class  --><!-- 94-01-15 : MSM : cosmetic change to model                --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : remove from class ditoplev              --><!-- 94-01-12 : MSM : correct model error introduced in last change --><!-- 94-01-12 : MSM : add anchor as inclusion exception       --><!-- 94-01-12 : MSM : add core elements to inclusion exceptn  --><!-- 94-01-12 : MSM : change desc                             --><!-- 94-01-12 : MSM : suppress dgroups class                  --><!-- 93-10-19 : MSM : normalize name                          --><!-- 93-10-19 : MSM : add to class compdict                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	entryfr.tag,v $
# Revision 1.4  94/04/01  17:36:34  msmcq
# changes while validating DTD
# 
# Revision 1.3  1994/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
#
# Revision 1.2  1994/01/04  00:37:58  msmcq
# first cut at DI revisions
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ********************************************** entryFree --><tagDoc id="ENTRYFR" usage="mwa"><gi tei="yes">entryFree</gi><desc>contains a dictionary entry which does not necessarily conform
to the constraints imposed by the <gi tei="yes">entry</gi> element.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="COMPDICT ENTRIES DIGLOBAL"/><dataDesc>May contain any dictionary elements in any combination.</dataDesc><elemDecl>- O  (#PCDATA)
+(%m.dictionaryParts | %m.phrase | %m.inter)</elemDecl><xref target="DIBO"/><xref target="DIEN"/></tagDoc><?tei:EOF entryfr.tag ??><!-- entryFree element --><?tei:SOF epigraph.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: epigraph.tag,v $
    * Revision 1.7  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.6  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.5  94/03/15  11:10:33  lou
    * minor typos etc
    * 
    * Revision 1.4  1994/01/05  16:51:23  lou
    * fix typo
    * 
    * Revision 1.3  1994/01/04  12:14:22  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/11/30  16:19:28  lou
    * fixed typo in content model
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- *****************************************************epigraph --><!-- 2 jan 94: LB : change content model to componentSeq --><tagDoc id="EPIGRAPH" usage="opt"><gi tei="yes">epigraph</gi><name>epigraph</name><desc>contains a quotation, anonymous or attributed, appearing at
the start of a section or chapter, or on a title page. </desc><attList></attList><exemplum><eg><![CDATA[<epigraph lang=lat>
<cit><bibl>Lucret.</bibl>
<quote><l part=f>petere inde coronam,
</l><l>Vnde prius nulli velarint tempora Musae.
</l></quote></cit>
</epigraph>]]></eg></exemplum><!-- Jonson, Alchemist, 1616 --><remarks></remarks><part type="base" name="core"/><classes names="DIVTOP TPPARTS DIVBOT FMCHUNK"/><elemDecl>- - (%component.seq;)</elemDecl><xref target="DSCO"/><xref target="DSDTB"/><xref target="DSTITL"/></tagDoc><?tei:EOF epigraph.tag ??><!-- epigraph element --><?tei:SOF epilogue.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: epilogue.tag,v $
    * Revision 1.7  1998/02/09 18:02:36  tei
    * fix egs
    *
    * Revision 1.6  94/01/04  12:14:22  lou
    * fix xrefs
    * 
    * Revision 1.5  1993/08/23  16:35:10  msmcq
    * correct content models for publication of DR
    * 
    * Revision 1.4  1993/08/13  20:49:57  msmcq
    * Clean ^Z
    * 
    * Revision 1.3  1993/08/12  21:31:15  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.2  1993/08/03  02:00:07  msmcq
    * fix MS end problem
    * --><!-- Revisions:                                               --><!-- 93-08-18 : MSM : correct m.component to component        --><!-- 93-08-07 : MSM : loosen content model as with prologue   --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- *********************************************** epilogue --><tagDoc id="EPILOGUE" usage="mwa"><gi tei="yes">epilogue</gi><desc>contains the epilogue to a drama,  typically spoken by an actor
out of character, possibly in association with a particular performance
or venue.</desc><attList></attList><exemplum><eg><![CDATA[<epilogue>
<head>Written by <name>Colley Cibber, Esq</name>
and spoken by <name>Mrs. Cibber</name>
<sp>
<lg type=couplet>
<l>Since Fate has robb'd me of the hapless Youth,</l>
<l>For whom my heart had hoarded up its truth;</l></lg>
<lg><l>By all the Laws of Love and Honour, now,</l>
<l>I'm free again to chuse, &mdash; and one of you</l>
</lg>
<!-- ... -->
<lg type=triplet><l>Suppose I search the sober Gallery; -- No,</l>
<l>There's none but Prentices &mdash; & Cuckolds all a row:</l>
<l>And these, I doubt, are those that make 'em so.</l></lg>
<stage>Pointing to the Boxes.</stage>
<lg type=couplet>
<l>'Tis very well, enjoy the jest:</l>
<!-- ... --></lg>
</sp>
</epilogue>]]></eg><!-- G. Lillo, The London Merchant  (1731) --></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes names="DRFRONT"/><dataDesc>Contains optional headings, a sequence of one or
more component-level elements, and an optional sequence of
closing material.</dataDesc><elemDecl>- - ((%m.divtop)*, (%component)+, (%m.divbot)*)</elemDecl><!-- was  - - (%divtop, sp, %divbot ) --><xref target="DRPRO" type="div3"/><xref target="DRFAB" type="div3"/></tagDoc><?tei:EOF epilogue.tag ??><!-- epilogue element --><?tei:SOF equipmen.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	equipmen.tag,v $
# Revision 1.2  94/01/04  12:14:23  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************************equipment --><tagDoc id="EQUIPMEN" usage="opt"><gi tei="yes">equipment</gi><name>equipment</name><desc>provides technical details of the equipment and media used for
an audio or video recording used as the source for a spoken text.</desc><attList></attList><exemplum><eg><![CDATA[  <equipment>
     <p>"Hi-8" 8 mm NTSC camcorder with integral directional
     microphone and windshield and stereo digital sound
     recording channel.
  </equipment>]]></eg></exemplum><exemplum><eg><![CDATA[  <equipment>
    <p>8-track analogue transfer mixed down to 19 cm/sec audio
    tape for cassette mastering
  </equipment>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD32"/><xref target="CCAS2"/></tagDoc><?tei:EOF equipmen.tag ??><!-- equipment element --><?tei:SOF equiv.tag ??><!-- Revisions:                                               --><!-- 93-09-11 : MSM : rename mlang as scheme, revise desc     --><!-- 93-09-10 : MSM : cosmetic                                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	equiv.tag,v $
# Revision 1.4  94/04/05  14:24:24  lou
# seriously abbreviate exemplum to fix oddp2x oddity
# 
# Revision 1.3  1994/01/04  12:14:24  lou
# fix xrefs
#
# Revision 1.2  1993/09/16  15:07:52  msmcq
# Publication of TD
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** equiv --><tagDoc id="EQUIV" usage="opt"><gi tei="yes">equiv</gi><desc>specifies an equivalent or comparable element in some other
markup language.</desc><attList><attDef usage="req"><attName>scheme
 </attName><desc>names the markup language or encoding scheme
 </desc><datatype>CDATA
 </datatype><valDesc>any phrase identifying a markup language
 </valDesc><default>#REQUIRED
 </default></attDef></attList><exemplum><eg><![CDATA[   <equiv mlang=LaTeX>\para</>]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes/><dataDesc>If the other markup language uses SGML-significant characters,
a CDATA marked section should be used.</dataDesc><elemDecl>- O (%specialPara)</elemDecl><!-- was soup --><xref target="TDTAG"/><xref target="TDATT"/><xref target="TDCLA"/><xref target="TDENT"/></tagDoc><?tei:EOF equiv.tag ??><!-- equiv element --><?tei:SOF etree.tag ??><!-- ********** EtREE                                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	etree.tag,v $
# Revision 1.5  93/09/22  19:08:20  msmcq
# version as of publication of GD
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/09  19:01:42  msmcq
# add RCS id, log
# --><!-- ********** EtREE                                         --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : suppress extraneous end-tag in eg       --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version:                      --><!--                  replace LABEL and FS content by value=  --><!--                     and label=                           --><!--                  eliminate ECHO from content model       --><!-- ********** EtREE                                         --><tagDoc id="ETREE" usage="opt"><gi tei="yes">eTree</gi><name>embedding tree</name><desc>provides an alternative to <gi tei="yes">tree</gi> element for representing
ordered rooted tree structures.</desc><attList><attDef usage="rwa"><attName>label</attName><desc>gives a label for an embedding tree.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef usage="rwa"><attName>value</attName><desc>provides the value of an embedding tree, which is a feature
structure or other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier of a feature structure or other analytic
element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<eTree n='ex1' label=PP>
   <eTree label=P><eLeaf label=with></eTree>
   <eTree label=NP>
      <eTree label=Art><eLeaf label=the></eTree>
      <eTree label=N><eLeaf label=periscope></eTree>
      </eTree>
   </eTree>]]></eg></exemplum><part type="top" name="graphs"/><classes names="CHUNK"/><dataDesc>zero or
more embedding trees, triangles, or embedding leafs.</dataDesc><elemDecl>- - ((eTree |  triangle | eLeaf )*)</elemDecl><xref target="GDAT" type="div2"/></tagDoc><?tei:EOF etree.tag ??><!-- eTree element --><?tei:SOF etym.tag ??><!-- Revisions:                                               --><!-- 94-01-15 : MSM : allow end-tag omission                  --><!-- 94-01-14 : MSM : correct example                         --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : add xr to model                         --><!-- 94-01-12 : MSM : morphInfo not morph                     --><!-- 94-01-12 : MSM : add usg, lbl to model                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: etym.tag,v $
    * Revision 1.3  1999/02/22 15:56:37  tei
    * fix comments
    *
   * Revision 1.2  1994/01/15 20:53:57  msmcq
   * msmcq revision of DI for P3.  Consult comments for details.

    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    * --><!-- ************************************************* etym       --><tagDoc id="ETYM" usage="rec"><gi tei="yes">etym</gi><name>etymology</name><desc>encloses the etymological information in a dictionary entry.</desc><attList></attList><exemplum><eg><![CDATA[<entry>
    <form><orth>publish</orth> ... </form>
    <etym>ME. <mentioned>publisshen</>, F. <mentioned>publier</>,
        L. <mentioned>publicare, publicatum</>.
        <xr>See <ref>public</>; cf. 2d <ref>-ish</>.</xr>
    </etym>
    <!-- ... -->
</entry>]]>
(From:  <citation>Webster's Second International</citation>)</eg></exemplum><remarks><p>There is no consensus on the internal structure of etymologies,
ore even on whether there is a standard internal structure.  The
<gi tei="yes">etym</gi> tag accordingly simply contains prose, within which names
of languages, cited words, glosses, and examples will typically be
prominent.  The tagging of such internal objects is optional.</p></remarks><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS DIGLOBAL"/><dataDesc>May contain character data mixed with any other elements
defined in the dictionary tag set.</dataDesc><elemDecl>- O  (%paraContent | usg | lbl | def | trans | tr |
(%m.morphInfo) | eg | xr)*</elemDecl><xref target="DITPET" type="div2"/></tagDoc><?tei:EOF etym.tag ??><!-- etym element --><?tei:SOF event.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	event.tag,v $
# Revision 1.5  94/04/01  17:36:34  msmcq
# changes while validating DTD
# 
# Revision 1.4  1994/02/17  21:06:08  msmcq
# make WHO attribute inherit, as per text (for SC version of P3)
#
# Revision 1.3  1994/01/04  12:14:24  lou
# fix xrefs
#
# Revision 1.2  1993/09/21  11:08:33  lou
# added to spokenm class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 94-02-14 : MSM : change desc                             --><!-- 94-02-14 : MSM : make who INHERITED                      --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************** event --><tagDoc id="EVENT" usage="rec"><gi tei="yes">event</gi><name>Event</name><desc>any phenomenon or occurrence, not necessarily vocalized or
communicative, for example incidental noises or other events affecting
communication.</desc><attList><attDef usage="opt"><attName>who</attName><desc>supplies an identifier for the agent of the event described,
         if any.
         Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
         or <tag compl="full" tei="yes">participant.grp</tag> element in the TEI header.</desc><datatype>IDREF</datatype><valDesc>Must identify a participant or participant group within the
       TEI Header</valDesc><default>%INHERITED</default></attDef><attDef usage="opt"><attName>iterated</attName><name>iterated</name><desc>indicates whether or not the phenomenon is repeated.</desc><datatype>(y | n | u)</datatype><valList type="open"><val>y </val><desc>the phenomenon is repeated.
    </desc><val>n </val><desc>the phenomenon is atomic.
    </desc><val>u </val><desc>unknown or unmarked.</desc></valList><default>n</default><remarks></remarks></attDef><attDef usage="opt"><attName>desc</attName><name>description</name><desc>supplies a conventional representation for the
    phenomenon.</desc><datatype>CDATA</datatype><valDesc>a description or representation of the phenomenon chosen
    from a semi-closed list</valDesc><default>#IMPLIED</default><remarks></remarks></attDef></attList><exemplum><eg><![CDATA[    <event desc="ceiling collapses">]]></eg></exemplum><remarks></remarks><part type="base" name="ts"/><classes names="COMPSPOK TIMED"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TSBAFD"/><xref target="TSBA"/><xref target="TSBAVO"/></tagDoc><?tei:EOF event.tag ??><!-- event element --><?tei:SOF exceptns.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	exceptns.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ********************************************* exceptions --><tagDoc id="EXCEPTNS" usage="opt"><gi tei="yes">exceptions</gi><desc>documents ways in which a writing system declaration differs from
the coded character sets, base writing system declarations, and entity
sets which form its bases.</desc><attList></attList><exemplum><eg><![CDATA[ <eclaration
     name='-//TEI P2: 1993//WSD TLG Beta code//en'
     date='1993-06-01'>
 <!-- ... -->
 <characters>
     <baseWsd name='-//TEI P2: 1993//WSD ISO 646 IRV//en'
              authority='TEI'>
     <exceptions>
        <character> ... </character>
        <character> ... </character>
        <character> ... </character>
        <!-- ... -->
     </exceptions>
 </characters>]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>Contains a series of <gi tei="yes">character</gi> elements, each
documenting one character unit of the writing system.</dataDesc><elemDecl>- O  (character*)</elemDecl><xref target="WDCSEX"/></tagDoc><?tei:EOF exceptns.tag ??><!-- exceptions element --><?tei:SOF exemplum.tag ??><!-- Revisions:                                               --><!-- 93-09-11 : MSM : fix example                             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	exemplum.tag,v $
# Revision 1.4  94/01/04  12:14:25  lou
# fix xrefs
# 
# Revision 1.3  1993/09/16  15:07:52  msmcq
# Publication of TD
#
# Revision 1.2  1993/08/13  20:49:58  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** exemplum --><tagDoc id="EXEMPLUM" usage="rwa"><gi tei="yes">exemplum</gi><desc>contains a single example demonstrating the use of an element,
together with optional paragraphs of commentary.</desc><attList></attList><exemplum><eg>  &lt;exemplum&gt;
   &lt;p&gt;The &lt;gi&gt;name&lt;/gi&gt; element can be used for both
   personal names and place names:&lt;/p&gt;
   &lt;eg&gt;
     &lt;![ CDATA [
     &lt;q&gt;My dear &lt;name type=person&gt;Mr. Bennet&lt;/name&gt;,&lt;/q&gt;
     said his lady to him one day, &lt;q&gt;have you heard that
     &lt;name type=place&gt;Netherfield Park&lt;/name&gt; is let
     at last?&lt;/q&gt;
     ]]&gt;
   &lt;/eg&gt;
   &lt;p&gt;As shown, the &lt;att&gt;type&lt;/att&gt; attribute may be used
   to distinguish the one from the other.
  &lt;/exemplum&gt;</eg><!-- OK wise guy, so how *do* I get this example tagged legal? --><!-- Make the enclosing CDATA marked section RCDATA           --><!-- instead, and use &nil inside the embedded msc (]]>) to   --><!-- keep the parser from recognizing the msc.  Nothing       --><!-- needs to be done about the embedded CDATA marked         --><!-- section opener, since it will be ignored within an       --><!-- RCDATA marked section. (msm)                             --><p>Note that an explicit end-tag must be supplied for the
paragraph immediately preceding the <gi tei="yes">eg</gi> element within an
<gi tei="yes">exemplum</gi>, to prevent the <gi tei="yes">eg</gi> from being mistaken for
part of the paragraph.</p></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl>- - (p*, eg, p*)</elemDecl><xref target="TDTAG"/></tagDoc><?tei:EOF exemplum.tag ??><!-- exemplum element --><?tei:SOF expan.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: expan.tag,v $
    * Revision 1.3  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.2  94/01/04  12:14:26  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : suppress membership in edit class       --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- ******************************************************* expan --><tagDoc id="EXPAN" usage="opt"><gi tei="yes">expan</gi><name>expansion</name><desc>contains the expansion of an abbreviation.</desc><attList><attDef usage="opt"><attName>abbr</attName><name>abbreviation</name><desc>gives the abbreviation in its unexpanded form.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ The address is Southmoor <expan abbr='Rd'>Road</expan>.]]></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>signifies the editor or transcriber responsible for supplying 
the expansion of the abbreviation held as the content of the 
<gi tei="yes">expan</gi> element.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document 
header, associated with a person asserted as responsible for some 
aspect of the text's creation, transcription, editing or encoding 
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ The address is Southmoor <expan abbrev='Rd' resp=LB>Road</>.]]></eg></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the expansion of 
the abbreviation.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><attDef usage="opt"><attName>type</attName><desc>allows the encoder to classify the abbreviation according to 
some
convenient typology.</desc><datatype>CDATA</datatype><valDesc>any useful classification name, e.g. <q>suspension</q>,
<q>contraction</q>, <q>brevigraph</q>, <q>title</q>,
<q>organization</q>, <q>geographic</q>, etc.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>The <att tei="yes">type</att> attribute is provided for the sake of
those who wish to classify abbreviations at their point of  occurrence;
this may be useful in some circumstances, though usually the same
abbreviation will have the same type in all occurrences.  As the 
sample values make clear, abbreviations may be classified by the method
used  to construct them, the method of writing them, or the referent of
the  term abbreviated; the typology used is up to the encoder and
should be carefully planned to meet the needs of the expected use.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>This tag is the mirror image of the <gi tei="yes">abbr</gi> tag; 
both allow the encoder to transcribe both an abbreviation and its 
expansion. In <gi tei="yes">abbr</gi>, however, the original is transcribed as
the content  of the element and the expansion as an attribute value;
<gi tei="yes">expan</gi> reverses this.	The choice between the two is up to the
user. </p><p>The <gi tei="yes">expan</gi> tag is not required; if appropriate, the 
encoder may expand abbreviations in the source text silently, without
tagging them.  If this is done, the TEI header should so indicate.</p></remarks><part type="top" name="core"/><classes names="DATA"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="CONAAB" type="div3"/></tagDoc><?tei:EOF expan.tag ??><!-- expan element --><?tei:SOF extent.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	extent.tag,v $
# Revision 1.2  94/01/04  12:14:27  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- *******************************************************extent --><tagDoc id="EXTENT" usage="opt"><gi tei="yes">extent</gi><desc>describes the approximate size of the electronic text as stored on
some carrier medium, specified in any convenient units.</desc><attList></attList><exemplum><eg><![CDATA[<extent>3200 sentences
<extent>between 10 and 20 Mb
<extent>ten 3.5 inch high density diskettes]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="BIBLPART"/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq; )</elemDecl><xref target="HD23"/><xref target="HD2"/><xref target="COBICOI"/></tagDoc><?tei:EOF extent.tag ??><!-- extent element --><?tei:SOF wsdxfig.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdxfig.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ********************************************** extFigure --><tagDoc id="WSDXFIG" usage="opt"><gi tei="yes">extFigure</gi><name>external figure</name><desc>(in a writing system declaration) refers to a figure or
illustration depicting the character form, which is stored in
some declared notation external to the text.</desc><attList><!-- ............................................... notation --><attDef usage="req"><attName>notation</attName><desc>identifies the notation in which the figure is stored.</desc><datatype>NAME</datatype><valDesc>a valid SGML name associated with a given notation by means of
an SGML NOTATION declaration in the document type definition.</valDesc><default>#REQUIRED</default><remarks><p></p></remarks></attDef><!-- ................................................. entity --><attDef usage="req"><attName>entity</attName><desc>gives the SGML name of the external entity which contains the
figure.</desc><datatype>ENTITY</datatype><valDesc>a valid SGML name associated with the external entity by means
of an SGML ENTITY declaration in the document type definition.</valDesc><default>#REQUIRED</default><remarks><p></p></remarks></attDef></attList><exemplum><p>An image of the character form may be stored and
transmitted in any desired graphics format.  The declaration of the
notation may specify a local system identifier for the processor (here
it is imagined that we use a program called <q>pddraw.exe</q> to process
files in TIFF format), thus:</p><eg><![CDATA[ <!-- in the DTD: -->
 <!NOTATION TIFF system 'pddraw.exe'>
 <!ENTITY lcthorn system 'lcthorn.TIF' NDATA TIFF>
 
 <!-- in the WSD itself: -->
 <extFigure notation=TIFF entity='lcthorn'>
 ]]></eg></exemplum><exemplum><p>The graphics format might also be declared with a public
identifier in addition to the system identifier; this is likely to be
more comprehensible and thus more useful to users of a different
system:</p><eg><![CDATA[ <!-- in the DTD: -->
 <!NOTATION TIFF
            PUBLIC '-//XXX//NOTATION Tagged Image File Format//EN'
            'pddraw.exe'>
 <!ENTITY lcthorn system 'lcthorn.TIF' NDATA TIFF>
 
 <!-- in the WSD itself: -->
 <extFigure notation=TIFF entity='lcthorn'>
 ]]></eg></exemplum><exemplum><p>Character shapes may be conveniently conveyed in forms
other than graphics images; one might, for example, define a character
shape using a font-design program such as Donald Knuth's MetaFont
program (which can be used to generate fonts for processing with TeX):</p><eg><![CDATA[ <!-- in the DTD: -->
 <!NOTATION metafont
            PUBLIC '-//DEK//NOTATION MetaFont//EN'
            'mf.exe'>
 <!ENTITY lcthorn system 'lcthorn.TIF' NDATA metafont>
 
 <!-- in the WSD itself: -->
 <extFigure notation=metafont entity='lcthorn'>]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="WDCSEX"/></tagDoc><?tei:EOF wsdxfig.tag ??><!-- extFigure element (for WSD) --><?tei:SOF f.tag ??><!-- ************************************************************ --><!-- TAGDOC for F                                                 --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	f.tag,v $
# Revision 1.3  94/01/04  00:39:28  msmcq
# change model (DFT name clash)
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-01-03 : MSM : change elemdecl:  dft, not default      --><!-- 93-12-20 : MSM : add valdesc                             --><!-- 93-09-22 : MSM : extract from bulk revision file         --><!-- ************************************************************ --><tagDoc id="F" usage="rwa"><gi tei="yes">f</gi><name>Feature</name><desc>associates a name with a value of any of several different types.</desc><attList><attDef id="FNAME" usage="req"><attName>name</attName><desc>provides a name for a feature.</desc><datatype>NMTOKEN</datatype><valDesc>A name token.</valDesc><default>#REQUIRED</default></attDef><attDef id="FORG" usage="rwa"><attName>org</attName><desc>indicates organization of given value or values as singleton, set,
bag or list.</desc><datatype>(single|set|bag|list)</datatype><valList type="closed"><val>single </val><desc>indicates that the given value is a singleton.
   </desc><val>set    </val><desc>indicates that the given values are organized as a
set.
   </desc><val>bag    </val><desc>indicates that the given values are organized as a
bag (multiset).
   </desc><val>list   </val><desc>indicates that the given values are organized as a
list.</desc></valList><default>#IMPLIED</default><remarks><p>If the <att tei="yes">org=single</att> attribute value is specified and
more than one value for the feature is given, then only the first value
is used.</p></remarks></attDef><attDef id="FREL" usage="req"><attName>rel</attName><desc>indicates the relation between the values that are given as the
content of the feature or pointed at by the <att tei="yes">fVal</att> attribute and
the actual values of the feature.</desc><datatype>(eq|ne|sb|ns)</datatype><valList type="closed"><val>eq     </val><desc>indicates that the given values are the actual
values.
   </desc><val>ne     </val><desc>indicates that the given values are not the actual
values.
   </desc><val>sb     </val><desc>indicates that the given values are a subset, subbag
or sublist of the actual values.
   </desc><val>ns     </val><desc>indicates that the given values are not a subset,
subbag or sublist of the actual values.</desc></valList><default>eq</default><remarks><p>If <att tei="yes">org=single</att>, then <att tei="yes">rel=sb</att> is
equivalent to <att tei="yes">rel=eq</att>, and <att tei="yes">rel=ns</att> is equivalent to
<att tei="yes">rel=ne</att>.</p></remarks></attDef><attDef id="FFVAL" usage="opt"><attName>fVal</attName><desc>points to the <att tei="yes">id</att> attributes of feature values.</desc><datatype>IDREFS</datatype><valDesc>one or more legal SGML identifiers.</valDesc><default>#IMPLIED</default><remarks><p>May be used instead of content.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<f name=gender><sym value=feminine></f>]]></eg></exemplum><remarks><p>If content is empty and no <att tei="yes">fVal</att> attribute is
present, then value is that specified by <gi tei="yes">default</gi>.</p><p>Content is defined as (null | (%mVal;)*) in FS3.dtd.
The entity %mVal; is defined as "%aVal; | %dVal;" in FS3.dtd.
%aVal; is defined as "plus | minus | any | none | dft | uncertain".
%dVal; is defined as "%cVal; | fs".
Finally, %cVal; is defined as "sym | nbr | msr | rate | str | vAlt |
alt",</p></remarks><part type="top" name="fs"/><classes/><dataDesc>Exactly one null value, or zero or more values other than null.</dataDesc><elemDecl>- O (null | (plus | minus | any | none | dft | uncertain |
sym | nbr | msr | rate | str | vAlt | alt | fs)*)</elemDecl><xref target="FSBI" type="div3"/></tagDoc><?tei:EOF f.tag ??><!-- f element      --><?tei:SOF factual.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	factual.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- 93-03-08 : MSM : suppress empty name element             --><!-- ******************************************************* factual --><tagDoc id="FACTUAL" usage="opt"><gi tei="yes">factuality</gi><desc>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. </desc><attList><attDef usage="opt"><attName>type
   </attName><desc>categorizes the factuality of the text.
   </desc><datatype>(fiction|fact|mixed|inapplicable)
   </datatype><valList type="closed"><val>fiction</val><desc>the text is to be regarded as entirely imaginative
  </desc><val>fact</val><desc>the text is to be regarded as entirely informative or factual
  </desc><val>mixed</val><desc>the text contains a mixture of fact and fiction
  </desc><val>inapplicable</val><desc>the fiction/fact distinction is not regarded
    as helpful or appropriate to this text
   </desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <factuality type=fiction>]]></eg></exemplum><exemplum><eg><![CDATA[  <factuality type=mixed>contains a mixture of gossip and
    speculation about real people and events]]></eg></exemplum><remarks><p>For many literary texts, a simple binary opposition between
 <q>fiction</q>
and <q>fact</q> is na&iuml;ve in the extreme; this parameter is not intended
for purposes of subtle literary analysis, but as a simple means of
characterising the claimed fictiveness of a given text. No claim is made
that works characterised as <q>fact</q> are in  any sense <q>true</q>.</p></remarks><part type="aux" name="corpora"/><classes/><dataDesc>Usually empty, unless some further clarification of the type
attribute is needed, in which case it may contain running prose</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF factual.tag ??><!-- factuality element --><?tei:SOF falt.tag ??><!-- ************************************************************ --><!-- TAGDOC for FALT                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	falt.tag,v $
# Revision 1.3  94/01/04  00:42:18  msmcq
# simplify content model
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 93-12-22 : MSM : replace & by seq in model               --><!-- 93-09-22 : MSM : extract from TDL group tagdoc           --><!-- ************************************************************ --><tagDoc id="FALT" usage="rwa"><gi tei="yes">fAlt</gi><name>Feature alternation</name><desc>provides alternative features for a feature structure or other
feature alternation.</desc><attList><attDef id="FALTME" usage="opt"><attName>mutExcl</attName><desc>indicates whether values are mutually exclusive.</desc><datatype>(Y|N)</datatype><valList type="closed"><val>Y     </val><desc>indicates that the values are mutually exclusive.
   </desc><val>N     </val><desc>indicates that the values are not mutually exclusive.</desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<fAlt mutExcl=Y>
  <f name=gender><sym value=masculine>
  <f name=gender><sym value=neuter>
  </fAlt>]]></eg></exemplum><part type="top" name="fs"/><classes/><dataDesc>Two or more features, feature structures or feature
alternations.</dataDesc><elemDecl>- - ((f | fs | fAlt), (f | fs | fAlt)+)</elemDecl><xref target="FSAL" type="div3"/></tagDoc><?tei:EOF falt.tag ??><!-- fAlt           --><?tei:SOF fdecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fdecl.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY fdecl system    'fdecl.tag' --><!-- fdecl tag --><!-- ************************************************* fDecl --><tagDoc id="FDECL" usage="mwa"><gi tei="yes">fDecl</gi><name>feature declaration</name><desc>declares a single feature, specifying its name, organization,
range of allowed values, and optionally its default value.</desc><attList><!-- ................................................... name --><attDef usage="req"><attName>name</attName><desc>indicates the name of the feature being declared; matches the
<att tei="yes">name</att> attribute of <gi tei="yes">f</gi> elements in the text.</desc><datatype>NMTOKEN</datatype><valDesc>any string of characters</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef><!-- .................................................... org --><attDef usage="opt"><attName>org</attName><name>organization</name><desc>specifies the organizing discipline of the feature value.</desc><datatype>(unit | set | bag | list)</datatype><valList type="closed"><val>unit </val><desc>unitary atomic value</desc><val>set </val><desc>set value (unordered, no duplicates)</desc><val>bag </val><desc>bag value (unordered, may have duplicates)</desc><val>list </val><desc>list value (ordered, may have duplicates)</desc></valList><default>unit</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (fDescr?, vRange, vDefault?)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF fdecl.tag ??><!-- fDecl element --><?tei:SOF fdescr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fdescr.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY fdescr system   'fdescr.tag' --><!-- fdescr tag --><!-- ************************************************* fdescr --><tagDoc id="FDESCR" usage="opt"><gi tei="yes">fDescr</gi><name>feature description (in FSD)</name><desc>describes in prose what is represented by the feature being
declared and its values.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain character data, phrase-level elements, and
inter-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF fdescr.tag ??><!-- fDescr element --><?tei:SOF figdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- ******************************************************** figdesc --><tagDoc id="FIGDESC" usage="rwa"><gi tei="yes">figDesc</gi><name>Description of Figure</name><desc>contains a brief prose description of the appearance or content
of a graphic figure, for use when documenting an image without
displaying it.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks><p></p><p>This element is intended for use as an alternative to the
content of its parent <gi tei="yes">figure</gi> element; for example, to display
when the image is required but the equipment in use cannot display
graphic images. It may also be used for indexing or documentary
purposes.</p></remarks><part type="top" name="graphics"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%paraContent;)</elemDecl><xref target="FTGRA" type="div2"/></tagDoc><?tei:EOF figdesc.tag ??><!-- figDesc element --><?tei:SOF wsdfig.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdfig.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ************************************************* figure --><tagDoc id="WSDFIG" usage="opt"><gi tei="yes">figure</gi><desc>(in a writing system declaration) contains an image of a character
form, stored in-line in some declared notation.</desc><attList><!-- ............................................... notation --><attDef usage="req"><attName>notation</attName><desc>identifies the notation in which the figure is encoded.</desc><datatype>NAME</datatype><valDesc>a valid SGML name associated with a given notation by means of
an SGML NOTATION declaration in the document type definition.</valDesc><default>#REQUIRED</default><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[<!-- in the DTD -->
<!NOTATION charcell
           PUBLIC '-//Anonymous//NOTATION
                   8x14 character cell format//en' >
 
<!-- 'CHARCELL' is a simple-minded notation for transcribing  -->
<!-- character images in the form used by the old IBM PC:     -->
<!-- an eight-by-fourteen pixel character cell.  Each pixel   -->
<!-- is represented by a period (if off) or an X (if on).     -->
<!-- Newlines are ignored, but for obvious reasons it's       -->
<!-- convenient to have one after each line of pixels.        -->
 
<!-- N.B.  This 'notation' is given as an example; it is not  -->
<!-- (repeat, NOT) recommended for serious use.               -->
 
<!-- in the WSD itself: -->
<character class='lexical'>
<desc>Latin lowercase letter thorn</desc>
<form entityStd='thorn' entityLoc='t'>
<figure notation=charcell>
 ........
 ........
 XXX.....
 .XX.....
 .XX.....
 .XXXXX..
 .XX..XX.
 .XX..XX.
 .XX..XX.
 .XXXXX..
 .XX.....
 .XX.....
 XXXX....
 ........
</figure>
</form>
</character>]]></eg></exemplum><remarks><p>Inline storage of non-SGML data may be convenient for a
variety of reasons, but complications occasionally ensue if any portion
of the data can be interpreted by the SGML parser as ending some open
SGML element.  For this reason, inline storage should be used only for
extremely simple notations such as the one shown, or by users well
versed in dealing with SGML and graphics.  In general, external storage
of figures is recommended because less error prone.
 </p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain non-SGML character data.</dataDesc><elemDecl>- -  CDATA</elemDecl><xref target="WDCSEX"/></tagDoc><?tei:EOF wsdfig.tag ??><!-- figure element (for WSD) --><?tei:SOF figure.tag ??><!-- Revisions:                                               --><!-- 94-02-28 : MSM : add to class INTER                      --><!-- 94-02-25 : MSM : allow p* for transcription of caption   --><!-- 94-02-25 : MSM : define entity attribute                 --><!-- 93-09-13 : MSM : change xref:  FT not GF                 --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: figure.tag,v $
    * Revision 1.6  1998/01/31 18:29:58  tei
    * added to new fmchunk class
    *
    * Revision 1.5  98/01/28  19:22:39  tei
    *  LB changes of 1998-01
    * Revision 1.4  1994/03/01  04:13:17  msmcq
    * revision during/after SC meeting
    * 
    * Revision 1.3  1994/02/02  16:58:53  lou
    * revused for FT
    * 
    * Revision 1.2  1993/09/22  19:26:36  msmcq
    * changes as of publication of TD
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- ************************************************** figure --><tagDoc id="FIGURE" usage="rwa"><gi tei="yes">figure</gi><desc>indicates the location of a graphic, illustration, or figure.</desc><attList><!-- ................................................. entity --><attDef usage="mwa"><attName>entity</attName><desc>names the external entity within which the graphic image of
the figure is stored.</desc><datatype>ENTITY</datatype><valDesc>the entity name of some external entity declared either as a
<code tei="yes" type="kw">SUBDOC</code> entity or as an entity using a non-SGML
notation.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute may be omitted if for some reason no
electronic form of the image is provided.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<figure entity='Fig1'>
<head>Figure One: The View from the Bridge</head>
<figDesc>A Whistleresque view showing four
or five sailing boats in the foreground, and a
series of buoys strung out between them.</figDesc>
</figure>]]></eg></exemplum><remarks><p>The end-tag must be supplied, even if the element has no
content.</p></remarks><part type="top" name="ft"/><classes names="INTER TPPARTS"/><dataDesc></dataDesc><elemDecl>- - (head?, p*, figDesc?, text?)</elemDecl><xref target="FT" type="div1"/></tagDoc><?tei:EOF figure.tag ??><!-- figure element --><?tei:SOF fildesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fildesc.tag,v $
# Revision 1.2  94/01/04  12:14:27  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *****************************************************fileDesc --><tagDoc id="FILDESC" usage="req"><gi tei="yes">fileDesc</gi><name>File Description</name><desc>contains a full bibliographic description of an electronic
file.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks><p>The major source of information for those seeking to create
a catalogue entry or bibliographic citation for an electronic file.  As
such, it provides a title and statements of responsibility together with
details of the publication or distribution of the file, of any series to
which it belongs, and detailed bibliographic notes for matters not
addressed elswhere in the header. It also contains a full bibliographic
description for the source or sources from which the electronic text was
derived.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- - (titleStmt,   editionStmt?,
               extent?,      publicationStmt,
               seriesStmt?, notesStmt?,
               sourceDesc+              )</elemDecl><xref target="HD2"/><xref target="HD11"/></tagDoc><?tei:EOF fildesc.tag ??><!-- fileDesc element --><?tei:SOF files.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	files.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/08  23:41:16  msmcq
# cosmetic changes, change desc, suppress query.
#
# Revision 1.2  1993/08/03  02:00:19  msmcq
# valDesc problems
# --><!-- Revisions:                                               --><!-- 93-09-11 : MSM : change desc                             --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : provide valDesc                         --><!-- *************************************************** files --><tagDoc id="FILES" usage="opt"><gi tei="yes">files</gi><desc>specifies the name of the operating system file(s) within which
this markup component is declared.</desc><attList><attDef usage="req"><attName>names
 </attName><desc>supplies the names of one or more files.
 </desc><datatype>CDATA
 </datatype><valDesc>a file identifier
 </valDesc><default>#IMPLIED
 </default></attDef></attList><exemplum><eg><![CDATA[<files names=TEIDICT2>]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TDTAG"/></tagDoc><?tei:EOF files.tag ??><!-- files element --><?tei:SOF frstlang.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	frstlang.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* frstlang --><tagDoc id="FRSTLANG" usage="opt"><gi tei="yes">firstLang</gi><name>First language</name><desc>specifies the first language of a participant.</desc><attList></attList><exemplum><eg><![CDATA[  <firstLang>French]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF frstlang.tag ??><!-- firstLang element --><?tei:SOF flib.tag ??><!-- ************************************************************ --><!-- TAGDOC for FLIB                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	flib.tag,v $
# Revision 1.2  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix FSINFO, make member of METADATA     --><!-- 93-09-22 : MSM : extract from bulk revision              --><!-- ************************************************************ --><tagDoc id="FLIB" usage="rwa"><gi tei="yes">fLib</gi><name>Feature library</name><desc>assembles library of feature elements.</desc><attList><attDef id="FLTYPE" usage="opt"><attName>type</attName><desc>indicates type of feature library (i.e., what kind of features it
contains).</desc><datatype>CDATA</datatype><valDesc>Character string, e.g. <term>word features</term>.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<fLib type='agreement features'>
  <f name=person id=P1 fVal='sfirst'></f>
  <f name=person id=P2 fVal='ssecond'></f>
<!-- ... -->
  <f name=number id=NS fVal='ssing'></f>
  <f name=number id=NP fVal='splur'></f>
<!-- ... -->
  </fLib>]]></eg></exemplum><remarks><p>The entity %fFamily; is used for "f | fAlt" in FS3.dtd.</p></remarks><part type="top" name="fs"/><classes names="METADATA"/><dataDesc>Zero or more features or alternations of features.</dataDesc><elemDecl>- - ((f | fAlt)*)</elemDecl><xref target="FSFL" type="div3"/></tagDoc><?tei:EOF flib.tag ??><!-- fLib           --><?tei:SOF foreign.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	foreign.tag,v $
# Revision 1.2  93/10/29  10:37:24  lou
# change content model to paracontent
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : add lang att                            --><!-- ***************************************************** foreign --><tagDoc id="FOREIGN" usage="opt"><gi tei="yes">foreign</gi><name>foreign</name><desc>identifies a word or phrase as belonging to some language other
than that of the surrounding text. </desc><attList><!-- ................................................... lang --><attDef usage="rec"><attName>lang</attName><name>language</name><desc>identifies the language of the word or phrase marked.</desc><datatype>IDREF</datatype><valDesc>contains a language code (associated with some writing system
declaration) for the language in question; where applicable, the
codes of ISO 639 should be used.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>It is strongly recommended that the <att tei="yes">lang</att>
attribute be consistently specified on all <gi tei="yes">foreign</gi> elements.</p></remarks></attDef></attList><exemplum><eg><![CDATA[   This is heathen Greek to you still?
   Your <foreign lang=lat>lapis philosophicus</foreign>?]]></eg></exemplum><remarks><p>This element is intended for use only where no other element
is available to mark the phrase or words concerned.  The global
<att tei="yes">lang</att> attribute should be used in preference to this element
where it is intended to mark the language of the whole of some text
element.</p><p>The <gi tei="yes">distinct</gi> element may be used to identify phrases
belonging to sublanguages or registers not generally regarded as true
languages.</p></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc>free prose</dataDesc><elemDecl>- - (%paraContent;)</elemDecl><xref target="COHQHF"/></tagDoc><?tei:EOF foreign.tag ??><!-- foreign element --><?tei:SOF forename.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	forename.tag,v $
# Revision 1.5  94/03/15  11:10:34  lou
# minor typos etc
# 
# Revision 1.4  1994/03/07  18:14:24  lou
# fixcontent model
#
# Revision 1.2  1994/03/07  16:15:53  lou
# revised for ND
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--************************************************************forename --><tagDoc id="FORENAME" usage="opt"><gi tei="yes">foreName</gi><name>forename</name><desc>contains a forename, given or baptismal name.</desc><attList></attList><exemplum><eg><![CDATA[<persName>
  <roleName>Ex-President</roleName>
  <foreName>George</foreName>
  <surname>Bush</surname>
</persName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="PERSPART"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF forename.tag ??><!-- forename element --><?tei:SOF forest.tag ??><!-- ********** FOREST                                        --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	forest.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/09  19:01:42  msmcq
# add RCS id, log
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version:                      --><!--                  eliminate ECHO from content model       --><!-- ********** FOREST                                        --><tagDoc id="FOREST" usage="opt"><gi tei="yes">forest</gi><desc>provides for groups of rooted trees.</desc><attList><attDef usage="opt"><attName>type</attName><desc>identifies the type of the forest.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="top" name="graphs"/><classes/><dataDesc>One or more trees, embedding trees, or underspecified embedding
trees (triangles).</dataDesc><elemDecl>- - ((tree | eTree | triangle)+)</elemDecl><xref target="GDAT" type="div2"/></tagDoc><?tei:EOF forest.tag ??><!-- forest element --><?tei:SOF forestgp.tag ??><!-- ********** FORESTgP                                      --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	forestgp.tag,v $
# Revision 1.3  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.2  1993/09/09  19:06:14  msmcq
# add RCSid, name of file is forestgp, not -gr
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version:                      --><!--                  eliminate ECHO from content model       --><!-- ********** FORESTgP                                      --><tagDoc id="FORESTGP" usage="opt"><gi tei="yes">forestGrp</gi><name>Forest group</name><desc>provides for groups of forests.</desc><attList><attDef usage="opt"><attName>type</attName><desc>identifies the type of the forest group.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<!--None provided. -->]]></eg></exemplum><part type="top" name="graphs"/><classes/><dataDesc>One or more forests.</dataDesc><elemDecl>- - ((forest)+)</elemDecl><xref target="GDAT" type="div2"/></tagDoc><?tei:EOF forestgp.tag ??><!-- forestGrp element --><?tei:SOF form.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-13 : MSM : allow usg, lbl (put them into formInfo!) --><!-- 94-01-12 : MSM : m.forminfo in model, not forminfo       --><!-- 94-01-12 : MSM : change model, add to forminfo class     --><!-- 93-10-19 : MSM : make TYPE att semi closed list          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	form.tag,v $
# Revision 1.3  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.2  1994/01/04  00:40:39  msmcq
# first cut at DI revisions; make TYPE semi
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************* form   --><tagDoc id="FORM" usage="rec"><gi tei="yes">form</gi><name>form information group</name><desc>groups all the information on the written and spoken forms of one
headword.</desc><attList><attDef usage="opt"><attName>type
    </attName><desc>classifies form as simple, compound, etc.
    </desc><datatype>CDATA
    </datatype><valList type="semi"><val>simple     </val><desc>single free lexical item
        </desc><val>lemma      </val><desc>the headword itself
        </desc><val>variant    </val><desc>a variant form
        </desc><val>compound   </val><desc>word formed from simple lexical items
        </desc><val>derivative </val><desc>word derived from headword
        </desc><val>inflected  </val><desc>word in other than usual dictionary form
        </desc><val>phrase     </val><desc>multiple-word lexical item
    </desc></valList><default>#IMPLIED</default><eg></eg></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS FORMINFO DIGLOBAL"/><dataDesc>May contain any of a variety of element.</dataDesc><elemDecl>- -  (%m.formInfo | %paraContent)+</elemDecl><xref target="DITPFO" type="div2"/></tagDoc><?tei:EOF form.tag ??><!-- form element --><?tei:SOF wsdform.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdform.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- *************************************************** form --><tagDoc id="WSDFORM" usage="mwa"><gi tei="yes">form</gi><name>letter form</name><desc>identifies one letter form taken by a particular character in a
writing system declaration.</desc><attList><!-- ................................................. string --><attDef usage="opt"><attName>string</attName><desc>gives the byte string used to encode the letter form in the text.</desc><datatype>CDATA</datatype><valDesc>any string of characters (often a single byte)</valDesc><default>#IMPLIED</default><eg><![CDATA[ <form string='a/'>
    <desc>lowercase Greek alpha with acute accent</desc>
 </form>]]></eg><remarks><p>If the character is encoded only using entity
references, then the value of <att tei="yes">string</att> should be ''
(the empty string).
 </p><p>In coded character sets which use character-set shifting (e.g. JIS
0208), the <att tei="yes">string</att> attribute should typically contain the
required shift characters, in order to render the value unambiguous.  In
such a case, there is no expectation that every occurrence of the
character will be immediately preceded by the shift sequence; processing
software is responsible for understanding the shift mechanism and acting
accordingly.
 </p><p>The same string value may not appear on more than one <gi tei="yes">form</gi>
elements (except the empty string), unless each occurrence is
associated with a different coded character set.
 </p></remarks></attDef><!-- ........................................... codedCharSet --><attDef usage="opt"><attName>et</attName><name>coded character set</name><desc>specifies which base coded character set the <att tei="yes">string</att>
value occurs in.</desc><datatype>IDREF</datatype><valDesc>a reference to the SGML identifier of a <gi tei="yes">et</gi>
element in the current writing system declaration.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>If more than one <gi tei="yes">et</gi> is specified as a
base component of the writing system declaration, then it is expected
that character-set shifting is in use, as described in ISO 2022 or some
equivalent.  In this case, each <gi tei="yes">form</gi> element which has a value
for the <att tei="yes">string</att> attribute should also identify, by means of
the <att tei="yes">codedCharSet</att> attribute, which identifies which coded
character set actually contains the string in question.  Proper shifting
among character sets is the responsibility of the user.
 </p></remarks></attDef><!-- .............................................. entityStd --><attDef usage="opt"><attName>entityStd</attName><name>standard entity name</name><desc>gives the name of one or more entities defined for this character
form in some standard entity set(s).</desc><datatype>ENTITIES</datatype><valDesc>One or more valid SGML entity names declared in the document
type definition of the WSD; the entity must also be included in an
entity set mentioned in an <gi tei="yes">entitySet</gi> declaration in the current
writing system declaration or in some base writing system referred to by
a <gi tei="yes">baseWsd</gi> element.</valDesc><default>#IMPLIED</default><eg><![CDATA[ <form entityStd='thorn'>
   <desc>lowercase Old English/Icelandic thorn</desc>
 <form>]]></eg><remarks><p>If the same letter form is defined by more than
one public entity set, more than one value may appear in this
attribute.
 </p><p>The same entity name may not appear in the <att tei="yes">entityStd</att> or
<att tei="yes">entityLoc</att> attributes of more than one <gi tei="yes">form</gi> element.
 </p></remarks></attDef><!-- .............................................. entityLoc --><attDef usage="opt"><attName>entityLoc</attName><name>local entity name</name><desc>gives one or more entity names used locally for this character
form.</desc><datatype>ENTITIES</datatype><valDesc>One or more valid SGML entity names declared in the document
type definition of the WSD; the entity must also be included in an
entity set mentioned in an <gi tei="yes">entitySet</gi> declaration in the current
writing system declaration or in some base writing system referred to by
a <gi tei="yes">baseWsd</gi> element.</valDesc><default>#IMPLIED</default><eg><![CDATA[ <form entityStd='thorn' entityLoc='t'>
   <desc>lowercase Old English/Icelandic thorn</desc>
   <note>The standard entity name is 'thorn'; the local entity 't'
         is used for brevity and legibility.</note>
 <form>]]></eg><remarks><p>The same entity name may not appear in the <att tei="yes">entityStd</att> or
<att tei="yes">entityLoc</att> attributes of more than one <gi tei="yes">form</gi> element.</p></remarks></attDef><!-- .................................................. ucs-4 --><attDef usage="opt"><attName>ucs-4</attName><name>universal-character-set code</name><desc>gives the position of the character form in the thirty-two bit
<soCalled>universal character set</soCalled> defined by ISO 10646.</desc><datatype>CDATA
 </datatype><valDesc>one or more sets of two or four two-digit hexadecimal numbers
giving a valid ISO 10646 code point for the character form; for
legibility the two-digit hexadecimal numbers should be separated by
hyphens.  If more than one UCS-4 code is associated with a given
character form, the two UCS-4 codes should be given separated by blanks.
If the character form is associated with a sequence of UCS-4 codes (e.g.
a base character followed by one or more non-spacing diacritics), then
the components of the sequence should be separated by '+'.
 </valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The same UCS-4 code (or sequence) may not appear within more
than one <gi tei="yes">character</gi> element within the writing system
declaration.  It may however appear on several forms of the same
character.
 </p><p>Multiple UCS-4 codes can be given for a single character; this allows
sequences treated as distinct by ISO 10646 to be documented as referring
to a single <soCalled>character</soCalled> as defined by the WSD (e.g.
<q>lowercase a-umlaut</q> and <q>lowercase a</q> plus <q>umlaut</q>).
 </p><p>If a single UCS-4 code is to be treated as relating to two distinct
<soCalled>characters</soCalled> as defined by the WSD (e.g. to reverse
the effects of Han unification on some character), then one of the
<gi tei="yes">character</gi> elements should be associated with the UCS-4 code in
the normal way, and the others should call attention to the relevant
UCS-4 code by a comment in a <gi tei="yes">note</gi> element.
 </p></remarks></attDef><!-- ............................................... afiicode --><attDef usage="opt"><attName>afiicode</attName><name>AFII code</name><desc>gives one or more codes associated with this letter form by the
Association for Font Information Interchange.</desc><datatype>CDATA</datatype><valDesc>any valid AFII identifier.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The AFII tables are designed as an inventory of
<term>glyphs</term> (identifiably distinct shapes, leaving differences
of font design out of account---one character may be associated with
several glyphs, and each glyph with items in several different fonts).
Because the same glyph may be associated with more than one character
(in some fonts, for example, the lowercase letter L and the digit 1
share the same glyph), the value of <att tei="yes">afiiCode</att> is used for
informational purposes only and need not be unique within the writing
system declaration.
 </p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The <gi tei="yes">form</gi> element documents one form of a character;
in most cases, there will be only one.  If more than one form is given,
in general, they are to be regarded as free variants of the character
unless otherwise specified in the notes.
 </p><p>The distinction between <gi tei="yes">character</gi> and <gi tei="yes">form</gi> makes it
possible to distinguish, in an encoding, among different letter forms
(which may have historical, aesthetic, linguistic, or other
significance) without having to claim that the different forms
constitute different <soCalled>characters</soCalled> in any normal
sense.  (Using the technical terms occasionally encountered, the
<gi tei="yes">form</gi> element can be used to record each <term>allograph</term>
of a given character or <term>grapheme</term>.)  The concepts of
<soCalled>character</soCalled> and <soCalled>letter form</soCalled>,
however, vary from analyst to analyst; the decision to treat a given set
of forms as a single character or as a set of characters is not always
obvious, and may require the application of considerable learning and
judgement.  The <gi tei="yes">note</gi> element should be used to record the
reasoning behind any particularly difficult decision.
 </p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain a series of description element, optionally one or
more figure elements showing the character form in question, and
optionally a series of notes.</dataDesc><elemDecl>- O  (desc+, (figure | extFigure)*, note*)</elemDecl><xref target="WDCSEX"/></tagDoc><?tei:EOF wsdform.tag ??><!-- form element --><?tei:SOF formula.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: formula.tag,v $
    * Revision 1.5  1998/02/01 17:47:00  tei
    * remove paremthesis
    *
    * Revision 1.4  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.3  1994/03/01  04:13:17  msmcq
    * revision during/after SC meeting
    * 
    * Revision 1.2  1994/02/02  16:58:13  lou
    * revised for publicn of FT
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 1 feb 98 : LB : whoops: remove  brackets from content model  --><!-- 10 jan 98 : LB : add brackets to content model  --><!-- 94-02-28 : MSM : add direct to phrase class              --><!-- 94-02-24 : MSM : change notation data type               --><!-- 92-11-23 : MSM : for formulas read formulae              --><!-- ************************************************** formula --><tagDoc id="FORMULA" usage="rwa"><gi tei="yes">formula</gi><desc>contains a mathematical or other formula.</desc><attList><attDef usage="opt"><attName>notation</attName><desc>supplies the name of a previously defined notation used for the
content of the element.</desc><datatype>%formulaNotations</datatype><valDesc>The name of a notation for which a formal SGML notation
declaration has been provided in the document type declaration.</valDesc><default>#REQUIRED</default><remarks></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p></p></remarks><part type="base" name="formulae"/><classes names="PHRASE"/><dataDesc>The content model for this element is specified by the
parameter entity <term>formulaContent</term>, the default value of
which is <q>CDATA</q>.</dataDesc><elemDecl>- - %formulaContent;</elemDecl><xref target="FTFOR" type="div1"/></tagDoc><?tei:EOF formula.tag ??><!-- formula element --><?tei:SOF front.tag ??><!-- Revisions:                                               --><!-- 31 jan 98: LB : changed divTop to fmchunk --><!-- 93-08-19 : MSM : fold titlepage into m.front             --><!-- 93-08-19 : MSM : allow m.front to appear!                --><!-- 93-08-18 : MSM : case correction for titlePage           --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: front.tag,v $
    * Revision 1.7  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.6  1998/01/31 18:29:58  tei
    * changed divtop to fmchunk in content model
    *
    * Revision 1.5  94/03/15  11:10:34  lou
    * minor typos etc
    * 
    * Revision 1.4  1994/01/04  12:14:28  lou
    * fix xrefs
    * 
    * Revision 1.3  1993/08/23  16:35:52  msmcq
    * check in version published with DR
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ********************************************************front --><tagDoc id="FRONT" usage="rec"><gi tei="yes">front</gi><name>front matter</name><desc>contains any prefatory matter (headers,
title page, prefaces, dedications, etc.)
found before the start of a text proper.</desc><attList></attList><exemplum><eg><![CDATA[<front>
<epigraph lang=LA>
<quote>Nam Sibyllam quidem Cumis ego ipse oculis meis
vidi in ampulla pendere, et cum illi pueri dicerent:
<q lang=GRC>Sibylla ti weleis</q>; respondebat
illa: <q lang=GRC>apowanein welo.</q></quote></epigraph>
<div type=dedication>
<p>For Ezra Pound <q lang=IT>il miglior fabbro.</q></p>
</front>]]></eg></exemplum><!-- T.S.Eliot, Wasteland, 1922 --><!-- changed tagging:  Q not FOREIGN for dialog in epigraph,  --><!-- iso 639's GRC not GK for language code, ITA for IT       --><!-- Q not FOREIGN for Dante quotation. -msm                  --><!-- P around dedication as per content model and other exx   --><exemplum><eg><![CDATA[<front>
<div type=dedication>
<p>To our three selves
</div>
<div type=preface>
<head>Author's Note</head>
<p>All the characters in this book are purely imaginary, and if the
author has used names that may suggest a reference to living persons
she has done so inadvertently.
 ...
</div>
</front>]]></eg></exemplum><!-- Radclyffe Hall, Well of Loneliness, 1928 --><remarks></remarks><part type="base" name="core"/><classes names="DECLING"/><elemDecl>- O (  (%m.front;)*,
                 (
                   ( (%m.fmchunk;), (%m.fmchunk; | titlePage)*)
                   |
                   ( (div), (div | (%m.front;) )*)
                   |
                   ( (div1), (div1 | (%m.front;) )*)
                 )?
              )</elemDecl><!-- < elemdecl > - O ((%m.divtop;)*, ( (div+ | div1+)        --><!--               | ( %component;+, (div* | div1*))),        --><!--               (%m.divbot;)*)                             --><!-- < / elemdecl >                                           --><xref target="DSTITL"/><xref target="DS"/></tagDoc><?tei:EOF front.tag ??><!-- front element --><?tei:SOF fstag.tag ??><!-- ************************************************************ --><!-- TAGDOC for FS                                                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fstag.tag,v $
# Revision 1.5  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.4  1994/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
#
# Revision 1.3  1994/01/04  00:43:51  msmcq
# change descriptions of REL values
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix FSINFO, make member of METADATA     --><!-- 94-04-07 : MSM : add to class cplxval                    --><!-- 94-04-07 : MSM : comment out remarks                     --><!-- 93-12-22 : MSM : change descriptions on REL att values   --><!-- 93-09-22 : MSM : extract from bulk revision              --><!-- ************************************************************ --><tagDoc id="FSTAG" usage="rwa"><gi tei="yes">fs</gi><name>Feature structure</name><desc>analyzes a collection of features and feature alternations as a
structural unit.</desc><attList><attDef id="FSTYPE" usage="rwa"><attName>type</attName><desc>provides a type for a feature structure.</desc><datatype>CDATA</datatype><valDesc>Character string, e.g. <term>word structure</term>.</valDesc><default>#IMPLIED</default></attDef><!-- why can't we call this 'features'? (msm) --><attDef id="FSFEATS" usage="opt"><attName>feats</attName><desc>pointer to features.</desc><datatype>IDREFS</datatype><valDesc>list of individual IDs for features.</valDesc><default>#IMPLIED</default><remarks><p>May be used instead of having features as content.</p></remarks></attDef><attDef id="FSREL" usage="opt"><attName>rel</attName><desc>indicates the relation of the given content to the actual content
or value of the feature structure.</desc><datatype>(eq|ne|sb|ns)</datatype><valList type="closed"><val>eq     </val><desc>indicates that the actual content is that given.
   </desc><val>ne     </val><desc>indicates that the actual content is not that given.
   </desc><val>sb     </val><desc>indicates that the actual content is subsumed by the
given content.
   </desc><val>ns     </val><desc>indicates that the actual content is not subsumed by
the given content.</desc></valList><default>sb</default><remarks><p>The <gi tei="yes">fs</gi> element is the only one for which the default
<att tei="yes">rel</att> attribute value is <term>sb</term>.  For all others, it is
<term>eq</term>.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<fs type='agreement structure' rel=ns>
   <f name=person><sym value=third></f>
   <f name=number><sym value=singular></f>
   </fs>]]></eg></exemplum><!-- <remarks><p>The entity %fFamily; is defined as "f |      --><!-- fAlt" in FS3.dtd.                                        --><part type="top" name="fs"/><classes names="CPLXVAL METADATA"/><dataDesc>Zero or more features or (feature) alternations.</dataDesc><elemDecl>- - ((f | fAlt | alt)*)</elemDecl><xref target="FSBI" type="div3"/></tagDoc><?tei:EOF fstag.tag ??><!-- fs element     --><?tei:SOF fsconstr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fsconstr.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY fsconstr system 'fsconstr.tag' --><!-- fsconstr tag --><!-- ****************************************** fsConstraints --><tagDoc id="FSCONSTR" usage="opt"><gi tei="yes">fsConstraints</gi><name>feature-structure constraints</name><desc>specifies constraints on the content of well formed feature
structures.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain a series of conditional or biconditional elements.</dataDesc><elemDecl>- -  (cond | bicond)*</elemDecl><xref target="FD"/></tagDoc><?tei:EOF fsconstr.tag ??><!-- fsConstraints element --><?tei:SOF fsddecl.tag ??><!-- Revisions:                                               --><!-- 94-04-06 : MSM : suppress project-internal & empty remarks --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fsddecl.tag,v $
# Revision 1.3  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.2  1994/01/28  18:02:20  lou
# add example and xref
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY fsddecl system  'fsddecl.tag' --><!-- fsddecl tag --><!-- ************************************************ fsdDecl --><tagDoc id="FSDDECL" usage="rwa"><gi tei="yes">fsdDecl</gi><name>FSD (feature-system declaration) declaration</name><desc>identifies the feature system declaration which contains
definitions for a particular type of feature structure.</desc><attList><!-- ................................................... type --><attDef usage="req"><attName>type</attName><desc>identifies the type of feature structure documented in the FSD;
this will be the value of the <att tei="yes">type</att> attribute on at least one
feature structure.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p>[Restore type of ID? -Ed.]</remarks>         --></attDef><!-- .................................................... fsd --><attDef usage="req"><attName>fsd</attName><name>feature-system declaration</name><desc>specifies the external entity containing the feature system
declaration; an entity declaration in the document's DTD subset must
associate the entity name with a file on the system.</desc><datatype>ENTITY</datatype><valDesc>an entity name (and therefore a valid SGML identifier)</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><!-- <remarks><p></remarks>                                   --></attDef></attList><exemplum><eg><![CDATA[     <encodingDesc>
           <!-- ... -->
           <fsdDecl type=GPSG fsd=fsd.gazdar>
           <fsdDecl type=entry fsd=fsd.lexicon>
           <fsdDecl type=subentry fsd=fsd.lexicon>
           <!-- ... -->
      </encodingDesc>
 ]]></eg></exemplum><!-- <remarks><p></remarks>                                   --><part type="top" name="fs"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="HDFSD"/><xref target="FD"/></tagDoc><?tei:EOF fsddecl.tag ??><!-- fsdDecl element --><?tei:SOF fsdecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fsdecl.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY fsdecl system   'fsdecl.tag' --><!-- fsdecl tag --><!-- ************************************************* fsDecl --><tagDoc id="FSDECL" usage="mwa"><gi tei="yes">fsDecl</gi><name>feature structure declaration</name><desc>declares one type of feature structure.</desc><attList><!-- ................................................... type --><attDef usage="req"><attName>type</attName><desc>gives a name for the type of feature structure being declared.</desc><datatype>CDATA</datatype><valDesc>any convenient string of characters.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef><!-- ............................................... baseType --><attDef usage="opt"><attName>baseType</attName><desc>gives the name of the feature structure type from which this
type inherits features and constraints; if this type declares a feature
with the same name as a feature of the base type, the definition within
this <gi tei="yes">fsDecl</gi> overrides the inherited definition.  The
<gi tei="yes">fsConstraints</gi> are inherited only if this <gi tei="yes">fsDecl</gi>
does not specify any; otherwise the constraints in this <gi tei="yes">fsDecl</gi>
override.  When no <att tei="yes">baseType</att> is specified, no features
or constraints are inherited.</desc><datatype>CDATA</datatype><valDesc>any convenient string for use as a name.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>Contains a description (optional), a series of feature
declarations, and an optional set of feature structure constraints.</dataDesc><elemDecl>- -  (fsDescr?, fDecl+, fsConstraints?)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF fsdecl.tag ??><!-- fsDecl element --><?tei:SOF fsdescr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fsdescr.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY fsdescr system  'fsdescr.tag' --><!-- fsdescr tag --><!-- ************************************************ fsdescr --><tagDoc id="FSDESCR" usage="opt"><gi tei="yes">fsDescr</gi><name>feature system description (in FSD)</name><desc>describes in prose what is represented by the type of feature
structure declared in the enclosing <gi tei="yes">fsDecl</gi>.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain character data, phrase-level elements, and
inter-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF fsdescr.tag ??><!-- fsDescr element --><?tei:SOF fslib.tag ??><!-- ************************************************************ --><!-- TAGDOC for FSLIB                                             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fslib.tag,v $
# Revision 1.3  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 93-09-22 : MSM : extract from bulk revision              --><!-- ************************************************************ --><tagDoc id="FSLIB" usage="rwa"><gi tei="yes">fsLib</gi><name>Feature-structure library</name><desc>assembles library of feature structure elements.</desc><attList><attDef id="FSLTYPE" usage="opt"><attName>type</attName><desc>indicates type of feature-structure library (i.e., what type of
feature structures it contains).</desc><datatype>CDATA</datatype><valDesc>Character string, e.g. <term>word structure library</term>.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<fsLib type='agreement structure library'>
  <fs type='agreement structure' id=P1NS feats='P1 Ns'></fs>
  <fs type='agreement structure' id=P1NP feats='P1 Np'></fs>
<!-- ... -->
  </fsLib>]]></eg></exemplum><remarks><p>If a <tag compl="full" tei="yes">vAlt</tag> member of an <tag compl="full" tei="yes">fsLib</tag> tag does
not consist of <tag compl="full" tei="yes">fs</tag> tags, the result is a semantic error.</p></remarks><part type="top" name="fs"/><classes names="METADATA"/><dataDesc>Zero or more feature structures or alternations of feature
structures (expressed as <gi tei="yes">vAlt</gi> elements, see remarks).</dataDesc><elemDecl>- - ((fs | vAlt)*)</elemDecl><xref target="FSFL" type="div3"/></tagDoc><?tei:EOF fslib.tag ??><!-- fsLib          --><?tei:SOF funder.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	funder.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- *******************************************************funder --><tagDoc id="FUNDER" usage="opt"><gi tei="yes">funder</gi><name>Funding body</name><desc>specifies the name of an individual, institution, or organization
responsible for the funding of a project or text.</desc><attList></attList><exemplum><eg><![CDATA[<funder>The National Endowment for the Humanities, an independent
        federal agency</>
<funder>Directorate General XIII of the Commission of the
        European Communities</>
<funder>The Andrew W. Mellon Foundation</>
<funder>The Social Sciences and Humanities Research Council of Canada</>]]></eg></exemplum><remarks><p>Funders provide financial support for a project; they are
distinct from <term>sponsors</term>, who provide intellectual
support and authority.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc>Any string of characters.</dataDesc><elemDecl>- o ( %phrase.seq; )</elemDecl><xref target="HD21"/></tagDoc><?tei:EOF funder.tag ??><!-- funder element --><?tei:SOF fvlib.tag ??><!-- ************************************************************ --><!-- TAGDOC for FVLIB                                             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fvlib.tag,v $
# Revision 1.3  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.2  1994/01/04  00:44:35  msmcq
# revise content model fairly seriously
#
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix FSINFO, make member of METADATA     --><!-- 94-01-03 : MSM : change elemdecl:  dft, not default      --><!-- 93-12-22 : MSM : serious change to model:                --><!-- 93-12-22 : MSM :            for ((%magic)? & (%normal)*) --><!-- 93-12-22 : MSM :        read:      ((%magic | %normal)*) --><!-- 93-12-22 : MSM : I hope this is right.                   --><!-- 93-09-22 : MSM : extract from bulk revision              --><!-- ************************************************************ --><tagDoc id="FVLIB" usage="rwa"><gi tei="yes">fvLib</gi><name>Feature-value library</name><desc>assembles library of feature value elements.</desc><attList><attDef id="FVLTYPE" usage="opt"><attName>type</attName><desc>indicates type of feature-value library (i.e., what type of feature
values it contains).</desc><datatype>CDATA</datatype><valDesc>Character string, e.g. <term>symbolic values</term>.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<fvLib type='symbolic values'>
  <sym id=SFIRST value=first>
  <sym id=SSECOND value=second>
<!-- ... -->
  <sym id=SSING value=singular>
  <sym id=SPLUR value=plural>
<!-- ... -->
  </fvLib>]]></eg></exemplum><remarks><p>Content defined as ((%bVal;)? &amp; (%cVal; | ptr | join)*) in
FS3.dtd. </p><p>If a <tag compl="full" tei="yes">vAlt</tag> member of an <tag compl="full" tei="yes">fvLib</tag> tag
contains <tag compl="full" tei="yes">fs</tag> tags, the result is a semantic error.</p></remarks><part type="top" name="fs"/><classes names="METADATA"/><dataDesc>At most one of each of the <term>unique</term> feature values;
and zero or more <term>nonunique</term> feature values, except feature
structures (which should be placed in feature-structure libraries).</dataDesc><elemDecl>- - ((plus | minus | any | none | dft | uncertain | null
| sym | nbr | msr | rate | str | vAlt)*)</elemDecl><xref target="FSFL" type="div3"/></tagDoc><?tei:EOF fvlib.tag ??><!-- fvLib          --><?tei:SOF fw.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	fw.tag,v $
# Revision 1.5  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.4  1994/03/28  12:21:42  lou
# bizarre typo introduced by RCS
#
# Revision 1.3  1994/03/21  14:33:07  lou
# second major typo purge
#
# Revision 1.1  1994/03/08  03:19:42  msmcq
# Initial revision
# --><!-- ************************************************ fw --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of PHRASE       --><!-- 94-03-07 : MSM : make from old skel.tag                  --><!-- 94-03-07 : MSM : Added RCS id                            --><!-- 94-01-27 : MSM : supply default tyupe                    --><!-- 94-01-27 : MSM : correct xref                            --><!-- 94-01-27 : MSM : made file                               --><!-- ************************************************ fw --><tagDoc id="FW" usage="opt"><gi tei="yes">fw</gi><name>forme work</name><desc>contains a running head (e.g. a <soCalled>header</soCalled>,
<soCalled>footer</soCalled>), catchword, or similar material
appearing on the current page.</desc><attList><!-- ................................................... type --><attDef usage="rec"><attName>type</attName><desc>classifies the material encoded according to some useful typology.</desc><datatype>CDATA</datatype><valList type="open"><val>header </val><desc>a running title at the top of the page</desc><val>footer </val><desc>a running title at the bottom of the page</desc><val>pag    </val><desc>a page number or foliation symbol</desc><val>sig    </val><desc>a signature or gathering symbol</desc><val>catch  </val><desc>a catch-word</desc></valList><default>#IMPLIED</default><remarks><p></p></remarks></attDef><!-- .................................................. place --><attDef usage="rec"><attName>place</attName><desc>indicates where on the page this material appears.</desc><datatype>CDATA</datatype><valList type="semi"><val>top </val><desc>top of the page.</desc><val>bot </val><desc>bottom of the page.</desc><val>left </val><desc>in left margin.</desc><val>right </val><desc>in right margin.</desc></valList><default>#IMPLIED</default><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[<fw type=sig place=bot>C3</fw>]]></eg></exemplum><remarks><p>Where running heads are consistent throughout a chapter or
section, it is usually more convenient to relate them to the chapter or
section, e.g. by use of the <att tei="yes">rend</att> attribute.  The
<gi tei="yes">fw</gi> element is intended for cases where the running head
changes from page to page, or where details of page layout and the
internal structure of the running heads, are of paramount importance.</p></remarks><part type="top" name="ph"/><classes names="PHRASE"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%phrase.seq;)</elemDecl><xref target="PHSK"/></tagDoc><?tei:EOF fw.tag ??><!-- fw (forme-work) element --><?tei:SOF gap.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	gap.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1994/04/07  16:50:14  msmcq
    * Added full stops (lack detected by WWP)
    * 
    * Revision 1.1  1994/01/04  13:18:24  lou
    * Initial revision
    * 
    * Revision 1.3  1993/08/18  20:46:14  msmcq
    * fix IHHERITED pseudo-keyword
    * 
    * Revision 1.2  1993/08/03  02:08:44  msmcq
    * fix INHERITED keyword
    *--><!-- Revisions:                                               --><!-- 4 Jan 98: LB : changed class membership from edit to editincl --><!-- 93-08-18 : MSM : correct #IHHERITED (? whence this?)     --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct INHERITED                       --><!-- 93-5-25  : PR  : attributes added, definitions refined   --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- ******************************************************** gap --><tagDoc id="GAP" usage="opt"><gi tei="yes">gap</gi><name>omitted material</name><desc>indicates a point where material has been omitted in a
transcription, whether for editorial reasons described in the TEI
header, as part of sampling practice, or because the material is
illegible or inaudible.</desc><attList><attDef usage="opt"><attName>desc</attName><name>description</name><desc>gives a description of the omitted text.</desc><datatype>CDATA</datatype><valDesc>a prose description of the material omitted.</valDesc><default>#IMPLIED</default><eg></eg></attDef><attDef usage="opt"><attName>reason</attName><desc>gives the reason for omission.  Sample values include
<q>sampling</q>, <q>illegible</q>, <q>inaudible</q>,
<q>irrelevant</q>, <q>canceled</q>, <q>canceled and illegible</q>.</desc><datatype>CDATA</datatype><valDesc>any short indication of the reason for the omission.</valDesc><default>#IMPLIED</default><eg></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>indicates the editor, transcriber or encoder responsible for
the decision not to provide any transcription of the text and hence
the application of the <gi tei="yes">gap</gi> tag.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>In the case of text omitted from the transcription because of
deliberate deletion by an identifiable hand, signifies the hand which
made the deletion.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... agent --><attDef usage="opt"><attName>agent</attName><desc>In the case of text omitted from the transcription because of
damage or other phenomenon  resulting from an identifiable cause,
signifies the causative agent.</desc><datatype>CDATA</datatype><valDesc>any prose description of the agency of damage.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><attDef usage="opt"><attName>extent</attName><desc>indicates approximately how much text has been omitted from the
transcription, in letters, minims, inches, or any appropriate unit,
either because of editorial policy or because a deletion, damage or
other cause has rendered transcription impossible.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>It is possible, but not always necessary, to provide
measurements precise to the millimeter or even to the printer's
point. The degree of precision attempted will vary with the purpose
of the encoding and the nature of the material.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>The <gi tei="yes">gap</gi>,  <gi tei="yes">unclear</gi>, and <gi tei="yes">del</gi> core 
tag elements may be closely allied in use with the <gi tei="yes">damage</gi>
and <gi tei="yes">supplied</gi> elements, available when using the additional
tagset for transcription of primary sources.  See section <xref target="PHCOMB"/> for discussion of which element is appropriate for
which circumstance.</p></remarks><part type="top" name="core"/><classes names="EDITINCL"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="COEDADD" type="div1"/></tagDoc><?tei:EOF gap.tag ??><!-- gap tag (n&eacute; omit) --><?tei:SOF gen.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : suppress dleaves class                  --><!-- 94-01-12 : MSM : note synonymy with GRAM element         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gen.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** gen --><tagDoc id="GEN" usage="rec"><gi tei="yes">gen</gi><name>gender</name><desc>identifies the morphological gender of a lexical item, as given in
the dictionary.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type=gender</tag>.</p></remarks><part type="base" name="dict"/><classes names="DIPARTS MORPH DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.  Typical
content will be <q>m</q>, <q>f</q>, <q>n</q> etc.</dataDesc><elemDecl>- -  (%paraContent)</elemDecl><xref target="DITPFO" type="div2"/></tagDoc><?tei:EOF gen.tag ??><!-- gen element --><?tei:SOF genname.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- renamed from relship              ************************genName--><tagDoc id="GENNAME" usage="opt"><gi tei="yes">genName</gi><desc>contains a name component used to indicating generational
information, such as <q>Junior</q>, or a number used in a monarch's
name.</desc><attList></attList><exemplum><eg><![CDATA[<persName>
  <foreName>Charles</foreName>
  <genName>II</genName>
</persName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="PERSPART"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF genname.tag ??><!-- genName --><?tei:SOF geog.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	geog.tag,v $
# Revision 1.1  94/03/07  16:16:09  lou
# Initial revision
# 
# Revision 1.2  1993/08/03  02:06:55  msmcq
# fix MS end problem
# --><!-- Revisions:                                               --><!-- 6 mar : renamed from gfn --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!--********************************************************GF --><tagDoc id="GEOG" usage="opt"><gi tei="yes">geog</gi><name>geographical feature name</name><desc>contains a common noun identifying some geographical feature 
contained within a geographic name, such as <q>valley</q>,
<q>mount</q> etc.</desc><attList></attList><exemplum><eg><![CDATA[<geogName>
  The <geog>vale</geog>
  of White Horse
</geogName>]]></eg></exemplum><remarks></remarks><part type="aux" name="ND"/><classes names="PLACPART"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF geog.tag ??><!-- geog --><?tei:SOF geogname.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: geogname.tag,v $
    * Revision 1.3  1998/02/01 17:47:00  tei
    * add to names class
    *
    * Revision 1.2  94/10/20  14:22:18  lou
    * Move from class placpart to class data (post-Pr fix)
    * 
    * Revision 1.1  1994/03/07  16:16:25  lou
    * Initial revision
    * 
    * Revision 1.2  1993/09/09  19:07:51  msmcq
    * re-synch versions
    * --><!-- Revisions:                                               --><!-- 1 feb 98: LB : added to names class in order to pick up attributes --><!-- 6 mar 94: renamed from gf --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!--********************************************************geogName --><tagDoc id="GEOGNAME" usage="opt"><gi tei="yes">geogName</gi><name>geographical name</name><desc>a name associated with  some geographical feature such as
 <q>Windrush Valley</q> or <q>Mount Sinai</q>.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>provides more culture- linguistic- or application- specific
information used to categorize this name component.</desc><datatype>CDATA</datatype><valDesc>one of a set of codes defined for the application.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<geogName>
   <geog>Mount</geog>
   <name>Sinai</name>
</geogName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="DATA NAMES"/><elemDecl>- - (geog | name | #PCDATA)*</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF geogname.tag ??><!-- geogName --><?tei:SOF gi.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : close valList for TEI att               --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gi.tag,v $
# Revision 1.4  94/01/04  12:14:29  lou
# fix xrefs
# 
# Revision 1.3  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.2  1993/09/08  23:37:00  msmcq
# change desc, add sgmlkw class, correct elemDecl.
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** gi --><tagDoc id="GI" usage="mwa"><gi tei="yes">gi</gi><name>generic identifier</name><desc>contains the name (generic identifier) of an SGML element.</desc><attList><attDef usage="opt"><attName>TEI
 </attName><desc>indicates whether this element is part of the TEI encoding
scheme (i.e., defined in a TEI DTD fragment) or not.
 </desc><datatype>(yes|no)
 </datatype><valList type="closed"><val>yes</val><desc>this element is part of the TEI scheme.
    </desc><val>no</val><desc>this element is not part of the TEI scheme.</desc></valList><default>yes
 </default></attDef></attList><exemplum><eg><![CDATA[   A  <gi =n>blort</gi> stalked the prairies.
   The element <gi>sourceDesc</gi> is missing.]]></eg></exemplum><part type="aux" name="tsd"/><classes names="SGMLKW"/><dataDesc>TEI naming rules require lower case letters for all identifiers,
except for names derived from multi-word phrases, in which case all but the
first word is capitalized.</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><!-- ODD has #pcdata --><!-- and it is right:  NAME is an ATTLIST keyword --><xref target="TD"/><xref target="TDTAG"/></tagDoc><?tei:EOF gi.tag ??><!-- gi element --><?tei:SOF gloss.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	gloss.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1994/03/25  22:14:43  msmcq
    * full stop after desc.
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- ******************************************************* gloss --><tagDoc id="GLOSS" usage="rwa"><gi tei="yes">gloss</gi><desc>identifies a phrase or word used to provide a gloss or
definition for some other word or phrase. </desc><attList><attDef usage="opt"><attName>target</attName><desc>identifies the associated term element</desc><datatype>IDREF</datatype><valDesc>must be a valid identifier for some <gi tei="yes">term</gi>
	element in the current document</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[We may define <term rend=sc id=TDPV>discoursal point of view</term>
as <gloss target=TDPV>the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc>free prose</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="COHQU"/></tagDoc><?tei:EOF gloss.tag ??><!-- gloss element --><?tei:SOF gram.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	gram.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/03/21  14:33:08  lou
    * second major typo purge
    * 
    * Revision 1.4  1994/03/07  16:15:59  lou
    * typos spotted by DTB
    * 
    * Revision 1.3  1994/01/15  20:53:57  msmcq
    * msmcq revision of DI for P3.  Consult comments for details.
    * 
    * Revision 1.2  1994/01/04  12:14:29  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB :  change  type= on vallist for TYPE       --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to morph class                      --><!-- 94-01-12 : MSM : add mention of use in dictionaries      --><!-- 92-12-23 : MSM : expand TC37dd entity                    --><!-- 92-12-18 : MSM : remove FLATTERM class                   --><!-- 92-12-18 : MSM : added number, animate, and proper as TYPE vals --><!-- 92-11-23 : MSM : define default                          --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- *************************************************** gram --><tagDoc id="GRAM" usage="opt"><gi tei="yes">gram</gi><name>grammatical information</name><desc>within an entry in a dictionary or a terminological data file,
contains grammatical information relating to a term, word, or form.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the grammatical information given according to some
convenient typology --- in the case of terminological information,
preferably the dictionary of data element types
specified in ISO WD 12 620.</desc><datatype>CDATA</datatype><valList type="open"><val>pos</val><desc>part of speech (any of the word classes to which a word may
be assigned in a given language, based on form, meaning, or a
combination of features, e.g. noun, verb, adjective, etc.)</desc><val>gen</val><desc>gender (formal classification by which nouns and pronouns, and
often accompanying modifiers, are grouped and inflected, or changed in
form, so as to control certain syntactic relationships)</desc><val>num</val><desc>number (e.g. singular, plural, dual, ...)</desc><val>animate</val><desc>animate or inanimate</desc><val>proper</val><desc>proper noun or common noun</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>A much fuller list of values for the <att tei="yes">type</att>
attribute may be generated from the dictionary of data element types
under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in
Terminology.  See ISO 12 620 for fuller details.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>In terminological data,
the <gi tei="yes">gram</gi> element usually refers to the most
recently specified <gi tei="yes">term</gi> or <gi tei="yes">otherForm</gi> element.  In
flat term entries, the <att tei="yes">group</att> and <att tei="yes">depend</att> attributes
may be used to indicate exceptions to this general rule.
In dictionaries, the element typically relates to the form or forms
with which it is grouped in a <gi tei="yes">form</gi> or other grouping element.</p></remarks><part type="base" name="term"/><classes names="MORPH DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="TEDTF" type="div1"/><xref target="TETA" type="div1"/><xref target="DITPGR" type="div1"/></tagDoc><?tei:EOF gram.tag ??><!-- gram element --><?tei:SOF gramgrp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	gramgrp.tag,v $
# Revision 1.1  94/01/15  20:53:57  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : usg, lbl are in graminfo                --><!-- 94-01-13 : MSM : allow usg, lbl                          --><!-- 94-01-12 : MSM : change model, add to graminfo class     --><!-- 94-01-12 : MSM : gen not gender                          --><!-- 94-01-12 : MSM : made file from old di gram element      --><!-- ************************************************ gramGrp --><tagDoc id="GRAMGRP" usage="rec"><gi tei="yes">gramGrp</gi><name>grammatical information group</name><desc>groups morpho-syntactic information about a lexical item, e.g.
<gi tei="yes">pos</gi>, <gi tei="yes">gen</gi>, <gi tei="yes">number</gi>, <gi tei="yes">case</gi>, or
<gi tei="yes">itype</gi> (inflectional class).</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS GRAMINFO DIGLOBAL"/><dataDesc>May contain character data mixed with any other elements
defined in the dictionary tag set.</dataDesc><elemDecl>- - (%m.gramInfo | %paraContent)*</elemDecl><xref target="DITPGR" type="div2"/></tagDoc><?tei:EOF gramgrp.tag ??><!-- gramGrp element --><?tei:SOF graph.tag ??><!-- ********** GRAPH                                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	graph.tag,v $
# Revision 1.5  94/01/04  12:14:30  lou
# fix xrefs
# 
# Revision 1.4  1993/09/22  19:09:25  msmcq
# As of chapter publication
#
# Revision 1.3  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
# --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : vallist semi > type=semi                --><!-- 93-09-17 : MSM : outDegr[ee   full word                  --><!-- 93-09-17 : MSM : inDegr[ee                               --><!-- 93-09-15 : MSM : cleanup, add RCS id                     --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version                       --><!--                  merge GRAPH and DIGRAPH tags            --><!--                  replace LABEL and FS content by         --><!--                      label= and value=                   --><!--                  add type= to distinguish among          --><!--                      types of graphs                     --><!--                  eliminate special drawing attributes    --><!--                      (use rend=)                         --><!-- ********** GRAPH                                          --><tagDoc id="GRAPH" usage="rwa"><gi tei="yes">graph</gi><desc>encodes a graph, which is a collection of nodes, and arcs which
connect the nodes.</desc><attList><attDef id="GRTYPE" usage="rec"><attName>type</attName><desc>describes the type of graph.</desc><datatype>CDATA</datatype><valList type="semi"><val>undirected</val><desc>undirected graph</desc><val>directed</val><desc>directed graph</desc><val>transition network</val><desc>a directed graph with distinguished initial and final nodes</desc><val>transducer</val><desc>a transition network with up to two labels on each arc</desc></valList><default>#IMPLIED</default><remarks><p>If <att tei="yes">type=undirected</att>, then the distinction between
the <att tei="yes">to</att> and <att tei="yes">from</att> attributes of the <gi tei="yes">arc</gi> tag
is neutralized.  Also, the <att tei="yes">adj</att> attribute, rather than the
<att tei="yes">adjFrom</att> and <att tei="yes">adjTo</att> attributes, should be used to
encode pointers to the ends of the arcs.  If <att tei="yes">type=directed</att>
(or any other value which implies directionality), then the
<att tei="yes">adjFrom</att> and <att tei="yes">adjTo</att> attributes should be used,
instead of the <att tei="yes">adj</att> attribute.</p></remarks></attDef><attDef id="GRLAB" usage="rwa"><attName>label</attName><desc>gives a label for a graph.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef id="GRORDER" usage="opt"><attName>order</attName><desc>states the order of the graph, i.e., the number of its nodes.</desc><datatype>NUMBER</datatype><valDesc>A positive integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="GRSIZE" usage="opt"><attName>size</attName><desc>states the size of the graph, i.e., the number of its arcs.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<graph type=undirected
       id=CUG1
       label='Airline Connections in Southwestern USA'
       rend='LABEL-PLACE bottom center NODE-FRAME none ARC solid line'
       order=5
       size=4>
  <node label=LAX id=LAX degree=2>
  <node label=LVG id=LVG degree=2>
  <node label=PHX id=PHX degree=3>
  <node label=TUS id=TUS degree=1>
  <node label=CIB id=CIB degree=0>
  <arc from=LAX to=LVG>
  <arc from=LAX to=PHX>
  <arc from=LVG to=PHX>
  <arc from=PHX to=TUS>
  </graph>]]></eg></exemplum><exemplum><eg><![CDATA[<graph type=directed
       id=RDG2
       label='Selected Airline Routes in Southwestern USA'
       rend='LABEL-PLACE bottom center NODE-FRAME none ARC solid line
with arrowhead'
       order=5
       size=5>
   <node label=LAX id=LAX inDegree=1 outDegree=1 adjTo=LVG adjFrom=PHX>
   <node label=LVG id=LVG inDegree=1 outDegree=1 adjFrom=LAX adjTo=PHX>
   <node label=PHX id=PHX inDegree=2 outDegree=2 adjTo='LAX TUS'
         adjFrom='LVG TUS'>
   <node label=TUS id=TUS inDegree=1 outDegree=1 adjTo=PHX adjFrom=PHX>
   <node label=CIB id=CIB inDegree=0 outDegree=0>
   </graph>]]></eg></exemplum><part type="top" name="graphs"/><classes names="CHUNK"/><dataDesc>One or more nodes and zero or more arcs in any order.</dataDesc><elemDecl>- - ((node)+ &amp; (arc)*)</elemDecl><xref target="GDGR" type="div1"/></tagDoc><?tei:EOF graph.tag ??><!-- graph element --><?tei:SOF group.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	group.tag,v $
# Revision 1.2  94/01/04  12:14:31  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************************************group --><tagDoc id="GROUP" usage="mwa"><gi tei="yes">group</gi><desc>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.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DECLING"/><elemDecl>- O ((%m.divtop;)*, (text | group)+, (%m.divbot;)*)</elemDecl><xref target="DS"/><xref target="DSGRP"/><xref target="CCDEF"/></tagDoc><?tei:EOF group.tag ??><!-- group element --><?tei:SOF hand.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	hand.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/04/07  16:54:20  msmcq
    * Full stops added (WWP)
    * 
    * Revision 1.4  1994/03/25  17:21:51  msmcq
    * cleanup of miscellaneous tagdocs:  some typos,
    * some INHERITED errors, supplied explicit end-tags for many attdef parts
    * to shield a weakness of oddref1 (now fixed)
    * 
    * Revision 1.3  1994/03/08  03:23:14  msmcq
    * trivial Script-motivated fix
    * 
    * Revision 1.2  1994/02/07  20:56:16  msmcq
    * revsisions for P3
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- Revisions:                                               --><!-- 7 jan 98 : LB : changes to HAND attribute (now deprecated); --><!--     mid-atlanticize description of ink attribute        --><!-- 94-03-21 : MSM : correct 'inherited' error               --><!-- 94-03-07 : MSM : suppress leading blank in a P           --><!-- 94-02-04 : MSM : CDATA not IDREF passi m                 --><!-- ENTITY hand   system 'hand.tag' --><!-- hand tag --><!-- ********************************************* hand --><tagDoc id="HAND" usage="rec"><gi tei="yes">hand</gi><desc>used in the header to define each distinct scribe or
handwriting style.</desc><attList><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>identifier, either numeric or alphanumeric, used
thereafter in the document to refer to this scribe or handwriting
style.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><!-- was #required --><eg><![CDATA[ ]]></eg><remarks><p>This attribute is retained only for compatibility with
P3 and may be withdrawn at a later version. Its use is deprecated;
the <att tei="yes">id</att> attribute should be used to supply a unique identifier
for the hand; the <att tei="yes">n</att> attribute may be used to supply an
alternative (and possibly non-unique) name.</p></remarks></attDef><attDef usage="req"><attName>id</attName><desc>identifier, either numeric or alphanumeric, used
thereafter in the document to refer to this scribe or handwriting
style.</desc><datatype>ID</datatype><default>#REQUIRED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................. scribe --><attDef usage="opt"><attName>scribe</attName><desc>gives the name of, or other identifier for, the scribe.</desc><datatype>CDATA</datatype><valDesc>'tremulous hand', 'hand b', 'Hoccleve'</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................style --><attDef usage="opt"><attName>style</attName><desc>indicates recognized writing styles.</desc><datatype>CDATA</datatype><valDesc>'secretary', 'copperplate', 'Chancery', 'Italian', etc.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................lang --><!-- this one should probably be renamed too! --><attDef usage="opt"><attName>lang</attName><name>language</name><desc>indicates dominant language of hand.</desc><datatype>CDATA</datatype><valDesc>'Latin', 'English'</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................ink --><attDef usage="opt"><attName>ink</attName><desc>describes tint or type of ink, e.g. 'brown'.  May also be used to
indicate the writing medium, e.g. 'pencil',</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................character --><attDef usage="opt"><attName>character</attName><desc>describes other characteristics of the hand,
particularly those related to the quality of the writing.</desc><datatype>CDATA</datatype><valDesc>'shaky', 'thick', 'regular'</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................first --><attDef usage="opt"><attName>first</attName><desc>indicates the first scribe in the document.</desc><datatype>CDATA</datatype><valDesc>'YES', 'NO'</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><attDef usage="rec"><attName>resp</attName><name>responsible</name><desc>indicates the editor or transcriber responsible for identifying
the hand.</desc><datatype>CDATA</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The <gi tei="yes">hand</gi>  element is used in the header to
define each unique hand, including unique scribes, distinguished by
the encoder in the document.  One such element must appear within the
header for each hand distinguished in the text.   Each location where
a change of hands occurs is marked in the text by the
<gi tei="yes">handShift</gi> milestone element.</p></remarks><part type="top" name="mss"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="PHDH"/></tagDoc><?tei:EOF hand.tag ??><!-- hand element --><?tei:SOF handlist.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	handlist.tag,v $
# Revision 1.1  94/02/07  20:56:16  msmcq
# Initial revision
#  --><!-- ********************************************* handList --><!-- Revisions:                                               --><!-- 94-02-04 : MSM : made file                               --><!-- ********************************************* handList --><tagDoc id="HANDLIST" usage="rec"><gi tei="yes">handList</gi><desc>contains a series of <gi tei="yes">hand</gi> elements listing the
different hands of the source.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="top" name="mss"/><classes/><dataDesc>Contains a series of <gi tei="yes">hand</gi> elements.</dataDesc><elemDecl>- O  (hand*)</elemDecl><xref target="PHDH"/></tagDoc><?tei:EOF handlist.tag ??><!-- handList element --><?tei:SOF handshft.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	handshft.tag,v $
# Revision 1.4  94/03/25  17:21:51  msmcq
# cleanup of miscellaneous tagdocs:  some typos,
# some INHERITED errors, supplied explicit end-tags for many attdef parts
# to shield a weakness of oddref1 (now fixed)
# 
# Revision 1.3  1994/03/08  03:23:14  msmcq
# trivial Script-motivated fix
#
# Revision 1.2  1994/02/07  20:56:16  msmcq
# revsisions for P3
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-03-21 : MSM : correct 'inherited' error               --><!-- 94-03-07 : MSM : suppress leading blank in a P           --><!-- 94-02-04 : MSM : full stop desc                          --><!-- 94-02-04 : MSM : suppress SCRIBE att                     --><!-- 94-02-04 : MSM : (redundant with same on HAND element)   --><!-- 94-02-04 : MSM : add to phrase class                     --><!-- ********************************************* handShift --><tagDoc id="HANDSHFT" usage="rec"><gi tei="yes">handShift</gi><desc>marks the beginning of a sequence of text written in a new
hand, or of a change in the scribe, writing style, ink or character
of the document hand.</desc><attList><!-- ................................................... new --><attDef usage="req"><attName>new</attName><desc>identifies the new hand.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... old --><attDef usage="req"><attName>old</attName><desc>identifies the old hand.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................style --><attDef usage="opt"><attName>style</attName><desc>indicates recognised writing styles</desc><datatype>CDATA</datatype><valDesc>'secretary', 'copperplate', 'Chancery', 'Italian', etc.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................ink --><attDef usage="opt"><attName>ink</attName><desc>describes colour of ink, e.g. 'brown'.  May also be used to
indicate the writing medium, e.g. 'pencil'</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- .................................................character --><attDef usage="opt"><attName>character</attName><desc>used to describe other characteristics of the hand,
particularly those related to the quality of the writing.</desc><datatype>CDATA</datatype><valDesc>'shaky', 'thick', 'regular'</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><attDef usage="rec"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for identifying
the change of hand.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The <gi tei="yes">handShift</gi> element may be used either to
denote a shift in the document hand (as from one scribe to another,
on one writing style to another).  Or, it may indicate a shift within
a document hand, as a change of writing style, character or ink</p></remarks><part type="top" name="mss"/><classes names="PHRASE"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="PHDH"/></tagDoc><?tei:EOF handshft.tag ??><!-- handShift element --><?tei:SOF head.tag ??><!-- Revisions:                                               --><!-- 94-02-28 : MSM : allow end-tag omission                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: head.tag,v $
    * Revision 1.6  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.5  98/01/31  18:29:58  tei
    * added to fmchunk class
    * 
    * Revision 1.4  94/03/01  04:13:54  msmcq
    * allow end-tag omission
    * 
    * Revision 1.3  1994/01/04  12:14:31  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/10/29  10:27:50  lou
    * changed content model to paraContent
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ******************************************************** head --><tagDoc id="HEAD" usage="rwa"><gi tei="yes">head</gi><name>heading</name><desc>contains any heading, for example, the title of a section,
or the heading of a list or glossary.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>categorizes the heading in some way meaningful to the encoder. </desc><datatype>CDATA
   </datatype><valDesc>A set of user-defined keywords may be employed. Their
   significance should be documented in the header.
   </valDesc><default>#IMPLIED</default></attDef></attList><exemplum><p>The most common use for the <gi tei="yes">head</gi> element
is to mark the headings of sections.  In older writings, the
headings or <term>incipits</term> may be rather longer than
usual in modern works.	If a section has an explicit ending as
well as a heading, it should be marked as a <gi tei="yes">trailer</gi>, as
in this example:</p><eg><![CDATA[ <div1 type=book n='I'><head>In the name of Christ here begins
 the first book of the ecclesiastical history of Georgius
 Florentinus, known as Gregory, Bishop of Tours.</head>
 <list><head>Chapter-Headings</head>
 <!-- list of chapter heads omitted ...  --></list>
 <div2 type=section><head>In the name of Christ here begins Book I of the
 history.</head>
 <p>Proposing as I do ...
 <p>From the Passion of our Lord until the death of Saint Martin
 four hundred and twelve years passed.
 <trailer>Here ends the first Book, which covers five thousand,
 five hundred and ninety-six years from the beginning of the
 world down to the death of Saint Martin.</trailer>
 </div2>
 </div1>]]></eg></exemplum><exemplum><p>The <gi tei="yes">head</gi> tag is also used to mark headings
of other units, such as lists:</p><eg><![CDATA[With a few exceptions, connectives are equally useful in
all kinds of discourse:  description, narration, exposition,
argument.
<list type=simple>
<head>Connectives</head>
<item>above
<item>accordingly
<item>across from
<item>adjacent to
<item>again
<item> <!-- ... -->
</list>]]></eg></exemplum><remarks><p>The <gi tei="yes">head</gi> tag is used for headings at all
levels; processing programs which treat (e.g.) chapter headings,
section headings, and list titles differently must determine the
proper processing of a <gi tei="yes">head</gi> element based on its
structural position.  A <gi tei="yes">head</gi> occurring as the first
element of a list is the title of that list; one occurring as
the first element of a <gi tei="yes">div1</gi> is the title of that
chapter or section.</p></remarks><part type="top" name="core"/><classes names="DIVTOP FMCHUNK"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O (%paraContent;)</elemDecl><xref target="COLI" type="div2"/><xref target="DSDTB" type="div2"/></tagDoc><?tei:EOF head.tag ??><!-- head element --><?tei:SOF headit.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: headit.tag,v $
    * Revision 1.2  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- Revisions:                                               --><!-- 2 jun: LB: changed name from head.item --><!-- 93-02-10 : MSM : cosmetic changes                        --><!-- 92-12-09 : MSM : suppress memberhip in lists class       --><!-- ****************************************************** headit --><tagDoc id="HEADIT" usage="rwa"><gi tei="yes">headItem</gi><name>heading for list items</name><desc>contains the heading for the item or gloss column in a
glossary list or similar structured list.</desc><attList></attList><exemplum><eg><![CDATA[The simple, straightforward statement of an idea is
preferable to the use of a worn-out expression.
<list type=gloss>
<headLabel rend='small caps'>TRITE</headLabel>
<headItem rend='small caps'>SIMPLE, STRAIGHTFORWARD</headItem>
<label>bury the hatchet</label><item>stop fighting, make peace</item>
<label>at loose ends</label><item>disorganized</item>
<label>on speaking terms</label><item>friendly</item>
<label>fair and square</label><item>completely honest</item>
<label>at death's door</label><item>near death</item>
</list>]]></eg></exemplum><remarks><p>The <gi tei="yes">headItem</gi> element may appear only if
each item in the list is preceded by a <gi tei="yes">label</gi>.</p></remarks><part type="top" name="core"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%phrase.seq;)</elemDecl><xref target="COLI" type="div2"/></tagDoc><?tei:EOF headit.tag ??><!-- headItem element --><?tei:SOF headlab.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: headlab.tag,v $
    * Revision 1.2  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- Revisions:                                               --><!-- 2 jun: changed name from head.lab --><!-- 92-12-09 : MSM : suppress memberhip in lists class       --><!-- ***************************************************** headlab --><tagDoc id="HEADLAB" usage="rwa"><gi tei="yes">headLabel</gi><name>heading for list labels</name><desc>contains the heading for the label or term column in a
glossary list or similar structured list.</desc><attList></attList><exemplum><eg><![CDATA[The simple, straightforward statement of an idea is
preferable to the use of a worn-out expression.
<list type=gloss>
<headLabel rend='small caps'>TRITE</headLabel>
<headItem rend='small caps'>SIMPLE, STRAIGHTFORWARD</headItem>
<label>bury the hatchet</label><item>stop fighting, make peace</item>
<label>at loose ends</label><item>disorganized</item>
<label>on speaking terms</label><item>friendly</item>
<label>fair and square</label><item>completely honest</item>
<label>at death's door</label><item>near death</item>
</list>]]></eg></exemplum><remarks><p>The <gi tei="yes">headLabel</gi> element may appear only if
each item in the list is preceded by a <gi tei="yes">label</gi>.</p></remarks><part type="top" name="core"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%phrase.seq;)</elemDecl><xref target="COLI" type="div2"/></tagDoc><?tei:EOF headlab.tag ??><!-- headLabel element --><?tei:SOF hi.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hi.tag,v $
# Revision 1.4  94/02/07  20:56:16  msmcq
# revsisions for P3
# 
# Revision 1.3  1994/01/04  12:14:32  lou
# fix xrefs
#
# Revision 1.2  1993/10/29  10:30:51  lou
# Changed content model to paraContent
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-02-04 : MSM : follow PR's suggestion:  graphically    --><!-- 94-02-04 : MSM :   (not *typo*graphically) distinct      --><!-- 92-12-09 : MSM : add rend attribute                      --><!-- ********************************************************** hi --><tagDoc id="HI" usage="opt"><gi tei="yes">hi</gi><name>highlighted</name><desc>marks a word or phrase as graphically distinct from the
surrounding text, for reasons concerning which no claim is made. </desc><attList><!-- ................................................... rend --><attDef usage="rec"><attName>rend</attName><name>rendition</name><desc>describes the rendition or presentation of the word or phrase
highlighted.</desc><datatype>CDATA</datatype><valDesc>a set of keywords from some suitable vocabulary; no systematic
recommendations for such a vocabulary are made by these Guidelines.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>The <att tei="yes">rend</att> attribute, though optional in general,
is recommended on the <gi tei="yes">hi</gi> element.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<hi rend=gothic>And this Indenture further witnesseth</hi>
that the said <hi rend=italic>Walter Shandy</hi>, merchant,
in consideration of the said intended marriage ...]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="HQPHRASE"/><dataDesc>free prose</dataDesc><elemDecl>- - (%paraContent;)</elemDecl><xref target="COHQHE"/><xref target="COHQH"/></tagDoc><?tei:EOF hi.tag ??><!-- hi element --><?tei:SOF hom.tag ??><!-- Revisions:                                               --><!-- 94-01-15 : MSM : allow end-tag omission                  --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : *not* a member of ditoplev!             --><!-- 94-01-12 : MSM : suppress remark about suppression of hn --><!-- 94-01-12 : MSM : suppress dgroups class                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hom.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** hom --><tagDoc id="HOM" usage="opt"><gi tei="yes">hom</gi><name>homograph</name><desc>groups information relating to one homograph within an
<gi tei="yes">entry</gi>.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="base" name="dict"/><classes names="DIPARTS DIGLOBAL"/><dataDesc>May contain character data mixed with any other elements
defined in the dictionary tag set.</dataDesc><elemDecl>- O  (sense | %m.dictionaryTopLevel)*   -(entry)</elemDecl><xref target="DIEN" type="div2"/></tagDoc><?tei:EOF hom.tag ??><!-- hom element --><?tei:SOF hour.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hour.tag,v $
# Revision 1.3  94/03/07  16:15:27  lou
# initial revision of ND
# 
# Revision 1.2  1993/08/03  02:06:55  msmcq
# fix MS end problem
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- hour --><tagDoc id="HOUR" usage="opt"><gi tei="yes">hour</gi><name>hour</name><desc>the hour component of a temporal expression such as</desc><attList></attList><exemplum><eg><![CDATA[  At the third stroke the time sponsored by Accurist
  will be 
  <timeStruct value='1821:30'>
    <hour>six</hour>
    <minute>twenty-one</minute and 
    <second>thirty</second> seconds
  </timeStruct>]]><!-- speaking clock --></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF hour.tag ??><!-- hour element --><?tei:SOF hyph.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to forminfo class                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hyph.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** hyph --><tagDoc id="HYPH" usage="opt"><gi tei="yes">hyph</gi><name>hyphenation</name><desc>contains a hyphenated form of a dictionary headword, or
hyphenation information in some other form.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DIPARTS FORMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/></tagDoc><?tei:EOF hyph.tag ??><!-- hyph element --><?tei:SOF hyphen.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	hyphen.tag,v $
# Revision 1.2  94/01/04  12:14:33  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- **************************************************hyphenation --><tagDoc id="HYPHEN" usage="opt"><gi tei="yes">hyphenation</gi><name>Hyphenation</name><desc>summarizes the way in which hyphenation in a source text has been
treated in an encoded version of it.</desc><attList><attDef usage="opt"><attName>eol
   </attName><desc>indicates whether or not end-of-line hyphenation has been
   retained in a text.
   </desc><datatype>(all|some|none)
   </datatype><valList type="open"><val>all  </val><desc>all end-of-line hyphenation has been retained,
                   even though the lineation of the original
                   may not have been.
   </desc><val>some </val><desc>end-of-line hyphenation has been retained in some
                   cases.
   </desc><val>hard </val><desc>all `soft' end-of-line hyphenation has been removed:
                   any remaining hyphenation represents `hard hyphens'.
  </desc><val>none </val><desc>all end-of-line hyphenation has been removed:
                  any remaining hyphenation occurred within the line.
   </desc></valList><default>some</default></attDef></attList><exemplum><eg><![CDATA[<hyphenation eol=some>
<p>End-of-line hyphenation silently removed where appropriate]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc>prose</dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/><xref target="CCAS2"/></tagDoc><?tei:EOF hyphen.tag ??><!-- hyphenation element --><?tei:SOF idno.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	idno.tag,v $
# Revision 1.2  94/01/04  12:14:33  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- *********************************************************idno --><tagDoc id="IDNO" usage="opt"><gi tei="yes">idno</gi><name>identifying number</name><desc>supplies any standard or non-standard number used to identify a
bibliographic item.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>categorizes the number, for example as an ISBN or other
         standard series.
   </desc><datatype>CDATA
   </datatype><valDesc>A name or abbreviation indicating what type of identifying
         number is given (e.g. ISBN, LCCN).</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<idno type=ISSN>0143-3385
<idno type=OTA>116]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="BIBLPART"/><dataDesc></dataDesc><elemDecl>- o (#PCDATA)</elemDecl><xref target="HD24"/><xref target="HD26"/><xref target="COBICOI"/></tagDoc><?tei:EOF idno.tag ??><!-- idno element --><?tei:SOF if.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : use m.featureVal not singVal            --><!-- 94-04-07 : MSM : replace fs.family with literal          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	if.tag,v $
# Revision 1.2  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY if system       'if.tag' --><!-- if tag --><!-- ***************************************************** if --><tagDoc id="IF" usage="opt"><gi tei="yes">if</gi><desc>defines a conditional default value for a feature; the condition
is specified as a feature structure, and is met if it
<term>subsumes</term> the feature structure in the text for which a
default value is sought.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain a feature structure, followed by a feature value;
the two are separated by a <gi tei="yes">then</gi> element.</dataDesc><elemDecl>- -  ((fs | f | fAlt), then, (%m.featureVal) )</elemDecl><xref target="FD"/></tagDoc><?tei:EOF if.tag ??><!-- if element --><?tei:SOF iff.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	iff.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY iff system      'iff.tag' --><!-- iff tag --><!-- **************************************************** iff --><tagDoc id="IFF" usage="mwa"><gi tei="yes">iff</gi><desc>separates the condition from the consequence in a <gi tei="yes">bicond</gi>
element.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is provided primarily to enhance the
human readability of the feature-system declaration.</p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="FD"/></tagDoc><?tei:EOF iff.tag ??><!-- iff element --><?tei:SOF ihs.tag ??><!-- Revisions:                                               --><!-- 93-09-15 : MSM : lowercase name                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ihs.tag,v $
# Revision 1.3  94/01/04  12:14:34  lou
# fix xrefs
# 
# Revision 1.2  1993/09/16  15:18:45  msmcq
# Interim revision of SH
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ************************************************** ihs --><tagDoc id="IHS" usage="req"><gi tei="yes">ihs</gi><name>independent header set</name><desc>contains a set of TEI Headers exchanged independently of
their associated text or group elements.</desc><attList></attList><exemplum><eg><![CDATA[<ihs>
<teiHeader> ... </teiHeader>
<teiHeader> ... </teiHeader>
<teiHeader> ... </teiHeader>
<!-- ... -->
</ihs>]]></eg></exemplum><remarks><p>This element is required.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc>Contains an arbitrary sequence of <gi tei="yes">teiHeader</gi> elements
only.</dataDesc><elemDecl>- O  (teiHeader+)</elemDecl><xref target="SHSTR" type="div1"/><!-- no ref for desc --></tagDoc><?tei:EOF ihs.tag ??><!-- ihs element --><?tei:SOF imprimat.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	imprimat.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************************imprimatur --><tagDoc id="IMPRIMAT" usage="opt"><gi tei="yes">imprimatur</gi><desc>contains a formal statement authorizing the publication of
a work, sometimes required to appear on a title page or its verso.</desc><attList></attList><exemplum><eg><![CDATA[<imprimatur>Licensed and entred acording to Order.]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="TPPARTS"/><dataDesc></dataDesc><elemDecl>- O (%paraContent;)</elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF imprimat.tag ??><!-- imprimatur element --><?tei:SOF imprint.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: imprint.tag,v $
    * Revision 1.5  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.4  94/01/04  12:14:35  lou
    * fix xrefs
    * 
    * Revision 1.3  1993/08/18  21:41:00  msmcq
    * fix typo (extra semicolon) in content model
    * 
    * Revision 1.2  1993/08/03  02:08:13  msmcq
    * change content model
    * --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : change model, use pubPlace, data not m. m. --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-06 : MSM : revise content model                    --><!-- 92-11-09 : MSM : set xref to CObi                        --><!-- *****************************************************imprint --><tagDoc id="IMPRINT" usage="opt"><gi tei="yes">imprint</gi><desc>groups information relating to the publication or distribution
of a bibliographic item.  </desc><attList></attList><exemplum><eg><![CDATA[<imprint><pubPlace>Oxford</pubPlace>
        <publisher>Clarendon Press</publisher>
        <date>1987</date>
</imprint>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc></dataDesc><elemDecl>- O (pubPlace | publisher | date | biblScope)*</elemDecl><xref target="COBICOI"/></tagDoc><?tei:EOF imprint.tag ??><!-- imprint element --><?tei:SOF index.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	index.tag,v $
# Revision 1.2  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : add to class metadata (fix INDEX)       --><!-- 93-01-05 : MSM : correct datatype values on levels 2-4   --><!-- 92-12-07 : MSM : change xref to COnoix                   --><!-- 92-11-09 : MSM : set xref to COmi                        --><!-- **************************************************index --><tagDoc id="INDEX" usage="opt"><gi tei="yes">index</gi><name>index entry</name><desc>marks a location to be indexed for whatever purpose.</desc><attList><!-- .................................................. index --><attDef usage="opt"><attName>index</attName><name>index number</name><desc>indicates which index (of several) the index entry belongs to.</desc><datatype>CDATA</datatype><valDesc>any string of characters; valid values are
application-dependent.</valDesc><default>#IMPLIED</default><remarks><p>This attribute makes it possible to create multiple
indices for a text.</p></remarks></attDef><!-- ................................................. level1 --><attDef usage="req"><attName>level1</attName><name>first-level index entry</name><desc>gives the form under which the index entry is to be made.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#REQUIRED</default><remarks><p>At least one level of entry is required.</p></remarks></attDef><!-- ................................................. level2 --><attDef usage="opt"><attName>level2</attName><name>second-level index entry</name><desc>gives the second-level form, if any.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#IMPLIED</default></attDef><!-- ................................................. level3 --><attDef usage="opt"><attName>level3</attName><name>third-level index entry</name><desc>gives the third-level form, if any.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#IMPLIED</default></attDef><!-- ................................................. level4 --><attDef usage="opt"><attName>level4</attName><name>fourth-level index entry</name><desc>gives the fourth-level form, if any.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[David's other principal backer, Josiah ha-Kohen
<index level1='Josiah ha-Kohen b. Azarya'
       level2='cousin and backer of David b. Daniel'>
b. Azarya, son of one of the last gaons of Sura,
<index level1='Azarya' level2='gaon of Sura'>
<index level1='Sura'>
was David's own first cousin.]]></eg></exemplum><part type="top" name="core"/><classes names="METADATA"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="CONOIX"/></tagDoc><?tei:EOF index.tag ??><!-- index element --><?tei:SOF inode.tag ??><!-- ********** InODE                                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	inode.tag,v $
# Revision 1.5  93/09/22  19:09:25  msmcq
# As of chapter publication
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/09  19:09:38  msmcq
# restore RCS id, log
# --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : outDegr[ee   full word                  --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version                       --><!--                   replace LABEL and FS content by        --><!--                       value= and label=                  --><!--                   eliminate special drawing attributes   --><!--                       (use rend=)                        --><!-- ********** InODE                                         --><tagDoc id="INODE" usage="rwa"><gi tei="yes">iNode</gi><name>intermediate (or internal) node</name><desc>represents an intermediate (or internal) node of a tree.</desc><attList><attDef id="INLAB" usage="opt"><attName>label</attName><desc>gives a label for an intermediate node.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef id="INVALUE" usage="rwa"><attName>value</attName><desc>provides the value of an intermediate node, which is a feature
structure or other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier of a feature structure or other analytic
element.</valDesc><default>#IMPLIED</default></attDef><attDef id="INCHILD" usage="req"><attName>children</attName><desc>provides a list of IDs of the elements which are the children of
the intermediate node.</desc><datatype>IDREFS</datatype><valDesc>A list of IDs.</valDesc><default>#REQUIRED</default></attDef><attDef id="INPAR" usage="opt"><attName>parent</attName><desc>provides the ID of the element which is the parent of this node.</desc><datatype>IDREF</datatype><valDesc>The ID of the parent node.</valDesc><default>#IMPLIED</default></attDef><attDef id="INORD" usage="opt"><attName>ord</attName><desc>indicates whether or not the internal node is ordered.</desc><datatype>(Y | N)</datatype><valList type="closed"><val>Y</val><desc>indicates that the children of the intermediate node are ordered.</desc><val>N</val><desc>indicates that the children of the intermediate node are unordered.</desc></valList><default>#IMPLIED</default><remarks><p>Use if and only if <att tei="yes">ord=partial</att> is specified on the
<gi tei="yes">tree</gi> tag and the intermediate node has more than one child.</p></remarks></attDef><attDef id="INFOL" usage="rwa"><attName>follow</attName><desc>provides an ID of the element which this node follows.</desc><datatype>IDREF</datatype><valDesc>An ID of another intermediate node or leaf of the tree.</valDesc><default>#IMPLIED</default><remarks><p>If the tree is unordered or partially ordered, this attribute
has the property of fixing the relative order of the intermediate node
and the element which is the value of the attribute.</p></remarks></attDef><attDef id="INOUTDG" usage="opt"><attName>outDegree</attName><desc>gives the out degree of an intermediate node, the number of its
children.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default><remarks><p>The in degree of an intermediate node is always 1.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<iNode label=PT id=PT1 parent=VB1 children=up1 outDegree=1 follow=PN1>]]></eg></exemplum><part type="top" name="graphs"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="GDTR" type="div2"/></tagDoc><?tei:EOF inode.tag ??><!-- iNode element --><?tei:SOF interact.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: interact.tag,v $
    * Revision 1.2  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* interact --><tagDoc id="INTERACT" usage="opt"><gi tei="yes">interaction</gi><desc>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.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>specifies whether or not there is any interaction between
  active and passive participants in the text.
   </desc><datatype>(none|partial|complete|inapplicable)
   </datatype><valList type="closed"><val>none</val><desc>no interaction of any kind, e.g. a monologue
  </desc><val>partial</val><desc>some degree of interaction, e.g. a monologue
    with set responses
  </desc><val>complete</val><desc>complete interaction, e.g. a face to
    face conversation
  </desc><val>inapplicable</val><desc>this parameter is inappropriate or inapplicable
    in this case
   </desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>active
   </attName><desc>specifies the number of active participants
   (or <term>addressors</term>) producing parts of the text.
   </desc><datatype>CDATA
   </datatype><valList type="closed"><val>singular</val><desc>a single addressor
  </desc><val>plural</val><desc>many addressors
  </desc><val>corporate</val><desc>a corporate addressor
  </desc><val>unknown</val><desc>number of addressors unknown or unspecifiable
   </desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>passive
   </attName><desc>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.
   </desc><datatype>CDATA
   </datatype><valList type="semi"><val>self</val><desc>text is addressed to the originator e.g. a diary
  </desc><val>single</val><desc>text is addressed to one other person e.g. a
    personal letter
  </desc><val>many</val><desc>text is addressed to a countable number of others
    e.g. a conversation in which all participants are identified
  </desc><val>group</val><desc>text is addressed to an undefined but fixed
    number of participants  e.g. a lecture
  </desc><val>world</val><desc>text is addressed to an undefined and indeterminately
    large number e.g. a published book
   </desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <!-- An informal conversation:  -->
  <interaction type=complete active=plural passive=many>]]></eg></exemplum><exemplum><eg><![CDATA[  <!-- A formal lecture:   -->
  <interaction type=none active=singular passive=group>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF interact.tag ??><!-- interaction element --><?tei:SOF interp.tag ??><!-- ************************************************* interp --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	interp.tag,v $
# Revision 1.4  94/02/27  15:55:49  lou
# Revisions for publication of AI
# 
# Revision 1.3  1993/11/26  18:16:08  msmcq
# MSM changes pre-publicatino
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 26 feb: add to clinterp and metadata classes --><!-- 93-11-26 : MSM : change resp att to INHERITED            --><!-- 93-11-23 : MSM : change NAME att to TYPE                 --><!-- 93-07-22 : DTL : create (prune definition of SPAN)       --><!--                                                          --><!-- ************************************************* interp --><tagDoc id="INTERP" usage="opt"><gi tei="yes">interp</gi><name>interpretation</name><desc>provides for an interpretative annotation which can be
linked to a span of text.</desc><attList><attDef usage="req"><attName>value</attName><desc>identifies the specific phenomenon being annotated.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#REQUIRED</default></attDef></attList><exemplum><eg><![CDATA[<interp resp=TMA type='structural unit' value='aftermath'>]]></eg></exemplum><part type="top" name="ana"/><classes names="METADATA CLINTERP"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="AISP" type="div2"/></tagDoc><?tei:EOF interp.tag ??><!-- interp element --><?tei:SOF interpgp.tag ??><!-- ********************************************* interpGrp  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	interpgp.tag,v $
# Revision 1.2  94/02/27  15:55:50  lou
# Revisions for publication of AI
# 
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 26 feb: add to clinterp and metadata classes --><!-- 93-07-22 : DTL : create (modify definition of SPANgRP)   --><!--                                                          --><!-- ********************************************* interpGrp  --><tagDoc id="INTERPGP" usage="opt"><gi tei="yes">interpGrp</gi><name>interpretation group</name><desc>collects together <gi tei="yes">interp</gi> tags.</desc><attList></attList><exemplum><eg><![CDATA[<interpGrp resp=TMA type='collection of structural units'>
 <interp value='introduction'>
 <interp value='conflict'>
 <interp value='climax'>
 <interp value='revenge'>
 <interp value='reconciliation'>
 <interp value='aftermath'>
 </interpGrp>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLINTERP METADATA"/><dataDesc>Any number of <gi tei="yes">interp</gi> elements.</dataDesc><elemDecl>- - ((interp)*)</elemDecl><xref target="AISP"/></tagDoc><?tei:EOF interpgp.tag ??><!-- interpGrp element --><?tei:SOF interptn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	interptn.tag,v $
# Revision 1.2  94/03/23  18:25:06  msmcq
# de-russify syntax, as per PR
# 
# Revision 1.1  1994/01/04  13:14:03  lou
# Initial revision
# --><!-- Revisions:                                               --><!-- 29 dec 93: LB : renamed (was "ANALYSIS")                 --><!-- 93-03-08 : MSM : add to class declabl                    --><!-- 93-02-10 : MSM : change target of xref                   --><!-- 92-12-09 : MSM : suppress word 'interpretative'          --><!-- 92-11-25 : MSM : correct error in end of EG              --><tagDoc id="INTERPTN" usage="opt"><gi tei="yes">interpretation</gi><desc>describes the scope of any analytic or interpretive information
added to the text in addition to the transcription. </desc><attList></attList><exemplum><eg><![CDATA[<interpretation>
  <p>The part of speech analysis applied throughout section 4 was
  added by hand and has not been checked]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/></tagDoc><?tei:EOF interptn.tag ??><!-- interpretation element --><?tei:SOF item.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	item.tag,v $
# Revision 1.2  94/01/04  13:17:09  lou
# *** empty log message ***
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : suppress memberhip in lists class       --><!-- 92-12-09 : MSM : change content desc                     --><!-- 92-12-07 : MSM : change content to specialPara           --><!-- ******************************************************** item --><tagDoc id="ITEM" usage="rwa"><gi tei="yes">item</gi><desc>contains one component of a list.</desc><attList><attDef id="ITEM.n" usage="opt"><attName>n</attName><name>name or number</name><desc>indicates the number (or letter, or other enumerator) borne by this
list item in the copy text.</desc><datatype>CDATA</datatype><valDesc>Whatever string of characters is used to label a list item in
the copy text may be used as the value of <att tei="yes">n</att>, but it is not
required that numbering be recorded explicitly.</valDesc><default>#IMPLIED</default><remarks><p>In ordered lists, the <att tei="yes">n</att> attribute on the
<gi tei="yes">item</gi> element is by definition synonymous with the use of the
<gi tei="yes">label</gi> element to record the enumerator of the list item.  In
glossary lists, however, the term being defined should be given with the
<gi tei="yes">label</gi> element, not <att tei="yes">n</att>.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<list type=ordered>
<head>Here begin the chapter headings of Book IV</head>
<item n='4.1'>The death of Queen Clotild.
<item n='4.2'>How King Lothar wanted to appropriate
     one third of the Church revenues.
<item n='4.3'>The wives and children of Lothar.
<item n='4.4'>The Counts of the Bretons.
<item n='4.5'>Saint Gall the Bishop.
<item n='4.6'>The priest Cato.
<item> ...
</list>]]></eg></exemplum><part type="top" name="core"/><classes/><dataDesc>May contain simple prose or a sequence of chunks.</dataDesc><elemDecl> - O (%specialPara;)</elemDecl><xref target="COLI" type="div2"/><xref target="HD6"/></tagDoc><?tei:EOF item.tag ??><!-- item element --><?tei:SOF itype.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	itype.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to morph class                      --><!-- 94-01-12 : MSM : suppress dleaves class                  --><!-- 94-01-12 : MSM : note synonymy with GRAM element         --><!-- 93-06-04 : MSM : supply default                          --><!-- ************************************************* itype  --><tagDoc id="ITYPE" usage="opt"><gi tei="yes">itype</gi><name>inflectional class</name><desc>indicates the inflectional class associated with a lexical item.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>indicates the type of indicator used to specify the inflection
class, when it is necessary to distinguish between the usual abbreviated
indications (e.g. <q>inv</q>) and other kinds of indicators, such as
special codes referring to conjugation patterns, etc.</desc><datatype>CDATA</datatype><valList type="open"><val>abbrev</val><desc>abbreviated indicator</desc><val>verb table</val><desc>coded reference to a table of verbs</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type='inflectional
type'</tag>.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="base" name="dict"/><classes names="DIPARTS MORPH DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.  Typical
content will be <q>invariant</q>, <q>n 3</q> etc.</dataDesc><elemDecl>- -  (%paraContent)</elemDecl><xref target="DITPFO" type="div2"/></tagDoc><?tei:EOF itype.tag ??><!-- itype element --><?tei:SOF join.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	join.tag,v $
# Revision 1.6  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.5  1994/03/16  03:45:14  msmcq
# revision of SA as per John Lavagnino
#
# Revision 1.4  1994/02/12  10:45:35  lou
# revns for publicn P3
#
# Revision 1.3  1994/01/14  18:37:54  lou
# fix typo (end of comment deimiter missing)
#
# Revision 1.2  1994/01/07  20:30:34  msmcq
# Merge Terry Langendoen's revisions of summer 1993
# rename PARTS as TARGETS as per Eynsham and DTL
# add INCL attribute to resolve a conundrum
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 94-03-15 : MSM : correct tagging slip                    --><!-- 94-03-15 : MSM : add DESC attribute                      --><!-- 94-03-15 : MSM : restore targRoot, renamed SCOPE         --><!--                  restore examples showing use of SCOPE   --><!-- 7 dec 94: LB commit murder on various attributes --><!-- 94-01-07 : MSM : accept DTL's renaming of PARTS as TARGETS --><!-- 94-01-07 : MSM : add targRoot attribute                  --><!-- 93-01-26 : MSM : change DESCs                            --><!-- ********************************************************** join --><tagDoc id="JOIN" usage="opt"><gi tei="yes">join</gi><desc>identifies a possibly fragmented segment of text, by pointing
at the possibly discontiguous elements which compose it.</desc><attList><attDef usage="req"><attName>targets</attName><desc>specifies the SGML identifiers of the elements or passages
       to be joined into a virtual element.</desc><datatype>IDREFS</datatype><valDesc>Each value specified must be the same as that specified as
    value for an <att tei="yes">ID</att> attribute for some other element in the
    current SGML document.</valDesc><default>#REQUIRED</default></attDef><attDef usage="opt"><attName>result</attName><desc>specifies the name of an element
which this aggregation
may be understood to represent.</desc><datatype>NAME</datatype><valDesc>The generic identifier of an element in the current DTD.</valDesc><default>%INHERITED</default></attDef><!-- ................................................... desc --><attDef usage="opt"><attName>desc</attName><name>description</name><desc>a brief phrase describing the virtual element created by the join.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>%INHERITED</default><remarks><p>The <att tei="yes">desc</att> attribute may be used to give a
brief description of the virtual element, if its content or function
are not obvious.</p></remarks></attDef><!-- ............................. (targRoot, rootIncl) scope --><attDef usage="rec"><attName>scope</attName><desc>indicates whether the targets to be joined include the
entire element indicated (the entire subtree including its root),
or just the children of the target (the branches of the subtree).</desc><datatype>(root | branches)</datatype><valList type="closed"><val>root </val><desc>the rooted subtrees indicated by the <att tei="yes">targets</att>
attribute are joined, each subtree become a child of the virtual
element created by the <gi tei="yes">join</gi></desc><val>branches </val><desc>the children of the subtrees indicated by the
<att tei="yes">targets</att> attribute become the children of the virtual element
(i.e. the roots of the subtrees are discarded)</desc></valList><default>root</default><eg><![CDATA[ <list><head>Authors</head>
   <item id=UF>Figge, Udo
   <item id=CH>Heibach, Christiane
   <item id=GH>Heyer, Gerhard
   <item id=BP>Philipp, Bettina
   <item id=MS>Samiec, Monika
   <item id=SS>Schierholz, Stefan
 </list>
 <!-- elsewhere ...  -->
 <join result='list' targets='ch bp ss' scope=root
       desc='Heidelberger authors'>]]></eg><!-- authors in Sprache und Datenverarbeitung 13.2 (1989).    --><remarks><p>In this example, the text contains a list of authors of
articles in a journal; the <gi tei="yes">join</gi> element is used to
join into one virtual list the names of the authors who reside in
Heidelberg.</p></remarks></attDef><attDef usage="opt"><attName>targOrder</attName><desc>specifies whether or not the order in which components of the
join are listed on the <att tei="yes">targets</att> attribute is significant.
 </desc><datatype>(Y | N | U)</datatype><valList type="closed"><val>Y</val><desc>Yes: the order
         should be followed when combining the
         targeted elements.
  </desc><val>N </val><desc>No: the order
         has no significance when combining the
         targeted elements.
  </desc><val>U </val><desc>Unspecified: the order
         may or may not be significant.
  </desc></valList><default>Y</default><remarks><p>This attribute has a different default value on this
element from that which it has for other members of the pointer
class.</p></remarks></attDef></attList><!-- transplanted discussion to text (LB) --><exemplum><p>The following example is discussed in section<xref target="SAAG"/>
.</p><eg><![CDATA[ <sp who='Hughie'><p>How does it go?
   <q><l id=X1>da-da-da
      <l id=L2>gets a new frog
      <l>...
   </q></p>
 <sp who='Louie'><p><q><l id=L1>When the old pond</l> ...</q></p>
 <sp who='Dewey'><p><q>... <l id=L3>It's a new pond.</l></q></p>
 <!-- ... -->
 <join result=lg targets='L1 L2 L3' scope=root
       desc='haiku'>
 <!-- a famous haiku by Bashoo, in an eccentric translation -->]]></eg><p>The attribute <att tei="yes">targOrder</att> is specified with a
value of <q>Y</q> to indicate that the order of the three
lines is significant.  The attribute <att tei="yes">scope</att> is
allowed to take the default value of <q>root</q> to
indicate that the virtual element being identified is a line
group (<gi tei="yes">lg</gi>) which contains the three <gi tei="yes">l</gi>
elements L1, L2, and L3, and not just their character data
content.</p></exemplum><exemplum><p>In this example, the attribute <att tei="yes">scope</att> is
specified with the value of <q>branches</q> to indicate that
the virtual list being constructed is to be made by taking the lists
indicated by the <att tei="yes">targets</att> attribute of the <gi tei="yes">join</gi>
element, discarding the <gi tei="yes">list</gi> tags which enclose them, and
combining the items contained within the lists into a single virtual
list.</p><eg><![CDATA[<s>Southern dialect (my own variety, at least) has only
<list id=LP1>
<item><s>I done gone</s></item>
<item><s>I done went</s></item>
</list>
whereas Negro Non-Standard basilect has both these and
<list id=LP2>
<item><s>I done go</s></item>.
</list></s>
<s>White Southern dialect also has
<list id=LP3>
<item><s>I've done gone</s></item>
<item><s>I've done went</s></item>
</list>
which, when they occur in Negro dialect, should probably be
considered as borrowings from other varieties of English.</s>
<!-- ... -->
<join result=list id=LST1 parts='lp1 lp2 lp3' scope=branches
      desc='Sample sentences in Southern speech'>]]></eg></exemplum><part type="top" name="links"/><classes names="POINTER METADATA"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="SAAG" type="div2"/></tagDoc><?tei:EOF join.tag ??><!-- join element --><?tei:SOF joingrp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	joingrp.tag,v $
# Revision 1.5  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.4  1994/03/16  03:45:14  msmcq
# revision of SA as per John Lavagnino
# --><!-- *********************************************** joinGrp  --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 94-03-15 : MSM : add DESC                                --><!-- 94-03-15 : MSM : Added RCS id                            --><!-- 93-07-22 : DTL : create, based on definition of linkGrp  --><!-- *********************************************** joinGrp  --><tagDoc id="JOINGRP" usage="opt"><gi tei="yes">joinGrp</gi><name>join group</name><desc>groups a collection of <gi tei="yes">join</gi> elements and possibly
pointers.</desc><attList><attDef usage="opt"><attName>result</attName><desc>describes the result of the joins gathered in this collection.</desc><datatype>CDATA</datatype><valDesc>where specified on a <gi tei="yes">joinGrp</gi> element, it supplies the
default value for the <att tei="yes">result</att> on each <gi tei="yes">join</gi> included
within the group.</valDesc><default>#IMPLIED</default></attDef><!-- ................................................... desc --><attDef usage="opt"><attName>desc</attName><name>description</name><desc>a brief phrase describing the virtual elements created by the joins
in this collection.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>The <att tei="yes">desc</att> attribute may be used to give a
brief description of the virtual elements jointed in this
<gi tei="yes">joinGrp</gi> if their function and significance
are not obvious.</p></remarks></attDef><!-- <attDef usage=opt> --><!-- <attName>targFunc --><!-- <desc>lists the functions of the individual targets. --><!-- <datatype>NAMES --><!-- <valDesc>descriptions of the functions of the targets. --><!-- <default>'first.part next.part' --><!-- <remarks><p>The <att>targFunc</att> attribute is one of the
attributes --><!-- assigned to elements of the grouper class.  It is specifically
defined --><!-- here so that it may be assigned a default value. --><!-- </attDef> --></attList><exemplum><eg><![CDATA[<joinGrp result='q' targType='q' domains='zuitxt' >
  <join targets='zuiq1 zuiq2 zuiq6'>
  <join targets='zuiq3 zuiq4 zuiq5'>
</joinGrp>]]></eg></exemplum><part type="top" name="link"/><!-- Where contained?  Part of header?  --><classes names="PTRGROUP METADATA"/><dataDesc>Any number of joins, pointers or extended pointers.</dataDesc><elemDecl>- - ((join | ptr | xptr)*)</elemDecl><xref target="SAAG"/></tagDoc><?tei:EOF joingrp.tag ??><!-- joinGrp element --><?tei:SOF keywords.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	keywords.tag,v $
# Revision 1.2  94/01/05  16:57:38  lou
# extirpate mixed content!
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- *****************************************************keywords --><tagDoc id="KEYWORDS" usage="opt"><gi tei="yes">keywords</gi><name>Keywords</name><desc>contains a list of keywords or phrases identifying the topic or
nature of a text.</desc><attList><attDef usage="req"><attName>scheme
   </attName><desc>identifies the controlled vocabulary within which the set of
  keywords concerned is defined.
   </desc><datatype>IDREF
   </datatype><valDesc>identifier of the associated <gi tei="yes">taxonomy</gi> element
    </valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<keywords scheme=BL>
    <list><item>Babbage, Charles
  <item>Mathematicians - Great Britain - Biography
     </list>
</keywords>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o (term+ | list)</elemDecl><xref target="HD43"/></tagDoc><?tei:EOF keywords.tag ??><!-- keywords element --><?tei:SOF kinesic.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	kinesic.tag,v $
# Revision 1.5  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.4  1994/02/17  21:06:08  msmcq
# make WHO attribute inherit, as per text (for SC version of P3)
#
# Revision 1.3  1994/01/04  12:14:36  lou
# fix xrefs
#
# Revision 1.2  1993/09/21  11:08:21  lou
# added to spoken class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 94-02-14 : MSM : change desc                             --><!-- 94-02-14 : MSM : make who INHERITED                      --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************ kinesic --><tagDoc id="KINESIC" usage="rec"><gi tei="yes">kinesic</gi><name>Non-vocalized quasi-lexical</name><desc>any communicative phenomenon, not necessarily vocalized, for
example a gesture, frown, etc.</desc><attList><attDef usage="opt"><attName>who</attName><desc>supplies an identifier for the participant performing the
         gesture.
         Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
         or <tag compl="full" tei="yes">participant.grp</tag> element in the TEI header.</desc><datatype>IDREF</datatype><valDesc>Must identify a participant or participant group within the
       TEI Header</valDesc><default>%INHERITED</default></attDef><attDef usage="opt"><attName>iterated</attName><name>iterated</name><desc>indicates whether or not the phenomenon is repeated.</desc><datatype>(y | n | u)</datatype><valList type="open"><val>y </val><desc>the phenomenon is repeated.
    </desc><val>n </val><desc>the phenomenon is atomic.
    </desc><val>u </val><desc>unknown or unmarked.
    </desc></valList><default>n</default></attDef><attDef usage="opt"><attName>desc</attName><name>description</name><desc>supplies a conventional representation for the phenomenon.
    </desc><datatype>CDATA</datatype><valDesc>a description or representation of the phenomenon
        chosen from a semi-closed list</valDesc><default>#IMPLIED</default><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[    <kinesic iterated=Y desc="shaking head vigorously" dur="1.5secs">]]></eg></exemplum><remarks></remarks><part type="base" name="ts"/><classes names="COMPSPOK TIMED"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TSBAFD"/><xref target="TSBA"/><xref target="TSBAVO"/></tagDoc><?tei:EOF kinesic.tag ??><!-- kinesic element --><?tei:SOF l.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	l.tag,v $
# Revision 1.6  94/01/04  12:14:37  lou
# fix xrefs
# 
# Revision 1.5  1993/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
#
# Revision 1.4  1993/09/16  15:56:49  msmcq
# changes a propos of TD:
# restore to class chunk
# paraContent
#
# Revision 1.3  1993/08/12  20:43:40  msmcq
# change content model to paraContent
#
# Revision 1.2  1993/08/11  13:03:24  lou
# changes for compatibility with VE
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-11-12 : MSM : add to enjamb class                     --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-14 : MSM : restore class chunk                     --><!-- 12 Aug 93 : MSM : change model (was phrase.seq)          --><!-- 8 aug 93: LB: added to compvers class                    --><!-- 92-12-10 : MSM : change class to CHUNK, after disc w/LB  --><!-- 92-12-09 : MSM : assign to class coreverse               --><!-- 92-12-09 : MSM : rename metre as met                     --><!-- 92-12-07 : MSM : fix problem at end of EG                --><!-- 92-12-07 : MSM : change xref to COve                     --><!-- ****************************************************** l --><tagDoc id="L" usage="mwa"><gi tei="yes">l</gi><name>verse line</name><desc>contains a single, possibly incomplete, line of verse.</desc><attList><attDef usage="mwa"><attName>part</attName><desc>specifies whether or not the line is metrically complete. </desc><datatype>(Y | N | I | M | F)</datatype><valList type="closed"><val>Y</val><desc>the line is metrically incomplete</desc><val>N</val><desc>either the line is complete, or no claim is made as to its
completeness</desc><val>I</val><desc>the initial part of an incomplete line</desc><val>M</val><desc>a medial part of an incomplete line</desc><val>F</val><desc>the final part of an incomplete line</desc></valList><default>N</default><remarks><p>The values I, M, or F should be used only where it is
clear how the line is to be reconstituted.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<l part=Y met='-/-/-/-/-/'>]]></eg></exemplum><part type="base" name="verse"/><classes names="CHUNK METRICAL ENJAMB"/><dataDesc>contains character data or phrase level elements
only</dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="COVE"/><xref target="CODV"/><xref target="DRPAL"/></tagDoc><?tei:EOF l.tag ??><!-- l element --><?tei:SOF label.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: label.tag,v $
    * Revision 1.2  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- ******************************************************* label --><tagDoc id="LABEL" usage="rwa"><gi tei="yes">label</gi><desc>contains the label associated with an item in a list; in
glossaries, marks the term being defined.</desc><attList></attList><exemplum><p>Labels are most commonly used for the headwords in glossary
lists; note the use of the global <att tei="yes">lang</att> attribute to set the
default language of the glossary list to Middle English, and identify
the glosses and headings as modern English or Latin.</p><eg><![CDATA[<list type=gloss lang=ME>
<head lang=EN>Vocabulary</head>
<headLabel lang=EN>Middle English</headLabel>
<headItem lang=EN>New English</headItem>
<label>nu</label><item lang=EN>now</item>
<label>lhude</label><item lang=EN>loudly</item>
<label>bloweth</label><item lang=EN>blooms</item>
<label>med</label><item lang=EN>meadow</item>
<label>wude</label><item lang=EN>wood</item>
<label>awe</label><item lang=EN>ewe</item>
<label>lhouth</label><item lang=EN>lows</item>
<label>sterteth</label><item lang=EN>bounds, frisks
		(cf. <cit>Chaucer, <ref>K.T.644</ref>:
                <q>a courser, <term>sterting</term>
                 as the fyr</q></cit></item>
<label>verteth	 </label><item lang=LA>pedit</item>
<label>murie</label><item lang=EN>merrily</item>
<label>swik</label><item lang=EN>cease</item>
<label>naver</label><item lang=EN>never</item>
</list>]]></eg></exemplum><exemplum><p>Labels may also be used to record explicitly the numbers or
letters which mark list items in ordered lists, as in this extract from
Gibbon's <title>Autobiography</title>.  In this usage the <gi tei="yes">label</gi>
element is synonymous with the <att tei="yes">n</att> attribute on the
<gi tei="yes">item</gi> element.</p><eg><![CDATA[I will add two facts, which have seldom occurred in
the composition of six, or at least of five quartos.
<list type=ordered rend=runon>
<label>(1) </label><item>My first rough manuscript, without any
intermediate copy, has been sent to the press.</item>
<label>(2) </label><item>Not a sheet has been seen by any human
eyes, excepting those of the author and the printer:
the faults and the merits are exclusively my own.</item>
</list>]]></eg></exemplum><exemplum><p>Labels may also be used for other structured list items, as
in this extract from the journal of Edward Gibbon:</p><eg><![CDATA[<list type=gloss>
<label>March 1757.</label><item>I wrote some critical observations
upon Plautus.</item>
<label>March 8th.</label><item>I wrote a long dissertation upon
some lines of Virgil.</item>
<label>June.</label><item>I saw Mademoiselle Curchod --
<q lang=LA>Omnia vincit amor, et nos cedamus amori.</q></item>
<label>August.</label><item>I went to Crassy, and staid two days.</item>
</list>]]></eg></exemplum><exemplum><eg><![CDATA[<list type=gloss>
<label>The fourth volume of the <title>History of the
Decline and Fall of the Roman Empire</title></label>
<item>begun March 1, 1782 -- ended June, 1784.</item>
<label>The fifth volume</label>
<item>begun July, 1784 -- ended May 1, 1786.</item>
<label>The sixth volume</label>
<item>begun May 18, 1786 -- ended June 27, 1787.</item>
</list>]]></eg></exemplum><part type="top" name="core"/><classes names="LISTS"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- o  (%phrase.seq;)</elemDecl><xref target="COLI" type="div2"/></tagDoc><?tei:EOF label.tag ??><!-- label element --><?tei:SOF lacend.tag ??><!-- Revisions:                                               --><!-- 94-03-29 : MSM : add to class fragment                   --><!-- 94-02-03 : MSM : clean gi                                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lacend.tag,v $
# Revision 1.4  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.3  1994/03/21  14:33:09  lou
# second major typo purge
#
# Revision 1.2  1994/02/07  20:56:16  msmcq
# revsisions for P3
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY lacend   system 'lacend.tag' --><!-- lacuna.end tag
--><!-- ********************************************* lacuna.end --><tagDoc id="LACEND" usage="opt"><gi tei="yes">lacunaEnd</gi><desc>indicates the end of a lacuna in a mostly complete textual
witness.</desc><attList></attList><exemplum><eg><![CDATA[<rdg wit=X><lacunaEnd>auctorite</rdg>]]></eg></exemplum><remarks><p> (optional)</p></remarks><part type="top" name="tc"/><classes names="FRAGMENT"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="TCAPMI"/></tagDoc><?tei:EOF lacend.tag ??><!-- lacunaEnd element --><?tei:SOF lacstart.tag ??><!-- Revisions:                                               --><!-- 94-03-29 : MSM : add to class fragment                   --><!-- 94-02-03 : MSM : clean gi                                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lacstart.tag,v $
# Revision 1.3  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.2  1994/02/07  20:56:16  msmcq
# revsisions for P3
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY lacstart system 'lacstart.tag' --><!-- lacuna.start
tag --><!-- ******************************************* lacuna.start --><tagDoc id="LACSTART" usage="opt"><gi tei="yes">lacunaStart</gi><desc>indicates the beginning of a lacuna in the text of a mostly
complete textual witness.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p> (optional)</p></remarks><part type="top" name="tc"/><classes names="FRAGMENT"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="TCAPMI"/></tagDoc><?tei:EOF lacstart.tag ??><!-- lacunaStart element --><?tei:SOF lang.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : correct example                         --><!-- 94-01-13 : MSM : remove from diparts to avoid ambiguity  --><!-- 94-01-12 : MSM : suppress dleaves class                  --><!-- 94-01-09 : MSM : suppress duplicate membership in DATA   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lang.tag,v $
# Revision 1.2  94/01/15  20:53:57  msmcq
# msmcq revision of DI for P3.  Consult comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************** lang --><tagDoc id="LANG" usage="rec"><gi tei="yes">lang</gi><name>language name</name><desc>name of a language mentioned in etymological or other linguistic
discussion.</desc><attList></attList><exemplum><eg><![CDATA[<entry>
    <form><orth>publish</orth> ... </form>
    <etym><lang>ME.</> <mentioned>publisshen</>,
        <lang>F.</> <mentioned>publier</>,
        <lang>L.</> <mentioned>publicare, publicatum</>.
        <xr>See <ref>public</>; cf. <ref>2d -ish</>.</xr>
    </etym>
    <!-- ... -->
</entry>]]>
(From:  <citation>Webster's Second International</citation>)</eg></exemplum><part type="base" name="dict"/><classes names="DATA DIGLOBAL"/><dataDesc>May contain character data mixed with phrase-level elements.</dataDesc><elemDecl>- -  (%paraContent)</elemDecl><xref target="DITPET" type="div2"/></tagDoc><?tei:EOF lang.tag ??><!-- lang element --><?tei:SOF langknow.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: langknow.tag,v $
    * Revision 1.3  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.2  94/08/29  15:23:27  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix LANGKNOW, define as member of demographic --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *********************************************** langknow --><tagDoc id="LANGKNOW" usage="opt"><gi tei="yes">langKnown</gi><name>linguistic competence</name><desc>contains an informal description of a person's competence in
different languages, dialects, etc.</desc><attList></attList><exemplum><eg><![CDATA[  <langKnown>Spoken French</langKnown>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc>May contain character data and phrase-level
elements.</dataDesc><elemDecl> - - (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF langknow.tag ??><!-- langKnown element --><?tei:SOF wsdlang.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdlang.tag,v $
# Revision 1.3  94/03/21  14:33:13  lou
# second major typo purge
# 
# Revision 1.2  1994/01/04  12:15:45  lou
# fix xrefs
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *********************************************** language --><tagDoc id="WSDLANG" usage="req"><gi tei="yes">language</gi><desc>identifies the language being described in the writing system
declaration.</desc><attList><!-- ................................................. iso639 --><attDef usage="req"><attName>iso639</attName><desc>gives the standard language code from ISO 639.</desc><datatype>CDATA</datatype><valDesc>any two- or three-letter code included included in ISO 639; if
the language is not included in the list in ISO 639, the value should be
given as the empty string.</valDesc><default>#REQUIRED</default><remarks></remarks></attDef></attList><exemplum><eg><![CDATA[<language iso639=''>Various</language> 
<language iso639=GRC>Classical Greek</language>]]></eg></exemplum><remarks><p>In general, the <soCalled>language</soCalled>
associated with a given writing system declaration will be a
natural language; it may however be a dialect, an artificial
language, or some other semiotic system conveniently treated as a
language.
 </p><p>The content of the <gi tei="yes">language</gi> element is a
description in prose of what language the WSD describes.
Usually this will simply be the conventional name of the
language; more information may however be included as needed.
 </p><p>Specialized writing system declarations which document a public
character set or entity set suitable for encoding several languages, and
which are intended for use as a base component within other
language-specific writing system declarations, should identify the
<gi tei="yes">language</gi> to which they apply as <q>Various</q>.  Such writing
systems should <emph>not</emph> be used directly by encoded texts; they
should be named only in the <gi tei="yes">baseWsd</gi> element of
language-specific writing system declarations.</p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain character data only.</dataDesc><elemDecl>- O  (#PCDATA)</elemDecl><xref target="WDLA"/><xref target="WDOV"/></tagDoc><?tei:EOF wsdlang.tag ??><!-- language element (for WSD) --><?tei:SOF language.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	language.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- *****************************************************language --><tagDoc id="LANGUAGE" usage="rec"><gi tei="yes">language</gi><desc>characterizes a single language or sublanguage used within a text.</desc><attList><attDef usage="opt"><attName>id
   </attName><desc>specifies the identifier for the <term>writing system
declaration</term> for this language (e.g. <term>eng</term>,
<term>fra</term>, <term>deu</term>)
   </desc><datatype>ID
   </datatype><valDesc>should usually be a language identifier from ISO 639.
   </valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>wsd
   </attName><desc>specifies the entity containing the <term>writing system
   declaration</term> used for representing texts in this language.
   </desc><datatype>ENTITY
   </datatype><valDesc>must be the name of an entity containing a full writing
system declaration
   </valDesc><default>#IMPLIED
   </default><remarks><p>The entity containing the writing system declaration will
typically be an external file; it must be declared in the DTD.</p></remarks></attDef><attDef usage="opt"><attName>usage
   </attName><desc>specifies the approximate percentage (by volume) of the text
which uses this language.
   </desc><datatype>NUMBER
   </datatype><valDesc>a whole number between 1 and 100
   </valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<language wsd=LA usage=100>Pig Latin]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc>Particularly for sublanguages, an informal prose
characterization should be supplied as content for the element in
addition to the specification implied by the WSD</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="HD41"/></tagDoc><?tei:EOF language.tag ??><!-- language element --><?tei:SOF langusg.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	langusg.tag,v $
# Revision 1.2  94/01/04  12:14:38  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ***************************************************langUsage --><tagDoc id="LANGUSG" usage="rec"><gi tei="yes">langUsage</gi><name>language usage</name><desc>describes the languages, sublanguages, registers, dialects etc.
represented within a text.</desc><attList></attList><exemplum><eg><![CDATA[   <langUsage>
   <language wsd=FR usage=60>Qu&eacute;becois
   <language wsd=EN usage=20>Canadian business English
   <language wsd=EN usage=20>British English
   </langUsage>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc>may contain either a simple prose description, or more
formally one or more <gi tei="yes">language</gi> elements</dataDesc><elemDecl>- o (p | language)+</elemDecl><xref target="HD41"/><xref target="HD4"/><xref target="CCAS2"/></tagDoc><?tei:EOF langusg.tag ??><!-- langUsage element --><?tei:SOF linebr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	linebr.tag,v $
# Revision 1.3  94/01/04  12:14:39  lou
# fix xrefs
# 
# Revision 1.2  1993/12/20  15:32:19  lou
# changed id to match filename
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 30 dec 93:LB:  make ED #implied not #required --><!-- 93-02-11 : MSM : loc class has id clloc not loc          --><!-- ****************************************************** linebr --><tagDoc id="LINEBR" usage="opt"><gi tei="yes">lb</gi><name>line break</name><desc>marks the start of a new (typographic) line in some
edition or version of a text.</desc><attList><attDef usage="rec"><attName>ed</attName><name>edition</name><desc>indicates the edition or version in which the line break is located
at this point</desc><datatype>CDATA</datatype><valDesc>Any string of characters; usually a siglum conventionally used
for the edition.</valDesc><default>#IMPLIED</default><eg><![CDATA[	<lb ed=Riverside n=123>]]></eg></attDef><attDef usage="opt"><attName>n</attName><name>number or name</name><desc>indicates the number or other value associated with the line
which follows the point of insertion of this <gi tei="yes">lb</gi>.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>Encoders should adopt a clear and consistent policy as to
whether the numbers associated with line breaks relate to the physical
sequence number of the line within the page, or to some aspect of the
logical structure of the text.
By convention, <gi tei="yes">lb</gi> elements should appear at the start of the
line to which they refer.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>Like other forms of milestone tag, <gi tei="yes">lb</gi> tags cannot
be automatically verified by SGML; for better validation, a
concurrent markup stream should be used.</p><p>The <gi tei="yes">lb</gi> tag is intended for making typographic line breaks
in prose. It should be carefully distinguished from the <gi tei="yes">l</gi>
element, used to mark lines of verse.</p></remarks><part type="top" name="core"/><classes names="REFSYS"/><elemDecl>- O EMPTY</elemDecl><xref target="CORS5" type="div3"/><xref target="DRPAL" type="div3"/></tagDoc><?tei:EOF linebr.tag ??><!-- lb element --><?tei:SOF lbl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lbl.tag,v $
# Revision 1.1  94/01/15  21:00:02  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : add TYPE attribute                      --><!-- 94-01-13 : MSM : add to graminfo                         --><!-- 94-01-12 : MSM : made file from frml, trl                --><!-- *************************************************** frml --><tagDoc id="LBL" usage="opt"><gi tei="yes">lbl</gi><name>label</name><desc>in dictionaries, contains a label for a form, example,
translation, or other piece of information, e.g. <q>abbreviation
for</q>, <q>contraction of</q>, <q>literally</q>, <q>approximately</q>,
<q>synonyms:</q>, etc.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the label using any convenient typology.</desc><datatype>CDATA</datatype><valDesc>any string of characters, such as <q>usage</q>, <q>sense
restriction</q>, etc.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Labels specifically relating to usage should be tagged with
the special-purpose <gi tei="yes">usg</gi> element rather than with the generic
<gi tei="yes">lbl</gi> element.</p></remarks><part type="base" name="dict"/><classes names="DIPARTS FORMINFO GRAMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/><xref target="DITPTR"/><xref target="DITPXR"/><xref target="DITPFO"/></tagDoc><?tei:EOF lbl.tag ??><!-- lbl tag  --><?tei:SOF leaf.tag ??><!-- ********** LEAF                                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	leaf.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/09  19:40:55  msmcq
# restore RCS id, log
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version                       --><!--                   replace LABEL and FS content by value= --><!--                       and label=                         --><!--                   eliminate special drawing attributes   --><!--                       (use rend=)                        --><!-- ********** LEAF                                          --><tagDoc id="LEAF" usage="rwa"><gi tei="yes">leaf</gi><desc>encodes the leaves (terminal nodes) of a tree.</desc><attList><attDef id="LFLAB" usage="opt"><attName>label</attName><desc>gives a label for a leaf.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef id="LFVALUE" usage="rwa"><attName>value</attName><desc>provides the value of a leaf, which is a feature
structure or other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier of a feature structure or other analytic
element.</valDesc><default>#IMPLIED</default></attDef><attDef id="LFPAR" usage="opt"><attName>parent</attName><desc>provides the ID of parent of a leaf.</desc><datatype>IDREF</datatype><valDesc>The ID of the parent node.</valDesc><default>#IMPLIED</default></attDef><attDef id="LFFOL" usage="rwa"><attName>follow</attName><desc>provides an ID of an element which this leaf follows.</desc><datatype>IDREF</datatype><valDesc>An ID of another intermediate node or leaf of the tree.</valDesc><default>#IMPLIED</default><remarks><p>If the tree is unordered or partially ordered, this
attribute has the property of fixing the relative order of the leaf and
the element which is the value of the attribute.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<leaf id=PERI1 parent=N1 label=periscope>]]></eg></exemplum><remarks><p>The in degree of a leaf is always 1, its out degree always
0.</p></remarks><part type="top" name="graphs"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="GDTR" type="div2"/></tagDoc><?tei:EOF leaf.tag ??><!-- leaf element --><?tei:SOF lem.tag ??><!-- Revisions:                                               --><!-- 94-02-03 : MSM : add fragmentary as inclusion            --><!-- 94-01-25 : MSM : paracontent not phrase.seq              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lem.tag,v $
# Revision 1.2  94/02/07  20:56:16  msmcq
# revsisions for P3
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY lem      system 'lem.tag' --><!-- lem tag --><!-- **************************************************** lem --><tagDoc id="LEM" usage="rwa"><gi tei="yes">lem</gi><name>lemma</name><desc>contains the lemma, or base text, of a textual variation.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The term <term>lemma</term> is used in text criticism to
describe the reading in the text itself (as opposed to those in the
apparatus); this usage is distinct from that of mathematics (where a
lemma is a major step in a proof) and natural-language processing
(where a lemma is the dictionary form associated with an inflected
form in the running text).</p></remarks><part type="top" name="tc"/><classes names="READINGS"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent)  +(%m.fragmentary)</elemDecl><xref target="TCAPLL"/></tagDoc><?tei:EOF lem.tag ??><!-- lem element --><?tei:SOF lg.tag ??><!-- Revisions:                                               --><!-- 93-11-18 : MSM : remove from compvers class              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lg.tag,v $
# Revision 1.9  94/01/04  12:14:38  lou
# fix xrefs
# 
# Revision 1.8  1993/11/26  18:18:29  msmcq
# revision for publication of VE
#
# Revision 1.7  1993/08/12  21:44:04  msmcq
# merge LB changes and MSM changes
#
# Revision 1.5  1993/08/11  13:03:47  lou
# changes for compatibility with VE
#
# Revision 1.4  1993/08/04  10:34:06  lou
# assigned to metrical class
# --><!-- 7 aug : LB add to classes METRICAL, compvers, divn
            remove redundant attributes --><!-- 93-06-04 : MSM : add MET attribute (DRbod wants it)      --><!-- 92-12-10 : MSM : change class to CHUNK, after disc w/LB  --><!-- 92-12-10 : MSM : add PART attribute, as per LB           --><!-- 92-12-09 : MSM : assign to class coreverse               --><!-- 92-12-09 : MSM : *inherited, not #inherited              --><!-- 92-12-09 : MSM : punctuation cleanup                     --><!-- 92-12-07 : MSM : fix problem at end of EG                --><!-- 92-12-07 : MSM : change xref to COve                     --><!-- **************************************************************lg --><tagDoc id="LG" usage="opt"><gi tei="yes">lg</gi><name>line group</name><desc>contains a group of verse lines functioning as a formal unit
e.g. a stanza, refrain, verse paragraph, etc.</desc><attList></attList><exemplum><eg><![CDATA[<lg type=free>
<l>Let me be my own fool
<l>of my own making, the sum of it
</lg>
<lg>
<l>is equivocal.
<l>One says of the drunken farmer:
</lg>
<lg>
<l>leave him lay off it. And this is
<l>the explanation.
</lg>]]><!-- R Creeley, 'A counterpoint' (For Love, Scribner, 1962 p.42)--></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="CHUNK METRICAL DIVN"/><dataDesc>contains verse lines or nested line groups only, possibly
prefixed by a heading.</dataDesc><elemDecl>- O ((%m.divtop)*, (l | lg)+, (%m.divbot)*)</elemDecl><xref target="COVE"/><xref target="CODV"/><xref target="DRPAL"/></tagDoc><?tei:EOF lg.tag ??><!-- lg element --><?tei:SOF lg1.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lg1.tag,v $
# Revision 1.4  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.3  1994/01/04  01:01:04  msmcq
# add RCS id
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : remove from class chunk                 --><!-- 2 aug : LB clone from existing LG --><!-- *****************************************************lg1 --><tagDoc id="LG1" usage="opt"><gi tei="yes">lg1</gi><name>line group</name><desc>contains a first-level (i.e. largest) group of verse lines
functioning as a formal unit e.g. a stanza, refrain, verse paragraph,
etc.</desc><attList></attList><exemplum><eg><![CDATA[     <lg1 n='VIII' type=stanza>
        <lg2 type=sestet>
          <l>In the first year of Freedom's second dawn
          <l>Died George the Third; although no tyrant, one
          <l>Who shielded tyrants, till each sense withdrawn
          <l>Left him nor mental nor external sun:
          <l>A better farmer ne'er brushed dew from lawn,
          <l>A worse king never left a realm undone!
        </lg2>
        <lg2 type=couplet>
          <l>He died &dash; but left his subjects still behind,
          <l>One half as mad &dash; and t'other no less blind.
        </lg2>
     </lg1>]]></eg><!-- Byron, Vision of Judgment viii ed EH Coleridge 1922) --></exemplum><remarks></remarks><part type="base" name="verse"/><classes names="METRICAL COMPVERS DIVN"/><dataDesc>contains verse lines or nested line groups only, possibly
prefixed by a heading.</dataDesc><elemDecl>- o (head?,(l|lg2)+)</elemDecl><xref target="VEST"/></tagDoc><?tei:EOF lg1.tag ??><!-- lg1 element --><?tei:SOF lg2.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lg2.tag,v $
# Revision 1.4  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.3  1994/01/04  01:01:04  msmcq
# add RCS id
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : remove from class chunk                 --><!-- 2 aug : LB clone from existing LG --><!-- *****************************************************lg2 --><tagDoc id="LG2" usage="opt"><gi tei="yes">lg2</gi><name>line group</name><desc>contains a second-level (i.e. second largest) group of verse lines
functioning as a formal unit e.g. a stanza, refrain, verse paragraph,
etc.</desc><attList></attList><remarks></remarks><part type="base" name="verse"/><classes names="METRICAL DIVN"/><dataDesc>contains verse lines or nested line groups only, possibly
prefixed by a heading.</dataDesc><elemDecl>- o (head?,(l|lg3)+)</elemDecl><xref target="VEST"/></tagDoc><?tei:EOF lg2.tag ??><!-- lg2 element --><?tei:SOF lg3.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lg3.tag,v $
# Revision 1.5  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.4  1994/01/04  01:01:04  msmcq
# add RCS id
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : remove from class chunk                 --><!-- 2 aug : LB clone from existing LG --><!-- *****************************************************lg3 --><tagDoc id="LG3" usage="opt"><gi tei="yes">lg3</gi><name>line group</name><desc>contains a third-level (i.e. third largest) group of verse lines
functioning as a formal unit e.g. a stanza, refrain, verse paragraph,
etc.</desc><attList></attList><remarks></remarks><part type="base" name="verse"/><classes names="METRICAL DIVN"/><dataDesc>contains verse lines or nested line groups only, possibly
prefixed by a heading.</dataDesc><elemDecl>- o (head?,(l|lg4)+)</elemDecl><xref target="VEST"/></tagDoc><?tei:EOF lg3.tag ??><!-- lg3 element --><?tei:SOF lg4.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lg4.tag,v $
# Revision 1.5  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.4  1994/01/04  01:01:04  msmcq
# add RCS id
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : remove from class chunk                 --><!-- 2 aug : LB clone from existing LG --><!-- *****************************************************lg4 --><tagDoc id="LG4" usage="opt"><gi tei="yes">lg4</gi><name>line group</name><desc>contains a fourth-level (i.e. fourth largest) group of verse lines
functioning as a formal unit e.g. a stanza, refrain, verse paragraph,
etc.</desc><attList></attList><remarks></remarks><part type="base" name="verse"/><classes names="METRICAL DIVN"/><dataDesc>contains verse lines or nested line groups only, possibly
prefixed by a heading.</dataDesc><elemDecl>- o (head?,(l|lg5)+)</elemDecl><xref target="VEST"/></tagDoc><?tei:EOF lg4.tag ??><!-- lg4 element --><?tei:SOF lg5.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	lg5.tag,v $
# Revision 1.5  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.4  1994/01/04  01:01:04  msmcq
# add RCS id
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : remove from class chunk                 --><!-- 2 aug : LB clone from existing LG --><!-- *****************************************************lg5 --><tagDoc id="LG5" usage="opt"><gi tei="yes">lg5</gi><name>line group</name><desc>contains a fifth-level (i.e. smallest) group of verse lines
functioning as a formal unit e.g. a stanza, refrain, verse paragraph,
etc.</desc><attList></attList><remarks></remarks><part type="base" name="verse"/><classes names="METRICAL DIVN"/><dataDesc>contains verse lines only, possibly
prefixed by a heading.</dataDesc><elemDecl>- o (head?, l+)</elemDecl><xref target="VEST"/></tagDoc><?tei:EOF lg5.tag ??><!-- lg5 element --><?tei:SOF plline.tag ??><!-- Revisions:                                               --><!-- 93-09-13 : MSM : xref was cors3, now NHrs                --><!-- 93-09-13 : MSM : drop dot in id                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	plline.tag,v $
# Revision 1.2  93/09/22  19:14:57  msmcq
# change id, xref
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************************** plline --><tagDoc id="PLLINE" usage="opt"><gi tei="yes">line</gi><desc>contains one line of a reference edition.</desc><attList></attList><exemplum><eg><![CDATA[    <(La)page n=32>
    <(La)line n=1> ... [text of edition La, p. 32, l. 1]
    <(La)line n=2> ... [text of edition La, p. 32, l. 2]
    <(La)line n=3> ... [text of edition La, p. 32, l. 3]
    <(La)line n=4> ... [text of edition La, p. 32, l. 4]
    <(La)page n=33> ...]]></eg></exemplum><remarks><p> (optional)</p></remarks><part type="base" name="print"/><classes/><dataDesc>May contain character data only.</dataDesc><elemDecl>- -  (#PCDATA)</elemDecl><xref target="NHRS" type="div3"/></tagDoc><?tei:EOF plline.tag ??><!-- line tag (in PL tag set) --><?tei:SOF link.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	link.tag,v $
# Revision 1.4  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.3  1994/02/12  10:46:15  lou
# revisions for publicn of P3
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 93-04-13 : MSM : eliminate ]]> problems                  --><!-- 93-02-12 : MSM : LOC class has id CLLOC, not LOC         --><!-- 93-01-26 : MSM : add TYPE attribute                      --><!-- 93-01-26 : MSM : change DESC                             --><!-- 93-01-26 : MSM : add to pointer class                    --><!-- 93-01-21 : MSM : correct name of att to targets          --><!-- ********************************************************** link --><tagDoc id="LINK" usage="opt"><gi tei="yes">link</gi><desc>defines an association or hypertextual link
among elements or passages, of some type
not more precisely specifiable by other elements.</desc><attList><attDef usage="req"><attName>targets</attName><desc>specifies the SGML identifiers of the elements or passages
    to be linked or associated.
 </desc><datatype>IDREFS </datatype><valDesc>Each value specified must be the same as that specified as
    value for an <att tei="yes">ID</att> attribute for some other element in the
    current SGML document.</valDesc><default>#REQUIRED</default></attDef><attDef usage="opt"><attName>type</attName><desc>categorizes the group of associations
 in some respect, using any convenient set of categories.</desc><datatype>CDATA </datatype><valDesc>Where type is specified on a <gi tei="yes">linkGrp</gi> element, it
supplies the default value for the <att tei="yes">type</att> attribute on each
<gi tei="yes">link</gi> included within the group.</valDesc><default>%INHERITED;</default></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>This element should only be used to encode associations
not otherwise provided for by more specific elements.</p><p>The location of this element within a document has no significance,
unless it is included within a <gi tei="yes">linkGrp</gi>, in which case it
may inherit the value of the <att tei="yes">type</att> attribute from the value
given on the <gi tei="yes">linkGrp</gi>.</p></remarks><part type="top" name="hyper"/><classes names="CLLOC POINTER METADATA"/><dataDesc></dataDesc><elemDecl>- o EMPTY </elemDecl><xref target="SAPT"/></tagDoc><?tei:EOF link.tag ??><!-- link element --><?tei:SOF linkgrp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: linkgrp.tag,v $
    * Revision 1.5  1998/01/31 19:55:51  tei
    * added to fmchunk
    *
    * Revision 1.4  94/08/29  15:23:27  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.3  1994/02/12  10:45:13  lou
    * revisions for publication of P3
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 4 feb: change content model slightly (no need for inclusion) --><!-- 93-04-13 : MSM : eliminate ]]> problems                  --><!-- 93-01-26 : MSM : make ptr, xptr exceptions not part of model --><!-- 93-01-26 : MSM : change text slighlyt                    --><!-- 93-01-26 : MSM : allow ptr, xptr in model                --><!-- 93-01-21 : MSM : move ... out of column 1                --><!-- ******************************************************* linkgrp --><tagDoc id="LINKGRP" usage="opt"><gi tei="yes">linkGrp</gi><desc>defines a collection of associations or hypertextual links.</desc><attList></attList><exemplum><eg><![CDATA[<linkGrp type='translation'>
<link target='S1 z1'>
<link target='S2 z2'>
 ...
<link target='S99 z99' type='paraphrase'>
</linkGrp>]]></eg></exemplum><remarks><p>A web or link group is an administrative convenience, which
should be used to collect a set of links together for any
purpose, not simply to supply a default value for the <att tei="yes">type</att>
attribute.</p></remarks><part type="top" name="hyper"/><classes names="PTRGROUP METADATA"/><dataDesc>May contain one or more <gi tei="yes">link</gi> elements only,
optionally with interspersed pointer elements.</dataDesc><elemDecl>- - (link | ptr | xptr)+ </elemDecl><xref target="SAPT"/></tagDoc><?tei:EOF linkgrp.tag ??><!-- linkGrp element --><?tei:SOF list.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: list.tag,v $
    * Revision 1.4  1998/01/31 18:29:58  tei
    * changed to allow empty lists (sigh)
    *
    * Revision 1.3  1994/01/04 13:17:01  lou
    * disallow empty lists
    *
    * Revision 1.2  1993/08/03  02:08:13  msmcq
    * change content model
    * --><!-- Revisions:                                               --><!-- 31 jan 98 : LB : reintroduce empty lists (under protest) --><!-- 2 jan 93: LB : must have at least one item, or one label/item pair --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : normalize headItem, headLabel           --><!-- 93-02-10 : MSM : remove id from type attribute           --><!-- 92-12-09 : MSM : normaliZe spelling                      --><!-- 92-12-07 : MSM : ?                                       --><!-- 92-11-23 : MSM : expand tabs                             --><!-- ******************************************************** list --><tagDoc id="LIST" usage="rwa"><gi tei="yes">list</gi><desc>contains any sequence of items organized as a list.</desc><attList><attDef usage="opt"><attName>type</attName><desc>describes the form of the list.</desc><datatype>CDATA</datatype><valList type="semi"><val>ordered</val><desc>list items are numbered or lettered.
    </desc><val>bulleted</val><desc>list items are marked with a
<soCalled>bullet</soCalled> or other typographic device.
    </desc><val>simple</val><desc>list items are not numbered or bulleted.
    </desc><val>gloss</val><desc>each list item glosses some term or
concept, which is given by a <gi tei="yes">label</gi> element preceding
the list item.</desc></valList><default>simple</default><eg></eg><remarks><p>The formal syntax of the element declarations allows
<gi tei="yes">label</gi> tags to be omitted from lists tagged <tag compl="full" tei="yes">list
type=gloss</tag>; this is however a semantic error.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<list type=ordered>
<item>a butcher
<item>a baker
<item>a candlestick maker, with
<list type=bullets>
<item>rings on his fingers
<item>bells on his toes
</list>
</list>]]></eg></exemplum><exemplum><p>The following example treats the short numbered clauses of
Anglo-Saxon legal codes as lists of items.  The text is from an
ordinance of King Athelstan (924-939).</p><eg><![CDATA[<div1><head>Athelstan's Ordinance</head>
<list type=ordered>
<item n='1'>Concerning thieves.  First, that no thief is to be
spared who is caught with the stolen goods, [if he is] over
twelve years and [if the value of the goods is] over eightpence.
<list type=ordered>
<item n='1.1'>And if anyone does spare one, he is to pay for the
thief with his wergild -- and the thief is to be no nearer a
settlement on that account -- or to clear himself by an oath of
that amount.
<item n=1.2>If, however, he [the thief] wishes to defend himself
or to escape, he is not to be spared [whether younger or older
than twelve].
<item n=1.3>If a thief is put into prison, he is to be in prison
40 days, and he may then be redeemed with 120 shillings; and the
kindred are to stand surety for him that he will desist for ever.
<item n=1.4>And if he steals after that, they are to pay for him
with his wergild, or to bring him back there.
<item n=1.5>And if
he steals after that, they are to pay for him with his wergild,
whether to the king or to him to whom it rightly belongs; and
everyone of those who supported him is to pay 120 shillings to
the king as a fine.
</list>
<item n=2>Concerning lordless men.  And we pronounced about these
lordless men, from whom no justice can be obtained, that one
should order their kindred to fetch back such a person to justice
and to find him a lord in public meeting.
<list type=ordered>
<item n=2.1>And if they then will not, or cannot, produce him on
that appointed day, he is then to be a fugitive afterwards, and
he who encounters him is to strike him down as a thief.
<item n=2.2>And he who harbours him after that, is to pay for him
with his wergild or to clear himself by an oath of that amount.
</list>
<item n=3>Concerning the refusal of justice.  The lord who
refuses justice and upholds his guilty man, so that the king is
appealed to, is to repay the value of the goods and 120 shillings
to the king; and he who appeals to the king before he demands
justice as often as he ought, is to pay the same fine as the
other would have done, if he had refused him justice.
<list type=ordered>
<item n=3.1>And the lord who is an accessory to a theft by his
slave, and it becomes known about him, is to forfeit the slave
and be liable to his wergild on the first occasionp if he does it
more often, he is to be liable to pay all that he owns.
<item n=3.2>And likewise any of the king's treasurers or of our
reeves, who has been an accessory of thieves who have committed
theft, is to liable to the same.
</list>
<item n=4>Concerning treachery to a lord.  And we have pronounced
concerning treachery to a lord, that he [who is accused] is to
forfeit his life if he cannot deny it or is afterwards convicted
at the three-fold ordeal.
</list>]]></eg><p>Note that nested lists have been used so the tagging mirrors the
structure indicated by the two-level numbering of the clauses.
The clauses could have been treated as a one-level list with
irregular numbering, if desired.</p></exemplum><exemplum><eg><![CDATA[<p>These decrees, most blessed Pope Hadrian, we propounded in the
public council ... and they confirmed them in our hand in your
stead with the sign of the Holy Cross, and afterwards inscribed
with a careful pen on the paper of this page, affixing thus the
sign of the Holy Cross.
<list type=simple>
<item>I, Eanbald, by the grace of God archbishop of the holy
church of York, have subscribed to the pious and catholic
validity of this document with the sign of the Holy Cross.
<item>I, &AElig;lfwold, king of the people across the Humber,
consenting have subscribed with the sign of the Holy Cross.
<item>I, Tilberht, prelate of the church of Hexham, rejoicing
have subscribed with the sign of the Holy Cross.
<item>I, Higbald, bishop of the church of Lindisfarne, obeying
have subscribed with the sign of the Holy Cross.
<item>I, Ethelbert, bishop of Candida Casa, suppliant, have
subscribed with thef sign of the Holy Cross.
<item>I, Ealdwulf, bishop of the church of Mayo, have subscribed
with devout will.
<item>I, &AElig;thelwine, bishop, have subscribed through
delegates.
<item>I, Sicga, `patrician', have subscribed with serene mind
with the sign of the Holy Cross.
</list>]]></eg></exemplum><part type="top" name="core"/><classes names="LISTS"/><dataDesc>May contain an optional heading followed by a series of
items, or a series of label and item pairs, the latter being optionally
preceded by one or two specialized headings.</dataDesc><elemDecl>- - (head?, ( (item*) | (headLabel?, headItem?, (label,
item)*)))</elemDecl><xref target="COLI" type="div2"/></tagDoc><?tei:EOF list.tag ??><!-- list element --><?tei:SOF listbibl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	listbibl.tag,v $
# Revision 1.2  94/01/04  12:14:41  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 1 jun : LB: changed name and ID for consistency with each other --><!--         (if nothing else)                                 --><!-- 93-03-08 : MSM : add to class declabl                    --><!-- 93-03-08 : MSM : correct example of bibl.struct          --><!-- 92-12-09 : MSM : add to lists class                      --><!-- 92-11-09 : MSM : set xref to CObi                        --><!-- 92-11-09 : MSM : rename BIBL from CITN                   --><!-- ***************************************************listBibl --><tagDoc id="LISTBIBL" usage="opt"><gi tei="yes">listBibl</gi><name>citation list</name><desc>contains a list of bibliographic citations of any kind. </desc><attList></attList><exemplum><eg><![CDATA[<listBibl>
    <head>Works consulted</head>
    <bibl>Blain, Clements and Grundy: Feminist Companion to
          Literature in English (Yale, 1990)
    </bibl>
    <biblStruct>
    <analytic>
         <title>The Interesting story of the Children in the Wood</>
    <monogr>
         <title>The Penny Histories</title>
         <author>Victor E Neuberg</author>
         <imprint><publisher>OUP</><date>1968</>
    </biblStruct>
</listBibl>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="LISTS DECLABL"/><dataDesc></dataDesc><elemDecl>- - (head?, (bibl | biblStruct | biblFull)+, trailer?)</elemDecl><xref target="COBITY"/><xref target="HD3"/><xref target="CCAS2"/></tagDoc><?tei:EOF listbibl.tag ??><!-- listBibl element --><?tei:SOF locale.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	locale.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *************************************************************** locale --><tagDoc id="LOCALE" usage="opt"><gi tei="yes">locale</gi><name>locale</name><desc>contains a brief informal description of the nature of a
place for example a room, a restaurant, a park bench etc.</desc><attList></attList><exemplum><eg><![CDATA[  <locale>a fashionable restaurant]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHSE"/></tagDoc><?tei:EOF locale.tag ??><!-- locale element --><?tei:SOF m.tag ??><!-- ****************************************************** m --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	m.tag,v $
# Revision 1.3  94/02/27  15:55:54  lou
# Revisions for publication of AI
# 
# Revision 1.2  1993/11/26  18:16:08  msmcq
# MSM changes pre-publication
#
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 93-11-26 : MSM : fix empty end tags                      --><!-- 93-11-15 : MSM : fix unmatched paren in content model    --><!-- 93-09-22 : MSM : change seg id to clseg                  --><!-- 93-07-22 : DTL : create                                  --><!--                                                          --><!-- ****************************************************** m --><tagDoc id="M" usage="opt"><gi tei="yes">m</gi><name>morpheme</name><desc>represents a grammatical morpheme.</desc><attList><attDef usage="opt"><attName>baseform</attName><desc>identifies the morpheme's base form.</desc><datatype>CDATA</datatype><valDesc>a string of characters representing the spelling of the
morpheme's base form.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<w type=adjective><w type=noun><m type=prefix baseform=con>com</m>
<m type=root>fort</m></w><m type=suffix>able</m></w>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLSEG"/><dataDesc>May contain character data, <gi tei="yes">seg</gi>, and <gi tei="yes">c</gi>
elements only.</dataDesc><elemDecl>- - ((#PCDATA | seg | c)*)</elemDecl><xref target="AILC"/></tagDoc><?tei:EOF m.tag ??><!-- m element --><?tei:SOF measure.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: measure.tag,v $
    * Revision 1.2  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- Revisions:                                               --><!-- 2 jun : LB: changed desc --><!-- 17 May 9 : DIG : sorting it all out                      --><!-- 92-12-09 : MSM : suppress leading space in desc          --><!-- 92-12-09 : MSM : normaliZe spelling                      --><!-- ***************************************************** measure --><tagDoc id="MEASURE" usage="opt"><gi tei="yes">measure</gi><desc>contains a word or phrase referring to some quantity of
an object or commodity, usually comprising a number, a unit and a
commodity name.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>specifies the type of unit in which the measure is expressed.</desc><datatype>CDATA</datatype><valList type="open"><val>weight</val><desc>measure of weight e.g. kg, pound.</desc><val>count</val><desc>unit of count, e.g. dozen, score.</desc><val>length</val><desc>measure of length, e.g. pole, mm.</desc><val>area</val><desc>measure of area e.g. acre, hectare.</desc><val>volume</val><desc>measure of volume e.g. litre, gallon.</desc><val>currency</val><desc>unit of currency e.g. ecu, escudo, mark.</desc></valList><default>#IMPLIED</default><remarks></remarks></attDef></attList><exemplum><eg><![CDATA[    <measure key=LBSF11 type='weight'>
        <num>2</num> pounds of flesh</measure>
    <measure type=currency reg='$1.56'>a quid</measure>
    <measure type=area reg='8 ECU'>2 merks of old extent</measure>]]></eg></exemplum><remarks></remarks><part type="top" name="core"/><classes names="DATA NAMES"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONANU" type="div2"/></tagDoc><?tei:EOF measure.tag ??><!-- measure element --><?tei:SOF meeting.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	meeting.tag,v $
# Revision 1.2  94/01/04  12:14:42  lou
# fix xrefs
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 93-06-21 : MSM : made file                               --><!-- ******************************************************** meeting --><tagDoc id="MEETING" usage="opt"><gi tei="yes">meeting</gi><desc>in bibliographic references,
contains a description of the meeting or conference from which
the bibliographic item derives.</desc><attList></attList><exemplum><eg><![CDATA[ <meeting>Ninth International Conference on Middle High German
 Textual Criticism, Aachen, June 1998.</meeting>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes/><elemDecl>- - (%paraContent)</elemDecl><xref target="COBICOR"/></tagDoc><?tei:EOF meeting.tag ??><!-- meeting element --><?tei:SOF mentiond.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : correct example                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	mentiond.tag,v $
# Revision 1.3  94/03/25  22:14:43  msmcq
# full stop after desc.
# 
# Revision 1.2  1994/01/15  21:16:35  msmcq
# revisions in connection with di, for p3; see comments for details
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- **************************************************** mentiond --><tagDoc id="MENTIOND" usage="rwa"><gi tei="yes">mentioned</gi><desc>marks words or phrases mentioned, not used.</desc><attList></attList><exemplum><eg><![CDATA[There is thus a striking accentual difference between a verbal
form like <mentioned lang=EL id=C234>eluthemen</mentioned>
<gloss target=C234>we were released,</gloss> accented on
the second syllable of the word, and its
participial derivative <mentioned lang=EL id=C235>lutheis</mentioned>
<gloss target=C235>released,</gloss> accented on the last.]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc>free prose</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="COHQU"/></tagDoc><?tei:EOF mentiond.tag ??><!-- mentioned element --><?tei:SOF metdecl.tag ??><!-- Revisions:                                               --><!-- 21 jan 94: LB : change name to metdecl, add xref --><!-- 93-11-18 : MSM : remove ghost exemplum, eg, cdata starts --><!-- 93-11-18 : MSM : correct model:  paraSeq becomes component.seq --><!-- 93-11-18 : MSM : fix line break within Xref (script prob) --><!-- 93-11-18 : MSM : allow use for RHYME notation, add TYPE att --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	metdecl.tag,v $
# Revision 1.2  94/03/23  18:21:15  msmcq
# correct errant spacing
# 
# Revision 1.1  1994/01/28  18:02:44  lou
# Initial revision
#
# Revision 1.2  1993/11/26  18:19:55  msmcq
# revision for publication of VE
#
# Revision 1.1  1993/08/11  13:11:14  lou
# Initial revision
# --><!-- 17 jul 93 : LB : made file --><!-- *************************************************** metDecl --><tagDoc id="METDECL" usage="rec"><gi tei="yes">metDecl</gi><desc>documents the notation employed to represent a metrical pattern
when this is specified as the value of a <att tei="yes">met</att>,
<att tei="yes">real</att>, or <att tei="yes">rhyme</att> attribute on any structural element
of a metrical text (e.g.  <gi tei="yes">lg</gi>, <gi tei="yes">l</gi>, or
<gi tei="yes">seg</gi>).</desc><attList><!-- ................................................... type --><attDef usage="mwa"><attName>type</attName><desc>indicates whether the notation conveys the abstract
metrical form, its actual prosodic realization, or the
rhyme scheme, or some combination thereof.</desc><datatype>NAMES</datatype><valDesc>One or more of the three attribute names <att tei="yes">met</att>,
<att tei="yes">real</att>, or <att tei="yes">rhyme</att>.</valDesc><default>"MET REAL"</default><eg><![CDATA[ ]]></eg><remarks><p>By default, the <gi tei="yes">metDecl</gi> element documents the
notation used for metrical pattern and realization.  It may also be used
to document the notation used for rhyme scheme information; if not
otherwise documented, the rhyme scheme notation defaults to the
traditional <q>abab</q> notation.</p></remarks></attDef><attDef usage="opt"><attName>pattern</attName><desc>specifies a regular expression defining any value that is
legal for this notation.</desc><datatype>CDATA</datatype><valDesc>the value must be a valid expression for the PATTERN keyword
as defined in the TEI extended pointer notation
(see section <xref target="SAXR1PA"/>).</valDesc><default>#IMPLIED</default><eg><![CDATA[ <metDecl pattern='( (1|0)+  \|? /? )* ' >
 <metDecl pattern= '((+-|-+)-+-+-+-+/)']]></eg><remarks></remarks></attDef></attList><exemplum><eg><![CDATA[   <metDecl id=IP pattern= '((+-|-+)-+-+-+-+/)'
        <symbol value='+'>stressed syllable
        <symbol value='-'>unstressed syllable
        <symbol value='/'>metrical line boundary
   </metDecl>]]></eg><p>This example is intended for the far more restricted case
typified by the Shakespearean iambic pentameter. Only metrical patterns
containing exactly ten syllables, alternately stressed and unstressed,
(except for the first two which may be in either order) to each
metrical line can be expressed using this notation.</p></exemplum><remarks><p>The encoder may choose whether to define the notation
formally or informally. However, the two methods may not be mixed.</p><p>Only usable within the header if the verse base is enabled.</p></remarks><part type="base" name="hdr"/><classes names="DECLABL"/><dataDesc>contains either a sequence of <gi tei="yes">symbol</gi> elements
or paragraphs. If one <gi tei="yes">symbol</gi> is defined, then all the
codes appearing within the <att tei="yes">pattern</att> attribute should
be documented, if the latter is specified.</dataDesc><elemDecl>- O  ((%component.seq) | (symbol+))</elemDecl><xref target="HDMN"/><xref target="VEME"/></tagDoc><?tei:EOF metdecl.tag ??><!-- metDecl element --><?tei:SOF milest.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: milest.tag,v $
    * Revision 1.3  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.2  94/01/04  12:14:42  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : add membership in refsys class          --><!-- 92-12-09 : MSM : remove membership in LOC class          --><!-- 92-12-07 : MSM : cosmetic changes                        --><!-- ****************************************************** milest --><tagDoc id="MILEST" usage="opt"><gi tei="yes">milestone</gi><desc>marks the boundary between sections of a text, as indicated by
changes in a standard reference system.</desc><attList><attDef usage="rec"><attName>ed</attName><name>edition</name><desc>indicates which edition or version the milestone applies to.</desc><datatype>CDATA</datatype><valDesc>Any string of characters; usually a siglum conventionally used
for the edition.</valDesc><default>#IMPLIED</default><eg></eg></attDef><attDef usage="opt"><attName>n</attName><name>number or name</name><desc>indicates the new number or other value for the unit which changes
at this milestone.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>The special value <term>unnumbered</term> should be used in
passages which fall outside the normal numbering scheme (e.g. chapter
heads, poem numbers or titles, or speaker attributions in verse drama).</p></remarks></attDef><attDef usage="req"><attName>unit</attName><desc>indicates what kind of section is changing at this milestone.</desc><datatype>CDATA</datatype><valList type="semi"><val>page </val><desc>page breaks in the reference edition.</desc><val>column </val><desc>column breaks.</desc><val>line </val><desc>line breaks.</desc><val>book </val><desc>any units termed <cited>book</cited>,
<cited>liber</cited>, etc.</desc><val>poem </val><desc>individual poems in a collection.</desc><val>canto </val><desc>cantos or other major sections of a poem.</desc><val>stanza </val><desc>stanzas within a poem, book, or canto.</desc><val>act </val><desc>acts within a play.</desc><val>scene </val><desc>scenes within a play or act.</desc><val>section</val><desc>sections of any kind.</desc><val>absent </val><desc>passages not present in the reference edition.</desc></valList><default>#REQUIRED</default><eg></eg><remarks><p>If the milestone marks the beginning of a piece of text not
present in the reference edition, the special value <term>absent</term>
may be used as the value of <att tei="yes">unit</att>.  The normal interpretation
is that the reference edition does not contain the text which follows,
until the next <gi tei="yes">milestone</gi> tag for the edition in question is
encountered.</p><p>In addition to the values suggested, other terms may be appropriate
(e.g. <term>Stephanus</term> for the Stephanus numbers in Plato).</p></remarks></attDef></attList><exemplum><eg><![CDATA[    <milestone ed=La unit=Dreissiger n=23>
    ...
    <milestone ed=AV unit=verse n=24>
    ...]]></eg></exemplum><remarks><p>Milestones for page and column should precede
milestones for line numbers, but this and other logical requirements
cannot be enforced automatically by SGML; for better validation, a
concurrent markup stream may be used.</p></remarks><part type="top" name="core"/><classes names="REFSYS"/><elemDecl>- O EMPTY</elemDecl><xref target="CORS5" type="div3"/></tagDoc><?tei:EOF milest.tag ??><!-- milestone element --><?tei:SOF minus.tag ??><!-- ************************************************************ --><!-- TAGDOC for MINUS                                             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	minus.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class binary                     --><!-- 93-09-22 : MSM : extract from group file                 --><!-- ************************************************************ --><tagDoc id="MINUS" usage="rwa"><gi tei="yes">minus</gi><name>Binary minus value</name><desc>provides binary minus value for a feature.</desc><attList></attList><exemplum><eg><![CDATA[<f name=nasal><minus></f>]]></eg></exemplum><part type="top" name="fs"/><classes names="BINARY"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSBI" type="div3"/></tagDoc><?tei:EOF minus.tag ??><!-- minus          --><?tei:SOF minute.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	minute.tag,v $
# Revision 1.3  94/03/07  16:15:20  lou
# initial revisn of ND
# 
# Revision 1.2  1993/08/03  02:06:55  msmcq
# fix MS end problem
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- minute --><tagDoc id="MINUTE" usage="opt"><gi tei="yes">minute</gi><name>minute</name><desc>the minute component of a structured time-expression.</desc><attList></attList><exemplum><eg><![CDATA[The train leaves for Boston at 
<timeStruct value='1345'>
<hour>13</hour>:
<minute>45</minute>
</timeStruct>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF minute.tag ??><!-- minute element      --><?tei:SOF monogr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	monogr.tag,v $
# Revision 1.3  94/01/04  12:14:43  lou
# fix xrefs
# 
# Revision 1.2  1993/09/22  19:10:36  msmcq
# make edition info optional
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 2 jan 94: LB : make auth/title optional, edition repeatable, --><!--                add extent, leave out kitchen sink         --><!-- 93-09-21 : MSM : make edition optional!                  --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-06 : MSM : allow multiple imprints (for double publishers) --><!-- 92-12-06 : MSM : made file                               --><!-- *********************************************** monogr --><tagDoc id="MONOGR" usage="mwa"><gi tei="yes">monogr</gi><name>monographic level</name><desc>contains bibliographic elements describing an item (e.g. a book
or journal) published as an independent item (i.e. as a separate
physical object).</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The <gi tei="yes">monogr</gi> element may occur only within
bibliographic citation or reference elements; it is mandatory for
description of the monographic level of <gi tei="yes">bibl.struct</gi> elements.</p></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc>May contain specialized bibliographic elements, in a
prescribed order.</dataDesc><elemDecl>- O  (
               ( ((author | editor | respStmt)+, title+, (editor | respStmt)*)
                 | (title+, (author | editor | respStmt)*))?,
               (note | meeting)*,
               (edition, (editor | respStmt)*)*,
               imprint, (imprint | extent | biblScope)*
                            )</elemDecl><xref target="COBICOL"/></tagDoc><?tei:EOF monogr.tag ??><!-- monogr element --><?tei:SOF month.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	month.tag,v $
# Revision 1.4  94/03/07  16:15:14  lou
# rvisn of ND
# 
# Revision 1.3  1993/08/03  02:06:55  msmcq
# fix MS end problem
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- month --><tagDoc id="MONTH" usage="opt"><gi tei="yes">month</gi><name>month</name><desc>the month component of a structured date.</desc><attList></attList><exemplum><eg><![CDATA[<dateStruct value='14-05-1993'>
<day type=name>Friday</day>,
<day type=number>14</day>
<month type=name>May</month>
<year>1993</year></dateStruct>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF month.tag ??><!-- month element --><?tei:SOF mood.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : note synonymy with GRAM                 --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	mood.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** mood --><tagDoc id="MOOD" usage="rwa"><gi tei="yes">mood</gi><desc>contains information about the grammatical mood of verbs (e.g.
<q>indicative</q>, <q>subjunctive</q>, <q>imperative</q>)</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type=mood</tag>.</p></remarks><part type="base" name="dict"/><classes names="MORPH DIPARTS DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/></tagDoc><?tei:EOF mood.tag ??><!-- mood element --><?tei:SOF move.tag ??><!-- Revisions:                                               --><!-- 93-08-19 : MSM : change class to stagedir                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	move.tag,v $
# Revision 1.6  94/02/12  10:43:27  lou
# JLs comments of 4 feb
# 
# Revision 1.5  1993/08/23  16:38:32  msmcq
# Changes at publication of DR
#
# Revision 1.3  1993/08/13  20:49:59  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:28:05  msmcq
# revisions for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- changedattrib names, defnms --><!-- *******************************************************   MOVE--><tagDoc id="MOVE" usage="opt"><gi tei="yes">move</gi><name>Movement</name><desc>marks the actual entrance or exit of one or more characters on stage.</desc><attList><attDef usage="req"><attName>who</attName><desc>identifies the character or characters performing the movement.</desc><datatype>IDREFS</datatype><valDesc>The IDREFS are derived from the ID attribute on the role
elements in the cast list.</valDesc><default>#REQUIRED</default></attDef><attDef usage="opt"><attName>type</attName><desc>characterizes the movement, for example as an entrance or exit.</desc><datatype>CDATA</datatype><valList type="semi"><val>entrance </val><desc>character is entering the stage.</desc><val>exit </val><desc>character is exiting the stage.</desc><val>onstage</val><desc>character moves on stage</desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>where</attName><desc>specifies the direction of a stage movement.</desc><datatype>CDATA</datatype><valList type="open"><val>L</val><desc>stage left</desc><val>R</val><desc>stage right</desc><val>C</val><desc>centre stage</desc></valList><default>#IMPLIED</default><remarks><p>Full blocking information will normally require combinations
of values, (for example <q>UL</q> for <q>upper stage left</q>) and may
also require more detailed encoding of speed, direction etc.  Full
documentation of any coding system used should be provided in the
header.</p></remarks></attDef><!-- .......................................................  perf --><attDef usage="opt"><attName>perf</attName><desc>identifies the performance or performances in which this movement
occurred as specified.</desc><datatype>IDREFS</datatype><valDesc>The ID of a <gi tei="yes">performance</gi> element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<stage type="entrance">
<move who=B type="enter" where=SL perf=P1>
Enter Bellafront mad.</stage>]]></eg></exemplum><part type="base" name="perf"/><classes names="STAGEDIR"/><dataDesc>Empty</dataDesc><elemDecl> - O EMPTY</elemDecl><xref target="DRSTA" type="div3"/></tagDoc><?tei:EOF move.tag ??><!-- move element --><?tei:SOF msr.tag ??><!-- ************************************************************ --><!-- TAGDOC for MSR                                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	msr.tag,v $
# Revision 1.4  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.3  1994/03/07  16:15:40  lou
# revision of ND
#
# Revision 1.2  1994/01/04  01:05:29  msmcq
# revise DESCs of REL values
#
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 93-12-23 : MSM : change value, valueTo atts:  CDATA not NUMBER --><!-- 93-12-22 : MSM : change descriptions on REL att values   --><!-- 93-09-22 : MSM : extract from bulk file                  --><!-- ************************************************************ --><tagDoc id="MSR" usage="rwa"><gi tei="yes">msr</gi><name>Measure value</name><desc>provides a measure value or range of values for a feature.</desc><attList><attDef id="MSRVAL" usage="req"><attName>value</attName><desc>provides a numeric value.</desc><datatype>CDATA</datatype><valDesc>A real number or integer.</valDesc><default>#REQUIRED</default></attDef><attDef id="MSVALTO" usage="opt"><attName>valueTo</attName><desc>together with <att tei="yes">value</att> attribute, provides a range of
numeric values.</desc><datatype>CDATA</datatype><valDesc>A real number or integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="MSRUNIT" usage="req"><attName>unit</attName><desc>provides a unit for a measure feature, one of a finite list that
may be specified in a feature declaration.</desc><datatype>CDATA</datatype><valDesc>A string, e.g. <term>meter</term>.</valDesc><default>#REQUIRED</default></attDef><attDef id="MSRREL" usage="req"><attName>rel</attName><desc>indicates the relation of the given value or range to the actual
value or range.</desc><datatype>(eq|ne|lt|le|gt|ge)</datatype><valList type="closed"><val>eq     </val><desc>indicates that the actual value or range is that
given.
   </desc><val>ne     </val><desc>indicates that the actual value or range is not the
value or range given.
   </desc><val>lt     </val><desc>indicates that the actual value or range is less
than the given value or range.
   </desc><val>le     </val><desc>indicates that the actual value or range is less
than or equal to the given value or range.
   </desc><val>gt     </val><desc>indicates that the actual value or range is greater
than the given value or range.
   </desc><val>ge     </val><desc>indicates that the actual value or range is greater
than or equal to the given value or range.</desc></valList><default>eq</default></attDef><attDef id="MSRTYPE" usage="opt"><attName>type</attName><desc>indicates whether value or range is to be understood as real or
integer.</desc><datatype>(int|real)</datatype><valList type="closed"><val>int    </val><desc>specifies that value is an integer; if noninteger
is given as value of <att tei="yes">value</att>, then only integer part is used.
   </desc><val>real   </val><desc>specifies that value is a real number.</desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<msr value=10000 valueTo=20000 unit=guilder>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Empty tag.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSSY" type="div3"/></tagDoc><?tei:EOF msr.tag ??><!-- msr            --><?tei:SOF name.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	name.tag,v $
# Revision 1.2  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 10 jan 98 : LB : add to addrpart class --><!-- 93-03-29 : MSM : add to class names                      --><!-- 92-12-09 : MSM : move key, reg to names class            --><!-- 92-12-06 : MSM : add to agent class                      --><!-- ******************************************************** name --><tagDoc id="NAME" usage="opt"><gi tei="yes">name</gi><name>name, proper noun</name><desc>contains a proper noun or noun phrase.</desc><attList><attDef usage="rec"><attName>type</attName><desc>indicates the type of the object which is being named by the
phrase.</desc><datatype>CDATA</datatype><valDesc>Values such as person, place, institution, product, acronym.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>Proper nouns referring to people, places, and organizations
may be tagged instead with <gi tei="yes">person</gi>, <gi tei="yes">place</gi>, or
<gi tei="yes">org</gi>.</p></remarks><part type="top" name="core"/><classes names="DATA AGENT NAMES ADDRPART"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONARS" type="div2"/></tagDoc><?tei:EOF name.tag ??><!-- name element --><?tei:SOF namelink.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: --><!-- renamed from namePref--><!--******************************************************nameLink --><tagDoc id="NAMELINK" usage="opt"><gi tei="yes">nameLink</gi><name>name link</name><desc>contains a connecting phrase or link used within a name but not
regarded as part of it, such as  <q>van der</q> or <q>of</q>.</desc><attList></attList><exemplum><eg><![CDATA[<persName>
  <foreName>Frederick</foreName>
  <nameLink>van der</nameLink>
  <surname>Tronck</surname>
</persName>]]></eg></exemplum><exemplum><eg><![CDATA[<persName>
  <foreName>Alfred</foreName>
  <nameLink>de</nameLink>
  <surname>Musset</surname>
</persName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="PERSPART"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF namelink.tag ??><!-- nameLink --><?tei:SOF nbr.tag ??><!-- ************************************************************ --><!-- TAGDOC for NBR                                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	nbr.tag,v $
# Revision 1.5  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.4  1994/03/07  16:14:53  lou
# revised for publication
#
# Revision 1.3  1994/01/04  01:06:38  msmcq
# revise DESCs of REL values
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 93-12-23 : MSM : change value, valueTo atts:  CDATA not NUMBER --><!-- 93-12-22 : MSM : change descriptions on REL att values   --><!-- 93-09-22 : MSM : extract from bulk file                  --><!-- ************************************************************ --><tagDoc id="NBR" usage="rwa"><gi tei="yes">nbr</gi><name>Numeric value</name><desc>provides a numeric value or range of values for a feature.</desc><attList><attDef id="NBRVAL" usage="req"><attName>value</attName><desc>provides a numeric value.</desc><datatype>CDATA</datatype><valDesc>A real number or integer.</valDesc><default>#REQUIRED</default></attDef><attDef id="NRVALTO" usage="opt"><attName>valueTo</attName><desc>together with <att tei="yes">value</att> attribute, provides a range of
numeric values.</desc><datatype>CDATA</datatype><valDesc>A real number or integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="NBRREL" usage="req"><attName>rel</attName><desc>indicates the relation of the given value or range to the actual
value or range.</desc><datatype>(eq|ne|lt|le|gt|ge)</datatype><valList type="closed"><val>eq     </val><desc>indicates that the actual value or range is that
given.
   </desc><val>ne     </val><desc>indicates that the actual value or range is not the
value or range given.
   </desc><val>lt     </val><desc>indicates that the actual value or range is less
than the given value or range.
   </desc><val>le     </val><desc>indicates that the actual value or range is less
than or equal to the given value or range.
   </desc><val>gt     </val><desc>indicates that the actual value or range is greater
than the given value or range.
   </desc><val>ge     </val><desc>indicates that the actual value or range is greater
than or equal to the given value or range.</desc></valList><default>eq</default></attDef><attDef id="NBRTYPE" usage="opt"><attName>type</attName><desc>indicates whether value or range is to be understood as real or
integer.</desc><datatype>(int|real)</datatype><valList type="closed"><val>int    </val><desc>specifies that value is an integer; if noninteger
is given as value of <att tei="yes">value</att>, then only integer part is used.
   </desc><val>real   </val><desc>specifies that value is a real number.</desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<nbr type=int rel=ge value=0>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Empty tag.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSSY" type="div3"/></tagDoc><?tei:EOF nbr.tag ??><!-- nbr            --><?tei:SOF node.tag ??><!-- ********** NODE                                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	node.tag,v $
# Revision 1.6  94/01/04  12:14:44  lou
# fix xrefs
# 
# Revision 1.5  1993/09/22  19:10:59  msmcq
# changes for publication of GD
#
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/09  19:40:55  msmcq
# restore RCS id, log
# --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : provide explicit att name for semi      --><!-- 93-09-17 : MSM : rename degr[ee], in, out                --><!-- 93-09-17 : MSM : add label2, for parallelism with ARC    --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version                       --><!--                  merge NODE and VERTEX tags              --><!--                  replace FS content by value=            --><!--                  eliminate LABEL content (retain label=) --><!--                  eliminate special drawing attributes    --><!--                      (use rend=)                         --><!-- ********** NODE                                          --><tagDoc id="NODE" usage="rwa"><gi tei="yes">node</gi><desc>encodes a node, a possibly labeled point in a graph.</desc><attList><attDef id="NDLAB" usage="opt"><attName>label</attName><desc>gives a label for a node.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>label2</attName><desc>gives a second label for a node.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default><remarks><p>Use this attribute together with the <att tei="yes">label</att>
attribute if a transducer is being encoded whose actions are
associated with nodes rather than with arcs.</p></remarks></attDef><attDef id="NDVALUE" usage="opt"><attName>value</attName><desc>provides the value of a node, which is a feature structure or
other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier.</valDesc><default>#IMPLIED</default></attDef><attDef id="NDTYPE" usage="opt"><attName>type</attName><desc>provides a type for a node.</desc><datatype>CDATA</datatype><valList type="semi"><val>initial</val><desc>initial node in a transition network</desc><val>final</val><desc>final node in a transition network</desc></valList><default>#IMPLIED</default></attDef><attDef id="NDADJTO" usage="rwa"><attName>adjTo</attName><desc>gives the IDs of the nodes which are adjacent to the current node.</desc><datatype>IDREFS</datatype><valDesc>A list of IDs.</valDesc><default>#IMPLIED</default></attDef><attDef id="NDADJFM" usage="rwa"><attName>adjFrom</attName><desc>gives the IDs of the nodes which are adjacent from the current
node.</desc><datatype>IDREFS</datatype><valDesc>A list of IDs.</valDesc><default>#IMPLIED</default></attDef><attDef id="NDADJ" usage="rwa"><attName>adj</attName><desc>gives the IDs of the nodes which are both adjacent to and
adjacent from the current node.</desc><datatype>IDREFS</datatype><valDesc>A list of IDs.</valDesc><default>#IMPLIED</default><remarks><p>Use this attribute instead of the <att tei="yes">adjTo</att> and
<att tei="yes">adjFrom</att> attributes when the graph is undirected and vice
versa if the graph is directed.</p></remarks></attDef><attDef id="NDINDG" usage="opt"><attName>inDegree</attName><desc>gives the in degree of the node, the number of nodes which
are adjacent from the given node.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="NDOUTDG" usage="opt"><attName>outDegree</attName><desc>gives the out degree of the node, the number of nodes which
are adjacent to the given node.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="NDDG" usage="opt"><attName>degree</attName><desc>gives the degree of the node, the number of arcs with which
the node is incident.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default><remarks><p>Use this attribute instead of the <att tei="yes">inDegree</att> and
<att tei="yes">outDegree</att> attributes when the graph is undirected and vice
versa if the graph is directed.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<node id=T6 label='6' inDegree=2 outDegree=0 type='final'>]]></eg></exemplum><part type="top" name="graphs"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="GDGR" type="div1"/></tagDoc><?tei:EOF node.tag ??><!-- node element --><?tei:SOF none.tag ??><!-- ************************************************************ --><!-- TAGDOC for NONE                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	none.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class boolean                    --><!-- 93-09-22 : MSM : extract from TDL group tagdoc           --><!-- ************************************************************ --><tagDoc id="NONE" usage="rwa"><gi tei="yes">none</gi><name>None value</name><desc>represents boolean <term>false</term> value variable.</desc><attList></attList><exemplum><eg><![CDATA[<f name=inflection><none>]]></eg></exemplum><part type="top" name="fs"/><classes names="BOOLEAN"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSBO" type="div3"/></tagDoc><?tei:EOF none.tag ??><!-- none           --><?tei:SOF normalzn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	normalzn.tag,v $
# Revision 1.2  94/01/04  12:14:45  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ************************************************normalization --><tagDoc id="NORMALZN" usage="opt"><gi tei="yes">normalization</gi><desc>indicates the extent of normalization or regularization of the
original source carried out in converting it to electronic form.</desc><attList><attDef usage="opt"><attName>source
   </attName><desc>indicates the authority for any normalization carried out.
    </desc><datatype>CDATA
   </datatype><valDesc>Should really be a bibliographic reference of some kind
   </valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>method
   </attName><desc>indicates the method adopted to indicate normalizations within
         the text.
   </desc><datatype>(silent|tags)
   </datatype><valList type="open"><val>silent</val><desc>normalization made silently
  </desc><val>tags</val><desc>normalization represented using editorial tags
   </desc></valList><default>silent</default></attDef></attList><exemplum><eg><![CDATA[<editorialDecl>
  <normalization id=WP5 source="WP5.1 spelling dict">
    <p>Converted to modern American spelling </normalization>
  <normalization id=NOED source=OED method=tags>
</editorialDecl>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/><xref target="CCAS2"/></tagDoc><?tei:EOF normalzn.tag ??><!-- normalization element --><?tei:SOF wsdnote.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	wsdnote.tag,v $
# Revision 1.2  94/01/04  12:15:46  lou
# fix xrefs
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** note --><tagDoc id="WSDNOTE" usage="opt"><gi tei="yes">note</gi><desc>(in a writing system) contains a note of any type.</desc><attList></attList><exemplum><eg><![CDATA[ <note>This writing system declaration describes the ad hoc
  character set developed for encoding Hebrew and Arabic for the
  Geniza Project at Princeton University.  It is intended for
  documentation of existing files only and should not be used to
  guide the implementation of new systems.
  </note>]]></eg></exemplum><exemplum><p>A note may also relate to a single character:</p><eg><![CDATA[ <note>This character is the Japanese form of the unified Han
  character xxxx in ISO 10646; for the Korean form, use the
  preceding character.</note>]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain character data only.</dataDesc><elemDecl>- O  (#PCDATA)</elemDecl><xref target="WDNO"/><xref target="WDOV"/></tagDoc><?tei:EOF wsdnote.tag ??><!-- note element (for WSD) --><?tei:SOF note.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	note.tag,v $
# Revision 1.5  94/01/15  21:16:35  msmcq
# revisions in connection with di, for p3; see comments for details
# 
# Revision 1.4  1994/01/04  12:14:45  lou
# fix xrefs
#
# Revision 1.3  1993/09/22  19:27:14  msmcq
# allow multiple targets
#
# Revision 1.2  1993/09/16  16:10:53  msmcq
# Add to terminologyInclusions class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-01-15 : MSM : add xref to di                          --><!-- 94-01-14 : MSM : mentioned, not cited                    --><!-- 94-01-14 : MSM : add to ditoplev class                   --><!-- 94-01-12 : MSM : targetEnd not target.end                --><!-- 93-09-17 : MSM : make target take IDREFS not IDREF       --><!-- 93-09-17 : MSM : (parallel to ptr, ref)                  --><!-- 93-09-15 : MSM : include in class termincl               --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-09 : MSM : target.end only for displaced notes     --><!-- 92-12-07 : MSM : change model to specialPara             --><!-- 92-12-07 : MSM : expand tabs                             --><!-- 92-11-23 : MSM : correct type in ATT end-tag             --><!-- ******************************************************** note --><tagDoc id="NOTE" usage="rec"><gi tei="yes">note</gi><desc>contains a note or annotation.</desc><attList><attDef usage="opt"><attName>n</attName><name>number or symbol</name><desc>indicates the symbol or number used to mark the note's point of
attachment to the main text.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[Mevorakh b. Saadya's mother, the matriarch of the family
during the second half of the eleventh century,
   <note n=126>
        The alleged mention of Judah Nagid's mother
        in a letter from 1071 is, in fact, a
        reference to Judah's children; cf. above,
        nn. 111 and 54.
   </note>
is well known from Geniza documents published by Jacob Mann.]]></eg><remarks><p>If notes are numbered in sequence and their numbering can be
reconstructed automatically by processing software, it may not be
considered necessary to record the note numbers.</p></remarks></attDef><attDef usage="opt"><attName>type</attName><desc>describes the type of note.</desc><datatype>CDATA</datatype><valDesc>Values can be taken from any convenient typology of annotation
suitable to the work in hand;  e.g. annotation, gloss, citation,
digression, preliminary, temporary, ...</valDesc><default>#IMPLIED</default></attDef><attDef usage="rwa"><attName>resp</attName><name>responsible</name><desc>indicates who is responsible for the annotation:  author, editor,
translator, etc.</desc><datatype>CDATA</datatype><valList type="open"><val>auth[or]
    </val><desc>note originated with the author of the text.
    </desc><val>ed[itor]
    </val><desc>note added by the editor of the text.
    </desc><val>comp[iler]
    </val><desc>note added by the compiler of a collection.
    </desc><val>tr[anslator]
    </val><desc>note added by the translator of a text.
    </desc><val>transcr[iber]
    </val><desc>note added by the transcriber of a text into electronic form.
    </desc><val>(initials)
    </val><desc>note added by the individual indicated by the initials.</desc></valList><default>#IMPLIED</default><remarks><p>For specialized types of editorial annotation (e.g. for
marking corrections, normalizations, cruxes, etc.), see chapter <xref target="TC" type="div1"/>.</p></remarks></attDef><attDef usage="opt"><attName>place</attName><desc>indicates where the note appears in the source text.</desc><datatype>CDATA</datatype><valList type="open"><val>foot
    </val><desc>note appears at foot of page.
    </desc><val>end
    </val><desc>note appears at end of chapter or volume.
    </desc><val>inline
    </val><desc>note appears as a marked paragraph in the
        body of the text.
    </desc><val>left
    </val><desc>note appears in left margin.
    </desc><val>right
    </val><desc>note appears in right margin.
    </desc><val>interlinear
    </val><desc>note appears between lines of the text.
    </desc><val>app[aratus]
    </val><desc>note appears in the apparatus at the foot of the
        page.</desc></valList><default>'unspecified'</default><eg></eg><remarks><p>For pages with multiple apparatus, values such as
<term>app1</term> and <term>app2</term> can be used.</p><p>The <att tei="yes">place</att> attribute can be used to indicate to text
formatting software where a note should be printed.  If the locations
indicated do not agree with those in the copy text, that fact should be
indicated in the TEI header.</p></remarks></attDef><attDef usage="opt"><attName>anchored</attName><desc>indicates whether the copy text shows the exact place of reference
for the note.</desc><datatype>(yes | no)</datatype><valList type="closed"><val>yes
    </val><desc>copy text indicates the place of attachment for the note.
    </desc><val>no
    </val><desc>copy text indicates no place of attachment for the note.</desc></valList><default>yes</default><remarks><p>In modern texts, notes are usually anchored by means of
explicit footnote or endnote symbols.  An explicit indication of the
phrase or line annotated may however be used instead (e.g.  <q>page 218,
lines 3-4</q>).  The <att tei="yes">anchored</att> attribute indicates whether any
explicit location is given, whether by symbol or by prose
cross-reference.  If the specific symbols used are to be recorded, use
the <att tei="yes">n</att> attribute.</p></remarks></attDef><attDef usage="rwa"><attName>target</attName><desc>indicates the point of attachment of a note, or the beginning of
the span to which the note is attached.</desc><datatype>IDREFS</datatype><valDesc>reference to the <att tei="yes">id</att>s of element(s) which begin at
the location in question (e.g. the <att tei="yes">id</att> of an <gi tei="yes">anchor</gi>
element).</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>If <att tei="yes">target</att> and <att tei="yes">targetEnd</att> are to be
used to indicate where notes attach to the text, then elements at the
appropriate locations (<gi tei="yes">anchor</gi> elements if necessary) must be
given <att tei="yes">id</att> values to be pointed at.</p></remarks></attDef><attDef usage="rwa"><attName>targetEnd</attName><desc>points to the end of the span to which the note is attached, if
the note is not embedded in the text at that point.</desc><datatype>IDREFS</datatype><valDesc>reference to the <att tei="yes">id</att>(s) of element(s) which
<emph>end</emph> at the location(s)
in question, or to an empty element at
the point in question.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[And yet it is not only in the great line of Italian
renaissance art, but even in the painterly
    <note resp=Tr><term lang=DE>Malerisch</term>.  This
    word has, in the German, two distinct meanings, one
    objective, a quality residing in the object, the
    other subjective, a mode of apprehension and creation.
    To avoid confusion, they have been distinguished in
    English as <mentioned>picturesque</> and
    <mentioned>painterly</> respectively.  (Tr.)</note>
style of the Dutch genre painters of the seventeenth
century that drapery has this psychological significance.]]></eg></exemplum><remarks><p></p></remarks><part type="top" name="core"/><classes names="NOTES BIBLPART TERMINCL DITOPLEV"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%specialPara;)</elemDecl><xref target="CONONO" type="div2"/><xref target="HD27"/><xref target="COBICON"/><xref target="DITPNO"/><xref target="TETA"/></tagDoc><?tei:EOF note.tag ??><!-- note element --><?tei:SOF notstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	notstmt.tag,v $
# Revision 1.2  94/01/04  12:14:46  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-08-19 : MSM : correct msc problem                     --><!-- ***********************************************notesStmt --><tagDoc id="NOTSTMT" usage="opt"><gi tei="yes">notesStmt</gi><name>Notes statement</name><desc>collects together any notes providing information about a text
additional to that recorded in other parts of the bibliographic
description.</desc><attList></attList><exemplum><eg><![CDATA[<notesStmt>
  <note>Historical commentary provided by Mark Cohen</note>
  <note>OCR scanning done at University of Toronto</note>
</notesStmt>]]></eg></exemplum><remarks><p>Information of different kinds should not be grouped
together into the same note.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o (note+)</elemDecl><xref target="HD27"/><xref target="HD2"/></tagDoc><?tei:EOF notstmt.tag ??><!-- notesStmt element --><?tei:SOF null.tag ??><!-- ************************************************************ --><!-- TAGDOC for NULL                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	null.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class featval                    --><!-- 93-09-22 : MSM : extract from group tagdoc               --><!-- ************************************************************ --><tagDoc id="NULL" usage="rwa"><gi tei="yes">null</gi><name>Null value</name><desc>represents the null set if <att tei="yes">org=set</att> is specified for the
feature of which it is the value; represents the null bag if
<att tei="yes">org=bag</att> is specified for the feature of which it is the value;
represents the null list if <att tei="yes">org=list</att> is specified for the
feature of which it is the value; has no interpretation if
<att tei="yes">org=single</att> is specified for the feature of which it is the
value.</desc><attList></attList><exemplum><eg><![CDATA[<f name=empty org=list><null>]]></eg></exemplum><remarks><p>If the <gi tei="yes">null</gi> element occurs as the value of a
feature, it must be the only value.  It is also a semantic error for the
<att tei="yes">org</att> attribute of that feature to have the value
<term>single</term>.</p></remarks><part type="top" name="fs"/><classes names="FEATVAL"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSSS" type="div3"/></tagDoc><?tei:EOF null.tag ??><!-- null           --><?tei:SOF num.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	num.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-06 : MSM : allow improper fractions                --><!-- ********************************************************* num --><tagDoc id="NUM" usage="opt"><gi tei="yes">num</gi><name>number</name><desc>contains a number, written in any form.</desc><attList><attDef usage="opt"><attName>type</attName><desc>indicates the type of numeric value.</desc><datatype>CDATA</datatype><valList type="semi"><val>cardinal </val><desc>absolute number, e.g. <q>21</q>, <q>21.5</q></desc><val>ordinal  </val><desc>ordinal number, e.g. <q>21st</q></desc><val>fraction </val><desc>fraction, e.g. <q>one half</q> or <q>three halves</q></desc><val>percentage </val><desc>e.g. <q>ten percent</q></desc></valList><default>#IMPLIED</default><remarks><p>If a different typology is desired, other values can be used
for this attribute.</p></remarks></attDef><attDef usage="opt"><attName>value</attName><desc>supplies the value of the number in an application-dependent
standard form.</desc><datatype>CDATA</datatype><valDesc>any numeric value in the chosen standard form.</valDesc><default>#IMPLIED</default><remarks><p>The standard form used should be described in the
<gi tei="yes">std.vals</gi> element in the TEI header.  Standard forms may be
defined from scratch, or borrowed from existing practice (e.g.
<q>Standard values are given in the notation defined for numeric
constants in the C language.</q>)</p></remarks></attDef></attList><exemplum><eg><![CDATA[<num type=cardinal value='21'>twenty-one</num>
<num type=cardinal value='1.5'>1.5</num>
He stands <num type=cardinal value='1.9'>1 &middot; 90</num>m. high.]]></eg></exemplum><remarks><p>Detailed analyses of quantities and units of measure in
historical documents should use the feature structure mechanism
described in chapter <xref target="FS"/>.	The <gi tei="yes">num</gi> element is
intended for use in simple applications.</p></remarks><part type="top" name="core"/><classes names="DATA"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONANU" type="div3"/></tagDoc><?tei:EOF num.tag ??><!-- num element --><?tei:SOF number.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	number.tag,v $
# Revision 1.1  94/01/15  21:00:02  msmcq
# Initial revision
#  --><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : Made file from old di NUM element       --><!-- ************************************************* number --><tagDoc id="NUMBER" usage="rec"><gi tei="yes">number</gi><desc>indicates grammatical number associated with a form, as given
in a dictionary.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type=num</tag>.</p></remarks><part type="base" name="dict"/><classes names="DIPARTS MORPH DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%paraContent;)</elemDecl><xref target="DITPFO" type="div2"/><xref target="DITPGR" type="div2"/></tagDoc><?tei:EOF number.tag ??><!-- number --><?tei:SOF occasion.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	occasion.tag,v $
# Revision 1.2  94/03/15  11:10:37  lou
# minor typos etc
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 6 Mar : LB: rename from relevent --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- 93-06-02 : MSM : rename from event                       --><!-- relEvent --><tagDoc id="OCCASION" usage="opt"><gi tei="yes">occasion</gi><desc>a temporal expression (either a date or a time)
given in terms of a named occasion such as a holiday,
a named time of day, or some notable event.</desc><attList></attList><exemplum><eg><![CDATA[In New York, 
  <dateStruct value='1-1'>
    <occasion type=holiday>New Years Day</occasion>
  </dateStruct> is the quietest of holidays, 
  <dateStruct value='4 July'>
    <occasion type=holiday>Independence Day</occasion>
  </dateStruct>
the most turbulent.]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="TEMPEXP"/><elemDecl>- - (%phrase.seq)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF occasion.tag ??><!-- occasion --><?tei:SOF occupat.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: occupat.tag,v $
    * Revision 1.2  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************** occupat --><tagDoc id="OCCUPAT" usage="opt"><gi tei="yes">occupation</gi><desc>contains an informal description of a person's trade,
profession or occupation.</desc><attList><attDef usage="opt"><attName>scheme</attName><desc>identifies the classification system or taxonomy in use by supplying
the identifier of a <gi tei="yes">taxonomy</gi> element elsewhere in the header.</desc><datatype>IDREF</datatype><valDesc>must identify a <gi tei="yes">taxonomy</gi> element</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>code</attName><desc>identifies an occupation code defined within the
classification system or taxonomy defined by the <att tei="yes">scheme</att>
attribute.</desc><datatype>IDREF</datatype><valDesc>Must identify a <gi tei="yes">category</gi> element</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <occupation>accountant</occupation>]]></eg></exemplum><exemplum><eg><![CDATA[  <occupation scheme=RG code=ACC>accountant</occupation>]]></eg></exemplum><exemplum><eg><![CDATA[  <occupation scheme=RG code=ACC>
        accountant with specialist knowledge of oil industry
  </occupation>]]></eg></exemplum><remarks><p>The content of this element may be used as an alternative
to the more formal specification made possible by its attributes; it
may also be used to supplement the formal specification with commentary
or clarification.</p></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl> - - (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF occupat.tag ??><!-- occupation element --><?tei:SOF offset.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	offset.tag,v $
# Revision 1.2  94/03/07  16:14:40  lou
# revised for publicn
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--******************************************************** offset --><tagDoc id="OFFSET" usage="opt"><gi tei="yes">offSet</gi><name>offset</name><desc>that  part of a relative temporal or spatial expression
which indicates the direction of the offset between the two place
names, dates, or times involved in the expression. </desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="aux" name="ND"/><classes names="PLACPART TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF offset.tag ??><!-- offset element --><?tei:SOF ofig.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ofig.tag,v $
# Revision 1.4  94/03/21  14:33:09  lou
# second major typo purge
# 
# Revision 1.3  1994/01/04  12:14:47  lou
# fix xrefs
#
# Revision 1.2  1993/09/16  16:11:51  msmcq
# Content model revision as per A.M.
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : changes agreed with A Melby by phone    --><!-- 93-09-15 : MSM : (to agree with tig)                     --><!-- 92-12-23 : MSM : expand TC37dd entity                    --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- *************************************************** ofig --><tagDoc id="OFIG" usage="rwa"><gi tei="yes">ofig</gi><name>other-form information group</name><desc>within a <gi tei="yes">tig</gi> element, contains information
elements relating to a single <gi tei="yes">otherForm</gi>.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the other-form information group according to some
convenient typology, preferably the dictionary of data element types
specified in ISO WD 12 620.</desc><datatype>CDATA</datatype><valDesc>any string identifying a class of <gi tei="yes">ofig</gi></valDesc><default>#IMPLIED</default><remarks><p>A much fuller list of values for the <att tei="yes">type</att>
attribute may be generated from the dictionary of data element types
under preparation as ISO TC 37/SC 3/WD 12 620, Computational Aids in
Terminology.  See ISO 12 620 for fuller details.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="term"/><classes/><dataDesc>May contain an <gi tei="yes">otherForm</gi> element and any data
elements relating to the <gi tei="yes">otherForm</gi> or to one of its related
elements.</dataDesc><elemDecl>- O
((%m.terminologyMisc)*, (otherForm, gram*), (%m.terminologyMisc)*)</elemDecl><xref target="TEDTN" type="div1"/><xref target="TETA" type="div1"/></tagDoc><?tei:EOF ofig.tag ??><!-- ofig element --><?tei:SOF opener.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: opener.tag,v $
    * Revision 1.5  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.4  1998/01/28 19:22:39  tei
    * LB changes of 1998-01
    *
    * Revision 1.3  1994/03/15  11:10:37  lou
    * minor typos etc
    * 
    * Revision 1.2  1994/01/04  12:14:47  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- 4 Jan 98 : LB : applied DIVTOP fix --><!-- Maybe content model should include anything in %m.divtop except --><!-- opener itself (which should be removed from divtop and put into --><!-- its own class maybe?). Not clear why both byLine and docAuthor, --><!-- dateLine and docDate are allowed. Added only the former, also   --><!-- argument; added dateLine to divTop.                             --><!-- *******************************************************opener --><tagDoc id="OPENER" usage="opt"><gi tei="yes">opener</gi><desc>groups together dateline, byline, salutation, and similar
phrases appearing as a preliminary group at the start of a
division, especially of a letter.</desc><attList></attList><exemplum><eg><![CDATA[<opener><dateline>Walden, this 29. of August 1592</dateline></opener>]]></eg></exemplum><exemplum><eg><![CDATA[ <opener>
   <dateline><name type=place>Great Marlborough Street</name>
   <date>November 11, 1848</date>
   </dateline>
   <salute>My dear Sir,</salute>
</opener>
<p>I am sorry to say that absence from town and other
circumstances have prevented me from earlier enquiring...]]></eg><!-- Trollope Autobiog, p 77 --></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVTOP"/><elemDecl>- O (argument | byline |  dateline | epigraph | salute | signed 
 | %phrase.seq;)* </elemDecl><!-- formerly:  (signed | dateline | salute | %phrase.seq;)*  --><xref target="DSCO"/><xref target="DSDTB"/></tagDoc><?tei:EOF opener.tag ??><!-- opener element --><?tei:SOF oref.tag ??><!-- Revisions:                                               --><!-- 94-01-15 : MSM : comment on remarks on need for revision --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-13 : MSM : remove from diparts to avoid ambiguity  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	oref.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** oRef --><tagDoc id="OREF" usage="opt"><gi tei="yes">oRef</gi><name>orthographic-form reference</name><desc>in a dictionary example, indicates a reference to the
orthographic form(s) of the headword.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>indicates the kind of typographic modification made to the
headword in the reference.</desc><datatype>CDATA</datatype><valList type="open"><val>cap </val><desc>indicates first letter is given as capital</desc><val>nohyph </val><desc>indicates that the headword, though a prefix or
suffix, loses its hyphen</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks><!-- [Need examples.  What do the sample values mean?  Is     --><!-- this attribute synonymous with <att>rend</att>?  If      --><!-- so, suppress; if not, explain how not.  Should this      --><!-- attribute be merged with <att>type</att> on              --><!-- <gi>oVar</gi> and inherited from a class?  -Ed.]         --></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="FORMPTRS DIGLOBAL"/><dataDesc>Empty element.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="DIHW"/></tagDoc><?tei:EOF oref.tag ??><!-- oRef element --><?tei:SOF orgdivn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	orgdivn.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1993/08/03  02:09:53  msmcq
    * fix MS end, fix or flag valdesc problems
    *--><!-- Revisions:                                               --><!-- 7 jan 98 : LB : fix capitalization --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-04 : MSM : fix empty valdesc                       --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!--           orgDivn       --><tagDoc id="ORGDIVN" usage="opt"><gi tei="yes">orgDivn</gi><name>organizational division</name><desc>indicates a division, branch or department specified
in an organizational name.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>more fully describes the organization division specified in the
name component.
Possible values include <q>branch</q>, <q>department</q>,
<q>section</q>,
<q>division</q>, etc.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a normalized or regularized form of the organizational
division.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>In providing a <soCalled>regularized</soCalled> form, no
claim is made that the form in the source text is incorrect; the
regularized form is simply that chosen as the main form for purposes
of unifying variant forms under a single heading.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<orgName type=academic key=DMHGU1>
<orgDivn type=department>
    Department of
    <orgType type=function>Modern History</orgType>
</orgDivn>,
Glasgow
<orgType type=function>University</orgType></orgName>]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes/><elemDecl>- - (%phrase.seq) </elemDecl><xref target="NDORG"/></tagDoc><?tei:EOF orgdivn.tag ??><!-- orgdivn element --><?tei:SOF orgname.tag ??><!-- Revisions:                                               --><!-- 3 jan 98 : LB : restore missing </elemDecl> --><!-- 94-08-04 : MSM : fix REACH:  make member of DATA         --><!-- 94-03-31 : MSM : for prhase.seq read phrase.seq          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: orgname.tag,v $
    * Revision 1.6  1998/02/01 17:47:00  tei
    * *** empty log message ***
    *
    * Revision 1.5  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.4  1994/10/20  14:23:16  lou
    * Make content model more consistent with others
    * 
    * Revision 1.3  1994/08/29  15:25:03  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.2  1994/04/01  17:44:00  msmcq
    * correct typo in content model
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!--**********************************************orgname --><tagDoc id="ORGNAME" usage="opt"><gi tei="yes">orgName</gi><name>organization name</name><desc>contains an organizational name. </desc><attList><attDef usage="mwa"><attName>type</attName><desc>more fully describes the organization indicated in the
organizational name. Possible values include <q>voluntary</q>,
<q>political</q>, <q>governmental</q>, <q>industrial</q>,
<q>commercial</q>, etc.</desc><datatype>CDATA</datatype><valDesc></valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>key</attName><desc>provides an alternative identifier for the organization being
named, such as a database record key.</desc><datatype>CDATA</datatype><valDesc>any string</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>The value may be a unique identifier from a database, or
simply a more explicit name for the referent. Its purpose is only to
record an identification; if the analysis leading to the identification
is to be recorded as well, the analytic tags described in chapter<xref target="FS"/>
 should be used in addition or instead.</p></remarks></attDef><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a normalized or regularized form of the organization name</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>In providing a <soCalled>regularized</soCalled> form, no
claim is made that the form in the source text is incorrect; the
regularized form is simply that chosen as the main form for purposes
of unifying variant forms under a single heading.</p></remarks></attDef></attList><exemplum><eg><![CDATA[About a year back, a question of considerable interest was
agitated in the
<orgName key=PAS1 type=voluntary reg=Pennsylvania Abolition Society'>
Pennsyla. Abolition Society</orgName>.]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes names="DATA"/><elemDecl>- - (orgTitle|orgType|orgDivn| %m.phrase | #pcdata)* </elemDecl><xref target="NDORG"/></tagDoc><?tei:EOF orgname.tag ??><!-- orgName element --><?tei:SOF orgtitle.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	orgtitle.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1993/08/03  02:09:53  msmcq
    * fix MS end, fix or flag valdesc problems
    *--><!-- Revisions:                                               --><!-- 7 jan 98 : LB : fix capitalization --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-04 : MSM : fix empty valdesc                       --><!-- 93-05-29 : MSM : fix ]]>, add missing delim to example   --><!-- *******************************************************orgTitle --><tagDoc id="ORGTITLE" usage="opt"><gi tei="yes">orgTitle</gi><name>organization title</name><desc>contains the proper name component of an organizational
name. </desc><attList><attDef usage="mwa"><attName>type</attName><desc>more fully describes the organization title. Possible values
include <q>formal</q>,
<q>colloquial</q>, <q>acronym</q>, etc.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a normalized or regularized form of the organization title.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>In providing a <soCalled>regularized</soCalled> form, no
claim is made that the form in the source text is incorrect; the
regularized form is simply that chosen as the main form for purposes
of unifying variant forms under a single heading.</p></remarks></attDef></attList><exemplum><eg><![CDATA[Mr Frost will be able to earn an extra fee from
<orgName type=media key=BSB1>
<orgTitle type=acronym>BSkyB</orgTitle></orgName>
rather than the <orgName type=media key=BBC1>
<orgTitle type=acronym reg='British Broadcasting Corporation'>BBC
</orgTitle></orgName>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl>- - (%phrase.seq) </elemDecl><xref target="NDORG"/></tagDoc><?tei:EOF orgtitle.tag ??><!-- orgtitle element --><?tei:SOF orgtype.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	orgtype.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1993/08/03  02:09:53  msmcq
    * fix MS end, fix or flag valdesc problems
    *--><!-- Revisions:                                               --><!-- 7 jan 98 : LB : fix capitalization --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-04 : MSM : fix empty valdesc                       --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- 93-05-29 : MSM : cosmetic changes, minor Script-oriented fixes --><!-- orgtype --><tagDoc id="ORGTYPE" usage="opt"><gi tei="yes">orgType</gi><name>organization type</name><desc>indicates a part of the organization name which contains
information about the organization's structure or function.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>more fully describes the organization type specified in the name
component.  Possible values include <q>function</q>, <q>structure</q>,
etc.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a normalized or regularized form of the organization type</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><eg></eg><remarks><p>In providing a <soCalled>regularized</soCalled> form, no
claim is made that the form in the source text is incorrect; the
regularized form is simply that chosen as the main form for purposes
of unifying variant forms under a single heading.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<orgName type='utility company' key=WWPC1>Washington
<orgType type=function>Water Power</orgType> <orgType
reg='incorporated' type=structure>Inc.</orgType></orgName>]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes/><elemDecl>- - (%phrase.seq) </elemDecl><xref target="NDORG"/></tagDoc><?tei:EOF orgtype.tag ??><!-- orgtype element --><?tei:SOF orig.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	orig.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1994/01/04  12:14:48  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : fix typo noted by Syd --><!-- 92-12-10 : MSM : suppress mention of retroversion        --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- 92-11-09 : MSM : change id ref                           --><!-- ******************************************************** orig --><tagDoc id="ORIG" usage="opt"><gi tei="yes">orig</gi><name>original form</name><desc>contains the original form of a reading, for which a
regularized form is given in an attribute value.</desc><attList><attDef usage="opt"><attName>reg</attName><name>regularization</name><desc>gives a regularized (normalized) form of the text.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>identifies the individual responsible for the regularization
of the word or phrase.</desc><datatype>CDATA</datatype><valDesc>any string of characters, typically the initials of the
individual involved, or a role identifier like <q>editor</q> if not
known by name.</valDesc><default>#IMPLIED</default><eg></eg></attDef></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="top" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="COEDREG" type="div2"/><xref target="TC" type="div1"/></tagDoc><?tei:EOF orig.tag ??><!-- orig element --><?tei:SOF orth.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	orth.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-01-15 : MSM : allow end-tag omission                  --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM :  add to forminfo class                  --><!-- 94-01-12 : MSM : suppress dleaves class                  --><!-- 93-06-04 : MSM : supply default                          --><!-- ************************************************* orth   --><tagDoc id="ORTH" usage="rec"><gi tei="yes">orth</gi><name>orthographic form</name><desc>gives the orthographic form of a dictionary headword.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>gives the type of spelling.</desc><datatype>CDATA</datatype><valDesc>Any convenient word or phrase, e.g. <q>lat</q> (latinate),
<q>std</q> (standard), <q>trans</q> (transliterated), etc.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef><!-- ................................................. extent --><attDef usage="opt"><attName>extent</attName><desc>gives the extent of the orthographic information provided.</desc><datatype>CDATA</datatype><valList type="open"><val>full </val><desc>full form</desc><val>pref </val><desc>prefix</desc><val>suff </val><desc>suffix</desc><val>part </val><desc>partial</desc></valList><default>full</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[<!>]]></eg></exemplum><part type="base" name="dict"/><classes names="DIPARTS FORMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent)</elemDecl><xref target="DITPFO" type="div2"/></tagDoc><?tei:EOF orth.tag ??><!-- orth element --><?tei:SOF othform.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: othform.tag,v $
    * Revision 1.4  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.3  94/03/21  14:33:10  lou
    * second major typo purge
    * 
    * Revision 1.2  1994/01/04  12:14:49  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 92-12-21 : MSM : mention iso 12620 in desc               --><!-- 92-12-18 : MSM : remove FLATTERM class                   --><!-- 92-12-18 : MSM : added TYPE attribute                    --><!-- 92-12-18 : MSM : revise desc, compromising with SEW      --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- ********************************************** otherform --><tagDoc id="OTHFORM" usage="rec"><gi tei="yes">otherForm</gi><name>other form</name><desc>contains an
alternate designation for the concept treated by the
term entry, such as a synonym.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the <gi tei="yes">otherForm</gi> using some typology,
preferably the dictionary of data element types specified in
ISO WD 12 620.</desc><datatype>CDATA</datatype><valDesc>any string of characters; for serious terminological work,
values should be taken from the dictionary of data element types
specified in ISO WD 12 620.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>In nested term entries, the <gi tei="yes">otherForm</gi> belongs to
the same terminological information group as the term for which it is an
alternate.</p></remarks><part type="base" name="term"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="TEDTF" type="div1"/><xref target="TEDTN" type="div1"/><xref target="TETA" type="div1"/></tagDoc><?tei:EOF othform.tag ??><!-- otherForm element --><?tei:SOF ovar.tag ??><!-- Revisions:                                               --><!-- 94-01-15 : MSM : comment on remarks on need for revision --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-13 : MSM : remove from diparts to avoid ambiguity  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ovar.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** oVar --><tagDoc id="OVAR" usage="opt"><gi tei="yes">oVar</gi><name>orthographic-variant reference</name><desc>in a dictionary example, indicates a reference to variant
orthographic form(s) of the headword.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>indicates the kind of variant involved.</desc><datatype>CDATA</datatype><valList type="open"><val>pt </val><desc>past tense</desc><val>pp </val><desc>past participle</desc><val>prp </val><desc>present participle</desc><val>f </val><desc>feminine</desc><val>pl </val><desc>plural</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks><!-- [Need examples, to clarify how this differs from other   --><!-- grammatical markup.  Merge with <att>type</att> on       --><!-- <gi>oRef</gi>?  <p>-Ed.]                                 --></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="FORMPTRS DIGLOBAL"/><dataDesc>Character data or <gi tei="yes">oRef</gi>.</dataDesc><elemDecl>- -  (#PCDATA | oRef)*</elemDecl><xref target="DI"/></tagDoc><?tei:EOF ovar.tag ??><!-- oVar element --><?tei:SOF p.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	p.tag,v $
# Revision 1.3  94/01/04  12:14:49  lou
# fix xrefs
# 
# Revision 1.2  1993/08/23  16:38:32  msmcq
# Changes at publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change class to CHUNK, after disc w/LB  --><!-- 92-12-06 : MSM : correct content model                   --><!-- *********************************************************** p --><tagDoc id="P" usage="req"><gi tei="yes">p</gi><name>paragraph</name><desc>marks paragraphs in prose.</desc><attList></attList><exemplum><eg><![CDATA[<p>Hallgerd was outside.  <q>There is blood on your
axe,</q> she said.  <q>What have you done?</q></p>
<p><q>I have now arranged that you can be married a
second time,</q> replied Thjostolf.</p>
<p><q>Then you must mean that Thorvald is dead,</q>
she said.</p>
<p><q>Yes,</q> said Thjostolf.  <q>And now you must
think up some plan for me.</q>]]></eg></exemplum><remarks><p>In some contexts, the paragraph may have a specialized
meaning, e.g. in the tag set for dictionaries, <gi tei="yes">p</gi> is used to
enclose any running text, and thus does not imply text set off as is
conventionally done in running prose.</p></remarks><part type="top" name="core"/><classes names="CHUNK"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="COPA" type="div2"/><xref target="DRPAL" type="div2"/></tagDoc><?tei:EOF p.tag ??><!-- p element --><?tei:SOF plpage.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-13 : MSM : xref was cors3, now NHrs                --><!-- 93-09-13 : MSM : drop dot in id                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	plpage.tag,v $
# Revision 1.2  93/09/16  16:16:16  msmcq
# Change ID, change xref, cosmetic
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************************** plpage --><tagDoc id="PLPAGE" usage="opt"><gi tei="yes">page</gi><desc>marks pages in a reference edition.</desc><attList></attList><exemplum><eg><![CDATA[    <(La)page n=32> ... [text of edition La, page 32]
    <(La)page n=32> ... [text of edition La, page 33]
    <(La)page n=32> ... [text of edition La, page 34]
    <(La)page n=32> ... [text of edition La, page 35]]]></eg></exemplum><remarks><p>The <gi tei="yes">page</gi> element in a concurrent page-reference DTD
may be subdivided into columns or lines if desired, or left unanalysed.</p></remarks><part type="base" name="print"/><classes/><dataDesc>May contain <gi tei="yes">col</gi> elements, <gi tei="yes">line</gi> elements, or
character data.</dataDesc><elemDecl>- O  (#PCDATA | line | col)*</elemDecl><xref target="NHRS" type="div3"/></tagDoc><?tei:EOF plpage.tag ??><!-- page tag (in PL tag set) --><?tei:SOF parents.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- 93-09-11 : MSM : correct content model                   --><!-- 93-09-11 : MSM : change dataDesc                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	parents.tag,v $
# Revision 1.2  93/09/16  16:15:21  msmcq
# Publication of TD
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** parents --><tagDoc id="PARENTS" usage="req"><gi tei="yes">parents</gi><desc>lists elements which can directly contain this element.</desc><attList></attList><exemplum><eg><![CDATA[   <parents>head, title]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>a list of valid SGML names separated by commas or spaces.</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><!-- odd system has PCDATA, 1st draft here had (NAMES) --><!-- PCDATA it has to be. --><xref target="TDTAG"/></tagDoc><?tei:EOF parents.tag ??><!-- parents element --><?tei:SOF part.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : allow name, type                        --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	part.tag,v $
# Revision 1.5  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.4  1994/01/04  12:14:51  lou
# fix xrefs
#
# Revision 1.3  1993/09/16  16:15:21  msmcq
# Publication of TD
#
# Revision 1.2  1993/08/13  20:50:02  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************************** part --><tagDoc id="PART" usage="opt"><gi tei="yes">part</gi><desc>specifies the module or part to which a particular element,
element class, or entity belongs in a modular encoding scheme such
as the TEI.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>indicates whether the tag set is a base, additional, core, or
auxiliary tag set.</desc><datatype>CDATA</datatype><valList type="semi"><val>core</val><desc>a core tag set (part of every document)</desc><val>base</val><desc>a base tag set</desc><val>add</val><desc>an additional tag set</desc><val>aux</val><desc>an auxiliary tag set</desc></valList><default>#IMPLIED</default></attDef><!-- ................................................... name --><attDef usage="opt"><attName>name</attName><desc>indicates the specific tag set or part in question, usually by
means of an identifier or short form.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[   <part type=base name=di>Base tag set for print dictionaries</part>]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes/><dataDesc>A descriptive phrase identifying the module concerned.</dataDesc><elemDecl>- O (#PCDATA)</elemDecl><xref target="TDTAG"/><xref target="TDCLA"/></tagDoc><?tei:EOF part.tag ??><!-- part element --><?tei:SOF partdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: partdesc.tag,v $
    * Revision 1.4  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.3  94/04/01  17:41:18  msmcq
    * Changes while checking DTD
    * 
    * Revision 1.2  1994/01/04  12:14:52  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : change model (for participant, read person) --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* partdesc --><tagDoc id="PARTDESC" usage="opt"><gi tei="yes">particDesc</gi><name>participation description</name><desc>describes the identifiable speakers, voices or other participants
in a linguistic interaction. </desc><attList></attList><exemplum><eg><![CDATA[<particDesc>
<person id=P1 sex=F age=42>
  <p>Female informant, well-educated, born in Shropshire
   UK, 12 Jan 1950, of unknown occupation.
   Speaks French fluently. Socio-Economic status B2.
</person>
<person id=P2 sex=M age=43>
<particLinks>
   <relation active="P1 P2" desc="spouse">
</particLinks>
</particDesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DECLABL"/><dataDesc>May contain a prose description organized as paragraphs, or a
structured list of persons and person groups, with an optional
formal specification of any relationships amongst them.</dataDesc><elemDecl>- o (p+ | ( (person | personGrp)+, particLinks?) )</elemDecl><xref target="CCAH"/><xref target="HD4"/><xref target="CCAS2"/></tagDoc><?tei:EOF partdesc.tag ??><!-- particDesc element --><?tei:SOF partirel.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: partirel.tag,v $
    * Revision 1.2  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.1  93/06/23  11:28:40  lou
    * Initial checkin
    *  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* partirel --><tagDoc id="PARTIREL" usage="opt"><gi tei="yes">particLinks</gi><name>participant relationships</name><desc>describes the relationships or social links existing between
participants in a linguistic interaction. </desc><attList></attList><exemplum><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></exemplum><exemplum><eg><![CDATA[<particLinks>
  <p>The persons with ids P1 and P2 are the parents of
     P3 and P4. P1 and P2 are married to each other.
     P1 is the employer of P3, P5., P6, and P7.</p>
</particLinks>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc>May contain a prose description organized as paragraphs, or
a sequence of <gi tei="yes">relation</gi> elements.</dataDesc><elemDecl>- o (p+ |  relation+) </elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF partirel.tag ??><!-- particLinks element --><?tei:SOF pause.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pause.tag,v $
# Revision 1.4  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.3  1994/01/04  12:14:53  lou
# fix xrefs
#
# Revision 1.2  1993/09/21  11:07:33  lou
# added to spoken class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************** pause --><tagDoc id="PAUSE" usage="rec"><gi tei="yes">pause</gi><desc>a pause either between or within utterances.</desc><attList><attDef usage="opt"><attName>type</attName><desc>categorizes the pause in some respect.</desc><datatype>CDATA</datatype><valDesc>An open list</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>who</attName><desc>supplies an identifier for the person or group pausing.
         Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
         or <tag compl="full" tei="yes">participant.grp</tag> element in the TEI header.</desc><datatype>IDREF</datatype><valDesc>Must identify a participant or participant group within the
       TEI Header</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<pause type=pregnant dur=42>]]></eg></exemplum><remarks></remarks><part type="base" name="ts"/><classes names="COMPSPOK TIMED"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TSBAFD"/><xref target="TSBA"/><xref target="TSBAPA"/></tagDoc><?tei:EOF pause.tag ??><!-- pause element --><?tei:SOF pagebr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pagebr.tag,v $
# Revision 1.3  94/01/04  12:14:50  lou
# fix xrefs
# 
# Revision 1.2  1993/12/20  15:32:32  lou
# changed id to match filename
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 25 dec 93: LB change class membership to refsys --><!-- 93-02-11 : MSM : loc class has id clloc not loc          --><!-- ****************************************************** pagebr --><tagDoc id="PAGEBR" usage="opt"><gi tei="yes">pb</gi><name>page break</name><desc>marks the boundary between one page of a text and the next
in a standard reference system.</desc><attList><attDef usage="rec"><attName>ed</attName><name>edition</name><desc>indicates the edition or version in which the page break is located
at this point</desc><datatype>CDATA</datatype><valDesc>Any string of characters; usually a siglum conventionally used
for the edition.</valDesc><default>#IMPLIED</default><eg><![CDATA[	<pb ed=Riverside n=123>]]></eg></attDef><attDef usage="opt"><attName>n</attName><name>number or name</name><desc>indicates the number or other value associated with the page
which follows the point of insertion of this <gi tei="yes">pb</gi>.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>Encoders should adopt a clear and consistent policy as to
whether the numbers associated with page breaks relate to the physical
sequence number of the page or the page number or signature printed on it.
By convention, <gi tei="yes">pb</gi> elements should appear at the start of the
page to which they refer.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>Like other forms of milestone tag, <gi tei="yes">pb</gi> tags cannot
be automatically verified by SGML; for better validation, a
concurrent markup stream should be used.</p></remarks><part type="top" name="core"/><classes names="REFSYS"/><elemDecl>- O EMPTY</elemDecl><xref target="CORS5" type="div3"/></tagDoc><?tei:EOF pagebr.tag ??><!-- pb element --><?tei:SOF per.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : note synonymy with GRAM                 --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	per.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** per --><tagDoc id="PER" usage="opt"><gi tei="yes">per</gi><name>person</name><desc>contains an indication of the grammatical person (1st, 2d, 3d,
etc.) associated with a given inflected form in a dictionary.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type=person</tag>.</p></remarks><part type="base" name="dict"/><classes names="MORPH DIPARTS DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/></tagDoc><?tei:EOF per.tag ??><!-- per element --><?tei:SOF perform.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: perform.tag,v $
    * Revision 1.7  1998/02/09 18:02:36  tei
    * fix egs
    *
    * Revision 1.6  94/01/04  12:14:55  lou
    * fix xrefs
    * 
    * Revision 1.5  1993/08/23  16:48:38  msmcq
    * version published with DR
    * 
    * Revision 1.4  1993/08/13  20:50:04  msmcq
    * Clean ^Z
    * 
    * Revision 1.3  1993/08/12  21:31:15  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.2  1993/08/03  02:10:18  msmcq
    * fix MS end
    * change content model
    * --><!-- Revisions:                                               --><!-- 93-08-20 : MSM : cosmetic changes                        --><!-- 93-08-20 : MSM : cast list two words                     --><!-- 93-08-18 : MSM : simplify content model radically        --><!-- 93-08-18 : MSM : disambiguate content model              --><!-- 93-08-18 : MSM : component is just a name not a class    --><!-- 93-08-07 : MSM : change P to COMPONENT in content model  --><!-- 93-08-07 : MSM : Added divtop, divbot to content model   --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- 93-05-29 : MSM : fix ]]>, fix ambiguous content model    --><!-- ************************************************ perform --><tagDoc id="PERFORM" usage="mwa"><gi tei="yes">performance</gi><desc>contains a section of front or back matter describing how a
dramatic piece is to be performed in general or how it was performed
on some specific occasion. </desc><attList></attList><exemplum><eg><![CDATA[<performance>
<p><rs type=place>Gateway Theatre, Edinburgh</rs>,
<date>6 September 1948</date>
<castList>
    <castItem><role>Anath Bithiah</>
       <actor>Athene Seyler</actor>
    <!-- ... -->
    <castItem><role>Shendi</role>
       <actor>Robert Rietty</actor>
  </castList>
  <p>Directed by <name>E. Martin Browne</name>
</performance>]]></eg></exemplum><exemplum><eg><![CDATA[<performance>
  <p>Cast of the original production at the
    <rs type=place>Savoy Theatre, London,</rs>
  on <date>September 24, 1907</>
  <castList>
    <castItem>Colonel Hope : Mr A.E.George</castItem>
    <!-- ... -->
  </castList>
</performance>]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes names="DRFRONT"/><dataDesc>contains paragraphs and an optional cast list only.</dataDesc><elemDecl>- - ((%m.divtop)*, (%component)+, (%m.divbot)*)</elemDecl><!-- This allows multiple cast lists in the performance       --><!-- element.  Alternatively, we can remove castlist from     --><!-- the class comp.drama, and define perform thus:  (msm)    --><!--      - - ((%m.divtop)*,                                  --><!--           ((castList, (%component.seq))+                 --><!--            | ((%component)+, (castList, (%component.seq))*)), --><!--           (%m.divbot)*)</elemDecl>                       --><xref target="DRPERF"/><xref target="DRFAB" type="div3"/></tagDoc><?tei:EOF perform.tag ??><!-- performance element --><?tei:SOF persname.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	persname.tag,v $
# Revision 1.8  94/10/20  14:22:48  lou
# add to class data (post P3 fix)
# 
# Revision 1.7  1994/07/28  22:08:00  msmcq
# fix typo
#
# Revision 1.6  1994/07/28  20:07:01  msmcq
# Change while finishing TEI P3 (change to desc)
#
# Revision 1.5  1994/04/01  17:41:18  msmcq
# Changes while checking DTD
#
# Revision 1.4  1994/03/15  11:10:38  lou
# minor typos etc
#
# Revision 1.3  1994/03/07  16:14:18  lou
# revisions for publication
#
# Revision 1.2  1993/08/03  02:10:42  msmcq
# fix MS end
# add to class demog
# fix (or just flag?) empty valdesc
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : change desc                             --><!-- 94-03-31 : MSM : change model                            --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : add to demog class                      --><!-- 93-06-03 : MSM : fix ]]                                  --><!-- 93-05-29 : MSM : cosmetic and cleanup changes            --><!-- 93-05-29 : MSM : key and reg should be inherited from NAMES --><!-- ******************************************************persname--><!-- 7 apr 93: LB : Revisions for printability:                    --><!--       changed xref target; part attribs                       --><!-- From: Dan Greenstein < digger@uk.ac.glasgow.udcf >            --><!-- Date: Wed, 1 Jul 92 15:21:04 BST                              --><!-- I need help with the content model here. The problem is that  --><!-- all the sub-elements can appear in any combination any order  --><!-- or the element can simply contain #PCDATA                     --><tagDoc id="PERSNAME" usage="opt"><gi tei="yes">persName</gi><name>personal name</name><desc>contains a proper noun or proper-noun phrase referring to
a person, possibly including any or all of the person's forename,
surname, honorific, added names, etc.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>describes the personal name more fully using an open-ended
list  of words or phrases which help to indicate the function, e.g.
<q>married name</q>, <q>maiden name</q>,
<q>pen name</q>, <q>religious name</q>, etc.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<persName>
   <foreName>Edward</foreName>
   <foreName>George</foreName>
   <surname type=linked>Bulwer-Lytton</surname>,
   <roleName>Baron Lytton of
     <placeName>Knebworth</placeName>
   </roleName>
</persName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="DEMOG NAMES DATA"/><elemDecl>- - (%m.personPart; | %m.phrase; | #PCDATA)*</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF persname.tag ??><!-- persName element --><?tei:SOF person.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	person.tag,v $
# Revision 1.4  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.3  1994/02/12  10:44:54  lou
    * JLs comments of 4 feb
    * 
    * Revision 1.2  1994/01/30  15:04:04  lou
    * renamed version of participant.tag
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 3 Jan 97 : LB : changed ID to match filename for consistency --><!-- 30 jan 94: LB : renamed to person (replacing earlier    --><!-- person.tag wh is now name or persname --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *************************************************************** partic --><tagDoc id="PERSON" usage="opt"><gi tei="yes">person</gi><desc>describes a single participant in a language interaction. </desc><attList><attDef usage="opt"><attName>role</attName><desc>specifies the role of this participant in the group.</desc><datatype>CDATA</datatype><valDesc>a set of keywords to be defined</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>sex</attName><desc>specifies the sex of the participant.</desc><datatype>(m | f | u )</datatype><valList type="open"><val>m</val><desc>male</desc><val>f</val><desc>female</desc><val>u</val><desc>unknown or inapplicable</desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>age</attName><desc>specifies the age group to which the participant belongs.</desc><datatype>CDATA</datatype><valDesc>suggested values are to be supplied</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<person id=P1 sex=F age=42>
  <p>Female informant, well-educated, born in Shropshire
   UK, 12 Jan 1950, of unknown occupation.
   Speaks French fluently. Socio-Economic status B2.
</person>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc>May contain a prose description organized as paragraphs, or
any sequence of demographic elements in any combination.</dataDesc><elemDecl>- o (p+ | (%m.demographic)* )</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF person.tag ??><!-- person element --><?tei:SOF persgrp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: persgrp.tag,v $
    * Revision 1.4  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.3  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.2  1994/04/01  17:41:18  msmcq
    * Changes while checking DTD
    * 
    * Revision 1.1  1994/01/30  15:05:12  lou
    * Initial revision
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 3 jan 97 : LB  : changed id (was partigrp) for consistency --><!-- 94-03-31 : MSM : for m.demog, read m.demographic         --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *********************************************** partigrp --><tagDoc id="PERSGRP" usage="opt"><gi tei="yes">personGrp</gi><name>personal group</name><desc>describes a group of individuals treated as a single person for
analytic purposes.</desc><attList><attDef usage="opt"><attName>role</attName><desc>specifies the role of this group of participants in the
        interaction.</desc><datatype>CDATA</datatype><valDesc>a set of keywords to be defined</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>sex</attName><desc>specifies the sex of the participant group.</desc><datatype>(m | f | u | x)</datatype><valList type="open"><val>m</val><desc>male</desc><val>f</val><desc>female</desc><val>u</val><desc>unknown</desc><val>x</val><desc>mixed</desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>age</attName><desc>specifies the age group of the participants.</desc><datatype>CDATA</datatype><valDesc>suggested values are to be supplied</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>size</attName><desc>specifies the size or approximate size of the group.</desc><datatype>CDATA</datatype><valDesc>may contain a number and an indication of accuracy,
      e.g. 'approx 200'</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <personGrp role=audience sex=x size='approx 50' id=PG1></personGrp>]]></eg></exemplum><remarks><p>The global <att tei="yes">id</att> attribute should be used to
identify each speaking participant in a spoken text if the
<att tei="yes">who</att> attribute is specified on individual utterances.</p></remarks><part type="aux" name="corpora"/><classes/><dataDesc>May contain a prose description organized as paragraphs, or
any sequence of demographic elements in any combination.</dataDesc><elemDecl>- o (p+ | (%m.demographic)* )</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF persgrp.tag ??><!-- personGrp element --><?tei:SOF phr.tag ??><!-- **************************************************** phr --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	phr.tag,v $
# Revision 1.2  94/02/27  15:55:52  lou
# Revisions for publication of AI
# 
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 93-09-22 : MSM : change id of seg class to clseg         --><!-- 93-07-22 : DTL : use as model for SEG, CL and PHR tags   --><!--                add sample values for type= and function= --><!-- 29 may 93: LB created C tag from old S tag               --><!--                                                          --><!-- **************************************************** phr --><tagDoc id="PHR" usage="opt"><gi tei="yes">phr</gi><name>phrase</name><desc>represents a grammatical phrase.</desc><attList></attList><exemplum><eg><![CDATA[<phr type=verb function='extraposted modifier'>To talk
  <phr type=preposition function=complement>of
    <phr type=noun function=object>many things</phr>
  </phr>
</phr>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLSEG"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq)</elemDecl><xref target="AILC"/></tagDoc><?tei:EOF phr.tag ??><!-- phr element --><?tei:SOF placname.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	placname.tag,v $
# Revision 1.5  94/10/20  14:21:38  lou
# Move from class placpart to class data (post-P3 fix)
# 
# Revision 1.4  1994/04/01  17:41:18  msmcq
# Changes while checking DTD
#
# Revision 1.3  1994/03/15  11:10:39  lou
# minor typos etc
#
# Revision 1.2  1994/03/07  16:14:32  lou
# revisions fpor publicn of ND
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : placePart is name of class              --><!-- 94-03-31 : MSM : correct case error in model             --><!-- 93-06-02 : MSM : fix valdescs                            --><!-- 93-04-13 : MSM : fix ]]> problems                        --><!-- ********************************************************placname --><!-- I need some help here with the content model, I think --><!-- Some tidying up done but I think it still needs help! (LB) --><tagDoc id="PLACNAME" usage="opt"><gi tei="yes">placeName</gi><name>place name</name><desc>contains an absolute or relative place name. </desc><attList></attList><exemplum><eg><![CDATA[<placeName>
  <settle>Rochester</settle>
  <region>New York</region>
</placeName>
 
<placeName>
  <geogName>Arrochar Alps</geogName>
  <region>Argylshire</region>
</placeName>
 
<placeName>
  <distance>10 miles</distance>
  <offSet>Northeast of</offSet>
  <settle>Attica</settle>
</placeName>
 ]]></eg></exemplum><remarks></remarks><part type="aux" name="ND"/><classes names="NAMES DATA"/><elemDecl>- - ((%m.placePart; | %m.phrase; | #PCDATA)+)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF placname.tag ??><!-- placeName element --><?tei:SOF plus.tag ??><!-- ************************************************************ --><!-- TAGDOC for PLUS                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	plus.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class binary                     --><!-- 93-09-22 : MSM : extract from bulk revision file         --><!-- ************************************************************ --><tagDoc id="PLUS" usage="rwa"><gi tei="yes">plus</gi><name>Binary plus value</name><desc>provides binary plus value for a feature.</desc><attList></attList><exemplum><eg><![CDATA[<f name=strident><plus></f>]]></eg></exemplum><part type="top" name="fs"/><classes names="BINARY"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSBI" type="div3"/></tagDoc><?tei:EOF plus.tag ??><!-- plus --><?tei:SOF pos.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to graminfo class                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pos.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** pos --><tagDoc id="POS" usage="opt"><gi tei="yes">pos</gi><name>part of speech</name><desc>indicates the part of speech assigned to a dictionary headword
(noun, verb, adjective, etc.)</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DIPARTS GRAMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPGR"/></tagDoc><?tei:EOF pos.tag ??><!-- pos element --><?tei:SOF postbox.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	postbox.tag,v $
# Revision 1.2  94/01/04  12:14:58  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-11-09 : MSM : set xref to CObi                        --><!-- *****************************************************postBox --><tagDoc id="POSTBOX" usage="opt"><gi tei="yes">postBox</gi><name>postBox</name><desc>contains a number or other identifier for some postal delivery
point other than a street address. </desc><attList></attList><exemplum><eg><![CDATA[        <postBox>P.O. Box 280]]></eg></exemplum><exemplum><eg><![CDATA[        <postBox>Postbus 532]]></eg></exemplum><remarks><p>The position and nature of postal codes is highly
country-specific; the conventions appropriate to the country concerned should
be used.</p></remarks><part type="base" name="core"/><classes names="ADDRPART"/><elemDecl>- o (#PCDATA)</elemDecl><xref target="CONAAD"/></tagDoc><?tei:EOF postbox.tag ??><!-- postBox element --><?tei:SOF postcode.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	postcode.tag,v $
# Revision 1.2  94/01/04  12:14:59  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************************postCode --><tagDoc id="POSTCODE" usage="opt"><gi tei="yes">postCode</gi><name>postCode</name><desc>contains a numerical or alphanumeric code used as part of a
postal address to simplify sorting or delivery of mail. </desc><attList></attList><exemplum><eg><![CDATA[        <postCode>HR1 3LR]]></eg></exemplum><exemplum><eg><![CDATA[        <postCode>60142-7]]></eg></exemplum><remarks><p>The position and nature of postal codes is highly
country-specific; the conventions appropriate to the country concerned should
be used.</p></remarks><part type="base" name="core"/><classes names="ADDRPART"/><elemDecl>- o (#PCDATA)</elemDecl><xref target="CONAAD"/></tagDoc><?tei:EOF postcode.tag ??><!-- postCode element --><?tei:SOF pref.tag ??><!-- Revisions:                                               --><!-- 94-01-13 : MSM : remove from diparts to avoid ambiguity  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pref.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** pRef --><tagDoc id="PREF" usage="opt"><gi tei="yes">pRef</gi><name>pronunciation reference</name><desc>in a dictionary example, indicates a reference to the
pronunciation(s) of the headword.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="FORMPTRS DIGLOBAL"/><dataDesc>Empty element.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="DIHW"/></tagDoc><?tei:EOF pref.tag ??><!-- pRef element --><?tei:SOF prepness.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	prepness.tag,v $
# Revision 1.2  94/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-04-06 : MSM : suppress remarks elements as needed     --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- *********************************************** prepness --><tagDoc id="PREPNESS" usage="opt"><gi tei="yes">preparedness</gi><desc>describes the extent to which a text may be regarded as
prepared or spontaneous. </desc><attList><attDef usage="opt"><attName>type
   </attName><desc>a keyword characterizing the type of preparedness.
   </desc><datatype>CDATA
   </datatype><valList type="open"><val>none</val><desc>spontaneous or unprepared
        </desc><val>scripted</val><desc>follows a script
        </desc><val>formulaic</val><desc>follows a predefined set of conventions
        </desc><val>revised</val><desc>polished or revised before presentation
   </desc></valList><default>#IMPLIED
 </default></attDef></attList><exemplum><eg><![CDATA[  <preparedness type='none'>]]></eg></exemplum><!-- <remarks><p>Difficulty in forming a consensus here       --><!-- means that I have allowed only a single attribute:       --><!-- possibly a degree attribute should be added              --><!-- (LB)</remarks>                                           --><part type="aux" name="corpora"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF prepness.tag ??><!-- preparedness element --><?tei:SOF principl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	principl.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- 92-08-19 : MSM : correct msc problem                     --><!-- ***********************************************principal --><tagDoc id="PRINCIPL" usage="mwa"><gi tei="yes">principal</gi><name>principal researcher</name><desc>supplies the name of the principal researcher responsible for the
creation of an electronic text.</desc><attList></attList><exemplum><eg><![CDATA[  <principal>Gary Taylor]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="HD21"/></tagDoc><?tei:EOF principl.tag ??><!-- principal element --><?tei:SOF profdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	profdesc.tag,v $
# Revision 1.4  94/02/11  16:55:41  msmcq
# allow handList element
# 
# Revision 1.3  1994/01/04  12:15:00  lou
# fix xrefs
#
# Revision 1.2  1993/09/15  17:30:41  lou
# added creation to content model
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-02-04 : MSM : allow handList element                  --><!-- 93-06-01 : MSM : rename lang.usage                       --><!-- 93-06-01 : MSM : allow declarable elements to repeat     --><!-- 93-03-11 : MSM : rename text.class textClass             --><!-- 92-08-19 : MSM : modify full name                        --><!-- 92-08-19 : MSM : correct msc problem                     --><!-- *********************************************profileDesc --><tagDoc id="PROFDESC" usage="rec"><gi tei="yes">profileDesc</gi><name>text-profile description</name><desc>provides a detailed description of non-bibliographic aspects of a
text, specifically the languages and sublanguages used, the situation in
which it was produced, the participants and their setting.</desc><attList></attList><exemplum><eg><![CDATA[<profileDesc>
  <langUsage><language wsd=FR>French
  <textDesc n=novel>
    <channel mode=w>print; part issues
    <constitution type=single>
    <derivation type=original>
    <domain type=art><factuality type=fiction>
    <interaction type=none>
    <preparedness type=prepared>
    <purposes><purpose type=entertain degree=high>
              <purpose type=inform degree=medium>
    </purposes>
  </textDesc>
  <settingDesc>
    <setting><place>Paris, France
             <time>Late 19th century
    </setting>
  </settingDesc>
</profileDesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- -  (creation?, langUsage*, textDesc*,
particDesc*, settingDesc*, handList*, textClass*)</elemDecl><xref target="HD4"/><xref target="HD11"/></tagDoc><?tei:EOF profdesc.tag ??><!-- profileDesc element --><?tei:SOF projdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	projdesc.tag,v $
# Revision 1.2  94/01/04  12:15:01  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-08-19 : MSM : correct msc problem                     --><!-- *********************************************projectDesc --><tagDoc id="PROJDESC" usage="opt"><gi tei="yes">projectDesc</gi><name>project description</name><desc>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.</desc><attList></attList><exemplum><eg><![CDATA[ <projectDesc><p>Texts collected for use in the Claremont Shakespeare
    Clinic, June 1990</projectDesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD51"/><xref target="HD5"/><xref target="CCAS2"/></tagDoc><?tei:EOF projdesc.tag ??><!-- projectDesc element --><?tei:SOF prologue.tag ??><!-- Prologue.tag                                             --><!-- Revisions:                                               --><!-- 93-08-18 : MSM : correct m.component to component        --><!-- 93-08-16 : MSM : put comment marks around ellipsis in example --><!-- 1993-08-07 : MSM : loosen content model a lot            --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	prologue.tag,v $
# Revision 1.6  94/01/04  12:15:01  lou
# fix xrefs
# 
# Revision 1.5  1993/08/23  16:35:10  msmcq
# correct content models for publication of DR
#
# Revision 1.3  1993/08/13  20:50:04  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:31:15  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ****************************************************** prologue --><tagDoc id="PROLOGUE" usage="mwa"><gi tei="yes">prologue</gi><desc>contains the prologue to a drama,  typically spoken by an actor out of
character, possibly in association with a particular performance or venue.</desc><attList></attList><exemplum><eg><![CDATA[<prologue>
<sp>
<l>Wits, like physicians never can agree,
<l>When of a different society.
<!-- ... -->
<l>New plays are stuffed with wits, and with deboches,
<l>That crowd and sweat like cits in May-Day coaches.
</sp>
<trailer>
Written by a person of quality
</trailer>
</prologue>]]></eg><!-- A. Behn: The Rover (1697) --></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes names="DRFRONT"/><dataDesc></dataDesc><elemDecl>- - ((%m.divtop)*, (%component)+, (%m.divbot)*)</elemDecl><!-- was  - - (%divtop, sp, %divbot ) --><xref target="DRPRO" type="div3"/><xref target="DRFAB" type="div3"/></tagDoc><?tei:EOF prologue.tag ??><!-- prologue element --><?tei:SOF pron.tag ??><!-- Revisions:                                               --><!-- 94-03-21 : MSM : supply explicit end-tags for attdef components --><!-- 4 mar 94: at stiug's suggn, made vallist same as that for orth
--><!-- 94-01-15 : MSM : allow end-tag omission                  --><!-- 94-01-15 : MSM : add full stops to all desc elements     --><!-- 94-01-14 : MSM : move pos out of form in example         --><!-- 94-01-14 : MSM : correct example (suppres GRAM element)  --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to forminfo class                   --><!-- 94-01-12 : MSM : suppress dleaves class                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pron.tag,v $
# Revision 1.4  94/03/25  17:21:51  msmcq
# cleanup of miscellaneous tagdocs:  some typos,
# some INHERITED errors, supplied explicit end-tags for many attdef parts
# to shield a weakness of oddref1 (now fixed)
# 
# Revision 1.3  1994/03/07  16:13:40  lou
# typos noted by DTB
#
# Revision 1.2  1994/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************* pron   --><tagDoc id="PRON" usage="rec"><gi tei="yes">pron</gi><name>pronunciation</name><desc>contains the pronunciation(s) of the word.</desc><attList><attDef usage="opt"><attName>extent</attName><desc>indicates whether the pronunciation is for whole word or part.
    </desc><datatype>CDATA</datatype><valList type="open"><val>full </val><desc>full form</desc><val>pref </val><desc>prefix</desc><val>suff </val><desc>suffix</desc><val>part </val><desc>partial</desc></valList><default>full</default><!--    <valList type=closed>
        <val>whole      <desc>the pronunciation is for the entire word.
        <val>prefix     <desc>the pronunciation is for a prefix only.
        <val>suffix     <desc>the pronunciation is for a suffix only.
    </valList>
    <default>whole</default>
--><eg></eg><remarks><p><!-- [Merge this and similar attributes into a class <term>partials</term>? -Ed.] --></p></remarks></attDef><attDef usage="rwa"><attName>notation</attName><desc>indicates what notation is used for the pronunciation, if more
than one occurs in the machine-readable dictionary.
    </desc><datatype>CDATA</datatype><valDesc>Sample values:  IPA, Murray, ...
    </valDesc><default>#IMPLIED</default><eg></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[<entry>
    <form>
         <orth>obverse</orth>
         <pron>&ACCENT;&auml;b-&accent;v&schwa;rs</pron>,
         <pron extent=prefix>&auml;b-&ACCENT;</pron>,
         <pron extent=prefix>&schwa;b-&ACCENT;</pron>
    </form>
    <gramGrp><pos>n</pos></gramGrp>
    <!-- ... -->
</entry>]]>
(From:  <citation>Webster's Collegiate</citation>, obverse 2)</eg></exemplum><part type="base" name="dict"/><classes names="DIPARTS FORMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent)</elemDecl><xref target="DITPFO" type="div2"/></tagDoc><?tei:EOF pron.tag ??><!-- pron element --><?tei:SOF ptr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ptr.tag,v $
# Revision 1.4  94/02/12  10:46:46  lou
# revisions for P3
# 
# Revision 1.2  1993/09/17  16:21:39  msmcq
# add to termincl class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : include in class termincl               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- 1 jun 93: modified desc --><!-- 93-02-11 : MSM : loc class has id clloc, not loc         --><!-- 93-01-26 : MSM : add to pointer class                    --><!-- 92-12-07 : MSM : remove common attributes to loc         --><!-- 92-12-07 : MSM : change values for evaluate              --><!-- 92-12-07 : MSM : clean up some attributes, more to go    --><!-- 92-11-09 : MSM : specify value desc for creator, date    --><!-- 92-11-09 : MSM : cosmetic and WGML changes               --><!-- ********************************************************* ptr --><tagDoc id="PTR" usage="opt"><gi tei="yes">ptr</gi><desc>defines a pointer to another location in the current document
in terms of one or more identifiable elements.</desc><attList><attDef usage="req"><attName>target</attName><desc>specifies the destination of the pointer as one or more
    SGML identifiers</desc><datatype>IDREFS </datatype><valDesc>Each value specified must be the same as that specified as
    value for an <att tei="yes">ID</att> attribute for some other element in the
    current SGML document.</valDesc><default>#REQUIRED</default></attDef></attList><exemplum><eg><![CDATA[<ptr target="P2 P5" resp=LB type=s>
<ptr target='D1' type='defn'>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="CLLOC POINTER TERMINCL"/><elemDecl>- O EMPTY</elemDecl><xref target="COXR"/><xref target="SAPT"/></tagDoc><?tei:EOF ptr.tag ??><!-- ptr element --><?tei:SOF pubstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pubstmt.tag,v $
# Revision 1.4  94/01/04  12:15:04  lou
# fix xrefs
# 
# Revision 1.3  1993/09/22  19:17:10  msmcq
# change model to allow place, pub as well as pub, place
#
# Revision 1.2  1993/08/03  02:11:25  msmcq
# rename place as pubPlace
# --><!-- Revisions:                                               --><!-- 93-09-16 : MSM : allow ISBD order of contents            --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : rename place as pubPlace                --><!-- 92-08-19 : MSM : correct msc problem                     --><!-- *****************************************publicationStmt --><tagDoc id="PUBSTMT" usage="req"><gi tei="yes">publicationStmt</gi><name>publication statement</name><desc>groups information concerning the publication or distribution
of an electronic or other text. </desc><attList></attList><exemplum><eg><![CDATA[<publicationStmt>
<publisher>C. Muquardt <pubPlace>Bruxelles & Leipzig
<date>1846]]></eg></exemplum><exemplum><eg><![CDATA[<publicationStmt>
<publisher>Chadwyck Healey
<pubPlace>Cambridge
<availability>Available under licence only
<date>1992]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o
(p+ | ( (publisher | distributor | authority) &amp; 
        (pubPlace?, address?, idno*, availability?, date?)+ )+ )</elemDecl><xref target="HD24"/><xref target="HD2"/></tagDoc><?tei:EOF pubstmt.tag ??><!-- publicationStmt element --><?tei:SOF publishr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	publishr.tag,v $
# Revision 1.2  94/01/04  12:15:03  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-11-09 : MSM : set xref to CObi                        --><!-- 92-08-19 : MSM : change xref to HD/22                    --><!-- *************************************************** publisher --><tagDoc id="PUBLISHR" usage="opt"><gi tei="yes">publisher</gi><desc>provides the name of the organization responsible for
the publication or distribution of a bibliographic item.</desc><attList></attList><exemplum><eg><![CDATA[<imprint><pubPlace>Oxford</pubPlace>
        <publisher>Clarendon Press</publisher>
        <date>1987</date>
</imprint>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc>Use the full form  of the name by which a company is usually
referred to, rather than any abbreviation of it which may appear on a
title page</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="COBICOI"/><xref target="HD24"/></tagDoc><!-- end of PUBLISHER --><?tei:EOF publishr.tag ??><!-- publisher element --><?tei:SOF pubplace.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pubplace.tag,v $
# Revision 1.3  94/01/04  12:15:03  lou
# fix xrefs
# 
# Revision 1.2  1993/09/16  16:13:47  msmcq
# Remove from class DATA
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagDoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-13 : MSM : move out of data class                  --><!-- 93-06-21 : MSM : remove demogs class                     --><!-- 93-06-21 : MSM : make pubplace tagDoc from old place tagDoc --><!-- 93-03-08 : MSM : add classes demog, names (!)            --><!-- 92-12-09 : MSM : move key, reg to names class            --><!-- ******************************************************* place --><tagDoc id="PUBPLACE" usage="opt"><gi tei="yes">pubPlace</gi><desc>contains the name of the place where a bibliographic item was
published.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="top" name="core"/><classes names="NAMES BIBLPART"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="COBICOI" type="div2"/></tagDoc><?tei:EOF pubplace.tag ??><!-- pubPlace element --><?tei:SOF purpose.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	purpose.tag,v $
# Revision 1.3  94/03/15  11:10:40  lou
# minor typos etc
# 
# Revision 1.2  1994/03/01  17:19:10  lou
# fix typo noted by Terry
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 14 mar: LB: remove ^Z --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************** purpose --><tagDoc id="PURPOSE" usage="opt"><gi tei="yes">purpose</gi><desc>characterizes a single purpose or communicative function of the
text.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>specifies a particular kind of purpose.
   </desc><datatype>CDATA
   </datatype><valList type="semi"><val>persuade</val><desc>didactic, advertising, propaganda, etc.
  </desc><val>express</val><desc>self expression, confessional, etc.
  </desc><val>inform</val><desc>convey information, educate, etc.
  </desc><val>entertain</val><desc>amuse, entertain, etc.
   </desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>degree
   </attName><desc>specifies the extent to which this purpose predominates.
   </desc><datatype>(high | medium | low | unknown)
   </datatype><valList type="closed"><val>high</val><desc>this purpose is predominant
  </desc><val>medium</val><desc>this purpose is intermediate
  </desc><val>low</val><desc>this purpose is weak
  </desc><val>unknown</val><desc>extent unknown
   </desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <purpose type=persuade degree=high>
  <purpose type=entertain degree=low>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc>Usually empty, unless some further clarification of the type
attribute is needed, in which case it may contain running prose</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF purpose.tag ??><!-- purpose element --><?tei:SOF pvar.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-13 : MSM : remove from diparts to avoid ambiguity  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	pvar.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** pVar --><tagDoc id="PVAR" usage="opt"><gi tei="yes">pVar</gi><name>pronunciation-variant reference</name><desc>in a dictionary example, indicates a reference to variant
pronunciation(s) of the headword.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="FORMPTRS DIGLOBAL"/><dataDesc>Character data or phrase-level elements.</dataDesc><elemDecl>- -  (#PCDATA | pRef)*</elemDecl><xref target="DI"/></tagDoc><?tei:EOF pvar.tag ??><!-- pvar element --><?tei:SOF q.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	q.tag,v $
# Revision 1.5  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.4  1994/01/15  21:16:35  msmcq
    * revisions in connection with di, for p3; see comments for details
    * 
    * Revision 1.3  1994/01/04  12:15:05  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/08/19  00:50:18  msmcq
    * change content model to specialPara
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : made vallist for direct type=closed      --><!-- 94-01-15 : MSM : recast desc                             --><!-- 93-02-11 : MSM : add full stops at end of DESCs          --><!-- 92-12-09 : MSM : normaliZe spelling                      --><!-- 92-12-06 : MSM : suppressed FREE attribute               --><!-- 92-12-06 : MSM : remove token conflicts in direct, free  --><!-- *********************************************************** q --><tagDoc id="Q" usage="opt"><gi tei="yes">q</gi><name>quoted speech or thought</name><desc>contains a quotation or apparent quotation --- a representation of
speech or thought marked as being quoted from someone else (whether in
fact quoted or not); in narrative, the words are usually those of of a
character or speaker; in dictionaries, <gi tei="yes">q</gi> may be used to mark
real or contrived examples of usage.</desc><attList><attDef usage="rwa"><attName>type</attName><desc>may be used to indicate whether the quoted matter is spoken
or thought, or to characterize it more finely.</desc><datatype>CDATA</datatype><valList type="open"><val>spoken</val><desc>representation of direct speech, usually
marked by quotation marks.</desc><val>thought</val><desc>representation of thought, e.g. internal monologue.</desc></valList><default>#IMPLIED</default></attDef><attDef usage="rwa"><attName>direct</attName><desc>may be used to indicate whether the quoted matter is regarded
as direct or indirect speech.</desc><datatype>(y | n | unspecified)</datatype><valList type="closed"><val>y</val><desc>speech or thought is represented directly.</desc><val>n</val><desc>speech or thought is represented indirectly,
e.g. by use of a marked verbal aspect.</desc><val>unspecified</val><desc>no claim is made.</desc></valList><default>unspecified</default></attDef><attDef usage="rwa"><attName>who</attName><desc>identifies the speaker of a piece of direct speech.</desc><datatype>CDATA</datatype><valDesc>may be an idref</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[And so, as Tiny Tim observed,
<q type=speech>God Bless Us, Every One!</q>]]></eg><!-- C Dickens, Xmas Carol, p 166 --></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQINTER"/><elemDecl>- - (%specialPara)</elemDecl><xref target="COHQQ"/></tagDoc><?tei:EOF q.tag ??><!-- q element --><?tei:SOF quotn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	quotn.tag,v $
# Revision 1.2  94/01/04  12:15:06  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-01 : MSM : minor change to wording of FORM att     --><!-- 92-08-19 : MSM : delete empty name element               --><!-- 92-08-19 : MSM : fix msc problem                         --><!-- ***********************************************quotation --><tagDoc id="QUOTN" usage="opt"><gi tei="yes">quotation</gi><desc>specifies editorial practice adopted with respect to quotation
marks in the original. </desc><attList><attDef usage="opt"><attName>marks
   </attName><desc>indicates whether or not quotation marks have been retained as
       content within the text.
   </desc><datatype>(none | some | all)
   </datatype><valList type="open"><val>none</val><desc>no quotation marks have been retained
  </desc><val>some</val><desc>some quotation marks have been retained
  </desc><val>all</val><desc>all quotation marks have been retained
   </desc></valList><default>all</default></attDef><attDef usage="opt"><attName>form
   </attName><desc>specifies how quotation marks are indicated within the text.
   </desc><datatype>(data | rend | std | nonstd | unknown)
   </datatype><valList type="open"><val>data    </val><desc>quotation marks are retained as data.
      </desc><val>rend    </val><desc>the <att tei="yes">rendition</att> attribute is
                         consistently used to indicate the form of
                         quotation marks.
      </desc><val>std     </val><desc>use of quotation marks has been standardized.
      </desc><val>nonstd  </val><desc>quotation marks are represented inconsistently.
      </desc><val>unknown </val><desc>use of quotation marks is unknown.
   </desc></valList><default>unknown</default></attDef></attList><exemplum><eg><![CDATA[  <quotation marks=none form=rend>
    <p>No quote marks have been retained. Instead, the rendition
    attribute on the Q element is used to specify what kinds of
    quote mark was used, according to the following list:
    <list type=gloss>
      <label>dq  <item>double quotes open and close
      <label>sq  <item>single quotes open and close
      <label>dash<item>long dash open
      <label>dg  <item>double guillemets open and close
    </list>
  </quotation>]]></eg></exemplum><exemplum><eg><![CDATA[  <quotation marks=all form=std>
  <p>All quotation marks are retained in the text and are
   represented by standard entity references
  </quotation>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/><xref target="CCAS2"/></tagDoc><?tei:EOF quotn.tag ??><!-- quotation element --><?tei:SOF quote.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	quote.tag,v $
# Revision 1.2  94/01/04  12:15:05  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************************* quote --><tagDoc id="QUOTE" usage="opt"><gi tei="yes">quote</gi><name>quotation</name><desc>contains a phrase or passage attributed by the narrator or
author to some agency external to the text. </desc><attList></attList><exemplum><eg><![CDATA[Lexicography has shown little sign of being affected by the
work of followers of J.R. Firth, probably best summarized
in his slogan, <quote>You shall know a word by the company it
keeps</quote><ref target=FI57>(Firth, 1957)</ref>]]></eg></exemplum><remarks><p>If a bibliographic citation is supplied for the source of a
quotation, the two may be grouped using the <gi tei="yes">cit</gi> element.</p></remarks><part type="base" name="core"/><classes names="HQINTER"/><elemDecl>- - (%specialPara;)</elemDecl><xref target="COHQQ"/><xref target="DSGRP"/></tagDoc><?tei:EOF quote.tag ??><!-- quote element --><?tei:SOF rate.tag ??><!-- ************************************************************ --><!-- TAGDOC for RATE                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	rate.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1994/01/04  01:17:21  msmcq
# revise DESC on values
# of REL
#
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 93-12-23 : MSM : change value, valueTo atts:  CDATA not NUMBER --><!-- 93-12-22 : MSM : change descriptions on REL att values   --><!-- 93-09-22 : MSM : extract from bulk file                  --><!-- ************************************************************ --><tagDoc id="RATE" usage="rwa"><gi tei="yes">rate</gi><name>rate value</name><desc>provides a rate value or range of values for a feature.</desc><attList><attDef id="RATEVAL" usage="req"><attName>value</attName><desc>provides a numeric value.</desc><datatype>CDATA</datatype><valDesc>A real number or integer.</valDesc><default>#REQUIRED</default></attDef><attDef id="RTVALTO" usage="opt"><attName>valueTo</attName><desc>together with <att tei="yes">value</att> attribute, provides a numeric range
of values.</desc><datatype>CDATA</datatype><valDesc>A real number or integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="RTUNIT" usage="rwa"><attName>unit</attName><desc>provides a unit for a rate feature, one of a finite list that
may be specified in a feature declaration.</desc><datatype>CDATA</datatype><valDesc>A string, e.g. <term>meter</term>.</valDesc><default>#IMPLIED</default></attDef><attDef id="RATEPER" usage="req"><attName>per</attName><desc>provides an interval for a rate feature, one of a finite list that
may be specified in a feature declaration.</desc><datatype>CDATA</datatype><valDesc>A string, e.g. <term>second</term>.</valDesc><default>#REQUIRED</default></attDef><attDef id="RATEREL" usage="req"><attName>rel</attName><desc>indicates the relation of the given value or range to the actual
value or range.</desc><datatype>(eq|ne|gt|ge|lt|le)</datatype><valList type="closed"><val>eq     </val><desc>indicates that the actual value or range is that
given.
   </desc><val>ne     </val><desc>indicates that the actual value or range is not the
value or range given by the element.
   </desc><val>lt     </val><desc>indicates that the actual value or range is less
than the given value or range.
   </desc><val>le     </val><desc>indicates that the actual value or range is less
than or equal to the given value or range.
   </desc><val>gt     </val><desc>indicates that the actual value or range is greater
than the given value or range.
   </desc><val>ge     </val><desc>indicates that the actual value or range is greater
than or equal to the given value or range.</desc></valList><default>eq</default></attDef><attDef id="RATETYPE" usage="opt"><attName>type</attName><desc>indicates whether value is to be understood as real or integer.</desc><datatype>(int|real)</datatype><valList type="closed"><val>int    </val><desc>specifies that value is an integer; if noninteger
is given as value of <att tei="yes">value</att>, then only integer part is used.
   </desc><val>real   </val><desc>specifies that value is that of a real number.</desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<rate rel=gt value=65 unit=mile per=hour>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Empty tag.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSSY" type="div3"/></tagDoc><?tei:EOF rate.tag ??><!-- rate           --><?tei:SOF rdg.tag ??><!-- Revisions:                                               --><!-- 94-02-03 : MSM : add fragmentary as inclusion            --><!-- 94-01-25 : MSM : paracontent not phrase.seq              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	rdg.tag,v $
# Revision 1.3  94/03/21  14:33:10  lou
# second major typo purge
# 
# Revision 1.2  1994/02/07  20:56:16  msmcq
# revsisions for P3
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY rdg      system 'rdg.tag' --><!-- rdg tag --><!-- **************************************************** rdg --><tagDoc id="RDG" usage="req"><gi tei="yes">rdg</gi><name>reading</name><desc>contains a single reading within a textual variation.</desc><attList></attList><exemplum><eg><![CDATA[<rdg wit='Ra2'>Eryment</rdg> ]]></eg></exemplum><remarks><p></p></remarks><part type="top" name="tc"/><classes names="READINGS"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent) +(%m.fragmentary)</elemDecl><xref target="TCAPLL"/></tagDoc><?tei:EOF rdg.tag ??><!-- rdg element --><?tei:SOF rdggrp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: rdggrp.tag,v $
    * Revision 1.5  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.4  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.3  1994/03/08  03:24:27  msmcq
    * revision for P3
    * 
    * Revision 1.2  1994/02/07  20:56:16  msmcq
    * revsisions for P3
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : change content model per MSM 1996-06-13 --><!-- 94-03-03 : MSM : change old wits to wit                  --><!-- 94-01-25 : MSM : clean gi                                --><!-- 94-01-25 : MSM : clean desc                              --><!-- 94-01-25 : MSM : clean model                             --><!-- ENTITY rdggrp   system 'rdggrp.tag' --><!-- rdgGrp tag --><!-- ************************************************ rdgGrp --><tagDoc id="RDGGRP" usage="opt"><gi tei="yes">rdgGrp</gi><name>reading group</name><desc>within a textual variation,
groups two or more readings perceived to have a genetic
relationship or other affinity.</desc><attList></attList><exemplum><eg><![CDATA[<app>
    <lem wit='El Ra2'>though</lem>
    <rdgGrp type=orthographic>
         <rdg wit='Hg'>thogh</rdg>
         <rdg wit='La'>thouhe</rdg>
    </rdgGrp>
</app>]]></eg></exemplum><remarks><p>Note that only one <gi tei="yes">lem</gi> element may appear within
a single apparatus entry, whether it appears outside a <gi tei="yes">rdgGrp</gi>
element or within it.</p></remarks><part type="top" name="tc"/><classes names="READINGS"/><dataDesc>May contain readings and nested reading groups.<!-- formerly  (rdgGrp | (rdg, wit?))+ --></dataDesc><elemDecl>- O (((rdgGrp, wit?) | ((lem, wit?)?, (rdg, wit?)*))+)</elemDecl><xref target="TCAPLL"/></tagDoc><?tei:EOF rdggrp.tag ??><!-- rdgGrp element --><?tei:SOF re.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	re.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1994/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add end-tag for exempla                 --><!-- 94-01-15 : MSM : allow end-tag omission                  --><!-- 94-01-14 : MSM : move punctuation into sense elems       --><!-- 94-01-14 : MSM : suppress archaic SN element             --><!-- 94-01-14 : MSM : move gramGrps out of form               --><!-- 94-01-14 : MSM : correct ref to emacr ent                --><!-- 94-01-14 : MSM : restore ORIG= in examples               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : change model:  m.phrase, pcdata, not paraContent --><!-- 94-01-12 : MSM : suppress pform elements in exx          --><!-- 94-01-12 : MSM : clean examples                          --><!-- 93-04-12 : MSM : suppress non-std bold, ital             --><!-- ***************************************************** re --><tagDoc id="RE" usage="opt"><gi tei="yes">re</gi><name>related entry</name><desc>contains a dictionary entry for a lexical item related to the
headword, such as a compound phrase or derived form, embedded inside a
larger entry.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the related entry according to any convenient typology.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><p>The following example from
<citation><title>Webster's New Collegiate Dictionary</title>
(Springfield, Mass.:  G. &amp; C. Merriam Company, 1975)</citation>
shows a single related entry for which no definition is given, since its
meaning is held to be readily derivable from the root entry.</p><eg><![CDATA[<entry>
<form>
   <orth>neu &middot; ral</orth>
   <pron>&STRESS;n(y)&udot;r-&schwa;l</pron>
   </form>
<gramGrp><pos>adj</pos></gramGrp>
<sense n='1'><def>of, relating to, or affecting a nerve or the
        nervous system</def></sense>
<sense n='2'> ... </sense>
<re>
<form>
   <orth>neurally</orth>
   <pron extent=suffix>-&schwa;-l&emacr;</pron>
   </form>
<gramGrp><pos>adv</pos></gramGrp>
</re>
</entry>
 ]]></eg></exemplum><exemplum><p>The following example from <citation><title>Diccionario
de la Universidad de Chicago Ingl&eacute;s-Espa&ntilde;ol y
Espa&ntilde;ol-Ingl&eacute;s</title> / <title>The University of Chicago
Spanish Dictionary</title>, Fourth Edition, compiled by Carlos Castillo
and Otto F. Bond (Chicago:  University of Chicago Press,
1987)</citation> shows a number of related entries embedded in the main
entry.  The original entry resembles the following:
<q rend="display"><hilited rend="bold">abeja</hilited>
[a &amp;middot; &amp;bslash;&eacute; &amp;middot; xa]
<hilited rend="ital">f.</hilited> bee;
<hilited rend="bold">abejera</hilited>
[a &amp;middot; &amp;bslash;e &amp;middot; x&eacute; &amp;middot; ra]
<hilited rend="ital">f.</hilited> beehive;
<hilited rend="bold">abej&oacute;n</hilited>
[a &amp;middot; &amp;bslash;e &amp;middot; x&oacute;on]
<hilited rend="ital">m.</hilited> drone; bumblebee;
<hilited rend="bold">abejorro</hilited>
[a &amp;middot; &amp;bslash;e &amp;middot; x&oacute; &amp;middot; rro]
<hilited rend="ital">m.</hilited> bumble bee.</q>
One encoding for this entry would be:</p><eg><![CDATA[<entry>
  <form> <orth> abeja </orth>
      <pron> [a &middot; &bslash;&eacute; &middot; xa] </pron>
      </form>
  <gramGrp> <pos> f. </pos> </gramGrp>
  <sense> <def> bee </def>; </sense>
<re>
  <form> <orth> abejera </orth>
      <pron> [a &middot; &bslash;e &middot; x&eacute; &middot; ra] </pron>
      </form>
  <gramGrp> <pos> f. </pos> </gramGrp>
  <sense> <def> beehive </def>; </sense> </re>
<re>
  <form> <orth> abej&oacute;n </orth>
      <pron> [a &middot; &bslash;e &middot; x&oacute;n] </pron>
      </form>
  <gramGrp> <pos> m. </pos> </gramGrp>
  <sense> <def> drone </def>; </sense>
  <sense> <def> bumblebee </def>; </sense> </re>
<re>
  <form> <orth> abejorro </orth>
      <pron> [a &middot; &bslash;e &middot; x&oacute; &middot; rro] </pron>
      </form>
  <gramGrp> <pos> m. </pos> </gramGrp>
  <sense> <def> bumble bee </def>. </sense> </re>
</entry>]]></eg></exemplum><exemplum><p>In the much larger Simon &amp; Schuster Spanish-English dictionary,<note source="auth" place="display" anchored="Y"><citation>Tana de G&aacute;mez, ed., <title>Simon and Schuster's
International Dictionary</title> (New York:  Simon and Schuster, 1973).</citation></note>
these derived forms of <cited>abeja</cited> are treated as separate
main entries, but there are other embedded phrases shown as
<gi tei="yes">re</gi>s in its main entry for <cited>abeja</cited>:
<q rend="display">abeja, f. 1. (ento.) bee. 2. busy bee, hard
worker. 3. (astron.) A., Musca. -- a. albanila,
mason bee; a. carpintera, carpenter bee;
a. reina or maestra, queen
bee; a. neutra or obrera, worker bee.</q>
This entry may be encoded thus:</p><eg><![CDATA[<entry>
<form> <orth> abeja </orth> <gramGrp><gen> f. </gen></gramGrp> </form>
<sense n='1.'>
        <usg type=domain> (ento.) </usg>
        <def> bee </def>.
        </sense>
<sense n='2.'>
        <def> busy bee, hard worker </def>.
        </sense>
<sense n='3.'>
        <usg type=domain orig='A.'> (astron.) </usg>,
        <def> Musca </def> ---
        </sense>
<re>
<form>  <orth orig='a. albanila'> abeja albanila </orth>,
        </form>
<sense><def> mason bee </def>; </sense>
</re>
<re>
<form>  <orth orig='a. carpintera'>  abeja carpintera </orth>,
        </form>
<sense> <def> carpenter bee </def>; </sense>
</re>
<re>
<form>  <orth id=O1 orig='a. reina or maestra'> abeja reina </orth>
        <orth mergedin=O1> abeja maestra </orth>
        </form>
<sense> <def> queen bee </def>; </sense>
</re>
<re>
<form>  <orth id=O2 orig='a. neutra or obrera'> abeja neutra </orth>
        <orth mergedin=O2> abeja obrera </orth>
        </form>
<sense> <def> worker bee </def> . </sense>
</re>
</entry>]]></eg></exemplum><remarks><p>Identical in sub-elements to an <gi tei="yes">entry</gi> tag, and used where
a dictionary has embedded information inside one entry which could have
formed a separate entry.
Some authorities distinguish related entries, run-on entries,
and various other types of degenerate entries; no such typology is
attempted here.</p></remarks><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS DIGLOBAL"/><dataDesc>May contain character data mixed with any other elements
defined in the dictionary tag set.</dataDesc><elemDecl>- O  (sense | %m.dictionaryTopLevel | %m.phrase | #PCDATA)*
-(re)</elemDecl><xref target="DITPRE" type="div2"/></tagDoc><?tei:EOF re.tag ??><!-- re element --><?tei:SOF recordin.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	recordin.tag,v $
# Revision 1.3  94/01/04  12:15:07  lou
# fix xrefs
# 
# Revision 1.2  1993/09/09  19:43:44  msmcq
# change citn to bibl
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : change citn to bibl, etc.               --><!-- 92-08-19 : MSM : fix msc problem                         --><!-- ***********************************************recording --><tagDoc id="RECORDIN" usage="opt"><gi tei="yes">recording</gi><name>recording event</name><desc>details of an audio or video recording event
used as the source of a spoken text, either directly or from
a public broadcast. </desc><attList><attDef usage="opt"><attName>type</attName><desc>the kind of recording.</desc><datatype>(audio | video)
   </datatype><valList type="closed"><val>audio</val><desc>audio recording
            </desc><val>video</val><desc>audio and video recording
   </desc></valList><default>audio</default></attDef><attDef usage="opt"><attName>dur</attName><desc>the original duration of the recording. </desc><datatype>CDATA
    </datatype><valDesc>Include the units, e.g. 30 mins.
    </valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <recording type=audio dur="30 mins">
  <equipment>Recorded on a Sony TR444 walkman by
           unknown participants; remastered to digital tape
     at <place>Borehamwood Studios</place> by
     <name>Transcription Services</name>]]></eg></exemplum><exemplum><eg><![CDATA[  <recording type=audio dur="10 mins">
    <equipment><p>Recorded from FM Radio to digital tape</>
    <broadcast>
     <bibl><title>Interview on foreign policy
              <author>BBC Radio 5
       <respStmt><resp>interviewer</><name>Robin Day</></>
       <respStmt><resp>interviewee</><name>Margaret Thatcher</></>
       <series><title>The World Tonight</></>
       <note>First broadcast on <date>27 Nov 1989</></>
   </bibl></broadcast> </recording>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- - (p+ | (respStmt | equipment | broadcast | date)*)</elemDecl><xref target="HD32"/><xref target="CCAS2"/></tagDoc><?tei:EOF recordin.tag ??><!-- recording element --><?tei:SOF recstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	recstmt.tag,v $
# Revision 1.2  94/01/04  12:15:07  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-08-19 : MSM : fix msc problem                         --><!-- *******************************************recordingStmt --><tagDoc id="RECSTMT" usage="rwa"><gi tei="yes">recordingStmt</gi><name>recording statement</name><desc>describes a set of recordings used in transcription of a
spoken text.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- - (p+ | recording+ )</elemDecl><xref target="HD32"/><xref target="HD3"/></tagDoc><?tei:EOF recstmt.tag ??><!-- recordingStmt element --><?tei:SOF ref.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	ref.tag,v $
# Revision 1.4  94/03/01  04:16:01  msmcq
# change content model to paracontent from phrase.seq
# 
# Revision 1.3  1994/01/04  12:15:08  lou
# fix xrefs
#
# Revision 1.2  1993/09/16  16:20:18  msmcq
# Add to terminologyInclusions class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-02-28 : MSM : allow to contain paraContent            --><!-- 94-02-28 : MSM : add (restore?) to clloc class           --><!-- 93-09-15 : MSM : include in class termincl               --><!-- 93-02-11 : MSM : loc class has id clloc, not loc         --><!-- 93-01-26 : MSM : move stag in second example             --><!-- 93-01-26 : MSM : add to pointer class                    --><!-- 92-12-07 : MSM : remove common attributes to loc         --><!-- 92-11-09 : MSM : specify value desc for creator, date    --><!-- 92-11-09 : MSM : cosmetic and WGML (]]>) changes         --><!-- ********************************************************* ref --><tagDoc id="REF" usage="opt"><gi tei="yes">ref</gi><desc>defines a reference to another location in the current document,
in terms of one or more identifiable elements, possibly modified by
additional text or comment.</desc><attList><attDef usage="opt"><attName>target</attName><desc>specifies the destination of the reference as one or more
    SGML identifiers</desc><datatype>IDREFS </datatype><valDesc>Each value specified must be the same as that specified as
    value for an <att tei="yes">ID</att> attribute for some other element in the
    current SGML document.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<ref target="P2 P5" resp=LB type=s>
   See especially the second sentence</ref>.
 
   See also <ref>s.v. <term>locution</term></ref>.]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="CLLOC POINTER TERMINCL"/><elemDecl>- - (%paraContent)</elemDecl><xref target="COXR"/><xref target="TETA"/></tagDoc><?tei:EOF ref.tag ??><!-- ref element --><?tei:SOF refsdecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	refsdecl.tag,v $
# Revision 1.3  94/03/25  16:02:11  msmcq
# make changes as per J. Lavagnino
# implementing new extended-pointer mechanism for canonical refs.
# 
# Revision 1.2  1994/01/04  12:15:09  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-24 : MSM : make changes as per JLav,               --><!-- 94-03-24 : MSM : putting Eynsham decisions into practice. --><!-- 92-08-19 : MSM : fix msc problem                         --><!-- ************************************************refsDecl --><tagDoc id="REFSDECL" usage="opt"><gi tei="yes">refsDecl</gi><name>references declaration</name><desc>specifies how canonical references are constructed for this text.</desc><attList><attDef usage="opt"><attName>doctype
   </attName><desc>identifies the <term>document type</term> within which this
   reference declaration is used.
   </desc><datatype>NAME
   </datatype><valDesc>must be the name of a document type</valDesc><default>TEI.2</default></attDef></attList><exemplum><eg><![CDATA[<refsDecl>
  <step gi=div1 att=n delim=":"
        from="DESCENDANT (1 DIV1 N %1) CHILD (1 HEAD) STRING %2"
        to  ="PARENT"
        refunit="chapter" >
  <step length=4>
        from="CHILD (ALL DIV2 N %3)"
        refunit="section" >
</refsDecl>]]></eg><p>This example is a formal representation for the referencing
scheme described informally in the following example:</p></exemplum><exemplum><eg><![CDATA[<refsDecl>
  <p>References are made up by concatenating the value for
  the <att>n</att> attribute on each <gi>div1</gi> element,
  followed by a colon, followed by the first six characters
  of the first <gi>head</gi> element found within it and a
  space, followed by exactly four characters derived from the
  value of the <att>n</att> attribute on the next included
  <gi>div2</gi> element.
</refsDecl>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o (p+ | step+ | state+)</elemDecl><xref target="HD54M"/><xref target="HD5"/><xref target="HD54"/></tagDoc><?tei:EOF refsdecl.tag ??><!-- refsDecl element --><?tei:SOF reg.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	reg.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : suppress mention of retroversion        --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- ********************************************************* reg --><tagDoc id="REG" usage="opt"><gi tei="yes">reg</gi><name>regularization</name><desc>contains a reading which has been regularized or normalized
in some sense.</desc><attList><attDef usage="opt"><attName>orig</attName><name>original</name><desc>gives the unregularized form of the text as found in the source
copy.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[     <reg orig='auctoritee'>Authority</reg>]]></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>identifies the individual responsible for the regularization
of the word or phrase.</desc><datatype>CDATA</datatype><valDesc>any string of characters, typically the initials of the
individual involved, or a role identifier like <q>editor</q> if not
known by name.</valDesc><default>#IMPLIED</default><eg></eg></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>The <gi tei="yes">reg</gi> tag is mirrored by the <gi tei="yes">orig</gi> tag,
which allows the unnormalized form of the original to be retained as
the content of the element, while still providing the opportunity to
record the regularized or normalized form postulated by a researcher.
The choice between the two elements is up to the encoder.</p></remarks><part type="top" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="COEDREG" type="div1"/><xref target="TC" type="div1"/></tagDoc><?tei:EOF reg.tag ??><!-- reg element --><?tei:SOF region.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	region.tag,v $
# Revision 1.2  94/03/07  16:13:50  lou
# revisions for ND
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-02 : MSM : revise des                              --><!-- 93-05-29 : MSM : delete long commented-out vallist       --><!-- 93-05-29 : MSM : fix ]]>                                 --><!-- 93-05-29 : MSM : change content model (no no no NOT pcdata!) --><!--********************************************************region --><tagDoc id="REGION" usage="opt"><gi tei="yes">region</gi><name>region</name><desc>in an address, contains the state, province, county or region
name; in a place name given as a hierarchy of geo-political
units, the <gi tei="yes">region</gi> is larger or administratively
superior to the <gi tei="yes">settlement</gi> and
smaller or administratively less important than the
<gi tei="yes">country</gi>.</desc><attList></attList><exemplum><eg><![CDATA[<placeName>
  <region type=state n='IL'>Illinois
</placeName>]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes names="PLACPART"/><elemDecl>- - (%paraContent)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF region.tag ??><!-- region element --><?tei:SOF relation.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	relation.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* relation --><tagDoc id="RELATION" usage="opt"><gi tei="yes">relation</gi><name>relationship</name><desc>describes any kind of relationship or linkage amongst a specified
group of participants.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>categorizes the relationship in some respect, e.g.
as social, personal or other.</desc><datatype>CDATA</datatype><valList type="semi"><val>social</val><desc>relationship concerned with social roles</desc><val>personal</val><desc>relationship concerned with personal roles, e.g.
kinship, marriage, etc.</desc><val>other</val><desc>other kinds of relationship</desc></valList><default>personal</default></attDef><attDef usage="req"><attName>desc</attName><desc>briefly describes the relationship.</desc><datatype>CDATA</datatype><valDesc>an open list of application-dependent keywords</valDesc><default>#IMPLIED</default></attDef><attDef usage="req"><attName>active</attName><desc>identifies the <q>active</q>participants in a non-mutual
relationship, or all the participants in a mutual one.</desc><datatype>IDREFS</datatype><valDesc>a list of identifier values for participant or participant
groups</valDesc><default>#IMPLIED</default></attDef><attDef usage="req"><attName>passive</attName><desc>identifies the <q>passive</q> participants in a non-mutual
relationship.</desc><datatype>IDREFS</datatype><valDesc>a list of identifier values for participant or participant
groups</valDesc><default>#IMPLIED</default></attDef><attDef usage="mwa"><attName>mutual</attName><desc>indicates whether the relationship holds equally amongst all the
participants.</desc><datatype>(Y | N)</datatype><valList type="closed"><val>Y</val><desc>the relationship is mutual</desc><val>N</val><desc>the relationship is directed</desc></valList><default>Y</default></attDef></attList><exemplum><eg><![CDATA[  <relation type=social desc="supervisor"
       active=P1 passive="P2 P3 P4" mutual=N>]]></eg></exemplum><exemplum><eg><![CDATA[  <relation type=personal desc="friends"
       active="P2 P3 P4" mutual=Y>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes/><dataDesc>Empty</dataDesc><elemDecl>- o EMPTY</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF relation.tag ??><!-- relation element --><?tei:SOF remarks.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : correct content model                   --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	remarks.tag,v $
# Revision 1.4  94/01/04  12:15:10  lou
# fix xrefs
# 
# Revision 1.3  1993/09/16  16:22:43  msmcq
# Publication of TD
#
# Revision 1.2  1993/08/13  20:50:06  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** remarks --><tagDoc id="REMARKS" usage="opt"><gi tei="yes">remarks</gi><desc>contains any commentary or discussion about the usage of an
element, attribute, class, or entity not otherwise documented within the
containing element.</desc><attList></attList><exemplum><eg><![CDATA[  <remarks><p>This element is probably redundant.]]></eg></exemplum><remarks><p>As defined in ODD, must contain paragraphs; should be
special.para</p></remarks><part type="aux" name="tsd"/><classes/><dataDesc>Contains at least one paragraph, unless it is empty.</dataDesc><elemDecl>- O (%component.seq)</elemDecl><xref target="TDTAG"/><xref target="TDATT"/><xref target="TDCLA"/><xref target="TDENT"/></tagDoc><?tei:EOF remarks.tag ??><!-- remarks element --><?tei:SOF renditn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	renditn.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- Revisions:                                               --><!-- 93-06-21 : MSM : correct para.content to paraContent     --><!-- 93-06-01 : MSM : correct ]]>                             --><!-- ****************************************************rendition --><tagDoc id="RENDITN" usage="rec"><gi tei="yes">rendition</gi><name>rendition</name><desc>supplies information about the intended rendition of one or more
elements.</desc><attList><!-- shd make ID required --></attList><exemplum><eg><![CDATA[ 
 ]]></eg></exemplum><remarks><p>Future releases of these Guidelines will provide for more
detailed specifications of rendition in terms of DSSSL properties; the
present proposal provides a hook for these extensions only.</p></remarks><part type="aux" name="hdr"/><classes/><elemDecl>- O (%paraContent) </elemDecl><xref target="HD57"/></tagDoc><?tei:EOF renditn.tag ??><!-- rendition element --><?tei:SOF residenc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	residenc.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ****************************************************** residenc --><!-- This one could use a little more structure, possibly --><tagDoc id="RESIDENC" usage="opt"><gi tei="yes">residence</gi><name>residence</name><desc>describes a person's present or past places of residence.</desc><attList></attList><exemplum><eg><![CDATA[  <residence>Childhood in East Africa, long term
    resident of Glasgow, Scotland.]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl> - o (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF residenc.tag ??><!-- residence element --><?tei:SOF role.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	role.tag,v $
# Revision 1.3  94/01/04  12:15:13  lou
# fix xrefs
# 
# Revision 1.2  1993/08/18  21:16:27  msmcq
# rename as resp (but keep old filename and id)
# as part of name shuffle for the sake of DR's role.
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- *********************************************************resp --><tagDoc id="ROLE" usage="opt"><gi tei="yes">resp</gi><desc>contains a phrase describing the nature of a person's
intellectual responsibility.</desc><attList></attList><exemplum><eg><![CDATA[<respStmt><resp>compiler</resp> <name>Edward Child</name></respStmt>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o (%phrase.seq;)</elemDecl><xref target="COBICOR"/><xref target="HD21"/><xref target="HD22"/><xref target="HD26"/></tagDoc><?tei:EOF role.tag ??><!-- resp element --><?tei:SOF respons.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	respons.tag,v $
# Revision 1.3  94/03/15  11:10:40  lou
# minor typos etc
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** resp --><!--12 mar:  change class membership from global to metadata --><tagDoc id="RESPONS" usage="opt"><gi tei="yes">respons</gi><name>responsibility</name><desc>identifies the individual(s) responsible for some aspect of the
markup of some particular element(s).</desc><attList><!-- ................................................. target --><attDef usage="req"><attName>target</attName><desc>gives the SGML identifier(s) of the element(s) for which some
aspect of the responsibility is being assigned.</desc><datatype>IDREFS</datatype><valDesc>one or more SGML identifiers.</valDesc><default>#REQUIRED</default><remarks><p></p></remarks></attDef><!-- .................................................. locus --><attDef usage="req"><attName>locus</attName><desc>indicates the specific aspect of the markup for which
responsibility is being assigned.</desc><datatype>CDATA</datatype><valList type="semi"><val>#gi </val><desc>responsibility for the claim that the element is of the
type indicated by the markup</desc><val>#location </val><desc>responsibility for the claim that the element
begins and ends where indicated</desc><val>#startloc </val><desc>responsibility for the claim that the element
begins where indicated</desc><val>#endloc </val><desc>responsibility for the claim that the element
ends where indicated</desc><val>name</val><desc>responsibility for the claim that the
<att tei="yes">name</att> attribute has the value given in the markup</desc><val>#transcribedContent </val><desc>responsibility for the transcription of
the element content</desc><val>#suppliedContent </val><desc>responsibility for the contents supplied by
the encoder (corrections, expansions of abbreviations, etc.)</desc></valList><default>#REQUIRED</default><remarks><p></p></remarks></attDef><!-- ................................................... resp --><attDef usage="req"><attName>resp</attName><desc>identifies the individual or agency responsible for the indicated
aspect of the electronic text.</desc><datatype>CDATA</datatype><valDesc>any string of characters, typically the initials of an
individual, the acronym of an agency, the name of a computer program,
etc.</valDesc><default>#REQUIRED</default><remarks><p></p></remarks></attDef><!-- ................................................... desc --><attDef usage="opt"><attName>desc</attName><name>description</name><desc>gives a brief prose note supplying any additional information
which should be recorded</desc><datatype>CDATA</datatype><valDesc>any string of characters, typically a phrase or sentence in a
natural language.</valDesc><default>#IMPLIED</default><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ <respons target=P1 
          locus='#gi #location' resp=AR>
  <respons target=P2
          locus=rend resp=LB>]]></eg></exemplum><remarks><p>The <gi tei="yes">respons</gi> element is designed for cases in which
fine-grained information about specific aspects of the markup of a text
is desirable for whatever reason.  Global responsibility for certain
aspects of markup is usually more simply indicated in the TEI header,
using the <gi tei="yes">respStmt</gi> element within the title statement, edition
statement, or change log.</p></remarks><part type="top" name="cert"/><classes names="METADATA"/><dataDesc>Empty.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="CERESP"/></tagDoc><?tei:EOF respons.tag ??><!-- respons element --><?tei:SOF resp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	resp.tag,v $
# Revision 1.3  94/01/04  12:15:11  lou
# fix xrefs
# 
# Revision 1.2  1993/08/18  21:12:18  msmcq
# rename as respStmt (part of name reorg for DR role)
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-08-18 : MSM : change name to respStmt (for DR role)   --><!--                  but leave id and filename alone         --><!-- 93-06-01 : MSM : change desc post Eynsham                --><!--                  fix typo in model                       --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-06 : MSM : allow any agent, not just name          --><!-- 92-12-06 : MSM : change from header to core              --><!-- *********************************************************resp --><tagDoc id="RESP" usage="rwa"><gi tei="yes">respStmt</gi><name>statement of responsibility</name><desc>supplies a statement of responsibility for someone responsible for
the intellectual content of a text, edition, recording, or series, where
the specialized elements for authors, editors, etc. do
not suffice or do not apply.</desc><attList></attList><exemplum><eg><![CDATA[  <respStmt><resp>transcribed from original ms</resp>
        <name>Claus Huitfeldt</name>
  </respStmt>]]></eg></exemplum><exemplum><eg><![CDATA[  <respStmt><resp>converted to SGML encoding</resp>
        <name>Alan Morrison</name>
  </respStmt>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc></dataDesc><elemDecl>- o ((resp &amp; name), (resp | name)*)</elemDecl><xref target="COBICOR"/><xref target="HD21"/><xref target="HD22"/><xref target="HD26"/></tagDoc><?tei:EOF resp.tag ??><!-- respStmt element --><?tei:SOF restore.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	restore.tag,v $
# Revision 1.4  94/08/29  15:23:27  msmcq
# Changes for unreachability bugs
# 
# Revision 1.3  1994/03/25  17:21:51  msmcq
# cleanup of miscellaneous tagdocs:  some typos,
# some INHERITED errors, supplied explicit end-tags for many attdef parts
# to shield a weakness of oddref1 (now fixed)
#
# Revision 1.2  1994/03/08  03:24:27  msmcq
# revision for P3
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- 94-03-21 : MSM : correct 'inherited' error               --><!-- 94-03-07 : MSM : correct ref to highlight: now hi (CH)   --><!-- 93-06-05 : MSM : modify valdesc                          --><!-- ENTITY restore   system 'restore.tag' --><!-- restore tag --><!-- **************************************************** lem --><tagDoc id="RESTORE" usage="rwa"><gi tei="yes">restore</gi><desc>indicates restoration of text to an earlier state by
cancellation of an editorial or authorial marking or instruction.</desc><attList><!-- ................................................... type --><attDef usage="rec"><attName>type</attName><desc>indicates the action cancelled by the restoration.</desc><datatype>CDATA</datatype><valDesc>The value of this should be the name of the tag contained
within the <gi tei="yes">restore</gi> element which is cancelled by the
restoration.  Most often, this will be <gi tei="yes">del</gi>, but might also
be <gi tei="yes">hi</gi>, etc.  In cases of simple nesting of a single
cancelled action within the <gi tei="yes">restore</gi> element this attribute
will not be necessary</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... desc --><attDef usage="rec"><attName>desc</attName><name>description</name><desc>gives a prose description of the means of restoration.</desc><datatype>CDATA</datatype><valDesc>Any word or phrase, such as <q>stet</q> or <q>strike-down</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... resp --><attDef usage="rec"><attName>resp</attName><name>responsible</name><desc>signifies the editor or transcriber responsible for identifying
the hand of the restoration.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... cert --><attDef usage="rec"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the
identification of the hand of the restoration.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="rec"><attName>hand</attName><desc>signifies the hand of the agent which made the restoration.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef></attList><remarks><p>Remainder of this tagdoc copied from rdg by LB</p></remarks><part type="top" name="tc"/><classes names="READINGS EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%phrase.seq;)</elemDecl><xref target="PHCD"/></tagDoc><?tei:EOF restore.tag ??><!-- restore element --><?tei:SOF revdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	revdesc.tag,v $
# Revision 1.2  94/01/04  12:15:12  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************revisionDesc --><tagDoc id="REVDESC" usage="rec"><gi tei="yes">revisionDesc</gi><name>revision description</name><desc>summarizes the revision history for a file.</desc><attList></attList><exemplum><eg><![CDATA[  <revisionDesc>
  <change><date>11 Nov 91  <name>EB  <what>Deleted chapter 10
  <change><date>23 Sept 91 <name>MSM <what>First draft
  </revisionDesc>]]></eg></exemplum><remarks><p>Record changes with most recent changes at the top of the
list.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- - (list | change+)</elemDecl><xref target="HD6"/><xref target="HD11"/></tagDoc><?tei:EOF revdesc.tag ??><!-- revisionDesc element --><?tei:SOF drrole.tag ??><!-- Role tag (DR version)                                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	drrole.tag,v $
# Revision 1.5  93/08/23  16:32:03  msmcq
# checkin of published version of DR
# 
# Revision 1.3  1993/08/13  20:49:53  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:31:15  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 93-08-16 : MSM : suppress membership in perfph           --><!-- 93-08-07 : MSM : cosmetic cleanup                        --><!-- 93-04-13 : MSM : fix ]]> problems                        --><!-- 93-04-12 : MSM : rename drrole from role                 --><!--****************************** role --><tagDoc id="DRROLE" usage="mwa"><gi tei="yes">role</gi><desc>the name of a dramatic role, as given in a cast list.</desc><attList><!-- XXX need to emphasize the ID attribute, since it is      --><!-- widely used elsewhere.  It is neither mentioned nor in   --><!-- an example, and the IDREF to it is all over the place.   --></attList><exemplum><eg><![CDATA[   <role id=JT>Joan Trash</><roleDesc>A Ginger-bread-woman</>]]></eg></exemplum><remarks><p>It is important to assign a meaningful ID attribute to
the <gi tei="yes">role</gi> element, since this ID is referred to by
<att tei="yes">who</att> attributes on many other elements.</p></remarks><part type="base" name="perf"/><classes/><dataDesc></dataDesc><elemDecl>- O (%phrase.seq)</elemDecl><xref target="DRCAST" type="div3"/></tagDoc><?tei:EOF drrole.tag ??><!-- role element --><?tei:SOF roledesc.tag ??><!-- RoleDesc tag                                             --><!-- Revisions:                                               --><!-- 93-08-20 : MSM : full stop at end of DESC                --><!-- 93-08-16 : MSM : suppress membership in perfph           --><!-- 93-08-16 : MSM : fix MS end problem                      --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: roledesc.tag,v $
    * Revision 1.7  1998/02/09 18:02:36  tei
    * fix egs
    *
    * Revision 1.6  94/02/12  10:43:17  lou
    * JL's comments of 4 feb
    * 
    * Revision 1.5  1993/08/23  16:48:38  msmcq
    * version published with DR
    * 
    * Revision 1.2  1993/08/13  20:50:07  msmcq
    * Clean ^Z
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!--****************************** roleDesc --><tagDoc id="ROLEDESC" usage="opt"><gi tei="yes">roleDesc</gi><name>role description</name><desc>describes a character's role in a drama.</desc><attList></attList><exemplum><eg><![CDATA[  <roleDesc>gentlemen of leisure</roleDesc>]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes/><dataDesc></dataDesc><elemDecl>- - (%phrase.seq)</elemDecl><xref target="DRCAST" type="div3"/></tagDoc><?tei:EOF roledesc.tag ??><!-- roleDesc element --><?tei:SOF rolename.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	rolename.tag,v $
# Revision 1.3  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.2  1994/03/15  11:10:41  lou
# minor typos etc
#
# Revision 1.1  1994/03/07  16:14:12  lou
# Initial revision
#
# Revision 1.2  1993/08/03  02:23:37  msmcq
# fix MS end problem
# --><!-- Revisions:                                               --><!-- 94-03-31 : MSM : for phraseSeq read phrase.seq           --><!-- renamed from titular --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- *************************************roleName (personal) --><!-- renamed from 'title' to avoid confusion: need better     --><!-- name: honorific?                                         --><tagDoc id="ROLENAME" usage="opt"><gi tei="yes">roleName</gi><name>roleName</name><desc>contains a name component which indicates that the referent has a
particular role or position in society, such as an official title or
rank.</desc><attList></attList><exemplum><eg><![CDATA[<persName>
  <foreName>William</foreName>
  <surname>Poulteny</surname>
  <roleName>Earl of Bath</roleName>
</persName>]]></eg></exemplum><remarks><p>A <gi tei="yes">roleName</gi> may be distinguished from an
<gi tei="yes">addName</gi> by virtue of the fact that, like a title, it typically
exists independently of its holder.</p></remarks><part type="top" name="ND"/><classes names="PERSPART"/><elemDecl>- - (%phrase.seq)</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF rolename.tag ??><!-- roleName element --><?tei:SOF root.tag ??><!-- ********** ROOT                                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	root.tag,v $
# Revision 1.5  93/09/22  19:19:27  msmcq
# changes for publicatin oof gD
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/09  19:48:16  msmcq
# restore RCS id, log
# --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : change CHILDREN to IMPLIED, change discussion --><!-- 93-09-17 : MSM : outDegr[ee   full word                  --><!-- 93-09-15 : MSM : cleanup                                 --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version                       --><!--                  replace LABEL and FS content by value=  --><!--                      and label=                          --><!--                  eliminate special drawing attributes    --><!--                      (use rend=)                         --><!-- ********** ROOT                                          --><tagDoc id="ROOT" usage="rwa"><gi tei="yes">root</gi><name>root node</name><desc>represents the root node of a tree.</desc><attList><attDef id="RTLAB" usage="rwa"><attName>label</attName><desc>gives a label for a root node.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef id="RTVALUE" usage="rwa"><attName>value</attName><desc>provides the value of the root, which is a feature structure or
other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier of a feature structure or other analytic
element.</valDesc><default>#IMPLIED</default></attDef><attDef id="RTCHILD" usage="req"><attName>children</attName><desc>provides a list of IDs of the elements which are the children of
the root node.</desc><datatype>IDREFS</datatype><valDesc>A list of valid identifiers.</valDesc><default>#IMPLIED</default><remarks><p>If the root has no children (i.e., the tree is
<soCalled>trivial</soCalled>), then the <att tei="yes">children</att>
attribute must be omitted.  For technical reasons, it cannot
be specified as <tag compl="full" tei="yes">root children=''</tag>.</p></remarks></attDef><attDef id="RTORD" usage="rwa"><!--On usage, see also remarks. --><attName>ord</attName><desc>indicates whether or not the root is ordered.</desc><datatype>(Y | N)</datatype><valList type="closed"><val>Y</val><desc>indicates that the children of the root are ordered.</desc><val>N</val><desc>indicates that the children of the root are unordered.</desc></valList><default>#IMPLIED</default><remarks><p>Use if and only if <att tei="yes">ord=partial</att> is specified on the
<gi tei="yes">tree</gi> tag and the root has more than one child.</p></remarks></attDef><attDef id="RTOUTDG" usage="opt"><attName>outDegree</attName><desc>gives the out degree of the root, the number of its children.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default><remarks><p>The in degree of the root is always 0.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<root id=VP1 label=VP children='VB1 PN1' outDegree=2>]]></eg></exemplum><part type="top" name="graphs"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="GDTR" type="div2"/></tagDoc><?tei:EOF root.tag ??><!-- root element --><?tei:SOF row.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	row.tag,v $
# Revision 1.4  94/03/01  16:15:57  msmcq
# fix rcs keywrods
#  --><!-- Revisions:                                               --><!-- 94-02-28 : MSM : allow end-tag omission                  --><!-- 94-02-24 : MSM : full stop after desc                    --><!-- ************************************************** row --><tagDoc id="ROW" usage="rwa"><gi tei="yes">row</gi><desc>contains one row of a table. </desc><attList><attDef usage="opt"><attName>role</attName><desc>indicates the kind of information held in the cells of this row.</desc><datatype>CDATA</datatype><valList type="semi"><val>label</val><desc>labelling or descriptive information only.</desc><val>data</val><desc>data values.</desc></valList><default>data</default><remarks><p>The value specified is the default for all cells in this
row.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<row role=data>
  <cell role=label>Classics
  <cell>Idle listless and unimproving
</row>]]></eg></exemplum><!-- shd find an example of nested table --><remarks><p></p></remarks><part type="base" name="tables"/><classes/><dataDesc></dataDesc><elemDecl>- O ((cell|table)+)</elemDecl><xref target="FTTAB1" type="div1"/></tagDoc><?tei:EOF row.tag ??><!-- row element --><?tei:SOF rs.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	rs.tag,v $
# Revision 1.3  94/03/28  19:59:41  msmcq
# punctuations, tyops (i don't know)
# 
# Revision 1.2  1993/09/16  16:18:28  msmcq
# add to class DATA
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-14 : MSM : add to class DATA                       --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!--*************************************************************rs --><tagDoc id="RS" usage="opt"><gi tei="yes">rs</gi><name>referencing string</name><desc>contains a general purpose name or referring string.</desc><attList><attDef usage="mwa"><attName>type</attName><desc>indicates more specifically the object referred to by the
referencing string. Values might include <q>person</q>,
<q>place</q>, <q>ship</q>, <q>element</q> etc.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<q>My dear <rs type=person>Mr. Bennet</rs>, </q>
said <rs type=person>his lady</rs> to him one day,
<q>have you heard that <rs type=place>Netherfield
Park</rs> is let at last?</q>]]></eg></exemplum><remarks></remarks><part type="common" name="co"/><classes names="DATA NAMES"/><elemDecl>- - (%phrase.seq)</elemDecl><xref target="NDPER"/><xref target="CONARS"/></tagDoc><?tei:EOF rs.tag ??><!-- rs element --><?tei:SOF s.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	s.tag,v $
# Revision 1.5  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.4  1994/02/27  15:55:51  lou
    * Revisions for publication of AI
    * 
    * Revision 1.3  1994/02/12  10:47:05  lou
    * revisions for P3
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- add to class clseg; change xref to ailc; fix content model --><!-- 93-02-10 : MSM : SP has been renamed TS.  Change xref    --><!-- 92-12-06 : MSM : correct xref to SP                      --><!-- 92-11-23 : MSM : add xref to SP chapter                  --><!-- *********************************************************** s --><tagDoc id="S" usage="opt"><gi tei="yes">s</gi><name>s-unit</name><desc>contains a sentence-like division of a text.</desc><attList></attList><exemplum><eg><![CDATA[<s>When are you leaving?</s>
<s>Tomorrow.</s>]]></eg></exemplum><remarks><p>The <gi tei="yes">s</gi> element may be used to mark orthographic
sentences, or any other segmentation of a text, provided that the
segmentation is end-to-end, complete, and non-nesting. For other kinds
of segmentation, the <gi tei="yes">seg</gi> element should be used.</p></remarks><part type="top" name="core"/><classes names="CLSEG"/><dataDesc>May contain character data, phrase-level and segmentation
class elements, other than <gi tei="yes">s</gi>.</dataDesc><elemDecl>- -  (%phrase.seq) -(s)</elemDecl><xref target="AILC"/><xref target="TSSASE"/></tagDoc><?tei:EOF s.tag ??><!-- s element --><?tei:SOF salute.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	salute.tag,v $
# Revision 1.3  94/03/15  11:10:41  lou
# minor typos etc
# 
# Revision 1.2  1994/01/04  12:15:14  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *******************************************************salute --><tagDoc id="SALUTE" usage="opt"><gi tei="yes">salute</gi><name>salutation</name><desc>contains a salutation or greeting prefixed to a foreword,
dedicatory epistle or other division of a text, or the
salutation in the closing of a letter, preface, etc.</desc><attList></attList><exemplum><eg><![CDATA[<salute>To all courteous mindes, that will voutchsafe the
readinge.</>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVTOP DIVBOT"/><elemDecl>- O (%phrase.seq;)</elemDecl><xref target="DSCO"/><xref target="DSOC"/></tagDoc><?tei:EOF salute.tag ??><!-- salute element --><?tei:SOF sampdecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	sampdecl.tag,v $
# Revision 1.2  94/01/04  12:15:15  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-01 : MSM : specify that samplingDecl is used for old TEXTINCL --><!-- 92-08-19 : MSM : provide full name                       --><!-- *************************************************samplingDecl --><tagDoc id="SAMPDECL" usage="opt"><gi tei="yes">samplingDecl</gi><name>sampling declaration</name><desc>contains a prose description of the rationale and methods used
in sampling texts in the creation of a corpus or collection.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks><p>This element records all information about systematic
inclusion or omission of portions of the text, whether a reflection
of sampling procedures in the pure sense or of systematic
omission of material deemed either too difficult to transcribe
or not of sufficient interest.</p></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD52"/><xref target="HD5"/><xref target="CCAS2"/></tagDoc><?tei:EOF sampdecl.tag ??><!-- samplingDecl element --><?tei:SOF script.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	script.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ************************************************* script --><tagDoc id="SCRIPT" usage="req"><gi tei="yes">script</gi><desc>contains a prose description of the script declared by a writing
system declaration.</desc><attList></attList><exemplum><eg><![CDATA[<eclaration lang=eng id='ISO8859-1'
    name='-//TEI P2: 1993//WSD ISO 8859-1: 1993//en'
    date='1993-06-01'>
 <language iso639=''>Various</language>
 <script>Latin script with diacritics.</script>
 <!-- ... -->
</eclaration>]]></eg></exemplum><exemplum><eg><![CDATA[<eclaration lang=eng id=JPN
 name='-//TEI P2: 1993//WSD JIS 0208//en' date='1993-06-01'>
 <language iso639='jpn'>Modern Japanese</language>
 <script>normal Japanese, with mixture of hiragana, katakana,
         and kanji.</script>
 <!-- ... -->
</eclaration>]]></eg></exemplum><remarks><p>This element is provided for the sake of clarity
and readability.  Strictly speaking, it is almost always redundant, as
knowledgeable readers will know what script is involved as soon as
they examine the base character set or the character repertoire.</p></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain character data only.</dataDesc><elemDecl>- O  (#PCDATA)</elemDecl><xref target="WDWS"/></tagDoc><?tei:EOF script.tag ??><!-- script element --><?tei:SOF scrstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	scrstmt.tag,v $
# Revision 1.3  94/01/04  12:15:16  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  02:20:58  msmcq
# rename old citn as bibl
# --><!-- Revisions:                                               --><!-- 93-06-21 : MSM : change citn to bibl, etc.               --><!-- ***************************************************scriptStmt --><tagDoc id="SCRSTMT" usage="rwa"><gi tei="yes">scriptStmt</gi><name>script statement</name><desc>contains a citation giving details of the script used for
a spoken text.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- - (p+ | bibl | biblFull | biblStruct)</elemDecl><xref target="HD32"/><xref target="HD3"/><xref target="CCAS2"/></tagDoc><?tei:EOF scrstmt.tag ??><!-- scriptStmt element --><?tei:SOF second.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	second.tag,v $
# Revision 1.4  94/03/15  11:10:42  lou
# minor typos etc
# 
# Revision 1.3  1994/03/07  16:12:51  lou
# revisions for publication
#
# Revision 1.2  1993/08/02  21:56:50  msmcq
# fix ]]> problem
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- second --><tagDoc id="SECOND" usage="opt"><gi tei="yes">second</gi><name>second</name><desc>the second component of a structured time-expression.</desc><attList></attList><exemplum><eg><![CDATA[  At the third stroke the time sponsored by Accurist
  will be 
  <timeStruct value='1821:30'>
    <hour>six</hour>
    <minute>twenty-one</minute> and 
    <second>thirty</second> seconds
  </timeStruct>]]><!-- speaking clock --></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF second.tag ??><!-- second element --><?tei:SOF seg.tag ??><!-- Seg tag ************************************************ --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	seg.tag,v $
# Revision 1.10  94/03/16  03:45:14  msmcq
# revision of SA as per John Lavagnino
# 
# Revision 1.8  1994/02/17  21:03:13  msmcq
# put MSC and eg end-tag on separate lines, to fix Script problem
#
# Revision 1.7  1994/02/12  10:47:00  lou
# revisions for P3
#
# Revision 1.6  1994/01/07  20:32:34  msmcq
# merge revisions made by DTL summer 1993
# some phrasing, add exx.
#
# Revision 1.5  1994/01/04  12:15:16  lou
# fix xrefs
#
# Revision 1.4  1993/11/26  18:33:09  msmcq
# revisions for publ of VE, pre-publ of AI
#
# Revision 1.3  1993/08/16  21:53:15  msmcq
# Tweaks for publication of DR
# --><!-- Revisions:                                               --><!-- 94-03-15 : MSM : suppress TYPE att, now on CLSEG         --><!-- 94-02-15 : MSM : put msc and /eg on separate lines       --><!-- 94-01-07 : MSM : merge DTL summer revisions              --><!-- 93-11-23 : MSM : add subtype                             --><!-- 93-11-18 : MSM : add PART attribute (needed for VE)      --><!-- 93-11-18 : MSM : change ID of class to clseg from seg    --><!-- 93-08-16 : MSM : change content model                    --><!-- 93-08-16 : MSM : make new seg element from old S element --><!-- 93-02-10 : MSM : SP has been renamed TS.  Change xref    --><!-- 92-12-06 : MSM : correct xref to SP                      --><!-- 92-11-23 : MSM : add xref to SP chapter                  --><!-- **************************************************** seg --><tagDoc id="SEG" usage="opt"><gi tei="yes">seg</gi><name>arbitrary segment</name><desc>contains any arbitrary phrase-level unit of text (including
other <gi tei="yes">seg</gi> elements).</desc><attList><!-- <attDef usage=opt>                                       --><!-- <attName>type                                            --><!-- <desc>indicates what sort of segment is marked.          --><!-- <datatype>CDATA                                          --><!-- <valDesc>any string of characters.                       --><!-- <default>#IMPLIED                                        --><!-- <remarks><p>The <att>type</att> attribute may be used    --><!-- to provide any suitable classification for the           --><!-- <gi>seg</gi> elements tagged in a text.  It should not   --><!-- be used to tag features for which other tags are         --><!-- defined in these Guidelines.                             --><!-- </attDef>                                                --><attDef usage="opt"><attName>subtype</attName><desc>provides a sub-categorization of the segment is marked.</desc><datatype>CDATA</datatype><valDesc>any string of characters.</valDesc><default>#IMPLIED</default><remarks><p>The <att tei="yes">subtype</att> attribute may be used to provide any
classification for the <gi tei="yes">seg</gi> elements tagged in a text suitable
for the <att tei="yes">type</att> given.</p></remarks></attDef><attDef usage="mwa"><attName>part</attName><desc>specifies whether or not the segment is complete. </desc><datatype>(Y | N | I | M | F)</datatype><valList type="closed"><val>Y</val><desc>the segment is incomplete</desc><val>N</val><desc>either the segment is complete, or no claim is made as to its
completeness</desc><val>I</val><desc>the initial part of an incomplete segment</desc><val>M</val><desc>a medial part of an incomplete segment</desc><val>F</val><desc>the final part of an incomplete segment</desc></valList><default>N</default><remarks><p>The values I, M, or F should be used only where it is
clear how the segment is to be reconstituted.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<seg>When are you leaving?</seg>
<seg>Tomorrow.</seg>]]></eg></exemplum><exemplum><eg><![CDATA[<s>
<seg type='typographic part-line'
rend=caps>So father's only</seg>
glory was the ballfield.</s>]]></eg></exemplum><exemplum><eg><![CDATA[<seg id=S1S3 type=preamble>
  <seg id=S1>Sigmund,
      <seg type=patronym>the son of Volsung</seg>,
  was a king in Frankish country.</seg>
  <seg id=S2>Sinfiotli was the eldest of his sons ...</seg>
  <seg id=S3>Borghild, Sigmund's wife, had a brother ... </seg>
<!-- ... -->
</seg>]]></eg></exemplum><remarks><p>The <gi tei="yes">seg</gi> element may be used at the encoder's
discretion to mark any  segments of the text of interest
for processing.  One use of the element is to mark text features for
which no appropriate markup is otherwise defined --- i.e. as a simple
extension mechanism.  Another use is to provide an identifier for some
segment which is to be pointed at by some other element --- i.e. to
provide a target, or a part of a target, for a <gi tei="yes">ptr</gi> or other
similar element.</p></remarks><part type="top" name="core"/><classes names="CLSEG"/><dataDesc>May contain anything which may appear within a paragraph.</dataDesc><elemDecl>- -  (%paraContent)</elemDecl><xref target="SASE"/><xref target="VESE"/><xref target="DRPAL"/></tagDoc><?tei:EOF seg.tag ??><!-- seg element --><?tei:SOF segmentn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	segmentn.tag,v $
# Revision 1.2  94/01/04  12:15:17  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-08-19 : MSM : delete otiose name element              --><!-- *************************************************segmentation --><tagDoc id="SEGMENTN" usage="opt"><gi tei="yes">segmentation</gi><desc>describes the principles according to which the text has been
segmented, for example into sentences, tone-units, graphemic strata,
etc.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/><xref target="CCAS2"/></tagDoc><?tei:EOF segmentn.tag ??><!-- segmentation element --><?tei:SOF sense.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : change model:  m.phrase, pcdata, not paraContent --><!-- 94-01-14 : MSM : allow paraContent (for example in MV)   --><!-- 94-01-14 : MSM : suppress extraneous commentary          --><!-- 94-01-12 : MSM : *not* a member of ditoplev!             --><!-- 94-01-12 : MSM : suppress dgroups class                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	sense.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ************************************************* sense  --><tagDoc id="SENSE" usage="opt"><gi tei="yes">sense</gi><name>sense information group</name><desc>groups together all information relating to one word sense in a
dictionary <gi tei="yes">entry</gi> (definitions, examples, translation
equivalents, etc.)</desc><attList><!-- .................................................. level --><attDef usage="opt"><attName>level</attName><desc>gives the nesting depth of this sense.</desc><datatype>NUMBER</datatype><valDesc>any string of digits</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="base" name="dict"/><classes names="DIPARTS DIGLOBAL"/><dataDesc>May contain character data mixed with any other elements
defined in the dictionary tag set.</dataDesc><elemDecl>- -  (sense | %m.dictionaryTopLevel | %m.phrase | #PCDATA)*</elemDecl><xref target="DIEN" type="div2"/></tagDoc><?tei:EOF sense.tag ??><!-- sense element --><?tei:SOF series.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	series.tag,v $
# Revision 1.3  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.2  1994/01/04  12:15:18  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 Jan 98 : LB : allow pcdata in content model --><!-- 92-12-09 : MSM : assign to class biblpart                --><!-- 92-12-06 : MSM : made file                               --><!-- ************************************************* series --><tagDoc id="SERIES" usage="mwa"><gi tei="yes">series</gi><name>series information</name><desc>contains information about the series in which a book or other
bibliographic item has appeared.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="core"/><classes names="BIBLPART"/><dataDesc>May contain character data and certain phrase-level elements.</dataDesc><elemDecl>- O  (title | editor | respStmt | biblScope | #PCDATA)*</elemDecl><xref target="COBICOL"/></tagDoc><?tei:EOF series.tag ??><!-- series element --><?tei:SOF serstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	serstmt.tag,v $
# Revision 1.3  94/01/04  12:15:18  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  02:21:33  msmcq
# old title.series becomes new title
# --><!-- Revisions:                                               --><!-- 2 jan 93: LB : modify content model again --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : modify content model                    --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- ***************************************************seriesStmt --><tagDoc id="SERSTMT" usage="opt"><gi tei="yes">seriesStmt</gi><name>series statement</name><desc>groups information about the <term>series</term>, if any, to which
a publication belongs.</desc><attList></attList><exemplum><eg><![CDATA[<seriesStmt>
    <title>Machine-Readable Texts for the Study of Indian
                  Literature</title>
    <respStmt>
         <resp>ed. by</resp> <name>Jan Gonda</name>
    </respStmt>
    <idno type=vol>1.2</idno>
    <idno type=ISSN>0 345 6789</idno>
</seriesStmt>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- O ( (title, (idno |  respStmt)*)
| p+ )</elemDecl><xref target="HD26"/><xref target="HD2"/></tagDoc><?tei:EOF serstmt.tag ??><!-- seriesStmt element --><?tei:SOF set.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: set.tag,v $
    * Revision 1.6  1998/02/09 18:02:36  tei
    * fix egs
    *
    * Revision 1.5  94/02/12  10:42:50  lou
    * JL's comments of 4 feb
    * 
    * Revision 1.3  1993/08/13  20:50:07  msmcq
    * Clean ^Z
    * 
    * Revision 1.2  1993/08/12  21:33:20  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ********************************************************** set --><!-- Revisions:                                               --><!-- 1993-08-07 : MSM : add head? to content model (O'Casey)  --><!-- 1993-08-07 : MSM : LB and MSM agree that this could use- --><!--                    fully be merged with the SETTING of   --><!--                    CC, but leave it as 'set' for now.    --><tagDoc id="SET" usage="opt"><gi tei="yes">set</gi><desc>contains a description of the setting, time, locale, appearance,
etc., of the action of a play, typically found in the front matter of
a printed performance text (not a stage direction).</desc><attList></attList><exemplum><eg><![CDATA[<set><p>The action takes place on February 7th between the hours of noon
and six in the afternoon, close to the Trenartha Tin Plate Works,
on the borders of England and Wales, where a strike has been in
progress throughout the winter.
</set>]]></eg><!-- Galsworthy, Strife --></exemplum><exemplum><eg><![CDATA[<set><head>SCENE</>
A Sub-Post Office on a late autumn evening
</set>]]><!-- Sean O'Casey, A Pound on Demand, in Five One-Act Plays,  --><!-- London:  Macmillan, 1975, p. 36.                         --></eg></exemplum><exemplum><eg rend="skel"><![CDATA[<front>
  <titlePage> ... </titlePage>
  <div type='Notice'> ... </>
  <div type='Dedication'> ... </>
  <div type='Performance'> ... </>
  <set><list type=gloss>
      <label>TIME: <item>1907
      <label>PLACE: <item>East Coast village in England
    </list>
  </set>
</front>]]><!-- Sean O'Casey, A Pound on Demand, in Five One-Act Plays,  --><!-- London:  Macmillan, 1975, p. 36.                         --></eg></exemplum><remarks><p>This element should not be used outside the front matter; for
similar contextual descriptions within the body of the text, use the
<gi tei="yes">stage</gi> element.</p></remarks><part type="base" name="perf"/><classes names="DRFRONT"/><dataDesc>Contains paragraphs or phrase level tags.</dataDesc><elemDecl>- - (head?, %specialPara)</elemDecl><xref target="DRFAB"/></tagDoc><?tei:EOF set.tag ??><!-- set element --><?tei:SOF setting.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: setting.tag,v $
    * Revision 1.5  1998/02/09 12:17:47  tei
    * fix examples
    *
    * Revision 1.4  98/01/29  21:50:43  tei
    * added DATE to content model
    * 
    * Revision 1.3  1998/01/28 19:22:39  tei
    * LB changes of 1998-01
    *
    * Revision 1.2  1994/01/30  15:20:37  lou
    * remove place; simplify content model
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 28 jan: add date to content model (again) --><!-- 4 Jan 98 : LB person not participant --><!-- 30 jan 94: change content model --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************** setting --><tagDoc id="SETTING" usage="opt"><gi tei="yes">setting</gi><name>setting</name><desc>describes one particular setting in which a language interaction
takes place.</desc><attList><attDef usage="rec"><attName>who</attName><desc>supplies the identifiers of the participants at this
setting.</desc><datatype>IDREFS</datatype><valDesc>must correspond with ID values of <gi tei="yes">person</gi>  or
<gi tei="yes">personGrp</gi> elements in the current document.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[  <setting who=P1>
  <name>New York City, US</name>
  <date>1989</date>
  <locale>on a park bench</locale>
  <activity>feeding birds</activity>
  </setting>]]></eg></exemplum><remarks><p>If the <att tei="yes">who</att> attribute is not supplied, the setting
is assumed to be that of all participants in the language
interaction.</p></remarks><part type="aux" name="core"/><classes/><dataDesc></dataDesc><!-- should content model use & rather than , --><elemDecl>- - (p+ | (name | time | date | locale | activity)* )</elemDecl><xref target="CCAHSE"/></tagDoc><?tei:EOF setting.tag ??><!-- setting element --><?tei:SOF settdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	settdesc.tag,v $
# Revision 1.2  94/01/04  12:15:20  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* settdesc --><tagDoc id="SETTDESC" usage="opt"><gi tei="yes">settingDesc</gi><name>setting description</name><desc>describes the setting or settings within which a language
interaction takes place, either as a prose description or as a
series of <gi tei="yes">setting</gi> elements.</desc><attList></attList><exemplum><eg><![CDATA[  <settingDesc>
  <p>Texts recorded in the Canadian Parliament building
  in Ottawa, between April and November 1988
  </settingDesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DECLABL"/><dataDesc>May contain a prose description organized as paragraphs, or
a series of <gi tei="yes">setting</gi> elements.</dataDesc><elemDecl>- o (p+ | setting+)</elemDecl><xref target="CCAH"/><xref target="HD4"/></tagDoc><?tei:EOF settdesc.tag ??><!-- settingDesc element --><?tei:SOF settle.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	settle.tag,v $
# Revision 1.2  94/03/07  16:13:08  lou
# revise for publicn.
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--********************************************************settle --><tagDoc id="SETTLE" usage="opt"><gi tei="yes">settlement</gi><desc>contains the name of the smallest component of a
place name expressed as a hierarchy of geo-political or
administrative units as in <q>Rochester</q>, New York;
<q>Glasgow</q>, Scotland.</desc><attList></attList><exemplum><eg><![CDATA[<placeName>
  <settlement type=town>Glasgow</settlement>
  <region>Scotland</region>
</placeName>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="PLACPART"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="NDPLAC"/></tagDoc><?tei:EOF settle.tag ??><!-- settlement element --><?tei:SOF shift.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	shift.tag,v $
# Revision 1.4  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.3  1994/01/04  12:15:20  lou
# fix xrefs
#
# Revision 1.2  1993/09/21  11:07:59  lou
# added to spoken class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************** shift --><tagDoc id="SHIFT" usage="opt"><gi tei="yes">shift</gi><name>Shift</name><desc>marks the point at which some paralinguistic feature of a series of
utterances by any one speaker changes.</desc><attList><attDef usage="opt"><attName>who</attName><desc>supplies an identifier for the speaker or group of speakers
         whose shift in some feature is being noted.
         Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
         or <tag compl="full" tei="yes">participant.grp</tag> element in the TEI header.</desc><datatype>IDREF</datatype><valDesc>Must identify a participant or participant group within the
       TEI Header</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>feature</attName><name>feature</name><desc>a paralinguistic feature.</desc><datatype>(tempo | loud | pitch | tension | rhythm | voice)
    </datatype><valList type="open"><val>tempo   </val><desc>speed of utterance.
    </desc><val>loud    </val><desc>loudness.
    </desc><val>pitch   </val><desc>pitch range.
    </desc><val>tension </val><desc>tension or stress pattern.
    </desc><val>rhythm  </val><desc>rhythmic qualities.
    </desc><val>voice   </val><desc>voice quality.
    </desc></valList><default>#REQUIRED</default><remarks></remarks></attDef><attDef usage="opt"><attName>new</attName><name>new state</name><desc>specifies the new state of the paralinguistic feature specified.</desc><datatype>CDATA</datatype><valDesc>An open list (for an example of possible values, see
      <xref target="TSSAPA"/>)</valDesc><default>normal</default><remarks><p>If no value is specified, it is assumed that the feature
concerned ceases to be remarkable. The value <q>normal</q> has the same
effect.
   </p></remarks></attDef></attList><exemplum><eg><![CDATA[    <u who=LB><shift feature=loud new=f>Elizabeth
    <u who=EB>Yes
    <u who=LB><shift>Come and try this <pause>
         <shift feature=loud new=ff>come on]]></eg><p>The word <q>Elizabeth</q> is spoken loudly, the words <q>Yes</q> and
<q>Come and try this</q> with normal volume, and the words <q>come on</q>
very loudly.</p></exemplum><remarks></remarks><part type="base" name="ts"/><classes names="COMPSPOK"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TSBAFD"/><xref target="TSSASH"/><xref target="TSBA"/></tagDoc><?tei:EOF shift.tag ??><!-- shift element --><?tei:SOF sic.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: sic.tag,v $
    * Revision 1.4  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.3  94/03/28  19:59:41  msmcq
    * punctuations, tyops (i don't know)
    * 
    * Revision 1.2  1993/08/03  02:22:09  msmcq
    * fix INHERITED keyword
    * --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct INHERITED                       --><!-- 92-12-07 : MSM : change model to specialPara             --><!-- 92-11-09 : MSM : supply missing end-tag for gi           --><!-- 92-11-09 : MSM : change id ref                           --><!-- ********************************************************* sic --><tagDoc id="SIC" usage="opt"><gi tei="yes">sic</gi><desc>contains text reproduced although apparently incorrect or
inaccurate.</desc><attList><attDef usage="opt"><attName>corr</attName><name>correction</name><desc>gives a correction for the apparent error in the copy text.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default><eg><![CDATA[  for his nose was as sharp as a pen, and
  <sic corr="a' babbled">a Table</sic>
  of green fields.]]></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>signifies the editor or transcriber responsible for suggesting
the correction held as the value of the <att tei="yes">corr</att> attribute.</desc><datatype>IDREF</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[  for his nose was as sharp as a pen, and
  <sic resp="Gifford" corr="a' babbled">a Table</sic>
  of green fields.]]></eg><remarks><p>This attribute has no meaning if no <att tei="yes">corr</att>
attribute is supplied.</p></remarks></attDef><!-- ................................................... cert --><attDef usage="opt"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the correction
held as the value of the <att tei="yes">corr</att> attribute.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute has no meaning if no <att tei="yes">corr</att>
attribute is supplied.</p></remarks></attDef></attList><exemplum><p>If all that is desired is to call attention to the
apparent problem in the copy text, no attributes are required:</p><eg><![CDATA[I don't know, Juan.  It's so far in the past now &mdash;
how <sic>we can</sic> prove or disprove anyone's theories?]]></eg><p>It is also possible to provide a correct reading and to identify
the individual responsible for the correction:
<eg><![CDATA[I don't know, Juan.  It's so far in the past now &mdash;
how <sic corr='can we' resp='MSM'>we can</sic> prove or
disprove anyone's theories?]]></eg></p></exemplum><remarks><p>The <gi tei="yes">sic</gi> tag is a mirror of <gi tei="yes">corr</gi>:	the
former leaves the original text untouched, giving the correction as
an
attribute value; the latter substitutes the correction, leaving the
original reading as an attribute value.  The choice between them is
up
to the encoder.</p></remarks><part type="top" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%specialPara;)</elemDecl><xref target="COEDCOR" type="div3"/></tagDoc><?tei:EOF sic.tag ??><!-- sic element --><?tei:SOF signed.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	signed.tag,v $
# Revision 1.3  94/03/15  11:10:43  lou
# minor typos etc
# 
# Revision 1.2  1994/01/04  12:15:21  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *******************************************************signed --><tagDoc id="SIGNED" usage="opt"><gi tei="yes">signed</gi><name>signature</name><desc>contains the closing salutation, etc., appended to a foreword,
dedicatory epistle, or other division of a text. </desc><attList></attList><exemplum><eg><![CDATA[<signed>Thine to command <name>Humph. Moseley</name></signed>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVTOP DIVBOT"/><elemDecl>- O (%phrase.seq;)</elemDecl><xref target="DSCO"/><xref target="DSOC"/></tagDoc><?tei:EOF signed.tag ??><!-- signed element --><?tei:SOF socalled.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	socalled.tag,v $
# Revision 1.3  94/03/27  21:39:30  msmcq
# ls so*
# add full stop in desc\.
# 
# Revision 1.2  1994/01/04  12:15:22  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- **************************************************** socalled --><tagDoc id="SOCALLED" usage="opt"><gi tei="yes">soCalled</gi><name>so called</name><desc>contains a word or phrase for which the author or narrator
indicates a disclaiming of responsibility, for example by the use
of scare quotes or italics.</desc><attList></attList><exemplum><eg><![CDATA[To edge his way along the crowded paths of life, warning
all human sympathy to keep its distance, was what the
knowing ones call <soCalled>nuts</soCalled> to Scrooge.]]></eg><!-- C.Dickens, Xmas Carol, 1843, p5 --></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="COHQQ"/></tagDoc><?tei:EOF socalled.tag ??><!-- soCalled element --><?tei:SOF socecsta.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	socecsta.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- ************************************************************* socecsta --><tagDoc id="SOCECSTA" usage="opt"><gi tei="yes">socecStatus</gi><name>socio-economic status</name><desc>contains an informal description of a person's perceived social or
economic status.</desc><attList><attDef usage="opt"><attName>scheme</attName><desc>identifies the classification system or taxonomy in use.</desc><datatype>IDREF</datatype><valDesc>Must identify a <gi tei="yes">taxonomy</gi> element</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>code</attName><desc>identifies a status code defined within the
classification system or taxonomy defined by the <att tei="yes">source</att>
attribute.</desc><datatype>IDREF</datatype><valDesc>Must identify a <gi tei="yes">category</gi> element</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<socecStatus scheme=RG code=AB1>]]></eg></exemplum><exemplum><eg><![CDATA[<socecStatus>Status AB1 in the RG Classification scheme]]></eg></exemplum><remarks><p>The content of this element may be used as an alternative
to the more formal specification made possible by its attributes; it
may also be used to supplement the formal specification with commentary
or clarification.</p></remarks><part type="aux" name="corpora"/><classes names="DEMOG"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl> - o (%phrase.seq)</elemDecl><xref target="CCAHPA"/></tagDoc><?tei:EOF socecsta.tag ??><!-- socecStatus element --><?tei:SOF sound.tag ??><!-- Sound tag                                                --><!-- Revisions:                                               --><!-- 93-08-19 : MSM : change class to stagedir                --><!-- 93-08-16 : MSM : cosmetic punctuation change             --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: sound.tag,v $
    * Revision 1.7  1998/02/09 18:02:36  tei
    * fix egs
    *
    * Revision 1.6  94/01/04  12:15:23  lou
    * fix xrefs
    * 
    * Revision 1.5  1993/08/23  16:48:38  msmcq
    * version published with DR
    * 
    * Revision 1.3  1993/08/13  20:50:08  msmcq
    * Clean ^Z
    * 
    * Revision 1.2  1993/08/12  21:33:20  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ******************************   sound--><tagDoc id="SOUND" usage="opt"><gi tei="yes">sound</gi><desc>describes a sound effect or musical sequence specified within a
screen play or radio script.</desc><attList><attDef usage="opt"><attName>type</attName><desc>categorizes the sound in some respect, e.g. as music, special
effect, etc.</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>discrete</attName><desc>indicates whether the sound overlaps the surrounding speeches
or interrupts them.</desc><datatype>(y|n|u)</datatype><valList type="open"><val>y</val><desc>the sound is heard between the surrounding speeches</desc><val>n</val><desc>the sound overlaps the surrounding speeches</desc><val>u</val><desc>unknown or inapplicable</desc></valList><default>u</default></attDef></attList><exemplum><eg><![CDATA[<sp><speaker>Benjy</speaker><p>Now to business.</sp>
<sp><speaker>Ford and Zaphod</speaker><p>To business.</sp>
<sound discrete=y>Glasses clink.</sound>
<sp><speaker>Benjy</speaker><p>I beg your pardon?</sp>
<sp><speaker>Ford</speaker><p>I'm sorry, I thought you were
  proposing a toast.</sp>]]></eg></exemplum><!-- possibly my favourite example in the whole of P3 (LB --><remarks><p>A specialized form of stage direction.</p></remarks><part type="base" name="perf"/><classes names="STAGEDIR"/><dataDesc>Contains character data and phrase level elements.</dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="DRTEC"/><xref target="DROTH" type="div3"/></tagDoc><?tei:EOF sound.tag ??><!-- sound element --><?tei:SOF soustmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	soustmt.tag,v $
# Revision 1.2  93/08/03  02:20:58  msmcq
# rename old citn as bibl
#  --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : change citn to bibl, etc.               --><!-- ***************************************************sourceDesc --><tagDoc id="SOUSTMT" usage="req"><gi tei="yes">sourceDesc</gi><desc>supplies a bibliographic description of the copy text(s) from
which an electronic text was derived or generated.</desc><attList></attList><exemplum><eg><![CDATA[  <sourceDesc>
  <p>No source: created in machine-readable form.</p>
  </sourceDesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- - (p | bibl | biblFull | biblStruct | listBibl |
scriptStmt | recordingStmt)+</elemDecl><xref target="HD3"/></tagDoc><?tei:EOF soustmt.tag ??><!-- sourceDesc element --><?tei:SOF sp.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: sp.tag,v $
    * Revision 1.7  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.6  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.5  1994/01/04  12:15:23  lou
    * fix xrefs
    * 
    * Revision 1.4  1993/08/23  16:48:38  msmcq
    * version published with DR
    * 
    * Revision 1.3  1993/08/13  20:50:09  msmcq
    * Clean ^Z
    * 
    * Revision 1.2  1993/08/12  21:31:15  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 feb 98 : LB : added AB to content model --><!-- 93-08-20 : MSM : cosmetic                                --><!-- 93-08-18 : MSM : allow end-tag omission!                 --><!-- 93-08-12 : MSM : change content model:  chunks only!     --><!-- 92-12-10 : MSM : correct end of marked section           --><!-- 92-12-10 : MSM : change class to CHUNK, after disc w/LB  --><!-- 92-12-09 : MSM : assign to class coredrama               --><!-- 92-12-07 : MSM : change xref to COdr                     --><!-- 92-12-07 : MSM : change model to specialPara from paraSeq --><!-- *************************************************************  sp--><tagDoc id="SP" usage="opt"><gi tei="yes">sp</gi><name>speech</name><desc>An individual speech in a performance text, or a passage
presented as such in a prose or verse text.</desc><attList><attDef usage="rec"><attName>who</attName><desc>identifies the speaker of the part by supplying an ID.</desc><datatype>IDREFS</datatype><valDesc>The IDREFS are derived from the ID attribute on the role
elements in the cast list or from a list of the participants.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<sp><speaker>The reverend Doctor Opimiam</speaker>
<p>I do not think I have named a single unpresentable fish.
<sp><speaker>Mr Gryll</speaker>
<p>Bream, Doctor: there is not much to be said for bream.
<sp><speaker>The Reverend Doctor Opimiam</speaker>
<p>On the contrary, sir, I think there is much to be said for him.
In the first place....
<p>Fish, Miss Gryll -- I could discourse to you on fish by the hour:
but for the present I will forbear...
</sp>]]></eg><!-- Peacock, Gryll Grange, p 778 --></exemplum><remarks><p>The <att tei="yes">who</att> attribute on this element may
be used either in addition to the <gi tei="yes">speaker</gi>
element or as an alternative.</p></remarks><part type="base" name="core"/><classes names="CHUNK"/><dataDesc>Lines or paragraphs, stage directions, and phrase-level
elements.</dataDesc><elemDecl>- O (speaker?, (p | l | lg | ab | seg | stage)+)</elemDecl><xref target="CODR"/><xref target="CODV"/><xref target="DRSP"/></tagDoc><?tei:EOF sp.tag ??><!-- sp element --><?tei:SOF space.tag ??><!-- Revisions:                                               --><!-- 3 Jan 97 : LB : fixed incidate typo --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- 94-04-07 : MSM : full stop after desc                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	space.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/08/29  15:23:27  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.4  1994/04/08  01:52:06  msmcq
    * Last fixes for FD in P3, etc.
    * 
    * Revision 1.3  1994/03/28  15:11:20  lou
    * rename SIZE as EXTENT to match examples
    * 
    * Revision 1.2  1994/03/15  11:10:44  lou
    * minor typos etc
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- 14 mar: fix xrefs; remove egregious comments and empty examples
--><!-- ************************************************** space --><tagDoc id="SPACE" usage="opt"><gi tei="yes">space</gi><desc>indicates the location of a significant space in the copy text.</desc><attList><!-- .................................................... dim --><attDef usage="rec"><attName>dim</attName><name>dimension</name><desc>indicates whether the space is horizontal or vertical.</desc><datatype>(horizontal | vertical)</datatype><valList type="closed"><val>horizontal</val><desc>the space is horizontal.</desc><val>vertical</val><desc>the space is vertical.</desc></valList><default>#IMPLIED</default><remarks><p>For irregular shapes in two dimensions, the value for
this attribute should reflect the more important of the two dimensions.
In conventional left-right scripts, a space with both vertical and
horizontal components should be classed as <q>vertical</q>.</p></remarks></attDef><!-- ................................................... size --><attDef usage="opt"><attName>extent</attName><desc>indicates approximately how large the space is, in letters,
minims, inches, or other appropriate unit.</desc><datatype>CDATA</datatype><valDesc>any measured quantity, e.g. <q>10 letters</q> or <q>4
lines</q>.</valDesc><default>#IMPLIED</default><remarks><p><!-- renamed from length to extent, so as to match examples (why not?) --><!-- [Renamed <att>length</att> as <att>size</att>. -MSM] --></p></remarks></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><desc>indicates the individual responsible for identifying and measuring
the space.</desc><datatype>CDATA</datatype><valDesc>usually the initials of the responsible individual.</valDesc><default>#IMPLIED</default><remarks><p><!-- [Not clear why this attribute is needed; could perhaps --><!-- better be handled by a general tagging-responsibility mechanism--><!-- parallel to the certainty mechanism of chapter CE. -MSM] --></p></remarks></attDef></attList><exemplum><eg><![CDATA[<![ CDATA [
By god if wommen had writen storyes
As <space extent='7'> han within her oratoryes]]></eg></exemplum><remarks><p>This element should be used wherever it is desired to record
an unusual space in the source text, e.g. space left for a word to be
filled in later, for later rubrication, etc.  It is not intended to be
used to mark normal inter-word space or the like.</p></remarks><part type="top" name="PH"/><classes names="EDIT"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="PHSP"/></tagDoc><?tei:EOF space.tag ??><!-- space element --><?tei:SOF span.tag ??><!-- *************************************************** span --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	span.tag,v $
# Revision 1.4  94/02/27  15:55:48  lou
# Revisions for publication of AI
# 
# Revision 1.3  1993/11/26  18:16:08  msmcq
# MSM changes pre-publicatino
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 26 feb : add to clinterp and metadata classes            --><!-- 93-11-26 : MSM : cosmetic                                --><!-- 93-11-26 : MSM : change resp att to INHERITED            --><!-- 93-11-26 : MSM : change tagging of ref to TO att         --><!-- 93-11-23 : MSM : change NAME att to TYPE                 --><!-- 93-09-22 : MSM : extract from ai tagdocs                 --><!-- *************************************************** span --><tagDoc id="SPAN" usage="opt"><gi tei="yes">span</gi><name>span</name><desc>associates an interpretative annotation directly with a span of
text.</desc><attList><attDef usage="req"><attName>value</attName><desc>identifies the specific phenomenon being annotated.</desc><datatype>CDATA</datatype><valDesc>Any string of characters.</valDesc><default>#REQUIRED</default></attDef><attDef usage="req"><attName>from</attName><desc>specifies the beginning of the passage being annotated; if not
accompanied by a <att tei="yes">to</att> attribute, then specifies the entire
passage.</desc><datatype>IDREF</datatype><valDesc>The ID of the element which occurs at the beginning of the
passage.</valDesc><default>#REQUIRED</default></attDef><attDef usage="opt"><attName>to</attName><desc>specifies the end of the passage being annotated.</desc><datatype>IDREF</datatype><valDesc>The ID of the element which occurs at the end of the passage.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<span resp=TMA type='structural unit' value='aftermath' from=P2 to=P4>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLINTERP METADATA"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="AISP"/></tagDoc><?tei:EOF span.tag ??><!-- span element --><?tei:SOF spangrp.tag ??><!-- *********************************************** spanGrp  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	spangrp.tag,v $
# Revision 1.2  94/02/27  15:55:48  lou
# Revisions for publication of AI
# 
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 26 feb : add to clinterp and metadata classes            --><!-- 93-07-22 : DTL : create                                  --><!--                                                          --><!-- *********************************************** spanGrp  --><tagDoc id="SPANGRP" usage="opt"><gi tei="yes">spanGrp</gi><name>span group</name><desc>collects together <gi tei="yes">span</gi> tags.</desc><attList></attList><exemplum><eg><![CDATA[<spanGrp resp=TMA type='collection of structural units'>
 <span value='introduction' from=S1 to=S3>
 <span value='conflict' from=S4a>
 <span value='climax' from=S4b>
 <span value='revenge' from=S5 to=Sx>
 <span value='reconciliation' from=nil1>
 <span value='aftermath' from=P2 to=P4>
 </spanGrp>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLINTERP METADATA"/><dataDesc>Any number of <gi tei="yes">span</gi> elements.</dataDesc><elemDecl>- - ((span)*)</elemDecl><xref target="AISP"/></tagDoc><?tei:EOF spangrp.tag ??><!-- spanGrp element --><?tei:SOF speaker.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	speaker.tag,v $
# Revision 1.3  93/08/13  20:50:09  msmcq
# Clean ^Z
# 
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-09 : MSM : correct content model                   --><!-- 92-12-09 : MSM : spelling changes                        --><!-- 92-12-07 : MSM : change xref to COdr                     --><!-- ************************************************************speaker --><tagDoc id="SPEAKER" usage="opt"><gi tei="yes">speaker</gi><desc>A specialized form of heading or label, giving the name of
one or more speakers in a dramatic text or fragment.</desc><attList></attList><exemplum><eg><![CDATA[<sp who="NI RSA">
<speaker>Nancy and Robert</speaker>
<stage type=delivery>(speaking simultaneously)</stage>
<p>The future? ...
</sp>]]></eg></exemplum><remarks><p>The <att tei="yes">who</att> attribute on the <gi tei="yes">sp</gi> element may
be used either in addition to this element or as an alternative.</p></remarks><part type="base" name="core"/><classes/><dataDesc>Any sequence of phrase level data</dataDesc><elemDecl>- O (%phrase.seq) -(speaker)</elemDecl><xref target="CODR"/></tagDoc><?tei:EOF speaker.tag ??><!-- speaker element --><?tei:SOF sponsor.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	sponsor.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- 92-08-19 : MSM : delete otiose name element              --><!-- ******************************************************sponsor --><tagDoc id="SPONSOR" usage="opt"><gi tei="yes">sponsor</gi><desc>specifies the name of a sponsoring organization or
institution.</desc><attList></attList><exemplum><eg><![CDATA[<sponsor>Association for Computers and the Humanities
</sponsor>
<sponsor>Association for Computational Linguistics
</sponsor>
<sponsor>Association for Literary and Linguistic Computing
</sponsor>]]></eg></exemplum><remarks><p>Sponsors give their intellectual authority to
a project; they are to be distinguished from <term>funders</term>,
who provide the funding but do not necessarily take
intellectual responsibility.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o ( %phrase.seq; )</elemDecl><xref target="HD21"/></tagDoc><?tei:EOF sponsor.tag ??><!-- sponsor element --><?tei:SOF stage.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: stage.tag,v $
    * Revision 1.8  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.7  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.6  1994/01/04  12:15:24  lou
    * fix xrefs
    * 
    * Revision 1.5  1993/09/16  16:21:45  msmcq
    * Add/restore to class COMMON
    * 
    * Revision 1.4  1993/08/13  20:50:11  msmcq
    * Clean ^Z
    * 
    * Revision 1.3  1993/08/12  21:31:15  msmcq
    * Rev. for publication of DR
    * 
    * Revision 1.2  1993/08/03  02:22:25  msmcq
    * change content model
    *--><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-14 : MSM : add to class COMMON                     --><!-- 93-08-07 : MSM : Reassign to class INTER, to allow to    --><!--                  occur within speeches and lines.        --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : change content model to specialPara     --><!-- 93-04-13 : MSM : eliminate ]]> problems                  --><!-- 92-12-10 : MSM : change class to CHUNK, after disc w/LB  --><!-- 92-12-09 : MSM : assign to class coredrama               --><!-- 92-12-07 : MSM : change xref to COdr                     --><!-- ************************************************** stage --><tagDoc id="STAGE" usage="mwa"><gi tei="yes">stage</gi><name>stage direction</name><desc>contains any kind of stage direction within a dramatic text or
fragment.</desc><attList><attDef usage="rec"><attName>type</attName><desc>indicates the kind of stage direction.</desc><datatype>CDATA</datatype><valList type="semi"><val>setting</val><desc>describes a setting.</desc><val>entrance</val><desc>describes an entrance.</desc><val>exit</val><desc>describes an exit.</desc><val>business</val><desc>describes stage business.</desc><val>novelistic</val><desc>is a narrative, motivating stage direction.</desc><val>delivery</val><desc>describes how a character speaks.</desc><val>modifier</val><desc>gives some detail about a character.</desc><val>location</val><desc>describes a location.</desc><val>mixed</val><desc>more than one of the above</desc></valList><default>mix</default></attDef></attList><!-- following examples from wg - origins unknown (for the most part) --><exemplum><eg><![CDATA[<stage type="setting">A curtain being drawn.</stage>
<stage type="setting">Music</stage>
<stage type="entrance">Enter Husband as being thrown off his
horse.</stage>
<stage type="exit">Exit pursued by a bear.</stage>
<stage type="business">He quickly takes the stone out.</stage>
<stage type="delivery">To Lussurioso.</stage>
<stage type="novelistic">Having had enough, and embarrassed for
the family.</stage>
<stage type="modifier">Disguised as Ansaldo.</stage>
<stage type="location">At a window.</stage>
<stage type="delivery" rend="inline">Aside.</stage>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="INTER COMMON"/><elemDecl>- - (%specialPara) -(stage)</elemDecl><xref target="CODR"/><xref target="CODV"/><xref target="DRSTA"/></tagDoc><?tei:EOF stage.tag ??><!-- stage element --><?tei:SOF state.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	state.tag,v $
# Revision 1.2  94/01/04  12:15:25  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-08-19 : MSM : provide valdesc for length att          --><!-- ********************************************************state --><tagDoc id="STATE" usage="opt"><gi tei="yes">state</gi><desc>specifies one component of a canonical reference defined by
the <q>milestone</q> method.</desc><attList><attDef id="ED" usage="opt"><attName>ed</attName><name>edition</name><desc>indicates which edition or version the milestone applies to.</desc><datatype>CDATA</datatype><valDesc>Any string of characters; usually a siglum conventionally used
for the edition.</valDesc><default>#IMPLIED</default><remarks><p>If <att tei="yes">ed</att> is not specified, then any milestone
tag with an appropriate <att tei="yes">unit</att> attribute will be selected.</p></remarks></attDef><attDef id="UNIT" usage="req"><attName>unit</attName><desc>indicates what kind of section is changing at this milestone.</desc><datatype>CDATA</datatype><valList type="semi"><val>page   </val><desc>page breaks in the reference edition.
    </desc><val>column </val><desc>column breaks.
    </desc><val>line   </val><desc>line breaks.
    </desc><val>book   </val><desc>any units termed <q>book</q>,<q>liber</q>, etc.
    </desc><val>poem   </val><desc>individual poems in a collection.
    </desc><val>canto  </val><desc>cantos or other major sections of a poem.
    </desc><val>stanza </val><desc>stanzas within a poem, book, or canto.
    </desc><val>act    </val><desc>acts within a play.
    </desc><val>scene  </val><desc>scenes within a play or act.
    </desc><val>section</val><desc>sections of any kind.
    </desc><val>absent </val><desc>passages not present in the reference edition.</desc></valList><default>#REQUIRED</default><remarks></remarks></attDef><attDef usage="opt"><attName>length</attName><desc>specifies the fixed length of the reference component.</desc><datatype>NUMBER</datatype><valDesc>Should be a positive integer; if no value is provided,
    the length is unlimited and goes to the next delimiter or to the
    end of the value.</valDesc><default>#IMPLIED</default><remarks><p>When constructing a reference, if the reference component
  found is of numeric type, the length
  is made up by inserting leading zeros; if it is not, by inserting
  trailing blanks. In either case, reference components are truncated
  if necessary at the right hand side.
  </p><p>When seeking a reference, the length indicates the
  number of characters which should be compared. Values longer than
  this will be regarded as matching, if they start correctly. </p></remarks></attDef><attDef usage="opt"><attName>delim</attName><desc>supplies a delimiting string following the reference
          component.</desc><datatype>CDATA</datatype><valDesc>If a single space is used it is interpreted as
          whitespace.</valDesc><default>#IMPLIED</default><remarks></remarks></attDef></attList><exemplum><eg><![CDATA[  <state unit=book delim=":">
  <state unit=line length=4>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o EMPTY</elemDecl><xref target="HD54M"/><xref target="HD54"/></tagDoc><?tei:EOF state.tag ??><!-- state element --><?tei:SOF stdvals.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	stdvals.tag,v $
# Revision 1.2  94/01/04  12:15:25  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *****************************************************stdVals --><tagDoc id="STDVALS" usage="rec"><gi tei="yes">stdVals</gi><name>Standard values</name><desc>specifies the format used when standardized date or number
values are supplied.</desc><attList></attList><exemplum><eg><![CDATA[<stdVals>
  <p>Dates are represented in ISO order: YYYYMMDD.
  <p>All integer numbers are left-filled to 8 digits.
</stdVals>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (p+)</elemDecl><xref target="HD53"/><xref target="CCAS2"/></tagDoc><?tei:EOF stdvals.tag ??><!-- stdVals element --><?tei:SOF step.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	step.tag,v $
# Revision 1.3  94/03/25  16:02:11  msmcq
# make changes as per J. Lavagnino
# implementing new extended-pointer mechanism for canonical refs.
# 
# Revision 1.2  1994/01/04  12:15:26  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-24 : MSM : del gi, att attributes                  --><!-- 94-03-24 : MSM : add refunit, from, to                   --><!-- 92-08-19 : MSM : provide valdesc for length att          --><!-- *********************************************************step --><tagDoc id="STEP" usage="opt"><gi tei="yes">step</gi><name>step</name><desc>specifies one component of a canonical reference defined by
the <q>stepwise</q> method.</desc><attList><!-- ................................................ refunit --><attDef usage="rec"><attName>refunit</attName><name>reference unit</name><desc>names the unit (book, chapter, canto, verse, ...) identified
by this step in a canonical reference.</desc><datatype>CDATA</datatype><valDesc>any string of characters; typically a word or phrase in
some natural language.</valDesc><default>#IMPLIED</default><remarks><p>The provision of this attribute helps make the structure
of the canonical reference much clearer.<!-- and may make it possible for application software to     --><!-- handle canonical references much more intelligently.     -->
Its use is strongly recommended.</p></remarks></attDef><attDef usage="opt"><attName>length</attName><desc>specifies the fixed length of the reference component.</desc><datatype>NUMBER</datatype><valDesc>Should be a positive integer; if no value is provided,
    the length is unlimited and goes to the next delimiter or to the
    end of the value.</valDesc><default>#IMPLIED</default><remarks><p>When constructing a reference, if the reference component
  found is of numeric type, the length
  is made up by inserting leading zeros; if it is not, by inserting
  trailing blanks. In either case, reference components are truncated
  if necessary at the right hand side.
  </p><p>When seeking a reference, the length indicates the
  number of characters which should be compared. Values longer than
  this will be regarded as matching, if they start correctly. </p></remarks></attDef><attDef usage="opt"><attName>delim</attName><desc>supplies a delimiting string following the reference
          component.</desc><datatype>CDATA</datatype><valDesc>If a single space is used it is interpreted as
         whitespace</valDesc><default>#IMPLIED</default><remarks></remarks></attDef><!-- ................................................... from --><attDef usage="req"><attName>from</attName><desc>specifies the starting point of the area referred to by this
step in the canonical reference.</desc><datatype>%extPtr</datatype><valDesc>a valid expression in the TEI extended pointer notation
documented in section <xref target="SAXR"/>.</valDesc><default>#REQUIRED</default></attDef><!-- ..................................................... to --><attDef usage="req"><attName>to</attName><desc>specifies the ending point of the area referred to by this step
in the canonical reference.</desc><datatype>%extPtr</datatype><valDesc>a valid expression in the TEI extended pointer notation
documented in section <xref target="SAXR"/>.</valDesc><default>'DITTO'</default><remarks><p> (optional)</p></remarks></attDef></attList><exemplum><eg><![CDATA[  <step delim=":" from='CHILD (1 DIV1 N %1)' refunit='book'>]]></eg></exemplum><remarks><p>With two differences, the extended pointer expressions given
as values for the <att tei="yes">from</att> and <att tei="yes">to</att> attributes behave
like those given for the corresponding attributes of an extended pointer
element like <gi tei="yes">xptr</gi>.  First:  unlike normal extended pointer
expressions, those on a <gi tei="yes">step</gi> element can contain references to
tokens in the canonical reference string itself, expressed as
<code tei="yes" type="frag">%1</code>, <code tei="yes" type="frag">%2</code>, etc.  Second:  the initial location
source for the first step is the root of the document, as for normal
extended pointers.  The initial location source for subsequent steps,
however, is the result of the previous step, not the root.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o EMPTY</elemDecl><xref target="HD54M"/><xref target="HD54"/><xref target="HD54S"/></tagDoc><?tei:EOF step.tag ??><!-- step element --><?tei:SOF str.tag ??><!-- ************************************************************ --><!-- TAGDOC for STR                                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	str.tag,v $
# Revision 1.4  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.3  1994/01/04  01:22:05  msmcq
# MSM rev. of FS; change REL value descriptions
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 93-12-22 : MSM : change descriptions on REL att values   --><!-- 93-09-22 : MSM : extract from group file                 --><!-- ************************************************************ --><tagDoc id="STR" usage="rwa"><gi tei="yes">str</gi><name>String value</name><desc>provides a string value for a feature.</desc><attList><attDef id="STRREL" usage="req"><attName>rel</attName><desc>indicates the relation of the given value to the actual value.</desc><datatype>(eq|ne|sb|ns|lt|le|gt|ge)</datatype><valList type="closed"><val>eq     </val><desc>indicates that the actual value is that given.
   </desc><val>ne     </val><desc>indicates that the actual value is not that given.
   </desc><val>sb     </val><desc>indicates that the value given is a substring of the
actual value.
   </desc><val>ns     </val><desc>indicates that the value given is not a substring
of the actual value.
   </desc><val>lt     </val><desc>indicates that the actual value is less than the
given value.
   </desc><val>le     </val><desc>indicates that the actual value is less than or
equal to the given value.
   </desc><val>gt     </val><desc>indicates that the actual value is greater than the
given value.
   </desc><val>ge     </val><desc>indicates that the actual value is greater than or
equal to the given value.</desc></valList><default>eq</default><remarks><p>The use of <att tei="yes">rel=lt</att>, etc. assumes that an ordering
of string values has been defined.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<str>Hello, world!</str>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Parsed character data.</dataDesc><elemDecl>- - (#PCDATA)</elemDecl><xref target="FSSY" type="div3"/></tagDoc><?tei:EOF str.tag ??><!-- str            --><?tei:SOF street.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	street.tag,v $
# Revision 1.2  94/01/04  12:15:27  lou
# fix xrefs
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-10 : MSM : change broth to phrase.seq              --><!-- 92-12-09 : MSM : punctuation cleanup                     --><!-- 92-12-07 : MSM : correct typo in desc                    --><!-- 92-11-09 : MSM : set xref to CObi                        --><!-- ******************************************************street --><tagDoc id="STREET" usage="opt"><gi tei="yes">street</gi><name>street</name><desc>a full street address including any name or number identifying a
building as well as the name of the street or route on which it is
located.</desc><attList></attList><exemplum><eg><![CDATA[        <street>via della Faggiola, 36</street>]]></eg></exemplum><exemplum><eg><![CDATA[        <street>Duntaggin,
                110 Southmoor Road
        </street>]]></eg></exemplum><remarks><p>The order and presentation of house names and numbers and
street names, etc., may vary considerably in different countries.  The
encoding should reflect the order which is appropriate in the country
concerned. </p></remarks><part type="base" name="core"/><classes names="ADDRPART"/><dataDesc>Running prose only</dataDesc><elemDecl>- o (%phrase.seq)</elemDecl><xref target="CONAAD"/></tagDoc><?tei:EOF street.tag ??><!-- street element --><?tei:SOF stress.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	stress.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ************************************************* stress --><tagDoc id="STRESS" usage="opt"><gi tei="yes">stress</gi><desc>contains the stress pattern for a dictionary headword, if given
separately.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DIPARTS"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/></tagDoc><?tei:EOF stress.tag ??><!-- stress element --><?tei:SOF string.tag ??><!-- Revisions:                                               --><!-- 93-09-11 : MSM : change desc, add system entity example  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	string.tag,v $
# Revision 1.3  93/09/16  16:22:01  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:50:11  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** string --><tagDoc id="STRING" usage="req"><gi tei="yes">string</gi><desc>contains the intended expansion for the entity documented
by an <gi tei="yes">entDoc</gi> element, enclosed by quotation marks.</desc><attList></attList><exemplum><eg><![CDATA[  <string>"the choice of quotes may'nt be insignificant"</string>]]></eg></exemplum><exemplum><p>System entities should include the <term>system</term> keyword
within the content of this element, as shown:</p><eg><![CDATA[  <string>SYSTEM 'teiclas2.ent'</>]]></eg></exemplum><remarks><p>The content of this element is the SGML
<term>entity text</term> for the entity, including any keywords.</p></remarks><part type="aux" name="tsd"/><classes/><dataDesc>any sequence of character data</dataDesc><elemDecl>- - (#PCDATA)</elemDecl><xref target="TDENT"/></tagDoc><?tei:EOF string.tag ??><!-- string element --><?tei:SOF subc.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to graminfo class                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	subc.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** subc --><tagDoc id="SUBC" usage="opt"><gi tei="yes">subc</gi><name>subcategorization</name><desc>contains subcategorization information (transitive/intransitive,
countable/non-count, etc.)</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DIPARTS GRAMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPGR"/></tagDoc><?tei:EOF subc.tag ??><!-- subc element --><?tei:SOF supentry.tag ??><!-- Revisions:                                               --><!-- 93-10-19 : MSM : add to class compdict                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	supentry.tag,v $
# Revision 1.2  94/01/04  01:22:39  msmcq
# add to class comp
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ********************************************* superentry --><tagDoc id="SUPENTRY" usage="rwa"><gi tei="yes">superentry</gi><desc>groups successive entries for a set of homographs.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="COMPDICT ENTRIES DIPARTS"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (form?, entry+)</elemDecl><xref target="DIBO"/></tagDoc><?tei:EOF supentry.tag ??><!-- superentry element --><?tei:SOF supplied.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of EDIT         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	supplied.tag,v $
# Revision 1.6  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.5  1994/08/29  15:23:27  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.4  1994/04/07  16:50:14  msmcq
    * Added full stops (lack detected by WWP)
    * 
    * Revision 1.3  1994/03/25  17:20:04  msmcq
    * correct #INHERITED to %INHERITED
    * 
    * Revision 1.2  1994/03/21  14:33:11  lou
    * second major typo purge
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- 4 Jan 98 : LB : it's <gap>, not <omit> stupid!           --><!-- ENTITY supplied  system 'supplied.tag' --><!-- supplied tag
--><!-- ************************************************ supplied --><tagDoc id="SUPPLIED" usage="opt"><gi tei="yes">supplied</gi><desc>signifies text supplied by the transcriber or editor in place
of text which cannot be read, either because of physical damage or
loss in the original or because it is illegible for any
reason.</desc><attList><!-- ................................................... reason --><attDef usage="opt"><attName>reason</attName><desc>indicates why the text has had to be supplied.</desc><datatype>CDATA</datatype><valDesc>any phrase describing the difficulty, e.g.
<q>overbinding</q>, <q>faded ink</q>, <q>lost folio</q>, <q>omitted
in original</q>.</valDesc><default>#IMPLIED</default></attDef><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><desc>indicates the individual responsible for supplying the letter,
word or passage contained within the <gi tei="yes">supplied</gi> element.</desc><datatype>CDATA</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>Where the presumed loss of text leading to the supplying of
text arises from action (partial deletion, etc.) assignable to an
identifiable hand, signifies the hand responsible for the action.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default></attDef><!-- ................................................... agent --><attDef usage="opt"><attName>agent</attName><desc>where the presumed loss of text leading to the supplying of
text arises from an identifiable cause, signifies the causative
agent.</desc><datatype>CDATA</datatype><valDesc>any prose description of the agent.</valDesc><default>#IMPLIED</default></attDef><!-- ................................................... source --><attDef usage="opt"><attName>source</attName><desc>states the source of the supplied text.</desc><datatype>CDATA</datatype><valDesc>any string of characters identifying the source of the
supplied text.  This might be the sigil for a manuscript, or a
particular edition, or the transcriber or editor's own initials,
indicating it as their conjecture.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[I am dr Sr yr
<supplied reason='illegible'
          resp='RW'
          source='amanuensis copy'>very humble Servt</>
Sydney Smith]]></eg></exemplum><remarks><p>The <gi tei="yes">damage</gi>, <gi tei="yes">gap</gi>, <gi tei="yes">del</gi>,
<gi tei="yes">unclear</gi> and <gi tei="yes">supplied</gi> elements may be closely allied
in use.  See section <xref target="PHCOMB"/> for discussion of which
element is appropriate for which circumstance.</p></remarks><part type="top" name="tc"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="PHDA"/></tagDoc><?tei:EOF supplied.tag ??><!-- supplied element --><?tei:SOF surname.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	surname.tag,v $
# Revision 1.4  94/03/15  11:10:44  lou
# minor typos etc
# 
# Revision 1.3  1994/03/07  16:13:01  lou
# revise for publicn
#
# Revision 1.2  1993/08/13  20:50:12  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!--******************************surname --><tagDoc id="SURNAME" usage="opt"><gi tei="yes">surname</gi><name>surname</name><desc>contains a family (inherited) name, as opposed to a given,
baptismal, or nick name.</desc><attList></attList><exemplum><eg><![CDATA[ 
<surname type=combine>St John Stevas</surname>]]></eg></exemplum><remarks></remarks><part type="top" name="nd"/><classes names="PERSPART"/><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="NDPER"/></tagDoc><?tei:EOF surname.tag ??><!-- surname element --><?tei:SOF syll.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : add to forminfo class                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	syll.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- *************************************************** syll --><tagDoc id="SYLL" usage="opt"><gi tei="yes">syll</gi><name>syllabification</name><desc>contains the syllabification of the headword.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DIPARTS FORMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/></tagDoc><?tei:EOF syll.tag ??><!-- syll element --><?tei:SOF sym.tag ??><!-- ************************************************************ --><!-- TAGDOC for SYM                                               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	sym.tag,v $
# Revision 1.4  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.3  1994/01/04  01:22:05  msmcq
# MSM rev. of FS; change REL value descriptions
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 93-12-22 : MSM : change descriptions on REL att values   --><!-- 93-09-22 : MSM : extract from bulk tagdoc                --><!-- ************************************************************ --><tagDoc id="SYM" usage="rwa"><gi tei="yes">sym</gi><name>Symbolic value</name><desc>provides symbolic values for features.</desc><attList><attDef id="SYMVAL" usage="req"><attName>value</attName><desc>provides a symbolic value for a feature, one of a finite list that
may be specified in a feature declaration.</desc><datatype>CDATA</datatype><valDesc>A string, e.g. <term>feminine</term>.</valDesc><default>#REQUIRED</default></attDef><attDef id="SYMREL" usage="req"><attName>rel</attName><desc>indicates the relation of the given value to the actual value.</desc><datatype>(eq|ne)</datatype><valList type="closed"><val>eq </val><desc>indicates that the actual value is that given.</desc><val>ne </val><desc>indicates that the actual value is not that given.</desc></valList><default>eq</default></attDef></attList><exemplum><eg><![CDATA[<sym rel=ne value=feminine>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Empty tag.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSSY" type="div3"/></tagDoc><?tei:EOF sym.tag ??><!-- sym            --><?tei:SOF symbol.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	symbol.tag,v $
# Revision 1.3  94/01/28  18:05:25  lou
# added xref
# 
# Revision 1.2  1993/11/26  18:19:55  msmcq
# revision for publication of VE
#
# Revision 1.1  1993/08/11  13:11:52  lou
# Initial revision
# --><!-- Revisions:                                               --><!-- 93-11-18 : MSM : fix omissibility to match LB's examples --><!-- 93-11-18 : MSM : correct model  phrase.seq for phraseSeq --><!-- 17 Jul 93 : LB : made file                                  --><!-- ********************************************************* symbol --><tagDoc id="SYMBOL" usage="opt"><gi tei="yes">symbol</gi><desc>documents the intended significance of a particular character or
character sequence within a metrical notation, either explicitly or in
terms of other <gi tei="yes">symbol</gi> elements in the same <gi tei="yes">metNotation</gi>.</desc><attList><attDef usage="req"><attName>value</attName><desc>specifies the character or character sequence being documented.</desc><datatype>CDATA</datatype><valDesc>any available character or character sequence.</valDesc><default>#REQUIRED</default></attDef><attDef usage="mwa"><attName>terminal</attName><desc>specifies whether the symbol is defined in terms of other
symbols (<att tei="yes">terminal=N</att>) or in prose (<att tei="yes">terminal=Y</att>).</desc><datatype>(Y|N)</datatype><valList type="open"><val>Y</val><desc>the element contains a prose definition of its meaning.</desc><val>N</val><desc>the element contains a definition of its meaning given using
symbols defined elsewhere in the same <gi tei="yes">metNotation</gi> element.</desc></valList><default>Y</default></attDef></attList><exemplum><eg><![CDATA[ <symbol value='x'>a stressed syllable
 <symbol value='o'>an unstressed syllable
 <symbol value='A' terminal=N>xoo]]></eg></exemplum><remarks></remarks><part type="base" name="hdr"/><classes/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%phrase.seq;)</elemDecl><xref target="HDMN"/><xref target="VEME"/></tagDoc><?tei:EOF symbol.tag ??><!-- symbol tag     --><?tei:SOF table.tag ??><!-- Revisions:                                               --><!-- 94-02-28 : MSM : status att has been renamed role        --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	table.tag,v $
# Revision 1.3  94/03/01  04:13:17  msmcq
# revision during/after SC meeting
# 
# Revision 1.2  1994/02/02  16:56:47  lou
# revised for publicn of FT
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ************************************************** table --><tagDoc id="TABLE" usage="rwa"><gi tei="yes">table</gi><desc>contains text displayed in tabular form, in
rows and columns.</desc><attList><attDef usage="opt"><attName>rows</attName><desc>indicates the number of rows in the table.</desc><datatype>NUMBER</datatype><valDesc>If no number is supplied, an application must calculate the
number of rows.</valDesc><default>#IMPLIED</default><remarks><p>Rows should be presented from top to bottom.</p></remarks></attDef><attDef usage="opt"><attName>cols</attName><desc>indicates the number of columns in each row of the table.</desc><datatype>NUMBER</datatype><valDesc>If no number is supplied, an application must calculate the
number of columns.</valDesc><default>#IMPLIED</default><remarks><p>Within each row, columns should be presented left to
right.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<table rows=4 cols=4>
<head>Poor Men's Lodgings in Norfolk (Mayhew, 1843)
<row role=label>
  <cell></>
  <cell>Dossing Cribs or Lodging Houses</>
  <cell>Beds</>
  <cell>Needys or Nightly Lodgers</></row>
<row role=data>
  <cell role=label>Bury St Edmund's</>
  <cell>5</><cell>8</><cell>128</></row>
<row role=data>
  <cell role=label>Thetford</>
  <cell>3</><cell>6</><cell>36</></row>
<row role=data>
  <cell role=label>Attleboro'</>
  <cell>3</><cell>5</><cell>20</></row>
<row role=data>
  <cell role=label>Wymondham</>
  <cell>1</><cell>11</><cell>22</></row>
<!-- ... -->
</table>]]></eg></exemplum><remarks><p>Any rendition information should be supplied using the
global <att tei="yes">rend</att> attribute, at the table, row, or cell level
as appropriate.</p></remarks><part type="base" name="tables"/><classes names="INTER"/><dataDesc>Contains an optional heading and a series of rows.</dataDesc><elemDecl>- - (head*, row+)</elemDecl><xref target="FTTAB1" type="div1"/></tagDoc><?tei:EOF table.tag ??><!-- table element --><?tei:SOF tag.tag ??><!-- *************************************************** tag --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tag.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/08  23:37:39  msmcq
# add sgmlkw class
#
# Revision 1.2  1993/08/13  20:50:13  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : trivial cleanup                         --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- *************************************************** tag --><tagDoc id="TAG" usage="opt"><gi tei="yes">tag</gi><desc>contains text of a complete SGML start- or end-tag, possibly
including attribute specifications, but excluding the opening and
closing markup delimiter characters.</desc><attList><attDef usage="opt"><attName>TEI
 </attName><desc>indicates whether this tag is valid within the TEI scheme or not.
 </desc><datatype>(yes|no)
 </datatype><valList type="open"><val>yes</val><desc>this is a valid TEI tag.
    </desc><val>no</val><desc>this is not a valid TEI tag.</desc></valList><default>yes
 </default></attDef></attList><exemplum><eg><![CDATA[    Mark the start of each italicised phrase with a <tag>hi rend=it</tag>
    tag, and its end with a <tag>/hi</tag> tag.]]></eg></exemplum><part type="aux" name="tsd"/><classes names="SGMLKW"/><dataDesc>contains only characters legal between markup delimiter
characters.</dataDesc><elemDecl>- - (#PCDATA)</elemDecl><xref target="TD"/></tagDoc><?tei:EOF tag.tag ??><!-- tag element --><?tei:SOF tagdoc.tag ??><!-- Revisions:                                               --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tagdoc.tag,v $
# Revision 1.4  94/01/04  12:15:27  lou
# fix xrefs
# 
# Revision 1.3  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.2  1993/09/08  23:41:55  msmcq
# change content model (make parents, children optional)
# and minor stylistic changes
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** tagDoc --><tagDoc id="TAGDOC" usage="opt"><gi tei="yes">tagDoc</gi><desc>documents the structure, content, and purpose of a single
SGML element type.</desc><attList><attDef usage="opt"><attName>usage
 </attName><desc>specifies the optionality of an attribute or element.
 </desc><datatype>(req|mwa|rec|rwa|opt)
 </datatype><valList type="closed"><val>req</val><desc>required</desc><val>mwa</val><desc>mandatory when applicable</desc><val>rec</val><desc>recommended</desc><val>rwa</val><desc>recommended when applicable</desc><val>opt</val><desc>optional</desc></valList><default>opt</default></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl>- - (gi, rs?, desc, attList?, exemplum*, remarks?,
   part?, classes?, files?, dataDesc?, parents?, children?,
   elemDecl, attlDecl?, ptr*, equiv*)</elemDecl><xref target="TDTAG"/><xref target="TD"/></tagDoc><?tei:EOF tagdoc.tag ??><!-- tagDoc element --><?tei:SOF tagsdecl.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tagsdecl.tag,v $
# Revision 1.2  94/01/04  12:15:28  lou
# fix xrefs
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- Revisions:                                               --><!-- 93-06-01 : MSM : Fixed ]]> problem                       --><!-- *****************************************************tagsDecl --><tagDoc id="TAGSDECL" usage="rec"><gi tei="yes">tagsDecl</gi><name>tagging declaration</name><desc>provides detailed information about the tagging applied to
an SGML document. </desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl>- O (rendition*, tagUsage*) </elemDecl><xref target="HD57"/><xref target="HD5"/></tagDoc><?tei:EOF tagsdecl.tag ??><!-- tagsDecl element --><?tei:SOF tagusage.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tagusage.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- Revisions:                                               --><!-- 93-06-21 : MSM : correct para.content to paraContent     --><!-- 93-06-01 : MSM : Fixed ]]> problem                       --><!-- 93-06-01 : MSM : fix typo                                --><!-- *****************************************************tagUsage --><tagDoc id="TAGUSAGE" usage="rec"><gi tei="yes">tagUsage</gi><name>tagUsage</name><desc>supplies information about the usage of a specific element
within a <gi tei="yes">text</gi>. </desc><attList><attDef usage="req"><attName>gi</attName><desc>the name (generic identifier) of the element indicated by the tag.</desc><datatype>NAME</datatype><valDesc>the name of an element from the current dtd</valDesc><default>#REQUIRED</default></attDef><attDef usage="rec"><attName>occurs</attName><desc>specifies the number of occurrences of this element within the text.
 </desc><datatype>NUMBER</datatype><valDesc>an integer number greater than zero</valDesc><default>#IMPLIED</default></attDef><attDef usage="rec"><attName>ident</attName><desc>specifies the number of occurrences of this element within the text
which bear a distinct value for the global <att tei="yes">id</att> attribute. </desc><datatype>NUMBER</datatype><valDesc>an integer number greater than zero</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>render</attName><desc>specifies the identifier of a <gi tei="yes">rendition</gi> element which
defines how this element is to be rendered.</desc><datatype>IDREF</datatype><valDesc>an SGML identifier specified as the value of the <att tei="yes">id</att>
attribute on some <gi tei="yes">rendition</gi> element in the current document.</valDesc><default>#IMPLIED
 </default></attDef></attList><exemplum><eg><![CDATA[ 
  <tagUsage gi=hi occurs=28 ident=2 render=IT>
      Used only to mark English words italicised in the copy text
  </tagUsage>
 ]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl>- O (%paraContent) </elemDecl><xref target="HD57"/></tagDoc><?tei:EOF tagusage.tag ??><!-- tagUsage element --><?tei:SOF taxonomy.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	taxonomy.tag,v $
# Revision 1.3  94/01/04  12:15:29  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  02:20:58  msmcq
# rename old citn as bibl
# --><!-- Revisions:                                               --><!-- 93-06-21 : MSM : change citn to bibl, etc.               --><!-- *****************************************************taxonomy --><tagDoc id="TAXONOMY" usage="opt"><gi tei="yes">taxonomy</gi><name>taxonomy</name><desc>defines a typology used to classify texts either implicitly, by
means of a bibliographic citation, or explicitly by a structured
taxonomy.</desc><attList></attList><exemplum><eg><![CDATA[  <taxonomy id=B>
    <bibl>Brown Corpus</bibl>
    <category id=B.A><catDesc>Press Reportage
      <category id=B.A1><catDesc>Daily</category>
      <category id=B.A2><catDesc>Sunday</category>
      <category id=B.A3><catDesc>National</category>
      <category id=B.A4><catDesc>Provincial</category>
      <category id=B.A5><catDesc>Political</category>
      <category id=B.A6><catDesc>Sports</category>
    </category>
    <category id=B.D><catDesc>Religion
      <category id=B.D1><catDesc>Books</category>
      <category id=B.D2><catDesc>Periodicals and tracts</category>
    </category>
  </taxonomy>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><elemDecl> - - (category+ | ((bibl | biblStruct | biblFull),
category*))</elemDecl><xref target="HD55"/></tagDoc><?tei:EOF taxonomy.tag ??><!-- taxonomy element --><?tei:SOF tech.tag ??><!-- Revisions:                                               --><!-- 93-08-19 : MSM : change class to stagedir                --><!-- 93-08-16 : MSM : change decl for TYPE att                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tech.tag,v $
# Revision 1.5  93/08/23  16:48:38  msmcq
# version published with DR
# 
# Revision 1.3  1993/08/13  20:50:13  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ***************************************************   TECH --><tagDoc id="TECH" usage="opt"><gi tei="yes">tech</gi><name>Technical stage direction</name><desc>describes a special purpose stage direction that is not
meant for the actors.</desc><attList><attDef usage="opt"><attName>type</attName><desc>categorizes the technical stage direction.</desc><datatype>(light | sound | prop | block)</datatype><valList type="semi"><val>light </val><desc>a lighting cue.</desc><val>sound </val><desc>a sound cue.</desc><val>prop  </val><desc>a prop cue.</desc><val>block </val><desc>a blocking instruction</desc></valList><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>perf</attName><desc>identifies the performance or performances to which this
technical direction applies.</desc><datatype>IDREFS</datatype><valDesc>The ID of a <gi tei="yes">performance</gi> element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<tech type=light>Red spot on his face</tech>]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="perf"/><classes names="STAGEDIR"/><dataDesc>Contains character level information.</dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="DRTEC" type="div3"/></tagDoc><?tei:EOF tech.tag ??><!-- tech element --><?tei:SOF tei2.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tei2.tag,v $
# Revision 1.5  94/03/15  11:10:45  lou
# minor typos etc
# 
# Revision 1.4  1994/03/01  17:18:34  lou
# fix typo noted by DTL
#
# Revision 1.3  1994/01/04  12:15:31  lou
# fix xrefs
#
# Revision 1.2  1993/08/03  02:23:17  msmcq
# normalize name case in model
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : correct name case in models             --><!-- 3 mar  : LB added example, changed desc                  --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************************** TEI.2 --><tagDoc id="TEI2" usage="req"><gi tei="yes">tei.2</gi><name>TEI 2 document</name><desc>contains a single TEI-conformant document, comprising a
TEI header and a text, either in isolation or as part of a
<gi tei="yes">teiCorpus</gi> element.</desc><attList></attList><exemplum><eg><![CDATA[ <tei.2>
   <teiHeader>
     <fileDesc>
        <titleStmt>
           <title>The shortest TEI Document Imaginable</title>
        <publicationStmt>
           <p>Published as part of TEI P2.
        </publicationStmt>
     <sourceDesc>
           <p>No source: this is an original work.
     </sourceDesc>
   </teiHeader>
   <text>
     <body>
      <p>This is about the shortest TEI document imaginable.
     </body>
   </text>
 </tei.2>]]></eg></exemplum><remarks><p>This element is required.</p></remarks><part type="aux" name="core"/><classes/><dataDesc>Must contain one TEI header and one text.</dataDesc><elemDecl>- O  (teiHeader, text)</elemDecl><xref target="STOVOV" type="div1"/><xref target="CCDEF"/></tagDoc><?tei:EOF tei2.tag ??><!-- tei.2 element --><?tei:SOF teicorp2.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teicorp2.tag,v $
# Revision 1.3  94/01/04  12:15:32  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  02:23:17  msmcq
# normalize name case in model
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : normalize case and punctuation of gis   --><!-- 3 mar : LB revised desc, changed content model (* -> +)  --><!-- 93-02-02 : MSM : made file                               --><!-- ************************************************** Teicorpus.2 --><tagDoc id="TEICORP2" usage="mwa"><gi tei="yes">teiCorpus.2</gi><name>TEI corpus</name><desc>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.</desc><attList></attList><exemplum><eg><![CDATA[ 
<teiCorpus.2>
    <teiHeader> ...
    <!-- header for corpus-level information -->
    </teiHeader>
    <tei.2 id=T1>
         <teiHeader> ...
         <!-- header for text-level information -->
         </teiHeader>
         <text> ... </text>
    </tei.2>
    <tei.2 id=T2>
         <teiHeader> ... </teiHeader>
         <text> ... </text>
    </tei.2>
    <!-- etc. -->
</teiCorpus.2>
 ]]></eg></exemplum><remarks><p>This element is mandatory when applicable.</p></remarks><part type="aux" name="core"/><classes/><dataDesc>Must contain one TEI header for the corpus, and a series
of <gi tei="yes">tei.2</gi> elements, one for each text.</dataDesc><elemDecl>- O  (teiHeader, TEI.2+)</elemDecl><xref target="STOVOV"/><xref target="CCDEF"/></tagDoc><?tei:EOF teicorp2.tag ??><!-- teiCorpus.2 element --><?tei:SOF teifsd2.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teifsd2.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY teifsd2 system  'teifsd2.tag' --><!-- teifsd2 tag --><!-- ************************************************ TEIFSD2 --><tagDoc id="TEIFSD2" usage="opt"><gi tei="yes">teiFsd2</gi><name>feature system declaration</name><desc>contains a feature system declaration.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>Must contain a standard TEI header, a set of feature
declarations, and optionally a set of feature co-occurrence constraints.</dataDesc><elemDecl>- - (teiHeader, fsDecl+)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF teifsd2.tag ??><!-- teiFsd2 element --><?tei:SOF teihead.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teihead.tag,v $
# Revision 1.3  94/01/04  12:15:34  lou
# fix xrefs
# 
# Revision 1.2  1993/08/03  02:20:58  msmcq
# rename old citn as bibl
# --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-21 : MSM : add explicit end tag to example         --><!-- 93-06-21 : MSM : change citn to bibl, etc.               --><!-- 93-06-01 : MSM : allow repeating encodingDesc elems      --><!-- 93-06-01 : MSM : also  repeating profileDesc (declable)  --><!-- 93-06-01 : MSM : normalized TeiHeader as teiHeader       --><!-- ****************************************************teiHeader --><tagDoc id="TEIHEAD" usage="req"><gi tei="yes">teiHeader</gi><name>TEI Header</name><desc>supplies the descriptive and declarative information making up an
<q>electronic title page</q> prefixed to every
TEI-conformant text.</desc><attList><attDef usage="opt"><attName>type
  </attName><desc>specifies the kind of document to which the header is attached.
  </desc><datatype>CDATA
  </datatype><valList type="closed"><val>text   </val><desc>the header is attached to a single text.
    </desc><val>corpus </val><desc>the header is attached to a corpus.
  </desc></valList><default>text</default></attDef><attDef usage="opt"><attName>creator
  </attName><desc>identifies the creator of the TEI Header.
  </desc><datatype>CDATA
  </datatype><valDesc>The name or initials of the person or institution
     responsible for creating this TEI header.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>status
  </attName><desc>indicates whether the header is new or has been substantially
        revised.
  </desc><datatype>(new | update)
  </datatype><valList type="open"><val>new    </val><desc>the header is a new header.
         </desc><val>update </val><desc>the header is an update (has been revised).
  </desc></valList><default>new</default></attDef><attDef usage="opt"><attName>date.created
  </attName><desc>indicates when the first version of the header was created.
  </desc><datatype>CDATA
  </datatype><valDesc>A date in any recognizable form.
  </valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>date.updated
  </attName><desc>indicates when the current version of the header was created.
  </desc><datatype>CDATA
  </datatype><valDesc>A date in any recognizable form.
  </valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<teiHeader>
<fileDesc>
   <titleStmt>
      <title>Shakespeare: the first folio (1623) in electronic form
      <author>Shakespeare, William (1564-1616)
      <resp><role>Originally prepared by</>
      <date>1968
            <name>Trevor Howard-Hill</>
      <resp><role>Revised and edited by</>
            <name>Christine Avern-Carr</>
   <publicationStmt>
      <distributor>Oxford Text Archive
      <address>13 Banbury Road, Oxford OX2 6NN, UK
      <idno>OTA number 119
      <availability>Freely available on a non-commercial basis.
      <date>1968
   <sourceDesc>
      <bibl>The first folio of Shakespeare, prepared by Charlton Hinman
      (The Norton Facsimile, 1968)</bibl>
</fileDesc>
<encodingDesc>
   <projectDesc>
   <p>Originally prepared for use in the production of a series of
      old-spelling concordances in 1968, this text was extensively
      checked and revised for use during the editing of the new Oxford
      Shakespeare (Wells and Taylor, 1989).
   <correction>
   <p>Turned letters are silently corrected.
   <normalization>
   <p>Original spelling and typography is retained, except that long s
      and ligatured forms are not encoded.
   </editorialDecl>
   <refsDecl id=ASLREF>
      <step gi=div1 attr=n><delim string=" ">
      <step gi=div2 attr=n><delim string=".">
      <step gi=l attr=n>
   </refsDecl>
</encodingDesc>
<revisionDesc>
    <change><by>CAC<date>12 Apr 89<what>Last checked</change>
    <change><by>LB<date>1 Mar 89<what>Made new file</change>
</revisionDesc>
</teiHeader>]]></eg></exemplum><remarks><p>One of the few elements unconditionally required in any
TEI document; the header may also be exchanged as an independent
document.</p></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- - (fileDesc, encodingDesc*, profileDesc*, revisionDesc?)</elemDecl><xref target="HD11"/><xref target="CCDEF"/></tagDoc><?tei:EOF teihead.tag ??><!-- teiHeader element --><?tei:SOF term.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	term.tag,v $
# Revision 1.3  94/03/21  14:33:12  lou
# second major typo purge
# 
# Revision 1.2  1994/01/04  12:15:36  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 92-12-18 : MSM : added type attribute                    --><!-- 92-12-18 : MSM : revise desc, add remarks on terminological work --><!-- ******************************************************** term --><tagDoc id="TERM" usage="rwa"><gi tei="yes">term</gi><desc>contains a single-word, multi-word or symbolic designation which
is regarded as a technical term.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the term using some typology.</desc><datatype>CDATA</datatype><valDesc>any string of characters; for serious terminological work,
values should be taken from the dictionary of data element types
specified in ISO WD 12 620.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[A computational device that infers structure from grammatical
strings of words is known as a <term>parser</term>, and much
of the history of NLP over the last 20 years has been occupied
with the design of parsers.]]></eg></exemplum><exemplum><eg><![CDATA[We may define <term rend=sc id=TDPV>discoursal point of view</term>
as <gloss target=TDPV>the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>]]></eg></exemplum><remarks><p>In formal terminological work, there is frequently
discussion over whether terms must be atomic or may include multi-word
lexical items, symbolic designations, or phraseological units.  The
<gi tei="yes">term</gi> element may be used to mark any of these.  No position is
taken on the philosophical issue of what a term can be; the looser
definition simply allows the <gi tei="yes">term</gi> element to be used by
practitioners of any persuasion.</p></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc>free prose</dataDesc><elemDecl>- - (%phrase.seq;)</elemDecl><xref target="COHQU"/><xref target="TETA"/></tagDoc><?tei:EOF term.tag ??><!-- term element --><?tei:SOF termentf.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: termentf.tag,v $
    * Revision 1.5  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.4  94/03/21  14:33:12  lou
    * second major typo purge
    * 
    * Revision 1.3  1994/01/04  12:15:37  lou
    * fix xrefs
    * 
    * Revision 1.2  1993/09/16  16:24:05  msmcq
    * Changes as per A.M.
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : changes agreed with A Melby by phone    --><!-- 93-09-15 : MSM : (drop inclusion exception, use classes) --><!-- 93-06-03 : MSM : class has new id: compterm not terminol --><!-- 92-12-23 : MSM : add note on dummy TERM element          --><!-- 92-12-23 : MSM : add note on dummy TERM element          --><!-- 92-12-21 : MSM : mention iso 12620 in desc               --><!-- 92-12-18 : MSM : remove FLATTERM class                   --><!-- 92-12-18 : MSM : added type attribute                    --><!-- 92-11-23 : MSM : correct element decl                    --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- ********************************************** termEntry --><tagDoc id="TERMENTF" usage="mwa"><gi tei="yes">termEntry</gi><name>terminological entry (flat structure)</name><desc>contains a single complete entry for one or more terms and their
associated descriptive and administrative data.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the term entry using some typology,
preferably the dictionary of data element types specified in
ISO WD 12 620.</desc><datatype>CDATA</datatype><valDesc>any string of characters; for serious terminological work,
values should be taken from the dictionary of data element types
specified in ISO WD 12 620.</valDesc><default>#IMPLIED</default><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Often but not always a term entry describes all
terms in a term bank denoting a given concept.  In the case of a
term entry documenting a concept for which no standard term
exists, the term entry will have to contain an empty
<soCalled>dummy</soCalled> <gi tei="yes">term</gi>,
of the form <tag compl="full" tei="yes">term</tag><tag compl="full" tei="yes">/term</tag>.</p></remarks><part type="base" name="term"/><classes names="COMPTERM"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O
( (%m.terminologyMisc | otherForm | gram | %m.terminologyInclusions)*,
  (term,
  (%m.terminologyMisc | otherForm | gram | %m.terminologyInclusions)*
  )+ )</elemDecl><xref target="TEBA" type="div1"/><!-- no desc appears --></tagDoc><?tei:EOF termentf.tag ??><!-- termEntry element (flat) --><?tei:SOF termentn.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	termentn.tag,v $
# Revision 1.4  94/03/21  14:33:13  lou
# second major typo purge
# 
# Revision 1.3  1994/01/04  12:15:38  lou
# fix xrefs
#
# Revision 1.2  1993/09/16  16:24:05  msmcq
# Changes as per A.M.
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-09-15 : MSM : changes agreed with A Melby by phone    --><!-- 93-09-15 : MSM : (change inclusion exception, use class) --><!-- 93-06-03 : MSM : class has new id: compterm not terminol --><!-- 92-12-23 : MSM : add note on dummy TERM element          --><!-- 92-12-21 : MSM : mention iso 12620 in desc               --><!-- 92-12-18 : MSM : remove FLATTERM class                   --><!-- 92-12-18 : MSM : added TYPE attribute                    --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- ********************************************** termEntry --><tagDoc id="TERMENTN" usage="mwa"><gi tei="yes">termEntry</gi><name>terminological entry (nested structure)</name><desc>contains a single complete entry for one concept
expressed in one language and comprising one or more terms and their
associated descriptive and administrative data, or, in bilingual and
multilingual terminology work, two or more very closely related concepts
comprising one or more terms in each language and their associated
descriptive and administrative data.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the term entry using some typology,
preferably the dictionary of data element types specified in
ISO WD 12 620.</desc><datatype>CDATA</datatype><valDesc>any string of characters; for serious terminological work,
values should be taken from the dictionary of data element types
specified in ISO WD 12 620.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>Often but not always a term entry describes all
terms in a term bank denoting a given concept.  In the case of a
term entry documenting a concept for which no standard term
exists, the term entry will have to contain a
<soCalled>dummy</soCalled> <gi tei="yes">tig</gi>, which contains a empty
term element of the form <tag compl="full" tei="yes">term</tag><tag compl="full" tei="yes">/term</tag>.</p></remarks><part type="base" name="term"/><classes names="COMPTERM"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O ((%m.terminologyMisc)*, tig+) +(%m.terminologyInclusions)</elemDecl><xref target="TEDTN"/><xref target="TEBA" type="div1"/></tagDoc><?tei:EOF termentn.tag ??><!-- termEntry element (nested) --><?tei:SOF text.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: text.tag,v $
    * Revision 1.6  1999/02/22 15:59:26  tei
    * fix comments
    *
   * Revision 1.5  1998/03/11 18:53:55  tei
   * correcting egs
   *
   * Revision 1.4  1994/03/15 11:10:45  lou
   * minor typos etc
   *
    * Revision 1.3  1994/01/15  21:16:35  msmcq
    * revisions in connection with di, for p3; see comments for details
    * 
    * Revision 1.2  1994/01/04  12:15:38  lou
    * fix xrefs
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- Revisions:                                               --><!-- 14 mar 94 : add group eg; add globincl to content model  --><!-- 94-01-12 : MSM : add dictionary to list of text types    --><!-- *********************************************************text --><tagDoc id="TEXT" usage="req"><gi tei="yes">text</gi><desc>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.</desc><attList></attList><exemplum><eg><![CDATA[<text>
<front><docTitle><titlePart>Autumn Haze</titlePart></docTitle>
<body>
<l>Is it a dragonfly or a maple leaf</l>
<l>That settles softly down upon the water?</l>
</body>
</text>]]>
 <!-- Amy Lowell, in Imagist Poetry, ed Jones, (Penguin 1972) --></eg></exemplum><exemplum><p>The body of a text may be replaced by a group of nested texts, as
in the following schematic:</p><eg rend="skel"><![CDATA[<text>
 <front>
    <!-- front matter for whole text -->
 </front>
 <group> 
   <!-- start of first group -->
  <text>
    <front>
      <!-- front matter for first text -->
    </front>
  </text>
  <text> 
     <!-- second text -->
  </text>
 </group> 
 <group>
  <!-- start of second group  -->
 </group>
</text>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="INTER DECLING"/><elemDecl>- - (front?, (body | group), back?) +(%m.globincl;)</elemDecl><xref target="DS"/><xref target="TEDT"/><xref target="CCDEF"/></tagDoc><?tei:EOF text.tag ??><!-- text element --><?tei:SOF textclas.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	textclas.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ***************************************************textClass --><tagDoc id="TEXTCLAS" usage="opt"><gi tei="yes">textClass</gi><name>text classification</name><desc>groups information which describes the nature or topic of a text
in terms of a standard classification scheme, thesaurus, etc.</desc><attList></attList><exemplum><eg><![CDATA[  <textClass>
    <catRef target=TC1>
    <classCode source=DD12>001.9
    <keywords>
      <list><item>End of the world
      <item>History - philosophy
      </list>
  </textClass>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes names="DECLABL"/><elemDecl> - - ((classCode | catRef | keywords)* )</elemDecl><xref target="HD43"/></tagDoc><?tei:EOF textclas.tag ??><!-- textClass element --><?tei:SOF textdesc.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	textdesc.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- Revisions:                                               --><!-- 93-03-10 : MSM : update idref:  AH/CCah                  --><!-- 93-03-10 : MSM : put term tag around sit. parms.         --><!-- ****************************************************** textdesc --><tagDoc id="TEXTDESC" usage="opt"><gi tei="yes">textDesc</gi><name>text description</name><desc>provides a description of a text in terms of its
<term>situational parameters</term>.</desc><attList></attList><exemplum><eg><![CDATA[<textDesc id=T1 n='Informal domestic conversation'>
  <channel mode=s>
  <constitution type=single>
  <derivation type=original>
  <domain type=domestic>
  <factuality type=mixed>
  <interaction type=complete active=plural passive=many>
  <preparedness type='spontaneous'>
  <purpose type=entertain degree=high>
  <purpose type=inform degree=medium>
</textDesc>]]></eg></exemplum><remarks></remarks><part type="aux" name="corpora"/><classes names="DECLABL"/><dataDesc></dataDesc><elemDecl>- o (channel, constitution, derivation, domain, factuality,
    interaction, preparedness, purpose+)</elemDecl><xref target="CCAHTD"/></tagDoc><?tei:EOF textdesc.tag ??><!-- textDesc element --><?tei:SOF then.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	then.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ENTITY then system     'then.tag' --><!-- then tag --><!-- *************************************************** then --><tagDoc id="THEN" usage="mwa"><gi tei="yes">then</gi><desc>separates the condition from the default in an <gi tei="yes">if</gi>, or
the antecedent and the consequent in a <gi tei="yes">cond</gi> element.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is provided primarily to enhance the
human readability of the feature-system declaration.</p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="FD"/></tagDoc><?tei:EOF then.tag ??><!-- then element --><?tei:SOF tig.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tig.tag,v $
# Revision 1.4  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.3  1994/01/04  12:15:39  lou
# fix xrefs
#
# Revision 1.2  1993/09/16  16:24:05  msmcq
# Changes as per A.M.
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-30 : MSM : correct case on ofig (not oFig)         --><!-- 93-09-15 : MSM : changes agreed with A Melby by phone    --><!-- 93-09-15 : MSM : Further revision of model, AM and MSM   --><!--                  (clarification of &, make naked         --><!--                  otherForm elements illegal, and use     --><!--                  termmisc and termincl classes)          --><!-- 20 may 93 : LB revised content model as per AM post-Eynsham --><!-- 92-12-23 : MSM : add note on dummy TERM element          --><!-- 92-12-21 : MSM : mention iso 12620 in desc               --><!-- 92-12-18 : MSM : added TYPE attribute                    --><!-- 92-11-23 : MSM : added end-tag for gi                    --><!-- **************************************************** tig --><tagDoc id="TIG" usage="opt"><gi tei="yes">tig</gi><name>term information group</name><desc>within a <gi tei="yes">termEntry</gi> element, contains information elements
associated with a single term.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the <gi tei="yes">tig</gi> using some typology,
preferably the dictionary of data element types specified in
ISO WD 12 620.</desc><datatype>CDATA</datatype><valDesc>any string of characters; for serious terminological work,
values should be taken from the dictionary of data element types
specified in ISO WD 12 620.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[ 
 ]]></eg></exemplum><remarks><p>The <gi tei="yes">tig</gi> element occurs only when the
<soCalled>nested</soCalled> form of the terminology base is used.  In
the case of a term entry documenting a concept for which no standard
term exists, the term entry will have to contain a
<soCalled>dummy</soCalled> <gi tei="yes">tig</gi>, which contains a empty term
element of the form <tag compl="full" tei="yes">term</tag><tag compl="full" tei="yes">/term</tag>.</p></remarks><part type="base" name="term"/><classes/><dataDesc>May contain a <gi tei="yes">term</gi> element, followed by zero or more
<gi tei="yes">descrip</gi> elements describing the term, followed in turn by zero
or more <gi tei="yes">otherForm</gi> or <gi tei="yes">ofig</gi> elements.</dataDesc><elemDecl>- O
((%m.terminologyMisc)*, (term, gram*), (%m.terminologyMisc)*, ofig*)</elemDecl><xref target="TEDTN"/><xref target="TETA" type="div1"/></tagDoc><?tei:EOF tig.tag ??><!-- tig element --><?tei:SOF time.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	time.tag,v $
# Revision 1.2  94/03/07  16:13:16  lou
# revision for ND
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-02 : MSM : add new atts from DGRtime               --><!-- 92-12-09 : MSM : normaliZe spelling                      --><!-- ******************************************************** time --><tagDoc id="TIME" usage="opt"><gi tei="yes">time</gi><desc>contains a phrase defining a time of day in any format.</desc><attList><attDef usage="opt"><attName>value</attName><desc>gives the value of the time in a standard form.</desc><datatype>CDATA</datatype><valDesc>Any string representing a time in standard format; recommended
form is <q>hhmm</q>, using the 24 hour clock.</valDesc><default>#IMPLIED</default><eg><![CDATA[<time value=1600>four o' clock</time>]]></eg><remarks><p>If the normalized form of time is not given using the twenty-four
hour clock, this fact should be documented in the <gi tei="yes">stdVals</gi>
element in the TEI Header.</p></remarks></attDef><attDef usage="rwa"><attName>type</attName><desc>indicates something about the type of temporal expression being
tagged.</desc><datatype>(am | pm | 24hour | descriptive)</datatype><valList type="closed"><val>am</val><desc>indicates a temporal expression made on the basis of a
twelve-hour clock and referring to a time between midnight and noon.</desc><val>pm</val><desc>indicates a temporal expression made on the basis of a
twelve-hour clock and referring to a time between noon and midnight.</desc><val>24hour</val><desc>indicates a temporal expression made on the basis of a
twenty-four-hour clock.</desc><val>descriptive</val><desc>indicates a temporal expression made in descriptive
terms, e.g. <q>noon</q>.</desc></valList><default>#IMPLIED</default></attDef><attDef usage="rwa"><attName>zone</attName><desc>indicates time zone or place name wherever this is necessary to
evaluate a temporal expression.</desc><datatype>CDATA</datatype><valDesc>contains a word or phrase such as GMT or 'Eastern Standard
Time' which might be helpful in evaluating the temporal expression.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[ As he sat smiling, the quarter struck &mdash <time value=1145>
 the quarter to twelve</time>.]]></eg><!-- Woolf, Mrs Dalloway, p64 --></exemplum><remarks></remarks><part type="top" name="core"/><classes names="DATA"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONADA" type="div3"/></tagDoc><!-- end of time --><?tei:EOF time.tag ??><!-- time element --><?tei:SOF timeline.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	timeline.tag,v $
# Revision 1.2  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
#  --><!-- *********************************************** timeline --><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix LINKINFO, make member of METADATA   --><!-- 94-08-04 : MSM : Added RCS id                            --><!-- 93-07-22 : DTL : based on P2 definition of ALIGN         --><!--                  delete type= (time only, space can wait!) --><!--                  make origin= required                   --><!--                                                          --><tagDoc id="TIMELINE" usage="opt"><gi tei="yes">timeline</gi><name>timeline</name><desc>provides a set of ordered points in time which can be linked to
elements of a spoken text to create a temporal alignment of that text.</desc><attList><attDef usage="req"><attName>origin</attName><desc>designates the origin of the timeline, i.e. the time at which it
begins.</desc><datatype>IDREF</datatype><valDesc>must point to one of the <tag compl="full" tei="yes">when</tag> tags in its content.</valDesc><default>#REQUIRED</default><remarks><p>If the time of the origin is not known, it should be
given an absolute value in descriptive terms, e.g. <q>sometime on the
night of the murder</q> or <q>unknown</q>.</p></remarks></attDef><attDef usage="rwa"><attName>unit</attName><desc>specifies the unit of time corresponding to the <att tei="yes">interval</att>
value of the timeline or of its constituent points in time.</desc><datatype>NMTOKEN</datatype><valDesc>a semi-closed list of recognized time units such as
<q>millisecond</q>, <q>second</q>, <q>minute</q>.</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>interval</attName><desc>specifies the numeric portion of a time interval</desc><datatype>NUTOKEN</datatype><valDesc>-1 or any nonnegative number</valDesc><default>#IMPLIED</default><remarks><p>The value -1 indicates uncertainty about all the intervals in
the timeline; 0 indicates that all the intervals are evenly spaced, but
the size of the intervals is not known; positive values indicate evenly
spaced values of the size specified.  If individual points in time in the
timeline are given different values for the <att tei="yes">interval</att>
attribute, those values locally override the value given in the timeline.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<timeline id=TL1 origin=w0 unit=centisecond>
  <when id=W0 absolute='sometime Monday morning before Christmas'
  <when id=W1 since=w0 interval=-1>
  <when id=W2 since=w1 interval=10>
  <when id=W3 since=w2 interval=20>
  <when id=W4 since=w3 interval=15>
  <when id=W5 since=w4 interval=25>
  <when id=W6 since=w5 interval=10>
  </timeline>]]></eg></exemplum><remarks><p>Occurs where??</p></remarks><part type="top" name="link"/><classes names="METADATA"/><dataDesc>one or more points in time, one of which is its origin</dataDesc><elemDecl>- - ((when)+)</elemDecl><xref target="SASYMP" type="div3"/></tagDoc><?tei:EOF timeline.tag ??><!-- timeline element --><?tei:SOF timerang.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	timerang.tag,v $
# Revision 1.2  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- ****************************************************** timerang --><tagDoc id="TIMERANG" usage="opt"><gi tei="yes">timeRange</gi><name>time range</name><desc>contains two times or another phrase indicating a time period.</desc><attList><attDef usage="opt"><attName>from</attName><desc>indicates the starting point of the time period in standard form.</desc><datatype>CDATA</datatype><valDesc>a time of day; recommended form is to use the 24 hour clock.</valDesc><default>#IMPLIED</default><remarks><p>The value should conform to the standard form declared in
the <gi tei="yes">stdVals</gi> element in the TEI header.</p></remarks></attDef><attDef usage="opt"><attName>to</attName><desc>indicates the ending point of the time period in standard form.</desc><datatype>CDATA</datatype><valDesc>a time of day; recommended form is to use the 24 hour clock.</valDesc><default>#IMPLIED</default><remarks><p>The value should conform to the standard form declared in
the <gi tei="yes">stdVals</gi> element in the TEI header.</p></remarks></attDef><attDef usage="opt"><attName>exact</attName><desc>indicates the precision to be attached to either or both times
specified.</desc><datatype>(to|from|both|none)</datatype><valList type="closed"><val>to</val><desc>the <att tei="yes">to</att> time is exact</desc><val>from</val><desc>the <att tei="yes">from</att> time is exact</desc><val>both</val><desc>both times are exact</desc><val>none</val><desc>both times are approximate or unspecified</desc></valList><default>#IMPLIED</default><eg><![CDATA[  <timeRange from=1600 to=1620 exact=from>
       Just after teatime</timeRange>]]></eg><remarks><p>time values should conform to the standard form declared in
the <gi tei="yes">stdVals</gi> element in the TEI header.</p></remarks></attDef></attList><exemplum><eg></eg></exemplum><part type="top" name="core"/><classes names="DATA"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- -  (%phrase.seq;)</elemDecl><xref target="CONADA" type="div3"/></tagDoc><?tei:EOF timerang.tag ??><!-- timeRange element --><?tei:SOF timestru.tag ??><!-- Revisions:                                               --><!-- 94-03-31 : MSM : for m.temporalExpr read %m.temporalExpr --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: timestru.tag,v $
    * Revision 1.4  1998/02/09 14:30:22  tei
    * fixing egs....
    *
    * Revision 1.3  94/04/01  17:41:18  msmcq
    * Changes while checking DTD
    *  --><!-- ********************************************* timeStruct --><tagDoc id="TIMESTRU" usage="opt"><gi tei="yes">timeStruct</gi><desc>contains an internally structured representation for a time of day.</desc><attList><attDef usage="rwa"><attName>zone</attName><desc>indicates time zone or place name wherever this is necessary to
evaluate a temporal expression.</desc><datatype>CDATA</datatype><valDesc>contains a word or phrase such as GMT or <q>Eastern Standard
Time</q> defining a time zone.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<timeStruct value=1615 zone=GMT>
   <hour>four</hour>
   <minute>fifteen</minute>
</timeStruct>]]></eg></exemplum><remarks></remarks><part type="top" name="core"/><classes names="DATA TEMPEXP"/><dataDesc>May contain temporal components and character data only.</dataDesc><elemDecl>- -  ((%m.temporalExpr; | #PCDATA)+)</elemDecl><xref target="CONADA" type="div3"/></tagDoc><?tei:EOF timestru.tag ??><!-- timeStruct element --><?tei:SOF title.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	title.tag,v $
# Revision 1.3  94/01/04  12:15:40  lou
# fix xrefs
# 
# Revision 1.2  1993/08/23  16:47:30  msmcq
# add to class hqphrase
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-08-19 : MSM : add to hqphrase                         --><!-- 93-03-10 : MSM : change model from soup to paracontent   --><!-- 92-12-06 : MSM : add level, type attributes              --><!-- 92-11-09 : MSM : set xref to CObi                        --><!-- 92-08-19 : MSM : change xref to HD/22                    --><!-- ******************************************************* title --><tagDoc id="TITLE" usage="opt"><gi tei="yes">title</gi><desc>contains the title of a work, whether article, book, journal, or
series, including any alternative titles or subtitles.</desc><attList><!-- .................................................. level --><attDef usage="rwa"><attName>level</attName><name>bibliographic level (or class) of title</name><desc>indicates whether this is the title of an article, book, journal,
series, or unpublished material.</desc><datatype>(a | m | j | s | u)</datatype><valList type="closed"><val>a
    </val><desc>analytic title (article, poem, or other item published as
          part of a larger item)
    </desc><val>m
    </val><desc>monographic title (book, collection, or other item published
          as a distinct item, including single volumes of multi-volume
          works)
    </desc><val>j
    </val><desc>journal title
    </desc><val>s
    </val><desc>series title
    </desc><val>u
    </val><desc>title of unpublished material (including theses and
          dissertations unless published by a commercial press)</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>If the title appears directly enclosed within an
<gi tei="yes">analytic</gi> element, the <att tei="yes">level</att>, if given, must be
<q>a</q>; if it appears directly enclosed within a <gi tei="yes">monogr</gi>
element, <att tei="yes">level</att> must be <q>m</q>, <q>j</q>, or <q>u</q>;
when <gi tei="yes">title</gi> is directly enclosed by <gi tei="yes">series</gi>,
<att tei="yes">level</att> must be <q>s</q>.</p></remarks></attDef><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><name>type of title</name><desc>classifies the title according to some convenient typology.</desc><datatype>CDATA</datatype><valList type="open"><val>main        </val><desc>main title
    </desc><val>subordinate </val><desc>subtitle, title of part
    </desc><val>parallel    </val><desc>alternate title, often in another language,
                           by which the work is also known
    </desc><val>abbreviated </val><desc>abbreviated form of title</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p>This attribute is provided for convenience in analysing
titles and processing them according to their type; where such
specialized processing is not necessary, there is no need for such
analysis, and the entire title, including subtitles and any parallel
titles, may be enclosed within a single <gi tei="yes">title</gi> element.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<title>La vie mode d'emploi. Romans.</title>]]></eg></exemplum><exemplum><eg><![CDATA[<title>Synthese: an international journal for epistemology, methodology
and history of science</title>]]></eg></exemplum><exemplum><eg><![CDATA[<title>Information Technology and the Research Process: Proceedings
of a conference held at Cranfield Institute of Technology, UK, 18-21
July 1989</title>]]></eg></exemplum><exemplum><eg><![CDATA[<title>Hardy's Tess of the D'Urbervilles: a machine readable edition]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="HQPHRASE"/><dataDesc></dataDesc><elemDecl>- o (%paraContent)</elemDecl><xref target="COBICOR"/><xref target="HD21"/><xref target="HD26"/></tagDoc><!-- end of TITLE --><?tei:EOF title.tag ??><!-- title element --><?tei:SOF titlepa.tag ??><!-- Revisions:                                               --><!-- 93-08-19 : MSM : add to clfront class                    --><!-- 93-08-19 : MSM : add TYPE attribute                      --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: titlepa.tag,v $
    * Revision 1.4  1999/02/22 15:58:21  tei
    * Fix comments
    *
   * Revision 1.3  1998/03/11 18:53:55  tei
   * correcting egs
   *
   * Revision 1.2  1994/03/15 11:10:46  lou
   * minor typos etc

    * Revision 1.1  1993/12/20  15:51:34  lou
    * Initial revision
    * 
    * Revision 1.2  1993/08/23  16:48:38  msmcq
    * version published with DR
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ****************************************************titlePage --><tagDoc id="TITLEPA" usage="rec"><gi tei="yes">titlePage</gi><name>title page</name><desc>contains the title page of a text, appearing within the front
or back matter. </desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the title page according to any convenient typology.</desc><datatype>CDATA</datatype><valDesc>Any string, e.g. <q>full</q>, <q>half</q>, <q>Series</q>, etc.</valDesc><default>#IMPLIED</default><remarks><p>This attribute allows the same element to be used for
volume title pages, series title pages, etc., as well as for the
<soCalled>main</soCalled> title page of a work.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<titlePage>
<docTitle>
<titlePart type=main>THOMAS OF
Reading.</>
<titlePart type=alt>
OR,
The sixe worthy yeomen
of the West.</>
</docTitle>
<docEdition>Now the fourth time corrected and enlarged</docEdition>
<byline>By T.D.</byline>
<figure>
<head>TP</head>
<p>Thou shalt labor till thou returne to duste
<figDesc>Printers Ornament used by TP</figDesc>
</figure>
<docImprint>
Printed at <name type=place>London</name> for <name>T.P.</name>
<date>1612.</date></docImprint>
</titlePage>]]></eg></exemplum><remarks></remarks><part type="aux" name="core"/><classes names="CLFRONT"/><!-- < elemdecl > - o ((docTitle | byline | docAuthor |       --><!-- docImprint | imprimatur | epigraph | ornament)+)< /      --><!-- elemdecl >                                               --><elemDecl>- o (%m.tpParts;)+ </elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF titlepa.tag ??><!-- titlePage element --><?tei:SOF titlept.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: titlept.tag,v $
    * Revision 1.3  1998/03/11 18:53:55  tei
    * correcting egs
    *
    * Revision 1.2  1998/01/31 18:29:58  tei
    * changed to allow empty lists (sigh)
    *
    * Revision 1.1  93/12/20  15:52:08  lou
    * Initial revision
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    * --><!-- ****************************************************titlepart --><tagDoc id="TITLEPT" usage="rec"><gi tei="yes">titlePart</gi><name>title part</name><desc>contains a subsection or division of the title of a work, as
indicated on a title page.</desc><attList><attDef usage="opt"><attName>type
   </attName><desc>specifies the role of this subdivision of the title.</desc><datatype>CDATA
   </datatype><valList type="semi"><val>main</val><desc>main title of the work
        </desc><val>sub</val><desc>subtitle  of the work
        </desc><val>alt</val><desc>alternative title  of the work
        </desc><val>desc</val><desc>descriptive paraphrase of the work included in
        title
   </desc></valList><default>main</default></attDef></attList><exemplum><eg><![CDATA[<docTitle>
  <titlePart type=main>THE
  FORTUNES
  AND
  MISFORTUNES
  Of the FAMOUS
  Moll Flanders, &amp;c.
  <titlePart type=desc>Who was BORN in
  NEWGATE,
  And during a Life of continu'd Variety for
  Threescore Years, besides her Childhood, was
  Twelve Year a <hi>Whore</hi>, five times a <hi>Wife</hi> (wherof
  once to her own Brother) Twelve Year a <hi>Thief,</hi>
  Eight Year a Transported <hi>Felon</hi> in <hi>Virginia</hi>, at last
  grew <hi>Rich</hi>, liv'd <hi>Honest</hi>, and died a <hi>Penitent</hi>.
</docTitle>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="TPPARTS FMCHUNK"/><dataDesc></dataDesc><elemDecl>- O (%paraContent;)</elemDecl><xref target="DSTITL"/></tagDoc><?tei:EOF titlept.tag ??><!-- titlePart element --><?tei:SOF titstmt.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	titstmt.tag,v $
# Revision 1.2  94/01/04  13:17:56  lou
# resp->respstmt
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 93-06-01 : MSM : allow editor                            --><!-- ****************************************************titleStmt --><tagDoc id="TITSTMT" usage="req"><gi tei="yes">titleStmt</gi><name>title statement</name><desc>groups information about the title of a work and those
responsible for its intellectual content.</desc><attList></attList><exemplum><eg><![CDATA[<titleStmt>
    <title>Capgrave's Life of St. John Norbert:  a machine-readable
         transcription</title>
    <respStmt>
         <resp>compiled by</resp> <name>P.J. Lucas</name>
    </respStmt>
</titleStmt>]]></eg></exemplum><remarks></remarks><part type="aux" name="hdr"/><classes/><dataDesc></dataDesc><elemDecl>- o ((title+, (author | editor
| sponsor | funder | principal
| respStmt)*))</elemDecl><xref target="HD21"/><xref target="HD2"/></tagDoc><?tei:EOF titstmt.tag ??><!-- titleStmt element --><?tei:SOF tns.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : note synonymy with GRAM                 --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tns.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** tns --><tagDoc id="TNS" usage="opt"><gi tei="yes">tns</gi><name>tense</name><desc>indicates the grammatical tense associated with a given inflected
form in a dictionary.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is synonymous with <tag compl="full" tei="yes">gram type=tense</tag>.</p></remarks><part type="base" name="dict"/><classes names="MORPH DIPARTS DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPFO"/></tagDoc><?tei:EOF tns.tag ??><!-- tns element --><?tei:SOF tr.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : change desc, remarks                    --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tr.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ***************************************************** tr --><tagDoc id="TR" usage="rwa"><gi tei="yes">tr</gi><name>translation equivalent</name><desc>contains a translation of the headword or an example.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>This element is provided as a convenient means to distinguish
translation equivalents from other methods of providing sense
information, in the cases where such a distinction is desired.  Where
no such distinction is desired, translation equivalents may be tagged
as <gi tei="yes">def</gi> or <gi tei="yes">gloss</gi> elements.</p></remarks><part type="base" name="dict"/><classes names="DIPARTS DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPTR"/></tagDoc><?tei:EOF tr.tag ??><!-- tr element --><?tei:SOF trailer.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	trailer.tag,v $
# Revision 1.3  94/03/15  11:10:47  lou
# minor typos etc
# 
# Revision 1.2  1994/01/04  12:15:40  lou
# fix xrefs
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************************trailer --><tagDoc id="TRAILER" usage="opt"><gi tei="yes">trailer</gi><name>trailer</name><desc>contains a closing title or footer appearing at the end of
a division of a text. </desc><attList></attList><exemplum><eg><![CDATA[<trailer>Explicit pars tertia</>]]></eg></exemplum><remarks></remarks><part type="base" name="core"/><classes names="DIVBOT"/><elemDecl>- O (%phrase.seq;)</elemDecl><xref target="DSCO"/><xref target="DSDTB"/></tagDoc><?tei:EOF trailer.tag ??><!-- trailer element --><?tei:SOF trans.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : Added class membership in diglobal      --><!-- 94-01-12 : MSM : m.dicparts                              --><!-- 94-01-12 : MSM : made file from old treq                 --><!-- 93-10-19 : MSM : rename te from tgt, id is treq          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	trans.tag,v $
# Revision 1.1  94/01/15  21:00:02  msmcq
# Initial revision
# 
# Revision 1.1  1994/01/04  01:25:19  msmcq
# Initial revision
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** te  --><tagDoc id="TRANS" usage="rec"><gi tei="yes">trans</gi><name>translation information</name><desc>contains translation text and related information (within an
entry in a multilingual dictionary).</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS DIGLOBAL"/><dataDesc>May contain character data mixed with any other elements
defined in the dictionary tag set.</dataDesc><elemDecl>- O  (%paraContent | %m.dictionaryParts)*</elemDecl><xref target="DITPTR" type="div2"/></tagDoc><?tei:EOF trans.tag ??><!-- trans element --><?tei:SOF tree.tag ??><!-- ********** TREE                                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tree.tag,v $
# Revision 1.4  93/09/22  19:22:23  msmcq
# change for publication of GD
# 
# Revision 1.3  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
# --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : change model:  eliminate &              --><!--                  allow root to be in middle as well as   --><!--                  at begin or end of tree                 --><!-- 93-09-15 : MSM : trivial cleanup                         --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version:                      --><!--                  add label=                              --><!-- eliminate special drawing attributes (use rend=)         --><!-- change description of ord= so that it cannot be          --><!-- overriden in ROOT or InODE tags.  If ord=partial, then   --><!-- ord= values must be specified on ROOT and every InODE.   --><!-- follow= attribute can however impose a "local"           --><!-- ordering between two elements in a tree.                 --><!-- ********** TREE                                          --><tagDoc id="TREE" usage="rwa"><gi tei="yes">tree</gi><desc>encodes a tree, which is made up of a root, internal nodes,
leaves, and arcs from root to leaves.</desc><attList><attDef id="TRLAB" usage="opt"><attName>label</attName><desc>gives a label for a tree.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef id="TRARITY" usage="opt"><attName>arity</attName><desc>gives the maximum number of children of the root and internal
nodes of the tree.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default></attDef><attDef id="TRORD" usage="req"><attName>ord</attName><desc>indicates whether or not the tree is ordered, or if it is
partially ordered.</desc><datatype>(Y | N | partial)</datatype><valList type="closed"><val>Y</val><desc>indicates that all of the branching nodes of the tree are ordered.</desc><val>partial</val><desc>indicates that some of the branching nodes of the tree are ordered
and some are unordered.</desc><val>N</val><desc>indicates that all of the branching nodes of the tree are
unordered.</desc></valList><default>Y</default></attDef><attDef id="TRORDER" usage="opt"><attName>order</attName><desc>gives the order of the tree, i.e., the number of its nodes.</desc><datatype>NUMBER</datatype><valDesc>A nonnegative integer.</valDesc><default>#IMPLIED</default><remarks><p>The size of a tree is always one less than its order, hence
there is no need for both a <att tei="yes">size</att> and <att tei="yes">order</att>
attribute.</p></remarks></attDef></attList><exemplum><eg><![CDATA[<tree n='ex2' ord=partial arity=2 order=13>
   <root label='/' id=DIV1 ord=Y children='plu1 exp1'>
   <iNode label='+' id=PLU1 ord=N parent=div1 children='exp2 exp3'>
   <iNode label='**' id=EXP1 ord=Y parent=div1 children='plu2 num2.3'>
   <iNode label='**' id=EXP2 ord=Y parent=plu1 children='vara1 num2.1'>
   <iNode label='**' id=EXP3 ord=Y parent=plu1 children='varb1 num2.2'>
   <iNode label='+' id=PLU2 ord=N parent=exp1 children='vara2 varb2'>
   <leaf label='a' id=VARA1 parent=exp2>
   <leaf label='2' id=NUM2.1 parent=exp2>
   <leaf label='b' id=VARB1 parent=exp3>
   <leaf label='2' id=NUM2.2 parent=exp3>
   <leaf label='a' id=VARA2 parent=plu2>
   <leaf label='b' id=VARB2 parent=plu2>
   <leaf label='2' id=NUM2.3 parent=exp1>
   </tree>]]></eg></exemplum><part type="top" name="graphs"/><classes names="CHUNK"/><dataDesc>A root, and zero or more internal nodes and leaves, but if
there is an internal node, there must also be at least one leaf.</dataDesc><elemDecl>- - ((leaf | iNode)*, root, (leaf | iNode)*)</elemDecl><xref target="GDTR" type="div2"/></tagDoc><?tei:EOF tree.tag ??><!-- tree element --><?tei:SOF triangle.tag ??><!-- ********** TRIANGLE                                      --><!-- $Id $--><!-- $Log:	triangle.tag,v $
# Revision 1.5  93/09/22  19:23:02  msmcq
# change for publication of GD
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/09  20:03:46  msmcq
# restore RCS id, log
# --><!-- Revisions:                                               --><!-- 93-09-17 : MSM : change desc of VALUE                    --><!-- 93-09-15 : MSM : trivial cleanup                         --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-07-23 : DTL : modify P2 version:                      --><!--                  replace LABEL and FS content by value=  --><!--                      and label=                          --><!--                  eliminate ECHO from content model       --><!-- ********** TRIANGLE                                      --><tagDoc id="TRIANGLE" usage="opt"><gi tei="yes">triangle</gi><name>Underspecified embedding tree, so called because of its
characteristic shape when drawn.</name><desc>provides for an underspecified <gi tei="yes">eTree</gi>, that is,
an <gi tei="yes">eTree</gi> with information left out.</desc><attList><attDef usage="opt"><attName>label</attName><desc>gives a label for an underspecified embedding tree.</desc><datatype>CDATA</datatype><valDesc>A character string.</valDesc><default>#IMPLIED</default></attDef><attDef usage="rwa"><attName>value</attName><desc>provides the value of a triangle, which is the SGML
identifier of a feature
structure or other analytic element.</desc><datatype>IDREF</datatype><valDesc>A valid identifier of a feature structure or other analytic
element.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<triangle label='NP'><eLeaf label='the periscope'></triangle>]]></eg></exemplum><part type="top" name="graphs"/><classes/><dataDesc>An optional label or feature structure followed by zero or
more embedding trees, triangles, or embedding leafs.</dataDesc><elemDecl>- - ((eTree | triangle | eLeaf)*)</elemDecl><xref target="GDAT" type="div2"/></tagDoc><?tei:EOF triangle.tag ??><!-- triangle element --><?tei:SOF tsd.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	tsd.tag,v $
# Revision 1.4  93/09/15  22:56:03  msmcq
# Changes as of mid-September
# 
# Revision 1.3  1993/09/08  23:42:47  msmcq
# Cosmetic changes
#
# Revision 1.2  1993/08/03  02:23:56  msmcq
# add &nil entity to fix premature recognition of end-tag
# --><!-- Revisions:                                               --><!-- 93-09-14 : MSM : add nil to example                      --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-05 : MSM : add nil entity to false end-tag for tagDoc --><!-- ************************************************** tsd --><tagDoc id="TSD" usage="req"><gi tei="yes">tsd</gi><name>tag set documentation</name><desc>contains a set of elements documenting an SGML tag set.</desc><attList></attList><exemplum><eg>  &lt;tsd&gt;
  &lt;tagDoc&gt; ... &lt;/tagDoc&gt;
  &lt;entDoc type=pe&gt; ... &lt;/entDoc&gt;
  &lt;tagDoc&gt; ... &lt;/tagDoc&gt;
  &lt;/tsd&gt;</eg></exemplum><remarks><p>This element is required.</p></remarks><part type="aux" name="tsd"/><classes/><dataDesc>Contains any mixture of <gi tei="yes">tagDoc</gi>, <gi tei="yes">entDoc</gi>, and
<gi tei="yes">classDoc</gi> elements.</dataDesc><elemDecl>- O  ((tagDoc | entDoc | classDoc)+)</elemDecl><xref target="TD" type="div1"/></tagDoc><?tei:EOF tsd.tag ??><!-- tsd element --><?tei:SOF u.tag ??><!-- add part attribute             --><!-- add overlap as value for TRANS --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    **
    * $Log: u.tag,v $
    * Revision 1.10  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.9  98/01/28  19:22:39  tei
    * LB changes of 1998-01
    * 
    * Revision 1.8  1994/04/01  17:41:18  msmcq
    * Changes while checking DTD
    * 
    * Revision 1.7  1994/02/17  21:06:08  msmcq
    * make WHO attribute inherit, as per text (for SC version of P3)
    * 
    * Revision 1.6  1994/01/04  12:15:41  lou
    * fix xrefs
    * 
    * Revision 1.5  1993/12/16  18:06:26  lou
    * improved wordingof trans attribute
    * 
    * Revision 1.4  1993/11/22  16:39:29  lou
    * changed content model; added end tag to example
    * 
    * Revision 1.1  1993/06/23  11:28:40  lou
    * Initial checkin
    *--><!-- Revisions:                                               --><!-- 4 feb 98 : LB : make WHO idrefs (not idref) again --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 94-02-14 : MSM : make who INHERITED                      --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ****************************************************** u --><tagDoc id="U" usage="req"><gi tei="yes">u</gi><name>utterance</name><desc>a stretch of speech usually preceded and followed by
silence or by a change of speaker.</desc><attList><attDef usage="opt"><attName>trans</attName><name>transition</name><desc>indicates the nature of the transition between this utterance
          and the previous one.</desc><datatype>(smooth | latching | overlap | pause)</datatype><valList type="open"><val>smooth</val><desc>this  utterance begins without unusual pause or rapidity.</desc><val>latching</val><desc>this utterance begins with a markedly shorter pause than normal.</desc><val>overlap</val><desc>this utterance begins before the previous one has finished.</desc><val>pause</val><desc>this utterance begins after a noticeable pause.</desc></valList><default>smooth</default><remarks></remarks></attDef><attDef usage="opt"><attName>who</attName><desc>supplies an identifier for the speaker or group of speakers.
         Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
         or <tag compl="full" tei="yes">participantGrp</tag> element in the TEI header.</desc><datatype>IDREFS</datatype><valDesc>Must identify a participant or participant group within the
        TEI Header</valDesc><default>%INHERITED</default></attDef><!--
<attDef usage=mwa><attName>part</attName>
<desc>specifies whether or not the utterance is complete. </desc>
<datatype>(Y | N | I | M | F)
<valList type=closed>
<val>Y<desc>the utterance is incomplete
<val>N<desc>either the utterance is complete, or no claim is made as to its
completeness
<val>I<desc>the initial part of an incomplete utterance
<val>M<desc>a medial part of an incomplete utterance
<val>F<desc>the final part of an incomplete utterance
</valList>
<default>N
<remarks><p>The values I, M, or F should be used only where it is
clear how the utterance is to be reconstituted.
</attDef>
--></attList><exemplum><eg><![CDATA[    <u who=A>if did you set</u>
    <u who=B trans=latching>well Joe and I set it between us</u>]]></eg></exemplum><remarks><p>Although individual transcriptions may consistently use
<gi tei="yes">u</gi> elements for turns or other units, and although in most
cases a <gi tei="yes">u</gi> will be delimited by pause or change of speaker,
<gi tei="yes">u</gi> is not required to represent a turn or any communicative
event, nor to be bounded by pauses or change of speaker.  At a minimum,
a <gi tei="yes">u</gi> is some phonetic production by a given speaker.</p></remarks><part type="base" name="ts"/><classes names="TIMED COMPSPOK DECLING"/><dataDesc>prose and a mixture of speech elements</dataDesc><elemDecl>- - ((%phrase|%m.comp.spoken)+)</elemDecl><xref target="TSBAFD"/><xref target="TSBAUT"/><xref target="TSBA"/></tagDoc><?tei:EOF u.tag ??><!-- u element --><?tei:SOF uncert.tag ??><!-- ************************************************************ --><!-- TAGDOC for UNCERTAIN                                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	uncert.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class singval                    --><!-- 93-09-22 : MSM : Extract from TDL group file             --><!-- TAGDOC for UNCERTAIN                                         --><!-- ************************************************************ --><tagDoc id="UNCERT" usage="rwa"><gi tei="yes">uncertain</gi><name>Uncertain value</name><desc>provides uncertainty value for a feature.</desc><attList></attList><exemplum><eg><![CDATA[<f name=gender><uncertain>]]></eg></exemplum><part type="top" name="fs"/><classes names="SINGVAL"/><dataDesc>Empty element.</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="FSBO" type="div3"/></tagDoc><?tei:EOF uncert.tag ??><!-- uncert         --><?tei:SOF unclear.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : add to class edit (fix UNCLEAR)         --><!-- 94-04-07 : MSM : full stop after etc                     --><!-- 94-02-28 : MSM : INHERITED is TEI keyword, not SGML      --><!-- 94-01-10 : MSM : correct typo in                         --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	unclear.tag,v $
# Revision 1.7  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.6  1994/08/29  15:25:03  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.5  1994/04/08  01:52:06  msmcq
    * Last fixes for FD in P3, etc.
    * 
    * Revision 1.4  1994/03/01  04:16:01  msmcq
    * fix slip on HAND att
    * 
    * Revision 1.3  1994/02/07  20:56:16  msmcq
    * revsisions for P3
    * 
    * Revision 1.2  1993/11/16  11:13:35  lou
    * moved to CO
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    *--><!-- ENTITY unclear  system 'unclear.tag' --><!-- unclear tag --><!-- 4 Jan 98 : LB : it's <gap>, not <omit> stupid!           --><!-- ************************************************ unclear --><tagDoc id="UNCLEAR" usage="opt"><gi tei="yes">unclear</gi><desc>contains a word, phrase, or passage which cannot be transcribed
with certainty because it is illegible or inaudible in the source.</desc><attList><!-- ................................................... reason --><attDef usage="opt"><attName>reason</attName><desc>indicates why the material is hard to transcribe.</desc><datatype>CDATA</datatype><valDesc>any phrase describing the difficulty, e.g. <q>faded</q>,
<q>ambient noise</q>, <q>passing truck</q>, <q>ill formed</q>,
<q>eccentric ductus</q>.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................. length --><!-- length attribute dropped PR 15/5/93                      --><!-- ................................................... resp --><attDef usage="opt"><attName>resp</attName><desc>indicates the individual responsible for the transcription of
the letter, word or passage contained with the <gi tei="yes">unclear</gi>
element.</desc><datatype>CDATA</datatype><valDesc>must be one of the identifiers declared in the document
header, associated with a person asserted as responsible for some
aspect of the text's creation, transcription, editing or encoding
(see chapter <xref target="CE"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... cert --><attDef usage="rec"><attName>cert</attName><name>certainty</name><desc>signifies the degree of certainty ascribed to the transcription
of the text contained within the <gi tei="yes">unclear</gi> element.</desc><datatype>CDATA</datatype><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... hand --><attDef usage="opt"><attName>hand</attName><desc>Where the difficulty in transcription arises from action
(partial deletion, etc.) assignable to an identifiable hand, signifies
the hand responsible for the action.</desc><datatype>IDREF</datatype><valDesc>must be one of the hand identifiers declared in the document
header (see section <xref target="PHDH"/>).</valDesc><default>%INHERITED</default><eg><![CDATA[ ]]></eg></attDef><!-- ................................................... agent --><attDef usage="opt"><attName>agent</attName><desc>Where the difficulty in transcription arises from an
identifiable cause, signifies the causative agent.</desc><datatype>CDATA</datatype><valDesc>any prose description of the agent.</valDesc><default>#IMPLIED</default><eg><![CDATA[ ]]></eg></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The same element is used for all cases of uncertainty in
the transcription of element content, whether for written or spoken
material.  For other aspects of certainty, uncertainty, and
reliability of tagging and transcription, see chapter <xref target="CE"/>.</p><p>The <gi tei="yes">damage</gi>, <gi tei="yes">gap</gi>, <gi tei="yes">del</gi>, <gi tei="yes">unclear</gi>
and <gi tei="yes">supplied</gi> elements may be closely allied in use.  See
section <xref target="PHCOMB"/> for discussion of which element is
appropriate for which circumstance.</p></remarks><part type="base" name="core"/><classes names="EDIT"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="PHDA"/><xref target="COEDADD"/></tagDoc><?tei:EOF unclear.tag ??><!-- unclear element --><?tei:SOF usg.tag ??><!-- Revisions:                                               --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	usg.tag,v $
# Revision 1.2  94/01/15  21:00:02  msmcq
# cmsmcq revisions for P3; see comments for details.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- **************************************************** usg --><tagDoc id="USG" usage="opt"><gi tei="yes">usg</gi><name>usage</name><desc>contains usage information in a dictionary entry.</desc><attList><!-- ................................................... type --><attDef usage="opt"><attName>type</attName><desc>classifies the usage information using any convenient typology.</desc><datatype>CDATA</datatype><valList type="open"><val>geo </val><desc>geographic area</desc><val>time </val><desc>temporal, historical era (<q>archaic</q>, <q>old</q>,
etc.)</desc><val>dom </val><desc>domain</desc><val>reg </val><desc>register</desc><val>style </val><desc>style (figurative, literal, etc.)</desc><val>plev </val><desc>preference level (<q>chiefly</q>, <q>usually</q>, etc.)</desc><val>lang </val><desc>lang (language for foreign words, spellings
pronunciations, etc.)</desc><val>gram </val><desc>grammatical usage</desc><val>syn </val><desc>synonym given to show use</desc><val>hyper </val><desc>hypernym given to show usage</desc><val>colloc </val><desc>collocation given to show usage</desc><val>comp </val><desc>typical complement</desc><val>obj </val><desc>typical object</desc><val>subj </val><desc>typical subject</desc><val>verb </val><desc>typical verb</desc><val>hint </val><desc>unclassifiable piece of information to guide sense choice</desc></valList><default>#IMPLIED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="base" name="dict"/><classes names="DITOPLEV DIPARTS FORMINFO GRAMINFO DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="DITPUS"/></tagDoc><?tei:EOF usg.tag ??><!-- usg element --><?tei:SOF val.tag ??><!-- Revisions:                                               --><!-- 93-09-10 : MSM : Normalize GI case                       --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	val.tag,v $
# Revision 1.5  94/01/04  12:15:42  lou
# fix xrefs
# 
# Revision 1.4  1993/09/15  22:56:03  msmcq
# Changes as of mid-September
#
# Revision 1.3  1993/09/08  23:43:27  msmcq
# Suppress internal query note, add sgmlkw class
#
# Revision 1.2  1993/08/13  20:50:14  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** val --><tagDoc id="VAL" usage="opt"><gi tei="yes">val</gi><name>value</name><desc>contains a single attribute value.</desc><attList></attList><exemplum><eg><![CDATA[	<val>unknown</val>]]></eg></exemplum><remarks></remarks><part type="aux" name="tsd"/><classes names="SGMLKW"/><dataDesc></dataDesc><elemDecl>- O (#PCDATA)</elemDecl><xref target="TD"/><xref target="TDATT"/></tagDoc><?tei:EOF val.tag ??><!-- val element --><?tei:SOF valdesc.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : uppercase omissibility                  --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	valdesc.tag,v $
# Revision 1.3  93/09/16  16:22:01  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:50:15  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** valDesc --><tagDoc id="VALDESC" usage="rwa"><gi tei="yes">valDesc</gi><name>value description</name><desc>specifies any semantic or syntactic constraint on the value that
an attribute may take, additional to the information carried by the
<gi tei="yes">datatype</gi> element.</desc><attList></attList><exemplum><eg><![CDATA[ <valDesc>must point to another <gi>align</gi>
    element logically preceding this
    one.</valDesc>]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc>contains any sequence of phrase level elements or pcdata</dataDesc><elemDecl>- O (%phrase.seq)</elemDecl><!-- was soup --><xref target="TDATT"/></tagDoc><?tei:EOF valdesc.tag ??><!-- valDesc element --><?tei:SOF vallist.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-11 : MSM : change desc on type semi                --><!-- 93-09-10 : MSM : valList type closed                     --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vallist.tag,v $
# Revision 1.3  93/09/16  16:22:01  msmcq
# Publication of TD
# 
# Revision 1.2  1993/08/13  20:50:15  msmcq
# Clean ^Z
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- *************************************************** valList --><tagDoc id="VALLIST" usage="mwa"><gi tei="yes">valList</gi><name>value list</name><desc>contains a list of value and description pairs for an attribute.</desc><attList><attDef usage="opt"><attName>type
 </attName><desc>specifies the extensibility of the list of attribute values
 specified.
 </desc><datatype>(closed | semi | open)
 </datatype><valList type="closed"><val>closed</val><desc>only the values specified are permitted.
  </desc><val>semi</val><desc>all the values specified should be supported, but
   other values are legal and software should have appropriate
   fallback processing for them.
  </desc><val>open</val><desc>the values specified are sample values only.
 </desc></valList><default>open
 </default></attDef></attList><exemplum><eg><![CDATA[ <valList>
  <val>req<desc>required
  <val>mwa<desc>mandatory when applicable
  <val>rec<desc>recommended
  <val>rwa<desc>recommended when applicable
  <val>opt<desc>optional
 </valList>]]></eg></exemplum><part type="aux" name="tsd"/><classes/><dataDesc></dataDesc><elemDecl> - - ((val,desc)*)</elemDecl><xref target="TDATT"/></tagDoc><?tei:EOF vallist.tag ??><!-- valList element --><?tei:SOF valt.tag ??><!-- ************************************************************ --><!-- TAGDOC for VALT                                              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	valt.tag,v $
# Revision 1.4  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.3  1994/01/04  01:26:21  msmcq
# revise content model
#
# Revision 1.2  1993/09/23  02:38:58  msmcq
# Unpacked TDL changes of July 93
# --><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add to class cplxval                    --><!-- 94-04-07 : MSM : comment out remarks                     --><!-- 94-01-03 : MSM : change elemdecl:  dft, not default      --><!-- 93-09-22 : MSM : extract from group tagdoc               --><!-- ************************************************************ --><tagDoc id="VALT" usage="rwa"><gi tei="yes">vAlt</gi><name>Value alternation</name><desc>provides alternative (disjunctive) values for a feature.</desc><attList><attDef id="VALTME" usage="opt"><attName>mutExcl</attName><desc>indicates whether values are mutually exclusive.</desc><datatype>(Y|N)</datatype><valList type="closed"><val>Y      </val><desc>indicates that the values are mutually exclusive.
   </desc><val>N      </val><desc>indicates that the values are not mutually exclusive.</desc></valList><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<vAlt mutExcl=Y><sym value=masculine><sym value=neuter></vAlt>]]></eg></exemplum><!-- <remarks><p>The content model is given as ((%sVal;),     --><!-- (%sVal;)+) in FS3.dtd.  The entity %sVal; is defined     --><!-- as "%bVal; | %dVal;".                                    --><!-- %bVal; is defined as "%aVal; | null".                    --><!-- %aVal; is defined as "plus | minus | any | none | dft    --><!-- | uncertain".                                            --><!-- %dVal; is defined as "%cVal; | fs".                      --><!-- %cVal; is defined as "sym | nbr | msr | rate | str |     --><!-- vAlt".                                                   --><part type="top" name="fs"/><classes names="CPLXVAL"/><dataDesc>Two or more feature values.</dataDesc><elemDecl>- - ((plus | minus | any | none | dft | uncertain | null |
sym | nbr | msr | rate | str | vAlt | fs), (plus | minus | any | none |
dft | uncertain | null | sym | nbr | msr | rate | str | vAlt | fs)+)</elemDecl><xref target="FSAL" type="div3"/></tagDoc><?tei:EOF valt.tag ??><!-- vAlt           --><?tei:SOF varencod.tag ??><!-- Revisions:                                               --><!-- 94-03-29 : MSM : suppress reminder to document this in HD --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	varencod.tag,v $
# Revision 1.2  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY varencod system 'varencod.tag' --><!--
variant.encoding tag --><!-- *************************************** variantEncoding --><tagDoc id="VARENCOD" usage="mwa"><gi tei="yes">variantEncoding</gi><desc>declares the method used to encode text-critical variants.</desc><attList><!-- ................................................. method --><attDef usage="req"><attName>method</attName><desc>indicates which method is used to encode the apparatus of
variants.</desc><datatype>(location-referenced | double-end-point |
parallel-segmentation)</datatype><valList type="closed"><val>location-referenced</val><desc>apparatus uses line numbers or other canonical reference scheme
referenced in a base text.</desc><val>double-end-point</val><desc>apparatus indicates the precise locations of the beginning and
ending of each lemma relative to a base text.</desc><val>parallel-segmentation</val><desc>alternate readings of a passage are given in parallel in the
text; no notion of a base text is necessary.</desc></valList><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p>The value <q>parallel-segmentation</q> requires in-line
encoding of the apparatus.</p></remarks></attDef><!-- ............................................... location --><attDef usage="req"><attName>location</attName><desc>indicates whether the apparatus appears within the running text
or
external to it.</desc><datatype>(internal | external)</datatype><valList type="closed"><val>internal </val><desc>apparatus appears within the running text.</desc><val>external </val><desc>apparatus appears outside the base text.</desc></valList><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p>The value <q>external</q> is inconsistent with the
parallel-segmentation method of apparatus markup.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ <variant.encoding method='location-referenced'
                   location='external'>]]></eg></exemplum><part type="base" name="hdr"/><classes/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="TCAPEN"/></tagDoc><?tei:EOF varencod.tag ??><!-- variantEncoding element --><?tei:SOF vdft.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : use m.featureVal in model               --><!-- 94-04-07 : MSM : use m.featureVal not singval            --><!-- 94-04-06 : MSM : suppress remarks elements as needed     --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vdft.tag,v $
# Revision 1.3  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.2  1994/04/07  02:49:28  msmcq
# Misc. cleanups (mostly suppressed remarks)
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY vdft system     'vdft.tag' --><!-- vdefault tag --><!-- ************************************************ vDefault --><tagDoc id="VDFT" usage="opt"><gi tei="yes">vDefault</gi><name>value default</name><desc>declares the default value to be supplied when a feature structure
does not contain an instance of <gi tei="yes">f</gi> for this name; if
unconditional, it is specified as one (or, depending on the value of
the <att tei="yes">org</att> attribute of the enclosing <gi tei="yes">fDecl</gi>) more
<gi tei="yes">fs</gi> elements or primitive values;
if conditional, it is specified as
one or more <gi tei="yes">if</gi> elements; if no default is specified, or no
condition matches, the value <gi tei="yes">none</gi> is assumed.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><!-- <remarks><p>[Is first plus in model correct?             --><!-- -MSM]</remarks>                                          --><part type="aux" name="fsd"/><classes/><dataDesc>May contain a legal feature value, or a series of <gi tei="yes">if</gi>
elements.</dataDesc><elemDecl>- - ((%m.featureVal)+ | if+)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF vdft.tag ??><!-- vDefault element --><?tei:SOF vername.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vername.tag,v $
# Revision 1.1  93/06/23  11:28:40  lou
# Initial checkin
#  --><!-- ************************************************************** vername --><tagDoc id="VERNAME" usage="mwa"><gi tei="yes">%version</gi><name>version name</name><desc>serves as the root element for a concurrent markup stream which
will be used to mark page and line numbers of a reference edition of the
text.</desc><attList></attList><exemplum><eg><![CDATA[ <!DOCTYPE TEI.2 system 'tei2.dtd' >
 <!DOCTYPE La    system 'teip2.dtd' [
        <!ENTITY % version 'La'>
 ]>
 <(TEI.2)TEI.2><(La)La>
 <(TEI.2)TEI.Header> ...
 </(TEI.2)TEI.Header>
 <(TEI.2)text>
 <(La)page n='[1]'>
   ...
 <(La)page n='4'>
   ...
 <(La)page n='5'>
   ...
 </(TEI.2)text>
 </(La)La>
 </(TEI.2)TEI.2>]]></eg></exemplum><remarks><p>The version name should be short (one or two characters), as
it must be prefixed to all page and line tags in the concurrent markup
stream.</p></remarks><part type="base" name="print"/><classes/><dataDesc>May contain character data, <gi tei="yes">vol</gi>, and <gi tei="yes">page</gi>
elements.</dataDesc><elemDecl>- -  (#PCDATA | page | vol)*</elemDecl><xref target="CORS" type="div3"/></tagDoc><?tei:EOF vername.tag ??><!--%version element --><?tei:SOF view.tag ??><!-- Revisions:                                               --><!-- 93-08-19 : MSM : suppress + in model                     --><!-- 93-08-19 : MSM : change class to stagedir                --><!-- 93-08-19 : MSM : change model to specialPara, like stage --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	view.tag,v $
# Revision 1.5  94/01/04  12:15:42  lou
# fix xrefs
# 
# Revision 1.4  1993/08/23  16:15:54  msmcq
# fixes for publication of DR
#
# Revision 1.3  1993/08/13  20:50:16  msmcq
# Clean ^Z
#
# Revision 1.2  1993/08/12  21:33:20  msmcq
# Rev. for publication of DR
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ********************************** VIEW --><tagDoc id="VIEW" usage="opt"><gi tei="yes">view</gi><desc>describes the visual context of some part of a screen play in
terms of what the spectator sees, generally independent of any
dialogue.</desc><attList></attList><exemplum><eg><![CDATA[<view><name>Max</name> joins his daughter
at the window. <hi>Rain</hi> sprays his
face-- </view>
<view><camera>Max's POV</camera> He sees occasional
windows open, and just across from his apartment
house, a <hi>man</hi> opens the front door of
a brownstone--</view>]]></eg></exemplum><exemplum><eg><![CDATA[<div type=shot>
  <view>BBC World symbol</view>
  <sp who=MP><speaker>Voice Over</speaker>
     <p>Monty Python's Flying Circus tonight comes to you live
     from the Grillomat Snack Bar, Paignton.
</div>
<div type=shot>
  <view>Interior of a nasty snack bar. Customers around, preferably
  real people. Linkman sitting at one of the plastic tables.</view>
  <sp who=JC><speaker>Linkman</speaker>
  <p>Hello to you live from the Grillomat Snack Bar.
  <!-- ... -->
</div>]]></eg></exemplum><remarks><p>A view is a particular form of stage direction.</p></remarks><part type="base" name="perf"/><classes names="STAGEDIR"/><dataDesc>text and crystals</dataDesc><elemDecl>- O (%specialPara)</elemDecl><xref target="DRTEC"/><xref target="DROTH" type="div3"/></tagDoc><?tei:EOF view.tag ??><!-- view element --><?tei:SOF vocal.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vocal.tag,v $
# Revision 1.5  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.4  1994/02/17  21:06:08  msmcq
# make WHO attribute inherit, as per text (for SC version of P3)
#
# Revision 1.3  1994/01/04  12:15:43  lou
# fix xrefs
#
# Revision 1.2  1993/09/21  11:07:47  lou
# added to spoken class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 94-02-14 : MSM : make who INHERITED                      --><!-- 94-02-14 : MSM : change desc                             --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************** vocal --><tagDoc id="VOCAL" usage="rec"><gi tei="yes">vocal</gi><name>Vocalized semi-lexical</name><desc>any vocalized but not necessarily lexical phenomenon, for example
voiced pauses, non-lexical backchannels, etc.</desc><attList><attDef usage="opt"><attName>who</attName><desc>supplies an identifier for the vocalist(s).
         Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
         or <tag compl="full" tei="yes">participant.grp</tag> element in the TEI header.</desc><datatype>IDREF</datatype><valDesc>Must identify a participant or participant group within the
       TEI Header</valDesc><default>%INHERITED</default></attDef><attDef usage="opt"><attName>iterated</attName><name>iterated</name><desc>indicates whether or not the phenomenon is repeated.</desc><datatype>(y | n | u)</datatype><valList type="open"><val>y </val><desc>the phenomenon is repeated.
    </desc><val>n </val><desc>the phenomenon is atomic.
    </desc><val>u </val><desc>unknown or unmarked.
   </desc></valList><default>n</default></attDef><attDef usage="opt"><attName>desc</attName><name>description</name><desc>supplies a conventional representation for the phenomenon.
    </desc><datatype>CDATA</datatype><valDesc>a description or representation of the phenomenon
        chosen from a semi-closed list</valDesc><default>#IMPLIED</default><remarks></remarks></attDef></attList><exemplum><eg><![CDATA[    <vocal dur=12 desc=whistles>]]></eg></exemplum><remarks></remarks><part type="base" name="ts"/><classes names="COMPSPOK TIMED"/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="TSBAFD"/><xref target="TSBAVO"/><xref target="TSBA"/></tagDoc><?tei:EOF vocal.tag ??><!-- vocal element --><?tei:SOF plvol.tag ??><!-- Revisions:                                               --><!-- 93-09-14 : MSM : Normalize GI case                       --><!-- 93-09-13 : MSM : drop dot in id                          --><!-- 93-09-13 : MSM : xref was cors3, now NHrs                --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	plvol.tag,v $
# Revision 1.2  93/09/16  16:16:16  msmcq
# Change ID, change xref, cosmetic
# 
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- ******************************************************* plvol --><tagDoc id="PLVOL" usage="opt"><gi tei="yes">vol</gi><name>volume</name><desc>marks the individual volumes of a reference edition.</desc><attList></attList><exemplum><eg><![CDATA[    <(La)vol  n=2>  ... [text of edition La, volume 2]
    <(La)page n=32> ... [text of edition La, vol. 2, page 32]
    <(La)page n=32> ... [text of edition La, vol. 2, page 33]
    <(La)page n=32> ... [text of edition La, vol. 2, page 34]
    <(La)page n=32> ... [text of edition La, vol. 2, page 35]]]></eg></exemplum><remarks><p>The <gi tei="yes">vol</gi> may be used if the reference edition has
more than one volume; otherwise it need not be used.  Any data contained
within a <gi tei="yes">vol</gi> element but not within a <gi tei="yes">page</gi> element is
assumed not to appear in the edition from which the reference scheme
derives.</p></remarks><part type="base" name="print"/><classes/><dataDesc>May contain character data and <gi tei="yes">page</gi> elements.</dataDesc><elemDecl>- -  (#PCDATA | page)*</elemDecl><xref target="NHRS" type="div3"/></tagDoc><?tei:EOF plvol.tag ??><!-- vol tag (in PL tag set) --><?tei:SOF vrange.tag ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : use featureVal not singVal              --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	vrange.tag,v $
# Revision 1.2  94/04/08  01:52:06  msmcq
# Last fixes for FD in P3, etc.
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY vrange system   'vrange.tag' --><!-- vrange tag --><!-- ********************************************** vRange --><tagDoc id="VRANGE" usage="mwa"><gi tei="yes">vRange</gi><name>value range</name><desc>defines the range of allowed values for a feature, in the form of
an <gi tei="yes">fs</gi>, <gi tei="yes">vAlt</gi>, or primitive value;
for the value of an <gi tei="yes">f</gi> to be valid, it must be
<term>subsumed</term> by the specified range; if the <gi tei="yes">f</gi>
contains multiple values (as sanctioned by the <att tei="yes">org</att> attribute),
then each value must be subsumed by the <gi tei="yes">vRange</gi>.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p></p></remarks><part type="aux" name="fsd"/><classes/><dataDesc>May contain any legal feature-value specification.</dataDesc><elemDecl>- O  (%m.featureVal)</elemDecl><xref target="FD"/></tagDoc><?tei:EOF vrange.tag ??><!-- vRange element --><?tei:SOF w.tag ??><!-- ****************************************************** w --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	w.tag,v $
# Revision 1.3  94/02/27  15:55:53  lou
# Revisions for publication of AI
# 
# Revision 1.2  1993/11/26  18:22:05  msmcq
# revision pre-publication of AI
#
# Revision 1.1  1993/09/23  02:36:34  msmcq
# Unpacked TDL changes July 93
# --><!-- Revisions:                                               --><!-- 93-11-15 : MSM : fix unmatched paren in content model    --><!-- 93-09-22 : MSM : change datadesc, class membershiop      --><!-- 93-07-22 : DTL : create                                  --><!--                                                          --><!-- ****************************************************** w --><tagDoc id="W" usage="opt"><gi tei="yes">w</gi><name>word</name><desc>represents a grammatical (not necessarily orthographic) word.</desc><attList><attDef usage="opt"><attName>lemma</attName><desc>identifies the word's lemma (dictionary entry form).</desc><datatype>CDATA</datatype><valDesc>a string of characters representing the spelling of the word's
dictionary entry form.</valDesc><default>#IMPLIED</default></attDef></attList><exemplum><eg><![CDATA[<w type=verb lemma=hit>hitt<m type=suffix>ing</m></w>]]></eg></exemplum><part type="top" name="ana"/><classes names="CLSEG"/><dataDesc>May contain character data and
<gi tei="yes">seg</gi>, <gi tei="yes">w</gi>, <gi tei="yes">m</gi> and <gi tei="yes">c</gi>
elements.</dataDesc><elemDecl>- - ((#PCDATA | seg | w | m | c)*)</elemDecl><xref target="AILC"/></tagDoc><?tei:EOF w.tag ??><!-- w element --><?tei:SOF week.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	week.tag,v $
# Revision 1.4  94/03/15  11:10:48  lou
# minor typos etc
# 
# Revision 1.3  1994/03/07  16:12:36  lou
# revisions for publication?
#
# Revision 1.2  1993/08/02  21:55:45  msmcq
# fix ]]> problem
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- week--><tagDoc id="WEEK" usage="opt"><gi tei="yes">week</gi><name>week</name><desc>the week component of a structured date.</desc><attList></attList><exemplum><eg><![CDATA[<title>Le Vieux Cordelier: Journals redige par Camille Desmoulins</title>,
<dateStruct type=Revolutionary value='03-02-1794'>
<day type=name>Quintidi</day> 
<month>Pluviose</month> 
<week value='2'>2e decade</week>, 
<year>l'an 2 de la Republique Indivicible</year>
</dateStruct>]]></eg></exemplum><remarks></remarks><part type="top" name="ND"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF week.tag ??><!-- week element --><?tei:SOF when.tag ??><!-- $Id: --><!-- Log: *
     *
--><!-- Revisions:
4 feb 98: LB : -1 is not legal value for NUTOKEN. Changed declared
value of INTERVAL to CDATA (marginally preferable to inventing special
value)
    
93-07-22 : DTL : based on P2 definition of LOC, but making
                  it empty rather than having PTRs as content
                 change distance= to interval=
                 include unit= in case various unit time values need
                  to be used (formerly specified on ALIGN only, as
                  units=)
                 modify interpretation of missing since= attribute
                 require ID attribute (WHEN is like ANCHOR)
                                                              --><tagDoc id="WHEN" usage="opt"><gi tei="yes">when</gi><name>when</name><desc>indicates a point in time either relative to other elements in the
same <gi tei="yes">timeline</gi> tag, or absolutely.</desc><attList><attDef usage="rwa"><attName>absolute</attName><desc>supplies an absolute value for the time.</desc><datatype>CDATA</datatype><valDesc>Times may be given in standard form, as specified in the
Encoding Declarations section of the header.</valDesc><default>#IMPLIED</default><remarks><p>Required for the element designated as the value of the
<att tei="yes">origin</att> attribute in the <tag compl="full" tei="yes">timeline</tag> tag.</p></remarks></attDef><attDef usage="rwa"><attName>unit</attName><desc>specifies the unit of time corresponding to the <att tei="yes">interval</att>
value.</desc><datatype>NMTOKEN</datatype><valDesc>a semi-closed list of recognized time units such as
<q>millisecond</q>, <q>second</q>, <q>minute</q></valDesc><default>%INHERITED;</default></attDef><attDef usage="rwa"><attName>interval</attName><desc>specifies the numeric portion of a time interval</desc><datatype>CDATA</datatype><valDesc>-1 or any positive number</valDesc><default>%INHERITED;</default><remarks><p>The value -1 indicates uncertainty about the interval.</p></remarks></attDef><attDef usage="rwa"><attName>since</attName><desc>identifies the reference point for determining the time of the
current <gi tei="yes">when</gi> element, which is obtained by adding the interval to the
time of the reference point.</desc><datatype>IDREF</datatype><valDesc>Should point to another <gi tei="yes">when</gi> element in the same
<gi tei="yes">timeline</gi>.</valDesc><default>#IMPLIED</default><remarks><p>If this attribute is omitted, and the <att tei="yes">absolute</att>
attribute is not specified, then the reference point is understood to be
the origin of the enclosing <gi tei="yes">timeline</gi> tag.</p></remarks></attDef><attDef usage="req"><attName>id</attName><desc>supplies an identifier, unique to the document, for each
<gi tei="yes">when</gi> element.</desc><datatype>ID</datatype><valDesc>any valid name</valDesc><default>#REQUIRED</default><remarks><p><!--There's an entity for this, no? --></p></remarks></attDef></attList><exemplum><eg><![CDATA[<when id=W3 since=w2 interval=20>]]></eg></exemplum><part type="top" name="link"/><classes/><dataDesc>empty</dataDesc><elemDecl>- O EMPTY</elemDecl><xref target="SASYMP" type="div3"/></tagDoc><?tei:EOF when.tag ??><!-- when element --><?tei:SOF wit.tag ??><!-- Revisions:                                               --><!-- 94-02-03 : MSM : rename old wits element as wit          --><!-- 94-01-25 : MSM : change remarks                          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: wit.tag,v $
    * Revision 1.3  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.2  94/02/07  20:56:16  msmcq
    * revsisions for P3
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    * --><!-- *************************************************** wit --><tagDoc id="WIT" usage="rwa"><gi tei="yes">wit</gi><desc>contains a list of one or more sigla of witnesses attesting a
given reading, in a textual variation.</desc><attList></attList><exemplum><eg><![CDATA[  <rdg wit='El Hg'>Experience</> <wit>El Hg</>]]></eg></exemplum><remarks><p>This element duplicates the information present in the
<att tei="yes">wit</att> attribute of the reading; it may be used to record the
exact form of the sigla given in the source edition, when that is of
interest.</p></remarks><part type="top" name="tc"/><classes/><dataDesc>May contain anything that can appear within a paragraph.</dataDesc><elemDecl>- O  (%paraContent;)</elemDecl><xref target="TCAPLW"/></tagDoc><?tei:EOF wit.tag ??><!-- wit element --><?tei:SOF witdtl.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of NOTES        --><!-- 94-02-03 : MSM : level 'sigils' to 'sigla'               --><!-- 94-01-25 : MSM : add some of NOTE's atts                 --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: witdtl.tag,v $
    * Revision 1.4  1998/02/05 17:15:38  tei
    * fix log message; make examples parse
    *
    * Revision 1.3  94/08/29  15:25:03  msmcq
    * Changes for unreachability bugs
    * 
    * Revision 1.2  1994/02/07  20:56:16  msmcq
    * revsisions for P3
    * 
    * Revision 1.1  1993/08/03  02:27:04  msmcq
    * tagdoc files:  resynching uicvm and onions
    * --><!-- ENTITY witDetail system 'witdetail.tag' --><!-- 4 feb 98 : LB : add RESP attribute --><!-- ************************************************ witDetail --><tagDoc id="WITDTL" usage="rwa"><gi tei="yes">witDetail</gi><desc>gives further information about a particular witness, or
witnesses, to a particular reading.</desc><attList><!-- ................................................. target --><attDef usage="req"><attName>target</attName><desc>indicates the identifier for the reading, or readings, to which
the witness detail refers.</desc><datatype>IDREFS</datatype><valDesc>the identifier of the reading or readings.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg></attDef><attDef usage="opt"><attName>resp</attName><name>responsibility</name><desc>identifies the individual responsible for  identifying the
witness</desc><datatype>CDATA</datatype><valDesc>any string of characters, typically the initials of the
individual involved, or a role identifier like <q>editor</q> if not
known by name.</valDesc><default>#IMPLIED</default><eg></eg></attDef><!-- ............................................... wit --><attDef usage="req"><attName>wit</attName><desc>indicates the sigil or sigla for the witnesses to which the
detail refers.</desc><datatype>CDATA</datatype><valDesc>the identifier of the sigil or sigla.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p>In local encoding schemes, the value of the
<att tei="yes">wit</att> attribute can be enforced as IDREFS, such that only
witnesses referred to in a <gi tei="yes">witList</gi> element may be the
subject of a <gi tei="yes">witDetail</gi>.</p></remarks></attDef><attDef usage="opt"><attName>type</attName><desc>describes the type of information given about the witness.</desc><datatype>CDATA</datatype><valDesc>Values can be taken from any convenient typology of annotation
suitable to the work in hand;  e.g. letter form, ornament, ...</valDesc><default>#IMPLIED</default></attDef><attDef usage="opt"><attName>place</attName><desc>indicates where the note appears in the source text.</desc><datatype>CDATA</datatype><valDesc>As for the <gi tei="yes">note</gi> element.</valDesc><default>'apparatus'</default><eg></eg><remarks><p>For pages with multiple apparatus, values such as
<term>app1</term> and <term>app2</term> can be used.</p><p>The <att tei="yes">place</att> attribute can be used to indicate to text
formatting software where a note should be printed.  If the locations
indicated do not agree with those in the copy text, that fact should be
indicated in the TEI header.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The <gi tei="yes">witDetail</gi> element should be regarded as a
specialized type of <gi tei="yes">note</gi> element; it is synonymous with
<tag compl="full" tei="yes">note type='witness detail'</tag>.  It differs from the general
purpose <gi tei="yes">note</gi> in the omission of some attributes seldom applicable to
notes within critical apparatus, and in the provision of the
<att tei="yes">wit</att> attribute, which
permits an application to extract all
annotation concerning a particular witness or witnesses from the
apparatus.</p></remarks><part type="top" name="tc"/><classes names="NOTES"/><dataDesc></dataDesc><elemDecl>- O (%paraContent)</elemDecl><xref target="TCAPLL"/></tagDoc><?tei:EOF witdtl.tag ??><!-- witDetail element --><?tei:SOF witend.tag ??><!-- Revisions:                                               --><!-- 94-03-29 : MSM : add to class fragment                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	witend.tag,v $
# Revision 1.2  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY witend   system 'witend.tag' --><!-- witness.end
tag --><!-- ******************************************** witness.end --><tagDoc id="WITEND" usage="opt"><gi tei="yes">witEnd</gi><desc>indicates the end, or suspension, of the text of a fragmentary
witness.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p> (optional)</p></remarks><part type="top" name="tc"/><classes names="FRAGMENT"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="TCAPMI"/></tagDoc><?tei:EOF witend.tag ??><!-- witEnd element --><?tei:SOF witlist.tag ??><!-- Revisions:                                               --><!-- 94-08-04 : MSM : fix REACH:  make member of CHUNK        --><!-- 94-03-03 : MSM : change child's name to WITNESS          --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	witlist.tag,v $
# Revision 1.2  94/08/29  15:25:03  msmcq
# Changes for unreachability bugs
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY witlist  system 'witlist.tag' --><!-- witList tag --><!-- ************************************************ witList --><tagDoc id="WITLIST" usage="rwa"><gi tei="yes">witList</gi><name>witness list</name><desc>contains a list of all the witnesses referred to in
<gi tei="yes">wit</gi> elements or <att tei="yes">wit</att> attributes
within the critical apparatus.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The provision of a <gi tei="yes">witList</gi> element simplifies
the automatic processing of the apparatus, e.g. the reconstruction
of the readings for all witnesses from an exhaustive apparatus.</p><p>Situations commonly arise where there are many more or less
fragmentary witnesses, such that there may be quite distinct groups
of witnesses for different parts of a text or collection of texts.
One may treat this with distinct <gi tei="yes">witList</gi> elements for each
different part.  Alternatively, one may have a single
<gi tei="yes">witList</gi> element at the beginning of the file listing all the
witnesses, partial and complete, for the text, with the attestation
of fragmentary witnesses indicated within the apparatus by use of the
<gi tei="yes">witStart</gi> and <gi tei="yes">witEnd</gi> elements described in section<xref target="TCAPMI"/>
.</p></remarks><part type="top" name="tc"/><classes names="CHUNK"/><dataDesc>May contain a series of <gi tei="yes">witness</gi> elements.
 </dataDesc><elemDecl>- O (witness+)</elemDecl><xref target="TCAPLL"/></tagDoc><?tei:EOF witlist.tag ??><!-- witList element --><?tei:SOF witness.tag ??><!-- Revisions:                                               --><!-- 94-02-03 : MSM : rename wit tag as witness               --><!-- 94-01-25 : MSM : added included attribute                --><!-- 94-01-25 : MSM : rename sigil att (was id)               --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	witness.tag,v $
# Revision 1.2  94/04/07  16:34:10  msmcq
# supply full stop at end of desc
# 
# Revision 1.1  1994/02/07  20:56:16  msmcq
# Initial revision
#
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- scrapped old-style wit tag, PR 25/5/93 --><!-- ENTITY wit  system 'wit.tag' --><!-- wit tag --><!-- ************************************************ witness --><tagDoc id="WITNESS" usage="rwa"><gi tei="yes">witness</gi><desc>contains either a description of a single witness referred to
within the critical apparatus, or a list of witnesses which is to be
referred to by a single sigil.</desc><attList><!-- ............................................... sigil --><attDef usage="req"><attName>sigil</attName><desc>indicates the sigil for one witness or for one group of
witnesses to which readings are assigned in a critical apparatus.</desc><datatype>CDATA</datatype><valDesc>the identifier to be used for this witness or witness group
in the <att tei="yes">wit</att> attribute of readings in the apparatus.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p>In local encoding schemes, the value of the <att tei="yes">id</att>
attribute can be used as the sigil, and the declared value of the
<att tei="yes">wit</att> attribute may be changed to IDREF, so as to ensure that
only witnesses referred to in a <gi tei="yes">witness</gi> element contained
within a <gi tei="yes">witList</gi> may occur in the value of any <att tei="yes">wit</att>
attribute on a reading element within an apparatus.</p></remarks></attDef><!-- ............................................... included --><attDef usage="mwa"><attName>included</attName><desc>indicates which other witnesses are included in a witness group.</desc><datatype>CDATA</datatype><valDesc>a blank-delimited list of sigla.</valDesc><default>''</default><eg><![CDATA[  <witness sigil='B'>
  <witness sigil='k'>
  <witness sigil='I'>
  <witness sigil='C*' included='B k I'>]]></eg><!-- need better example --><remarks><p>The <att tei="yes">included</att> attribute applies only in the case
of witness groups; if no value is given,
the <gi tei="yes">witness</gi> element is held to refer to a single witness rather
than a group.</p></remarks></attDef></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p>The content of the <gi tei="yes">witness</gi> element may give
bibliographic information about the witness or witness group, or it
may be empty.</p></remarks><part type="top" name="tc"/><classes/><elemDecl>- O (%paraContent)</elemDecl><xref target="TCAPLL"/></tagDoc><?tei:EOF witness.tag ??><!-- witness element --><?tei:SOF witstart.tag ??><!-- Revisions:                                               --><!-- 94-03-29 : MSM : add to class fragment                   --><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	witstart.tag,v $
# Revision 1.2  94/04/01  17:41:18  msmcq
# Changes while checking DTD
# 
# Revision 1.1  1993/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
# --><!-- ENTITY witstart system 'witstart.tag' --><!-- witness.start
tag --><!-- ****************************************** witness.start --><tagDoc id="WITSTART" usage="opt"><gi tei="yes">witStart</gi><desc>indicates the beginning, or resumption, of the text of a
fragmentary witness.</desc><attList></attList><exemplum><eg><![CDATA[ ]]></eg></exemplum><remarks><p> (optional)</p></remarks><part type="top" name="tc"/><classes names="FRAGMENT"/><dataDesc>Empty.</dataDesc><elemDecl>- O  EMPTY</elemDecl><xref target="TCAPMI"/></tagDoc><?tei:EOF witstart.tag ??><!-- witStart element --><?tei:SOF writing.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log:	writing.tag,v $
# Revision 1.7  98/01/28  19:22:39  tei
# LB changes of 1998-01
# 
    * Revision 1.6  1994/04/01  17:41:18  msmcq
    * Changes while checking DTD
    * 
    * Revision 1.5  1994/02/17  21:06:08  msmcq
    * make WHO attribute inherit, as per text (for SC version of P3)
    *--><!-- Revisions:                                               --><!-- 94-03-29 : MSM : member of compspok, not spoken          --><!-- 94-02-14 : MSM : make who INHERITED                      --><!-- 09 Aug 93: change content model to specialPara --><!-- 93-02-10 : MSM : change target of xref                   --><!-- ************************************************ writing --><tagDoc id="WRITING" usage="rec"><gi tei="yes">writing</gi><name>Writing</name><desc>a passage of written text revealed to participants in the course
of a spoken text.</desc><attList><attDef usage="rwa"><attName>who</attName><name>who</name><desc>supplies an identifier for the participant who reveals or
    creates the writing, if any.
    Its value is the identifier of a <tag compl="full" tei="yes">participant</tag>
    or <tag compl="full" tei="yes">participant.grp</tag> element in the TEI header.</desc><datatype>IDREF</datatype><valDesc>Must identify a participant or participant group within the
       TEI Header</valDesc><default>%INHERITED</default><remarks></remarks></attDef><attDef usage="opt"><attName>type</attName><name>Type</name><desc>categorizes the kind of writing in some way, for example
      as a subtitle, noticeboard etc.</desc><datatype>CDATA</datatype><valDesc>Open list</valDesc><default>#IMPLIED</default><remarks></remarks></attDef><attDef usage="opt"><attName>script</attName><name>Script pointer</name><desc>points to a bibliographic citation in the header giving
      a full description of the source or script of the writing.</desc><datatype>IDREF</datatype><valDesc>Must be a valid identifier for a <tag compl="full" tei="yes">script.decl</tag>
     element in the TEI header</valDesc><default>#IMPLIED</default><remarks></remarks></attDef><attDef usage="opt"><attName>gradual</attName><name>gradual</name><desc>indicates whether the writing is revealed all at once or
        gradually.</desc><datatype>(y | n | u)</datatype><valList type="open"><val>y</val><desc>the writing is revealed gradually.</desc><val>n</val><desc>the writing is revealed all at once.</desc><val>u</val><desc>unknown or unmarked.</desc></valList><default>#IMPLIED</default><remarks></remarks></attDef></attList><exemplum><eg></eg></exemplum><remarks><p>The <gi tei="yes">writing</gi> element will usually be short
    and most simply transcribed as a character string; the content
    model also allows a sequence of paragraphs and paragraph-level
    elements, in case the writing has enough internal structure to
    warrant such markup.  In either case the usual phrase-level
    tags for written text are available.</p></remarks><part type="base" name="ts"/><classes names="COMPSPOK"/><!-- making this specialPara would allow it to contain m.comp.spoken! --><elemDecl>- - (%paraContent;)</elemDecl><xref target="TSBAFD"/><xref target="TSBAWR"/><xref target="TSBA"/></tagDoc><?tei:EOF writing.tag ??><!-- writing element --><?tei:SOF teiwsd.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	teiwsd.tag,v $
# Revision 1.1  93/08/03  02:27:04  msmcq
# tagdoc files:  resynching uicvm and onions
#  --><!-- ******************************* writingSystemDeclaration --><tagDoc id="TEIWSD" usage="req"><gi tei="yes">eclaration</gi><desc>declares the coded character set, transliteration scheme, or
entity set used to transcribe a given writing system of a given
language.</desc><attList><!-- ................................................... name --><attDef usage="req"><attName>name</attName><desc>gives a formal name for the writing system declaration</desc><datatype>CDATA</datatype><valDesc>any string of characters</valDesc><default>#REQUIRED</default><eg><![CDATA[ <eclaration
     name='-//TEI P2: 1993//WSD ISO 646 IRV//en'
     date='1993-06-30'>]]></eg><remarks><p></p></remarks></attDef><!-- ................................................... date --><attDef usage="req"><attName>date</attName><desc>gives the date on which the writing system declaration was last
revised.</desc><datatype>%ISO-date</datatype><valDesc>A date in valid ISO format.</valDesc><default>#REQUIRED</default><eg><![CDATA[ ]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[ <eclaration id=ENG lang=eng
   name='-//TEI P2: 1993//WSD Modern English//en'
   date='1993-05-25'>
   <language>Modern English</>
   <direction lines=TB chars=LR>
   <base name='ANSI X3.4' authority='national'>
   <exceptions></>
 </eclaration>]]></eg></exemplum><remarks></remarks><part type="aux" name="wsd"/><classes/><dataDesc>May contain only a prescribed series of sub-elements.</dataDesc><elemDecl>- -  (language, script, direction*, characters, note*)</elemDecl><xref target="WDOV"/></tagDoc><?tei:EOF teiwsd.tag ??><!-- writingSystemDeclaration element --><?tei:SOF xptr.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	xptr.tag,v $
# Revision 1.5  94/03/16  03:44:49  msmcq
# suppress atts inherited from xPointer class
# 
# Revision 1.4  1994/02/12  10:46:40  lou
# revisions for P3
#
# Revision 1.2  1993/09/16  16:20:18  msmcq
# Add to terminologyInclusions class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-15 : MSM : member of xpointer, not pointer         --><!-- 93-09-15 : MSM : include in class termincl               --><!-- 93-02-12 : MSM : LOC class has id CLLOC not LOC          --><!-- 93-01-26 : MSM : correct desc of TO att                  --><!-- 93-01-26 : MSM : add to pointer class                    --><!-- 93-01-21 : MSM : supply full end tags not empty ones     --><!-- ********************************************************** xptr --><tagDoc id="XPTR" usage="opt"><gi tei="yes">xptr</gi><name>extended pointer</name><desc>defines a pointer to another location in the current document
or an external document.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="top" name="links"/><classes names="CLLOC XPOINTER TERMINCL"/><elemDecl>- O EMPTY</elemDecl><xref target="SAXR"/></tagDoc><?tei:EOF xptr.tag ??><!-- xptr element --><?tei:SOF xr.tag ??><!-- Revisions:                                               --><!-- 11 mar 98: LB: corect examples --><!-- 94-01-14 : MSM : add explicit membership in diglobal     --><!-- 94-01-14 : MSM : star the model!  sheesh.                --><!-- 94-01-14 : MSM : add usg, lbl to model                   --><!-- 94-01-14 : MSM : suppress ref to formPointers in model   --><!-- 94-01-14 : MSM : formPointers are in phrase already      --><!-- 94-01-13 : MSM : add to ditoplev                         --><!-- 94-01-13 : MSM : add formptrs to model                   --><!-- 94-01-12 : MSM : correct xref, class                     --><!-- 94-01-12 : MSM : add vallist values                      --><!-- 94-01-12 : MSM : change desc                             --><!-- ***************************************************** xr --><tagDoc id="XR" usage="opt"><gi tei="yes">xr</gi><name>cross-reference phrase</name><desc>contains a phrase, sentence, or icon referring the reader to
some other location in this or another text.</desc><attList><!-- ................................................... type --><attDef usage="rec"><attName>type</attName><desc>indicates the type of cross reference, using any convenient
typology.</desc><datatype>CDATA</datatype><valList type="open"><val>syn </val><desc>cross reference for synonym information</desc><val>etym </val><desc>etymological information</desc><val>cf </val><desc>related or similar term</desc><val>illus </val><desc>illustration of an object</desc></valList><default>#IMPLIED</default><eg><![CDATA[ <xr type=cf>Compare <ref>madrigal (sense 1)</></xr>
 <xr type=illus>see the illus. at <ref>tool</></xr>]]></eg><remarks><p></p></remarks></attDef></attList><exemplum><eg><![CDATA[<entry>
  <form><orth>lavage</orth></etym>
  <!-- ... -->
  <etym>[Fr. < <mentioned>laver</>; L. <mentioned>lavare</>,
        to wash; <xr>see <ref>lather</ref></xr>].</etym>
  <!-- ... -->
</entry>]]></eg></exemplum><exemplum><eg><![CDATA[<entry>
  <form><orth>lawful</orth></form>
  <!-- ... -->
  <xr type='syn'>SYN. see <ref>legal</ref></xr>
</entry>]]></eg></exemplum><remarks><p>This element encloses both the actual indication of the
location referred to, which may be tagged using the <gi tei="yes">ref</gi> or
<gi tei="yes">ptr</gi> elements, and any accompanying material which gives more
information about why the reader is being referred there.</p></remarks><part type="top" name="di"/><classes names="DITOPLEV DIPARTS DIGLOBAL"/><dataDesc>May contain character data and phrase-level elements; usually
contains a <gi tei="yes">ref</gi> or a <gi tei="yes">ptr</gi> element.</dataDesc><elemDecl>- O  (%paraContent | usg | lbl)*</elemDecl><xref target="DITPXR"/></tagDoc><?tei:EOF xr.tag ??><!-- xr element --><?tei:SOF xref.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	xref.tag,v $
# Revision 1.5  94/03/16  03:44:49  msmcq
# suppress atts inherited from xPointer class
# 
# Revision 1.4  1994/03/01  04:16:01  msmcq
# add to clloc class
#
# Revision 1.3  1994/01/04  13:19:24  lou
# xref check
#
# Revision 1.2  1993/09/16  16:20:18  msmcq
# Add to terminologyInclusions class
#
# Revision 1.1  1993/06/23  11:28:40  lou
# Initial checkin
# --><!-- Revisions:                                               --><!-- 94-03-15 : MSM : paraContent, not EMPTY                  --><!-- 94-02-28 : MSM : add / restore to class loc              --><!-- 93-09-15 : MSM : include in class termincl               --><!-- 93-02-12 : MSM : LOC class has id CLLOC not LOC          --><!-- 93-01-26 : MSM : correct desc of TO att                  --><!-- 93-01-26 : MSM : add to pointer class                    --><!-- 93-01-21 : MSM : fill out empty end tags                 --><!-- **********************************************************xref --><tagDoc id="XREF" usage="opt"><gi tei="yes">xref</gi><name>extended reference</name><desc>defines a reference to another location in the current document,
or an external document, using an extended pointer notation,
possibly modified by additional text or comment.</desc><attList></attList><exemplum><eg></eg></exemplum><remarks></remarks><part type="top" name="ling"/><classes names="CLLOC XPOINTER TERMINCL"/><elemDecl>- O (%paraContent)</elemDecl><xref target="SAXR"/><xref target="TETA"/></tagDoc><?tei:EOF xref.tag ??><!-- xref element --><?tei:SOF year.tag ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log:	year.tag,v $
# Revision 1.2  93/08/03  02:25:16  msmcq
# fix MS end problem
#  --><!-- Revisions:                                               --><!-- 93-08-02 : MSM : Added RCS id                            --><!-- 93-06-03 : MSM : Fixed ]]> problem                       --><!-- year --><tagDoc id="YEAR" usage="opt"><gi tei="yes">year</gi><name>year</name><desc>the year component of a date.</desc><attList></attList><exemplum><eg><![CDATA[<date value='14-05-1993'>
<day type=name>Friday</day>,
<day type=number>14</day>
<month type=name>May</month>
<year>1993</year></date>]]></eg></exemplum><remarks></remarks><part type="top" name="office"/><classes names="TEMPEXP"/><elemDecl>- - (#PCDATA)</elemDecl><xref target="NDDATE"/></tagDoc><?tei:EOF year.tag ??><!-- year element --><?tei:EOF p2refs.odd ??><!-- The reference crystals  --></div1></div0><div0 id="P2REFS" n="8" name="Part" ref="Y"><head>Reference Material</head><?tei:SOF p2dt.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2dt.odd,v $
    * Revision 1.4  1998/01/30 16:44:49  tei
    * fix log keyword
    *
    * Revision 1.3  1994/04/08 18:54:36  msmcq
    * Last-second fixes for P3
    *--><!-- Revisions:                                               --><!-- 94-04-07 : MSM : add ID, add list of files               --><!-- 94-04-07 : MSM : Added RCS id                            --><div1 id="DT" n="36" name="Faisal" ref="Y"><head>Obtaining the TEI DTD</head><p>Full copies of the TEI DTD fragments are not repeated in this
document, although they may be reconstituted by a careful reading of
each chapter.</p><p>The DTD fragments are widely available over the Internet and
elsewhere.  At the time of publication, the following anonymous file
servers are expected to carry copies of a full set.  The first is
a Listserv server, the others are anonymous FTP servers.
<list type="simple"><item>listserv@uicvm.uic.edu in filelist tei-l</item><item>sgml1.ex.ac.uk in directory tei/p2/dtds</item><item>ftp.ifi.uio.no in directory TEI</item></list></p><p>The files are these:
<list type="bullets"><item><ident tei="yes" type="file">teiana2.dtd</ident>:  tags for simple analysis</item><item><ident tei="yes" type="file">teiana2.ent</ident>:  parameter entities for
simple analysis</item><item><ident tei="yes" type="file">teiback2.dtd</ident>:  tags for back matter</item><item><ident tei="yes" type="file">teicert2.dtd</ident>:  tags for certainty and
responsibility</item><item><ident tei="yes" type="file">teiclas2.ent</ident>:  parameter entities for the
core tag sets</item><item><ident tei="yes" type="file">teicore2.dtd</ident>:  core tags</item><item><ident tei="yes" type="file">teicorp2.dtd</ident>:  tags for additional header
material for corpora and collections</item><item><ident tei="yes" type="file">teidict2.dtd</ident>:  tags for printed
dictionaries</item><item><ident tei="yes" type="file">teidict2.ent</ident>:  parameter entities for
printed dictionaries</item><item><ident tei="yes" type="file">teidram2.dtd</ident>:  tags for performance texts</item><item><ident tei="yes" type="file">teidram2.ent</ident>:  parameter entities for
performance texts</item><item><ident tei="yes" type="file">teifig2.dtd</ident>:  tags for tables, formulae,
and graphics</item><item><ident tei="yes" type="file">teifig2.ent</ident>:  parameter entities for
tables, formulae, and graphics</item><item><ident tei="yes" type="file">teifron2.dtd</ident>:  tags for front matter</item><item><ident tei="yes" type="file">teifsd2.dtd</ident>:  feature system declaration</item><item><ident tei="yes" type="file">teifs2.dtd</ident>:  tags for feature structure
annotation</item><item><ident tei="yes" type="file">teigen2.dtd</ident>:  tags for general base</item><item><ident tei="yes" type="file">teigis2.ent</ident>:  parameter entities for
names of TEI elements</item><item><ident tei="yes" type="file">teihdr2.dtd</ident>:  tags for TEI header</item><item><ident tei="yes" type="file">teikey2.ent</ident>:  parameter entities for TEI
keywords</item><item><ident tei="yes" type="file">teilink2.dtd</ident>:  tags for linking,
segmentation, and alignment</item><item><ident tei="yes" type="file">teilink2.ent</ident>:  parameter entities for
linking, segmentation, and alignment</item><item><ident tei="yes" type="file">teimix2.dtd</ident>:  tags for mixed base</item><item><ident tei="yes" type="file">teind2.dtd</ident>:  tags for names and dates</item><item><ident tei="yes" type="file">teind2.ent</ident>:  parameter entities for names
and dates</item><item><ident tei="yes" type="file">teinet2.dtd</ident>:  tags for networks, graphs,
digraphs, and trees</item><item><ident tei="yes" type="file">teipl2.dtd</ident>:  tags for concurrent markup
of pages and lines</item><item><ident tei="yes" type="file">teipros2.dtd</ident>:  tags for prose</item><item><ident tei="yes" type="file">teishd2.dtd</ident>:  tags for independent header</item><item><ident tei="yes" type="file">teispok2.dtd</ident>:  tags for spoken texts</item><item><ident tei="yes" type="file">teispok2.ent</ident>:  parameter entities for
spoken texts</item><item><ident tei="yes" type="file">teistr2.dtd</ident>:  tags for default text
structure</item><item><ident tei="yes" type="file">teitc2.dtd</ident>:  tags for text criticism</item><item><ident tei="yes" type="file">teitc2.ent</ident>:  parameter entities for text
criticism</item><item><ident tei="yes" type="file">teiterm2.dtd</ident>:  tags for terminological
data</item><item><ident tei="yes" type="file">teiterm2.ent</ident>:  parameter entities for
terminological data</item><item><ident tei="yes" type="file">teite2f.dtd</ident>:  tags for terminological
data</item><item><ident tei="yes" type="file">teite2n.dtd</ident>:  tags for terminological
data</item><item><ident tei="yes" type="file">teitran2.dtd</ident>:  tags for transcription of
primary sources</item><item><ident tei="yes" type="file">teitran2.ent</ident>:  parameter entities for
transcription of primary sources</item><item><ident tei="yes" type="file">teitsd2.dtd</ident>:  tags for tag set
documentation</item><item><ident tei="yes" type="file">teivers2.dtd</ident>:  tags for verse</item><item><ident tei="yes" type="file">teivers2.ent</ident>:  parameter entities for
verse</item><item><ident tei="yes" type="file">teiwsd2.dtd</ident>:  tags for writing system
declaration</item><item><ident tei="yes" type="file">tei2.dtd</ident>:  main TEI DTD file</item></list><?tei:EOF p2dt.odd ??>
                    <!-- 33 Full TEI DTDs -->
 <?tei:SOF p2xw.odd ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : mostly cosmetic changes                 --><!-- 94-04-07 : MSM : suppress div2 elements                  --><!-- 94 -03-15 LB : rewrote --><!-- 93-04-12 : MSM : made file                               --></p></div1><div1 id="XW" n="37" name="Faisal" ref="Y"><head>Obtaining TEI WSDs</head><p>The TEI has produced a number of exemplary Writing System
Definitions, corresponding with several major international standards.
This section lists those which are currently available. In each case,
the root name specified is that used for the file on the TEI file
servers.
 </p><p>A typical public identifier for a Writing System Declaration from this
list would be
 
<eg><![CDATA[ 
<!ENTITY xxxx PUBLIC
    " -//TEI-1994//NOTATION WSD for YYY //EN" >
 ]]></eg>
 
where xxxxx corresponds with the short name given in the list below,
and YYY with the longer description provided.
 </p><p>Writing system declarations corresponding to some
standard character sets include:
<list type="gloss"><label>ISO646ss </label><item>ISO 646 Non-national Subset</item><label>ISO646ir </label><item>ISO 646 International Reference Version</item><label>ISO88591 </label><item>ISO 8859 Part 1 (Latin 1, Western Europe)</item><label>ISO88592 </label><item>ISO 8859 Part 2 (Latin 2, Eastern Europe)</item><label>ISO88595</label><item>ISO 8859 Part 5 (Latin and Cyrillic)</item><label>ISO88597 </label><item>ISO 8859 Part 7 (Latin and Greek)</item><label>ISO88598 </label><item>ISO 8859 Part 8 (Latin and Hebrew)</item><label>ISO88599 </label><item>ISO 8859 Part 9 (Latin 5, Western Europe and Turkey)</item></list></p><p>Writing system declarations documenting special sets of entities for
different alphabets, or commonly used transliteration systems, include
the following:
 
<list type="simple"><label>TEIarb</label><item>TEI Entities for Arabic</item><label>TEIcop</label><item>TEI Entities for Coptic</item><label>TEIgrk</label><item>TEI Entities for Greek</item><label>TEIipa</label><item>TEI Entities for International Phonetic Alphabet</item></list>
 </p><p>All standard TEI writing system declarations may be obtained from
the same file servers as are listed in chapter<xref target="DT"/>
.
 <?tei:EOF p2xw.odd ??>
                    <!-- 33 Standard WSDs --><!-- &p2.xf; -->
    <!--    FSD for Basic Gramm. --><?tei:SOF p2xt.odd ??><!-- Revisions:                                               --><!-- 94-04-07 : MSM : strip down classdoc                     --><!-- 94-04-07 : MSM : complete refreshment                    --><!-- 94-04-07 : MSM : refresh examples                        --><!-- 93-06-05 : MSM : add editorial note, change title per Eynsham --><!-- 93-04-13 : MSM : Use refs, not odd versions (!)          --><!-- 93-04-13 : MSM : Correct marked sections                 --></p></div1><div1 id="XT" n="38" name="Faisal" ref="Y"><head>Sample Tag Set Documentation
 </head><div2 name="Anthony" ref="Y"><head>Tag Documentation for the TEI P Element</head><p>This example shows the documentation for the element <gi tei="yes">p</gi>.
Since this element has no attributes other than global attributes,
its <gi tei="yes">attList</gi> element is empty.
For a formatted, printed version of this information, see the
alphabetical reference section.
<eg>&lt;tagDoc id=P usage=req&gt;
&lt;gi&gt;p&lt;/gi&gt;
&lt;rs&gt;paragraph&lt;/rs&gt;
&lt;desc&gt;marks paragraphs in prose.&lt;/desc&gt;
&lt;attList&gt;
&lt;/attList&gt;
&lt;exemplum&gt;&lt;eg&gt;&lt;![ CDATA [
&lt;p&gt;Hallgerd was outside.  &lt;q&gt;There is blood on your
axe,&lt;/q&gt; she said.  &lt;q&gt;What have you done?&lt;/q&gt;&lt;/p&gt;
&lt;p&gt;&lt;q&gt;I have now arranged that you can be married a
second time,&lt;/q&gt; replied Thjostolf.&lt;/p&gt;
&lt;p&gt;&lt;q&gt;Then you must mean that Thorvald is dead,&lt;/q&gt;
she said.&lt;/p&gt;
&lt;p&gt;&lt;q&gt;Yes,&lt;/q&gt; said Thjostolf.  &lt;q&gt;And now you must
think up some plan for me.&lt;/q&gt;
]]&gt;
&lt;/eg&gt;
&lt;/exemplum&gt;
&lt;remarks&gt;&lt;p&gt;In some contexts, the paragraph may have a specialized
meaning, e.g. in the tag set for dictionaries, &lt;gi&gt;p&lt;/gi&gt; is used to
enclose any running text, and thus does not imply text set off as is
conventionally done in running prose.
&lt;part type='top' name='core'&gt;additional tag set for common core
features&lt;/part&gt;
&lt;classes names='CHUNK'&gt;chunk [and indirectly also:] common&lt;/classes&gt;
&lt;files names='TEICORE2'&gt;
&lt;dataDesc&gt;May contain character data and phrase-level elements.
&lt;parents&gt;add argument availability body broadcast castList corr
correction div div0 div1 div2 div3 div4 div5 div6 div7 editionStmt
editorialDecl encodingDesc epigraph epilogue equipment equiv exemplum
figure hyphenation interpretation item langUsage metDecl
normalization note particDesc particLinks performance person
personGrp projectDesc prologue publicationStmt q quotation quote
recording recordingStmt refsDecl remarks samplingDecl scriptStmt
segmentation seriesStmt set setting settingDesc sic sourceDesc sp
stage stdVals view&lt;/parents&gt;
&lt;children&gt;#PCDATA abbr add address anchor att bibl biblFull
biblStruct c caesura camera caption castList cit cl corr date
dateRange dateStruct del distinct emph expan figure foreign formula
gap gi gloss handShift hi label lang link list listBibl m measure
mentioned move name note num orig oRef oVar phr ptr pRef pVar q quote
ref reg rs s seg sic sound soCalled stage table tag tech term text
time timeRange timeStruct title val view w xptr xref&lt;/children&gt;
&lt;elemDecl&gt;
&lt;![ CDATA [
&lt;!ELEMENT p             - O  (%paraContent;)                    &gt;
]]&gt;
&lt;/elemDecl&gt;
&lt;attldecl&gt;
&lt;![ CDATA [
&lt;!ATTLIST p                  %a.global                          &gt;
]]&gt;
&lt;/attldecl&gt;
 
&lt;ptr type=div2 target=COPA&gt;
&lt;ptr type=div2 target=DRPAL&gt;
&lt;/tagDoc&gt;</eg>
 </p></div2><div2 name="Anthony" ref="Y"><head>Tag Documentation for the TEI HI Element</head><p>The <gi tei="yes">hi</gi> element, shown below, offers an example of attribute
definition.  Since the attribute definition in question overrides a
definition inherited from the <ident tei="yes" type="class">global</ident> class,
no reference is made to the entity <ident tei="yes" type="pe">a.global</ident>.
Instead, the other global attributes are all redefined.
<eg>&lt;tagDoc usage=opt id="HI"&gt;&lt;gi&gt;hi&lt;/gi&gt;
&lt;rs&gt;highlighted&lt;/rs&gt;
&lt;desc&gt;marks a word or phrase as graphically distinct from the
surrounding text, for reasons concerning which no claim is made. &lt;/desc&gt;
&lt;attList&gt;
&lt;!-- ................................................... rend --&gt;
&lt;attDef usage=rec&gt;
&lt;attName&gt;rend
&lt;rs&gt;rendition&lt;/rs&gt;
&lt;desc&gt;describes the rendition or presentation of the word or phrase
highlighted.
&lt;datatype&gt;CDATA
&lt;valDesc&gt;a set of keywords from some suitable vocabulary; no systematic
recommendations for such a vocabulary are made by these Guidelines.
&lt;default&gt;#IMPLIED
&lt;eg&gt;&lt;![ CDATA [
 
]]&gt;
&lt;/eg&gt;
&lt;remarks&gt;&lt;p&gt;The &lt;att&gt;rend&lt;/att&gt; attribute, though optional in general,
is recommended on the &lt;gi&gt;hi&lt;/gi&gt; element.
&lt;/attDef&gt;
&lt;/attList&gt;
&lt;exemplum&gt;&lt;eg&gt;&lt;![ CDATA [
&lt;hi rend=gothic&gt;And this Indenture further witnesseth&lt;/hi&gt;
that the said &lt;hi rend=italic&gt;Walter Shandy&lt;/hi&gt;, merchant,
in consideration of the said intended marriage ...
]]&gt;
&lt;/eg&gt;&lt;/exemplum&gt;
&lt;remarks&gt;&lt;/remarks&gt;
&lt;part type='aux' name='hdr'&gt;auxiliary tag set for TEI headers&lt;/part&gt;
&lt;classes names='HQPHRASE'&gt;hqphrase [and indirectly also:]
phrase&lt;/classes&gt;
&lt;files names='TEICORE2'&gt;
&lt;dataDesc&gt;free prose&lt;/dataDesc&gt;
&lt;parents&gt;abbr activity actor add addrLine addName admin affiliation
author authority bibl biblScope birth bloc byline camera caption case
castItem catDesc cell channel cl classCode closer colloc constitution
corr country creation damage dataDesc date dateRange def del
derivation desc descrip distance distinct distributor docAuthor
docDate docEdition docImprint domain edition editor education emph
equiv etym expan extent factuality figDesc firstLang foreign forename
form fsDescr funder fw fDescr gen genName gloss gram gramGrp head
headItem headLabel hi hyph imprimatur interaction item itype l label
lang language langKnown lbl lem locale measure meeting mentioned mood
name nameLink note num number occasion occupation opener orgdivn
orgtitle orgtype orgName orig orth otherForm p per persName phr
placeName pos preparedness principal pron publisher pubPlace purpose
q quote rdg re ref reg region rendition residence resp restore role
roleDesc roleName rs s salute seg sense set settlement sic signed
socecStatus sound soCalled speaker sponsor stage street stress subc
supplied surname syll symbol tagUsage tech term time timeRange title
titlePart tns tr trailer trans u unclear usg valDesc view wit witness
witDetail writing xr xref&lt;/parents&gt;
&lt;children&gt;#PCDATA abbr add address anchor att bibl biblFull
biblStruct c caesura camera caption castList cit cl corr date
dateRange dateStruct del distinct emph expan figure foreign formula
gap gi gloss handShift hi label lang link list listBibl m measure
mentioned move name note num orig oRef oVar phr ptr pRef pVar q quote
ref reg rs s seg sic sound soCalled stage table tag tech term text
time timeRange timeStruct title val view w xptr xref&lt;/children&gt;
&lt;elemDecl&gt;
&lt;![ CDATA [
&lt;!ELEMENT hi            - -  (%paraContent;)                    &gt;
]]&gt;
&lt;/elemDecl&gt;
&lt;attldecl&gt;
&lt;![ CDATA [
&lt;!ATTLIST hi                 %a.fs
                             %a.analysis
                             %a.linking
                             %a.terminology
          id                 ID                  #IMPLIED
          n                  CDATA               #IMPLIED
          lang               IDREF               %INHERITED
 
          rend               CDATA               #IMPLIED       &gt;
]]&gt;
&lt;/attldecl&gt;
 
&lt;ptr target=COHQHE&gt;
&lt;ptr target=COHQH&gt;
&lt;/tagDoc&gt;</eg>
 
 </p></div2><div2 name="Anthony" ref="Y"><head>Tag Documentation for the TEI Div Element
 </head><p>The example below shows the documentation for the <gi tei="yes">div</gi>
element; this element is a member of the class
<ident tei="yes" type="class">divn</ident>, the documentation for which is shown
further below.
<eg>&lt;tagDoc usage=rwa id="DIV"&gt;&lt;gi&gt;div&lt;/gi&gt;
&lt;rs&gt;text division&lt;/rs&gt;
&lt;desc&gt;contains a subdivision of the front, body, or back of a
text.&lt;/desc&gt;
&lt;attList&gt;
&lt;/attList&gt;
&lt;exemplum&gt;&lt;eg&gt;&lt;![ CDATA [
&lt;body&gt;
&lt;div type=part&gt;&lt;head&gt;Fallacies of Authority&lt;/head&gt;
&lt;epigraph&gt;The subject of which is Authority in
various shapes, and the object, to repress all
exercise of the reasoning faculty.&lt;/epigraph&gt;
  &lt;div type=chapter n=1&gt;&lt;head&gt;The Nature of Authority&lt;/head&gt;
  &lt;p&gt;With reference to any proposed measures
  having for their object the greatest happiness
  of the greatest number....
     &lt;div type=section n='1.1'&gt;&lt;head&gt;Analysis of Authority
      &lt;p&gt;What on any given occasion is the legitimate
      weight or influence to be attached to authority
      &lt;!-- ... --&gt;
     &lt;/div&gt;
     &lt;div type=section n='1.2'&gt;&lt;head&gt;Appeal to Authority,
        in What Cases Fallacious.
      &lt;p&gt;Reference to authority is open to the charge of
      fallacy when...
      &lt;!-- ... --&gt;
     &lt;/div&gt;
     &lt;!-- other sections here --&gt;
   &lt;/div&gt;
   &lt;div type=chapter n=2&gt;
   &lt;!-- other chapters here --&gt;
   &lt;/div&gt;
&lt;/div&gt;
&lt;!-- other parts here --&gt;
&lt;/body&gt;
]]&gt;&lt;!-- J Bentham: Handbook of Political Fallacies (1824), ed --&gt;
&lt;!-- Larrabee, Johns Hopkins Pr, 1952 --&gt;
&lt;/eg&gt;&lt;/exemplum&gt;
&lt;remarks&gt;
&lt;part type='base' name='core'&gt;base tag set for common core
features&lt;/part&gt;
&lt;classes names='DIVN decling'&gt;declaring, divn&lt;/classes&gt;
&lt;files names='TEISTR2'&gt;
&lt;dataDesc&gt;any sequence of low-level structural elements, possibly grouped
into lower subdivisions.&lt;/dataDesc&gt;
&lt;parents&gt;back body div front&lt;/parents&gt;
&lt;children&gt;argument bibl biblFull biblStruct byline camera caption
castList cit closer div docAuthor docDate entry entryFree epigraph
event eTree graph head kinesic l label lg lg1 list listBibl move note
opener p pause q quote salute shift signed sound sp stage superentry
tech termEntry trailer tree u view vocal writing&lt;/children&gt;
&lt;elemDecl&gt;
&lt;![ CDATA [
&lt;!ELEMENT div           - O  ((%m.divtop;)*, (div+ |
                             ((%component;)+, div*)),
                             (%m.divbot;)*)                     &gt;
]]&gt;
&lt;/elemDecl&gt;
&lt;attldecl&gt;
&lt;![ CDATA [
&lt;!ATTLIST div                %a.global
                             %a.declaring
                             %a.divn                            &gt;
]]&gt;
&lt;/attldecl&gt;
 
&lt;ptr target=DSDIV&gt;
&lt;ptr target=TEDT&gt;&lt;ptr target=DSDIV1&gt;
&lt;/tagDoc&gt;</eg>
 </p></div2><div2 name="Anthony" ref="Y"><head>Class Documentation for the TEI Divn Class
 </head><p>The example below shows the documentation for the class
<ident tei="yes" type="class">divn</ident>, which is referred to by the
documentation for <gi tei="yes">div</gi> shown above.  The class documentation
in the alphabetical reference section of this document uses a
slightly extended tag set which provides for information about
elements within which members of the class may appear, members of
the class, and the actual declaration of the parameter entities
by which properties of the class are expressed.
 
<eg>&lt;classDoc id=DIVN type=atts&gt;
&lt;class&gt;divn&lt;/class&gt;
&lt;desc&gt;structural elements which behave in the same way as divisions.
&lt;attList&gt;
&lt;attDef usage=rec&gt;
&lt;attName&gt;type&lt;/attName&gt;
&lt;desc&gt;specifies a name conventionally used
for this level of subdivision, e.g. &lt;q&gt;act&lt;/q&gt;,
&lt;q&gt;volume&lt;/q&gt;, &lt;q&gt;book&lt;/q&gt;, &lt;q&gt;section&lt;/q&gt;, &lt;q&gt;canto&lt;/q&gt;, etc.&lt;/desc&gt;
&lt;datatype&gt;CDATA
&lt;valDesc&gt;any string of characters&lt;/valDesc&gt;
&lt;default&gt;#CURRENT
&lt;/attDef&gt;
&lt;attDef usage=opt&gt;&lt;attName&gt;org
&lt;desc&gt;specifies how the content of the division is organized.
&lt;datatype&gt;(composite | uniform)
&lt;valList type=closed&gt;
&lt;val&gt;composite&lt;desc&gt;composite content: i.e. no claim is
made about the sequence in which the immediate contents of this
division are to be processed, or their inter-relationships.&lt;/desc&gt;
&lt;val&gt;uniform&lt;desc&gt;uniform content: i.e. the immediate contents
of this element are regarded as forming a logical unit,
to be processed in sequence.&lt;/desc&gt;
&lt;/valList&gt;
&lt;default&gt;uniform
&lt;/attDef&gt;
&lt;attDef&gt;
&lt;attName&gt;sample
&lt;desc&gt;indicates whether this division is a sample of the original source
and if so, from which part.
&lt;/desc&gt;
&lt;datatype&gt;(initial | medial | final | unknown | complete)
&lt;valList type=closed&gt;
&lt;val&gt;initial&lt;desc&gt;division lacks material present at end in
source.&lt;/desc&gt;
&lt;val&gt;medial&lt;desc&gt;division lacks material at start and end.&lt;/desc&gt;
&lt;val&gt;final&lt;desc&gt;division lacks material at start.&lt;/desc&gt;
&lt;val&gt;unknown&lt;desc&gt;position of sampled material within original
unknown.&lt;/desc&gt;
&lt;val&gt;complete&lt;desc&gt;division is not a sample.&lt;/desc&gt;
&lt;/valList&gt;
&lt;default&gt;complete
&lt;remarks&gt;
&lt;/attDef&gt;
&lt;attDef usage=mwa&gt;&lt;attName&gt;part&lt;/attName&gt;
&lt;desc&gt;specifies whether or not the division is fragmented by some other
structural element, for example a speech which is divided between two
or more verse stanzas.
&lt;/desc&gt;
&lt;datatype&gt;(Y | N | I | M | F)
&lt;valList type=closed&gt;
&lt;val&gt;Y&lt;desc&gt;the division is incomplete in some respect&lt;/desc&gt;
&lt;val&gt;N&lt;desc&gt;either the division is complete, or no claim is made as to
its completeness.&lt;/desc&gt;
&lt;val&gt;I&lt;desc&gt;the initial part of an incomplete division&lt;/desc&gt;
&lt;val&gt;M&lt;desc&gt;a medial part of an incomplete division&lt;/desc&gt;
&lt;val&gt;F&lt;desc&gt;the final part of an incomplete division&lt;/desc&gt;
&lt;/valList&gt;
&lt;default&gt;N
&lt;remarks&gt;&lt;p&gt;The values I, M, or F should be used only where it is
clear how the division is to be reconstituted.
&lt;/attDef&gt;
&lt;/attList&gt;
&lt;part type='base' name='core'&gt;base tag set for common core
features&lt;/part&gt;
&lt;classes names=''&gt;&lt;/classes&gt;
&lt;files names='TEICLAS2.ent'&gt;
&lt;ptr target=DS&gt;
&lt;/classdoc&gt;</eg><?tei:EOF p2xt.odd ??>
            <!-- 33 Sample Tag Set Decl. --><?tei:SOF p2gr.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2gr.odd,v $
    * Revision 1.8  1998/01/29 13:22:19  tei
    * Fixes to marked section treatment, responding to Joe Wells 1995-10
    *
    * Revision 1.7  94/04/08  18:54:36  msmcq
    * Last-second fixes for P3
    * 
    * Revision 1.6  1994/03/28  14:43:13  lou
    * fix mistagged terms
    * 
    * Revision 1.5  1994/03/27  16:30:31  lou
    * *** empty log message ***
    * 
    * Revision 1.2  1994/02/17  20:31:08  msmcq
    * revision for SC review
    *--><!-- P2 GR:  BNF of DTD Grammar                               --><!-- Revisions                                                --><!-- 98-01-29 : MSM : recast MS keyword treatment             --><!--                  (thanks due to Joe Wells)               --><!-- 94-04-07 : MSM : suppress N attribute, restore           --><!-- 94-02-15 : MSM : Added RCS id                            --><!-- 92-12-04 : MSM : change IDs to new style                 --><!-- 21 May 92 : CMSMcQ : correct mistake in chardesc comment --><!-- 18 May 92 : CMSMcQ : reorder as per LB, minor revisions  --><!-- 11 Mar 92 : CMSMcQ : phrasing improvements               --><!-- 10 Mar 92 : CMSMcQ : tests with bison, flex completed.   --><!-- 10 Mar 92 : CMSMcQ : add conflict-free alternate doc gr. --><!-- 10 Mar 92 : CMSMcQ : fix assocnotan, other name grps     --><!--  4 Mar 92 : CMSMcQ : correct value:  add nametoken       --><!-- 28 Feb 92 : CMSMcQ : add SGMLdec, doc, common constructs --><!--  2 Feb 92 : CMSMcQ : revise paragraph marking            --><!-- 10 Nov 91 : CMSMcQ : revise to agree with yacc version   -->
</p></div2></div1><div1 id="GR" n="39" name="Faisal" ref="Y"><head>Formal Grammar for the TEI-Interchange-Format Subset of SGML</head><p>This grammar is intended to help make SGML more comprehensible for
formal manipulation.  For this reason, a number of simplifications have
been undertaken, which are described below in section <xref target="GRIS"/>.  These simplifications may cause this grammar to accept
some documents not accepted by the official grammar.  As far as is
known, however, the grammar provided here will recognize any valid SGML
document in the TEI Interchange Format.</p><p>For ease in relating this grammar to the formal grammar defined in
ISO 8879, comments for each group here give the numbers of the related
productions in that grammar.  Where the changes to SGML syntax suggested
by the SGML working group in its document ISO/IEC JTC1 / SC18 / WG8 /
N1035 would affect the productions here, that fact is noted after the
affected production.</p><p>Each sub-grammar given here has been checked for ambiguity with
<term rend="noindex">bison</term>, a public-domain workalike for <term rend="noindex">yacc</term>, and <term rend="noindex">flex</term>, a
public-domain workalike for <term rend="noindex">lex</term>.  The bison
and flex source files, including the simple modifications needed to
implement the recognition-mode stack, are available from the TEI.</p><p>The SGML declaration grammar and the DTD grammar have no ambiguities.
The document grammar has several ambiguities, which are discussed in
section <xref target="GRDI"/>.</p><div2 id="GRNO" name="Anthony" ref="Y"><head>Notation</head><p>The notation used here is based on notations commonly used in writing
context-free grammars.  All non-terminals are written as single tokens.
 
<list type="simple"><label><code tei="yes" type="frag">::=   </code></label><item><q>is defined as</q></item><label><code tei="yes" type="frag">a b   </code></label><item>instance of <code tei="yes" type="frag">a</code>
followed by instance of <code tei="yes" type="frag">b</code>, possibly separated
by white space; white space may
be required if <code tei="yes" type="frag">a</code> and <code tei="yes" type="frag">b</code> cannot otherwise
be delimited</item><label><code tei="yes" type="frag">a | b </code></label><item>instance of <code tei="yes" type="frag">a</code> or
instance of <code tei="yes" type="frag">b</code></item><label><code tei="yes" type="frag">a || b</code></label><item>instance of <code tei="yes" type="frag">a</code> followed
immediately by an instance of <code tei="yes" type="frag">b</code>, without any
intervening white space</item><label><code tei="yes" type="frag">/* */</code></label><item>comment; right-hand
sides comprising only a comment are used to call attention to
productions in which the left-hand sides can reduce to the empty
string</item><label><code tei="yes" type="frag">//</code></label><item>comment; runs to end of line</item></list>
 
All non-quoted strings are non-terminals.  All terminals are quoted.</p></div2><div2 id="GRDO" name="Anthony" ref="Y"><head>Grammar for SGML Document (Overview)</head><p>An SGML document is preceded by an SGML declaration and a prolog
comprising one or more document-type declarations.  It may be
accompanied by one or more subdocument entities, text entities, non-SGML
entities, etc., but for simplicity these last are not discussed here.
 
<eg>SGMLdoc ::= SGMLdeclaration prolog docinstance  // cf. 1, 2</eg></p><p>The grammars for the SGML declaration, the prolog, and the document
instance are provided in the following three sections.</p></div2><div2 id="GRSG" name="Anthony" ref="Y"><head>Grammar for SGML Declaration</head><p>This grammar is substantively the same as that in ISO 8879; it does
not reflect the restrictions placed on SGML declarations for
TEI-conformant documents.
 
<eg><![CDATA[SGMLdeclaration ::= '<!SGML'                // cf. 171
                    'ISO 8879:1986'
                    'CHARSET' charset       // cf. 172
                    'CAPACITY' capacity     // cf. 180
                    'SCOPE' scope           // cf. 181
                    'SYNTAX' syntax
                    'FEATURES'              // cf. 195-198
                        'MINIMIZE'
                                'DATATAG'  yesno
                                'OMITTAG'  yesno
                                'RANK'     yesno
                                'SHORTTAG' yesno
                        'LINK'
                                'SIMPLE' count
                                'IMPLICIT' yesno
                                'EXPLICIT' count
                        'OTHER'
                                'CONCUR' count
                                'SUBDOC' count
                                'FORMAL' yesno
                    'APPINFO' appinfo       // cf. 199
                    '>'
/*
** Strictly speaking, the blank in 'ISO 8879:1986' may be
** replaced by any amount or type of white space.
*/
 
charset     ::= baseset descset             // cf. 173
              | charset baseset descset
baseset     ::= 'BASESET' pubid             // cf. 174
/* For pubid, see Common Constructs below */
descset     ::= 'DESCSET' chardesc          // cf. 175
              |  descset  chardesc
chardesc    ::= NUMBER NUMBER NUMBER        // cf. 176-179
              | NUMBER NUMBER LITERAL
              | NUMBER NUMBER 'UNUSED'
/*
** The first two numbers in chardesc identify starting point
** and a number of characters in the described character set;
** the third number gives the starting position for that run
** in the base set; a literal provides a description of the
** character(s); 'UNUSED' marks the run as unused.
*/
 
capacity    ::= 'PUBLIC' pubid              // cf. 180
              | 'SGMLREF' caplist
caplist     ::= capname NUMBER
              | caplist capname NUMBER
capname     ::= 'TOTALCAP' | 'ENTCAP'   | 'ENTCHCAP'
              | 'ELEMCAP'  | 'GRPCAP'   | 'EXGRPCAP'
              | 'EXNMCAP'  | 'ATTCAP'   | 'ATTCHCAP'
              | 'AVGRPCAP' | 'NOTCAP'   | 'NOTCHCAP'
              | 'IDCAP'    | 'IDREFCAP' | 'MAPCAP'
              | 'LKSETCAP' | 'LKNMCAP'      // cf. Fig. 5
 
scope       ::= 'DOCUMENT' | 'INSTANCE'     // cf. 181
 
syntax      ::= 'PUBLIC' pubid              // cf. 182-183
              | 'PUBLIC' pubid switchlist
              | 'SHUNCHAR' shunchars        // cf. 184
                charset                     // cf. 185
                'FUNCTION'                  // cf. 186
                    'RE' NUMBER 'RS' NUMBER 'SPACE' NUMBER
                    funlist
                'NAMING'                    // cf. 189
                    'LCNMSTRT' LITERAL
                    'UCNMSTRT' LITERAL
                    'LCNMCHAR' LITERAL
                    'UCNMCHAR' LITERAL
                    'NAMECASE' 'GENERAL' yesno 'ENTITY' yesno
                'DELIM'                     // cf. 190-92
                    'GENERAL' 'SGMLREF' gendelim
                    'SHORTREF' srdelim
                'NAMES'    'SGMLREF' nameset // cf. 193
                'QUANTITY' 'SGMLREF' quantityset // cf. 194
/*
** Document WG8 / N1035 suggests allowing multiple literals
** after each keyword in the NAMING section; this may be
** effected by adding the non-terminal literalset after each
** LITERAL.
*/
 
switchlist  ::= 'SWITCHES' NUMBER NUMBER    // cf. 183
              | switchlist NUMBER NUMBER
 
shunchars   ::= 'NONE'                      // cf. 184
              | shunlist
shunlist    ::= 'CONTROLS'
              | NUMBER
              | shunlist NUMBER
 
funlist     ::= NAME funclass NUMBER        // cf. 186-187
              | funlist NAME funclass NUMBER
funclass    ::= 'FUNCHAR' | 'MSICHAR' | 'MSOCHAR' // cf. 188
              | 'MSSCHAR' | 'SEPCHAR'
 
gendelim    ::= /* nil */                   // cf. 191
              | gendelim delimname LITERAL
delimname   ::= 'AND'   | 'COM'  | 'CRO'    // cf. Fig. 3
              | 'DSC'   | 'DSO'  | 'DTGC'   // clause 9.6
              | 'DTGO'  | 'ERO'  | 'ETAGO'
              | 'GRPC'  | 'GRPO' | 'LIT'
              | 'LITA'  | 'MDC'  | 'MDO'
              | 'MINUS' | 'MSC'  | 'NET'
              | 'OPT'   | 'OR'   | 'PERO'
              | 'PIC'   | 'PIO'  | 'PLUS'
              | 'REFC'  | 'REP'  | 'RNI'
              | 'SEQ'   | 'SHORTREF'
              | 'STAGO' | 'TAGC' | 'VI'
 
srdelim     ::= 'SGMLREF' literalset        // cf. 192
              | 'NONE' literalset
literalset  ::= /* nil */
              | literalset LITERAL
nameset     ::= /* nil */
              | nameset sgmlname NAME
/*
** WG8 / N1035 substitutes a LITERAL for the NAME of the
** preceding rule; the value must be a NAME in the declared
** concrete syntax, but it need not be a legal name in the
** reference concrete syntax.
*/
 
sgmlname    ::= 'ANY'      | 'ATTLIST'  | 'CDATA'
              | 'CONREF'   | 'CURRENT'  | 'DEFAULT'
              | 'DOCTYPE'  | 'ELEMENT'  | 'EMPTY'
              | 'ENDTAG'   | 'ENTITIES' | 'ENTITY'
              | 'FIXED'    | 'ID'       | 'IDLINK'
              | 'IDREF'    | 'IDREFS'   | 'IGNORE'
              | 'IMPLIED'  | 'INCLUDE'  | 'INITIAL'
              | 'LINK'     | 'LINKTYPE' | 'MD'
              | 'MS'       | 'NAME'     | 'NAMES'
              | 'NDATA'    | 'NMTOKEN'  | 'NMTOKENS'
              | 'NOTATION' | 'NUMBER'   | 'NUMBERS'
              | 'NUTOKEN'  | 'NUTOKENS' | 'O'
              | 'PCDATA'   | 'PI'       | 'POSTLINK'
              | 'PUBLIC'   | 'RCDATA'   | 'RE'
              | 'REQUIRED' | 'RESTORE'  | 'RS'
              | 'SDATA'    | 'SHORTREF' | 'SIMPLE'
              | 'SPACE'    | 'STARTTAG' | 'SUBDOC'
              | 'SYSTEM'   | 'TEMP'     | 'USELINK'
              | 'USEMAP'
 
quantityset ::= /* nil */
              | quantityset quantity NUMBER
quantity    ::= 'ATTCNT'   | 'ATTSPLEN' | 'BSEQLEN' // Cf.
              | 'DTAGLEN'  | 'DTEMPLEN' | 'ENTLVL'  // Fig. 6
              | 'GRPCNT'   | 'GRPGTCNT' | 'GRPLVL'
              | 'LITLEN'   | 'NAMELEN'  | 'NORMSEP'
              | 'PILEN'    | 'TAGLEN'   | 'TAGLVL'
 
yesno       ::= 'NO' | 'YES'
count       ::= 'NO' | 'YES' NUMBER
 
appinfo     ::= 'NONE' | LITERAL            // cf. 199
/*
** The literal string is restricted to letters, digits,
** whitespace, and 'specials':  viz. any of
** ' ( ) + , - . / : = ?
*/]]></eg></p></div2><div2 id="GRDT" name="Anthony" ref="Y"><head>Grammar for DTD</head><p>An SGML <term>prolog</term> is composed of one or more document type
declarations; if multiple DTDs are present, the SGML declaration must
include <q>CONCUR YES</q> in the FEATURES section.  A document type
declaration names the root element of the document and declares (in an
external file, in a DTD subset, or both) elements, attributes,
notations, and entities used in the document instance.  Interspersed
with these declarations may be comments and processing instructions.
 
<eg><![CDATA[prolog      ::= misc dtdseq                 // cf. 7, 9
 
/* For misc, see Common Constructs below */
 
dtdseq      ::= dtd misc                    // cf. 7
              | dtdseq dtd misc
 
                                            // cf. 110, 111, 30
dtd         ::= '<!DOCTYPE' NAME extid '[' dtdsubset ']' '>'
              | '<!DOCTYPE' NAME       '[' dtdsubset ']' '>'
              | '<!DOCTYPE' NAME extid                   '>'
              | '<!DOCTYPE' NAME                         '>'
 
dtdsubset   ::= /* */                       // cf. 112, 113, 114
              | dtdsubset elementdecl
              | dtdsubset attlistdecl
              | dtdsubset notationdecl
              | dtdsubset entitydecl
              | dtdsubset commdecl
              | dtdsubset procinst
 
/* Element Declarations */                  // cf. 116
elementdecl ::= '<!ELEMENT' elemtype minimiz contentdecl '>'
 
elemtype    ::= NAME                        // cf. 117, 30, 72
              | '(' namegrp ')'
 
namegrp     ::= andnames                    // cf. 69, 131
              | ornames
              | seqnames
seqnames    ::= NAME
              | seqnames ',' NAME
ornames     ::= NAME     '|' NAME
              | ornames  '|' NAME
andnames    ::= NAME     '&' NAME
              | andnames '&' NAME
 
minimiz     ::= min min                     // cf. 122-124
min         ::= 'O' | '-'
 
contentdecl ::= 'CDATA'                     // cf. 125, 126
              | 'RCDATA'
              | 'EMPTY'
              | 'ANY'  exceptions
              | model  exceptions
 
model       ::= '(' tokengrp ')'            // cf. 127
              | '(' tokengrp ')?'
              | '(' tokengrp ')*'
              | '(' tokengrp ')+'
 
tokengrp    ::= seqtokens                   // cf. 127
              | ortokens
              | andtokens
seqtokens   ::= token
              | seqtokens ',' token
ortokens    ::= token     '|' token
              | ortokens  '|' token
andtokens   ::= token     '&' token
              | andtokens '&' token
 
token       ::= '#PCDATA'                   // cf. 128-130
              | NAME || occurrence
              | model
 
occurrence  ::= /* nil */                   // cf. 132
              | '?'
              | '*'
              | '+'
 
exceptions  ::= exclusions inclusions       // cf. 138-140
exclusions  ::= /* nil */
              | '-(' namegrp ')
inclusions  ::= /* nil */
              | '+(' namegrp ')'
 
 
/* Attribute List Declarations */
attlistdecl ::= '<!ATTLIST' associated attdeflist '>' // Cf. 141
 
associated  ::= elemtype
              | assocnotatn
 
assocnotatn ::= '#NOTATION' NAME            // Cf. 149.1
              | '#NOTATION' '(' namegrp ')'
 
attdeflist  ::= attdef                      // Cf. 142
              | attdeflist attdef
 
attdef      ::= NAME valtype default        // Cf. 143-44
 
valtype     ::= 'CDATA'   |                 // Cf. 145
              | 'ENTITY'  | 'ENTITIES'
              | 'ID'      |
              | 'IDREF'   | 'IDREFS'
              | 'NAME'    | 'NAMES'
              | 'NMTOKEN' | 'NMTOKENS'
              | 'NUMBER'  | 'NUMBERS'
              | 'NUTOKEN' | 'NUTOKENS'
              | 'NOTATION' '(' namegrp ')'
              | '(' nmtokgrp ')'
 
nmtokgrp    ::= nmtokcom | nmtokbar | nmtokamp   // Cf. 68, 131
nmtokcom    ::= nametoken
              | nmtokcom  ',' nametoken
nmtokbar    ::= nametoken '|' nametoken
              | nmtokbar  '|' nametoken
nmtokamp    ::= nametoken '&' nametoken
              | nmtokamp  '&' nametoken
nametoken   ::= NAME
              | NUMBER
              | NUMTOKEN
 
default     ::=  value                      // Cf. 147
              | '#FIXED' value
              | '#REQUIRED'
              | '#CURRENT'
              | '#CONREF'
              | '#IMPLIED'
 
/* For value, see Common Constructs below */
 
 
/* Notation Declarations */                 // cf. 148-49, 41
notationdecl ::= '<!NOTATION' NAME extid '>'
 
 
/* Entity Declarations */                   // cf. 101-04
entitydecl  ::= '<!ENTITY' NAME       enttext '>'
              | '<!ENTITY' '#DEFAULT' enttext '>'
              | '<!ENTITY' '% ' NAME  enttext '>'
/*
** Strictly, any white space is acceptable after the %
** in a parameter entity declaration, not just a single
** space.
*/
 
enttext     ::= LITERAL                     // cf. 105-08
              | 'CDATA'    LITERAL
              | 'SDATA'    LITERAL
              | 'PI'       LITERAL
              | 'STARTTAG' LITERAL
              | 'ENDTAG'   LITERAL
              | 'MS'       LITERAL
              | 'MD'       LITERAL
              | extid enttype
 
enttype     ::= /* */                       // cf. 108-109, 149.2
              | 'SUBDOC'
              | 'CDATA' NAME
              | 'CDATA' NAME '[' attspecset ']'
              | 'NDATA' NAME
              | 'NDATA' NAME '[' attspecset ']'
              | 'SDATA' NAME
              | 'SDATA' NAME '[' attspecset ']'
/* For attspecset, see Common Constructs below. */
 
extid       ::= 'SYSTEM'                    // cf. 73
              | 'SYSTEM' sysid
              | 'PUBLIC' pubid
              | 'PUBLIC' pubid sysid
/* For pubid, see Common Constructs below */
 
sysid       ::= LITERAL                     // cf. 75]]></eg></p></div2><div2 id="GRDI" name="Anthony" ref="Y"><head>Grammar for Document Instance</head><p>The SGML document instance is composed of one element (the <term>root
element</term>), followed optionally by white space, comments, and
processing instructions.  The root element, like any other, has a
start-tag, content, and an end-tag, or only a start-tag (if it is
empty).  The specific sort of content recognized within an element
depends upon its element declaration.
 
<eg><![CDATA[docinstance ::= element misc                // cf. 10-12
 
element     ::= start-tag content end-tag   // cf. 13
              | start-tag
/*
** N.B. this BNF is for minimal SGML documents; tags may
** not be omitted.
*/
 
start-tag   ::= '<' || NAME attspecset '>'  // cf. 14, 28-30
              | '<(' namegrp ')' || NAME attspecset '>'
/*
** The name group is used only if the SGML declaration
** specifies CONCUR YES.
** For attspecset, see Common Constructs below.
*/
 
content     ::= mixedcontent                // cf. 24
              | elemcontent
              | rcdata
              | cdata
 
mixedcontent ::= /* nil */                  // cf. 25
              | mixedcontent STRING
              | mixedcontent element
              | mixedcontent misccontent
 
elemcontent ::= /* nil */                   // cf. 26
              | elemcontent element
              | elemcontent misccontent
cdata       ::= STRING                      // cf. 47
              | cdata STRING
rcdata      ::= STRING                      // cf. 46
              | rcdata STRING
/*
** White space is ignored between elements in element content,
** but not in mixed content.  In CDATA and RCDATA, start-tag
** delimiters are not recognized.  In CDATA, entity reference
** delimiters are not recognized.  An element's content model
** determines whether it is scanned for mixed content, element
** content, CDATA content, or RCDATA content.
*/
 
misccontent ::= commdecl                    // cf. 27
              | procinst
/*
** For commdecl and procinst, see Common Constructs below.
** Omitted here for simplicity are short-reference and
** link-set use declarations and short references (which are
** not allowed in TEI interchange format), entity references
** (which are assumed to be handled by the lexical scanner),
** and marked-section declarations (also in lexical
** scanner).
*/
 
end-tag     ::= '</' || NAME '>'            // cf. 19, 21
              | '</(' namegrp ')' || NAME '>'
              | '</>'
/*
** The name group is used only if the SGML declaration
** specifies CONCUR YES.
** N.B. The last form (short end-tag) is not allowed in the
** TEI Interchange Format.
*/
 ]]></eg></p><p>The document-instance grammar just given contains two sets of formal
ambiguities.  One set concerns the distinction among mixed content,
element content, RCDATA, and CDATA, which depends not on the document
content but on the definition of the element within which they appear.
These conflicts can be eliminated by eliminating the distinction and
assigning the task of distinguishing content type (and alerting the
lexical analyzer to modify its behavior) to the semantic rules of the
parser, rather than to the syntax.</p><p>The second set of ambiguities arises in connection with start-tags:
after a start-tag, empty elements are complete, others not, and the
ambiguity can be resolved only by consulting the DTD, not by lookahead.
Such conflicts can be avoided by defining document content as an
unstructured sequence of start-tags, end-tags, and data content; the
parser's semantic actions must enforce the pairing and nesting of
start- and end-tags and the distinction between empty and non-empty
elements.  Despite the ambiguities, the grammar given here seems to
express the nature of SGML documents more clearly than the unambiguous
alternative and so has not been changed; the changes needed to eliminate
the parsing conflicts are these:
 
<list type="bullets"><item>delete <term>element</term>, <term>mixedcontent</term>,
<term>elemcontent</term>, <term>cdata</term>, and <term>rcdata</term>.</item><item>redefine <term>docinstance</term> and <term>content</term> as
follows:</item></list>
<eg><![CDATA[docinstance ::= start-tag content           // cf. 10-12
content     ::= /* nil */                   // cf. 25
              | content STRING
              | content start-tag
              | content end-tag
              | content misccontent]]></eg>
Applications using this simplification must distinguish mixed content,
element content, RCDATA, and CDATA using other methods than document
syntax.  They can check the appropriate matching of start- and end-tags
using a simple element stack with provision for empty elements.  Some
SGML normalizers provide explicit end-tags for empty elements to
simplify this task.</p></div2><div2 id="GRCO" name="Anthony" ref="Y"><head>Common Syntactic Constructs</head><p>This section defines syntactic constructions used in more than one of
the three preceding grammar fragments.
 
<eg><![CDATA[misc        ::= /* nothing */               // cf. 8
              | misc commdecl
              | misc procinst
 
commdecl    ::= '<!--' STRING '--' commseq '>'   // cf. 91, 92
              | '<!>'
commseq     ::= /* nil */
              | commseq '--' STRING '--'
 
procinst    ::= '<?' STRING '>'             // cf. 44
 
attspecset  ::= /* nil */                   // cf. 31
              | attspecset attspec
 
attspec     ::= NAME '=' value              // cf. 32
              | value
/*
** NAME may be omitted only if the attribute has an
** enumerated range of values and the value is an unquoted
** name token.
*/
 
value       ::= LITERAL                     // Cf. 33
              | NAME
              | NUMBER
              | NUMTOKEN
 
pubid       ::= LITERAL                     // cf. 74, 76
/*
** The literal string is restricted to letters, digits,
** whitespace, and 'specials':  viz. any of
** ' ( ) + , - . / : = ?
*/]]></eg></p></div2><div2 id="GRLX" name="Anthony" ref="Y"><head>Lexical Scanner</head><p>The grammar given above assumes a lexical scanner which
<list type="simple"><item n="1">scans for the terminal strings represented here in quotes</item><item n="2">scans for certain other token types (listed below)</item><item n="3">handles white space and some comments without
returning them</item><item n="4">recognizes and expands entity references appropriately without
notifying the parser</item></list></p><p>N.B. the literals given here for delimiters, keywords, and in the
definitions of character classes and character types, are those used in
the reference concrete syntax of SGML; a full SGML parser must be able
to use other concrete syntaxes.</p><p>The token types to be returned by the lexical scanner include (in
addition to the literals used in the grammars above):
<list type="simple"><item>name</item><item>number</item><item>numtoken</item><item>literal</item><item>string</item></list>
 
These are printed in all caps in the grammar and are defined thus:
 
<eg>NAME        ::= letter                      // Cf. 55
              | NAME || letter
              | NAME || digit
              | NAME || othernamech
NUMBER      ::= digit                       // cf. 56
              | NUMBER || digit
NUMTOKEN    ::= digit || letter             // cf. 58
              | digit || othernamech
              | NUMTOKEN || letter
              | NUMTOKEN || digit
              | NUMTOKEN || othernamech
LITERAL     ::= "'" || STRING || "'"        // Cf. 66, 76, 34
              | '"' || STRING || '"'
STRING      ::= /* */
              | STRING || character

/* N.B. The characters legal in a string vary with the string's
location:  in a literal, the string must not contain the closing
quote character; in content or mixed content, the string will
end before a tag or entity reference; in a commdecl or commseq,
the string must not contain the double hyphen that closes the
comment; in a processing instruction, the string may not contain
the '&gt;' which closes the processing instruction, etc. */
 
character   ::= letter | digit | othercharacter
letter      ::= 'a' | 'b' | 'c' | 'd' ... | 'z'
              | 'A' | 'B' | 'C' | 'D' ... | 'Z'
digit       ::= '0' | '1' | '2' | '3' ... | '9'
othernamech ::= '-' | '.'
whitespace  ::= space | tab | record-end | record-start
space          ::= /* as defined in SGML declaration */
tab            ::= /* as defined in SGML declaration */
record-end     ::= /* as defined in SGML declaration */
record-start   ::= /* as defined in SGML declaration */
othercharacter ::= /* as defined in SGML declaration */</eg></p><p>This list of primitive token types differs slightly from that of
ISO 8879, which defines names, numbers, name tokens, and number
tokens as overlapping sets of tokens distinguished by context.  The
redefinition provided here assigns each string to a single class and
thus allows a simpler lexical analyzer.  The terms in ISO 8879
correspond to those here in the following way:
 
<list type="bullets"><item>ISO 8879 <term>name</term> = NAME</item><item>ISO 8879 <term>number</term> = NUMBER</item><item>ISO 8879 <term>name token</term> = NAME | NUMBER | NUMTOKEN</item><item>ISO 8879 <term>number token</term> = NUMBER | NUMTOKEN</item></list></p><p>The grammar given above assumes that the lexical scanner will
recognize and handle entity references and marked sections.  Entity
references take one of the following forms (parameter entities within
the DTD and within marked section declarations, general entities
within document content and attribute values):
<eg><![CDATA[entityref ::= '&' NAME erc
            | '&' '(' namegrp ')' erc
peref     ::= '%' NAME erc
            | '%' '(' namegrp ')' erc
/*
** The name groups are used only if the SGML declaration
** specifies CONCUR YES.  The TEI Interchange Format
** specifies that entities should never be defined
** differently in different DTDs, so the name group form
** is strictly speaking unnecessary for that format.
*/
erc       ::= ';'
            | '&#RE;'                       // i.e. record-end
            | /* nothing */
/*
** If the entity reference is not ended explicitly by a
** semicolon or end of line, it is ended implicitly by the
** first non-name character.  Unlike the semicolon or
** record-end, this non-name character counts as data and is
** passed to the application as data.
*/]]></eg></p><p>The processing of an entity reference may involve scanning its
replacement text for delimiters, passing its content to the parser
without scanning for delimiters, opening a new file if the entity
is external to the SGML document, and other special processing
not described here.</p><p>Marked sections take the following forms (n.b. the marked section
keywords may be replaced by parameter entity references).
<eg>/* Marked Sections */                       // Cf. 97-100
msinclude ::= '&lt;![' includespec '[' scandata  ']]&gt;'
msrcdata  ::= '&lt;![' rcdataspec  '[' rchardata ']]&gt;'
mscdata   ::= '&lt;![' cdataspec   '[' chardata  ']]&gt;'
msignore  ::= '&lt;![' ignorespec  '[' anything  ']]&gt;'
 
/* Marked Section keywords */
kwinclude ::= 'INCLUDE' | 'TEMP'
kwrcdata  ::= kwinclude | 'RCDATA' 
kwcdata   ::= kwrcdata  | 'CDATA' 
kwignore  ::= kwcdata   | 'IGNORE'
 
includespec ::= /* nothing */
            | includespec kwinclude
rcdataspec  ::= includespec 'RCDATA'
            | rcdataspec kwrcdata
cdataspec   ::= rcdataspec 'CDATA' 
            | cdataspec  kwcdata
ignorespec  ::= cdataspec 'IGNORE'
            | ignorespec kwignore

/*
** Multiple keywords may appear; rank order is IGNORE,
** CDATA, RCDATA, INCLUDE.  TEMP is also legal but has
** no effect.
*/
 
chardata  ::= /* characters scanned for ']]&gt;' and
                 returned to parser as character data,
                 regardless of what other delimiters are
                 present */
rchardata ::= /* characters scanned for entity references
                 and ']]&gt;', and then returned to parser
                 as character data, regardless of what other
                 delimiters are present; n.b. the closing
                 ']]&gt;' must occur within the same entity
                 as the opening '&lt;![', not within the expansion
                 of an entity within the marked section */
scandata  ::= /* characters scanned and returned to parser
                 as normal; the marked-section end ']]&gt;'
                 is recognized only within content or
                 between declarations within a DTD */
anything  ::= /* contents of the marked section are 'ignored';
                 i.e., characters are scanned for ']]&gt;'
                 and for nested pairs of '&lt;![' and ']]&gt;',
                 and the lexical scanner does not return the
                 characters to the parser.  */</eg></p></div2><div2 id="GRIS" name="Anthony" ref="Y"><head>Differences from ISO 8879</head><p>This grammar assumes the reference concrete syntax; if an alternate
concrete syntax is used, some literal strings given in the DTD and
document-instance grammars would need to be replaced accordingly.</p><p>White space, entity reference, entity end, and comments within markup
declarations are assumed to be handled by the lexical scanner and are
omitted from this grammar.  This shortens and simplifies the grammar
somewhat.</p><p>The grammar is written as a Backus-Naur-Form (BNF) grammar rather
than a regular-right-part grammar; some additional constructs have thus
been introduced to deal with repeating and optional items in the
original grammar.  Non-terminals optional in the original may be
required here, and vice versa, depending on how the optionality of a
construct has been expressed; in no case does such a change actually
affect the set of strings accepted by the grammar.</p><p>Some constructs are omitted entirely because they do not occur in the
subset of SGML prescribed for use in the TEI Interchange Format:
<list type="simple"><item>link type declaration</item><item>short reference set</item><item>ranked elements and ranked groups</item><item>data tag group</item><item>minimized start-tags</item><item>formal identifiers</item></list></p><p>Finally, the recognition and expansion of entity references and the
handling of marked sections, CDATA and RCDATA elements, and CDATA,
SDATA, or NDATA entities have been ignored in the current version.
Entity references are assumed to be handled by the lexical scanner,
though in a fully conformant SGML parser they are in part dependent on
the state of the syntactic parser.  CDATA, RCDATA, SDATA, and NDATA
elements or entities, like marked sections, are assumed either not to
occur or to be handled by the lexical scanner.
 <!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-default-dtd-file:"~/lib/psgml/fullodd.ced"
sgml-parent-document:("/home/tei/P3/Master/Odds/p2.odd" "TEI.1" "TEXT" "BODY" "DIV1")
sgml-omittag:t
sgml-shorttag:t
End:
--></p></div2></div1><?tei:EOF p2gr.odd ??><!-- 34 SGML BNF subset --></div0></body><back><?tei:SOF p2bib.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!--*
    * $Log: p2bib.odd,v $
    * Revision 1.7  1998/02/01 17:55:08  tei
    * fix log keyword (still need SGML normalization)
    *
    * Revision 1.6  98/01/28  11:09:58  cmsmcq
    * LB changes of January 1998
    * 
    * Revision 1.5  1994/04/01  16:14:29  msmcq
    * Add works newly cited in text
    * 
    * Revision 1.4  1994/03/27  21:49:02  msmcq
    * Strip annotations
    * 
    * Revision 1.3  1994/02/17  20:31:08  msmcq
    * revision for SC review
    * --><!-- TEI P2,       Bibliography                                 --><!-- Title:                                                     --><!-- Drafted:      CMSMcQ 31 May 90 from chapters               --><!-- ********************************************************** --><!-- Revision History (add lines at top)                        --><!-- 7 jan 98 : LB : remove redundant whitespace --><!-- 94-03-30 : MSM : remove stray full stop, temporary garbage at eof --><!-- 94-03-29 : MSM : supplement with titles cited in text    --><!-- 94-03-27 : MSM : strip annotations, typos from SJ        --><!-- 94-02-17 : MSM : Added RCS id                            --><!-- 94-02-17 : MSM : remove ansi=y (debugging error)         --><!-- 94-02-15 : MSM : remove the intentional errors           --><!-- 94-02-03 : MSM : fix kucera's name                       --><!-- 94-02-03 : MSM : suppress stray note end-tag             --><!-- 94-02-02 : MSM : correct slip                            --><!-- 94-02-02 : MSM : supply missing ./date                   --><!-- 94-02-02 : MSM : retag all cit.str as citation           --><!-- 94-02-02 : MSM : (bug in model or sgmls)                 --><!-- 93-02-10 : MSM : add sgml error to cause message         --><!-- Date      Who    What                                      --><!-- 15 Jul 92 CMSMcQ add Goldfarb                              --><!-- 16 Apr 92 CMSMcQ add Edwards/Lampert, Johansson 92.        --><!-- 31 Dec 91 CMSMcQ add Amsler/Tompa                          --><!-- 28 Dec 91 CMSMcQ Into ODD tags for TEI P2, merge SGML bibl --><!-- 12 Oct 90 CMSMcQ * Version 1.1 *************************   --><!-- 12 Oct 90 CMSMcQ added xref to SGML reading list           --><!-- 17 Jul 90 CMSMcQ corrected ISO 639 from Robin Cover        --><!-- 22 Jun 90 CMSMcQ added some material from Stig Johansson   --><!-- 31 May 90 CMSMcQ made from bits and pieces for draft 0     --><!-- ********************************************************** --><div1 name="Faisal" ref="Y"><head>Bibliography</head><p>This bibliography lists the works cited in the text of the Guidelines,
as well as including some useful publications relating to SGML.  It does
not include works cited only as sources of examples.</p><!-- and it really needs to be updated! (LB) --><list.cit><citation>AAP (Association of American Publishers).  <title>Author's
Guide to Electronic Manuscript Preparation and Markup.</title>  Version
2.0 Revised Edition.  [Dublin, Ohio]:  Electronic Publishing Special
Interest Group (EPSIG), 1989.</citation><citation>AAP (Association of American Publishers).  <title>Markup of
Mathematical Formulas.</title>  Version 2.0 Revised Edition.  [Dublin,
Ohio]:  EPSIG, 1989.</citation><citation>AAP (Association of American Publishers).  <title>Markup of
Tabular Material.</title>  Version 2.0 Revised Edition.  [Dublin, Ohio]:
EPSIG, 1989.</citation><citation>AAP (Association of American Publishers).  <title>Reference
Manual on Electronic Manuscript Preparation and Markup.</title>  Version
2.0 Revised Edition.  [Dublin, Ohio]:  EPSIG, 1989.</citation><citation>ALA (American Library Association).  <title>ALA-LC
Romanization Tables:  Transliteration Schemes for Non-Roman
Scripts</title>, approved by the Library of Congress and the American
Library Association, tables compiled and edited by Randall K. Barry.
Washington:  Library of Congress, 1991.</citation><citation>Amsler, R. A., and F. W. Tompa,
<title.p>An SGML-based Standard for English Monolingual
Dictionaries.</title.p>
<title>Information in Text,
Proc. 4th Conf. of Univ. of Waterloo Centre for the New OED</title>
(Waterloo:  [n.p.], October 1988), pp. 61-79.</citation><citation>ANSI (American National Standards Institute).  <title>ANSI
X3.4-1986.  American National Standard for Information Systems --- Coded
Character Sets --- 7-bit American National Standard Code for Information
Interchange (7-bit ASCII).</title>  [New York]:  ANSI, 1986.</citation><citation>ANSI (American National Standards Institute).  <title> ANSI
X3.41-1974.  American National Standard Code Extension Techniques for
Use with the 7-bit Coded Character Set of American National Standard
Code for Information Interchange</title>.  [New York]:  ANSI, 1974.</citation><citation>ANSI (American National Standards Institute).  <title>ANSI
Z39.47-1985.  American National Standard for Information Sciences ---
Extended Latin Alphabet Coded Character Set for Bibliographic
Use.</title>  [New York]:  ANSI, 1984.</citation><citation>Atkinson, J. Maxwell, and John Heritage, eds.
<title>Transcript notation.  Structures of social action:  Studies in
conversation analysis.</title>
Cambridge:  Cambridge University Press, 1984.</citation><citation>Avram, Henriette.
<title>The MARC Pilot Project.</title>
Washington D.C.:  Library of Congress, 1968, p.  3.</citation><citation><author>Barnard, David, et al.</author>
<title.p>SGML-Based Markup for Literary Texts.</title.p>
<title>Computers and the Humanities</title>
<detail>22 (1988):  265-76.</detail></citation><citation><author>Barron, David</author>
<title.p>Why use SGML?</title.p>
<title>Electronic Publishing
Origination, Dissemination and Design</title>
<detail>2.1 (April 1989):  3-24.</detail></citation><citation><author>Berkowitz, Luci, and Karl A.
Squitier</author>.
<title>Thesaurus Linguae Graecae Canon of Greek
Authors and Works</title>,
2nd edition.  Oxford:  Oxford University Press,
1986.</citation><citation>Boase, S.
<title>London-Lund Corpus:  Example Text and Transcription Guide.</title>
London:  Survey of English Usage, University College London,
1990.</citation><citation><author>Bryan, Martin</author>
<title>SGML:  an Author's Guide to the Standard Generalized
Markup Language.</title>
Reading:  Addison-Wesley, 1988.</citation><citation>Butcher, Judith.  <title>Copy-editing:  The Cambridge
Handbook.</title>  2nd edition.  Cambridge:  Cambridge University Press,
1981.</citation><citation>Byrne, Deborah J.
<title>MARC Manual:  Understanding and Using MARC Records.</title>
Englewood, Colo.:
Libraries Unlimited, Inc., 1991.</citation><citation>Calzolari,
Nicoletta, et al.
<title.p>Computational Model of the
Dictionary Entry:  Preliminary Report,</title.p> Acquilex:  Esprit Basic
Research Action No. 3030, Six-Month Deliverable. Pisa, April 1990.</citation><citation><author>Chartrand, Gary, and
Linda Lesniak</author>.
<title>Graphs and Digraphs.</title>
Menlo Park, CA: Wadsworth, 1986).</citation><citation><title>The Chicago Manual of Style, for Authors, Editors and
Copywriters.</title>  13th Edition.  Chicago and London:  Univ. of
Chicago Press, 1982.</citation><citation><author>Coombs, James H., Allen H. Renear, and Steven J.
DeRose.</author> <title.p>Markup Systems and the Future of Scholarly
Text Processing.</title.p> <title>Communications of the ACM</title>
<detail>30.11 (November 1987):  933-947.</detail></citation><citation><editor>Cover, Robin C., et al.</editor>
<title>A Bibliography on Structured Text: Technical Report 90-281</title>
<imprint><publ>Queen's University, </publ><city>Kingston, Ont.</city><date>June 1990</date></imprint></citation><citation>Crawford, Walt.  <title>MARC for Library Use:  Understanding
the USMARC Formats.</title>  Professional Librarian Series.  White
Plains, NY:  Knowledge Industry Publications, 1984.</citation><!-- <citation>Crawford, Walt.                                --><!-- <title>MARC for library use:  understanding USMARC.</title> --><!-- Boston: G.K. Hall, 1989.                                 --><!-- </citation>                                              --><citation>The DANLEX Group.
<title.p>Descriptive Tools for Electronic Processing
of Dictionary Data.</title.p> In
<title>Lexicographica, Series Maior.</title>
T&uuml;bingen:  Niemeyer, 1987.</citation><citation>ECMA (European Computer Manufacturers Association).
<title>Standard ECMA-94:  8-Bit Single-Byte Coded Graphic Character
Sets.  Latin Alphabets No. 1 to No. 4.</title>  2nd Edition --- June
1986.  [Geneva]:  ECMA, 1986.</citation><citation>ECMA (European Computer Manufacturers Association).
<title>Standard ECMA-113:  8-Bit Single-Byte Coded Graphic Character
Sets.  Latin/Cyrillic Alphabet.</title>  2nd Edition --- July 1988.
[Geneva]:  ECMA, 1988.</citation><citation>ECMA (European Computer Manufacturers Association).
<title>Standard ECMA-114:  8-Bit Single-Byte Coded Graphic Character
Sets.  Latin/Arabic Alphabet.</title>  June 1986.  [Geneva]:  ECMA, 1986.</citation><citation>ECMA (European Computer Manufacturers Association).
<title>Standard ECMA-118:  8-Bit Single-Byte Coded Graphic Character
Sets.  Latin/Greek Alphabet.</title>  December 1986.  [Geneva]:  ECMA,
1986.</citation><citation>ECMA (European Computer Manufacturers Association).
<title>Standard ECMA-121:  8-Bit Single-Byte Coded Graphic Character
Sets.  Latin/Hebrew Alphabet.</title>  July 1987.  [Geneva]:  ECMA, 1987.</citation><citation>ECMA (European Computer Manufacturers Association).
<title>Standard ECMA-128:  8-Bit Single-Byte Coded Graphic Character
Sets.  Latin Alphabet No. 5.</title>  July 1988.  [Geneva]:  ECMA, 1988.</citation><citation>Edwards, J. A., and M. D. Lampert, eds.
<title>Talking Language:  Transcription and Coding of
Spoken Discourse</title>
Hillsdale, N.J.:  Lawrence Erlbaum Associates, 1993.</citation><citation>Fought, John, and Carol Van Ess-Dykema.
<title.p>Toward an SGML Document
Type Definition for Bilingual Dictionaries.</title.p>
TEI working paper
TEI AIW20 (available from the TEI).</citation><citation>Francis, W. N., and H. Ku&ccaron;era.  <title>Manual of
Information to Accompany a Standard Sample of Present-day Edited
American English, for Use with Digital Computers.</title>  Original ed.
1964, revised 1971, revised and augmented 1979.  Providence, R.I.:
Department of Linguistics, Brown University.</citation><citation>Francis, W. Nelson, and Henry Kucera,
with the assistance of
Andrew W. Mackie.  <title>Frequency Analysis of English Usage:  Lexicon
and Grammar.</title>  Boston:  Houghton Mifflin, 1982.</citation><citation>Gale, William A., and Kenneth W. Church.
<title.p>Program for Aligning Sentences in Bilingual Corpora.</title.p>
<title>Computational Linguistics</title>
19 (1993):  75-102.</citation><citation>Garside, R. G., G. N. Leech, and G. R. Sampson.
<title>The Computational Analysis of English: a Corpus-Based
Approach.</title>
Oxford:  Oxford University Press, 1987.</citation><citation><author>Gavioli, Laura, and Gillian Mansfield.</author>
<title>The Pixi Corpora.</title>
Bologna:  Cooperativa Libraria Universitaria Editrice, 1990.</citation><citation>Geens, D., L.K.  Engels, and W. Martin.  <title>Leuven Drama
Corpus and Frequency List.</title>  Leuven:  University of Leuven,
Institute of Applied Linguistics, 1975.</citation><citation>Goldfarb, Charles F., <title>The SGML Handbook.</title>
Oxford:  Clarendon Press, 1990.</citation><citation>Gorman, Michael, and Paul W. Winkler, eds.
<title>Anglo-American Cataloguing Rules.</title>  Second Edition.
Chicago:  American Library Association; London:  Library Association;
Ottawa:  Canadian Library Association, 1978.</citation><citation>Gorman, Michael.  <q>After AACR2R: The Future of the
Anglo-American Cataloging Rules.</q> In
<title>Origins, Content and Future of AACR2 Revised,</title>
ed. Richard Smiraglia.
Chicago:  American Library Association, 1992.</citation><citation>Guittet, C., ed., <title>Formex:  Formalized Exchange of
Electronic Publications.</title>  Luxembourg:  Office for Official
Publications of the European Communities, New Technologies --
Project Management Department, 1984.</citation><citation><author>van Herwijnen, Eric.</author>
<title>Practical SGML.</title>
<imprint><publ>Kluwer</publ><date>1990</date></imprint></citation><citation>Holt, Brian P.
<title>UNIMARC Manual.</title>
London, U.K.: IFLA Universal
Bibliographic Control and International MARC Programme, British Library,
1987.</citation><citation>IBM (International Business Machines).  <title>3174
Establishment Controller:  Character Set Reference.</title>  Manual no.
GA27-3831-01.  Second Edition (May 1989).  [n.p.]:  IBM, 1989.<!-- (MSM) Check this suspicious title.  --></citation><citation>Ide, Nancy, and Jean Veronis.
<title.p>Encoding Print Dictionaries.</title.p>
<title>Computers and the Humanities</title>
(1994, in press).</citation><citation>Ide, Nancy, Jacques Le Maitre, and Jean Veronis.
<title.p>Outline of a Model for Lexical Databases,</title.p>
<title>Information Processing and Management</title>
29.2 (1993): 159-186.</citation><citation>Ide, Nancy, Jean Veronis, Susan Warwick-Armstrong, and
Nicoletta Calzolari.
<title.p>Principles for Encoding machine readable
dictionaries.</title.p>
<title>Proceedings of the Fifth EURALEX
International Congress, EURALEX'92</title> (University of
Tempere, Finland).  In press.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 639:  1988.  Code for the representation of names of
languages.</title>  [Geneva]:  International Organization for
Standardization, 1988.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 646:  1983.  Information processing --- ISO 7-bit coded
character set for information interchange.</title>  [Geneva]:
International Organization for Standardization, 1983.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 646:  1991.  Information processing --- ISO 7-bit coded
character set for information interchange.</title>  ([Geneva]:
International Organization for Standardization, 1991.)<!-- need to check date on this new version of 646. (MSM) --></citation><citation>ISO (International Organization for Standardization).
<title>ISO 2014:  1976.  Writing of Calendar Dates in All-Numeric
Form.</title>  [Geneva]:  International Organization for Standardization,
1976.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 2022:  1986.
Information processing --- ISO 7-bit and
8-bit coded character sets --- Code extension techniques.</title>
3d ed.
[Geneva]:  International Organization for Standardization,
1986.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 6429:  1992.
Information processing --- Control
functions for 7-bit and 8-bit coded character sets</title>.
[Geneva]:  International Organization for Standardization,
1992.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8601: 1988.
Data elements and interchange formats --- Information
interchange ---  Representation of dates and times.</title>
[Geneva]:  International Organization for Standardization,
1988.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8859-1:  1987 (E).  Information processing --- 8-bit
Single-Byte Coded Graphic Character Sets --- Part 1:  Latin Alphabet No.
1.</title>  (<title>Traitement de l'information --- Jeux de caracte``res
graphiques code''s sur un seul octet --- Partie 1:  Alphabet latin no
1.</title>) First edition --- 1987-02-15.  [Geneva]:  International
Organization for Standardization, 1987.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8859-2:  1987 (E).  Information processing --- 8-bit
Single-Byte Coded Graphic Character Sets --- Part 2:  Latin Alphabet No.
2.</title>  (<title>Traitement de l'information --- Jeux de caracte``res
graphiques code''s sur un seul octet --- Partie 2:  Alphabet latin no
2.</title>) First edition --- 1987-02-15.  [Geneva]:  International
Organization for Standardization, 1987.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8859-7:  1987 (E).  Information processing --- 8-bit
Single-Byte Coded Graphic Character Sets --- Part 7:  Latin/Greek
Alphabet.</title>  First edition --- 1987-11-15.  [Geneva]:
International Organization for Standardization, 1987.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8859-8:  1988 (E).  Information processing --- 8-bit
Single-Byte Coded Graphic Character Sets --- Part 8:  Latin/Hebrew
Alphabet.</title>  (<title>Traitement de l'information --- Jeux de
caracte``res graphiques code''s sur un seul octet --- Partie 8:
Alphabet Latin/He''breu.</title>) First edition --- 1988-06-01.
[Geneva]:  International Organization for Standardization, 1988.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8879-1986 (E).  Information processing --- Text and Office
Systems --- Standard Generalized Markup Language (SGML).</title>  First
edition --- 1986-10-15.  [Geneva]:  International Organization for
Standardization, 1986.</citation><citation>ISO (International Organization for Standardization).
<title>ISO 8879:1986 / A1:1988 (E).  Information processing --- Text and
Office Systems --- Standard Generalized Markup Language (SGML),
Amendment 1.</title>  Published 1988-07-01.
[Geneva]:  International Organization for Standardization, 1988.</citation><citation>ISO (International Organization for Standardization).
<title>ISO/TR 9573-1988(E).  Information processing---SGML support
facilities---Techniques for using SGML.</title>  Final text of
1988-09-12.</citation><citation></citation><citation>ISO (International Organization for Standardization).
<title>ISO 10241: 1993.
Preparation and
layout of international terminology standards.</title>
[Geneva]:  International Organization for Standardization, 1993.</citation><citation>ISO (International Organization for Standardization), and IEC
(International Electrotechnical Commission). <title>ISO/IEC 10646-1:
1993.  Information technology --- Universal Multiple-Octet Coded
Character Set (UCS) --- Part 1:  Architecture and Basic Multilingual
Plane.</title>
[Geneva]:  International Organization for
Standardization, 1993.</citation><citation></citation><citation>ISO (International Organization for Standardization), and IEC
(International Electrotechnical Commission).
<title>ISO/IEC 10744: 1992.  Information
Technology --- Hypermedia/Time-based Structuring Language
(HyTime).</title>
[Geneva]:  International Organization for Standardization, 1992.</citation><citation>Jackendoff, R.
<title>X-Bar Syntax:  A Study in Phrase Structure.</title>
Linguistic Inquiry Monographs, 2.
Cambridge:  MIT Press, 1977.</citation><citation>Johansson, Stig.
<title.p>Encoding a Corpus in Machine-Readable Form.</title.p>
In <title>Computational Approaches
to the Lexicon:  An Overview,</title> ed. B. T. S. Atkins et al.
Oxford:  Oxford University Press, forthcoming.</citation><citation>Johansson, Stig, in collaboration with Eric Atwell, Roger
Garside, and Geoffrey Leech.  <title>The Tagged LOB Corpus:  User's
Manual</title>.  Bergen:  Norwegian Computing Centre for the Humanities,
1986.</citation><citation>Johansson, S., G. Leech, and H. Goodluck.  <title>Manual of
Information to Accompany the Lancaster-Oslo/Bergen Corpus of British
English, for Use with Digital Computers.</title>  Oslo:  Department of
English, University of Oslo, 1978.</citation><citation>Johansson, Stig, et al.
<title.p>Working Paper on Spoken
Texts,</title.p> document TEI AI2 W1, 1991.</citation><citation>Kucera, Henry, and W. Nelson Francis.  <title>Computational
analysis of present-day American English</title>, with a foreword by W.
F. Twaddell, a study by Mary Lois Marckworth and Laura M. Bell, and an
analytical essay by John B. Carroll.  Providence, Brown University
Press, 1967.</citation><citation>Kyt&ouml;, M., and M. Rissanen.
<title.p>The Helsinki Corpus of English
Texts,</title.p> in <title>Corpus Linguistics:  Hard and Soft</title>,
ed. M. Kyt&ouml;, O. Ihalainen, and M. Rissanen.
Amsterdam:  Rodopi, 1988.</citation><citation>Langendoen, D. Terence, and Gary F. Simons.
<q>A Rationale for the TEI
Recommendations for Feature-Structure Markup.</q>
<title>Computers and the Humanities</title>
(1994; in press).</citation><citation>Leech, G. N., and R. G. Garside.
<title.p>Running a Grammar Factory,</title.p> in
<title>English Computer Corpora:
Selected Papers and Research Guide,</title>
ed. S. Johansson and A.-B. Stenstr&ouml;m.
Berlin: de Gruyter; New York:  Mouton, 1991,
pp. 15-32.</citation><citation>Loman, Bengt, and Nils J&oslash;rgensen.  <title>Manual for
analys och beskrivning av macrosyntagmer.</title>  Lundastudier i
nordisk spr&aring;kvetenskap, serie C nr. 1.  Lund:  Studentlitteratur,
1971.</citation><citation><author>MacWhinney, Brian.</author>
<title>CHAT Manual.</title>
[Pittsburgh]:  Dept of Psychology, Carnegie-Mellon University,
1988, pp. 87ff.</citation><citation>Marshall, I.
<title.p>Choice of Grammatical Word Class without Global Syntactic
Analysis:  Tagging Words in the LOB Corpus.</title.p>
<title>Computers and the Humanities</title>
17 (1983): 139-50.</citation><citation>Modern Humanities Research Association.  <title>MHRA style
book:  notes for authors, editors and writers of dissertations.</title>
3rd edition.  London:  MHRA, 1981.</citation><citation>Pereira, Fernando C. N.
<title>Grammars and Logics of Partial Information.</title>
SRI International Technical Note 420.
Menlo Park, CA: SRI International, 1987.</citation><citation>Renouf, A. <title.p>Corpus Development.</title.p> In
<title>Looking Up:  An Account of the COBUILD Project in Lexical
Computing.</title>  Ed. J. McH. Sinclair.  London:  Collins ELT, 1987.</citation><citation>Shieber, Stuart.
<title>An Introduction to Unification-based Approaches
to Grammar.</title>
CSLI Lecture Notes 4.
Palo Alto, CA: Center for the Study of Language and Information,
1986.</citation><citation><title>Sociolinguistics/Soziolinguistik (An international
handbook of the science of language and society.  Ein internationales
Handbuch zur Wissenschaft von Sprache und Gesellschaft).</title>
Berlin,
New York:  De Gruyter, 1988.
I, pp. 271 and 274.</citation><citation>Stokes, Roy, rev.  <title>Esdaile's Manual of
Bibliography,</title> revised edition by Roy Stokes.  London:  George
Allen and Unwin Ltd, 1931; 1967.</citation><citation>TEI (Text Encoding Initiative).  <title.p>Design Principles
for Text Encoding Guidelines.</title.p> Document No.  TEI EDP1.  Version
2, 10 January 1990.</citation><citation>TEI.  <title.p>Charges to the Working Committees.</title.p>
Document No.  TEI EDP2.  Version 3, 28 August 1989.</citation><citation><title>TEI / LISA / ISO - TIF --- Terminology Interchange
Format --- A Tutorial.</title>  Rpt. in
<title>TermNet News</title>
no 40 (1993), pp. 5-64.</citation><citation>   <author>Warmer, J., and S. van Egmond</author>
   <title.p>The implementation of the Amsterdam
        SGML parser.</title.p>
   <title>Electronic Publishing
        Origination, Dissemination and Design</title>
   <detail>2.2 (July 1989):  65-90.</detail></citation><citation>TLG (Thesaurus Linguae Graecae).
<title>Beta Manual</title>.
(Irvine:  TLG, [1988]).</citation><citation>The Unicode Consortium.
<title>The Unicode Standard:
Worldwide Character Encoding.</title>
Version 1.0, Volume 1.
Reading, Mass.:  Addison-Wesley, 1991.</citation><citation><title>USMARC format for bibliographic data,
including content designation.</title>
Washington, D.C.: Library of
Congress, 1987.</citation><citation><title>Webster's New Collegiate Dictionary.</title>
Springfield, Mass.:  G. &amp; C. Merriam Co., 1975.
(Cited as:  Webster's Collegiate.)</citation><citation><title>Webster's New International Dictionary of the English
Language</title>, ed. W. T. Harris and F. Sturges Allen.  Springfield,
Mass.:  G. &amp; C. Merriam Co., 1922.
(Cited as:  Webster's Second International.)</citation><citation>   <author>Wu, Gilbert S.K.</author>
   <title>SGML theory and practice.</title>
   <imprint><date>1989</date></imprint><series>British Library research paper 68</series></citation></list.cit></div1><?tei:EOF p2bib.odd ??><!-- Bibliography --><!-- Table of name equivalents in EEC languages --><!-- Mapping markup from other schemes into TEI --><!--  &p2.urc; --><!-- User Response and Comment form --><div1 name="Faisal" ref="Y"><head>Index</head><!-- generate index here --><?tei:SOF p2col.odd ??><!-- $Id: p2odd.xml 483 2008-09-02 09:24:21Z rahtz $ --><!-- $Log: p2col.odd,v $
# Revision 1.1  1994/02/17  20:29:04  msmcq
# Initial revision
# --><!-- Revisions:                                               --><!-- 94-02-17 : MSM : Added RCS id                            --><!-- 94-02-17 : MSM : change id                               --><!-- 93-06-03 : MSM : change phrasing on validation           --><!-- 92-12-06 : MSM : revise description of processing        --></div1><div1 id="P2COL" name="Faisal" ref="Y"><!-- no head:  colophons don't need titles --><p>The text of this manual was prepared electronically on a variety of
systems.  Most sections were originally drafted by members of the work
groups and working committees of the TEI; all have been revised by the
editors to achieve greater uniformity of style and greater consistency
in the tag set.</p><p>SGML tags from a preliminary version of the tag set documented here were
introduced in the text by the original drafters of the sections or by
the editors, using standard text editors on VMS, VM/CMS, PC-DOS, and
Apple Macintosh systems.  The resulting SGML document fragments were
validated using VM2 (a markup validator distributed with the
public-domain ARCSGML materials), sgmls (a parser built on the same
engine), Markit, Checkmark, XGML Validator, and/or
Author/Editor.  The validated files, which contained both the prose
description of the tag set and the reference materials, were then
processed with ad hoc programs written in Spitbol to produce separate
SGML documents for the prose, the reference section, and the DTDs; these
SGML documents were then further translated by simple programs in Rexx
and Spitbol into either LaTeX or Waterloo GML for formatting and
printing.</p><p>The camera ready copy of this document was produced by Waterloo Script
GML,
version 89.1,
running on the IBM 3090 at the University of Illinois at Chicago
Academic Computer Center (to which thanks), and using a set of
macros extending the GML Starter Set of tags with specialized tags
designed for this document.<!-- The printing was done by                                 --><!-- Omnipress, Inc., of Madison, Wisconsin.                  --><!-- (msm) check LaTeX version number; check Omnipress address.  --></p></div1><?tei:EOF p2col.odd ??><!-- Colophon     --></back></text></TEI.1><?tei:EOF p2.odd ??>
