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 VERSION8.9 Record Type-9: Minutiae data recordType-9 records shall contain text describing minutiae and related information encoded froma finger, palm, or plantar image. There is no limit on the number of Type-9 records for alatent search transaction. The Type-9 record shall also be used to exchange minutiae andrelated information from latent friction ridge images between similar or different systems.Note that Fields 9.005 through 9.012 in this version of the standard shall not appear for allnew applications and are 'legacy fields'. For users encountering these fields in legacysystems, please refer to ANSI/NIST-ITL 1-2007 or ANSI/NIST-ITL 2-2008 for a descriptionof those fields. Old (legacy) data containing these fields may still be transmitted in atransaction conformant to the this version .Reserved blocks, each consisting of several fields, are registered and allocated for use byspecific vendors. As these blocks may contain proprietary information, no detailedinformation is provided regarding the content of these vendor-defined feature sets asidefrom the range of field numbers in this standard. For detailed information on each of thesefields, the vendor should be contacted. These alternative blocks of reserved fields allowvendors to encode minutiae data and any additional required characteristic or feature data inaccordance with their own system’s specific hardware and software configuration. Table 27identifies the vendor implementations and their assigned blocks of field numbers. For thosevendors not identified in the table, Fields 9.176 through 9.225 may be used to record theirproprietary features 56 . Any vendor may use these fields to record information. The name ofthe vendor or developer of the proprietary feature data, the name and version of thealgorithm used, the target device for which the data is generated, and the contactinformation, together with the feature data shall be recorded within this block of fields.Record Fields 9.126 through 9.150 correspond to the conventions defined and describedoriginally by the ANSI INCITS 378 standard. Record Fields 9.300 through 9.399 are theExtended Feature Set.In the 2008 version of the standard, only one vendor block (including the M1 format) couldbe present in a single record. The 2007 version allowed multiple blocks to be present. The2011 version is consistent with the 2007 version for all encodings -- allowing multipleblocks (including the INCITS 378 block and the EFS block) to be present.Although this record type may also be used to accommodate a variety of methods used bydifferent AFIS vendors for encoding minutiae data according to their particularrequirements, each vendor implementation shall contain the first four fields described below.Fields corresponding to the INCITS-378 features, the Extended Feature Set and theUniversal Latent annotation 56 may be used with or without the fields associated withregistered implementations.56New for the 2011 version of the standard.May, 2013 DRAFT VERSION UPDATE 2013 Page 115

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONTable 27 Type-9 record layoutFieldNumberMnemonicContentDescriptionCondcodeCharacterTypeMIn#Max#ValueConstraintsOccurrenceMIn#Max#9.001 RECORD HEADER Mencoding specific:see Annex B:Traditionalencoding orAnnexC: NIEMconformantencoding rulesencoding specific:see Annex B:Traditionalencoding orAnnexC: NIEMconformantencoding rules1 19.002 IDCINFORMATIONDESIGNATIONCHARACTERM N 1 20 < IDC < 99integer1 19.003 IMP IMPRESSION TYPE M N 1 2 Value from Table 7 1 1FMT = U9.004 FMT MINUTIA FORMAT M A 1 1FMT = S only ifincluding legacy fields9.005-9.012 from oldrecord sources1 19.005-9.012Legacy Fields; See ANSI/NIST-ITL 1-2007 or ANSI/NIST-ITL 2-2008 for a description of thesefieldsOnly to be used for interchange of legacy data.9.013-9.030 FBI IAFIS FEATURE SET O user-defined user-defined user-defined9.031-9.055 COGENT FEATURE SET O user-defined user-defined user-defined9.056-9.070 MOTOROLA FEATURE SET O user-defined user-defined user-defined9.071-9.099MORPHOTRAK FEATURESETO user-defined user-defined user-defined9.100-9.125 NEC FEATURE SET O user-defined user-defined user-defined9.126-9.150 INCITS 378 FIELDS O See Table 289.151-9.175L1 / IDENTIX FEATURESET 57 O user-defined user-defined user-defined9.176-9.225OTHER FEATURE SETS -DEFINED FIELDSO See Table 299.226-9.299RESERVED FOR FUTUREUSE only by ANSI/NIST-ITLNot to be used9.300-9.399 EXTENDED FEATURE SET O See Table 3057[2013a>] In 2013 this was MorphoTrust USA. [

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.9 Record Type-9: Minutiae data recordType-9 records shall contain text describing minutiae and related in<strong>for</strong>mation encoded froma finger, palm, or plantar image. There is no limit on the number of Type-9 records <strong>for</strong> alatent search transaction. The Type-9 record shall also be used to exchange minutiae andrelated in<strong>for</strong>mation from latent friction ridge images between similar or different systems.Note that Fields 9.005 through 9.012 in this version of the standard shall not appear <strong>for</strong> allnew applications and are 'legacy fields'. For users encountering these fields in legacysystems, please refer to ANSI/<strong>NIST</strong>-ITL 1-2007 or ANSI/<strong>NIST</strong>-ITL 2-2008 <strong>for</strong> a descriptionof those fields. Old (legacy) data containing these fields may still be transmitted in atransaction con<strong>for</strong>mant to the this version .Reserved blocks, each consisting of several fields, are registered and allocated <strong>for</strong> use byspecific vendors. As these blocks may contain proprietary in<strong>for</strong>mation, no detailedin<strong>for</strong>mation is provided regarding the content of these vendor-defined feature sets asidefrom the range of field numbers in this standard. For detailed in<strong>for</strong>mation on each of thesefields, the vendor should be contacted. These alternative blocks of reserved fields allowvendors to encode minutiae data and any additional required characteristic or feature data inaccordance with their own system’s specific hardware and software configuration. Table 27identifies the vendor implementations and their assigned blocks of field numbers. For thosevendors not identified in the table, Fields 9.176 through 9.225 may be used to record theirproprietary features 56 . Any vendor may use these fields to record in<strong>for</strong>mation. The name ofthe vendor or developer of the proprietary feature data, the name and version of thealgorithm used, the target device <strong>for</strong> which the data is generated, and the contactin<strong>for</strong>mation, together with the feature data shall be recorded within this block of fields.Record Fields 9.126 through 9.150 correspond to the conventions defined and describedoriginally by the ANSI INCITS 378 standard. Record Fields 9.300 through 9.399 are theExtended Feature Set.In the 2008 version of the standard, only one vendor block (including the M1 <strong>for</strong>mat) couldbe present in a single record. The 2007 version allowed multiple blocks to be present. The<strong>2011</strong> version is consistent with the 2007 version <strong>for</strong> all encodings -- allowing multipleblocks (including the INCITS 378 block and the EFS block) to be present.Although this record type may also be used to accommodate a variety of methods used bydifferent AFIS vendors <strong>for</strong> encoding minutiae data according to their particularrequirements, each vendor implementation shall contain the first four fields described below.Fields corresponding to the INCITS-378 features, the Extended Feature Set and theUniversal Latent annotation 56 may be used with or without the fields associated withregistered implementations.56New <strong>for</strong> the <strong>2011</strong> version of the standard.May, 2013 DRAFT VERSION UPDATE 2013 Page 115

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

Saved successfully!

Ooh no, something went wrong!