<?tei:SOF p2pref.odd ?>
<!-- $Id: p2pref.odd,v 1.2 1994/04/01 16:31:21 msmcq Exp $ -->
<!-- $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'><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 name='Preface' id=PF><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>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>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>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>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>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>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>
<item>Berger-Levrault AIS s.a. (for Balise).
<item>E2S n.v. (for E2S Advanced SGML Editor)
<item>Electronic Book Technology (for DynaText),
<item>SEMA Group and Yard Software (for Mark-It and Write-It),
<item>Software Exoterica (for CheckMark and Xtran),
<item>SoftQuad, Inc., (for Author/Editor and RulesBuilder),
<item>WordPerfect Corporation (for Intellitag)
<item>Xerox Corporation (for Ventura Publisher)
</list>
<!-- also DARC ? kill Xerox? -->
 
<p>Details of the software actually used to produce the current document
are given in the colophon at the end of the work.
</div1>
<?tei:EOF p2pref.odd ?>
