Gama Specification 9 Elecpubs March 1999 PDF 498cace8ce

ELECTRONIC PUBLICATIONS STANDARD
GAMA SPECIFICATION NO. 9

Version 2.0
March 1999
General Aviation
Manufacturers Association
THIS PAGE INTENTIONALLY BLANK
GAMA ELECTRONIC PUBLICATIONS STANDARD
ELECTRONIC PUBLICATIONS STANDARD
GAMA SPECIFICATION NO. 9

Version 2.0
March 1999
Prepared and Published by:
General Aviation Manufacturers Association

1400 K Street NW, Suite 801
Washington, DC 20005
(202) 393-1500 Fax (202) 842-4063
www.generalaviation.org
All Rights Reserved. No part of this document may be reproduced

in any form without permission in writing from the publisher.
© Copyright 1994, 1999

Washington. D.C.
MARCH 1999 i
REVISION INFORMATION
Editor: Chairman - Electronic Publications Standard Committee

Washington, DC 20005
USA
Phone: (202) 393-1500
Fax: (202) 842-4063
May 1994 V 1.0

This revision is based upon the decisions and discussions put forth during the second GAMA
SPECIFICATION 9 Task Force meeting. This revision will serve as the working draft for review at the
GAMA SPECIFICATION 9 meeting dated May 25, 26 and 27 in Washington D.C.
June 1994 V 1.1
This revision is based upon the review completed at the GAMA SPECIFICATION 9 meeting held May
25-27, 1994 in Washington D.C. This final draft will be submitted to the GAMA Technical Policy
Committee at the June 23-24, 1994 meeting in Atlantic City, New Jersey, for final approval. It is
anticipated that this version will be published for general distribution shortly thereafter.
August 1994 V 1.2
This revision is based upon the meeting of the DTD working group held July 19th and 20th 1994
during which the Sections 3.4.3 and 3.5.2 Control File Schema’s as well as the Appendix 2 DTDs
were finalized. This version of the specification is the first issuance for publication.
October 1994 V 1.3
This version is based upon the meeting of the DTD working group held September 20th and 21st
1994 during which the five DTDs included in Appendix 2 were finalized. Additionally, this version
reflects the amendments resulting from the EPS Subcommittee meeting held September 22nd and
23rd 1994. These amendments include Data Exchange use of DTDs (3.1), support for gray scale and
color graphics (3.3.2) (5.3.2), use of color (5.2.7), annotations (7.3.1.F), and data integrity (7.3.7).
This version has been approved for general circulation by the GAMA Board of Directors.
March 1999 V 2.0
This version is of GAMA Specification 9 incorporates many editorial changes based upon the
meetings of the DTD working group and EPS subcommittee in July and October 1998, including the
removal of all Appendix information. Appendix 1, Extensions to the Electronic Publications Standard,
was removed due to the lack in industry need to standardize on operating controls and on-line
distribution of publication information. Appendix 2, Document Type Definitions was removed. The
GAMA DTDs are available on the GAMA World Wide Web site, http://www.generalaviation.org under
the “Publications” link.
ii MARCH 1999
Foreword
The GAMA Specification 9 - Electronic Publications Standard was made possible by the dedicated efforts of a
broad aviation industry coalition of both GAMA and non-GAMA member manufacturers, associations and
regulatory authorities. Since the first meeting in June of 1993, the EPS Subcommittee has met in San
Francisco, Wichita, Washington DC, Phoenix, and Ottawa. The meetings were well attended as a result of the
strong industry interest in this effort. Version 2.0 of the specification is the result of a need to maintain the
specification with the changing of technology and to better meet the need of the GAMA community by
changing the GAMA DTDs format and content to closely match the ATA Specification 2100 DTDs.
Sincere thanks are hereby extended to the following organizations for their contributions and participation in
the various meetings to draft this specification:
• Aircraft Technical Publishers*
• AlliedSignal Engines*
• AlliedSignal Commercial Avionics Systems*

• Bombardier Aerospace
• Cessna Aircraft Company*
• Dassault Aviation
• Federal Aviation Administration Aircraft Certification Service
• General Aviation Manufacturers Association
• Honeywell, Inc., Business and Commuter Aviation Systems*
• Pratt and Whitney Canada, Inc.
• Raytheon Aircraft Company*
• Rockwell Collins, Inc. Business and Commuter Aviation Systems*
• Sogitec
• Teledyne Continental Motors
* also participated in the Document Type Definition working group
MARCH 1999 iii

TABLE OF CONTENTS
1. Scope_____________________________________________________________________ 1
1.1 General________________________________________________________________________ 1
1.2 Aviation Technical Publications ___________________________________________________ 1
1.2.1 Legacy Data _________________________________________________________________________1
1.2.2 ATA Specification 100 and Specification 2100 (Digital Data Standard) __________________________2
1.2.3 EPS Specification Use Requirements _____________________________________________________3
1.2.4 Electronic Publication Options __________________________________________________________3
1.3 Specification Objectives __________________________________________________________ 3
1.3.1 End User Needs ______________________________________________________________________3
1.3.2 Manufacturer Needs___________________________________________________________________4
1.3.3 Design Goals ________________________________________________________________________4
2. Minimum and Recommended Retrieval System ___________________________________ 7
2.1 General________________________________________________________________________ 7
2.2 CD-ROM Electronic Publications Platform__________________________________________ 7
2.3 Online Electronic Publications Platform ____________________________________________ 7
3. Data Exchange_____________________________________________________________ 9
3.1 General________________________________________________________________________ 9
3.2 Electronic Text File Formats ______________________________________________________ 9
3.2.1 Minimum Requirements _______________________________________________________________9
3.2.2 Recommended Requirements ___________________________________________________________9
3.3 Electronic Graphics File Formats _________________________________________________ 10
3.3.1 Raster Text Pages____________________________________________________________________10
3.3.2 Raster Graphics _____________________________________________________________________10
3.3.3 Vector Graphics _____________________________________________________________________11
3.4 Medium and Method Of Data Exchange for Electronic Text and Graphics_______________ 12
3.4.1 Telecommunication __________________________________________________________________12
3.4.2 Compression _______________________________________________________________________12
3.4.3 Control Files - Transmittal_____________________________________________________________12
3.4.4 Media Formats ______________________________________________________________________13
3.4.5 Minimum Data Elements ______________________________________________________________13
3.4.6 Data Organization ___________________________________________________________________13
3.5 Method Of Data Exchange for Paper Source Documents ______________________________ 13
3.5.1 Minimum Data Elements ______________________________________________________________13
3.5.2 Control Files - Transmittal_____________________________________________________________13
4. Documentation and Packaging _______________________________________________ 15
4.1 General_______________________________________________________________________ 15
4.2 User Guide ____________________________________________________________________ 15
4.2.1 Paper _____________________________________________________________________________15
4.2.2 Online ____________________________________________________________________________15
4.3 Minimum Requirements_________________________________________________________ 15
4.3.1 Introductory Section _________________________________________________________________15
4.3.2 Table of Contents / Index______________________________________________________________15
4.3.3 Minimum Configuration and Performance ________________________________________________16
4.3.4 Discussion of Functionality ____________________________________________________________16
iv MARCH 1999
4.3.5 Installation Procedure ________________________________________________________________ 16
4.3.6 Error Codes and Trouble-Shooting______________________________________________________ 16
4.3.7 Terminology _______________________________________________________________________ 16
4.3.8 Operation Notes and Cautions _________________________________________________________ 16
4.4 CD-ROM Packaging ____________________________________________________________17
4.4.1 Labeling __________________________________________________________________________ 17
4.4.2 Operating Instructions _______________________________________________________________ 17
5. Text and Graphics Appearance _______________________________________________ 19
5.1 General _______________________________________________________________________19
5.2 Electronic Text Appearance Requirements __________________________________________19
5.2.1 Readability at Various Resolutions______________________________________________________ 19
5.2.2 Style Support ______________________________________________________________________ 20
5.2.3 Typefaces _________________________________________________________________________ 20
5.2.4 Distinguishing Titles_________________________________________________________________ 20
5.2.5 Tables ____________________________________________________________________________ 20
5.2.6 Character Set_______________________________________________________________________ 20
5.2.7 Use of Color _______________________________________________________________________ 21
5.3 Graphics Appearance____________________________________________________________21
5.3.1 Display of Raster Text Pages __________________________________________________________ 21
5.3.2 Display of Raster Graphics ____________________________________________________________ 21
5.3.3 Display of Vector Graphics ___________________________________________________________ 23
6. Authenticity Rules _________________________________________________________ 25
6.1 General _______________________________________________________________________25
6.2 Authenticity Guidelines for Page-Based Publications__________________________________25
6.3 Authenticity Guidelines for Pageless Publications ____________________________________25
6.4 Authenticity Guidelines for Bookless Publications ____________________________________27
7. Functionality _____________________________________________________________ 29
7.1 General _______________________________________________________________________29
7.2 Page-Based Publication Functionality ______________________________________________29
7.2.1 Browse / Traversal (Navigation) _______________________________________________________ 29
7.2.2 Cross Reference Links _______________________________________________________________ 29
7.2.3 Search ____________________________________________________________________________ 30
7.2.4 Retrieval Software Response __________________________________________________________ 31
7.2.5 Printing ___________________________________________________________________________ 31
7.2.6 Revision Identification (Tracking and Control) ____________________________________________ 32
7.2.7 Data Integrity ______________________________________________________________________ 32
7.2.8 Data Export________________________________________________________________________ 32
7.2.9 Help _____________________________________________________________________________ 32
7.3 Pageless Publication Functionality _________________________________________________32
7.3.1 Browse / Traversal (Navigation) _______________________________________________________ 32
7.3.2 Cross Reference Links _______________________________________________________________ 34
7.3.3 Search ____________________________________________________________________________ 35
7.3.4 Retrieval Software Response __________________________________________________________ 36
7.3.5 Printing ___________________________________________________________________________ 36
7.3.6 Revision Identification (Tracking and Control) ____________________________________________ 37
7.3.7 Data Integrity ______________________________________________________________________ 38
7.3.8 Data Export________________________________________________________________________ 38
7.3.9 Help _____________________________________________________________________________ 38
MARCH 1999 v
7.4 Bookless Publication Functionality ________________________________________________ 39
8. Operating Controls_________________________________________________________ 41
8.1 General_______________________________________________________________________ 41
8.2 Retrieval Software Controls______________________________________________________ 41
8.3 Keyboard Access and Navigation _________________________________________________ 41
8.3.1 Dialog Box Controls _________________________________________________________________41
8.3.2 Navigation and Keyboard Access within Dialog Boxes ______________________________________42
8.3.3 Navigation within Text or Image Retrieval Screens _________________________________________43
8.3.4 Control Key Shortcuts ________________________________________________________________43
8.3.5 Function Key Shortcuts _______________________________________________________________44
8.4 Retrieval Software Conventions __________________________________________________ 44
9. Associated Standards _______________________________________________________ 45
9.1 General_______________________________________________________________________ 45
9.2 Controlled Vocabularies_________________________________________________________ 45
9.3 Required Standards ____________________________________________________________ 45
9.4 Recommended Standards________________________________________________________ 46
10. GAMA DTD Information ___________________________________________________ 47
11. GLOSSARY OF ELECTRONIC PUBLICATION TERMS ________________________ 49
vi MARCH 1999
1. SCOPE
1.1 General
This specification was developed by the General Aviation Manufacturers Association (GAMA) Electronic
Publications Standard (EPS) Subcommittee to assist in the preparation of technical maintenance information
to be published on electronic media, and in the implementation of systems to retrieve, display and print
electronic publications.
The GAMA SPECIFICATION 9 Subcommittee began by evaluating the existing relevant standards and
determined that there was not a general aviation industry standard appropriate for the problem of converting
millions of pages of legacy (both Air Transport Association (ATA) and non-ATA conforming publications from
source documents existing either electronically or in paper). This specification is established as a guideline
for the transition into publishing and exchanging manufacturers' data electronically. Specifically, this standard
is intended for use when compliance with ATA Specification 2100 is inappropriate or impractical.
Additionally, this specification describes the minimum and recommended functional requirements that must
be met by computerized retrieval systems used to access aviation technical maintenance information.
The intent of this specification is to standardize the minimum computer delivery systems, distribution media,
system functionality and operating controls, text and graphics appearance, system documentation,
terminology and data exchange between manufacturers. Standardization is expected to enhance safety
through the elimination of problems caused by inconsistent results derived from disparate systems, and by
the minimization of training and equipment necessary to utilize electronic publications originating from the
multitude of general aviation manufacturers. Standardizing “look and feel" and “system usability" will expedite
the transition to the use of electronic publications.
This specification is not intended to affect the technical content of electronic publications. Technical content is
the responsibility of the producer of the publication in cooperation with the civil aviation authorities.
Questions on interpretation and proposed changes to this specification should be submitted to the General
Aviation Manufacturers Association, Electronic Publications Standard Subcommittee, Suite 801 1400 K
Street, NW, Washington, D.C. 20005.
1.2 Aviation Technical Publications
1.2.1 Legacy Data

The millions of pages of technical publications (maintenance manuals, structural repair manuals, wiring
manuals, illustrated parts catalogs, service letters and bulletins. etc.) currently being used every day in
general aviation constitute a body of information authored over a period of more than 50 years. This
information is collectively referred to as “legacy data".
The majority of these publications are not compliant with the ATA Specification 100, and an even greater
proportion was not created using electronic publishing systems. For these publications, the source
documents exist only in paper form.
A guiding concern of this standard is to identify a pathway whereby this legacy data can cost-effectively and
consistently be converted into electronic form for retrieval anywhere in the world using standard hardware
and software systems.
MARCH 1999 1
ATA
2100
COMPLIANT
SGML SOURCE
ATA 100 COMPLIANT

PAPER SOURCE
NON-ATA COMPLIANT
ELECTRONIC SOURCE
NON ATA COMPLIANT

PAPER SOURCE
Figure 1.1
General Aviation Legacy Data
1.2.2 ATA Specification 100 and Specification 2100 (Digital Data Standard)
While acknowledging that the tremendous efforts of the ATA working groups have produced a model
specification for in the creation of new publications destined for distribution on electronic media, the majority
of general aviation legacy data (as illustrated in figure 1.1) does not conform to these stringent standards.
The ATA Specification 2100 Digital Data Standard was developed by the airlines to promote data portability
between manufacturers and the airline's in-house publishing systems, since historically a substantial portion
of the information received had to be rewritten to conform to specific operating requirements. Extensive rules
were created to accommodate task-oriented maintenance instructions and provisioning information. General
aviation technical publications are not typically organized in such a manner. Conformance to ATA
Specification 2100, and accommodation to that level of information content, structure and tagging, would
require that almost all of the currently existing general aviation technical documentation be rewritten, a
solution as cost-prohibitive as it is unfeasible.
The challenge is the conversion of general aviation legacy data to electronic media while maintaining
compatibility with information that is authored in conformance with the ATA Specification 2100. As a cost-
effective solution, the GAMA SPECIFICATION 9 has adopted the most appropriate subset of the ATA
Specification 2100 requirements applicable to general aviation legacy data. As a result, information authored
in conformance with the ATA Specification 2100 is compliant with the GAMA SPECIFICATION 9. The less
stringent requirements of the GAMA SPECIFICATION 9 will allow the vast majority of the existing general
aviation publications to be cost-effectively converted from paper to electronic media using currently available
technology in one of the electronic publication options identified in this specification.
2 MARCH 1999
1.2.3 EPS Specification Use Requirements

To effectively use this specification, you must obtain ATA Specifications 100 and 2100 from:
Air Transport Association

1301 Pennsylvania Ave., NW
Suite 1100
Washington, DC 20004-1707
(202) 626-4000
http://www.air-transport.org/
ATA Specification 100 provides the authoring rules and content guidelines that were used to develop ATA
Specification 2100. ATA Specification 2100 contains the information needed to interpret and apply GAMA
Specification 9 and its associated DTDs.
1.2.4 Electronic Publication Options

This specification will present three approaches to the production and delivery of electronic technical
publications.
A. Page-Based Publications
Page-based electronic publications are the functional equivalent of “fiche on CD".
Navigation within a page-based publication, at a minimum, consists of an electronic table of
contents, the ability to turn pages forward and backward, and possibly to hyperlink to text and
images.
B. Pageless Publications
Pageless electronic publications present and distribute data as discreet elements (i.e.,
maintenance manual (MM) page blocks or illustrated parts catalog (lPC) sections) rather than
individual pages. The presentation to the end user is of scrolling text formatted similarly, but
not exactly, like the paper source document. Text and graphics may be displayed either
separately or in-line. Navigation functionality includes an electronic table of contents,
hyperlinking to text and images, full-text searches, and may also include bookmarks and
backtracking.
C. Bookless Publications
A bookless electronic publication maintains information in a database, with the information
retrieved through an inquiry of the system. This approach is consistent with the ATA
Specification 2100, and is viewed as a future direction for general aviation technical
publications once electronic publishing matures, and when the needs of the end user can be
designed into the publications during the initial authoring of publications.
1.3 Specification Objectives
1.3.1 End User Needs

This specification endeavors to satisfy the needs of that portion of the end-user community inexperienced
with computers and have had little or no exposure to electronic document retrieval systems.
A. Common Presentation Style
End users will benefit from a common presentation style, or look and feel, to provide them
with comfortable and familiar reference points when accessing electronic data from different
manufacturers.
B. Similar Platform Base
To avoid the burden of having to purchase, understand, and maintain different types of
computer systems to benefit from the use of electronic documentation, the end user will
MARCH 1999 3
greatly benefit from the identification of a common platform base for general aviation
electronic retrieval systems
C. Similar Software Base
The identification of a common software base for general aviation electronic retrieval systems
will relieve the end user of the need to purchase, learn, and maintain different types of
operating systems and user interfaces.
D. Common Features of Functionality
A standard suite of minimum functionality common to general aviation electronic retrieval
systems will reduce the cost to the end user for training and support, while eliminating
confusion and frustration.
E. Authenticity
The end user will need confidence in the authenticity and completeness of the electronic
information. There will be a responsibility to educate the end user concerning the fact that the
screen display of information and the original legacy data of that same information may
appear different, yet the content between the two presentations of the data is identical.
1.3.2 Manufacturer Needs
This specification endeavors to satisfy the needs of the manufacturers by presenting cost-effective solutions
incorporating current technology, appropriate for the conversion of legacy data and the authoring of new
publications.
A. Satisfy Users Needs
Manufacturers require a set of standards to which they can build their publications in order to
universally satisfy the mechanics, maintenance professionals, and support people who will have
access to this information.
B. A Direction for Future Development
This specification will provide manufacturers transitioning into electronic publishing systems with a
set of requirements to furnish to vendors that satisfies the issue of legacy data conversion, current
on-going publication, and the creation of new publications. Additionally, this specification will
endeavor to provide direction concerning emerging technologies and their appropriateness for
general aviation publications.
C. Compatibility of Data
A set of Data Exchange Standards is required to ensure data compatibility for interchange between
manufacturers (i.e. for the integration of various manufacturers' data into a single publication set) and
between publication authors and their electronic publication integrators.
This data exchange standard must provide compatibility guidelines for the various levels of data
enrichment (tagging) dictated by the publication method employed by the manufacturer (page-based,
page-less or book-less). Additionally, this standard must apply to both initial data exchange, and
revisions to that data.
1.3.3 Design Goals

This specification endeavors to identify solutions that are feasible for adoption and flexible for enhancement.
A. Feasible Methods for Paper to Electronic Conversion
The standard must focus on the use of cost-effective technology and techniques to make the
conversion of millions of pages of legacy data feasible. For example, to minimize the
complexity of migrating to new electronic publication authoring systems, SGML is employed
as a data exchange standard, not for delivery of data to the end user. This and other such
4 MARCH 1999
minimum subsets of the ATA Specification 2100 requirements provide reasonable electronic
publication guidelines appropriate for general aviation.
B. Flexibility to Innovate
This specification must allow manufacturers and electronic system designers the flexibility to
provide new system functionality and additional ways of enriching the information to satisfy
the unique needs of the aviation community.
MARCH 1999 5
2. MINIMUM AND RECOMMENDED RETRIEVAL SYSTEM
2.1 General
This section defines the system requirements for the end user to retrieve, display and print electronic
publications and is referred to throughout this specification as the "retrieval system.” At a minimum, the
retrieval system must support IBM®-compatible personal computers operating under Microsoft Windows®
version 3.11 or greater. This does not preclude other additional platforms from being utilized (i.e. Apple®/
Macintosh® or UNIX workstations.)
Additionally the minimum and recommended retrieval systems must be capable of supporting all of the
functionality of the “retrieval software”. “Retrieval software" is defined to include the documentation, text and
graphics appearance, functionality and operating controls defined in Sections 4, 5, 7, and 8 of this
specification.
This section also furnishes the end user with a recommendation of the most appropriate and cost effective
retrieval system components to acquire. Additionally, this recommendation provides guidance for developers
regarding the related performance expectations of end users. Due to the rapid development of personal
computers and the hardware-limited expansion of functionality that comes with the evolution of software, this
recommendation will be updated periodically.
As new media and methods of delivery of electronic publications are introduced, additional minimum and
recommended retrieval system configurations will be identified.
2.2 CD-ROM Electronic Publications Platform

The platform for a CD-ROM technical data retreival system should be a standard commercially available
computer system capable of running the most recent versions of the Microsoft Windows® operating system.
At the time of publishing this specification, an example of an acceptable configuration would be:
• Pentium®-based (or later) CPU
• 32 MB RAM
• 3 ½” floppy disk drive
• 800 MB hard disk drive
• CD-ROM drive
• Microsoft Windows95® or greater
• 17” or larger color monitor
• Microsoft Windows® accelerated graphic adapter 1024x768 or higher resolution
• 300 DPI or higher resolution Microsoft Windows®-compatible laser printer.*
Note:
A backup may provide additional beneficial functionality. This may also be desired (or required) for some
retrieval systems.
*Plotters may not be acceptable to print raster images
2.3 Online Electronic Publications Platform

For online retrieval, users should have a system comparable to that described in 2.1, above, with the addition
of a high-speed modem, ISDN or comparable technology, or direct Internet connection. Due to the rich
graphics content in much technical documentation, a low-speed online connection will not deliver adequate
document retrieval performance.
MARCH 1999 7
3. DATA EXCHANGE
3.1 General
This section describes the minimum requirements for electronic data exchange for both text and graphics, the
medium of that electronic exchange, and the rules for the exchange of paper source documents.
These guidelines are intended for use by the authors of electronic data and information integrators to facilitate
data exchange. They in no way imply requirements or methods for how that information should be distributed
to the end user.
3.2 Electronic Text File Formats

This subsection specifies the data exchange requirements for electronic (ASCII) text.
Electronic data conforming to the ATA Specification 2100 is in compliance with this subsection of this
specification.
The GAMA SPECIFICATION 9 Subcommittee has reviewed the ATA Specification 2100 DTDs and
determined that the following DTDs will be developed to accommodate the types of publications found in
general aviation legacy data:
• Airframe Illustrated Parts Catalog (AIPC)

• Airframe Maintenance Manual (AMM)
• Component Maintenance Manual (CMM)
• Engine Illustrated Parts Catalog (ElPC)
• Engine Maintenance Manual (EMM)
• Service Bulletins (SB)
• System Installation/Maintenance Manual (SIMM)
• Wiring Manual (WM).
Each of the GAMA SPECIFICATION 9 DTDs will accommodate all three types of publications (bookless,
pageless and page-based) identified in this specification. The DTDs developed for data exchange under this
section will be available on the GAMA web site, http://www.generalaviation.org.
3.2.1 Minimum Requirements

Electronic text data will consist of SGML-tagged ASCII Text conforming to a DTD listed in this specification.
These DTDs are available from GAMA.
3.2.2 Recommended Requirements

To provide for the required functionality identified in Section 7 of this specification, data files should contain:
• Tagging or a method to identify text that requires distinctive screen display and print attributes:
− Bold
− Italic
− Underline
− Highlight
− Reverse Video
MARCH 1999 9
− Special Characters
• Tagging to support the cross-referencing of text and graphics
• Consistent table creation methods (avoiding combinations of spaces, tabs, indents, computer
controlled, etc.)
3.3 Electronic Graphics File Formats

This subsection specifies the requirements that apply to all electronic graphic data.
Electronic data conforming to the ATA Specification 2100 is in compliance with this subsection of this
specification.
Note: For raster graphics, determination of appropriate resolutions should be made from a VGA screen, as
that is the lowest common denominator. The following are guidelines in determining appropriate resolutions:
• Text is legible at any normal working magnification

• Lines are not jagged at any normal working magnification
• Lines and/or text do not overlap (appear muddy).
3.3.1 Raster Text Pages

A. Minimum Requirements
Electronic raster text pages are required to be in a digital format that is Class* 1 CCITT
Group 4 TIFF scanned at 300 dots per inch
B. Recommended Requirements
Electronic raster text pages are recommended to be scanned at the Class* level appropriate
to adhere to the guidelines as identified in Section 3.3 of this Specification:
• Class* 1: CCITT Group 4 TIFF scanned at 300 dots per inch

• Class* 4: CCITT Group 4 TIFF scanned at 1200 dots per inch.
*Classes are for reference to ATA Specification 2100 graphic section but are not indicative of
compliance with the class attributes defined there.
3.3.2 Raster Graphics

Electronic raster graphics files are required to be in a digital format that is Class * 1 CCITT
Group 4 TIFF scanned at 300 dots per inch
Complex graphics (multiple individual illustrations on a single 8.5 x 11 page) should be
separated into individual illustrations (one illustration per file) when:
• Upon initial display on a VGA screen, the individual illustrations are not
distinguishable
• Separation of the illustrations would enhance the usefulness of the information.
10 MARCH 1999
Note: The separated illustrations should be individually captioned for use in Tables of
Content.
Recommended raster file format exchange options are as follows:
Monochrome electronic raster graphics files are recommended to be scanned at the Class*
level appropriate to adhere to the guidelines as identified in Section 3.3 of this Specification:

• Class* 4: CCITT Group 4 TIFF scanned at 1200 dots per inch.
*Classes are for reference to the ATA Specification 2100 graphic specification section but are
not indicative of compliance with the class attributes defined there.
C. Gray scale and color graphic support
General aviation legacy data may contains photographs and color illustrations which are not
accommodated by the ATA Specification 2100. The following raster file formats are
recommended for use in the exchange of gray scale and color graphic images:
1. Gray-scale
• TIFF using Packbit compression

• PCX.
2. Color
• PCX-16 colors
• PCX -256 colors
• PCX - 16.7 million colors
• Baseline JPEG.
3.3.3 Vector Graphics

Electronic vector graphics files are required to be in a digital format that is electronically
convertible to CClTT Group 4 TIFF.
Examples include:
• HPGL
• CGM
• IGES.
The following electronic vector graphics files are recommended in order to conform to ATA
Specification 2100 graphic section:
• CGM file conforming to ISO Standard lSO/lEO 8632:1992 version 3

• DWG or DXF.
MARCH 1999 11
3.4 Medium and Method Of Data Exchange for Electronic Text and Graphics
This subsection describes the requirements concerning the medium and method of data exchange for
electronic text and graphics.
3.4.1 Telecommunication
Telecommunication specifics are at the discretion of the exchanging parties.
3.4.2 Compression
Data compression algorithms are at the discretion of the exchanging parties.
3.4.3 Control Files - Transmittal

Control files will be used to identify and communicate pertinent information for each discreet element or
Minimum Revisable Unit*(MRU) during data exchange. Information provided by the control files will be used
to track revisions as well as furnish important data for indexing in the retrieval software.
The minimum elements that should be communicated (per minimum revisable unit as defined in Section 7.3.6
of this specification) in the control files are as follows:
Table 3-1
Control File for Pageless Publications
Field Name Description Data Examples
File name Electronic filename with path (as it appears on data \G4\AMM\32\01010001.TXT
exchange media, including path names.) \G4\AIPC\32\12345.TIF;
File format Format of the file. ASCII text; SGML; CGM; HPGL;
TIFF - CCITT G4
Document Type of publication. AIPC; AMM; CMM; EIPC; EMM;
type SB; WM;
MRU title Chapter, section, subject, pageblock, title, or figure “Landing Gear - Fault Isolation”;
caption). “Main Landing Gear Door
Assembly”
MRU ID Unique MRU Identifier: For MM or IPC text, the “32-03-03-001”
chapter sequence number; for service information “32-05-01 Figure 1”
text, the issue number; and for graphics, the unique “SB-32-115R2”
graphic reference in the text.
OI date Original issue date (using the format: YYYYMMDD). “19921005” = Oct. 5, 1992
Rev date Revision date (if applicable using the format 19940510 = May 10, 1994
YYYYMMDD).
ATA chapter ATA/GAMA chapter-section applicability (using the 32-01; 24-05
format CC-SS).
Reason Reason for revision (if applicable). Revised, New, Deleted
Comments Comments pertaining to the file. “To replace previous corrupt file”,
“Scanned at 600 DPI”
* Refer to Section 7 of this specification for a listing of minimum revisable units by publication.
The control file format will be comma-delimited ASCII text with field names, maximum lengths, and other
recommended elements as defined in Section 7 of this specification when available.
12 MARCH 1999
3.4.4 Media Formats
Disk and tape formats used in data exchange are at the discretion of the exchanging parties.
3.4.5 Minimum Data Elements

Individual data exchange elements will be consistent with the minimum revisable units as identified in Section
7 of this specification.
3.4.6 Data Organization

As indicated by ATA Specification 2100, documentation (electronic file or paper) must accompany the data
describing:
• Media specifications i.e., block, sector sizes, operating system (if applicable)
• Directory structure
• Files in each directory.
Recommendations for directory structuring (taking into consideration DOS limitations):
• Text and graphics should reside in separate directories

• Text MRUs for MMs and IPCs should be grouped by chapter
• Graphics for MMs and lPCs should be grouped by chapter
• Service information text should be grouped by type of publication
• Service information images should be grouped by type of publication.
3.5 Method Of Data Exchange for Paper Source Documents

This subsection describes the requirements concerning the method of data exchange for paper source
documents. At a minimum, paper source documents will consist of clean, legible originals. Whenever
possible, first generation publications are recommended.
3.5.1 Minimum Data Elements

Individual data exchange elements will be consistent with the minimum revisable units as identified in Section
7 of this specification.
3.5.2 Control Files - Transmittal

Control files will be used to identify and capture pertinent information for each discreet element (minimum
revisable unit) during data exchange. Information provided by the control files will be used to track revisions
as well as furnish important data for indexing in the retrieval software. For transmission of paper source
documents, the control file may also be furnished in paper.
The minimum elements that should be communicated (per minimum revisable unit) in the control files are as
listed in Table 3-2.
MARCH 1999 13
Table 3-2
Control File for Page Based Publications
Field Description Data Examples

Name
File name Electronic filename with path (as it appears on \G4\AMM\32\01010001.TXT
data exchange media, including path names.) \G4\AIPC\32\12345.TIF;
File format Format of the file. ASCII text; SGML; CGM; HPGL;
TIFF - CCITT G4
Document Type of publication. AIPC; AMM; CMM; EIPC; EMM; SB;
type WM;
MRU title Chapter, section, subject, pageblock, title, or “Landing Gear - Fault Isolation”;
figure caption). “Main Landing Gear Door Assembly”
MRU ID Unique MRU Identifier: For MM or IPC text, “32-03-03-001”
the chapter sequence number; for service “32-05-01 Figure 1”
information text, the issue number; and for “SB-32-115R2”
graphics, the unique graphic reference in the
text.
OI date Original issue date (using the format: “19921005” = Oct. 5, 1992
YYYYMMDD).
Rev date Revision date (if applicable using the format 19940510 = May 10, 1994
YYYYMMDD).
ATA ATA/GAMA chapter-section applicability (using 32-01; 24-05
chapter the format CC-SS).
Reason Reason for revision (if applicable). Revised, New, Deleted
Comments Comments pertaining to the file. “To replace previous corrupt file”,
“Scanned at 600 DPI”
The control file format will be comma-delimited ASCII text with field names, maximum lengths and other
recommended elements as defined in Section 7 of this specification when available.
14 MARCH 1999
4. DOCUMENTATION AND PACKAGING
4.1 General
This section describes the requirements for end user documentation and distribution packaging.
4.2 User Guide

End user documentation is required for the retrieval software and will be provided in two forms, electronic (on-
line help) and paper.
4.2.1 Paper
The paper user guide will contain, at a minimum, those requirements defined in section 4.3 of this
specification.
4.2.2 Online
The online user guide (the help system) will contain, at a minimum, those requirements defined in section 4.3
of this specification.
Additionally, online help will follow the Microsoft Windows® help system conventions, including:
• Context-sensitivity from within the retrieval software

• Search within the help system
• Use of bookmarks
• Use of annotations
• Ability to copy information to the Windows® Clipboard
• Ability to print topics.
4.3 Minimum Requirements

This subsection delineates the minimum requirements for the contents of both the paper and online
documentation.
4.3.1 Introductory Section

The end user documentation will provide an introductory section that will include:
• Overview of the structure of the user guide

• Discussion on how to use the manual
• Where to get technical spport.
4.3.2 Table of Contents / Index

The end user documentation must employ the use of both a table of contents and an index.
MARCH 1999 15
4.3.3 Minimum Configuration and Performance
A section of the end user documentation will contain a minimum configuration list and will discuss the
performance expectations of that minimum configuration. Additionally, a recommended configuration list may
be included in this section.
4.3.4 Discussion of Functionality

A complete description of product functionality must be included in the end user documentation.
4.3.5 Installation Procedure

A section of the end user documentation must contain step-by-step installation procedures including:
• First-time installation
• Data revision installation
• Retrieval software update installation.
4.3.6 Error Codes and Trouble-Shooting

A section of the end user documentation shall provide a list of all the retrieval software error codes (as they
appear in the program) and the steps the end user should perform to eliminate the problem.
4.3.7 Terminology
A section devoted to terminology used in the retrieval software shall be incorporated into the end user
documentation.
4.3.8 Operation Notes and Cautions

To appropriately set an end user's expectation level, a section of the end user documentation will contain
operation notes and cautions that will include:
• Retrieval software limitations

• Cautions concerning nomenclature in word searches
• Word search limitations or absence in page-based publications (see definition in Section 1.2.3 of this
specification.)
16 MARCH 1999
4.4 CD-ROM Packaging

This subsection covers CD-ROM packaging requirements and operating instructions.
4.4.1 Labeling
The following information is required on a printed CD-ROM label:
• Data supplier's identifier (manufacturer)

• Model (if appropriate)
• Disc set name
• Disc revision number
• CD issue date
• Physical disc number (1 of 3, 2 of 3, etc.)
• Disc contents.
4.4.2 Operating Instructions

Condensed operating instructions, independent of the user guide, should be provided. This document
(commonly referred to as a "quick start guide") should encompass:
• Retrieval software requirements

• First-time installation procedures
• Application start-up instructions
MARCH 1999 17
5. TEXT AND GRAPHICS APPEARANCE
5.1 General
This section describes the appearance requirements for the display of electronic text and graphics.
To accommodate the viewing limitations of a VGA screen, yet maintain publication authenticity, the following
global display rules apply to the electronic display of information:
• Information content between the paper and electronic information must be identical, except:
− Corrected errors in spelling (see Section 6.3 of this Specification)

− Corrected errors in numbering (see Section 6.3 of this Specification)
− Tables of contents and indices which are replaced by retrieval system functionality
− Relationships and subordination implied by indentation must be preserved
• Indentation size may differ between paper and electronic text to maximize the usage of the electronic
display area
• Typefaces may differ between paper and electronic text to maximize the readability of the electronic
text (including, but not limited to: body text, titles, and captions.)
• Typeface sizes may differ between paper and electronic text to maximize the readability of the
electronic text (including, but not limited to: body text, titles, captions.)
5.2 Electronic Text Appearance Requirements

This subsection contains the requirements for the display appearance of electronic text.
5.2.1 Readability at Various Resolutions

These tables describe the recommended maximum display resolution for each of several popular monitor
sizes and the recommended minimum Microsoft Windows® font size for each screen resolution.
Table 5-1
Recommended Maximum Resolution for Various Monitor Sizes
Monitor Size Maximum Display Resolution
14” 800 x 600
15” 800 x 600
17” 1024 x 768
19 or 20” 1600 x 1200
Table 5-2
Font Size rules for Display Under MS Windows
Resolution Minimum Font Size

640 x 480 8
800 x 600 8
1024 x 768 7
1280 x 1024 7
MARCH 1999 19
5.2.2 Style Support
The display electronic text should support any combination of the following attributes:
• Bold
• Italic
• Underline
• Highlight
• Reverse video
• Special characters
• Color (see Section 5.2.7)
5.2.3 Typefaces
Typeface support within the retrieval software should allow adjusting font size for appropriate screen display
and printed output.
Typeface support must be in accordance with GAMA Specifications 1 and 2. Refer to the display rules in
Section 5.1 of this specification for additional considerations.
5.2.4 Distinguishing Titles

Title display must be in accordance with GAMA Specifications 1 and 2. Refer to the display rules in Section
5.1 of this specification for additional considerations.
5.2.5 Tables
It is mandatory that table meaning be preserved in both display and print. Ruling lines in complex tables can
convey meaning, and therefore, the following guidelines should be used to select the appropriate display
method. Refer to the display rules in Section 5.1 of this specification for additional considerations.
Tables should be displayed as text when:
• The retrieval software is capable of generating ruling lines, or

• The lack of ruling lines does not affect the table's meaning.
Tables should be displayed as graphics when the lack of ruling lines does affect the table's meaning.
5.2.6 Character Set

To augment the limited number of special characters found in the extended ASCII range of common Microsoft
Windows® fonts (e.g., º, ± ¼, ½, ¾, £), any ISO standard entity set may be used. These entity sets should be
declared in the DTD. If additional characters are needed beyond those available in ISO entity sets, the user
should create a custom entity set with the additional characters required, declare the entity set in the DTD
and transmit the entity set, with a description of the characters needed, with the DTD.
20 MARCH 1999
5.2.7 Use of Color

Use of color within the retrieval software is allowed. However, in instances where color is the only means to
convey pertinent information (i.e. the existence of a hyperlink) an alternative identification method (i.e. cursor
change) must be provided for users of monochrome displays and users who are colorblind.
The use of color is acceptable in the following instances:
• Text and Image hyperlink references

• Word search results
• Notes, Warnings and Cautions
• Title strips
• Table headers
• Temporary revisions.
A. Recommended Use of Color

If color in text is used to distinguish warnings and cautions then the following colors should be used:
• For warnings use red

• For cautions use yellow.
If users are given the opportunity to change the colors displayed, warnings and cautions should adhere to the
colors above and not be changeable.
5.3 Graphics Appearance

This subsection contains the requirements for the electronic display appearance of graphic images.
5.3.1 Display of Raster Text Pages

To facilitate the cost-effective conversion of legacy data to electronic publications, the raster display of text
pages is allowed. Additionally, the raster display of tables may be necessary, as outlined in Section 5.2.5 of
this specification.
5.3.2 Display of Raster Graphics

The following minimum scanning and raster graphics display requirements may be augmented by:
• ATA Graphics Committee developing efforts

• IGE Functional Requirements.
A. Minimum Scanning Requirements

The minimum scanning requirements for source graphics and text pages to be presented as raster
images is Class 1*: 300 dots per inch resolution.
B. Recommended Scanning Requirements
Recommendations for scanning source graphics and text pages to be presented as raster images are
as follows:**
• Class 2*: 400 dots per inch resolution

MARCH 1999 21
• Image cropping for minimal white space

• Free of graphic "noise" (punch holes, etc.)
The following are guidelines in determining appropriate resolutions:
• Text is legible at normal working magnification

• Lines are not jagged at normal working magnification
• Lines and/or text do not overlap (appear muddy).
*Classes are for reference to the ATA Specification 2100 graphic section but are not indicative of
** For source graphics, determination of appropriate scanning resolutions should be done from a
VGA screen, as that is the lowest common denominator.
C. Screen Display Minimum Requirements
The minimum retrieval software requirements for screen display support are as follows:
• Support for Classes* 1-4 monochrome raster graphics:

− Class 1: scanned at 300 dots per inch resolution
• Support for image sizes up to and including 11 inches by 25 inches.
* Classes are for reference to the ATA Specification 2100 graphic section but are not indicative of
D. Gray Scale and Color Graphic Screen Display Recommendations
To accommodate the screen display of gray-scale and color graphic images found in general aviation
legacy data that are not supported by the ATA Specification 2100, the following raster file formats are
recommended to be supported by the retrieval software:
1. Gray-scale
• TIFF using Packbit compression

• PCX.
2. Color
• PCX - 16 colors
• PCX - 256 colors
• PCX - 16.7 million colors
• Baseline JPEG.
22 MARCH 1999
5.3.3 Display of Vector Graphics

A. Minimum Line Weights
For vector graphics, determination of appropriate line weights should be done from a VGA screen, as that is
the lowest common denominator. The following are guidelines in determining minimum line weights:
• Text is legible at normal working magnification

• Lines are not jagged at normal working magnification
• Lines and/or text do not overlap (appear muddy)
• All lines must be visible at the normal working magnification
This section is reserved for the future discussion of other Vector Graphics Display requirements.
MARCH 1999 23
6. AUTHENTICITY RULES
6.1 General
This section presents a set of authenticity rules for each of the three approaches to the production and
delivery of electronic technical publications defined in Section 1.2.4 of this specification. These rules are put
forth to identify and standardize those changes and compromises permitted by the transition to electronic
publications. These rules are designed to provide the end user with consistent levels of expectation across
systems, and thus instill a sense of confidence in the integrity of the information.
6.2 Authenticity Guidelines for Page-Based Publications

This subsection identifies the authenticity rules for page-based publications defined in Section 1.2.4 A of this
specification.
A. Content and Display
The entire publication, from beginning to end, will be available as raster images for viewing
and printing. An additional electronic Table of Contents may be provided for aid in
navigation.
B. Front Matter
As from the original paper source document.
C. Headers and Footers
As from the original source document. Additionally, Title Strips may be employed to carry
this, and other, information.
D. Page Numbers
As from the original source document.
E. Text and Graphics Display
F. Completeness
G. Correction of Errors
Since the raster images are obtained from the original source document and equivalency with
the paper is desired, correction of errors without the revision of the equivalent paper
publication or notice to the end user is not allowed.
H. Signatures for Approved Data
6.3 Authenticity Guidelines for Pageless Publications

This subsection identifies the Authenticity Rules for Pageless publications defined in Section 1.2.4 B of this
specification.
A. Content and Display
The following represent the Authenticity Rules governing the content and display of electronic
data in a Pageless publication:
• Text content between the paper and electronic information must be identical
• Relationships and subordination implied by indentation must be preserved
MARCH 1999 25
• Indentation size may differ between paper and electronic text to maximize the usage
of the electronic display area
• Typefaces may differ between paper and electronic text to maximize the readability
of the electronic text (including, but not limited to: body text, titles, and captions)
• Typeface sizes may differ between paper and electronic text to maximize the
readability of the electronic text (including, but not limited to: body text, titles, and
captions)
• Graphic content between the paper and electronic information must be identical,
except:
− Graphic "noise" may be removed from electronic graphics
− Electronic graphics may be cropped of white space
− Complex multiview graphics may be separated into individual files
• Logos may be replaced by equivalent text
• Pagination when printed will most likely not match the equivalent paper publication.
B. Front Matter
Portions of the equivalent paper publication front matter (e.g., title pages and list of effective
pages) if included should be identified "For Paper Reference Only" or may optionally be
excluded from the pageless publication.
Front matter, if included, must be accessible from the table of contents, and must appear in
its original location during “page turning" (i.e., the beginning of a chapter or the beginning of a
publication).
However, upon direct entry at the beginning of a publication or chapter, the user will be
brought to the logical beginning of the information, not the front matter.
C. Headers and Footers
The inclusion of repeating headers and footers in the electronic data is allowed.
The following identifying information is required to be visible whenever text or graphic images
are displayed by the retrieval software via a vehicle such as a title strip, status bar, caption
bar or about screen:
• MRU identity - title or illustration caption

• MRU revision date
• CD library
• CD issue date
• Manufacturer and model (if feasible).
Since this same information will be provided on the printed page, the inclusion of a Header
and a Footer in the data is unnecessary. Additionally, the repetitive appearance of Header
and Footer information can be intrusive to the reader while scrolling through pageless data.
D. Page Numbers
The inclusion of page numbers in the electronic data is allowed to facilitate reference to
equivalent paper publications
26 MARCH 1999
E. Text and Graphics Display

Although the equivalent paper publication may have text and graphics appearing on the
same page. it is acceptable that they be separated.
The following text and graphic screen display options are allowed:
• Simultaneous text and graphic display in a single window (in-line graphics)

• Simultaneous text and graphic display in separate windows (overlapping or side-by-
side)
• Singular display of text or graphic in a single window (with a method for switching
between text and graphics without an intermediate step).
F. Completeness
Except for the differences specifically defined in this section, a paper publication and a
pageless publication with the same title and revision level must have the same contents.
G. Correction of Errors
Errors identified during data conversion should be reported back to the originating author for
correction of the source documentation.
H. Signatures for Approved Data
Aviation regulatory authority approval signatures and signatures attesting to the source of
publication should be captured as raster images and made available within the electronic
version of the information.
I. Consistency in Terminology and Nomenclature
Since inconsistency in terminology and parts nomenclature within and between publications
will result in incomplete or erroneous word search results, it is recommended that
publications be reviewed for this potential problem prior to release as electronic publications.
If it is determined that the problem exists, a suitable notice should be given to the end user.
Any corrected or amended terminology or nomenclature must not be changed without also
revising the equivalent paper publication.
6.4 Authenticity Guidelines for Bookless Publications

This section is reserved for future discussion of bookless publications defined in Section 1.2.4 C of this
specification.
MARCH 1999 27
7. FUNCTIONALITY
7.1 General
This section describes the minimum functionality requirements for electronic document and graphics retrieval
software, referred to in this section as the "retrieval software". It is based upon a subset of the ATA
Specification 2100 General Functional Requirements as applicable to general aviation technical
documentation converted for electronic publication. This specification contains general requirements that
apply to all publications covered by the standards. All retrieval software must also conform to these
requirements.
7.2 Page-Based Publication Functionality

This subsection describes the requirements that apply to all electronic publications and retrieval software that
utilize raster images of text pages defined in Section 1.2.4 A of this specification.
7.2.1 Browse / Traversal (Navigation)

The following represents the retrieval software's minimum requirements for browsing and navigation:
A. Publication Front Matter Data
Front matter will be available as captured from the original source document.
B. TOC
The retrieval software will provide a table of contents for each publication that supports
logical structuring. The retrieval software must permit access to the publication via this table
of contents.
C. Illustrations and Tables
Illustrations and tables will be available as captured from the original source document. It is
recommended that all illustrations and tables that are uniquely identified with a caption be
accessible from a selection list.
D. History Lists (audit trail)
The retrieval software should maintain a history list of the documents and images traversed
in a session, and allow the naming and saving of all or part of that history list. The history list
will permit direct access to each listed document positioned either at the beginning of the
document or on a graphic zoomed out to display the full image.
7.2.2 Cross Reference Links

It is recommended that the retrieval software support navigational links between data. For all publications,
the retrieval software should support links where the original source document explicitly indicates a cross-
reference (e.g., See, Refer to ). The links should be able to connect information within a publication
(intrapublication) or between publications (interpublication).
The user should be able to select the links using direct point-and-click manipulation (hyperlink). Upon
selection of a link, the retrieval software will traverse to the other end (page) of the link directly (so long as
alternative cross-references are not available) without a need to go through intermediate steps.
Links should be visually distinguishable on the screen display.
Links should be supported from:
• Text to text
• Text to graphics
MARCH 1999 29
• Graphics to text
• Graphics to graphics
• Text to database
• Graphics to database
• Database to text
• Database to graphics.
7.2.3 Search
A. Word Search
It is recommended that the retrieval software be able to search throughout a publication for
every occurrence of a word, combination of words or alphanumeric strings, phrase or
number. The entire contents of text provided must be searchable except for common "stop"
or "noise" words (e.g., a, an, and. by. the). If there is a possibility that every occurrence of the
search expression will not be found, the user should be so advised.
The retrieval software should:
• either ignore differences in the case of alphabetic characters or provide a case-
insensitive option.
• either ignore differences in word pluralization or provide a plural-insensitive option.
• allow the use of a wildcard (*) to match any sequence of one or more trailing
characters at the end of a word.
• allow a search with a single missing character (e.g., 35?72)
B. Scope of Search (Domain)
The retrieval software should allow the search to be limited in scope to:
• A specific publication type

• A specific publication
C. Search Expressions
Search expression construction should support the following Boolean operators and proximity
statements:
• And
• Or
• And not
• Within 5 (before and after)
• User definable Within 1-99 (before and after)
D. Search Results
The search will return an unambiguous identifier (e.g., title) for each MRU (refer to Section
7.3.6 for a discussion of MRUs).
Search results will be presented as a summary. Occurrences of the search expression within
the MRU will be included with the summary. The retrieval software must provide a
30 MARCH 1999
mechanism to launch to any item selected. When a search result contains only one item, the
retrieval software shall present the item directly.
Displayed text search results will be distinguishable from the other text (i.e., highlighted or
inverse video).
7.2.4 Retrieval Software Response

A. Response Time
The following specific maximum response time requirements apply when operating on either
the minimum or recommended retrieval system configuration.
Word Search
During a word search, the retrieval software should display partial results if a search
cannot be completed within fifteen seconds. The search may optionally continue
during preliminary display.
Text and Graphic Display
Same requirements as Section 7.3.4 A 2.
B. In-progress Status Message
Same requirements as Section 7.3.4 B.
C. Process Interruption
Same requirements as Section 7.3.4 C.
7.2.5 Printing
A. Print Information
At a minimum, the retrieval software must provide the following information on all printouts:
• MRU Identity - Title or Illustration Caption

• MRU Revision Date
• CD Library
• CD Issue Date
Recommendations for inclusion on all printed pages produced by the retrieval software:
• System Date and Time of Print

• Manufacturer and Model (if feasible)
• A statement advising the user not to retain printed pages. For example:
"`This page must not be retained for future reference."
B. General Printing
The retrieval software must provide the following print options:
• "Print Screen" capability for the current screen (text and/or graphics).
• Print the current page
• Print the current MRU
The retrieval software may provide printing of the marked section of the graphic currently displayed.
MARCH 1999 31
C. Range Printing
The retrieval software will support the printing of a range of pages.
D. Summary Data
The retrieval software should be able to print any generated summary or selection list (i.e., a list of
search results or a list of bookmarks).
Additionally, the retrieval software should be able to print all tables of content.
7.2.6 Revision Identification (Tracking and Control)

A. Revised Material Identification
The retrieval software must be capable of displaying revision symbols as they appear in graphics. For
additional information, refer to GAMA Specifications 1 and 2.
B. Effectivity Identification and Control
Effectivity identification and control will be available as occurring in the original list of effective pages.
When applicable the recommendations occurring in Section 7.3.6 should also be used.
C. Presentation of Revision Information
The retrieval software will provide a method of displaying the title of the publication being viewed, and
the revision date of the current page via a vehicle such as a title strip, status bar or caption bar.
D. Temporary Revisions
The retrieval software must provide a method for visually distinguishing temporary revisions when the
equivalent paper publication uniquely identifies temporary revisions (i.e. "yellow sheets").
7.2.7 Data Integrity

Data integrity assurance will be available as via the original list of effective pages.
7.2.8 Data Export

The retrieval software may support the copying of a marked area of a graphic, at any magnification, to the
Microsoft Windows® Clipboard for incorporation into other Microsoft Windows® applications.
7.2.9 Help
The retrieval software will have the same requirements as Section 7.3.9.
7.3 Pageless Publication Functionality

This subsection describes the requirements that apply to all pageless publications and retrieval software that
utilizes the display of ASCII text rather than raster images of text pages as defined in Section 1.2.2 B of this
specification.
7.3.1 Browse / Traversal (Navigation)

The following represents the retrieval software's minimum requirements for browsing and navigation:
A. Publication Front Matter Data
Front Matter must be made available from the table of contents, and must appear in its original
location during "page turning" (i.e., the beginning of a chapter or the beginning of a publication).
32 MARCH 1999
However, upon direct entry at the beginning of a publication or chapter, the user will be brought to the
logical beginning of the information, not to the front matter.
Refer to the glossary of terms appended to this specification for more information on front matter.
B. TOC
The retrieval software will provide a table of contents of text and graphic minimum revisable units for
each publication that supports such structuring. The retrieval software must permit access into the
publication via this table of contents.
C. Illustrations and Tables
The retrieval software will support the display of any illustration or table included, or referred to, in
the text.
Illustrations and tables (according to the rules defined in Section 5.2.5) will be available as scanned
from the original paper source document. It is recommended that all illustrations and tables that are
uniquely identified with a caption be accessible from a selection list.
The following text and graphic screen display options are allowed:
• Simultaneous text and graphic display in a single window (inline graphics)

• Simultaneous text and graphic display in separate windows (overlapping or side-by-side)
• Display of text or graphic in a single window (with a method for switching between text and
graphics without an intermediate step)
D. Backtracking
The retrieval software will maintain a record of the user's navigation within and across publications
during the current session. Departure points (the text being displayed at the time of leaving a MRU)
will be tracked, and a mechanism will be provided to directly select and return to any of these
departure points.
The retrieval software should keep track of a minimum of the last 24 departure points during the
current session.
E. Bookmarks
The retrieval software will provide support for user-definable bookmarks. The bookmark will record a
specific position in the publication. The retrieval software will provide the user with a mechanism to
access the list of previously defined bookmarks, and the ability to navigate to a bookmark's location.
The retrieval software should permit the saving of user-defined bookmarks such that they can be
recalled and re-used in future sessions.
Upon revision of the publication by the author, the system relocated position of the bookmarks
should conform to the following rules:
• If a particular MRU contains a bookmark and that MRU has not been revised, the position of
the bookmark is preserved within the MRU.
• If an MRU containing a bookmark has been revised, but the text containing the bookmark has
not changed, the bookmark is preserved within the MRU.
• If an MRU containing a bookmark has been revised and the text containing the bookmark has
changed, the bookmark repositions to the beginning of the MRU.
• If an MRU containing a bookmark is eliminated, the bookmark is orphaned and repositions to
the next higher level within the publication (i.e. section, chapter, title page).
MARCH 1999 33
F. Annotations
To accommodate the creation of reference work aids, the retrieval system may provide an
annotations function. Annotations can be used, for example, to record cross references to other
publications, to note the location of tools or consumables, for reminders of product repair and
modifications and to note product support contacts and phone numbers.
The retrieval software may provide support for user definable annotations. The annotations function,
if implemented, must comply with the following requirements:
• Annotations must be clearly distinguishable (in a separate pop-up dialog box) from the
author's unaltered source information.
• Annotations must be stored as a separate data file from the author's unaltered source
information.
The annotations function, if implemented, should also comply with the following requirements:
• Text may be input as an annotation at a user-defined specific position in the publication.

• The retrieval software should provide the user with a mechanism to access the list of
previously defined annotations, delete previously defined annotations and the ability to
navigate to an annotation's location.
• The retrieval software should permit the saving of user-defined annotations such that they
can be recalled and re-used in future sessions.
• Upon revision of the publication by the author, the system-relocated position of the
annotations should conform to the rules identified for bookmarks above. The retrieval
system should indicate to the user if the attachment position has been modified due to
revision of the publication and enable a means of reattachment to a new position.
• Annotations should record the date last updated and the originator's identity.
G. History Lists (audit trail)

The retrieval software will maintain a history list of the MRUs and images traversed in a session, and
allow the naming and saving of all or part of that history list. The history list will permit directly
accessing each listed MRU positioned to either the beginning text or graphic zoomed out to display
the full image.
H. Direct Access to MRUs
The retrieval software may provide the user with the means to display any MRU by direct reference
to the MRU through for example a system index number.
7.3.2 Cross Reference Links

The retrieval software will support navigational links between data. For all publications, the retrieval software
will support links where the text explicitly indicates a cross-reference (e.g., See Refer to). The links must be
able to connect information within a publication (intrapublication) or between publications (interpublication).
The user must be able to select the links using direct point-and-click manipulation (hyperlinking). Upon
selection of a link, the retrieval software will link directly to the hyperlink target going through intermediate
steps, so long as alternative cross references are not available.
Links must be visually distinguishable on the screen display.
If applicable, links must be supported from:
• Text to text
• Text to graphics
• Graphics to text
34 MARCH 1999
• Graphics to graphics
• Text to database
• Graphics to database
• Database to text
• Database to graphics
7.3.3 Search
A. Word Search
The retrieval software must be able to search throughout a publication for every occurrence of a
word, combination of words or alphanumeric strings, phrase or number. The entire contents of text
provided must be searchable except for common "stop" or "noise" words (e.g., a, an, and, by, the).
The retrieval software will:
• either ignore differences in the case of alphabetic characters or provide a case-insensitive
option.
• either ignore differences in word pluralization or provide a plural-insensitive option.
• allow the use of a wildcard (*) to match any sequence of one or more trailing characters at
the end of a word.
• allow a search with a single missing character (e.g., 35?72).
B. Scope of Search (Domain)

The retrieval software will allow the search to be limited in scope to:
• A specific publication type

• A specific publication
C. Search Expressions
Search expression construction must support the following Boolean operators and proximity
statements:
• And
• Or
• And not
• User definable Within 1-99 (before and after)
D. Search Results
The search will return an unambiguous identifier (e.g., title) for the MRU.
Search results will be presented as a summary. Occurrences of the search expression within the
MRU will be included with the summary. The retrieval software must provide a mechanism to launch
to any item selected. When a search result contains only one item, the retrieval software shall
present the item directly.
In the data, search results will be distinguishable from other text (i.e., highlighted or inverse video).
MARCH 1999 35
7.3.4 Retrieval Software Response
The following specific maximum response time requirements apply when operating on either the minimum or
recommended retrieval system configuration.
A. Response Time
During a word search, the retrieval software will display partial results if a search cannot be
completed within fifteen seconds. The search may optionally continue during preliminary display.
The following specific maximum response time requirements apply:
• Publication front matter data will be displayed within 15 seconds of request.

• TOC data will be displayed within 15 seconds of request.
• A specific illustrations shall be displayed within 10 seconds of request.
• Intrapublication links shall be accomplished within 5 seconds.
• Interpublication links shall be accomplished within 15 seconds.
B. In-progress Status Message

The retrieval software will at a minimum provide a system busy icon for operations estimated to take
longer than three seconds. It is recommended that a status message be presented while processing
operations that exceed fifteen seconds are being performed.
C. Process Interruption
The retrieval software must provide a simple means for the end user, if desired, to interrupt any
process operation (e.g., search, print, etc.). Upon such interruption, the retrieval software will return
the user to the point he was at immediately before the interrupted process started.
7.3.5 Printing
A. Print Information
At a minimum, the retrieval software must provide the following information on all printouts:
• MRU identity - title or illustration caption, MRU revision date
• CD library
• CD issue date
The following are recommended for inclusion on all printed pages produced by the retrieval software:
• Retrieval software date and time of print
• Manufacturer and model (if feasible)
• A statement advising the user not to retain printed pages. For example:
"This page must not be retained for future reference."
B. General Printing
The retrieval software will provide the following print options:
• A "Print Screen" facility for the current screen (text and/or graphics).
• Print the page currently displayed
• Print the graphic currently displayed
• Print the MRU currently displayed
36 MARCH 1999
The retrieval software may provide the following print options:
• Print the currently marked text
• Print the marked section of the graphic currently displayed
C. Range Printing
The retrieval software will support the printing of the following range options:
• MRU
• MRU and its associated graphics only
• A range of MRUs.
D. Summary Data
The retrieval software will be able to print any generated summary or selection list (i.e., a list of
search results or a list of bookmarks).
Additionally, the retrieval software will be able to print all tables of content.
7.3.6 Revision Identification (Tracking and Control)

A. Revised Material Identification
1. Text
The retrieval software must be capable of displaying revision symbols (e.g., revision bars - |
or R). For additional information, refer to GAMA Specifications 1 and 2.
2. Graphics
The retrieval software must be capable of displaying revision symbols as they appear in
graphics. For additional information, refer to GAMA Specifications 1 and 2.
B. Minimum Revisable Unit - Granularity
To accommodate revisioning and indexing of pageless information, the publication's data is divided
into logical groupings.
Since the concept of individual pages is not utilized in a pageless representation of electronic data,
the ability to record revisions for a specific page as they appear on the paper may not be possible.
Therefore, a logical subdivision of the data is identified as appropriate for carrying revision
information. That subdivision is referred to as a Minimum Revisable Unit (MRU), and serves as the
basis for electronic table of contents and data exchange.
For graphics, a single graphic is the minimum revisable unit. The following table depicts the rules for
text MRUs:
Table 7-1
Rules for Text MRUs
Publication Type Revisable Unit
Maintenance Manual (MM) type of Page block, or task, or comparable

publication unit
Illustrated Parts Catalog (IPC) Parts list pertaining to a figure
Service information Complete service information
Airworthiness Directives (AD) Complete AD
MARCH 1999 37
C. Minimum Revisable Unit-Based Revision Dates
Revision marking and dating applies to the entire MRU. Upon revising an MRU, all prior revision bars
are eliminated and only the revised content for this revision will be marked.
D. Effectivity Identification and Control
At a minimum a list of effective MRUs will be presented which includes the MRU identity and revision
date.
The original paper's List of Effective Pages (LEP) may be included as a reference tool for personnel
supporting customers with paper publications. This information may not be relevant to the electronic
version of the information.
It is recommended that an LEP be marked "For Paper Reference Only" when included with the
electronic data.
E. Presentation of Revision Information
The retrieval software will provide a method of displaying the title of the MRU being viewed, and it’s
revision date via a vehicle such as a title strip, status bar or caption bar.
F. Temporary Revisions
The retrieval software must provide a method for visually identifying temporary revisions to the
equivalent paper publication.
7.3.7 Data Integrity

The retrieval software will accommodate data integrity assurance by providing a record of MRU revision
activity. The user must be provided a means of determining which MRUs have been revised in the current
revision as well as the date of last revision for every MRU in the publication.
7.3.8 Data Export

A. Text
The retrieval software will support the copying of any amount of marked text (within the limitations of
the end user's hardware and software) to the Microsoft Windows® Clipboard for incorporation into
other Microsoft Windows® applications.
B. Graphics
The retrieval software will support the copying of a marked area of a graphic, at any magnification, to
the Microsoft Windows® Clipboard for incorporation into other Microsoft Windows® applications.
7.3.9 Help
The retrieval software will provide help function via a single action on the keyboard or other input device.
The online help function will contain, at a minimum, those requirements defined in Section 4.3 of this
specification. Additionally, online Help will follow the Microsoft Windows® Help system conventions,
including:
• Context-sensitivity from within the retrieval software
• Search within the Help system
• Use of Bookmarks
• Use of Annotations
• Ability to copy information to the Microsoft Windows™ Clipboard
• Ability to print Topics
• History tracking within the Help system
38 MARCH 1999
7.4 Bookless Publication Functionality
This section is reserved for future discussion of the functionality of bookless publications defined in Section
1.2.4 C.
MARCH 1999 39
8. OPERATING CONTROLS
8.1 General
This section describes the minimum requirements for retrieval software operating controls that shall conform
to the following Microsoft Windows®; conventions as defined in the Microsoft Common User Access -
Advanced Interface Design Guide. Additionally operating control conventions are specified to standardize the
end user control of the functionality defined in Section 7.
8.2 Retrieval Software Controls

The retrieval software may support the following types of operating controls and functionality:
• Pull down menus
• Dialog boxes
• Buttons
• Keyboard shortcuts
8.3 Keyboard Access and Navigation

This subsection describes appropriate keyboard and control activities within dialog boxes and retrieval
screens and identifies the minimum requirements for retrieval software-wide keyboard response.
8.3.1 Dialog Box Controls

Microsoft Windows® standard dialog box controls, as described in the Common User Access - Advanced
Interface Design Guide, should be used for all dialog boxes.
MARCH 1999 41
8.3.2 Navigation and Keyboard Access within Dialog Boxes

Table 8-1
Navigation and Keyboard Access within Dialog Boxes
Key Conditions Action

Alt+Mnemonic Control buttons Operates the Control
(Underlined letter on a
control label)* Option Buttons Selects the Control
Check Boxes
List Boxes (all) Moves the focus to the control

Enter Default command button (if Operates the control
present)
Selected command button (if Operates the control

no default button is present)
Esc All Operates the Cancel or Close button if present
Spacebar Command button with focus Operates the control
Option Button with focus or Selects the control

Check box with focus
Text input field Inserts a space

Tab All Moves the focus (active state) to the next control (button,
check box, drop down, etc.). Typically, focus movement
is from left to right and from top to bottom, and that
sequencing has been employed except in those
instances where a more appropriate route has identified.
Shift+Tab All Reverses the Tab navigation order by moving the focus
to the prior control.
Arrow Keys Option Buttons (Group) Selects the next button, wraps at top and bottom of group
Check Boxes Moves focus to next button without selection, wraps at

top and bottom of group
List Boxes Selects next item, does not wrap to top of list
Spin Boxes Increases or decreases value, wraps at highest and

lowest values
Text Boxes
Moves insertion to the left, right, up or down
Alt+Down Arrow Drop-down List Boxes and Toggles between collapsed and expanded state of active
Alt+Up Arrow Drop-down Combo Boxes drop-down.
Del Text Input Fields Deletes selected text
(text selected)
Text Input Fields Deletes character just right of the insertion point
(no text selected)
Backspace ← Text Input Fields Deletes selected text
(text selected)
Text Input Fields Deletes character just left of the insertion point
(no text selected)
Ins Text Input Fields Toggles between insert mode and Over type mode
* No Alt+mnemonic combinations are reserved or recommended by Microsoft, however when a HELP control
button is present, its shortcut key combination is Alt+H. All Alt+ mnemonic combinations must be unique
within the active dialog box(es).
42 MARCH 1999
8.3.3 Navigation within Text or Image Retrieval Screens
Table 8-2
Navigation within Text or Image Retrieval Screens
Key Conditions Action

Home All Moves cursor to the beginning of the current
page
End All Moves cursor to the end of the current page
Ctrl+Home All Moves cursor to the beginning of the current

document
Ctrl+End All Moves cursor to the end of the current

document
Page UP Within a publication Scrolls up a screen
Page Up Within an image Scrolls up a screen (maintaining zoom)
Page Down Within a publication Scrolls down a screen
Page Down With a graphic Scrolls down a screen (maintaining zoom)
Ctrl+Page Up Within a publication Beginning of previous publication (MRU)
Ctrl+Page Up Within a graphic Displays previous graphic
Ctrl+Page Down Within a publication Beginning of next publication (MRU)
Ctrl+Page Down Within a graphic Displays next graphic
8.3.4 Control Key Shortcuts

Table 8-3
Control Key Shortcuts
Key Action
Ctrl+C* Copy to the Windows Clipboard
Ctrl+V* Paste from the Windows Clipboard
Ctrl+P** Open the Print dialog box
* Recommended by Microsoft
** Suggested by Microsoft
MARCH 1999 43
8.3.5 Function Key Shortcuts
Table 8-4
Function Key Shortcuts
Key Action
F1* Brings up Help
Alt+F4* Close the Application
* Recommended by Microsoft
8.4 Retrieval Software Conventions

This section is reserved for a future discussion of operating control conventions to be used to standardize the
presentation to the end user of the functionality defined in Section 7.
44 MARCH 1999
9. ASSOCIATED STANDARDS
9.1 General
This section identifies additional controlled vocabularies and technical specifications to be used in the
creation of electronic publications and retrieval software. The consistent use of controlled vocabularies is
necessary to accommodate word search in electronic publications in fulfillment of the end user's
expectations. Technical specifications are necessary to accommodate data exchange and retrieval software
interchangeability as well as standardize content, format and structure.
9.2 Controlled Vocabularies

The consistent use of nomenclature across publications facilitates electronic word searching and eliminates
information ambiguity.
As a minimum requirement, Webster's Dictionary shall be used for English language definitions and spelling
(except for new terminology that has not yet been incorporated.)
AECMA Simplified English is recommended for the unambiguous and consistent use of the English language.
9.3 Required Standards

The following constitutes required Standards:
• ISO 8879 - Standard Generalized Markup Language
• ISO 9660- This Standard describes the CD-ROM formatting to accommodate universal
interchangeability.
Content Specifications
• ATA Specification 100
• ATA Specification 2100
Available From:
Air Transport Association
1301 Pennsylvania Ave., NW
Suite 1100
Washington, DC 20004-1707
(202) 626-4000
http://www.air-transport.org/
• GAMA Specification 1 Pilots Operating Manual

• GAMA Specification 2 Maintenance Manual
Available From:
Washington, D.C. 20005
(202) 393-1500
http://www.generalaviation.org
MARCH 1999 45
9.4 Recommended Standards

The following is a list of recommended Standards for reference:
• Guide to Simplified Graphics - Technical Report No. 92-1
Available From:
Aerospace Industries Association
1250 Eye Street, NW
Washington, DC 20005 - USA
Technical Specifications:
• Aldus TIFF
Available From:
Aldus Corporation
411 First Ave. S Suite 200
Seattle, WA 98104- USA
• ISO CGM Specification #
Available From:
ANSI
1430 Broadway
New York, NY 10018 - USA
• ISO CCITT Specification # [what belongs here?]
Available from:
CCITT
Place des Nations
12111 GENEVA 20- Switzerland
• Common User Access - Advanced Interface Design Guide
Available from:
Microsoft Corporation
One Microsoft Way
Redmond, WA 98052-6399 - USA
46 MARCH 1999
10. GAMA DTD INFORMATION

The GAMA DTDs are designed for the conversion of legacy publications, or the generation of new
publications, in a structured format based on the ATA Specification 2100. Except for the inclusion of DTD
changes related to GAMA, the DTDs are formatted to conform to ATA Specification 2100 DTD style guides.
The GAMA DTDs are available at the GAMA World Wide Web site, http://www.generalaviation.org under the
“publications” link.
The GAMA DTDs derived from their equivalent ATA Specification 2100 DTD are listed below:
GAMASB.DTD
GAMAWM.DTD
GAMAAMM.DTD
GAMAAIPC.DTD
GAMAEMM.DTD
GAMAEIPC.DTD
GAMASIMM.DTD
The GAMASIMM.DTD provides a way to convert legacy data into structured information. It can be modified
by users as needed to support internal data conversion projects. However, remember to change the DTD
public identifier to ensure that only the modified DTD is used during document instance validation.
MARCH 1999 47
11. GLOSSARY OF ELECTRONIC PUBLICATION TERMS

Aircraft Specific - Information that relates to a particular aircraft based upon any of several factors of
Effectivity, (i.e. manufacturer, model number, part number, serial number...)
Annotations - Comments created by the user and associated with a location within the text or graphic of an
electronic publication. Annotation place holders permit the viewing of previously saved annotations via a pop
up text display. From a selection list of annotations, the user can hyperlink to the particular location or range
of text where the annotation was originally defined.
ANSI - American National Standards Institute
11 West 42nd Street
New York, NY 10036- USA
(212) 642-4900
ASCII - American Standard Code for Information Interchange; a binary code representing alphanumeric
characters that permit the exchange of data between most minicomputers and personal computers utilizing
different operating systems.
ATA - Air Transport Association
1301 Pennsylvania Ave, NW
Washington, D.C. 20004-1707 - USA
(202) 626-4000
ATA Specification 100 - Air Transport Association's specification that provides guidance to the content and
format of aircraft maintenance publications.
ATA Specification 2100 - Air Transport Association's specification that establishes standards for the
authoring, interchange, delivery and use of digital data produced by aircraft, engine and component
manufacturers.
Authoring - Refers to the process of creating new information.
Authoring systems - Can include a wide range of systems from word processors to electronic publishing
systems.
Backtracking - The retrieval software's ability to keep track of prior screens viewed when a user departs to
other screen views. This allows the user to return to a limited number of stored prior views at a later time
during a search, usually through the use of a function key command or macro.
Bitmap Image - is a raster image made up of pixels, or dots, that are either black and white (bilevel), shades
of gray (gray-scale), or color. Windows Bitmap (BMP) is a popular format among PC software exchange
options.
BMP - (Bit MaP) Windows graphics format that may be device dependent or independent. Device
Independent BMP files (DIB) are coded for translation to a wide variety of displays and printers.
Bookless Publications - Electronic publications in that the information is maintained via a database of task
based elements that do not require the information to be structured in books. The ATA Specification 2100's
use of SGML and SFQL based retrieval systems are an example of Bookless Publications.
Bookmarks - A bookmark is a place holder that marks the current view. Bookmarks allow the user to identify
a particular location in the text that can be directly accessed in future sessions.
Boolean Search - A search method used to access information in a database by specifying search criteria
based upon Boolean operators such as AND, OR and NOT. Boolean operators help to create a true or false
filter to narrow the scope of information to be retrieved.
Browse / Browsing - Method of locating information in a database by utilizing either a table of contents or
moving through the document by using its logical structure.
Button - Buttons are click-on icons that appear throughout windows programs in such places as toolbars and
dialog boxes.
MARCH 1999 49
CAD - Computer Aided Design. Refers to the use of computers to design products. CAD systems are
workstations or PCs using CAD software and graphic input devices. CAD software is used for generic design
or specialized uses, such as architectural, electrical and mechanical designs.
CALS - Computer-Aided Acquisition and Logistics Support. A U.S. Department of Defense 1985 initiative to
provide a framework for the transmission and usage of information on weapon systems in electronic form.
The support of specific standards by the CALS initiative has accelerated industry-wide adoption of these
standards, including CCITT Group IV and SGML.
CCITT - Consultative Committee on International Telegraphy and Telephony. This international advisory
committee originally established under the United Nations endorses a variety of communications usage
standards, particularly facsimile and image compression and decompression, including the CCITT Group 3
and Group 4 standards that are used widely in image storage and transmission.
CCITT
Place des Nations
12111 GENEVA 20 - Switzerland
CD-ROM - Compact Disc Read Only Memory. Designed primarily for use as an electronic publishing medium,
a CD-ROM is capable of storing text, graphics and audio data. Unlike hard disks and floppy disks, a CD-ROM
is read only, meaning it does not permit the user to write information to the disc. A single CD-ROM can store
up to 660 megabytes of information and has a storage capacity equivalent to 550 1.2 MB floppy disks.
CD-ROM Drive - Device connected to a computer for reading data from CD-ROMs.
CGM - Computer Graphics Metafile. The ISO standard format that identifies the three versions of metafiles
used to exchange vector data and textural characters. Often used as a cross-platform exchange option, CGM
store graphics primarily in a vector format but also provides a raster format enabling color fills.
Compact Disc - Commonly referred to as a CD. A CD is a molded plastic disk on which data is recorded as
microscopic pits to be read optically by a laser beam.
Controlled Vocabularies - A specific source or sources of words, phrases, and terminology in an
alphabetical arrangement accessed to provide uniform cross-referencing.
CPU - Central Processing Unit. Most commonly refers to the part of a computer that controls translation and
execution of processing instructions. Informally, the term CPU is sometimes used to refer to a single PC
workstation unit.
Cross Reference Links - Connection of information within a publication or between publications where the
original source document indicates a cross-reference.
Database - A collection of electronically stored data that is structured and organized to facilitate efficient
retrieval of information.
Database Preparation Software - Software used to organize and index a database.
Data Capture - The process of converting data from non-electronic formats (such as paper, photographs,
drawings, etc.) into an electronic format that makes possible the retrieval, storage and modification of the
data on a computer system.
Data Conversion - The process of converting information from one electronic format to another. For
example, text information can be converted from WordPerfect to ASCII and graphic information can be
converted from an uncompressed bitmap image to a compressed format like CCITT Group 4 Fax.
Data Refinement - The Process of converting data into an enhanced format based upon the content,
structure and meaning of the data. This refinement process may involve adding special tags identifying the
documents structure or generating specialized indexes and a table of contents.
Dialog Box - A window that displays options available within a particular command. For example, a print
dialog box might display options for printing the whole document, a range of pages within a document, or only
the current page.
Digital - Relative to computer systems, refers to data that is composed of a series of discreet, fixed values
such as single digits or characters. Digital information is recorded in a binary notation format.
50 MARCH 1999
Drive - A computer device used to read from and in some cases when to an electronic storage medium . The
most widely used electronic storage medium are optical or magnetic.
DTD - Document Type Definition. The programmatic rules and format definitions that describe the format
commands (tags) used to define content and structure in an SGML document.
DWG - The native AutoCAD 3-D vector file format that has become a standard due to its significant market
share.
DXF - Drawing Exchange Format. The AutoCAD® 2-D vector file format used by many CAD systems to
import and export for graphics interchange.
Element - (1) The discrete components defined in a Document Type Definition (DTD); (2) the individual units
of information that comprise an electronic publication (e.g., text page blocks, tables, and figures).
End User - The individual who uses software or hardware products and does not resell it to others.
EPS - Electronic Publication Standard. The GAMA Specification 9, which as an alternative to the ATA
Specification 2100, provides guidance for the transition to electronic publications by defining computer
systems, data exchange, text and graphics appearance, functionality and operating controls.
Flight Operations Information - The technical publications that support the operation of aircraft (e.g., Flight
Manuals, Pilots Handbooks, Weight and Balance Manuals) which may be included in collections of electronic
publications for reference during aircraft maintenance.
Front Matter - Data found at the beginning of a document, chapter or section that is general to the element.
Functionality - Performing tasks and operations by design.
Full Text Searching - Also known as Full Text Retrieval (FTR). The ability to use a word or words contained
within an electronic document as the criteria for retrieving information in a document Full text - searches can
be based upon a single word or words in combination with other words. Words within the electronic document
are indexed to accommodate this full text searching capability.
GAMA - General Aviation Manufacturers Association
Washington, D.C. 20005
(202) 393-1500
www.generalaviation.org
Graphics - Visual data. This includes photographs, line drawings, computer-generated artwork, and graphs.
Graphics can be entered into the computer using scanners, drawing programs, cameras, and graphics tables.
GUI - Graphical User Interface. A layer of software that allows the user to interact with the computer by
choosing items from menus or selecting icons from the screen, usually with a mouse. The Macintosh® Finder
and Microsoft Windows® are examples of GUl environments.
Hard Disk - Fixed disk media; generally internal, high-speed, high-capacity, rotating magnetic disk.
History List - A list of the MRUs and images traversed during a session, for use in direct accessing of each,
and the naming and saving for later reuse.
HPGL - Hewlett-Packard Graphic Language. A descriptive plotter output file format, it is considered one of
the more common interchange file formats. HPGL files are vectored.
Hyperlink - The means by which sets of information are linked to each other in any combination of;
application; database; document element (text, table or graphic).
Hypertext - An information retrieval and search methodology based upon hyperlinks between related text,
graphic and database elements that may be predefined or defined by the user.
MARCH 1999 51
IGES - Initial Graphics Exchange Specification. The ANSI vector graphics file format that is system
independent and intended for human interpretation and often used as a cross-platform exchange option.
The IGES Organization
National Institute of Standards and Technology
Building 220 Room A-353
Gaithersburg, MD 20899 USA
(301) 921-3691
In-Line Graphics - The on screen simultaneous presentation of text and graphics within a single display
window. Sometimes referred to as compound documents.
Index, Indexing - The process of building data structures for electronic databases. Indexes contain the
location of each data item and permit rapid location of data.
Information - Data that has been structured, indexed and formatted to make it more intelligible and helpful for
people that need to make use of the data.
ISO/lEO 8632:1992 - The Computer Graphics Metafile (CGM) format which identifies the three versions of
metafiles used to exchange vector data and textural characters.
ISO 8879 - The Standard Generalized Markup Language Specification.
ISO 9660 - The international standard for directory structures and file layout on CD-ROMs, a logical,
structural standard compared to the physical standards for manufacturing called the "Yellow Book." This
standard specifies, for single sessions, exactly how much information is stored on a CD-ROM to be
accessible in any CD-ROM drive running on a variety of common operating systems.
Magnetic Media - Any medium on which data is stored as variations in magnetic polarity. Usually floppy
disks, hard disks, and tape.
Mastering - A part of the process of manufacturing a CD-ROM by using a laser to embed microscopic pits
into the surface of a glass disk. The glass master is then used to make a metal stamper that is used to
replicate CD-ROM copies of the master.
Mastering Facility - A manufacturing plant where compact disc "masters" are created for the mass
production or replication of the actual compact discs.
Medium - Refers to an object used to store information; usually refers to a particular type of storage device
such as disk, tape, microfiche or paper.
Memory - In the computer industry, refers to a location where digital information is stored during processing.
Memory is stored on computer chips and may be either permanent or temporary.
Menu - On screen list of available functions, or operations, that can be performed currently.
MIPS - Millions of Instructions Per Second. A standard means of measuring a computer's performance
capabilities.
MRU - Minimum Revisable Unit. Discreet, logical groupings of information used in Pageless publications to
describe and work with electronic data, as opposed to an individual page. MRU examples included Page
Blocks within Maintenance Manuals and Figures within IPCs
Multimedia - The dissemination of information in more than one form including the use of text, audio,
graphics, animated graphics and full motion video.
Navigation - The process of browsing or traversing through a database or document by use of keyboard or
mouse functions.
Object - (1) A piece of visual data used to assist in the representation of an idea, or message. (2) A self
contained module of data and its associated processing.
OCR - Optical Character Recognition. Machine recognition of printed characters using a process that visually
scans text (handwritten. printed and typewritten) and converts it to a standard format such as ASCII. OCR
software may be used during the process of converting paper source documents for distribution via electronic
publications.
52 MARCH 1999
On-Line - Data processing method that allows users to transmit or receive data from a remote computer and
output the information on demand.
Operating Controls - The set of Microsoft Windows® and retrieval software controls that enable a
standardized graphical user interface for the execution of the functionality defined within the GAMA.
Optical Disc - A storage device on which data is recorded and retrieved by use of a light source, most often
a laser beam. Optical disks are capable of storing digital, audio and video data (e.g., CD, CD-ROM, Video
Disc).
Pageless Publications - Electronic publications that utilize discreet, logical groupings (MRUs) of information
to describe and work with electronic data, as opposed to an individual page.
Page-Based Publications - Electronic publications that employ the use of scanned raster images of the
original paper documentation.
Page Block - (1) A section of text defined by the ATA Specification 100. (2) Any logical sequence of
unbroken text for use in defining the minimum granularity of text in an electronic publication..
Presentation - The method of display to the end user of text and graphic information contained in electronic
publications.
Proximity Searching - The search for one or more terms in a document, within a specified distance from
another term (i.e. within the same paragraph. within the same sentence).
Publication - A non-specific term for documentation. Maintenance Manuals, Illustrated Parts Catalogs, ADs
and Service Information are all publication examples.
Raster Images - The representation of a graphic image as a matrix of dots that are produced by scanning or
computer generated at various resolutions measured in dots per inch.
Resolution - The degree of sharpness of a displayed or printed character or image. On screen resolution is
expressed as a matrix of dots (640 x 480 means 640 dots across each of 480 lines). For printers resolution is
expressed as the number of dots per linear inch (Dots Per Inch - DPI).
Revision Symbols - Revision symbols (e.g., |, R) indicate where a change has been made since the last
issuance of the data.
ROM - Read Only Memory. Information storage format that does not permit modification or deletion of
information when in use.
Replication - The process of making multiple copies, i.e. of a CD-ROM.
Retrieval Software - The computer application providing the documentation, text and graphics appearance,
functionality and operating controls to retrieve, display and print electronic publications as defined in the
GAMA SPECIFICATION 9.
Retrieval System - The computer system employed by the end user to retrieve, display and print Electronic
Publications.
Retrieval System Page - The page of text as defined by the storage of text in electronic publications and
reproduced through the retrieval software's print function.
Scanner - A device used to scan analog images, such as a document and convert its contents into digital
images, such as bitmap images on a computer system. Scanners create bitmap images that are based upon
a grid of pixels, and record whether each pixel is light or dark. Scanners are used in conjunction with OCR
software to capture and convert images or text to an electronic bitmap format.
Schema - A logical representation of data that is oriented toward a particular database management system
approach (such as SQL or SFQL). Relative to SFQL and SQL, a schema is defined as a collection of tables
that model related data.
SCSI - Small Computer Systems Interface. A standardized method by which storage devices such as CD-
ROM drives and hard disk drives interpret and communicate data. SCSI peripherals are capable of
connecting multiple devices. CD-ROM drives typically utilize a SCSI interface for connection to a host
system.
MARCH 1999 53
Search - Process of locating information in a database by indicating search criteria, such as words or
phrases. During the search process, the retrieval software will find all matches of the criteria indicated.
Search Results - The outcome of a cross-reference driven search through a document or database, a
presentation of information or data related to search criteria such as a key word or phrase.
Service Information - Data issued by an aircraft, engine or component manufacturer that details
maintenance procedures or informs about new procedures and services. Service Information is a generic
term for all of the different types of short. timely issues published by general aviation manufacturers (e.g.,
Service Letters, Customer Bulletins, Service Instructions, News, etc.).
SFQL - Structured Full-Text Query Language. A proposed standard for full text databases defined by the
ATA in Specification 2100. The primary focus of the proposed standard is interoperability of CD-ROMs. SFQL
is based on the SQL (Structured Query Language) standard for relational databases.
SGML - Standard Generalized Markup Language. The ISO Standard 8879 that defines application and
platform independent structuring and organization of information by tagging documents as a series of data
objects defined in Document Type Definitions (DTDs). SGML separates the informational content of a
document from the information needed to present it. either on paper or on screen.
Status Message - An icon that indicates the retrieval software is busy or engaged in processing a command.
System Response - The amount of time the retrieval software takes to display a selection list or the selected
text or graphic image.
Tagging - Refers to the process of adding special markup characters to ASCII data. These tags are used to
indicate structural elements in the data, such as headings and subheadings, document margins, references
to graphic figures, etc.
Technical Maintenance Information - The maintenance information published by the manufacturers of
aviation products that supports continued airworthiness (e.g., Maintenance Manuals, Illustrated Parts
Catalogs, Structural Repair Manuals, Component Maintenance Manuals, Wiring Manuals, etc.)
Text - In electronic publications, the ASCII characters as distinguished from graphic images.
TIFF - Tagged Image File Format. An industry-wide standard graphics file format developed by Aldus, for
storing and exchanging raster image data. TIFF is used to define the specific data structures of images to be
processed.
Title Strip - An area of the display reserved for the identification of the text or graphic image being displayed.
Vector Graphics - Images based upon lines drawn between specific coordinates as defined by the
mathematical relationship between each line's beginning point, length and direction.
Windows® - Microsoft's Graphical User Interface software that accommodates the use of multiple
applications simultaneously by separating applications into different "windows" displayed on the computer
display screen. Windows runs on PCs in a DOS environment and has functionality similar to the graphical
environment employed by Apple® / Macintosh® systems.
Word Search - A search method used to locate every occurrence of a word, combination of words (or
alphanumeric strings), phrase or number in a database or document.
54 MARCH 1999

Gama Specification 9 Elecpubs March 1999 PDF 498cace8ce

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Gama Specification 9 Elecpubs March 1999 PDF 498cace8ce

Hochgeladen von

Copyright:

Verfügbare Formate

ELECTRONIC PUBLICATIONS STANDARD

GAMA SPECIFICATION NO. 9

ELECTRONIC PUBLICATIONS STANDARD

GAMA SPECIFICATION NO. 9

Prepared and Published by:

General Aviation Manufacturers Association

All Rights Reserved. No part of this document may be reproduced

© Copyright 1994, 1999

Editor: Chairman - Electronic Publications Standard Committee

May 1994 V 1.0

• Aircraft Technical Publishers*

• AlliedSignal Commercial Avionics Systems*

• Cessna Aircraft Company*

• Federal Aviation Administration Aircraft Certification Service

• General Aviation Manufacturers Association

• Honeywell, Inc., Business and Commuter Aviation Systems*

• Pratt and Whitney Canada, Inc.

• Raytheon Aircraft Company*

• Rockwell Collins, Inc. Business and Commuter Aviation Systems*

* also participated in the Document Type Definition working group

MARCH 1999 iii

1.2 Aviation Technical Publications

1.2.1 Legacy Data

ATA 100 COMPLIANT

NON ATA COMPLIANT

1.2.3 EPS Specification Use Requirements

Air Transport Association

1.2.4 Electronic Publication Options

1.3 Specification Objectives

1.3.1 End User Needs

1.3.2 Manufacturer Needs

1.3.3 Design Goals

2. MINIMUM AND RECOMMENDED RETRIEVAL SYSTEM

2.2 CD-ROM Electronic Publications Platform

2.3 Online Electronic Publications Platform

3.2 Electronic Text File Formats

• Airframe Illustrated Parts Catalog (AIPC)

3.2.1 Minimum Requirements

3.2.2 Recommended Requirements

3.3 Electronic Graphics File Formats

• Text is legible at any normal working magnification

3.3.1 Raster Text Pages

• Class* 1: CCITT Group 4 TIFF scanned at 300 dots per inch

3.3.2 Raster Graphics

• Class* 1: CCITT Group 4 TIFF scanned at 300 dots per inch

• TIFF using Packbit compression

3.3.3 Vector Graphics

• CGM file conforming to ISO Standard lSO/lEO 8632:1992 version 3

3.4.3 Control Files - Transmittal

Field Name Description Data Examples

3.4.5 Minimum Data Elements

3.4.6 Data Organization

Recommendations for directory structuring (taking into consideration DOS limitations):

• Text and graphics should reside in separate directories

3.5 Method Of Data Exchange for Paper Source Documents

3.5.1 Minimum Data Elements

3.5.2 Control Files - Transmittal

Field Description Data Examples

4. DOCUMENTATION AND PACKAGING

4.2 User Guide

• Context-sensitivity from within the retrieval software

4.3 Minimum Requirements

4.3.1 Introductory Section

• Overview of the structure of the user guide