ELECTRONIC PUBLICATIONS STANDARD
ELECTRONIC PUBLICATIONS STANDARD
ELECTRONIC PUBLICATIONS STANDARD
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
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