Sethworks Mooseum Annex Exhibit: EGS Standard - Introduction


FILE: egs_defn.txt Extended Grammatical Standard/Structuring
DATE: [95/03/15;23:21:00] first draft composition.
MODI: [95/09/25;22:10:00] convert document from EGS to ASCII text.
MODI: [95/11/13;22:09:03] update vector protocol.
MARK: version 3.2
ORIG: Forrest Glen Landry.
 
TITLE: The Definition of the EGS Standard.

TEXT: DEGS.

Introduction:
The purpose of this document is to define the parameters and form for the EGS format of written ASCII text.  Herein, EGS is an acronym for "Extended Grammatical Structuring/Standard."  This document is not intended to be a beginning tutorial, but rather a complete and detailed specification of all currently defined aspects of EGS, including its rules and limitations.  As such, this document is presented for completeness and is organized by structure, making the standard seem somewhat more complex than it is in ordinary usage.  Some of the constructions detailed below will appear only in special circumstances and are not otherwise common.  EGS acts as an extension of the standard grammatical structure of English in specific and well-defined ways.  As an extension of English, EGS is more a "style of writing" than a separate, or new language in and of itself. This document is a complete specification of the "style" and protocol that EGS follows.

Note:  This format specifies the structural organization within a file which contains only ASCII characters.

From here, you can:

Move next to the EGS Definition Beginning.

Jump ahead to the part on Grouping and Modularization

Jump ahead to the part on Statement Type Codes

Jump ahead to the part on Statement Specifications

Jump ahead to the part on Context Specifications

Jump ahead to the part on Referencing Statements

Jump ahead to the part on Bracketing Terms

Jump ahead to the part on Control of Special Characters

Return to the entrance of The Sethworks Mooseum Annex.

Return to The Sethworks Mooseum.

Send questions or comments to:
Jimbo9@aol.com (Web page editor),
or to:
F_landry@bbs.tka.com (Content Author),