ANSI/NIST-ITL 2-2008 - National Institute of Standards and ...

Part 2 ANSI/NIST-ITL 2-2008
transaction interchanges between non-English-speaking or based agencies, a technique is
available to encode information using character sets other than 7-bit ASCII. Fields/elements in
theType-1 logical record and ASCII “LEN” (in Part 1 only) and “IDC” text fields/elements must still
be encoded using 7-bit ASCII. But all other designated text fields/elements can be encoded
using alternate character sets. The general mechanism for accomplishing this provides for
backward compatibility with existing readers, supports multiple character sets in a single text
string, and handles internationally accepted character sets and text order conventions such as
ISO character sets, UTF-8, and Unicode.
Character sets within a transaction may only be switched in user-defined data. Appropriate
mechanisms must be defined as part of the user-defined data definition.
The base-64 encoding scheme, found in email, shall be used for converting non-ASCII text into
ASCII form. Annex C describes the use of the base-64 system. It is expected that this encoding
scheme will be used to convert all (originally) binary image data to ASCII for transmission, and
will also be used to convert non-ASCII data into ASCII data in user-defined data.
All XML element tags including the “” characters shall appear in the transaction as 7-bit
ASCII characters.
209 Type-1 transaction information record
209.1 XML elements for the Type-1 transaction information record
The following paragraphs describe the data contained in each XML element of the transaction
information record. Table 207 provides a list of the elements for the transaction information
record. It is required that all elements of the record are ordered in the sequence described. For
each of the elements, Table 207 lists for cross-reference purposes the Part 1 mnemonic and field
number, the “condition code” as being mandatory “M” or optional “O”, the Part 2 XML element
name, and occurrence limits. An entry containing an "*" indicates that there is no established
limit. Annex F contains an example of the use of the standard that illustrates the layout for a
Type-1 logical record. (Table 207 corresponds to Table 8 in Part 1.)
The Type-1 record shall be contained within this complex element:
[. . . Type 01 Record Content . . .]
209.1.1 Record length
Cross-reference: Part 1, Section 9.1.1 Field 1.001: Logical record length (LEN)
There is no corresponding Part 2 XML element.
209.1.2 Element
This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the
record type. For the Type-1 record, it shall contain a value of 01.
01
25