21.06.2014 Views

ELECTRONIC PUBLICATIONS STANDARD

ELECTRONIC PUBLICATIONS STANDARD

ELECTRONIC PUBLICATIONS STANDARD

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

GAMA SPECIFICATION NO. 9<br />

Version 2.0<br />

March 1999<br />

General Aviation<br />

Manufacturers Association


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

<strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

GAMA SPECIFICATION NO. 9<br />

Version 2.0<br />

March 1999<br />

Prepared and Published by:<br />

General Aviation Manufacturers Association<br />

1400 K Street NW, Suite 801<br />

Washington, DC 20005<br />

(202) 393-1500 Fax (202) 842-4063<br />

www.generalaviation.org<br />

© Copyright 1994, 1999<br />

General Aviation Manufacturers Association<br />

Washington. D.C.<br />

All Rights Reserved. No part of this document may be reproduced<br />

in any form without permission in writing from the publisher.<br />

MARCH 1999<br />

i


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

REVISION INFORMATION<br />

Editor:<br />

Chairman - Electronic Publications Standard Committee<br />

General Aviation Manufacturers Association<br />

1400 K Street NW, Suite 801<br />

Washington, DC 20005<br />

USA<br />

Phone: (202) 393-1500<br />

Fax: (202) 842-4063<br />

May 1994 V 1.0<br />

This revision is based upon the decisions and discussions put forth during the second GAMA<br />

SPECIFICATION 9 Task Force meeting. This revision will serve as the working draft for review at the<br />

GAMA SPECIFICATION 9 meeting dated May 25, 26 and 27 in Washington D.C.<br />

June 1994 V 1.1<br />

This revision is based upon the review completed at the GAMA SPECIFICATION 9 meeting held May<br />

25-27, 1994 in Washington D.C. This final draft will be submitted to the GAMA Technical Policy<br />

Committee at the June 23-24, 1994 meeting in Atlantic City, New Jersey, for final approval. It is<br />

anticipated that this version will be published for general distribution shortly thereafter.<br />

August 1994 V 1.2<br />

This revision is based upon the meeting of the DTD working group held July 19th and 20th 1994<br />

during which the Sections 3.4.3 and 3.5.2 Control File Schema’s as well as the Appendix 2 DTDs<br />

were finalized. This version of the specification is the first issuance for publication.<br />

October 1994 V 1.3<br />

This version is based upon the meeting of the DTD working group held September 20th and 21st<br />

1994 during which the five DTDs included in Appendix 2 were finalized. Additionally, this version<br />

reflects the amendments resulting from the EPS Subcommittee meeting held September 22nd and<br />

23rd 1994. These amendments include Data Exchange use of DTDs (3.1), support for gray scale and<br />

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).<br />

This version has been approved for general circulation by the GAMA Board of Directors.<br />

March 1999 V 2.0<br />

This version is of GAMA Specification 9 incorporates many editorial changes based upon the<br />

meetings of the DTD working group and EPS subcommittee in July and October 1998, including the<br />

removal of all Appendix information. Appendix 1, Extensions to the Electronic Publications Standard,<br />

was removed due to the lack in industry need to standardize on operating controls and on-line<br />

distribution of publication information. Appendix 2, Document Type Definitions was removed. The<br />

GAMA DTDs are available on the GAMA World Wide Web site, http://www.generalaviation.org under<br />

the “Publications” link.<br />

ii MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Foreword<br />

The GAMA Specification 9 - Electronic Publications Standard was made possible by the dedicated efforts of a<br />

broad aviation industry coalition of both GAMA and non-GAMA member manufacturers, associations and<br />

regulatory authorities. Since the first meeting in June of 1993, the EPS Subcommittee has met in San<br />

Francisco, Wichita, Washington DC, Phoenix, and Ottawa. The meetings were well attended as a result of the<br />

strong industry interest in this effort. Version 2.0 of the specification is the result of a need to maintain the<br />

specification with the changing of technology and to better meet the need of the GAMA community by<br />

changing the GAMA DTDs format and content to closely match the ATA Specification 2100 DTDs.<br />

Sincere thanks are hereby extended to the following organizations for their contributions and participation in<br />

the various meetings to draft this specification:<br />

• Aircraft Technical Publishers*<br />

• AlliedSignal Engines*<br />

• AlliedSignal Commercial Avionics Systems*<br />

• Bombardier Aerospace<br />

• Cessna Aircraft Company*<br />

• Dassault Aviation<br />

• Federal Aviation Administration Aircraft Certification Service<br />

• General Aviation Manufacturers Association<br />

• Honeywell, Inc., Business and Commuter Aviation Systems*<br />

• Pratt and Whitney Canada, Inc.<br />

• Raytheon Aircraft Company*<br />

• Rockwell Collins, Inc. Business and Commuter Aviation Systems*<br />

• Sogitec<br />

• Teledyne Continental Motors<br />

* also participated in the Document Type Definition working group<br />

MARCH 1999<br />

iii


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

TABLE OF CONTENTS<br />

1. Scope_____________________________________________________________________ 1<br />

1.1 General________________________________________________________________________ 1<br />

1.2 Aviation Technical Publications ___________________________________________________ 1<br />

1.2.1 Legacy Data _________________________________________________________________________1<br />

1.2.2 ATA Specification 100 and Specification 2100 (Digital Data Standard) __________________________2<br />

1.2.3 EPS Specification Use Requirements _____________________________________________________3<br />

1.2.4 Electronic Publication Options __________________________________________________________3<br />

1.3 Specification Objectives __________________________________________________________ 3<br />

1.3.1 End User Needs ______________________________________________________________________3<br />

1.3.2 Manufacturer Needs___________________________________________________________________4<br />

1.3.3 Design Goals ________________________________________________________________________4<br />

2. Minimum and Recommended Retrieval System ___________________________________ 7<br />

2.1 General________________________________________________________________________ 7<br />

2.2 CD-ROM Electronic Publications Platform__________________________________________ 7<br />

2.3 Online Electronic Publications Platform ____________________________________________ 7<br />

3. Data Exchange_____________________________________________________________ 9<br />

3.1 General________________________________________________________________________ 9<br />

3.2 Electronic Text File Formats ______________________________________________________ 9<br />

3.2.1 Minimum Requirements _______________________________________________________________9<br />

3.2.2 Recommended Requirements ___________________________________________________________9<br />

3.3 Electronic Graphics File Formats _________________________________________________ 10<br />

3.3.1 Raster Text Pages____________________________________________________________________10<br />

3.3.2 Raster Graphics _____________________________________________________________________10<br />

3.3.3 Vector Graphics _____________________________________________________________________11<br />

3.4 Medium and Method Of Data Exchange for Electronic Text and Graphics_______________ 12<br />

3.4.1 Telecommunication __________________________________________________________________12<br />

3.4.2 Compression _______________________________________________________________________12<br />

3.4.3 Control Files - Transmittal_____________________________________________________________12<br />

3.4.4 Media Formats ______________________________________________________________________13<br />

3.4.5 Minimum Data Elements ______________________________________________________________13<br />

3.4.6 Data Organization ___________________________________________________________________13<br />

3.5 Method Of Data Exchange for Paper Source Documents______________________________ 13<br />

3.5.1 Minimum Data Elements ______________________________________________________________13<br />

3.5.2 Control Files - Transmittal_____________________________________________________________13<br />

4. Documentation and Packaging _______________________________________________ 15<br />

4.1 General_______________________________________________________________________ 15<br />

4.2 User Guide ____________________________________________________________________ 15<br />

4.2.1 Paper _____________________________________________________________________________15<br />

4.2.2 Online ____________________________________________________________________________15<br />

4.3 Minimum Requirements_________________________________________________________ 15<br />

4.3.1 Introductory Section _________________________________________________________________15<br />

4.3.2 Table of Contents / Index______________________________________________________________15<br />

4.3.3 Minimum Configuration and Performance ________________________________________________16<br />

4.3.4 Discussion of Functionality ____________________________________________________________16<br />

iv MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

4.3.5 Installation Procedure ________________________________________________________________ 16<br />

4.3.6 Error Codes and Trouble-Shooting______________________________________________________ 16<br />

4.3.7 Terminology _______________________________________________________________________ 16<br />

4.3.8 Operation Notes and Cautions _________________________________________________________ 16<br />

4.4 CD-ROM Packaging ____________________________________________________________17<br />

4.4.1 Labeling __________________________________________________________________________ 17<br />

4.4.2 Operating Instructions _______________________________________________________________ 17<br />

5. Text and Graphics Appearance _______________________________________________ 19<br />

5.1 General _______________________________________________________________________19<br />

5.2 Electronic Text Appearance Requirements __________________________________________19<br />

5.2.1 Readability at Various Resolutions______________________________________________________ 19<br />

5.2.2 Style Support ______________________________________________________________________ 20<br />

5.2.3 Typefaces _________________________________________________________________________ 20<br />

5.2.4 Distinguishing Titles_________________________________________________________________ 20<br />

5.2.5 Tables ____________________________________________________________________________ 20<br />

5.2.6 Character Set_______________________________________________________________________ 20<br />

5.2.7 Use of Color _______________________________________________________________________ 21<br />

5.3 Graphics Appearance____________________________________________________________21<br />

5.3.1 Display of Raster Text Pages __________________________________________________________ 21<br />

5.3.2 Display of Raster Graphics____________________________________________________________ 21<br />

5.3.3 Display of Vector Graphics ___________________________________________________________ 23<br />

6. Authenticity Rules _________________________________________________________ 25<br />

6.1 General _______________________________________________________________________25<br />

6.2 Authenticity Guidelines for Page-Based Publications__________________________________25<br />

6.3 Authenticity Guidelines for Pageless Publications ____________________________________25<br />

6.4 Authenticity Guidelines for Bookless Publications ____________________________________27<br />

7. Functionality _____________________________________________________________ 29<br />

7.1 General _______________________________________________________________________29<br />

7.2 Page-Based Publication Functionality ______________________________________________29<br />

7.2.1 Browse / Traversal (Navigation) _______________________________________________________ 29<br />

7.2.2 Cross Reference Links _______________________________________________________________ 29<br />

7.2.3 Search ____________________________________________________________________________ 30<br />

7.2.4 Retrieval Software Response __________________________________________________________ 31<br />

7.2.5 Printing ___________________________________________________________________________ 31<br />

7.2.6 Revision Identification (Tracking and Control) ____________________________________________ 32<br />

7.2.7 Data Integrity ______________________________________________________________________ 32<br />

7.2.8 Data Export________________________________________________________________________ 32<br />

7.2.9 Help _____________________________________________________________________________ 32<br />

7.3 Pageless Publication Functionality _________________________________________________32<br />

7.3.1 Browse / Traversal (Navigation) _______________________________________________________ 32<br />

7.3.2 Cross Reference Links _______________________________________________________________ 34<br />

7.3.3 Search ____________________________________________________________________________ 35<br />

7.3.4 Retrieval Software Response __________________________________________________________ 36<br />

7.3.5 Printing ___________________________________________________________________________ 36<br />

7.3.6 Revision Identification (Tracking and Control) ____________________________________________ 37<br />

7.3.7 Data Integrity ______________________________________________________________________ 38<br />

7.3.8 Data Export________________________________________________________________________ 38<br />

7.3.9 Help _____________________________________________________________________________ 38<br />

MARCH 1999<br />

v


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

7.4 Bookless Publication Functionality ________________________________________________ 39<br />

8. Operating Controls_________________________________________________________ 41<br />

8.1 General_______________________________________________________________________ 41<br />

8.2 Retrieval Software Controls______________________________________________________ 41<br />

8.3 Keyboard Access and Navigation _________________________________________________ 41<br />

8.3.1 Dialog Box Controls _________________________________________________________________41<br />

8.3.2 Navigation and Keyboard Access within Dialog Boxes ______________________________________42<br />

8.3.3 Navigation within Text or Image Retrieval Screens _________________________________________43<br />

8.3.4 Control Key Shortcuts ________________________________________________________________43<br />

8.3.5 Function Key Shortcuts _______________________________________________________________44<br />

8.4 Retrieval Software Conventions __________________________________________________ 44<br />

9. Associated Standards _______________________________________________________ 45<br />

9.1 General_______________________________________________________________________ 45<br />

9.2 Controlled Vocabularies_________________________________________________________ 45<br />

9.3 Required Standards ____________________________________________________________ 45<br />

9.4 Recommended Standards________________________________________________________ 46<br />

10. GAMA DTD Information ___________________________________________________ 47<br />

11. GLOSSARY OF <strong>ELECTRONIC</strong> PUBLICATION TERMS ________________________ 49<br />

vi MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

1. SCOPE<br />

1.1 General<br />

This specification was developed by the General Aviation Manufacturers Association (GAMA) Electronic<br />

Publications Standard (EPS) Subcommittee to assist in the preparation of technical maintenance information<br />

to be published on electronic media, and in the implementation of systems to retrieve, display and print<br />

electronic publications.<br />

The GAMA SPECIFICATION 9 Subcommittee began by evaluating the existing relevant standards and<br />

determined that there was not a general aviation industry standard appropriate for the problem of converting<br />

millions of pages of legacy (both Air Transport Association (ATA) and non-ATA conforming publications from<br />

source documents existing either electronically or in paper). This specification is established as a guideline<br />

for the transition into publishing and exchanging manufacturers' data electronically. Specifically, this standard<br />

is intended for use when compliance with ATA Specification 2100 is inappropriate or impractical.<br />

Additionally, this specification describes the minimum and recommended functional requirements that must<br />

be met by computerized retrieval systems used to access aviation technical maintenance information.<br />

The intent of this specification is to standardize the minimum computer delivery systems, distribution media,<br />

system functionality and operating controls, text and graphics appearance, system documentation,<br />

terminology and data exchange between manufacturers. Standardization is expected to enhance safety<br />

through the elimination of problems caused by inconsistent results derived from disparate systems, and by<br />

the minimization of training and equipment necessary to utilize electronic publications originating from the<br />

multitude of general aviation manufacturers. Standardizing “look and feel" and “system usability" will expedite<br />

the transition to the use of electronic publications.<br />

This specification is not intended to affect the technical content of electronic publications. Technical content is<br />

the responsibility of the producer of the publication in cooperation with the civil aviation authorities.<br />

Questions on interpretation and proposed changes to this specification should be submitted to the General<br />

Aviation Manufacturers Association, Electronic Publications Standard Subcommittee, Suite 801 1400 K<br />

Street, NW, Washington, D.C. 20005.<br />

1.2 Aviation Technical Publications<br />

1.2.1 Legacy Data<br />

The millions of pages of technical publications (maintenance manuals, structural repair manuals, wiring<br />

manuals, illustrated parts catalogs, service letters and bulletins. etc.) currently being used every day in<br />

general aviation constitute a body of information authored over a period of more than 50 years. This<br />

information is collectively referred to as “legacy data".<br />

The majority of these publications are not compliant with the ATA Specification 100, and an even greater<br />

proportion was not created using electronic publishing systems. For these publications, the source<br />

documents exist only in paper form.<br />

A guiding concern of this standard is to identify a pathway whereby this legacy data can cost-effectively and<br />

consistently be converted into electronic form for retrieval anywhere in the world using standard hardware<br />

and software systems.<br />

MARCH 1999 1


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

ATA<br />

2100<br />

COMPLIANT<br />

SGML SOURCE<br />

ATA 100 COMPLIANT<br />

PAPER SOURCE<br />

NON-ATA COMPLIANT<br />

<strong>ELECTRONIC</strong> SOURCE<br />

NON ATA COMPLIANT<br />

PAPER SOURCE<br />

Figure 1.1<br />

General Aviation Legacy Data<br />

1.2.2 ATA Specification 100 and Specification 2100 (Digital Data Standard)<br />

While acknowledging that the tremendous efforts of the ATA working groups have produced a model<br />

specification for in the creation of new publications destined for distribution on electronic media, the majority<br />

of general aviation legacy data (as illustrated in figure 1.1) does not conform to these stringent standards.<br />

The ATA Specification 2100 Digital Data Standard was developed by the airlines to promote data portability<br />

between manufacturers and the airline's in-house publishing systems, since historically a substantial portion<br />

of the information received had to be rewritten to conform to specific operating requirements. Extensive rules<br />

were created to accommodate task-oriented maintenance instructions and provisioning information. General<br />

aviation technical publications are not typically organized in such a manner. Conformance to ATA<br />

Specification 2100, and accommodation to that level of information content, structure and tagging, would<br />

require that almost all of the currently existing general aviation technical documentation be rewritten, a<br />

solution as cost-prohibitive as it is unfeasible.<br />

The challenge is the conversion of general aviation legacy data to electronic media while maintaining<br />

compatibility with information that is authored in conformance with the ATA Specification 2100. As a costeffective<br />

solution, the GAMA SPECIFICATION 9 has adopted the most appropriate subset of the ATA<br />

Specification 2100 requirements applicable to general aviation legacy data. As a result, information authored<br />

in conformance with the ATA Specification 2100 is compliant with the GAMA SPECIFICATION 9. The less<br />

stringent requirements of the GAMA SPECIFICATION 9 will allow the vast majority of the existing general<br />

aviation publications to be cost-effectively converted from paper to electronic media using currently available<br />

technology in one of the electronic publication options identified in this specification.<br />

2 MARCH 1999


1.2.3 EPS Specification Use Requirements<br />

GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

To effectively use this specification, you must obtain ATA Specifications 100 and 2100 from:<br />

Air Transport Association<br />

1301 Pennsylvania Ave., NW<br />

Suite 1100<br />

Washington, DC 20004-1707<br />

(202) 626-4000<br />

http://www.air-transport.org/<br />

ATA Specification 100 provides the authoring rules and content guidelines that were used to develop ATA<br />

Specification 2100. ATA Specification 2100 contains the information needed to interpret and apply GAMA<br />

Specification 9 and its associated DTDs.<br />

1.2.4 Electronic Publication Options<br />

This specification will present three approaches to the production and delivery of electronic technical<br />

publications.<br />

A. Page-Based Publications<br />

Page-based electronic publications are the functional equivalent of “fiche on CD".<br />

Navigation within a page-based publication, at a minimum, consists of an electronic table of<br />

contents, the ability to turn pages forward and backward, and possibly to hyperlink to text and<br />

images.<br />

B. Pageless Publications<br />

Pageless electronic publications present and distribute data as discreet elements (i.e.,<br />

maintenance manual (MM) page blocks or illustrated parts catalog (lPC) sections) rather than<br />

individual pages. The presentation to the end user is of scrolling text formatted similarly, but<br />

not exactly, like the paper source document. Text and graphics may be displayed either<br />

separately or in-line. Navigation functionality includes an electronic table of contents,<br />

hyperlinking to text and images, full-text searches, and may also include bookmarks and<br />

backtracking.<br />

C. Bookless Publications<br />

A bookless electronic publication maintains information in a database, with the information<br />

retrieved through an inquiry of the system. This approach is consistent with the ATA<br />

Specification 2100, and is viewed as a future direction for general aviation technical<br />

publications once electronic publishing matures, and when the needs of the end user can be<br />

designed into the publications during the initial authoring of publications.<br />

1.3 Specification Objectives<br />

1.3.1 End User Needs<br />

This specification endeavors to satisfy the needs of that portion of the end-user community inexperienced<br />

with computers and have had little or no exposure to electronic document retrieval systems.<br />

A. Common Presentation Style<br />

End users will benefit from a common presentation style, or look and feel, to provide them<br />

with comfortable and familiar reference points when accessing electronic data from different<br />

manufacturers.<br />

B. Similar Platform Base<br />

To avoid the burden of having to purchase, understand, and maintain different types of<br />

computer systems to benefit from the use of electronic documentation, the end user will<br />

MARCH 1999 3


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

greatly benefit from the identification of a common platform base for general aviation<br />

electronic retrieval systems<br />

C. Similar Software Base<br />

The identification of a common software base for general aviation electronic retrieval systems<br />

will relieve the end user of the need to purchase, learn, and maintain different types of<br />

operating systems and user interfaces.<br />

D. Common Features of Functionality<br />

A standard suite of minimum functionality common to general aviation electronic retrieval<br />

systems will reduce the cost to the end user for training and support, while eliminating<br />

confusion and frustration.<br />

E. Authenticity<br />

The end user will need confidence in the authenticity and completeness of the electronic<br />

information. There will be a responsibility to educate the end user concerning the fact that the<br />

screen display of information and the original legacy data of that same information may<br />

appear different, yet the content between the two presentations of the data is identical.<br />

1.3.2 Manufacturer Needs<br />

This specification endeavors to satisfy the needs of the manufacturers by presenting cost-effective solutions<br />

incorporating current technology, appropriate for the conversion of legacy data and the authoring of new<br />

publications.<br />

A. Satisfy Users Needs<br />

Manufacturers require a set of standards to which they can build their publications in order to<br />

universally satisfy the mechanics, maintenance professionals, and support people who will have<br />

access to this information.<br />

B. A Direction for Future Development<br />

This specification will provide manufacturers transitioning into electronic publishing systems with a<br />

set of requirements to furnish to vendors that satisfies the issue of legacy data conversion, current<br />

on-going publication, and the creation of new publications. Additionally, this specification will<br />

endeavor to provide direction concerning emerging technologies and their appropriateness for<br />

general aviation publications.<br />

C. Compatibility of Data<br />

A set of Data Exchange Standards is required to ensure data compatibility for interchange between<br />

manufacturers (i.e. for the integration of various manufacturers' data into a single publication set) and<br />

between publication authors and their electronic publication integrators.<br />

This data exchange standard must provide compatibility guidelines for the various levels of data<br />

enrichment (tagging) dictated by the publication method employed by the manufacturer (page-based,<br />

page-less or book-less). Additionally, this standard must apply to both initial data exchange, and<br />

revisions to that data.<br />

1.3.3 Design Goals<br />

This specification endeavors to identify solutions that are feasible for adoption and flexible for enhancement.<br />

A. Feasible Methods for Paper to Electronic Conversion<br />

The standard must focus on the use of cost-effective technology and techniques to make the<br />

conversion of millions of pages of legacy data feasible. For example, to minimize the<br />

complexity of migrating to new electronic publication authoring systems, SGML is employed<br />

as a data exchange standard, not for delivery of data to the end user. This and other such<br />

4 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

minimum subsets of the ATA Specification 2100 requirements provide reasonable electronic<br />

publication guidelines appropriate for general aviation.<br />

B. Flexibility to Innovate<br />

This specification must allow manufacturers and electronic system designers the flexibility to<br />

provide new system functionality and additional ways of enriching the information to satisfy<br />

the unique needs of the aviation community.<br />

MARCH 1999 5


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

2. MINIMUM AND RECOMMENDED RETRIEVAL SYSTEM<br />

2.1 General<br />

This section defines the system requirements for the end user to retrieve, display and print electronic<br />

publications and is referred to throughout this specification as the "retrieval system.” At a minimum, the<br />

retrieval system must support IBM®-compatible personal computers operating under Microsoft Windows®<br />

version 3.11 or greater. This does not preclude other additional platforms from being utilized (i.e. Apple®/<br />

Macintosh® or UNIX workstations.)<br />

Additionally the minimum and recommended retrieval systems must be capable of supporting all of the<br />

functionality of the “retrieval software”. “Retrieval software" is defined to include the documentation, text and<br />

graphics appearance, functionality and operating controls defined in Sections 4, 5, 7, and 8 of this<br />

specification.<br />

This section also furnishes the end user with a recommendation of the most appropriate and cost effective<br />

retrieval system components to acquire. Additionally, this recommendation provides guidance for developers<br />

regarding the related performance expectations of end users. Due to the rapid development of personal<br />

computers and the hardware-limited expansion of functionality that comes with the evolution of software, this<br />

recommendation will be updated periodically.<br />

As new media and methods of delivery of electronic publications are introduced, additional minimum and<br />

recommended retrieval system configurations will be identified.<br />

2.2 CD-ROM Electronic Publications Platform<br />

The platform for a CD-ROM technical data retreival system should be a standard commercially available<br />

computer system capable of running the most recent versions of the Microsoft Windows® operating system.<br />

At the time of publishing this specification, an example of an acceptable configuration would be:<br />

• Pentium®-based (or later) CPU<br />

• 32 MB RAM<br />

• 3 ½” floppy disk drive<br />

• 800 MB hard disk drive<br />

• CD-ROM drive<br />

• Microsoft Windows95® or greater<br />

• 17” or larger color monitor<br />

• Microsoft Windows® accelerated graphic adapter 1024x768 or higher resolution<br />

• 300 DPI or higher resolution Microsoft Windows®-compatible laser printer.*<br />

Note:<br />

A backup may provide additional beneficial functionality. This may also be desired (or required) for some<br />

retrieval systems.<br />

*Plotters may not be acceptable to print raster images<br />

2.3 Online Electronic Publications Platform<br />

For online retrieval, users should have a system comparable to that described in 2.1, above, with the addition<br />

of a high-speed modem, ISDN or comparable technology, or direct Internet connection. Due to the rich<br />

graphics content in much technical documentation, a low-speed online connection will not deliver adequate<br />

document retrieval performance.<br />

MARCH 1999 7


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

3. DATA EXCHANGE<br />

3.1 General<br />

This section describes the minimum requirements for electronic data exchange for both text and graphics, the<br />

medium of that electronic exchange, and the rules for the exchange of paper source documents.<br />

These guidelines are intended for use by the authors of electronic data and information integrators to facilitate<br />

data exchange. They in no way imply requirements or methods for how that information should be distributed<br />

to the end user.<br />

3.2 Electronic Text File Formats<br />

This subsection specifies the data exchange requirements for electronic (ASCII) text.<br />

Electronic data conforming to the ATA Specification 2100 is in compliance with this subsection of this<br />

specification.<br />

The GAMA SPECIFICATION 9 Subcommittee has reviewed the ATA Specification 2100 DTDs and<br />

determined that the following DTDs will be developed to accommodate the types of publications found in<br />

general aviation legacy data:<br />

• Airframe Illustrated Parts Catalog (AIPC)<br />

• Airframe Maintenance Manual (AMM)<br />

• Component Maintenance Manual (CMM)<br />

• Engine Illustrated Parts Catalog (ElPC)<br />

• Engine Maintenance Manual (EMM)<br />

• Service Bulletins (SB)<br />

• System Installation/Maintenance Manual (SIMM)<br />

• Wiring Manual (WM).<br />

Each of the GAMA SPECIFICATION 9 DTDs will accommodate all three types of publications (bookless,<br />

pageless and page-based) identified in this specification. The DTDs developed for data exchange under this<br />

section will be available on the GAMA web site, http://www.generalaviation.org.<br />

3.2.1 Minimum Requirements<br />

Electronic text data will consist of SGML-tagged ASCII Text conforming to a DTD listed in this specification.<br />

These DTDs are available from GAMA.<br />

3.2.2 Recommended Requirements<br />

To provide for the required functionality identified in Section 7 of this specification, data files should contain:<br />

• Tagging or a method to identify text that requires distinctive screen display and print attributes:<br />

−<br />

−<br />

−<br />

−<br />

−<br />

Bold<br />

Italic<br />

Underline<br />

Highlight<br />

Reverse Video<br />

MARCH 1999 9


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

−<br />

Special Characters<br />

• Tagging to support the cross-referencing of text and graphics<br />

• Consistent table creation methods (avoiding combinations of spaces, tabs, indents, computer<br />

controlled, etc.)<br />

3.3 Electronic Graphics File Formats<br />

This subsection specifies the requirements that apply to all electronic graphic data.<br />

Electronic data conforming to the ATA Specification 2100 is in compliance with this subsection of this<br />

specification.<br />

Note: For raster graphics, determination of appropriate resolutions should be made from a VGA screen, as<br />

that is the lowest common denominator. The following are guidelines in determining appropriate resolutions:<br />

• Text is legible at any normal working magnification<br />

• Lines are not jagged at any normal working magnification<br />

• Lines and/or text do not overlap (appear muddy).<br />

3.3.1 Raster Text Pages<br />

A. Minimum Requirements<br />

Electronic raster text pages are required to be in a digital format that is Class* 1 CCITT<br />

Group 4 TIFF scanned at 300 dots per inch<br />

B. Recommended Requirements<br />

Electronic raster text pages are recommended to be scanned at the Class* level appropriate<br />

to adhere to the guidelines as identified in Section 3.3 of this Specification:<br />

• Class* 1: CCITT Group 4 TIFF scanned at 300 dots per inch<br />

• Class* 2: CCITT Group 4 TIFF scanned at 400 dots per inch<br />

• Class* 3: CCITT Group 4 TIFF scanned at 600 dots per inch<br />

• Class* 4: CCITT Group 4 TIFF scanned at 1200 dots per inch.<br />

*Classes are for reference to ATA Specification 2100 graphic section but are not indicative of<br />

compliance with the class attributes defined there.<br />

3.3.2 Raster Graphics<br />

A. Minimum Requirements<br />

Electronic raster graphics files are required to be in a digital format that is Class * 1 CCITT<br />

Group 4 TIFF scanned at 300 dots per inch<br />

B. Recommended Requirements<br />

Complex graphics (multiple individual illustrations on a single 8.5 x 11 page) should be<br />

separated into individual illustrations (one illustration per file) when:<br />

• Upon initial display on a VGA screen, the individual illustrations are not<br />

distinguishable<br />

• Separation of the illustrations would enhance the usefulness of the information.<br />

10 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Note: The separated illustrations should be individually captioned for use in Tables of<br />

Content.<br />

Recommended raster file format exchange options are as follows:<br />

Monochrome electronic raster graphics files are recommended to be scanned at the Class*<br />

level appropriate to adhere to the guidelines as identified in Section 3.3 of this Specification:<br />

• Class* 1: CCITT Group 4 TIFF scanned at 300 dots per inch<br />

• Class* 2: CCITT Group 4 TIFF scanned at 400 dots per inch<br />

• Class* 3: CCITT Group 4 TIFF scanned at 600 dots per inch<br />

• Class* 4: CCITT Group 4 TIFF scanned at 1200 dots per inch.<br />

*Classes are for reference to the ATA Specification 2100 graphic specification section but are<br />

not indicative of compliance with the class attributes defined there.<br />

C. Gray scale and color graphic support<br />

General aviation legacy data may contains photographs and color illustrations which are not<br />

accommodated by the ATA Specification 2100. The following raster file formats are<br />

recommended for use in the exchange of gray scale and color graphic images:<br />

1. Gray-scale<br />

• TIFF using Packbit compression<br />

• PCX.<br />

2. Color<br />

• PCX-16 colors<br />

• PCX -256 colors<br />

• PCX - 16.7 million colors<br />

• Baseline JPEG.<br />

3.3.3 Vector Graphics<br />

A. Minimum Requirements<br />

Electronic vector graphics files are required to be in a digital format that is electronically<br />

convertible to CClTT Group 4 TIFF.<br />

Examples include:<br />

• HPGL<br />

• CGM<br />

• IGES.<br />

B. Recommended Requirements<br />

The following electronic vector graphics files are recommended in order to conform to ATA<br />

Specification 2100 graphic section:<br />

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

• DWG or DXF.<br />

MARCH 1999 11


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

3.4 Medium and Method Of Data Exchange for Electronic Text and Graphics<br />

This subsection describes the requirements concerning the medium and method of data exchange for<br />

electronic text and graphics.<br />

3.4.1 Telecommunication<br />

Telecommunication specifics are at the discretion of the exchanging parties.<br />

3.4.2 Compression<br />

Data compression algorithms are at the discretion of the exchanging parties.<br />

3.4.3 Control Files - Transmittal<br />

Control files will be used to identify and communicate pertinent information for each discreet element or<br />

Minimum Revisable Unit*(MRU) during data exchange. Information provided by the control files will be used<br />

to track revisions as well as furnish important data for indexing in the retrieval software.<br />

The minimum elements that should be communicated (per minimum revisable unit as defined in Section 7.3.6<br />

of this specification) in the control files are as follows:<br />

Table 3-1<br />

Control File for Pageless Publications<br />

Field Name Description Data Examples<br />

File name Electronic filename with path (as it appears on data<br />

exchange media, including path names.)<br />

\G4\AMM\32\01010001.TXT<br />

\G4\AIPC\32\12345.TIF;<br />

File format Format of the file. ASCII text; SGML; CGM; HPGL;<br />

TIFF - CCITT G4<br />

Document<br />

type<br />

Type of publication.<br />

AIPC; AMM; CMM; EIPC; EMM;<br />

SB; WM;<br />

MRU title Chapter, section, subject, pageblock, title, or figure<br />

caption).<br />

“Landing Gear - Fault Isolation”;<br />

“Main Landing Gear Door<br />

MRU ID<br />

Unique MRU Identifier: For MM or IPC text, the<br />

chapter sequence number; for service information<br />

text, the issue number; and for graphics, the unique<br />

graphic reference in the text.<br />

Assembly”<br />

“32-03-03-001”<br />

“32-05-01 Figure 1”<br />

“SB-32-115R2”<br />

OI date Original issue date (using the format: YYYYMMDD). “19921005” = Oct. 5, 1992<br />

Rev date Revision date (if applicable using the format 19940510 = May 10, 1994<br />

YYYYMMDD).<br />

ATA chapter ATA/GAMA chapter-section applicability (using the 32-01; 24-05<br />

format CC-SS).<br />

Reason Reason for revision (if applicable). Revised, New, Deleted<br />

Comments Comments pertaining to the file. “To replace previous corrupt file”,<br />

“Scanned at 600 DPI”<br />

* Refer to Section 7 of this specification for a listing of minimum revisable units by publication.<br />

The control file format will be comma-delimited ASCII text with field names, maximum lengths, and other<br />

recommended elements as defined in Section 7 of this specification when available.<br />

12 MARCH 1999


3.4.4 Media Formats<br />

GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Disk and tape formats used in data exchange are at the discretion of the exchanging parties.<br />

3.4.5 Minimum Data Elements<br />

Individual data exchange elements will be consistent with the minimum revisable units as identified in Section<br />

7 of this specification.<br />

3.4.6 Data Organization<br />

As indicated by ATA Specification 2100, documentation (electronic file or paper) must accompany the data<br />

describing:<br />

• Media specifications i.e., block, sector sizes, operating system (if applicable)<br />

• Directory structure<br />

• Files in each directory.<br />

Recommendations for directory structuring (taking into consideration DOS limitations):<br />

• Text and graphics should reside in separate directories<br />

• Text MRUs for MMs and IPCs should be grouped by chapter<br />

• Graphics for MMs and lPCs should be grouped by chapter<br />

• Service information text should be grouped by type of publication<br />

• Service information images should be grouped by type of publication.<br />

3.5 Method Of Data Exchange for Paper Source Documents<br />

This subsection describes the requirements concerning the method of data exchange for paper source<br />

documents. At a minimum, paper source documents will consist of clean, legible originals. Whenever<br />

possible, first generation publications are recommended.<br />

3.5.1 Minimum Data Elements<br />

Individual data exchange elements will be consistent with the minimum revisable units as identified in Section<br />

7 of this specification.<br />

3.5.2 Control Files - Transmittal<br />

Control files will be used to identify and capture pertinent information for each discreet element (minimum<br />

revisable unit) during data exchange. Information provided by the control files will be used to track revisions<br />

as well as furnish important data for indexing in the retrieval software. For transmission of paper source<br />

documents, the control file may also be furnished in paper.<br />

The minimum elements that should be communicated (per minimum revisable unit) in the control files are as<br />

listed in Table 3-2.<br />

MARCH 1999 13


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Table 3-2<br />

Control File for Page Based Publications<br />

Field<br />

Description<br />

Data Examples<br />

Name<br />

File name Electronic filename with path (as it appears on<br />

data exchange media, including path names.)<br />

\G4\AMM\32\01010001.TXT<br />

\G4\AIPC\32\12345.TIF;<br />

File format Format of the file. ASCII text; SGML; CGM; HPGL;<br />

TIFF - CCITT G4<br />

Document<br />

type<br />

Type of publication.<br />

AIPC; AMM; CMM; EIPC; EMM; SB;<br />

WM;<br />

MRU title Chapter, section, subject, pageblock, title, or<br />

figure caption).<br />

“Landing Gear - Fault Isolation”;<br />

“Main Landing Gear Door Assembly”<br />

MRU ID Unique MRU Identifier: For MM or IPC text,<br />

the chapter sequence number; for service<br />

information text, the issue number; and for<br />

“32-03-03-001”<br />

“32-05-01 Figure 1”<br />

“SB-32-115R2”<br />

graphics, the unique graphic reference in the<br />

text.<br />

OI date Original issue date (using the format:<br />

“19921005” = Oct. 5, 1992<br />

YYYYMMDD).<br />

Rev date Revision date (if applicable using the format 19940510 = May 10, 1994<br />

YYYYMMDD).<br />

ATA ATA/GAMA chapter-section applicability (using 32-01; 24-05<br />

chapter the format CC-SS).<br />

Reason Reason for revision (if applicable). Revised, New, Deleted<br />

Comments Comments pertaining to the file. “To replace previous corrupt file”,<br />

“Scanned at 600 DPI”<br />

The control file format will be comma-delimited ASCII text with field names, maximum lengths and other<br />

recommended elements as defined in Section 7 of this specification when available.<br />

14 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

4. DOCUMENTATION AND PACKAGING<br />

4.1 General<br />

This section describes the requirements for end user documentation and distribution packaging.<br />

4.2 User Guide<br />

End user documentation is required for the retrieval software and will be provided in two forms, electronic (online<br />

help) and paper.<br />

4.2.1 Paper<br />

The paper user guide will contain, at a minimum, those requirements defined in section 4.3 of this<br />

specification.<br />

4.2.2 Online<br />

The online user guide (the help system) will contain, at a minimum, those requirements defined in section 4.3<br />

of this specification.<br />

Additionally, online help will follow the Microsoft Windows® help system conventions, including:<br />

• Context-sensitivity from within the retrieval software<br />

• Search within the help system<br />

• Use of bookmarks<br />

• Use of annotations<br />

• Ability to copy information to the Windows® Clipboard<br />

• Ability to print topics.<br />

4.3 Minimum Requirements<br />

This subsection delineates the minimum requirements for the contents of both the paper and online<br />

documentation.<br />

4.3.1 Introductory Section<br />

The end user documentation will provide an introductory section that will include:<br />

• Overview of the structure of the user guide<br />

• Discussion on how to use the manual<br />

• Where to get technical spport.<br />

4.3.2 Table of Contents / Index<br />

The end user documentation must employ the use of both a table of contents and an index.<br />

MARCH 1999 15


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

4.3.3 Minimum Configuration and Performance<br />

A section of the end user documentation will contain a minimum configuration list and will discuss the<br />

performance expectations of that minimum configuration. Additionally, a recommended configuration list may<br />

be included in this section.<br />

4.3.4 Discussion of Functionality<br />

A complete description of product functionality must be included in the end user documentation.<br />

4.3.5 Installation Procedure<br />

A section of the end user documentation must contain step-by-step installation procedures including:<br />

• First-time installation<br />

• Data revision installation<br />

• Retrieval software update installation.<br />

4.3.6 Error Codes and Trouble-Shooting<br />

A section of the end user documentation shall provide a list of all the retrieval software error codes (as they<br />

appear in the program) and the steps the end user should perform to eliminate the problem.<br />

4.3.7 Terminology<br />

A section devoted to terminology used in the retrieval software shall be incorporated into the end user<br />

documentation.<br />

4.3.8 Operation Notes and Cautions<br />

To appropriately set an end user's expectation level, a section of the end user documentation will contain<br />

operation notes and cautions that will include:<br />

• Retrieval software limitations<br />

• Cautions concerning nomenclature in word searches<br />

• Word search limitations or absence in page-based publications (see definition in Section 1.2.3 of this<br />

specification.)<br />

16 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

4.4 CD-ROM Packaging<br />

This subsection covers CD-ROM packaging requirements and operating instructions.<br />

4.4.1 Labeling<br />

The following information is required on a printed CD-ROM label:<br />

• Data supplier's identifier (manufacturer)<br />

• Model (if appropriate)<br />

• Disc set name<br />

• Disc revision number<br />

• CD issue date<br />

• Physical disc number (1 of 3, 2 of 3, etc.)<br />

• Disc contents.<br />

4.4.2 Operating Instructions<br />

Condensed operating instructions, independent of the user guide, should be provided. This document<br />

(commonly referred to as a "quick start guide") should encompass:<br />

• Retrieval software requirements<br />

• First-time installation procedures<br />

• Application start-up instructions<br />

MARCH 1999 17


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

5. TEXT AND GRAPHICS APPEARANCE<br />

5.1 General<br />

This section describes the appearance requirements for the display of electronic text and graphics.<br />

To accommodate the viewing limitations of a VGA screen, yet maintain publication authenticity, the following<br />

global display rules apply to the electronic display of information:<br />

• Information content between the paper and electronic information must be identical, except:<br />

−<br />

−<br />

−<br />

−<br />

Corrected errors in spelling (see Section 6.3 of this Specification)<br />

Corrected errors in numbering (see Section 6.3 of this Specification)<br />

Tables of contents and indices which are replaced by retrieval system functionality<br />

Relationships and subordination implied by indentation must be preserved<br />

• Indentation size may differ between paper and electronic text to maximize the usage of the electronic<br />

display area<br />

• Typefaces may differ between paper and electronic text to maximize the readability of the electronic<br />

text (including, but not limited to: body text, titles, and captions.)<br />

• Typeface sizes may differ between paper and electronic text to maximize the readability of the<br />

electronic text (including, but not limited to: body text, titles, captions.)<br />

5.2 Electronic Text Appearance Requirements<br />

This subsection contains the requirements for the display appearance of electronic text.<br />

5.2.1 Readability at Various Resolutions<br />

These tables describe the recommended maximum display resolution for each of several popular monitor<br />

sizes and the recommended minimum Microsoft Windows® font size for each screen resolution.<br />

Table 5-1<br />

Recommended Maximum Resolution for Various Monitor Sizes<br />

Monitor Size Maximum Display Resolution<br />

14” 800 x 600<br />

15” 800 x 600<br />

17” 1024 x 768<br />

19 or 20” 1600 x 1200<br />

Table 5-2<br />

Font Size rules for Display Under MS Windows<br />

Resolution Minimum Font Size<br />

640 x 480 8<br />

800 x 600 8<br />

1024 x 768 7<br />

1280 x 1024 7<br />

MARCH 1999 19


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

5.2.2 Style Support<br />

The display electronic text should support any combination of the following attributes:<br />

• Bold<br />

• Italic<br />

• Underline<br />

• Highlight<br />

• Reverse video<br />

• Special characters<br />

• Color (see Section 5.2.7)<br />

5.2.3 Typefaces<br />

Typeface support within the retrieval software should allow adjusting font size for appropriate screen display<br />

and printed output.<br />

Typeface support must be in accordance with GAMA Specifications 1 and 2. Refer to the display rules in<br />

Section 5.1 of this specification for additional considerations.<br />

5.2.4 Distinguishing Titles<br />

Title display must be in accordance with GAMA Specifications 1 and 2. Refer to the display rules in Section<br />

5.1 of this specification for additional considerations.<br />

5.2.5 Tables<br />

It is mandatory that table meaning be preserved in both display and print. Ruling lines in complex tables can<br />

convey meaning, and therefore, the following guidelines should be used to select the appropriate display<br />

method. Refer to the display rules in Section 5.1 of this specification for additional considerations.<br />

Tables should be displayed as text when:<br />

• The retrieval software is capable of generating ruling lines, or<br />

• The lack of ruling lines does not affect the table's meaning.<br />

Tables should be displayed as graphics when the lack of ruling lines does affect the table's meaning.<br />

5.2.6 Character Set<br />

To augment the limited number of special characters found in the extended ASCII range of common Microsoft<br />

Windows® fonts (e.g., º, ± ¼, ½, ¾, £), any ISO standard entity set may be used. These entity sets should be<br />

declared in the DTD. If additional characters are needed beyond those available in ISO entity sets, the user<br />

should create a custom entity set with the additional characters required, declare the entity set in the DTD<br />

and transmit the entity set, with a description of the characters needed, with the DTD.<br />

20 MARCH 1999


5.2.7 Use of Color<br />

GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Use of color within the retrieval software is allowed. However, in instances where color is the only means to<br />

convey pertinent information (i.e. the existence of a hyperlink) an alternative identification method (i.e. cursor<br />

change) must be provided for users of monochrome displays and users who are colorblind.<br />

The use of color is acceptable in the following instances:<br />

• Text and Image hyperlink references<br />

• Word search results<br />

• Notes, Warnings and Cautions<br />

• Title strips<br />

• Table headers<br />

• Temporary revisions.<br />

A. Recommended Use of Color<br />

If color in text is used to distinguish warnings and cautions then the following colors should be used:<br />

• For warnings use red<br />

• For cautions use yellow.<br />

If users are given the opportunity to change the colors displayed, warnings and cautions should adhere to the<br />

colors above and not be changeable.<br />

5.3 Graphics Appearance<br />

This subsection contains the requirements for the electronic display appearance of graphic images.<br />

5.3.1 Display of Raster Text Pages<br />

To facilitate the cost-effective conversion of legacy data to electronic publications, the raster display of text<br />

pages is allowed. Additionally, the raster display of tables may be necessary, as outlined in Section 5.2.5 of<br />

this specification.<br />

5.3.2 Display of Raster Graphics<br />

The following minimum scanning and raster graphics display requirements may be augmented by:<br />

• ATA Graphics Committee developing efforts<br />

• IGE Functional Requirements.<br />

A. Minimum Scanning Requirements<br />

The minimum scanning requirements for source graphics and text pages to be presented as raster<br />

images is Class 1*: 300 dots per inch resolution.<br />

B. Recommended Scanning Requirements<br />

Recommendations for scanning source graphics and text pages to be presented as raster images are<br />

as follows:**<br />

• Class 2*: 400 dots per inch resolution<br />

• Class 3*: 600 dots per inch resolution<br />

MARCH 1999 21


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

• Class 4*: 1200 dots per inch resolution<br />

• Image cropping for minimal white space<br />

• Free of graphic "noise" (punch holes, etc.)<br />

The following are guidelines in determining appropriate resolutions:<br />

• Text is legible at normal working magnification<br />

• Lines are not jagged at normal working magnification<br />

• Lines and/or text do not overlap (appear muddy).<br />

*Classes are for reference to the ATA Specification 2100 graphic section but are not indicative of<br />

compliance with the class attributes defined there.<br />

** For source graphics, determination of appropriate scanning resolutions should be done from a<br />

VGA screen, as that is the lowest common denominator.<br />

C. Screen Display Minimum Requirements<br />

The minimum retrieval software requirements for screen display support are as follows:<br />

• Support for Classes* 1-4 monochrome raster graphics:<br />

−<br />

−<br />

−<br />

−<br />

Class 1: scanned at 300 dots per inch resolution<br />

Class 2: scanned at 400 dots per inch resolution<br />

Class 3: scanned at 600 dots per inch resolution<br />

Class 4: scanned at 1200 dots per inch resolution<br />

• Support for image sizes up to and including 11 inches by 25 inches.<br />

* Classes are for reference to the ATA Specification 2100 graphic section but are not indicative of<br />

compliance with the class attributes defined there.<br />

D. Gray Scale and Color Graphic Screen Display Recommendations<br />

To accommodate the screen display of gray-scale and color graphic images found in general aviation<br />

legacy data that are not supported by the ATA Specification 2100, the following raster file formats are<br />

recommended to be supported by the retrieval software:<br />

1. Gray-scale<br />

• TIFF using Packbit compression<br />

• PCX.<br />

2. Color<br />

• PCX - 16 colors<br />

• PCX - 256 colors<br />

• PCX - 16.7 million colors<br />

• Baseline JPEG.<br />

22 MARCH 1999


5.3.3 Display of Vector Graphics<br />

GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

A. Minimum Line Weights<br />

For vector graphics, determination of appropriate line weights should be done from a VGA screen, as that is<br />

the lowest common denominator. The following are guidelines in determining minimum line weights:<br />

• Text is legible at normal working magnification<br />

• Lines are not jagged at normal working magnification<br />

• Lines and/or text do not overlap (appear muddy)<br />

• All lines must be visible at the normal working magnification<br />

This section is reserved for the future discussion of other Vector Graphics Display requirements.<br />

MARCH 1999 23


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

6. AUTHENTICITY RULES<br />

6.1 General<br />

This section presents a set of authenticity rules for each of the three approaches to the production and<br />

delivery of electronic technical publications defined in Section 1.2.4 of this specification. These rules are put<br />

forth to identify and standardize those changes and compromises permitted by the transition to electronic<br />

publications. These rules are designed to provide the end user with consistent levels of expectation across<br />

systems, and thus instill a sense of confidence in the integrity of the information.<br />

6.2 Authenticity Guidelines for Page-Based Publications<br />

This subsection identifies the authenticity rules for page-based publications defined in Section 1.2.4 A of this<br />

specification.<br />

A. Content and Display<br />

The entire publication, from beginning to end, will be available as raster images for viewing<br />

and printing. An additional electronic Table of Contents may be provided for aid in<br />

navigation.<br />

B. Front Matter<br />

As from the original paper source document.<br />

C. Headers and Footers<br />

As from the original source document. Additionally, Title Strips may be employed to carry<br />

this, and other, information.<br />

D. Page Numbers<br />

As from the original source document.<br />

E. Text and Graphics Display<br />

As from the original source document.<br />

F. Completeness<br />

As from the original source document.<br />

G. Correction of Errors<br />

Since the raster images are obtained from the original source document and equivalency with<br />

the paper is desired, correction of errors without the revision of the equivalent paper<br />

publication or notice to the end user is not allowed.<br />

H. Signatures for Approved Data<br />

As from the original source document.<br />

6.3 Authenticity Guidelines for Pageless Publications<br />

This subsection identifies the Authenticity Rules for Pageless publications defined in Section 1.2.4 B of this<br />

specification.<br />

A. Content and Display<br />

The following represent the Authenticity Rules governing the content and display of electronic<br />

data in a Pageless publication:<br />

• Text content between the paper and electronic information must be identical<br />

• Relationships and subordination implied by indentation must be preserved<br />

MARCH 1999 25


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

• Indentation size may differ between paper and electronic text to maximize the usage<br />

of the electronic display area<br />

• Typefaces may differ between paper and electronic text to maximize the readability<br />

of the electronic text (including, but not limited to: body text, titles, and captions)<br />

• Typeface sizes may differ between paper and electronic text to maximize the<br />

readability of the electronic text (including, but not limited to: body text, titles, and<br />

captions)<br />

• Graphic content between the paper and electronic information must be identical,<br />

except:<br />

−<br />

−<br />

−<br />

Graphic "noise" may be removed from electronic graphics<br />

Electronic graphics may be cropped of white space<br />

Complex multiview graphics may be separated into individual files<br />

• Logos may be replaced by equivalent text<br />

• Pagination when printed will most likely not match the equivalent paper publication.<br />

B. Front Matter<br />

Portions of the equivalent paper publication front matter (e.g., title pages and list of effective<br />

pages) if included should be identified "For Paper Reference Only" or may optionally be<br />

excluded from the pageless publication.<br />

Front matter, if included, must be accessible from the table of contents, and must appear in<br />

its original location during “page turning" (i.e., the beginning of a chapter or the beginning of a<br />

publication).<br />

However, upon direct entry at the beginning of a publication or chapter, the user will be<br />

brought to the logical beginning of the information, not the front matter.<br />

C. Headers and Footers<br />

The inclusion of repeating headers and footers in the electronic data is allowed.<br />

The following identifying information is required to be visible whenever text or graphic images<br />

are displayed by the retrieval software via a vehicle such as a title strip, status bar, caption<br />

bar or about screen:<br />

• MRU identity - title or illustration caption<br />

• MRU revision date<br />

• CD library<br />

• CD issue date<br />

• Manufacturer and model (if feasible).<br />

Since this same information will be provided on the printed page, the inclusion of a Header<br />

and a Footer in the data is unnecessary. Additionally, the repetitive appearance of Header<br />

and Footer information can be intrusive to the reader while scrolling through pageless data.<br />

D. Page Numbers<br />

The inclusion of page numbers in the electronic data is allowed to facilitate reference to<br />

equivalent paper publications<br />

26 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

E. Text and Graphics Display<br />

Although the equivalent paper publication may have text and graphics appearing on the<br />

same page. it is acceptable that they be separated.<br />

The following text and graphic screen display options are allowed:<br />

• Simultaneous text and graphic display in a single window (in-line graphics)<br />

• Simultaneous text and graphic display in separate windows (overlapping or side-byside)<br />

• Singular display of text or graphic in a single window (with a method for switching<br />

between text and graphics without an intermediate step).<br />

F. Completeness<br />

Except for the differences specifically defined in this section, a paper publication and a<br />

pageless publication with the same title and revision level must have the same contents.<br />

G. Correction of Errors<br />

Errors identified during data conversion should be reported back to the originating author for<br />

correction of the source documentation.<br />

H. Signatures for Approved Data<br />

Aviation regulatory authority approval signatures and signatures attesting to the source of<br />

publication should be captured as raster images and made available within the electronic<br />

version of the information.<br />

I. Consistency in Terminology and Nomenclature<br />

Since inconsistency in terminology and parts nomenclature within and between publications<br />

will result in incomplete or erroneous word search results, it is recommended that<br />

publications be reviewed for this potential problem prior to release as electronic publications.<br />

If it is determined that the problem exists, a suitable notice should be given to the end user.<br />

Any corrected or amended terminology or nomenclature must not be changed without also<br />

revising the equivalent paper publication.<br />

6.4 Authenticity Guidelines for Bookless Publications<br />

This section is reserved for future discussion of bookless publications defined in Section 1.2.4 C of this<br />

specification.<br />

MARCH 1999 27


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

7. FUNCTIONALITY<br />

7.1 General<br />

This section describes the minimum functionality requirements for electronic document and graphics retrieval<br />

software, referred to in this section as the "retrieval software". It is based upon a subset of the ATA<br />

Specification 2100 General Functional Requirements as applicable to general aviation technical<br />

documentation converted for electronic publication. This specification contains general requirements that<br />

apply to all publications covered by the standards. All retrieval software must also conform to these<br />

requirements.<br />

7.2 Page-Based Publication Functionality<br />

This subsection describes the requirements that apply to all electronic publications and retrieval software that<br />

utilize raster images of text pages defined in Section 1.2.4 A of this specification.<br />

7.2.1 Browse / Traversal (Navigation)<br />

The following represents the retrieval software's minimum requirements for browsing and navigation:<br />

A. Publication Front Matter Data<br />

Front matter will be available as captured from the original source document.<br />

B. TOC<br />

The retrieval software will provide a table of contents for each publication that supports<br />

logical structuring. The retrieval software must permit access to the publication via this table<br />

of contents.<br />

C. Illustrations and Tables<br />

Illustrations and tables will be available as captured from the original source document. It is<br />

recommended that all illustrations and tables that are uniquely identified with a caption be<br />

accessible from a selection list.<br />

D. History Lists (audit trail)<br />

The retrieval software should maintain a history list of the documents and images traversed<br />

in a session, and allow the naming and saving of all or part of that history list. The history list<br />

will permit direct access to each listed document positioned either at the beginning of the<br />

document or on a graphic zoomed out to display the full image.<br />

7.2.2 Cross Reference Links<br />

It is recommended that the retrieval software support navigational links between data. For all publications,<br />

the retrieval software should support links where the original source document explicitly indicates a crossreference<br />

(e.g., See, Refer to ). The links should be able to connect information within a publication<br />

(intrapublication) or between publications (interpublication).<br />

The user should be able to select the links using direct point-and-click manipulation (hyperlink). Upon<br />

selection of a link, the retrieval software will traverse to the other end (page) of the link directly (so long as<br />

alternative cross-references are not available) without a need to go through intermediate steps.<br />

Links should be visually distinguishable on the screen display.<br />

Links should be supported from:<br />

• Text to text<br />

• Text to graphics<br />

MARCH 1999 29


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

• Graphics to text<br />

• Graphics to graphics<br />

• Text to database<br />

• Graphics to database<br />

• Database to text<br />

• Database to graphics.<br />

7.2.3 Search<br />

A. Word Search<br />

It is recommended that the retrieval software be able to search throughout a publication for<br />

every occurrence of a word, combination of words or alphanumeric strings, phrase or<br />

number. The entire contents of text provided must be searchable except for common "stop"<br />

or "noise" words (e.g., a, an, and. by. the). If there is a possibility that every occurrence of the<br />

search expression will not be found, the user should be so advised.<br />

The retrieval software should:<br />

• either ignore differences in the case of alphabetic characters or provide a caseinsensitive<br />

option.<br />

• either ignore differences in word pluralization or provide a plural-insensitive option.<br />

• allow the use of a wildcard (*) to match any sequence of one or more trailing<br />

characters at the end of a word.<br />

• allow a search with a single missing character (e.g., 35?72)<br />

B. Scope of Search (Domain)<br />

The retrieval software should allow the search to be limited in scope to:<br />

• A specific publication type<br />

• A specific publication<br />

C. Search Expressions<br />

Search expression construction should support the following Boolean operators and proximity<br />

statements:<br />

• And<br />

• Or<br />

• And not<br />

• Within 5 (before and after)<br />

• Within 10 (before and after)<br />

• User definable Within 1-99 (before and after)<br />

D. Search Results<br />

The search will return an unambiguous identifier (e.g., title) for each MRU (refer to Section<br />

7.3.6 for a discussion of MRUs).<br />

Search results will be presented as a summary. Occurrences of the search expression within<br />

the MRU will be included with the summary. The retrieval software must provide a<br />

30 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

mechanism to launch to any item selected. When a search result contains only one item, the<br />

retrieval software shall present the item directly.<br />

Displayed text search results will be distinguishable from the other text (i.e., highlighted or<br />

inverse video).<br />

7.2.4 Retrieval Software Response<br />

A. Response Time<br />

The following specific maximum response time requirements apply when operating on either<br />

the minimum or recommended retrieval system configuration.<br />

Word Search<br />

During a word search, the retrieval software should display partial results if a search<br />

cannot be completed within fifteen seconds. The search may optionally continue<br />

during preliminary display.<br />

Text and Graphic Display<br />

Same requirements as Section 7.3.4 A 2.<br />

B. In-progress Status Message<br />

Same requirements as Section 7.3.4 B.<br />

C. Process Interruption<br />

Same requirements as Section 7.3.4 C.<br />

7.2.5 Printing<br />

A. Print Information<br />

At a minimum, the retrieval software must provide the following information on all printouts:<br />

• MRU Identity - Title or Illustration Caption<br />

• MRU Revision Date<br />

• CD Library<br />

• CD Issue Date<br />

Recommendations for inclusion on all printed pages produced by the retrieval software:<br />

• System Date and Time of Print<br />

• Manufacturer and Model (if feasible)<br />

• A statement advising the user not to retain printed pages. For example:<br />

"`This page must not be retained for future reference."<br />

B. General Printing<br />

The retrieval software must provide the following print options:<br />

• "Print Screen" capability for the current screen (text and/or graphics).<br />

• Print the current page<br />

• Print the current MRU<br />

The retrieval software may provide printing of the marked section of the graphic currently displayed.<br />

MARCH 1999 31


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

C. Range Printing<br />

The retrieval software will support the printing of a range of pages.<br />

D. Summary Data<br />

The retrieval software should be able to print any generated summary or selection list (i.e., a list of<br />

search results or a list of bookmarks).<br />

Additionally, the retrieval software should be able to print all tables of content.<br />

7.2.6 Revision Identification (Tracking and Control)<br />

A. Revised Material Identification<br />

The retrieval software must be capable of displaying revision symbols as they appear in graphics. For<br />

additional information, refer to GAMA Specifications 1 and 2.<br />

B. Effectivity Identification and Control<br />

Effectivity identification and control will be available as occurring in the original list of effective pages.<br />

When applicable the recommendations occurring in Section 7.3.6 should also be used.<br />

C. Presentation of Revision Information<br />

The retrieval software will provide a method of displaying the title of the publication being viewed, and<br />

the revision date of the current page via a vehicle such as a title strip, status bar or caption bar.<br />

D. Temporary Revisions<br />

The retrieval software must provide a method for visually distinguishing temporary revisions when the<br />

equivalent paper publication uniquely identifies temporary revisions (i.e. "yellow sheets").<br />

7.2.7 Data Integrity<br />

Data integrity assurance will be available as via the original list of effective pages.<br />

7.2.8 Data Export<br />

The retrieval software may support the copying of a marked area of a graphic, at any magnification, to the<br />

Microsoft Windows® Clipboard for incorporation into other Microsoft Windows® applications.<br />

7.2.9 Help<br />

The retrieval software will have the same requirements as Section 7.3.9.<br />

7.3 Pageless Publication Functionality<br />

This subsection describes the requirements that apply to all pageless publications and retrieval software that<br />

utilizes the display of ASCII text rather than raster images of text pages as defined in Section 1.2.2 B of this<br />

specification.<br />

7.3.1 Browse / Traversal (Navigation)<br />

The following represents the retrieval software's minimum requirements for browsing and navigation:<br />

A. Publication Front Matter Data<br />

Front Matter must be made available from the table of contents, and must appear in its original<br />

location during "page turning" (i.e., the beginning of a chapter or the beginning of a publication).<br />

32 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

However, upon direct entry at the beginning of a publication or chapter, the user will be brought to the<br />

logical beginning of the information, not to the front matter.<br />

Refer to the glossary of terms appended to this specification for more information on front matter.<br />

B. TOC<br />

The retrieval software will provide a table of contents of text and graphic minimum revisable units for<br />

each publication that supports such structuring. The retrieval software must permit access into the<br />

publication via this table of contents.<br />

C. Illustrations and Tables<br />

The retrieval software will support the display of any illustration or table included, or referred to, in<br />

the text.<br />

Illustrations and tables (according to the rules defined in Section 5.2.5) will be available as scanned<br />

from the original paper source document. It is recommended that all illustrations and tables that are<br />

uniquely identified with a caption be accessible from a selection list.<br />

The following text and graphic screen display options are allowed:<br />

• Simultaneous text and graphic display in a single window (inline graphics)<br />

• Simultaneous text and graphic display in separate windows (overlapping or side-by-side)<br />

• Display of text or graphic in a single window (with a method for switching between text and<br />

graphics without an intermediate step)<br />

D. Backtracking<br />

The retrieval software will maintain a record of the user's navigation within and across publications<br />

during the current session. Departure points (the text being displayed at the time of leaving a MRU)<br />

will be tracked, and a mechanism will be provided to directly select and return to any of these<br />

departure points.<br />

The retrieval software should keep track of a minimum of the last 24 departure points during the<br />

current session.<br />

E. Bookmarks<br />

The retrieval software will provide support for user-definable bookmarks. The bookmark will record a<br />

specific position in the publication. The retrieval software will provide the user with a mechanism to<br />

access the list of previously defined bookmarks, and the ability to navigate to a bookmark's location.<br />

The retrieval software should permit the saving of user-defined bookmarks such that they can be<br />

recalled and re-used in future sessions.<br />

Upon revision of the publication by the author, the system relocated position of the bookmarks<br />

should conform to the following rules:<br />

• If a particular MRU contains a bookmark and that MRU has not been revised, the position of<br />

the bookmark is preserved within the MRU.<br />

• If an MRU containing a bookmark has been revised, but the text containing the bookmark has<br />

not changed, the bookmark is preserved within the MRU.<br />

• If an MRU containing a bookmark has been revised and the text containing the bookmark has<br />

changed, the bookmark repositions to the beginning of the MRU.<br />

• If an MRU containing a bookmark is eliminated, the bookmark is orphaned and repositions to<br />

the next higher level within the publication (i.e. section, chapter, title page).<br />

MARCH 1999 33


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

F. Annotations<br />

To accommodate the creation of reference work aids, the retrieval system may provide an<br />

annotations function. Annotations can be used, for example, to record cross references to other<br />

publications, to note the location of tools or consumables, for reminders of product repair and<br />

modifications and to note product support contacts and phone numbers.<br />

The retrieval software may provide support for user definable annotations. The annotations function,<br />

if implemented, must comply with the following requirements:<br />

• Annotations must be clearly distinguishable (in a separate pop-up dialog box) from the<br />

author's unaltered source information.<br />

• Annotations must be stored as a separate data file from the author's unaltered source<br />

information.<br />

The annotations function, if implemented, should also comply with the following requirements:<br />

• Text may be input as an annotation at a user-defined specific position in the publication.<br />

• The retrieval software should provide the user with a mechanism to access the list of<br />

previously defined annotations, delete previously defined annotations and the ability to<br />

navigate to an annotation's location.<br />

• The retrieval software should permit the saving of user-defined annotations such that they<br />

can be recalled and re-used in future sessions.<br />

• Upon revision of the publication by the author, the system-relocated position of the<br />

annotations should conform to the rules identified for bookmarks above. The retrieval<br />

system should indicate to the user if the attachment position has been modified due to<br />

revision of the publication and enable a means of reattachment to a new position.<br />

• Annotations should record the date last updated and the originator's identity.<br />

G. History Lists (audit trail)<br />

The retrieval software will maintain a history list of the MRUs and images traversed in a session, and<br />

allow the naming and saving of all or part of that history list. The history list will permit directly<br />

accessing each listed MRU positioned to either the beginning text or graphic zoomed out to display<br />

the full image.<br />

H. Direct Access to MRUs<br />

The retrieval software may provide the user with the means to display any MRU by direct reference<br />

to the MRU through for example a system index number.<br />

7.3.2 Cross Reference Links<br />

The retrieval software will support navigational links between data. For all publications, the retrieval software<br />

will support links where the text explicitly indicates a cross-reference (e.g., See Refer to). The links must be<br />

able to connect information within a publication (intrapublication) or between publications (interpublication).<br />

The user must be able to select the links using direct point-and-click manipulation (hyperlinking). Upon<br />

selection of a link, the retrieval software will link directly to the hyperlink target going through intermediate<br />

steps, so long as alternative cross references are not available.<br />

Links must be visually distinguishable on the screen display.<br />

If applicable, links must be supported from:<br />

• Text to text<br />

• Text to graphics<br />

• Graphics to text<br />

34 MARCH 1999


• Graphics to graphics<br />

• Text to database<br />

• Graphics to database<br />

• Database to text<br />

• Database to graphics<br />

GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

7.3.3 Search<br />

A. Word Search<br />

The retrieval software must be able to search throughout a publication for every occurrence of a<br />

word, combination of words or alphanumeric strings, phrase or number. The entire contents of text<br />

provided must be searchable except for common "stop" or "noise" words (e.g., a, an, and, by, the).<br />

The retrieval software will:<br />

• either ignore differences in the case of alphabetic characters or provide a case-insensitive<br />

option.<br />

• either ignore differences in word pluralization or provide a plural-insensitive option.<br />

• allow the use of a wildcard (*) to match any sequence of one or more trailing characters at<br />

the end of a word.<br />

• allow a search with a single missing character (e.g., 35?72).<br />

B. Scope of Search (Domain)<br />

The retrieval software will allow the search to be limited in scope to:<br />

• A specific publication type<br />

• A specific publication<br />

C. Search Expressions<br />

Search expression construction must support the following Boolean operators and proximity<br />

statements:<br />

• And<br />

• Or<br />

• And not<br />

• Within 5 (before and after)<br />

• Within 10 (before and after)<br />

• User definable Within 1-99 (before and after)<br />

D. Search Results<br />

The search will return an unambiguous identifier (e.g., title) for the MRU.<br />

Search results will be presented as a summary. Occurrences of the search expression within the<br />

MRU will be included with the summary. The retrieval software must provide a mechanism to launch<br />

to any item selected. When a search result contains only one item, the retrieval software shall<br />

present the item directly.<br />

In the data, search results will be distinguishable from other text (i.e., highlighted or inverse video).<br />

MARCH 1999 35


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

7.3.4 Retrieval Software Response<br />

The following specific maximum response time requirements apply when operating on either the minimum or<br />

recommended retrieval system configuration.<br />

A. Response Time<br />

During a word search, the retrieval software will display partial results if a search cannot be<br />

completed within fifteen seconds. The search may optionally continue during preliminary display.<br />

The following specific maximum response time requirements apply:<br />

• Publication front matter data will be displayed within 15 seconds of request.<br />

• TOC data will be displayed within 15 seconds of request.<br />

• A specific illustrations shall be displayed within 10 seconds of request.<br />

• Intrapublication links shall be accomplished within 5 seconds.<br />

• Interpublication links shall be accomplished within 15 seconds.<br />

B. In-progress Status Message<br />

The retrieval software will at a minimum provide a system busy icon for operations estimated to take<br />

longer than three seconds. It is recommended that a status message be presented while processing<br />

operations that exceed fifteen seconds are being performed.<br />

C. Process Interruption<br />

The retrieval software must provide a simple means for the end user, if desired, to interrupt any<br />

process operation (e.g., search, print, etc.). Upon such interruption, the retrieval software will return<br />

the user to the point he was at immediately before the interrupted process started.<br />

7.3.5 Printing<br />

A. Print Information<br />

At a minimum, the retrieval software must provide the following information on all printouts:<br />

• MRU identity - title or illustration caption, MRU revision date<br />

• CD library<br />

• CD issue date<br />

The following are recommended for inclusion on all printed pages produced by the retrieval software:<br />

• Retrieval software date and time of print<br />

• Manufacturer and model (if feasible)<br />

• A statement advising the user not to retain printed pages. For example:<br />

"This page must not be retained for future reference."<br />

B. General Printing<br />

The retrieval software will provide the following print options:<br />

• A "Print Screen" facility for the current screen (text and/or graphics).<br />

• Print the page currently displayed<br />

• Print the graphic currently displayed<br />

• Print the MRU currently displayed<br />

36 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

The retrieval software may provide the following print options:<br />

• Print the currently marked text<br />

• Print the marked section of the graphic currently displayed<br />

C. Range Printing<br />

The retrieval software will support the printing of the following range options:<br />

• MRU<br />

• MRU and its associated graphics only<br />

• A range of MRUs.<br />

D. Summary Data<br />

The retrieval software will be able to print any generated summary or selection list (i.e., a list of<br />

search results or a list of bookmarks).<br />

Additionally, the retrieval software will be able to print all tables of content.<br />

7.3.6 Revision Identification (Tracking and Control)<br />

A. Revised Material Identification<br />

1. Text<br />

The retrieval software must be capable of displaying revision symbols (e.g., revision bars - |<br />

or R). For additional information, refer to GAMA Specifications 1 and 2.<br />

2. Graphics<br />

The retrieval software must be capable of displaying revision symbols as they appear in<br />

graphics. For additional information, refer to GAMA Specifications 1 and 2.<br />

B. Minimum Revisable Unit - Granularity<br />

To accommodate revisioning and indexing of pageless information, the publication's data is divided<br />

into logical groupings.<br />

Since the concept of individual pages is not utilized in a pageless representation of electronic data,<br />

the ability to record revisions for a specific page as they appear on the paper may not be possible.<br />

Therefore, a logical subdivision of the data is identified as appropriate for carrying revision<br />

information. That subdivision is referred to as a Minimum Revisable Unit (MRU), and serves as the<br />

basis for electronic table of contents and data exchange.<br />

For graphics, a single graphic is the minimum revisable unit. The following table depicts the rules for<br />

text MRUs:<br />

Table 7-1<br />

Rules for Text MRUs<br />

Publication Type<br />

Maintenance Manual (MM) type of<br />

publication<br />

Illustrated Parts Catalog (IPC)<br />

Service information<br />

Airworthiness Directives (AD)<br />

Revisable Unit<br />

Page block, or task, or comparable<br />

unit<br />

Parts list pertaining to a figure<br />

Complete service information<br />

Complete AD<br />

MARCH 1999 37


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

C. Minimum Revisable Unit-Based Revision Dates<br />

Revision marking and dating applies to the entire MRU. Upon revising an MRU, all prior revision bars<br />

are eliminated and only the revised content for this revision will be marked.<br />

D. Effectivity Identification and Control<br />

At a minimum a list of effective MRUs will be presented which includes the MRU identity and revision<br />

date.<br />

The original paper's List of Effective Pages (LEP) may be included as a reference tool for personnel<br />

supporting customers with paper publications. This information may not be relevant to the electronic<br />

version of the information.<br />

It is recommended that an LEP be marked "For Paper Reference Only" when included with the<br />

electronic data.<br />

E. Presentation of Revision Information<br />

The retrieval software will provide a method of displaying the title of the MRU being viewed, and it’s<br />

revision date via a vehicle such as a title strip, status bar or caption bar.<br />

F. Temporary Revisions<br />

The retrieval software must provide a method for visually identifying temporary revisions to the<br />

equivalent paper publication.<br />

7.3.7 Data Integrity<br />

The retrieval software will accommodate data integrity assurance by providing a record of MRU revision<br />

activity. The user must be provided a means of determining which MRUs have been revised in the current<br />

revision as well as the date of last revision for every MRU in the publication.<br />

7.3.8 Data Export<br />

7.3.9 Help<br />

A. Text<br />

The retrieval software will support the copying of any amount of marked text (within the limitations of<br />

the end user's hardware and software) to the Microsoft Windows® Clipboard for incorporation into<br />

other Microsoft Windows® applications.<br />

B. Graphics<br />

The retrieval software will support the copying of a marked area of a graphic, at any magnification, to<br />

the Microsoft Windows® Clipboard for incorporation into other Microsoft Windows® applications.<br />

The retrieval software will provide help function via a single action on the keyboard or other input device.<br />

The online help function will contain, at a minimum, those requirements defined in Section 4.3 of this<br />

specification. Additionally, online Help will follow the Microsoft Windows® Help system conventions,<br />

including:<br />

• Context-sensitivity from within the retrieval software<br />

• Search within the Help system<br />

• Use of Bookmarks<br />

• Use of Annotations<br />

• Ability to copy information to the Microsoft Windows Clipboard<br />

• Ability to print Topics<br />

• History tracking within the Help system<br />

38 MARCH 1999


7.4 Bookless Publication Functionality<br />

GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

This section is reserved for future discussion of the functionality of bookless publications defined in Section<br />

1.2.4 C.<br />

MARCH 1999 39


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

8. OPERATING CONTROLS<br />

8.1 General<br />

This section describes the minimum requirements for retrieval software operating controls that shall conform<br />

to the following Microsoft Windows®; conventions as defined in the Microsoft Common User Access -<br />

Advanced Interface Design Guide. Additionally operating control conventions are specified to standardize the<br />

end user control of the functionality defined in Section 7.<br />

8.2 Retrieval Software Controls<br />

The retrieval software may support the following types of operating controls and functionality:<br />

• Pull down menus<br />

• Dialog boxes<br />

• Buttons<br />

• Keyboard shortcuts<br />

8.3 Keyboard Access and Navigation<br />

This subsection describes appropriate keyboard and control activities within dialog boxes and retrieval<br />

screens and identifies the minimum requirements for retrieval software-wide keyboard response.<br />

8.3.1 Dialog Box Controls<br />

Microsoft Windows® standard dialog box controls, as described in the Common User Access - Advanced<br />

Interface Design Guide, should be used for all dialog boxes.<br />

MARCH 1999 41


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

8.3.2 Navigation and Keyboard Access within Dialog Boxes<br />

Table 8-1<br />

Navigation and Keyboard Access within Dialog Boxes<br />

Key Conditions Action<br />

Control buttons<br />

Operates the Control<br />

Alt+Mnemonic<br />

(Underlined letter on a<br />

control label)*<br />

Option Buttons<br />

Check Boxes<br />

Selects the Control<br />

Enter<br />

List Boxes (all)<br />

Default command button (if<br />

present)<br />

Moves the focus to the control<br />

Operates the control<br />

Selected command button (if Operates the control<br />

no default button is present)<br />

Esc All Operates the Cancel or Close button if present<br />

Spacebar<br />

Command button with focus Operates the control<br />

Option Button with focus or<br />

Check box with focus<br />

Selects the control<br />

Text input field<br />

Inserts a space<br />

Tab All Moves the focus (active state) to the next control (button,<br />

check box, drop down, etc.). Typically, focus movement<br />

is from left to right and from top to bottom, and that<br />

sequencing has been employed except in those<br />

instances where a more appropriate route has identified.<br />

Shift+Tab All Reverses the Tab navigation order by moving the focus<br />

to the prior control.<br />

Arrow Keys<br />

Option Buttons (Group) Selects the next button, wraps at top and bottom of group<br />

<br />

<br />

<br />

Alt+Down Arrow <br />

Alt+Up Arrow <br />

Del<br />

Check Boxes<br />

List Boxes<br />

Spin Boxes<br />

Text Boxes<br />

Drop-down List Boxes and<br />

Drop-down Combo Boxes<br />

Text Input Fields<br />

(text selected)<br />

Moves focus to next button without selection, wraps at<br />

top and bottom of group<br />

Selects next item, does not wrap to top of list<br />

Increases or decreases value, wraps at highest and<br />

lowest values<br />

Moves insertion to the left, right, up or down<br />

Toggles between collapsed and expanded state of active<br />

drop-down.<br />

Deletes selected text<br />

Text Input Fields<br />

(no text selected)<br />

Backspace ← Text Input Fields<br />

(text selected)<br />

Deletes character just right of the insertion point<br />

Deletes selected text<br />

Text Input Fields<br />

Deletes character just left of the insertion point<br />

(no text selected)<br />

Ins Text Input Fields Toggles between insert mode and Over type mode<br />

* No Alt+mnemonic combinations are reserved or recommended by Microsoft, however when a HELP control<br />

button is present, its shortcut key combination is Alt+H. All Alt+ mnemonic combinations must be unique<br />

within the active dialog box(es).<br />

42 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

8.3.3 Navigation within Text or Image Retrieval Screens<br />

Table 8-2<br />

Navigation within Text or Image Retrieval Screens<br />

Key Conditions Action<br />

Home All Moves cursor to the beginning of the current<br />

page<br />

End All Moves cursor to the end of the current page<br />

Ctrl+Home All Moves cursor to the beginning of the current<br />

document<br />

Ctrl+End All Moves cursor to the end of the current<br />

document<br />

Page UP Within a publication Scrolls up a screen<br />

Page Up Within an image Scrolls up a screen (maintaining zoom)<br />

Page Down Within a publication Scrolls down a screen<br />

Page Down With a graphic Scrolls down a screen (maintaining zoom)<br />

Ctrl+Page Up Within a publication Beginning of previous publication (MRU)<br />

Ctrl+Page Up Within a graphic Displays previous graphic<br />

Ctrl+Page Down Within a publication Beginning of next publication (MRU)<br />

Ctrl+Page Down Within a graphic Displays next graphic<br />

8.3.4 Control Key Shortcuts<br />

Table 8-3<br />

Control Key Shortcuts<br />

Ctrl+C*<br />

Ctrl+V*<br />

Ctrl+P**<br />

Key<br />

Action<br />

Copy to the Windows Clipboard<br />

Paste from the Windows Clipboard<br />

Open the Print dialog box<br />

* Recommended by Microsoft<br />

** Suggested by Microsoft<br />

MARCH 1999 43


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

8.3.5 Function Key Shortcuts<br />

Table 8-4<br />

Function Key Shortcuts<br />

Key<br />

F1* Brings up Help<br />

Action<br />

Alt+F4*<br />

Close the Application<br />

* Recommended by Microsoft<br />

8.4 Retrieval Software Conventions<br />

This section is reserved for a future discussion of operating control conventions to be used to standardize the<br />

presentation to the end user of the functionality defined in Section 7.<br />

44 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

9. ASSOCIATED <strong>STANDARD</strong>S<br />

9.1 General<br />

This section identifies additional controlled vocabularies and technical specifications to be used in the<br />

creation of electronic publications and retrieval software. The consistent use of controlled vocabularies is<br />

necessary to accommodate word search in electronic publications in fulfillment of the end user's<br />

expectations. Technical specifications are necessary to accommodate data exchange and retrieval software<br />

interchangeability as well as standardize content, format and structure.<br />

9.2 Controlled Vocabularies<br />

The consistent use of nomenclature across publications facilitates electronic word searching and eliminates<br />

information ambiguity.<br />

As a minimum requirement, Webster's Dictionary shall be used for English language definitions and spelling<br />

(except for new terminology that has not yet been incorporated.)<br />

AECMA Simplified English is recommended for the unambiguous and consistent use of the English language.<br />

9.3 Required Standards<br />

The following constitutes required Standards:<br />

• ISO 8879 - Standard Generalized Markup Language<br />

• ISO 9660- This Standard describes the CD-ROM formatting to accommodate universal<br />

interchangeability.<br />

Content Specifications<br />

• ATA Specification 100<br />

• ATA Specification 2100<br />

Available From:<br />

Air Transport Association<br />

1301 Pennsylvania Ave., NW<br />

Suite 1100<br />

Washington, DC 20004-1707<br />

(202) 626-4000<br />

http://www.air-transport.org/<br />

• GAMA Specification 1 Pilots Operating Manual<br />

• GAMA Specification 2 Maintenance Manual<br />

Available From:<br />

General Aviation Manufacturers Association<br />

1400 K Street NW, Suite 801<br />

Washington, D.C. 20005<br />

(202) 393-1500<br />

http://www.generalaviation.org<br />

MARCH 1999 45


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

9.4 Recommended Standards<br />

The following is a list of recommended Standards for reference:<br />

• Guide to Simplified Graphics - Technical Report No. 92-1<br />

Available From:<br />

Aerospace Industries Association<br />

1250 Eye Street, NW<br />

Washington, DC 20005 - USA<br />

Technical Specifications:<br />

• Aldus TIFF<br />

Available From:<br />

Aldus Corporation<br />

411 First Ave. S Suite 200<br />

Seattle, WA 98104- USA<br />

• ISO CGM Specification #<br />

Available From:<br />

ANSI<br />

1430 Broadway<br />

New York, NY 10018 - USA<br />

• ISO CCITT Specification # [what belongs here?]<br />

Available from:<br />

CCITT<br />

Place des Nations<br />

12111 GENEVA 20- Switzerland<br />

• Common User Access - Advanced Interface Design Guide<br />

Available from:<br />

Microsoft Corporation<br />

One Microsoft Way<br />

Redmond, WA 98052-6399 - USA<br />

46 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

10. GAMA DTD INFORMATION<br />

The GAMA DTDs are designed for the conversion of legacy publications, or the generation of new<br />

publications, in a structured format based on the ATA Specification 2100. Except for the inclusion of DTD<br />

changes related to GAMA, the DTDs are formatted to conform to ATA Specification 2100 DTD style guides.<br />

The GAMA DTDs are available at the GAMA World Wide Web site, http://www.generalaviation.org under the<br />

“publications” link.<br />

The GAMA DTDs derived from their equivalent ATA Specification 2100 DTD are listed below:<br />

GAMASB.DTD<br />

GAMAWM.DTD<br />

GAMAAMM.DTD<br />

GAMAAIPC.DTD<br />

GAMAEMM.DTD<br />

GAMAEIPC.DTD<br />

GAMASIMM.DTD<br />

The GAMASIMM.DTD provides a way to convert legacy data into structured information. It can be modified<br />

by users as needed to support internal data conversion projects. However, remember to change the DTD<br />

public identifier to ensure that only the modified DTD is used during document instance validation.<br />

MARCH 1999 47


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

11. GLOSSARY OF <strong>ELECTRONIC</strong> PUBLICATION TERMS<br />

Aircraft Specific - Information that relates to a particular aircraft based upon any of several factors of<br />

Effectivity, (i.e. manufacturer, model number, part number, serial number...)<br />

Annotations - Comments created by the user and associated with a location within the text or graphic of an<br />

electronic publication. Annotation place holders permit the viewing of previously saved annotations via a pop<br />

up text display. From a selection list of annotations, the user can hyperlink to the particular location or range<br />

of text where the annotation was originally defined.<br />

ANSI - American National Standards Institute<br />

11 West 42nd Street<br />

New York, NY 10036- USA<br />

(212) 642-4900<br />

ASCII - American Standard Code for Information Interchange; a binary code representing alphanumeric<br />

characters that permit the exchange of data between most minicomputers and personal computers utilizing<br />

different operating systems.<br />

ATA - Air Transport Association<br />

1301 Pennsylvania Ave, NW<br />

Washington, D.C. 20004-1707 - USA<br />

(202) 626-4000<br />

ATA Specification 100 - Air Transport Association's specification that provides guidance to the content and<br />

format of aircraft maintenance publications.<br />

ATA Specification 2100 - Air Transport Association's specification that establishes standards for the<br />

authoring, interchange, delivery and use of digital data produced by aircraft, engine and component<br />

manufacturers.<br />

Authoring - Refers to the process of creating new information.<br />

Authoring systems - Can include a wide range of systems from word processors to electronic publishing<br />

systems.<br />

Backtracking - The retrieval software's ability to keep track of prior screens viewed when a user departs to<br />

other screen views. This allows the user to return to a limited number of stored prior views at a later time<br />

during a search, usually through the use of a function key command or macro.<br />

Bitmap Image - is a raster image made up of pixels, or dots, that are either black and white (bilevel), shades<br />

of gray (gray-scale), or color. Windows Bitmap (BMP) is a popular format among PC software exchange<br />

options.<br />

BMP - (Bit MaP) Windows graphics format that may be device dependent or independent. Device<br />

Independent BMP files (DIB) are coded for translation to a wide variety of displays and printers.<br />

Bookless Publications - Electronic publications in that the information is maintained via a database of task<br />

based elements that do not require the information to be structured in books. The ATA Specification 2100's<br />

use of SGML and SFQL based retrieval systems are an example of Bookless Publications.<br />

Bookmarks - A bookmark is a place holder that marks the current view. Bookmarks allow the user to identify<br />

a particular location in the text that can be directly accessed in future sessions.<br />

Boolean Search - A search method used to access information in a database by specifying search criteria<br />

based upon Boolean operators such as AND, OR and NOT. Boolean operators help to create a true or false<br />

filter to narrow the scope of information to be retrieved.<br />

Browse / Browsing - Method of locating information in a database by utilizing either a table of contents or<br />

moving through the document by using its logical structure.<br />

Button - Buttons are click-on icons that appear throughout windows programs in such places as toolbars and<br />

dialog boxes.<br />

MARCH 1999 49


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

CAD - Computer Aided Design. Refers to the use of computers to design products. CAD systems are<br />

workstations or PCs using CAD software and graphic input devices. CAD software is used for generic design<br />

or specialized uses, such as architectural, electrical and mechanical designs.<br />

CALS - Computer-Aided Acquisition and Logistics Support. A U.S. Department of Defense 1985 initiative to<br />

provide a framework for the transmission and usage of information on weapon systems in electronic form.<br />

The support of specific standards by the CALS initiative has accelerated industry-wide adoption of these<br />

standards, including CCITT Group IV and SGML.<br />

CCITT - Consultative Committee on International Telegraphy and Telephony. This international advisory<br />

committee originally established under the United Nations endorses a variety of communications usage<br />

standards, particularly facsimile and image compression and decompression, including the CCITT Group 3<br />

and Group 4 standards that are used widely in image storage and transmission.<br />

CCITT<br />

Place des Nations<br />

12111 GENEVA 20 - Switzerland<br />

CD-ROM - Compact Disc Read Only Memory. Designed primarily for use as an electronic publishing medium,<br />

a CD-ROM is capable of storing text, graphics and audio data. Unlike hard disks and floppy disks, a CD-ROM<br />

is read only, meaning it does not permit the user to write information to the disc. A single CD-ROM can store<br />

up to 660 megabytes of information and has a storage capacity equivalent to 550 1.2 MB floppy disks.<br />

CD-ROM Drive - Device connected to a computer for reading data from CD-ROMs.<br />

CGM - Computer Graphics Metafile. The ISO standard format that identifies the three versions of metafiles<br />

used to exchange vector data and textural characters. Often used as a cross-platform exchange option, CGM<br />

store graphics primarily in a vector format but also provides a raster format enabling color fills.<br />

Compact Disc - Commonly referred to as a CD. A CD is a molded plastic disk on which data is recorded as<br />

microscopic pits to be read optically by a laser beam.<br />

Controlled Vocabularies - A specific source or sources of words, phrases, and terminology in an<br />

alphabetical arrangement accessed to provide uniform cross-referencing.<br />

CPU - Central Processing Unit. Most commonly refers to the part of a computer that controls translation and<br />

execution of processing instructions. Informally, the term CPU is sometimes used to refer to a single PC<br />

workstation unit.<br />

Cross Reference Links - Connection of information within a publication or between publications where the<br />

original source document indicates a cross-reference.<br />

Database - A collection of electronically stored data that is structured and organized to facilitate efficient<br />

retrieval of information.<br />

Database Preparation Software - Software used to organize and index a database.<br />

Data Capture - The process of converting data from non-electronic formats (such as paper, photographs,<br />

drawings, etc.) into an electronic format that makes possible the retrieval, storage and modification of the<br />

data on a computer system.<br />

Data Conversion - The process of converting information from one electronic format to another. For<br />

example, text information can be converted from WordPerfect to ASCII and graphic information can be<br />

converted from an uncompressed bitmap image to a compressed format like CCITT Group 4 Fax.<br />

Data Refinement - The Process of converting data into an enhanced format based upon the content,<br />

structure and meaning of the data. This refinement process may involve adding special tags identifying the<br />

documents structure or generating specialized indexes and a table of contents.<br />

Dialog Box - A window that displays options available within a particular command. For example, a print<br />

dialog box might display options for printing the whole document, a range of pages within a document, or only<br />

the current page.<br />

Digital - Relative to computer systems, refers to data that is composed of a series of discreet, fixed values<br />

such as single digits or characters. Digital information is recorded in a binary notation format.<br />

50 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Drive - A computer device used to read from and in some cases when to an electronic storage medium . The<br />

most widely used electronic storage medium are optical or magnetic.<br />

DTD - Document Type Definition. The programmatic rules and format definitions that describe the format<br />

commands (tags) used to define content and structure in an SGML document.<br />

DWG - The native AutoCAD 3-D vector file format that has become a standard due to its significant market<br />

share.<br />

DXF - Drawing Exchange Format. The AutoCAD® 2-D vector file format used by many CAD systems to<br />

import and export for graphics interchange.<br />

Element - (1) The discrete components defined in a Document Type Definition (DTD); (2) the individual units<br />

of information that comprise an electronic publication (e.g., text page blocks, tables, and figures).<br />

End User - The individual who uses software or hardware products and does not resell it to others.<br />

EPS - Electronic Publication Standard. The GAMA Specification 9, which as an alternative to the ATA<br />

Specification 2100, provides guidance for the transition to electronic publications by defining computer<br />

systems, data exchange, text and graphics appearance, functionality and operating controls.<br />

Flight Operations Information - The technical publications that support the operation of aircraft (e.g., Flight<br />

Manuals, Pilots Handbooks, Weight and Balance Manuals) which may be included in collections of electronic<br />

publications for reference during aircraft maintenance.<br />

Front Matter - Data found at the beginning of a document, chapter or section that is general to the element.<br />

Functionality - Performing tasks and operations by design.<br />

Full Text Searching - Also known as Full Text Retrieval (FTR). The ability to use a word or words contained<br />

within an electronic document as the criteria for retrieving information in a document Full text - searches can<br />

be based upon a single word or words in combination with other words. Words within the electronic document<br />

are indexed to accommodate this full text searching capability.<br />

GAMA - General Aviation Manufacturers Association<br />

1400 K Street NW, Suite 801<br />

Washington, D.C. 20005<br />

(202) 393-1500<br />

www.generalaviation.org<br />

Graphics - Visual data. This includes photographs, line drawings, computer-generated artwork, and graphs.<br />

Graphics can be entered into the computer using scanners, drawing programs, cameras, and graphics tables.<br />

GUI - Graphical User Interface. A layer of software that allows the user to interact with the computer by<br />

choosing items from menus or selecting icons from the screen, usually with a mouse. The Macintosh® Finder<br />

and Microsoft Windows® are examples of GUl environments.<br />

Hard Disk - Fixed disk media; generally internal, high-speed, high-capacity, rotating magnetic disk.<br />

History List - A list of the MRUs and images traversed during a session, for use in direct accessing of each,<br />

and the naming and saving for later reuse.<br />

HPGL - Hewlett-Packard Graphic Language. A descriptive plotter output file format, it is considered one of<br />

the more common interchange file formats. HPGL files are vectored.<br />

Hyperlink - The means by which sets of information are linked to each other in any combination of;<br />

application; database; document element (text, table or graphic).<br />

Hypertext - An information retrieval and search methodology based upon hyperlinks between related text,<br />

graphic and database elements that may be predefined or defined by the user.<br />

MARCH 1999 51


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

IGES - Initial Graphics Exchange Specification. The ANSI vector graphics file format that is system<br />

independent and intended for human interpretation and often used as a cross-platform exchange option.<br />

The IGES Organization<br />

National Institute of Standards and Technology<br />

Building 220 Room A-353<br />

Gaithersburg, MD 20899 USA<br />

(301) 921-3691<br />

In-Line Graphics - The on screen simultaneous presentation of text and graphics within a single display<br />

window. Sometimes referred to as compound documents.<br />

Index, Indexing - The process of building data structures for electronic databases. Indexes contain the<br />

location of each data item and permit rapid location of data.<br />

Information - Data that has been structured, indexed and formatted to make it more intelligible and helpful for<br />

people that need to make use of the data.<br />

ISO/lEO 8632:1992 - The Computer Graphics Metafile (CGM) format which identifies the three versions of<br />

metafiles used to exchange vector data and textural characters.<br />

ISO 8879 - The Standard Generalized Markup Language Specification.<br />

ISO 9660 - The international standard for directory structures and file layout on CD-ROMs, a logical,<br />

structural standard compared to the physical standards for manufacturing called the "Yellow Book." This<br />

standard specifies, for single sessions, exactly how much information is stored on a CD-ROM to be<br />

accessible in any CD-ROM drive running on a variety of common operating systems.<br />

Magnetic Media - Any medium on which data is stored as variations in magnetic polarity. Usually floppy<br />

disks, hard disks, and tape.<br />

Mastering - A part of the process of manufacturing a CD-ROM by using a laser to embed microscopic pits<br />

into the surface of a glass disk. The glass master is then used to make a metal stamper that is used to<br />

replicate CD-ROM copies of the master.<br />

Mastering Facility - A manufacturing plant where compact disc "masters" are created for the mass<br />

production or replication of the actual compact discs.<br />

Medium - Refers to an object used to store information; usually refers to a particular type of storage device<br />

such as disk, tape, microfiche or paper.<br />

Memory - In the computer industry, refers to a location where digital information is stored during processing.<br />

Memory is stored on computer chips and may be either permanent or temporary.<br />

Menu - On screen list of available functions, or operations, that can be performed currently.<br />

MIPS - Millions of Instructions Per Second. A standard means of measuring a computer's performance<br />

capabilities.<br />

MRU - Minimum Revisable Unit. Discreet, logical groupings of information used in Pageless publications to<br />

describe and work with electronic data, as opposed to an individual page. MRU examples included Page<br />

Blocks within Maintenance Manuals and Figures within IPCs<br />

Multimedia - The dissemination of information in more than one form including the use of text, audio,<br />

graphics, animated graphics and full motion video.<br />

Navigation - The process of browsing or traversing through a database or document by use of keyboard or<br />

mouse functions.<br />

Object - (1) A piece of visual data used to assist in the representation of an idea, or message. (2) A self<br />

contained module of data and its associated processing.<br />

OCR - Optical Character Recognition. Machine recognition of printed characters using a process that visually<br />

scans text (handwritten. printed and typewritten) and converts it to a standard format such as ASCII. OCR<br />

software may be used during the process of converting paper source documents for distribution via electronic<br />

publications.<br />

52 MARCH 1999


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

On-Line - Data processing method that allows users to transmit or receive data from a remote computer and<br />

output the information on demand.<br />

Operating Controls - The set of Microsoft Windows® and retrieval software controls that enable a<br />

standardized graphical user interface for the execution of the functionality defined within the GAMA.<br />

Optical Disc - A storage device on which data is recorded and retrieved by use of a light source, most often<br />

a laser beam. Optical disks are capable of storing digital, audio and video data (e.g., CD, CD-ROM, Video<br />

Disc).<br />

Pageless Publications - Electronic publications that utilize discreet, logical groupings (MRUs) of information<br />

to describe and work with electronic data, as opposed to an individual page.<br />

Page-Based Publications - Electronic publications that employ the use of scanned raster images of the<br />

original paper documentation.<br />

Page Block - (1) A section of text defined by the ATA Specification 100. (2) Any logical sequence of<br />

unbroken text for use in defining the minimum granularity of text in an electronic publication..<br />

Presentation - The method of display to the end user of text and graphic information contained in electronic<br />

publications.<br />

Proximity Searching - The search for one or more terms in a document, within a specified distance from<br />

another term (i.e. within the same paragraph. within the same sentence).<br />

Publication - A non-specific term for documentation. Maintenance Manuals, Illustrated Parts Catalogs, ADs<br />

and Service Information are all publication examples.<br />

Raster Images - The representation of a graphic image as a matrix of dots that are produced by scanning or<br />

computer generated at various resolutions measured in dots per inch.<br />

Resolution - The degree of sharpness of a displayed or printed character or image. On screen resolution is<br />

expressed as a matrix of dots (640 x 480 means 640 dots across each of 480 lines). For printers resolution is<br />

expressed as the number of dots per linear inch (Dots Per Inch - DPI).<br />

Revision Symbols - Revision symbols (e.g., |, R) indicate where a change has been made since the last<br />

issuance of the data.<br />

ROM - Read Only Memory. Information storage format that does not permit modification or deletion of<br />

information when in use.<br />

Replication - The process of making multiple copies, i.e. of a CD-ROM.<br />

Retrieval Software - The computer application providing the documentation, text and graphics appearance,<br />

functionality and operating controls to retrieve, display and print electronic publications as defined in the<br />

GAMA SPECIFICATION 9.<br />

Retrieval System - The computer system employed by the end user to retrieve, display and print Electronic<br />

Publications.<br />

Retrieval System Page - The page of text as defined by the storage of text in electronic publications and<br />

reproduced through the retrieval software's print function.<br />

Scanner - A device used to scan analog images, such as a document and convert its contents into digital<br />

images, such as bitmap images on a computer system. Scanners create bitmap images that are based upon<br />

a grid of pixels, and record whether each pixel is light or dark. Scanners are used in conjunction with OCR<br />

software to capture and convert images or text to an electronic bitmap format.<br />

Schema - A logical representation of data that is oriented toward a particular database management system<br />

approach (such as SQL or SFQL). Relative to SFQL and SQL, a schema is defined as a collection of tables<br />

that model related data.<br />

SCSI - Small Computer Systems Interface. A standardized method by which storage devices such as CD-<br />

ROM drives and hard disk drives interpret and communicate data. SCSI peripherals are capable of<br />

connecting multiple devices. CD-ROM drives typically utilize a SCSI interface for connection to a host<br />

system.<br />

MARCH 1999 53


GAMA <strong>ELECTRONIC</strong> <strong>PUBLICATIONS</strong> <strong>STANDARD</strong><br />

Search - Process of locating information in a database by indicating search criteria, such as words or<br />

phrases. During the search process, the retrieval software will find all matches of the criteria indicated.<br />

Search Results - The outcome of a cross-reference driven search through a document or database, a<br />

presentation of information or data related to search criteria such as a key word or phrase.<br />

Service Information - Data issued by an aircraft, engine or component manufacturer that details<br />

maintenance procedures or informs about new procedures and services. Service Information is a generic<br />

term for all of the different types of short. timely issues published by general aviation manufacturers (e.g.,<br />

Service Letters, Customer Bulletins, Service Instructions, News, etc.).<br />

SFQL - Structured Full-Text Query Language. A proposed standard for full text databases defined by the<br />

ATA in Specification 2100. The primary focus of the proposed standard is interoperability of CD-ROMs. SFQL<br />

is based on the SQL (Structured Query Language) standard for relational databases.<br />

SGML - Standard Generalized Markup Language. The ISO Standard 8879 that defines application and<br />

platform independent structuring and organization of information by tagging documents as a series of data<br />

objects defined in Document Type Definitions (DTDs). SGML separates the informational content of a<br />

document from the information needed to present it. either on paper or on screen.<br />

Status Message - An icon that indicates the retrieval software is busy or engaged in processing a command.<br />

System Response - The amount of time the retrieval software takes to display a selection list or the selected<br />

text or graphic image.<br />

Tagging - Refers to the process of adding special markup characters to ASCII data. These tags are used to<br />

indicate structural elements in the data, such as headings and subheadings, document margins, references<br />

to graphic figures, etc.<br />

Technical Maintenance Information - The maintenance information published by the manufacturers of<br />

aviation products that supports continued airworthiness (e.g., Maintenance Manuals, Illustrated Parts<br />

Catalogs, Structural Repair Manuals, Component Maintenance Manuals, Wiring Manuals, etc.)<br />

Text - In electronic publications, the ASCII characters as distinguished from graphic images.<br />

TIFF - Tagged Image File Format. An industry-wide standard graphics file format developed by Aldus, for<br />

storing and exchanging raster image data. TIFF is used to define the specific data structures of images to be<br />

processed.<br />

Title Strip - An area of the display reserved for the identification of the text or graphic image being displayed.<br />

Vector Graphics - Images based upon lines drawn between specific coordinates as defined by the<br />

mathematical relationship between each line's beginning point, length and direction.<br />

Windows® - Microsoft's Graphical User Interface software that accommodates the use of multiple<br />

applications simultaneously by separating applications into different "windows" displayed on the computer<br />

display screen. Windows runs on PCs in a DOS environment and has functionality similar to the graphical<br />

environment employed by Apple® / Macintosh® systems.<br />

Word Search - A search method used to locate every occurrence of a word, combination of words (or<br />

alphanumeric strings), phrase or number in a database or document.<br />

54 MARCH 1999

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!