acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ... acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

biometrics.nist.gov
from biometrics.nist.gov More from this publisher
11.07.2015 Views

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION“2.000000123:”.For purposes of illustration throughout this annex, a three-digit number shall be used forenumerating the fields contained in each of the Record Types, other than 4, 7 and 8. Fieldnumbers will have the form of “TT.xxx:” where the “TT” represents the one- or twocharacterrecord type followed by a period. The next three characters comprise theappropriate field number followed by a colon. Descriptive ASCII information or the sampledata follows the colon.Logical Type-1, Type-2, and Type-9 records contain only ASCII textual data fields (SeeAnnex A: Character encoding information). The entire length of the record (includingfield numbers, colons, and information separators) shall be recorded as the first ASCII fieldwithin each of these record types. The ASCII File Separator “ F S” control character (signifyingthe end of the logical record or transaction) shall follow the last byte of ASCII informationand shall be included in the length of the record.The Record Type-4: Grayscale fingerprint image, the Record Type-7: User-definedimage record and the Record Type-8: Signature image record contain only binary datarecorded as ordered fixed-length binary fields. The entire length of the record shall berecorded in the first four-byte binary field of each record. For these binary records, neitherthe record number with its period, nor the field identifier number and its following colon,shall be recorded. Furthermore, as all the field lengths of these three records are either fixedand specified, none of the four separator characters (“ U S”, “ R S”, ” G S”, or “ F S”) shall beinterpreted as anything other than binary data. For these binary records, the “ F S” charactershall not be used as a record separator or transaction terminating character.Each ASCII field contains a numeric field identifier and its descriptive data.When Field 999 is present in a record, it shall appear as the last entry in the record and shallcontain the data placed immediately following the colon (“:”) of the field identifier. Therecord length field shall contain the length of the record. The ASCII File Separator “ F S”control character shall follow the last byte of the compressed or uncompressed sample data.The “ F S” character shall signify the end of the logical record or transaction and shall beincluded as part of the record length.The Base-64 encoding scheme (See Annex A: Character encoding information) shall beused for converting non-ASCII text into ASCII form. The field number including the periodand colon, for example “2.001:”, in addition to the “ U S”, “ R S”, “ G S”, and “ F S” informationseparators shall appear in the transaction as 7-bit ASCII characters without conversion toBase-64 encoding.B.1.6Switching between character encoding setsAll of the fields in the Type-1 record shall be recorded using the 7-bit ASCII code, which isthe default character encoding set code within a transaction. In order to effect data andtransaction interchanges between non-English speaking or foreign-based agencies, atechnique is available to encode information using character encoding sets other than 7-bitMay, 2013 DRAFT VERSION UPDATE 2013 Page 449

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONASCII. Fields from the Type-1 logical record and ASCII Field xx.001 and Field xx.002 textfields shall still be encoded using 7-bit ASCII, but all other designated text fields may beencoded using an alternate character encoding set, if they are shown with the character typeof 'U' or 'user-defined' in the record layout tables at the beginning of each Record TypeSection of this standard. One alternate character encoding set may be chosen per transaction.To switch character encoding sets within a transaction, the Type-1 record shall contain Field1.015 Character encoding / DCS. The DCS consists of 3 information items containing anidentifying code, the name of an international character encoding set, and its version.Retained for backward compatibility is a mechanism using codes to signal the conversion toa different international character encoding set. This mechanism is not recommended for newapplications. However, these codes must be used for UTF-16 or UTF-32 data, since onlyUTF-8 is allowed to be used without the codes. Use of the code requires the ASCII Start-of-Text “ STX ” character (0x02) followed by the equal sign “=” to signal the change to analternate character encoding set defined by the specific DCS code that follows. The entireStart-of-Text sequence is terminated by a single instance of the ASCII End-of-Text “ ETX ”character (0x03). This alternate character encoding set will remain active until a closing“ ETX ” character is encountered or the next ASCII information separator character isencountered. All text between the STX sequence and the closing ETX character shall beencoded in Base-64 notation (See Annex A: Character encoding information). This is trueeven when the 7-bit ASCII character encoding set is specified.Usage of UTF-8 is allowed as an alternative to the technique that requires the usage of theASCII “ STX ” and “ ETX ” characters to signify the beginning or end of international characters.UTF-8 is only allowed in fields marked 'U' or 'user-defined' in the character type column ofthe record layout tables. Notice that this technique does not require the conversion of text toBase-64 as does the technique employing “ STX ” and “ ETX ”.B.2 Encoding for specific record typesThe following sections provide specific detail for for certain fields within the record types toensure clarity to programmers.B.2.1Type-1 recordField 1.001 Record header shall begin with “1.001:” followed by the length of the recordincluding every character of every field contained in the record and the informationseparators. The “ G S” separator character shall separate the length code of Field 1.001 fromthe next field.The year, month, and day values in Field 1.005 Date / DAT are concatenated“YYYYMMDD”.In Field 1.013 Domain name / DOM, the default is “1.013:NORAM U S G S”Immediately following the last information item in the Type-1 record (See Section 8.1), an450

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION“2.000000123:”.For purposes of illustration throughout this annex, a three-digit number shall be used <strong>for</strong>enumerating the fields contained in each of the Record Types, other than 4, 7 and 8. Fieldnumbers will have the <strong>for</strong>m of “TT.xxx:” where the “TT” represents the one- or twocharacterrecord type followed by a period. The next three characters comprise theappropriate field number followed by a colon. Descriptive ASCII in<strong>for</strong>mation or the sampledata follows the colon.Logical Type-1, Type-2, and Type-9 records contain only ASCII textual data fields (SeeAnnex A: Character encoding in<strong>for</strong>mation). The entire length of the record (includingfield numbers, colons, and in<strong>for</strong>mation separators) shall be recorded as the first ASCII fieldwithin each of these record types. The ASCII File Separator “ F S” control character (signifyingthe end of the logical record or transaction) shall follow the last byte of ASCII in<strong>for</strong>mationand shall be included in the length of the record.The Record Type-4: Grayscale fingerprint image, the Record Type-7: User-definedimage record and the Record Type-8: Signature image record contain only binary datarecorded as ordered fixed-length binary fields. The entire length of the record shall berecorded in the first four-byte binary field of each record. For these binary records, neitherthe record number with its period, nor the field identifier number and its following colon,shall be recorded. Furthermore, as all the field lengths of these three records are either fixedand specified, none of the four separator characters (“ U S”, “ R S”, ” G S”, or “ F S”) shall beinterpreted as anything other than binary data. For these binary records, the “ F S” charactershall not be used as a record separator or transaction terminating character.Each ASCII field contains a numeric field identifier and its descriptive data.When Field 999 is present in a record, it shall appear as the last entry in the record and shallcontain the data placed immediately following the colon (“:”) of the field identifier. Therecord length field shall contain the length of the record. The ASCII File Separator “ F S”control character shall follow the last byte of the compressed or uncompressed sample data.The “ F S” character shall signify the end of the logical record or transaction and shall beincluded as part of the record length.The Base-64 encoding scheme (See Annex A: Character encoding in<strong>for</strong>mation) shall beused <strong>for</strong> converting non-ASCII text into ASCII <strong>for</strong>m. The field number including the periodand colon, <strong>for</strong> example “2.001:”, in addition to the “ U S”, “ R S”, “ G S”, and “ F S” in<strong>for</strong>mationseparators shall appear in the transaction as 7-bit ASCII characters without conversion toBase-64 encoding.B.1.6Switching between character encoding setsAll of the fields in the Type-1 record shall be recorded using the 7-bit ASCII code, which isthe default character encoding set code within a transaction. In order to effect data andtransaction interchanges between non-English speaking or <strong>for</strong>eign-based agencies, atechnique is available to encode in<strong>for</strong>mation using character encoding sets other than 7-bitMay, 2013 DRAFT VERSION UPDATE 2013 Page 449

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!