<?tei:SOF p2ab1.odd ?>
<!-- Date: Tue, 09 Mar 1993 21:39:41 +0000                    -->
<!-- From: Lou Burnard < lou@vax.ox.ac.uk >                   -->
<!-- To: U35395@UICVM.UIC.EDU                                 -->
<!-- CC: lou@vax.ox.ac.uk                                     -->
<!-- Subject: AB1.ODD (1 of 3)                                -->
 
<!-- Revisions:                                               -->
<!-- 93-06-03 : MSM : add N value                             -->
<!-- 93-06-02 : LB : reorganize post Eynsham                  -->
<!-- 93-03-13 : MSM : further cosmetic changes                -->
<!-- 93-03-13 : MSM : minor cosmetic changes, spellcheck      -->
<!--                  some stylistic changes                  -->
<!--                  stress creation of feature subset       -->
<!-- 93-03-09 : MSM : cosmetic changes                        -->
<!-- 8 Mar 93 : LB incorporate SMH's suggestions with some    -->
<!--         minor tweaks and much re-tagging                 -->
<!-- 5  Mar 93 : SMH  : extensive and reductive rewrites      -->
<!-- 15 May 92 : CMSMcQ : small changes possibly debatable    -->
<!-- 12 may 92 : LB : extensive rewriting/slaughter           -->
<!-- 20 Apr 92 : CMSMcQ : further work                        -->
<!-- 30 Mar 92 : CMSMcQ : revisions                           -->
<!-- ? : CMSMcQ : make from scratch, no source in P1          -->
 
<div1 id=AB n=1><head>About these Guidelines</head>
 
<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.  They provide a
means of encoding those features of a text which need to be identified
in some way in order to aid the processing of that text by computer
programs.  Such encoding 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.
 
<p>The TEI Guidelines are intended to codify the form, content, and
interpretation of textual features for a wide variety of purposes.  They
are intended for use in interchange between individuals and research
groups using different programs and computer systems over a broad range
of applications.  They can also be used for the local storage of text
which is to be processed with multiple software packages with
different input formats.
And since they contain an inventory of the features most
often found useful for text processing, the Guidelines also provide
help to those creating electronic texts.
 
<p>It should be noted that the present document is a technical
reference manual for a markup language designed to solve a large number
of occasionally complex problems; it is not a tutorial, and should not
be read as one.  No user of the scheme described here is likely to need
to be familiar with the whole of it.  Separate tutorials on SGML and the
TEI are being developed, which will include both introductory
background material for novice readers and more detailed information
appropriate to particular application areas.
 
<!-- above is rewrite by Lou of following: -->
<!-- problems; it is not a tutorial, and should not be read   -->
<!-- as one.  Separate tutorials on SGML and the TEI are      -->
<!-- being developed, which are designed to provide enough    -->
<!-- background knowledge to allow most readers to begin      -->
<!-- with the task of encoding texts they wish to work        -->
<!-- with, and to allow them to read usefully those           -->
<!-- portions of this document which apply to them.           -->
 
<p>This introductory chapter begins with
a brief summary of the contents of the present volume
(section <xref target=ABSUM>), and a definition of the stylistic
conventions and notation used throughout the body of the text (section
<xref target=ABNOT>).  Section <xref target=ABTEI> gives a
brief account of the process by which the Guidelines came into being,
and their likely development in the future. Finally, the chapter
describes informally some of the ideas
underlying our approach to the encoding of textual material in
electronic form, (section <xref target=ABDEF>), and suggests the kinds
of usage envisaged for these recommendations (section <xref
target=ABAPP>).
 
<?tei:EOF p2ab1.odd ?>
