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 VERSION8.15.27 Field 15.995: Associated context / ASCThis optional field refers to one or more Record(s) Type-21 with the same ACN. SeeSection 7.3.3. Record Type-21 contains images that are NOT used to derive the biometricdata in Field 15.999: Palmprint image / DATA but that may be relevant to thecollection of that data.8.15.28 Field 15.996: Hash/ HASThis optional field shall contain the hash value of the data in Field 15.999: Palmprintimage / DATA of this record, calculated using SHA-256. See Section 7.5.2.8.15.29 Field 15.997: Source representation / SORThis optional field refers to a representation in Record Type-20 with the same SRN. SeeSection 7.3.2.8.15.30 Field 15.998: Geographic sample acquisition location / GEOThis optional field contains the location where the palm sample was acquired – not whereit is stored. See Section 7.7.3.8.15.31 Field 15.999: Palmprint image / DATAThis field contains the palmprint image. See Section 7.2 <strong>for</strong> details. It shall contain animage, unless Field 15.018: Amputated or bandaged / AMP has a value of “UP”. Inthe latter case, the field is optional. Some domains and application profiles may stillrequire an image in this field (such as of the word “Amputated”). Note that in previousversions of the standard that this field was mandatory in all circumstances.8.16 Record Type-16: User-defined testing image recordThe Type-16 record shall contain and be used to exchange image data together with textualin<strong>for</strong>mation fields pertinent to the digitized image. This record type allows the exchangeimages not addressed by other record types in the standard. It is intended as the user-definedrecord to be used <strong>for</strong> developmental or test purposes. The image data contained in the Type-16 record may be in a compressed <strong>for</strong>m. With the exception of the fields described below,the <strong>for</strong>mat, parameters, and types of images to be exchanged are undefined by this standardand shall be agreed upon between the sender and recipient.Table 87 Type-16 record layout336

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

Saved successfully!

Ooh no, something went wrong!