1 American National Standard 

2 for Information Systems — 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

3 

4 Data Format for the Interchange of Fingerprint, 

5 Facial, & Other Biometric Information – Part 2: 

6 XML Version 

7 

8 03/05/2008 Draft for Comment 

9 

10 

11 

12 Please send comments in the comment form for this draft to 

13 ansi-nist-xml@nist.gov no later than April 7, 2008. 

14 Download a copy of the comment form from 

15 <http://fingerprint.nist.gov/standard/>. 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Contents 

Foreword ................................................................................................................viii 

201 Introduction............................................................................................................................... 1 

202 Scope, purpose, and conformance .......................................................................................... 1 

202.1 Scope ............................................................................................................................. 1 

202.2 Purpose.......................................................................................................................... 2 

202.3 Conformance.................................................................................................................. 2 

203 Normative References.............................................................................................................. 3 

204 Definitions................................................................................................................................. 4 

205 Transmitted data conventions .................................................................................................. 6 

205.1 Fingerprint Ridge Representation .................................................................................. 6 

205.2 Byte and bit ordering ...................................................................................................... 6 

205.3 Grayscale data ............................................................................................................... 7 

205.4 Binary data ..................................................................................................................... 7 

205.5 Color data....................................................................................................................... 7 

205.6 Compression algorithms ................................................................................................ 8 

205.7 Color spaces ................................................................................................................ 10 

205.8 Scan sequence............................................................................................................. 11 

206 Image resolution requirements............................................................................................... 12 

206.1 Scanner resolution requirement................................................................................... 12 

206.2 Transmitting resolution requirement............................................................................. 13 

207 Information exchange package description............................................................................ 13 

207.1 Information exchange package format......................................................................... 15 

207.2 Information exchange package contents ..................................................................... 15 

207.3 Implementation domains .............................................................................................. 16 

207.4 Image reference identification...................................................................................... 17 

ii 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

208 Record description ................................................................................................................. 18 

208.1 Logical record types ..................................................................................................... 18 

208.2 Record format............................................................................................................... 23 

209 Type-1 transaction information record ................................................................................... 24 

209.1 XML elements for the Type-1 transaction information record...................................... 24 

209.2 End of transaction information record Type-1.............................................................. 33 

210 Type-2 user-defined descriptive text record........................................................................... 33 

210.1 XML elements for Type-2 logical records .................................................................... 33 

210.2 End of Type-2 user-defined descriptive text record ..................................................... 36 

210.3 Additional user-defined descriptive text records .......................................................... 36 

211 Type-3 through Type-6 fingerprint image records.................................................................. 37 

211.1 General......................................................................................................................... 37 

211.2 Types 3-6 logical record XML elements....................................................................... 37 

211.3 End of fixed-resolution fingerprint image record .......................................................... 41 

211.4 Additional fixed-resolution image records .................................................................... 41 

212 Type-7 user-defined image record ......................................................................................... 43 

212.1 XML elements for Type-7 logical records .................................................................... 44 

212.2 End of Type-7 user-defined image record ................................................................... 46 

212.3 Additional user-defined descriptive text records .......................................................... 46 

213 Type-8 signature image record .............................................................................................. 46 

213.1 XML elements for the Type-8 logical record ................................................................ 46 

213.2 End of Type-8 signature image record......................................................................... 51 

213.3 Additional variable-resolution latent image records ..................................................... 51 

214 Type-9 minutiae data record .................................................................................................. 51 

214.1 Minutiae and other information descriptors (Standard Format) ................................... 51 

214.2 XML elements for Type-9 logical record ...................................................................... 54 

214.3 End of Type-9 logical record ........................................................................................ 63 

iii 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

214.4 Additional minutiae records.......................................................................................... 63 

215 Type-10 facial & SMT image record....................................................................................... 63 

215.1 XML elements for the Type-10 logical record .............................................................. 64 

215.2 End of Type-10 logical record ...................................................................................... 95 

215.3 Additional facial & SMT image records ........................................................................ 95 

216 Type-11 record reserved for future use.................................................................................. 96 

217 Type-12 record reserved for future use.................................................................................. 96 

218 Type-13 variable-resolution latent image record.................................................................... 96 

218.1 XML elements for the Type-13 logical record .............................................................. 96 

218.2 Additional variable-resolution latent image records ................................................... 109 

219 Type-14 variable-resolution fingerprint image record .......................................................... 109 

219.1 XML elements for the Type-14 logical record ............................................................ 110 

219.2 Additional variable-resolution fingerprint image records............................................ 125 

220 Type-15 variable-resolution palmprint image record............................................................ 125 

220.1 XML elements for the Type-15 logical record ............................................................ 126 

220.2 Additional variable-resolution palmprint image records ............................................. 135 

221 Type-16 user-defined testing image record ......................................................................... 135 

221.1 XML elements for the Type-16 logical record ............................................................ 135 

221.2 Additional variable-resolution latent image records ................................................... 144 

222 Type-17 Iris image record .................................................................................................... 144 

222.1 General....................................................................................................................... 144 

222.2 XML elements for the Type-17 logical record ............................................................ 144 

222.3 End of Type-17 Iris Data Record................................................................................ 156 

222.4 Additional Type-17 Iris Data Records ........................................................................ 156 

223 Type-99 CBEFF record ........................................................................................................ 157 

223.1 XML elements for the Type-99 logical record ............................................................ 157 

223.2 End of Type-99 CBEFF Data Record......................................................................... 163 

iv 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

223.3 Additional Type-99 CBEFF Data Records ................................................................. 163 

224 Another individual................................................................................................................. 164 

Annex A 7-bit American Standard Code for Information Interchange (ASCII) ........................ 165 

Annex B Package Schema....................................................................................................... 166 

Annex C Base-64 encoding scheme ........................................................................................ 179 

Annex D JPEG file interchange format..................................................................................... 182 

Annex E NCIC Codes for Scars, marks, tattoos, and other characteristics ............................. 190 

Annex F Instance Document .................................................................................................... 202 

Annex G INCITS / M1 378 Minutiae Format............................................................................. 247 

Annex H Best Practice Application Level 30 ............................................................................ 258 

Annex I Best Practice Image Capture Requirements for SAP Levels 40, 50, and 51.............. 261 

Annex J Face-Pose Values ...................................................................................................... 268 

Annex K Bibliography ............................................................................................................... 271 

Annex L Constraint Schema..................................................................................................... 272 

Figures 

Figure 1 Byte and bit ordering ......................................................................................................... 7 

Figure 2 Order of scanned image.................................................................................................. 12 

Figure 3 Minutiae coordinate system ........................................................................................... 53 

Figure 4 Examples of resolution for levels 30, 40, & 50/51.......................................................... 78 

Figure 6 Eye and nostril center feature points............................................................................... 83 

Figure 5 Feature point codes defined in ISO/IEC 14496-2 ........................................................... 85 

Figure 7 Entire joint image.......................................................................................................... 105 

v 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Tables 

Table 201 Grayscale & color image compression codes ............................................................... 8 

Table 202 Binary compression codes .......................................................................................... 10 

Table 203 Color spaces................................................................................................................ 10 

Table 204 Logical record types .................................................................................................... 14 

Table 205 Number of logical records per transaction................................................................... 16 

Table 206 Resolution of Transmitted fingerprint image records .................................................. 19 

Table 207 Type-1 transaction information record........................................................................ 26 

Table 208 Directory of character sets .......................................................................................... 33 

Table 209 Type-2 user-defined descriptive text record................................................................ 34 

Table 210 Type 3-6 record layout................................................................................................. 38 

Table 211 Finger & palm impression types .................................................................................. 42 

Table 212 Finger position code & maximum image dimensions................................................... 43 

Table 213 Type-7 user-defined image record .............................................................................. 44 

Table 214 Type-8 record layout.................................................................................................... 47 

Table 215 Minutiae types ............................................................................................................. 52 

Table 216a Type-9 minutiae record (all implementations) ........................................................... 55 

Table 217 Pattern classification.................................................................................................... 62 

Table 218 Type-10 facial and SMT record layout ........................................................................ 64 

Table 219 Device monitoring modes............................................................................................ 70 

Table 220 Subject acquisition profiles.......................................................................................... 75 

Table 221 Photo descriptors......................................................................................................... 78 

Table 222 Subject facial description codes .................................................................................. 80 

Table 223 Eye color codes ........................................................................................................... 81 

Table 224 Subject feature points.................................................................................................. 82 

Table 225 Eye and nostril center feature point codes.................................................................. 83 

vi 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 226 Hair color codes........................................................................................................... 86 

Table 227 Subject pose................................................................................................................ 87 

Table 228 Acquisition source type codes..................................................................................... 88 

Table 229 Color codes ................................................................................................................. 90 

Table 230 Tattoo classes ............................................................................................................. 91 

Table 231 Tattoo subclasses........................................................................................................ 92 

Table 232 Type-13 Variable-resolution latent record ................................................................... 97 

Table 233 EJI and tip codes ....................................................................................................... 105 

Table 234 Type-14 Variable-resolution fingerprint record.......................................................... 110 

Table 235 Palm codes and dimensions ..................................................................................... 126 

Table 236 Type-15 Variable-resolution palmprint record ........................................................... 128 

Table 237 Type-16 Variable-resolution latent record ................................................................. 137 

Table 238 Type-17 Iris image record layout............................................................................... 145 

Table 239 Type-99 CBEFF biometric data record layout........................................................... 158 

Table 240 CBEFF Biometric type............................................................................................... 164 

vii 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

45 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Foreword (This foreword is not part of American National Standard 

2 ANSI/NIST-ITL 2-200X) 

3 Various levels of law enforcement and related criminal justice agencies as well as identity 

4 management organizations procure equipment and systems intended to facilitate the 

determination of the personal identity of a subject from fingerprint, palm, facial (mugshot), or other 

6 biometric information (including iris data). To effectively exchange identification data across 

7 jurisdictional lines or between dissimilar systems made by different manufacturers, a standard is 

8 needed to specify a common format for the data exchange. To this end, this standard has been 

9 developed. 

Fingerprint and palmprint images are acquired from flatbed scanners, Automated Fingerprint 

11 Identification Systems (AFIS), live-scan fingerprint and palmprint readers, and/or image storage 

12 and retrieval systems. An AFIS scans and stores the digital representations of fingerprint and 

13 palmprint images that are captured from inked cards, chemical cards, or live-scan readers that 

14 acquire the fingerprint and palmprint image data directly from the subject's fingers and hands. 

The scanned images are then processed to extract specific types of features from the images. 

16 Sources used for the electronic capture of a subject's facial image (mugshot) and scars, marks, 

17 and tattoos (SMTs) present include digital still and video cameras and other types of video 

18 recorders that capture images and produce digital image files directly from the subject's head and 

19 body. Scanners are used to digitize images from photographs, pictures, or sketches. The digital 

representations of these images consist of grayscale or color pixels depending on the application 

21 and equipment. 

22 These digital images may be stored in a compressed or uncompressed form in an image storage 

23 and retrieval system together with textual descriptive data and other information for each image. 

24 When required, specific images stored on a file can be retrieved from storage and be 

incorporated as part of an electronic mugshot book, or an electronic line-up. Images selected 

26 may be the result of textual filters based on physical descriptive or information fields associated 

27 with each image. Stored SMT images can also be retrieved as part of an identification process. 

28 Features from the scanned fingerprint, palmprint, facial, or other biometric images can be 

29 compared against a masterfile containing features extracted from previously scanned images. 

The result of these comparisons is a list of potential candidate identifications. A human examiner, 

31 using images retrieved from the system or fingerprint cards, then can identify a subject. 

32 The Information Technology Laboratory (ITL) of the National Institute of Standards and 

33 Technology (NIST) sponsored the development of this American National Standards Institute 

34 (ANSI) approved American National Standard using the NIST Canvass Method to demonstrate 

evidence of consensus. This updated standard replaces ANSI/NIST-ITL 1-2000 that address the 

36 interchange of fingerprint, facial, and SMT data. 

37 The document that follows is the Extensible Markup Language (XML) version. Part 1, the 

38 conventional version, was approved April 20, 2007. 

39 Part 2 of this standard includes twelve annexes. Annex A is normative and contains the 7-bit 

American Standard Code for Information Interchange (ASCII). Annex B is normative and 

41 contains the ITL package schema. Annex C is normative and describes the base-64 encoding 

42 scheme. Annex D, a description of the Joint Photographic Experts Group (JPEG) File 

43 Interchange Format (JFIF), is normative and considered part of the standard. Annex E is 

44 normative and contains the current version’s (December 2000) codes from the National Crime 

Information Center (NCIC) Code Manual for describing the body locations of Scars, Marks, and 

viii 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Tattoos. Annex F is an example XML instance document file containing all logical record types, 

2 and illustrating the use of every data element. The biometric exchange records contained in 

3 Annex F are formatted in accordance with this standard and are informative and not considered 

4 as part of the standard. Annex G is informative and contains the XML version of the INCITS/M1 

5 378 minutiae format specifications. Informative Annexes H and I contain best practices for 

6 mugshots for application levels 30 through 51, respectively. Annex J is also informative and 

7 contains various examples of face-pose value combinations. Annex K is a bibliography of 

8 informative references. Annex L is a normative and contains the constraint schema. 

9 Over the past several years, many data interchange and processing applications have converted 

10 to or are in the process of migrating toward an XML format approach for processing data. In 

11 order to provide the ability to directly interface with such applications, this XML alternative 

12 representation of the textual, image, and other biometric information has been developed. This 

13 Part 2 of this standard contains the XML alternative for the conventional ANSI/NIST standard. A 

14 goal of Part 2 is to describe a “one-to-one” correspondence of XML elements to the numerically 

15 tagged conventional elements described in Part 1. Another goal is to define an XML 

16 representation that conforms to the National Information Exchange Model (NIEM). The Part 1 

17 subelements (separated by the US and RS characters in the conventional representation) have 

18 been given XML counterparts in Part 2. 

19 Suggestions for the improvement of this standard are welcome. They should be sent to the 

20 attention of Elaine M. Newton, NIST ITL Biometric Standards, Information Access Division, Image 

21 Processing Group, NIST, 100 Bureau Dr, Mail Stop 8940, Gaithersburg, MD 20899-8940. 

22 The following organizations, recognized as having an interest in the standardization of the data 

23 format for the interchange of fingerprint, facial, SMT, and other biometric information, were 

24 contacted prior to the approval of this revision of the standard. Inclusion in this list does not 

25 necessarily imply that the organization concurred with the submittal of the proposed standard to 

26 ANSI. 

27 

ATS John Loverude 

Authenti-Corp Roger Cottam 

Aware, Inc. Robert Mungovan 

Scott Hills (Alt.) 

BAE Systems Information Technology Brian Finegold 

Biometric Information Mgmt Michael Powers 

BPRA William Long 

BSI 2000, Inc. Kevin Wilson 

Bundeskriminalamt Gerd Hardt 

 Christopher Schiel (Alt.) 

BWXT Y-12 Edmon Begoli 

Mark Patterson (Alt.) 

California Department of Justice Anthony Doonan 

Cherry Biometrics Michael Cherry 

City of Henderson, Nevada Kent Timothy (Alt.) 

Cogent Systems, Inc. Anne Wang 

Howard Dong (Alt.) 

ix 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Comnetix, Inc. Henri Schueler 

Cross Match Technologies Greg Cannon 

Ralph Lessmann (Alt.) 

Daon Matt Swayze 

Catherine Tilton (Alt.) 

Dataworks Plus Rick Johnson 

Todd Pastorini (Alt.) 

Delaware State Police Russell McNatt 

DHS/TSA -Federal Air Marshal Service Matthew O'Neill 

DHS/US-VISIT Brad Wing 

FBI/CJIS Tom Hopper 

B. Scott Swann 

 Patrice Yuh 

Florida Department of Law Enforcement Charles Schaeffer 

Foray Technologies David Witzke, II 

Global XSTF Paul Embley 

Hall Biometric Associates David Hall 

Hennepin County Shefiff's Office Leila Tite 

Higgins-Hermansen Group, LLC Peter Higgins 

Kathleen Higgins (Alt.) 

Homeland Security Institute Robert Zimmerman 

IAI AFIS Committee, Chair Peter Komarinski 

ID Technology Partners, Inc. Mark Jerde 

M. Paul Collier (Alt.) 

Tom Greiner (Alt.) 

R. Michael McCabe (Alt.) 

Kern County Sheriff Daniel Harmuth 

Kosovo Police Besim Hasanaj 

KS Information Technology Kristianne Scheier 

L-1 Identity Solutions Scott Piette 

Brian Martin (Alt.) 

D.P. Weston (Alt.) 

Lockheed Martin David Hagan 

Scott Rogers (Alt.) 

Los Angeles Co. Sheriff's Dept. T.J. Smith (Alt.) 

Mentalix, Inc. Dale Remmers 

MN Bureau of Criminal Apprehension Jerry Olson 

Motorola Mitchell Higashi 

MTG Management Consultants Terrance Gough, Jr. (Alt.) 

National Policing Improvement Agency Geoff Whitaker 

John Flahive (Alt.) 

x 

1 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Nebraska State Patrol Jill Davidson 

Bruce Luhr (Alt.) 

NEC Corporation of America Stephen Dunbar 

Netherlands National Police Agency Bastiaan Zetstra 

NIST Michael Garris 

Patrick Grother (Alt.) 

Stan Janet (Alt.) 

NLETS Catherine Plummer 

Noblis John Mayer-Splain (Alt.) 

Nortel PEC Solutions, Inc Benjamin McDowell 

NYS Div. of Criminal Justice Services Nancy Campbell 

 Marie Sciocchetti 

Mary Ann Pelletier (Alt.) 

Raytheon Teddy Ko 

Charles Li (Alt.) 

Recorders & Medicare Systems Pvt. Ltd. Vikas Goel 

Royal Canadian Mounted Police Mark Labonte 

Saber Bonny Scheier 

Sagem Morpho, Inc. Glen McNeil 

Jean-Christophe Fondeur 

(Alt.) 

SAIC Doug Houck 

Santa Clara County Sherrif's Office Richard Reneau 

Steria JR Vanden Eynde 

Terrorist Screening Center Joseph Krozak 

 Stan Larmee 

 CJ Lee 

 Christopher Holmes 

Texas Department of Public Safety Mike Lesko 

Toronto Police Service Newton Phoon 

United States Army Biometrics Task Force Dale Hapeman 

 Samuel DeWolfe 

 Arun Vemury 

vIDentity Systems, Inc. Alan Viars 

WI Dept. of Justice Gerry Coleman 

xi 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 201 Introduction 

2 The first version of this standard, ANSI/NBS-ICST 1-1986, was published by NIST (formerly the 

3 National Bureau of Standards) in 1986. It was a minutiae-based standard that required a 

4 minimum amount of memory for the exchange and storage of fingerprint information. 

5 In 1993 an updated version of the "Data Format for the Interchange of Fingerprint Information" 

6 standard (ANSI/NIST-CSL 1-1993) was approved by ANSI. While retaining the provision for 

7 minutiae data, the standard focused on formats for the exchange of fingerprint images rather than 

8 processed minutiae data. 

9 In 1997 an addendum was approved to provide for the interchange of facial ("mugshot") image 

10 data and captured image data from scars, marks, and tattoos. The addendum carried the ANSI 

11 designation of ANSI/NIST-ITL 1a-1997. 

12 A workshop convened in 1998 to review the standard and its addendum. This resulted in a new 

13 revision that merged the two documents, emphasized the tagged-field record, and introduced 

14 new record types for the exchange of recorded fingerprint, latent, and palm print images. The 

15 revision was titled “Data Format for the Interchange of Fingerprint, Facial, & Scar Mark & Tattoo 

16 (SMT) Information” and carried the ANSI designation of ANSI/NIST-ITL 1-2000. 

17 This Part 1 version of the standard approved in 2007 was the result of agreements reached 

18 during two workshops held in April and December of 2005 to review the ANSI/NIST-ITL 1-2000 

19 standard. During the first workshop, proposals to update the standard were introduced. The 

20 proposals were refined and presented for discussion and approval during the second workshop. 

21 The major enhancements in this revision include: 

22 • Image quality and segmentation data to support the processing of the "flat" images 

23 • Definition of a new block of minutiae fields to harmonize with the INCITS M1 minutiae 

24 standard 

25 • Best practice application levels for the capture of facial images 

26 • A new record type for the exchange of iris information 

27 • A new record type to contain biometric information not described in this standard but 

28 conformant to other registered biometric data format standards; and 

29 • An XML alternative representation for this standard. 

30 202 Scope, purpose, and conformance 

31 202.1 Scope 

32 This standard defines the content, format, and units of measurement for the exchange of 

33 fingerprint, palmprint, facial/mugshot, scar mark & tattoo (SMT), iris, and other biometric sample 

34 information that may be used in the identification or verification process of a subject. The 

35 information consists of a variety of mandatory and optional items, including scanning parameters, 

36 related descriptive and record data, digitized fingerprint information, and compressed or 

1 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 uncompressed images. This information is primarily intended for interchange among criminal 

2 justice administrations or organizations that rely on automated fingerprint and palmprint 

3 identification systems, or use facial/mugshot, SMT, iris, or other biometric data for identification 

4 purposes. 

This standard does not define the characteristics of the software that shall be required to format 

6 the textual information or to compress and reconstruct the associated digital fingerprint image 

7 information. Typical applications for this software might include, but are not limited to, computer 

8 systems associated with a live-scan fingerprinting system, a workstation that is connected to or is 

9 part of an Automated Fingerprint Identification System (AFIS), or an image storage and retrieval 

system containing fingerprints, facial/mugshot, SMT, or other biometric images. 

11 202.2 Purpose 

12 Information compiled and formatted in accordance with this standard can be recorded on 

13 machine-readable media or may be transmitted by data communication facilities. This information 

14 may have been gathered directly from a fingerprint scanner or camera in lieu of a fingerprint card, 

a latent fingerprint, facial/mugshot, or other types of photographs. Law enforcement, criminal 

16 justice agencies, and other organizations that process biometric data will use the standard to 

17 exchange fingerprint, palmprint, facial, iris, or other photographic images and related biometric 

18 identification data. 

19 202.3 Conformance 

Systems claiming conformance with this standard shall implement the transmitting and/or 

21 receiving of record types as defined by this standard. Systems claiming conformance are not 

22 required to implement every record type specified herein. At a minimum, they must be capable of 

23 transmitting and receiving Type-1 records. However, in order for a transaction to be meaningful, 

24 there must be at least one additional type of record included. The implementer must document 

the record types supported in terms of transmitting and/or receiving. Those record types not 

26 implemented shall be ignored by the conforming system receiving a transaction. 

27 Implementers are expected to extend this standard by supplying substitution elements for the 

28 abstract elements <itl:UserDefinedFields>, <itl:RecordImage>, <itl:RecordMinutiae>, 

29 <itl:DomainDefinedDescriptiveText>, and/or <itl:OtherDescriptiveText>. The substitution 

elements must be created in a separate user-declared namespace. The content of the 

31 substitution elements must be well-formed XML and should follow NIEM rules for extending the 

32 National Information Exchange Model. Implementers may modify the xmlns: and import attributes 

33 to reference user-defined namespaces and extension schema. The minOccurs and maxOccurs 

34 attributes in the ITL constraint schema version of ansi-nist.xsd may be modified to facilitate use of 

NIEM ansi-nist elements in user-defined blocks. 

36 Implementers may not introduce new elements except within the substitution elements described 

37 above, nor may they change the order or structure of elements defined by the standard. 

38 The root element, <itl:NISTBiometricInformationExchangePackage>, may be included as a 

39 payload in a larger package. 

All required elements must be present in a conforming instance document even if the standard’s 

41 schema do not strictly enforce the requirement. 

2 
 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 203 Normative References 

2 The following standards contain provisions that, through reference in this text, constitute 

3 provisions of this American National Standard. At the time of publication, the editions indicated 

4 were valid. All standards are subject to revision, and parties that utilize this American National 

5 Standard are encouraged to investigate the possibility of applying the most recent editions of the 

6 standards indicated below. 

7 ANSI X3.4-1986 (R1992), Information Systems --- Coded Character Sets ---7-Bit American 

8 National Standard Code for Information Interchange (7-Bit ASCII).1 

9 ANSI X3.172-1990, Information Systems --- Dictionary for Information Systems. 

10 ANSI/EIA - 538-1988 Facsimile Coding Schemes and Coding Control Functions for Group 4 

11 Facsimile Equipment. 

12 ANSI/IAI 2-1988, Forensic Identification --- Automated Fingerprint Identification Systems --- 

13 Glossary of Terms and Acronyms.2 

14 ANSI INCITS 378-2004, Finger Minutiae Format for Data Interchange.3 

15 ANSI INCITS 398-2005, the Common Biometric Exchange Formats Framework (CBEFF) 

16 ANSI/NIST-ITL 1-2000, Information systems – Data Format for the Interchange of Fingerprint, 

17 Facial, and Scar Mark & Tattoo (SMT) Information.4 

18 IAFIS-DOC-0178-7.1 Electronic Fingerprint Transmission Specification, Version 7.1, May 2, 

19 20055

. 

20 IAFIS-IC-0110 (V3) WSQ Gray-scale Fingerprint Image Compression Specification, December 

21 19, 1997. 

22 ISO 646-1983 7-Bit Coded Character Set for Information Interchange.6 

23 ISO 8601-1988, Data Elements and Interchange Formats - Information Interchange 

24 Representation of Dates and Times. 

1

 ANSI X3 Documents available from the American National Standards Institute, 11 West 42nd Street, New York, NY 

10036. 

2

 Available from the International Association for Identification. 

3

 All INCITS documents available from http://www.incits.org 

4

 http://fingerprint.nist.gov/standard/index.html 

5

 All CJIS, IAFIS, and NCIC documents available from Criminal Justice Information Services Division, Federal Bureau of 

Investigation 935 Pennsylvania Avenue, NW, Washington, DC 20535. 

6

 All ISO documents available from the American National Standards Institute, 11 West 42nd Street, New York, NY 10036. 

3 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 ISO/IEC International Standard 10918-1, Information Technology - Digital Compression and 

2 Coding of Continuous-Tone Still Images Part 1: Requirements and Guidelines. This is commonly 

3 referred to as the JPEG (Joint Photographic Experts Group) algorithm. 

4 ISO/IEC 14496-2, MPEG4 Feature Points, Annex C. 

5 ISO/IEC International Standard 15444-1, JPEG 2000, Information Technology - Digital 

6 Compression and Coding of Continuous-Tone Still Images Part 1: Requirements and Guidelines. 

7 MTR 04B0000022 (Mitre Technical Report), Margaret Lepley, Profile for 1000ppi Fingerprint 

8 Compression, Version 1.1, April 2004.7 Available at: 

9 http://www.mitre.org/work/tech_papers/tech_papers_04/lepley_fingerprint/lepley_fingerprint.pdf 

10 National Crime Information Center (NCIC) Code Manual, Ninth Edition, December, 2000. 

11 W3C XML and XML Schema, World Wide Web Consortium, Extensible Markup Language, 

12 http://www.w3.org/XML/. Extensible Markup Language (XML) 1.0 (Third Edition) W3C 

13 Recommendation 4th February 2004, François Yergeau, Tim Bray, Jean Paoli, C. M. Sperberg14 McQueen, Eve Maler 

15 National Information Exchange Model, NIEM Version 2.0, July 2007, http://www.niem.gov 

16 NIST Fingerprint Image Quality (NFIQ), NISTIR 7151 ed., National Institute of Standards and 

17 Technology, 2004.8

 Available at: 

18 http://fingerprint.nist.gov/NFIS/ir_7151.pdf 

19 204 Definitions 

20 The following definitions and those given in the American National Standard Automated 

21 Fingerprint Identification Systems --- Glossary of Terms and Acronyms, ANSI/IAI 2-1988, apply to 

22 this standard. 

23 204.1 AAMVA 

24 Abbreviation for the American Association of Motor Vehicle Administrators 

25 204.2 ANSI 

26 Abbreviation for the American National Standards Institute, Inc. 

27 204.3 aspect ratio 

28 The width-to-height ratio of the captured image. 

29 204.4 complete friction ridge exemplars 

30 See major case prints. 

7 http://www.mitre.org/work/tech_papers/tech_papers_04/lepley_fingerprint/lepley_fingerprint.pdf 

8

 Also see: E. Tabassi, “A novel approach to fingerprint image quality” in IEEE International Conference on Image 

Processing ICIP-05, Genoa, Italy, September 2005. 

4 
 

 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

204.5 effective scanning resolution 

The number of pixels per unit distance that remain after a captured image has been subsampled, 

scaled, or interpolated down to produce an image having a lower value of scanning resolution 

(fewer pixels per mm) than was used originally to capture the image. 

204.6 Entire Joint Image 

An exemplar image containing one rolled and three plain full finger views (full-length finger 

images) for a single finger. 

204.7 FAP 

Abbreviation Facial Animation Parameters 

204.8 IBIA 

Abbreviation for International Biometric Industry Association 

204.9 ICC 

Abbreviation for International Color Consortium. 

204.10 logical record 

A record independent of its physical environment; portions of one logical record may be located in 

different physical records, or several logical records or parts of logical records may be located in 

one physical record. 

204.11 major case prints 

A set of exemplar images of all finger and palm friction skin for an individual. Major case prints 

include full palm print images, as well as rolled fingerprints, plain fingerprints, entire joint images, 

and rolled tips for all fingers. They are also known as complete friction ridge exemplars. (Note 

that the term Major Case Prints may be deprecated for some uses because in legal contexts it 

can be incorrectly read as making an implication regarding the severity of the case.) 

204.12 minutia 

The point where a friction ridge begins, terminates, or splits into two or more ridges. Minutiae are 

friction ridge characteristics that are used to individualize a fingerprint image. 

204.13 mugshot 

Term used interchangeably with facial image. The term facial image usually implies a higher 

quality image than a mugshot. 

204.14 native scanning resolution 

The nominal scanning resolution used by a specific AFIS, live-scan reader, or other image 

capture device and supported by the originator of the transmission. 

204.15 nominal transmitting resolution 

The nominal number of pixels per unit distance (ppmm or ppi) of the transmitted image. The 

transmitting resolution may be the same as the scanning resolution for a particular image. On the 

other hand, the transmitting resolution may be less than the scanning resolution if the scanned 

image was subsampled, scaled, or interpolated down before transmission. 

204.16 NFIQ 

Abbreviation for NIST Fingerprint Image Quality. 

204.17 ppi 

Abbreviation for pixels per inch 

5 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 204.18 ppmm 

2 Abbreviation for pixels per millimeter 

3 204.19 RGB 

4 Red, Green, Blue used to represent color pixels comprised of a specified number of bits to 

5 represent each of these primary color components. 

6 204.20 ROI 

7 Abbreviation for region of interest. 

8 204.21 SMT 

9 Abbreviation used for scar, mark, and tattoo information. 

10 204.22 scanning resolution 

11 The number of pixels per unit distance at which an image is captured (ppmm or ppi). 

12 204.23 tagged-field record 

13 A logical record containing unique ASCII field identifiers for variable-length data fields that is 

14 capable of being parsed based on the field identifier and the data contents of each field. 

15 204.24 transaction 

16 A command, message, or an input record that explicitly or implicitly calls for a processing action. 

17 Information contained in a transaction shall be applicable to a single subject. 

18 204.25 XML 

19 Extensible Markup Language. A convention for marking-up, tagging, data for electronic 

20 transmission. 

21 205 Transmitted data conventions 

22 205.1 Fingerprint Ridge Representation 

23 Ridges in fingerprint images shall be represented as “dark ridges” in either grayscale or binary 

24 image data. 

25 205.2 Byte and bit ordering 

26 Each XML information element, tags and data shall be represented using ASCII character data. The 

27 order for transmission of the ASCII bytes shall be most significant byte first and least significant byte 

28 last. Within a byte, the order of transmission shall be the most significant bit first and the least 

29 significant bit last. Figure 1 illustrates the order of transmission of the bytes and bits within an 

30 exchange package. 

31 

6 
 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

MSB LSB MSB LSB 

First Byte Last Byte 

Most Significant Byte Least Significant Byte 

Most Significant Byte Least Significant Byte 

Most Significant Byte Within a Block Transmitted First 

Least Most 

Significant Byte of Data Significant 

Bit Bit 

Most Significant Bit Within a Byte Transmitted First 

1 Figure 1 Byte and bit ordering 

2 

3 205.3 Grayscale data 

4 Depending on the record type, grayscale image data may be transmitted in either compressed or 

5 uncompressed form. The transmission of uncompressed grayscale images shall consist of 

6 pixels, each of which shall normally be quantized to eight bits (256 gray levels) and held in a 

7 single unsigned byte. Increased precision for pixel values greater than 255 shall use two 

8 unsigned bytes to hold sixteen-bit pixels with values in the range of 0-65635. For grayscale data, 

9 a true black pixel shall be represented by a zero. A true white pixel shall have all of its bits of 

10 precision set to “1”. Therefore, true white pixels quantized to eight bits shall have a value of 

11 “255”, while a value of “1023” shall be used for pixels quantized to ten bits. As explained in 

12 205.2, grayscale values requiring less than 8 or 16 bits are expressed as one or two bytes, right 

13 justified and zero padded on the left. 

14 The transmission of compressed grayscale images shall be the output of the appropriate 

15 grayscale compression algorithm specified. Upon reconstruction of a compressed image the 

16 grayscale value for each pixel shall be the same (for lossless algorithms) or nearly the same (for 

17 lossy algorithms) as pixels in an uncompressed image. Binary data so constructed shall be 

18 converted to ASCII for transmission using Base64 encoding. 

19 

20 205.4 Binary data 

21 Binary image data may be transmitted in either compressed or uncompressed form, then 

22 converted to ASCII for transmission using Base64 encoding. The transmission of uncompressed 

23 binary images shall consist of pixels, each of which shall be quantized to one of two levels (binary 

24 representation). A value of zero shall be used to represent a white pixel and a value of one shall 

25 be used to represent a black pixel. For transmission of uncompressed binary images, eight pixels 

26 shall be left justified and packed into a single unsigned byte. The most significant bit of the byte 

27 shall be the first of the eight pixels scanned. 

28 205.5 Color data 

29 It is assumed that the scanned images consist of nominal 24 to 48-bit RGB pixels for color facial, 

30 SMT, iris, or user-defined testing images. Color image data may be transmitted in either 

7 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 compressed or uncompressed form. The transmission of uncompressed color images shall 

2 consist of RGB pixels, each component of which shall be quantized to at least 256 levels (8 bits). 

3 For each pixel, the three components shall be sequentially formatted for transmission on a pixel4 by-pixel basis. 

5 205.6 Compression algorithms 

6 205.6.1 Color and grayscale compression algorithms 

7 Compressed image data shall adhere to the requirements of the algorithm used. Table 201 lists 

8 the binary (shown here in base 10) and ASCII codes to be used for the available compression 

9 methods for encoding grayscale and color images described by this standard. (Table 201 is the 

10 same as Table 1 in Part 1.) But the choice of compression algorithms is limited by the type of 

11 data being exchanged (fingerprint, face, etc.). The description for each type of data exchange 

12 lists the legitimate compression algorithms that can be used for that type and whether a binary or 

13 ASCII code should be used. 

14 

15 Table 201 Grayscale & color image compression codes 

Algorithm Name Binary Code 

(in base 10) 

ASCII Code 

Uncompressed 0 NONE 

WSQ Version 2.0 1 WSQ20 

JPEG ISO/IEC 10918 (Lossy) 2 JPEGB 

JPEG ISO/IEC 10918 (Lossless) 3 JPEGL 

JPEG 2000 ISO/IEC 15444-1 (Lossy) 4 JP2 

JPEG 2000 ISO/IEC 15444-1 (Lossless) 5 JP2L 

Portable Network Graphics 6 PNG 

16 

17 The "JPEGB" algorithm indicates that the scanned or captured image was compressed using 

18 baseline JPEG. An entry of "JPEGL" indicates that the lossless mode of the JPEG algorithm was 

19 used to compress the image. If the image is captured in grayscale, then only the luminance 

20 component will be compressed and transmitted. For JPEG, the data shall be formatted in 

21 accordance with the JPEG File Interchange Format, Version 1.02 (JFIF)9

 as found in Annex D.10 

22 An entry of "JP2" indicates that the scanned or captured image was compressed using lossy 

23 JPEG 2000. (Conformance with ISO 15444-1 is provided through part 4 of the standard, ISO 

24 15444-4 “Conformance Testing”.) An entry of "JP2L" indicates that the lossless mode of the 

9 Developed by C-Cube Microsystems, 1778 McCarthy Blvd., Milpitas, CA 95035. 

10 Annex D specifies YCC as the standard color space to be used for JFIF. YCC is a linear combination of RGB 

components or channels. sRGB can be JPEG compressed and stored using JFIF, which is specified in Annex D. 

8 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 JPEG 2000 algorithm was used to compress the image. For JPEG 2000, the data shall be 

2 formatted in conformance with JP2 format as described in ISO 15444-1. 

3 Where JPEG 2000 is used for the compression of fingerprint images, specification/options 

4 contained in Profile for 1000ppi Fingerprint Compression (as listed in Section 203, Normative 

References) shall apply. This reference addresses the 9 quality layers between 0.015 bpp and 

6 0.55 bpp. 

7 Where JPEG 2000 is used for compression of facial images, the following conditions shall apply: 

8• Filters: The 9-7 irreversible filters described in ISO 15444-1 should be used for lossy mode; 

9 however for handheld devices (fixed point processors), the 5-3 reversible filters may be used 

instead. The 5-3 reversible filters shall be used for lossless mode. A conformant decoder shall be 

11 able to decode code streams created through both filters. 

12• Number of resolution levels: The image shall be encoded using enough resolution levels to 

13 ensure that a thumbnail with max(width, height) <= 64 is available in the image. Example: a 

14 640x480 image shall be encoded with 5 resolution levels, which enables sub-resolution decodes 

of 320x240, 160x120, 80x60, and 40x30. 

16• Resolution as the dominant progression: JPEG 2000 allows five progression orders - LRCP, 

17 RLCP, RPCL, PCRL and CPRL. The RLCP progression order (resolution, layer, component, 

18 position) shall be used since it best facilitates decode and display of lower resolution derivative 

19 images by remote networked devices. Through the RLPC progression order, the code stream 

shall be formatted so that the resolution information of the image is the first data made available 

21 to a decoder in a streaming mode of operation. 

22• Bits per Channel: The number of bits per channel for encoders and decoders shall be 8-16 bits. 

23• Single tile images: Facial images shall be encoded using only single tile to avoid tiling artifacts. 

24• JPEG 2000 quality layers: The image shall be encoded using at least 10 quality layers to enable 

quality progressive decoding or sub-quality image extraction. 

26 Region of Interest (ROI) Encoding is allowed: This encoding method is a useful way to compress 

27 a facial image to a small size, while retaining sufficient image quality within the specified ROI to 

28 perform either human or automated identification. 

29 205.6.2 Binary compression algorithms 

Table 202 lists the binary codes for the available compression schemes that can be used for 

31 encoding binary image data described by this standard. (Table 202 is the same as Table 2 in 

32 Part 1.)This standard does not use ASCII codes for describing compression methods for the 

33 exchange of binary images. 

34 

36 

37 

9 
 

 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 202 Binary compression codes 

Algorithm Name Binary Code ASCII Code Notes 

Uncompressed 0 ________ Image Packed 8 pixels/byte 

Facsimile ANSI/EIA 538-1988 1 ________ Lossless 

2 

3 The transmission of compressed binary images shall be the output of the binary compression 

4 algorithm specified by ANSI/EIA-538-1988, then converted to ASCII characters using Base64 

5 encoding. Upon decompression, each pixel with a value of zero shall be considered to be white 

6 and each pixel with a value of one shall be considered to be black. 

7 205.7 Color spaces 

8 Table 203 lists the codes and their descriptions for each of the available color spaces used within 

9 this standard. (Table 203 is the same as Table 3 in Part 1.) All other color spaces are to be 

10 marked as undefined. 

11 

12 Table 203 Color spaces 

Code Description 

UNK Undefined 

GRAY Grayscale (monochrome) 

RGB Undetermined color space for an RGB image 

SRGB sRGB (IEC 61966-2-1) 

YCC YCbCr (legacy) 

SYCC YCbCr (JPEG 2000 compressed) 

13 

14 205.7.1 Backwards compatibility 

15 In previous versions of this standard, the term “color space” referred to device-dependent color 

16 information with a particular sequence and range for the three color channels. The choice was 

17 either RGB or an RGB-derivative space known as YCC. Neither space provides an objective 

18 definition of a particular color or relates to the way in which humans perceive color. 

19 Although sRGB is the preferred color space for compressed images for this version, in the 

20 previous version of this standard, it was stated that “the preferred color space for compressed 

21 images using baseline JPEG and JFIF is YCbCr to be coded as ‛YCC’,” while the color space for 

22 uncompressed color images was to be labeled RGB. Therefore, for backwards compatibility 

23 purposes, new systems must accommodate JPEG images that have been labeled as using the 

24 YCC color space. Specifically, systems conformant with this standard must accept an entry of 

25 YCC and interpret it as meaning a (device-dependent) RGB color space. 

10 
 

 

 

 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 205.7.2 Color space sRGB 

2 

3 

To ensure that color images exchanged between differing systems can be correctly displayed or 

printed, images should be converted to the device-independent color space, sRGB11, before 

4 compression or transmission to another system. As defined by IEC 61966-2-1, sRGB is a non5 linear display profile that accommodates the voltage-to-color response characteristics of most 

6 high quality CRT monitors. The colors of the red, green, and blue phosphors (primaries) and the 

7 white point setting of an sRGB-conformant monitor are specified in the IEC document. 

8 The relationship between sRGB and a linear RGB space having the IEC-defined primaries and 

9 white point is as follows: 

value , value lin lin 12.92 for ≤ 0.0031308

valuesRGB = ( 1/ 2.4 ) value 0.055, value lin − lin 1.055 for > 0.0031308

⎧

⎨

⎩

where valuelin is an R, G, or B value in linear RGB space 

10 (with a range of 0 to1) and valuesRGB is the corresponding 

R, G, or B value in non - linear sRGB space (also with a 

range of 0 to1). To convert from/to the range of 0 to 255, 

divide/multiply by 255. 

11 Typically, modern digital cameras, desktop scanners, LCD monitors, and printers, although they 

12 don't inherently operate in sRGB space, are designed with circuitry or software to produce sRGB 

13 output or to accommodate sRGB as an input space. If an image acquisition device's color space 

14 is unknown, sRGB is usually a reasonable choice. If an acquisition device and its software 

15 cannot provide sRGB output, various color management products are available commercially that 

16 use its color profile, often available from its manufacturer, to convert images in its native color 

17 space to sRGB. 

18 205.8 Scan sequence 

19 Each color, grayscale, or binary image formatted in accordance with this standard shall appear to 

20 have been captured in an upright position and approximately centered horizontally in the field of 

21 view. The recorded image data shall appear to be the result of a scanning of a conventional 

22 inked impression of a fingerprint or photo of a face or iris. This is also equivalent to a live-scan 

23 capture of the finger, or a camera capture of a face or iris. The scanning sequence (and recorded 

24 data) shall appear to have been from left-to-right, progressing from top-to-bottom of the 

25 fingerprint, palm print, face, SMT, or iris. Figure 2 illustrates the recording order for the scanned 

26 fingerprint image. 

27 For the purpose of describing the position of each pixel within an image to be exchanged, a pair 

28 of reference axes shall be used. The origin of the axes, pixel location (0,0), shall be located at 

29 the upper left-hand corner of each image. The x-coordinate (horizontal) position shall increase 

30 positively from the origin to the right side of the image. The y-coordinate (vertical) position shall 

31 increase positively from the origin to the bottom of the image. 

11 For information on sRGB, see http://www.w3.org/Graphics/Color/sRGB or many of the white papers available at 

http://www.color.org. 

11 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

2 

3 Figure 2 Order of scanned image 

4 

5 206 Image resolution requirements 

6 Image resolution requirements are applicable to fingerprint, palmprint, and signature images. 

7 Facial/ mugshot, SMT, and iris images rely on the total number of pixels scanned and transmitted 

8 and are not dependent on the specific scanning resolution used. 

9 206.1 Scanner resolution requirement 

10 Binary and grayscale fingerprint images to be exchanged shall be captured by an AFIS, live-scan 

11 reader, or other image capture device operating at a specific native scanning resolution. The 

12 minimum scanning resolution for this capture process shall be 19.69 ppmm plus or minus 0.20 

13 ppmm (500 ppi plus or minus 5 ppi). Scanning resolutions greater than this minimum value and 

14 with a device tolerance of plus or minus 1% may be used. Although a minimum scanning 

15 resolution is specified, a maximum value for scanning resolution is not specified by this standard. 

16 However, for latents images, the minimum scanning resolution (or effective scanning resolution) 

17 and transmission rate for latent images shall be 39.37 ppmm plus or minus 0.40 ppmm (1000 ppi 

18 plus or minus 10 ppi). 

19 The recommended migration path to higher scanning resolutions for image capturing devices with 

20 a native scanning resolution of 19.69 ppmm (500 ppi) shall be at a rate of 100% of the current 

21 native scanning resolution. The recommended migration path progresses from 19.69 ppmm to 

22 39.37 ppmm (500 ppi to 1000 ppi), from 39.37 ppmm to 78.74 ppmm (1000 ppi to 2000 ppi), etc. 

23 Capture devices with native scanning resolutions not in step with this migration path shall provide 

24 (through subsampling, scaling, or interpolating downward) an effective scanning resolution that 

25 matches the next lower interval in the migration path. For example a device with native scanning 

26 resolution of 47.24 ppmm (1200 ppi) shall be required to provide an effective resolution of 39.37 

27 ppmm (1000 ppi). 

12 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 206.2 Transmitting resolution requirement 

2 Each image to be exchanged shall have a specific resolution associated with the transmitted 

3 data. This transmitting resolution does not have to be the same as the scanning resolution. 

4 However, the transmitting resolution shall be within the range of permissible resolution values for 

5 that record type. When an image is captured at a scanning resolution greater than the 

6 permissible upper limit of the transmitting resolution for that record type, the image shall be 

7 subsampled, scaled, or interpolated down. This processing to reduce the scanning resolution to 

8 a lower effective resolution must be performed before the transmission occurs. 

9 For high-resolution binary and grayscale images, the preferred transmitting resolution shall be the 

10 same as the minimum scanning resolution of 19.69 ppmm plus or minus 0.20 ppmm (500 ppi plus 

11 or minus 5 ppi). Any transmitting resolution within the range of the minimum scanning resolution 

12 to a value of 20.47 ppmm plus or minus 0.20 ppmm (520 ppi plus or minus 5 ppi) is permitted for 

13 the processing of high-resolution records. 

14 For low-resolution binary and grayscale images, the preferred transmitting resolution shall be half 

15 of the minimum scanning resolution or 9.84 ppmm plus or minus 0.10 ppmm (250 ppi plus or 

16 minus 2.5 ppi). Any transmitting resolution within the range of half of the minimum scanning 

17 resolution to a value of 10.24 ppmm plus or minus 0.10 ppmm (260 ppi plus or minus 2.5 ppi) is 

18 permitted for the processing of low-resolution records. 

19 For variable-resolution images, the preferred transmitting resolution is not specified, but must be 

20 at least as great as the high-resolution rate of 19.69 ppmm. At this time there is no upper limit on 

21 the variable-resolution rate for transmission. However, the recommended migration path to 

22 higher transmitting resolutions is the same as for the scanning resolutions. That is, to progress 

23 from 19.69 ppmm to 39.37 ppmm plus or minus 1% (500 ppi to 1000 ppi), from 39.37 ppmm to 

24 78.74 ppmm plus or minus 1% (1000 ppi to 2000 ppi), etc. For images captured at a native 

25 scanning resolution greater than the permissible upper limit of a transmitting resolution step in the 

26 migration path, it may be necessary to subsample, scale, or interpolate down. The result of this 

27 processing is to obtain an effective scanning resolution that conforms to a step in the 

28 transmission migration path. 

29 The transmitting resolution shall be contained in fields specified by the format for the variable30 resolution record. However, before transmitting variable-resolution records, the operational 

31 capabilities of the sending and receiving systems should be addressed, and prior agreement 

32 should be made with the recipient agency or organization before transmitting the image. 

33 207 Information exchange package description 

34 This standard defines the composition of an information exchange package that is transmitted to 

35 a remote site or agency. The package may or may not be a complete file. In many cases the 

36 package will be included as a payload with an XML formatted outer wrapper for transaction or 

37 protocol purposes. The package may also be a part of a larger, user-defined data structure. The 

38 standard strictly defines, however, the content of data within the 

39 <itl:NISTBiometricInformationExchangePackage> complex element. 

40 As specified in this standard, certain portions of the exchange package shall be in accordance 

41 with definitions provided by the receiving agency. This exchange package shall contain one or 

42 more logical records each corresponding to one of the defined available types. The logical 

43 records are intended to convey specific types of related information pertinent to the exchange 

44 package itself or to the subject of the package. All of the logical records belonging to a single 

13 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 package shall be contained within a single 

2 <itl:NISTBiometricInformationExchangePackage> element. 

3 The Part 1 conventional standard defines three logical records for the exchange of ASCII textual 

4 information fields, six logical records for the exchange of binary information and seven tagged5 field record types designed for the exchange of a combination of ASCII and image data 

6 within a single logical record structure. For this Part 2 version, the distinction between ASCII 

7 and binary information is gone. All records are ASCII, with ASCII XML element tags. All binary 

8 image data is converted to ASCII using Base64 encoding and contained within a 

9 <nc:BinaryBase64> element. 

10 Two additional record types are reserved for inclusion in future revisions of this standard. The 

11 sixteen defined types of logical records together with the identifier for each type are listed in Table 

12 204. 

13 

14 Table 204 Logical record types 

Record 

Category 

Code 

Record Element Tag Logical record contents Type of data 

1 <itl:PackageInformationRecord> Transaction information ASCII 

2 <itl:PackageDescriptiveTextRecord> User-defined descriptive text ASCII 

3 <itl:PackageImageRecord> Low-resolution grayscale fingerprint image ASCII/Base64 

4 <itl:PackageImageRecord> High-resolution grayscale fingerprint image ASCII/Base64 

5 <itl:PackageImageRecord> Low-resolution binary fingerprint image ASCII/Base64 

6 <itl:PackageImageRecord> High-resolution binary fingerprint image ASCII/Base64 

7 <itl:PackageImageRecord> User-defined image ASCII/Base64 

8 <itl:PackageImageRecord> Signature image ASCII/Base64, or 

Vector data 

9 <itl:PackageMinutiaeRecord> Minutiae data ASCII 

10 <itl:PackageImageRecord> Facial & SMT image ASCII/Base64 

11 Reserved for future use -

12 Reserved for future use -

13 <itl:PackageImageRecord> Variable-resolution latent image ASCII/ Base64 

14 <itl:PackageImageRecord> Variable-resolution fingerprint image ASCII/ Base64 

15 <itl:PackageImageRecord> Variable-resolution palmprint Image ASCII/ Base64 

16 <itl:PackageImageRecord> User-defined variable-resolution testing Image ASCII/ Base64 

17 <itl:PackageImageRecord> Iris image ASCII/ Base64 

18-98 Reserved for future use ASCII/ Base64 

99 <itl:PackageImageRecord> CBEFF Biometric data record ASCII/ Base64 

14 

15 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 207.1 Information exchange package format 

2 An exchange package shall contain one or more logical records pertaining to a single subject. 

3 The data in every record shall always be recorded in variable length fields using the 7-bit 

4 American National Standard Code for Information Interchange (ASCII) as described in ANSI 

X3.4-1986 and Annex A. For purposes of compatibility, the eighth (leftmost) bit shall contain a 

6 value of zero. 

7 For data interchange between non-English speaking agencies, character sets other than 7-bit 

8 ASCII may be used in non-image fields. UTF-8 is the preferred method of storing textual data 

9 that cannot be represented as 7-bit ASCII. This method supports international character sets for 

all user-defined fields in all record types. The mechanism to change character sets is described 

11 in Section 208.2.3, International Character Sets. By definition UTF-8 and other international 

12 character exchange methods are not applicable to record Type 1. 

13 The Part-1 data field element logical record length has been omitted from the Part-2 XML 

14 specification; there is no technical need for the byte count, and the value would be incompatible 

and meaningless for transformations between Part-1 and Part-2 formats. 

16 The first field in all records shall be labeled <ansi-nist:RecordCategoryCode> and contain 

17 the type (category) number of the record. The second field shall be labeled <ansi18 nist:ImageReferenceIdentification> and contain the image designation character as 

19 described in Section 207.4. The remaining XML elements must be present in the order defined 

by the standard and contain information as described for that particular element. 

21 Image data, compressed or uncompressed, originates as binary information. All binary 

22 information shall be converted to ASCII text using Base64 encoding. The XML tag 

23 <nc:BinaryBase64Object> shall be used to enclose converted binary data. 

24 The Type-2, Type-7, Type-9, Type-10, Type-13, Type-14, Type-15, Type-16, Type-17, and Type99 contain “abstract” XML elements intended to be used by implementers to contain user-defined 

26 data extensions to this standard. The abstract elements that can be substituted are 

27 <itl:UserDefinedFields> wherever it appears, <itl:RecordImage> in the Type-7 record, 

28 <itl:RecordMinutiae> in the Type-9 record, and <itl:DomainDefinedDescriptiveText> and 

29 <itl:OtherDescriptiveText> in the Type-2 record. Within the exchange package, user-defined 

extensions can only appear as substitutes for these abstract elements. 

31 207.2 Information exchange package contents 

32 Exchange packages are required to contain one and only one Type-1 logical record per 

33 transaction. The Type-1 logical record, <itl:PackageInformationRecord>, shall always 

34 be the first logical record within the package. Depending on the usage and the number of 

fingerprint, palmprint, facial/mugshot, SMT, iris, or other biometric images available for 

36 processing, one or more additional records may be present in the package. 

37 Table 205 lists the typical range or the number of records that may be contained in a package. 

38 (Table 205 is the same as Table 5 in Part 1.) These record counts are shown by logical record 

39 types for common processing functions used for search inquiries, file maintenance, image 

request, and image responses. The record limits stated in the table are examples of typical 

41 transactions and should only be interpreted as a guideline. Receiving agencies may impose their 

42 own specific limit for each type of logical record depending on the application. The ranges listed 

43 specify the minimum and maximum number of logical records that may be contained in the 

44 package. The mandatory inclusion of a logical record is indicated by an entry of "1" in the table. 

15 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 An entry of "0" indicates the exclusion of that logical record type. The appearance of "0-N" in the 

2 table indicates that the standard imposes no limits on the number of records for that logical record 

3 type. An entry of "1-N" requires that at least one record be present with no upper limit on the 

4 number of records that may be present. 

5 207.3 Implementation domains 

6 The Type-2 record is composed of user-defined content. Much of the content in the Type-2 

7 record is used in the same way by local, state, and Federal agencies and requires the same data 

8 and formatting. In order to establish a common basis for XML elements, meaning, and 

9 formatting, jurisdictions that use the same general set of data may subscribe to a common 

10 implementation domain. 

11 An implementation domain can be viewed as a group of agencies or organizations that have 

12 agreed to use specific pre-assigned data blocks for exchanging information unique to their 

13 installations. Each user-defined XML element shall also have a definition and format associated 

14 with it. Each domain created shall have a point of contact responsible for keeping the 

15 documentation on the content of the user-defined data blocks within their domain. The contact 

16 shall serve as a registrar and maintain a repository including documentation for all the common 

17 and user-specific Type-2 content contained within the substitution block for 

18 <itl:DomainDefinedDescriptiveText>. As additional fields are required by specific 

19 agencies for their own applications, new XML elements and definitions can be registered and 

20 reserved to have a specific meaning. When this occurs, the domain registrar is responsible for 

21 registering a single definition for each XML element used by different members of the domain. 

22 Additional content in the Type-2 record may be defined as a substitute for 

23 <itl:OtherDescriptiveText> by agreement of sending and receiving parties. 

24 

25 Table 205 Number of logical records per transaction 

Record 

Category 

Code 

Master 

file 

inquiry 

Latent 

inquiry 

File 

maintenance 

Image 

request 

Search 

response 

Image 

request 

response 

1 1 1 1 1 1 1 

2 1-N 1-N 1-N 1 1 1 

3 0-14 0 0-14 0 0-14 0-14 

4 0-14 0-10 0-14 0 0-14 0-14 

5 0-14 0 0-14 0 0-14 0-14 

6 0-14 0-10 0-14 0 0-14 0-14 

7 0 0-N 0-N 0 0-N 0-N 

8 0-2 0 0-2 0 0-2 0-2 

9 0-10 0-N 0-N 0 0 0 

10 0-N 0-N 0-N 0 0-N 0-N 

13 0 0-N 0-N 0 0-N 0-N 

14 0-14 0 0-14 0 0-N 0-N 

15 0-8 0-N 0-8 0 0-N 0-N 

16 0 0 0-N 0 0-N 0-N 

17 0-2 0 0-2 0 0-2 0-2 

99 0 0 0-N 0 0-N 0-N 

16 

26 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 The Criminal Justice Information Services (CJIS) Division of the Federal Bureau of Investigation 

2 (FBI) has established and maintains the North American Domain subscribed to by the Royal 

3 Canadian Mounted Police (RCMP), the FBI, and several state and Federal agencies in North 

4 America. The registrar for this domain assigns and accounts for the domain-defined content to 

5 be used by its clients during the processing of transactions. Other domains also exist including 

6 those maintained by the United Kingdom (UK) and Interpol. These organizations have developed 

7 their own Type-2 record implementations tailored to their specific communities. 

8 207.4 Image reference identification 

9 With the exception of the Type-1 logical record, each of the remaining logical records present in 

10 an exchange package shall include an <ansi-nist:ImageReferenceIdentification>

11 element containing the Image Designation Character (IDC). The IDC shall be used to relate 

12 information items in the <ansi-nist:TransactionContentSummary> element of the Type-1 

13 record to each logical record, and to properly identify and link together logical records that pertain 

14 to the same entity such as a particular finger or face. The value of the IDC shall be a sequentially 

15 assigned positive integer starting from zero and incremented by one. If two or more logical 

16 records that are different representations of the same subject matter are present in a file, each of 

17 those logical records shall contain the same IDC. For example, a high-resolution image record of 

18 a specific fingerprint and the corresponding minutiae record for the same finger would carry the 

19 same IDC number. 

20 Although there is no upper limit on the number of logical records that may be present in a file, 

21 generally a minimum of two and no more than 25 logical records will be present in a file. For 

22 example, a tenprint search inquiry transaction may consist of a Type-1 record, a Type-2 record, 

23 14 high-resolution Type-4 or variable-resolution Type-14 grayscale image records, two Type-8 

24 signature records, six Type-15 palmprint records, and a Type-10 facial/mugshot image of the 

25 subject. Additional mugshot, SMT, iris, or other biometric logical records may expand the file 

26 even more. For this file configuration, the IDC shall range from "0" to "24" which would include an 

27 IDC code for the Type-2 record. Within the same file, multiple logical record types may be 

28 present and represent the same image. For example, if core and delta location information for 

29 the rolled impressions is requested, the transmission may also need to accommodate ten 

30 minutiae records within the same file. For each image representing the ten finger positions, the 

31 same IDC would be used in both the image and minutiae records. 

32 The IDC shall also be used to relate information items in the <ansi33 nist:TransactionContentSummary> element of the Type-1 record to each facial, SMT, iris, 

34 or other biometric image record. It properly identifies and links together different logical record 

35 types created from the same face/mugshot or SMT image. 

36 Furthermore, zero or more Type-7 records may also be present. Each Type-7 logical record 

37 representing a specific sample shall have a unique IDC with an increment of one greater than the 

38 last IDC used. 

17 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 208 Record description 

2 208.1 Logical record types 

3 208.1.1 Type-1 Transaction information record 

4 The XML name for the Type-1 record is <itl:PackageInformationRecord>, and its <ansi5 nist:RecordCategoryCode> element shall have a value of “01”. A Type-1 logical record is 

6 mandatory and is required for each exchange package. The Type-1 record shall provide 

7 information describing type and use or purpose for the transaction involved, a listing of each 

8 logical record included in the file, the originator or source of the physical record, and other useful 

9 and required information items. 

10 208.1.2 Type-2 User-defined descriptive text record 

11 The XML name for the Type-2 record is <itl:PackageDescriptiveTextRecord>, and its 

12 <ansi-nist:RecordCategoryCode> element shall have a value of “02”. Type-2 logical 

13 records shall contain user-defined XML data blocks substituting for the abstract elements 

14 provided by the standard. These data blocks provide identification and descriptive information 

15 associated with the subject of the transaction. Data contained in this record shall conform in 

16 format and content to the specifications of the domain name as listed in Domain Name field found 

17 in the Type-1 record. 

18 208.1.3 Type-3 through Type-6 fingerprint image records 

19 The XML name for the Type-3 through Type-6 records is <itl:PackageImageRecord>, and 

20 their <ansi-nist:RecordCategoryCode> elements shall have a values of “03”, “04”, “05”, 

21 and “06” respectively. Logical record types 3-6 are used to exchange fingerprint image records 

22 originally scanned at the minimum scanning resolution of 19.69 ppmm plus or minus 0.20 ppmm 

23 (500 ppi plus or minus 5 ppi) and transmitted at the nominal pixel density of 19.69 or 9.84 ppmm. 

24 The four record types differ according to the pixel density of the transmitted image and the type of 

25 data exchanged. Table 206 summarizes the differences between the four record types. (Table 

26 206 is the same as Table 6 in Part 1.) 

27 The fingerprint image data contained in any of the logical records may be in compressed form. 

28 The WSQ algorithm has been generally used to compress grayscale images while the facsimile 

29 algorithm is used for the binary images. Typically, there may be up to 14 records of any of these 

30 logical types of fingerprint images in a file; ten rolled impressions of the individual fingers, two 

31 plain impressions of the thumbs, and two simultaneously obtained plain impressions of the four 

32 remaining fingers on each hand. 

33 When the image data is obtained from a live-scan reader, it shall be the grayscale or binary 

34 output (or subsampled, scaled down, or interpolated output) of the live-scan fingerprint scanner 

35 and not a rescan of a hard copy fingerprint image. 

36 

37 

38 

39 

18 
 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 206 Resolution of Transmitted fingerprint image records 

Record type Data type Preferred 

Pixel Density 

Maximum 

Pixel Density 

Ppmm ppi ppmm ppi 

Type-3 Grayscale 9.84 250.00 10.34 252.50 

Type-4 Grayscale 19.69 500.00 20.67 525.00 

Type-5 Binary 9.84 250.00 10.34 252.50 

Type-6 Binary 19.69 500.00 20.67 525.00 

2 

3 208.1.3.1 Type-3 Low-resolution grayscale fingerprint image 

4 Type-3 logical records shall contain and be used to exchange low-resolution grayscale fingerprint 

5 image data that was scanned at no less than the minimum scanning resolution and then 

6 subsampled, scaled down, or interpolated. Alternatively, provided that it is no less than the 

7 minimum scanning resolution, the native scanning resolution may be used and the image 

8 processed. The resultant transmitting resolution in either case shall be within the bounds of the 

9 permissible transmitting resolution requirement for low-resolution images. 

10 208.1.3.2 Type-4 High-resolution grayscale fingerprint image 

11 Type-4 logical records shall contain and be used to exchange high-resolution grayscale 

12 fingerprint image data that was scanned at no less than the minimum scanning resolution. 

13 Alternatively, the native scanning resolution may be used. But in either case, if the scanning 

14 resolution is greater than the upper limit of the permissible transmitting resolution, the scanned 

15 data shall be subsampled, scaled down, or interpolated. The resultant transmitting resolution 

16 shall be within the bounds of the permissible transmitting resolutions for high-resolution fingerprint 

17 images. 

18 208.1.3.3 Type-5 Low-resolution binary fingerprint image 

19 Type-5 logical records shall contain and be used to exchange low-resolution binary fingerprint 

20 image data that was scanned at no less than the minimum scanning resolution and then 

21 subsampled, scaled down, or interpolated. Alternatively, provided that it is no less than the 

22 minimum scanning resolution, the native scanning resolution may be used and the image 

23 processed. The resultant transmitting resolution in either case shall be within the bounds of the 

24 permissible transmitting resolution requirement for low-resolution images. 

25 208.1.3.4 Type-6 High-resolution binary fingerprint image 

26 Type-6 logical records shall contain and be used to exchange high-resolution binary fingerprint 

27 image data that was scanned at no less than the minimum scanning resolution. Alternatively, the 

28 native scanning resolution may be used. But in either case, if the scanning resolution is greater 

29 than the upper limit of the permissible transmitting resolution, the scanned data shall be 

19 
 

30 208.1.6 Type-9 Minutiae data record 

31 The XML name for the Type-9 record is <itl:PackageMinutiaeRecord>, and its <ansi32 nist:RecordCategoryCode> element shall have a value of “09”. Type-9 logical records shall 

33 contain and be used to exchange geometric and topological minutiae templates and related 

34 information encoded from a finger or palm. Each record shall represent the processed image 

35 data from which the location and orientation descriptors of extracted minutiae characteristics are 

36 listed. The primary use of this record type shall be for remote searching of latent prints but may 

37 also be used for applications such as physical or logical access control. Each Type-9 logical 

38 record shall contain the minutiae data read from a fingerprint, palm, or latent image. 

39 208.1.7 Type-10 Facial & SMT image record 

40 The XML name for the Type-10 record is <itl:PackageImageRecord>, and its <ansi41 nist:RecordCategoryCode> element shall have a value of “10”. Type-10 image records shall 

42 contain and be used to exchange facial and image data from scars, marks, and tattoos (SMT) 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 subsampled, scaled down, or interpolated. The resultant transmitting resolution shall be within 

2 the bounds of the permissible transmitting resolutions for high-resolution fingerprint images. 

3 208.1.4 Type-7 User-defined image record 

4 The XML name for the Type-7 record is <itl:PackageImageRecord>, and its <ansi5 nist:RecordCategoryCode> element shall have a value of “07”. Type-7 logical records shall 

6 contain user-defined image data. Originally defined in 1993, this record type was designed for 

7 the exchange of binary image data that was not specified or described elsewhere in this 

8 standard. However, it is not intended that the use of the Type-7 record is restricted by the 

9 existence of other record types in this standard. It was intended as a temporary measure to 

10 enable the exchange of binary image data that would be defined by specific record types in later 

11 versions of the standard. 

12 With the exception of the <ansi-nist:RecordCategoryCode> and <ansi13 nist:ImageReferenceIdentification> elements, the parameters, and types of images to 

14 be exchanged are undefined by this standard. Implementers will define an XML data block that 

15 substitutes for the abstract <itl:RecordImage> element provided by this standard. These 

16 levels of required details shall be agreed upon between the sender and recipient. 

17 208.1.5 Type-8 Signature image record 

18 The XML name for the Type-8 record is <itl:PackageImageRecord>, and its <ansi19 nist:RecordCategoryCode> element shall have a value of “08”. Type-8 logical records shall 

20 contain and be used to exchange scanned high-resolution binary or vectored signature image 

21 data. If scanned, the resolution of the image data shall be no less than the minimum scanning 

22 resolution. If necessary, the scanned image data shall be subsampled, scaled down, or 

23 interpolated to fall within the limits of the transmitting resolution requirement. The resultant 

24 transmitting resolution shall be within the bounds of the permissible transmitting resolutions for 

25 the high-resolution fingerprint images. Vectored signature data shall be expressed as a series of 

26 numeric integers. 

27 Typically, there may be up to two of these Type-8 signature records in a file. Each Type-8 record 

28 shall contain image data representing the signature of the person being fingerprinted or of the 

29 official taking the fingerprint. 

20 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 together with textual information pertinent to the digitized image. The source of the image data 

2 shall be the image captured from scanning a photograph, a live image captured with a digital 

3 camera, or a digitized “freeze-frame” from a video camera. 

4 208.1.8 Type-11 Reserved for future use 

5 208.1.9 Type-12 Reserved for future use 

6 208.1.10 Type-13 Variable-resolution latent image record 

7 The XML name for the Type-13 record is <itl:PackageImageRecord>, and its <ansi8 nist:RecordCategoryCode> element shall have a value of “13”. Type-13 image records shall 

9 contain and be used to exchange variable-resolution latent fingerprint or palmprint image data 

10 together with fixed and user-defined textual information elements pertinent to the 

11 digitized image. In all cases, the minimum scanning resolution (or effective scanning 

12 resolution) and transmission rate for latent images shall be 39.37 ppmm plus or minus 0.40 

13 ppmm (1000 ppi plus or minus 10 ppi). The variable-resolution latent image data contained in the 

14 Type-13 logical record shall be uncompressed or may be the output from a lossless compression 

15 algorithm. There is no limit on the number of latent records that may be present in an exchange 

16 package. The Type-13 record may be considered as a version of the Type-7 record used for the 

17 exchange of latent images. 

18 208.1.11 Type-14 Variable-resolution fingerprint image record 

19 The XML name for the Type-14 record is <itl:PackageImageRecord>, and its <ansi20 nist:RecordCategoryCode> element shall have a value of “14”. Type-14 image records shall 

21 contain and be used to exchange variable-resolution fingerprint image data, segmented flat 

22 fingerprint data, or major case print data. Fixed and user-defined textual information elements 

23 pertinent to the digitized image may also be included. Fingerprint images can be either rolled or 

24 plain (including swiped) impressions. 

25 The scanning resolution is not specified for this record type. While the Type-14 record may be 

26 used for the exchange of 19.69 ppmm (500 ppi) images, it is strongly recommended that the 

27 minimum scanning resolution (or effective scanning resolution) for fingerprint images be 39.37 

28 ppmm plus or minus 0.40 ppmm (1000 ppi plus or minus 10 ppi). It should be noted that as the 

29 resolution is increased, more detailed ridge and structure information becomes available in the 

30 image. However, in all cases the scanning resolution used to capture a fingerprint image shall be 

31 at least as great as the minimum scanning resolution of 19.69 ppmm (500ppi). 

32 The variable-resolution fingerprint image data contained in the Type-14 logical record may be in a 

33 compressed form. Typically, there may be up to 14 of these Type-14 records in a file; ten rolled 

34 impressions of the individual fingers, two plain impressions of the thumbs or one plain impression 

35 of the two thumbs simultaneously, and two plain impressions of the four simultaneously obtained 

36 remaining fingers of each hand. The Type-14 record may be considered as a version of the 

37 Type-4 record used for the exchange of rolled or flat fingerprint images. 

38 208.1.12 Type-15 Variable-resolution palmprint image record 

39 The XML name for the Type-15 record is <itl:PackageImageRecord>, and its <ansi40 nist:RecordCategoryCode> element shall have a value of “15”. Type-15 image records shall 

41 contain and be used to exchange variable-resolution palmprint image data together with fixed 

42 and user-defined textual information elements pertinent to the digitized image. 

21 
 

1 The scanning resolution is not specified for this record type. While the Type-15 record may be 

2 used for the exchange of 19.69 ppmm (500 ppi) images, it is strongly recommended that the 

3 minimum scanning resolution (or effective scanning resolution) for palmprint images be 39.37 

4 ppmm plus or minus 0.40 ppmm (1000 ppi plus or minus 10 ppi). It should be noted that as the 

5 resolution is increased, more detailed ridge and structure information becomes available in the 

6 image. However, in all cases the scanning resolution used to capture a palmprint image shall be 

7 at least as great as the minimum scanning resolution of 19.69 ppmm (500ppi). 

8 The variable-resolution palmprint image data contained in the Type-15 logical record may be in a 

9 compressed form. The maximum number of occurrences of these Type-15 records in a file is 

10 eight. Different combinations may include: two writer’s palms to pair with two full palmprints; a 

11 writer's palm with an upper and lower palm from each hand; or a writer's palm with the thenar, 

12 hypothenar and interdigital areas from each hand. 

13 208.1.13 Type-16 User-defined variable-resolution testing image record 

14 The XML name for the Type-16 record is <itl:PackageImageRecord>, and its <ansi15 nist:RecordCategoryCode> element shall have a value of “16”. The Type-16 image record 

16 is intended as an alternate version of the Type-7 user-defined logical record. It is designed for 

17 developmental purposes and for the exchange of miscellaneous images. This logical record shall 

18 contain and be used to exchange, image data together with textual information elements 

19 pertinent to the digitized image. Such an image is usually not elsewhere specified or described in 

20 this Standard. 

21 A fixed scanning resolution is not specified for this record type. However where resolution is a 

22 factor in the captured image, it shall be at least as great as the minimum scanning resolution, that 

23 is, 19.69 ppmm (500ppi). Increases in the resolution used for capturing images should follow the 

24 recommended migration path to 39.37 ppmm (1000 ppi), 78.74 ppmm (2000 ppi), etc. It should 

25 be noted that as the resolution is increased, more detailed ridge and structure information 

26 becomes available in the image. 

27 The variable-resolution image data contained in the Type-16 logical record may be in a 

28 compressed form. With the exception of the tagged fields at the start of the record and the 

29 descriptors for the image data, the remaining details of the Type-16 record are undefined by this 

30 standard and shall be agreed upon between the sender and recipient. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

31 208.1.14 Type-17 Iris image record 

32 The XML name for the Type-17 record is <itl:PackageImageRecord>, and its <ansi33 nist:RecordCategoryCode> element shall have a value of “17”. Type-17 tagged-field image 

34 records shall contain and be used to exchange iris image data. This record type was developed 

35 to provide a basic level of interoperability and harmonization with the ANSI INCITS 379-2004 Iris 

36 Image Interchange Format and the ISO/IEC 19794-6 iris image data interchange format. Generic 

37 iris images may be exchanged using the mandatory elements of this record type. Optional 

38 elements may also be used to exchange additional information. Although the iris standards 

39 provide for two alternative iris image interchange formats, the Type-17 record shall only address 

40 and establish provision for the rectilinear image storage format that may be a raw uncompressed 

41 array of intensity values or a compressed format of the raw data. 

22 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 208.1.15 Type-99 CBEFF biometric data record 

2 The XML name for the Type-99 record is <itl:PackageImageRecord>, and its <ansi3 nist:RecordCategoryCode> element shall have a value of “99”. Type-99 logical records 

4 shall contain and be used to exchange biometric data that is not supported by other ANSI/NIST5 ITL logical record types. This provides a basic level of interoperability and harmonization with the 

6 ANSI INCITS and other biometric interchange formats. This is accomplished by using a basic 

7 record structure that is conformant with ANSI INCITS 398-2005, the Common Biometric 

8 Exchange Formats Framework (CBEFF) and a biometric data block specification registered with 

9 the International Biometrics Industry Association (IBIA)12. This logical record type supports and is 

10 intended to be used for biometric data types or formats that are not already represented by an 

11 existing ANSI/NIST data type. 

12 A CBEFF conformant Biometric Information Record (BIR) is made up of a Header, a Biometric 

13 Data Block (BDB), and an optional Signature Block. The Type-99 logical record does not use the 

14 Signature Block. Information required by the Header portion is encoded as XML elements within 

15 the Type-99 record. The final tagged field of the Type-99 record will contain biometric data as 

16 specified by the BDB interchange format. 

17 208.2 Record format 

18 An exchange package shall consist of one or more logical records. For each logical record 

19 contained in the package, several information elements appropriate to that record type shall be 

20 present. Complex elements may contain one or more complex or simple elements according to 

21 the rules of well-formed XML. Taken together these items are used to convey different aspects of 

22 the data contained in a data information object. To the extent possible, the objects used have 

23 been defined as a part of the National Information Exchange Model (NIEM). Some information 

24 objects may be repeated multiple times. 

25 The XML schema for this specification defines the structure, order and allowable content of the 

26 information exchange package. 

27 208.2.1 Information separators 

28 All separators are defined by the W3C XML recommendations. The characters “<” and “>” are 

29 reserved exclusively for enclosing element tag names. Every element with an opening tag 

30 <Name> must have a closing tag of format </Name>. 

31 The XML schema defined for this specification defines the sequence of elements as well as the 

32 allowable content of the data. All elements must contain valid data. Assuming the schema 

33 defines an element as optional, it should be omitted altogether rather than transmitting the 

34 element tags without any data content. 

35 Annex F provides a full set of examples of the use of XML elements in the standard. 

36 (Note: Table 7 from Part 1 has been intentionally omitted.) 

12 For more information, go to <http://www.ibia.org>. 

23 
 

30 209 Type-1 transaction information record 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 208.2.2 Record layout 

2 For all logical records, data elements are tagged according to XML rules. The format for each 

3 element shall consist of a tag name enclosed in angle brackets followed by data followed by a 

4 closing tag. For example <nc:IdentificationID>6</nc:IdentificationID>. Complex 

5 data elements contain other elements in a nested fashion; for example 

6 <ansi-nist:ImageReferenceIdentification>

7 <nc:IdentificationID>6</nc:IdentificationID>

8 </ansi-nist:ImageReferenceIdentification> 

9 The ordering of elements is strict. The text of this standard defines the order and nesting 

10 structure of elements. The schema also provides a W3C representation of the order and 

11 hierarchical structure of the XML content. 

12 208.2.3 International character sets 

13 All of the fields in the Type-1 transaction record must be recorded using the 7-bit ASCII code, 

14 which is the default character set code within a transaction. In order to affect data and 

15 transaction interchanges between non-English speaking or based agencies, a technique is 

16 available to encode information using character sets other than 7-bit ASCII. Fields from theType17 1 logical record and ASCII “LEN” and “IDC” text fields must still be encoded using 7-bit ASCII. 

18 But all other designated text fields can be encoded using alternate character sets. The general 

19 mechanism for accomplishing this provides for backward compatibility with existing readers, 

20 supports multiple character sets in a single text string, and handles internationally accepted 

21 character sets and text order conventions such as ISO character sets, UTF-8, and Unicode. 

22 Character sets within a transaction may only be switched in user-defined data. Appropriate 

23 mechanisms must be defined as part of the user-defined data definition. 

24 The base-64 encoding scheme, found in email, shall be used for converting non-ASCII text into 

25 ASCII form. Annex C describes the use of the base-64 system. It is expected that this encoding 

26 scheme will be used to convert all (originally) binary image data to ASCII for transmission, and 

27 will also be used to convert non-ASCII data into ASCII data in user-defined data. 

28 All XML element tags including the “<” and “>” characters shall appear in the transaction as 7-bit 

29 ASCII characters. 

31 209.1 XML elements for the Type-1 transaction information record 

32 The following paragraphs describe the data contained in each XML element of the transaction 

33 information record. Table 207 provides a list of the elements for the transaction information 

34 record. It is required that all elements of the record are ordered in the sequence described. For 

35 each of the elements, Table 207 lists for cross-reference purposes the Part-1 mnemonic and field 

36 number, the “condition code” as being mandatory “M” or optional “O”, the Part-2 XML element 

37 name, and occurrence limits. An entry containing an "*" indicate that there is no established limit. 

38 Annex F contains an example of the use of the standard that illustrates the layout for a Type-1 

39 logical record. 

24 
 

5 

10 

15 

20 

25 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 The Type-1 record shall be contained within this complex element: 

2 <itl:PackageInformationRecord> 

3 [. . . Type 01 Record Content . . .] 

4 </itl:PackageInformationRecord> 

209.1.1 Record length 

6 Cross reference: Part-1 Section 9.1.1 Field 1.001: Logical record length (LEN) 

7 There is no corresponding Part 2 XML element. 

8 209.1.2 Element <ansi-nist:RecordCategoryCode> 

9 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

record type. For the Type-1 record, it shall contain a value of 01. 

11 <ansi-nist:RecordCategoryCode>01</ansi12 nist:RecordCategoryCode> 

13 209.1.3 Element <ansi-nist:Transaction> 

14 This is a mandatory complex element. All of the remaining elements in the Type-1 record are 

nested within, as described in the subsections below. 

16 <ansi-nist:Transaction> 

17 [. . . Transaction elements . . .] 

18 </ansi-nist:Transaction> 

19 

21 

22 

23 

24 

25 

26 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

LEN 1.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

 <ansi-nist:Transaction> 1 1 

DAT M 1.005 <ansi-nist:TransactionDate> 1 1

DAI M 1.007 <ansi-nist:TransactionDestinationOrganization> 1 1 

ORI M 1.008 <ansi-nist:TransactionOriginatingOrganization> 1 1 

GMT O 1.014 <ansi-nist:TransactionUTCDate> 0 1

TCN M 1.009 <ansi-nist:TransactionControlIdentification> 1 1 

TCR O 1.010 <ansi-nist:TransactionControlReferenceIdentification> 0 1 

DOM O 1.013 <ansi-nist:TransactionDomain> 0 1

 <ansi-nist:TransactionImageResolutionDetails> 1 1 

NSR M 1.011 <ansi-nist:NativeScanningResolutionValue> 1 1 

NTR M 1.012 <ansi-nist:NominalTransmittingResolutionValue> 1 1 

VER M 1.002 <ansi-nist:TransactionMajorVersionValue> 1 1

VER M 1.002 <ansi-nist:TransactionMinorVersionValue> 1 1

PRY O 1.006 <ansi-nist:PriorityValue> 0 1

TOT M 1.004 <ansi-nist:TransactionCategoryCode> 1 1

CNT M 1.003 <ansi-nist:TransactionContentSummary> 1 1

DCS O 1.015 <ansi-nist:TransactionCharacterSetDirectory> 0 * 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 

2 Table 207 Type-1 transaction information record 

3 

4 209.1.3.1 Element <ansi-nist:TransactionDate> 

5 Cross reference: Part-1 Section 9.1.5 Field 1.005: Date (DAT) 

6 This mandatory element shall contain the date that the transaction was initiated. The date shall 

7 appear as eight digits, separated by dashes, in the format YYYY-MM-DD. The YYYY characters 

8 shall represent the year the transaction was initiated; the MM characters shall be the tens and 

9 units values of the month; and the DD characters shall be the tens and units values of the day in 

10 the month. For example, 2008-02-29 represents February 29, 2008. The complete date must be 

11 a legitimate date. 

12 

26 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Complex element <ansi-nist:TransactionDate> shall have the simple element <nc:Date>, which 

2 will contain transaction date data. 

3 <ansi-nist:TransactionDate> 

4 <nc:Date>2008-02-29</nc:Date>

</ansi-nist:TransactionDate> 

6 209.1.3.2 Element <ansi-nist:TransactionDestinationOrganization> 

7 Cross reference: Part-1 Section 9.1.7 Field 1.007: Destination agency identifier (DAI) 

8 This mandatory complex element shall contain the identifier of the administration or organization 

9 designated to receive the transmission. The size and data content of this element shall be userdefined and in accordance with the receiving agency. 

11 Element <ansi-nist:TransactionDestinationOrganization> shall have two child elements: a 

12 mandatory <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex 

13 element <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, 

14 which will contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> 

shall contain the datum for the text name of the organization. 

16 <ansi-nist:TransactionDestinationOrganization>

17 <nc:OrganizationIdentification>

18 <nc:IdentificationID>WI013415Y 

19 </nc:IdentificationID>

</nc:OrganizationIdentification>

21 <nc:OrganizationName>Text</nc:OrganizationName>

22 </ansi-nist:TransactionDestinationOrganization> 

23 209.1.3.3 Element <ansi-nist:TransactionOriginatingOrganization> 

24 Cross reference: Part-1 Section 9.1.8 Field 1.008: Originating agency identifier (ORI) 

This mandatory complex element shall contain the identifier of the administration or organization 

26 originating the transaction. The size and data content of this element shall be user-defined and in 

27 accordance with the receiving agency. 

28 Element <ansi-nist:TransactionOriginatingOrganization> shall have two child elements: a 

29 mandatory <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex 

element <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, 

31 which will contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> 

32 shall contain the datum for the text name of the organization. 

33 <ansi-nist:TransactionOriginatingOrganization>

34 <nc:OrganizationIdentification>

<nc:IdentificationID>WI013415Y</nc:Identific

36 ationID> 

37 </nc:OrganizationIdentification>

38 <nc:OrganizationName>Text</nc:OrganizationName>

39 </ansi-nist:TransactionOriginatingOrganization> 

27 
 

1 209.1.3.4 Element <ansi-nist:TransactionUTCDate> 

2 Cross reference: Part-1 Section 9.1.14 Field 1.014: Date (GMT) 

3 This optional element provides a mechanism for expressing the date and time in terms of 

4 universal Greenwich Mean Time (GMT) units, also called Coordinated Universal Time (UTC), 

5 also called Zulu Time (Z). If used, the <ansi-nist:TransactionUTCDate> element contains the 

6 universal date that will be in addition to the local date contained in <ansi-nist:TransactionDate>. 

7 Use of the GMT element eliminates local time inconsistencies encountered when a transaction 

8 and its response are transmitted between two places separated by several time zones. The GMT 

9 provides a universal date and 24-hour clock time independent of time zones. It is represented as 

10 "YYYY-MM-DDTHH:MM:SSZ”, a 20-character string that is the concatenation of the date with the 

11 GMT, separated by the character “T”, and concluding with a “Z”. The “YYYY” characters shall 

12 represent the year of the transaction, the “MM” characters shall be the tens and units values of 

13 the month, and the “DD” characters shall be the tens and units values of the day of the month, the 

14 “HH” characters represent the hour, the “MM” the minute, and the “SS” represents the second. 

15 The complete date shall not exceed the current date. 

16 Complex element <ansi-nist:TransactionUTCDate> shall have the simple element 

17 <nc:DateTime>, which will contain transaction date and time data. 

18 <ansi-nist:TransactionUTCDate> 

19 <nc:DateTime>2008-02-29T05:25:00Z 

20 </nc:DateTime>

21 </ansi-nist:TransactionUTCDate> 

22 209.1.3.5 Element <ansi-nist:TransactionControlIdentification> 

23 Cross reference: Part-1 Section 9.1.9 Field 1.009: Transaction control number (TCN) 

24 This mandatory element shall contain the Transaction Control Number as assigned by the 

25 originating agency. A unique alphanumeric control number shall be assigned to each transaction. 

26 For any transaction that requires a response, the respondent shall refer to this number in 

27 communicating with the originating agency. 

28 Complex element <ansi-nist:TransactionControlIdentification> shall have the simple element 

29 <nc:IdentificationID>, which will contain the transaction control identification datum. 

30 <ansi-nist:TransactionControlIdentification> 

31 

32 <nc:IdentificationID>56839</nc:IdentificationID>

33 </ansi-nist:TransactionControlIdentification> 

34 209.1.3.6 Element <ansi-nist:TransactionControlReferenceIdentification> 

35 Cross reference: Part-1 Section 9.1.10 Field 1.010: Transaction control reference (TCR) 

36 This optional element shall be used for responses that refer to the TCN of a previous transaction 

37 involving an inquiry or other action that required a response. 

38 Complex element <ansi-nist:TransactionControlReferenceIdentification> shall have the simple 

39 element <nc:IdentificationID>, which will contain the transaction control reference identification 

40 datum. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

28 
 

 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<ansi-nist:TransactionControlReferenceIdentification> 

<nc:IdentificationID>56839</nc:IdentificationID>

</ansi-nist:TransactionControlReferenceIdentification> 

209.1.3.7Element <ansi-nist:TransactionDomain> 

Cross reference: Part-1 Section 9.1.13 Field 1.013: Domain name (DOM) 

This optional complex element identifies the domain name for the user-defined Type-2 logical 

record implementation. If present, the domain name may only appear once within a transaction. 

It shall consist of one or two information items. One mandatory child information item will 

uniquely identify the agency, entity, or implementation used for formatting the content in the Type2 record. Another optional child information item will contain the unique version of the particular 

implementation. The default value for the domain name shall be the North American Domain 

implementation “NORAM”. 

Complex element <ansi-nist:TransactionDomain> shall have two child elements, <ansinist:DomainVersionNumberIdentification> and <ansi-nist:OrganizationName>. Complex element 

<ansi-nist:DomainVersionNumberIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the domain version number datum. 

<ansi-nist:TransactionDomain> 

<ansi-nist:DomainVersionNumberIdentification> 

<nc:IdentificationID>7.02</nc:Identification

ID> 

<ansi-nist:DomainVersionNumberIdentification> 

<ansi-nist:OrganizationName>NORAM</ansinist:OrganizationName>

</ansi-nist:TransactionDomain> 

209.1.3.8Element <ansi-nist:TransactionImageResolutionDetails> 

This is a mandatory complex element. The native scanning resolution and nominal transmitting 

resolution elements are nested within, as described in the subsections below. 

<ansi-nist:TransactionImageResolutionDetails> 

[. . . Image resolution elements . . .] 

</ansi-nist:TransactionImageResolutionDetails> 

209.1.3.8.1Element <ansi-nist:NativeScanningResolutionValue> 

Cross reference: Part-1 Section 9.1.11 Field 1.011: Native scanning resolution (NSR) 

This mandatory element shall specify the native scanning resolution of the AFIS or other 

fingerprint or palmprint image capture device supported by the originator of the transmission. The 

value permits the recipient of this transaction to send response data at a transmitting resolution 

tailored to the NSR (if it is able to do so) or to the minimum scanning resolution. The value shall 

be expressed as five bytes specifying the native scanning resolution in pixels per millimeter. The 

resolution shall be expressed as two numeric characters followed by a decimal point and two 

29 
 

1 more numeric characters (e.g., 19.69). This element is needed because the interchange of 

2 fingerprint information between systems of the same manufacturer may, in some instances, be 

3 more efficiently done at a transmitting resolution equal to the native scanning resolution of the 

4 system rather than at the minimum scanning resolution specified in this standard. For 

5 transactions that do not contain Type-3 through Type-7 fingerprint image records, the value shall 

6 be set to “00.00”. 

7 <ansi-nist:NativeScanningResolutionValue>19.69 

8 </ansi-nist:NativeScanningResolutionValue> 

9 209.1.3.8.2 Element <ansi-nist:NominalTransmittingResolutionValue> 

10 Cross reference: Part-1 Section 9.1.12 Field 1.012: Nominal transmitting resolution (NTR) 

11 This mandatory element shall specify the nominal transmitting resolution for the fingerprint or 

12 palmprint image(s) being exchanged. The value shall be expressed as five bytes specifying the 

13 transmitting resolution in pixels per millimeter. The resolution shall be expressed as two numeric 

14 characters followed by a decimal point and two more numeric characters (e.g., 19.69). The 

15 transmitting resolution shall be within the range specified by the transmitting resolution 

16 requirement. For transactions that do not contain Type-3 through Type-7 fingerprint image 

17 records, the value shall be set to “00.00”. 

18 <ansi-nist:NominalTransmittingValue>19.69 

19 </ansi-nist:NominalTransmittingResolutionValue> 

20 

21 209.1.3.9 Element <ansi-nist:TransactionMajorVersionValue> 

22 Cross reference: Part-1 Section 9.1.2 Field 1.002: Version number (VER), first two characters 

23 This mandatory two-byte ASCII value shall be used to specify the current major version number 

24 of the standard implemented by the software or system creating the file. The entry in this element 

25 for the 2000 version is "03" and the entry for this 2007 version of the approved standard shall be 

26 "04". This version number addresses the optional inclusion of the logical Type-10 

27 through Type-17 and Type-99 image records. 

28 <ansi-nist:TransactionMajorVersionValue>04 

29 </ansi-nist:TransactionMajorVersionValue> 

30 209.1.3.10 Element <ansi-nist:TransactionMinorVersionValue> 

31 Cross reference: Part-1 Section 9.1.2 Field 1.002: Version number (VER), last two characters 

32 This mandatory two-byte ASCII value shall be used to specify the current minor version number 

33 of the standard implemented by the software or system creating the file. The initial revision 

34 number for a version shall be "00”. 

35 <ansi-nist:TransactionMinorVersionValue>00 

36 </ansi-nist:TransactionMinorVersionValue> 

37 

38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

30 
 

1 209.1.3.11 Element <ansi-nist:TransactionPriorityValue> 

2 Cross reference: Part-1 Section 9.1.6 Field 1.006: Priority (PRY) 

3 This optional element shall contain a single information character to designate the urgency with 

4 which a response is desired. The values shall range from “1” to “9”, with "1" denoting the highest 

5 priority. The default value shall be defined by the agency receiving the transaction. 

6 <ansi-nist:TransactionPriorityValue>5 

7 </ansi-nist:TransactionPriorityValue> 

8 209.1.3.12 Element <ansi-nist:TransactionCategoryCode> 

9 Cross reference: Part-1 Section 9.1.4 Field 1.004: Type of transaction (TOT) 

10 This mandatory element shall contain an identifier, which designates the type of transaction and 

11 subsequent processing that this file should be given. (Note: Type of Transaction shall be in 

12 accordance with definitions provided by the receiving agency.) 

13 <ansi-nist:TransactionCategoryCode>CAR 

14 </ansi-nist:TransactionCategoryCode> 

15 209.1.3.13 Element <ansi-nist:TransactionContentSummary> 

16 Cross reference: Part-1 Section 9.1.3 Field 1.003: File content (CNT) 

17 This mandatory complex element shall list and identify each of the logical records in the file by 

18 record type. It also specifies the order in which the remaining logical records shall appear in the 

19 file. It shall consist of three child elements. The first two have one occurrence each. The third 

20 complex element child is repeated, one occurrence for each logical record in the package 

21 following this Type-1 information record. 

22 The first child element, <ansi-nist:ContentFirstRecordCategoryCode>, shall relate to this Type-1 

23 Transaction record. The value of this child element shall be the single character "1" (selected 

24 from Table 204) indicating that this is a Type-1 record consisting of header information. 

25 The second child element, <ansi-nist:ContentRecordCount>, shall be the sum of the Type-2 

26 through Type-99 logical records contained in this exchange package. This is also a count of the 

27 number of occurrences of the third child element <ansi-nist:ContentRecordSummary>. 

28 The third child element, <ansi-nist:ContentRecordSummary>, is a complex element each 

29 occurrence of which relates to a single Type-2 through Type-99 logical record contained in the 

30 package. Two child elements shall comprise each occurrence of <ansi31 nist:ContentRecordSummary>. The first child element, <ansi-nist:ImageReferenceIdentification> 

32 shall be the IDC associated with the logical record. The IDC shall be a positive integer equal to 

33 or greater than zero. The second child element, <ansi-nist:RecordCategoryCode>, shall be the 

34 record identifier character(s) chosen from Table 204 that identifies the record type. The complex 

35 element <ansi-nist:ContentRecordSummary> shall be repeated once for every record in the 

36 exchange package except record Type-1. 

37 Complex element <ansi-nist:ImageReferenceIdentification> shall have the simple element 

38 <nc:IdentificationID>, which will contain the IDC datum. 

39 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

31 
 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:TransactionContentSummary>

2 <ansi-nist:ContentFirstRecordCategoryCode>1 

3 </ansi-nist:ContentFirstRecordCategoryCode>

4 <ansi-nist:ContentRecordCount>2</ansinist:ContentRecordCount> 

6 <ansi-nist:ContentRecordSummary>

7 <ansi-nist:ImageReferenceIdentification>

8 <nc:IdentificationID>00<nc:IdentificationID> 

9 </ansi-nist:ImageReferenceIdentification>

<ansi-nist:RecordCategoryCode>2</ansi11 nist:RecordCategoryCode>

12 </ansi-nist:ContentRecordSummary>

13 <ansi-nist:ContentRecordSummary>

14 <ansi-nist:ImageReferenceIdentification>

<nc:IdentificationID>01<nc:IdentificationID> 

16 </ansi-nist:ImageReferenceIdentification>

17 <ansi-nist:RecordCategoryCode>15</ansi18 nist:RecordCategoryCode>

19 </ansi-nist:ContentRecordSummary>

</ansi-nist: TransactionContentSummary >

21 

22 209.1.3.14 Element <ansi-nist:TransactionCharacterSetDirectory> 

23 Cross reference: Part-1 Section 9.1.15 Field 1.015: Directory of character sets (DCS) 

24 This optional complex element contains information about a single character set other than 7-bit 

ASCII that may appear within this packag. Multiple occurrences of this element may be used to 

26 represent a directory or list of character sets other than 7-bit ASCII that may appear. 

27 This element shall contain three child elements. The first information item, <ansi28 nist:CharacterSetCommonNameCode> shall be the common name for the character set 

29 associated with an index number from Table 208. (Table 208 is the same as Table 9 in Part 1.) 

The second information item, <ansi-nist:CharacterSetIndexCode>, is the three-character identifier 

31 for the character set index number that references an associated character set throughout the 

32 transaction exchange package. The optional third information item, <ansi33 nist:CharacterSetVersionIdentification>, is the specific version of the character set used. 

34 In the case of the use of UTF-8, the third optional information item can be used to hold the 

specific version of the character set used with UTF-8, so that the display terminal can be switched 

36 to the correct font family. Table 208 lists the reserved named character sets and their associated 

37 3-character index numbers. 

38 The complex element <ansi-nist:TransactionCharacterSetDirectory> may appear multiple times, 

39 once for each character set other than 7-bit ASCII that may appear within this package. 

Complex element <ansi-nist:CharacterSetVersionIdentification> shall have the simple element 

41 <nc:IdentificationID>, which will contain the version datum. 

42 

32 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 208 Directory of character sets 

Character 

set index 

Character 

set name 

Description 

000 ASCII 7-bit English (Default) 

001 ASCII 8-bit Latin 

002 UNICODE 16-bit 

003 UTF-8 8-bit 

004-127 ------------- Reserved for ANSI/NIST future use 

128-999 ------------- User-defined character sets 

2 

3 <ansi-nist:TransactionCharacterSetDirectory>

4 <ansi-nist:CharacterSetCommonNameCode>UNICODE 

5 </ansi-nist:CharacterSetCommonNameCode>

6 <ansi-nist:CharacterSetIndexCode>002 

7 </ansi-nist:CharacterSetIndexCode>

8 <ansi-nist:CharacterSetVersionIdentification> 

9 <nc:IdentificationID>000<nc:IdentificationID> 

10 </ansi-nist:CharacterSetVersionIdentification>

11 </ansi-nist:TransactionCharacterSetDirectory> 

12 

13 209.2 End of transaction information record Type-1 

14 The Type-1 logical record shall end with the XML tag </itl:PackageInformationRecord>. 

15 210 Type-2 user-defined descriptive text record 

16 Type-2 logical records shall contain textual information relating to the subject of the exchange 

17 package and shall be represented in an ASCII format. This record may include such information 

18 as the state or FBI numbers, physical characteristics, demographic data, and the subject’s 

19 criminal history. Every exchange package usually contains one or more Type-2 records which is 

20 dependent upon the entry in the <ansi-nist:TransactionCategoryCode> element (Part-1 Type-of21 Transaction, field 1.004, TOT). Table 209 lists the contents of the records. (This table has no 

22 equivalent in Part 1.) 

23 210.1 XML elements for Type-2 logical records 

24 Type-2 records shall be contained within this complex element: 

25 <itl:PackageDescriptiveTextRecord> 

26 [. . . Type 02 Record Content . . .] 

27 </itl:PackageDescriptiveTextRecord> 

33 
 

1 The first two data elements of the Type-2 record are mandatory, ordered, and defined by this 

2 standard. The remaining content of the record(s) shall conform to the format, content, and 

3 requirements of the subscribed Domain Name (DOM), <ansi-nist:TransactionDomain> used by 

4 the agency to which the exchange package is being sent. 

5 

6 Table 209 Type-2 user-defined descriptive text record 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

LEN 2.001 0

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 2.002 <ansi-nist:ImageReferenceIdentification> 1 1

O 2.003 

and 

higher 

<itl:UserDefinedDescriptiveText> 0 1

O <ansi-nist:DomainDefinedDescriptiveText> 0 1

O <ansi-nist:OtherDescriptiveText> 0 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

7 

8 210.1.1 Record length 

9 Cross reference: Part-1 Section 10.1.1 Field 2.001: Logical record length (LEN) 

10 There is no corresponding Part 2 XML element. 

11 210.1.2 Element <ansi-nist:RecordCategoryCode> 

12 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

13 record type. For the Type-2 record, it shall contain a value of 02. 

14 <ansi-nist:RecordCategoryCode>02</ansi15 nist:RecordCategoryCode> 

16 210.1.3 Element <ansi-nist:ImageReferenceIdentification> 

17 Cross reference: Part-1 Section 10.1.2 Field 2.002: Image designation character (IDC) 

18 This mandatory complex element shall be used to identify the user-defined text data contained in 

19 the record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

20 found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

21 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

22 <nc:IdentificationID>, which shall contain the image reference identification datum. 

23 

34 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:ImageReferenceIdentification>

2 <nc:IdentificationID>00</nc:IdentificationID>

3 </ansi-nist:ImageReferenceIdentification>

4 

210.1.4 Element <itl:UserDefinedDescriptiveText> 

6 Cross reference: Part-1 Section 10.1.3 Fields 2.003 and above: User-defined fields 

7 This is a optional complex element. The user-defined content elements are nested within, as 

8 described in the subsections below. 

9 <itl:UserDefinedDescriptiveText> 

[. . . Domain and other descriptive elements . . .] 

11 </itl:UserDefinedDescriptiveText> 

12 210.1.4.1 Element <itl:DomainDefinedDescriptiveText> 

13 This element shall only contain content defined by the Domain owner specified in the Type-1 

14 record element <ansi-nist:TransactionDomain>. Individual XML elements, required for given 

transaction types, including tag names and content, shall conform to the specifications set forth 

16 by the agency to whom the exchange package is being sent. Each user-defined XML element 

17 used in the Type-2 record and its format shall conform to the requirements contained in Section 

18 208.2.2. 

19 Complex element <itl:DomainDefinedDescriptiveText> is abstract, and as such is unusable by 

itself. Implementers should define, in an extension schema, a substitution element containing 

21 user-defined child elements from the user’s domain. 

22 A substitution element should be defined in a user’s extension schema similar to this: 

23 <xsd:element name="DomainDefinedDescriptiveText"

24 substitutionGroup="itl:DomainDefinedDescriptiveText"

type="user26 domain:DomainDefinedDescriptiveTextType"/>

27 

28 <xsd:complexType

29 name="DomainDefinedDescriptiveTextType">

<xsd:complexContent>

31 <xsd:extension base="s:ComplexObjectType">

32 <xsd:sequence>

33 <xsd:element ref="user-domain:OneField"/>

34 <xsd:element ref="user-domain:TwoField”"/>

</xsd:sequence>

36 </xsd:extension>

37 </xsd:complexContent>

38 </xsd:complexType> 

39 The element would then appear in an instance document like this: 

35 
 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <user-domain:DomainDefinedDescriptiveText>

2 <user-domain:OneField>Text</user-domain:OneField> 

3 <user-domain:TwoField>Text</user-domain:TwoField> 

4 </user-domain:DomainDefinedDescriptiveText> 

210.1.4.2Element <itl:OtherDescriptiveText> 

6 This element shall contain additional content not defined by a Domain owner, but necessary for 

7 information exchange between certain parties. Individual XML elements, required for given 

8 transaction types, including tag names and content, shall conform to the specifications set forth 

9 by the agency to whom the exchange package is being sent. Each user-defined XML element 

used in the Type-2 record and its format shall conform to the requirements contained in Section 

11 208.2.2. 

12 Complex element <itl:OtherDescriptiveText> is abstract, and as such is unusable by itself. 

13 Implementers should define, in an extension schema, a substitution element containing user14 defined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

16 <xsd:element name="OtherDescriptiveText"

17 substitutionGroup="itl:OtherDescriptiveText"

18 type="user-domain:OtherDescriptiveTextType"/>

19 

<xsd:complexType name="OtherDescriptiveTextType">

21 <xsd:complexContent>

22 <xsd:extension base="s:ComplexObjectType">

23 <xsd:sequence>

24 <xsd:element ref="user-domain:OneField"/>

<xsd:element ref="user-domain:TwoField”"/>

26 </xsd:sequence>

27 </xsd:extension>

28 </xsd:complexContent>

29 </xsd:complexType> 

The element would then appear in an instance document like this: 

31 <user-domain:OtherDescriptiveText>

32 <user-domain:OneField>Text</user-domain:OneField> 

33 <user-domain:TwoField>Text</user-domain:TwoField> 

34 </user-domain:OtherDescriptiveText> 

210.2 End of Type-2 user-defined descriptive text record 

36 The Type-2 logical record shall end with the XML tag </itl:PackageDescriptiveTextRecord>. 

37 210.3 Additional user-defined descriptive text records 

38 Additional Type-2 records may be included in the exchange package. For each additional user39 defined descriptive text record present, the <ansi-nist:RecordCategoryCode> and <ansinist:ImageReferenceIdentification> elements will be required together with additional Type-2 

41 content needed. 

36 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 211 Type-3 through Type-6 fingerprint image records 

2 211.1 General 

3 As discussed in Section 208.1.3, the Type-3 through Type-6 logical records are based on the use 

4 of a captured fingerprint image obtained using a scanning resolution that is at least as great as 

5 the minimal scanning resolution of 19.69 ppmm (500 ppi). The records differ from each other 

6 based on the properties of the transmitted image - data type (grayscale or binary) and resolution 

7 (scanning resolution or half-resolution). 

8 All four of the logical records use the same XML element structure for the record and exchange of 

9 data. For this Part-2 version of the Standard, all data are represented as ASCII data. The data 

10 values are not required to be fixed length. The order in which the XML elements must appear is 

11 defined in the subsections that follow. Table 210 lists the contents of the records. 

12 211.2 Types 3-6 logical record XML elements 

13 The following descriptions for each element in Table 210 are applicable to logical record types 3-

14 6. 

15 The Type-3 through Type-6 records shall be contained within this complex element: 

16 <itl:PackageImageRecord> 

17 [. . . Type 03 – 06 Record Content . . .] 

18 </itl:PackageImageRecord> 

19 211.2.1 Record length 

20 Cross reference: Part-1 Section 11.2.1: Logical record length (LEN) 

21 There is no corresponding Part 2 XML element. 

22 211.2.2 Element <ansi-nist:RecordCategoryCode> 

23 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

24 record type. For the Type-3 through Type-6 records, it shall contain a value of 03, 04, 05, or 06 

25 respectively. 

26 <ansi-nist:RecordCategoryCode>03</ansi27 nist:RecordCategoryCode> 

28 211.2.3 Element <ansi-nist:ImageReferenceIdentification> 

29 Cross reference: Part-1 Section 11.2.2: Image designation character (IDC) 

30 This mandatory complex element shall be used to identify the image data contained in the record. 

31 The content of this element shall match the <ansi-nist:ImageReferenceIdentification> found in the 

32 <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

37 
 

Part 1 Cond Part 1 Part 2 XML Element Name Occur count 

Ident code Field 

Number 

 min Max 

LEN 1 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 2 <ansi-nist:ImageReferenceIdentification> 1 1

M <ansi-nist:FingerprintImage> 1 1 

image M <nc:BinaryBase64Object> 1 1

data 

M <ansi-nist:ImageCaptureDetail> 1 1

ISR M <ansi-nist:CaptureResolutionCode> 1 1 

CGA/ M <ansi-nist:ImageCompressionAlgorithmCode> 1 1 

BCA 

HLL M <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

VLL M <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1 

M <ansi-nist:FingerprintImagePosition> 1 1

FGP M <ansi-nist:FingerPositionCode> 1 6 

IMP M <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 1 1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

2 <nc:IdentificationID>, which shall contain the image reference identification datum. 

3 <ansi-nist:ImageReferenceIdentification> 

4 <nc:IdentificationID>01</nc:IdentificationID> 

5 </ansi-nist:ImageReferenceIdentification> 

6 

7 Table 210 Type 3-6 record layout 

8 

9 211.2.4 Element <ansi-nist:FingerprintImage> 

10 This is a mandatory complex element. All of the remaining elements in the Type-13 record are 

11 nested within, as described in the subsections below. 

12 <ansi-nist:FingerprintImage> 

13 [. . . Image elements . . .] 

14 </ansi-nist:FingerprintImage> 

38 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 211.2.4.1 Element <nc:BinaryBase64Object> 

2 Cross reference: Part-1 Section 11.2.9: Image data 

3 This mandatory element shall contain the image data. Each pixel of the uncompressed grayscale 

4 image shall be quantized to eight bits (256 gray levels) contained in a single byte. For the 

5 exchange of an uncompressed binary image, eight pixels shall be left justified and packed into a 

6 single unsigned byte. The most significant bit of the byte shall be the first of the eight pixels 

7 scanned. If compression is used, the pixel data shall be compressed in accordance with the 

8 compression technique specified in the <ansi-nist:ImageCompressionAlgorithmCode> element 

9 (CGA / BCA). 

10 The image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

11 <nc:BinaryBase64Object>base64 data 

12 </nc:BinaryBase64Object> 

13 211.2.4.2 Element <ansi-nist:ImageCaptureDetail> 

14 This mandatory complex element contains the single child element described in the subsection 

15 below. 

16 <ansi-nist:ImageCaptureDetail> 

17 [. . . Image capture elements . . .] 

18 </ansi-nist:ImageCaptureDetail> 

19 211.2.4.2.1 Element <ansi-nist:CaptureResolutionCode> 

20 Cross reference: Part-1 Section 11.2.5: Image scanning resolution (ISR) 

21 This element is mandatory. 

22 • For Type-3 or Type-5 logical records, it shall contain the ASCII character “0” if half the 

23 minimum scanning resolution is used and a “1” if half the native scanning resolution is used; 

24 • For Type-4 or Type-6 logical records, it shall contain the ASCII character “0” if the minimum 

25 scanning resolution is used and a “1” if the native scanning resolution is used. 

26 

27 See Section 206.2 where it is stated that the preferred transmitting resolution shall be the same 

28 as the minimum scanning resolution. 

29 <ansi-nist:CaptureResolutionCode>1</ansi30 nist:CaptureResolutionCode> 

31 211.2.4.3 Element <ansi-nist:ImageCompressionAlgorithmCode> 

32 Cross reference: Part-1 Section 11.2.8: Compression algorithm (GCA / BCA) 

33 This element is mandatory. It shall be used to specify the type of compression algorithm used (if 

34 any). The ASCII character “0” denotes no compression. Otherwise, the contents of this byte 

35 shall be the ASCII representation of the number allocated to the particular compression technique 

36 used by the interchange parties. The specific code for each algorithm can be found in Table 201 

39 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 or Table 202 or from the domain registrar who will maintain a registry relating these numbers to 

2 the compression algorithms. 

3 • For the Type-3 logical record, there is no recommendation for a commonly used grayscale 

4 compression algorithm; 

• For the Type-4 logical record, the Wavelet Scalar Quantization (WSQ), or the JPEG 10918 

6 standard alogithms are recommended for compressing the high-resolution grayscale data; 

7 For Type-5 or Type 6 logical records, the Facsimile ANSI/EIA 538-1988 algorithm is 

8 recommended for the lossless compression and decompression of binary fingerprint images. 

9 <ansi-nist:ImageCompressionAlgorithmCode>0 

</ansi-nist:ImageCompressionAlgorithmCode> 

11 211.2.4.4 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

12 Cross reference: Part-1 Section 11.2.6: Horizontal line length (HLL) 

13 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

14 the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

16 </ansi17 nist:ImageHorizontalLineLengthPixelQuantity> 

18 211.2.4.5 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

19 Cross reference: Part-1 Section 11.2.7: Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

21 image. 

22 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

23 </ansi-nist:ImageVerticalLineLengthPixelQuantity>

24 

211.2.4.6Element <ansi-nist:FingerprintImagePosition> 

26 Cross reference: Part-1 Section 11.2.4: Finger position (FGP) 

27 This mandatory complex element contains the child element(s) described in the subsection 

28 below. This complex shall contain possible finger positions for the image. 

29 <ansi-nist:FingerprintImagePosition> 

[. . . Finger position code element(s) . . .] 

31 </ansi-nist:FingerprintImagePosition> 

32 211.2.4.6.1 Element <ansi-nist:FingerPositionCode> 

33 Cross reference: Part-1 Section 11.2.4: Finger position (FGP) 

34 At least one occurrence of this element is mandatory. The first occurrence shall correspond to 

the known or most probable finger position. Following the first occurrence of <ansi40 
 

 

 

 

 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 nist:FingerPositionCode>, up to five additional finger positions may be referenced by repeating 

2 occurrences of <ansi-nist:FingerPositionCode>. Each occurrence of this element shall contain 

3 one possible finger position. The decimal code number corresponding to the finger position shall 

4 be taken from Table 212 (only finger numbers 0-14 apply to Types 3-6) and entered as an ASCII 

number. Table 212 also lists the maximum image width and height dimensions for each of the 

6 finger positions. (Table 212 is the same as Table 12 in Part 1.) 

7 The code “0”, for “Unknown Finger”, shall be used to reference every finger position from one 

8 through ten. 

9 For compatibility with the Part-1 version of the standard, the ASCII value “255” is allowable, but 

not required. This value was a filler for unused finger position elements. No more than six 

11 occurrences of this element are permitted. 

12 <ansi-nist:FingerPositionCode>12</ansi13 nist:FingerPositionCode>

14 <ansi-nist:FingerPositionCode>11</ansinist:FingerPositionCode>

16 <ansi-nist:FingerPositionCode>255</ansi17 nist:FingerPositionCode>

18 <ansi-nist:FingerPositionCode>255</ansi19 nist:FingerPositionCode>

<ansi-nist:FingerPositionCode>255</ansi21 nist:FingerPositionCode>

22 <ansi-nist:FingerPositionCode>255</ansi23 nist:FingerPositionCode> 

24 211.2.4.7 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

Cross reference: Part-1 Section 11.2.3: Impression type (IMP) 

26 This element is mandatory. The code selected from Table 211, describing the manner by which 

27 the fingerprint image information was obtained, shall be entered in this element. (Table 211 is the 

28 same as Table 11 in Part 1.) 

29 <ansinist:FingerprintImageImpressionCaptureCategoryCode>1 

31 </ansi32 nist:FingerprintImageImpressionCaptureCategoryCode>

33 

34 211.3 End of fixed-resolution fingerprint image record 

Type-3 through Type-6 logical records shall end with the XML tag </itl:PackageImageRecord>. 

36 211.4 Additional fixed-resolution image records 

37 Typically, for each of these logical record types, there may be up to thirteen additional images 

38 contained within the exchange package. For each additional image, a logical record is required. 

39 

41 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 211 Finger & palm impression types 

Description Code 

Live-scan plain 0 

Live-scan rolled 1 

Nonlive-scan plain 2 

Nonlive-scan rolled 3 

Latent impression 4 

Latent tracing 5 

Latent photo 6 

Latent lift 7 

Live-scan vertical swipe 8 

Live-scan palm 10 

Nonlive-scan palm 11 

Latent palm impression 12 

Latent palm tracing 13 

Latent palm photo 14 

Latent palm lift 15 

Live-scan optical contact plain 20 

Live-scan optical contact rolled 21 

Live-scan non-optical contact plain 22 

Live-scan non-optical contact rolled 23 

Live-scan optical contactless plain 24 

Live-scan optical contactless rolled 25 

Live-scan non-optical contactless plain 26 

Live-scan non-optical contactless rolled 27 

Other 28 

Unknown 29 

2 Note: Table 211 is also used to describe the manner by which palm image 

3 information was obtained. 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

42 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 

2 Table 212 Finger position code & maximum image dimensions 

Finger position Finger 

code 

Width 

(mm) (in) 

Length 

(mm) (in) 

Unknown 0 40.6 1.6 38.1 1.5 

Right thumb 1 40.6 1.6 38.1 1.5 

Right index finger 2 40.6 1.6 38.1 1.5 

Right middle finger 3 40.6 1.6 38.1 1.5 

Right ring finger 4 40.6 1.6 38.1 1.5 

Right little finger 5 40.6 1.6 38.1 1.5 

Left thumb 6 40.6 1.6 38.1 1.5 

Left index finger 7 40.6 1.6 38.1 1.5 

Left middle finger 8 40.6 1.6 38.1 1.5 

Left ring finger 9 40.6 1.6 38.1 1.5 

Left little finger 10 40.6 1.6 38.1 1.5 

Plain right thumb 11 25.4 1.0 50.8 2.0 

Plain left thumb 12 25.4 1.0 50.8 2.0 

Plain right four fingers 13 81.3 3.2 76.2 3.0 

Plain left four fingers 14 81.3 3.2 76.2 3.0 

Left & right thumbs 15 81.3 3.2 76.2 3.0 

EJI or tip 19 114.3 4.5 127.0 5.0 

3 Note: Finger codes 15 and 19 apply to tagged-field fingerprint image records. 

4 

5 212 Type-7 user-defined image record 

6 Type-7 logical records shall contain user-defined image information relating to the exchange 

7 package submitted for processing. This record type was originally defined to handle 

8 miscellaneous images such as those pertaining to mugshots, latent prints, palm prints, wrists, 

9 toes, soles, etc. that were not addressed elsewhere in the standard. However, it is not intended 

10 that the use of the Type-7 record is restricted by the existence of other record types in this 

11 standard. 

12 Type-7 records are still commonly used for the exchange of latent fingerprints. But since its 

13 creation, other record types have also been formally defined and are used by this standard to 

14 handle mugshots (Type-10), latent fingerprint images (Type-13), variable-resolution fingerprint 

15 images (Type-14), palm print images (Type-15), and other user-defined image records (Type-16). 

16 These images shall consist of scanned pixels that may be either binary or grayscale output. Each 

17 grayscale pixel value shall be expressed as an unsigned byte. A value of “0” shall be used to 

18 define a black pixel and an unsigned value of “255” shall be used to define a white pixel. For 

43 
 

Part 1 

Ident 

Cond 

code 

Part 2 XML Element Name Occur count 

 min Max 

LEN 0

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M <ansi-nist:ImageReferenceIdentification> 1 1

O <itl:RecordImage> 0 1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 binary pixels, a value of “0” shall represent a white pixel and a value of “1” shall represent a black 

2 pixel. If compression is used, the algorithm shall be the same as that specified for Type-3 

3 through Type-6 logical records. Table 213 lists the contents of the records. (This table has no 

4 equivalent in Part 1.) 

5 212.1 XML elements for Type-7 logical records 

6 Type-7 records shall be contained within this complex element: 

7 <itl:PackageImageRecord> 

8 [. . . Type 07 Record Content . . .] 

9 </itl:PackageImageRecord> 

10 The XML Part-2 version of the Type-7 logical record shall be composed completely of ASCII data. 

11 The first two data elements of the Type-7 record are defined by this Standard. Remaining record 

12 content shall conform to the requirements set forth by the agency receiving the exchange 

13 package. 

14 

15 Table 213 Type-7 user-defined image record 

16 

17 212.1.1 Record length 

18 Cross reference: Part-1 Section 12.1.1: Logical record length (LEN) 

19 There is no corresponding Part 2 XML element. 

20 212.1.2 Element <ansi-nist:RecordCategoryCode> 

21 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

22 record type. For the Type-7 record, it shall contain a value of 07. 

23 <ansi-nist:RecordCategoryCode>07</ansi24 nist:RecordCategoryCode> 

25 

26 

44 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 212.1.3 Element <ansi-nist:ImageReferenceIdentification> 

2 Cross reference: Part-1 Section 12.1.2: Image designation character (IDC) 

3 This mandatory complex element shall be used to identify the image data contained in the record. 

4 The content of this element shall match the <ansi-nist:ImageReferenceIdentification> found in the 

<ansi-nist:TransactionContentSummary> element of the Type-1 record. 

6 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

7 <nc:IdentificationID>, which shall contain the image reference identification datum. 

8 <ansi-nist:ImageReferenceIdentification>

9 <nc:IdentificationID>05</nc:IdentificationID>

</ansi-nist:ImageReferenceIdentification>

11 

12 212.1.4 Element <itl:RecordImage> 

13 Cross reference: Part-1 Section 12.1.3: User-defined fields for Type-7 logical record 

14 The remaining content of the Type-7 logical record shall be user-defined. Individual elements 

required for a given exchange package, such as element description, size, and content shall 

16 conform to the specifications set forth by the agency to whom the package is being sent. 

17 Complex element <itl:RecordImage> is abstract, and as such is unusable by itself. Implementers 

18 should define, in an extension schema, a substitution element containing user-defined child 

19 elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

21 <xsd:element name="UserDefinedImageRecord"

22 substitutionGroup="itl:RecordImage"

23 type="user-domain:UserDefinedImageRecordType"/>

24 

<xsd:complexType name="UserDefinedImageRecordType">

26 <xsd:complexContent>

27 <xsd:extension base="s:ComplexObjectType">

28 <xsd:sequence>

29 <xsd:element ref="user-domain:OneField"/>

<xsd:element ref="user-domain:TwoField”"/>

31 </xsd:sequence>

32 </xsd:extension>

33 </xsd:complexContent>

34 </xsd:complexType> 

The element would then appear in an instance document like this: 

36 <user-domain:UserDefinedImageRecord>

37 <user-domain:OneField>Text</user-domain:OneField> 

38 <user-domain:TwoField>Text</user-domain:TwoField> 

39 </user-domain:UserDefinedImageRecord> 

45 
 

 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 212.2 End of Type-7 user-defined image record 

2 The Type-7 logical record shall end with the XML tag </itl:PackageImageRecord>. 

3 212.3 Additional user-defined descriptive text records 

4 Additional images may be described within the exchange package. For each additional image, a 

Type-7 logical record is required. 

6 213 Type-8 signature image record 

7 Type-8 logical records shall contain either scanned or vectored signature data. Each Type-8 

8 record shall cover an area of up to 1000 mm2

. 

9 If scanned, the resolution shall be the minimum scanning resolution or the native scanning 

resolution, and the scan sequence shall be left to right and top to bottom. The scanned data shall 

11 be a binary representation quantized to two levels. 

12 If vectored signature data is present, it shall be expressed as a series of numbers. 

13 213.1 XML elements for the Type-8 logical record 

14 When one or two Type-8 logical records are used, entries shall be provided in XML elements for 

each signature record. Table 214 provides a list of the elements for the Type-8 logical record. 

16 Elements containing entries in the “IMG” column are only applicable to that image type. An entry 

17 of “IMG” applies to a scanned signature image, and an entry of "VEC" applies to vectored 

18 signature data. 

19 The Type-8 record shall be contained within this complex element: 

<itl:PackageImageRecord> 

21 [. . . Type 8 Record Content . . .] 

22 </itl:PackageImageRecord> 

23 In the subsections that follow, text in bold between opening and closing tags is informative and 

24 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansinist:RecordCategoryCode> for example). 

26 213.1.1 Record length 

27 Cross reference: Part-1 Section 13.1.1: Logical record length (LEN) 

28 There is no corresponding Part 2 XML element. 

29 

31 

46 
 

1 Table 214 Type-8 record layout 

Part 1 Cond Part 2 XML Element Name IMG Occur count 

Ident code 

 min Max 

LEN 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M <ansi-nist:ImageReferenceIdentification> 1 1

M <itl:SignatureImage> 1 1 

DATA *M <nc:BinaryBase64Object> IMG *1 1

M <ansi-nist:ImageCaptureDetail> 1 1

ISR M <ansi-nist:CaptureResolutionCode> 1 1

HLL M <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1

VLL M <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1

DATA *M <ansi-nist:SignatureImageVectorRepresentation> VEC *1 1 

*M <ansi-nist:SignatureImageVector> VEC 2 Unlim 

SRT M <ansi-nist:SignatureRepresentationCode> 1 1

SIG M <ansi-nist:SignatureCategoryCode> 1 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

2 * Mandatory (or optional) for a particular image type 

3 213.1.2 Element <ansi-nist:RecordCategoryCode> 

4 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

5 record type. For the Type-8 record, it shall contain a value of 08. 

6 <ansi-nist:RecordCategoryCode>08</ansi7 nist:RecordCategoryCode> 

8 213.1.3 Element <ansi-nist:ImageReferenceIdentification> 

9 Cross reference: Part-1 Section 13.1.2: Image designation character (IDC) 

10 This mandatory complex element shall be used to identify the image data contained in the record. 

11 The content of this element shall match the <ansi-nist:ImageReferenceIdentification> found in the 

12 <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

13 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

14 <nc:IdentificationID>, which shall contain the image reference identification datum. 

15 <ansi-nist:ImageReferenceIdentification>

16 <nc:IdentificationID>6</nc:IdentificationID>

17 </ansi-nist:ImageReferenceIdentification> 

47 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 213.1.4 Element <ansi-nist:SignatureImage> 

2 All of the remaining elements in the Type-8 record are nested within, as described in the 

3 subsections below. 

4 <ansi-nist:SignatureImage> 

[. . . Signature image, or vectored data elements . . .] 

6 </ansi-nist:SignatureImage> 

7 213.1.4.1 Element <nc:BinaryBase64Object> 

8 Cross reference: Part-1 Section 13.1.8.1 and 13.1.8.2: Signature image data (DATA), scanned 

9 images 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element is “0” or “1”, this element is 

11 mandatory. This element shall not appear in a record if <ansi12 nist:SignatureRepresentationCode> (SRT) element is “2”. 

13 This element shall contain all of data from a scanned signature image. The binary image data 

14 shall be converted to ASCII characters using the Base64 encoding algorithm. 

Uncompressed scanned image data 

16 If the <ansi-nist:SignatureRepresentationCode> (SRT) contains the value “0”, then this element 

17 shall contain the uncompressed scanned binary image data for the signature. In uncompressed 

18 mode, the data shall be packed at eight pixels per byte. 

19 Compressed scanned image data 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element contains the value “1”, then this 

21 element shall contain the scanned binary image data for the signature in compressed form using 

22 the ANSI/EIA-538-1988 facsimile compression algorithm. 

23 <nc:BinaryBase64Object>base64 

24 data</nc:BinaryBase64Object> 

213.1.4.2 Element <ansi-nist:ImageCaptureDetail> 

26 This mandatory complex element contains the single child element described in the subsection 

27 below. 

28 <ansi-nist:ImageCaptureDetail> 

29 [. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

31 

48 
 

 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 213.1.4.2.1 Element <ansi-nist:CaptureResolutionCode> 

2 Cross reference: Part-1 Section 13.1.5: Image scanning resolution (ISR) 

3 This element is mandatory. It shall contain an ASCII “0” if the minimum scanning resolution is 

4 used and an ASCII “1” if the native scanning resolution is used. An ASCII value of “0” shall also 

be used if the image is vector data. 

6 <ansi-nist:CaptureResolutionCode>1</ansi7 nist:CaptureResolutionCode> 

8 213.1.4.3 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

9 Cross reference: Part-1 Section 13.1.6: Horizontal line length (HLL) 

This element is mandatory. For scanned signature data, this element shall be used to specify the 

11 number of pixels contained on a single horizontal line of the transmitted signature image. For 

12 vectored signature data, this element shall contain the ASCII value of “00”. 

13 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

14 </ansinist:ImageHorizontalLineLengthPixelQuantity> 

16 213.1.4.4 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

17 Cross reference: Part-1 Section 13.1.7: Vertical line length (VLL) 

18 This element is mandatory. For scanned signature data, this element shall be used to specify the 

19 number of horizontal lines contained in the transmitted signature image. For vectored signature 

data, this element shall contain the ASCII value of “00”. 

21 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

22 </ansi-nist:ImageVerticalLineLengthPixelQuantity>

23 

24 213.1.4.5 Element <ansi-nist:SignatureImageVectorRepresentation> 

Cross reference: Part-1 Section 13.1.8.3: Signature image data (DATA), Vectored image data 

26 If the <ansi-nist:SignatureRepresentationCode> (SRT) element is “2”, this element is mandatory. 

27 This element shall not appear in a record if <ansi-nist:SignatureRepresentationCode> (SRT) 

28 element is “0” or “1”. 

29 Vectored image data 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element contains the value of “2”, then this 

31 complex parent element shall contain a list of vector elements describing the pen position and 

32 pen pressure of line segments within the signature. Each vector element shall be contained in 

33 the complex child element <ansi-nist:SignatureImageVector> described in the subsection below. 

34 The complex parent element <ansi-nist:SignatureImageVectorRepresentation> contains all the 

35 occurrences of the child element: 

36 

49 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:SignatureImageVectorRepresentation> 

2 [. . . Vector elements . . .] 

3 </ansi-nist:SignatureImageVectorRepresentation> 

4 213.1.4.5.1 Element <ansi-nist:SignatureImageVector> 

Each occurrence of <ansi-nist:SignatureImageVector> shall contain information describing the 

6 coordinates of the end point of a vector, and a pen pressure setting. 

7 A number between “0” and “255” contained in the <ansi-nist:VectorPenPressureValue> element 

8 shall represent the pen pressure. This shall be a constant pressure until the next vector becomes 

9 active. Values shall be represented as ASCII numeric characters. A pressure value of “0” shall 

represent a "pen-up" (or no pressure) condition. The pressure value of “1” shall represent the 

11 least recordable pressure for a particular device, while the value “254” shall represent the 

12 maximum recordable pressure for that device. To denote the end of the vector list the value 

13 “255” shall be inserted in the <ansi-nist:VectorPenPressureValue> element. 

14 The <ansi-nist:VectorPositionVerticalCoordinateValue> shall hold the Y coordinate of the pen 

position. The <ansi-nist:VectorPositionHorizontalCoordinateValue> shall hold the X coordinate of 

16 the pen position. Both the X and Y coordinates shall be expressed in units of .0254 mm (.001 

17 inches) referenced from the bottom leftmost corner of the signature. Positive values of X shall 

18 increase from left-to-right and positive values of Y shall increase from bottom-to-top. 

19 The <ansi-nist:SignatureImageVector> element may be repeated as many times as necessary to 

describe a signature image. 

21 <ansi-nist:SignatureImageVector>

22 <ansi-nist:VectorPenPressureValue>254 

23 </ansi-nist:VectorPenPressureValue>

24 <ansinist:VectorPositionVerticalCoordinateValue>0 

26 </ansi27 nist:VectorPositionVerticalCoordinateValue> 

28 <ansi29 nist:VectorPositionHorizontalCoordinateValue>0 

</ansi31 nist:VectorPositionHorizontalCoordinateValue> 

32 </ansi-nist:SignatureImageVector> 

33 213.1.4.6 Element <ansi-nist:SignatureRepresentationCode> 

34 Cross reference: Part-1 Section 13.1.4: Signature representation type (SRT) 

This element is mandatory. Its value shall be an ASCII “0” if the image is scanned and not 

36 compressed, an ASCII “1” if the image is scanned and compressed, and an ASCII “2” if the image 

37 is vector data. 

38 <ansi-nist:SignatureRepresentationCode>0 

39 </ansi-nist:SignatureRepresentationCode> 

50 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 213.1.4.7 Element <ansi-nist:SignatureCategoryCode> 

2 Cross reference: Part-1 Section 1.1.3: Signature Type (SIG) 

3 This element is mandatory. Its value shall be an ASCII “0” for the signature image of the subject, 

4 or an ASCII “1” for the signature image of the official processing the transaction. 

5 <ansi-nist:SignatureCategoryCode>0 

6 </ansi-nist:SignatureCategoryCode> 

7 213.2 End of Type-8 signature image record 

8 The Type-8 logical record shall end with the XML tag </itl:PackageImageRecord>. 

9 213.3 Additional variable-resolution latent image records 

10 One more signature may be described within the file. For an additional signature, a Type-8 

11 logical record is required. 

12 214 Type-9 minutiae data record 

13 Type-9 records shall contain XML elements and ASCII content describing minutiae and related 

14 information encoded from a finger or palm. For a tenprint search transaction, generally there may 

15 be up to ten of these Type-9 records in an exchange package, each of which shall be for a 

16 different finger. There may be up to eight records for palmprint searches - each record 

17 representing a different area on one of the two palms. The Type-9 record shall also be used to 

18 exchange the minutiae information from latent finger or palm images between similar or different 

19 systems. 

20 Minutiae information may be extracted and encoded in any of several different manners 

21 depending on the system that is used to scan an image, extract minutiae, and encode the 

22 minutiae template. This standard defines an abstract XML element called <itl:RecordMinutiae>. 

23 Any number of concrete implementations can be defined to substitute for <itl:RecordMinutiae>. 

24 This standard defines a NIST “Standard format.” The concrete complex element <itl:Minutiae> 

25 substitutes for the abstract <itl:RecordMinutiae> creating a minutiae representation based on the 

26 conventions and parameters described below in Section 214.1. 

27 Additional substitution elements may be defined by vendors to represent minituae differently. 

28 Alternative elements constructed to substitute for <itl:RecordMinutiae> will allow vendors to 

29 encode minutiae data and any additional required characteristic or feature data in accordance 

30 with their own system’s specific hardware and software configuration. The registration of blocks 

31 of substitution elements to specific vendors is controlled by the domain registrar responsible for 

32 the implementation domain. By default this shall be the registrar for the North American Domain. 

33 Table 14 in the Part-1 version of this specification identifies vendors who have Part-1 alternate 

34 representations. None, as of this publication, has a Part-2 XML representation. 

35 214.1 Minutiae and other information descriptors (Standard Format) 

36 214.1.1 Minutiae type identification 

37 This standard defines four identifier characters that are used to describe the minutia type. These 

38 are listed in Table 215. A ridge ending shall be designated Type A. It occurs at the point on a 

51 
 

1 fingerprint or palmprint that a friction ridge begins or ends without splitting into two or more 

2 continuing ridges. The ridge must be longer than it is wide. A bifurcation shall be designated 

3 Type B. It occurs at the point that a ridge divides or splits to form two ridges that continue past 

4 the point of division for a distance that is at least equal to the spacing between adjacent ridges at 

5 the point of bifurcation. A minutia shall be designated Type C, a compound type, if it is either a 

6 trifurcation (a single ridge that splits into three ridges) or a crossover (two ridges that intersect). If 

7 a minutia cannot be clearly categorized as one of the above three types, it shall be designated as 

8 undetermined, Type D. 

9 

10 Table 215 Minutiae types 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Type Description 

A Ridge ending 

B Bifurcation 

C Compound (trifurcation or crossover) 

D Type undetermined 

11 

12 214.1.2 Minutia numbering 

13 Each minutia shall be identified by an index number that is assigned to it. The numbering shall 

14 begin at “1” and be incremented by “1” for as many times as there are minutiae encountered. 

15 This allows each minutia to be uniquely identified. The numbering of the minutiae shall be 

16 unordered. 

17 214.1.3 Minutiae ridge counts 

18 As required, ridge counts shall be determined from each minutia in a fingerprint or palmprint to 

19 certain other neighboring minutiae. When this occurs, ridge counts between designated minutiae 

20 shall be associated with the applicable index numbers so as to ensure maintenance of the proper 

21 relationships. Rules for identifying neighboring minutiae and the method to be used for counting 

22 the intervening ridge crossings is not part of this “standard format”. 

23 214.1.4 Minutiae coordinate system 

24 The relative position of minutiae entered in Type-9 records shall be expressed as positive 

25 integers in units of 0.01 mm (0.00039 in) in a Cartesian coordinate system located in Quadrant 1. 

26 In this coordinate system, values of X increase from left to right and values of Y increase from 

27 bottom to top. 

28 Note (Informative) – This standard follows the practice of placing the origin at the lower left-corner 

29 for describing the location of minutiae. This is in contrast to the placement of the origin in the 

30 upper left-hand corner which is conventionally used for images. 

31 For encoded minutiae from fingerprints, values for both X and Y are equal to or greater than 

32 "0000" and are less than "5000". This range of units converts to 5 cm (1.97”) in both the 

33 horizontal and vertical directions. If the conversion to this coordinate system is from a system 

34 that normally centers the fingerprint image during the registration process, that center position 

52 
 

1 shall be assigned the values X = 2500, Y = 2500. Figure 3 illustrates the defined coordinate 

2 system for a fingerprint using the complex XML element for the “standard format”, <itl:Minutiae>. 

3 For encoded minutiae from a palmprint, values of both X and Y are equal to or greater than 

4 "0000" and are less than "14000" and “21000” respectively. This range of units converts to 14 cm 

5 (5.51”) in the horizontal and 21 cm (8.27”) in the vertical directions. 

6 The relative orientation, Theta, of a ridge ending or a bifurcation shall be expressed as positive 

7 integers in units of degrees from “0” to “359”. Theta is defined as the angle between the 

8 horizontal axis of the coordinate system and the direction that a ridge ending points, assuming 

9 that a ridge ending is analogous to a pointing finger. A ridge ending that is formed by a ridge 

10 lying parallel to the X axis, and ending in the direction of increasing values of X, shall have an 

11 orientation of zero degrees. Counterclockwise rotation of this ridge about the ridge ending shall 

12 cause the value of Theta to increase. A ridge ending pointing due east has a direction of zero 

13 degrees, due north 90 degrees and so forth. No orientation value shall be assigned to an 

14 undetermined or compound type of minutiae; therefore, a value of "000" shall be entered for 

15 Theta in the Type-9 logical record entry. 

16 A bifurcation may be converted to a ridge ending by logical inversion, i.e., transposing the identity 

17 of ridges and valleys. The orientation of a bifurcation is expressed as if this inversion had 

18 occurred. This convention causes no significant change in the orientation of a minutia if it 

19 appears as a ridge ending in one impression of a fingerprint and as a bifurcation in another 

20 impression of the same fingerprint. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Theta = 45 units 

Y = 2500 units 

0 X-coordinate 5000 

X = 2500 units 

Minutia Data 

5000 

Theta 

Units: 

X, Y, = 0.01mm 

Theta = 1° / unit 

Y-coordinate 

21 

22 Figure 3 Minutiae coordinate system 

23 The exact features or characteristics of a minutia that are used to establish its position and 

24 orientation are system dependent and outside the scope of this standard. 

25 

53 
 

1 214.2 XML elements for Type-9 logical record 

2 Type-9 records shall be contained within this complex element: 

3 <itl:PackageMinutiaeRecord> 

4 [. . . Type 9 Record Content . . .] 

5 </itl:PackageMinutiaeRecord> 

6 All XML elements and content of the Type-9 records shall be recorded as ASCII text. No binary 

7 data are defined in the “Standard format” so there is no conversion of binary data required using 

8 Base64 encoding. Vendors who define alternate representations shall create substitute elements 

9 that shall be recorded as ASCII text. The abstract element <itl:RecordMinutiae> is a placeholder 

10 for a specific vendor representation. The concrete element <itl:Minutiae> is a substitute for 

11 <itl:RecordMinutiae> and provides a common or generic manner of encoding minutiae and other 

12 characteristic data. The contents of <itl:Minutiae> are formatted in accordance with the 

13 conventions described above. 

14 Although this logical record type can also be used to accommodate a variety of methods used by 

15 different AFIS vendors for encoding minutiae data according to their particular requirements, each 

16 vendor implementation must appear as a substitute for the abstract element <itl:RecordMinutiae>. 

17 All other structure of the Type-9 record is required including the outer XML element 

18 <itl:PackageMinutiaeRecord>, and its first four elements <ansi-nist:RecordCategoryCode>, 

19 <ansi-nist:ImageReferenceIdentification, <ansi-nist:MinutiaeImpressionCaptureCategoryCode> 

20 and <ansi-nist:MinutiaeFormatNISTStandardIndicator>. None of the content of <itl:Minutiae> is 

21 required to be present in specific vendor implementations. 

22 Within a Type-9 logical record, entries shall be provided in XML elements. Two tables are 

23 presented. (Neither exist in Part 1.) Table 216a is the structure of the Type-9 record for all 

24 implementations, NIST standard and vendor alternatives. Table 216b is the structure of the NIST 

25 Standard representation. For each element of the Type-9 record, a “condition code” is shown as 

26 being mandatory “M” or optional “O”, or not allowed “X”. XML tag name, and occurrence limits 

27 are shown. 

28 In the subsections that follow, text in bold between opening and closing tags is informative and 

29 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi30 nist:RecordCategoryCode> for example). 

31 214.2.1 Record length 

32 Cross reference: Part-1 Section 14.2.1 Field 9.001: Logical record length (LEN) 

33 There is no corresponding Part 2 XML element. 

34 

35 

36 

37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

54 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

LEN 9.001 0

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 9.002 <ansi-nist:ImageReferenceIdentification> 1 1

IMP M 9.003 <ansi-nist:MinutiaeImpressionCaptureCategoryCode> 1 1 

FMT M 9.004 <ansi-nist:MinutiaeFormatNISTStandardIndicator> 1 1

M <itl:RecordMinutiae> ABSTRACT See 

note 

below 

Unlim 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 min Max 

<itl:Minutiae> CONCRETE SUBSTITUTE FOR <itl:RecordMinutiae> 1 1 

MRC M 9.012 <itl:MinutiaeNISTStandard> 1 1

M <itl:MinutiaDetail> 1 Unlim

MIN M 9.010 <ansi-nist:MinutiaeQuantity> 1 1

OFR O 9.005 <ansi-nist:MinutiaeReadingSystem> 0 1

RDG M 9.011 <ansi-nist:MinutiaeRidgeCountIndicator> 1 1

CRP O 9.008 <ansi-nist:MinutiaeFingerCorePosition> FIN 0 Unlim 

CRP X 9.008 < ansi-nist:MinutiaeFingerCorePosition> PAL 0 0 

DLT O 9.009 < ansi-nist:MinutiaeFingerDeltaPosition> FIN 0 Unlim 

DLT X 9.009 < ansi-nist:MinutiaeFingerDeltaPosition> PAL 0 0 

FPC M 9.007 <itl:MinutiaeFingerPatternDetail> FIN 1 Unlim 

FPC X 9.007 <itl:MinutiaeFingerPatternDetail> PAL 0 0 

FGP M 9.006 < ansi-nist:MinutiaeFingerPositionCode> FIN 1 Unlim 

FGP M 9.006 < ansi-nist:MinutiaePalmPositionCode> PAL 1 Unlim 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 216a Type-9 minutiae record (all implementations) 

2 Note: At least one occurrence of a concrete substitute for the abstract element is 

3 required 

4 

5 Table 216b Type-9 NIST Standard minutiae representation 

55 

6 
 

1 214.2.2 Element <ansi-nist:RecordCategoryCode> 

2 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

3 record type. For the Type-9 record, it shall contain a value of 09. 

4 <ansi-nist:RecordCategoryCode>09 

5 </ansi-nist:RecordCategoryCode> 

6 214.2.3 Element <ansi-nist:ImageReferenceIdentification> 

7 Cross reference: Part-1 Section 14.2.2 Field 9.002: Image designation character (IDC) 

8 This mandatory complex element shall be used for the identification and location of the minutiae 

9 data. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> found 

10 in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

11 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

12 <nc:IdentificationID>, which shall contain the reference identification datum. 

13 <ansi-nist:ImageReferenceIdentification>

14 <nc:IdentificationID>00</nc:IdentificationID>

15 </ansi-nist:ImageReferenceIdentification> 

16 214.2.4 Element <ansi-nist:MinutiaeImpressionCaptureCategoryCode> 

17 Cross reference: Part-1 Section 14.2.3 Field 9.003 Impression type (IMP) 

18 This mandatory element shall contain a one- or two-byte ASCII value describing the manner by 

19 which the fingerprint or palmprint image information was obtained. The ASCII value for the 

20 proper code as selected from Table 211 for finger impressions and palm impressions shall be 

21 entered in this element to signify the impression type. 

22 <ansi-nist:MinutiaeImpressionCaptureCategoryCode>4 

23 </ansi24 nist:MinutiaeImpressionCaptureCategoryCode> 

25 214.2.5 Element <ansi-nist:MinutiaeFormatNISTStandardIndicator> 

26 Cross reference: Part-1 Section 14.2.4 Field 9.004 Minutiae format (FMT) 

27 This mandatory element shall contain a value indicating whether the information in the remainder 

28 of the record adheres to the standard format or is a user-defined format. This element shall 

29 contain a value of "true" to indicate that the minutiae are formatted as specified by the standard 

30 Type-9 logical record description using location information and other conventions described 

31 above. A standard Type-9 logical record will substitute <itl:Minutiae> for the abstract element 

32 <itl:RecordMinutiae>. 

33 This element shall contain a value of "false" to indicate that the minutiae are formatted in vendor34 specific or M1-378 terms. More than one vendor representation of the same set of minutiae from 

35 one view of one finger could be present in a single Type 9 record when this element contains a 

36 value of “false”. Multiple blocks of vendor-specific data, which may include content from 

37 <itl:Minutiae>, can occur within a single Type-9 record when this element contains a value of 

38 “false”. Even though information may be encoded in accordance with a specific vendor’s 

39 implementation, all XML elements and content in the Type-9 record must remain as ASCII text. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

56 
 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:MinutiaeFormatNISTStandardIndicator>true 

2 </ansi-nist:MinutiaeFormatNISTStandardIndicator> 

3 214.2.6 Element <itl:RecordMinutiae> 

4 Complex element <itl:RecordMinutiae> is abstract, and as such is unusable by itself. 

Implementers may use the NIST “Standard format” substitution element <ansi-nist:Minutiae> 

6 which is described in the next subsection. Implementers alternatively may define, in an extension 

7 schema, a substitution element containing user-defined child elements from the user’s domain. 

8 Vendor specific substitution elements may be registered with the domain owner specified in the 

9 Type-1 record, element <ansi-nist:TransactionDomain>. 

A substitution element should be defined in a user’s extension schema similar to this: 

11 <xsd:element name="VendorDefinedMinutiae" 

12 substitutionGroup="itl:RecordMinutiae"

13 type="user-domain:VendorDefinedMinutiaeType"/>

14 

<xsd:complexType name="VendorDefinedMinutiaeType">

16 <xsd:complexContent>

17 <xsd:extension base="s:ComplexObjectType">

18 <xsd:sequence>

19 <xsd:element ref="user-domain:OneField"/>

<xsd:element ref="user-domain:TwoField”"/>

21 </xsd:sequence>

22 </xsd:extension>

23 </xsd:complexContent>

24 </xsd:complexType> 

The element would then appear in an instance document like this: 

26 <user-domain:VendorDefinedMinutiae> 

27 <user-domain:OneField>Text</user-domain:OneField> 

28 <user-domain:TwoField>Text</user-domain:TwoField> 

29 </user-domain:VendorDefinedMinutiae> 

214.2.7 Element <itl:Minutiae> 

31 The complex element <itl:Minutiae> has been defined as a concrete substitution for the abstract 

32 element <itl:RecordMinutiae>. It contains the NIST “Standard format” content for representation 

33 of minutiae. All of the elements in the “Standard format” are nested within, as described in the 

34 subsections below. 

<itl:Minutiae> 

36 [. . . NIST “Standard format” minutiae elements . . .] 

37 </itl:Minutiae> 

57 
 

1 214.2.7.1 Element <itl:MinutiaeNISTStandard> 

2 This mandatory complex element contains four child elements described in the subsections 

3 below: <itl:MinutiaDetail>, <ansi-nist:MinutiaeQuantity>, <ansi-nist:MinutiaeReadingSystem>, 

4 and <ansi-nist:MinutiaeRidgeCountIndicator>. 

5 <itl:MinutiaeNISTStandard> 

6 [. . . Minutiae elements . . .] 

7 </itl:MinutiaeNISTStandard> 

8 214.2.7.1.1 Element <itl:MinutiaDetail> 

9 Cross reference: Part-1 Section 14.2.12 Field 9.012: Minutiae and ridge count data (MRC) 

10 At least one occurrence of this complex element is mandatory. The set of occurrences of this 

11 element shall contain all of the individual minutiae and ridge count data associated with the 

12 current fingerprint or palmprint impression. The number of occurrences shall be as many 

13 minutiae stated in the minutiae count in <ansi-nist:MinutiaeQuantity> (MIN). Each occurrence of 

14 <itl:MinutiaDetail> shall be devoted to a single minutia and shall consist of mandatory and 

15 optional child XML elements. 

16 The child elements must appear in the order below. Optional elements may be omitted 

17 altogether. 

18 X coordinate value <ansi-nist:PositionHorizontalCoordinateValue> 

19 There shall be one and only one occurrence of this mandatory element in the <ansi20 nist:MinutiaDetail> complex. For minutiae encoded from fingerprints, the X (horizontal) 

21 coordinate shall be represented by a four-digit ASCII numeric value ranging from “0000” zero 

22 upward. For minutiae encoded from palmprints, the X (horizontal) coordinate shall be 

23 represented by a five-digit ASCII numeric value ranging from “00000” zero upward. 

24 Y coordinate value <ansi-nist:PositionVerticalCoordinateValue> 

25 There shall be one and only one occurrence of this mandatory element in the <ansi26 nist:MinutiaDetail> complex. For minutiae encoded from fingerprints, the Y (vertical) coordinate 

27 shall be represented by a four-digit ASCII numeric value ranging from “0000” zero upward. For 

28 minutiae encoded from palmprints, the Y (vertical) coordinate shall be represented by a five-digit 

29 ASCII numeric value ranging from “00000” zero upward. 

30 Index number <ansi-nist:MinutiaIdentification> 

31 There shall be one and only one occurrence of this mandatory element in the <ansi32 nist:MinutiaDetail> complex. The index number shall be initialized to "1" and incremented by “1” 

33 for each additional minutia in the fingerprint. This index number serves to identify each individual 

34 minutia. Complex element <ansi-nist:MinutiaIdentification> shall have the simple element 

35 <nc:IdentificationID>, which will contain index datum. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

58 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Theta value <ansi-nist:PositionThetaAngleMeasure> 

2 There shall be one and only one occurrence of this mandatory element in the <ansi3 nist:MinutiaDetail> complex. For minutiae encoded from fingerprints and from palmprints, the 

4 Theta value shall be represented by a three-digit ASCII value between 000 and 359. 

Quality measure <ansi-nist:MinutiaQualityValue> 

6 This is an optional quality measure element that if present shall have only one occurrence. 

7 Values shall range from "0" to "63". The value "0" shall indicate a manually encoded minutia. 

8 The value "1" shall indicate that no method of indicating a confidence level is available. Values 

9 between "2" and "63" shall indicate decreasing levels of confidence, with "2" meaning the 

greatest confidence. 

11 Minutia type designation <ansi-nist:MinutiaCategoryCode> 

12 This is an optional minutia type designation element that if present shall have only one 

13 occurrence. This shall be a single alphabetic character as chosen from Table 215. 

14 Ridge count data <ansi-nist:MinutiaRidgeCount> 

This is an optional ridge count data element. This complex element may have a zero to 

16 unbounded number of occurrences. It is a complex element with two children, each of which are 

17 mandatory and shall have only one occurrence. Each occurrence of <ansi18 nist:MinutiaRidgeCount> consists of a minutia number element and a ridge count element. This 

19 information shall be conveyed by listing the identity (index number) of the distant minutia in the 

<ansi-nist:RidgeCountReferenceIdentification> element, and the ridge count to that distant 

21 minutia in the <ansi-nist:RidgeCountValue> element. The complex <ansi22 nist:MinutiaRidgeCount> shall be repeated as many times as required for each minutia. Complex 

23 element <ansi-nist:RidgeCountReferenceIdentification> shall have the simple element 

24 <nc:IdentificationID>, which will contain the index datum. 

<itl:MinutiaDetail> 

26 <ansi-nist:PositionHorizontalCoordinateValue>0486 

27 

28 

</ansinist:PositionHorizontalCoordinateValue> 

29 <ansi-nist:PositionVerticalCoordinateValue>2839 

31 

</ansi-nist:PositionVerticalCoordinateValue>

<ansi-nist:MinutiaIdentification> 

32 

33 

<nc:IdentificationID>00</nc:IdentificationID

> 

34 

36 

37 

38 

39 

41 

42 

</ansi-nist:MinutiaIdentification>

<ansi-nist:PositionThetaAngleMeasure>048 

</ansi-nist:PositionThetaAngleMeasure>

<ansi-nist:MinutiaQualityValue>1 

</ansi-nist:MinutiaQualityValue>

<ansi-nist:MinutiaCategoryCode>B 

</ansi-nist:MinutiaCategoryCode>

<ansi-nist:MinutiaRidgeCount>

<ansi43 nist:RidgeCountReferenceIdentification> 

59 
 

5 

10 

15 

20 

25 

30 

35 

40 

45 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <nc:IdentificationID>2</nc:Identificati

2 onID> 

3 </ansi4 nist:RidgeCountReferenceIdentification>

<ansi-nist:RidgeCountValue>6 

6 </ansi-nist:RidgeCountValue>

7 </ansi-nist:MinutiaRidgeCount>

8 <ansi-nist:MinutiaRidgeCount>

9 <ansinist:RidgeCountReferenceIdentification>

11 <nc:IdentificationID>8</nc:Identificati

12 onID> 

13 </ansi14 nist:RidgeCountReferenceIdentification>

<ansi-nist:RidgeCountValue>3 

16 </ansi-nist:RidgeCountValue>

17 </ansi-nist:MinutiaRidgeCount>

18 </itl:MinutiaDetail>

19 

214.2.7.1.2Element <ansi-nist:MinutiaeQuantity> 

21 Cross reference: Part-1 Section 14.2.10 Field 9.010: Number of minutiae (MIN) 

22 This mandatory element shall contain the count of the number of minutiae recorded for this 

23 fingerprint or palmprint. 

24 

<ansi-nist:MinutiaeQuantity>38</ansi26 nist:MinutiaeQuantity>

27 

28 214.2.7.1.3 Element <ansi-nist:MinutiaeReadingSystem> 

29 Cross reference: Part-1 Section 14.2.15 Field 9.005: Originating fingerprint reading system 

(OFR) 

31 This optional complex element shall contain three child elements relating to the originating 

32 fingerprint reading system. The <ansi-nist:ReadingSystemCodingMethodCode> element shall 

33 contain a single character to indicate the method by which the minutiae data was read, encoded, 

34 and recorded. The following coding shall be used: (1) "A", if the data was automatically read, 

encoded, and recorded without any possibility of human editing; (2) "U", if human editing was 

36 possible but unneeded; (3) "E", if the data was automatically read but manually edited before 

37 encoding and recording; (4) "M", if the data was manually read. The <ansi38 nist:ReadingSystemName> element shall contain the originator's designation or name for the 

39 particular fingerprint or palmprint reading system that generated this record The <ansinist:ReadingSystemSubsystemIdentification> element an optional, two-character, user-generated 

41 subsystem designator that uniquely identifies the originator's equipment. Complex element 

42 <ansi-nist:ReadingSystemSubsystemIdentification> if used shall have the simple element 

43 <nc:IdentificationID>, which will contain the subsystem designator datum. 

44 

<ansi-nist:MinutiaeReadingSystem> 

60 
 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:ReadingSystemCodingMethodCode>E 

2 </ansi-nist:ReadingSystemCodingMethodCode>

3 <ansi-nist:ReadingSystemName>Text 

4 </ansi-nist:ReadingSystemName>

<ansi-nist:ReadingSystemSubsystemIdentification>

6 <nc:IdentificationID>88</nc:IdentificationID

7 > 

8 </ansi-nist:ReadingSystemSubsystemIdentification>

9 </ansi-nist:MinutiaeReadingSystem> 

214.2.7.2Element <ansi-nist:MinutiaeRidgeCountIndicator> 

11 Cross reference: Part-1 Section 14.2.11 Field 9.011 Minutiae ridge count indicator (RDG) 

12 This mandatory single-character element shall be used to indicate the presence of minutiae ridge 

13 count information. A "false" in this element indicates that no ridge count information is available. 

14 A "true" indicates that ridge count information is available. 

16 <ansi-nist:MinutiaeRidgeCountIndicator>true 

17 </ansi-nist:MinutiaeRidgeCountIndicator> 

18 214.2.7.3 Element <ansi-nist:MinutiaeFingerCorePosition> 

19 Cross reference: Part-1 Section 14.2.8 Field 9.008 Core position (CRP) 

This element is optional for fingerprint minutiae, and may not appear at all for palmprint minutiae. 

21 If this element is used, it shall contain the X and Y coordinate position of the core of a fingerprint. 

22 The X value shall be coded as a four-digit ASCII number in the <ansi23 nist:PositionHorizontalCoordinateValue> child element. The Y value shall be coded as a four24 digit ASCII number in the <ansi-nist:PositionVerticalCoordinateValue> child element. Multiple 

occurrences of the core position complex are allowable. 

26 <ansi-nist:MinutiaeFingerCorePosition>

27 <ansi-nist:PositionHorizontalCoordinateValue>0035 

28 </ansi29 nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>0045 

31 </ansi-nist:PositionVerticalCoordinateValue>

32 </ansi-nist:MinutiaeFingerCorePosition> 

33 214.2.7.4 Element <ansi-nist:MinutiaeFingerDeltaPosition> 

34 Cross reference: Part-1 Section 14.2.9 Field 9.009 Delta(s) position (DLT) 

This element is optional for fingerprint minutiae, and may not appear at all for palmprint minutiae. 

36 If this element is used, it shall contain the X and Y coordinate position of each delta that is 

37 present on the fingerprint. The X value shall be coded as a four-digit ASCII number in the <ansi38 nist:PositionHorizontalCoordinateValue> child element. The Y value shall be coded as a four39 digit ASCII number in the <ansi-nist:PositionVerticalCoordinateValue> child element. Multiple 

occurrences of the delta position complex are allowable. 

41 <ansi-nist:MinutiaeFingerDeltaPosition> 

61 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:PositionHorizontalCoordinateValue>0035 

2 

3 

</ansinist:PositionHorizontalCoordinateValue> 

4 <ansi-nist:PositionVerticalCoordinateValue>0045 

5 

6 

</ansi-nist:PositionVerticalCoordinateValue>

</ansi-nist:MinutiaeFingerDeltaPosition> 

7 214.2.7.5 Element <itl:MinutiaeFingerPatternDetail> 

8 Cross reference: Part-1 Section 14.2.7 Field 9.007 Fingerprint pattern classification (FPC) 

9 This element is mandatory when the minutiae are derived from a fingerprint image. It shall 

10 contain a single occurrence of child element for the source of the pattern code and one or more 

11 occurrences of the child element for the fingerprint pattern classification code. If the minutiae are 

12 derived from a palmprint, this element shall not be present. The element shall contain two 

13 information items. The <itl:FingerPatternCodeSourceCode> shall indicate the source of the 

14 specific pattern classification code. The source may be Table 217 or a user-defined classification 

15 code. This element shall contain a "T" to indicate that the pattern classification code is from 

16 Table 217 or a "U" to indicate that the code is user-defined. The <ansi-nist:FingerPatternCode> 

17 shall contain the pattern classification code chosen from Table 217 or a specific user-defined 

18 code. When it is not possible to uniquely identify the fingerprint class, reference fingerprint 

19 classes may be used and shall be included as multiple occurrences of the <ansi20 nist:FingerPatternCode> element. 

21 Table 217 Pattern classification 

Description Code 

Plain arch PA 

Tented arch TA 

Radial loop RL 

Ulnar loop UL 

Plain whorl PW 

Central pocket loop CP 

Double loop DL 

Accidental whorl AW 

Whorl, type not designated WN 

Right slant loop RS 

Left slant loop LS 

Scar SR 

Amputation XX 

Unknown or unclassifiable UN 

22 

23 <itl:MinutiaeFingerPatternDetail> 

62 
 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <itl:FingerPatternCodeSourceCode>T 

2 </itl:FingerPatternCodeSourceCode>

3 <ansi-nist:FingerPatternCode>PW 

4 </ansi-nist:FingerPatternCode>

<ansi-nist:FingerPatternCode>CP 

6 </ansi-nist:FingerPatternCode>

7 </itl:MinutiaeFingerPatternDetail> 

8 214.2.7.6 Element <ansi-nist:MinutiaeFingerPositionCode> or <ansi9 nist:MinutiaePalmPositionCode 

Cross reference: Part-1 Section 14.2.6 Field 9.006 Finger position (FGP) 

11 This mandatory element shall contain the code designating the finger or palm position that 

12 produced information in this Type-9 record. If the exact finger or palm position cannot be 

13 determined, multiple finger positions may be entered as multiple occurrences of this element. 

14 Table 212 and Table 235 list the codes that shall be used for each fingerprint or palmprint 

position. Finger position codes shall be entered in the <ansi-nist:MinutiaeFingerPositionCode> 

16 element. Palm position codes shall be entered in the <ansi-nist:MinutiaePalmPositionCode>. 

17 Multiple occurrences of either element are allowable. 

18 <ansi-nist:MinutiaeFingerPositionCode>5 

19 </ansi-nist:MinutiaeFingerPositionCode>

<ansi-nist:MinutiaeFingerPositionCode>6 

21 </ansi-nist:MinutiaeFingerPositionCode>

22 or 

23 <ansi-nist:MinutiaePalmPositionCode>22 

24 </ansi-nist:MinutiaePalmPositionCode>

<ansi-nist:MinutiaePalmPositionCode>24 

26 </ansi-nist:MinutiaePalmPositionCode> 

27 214.3 End of Type-9 logical record 

28 The Type-9 logical record shall end with the XML tag </itl:PackageMinutiaeRecord>. 

29 214.4 Additional minutiae records 

Typically, up to nine more fingers may be described within the exchange package. Alternatively, 

31 up to 7 more additional palm records may be described within the exchange package. For each 

32 additional finger or palm, a Type-9 logical record is required. 

33 215 Type-10 facial & SMT image record 

34 Type-10 records shall contain facial and/or SMT image data and related ASCII information 

pertaining to the specific image contained in this record. It shall be used to exchange both 

36 grayscale and color image data in a compressed or uncompressed form. Annex F includes an 

37 XML instance example of the Type-10 facial image record. 

63 
 

Part 1 Cond Part 1 Part 2 XML Element Name IMG Occur count 

Ident code Field 

Number 

 min Max

LEN 10.001 0

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 10.002 <ansi-nist:ImageReferenceIdentification> 1 1

UDF O 10.200 – <itl:UserDefinedFields> 0 Unlim

10.998 

 M <itl:FaceImage> FAC 1 1 

M <ansi-nist:PhysicalFeatureImage> SMT 1 1 

DATA M 10.999 <nc:BinaryBase64Object> 1 1

 <ansi-nist:ImageCaptureDetail> 1 1

PHD M 10.005 <ansi-nist:CaptureDate> 1 1

SHPS O 10.016 <ansi-nist:CaptureHorizontalPixelDensityValue> 0 1

SRC M 10.004 <ansi-nist:CaptureOrganization> 1 1

SVPS O 10.017 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 215.1 XML elements for the Type-10 logical record 

2 Table 218 lists each of the mandatory and optional XML elements present in a Type-10 logical 

3 record. The following paragraphs describe the data contained in each of the elements for the 

4 Type-10 logical record. 

5 Within a Type-10 logical record, entries shall be provided in XML elements. It is required that all 

6 of the elements of the record are ordered, and the image data shall be converted to ASCII using 

7 Base64 encoding. For each element of the Type-10 record, Table 218 lists the “condition code” 

8 as being mandatory “M” or optional “O”, provides a cross-reference to the Part-1 field number and 

9 mnemonic, the XML tag name, and occurrence limits. Elements containing entries in the “IMG” 

10 column are only applicable to that image type. An entry of “FAC” applies to a mugshot or facial 

11 image, and an entry of "SMT" applies to scar, a mark, or a tattoo image. 

12 The Type-10 record shall be contained within this complex element: 

13 <itl:PackageImageRecord> 

14 [. . . Type 10 Record Content . . .] 

15 </itl:PackageImageRecord> 

16 In the subsections that follow, text in bold between opening and closing tags is informative and 

17 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi18 nist:RecordCategoryCode> for example). 

19 Table 218 Type-10 facial and SMT record layout 

64 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 min Max 

DMM O 10.030 <ansi-nist:CaptureDeviceMonitoringModeCode> FAC 0 1 

CSP M 10.012 <ansi-nist:ImageColorSpaceCode> 1 1

CGA M 10.011 <ansi-nist:ImageCompressionAlgorithmText> 1 1

HLL M 10.006 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1

HPS M 10.009 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1

SQS O 10.024 <ansi-nist:ImageQuality> FAC 0 1

SLC M 10.008 <ansi-nist:ImageScaleUnitsCode> 1 1

IMT M 10.003 <ansi-nist:ImageCategoryCode> 1 1

VLL M 10.007 <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1

VPS M 10.010 <ansi-nist:ImageVerticalPixelDensityValue> 1 1

SPA O 10.025 <ansi-nist:FaceImage3DPoseAngle> FAC 0 1

SAP M 10.013 <ansi-nist:FaceImageAcquisitionProfileCode> FAC 1 1

PXS O 10.022 <ansi-nist:FaceImageAttribute> FAC 0 Unlim

SXS O 10.026 <ansi-nist:FaceImageDescriptionCode> FAC 0 Unlim

SEC O 10.027 <ansi-nist:FaceImageEyeColorAttributeCode> FAC 0 1

SFP O 10.029 <ansi-nist:FaceImageFeaturePoint> FAC 0 Unlim

SHC O 10.028 <ansi-nist:FaceImageHairColorAttributeCode> FAC 0 2

POA O 10.021 <ansi-nist:FaceImagePoseOffsetAngleMeasure> FAC 0 1

POS O 10.020 <ansi-nist:FaceImageSubjectPoseCode> FAC 0 1

PAS O 10.023 <itl:FaceImageAcquisitionSource> FAC 0 1

O <ansi-nist:PhysicalFeatureDescriptionDetail> SMT 0 Unlim

COL 10.043 <ansi-nist:PhysicalFeatureColorDetail> SMT 0 1

SMD 10.042 <ansi-nist:PhysicalFeatureCategoryCode> SMT 1 1

 <ansi-nist:PhysicalFeatureClassCode> SMT 0 1

 <ansi-nist:PhysicalFeatureDescriptionText> SMT 0 1

 <ansi-nist:PhysicalFeatureSubClassCode> SMT 0 1

SMT M 10.040 <ansi-nist:PhysicalFeatureNCICCode> SMT 1 Unlim

SMS O 10.041 <ansi-nist:PhysicalFeatureSize> SMT 0 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

65 
 

1 

2 215.1.1 Record length 

3 Cross reference: Part-1 Section 15.1.1 Field 10.001: Logical record length (LEN) 

4 There is no corresponding Part 2 XML element. 

5 215.1.2 Element <ansi-nist:RecordCategoryCode> 

6 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

7 record type. For the Type-10 record, it shall contain a value of 10. 

8 <ansi-nist:RecordCategoryCode>10</ansi9 nist:RecordCategoryCode> 

10 215.1.3 Element <ansi-nist:ImageReferenceIdentification> 

11 Cross reference: Part-1 Section 15.1.2 Field 10.002: Image designation character (IDC) 

12 This mandatory complex element shall be used to identify the facial or SMT image data contained 

13 in the record. The content of this element shall match the <ansi14 nist:ImageReferenceIdentification> found in the <ansi-nist:TransactionContentSummary> 

15 element of the Type-1 record. 

16 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

17 <nc:IdentificationID>, which shall contain the image reference identification datum. 

18 <ansi-nist:ImageReferenceIdentification>

19 <nc:IdentificationID>8</nc:IdentificationID>

20 </ansi-nist:ImageReferenceIdentification> 

21 215.1.4 Element <itl:UserDefinedFields> 

22 Cross reference: Part-1 Section 15.1.35 Fields 10.200-998: User-defined fields (UDF) 

23 These elements are user-definable. Their size and content shall be defined by the user and be in 

24 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

25 content values. 

26 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

27 Implementers should define, in an extension schema, a substitution element containing user28 defined child elements from the user’s domain. 

29 A substitution element should be defined in a user’s extension schema similar to this: 

30 <xsd:element name="UserDefinedFields" 

31 substitutionGroup="itl:UserDefinedFields"

32 type="user-domain:UserDefinedFieldsType"/> 

33 

34 <xsd:complexType name="UserDefinedFieldsType">

35 <xsd:complexContent>

36 <xsd:extension base="s:ComplexObjectType"> 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

66 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <xsd:sequence>

2 <xsd:element ref="user-domain:OneField"/>

3 <xsd:element ref="user-domain:TwoField”"/>

4 </xsd:sequence>

</xsd:extension>

6 </xsd:complexContent>

7 </xsd:complexType>

8 

9 

The element would then appear in an instance document like this: 

11 <user-domain:UserDefinedFields> 

12 <user-domain:OneField>Text</user-domain:OneField> 

13 <user-domain:TwoField>Text</user-domain:TwoField> 

14 </user-domain:UserDefinedFields> 

215.1.5 Element <itl:FaceImage> or <ansi-nist:PhysicalFeatureImage> 

16 This mandatory complex element can take one of two forms. If the Type-10 record contains the 

17 image of a face, the <itl:FaceImage> complex element shall be used. If the record contains the 

18 image of a SMT, the <itl:PhysicalFeatureImage> complex shall be used. All of the remaining 

19 elements in the Type-10 record are nested within, as described in the subsections below. 

<itl:FaceImage> 

21 [. . . Face image elements . . .] 

22 </itl:FaceImage> 

23 or 

24 <ansi-nist:PhysicalFeatureImage> 

[. . . SMT image elements . . .] 

26 </ansi-nist:PhysicalFeatureImage> 

27 215.1.5.1 Element <nc:BinaryBase64Object> 

28 Cross reference: Part-1 Section 15.1.36 Field 10.999: Image data (DATA) 

29 This mandatory element shall contain all of the grayscale or color image data from a face, scar, 

mark, tattoo, or other image. Binary image data shall be converted to ASCII using Base64 

31 encoding. 

32 Each pixel of uncompressed grayscale data shall be quantized to eight bits (256 gray levels) and 

33 shall occupy a single byte. Uncompressed color image data shall be expressed as 24 or 48 bit 

34 sRGB pixels. For the 24-bit sRGB, the first byte shall contain the eight bits for the red component 

of the pixel, the second byte shall contain the eight bits for the green component of the pixel, and 

36 the third byte shall contain the last eight bits for the blue component of the pixel. For the 48-bit 

37 sRGB pixel, each color component will occupy two bytes. If compression is used, the pixel data 

38 shall be compressed in accordance with the compression technique specified in the <ansi67 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 nist:ImageCompressionAlgorithmText> element. If the JPEG algorithm is to be used to compress 

2 the data, the data to be placed in this element shall be encoded first using the JFIF format 

3 specification then Base64 encoded. 

4 <nc:BinaryBase64Object>base64 data 

</nc:BinaryBase64Object> 

6 215.1.5.2 Element <ansi-nist:ImageCaptureDetail> 

7 This mandatory complex element contains five child elements described in the subsections 

8 below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansi9 nist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode>. 

11 <ansi-nist:ImageCaptureDetail> 

12 [. . . Image capture elements . . .] 

13 </ansi-nist:ImageCaptureDetail> 

14 215.1.5.2.1 Element <ansi-nist:CaptureDate> 

Cross reference: Part-1 Section 15.1.5 Field 10.005: Photo date (PHD) 

16 This mandatory element <ansi-nist:CaptureDate> shall contain the date that the image contained 

17 in the record was captured. The date shall appear as eight digits, separated by dashes, in the 

18 format YYYY-MM-DD. The YYYY characters shall represent the year the image was captured; 

19 the MM characters shall be the tens and units values of the month; and the DD characters shall 

be the tens and units values of the day in the month. For example, 2008-02-29 represents 

21 February 29, 2008. The complete date must be a legitimate date. 

22 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

23 contain capture date data. 

24 <ansi-nist:CaptureDate>

<nc:Date>2008-02-29</nc:Date>

26 </ansi-nist:CaptureDate> 

27 215.1.5.2.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

28 Cross reference: Part-1 Section 15.1.16 Field 10.016: Scanned horizontal pixel scale (SHPS) 

29 This optional element shall specify the horizontal pixel density used for the scanning of the 

original impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

31 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

32 <ansi-nist:CaptureHorizontalPixelDensityValue>500 

33 </ansi-nist:CaptureHorizontalPixelDensityValue>

34 

68 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 215.1.5.2.3 Element <ansi-nist:CaptureOrganization> 

2 Cross reference: Part-1 Section 15.1.4 Field 10.004: Source agency / ORI (SRC) 

3 This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

4 <nc:IdentificationID> the identification of the administration or organization that originally captured 

the facial or SMT image contained in the record, and may contain in <nc:OrganizationName> the 

6 text name of the organization. Normally, the ORI of the agency that captured the image will be 

7 contained in <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may 

8 contain up to 36 identifying characters each and the data content of this element shall be defined 

9 by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

11 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

12 <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

13 contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

14 contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization>

16 <nc:OrganizationIdentification>

17 <nc:IdentificationID>WI013415Y</nc:Iden

18 tificationID> 

19 </nc:OrganizationIdentification>

<nc:OrganizationName>Text</nc:OrganizationName>

21 </ansi-nist:CaptureOrganization> 

22 

23 215.1.5.2.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

24 Cross reference: Part-1 Section 15.1.17 Field 10.017: Scanned vertical pixel scale (SVPS) 

This optional element shall specify the vertical pixel density used for the scanning of the original 

26 impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

27 indicates the vertical component of the pixel aspect ratio. 

28 <ansi-nist:CaptureVerticalPixelDensityValue>500 

29 </ansinist:CaptureVerticalPixelDensityValue> 

31 215.1.5.2.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

32 Cross reference: Part-1 Section 15.1.28 Field 10.030: Device monitoring mode (DMM) 

33 This optional element provides information describing the level of human monitoring for the image 

34 capture device. This element will contain an entry from Table 219 to indicate the monitoring 

mode of the biometric sample capture device. (Table 219 is the same as Table 27 in Part 1.) 

36 

37 

38 

69 
 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 219 Device monitoring modes 

CONDITION DESCRIPTION 

CONTROLLED Operator physically controls the subject to acquire biometric sample 

ASSISTED Person available to provide assistance to subject submitting the biometric 

OBSERVED Person present to observe operation of the device but provides no assistance 

UNATTENDED No one present to observe or provide assistance 

UNKNOWN No information is known 

2 

3 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED 

4 </ansi-nist:CaptureDeviceMonitoringModeCode> 

5 215.1.5.3 Element <ansi-nist:ImageColorSpaceCode> 

6 Cross reference: Part-1 Section 15.1.12 Field 10.012: Color space (CSP) 

7 This mandatory element shall contain an ASCII entry from Table 203 to identify the color space 

8 used to exchange the image data. If the color space for an RGB image cannot be determined, an 

9 entry of "RGB" shall be entered in this element. 

10 For JPEG-compressed color image files (stored using the JFIF file format), the preferred 

11 (external) color space is sRGB and an entry of “SRGB” shall be used for this element. For all 

12 grayscale (monochrome) images, an entry of "GRAY" shall be used for this element. 

13 For JPEG 2000 images stored using the JP2 file format, the available enumerated color spaces 

14 are sRGB, sYCC, and grayscale, to be entered, respectively, as “SRGB”, “SYCC”, and “GRAY” in 

15 this element. The preferred (external) color space for color images is sRGB. If a photo 

16 acquisition device uses another ICC13 color profile, the acquisition system must convert the image 

17 data to one of these enumerated color spaces before the JP2 file may be embedded in a Type 10 

18 record. 

19 For uncompressed color images containing non-interleaved red, green, and blue pixels in that 

20 order, the preferred color space is sRGB and an entry of “SRGB” shall be used for this element. 

21 The element <ansi-nist:ImageCompressionAlgorithmText> will need to be examined to determine 

22 if the image data is JPEG, JPEG 2000, or an uncompressed color image. 

23 <ansi-nist:ImageColorSpaceCode>YCC 

24 </ansi-nist:ImageColorSpaceCode> 

25 215.1.5.4 Element <ansi-nist:ImageCompressionAlgorithmText> 

26 Cross reference: Part-1 Section 15.1.11 Field 10.011: Compression algorithm (CGA) 

27 This mandatory element shall contain an ASCII entry from Table 201 (other than WSQ) to specify 

28 the algorithm used for compressing the color or grayscale image. An entry of "NONE" indicates 

13 International Color Consortium (ICC), http://www.color.org/ 

70 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 that the data contained in this record is uncompressed. The image shall be represented as an 

2 array of n rows by m columns by at least 8-bit pixels. Each pixel in a monochrome image shall be 

3 represented by eight or more bits. Color images shall be represented as a series of sequential 

4 samples of a red, green, and blue intensity for each pixel. The image shall be organized in rowmajor order, with the lowest address corresponding to the upper left corner of the image. For 

6 those images that are to be compressed, the method for the compression of facial and SMT 

7 images is specified by the baseline mode of the JPEG, JPEG 2000, or PNG algorithms. 

8 <ansi-nist:ImageCompressionAlgorithmText>JPEGB 

9 </ansi-nist:ImageCompressionAlgorithmText> 

215.1.5.5 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

11 Cross reference: Part-1 Section 15.1.6 Field 10.006: Horizontal line length (HLL) 

12 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

13 the transmitted image. 

14 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

</ansi16 nist:ImageHorizontalLineLengthPixelQuantity> 

17 215.1.5.6 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

18 Cross reference: Part-1 Section 15.1.9 Field 10.009: Horizontal pixel scale (HPS) 

19 This mandatory element shall specify the integer pixel density used in the horizontal direction of 

the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

21 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

22 <ansi-nist:CaptureHorizontalPixelDensityValue>1200 

23 </ansi-nist:CaptureHorizontalPixelDensityValue> 

24 215.1.5.7 Element <ansi-nist:ImageQuality> 

Cross reference: Part-1 Section 15.1.22 Field 10.024: Subject quality score (SQS) 

26 This optional element shall specify quality score data for facial images stored in this record. 

27 There are three child elements. They identify a quality score and the algorithm used to create the 

28 quality score. This information is useful to enable the recipient of the quality score to differentiate 

29 between quality scores generated by different algorithms and adjust for any differences in 

processing or analysis as necessary. 

31 1. The child element <ansi-nist:QualityAlgorithmProductIdentification> shall specify a 

32 numeric product code assigned by the vendor of the quality algorithm, which may be registered 

33 with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms 

34 was used in the calculation of the quality score. This complex element contains a child element 

<nc:IdentificationID> which contains the ASCII representation of the integer product code and 

36 should be within the range 1 to 65,535. 

37 2. The child element <ansi-nist:QualityValue> shall be a quantitative expression of the 

38 predicted matching performance of the biometric sample. This element contains the ASCII 

39 representation of the integer image quality score between 0 and 100 assigned to the image data 

by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a 

71 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 failed attempt to calculate a quality score. An entry of “254” shall indicate that no attempt to 

2 calculate a quality score was made. The use of additional values to convey other information 

3 should be harmonized with ISO/IEC 19794 standards. 

4 3. The child element <ansi-nist:QualityMeasureVendorIdentification> shall specify the ID of 

5 the vendor of the quality algorithm used to calculate the quality score. This 4-digit hex value is 

6 assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor 

7 Registry of CBEFF Biometric Organizations that will map the value in this element to a registered 

8 organization. This complex element contains a child element <nc:IdentificationID> which shall 

9 contain the identification datum. 

10 <ansi-nist:ImageQuality>

11 <ansi-nist:QualityAlgorithmProductIdentification>

12 <nc:IdentificationID>28488</nc:Identificatio

13 nID> 

14 </ansi15 nist:QualityAlgorithmProductIdentification>

16 <ansi-nist:QualityValue>100 

17 </ansi-nist:QualityValue>

18 <ansi-nist:QualityMeasureVendorIdentification>

19 <nc:IdentificationID>FFF0</nc:Identification

20 ID> 

21 </ansi-nist:QualityMeasureVendorIdentification>

22 </ansi-nist:ImageQuality> 

23 215.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

24 Cross reference: Part-1 Section 15.1.8 Field 10.008: Scale units (SLC) 

25 This mandatory element shall specify the units used to describe the image sampling frequency 

26 (pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per 

27 centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

28 HPS/VPS gives the pixel aspect ratio. 

29 <ansi-nist:ImageScaleUnitsCode>1</ansi30 nist:ImageScaleUnitsCode> 

31 215.1.5.9 Element <ansi-nist:ImageCategoryCode> 

32 Cross reference: Part-1 Section 15.1.3 Field 10.003: Image type (IMT) 

33 This mandatory element is used to indicate the type of image contained in this record. It shall 

34 contain "FACE", "SCAR", "MARK", or "TATTOO" to indicate the appropriate image type. 

35 <ansi-nist:ImageCategoryCode>FACE</ansi36 nist:ImageCategoryCode> 

37 

72 
 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 215.1.5.10 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

2 Cross reference: Part-1 Section 15.1.7 Field 10.007: Vertical line length (VLL) 

3 This mandatory element shall contain the number of horizontal lines contained in the transmitted 

4 image. 

6 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

7 215.1.5.11 Element <ansi-nist:ImageVerticalPixelDensityValue> 

8 Cross reference: Part-1 Section 15.1.10 Field 10.010: Vertical pixel scale (VPS) 

9 This mandatory element shall specify the integer pixel density used in the vertical direction of the 

transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

11 Otherwise, it indicates the vertical component of the pixel aspect ratio. 

12 

13 

<ansi-nist:ImageVerticalPixelDensityValue>1200 

</ansi-nist:ImageVerticalPixelDensityValue> 

14 215.1.5.12 Element <ansi-nist:FaceImage3DPoseAngle> 

Cross reference: Part-1 Section 15.1.23 Field 10.025: Subject pose angles (SPA) 

16 This optional element shall be present when <ansi-nist:FaceImageSubjectPoseCode> (POS) 

17 contains a "D" to indicate a set of determined 3D pose angles of the same subject. If the entry in 

18 the POS element is an "F", "L", or "R", the contents of this element are ignored. When present, 

19 this information shall be entered as three or six child elements. These hold the Pitch, Roll, and 

Yaw angles, and optional uncertainty degrees. If the child elements for the uncertainty degrees 

21 are not present, then the uncertainty in the angles is not determined. 

22 The child element <ansi-nist:PosePitchAngleMeasure> contains the Pitch angle (rotation about 

23 the ‘x’ horizontal axis). The optional child element <ansi-nist:PosePitchUncertaintyValue> 

24 contains the uncertainty degree for the Pitch angle. 

The child element <ansi-nist:PoseRollAngleMeasure> contains the Roll angle (rotation about the 

26 ‘z’ axis). The optional child element <ansi-nist:PoseRollUncertaintyValue> contains the 

27 uncertainty degree for the Roll angle. 

28 The child element <ansi-nist:PoseYawAngleMeasure> contains the Yaw angle (rotation about the 

29 vertical ‘y’ axis). The optional child element <ansi-nist:PoseYawUncertaintyValue> contains the 

uncertainty degree for the Yaw angle. 

31 The first Pitch, Roll, and Yaw angles specify the pose of the subject estimated or measured at 

32 constrained possible orientations within a sphere. Each angle value shall be to the nearest 

33 integer degree. 

34 If both this element and <ansi-nist:FaceImagePoseOffsetAngleMeasure> (POA) are present, the 

Yaw angle present in this element shall supersede the offset angle contained in POA. Note that 

36 the Yaw angle of this element has the opposite sign of the offset angle contained in POA. Annex 

37 J contains, additional information, details, and examples of the subject pose angles. 

38 

39 

41 

73 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:FaceImage3DPoseAngle>

2 <ansi-nist:PosePitchAngleMeasure>45 

3 </ansi-nist:PosePitchAngleMeasure>

4 <ansi-nist:PosePitchUncertaintyMeasure>35 

5 </ansi-nist:PosePitchUncertaintyMeasure>

6 <ansi-nist:PoseRollAngleMeasure>0 

7 </ansi-nist:PoseRollAngleMeasure>

8 <ansi-nist:PoseRollUncertaintyMeasure>90 

9 </ansi-nist:PoseRollUncertaintyMeasure>

10 <ansi-nist:PoseYawAngleMeasure>0 

11 </ansi-nist:PoseYawAngleMeasure>

12 <ansi-nist:PoseYawUncertaintyMeasure>0 

13 </ansi-nist:PoseYawUncertaintyMeasure>

14 </ansi-nist:FaceImage3DPoseAngle> 

15 215.1.5.13 Element <ansi-nist:FaceImageAcquisitionProfileCode> 

16 Cross reference: Part-1 Section 15.1.13 Field 10.013: Subject acquisition profile (SAP) 

17 The Subject Acquisition Profile (SAP) is a mandatory element when the element <ansi18 nist:ImageCategoryCode> (IMT) contains "FACE”. The intent of this element is to provide a 

19 general description of the criteria under which the facial image was captured. This element shall 

20 contain an ASCII character code selected from Table 220 to indicate the numeric value of the 

21 acquisition profile and conditions used to acquire the image. (Table 220 is the same as Table 18 

22 in Part 1.) Typically, the higher the value, the stronger the acquisition requirements become. 

23 Therefore, in the text below, the SAP value will also be denoted as a “level”. 

24 Together with Table 220 is a brief description of each of the levels. Note that levels 10 to 15 

25 denote applications associated with image acquisition under the guidance of other facial 

26 standards or application profiles. Levels 30 to 51 reference best practice recommendations 

27 consisting of increasingly more stringent requirements that must be satisfied. Additional details 

28 and criteria for these levels are contained in Annex H and Annex I. 

29 

30 

31 

32 

33 

34 

35 

36 

37 

74 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 220 Subject acquisition profiles 

Subject Acquisition Profile Attribute Level Code 

Unknown profile 0 

Surveillance facial image 1 

Driver’s license image (AAMVA) 10 

ANSI Full Frontal facial image (ANSI 385) 11 

ANSI Token facial image (ANSI 385) 12 

ISO Full Frontal facial image (ISO/IEC 19794-5) 13 

ISO Token facial image (ISO/IEC 19794-5) 14 

PIV facial image (NIST SP 800-76) 15 

Legacy Mugshot 20 

Best Practice Application - Level 30 30 

Best Practice Application - Level 40 40 

Best Practice Application - Level 50 50 

Best Practice Application - Level 51 51 

2 

3 Level 0 (Unknown profile) 

4 This level denotes any case when the Subject Acquisition Profile is unknown. This value can be 

5 used to alert systems that the profile of the face image needs to be determined manually or via 

6 advanced face image quality evaluation techniques. 

7 Level 1 (Surveillance facial image) 

8 This SAP denotes a surveillance facial image: a face image captured without specific regard to 

9 scene, photographic, or digital requirements. For example, an image of a face from commonly 

10 available surveillance video equipment is generally considered a surveillance facial image. 

11 Typically surveillance facial images are of relatively poor quality compared to mugshots, including 

12 significant pose angle used for the frontal view, poor image resolution, poor image contrast, etc. 

13 Levels 10-15 (Other application profiles) 

14 Levels 10-15 shall denote images associated with capture under the guidance of other facial 

15 standards or application profiles as defined below. 

16 

17 • Level 10 denotes a driver license facial portrait described in the AAMVA International 

18 Specification – DL/ID Card Design 

19 

20 • Level 11 denotes an ANSI facial image which meets requirements of the Full Frontal Image 

21 type defined in ANSI INCITS 385-2004 

22 

75 
 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 • Level 12 denotes an ANSI facial image which meets requirements of the Token Face Image 

2 type defined in ANSI INCITS 385-2004 

3 

4 

• Level 13 denotes an ISO facial image that meets the requirements of the Full Frontal Image 

6 defined in International standard ISO/IEC 19794-5 

7 

8 • Level 14 denotes an ISO facial image that meets the requirements of the Token Face Image 

9 type defined in International standard ISO/IEC 19794-5 

11 • Level 15 denotes a PIV facial image which meets requirements of Biometric Data 

12 Specification for Personal Identity Verification. 

13 

14 Note that the facial images of Levels 13 and 14 may come from travel documents as described in 

“Deployment of Machine Readable Travel Documents’’, ICAO Technical Report, version 2.0 . 

16 Level 20 (Legacy facial mugshot) 

17 An image conforming to this application profile level shall be a mugshot formatted according to 

18 ANSI/NIST-ITL 2000, but not necessarily or known to be conforming to the best practice 

19 requirements given in profile 30 below. The subject pose(s) can be Frontal, Profile, or Angled.

 Best Practice Application Level 30 

21 An image conforming to a level 30 application profile shall include at least one mugshot record 

22 conforming to all best practice requirements (BPR) in Annex H. These mugshots shall adhere to 

23 strict background, lighting, and resolution requirements. In particular, the background is 18% 

24 gray, the lighting is three-point, and the image size is at least 480x600 pixels with an aspect ratio 

of 1:1.25. 

26 Best Practice Application Level 40 

27 A facial image conforming to the level 40 application profile can be captured with an off-the-shelf 

28 1 megapixel camera. Annex I contains detailed information for the capture of level 40, 50, and 51 

29 facial images. Requirements for conformance with level 40 facial image capture include the 

following: 

31 • Conformance to the minimum requirements for the capture of level 30 facial images 

32 • At least one frontal face image shall be captured which conforms to the “face image capture 

33 requirements” 

34 • The minimum number of pixels in the electronic digital image shall be 768 pixels in the 

horizontal direction by 1024 pixels in the vertical direction and 

36 • Facial images shall conform to the “head and shoulders” composition detailed requirements. 

37 

38 It should be noted that the image quality of the captured facial images will be improved as the 

39 number of pixels in both directions are increased. However, as images are captured with an 

increased number of pixels, the 3:4 (Width:Height) aspect ratio shall be maintained. 

41 Best Practice Application Level 50 and Level 51 

42 An image conforming to the level 50 and level 51 application profiles shall include “face image 

43 capture requirements” as described in Annex I. These profile levels are intended to allow for 

44 examination of up to forensic-level (10 ppmm) detail on a subject’s face. The only difference 

76 
 

1 between levels 50 and 51 is that level 50 specifies the “head and shoulders” composition 

2 requirements while level 51 specifies the “head only” composition requirements. 

3 Identification applications require approximately 1700 pixels wide by 2515 pixels high on the face 

4 for the 99th percentile male in the U.S. population. Allocating 50% of the image width for the 

5 head requires approximately 3400 pixels for a “head and shoulders photo” image width. For a 

6 level 50 image capture profile, the minimum number of pixels in the electronic digital image shall 

7 be 3300 pixels in the horizontal direction by 4400 pixels in the vertical direction. Off-the-shelf 15 

8 (or more) megapixel digital cameras satisfy this requirement. 

9 As an alternative, allocating 70% of the image width for the head requires approximately 2400 

10 pixels for the “head only” facial capture. For a level 51 image capture profile, the minimum 

11 number of pixels in the electronic digital image shall be 2400 pixels in the horizontal direction by 

12 3200 pixels in the vertical direction. Off-the-shelf 8 megapixel digital cameras satisfy this 

13 requirement. 

14 The level 50 and level 51 SAPs allow for the encoding of very high resolution face images that 

15 are consistent with the discussion above and with the “face image capture requirements”. It 

16 should be noted that the image quality of the captured facial images may be improved as the 

17 number of pixels in both directions are increased. Figure 4 illustrates the improvement in image 

18 quality from levels 30 to 50/51. However, as images are captured with an increased number of 

19 pixels, the 3:4 (Width:Height) aspect ratio shall be maintained. 

20 <ansi-nist:FaceImageAcquisitionProfileCode>20 

21 </ansi-nist:FaceImageAcquisitionProfileCode> 

22 215.1.5.14 Element <ansi-nist:FaceImageAttribute> 

23 Cross reference: Part-1 Section 15.1.20 Field 10.022: Photo description (PXS) 

24 This optional element, retained for legacy systems, is used for the exchange of facial image data. 

25 When present, it shall consist of one or more child elements and shall describe special attributes 

26 of the captured facial image. Attributes associated with the facial image may be selected from 

27 Table 221. (Table 221 is the same as Table 20 in Part 1.) The “attribute code” shall be entered 

28 in the <ansi-nist:FaceImageAttributeCode> child element. 

29 Physical characteristics, such as "FRECKLES" may be entered using a pair of child elements. 

30 The “attribute code” "PHYSICAL" from Table 221 shall be entered in the <ansi31 nist:FaceImageAttributeCode> element. It shall be followed by a <ansi32 nist:FaceImageAttributeText> element containing the characteristic as listed in the Ninth (or 

33 current) Edition of the NCIC Code Manual, December, 2000. The "OTHER" category is used to 

34 enter unlisted or miscellaneous attributes of the facial image. This information shall be entered 

35 using a pair of child elements. The first is "OTHER" in the <ansi-nist:FaceImageAttributeCode> 

36 element followed by the unformatted text used to describe the attribute in the <ansi37 nist:FaceImageAttributeText> element. 

38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

77 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

a. Level 30 b. Level 40 c. Levels 50 and 51 

1 Figure 4 Examples of resolution for levels 30, 40, & 50/51 

2 

3 Table 221 Photo descriptors 

Facial image attribute Attribute code 

Subject Wearing Glasses GLASSES 

Subject Wearing Hat HAT 

Subject Wearing Scarf SCARF 

Physical Characteristics PHYSICAL 

Other Characteristics OTHER 

4 

5 Multiple attributes with child code and text elements may be listed as repeating occurrences of 

6 the parent <ansi-nist:FaceImageAttribute>. 

7 Note: The Subject facial description (SXS) is intended as a replacement for PXS. Table 221 

8 entries are now duplicated and expanded upon in Table 222. 

9 

10 <ansi-nist:FaceImageAttribute>

11 <ansi-nist:FaceImageAttributeCode>GLASSES 

12 </ansi-nist:FaceImageAttributeCode>

13 </ansi-nist:FaceImageAttribute>

14 <ansi-nist:FaceImageAttribute>

15 <ansi-nist:FaceImageAttributeCode>OTHER 

16 </ansi-nist:FaceImageAttributeCode> 

78 
 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:FaceImageAttributeText>Text 

2 </ansi-nist:FaceImageAttributeText>

3 </ansi-nist:FaceImageAttribute>

4 <ansi-nist:FaceImageAttribute>

<ansi-nist:FaceImageAttributeCode>PHYSICAL 

6 </ansi-nist:FaceImageAttributeCode>

7 <ansi-nist:FaceImageAttributeText>ART EYE 

8 </ansi-nist:FaceImageAttributeText>

9 </ansi-nist:FaceImageAttribute> 

215.1.5.15 Element <ansi-nist:FaceImageDescriptionCode> 

11 Cross reference: Part-1 Section 15.1.24 Field 10.026: Subject facial description (SXS) 

12 This optional element shall be used for the exchange of facial image data. This element is 

13 mandatory if the element <ansi-nist:FaceImageAcquisitionProfileCode> contains a SAP entry of 

14 "40" or greater. When present, it shall describe the facial expression of the subject and other 

attributes associated with the subject's captured facial image. This element may have multiple 

16 occurrences, each containing a single information item. Attributes associated with the facial 

17 image may be selected from Table 222 and entered in this element. (Table 222 is the same as 

18 Table 22 in Part 1.) For "Physical Characteristic", enter a characteristic as listed in the Ninth(or 

19 current) Edition of the NCIC Code Manual, December, 2000. For the "Other Characteristic" enter 

unlisted or miscellaneous attributes as unformatted text used to describe the attribute. Multiple 

21 attributes may be listed as separate occurrences of the <ansi-nist:FaceImageDescriptionCode> 

22 element. 

23 <ansi-nist:FaceImageDescriptionCode>MOUTH OPEN 

24 </ansi-nist:FaceImageDescriptionCode>

<ansi-nist:FaceImageDescriptionCode>TEETH VISIBLE 

26 </ansi-nist:FaceImageDescriptionCode> 

27 215.1.5.16 Element <ansi-nist:FaceImageEyeColorAttributeCode> 

28 Cross reference: Part-1 Section 15.1.25 Field 10.027: Subject eye color (SEC) 

29 This optional element shall be used for the exchange of facial image data. This element is 

mandatory if the element <ansi-nist:FaceImageAcquisitionProfileCode> contains a SAP entry of 

31 "40" or greater. When present, it shall describe the eye color of the subject as seen in the 

32 photograph. If unusual or unnatural such as may be the case when colored contact lenses are 

33 present and the “real” eye color cannot be ascertained, then the color should be labeled as 

34 “XXX”. Eye color attributes and attribute codes are given by Table 223. (Table 223 is the same 

as Table 23 in Part 1.) 

36 

37 

38 

39 

79 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 222 Subject facial description codes 

Facial description attribute Attribute code 

Expression unspecified UNKNOWN 

Neutral (non-smiling) with both eyes open and 

mouth closed) 

NEUTRAL 

Smiling where the inside of the mouth and/or teeth 

is not exposed (closed jaw). 

SMILE 

Subject Having Mouth open MOUTH OPEN 

Having Teeth visible TEETH VISIBLE 

Raising eyebrows RAISED BROWS 

Frowning FROWNING 

Looking away from the camera EYES AWAY 

Squinting SQUINTING 

Subject Wearing Left Eye Patch LEFT EYE PATCH 

Subject Wearing Right Eye Patch RIGHT EYE PATCH 

Subject Wearing Clear Glasses CLEAR GLASSES 

Subject Wearing Dark or Visible Colored Glasses 

(medical) 

DARK GLASSES 

Head covering/hat HAT 

Wearing Scarf SCARF 

Having Moustache MOUSTACHE 

Having Beard BEARD 

Ear(s) obscured by hair NO EAR 

Blinking (either or both eyes closed) BLINK 

Having Distorting Medical Condition impacting 

Feature Point detection 

DISTORTING CONDITION 

Physical Characteristics <From NCIC Code Manual> 

Other Characteristics <Unformatted Text> 

2 Note: This element is intended to replace the photo description element <ansi3 nist:FaceImageAttribute) (PXS) and to enhance the content with additional 

4 descriptive information. As such, photo descriptors found in Table 221 also 

5 appear in Table 222. 

6 

7 

8 

9 

80 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 

2 Table 223 Eye color codes 

Eye color attribute Attribute code 

Black BLK 

Blue BLU 

Brown BRO 

Gray GRY 

Green GRN 

Hazel HAZ 

Maroon MAR 

Multicolored MUL 

Pink PNK 

Unknown XXX 

3 

4 <ansi-nist:FaceImageEyeColorAttributeCode>BLU 

5 </ansi-nist:FaceImageEyeColorAttributeCode> 

6 215.1.5.17 Element <ansi-nist:FaceImageFeaturePoint> 

7 Cross reference: Part-1 Section 15.1.27 Field 10.029: Facial feature points (FFP) 

8 The optional element shall be used for the exchange of facial image data. When present, it shall 

9 describe special attributes of manually or automatically detected facial feature points of the 

10 captured facial image. This information shall be entered as a four-information item feature point 

11 block as described in Table 224. (Table 224 is the same as Table 25 in Part 1.) 

12 The child element <ansi-nist:FeaturePointHorizontalCoordinateValue> contains the X coordinate 

13 of the feature point. 

14 The child element <ansi-nist:FeaturePointIdentification> contains feature point code. This 

15 complex element contains a child element <nc:IdentificationID> that shall hold the code datum. 

16 The child element <ansi-nist:FeaturePointCategoryCode> contains the feature point type. 

17 The child element <ansi-nist:FeaturePointVerticalCoordinateValue> contains the Y coordinate of 

18 the feature point. 

19 Multiple facial points may be listed by repeated occurrences of the parent <ansi20 nist:FaceImageFeaturePoint> complex, each containing these four information items. The 

21 maximum number of feature points shall be 88, with the use of 84 MPEG4 feature points and 4 

22 additional eye and nostril center feature points. 

23 Feature points shall be included in the Type-10 record if they have been accurately determined, 

24 thereby providing the option that that these parameters do not have to be re-determined when the 

25 image is processed for face recognition tasks. 

81 
 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 224 Subject feature points 

Item Size Value Notes 

X coordinate 1-4 characters Horizontal pixel count from 

upper left pixel. 

Count starts at 0. 

Feature Point Code 3-5 characters A.B in ASCII text 

A and B are described in 0. 

The maximum value of A is 

12 and of B is 15. 

Feature Point Type 1 character 1 Denotes a 2D Feature 

Point. 

 All other values are 

reserved. 

Y coordinate 1-4 characters Vertical pixel count from 

upper left pixel. 

Count starts at 0. 

2 

3 Typically a computer algorithm will either accurately determine the position of the feature point or 

4 completely fail and provide either clearly erroneous or no landmark information. Therefore, a 

5 method for accurate determination is the use of computer-automated feature point determination 

6 followed by human verification and potential override of the computer determined feature points. 

7 MPEG4 Feature points 

8 The feature point code item shall specify the feature point that is stored in the feature point block. 

9 The codes for the feature points are taken from the MPEG4 standard and defined as MPEG4 

10 feature points. Each feature point code is represented by a notation A.B using a major (A) and a 

11 minor (B) value. The encoding of the feature point code is given by the numeric ASCII 

12 representation of the value of A.B. The period is required, and the maximum size of this entry 

13 shall be 5 characters. 

14 Figure 6 denotes the feature point codes associated with feature points as given by Annex C of 

15 ISO/IEC 14496-2. Each code is given by major value A and minor value B. For example, the 

16 code for the left corner of the left eye is given by major value 3 and minor value 7. 

17 Eye and nostril centre Feature Points 

18 The eye center feature points 12.1 (left) and 12.2 (right) are defined to be the horizontal and 

19 vertical midpoints of the eye corners (3.7, 3.11) and (3.8, 3.12) respectively. The left nostril center 

20 feature point 12.3 is defined to be the midpoint of the nose feature points (9.1, 9.15) in the 

21 horizontal direction and (9.3, 9.15) in the vertical direction. Similarly, the right nostril center 

22 feature point 12.4 is defined to be the midpoint of the nose feature points (9.2, 9.15) in the 

23 horizontal direction and (9.3, 9.15) in the vertical direction. Both the eye center and nostril center 

24 Feature points are shown in Figure 5 and values given in Table 225. (Table 225 is the same as 

25 Table 26 in Part 1.) 

26 

27 

82 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Figure 5 Eye and nostril center feature points 

2 

3 Table 225 Eye and nostril center feature point codes 

Center Feature Point Midpoint of Feature Points Feature Point code 

Left Eye 3.7, 3.11 12.1 

Right Eye 3.8, 3.12 12.2 

Left Nostril Horizontal Vertical 12.3 

9.1, 9.15 9.3,9.15 

Right Nostril Horizontal Vertical 12.4 

9.2, 9.15 9.3,9.15 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

83 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

An example instance for representing two feature points of eye centers follows. 

<ansi-nist:FaceImageFeaturePoint>

<ansinist:FeaturePointHorizontalCoordinateValue>120 

</ansinist:FeaturePointHorizontalCoordinateValue> 

<ansi-nist:FeaturePointIdentification> 

<nc:IdentificationID>12.2</nc:Identification

ID> 

</ansi-nist:FeaturePointIdentification>

<ansi-nist:FeaturePointCategoryCode>1 

</ansi-nist:FeaturePointCategoryCode>

<ansinist:FeaturePointVerticalCoordinateValue>130 

</ansinist:FeaturePointVerticalCoordinateValue> 

</ansi-nist:FaceImageFeaturePoint>

<ansi-nist:FaceImageFeaturePoint>

<ansinist:FeaturePointHorizontalCoordinateValue>240 

</ansinist:FeaturePointHorizontalCoordinateValue> 

<ansi-nist:FeaturePointIdentification> 

<nc:IdentificationID>12.1</nc:Identification

ID> 

</ansi-nist:FeaturePointIdentification>

<ansi-nist:FeaturePointCategoryCode>1 

</ansi-nist:FeaturePointCategoryCode>

<ansinist:FeaturePointVerticalCoordinateValue>129 

</ansinist:FeaturePointVerticalCoordinateValue> 

</ansi-nist:FaceImageFeaturePoint> 

84 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

11.5 11.5 

2.1 

2.12 2.11 

2.14 

2.10 

2.13 

10.6 10.8 

10.4 

10.2 

10.10 

5.4 

5.2 

5.3 

5.1 

10.9 

10.3 

10.5 10.7 

4.1 4.3 

4.6 4.5

4.4 4.2 

11.2 11.1 11.3 

11.4 

x 

y x y 

z 

11.4 

11.2 

10.2 

10.4 

10.10 

10.8 

10.6 

7.1 

11.6 4.6 

4.4 

4.2 

5.2 

5.4 

2.10 

2.1 

11.1 

10.1 

2.14 2.12 

z 

3.14 3.13 

3.5 

3.1 

3.3 

3.11 3.6 

3.4 

3.2 

3.8 

3.12 3.7

3.10 3.9 9.6 9.7

Right eye Left eye 

9.8 

Nose 9.12 

9.14 9.13 

9.10 9.11 

9.3 

9.9 9.2 9.1 

Teeth 9.4 9.15 9.5 

Tongue 

6.2 6.4 6.3 

6.1 Mouth 

8.1 8.9 8.10 8.5 8.3 

8.7 

8.2 

8.8 

8.4 

8.6 

2.2 

2.3 

2.6 

2.9 2.8

2.5 2.7 2.4 

Feature points affected by FAPs 

Other feature points 

 

1 Figure 6 Feature point codes defined in ISO/IEC 14496-2 

2 

3 215.1.5.18 Element <ansi-nist:FaceImageHairColorAttributeCode> 

4 Cross reference: Part-1 Section 15.1.26 Field 10.028: Subject hair color (SHC) 

5 This optional element shall be used for the exchange of facial image data. This element is 

6 mandatory if the element <ansi-nist:FaceImageAcquisitionProfileCode> contains a SAP entry of 

7 "40" or greater. When present, it shall contain an entry form Table 226 that describes the hair 

8 color of the subject as seen in the photograph. (Table 226 is the same as Table 24 in Part 1.) 

85 
 

1 For unusual or unnatural colors not listed in the table, or the "real" color cannot be ascertained, 

2 the hair color should be labeled as “XXX”. 

3 If the subject is completely bald, or has a completely shaved head, then the hair color shall be 

4 labeled as “BAL”. When the subject is predominantly bald, but hair color is discernable, then the 

5 appropriate hair color attribute code shall follow “BAL” in a separate occurrence of this element. 

6 Table 226 Hair color codes 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Hair color attribute Attribute code 

Unspecified or unknown XXX 

Bald BAL 

Black BLK 

Blonde or Strawberry BLN 

Brown BRO 

Gray or Partially Gray GRY 

Red or Auburn RED 

Sandy SDY 

White WHI 

Blue BLU 

Green GRN 

Orange ONG 

Pink PNK 

Purple PLE 

7 

8 <ansi-nist:FaceImageHairColorAttributeCode>BAL 

9 </ansi-nist:FaceImageHairColorAttributeCode>

10 <ansi-nist:FaceImageHairColorAttributeCode>GRY 

11 </ansi-nist:FaceImageHairColorAttributeCode> 

12 215.1.5.19 Element <ansi-nist:FaceImagePoseOffsetAngleMeasure> 

13 Cross reference: Part-1 Section 15.1.19 Field 10.021: Pose offset angle (POA) 

14 This element shall only be used for the exchange of facial image data if <ansi15 nist:FaceImageSubjectPoseCode> (POS) contains an "A" to indicate an angled pose of the 

16 subject. This element should be omitted for a full face or a profile. This element specifies the 

17 pose position of the subject at any possible orientation within a circle. Its value shall be to a 

18 nearest degree. 

19 The offset angle shall be measured from the full-face pose position and have a range of values 

20 from -180 degrees to +180 degrees. A positive angle is used to express the angular offset as the 

21 subject rotates from a full-face pose to their right (approaching a left profile). A negative angle is 

22 used to express the angular offset as the subject rotates from a full-face pose to their left 

86 
 

1 (approaching a right profile). If the entry in the POS element is an "F", "L", or "R", the contents of 

2 this element are ignored. 

3 <ansi-nist:FaceImagePoseOffsetAngleMeasure>45 

4 </ansi-nist:FaceImagePoseOffsetAngleMeasure> 

5 215.1.5.20 Element <ansi-nist:FaceImageSubjectPoseCode> 

6 Cross reference: Part-1 Section 15.1.18 Field 10.020: Subject pose (POS) 

7 This optional element is to be used for the exchange of facial image data. When included, this 

8 element shall contain one ASCII character code selected from Table 227 to describe the pose of 

9 the subject. (Table 227 is the same as Table 19 in Part 1.) For the angled pose entry "A", 

10 element <ansi-nist:FaceImagePoseOffsetAngleMeasure> (POA) shall contain the offset angle 

11 from the full face orientation. For the determined 3D pose entry "D", element <ansi12 nist:FaceImage3DPoseAngle> (SPA) shall contain a set of determined 3D pose angles (i.e., Yaw, 

13 Pitch, and Roll angles) away from the full frontal face orientation. Note that the offset angle in 

14 SPA is opposite from the yaw angle in POA as indicated by a minus sign. 

15 Table 227 Subject pose 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Pose description Pose code 

Full Face Frontal F 

Right Profile (90 degree) R 

Left Profile (90 degree) L 

Angled Pose A 

Determined 3D Pose D 

16 

17 <ansi-nist:FaceImageSubjectPoseCode>F 

18 </ansi-nist:FaceImageSubjectPoseCode> 

19 215.1.5.21 Element <itl:FaceImageAcquisitionSource> 

20 Cross reference: Part-1 Section 15.1.21 Field 10.023: Photo acquisition source (PAS) 

21 This optional element shall specify the classification of the source of the image contained in this 

22 record. This element is mandatory if the <ansi-nist:FaceImageAcquisitionProfileCode> (SAP) 

23 entry is "40" or greater. When included, the child element <ansi-nist:CaptureSourceCode> shall 

24 contain an ASCII attribute code selected from Table 228 to describe the source of captured 

25 image data. (Table 228 is the same as Table 21 in Part 1.) 

26 

27 

28 

29 

30 

87 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 228 Acquisition source type codes 

Acquisition source type attribute Attribute code 

Unspecified or unknown UNSPECIFIED 

Static photograph from an unknown source UNKNOWN PHOTO 

Static photograph from a digital still-image camera DIGITAL CAMERA 

Static photograph from a scanner SCANNER 

Single video frame from an unknown source UNKNOWN VIDEO 

Single video frame from an analogue video camera ANALOGUE VIDEO 

Single video frame from a digital video camera DIGITAL VIDEO 

Vendor Specific source VENDOR 

2 The "VENDOR" category is used to enter unlisted or miscellaneous source attributes of the facial 

3 image. This information shall be entered in two child elements. The child element <ansi4 nist:CaptureSourceCode> contains "VENDOR" followed by the child element 

5 <itl:CaptureSourceDescriptionText> containing unformatted text used to describe the attribute. 

6 <itl:FaceImageAcquisitionSource>

7 <ansi-nist:CaptureSourceCode>DIGITAL CAMERA 

8 </ansi-nist:CaptureSourceCode>

9 </itl:FaceImageAcquisitionSource> 

10 Another example: 

11 <itl:FaceImageAcquisitionSource>

12 <ansi-nist:CaptureSourceCode>VENDOR 

13 </ansi-nist:CaptureSourceCode>

14 <itl:CaptureSourceDescriptionText>Text 

15 </itl:CaptureSourceDescriptionText>

16 </itl:FaceImageAcquisitionSource> 

17 215.1.5.22 Element <ansi-nist:PhysicalFeatureDescriptionDetail> 

18 Cross reference: Part-1 Section 15.1.32 Field 10.042: SMT descriptors (SMD) 

19 This optional element is used to describe the content of the SMT image. Its child elements 

20 provide progressively detailed information describing the total image or a portion of the image. 

21 An SMT image consisting of several parts or sub-images shall use multiple occurrences of this 

22 complex parent element to fully describe the various parts or features found in the total image. 

23 The first occurrence shall describe the most predominant feature or sub-image contained in the 

24 SMT image. Subsequent occurrences shall describe additional portions of the image that are not 

25 part of the main or central focal point of the image. For example, a tattoo consisting of a man 

26 with a snake on the arm being followed by a dog may contain three occurrences of <ansi27 nist:PhysicalFeatureDescriptionDetail> - one describing the man, a second describing the snake, 

28 and a third describing the dog. 

29 This complex element contains five child elements described in the subsections below: <ansi30 nist:PhysicalFeatureColorDetail>, <ansi-nist:PhysicalFeatureCategoryCode>, <ansi88 
 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 nist:PhysicalFeatureClassCode>, <ansi-nist:PhysicalFeatureDescriptionText>, and <ansi2 nist:PhysicalFeatureSubClassCode>. 

3 <ansi-nist:PhysicalFeatureDescriptionDetail> 

4 [. . . Tattoo or SMT image description elements . . .] 

</ansi-nist:PhysicalFeatureDescriptionDetail> 

6 215.1.5.22.1 Element <ansi-nist:PhysicalFeatureColorDetail> 

7 Cross reference: Part-1 Section 15.1.33 Field 10.0043: Color (COL) 

8 This is an optional child element of <ansi-nist:PhysicalFeatureDescriptionDetail>. It shall contain 

9 one or more information child elements that list the color(s) of the tattoo or part of the tattoo. The 

child element <ansi-nist:PhysicalFeaturePrimaryColorCode> shall be the predominant color 

11 chosen from Table 230. (Table 230 is the same as Table 30 in Part 1.) Additional colors shall be 

12 entered as information items in one or more occurrences of the child element <ansi13 nist:PhysicalFeatureSecondaryColorCode>. 

14 

16 <ansi-nist:PhysicalFeatureColorDetail>

17 <ansi-nist:PhysicalFeaturePrimaryColorCode>YELLOW 

18 </ansi-nist:PhysicalFeaturePrimaryColorCode>

19 <ansinist:PhysicalFeatureSecondaryColorCode>WHITE 

21 </ansi22 nist:PhysicalFeatureSecondaryColorCode>

23 <ansi-nist:PhysicalFeatureSecondaryColorCode>BLUE 

24 </ansinist:PhysicalFeatureSecondaryColorCode>

26 </ansi-nist:PhysicalFeatureColorDetail>

27 

28 

29 

31 

32 

33 

34 

36 

37 

38 

39 

41 

42 

43 

89 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 229 Color codes 

Color description Color code 

Black BLACK 

Brown BROWN 

Gray GRAY 

Blue BLUE 

Green GREEN 

Orange ORANGE 

Purple PURPLE 

Red RED 

Yellow YELLOW 

White WHITE 

Multi-colored MULTI 

Outlined OUTLINE 

2 

3 215.1.5.22.2 Element <ansi-nist:PhysicalFeatureCategoryCode> 

4 Cross reference: Part-1 Section 15.1.32 Field 10.042: SMT descriptors (SMD), the first subfield 

5 This is a mandatory child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. 

6 This child element shall identify the source of the image as being a scar, a mark, or a tattoo. It 

7 shall contain “SCAR” to indicate healed scar tissue that was the result an accident or medical 

8 procedure. An entry of “MARK” shall be used for the pattern resulting from needle or track marks. 

9 For deliberately applied or drawn images, this element will contain "TATTOO" to indicate a 

10 common tattoo or indelible image resulting from the pricking of the skin with a coloring matter; 

11 "CHEMICAL" if the image was created by the use of chemicals to burn the image into the skin; 

12 "BRANDED" if the image was burned into the skin using a branding iron or other form of heat; or 

13 “CUT” if the image was caused by incision of the skin. 

14 

15 <ansi-nist:PhysicalFeatureCategoryCode>SCAR 

16 </ansi-nist:PhysicalFeatureCategoryCode> 

17 

18 215.1.5.22.3 Element <ansi-nist:PhysicalFeatureClassCode> 

19 Cross reference: Part-1 Section 15.1.32 Field 10.042: SMT descriptors (SMD), the second 

20 subfield 

21 This is a mandatory child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. 

22 This element shall contain the general class code of tattoo chosen from Table 230. (Table 230 is 

23 the same as Table 28 in Part 1.) 

24 

90 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 230 Tattoo classes 

Class description Class code 

Human Forms and Features HUMAN 

Animals and Animal Features ANIMAL 

Plants PLANT 

Flags FLAG 

Objects OBJECT 

Abstractions ABSTRACT 

Insignias & Symbols SYMBOL 

Other Images OTHER 

2 

3 If the <ansi-nist:PhysicalFeatureCategoryCode> is “SCAR” or “MARK”, this element shall contain 

4 the value “OTHER”. 

5 

6 <ansi-nist:PhysicalFeatureClassCode>ABSTRACT 

7 </ansi-nist:PhysicalFeatureClassCode> 

8 

9 215.1.5.22.4 Element <ansi-nist:PhysicalFeatureDescriptionText> 

10 Cross reference: Part-1 Section 15.1.32 Field 10.042: SMT descriptors (SMD), the text string 

11 description subfield 

12 This is an optional child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. It 

13 shall contain an ASCII text string that provides additional qualifiers to describe the image or 

14 portion of the image. For example, to fully describe a tattoo, there may be a class description of 

15 "ANIMAL", with a subclass description of "DOG", and qualified by "golden retriever with an 

16 overbite". 

17 If the <ansi-nist:PhysicalFeatureCategoryCode> is “SCAR” or “MARK”, this element shall contain 

18 a textual description or other information concerning the scar or mark pattern. 

19 

20 <ansi-nist:PhysicalFeatureDescriptionText>Text 

21 </ansi-nist:PhysicalFeatureDescriptionText> 

22 

23 215.1.5.22.5 Element <ansi-nist:PhysicalFeatureSubClassCode> 

24 Cross reference: Part-1 Section 15.1.32 Field 10.042: SMT descriptors (SMD), the subclass 

25 code subfield 

26 This is a mandatory child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. 

27 For each general class of tattoo, identified in the <ansi-nist:PhysicalFeatureClassCode> element, 

28 there are several defined subclasses. This element shall contain the appropriate subclass code 

91 
 

1 selected from Table 231 a-h which lists the various subclasses of tattoos for each of the general 

2 classes. (Table 231 a-h is the same as Table 29 a-h in Part 1.) 

3 If the <ansi-nist:PhysicalFeatureCategoryCode> is “SCAR” or “MARK”, this element shall contain 

4 “MISC”. 

5 

6 <ansi-nist:PhysicalFeatureSubClassCode>DOG 

7 </ansi-nist:PhysicalFeatureSubClassCode> 

8 

9 Table 231 Tattoo subclasses 

10 Table 231a Human tattoo subclasses 12 Table 231b Animal tattoo subclasses 

11 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Subclass Subclass 

code 

Male Face MFACE 

Female Face FFACE 

Abstract Face ABFACE 

Male Body MBODY 

Female Body FBODY 

Abstract Body ABBODY 

Roles (Knight, Witch, man, etc.) ROLES 

Sports Figures (Football Player, 

Skier, etc.) 

SPORT 

Male Body Parts MBPART 

Female Body Parts FBPART 

Abstract Body Parts ABBPART 

Skulls SKULL 

Miscellaneous Human Forms MHUMAN 

Subclass Subclass 

code 

Cats & Cat Heads CAT 

Dogs & Dog Heads DOG 

Other Domestic Animals DOMESTIC 

Vicious Animals (Lions, etc.) VICIOUS 

Horses (Donkeys, Mules, etc.) HORSE 

Other Wild Animals WILD 

Snakes SNAKE 

Dragons DRAGON 

Birds (Cardinal, Hawk, etc.) BIRD 

Spiders, Bugs, and Insects INSECT 

Abstract Animals ABSTRACT 

Animal Parts PARTS 

Miscellaneous Animal Forms MANIMAL 

13 

14 

15 

16 

17 

18 

19 

20 

92 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Table 231c Plant tattoo subclasses 

Subclass Subclass 

code 

Narcotics NARCOTICS 

Red Flowers REDFL 

Blue Flowers BLUEFL 

Yellow Flowers YELFL 

Drawings of Flowers DRAW 

Rose ROSE 

Tulip TULIP 

Lily LILY 

Miscellaneous Plants, Flowers, 

Vegetables 

MPLANT 

5 Table 231e Objects tattoo subclasses 

2 

3 Table 231d Flags tattoo subclasses 

6 

7 Table 231f Abstract tattoo subclasses 

Subclass Subclass 

code 

Fire FIRE 

Weapons(Guns, Arrows, etc.) WEAP 

Airplanes PLANE 

Boats, Ships, & Other Vessels VESSEL 

Trains TRAIN 

Cars, Trucks, and Vehicles VEHICLE 

Mythical (Unicorns, etc.) MYTH 

Sporting Objects (Football, Ski, 

Hurdles, etc.) 

SPORT 

Water & Nature Scenes(Rivers, 

Sky, Trees, etc.) 

NATURE 

Miscellaneous Objects MOBJECTS 

Subclass Subclass code 

Figure(s) FIGURE 

Sleeve SLEEVE 

Bracelet BRACE 

Anklet ANKLET 

Necklace NECKLC 

Shirt SHIRT 

Body Band BODBND 

Head Band HEDBND 

Miscellaneous Abstract MABSTRACT 

Subclass Subclass code 

American Flag USA 

State Flag STATE 

Nazi Flag NAZI 

Confederate Flag CONFED 

British Flag BRIT 

Miscellaneous Flags MFLAG 

4 

8 

93 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 231g Symbols tattoo subclasses 2 Table 231h Other tattoo subclasses 

Subclass Subclass code 

National Symbols NATION 

Political Symbols POLITIC 

Military Symbols MILITARY 

Fraternal Symbols FRATERNAL 

Professional Symbols PROFESS 

Gang Symbols GANG 

Miscellaneous Symbols MSYMBOLS 

3 

Subclass Subclass code 

Wording (Mom, Dad, Mary, 

etc.) 

WORDING 

Freeform Drawings FREEFRM 

Miscellaneous Images MISC 

94 
 

1 215.1.5.23 Element <ansi-nist:PhysicalFeatureNCICCode> 

2 Cross reference: Part-1 Section 15.1.30 Field 10.040: NCIC designation code (SMT) 

3 This element is mandatory for a Type-10 record containing SMT image data. It is used to identify 

4 a general location of the captured scar, mark, tattoo, or other characteristic (including piercings) 

5 in an image. The contents of this element will be an entry chosen from the December, 2000 ninth 

6 (or current) edition of the NCIC Code Manual. The captured image can encompass an area 

7 larger than that specified by a single NCIC body part code for the particular image type. This 

8 situation can be accommodated by listing multiple NCIC codes in separate occurrences of this 

9 element. In this case the primary code is listed first. 

10 For the "marks" category, the NCIC manual lists the common locations for needle track marks. 

11 For other body part locations not listed under the "marks" category, use the body location codes 

12 listed for scars. 

13 <ansi-nist:PhysicalFeatureNCICCode>TAT L TOE 

14 </ansi-nist:PhysicalFeatureNCICCode>

15 <ansi-nist:PhysicalFeatureNCICCode>TAT FARM 

16 </ansi-nist:PhysicalFeatureNCICCode> 

17 215.1.5.24 Element <ansi-nist:PhysicalFeatureSize> 

18 Cross reference: Part-1 Section 15.1.31 Field 10.041: SMT size (SMS) 

19 This optional element shall contain the dimensions of the scar, mark or tattoo. It shall consist of 

20 two child elements. The height shall be contained in the child element <ansi21 nist:PhysicalFeatureHeightMeasure>, and the width shall be contained in the child element <ansi22 nist:PhysicalFeatureWidthMeasure>. Each dimension shall be entered to the nearest centimeter. 

23 <ansi-nist:PhysicalFeatureSize>

24 <ansi-nist:PhysicalFeatureHeightMeasure>112 

25 </ansi-nist:PhysicalFeatureHeightMeasure>

26 <ansi-nist:PhysicalFeatureWidthMeasure>15 

27 </ansi-nist:PhysicalFeatureWidthMeasure>

28 </ansi-nist:PhysicalFeatureSize> 

29 215.2 End of Type-10 logical record 

30 The Type-10 logical record shall end with the XML tag </itl:PackageImageRecord>. 

31 215.3 Additional facial & SMT image records 

32 Additional Type-10 records may be included in the file. For each additional facial or SMT image, 

33 a complete Type-10 logical record is required. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

95 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 216 Type-11 record reserved for future use 

2 217 Type-12 record reserved for future use 

3 218 Type-13 variable-resolution latent image record 

4 The Type-13 logical record shall contain image data acquired from latent fingerprint or palmprint 

images. These images are intended to be transmitted to agencies that will automatically extract 

6 or provide human intervention and processing to extract the desired feature information from the 

7 images. Information regarding the scanning resolution used, the image size, and other 

8 parameters required to process the image, are recorded as XML elements within the record. 

9 218.1 XML elements for the Type-13 logical record 

The following paragraphs describe the data contained in each of the elements for the Type-13 

11 logical record. 

12 Within a Type-13 logical record, entries shall be provided in XML elements. For each element of 

13 the Type-13 record, Table 232 lists the “condition code” as being mandatory “M” or optional “O”, 

14 the XML tag name, and occurrence limits. Elements containing entries in the “IMG” column are 

only applicable to that image type. An entry of “FIN” applies to a fingerprint image, and an entry 

16 of "PAL" applies to a palmprint image. 

17 The Type-13 record shall be contained within this complex element: 

18 <itl:PackageImageRecord> 

19 [. . . Type 13 Record Content . . .] 

</itl:PackageImageRecord> 

21 In the subsections that follow, text in bold between opening and closing tags is informative and 

22 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi23 nist:RecordCategoryCode> for example). 

24 218.1.1 Record length 

Cross reference: Part-1 Section 18.1.1 Field 13.001: Logical record length (LEN) 

26 There is no corresponding Part 2 XML element. 

27 218.1.2 Element <ansi-nist:RecordCategoryCode> 

28 This mandatory Part-2 element has no corresponding field in Part-1. 

29 record type. For the Type-13 record, it shall contain a value of 13. 

<ansi-nist:RecordCategoryCode>13 

31 </ansi-nist:RecordCategoryCode> 

 It is used to identify the 

96 
 

 

 

 

 

 

 

 

 

 

 

 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 232 Type-13 Variable-resolution latent record 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

min Max 

LEN 13.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 13.002 <ansi-nist:ImageReferenceIdentification> 1 1 

UDF O 13.200 – 

13.998 

<itl:UserDefinedFields> -- --

M <itl:FingerprintImage> FIN 1 1 

M <itl:PalmprintImage> PAL 1 1 

DATA M 13.999 <nc:BinaryBase64Object> 1 1 

BPX M 13.012 <ansi-nist:ImageBitsPerPixelQuantity> 1 1 

M <ansi-nist:ImageCaptureDetail> 1 1 

LCD M 13.005 <ansi-nist:CaptureDate> 1 1 

SHPS O 13.016 <ansi-nist:CaptureHorizontalPixelDensityValue> 0 1 

SRC M 13.004 <ansi-nist:CaptureOrganization> 1 1 

SVPS O 13.017 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1 

COM O 13.020 <ansi-nist:ImageCommentText> 0 1 

CGA M 13.011 <ansi-nist:ImageCompressionAlgorithmText> 1 1 

HLL M 13.006 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

HPS M 13.009 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1 

SLC M 13.008 <ansi-nist:ImageScaleUnitsCode> 1 1 

VLL M 13.007 <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1 

VPS M 13.010 <ansi-nist:ImageVerticalPixelDensityValue> 1 1 

IMP M 13.003 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 1 1 

FGP M 13.013 <ansi-nist:FingerPositionCode> FIN 1 6 

FGP M 13.013 <ansi-nist:PalmPositionCode> PAL 1 6 

O <ansi-nist:FingerprintImageMajorCasePrint> 0 1 

SPD O 13.014 <ansi-nist:FingerPositionCode> 0 9 

SPD O 13.014 <ansi-nist:MajorCasePrintCode> 0 9 

PPC O 13.015 <ansi-nist:MajorCasePrintSegmentOffset> 0 12 

LQM O 13.024 <itl:FingerprintImageQuality> FIN 0 --

LQM O 13.024 <itl:PalmprintImageQuality> PAL 0 --

97 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 218.1.3 Element <ansi-nist:ImageReferenceIdentification> 

2 Cross reference: Part-1 Section 18.1.2 Field 13.002: Image designation character (IDC) 

3 This mandatory complex element shall be used to identify the latent image data contained in the 

4 record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

6 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

7 <nc:IdentificationID>, which shall contain the image reference identification datum. 

8 <ansi-nist:ImageReferenceIdentification>

9 <nc:IdentificationID>6</nc:IdentificationID>

</ansi-nist:ImageReferenceIdentification> 

11 218.1.4 Element <itl:UserDefinedFields> 

12 Cross reference: Part-1 Section 18.1.23 Fields 13.200-998: User-defined fields (UDF) 

13 These elements are user-definable. Their size and content shall be defined by the user and be in 

14 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

content values. 

16 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

17 Implementers should define, in an extension schema, a substitution element containing user18 defined child elements from the user’s domain. 

19 A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

21 substitutionGroup="itl:UserDefinedFields"

22 type="user-domain:UserDefinedFieldsType"/>

23 

24 <xsd:complexType name="UserDefinedFieldsType">

<xsd:complexContent>

26 <xsd:extension base="s:ComplexObjectType">

27 <xsd:sequence>

28 <xsd:element ref="user-domain:OneField"/>

29 <xsd:element ref="user-domain:TwoField”"/>

</xsd:sequence>

31 </xsd:extension>

32 </xsd:complexContent>

33 </xsd:complexType> 

34 The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

36 <user-domain:OneField>Text</user-domain:OneField>

37 <user-domain:TwoField>Text</user-domain:TwoField>

38 </user-domain:UserDefinedFields> 

98 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 218.1.5 Element <itl:FingerprintImage> or <itl:PalmprintImage> 

2 This mandatory complex element can take one of two forms. If the Type-13 record contains the 

3 image of a latent fingerprint, the <itl:FingerprintImage> complex element shall be used. If the 

4 record contains the image of a latent palmprint, the <itl:PalmprintImage> complex shall be used. 

All of the remaining elements in the Type-13 record are nested within, as described in the 

6 subsections below. 

7 <itl:FingerprintImage> 

8 [. . . Image elements . . .] 

9 </itl:FingerprintImage> 

or 

11 <itl:PalmprintImage> 

12 [. . . Image elements . . .] 

13 </itl:PalmprintImage> 

14 218.1.5.1 Element <nc:BinaryBase64Object> 

Cross reference: Part-1 Section 18.1.24 Field 13.999: Image data (DATA) 

16 This mandatory element shall contain all of the data from a captured latent image. The binary 

17 image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

18 Each pixel of uncompressed grayscale data shall normally be quantized to eight bits (256 gray 

19 levels) contained in a single byte. If the entry in <ansi-nist:ImageBitsPerPixelQuantity> is greater 

than “8”, the number of bytes required to represent a pixel will be different. If compression is 

21 used, the pixel data shall be compressed in accordance with the compression technique specified 

22 in <ansi-nist:ImageCompressionAlgorithmText>. 

23 <nc:BinaryBase64Object>base64 

24 data</nc:BinaryBase64Object> 

218.1.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

26 Cross reference: Part-1 Section 18.1.12 Field 13.012: Bits per pixel (BPX) 

27 This mandatory element shall contain the number of bits used to represent a pixel. This element 

28 shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

29 greater than “8” shall represent a grayscale pixel with increased precision. 

<ansi-nist:ImageBitsPerPixelQuantity>16 

31 </ansi-nist:ImageBitsPerPixelQuantity> 

32 218.1.5.3 Element <ansi-nist:ImageCaptureDetail> 

33 This mandatory complex element contains four child elements described in the subsections 

34 below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansinist:CaptureOrganization>, and <ansi-nist:CaptureVerticalPixelDensityValue>. 

99 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:ImageCaptureDetail> 

2 [. . . Image capture elements . . .] 

3 </ansi-nist:ImageCaptureDetail> 

4 218.1.5.3.1 Element <ansi-nist:CaptureDate> 

Cross reference: Part-1 Section 18.1.5 Field 13.005: Latent capture date (LCD) 

6 This mandatory element <ansi-nist:CaptureDate> shall contain the date that the latent image 

7 contained in the record was captured. The date shall appear as eight digits, separated by dashes, 

8 in the format YYYY-MM-DD. The YYYY characters shall represent the year the image was 

9 captured; the MM characters shall be the tens and units values of the month; and the DD 

characters shall be the tens and units values of the day in the month. For example, 2008-02-29 

11 represents February 29, 2008. The complete date must be a legitimate date. 

12 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

13 contain capture date data. 

14 

16 

<ansi-nist:CaptureDate>

<nc:Date>2008-02-29</nc:Date>

</ansi-nist:CaptureDate> 

17 218.1.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

18 Cross reference: Part-1 Section 18.1.16 Field 13.016: Scanned horizontal pixel scale (SHPS) 

19 This optional element shall specify the horizontal pixel density used for the scanning of the 

original impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

21 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

22 

23 

<ansi-nist:CaptureHorizontalPixelDensityValue>500 

</ansi-nist:CaptureHorizontalPixelDensityValue> 

24 218.1.5.3.3 Element <ansi-nist:CaptureOrganization> 

Cross reference: Part-1 Section 18.1.4 Field 13.004: Source agency / ORI (SRC) 

26 This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

27 <nc:IdentificationID> the identification of the administration or organization that originally captured 

28 the latent image contained in the record, and may contain in <nc:OrganizationName> the text 

29 name of the organization. Normally, the ORI of the agency that captured the image will be 

contained in <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may 

31 contain up to 36 identifying characters each and the data content of this element shall be defined 

32 by the user and be in accordance with the receiving agency. 

33 Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

34 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

36 contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

37 contain the datum for the text name of the organization. 

38 

100 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:CaptureOrganization>

2 <nc:OrganizationIdentification>

3 <nc:IdentificationID>WI013415Y</nc:Identific

4 ationID> 

</nc:OrganizationIdentification>

6 <nc:OrganizationName>Text</nc:OrganizationName>

7 </ansi-nist:CaptureOrganization> 

8 218.1.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

9 Cross reference: Part-1 Section 18.1.17 Field 13.017: Scanned vertical pixel scale (SVPS) 

This optional element shall specify the vertical pixel density used for the scanning of the original 

11 impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

12 indicates the vertical component of the pixel aspect ratio. 

13 <ansi-nist:CaptureVerticalPixelDensityValue>500 

14 </ansinist:CaptureVerticalPixelDensityValue> 

16 218.1.5.4 Element <ansi-nist:ImageCommentText> 

17 Cross reference: Part-1 Section 18.1.19 Field 13.020: Comment (COM) 

18 This optional element may be used to insert comments or other ASCII text information with the 

19 latent image data. 

<ansi-nist:ImageCommentText>Text</ansi21 nist:ImageCommentText> 

22 218.1.5.5 Element <ansi-nist:ImageCompressionAlgorithmText> 

23 Cross reference: Part-1 Section 18.1.11 Field 13.011: Compression algorithm (CGA) 

24 This mandatory element shall specify the algorithm used to compress the transmitted grayscale 

images. A value of "NONE" in this element indicates that the data contained in this record is 

26 uncompressed. For those images that are to be losslessly compressed, this element shall contain 

27 the text value from Table 201 to indicate the compression method used for the latent fingerprint 

28 images. See Section 205.6.1 for additional information on the usage of JPEG 2000 for the 

29 compression of fingerprint images. The domain registrar shall maintain a registry of acceptable 

compression techniques and corresponding codes that may be used as they become available. 

31 Falafel 

32 <ansi-nist:ImageCompressionAlgorithmText>JPEGB 

33 </ansi-nist:ImageCompressionAlgorithmText> 

34 218.1.5.6 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross reference: Part-1 Section 18.1.6 Field 13.006: Horizontal line length (HLL) 

36 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

37 the transmitted image. 

101 
 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 

2 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

3 </ansi4 nist:ImageHorizontalLineLengthPixelQuantity> 

218.1.5.7 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

6 Cross reference: Part-1 Section 18.1.9 Field 13.009: Horizontal pixel scale (HPS) 

7 This mandatory element shall specify the integer pixel density used in the horizontal direction of 

8 the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

9 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200 

11 </ansi-nist:CaptureHorizontalPixelDensityValue> 

12 218.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

13 Cross reference: Part-1 Section 18.1.8 Field 13.008: Scale units (SLC) 

14 This mandatory element shall specify the units used to describe the image sampling frequency 

(pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per 

16 centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

17 HPS/VPS gives the pixel aspect ratio. 

18 <ansi-nist:ImageScaleUnitsCode>1</ansi19 nist:ImageScaleUnitsCode> 

218.1.5.9 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

21 Cross reference: Part-1 Section 18.1.7 Field 13.007: Vertical line length (VLL) 

22 This mandatory element shall contain the number of horizontal lines contained in the transmitted 

23 image. 

24 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

</ansi-nist:ImageVerticalLineLengthPixelQuantity>

26 

27 218.1.5.10 Element <ansi-nist:ImageVerticalPixelDensityValue> 

28 Cross reference: Part-1 Section 18.1.10 Field 13.010: Vertical pixel scale (VPS) 

29 This mandatory element shall specify the integer pixel density used in the vertical direction of the 

transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

31 Otherwise, it indicates the vertical component of the pixel aspect ratio. 

32 <ansi-nist:ImageVerticalPixelDensityValue>1200 

33 </ansi-nist:ImageVerticalPixelDensityValue>

34 

102 
 

 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 218.1.5.11 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

2 Cross reference: Part-1 Section 18.1.3 Field 13.003: Impression type (IMP) 

3 This mandatory element shall indicate the manner by which the latent image information was 

4 obtained. The appropriate latent code choice selected from Table 211 for finger or palm shall be 

entered in this element. 

6 <ansi7 nist:FingerprintImageImpressionCaptureCategoryCode>4 

8 </ansi9 nist:FingerprintImageImpressionCaptureCategoryCode> 

11 

12 

13 218.1.5.12 Element <ansi-nist:FingerPositionCode> or <ansi-nist:PalmPositionCode> 

14 Cross reference: Part-1 Section 18.1.13 Field 13.013: Finger / palm position (FGP) 

This mandatory element shall contain one or more possible finger or palm positions that may 

16 match the latent image. The required element (<ansi-nist:FingerPositionCode> or <ansi17 nist:PalmPositionCode>) depends upon the data in element <ansi18 nist:FingerprintImageImpressionCaptureCategoryCode> signifying a fingerprint or palmprint 

19 impression type respectively. The decimal code number corresponding to the known or most 

probable finger position shall be taken from Table 212 or the most probable palm position from 

21 Table 235 and entered as a one- or two-character ASCII value. Additional finger and/or palm 

22 positions may be referenced by entering multiple occurrences of the <ansi23 nist:FingerPositionCode> or <ansi-nist:PalmPositionCode> element. The code "0", for "Unknown 

24 Finger", shall be used to reference every finger position from one through ten. The code “20”, for 

“Unknown Palm”, shall be used to reference every listed palmprint position. Code "19" shall be 

26 used to reference one or more parts of an EJI or tip. 

27 If the element <itl:FingerprintImage> is used, then this child element shall be <ansi28 nist:FingerPositionCode>. If the element <itl:PalmprintImage> is used, then this child element 

29 shall be <ansi-nist:PalmPositionCode>. 

This element will contain the finger or palm position code datum. Multiple occurrences of the 

31 element are allowable. The XML code shall be as follows: 

32 <ansi-nist:FingerPositionCode>12</ansi33 nist:FingerPositionCode>

34 <ansi-nist:FingerPositionCode>11</ansinist:FingerPositionCode> 

36 or 

37 <ansi-nist:PalmPositionCode>27</ansi38 nist:PalmPositionCode> 

39 <ansi-nist:PalmPositionCode>26</ansinist:PalmPositionCode> 

103 
 

1 218.1.5.13 Element <ansi-nist:FingerprintImageMajorCasePrint> 

2 This complex element shall be present if and only if the value contained by <ansi3 nist:FingerPositionCode> is equal to “19”. This parent element contains three child elements: 

4 <ansi-nist:FingerPositionCode>, <ansi-nist:MajorCasePrintCode>, and <ansi5 nist:MajorCasePrintSegmentOffset>. 

6 218.1.5.13.1 Element <ansi-nist:FingerPositionCode> 

7 Cross reference: Part-1 Section 18.1.14 Field 13.014: Search Position Descriptors (SPD) – First 

8 information item 

9 This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

10 when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. It is used to 

11 narrow the search of the latent image in this record against a database. This element is the 

12 probable decimal finger position code (0-10) taken from Table 212. A "0" indicates that all the 

13 fingers of a possible candidate should be searched. 

14 <ansi-nist:FingerPositionCode>8 

15 </ansi-nist:FingerPositionCode> 

16 218.1.5.13.2 Element <ansi-nist:MajorCasePrintCode> 

17 Cross reference: Part-1 Section 18.1.14 Field 13.014: Search Position Descriptors (SPD) – 

18 Second information item 

19 This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

20 when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. It is used to 

21 narrow the search of the latent image in this record against a database. This element is the code 

22 taken from Table 233 to indicate the portion of the EJI or tip image in the database to search. 

23 (Table 233 is the same as Table 32 in Part 1.) Latent images of full-length fingers use codes FV1 

24 through FV4 as defined in Table 233. Figure 7 is an illustration of the Entire Joint Image for a 

25 middle finger with each of the full finger views and constituent parts identified. The EJI code is 

26 used for the case where all four finger images are to be considered. For the case where the 

27 latent is to be compared to proximal, distal, or medial segments of a finger, this information item 

28 will contain the appropriate finger segment character. 

29 <ansi-nist:MajorCasePrintCode>EJI 

30 </ansi-nist:MajorCasePrintCode> 

31 

32 

33 

34 

35 

36 

37 

38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

104 
 

 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 233 EJI and tip codes 

TYPE OF IMAGE IMAGE CODE 

Entire Joint Image EJI 

Rolled Tip TIP 

Full Finger Rolled Image FV1 

Full Finger Plain Image – left side FV2 

Full Finger Plain Image – center FV3 

Full Finger Plain Image – right side FV4 

Proximal, Distal, or Medial Segments PRX, DST, MED 

2 

3 NOTE: Elements FingerPositionCode and PalmPositionCode are included to make the standard 

4 flexible enough to accommodate many different scenarios and applications. These two elements 

5 facilitate searching of latents formatted within Type-13 records against Type-14 records contained 

6 in the various database files. The search of a database by a latent can be narrowed with the use 

7 of additional information such as finger position, finger segment, or full finger view. It is unlikely 

8 that an entire EJI will ever be left at the scene of a crime. But a latent can be searched against 

9 the EJIs in an image or features file based on a specific finger segment or full finger view. This 

10 can be accomplished for a portion of the latent described by the X and Y coordinates. 

 Distal 

Medial 

Proximal 

11 

FV1 FV2 FV3 FV4 

12 Figure 7 Entire joint image 

13 

14 

15 

105 
 

45 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 218.1.5.13.3 Element <ansi-nist:MajorCasePrintSegmentOffset> 

2 Cross reference: Part-1 Section 18.1.15 Field 13.015: Print Position Coordinates (PPC) 

3 This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

4 when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. 

5 This element contains offsets to the locations for the bounding box of the EJI, each of the full 

6 finger views, or segments within the EJI. When used, this complex element shall consist of six 

7 (6) mandatory information items to describe the type or portion of the latent image contained in 

8 this record and its location within an entire joint image. The information item <ansi9 nist:SegmentFingerViewCode> is the number of the full finger view with values of "FV1" through 

10 "FV4". Values of “FV1” to “FV4” specify the bounding coordinates for each full finger view. The 

11 information item <ansi-nist:SegmentLocationCode> is used to identify the location of a segment 

12 within a full finger view. It will contain the not applicable code “NA” if the image portion refers to a 

13 full finger view or to the entire joint image locations. It shall contain “PRX”, “DST”, “MED” for a 

14 proximal, distal, or medial segment. The next four information items are the horizontal and vertical 

15 offsets relative to the origin positioned in the upper left corner of the image. The horizontal 

16 offsets (X) are the pixel counts to the right, and the vertical offsets (Y) are the pixel counts down. 

17 The location of the image portion is defined by the sequence of X coordinates (LEFT=<ansi18 nist:SegmentLeftHorizontalCoordinateValue>, RIGHT=<ansi19 nist:SegmentRightHorizontalCoordinateValue>) and the Y coordinates (TOP=<ansi20 nist:SegmentTopVerticalCoordinateValue>, BOTTOM=<ansi21 nist:SegmentBottomVerticalCoordinateValue>), of its bounding box. For the case of a fingertip, 

22 <ansi-nist:SegmentFingerViewCode> shall be “TIP”, and <ansi-nist:SegmentLocationCode> shall 

23 be “NA”. The collection of six subelements will describe either the location of the entire joint 

24 image, one full finger view, or segment. Individual full finger or segment definitions may be 

25 repeated as multiple occurrences of <ansi-nist:MajorCasePrintSegmentOffset>. 

26 Element <ansi-nist:MajorCasePrintSegmentOffset> shall have six child elements: <ansi27 nist:SegmentBottomVerticalCoordinateValue>, <ansi-nist:SegmentLocationCode>, <ansi28 nist:SegmentFingerViewCode>, <ansi-nist:SegmentLeftHorizontalCoordinateValue>, <ansi29 nist:SegmentRightHorizontalCoordinateValue>, and <ansi30 nist:SegmentTopVerticalCoordinateValue>. 

31 Part-1 cross reference information: Element <ansi-nist:SegmentBottomVerticalCoordinateValue> 

32 shall correspond to the sixth information in field 13.015. Element <ansi33 nist:SegmentLocationCode> shall correspond to the second information item in field 13.015. 

34 Element <ansi-nist:SegmentFingerViewCode> shall correspond to the first information item in 

35 field 13.015. Element <ansi-nist:SegmentLeftHorizontalCoordinateValue> shall correspond to the 

36 third information item in field 13.015. Element <ansi37 nist:SegmentRightHorizontalCoordinateValue> shall correspond to the fourth information item in 

38 field 13.015. Element <ansi-nist:SegmentTopVerticalCoordinateValue> shall correspond to the 

39 fifth information item in field 13.015. 

40 At least one occurrence of this subelement <ansi-nist:MajorCasePrintSegmentOffset> is 

41 mandatory. In practice, multiple occurrences may be used to describe the bounding boxes of 

42 multiple finger segments, or multiple full finger views. 

43 

44 

106 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

The XML code shall be as follows: 

<ansi-nist:MajorCasePrintSegmentOffset>

<ansinist:SegmentBottomVerticalCoordinateValue>85 

</ansinist:SegmentBottomVerticalCoordinateValue>

<ansi-nist:SegmentLocationCode>DST 

</ansi-nist:SegmentLocationCode>

<ansi-nist:SegmentFingerViewCode>FV1 

</ansi-nist:SegmentFingerViewCode>

<ansinist:SegmentLeftHorizontalCoordinateValue>115 

</ansinist:SegmentLeftHorizontalCoordinateValue>

<ansinist:SegmentRightHorizontalCoordinateValue>188 

</ansinist:SegmentRightHorizontalCoordinateValue>

<ansi-nist:SegmentTopVerticalCoordinateValue>55 

</ansinist:SegmentTopVerticalCoordinateValue>

</ansi-nist:MajorCasePrintSegmentOffset> 

218.1.5.14 Element <itl:FingerprintImageQuality> or <itl:PalmprintImageQuality> 

Cross reference: Part-1 Section 18.1.21 Field 13.024: Latent quality metric (LQM) 

This optional complex element <itl:FingerprintImageQuality> or <itl:PalmprintImageQuality> is 

used to specify one or more different metrics of latent image quality score data for the image 

stored in this record. The meaning attributed to this metric must be defined and interpreted by 

the producer of the scoring algorithm or by the person or system used to assign the metric to the 

latent image. The metric may be a predictor of AFIS matcher accuracy performance or a different 

metric to indicate a value associated with the quality of the latent image for a particular function. 

If the <itl:FingerprintImage> complex element is used, then the optional complex element 

<itl:FingerprintImageQuality> should be used. It shall have four child elements: <ansinist:FingerPositionCode>, <ansi-nist:QualityAlgorithmProductIdentification>, <ansinist:QualityAlgorithmVendorIdentification>, and <ansi-nist:QualityValue>. 

If the <itl:PalmprintImage> complex element is used, then the optional complex element 

<itl:PalmprintImageQuality> should be used. It shall have four child elements: <ansinist:PalmPositionCode>, <ansi-nist:QualityAlgorithmProductIdentification>, <ansinist:QualityAlgorithmVendorIdentification>, and <ansi-nist:QualityValue>. 

The first information item is a finger or palm position code. In <itl:FingerprintImageQuality>, the 

information item <ansi-nist:FingerPositionCode> shall contain a code chosen from Table 212. In 

<itl:PalmprintImageQuality>, the information item <ansi-nist:PalmPositionCode> shall contain a 

code chosen from Table 235. (This corresponds to the first information item in 13.024.) 

107 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

45 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 The other three items identify a quality score and the algorithm used to create the quality score. 

2 This information is useful to enable the recipient of the quality score to differentiate between 

3 quality scores generated by different algorithms and adjust for any differences in processing or 

4 analysis as necessary. 

• The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

6 <nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

7 quality algorithm, which may be registered with the IBIA, but registration is not required. It 

8 indicates which of the vendor’s algorithms was used in the calculation of the quality 

9 score. This element contains the ASCII representation of the integer product code and 

should be within the range 1 to 65535. Element <ansi11 nist:QualityAlgorithmProductIdentification> shall have a child element 

12 <nc:IdentificationID>, which will contain the numeric product code datum. (This 

13 corresponds to the fourth information item in 13.024.) 

14 • The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

<nc:IdentificationID> shall specify the ID of the vendor of the quality algorithm used to 

16 calculate the quality score. This 4-digit hex value is assigned by IBIA and expressed as 

17 four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF Biometric 

18 Organizations that will map the value in this element to a registered organization. 

19 Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

21 third information item in 13.024.) 

22 • The information item <ansi-nist:QualityValue> shall be a quantitative expression of the 

23 predicted matching performance of the biometric sample. This item contains the ASCII 

24 representation of the integer image quality score between 0 and 100 assigned to the 

image data by a quality algorithm. Higher values indicate better quality. An entry of 

26 “255” shall indicate a failed attempt to calculate a quality score. An entry of “254” shall 

27 indicate that no attempt to calculate a quality score was made. The use of additional 

28 values to convey other information should be harmonized with ISO/IEC 19794 standards. 

29 (This corresponds to the second information item in 13.024.) 

The complex element <itl:FingerprintImageQuality> or <itl:PalmprintImageQuality> may be 

31 repeated for each quality algorithm used. 

32 <itl:FingerprintImageQuality>

33 <ansi-nist:FingerPositionCode>4 

34 </ansi-nist:FingerPositionCode>

<ansi36 nist:QualityAlgorithmProductIdentification>

37 

38 <nc:IdentificationID>28495</nc:IdentificationID>

39 </ansinist:QualityAlgorithmProductIdentification>

41 <ansi42 nist:QualityAlgorithmVendorIdentification>

43 

44 <nc:IdentificationID>FFF0</nc:IdentificationID>

</ansi46 nist:QualityAlgorithmVendorIdentification> 

108 
 

 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:QualityValue>100</ansi2 nist:QualityValue>

3 </itl:FingerprintImageQuality> 

4 or 

<itl:PalmprintImageQuality>

6 <ansi-nist:PalmPositionCode>29 

7 </ansi-nist:PalmPositionCode>

8 <ansi9 nist:QualityAlgorithmProductIdentification> 

11 <nc:IdentificationID>28495</nc:IdentificationID>

12 </ansi13 nist:QualityAlgorithmProductIdentification>

14 <ansinist:QualityAlgorithmVendorIdentification>

16 

17 <nc:IdentificationID>FFF0</nc:IdentificationID>

18 </ansi19 nist:QualityAlgorithmVendorIdentification>

<ansi-nist:QualityValue>100</ansi21 nist:QualityValue>

22 </itl:PalmprintImageQuality> 

23 218.2 Additional variable-resolution latent image records 

24 Additional Type-13 records may be included in the file. For each additional latent image, a 

complete Type-13 logical record is required. 

26 219 Type-14 variable-resolution fingerprint image record 

27 The Type-14 logical record shall contain and be used to exchange fingerprint image data from a 

28 rolled tenprint, an identification flat, or a major case print (also referred to as a complete friction 

29 ridge exemplar). All fingerprint impressions shall be acquired from a tenprint card, a major case 

print card, or from a live-scan device. Captured images are intended to be transmitted to 

31 agencies that will automatically extract the desired feature information from the images for 

32 matching purposes. Textual information regarding the scanning resolution, the image size and 

33 other parameters or comments required to process the image are recorded as XML elements 

34 within the record. 

The Type-14 record is also used to exchange identification flats (simultaneous plain impressions 

36 captured on a platen) for civil background checks. Rolled images are generally not used for this 

37 application. Three Type-14 image records are used to contain the flat fingerprint impressions. 

38 Two of the image records contain the left and right simultaneous four fingers, and the third 

39 contains the two thumbs. Offsets to the locations of image segments containing the individual 

fingers are included with the image records. Additional fields are defined to contain the NIST 

41 Fingerprint Image Quality (NFIQ) metric, alternate image quality metrics, and metrics for 

42 predicting the correctness of the segmentation. 

109 
 

 

 

 

 

 

 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 219.1 XML elements for the Type-14 logical record 

2 The following paragraphs describe the data contained in each of the elements for the Type-14 

3 logical record. 

4 Within a Type-14 logical record, entries shall be provided in XML elements. For each element of 

5 the Type-14 record, Table 234 lists the “condition code” as being mandatory “M” or optional “O”, 

6 the XML tag name, and occurrence limits. 

7 The Type-14 record shall be contained within this complex element: 

8 <itl:PackageImageRecord> 

9 [. . . Type 14 Record Content . . .] 

10 </itl:PackageImageRecord> 

11 In the subsections that follow, text in bold between opening and closing tags is informative and 

12 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi13 nist:RecordCategoryCode> for example). 

14 

15 Table 234 Type-14 Variable-resolution fingerprint record 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

min Max 

LEN 14.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 14.002 <ansi-nist:ImageReferenceIdentification> 1 1 

UDF O 14.200 – 

14.998 

<itl:UserDefinedFields> -- --

M <itl:FingerprintImage> 1 1 

DATA M 14.999 <nc:BinaryBase64Object> 1 1 

BPX M 14.012 <ansi-nist:ImageBitsPerPixelQuantity> 1 1 

<ansi-nist:ImageCaptureDetail> 1 1 

FCD M 14.005 <ansi-nist:CaptureDate> 1 1 

SHPS O 14.016 <ansi-nist:CaptureHorizontalPixelDensityValue> 0 1 

SRC M 14.004 <ansi-nist:CaptureOrganization> 1 1 

SVPS O 14.017 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1 

DMM O 14.030 <ansi-nist:CaptureDeviceMonitoringModeCode> 0 1 

COM O 14.020 <ansi-nist:ImageCommentText> 0 1 

110 
 

 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

min Max 

CGA M 14.011 <ansi-nist:ImageCompressionAlgorithmText> 1 1 

HLL M 14.006 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

HPS M 14.009 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1 

SLC M 14.008 <ansi-nist:ImageScaleUnitsCode> 1 1 

VLL M 14.007 <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1 

VPS M 14.010 <ansi-nist:ImageVerticalPixelDensityValue> 1 1 

IMP M 14.003 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 1 1 

FGP M 14.013 <ansi-nist:FingerPositionCode> 1 6 

O <ansi-nist:FingerprintImageMajorCasePrint> 0 1 

PPD O 14.014 <ansi-nist:FingerPositionCode> 0 1 

PPD O 14.014 <ansi-nist:MajorCasePrintCode> 0 1 

PPC O 14.015 <ansi-nist:MajorCasePrintSegmentOffset> 0 12 

AMP O 14.018 <itl:FingerprintImageFingerMissing> 0 4 

SEG O 14.021 <itl:FingerprintImageSegmentPositionSquare> 0 --

NQM O 14.022 <ansi-nist:FingerprintImageNISTQuality> 0 4 

SQM O 14.023 <ansi-nist:FingerprintImageSegmentationQuality> 0 --

FQM O 14.024 <itl:FingerprintImageQuality> 0 --

ASEG O 14.025 <itl:FingerprintImageSegmentPositionPolygon> 0 4 

1 

2 219.1.1 Record length 

3 Cross reference: Part-1 Section 19.1.1 Field 14.001: Logical record length (LEN) 

4 There is no corresponding Part 2 XML element. 

5 219.1.2 Element <ansi-nist:RecordCategoryCode> 

6 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

7 record type. For the Type-14 record, it shall contain a value of 14. 

8 <ansi-nist:RecordCategoryCode>14</ansi9 nist:RecordCategoryCode>

10 

111 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 219.1.3 Element <ansi-nist:ImageReferenceIdentification> 

2 Cross reference: Part-1 Section 19.1.2 Field 14.002: Image designation character (IDC) 

3 This mandatory complex element shall be used to identify the fingerprint image data contained in 

4 the record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

6 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

7 <nc:IdentificationID>, which shall contain the image reference identification datum. 

8 <ansi-nist:ImageReferenceIdentification>

9 <nc:IdentificationID>10</nc:IdentificationID>

</ansi-nist:ImageReferenceIdentification> 

11 219.1.4 Element <itl:UserDefinedFields> 

12 Cross reference: Part-1 Section 19.1.29 Fields 14.200-998: User-defined fields (UDF) 

13 These elements are user-definable. Their size and content shall be defined by the user and be in 

14 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

content values. 

16 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

17 Implementers should define, in an extension schema, a substitution element containing user18 defined child elements from the user’s domain. 

19 A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

21 substitutionGroup="itl:UserDefinedFields"

22 type="user-domain:UserDefinedFieldsType"/>

23 

24 <xsd:complexType name="UserDefinedFieldsType">

<xsd:complexContent>

26 <xsd:extension base="s:ComplexObjectType">

27 <xsd:sequence>

28 <xsd:element ref="user-domain:OneField"/>

29 <xsd:element ref="user-domain:TwoField”"/>

</xsd:sequence>

31 </xsd:extension>

32 </xsd:complexContent>

33 </xsd:complexType> 

34 The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

36 <user-domain:OneField>Text</user-domain:OneField>

37 <user-domain:TwoField>Text</user-domain:TwoField>

38 </user-domain:UserDefinedFields> 

112 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 219.1.5 Element <itl:FingerprintImage> 

2 This mandatory complex element contains the remaining elements in the Type-14 record, as 

3 described in the subsections below. 

4 <itl:FingerprintImage> 

[. . . Image elements . . .] 

6 </itl:FingerprintImage> 

7 219.1.5.1 Element <nc:BinaryBase64Object> 

8 Cross reference: Part-1 Section 19.1.30 Field 14.999: Image data (DATA) 

9 This mandatory element shall contain all of the data from a captured tenprint image. The binary 

image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

11 Each pixel of uncompressed grayscale data shall normally be quantized to eight bits (256 gray 

12 levels) contained in a single byte. If the entry in <ansi-nist:ImageBitsPerPixelQuantity> is greater 

13 than “8”, the number of bytes required to represent a pixel will be different. If compression is 

14 used, the pixel data shall be compressed in accordance with the compression technique specified 

in <ansi-nist:ImageCompressionAlgorithmText>. 

16 <nc:BinaryBase64Object>base64 

17 data</nc:BinaryBase64Object> 

18 219.1.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

19 Cross reference: Part-1 Section 19.1.12 Field 14.012: Bits per pixel (BPX) 

This mandatory element shall contain the number of bits used to represent a pixel. This element 

21 shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

22 greater than “8” shall represent a grayscale pixel with increased precision. 

23 <ansi-nist:ImageBitsPerPixelQuantity>8 

24 </ansi-nist:ImageBitsPerPixelQuantity> 

219.1.5.3 Element <ansi-nist:ImageCaptureDetail> 

26 This mandatory complex element contains five child elements described in the subsections 

27 below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansi28 nist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansi29 nist:CaptureDeviceMonitoringModeCode>. 

<ansi-nist:ImageCaptureDetail> 

31 [. . . Image capture elements . . .] 

32 </ansi-nist:ImageCaptureDetail> 

33 

113 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 219.1.5.3.1 Element <ansi-nist:CaptureDate> 

2 Cross reference: Part-1 Section 19.1.5 Field 14.005: Fingerprint capture date (FCD) 

3 This mandatory element <ansi-nist:CaptureDate> shall contain the date that the image contained 

4 in the record was captured. The date shall appear as eight digits, separated by dashes, in the 

format YYYY-MM-DD. The YYYY characters shall represent the year the image was captured; 

6 the MM characters shall be the tens and units values of the month; and the DD characters shall 

7 be the tens and units values of the day in the month. For example, 2008-02-29 represents 

8 February 29, 2008. The complete date must be a legitimate date. 

9 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

11 <ansi-nist:CaptureDate>

12 <nc:Date>2008-02-29</nc:Date>

13 </ansi-nist:CaptureDate> 

14 219.1.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

Cross reference: Part-1 Section 19.1.16 Field 14.016: Scanned horizontal pixel scale (SHPS) 

16 This optional element shall specify the horizontal pixel density used for the scanning of the 

17 original impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

18 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

19 <ansi-nist:CaptureHorizontalPixelDensityValue>500 

</ansi-nist:CaptureHorizontalPixelDensityValue> 

21 219.1.5.3.3 Element <ansi-nist:CaptureOrganization> 

22 Cross reference: Part-1 Section 19.1.4 Field 14.004: Source agency / ORI (SRC) 

23 This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

24 <nc:IdentificationID> the identification of the administration or organization that originally captured 

the fingerprint images contained in the record, and may contain in <nc:OrganizationName> the 

26 text name of the organization. Normally, the ORI of the agency that captured the image will be 

27 contained in <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may 

28 contain up to 36 identifying characters each and the data content of this element shall be defined 

29 by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

31 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

32 <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

33 contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

34 contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization>

36 <nc:OrganizationIdentification>

37 <nc:IdentificationID>WI013415Y</nc:Identific

38 ationID> 

39 </nc:OrganizationIdentification>

<nc:OrganizationName>Text</nc:OrganizationName>

41 </ansi-nist:CaptureOrganization> 

114 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 219.1.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

2 Cross reference: Part-1 Section 19.1.17 Field 14.017: Scanned vertical pixel scale (SVPS) 

3 This optional element shall specify the vertical pixel density used for the scanning of the original 

4 impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

6 <ansi-nist:CaptureVerticalPixelDensityValue>500 

7 </ansi8 nist:CaptureVerticalPixelDensityValue> 

9 219.1.5.3.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross reference: Part-1 Section 19.1.27 Field 14.030 Device monitoring mode (DMM) 

11 This optional element provides information describing the level of human monitoring for the image 

12 capture device. This element will contain an entry from Table 219 to indicate the monitoring 

13 mode of the biometric sample capture device. 

14 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED 

</ansi-nist:CaptureDeviceMonitoringModeCode> 

16 219.1.5.4 Element <ansi-nist:ImageCommentText> 

17 Cross reference: Part-1 Section 19.1.20 Field 14.020: Comment (COM) 

18 This optional element may be used to insert comments or other ASCII text information with the 

19 image data. 

<ansi-nist:ImageCommentText>Text</ansi21 nist:ImageCommentText> 

22 219.1.5.5 Element <ansi-nist:ImageCompressionAlgorithmText> 

23 Cross reference: Part-1 Section 19.1.11 Field 14.011: Compression algorithm (CGA) 

24 This mandatory element shall specify the algorithm used to compress the transmitted grayscale 

images. A value of "NONE" in this element indicates that the data contained in this record is 

26 uncompressed. For those images that are to be compressed, this element shall contain the text 

27 value from Table 201 to indicate the compression method used for this record type. The 

28 preferred methods for the compression of fingerprint images are WSQ for those images scanned 

29 or transmitted at 500 ppi or JPEG 2000 for those images scanned and transmitted at 1000 ppi. 

See Section 205.6.1and the Profile for 1000 ppi Fingerprint Compression for additional 

31 information on the usage of JPEG 2000 for the compression of fingerprint images. The domain 

32 registrar maintains a registry of acceptable compression techniques and corresponding codes 

33 that may be used as they become available. 

34 <ansi-nist:ImageCompressionAlgorithmText>WSQ

</ansi-nist:ImageCompressionAlgorithmText>

36 

37 

115 
 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 219.1.5.6 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

2 Cross reference: Part-1 Section 19.1.6 Field 14.006: Horizontal line length (HLL) 

3 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

4 the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

6 </ansi7 nist:ImageHorizontalLineLengthPixelQuantity> 

8 219.1.5.7 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

9 Cross reference: Part-1 Section 19.1.9 Field 14.009: Horizontal pixel scale (HPS) 

This mandatory element shall specify the integer pixel density used in the horizontal direction of 

11 the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

12 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

13 <ansi-nist:CaptureHorizontalPixelDensityValue>1200 

14 </ansi-nist:CaptureHorizontalPixelDensityValue> 

219.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

16 Cross reference: Part-1 Section 19.1.8 Field 14.008: Scale units (SLC) 

17 This mandatory element shall specify the units used to describe the image sampling frequency 

18 (pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per 

19 centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

21 <ansi-nist:ImageScaleUnitsCode>1</ansi22 nist:ImageScaleUnitsCode> 

23 219.1.5.9 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

24 Cross reference: Part-1 Section 19.1.7 Field 14.007: Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

26 image. 

27 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

28 </ansi-nist:ImageVerticalLineLengthPixelQuantity>

29 

219.1.5.10 Element <ansi-nist:ImageVerticalPixelDensityValue> 

31 Cross reference: Part-1 Section 19.1.10 Field 14.010: Vertical pixel scale (VPS) 

32 This mandatory element shall specify the integer pixel density used in the vertical direction of the 

33 transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

34 Otherwise, it indicates the vertical component of the pixel aspect ratio. 

116 
 

1 <ansi-nist:ImageVerticalPixelDensityValue>1200 

2 </ansi-nist:ImageVerticalPixelDensityValue> 

3 219.1.5.11 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

4 Cross reference: Part-1 Section 19.1.3 Field 14.003: Impression type (IMP) 

5 This mandatory element shall indicate the manner by which the fingerprint image information was 

6 obtained. The appropriate code choice selected from Table 211 shall be entered in this element. 

7 <ansi8 nist:FingerprintImageImpressionCaptureCategoryCode>1 

9 </ansi10 nist:FingerprintImageImpressionCaptureCategoryCode> 

11 219.1.5.12 Element <ansi-nist:FingerPositionCode> 

12 Cross reference: Part-1 Section 19.1.13 Field 14.013: Finger position (FGP) 

13 This mandatory element shall contain the finger position that matches the tenprint image. The 

14 decimal code number corresponding to the known or most probable finger position shall be taken 

15 from Table 212 and entered as a one- or two-character ASCII value. Table 212 also lists the 

16 maximum image dimensions that can be transmitted for each of the sixteen possible finger 

17 positions. Additional finger positions may be referenced in the transaction. The code "0", for 

18 "Unknown Finger", shall be used to reference every finger position from one through ten. Code 

19 "19" shall be used to reference one or more parts of an EJI or tip. 

20 <ansi-nist:FingerPositionCode>8</ansi21 nist:FingerPositionCode> 

22 219.1.5.13 Element <ansi-nist:FingerprintImageMajorCasePrint> 

23 This complex element shall be present if and only if the value contained by <ansi24 nist:FingerPositionCode> is equal to “19”. This parent element contains three child elements: 

25 <ansi-nist:FingerPositionCode>, <ansi-nist:MajorCasePrintCode>, and <ansi26 nist:MajorCasePrintSegmentOffset>. 

27 219.1.5.13.1 Element <ansi-nist:FingerPositionCode> 

28 Cross reference: Part-1 Section 19.1.14 Field 14.014: Print Position Descriptors (PPD) – First 

29 information item 

30 This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

31 when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. This element is the 

32 probable decimal finger position code (0-10) taken from Table 212. 

33 <ansi-nist:FingerPositionCode>8</ansi34 nist:FingerPositionCode> 

35 219.1.5.13.2 Element <ansi-nist:MajorCasePrintCode> 

36 Cross reference: Part-1 Section 19.1.14 Field 14.014: Print Position Descriptors (PPD) – Second 

37 information item 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

117 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

2 when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. This element is the 

3 code taken from Table 233 to indicate the portion of the EJI or tip image that is stored as a single 

4 image in the database. There may be up to 17 such images for a single finger. Images of full5 length fingers use codes FV1 through FV4 as defined in Table 233. Figure 7 is an illustration of 

6 the Entire Joint Image for a middle finger with each of the full finger views and constituent parts 

7 identified. 

8 <ansi-nist:MajorCasePrintCode>EJI</ansi9 nist:MajorCasePrintCode> 

10 219.1.5.13.3 Element <ansi-nist:MajorCasePrintSegmentOffset> 

11 Cross reference: Part-1 Section 19.1.15 Field 14.015: Print Position Coordinates (PPC) 

12 This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

13 when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. 

14 This element contains offsets to the locations for the bounding box of the EJI, each of the full 

15 finger views, or segments within the EJI. When used, this complex element shall consist of six 

16 (6) mandatory information items to describe the type or portion of the image contained in this 

17 record and its location within an entire joint image. The information item <ansi18 nist:SegmentFingerViewCode> is the number of the full finger view with values of "FV1" through 

19 "FV4". Values of “FV1” to “FV4” specify the bounding coordinates for each full finger view. The 

20 information item <ansi-nist:SegmentLocationCode> is used to identify the location of a segment 

21 within a full finger view. It will contain the not applicable code “NA” if the image portion refers to a 

22 full finger view or to the entire joint image locations. It shall contain “PRX”, “DST”, “MED” for a 

23 proximal, distal, or medial segment. The next four information items are the horizontal and vertical 

24 offsets relative to the origin positioned in the upper left corner of the image. The horizontal 

25 offsets (X) are the pixel counts to the right, and the vertical offsets (Y) are the pixel counts down. 

26 The location of the image portion is defined by the sequence of X coordinates (LEFT=<ansi27 nist:SegmentLeftHorizontalCoordinateValue>, RIGHT=<ansi28 nist:SegmentRightHorizontalCoordinateValue>) and the Y coordinates (TOP=<ansi29 nist:SegmentTopVerticalCoordinateValue>, BOTTOM=<ansi30 nist:SegmentBottomVerticalCoordinateValue>), of its bounding box. For the case of a fingertip, 

31 <ansi-nist:SegmentFingerViewCode> shall be “TIP”, and <ansi-nist:SegmentLocationCode> shall 

32 be “NA”. The collection of six subelements will describe either the location of the entire joint 

33 image, one full finger view, or segment. Individual full finger or segment definitions may be 

34 repeated as multiple occurrences of <ansi-nist:MajorCasePrintSegmentOffset>. 

35 Element <ansi-nist:MajorCasePrintSegmentOffset> shall have six child elements: <ansi36 nist:SegmentBottomVerticalCoordinateValue>, <ansi-nist:SegmentLocationCode>, <ansi37 nist:SegmentFingerViewCode>, <ansi-nist:SegmentLeftHorizontalCoordinateValue>, <ansi38 nist:SegmentRightHorizontalCoordinateValue>, and <ansi39 nist:SegmentTopVerticalCoordinateValue>. 

40 Part-1 cross reference information: Element <ansi-nist:SegmentBottomVerticalCoordinateValue> 

41 shall correspond to the sixth information in field 14.015. Element <ansi42 nist:SegmentLocationCode> shall correspond to the second information item in field 14.015. 

43 Element <ansi-nist:SegmentFingerViewCode> shall correspond to the first information item in 

44 field 14.015. Element <ansi-nist:SegmentLeftHorizontalCoordinateValue> shall correspond to the 

45 third information item in field 14.015. Element <ansi46 nist:SegmentRightHorizontalCoordinateValue> shall correspond to the fourth information item in 

118 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 field 14.015. Element <ansi-nist:SegmentTopVerticalCoordinateValue> shall correspond to the 

2 fifth information item in field 14.015. 

3 At least one occurrence of this subelement <ansi-nist:MajorCasePrintSegmentOffset> is 

4 mandatory. In practice, multiple occurrences may be used to describe the bounding boxes of 

multiple finger segments, or multiple full finger views. 

6 <ansi-nist:MajorCasePrintSegmentOffset>

7 <ansi8 nist:SegmentBottomVerticalCoordinateValue>85 

9 </ansinist:SegmentBottomVerticalCoordinateValue>

11 <ansi-nist:SegmentLocationCode>DST 

12 </ansi-nist:SegmentLocationCode>

13 <ansi-nist:SegmentFingerViewCode>FV1 

14 </ansi-nist:SegmentFingerViewCode>

<ansi16 nist:SegmentLeftHorizontalCoordinateValue>115 

17 </ansi18 nist:SegmentLeftHorizontalCoordinateValue>

19 <ansinist:SegmentRightHorizontalCoordinateValue>188 

21 </ansi22 nist:SegmentRightHorizontalCoordinateValue>

23 <ansi-nist:SegmentTopVerticalCoordinateValue>55 

24 </ansinist:SegmentTopVerticalCoordinateValue>

26 </ansi-nist:MajorCasePrintSegmentOffset> 

27 219.1.5.14 Element <itl:FingerprintImageFingerMissing> 

28 Cross reference: Part-1 Section 19.1.18 Field 14.018: Amputated or bandaged (AMP) 

29 This optional complex element shall specify if one or more fingers are amputated or bandaged. 

This element has two child elements which will be repeated for each amputated or missing finger: 

31 <ansi-nist:FingerPositionCode> and <itl:FingerMissingCode>. Element <ansi32 nist:FingerPositionCode> is the finger number between one and ten as chosen from Table 212. 

33 Element <itl:FingerMissingCode> is the amputated or bandaged code (AMPCD). The following is 

34 a list of allowable indicators for the AMPCD: 

Descriptor AMPCD 

36 Amputation XX 

37 Unable to print (e.g., bandaged) UP 

38 

119 
 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 This field is to be used anytime there are fewer than expected printable fingers in a submission 

2 (e.g., less than four in a left or right slap or less than two in a two-thumb slap). A partially scarred 

3 finger should be printed. 

4 <itl:FingerprintImageFingerMissing>

<ansi-nist:FingerPositionCode>10 

6 </ansi-nist:FingerPositionCode>

7 <itl: FingerMissingCode>XX 

8 </itl:FingerMissingCode>

9 </itl:FingerprintImageFingerMissing> 

219.1.5.15 Element <itl:FingerprintImageSegmentPositionSquare> 

11 Cross reference: Part-1 Section 19.1.21 Field 14.021: Finger segment position(s) (SEG) 

12 This optional complex element shall contain offsets to the locations of image segments containing 

13 the individual fingers within the flat images of the four simultaneous fingers from each hand or the 

14 two simultaneous thumbs. The offsets are relative to the origin positioned in the upper left corner 

of the image. The horizontal offsets (X) are the pixel counts to the right, and the vertical offsets 

16 (Y) are the pixel counts down. 

17 This element shall have five child elements: <ansi-nist:FingerPositionCode>, <ansi18 nist:SegmentBottomVerticalCoordinateValue>, <ansi19 nist:SegmentLeftHorizontalCoordinateValue>, <ansinist:SegmentRightHorizontalCoordinateValue>, and 

21 <ansi-nist:SegmentTopVerticalCoordinateValue>. A finger segment is defined first by the finger 

22 number in <ansi-nist:FingerPositionCode> from Table 212, the X coordinates (LEFT, RIGHT or 

23 <ansi-nist:SegmentLeftHorizontalCoordinateValue>, <ansi24 nist:SegmentRightHorizontalCoordinateValue>) and the Y coordinates (TOP, BOTTOM or <ansinist:SegmentTopVerticalCoordinateValue>, <ansi-nist:SegmentBottomVerticalCoordinateValue>) 

26 of its bounding box. 

27 If more than one algorithm is used to segment the image, successive sets of finger segmentation 

28 positions shall be formatted as above and immediately follow the previous set. 

29 <itl:FingerprintImageSegmentPositionSquare>

< ansi-nist:FingerPositionCode>7</ansi31 nist:FingerPositionCode>

32 <ansi33 nist:SegmentBottomVerticalCoordinateValue>85 

34 </ansinist:SegmentBottomVerticalCoordinateValue>

36 <ansi37 nist:SegmentLeftHorizontalCoordinateValue>160 

38 </ansi39 nist:SegmentLeftHorizontalCoordinateValue>

<ansi41 nist:SegmentRightHorizontalCoordinateValue>200 

42 </ansi43 nist:SegmentRightHorizontalCoordinateValue> 

120 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:SegmentTopVerticalCoordinateValue>15 

2 </ansi3 nist:SegmentTopVerticalCoordinateValue>

4 </itl:FingerprintImageSegmentPositionSquare> 

219.1.5.16 Element <ansi-nist:FingerprintImageNISTQuality> 

6 Cross reference: Part-1 Section 19.1.22 Field 14.022: NIST quality metric (NQM) 

7 This optional complex element shall contain the NIST Fingerprint Image Quality (NFIQ) scores for 

8 the individual finger(s) derived from the slap impressions or individual rolled fingerprints. This 

9 element shall have two child elements: < ansi-nist:FingerPositionCode> and <ansinist:NISTQualityMeasure>. The former element is the finger number between one and ten as 

11 chosen from Table 212. The latter is the quality score which is a quantitative expression of the 

12 predicted AFIS matcher accuracy performance of the fingerprint image. The scores range from 

13 "1" for the best quality image, to "5" for the worst quality image. A "254" indicates that no score 

14 was ever computed while an entry of "255" shall indicate a failed attempt to calculate the image 

quality metric. 

16 This complex element may be repeated for different fingers. 

17 <ansi-nist:FingerprintImageNISTQuality>

18 <ansi-nist:FingerPositionCode>8 

19 </ansi-nist:FingerPositionCode>

<ansi-nist:NISTQualityMeasure>1 

21 </ansi-nist:NISTQualityMeasure>

22 </ansi-nist:FingerprintImageNISTQuality> 

23 219.1.5.17 Element <ansi-nist:FingerprintImageSegmentationQuality> 

24 Cross reference: Part-1 Section 19.1.23 Field 14.023: Segmentation quality metric (SQM) 

This optional complex element provides a measure of estimated correctness regarding the 

26 accuracy of the location of the segmented finger within the right or left four finger or two thumbs 

27 slap image. For each segmented finger, there shall be four child elements: <ansi28 nist:FingerPositionCode>, <ansi-nist:QualityAlgorithmProductIdentification>, <ansi29 nist:QualityAlgorithmVendorIdentification>, and <ansi-nist:QualityValue>. 

The element <ansi-nist:FingerPositionCode> is a finger position code and shall contain a code 

31 chosen from Table 212. (This corresponds to the first information item in 14.024.) 

32 The other three items identify a quality score and the algorithm used to create the quality score. 

33 This information is useful to enable the recipient of the quality score to differentiate between 

34 quality scores generated by different algorithms and adjust for any differences in processing or 

analysis as necessary. 

36 • The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

37 <nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

38 quality algorithm, which may be registered with the IBIA, but registration is not required. It 

39 indicates which of the vendor’s algorithms was used in the calculation of the quality 

score. This element contains the ASCII representation of the integer product code and 

41 should be within the range 1 to 65535. Element <ansi42 nist:QualityAlgorithmProductIdentification> shall have a child element 

121 
 

 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <nc:IdentificationID>, which will contain the numeric product code datum. (This 

2 corresponds to the fourth information item in 14.024.) 

3 • The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

4 <nc:IdentificationID> shall specify the ID of the vendor of the quality algorithm used to 

calculate the quality score. This 4-digit hex value is assigned by IBIA and expressed as 

6 four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF Biometric 

7 Organizations that will map the value in this element to a registered organization. 

8 Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

9 <nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

third information item in 14.024.) 

11 • The information item <ansi-nist:QualityValue> shall be a quantitative expression of the 

12 predicted matching performance of the biometric sample. This item contains the ASCII 

13 representation of the integer image quality score between 0 and 100 assigned to the 

14 image data by a quality algorithm. Higher values indicate better quality. An entry of 

“255” shall indicate a failed attempt to calculate a quality score. An entry of “254” shall 

16 indicate that no attempt to calculate a quality score was made. The use of additional 

17 values to convey other information should be harmonized with ISO/IEC 19794 standards. 

18 (This corresponds to the second information item in 14.024.) 

19 The complex element <ansi-nist:FingerprintImageSegmentationQuality> may be repeated for 

each quality algorithm used. 

21 <ansi-nist:FingerprintImageSegmentationQuality>

22 <ansi-nist:FingerPositionCode>7 

23 </ansi-nist:FingerPositionCode>

24 <ansinist:QualityAlgorithmProductIdentification>

26 

27 <nc:IdentificationID>28495</nc:IdentificationID>

28 </ansi29 nist:QualityAlgorithmProductIdentification>

<ansi31 nist:QualityAlgorithmVendorIdentification>

32 

33 <nc:IdentificationID>FFF0</nc:IdentificationID>

34 </ansinist:QualityAlgorithmVendorIdentification>

36 <ansi-nist:QualityValue>100</ansi37 nist:QualityValue>

38 </ansi-nist:FingerprintImageSegmentationQuality> 

39 219.1.5.18 Element <itl:FingerprintImageQuality> 

Cross reference: Part-1 Section 19.1.24 Field 14.024: Fingerprint quality metric (FQM) 

41 This optional complex element <itl:FingerprintImageQuality> is used to specify one or more 

42 different metrics of fingerprint image quality score data for the image stored in this record. The 

43 meaning attributed to this metric must be defined and interpreted by the producer of the scoring 

44 algorithm or by the person or system used to assign the metric to the fingerprint image. The 

122 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

45 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 metric may be a predictor of AFIS matcher accuracy performance or a different metric to indicate 

2 a value associated with the quality of the fingerprint image for a particular function. 

3 This element shall have four child elements: <ansi-nist:FingerPositionCode>, <ansi4 nist:QualityAlgorithmProductIdentification>, <ansi-nist:QualityAlgorithmVendorIdentification>, 

and <ansi-nist:QualityValue>. 

6 The element <ansi-nist:FingerPositionCode> is a finger position code and shall contain a code 

7 chosen from Table 212. (This corresponds to the first information item in 14.024.) 

8 The other three items identify a quality score and the algorithm used to create the quality score. 

9 This information is useful to enable the recipient of the quality score to differentiate between 

quality scores generated by different algorithms and adjust for any differences in processing or 

11 analysis as necessary. 

12 • The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

13 <nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

14 quality algorithm, which may be registered with the IBIA, but registration is not required. It 

indicates which of the vendor’s algorithms was used in the calculation of the quality 

16 score. This element contains the ASCII representation of the integer product code and 

17 should be within the range 1 to 65535. Element <ansi18 nist:QualityAlgorithmProductIdentification> shall have a child element 

19 <nc:IdentificationID>, which will contain the numeric product code datum. (This 

corresponds to the fourth information item in 14.024.) 

21 • The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

22 <nc:IdentificationID> shall specify the ID of the vendor of the quality algorithm used to 

23 calculate the quality score. This 4-digit hex value is assigned by IBIA and expressed as 

24 four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF Biometric 

Organizations that will map the value in this element to a registered organization. 

26 Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

27 <nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

28 third information item in 14.024.) 

29 • The information item <ansi-nist:QualityValue> shall be a quantitative expression of the 

predicted matching performance of the biometric sample. This item contains the ASCII 

31 representation of the integer image quality score between 0 and 100 assigned to the 

32 image data by a quality algorithm. Higher values indicate better quality. An entry of 

33 “255” shall indicate a failed attempt to calculate a quality score. An entry of “254” shall 

34 indicate that no attempt to calculate a quality score was made. The use of additional 

values to convey other information should be harmonized with ISO/IEC 19794 standards. 

36 (This corresponds to the second information item in 14.024.) 

37 The complex element <itl:FingerprintImageQuality> may be repeated for each quality algorithm 

38 used. 

39 <itl:FingerprintImageQuality>

<ansi-nist:FingerPositionCode>7 

41 </ansi-nist:FingerPositionCode>

42 <ansi43 nist:QualityAlgorithmProductIdentification>

44 

<nc:IdentificationID>28495</nc:IdentificationID> 

123 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 </ansi2 nist:QualityAlgorithmProductIdentification>

3 <ansi4 nist:QualityAlgorithmVendorIdentification> 

6 <nc:IdentificationID>FFF0</nc:IdentificationID>

7 </ansi8 nist:QualityAlgorithmVendorIdentification>

9 <ansi-nist:QualityValue>100</ansinist:QualityValue>

11 </itl:FingerprintImageQuality> 

12 219.1.5.19 Element <itl:FingerprintImageSegmentPositionPolygon> 

13 Cross reference: Part-1 Section 19.1.25 Field 14.025: Alternate Finger segment position(s) 

14 (ASEG) 

This optional complex element is an alternate approach to describing the locations for each of the 

16 image segments of the individual fingers within a flat image containing the capture of four 

17 simultaneous fingers or two simultaneous thumbs. This element uses an n-vertex polygon to 

18 encompass each finger image segment, where “n” is between 3 and 99. The order of the vertices 

19 must be in their consecutive order around the perimeter of the polygon, either clockwise or 

counterclockwise. No two vertices may occupy the same location. The polygon side defined by 

21 the last vertex and the first vertex shall complete the polygon. The polygon must be a simple, 

22 plane figure with no sides crossing and no interior holes. 

23 This element can be used one to four times and shall consist of three child elements: <ansi24 nist:FingerPositionCode>, <itl:PositionPolygonVertexQuantity>, and <itl:PositionPolygonVertex>. 

Element <ansi-nist:FingerPositionCode> shall consist of a finger number between 1 and 10 from 

26 Table 212. Element <itl:PositionPolygonVertexQuantity> shall consist of the total number of 

27 vertices of the polygon encompassing the finger. 

28 Complex element <itl:PositionPolygonVertex> shall consist of the two child elements <ansi29 nist:PositionHorizontalCoordinateValue> and <ansi-nist:PositionVerticalCoordinateValue>, and 

<itl:PositionPolygonVertex> shall be repeated for each vertex. Each vertex shall be represented 

31 as horizontal and vertical pixel offsets relative to the origin positioned in the upper left corner of 

32 the image. The horizontal offsets (X) are the pixel counts to the right, and the vertical offsets (Y) 

33 are the pixel counts down from the origin. A minimum of three points is required to describe a 

34 finger location. 

<itl:FingerprintImageSegmentPositionPolygon>

36 <ansi-nist:FingerPositionCode>7<ansi37 nist:FingerPositionCode>

38 <itl:PositionPolygonVertexQuantity>3 

39 </itl:PositionPolygonVertexQuantity>

<itl:PositionPolygonVertex>

41 <ansi42 nist:PositionHorizontalCoordinateValue>160 

43 </ansi44 nist:PositionHorizontalCoordinateValue> 

124 
 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi2 nist:PositionVerticalCoordinateValue>15 

3 </ansi4 nist:PositionVerticalCoordinateValue> 

</itl:PositionPolygonVertex>

6 <itl:PositionPolygonVertex>

7 <ansi8 nist:PositionHorizontalCoordinateValue>200 

9 </ansinist:PositionHorizontalCoordinateValue> 

11 <ansi12 nist:PositionVerticalCoordinateValue>15 

13 </ansi14 nist:PositionVerticalCoordinateValue> 

</itl:PositionPolygonVertex>

16 <itl:PositionPolygonVertex>

17 <ansi18 nist:PositionHorizontalCoordinateValue>180 

19 </ansinist:PositionHorizontalCoordinateValue> 

21 <ansi22 nist:PositionVerticalCoordinateValue>85 

23 </ansi24 nist:PositionVerticalCoordinateValue> 

</itl:PositionPolygonVertex>

26 </itl:FingerprintImageSegmentPositionPolygon > 

27 219.2 Additional variable-resolution fingerprint image records 

28 Additional Type-14 records may be included in the file. For each additional fingerprint image, a 

29 complete Type-14 logical record is required. 

220 Type-15 variable-resolution palmprint image record 

31 The Type-15 logical record shall contain and be used to exchange palmprint image data together 

32 with fixed and user-defined textual information pertinent to the digitized image. Information 

33 regarding the scanning resolution used, the image size, and other parameters or comments 

34 required to process the image are recorded as XML elements within the record. Palmprint 

images transmitted to other agencies will be processed by the recipient agencies to extract the 

36 desired feature information required for matching purposes. 

37 The image data shall be acquired directly from a subject using a live-scan device, a palmprint 

38 card, a major case print card, or other media that contains the subject’s palmprints. 

39 Any method used to acquire the palmprint images shall be capable of capturing a set of images 

for each hand. This set shall include the writer’s palm as a single scanned image, and the entire 

41 area of the full palm extending from the wrist bracelet to the tips of the fingers as one or two 

42 scanned images. If two images are used to represent the full palm, the lower image shall extend 

125 
 

1 from the wrist bracelet to the top of the interdigital area (third finger joint) and shall include the 

2 thenar, and hypothenar areas of the palm. The upper image shall extend from the bottom of the 

3 interdigital area to the upper tips of the fingers. This provides an adequate amount of overlap 

4 between the two images. The standard also has provision for encoding the interdigital, thenar, 

5 and hypothenar areas separately for each palm. By matching the ridge structure and details 

6 contained in this common area, an examiner can confidently state that both images came from 

7 the same palm. 

8 As a palmprint transaction may be used for different purposes, it may contain one or more unique 

9 image areas recorded from the palm or hand. A complete palmprint record set for one individual 

10 will normally include the writer’s palm and the full palm image(s) from each hand. Since a logical 

11 image record may contain only one binary, a single Type-15 record will be required for each 

12 writer’s palm and one to three Type-15 records for each full palm. Therefore, four to eight Type13 15 records will be required to represent the subject’s palmprints in a normal palmprint transaction. 

14 Table 235 contains palm positions, dimentions, and codes used in this section and throughout the 

15 standard. (Table 235 is the same as Table 35 in Part 1.) 

16 220.1 XML elements for the Type-15 logical record 

17 The following paragraphs describe the data contained in each of the elements for the Type-15 

18 logical record. 

19 Table 235 Palm codes and dimensions 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Palm 

Position 

Palm 

code 

Width 

(mm) (in) 

Height 

(mm) (in) 

Unknown Palm 20 139.7 5.5 203.2 8.0 

Right Full Palm 21 139.7 5.5 203.2 8.0 

Right Writer’s Palm 22 44.5 1.8 127.0 5.0 

Left Full Palm 23 139.7 5.5 203.2 8.0 

Left Writer’s Palm 24 44.5 1.8 127.0 5.0 

Right Lower Palm 25 139.7 5.5 139.7 5.5 

Right Upper Palm 26 139.7 5.5 139.7 5.5 

Left Lower Palm 27 139.7 5.5 139.7 5.5 

Left Upper Palm 28 139.7 5.5 139.7 5.5 

Right Other 29 139.7 5.5 203.2 8.0 

Left Other 30 139.7 5.5 203.2 8.0 

Right Interdigital 31 139.7 5.5 76.2 3.0 

Right Thenar 32 76.2 3.0 114.3 4.5 

Right Hypothenar 33 76.2 3.0 114.3 4.5 

Left Interdigital 34 139.7 5.5 76.2 3.0 

Left Thenar 35 76.2 3.0 114.3 4.5 

Left Hypothenar 36 76.2 3.0 114.3 4.5 

20 

21 Within a Type-15 logical record, entries shall be provided in XML elements. For each element of 

22 the Type-15 record, Table 236 lists the “condition code” as being mandatory “M” or optional “O”, 

23 the XML tag name, and occurrence limits. 

24 The Type-15 record shall be contained within this complex element: 

126 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <itl:PackageImageRecord> 

2 [. . . Type 15 Record Content . . .] 

3 </itl:PackageImageRecord> 

4 In the subsections that follow, text in bold between opening and closing tags is informative and 

only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi6 nist:RecordCategoryCode> for example). 

7 220.1.1 Record length 

8 Cross reference: Part-1 Section 20.1.1 Field 15.001: Logical record length (LEN) 

9 There is no corresponding Part 2 XML element. 

220.1.2 Element <ansi-nist:RecordCategoryCode> 

11 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

12 record type. For the Type-15 record, it shall contain a value of 15. 

13 <ansi-nist:RecordCategoryCode>15</ansi14 nist:RecordCategoryCode> 

220.1.3 Element <ansi-nist:ImageReferenceIdentification> 

16 Cross reference: Part-1 Section 20.1.2 Field 15.002: Image designation character (IDC) 

17 This mandatory complex element shall be used to identify the palmprint image data contained in 

18 the record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

19 found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

21 <nc:IdentificationID>, which shall contain the image reference identification datum. 

22 <ansi-nist:ImageReferenceIdentification>

23 <nc:IdentificationID>13</nc:IdentificationID>

24 </ansi-nist:ImageReferenceIdentification> 

26 

27 

28 

29 

31 

127 
 

 

 

 

 

 

 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 236 Type-15 Variable-resolution palmprint record 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

min Max 

LEN 15.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 15.002 <ansi-nist:ImageReferenceIdentification> 1 1 

UDF O 15.200 – 

15.998 

<itl:UserDefinedFields> -- --

M <itl:PalmprintImage> 1 1 

DATA M 15.999 <nc:BinaryBase64Object> 1 1 

BPX M 15.012 <ansi-nist:ImageBitsPerPixelQuantity> 1 1 

M <ansi-nist:ImageCaptureDetail> 1 1 

PCD M 15.005 <ansi-nist:CaptureDate> 1 1 

SHPS O 15.016 <ansi-nist:CaptureHorizontalPixelDensityValue> 0 1 

SRC M 15.004 <ansi-nist:CaptureOrganization> 1 1 

SVPS O 15.017 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1 

DMM O 15.030 <ansi-nist:CaptureDeviceMonitoringModeCode> 0 1 

COM O 15.020 <ansi-nist:ImageCommentText> 0 1 

CGA M 15.011 <ansi-nist:ImageCompressionAlgorithmText> 1 1 

HLL M 15.006 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

HPS M 15.009 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1 

SLC M 15.008 <ansi-nist:ImageScaleUnitsCode> 1 1 

VLL M 15.007 <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1 

VPS M 15.010 <ansi-nist:ImageVerticalPixelDensityValue> 1 1 

IMP M 15.003 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 1 1 

PLP M 15.013 <ansi-nist:PalmPositionCode> 1 1 

PQM O 15.024 <itl:PalmprintImageQuality> 0 4 

2 

3 220.1.4 Element <itl:UserDefinedFields> 

4 Cross reference: Part-1 Section 20.1.24 Fields 15.200-998: User-defined fields (UDF) 

5 These elements are user-definable. Their size and content shall be defined by the user and be in 

6 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

7 content values. 

128 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

2 Implementers should define, in an extension schema, a substitution element containing user3 defined child elements from the user’s domain. 

4 A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

6 substitutionGroup="itl:UserDefinedFields"

7 type="user-domain:UserDefinedFieldsType"/>

8 

9 <xsd:complexType name="UserDefinedFieldsType">

<xsd:complexContent>

11 <xsd:extension base="s:ComplexObjectType">

12 <xsd:sequence>

13 <xsd:element ref="user-domain:OneField"/>

14 <xsd:element ref="user-domain:TwoField”"/>

</xsd:sequence>

16 </xsd:extension>

17 </xsd:complexContent>

18 </xsd:complexType> 

19 The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

21 <user-domain:OneField>Text</user-domain:OneField>

22 <user-domain:TwoField>Text</user-domain:TwoField>

23 </user-domain:UserDefinedFields> 

24 220.1.5 Element <itl:PalmprintImage> 

This mandatory complex element contains the remaining elements in the Type-15 record, as 

26 described in the subsections below. 

27 <itl:PalmprintImage> 

28 [. . . Image elements . . .] 

29 </itl:PalmprintImage> 

220.1.5.1 Element <nc:BinaryBase64Object> 

31 Cross reference: Part-1 Section 20.1.25 Field 15.999 Image data (DATA) 

32 This mandatory element shall contain all of the data from a captured palmprint image. The binary 

33 image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

34 Each pixel of uncompressed grayscale data shall normally be quantized to eight bits (256 gray 

levels) contained in a single byte. If the entry in <ansi-nist:ImageBitsPerPixelQuantity> is greater 

36 than “8”, the number of bytes required to represent a pixel will be different. If compression is 

37 used, the pixel data shall be compressed in accordance with the compression technique specified 

38 in <ansi-nist:ImageCompressionAlgorithmText>. 

129 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <nc:BinaryBase64Object>base64 

2 data</nc:BinaryBase64Object> 

3 220.1.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

4 Cross reference: Part-1 Section 20.1.12 Field 15.012 Bits per pixel (BPX) 

This mandatory element shall contain the number of bits used to represent a pixel. This element 

6 shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

7 greater than “8” shall represent a grayscale pixel with increased precision. 

8 <ansi-nist:ImageBitsPerPixelQuantity>8 

9 </ansi-nist:ImageBitsPerPixelQuantity> 

220.1.5.3 Element <ansi-nist:ImageCaptureDetail> 

11 This mandatory complex element contains five child elements described in the subsections 

12 below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansi13 nist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansi14 nist:CaptureDeviceMonitoringModeCode>. 

<ansi-nist:ImageCaptureDetail> 

16 [. . . Image capture elements . . .] 

17 </ansi-nist:ImageCaptureDetail> 

18 220.1.5.3.1 Element <ansi-nist:CaptureDate> 

19 Cross reference: Part-1 Section 20.1.5 Field 15.005: Palmprint capture date (PCD) 

This mandatory element <ansi-nist:CaptureDate> shall contain the date that the palmprint image 

21 contained in the record was captured. The date shall appear as eight digits, separated by dashes, 

22 in the format YYYY-MM-DD. The YYYY characters shall represent the year the image was 

23 captured; the MM characters shall be the tens and units values of the month; and the DD 

24 characters shall be the tens and units values of the day in the month. For example, 2008-02-29 

represents February 29, 2008. The complete date must be a legitimate date. 

26 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

27 contain capture date data. 

28 <ansi-nist:CaptureDate>

29 <nc:Date>2008-02-29</nc:Date>

</ansi-nist:CaptureDate> 

31 220.1.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

32 Cross reference: Part-1 Section 20.1.15 Field 15.016 Scanned horizontal pixel scale (SHPS) 

33 This optional element shall specify the horizontal pixel density used for the scanning of the 

34 original impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

36 

130 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:CaptureHorizontalPixelDensityValue>500 

2 </ansi-nist:CaptureHorizontalPixelDensityValue> 

3 220.1.5.3.3 Element <ansi-nist:CaptureOrganization> 

4 Cross reference: Part-1 Section 20.1.4 Field 15.004 Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

6 <nc:IdentificationID> the identification of the administration or organization that originally captured 

7 the palmprint image contained in the record, and may contain in <nc:OrganizationName> the text 

8 name of the organization. Normally, the ORI of the agency that captured the image will be 

9 contained in <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may 

contain up to 36 identifying characters each and the data content of this element shall be defined 

11 by the user and be in accordance with the receiving agency. 

12 Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

13 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

14 <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

16 contain the datum for the text name of the organization. 

17 <ansi-nist:CaptureOrganization>

18 <nc:OrganizationIdentification>

19 <nc:IdentificationID>WI013415Y</nc:Identific

ationID> 

21 </nc:OrganizationIdentification>

22 <nc:OrganizationName>Text</nc:OrganizationName>

23 </ansi-nist:CaptureOrganization> 

24 220.1.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

Cross reference: Part-1 Section 20.1.16 Field 15.017 Scanned vertical pixel scale (SVPS) 

26 This optional element shall specify the vertical pixel density used for the scanning of the original 

27 impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

28 indicates the vertical component of the pixel aspect ratio. 

29 <ansi-nist:CaptureVerticalPixelDensityValue>500 

</ansi31 nist:CaptureVerticalPixelDensityValue> 

32 220.1.5.3.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

33 Cross reference: Part-1 Section 20.1.22 Field 15.030 Device monitoring mode (DMM) 

34 This optional element provides information describing the level of human monitoring for the image 

capture device. This element will contain an entry from Table 219 to indicate the monitoring 

36 mode of the biometric sample capture device. 

37 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED 

38 </ansi-nist:CaptureDeviceMonitoringModeCode> 

131 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 220.1.5.4 Element <ansi-nist:ImageCommentText> 

2 Cross reference: Part-1 Section 20.1.18 Field 15.020 Comment (COM) 

3 This optional element may be used to insert comments or other ASCII text information with the 

4 palmprint image data. 

<ansi-nist:ImageCommentText>Text</ansi6 nist:ImageCommentText> 

7 220.1.5.5 Element <ansi-nist:ImageCompressionAlgorithmText> 

8 Cross reference: Part-1 Section 20.1.11 Field 15.011 Compression algorithm (CGA) 

9 This mandatory element shall specify the algorithm used to compress the transmitted grayscale 

images. A value of "NONE" in this element indicates that the data contained in this record is 

11 uncompressed. For those images that are to be compressed, this element shall contain the text 

12 value from Table 201 to indicate the compression method used for this record type. The 

13 preferred methods for the compression of palmprint images are WSQ for those images scanned 

14 or transmitted at 500 ppi or JPEG 2000 for those images scanned and transmitted at 1000 ppi. 

See Section 205.6.1 and the Profile for 1000 ppi Fingerprint Compression for additional 

16 information on the usage of JPEG 2000 for the compression of fingerprint images. The domain 

17 registrar maintains a registry of acceptable compression techniques and corresponding codes 

18 that may be used as they become available. 

19 <ansi-nist:ImageCompressionAlgorithmText>WSQ

</ansi-nist:ImageCompressionAlgorithmText> 

21 220.1.5.6 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

22 Cross reference: Part-1 Section 20.1.6 Field 15.006 Horizontal line length (HLL) 

23 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

24 the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

26 </ansi27 nist:ImageHorizontalLineLengthPixelQuantity> 

28 220.1.5.7 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

29 Cross reference: Part-1 Section 20.1.9 Field 15.009 Horizontal pixel scale (HPS) 

This mandatory element shall specify the integer pixel density used in the horizontal direction of 

31 the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

32 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

33 <ansi-nist:CaptureHorizontalPixelDensityValue>1200 

34 </ansi-nist:CaptureHorizontalPixelDensityValue> 

36 

37 

132 
 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 220.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

2 Cross reference: Part-1 Section 20.1.8 Field 15.008 Scale units (SLC) 

3 This mandatory element shall specify the units used to describe the image sampling frequency 

4 (pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

6 HPS/VPS gives the pixel aspect ratio. 

7 <ansi-nist:ImageScaleUnitsCode>1</ansi8 nist:ImageScaleUnitsCode> 

9 220.1.5.9 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross reference: Part-1 Section 20.1.7 Field 15.007 Vertical line length (VLL) 

11 This mandatory element shall contain the number of horizontal lines contained in the transmitted 

12 image. 

13 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

14 </ansi-nist:ImageVerticalLineLengthPixelQuantity> 

16 220.1.5.10 Element <ansi-nist:ImageVerticalPixelDensityValue> 

17 Cross reference: Part-1 Section 20.1.10 Field 15.010 Vertical pixel scale (VPS) 

18 This mandatory element shall specify the integer pixel density used in the vertical direction of the 

19 transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

21 <ansi-nist:ImageVerticalPixelDensityValue>1200 

22 </ansi-nist:ImageVerticalPixelDensityValue> 

23 220.1.5.11 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

24 Cross reference: Part-1 Section 20.1.3 Field 15.003: Impression type (IMP) 

This mandatory element shall indicate the manner by which the palmprint image information was 

26 obtained. The appropriate code choice selected from Table 211 for palm shall be entered in this 

27 element. 

28 <ansi29 nist:FingerprintImageImpressionCaptureCategoryCode>10 

</ansi31 nist:FingerprintImageImpressionCaptureCategoryCode> 

32 220.1.5.12 Element <ansi-nist:PalmPositionCode> 

33 Cross reference: Part-1 Section 20.1.13 Field 15.013 Palmprint position (PLP) 

34 This mandatory element shall contain the palmprint position that matches the palmprint image. 

The decimal code number corresponding to the known or most probable palmprint position shall 

36 be taken from Table 235 and entered as a two-character ASCII value. 

133 
 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:PalmPositionCode>28</ansi2 nist:PalmPositionCode> 

3 220.1.5.13 Element <itl:PalmprintImageQuality> 

4 Cross reference: Part-1 Section 20.1.20 Field 15.024 NIST quality metric (PQM) 

This optional complex element is used to specify one or more different metrics of palm image 

6 quality score data for the image stored in this record. The meaning attributed to this metric must 

7 be defined and interpreted by the producer of the scoring algorithm or by the person or system 

8 used to assign the metric to the palm print image. The metric may be a predictor of AFIS matcher 

9 accuracy performance or a different metric to indicate a value associated with the quality of the 

palm print image for a particular function. 

11 Element <itl:PalmprintImageQuality> shall have four child elements: <ansi12 nist:PalmPositionCode>, <ansi-nist:QualityAlgorithmProductIdentification>, <ansi13 nist:QualityAlgorithmVendorIdentification>, and <ansi-nist:QualityValue>. 

14 The first information item is a palm position code; the information item <ansinist:PalmPositionCode> shall contain a code chosen from Table 235. (This corresponds to the 

16 first information item in 15.024.) 

17 The other three items identify a quality score and the algorithm used to create the quality score. 

18 This information is useful to enable the recipient of the quality score to differentiate between 

19 quality scores generated by different algorithms and adjust for any differences in processing or 

analysis as necessary. 

21 • The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

22 <nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

23 quality algorithm, which may be registered with the IBIA, but registration is not required. It 

24 indicates which of the vendor’s algorithms was used in the calculation of the quality 

score. This element contains the ASCII representation of the integer product code and 

26 should be within the range 1 to 65535. Element <ansi27 nist:QualityAlgorithmProductIdentification> shall have a child element 

28 <nc:IdentificationID>, which will contain the numeric product code datum. (This 

29 corresponds to the fourth information item in 15.024.) 

• The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

31 <nc:IdentificationID> shall specify the ID of the vendor of the quality algorithm used to 

32 calculate the quality score. This 4-digit hex value is assigned by IBIA and expressed as 

33 four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF Biometric 

34 Organizations that will map the value in this element to a registered organization. 

Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

36 <nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

37 third information item in 15.024.) 

38 • The information item <ansi-nist:QualityValue> shall be a quantitative expression of the 

39 predicted matching performance of the biometric sample. This item contains the ASCII 

representation of the integer image quality score between 0 and 100 assigned to the 

41 image data by a quality algorithm. Higher values indicate better quality. An entry of 

42 “255” shall indicate a failed attempt to calculate a quality score. An entry of “254” shall 

43 indicate that no attempt to calculate a quality score was made. The use of additional 

134 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 values to convey other information should be harmonized with ISO/IEC 19794 standards. 

2 (This corresponds to the second information item in 15.024.) 

3 The complex element <itl:PalmprintImageQuality> may be repeated for each quality algorithm 

4 used. 

5 <itl:PalmprintImageQuality>

6 <ansi-nist:PalmPositionCode>28 

7 </ansi-nist:PalmPositionCode>

8 <ansi9 nist:QualityAlgorithmProductIdentification>

10 

11 <nc:IdentificationID>28495</nc:IdentificationID>

12 </ansi13 nist:QualityAlgorithmProductIdentification>

14 <ansi15 nist:QualityAlgorithmVendorIdentification>

16 

17 <nc:IdentificationID>FFF0</nc:IdentificationID>

18 </ansi19 nist:QualityAlgorithmVendorIdentification>

20 <ansi-nist:QualityValue>100</ansi21 nist:QualityValue> 

22 </itl:PalmprintImageQuality> 

23 220.2 Additional variable-resolution palmprint image records 

24 Additional Type-15 records may be included in the file. For each additional palmprint image, a 

25 complete Type-15 logical record is required. 

26 

27 221 Type-16 user-defined testing image record 

28 The Type-16 logical record shall contain and be used to exchange image data together with 

29 textual information fields pertinent to the digitized image. This logical record type allows the 

30 standard to provide the ability to exchange images not addressed by other record types in the 

31 standard. It is intended as the XML user-defined logical record to be used for developmental or 

32 test purposes. 

33 The image data contained in the Type-16 logical record may be in a compressed form. With the 

34 exception of the XML elements described below, the format, parameters, and types of images to 

35 be exchanged are undefined by this Standard and shall be agreed upon between the sender and 

36 recipient. 

37 221.1 XML elements for the Type-16 logical record 

38 The following paragraphs describe the data contained in each of the elements for the Type-16 

39 logical record. 

135 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Within a Type-16 logical record, entries shall be provided in XML elements. For each element of 

2 the Type-16 record, Table 237 lists the “condition code” as being mandatory “M” or optional “O”, 

3 the XML tag name, and occurrence limits. 

4 The Type-16 record shall be contained within this complex element: 

<itl:PackageImageRecord> 

6 [. . . Type 16 Record Content . . .] 

7 </itl:PackageImageRecord> 

8 In the subsections that follow, text in bold between opening and closing tags is informative and 

9 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansinist:RecordCategoryCode> for example). 

11 221.1.1 Record length 

12 Cross reference: Part-1 Section 21.1.1 Field 16.001: Logical record length (LEN) 

13 There is no corresponding Part 2 XML element. 

14 221.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

16 record type. For the Type-16 record, it shall contain a value of 16. 

17 <ansi-nist:RecordCategoryCode>16 

18 </ansi-nist:RecordCategoryCode> 

19 221.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross reference: Part-1 Section 21.1.2 Field 16.002: Image designation character (IDC) 

21 This mandatory complex element shall be used to identify the latent image data contained in the 

22 record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

23 found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

24 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

26 <ansi-nist:ImageReferenceIdentification>

27 <nc:IdentificationID>14</nc:IdentificationID>

28 </ansi-nist:ImageReferenceIdentification>

29 

31 

32 

33 

34 

136 
 

 

 

 

 

 

 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 237 Type-16 Variable-resolution latent record 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

min Max 

LEN 16.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 16.002 <ansi-nist:ImageReferenceIdentification> 1 1 

UDF O 16.200 – 

16.998 

<itl:UserDefinedFields> -- --

M <itl:TestImage> 1 1 

DATA M 16.999 <nc:BinaryBase64Object> 1 1 

UDI M 16.003 <nc:BinaryDescriptionText> 1 1 

BPX M 16.012 <ansi-nist:ImageBitsPerPixelQuantity> 1 1 

M <ansi-nist:ImageCaptureDetail> 1 1 

UTD M 16.005 <ansi-nist:CaptureDate> 1 1 

SHPS O 16.016 <ansi-nist:CaptureHorizontalPixelDensityValue> 0 1 

SRC M 16.004 <ansi-nist:CaptureOrganization> 1 1 

SVPS O 16.017 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1 

DMM O 16.030 <ansi-nist:CaptureDeviceMonitoringModeCode> 0 1 

CSP O 16.013 <ansi-nist:ImageColorSpaceCode> 0 1 

COM O 16.020 <ansi-nist:ImageCommentText> 0 1 

CGA M 16.011 <ansi-nist:ImageCompressionAlgorithmText> 1 1 

HLL M 16.006 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

HPS M 16.009 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1 

UQS O 16.024 <ansi-nist:ImageQuality> 0 1 

SLC M 16.008 <ansi-nist:ImageScaleUnitsCode> 1 1 

VLL M 16.007 <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1 

VPS M 16.010 <ansi-nist:ImageVerticalPixelDensityValue> 1 1 

2 

3 221.1.4 Element <itl:UserDefinedFields> 

4 Cross reference: Part-1 Section 21.1.24 Fields 16.200-998: User-defined fields (UDF) 

5 These elements are user-definable. Their size and content shall be defined by the user and be in 

6 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

7 content values. 

137 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

2 Implementers should define, in an extension schema, a substitution element containing user3 defined child elements from the user’s domain. 

4 A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

6 substitutionGroup="itl:UserDefinedFields"

7 type="user-domain:UserDefinedFieldsType"/>

8 

9 <xsd:complexType name="UserDefinedFieldsType">

<xsd:complexContent>

11 <xsd:extension base="s:ComplexObjectType">

12 <xsd:sequence>

13 <xsd:element ref="user-domain:OneField"/>

14 <xsd:element ref="user-domain:TwoField”"/>

</xsd:sequence>

16 </xsd:extension>

17 </xsd:complexContent>

18 </xsd:complexType> 

19 The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

21 <user-domain:OneField>Text</user-domain:OneField>

22 <user-domain:TwoField>Text</user-domain:TwoField>

23 </user-domain:UserDefinedFields> 

24 221.1.5 Element <itl:TestImage> 

This mandatory complex element contains the remaining elements in the Type-16 record, as 

26 described in the subsections below. 

27 <itl:TestImage> 

28 [. . . Image elements . . .] 

29 </itl:TestImage> 

221.1.5.1 Element <nc:BinaryBase64Object> 

31 Cross reference: Part-1 Section 21.1.25 Field 16.999: Image data (DATA) 

32 This mandatory element shall contain all of the data from a captured latent image. The binary 

33 image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

34 Each pixel of uncompressed grayscale data shall normally be quantized to eight bits (256 gray 

levels) contained in a single byte. If the entry in <ansi-nist:ImageBitsPerPixelQuantity> is greater 

36 than “8”, the number of bytes required to represent a pixel will be different. If compression is 

37 used, the pixel data shall be compressed in accordance with the compression technique specified 

38 in <ansi-nist:ImageCompressionAlgorithmText>. 

138 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <nc:BinaryBase64Object>base64 data 

2 </nc:BinaryBase64Object> 

3 221.1.5.2 Element <nc:BinaryDescriptionText> 

4 Cross reference: Part-1 Section 21.1.3 Field 16.003: User-defined image (UDI) 

This mandatory element shall contain the type of user-defined image contained in this record. Its 

6 content shall be defined by the user and be in accordance with the receiving agency. 

7 <nc:BinaryDescriptionText>Test Image

8 </nc:BinaryDescriptionText> 

9 221.1.5.3 Element <ansi-nist:ImageBitsPerPixelQuantity> 

Cross reference: Part-1 Section 21.1.12 Field 16.012: Bits per pixel (BPX) 

11 This mandatory element shall contain the number of bits used to represent a pixel. This element 

12 shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

13 greater than “8” shall represent a grayscale pixel with increased precision. 

14 <ansi-nist:ImageBitsPerPixelQuantity>16 

</ansi-nist:ImageBitsPerPixelQuantity> 

16 221.1.5.4 Element <ansi-nist:ImageCaptureDetail> 

17 This mandatory complex element contains five child elements described in the subsections 

18 below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansi19 nist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode>. 

21 <ansi-nist:ImageCaptureDetail> 

22 [. . . Image capture elements . . .] 

23 </ansi-nist:ImageCaptureDetail> 

24 

26 221.1.5.4.1 Element <ansi-nist:CaptureDate> 

27 Cross reference: Part-1 Section 21.1.5 Field 16.005: Latent capture date (UTD) 

28 This mandatory element <ansi-nist:CaptureDate> shall contain the date that the image contained 

29 in the record was captured. The date shall appear as eight digits, separated by dashes, in the 

format YYYY-MM-DD. The YYYY characters shall represent the year the image was captured; 

31 the MM characters shall be the tens and units values of the month; and the DD characters shall 

32 be the tens and units values of the day in the month. For example, 2008-02-29 represents 

33 February 29, 2008. The complete date must be a legitimate date. 

34 

139 
 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

2 contain capture date data. 

3 <ansi-nist:CaptureDate>

4 <nc:Date>2008-02-29</nc:Date>

</ansi-nist:CaptureDate> 

6 221.1.5.4.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

7 Cross reference: Part-1 Section 21.1.15 Field 16.016: Scanned horizontal pixel scale (SHPS) 

8 This optional element shall specify the horizontal pixel density used for the scanning of the 

9 original impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

11 <ansi-nist:CaptureHorizontalPixelDensityValue>500 

12 </ansi-nist:CaptureHorizontalPixelDensityValue> 

13 221.1.5.4.3 Element <ansi-nist:CaptureOrganization> 

14 Cross reference: Part-1 Section 21.1.4 Field 16.004: Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

16 <nc:IdentificationID> the identification of the administration or organization that originally captured 

17 the latent image contained in the record, and may contain in <nc:OrganizationName> the text 

18 name of the organization. Normally, the ORI of the agency that captured the image will be 

19 contained in <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may 

contain up to 36 identifying characters each and the data content of this element shall be defined 

21 by the user and be in accordance with the receiving agency. 

22 Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

23 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

24 <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

26 contain the datum for the text name of the organization. 

27 <ansi-nist:CaptureOrganization>

28 <nc:OrganizationIdentification>

29 <nc:IdentificationID>WI013415Y</nc:Identific

ationID> 

31 </nc:OrganizationIdentification>

32 <nc:OrganizationName>Text</nc:OrganizationName>

33 </ansi-nist:CaptureOrganization> 

34 221.1.5.4.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

Cross reference: Part-1 Section 21.1.16 Field 16.017: Scanned vertical pixel scale (SVPS) 

36 This optional element shall specify the vertical pixel density used for the scanning of the original 

37 impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

38 indicates the vertical component of the pixel aspect ratio. 

39 

140 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:CaptureVerticalPixelDensityValue>500 

2 </ansi3 nist:CaptureVerticalPixelDensityValue> 

4 221.1.5.4.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross reference: Part-1 Section 21.1.22 Field 16.030 Device monitoring mode (DMM) 

6 This optional element provides information describing the level of human monitoring for the image 

7 capture device. This element will contain an entry from Table 219 to indicate the monitoring 

8 mode of the biometric sample capture device. 

9 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED 

</ansi-nist:CaptureDeviceMonitoringModeCode> 

11 221.1.5.5 Element <ansi-nist:ImageColorSpaceCode> 

12 Cross reference: Part-1 Section 21.1.13 Field 16.013: Color space (CSP) 

13 This mandatory element shall contain an ASCII entry from Table 203 to identify the color space 

14 used to exchange the image data. If the color space for an RGB image cannot be determined, an 

entry of "RGB" shall be entered in this element. The description for <ansi16 nist:ImageColorSpaceCode> in the Type-10 record contains additional information for the color 

17 space element. 

18 <ansi-nist:ImageColorSpaceCode>YCC 

19 </ansi-nist:ImageColorSpaceCode> 

221.1.5.6 Element <ansi-nist:ImageCommentText> 

21 Cross reference: Part-1 Section 21.1.18 Field 16.020: Comment (COM) 

22 This optional element may be used to insert comments or other ASCII text information with the 

23 latent image data. 

24 <ansi-nist:ImageCommentText>Text</ansinist:ImageCommentText> 

26 221.1.5.7 Element <ansi-nist:ImageCompressionAlgorithmText> 

27 Cross reference: Part-1 Section 21.1.11 Field 16.011: Compression algorithm (CGA) 

28 This mandatory element shall specify the algorithm used to compress the transmitted grayscale 

29 images. A value of "NONE" in this element indicates that the data contained in this record is 

uncompressed. For those images that are to be losslessly compressed, this element shall contain 

31 the text value from Table 201 to indicate the compression method used for the latent fingerprint 

32 images. See Section 205.6.1 for additional information on the usage of JPEG 2000 for the 

33 compression of fingerprint images. The domain registrar shall maintain a registry of acceptable 

34 compression techniques and corresponding codes that may be used as they become available. 

Falafel 

36 <ansi-nist:ImageCompressionAlgorithmText>JPEGB 

37 </ansi-nist:ImageCompressionAlgorithmText> 

141 
 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 221.1.5.8 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

2 Cross reference: Part-1 Section 21.1.6 Field 16.006: Horizontal line length (HLL) 

3 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

4 the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

6 </ansi7 nist:ImageHorizontalLineLengthPixelQuantity> 

8 221.1.5.9 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

9 Cross reference: Part-1 Section 21.1.9 Field 16.009: Horizontal pixel scale (HPS) 

This mandatory element shall specify the integer pixel density used in the horizontal direction of 

11 the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

12 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

13 <ansi-nist:CaptureHorizontalPixelDensityValue>1200 

14 </ansi-nist:CaptureHorizontalPixelDensityValue> 

221.1.5.10 Element <ansi-nist:ImageQuality> 

16 Cross reference: Part-1 Section 21.1.20 Field 16.024: User-defined testing quality score (UQS) 

17 This optional complex element shall specify a quality score for the user-defined testing image 

18 stored in this record. This element shall have three child elements: <ansi19 nist:QualityAlgorithmProductIdentification>, <ansi-nist:QualityValue>, and <ansinist:QualityMeasureVendorIdentification>. They identify a quality score and the algorithm used to 

21 create the quality score. This information is useful to enable the recipient of the quality score to 

22 differentiate between quality scores generated by different algorithms and adjust for any 

23 differences in processing or analysis as necessary. 

24 1. The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

<nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

26 quality algorithm, which may be registered with the IBIA, but registration is not required. It 

27 indicates which of the vendor’s algorithms was used in the calculation of the quality 

28 score. This element contains the ASCII representation of the integer product code and 

29 should be within the range 1 to 65535. Element <ansinist:QualityAlgorithmProductIdentification> shall have a child element 

31 <nc:IdentificationID>, which will contain the numeric product code datum. (This 

32 corresponds to the third information item in 16.024.) 

33 2. The information item <ansi-nist:QualityValue> shall be a quantitative expression of the 

34 predicted matching performance of the biometric sample. This item contains the ASCII 

representation of the integer image quality score between 0 and 100 assigned to the 

36 image data by a quality algorithm. Higher values indicate better quality. An entry of 

37 “255” shall indicate a failed attempt to calculate a quality score. An entry of “254” shall 

38 indicate that no attempt to calculate a quality score was made. The use of additional 

39 values to convey other information should be harmonized with ISO/IEC 19794 standards. 

(This corresponds to the first information item in 16.024.) 

142 
 

 

 

 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 3. The information item <ansi-nist:QualityMeasureVendorIdentification> and its child 

2 <nc:IdentificationID> shall specify the ID of the vendor of the quality algorithm used to 

3 calculate the quality score. This 4-digit hex value is assigned by IBIA and expressed as 

4 four ASCII characters. The IBIA shall maintain the Vendor Registry of CBEFF Biometric 

5 Organizations that will map the value in this element to a registered organization. 

6 Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

7 <nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

8 second information item in 16.024.) 

9 <ansi-nist:ImageQuality>

10 <ansi11 nist:QualityAlgorithmProductIdentification>

12 

13 <nc:IdentificationID>28495</nc:IdentificationID>

14 </ansi15 nist:QualityAlgorithmProductIdentification>

16 <ansi-nist:QualityValue>100</ansi17 nist:QualityValue>

18 <ansi-nist: 

19 QualityMeasureVendorIdentification>

20 

21 <nc:IdentificationID>FFF0</nc:IdentificationID>

22 </ansi-nist:

23 QualityMeasureVendorIdentification>

24 </ansi-nist: ImageQuality> 

25 221.1.5.11 Element <ansi-nist:ImageScaleUnitsCode> 

26 Cross reference: Part-1 Section 21.1.8 Field 16.008: Scale units (SLC) 

27 This mandatory element shall specify the units used to describe the image sampling frequency 

28 (pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per 

29 centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

30 HPS/VPS gives the pixel aspect ratio. 

31 <ansi-nist:ImageScaleUnitsCode>1</ansi32 nist:ImageScaleUnitsCode> 

33 221.1.5.12 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

34 Cross reference: Part-1 Section 21.1.7 Field 16.007: Vertical line length (VLL) 

35 This mandatory element shall contain the number of horizontal lines contained in the transmitted 

36 image. 

37 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

38 </ansi-nist:ImageVerticalLineLengthPixelQuantity>

39 

143 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 221.1.5.13 Element <ansi-nist:ImageVerticalPixelDensityValue> 

2 Cross reference: Part-1 Section 21.1.10 Field 16.010: Vertical pixel scale (VPS) 

3 This mandatory element shall specify the integer pixel density used in the vertical direction of the 

4 transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

5 Otherwise, it indicates the vertical component of the pixel aspect ratio. 

6 <ansi-nist:ImageVerticalPixelDensityValue>1200 

7 </ansi-nist:ImageVerticalPixelDensityValue> 

8 221.2 Additional variable-resolution latent image records 

9 Additional Type-16 records may be included in the file. For each additional latent image, a 

10 complete Type-16 logical record is required. 

11 222 Type-17 Iris image record 

12 222.1 General 

13 The Part-2 XML version of the Type-17 logical record shall contain and be used to exchange 

14 generic iris image data using mandatory elements of this record type. Optional elements may be 

15 used to exchange additional information available in the INCITS 379-2004 – Iris Image 

16 Interchange Format standard and the ISO/IEC 19794-6 iris image data interchange format 

17 standard. Images may be monochrome or color with 256 or more intensity levels (grey or per18 color component), and vary in size depending on field of view and compression. 

19 The iris standards specify two alternative image interchange formats for biometric authentication 

20 systems that utilize iris recognition. The first, which is represented in this record type, is based on 

21 a rectilinear image storage format that specifies a raw, uncompressed or compressed array of 

22 intensity values. The second is an image data format based on a polar image specification and is 

23 not represented in this logical record type. If such a polar representation is required for a specific 

24 application, a Type-99 CBEFF biometric data record may be used. 

25 222.2 XML elements for the Type-17 logical record 

26 The following paragraphs describe the data contained in each of the elements for the Type-17 

27 logical record. 

28 Within a Type-17 logical record, entries shall be provided in XML elements. For each element of 

29 the Type-17 record, Table 238 lists the “condition code” as being mandatory “M” or optional “O”, 

30 the XML tag name, and occurrence limits. It is required that all elements of the record are 

31 ordered as described in the subsections below. 

32 The Type-17 record shall be contained within this complex element: 

33 <itl:PackageImageRecord> 

34 [. . . Type 17 Record Content . . .] 

35 </itl:PackageImageRecord> 

144 
 

1 In the subsections that follow, text in bold between opening and closing tags is informative and 

2 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi3 nist:RecordCategoryCode> for example). 

4 

5 Table 238 Type-17 Iris image record layout 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

LEN 17.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 17.002 <ansi-nist:ImageReferenceIdentification> 1 1

UDF O 17.200 – <itl:UserDefinedFields> 0 Unlim

17.998 

 M <itl:IrisImage> 1 1 

DATA M 17.999 <nc:BinaryBase64Object> 1 1

BPX M 17.012 <ansi-nist:ImageBitsPerPixelQuantity> 1 1

 <ansi-nist:ImageCaptureDetail> 1 1

ICD M 17.005 <ansi-nist:CaptureDate> 1 1

SHPS O 17.022 <ansi-nist:CaptureHorizontalPixelDensityValue> 0 1

SRC M 17.004 <ansi-nist:CaptureOrganization> 1 1

SVPS O 17.023 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1

DMM O 17.030 <ansi-nist:CaptureDeviceMonitoringModeCode> 0 1

CSP M 17.013 <ansi-nist:ImageColorSpaceCode> 1 1

COM O 17.021 <ansi-nist:ImageCommentText> 0 Unlim

CGA M 17.011 <ansi-nist:ImageCompressionAlgorithmText> 1 1

HLL M 17.006 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1

HPS M 17.009 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1

IQS O 17.024 <ansi-nist:ImageQuality> 0 1

SLC M 17.008 <ansi-nist:ImageScaleUnitsCode> 1 1

VLL M 17.007 <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1

VPS M 17.010 <ansi-nist:ImageVerticalPixelDensityValue> 1 1

FID M 17.003 <ansi-nist:IrisEyePositionCode> 1 1

RAE O 17.014 <ansi-nist:IrisEyeRotationAngleMeasure> 0 1

RAU O 17.015 <ansi-nist:IrisEyeRotationUncertaintyValueText> 0 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

145 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

 <ansi-nist:IrisImageCapture> 

GUI O 17.018 <ansi-nist:CaptureDeviceGlobalIdentification> 0 1

DUI O 17.017 <ansi-nist:CaptureDeviceIdentification> 0 1

MMS O 17.019 <ansi-nist:CaptureDeviceMakeText> 0 1

O <ansi-nist:CaptureDeviceModelText> 0 1

O <ansi-nist:CaptureDeviceSerialNumberText> 0 1

IPC O 17.016 <ansi-nist:IrisImageHorizontalOrientationCode> 0 1 

O <ansi-nist:IrisImageScanCategoryCode> 0 1

O <ansi-nist:IrisImageVerticalOrientationCode> 0 1

ECL O 17.020 <ansi-nist:IrisEyeColorAttributeCode> 0 1

ALS O 17.025 <ansi-nist:IrisImageAcquisitionLightingSpectrumValue> 0 1 

IRD O 17.026 <itl:IrisDiameterPixelQuantity> 0 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 

2 222.2.1 Record length 

3 Cross reference: Part-1 Section 22.2.1 Field 17.001: Logical record length (LEN) 

4 There is no corresponding Part-2 XML element. 

5 222.2.2 Element <ansi-nist:RecordCategoryCode> 

6 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

7 record type. For the Type-17 record, it shall contain a value of 17. 

8 <ansi-nist:RecordCategoryCode>17</ansi9 nist:RecordCategoryCode> 

10 222.2.3 Element <ansi-nist:ImageReferenceIdentification> 

11 Cross reference: Part-1 Section 22.2.2 Field 17.002: Image designation character (IDC) 

12 This mandatory complex element shall be used to identify the iris image data contained in the 

13 record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

14 found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

15 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

16 <nc:IdentificationID>, which shall contain the image reference identification datum. 

17 

18 

146 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 <ansi-nist:ImageReferenceIdentification>

2 <nc:IdentificationID>13</nc:IdentificationID>

3 </ansi-nist:ImageReferenceIdentification> 

4 222.2.4 Element <itl:UserDefinedFields> 

Cross reference: Part-1 Section 22.2.30 Fields 17.200-998: User-defined fields (UDF) 

6 These elements are user-definable. Their size and content shall be defined by the user and be in 

7 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

8 content values. 

9 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing user11 defined child elements from the user’s domain. 

12 A substitution element should be defined in a user’s extension schema similar to this: 

13 <xsd:element name="UserDefinedFields" 

14 substitutionGroup="itl:UserDefinedFields"

type="user-domain:UserDefinedFieldsType"/>

16 

17 <xsd:complexType name="UserDefinedFieldsType">

18 <xsd:complexContent>

19 <xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

21 <xsd:element ref="user-domain:OneField"/>

22 <xsd:element ref="user-domain:TwoField”"/>

23 </xsd:sequence>

24 </xsd:extension>

</xsd:complexContent>

26 </xsd:complexType> 

27 The element would then appear in an instance document like this: 

28 <user-domain:UserDefinedFields> 

29 <user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

31 </user-domain:UserDefinedFields> 

32 222.2.5 Element <itl:IrisImage> 

33 This is a mandatory complex element. All of the remaining elements in the Type-17 record are 

34 nested within, as described in the subsections below. 

<itl:IrisImage> 

36 [. . . Image elements . . .] 

37 </itl:IrisImage> 

38 

147 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 222.2.5.1 Element <nc:BinaryBase64Object> 

2 Cross reference: Part-1 Section 22.2.31 Field 17.999: Image data (DATA) 

3 This mandatory element shall contain the iris image. The binary image data shall be converted to 

4 ASCII characters using the Base64 encoding algorithm. 

5 <nc:BinaryBase64Object>base64 

6 data</nc:BinaryBase64Object> 

7 222.2.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

8 Cross reference: Part-1 Section 22.2.12 Field 17.012: Bits per pixel (BPX) 

9 This mandatory element shall contain the number of bits used to represent a pixel. This element 

10 shall contain an entry of “8” for normal grayscale values of “0” to “255” or each RGB color 

11 component. Any entry in this element greater than “8” shall represent a grayscale pixel with 

12 increased precision. 

13 <ansi-nist:ImageBitsPerPixelQuantity>16 

14 </ansi-nist:ImageBitsPerPixelQuantity> 

15 222.2.5.3 Element <ansi-nist:ImageCaptureDetail> 

16 This mandatory complex element contains five child elements described in the subsections 

17 below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansi18 nist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansi19 nist:CaptureDeviceMonitoringModeCode. 

20 <ansi-nist:ImageCaptureDetail> 

21 [. . . Image capture elements . . .] 

22 </ansi-nist:ImageCaptureDetail> 

23 222.2.5.3.1 Element <ansi-nist:CaptureDate> 

24 Cross reference: Part-1 Section 22.2.5 Field 17.005: Iris capture date (ICD) 

25 This mandatory element <ansi-nist:CaptureDate> shall contain the date that the iris image 

26 contained in the record was captured. The date shall appear as eight digits, separated by dashes, 

27 in the format YYYY-MM-DD. The YYYY characters shall represent the year the image was 

28 captured; the MM characters shall be the tens and units values of the month; and the DD 

29 characters shall be the tens and units values of the day in the month. For example, 2008-02-29 

30 represents February 29, 2008. The complete date must be a legitimate date. 

31 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

32 contain capture date data. 

33 <ansi-nist:CaptureDate>

34 <nc:Date>2008-02-29</nc:Date>

35 </ansi-nist:CaptureDate>

36 

148 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 222.2.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

2 Cross reference: Part-1 Section 22.2.22 Field 17.022: Scanned horizontal pixel scale (SHPS) 

3 This optional element shall specify the horizontal pixel density used for the scanning of the 

4 original impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

5 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

6 <ansi-nist:CaptureHorizontalPixelDensityValue>500 

7 </ansi-nist:CaptureHorizontalPixelDensityValue> 

8 222.2.5.3.3 Element <ansi-nist:CaptureOrganization> 

9 Cross reference: Part-1 Section 22.2.4 Field 17.004: Source agency / ORI (SRC) 

10 This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

11 <nc:IdentificationID> the identification of the administration or organization that originally captured 

12 the iris image contained in the record, and may contain in <nc:OrganizationName> the text name 

13 of the organization. Normally, the ORI of the agency that captured the image will be contained in 

14 <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may contain up to 

15 36 identifying characters each and the data content of this element shall be defined by the user 

16 and be in accordance with the receiving agency. 

17 Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

18 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

19 <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

20 contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

21 contain the datum for the text name of the organization. 

22 <ansi-nist:CaptureOrganization>

23 <nc:OrganizationIdentification>

24 <nc:IdentificationID>WI013415Y</nc:Identific

25 ationID> 

26 </nc:OrganizationIdentification>

27 <nc:OrganizationName>Text</nc:OrganizationName>

28 </ansi-nist:CaptureOrganization> 

29 222.2.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

30 Cross reference: Part-1 Section 22.2.23 Field 17.023: Scanned vertical pixel scale (SVPS) 

31 This optional element shall specify the vertical pixel density used for the scanning of the original 

32 impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

33 indicates the vertical component of the pixel aspect ratio. 

34 <ansi-nist:CaptureVerticalPixelDensityValue>500 

35 </ansi36 nist:CaptureVerticalPixelDensityValue>

37 

38 

149 
 

1 222.2.5.3.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

2 Cross reference: Part-1 Section 22.2.28 Field 10.030: Device monitoring mode (DMM) 

3 This optional element provides information describing the level of human monitoring for the image 

4 capture device. This element will contain an entry from Table 219 to indicate the monitoring 

5 mode of the biometric sample capture device. 

6 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED 

7 </ansi-nist:CaptureDeviceMonitoringModeCode> 

8 222.2.5.4 Element <ansi-nist:ImageColorSpaceCode> 

9 Cross reference: Part-1 Section 22.2.13 Field 17.013: Color space (CSP) 

10 This mandatory element shall contain an ASCII entry from Table 203 to identify the color space 

11 used to exchange the image data. If the color space for an RGB image cannot be determined, an 

12 entry of "RGB" shall be entered in this element. The description for <ansi13 nist:ImageColorSpaceCode> in the Type-10 record contains additional information for the color 

14 space element. 

15 <ansi-nist:ImageColorSpaceCode>YCC 

16 </ansi-nist:ImageColorSpaceCode> 

17 222.2.5.5 Element <ansi-nist:ImageCommentText> 

18 Cross reference: Part-1 Section 22.2.21 Field 17.021: Comment (COM) 

19 This optional element may be used to insert comments or other ASCII text information with the 

20 iris image data. 

21 The simple element <ansi-nist:ImageCommentText> may have multiple occurrences if the 

22 sending and receiving agencies agree to have multiple, separate comments. 

23 <ansi-nist:ImageCommentText>Text</ansi24 nist:ImageCommentText>

25 <ansi-nist:ImageCommentText>Text</ansi26 nist:ImageCommentText> 

27 222.2.5.6 Element <ansi-nist:ImageCompressionAlgorithmText> 

28 Cross reference: Part-1 Section 22.2.11 Field 17.011: Compression algorithm (CGA) 

29 This mandatory element shall specify the algorithm used to compress the color or grayscale 

30 images. Table 201 contains the codes for the compression methods. An entry of "NONE" in this 

31 field indicates that the data contained in this record is uncompressed. The image shall be 

32 represented as an array of n rows by m columns by at least 8-bit pixels. Each pixel in a 

33 monochrome image shall be represented by eight or more bits. Color images shall be 

34 represented as a sequential sample of a red, green, and blue intensity for each pixel. The image 

35 shall be organized in row-major order, with the lowest address corresponding to the upper left 

36 corner of the image. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

150 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 For those images that are to be compressed, the method for the compression of iris images is 

2 specified by the baseline mode of the JPEG algorithm or JPEG 2000. For best results, the 

3 compression ratio should not exceed 6:1. 

4 <ansi-nist:ImageCompressionAlgorithmText>JPEGB 

</ansi-nist:ImageCompressionAlgorithmText> 

6 222.2.5.7 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

7 Cross reference: Part-1 Section 22.2.6 Field 17.006: Horizontal line length (HLL) 

8 This mandatory element shall contain the number of pixels contained on a single horizontal line of 

9 the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

11 </ansi12 nist:ImageHorizontalLineLengthPixelQuantity> 

13 222.2.5.8 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

14 Cross reference: Part-1 Section 22.2.9 Field 17.009: Horizontal pixel scale (HPS) 

This mandatory element shall specify the integer pixel density used in the horizontal direction of 

16 the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

17 Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

18 <ansi-nist:CaptureHorizontalPixelDensityValue>1200 

19 </ansi-nist:CaptureHorizontalPixelDensityValue> 

222.2.5.9 Element <ansi-nist:ImageQuality> 

21 Cross reference: Part-1 Section 22.2.24 Field 17.024: Image Quality Score (IQS) 

22 This optional element shall specify quality score data for the iris image stored in this record. 

23 There are three child elements. They identify a quality score and the algorithm used to create the 

24 quality score. This information is useful to enable the recipient of the quality score to differentiate 

between quality scores generated by different algorithms and adjust for any differences in 

26 processing or analysis as necessary. 

27 The parent element <ansi-nist:ImageQuality> may have multiple occurrences, one for each 

28 quality algorithm used. 

29 1. The child element <ansi-nist:QualityAlgorithmProductIdentification> shall specify a 

numeric product code assigned by the vendor of the quality algorithm, which may be registered 

31 with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms 

32 was used in the calculation of the quality score. This complex element contains a child element 

33 <nc:IdentificationID> which contains the ASCII representation of the integer product code and 

34 should be within the range 1 to 65,535. 

2. The child element <ansi-nist:QualityValue> shall be a quantitative expression of the 

36 predicted matching performance of the biometric sample. This element contains the ASCII 

37 representation of the integer image quality score between 0 and 100 assigned to the image data 

38 by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a 

39 failed attempt to calculate a quality score. An entry of “254” shall indicate that no attempt to 

151 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 calculate a quality score was made. The use of additional values to convey other information 

2 should be harmonized with ISO/IEC 19794 standards. 

3 3. The child element <ansi-nist:QualityMeasureVendorIdentification> shall specify the ID of 

4 the vendor of the quality algorithm used to calculate the quality score. This 4-digit hex value is 

assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor 

6 Registry of CBEFF Biometric Organizations that will map the value in this element to a registered 

7 organization. This complex element contains a child element <nc:IdentificationID> which shall 

8 contain the identification datum. 

9 <ansi-nist:ImageQuality>

<ansi-nist:QualityAlgorithmProductIdentification>

11 <nc:IdentificationID>28488</nc:Identificatio

12 nID> 

13 </ansi14 nist:QualityAlgorithmProductIdentification>

<ansi-nist:QualityValue>100 

16 </ansi-nist:QualityValue>

17 <ansi-nist:QualityMeasureVendorIdentification>

18 <nc:IdentificationID>FFF0</nc:Identification

19 ID> 

</ansi-nist:QualityMeasureVendorIdentification>

21 </ansi-nist:ImageQuality> 

22 222.2.5.10 Element <ansi-nist:ImageScaleUnitsCode> 

23 Cross reference: Part-1 Section 22.2.8 Field 17.008: Scale units (SLC) 

24 This mandatory element shall specify the units used to describe the image sampling frequency 

(pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per 

26 centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

27 HPS/VPS gives the pixel aspect ratio. 

28 <ansi-nist:ImageScaleUnitsCode>1</ansi29 nist:ImageScaleUnitsCode> 

222.2.5.11 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

31 Cross reference: Part-1 Section 22.2.7 Field 17.007: Vertical line length (VLL) 

32 This mandatory element shall contain the number of horizontal lines contained in the transmitted 

33 image. 

34 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

</ansi-nist:ImageVerticalLineLengthPixelQuantity>

36 

37 222.2.5.12 Element <ansi-nist:ImageVerticalPixelDensityValue> 

38 Cross reference: Part-1 Section 22.2.10 Field 17.010: Vertical pixel scale (VPS) 

152 
 

 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 This mandatory elemeent shall specify the integer pixel density used in the vertical direction of 

2 the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

3 Otherwise, it indicates the vertical component of the pixel aspect ratio. 

4 <ansi-nist:ImageVerticalPixelDensityValue>1200 

</ansi-nist:ImageVerticalPixelDensityValue> 

6 222.2.5.13 Element <ansi-nist:IrisEyePositionCode> 

7 Cross reference: Part-1 Section 22.2.3 Field 17.003: Feature identifier (FID) 

8 This mandatory element shall contain an identifier for the eye represented by the image in the 

9 record. An entry of “0” in this element indicates that the image in this record is undefined. An 

entry of “1” in this element indicates that the image in this record is the subject's right eye. An 

11 entry of “2” in this element indicates that the image in this record is the subject's left eye. 

12 <ansi-nist:IrisEyePositionCode>2 

13 </ansi-nist:IrisEyePositionCode> 

14 222.2.5.14 Element <ansi-nist:IrisEyeRotationAngleMeasure> 

Cross reference: Part-1 Section 22.2.14 Field 17.014: Rotation Angle of Eye (RAE) 

16 This optional element shall indicate the rotation angle of the eye. For rectilinear images, rotation 

17 angle = round (65536 * angle / 360) modulo 65536. The angle is measured in degrees from 

18 horizontal to the interpupillary line. The value “FFFF” indicates rotation angle of eye is undefined. 

19 <ansi-nist:IrisEyeRotationAngleMeasure>8192 

</ansi-nist:IrisEyeRotationAngleMeasure> 

21 222.2.5.15 Element <ansi-nist:IrisEyeRotationUncertaintyValueText> 

22 Cross reference: Part-1 Section 22.2.15 Field 17.015: Rotation Uncertainty (RAU) 

23 This optional field shall indicate the rotation uncertainty. The rotation uncertainty is equal to 

24 [round (65536 * uncertainty / 180)]. The uncertainty is measured in degrees and is the absolute 

value of maximum error. The value “FFFF” indicates uncertainty is undefined. 

26 <ansi-nist:IrisEyeRotationUncertainty>FFFF 

27 </ansi-nist:IrisEyeRotationUncertainty>

28 

29 222.2.5.16 Element <ansi-nist:IrisImageCapture> 

This mandatory complex element contains eight child elements described in the subsections 

31 below. The eight child elements shall be contained within this parent element: 

32 <ansi-nist:IrisImageCapture> 

33 [. . . Iris image capture elements . . .] 

34 </ansi-nist:IrisImageCapture> 

153 
 

1 222.2.5.16.1 Element <ansi-nist:CaptureDeviceGlobalIdentification> 

2 Cross reference: Part-1 Section 22.2.18 Field 17.018: Global Unique Identifier (GUI) 

3 This optional element shall contain a 16-byte string to indicate a GUID – a globally unique 

4 identifier. 

5 Complex element <ansi-nist:CaptureDeviceGlobalIdentification> shall have the simple element 

6 <nc:IdentificationID>, which will contain the identifier datum. 

7 <ansi-nist:CaptureDeviceGlobalIdentification> 

8 

9 <nc:IdentificationID>A2849B293059C200</nc:Identif

10 icationID> 

11 </ansi-nist:CaptureDeviceGlobalIdentification> 

12 222.2.5.16.2 Element <ansi-nist:CaptureDeviceIdentification> 

13 Cross reference: Part-1 Section 22.2.17 Field 17.017: Device Unique Identifier (DUI) 

14 This optional element shall contain a sixteen-byte string uniquely identifying the device or source 

15 of the data. This data can be one of: (1) Device Serial number, identified by the first character “D”, 

16 (2) Host PC Mac address, identified by the first character “M”, (3) Host PC processor ID, identified 

17 by the first character “P”, and (4) No serial number, identified by all zero’s. 

18 Complex element <ansi-nist:CaptureDeviceIdentification> shall have the simple element 

19 <nc:IdentificationID>, which will contain the identifier datum. 

20 <ansi-nist:CaptureDeviceIdentification> 

21 

22 <nc:IdentificationID>P270NEIS67830001</nc:Identif

23 icationID> 

24 </ansi-nist:CaptureDeviceIdentification> 

25 222.2.5.16.3 Element <ansi-nist:CaptureDeviceMakeText> 

26 Cross reference: Part-1 Section 22.2.19 Field 17.019: Make/Model/Serial Number (MMS), 

27 subfield make 

28 This optional element contains the make for the iris capture device. This information item shall be 

29 1 to 50 characters. This information item may indicate that information is unknown with the value 

30 “0”. 

31 <ansi-nist:CaptureDeviceMakeText>Text 

32 </ansi-nist:CaptureDeviceMakeText> 

33 222.2.5.16.4 Element <ansi-nist:CaptureDeviceModelText> 

34 Cross reference: Part-1 Section 22.2.19 Field 17.019: Make/Model/Serial Number (MMS), 

35 subfield model 

36 This optional element contains the model for the iris capture device. This information item shall 

37 be 1 to 50 characters. This information item may indicate that information is unknown with the 

38 value “0”. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

154 
 

1 <ansi-nist:CaptureDeviceModelText>Text 

2 </ansi-nist:CaptureDeviceModelText> 

3 222.2.5.16.5 Element <ansi-nist:CaptureDeviceSerialNumberText> 

4 Cross reference: Part-1 Section 22.2.19 Field 17.019: Make/Model/Serial Number (MMS), 

5 subfield serial number 

6 This optional element contains the serial number for the iris capture device. This information item 

7 shall be 1 to 50 characters. This information item may indicate that information is unknown with 

8 the value “0”. 

9 <ansi-nist:CaptureDeviceSerialNumberText>Text 

10 </ansi-nist:CaptureDeviceSerialNumberText> 

11 222.2.5.16.6 Element <ansi-nist:IrisImageHorizontalOrientationCode> 

12 Cross reference: Part-1 Section 22.2.16 Field 17.016: Image Property Code (IPC), subfield 

13 horizontal orientation 

14 This optional element shall contain the horizontal orientation of the image. 

15 Values for Horizontal Orientation shall be one of: “0” for Undefined, “1” for Base, or “2” for 

16 Flipped. “Base” orientation refers to images corresponding to the view facing the subject, where 

17 the nasal side of subject’s left eye or outer edge of the subject’s right eye is on the left side the of 

18 image. “Flipped” orientation refers to images where the orientation is opposite from that 

19 described for “Base”. 

20 <ansi-nist:IrisImageHorizontalOrientationCode>2 

21 </ansi-nist:IrisImageHorizontalOrientationCode> 

22 

23 222.2.5.16.7 Element <ansi-nist:IrisImageScanCategoryCode> 

24 Cross reference: Part-1 Section 22.2.16 Field 17.016: Image Property Code (IPC), subfield scan 

25 type 

26 This optional element shall contain the scan type of the image. 

27 Values for Scan Type shall be one of: “0” for Undefined, “1” for Progressive, “2” for Interlace 

28 Frame, or “3” for Interlace Field. “Progressive” indicates that the image was captured using 

29 progressive scanning, in which case all image lines are generated sequentially. “Interlace Frame” 

30 indicates that the image was captured using interlaced scanning, in which two fields are 

31 generated in sequence, the first composed of odd-numbered lines and the second of even32 numbered lines. “Interlace Field” indicates that the image was captured using interlaced 

33 scanning, in which only one field is generated, and then each line is duplicated to produce a full 

34 size image. 

35 <ansi-nist:IrisImageScanCategoryCode>3 

36 </ansi-nist:IrisImageScanCategoryCode> 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

155 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 222.2.5.16.8 Element <ansi-nist:IrisImageVerticalOrientationCode> 

2 Cross reference: Part-1 Section 22.2.16 Field 17.016: Image Property Code (IPC), subfield 

3 vertical orientation 

4 This optional element shall contain the vertical orientation of the image. 

Values for Vertical Orientation shall be one of: “0” for Undefined, “1” for Base, or “2” for Flipped. 

6 “Base” orientation refers to images where the superior (top) edge of the eye is at the top of the 

7 image. “Flipped” orientation refers to images where the orientation is opposite from that 

8 described for “Base”. 

9 <ansi-nist:IrisImageVerticalOrientationCode>1 

</ansi-nist:IrisImageVerticalOrientationCode> 

11 222.2.5.17 Element <ansi-nist:IrisEyeColorAttributeCode> 

12 Cross reference: Part-1 Section 22.2.20 Field 17.020: Eye Color (ECL) 

13 This optional element shall specify the subject's eye color. When used, this element shall contain 

14 an entry chosen from Table 223. 

<ansi-nist:IrisEyeColorAttributeCode>MUL 

16 </ansi-nist:IrisEyeColorAttributeCode> 

17 222.2.5.18 Element <ansi-nist:IrisImageAcquisitionLightingSpectrumValue> 

18 Cross reference: Part-1 Section 22.2.25 Field 17.025: Acquisition Lighting Spectrum (ALS) 

19 This optional element indicates the lighting spectrum used in capturing the iris image. Values 

shall be one of the following: “NIR” for near-infrared illumination (~700-850nm), “VIS” for visible 

21 full-spectrum illumination (~380-740nm), or “OTHER” for other illumination. 

22 <ansi23 nist:IrisImageAcquisitionLightingSpectrumValue>VIS 

24 </ansinist:IrisImageAcquisitionLightingSpectrumValue> 

26 222.2.5.19 Element <ansi-nist:IrisDiameterPixelQuantity> 

27 Cross reference: Part-1 Section 22.2.26 Field 17.026: Iris Diameter (IRD) 

28 This optional element shall specify the expected iris diameter in pixels. 

29 <ansi-nist:IrisDiameterPixelQuantity>304 

</ansi-nist:IrisDiameterPixelQuantity> 

31 222.3 End of Type-17 Iris Data Record 

32 The Type-17 logical record shall end with the XML tag </itl:PackageImageRecord>. 

33 222.4 Additional Type-17 Iris Data Records 

34 Additional Type-17 records may be included in the exchange package. For each additional iris 

image, a complete Type-17 logical record is required. 

156 
 

1 223 Type-99 CBEFF record 

2 The Type-99 logical record shall contain and be used to exchange biometric data that is not 

3 supported by other ANSI/NIST-ITL logical records. This data is exchanged in a format that 

4 conforms to INCITS 398-2005, the Common Biometric Exchange Formats Framework. 

5 The CBEFF conformant Biometric Information Record (BIR) used by the Type-99 logical record 

6 includes a common Header and a Biometric Data Block (BDB). Two mandatory components of 

7 the CBEFF Header are Format Owner and Format Type. The Format Owner denotes the vendor, 

8 standards body, working group, or industry consortium that has defined the format of the 

9 biometric data (the data contained in the BDB). A CBEFF requirement is that format owners 

10 register with the IBIA for an assigned identifier of the format owner. The values used for Format 

11 Type are assigned by the format owner and represent a specific BDB format as specified by the 

12 format owner. This may be a non-standard, unpublished data format or a data format that has 

13 been standardized by an industry group, consortium, or standards body. It is the combination of 

14 CBEFF Format Owner and CBEFF Format Type that uniquely identifies the BDB format. 

15 This Part-2 XML version of the Type-99 logical record provides the CBEFF elements necessary 

16 for users to send, receive, and interpret biometric data in any registered BDB format (with the 

17 exception of biometric data which is exchanged using the other logical records in this standard). 

18 The data carried in the Biometric Data Block element (<nc:BinaryBase64Object>) is the BDB. 

19 The format of that data is identified by the BDB Format Owner (<ansi20 nist:CBEFFFormatOwnerIdentification>) and BDB Format Type (<ansi21 nist:CBEFFFormatCategoryIdentification>) as described by the CBEFF standard. 

22 223.1 XML elements for the Type-99 logical record 

23 The following paragraphs describe the data contained in each of the elements for the Type-99 

24 logical record. 

25 Within a Type-99 logical record, entries shall be provided in XML elements. For each element of 

26 the Type-99 record, Table 239 lists the “condition code” as being mandatory “M” or optional “O”, 

27 the XML tag name, and occurrence limits. It is required that all elements of the record are 

28 ordered as described in the subsections below. Annex F provides an example that includes the 

29 Type-99 record. 

30 The Type-99 record shall be contained within this complex element: 

31 <itl:PackageImageRecord> 

32 [. . . Type 99 Record Content . . .] 

33 </itl:PackageImageRecord> 

34 In the subsections that follow, text in bold between opening and closing tags is informative and 

35 only included for illustrative purposes, unless otherwise specifically stated (as it is for <ansi36 nist:RecordCategoryCode> for example). 

37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

157 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

LEN 99.001 0 

M <ansi-nist:RecordCategoryCode> 1 1 

IDC M 99.002 <ansi-nist:ImageReferenceIdentification> 1 1

UDF O 99.200 – <itl:UserDefinedFields> 0 Unlim

99.998 

 M <ansi-nist:CBEFFImage> 1 1 

BDB M 99.999 <nc:BinaryBase64Object> 1 1

 <ansi-nist:ImageCaptureDetail> 1 1

BCD M 99.005 <ansi-nist:CaptureDate> 1 1

SRC M 99.004 <ansi-nist:CaptureOrganization> 1 1

BDQ O 99.102 <ansi-nist:ImageQuality> 0 1

BFO M 99.103 <ansi-nist:CBEFFFormatOwnerIdentification> 1 1

BFT M 99.104 <ansi-nist:CBEFFFormatCategoryIdentification> 1 1

HDV M 99.100 <ansi-nist:CBEFFVersionIdentification> 1 1

BTY M 99.101 <ansi-nist:CBEFFCategoryCode> 1 1

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 223.1.1 Record length 

2 Cross reference: Part-1 Section 23.1.1 Field 99.001: Logical record length (LEN) 

3 There is no corresponding Part-2 XML element. 

4 223.1.2 Element <ansi-nist:RecordCategoryCode> 

5 This mandatory Part-2 element has no corresponding field in Part-1. It is used to identify the 

6 record type. For the Type-99 record, it shall contain a value of 99. 

7 <ansi-nist:RecordCategoryCode>99 

8 </ansi-nist:RecordCategoryCode> 

9 

10 Table 239 Type-99 CBEFF biometric data record layout 

11 

12 

158 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 223.1.3 Element <ansi-nist:ImageReferenceIdentification> 

2 Cross reference: Part-1 Section 23.1.2 Field 99.002: Image designation character (IDC) 

3 This mandatory complex element shall be used to identify the CBEFF data contained in the 

4 record. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> 

found in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

6 Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

7 <nc:IdentificationID>, which shall contain the image reference identification datum. 

8 <ansi-nist:ImageReferenceIdentification>

9 <nc:IdentificationID>14</nc:IdentificationID>

</ansi-nist:ImageReferenceIdentification> 

11 223.1.4 Element <itl:UserDefinedFields> 

12 Cross reference: Part-1 Section 23.1.13 Fields 99.200-998: User-defined fields (UDF) 

13 These elements are user-definable. Their size and content shall be defined by the user and be in 

14 accordance with the receiving agency. If present they shall contain well-formed XML and ASCII 

content values. 

16 Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

17 Implementers should define, in an extension schema, a substitution element containing user18 defined child elements from the user’s domain. 

19 A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

21 substitutionGroup="itl:UserDefinedFields"

22 type="user-domain:UserDefinedFieldsType"/>

23 

24 <xsd:complexType name="UserDefinedFieldsType">

<xsd:complexContent>

26 <xsd:extension base="s:ComplexObjectType">

27 <xsd:sequence>

28 <xsd:element ref="user-domain:OneField"/>

29 <xsd:element ref="user-domain:TwoField”"/>

</xsd:sequence>

31 </xsd:extension>

32 </xsd:complexContent>

33 </xsd:complexType> 

34 The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

36 <user-domain:OneField>Text</user-domain:OneField> 

37 <user-domain:TwoField>Text</user-domain:TwoField> 

38 </user-domain:UserDefinedFields> 

159 
 

 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 223.1.5 Element <ansi-nist:CBEFFImage> 

2 This is a mandatory complex element. All of the remaining elements in the Type-99 record are 

3 nested within, as described in the subsections below. 

4 <ansi-nist:CBEFFImage> 

[. . . CBEFF elements . . .] 

6 </ansi-nist:CBEFFImage> 

7 223.1.5.1 Element <nc:BinaryBase64Object> 

8 Cross reference: Part-1 Section 23.1.14 Field 99.999: Biometric Data Block (BDB) 

9 This mandatory element shall contain the CBEFF Biometric Data Block (BDB). The binary 

representation shall be converted to ASCII characters using the Base64 encoding algorithm. 

11 <nc:BinaryBase64Object>base64 data 

12 </nc:BinaryBase64Object> 

13 223.1.5.2 Element <ansi-nist:ImageCaptureDetail> 

14 This mandatory complex element contains two child elements described in the subsections 

below: <ansi-nist:CaptureDate>, and <ansi-nist:CaptureOrganization>. 

16 <ansi-nist:ImageCaptureDetail> 

17 [. . . Date, time and source agency elements . . .] 

18 </ansi-nist:ImageCaptureDetail> 

19 223.1.5.2.1 Element <ansi-nist:CaptureDate> 

Cross reference: Part-1 Section 23.1.5 Field 99.005: Biometric creation date (BCD) 

21 This mandatory element shall contain the date and time that the biometric sample was captured. 

22 The date and time shall appear as twenty characters in the format YYYY-MM-DDThh:mm:ssZ. 

23 The YYYY characters shall represent the year; the MM characters shall be the tens and units 

24 values of the month; and the DD characters shall be the tens and units values of the day of the 

month; the character T separates the date from the time; the hh characters represent the hour; 

26 the mm the minute; the ss represents the second; and Z denotes Coordinated Universal Time, 

27 which is abbreviated UTS. The complete date shall not exceed the current date. 

28 Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:DateTime>, which 

29 will contain transaction date and time data. 

<ansi-nist:CaptureDate>

31 <nc:DateTime>2008-02-29T05:25:00Z 

32 </nc:DateTime>

33 </ansi-nist:CaptureDate>

34 

160 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 223.1.5.2.2 Element <ansi-nist:CaptureOrganization> 

2 Cross reference: Part-1 Section 23.1.4 Field 99.004: Source agency / ORI (SRC) 

3 This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

4 <nc:IdentificationID> the identification of the administration or organization that originally captured 

the biometric sample contained in the record, and may contain in <nc:OrganizationName> the 

6 text name of the organization. Normally, the ORI of the agency that captured the image will be 

7 contained in <nc:IdentificationID>. Both <nc:IdentificationID> and <nc:OrganizationName> may 

8 contain up to 36 identifying characters each and the data content of this element shall be defined 

9 by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

11 <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

12 <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

13 contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

14 contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization>

16 <nc:OrganizationIdentification>

17 <nc:IdentificationID>WI013415Y</nc:Identific

18 ationID> 

19 </nc:OrganizationIdentification>

<nc:OrganizationName>Text</nc:OrganizationName>

21 </ansi-nist:CaptureOrganization> 

22 223.1.5.3 Element <ansi-nist:ImageQuality> 

23 Cross reference: Part-1 Section 23.1.9 Field 99.102: Biometric Data Quality (BDQ) 

24 This optional element shall specify quality score data for the biometric data stored in the BDB in 

this record. There are three child elements. They identify a quality score and the algorithm used 

26 to create the quality score. This information is useful to enable the recipient of the quality score to 

27 differentiate between quality scores generated by different algorithms and adjust for any 

28 differences in processing or analysis as necessary. 

29 The parent element <ansi-nist:ImageQuality> may have multiple occurrences, one for each 

quality algorithm used. 

31 1. The child element <ansi-nist:QualityAlgorithmProductIdentification> shall specify a 

32 numeric product code assigned by the vendor of the quality algorithm, which may be registered 

33 with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms 

34 was used in the calculation of the quality score. This complex element contains a child element 

<nc:IdentificationID> which contains the ASCII representation of the integer product code and 

36 should be within the range 1 to 65,535. 

37 2. The child element <ansi-nist:QualityValue> shall be a quantitative expression of the 

38 predicted matching performance of the biometric sample. This element contains the ASCII 

39 representation of the integer image quality score between 0 and 100 assigned to the image data 

by a quality algorithm. Higher values indicate better quality. An entry of “255” shall indicate a 

41 failed attempt to calculate a quality score. An entry of “254” shall indicate that no attempt to 

42 calculate a quality score was made. The use of additional values to convey other information 

43 should be harmonized with ISO/IEC 19794 standards. 

161 
 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 3. The child element <ansi-nist:QualityMeasureVendorIdentification> shall specify the ID of 

2 the vendor of the quality algorithm used to calculate the quality score. This 4-digit hex value is 

3 assigned by IBIA and expressed as four ASCII characters. The IBIA shall maintain the Vendor 

4 Registry of CBEFF Biometric Organizations that will map the value in this element to a registered 

organization. This complex element contains a child element <nc:IdentificationID> which shall 

6 contain the identification datum. 

7 <ansi-nist:ImageQuality>

8 <ansi-nist:QualityAlgorithmProductIdentification>

9 <nc:IdentificationID>28488</nc:Identificatio

nID> 

11 </ansi12 nist:QualityAlgorithmProductIdentification>

13 <ansi-nist:QualityValue>100 

14 </ansi-nist:QualityValue>

<ansi-nist:QualityMeasureVendorIdentification>

16 <nc:IdentificationID>FFF0</nc:Identification

17 ID> 

18 </ansi-nist:QualityMeasureVendorIdentification>

19 </ansi-nist:ImageQuality> 

223.1.5.4Element <ansi-nist:CBEFFFormatOwnerIdentification> 

21 Cross reference: Part-1 Section 23.1.10 Field 99.103: BDB Format Owner (BFO) 

22 This mandatory element shall be used to denote the vendor, standards body, working group, or 

23 industry consortium that has defined the format of the biometric data (in the BDB). In a CBEFF 

24 structure the BDB Format Owner and Format Type, when used in combination, uniquely identify 

the specific format of the BDB content. The format and content of the BDB is “owned” by the 

26 CBEFF Client (see Clause 6.1 of the CBEFF standard). This BDB format definition may be 

27 published (public) or unpublished (non-public). 

28 A CBEFF requirement is that format owners register with IBIA for an assigned identifier of the 

29 format owner. The number is guaranteed to be unique. Refer to the CBEFF standard, Clause 6, 

“CBEFF Patrons and Clients,” for registration information. 

31 Complex element <ansi-nist:CBEFFFormatOwnerIdentification> shall have the simple element 

32 <nc:IdentificationID>, which will contain the four hex digits assigned by IBIA represented by a 

33 string of four ASCII characters. 

34 <ansi-nist:CBEFFFormatOwnerIdentification> 

36 <nc:IdentificationID>FFF0</nc:IdentificationID>

37 </ansi-nist:CBEFFFormatOwnerIdentification> 

38 223.1.5.5 Element <ansi-nist:CBEFFFormatCategoryIdentification> 

39 Cross reference: Part-1 Section 23.1.11 Field 99.104: BDB Format Type (BFT) 

This mandatory element shall be used to identify the value assigned by the format owner to 

41 represent the specific BDB Format as specified by the format owner. This may be a non42 standard, unpublished data format or a data format that has been standardized by an industry 

162 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 group, consortium, or standards body. The registration of the Format Type value is 

2 recommended but not required. Refer to the CBEFF standard, Clause 6, “CBEFF Patrons and 

3 Clients,” for registration information. 

4 Complex element <ansi-nist:CBEFFFormatCategoryIdentification> shall have the simple element 

5 <nc:IdentificationID>, which will contain the four hex digits assigned by the format owner 

6 represented by a string of four ASCII characters. 

7 

8 <ansi-nist:CBEFFFormatCategoryIdentification> 

9 

10 <nc:IdentificationID>000A</nc:IdentificationID>

11 </ansi-nist:CBEFFFormatCategoryIdentification> 

12 223.1.5.6 Element <ansi-nist:CBEFFVersionIdentification> 

13 Cross reference: Part-1 Section 23.1.7 Field 99.100: CBEFF Header Version (HDV) 

14 This mandatory element shall be used to identify the version of CBEFF specification to which this 

15 record conforms. The format is two characters for major version number followed by two 

16 characters for minor version. The current version of CBEFF is INCITS 398-2005 represented by 

17 the string ‘0101’ (major version ‘01’ and minor version ‘01’). 

18 Complex element <ansi-nist:CBEFFVersionIdentification> shall have the simple element 

19 <nc:IdentificationID>, which will contain the version data. 

20 <ansi-nist:CBEFFVersionIdentification>

21 <nc:IdentificationID>0101 

22 </nc:IdentificationID>

23 </ansi-nist:CBEFFVersionIdentification> 

24 223.1.5.7 Element <ansi-nist:CBEFFCategoryCode> 

25 Cross reference: Part-1 Section 23.1.8 Field 99.101: Biometric Type (BTY) 

26 This mandatory element shall be used to identify the type of biometric technology. This 

27 specification adopts the values presented in CBEFF with the addition of two leading zeros for 

28 future expansion. Table 240 lists the current biometric type codes. 

29 <ansi-nist:CBEFFCategoryCode>200 

30 </ansi-nist:CBEFFCategoryCode> 

31 

32 223.2 End of Type-99 CBEFF Data Record 

33 The Type-99 logical record shall end with the XML tag </itl:PackageImageRecord>. 

34 223.3 Additional Type-99 CBEFF Data Records 

35 Additional Type-99 records may be included in the exchange package. For each additional 

36 CBEFF record, a complete Type-99 logical record is required. 

37 

163 
 

 

 

 

 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Table 240 CBEFF Biometric type 

Biometric Type 

Name 

Biometric Type 

Code 

No Information Given ‘00000000’ 

Multiple Biometrics Used ‘00000001' 

Facial Features ‘00000002' 

Voice ‘00000004' 

Fingerprint ‘00000008' 

Iris ‘00000010' 

Retina ‘00000020' 

Hand Geometry ‘00000040' 

Signature Dynamics ‘00000080' 

Keystroke Dynamics ‘00000100' 

Lip Movement ‘00000200' 

Thermal Face Image ‘00000400' 

Thermal Hand Image ‘00000800' 

Gait ‘00001000' 

Body Odor ‘00002000' 

DNA ‘00004000' 

Ear Shape ‘00008000' 

Finger Geometry ‘00010000' 

Palm Print ‘00020000' 

Vein Pattern ‘00040000' 

Foot Print ‘00080000’ 

2 

3 224 Another individual 

4 If fingerprint or other biometric data for another individual is to be recorded or transmitted, a new 

5 information exchange package shall be generated for that individual using the same format as 

6 described previously. 

164 
 

1 Annex A 7-bit American Standard Code for Information Interchange (ASCII) 

2 (normative) 

3 

 

 

 

 

 

 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

B 7 = M S B 

b 6 

b 5 

→

→

→

0 

0 

0 

0 

0 

1 

0 

1 

0 

0 

1 

1 

1 

0 

0 

1 

0 

1 

1 

1 

0 

1 

1 

1 

B 

i 

t 

s 

b 4 

↓

b 3 

↓

b 2 

↓

b 1 

↓

COLUMN 

→

ROW ↓

0 1 2 3 4 5 6 7 

0 0 0 0 0 N U L D L E S P 0 @ P  p 

0 0 0 1 1 S O H D C 1 ! 1 A Q a q 

0 0 1 0 2 S T X D C 2 " 2 B R b r 

0 0 1 1 3 E T X D C 3 # 3 C S c s 

0 1 0 0 4 E O T D C 4 $ 4 D T d t 

0 1 0 1 5 E N Q N A K % 5 E U e u 

0 1 1 0 6 A C K S Y N & 6 F V f v 

0 1 1 1 7 B E L E T B  7 G W g w 

1 0 0 0 8 B S C A N ( 8 H X h x 

1 0 0 1 9 H T E M ) 9 I Y i y 

1 0 1 0 10 L F S U B * : J Z j z 

1 0 1 1 11 V T E S C + ; K [ K { 

1 1 0 0 12 F F F S , < L \ | 

1 1 0 1 13 C R G S - = M ] m } 

1 1 1 0 14 S O R S . > N ^ n  ̃ 

1 1 1 1 15 S I U S / ? O _ o D E L 

4 

5 

6 

165 
1 Annex B Package Schema 

2 (normative) 3 4 This Annex contains the ITL package schema from “ITL-2007e-Package.xsd”. 5 6 7 8 <?xml version="1.0" encoding="UTF-8"?> 9 <xsd:schema 

10 targetNamespace="http://itl.nist.gov/biometric/1-2007" 

11 xmlns:itl="http://itl.nist.gov/biometric/1-2007" 12 xmlns:xsd="http://www.w3.org/2001/XMLSchema" 13 xmlns:s="http://niem.gov/niem/structures/2.0" 14 xmlns:ansi-nist="http://niem.gov/niem/ansi-nist/2.0" 15 xmlns:i="http://niem.gov/niem/appinfo/2.0" 16 elementFormDefault="qualified" 17 attributeFormDefault="unqualified"> 18 19 <!-- =============================== --> 20 <!-- IMPORTED SCHEMA --> 

21 <!-- =============================== --> 

22 <xsd sc:import hemaLocation="niem/ansi-nist/2.0/ansi-nist_itl_constraint.xsd" namespace="http://niem.gov/niem/an23 <xsd sc:import hemaLocation="niem/structures/2.0/structures.xsd" namespace="http://niem.gov/niem/structures/2.024 <xsd:imp schemort aLocation="niem/appinfo/2.0/appinfo.xsd" namespace="http://niem.gov/niem/appinfo/2.0"/> 25 26 <!-- =============================== --> 27 <!-- NIST-ITL BIOMETRIC INFORMATION EXCHANGE PACKAGE --> 28 <!-- =============================== --> 29 <xsd:element name="NISTBiometricInformationExchangePackage" type="itl:NISTBiometricInformationExchangeP

30 <xsd:element name="PackageInformationRecord" type="itl:PackageInformationRecordType"/>

31 <xsd:element name="PackageDescriptiveTextRecord" type="itl:PackageDescriptiveTextRecordType"/> 

32 <xsd:element name="PackageDataRecord" abstract="true"/> 

33 <!-- RECORD SUBSTITUTION GROUP --> 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

166 
<xsd:element name="PackageImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImage

<xsd:element name="PackageMinutiaeRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageMin

<!-- =============================== --> <!-- PACKAGE TYPE DEFINITION --> <!-- =============================== -->

 <xsd:complex name= Type "NISTBiometricInformationExchangePackageType">  <xsd:complexContent>  <xsd:extensi baseon ="s:ComplexObjectType">  <xsd:sequence>  <xsd:ele ref="i ment tl:PackageInformationRecord"/>  <xsd:element ref="itl:PackageDescriptiveTextRecord" maxOccurs="unbounded"/> 

 <xsd:element ref="itl:PackageDataRecord" minOccurs="0" maxOccurs="unbound </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- =============================== --> 

<!-- RECORD TYPE DEFINITIONS --> <!-- =============================== --> 

<!-- Record Type 01 --> 

 <xsd:complex name= Type "PackageInformationRecordType"> 

 <xsd:complexContent>  <xsd:extensi baseon ="s:ComplexObjectType">  <xsd:sequence>  <xsd:ele ref="an ment si-nist:RecordCategoryCode"/>

 <xsd ref= :element "ansi-nist:Transaction"/> </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- Record Type Base for 02 through 99 --> 

 <xsd:complex name= Type "PackageDataRecordType">  <xsd:complexContent> 

1 2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

167 
 <xsd:extensi baseon ="s:ComplexObjectType"> 

 <xsd:sequence>  <xsd:ele ref="an ment si-nist:RecordCategoryCode"/> 

<!-- ====================================================== fieldID="XX.002" fieldMne

 <xsd:ele ref="an ment si-nist:ImageReferenceIdentification"/> 

<!-- =================================================== fieldID="XX.200-998" fieldMne

 <xsd ref= :element "itl:UserDefinedFields" minOccurs="0"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- Record Type 02 --> 

 <xsd:complex name= Type "PackageDescriptiveTextRecordType"> 

 <xsd:complexContent>  <xsd:extensi base="on itl:PackageDataRecordType">  <xsd:sequence>  <xsd ref="itl :element :UserDefinedDescriptiveText"/> 

 </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- Image Records: 03, 04, 05, 06, 07, 08, 10, 13, 14, 15, 16, 17, 99 --> 

 <xsd:complex name= Type "PackageImageRecordType"> 

 <xsd:complexContent>  <xsd:extensi base="on itl:PackageDataRecordType">  <xsd:sequence>  <xsd:el ref="an ement si-nist:RecordImage"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- Minutiae Record: 09 --> 

 <xsd:complex name= Type "PackageMinutiaeRecordType"> 

 <xsd:complexContent> 

1 2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

168 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <xsd:extension base="itl:PackageDataRecordType">  <xsd:sequence>  <xsd:element ref="ansi-nist:MinutiaeImpressionCaptureCategory"/>  <xsd:element ref="ansi-nist:MinutiaeFormatNISTStandardIndicator"/>  <xsd:element ref="itl:RecordMinutiae"/> </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- =============================== --> <!-- IMAGE RECORDS SUBSTITUTION GROUP --> <!-- =============================== --> <xsd:element name="FingerprintImage" substitutionGroup="ansi-nist:RecordImage" type="itl:FingerprintImageTyp<xsd:element name="PalmprintImage" substitutionGroup="ansi-nist:RecordImage" type="itl:PalmprintImageType"<xsd:element name="IrisImage" substitutionGroup="ansi-nist:RecordImage" type="itl:IrisImageType"/> 

<xsd:element name="TestImage" substitutionGroup="ansi-nist:RecordImage" type="ansi-nist:NISTImageType"/> 

<xsd:element name="FaceImage" substitutionGroup="ansi-nist:RecordImage" type="itl:FaceImageType"/> <!-- Here is a sample substitute for the Type07 user defined image. Users should create their own in a different do<xsd:element name="ExampleRecordImage" substitutionGroup="ansi-nist:RecordImage" type="xsd:anyType" nilla<!-- =============================== --> <!-- MINUTIAE RECORD SUBSTITUTION GROUP --> <!-- =============================== --> <xsd:element name="RecordMinutiae" abstract="true"/> <xsd:element name="Minutiae" substitutionGroup="itl:RecordMinutiae" type="itl:MinutiaeType"/> <!-- =============================== --> <!-- ITL ELEMENTS --> <!-- =============================== -->

 <xsd:element name="FingerprintImageSegmentPositionSquare" type="itl:FingerprintImageSegmentPositionSquare

 <xsd:element name="FingerprintImageSegmentPositionPolygon" type="itl:FingerprintImageSegmentPositionPolyg <xsd:element name="FingerprintImageFingerMissing" type="itl:FingerprintImageFingerMissingType"/>  <xsd:element name="FingerprintImageQuality" type="ansi-nist:FingerprintImageQualityType"/>  <xsd:element name="PalmprintImageQuality" type="itl:PalmprintImageQualityType"/>  <xsd:element name="PositionPolygonVertexQuantity" type="xsd:nonNegativeInteger"/> 

 <xsd:element name="PositionPolygonVertex" type="itl:PositionPolygonVertexType"/>  <xsd:element name="FingerMissingCode" type="itl:AMPCodeType"/> 

169 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <xsd:element name="IrisDiameterPixelQuantity" type="xsd:nonNegativeInteger" nillable="true"/>  <xsd:element name="FaceImageAcquisitionSource" type="itl:FaceImageAcquisitionSourceType"/> 

 <xsd:element name="CaptureSourceDescriptionText" type="xsd:string"/> 

<!-- ITL USER DEFINED DESCRIPTIVE TEXT AND FIELDS -->

 <xsd:element name="UserDefinedDescriptiveText" type="itl:UserDefinedDescriptiveTextType"/> 

<!-- Users may define substitutes for the following abstract elements . -->

 <xsd:element name="DomainDefinedDescriptiveText" abstract="true"/> 

 <xsd:element name="OtherDescriptiveText" abstract="true"/> 

<xsd:element name="UserDefinedFields" abstract="true"/> <!-- Here are sample substitutes for user-defined abstract elements. Users should create their own in a different d

 <xsd:element name="ExampleDomainDefinedDescriptiveText" substitutionGroup="itl:DomainDefinedDescriptiveTtype="xsd:anyType" nillable="true"/>  <xsd:element name="ExampleOtherDescriptiveText" substitutionGroup="itl:OtherDescriptiveText" type="xsd:anyT

<xsd:element name="ExampleUserDefinedFields" substitutionGroup="itl:UserDefinedFields" type="xsd:anyType" <!-- =============================== --> <!-- CORRECTED NIEM 2.0 ELEMENTS --> <!-- =============================== -->

 <xsd:element name="MinutiaeNISTStandard" type="itl:NISTStandardMinutiaeType"/> 

<xsd:element name="MinutiaDetail" type="itl:MinutiaType"/> 

 <xsd:element name="MinutiaeFingerPatternDetail" type="itl:MinutiaeFingerPatternType"/> 

 <xsd:element name="FingerPatternCodeSourceCode" type="itl:PCSCodeType" nillable="true"/> 

<!-- =============================== --> <!-- ITL ELEMENT TYPES --> <!-- =============================== -->

 <xsd:complexType name="FingerprintImageType">  <xsd:complexContent>  <xsd:extension base="ansi-nist:NISTImageType">  <xsd:sequence> 

<!-- =====================================================fieldID="XX.003" fieldMnem

 <xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory"/> 

<!-- =====================================================fieldID="XX.013" fieldMnem

 <xsd:element ref="ansi-nist:FingerPositionCode" maxOccurs="unbounded"/> 

<!-- =====================================================fieldID="XX.014" fieldMnem<!-- =====================================================fieldID="XX.015" fieldMnem

170 
 <xsd:el ref="an ement si-nist:FingerprintImageMajorCasePrint" minOccurs="0"/> 

<!-- =====================================================fieldID="14.018" fieldMnemo

 <xsd:element ref="itl:FingerprintImageFingerMissing" minOccurs="0" maxOccurs=

<!-- =====================================================fieldID="14.021" fieldMnemo<xsd:element ref="itl:FingerprintImageSegmentPositionSquare" minOccurs="0" maxOccurs<!-- =====================================================fieldID="14.022" fieldMnemo

 <xsd:ele ref="an ment si-nist:FingerprintImageNISTQuality" minOccurs="0" maxOc

<!-- =====================================================fieldID="14.023" fieldMnemo<xsd:element ref="ansi-nist:FingerprintImageSegmentationQuality" minOccurs="0" maxOcc<!-- =====================================================fieldID="13.024" fieldMnemo

 <!-- =====================================================fieldID="14.024" fieldMnemo

 <xsd:element ref="itl:FingerprintImageQuality" minOccurs="0" maxOccurs="unbou

<!-- =====================================================fieldID="14.025" fieldMnemo

 <xsd:element ref="itl:FingerprintImageSegmentPositionPolygon" minOccurs="0" m

 </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType>

 <xsd:complex name= Type "PalmprintImageType">  <xsd:complexContent>  <xsd:extensi baseon ="ansi-nist:NISTImageType">  <xsd:sequence> 

<!-- =====================================================fieldID="XX.003" fieldMnem

 <xsd:ele ref="an ment si-nist:FingerprintImageImpressionCaptureCategory"/> 

<!-- =====================================================fieldID="13.013" fieldMnemo<!-- =====================================================fieldID="15.013" fieldMnemo

 <xsd:element si-nist ref="an :PalmPosition" maxOccurs="unbounded"/> 

<!-- =====================================================fieldID="13.024" fieldMnemo<!-- =====================================================fieldID="15.024" fieldMnemo

 <xsd:element ref="itl:PalmprintImageQuality" minOccurs="0" maxOccurs="unboun </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complex name= Type "IrisImageType"> 

123456789

101112131415161718192021222324252627282930313233343536373839 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <xsd:complexContent> 

171 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <xsd:extension base="ansi-nist:NISTImageType">  <xsd:sequence> 

<!-- =====================================================fieldID="17.003" fieldMnemo

 <xsd:element ref="ansi-nist:IrisEyePosition"/> 

<!-- =====================================================fieldID="17.014" fieldMnemo

 <xsd:element ref="ansi-nist:IrisEyeRotationAngleMeasure" minOccurs="0"/> 

<!-- =====================================================fieldID="17.015" fieldMnemo

 <xsd:element ref="ansi-nist:IrisEyeRotationUncertaintyValueText" minOccurs="0"/

<!-- ===========See complex in ansi-nist file =================================

 <xsd:element ref="ansi-nist:IrisImageCapture" minOccurs="0" maxOccurs="unbou

<!-- =====================================================fieldID="17.020" fieldMnemo

 <xsd:element ref="ansi-nist:IrisEyeColorAttributeCode" minOccurs="0"/> 

<!-- =====================================================fieldID="17.025" fieldMnemo

 <xsd:element ref="ansi-nist:IrisImageAcquisitionLightingSpectrumValue" minOccu

<!-- =====================================================fieldID="17.026" fieldMnemo

 <xsd:element ref="itl:IrisDiameterPixelQuantity" minOccurs="0"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="FaceImageType">  <xsd:complexContent>  <xsd:extension base="ansi-nist:FaceImageType">  <xsd:sequence> 

<!-- =====================================================fieldID="10.023" fieldMnemo

 <xsd:element ref="itl:FaceImageAcquisitionSource" minOccurs="0"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="UserDefinedDescriptiveTextType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="itl:DomainDefinedDescriptiveText"/> 

172 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <xsd:element ref="itl:OtherDescriptiveText" minOccurs="0"/> </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="FingerprintImageSegmentPositionSquareType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="ansi-nist:FingerPositionCode"/>  <xsd:element ref="ansi-nist:SegmentBottomVerticalCoordinateValue"/>  <xsd:element ref="ansi-nist:SegmentLeftHorizontalCoordinateValue"/>  <xsd:element ref="ansi-nist:SegmentRightHorizontalCoordinateValue"/>  <xsd:element ref="ansi-nist:SegmentTopVerticalCoordinateValue"/> </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="FingerprintImageSegmentPositionPolygonType">  <xsd:complexContent>  <xsd:extension base="ansi-nist:FingerprintType">  <xsd:sequence>  <xsd:element ref="itl:PositionPolygonVertexQuantity"/>  <xsd:element ref="itl:PositionPolygonVertex" minOccurs="3" maxOccurs="99"/> </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="PositionPolygonVertexType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue"/> <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue"/> 

173 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="FingerprintImageFingerMissingType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="ansi-nist:FingerPositionCode"/>  <xsd:element ref="itl:FingerMissingCode"/> </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="AMPCodeType">  <xsd:annotation>  <xsd:appinfo> <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> </xsd:appinfo> </xsd:annotation>  <xsd:simpleContent>  <xsd:extension base="xsd:token">  <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>  </xsd:extension>  </xsd:simpleContent>  </xsd:complexType> <xsd:complexType name="PalmprintImageQualityType">  <xsd:complexContent>  <xsd:extension base="ansi-nist:FingerprintPalmImagePositionType">  <xsd:sequence>  <xsd:element ref="ansi-nist:QualityAlgorithmProductIdentification"/>  <xsd:element ref="ansi-nist:QualityAlgorithmVendorIdentification"/>  <xsd:element ref="ansi-nist:QualityValue"/>  </xsd:sequence> 

174 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="FaceImageAcquisitionSourceType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="ansi-nist:CaptureSourceCode"/>  <xsd:element ref="itl:CaptureSourceDescriptionText" minOccurs="0"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

<!-- =============================== --> <!-- CORRECTIONS TO NIEM 2.0 ELEMENTS --> <!-- =============================== -->

 <xsd:complexType name="MinutiaeType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="itl:MinutiaeNISTStandard"/> 

<!-- ======================================================== fieldID="9.008" fieldMne

 <xsd:element ref="ansi-nist:MinutiaeFingerCorePosition" minOccurs="0" maxOccu

<!-- ======================================================== fieldID="9.009" fieldMne

 <xsd:element ref="ansi-nist:MinutiaeFingerDeltaPosition" minOccurs="0" maxOcc

<!-- ======================================================== fieldID="9.007" fieldMne

 <xsd:element ref="itl:MinutiaeFingerPatternDetail" minOccurs="0" maxOccurs="un

<!-- ======================================================== fieldID="9.006" fieldMne

 <xsd:element ref="ansi-nist:MinutiaeFingerPosition" minOccurs="0" maxOccurs=" <xsd:element ref="ansi-nist:MinutiaePalmPosition" minOccurs="0" maxOccurs="u </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> 

175 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <xsd:complexType name="NISTStandardMinutiaeType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence> 

<!-- ======================================================== fieldID="9.012" fieldMne

 <xsd:element ref="itl:MinutiaDetail" maxOccurs="unbounded"/> 

<!-- ======================================================== fieldID="9.010" fieldMne

 <xsd:element ref="ansi-nist:MinutiaeQuantity"/> 

<!-- ======================================================== fieldID="9.005" fieldMne

 <xsd:element ref="ansi-nist:MinutiaeReadingSystem" minOccurs="0"/> 

<!-- ======================================================== fieldID="9.011" fieldMne

 <xsd:element ref="ansi-nist:MinutiaeRidgeCountIndicator"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="MinutiaType">  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue"/> <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue"/>  <xsd:element ref="ansi-nist:MinutiaIdentification"/>  <xsd:element ref="ansi-nist:PositionThetaAngleMeasure"/> <!--

==Move 3 elements from NISTStandardMinutiaeType==== --> 

 <xsd:element ref="ansi-nist:MinutiaQualityValue" minOccurs="0"/>  <xsd:element ref="ansi-nist:MinutiaCategory" minOccurs="0"/>  <xsd:element ref="ansi-nist:MinutiaRidgeCount" minOccurs="0" maxOccurs="unb </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:complexType name="MinutiaeFingerPatternType">  <xsd:annotation>  <xsd:appinfo> 

176 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> </xsd:appinfo> </xsd:annotation>  <xsd:complexContent>  <xsd:extension base="s:ComplexObjectType">  <xsd:sequence>  <xsd:element ref="itl:FingerPatternCodeSourceCode"/> <xsd:element ref="ansi-nist:FingerPattern"/>  </xsd:sequence>  </xsd:extension>  </xsd:complexContent>  </xsd:complexType> <xsd:simpleType name="PCSCodeSimpleType">  <xsd:annotation>  <xsd:appinfo> <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> </xsd:appinfo> </xsd:annotation>  <xsd:restriction base="xsd:token">  <xsd:enumeration value="T">  <xsd:annotation>  <xsd:documentation>Pattern codes from Table 16</xsd:documentation>  </xsd:annotation>  </xsd:enumeration>  <xsd:enumeration value="U">  <xsd:annotation>  <xsd:documentation>User-defined pattern codes</xsd:documentation>  </xsd:annotation>  </xsd:enumeration>  </xsd:restriction>  </xsd:simpleType>  <xsd:complexType name="PCSCodeType">  <xsd:annotation>  <xsd:appinfo> <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> </xsd:appinfo> </xsd:annotation> 

177 
1 

2 3 4 5 6 7 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <xsd:simpleContent>  <xsd:extension base="itl:PCSCodeSimpleType">  <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>  </xsd:extension>  </xsd:simpleContent>  </xsd:complexType> </xsd:schema> 

178 
 

5 

10 

15 

20 

25 

30 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Annex C Base-64 encoding scheme 

2 (normative) 

3 

4 The base-64 Content-Transfer-Encoding is designed to represent arbitrary sequences of octets in 

a form that need not be humanly readable. The encoding and decoding algorithms are simple, but 

6 the encoded data are consistently only about 33 percent larger than the unencoded data. This 

7 encoding is virtually identical to the one used in Privacy Enhanced Mail (PEM) applications, as 

8 defined in RFC 1421. The base-64 encoding is adapted from RFC 1421, with one change: base9 64 eliminates the "*" mechanism for embedded clear text. 

11 

A 65-character subset of US-ASCII is used, enabling 6 bits to be represented per printable 

character. (The extra 65th character, "=", is used to signify a special processing function.) 

12 NOTE: This subset has the important property that it is represented identically in all versions of 

13 ISO 646, including US ASCII and all characters in the subset are also represented identically in 

14 all versions of EBCDIC. Other popular encodings, such as the encoding used by the uuencode 

utility and the base-85 encoding specified as part of Level 2 PostScript, do not share these 

16 properties, and thus do not fulfill the portability requirements a binary transport encoding for mail 

17 must meet. 

18 The encoding process represents 24-bit groups of input bits as output strings of 4 encoded 

19 characters. Proceeding from left to right, concatenating 3 8-bit input groups forms a 24-bit input 

group. These 24 bits are then treated as 4 concatenated 6-bit groups, each of which is translated 

21 into a single digit in the base-64 alphabet. When encoding a bit stream via the base-64 encoding, 

22 the bit stream must be presumed to be ordered with the most significant bit first. That is, the first 

23 bit in the stream will be the high-order bit in the first byte, and the eighth bit will be the low-order 

24 bit in the first byte, and so on. 

Each 6-bit group is used as an index into an array of 64 printable characters. The character 

26 referenced by the index is placed in the output string. These characters, identified in Table C1, 

27 below, are selected so as to be universally representable, and the set excludes characters with 

28 particular significance to SMTP (e.g., ".", CR, LF) and to the encapsulation boundaries defined in 

29 this document (e.g., "-"). 

The output stream (encoded bytes) must be represented in lines of no more than 76 characters 

31 each. All line breaks or other characters not found in Table C1 must be ignored by decoding 

32 software. In base-64 data, characters other than those in Table C1, line breaks, and other white 

33 space probably indicate a transmission error, about which a warning message or even a 

34 message rejection might be appropriate under some circumstances. 

179 
 

1 

2 Table C1 – Base-64 alphabet 

3 Value Value Value Value 

4 Encoding Encoding Encoding Encoding 

5 0 A 17 R 34 I 51 z 

6 1 B 18 S 35 j 52 0 

7 2 C 19 T 36 k 53 1 

8 3 D 20 U 37 l 54 2 

9 4 E 21 V 38 m 55 3 

10 5 F 22 W 39 n 56 4 

11 6 G 23 X 40 o 57 5 

12 7 H 24 Y 41 p 58 6 

13 8 I 25 Z 42 q 59 7 

14 9 J 26 a 43 r 60 8 

15 10 K 27 b 44 s 61 9 

16 11 L 28 c 45 t 62 + 

17 12 M 29 d 46 u 63 / 

18 13 N 30 e 47 v 

19 14 O 31 f 48 w (pad) = 

20 15 P 32 g 49 x 

21 16 Q 33 h 50 y 

22 

23 Special processing is performed if fewer than 24 bits are available at the end of the data being 

24 encoded. A full encoding quantum is always completed at the end of a body. When fewer than 24 

25 input bits are available in an input group, zero bits are added (on the right) to form an integral 

26 number of 6-bit groups. Padding at the end of the data is performed using the '=' character. Since 

27 all base-64 input is an integral number of octets, only the following cases can arise: (1) the final 

28 quantum of encoding input is an integral multiple of 24 bits; here, the final unit of encoded output 

29 will be an integral multiple of 4 characters with no "=" padding, (2) the final quantum of encoding 

30 input is exactly 8 bits; here, the final unit of encoded output will be two characters followed by two 

31 "=" padding characters, or (3) the final quantum of encoding input is exactly 16 bits; here, the final 

32 unit of encoded output will be three characters followed by one "=" padding character. 

33 Because it is used only for padding at the end of the data, the occurrence of any '=' characters 

34 may be taken as evidence that the end of the data has been reached (without truncation in 

35 transit). No such assurance is possible, however, when the number of octets transmitted was a 

36 multiple of three. 

37 Any characters outside of the base-64 alphabet are to be ignored in base-64-encoded data. The 

38 same applies to any illegal sequence of characters in the base-64 encoding, such as "=====" 

39 .Care must be taken to use the proper octets for line breaks if base-64 encoding is applied 

40 directly to text material that has not been converted to canonical form. In particular, text line 

41 breaks must be converted into CRLF sequences prior to base-64 encoding. The important thing 

42 to note is that this may be done directly by the encoder rather than in a prior cannibalization step 

43 in some implementations. 

44 NOTE: There is no need to worry about quoting apparent encapsulation boundaries within base45 64-encoded parts of multipart because no hyphen characters are used in the base-64 encoding. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

180 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

181 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Annex D JPEG file interchange format 

(normative) 

Version 1.02 

September 1, 1992 

1 408 944-6300 

Fax: +1 408 944-6314 

E-mail: eric@c3.pla.ca.us 

182 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Why a file interchange format 

2 JPEG File Interchange Format (JFIF) is a minimal file format, which enables JPEG bitstreams to be 

3 exchanged between a wide variety of platforms and applications. This minimal format does not include 

4 any of the advanced features found in the TIFF JPEG specification or any application specific file format. 

The only purpose of this simplified format is to allow the exchange of JPEG compressed images. 

6 JPEG file interchange format 

7 • Uses JPEG compression 

8 • Uses JPBG interchange format compressed image representation 

9 • PC or Mac or UNIX workstation compatible 

• Standard color space: one or three components. For three components YCbCr (CCIR 601-256 levels) 

11 • APP0 marker used to specify Units, X pixel density, Y pixel density, thumbnail 

12 • APP0 marker also used to specify JFIF extensions 

13 • APP0 mater also used to specify application-specific information 

14 JPEG compression 

Although any JPEG process is supported by the syntax of the JFIF it is strongly recommended that the 

16 JPEG baseline process be used for the purposes of file interchange. This ensures maximum compatibility 

17 with all applications supporting JPEG. JFIF conforms to the JPEG Draft International Standard (ISO DIS 

18 10918-1). 

19 The JFIF is entirely compatible with the standard JPEG interchange format; the only additional 

requirement is the mandatory presence of the APP0 marker right after the SOI marker. Note that the 

21 JPEG interchange format requires (as does JFIF) all table specifications used in the encoding process be 

22 coded in the bitstream prior to their use. 

23 Compatible across platforms 

24 The JFIF is compatible across platforms: for example, it can use any resource forks supported by the 

Macintosh and by PCs or workstations, but not just one platform. 

26 Standard color space 

27 The color space to be used is YCbCr as defined by CCIR 601(256 levels). The RGB components 

28 calculated by linear conversion from YCbCr shall not be gamma corrected (gamma = 1.0). If only one 

29 component is used, that component shall be Y. 

APP0 marker is used to identify JPEG FIF 

31 • The APP0 marker is used to identify a JPEG FIF file. 

32 • The JPEG FIF APP0 marker is mandatory right after the SOI marker. 

33 • The JFIF APP0 marker is identified by a zero terminated string: “JFIF”. 

34 • The APP0 can be used for any other purpose by the application provided it can be distinguished from 

the JFIF APP0. 

36 • The JFIF APP0 marker provides information which is missing from the JPEG stream: version number, 

37 X and Y pixel density (dots per inch or dots per cm), pixel aspect ratio (derived from X and Y pixel 

38 density), thumbnail. 

183 
 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 APP0 marker used to specify JFIF extensions 

2 Additional APP0 marker segment(s) can optionally be used to specify JFIF extensions. If used, these 

3 segments must immediately follow the JFIF APP0 marker. Decoders should skip any unsupported JFIF 

4 extension segments and continue decoding. 

The JFIF extension APP0 marker is identified by a zero terminated string: "JFXX". The JFIF extension 

6 APP0 marker segment contains a 1-byte code, which identifies the extension. This version, version 1.02, 

7 has only one extension defined: an extension for defining thumbnails stored in formats other than 24-bit 

8 RGB. 

9 APP0 marker used for application-specific information 

Additional APP0 marker segments can be used to hold application-specific information which does not 

11 affect the decodability or displayability of the JFIF file. Application-specific APP0 marker segments must 

12 appear after the JFIF APP0 and any JFXX APP0 segments. Decoders should skip any unrecognized 

13 application-specific APP0 segments. 

14 Application-specific APP0 marker segments are identified by a zero terminated string which identifies the 

application (not “JFlF” or "JFXX"). This string should be an organization name or company trademark. 

16 Generic strings such as dog, cat, tree, etc. should not be used. 

17 Conversion to and from RGB 

18 Y, Cb, and Cr are converted from R, G, and B as defined in CCIR Recommendation 601 but are 

19 normalized so as to occupy the full 256 levels of an 8-bit binary encoding. More precisely: 

Y = 256 * E'y 

21 Cb = 256 * [ E'Cb] + 128 

22 Cr= 256 * [ E'Cr] + 128 

23 where the E'y E'Cb and E'Cr are defined as in CCIR 601. Since values of E'y have a range of 0 to 1.0 and 

24 those for E'Cb and E'Cr have a range of -0.5 to +0.5, Y, Cb, and Cr must be clamped to 255 when they are 

maximum value. 

26 RGB to YCbCr conversion 

27 YCbCr (256 levels) can be computed directly from 8-bit RGB as follows: 

28 Y = 0.299 R + 0.587G + 0.114B 

29 Cb = -0.1687 R - 0.3313 G + 0.5 B + 128 

Cr = 0.5R - 0.4177 G - 0.0813 B + 128 

31 NOTE - Not all image file formats store image samples in the order R0, G0, B0, ... Rn, Gn, Bn. Be sure to 

32 verify the sample order before converting an RGB file to JFIF 

33 YCbCr to RGB conversion 

34 RGB can be computed directly from YCbCr (256 levels) as follows: 

R = Y + 1.402 (Cr - 128) 

36 G = Y-0.34414 (Cb - 128) - 0.71414 (Cr - 128) 

37 B = Y + 1.772 (Cb - 128) 

184 
 

 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Image orientation 

2 In JFIF files, the image orientation is always top-down. This means that the first image samples encoded 

3 in a JFIF file are located in the upper left hand corner of the image and encoding proceeds from left to 

4 right and top to bottom. Top-down orientation is used for both the full resolution image and the thumbnaiI 

5 image. 

6 The process of converting an image file having bottom-up orientation to JFIF must include inverting the 

7 order of all image lines before JPEG encoding. 

8 Spatial relationship of components 

9 Specification of the spatial positioning of pixel samples within components relative to the samples of other 

10 components is necessary for proper image post processing and accurate image presentation. In JFIF 

11 files, the position of the pixels in subsampled components are defined with respect to the highest 

12 resolution component. Since components must be sampled orthogonally (along rows and columns), the 

13 spatial position of the samples in a given subsampled component may be determined by specifying the 

14 horizontal and vertical offsets of the first sample, i.e. the sample in the upper left corner, with respect to 

15 the highest resolution component. 

16 The horizontal and vertical offsets of the first sample in a subsampled component, Xoffseti [0,0] and 

17 Yoffseti [0,0], are defined to be: 

18 Xoffseti

[0,0] = ((Nsamplesref / Nsamplesj) / 2) - 0.5 

19 Yoffseti

[0,0] = ((Nlinesref / Nlinesi) / 2) - 0.5 

20 where 

21 Nsamplesref is the number of samples per line in the largest component; 

22 Nsamplesi

 is the number of samples per line in the ith component; 

23 Nlinesref is the number of lines in the largest component; 

24 Nlinesi

 is the number of lines in the ith component. 

25 Proper subsampling of components incorporates an anti-aliasing filter which reduces the spectral 

26 bandwidth of the full resolution components. Subsampling can easily be accomplished using a 

27 symmetrical digital filter with an even number of taps (coefficients). A commonly used filter for 2:1 

28 subsampling utilizes two taps (1/2,1/2). 

29 As an example, consider a 3 component image which is comprised of components having the following 

30 dimensions: 

31 Component 1: 256 samples, 288 lines 

32 Component 2: 128 samples, 144 lines 

33 Component 3: 64 samples, 96 lines 

34 In a JFIF file, centers of the samples are positioned as illustrated below: 

35 x x x x 

36  

37 x x  x x 

38 x x x x 

39  

40 x x x x 

185 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

where 

X Component 1 

 Component 2 

 Component 3 

NOTE - This definition is compatible with industry standards such as Postscript Level 2 and QuickTime. 

This definition is not compatible with the conventions used by CCIR Recommendation 601-I and other 

digital video formats. For these formats, pre-processing of the chrominance components is necessary 

prior to compression in order to ensure accurate reconstruction of the compressed image. 

JPEG fiIe interchange format specification 

The syntax of a JFIF file conforms to the syntax for interchange format defined in Annex B of ISO DIS 

10918-1. In addition, a JFIF file uses APP0 marker segments and constrains certain parameters in the 

frame header as defined below. 

X'FF', SOI 

X’FF’, APP0, length, identifier, version, units, Xdensity, Ydensity, Xthumbnail, Ythumbnail, (RGB)n 

Length (2 bytes) Total APP0 field byte count,

including the 

byte count value (2 bytes), but excluding 

the APP0 marker itself 

identifier (5 bytes) = X'4A', X'46', X'49’, X’46', X'00' 

This zero terminated string ("JFIF") 

Uniquely identifies this APP0 marker. This 

string shall have zero parity (bit 7=0). 

version (2 bytes) = X'0102' 

The most significant byte is used for major 

revisions, the least significant byte for 

minor revisions. Version 1.02 is the 

current released revision. 

units (1 byte) Units for the X and Y densities 

units = 0: no units, X and Y specify the pixel 

units = 1: X and Y are dots per inch 

units = 2: X and Y are dots per cm 

Xdensity (2 bytes) Horizontal pixel density 

Ydensity (2 bytes) Vertical pixel density 

XthumbnaiI (1 byte) Thumbnail horizontal pixel count 

Ythumbnail (1 byte) Thumbnail vertical pixel count 

(RGB)n (3n bytes) Packed (24-bit) RGB values for 

the 

thumbnail pixels, n = XthumbnaiI * Ythumbnail 

[Optional JFIF extension APP0 marker segment(s) - see below] 

• 

• 

• 

186 
 

 

 

 

 

 

 

5 

10 

15 

20 

25 

30 

35 

40 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 X 'FF', SOFn, length,. frame parameters 

2 Number of components Nf = 1 or 3 

3 1st component C1 = 1 = Y component 

4 2nd component C2 = 2 = Cb component 

3rd component C3 = 3 = Cr component 

6 • 

7 • 

8 • 

9 X 'FF', EOI 

JFIF Extension: APP0 marker segment 

11 Immediately following the JFIF APP0 marker segment may be a JFIF extension APP0 marker. This JFIF 

12 extension APP0 marker segment may only be present for JFIF versions 1.02 and above. The syntax of 

13 the JFIF extension APP0 marker segment is: 

14 X 'FF', APP0,. Length, identifier, extension code, extension data 

length (2 bytes) Total APP0 field byte count, including 

16 the 

17 byte count value (2 bytes), but excluding 

18 the APP0 marker itself 

19 identifier (5 bytes) = X '4A', X ‘461

, X '58', X '58', X ‘00’ 

This zero terminated string ("JFXX") 

21 uniquely identifies this APP0 marker. This 

22 string shall have zero parity (bit 7 = 0). 

23 extension_code (1 byte) = Code which identifies the extension. In 

24 this version, the following extensions are 

defined: 

26 = X '10' Thumbnail coded using JPEG 

27 = X '11’ Thumbnail stored using 1 byte/pixel 

28 = X '13’ Thumbnail stored using 3 bytes/pixel 

29 extension_data (variable) = The specification of the remainder of the 

JFIF extension APP0 marker segment 

31 varies with the extension. See below for a 

32 specification of extension_data for each extension. 

33 JFIF Extension: Thumbnail coded using JPEG 

34 This extension supports thumbnails compressed using JPEG. The compressed thumbnail immediately 

follows the extension-code (X ‘I0') in the extension_data field and the length of the compressed data must 

36 be included in the JFIF extension APP0 marker length field. 

37 The syntax of the extension_data field conforms to the syntax for interchange format defined in Annex B 

38 of ISO DIS 10917-1. However, no "JFIF" or "JFXX" marker segments shall be present. As in the full 

39 resolution image of the JFIF file, the syntax of extension_data constrains parameters in the frame header 

as defined below: 

187 
 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 X 'FF', SOI 

2 •

3 •

4 X'FF'. SOFn, length, frame parameters 

Number of components Nf = 1 or 3 

6 1st component C1 = 1 = Y component 

7 2nd component C2 = 2 = Cb component 

8 3rd component C3 = 3 = Cr component 

9 •

•

11 X 'FF', EOI 

12 JFIF Extension: ThumbnaiI stored using one byte per pixel 

13 This extension supports thumbnails stored using one byte per pixel and a color palette in the 

14 extension_data field. The syntax of extension_data is: 

Xthumbnail (I byte) Thumbnail horizontal pixel count 

16 Ythumbnail (1 byte) Thumbnail vertical pixel count 

17 Palette (768 bytes) 24-bit RGB pixel values for the 

18 color 

19 palette. The RGB values define the colors 

represented by each value of an 8-bit 

21 binary encoding (0 - 255). 

22 (pixel)n (n bytes) 8-bit values for the thumbnail 

23 pixels 

24 n = Xthumbnail * Ythumbnall 

JFIF Extension: Thumbnail stored using three bytes per pixel 

26 This extension supports thumbnails stored using three bytes per pixel in the extension_data field. The 

27 syntax of extension_data is: 

28 Xthumbnail (1 byte) Thumbnail horizontal pixel count 

29 Ythumbnail (1 byte) Thumbnail vertical pixel count 

(RGB)n (3n bytes) Packed (24-bit) RGB values for 

31 the thumbnail 

32 pixels, n = Xthumbnail * Ythumbnail 

33 Useful tips 

34 • You can identify a JFIF file by looking for the following sequence: X'FF’, SOI, X'FF', APP0, <2 bytes 

to be skipped>, "JFIF", X'00'. 

36 • If you use APP0 elsewhere, be sure not to have the strings "JFIF” or “JFXX” right after the APP0 

37 marker. 

38 • If you do not want to include a thumbnail, just program Xthumbnail = Ythumbnail = 0. 

188 
 

1 

2 

3 

4 

5 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

• Be sure to check the version number in the special APP0 field. In general, if the major version 

number of the JFIF file matches that supported by the decoder, the file will be decodable. 

• If you only want to specify a pixel aspect ratio, put 0 for the units field in the special APP0 field. 

Xdensity and Ydensity can then be programmed for the desired aspect ratio. Xdensity = 1, Ydensity = 

1 will program a 1:1 aspect ratio. Xdensity and Ydensity should always be non-zero. 

189 
 

1 Annex E NCIC Codes for Scars, marks, tattoos, and other characteristics 

2 (normative) 

3 

4 This annex contains codes based on portions of the Ninth edition (December, 2000) of the NCIC Code 

5 Manual for describing Scars, Marks, Tattoos, and other characteristics (alphabetized by code). The 

6 following list is intended to standardize entry of data in the SMT Field. Care must be taken to enter 

7 spaces exactly as shown. However, as the NCIC Code Manual gets updated, the latest edition shall be 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

8 the governing document regarding valid SMT codes. 

9 Item/Location Code 

Arm, nonspecific, artificial ART ARM 

Breast, nonspecific, 

artificial 

ART BRST 

Breast implant, left and 

right 

ART BRSTS 

Ear, nonspecific, artificial ART EAR 

Artificial elbow joint ART ELB0W 

Eye, nonspecific, artificial ART EYE 

Foot, nonspecific, artificial ART F00T 

Hand, nonspecific, 

artificial 

ART HAND 

Artificial hip joint ART HIP 

Artificial knee joint ART KNEE 

Arm, left, artificial ART L ARM 

Breast implant, left ART L BRST 

Ear, left, artificial ART L EAR 

Left Elbow, artificial ART L ELB 

Eye, left, artificial ART L EYE 

Foot, left, artificial ART L FT 

Left Hip, artificial ART L HIP 

Hand, left, artificial ART L HND 

Left Knee, artificial ART L KNE 

Leg, left, artificial ART L LEG 

Left Shoulder, artificial ART L SHLD 

Artificial larynx ART LARYNX 

Leg, nonspecific, artificial ART LEG 

Arm, right, artificial ART R ARM 

Breast implant, right ART R BRST 

Ear, right, artificial ART R EAR 

Right Elbow, artificial ART R ELB 

Eye, right, artificial ART R EYE 

Foot, right, artificial ART R FT 

Right Hip, artificial ART R HIP 

Hand, right, artificial ART R HND 

Right Knee, artificial ART R KNE 

Leg, right, artificial ART R LEG 

Right Shoulder, artificial ART R SHLD 

Artificial shoulder joint ART SHLD 

Bald/Balding BALD 

Blind, both eyes BLIND 

Blind, one eye, 

nonspecific 

BLND EYE 

Blind, left eye BLND L EYE 

Blind, right eye BLND R EYE 

Brace, left and right arms BRA LR ARM 

Brace, left and right legs BRA LR LEG 

Brace, one arm, 

nonspecific 

BRAC ARM 

Brace, left arm BRAC L ARM 

Brace, left leg BRAC L LEG 

Brace, one leg, 

nonspecific 

BRAC LEG 

Brace, right arm BRAC R ARM 

Brace, right leg BRAC R LEG 

Brace, teeth BRAC TEETH 

Brace, back BRACE BACK 

Brace, neck BRACE NECK 

Cane CANE 

Cardiac pacemaker CARD PACEM 

Cataract, left eye CATA L EYE 

Cataract, right eye CATA R EYE 

Cataract, (nonspecified) CATARACT 

Cauliflower Ear CAUL EAR 

Cauliflower ear, left CAUL L EAR 

Cauliflower ear, right CAUL R EAR 

Cleft Lip CL LIP 

Cleft chin CLEFT CHIN 

Cleft palate CLEFT PAL 

Arm, nonspecific, crippled CRIP ARM 

Finger(s), nonspecific, 

crippled 

CRIP FGR 

190 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Foot, nonspecific, crippled CRIP F00T 

Hand, nonspecific, 

crippled 

CRIP HAND 

Crippled arm, left CRIP L ARM 

Crippled finger(s), left 

hand (includes 

webbed fingers) 

CRIP L FGR 

Crippled foot, left 

(includes clubfoot) 

CRIP L FT 

Crippled hand, left CRIP L HND 

Crippled leg, left CRIP L LEG 

Crippled toe(s), left 

(includes webbed 

toes) 

CRIP L T0E 

Leg, nonspecific, crippled CRIP LEG 

Crippled arm, right CRIP R ARM 

Crippled finger(s), right 

hand (includes 

webbed fingers) 

CRIP R FGR 

Crippled foot, right 

(includes clubfoot) 

CRIP R FT 

Crippled hand, right CRIP R HND 

Crippled leg, right CRIP R LEG 

Crippled toe(s), right 

(includes webbed 

toes) 

CRIP R T0E 

Toe(s), nonspecific, 

crippled 

CRIP T0E 

Crutches CRUTCHES 

Crosseyed CR0SSEYED 

Colostomy appliances C0L0ST APP 

Contact lenses C0N LENSES 

Alcohol DA ALC0H0L 

Amphetamines (includes 

stimulants, speed, 

etc.) 

DA AMPHETA 

Barbiturates DA BARBITU 

Cocaine (includes crack) DA C0CAINE 

Glue DA GLUE 

Hallucinogens DA HALLUCI 

Marijuana DA MARIJUA 

Narcotics (includes 

Heroin,Morphine, 

Dilaudid, Methadone, 

etc.) 

DA NARC0TI 

Paint (includes thinner) DA PAINT 

Ritalin DA RITALIN 

Rohypnol (Brand name 

for Flunitrazepam. 

Also referred to as 

"rophies", "roofies", 

"ruffies", and "roche". 

DA R0HYPNL 

Other drugs of abuse not 

listed above, identify 

in the miscellaneous 

(MIS) field 

DA 0THER 

Deaf, left and right ears DEAF 

Deaf, one ear 

(nonspecific) 

DEAF EAR 

Deaf, left ear DEAF L EAR 

Deaf-mute DEAF MUTE 

Deaf, right ear DEAF R EAR 

Denture, lower only DENT L0W 

Denture, upper only DENT UP 

Denture, upper and lower DENT UP L0 

Deviated septum DEV SEPTUM 

Cheek, nonspecific, 

dimple 

DIMP CHEEK 

Dimples, chin DIMP CHIN 

Face, dimple DIMP FACE 

Dimples, left cheek (face) DIMP L CHK 

Dimples, right cheek 

(face) 

DIMP R CHK 

Abdomen DISC ABD0M 

Ankle, nonspecific DISC ANKL 

Arm, nonspecific DISC ARM 

Back DISC BACK 

Breast, nonspecific DISC BRST 

Buttocks, nonspecific DISC BUTTK 

Calf, nonspecific, 

discolored 

DISC CALF 

Cheek (face), nonspecific DISC CHEEK 

Chest DISC CHEST 

Chin DISC CHIN 

Ear, nonspecific DISC EAR 

Elbow, nonspecific, 

discolored 

DISC ELB0W 

Eyebrow, nonspecific DISC EYE 

Forearm, nonspecific, 

discolored 

DISC F ARM 

Face, nonspecific DISC FACE 

Finger, nonspecific DISC FGR 

Forehead DISC FHD 

Foot, nonspecific DISC F00T 

Groin, nonspecific, 

discolored 

DISC GR0IN 

191 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Hand, nonspecific, 

discolored 

DISC HAND 

Head DISC HEAD 

Hip, nonspecific DISC HIP 

Knee, nonspecific DISC KNEE 

Ankle, left DISC L ANK 

Arm, left DISC L ARM 

Breast, left DISC L BRS 

Buttock, left DISC L BUT 

Left Calf, discolored DISC L CALF 

Cheek (face), left DISC L CHK 

Ear, left DISC L EAR 

Left Elbow, discolored DISC L ELB 

Eyebrow, left/left eye area DISC L EYE 

Finger(s), left hand DISC L FGR 

Foot, left DISC L FT 

Hip, left DISC L HIP 

Hand, left DISC L HND 

Leg, left DISC L LEG 

Lip, lower DISC L LIP 

Left Toe, discolored DISC L T0E 

Wrist, left DISC L WRS 

Leg, nonspecific DISC LEG 

Left Forearm, discolored DISC LF ARM 

Lip, nonspecific DISC LIP 

Knee, left DISC LKNEE 

Shoulder, left DISC LSHLD 

Thigh, left DISC LTHGH 

Neck DISC NECK 

Nose DISC N0SE 

Penis DISC PENIS 

Ankle, right DISC R ANK 

Arm, right DISC R ARM 

Breast, right DISC R BRS 

Buttock, right DISC R BUT 

Right Calf, discolored DISC R CALF 

Cheek (face), right DISC R CHK 

Ear, right DISC R EAR 

Right Elbow, discolored DISC R ELB 

Eyebrow, right/right eye 

area 

DISC R EYE 

Finger(s), right hand DISC R FGR 

Foot, right DISC R FT 

Hip, right DISC R HIP 

Hand, right DISC R HND 

Leg, right DISC R LEG 

Right Toe, discolored DISC R T0E 

Wrist, right DISC R WRS 

Right Forearm, discolored DISC RF ARM 

Knee, right DISC RKNEE 

Shoulder, right DISC RSHLD 

Thigh, right DISC RTHGH 

Shoulder, nonspecific DISC SHLD 

Thigh, nonspecific DISC THGH 

Toe(s), nonspecific, 

discolored 

DISC T0E 

Lip, upper DISC U LIP 

Upper Left Arm, 

discolored 

DISC UL ARM 

Upper Right Arm, 

discolored 

DISC UR ARM 

Wrist, nonspecific DISC WRIST 

Tubes in ears, left and 

right 

EAR TUBES 

Extra breast, nonspecific EXTR BRST 

Extra nipple, center EXTR C NIP 

Extra vertebrae, cervical EXTR C VRT 

Extra breast, center EXTR CBRST 

Finger(s), nonspecific, 

extra 

EXTR FGR 

Extra finger(s), left hand EXTR L FGR 

Extra nipple, left EXTR L NIP 

EXTRA TOOTH/TEETH 

(LOWER JAW) 

EXTR L TTH 

Extra toe(s), left EXTR L T0E 

Extra vertebrae, lumbar EXTR L VRT 

Extra breast, left EXTR LBRST 

Extra nipple, nonspecific EXTR NIP 

Extra finger(s), right hand EXTR R FGR 

Extra nipple, right EXTR R NIP 

Extra toe(s), right EXTR R T0E 

Extra breast, right EXTR RBRST 

Tooth/Teeth, nonspecific, 

extra 

EXTR TTH 

Toe(s), nonspecific, extra EXTR T0E 

EXTRA TOOTH/TEETH 

(UPPER JAW) 

EXTR U TTH 

Extra vertebrae, 

nonspecific 

EXTR VRT 

Ankle, nonspecific FRC ANKL 

Arm, nonspecific FRC ARM 

Back FRC BACK 

Clavicle, nonspecific FRC CLAVIC 

Elbow, nonspecific, 

fractured 

FRC ELB0W 

Finger(s), nonspecific FRC FGR 

Foot, nonspecific FRC F00T 

192 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Hand, nonspecific FRC HAND 

Hip, nonspecific, fractured FRC HIP 

Jaw, nonspecific FRC JAW 

Knee, nonspecific FRC KNEE 

Ankle, left FRC L ANKL 

Left Arm, fractured FRC L ARM 

Left Elbow, fractured FRC L ELB 

Finger(s), left FRC L FGR 

Foot, left FRC L F00T 

Hand, left FRC L HAND 

Left Hip, fractured FRC L HIP 

Knee, left FRC L KNEE 

Left Leg, fractured FRC L LEG 

Rib(s), left FRC L RIB 

Shoulder, left FRC L SHLD 

Toe(s), left foot FRC L T0E 

Wrist, left FRC L WRST 

Clavicle, left FRC LCLAVI 

Leg, nonspecific FRC LEG 

Arm, lower left FRC LL ARM 

Jaw, lower left FRC LL JAW 

Leg, lower left FRC LL LEG 

Pelvis bone, left FRC LPELVI 

Arm, lower right FRC LR ARM 

Jaw, lower left FRC LR JAW 

Leg, lower right FRC LR LEG 

Neck FRC NECK 

Nose FRC N0SE 

Pelvis FRC PELVIS 

Ankle, right FRC R ANKL 

Right Arm, fractured FRC R ARM 

Right Elbow, fractured FRC R ELB 

Finger(s), right FRC R FGR 

Foot, right FRC R F00T 

Hand, right FRC R HAND 

Right Hip, fractured FRC R HIP 

Knee, right FRC R KNEE 

Right Leg, fractured FRC R LEG 

Rib(s), right FRC R RIB 

Shoulder, right FRC R SHLD 

Toe(s), right foot FRC R T0E 

Wrist, right FRC R WRST 

Clavicle, right FRC RCLAVI 

Rib(s), nonspecific FRC RIBS 

Pelvis bone, right FRC RPELVI 

Shoulder, nonspecific FRC SHLD 

Skull FRC SKULL 

Spine FRC SPINE 

Sternum FRC STERN 

Toe(s), nonspecific FRC T0E 

Arm, upper left FRC UL ARM 

Jaw, upper left FRC UL JAW 

Leg, upper left FRC UL LEG 

Arm, upper right FRC UR ARM 

Jaw, upper right FRC UR JAW 

Leg, upper right FRC UR LEG 

Wrist, nonspecific FRC WRIST 

Freckles FRECKLES 

Glasses (prescription) GLASSES 

Glaucoma GLAUC0MA 

Gold tooth G0LD T00TH 

Hair implants HAIR IMPL 

Hearing Aid HEAR AID 

Ankle, nonspecific HFR ANKL 

Arm, nonspecific HFR ARM 

Back HFR BACK 

Clavicle, nonspecific HFR CLAVIC 

Elbow, nonspecific, 

healed fractured 

HFR ELB0W 

Finger(s), nonspecific HFR FGR 

Foot, nonspecific HFR F00T 

Hand, nonspecific HFR HAND 

Hip, nonspecific, healed 

fractured 

HFR HIP 

Jaw, nonspecific HFR JAW 

Knee, nonspecific HFR KNEE 

Ankle, left HFR L ANKL 

Left Arm, healed fractured HFR L ARM 

Left Elbow, healed 

fractured 

HFR L ELB 

Finger(s), left HFR L FGR 

Foot, left HFR L F00T 

Hand, left HFR L HAND 

Left Hip, healed fractured HFR L HIP 

Knee, left HFR L KNEE 

Left Leg, healed fractured HFR L LEG 

Rib(s), left HFR L RIB 

Shoulder, left HFR L SHLD 

Toe(s), left foot HFR L T0E 

Wrist, left HFR L WRST 

Clavicle, left HFR LCLAVI 

Leg, nonspecific HFR LEG 

Arm, lower left HFR LL ARM 

Jaw, lower left HFR LL JAW 

Leg, lower left HFR LL LEG 

193 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Pelvis bone, left HFR LPELVI 

Arm, lower right HFR LR ARM 

Jaw, lower left HFR LR JAW 

Leg, lower right HFR LR LEG 

Neck HFR NECK 

Nose HFR N0SE 

Pelvis HFR PELVIS 

Ankle, right HFR R ANKL 

Right Arm, healed 

fractured 

HFR R ARM 

Right Elbow, healed 

fractured 

HFR R ELB 

Finger(s), right HFR R FGR 

Foot, right HFR R F00T 

Hand, right HFR R HAND 

Right Hip, healed 

fractured 

HFR R HIP 

Knee, right HFR R KNEE 

Right Leg, healed 

fractured 

HFR R LEG 

Rib(s), right HFR R RIB 

Shoulder, right HFR R SHLD 

Toe(s), right foot HFR R T0E 

Wrist, right HFR R WRST 

Clavicle, right HFR RCLAVI 

Rib(s), nonspecific HFR RIBS 

Pelvis bone, right HFR RPELVI 

Shoulder, nonspecific HFR SHLD 

Skull HFR SKULL 

Spine HFR SPINE 

Sternum HFR STERN 

Toe(s), nonspecific HFR T0E 

Arm, upper left HFR UL ARM 

Jaw, upper left HFR UL JAW 

Leg, upper left HFR UL LEG 

Arm, upper right HFR UR ARM 

Jaw, upper right HFR UR JAW 

Leg, upper right HFR UR LEG 

Wrist, nonspecific HFR WRIST 

Humpbacked HUMPBACKED 

Penile implant IMPL PENIS 

Intramedullary rod INTRA R0D 

Intrauterine device IUD 

Acne MC ACNE 

Attention Deficit Disorder MC ADD 

Alcoholism MC ALC0H0L 

Allergies including asthma MC ALLERGY 

Alzheimer's Disease MC ALZHMRS 

Arthritis MC ARTHRTS 

Behavior Disorder 

(includes Autism, 

Depression, 

Schizophrenia, 

Suicidal Tendencies 

(past and present) 

MC BEHAVI0 

Hematological Diseases 

(disease of the blood 

- includes: anemia, 

hemophilia, 

leukemia, and sickle 

cell anemia 

MC BL00D 

Cancer MC CANCER 

Diabetic MC DIABTIC 

Drug Abuse MC DRUGAB 

Down's Syndrome MC D0WNSYN 

Eating Disorders 

(Includes Anorexia 

Nervosa and 

Bulimia) 

MC EATDIS 

Heart or circulatory 

diseases including: 

high blood pressure, 

heart failure, heart 

attack, hardening of 

the arteries, and 

circulation problems 

MC HEART 

Kidney Conditions or 

Diseases 

MC KIDNEY 

Liver Disease (Including 

cirrhosis and 

hepatitis) 

MC LIVER 

Nervous conditions 

including: seizures, 

stroke, senility, and 

mental retardation 

MC NERV0US 

Neurological Conditions 

or Diseases 

(includes Cerebral 

Palsy, Epilepsy, 

Multiple Sclerosis, 

Parkinson's Disease) 

MC NRLGCAL 

Paraplegic MC PARPLGC 

Pregnancy - Past MC PASTPRE 

Pulmonary (Lung) 

Diseases (includes 

Emphesyma, Cystic 

Fibrosis) 

MC PLMNARY 

Pregnancy - Present MC PREGNAN 

Quadriplegic MC QUADPLG 

194 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Skin Disorders (includes 

psoriasis and 

eczema) 

MC SKIN 

Tuberculosis MC TB 

Thyroid Conditions or 

Diseases 

MC THYR0ID 

Tourette's Syndrome MC T0URETE 

Other medical 

disorders/conditions 

not listed above, 

identify in the 

Miscellaneous (MIS) 

Field 

MC 0THER 

Adenoids MISS ADND 

Appendix MISS APPNX 

Arm, nonspecific, missing MISS ARM 

Breast, nonspecific, 

missing 

MISS BRST 

Breasts MISS BRSTS 

Missing Cervical 

Vertebra(e) 

MISS C VRT 

Ear, nonspecific, missing MISS EAR 

Eye, nonspecific, missing MISS EYE 

Finger(s), nonspecific, 

missing 

MISS FGR 

Finger Joint, nonspecific, 

missing 

MISS FJT 

Foot, nonspecific, missing MISS F00T 

Gallbladder MISS GALL 

Hand, nonspecific, 

missing 

MISS HAND 

Intestines MISS INTES 

Kidney, nonspecific, 

missing 

MISS KID 

Arm, left MISS L ARM 

Ear, left MISS L EAR 

Eye, left MISS L EYE 

Finger(s), left hand MISS L FGR 

Finger joint(s), left hand MISS L FJT 

Foot, left MISS L FT 

Hand, left MISS L HND 

Kidney, left MISS L KID 

Leg, left MISS L LEG 

Testis, left MISS L TES 

Toes(s), left foot MISS L T0E 

Missing Lumbar 

Vertebra(e) 

MISS L VRT 

Breast, left MISS LBRST 

Leg, nonspecific, missing MISS LEG 

Arm, lower left MISS LLARM 

Leg, lower left MISS LLLEG 

Lung, left MISS LLUNG 

Arm, lower right MISS LRARM 

Leg, lower right MISS LRLEG 

Larynx MISS LRYNX 

Lung, nonspecific, 

missing 

MISS LUNG 

Ovary, left MISS L0VAR 

Nose MISS N0SE 

Pancreas MISS PANCR 

Missing Penis MISS PENIS 

Prostate Gland MISS PR0ST 

Arm, right MISS R ARM 

Ear, right MISS R EAR 

Eye, right MISS R EYE 

Finger(s), right hand MISS R FGR 

Finger joint(s), right hand MISS R FJT 

Foot, right MISS R FT 

Hand, right MISS R HND 

Kidney, right MISS R KID 

Leg, right MISS R LEG 

Testis, right MISS R TES 

Toes(s), right foot MISS R T0E 

Breast, right MISS RBRST 

Lung, right MISS RLUNG 

Ovary, right MISS R0VAR 

Spleen MISS SPLEN 

Stomach MISS ST0MA 

Testical, nonspecific, 

missing 

MISS TES 

Thyroid MISS THYRD 

Toe(s), nonspecific, 

missing 

MISS T0E 

Tongue MISS T0NG 

Tonsils MISS T0NSL 

Uterus MISS UTRUS 

Missing 

Vertebra(e),nonspeci 

fic 

MISS VRT 

Ovaries MISS 0VARS 

Ovary, nonspecific, 

missing 

MISS 0VARY 

Mute (To be used if 

person is mute but 

not deaf.) 

MUTE 

Abdomen M0LE ABD0M 

Ankle, nonspecific M0LE ANKL 

195 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Arm, nonspecific, mole M0LE ARM 

Back M0LE BACK 

Breast, nonspecific M0LE BRST 

Buttocks, nonspecific M0LE BUTTK 

Calf, nonspecific, mole M0LE CALF 

Chest M0LE CHEST 

Chin M0LE CHIN 

Cheek (face), nonspecific M0LE CHK 

Ear, nonspecific M0LE EAR 

Elbow, nonspecific, mole M0LE ELB0W 

Eye, nonspecific, mole M0LE EYE 

Forearm, nonspecific, 

mole 

M0LE F ARM 

Face, mole M0LE FACE 

Finger, nonspecific M0LE FGR 

Forehead M0LE FHD 

Foot, nonspecific M0LE F00T 

Groin area M0LE GR0IN 

Hand M0LE HAND 

Head, nonspecific M0LE HEAD 

Hip, nonspecific M0LE HIP 

Knee, nonspecific M0LE KNEE 

Ankle, left M0LE L ANK 

Arm, left M0LE L ARM 

Buttock, left M0LE L BUT 

Left Calf, mole M0LE L CALF 

Cheek (face), left M0LE L CHK 

Ear, left M0LE L EAR 

Left Elbow, mole M0LE L ELB 

Eyebrow, left/left eye area M0LE L EYE 

Finger(s), left hand M0LE L FGR 

Foot, left M0LE L FT 

Hip, left M0LE L HIP 

Hand, left M0LE L HND 

Knee, left M0LE L KNE 

Leg, left M0LE L LEG 

Lip, lower M0LE L LIP 

Shoulder, left M0LE L SHD 

Thigh, left M0LE L THG 

Left Toe, mole M0LE L T0E 

Wrist, left M0LE L WRS 

Breast, left M0LE LBRST 

Leg, nonspecific M0LE LEG 

Left forearm, mole M0LE LF ARM 

Lip, nonspecific M0LE LIP 

Neck M0LE NECK 

Nose M0LE N0SE 

Penis M0LE PENIS 

Ankle, right M0LE R ANK 

Arm, right M0LE R ARM 

Buttock, right M0LE R BUT 

Right Calf, mole M0LE R CALF 

Cheek (face), right M0LE R CHK 

Ear, right M0LE R EAR 

Right Elbow, mole M0LE R ELB 

Eyebrow, right/right eye 

area 

M0LE R EYE 

Finger(s), right hand M0LE R FGR 

Foot, right M0LE R FT 

Hip, right M0LE R HIP 

Hand, right M0LE R HND 

Knee, right M0LE R KNE 

Leg, right M0LE R LEG 

Shoulder, right M0LE R SHD 

Thigh, right M0LE R THG 

Right Toe, mole M0LE R T0E 

Wrist, right M0LE R WRS 

Breast, right M0LE RBRST 

Right forearm, mole M0LE RF ARM 

Shoulder, nonspecific M0LE SHLD 

Thigh, nonspecific M0LE THGH 

Toe(s), nonspecific, mole M0LE T0E 

Lip, right M0LE U LIP 

Upper Left Arm, mole M0LE UL ARM 

Upper Right Arm, mole M0LE UR ARM 

Wrist, nonspecific, mole M0LE WRS 

Ankle, nonspecific, needle 

mark 

NM ANKL 

Arm, nonspecific, needle 

mark 

NM ARM 

Buttock, nonspecific, 

needle mark 

NM BUTTK 

Calf, nonspecific, needle 

mark 

NM CALF 

Elbow, nonspecific, 

needle mark 

NM ELB0W 

Finger(s), nonspecific, 

needle mark 

NM FGR 

Foot, nonspecific, needle 

mark 

NM F00T 

Groin, nonspecific, needle 

mark 

NM GR0IN 

Hand, nonspecific, needle 

mark 

NM HAND 

Hip, nonspecific, needle 

mark 

NM HIP 

196 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Knee, nonspecific, needle 

mark 

NM KNEE 

Left Ankle, needle mark NM L ANKL 

Arm, left NM L ARM 

Buttock, left NM L BUTTK 

Left Calf, needle mark NM L CALF 

Left Elbow, needle mark NM L ELB 

Finger(s), left hand NM L FGR 

Foot, left NM L F00T 

Left Hip, needle mark NM L HIP 

Hand, left NM L HND 

Left Knee, needle mark NM L KNE 

Leg, left NM L LEG 

Left Shoulder, needle 

mark 

NM L SHLD 

Thigh, left NM L THIGH 

Left Toe, needle mark NM L T0E 

Wrist, left NM L WRIST 

Leg, nonspecific, needle 

mark 

NM LEG 

Lower Left Arm, needle 

mark 

NM LL ARM 

Lower Right Arm, needle 

mark 

NM LR ARM 

Penis, needle mark NM PENIS 

Right Ankle, needle mark NM R ANKL 

Arm, right NM R ARM 

Buttock, right NM R BUTTK 

Right Calf, needle mark NM R CALF 

Right Elbow, needle mark NM R ELB 

Finger(s), right hand NM R FGR 

Foot, right NM R F00T 

Right Hip, needle mark NM R HIP 

Hand, right NM R HND 

Right Knee, needle mark NM R KNE 

Leg, right NM R LEG 

Right Shoulder, needle 

mark 

NM R SHLD 

Thigh, right NM R THIGH 

Right Toe, needle mark NM R T0E 

Wrist, right NM R WRIST 

Shoulder, nonspecific, 

needle mark 

NM SHLD 

Thigh, nonspecific, needle 

mark 

NM THIGH 

Toe(s), nonspecific, 

needle mark 

NM T0E 

Upper Left Arm, needle 

mark 

NM UL ARM 

Upper Right Arm, needle 

mark 

NM UR ARM 

Wrist, nonspecific, needle 

mark 

NM WRIST 

Pierced abdomen PRCD ABDMN 

Pierced back PRCD BACK 

Pierced ear, one 

nonspecific 

PRCD EAR 

Pierced ears PRCD EARS 

Pierced eyebrow, 

nonspecific 

PRCD EYE 

Pierced genitalia PRCD GNTLS 

Pierced left ear PRCD L EAR 

Pierced left eyebrow PRCD L EYE 

Pierced nipple, left PRCD L NIP 

Pierced lip, nonspecific PRCD LIP 

Pierced lip, lower PRCD LLIP 

Pierced nipple, 

nonspecific 

PRCD NIPPL 

Pierced nose PRCD N0SE 

Pierced right ear PRCD R EAR 

Pierced right eyebrow PRCD R EYE 

Pierced nipple, right PRCD R NIP 

Pierced tongue PRCD T0NGU 

Pierced lip, upper PRCD ULIP 

Jaw, nonspecific, 

protruding 

PR0T JAW 

Protruding lower jaw PR0T L JAW 

Protruding upper jaw PR0T U JAW 

Pockmarks P0CKMARKS 

Abdomen RTAT ABDM 

Ankle, nonspecific RTAT ANKL 

Arm, nonspecific RTAT ARM 

Back RTAT BACK 

Breast, nonspecific RTAT BRST 

Buttocks, nonspecific RTAT BUTTK 

Calf, nonspecific RTAT CALF 

Cheek (face), nonspecific RTAT CHEEK 

Chest RTAT CHEST 

Chin RTAT CHIN 

Ear, nonspecific RTAT EAR 

Elbow, nonspecific RTAT ELB0W 

Eye, nonspecific, remove 

tattoo 

RTAT EYE 

Face, nonspecific (Use 

the MIS field to 

further describe 

location) 

RTAT FACE 

Forearm, nonspecific RTAT FARM 

197 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Forehead RTAT FHD 

Full body RTAT FLB0D 

Finger, nonspecific RTAT FNGR 

Foot, nonspecific RTAT F00T 

Groin Area RTAT GR0IN 

Hand, nonspecific RTAT HAND 

Head, nonspecific (Use 

the MIS fieldo further 

describe location) 

RTAT HEAD 

Hip, nonspecific RTAT HIP 

Knee, nonspecific RTAT KNEE 

Arm, left RTAT L ARM 

Cheek (face), left RTAT L CHK 

Ear, left RTAT L EAR 

Elbow, left RTAT L ELB 

Left Eye, remove tattoo RTAT L EYE 

Finger(s), left hand RTAT L FGR 

Hip, left RTAT L HIP 

Hand, left RTAT L HND 

Leg, left RTAT L LEG 

Left Toe, remove tattoo RTAT L T0E 

Ankle, left RTAT LANKL 

Breast, left RTAT LBRST 

Buttocks, left RTAT LBUTK 

Calf, left RTAT LCALF 

Leg, nonspecific RTAT LEG 

Forearm, left RTAT LFARM 

Foot, left RTAT LF00T 

Lip, nonspecific RTAT LIP 

Knee, left RTAT LKNEE 

Shoulder, left RTAT LSHLD 

Thigh, left RTAT LTHGH 

Lip, lower RTAT LWLIP 

Wrist, left RTAT LWRS 

Neck RTAT NECK 

Nose RTAT N0SE 

Penis RTAT PENIS 

Arm, right (Use the MIS 

field to further 

describe location) 

RTAT R ARM 

Cheek (face), right RTAT R CHK 

Ear, right RTAT R EAR 

Elbow, right RTAT R ELB 

Right Eye, remove tattoo RTAT R EYE 

Finger(s), right hand RTAT R FGR 

Hip, right RTAT R HIP 

Hand, right RTAT R HND 

Leg, right (Use the MIS 

field tourther 

describe location) 

RTAT R LEG 

Right Toe, remove tattoo RTAT R T0E 

Angle, right RTAT RANKL 

Breast, right RTAT RBRST 

Buttocks, right RTAT RBUTK 

Calf, right RTAT RCALF 

Forearm, right RTAT RFARM 

Foot, right RTAT RF00T 

Knee, right RTAT RKNEE 

Shoulder, right RTAT RSHLD 

Thigh, right RTAT RTHGH 

Wrist, right RTAT RWRS 

Shoulder, nonspecific RTAT SHLD 

Thigh, nonspecific RTAT THGH 

Toe(s), nonspecific, 

remove tattoo 

RTAT T0E 

Arm, left upper RTAT ULARM 

Lip, upper RTAT UPLIP 

Arm, right upper RTAT URARM 

Wrist, nonspecific RTAT WRS 

Abdomen SC ABD0M 

Ankle, nonspecific SC ANKL 

Arm, nonspecific SC ARM 

Back SC BACK 

Breast, nonspecific SC BREAST 

Buttocks, nonspecific SC BUTTK 

Calf, nonspecific SC CALF 

Chest SC CHEST 

Chin SC CHIN 

Cheek, nonspecific SC CHK 

Ear, nonspecific SC EAR 

Elbow, nonspecific SC ELB0W 

Eyebrow, nonspecific SC EYE 

Forearm, nonspecific SC F ARM 

Face, nonspecific (use 

MIS field to further 

describe location) 

SC FACE 

Finger, nonspecific SC FGR 

Forehead SC FHD 

Foot, nonspecific SC F00T 

Groin area SC GR0IN 

Hand, nonspecific SC HAND 

Head, nonspecific (use 

MIS field to further 

describe location) 

SC HEAD 

Hip, nonspecific SC HIP 

198 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Knee, nonspecific SC KNEE 

Ankle, left SC L ANKL 

Arm, left, nonspecific SC L ARM 

Breast, left SC L BRST 

Buttocks, left SC L BUTTK 

Calf, left SC L CALF 

Cheek, left SC L CHK 

Ear, left SC L EAR 

Elbow, left SC L ELB 

Eyebrow, left/left eye area SC L EYE 

Finger(s), left hand SC L FGR 

Foot, left SC L FT 

Hip, left SC L HIP 

Hand, left SC L HND 

Knee, left SC L KNEE 

Leg, left SC L LEG 

Shoulder, left SC L SHLD 

Thigh, left SC L THGH 

Left Toe, scar SC L T0E 

Wrist, left SC L WRIST 

Leg, nonspecific SC LEG 

Forearm, left SC LF ARM 

Lip, nonspecific SC LIP 

Lip, lower SC L0W LIP 

Neck SC NECK 

Nose SC N0SE 

Penis SC PENIS 

Ankle, right SC R ANKL 

Arm, right, nonspecific SC R ARM 

Breast, right SC R BRST 

Buttocks, right SC R BUTTK 

Calf, right SC R CALF 

Cheek, right SC R CHK 

Ear, right SC R EAR 

Elbow, right SC R ELB 

Eyebrow, right/right eye 

area 

SC R EYE 

Finger(s), right hand SC R FGR 

Foot, right SC R FT 

Hip, right SC R HIP 

Hand, right SC R HND 

Knee, right SC R KNEE 

Leg, right SC R LEG 

Shoulder, right SC R SHLD 

Thigh, right SC R THGH 

Right Toe, scar SC R T0E 

Wrist, right SC R WRIST 

Forearm, right SC RF ARM 

Shoulder, nonspecific SC SHLD 

Thigh, nonspecific SC THGH 

Toe(s), nonspecific, scar SC T0E 

Arm, left upper SC UL ARM 

Lip, upper SC UP LIP 

Arm, right upper SC UR ARM 

Wrist, nonspecific SC WRIST 

Shorter left leg SHRT L LEG 

Leg, nonspecific, short SHRT LEG 

Shorter right leg SHRT R LEG 

Shunt, arterial vascular SHUNT ART 

Shunt, cerebral ventricule SHUNT CERB 

Skull plate SKL PLATE 

Silver tooth SLVR T00TH 

Staples STAPLES 

Stutters STUTTERS 

Abdomen TAT ABD0M 

Ankle, nonspecific TAT ANKL 

Arm, nonspecific TAT ARM 

Back TAT BACK 

Breast TAT BREAST 

Buttocks TAT BUTTK 

Calf, nonspecific TAT CALF 

Cheek (face), nonspecific TAT CHEEK 

Chest TAT CHEST 

Chin TAT CHIN 

Ear, nonspecific TAT EAR 

Elbow, nonspecific TAT ELB0W 

Eye, nonspecific, tattoo TAT EYE 

Face, nonspecific (use 

MIS field to further 

describe location) 

TAT FACE 

Forearm, nonspecific TAT FARM 

Forehead TAT FHD 

Full Body (Use only when 

the entire body -

arms, legs, chest, 

and back are 

covered with 

tattoos.) 

TAT FLB0DY 

Finger, nonspecific TAT FNGR 

Foot, nonspecific TAT F00T 

Groin area TAT GR0IN 

Hand, nonspecific TAT HAND 

Head, nonspecific (use 

MIS field to further 

describe location) 

TAT HEAD 

199 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Hip, nonspecific TAT HIP 

Knee, nonspecific TAT KNEE 

Ankle, left TAT L ANKL 

Arm, left TAT L ARM 

Breast, left TAT L BRST 

Buttock, left TAT L BUTK 

Calf, left TAT L CALF 

Cheek (face), left TAT L CHK 

Ear, left TAT L EAR 

Left Eye, tattoo TAT L EYE 

Finger(s), left hand TAT L FGR 

Foot, left TAT L F00T 

Hip, left TAT L HIP 

Hand, left TAT L HND 

Knee, left TAT L KNEE 

Leg, left, nonspecific TAT L LEG 

Shoulder, left TAT L SHLD 

Thigh, left TAT L THGH 

Left Toe, tattoo TAT L T0E 

Wrist, left TAT L WRS 

Leg, nonspecific TAT LEG 

Elbow, left TAT LELB0W 

Forearm, left TAT LF ARM 

Lip, nonspecific TAT LIP 

Lip, lower TAT LW LIP 

Neck TAT NECK 

Nose TAT N0SE 

Penis TAT PENIS 

Ankle, right TAT R ANKL 

Arm, right TAT R ARM 

Breast, right TAT R BRST 

Buttock, right TAT R BUTK 

Calf, right TAT R CALF 

Cheek (face), right TAT R CHK 

Ear, right TAT R EAR 

Right Eye, tattoo TAT R EYE 

Finger(s), right hand TAT R FGR 

Foot, right TAT R F00T 

Hip, right TAT R HIP 

Hand, right TAT R HND 

Knee, right TAT R KNEE 

Leg, right, nonspecific TAT R LEG 

Shoulder, right TAT R SHLD 

Thigh, right TAT R THGH 

Right Toe, tattoo TAT R T0E 

Wrist, right TAT R WRS 

Elbow, right TAT RELB0W 

Forearm, right TAT RF ARM 

Shoulder, nonspecific TAT SHLD 

Thigh, nonspecific TAT THGH 

Toe(s), nonspecific, tattoo TAT T0E 

Arm, left upper TAT UL ARM 

Lip, upper TAT UP LIP 

Arm, right upper TAT UR ARM 

Wrist, nonspecific TAT WRS 

Anticonvulsants (seizure 

medicines - includes: 

Dilantin Mysoline, 

Phenobarbital, etc.) 

TD AC0NVUL 

Antidepressants (moodlifters - (Mood lifters - 

includes: 

Amitriptylene, Elavil, 

Norpramine, Prozac, 

Triavil, Zoloft, etc.) 

TD ADEPRES 

Analgesics (pain relievers 

-includes: Darvon, 

Acetominophen, 

Aspirin, etc.) 

TD ANALGES 

Antibiotics TD ANTBTCS 

Anti-Inflammatory 

Medication 

TD ANTINFL 

Bronchial Dilators 

(Includes inhalers) 

TD BRNCHDL 

Cardiac (heart 

medications -

includes: Digitalis, 

Digoxin, etc.) 

TD CARDIAC 

Hypnotics (sleeping aides 

-includes: 

Barbiturates, Chloral 

Hydrate, 

Glutethemide, etc.) 

TD HYPN0TI 

Insulin TD INSULIN 

Ritalin TD RITALIN 

Tranquilizers (includes: 

Valium, Thorazine, 

Stellazine, etc.) 

TD TRANQUI 

Other therapeutic 

medications not 

listed above, identify 

in the MIS Field. 

TD 0THER 

200 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Transsexual 

(Miscellaneous field 

should indicate what 

the individual was at 

birth and what they 

are at the time the 

record is entered into 

NCIC.) 

TRANSSXL 

Transvestite TRANSVST 

Tube in left ear TUBE L EAR 

Tube in right ear TUBE R EAR 

Vascular prosthesis VASC PR0TH 

Wheelchair WHEELCHAIR 

Wire sutures WIRE SUTUR 

Orthopedic nail or pin 0RTH NAIL 

Orthopedic plate 0RTH PLATE 

Orthopedic screw 0RTH SCREW 

201 
1 Annex F Instance Document 

2 (informative) 3 4 This annex contains an example XML instance document file (“Instance_2007e.xml”) containing all logical record types and 

5 every data element. 

6 7 8 9 <?xml version="1.0" encoding="UTF-8"?> 

10 <itl:NISTBiometricInformationExchangePackage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 

11 xsi:schemaLocation="http://itl.nist.gov/biometric/1-2007 ITL-2007e-Package.xsd" 

12 xmlns:ansi-nist="http://niem.gov/niem/ansi-nist/2.0" 13 xmlns:itl="http://itl.nist.gov/biometric/1-2007" 14 xmlns:s="http://niem.gov/niem/structures/2.0" 

15 xmlns:nc="http://niem.gov/niem/niem-core/2.0" 

16 xmlns:xsd="http://www.w3.org/2001/XMLSchema"> 17 <!-- ========================================================================================

18 <!-- 19 <!-- ======================================= RECORD TYPE 01 =================================================

20 <itl:PackageInformationRecord>

21 <ansi-nist:RecordCategoryCode>01</ansi-nist:RecordCategoryCode> 22 <ansi-nist:Transaction> 23 <!-- ====================================================== fieldID="1.005" fieldMnemonic="DAT" =

24 <ansi-nist:TransactionDate> 25 <nc:Date>2007-07-06</nc:Date>26 </ansi-nist:TransactionDate> 27 <!-- ====================================================== fieldID="1.007" fieldMnemonic="DAI" =28 <ansi-nist:TransactionDestinationOrganization> 29 <nc:OrganizationIdentification> 

30 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 31 </nc:OrganizationIdentification> 32 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 

33 </ansi-nist:TransactionDestinationOrganization> 34 <!-- ====================================================== fieldID="1.008" fieldMnemonic="ORI" =

35 <ansi-nist:TransactionOriginatingOrganization> 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

202 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:OrganizationIdentification>

 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:TransactionOriginatingOrganization>  <!-- ====================================================== fieldID="1.014" fieldMnemonic="GMT" 

 <ansi-nist:TransactionUTCDate> 

 <nc:DateTime>2005-11-05T05:25:00Z</nc:DateTime>

 </ansi-nist:TransactionUTCDate>  <!-- ====================================================== fieldID="1.009" fieldMnemonic="TCN" =

 <ansi-nist:TransactionControlIdentification> 

 <nc:IdentificationID>56839</nc:IdentificationID> 

 </ansi-nist:TransactionControlIdentification> <!-- ====================================================== fieldID="1.010" fieldMnemonic="TCR" =

 <ansi-nist:TransactionControlReferenceIdentification>

 <nc:IdentificationID>29385</nc:IdentificationID> 

 </ansi-nist:TransactionControlReferenceIdentification> <!-- ====================================================== fieldID="1.013" fieldMnemonic="DOM" 

 <ansi-nist:TransactionDomain>

 <ansi-nist:DomainVersionNumberIdentification> 

 <nc:IdentificationID>7.02</nc:IdentificationID> 

 </ansi-nist:DomainVersionNumberIdentification> 

 <ansi-nist:OrganizationName>NORAM</ansi-nist:OrganizationName>

 </ansi-nist:TransactionDomain> <ansi-nist:TransactionImageResolutionDetails> 

 <!-- ====================================================== fieldID="1.011" fieldMnemonic="NSR <ansi-nist:NativeScanningResolutionValue>19.69</ansi-nist:NativeScanningResolutionValue>  <!-- ====================================================== fieldID="1.012" fieldMnemonic="NTR <ansi-nist:NominalTransmittingResolutionValue>19.69</ansi-nist:NominalTransmittingResolutionValue> 

 </ansi-nist:TransactionImageResolutionDetails> <!-- ====================================================== fieldID="1.002" fieldMnemonic="VER" =

 <ansi-nist:TransactionMajorVersionValue>04</ansi-nist:TransactionMajorVersionValue>  <ansi-nist:TransactionMinorVersionValue>00</ansi-nist:TransactionMinorVersionValue>  <!-- ====================================================== fieldID="1.006" fieldMnemonic="PRY" =

 <ansi-nist:TransactionPriorityValue>5</ansi-nist:TransactionPriorityValue>  <!-- ====================================================== fieldID="1.004" fieldMnemonic="TOT" =

 <ansi-nist:TransactionCategoryCode>CAR</ansi-nist:TransactionCategoryCode> 

203 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- ====================================================== fieldID="1.003" fieldMnemonic="CNT" =

 <ansi-nist:TransactionContentSummary> 

 <ansi-nist:ContentFirstRecordCategoryCode>1</ansi-nist:ContentFirstRecordCategoryCode> <ansi-nist:ContentRecordCount>21</ansi-nist:ContentRecordCount>  <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>00</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>02</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>01</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>03</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>02</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>04</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>03</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>05</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>04</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>06</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>05</nc:IdentificationID> 

204 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>07</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>06</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>06</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>07</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>09</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>08</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>08</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>09</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

205 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>09</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>09</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>10</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>11</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>12</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>13</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>15</ansi-nist:RecordCategoryCode> 

206 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>14</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>16</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>15</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>17</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary> <ansi-nist:ContentRecordSummary>

 <ansi-nist:ImageReferenceIdentification> 

 <nc:IdentificationID>16</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

 <ansi-nist:RecordCategoryCode>99</ansi-nist:RecordCategoryCode> 

 </ansi-nist:ContentRecordSummary>

 </ansi-nist:TransactionContentSummary>  <!-- ====================================================== fieldID="1.015" fieldMnemonic="DCS" 

 <ansi-nist:TransactionCharacterSetDirectory>

 <ansi-nist:CharacterSetCommonNameCode>ASCII 7-bit English</ansi-nist:CharacterSetCommonNameCode>  <ansi-nist:CharacterSetIndexCode>000</ansi-nist:CharacterSetIndexCode>  <ansi-nist:CharacterSetVersionIdentification> 

 <nc:IdentificationID>000</nc:IdentificationID> 

 </ansi-nist:CharacterSetVersionIdentification> 

 </ansi-nist:TransactionCharacterSetDirectory>

 </ansi-nist:Transaction>

 </itl:PackageInformationRecord>  <!-- ======================================================================================== <!-- 

RECORD TYPE 02 

 <!-- ======================================================================================== <itl:PackageDescriptiveTextRecord>

 <ansi-nist:RecordCategoryCode>02</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="2.002" fieldMnemonic="IDC" == -

207 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>00</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- ====================================================== fieldID="2.003 999" User-defined fields == 

 <itl:UserDefinedDescriptiveText>

 <itl:ExampleDomainDefinedDescriptiveText> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleDomainDefinedDescriptiveText>  <itl:ExampleOtherDescriptiveText>

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleOtherDescriptiveText>

 </itl:UserDefinedDescriptiveText>

 </itl:PackageDescriptiveTextRecord> <!-- ======================================================================================== <!-- 

RECORD TYPE 03 Low Resolution Grayscale Fingerprint Image 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>03</ansi-nist:RecordCategoryCode>  <!-- ====================================================================fieldMnemonic="IDC" = <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>01</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <ansi-nist:FingerprintImage>

 <!-- ====================================================================fieldMnemonic="DAT <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- ====================================================================fieldMnemonic="IS <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 

 </ansi-nist:ImageCaptureDetail>  <!-- ====================================================================fieldMnemonic="GCA <ansi-nist:ImageCompressionAlgorithmCode>0</ansi-nist:ImageCompressionAlgorithmCode>

 <!-- ====================================================================fieldMnemonic="HLL <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

 <!-- ====================================================================fieldMnemonic="VLL

208 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- ====================================================================fieldMnemonic="FGP <ansi-nist:FingerprintImagePosition> 

 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode> 

 <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

 </ansi-nist:FingerprintImagePosition>  <!-- ====================================================================fieldMnemonic="IMP <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureCate

 </ansi-nist:FingerprintImage>

 </itl:PackageImageRecord> 

 <!-- ====================================================================================== <!-- RECORD TYPE 04 High Resolution Grayscale Fingerprint Image 

<!-- ======================================================================================

 <itl:PackageImageRecord> 

 <ansi-nist:RecordCategoryCode>04</ansi-nist:RecordCategoryCode>  <!-- ====================================================================fieldMnemonic="IDC"  <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>02</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <ansi-nist:FingerprintImage> 

 <!-- ====================================================================fieldMnemonic="D <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 

 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object>

 <ansi-nist:ImageCaptureDetail>

 <!-- ====================================================================fieldMnemonic= <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 

 </ansi-nist:ImageCaptureDetail> <!-- ====================================================================fieldMnemonic="G <ansi-nist:ImageCompressionAlgorithmCode>1</ansi-nist:ImageCompressionAlgorithmCode> <!-- ====================================================================fieldMnemonic="H <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

209 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- ====================================================================fieldMnemonic="V <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- ====================================================================fieldMnemonic="F <ansi-nist:FingerprintImagePosition>

 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

 </ansi-nist:FingerprintImagePosition> <!-- ====================================================================fieldMnemonic="IM <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureC

 </ansi-nist:FingerprintImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 05 Low Resolution Binary Fingerprint Image 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>05</ansi-nist:RecordCategoryCode>  <!-- ====================================================================fieldMnemonic="IDC" = <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>03</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <ansi-nist:FingerprintImage>

 <!-- ====================================================================fieldMnemonic="DAT <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- ====================================================================fieldMnemonic="IS <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 

 </ansi-nist:ImageCaptureDetail>  <!-- ====================================================================fieldMnemonic="BCA <ansi-nist:ImageCompressionAlgorithmCode>1</ansi-nist:ImageCompressionAlgorithmCode> <!-- ====================================================================fieldMnemonic="HLL

210 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- ====================================================================fieldMnemonic="VLL <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- ====================================================================fieldMnemonic="FGP <ansi-nist:FingerprintImagePosition> 

 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode> 

 <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

 </ansi-nist:FingerprintImagePosition>  <!-- ====================================================================fieldMnemonic="IMP <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureCate

 </ansi-nist:FingerprintImage>

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 06 High Resolution Binary Fingerprint Image 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>06</ansi-nist:RecordCategoryCode>  <!-- ====================================================================fieldMnemonic="IDC" = <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>04</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <ansi-nist:FingerprintImage>

 <!-- ====================================================================fieldMnemonic="DAT <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- ====================================================================fieldMnemonic="IS <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 

 </ansi-nist:ImageCaptureDetail>  <!-- ====================================================================fieldMnemonic="BCA <ansi-nist:ImageCompressionAlgorithmCode>1</ansi-nist:ImageCompressionAlgorithmCode> 

211 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- ====================================================================fieldMnemonic="HLL <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- ====================================================================fieldMnemonic="VLL <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- ====================================================================fieldMnemonic="FGP <ansi-nist:FingerprintImagePosition> 

 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

 </ansi-nist:FingerprintImagePosition>  <!-- ====================================================================fieldMnemonic="IMP <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureCate

 </ansi-nist:FingerprintImage>

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!--

 RECORD TYPE 07 User-defined Image Record 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>07</ansi-nist:RecordCategoryCode>  <!-- ====================================================================fieldMnemonic="IDC" = <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>05</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <itl:ExampleRecordImage>

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleRecordImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!--

 RECORD TYPE 08 Signature Image Record (with scanned image) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 

212 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- ====================================================================fieldMnemonic="IDC" = <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>06</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <ansi-nist:SignatureImage> 

 <!-- ==========================================================Scanned Image Data ==========

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- ====================================================================fieldMnemonic="IS <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 

 </ansi-nist:ImageCaptureDetail>  <!-- ====================================================================fieldMnemonic="HLL <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- ====================================================================fieldMnemonic="VLL <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- ====================================================================fieldMnemonic="SRT <ansi-nist:SignatureRepresentationCode>1</ansi-nist:SignatureRepresentationCode> <!-- ====================================================================fieldMnemonic="SIG"  <ansi-nist:SignatureCategoryCode>0</ansi-nist:SignatureCategoryCode> 

 </ansi-nist:SignatureImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 08 Signature Image Record (with vector image)  <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode>  <!-- ====================================================================fieldMnemonic="IDC" = <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>06</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <ansi-nist:SignatureImage> 

 <ansi-nist:ImageCaptureDetail>

 <!-- ====================================================================fieldMnemonic="IS <ansi-nist:CaptureResolutionCode>0</ansi-nist:CaptureResolutionCode> 

213 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 </ansi-nist:ImageCaptureDetail>  <!-- ====================================================================fieldMnemonic="HLL <ansi-nist:ImageHorizontalLineLengthPixelQuantity>00</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- ====================================================================fieldMnemonic="VLL <ansi-nist:ImageVerticalLineLengthPixelQuantity>00</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- ==========================================================Vectored Image Data ========= <ansi-nist:SignatureImageVectorRepresentation> 

 <ansi-nist:SignatureImageVector>

 <ansi-nist:VectorPenPressureValue>254</ansi-nist:VectorPenPressureValue>  <ansi-nist:VectorPositionVerticalCoordinateValue>0</ansi-nist:VectorPositionVerticalCoordinateValue>  <ansi-nist:VectorPositionHorizontalCoordinateValue>0</ansi-nist:VectorPositionHorizontalCoordinateValue> 

 </ansi-nist:SignatureImageVector> <ansi-nist:SignatureImageVector>

 <ansi-nist:VectorPenPressureValue>1</ansi-nist:VectorPenPressureValue>  <ansi-nist:VectorPositionVerticalCoordinateValue>5</ansi-nist:VectorPositionVerticalCoordinateValue>  <ansi-nist:VectorPositionHorizontalCoordinateValue>5</ansi-nist:VectorPositionHorizontalCoordinateValue> 

 </ansi-nist:SignatureImageVector>

 </ansi-nist:SignatureImageVectorRepresentation>  <!-- ====================================================================fieldMnemonic="SRT <ansi-nist:SignatureRepresentationCode>2</ansi-nist:SignatureRepresentationCode> <!-- ====================================================================fieldMnemonic="SIG"  <ansi-nist:SignatureCategoryCode>0</ansi-nist:SignatureCategoryCode> 

 </ansi-nist:SignatureImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- 

RECORD TYPE 09 

 Minutiae Data Record 

 <!-- ======================================================================================== <itl:PackageMinutiaeRecord>

 <ansi-nist:RecordCategoryCode>09</ansi-nist:RecordCategoryCode> 

 <!-- ======================================================== fieldID="9.002" fieldMnemonic="IDC" =

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>07</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- ======================================================== fieldID="9.003" fieldMnemonic="IMP" =

 <ansi-nist:MinutiaeImpressionCaptureCategoryCode>4</ansi-nist:MinutiaeImpressionCaptureCategoryCode>  <!-- ======================================================== fieldID="9.004" fieldMnemonic="FMT" 

214 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:MinutiaeFormatNISTStandardIndicator>true</ansi-nist:MinutiaeFormatNISTStandardIndicator>  <itl:Minutiae>

 <itl:MinutiaeNISTStandard> 

 <!-- ======================================================== fieldID="9.012" fieldMnemonic="M <itl:MinutiaDetail>

 <ansi-nist:PositionHorizontalCoordinateValue>0486</ansi-nist:PositionHorizontalCoordinateValue>  <ansi-nist:PositionVerticalCoordinateValue>2839</ansi-nist:PositionVerticalCoordinateValue>  <ansi-nist:MinutiaIdentification> 

 <nc:IdentificationID>1</nc:IdentificationID> 

 </ansi-nist:MinutiaIdentification>  <ansi-nist:PositionThetaAngleMeasure>048</ansi-nist:PositionThetaAngleMeasure>  <ansi-nist:MinutiaQualityValue>1</ansi-nist:MinutiaQualityValue> 

 <ansi-nist:MinutiaCategoryCode>B</ansi-nist:MinutiaCategoryCode>  <ansi-nist:MinutiaRidgeCount> 

<ansi-nist:RidgeCountReferenceIdentification>

 <nc:IdentificationID>2</nc:IdentificationID> 

 </ansi-nist:RidgeCountReferenceIdentification> <ansi-nist:RidgeCountValue>6</ansi-nist:RidgeCountValue> 

 </ansi-nist:MinutiaRidgeCount> <ansi-nist:MinutiaRidgeCount> 

<ansi-nist:RidgeCountReferenceIdentification>

 <nc:IdentificationID>8</nc:IdentificationID> 

 </ansi-nist:RidgeCountReferenceIdentification> <ansi-nist:RidgeCountValue>3</ansi-nist:RidgeCountValue> 

 </ansi-nist:MinutiaRidgeCount>

 </itl:MinutiaDetail> <itl:MinutiaDetail>

 <ansi-nist:PositionHorizontalCoordinateValue>4859</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>0473</ansi-nist:PositionVerticalCoordinateValue>  <ansi-nist:MinutiaIdentification> 

 <nc:IdentificationID>1</nc:IdentificationID> 

 </ansi-nist:MinutiaIdentification>  <ansi-nist:PositionThetaAngleMeasure>256</ansi-nist:PositionThetaAngleMeasure>  <ansi-nist:MinutiaQualityValue>63</ansi-nist:MinutiaQualityValue>  <ansi-nist:MinutiaCategoryCode>A</ansi-nist:MinutiaCategoryCode>  <ansi-nist:MinutiaRidgeCount> 

<ansi-nist:RidgeCountReferenceIdentification> 

215 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:IdentificationID>14</nc:IdentificationID> 

 </ansi-nist:RidgeCountReferenceIdentification> <ansi-nist:RidgeCountValue>4</ansi-nist:RidgeCountValue> 

 </ansi-nist:MinutiaRidgeCount>

 </itl:MinutiaDetail> <!-- ======================================================== fieldID="9.010" fieldMnemonic="M <ansi-nist:MinutiaeQuantity>2</ansi-nist:MinutiaeQuantity>  <!-- ======================================================== fieldID="9.005" fieldMnemonic="O <ansi-nist:MinutiaeReadingSystem> 

 <ansi-nist:ReadingSystemCodingMethodCode>E</ansi-nist:ReadingSystemCodingMethodCode> 

 <ansi-nist:ReadingSystemName>Universal Latent Workstation</ansi-nist:ReadingSystemName>  <ansi-nist:ReadingSystemSubsystemIdentification>

 <nc:IdentificationID>AA</nc:IdentificationID> 

 </ansi-nist:ReadingSystemSubsystemIdentification>

 </ansi-nist:MinutiaeReadingSystem>  <!-- ======================================================== fieldID="9.011" fieldMnemonic="R <ansi-nist:MinutiaeRidgeCountIndicator>true</ansi-nist:MinutiaeRidgeCountIndicator> 

 </itl:MinutiaeNISTStandard>  <!-- ======================================================== fieldID="9.008" fieldMnemonic="CRP

 <ansi-nist:MinutiaeFingerCorePosition>

 <ansi-nist:PositionHorizontalCoordinateValue>0035</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>0045</ansi-nist:PositionVerticalCoordinateValue> 

 </ansi-nist:MinutiaeFingerCorePosition> <ansi-nist:MinutiaeFingerCorePosition>

 <ansi-nist:PositionHorizontalCoordinateValue>0038</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>0048</ansi-nist:PositionVerticalCoordinateValue> 

 </ansi-nist:MinutiaeFingerCorePosition> <!-- ======================================================== fieldID="9.009" fieldMnemonic="DLT <ansi-nist:MinutiaeFingerDeltaPosition>

 <ansi-nist:PositionHorizontalCoordinateValue>0158</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>1948</ansi-nist:PositionVerticalCoordinateValue> 

 </ansi-nist:MinutiaeFingerDeltaPosition> <!-- ======================================================== fieldID="9.007" fieldMnemonic="FPC <itl:MinutiaeFingerPatternDetail>

 <itl:FingerPatternCodeSourceCode>T</itl:FingerPatternCodeSourceCode>  <ansi-nist:FingerPatternCode>PW</ansi-nist:FingerPatternCode> 

 </itl:MinutiaeFingerPatternDetail> 

216 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- ======================================================== fieldID="9.006" fieldMnemonic="FGP

 <ansi-nist:MinutiaeFingerPositionCode>5</ansi-nist:MinutiaeFingerPositionCode>  <ansi-nist:MinutiaeFingerPositionCode>6</ansi-nist:MinutiaeFingerPositionCode>  <ansi-nist:MinutiaePalmPositionCode>22</ansi-nist:MinutiaePalmPositionCode>

 </itl:Minutiae>

 </itl:PackageMinutiaeRecord> <!-- ======================================================================================== <!-- RECORD TYPE 10 Facial Image Record 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="10.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>08</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="10.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields> <itl:FaceImage> <!-- =====================================================fieldID="10.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="10.005" fieldMnemonic="PHD <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="10.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>1200</ansi-nist:CaptureHorizontalPixelDensityValue> 

 <!-- =====================================================fieldID="10.004" fieldMnemonic="SRC

 <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification> 

217 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="10.017" fieldMnemonic="SVP <ansi-nist:CaptureVerticalPixelDensityValue>1200</ansi-nist:CaptureVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="10.030" fieldMnemonic="DMM <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="10.012" fieldMnemonic="CSP" =

 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> <!-- =====================================================fieldID="10.011" fieldMnemonic="CGA" = <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="10.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="10.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="10.024" fieldMnemonic="SQS" = <ansi-nist:ImageQuality>

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue>  <ansi-nist:QualityMeasureVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityMeasureVendorIdentification> 

 </ansi-nist:ImageQuality> <!-- =====================================================fieldID="10.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="10.003" fieldMnemonic="IMT" == 

 <ansi-nist:ImageCategoryCode>FACE</ansi-nist:ImageCategoryCode>  <!-- =====================================================fieldID="10.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity>  <!-- =====================================================fieldID="10.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="10.025" fieldMnemonic="SPA" =

 <ansi-nist:FaceImage3DPoseAngle> 

 <ansi-nist:PosePitchAngleMeasure>45</ansi-nist:PosePitchAngleMeasure> 

 <ansi-nist:PosePitchUncertaintyValue>35</ansi-nist:PosePitchUncertaintyValue> 

218 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:PoseRollAngleMeasure>0</ansi-nist:PoseRollAngleMeasure>  <ansi-nist:PoseRollUncertaintyValue>90</ansi-nist:PoseRollUncertaintyValue>  <ansi-nist:PoseYawAngleMeasure>0</ansi-nist:PoseYawAngleMeasure>  <ansi-nist:PoseYawUncertaintyValue>0</ansi-nist:PoseYawUncertaintyValue> 

 </ansi-nist:FaceImage3DPoseAngle>  <!-- =====================================================fieldID="10.013" fieldMnemonic="SAP" =

 <ansi-nist:FaceImageAcquisitionProfileCode>20</ansi-nist:FaceImageAcquisitionProfileCode>  <!-- =====================================================fieldID="10.022" fieldMnemonic="PXS" =

 <ansi-nist:FaceImageAttribute>

 <ansi-nist:FaceImageAttributeCode>GLASSES</ansi-nist:FaceImageAttributeCode> 

 </ansi-nist:FaceImageAttribute> <ansi-nist:FaceImageAttribute>

 <ansi-nist:FaceImageAttributeCode>OTHER</ansi-nist:FaceImageAttributeCode> <ansi-nist:FaceImageAttributeText>SKI MASK</ansi-nist:FaceImageAttributeText> 

 </ansi-nist:FaceImageAttribute> <ansi-nist:FaceImageAttribute>

 <ansi-nist:FaceImageAttributeCode>PHYSICAL</ansi-nist:FaceImageAttributeCode>  <ansi-nist:FaceImageAttributeText>ART EYE</ansi-nist:FaceImageAttributeText> 

 </ansi-nist:FaceImageAttribute> <!-- =====================================================fieldID="10.026" fieldMnemonic="SXS" =

 <ansi-nist:FaceImageDescriptionCode>MOUTH OPEN</ansi-nist:FaceImageDescriptionCode> <ansi-nist:FaceImageDescriptionCode>TEETH VISIBLE</ansi-nist:FaceImageDescriptionCode> 

 <ansi-nist:FaceImageDescriptionCode>NO EAR</ansi-nist:FaceImageDescriptionCode>  <!-- =====================================================fieldID="10.027" fieldMnemonic="SEC" =

 <ansi-nist:FaceImageEyeColorAttributeCode>HAZ</ansi-nist:FaceImageEyeColorAttributeCode>  <!-- =====================================================fieldID="10.029" fieldMnemonic="SFP" =

 <ansi-nist:FaceImageFeaturePoint> 

 <ansi-nist:FeaturePointHorizontalCoordinateValue>258</ansi-nist:FeaturePointHorizontalCoordinateValue>  <ansi-nist:FeaturePointIdentification>

 <nc:IdentificationID>11.5</nc:IdentificationID> 

 </ansi-nist:FeaturePointIdentification> <ansi-nist:FeaturePointCategoryCode>1</ansi-nist:FeaturePointCategoryCode>  <ansi-nist:FeaturePointVerticalCoordinateValue>55</ansi-nist:FeaturePointVerticalCoordinateValue> 

 </ansi-nist:FaceImageFeaturePoint>  <ansi-nist:FaceImageFeaturePoint> 

 <ansi-nist:FeaturePointHorizontalCoordinateValue>256</ansi-nist:FeaturePointHorizontalCoordinateValue>  <ansi-nist:FeaturePointIdentification> 

219 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:IdentificationID>2.1</nc:IdentificationID> 

 </ansi-nist:FeaturePointIdentification> <ansi-nist:FeaturePointCategoryCode>1</ansi-nist:FeaturePointCategoryCode>  <ansi-nist:FeaturePointVerticalCoordinateValue>212</ansi-nist:FeaturePointVerticalCoordinateValue>

 </ansi-nist:FaceImageFeaturePoint>  <!-- =====================================================fieldID="10.028" fieldMnemonic="SHC" =

 <ansi-nist:FaceImageHairColorAttributeCode>BAL</ansi-nist:FaceImageHairColorAttributeCode>  <ansi-nist:FaceImageHairColorAttributeCode>GRN</ansi-nist:FaceImageHairColorAttributeCode> 

 <!-- =====================================================fieldID="10.021" fieldMnemonic="POA" =

 <ansi-nist:FaceImagePoseOffsetAngleMeasure>45</ansi-nist:FaceImagePoseOffsetAngleMeasure>  <!-- =====================================================fieldID="10.020" fieldMnemonic="POS" = <ansi-nist:FaceImageSubjectPoseCode>A</ansi-nist:FaceImageSubjectPoseCode>  <!-- =====================================================fieldID="10.023" fieldMnemonic="PAS" = <itl:FaceImageAcquisitionSource>

 <ansi-nist:CaptureSourceCode>VENDOR</ansi-nist:CaptureSourceCode>  <itl:CaptureSourceDescriptionText>CELL PHONE</itl:CaptureSourceDescriptionText> 

 </itl:FaceImageAcquisitionSource>

 </itl:FaceImage>

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!--

 RECORD TYPE 10 SMT Image Record 

<!-- ========================================================================================

 <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="10.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>08</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="10.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <ansi-nist:PhysicalFeatureImage> 

 <!-- =====================================================fieldID="10.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 

220 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="10.005" fieldMnemonic="PHD <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="10.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue>  <!-- =====================================================fieldID="10.004" fieldMnemonic="SRC <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="10.023" fieldMnemonic="PAS

 <ansi-nist:CaptureSourceCode>DIGITAL CAMERA</ansi-nist:CaptureSourceCode>

 <!-- =====================================================fieldID="10.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> <!-- =====================================================fieldID="10.030" fieldMnemonic="DMM <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="10.012" fieldMnemonic="CSP" =

 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> <!-- =====================================================fieldID="10.011" fieldMnemonic="CGA" = <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="10.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="10.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="10.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="10.003" fieldMnemonic="IMT" ==  <ansi-nist:ImageCategoryCode>TATTOO</ansi-nist:ImageCategoryCode>  <!-- =====================================================fieldID="10.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity>  <!-- =====================================================fieldID="10.010" fieldMnemonic="VPS" =

221 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="10.042" fieldMnemonic="SMD" =

 <ansi-nist:PhysicalFeatureDescriptionDetail> 

<!-- =Req'd to be associated with 10.042=====fieldID="10.043" fieldMnemonic="COL" == --> <ansi-nist:PhysicalFeatureColorDetail>

 <ansi-nist:PhysicalFeaturePrimaryColorCode>ORANGE</ansi-nist:PhysicalFeaturePrimaryColorCode>  <ansi-nist:PhysicalFeatureSecondaryColorCode>BLACK</ansi-nist:PhysicalFeatureSecondaryColorCode>

 <ansi-nist:PhysicalFeatureSecondaryColorCode>RED</ansi-nist:PhysicalFeatureSecondaryColorCode> 

 </ansi-nist:PhysicalFeatureColorDetail> <!-- =============================SubFields for "10.042" fieldMnemonic="SMD" == --> 

 <ansi-nist:PhysicalFeatureCategoryCode>TATTOO</ansi-nist:PhysicalFeatureCategoryCode>  <ansi-nist:PhysicalFeatureClassCode>ANIMAL</ansi-nist:PhysicalFeatureClassCode>  <ansi-nist:PhysicalFeatureDescriptionText>Golden retriever with an overbite</ansi-nist:PhysicalFeatureDescripti

 <ansi-nist:PhysicalFeatureSubClassCode>DOG</ansi-nist:PhysicalFeatureSubClassCode> 

 </ansi-nist:PhysicalFeatureDescriptionDetail>  <ansi-nist:PhysicalFeatureDescriptionDetail> 

 <ansi-nist:PhysicalFeatureColorDetail>

 <ansi-nist:PhysicalFeaturePrimaryColorCode>YELLOW</ansi-nist:PhysicalFeaturePrimaryColorCode>  <ansi-nist:PhysicalFeatureSecondaryColorCode>MULTI</ansi-nist:PhysicalFeatureSecondaryColorCode>

 </ansi-nist:PhysicalFeatureColorDetail> <ansi-nist:PhysicalFeatureCategoryCode>TATTOO</ansi-nist:PhysicalFeatureCategoryCode>  <ansi-nist:PhysicalFeatureClassCode>HUMAN</ansi-nist:PhysicalFeatureClassCode>  <ansi-nist:PhysicalFeatureDescriptionText>Fist</ansi-nist:PhysicalFeatureDescriptionText>  <ansi-nist:PhysicalFeatureSubClassCode>MBPART</ansi-nist:PhysicalFeatureSubClassCode>

 </ansi-nist:PhysicalFeatureDescriptionDetail>  <!-- =====================================================fieldID="10.040" fieldMnemonic="SMT" =

 <ansi-nist:PhysicalFeatureNCICCode>TAT L TOE</ansi-nist:PhysicalFeatureNCICCode>  <ansi-nist:PhysicalFeatureNCICCode>TAT FARM</ansi-nist:PhysicalFeatureNCICCode>  <!-- =====================================================fieldID="10.041" fieldMnemonic="SMS" = <ansi-nist:PhysicalFeatureSize>

 <ansi-nist:PhysicalFeatureHeightMeasure>112</ansi-nist:PhysicalFeatureHeightMeasure> <ansi-nist:PhysicalFeatureWidthMeasure>15</ansi-nist:PhysicalFeatureWidthMeasure> 

 </ansi-nist:PhysicalFeatureSize>

 </ansi-nist:PhysicalFeatureImage> 

 </itl:PackageImageRecord>  <!-- ========================================================================================

222 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X  <!-- RECORD TYPE 13 Variable-Resolution Latentprint Image (Single finger example) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

 <!-- ====================================================== fieldID="13.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>09</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="13.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:FingerprintImage>

 <!-- =====================================================fieldID="13.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="13.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="13.005" fieldMnemonic="LCD

 <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="13.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

 <!-- =====================================================fieldID="13.004" fieldMnemonic="SRC

 <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="13.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="13.020" fieldMnemonic="COM" =

223 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="13.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="13.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="13.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="13.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="13.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="13.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="13.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4</ansi-nist:FingerprintImageImpressionCaptureCate

 <!-- =====================================================fieldID="13.013" fieldMnemonic="FGP" =

 <ansi-nist:FingerPositionCode>4</ansi-nist:FingerPositionCode>  <ansi-nist:FingerPositionCode>5</ansi-nist:FingerPositionCode> 

 <!-- =====================================================fieldID="13.024" fieldMnemonic="LQM" =

 <itl:FingerprintImageQuality> 

 <ansi-nist:FingerPositionCode>4</ansi-nist:FingerPositionCode>  <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:FingerprintImageQuality> 

 </itl:FingerprintImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 13 Variable-Resolution Latentprint Image (Palm Latent Example) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

224 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- ====================================================== fieldID="13.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>09</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="13.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:PalmprintImage>

 <!-- =====================================================fieldID="13.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="13.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="13.005" fieldMnemonic="LCD <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="13.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

 <!-- =====================================================fieldID="13.004" fieldMnemonic="SRC <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="13.017" fieldMnemonic="SVP <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="13.020" fieldMnemonic="COM" =

 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="13.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText>

 <!-- =====================================================fieldID="13.006" fieldMnemonic="HLL" =

225 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="13.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="13.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="13.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="13.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="13.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4</ansi-nist:FingerprintImageImpressionCaptureCate

 <!-- =====================================================fieldID="13.013" fieldMnemonic="FGP" = <ansi-nist:PalmPositionCode>29</ansi-nist:PalmPositionCode>  <ansi-nist:PalmPositionCode>23</ansi-nist:PalmPositionCode>  <!-- =====================================================fieldID="13.024" fieldMnemonic="LQM" = <itl:PalmprintImageQuality>

 <ansi-nist:PalmPositionCode>29</ansi-nist:PalmPositionCode>

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:PalmprintImageQuality>

 </itl:PalmprintImage>

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 13 Variable-Resolution Latentprint Image (Major Case example) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="13.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>09</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> 

226 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- =================================================== fieldID="13.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:FingerprintImage>

 <!-- =====================================================fieldID="13.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 

 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="13.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="13.005" fieldMnemonic="LCD

 <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="13.016" fieldMnemonic="SHP <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

 <!-- =====================================================fieldID="13.004" fieldMnemonic="SRC

 <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="13.017" fieldMnemonic="SVP <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="13.020" fieldMnemonic="COM" =

 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="13.011" fieldMnemonic="CGA" = <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText>

 <!-- =====================================================fieldID="13.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="13.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="13.008" fieldMnemonic="SLC" =

227 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="13.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="13.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="13.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4</ansi-nist:FingerprintImageImpressionCaptureCate

 <!-- =====================================================fieldID="13.013" fieldMnemonic="FGP" = <ansi-nist:FingerPositionCode>19</ansi-nist:FingerPositionCode>  <ansi-nist:FingerprintImageMajorCasePrint> 

 <!-- =====================================================fieldID="13.014" fieldMnemonic="SPD <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:MajorCasePrintCode>EJI</ansi-nist:MajorCasePrintCode>  <!-- =====================================================fieldID="13.015" fieldMnemonic="PPC <ansi-nist:MajorCasePrintSegmentOffset> 

 <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 

 <ansi-nist:SegmentLocationCode>DST</ansi-nist:SegmentLocationCode>  <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode> 

 <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

 <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue> 

 <ansi-nist:SegmentTopVerticalCoordinateValue>55</ansi-nist:SegmentTopVerticalCoordinateValue> 

 </ansi-nist:MajorCasePrintSegmentOffset>  <ansi-nist:MajorCasePrintSegmentOffset> 

 <ansi-nist:SegmentBottomVerticalCoordinateValue>126</ansi-nist:SegmentBottomVerticalCoordinateValue> 

 <ansi-nist:SegmentLocationCode>MED</ansi-nist:SegmentLocationCode>  <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode>  <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

 <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue> 

 <ansi-nist:SegmentTopVerticalCoordinateValue>92</ansi-nist:SegmentTopVerticalCoordinateValue> 

 </ansi-nist:MajorCasePrintSegmentOffset> 

 </ansi-nist:FingerprintImageMajorCasePrint>  <!-- =====================================================fieldID="13.024" fieldMnemonic="LQM" =

 <itl:FingerprintImageQuality> 

 <ansi-nist:FingerPositionCode>19</ansi-nist:FingerPositionCode>  <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification> 

228 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:FingerprintImageQuality> 

 </itl:FingerprintImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!--

 RECORD TYPE 14 Variable Resolution Fingerprint Image (Single Finger) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

 <!-- ====================================================== fieldID="14.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>10</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="14.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:FingerprintImage>

 <!-- =====================================================fieldID="14.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="14.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="14.005" fieldMnemonic="FCD

 <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="14.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue>  <!-- =====================================================fieldID="14.004" fieldMnemonic="SRC

 <ansi-nist:CaptureOrganization> 

229 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="14.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> <!-- =====================================================fieldID="14.030" fieldMnemonic="DMM <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="14.020" fieldMnemonic="COM" = <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="14.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="14.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="14.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="14.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="14.007" fieldMnemonic="VLL" ==  <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="14.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="14.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1</ansi-nist:FingerprintImageImpressionCaptureCate

 <!-- =====================================================fieldID="14.013" fieldMnemonic="FGP" =

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

 <!-- =====================================================fieldID="14.022" fieldMnemonic="NQM" =

 <ansi-nist:FingerprintImageNISTQuality> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure>

 </ansi-nist:FingerprintImageNISTQuality>  <!-- =====================================================fieldID="14.024" fieldMnemonic="FQM" =

 <itl:FingerprintImageQuality> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

 <ansi-nist:QualityAlgorithmProductIdentification> 

230 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:FingerprintImageQuality> 

 </itl:FingerprintImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!--

 RECORD TYPE 14 Variable Resolution Fingerprint Image (Slap Print Set) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="14.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>11</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="14.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:FingerprintImage>

 <!-- =====================================================fieldID="14.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 

 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="14.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="14.005" fieldMnemonic="FCD

 <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="14.016" fieldMnemonic="SHP <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

231 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- =====================================================fieldID="14.004" fieldMnemonic="SRC <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="14.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> <!-- =====================================================fieldID="14.030" fieldMnemonic="DMM <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="14.020" fieldMnemonic="COM" = <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="14.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="14.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="14.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="14.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="14.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="14.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="14.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1</ansi-nist:FingerprintImageImpressionCaptureCate

 <!-- =====================================================fieldID="14.013" fieldMnemonic="FGP" = <ansi-nist:FingerPositionCode>14</ansi-nist:FingerPositionCode>  <!-- =====================================================fieldID="14.018" fieldMnemonic="AMP" = <itl:FingerprintImageFingerMissing> 

 <ansi-nist:FingerPositionCode>10</ansi-nist:FingerPositionCode>  <itl:FingerMissingCode>XX</itl:FingerMissingCode> 

 </itl:FingerprintImageFingerMissing>  <itl:FingerprintImageFingerMissing> 

 <ansi-nist:FingerPositionCode>9</ansi-nist:FingerPositionCode> 

232 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <itl:FingerMissingCode>XX</itl:FingerMissingCode> 

 </itl:FingerprintImageFingerMissing>  <!-- =====================================================fieldID="14.021" fieldMnemonic="SEG" = <itl:FingerprintImageSegmentPositionSquare>

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue>  <ansi-nist:SegmentLeftHorizontalCoordinateValue>100</ansi-nist:SegmentLeftHorizontalCoordinateValue>  <ansi-nist:SegmentRightHorizontalCoordinateValue>150</ansi-nist:SegmentRightHorizontalCoordinateValue>  <ansi-nist:SegmentTopVerticalCoordinateValue>15</ansi-nist:SegmentTopVerticalCoordinateValue> 

 </itl:FingerprintImageSegmentPositionSquare> <itl:FingerprintImageSegmentPositionSquare>

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode>  <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 

 <ansi-nist:SegmentLeftHorizontalCoordinateValue>160</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

 <ansi-nist:SegmentRightHorizontalCoordinateValue>200</ansi-nist:SegmentRightHorizontalCoordinateValue>  <ansi-nist:SegmentTopVerticalCoordinateValue>15</ansi-nist:SegmentTopVerticalCoordinateValue> 

 </itl:FingerprintImageSegmentPositionSquare> <!-- =====================================================fieldID="14.022" fieldMnemonic="NQM" =

 <ansi-nist:FingerprintImageNISTQuality> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure>

 </ansi-nist:FingerprintImageNISTQuality>  <ansi-nist:FingerprintImageNISTQuality> 

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 

 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure>

 </ansi-nist:FingerprintImageNISTQuality>  <ansi-nist:FingerprintImageNISTQuality> 

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode>  <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure>

 </ansi-nist:FingerprintImageNISTQuality>  <ansi-nist:FingerprintImageNISTQuality> 

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode>  <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure>

 </ansi-nist:FingerprintImageNISTQuality>  <!-- =====================================================fieldID="14.023" fieldMnemonic="SQM" =

 <ansi-nist:FingerprintImageSegmentationQuality> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

233 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </ansi-nist:FingerprintImageSegmentationQuality>  <ansi-nist:FingerprintImageSegmentationQuality> 

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode>  <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </ansi-nist:FingerprintImageSegmentationQuality>  <!-- =====================================================fieldID="14.024" fieldMnemonic="FQM" =

 <itl:FingerprintImageQuality> 

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode>  <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:FingerprintImageQuality>  <itl:FingerprintImageQuality> 

 <ansi-nist:FingerPositionCode>9</ansi-nist:FingerPositionCode>  <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification> 

234 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 

36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:FingerprintImageQuality>  <!-- =====================================================fieldID="14.025" fieldMnemonic="ASEG" 

 <itl:FingerprintImageSegmentPositionPolygon> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

 <itl:PositionPolygonVertexQuantity>4</itl:PositionPolygonVertexQuantity>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>100</ansi-nist:PositionHorizontalCoordinateValue>  <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>150</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>150</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>100</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex> 

 </itl:FingerprintImageSegmentPositionPolygon>  <itl:FingerprintImageSegmentPositionPolygon> 

 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode>  <itl:PositionPolygonVertexQuantity>4</itl:PositionPolygonVertexQuantity>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>160</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>200</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>200</ansi-nist:PositionHorizontalCoordinateValue> 

 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 

235 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 </itl:PositionPolygonVertex>  <itl:PositionPolygonVertex>

 <ansi-nist:PositionHorizontalCoordinateValue>160</ansi-nist:PositionHorizontalCoordinateValue>  <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 

 </itl:PositionPolygonVertex> 

 </itl:FingerprintImageSegmentPositionPolygon> 

 </itl:FingerprintImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 14 Variable Resolution Fingerprint Image (Major Case) 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>12</ansi-nist:RecordCategoryCode> 

 <!-- ====================================================== fieldID="14.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>10</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="14.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:FingerprintImage>

 <!-- =====================================================fieldID="14.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="14.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="14.005" fieldMnemonic="FCD <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="14.016" fieldMnemonic="SHP <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue>  <!-- =====================================================fieldID="14.004" fieldMnemonic="SRC

236 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="14.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> <!-- =====================================================fieldID="14.030" fieldMnemonic="DMM <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="14.020" fieldMnemonic="COM" = <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="14.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="14.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="14.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="14.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="14.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="14.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="14.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1</ansi-nist:FingerprintImageImpressionCaptureCate

 <!-- =====================================================fieldID="14.013" fieldMnemonic="FGP" = <ansi-nist:FingerPositionCode>19</ansi-nist:FingerPositionCode>  <!-- =====================================================fieldID="14.014" fieldMnemonic="PPD" = <ansi-nist:FingerprintImageMajorCasePrint> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:MajorCasePrintCode>EJI</ansi-nist:MajorCasePrintCode>  <!-- =====================================================fieldID="14.015" fieldMnemonic="PPC <ansi-nist:MajorCasePrintSegmentOffset> 

 <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 

 <ansi-nist:SegmentLocationCode>DST</ansi-nist:SegmentLocationCode> 

237 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode>  <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue>  <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue>  <ansi-nist:SegmentTopVerticalCoordinateValue>55</ansi-nist:SegmentTopVerticalCoordinateValue> 

 </ansi-nist:MajorCasePrintSegmentOffset>  <ansi-nist:MajorCasePrintSegmentOffset> 

 <ansi-nist:SegmentBottomVerticalCoordinateValue>126</ansi-nist:SegmentBottomVerticalCoordinateValue> 

 <ansi-nist:SegmentLocationCode>MED</ansi-nist:SegmentLocationCode>  <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode>  <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue>  <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue>  <ansi-nist:SegmentTopVerticalCoordinateValue>92</ansi-nist:SegmentTopVerticalCoordinateValue> 

 </ansi-nist:MajorCasePrintSegmentOffset> 

 </ansi-nist:FingerprintImageMajorCasePrint>  <!-- =====================================================fieldID="14.022" fieldMnemonic="NQM" =

 <ansi-nist:FingerprintImageNISTQuality> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure>

 </ansi-nist:FingerprintImageNISTQuality>  <!-- =====================================================fieldID="14.024" fieldMnemonic="FQM" =

 <itl:FingerprintImageQuality> 

 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode>  <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:FingerprintImageQuality> 

 </itl:FingerprintImage> 

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- RECORD TYPE 15 Variable Resolution Palmprint Image 

 <!-- ======================================================================================== <itl:PackageImageRecord> 

238 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:RecordCategoryCode>15</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="15.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>13</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="15.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:PalmprintImage>

 <!-- =====================================================fieldID="15.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="15.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="15.005" fieldMnemonic="PCD

 <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="15.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

 <!-- =====================================================fieldID="15.004" fieldMnemonic="SRC <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="15.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue>

 <!-- =====================================================fieldID="15.030" fieldMnemonic="DMM

 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="15.020" fieldMnemonic="COM" = <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

239 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- =====================================================fieldID="15.011" fieldMnemonic="CGA" = <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="15.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="15.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="15.008" fieldMnemonic="SLC" = <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="15.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="15.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="15.003" fieldMnemonic="IMP" == 

 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>10</ansi-nist:FingerprintImageImpressionCaptureCa

 <!-- =====================================================fieldID="15.013" fieldMnemonic="PLP" = <ansi-nist:PalmPositionCode>28</ansi-nist:PalmPositionCode>  <!-- =====================================================fieldID="15.024" fieldMnemonic="PQM" = <itl:PalmprintImageQuality>

 <ansi-nist:PalmPositionCode>28</ansi-nist:PalmPositionCode>

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityAlgorithmVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmVendorIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

 </itl:PalmprintImageQuality>

 </itl:PalmprintImage>

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!--

 RECORD TYPE 16 User Defined Testing Image 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>16</ansi-nist:RecordCategoryCode> 

 <!-- ====================================================== fieldID="16.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification> 

240 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <nc:IdentificationID>14</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="16.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:TestImage>

 <!-- =====================================================fieldID="16.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 

 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="16.003" fieldMnemonic="UDI" ==  <nc:BinaryDescriptionText>Test Image</nc:BinaryDescriptionText>  <!-- =====================================================fieldID="16.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="16.005" fieldMnemonic="UTD

 <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="16.016" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue>  <!-- =====================================================fieldID="16.004" fieldMnemonic="SRC

 <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="16.017" fieldMnemonic="SVP

 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> <!-- =====================================================fieldID="16.030" fieldMnemonic="DMM

 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="16.013" fieldMnemonic="CSP" =

 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> <!-- =====================================================fieldID="16.020" fieldMnemonic="COM" =

241 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="16.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="16.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="16.009" fieldMnemonic="HPS" =

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="16.024" fieldMnemonic="UQS" = <ansi-nist:ImageQuality>

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue>  <ansi-nist:QualityMeasureVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityMeasureVendorIdentification> 

 </ansi-nist:ImageQuality> <!-- =====================================================fieldID="16.008" fieldMnemonic="SLC" =

 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="16.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

 <!-- =====================================================fieldID="16.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 </itl:PackageImageRecord> </itl:TestImage>  <!-- ======================================================================================== <!--

 RECORD TYPE 17 Iris Image 

<!-- ========================================================================================

 <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>17</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="17.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>15</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="17.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

242 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <itl:IrisImage>

 <!-- =====================================================fieldID="17.999" fieldMnemonic="DATA" 

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <!-- =====================================================fieldID="17.012" fieldMnemonic="BPX" = <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity>  <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="17.005" fieldMnemonic="ICD"  <ansi-nist:CaptureDate>

 <nc:Date>1953-04-23</nc:Date>

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="17.022" fieldMnemonic="SHP

 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue>  <!-- =====================================================fieldID="17.004" fieldMnemonic="SRC <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization> <!-- =====================================================fieldID="17.023" fieldMnemonic="SVP <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> <!-- =====================================================fieldID="17.030" fieldMnemonic="DMM <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="17.013" fieldMnemonic="CSP" =

 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> <!-- =====================================================fieldID="17.021" fieldMnemonic="COM" = <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText>

 <!-- =====================================================fieldID="17.011" fieldMnemonic="CGA" =

 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> <!-- =====================================================fieldID="17.006" fieldMnemonic="HLL" =

 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity>  <!-- =====================================================fieldID="17.009" fieldMnemonic="HPS" =

243 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue>  <!-- =====================================================fieldID="17.024" fieldMnemonic="IQS" ==  <ansi-nist:ImageQuality>

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityValue>100</ansi-nist:QualityValue>  <ansi-nist:QualityMeasureVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityMeasureVendorIdentification> 

 </ansi-nist:ImageQuality> <!-- =====================================================fieldID="17.008" fieldMnemonic="SLC" =

 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

 <!-- =====================================================fieldID="17.007" fieldMnemonic="VLL" == 

 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity>  <!-- =====================================================fieldID="17.010" fieldMnemonic="VPS" =

 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

 <!-- =====================================================fieldID="17.003" fieldMnemonic="FID" == 

 <ansi-nist:IrisEyePositionCode>2</ansi-nist:IrisEyePositionCode> <!-- =====================================================fieldID="17.014" fieldMnemonic="RAE" =

 <ansi-nist:IrisEyeRotationAngleMeasure>8192</ansi-nist:IrisEyeRotationAngleMeasure>

 <!-- =====================================================fieldID="17.015" fieldMnemonic="RAU" =

 <ansi-nist:IrisEyeRotationUncertaintyValueText>FFFF</ansi-nist:IrisEyeRotationUncertaintyValueText> 

 <ansi-nist:IrisImageCapture>

 <!-- =====================================================fieldID="17.018" fieldMnemonic="GUI" 

 <ansi-nist:CaptureDeviceGlobalIdentification> 

 <nc:IdentificationID>A2849B293059C200</nc:IdentificationID> 

 </ansi-nist:CaptureDeviceGlobalIdentification>  <!-- =====================================================fieldID="17.017" fieldMnemonic="DUI" 

 <ansi-nist:CaptureDeviceIdentification> 

 <nc:IdentificationID>P270NEIS67830000</nc:IdentificationID> 

 </ansi-nist:CaptureDeviceIdentification>  <!-- =====================================================fieldID="17.019" fieldMnemonic="MMS

 <ansi-nist:CaptureDeviceMakeText>RGT88</ansi-nist:CaptureDeviceMakeText>  <ansi-nist:CaptureDeviceModelText>PEARL</ansi-nist:CaptureDeviceModelText>  <ansi-nist:CaptureDeviceSerialNumberText>2838590029395784-4</ansi-nist:CaptureDeviceSerialNumberText>  <!-- =====================================================fieldID="17.016" fieldMnemonic="IPC" 

244 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:IrisImageHorizontalOrientationCode>2</ansi-nist:IrisImageHorizontalOrientationCode> <ansi-nist:IrisImageScanCategoryCode>3</ansi-nist:IrisImageScanCategoryCode>  <ansi-nist:IrisImageVerticalOrientationCode>1</ansi-nist:IrisImageVerticalOrientationCode> 

 </ansi-nist:IrisImageCapture> <!-- =====================================================fieldID="17.020" fieldMnemonic="ECL" =

 <ansi-nist:IrisEyeColorAttributeCode>MUL</ansi-nist:IrisEyeColorAttributeCode>

 <!-- =====================================================fieldID="17.025" fieldMnemonic="ALS" =

 <ansi-nist:IrisImageAcquisitionLightingSpectrumValue>VIS</ansi-nist:IrisImageAcquisitionLightingSpectrumValue>  <!-- =====================================================fieldID="17.026" fieldMnemonic="IRD" ==  <itl:IrisDiameterPixelQuantity>304</itl:IrisDiameterPixelQuantity> 

 </itl:IrisImage>

 </itl:PackageImageRecord>  <!-- ======================================================================================== <!-- 

RECORD TYPE 99 CBEFF Data 

 <!-- ======================================================================================== <itl:PackageImageRecord>

 <ansi-nist:RecordCategoryCode>99</ansi-nist:RecordCategoryCode>  <!-- ====================================================== fieldID="99.002" fieldMnemonic="IDC" == 

 <ansi-nist:ImageReferenceIdentification>

 <nc:IdentificationID>16</nc:IdentificationID> 

 </ansi-nist:ImageReferenceIdentification> <!-- =================================================== fieldID="99.200-998" fieldMnemonic="UDF" =

 <itl:ExampleUserDefinedFields> 

 <!-- Well-formed XML goes here. Users may define a substitute element. --> 

 </itl:ExampleUserDefinedFields>  <ansi-nist:CBEFFImage>

 <!-- =====================================================fieldID="99.999" fieldMnemonic="BDB" =

 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42  d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

 <ansi-nist:ImageCaptureDetail>

 <!-- =====================================================fieldID="99.005" fieldMnemonic="BCD

 <ansi-nist:CaptureDate>

 <nc:DateTime>2005-11-05T05:25:00Z</nc:DateTime> 

 </ansi-nist:CaptureDate> <!-- =====================================================fieldID="99.004" fieldMnemonic="SRC

245 
1 

2 3 4 5 6 7 8 9 

10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 <ansi-nist:CaptureOrganization>

 <nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

 </nc:OrganizationIdentification>  <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName>

 </ansi-nist:CaptureOrganization>

 </ansi-nist:ImageCaptureDetail>  <!-- =====================================================fieldID="99.102" fieldMnemonic="BDQ" =

 <ansi-nist:ImageQuality>

 <ansi-nist:QualityAlgorithmProductIdentification> 

 <nc:IdentificationID>28495</nc:IdentificationID> 

 </ansi-nist:QualityAlgorithmProductIdentification>  <ansi-nist:QualityValue>49</ansi-nist:QualityValue>  <ansi-nist:QualityMeasureVendorIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

 </ansi-nist:QualityMeasureVendorIdentification> 

 </ansi-nist:ImageQuality> <!-- =====================================================fieldID="99.103" fieldMnemonic="BFO" =

 <ansi-nist:CBEFFFormatOwnerIdentification> 

 <nc:IdentificationID>001B</nc:IdentificationID> 

 </ansi-nist:CBEFFFormatOwnerIdentification>  <!-- =====================================================fieldID="99.104" fieldMnemonic="BFT" = <ansi-nist:CBEFFFormatCategoryIdentification>

 <nc:IdentificationID>000A</nc:IdentificationID> 

 </ansi-nist:CBEFFFormatCategoryIdentification> <!-- =====================================================fieldID="99.100" fieldMnemonic="HDV" =

 <ansi-nist:CBEFFVersionIdentification>

 <nc:IdentificationID>0101</nc:IdentificationID> 

 </ansi-nist:CBEFFVersionIdentification> <!-- =====================================================fieldID="99.101" fieldMnemonic="BTY" = <ansi-nist:CBEFFCategoryCode>200</ansi-nist:CBEFFCategoryCode> 

 </ansi-nist:CBEFFImage>

 </itl:PackageImageRecord> </itl:NISTBiometricInformationExchangePackage> 

246 
 

1 Annex G INCITS / M1 378 Minutiae Format 

2 (Informative) 

3 Minutia placement and type 

4 For templates to be conformant with Section 5 of the ANSI INCITS 378-2004 standard, the following method, which 

5 enhances the current INCITS 378-2004 standard, shall be used for determining placement (location and angular direction) 

6 of individual minutiae. 

7 The position or location of a minutia representing a ridge ending shall be the point of forking of the medial skeleton of the 

8 valley area immediately in front of the ridge ending. If the three legs of the valley area were thinned down to a single9 pixel-wide skeleton, the point of the intersection is the location of the minutia. Similarly, the location of the minutia for a 

10 bifurcation shall be the point of forking of the medial skeleton of the ridge. If the three legs of the ridge were each thinned 

11 down to a single-pixel-wide skeleton, the point where the three legs intersect is the location of the minutia. 

12 After all ridge endings have been converted to bifurcations, all of the minutiae of the fingerprint image are represented as 

13 bifurcations. The X and Y pixel coordinates of the intersection of the three legs of each minutia can be directly formatted. 

14 Determination of the minutia direction can be extracted from each skeleton bifurcation. The three legs of every skeleton 

15 bifurcation must be examined and the endpoint of each leg determined. Figure G1 illustrates the three methods used for 

16 determining the end of a leg that is based on a scanning resolution of 500 ppi. The ending is established according to 

17 the event that occurs first. The pixel count is based on a scan resolution of 500 ppi. Different scan resolutions would 

18 imply different pixel counts. 

19 • A distance of .064” (the 32nd pixel) 

20 • The end of skeleton leg that occurs between a distance of .02” and .064” (the 10th through the 32nd pixels); shorter 

21 legs are not used 

22 • A second bifurcation is encountered within a distance of .064” (before the 32nd pixel) 

23 

24 Figure G1 Minutiae angle components 

25 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

32 pixels 

<32 pixels 32 pixels 

32 pixels 

26 

27 The angle of the minutiae is determined by constructing three virtual rays originating at the bifurcation point and extending 

28 to the end of each leg. The smallest of the three angles formed by the rays is bisected to indicate the minutiae direction. 

247 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 min Max 

<incits:Minutiae> CONCRETE SUBSTITUTE FOR <itl:RecordMinutiae> 1 1 

M 9.126 <ansi-nist:CBEFFFormatOwnerIdentification> 1 1

M <ansi-nist:CBEFFFormatCategoryIdentification> 1 1

M <incits:CBEFFProductIdentification> 1 1

M 9.127 <incits:FingerprintImageCapture> 1 1

M <incits:CaptureDeviceCertificationText:> 1 1

M <incits:CaptureDeviceIdentification:> 1 1

M < ansi-nist:NISTImage> 1 1 

HLL M 9.128 <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 

2 Coordinate system 

3 The coordinate system used to express the minutiae of a fingerprint shall be a Cartesian coordinate system. Minutiae 

4 locations shall be represented by their x and y coordinates. The origin of the coordinate system shall be the upper left 

5 corner of the original image with x increasing to the right and y increasing downward. Both x and y coordinates of a 

6 minutiae shall be represented in pixel units from the origin. It should be noted that the location of the origin and units of 

7 measure is not in agreement with the convention used in the “standard format” definitions of Section 214.1. 

8 Minutiae direction 

9 Angles are expressed in standard mathematical format, with zero degrees to the right and angles increasing in the 

10 counterclockwise direction. Recorded angles are in the direction pointing back along the ridge for a ridge ending and 

11 toward the center of the valley for a bifurcation. This convention is 180 degrees opposite of the angle convention 

12 described in the “standard format” definitions of Section 214.1.4. 

13 XML elements for Type-9 logical record INCITS-378 Format 

14 For purposes of this standard, no proprietary information shall be contained in any of the information and data specified by 

15 the M1-378 block of information items. Therefore, the following descriptions are presented for each of the elements in this 

16 Type-9 block. All elements of the Type-9 records shall be recorded as ASCII text. No binary content is permissible in this 

17 record. 

18 The first four elements of the Type-9 record are mandatory and retain the same meaning a described in Sections 214.2.2 

19 through 214.2.5. The description of those elements is not repeated here. In the Part-2 XML version of the Type-9 record, 

20 a minutiae representation other than the NIST “standard format” is implemented as substitution element for the abstract 

21 element <itl:RecordMinutiae>. This Annex defines a substitution element. 

22 

23 Table G201 Type-9 INCITS-378 minutiae representation 

248 
 

Part 1 

Ident 

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 min Max 

HPS M 9.131 <ansi-nist:ImageHorizontalPixelDensityValue> 1 1 

SLC M 9.130 <ansi-nist:ImageScaleUnitsCode> 1 1

VLL M 9.129 <ansi-nist:VerticalLineLengthPixelQuantity> 1 1

VPS M 9.132 <ansi-nist:ImageVerticalPixelDensityValue> 1 1

M 9.133 < incits:FingerViewCode> 1 1 

*M 9.134 < ansi-nist:FingerPositionCode> FIN 1 Unlim

 *M < ansi-nist:PalmPositionCode> PAL 1 Unlim

 M 9.135 < incits:MinutiaeQuality> 1 1 

M < ansi-nist:QualityAlgorithmProductIdentification> 1 1 

M < ansi-nist:QualityValue> 1 1 

M < ansi-nist:QualityMeasureVendorIdentification> 1 1 

M 9.136 < ansi-nist:MinutiaeQuantity> 1 1 

M 9.137 < itl:MinutiaDetail> 1 Unlim

 M < ansi-nist:PositionHorizontalCoordinateValue> 1 1 

M < ansi-nist:PositionVerticalCoordinateValue> 1 1 

M < ansi-nist:MinutiaIdentification> 1 1 

M < ansi-nist:PositionThetaAngleMeasure> 1 1 

M < ansi-nist:MinutiaQualityValue> 1 1 

M <incits:MinutiaCategoryCode> 1 1 

O 9.138 < incits:RidgeCountExtractionMethodCode> 0 1 

O < incits:RidgeCountDetail> 0 Unlim

 M < ansi-nist:MinutiaIdentification> 1 1 

M < ansi-nist:RidgeCountReferenceIdentification> 1 1 

M < ansi-nist:RidgeCountValue> 1 1 

O 9.139 < incits:MinutiaeFingerCorePosition> 0 Unlim

 M <ansi-nistPositionHorizontalCoordinateValue> 1 1 

M <ansi-nistPositionVerticalCoordinateValue> 1 1 

M <ansi-nistPositionThetaAngleMeasure> 1 1 

O 9.139 < incits:MinutiaeFingerDeltaPosition> 0 Unlim

 M <ansi-nistPositionHorizontalCoordinateValue> 1 1 

M <ansi-nistPositionVerticalCoordinateValue> 1 1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

249 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Part 1 Cond Part 1 Part 2 XML Element Name IMG Occur count 

Ident code Field 

Number 

 min Max 

M <ansi-nistPositionThetaAngleMeasure> 1 1 

1 In the subsections that follow, text in bold between opening and closing tags is informative and only included for 

2 illustrative purposes, unless otherwise specifically stated (as it is for <ansi-nist:CBEFFFormatOwnerIdentification> for 

3 example). 

4 224.1.1 Element <incits:Minutiae> 

5 Complex element <itl:RecordMinutiae> is abstract, and as such is unusable by itself. This Annex defines a specific, 

6 concrete substitution element named <incits:Minutiae>. 

7 This substitution element may be defined in an extension schema similar to this, using “incits:” as the namespace. 

8 <xsd:element name="Minutiae" 

9 substitutionGroup="itl:RecordMinutiae"

10 type="incits:MinutiaeType"/>

11 

12 <xsd:complexType name="MinutiaeType">

13 <xsd:complexContent>

14 <xsd:extension base="s:ComplexObjectType">

15 <xsd:sequence>

16 

17 [ Content defined in schema for this Annex ]

18 

19 </xsd:sequence>

20 </xsd:extension>

21 </xsd:complexContent>

22 </xsd:complexType> 

23 The element would then appear in an instance document like this: 

24 <incits:Minutiae> 

25 

26 [ Content defined in instance example for this Annex ]

27 

28 </incits:Minutiae> 

29 

30 The complex element <incits:Minutiae> has been defined as a concrete substitution for the abstract element 

31 <itl:RecordMinutiae>. It contains the INCITS/M1 378 Minutiae Format content for representation of minutiae. All of the 

32 elements in this format are nested within, as described in the subsections below. 

33 <incits:Minutiae> 

34 [. . . INCITS/M1 378 minutiae elements . . .] 

250 
 

1 </incits:Minutiae> 

2 Element <ansi-nist:CBEFFFormatOwnerIdentification> 

3 Cross reference: Part-1 Annex G Field 9.126: CBEFF information, owner item 

4 This mandatory element shall contain the value "27". This is the identification of the CBEFF Format Owner assigned by 

5 the International Biometric Industry Association (IBIA) to INCITS Technical Committee M1. 

6 Complex element <ansi-nist:CBEFFFormatOwnerIdentification> shall have the simple element <nc:IdentificationID>, 

7 which will contain the four hex digits assigned by IBIA represented by a string of four ASCII characters. 

8 

9 <ansi-nist:CBEFFFormatOwnerIdentification> 

10 <nc:IdentificationID>FFF0</nc:IdentificationID>

11 </ansi-nist:CBEFFFormatOwnerIdentification> 

12 Element <ansi-nist:CBEFFFormatCategoryIdentification> 

13 Cross reference: Part-1 Annex G Field 9.126: CBEFF information, type item 

14 This mandatory element shall contain the CBEFF Format Type that is assigned a value of "513" to indicate that this record 

15 contains only location and angular direction data without any Extended Data Block information. A value of “514” indicates 

16 the presence of extended data. 

17 Complex element <ansi-nist:CBEFFFormatCategoryIdentification> shall have the simple element <nc:IdentificationID>, 

18 which will contain the required value. 

19 <ansi-nist:CBEFFFormatCategoryIdentification>

20 <nc:IdentificationID>513</nc:IdentificationID>

21 </ansi-nist:CBEFFFormatCategoryIdentification> 

22 Element <incits:CBEFFProductIdentification> 

23 Cross reference: Part-1 Annex G Field 9.126: CBEFF information, product item 

24 This mandatory element shall contain the CBEFF Product Identifier (PID) that identifies the "owner" of the encoding 

25 equipment. The vendor establishes this value. It can be obtained from the IBIA website (www.ibia.org) if it is posted. 

26 Complex element <incits:CBEFFProductIdentification> shall have the simple element <nc:IdentificationID>, which will 

27 contain the required value. 

28 <incits:CBEFFProductIdentification> 

29 <nc:IdentificationID>RG88</nc:IdentificationID>

30 </incits:CBEFFProductIdentification> 

31 Element <incits:FingerprintImageCapture> 

32 Cross reference: Part-1 Annex G Field 9.127: Capture equipment identification 

33 This mandatory element shall contain two child elements. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

251 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 The child element <incits:CaptureDeviceCertificationText> shall contain "APPF" if the equipment used originally to 

2 acquire the image was certified to conform with Appendix F (IAFIS Image Quality Specification, January 29, 1999) of 

3 CJIS-RS-0010, the Federal Bureau of Investigation's Electronic Fingerprint Transmission Specification. If the equipment 

4 did not conform it will contain the value of "NONE". 

5 The child element <ansi-nist:CaptureDeviceIdentification> shall contain the Capture Equipment ID which is a vendor6 assigned product number of the capture equipment. A value of "0" indicates that the capture equipment ID is unreported. 

7 Complex element <ansi-nist:CaptureDeviceIdentification> shall have the simple element <nc:IdentificationID>, which will 

8 contain the required value. 

9 

10 

11 

12 

13 

14 

15 <incits:FingerprintImageCapture>

16 <incits:CaptureDeviceCertificationText>APPF 

17 </incits:CaptureDeviceCertificationText>

18 <incits:CaptureDeviceIdentification>

19 <nc:IdentificationID>SCANR88</nc:IdentificationID>

20 </incits:CaptureDeviceIdentification>

21 </incits:FingerprintImageCapture>

22 

23 Element <ansi-nist:NISTImage> 

24 This mandatory element shall contain five mandatory child elements. 

25 Cross reference: Part-1 Annex G Field 9.128: Horizontal line length (HLL) 

26 The mandatory child element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> shall contain the number of pixels 

27 contained on a single horizontal line of the transmitted image. The maximum horizontal size is limited to 65,534 pixels. 

28 Cross reference: Part-1 Annex G Field 9.131: Horizontal pixel scale (HPS) 

29 The mandatory child element <ansi-nist:ImageHorizontalPixelDensityValue> shall specify the integer pixel density used in 

30 the horizontal direction providing the <ansi-nist:ImageScaleUnitsCode> (SLC) element contains a "1" or a "2". Otherwise, 

31 it indicates the horizontal component of the pixel aspect ratio. 

32 Cross reference: Part-1 Annex G Field 9.130: Scale units (SLC) 

33 The mandatory child element <ansi-nist:ImageScaleUnitsCode> shall specify the units used to describe the image 

34 sampling frequency (pixel density). A "1" in this element indicates pixels per inch, or a "2" indicates pixels per centimeter. 

35 A "0" in this element indicates no scale is given. For this case, the quotient of HPS/VPS gives the pixel aspect ratio. 

36 Cross reference: Part-1 Annex G Field 9.129: Vertical line length (VLL) 

37 The mandatory child element <ansi-nist:ImageVerticalLineLengthPixelQuantity> shall contain the number of horizontal 

38 lines contained in the transmitted image. The maximum vertical size is limited to 65,534 pixels. 

39 Cross reference: Part-1 Annex G Field 9.132: Vertical pixel scale (VPS) 

252 
 

 

 

 

5 

10 

15 

20 

25 

30 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 The mandatory child element <ansi-nist:ImageVerticalPixelDensityValue> shall specify the integer pixel density used in 

2 the vertical direction providing the <ansi-nist:ImageScaleUnitsCode> (SLC) element contains a "1" or a "2". Otherwise, it 

3 indicates the vertical component of the pixel aspect ratio. 

4 <ansi-nist:NISTImage>

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80 

6 </ansi-nist:ImageHorizontalLineLengthPixelQuantity>

7 <ansi-nist:CaptureHorizontalPixelDensityValue>1200 

8 </ansi-nist:CaptureHorizontalPixelDensityValue>

9 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode>

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65 

11 </ansi-nist:ImageVerticalLineLengthPixelQuantity>

12 <ansi-nist:ImageVerticalPixelDensityValue>1200 

13 </ansi-nist:ImageVerticalPixelDensityValue>

14 </ansi-nist:NISTImage> 

Element <incits:FingerViewCode> 

16 Cross reference: Part-1 Annex G Field 9.133: Finger view 

17 This mandatory element contains the view number of the finger associated with this record's data. The view number 

18 begins with "0" and increments by one to "15". 

19 <incits:FingerViewCode>12</incits:FingerViewCode> 

Element <ansi-nist:FingerPositionCode> or <ansi-nist:PalmPositionCode> 

21 Cross reference: Part-1 Annex G Field 9.134: Finger position 

22 This mandatory element shall contain the code designating the finger position that produced the information in this Type-9 

23 record. A code between 1 and 10 taken from Table 212 shall be used to indicate the finger position. 

24 <ansi-nist:FingerPositionCode>12</ansi-nist:FingerPositionCode> 

Element <incits:MinutiaeQuality> 

26 Cross reference: Part-1 Annex G Field 9.135: Finger quality 

27 This mandatory complex element shall contain the quality of the overall finger minutiae data in three child elements. They 

28 identify a quality score and the algorithm used to create the quality score. This information is useful to enable the recipient 

29 of the quality score to differentiate between quality scores generated by different algorithms and adjust for any differences 

in processing or analysis as necessary. 

31 The child element <ansi-nist:QualityAlgorithmProductIdentification> shall contain a numeric product code assigned by the 

32 vendor of the quality algorithm, which may be registered with the IBIA, but it is not required to be registered. It indicates 

33 which of the vendor’s algorithms was used in the calculation of the quality score. This element contains the ASCII 

34 representation of the integer product code and should be within the range 1 to 65535. Complex element <ansinist:QualityAlgorithmProductIdentification> shall have the simple element <nc:IdentificationID>, which will contain the 

36 identification datum. 

37 The child element <ansi-nist:QualityValue> shall contain a quantitative expression of the predicted matching performance 

38 of the biometric sample. This item contains the ASCII representation of the integer image quality score between 0 and 

39 100 assigned to the image data by a quality algorithm. Higher values indicate better quality. An entry of “255” shall 

253 
 

1 indicate a failed attempt to calculate a quality score. An entry of “254” shall indicate that no attempt to calculate a quality 

2 score was made. The use of additional values to convey other information should be harmonized with ISO/IEC 19794 

3 standards. 

4 The child element <ansi-nist:QualityMeasureVendorIdentification> shall contain the ID of the vendor of the quality 

5 algorithm used to calculate the quality score. This 4-digit hex value is assigned by IBIA and expressed as four ASCII 

6 characters. The IBIA shall maintain the Vendor Registry of CBEFF Biometric Organizations that will map the value in this 

7 element to a registered organization. Complex element <ansi-nist:QualityMeasureVendorIdentification> shall have the 

8 simple element <nc:IdentificationID>, which will contain the identification datum. 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 <incits:MinutiaeQuality>

19 <ansi-nist:QualityAlgorithmProductIdentification>

20 <nc:IdentificationID>28488</nc:IdentificationID>

21 </ansi-nist:QualityAlgorithmProductIdentification>

22 <ansi-nist:QualityValue>100 

23 </ansi-nist:QualityValue>

24 <ansi-nist:QualityMeasureVendorIdentification>

25 <nc:IdentificationID>FFF0</nc:IdentificationID>

26 </ansi-nist:QualityMeasureVendorIdentification>

27 </incits:MinutiaeQuality> 

28 Element <ansi-nist:MinutiaeQuantity> 

29 Cross reference: Part-1 Annex G Field 9.136: Number of minutiae 

30 The mandatory element shall contain a count of the number of minutiae recorded in this logical record. 

31 <ansi-nist:MinutiaeQuantity>4</ansi-nist:MinutiaeQuantity> 

32 Element <itl:MinutiaDetail> 

33 Cross reference: Part-1 Annex G Field 9.137: Finger minutiae data 

35 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

34 This mandatory complex element has six child elements, each containing the details for a single minutiae. This complex 

element shall occur in its entirety multiple times. The total number of occurrences of <itl:MinutiaDetail> must agree with 

36 the count found in <ansi-nist:MinutiaeQuantity> (field 136). 

37 The child element <ansi-nist:PositionHorizontalCoordinateValue> shall contain the 'x' coordinate of the minutia in pixel 

38 units. 

39 The child element <ansi-nist:PositionVerticalCoordinateValue> shall contain the 'y' coordinate of the minutia in pixel units. 

254 
 

1 The child element <ansi-nist:MinutiaIdentification> shall contain the minutiae index number, which shall be initialized to “1” 

2 and incremented by “1” for each additional minutia in the fingerprint. Complex element <ansi-nist:MinutiaIdentification> 

3 shall have the simple element <nc:IdentificationID>, which will contain the identification datum. 

4 The child element <ansi-nist:PositionThetaAngleMeasure> shall contain the minutiae angle recorded in units of two 

5 degrees. This value shall be nonnegative between 0 and 179. 

6 The child element <incits:MinutiaQualityValue> shall contain the quality of each minutiae. This value shall range from 1 

7 as a minimum to 100 as a maximum. A value of "0" indicates that no quality value is available. 

8 The child element <incits:MinutiaCategoryCode> shall contain the minutiae type. A value of "0" is used to represent a 

9 minutiae of type "OTHER", a value of "1" for a ridge ending and a value of "2" for a ridge bifurcation. 

10 <itl:MinutiaDetail> 

11 <ansi-nist:PositionHorizontalCoordinateValue>0486 

12 </ansi-nist:PositionHorizontalCoordinateValue>

13 <ansi-nist:PositionVerticalCoordinateValue>2839 

14 </ansi-nist:PositionVerticalCoordinateValue>

15 <ansi-nist:MinutiaIdentification> 

16 <nc:IdentificationID>00</nc:IdentificationID>

17 </ansi-nist:MinutiaIdentification>

18 <ansi-nist:PositionThetaAngleMeasure>048 

19 </ansi-nist:PositionThetaAngleMeasure>

20 <ansi-nist:MinutiaQualityValue>100 

21 </ansi-nist:MinutiaQualityValue>

22 <incits:MinutiaCategoryCode>2 

23 </incits:MinutiaCategoryCode>

24 </itl:MinutiaDetail> 

25 Element <incits:RidgeCountExtractionMethodCode> 

26 Cross reference: Part-1 Annex G Field 9.138: Ridge count information, first information item 

27 This element shall indicate the ridge count extraction method. A “0” indicates that no assumption shall be made about the 

28 method used to extract ridge counts, nor their order in the record. A “1” indicates that for each center minutiae, ridge 

29 count data was extracted to the nearest neighboring minutiae in four quadrants, and ridge counts for each center minutia 

30 are listed together. A “2” indicates that for each center minutiae, ridge count data was extracted to the nearest 

31 neighboring minutiae in eight octants, and ridge counts for each center minutia are listed together. 

32 

33 <incits:RidgeCountExtractionMethodCode>1 

34 </incits:RidgeCountExtractionMethodCode> 

35 Element <incits:RidgeCountDetail> 

36 Cross reference: Part-1 Annex G Field 9.138: Ridge count information 

37 This complex element shall consist of three child elements. The complex element <incits:RidgeCountDetail> shall have 

38 multiple occurrences, one for each ridge count value reported. 

39 The child element <ansi-nist:MinutiaIdentification> will contain the center minutiae index number. Complex element 

40 <ansi-nist:MinutiaIdentification> shall have the simple element <nc:IdentificationID>, which will contain the identification 

41 datum. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

255 
 

1 The child element <ansi-nist:RidgeCountReferenceIdentification> will contain the neighboring minutiae index number. 

2 Complex element <ansi-nist:RidgeCountReferenceIdentification> shall have the simple element <nc:IdentificationID>, 

3 which will contain the identification datum. 

4 The child element <ansi-nist:RidgeCountValue> will contain the number of ridges crossed. 

5 <incits:RidgeCountDetail>

6 <ansi-nist:MinutiaIdentification> 

7 <nc:IdentificationID>1</nc:IdentificationID>

8 </ansi-nist:MinutiaIdentification>

9 <ansi-nist:RidgeCountReferenceIdentification>

10 <nc:IdentificationID>2</nc:IdentificationID>

11 </ansi-nist:RidgeCountReferenceIdentification>

12 <ansi-nist:RidgeCountValue>6 

13 </ansi-nist:RidgeCountValue>

14 </incits:RidgeCountDetail> 

15 Element <incits:MinutiaeFingerCorePosition> 

16 Cross reference: Part-1 Annex G Field 9.139: Core information 

17 This element may have multiple occurrences, one for each core present in the original image. This element shall have 

18 three child elements. 

19 The child element <ansi-nist:PositionHorizontalCoordinateValue> contains the ‘x’ coordinate position in pixel units. 

20 The child element <ansi-nist:PositionVerticalCoordinateValue> contains the ‘y’ coordinate position in pixel units. 

21 The child element <ansi-nist:PositionThetaAngleMeasure> contains the angle of the core recorded in units of 2 degrees. 

22 The value shall be a nonnegative value between 0 and 179. 

23 <incits:MinutiaeFingerCorePosition>

24 <ansi-nist:PositionHorizontalCoordinateValue>0035 

25 </ansi-nist:PositionHorizontalCoordinateValue>

26 <ansi-nist:PositionVerticalCoordinateValue>0045 

27 </ansi-nist:PositionVerticalCoordinateValue>

28 <ansi-nist:PositionThetaAngleMeasure>0045 

29 </ansi-nist:PositionThetaAngleMeasure>

30 </incits:MinutiaeFingerCorePosition> 

31 Element <incits:MinutiaeFingerDeltaPosition> 

32 Cross reference: Part-1 Annex G Field 9.140: Delta information 

33 This element may have multiple occurrences, one for each delta present in the original image. This element shall have 

34 three child elements. 

35 The child element <ansi-nist:PositionHorizontalCoordinateValue> contains the ‘x’ coordinate position in pixel units. 

36 The child element <ansi-nist:PositionVerticalCoordinateValue> contains the ‘y’ coordinate position in pixel units. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

256 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

The child element <ansi-nist:PositionThetaAngleMeasure> contains the angle of the delta recorded in units of 2 degrees. 

The value shall be a nonnegative value between 0 and 179. 

<incits:MinutiaeFingerDeltaPosition>

<ansi-nist:PositionHorizontalCoordinateValue>0035 

</ansi-nist:PositionHorizontalCoordinateValue>

<ansi-nist:PositionVerticalCoordinateValue>0045 

</ansi-nist:PositionVerticalCoordinateValue>

<ansi-nist:PositionThetaAngleMeasure>0045 

</ansi-nist:PositionThetaAngleMeasure>

</incits:MinutiaeFingerDeltaPosition> 

257 
 

1 Annex H Best Practice Application Level 30 

2 (Informative) 

3 

4 BEST PRACTICE RECOMMENDATION 

5 FOR THE CAPTURE OF MUGSHOTS 

6 Version 2.0 

7 September 23, 1997 

8 

9 The original version of the •Best Practice Recommendation was initiated at the Mugshot and Facial Image Workshop which was 

10 held in Gaithersburg, MD on October 23-25, 1995. Developed as a recommendation, the implementation of the practices and 

11 principles described in that document makes the conversion of existing and ongoing photographic collections more uniform. It 

12 contains a suggested set of procedures and equipment specifications for organizations considering the purchase of new systems or the 

13 upgrade of current systems. The recommendation is not designed to render current and legacy mugshot collections unacceptable. 

14 Rather, it is intended as a means of establishing or improving interoperability between mugshot systems. 

15 

16 The information contained in this updated revision of the Best Practice Recommendation, Version 2.0, does not alter any of the 

17 individual points that were consensually agreed upon and included in the original version of this recommendation. It does provide 

18 additional details and clarifications for many of those points and has been supplemented with information regarding depth-of-field 

19 and exposure considerations. 

20 

21 This recommendation reflects a minimum set of common denominators. The provisions of this recommendation are keyed to the 

22 quality aspects associated with the unaltered captured mugshot image. For new mugshot images being captured, the specifications 

23 contained in this recommendation are equally applicable to realtime electronic capture of mugshots as well as the electronic 

24 conversion of photographic images. For conversion of legacy files of photographs, most of the provisions of this recommendation are 

25 also still applicable. In the future, it should be possible to add additional specifications without contradicting any of the current 

26 contents of the recommendation. 

27 

28 * POSE 

29 The full-face or frontal pose is the most commonly used pose in photo lineups and shall always be captured. This pose is in 

30 addition to profiles or intermediate angled poses captured to acquire perspective and other information. For subjects who 

31 normally wear eyeglasses, a frontal mugshot image should be captured of the subject without glasses. This is required due to 

32 the glare from exernal illumination. An additional image can optionally be captured of the subject wearing eyeglasses. 

33 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

258 
 

1 * DEPTH OF FIELD 

2 The subjects captured facial image shall always be in focus from the nose to the ears. Although this may result in the 

3 background behind the subject being out of focus, it is not a problem. For optimum quality of the captured mugshot, the f4 stop of the lens should be set at two f-stops below the maximum aperture opening when possible. 

5 

6 * CENTERING 

7 The facial image being captured (full-face pose) shall be positioned to satisfy all of the following conditions: 

8 - The approximate horizontal mid-points of the mouth and of the bridge of the nose shall lie on an imaginary vertical 

9 straight line positioned at the horizontal center of the image. 

10 - An imaginary horizontal line through the center of the subject's eyes shall be located at approximately the 55% point 

11 of the vertical distance up from the bottom edge of the captured image. 

12 - The width of the subject's head shall occupy approximately 50% of the width of the captured image. This width 

13 shall be the horizontal distance between the mid-points of two imaginary vertical lines. Each imaginary line shall 

14 be drawn between the upper and lower lobes of each ear and shall be positioned where the external ear connects to 

15 the head. 

16 * LIGHTING 

17 Subject illumination shall be accomplished using a minimum of three (3) point balanced illumination. Appropriate diffusion 

18 techniques shall also be employed and lights positioned to minimize shadows, and to eliminate hot spots on the facial image. 

19 These hot spots usually appear on reflective areas such as cheeks and foreheads. Proper lighting shall contribute to the 

20 uniformity of illumination of the background described in the exposure requirement. 

21 * BACKGROUND 

22 The subject whose image is being captured shall be positioned in front of a background which is 18% gray with a plain 

23 smooth flat surface. A Kodak or other neutral gray card or densitometer shall be used to verify this 18% gray reflectance 

24 requirement. 

25 * EXPOSURE 

26 The exposure shall be keyed to the background. Several areas of the recorded 18% gray background shall be used to verify 

27 the proper exposure. The averages of the 8-bit Red, Green, and Blue (RGB) components within each area shall be 

28 calculated. Each of the RGB means shall fall between 105 and 125 with a standard deviation of plus or minus 10. 

29 Furthermore, for every area examined, the maximum difference between the means of any two of the RGB components 

30 shall not exceed 10. 

31 * ASPECT RATIO 

32 The Width:Height aspect ratio of the captured image shall be 1:1.25. 

33 * MINIMUM NUMBER OF PIXELS 

34 The minimum number of pixels in an electronic digital image shall be 480 pixels in the horizontal direction by 600 pixels in 

35 the vertical direction. It should be noted that the image quality of the captured mugshots and facial images will be improved 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

259 
 

1 as the number of pixels in both directions are increased. However, as images are captured with an increased number of 

2 pixels, the 1:1.25 (Width:Height) aspect ratio will be maintained. 

3 Two considerations must be noted regarding this aspect of the recommendation. First, the normal orientation of many available 

4 cameras is the landscape format which specifies a greater number of pixels in the horizontal than in the vertical direction. Unless 

5 these cameras capture at least 600 pixels in the vertical direction, it may be necessary to rotate the camera 90 degrees. Second, the 

6 480x600 capture format exceeds the VGA display format of 640x480. Therefore, at a minimum, an SVGA specification of 800x600 

7 pixels will be required to display the facial image. The image will occupy less than the total number of available horizontal pixels. 

8 

9 * COLOR SPACE 

10 Captured electronic color facial images are required. Digital images shall be represented as 24-bit RGB pixels. For every 

11 pixel, eight (8) bits will be used to represent each of the Red, Green, and Blue components. The RGB color space is the basis 

12 for other color spaces including the Y, Cb, Cr and YUV. Additional color management techniques are available from the 

13 International Color Consortium. Information regarding these techniques can be downloaded from the following URL: 

14 http://www.color.org . 

15 

16 * PIXEL ASPECT RATIO 

17 Digital cameras and scanners used to capture facial images shall use square pixels with a pixel aspect ratio of 1:1. 

18 

19 * COMPRESSION ALGORITHM 

20 The algorithm used to compress mugshot and facial images shall conform to the JPEG Sequential Baseline mode of operation 

21 as described in the specification approved by the ANSI X3L3 Standards committee. The target size for a JPEG compressed 

22 color mugshot image file shall be 25,000 to 45,000 bytes. 

23 

24 * FILE FORMAT 

25 The JPEG File Interchange Format (JFIF) shall contain the JPEG compressed image data. The JFIF file shall then be part of 

26 the transaction file for interchange which conforms to the requirements as contained in ANSI/NIST-CSL 1-1993 and 

27 ANSI/NIST-ITL 1a-1997. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

260 
 

1 Annex I Best Practice Image Capture Requirements for SAP Levels 40, 50, and 51 

2 (Informative) 

3 

4 

5 

6 

7 Introduction 

8 This set of “enhanced best practice recommendation” (EBPR) clauses is a set of constraints. These constraints can be 

9 categorized into four types of requirements: scene, photographic, digital, and format. Scene requirements refer to the 

10 content, subject and background in the image. Photographic requirements refer to lighting, focus and other constraints 

11 required for photo capture. Digital requirements refer to the conversion of the captured image into a digital record. Finally, 

12 format requirements refer to additional or conditional required fields and in a Type-10 record or NIST transaction. 

13 Note that the set of requirements applies to all poses of a subject. 

14 Scene Requirements 

15 Number of photographs 

16 Level 50 and 51 records shall include at least five photographs of the subject: frontal, left and right profile, and left and 

17 right 3⁄4 profile. 

18 A 3⁄4 profile view consists of a face with a Yaw pose angle of ± 67.5 degrees, and with Pitch and Roll angles of zero (see 

19 Section Error! Reference source not found., “Field 10.025: Subject pose angle (SPA)”). Note that for 3⁄4 profile, the 

20 orientation of the head is rotated to 3⁄4 profile (the rotation of the body shall not be required), and care should be taken to 

21 prevent the subject from keeping the head fixed while changing only the gaze. In addition, for 3⁄4 profile photographs, 

22 both eyes must be visible in the image. For full profile images, the entire body shall be rotated with the head. 

23 The “Head and Shoulders” photo composition 

24 The composition consists of a subject’s head, partial shoulders, and plain background. For a frontal-facing pose, the 

25 width of the subject's head shall occupy approximately 50% of the width of the captured image. This width shall be the 

26 horizontal distance between the mid-points of two imaginary vertical lines. Each imaginary line shall be drawn between 

27 the upper and lower lobes of each ear and shall be positioned where the external ear connects to the head. A template 

28 and an example is shown in Figure I1. For other poses, the composition shall be rotated about an imaginary axis 

29 extending from the top of the head though the base of the neck. 

30 This composition is applied to SAP levels 30, 40, and 50. 

31 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

261 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

a. A template of the “head and b. An example “head and 

shoulders” photo. The width of the shoulders” photo. 

head is 1⁄2 the width of the photo. 

1 Figure I1 – A facial image template and an example image that meets “Head and Shoulders” (levels 40 and 50) 

2 scene constraints. 

3 

4 The “Head Only” photo composition 

5 The composition consists of a subject’s head, and a plain background. For a frontal-facing pose, the width of the subject's 

6 head shall occupy approximately 70% of the width of the captured image. This width shall be the horizontal distance 

7 between the mid-points of two imaginary vertical lines. Each imaginary line shall be drawn between the upper and lower 

8 lobes of each ear and shall be positioned where the external ear connects to the head. A template and an example are 

9 shown in Figure I2. For other poses, the composition shall be rotated about an imaginary axis extending from the top of 

10 the head though the base of the neck. 

11 This composition is applied to SAP level 51. 

12 

262 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

a. A template of the “head only” b. An example “head only” 

photo. The width of the head is 7/10th photo. 

the width of the photo. 

1 Figure I2 – A facial image template and an example image that meets “Head Only” (level 51) scene constraints. 

2 

3 Head centering 

4 For the frontal pose, the face shall be positioned to satisfy all of the following conditions: 

5 The approximate horizontal mid-points of the mouth and of the bridge of the nose shall lie on an imaginary vertical straight 

6 line positioned at the horizontal center of the image. 

7 An imaginary horizontal line through the center of the subject's eyes shall be located at approximately the 55% point of 

8 the vertical distance up from the bottom edge of the captured image. 

9 For non-frontal pose, the subject shall satisfy these conditions when the head is rotated about an axis though the head 

10 and torso from the current pose back to center (zero angles) pose. 

11 Visibility of Ears 

12 The ear(s) shall be visible in frontal, profile and angled views for both “Head and Shoulders” and “Head Only” scene 

13 compositions. The hair shall be pushed back or tied behind the ears when appropriate. 

14 From the 50/51 level description: 

15 If hair covers the ears, then when possible, two photographs should be captured – one with hair in its normal state, and 

16 one with hair pulled back behind the ears. 

263 
 

1 Facial expression 

2 The expression should be neutral (non-smiling) with both eyes open normally (i.e. not wide-open), and mouth closed. 

3 Every effort should be made to have supplied images conform with this specification. A smile with closed jaw is not 

4 recommended. 

5 Eyeglasses 

6 For subjects who normally wear eyeglasses, every effort should be made to capture the mugshots with the glasses on. If 

7 significant glare in the glasses is evident in the photograph, then a second frontal mugshot image should be captured of 

8 the subject without glasses. Specification of eyeglasses in the SXS field is required. 

9 Eye patches 

10 The wearing of eye patches is allowed only for medical reasons. In these cases, the specification of the patch, in the SXS 

11 field is required. 

12 Background 

13 The subject whose image is being captured shall be positioned in front of a background which is 18% gray with a plain 

14 smooth flat surface. A Kodak or other neutral gray card or densitometer shall be used to verify this 18% gray reflectance 

15 requirement. 

16 The boundary between the head and the background should be clearly identifiable about the entire subject (very large 

17 volume hair excepted). There should be no shadows visible on the background behind the face image. 

18 Photographic Requirements 

19 Depth of field 

20 The subject's captured facial image shall always be in focus from the nose to the ears. Although this may result in the 

21 background behind the subject being out of focus, this is not a problem14 . It is recommended that auto-focus on the 

22 central part of face be used with digital camera photography. 

23 Subject lighting 

24 Lighting shall be equally distributed on the face. There shall be no significant direction of the light from the point of view of 

25 the photographer. 

26 The region of the face, from the crown to the base of the chin, and from ear-to-ear, shall be clearly visible and free of 

27 shadows. In particular, there shall be no dark shadows in the eye-sockets due to the brow and the iris and pupil of the 

28 eyes shall be clearly visible. 

29 Subject illumination can be accomplished using three point balanced illumination sources. A single bare “point” light 

30 source, such as a camera flash, is not acceptable for imaging. 

31 Appropriate diffusion techniques shall be employed to eliminate hot spots on the facial image. These hot spots usually 

32 appear on reflective areas such as cheeks and foreheads. 

 

14 For optimum quality of the captured mugshot, the f-stop of the lens should be set at two f-stops below the maximum aperture opening when possible. 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

264 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Background lighting 

2 Proper lighting shall contribute to the uniformity of illumination of the background, and the background shall be free of 

3 shadows. 

4 Exposure calibration 

5 The exposure shall be keyed to the background. Several areas of the recorded 18% gray background shall be used to 

6 verify the proper exposure. The averages of the 8-bit Red, Green, and Blue (RGB) components within each area shall be 

7 calculated. Each of the RGB means shall fall between 105 and 125 with a standard deviation of plus or minus 10. 

8 Furthermore, for every area examined, the maximum difference between the means of any two of the RGB components 

9 shall not exceed 10. 

10 No saturation 

11 For each patch of skin on the person’s face, the gradations in textures shall be clearly visible. In this sense, there will be 

12 no saturation (over or under exposure) on the face. 

13 No unnatural color or “red-eye” 

14 Unnaturally colored lighting (e.g. yellow, red) is not allowed. Care shall be taken to correct the "white balance" of image 

15 capture devices. The lighting shall produce a face image with natural looking flesh tones when viewed in typical 

16 examination environments. “Red-eye” is not acceptable. 

17 No color or grayscale enhancement 

18 A process that overexposes or under-develops a color or grayscale image for purposes of beauty enhancement or artistic 

19 pleasure is not allowed. The full spectrum shall be represented on the face image where appropriate. Teeth and whites 

20 of eyes shall be clearly light or white (when appropriate) and dark hair or features (when appropriate) shall be clearly dark. 

21 No unnatural radial distortion of the camera lens, resulting in a diagonal angle of view of approximately 20 to 28 degrees 

22 Fish eye effect, a type of distortion where central objects of the image erroneously appear closer than those at the edge, 

23 typically resulting in what appear to be unusually large noses in the image, is not allowed. While some distortion is almost 

24 always present during portrait photography, that distortion should not be noticeable by human examination. 

25 For a typical photo capture system with a subject 1.5 to 2.5 meters from the camera, the focal length of the camera lens 

26 should be that of a medium telephoto lens. For 35 mm photography this means that the focal length should be between 

27 90 mm and 130 mm. For other negative formats/sensors the recommended focal length is 2 to 3 times the diagonal of the 

28 negative/sensor 

29 Digital Requirements 

30 Pixel aspect ratio 

31 Digital cameras and scanners used to capture facial images shall use square pixels with a pixel aspect ratio of 1:1 

32 Image aspect ratio 

33 The Width:Height (i.e., HLL:VLL) aspect ratio of the captured image shall be 3:4. This corresponds to commonly used 

34 format sizes such as 600 x 800, 768x1024, etc., allowing for a COTS digital camera to be used for capture. 

35 No interlacing 

265 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Interlaced video frames are not allowed and all interlacing must be absent (not simply removed, but absent). 

2 No digital zoom 

3 The use of digital zoom (interpolation) to achieve specified resolution associated with Subject Application Profiles. 

4 Image Compression 

5 Non-frontal facial images shall be compressed using JPEG 2000 (JPEG is not allowed) meeting the maximum 

6 compression limits specified below. 

7 There shall be one frontal facial image compressed using lossless JPEG 2000. If multiple frontal images are in the 

8 transaction, then one image must be compressed via lossless compression and the others can be compressed either 

9 using lossless JPEG 2000 or lossy JPEG 2000 that meets the maximum compression limits specified below. The best 

10 practice is to apply the lossless compression to the frontal image meeting the “Ears Visible” constraint. 

11 The maximum compression ratio for both JPEG and JPEG 2000 of a rectangular region containing any exposed skin of 

12 the face, from crown to chin and ear to ear, shall be at most 15:1. This requirement is derived from studies of face 

13 algorithm matching at high and low resolutions. The non-facial portion of the mugshot, as well as the SMT Type-10 

14 record, can be compressed up to a ratio of 120:1. 

15 For JPEG, reference [14] provides source code to implement compression with both ROI and fixed compression ratios. 

16 For JPEG 2000, these capabilities are built into the implementation. 

17 For both JPEG and JPEG 2000, care must be taken to account for automatic compression by camera hardware. Multiple 

18 compression stages can damage the quality of photographic data. When possible, minimum compression (highest 

19 resolutions) should be applied at the camera level when external software performs the final (15:1 or less) compression 

20 stage. 

21 The table on the following page provides the the typical size of a single facial photograph using the compression 

22 recommendations contained in this section for levels 30 and 40, 50, and 51. . We assume that the image is formated as 

23 RGB888 (8 bits per color chanel per pixel). For levels 30 and 40, we also estimate that since the face width is 50% of the 

24 image width, then the area taken by the face is 25% of the total image area. SAP levels 50 and 51 include the constraint 

25 of lossless compression for the frontal pose facial image as discussed above. 

26 Allowed color space 

27 A full color image shall be captured. To ensure that color images exchanged between differing systems can be correctly 

28 displayed or printed, images shall be converted to the device-independent color space, sRGB. 

29 

30 Example File Sizes after compression 

Level Minimum WxH Uncompressed 

Size (RGB888) 

Size @ 2:1 

Lossless 

Compression 

Size @ 15:1 

compression for 

the entire image 

Size @ 15:1 

compression for the 

face and 120:1 for 

the background 

30 480x600 844 KB 58 KB 19.34 KB 

40 768x1024 2.3 MB 156 KB 52.8 KB 

50 3300x4400 42.5MB 14.2 MB 

266 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

51 2400x3200 22.5 MB 7.5 MB 

1 

2 Format Requirements 

3 Subject Pose (POS) and Subject pose angles (SPA) 

4 One of either the POS or SPA fields shall be used to denote pose angles. 

5 The POS field code values “F”, “R”, and “L” can be used for images in which the Pitch and Roll angles are 0 and the Yaw 

6 angle is 0, 90, and -90 respectively. (The sign of the Yaw angle in the previous sentence corresponds to the field 10.020 

7 convention where a right profile is when the subject turns to the left). 

8 The SPA field 10.025 can be used for the above poses and shall be used for all other angled poses. The POS field 

9 10.020 shall then be of type code “D”, for determined 3D pose, instructing the user to use 10.025 as the reference for 

10 pose angles. (For example, a 3⁄4 profile capture would require a POS field entry of “D” with the angle specified in the SPA 

11 field.) 

12 In all cases, the uncertainty in the Yaw pose angle determination shall be less than 5 degrees of the frontal photograph, 

13 and 10 degrees in the non-frontal photographs. The uncertainty in the Pitch and Roll angles shall be less than 5 degrees. 

14 Subject facial description (SXS) 

15 The Subject facial description field shall be present in the transaction when one or more of the facial attributes given by 

16 the type codes of 10.026 is present in the image. 

17 Subject hair color (SHC) 

18 The Subject hair color field shall be present in the transaction. The code “UNSPECIFIED” for this field is not allowed. 

19 Subject eye color (SEC) 

20 The Subject eye color field shall be present in the transaction. The code “UNSPECIFIED” for this field is not allowed. 

267 
 

1 Annex J Face-Pose Values 

2 (Informative) 

3 

4 The definition and range of pose angles 

5 The Yaw and Roll angles shall be measured from the full face pose position and have a range of values from -180 

6 degrees to +180 degrees. The Pitch angle shall have a range of values from -90 degrees to +90 degrees. The pose angle 

7 set is given by Tait-Bryan angles. 

8 Yaw angle: rotation about the vertical (y) axis. A positive Yaw angle is used to express the angular offset as the subject 

9 rotates from a full-face pose to their left (approaching a right profile). A negative Yaw angle is used to express the angular 

10 offset as the subject rotates from a full-face pose to their right (approaching a left profile). 

11 Pitch angle: rotation about the horizontal side-to-side (x) horizontal axis. 

12 Roll angle: rotation about the horizontal back to front (z) axis. 

13 

14 The angles are defined relative to the frontal view of the subject, which has angles (0, 0, 0) as shown in Figure J1. 

15 Examples are shown in Figure J2. 

16 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

17 Figure J1 – The definition of pose angle set is with respect to the frontal view of the subject. 

18 

268 
 

 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

A B C d e f g 

1 Figure J2 – Examples of pose angles and their encodings. The pose angles (Y, P, R) of Figures (a) – (g) are given 

2 by (0, 0, 0), (+45, 0, 0), (-45, 0, 0), (0, -45, 0), (0, +45, 0), (0, 0, -45), and (0, 0, +45), respectively. 

3 The uncertainty in the pose angles is given by the range 0 to 90 inclusive. It shall denote approximately a maximum value 

4 of possible deviation in the measurement of the pose. This shall correspond to a two standard deviation confidence 

5 interval. 

6 The encoding of angles is in ASCII format, with the minus sign “-“ used to denote a negative value and the plus “+” sign 

7 optionally used to denote a positive value. Pose angle uncertainty angles always are positive. 

8 The order of rotation through pose angles 

9 As order of the successive rotation around the different axes does matter, the encoded rotation angle shall correspond to 

10 an order of execution starting from the frontal view. This order shall be given by Roll (about the front axis), then Pitch 

11 (about the horizontal axis) and finally Yaw (about the vertical axis). The (first executed) Roll transformation will therefore 

12 always be in the image (x, y) plane. Examples are shown in Figure J3. 

13 From the point of view of executing a transformation from the observed view to a frontal view, the transformation order will 

14 therefore be Yaw, Pitch, and then Roll. Note however that the encoded angle is from the frontal view to the observed 

15 view. 

269 
 

1 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

 (Y, P, R)=(0, 0, +45) (Y, P, R)=(0,-30, +45) (Y, P, R)=(-45, -30, +45) 

A B c 

(Y, P, R)=(0, 0, -30) (Y, P, R)=(0, +20, -30) (Y, P, R)=(-30, +20, -30) 

D E F 

2 Figure J3 – Examples of the order of rotation through pose angles with an origin of coordinate system at the 

3 nose tip. Figures (a)-(c) show three successive rotation steps to achieve the pose angles (Y, P, R) of (-45, -30, 

4 +45). Figures (d)-(f) show three successive rotation steps to achieve the pose angles (Y, P, R) of (-30, +20, -30). 

270 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

Annex K Bibliography 

(Informative) 

AAMVA, Personal Identification – AAMVA International Specification – DL/ID Card Design, March 2005. 

ANSI INCITS 379-2004, Iris Image Interchange Format. 

ANSI INCITS 385-2004, Face Recognition Format for Data Interchange. 

ISO/IEC 19794-5 Information technology - Biometric data interchange formats - Part 5: Face image data. 

ISO/IEC 19794-6 Information technology - Biometric data interchange formats - Part 6: Iris image data. 

NIST SP 800-76, Biometric Data Specification for Personal Identity Verification, February 2006. 

271 
Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

1 Annex L Constraint Schema 

2 (Normative) 

3 

4 Constraints to an implementer’s ansi-nist.xsd subset schema should be based on the ANSI/NIST constraint schema 

5 presented here in this annex (“ansi-nist_itl_constraint.xsd”). Changes must be made to the minOccurs and maxOccurs. 

6 

7 

8 

9 <?xml version="1.0" encoding="UTF-8"?>

10 <xsd:schema targetNamespace="http://niem.gov/niem/ansi-nist/2.0" version="1" 

11 xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema" 

12 xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:ansi-nist="http://niem.gov/niem/ansi-nist/2.0" 

13 xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:fbi="http://niem.gov/niem/fbi/2.0" 

14 xmlns:i="http://niem.gov/niem/appinfo/2.0"> 

15 <!-- ======================================================= --> 

16 <!-- ==This file is modified from the NIEM ansi-nist.xsd to constrain ====== --> 

17 <!-- ==the occurrences of elements and enforce, where possible the ===== -->

18 <!-- ==mandatory/optional rules of the ANSI/NIST-ITL 1-2007 standard. === -->

19 <!-- ==Comments have been added to assist implementers converting === -->

20 <!-- ==from the Part 1 version. =================================== --> 

21 <!-- ======================================================= --> 

22 <xsd:annotation> 

23 <xsd:documentation>ANSI/NIST Fingerprint and Biometric standard.</xsd:documentation>

24 <xsd:appinfo>

25 <i:ConformantIndicator>true</i:ConformantIndicator>

26 </xsd:appinfo>

27 </xsd:annotation>

28 <xsd:import schemaLocation="../../structures/2.0/structures.xsd"

29 namespace="http://niem.gov/niem/structures/2.0"/>

30 <xsd:import schemaLocation="../../appinfo/2.0/appinfo.xsd"

31 namespace="http://niem.gov/niem/appinfo/2.0"/>

32 <xsd:import schemaLocation="../../fbi/2.0/fbi.xsd" namespace="http://niem.gov/niem/fbi/2.0"/>

33 <xsd:import schemaLocation="../../niem-core/2.0/niem-core.xsd"

34 namespace="http://niem.gov/niem/niem-core/2.0"/>

35 <xsd:import schemaLocation="../../proxy/xsd/2.0/xsd.xsd"

36 namespace="http://niem.gov/niem/proxy/xsd/2.0"/>

37 <!-- ======================================================= --> 

38 <xsd:simpleType name="ALSCodeSimpleType">

39 <xsd:annotation> 

40 <xsd:appinfo>

41 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

42 </xsd:appinfo>

43 </xsd:annotation>

44 <xsd:restriction base="xsd:token"> 

45 <xsd:enumeration value="NIR"> 

46 <xsd:annotation> 

47 <xsd:documentation>Near-infrared illumination (~700-850nm) </xsd:documentation>

48 </xsd:annotation>

49 </xsd:enumeration>

50 <xsd:enumeration value="VIS"> 

51 <xsd:annotation> 

52 <xsd:documentation>Visible full-spectrum illumination (~380-740nm)</xsd:documentation>

53 </xsd:annotation>

54 </xsd:enumeration>

55 </xsd:restriction>

56 </xsd:simpleType>

57 <xsd:complexType name="ALSCodeType"> 

272 
 

1 <xsd:annotation> 

2 <xsd:appinfo>

3 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

4 </xsd:appinfo>

5 </xsd:annotation>

6 <xsd:simpleContent>

7 <xsd:extension base="ansi-nist:ALSCodeSimpleType">

8 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

9 </xsd:extension>

10 </xsd:simpleContent>

11 </xsd:complexType>

12 <!-- ======================================================= --> 

13 <!-- =====================================================not used ========================= --> 

14 <!-- ======================================================= --> 

15 <xsd:complexType name="ActivityAugmentationType">

16 <xsd:annotation> 

17 <xsd:documentation>A data type for additional information about an

18 activity.</xsd:documentation>

19 <xsd:appinfo>

20 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="AugmentationType"/>

21 </xsd:appinfo>

22 </xsd:annotation>

23 <xsd:complexContent>

24 <xsd:extension base="s:AugmentationType">

25 <xsd:sequence>

26 <xsd:element ref="ansi-nist:ActivityAgencyNotificationIndicator" minOccurs="0"

27 maxOccurs="unbounded"/>

28 <xsd:element ref="ansi-nist:ActivityApprovalDate" minOccurs="0" maxOccurs="unbounded"/>

29 <xsd:element ref="ansi-nist:ActivityEndTimeZoneCode" minOccurs="0" maxOccurs="unbounded"/>

30 <xsd:element ref="ansi-nist:ActivityTimeZoneCode" minOccurs="0" maxOccurs="unbounded"/>

31 </xsd:sequence>

32 </xsd:extension>

33 </xsd:complexContent>

34 </xsd:complexType>

35 <!-- ======================================================= --> 

36 <xsd:simpleType name="BTYCodeSimpleType">

37 <xsd:annotation> 

38 <xsd:appinfo>

39 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

40 </xsd:appinfo>

41 </xsd:annotation>

42 <xsd:restriction base="xsd:token"> 

43 <xsd:enumeration value="0"> 

44 <xsd:annotation> 

45 <xsd:documentation>No information given</xsd:documentation>

46 </xsd:annotation>

47 </xsd:enumeration>

48 <xsd:enumeration value="1"> 

49 <xsd:annotation> 

50 <xsd:documentation>Multple biometrics used</xsd:documentation>

51 </xsd:annotation>

52 </xsd:enumeration>

53 <xsd:enumeration value="10"> 

54 <xsd:annotation> 

55 <xsd:documentation>Iris</xsd:documentation>

56 </xsd:annotation>

57 </xsd:enumeration>

58 <xsd:enumeration value="100"> 

59 <xsd:annotation> 

60 <xsd:documentation>Keystroke dynamics</xsd:documentation>

61 </xsd:annotation> 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

273 
 

1 </xsd:enumeration>

2 <xsd:enumeration value="1000"> 

3 <xsd:annotation> 

4 <xsd:documentation>Gait</xsd:documentation>

5 </xsd:annotation>

6 </xsd:enumeration>

7 <xsd:enumeration value="10000"> 

8 <xsd:annotation> 

9 <xsd:documentation>Finger geometry</xsd:documentation>

10 </xsd:annotation>

11 </xsd:enumeration>

12 <xsd:enumeration value="2"> 

13 <xsd:annotation> 

14 <xsd:documentation>Facial features</xsd:documentation>

15 </xsd:annotation>

16 </xsd:enumeration>

17 <xsd:enumeration value="20"> 

18 <xsd:annotation> 

19 <xsd:documentation>Retina</xsd:documentation>

20 </xsd:annotation>

21 </xsd:enumeration>

22 <xsd:enumeration value="200"> 

23 <xsd:annotation> 

24 <xsd:documentation>Lip movement</xsd:documentation>

25 </xsd:annotation>

26 </xsd:enumeration>

27 <xsd:enumeration value="2000"> 

28 <xsd:annotation> 

29 <xsd:documentation>Body odor</xsd:documentation>

30 </xsd:annotation>

31 </xsd:enumeration>

32 <xsd:enumeration value="20000"> 

33 <xsd:annotation> 

34 <xsd:documentation>Palm print</xsd:documentation>

35 </xsd:annotation>

36 </xsd:enumeration>

37 <xsd:enumeration value="4"> 

38 <xsd:annotation> 

39 <xsd:documentation>Voice</xsd:documentation>

40 </xsd:annotation>

41 </xsd:enumeration>

42 <xsd:enumeration value="40"> 

43 <xsd:annotation> 

44 <xsd:documentation>Hand geometry</xsd:documentation>

45 </xsd:annotation>

46 </xsd:enumeration>

47 <xsd:enumeration value="400"> 

48 <xsd:annotation> 

49 <xsd:documentation>Thermal face image</xsd:documentation>

50 </xsd:annotation>

51 </xsd:enumeration>

52 <xsd:enumeration value="4000"> 

53 <xsd:annotation> 

54 <xsd:documentation>DNA</xsd:documentation>

55 </xsd:annotation>

56 </xsd:enumeration>

57 <xsd:enumeration value="40000"> 

58 <xsd:annotation> 

59 <xsd:documentation>Vein pattern</xsd:documentation>

60 </xsd:annotation>

61 </xsd:enumeration> 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

274 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:enumeration value="8"> 

<xsd:annotation> 

<xsd:documentation>Fingerprint</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="80"> 

<xsd:annotation> 

<xsd:documentation>Signature dynamics</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="800"> 

<xsd:annotation> 

<xsd:documentation>Thermal hand image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="8000"> 

<xsd:annotation> 

<xsd:documentation>Ear shape</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="80000"> 

<xsd:annotation> 

<xsd:documentation>Foot print</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="BTYCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:BTYCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="CBEFFImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<!-- =====================================================fieldID="99.103" 

fieldMnemonic="BFO" == --> 

<xsd:element ref="ansi-nist:CBEFFFormatOwnerIdentification"/>

<!-- =====================================================fieldID="99.104" 

fieldMnemonic="BFT" == --> 

<xsd:element ref="ansi-nist:CBEFFFormatCategoryIdentification"/>

<!-- =====================================================fieldID="99.100" 

fieldMnemonic="HDV" == --> 

<xsd:element ref="ansi-nist:CBEFFVersionIdentification"/>

<!-- =====================================================fieldID="99.101" 

fieldMnemonic="BTY" == --> 

<xsd:element ref="ansi-nist:CBEFFCategoryCode"/> 

275 
 

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="COLCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="BLACK"> 

<xsd:annotation> 

<xsd:documentation>Black</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLUE"> 

<xsd:annotation> 

<xsd:documentation>Blue</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BROWN"> 

<xsd:annotation> 

<xsd:documentation>Brown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GRAY"> 

<xsd:annotation> 

<xsd:documentation>Gray</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GREEN"> 

<xsd:annotation> 

<xsd:documentation>Green</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MULTI"> 

<xsd:annotation> 

<xsd:documentation>Multi</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ORANGE"> 

<xsd:annotation> 

<xsd:documentation>Orange</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="OUTLINE"> 

<xsd:annotation> 

<xsd:documentation>Outline</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PURPLE"> 

<xsd:annotation> 

<xsd:documentation>Purple</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RED"> 

<xsd:annotation> 

<xsd:documentation>Red</xsd:documentation>

</xsd:annotation> 

276 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:enumeration>

<xsd:enumeration value="WHITE"> 

<xsd:annotation> 

<xsd:documentation>White</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="YELLOW"> 

<xsd:annotation> 

<xsd:documentation>Yellow</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="COLCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:COLCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="CSICodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>ASCII 7-bit English</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>ASCII 8-bit Latin</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>UNICODE 16-bit</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="3"> 

<xsd:annotation> 

<xsd:documentation>UTF 8-bit</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="CSICodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation> 

277 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:simpleContent>

<xsd:extension base="ansi-nist:CSICodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="CSNCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="ASCII 7-bit English">

<xsd:annotation> 

<xsd:documentation>American Standard Code for Information Interchange is a code

representing English characters as numbers</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ASCII 8-bit Latin"> 

<xsd:annotation> 

<xsd:documentation>Larger character set of ASCII code to represent non-English

characters</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNICODE 16-bit"> 

<xsd:annotation> 

<xsd:documentation>Unicode provides a unique number for every character, no matter what

platform, program, and language</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UTF 8-bit"> 

<xsd:annotation> 

<xsd:documentation>Unicode Transformation Format whose initial encoding is consistent with

ASCII</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="CSNCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:CSNCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="CSPCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="GRAY"> 

278 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Grayscale, monochrome</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RGB"> 

<xsd:annotation> 

<xsd:documentation>Undetermined color space for an RGB image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SRGB"> 

<xsd:annotation> 

<xsd:documentation>sRGB IEC 61966-2-1</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SYCC"> 

<xsd:annotation> 

<xsd:documentation>YCbCr JPEG 2000 compressed</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNK"> 

<xsd:annotation> 

<xsd:documentation>Undefined</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="YCC"> 

<xsd:annotation> 

<xsd:documentation>YCbCr legacy</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="CSPCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:CSPCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="ContentRecordType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:ImageReferenceIdentification"/>

<xsd:element ref="ansi-nist:RecordCategoryCode"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="DMMCodeSimpleType"> 

279 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="ASSISTED"> 

<xsd:annotation> 

<xsd:documentation>Assisted</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="OBSERVED"> 

<xsd:annotation> 

<xsd:documentation>Observed</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNATTENDED"> 

<xsd:annotation> 

<xsd:documentation>Unattended</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNKNOWN"> 

<xsd:annotation> 

<xsd:documentation>Unknown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="DMMCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:DMMCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="FEFCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="FV0"> 

<xsd:annotation> 

<xsd:documentation>All fingers within EJI</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV1"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV2"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation> 

280 
 

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV3"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV4"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="FEFCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:FEFCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="FERCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="DST"> 

<xsd:annotation> 

<xsd:documentation>Distal Segment</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="EJI"> 

<xsd:annotation> 

<xsd:documentation>Entire Joint Image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV1"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV2"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV3"> 

<xsd:annotation> 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FV4"> 

<xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

281 
 

<xsd:documentation>Single Full Finger View</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MED"> 

<xsd:annotation> 

<xsd:documentation>Medial Segment</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PRX"> 

<xsd:annotation> 

<xsd:documentation>Proximal Segment</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TIP"> 

<xsd:annotation> 

<xsd:documentation>Rolled Tip</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="FERCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:FERCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="FIDCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Undefined</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Right eye</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>Left eye</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="FIDCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

282 
 

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:FIDCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="FMTCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="S"> 

<xsd:annotation> 

<xsd:documentation>Standard descriptions</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="U"> 

<xsd:annotation> 

<xsd:documentation>Vendor specific, or M1-378 descriptions</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="FMTCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:FMTCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="FPCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Unknown, or every finger 1-10</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation> Right thumb</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="10"> 

<xsd:annotation> 

<xsd:documentation> Left little</xsd:documentation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

283 
 

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="11"> 

<xsd:annotation> 

<xsd:documentation> Plain right thumb</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="12"> 

<xsd:annotation> 

<xsd:documentation> Plain left thumb</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="13"> 

<xsd:annotation> 

<xsd:documentation> Plain right four</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="14"> 

<xsd:annotation> 

<xsd:documentation> Plain left four</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="15"> 

<xsd:annotation> 

<xsd:documentation> Left and right thumbs</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="19"> 

<xsd:annotation> 

<xsd:documentation> Complete friction ridge exemplars</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation> Right index</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="255"> 

<xsd:annotation> 

<xsd:documentation> Unused field value in record types 3-6</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="3"> 

<xsd:annotation> 

<xsd:documentation> Right middle</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="4"> 

<xsd:annotation> 

<xsd:documentation> Right ring</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="5"> 

<xsd:annotation> 

<xsd:documentation> Right little</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="6"> 

<xsd:annotation> 

<xsd:documentation> Left thumb</xsd:documentation>

</xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

284 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:enumeration>

<xsd:enumeration value="7"> 

<xsd:annotation> 

<xsd:documentation> Left index</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="8"> 

<xsd:annotation> 

<xsd:documentation> Left middle</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="9"> 

<xsd:annotation> 

<xsd:documentation> Left ring</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="FPCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:FPCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FaceImage3DPoseAngleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="xsd:token"> 

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FaceImageAttributeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:FaceImageAttributeAbstract" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FaceImageFeaturePointType"> 

285 
 

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:FeaturePointHorizontalCoordinateValue"/>

<xsd:element ref="ansi-nist:FeaturePointIdentification"/>

<xsd:element ref="ansi-nist:FeaturePointCategory"/>

<xsd:element ref="ansi-nist:FeaturePointVerticalCoordinateValue"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FaceImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<!-- =====================================================fieldID="10.025" 

fieldMnemonic="SPA" == --> 

<xsd:element ref="ansi-nist:FaceImage3DPoseAngle" minOccurs="0"/>

<!-- =====================================================fieldID="10.013" 

fieldMnemonic="SAP" == --> 

<xsd:element ref="ansi-nist:FaceImageAcquisitionProfile"/>

<!-- =====================================================fieldID="10.022" 

fieldMnemonic="PXS" == --> 

<xsd:element ref="ansi-nist:FaceImageAttribute" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================fieldID="10.026" 

fieldMnemonic="SXS" == --> 

<xsd:element ref="ansi-nist:FaceImageDescription" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================fieldID="10.027" 

fieldMnemonic="SEC" == --> 

<xsd:element ref="ansi-nist:FaceImageEyeColorAttribute" minOccurs="0"/>

<!-- =====================================================fieldID="10.029" 

fieldMnemonic="SFP" == --> 

<xsd:element ref="ansi-nist:FaceImageFeaturePoint" minOccurs="0" maxOccurs="88"/>

<!-- =====================================================fieldID="10.028" 

fieldMnemonic="SHC" == --> 

<xsd:element ref="ansi-nist:FaceImageHairColorAttribute" minOccurs="0" maxOccurs="2"/>

<!-- =====================================================fieldID="10.021" 

fieldMnemonic="POA" == --> 

<xsd:element ref="ansi-nist:FaceImagePoseOffsetAngleMeasure" minOccurs="0"/>

<!-- =====================================================fieldID="10.020" 

fieldMnemonic="POS" == --> 

<xsd:element ref="ansi-nist:FaceImageSubjectPose" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintImageMajorCasePrintType">

<xsd:annotation> 

<xsd:appinfo> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

286 
 

<i:Base i:name="FingerprintType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:FingerprintType">

<xsd:sequence>

<!-- =====================================================fieldID="14.014" 

fieldMnemonic="PPD" == --> 

<!-- ==FingerPositionCode is used from the base FingerprintType == -->

<xsd:element ref="ansi-nist:MajorCasePrintCode" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================fieldID="14.015" 

fieldMnemonic="PPC" == --> 

<xsd:element ref="ansi-nist:MajorCasePrintSegmentOffset" minOccurs="0"

maxOccurs="unbounded"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:MajorCasePrintText" minOccurs="0" maxOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintImageNISTQualityType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerprintType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:FingerprintType">

<xsd:sequence>

<xsd:element ref="ansi-nist:NISTQualityMeasure"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintImageQualityType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerprintType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:FingerprintType">

<xsd:sequence>

<xsd:element ref="ansi-nist:QualityAlgorithmProductIdentification"/>

<xsd:element ref="ansi-nist:QualityAlgorithmVendorIdentification"/>

<xsd:element ref="ansi-nist:QualityValue"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ansi-nist:FingerprintImageType has been replaced by itl:FingerprintImageType -->

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

287 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<xsd:element ref="ansi-nist:FingerprintImageMajorCasePrint" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:FingerprintImagePosition" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:FingerprintImageSegmentationQuality" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- Just as <ansi-nist:FingerprintType> is a base for <ansi-nist:FingerprintImageQualityType>, -

-> 

<!-- the element below is a base for <itl:PalmprintImageQualityType, -->

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintPalmImagePositionType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerprintType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:FingerprintType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PalmPosition" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintPatternType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PatternCodeSourceCode" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PatternCorePosition" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PatternDeltaPosition" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PatternNISTStandardText" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PatternUserText" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="FingerprintType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation> 

288 
 

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<!-- =====================================================Types 03-06

===fieldMnemonic="FGP" == --> 

<!-- =====================================================fieldID="14.014" 

fieldMnemonic="PPD" == --> 

<!-- =====================================================fieldID="14.022" 

fieldMnemonic="NQM" == -->

<!-- =====================================================fieldID="14.023" 

fieldMnemonic="SQM" == -->

<!-- =====================================================fieldID="14.024" 

fieldMnemonic="FQM" == -->

<!-- ===<ansi-nist:MajorCasePrintSegmentOffset> is based on this type, but uses none of

the components == -->

<xsd:element ref="ansi-nist:FingerPositionCode" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:FingerPositionIndicator" minOccurs="0" maxOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="GCACodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>NONE - Uncompressed</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>WSQ - Wavelet Scalar Quantization</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>JPEGB - Baseline mode of the JPEG algorithm used to compress an

image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="3"> 

<xsd:annotation> 

<xsd:documentation>JPEGL - Lossless mode of the JPEG algorithm used to compress an

image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="4"> 

<xsd:annotation> 

<xsd:documentation>JP2 - Lossy mode of the JPEG2000 algorithm used to compress an

image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="5"> 

<xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

289 
 

<xsd:documentation>JP2L - Lossless mode of the JPEG2000 algorithm used to compress an

image</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="6"> 

<xsd:annotation> 

<xsd:documentation>PNG - Portable Network Graphics image format</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="GCACodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:GCACodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="ICTCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Undefined</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Progressive</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>Interlace Frame</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="3"> 

<xsd:annotation> 

<xsd:documentation>Interlace Field</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="ICTCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:ICTCodeSimpleType"> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

290 
 

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="IMPCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Live-scan plain</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Live-scan rolled</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="10"> 

<xsd:annotation> 

<xsd:documentation>Live-scan palm</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="11"> 

<xsd:annotation> 

<xsd:documentation>NonLive-scan palm</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="12"> 

<xsd:annotation> 

<xsd:documentation>Latent palm impression</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="13"> 

<xsd:annotation> 

<xsd:documentation>Latent palm tracing</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="14"> 

<xsd:annotation> 

<xsd:documentation>Latent palm photo</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="15"> 

<xsd:annotation> 

<xsd:documentation>Latent palm lift</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>NonLive-scan plain</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="20"> 

<xsd:annotation> 

<xsd:documentation>Live-scan optical contact plain</xsd:documentation>

</xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

291 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:enumeration>

<xsd:enumeration value="21"> 

<xsd:annotation> 

<xsd:documentation>Live-scan optical contact rolled </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="22"> 

<xsd:annotation> 

<xsd:documentation>Live-scan non-optical contact plain</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="23"> 

<xsd:annotation> 

<xsd:documentation>Live-scan non-optical contact rolled</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="24"> 

<xsd:annotation> 

<xsd:documentation>Live-scan optical contactless plain</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="25"> 

<xsd:annotation> 

<xsd:documentation>Live-scan optical contactless rolled </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="26"> 

<xsd:annotation> 

<xsd:documentation>Live-scan non-optical contactless plain</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="27"> 

<xsd:annotation> 

<xsd:documentation>Live-scan non-optical contactless rolled</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="28"> 

<xsd:annotation> 

<xsd:documentation>Other</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="29"> 

<xsd:annotation> 

<xsd:documentation>Unknown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="3"> 

<xsd:annotation> 

<xsd:documentation>NonLive-scan rolled</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="4"> 

<xsd:annotation> 

<xsd:documentation>Latent impression</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="5"> 

<xsd:annotation> 

<xsd:documentation>Latent tracing</xsd:documentation>

</xsd:annotation>

</xsd:enumeration> 

292 
 

<xsd:enumeration value="6"> 

<xsd:annotation> 

<xsd:documentation>Latent photo</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="7"> 

<xsd:annotation> 

<xsd:documentation>Latent lift</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="8"> 

<xsd:annotation> 

<xsd:documentation>Live-scan vertical swipe</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="IMPCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:IMPCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="IMTCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="FACE"> 

<xsd:annotation> 

<xsd:documentation>Face</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MARK"> 

<xsd:annotation> 

<xsd:documentation>Mark</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SCAR"> 

<xsd:annotation> 

<xsd:documentation>Scar</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TATTOO"> 

<xsd:annotation> 

<xsd:documentation>Tattoo</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="IMTCodeType">

<xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

293 
 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:IMTCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="IOCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Undefined</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Base</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>Flipped</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="IOCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:IOCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="IRTCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Transaction information - ASCII</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="10"> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

294 
 

<xsd:annotation> 

<xsd:documentation>Facial & SMT image - ASCII/Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="13"> 

<xsd:annotation> 

<xsd:documentation>Variable-resolution latent image - ASCII/Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="14"> 

<xsd:annotation> 

<xsd:documentation>Variable-resolution fingerprint image -

ASCII/Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="15"> 

<xsd:annotation> 

<xsd:documentation>Variable-resolution palmprint Image - ASCII/Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="16"> 

<xsd:annotation> 

<xsd:documentation>User-defined variable-resolution testing Image -

ASCII/Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="17"> 

<xsd:annotation> 

<xsd:documentation>Iris image - ASCII/Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>User-defined descriptive text - ASCII</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="3"> 

<xsd:annotation> 

<xsd:documentation>Low-resolution grayscale fingerprint image - Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="4"> 

<xsd:annotation> 

<xsd:documentation>High-resolution grayscale fingerprint image -

Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="5"> 

<xsd:annotation> 

<xsd:documentation>Low-resolution binary fingerprint image - Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="6"> 

<xsd:annotation> 

<xsd:documentation>High-resolution binary fingerprint image - Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="7"> 

<xsd:annotation> 

<xsd:documentation>User-defined image - Binary</xsd:documentation>

</xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

295 
 

</xsd:enumeration>

<xsd:enumeration value="8"> 

<xsd:annotation> 

<xsd:documentation>Signature image - Binary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="9"> 

<xsd:annotation> 

<xsd:documentation>Minutiae data - ASCII</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="99"> 

<xsd:annotation> 

<xsd:documentation>CBEFF Biometric data record - ASCII/BInary</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="IRTCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:IRTCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="ISRCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Types 3 and 5, half minimum; Types 4, 6 and 8, minimum; Type 8

vector</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Types 3 and 5, half native; Types 4, 6, and 8 native

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="ISRCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:ISRCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

296 
 

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="IdentificationRangeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:MaximumRangeIdentification" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinimumRangeIdentification" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="ImageCaptureType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<!-- =====================================================fieldID="10.005" 

fieldMnemonic="PHD" == --> 

<!-- =====================================================fieldID="13.005" 

fieldMnemonic="LCD" == --> 

<!-- =====================================================fieldID="14.005" 

fieldMnemonic="FCD" == --> 

<!-- =====================================================fieldID="15.005" 

fieldMnemonic="PCD" == --> 

<!-- =====================================================fieldID="16.005" 

fieldMnemonic="UTD" == --> 

<!-- =====================================================fieldID="17.005" 

fieldMnemonic="ICD" == --> 

<!-- =====================================================fieldID="99.005" 

fieldMnemonic="BCD" == --> 

<xsd:element ref="ansi-nist:CaptureDate" minOccurs="0"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:CaptureDescription" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================fieldID="17.018" 

fieldMnemonic="GUI" == --> 

<xsd:element ref="ansi-nist:CaptureDeviceGlobalIdentification" minOccurs="0"/>

<!-- =====================================================fieldID="17.017" 

fieldMnemonic="DUI" == --> 

<xsd:element ref="ansi-nist:CaptureDeviceIdentification" minOccurs="0"/>

<!-- =====================================================fieldID="17.019" 

fieldMnemonic="MMS" == --> 

<xsd:element ref="ansi-nist:CaptureDeviceMakeText" minOccurs="0"/>

<xsd:element ref="ansi-nist:CaptureDeviceModelText" minOccurs="0"/>

<xsd:element ref="ansi-nist:CaptureDeviceSerialNumberText" minOccurs="0"/> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

297 
 

<!-- =====================================================fieldID="XX.016" 

fieldMnemonic="SHPS" == --> 

<xsd:element ref="ansi-nist:CaptureHorizontalPixelDensityValue" minOccurs="0"/>

<!-- =====================================================fieldID="XX.004" 

fieldMnemonic="SRC" == --> 

<xsd:element ref="ansi-nist:CaptureOrganization" minOccurs="0"/>

<!--

====================================================================fieldMnemonic="ISR" == --> 

<xsd:element ref="ansi-nist:CaptureResolution" minOccurs="0"/>

<!-- =====================================================fieldID="10.023" 

fieldMnemonic="PAS" == --> 

<xsd:element ref="ansi-nist:CaptureSource" minOccurs="0"/>

<!-- =====================================================fieldID="XX.017" 

fieldMnemonic="SVPS" == --> 

<xsd:element ref="ansi-nist:CaptureVerticalPixelDensityValue" minOccurs="0"/>

<!-- =====================================================fieldID="XX.030" 

fieldMnemonic="DMM" == --> 

<xsd:element ref="ansi-nist:CaptureDeviceMonitoringMode" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="ImageQualityType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:QualityAlgorithmProductIdentification" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:QualityValue" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:QualityMeasureVendorIdentification" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="IndicatorCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="false "> 

<xsd:annotation> 

<xsd:documentation>Indicates the record does not meet the 

specification</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="true "> 

<xsd:annotation> 

<xsd:documentation>Indicates the record meets the specification</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="unknown"> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

298 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Indicates it is not known if the record meets the 

specification</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="IndicatorCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:IndicatorCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="IrisImageCaptureType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="ImageCaptureType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:ImageCaptureType">

<xsd:sequence>

<!-- =====================================================fieldID="17.016" 

fieldMnemonic="IPC" == --> 

<xsd:element ref="ansi-nist:IrisImageHorizontalOrientation" minOccurs="0"/>

<xsd:element ref="ansi-nist:IrisImageScanCategory" minOccurs="0"/>

<xsd:element ref="ansi-nist:IrisImageVerticalOrientation" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ansi-nist:IrisImageType has been replaced by itl:IrisImageType -->

<!-- ======================================================= --> 

<xsd:complexType name="IrisImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<xsd:element ref="ansi-nist:IrisEyeColorAttributeCode" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:IrisEyePosition" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:IrisEyeRotationAngleMeasure" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:IrisEyeRotationUncertaintyValueText" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:IrisImageAcquisitionLightingSpectrumValue" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:IrisImageCapture" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence> 

299 
 

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="MILCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="A"> 

<xsd:annotation> 

<xsd:documentation>Army</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="F"> 

<xsd:annotation> 

<xsd:documentation>Air Force</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="G"> 

<xsd:annotation> 

<xsd:documentation>Coast Guard</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="M"> 

<xsd:annotation> 

<xsd:documentation>Marines</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="N"> 

<xsd:annotation> 

<xsd:documentation>Navy</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="MILCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:MILCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="MTCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="A"> 

<xsd:annotation> 

<xsd:documentation>Ridge ending</xsd:documentation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

300 
 

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="B"> 

<xsd:annotation> 

<xsd:documentation>Bifurcation</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="C"> 

<xsd:annotation> 

<xsd:documentation>Compound</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="D"> 

<xsd:annotation> 

<xsd:documentation>Undetermined</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="MTCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:MTCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="MajorCasePrintSegmentOffsetType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerprintType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:FingerprintType">

<xsd:sequence>

<xsd:element ref="ansi-nist:SegmentBottomVerticalCoordinateValue"/>

<xsd:element ref="ansi-nist:SegmentLocationCode"/>

<xsd:element ref="ansi-nist:SegmentFingerViewCode"/>

<!-- ===============not used======================================== --> 

<xsd:element ref="ansi-nist:SegmentFingerText" minOccurs="0" maxOccurs="0"/>

<!-- ======================================================= --> 

<xsd:element ref="ansi-nist:SegmentLeftHorizontalCoordinateValue"/>

<xsd:element ref="ansi-nist:SegmentRightHorizontalCoordinateValue"/>

<!-- ===============not used======================================== --> 

<xsd:element ref="ansi-nist:SegmentText" minOccurs="0" maxOccurs="0"/>

<!-- ======================================================= --> 

<xsd:element ref="ansi-nist:SegmentTopVerticalCoordinateValue"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- =======not used========================================= --> 

<!-- =======replaced, mainly by itl:MinutiaType ===================== -->

<!-- ======================================================= --> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

301 
 

<xsd:complexType name="MinutiaPositionType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PositionBottomCoordinateValue" minOccurs="0" 

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionDirectionDegreeValue" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue" minOccurs="0" 

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionThetaAngleMeasure" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionTopCoordinateValue" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionUncertaintyValue" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionVerticalCoordinateValue" minOccurs="0" 

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="MinutiaRidgeCountType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaPositionType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:MinutiaPositionType">

<xsd:sequence>

<xsd:element ref="ansi-nist:RidgeCountReferenceIdentification"/>

<xsd:element ref="ansi-nist:RidgeCountValue"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- =======not used========================================= --> 

<!-- =======replaced, mainly by itl:MinutiaType ===================== -->

<!-- ======================================================= --> 

<xsd:complexType name="MinutiaType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue" minOccurs="0" 

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:PositionVerticalCoordinateValue" minOccurs="0" 

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaIdentification" minOccurs="0" maxOccurs="unbounded"/> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

302 
 

<xsd:element ref="ansi-nist:PositionThetaAngleMeasure" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaPosition" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="MinutiaeFingerPatternType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:FingerPatternCodeSourceCode"/>

<xsd:element ref="ansi-nist:FingerPattern"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="MinutiaeFingerPositionType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue"/>

<xsd:element ref="ansi-nist:PositionVerticalCoordinateValue"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="MinutiaeReadingSystemType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:ReadingSystemCodingMethodCode"/>

<xsd:element ref="ansi-nist:ReadingSystemName"/>

<xsd:element ref="ansi-nist:ReadingSystemSubsystemIdentification" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ==ansi-nist:MinutiaeType has been replaced by itl:MinutiaeType====== -->

<!-- ======================================================= --> 

<xsd:complexType name="MinutiaeType">

<xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

303 
 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:MinutiaeNISTStandard" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeFingerCorePosition" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeFingerDeltaPosition" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeFingerPatternDetail" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeFormatNISTStandardIndicator" minOccurs="0" 

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeImpressionCaptureCategory" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeFingerPosition" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaePalmPosition" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="NISTImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/niem-core/2.0" i:name="ImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="nc:ImageType">

<xsd:sequence>

<!-- =====================================================fieldID="XX.012" 

fieldMnemonic="BPX" == --> 

<xsd:element ref="ansi-nist:ImageBitsPerPixelQuantity" minOccurs="0"/>

<!-- =====================================================fieldID="XX.005"=date, various

mnemonics --> 

<xsd:element ref="ansi-nist:ImageCaptureDetail" minOccurs="0"/>

<!-- =====================================================fieldID="XX.012" 

fieldMnemonic="CSP" == --> 

<xsd:element ref="ansi-nist:ImageColorSpace" minOccurs="0"/>

<!-- =====================================================fieldID="XX.020" 

fieldMnemonic="COM" == --> 

<!-- =====================================================fieldID="17.021" 

fieldMnemonic="COM" == --> 

<xsd:element ref="ansi-nist:ImageCommentText" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================fieldID="XX.011" 

fieldMnemonic="CGA" == --> 

<xsd:element ref="ansi-nist:ImageCompressionAlgorithm" minOccurs="0"/>

<!-- =====================================================fieldID="XX.006" 

fieldMnemonic="HLL" == --> 

<xsd:element ref="ansi-nist:ImageHorizontalLineLengthPixelQuantity" minOccurs="0"/>

<!-- =====================================================fieldID="XX.009" 

fieldMnemonic="HPS" == --> 

<xsd:element ref="ansi-nist:ImageHorizontalPixelDensityValue" minOccurs="0"/>

<!-- =====================================================fieldID="10.024" 

fieldMnemonic="SQS" == -->

<!-- =====================================================fieldID="16.024" 

fieldMnemonic="UQS" == --> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

304 
 

<!-- =====================================================fieldID="17.024" 

fieldMnemonic="IQS" == -->

<!-- =====================================================fieldID="99.102" 

fieldMnemonic="BDQ" == -->

<xsd:element ref="ansi-nist:ImageQuality" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:ImageRecordCategoryCode" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:ImageReferenceIdentification" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================fieldID="XX.008" 

fieldMnemonic="SLC" == --> 

<xsd:element ref="ansi-nist:ImageScaleUnitsCode" minOccurs="0"/>

<!-- =====================================================fieldID="10.003" 

fieldMnemonic="IMT" == --> 

<xsd:element ref="ansi-nist:ImageCategoryCode" minOccurs="0"/>

<!-- =====================================================fieldID="XX.007" 

fieldMnemonic="VLL" == --> 

<xsd:element ref="ansi-nist:ImageVerticalLineLengthPixelQuantity" minOccurs="0"/>

<!-- =====================================================fieldID="XX.010" 

fieldMnemonic="VPS" == --> 

<xsd:element ref="ansi-nist:ImageVerticalPixelDensityValue" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ==ansi-nist:NISTStandardMinutiaeType has been replaced by an itl: version == -->

<!-- ======================================================= --> 

<xsd:complexType name="NISTStandardMinutiaeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:MinutiaDetail" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeQuantity" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeReadingSystem" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaeRidgeCountIndicator" minOccurs="0"

maxOccurs="unbounded"/>

<!-- ======================================================= --> 

<!-- ==The three elements below belong in MinutiaType (singular)======= -->

<!-- ======================================================= --> 

<xsd:element ref="ansi-nist:MinutiaQualityValue" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaCategory" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:MinutiaRidgeCount" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="OFRCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

305 
 

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="A"> 

<xsd:annotation> 

<xsd:documentation>Automatic, human never involved</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="E"> 

<xsd:annotation> 

<xsd:documentation>Automatic, human edited</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="M"> 

<xsd:annotation> 

<xsd:documentation>Manual</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="U"> 

<xsd:annotation> 

<xsd:documentation>Automatic, human unneeded</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="OFRCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:OFRCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- =====not used=========================================== --> 

<!-- ======================================================= --> 

<xsd:complexType name="OrganizationDocumentCountType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:CodeManualCount" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:NewsletterCount" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:OperatingManualCount" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:TOUCount" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="PASCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

306 
 

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="ANALOGUE VIDEO"> 

<xsd:annotation> 

<xsd:documentation>Analogue Video</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DIGITAL CAMERA"> 

<xsd:annotation> 

<xsd:documentation>Digital Camera</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DIGITAL VIDEO"> 

<xsd:annotation> 

<xsd:documentation>Digital Video</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SCANNER"> 

<xsd:annotation> 

<xsd:documentation>Scanner</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNKNOWN"> 

<xsd:annotation> 

<xsd:documentation>Unknown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNKNOWN PHOTO"> 

<xsd:annotation> 

<xsd:documentation>Unknown Photo</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNKNOWN VIDEO"> 

<xsd:annotation> 

<xsd:documentation>Unknown Video</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNSPECIFIED"> 

<xsd:annotation> 

<xsd:documentation>Unspecified</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="VENDOR"> 

<xsd:annotation> 

<xsd:documentation>Vendor</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PASCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PASCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

307 
 

<!-- ======================================================= --> 

<xsd:simpleType name="PCCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="ABSTRACT"> 

<xsd:annotation> 

<xsd:documentation>Abstractions</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ANIMAL"> 

<xsd:annotation> 

<xsd:documentation>Animals and Animal Features</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FLAG"> 

<xsd:annotation> 

<xsd:documentation>Flags</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="HUMAN"> 

<xsd:annotation> 

<xsd:documentation>Human Forms and Features</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="OBJECT"> 

<xsd:annotation> 

<xsd:documentation>Objects</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="OTHER"> 

<xsd:annotation> 

<xsd:documentation>Other Images</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PLANT"> 

<xsd:annotation> 

<xsd:documentation>Plants</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SYMBOL"> 

<xsd:annotation> 

<xsd:documentation>Insignias & Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PCCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PCCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

308 
 

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="PCSCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="AW"> 

<xsd:annotation> 

<xsd:documentation>Accidental whorl</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CP"> 

<xsd:annotation> 

<xsd:documentation>Central pocket loop</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DL"> 

<xsd:annotation> 

<xsd:documentation>Double loop</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LS"> 

<xsd:annotation> 

<xsd:documentation>Left slant loop</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PA"> 

<xsd:annotation> 

<xsd:documentation>Plain arch </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PW"> 

<xsd:annotation> 

<xsd:documentation>Plain whorl</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RL"> 

<xsd:annotation> 

<xsd:documentation>Radial loop</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RS"> 

<xsd:annotation> 

<xsd:documentation>Right slant loop</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SR"> 

<xsd:annotation> 

<xsd:documentation>Scar</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TA"> 

<xsd:annotation> 

<xsd:documentation>Tented arch </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UL"> 

<xsd:annotation> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

309 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Ulnar loop</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UN"> 

<xsd:annotation> 

<xsd:documentation>Unknown or unclassifiable </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="WN"> 

<xsd:annotation> 

<xsd:documentation>Whorl, type not designated</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="XX"> 

<xsd:annotation> 

<xsd:documentation>Amputation</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PCSCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PCSCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="POSCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="A"> 

<xsd:annotation> 

<xsd:documentation>Angled</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="D"> 

<xsd:annotation> 

<xsd:documentation>Determined 3D</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="F"> 

<xsd:annotation> 

<xsd:documentation>Full face frontal </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="L"> 

<xsd:annotation> 

<xsd:documentation>Left profile 90 degree</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="R"> 

310 
 

<xsd:annotation> 

<xsd:documentation>Right profile 90 degree</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="POSCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:POSCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="PPCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="20"> 

<xsd:annotation> 

<xsd:documentation>Unknown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="21"> 

<xsd:annotation> 

<xsd:documentation>Right full</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="22"> 

<xsd:annotation> 

<xsd:documentation>Right writers</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="23"> 

<xsd:annotation> 

<xsd:documentation>Left full</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="24"> 

<xsd:annotation> 

<xsd:documentation>Left writers</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="25"> 

<xsd:annotation> 

<xsd:documentation>Right lower</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="26"> 

<xsd:annotation> 

<xsd:documentation>Right upper</xsd:documentation>

</xsd:annotation>

</xsd:enumeration> 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

311 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:enumeration value="27"> 

<xsd:annotation> 

<xsd:documentation>Left lower</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="28"> 

<xsd:annotation> 

<xsd:documentation>Left upper</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="29"> 

<xsd:annotation> 

<xsd:documentation>Right other</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="30"> 

<xsd:annotation> 

<xsd:documentation>Left other</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="31"> 

<xsd:annotation> 

<xsd:documentation>Right interdigital</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="32"> 

<xsd:annotation> 

<xsd:documentation>Right thenar</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="33"> 

<xsd:annotation> 

<xsd:documentation>Right hypothenar</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="34"> 

<xsd:annotation> 

<xsd:documentation>Left interdigital</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="35"> 

<xsd:annotation> 

<xsd:documentation>Left thenar</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="36"> 

<xsd:annotation> 

<xsd:documentation>Left hypothenar</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PPCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PPCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 

312 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="PPLCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="C"> 

<xsd:annotation> 

<xsd:documentation>Complete Shipment</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="P"> 

<xsd:annotation> 

<xsd:documentation>Partial Shipment</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PPLCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PPLCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="PSCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="ABBODY"> 

<xsd:annotation> 

<xsd:documentation>Abstract Body</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ABBPART"> 

<xsd:annotation> 

<xsd:documentation>Abstract Body Parts</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ABFACE"> 

<xsd:annotation> 

<xsd:documentation>Abstract Face</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ABSTRACT"> 

<xsd:annotation> 

<xsd:documentation>Abstract Animals</xsd:documentation> 

313 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ANKLET"> 

<xsd:annotation> 

<xsd:documentation>Anklet</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BIRD"> 

<xsd:annotation> 

<xsd:documentation>Birds (Cardinal, Hawk, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLUEFL"> 

<xsd:annotation> 

<xsd:documentation>Blue Flowers</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BODBND"> 

<xsd:annotation> 

<xsd:documentation>Body Band</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BRACE"> 

<xsd:annotation> 

<xsd:documentation>Bracelet</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BRIT"> 

<xsd:annotation> 

<xsd:documentation>British Flag</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CAT"> 

<xsd:annotation> 

<xsd:documentation>Cats & Cat Heads</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CONFED"> 

<xsd:annotation> 

<xsd:documentation>Confederate Flag</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DOG"> 

<xsd:annotation> 

<xsd:documentation>Dogs & Dog Heads</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DOMESTIC"> 

<xsd:annotation> 

<xsd:documentation>Other Domestic Animals</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DRAGON"> 

<xsd:annotation> 

<xsd:documentation>Dragons</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DRAW"> 

<xsd:annotation> 

<xsd:documentation>Drawings of Flowers</xsd:documentation>

</xsd:annotation> 

314 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:enumeration>

<xsd:enumeration value="FBODY"> 

<xsd:annotation> 

<xsd:documentation>Female Body</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FBPART"> 

<xsd:annotation> 

<xsd:documentation>Female Body Parts</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FFACE"> 

<xsd:annotation> 

<xsd:documentation>Female Face</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FIGURE"> 

<xsd:annotation> 

<xsd:documentation>Figure(s)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FIRE"> 

<xsd:annotation> 

<xsd:documentation>Fire</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FRATERNAL"> 

<xsd:annotation> 

<xsd:documentation>Fraternal Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FREEFRM"> 

<xsd:annotation> 

<xsd:documentation>Freeform Drawings</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GANG"> 

<xsd:annotation> 

<xsd:documentation>Gang Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="HEADBND"> 

<xsd:annotation> 

<xsd:documentation>Head Band</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="HORSE"> 

<xsd:annotation> 

<xsd:documentation>Horses (Donkeys, Mules, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="INSECT"> 

<xsd:annotation> 

<xsd:documentation>Spiders, Bugs, and Insects</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LILY"> 

<xsd:annotation> 

<xsd:documentation>Lily</xsd:documentation>

</xsd:annotation>

</xsd:enumeration> 

315 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:enumeration value="MABSTRACT"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Abstract</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MANIMAL"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Animal Forms</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MBODY"> 

<xsd:annotation> 

<xsd:documentation>Male Body</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MBPART"> 

<xsd:annotation> 

<xsd:documentation>Male Body Parts</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MFACE"> 

<xsd:annotation> 

<xsd:documentation>Male Face</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MFLAG"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Flags</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MHUMAN"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Human Forms</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MILITARY"> 

<xsd:annotation> 

<xsd:documentation>Military Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MISC"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Images</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MOBJECTS"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Objects</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MPLANT"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Plants, Flowers, Vegetables</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MSYMBOLS"> 

<xsd:annotation> 

<xsd:documentation>Miscellaneous Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MYTH"> 

316 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Mythical (Unicorns, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NARCOTICS"> 

<xsd:annotation> 

<xsd:documentation>Narcotics</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NATION"> 

<xsd:annotation> 

<xsd:documentation>National Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NATURE"> 

<xsd:annotation> 

<xsd:documentation>Water & Nature Scenes(Rivers, Sky, Trees, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NAZI"> 

<xsd:annotation> 

<xsd:documentation>Nazi Flag</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NECKLC"> 

<xsd:annotation> 

<xsd:documentation>Necklace</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PARTS"> 

<xsd:annotation> 

<xsd:documentation>Animal Parts</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PLANE"> 

<xsd:annotation> 

<xsd:documentation>Airplanes</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="POLITIC"> 

<xsd:annotation> 

<xsd:documentation>Political Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PROFESS"> 

<xsd:annotation> 

<xsd:documentation>Professional Symbols</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="REDFL"> 

<xsd:annotation> 

<xsd:documentation>Red Flowers</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ROLES"> 

<xsd:annotation> 

<xsd:documentation>Roles (Knight, Witch, man, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ROSE"> 

<xsd:annotation> 

317 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Rose</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SHIRT"> 

<xsd:annotation> 

<xsd:documentation>Shirt</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SKULL"> 

<xsd:annotation> 

<xsd:documentation>Skulls</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SLEEVE"> 

<xsd:annotation> 

<xsd:documentation>Sleeve</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SNAKE"> 

<xsd:annotation> 

<xsd:documentation>Snakes</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SPORT"> 

<xsd:annotation> 

<xsd:documentation>Sports Figures (Football Player, Skier, etc.) or Sporting Objects

(Football, Ski, Hurdles, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="STATE"> 

<xsd:annotation> 

<xsd:documentation>State Flag</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TRAIN"> 

<xsd:annotation> 

<xsd:documentation>Trains</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TULIP"> 

<xsd:annotation> 

<xsd:documentation>Tulip</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="USA"> 

<xsd:annotation> 

<xsd:documentation>American Flag</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="VEHICLE"> 

<xsd:annotation> 

<xsd:documentation>Cars, Trucks, and Vehicles</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="VESSEL"> 

<xsd:annotation> 

<xsd:documentation>Boats, Ships, & Other Vessels</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="VICIOUS"> 

<xsd:annotation> 

318 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Vicious Animals (Lions, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="WEAP"> 

<xsd:annotation> 

<xsd:documentation>Weapons(Guns, Arrows, etc.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="WILD"> 

<xsd:annotation> 

<xsd:documentation>Other Wild Animals</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="WORDING"> 

<xsd:annotation> 

<xsd:documentation>Wording (Mom, Dad, Mary, ect.)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="YELFL"> 

<xsd:annotation> 

<xsd:documentation>Yellow Flowers</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PSCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PSCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="PXSCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="GLASSES"> 

<xsd:annotation> 

<xsd:documentation>Glasses</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="HAT"> 

<xsd:annotation> 

<xsd:documentation>Hat</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="OTHER"> 

<xsd:annotation> 

<xsd:documentation>Other</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PHYSICAL"> 

319 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Physical</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SCARF"> 

<xsd:annotation> 

<xsd:documentation>Scarf</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="PXSCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:PXSCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ansi-nist:PalmprintImageType has been replaced by itl:PalmprintImageType -->

<!-- ======================================================= --> 

<xsd:complexType name="PalmprintImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PalmPosition" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="PhysicalFeatureColorDetailType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PhysicalFeaturePrimaryColorCode"/>

<xsd:element ref="ansi-nist:PhysicalFeatureSecondaryColorCode" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="PhysicalFeatureDescriptionType"> 

320 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<!-- =Req'd to be associated with 10.042=====fieldID="10.043" fieldMnemonic="COL" == -->

<xsd:element ref="ansi-nist:PhysicalFeatureColorDetail" minOccurs="0"/>

<!-- =============================SubFields for "10.042" fieldMnemonic="SMD" == --> 

<xsd:element ref="ansi-nist:PhysicalFeatureCategoryCode"/>

<xsd:element ref="ansi-nist:PhysicalFeatureClassCode"/>

<xsd:element ref="ansi-nist:PhysicalFeatureDescriptionText" minOccurs="0"/>

<xsd:element ref="ansi-nist:PhysicalFeatureSubClassCode"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="PhysicalFeatureImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<!-- =====================================================fieldID="10.042" 

fieldMnemonic="SMD" == --> 

<xsd:element ref="ansi-nist:PhysicalFeatureDescriptionDetail" minOccurs="0"

maxOccurs="unbounded"/>

<!-- =====================================================fieldID="10.040" 

fieldMnemonic="SMT" == --> 

<xsd:element ref="ansi-nist:PhysicalFeatureNCICCode" minOccurs="0" maxOccurs="unbounded"/>

<!-- =====================================================fieldID="10.041" 

fieldMnemonic="SMS" == --> 

<xsd:element ref="ansi-nist:PhysicalFeatureSize" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="PhysicalFeatureSizeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PhysicalFeatureHeightMeasure"/>

<xsd:element ref="ansi-nist:PhysicalFeatureWidthMeasure"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="PoseAngleType"> 

321 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:PosePitchAngleMeasure"/>

<xsd:element ref="ansi-nist:PosePitchUncertaintyValue" minOccurs="0"/>

<xsd:element ref="ansi-nist:PoseRollAngleMeasure"/>

<xsd:element ref="ansi-nist:PoseRollUncertaintyValue" minOccurs="0"/>

<xsd:element ref="ansi-nist:PoseYawAngleMeasure"/>

<xsd:element ref="ansi-nist:PoseYawUncertaintyValue" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ======not used========================================== --> 

<!-- ======================================================= --> 

<xsd:complexType name="ProtectionOrderAugmentationType">

<xsd:annotation> 

<xsd:documentation>A data type for additional information about a protection

order.</xsd:documentation>

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="AugmentationType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:AugmentationType">

<xsd:sequence>

<xsd:element ref="ansi-nist:ProtectionOrderBradyIndicator" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:ProtectionOrderConditionText" minOccurs="0" 

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="RTCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="xsd:token"> 

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ======not used==== ====================================== --> 

<!-- ======================================================= --> 

<xsd:complexType name="RecordType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo> 

322 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:RecordRetentionIndicator" minOccurs="0" 

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:RecordForwardOrganizations" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:RecordImage" minOccurs="0" maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:RecordRapSheetRequestIndicator" minOccurs="0"

maxOccurs="unbounded"/>

<xsd:element ref="ansi-nist:RecordTransactionData" minOccurs="0" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SAPCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Unknown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Latent facial</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="10"> 

<xsd:annotation> 

<xsd:documentation>Drivers license</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="11"> 

<xsd:annotation> 

<xsd:documentation>ANSI full frontal</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="12"> 

<xsd:annotation> 

<xsd:documentation>ANSI token</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="13"> 

<xsd:annotation> 

<xsd:documentation>ISO full frontal</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="14"> 

<xsd:annotation> 

<xsd:documentation>ISO token</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="15"> 

<xsd:annotation> 

323 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>PIV facial</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="20"> 

<xsd:annotation> 

<xsd:documentation>Legacy mugshot</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="30"> 

<xsd:annotation> 

<xsd:documentation>Best practice level 30</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="40"> 

<xsd:annotation> 

<xsd:documentation>Best practice level 40</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="50"> 

<xsd:annotation> 

<xsd:documentation>Best practice level 50</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="51"> 

<xsd:annotation> 

<xsd:documentation>Best practice level 51</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SAPCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SAPCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SECCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="BLK"> 

<xsd:annotation> 

<xsd:documentation>Black</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLU"> 

<xsd:annotation> 

<xsd:documentation>Blue</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BRO"> 

324 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Brown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GRN"> 

<xsd:annotation> 

<xsd:documentation>Green</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GRY"> 

<xsd:annotation> 

<xsd:documentation>Gray</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="HAZ"> 

<xsd:annotation> 

<xsd:documentation>Hazel</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MAR"> 

<xsd:annotation> 

<xsd:documentation>Maroon</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MUL"> 

<xsd:annotation> 

<xsd:documentation>Multicolored</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PNK"> 

<xsd:annotation> 

<xsd:documentation>Pink</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="XXX"> 

<xsd:annotation> 

<xsd:documentation>Unknown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SECCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SECCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SFPCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

325 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>A 2D feature point </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SFPCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SFPCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SHCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="BAL"> 

<xsd:annotation> 

<xsd:documentation>Bald</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLK"> 

<xsd:annotation> 

<xsd:documentation>Black</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLN"> 

<xsd:annotation> 

<xsd:documentation>Blonde or Strawberry</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLU"> 

<xsd:annotation> 

<xsd:documentation>Blue</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BRO"> 

<xsd:annotation> 

<xsd:documentation>Brown</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GRN"> 

<xsd:annotation> 

<xsd:documentation>Green</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="GRY"> 

<xsd:annotation> 

<xsd:documentation>Gray or Partially Gray</xsd:documentation>

</xsd:annotation> 

326 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:enumeration>

<xsd:enumeration value="ONG"> 

<xsd:annotation> 

<xsd:documentation>Orange</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PLE"> 

<xsd:annotation> 

<xsd:documentation>Purple</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="PNK"> 

<xsd:annotation> 

<xsd:documentation>Pink</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RED"> 

<xsd:annotation> 

<xsd:documentation>Red or Auburn</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SDY"> 

<xsd:annotation> 

<xsd:documentation>Sandy</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="WHI"> 

<xsd:annotation> 

<xsd:documentation>White</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="XXX"> 

<xsd:annotation> 

<xsd:documentation>Unspecified or unknown </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SHCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SHCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SIGCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Signature image of the subject</xsd:documentation> 

327 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Signature image of the official processing the

transaction</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SIGCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SIGCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SLCCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>No scale given</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Pixels per inch</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>Pixels per centimeter</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SLCCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SLCCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SMDCodeSimpleType"> 

328 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="BRANDED"> 

<xsd:annotation> 

<xsd:documentation>Image burned into the skin using a branding iron or other form of

heat.</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CHEMICAL"> 

<xsd:annotation> 

<xsd:documentation>Image created by the use of chemicals to burn the image into the

skin.</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CUT"> 

<xsd:annotation> 

<xsd:documentation>Image caused by an incision of the skin.</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MARK"> 

<xsd:annotation> 

<xsd:documentation>Pattern resulting from needle or "Track" marks.</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SCAR"> 

<xsd:annotation> 

<xsd:documentation>Healed scar tissue that was the result an accident or medical 

procedure.</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TATTOO"> 

<xsd:annotation> 

<xsd:documentation>A common tattoo or indelible image resulting from the pricking of the

skin with a coloring matter.</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SMDCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SMDCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SRMCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation> 

329 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="B"> 

<xsd:annotation> 

<xsd:documentation>Bait money</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="C"> 

<xsd:annotation> 

<xsd:documentation>Counterfeit</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="R"> 

<xsd:annotation> 

<xsd:documentation>Ransom</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SRMCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SRMCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SRTCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="0"> 

<xsd:annotation> 

<xsd:documentation>Scanned uncompressed</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="1"> 

<xsd:annotation> 

<xsd:documentation>Scanned compressed</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="2"> 

<xsd:annotation> 

<xsd:documentation>Vector</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SRTCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation> 

330 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SRTCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="SXSCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="BEARD"> 

<xsd:annotation> 

<xsd:documentation>Having Beard</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="BLINK"> 

<xsd:annotation> 

<xsd:documentation>Blinking (either or both eyes closed)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CLEAR GLASSES"> 

<xsd:annotation> 

<xsd:documentation>Subject Wearing Clear Glasses</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DARK GLASSES"> 

<xsd:annotation> 

<xsd:documentation>Subject Wearing Dark or Visible Colored Glasses

(medical)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DISTORTING CONDITION"> 

<xsd:annotation> 

<xsd:documentation>Having Distorting Medical Condition impacting Feature Point

detection</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="EYES AWAY"> 

<xsd:annotation> 

<xsd:documentation>Looking away from the camera</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FROWNING"> 

<xsd:annotation> 

<xsd:documentation>Frowning</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="HAT"> 

<xsd:annotation> 

<xsd:documentation>Head covering/hat </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LEFT EYE PATCH"> 

<xsd:annotation> 

<xsd:documentation>Subject Wearing Left Eye Patch</xsd:documentation>

</xsd:annotation>

</xsd:enumeration> 

331 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:enumeration value="MOUSTACHE"> 

<xsd:annotation> 

<xsd:documentation>Having Moustache</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MOUTH OPEN"> 

<xsd:annotation> 

<xsd:documentation>Subject Having Mouth open </xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NEUTRAL"> 

<xsd:annotation> 

<xsd:documentation>Neutral (non-smiling) with both eyes open and mouth

closed)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NO EAR"> 

<xsd:annotation> 

<xsd:documentation>Ear(s) obscured by hair</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RAISED EYEBROWS"> 

<xsd:annotation> 

<xsd:documentation>Raising eyebrows</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="RIGHT EYE PATCH"> 

<xsd:annotation> 

<xsd:documentation>Subject Wearing Right Eye Patch</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SCARF"> 

<xsd:annotation> 

<xsd:documentation>Wearing Scarf</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SMILE"> 

<xsd:annotation> 

<xsd:documentation>Smiling where the inside of the mouth and/or teeth is not exposed

(closed jaw).</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="SQUINTING">

<xsd:annotation> 

<xsd:documentation>Squiting</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TEETH VISIBLE"> 

<xsd:annotation> 

<xsd:documentation>Having Teeth visible</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="UNKNOWN"> 

<xsd:annotation> 

<xsd:documentation>Expression unspecified</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="SXSCodeType">

<xsd:annotation> 

332 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:SXSCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="SignatureImageType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="NISTImageType"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="ansi-nist:NISTImageType">

<xsd:sequence>

<xsd:element ref="ansi-nist:SignatureImageVectorRepresentation" minOccurs="0"/>

<!--

====================================================================fieldMnemonic="SRT" == --> 

<xsd:element ref="ansi-nist:SignatureRepresentationCode"/>

<!--

====================================================================fieldMnemonic="SIG" == --> 

<xsd:element ref="ansi-nist:SignatureCategoryCode"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="SignatureImageVectorRepresentationType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:SignatureImageVector" minOccurs="2" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="SignatureImageVectorType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:VectorPenPressureValue"/>

<xsd:element ref="ansi-nist:VectorPositionVerticalCoordinateValue"/>

<xsd:element ref="ansi-nist:VectorPositionHorizontalCoordinateValue"/>

</xsd:sequence>

</xsd:extension> 

333 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="TMZCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="EDT"> 

<xsd:annotation> 

<xsd:documentation>Eastern Daylight Time</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="EST"> 

<xsd:annotation> 

<xsd:documentation>Eastern Standard Time</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="TMZCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:TMZCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="TOTCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="AMN"> 

<xsd:annotation> 

<xsd:documentation>AMNESIA VICTIM</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CAR"> 

<xsd:annotation> 

<xsd:documentation>CRIMINAL TEN-PRINT SUBMISSION - ANSWER REQUIRED</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CFS"> 

<xsd:annotation> 

<xsd:documentation>COMPARISON FINGERPRINT IMAGE SUBMISSION</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CNA"> 

<xsd:annotation> 

<xsd:documentation>CRIMINAL TEN-PRINT SUBMISSION - NO ANSWER REQUIRED</xsd:documentation>

</xsd:annotation> 

334 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:enumeration>

<xsd:enumeration value="CPD"> 

<xsd:annotation> 

<xsd:documentation>CRIMINAL SUBJECT PHOTO DELETE REQUEST</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="CPR"> 

<xsd:annotation> 

<xsd:documentation>CRIMINAL SUBJECT PHOTO REQUEST</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DEK"> 

<xsd:annotation> 

<xsd:documentation>KNOWN DECEASED</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="DEU"> 

<xsd:annotation> 

<xsd:documentation>UNKNOWN DECEASED</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ELR"> 

<xsd:annotation> 

<xsd:documentation>EVALUATION LATENT FINGERPRINT IMAGE SUBMISSION</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FANC"> 

<xsd:annotation> 

<xsd:documentation>FEDERAL APPLICANT - NO CHARGE</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FAUF"> 

<xsd:annotation> 

<xsd:documentation>FEDERAL APPLICANT - USER FEE</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="FIS"> 

<xsd:annotation> 

<xsd:documentation>FINGERPRINT IMAGE SUBMISSION</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="IRQ">

<xsd:annotation> 

<xsd:documentation>FINGERPRINT IMAGE REQUEST</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LFFS"> 

<xsd:annotation> 

<xsd:documentation>LATENT FINGERPRINT FEATURES SEARCH</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LFIS"> 

<xsd:annotation> 

<xsd:documentation> FINGERPRINT IMAGE SEARCH</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LFS"> 

<xsd:annotation> 

<xsd:documentation>LATENT FINGERPRINT IMAGE SUBMISSION</xsd:documentation>

</xsd:annotation>

</xsd:enumeration> 

335 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:enumeration value="LPNQ">

<xsd:annotation> 

<xsd:documentation>LATENT PENETRATION QUERY</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="LSRQ">

<xsd:annotation> 

<xsd:documentation>LATENT REPOSITORY STATISTICS QUERY</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MAP"> 

<xsd:annotation> 

<xsd:documentation>MISCELLANEOUS APPLICANT - CIVIL</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MCS"> 

<xsd:annotation> 

<xsd:documentation>MAJOR CASE IMAGE SUBMISSION</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="MPR"> 

<xsd:annotation> 

<xsd:documentation>MISSING PERSON</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="NFUF"> 

<xsd:annotation> 

<xsd:documentation>NON-FEDERAL APPLICANT USER FEE</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TPFS"> 

<xsd:annotation> 

<xsd:documentation>TEN-PRINT FINGERPRINT FEATURES SEARCH</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="TPIS"> 

<xsd:annotation> 

<xsd:documentation>TEN-PRINT FINGERPRINT IMAGE SEARCH</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ULAC"> 

<xsd:annotation> 

<xsd:documentation>UNSOLVED LATENT ADD CONFIRM REQUEST</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="ULD"> 

<xsd:annotation> 

<xsd:documentation>UNSOLVED LATENT RECORD DELETE REQUEST</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="TOTCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:TOTCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 

336 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="TSRCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="P"> 

<xsd:annotation> 

<xsd:documentation>Pre-commission candidate record with fingerprints</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="V"> 

<xsd:annotation> 

<xsd:documentation>Civil submission in support of the National Child Protection Act of

1993</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="TSRCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:TSRCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="TransactionCharacterSetDirectoryType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:CharacterSetCommonNameCode"/>

<xsd:element ref="ansi-nist:CharacterSetIndexCode"/>

<xsd:element ref="ansi-nist:CharacterSetVersionIdentification" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="TransactionContentSummaryType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent> 

337 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:ContentFirstRecordCategoryCode"/>

<xsd:element ref="ansi-nist:ContentRecordCount"/>

<xsd:element ref="ansi-nist:ContentRecordSummary" maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="TransactionDomainType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<xsd:element ref="ansi-nist:DomainVersionNumberIdentification"/>

<xsd:element ref="ansi-nist:OrganizationName" minOccurs="0"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="TransactionImageResolutionType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<!-- ============================================================================= 

fieldID="1.011" fieldMnemonic="NSR" == --> 

<xsd:element ref="ansi-nist:NativeScanningResolutionValue"/>

<!-- ============================================================================= 

fieldID="1.012" fieldMnemonic="NTR" == --> 

<xsd:element ref="ansi-nist:NominalTransmittingResolutionValue"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:complexType name="TransactionType">

<xsd:annotation> 

<xsd:documentation>A data type for information pertaining to the transaction being

transmitted.</xsd:documentation>

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="s:ComplexObjectType">

<xsd:sequence>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionSearchRequestCategoryCode" minOccurs="0"

maxOccurs="0"/> 

338 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionSubmissionMilitaryCode" minOccurs="0"

maxOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.005" fieldMnemonic="DAT" == --> 

<xsd:element ref="ansi-nist:TransactionDate"/>

<!-- ============================================================================= 

fieldID="1.007" fieldMnemonic="DAI" == --> 

<xsd:element ref="ansi-nist:TransactionDestinationOrganization"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionHeaderText" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionKeyText" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionKeyTranslationText" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionOrganization" minOccurs="0" maxOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.008" fieldMnemonic="ORI" == --> 

<xsd:element ref="ansi-nist:TransactionOriginatingOrganization"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionReasonText" minOccurs="0" maxOccurs="0"/>

<!-- =====================================================not used 

========================= --> 

<xsd:element ref="ansi-nist:TransactionUserIdentification" minOccurs="0" maxOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.014" fieldMnemonic="GMT" == --> 

<xsd:element ref="ansi-nist:TransactionUTCDate" minOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.009" fieldMnemonic="TCN" == --> 

<xsd:element ref="ansi-nist:TransactionControlIdentification"/>

<!-- ============================================================================= 

fieldID="1.010" fieldMnemonic="TCR" == --> 

<xsd:element ref="ansi-nist:TransactionControlReferenceIdentification" minOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.013" fieldMnemonic="DOM" == --> 

<xsd:element ref="ansi-nist:TransactionDomain" minOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.011" fieldMnemonic="NSR" == --> 

<!-- ============================================================================= 

fieldID="1.012" fieldMnemonic="NTR" == --> 

<xsd:element ref="ansi-nist:TransactionImageResolutionDetails"/>

<!-- ============================================================================= 

fieldID="1.002" fieldMnemonic="VER" == --> 

<xsd:element ref="ansi-nist:TransactionMajorVersionValue"/>

<xsd:element ref="ansi-nist:TransactionMinorVersionValue"/>

<!-- ============================================================================= 

fieldID="1.006" fieldMnemonic="PRY" == --> 

<xsd:element ref="ansi-nist:TransactionPriorityValue" minOccurs="0"/>

<!-- ============================================================================= 

fieldID="1.004" fieldMnemonic="TOT" == --> 

<xsd:element ref="ansi-nist:TransactionCategoryCode"/>

<!-- ============================================================================= 

fieldID="1.003" fieldMnemonic="CNT" == --> 

<xsd:element ref="ansi-nist:TransactionContentSummary"/> 

339 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ============================================================================= 

fieldID="1.015" fieldMnemonic="DCS" == --> 

<xsd:element ref="ansi-nist:TransactionCharacterSetDirectory" minOccurs="0"

maxOccurs="unbounded"/>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

<!-- ======================================================= --> 

<xsd:simpleType name="VODCodeSimpleType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:restriction base="xsd:token"> 

<xsd:enumeration value="A"> 

<xsd:annotation> 

<xsd:documentation>GANICBAOO INTEREST (Atlanta, Georgia)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="C"> 

<xsd:annotation> 

<xsd:documentation>ILNICBCOO INTEREST (Chicago, Illinois)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="D"> 

<xsd:annotation> 

<xsd:documentation>TXNICBDOO INTEREST (Dallas, Texas)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="N"> 

<xsd:annotation> 

<xsd:documentation>NYNICBNOO INTEREST (New York, New York)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="S"> 

<xsd:annotation> 

<xsd:documentation>CANICBSOO INTEREST (San Francisco, California)</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

</xsd:restriction>

</xsd:simpleType>

<xsd:complexType name="VODCodeType">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/>

</xsd:appinfo>

</xsd:annotation>

<xsd:simpleContent>

<xsd:extension base="ansi-nist:VODCodeSimpleType">

<xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/>

</xsd:extension>

</xsd:simpleContent>

</xsd:complexType>

<!-- ======================================================= --> 

<!-- ====not used============================================ --> 

<!-- ======================================================= --> 

<xsd:element name="ActivityAgencyNotificationIndicator" type="niem-xsd:boolean" nillable="true">

<xsd:annotation> 

340 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>A flag which indicates the Investigative Agency is to be notified of any

query response which includes this Criminal Justice Entry. </xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element name="ActivityApprovalDate" type="nc:DateType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Date the information was reviewed, signed off, or otherwise approved as a

whole.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element name="ActivityAugmentation" type="ansi-nist:ActivityAugmentationType"

substitutionGroup="s:Augmentation">

<xsd:annotation> 

<xsd:documentation>An augmentation that applies to type nc:ActivityType</xsd:documentation>

<xsd:appinfo>

<i:AppliesTo i:namespace="http://niem.gov/niem/niem-core/2.0" i:name="ActivityType"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<xsd:element name="ActivityEndTimeZoneCode" type="ansi-nist:TMZCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Time Zone corresponding to the Activity End time. EDT during the months of

Daylight Savings Time.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element name="ActivityTimeZoneCode" type="ansi-nist:TMZCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Time Zone corresponding to the Activity time. EDT during the months of

Daylight Savings Time.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CBEFFCategoryCode" type="ansi-nist:BTYCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The type of biometric technology.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CBEFFFormatCategoryIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The identifier assigned to the format by the owner.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CBEFFFormatOwnerIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The identifier assigned to the registered owner of the biometric format

used in this record.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="CBEFFImage" type="ansinist:CBEFFImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

341 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:element name="CBEFFVersionIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The version of CBEFF specification that this record conforms

to.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDate" type="nc:DateType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Date image was captured.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDescription" abstract="true">

<xsd:annotation> 

<xsd:documentation>Type of human monitoring used to capture an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureDescription" name="CaptureDescriptionCode"

type="ansi-nist:DMMCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Table 25 level of human monitoring of image capture.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="CaptureDescription"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureDescription" name="CaptureDescriptionText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Type of human monitoring used to capture an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="CaptureDescription"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDeviceGlobalIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>A globally unique identifier.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDeviceIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A string identifying the device or source of the image

data.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDeviceMakeText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The make of the image capture device.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDeviceModelText" type="nc:TextType" nillable="true">

<xsd:annotation> 

342 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>The model of the image capture device.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDeviceMonitoringMode" abstract="true"/>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureDeviceMonitoringMode"

name="CaptureDeviceMonitoringModeCode" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="CaptureDeviceMonitoringMode"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureDeviceMonitoringMode"

name="CaptureDeviceMonitoringModeText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="CaptureDeviceMonitoringMode"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureDeviceSerialNumberText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The serial number of the image capture device.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureHorizontalPixelDensityValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Transmitted pixel density in horizontal direction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureOrganization" type="nc:OrganizationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The organization that originally captured the facial or SMT image contained

in this record.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureResolution" abstract="true">

<xsd:annotation> 

<xsd:documentation>A minimum or native resolution indicator.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureResolution" name="CaptureResolutionCode"

type="ansi-nist:ISRCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the minimum or native resolution indicator.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="CaptureResolution"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

343 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:element substitutionGroup="ansi-nist:CaptureResolution" name="CaptureResolutionText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A minimum or native resolution indicator.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="CaptureResolution"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureSource" abstract="true">

<xsd:annotation> 

<xsd:documentation>Source of an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureSource" name="CaptureSourceCode" type="ansinist:PASCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the classification of the source of the 

image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="CaptureSource"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:CaptureSource" name="CaptureSourceText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Source of an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="CaptureSource"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CaptureVerticalPixelDensityValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Transmitted pixel density in the vertical direction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CharacterSetCommonNameCode" type="ansi-nist:CSNCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the common name for the character set associated with the index 

number that references an associated character set throughout a transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CharacterSetIndexCode" type="ansi-nist:CSICodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the three-character identifier for the character set index number 

that references an associated character set throughout a transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CharacterSetVersionIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

344 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>A specific character set version.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="CodeManualCount" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The number of NCIC Code Manuals needed.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ContentFirstRecordCategoryCode" type="ansi-nist:RTCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Type code must be 01</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ContentRecordCount" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>Sum of records, not counting the Type-01 transaction

record.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ContentRecordSummary" type="ansi-nist:ContentRecordType" nillable="true">

<xsd:annotation> 

<xsd:documentation>One sub-field entry for each logical record in this file other than the

Type-01 transaction record.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="DomainVersionNumberIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Unique version number of an implementation.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="FaceImage" type="ansinist:FaceImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImage3DPoseAngle" type="ansi-nist:PoseAngleType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The angular offsets of the subject from a full face or a profile, for pose

code 'D'.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageAcquisitionProfile" abstract="true">

<xsd:annotation> 

<xsd:documentation>The criteria under which the facial image was captured.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageAcquisitionProfile"

name="FaceImageAcquisitionProfileCode" type="ansi-nist:SAPCodeType" nillable="true"> 

345 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Indicates the criteria under which the facial image was

captured.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageAcquisitionProfile"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageAcquisitionProfile"

name="FaceImageAcquisitionProfileText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The criteria under which the facial image was captured.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageAcquisitionProfile"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageAttribute" type="ansi-nist:FaceImageAttributeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Information about a single facial attribute.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageAttributeAbstract" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates special attributes of the captured facial

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageAttributeAbstract"

name="FaceImageAttributeCode" type="ansi-nist:PXSCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates special attributes of the captured facial

image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageAttributeAbstract"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageAttributeAbstract"

name="FaceImageAttributeText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Part 4, Sec 13 NCIC code description, or free text additional information

for "other" attributes</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageAttributeAbstract"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageDescription" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates the facial expression of the subject and other attributes

associated with the subject's captured facial image</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

346 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:element substitutionGroup="ansi-nist:FaceImageDescription" name="FaceImageDescriptionCode"

type="ansi-nist:SXSCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the facial expression of the subject and other attributes

associated with the subject's captured facial image</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageDescription"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageDescription" name="FaceImageDescriptionText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Text description of the facial image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageDescription"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageEyeColorAttribute" abstract="true">

<xsd:annotation> 

<xsd:documentation>Eye Color shown in an image of a persons face</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageEyeColorAttribute"

name="FaceImageEyeColorAttributeCode" type="ansi-nist:SECCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the eye color of the subject as seen in the

photograph.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageEyeColorAttribute"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageEyeColorAttribute"

name="FaceImageEyeColorAttributeText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Eye Color shown in an image of a persons face</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageEyeColorAttribute"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageFeaturePoint" type="ansi-nist:FaceImageFeaturePointType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>A set of attributes describing facial feature points and their

locations.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageHairColorAttribute" abstract="true">

<xsd:annotation> 

<xsd:documentation>Hair color shown in an image of a persons face</xsd:documentation>

</xsd:annotation>

</xsd:element> 

347 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageHairColorAttribute"

name="FaceImageHairColorAttributeCode" type="ansi-nist:SHCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the hair color of the subject as seen in the

photograph.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageHairColorAttribute"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageHairColorAttribute"

name="FaceImageHairColorAttributeText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Hair color shown in an image of a persons face</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageHairColorAttribute"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImagePoseOffsetAngleMeasure" type="niem-xsd:integer" nillable="true">

<xsd:annotation> 

<xsd:documentation>The angular offset of the subject from full face or a profile, for pose

code 'A'.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FaceImageSubjectPose" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates the pose of the subject.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageSubjectPose" name="FaceImageSubjectPoseCode"

type="ansi-nist:POSCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the pose of the subject.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageSubjectPose"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FaceImageSubjectPose" name="FaceImageSubjectPoseText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Text description of the pose of a subject.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FaceImageSubjectPose"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FeaturePointCategory" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates the feature point type of the captured facial

image.</xsd:documentation>

</xsd:annotation>

</xsd:element> 

348 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FeaturePointCategory" name="FeaturePointCategoryCode"

type="ansi-nist:SFPCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the feature point type of the captured facial

image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FeaturePointCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FeaturePointCategory" name="FeaturePointCategoryText"

type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Text description indicating the type of feature point being

described.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FeaturePointCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FeaturePointHorizontalCoordinateValue" type="niem-xsd:decimal" nillable="true">

<xsd:annotation> 

<xsd:documentation>The X coordinate of a core or delta position of a

biometric.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FeaturePointIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Annex K code for a particular feature point.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FeaturePointVerticalCoordinateValue" type="niem-xsd:decimal" nillable="true">

<xsd:annotation> 

<xsd:documentation>The Y coordinate of a core or delta position of a

biometric.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerPattern" abstract="true">

<xsd:annotation> 

<xsd:documentation>A particular pattern classification code.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FingerPattern" name="FingerPatternCode"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerPattern"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerPatternCodeSourceCode" type="ansi-nist:PCSCodeType" nillable="true">

<xsd:annotation> 

349 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Designator of Table 15, or user source of classification

codes.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FingerPattern" name="FingerPatternText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A particular pattern classification code. Table 15, or

other.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="FingerPattern"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerPositionCode" type="ansi-nist:FPCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Set of possible finger position codes, most probable position

first.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerPositionIndicator" type="niem-xsd:boolean" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicator denoting whether or not a fingerprint image represents a latent

print </xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="FingerprintImage" type="ansinist:FingerprintImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerprintImageImpressionCaptureCategory" abstract="true"/>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FingerprintImageImpressionCaptureCategory"

name="FingerprintImageImpressionCaptureCategoryCode" type="ansi-nist:IMPCodeType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerprintImageImpressionCaptureCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:FingerprintImageImpressionCaptureCategory"

name="FingerprintImageImpressionCaptureCategoryText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="FingerprintImageImpressionCaptureCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerprintImageMajorCasePrint" type="ansinist:FingerprintImageMajorCasePrintType" nillable="true"> 

350 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Information required when finger position code is "19" complete friction

ridge exemplars.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerprintImageNISTQuality" type="ansi-nist:FingerprintImageNISTQualityType"

nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="FingerprintImagePosition" type="ansi-nist:FingerprintType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Set of possible finger position codes, most probable position

first.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerprintImageSegmentationQuality" type="ansinist:FingerprintImageQualityType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Information about the accuracy of the slap print

segmentation.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="FingerprintPattern" type="ansi-nist:FingerprintPatternType" nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="ImageBitsPerPixelQuantity" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The number of bits used to represent a pixel.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageCaptureDetail" type="ansi-nist:ImageCaptureType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Information regarding the captured (e.g., scanned)

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageCategoryCode" type="ansi-nist:IMTCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the type of image contained in this record</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageColorSpace" abstract="true">

<xsd:annotation> 

<xsd:documentation>Color space used to exchange an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:ImageColorSpace" name="ImageColorSpaceCode" type="ansinist:CSPCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The color space code used to exchange an image from Table

3.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="ImageColorSpace"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element> 

351 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:ImageColorSpace" name="ImageColorSpaceText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Color space used to exchange an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="ImageColorSpace"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageCommentText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Comments or other text information regarding an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageCompressionAlgorithm" abstract="true">

<xsd:annotation> 

<xsd:documentation>ASCII code from Table 1</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:ImageCompressionAlgorithm"

name="ImageCompressionAlgorithmCode" type="ansi-nist:GCACodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>ASCII code from Table 1</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="ImageCompressionAlgorithm"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:ImageCompressionAlgorithm"

name="ImageCompressionAlgorithmText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>ASCII code from Table 1 (e.g. NONE or per domain registrar) or Integer code

from Table 2.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="ImageCompressionAlgorithm"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageHorizontalLineLengthPixelQuantity" type="niem-xsd:integer"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Number of pixels on a single horizontal line.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageHorizontalPixelDensityValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Transmitted pixel density in horizontal direction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageQuality" type="ansi-nist:ImageQualityType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Details about the quality of an image.</xsd:documentation> 

352 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageRecordCategoryCode" type="ansi-nist:IRTCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the type of logical image record.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageReferenceIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>An integer value associated with a particular subject matter object (e.g.,

a particular finger).</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageScaleUnitsCode" type="ansi-nist:SLCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the sampling frequency unit designator, pixels per inch, or

pixels per centimeter.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageVerticalLineLengthPixelQuantity" type="niem-xsd:integer" nillable="true">

<xsd:annotation> 

<xsd:documentation>Number of horizontal lines.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ImageVerticalPixelDensityValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Transmitted pixel density in the vertical direction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisEyeColorAttributeCode" type="ansi-nist:SECCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Table 22, eye color code.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisEyePosition" abstract="true">

<xsd:annotation> 

<xsd:documentation>Designates which eye is represented by the image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisEyePosition" name="IrisEyePositionCode" type="ansinist:FIDCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Designates which eye is represented by the image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisEyePosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisEyePosition" name="IrisEyePositionText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

353 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Which eye is represented by the text.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisEyePosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisEyeRotationAngleMeasure" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The rotation angle of the image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisEyeRotationUncertaintyValueText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Image rotation uncertainty.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="IrisImage" type="ansinist:IrisImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisImageAcquisitionLightingSpectrumValue" type="ansi-nist:ALSCodeType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Indicates the lighting spectrum used in capturing the iris

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisImageCapture" type="ansi-nist:IrisImageCaptureType" nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="IrisImageHorizontalOrientation" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates the horizontal orientation of an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisImageHorizontalOrientation"

name="IrisImageHorizontalOrientationCode" type="ansi-nist:IOCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the horizontal orientation of an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisImageHorizontalOrientation"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisImageHorizontalOrientation"

name="IrisImageHorizontalOrientationText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the horizontal orientation of an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisImageHorizontalOrientation"/> 

354 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisImageScanCategory" abstract="true">

<xsd:annotation> 

<xsd:documentation>Criteria under which the image was captured.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisImageScanCategory" name="IrisImageScanCategoryCode"

type="ansi-nist:ICTCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Iris image scan type code.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisImageScanCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisImageScanCategory" name="IrisImageScanCategoryText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Criteria under which the image was captured.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisImageScanCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="IrisImageVerticalOrientation" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates the vertical orientation of an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisImageVerticalOrientation"

name="IrisImageVerticalOrientationCode" type="ansi-nist:IOCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the vertical orientation of an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisImageVerticalOrientation"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:IrisImageVerticalOrientation"

name="IrisImageVerticalOrientationText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the vertical orientation of an image.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="IrisImageVerticalOrientation"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MajorCasePrintCode" type="ansi-nist:FERCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>An exemplar image type code from Table 30.</xsd:documentation>

</xsd:annotation>

</xsd:element> 

355 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element name="MajorCasePrintSegmentOffset" type="ansi-nist:MajorCasePrintSegmentOffsetType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Data describing the type and location of segments within a complete

friction ridge exemplars image or slap print image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MajorCasePrintText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Type of exemplar image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MaximumRangeIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Highest Value in consecutive Number Range</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinimumRangeIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Lowest Value in consecutive Number Range</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaCategory" abstract="true">

<xsd:annotation> 

<xsd:documentation>Indicates the minutia type</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaCategory" name="MinutiaCategoryCode" type="ansinist:MTCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the minutia type</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="MinutiaCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaCategory" name="MinutiaCategoryText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Text describing the type of minutia</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="MinutiaCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaDetail" type="ansi-nist:MinutiaType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Information about one finger or palmprint minutia

object.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaIdentification" type="nc:IdentificationType" nillable="true"> 

356 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>An integer value sequentially assigned to minutia in this

record.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaPosition" type="ansi-nist:MinutiaPositionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A set of coordinates describing the position of a single

minutia.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaQualityValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>A confidence level quality value.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaRidgeCount" type="ansi-nist:MinutiaRidgeCountType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A set of measurements from this minutia point to distant minutia

points.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="Minutiae" type="ansi-nist:MinutiaeType" nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeFingerCorePosition" type="ansi-nist:MinutiaeFingerPositionType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The position of the finger's pattern core.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeFingerDeltaPosition" type="ansi-nist:MinutiaeFingerPositionType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The position of the finger's pattern delta.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeFingerPatternDetail" type="ansi-nist:MinutiaeFingerPatternType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>A repeatable subelement containing details about a fingerprint pattern.

The first occurrence is the primary pattern, others are reference patterns.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeFingerPosition" abstract="true"/>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaeFingerPosition"

name="MinutiaeFingerPositionCode" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaeFingerPosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

357 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:element substitutionGroup="ansi-nist:MinutiaeFingerPosition"

name="MinutiaeFingerPositionText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaeFingerPosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeFormatNISTStandardIndicator" type="niem-xsd:boolean" nillable="true">

<xsd:annotation> 

<xsd:documentation>Designator of standard or user-defined format.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeImpressionCaptureCategory" abstract="true"/>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaeImpressionCaptureCategory"

name="MinutiaeImpressionCaptureCategoryCode" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaeImpressionCaptureCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaeImpressionCaptureCategory"

name="MinutiaeImpressionCaptureCategoryText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaeImpressionCaptureCategory"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeNISTStandard" type="ansi-nist:NISTStandardMinutiaeType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Details regarding NIST Standard Minutiae</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaePalmPosition" abstract="true"/>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaePalmPosition" name="MinutiaePalmPositionCode"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaePalmPosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:MinutiaePalmPosition" name="MinutiaePalmPositionText"

type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="MinutiaePalmPosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element> 

358 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element name="MinutiaeQuantity" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The number of minutiae recorded for this finger or

palmprint.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeReadingSystem" type="ansi-nist:MinutiaeReadingSystemType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Designator of standard or user-defined format.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="MinutiaeRidgeCountIndicator" type="niem-xsd:boolean" nillable="true">

<xsd:annotation> 

<xsd:documentation>Designates whether minutiae data record contains ridge count

information.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="NISTImage" type="ansi-nist:NISTImageType" nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="NISTQualityMeasure" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The value of a NIST Fingerprint Image Quality score, predicted matcher

accuracy.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="NativeScanningResolutionValue" type="niem-xsd:decimal" nillable="true">

<xsd:annotation> 

<xsd:documentation>In pixels per mm, the native resolution of transaction originator's

scanning equipment.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="NewsletterCount" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The number of CJIS newsletters needed.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="NominalTransmittingResolutionValue" type="niem-xsd:decimal" nillable="true">

<xsd:annotation> 

<xsd:documentation>In pixels per mm, this transaction's transmitting

resolution.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="OperatingManualCount" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The number of Operating Manuals needed.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="OrganizationDocumentCount" type="ansi-nist:OrganizationDocumentCountType"

nillable="true"> 

<xsd:annotation> 

359 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Data regarding the document counts for the ORI being

entered.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="OrganizationName" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Unique domain agency identifier.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PalmPosition" abstract="true"> 

<xsd:annotation> 

<xsd:documentation>Indicates the location on the palm that a print

represents.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:PalmPosition" name="PalmPositionCode" type="ansinist:PPCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the location on the palm that a print

represents.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="PalmPosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:PalmPosition" name="PalmPositionText" type="nc:TextType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Text indicating the location on the palm that a print

represents.</xsd:documentation>

<xsd:appinfo>

<i:Base i:name="PalmPosition"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="PalmprintImage" type="ansinist:PalmprintImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PatternCodeSourceCode" type="ansi-nist:PCSCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Designator of Table 15, or user source of classification

codes.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PatternCorePosition" type="ansi-nist:MinutiaPositionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A set of coordinates describing the position of a pattern's core or

delta.</xsd:documentation>

</xsd:annotation> 

360 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PatternDeltaPosition" type="ansi-nist:MinutiaPositionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The position of the finger's pattern delta.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PatternNISTStandardText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A particular pattern classification code. Table 15, or

other.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PatternUserText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A particular pattern classification code. Table 15, or

other.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureCategoryCode" type="ansi-nist:SMDCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the source of the image as being a scar, a mark, or a

tattoo.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureClassCode" type="ansi-nist:PCCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the human tattoo class of an SMT, OTHER if not

tattoo.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureColorDetail" type="ansi-nist:PhysicalFeatureColorDetailType"

nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureDescriptionDetail" type="ansinist:PhysicalFeatureDescriptionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A complete description of scars, marks, or tattoos visible in a transmitted

image</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureDescriptionText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Additional free text qualifiers describing the contents of the

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureHeightMeasure" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The feature's height in whole centimeters</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

361 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="PhysicalFeatureImage" type="ansinist:PhysicalFeatureImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureNCICCode" type="fbi:SMTCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>NCIC code for a particular scar, mark, or tattoo.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeaturePrimaryColorCode" type="ansi-nist:COLCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Primary Color of a tattoo in an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureSecondaryColorCode" type="ansi-nist:COLCodeType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Secondary Color of a tattoo in an image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureSize" type="ansi-nist:PhysicalFeatureSizeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The dimensions of the scar, mark, or tattoo.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureSubClassCode" type="ansi-nist:PSCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the human tattoo subclass of an SMT, MISC if not

tattoo.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PhysicalFeatureWidthMeasure" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The feature's width in whole centimeters</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PosePitchAngleMeasure" type="niem-xsd:integer" nillable="true">

<xsd:annotation> 

<xsd:documentation>Rogation about the horizontal 'x' axis.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PosePitchUncertaintyValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The pitch uncertainty.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PoseRollAngleMeasure" type="niem-xsd:integer" nillable="true"> 

362 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>Rotation about the 'z' axis.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PoseRollUncertaintyValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The roll uncertainty.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PoseYawAngleMeasure" type="niem-xsd:integer" nillable="true">

<xsd:annotation> 

<xsd:documentation>Rotation about the vertical 'y' axis.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PoseYawUncertaintyValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The yaw uncertainty.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionBottomCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>In pixels, the bottom vertical offset of the segment box within an

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionDirectionDegreeValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Direction of the core opening, through the center of curvature for the

innermost recurve at maximum curvature in integer degrees (000 to 360)</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionHorizontalCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The minutia's X coordinate</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionThetaAngleMeasure" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The minutia's theta angle</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionTopCoordinateValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>In pixels, the top vertical offset of the segment box within an

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionUncertaintyValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

363 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Radius of position uncertainty (PUM) in the manual or automatic placement

of the core in integer units of 10 micrometers.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="PositionVerticalCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The minutia's Y coordinate</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ProtectionOrderAugmentation" type="ansi-nist:ProtectionOrderAugmentationType"

substitutionGroup="s:Augmentation">

<xsd:annotation> 

<xsd:documentation>An augmentation that applies to j:ProtectionOrderType</xsd:documentation>

<xsd:appinfo>

<i:AppliesTo i:namespace="http://niem.gov/niem/domains/jxdm/4.0"

i:name="ProtectionOrderType"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ProtectionOrderBradyIndicator" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates whether the subject is considered Brady

disqualified.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ProtectionOrderConditionText" type="ansi-nist:IndicatorCodeType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Translation of the Protection Order Condition Indicates Response

Message.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="QualityAlgorithmProductIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The numeric product code assigned by a vendor to the quality

algorithm.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="QualityAlgorithmVendorIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>From a registry table, the ID of the vendor of the quality

algorithm.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="QualityMeasureVendorIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>From a registry table, the ID of the vendor of the quality

algorithm.</xsd:documentation>

</xsd:annotation>

</xsd:element> 

364 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element name="QualityValue" type="niem-xsd:integer" nillable="true">

<xsd:annotation> 

<xsd:documentation>Predicted matching performance.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ReadingSystemCodingMethodCode" type="ansi-nist:OFRCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the method by which the minutiae data was read, encoded, and

recorded.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ReadingSystemName" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The name of the system.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="ReadingSystemSubsystemIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>A two-character unique identifier for the originator's

equipment.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="Record" type="ansi-nist:RecordType" nillable="true"/>

<!-- ======================================================= --> 

<xsd:element name="RecordCategoryCode" type="ansi-nist:RTCCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The type of record (e.g., 02)</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RecordForwardOrganizations" type="nc:OrganizationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Organizations that additional electronic responses need to be forwarded

to.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RecordImage" abstract="true">

<xsd:annotation> 

<xsd:documentation>Information regarding an Image being transmitted in an ITL Record

Transaction</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RecordRapSheetRequestIndicator" type="niem-xsd:boolean" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates whether an electronic rap sheet should be returned with the

response.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RecordRetentionIndicator" type="niem-xsd:boolean" nillable="true">

<xsd:annotation> 

365 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Indicates whether the arrest/civil submission information submitted is to

be retained as a permanent part of the FBI's Criminal Master File/Civil

File</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RecordTransactionData" type="ansi-nist:TransactionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Detailed information pertaining to the transaction being

transmitted.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RidgeCountReferenceIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The index number of the distant minutia point.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="RidgeCountValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>The count of ridges between this and the distant point.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentBottomVerticalCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>In pixels, the bottom vertical offset of the segment box within an

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentFingerText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Exemplar image type represented in a major case print</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentFingerViewCode" type="ansi-nist:FEFCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The bounding coordinates for a full finger view.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentLeftHorizontalCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>In pixels, the left horizontal offset of the segment box within an

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentLocationCode" type="ansi-nist:FERCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A Major case print segment code from Table 30.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

366 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:element name="SegmentRightHorizontalCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>In pixels, the right horizontal offset of the segment box within an

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Exemplar image type represented in a major case print</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SegmentTopVerticalCoordinateValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>In pixels, the top vertical offset of the segment box within an

image.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SignatureCategoryCode" type="ansi-nist:SIGCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the signature image of the subject, or the signature image of the

official processing the transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element substitutionGroup="ansi-nist:RecordImage" name="SignatureImage" type="ansinist:SignatureImageType" nillable="true">

<xsd:annotation> 

<xsd:appinfo>

<i:Base i:name="RecordImage"/>

</xsd:appinfo>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SignatureImageVector" type="ansi-nist:SignatureImageVectorType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Detail information about one vector object.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SignatureImageVectorRepresentation" type="ansinist:SignatureImageVectorRepresentationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Repeatable set of elements regarding a signature

representation.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="SignatureRepresentationCode" type="ansi-nist:SRTCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates if an image is scanned and not compressed, scanned and

compressed, or vector data.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TOUCount" type="niem-xsd:nonNegativeInteger" nillable="true"> 

367 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:annotation> 

<xsd:documentation>The number of Technical and Operational Updates (TOUs)

needed.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="Transaction" type="ansi-nist:TransactionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Detailed information pertaining to the transaction being

transmitted.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionCategoryCode" type="ansi-nist:TOTCodeType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Indicates the type of transaction defined by receiving

agency.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionCharacterSetDirectory" type="ansinist:TransactionCharacterSetDirectoryType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Character sets other than 7-bit ASCII used in this 

transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionContentSummary" type="ansi-nist:TransactionContentSummaryType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Summary details pertaining to the record contents being

transmitted.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionControlIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Unique number assigned to transaction by the originating

agency.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionControlReferenceIdentification" type="nc:IdentificationType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Contains original TCN on transaction responses.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionDate" type="nc:DateType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Date the transaction was sent by the user</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionDestinationOrganization" type="nc:OrganizationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Organization the transaction is being sent to.</xsd:documentation>

</xsd:annotation>

</xsd:element> 

368 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<!-- ======================================================= --> 

<xsd:element name="TransactionDomain" type="ansi-nist:TransactionDomainType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Domain of Type-02 logical record implementation.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionHeaderText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>The header is a sequence of characters acceptable to the NCIC computer and

is used to provide message information for the CSA.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionImageResolutionDetails" type="ansinist:TransactionImageResolutionType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Resolution values in pixels per mm for a transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionKeyText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>A code in the header of an incoming III/FBI transaction indicating the type

of action required for processing the message. The transaction key field is the second data element

in the transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionKeyTranslationText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Translation of the Transaction Key Code for response

messages</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionMajorVersionValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>2-character major version number of the standard implemented by the

creating system.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionMinorVersionValue" type="niem-xsd:nonNegativeInteger"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>2-character minor version number of the standard implemented by the

creating system.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionOrganization" type="nc:OrganizationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Information regarding the Organization requesting the transaction

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionOriginatingOrganization" type="nc:OrganizationType" nillable="true">

<xsd:annotation> 

369 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

16 

17 

18 

19 

20 

21 

22 

23 

24 

25 

26 

27 

28 

29 

30 

31 

32 

33 

34 

35 

36 

37 

38 

39 

40 

41 

42 

43 

44 

45 

46 

47 

48 

49 

50 

51 

52 

53 

54 

55 

56 

57 

58 

59 

60 

61 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>Organization originating the transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionPriorityValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>Urgency with which transaction response is expected (0..Low

9..High)</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionReasonText" type="nc:TextType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Text field for user to provide information regarding the reason for

requesting the transaction</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionSearchRequestCategoryCode" type="ansi-nist:TSRCodeType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Indicates the type of record being submitted.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionSubmissionMilitaryCode" type="ansi-nist:MILCodeType"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>Indicates which branch of the United States Military submitted the

enlistment transaction.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionUTCDate" type="nc:DateType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Date and time of the transaction in universal units.</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="TransactionUserIdentification" type="nc:IdentificationType" nillable="true">

<xsd:annotation> 

<xsd:documentation>Unique ID to identify the Individual requesting the

transaction</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="VectorPenPressureValue" type="niem-xsd:nonNegativeInteger" nillable="true">

<xsd:annotation> 

<xsd:documentation>Constant value of pressure for the length of the vector</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="VectorPositionHorizontalCoordinateValue" type="niem-xsd:decimal"

nillable="true"> 

<xsd:annotation> 

<xsd:documentation>The vector's X coordinate in units of .0254 mm</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="VectorPositionVerticalCoordinateValue" type="niem-xsd:decimal" nillable="true">

<xsd:annotation> 

370 
 

1 

2 

3 

4 

5 

6 

7 

8 

9 

10 

11 

12 

13 

14 

15 

Part 2 March 2008 Draft ANSI/NIST-ITL 2-200X 

<xsd:documentation>The vector's Y coordinate in units of .0254 mm</xsd:documentation>

</xsd:annotation>

</xsd:element>

<!-- ======================================================= --> 

<xsd:element name="VehicleOwnershipNICB" abstract="true">

<xsd:annotation> 

<xsd:documentation>NICB Division location in the United States, showing interest in a stolen

vehicle entry.</xsd:documentation>

</xsd:annotation>

</xsd:element>

</xsd:schema> 

371