11.07.2015 Views

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 ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONRecord Identifier Logical record contents Type of data23-97 Reserved <strong>for</strong> future use ASCII/Binary98 In<strong>for</strong>mation assurance ASCII/Binary99 CBEFF biometric data record ASCII/BinaryThe first field in all records shall contain the length in bytes of the record. For all ASCII orASCII/Binary records the first field shall also be labelled as field “1:”. The length has noupper bound. The mnemonic associated with each of these fields (xx.001) is LEN. It is anumeric (positive integer) value. The mnemonic LEN is used in Field 98.900: Audit log /ALF <strong>for</strong> the in<strong>for</strong>mation item in<strong>for</strong>mation identifier / IID in order to record changes to thevalue in this field.With the exception of the Type-1 record (See Section 8.1), the second field shall be labeledas field “2” and contain the in<strong>for</strong>mation designation character / IDC. See Section 7.3.1.The data in the Type-1 record shall always be recorded in variable length fields using the 7-bit American Standard Code <strong>for</strong> In<strong>for</strong>mation Interchange (ASCII) as described in ISO/IEC646 189 . For purposes of compatibility, the eighth (leftmost) bit shall contain a value of zero.All field numbers and in<strong>for</strong>mation separators shall be recorded in 7-bit ASCII as described inISO/IEC 646.Textual fields in Record Types 2 and 9-99 may occur in any order after the first two fieldsand contain the in<strong>for</strong>mation as described <strong>for</strong> that particular numbered field, except <strong>for</strong> field999, which shall be the concluding field, when it is included in a record. The allowedcharacter encoding sets are included in Table 4.In the Type-1, Type-2, Type-9 through Type-99 records, in<strong>for</strong>mation is delimited by the fourASCII in<strong>for</strong>mation separators. The delimited in<strong>for</strong>mation may be items within a field orsubfield, fields within a logical record, or multiple occurrences of subfields. Thesein<strong>for</strong>mation separators are defined in the referenced standard ISO/IEC 646 with the codetable shown in Table 108 . See also Annex A: Character encoding in<strong>for</strong>mation.These characters are used to separate and qualify in<strong>for</strong>mation in a logical sense. Viewed in ahierarchical relationship, the File Separator “ F S” character is the most inclusive followed bythe Group Separator “ G S”, the Record Separator “ R S”, and finally the Unit Separator “ U S”characters. The four characters are only meaningful when used as separators of data items inthe ASCII fields of records. There is no specific meaning attached to these charactersoccurring in binary sample records and binary fields – they are just part of the exchangeddata. In<strong>for</strong>mation separators should be functionally viewed as an indication of the type datathat follows.Multiple records within a transaction are separated by the “ F S” character, which signals theend of a logical record. Use of separators within the Type-1, Type-2, Type-9 through Type-189See Section 3 Normative references.May, 2013 DRAFT VERSION UPDATE 2013 Page 445

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

Saved successfully!

Ooh no, something went wrong!