acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
Share Embed Flag
Download ePaper

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, and its elementshall have a value of “98”.C.10.21Type-99 CBEFF biometric data recordThe XML name for the Type-99 record (Section 8.24) is, and its elementshall have a value of “99”. Implementers should note that the value of the element differs in the Type-99 record from its occurrence in otherrecords. CBEFF requires both date and time. The date and time shall appear as twentycharacters in the format YYYY-MM-DDThh:mm:ssZ. The YYYY characters shall representthe year; the MM characters shall be the tens and units values of the month; and the DDcharacters shall be the tens and units values of the day of the month; the character T separatesthe date from the time; the hh characters represent the hour; the mm the minute; the ssrepresents the second; and Z denotes Coordinated Universal Time.Complex element shall have the simple element ,which shall contain transaction date and time data.2008-02-29T05:25:00ZC.11 Information exchange package documentation (IEPD) artifactsThe latest version of all documents is to be referenced.The following artifacts are available athttp://www.nist.gov/itl/iad/ig/ansi_standard.cfm :• Metadata• Catalog• Exchange Schema• NIEM subset schema• Instance document(s)• Change log describing differences between ANSI/NIST-ITL 2-2008 to ANSI/NIST-ITL 2011• XSLT transformation to/from ANSI/NIST-ITL 2-2008May, 2013 DRAFT VERSION UPDATE 2013 Page 469

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONAnnex D: NCIC code tableNormativeIn the 2007 and 2008 versions of the standard, the NCIC code table was present in the text ofthe standard as an annex. The NCIC table codes have been updated since the publication ofthose versions of this standard. In order to ensure consistency with the current version ofthese codes, this version of the standard includes the latest version of the NCIC code table asa normative reference. It is available at http://www.oregon.gov/OSP/CJIS/NCIC.shtml .Note that any codes that were listed in the 2007 and 2008 versions of this standard that arenot included in the list at the above website are still valid, in order to maintain backwardcompatibility. An example is CRIP FOOT. The current version of the NCIC code table hasCRIP L FT and CRIP R FT.Annex E: Facial Capture – SAPs 30 and aboveNormativeE.1 IntroductionThis annex is based upon work originating at a Mugshot and Facial Image Workshop held atNIST in 1995. The original recommendation document was incorporated as Annex H in the2007 / 2008 version of the ANSI/NIST-ITL standard, supplemented by Annex I, which extendedthe recommendations further, as well as Annex J, which dealt with Face-Pose values. Thisannex combines the three annexes of the 2007 / 2008 standard and includes new information,which in no manner contradicts earlier guidance.The annex is not designed to render current and legacy mugshot collections unacceptable.Rather, it is intended as a means of establishing or improving interoperability between mugshotsystems. The provisions of this annex are keyed to the quality aspects associated with theunaltered captured mugshot image. For new mugshot images being captured, the specificationscontained in this annex are equally applicable to real-time electronic capture of mugshots aswell as the electronic conversion of photographic images. For conversion oflegacy files ofphotographs, the provisions of this annex are applicable.This annex consists of a set of Sections describing the capture of facial images at SAP levels 30and above. See Section 7.7.5.1 Subject acquisition profile for face / SAP. These Sectionscan be categorized into six types of requirements: digital, photographic, subject and scene,number of photographs, data handling, and format (for SAP levels 40 and above).470

ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION, and its elementshall have a value of “98”.C.10.21Type-99 CBEFF biometric data recordThe XML name <strong>for</strong> the Type-99 record (Section 8.24) is, and its elementshall have a value of “99”. Implementers should note that the value of the element differs in the Type-99 record from its occurrence in otherrecords. CBEFF requires both date and time. The date and time shall appear as twentycharacters in the <strong>for</strong>mat YYYY-MM-DDThh:mm:ssZ. The YYYY characters shall representthe year; the MM characters shall be the tens and units values of the month; and the DDcharacters shall be the tens and units values of the day of the month; the character T separatesthe date from the time; the hh characters represent the hour; the mm the minute; the ssrepresents the second; and Z denotes Coordinated Universal Time.Complex element shall have the simple element ,which shall contain transaction date and time data.2008-02-29T05:25:00ZC.11 In<strong>for</strong>mation exchange package documentation (IEPD) artifactsThe latest version of all documents is to be referenced.The following artifacts are available athttp://www.<strong>nist</strong>.gov/<strong>itl</strong>/iad/ig/<strong>ansi</strong>_standard.cfm :• Metadata• Catalog• Exchange Schema• NIEM subset schema• Instance document(s)• Change log describing differences between ANSI/<strong>NIST</strong>-ITL 2-2008 to ANSI/<strong>NIST</strong>-ITL <strong>2011</strong>• XSLT trans<strong>for</strong>mation to/from ANSI/<strong>NIST</strong>-ITL 2-2008May, 2013 DRAFT VERSION UPDATE 2013 Page 469

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!