Transfer unit declaration file provides all information necessary to uniquely identify the unit and contains the count of each transfer unit data file type contained in the transfer unit. The file name used for each transfer unit declaration file shall be four characters long; the first shall be “D”; the last three characters shall begin at “001” and shall be incremented for each transfer unit. The last available transfer unit file name shall be “DZZZ”.
The transfer unit declaration file shall be written in fixed length records of 128 bytes each. Each record has a dedicated use, and each record is required. All the data shall be ASCII character format. When no data is placed and a record exists, the ASCII character string “EMPTY” shall be used. When the data required by a record is not applicable to the transfer unit, the ASCII character string “NA” shall be used. When data to be placed in a record does not exist, the ASCII character string “NONE” shall be used.
Table I. Transfer unit declaration file record.
Table II. Change level (chglvl:) header record entries.
CHG TYPE |
MEANING |
REV LEVEL |
CHG LEVEL |
The document or product is the original. |
0 |
0 |
|
The document or product data is the original with changes incorporated. |
0 |
Highest level changes included |
|
The document or product data is a complete revision to a document or product data. |
Indicates current revision level |
0 |
|
The document or product data is a complete revision of a document or product data with changes incorporated. |
Indicates current revision level |
Highest level changes included |
|
The document or product data is change material to an original, revision, or supplement. |
Indicates current revision level |
0 |
|
OTHER
|
Used when none of above change types apply. |
0 |
0 |
Transfer unit data files may be of the types shown in the table III. The file name for transfer unit data files shall be eight characters long, with the first four characters being the same as the transfer unit declaration file name. The fifth character shall be a code from Table III, identifying the type of data file. The last three characters shall begin at “001” and shall be incremented for each transfer unit data file.
Table III :Data file name code letters and file format.
Code letter |
Data file type |
Fixed record length |
Block length |
A |
As specified by contract |
As specified by contract |
|
C |
80 |
800 |
|
E |
As specified by contract |
As specified by contract |
|
G |
Document type declaration file with no contained text data |
256 |
2048 |
H |
256 |
2048 |
|
I |
As specified by contract |
As specified by contract |
|
N |
IPC file |
As specified by contract |
As specified by contract |
P |
As specified by contract |
As specified by contract |
|
Q |
80 |
800 |
|
R |
128 |
2048 |
|
T |
As specified by contract |
As specified by contract |
|
V |
80 |
1920 |
|
X |
As specified by contract |
As specified by contract |
|
Z |
As specified by contract |
As specified by contract |
Table IV.: Transfer set data file header records
RECORD ID |
RECORD NAME |
DESCRIPTION |
A character string identifying the document number, revision level, and date of the specification data file it’s in accordance with. The date format shall be YYYYMMDD |
||
A character string used by the system to uniquely identify the document to which this file belongs. |
||
This character string is the same as the dstdocid identifier of the transfer unit declaration file. The parenthetical words “(Multiple Document)” should be appended to the identifier if the entry is intended for use in more than one transfer unit. |
||
This record shall contain the contract-specified description, identifying the contents and processing this file. |
||
Used for SGML document file. |
||
In this record is an ASCII character string containing an integer that indicates the type of data contained in the file. For raster file, this value can be 1 (Type 1 Raster) or 2 (Type 2 Raster). |
||
Two right-justified, three character strings separated by a comma specifying respectively the direction of the progression of successive pels along a line relative to the horizontal and the direction of the progression of successive lines relative to the pel path. If more than one value is applicable to the data file, the ASCII character string “MIXED” shall be used. |
||
Two right-justified, six character strings separated by a comma specifying the image count of pels in the pel path direction, and lines in the line progression direction. If more than one value is applicable to the data file, the ASCII character string “MIXED” shall be used. |
||
One right justified, four-character string representing the numerical value of the raster image density. If more than one value is applicable to the data file, the ASCII character string “MIXED” shall be used. |
||
This record shall contain the applicable Data Item Description identification number. |
||
Character string stating the security/sensitivity level or other restrictions on the data file. |
||
For the document type declaration or text source file containing the document type declaration of the document being transferred. |
||
Notes |
Notes shall consist of free form text consistent with the number of characters permitted for records in this file. |