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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSIONType-99 records shall contain and be used to exchange biometric data that is not supportedby other ANSI/<strong>NIST</strong>-ITL record types. This provides a basic level of interoperability andharmonization with other biometric interchange <strong>for</strong>mats. This is accomplished by using abasic record structure that is con<strong>for</strong>mant with ANSI INCITS 398-2005, the CommonBiometric Exchange Formats Framework (CBEFF) and a biometric data block specificationregistered with the International Biometrics Industry Association (IBIA) 14 .5.4 Backward compatibilityBackward compatibility is important, since organizations adhering to earlier versions of thestandard may create transactions according to that version, and these transactions may stillbe received by organizations that have updated to a newer version of the standard.The fields and <strong>for</strong>mat of Type-4 (fingerprint images) and Type-8 (signature) records cannotchange between versions of the standard due to restrictions in the Traditional encoding<strong>for</strong>mat. (In Traditional encoding, they are ‘binary’ data with a fixed structure.) Since thetime when these record types were defined, users have needed more flexibility in definingthe metadata associated with the fingerprint image data. Thus, Type-14 was developed toreplace Type-4 fingerprint image records. However, since several systems exist that useType-4 to transmit fingerprint images, that record type is retained in the standard. Type-2(user-defined descriptive text entries), Type-7 (user-defined image) and Type-16 (userdefinedtesting image) records are further defined in application profile-specificdocumentation (See Section 6 Implementation domain and application profiles ).Record Types 9 through 99 may be updated, expanded or introduced with new versions ofthe standard. New fields in existing records may be added, as well as new data record types.If it is determined by the canvassees that a record type, field, subfield, in<strong>for</strong>mation item orvalue is not used or needed, it may be declared ‘deprecated.’ In this version of the standard,the deprecated record type, field, or in<strong>for</strong>mation item is not included in the description.Deprecated records <strong>for</strong> this version are Record Types 3, 5 and 6. Field 17.018 isdeprecated. There are two deprecated values in Field 17.016: <strong>Image</strong> property code / IPC(2: <strong>for</strong> interlace frame, and 3: <strong>for</strong> interlace field).There are also certain items that are noted in the standard as being discouraged <strong>for</strong> use innew applications, but that have not yet been agreed upon by the canvassees to be deprecated.There is a special category called 'legacy' <strong>for</strong> a record type, field, subfield, in<strong>for</strong>mationitem or value that was valid in previous versions of the standard, but shall not be used <strong>for</strong>new data. 'Legacy' indicates that if there is existing data using this record type, field,in<strong>for</strong>mation item or value it may still be transmitted in a transaction con<strong>for</strong>mant to thisversion of the standard. In this version 'legacy' applies to Fields 9.005 through 9.012, Field10.022 and to the value '1' in Table 4 Character encoding.14For more in<strong>for</strong>mation, go to http://www.ibia.org .May, 2013 DRAFT VERSION UPDATE 2013 Page 41

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

Saved successfully!

Ooh no, something went wrong!