RFC 1895 (rfc1895) - Page 2 of 6
The Application/CALS-1840 Content-type
Alternative Format: Original Text Document
RFC 1895 CALS-1840 February 1996
records immediately followed by the data. The data itself may be
formatted in accordance with a published specification or a
contractual agreement.
MIL-STD-1840 encodes the file's data type in the file name.
It might seem appropriate to transform the 1840 headers into MIME
headers and use the appropriate media type, essentially transforming
the 1840 files into MIME body parts. There are three reasons for not
doing that. First, not all of the "types" used in [1840] are
registered MIME types. Second, there exists an installed base of
software capable of reading the 1840 formatted files and processing
the data appropriately. Finally the three existing revisions to the
standard have maintained the same file structure. Consequently, a
processor for the data may be able to handle any one of the
standard's revisions. Thus, a single Application/CALS-1840 is being
proposed and its body part body contains headers and data in the
[1840] format.
A set of related files constitutes a "transfer unit" in 1840 and each
transfer unit shall correspond to a Multipart/Mixed MIME entity.
Included in each transfer unit is a declaration file which shall be
the first body part in the Multipart/Mixed entity. Several transfer
units may be included in a single MIME message.
Levinson Informational