% Received: by UICVM (Mailer R2.02) id 8897; Tue, 25 Apr 89 08:18:19 CDT
% Date:         Tue, 25 Apr 89 09:17 EST
% Reply-To:     Text Encoding Initiative Steering Committee List
%               <TEISTEER@UICVM>, IDE@VASSAR
% Sender:       Text Encoding Initiative Steering Committee List <TEISTEER@UICVM>
% From:         IDE@VASSAR
% To:           "C. M. Sperberg-McQueen" <U35395@UICVM>
%
% From:   edu%"mamrak@cis.ohio-state.edu" 20-APR-1989 15:17
% To:     IDE
% Subj:   Re:  AITRIC PROPOSAL
%
% Received: From CUNYVM(MAILER) by VASPSY with Jnet id 2537
%           for IDE@VASPSY; Thu, 20 Apr 89 15:16 EST
% Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.01) with BSMTP id 6229; Thu,
%  20 Apr 89 15:15:35 EDT
% Received: from tut.cis.ohio-state.edu by CUNYVM.CUNY.EDU (IBM VM SMTP R1.1) with
%  TCP; Thu, 20 Apr 89 15:15:30 EDT
% Received: from bucatina.cis.ohio-state.edu by tut.cis.ohio-state.edu
% (5.59/3.890413)
%     id AA16864; Thu, 20 Apr 89 15:11:05 EDT
% Received: by bucatina.cis.ohio-state.edu (3.2/2.890120)
%     id <AA02899@bucatina.cis.ohio-state.edu>; Thu, 20 Apr 89 15:08:58 EDT
% Date: Thu, 20 Apr 89 15:08:58 EDT
% From: Sandy Mamrak <mamrak@cis.ohio-state.edu>
% Message-Id: <8904201908.AA02899@bucatina.cis.ohio-state.edu>
% To: IDE%VASPSY.BITNET@cunyvm.cuny.edu, mamrak@cis.ohio-state.edu
% Subject: Re:  AITRIC PROPOSAL
% Cc: IDE%vaspsy.bitnet@relay.cs.net, mamrak@cis.ohio-state.edu
%
% Below I include the summary of a proposal that I would
% prepare for aitrc if I get further encouragement from
% them.  I attached a preliminary budget which says I
% would match the ~$42K that I am getting from NEH for
% this work, with $22K, enough to support a grad student
% at half-time for a year.  The maximum allowable match
% under aitrc rules is 55%, so this is right under the wire.
%
\documentstyle[12pt]{article}
\begin{document}

\hyphenation{Com-pu-ter-Pro-cess-able}

\begin{center}

{\small \bf Execution of the Tasks of the Metalanguage Subcommittee\\
of the Text Encoding Initiative}

{\small \bf Executive Summary}

S.A. Mamrak\\

\today

\end{center}

\section{Overview of the Text Encoding Initiative Project}

The Association for Computers and the Humanities, the Association for
Computational Linguistics, and the Association for Literary and
Linguistic Computing have proposed to develop and promote guidelines
for the preparation and interchange of machine-readable texts for
scholarly research.  Committees on text documentation, text
representation, text analysis and formal-language issues have been
formed to draft the guidelines.  A variety of other professional
organizations and learned societies are participating in the project's
advisory board and will approve the final form of the guidelines,
following which the three sponsoring organizations will arrange for
their publication.

Professor S. A. Mamrak has been invited to chair the committee
addressing formal-language issues, now designated the Metalanguage
committee.  This committee has two tasks.  The first is to generate
guidelines for the use of SGML Document Type Definitions in the TEI
project.  The second is to design an intermediate language, for
representing currently existing encoding schemes, to facilitate
translation into their SGML equivalents.

\section{Proposed Work of the Metalanguage Committee}

We are proposing to undertake the two tasks assigned to the
Metalanguage Committee, and in addition to begin the design and
implementation of a set of prototype software tools for creating and
manipulating DTDs.  These tools will be unique in that they will
enforce usage according to the guidelines promulgated by the
Metalanguage committee.  These guidelines will be generally
applicable, not only to the work of the TEI, but to the work of all
groups faced with specifying DTDs.  Thus, the toolset is expected to
be generally applicable as well.

In particular, we propose to begin this toolset with the design and
implementation of a software environment to support the specification
of the DTDs themselves.  This specification task is a very complex one,
and virtually impossible for humans to perform properly without software
tools that can aid in avoiding the specification of incomplete or
incorrect DTDs.  Existing tools to support this specification are not
nearly adequate to address all the forms of complexity.  We have
already fully identified all the sources of complexity in the task,
reviewed related work and found it lacking, and conceived a design for
an adequate support system.  We now propose to proceed with the
implementation of the prototype environment.

\end{document}
