12.07.2015 Views

ANSI/NIST-ITL 1-2011 - NIST Visual Image Processing Group ...

ANSI/NIST-ITL 1-2011 - NIST Visual Image Processing Group ...

ANSI/NIST-ITL 1-2011 - NIST Visual Image Processing Group ...

SHOW MORE
SHOW LESS
  • No tags were found...

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

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

<strong>ANSI</strong>/<strong>NIST</strong>-<strong>ITL</strong> 1-<strong>2011</strong>Data Format for the Interchange of Biometric and Forensic Information<strong>ANSI</strong> X3.4-1986. The text or character data in Type-2, Type-9, and records arenormally recorded using the 7-bit ASCII code in variable-length fields withspecified upper limits on the size of the fields. For data interchange betweennon-English speaking agencies, character sets other than 7-bit ASCII may beused in metadata. UTF-8 is the preferred method of storing textual data thatcannot be represented as 7-bit ASCII. This method supports internationalcharacter sets for all user-defined fields in all record types. By definition UTF-8and other international character exchange methods are not applicable to RecordType-1 in all encodings.7 Record type descriptions 97.1 Type-1 Transaction information recordTransmissions to be exchanged are required to contain one and only one Type-1record per transaction. A Type-1 record is mandatory and is required for eachtransaction. The Type-1 record shall always be the first record within thetransaction. Depending on the usage and the number of fingerprint, palmprint,facial, SMT, DNA, plantar, iris, or other biometric information records available forprocessing, one or more additional records shall be present in the file. The Type-1 record shall provide information describing type and use or purpose for thetransaction involved, a listing of each record included in the transaction, theoriginator or source of the physical record, and other useful and requiredinformation items. There is only one Type-1 record in each transaction.7.1.1 Implementation Domain (DOM)Brad Wing 6/19/10 5:07 PMComment: ClarificationAn implementation domain 10 , codified as Domain Name (DOM) in a Type-1record, is a group of agencies or organizations that have agreed to use preassigneddata fields with specific meanings (typically in Record Type-2) forexchanging information unique to their installations.An example of an implementation domain is the one maintained by the CriminalJustice Information Services (CJIS) Division of the Federal Bureau ofInvestigation (FBI). It is the North American Domain subscribed to by the RoyalCanadian Mounted Police (RCMP), the FBI, and several state and Federalagencies in North America.Brad Wing 6/19/10 5:07 PMComment: Revised wording•9 Throughout this standard the terminology Record Type or record is used. It does not imply a separate file.•10 The “implementation domain” is not to be confused with the “Biometrics domain.” The Biometrics domain is anamespace used in NIEM-conformant implementations of this standard.14DRAFT 2

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

Saved successfully!

Ooh no, something went wrong!