Information Technology:

American National Standard for Information 

Systems— 

Data Format for the Interchange of Fingerprint 

Facial, & Other Biometric Information – Part 2: 

XML Version

NIST Special Publication 500-275 ANSI/NIST-ITL 2-2008 

XML Version of 

ANSI/NIST-ITL 1-2007

NIST Special Publication 500-275 

Information Technology:

American National Standard for 

Information Systems— 

Data Format for the Interchange of Fingerprint, 

Facial, & Other Biometric Information – Part 2: 

XML Version 

Elaine Newton, Gerry Coleman, and Patrice Yuh, Editors 

Sponsored by 

Information Access Division 

Information Technology Laboratory 

National Institute of Standards and Technology 

Gaithersburg, MD 20899-8940

August 2008 

U.S. Department of Commerce 

Carlos M. Gutierrez, Secretary 

National Institute of Standards and Technology 

James M. Turner, Deputy Director 

ANSI/NIST-ITL 2-2008 

XML Version of 

ANSI/NIST-ITL 1-2007

Approved August 12, 2008 

American National Standards Institute, Inc. 
Certain commercial entities, equipment, or materials may be identified in this document to assign field numbers 

to registered vendors or to describe a procedure or concept adequately. Such identification is not intended to 

imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it 

intended to imply that the entities, materials, or equipment are necessarily the best available for the purpose. 

National Institute of Standards and Technology 

Special Publication 500-275 

Natl. Inst. Stand. Technol. 

Spec. Publ. 500-275 

408 pages (August 2008) 

CODEN: NSPUE2 

Reports on Information Technology 

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

Technology (NIST) stimulates U.S. economic growth and industrial competitiveness through technical 

leadership and collaborative research in critical infrastructure technology, including tests, test methods, 

reference data, and forward-looking standards, to advance the development and productive use of 

information technology. To overcome barriers to usability, scalability, interoperability, and security in 

information systems and networks, ITL programs focus on a broad range of networking, security, and 

advanced information technologies, as well as the mathematical, statistical, and computational sciences. 

This Special Publication 500-series reports on ITL’s research in tests and test methods for information 

technology, and its collaborative activities with industry, government, and academic organizations. 

This document is a contribution of the National Institute of Standards and Technology and is 

not subject to copyright. Any organization interested in reproducing ANSI/NIST-ITL 2-2008 

Data Format for the Interchange of Fingerprint, Facial, & Other Biometric Information – Part 

2: XML Version is free to do so. However there shall be no alteration to any of the material 

contained in the document. NIST retains the sole right to submit this standard to any other 

forum for any purpose. 
Part 2 ANSI/NIST-ITL 2-2008

i

Contents 

Acknowledgements ................................................................................................... vii 

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

205.9 Guidance on Missing Data for Mandatory Elements.................................................... 12

206 Image resolution requirements............................................................................................... 13

206.1 Scanner resolution requirement................................................................................... 13

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

207 Information exchange package description............................................................................ 14

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

207.2 Information exchange package contents ..................................................................... 16
Part 2 ANSI/NIST-ITL 2-2008

ii

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

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

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

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

208.2 Record format............................................................................................................... 24

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

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

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.................................................................. 36

211.1 General......................................................................................................................... 36

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

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

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

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

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

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

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

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

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

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

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

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

214.1 Minutiae and other information descriptors (Standard Format) ................................... 50
Part 2 ANSI/NIST-ITL 2-2008

iii

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

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

214.4 Additional minutiae records.......................................................................................... 61

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

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

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

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

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

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

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

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

218.2 End of Type-13 variable-resolution latent image record ............................................ 103

218.3 Additional variable-resolution latent image records ................................................... 103

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

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

219.2 End of Type-14 variable-resolution fingerprint image record..................................... 118

219.3 Additional variable-resolution fingerprint image records............................................ 118

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

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

220.2 End of Type-15 variable-resolution palmprint image record ...................................... 127

220.3 Additional variable-resolution palmprint image records ............................................. 127

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

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

221.2 End of Type-16 user-defined testing image record.................................................... 136

221.3 Additional Type-16 user-defined testing image records............................................. 136

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

222.1 General....................................................................................................................... 136
Part 2 ANSI/NIST-ITL 2-2008

iv

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

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

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

223 Type-99 CBEFF record ........................................................................................................ 148

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

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

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

224 Another individual................................................................................................................. 155

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

Annex B Package Schema....................................................................................................... 157

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

Annex D JPEG file interchange format..................................................................................... 172

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

Annex F Instance Document .................................................................................................... 192

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

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

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

Annex J Face-Pose Values ...................................................................................................... 258

Annex K Bibliography ............................................................................................................... 261

Annex L Constraint Schema..................................................................................................... 262

Figures 

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

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

Figure 3 Minutiae coordinate system ........................................................................................... 52

Figure 4 Examples of resolution for levels 30, 40, & 50/51.......................................................... 74
Part 2 ANSI/NIST-ITL 2-2008

v

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

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

Figure 7 Entire joint image.......................................................................................................... 100

Tables 

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

Table 202 Binary compression codes ............................................................................................ 9

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

Table 204 Logical record types .................................................................................................... 15

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

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 .................................................................................. 41

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

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

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

Table 215 Minutiae types ............................................................................................................. 51

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

Table 217 Pattern classification.................................................................................................... 60

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

Table 219 Device monitoring modes............................................................................................ 67

Table 220 Subject acquisition profiles.......................................................................................... 72

Table 221 Photo descriptors......................................................................................................... 76
Part 2 ANSI/NIST-ITL 2-2008

vi

Table 222 Subject facial description codes.................................................................................. 77

Table 223 Eye color codes........................................................................................................... 78

Table 224 Subject feature points.................................................................................................. 79

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

Table 226 Hair color codes........................................................................................................... 81

Table 227 Subject pose................................................................................................................ 84

Table 228 Acquisition source type codes..................................................................................... 85

Table 229 Color codes ................................................................................................................. 86

Table 230 Tattoo classes ............................................................................................................. 87

Table 231 Tattoo subclasses........................................................................................................ 88

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

Table 233 EJI and tip codes......................................................................................................... 99

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

Table 235 Palm codes and dimensions ..................................................................................... 119

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

Table 237 Type-16 Variable-resolution user-defined testing image record layout..................... 129

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

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

Table 240 CBEFF Biometric type............................................................................................... 155
Part 2 ANSI/NIST-ITL 2-2008

vii

Acknowledgements 

NIST would like to acknowledge the significant contributions of Gerry Coleman from the 

Wisconsin Department of Justice for his invaluable leadership and technical contributions in the 

development of this standard. Mr. Coleman initiated and led the ANSI/NIST XML Work Group to 

develop this inaugural XML version of the ANSI/NIST standard. He spent over three years on 

this project to create and refine the XML tags and schema. 

NIST would also like to acknowledge the significant contributions of Patrice Yuh at the FBI. The 

conformance of this standard with the National Information Exchange Model (NIEM) would not 

have been possible without the invaluable work of Mr. Yuh, who served as an ANSI/NIST 

representative at NIEM meetings and coordinated the work of the XML work group with the NIEM. 

Special thanks to those who have participated in the work group and workshops and provided 

valuable suggestions in shaping this standard. NIST also acknowledges the comments received 

from government and industry organizations during both the preliminary draft and ballot review 

periods. Thanks to Elizabeth Lennon at NIST for reviewing this publication. 
Part 2 ANSI/NIST-ITL 2-2008

viii

Foreword (This foreword is not part of American National Standard 

 ANSI/NIST-ITL 2-2008.) 

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

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 

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

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

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

developed. However, this standard does not address policies, permissions, or jurisdictional 

issues regarding the exchange of data. 

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

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

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

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

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. 

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

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

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

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 

and equipment. 

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

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

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 

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

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

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

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, 

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

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

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

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

evidence of consensus. This updated standard is an XML version of ANSI/NIST-ITL 1-2007 that 

address the interchange of fingerprint, facial, and SMT data. 

The document that follows is the Extensible Markup Language (XML) version, or a second part to 

the ANSI/NIST-ITL standard. Part 1, the conventional version, was approved April 20, 2007. 

Part 2 includes twelve annexes. Annex A is normative and contains the 7-bit American Standard 

Code for Information Interchange (ASCII). Annex B is normative and contains the ITL package 

schema. Annex C is normative and describes the base-64 encoding scheme. Annex D, a 

description of the Joint Photographic Experts Group (JPEG) File Interchange Format (JFIF), is 

normative and considered part of the standard. Annex E is normative and contains the current 

version’s (December 2000) codes from the National Crime Information Center (NCIC) Code 
Part 2 ANSI/NIST-ITL 2-2008

ix

Manual for describing the body locations of Scars, Marks, and Tattoos. Annex F is an example 

XML instance document file containing all logical record types, and illustrating the use of every 

data element. The biometric exchange records contained in Annex F are formatted in 

accordance with this standard and are informative and not considered as part of the standard. 

Annex G is informative and contains the XML version of the INCITS/M1 378 minutiae format 

specifications. Informative Annexes H and I contain best practices for mugshots for application 

levels 30 through 51, respectively. Annex J is informative and contains various examples of facepose value combinations. Annex K is a bibliography of informative references. Annex L contains 

the constraint schema and is informative. 

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

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

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

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

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

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

tagged conventional elements described in Part 1. The Part 1 subelements (separated by the US

and RS characters in the conventional representation) have been given XML counterparts in Part 

2. Another goal is to define an XML representation that conforms to the National Information 

Exchange Model (NIEM). 

This standard and supplementary files are available at the website 

<http://biometrics.nist.gov/standard/2-2008>. 

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

attention of the ANSI/NIST Project Leader, NIST ITL Biometric Standards, Information Access 

Division, Image Processing Group, NIST, 100 Bureau Dr, Mail Stop 8940, Gaithersburg, MD 

20899-8940, <ansi-nist-xml@nist.gov>. 

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

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

contacted prior to the approval of this standard. Inclusion in this list does not necessarily imply 

that the organization concurred with the submittal of the proposed standard to ANSI. 

Member Organization Canvassee

ATS John Loverude 

Authenti-Corp Valorie Valencia 

Aware, Inc. Robert Mungovan 

 Scott Hills (Alt.) 

BAE Systems Information Technology Brian Finegold 

Biometric Information Mgmt Michael Powers 

Bundeskriminalamt Gerd Hardt 

 Christopher Schiel (Alt.) 

BWXT Y-12 Mark Patterson 

California Department of Justice Anthony Doonan 

 Rochelle Dann (Alt.) 

 Rick McFarland (Alt.) 

Cherry Biometrics Michael Cherry 
Part 2 ANSI/NIST-ITL 2-2008

x

City of Henderson, Nevada Kent Timothy 

Cogent Systems, Inc. Anne Wang 

 Howard Dong (Alt.) 

 Mark Goulding (Alt.) 

 Geppy Parziale (Alt.) 

Cross Match Technologies Erik Schuster 

 Greg Cannon (Alt.) 

 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 

 Marianne Kilgannon-Martz (Alt.) 

FBI/CJIS Tom Hopper 

 Patrice Yuh (Alt.) 

 B. Scott Swann (Alt.) 

 Fred Jaco (Alt.) 

Florida Department of Law Enforcement Charles Schaeffer 

Foray Technologies David Witzke 

Global XSTF Paul Embley 

Hall Biometric Associates David Hall 

Hennepin County Sheriff's Office Leila Tite 

Higgins-Hermansen-Banikas, 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.) 

International Biometric Group (IBG) Brian Wong 

Kern County Sheriff Daniel Harmuth 

King County Sheriff's Office Carol Gillespie 

Kosovo Police Besim Hasanaj 

KS Information Technology Kristianne Scheier 

L-1 Identity Solutions Scott Piette 

 Brian Martin (Alt.) 

 Henri Schueler (Alt.) 

 D.P. Weston (Alt.) 
Part 2 ANSI/NIST-ITL 2-2008

xi

Lockheed Martin David Hagan 

 Scott Rogers (Alt.) 

Los Angeles Co. Sheriff's Dept. T.J. Smith 

 Stephen Bevan (Alt.) 

Mentalix, Inc. Dale Remmers 

MN Bureau of Criminal Apprehension Jerry Olson 

Motorola Mitchell Higashi 

MTG Management Consultants Terrance Gough 

National Policing Improvement Agency Geoff Whitaker 

 John Flahive (Alt.) 

Nebraska State Patrol Bruce Luhr 

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 

Nortel PEC Solutions, Inc Benjamin McDowell 

NYS Div. of Criminal Justice Services Joyce Bellinghausen 

 Marie Sciocchetti (Alt.) 

 Mary Ann Pelletier (Alt.) 

 Joe Morrissey (Alt.) 

Philadelphia Police Department Gabriel Keown 

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.) 

Santa Clara County Sherrif's Office Richard Reneau 

Science Applications International 

Corporation Doug Houck 

Shelby County Sheriff's Office Stanley Sellers 

Terrorist Screening Center John N. Latta 

 Joseph Krozak (Alt.) 

 Christopher Holmes (Alt.) 

 CJ Lee (Alt.) 

 Stan Larmee (Alt.) 

Texas Department of Public Safety Mike Lesko 
Part 2 ANSI/NIST-ITL 2-2008

xii

Toronto Police Service Newton Phoon 

United States Army Biometrics Task Force Dale Hapeman 

 Samuel DeWolfe (Alt.) 

US Secret Service Keri Moorefield 

vIDentity Systems, Inc. Alan Viars 

WI Dept. of Justice Gerry Coleman 
Part 2 ANSI/NIST-ITL 2-2008

1

201 Introduction 

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

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

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

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

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

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

processed minutiae data. 

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

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

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

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

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

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

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

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

As a result of workshops convened in 2005, the standard was updated and expanded into two 

parts. Part 1 (ANSI/NIST-ITL 1-2007) is the conventional tagged-field format version and was 

passed in April 2007. Major enhancements in the Part 1 revision include quality and 

segmentation support for “flats,” a new block of minutiae fields to harmonize with the INCITS M1 

minutiae standard, a new record type for the exchange of iris information, and a new record type 

to contain biometric information not described in the standard but conformant to other registered 

biometric data format standards. 

This document contains the Extensible Markup Language (XML) version, or Part 2. Over the past 

several years, many data interchange and processing applications have converted to or are in the 

process of migrating toward an XML format approach for processing data. In order to provide the 

ability to directly interface with such applications, this XML alternative representation of the 

textual, image, and other biometric information has been developed. A goal of Part 2 of this 

standard is to describe a “one-to-one” correspondence of XML elements to the numerically 

tagged conventional fields described in Part 1. Another goal is to define an XML representation 

that conforms to the National Information Exchange Model (NIEM), which enables interoperability 

for information sharing among multiple government agencies. 

202 Scope, purpose, and conformance 

202.1 Scope

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

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

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

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

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

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

justice administrations or organizations that rely on automated fingerprint and palmprint 
Part 2 ANSI/NIST-ITL 2-2008

2

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

purposes. 

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

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

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

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

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

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

202.2 Purpose 

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

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

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 

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

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

identification data. 

202.3 Conformance 

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

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

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

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

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 

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

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

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

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

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

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

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

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

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. 

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

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

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

payload in a larger package. 

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

schema do not strictly enforce the requirement. 
Part 2 ANSI/NIST-ITL 2-2008

3

203 Normative References 

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

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

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

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

standards indicated below. 

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

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

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

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

Facsimile Equipment. 

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

Glossary of Terms and Acronyms.2

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

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

ANSI/NIST-ITL 1-2007, American National Standard for Information Systems – Data Format for 

the Interchange of Fingerprint, Facial, and Other Biometric Information – Part 1.4

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

2005.5

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

19, 1997. 

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

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

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. 
Part 2 ANSI/NIST-ITL 2-2008

4

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

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

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

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

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

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

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

Compression, Version 1.1, April 2004.7

 Available at: 

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

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

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

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

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

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

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

Technology, 2004.8

 Available at: 

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

204 Definitions 

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

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

this standard. 

204.1 AAMVA 

Abbreviation for the American Association of Motor Vehicle Administrators 

204.2 ANSI 

Abbreviation for the American National Standards Institute, Inc. 

204.3 aspect ratio 

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

204.4 complete friction ridge exemplars 

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. 
Part 2 ANSI/NIST-ITL 2-2008

5

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 for 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 
Part 2 ANSI/NIST-ITL 2-2008

6

204.18 ppmm 

Abbreviation for pixels per millimeter 

204.19 RGB 

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

represent each of these primary color components. 

204.20 ROI 

Abbreviation for region of interest. 

204.21 SMT 

Abbreviation used for scar, mark, and tattoo information. 

204.22 scanning resolution 

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

204.23 tagged-field record 

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

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

204.24 transaction 

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

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

204.25 XML 

Extensible Markup Language. A convention for marking up and tagging data for electronic 

transmission. 

205 Transmitted data conventions 

205.1 Fingerprint Ridge Representation 

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

image data. 

205.2 Byte and bit ordering 

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

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

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

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

exchange package. 
Part 2 ANSI/NIST-ITL 2-2008

7

Figure 1 Byte and bit ordering 

205.3 Grayscale data 

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

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

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

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

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

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

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

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

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

justified and zero padded on the left. 

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

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

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

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

converted to ASCII for transmission using Base64 encoding. 

205.4 Binary data 

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

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

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

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

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

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

shall be the first of the eight pixels scanned. 

205.5 Color data 

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

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

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

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

First Byte Last Byte

Byte of Data

Most Significant Byte Least Significant Byte

Most Significant Byte Within a Block Transmitted First

Most Significant Bit Within a Byte Transmitted First

Most

Significant

Bit

Least

Significant

Bit

MSB LSB MSB LSB

Most Significant Byte Least Significant Byte
Part 2 ANSI/NIST-ITL 2-2008

8

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

205.6 Compression algorithms 

205.6.1 Color and grayscale compression algorithms 

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

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

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

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

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

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

ASCII code should be used. 

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 

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

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

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

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

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

 as found in Annex D.10 

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

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

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

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

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

 

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. 
Part 2 ANSI/NIST-ITL 2-2008

9

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

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 

0.55 bpp. 

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

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

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 

able to decode code streams created through both filters. 

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

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

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

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

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

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

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

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 

to a decoder in a streaming mode of operation. 

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

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

• 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. 

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

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

perform either human or automated identification. 

205.6.2 Binary compression algorithms 

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

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

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

exchange of binary images. 

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 
Part 2 ANSI/NIST-ITL 2-2008

10

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

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

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

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

205.7 Color spaces 

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

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

marked as undefined. 

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) 

205.7.1 Backwards compatibility 

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

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

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

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

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

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

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

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

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

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

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

205.7.2 Color space sRGB 

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, sRGB,11 before 

 

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. 
Part 2 ANSI/NIST-ITL 2-2008

11

compression or transmission to another system. As defined by IEC 61966-2-1, sRGB is a 

nonlinear display profile that accommodates the voltage-to-color response characteristics of most 

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

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

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

white point is as follows: 

divide/multiply by 255.

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

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

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

where is an R, G, or B value in linear RGBspace

1055 0 055 for 0 0031308

12 92 for 0 0031308

1 2 4

sRGB

value

value

. value . , value .

. value , value . value

sRGB

lin

lin

( / . )

lin

lin lin 

sRGB ⎩

⎨

⎧

− >

≤ =

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

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

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

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

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

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

space to sRGB. 

205.8 Scan sequence 

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

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

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

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

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

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

fingerprint, palmprint, face, SMT, or iris. Figure 2 illustrates the recording order for the scanned 

fingerprint image. 

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

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

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

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

increase positively from the origin to the bottom of the image. 
Part 2 ANSI/NIST-ITL 2-2008

12

Figure 2 Order of scanned image 

205.9 Guidance on Missing Data for Mandatory Elements 

In all cases, the element tags for mandatory elements shall appear in the instance package. 

When there is no information to be transmitted for a mandatory element, prior agreement shall be 

made with the recipient agency or organization before constructing and transmitting an instance 

package. For cases where an agreement is made to accept records with missing mandatory 

data, the following recommendations are made. 

205.9.1 String Elements (nc:TextType) 

The content of certain elements (such as agency identifiers or types of transaction) is left to users 

to define. For example, it is stated in this standard that the content of the element <ansinist:CaptureOrganization> (or Source agency/ORI) “shall be defined by the user and be in 

accordance with the receiving agency.” The sender and receiver may choose to establish an 

identifier for missing information. In this case, the preferred representation for missing data is to 

use the value “UNKNOWN” (provided that there is no other option available). 

<ansi-nist:CaptureOrganization>UNKNOWN 

</ansi-nist:CaptureOrganization> 

205.9.2 Date Elements 

Due to NIEM rules for date elements, the preferred representation for missing date data is to “nil” 

the parent element, as shown in this example: 

<ansi-nist:CaptureDate xsi:nil=”true”/> 

Partially missing date data may be represented as follows: 

<ansi-nist:CaptureDate> 

<nc:Year>1995</nc:Year> 

</ansi-nist:CaptureDate> 

 or 
Part 2 ANSI/NIST-ITL 2-2008

13

<ansi-nist:CaptureDate> 

<nc:YearMonth>1995-05</nc:YearMonth> 

</ansi-nist:CaptureDate> 

206 Image resolution requirements 

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

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

and are not dependent on the specific scanning resolution used. 

206.1 Scanner resolution requirement 

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

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

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

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

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

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

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

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

plus or minus 10 ppi). 

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

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

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

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

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

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

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

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

ppmm (1000 ppi). 

206.2 Transmitting resolution requirement 

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

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

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

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

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

subsampled, scaled, or interpolated down. This process to reduce the scanning resolution to a 

lower effective resolution must be performed before the transmission occurs. 

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

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

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

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

the processing of high-resolution records. 

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

of the minimum scanning resolution or 9.84 ppmm plus or minus 0.10 ppmm (250 ppi plus or 
Part 2 ANSI/NIST-ITL 2-2008

14

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

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

permitted for the processing of low-resolution records. 

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

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

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

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

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

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

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

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

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

transmission migration path. 

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

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

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

207 Information exchange package description 

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

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

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

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

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

<itl:NISTBiometricInformationExchangePackage> complex element. 

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

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

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

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

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

package shall be contained within a single 

<itl:NISTBiometricInformationExchangePackage> element. 

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

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

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

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

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

<nc:BinaryBase64Object> element. 

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

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

204. (Table 204 corresponds to Table 4 in Part 1.) 
Part 2 ANSI/NIST-ITL 2-2008

15

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:PackageLowResolutionGrayscaleImageRecord> Low-resolution grayscale fingerprint image ASCII/Base64 

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

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

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

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

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

Vector data 

9 <itl:PackageMinutiaeRecord> Minutiae data ASCII 

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

11 Reserved for future use - 

12 Reserved for future use - 

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

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

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

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

17 <itl:PackageIrisImageRecord> Iris image ASCII/ Base64 

18-98 Reserved for future use ASCII/ Base64 

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

207.1 Information exchange package format 

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

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

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 

value of zero. 

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

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

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

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

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

international character exchange methods are not applicable to record Type 1. 
Part 2 ANSI/NIST-ITL 2-2008

16

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

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. 

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

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

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. (Note that the 

order of the elements in this standard are mandatory, unlike the order of fields in Part 1. The 

elements appear in the following order: NIEM core, NIEM domains, and then extensions.) 

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

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

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

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 

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

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

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

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

extensions can only appear as substitutes for these abstract elements. 

207.2 Information exchange package contents 

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

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

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 

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

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

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

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 

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

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

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

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

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

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

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

number of records that may be present. 

207.3 Implementation domains 

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

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

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

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

implementation domain. 
Part 2 ANSI/NIST-ITL 2-2008

17

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

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

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

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

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

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

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

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

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

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

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

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

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

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 

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

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

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

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

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

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

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

207.4 Image reference identification 

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

an exchange package shall include an <ansi-nist:ImageReferenceIdentification>
Part 2 ANSI/NIST-ITL 2-2008

18

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

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

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

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

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

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

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

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

same IDC number. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

last IDC used. 

208 Record description 

208.1 Logical record types 

208.1.1 Type-1 Transaction information record 

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

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

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

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

and required information items. 

208.1.2 Type-2 User-defined descriptive text record 

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

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

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

provided by the standard. These data blocks provide identification and descriptive information 
Part 2 ANSI/NIST-ITL 2-2008

19

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

format and content to the specifications of the domain name as listed in Domain Name element 

found in the Type-1 record. 

208.1.3 Type-3 through Type-6 fingerprint image records 

The XML names for the Type-3 through Type-6 records are 

<itl:PackageLowResolutionGrayscaleImageRecord>, 

<itl:PackageHighResolutionGrayscaleImageRecord>, 

<itl:PackageLowResolutionBinaryImageRecord>,and 

<itl:PackageHighResolutionBinaryImageRecord>, respectively. 

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

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

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

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

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

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

206 is the same as Table 6 in Part 1 except the errors have been corrected for Type-3 and Type5 maximum pixel density values.) 

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

The Wavelet Scalar Quantization (WSQ) algorithm has been generally used to compress 

grayscale images while the facsimile algorithm is used for the binary images. Typically, there 

may be up to 14 records of any of these logical types of fingerprint images in a file; ten rolled 

impressions of the individual fingers, two plain impressions of the thumbs, and two 

simultaneously obtained plain impressions of the four remaining fingers on each hand. 

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

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

and not a rescan of a hard copy fingerprint image. 

Table 206 Resolution of Transmitted fingerprint image records 

Preferred 

Pixel Density 

Maximum 

Pixel Density 

Record type Data type 

Ppmm ppi ppmm ppi 

Type-3 Grayscale 9.84 250.00 10.34 262.50 

Type-4 Grayscale 19.69 500.00 20.67 525.00 

Type-5 Binary 9.84 250.00 10.34 262.50 

Type-6 Binary 19.69 500.00 20.67 525.00 
Part 2 ANSI/NIST-ITL 2-2008

20

208.1.3.1 Type-3 Low-resolution grayscale fingerprint image 

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

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

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

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

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

permissible transmitting resolution requirement for low-resolution images. 

208.1.3.2 Type-4 High-resolution grayscale fingerprint image 

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

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

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

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

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

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

images. 

208.1.3.3 Type-5 Low-resolution binary fingerprint image 

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

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

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

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

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

permissible transmitting resolution requirement for low-resolution images. 

208.1.3.4 Type-6 High-resolution binary fingerprint image 

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

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

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

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

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

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

208.1.4 Type-7 User-defined image record 

The XML name for the Type-7 record is <itl:PackageUserDefinedImageRecord>, and its 

<ansi-nist:RecordCategoryCode> element shall have a value of “07”. Type-7 logical 

records shall contain user-defined image data. Originally defined in 1993, this record type was 

designed for the exchange of binary image data that was not specified or described elsewhere in 

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

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

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

versions of the standard. 

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

be exchanged are undefined by this standard. Implementers will define an XML data block that 
Part 2 ANSI/NIST-ITL 2-2008

21

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

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

208.1.5 Type-8 Signature image record 

The XML name for the Type-8 record is <itl:PackageSignatureImageRecord>, and its 

<ansi-nist:RecordCategoryCode> element shall have a value of “08”. Type-8 logical 

records shall contain and be used to exchange scanned high-resolution binary or vectored 

signature image data. If scanned, the resolution of the image data shall be no less than the 

minimum scanning resolution. If necessary, the scanned image data shall be subsampled, 

scaled down, or interpolated to fall within the limits of the transmitting resolution requirement. 

The resultant transmitting resolution shall be within the bounds of the permissible transmitting 

resolutions for the high-resolution fingerprint images. Vectored signature data shall be expressed 

as a series of numeric integers. 

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

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

official taking the fingerprint. 

208.1.6 Type-9 Minutiae data record 

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

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

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

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

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

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

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

208.1.7 Type-10 Facial & SMT image record 

The XML name for the Type-10 record is <itl:PackageFacialAndSMTImageRecord>, and 

its <ansi-nist:RecordCategoryCode> element shall have a value of “10”. Type-10 image 

records shall contain and be used to exchange facial and image data from scars, marks, and 

tattoos (SMT) together with textual information pertinent to the digitized image. The source of the 

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

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

208.1.8 Type-11 Reserved for future use 

208.1.9 Type-12 Reserved for future use 

208.1.10 Type-13 Variable-resolution latent image record 

The XML name for the Type-13 record is <itl:PackageLatentImageRecord>, and its 

<ansi-nist:RecordCategoryCode> element shall have a value of “13”. Type-13 image 

records shall contain and be used to exchange variable-resolution latent fingerprint or palmprint 

image data together with fixed and user-defined textual information elements pertinent 

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

resolution) and transmission rate for latent images shall be 39.37 ppmm plus or minus 0.40 
Part 2 ANSI/NIST-ITL 2-2008

22

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

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

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

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

exchange of latent images. 

208.1.11 Type-14 Variable-resolution fingerprint image record 

The XML name for the Type-14 record is <itl:PackageFingerprintImageRecord>, and its 

<ansi-nist:RecordCategoryCode> element shall have a value of “14”. Type-14 image 

records shall contain and be used to exchange variable-resolution fingerprint image data, 

segmented flat fingerprint data, or major case print data. Fixed and user-defined textual 

information elements pertinent to the digitized image may also be included. Fingerprint images 

can be either rolled or plain (including swiped) impressions. 

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

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

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

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

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

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

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

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

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

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

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

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

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

208.1.12 Type-15 Variable-resolution palmprint image record 

The XML name for the Type-15 record is <itl:PackagePalmprintImageRecord>, and its 

<ansi-nist:RecordCategoryCode> element shall have a value of “15”. Type-15 image 

records shall contain and be used to exchange variable-resolution palmprint image data 

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

digitized image. 

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

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

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

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

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

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

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

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

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

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

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

hypothenar, and interdigital areas from each hand. 
Part 2 ANSI/NIST-ITL 2-2008

23

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

The XML name for the Type-16 record is 

<itl:PackageUserDefinedTestingImageRecord>, and its <ansinist:RecordCategoryCode> element shall have a value of “16”. The Type-16 image record 

is intended as an alternate version of the Type-7 user-defined logical record. It is designed for 

developmental purposes and for the exchange of miscellaneous images. This logical record shall 

contain and be used to exchange image data together with textual information elements 

pertinent to the digitized image. Such an image is usually not elsewhere specified or described in 

this standard. 

A fixed scanning resolution is not specified for this record type. However, where resolution is a 

factor in the captured image, it shall be at least as great as the minimum scanning resolution, that 

is, 19.69 ppmm (500ppi). Increases in the resolution used for capturing images should follow the 

recommended migration path to 39.37 ppmm (1000 ppi), 78.74 ppmm (2000 ppi), etc. It should 

be noted that as the resolution is increased, more detailed ridge and structure information 

becomes available in the image. 

The variable-resolution image data contained in the Type-16 logical record may be in a 

compressed form. With the exception of the elements at the start of the record and the 

descriptors for the image data, the remaining details of the Type-16 record are undefined by this 

standard and shall be agreed upon between the sender and recipient. 

208.1.14 Type-17 Iris image record 

The XML name for the Type-17 record is <itl:PackageIrisImageRecord>, and its <ansinist:RecordCategoryCode> element shall have a value of “17”. Type-17 image records shall 

contain and be used to exchange iris image data. This record type was developed to provide a 

basic level of interoperability and harmonization with the ANSI INCITS 379-2004 Iris Image 

Interchange Format and the ISO/IEC 19794-6 iris image data interchange format. Generic iris 

images may be exchanged using the mandatory elements of this record type. Optional elements 

may also be used to exchange additional information. Although the iris standards provide for two 

alternative iris image interchange formats, the Type-17 record shall only address and establish 

provision for the rectilinear image storage format that may be a raw uncompressed array of 

intensity values or a compressed format of the raw data. 

208.1.15 Type-99 CBEFF biometric data record 

The XML name for the Type-99 record is <itl:PackageCBEFFBiometricDataRecord>, and 

its <ansi-nist:RecordCategoryCode> element shall have a value of “99”. Type-99 logical 

records shall contain and be used to exchange biometric data that is not supported by other 

ANSI/NIST-ITL logical record types. This provides a basic level of interoperability and 

harmonization with the ANSI INCITS and other biometric interchange formats. This is 

accomplished by using a basic record structure that is conformant with ANSI INCITS 398-2005, 

the Common Biometric Exchange Formats Framework (CBEFF), and a biometric data block 

specification registered with the International Biometrics Industry Association (IBIA).12 This 

logical record type supports and is intended to be used for biometric data types or formats that 

are not already represented by an existing ANSI/NIST data type. 

 

12 For more information, go to <http://www.ibia.org>. 
Part 2 ANSI/NIST-ITL 2-2008

24

A CBEFF-conformant Biometric Information Record (BIR) is made up of a Header, a Biometric 

Data Block (BDB), and an optional Signature Block. The Type-99 logical record does not use the 

Signature Block. Information required by the Header portion is encoded as XML elements within 

the Type-99 record. The final tagged field in Part 1 (corresponding to element 

<nc:BinaryBase64Object>) of the Type-99 record will contain biometric data as specified by the 

BDB interchange format. 

208.2 Record format 

An exchange package shall consist of one or more logical records. For each logical record 

contained in the package, several information elements appropriate to that record type shall be 

present. Complex elements may contain one or more complex or simple elements according to 

the rules of well-formed XML. Taken together, these items are used to convey different aspects of 

the data contained in a data information object. To the extent possible, the objects used have 

been defined as a part of the National Information Exchange Model (NIEM). Some information 

objects may be repeated multiple times. 

The XML schema for this specification defines the structure, order, and allowable content of the 

information exchange package. 

208.2.1 Information separators 

All separators are defined by the W3C XML recommendations. The characters “<” and “>” are 

reserved exclusively for enclosing element tag names. Every element with an opening tag 

<Name> must have a closing tag of format </Name>. 

The XML schema defined for this specification defines the sequence of elements as well as the 

allowable content of the data. All elements must contain valid data. Assuming the schema

defines an element as optional, it should be omitted altogether rather than transmitting the 

element tags without any data content. 

Annex F provides a full set of examples of the use of XML elements in the standard. 

(Note: Table 7 from Part 1 has been intentionally omitted.) 

208.2.2 Record layout 

For all logical records, data elements are tagged according to XML rules. The format for each 

element shall consist of a tag name enclosed in angle brackets followed by data followed by a 

closing tag. For example <nc:IdentificationID>6</nc:IdentificationID>. Complex 

data elements contain other elements in a nested fashion; for example 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>6</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

The ordering of elements is strict. The text of this standard defines the order and nesting 

structure of elements. The schema also provides a W3C representation of the order and 

hierarchical structure of the XML content. 

208.2.3 International character sets 

All of the elements in the Type-1 transaction record must be recorded using the 7-bit ASCII code, 

which is the default character set code within a transaction. In order to affect data and 
Part 2 ANSI/NIST-ITL 2-2008

25

transaction interchanges between non-English-speaking or based agencies, a technique is 

available to encode information using character sets other than 7-bit ASCII. Fields/elements in 

theType-1 logical record and ASCII “LEN” (in Part 1 only) and “IDC” text fields/elements must still 

be encoded using 7-bit ASCII. But all other designated text fields/elements can be encoded 

using alternate character sets. The general mechanism for accomplishing this provides for 

backward compatibility with existing readers, supports multiple character sets in a single text 

string, and handles internationally accepted character sets and text order conventions such as 

ISO character sets, UTF-8, and Unicode. 

Character sets within a transaction may only be switched in user-defined data. Appropriate 

mechanisms must be defined as part of the user-defined data definition. 

The base-64 encoding scheme, found in email, shall be used for converting non-ASCII text into 

ASCII form. Annex C describes the use of the base-64 system. It is expected that this encoding 

scheme will be used to convert all (originally) binary image data to ASCII for transmission, and 

will also be used to convert non-ASCII data into ASCII data in user-defined data. 

All XML element tags including the “<” and “>” characters shall appear in the transaction as 7-bit 

ASCII characters. 

209 Type-1 transaction information record 

209.1 XML elements for the Type-1 transaction information record 

The following paragraphs describe the data contained in each XML element of the transaction 

information record. Table 207 provides a list of the elements for the transaction information 

record. It is required that all elements of the record are ordered in the sequence described. For 

each of the elements, Table 207 lists for cross-reference purposes the Part 1 mnemonic and field 

number, the “condition code” as being mandatory “M” or optional “O”, the Part 2 XML element 

name, and occurrence limits. An entry containing an "*" indicates that there is no established 

limit. Annex F contains an example of the use of the standard that illustrates the layout for a 

Type-1 logical record. (Table 207 corresponds to Table 8 in Part 1.) 

The Type-1 record shall be contained within this complex element: 

<itl:PackageInformationRecord> 

 [. . . Type 01 Record Content . . .] 

</itl:PackageInformationRecord> 

209.1.1 Record length 

Cross-reference: Part 1, Section 9.1.1 Field 1.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

209.1.2 Element <ansi-nist:RecordCategoryCode> 

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. 

<ansi-nist:RecordCategoryCode>01</ansi-nist:RecordCategoryCode> 
Part 2 ANSI/NIST-ITL 2-2008

26

Table 207 Type-1 transaction information record 

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:TransactionPriorityValue> 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 * 

209.1.3 Element <ansi-nist:Transaction> 

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. 

<ansi-nist:Transaction> 

[. . . Transaction elements . . .] 

</ansi-nist:Transaction> 
Part 2 ANSI/NIST-ITL 2-2008

27

209.1.3.1 Element <ansi-nist:TransactionDate> 

Cross-reference: Part 1, Section 9.1.5 Field 1.005: Date (DAT) 

This mandatory element shall contain the date that the transaction was initiated. The date shall 

appear as eight digits, separated by dashes, in the format YYYY-MM-DD. The YYYY characters 

shall represent the year the transaction was initiated; 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 February 29, 2008. The complete date must be 

a legitimate date. 

Complex element <ansi-nist:TransactionDate> shall have the simple element <nc:Date>, which 

will contain transaction date data. 

<ansi-nist:TransactionDate> 

 <nc:Date>2008-02-29</nc:Date> 

</ansi-nist:TransactionDate> 

209.1.3.2 Element <ansi-nist:TransactionDestinationOrganization> 

Cross-reference: Part 1, Section 9.1.7 Field 1.007: Destination agency identifier (DAI) 

This mandatory complex element shall contain the identifier of the administration or organization 

designated to receive the transmission. The size and data content of this element shall be userdefined and in accordance with the receiving agency. 

Element <ansi-nist:TransactionDestinationOrganization> shall have two child elements: a 

mandatory <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex 

element <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, 

which will contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> 

shall contain the datum for the text name of the organization. 

<ansi-nist:TransactionDestinationOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:TransactionDestinationOrganization> 

209.1.3.3 Element <ansi-nist:TransactionOriginatingOrganization> 

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 

originating the transaction. The size and data content of this element shall be user-defined and in 

accordance with the receiving agency. 

Element <ansi-nist:TransactionOriginatingOrganization> shall have two child elements: a 

mandatory <nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex 

element <nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, 

which will contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> 

shall contain the datum for the text name of the organization. 
Part 2 ANSI/NIST-ITL 2-2008

28

<ansi-nist:TransactionOriginatingOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:TransactionOriginatingOrganization> 

209.1.3.4 Element <ansi-nist:TransactionUTCDate> 

Cross-reference: Part 1, Section 9.1.14 Field 1.014: Date (GMT) 

This optional element provides a mechanism for expressing the date and time in terms of 

universal Greenwich Mean Time (GMT) units, also called Coordinated Universal Time (UTC), 

also called Zulu Time (Z). If used, the <ansi-nist:TransactionUTCDate> element contains the 

universal date that will be in addition to the local date contained in <ansi-nist:TransactionDate>. 

Use of the GMT element eliminates local time inconsistencies encountered when a transaction 

and its response are transmitted between two places separated by several time zones. The GMT 

provides a universal date and 24-hour clock time independent of time zones. It is represented as 

"YYYY-MM-DDTHH:MM:SSZ”, a 20-character string that is the concatenation of the date with the 

GMT, separated by the character “T”, and concluding with a “Z”. The “YYYY” characters shall 

represent the year of the transaction, the “MM” characters shall be the tens and units values of 

the month, the “DD” characters shall be the tens and units values of the day of the month, the 

“HH” characters represent the hour, the “MM” the minute, and the “SS” represents the second. 

The complete date shall not exceed the current date. 

Complex element <ansi-nist:TransactionUTCDate> shall have the simple element 

<nc:DateTime>, which will contain transaction date and time data. 

<ansi-nist:TransactionUTCDate> 

<nc:DateTime>2008-02-29T05:25:00Z </nc:DateTime> 

</ansi-nist:TransactionUTCDate> 

209.1.3.5 Element <ansi-nist:TransactionControlIdentification> 

Cross-reference: Part 1, Section 9.1.9 Field 1.009: Transaction control number (TCN) 

This mandatory element shall contain the Transaction Control Number as assigned by the 

originating agency. A unique alphanumeric control number shall be assigned to each transaction. 

For any transaction that requires a response, the respondent shall refer to this number in 

communicating with the originating agency. 

Complex element <ansi-nist:TransactionControlIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the transaction control identification datum. 

<ansi-nist:TransactionControlIdentification> 

 <nc:IdentificationID>56839</nc:IdentificationID> 

</ansi-nist:TransactionControlIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

29

209.1.3.6 Element <ansi-nist:TransactionControlReferenceIdentification> 

Cross-reference: Part 1, Section 9.1.10 Field 1.010: Transaction control reference (TCR) 

This optional element shall be used for responses that refer to the TCN of a previous transaction 

involving an inquiry or other action that required a response. 

Complex element <ansi-nist:TransactionControlReferenceIdentification> shall have the simple 

element <nc:IdentificationID>, which will contain the transaction control reference identification 

datum. 

<ansi-nist:TransactionControlReferenceIdentification> 

 <nc:IdentificationID>56839</nc:IdentificationID> 

</ansi-nist:TransactionControlReferenceIdentification> 

209.1.3.7 Element <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:IdentificationID> 

</ansi-nist:DomainVersionNumberIdentification> 

<ansi-nist:OrganizationName>NORAM 

</ansi-nist:OrganizationName> 

</ansi-nist:TransactionDomain> 

209.1.3.8 Element <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.1 Element <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 
Part 2 ANSI/NIST-ITL 2-2008

30

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 

more numeric characters (e.g., 19.69). This element is needed because the interchange of 

fingerprint information between systems of the same manufacturer may, in some instances, be 

more efficiently done at a transmitting resolution equal to the native scanning resolution of the 

system rather than at the minimum scanning resolution specified in this standard. For 

transactions that do not contain Type-3 through Type-7 fingerprint image records, the value shall 

be set to “00.00”. 

<ansi-nist:NativeScanningResolutionValue>19.69

</ansi-nist:NativeScanningResolutionValue> 

209.1.3.8.2 Element <ansi-nist:NominalTransmittingResolutionValue> 

Cross-reference: Part 1, Section 9.1.12 Field 1.012: Nominal transmitting resolution (NTR) 

This mandatory element shall specify the nominal transmitting resolution for the fingerprint or 

palmprint image(s) being exchanged. The value shall be expressed as five bytes specifying the 

transmitting resolution in pixels per millimeter. The resolution shall be expressed as two numeric 

characters followed by a decimal point and two more numeric characters (e.g., 19.69). The 

transmitting resolution shall be within the range specified by the transmitting resolution 

requirement. For transactions that do not contain Type-3 through Type-7 fingerprint image 

records, the value shall be set to “00.00”. 

<ansi-nist:NominalTransmittingValue>19.69

</ansi-nist:NominalTransmittingResolutionValue> 

209.1.3.9 Element <ansi-nist:TransactionMajorVersionValue> 

Cross-reference: Part 1, Section 9.1.2 Field 1.002: Version number (VER), first two characters 

This mandatory two-byte ASCII value shall be used to specify the current major version number 

of the standard implemented by the software or system creating the file. The entry in this element 

for the 2000 version is "03" and the entry for this 2007 version of the approved standard shall be 

"04". This version number addresses the optional inclusion of the logical Type-10 

through Type-17 and Type-99 image records. 

<ansi-nist:TransactionMajorVersionValue>04 

</ansi-nist:TransactionMajorVersionValue> 

209.1.3.10 Element <ansi-nist:TransactionMinorVersionValue> 

Cross-reference: Part 1, Section 9.1.2 Field 1.002: Version number (VER), last two characters 

This mandatory two-byte ASCII value shall be used to specify the current minor version number 

of the standard implemented by the software or system creating the file. The initial revision 

number for a version shall be "00”. 

<ansi-nist:TransactionMinorVersionValue>00 

</ansi-nist:TransactionMinorVersionValue> 
Part 2 ANSI/NIST-ITL 2-2008

31

209.1.3.11 Element <ansi-nist:TransactionPriorityValue> 

Cross-reference: Part 1, Section 9.1.6 Field 1.006: Priority (PRY) 

This optional element shall contain a single information character to designate the urgency with 

which a response is desired. The values shall range from “1” to “9”, with "1" denoting the highest 

priority. The default value shall be defined by the agency receiving the transaction. 

<ansi-nist:TransactionPriorityValue>5

</ansi-nist:TransactionPriorityValue> 

209.1.3.12 Element <ansi-nist:TransactionCategoryCode> 

Cross-reference: Part 1, Section 9.1.4 Field 1.004: Type of transaction (TOT) 

This mandatory element shall contain an identifier, which designates the type of transaction and 

subsequent processing that this file should be given. (Note: Type of Transaction shall be in 

accordance with definitions provided by the receiving agency.) 

<ansi-nist:TransactionCategoryCode>CAR

</ansi-nist:TransactionCategoryCode> 

209.1.3.13 Element <ansi-nist:TransactionContentSummary> 

Cross-reference: Part 1, Section 9.1.3 Field 1.003: File content (CNT) 

This mandatory complex element shall list and identify each of the logical records in the file by 

record type. It also specifies the order in which the remaining logical records shall appear in the 

file. It shall consist of three child elements. The first two have one occurrence each. The third 

complex element child is repeated, one occurrence for each logical record in the package 

following this Type-1 information record. 

The first child element, <ansi-nist:ContentFirstRecordCategoryCode>, shall relate to this Type-1 

Transaction record. The value of this child element shall be the single character "1" (selected 

from Table 204) indicating that this is a Type-1 record consisting of header information. 

The second child element, <ansi-nist:ContentRecordCount>, shall be the sum of the Type-2 

through Type-99 logical records contained in this exchange package. This is also a count of the 

number of occurrences of the third child element <ansi-nist:ContentRecordSummary>. 

The third child element, <ansi-nist:ContentRecordSummary>, is a complex element each 

occurrence of which relates to a single Type-2 through Type-99 logical record contained in the 

package. Two child elements shall comprise each occurrence of <ansinist:ContentRecordSummary>. The first child element, <ansi-nist:ImageReferenceIdentification> 

shall be the IDC associated with the logical record. The IDC shall be a positive integer equal to 

or greater than zero. The second child element, <ansi-nist:RecordCategoryCode>, shall be the 

record identifier character(s) chosen from Table 204 that identifies the record type. The complex 

element <ansi-nist:ContentRecordSummary> shall be repeated once for every record in the 

exchange package except record Type-1. 

Complex element <ansi-nist:ImageReferenceIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the IDC datum. 
Part 2 ANSI/NIST-ITL 2-2008

32

<ansi-nist:TransactionContentSummary> 

<ansi-nist:ContentFirstRecordCategoryCode>1

</ansi-nist:ContentFirstRecordCategoryCode> 

<ansi-nist:ContentRecordCount>2 

</ansi-nist:ContentRecordCount> 

<ansi-nist:ContentRecordSummary> 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>00</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

<ansi-nist:RecordCategoryCode>2 

</ansi-nist:RecordCategoryCode> 

</ansi-nist:ContentRecordSummary> 

<ansi-nist:ContentRecordSummary> 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>01</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

<ansi-nist:RecordCategoryCode>15 

</ansi-nist:RecordCategoryCode> 

</ansi-nist:ContentRecordSummary> 

</ansi-nist: TransactionContentSummary> 

209.1.3.14 Element <ansi-nist:TransactionCharacterSetDirectory> 

Cross-reference: Part 1, Section 9.1.15 Field 1.015: Directory of character sets (DCS) 

This optional complex element contains information about a single character set other than 7-bit 

ASCII that may appear within this package. Multiple occurrences of this element may be used to 

represent a directory or list of character sets other than 7-bit ASCII that may appear. 

This element shall contain three child elements. The first information item, <ansinist:CharacterSetCommonNameCode> shall be the common name for the character set 

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 

for the character set index number that references an associated character set throughout the 

transaction exchange package. The optional third information item, <ansinist:CharacterSetVersionIdentification>, is the specific version of the character set used. 

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 

to the correct font family. Table 208 lists the reserved named character sets and their associated 

3-character index numbers. 

The complex element <ansi-nist:TransactionCharacterSetDirectory> may appear multiple times, 

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 

<nc:IdentificationID>, which will contain the version datum. 
Part 2 ANSI/NIST-ITL 2-2008

33

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 

<ansi-nist:TransactionCharacterSetDirectory> 

<ansi-nist:CharacterSetCommonNameCode>UNICODE

</ansi-nist:CharacterSetCommonNameCode> 

<ansi-nist:CharacterSetIndexCode>002 

</ansi-nist:CharacterSetIndexCode> 

<ansi-nist:CharacterSetVersionIdentification>

<nc:IdentificationID>000<nc:IdentificationID> 

</ansi-nist:CharacterSetVersionIdentification> 

</ansi-nist:TransactionCharacterSetDirectory> 

209.2 End of transaction information record Type-1 

The Type-1 logical record shall end with the XML tag </itl:PackageInformationRecord>. 

210 Type-2 user-defined descriptive text record 

Type-2 logical records shall contain textual information relating to the subject of the exchange 

package and shall be represented in an ASCII format. This record may include such information 

as the state or FBI numbers, physical characteristics, demographic data, and the subject’s 

criminal history. Every exchange package usually contains one or more Type-2 records, which is 

dependent upon the entry in the <ansi-nist:TransactionCategoryCode> element (Part 1 Type-ofTransaction, field 1.004, TOT). Table 209 lists the contents of the records. (This table has no 

equivalent in Part 1.) 

210.1 XML elements for Type-2 logical records 

Type-2 records shall be contained within this complex element: 

<itl:PackageDescriptiveTextRecord> 

 [. . . Type 02 Record Content . . .] 

</itl:PackageDescriptiveTextRecord> 

The first two data elements of the Type-2 record are mandatory, ordered, and defined by this 

standard. The remaining content of the record(s) shall conform to the format, content, and 

requirements of the subscribed Domain Name (DOM), <ansi-nist:TransactionDomain>, used by 

the agency to which the exchange package is being sent. 
Part 2 ANSI/NIST-ITL 2-2008

34

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 <itl:DomainDefinedDescriptiveText> 0 1 

 O <itl:OtherDescriptiveText> 0 1 

210.1.1 Record length 

Cross-reference: Part 1, Section 10.1.1 Field 2.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

210.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-2 record, it shall contain a value of 02. 

<ansi-nist:RecordCategoryCode>02</ansi-nist:RecordCategoryCode> 

210.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 10.1.2 Field 2.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the user-defined text data contained in 

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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>00</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

35

210.1.4 Element <itl:UserDefinedDescriptiveText> 

Cross-reference: Part 1, Section 10.1.3 Fields 2.003 and above: User-defined fields 

This is a optional complex element. The user-defined content elements are nested within, as 

described in the subsections below. 

<itl:UserDefinedDescriptiveText> 

[. . . Domain and other descriptive elements . . .] 

</itl:UserDefinedDescriptiveText> 

210.1.4.1 Element <itl:DomainDefinedDescriptiveText> 

This element shall only contain content defined by the Domain owner specified in the Type-1 

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 

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 

208.2.2. 

Complex element <itl:DomainDefinedDescriptiveText> is abstract, and as such is unusable by 

itself. Implementers should define, in an extension schema, a substitution element containing 

user-defined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="DomainDefinedDescriptiveText" 

 substitutionGroup="itl:DomainDefinedDescriptiveText" 

 type="user-domain:DomainDefinedDescriptiveTextType"/> 

<xsd:complexType name="DomainDefinedDescriptiveTextType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:DomainDefinedDescriptiveText> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:DomainDefinedDescriptiveText> 

210.1.4.2 Element <itl:OtherDescriptiveText> 

This element shall contain additional content not defined by a Domain owner, but necessary for 

information exchange between certain parties. Individual XML elements, required for given 

transaction types, including tag names and content, shall conform to the specifications set forth 

by the agency to whom the exchange package is being sent. Each user-defined XML element 
Part 2 ANSI/NIST-ITL 2-2008

36

used in the Type-2 record and its format shall conform to the requirements contained in Section 

208.2.2. 

Complex element <itl:OtherDescriptiveText> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="OtherDescriptiveText" 

 substitutionGroup="itl:OtherDescriptiveText" 

 type="user-domain:OtherDescriptiveTextType"/> 

<xsd:complexType name="OtherDescriptiveTextType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:OtherDescriptiveText> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:OtherDescriptiveText> 

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

The Type-2 logical record shall end with the XML tag </itl:PackageDescriptiveTextRecord>. 

210.3 Additional user-defined descriptive text records 

Additional Type-2 records may be included in the exchange package. For each additional userdefined descriptive text record present, the <ansi-nist:RecordCategoryCode> and <ansinist:ImageReferenceIdentification> elements will be required together with additional Type-2 

content needed. 

211 Type-3 through Type-6 fingerprint image records 

211.1 General 

As discussed in Section 208.1.3, the Type-3 through Type-6 logical records are based on the use 

of a captured fingerprint image obtained using a scanning resolution that is at least as great as 

the minimal scanning resolution of 19.69 ppmm (500 ppi). The records differ from each other 

based on the properties of the transmitted image - data type (grayscale or binary) and resolution 

(scanning resolution or half-resolution). 
Part 2 ANSI/NIST-ITL 2-2008

37

All four of the logical records use the same XML element structure for the record and exchange of 

data. For this Part 2 version of the standard, all data are represented as ASCII data. The data 

values are not required to be fixed length. The order in which the XML elements must appear is 

defined in the subsections that follow. Table 210 lists the contents of the records. (Table 210 

corresponds to Table 10 in Part 1.) 

211.2 Types 3-6 logical record XML elements 

The Type-3 record shall be contained within this complex element: 

<itl:PackageLowResolutionGrayscaleImageRecord> 

 [. . . Type 03 Record Content . . .] 

</itl:PackageLowResolutionGrayscaleImageRecord> 

The Type-4 record shall be contained within this complex element: 

<itl:PackageHighResolutionGrayscaleImageRecord> 

 [. . . Type 04 Record Content . . .] 

</itl:PackageHighResolutionGrayscaleImageRecord> 

The Type-5 record shall be contained within this complex element: 

<itl:PackageLowResolutionBinaryImageRecord> 

 [. . . Type 05 Record Content . . .] 

</itl:PackageLowResolutionBinaryImageRecord> 

The Type-6 record shall be contained within this complex element: 

<itl:PackageHighResolutionBinaryImageRecord> 

 [. . . Type 06 Record Content . . .] 

</itl:PackageHighResolutionBinaryImageRecord> 

The following descriptions for each element in Table 210 are applicable to logical record types 3-

6. 

211.2.1 Record length 

Cross-reference: Part 1, Section 11.2.1: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

211.2.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-3 through Type-6 records, it shall contain a value of 03, 04, 05, or 06, 

respectively. 

<ansi-nist:RecordCategoryCode>03</ansi-nist:RecordCategoryCode> 

211.2.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 11.2.2: Image designation character (IDC) 

This mandatory complex element shall be used to identify the image data contained in 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. 
Part 2 ANSI/NIST-ITL 2-2008

38

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>01</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

Table 210 Type 3-6 record layout 

Part 1 

Ident

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 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

data 

M <nc:BinaryBase64Object> 1 1 

 M <ansi-nist:ImageCaptureDetail> 1 1 

ISR M <ansi-nist:CaptureResolutionCode> 1 1 

GCA/

BCA 

M <ansi-nist:ImageCompressionAlgorithmCode> 1 1 

HLL M <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 1 1 

VLL M <ansi-nist:ImageVerticalLineLengthPixelQuantity> 1 1 

FGP M <ansi-nist:FingerprintImagePosition> 1 1 

FGP M <ansi-nist:FingerPositionCode> 1 6 

IMP M <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 1 1 

211.2.4 Element <ansi-nist:FingerprintImage> 

This is a mandatory complex element. All of the remaining elements in the Type-3 through Type6 records are nested within, as described in the subsections below. 

<ansi-nist:FingerprintImage> 

[. . . Image elements . . .] 

</ansi-nist:FingerprintImage> 

211.2.4.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 11.2.9: Image data 

This mandatory element shall contain the image data. Each pixel of the uncompressed grayscale 

image shall be quantized to eight bits (256 gray levels) contained in a single byte. For the 
Part 2 ANSI/NIST-ITL 2-2008

39

exchange of an uncompressed binary image, eight pixels shall be left justified and packed into a 

single unsigned byte. The most significant bit of the byte shall be the first of the eight pixels 

scanned. If compression is used, the pixel data shall be compressed in accordance with the 

compression technique specified in the <ansi-nist:ImageCompressionAlgorithmCode> element 

(CGA / BCA). 

The image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

211.2.4.2 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains the single child element described in the subsection 

below. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

211.2.4.2.1 Element <ansi-nist:CaptureResolutionCode> 

Cross-reference: Part 1, Section 11.2.5: Image scanning resolution (ISR) 

This element is mandatory. 

• For Type-3 or Type-5 logical records, it shall contain the ASCII character “0” if half the 

minimum scanning resolution is used and a “1” if half the native scanning resolution is used; 

• For Type-4 or Type-6 logical records, it shall contain the ASCII character “0” if the minimum 

scanning resolution is used and a “1” if the native scanning resolution is used. 

See Section 206.2 where it is stated that the preferred transmitting resolution shall be the same 

as the minimum scanning resolution. 

<ansi-nist:CaptureResolutionCode>1 

</ansi-nist:CaptureResolutionCode> 

211.2.4.3 Element <ansi-nist:ImageCompressionAlgorithmCode> 

Cross-reference: Part 1, Section 11.2.8: Compression algorithm (GCA / BCA) 

This element is mandatory. It shall be used to specify the type of compression algorithm used (if 

any). The ASCII character “0” denotes no compression. Otherwise, the contents of this byte 

shall be the ASCII representation of the number allocated to the particular compression technique 

used by the interchange parties. The specific code for each algorithm can be found in Table 201 

or Table 202 or from the domain registrar who will maintain a registry relating these numbers to 

the compression algorithms. 

• For the Type-3 logical record, there is no recommendation for a commonly used grayscale 

compression algorithm; 

• For the Type-4 logical record, the Wavelet Scalar Quantization (WSQ) or the JPEG 10918 

standard alogithms are recommended for compressing the high-resolution grayscale data; 

• For Type-5 or Type 6 logical records, the Facsimile ANSI/EIA 538-1988 algorithm is 

recommended for the lossless compression and decompression of binary fingerprint images. 
Part 2 ANSI/NIST-ITL 2-2008

40

<ansi-nist:ImageCompressionAlgorithmCode>0

</ansi-nist:ImageCompressionAlgorithmCode> 

211.2.4.4 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 11.2.6: Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

211.2.4.5 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

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 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

211.2.4.6 Element <ansi-nist:FingerprintImagePosition> 

Cross-reference: Part 1, Section 11.2.4: Finger position (FGP) 

This mandatory complex element contains the child element(s) described in the subsection 

below. This element shall contain possible finger positions for the image. 

<ansi-nist:FingerprintImagePosition> 

[. . . Finger position code element(s) . . .] 

</ansi-nist:FingerprintImagePosition> 

211.2.4.6.1 Element <ansi-nist:FingerPositionCode> 

Cross-reference: Part 1, Section 11.2.4: Finger position (FGP) 

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 <ansinist:FingerPositionCode>, up to five additional finger positions may be referenced by repeating 

occurrences of <ansi-nist:FingerPositionCode>. Each occurrence of this element shall contain 

one possible finger position. The decimal code number corresponding to the finger position shall 

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 

finger positions. (Table 212 is the same as Table 12 in Part 1.) 

The code “0”, for “Unknown Finger”, shall be used to reference every finger position from one 

through ten. 
Part 2 ANSI/NIST-ITL 2-2008

41

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 

occurrences of this element are permitted. 

<ansi-nist:FingerPositionCode>12</ansi-nist:FingerPositionCode> 

<ansi-nist:FingerPositionCode>11</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> 

211.2.4.7 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

Cross-reference: Part 1, Section 11.2.3: Impression type (IMP) 

This element is mandatory. The code selected from Table 211, describing the manner by which 

the fingerprint image information was obtained, shall be entered in this element. (Table 211 is the 

same as Table 11 in Part 1.) 

<ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1

</ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

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 

Note: Table 211 is also used to describe the manner by which palm image information was 

obtained. 
Part 2 ANSI/NIST-ITL 2-2008

42

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 

Note: Finger codes 15 and 19 apply to tagged-field fingerprint image records. 

211.3 End of fixed-resolution fingerprint image record 

The Type-3 logical record shall end with the XML tag 

</itl:PackageLowResolutionGrayscaleImageRecord>. 

The Type-4 logical record shall end with the XML tag 

</itl:PackageHighResolutionGrayscaleImageRecord>. 

The Type-5 logical record shall end with the XML tag 

</itl:PackageLowResolutionBinaryImageRecord>. 

The Type-6 logical record shall end with the XML tag 

</itl:PackageHighResolutionBinaryImageRecord>. 

211.4 Additional fixed-resolution image records 

Typically, for each of these logical record types, there may be up to thirteen additional images 

contained within the exchange package. For each additional image, a logical record is required. 
Part 2 ANSI/NIST-ITL 2-2008

43

212 Type-7 user-defined image record 

Type-7 logical records shall contain user-defined image information relating to the exchange 

package submitted for processing. This record type was originally defined to handle 

miscellaneous images such as those pertaining to mugshots, latent prints, palmprints, wrists, 

toes, soles, etc., that were not addressed elsewhere in the standard. However, it is not intended 

that the use of the Type-7 record is restricted by the existence of other record types in this 

standard. 

Type-7 records are still commonly used for the exchange of latent fingerprints. But since its 

creation, other record types have also been formally defined and are used by this standard to 

handle mugshots (Type-10), latent fingerprint images (Type-13), variable-resolution fingerprint 

images (Type-14), palmprint images (Type-15), and other user-defined image records (Type-16). 

These images shall consist of scanned pixels that may be either binary or grayscale output. Each 

grayscale pixel value shall be expressed as an unsigned byte. A value of “0” shall be used to 

define a black pixel, and an unsigned value of “255” shall be used to define a white pixel. For 

binary pixels, a value of “0” shall represent a white pixel, and a value of “1” shall represent a black 

pixel. If compression is used, the algorithm shall be the same as that specified for Type-3 

through Type-6 logical records. Table 213 lists the contents of the records. (This table has no 

equivalent in Part 1.) 

212.1 XML elements for Type-7 logical records 

Type-7 records shall be contained within this complex element: 

<itl:PackageUserDefinedImageRecord> 

 [. . . Type 07 Record Content . . .] 

</itl:PackageUserDefinedImageRecord> 

The XML Part 2 version of the Type-7 logical record shall be composed completely of ASCII data. 

The first two data elements of the Type-7 record are defined by this standard. Remaining record 

content shall conform to the requirements set forth by the agency receiving the exchange 

package. 

Table 213 Type-7 user-defined image record 

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 ANSI/NIST-ITL 2-2008

44

212.1.1 Record length 

Cross-reference: Part 1, Section 12.1.1: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

212.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-7 record, it shall contain a value of 07. 

<ansi-nist:RecordCategoryCode>07</ansi-nist:RecordCategoryCode> 

212.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 12.1.2: Image designation character (IDC) 

This mandatory complex element shall be used to identify the image data contained in 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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>05</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

212.1.4 Element <itl:RecordImage> 

Cross-reference: Part 1, Section 12.1.3: User-defined fields for Type-7 logical record 

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 

conform to the specifications set forth by the agency to whom the package is being sent. 

Complex element <itl:RecordImage> is abstract, and as such is unusable by itself. Implementers 

should define, in an extension schema, a substitution element containing user-defined child 

elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedImageRecord" 

 substitutionGroup="itl:RecordImage" 

 type="user-domain:UserDefinedImageRecordType"/> 

<xsd:complexType name="UserDefinedImageRecordType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 
Part 2 ANSI/NIST-ITL 2-2008

45

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedImageRecord> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedImageRecord> 

212.2 End of Type-7 user-defined image record 

The Type-7 logical record shall end with the XML tag </itl:PackageUserDefinedImageRecord>. 

212.3 Additional user-defined descriptive text records 

Additional images may be described within the exchange package. For each additional image, a 

Type-7 logical record is required. 

213 Type-8 signature image record 

Type-8 logical records shall contain either scanned or vectored signature data. Each Type-8 

record shall cover an area of up to 1000 mm2

. 

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 

be a binary representation quantized to two levels. 

If vectored signature data is present, it shall be expressed as a series of numbers. 

213.1 XML elements for the Type-8 logical record 

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. 

Elements containing entries in the “IMG” column are only applicable to that image type. An entry 

of “IMG” applies to a scanned signature image, and an entry of "VEC" applies to vectored 

signature data. (Table 214 corresponds to Table 13 in Part 1.) 

The Type-8 record shall be contained within this complex element: 

<itl:PackageSignatureImageRecord> 

 [. . . Type 8 Record Content . . .] 

</itl:PackageSignatureImageRecord> 

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 <ansinist:RecordCategoryCode>, for example). 

213.1.1 Record length 

Cross-reference: Part 1, Section 13.1.1: Logical record length (LEN) 
Part 2 ANSI/NIST-ITL 2-2008

46

There is no corresponding Part 2 XML element. 

213.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-8 record, it shall contain a value of 08. 

<ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 

213.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 13.1.2: Image designation character (IDC) 

This mandatory complex element shall be used to identify the image data contained in 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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>6</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

Table 214 Type-8 record layout 

Part 1 

Ident

Cond 

code 

Part 2 XML Element Name IMG Occur count 

 min Max 

LEN 0 

 M <ansi-nist:RecordCategoryCode> 1 1 

IDC M <ansi-nist:ImageReferenceIdentification> 1 1 

 M <ansi-nist: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 

* Mandatory (or optional) for a particular image type 
Part 2 ANSI/NIST-ITL 2-2008

47

213.1.4 Element <ansi-nist:SignatureImage> 

All of the remaining elements in the Type-8 record are nested within, as described in the 

subsections below. 

<ansi-nist:SignatureImage> 

[. . . Signature image, or vectored data elements . . .] 

</ansi-nist:SignatureImage> 

213.1.4.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 13.1.8.1 and 13.1.8.2: Signature image data (DATA), scanned 

images 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element is “0” or “1”, this element is 

mandatory. This element shall not appear in a record if <ansinist:SignatureRepresentationCode> (SRT) element is “2”. 

This element shall contain all of the data from a scanned signature image. The binary image data 

shall be converted to ASCII characters using the Base64 encoding algorithm. 

Uncompressed scanned image data 

If the <ansi-nist:SignatureRepresentationCode> (SRT) contains the value “0”, then this element 

shall contain the uncompressed scanned binary image data for the signature. In uncompressed 

mode, the data shall be packed at eight pixels per byte. 

Compressed scanned image data 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element contains the value “1”, then this 

element shall contain the scanned binary image data for the signature in compressed form using 

the ANSI/EIA-538-1988 facsimile compression algorithm. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

213.1.4.2 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains the single child element described in the subsection 

below. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

213.1.4.2.1 Element <ansi-nist:CaptureResolutionCode> 

Cross-reference: Part 1, Section 13.1.5: Image scanning resolution (ISR) 

This element is mandatory. It shall contain an ASCII “0” if the minimum scanning resolution is 

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. 
Part 2 ANSI/NIST-ITL 2-2008

48

<ansi-nist:CaptureResolutionCode>1 

</ansi-nist:CaptureResolutionCode> 

213.1.4.3 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

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 

number of pixels contained on a single horizontal line of the transmitted signature image. For 

vectored signature data, this element shall contain the ASCII value of “00”. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

213.1.4.4 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 13.1.7: Vertical line length (VLL) 

This element is mandatory. For scanned signature data, this element shall be used to specify the 

number of horizontal lines contained in the transmitted signature image. For vectored signature 

data, this element shall contain the ASCII value of “00”. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

213.1.4.5 Element <ansi-nist:SignatureImageVectorRepresentation> 

Cross-reference: Part 1, Section 13.1.8.3: Signature image data (DATA), Vectored image data 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element is “2”, this element is mandatory. 

This element shall not appear in a record if <ansi-nist:SignatureRepresentationCode> (SRT) 

element is “0” or “1”. 

Vectored image data 

If the <ansi-nist:SignatureRepresentationCode> (SRT) element contains the value of “2”, then this 

complex parent element shall contain a list of vector elements describing the pen position and 

pen pressure of line segments within the signature. Each vector element shall be contained in 

the complex child element <ansi-nist:SignatureImageVector> described in the subsection below. 

The complex parent element <ansi-nist:SignatureImageVectorRepresentation> contains all the 

occurrences of the child element: 

<ansi-nist:SignatureImageVectorRepresentation> 

[. . . Vector elements . . .] 

</ansi-nist:SignatureImageVectorRepresentation> 

213.1.4.5.1 Element <ansi-nist:SignatureImageVector> 

Each occurrence of <ansi-nist:SignatureImageVector> shall contain information describing the 

coordinates of the end point of a vector, and a pen pressure setting. 
Part 2 ANSI/NIST-ITL 2-2008

49

A number between “0” and “255” contained in the <ansi-nist:VectorPenPressureValue> element 

shall represent the pen pressure. This shall be a constant pressure until the next vector becomes 

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 

least recordable pressure for a particular device, while the value “254” shall represent the 

maximum recordable pressure for that device. To denote the end of the vector list, the value 

“255” shall be inserted in the <ansi-nist:VectorPenPressureValue> element. 

The <ansi-nist:VectorPositionVerticalCoordinateValue> shall hold the Y coordinate of the pen 

position. The <ansi-nist:VectorPositionHorizontalCoordinateValue> shall hold the X coordinate of 

the pen position. Both the X and Y coordinates shall be expressed in units of .0254 mm (.001 

inches) referenced from the bottom leftmost corner of the signature. Positive values of X shall 

increase from left to right and positive values of Y shall increase from bottom to top. 

The <ansi-nist:SignatureImageVector> element may be repeated as many times as necessary to 

describe a signature image. 

<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> 

213.1.4.6 Element <ansi-nist:SignatureRepresentationCode> 

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 

compressed, an ASCII “1” if the image is scanned and compressed, and an ASCII “2” if the image 

is vector data. 

<ansi-nist:SignatureRepresentationCode>0

</ansi-nist:SignatureRepresentationCode> 

213.1.4.7 Element <ansi-nist:SignatureCategoryCode> 

Cross-reference: Part 1, Section 1.1.3: Signature Type (SIG) 

This element is mandatory. Its value shall be an ASCII “0” for the signature image of the subject 

or an ASCII “1” for the signature image of the official processing the transaction. 

<ansi-nist:SignatureCategoryCode>0 

</ansi-nist:SignatureCategoryCode> 

213.2 End of Type-8 signature image record 

The Type-8 logical record shall end with the XML tag </itl:PackageSignatureImageRecord>. 
Part 2 ANSI/NIST-ITL 2-2008

50

213.3 Additional variable-resolution latent image records 

One more signature may be described within the file. For an additional signature, a Type-8 

logical record is required. 

214 Type-9 minutiae data record 

Type-9 records shall contain XML elements and ASCII content describing minutiae and related 

information encoded from a finger or palm. For a tenprint search transaction, generally there may 

be up to ten of these Type-9 records in an exchange package, each of which shall be for a 

different finger. There may be up to eight records for palmprint searches - each record 

representing a different area on one of the two palms. The Type-9 record shall also be used to 

exchange the minutiae information from latent finger or palm images between similar or different 

systems. 

Minutiae information may be extracted and encoded in any of several different manners 

depending on the system that is used to scan an image, extract minutiae, and encode the 

minutiae template. This standard defines an abstract XML element called <itl:RecordMinutiae>. 

Any number of concrete implementations can be defined to substitute for <itl:RecordMinutiae>. 

This standard defines a NIST “Standard format.” The concrete complex element <itl:Minutiae> 

substitutes for the abstract <itl:RecordMinutiae> creating a minutiae representation based on the 

conventions and parameters described below in Section 214.1. 

Additional substitution elements may be defined by vendors to represent minituae differently. 

Alternative elements constructed to substitute for <itl:RecordMinutiae> will allow vendors to 

encode minutiae data and any additional required characteristic or feature data in accordance 

with their own system’s specific hardware and software configuration. The registration of blocks 

of substitution elements to specific vendors is controlled by the domain registrar responsible for 

the implementation domain. By default, this shall be the registrar for the North American Domain. 

Table 14 in the Part 1 version of this specification identifies vendors who have Part 1 alternate 

representations. None, as of this publication, has a Part 2 XML representation. 

214.1 Minutiae and other information descriptors (Standard Format) 

214.1.1 Minutiae type identification 

This standard defines four identifier characters that are used to describe the minutia type. These 

are listed in Table 215. (Table 215 is the same as Table 15 in Part 1.) A ridge ending shall be 

designated Type A. It occurs at the point on a fingerprint or palmprint that a friction ridge begins 

or ends without splitting into two or more continuing ridges. The ridge must be longer than it is 

wide. A bifurcation shall be designated Type B. It occurs at the point that a ridge divides or splits 

to form two ridges that continue past the point of division for a distance that is at least equal to the 

spacing between adjacent ridges at the point of bifurcation. A minutia shall be designated Type 

C, a compound type, if it is either a trifurcation (a single ridge that splits into three ridges) or a 

crossover (two ridges that intersect). If a minutia cannot be clearly categorized as one of the 

above three types, it shall be designated as undetermined, Type D. 
Part 2 ANSI/NIST-ITL 2-2008

51

Table 215 Minutiae types 

Type Description 

A Ridge ending 

B Bifurcation 

C Compound (trifurcation or crossover) 

D Type undetermined 

214.1.2 Minutia numbering 

Each minutia shall be identified by an index number that is assigned to it. The numbering shall 

begin at “1” and be incremented by “1” for as many times as there are minutiae encountered. 

This allows each minutia to be uniquely identified. The numbering of the minutiae shall be 

unordered. 

214.1.3 Minutiae ridge counts 

As required, ridge counts shall be determined from each minutia in a fingerprint or palmprint to 

certain other neighboring minutiae. When this occurs, ridge counts between designated minutiae 

shall be associated with the applicable index numbers so as to ensure maintenance of the proper 

relationships. Rules for identifying neighboring minutiae and the method to be used for counting 

the intervening ridge crossingsare not part of this “standard format.” 

214.1.4 Minutiae coordinate system 

The relative position of minutiae entered in Type-9 records shall be expressed as positive 

integers in units of 0.01 mm (0.00039 in) in a Cartesian coordinate system located in Quadrant 1. 

In this coordinate system, values of X increase from left to right and values of Y increase from 

bottom to top. 

Note (Informative) – This standard follows the practice of placing the origin at the lower left corner 

for describing the location of minutiae. This is in contrast to the placement of the origin in the 

upper left-hand corner which is conventionally used for images. 

For encoded minutiae from fingerprints, values for both X and Y are equal to or greater than 

"0000" and are less than "5000". This range of units converts to 5 cm (1.97”) in both the 

horizontal and vertical directions. If the conversion to this coordinate system is from a system 

that normally centers the fingerprint image during the registration process, that center position 

shall be assigned the values X = 2500, Y = 2500. Figure 3 illustrates the defined coordinate 

system for a fingerprint using the complex XML element for the “standard format,” <itl:Minutiae>. 

For encoded minutiae from a palmprint, values of both X and Y are equal to or greater than 

"0000" and are less than "14000" and “21000”, respectively. This range of units converts to 14 

cm (5.51”) in the horizontal and 21 cm (8.27”) in the vertical directions. 

The relative orientation, Theta, of a ridge ending or a bifurcation shall be expressed as positive 

integers in units of degrees from “0” to “359”. Theta is defined as the angle between the 

horizontal axis of the coordinate system and the direction that a ridge ending points, assuming 

that a ridge ending is analogous to a pointing finger. A ridge ending that is formed by a ridge 

lying parallel to the X axis, and ending in the direction of increasing values of X, shall have an 
Part 2 ANSI/NIST-ITL 2-2008

52

orientation of zero degrees. Counterclockwise rotation of this ridge about the ridge ending shall 

cause the value of Theta to increase. A ridge ending pointing due east has a direction of zero 

degrees, due north 90 degrees, and so forth. No orientation value shall be assigned to an 

undetermined or compound type of minutiae; therefore, a value of "000" shall be entered for 

Theta in the Type-9 logical record entry. 

A bifurcation may be converted to a ridge ending by logical inversion, i.e., transposing the identity 

of ridges and valleys. The orientation of a bifurcation is expressed as if this inversion had 

occurred. This convention causes no significant change in the orientation of a minutia if it 

appears as a ridge ending in one impression of a fingerprint and as a bifurcation in another 

impression of the same fingerprint. 

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 

Figure 3 Minutiae coordinate system 

The exact features or characteristics of a minutia that are used to establish its position and 

orientation are system-dependent and outside the scope of this standard. 

214.2 XML elements for Type-9 logical record 

Type-9 records shall be contained within this complex element: 

<itl:PackageMinutiaeRecord> 

 [. . . Type 9 Record Content . . .] 

</itl:PackageMinutiaeRecord> 

All XML elements and content of the Type-9 records shall be recorded as ASCII text. No binary 

data are defined in the “standard format,” so there is no conversion of binary data required using 

Base64 encoding. Vendors who define alternate representations shall create substitute elements 

that shall be recorded as ASCII text. The abstract element <itl:RecordMinutiae> is a placeholder 

for a specific vendor representation. The concrete element <itl:Minutiae> is a substitute for 
Part 2 ANSI/NIST-ITL 2-2008

53

<itl:RecordMinutiae> and provides a common or generic manner of encoding minutiae and other 

characteristic data. The contents of <itl:Minutiae> are formatted in accordance with the 

conventions described above. 

Although this logical record type can also be used to accommodate a variety of methods used by 

different AFIS vendors for encoding minutiae data according to their particular requirements, each 

vendor implementation must appear as a substitute for the abstract element <itl:RecordMinutiae>. 

All other structure of the Type-9 record is required including the outer XML element 

<itl:PackageMinutiaeRecord>, and its first four elements <ansi-nist:RecordCategoryCode>, 

<ansi-nist:ImageReferenceIdentification, <ansi-nist:MinutiaeImpressionCaptureCategoryCode> 

and <ansi-nist:MinutiaeFormatNISTStandardIndicator>. None of the content of <itl:Minutiae> is 

required to be present in specific vendor implementations. 

Within a Type-9 logical record, entries shall be provided in XML elements. Two tables are 

presented. (Neither exist in Part 1.) Table 216a is the structure of the Type-9 record for all 

implementations, NIST standard and vendor alternatives. Table 216b is the structure of the NIST 

standard representation. For each element of the Type-9 record, a “condition code” is shown as 

being mandatory “M” or optional “O”, or not allowed “X”. XML tag name and occurrence limits are 

shown. 

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 <ansinist:RecordCategoryCode>, for example). 

214.2.1 Record length 

Cross-reference: Part 1, Section 14.2.1 Field 9.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

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

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 

Note: At least one occurrence of a concrete substitute for the abstract element is 

required. 
Part 2 ANSI/NIST-ITL 2-2008

54

214.2.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-9 record, it shall contain a value of 09. 

<ansi-nist:RecordCategoryCode>09</ansi-nist:RecordCategoryCode> 

Table 216b Type-9 NIST Standard minutiae representation 

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 

 M <itl:MinutiaeNISTStandard> 1 1 

MRC M 9.012 <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 

214.2.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 14.2.2 Field 9.002: Image designation character (IDC) 

This mandatory complex element shall be used for the identification and location of the minutiae 

data. The content of this element shall match the <ansi-nist:ImageReferenceIdentification> found 

in the <ansi-nist:TransactionContentSummary> element of the Type-1 record. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>00</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

55

214.2.4 Element <ansi-nist:MinutiaeImpressionCaptureCategoryCode> 

Cross-reference: Part 1, Section 14.2.3 Field 9.003 Impression type (IMP) 

This mandatory element shall contain a one- or two-byte ASCII value describing the manner by 

which the fingerprint or palmprint image information was obtained. The ASCII value for the 

proper code as selected from Table 211 for finger impressions and palm impressions shall be 

entered in this element to signify the impression type. 

<ansi-nist:MinutiaeImpressionCaptureCategoryCode>4

</ansi-nist:MinutiaeImpressionCaptureCategoryCode> 

214.2.5 Element <ansi-nist:MinutiaeFormatNISTStandardIndicator> 

Cross-reference: Part 1, Section 14.2.4 Field 9.004 Minutiae format (FMT) 

This mandatory element shall contain a value indicating whether the information in the remainder 

of the record adheres to the standard format or is a user-defined format. This element shall 

contain a value of "true" to indicate that the minutiae are formatted as specified by the standard 

Type-9 logical record description using location information and other conventions described 

above. A standard Type-9 logical record will substitute <itl:Minutiae> for the abstract element 

<itl:RecordMinutiae>. 

This element shall contain a value of "false" to indicate that the minutiae are formatted in vendorspecific or M1-378 terms. More than one vendor representation of the same set of minutiae from 

one view of one finger could be present in a single Type 9 record when this element contains a 

value of “false”. Multiple blocks of vendor-specific data, which may include content from 

<itl:Minutiae>, can occur within a single Type-9 record when this element contains a value of 

“false”. Even though information may be encoded in accordance with a specific vendor’s 

implementation, all XML elements and content in the Type-9 record must remain as ASCII text. 

<ansi-nist:MinutiaeFormatNISTStandardIndicator>true

</ansi-nist:MinutiaeFormatNISTStandardIndicator> 

214.2.6 Element <itl:RecordMinutiae> 

Complex element <itl:RecordMinutiae> is abstract, and as such is unusable by itself. 

Implementers may use the NIST “Standard format” substitution element <itl:Minutiae> which is 

described in the next subsection. Implementers alternatively may define, in an extension 

schema, a substitution element containing user-defined child elements from the user’s domain. 

Vendor-specific substitution elements may be registered with the domain owner specified in the 

Type-1 record, element <ansi-nist:TransactionDomain>. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="VendorDefinedMinutiae" 

 substitutionGroup="itl:RecordMinutiae" 

 type="user-domain:VendorDefinedMinutiaeType"/> 

<xsd:complexType name="VendorDefinedMinutiaeType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 
Part 2 ANSI/NIST-ITL 2-2008

56

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:VendorDefinedMinutiae> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:VendorDefinedMinutiae> 

214.2.7 Element <itl:Minutiae> 

The complex element <itl:Minutiae> has been defined as a concrete substitution for the abstract 

element <itl:RecordMinutiae>. It contains the NIST “Standard format” content for representation 

of minutiae. All of the elements in the “Standard format” are nested within, as described in the 

subsections below. 

<itl:Minutiae> 

[. . . NIST “Standard format” minutiae elements . . .] 

</itl:Minutiae> 

214.2.7.1 Element <itl:MinutiaeNISTStandard> 

This mandatory complex element contains four child elements described in the subsections 

below: <itl:MinutiaDetail>, <ansi-nist:MinutiaeQuantity>, <ansi-nist:MinutiaeReadingSystem>, 

and <ansi-nist:MinutiaeRidgeCountIndicator>. 

<itl:MinutiaeNISTStandard> 

[. . . Minutiae elements . . .] 

</itl:MinutiaeNISTStandard> 

214.2.7.1.1 Element <itl:MinutiaDetail> 

Cross-reference: Part 1, Section 14.2.12 Field 9.012: Minutiae and ridge count data 

(MRC) 

At least one occurrence of this complex element is mandatory. The set of occurrences of this 

element shall contain all of the individual minutiae and ridge count data associated with the 

current fingerprint or palmprint impression. The number of occurrences shall be as many 

minutiae stated in the minutiae count in <ansi-nist:MinutiaeQuantity> (MIN). Each occurrence of 

<itl:MinutiaDetail> shall be devoted to a single minutia and shall consist of mandatory and 

optional child XML elements. 

The child elements must appear in the order below. Optional elements may be omitted 

altogether. 

X coordinate value <ansi-nist:PositionHorizontalCoordinateValue> 

There shall be one and only one occurrence of this mandatory element in the <ansinist:MinutiaDetail> complex. For minutiae encoded from fingerprints, the X (horizontal) 
Part 2 ANSI/NIST-ITL 2-2008

57

coordinate shall be represented by a four-digit ASCII numeric value ranging from “0000” zero 

upward. For minutiae encoded from palmprints, the X (horizontal) coordinate shall be 

represented by a five-digit ASCII numeric value ranging from “00000” zero upward. 

Y coordinate value <ansi-nist:PositionVerticalCoordinateValue> 

There shall be one and only one occurrence of this mandatory element in the <ansinist:MinutiaDetail> complex. For minutiae encoded from fingerprints, the Y (vertical) coordinate 

shall be represented by a four-digit ASCII numeric value ranging from “0000” zero upward. For 

minutiae encoded from palmprints, the Y (vertical) coordinate shall be represented by a five-digit 

ASCII numeric value ranging from “00000” zero upward. 

Index number <ansi-nist:MinutiaIdentification> 

There shall be one and only one occurrence of this mandatory element in the <ansinist:MinutiaDetail> complex. The index number shall be initialized to "1" and incremented by “1” 

for each additional minutia in the fingerprint. This index number serves to identify each individual 

minutia. Complex element <ansi-nist:MinutiaIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain index datum. 

Theta value <ansi-nist:PositionThetaAngleMeasure> 

There shall be one and only one occurrence of this mandatory element in the <ansinist:MinutiaDetail> complex. For minutiae encoded from fingerprints and from palmprints, the 

Theta value shall be represented by a three-digit ASCII value between 000 and 359. 

Quality measure <ansi-nist:MinutiaQualityValue> 

This is an optional quality measure element that, if present, shall have only one occurrence. 

Values shall range from "0" to "63". The value "0" shall indicate a manually encoded minutia. 

The value "1" shall indicate that no method of indicating a confidence level is available. Values 

between "2" and "63" shall indicate decreasing levels of confidence, with "2" meaning the 

greatest confidence. 

Minutia type designation <ansi-nist:MinutiaCategoryCode> 

This is an optional minutia type designation element that, if present, shall have only one 

occurrence. This shall be a single alphabetic character as chosen from Table 215. 

Ridge count data <ansi-nist:MinutiaRidgeCount> 

This is an optional ridge count data element. This complex element may have a zero to 

unbounded number of occurrences. It is a complex element with two children, each of which are 

mandatory and shall have only one occurrence. Each occurrence of <ansinist:MinutiaRidgeCount> consists of a minutia number element and a ridge count element. This 

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 minutia 

in the <ansi-nist:RidgeCountValue> element. The complex <ansi-nist:MinutiaRidgeCount> shall 

be repeated as many times as required for each minutia. Complex element <ansinist:RidgeCountReferenceIdentification> shall have the simple element <nc:IdentificationID>, 

which will contain the index datum. 
Part 2 ANSI/NIST-ITL 2-2008

58

<itl:MinutiaDetail> 

<ansi-nist:PositionHorizontalCoordinateValue>0486

</ansi-nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>2839

</ansi-nist:PositionVerticalCoordinateValue> 

<ansi-nist:MinutiaIdentification> 

<nc:IdentificationID>00</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> 

214.2.7.1.2 Element <ansi-nist:MinutiaeQuantity> 

Cross-reference: Part 1, Section 14.2.10 Field 9.010: Number of minutiae (MIN) 

This mandatory element shall contain the count of the number of minutiae recorded for this 

fingerprint or palmprint. 

<ansi-nist:MinutiaeQuantity>38</ansi-nist:MinutiaeQuantity> 

214.2.7.1.3 Element <ansi-nist:MinutiaeReadingSystem> 

Cross-reference: Part 1, Section 14.2.15 Field 9.005: Originating fingerprint reading system 

(OFR) 

This optional complex element shall contain three child elements relating to the originating 

fingerprint reading system. The <ansi-nist:ReadingSystemCodingMethodCode> element shall 

contain a single character to indicate the method by which the minutiae data was read, encoded, 

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 

possible but unneeded; (3) "E", if the data was automatically read but manually edited before 

encoding and recording; or (4) "M", if the data was manually read. The <ansinist:ReadingSystemName> element shall contain the originator's designation or name for the 

particular fingerprint or palmprint reading system that generated this record. The <ansinist:ReadingSystemSubsystemIdentification> element is an optional, two-character, user-
Part 2 ANSI/NIST-ITL 2-2008

59

generated subsystem designator that uniquely identifies the originator's equipment. Complex 

element <ansi-nist:ReadingSystemSubsystemIdentification>, if used, shall have the simple 

element <nc:IdentificationID>, which will contain the subsystem designator datum. 

<ansi-nist:MinutiaeReadingSystem> 

<ansi-nist:ReadingSystemCodingMethodCode>E

</ansi-nist:ReadingSystemCodingMethodCode> 

<ansi-nist:ReadingSystemName>Text

</ansi-nist:ReadingSystemName> 

<ansi-nist:ReadingSystemSubsystemIdentification> 

<nc:IdentificationID>88</nc:IdentificationID> 

</ansi-nist:ReadingSystemSubsystemIdentification> 

</ansi-nist:MinutiaeReadingSystem> 

214.2.7.2 Element <ansi-nist:MinutiaeRidgeCountIndicator> 

Cross-reference: Part 1, Section 14.2.11 Field 9.011 Minutiae ridge count indicator (RDG) 

This mandatory single-character element shall be used to indicate the presence of minutiae ridge 

count information. A "false" in this element indicates that no ridge count information is available. 

A "true" indicates that ridge count information is available. 

<ansi-nist:MinutiaeRidgeCountIndicator>true 

</ansi-nist:MinutiaeRidgeCountIndicator> 

214.2.7.3 Element <ansi-nist:MinutiaeFingerCorePosition> 

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. 

If this element is used, it shall contain the X and Y coordinate position of the core of a fingerprint. 

The X value shall be coded as a four-digit ASCII number in the <ansinist:PositionHorizontalCoordinateValue> child element. The Y value shall be coded as a fourdigit ASCII number in the <ansi-nist:PositionVerticalCoordinateValue> child element. Multiple 

occurrences of the core position complex are allowable. 

<ansi-nist:MinutiaeFingerCorePosition> 

<ansi-nist:PositionHorizontalCoordinateValue>0035

</ansi-nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>0045

</ansi-nist:PositionVerticalCoordinateValue> 

</ansi-nist:MinutiaeFingerCorePosition> 

214.2.7.4 Element <ansi-nist:MinutiaeFingerDeltaPosition> 

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. 

If this element is used, it shall contain the X and Y coordinate position of each delta that is 

present on the fingerprint. The X value shall be coded as a four-digit ASCII number in the <ansinist:PositionHorizontalCoordinateValue> child element. The Y value shall be coded as a fourdigit ASCII number in the <ansi-nist:PositionVerticalCoordinateValue> child element. Multiple 

occurrences of the delta position complex are allowable. 
Part 2 ANSI/NIST-ITL 2-2008

60

<ansi-nist:MinutiaeFingerDeltaPosition> 

<ansi-nist:PositionHorizontalCoordinateValue>0035

</ansi-nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>0045

</ansi-nist:PositionVerticalCoordinateValue> 

</ansi-nist:MinutiaeFingerDeltaPosition> 

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 

214.2.7.5 Element <itl:MinutiaeFingerPatternDetail> 

Cross-reference: Part 1, Section 14.2.7 Field 9.007 Fingerprint pattern classification (FPC) 

This element is mandatory when the minutiae are derived from a fingerprint image. It shall 

contain a single occurrence of child element for the source of the pattern code and one or more 

occurrences of the child element for the fingerprint pattern classification code. If the minutiae are 

derived from a palmprint, this element shall not be present. The element shall contain two 

information items. The <itl:FingerPatternCodeSourceCode> shall indicate the source of the 

specific pattern classification code. The source may be Table 217 or a user-defined classification 

code. This element shall contain a "T" to indicate that the pattern classification code is from 

Table 217 or a "U" to indicate that the code is user-defined. The <ansi-nist:FingerPatternCode> 

shall contain the pattern classification code chosen from Table 217 or a specific user-defined 

code. (Table 217 is the same as Table 16 in Part 1.) When it is not possible to uniquely identify 

the fingerprint class, reference fingerprint classes may be used and shall be included as multiple 

occurrences of the <ansi-nist:FingerPatternCode> element. 
Part 2 ANSI/NIST-ITL 2-2008

61

<itl:MinutiaeFingerPatternDetail> 

<itl:FingerPatternCodeSourceCode>T

</itl:FingerPatternCodeSourceCode> 

<ansi-nist:FingerPatternCode>PW

</ansi-nist:FingerPatternCode> 

<ansi-nist:FingerPatternCode>CP

</ansi-nist:FingerPatternCode> 

</itl:MinutiaeFingerPatternDetail> 

214.2.7.6 Element <ansi-nist:MinutiaeFingerPositionCode> or <ansinist:MinutiaePalmPositionCode 

Cross-reference: Part 1, Section 14.2.6 Field 9.006 Finger position (FGP) 

This mandatory element shall contain the code designating the finger or palm position that 

produced information in this Type-9 record. If the exact finger or palm position cannot be 

determined, multiple finger positions may be entered as multiple occurrences of this element. 

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> 

element. Palm position codes shall be entered in the <ansi-nist:MinutiaePalmPositionCode>. 

Multiple occurrences of either element are allowable. 

<ansi-nist:MinutiaeFingerPositionCode>5

</ansi-nist:MinutiaeFingerPositionCode> 

<ansi-nist:MinutiaeFingerPositionCode>6 

</ansi-nist:MinutiaeFingerPositionCode> 

or

<ansi-nist:MinutiaePalmPositionCode>22

</ansi-nist:MinutiaePalmPositionCode> 

<ansi-nist:MinutiaePalmPositionCode>24 

</ansi-nist:MinutiaePalmPositionCode> 

214.3 End of Type-9 logical record 

The Type-9 logical record shall end with the XML tag </itl:PackageMinutiaeRecord>. 

214.4 Additional minutiae records 

Typically, up to nine more fingers may be described within the exchange package. Alternatively, 

up to seven more additional palm records may be described within the exchange package. For 

each additional finger or palm, a Type-9 logical record is required. 

215 Type-10 facial & SMT image record 

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 
Part 2 ANSI/NIST-ITL 2-2008

62

grayscale and color image data in a compressed or uncompressed form. Annex F includes an 

XML instance example of the Type-10 facial image record. 

215.1 XML elements for the Type-10 logical record 

Table 218 lists each of the mandatory and optional XML elements present in a Type-10 logical 

record. (Table 218 corresponds to Table 17 in Part 1.) The following paragraphs describe the 

data contained in each of the elements for the Type-10 logical record. 

Within a Type-10 logical record, entries shall be provided in XML elements. It is required that all 

of the elements of the record are ordered, and the image data shall be converted to ASCII using 

Base64 encoding. For each element of the Type-10 record, Table 218 lists the “condition code” 

as being mandatory “M” or optional “O” and provides a cross-reference to the Part 1 field number 

and mnemonic, the XML tag name, and occurrence limits. Elements containing entries in the 

“IMG” column are only applicable to that image type. An entry of “FAC” applies to a mugshot or 

facial image, and an entry of "SMT" applies to scar, a mark, or a tattoo image. 

The Type-10 record shall be contained within this complex element: 

<itl:PackageFacialAndSMTImageRecord> 

 [. . . Type 10 Record Content . . .] 

</itl:PackageFacialAndSMTImageRecord> 

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 <ansinist:RecordCategoryCode>, for example). 

Table 218 Type-10 facial and SMT record layout 

Part 1 

Ident

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 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 – 

10.998 

<itl:UserDefinedFields> 0 Unlim 

 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 
Part 2 ANSI/NIST-ITL 2-2008

63

Part 1 

Ident

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 min Max 

SVPS O 10.017 <ansi-nist:CaptureVerticalPixelDensityValue> 0 1 

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 

SMD 10.042 <ansi-nist:PhysicalFeatureClassCode> SMT 0 1 

SMD 10.042 <ansi-nist:PhysicalFeatureDescriptionText> SMT 0 1 

SMD 10.042 <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 ANSI/NIST-ITL 2-2008

64

215.1.1 Record length 

Cross-reference: Part 1, Section 15.1.1 Field 10.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

215.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-10 record, it shall contain a value of 10. 

<ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 

215.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 15.1.2 Field 10.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the facial or SMT image data contained 

in the record. The content of this element shall match the <ansinist:ImageReferenceIdentification> found in the <ansi-nist:TransactionContentSummary> 

element of the Type-1 record. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>8</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

215.1.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 15.1.35 Fields 10.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 
Part 2 ANSI/NIST-ITL 2-2008

65

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 

215.1.5 Element <itl:FaceImage> or <ansi-nist:PhysicalFeatureImage> 

This mandatory complex element can take one of two forms. If the Type-10 record contains the 

image of a face, the <itl:FaceImage> complex element shall be used. If the record contains the 

image of a SMT, the <itl:PhysicalFeatureImage> complex shall be used. All of the remaining 

elements in the Type-10 record are nested within, as described in the subsections below. 

<itl:FaceImage> 

[. . . Face image elements . . .] 

</itl:FaceImage> 

or 

<ansi-nist:PhysicalFeatureImage> 

[. . . SMT image elements . . .] 

</ansi-nist:PhysicalFeatureImage> 

215.1.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 15.1.36 Field 10.999: Image data (DATA) 

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 

encoding. 

Each pixel of uncompressed grayscale data shall be quantized to eight bits (256 gray levels) and 

shall occupy a single byte. Uncompressed color image data shall be expressed as 24- or 48-bit 

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 

the third byte shall contain the last eight bits for the blue component of the pixel. For the 48-bit 

sRGB pixel, each color component will occupy two bytes. If compression is used, the pixel data 

shall be compressed in accordance with the compression technique specified in the <ansinist:ImageCompressionAlgorithmText> element. If the JPEG algorithm is to be used to compress 

the data, the data to be placed in this element shall be encoded first using the JFIF format 

specification, then Base64 encoded. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

215.1.5.2 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains five child elements described in the subsections 

below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansi-
Part 2 ANSI/NIST-ITL 2-2008

66

nist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode>. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

215.1.5.2.1 Element <ansi-nist:CaptureDate> 

Cross-reference: Part 1, Section 15.1.5 Field 10.005: Photo date (PHD) 

This mandatory element <ansi-nist:CaptureDate> shall contain the date that the image contained 

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; 

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 

February 29, 2008. The complete date must be a legitimate date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

<ansi-nist:CaptureDate> 

 <nc:Date>2008-02-29</nc:Date> 

</ansi-nist:CaptureDate> 

215.1.5.2.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 15.1.16 Field 10.016: Scanned horizontal pixel scale (SHPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>500

</ansi-nist:CaptureHorizontalPixelDensityValue> 

215.1.5.2.3 Element <ansi-nist:CaptureOrganization> 

Cross-reference: Part 1, Section 15.1.4 Field 10.004: Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

<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 

text 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 

contain up to 36 identifying characters each, and the data content of this element shall be defined 

by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 
Part 2 ANSI/NIST-ITL 2-2008

67

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 

215.1.5.2.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

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 

impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:CaptureVerticalPixelDensityValue>500

</ansi-nist:CaptureVerticalPixelDensityValue> 

215.1.5.2.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross-reference: Part 1, Section 15.1.28 Field 10.030: Device monitoring mode (DMM) 

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 

mode of the biometric sample capture device. (Table 219 is the same as Table 27 in Part 1.) 

<ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED

</ansi-nist:CaptureDeviceMonitoringModeCode> 

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 

215.1.5.3 Element <ansi-nist:ImageColorSpaceCode> 

Cross-reference: Part 1, Section 15.1.12 Field 10.012: Color space (CSP) 

This mandatory element shall contain an ASCII entry from Table 203 to identify the color space 

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. 
Part 2 ANSI/NIST-ITL 2-2008

68

For JPEG-compressed color image files (stored using the JFIF file format), the preferred 

(external) color space is sRGB and an entry of “SRGB” shall be used for this element. For all 

grayscale (monochrome) images, an entry of "GRAY" shall be used for this element. 

For JPEG 2000 images stored using the JP2 file format, the available enumerated color spaces 

are sRGB, sYCC, and grayscale, to be entered, respectively, as “SRGB”, “SYCC”, and “GRAY” in 

this element. The preferred (external) color space for color images is sRGB. If a photo 

acquisition device uses another ICC13 color profile, the acquisition system must convert the image 

data to one of these enumerated color spaces before the JP2 file may be embedded in a Type 10 

record. 

For uncompressed color images containing non-interleaved red, green, and blue pixels in that 

order, the preferred color space is sRGB, and an entry of “SRGB” shall be used for this element. 

The element <ansi-nist:ImageCompressionAlgorithmText> will need to be examined to determine 

if the image data is JPEG, JPEG 2000, or an uncompressed color image. 

<ansi-nist:ImageColorSpaceCode>YCC 

</ansi-nist:ImageColorSpaceCode> 

215.1.5.4 Element <ansi-nist:ImageCompressionAlgorithmText> 

Cross-reference: Part 1, Section 15.1.11 Field 10.011: Compression algorithm (CGA) 

This mandatory element shall contain an ASCII entry from Table 201 (other than WSQ) to specify 

the algorithm used for compressing the color or grayscale image. An entry of "NONE" indicates 

that the data contained in this record is uncompressed. The image shall be represented as an 

array of n rows by m columns by at least 8-bit pixels. Each pixel in a monochrome image shall be 

represented by eight or more bits. Color images shall be represented as a series of sequential 

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 

those images that are to be compressed, the method for the compression of facial and SMT 

images is specified by the baseline mode of the JPEG, JPEG 2000, or PNG algorithms. 

<ansi-nist:ImageCompressionAlgorithmText>JPEGB

</ansi-nist:ImageCompressionAlgorithmText> 

215.1.5.5 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 15.1.6 Field 10.006: Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

 

13 International Color Consortium (ICC), http://www.color.org/ 
Part 2 ANSI/NIST-ITL 2-2008

69

215.1.5.6 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 15.1.9 Field 10.009: Horizontal pixel scale (HPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 

215.1.5.7 Element <ansi-nist:ImageQuality> 

Cross-reference: Part 1, Section 15.1.22 Field 10.024: Subject quality score (SQS) 

This optional element shall specify quality score data for facial images stored in this record. 

There are three child elements. They identify a quality score and the algorithm used to create the 

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 

processing or analysis as necessary. 

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 

with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms 

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 

should be within the range 1 to 65,535. 

2. The child element <ansi-nist:QualityValue> shall be a quantitative expression of the 

predicted matching performance of the biometric sample. This element contains the ASCII 

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 

failed attempt to calculate a quality score. An entry of “254” shall 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. 

3. The child element <ansi-nist:QualityMeasureVendorIdentification> 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 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. This complex element contains a child element <nc:IdentificationID> that shall 

contain the identification datum. 

<ansi-nist:ImageQuality> 

<ansi-nist:QualityAlgorithmProductIdentification> 

<nc:IdentificationID>28488</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> 
Part 2 ANSI/NIST-ITL 2-2008

70

215.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

Cross-reference: Part 1, Section 15.1.8 Field 10.008: Scale units (SLC) 

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 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

215.1.5.9 Element <ansi-nist:ImageCategoryCode> 

Cross-reference: Part 1, Section 15.1.3 Field 10.003: Image type (IMT) 

This mandatory element is used to indicate the type of image contained in this record. It shall 

contain "FACE", "SCAR", "MARK", or "TATTOO" to indicate the appropriate image type. 

<ansi-nist:ImageCategoryCode>FACE</ansi-nist:ImageCategoryCode> 

215.1.5.10 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 15.1.7 Field 10.007: Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

215.1.5.11 Element <ansi-nist:ImageVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 15.1.10 Field 10.010: Vertical pixel scale (VPS) 

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". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 

215.1.5.12 Element <ansi-nist:FaceImage3DPoseAngle> 

Cross-reference: Part 1, Section 15.1.23 Field 10.025: Subject pose angles (SPA) 

This optional element shall be present when <ansi-nist:FaceImageSubjectPoseCode> (POS) 

contains a "D" to indicate a set of determined 3D pose angles of the same subject. If the entry in 

the POS element is an "F", "L", or "R", the contents of this element are ignored. When present, 

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 

are not present, then the uncertainty in the angles is not determined. 
Part 2 ANSI/NIST-ITL 2-2008

71

The child element <ansi-nist:PosePitchAngleMeasure> contains the Pitch angle (rotation about 

the ‘x’ horizontal axis). The optional child element <ansi-nist:PosePitchUncertaintyValue> 

contains the uncertainty degree for the Pitch angle. 

The child element <ansi-nist:PoseRollAngleMeasure> contains the Roll angle (rotation about the 

‘z’ axis). The optional child element <ansi-nist:PoseRollUncertaintyValue> contains the 

uncertainty degree for the Roll angle. 

The child element <ansi-nist:PoseYawAngleMeasure> contains the Yaw angle (rotation about the 

vertical ‘y’ axis). The optional child element <ansi-nist:PoseYawUncertaintyValue> contains the 

uncertainty degree for the Yaw angle. 

The first Pitch, Roll, and Yaw angles specify the pose of the subject estimated or measured at 

constrained possible orientations within a sphere. Each angle value shall be to the nearest 

integer degree. 

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 

the Yaw angle of this element has the opposite sign of the offset angle contained in POA. Annex 

J contains additional information, details, and examples of the subject pose angles. 

<ansi-nist:FaceImage3DPoseAngle> 

<ansi-nist:PosePitchAngleMeasure>45

</ansi-nist:PosePitchAngleMeasure> 

<ansi-nist:PosePitchUncertaintyMeasure>35 

</ansi-nist:PosePitchUncertaintyMeasure> 

<ansi-nist:PoseRollAngleMeasure>0

</ansi-nist:PoseRollAngleMeasure> 

<ansi-nist:PoseRollUncertaintyMeasure>90

</ansi-nist:PoseRollUncertaintyMeasure> 

<ansi-nist:PoseYawAngleMeasure>0

</ansi-nist:PoseYawAngleMeasure> 

<ansi-nist:PoseYawUncertaintyMeasure>0

</ansi-nist:PoseYawUncertaintyMeasure> 

</ansi-nist:FaceImage3DPoseAngle> 

215.1.5.13 Element <ansi-nist:FaceImageAcquisitionProfileCode> 

Cross-reference: Part 1, Section 15.1.13 Field 10.013: Subject acquisition profile (SAP) 

The Subject Acquisition Profile (SAP) is a mandatory element when the element <ansinist:ImageCategoryCode> (IMT) contains "FACE”. The intent of this element is to provide a 

general description of the criteria under which the facial image was captured. This element shall 

contain an ASCII character code selected from Table 220 to indicate the numeric value of the 

acquisition profile and conditions used to acquire the image. (Table 220 is the same as Table 18 

in Part 1.) Typically, the higher the value, the stronger the acquisition requirements become. 

Therefore, in the text below, the SAP value will also be denoted as a “level”. 

Together with Table 220 is a brief description of each of the levels. Note that levels 10 to 15 

denote applications associated with image acquisition under the guidance of other facial 

standards or application profiles. Levels 30 to 51 reference best practice recommendations 

consisting of increasingly more stringent requirements that must be satisfied. Additional details 

and criteria for these levels are contained in Annex H and Annex I. 
Part 2 ANSI/NIST-ITL 2-2008

72

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 

Level 0 (Unknown profile) 

This level denotes any case when the Subject Acquisition Profile is unknown. This value can be 

used to alert systems that the profile of the face image needs to be determined manually or via 

advanced face image quality evaluation techniques. 

 Level 1 (Surveillance facial image) 

This SAP denotes a surveillance facial image: a face image captured without specific regard to 

scene, photographic, or digital requirements. For example, an image of a face from commonly 

available surveillance video equipment is generally considered a surveillance facial image. 

Typically surveillance facial images are of relatively poor quality compared to mugshots, including 

significant pose angle used for the frontal view, poor image resolution, poor image contrast, etc. 

 Levels 10-15 (Other application profiles) 

Levels 10-15 shall denote images associated with capture under the guidance of other facial 

standards or application profiles as defined below. 

• Level 10 denotes a driver license facial portrait described in the AAMVA International 

Specification – DL/ID Card Design 

• Level 11 denotes an ANSI facial image which meets requirements of the Full Frontal image 

type defined in ANSI INCITS 385-2004 
Part 2 ANSI/NIST-ITL 2-2008

73

• Level 12 denotes an ANSI facial image which meets requirements of the Token Face Image 

type defined in ANSI INCITS 385-2004 

• Level 13 denotes an ISO facial image that meets the requirements of the Full Frontal Image 

defined in International standard ISO/IEC 19794-5 

• Level 14 denotes an ISO facial image that meets the requirements of the Token Face Image 

type defined in International standard ISO/IEC 19794-5 

• Level 15 denotes a PIV facial image which meets requirements of Biometric Data 

Specification for Personal Identity Verification. 

 

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 . 

 Level 20 (Legacy facial mugshot) 

An image conforming to this application profile level shall be a mugshot formatted according to 

ANSI/NIST-ITL 2000, but not necessarily or known to be conforming to the best practice 

requirements given in profile 30 below. The subject pose(s) can be Frontal, Profile, or Angled. 

 Best Practice Application Level 30 

An image conforming to a level 30 application profile shall include at least one mugshot record 

conforming to all best practice requirements (BPR) in Annex H. These mugshots shall adhere to 

strict background, lighting, and resolution requirements. In particular, the background is 18% 

gray, the lighting is three-point, and the image size is at least 480x600 pixels with an aspect ratio 

of 1:1.25. 

 Best Practice Application Level 40 

A facial image conforming to the level 40 application profile can be captured with an off-the-shelf 

1 megapixel camera. Annex I contains detailed information for the capture of level 40, 50, and 51 

facial images. Requirements for conformance with level 40 facial image capture include the 

following: 

• Conformance to the minimum requirements for the capture of level 30 facial images; 

• At least one frontal face image shall be captured which conforms to the “face image capture 

requirements”; 

• 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 

• Facial images shall conform to the “head and shoulders” composition detailed requirements. 

It should be noted that the image quality of the captured facial images will be improved as the 

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. 

 Best Practice Application Level 50 and Level 51 

An image conforming to the level 50 and level 51 application profiles shall include “face image 

capture requirements” as described in Annex I. These profile levels are intended to allow for 

examination of up to forensic-level (10 ppmm) detail on a subject’s face. The only difference 
Part 2 ANSI/NIST-ITL 2-2008

74

between levels 50 and 51 is that level 50 specifies the “head and shoulders” composition 

requirements while level 51 specifies the “head only” composition requirements. 

Identification applications require approximately 1700 pixels wide by 2515 pixels high on the face 

for the 99th percentile male in the U.S. population. Allocating 50% of the image width for the 

head requires approximately 3400 pixels for a “head and shoulders photo” image width. For a 

level 50 image capture profile, the minimum number of pixels in the electronic digital image shall 

be 3300 pixels in the horizontal direction by 4400 pixels in the vertical direction. Off-the-shelf 15 

(or more) megapixel digital cameras satisfy this requirement. 

As an alternative, allocating 70% of the image width for the head requires approximately 2400 

pixels for the “head only” facial capture. For a level 51 image capture profile, the minimum 

number of pixels in the electronic digital image shall be 2400 pixels in the horizontal direction by 

3200 pixels in the vertical direction. Off-the-shelf 8 megapixel digital cameras satisfy this 

requirement. 

The level 50 and level 51 SAPs allow for the encoding of very high resolution face images that 

are consistent with the discussion above and with the “face image capture requirements.” It 

should be noted that the image quality of the captured facial images may be improved as the 

number of pixels in both directions are increased. Figure 4 illustrates the improvement in image 

quality from levels 30 to 50/51. However, as images are captured with an increased number of 

pixels, the 3:4 (Width:Height) aspect ratio shall be maintained. 

<ansi-nist:FaceImageAcquisitionProfileCode>20 

</ansi-nist:FaceImageAcquisitionProfileCode> 

 

a. Level 30 b. Level 40 c. Levels 50 and 51 

Figure 4 Examples of resolution for levels 30, 40, & 50/51 
Part 2 ANSI/NIST-ITL 2-2008

75

215.1.5.14 Element <ansi-nist:FaceImageAttribute> 

Cross-reference: Part 1, Section 15.1.20 Field 10.022: Photo description (PXS) 

This optional element, retained for legacy systems, is used for the exchange of facial image data. 

When present, it shall consist of one or more child elements and shall describe special attributes 

of the captured facial image. Attributes associated with the facial image may be selected from 

Table 221. (Table 221 is the same as Table 20 in Part 1.) The “attribute code” shall be entered 

in the <ansi-nist:FaceImageAttributeCode> child element. 

Physical characteristics, such as "FRECKLES", may be entered using a pair of child elements. 

The “attribute code” "PHYSICAL" from Table 221 shall be entered in the <ansinist:FaceImageAttributeCode> element. It shall be followed by a <ansinist:FaceImageAttributeText> element containing the characteristic as listed in the Ninth (or 

current) Edition of the NCIC Code Manual, December 2000. The "OTHER" category is used to 

enter unlisted or miscellaneous attributes of the facial image. This information shall be entered 

using a pair of child elements. The first is "OTHER" in the <ansi-nist:FaceImageAttributeCode> 

element followed by the unformatted text used to describe the attribute in the <ansinist:FaceImageAttributeText> element. 

Multiple attributes with child code and text elements may be listed as repeating occurrences of 

the parent <ansi-nist:FaceImageAttribute>. 

Note: The Subject facial description (SXS) is intended as a replacement for PXS. Table 221 

entries are now duplicated and expanded upon in Table 222. (Table 222 is the same as Table 22 

in Part 1.) 

<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>Text 

</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> 

215.1.5.15 Element <ansi-nist:FaceImageDescriptionCode> 

Cross-reference: Part 1, Section 15.1.24 Field 10.026: Subject facial description (SXS) 

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 

"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 

occurrences, each containing a single information item. Attributes associated with the facial 

image may be selected from Table 222 and entered in this element. For "Physical Characteristic," 
Part 2 ANSI/NIST-ITL 2-2008

76

enter a characteristic as listed in the Ninth (or 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 attributes may be listed as separate 

occurrences of the <ansi-nist:FaceImageDescriptionCode> element. 

<ansi-nist:FaceImageDescriptionCode>MOUTH OPEN

</ansi-nist:FaceImageDescriptionCode> 

<ansi-nist:FaceImageDescriptionCode>TEETH VISIBLE

</ansi-nist:FaceImageDescriptionCode> 

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 

215.1.5.16 Element <ansi-nist:FaceImageEyeColorAttributeCode> 

Cross-reference: Part 1, Section 15.1.25 Field 10.027: Subject eye color (SEC) 

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 

"40" or greater. When present, it shall describe the eye color of the subject as seen in the 

photograph. If unusual or unnatural such as may be the case when colored contact lenses are 

present and the “real” eye color cannot be ascertained, then the color should be labeled as 

“XXX”. Eye color attributes and attribute codes are given in Table 223. (Table 223 is the same 

as Table 23 in Part 1.) 

<ansi-nist:FaceImageEyeColorAttributeCode>BLU

</ansi-nist:FaceImageEyeColorAttributeCode> 
Part 2 ANSI/NIST-ITL 2-2008

77

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> 

Note: This element is intended to replace the photo description element <ansinist:FaceImageAttribute) (PXS) and to enhance the content with additional 

descriptive information. As such, photo descriptors found in Table 221 also 

appear in Table 222. 
Part 2 ANSI/NIST-ITL 2-2008

78

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 

215.1.5.17 Element <ansi-nist:FaceImageFeaturePoint> 

Cross-reference: Part 1, Section 15.1.27 Field 10.029: Facial feature points (FFP) 

This optional element shall be used for the exchange of facial image data. When present, it shall 

describe special attributes of manually or automatically detected facial feature points of the 

captured facial image. This information shall be entered as a four-information item feature point 

block as described in Table 224. (Table 224 is the same as Table 25 in Part 1.) 

The child element <ansi-nist:FeaturePointHorizontalCoordinateValue> contains the X coordinate 

of the feature point. 

The child element <ansi-nist:FeaturePointIdentification> contains feature point code. This 

complex element contains a child element <nc:IdentificationID> that shall hold the code datum. 

The child element <ansi-nist:FeaturePointCategoryCode> contains the feature point type. 

The child element <ansi-nist:FeaturePointVerticalCoordinateValue> contains the Y coordinate of 

the feature point. 

Multiple facial points may be listed by repeated occurrences of the parent <ansinist:FaceImageFeaturePoint> complex, each containing these four information items. The 

maximum number of feature points shall be 88, with the use of 84 MPEG4 feature points and 4 

additional eye and nostril center feature points. 

Feature points shall be included in the Type-10 record if they have been accurately determined, 

thereby providing the option that these parameters do not have to be redetermined when the 

image is processed for face recognition tasks. 

Typically a computer algorithm will either accurately determine the position of the feature point or 

completely fail and provide either clearly erroneous or no landmark information. Therefore, a 
Part 2 ANSI/NIST-ITL 2-2008

79

method for accurate determination is the use of computer-automated feature point determination 

followed by human verification and potential override of the computer-determined feature points. 

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. 

MPEG4 Feature points 

The feature point code item shall specify the feature point that is stored in the feature point block. 

The codes for the feature points are taken from the MPEG4 standard and defined as MPEG4 

feature points. Each feature point code is represented by a notation A.B using a major (A) and a 

minor (B) value. The encoding of the feature point code is given by the numeric ASCII 

representation of the value of A.B. The period is required, and the maximum size of this entry 

shall be 5 characters. 

Figure 5 denotes the feature point codes associated with feature points as given by Annex C of 

ISO/IEC 14496-2. Each code is given by major value A and minor value B. For example, the 

code for the left corner of the left eye is given by major value 3 and minor value 7. 

 Eye and nostril centre Feature Points 

The eye center feature points 12.1 (left) and 12.2 (right) are defined to be the horizontal and 

vertical midpoints of the eye corners (3.7, 3.11) and (3.8, 3.12) respectively. The left nostril center 

feature point 12.3 is defined to be the midpoint of the nose feature points (9.1, 9.15) in the 

horizontal direction and (9.3, 9.15) in the vertical direction. Similarly, the right nostril center 

feature point 12.4 is defined to be the midpoint of the nose feature points (9.2, 9.15) in the 

horizontal direction and (9.3, 9.15) in the vertical direction. Both the eye center and nostril center 

Feature points are shown in Figure 6 and values given in Table 225. (Table 225 is the same as 

Table 26 in Part 1.) 

An example instance for representing two feature points of eye centers follows. 

<ansi-nist:FaceImageFeaturePoint> 

<ansi-nist:FeaturePointHorizontalCoordinateValue>120

</ansi-nist:FeaturePointHorizontalCoordinateValue> 

<ansi-nist:FeaturePointIdentification> 

<nc:IdentificationID>12.2</nc:IdentificationID> 

</ansi-nist:FeaturePointIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

80

<ansi-nist:FeaturePointCategoryCode>1

</ansi-nist:FeaturePointCategoryCode> 

<ansi-nist:FeaturePointVerticalCoordinateValue>130

</ansi-nist:FeaturePointVerticalCoordinateValue> 

</ansi-nist:FaceImageFeaturePoint> 

<ansi-nist:FaceImageFeaturePoint> 

<ansi-nist:FeaturePointHorizontalCoordinateValue>240

</ansi-nist:FeaturePointHorizontalCoordinateValue> 

<ansi-nist:FeaturePointIdentification> 

<nc:IdentificationID>12.1</nc:IdentificationID> 

</ansi-nist:FeaturePointIdentification> 

<ansi-nist:FeaturePointCategoryCode>1

</ansi-nist:FeaturePointCategoryCode> 

<ansi-nist:FeaturePointVerticalCoordinateValue>129

</ansi-nist:FeaturePointVerticalCoordinateValue> 

</ansi-nist:FaceImageFeaturePoint> 

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 

9.1, 9.15 9.3,9.15 

12.3 

Right Nostril Horizontal Vertical 

9.2, 9.15 9.3,9.15 

12.4 

215.1.5.18 Element <ansi-nist:FaceImageHairColorAttributeCode> 

Cross-reference: Part 1, Section 15.1.26 Field 10.028: Subject hair color (SHC) 

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 

"40" or greater. When present, it shall contain an entry from Table 226 that describes the hair 

color of the subject as seen in the photograph. (Table 226 is the same as Table 24 in Part 1.) 

For unusual or unnatural colors not listed in the table, or the "real" color cannot be ascertained, 

the hair color should be labeled as “XXX”. 

If the subject is completely bald or has a completely shaved head, then the hair color shall be 

labeled as “BAL”. When the subject is predominantly bald, but hair color is discernable, then the 

appropriate hair color attribute code shall follow “BAL” in a separate occurrence of this element. 

<ansi-nist:FaceImageHairColorAttributeCode>BAL

</ansi-nist:FaceImageHairColorAttributeCode> 

<ansi-nist:FaceImageHairColorAttributeCode>GRY

</ansi-nist:FaceImageHairColorAttributeCode> 
Part 2 ANSI/NIST-ITL 2-2008

81

Table 226 Hair color codes 

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 
Part 2 ANSI/NIST-ITL 2-2008

82

x y

z

11.5

11.4

11.2

10.2

10.4

10.10

10.8

10.6

2.14

7.1

11.6 4.6

4.4

4.2

5.2

5.4

2.10

2.12 2.1

11.1

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

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.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

11.5

x

y

z

Nose

9.6 9.7

9.14 9.13

9.12

9.2

9.4 9.15 9.5

9.3

9.1

Teeth

9.10 9.11

9.8

9.9

Feature points affected by FAPs

Other feature points

Right eye Left eye

3.13

3.7

3.9

3.5

3.1

3.3

3.11

3.14

3.10

3.12 3.6

3.4

3.2

3.8

Figure 5 Feature point codes defined in ISO/IEC 14496-2 
Part 2 ANSI/NIST-ITL 2-2008

83

Figure 6 Eye and nostril center feature points 

215.1.5.19 Element <ansi-nist:FaceImagePoseOffsetAngleMeasure> 

Cross-reference: Part 1, Section 15.1.19 Field 10.021: Pose offset angle (POA) 

This element shall only be used for the exchange of facial image data if <ansinist:FaceImageSubjectPoseCode> (POS) contains an "A" to indicate an angled pose of the 

subject. This element should be omitted for a full face or a profile. This element specifies the 

pose position of the subject at any possible orientation within a circle. Its value shall be to a 

nearest degree. 

The offset angle shall be measured from the full-face pose position and have a range of values 

from -180 degrees to +180 degrees. A positive angle is used to express the angular offset as the 

subject rotates from a full-face pose to their right (approaching a left profile). A negative angle is 

used to express the angular offset as the subject rotates from a full-face pose to their left 

(approaching a right profile). If the entry in the POS element is an "F", "L", or "R", the contents of 

this element are ignored. 

<ansi-nist:FaceImagePoseOffsetAngleMeasure>45

</ansi-nist:FaceImagePoseOffsetAngleMeasure> 

215.1.5.20 Element <ansi-nist:FaceImageSubjectPoseCode> 

Cross-reference: Part 1, Section 15.1.18 Field 10.020: Subject pose (POS) 

This optional element is to be used for the exchange of facial image data. When included, this 

element shall contain one ASCII character code selected from Table 227 to describe the pose of 

the subject. (Table 227 is the same as Table 19 in Part 1.) For the angled pose entry "A", 

element <ansi-nist:FaceImagePoseOffsetAngleMeasure> (POA) shall contain the offset angle 

from the full face orientation. For the determined 3D pose entry "D", element <ansinist:FaceImage3DPoseAngle> (SPA) shall contain a set of determined 3D pose angles (i.e., Yaw, 

Pitch, and Roll angles) away from the full frontal face orientation. Note that the offset angle in 

SPA is opposite from the yaw angle in POA as indicated by a minus sign. 

<ansi-nist:FaceImageSubjectPoseCode>F

</ansi-nist:FaceImageSubjectPoseCode> 
Part 2 ANSI/NIST-ITL 2-2008

84

Table 227 Subject pose 

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 

215.1.5.21 Element <itl:FaceImageAcquisitionSource> 

Cross-reference: Part 1, Section 15.1.21 Field 10.023: Photo acquisition source (PAS) 

This optional element shall specify the classification of the source of the image contained in this 

record. This element is mandatory if the <ansi-nist:FaceImageAcquisitionProfileCode> (SAP) 

entry is "40" or greater. When included, the child element <ansi-nist:CaptureSourceCode> shall 

contain an ASCII attribute code selected from Table 228 to describe the source of captured 

image data. (Table 228 is the same as Table 21 in Part 1.) 

The "VENDOR" category is used to enter unlisted or miscellaneous source attributes of the facial 

image. This information shall be entered in two child elements. The child element <ansinist:CaptureSourceCode> contains "VENDOR" followed by the child element 

<itl:CaptureSourceDescriptionText> containing unformatted text used to describe the attribute. 

<itl:FaceImageAcquisitionSource> 

<ansi-nist:CaptureSourceCode>DIGITAL CAMERA

</ansi-nist:CaptureSourceCode> 

</itl:FaceImageAcquisitionSource> 

Another example: 

<itl:FaceImageAcquisitionSource> 

<ansi-nist:CaptureSourceCode>VENDOR

</ansi-nist:CaptureSourceCode> 

<itl:CaptureSourceDescriptionText>Text

</itl:CaptureSourceDescriptionText> 

</itl:FaceImageAcquisitionSource> 

215.1.5.22 Element <ansi-nist:PhysicalFeatureDescriptionDetail> 

This optional element is used to describe the content of the SMT image. Its child elements 

provide progressively detailed information describing the total image or a portion of the image. 

An SMT image consisting of several parts or sub-images shall use multiple occurrences of this 

complex parent element to fully describe the various parts or features found in the total image. 

The first occurrence shall describe the most predominant feature or sub-image contained in the 

SMT image. Subsequent occurrences shall describe additional portions of the image that are not 

part of the main or central focal point of the image. For example, a tattoo consisting of a man 

with a snake on the arm being followed by a dog may contain three occurrences of <ansi-
Part 2 ANSI/NIST-ITL 2-2008

85

nist:PhysicalFeatureDescriptionDetail> - one describing the man, a second describing the snake, 

and a third describing the dog. 

This complex element contains five child elements described in the subsections below: <ansinist:PhysicalFeatureColorDetail>, <ansi-nist:PhysicalFeatureCategoryCode>, <ansinist:PhysicalFeatureClassCode>, <ansi-nist:PhysicalFeatureDescriptionText>, and <ansinist:PhysicalFeatureSubClassCode>. 

<ansi-nist:PhysicalFeatureDescriptionDetail> 

[. . . Tattoo or SMT image description elements . . .] 

</ansi-nist:PhysicalFeatureDescriptionDetail> 

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 

215.1.5.22.1 Element <ansi-nist:PhysicalFeatureColorDetail> 

Cross-reference: Part 1, Section 15.1.33 Field 10.043: Color (COL) 

This is an optional child element of <ansi-nist:PhysicalFeatureDescriptionDetail>. It shall contain 

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 

chosen from Table 229. (Table 229 is the same as Table 30 in Part 1.) Additional colors shall be 

entered as information items in one or more occurrences of the child element <ansinist:PhysicalFeatureSecondaryColorCode>. 

<ansi-nist:PhysicalFeatureColorDetail> 

<ansi-nist:PhysicalFeaturePrimaryColorCode>YELLOW

</ansi-nist:PhysicalFeaturePrimaryColorCode> 

<ansi-nist:PhysicalFeatureSecondaryColorCode>WHITE

</ansi-nist:PhysicalFeatureSecondaryColorCode> 

<ansi-nist:PhysicalFeatureSecondaryColorCode>BLUE

</ansi-nist:PhysicalFeatureSecondaryColorCode> 

</ansi-nist:PhysicalFeatureColorDetail> 
Part 2 ANSI/NIST-ITL 2-2008

86

215.1.5.22.2 Element <ansi-nist:PhysicalFeatureCategoryCode> 

Cross-reference: Part 1, Section 15.1.32 Field 10.042: SMT descriptors (SMD), the first 

subfield 

This is a mandatory child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. 

This child element shall identify the source of the image as being a scar, a mark, or a tattoo. It 

shall contain “SCAR” to indicate healed scar tissue that was the result an accident or medical 

procedure. An entry of “MARK” shall be used for the pattern resulting from needle or track marks. 

For deliberately applied or drawn images, this element will contain "TATTOO" to indicate a 

common tattoo or indelible image resulting from the pricking of the skin with a coloring matter; 

"CHEMICAL" if the image was created by the use of chemicals to burn the image into the skin; 

"BRANDED" if the image was burned into the skin using a branding iron or other form of heat; or 

“CUT” if the image was caused by incision of the skin. 

<ansi-nist:PhysicalFeatureCategoryCode>SCAR

</ansi-nist:PhysicalFeatureCategoryCode> 

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 

215.1.5.22.3 Element <ansi-nist:PhysicalFeatureClassCode> 

Cross-reference: Part 1, Section 15.1.32 Field 10.042: SMT descriptors (SMD), the 

second subfield 

This is a mandatory child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. 

This element shall contain the general class code of tattoo chosen from Table 230. (Table 230 is 

the same as Table 28 in Part 1.) 

If the <ansi-nist:PhysicalFeatureCategoryCode> is “SCAR” or “MARK”, this element shall contain 

the value “OTHER”. 
Part 2 ANSI/NIST-ITL 2-2008

87

<ansi-nist:PhysicalFeatureClassCode>ABSTRACT

</ansi-nist:PhysicalFeatureClassCode> 

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 

215.1.5.22.4 Element <ansi-nist:PhysicalFeatureDescriptionText> 

Cross-reference: Part 1, Section 15.1.32 Field 10.042: SMT descriptors (SMD), the text 

string description, fourth subfield 

This is an optional child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. It 

shall contain an ASCII text string that provides additional qualifiers to describe the image or 

portion of the image. For example, to fully describe a tattoo, there may be a class description of 

"ANIMAL", with a subclass description of "DOG", and qualified by "golden retriever with an 

overbite".

If the <ansi-nist:PhysicalFeatureCategoryCode> is “SCAR” or “MARK”, this element shall contain 

a textual description or other information concerning the scar or mark pattern. 

<ansi-nist:PhysicalFeatureDescriptionText>Text

</ansi-nist:PhysicalFeatureDescriptionText> 

215.1.5.22.5 Element <ansi-nist:PhysicalFeatureSubClassCode> 

Cross-reference: Part 1, Section 15.1.32 Field 10.042: SMT descriptors (SMD), the 

subclass code, third subfield 

This is a mandatory child element of the optional <ansi-nist:PhysicalFeatureDescriptionDetail>. 

For each general class of tattoo, identified in the <ansi-nist:PhysicalFeatureClassCode> element, 

there are several defined subclasses. This element shall contain the appropriate subclass code 

selected from Table 231 a-h which lists the various subclasses of tattoos for each of the general 

classes. (Table 231 a-h is the same as Table 29 a-h in Part 1.) 

If the <ansi-nist:PhysicalFeatureCategoryCode> is “SCAR” or “MARK”, this element shall contain 

“MISC”. 
Part 2 ANSI/NIST-ITL 2-2008

88

<ansi-nist:PhysicalFeatureSubClassCode>DOG

</ansi-nist:PhysicalFeatureSubClassCode> 

Table 231 Tattoo subclasses

Table 231a Human tattoo subclasses 

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 

Table 231b Animal tattoo subclasses 

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 

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 
Part 2 ANSI/NIST-ITL 2-2008

89

Table 231d Flags tattoo subclasses 

Subclass Subclass code 

American Flag USA 

State Flag STATE 

Nazi Flag NAZI 

Confederate Flag CONFED 

British Flag BRIT 

Miscellaneous Flags MFLAG 

Table 231e Objects 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 

Table 231f Abstract tattoo subclasses 

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 

Table 231g Symbols 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 

Table 231h Other tattoo subclasses

Subclass Subclass code 

Wording (Mom, Dad, Mary, 

etc.) 

WORDING 

Freeform Drawings FREEFRM 

Miscellaneous Images MISC 

 
Part 2 ANSI/NIST-ITL 2-2008

90

215.1.5.23 Element <ansi-nist:PhysicalFeatureNCICCode> 

Cross-reference: Part 1, Section 15.1.30 Field 10.040: NCIC designation code (SMT) 

This element is mandatory for a Type-10 record containing SMT image data. It is used to identify 

a general location of the captured scar, mark, tattoo, or other characteristic (including piercings) 

in an image. The contents of this element will be an entry chosen from the December 2000 ninth 

(or current) edition of the NCIC Code Manual. The captured image can encompass an area 

larger than that specified by a single NCIC body part code for the particular image type. This 

situation can be accommodated by listing multiple NCIC codes in separate occurrences of this 

element. In this case, the primary code is listed first. 

For the "marks" category, the NCIC manual lists the common locations for needle track marks. 

For other body part locations not listed under the "marks" category, use the body location codes 

listed for scars. 

<ansi-nist:PhysicalFeatureNCICCode>TAT L TOE

</ansi-nist:PhysicalFeatureNCICCode> 

<ansi-nist:PhysicalFeatureNCICCode>TAT FARM

</ansi-nist:PhysicalFeatureNCICCode> 

215.1.5.24 Element <ansi-nist:PhysicalFeatureSize> 

Cross-reference: Part 1, Section 15.1.31 Field 10.041: SMT size (SMS) 

This optional element shall contain the dimensions of the scar, mark, or tattoo. It shall consist of 

two child elements. The height shall be contained in the child element <ansinist:PhysicalFeatureHeightMeasure>, and the width shall be contained in the child element <ansinist:PhysicalFeatureWidthMeasure>. Each dimension shall be entered to the nearest centimeter. 

<ansi-nist:PhysicalFeatureSize> 

<ansi-nist:PhysicalFeatureHeightMeasure>112

</ansi-nist:PhysicalFeatureHeightMeasure> 

<ansi-nist:PhysicalFeatureWidthMeasure>15

</ansi-nist:PhysicalFeatureWidthMeasure> 

</ansi-nist:PhysicalFeatureSize> 

215.2 End of Type-10 logical record 

The Type-10 logical record shall end with the XML tag 

</itl:PackageFacialAndSMTImageRecord>. 

215.3 Additional facial & SMT image records 

Additional Type-10 records may be included in the file. For each additional facial or SMT image, 

a complete Type-10 logical record is required. 
Part 2 ANSI/NIST-ITL 2-2008

91

216 Type-11 record reserved for future use 

217 Type-12 record reserved for future use 

218 Type-13 variable-resolution latent image record 

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 

or provide human intervention and processing to extract the desired feature information from the 

images. Information regarding the scanning resolution used, the image size, and other 

parameters required to process the image, are recorded as XML elements within the record. 

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 

logical record. 

Within a Type-13 logical record, entries shall be provided in XML elements. For each element of 

the Type-13 record, Table 232 lists the “condition code” as being mandatory “M” or optional “O”, 

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 

of "PAL" applies to a palmprint image. (Table 232 corresponds to Table 31 in Part 1.) 

The Type-13 record shall be contained within this complex element: 

<itl:PackageLatentImageRecord> 

 [. . . Type 13 Record Content . . .] 

</itl:PackageLatentImageRecord> 

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 <ansinist:RecordCategoryCode>, for example). 

218.1.1 Record length 

Cross-reference: Part 1, Section 18.1.1 Field 13.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

218.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-13 record, it shall contain a value of 13. 

<ansi-nist:RecordCategoryCode>13 

</ansi-nist:RecordCategoryCode> 
Part 2 ANSI/NIST-ITL 2-2008

92

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 -- 
Part 2 ANSI/NIST-ITL 2-2008

93

218.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 18.1.2 Field 13.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the latent image data contained in 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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>6</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

218.1.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 18.1.23 Fields 13.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 
Part 2 ANSI/NIST-ITL 2-2008

94

218.1.5 Element <itl:FingerprintImage> or <itl:PalmprintImage> 

This mandatory complex element can take one of two forms. If the Type-13 record contains the 

image of a latent fingerprint, the <itl:FingerprintImage> complex element shall be used. If the 

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 

subsections below. 

<itl:FingerprintImage> 

[. . . Image elements . . .] 

</itl:FingerprintImage> 

or 

<itl:PalmprintImage> 

[. . . Image elements . . .] 

</itl:PalmprintImage> 

218.1.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 18.1.24 Field 13.999: Image data (DATA) 

This mandatory element shall contain all of the data from a captured latent image. The binary 

image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

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 

than “8”, the number of bytes required to represent a pixel will be different. If compression is 

used, the pixel data shall be compressed in accordance with the compression technique specified 

in <ansi-nist:ImageCompressionAlgorithmText>. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

218.1.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

Cross-reference: Part 1, Section 18.1.12 Field 13.012: Bits per pixel (BPX) 

This mandatory element shall contain the number of bits used to represent a pixel. This element 

shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

greater than “8” shall represent a grayscale pixel with increased precision. 

<ansi-nist:ImageBitsPerPixelQuantity>16

</ansi-nist:ImageBitsPerPixelQuantity> 

218.1.5.3 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains four child elements described in the subsections 

below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansinist:CaptureOrganization>, and <ansi-nist:CaptureVerticalPixelDensityValue>. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 
Part 2 ANSI/NIST-ITL 2-2008

95

218.1.5.3.1 Element <ansi-nist:CaptureDate> 

Cross-reference: Part 1, Section 18.1.5 Field 13.005: Latent capture date (LCD) 

This mandatory element <ansi-nist:CaptureDate> shall contain the date that the latent image 

contained 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; 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 February 29, 2008. The complete date must be a legitimate date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

<ansi-nist:CaptureDate> 

 <nc:Date>2008-02-29</nc:Date> 

</ansi-nist:CaptureDate> 

218.1.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 18.1.16 Field 13.016: Scanned horizontal pixel scale (SHPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>500

</ansi-nist:CaptureHorizontalPixelDensityValue> 

218.1.5.3.3 Element <ansi-nist:CaptureOrganization> 

Cross-reference: Part 1, Section 18.1.4 Field 13.004: Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

<nc:IdentificationID> the identification of the administration or organization that originally captured 

the latent image contained in the record, and may contain in <nc:OrganizationName> the text 

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 

contain up to 36 identifying characters each, and the data content of this element shall be defined 

by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 
Part 2 ANSI/NIST-ITL 2-2008

96

218.1.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

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 

impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:CaptureVerticalPixelDensityValue>500

</ansi-nist:CaptureVerticalPixelDensityValue> 

218.1.5.4 Element <ansi-nist:ImageCommentText> 

Cross-reference: Part 1, Section 18.1.19 Field 13.020: Comment (COM) 

This optional element may be used to insert comments or other ASCII text information with the 

latent image data. 

<ansi-nist:ImageCommentText>Text</ansi-nist:ImageCommentText> 

218.1.5.5 Element <ansi-nist:ImageCompressionAlgorithmText> 

Cross-reference: Part 1, Section 18.1.11 Field 13.011: Compression algorithm (CGA) 

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 

uncompressed. For those images that are to be losslessly compressed, this element shall contain 

the text value from Table 201 to indicate the compression method used for the latent fingerprint 

images. See Section 205.6.1 for additional information on the usage of JPEG 2000 for the 

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. 

<ansi-nist:ImageCompressionAlgorithmText>JPEGB

</ansi-nist:ImageCompressionAlgorithmText> 

218.1.5.6 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 18.1.6 Field 13.006: Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

218.1.5.7 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 18.1.9 Field 13.009: Horizontal pixel scale (HPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 
Part 2 ANSI/NIST-ITL 2-2008

97

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 

218.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

Cross-reference: Part 1, Section 18.1.8 Field 13.008: Scale units (SLC) 

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 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

218.1.5.9 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 18.1.7 Field 13.007: Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

218.1.5.10 Element <ansi-nist:ImageVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 18.1.10 Field 13.010: Vertical pixel scale (VPS) 

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". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 

218.1.5.11 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

Cross-reference: Part 1, Section 18.1.3 Field 13.003: Impression type (IMP) 

This mandatory element shall indicate the manner by which the latent image information was 

obtained. The appropriate latent code choice selected from Table 211 for finger or palm shall be 

entered in this element. 

<ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4

</ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

218.1.5.12 Element <ansi-nist:FingerPositionCode> or <ansi-nist:PalmPositionCode> 

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 

match the latent image. The required element (<ansi-nist:FingerPositionCode> or <ansi-
Part 2 ANSI/NIST-ITL 2-2008

98

nist:PalmPositionCode>) depends upon the data in element <ansinist:FingerprintImageImpressionCaptureCategoryCode> signifying a fingerprint or palmprint 

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 

Table 235 and entered as a one- or two-character ASCII value. Additional finger and/or palm 

positions may be referenced by entering multiple occurrences of the <ansinist:FingerPositionCode> or <ansi-nist:PalmPositionCode> element. The code "0", for "Unknown 

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 

used to reference one or more parts of an Entire Joint Image (EJI) or tip. 

If the element <itl:FingerprintImage> is used, then this child element shall be <ansinist:FingerPositionCode>. If the element <itl:PalmprintImage> is used, then this child element 

shall be <ansi-nist:PalmPositionCode>. 

This element will contain the finger or palm position code datum. Multiple occurrences of the 

element are allowable. The XML code shall be as follows: 

<ansi-nist:FingerPositionCode>12</ansi-nist:FingerPositionCode> 

<ansi-nist:FingerPositionCode>11</ansi-nist:FingerPositionCode> 

or 

<ansi-nist:PalmPositionCode>27</ansi-nist:PalmPositionCode> 

<ansi-nist:PalmPositionCode>26</ansi-nist:PalmPositionCode> 

218.1.5.13 Element <ansi-nist:FingerprintImageMajorCasePrint> 

This complex element shall be present if and only if the value contained by <ansinist:FingerPositionCode> is equal to “19”. This parent element contains three child elements: 

<ansi-nist:FingerPositionCode>, <ansi-nist:MajorCasePrintCode>, and <ansinist:MajorCasePrintSegmentOffset>. 

218.1.5.13.1 Element <ansi-nist:FingerPositionCode> 

Cross-reference: Part 1, Section 18.1.14 Field 13.014: Search Position Descriptors (SPD) – First 

information item 

This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. It is used to 

narrow the search of the latent image in this record against a database. This element is the 

probable decimal finger position code (0-10) taken from Table 212. A "0" indicates that all the 

fingers of a possible candidate should be searched. 

<ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

218.1.5.13.2 Element <ansi-nist:MajorCasePrintCode> 

Cross-reference: Part 1, Section 18.1.14 Field 13.014: Search Position Descriptors (SPD) – 

Second information item 

This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. It is used to 

narrow the search of the latent image in this record against a database. This element is the code 
Part 2 ANSI/NIST-ITL 2-2008

99

taken from Table 233 to indicate the portion of the EJI or tip image in the database to search. 

(Table 233 is the same as Table 32 in Part 1.) Latent images of full-length fingers use codes FV1 

through FV4 as defined in Table 233. Figure 7 is an illustration of the Entire Joint Image for a 

middle finger with each of the full finger views and constituent parts identified. The EJI code is 

used for the case where all four finger images are to be considered. For the case where the 

latent is to be compared to proximal, distal, or medial segments of a finger, this information item 

will contain the appropriate finger segment character. 

<ansi-nist:MajorCasePrintCode>EJI 

</ansi-nist:MajorCasePrintCode> 

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 

NOTE: Elements FingerPositionCode and PalmPositionCode are included to make the standard 

flexible enough to accommodate many different scenarios and applications. These two elements 

facilitate searching of latents formatted within Type-13 records against Type-14 records contained 

in the various database files. The search of a database by a latent can be narrowed with the use 

of additional information such as finger position, finger segment, or full finger view. It is unlikely 

that an entire EJI will ever be left at the scene of a crime. But a latent can be searched against 

the EJIs in an image or features file based on a specific finger segment or full finger view. This 

can be accomplished for a portion of the latent described by the X and Y coordinates. 

218.1.5.13.3 Element <ansi-nist:MajorCasePrintSegmentOffset> 

Cross-reference: Part 1, Section 18.1.15 Field 13.015: Print Position Coordinates (PPC) 

This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. 

This element contains offsets to the locations for the bounding box of the EJI, each of the full 

finger views, or segments within the EJI. When used, this complex element shall consist of six 

mandatory information items to describe the type or portion of the latent image contained in this 

record and its location within an entire joint image. The information item <ansinist:SegmentFingerViewCode> is the number of the full finger view with values of "FV1" through 

"FV4". Values of “FV1” to “FV4” specify the bounding coordinates for each full finger view. The 

information item <ansi-nist:SegmentLocationCode> is used to identify the location of a segment 

within a full finger view. It will contain the not applicable code “NA” if the image portion refers to a 
Part 2 ANSI/NIST-ITL 2-2008

100

full finger view or to the entire joint image locations. It shall contain “PRX”, “DST”, “MED” for a 

proximal, distal, or medial segment. The next four information items are the horizontal and vertical 

offsets 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 (Y) are the pixel counts down. 

The location of the image portion is defined by the sequence of X coordinates (LEFT=<ansinist:SegmentLeftHorizontalCoordinateValue>, RIGHT=<ansinist:SegmentRightHorizontalCoordinateValue>) and the Y coordinates (TOP=<ansinist:SegmentTopVerticalCoordinateValue>, BOTTOM=<ansinist:SegmentBottomVerticalCoordinateValue>) of its bounding box. For the case of a fingertip, 

<ansi-nist:SegmentFingerViewCode> shall be “TIP”, and <ansi-nist:SegmentLocationCode> shall 

be “NA”. The collection of six subelements will describe either the location of the entire joint 

image, one full finger view, or segment. Individual full finger or segment definitions may be 

repeated as multiple occurrences of <ansi-nist:MajorCasePrintSegmentOffset>. 

Figure 7 Entire joint image 

Element <ansi-nist:MajorCasePrintSegmentOffset> shall have six child elements: <ansinist:SegmentBottomVerticalCoordinateValue>, <ansi-nist:SegmentLocationCode>, <ansinist:SegmentFingerViewCode>, <ansi-nist:SegmentLeftHorizontalCoordinateValue>, <ansinist:SegmentRightHorizontalCoordinateValue>, and <ansinist:SegmentTopVerticalCoordinateValue>. 

Part 1 cross-reference information: Element <ansi-nist:SegmentBottomVerticalCoordinateValue> 

shall correspond to the sixth information item in field 13.015. Element <ansinist:SegmentLocationCode> shall correspond to the second information item in field 13.015. 

Element <ansi-nist:SegmentFingerViewCode> shall correspond to the first information item in 

field 13.015. Element <ansi-nist:SegmentLeftHorizontalCoordinateValue> shall correspond to the 

third information item in field 13.015. Element <ansinist:SegmentRightHorizontalCoordinateValue> shall correspond to the fourth information item in 

 Distal 

 Medial 

 Proximal 

FV1 FV2 FV3 FV4 
Part 2 ANSI/NIST-ITL 2-2008

101

field 13.015. Element <ansi-nist:SegmentTopVerticalCoordinateValue> shall correspond to the 

fifth information item in field 13.015. 

At least one occurrence of this subelement <ansi-nist:MajorCasePrintSegmentOffset> is 

mandatory. In practice, multiple occurrences may be used to describe the bounding boxes of 

multiple finger segments or multiple full finger views. 

The XML code shall be as follows: 

<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> 

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.) 

The other three items identify a quality score and the algorithm used to create the 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 processing or 

analysis as necessary. 
Part 2 ANSI/NIST-ITL 2-2008

102

• The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

<nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

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 

score. This element contains the ASCII representation of the integer product code and 

should be within the range 1 to 65535. Element <ansinist:QualityAlgorithmProductIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the numeric product code datum. (This 

corresponds to the fourth information item in 13.024.) 

• The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

<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 

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. 

Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

third information item in 13.024.) 

• 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 

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 failed attempt to calculate a quality score. An entry of “254” shall 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. (This 

corresponds to the second information item in 13.024.) 

The complex element <itl:FingerprintImageQuality> or <itl:PalmprintImageQuality> may be 

repeated for each quality algorithm used. 

<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> 

or 
Part 2 ANSI/NIST-ITL 2-2008

103

<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> 

218.2 End of Type-13 variable-resolution latent image record 

The Type-13 logical record shall end with the XML tag </itl:PackageLatentImageRecord>. 

218.3 Additional variable-resolution latent image records 

Additional Type-13 records may be included in the file. For each additional latent image, a 

complete Type-13 logical record is required. 

219 Type-14 variable-resolution fingerprint image record 

The Type-14 logical record shall contain and be used to exchange fingerprint image data from a 

rolled tenprint, an identification flat, or a major case print (also referred to as a complete friction 

ridge exemplar). All fingerprint impressions shall be acquired from a tenprint card, a major case 

print card, or a live-scan device. Captured images are intended to be transmitted to agencies that 

will automatically extract the desired feature information from the images for matching purposes. 

Textual information regarding the scanning resolution, the image size, and other parameters or 

comments required to process the image are recorded as XML elements within the record. 

The Type-14 record is also used to exchange identification flats (simultaneous plain impressions 

captured on a platen) for civil background checks. Rolled images are generally not used for this 

application. Three Type-14 image records are used to contain the flat fingerprint impressions. 

Two of the image records contain the left and right simultaneous four fingers, and the third 

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 

Fingerprint Image Quality (NFIQ) metric, alternate image quality metrics, and metrics for 

predicting the correctness of the segmentation. 

219.1 XML elements for the Type-14 logical record 

The following paragraphs describe the data contained in each of the elements for the Type-14 

logical record. 

Within a Type-14 logical record, entries shall be provided in XML elements. For each element of 

the Type-14 record, Table 234 lists the “condition code” as being mandatory “M” or optional “O”, 

the XML tag name, and occurrence limits. (Table 234 corresponds to Table 33 in Part 1.) 
Part 2 ANSI/NIST-ITL 2-2008

104

The Type-14 record shall be contained within this complex element: 

<itl:PackageFingerprintImageRecord> 

 [. . . Type 14 Record Content . . .] 

</itl:PackageFingerprintImageRecord> 

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 <ansinist:RecordCategoryCode>, for example). 

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 

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 
Part 2 ANSI/NIST-ITL 2-2008

105

Part 1 

Ident

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

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 

219.1.1 Record length 

Cross-reference: Part 1, Section 19.1.1 Field 14.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

219.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-14 record, it shall contain a value of 14. 

<ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

219.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 19.1.2 Field 14.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the fingerprint image data contained in 

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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>10</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

106

219.1.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 19.1.29 Fields 14.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 

219.1.5 Element <itl:FingerprintImage> 

This mandatory complex element contains the remaining elements in the Type-14 record, as 

described in the subsections below. 

<itl:FingerprintImage> 

[. . . Image elements . . .] 

</itl:FingerprintImage> 

219.1.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 19.1.30 Field 14.999: Image data (DATA) 

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. 

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 
Part 2 ANSI/NIST-ITL 2-2008

107

than “8”, the number of bytes required to represent a pixel will be different. If compression is 

used, the pixel data shall be compressed in accordance with the compression technique specified 

in <ansi-nist:ImageCompressionAlgorithmText>. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

219.1.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

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 

shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

greater than “8” shall represent a grayscale pixel with increased precision. 

<ansi-nist:ImageBitsPerPixelQuantity>8

</ansi-nist:ImageBitsPerPixelQuantity> 

219.1.5.3 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains five child elements described in the subsections 

below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansinist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode>. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

219.1.5.3.1 Element <ansi-nist:CaptureDate> 

Cross-reference: Part 1, Section 19.1.5 Field 14.005: Fingerprint capture date (FCD) 

This mandatory element <ansi-nist:CaptureDate> shall contain the date that the image contained 

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; 

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 

February 29, 2008. The complete date must be a legitimate date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

<ansi-nist:CaptureDate> 

 <nc:Date>2008-02-29</nc:Date> 

</ansi-nist:CaptureDate> 

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) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 
Part 2 ANSI/NIST-ITL 2-2008

108

<ansi-nist:CaptureHorizontalPixelDensityValue>500

</ansi-nist:CaptureHorizontalPixelDensityValue> 

219.1.5.3.3 Element <ansi-nist:CaptureOrganization> 

Cross-reference: Part 1, Section 19.1.4 Field 14.004: Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

<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 

text 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 

contain up to 36 identifying characters each, and the data content of this element shall be defined 

by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 

219.1.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 19.1.17 Field 14.017: Scanned vertical pixel scale (SVPS) 

This optional element shall specify the vertical pixel density used for the scanning of the original 

impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:CaptureVerticalPixelDensityValue>500

</ansi-nist:CaptureVerticalPixelDensityValue> 

219.1.5.3.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross-reference: Part 1, Section 19.1.27 Field 14.030 Device monitoring mode (DMM) 

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 

mode of the biometric sample capture device. 

<ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED

</ansi-nist:CaptureDeviceMonitoringModeCode> 
Part 2 ANSI/NIST-ITL 2-2008

109

219.1.5.4 Element <ansi-nist:ImageCommentText> 

Cross-reference: Part 1, Section 19.1.20 Field 14.020: Comment (COM) 

This optional element may be used to insert comments or other ASCII text information with the 

image data. 

<ansi-nist:ImageCommentText>Text</ansi-nist:ImageCommentText> 

219.1.5.5 Element <ansi-nist:ImageCompressionAlgorithmText> 

Cross-reference: Part 1, Section 19.1.11 Field 14.011: Compression algorithm (CGA) 

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 

uncompressed. For those images that are to be compressed, this element shall contain the text 

value from Table 201 to indicate the compression method used for this record type. The 

preferred methods for the compression of fingerprint images are WSQ for those images scanned 

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 

information on the usage of JPEG 2000 for the compression of fingerprint images. The domain 

registrar maintains a registry of acceptable compression techniques and corresponding codes 

that may be used as they become available. 

<ansi-nist:ImageCompressionAlgorithmText>WSQ

</ansi-nist:ImageCompressionAlgorithmText> 

219.1.5.6 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 19.1.6 Field 14.006: Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

219.1.5.7 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

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 

the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 
Part 2 ANSI/NIST-ITL 2-2008

110

219.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

Cross-reference: Part 1, Section 19.1.8 Field 14.008: Scale units (SLC) 

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 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

219.1.5.9 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

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 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

219.1.5.10 Element <ansi-nist:ImageVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 19.1.10 Field 14.010: Vertical pixel scale (VPS) 

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". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 

219.1.5.11 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

Cross-reference: Part 1, Section 19.1.3 Field 14.003: Impression type (IMP) 

This mandatory element shall indicate the manner by which the fingerprint image information was 

obtained. The appropriate code choice selected from Table 211 shall be entered in this element. 

<ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1

</ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

219.1.5.12 Element <ansi-nist:FingerPositionCode> 

Cross-reference: Part 1, Section 19.1.13 Field 14.013: Finger position (FGP) 

This mandatory element shall contain the finger position that matches the tenprint image. The 

decimal code number corresponding to the known or most probable finger position shall be taken 

from Table 212 and entered as a one- or two-character ASCII value. Table 212 also lists the 

maximum image dimensions that can be transmitted for each of the sixteen possible finger 

positions. Additional finger positions may be referenced in the transaction. The code "0", for 

"Unknown Finger," shall be used to reference every finger position from one through ten. Code 

"19" shall be used to reference one or more parts of an EJI or tip. 
Part 2 ANSI/NIST-ITL 2-2008

111

<ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

219.1.5.13 Element <ansi-nist:FingerprintImageMajorCasePrint> 

This complex element shall be present if and only if the value contained by <ansinist:FingerPositionCode> is equal to “19”. This parent element contains three child elements: 

<ansi-nist:FingerPositionCode>, <ansi-nist:MajorCasePrintCode>, and <ansinist:MajorCasePrintSegmentOffset>. 

219.1.5.13.1 Element <ansi-nist:FingerPositionCode> 

Cross-reference: Part 1, Section 19.1.14 Field 14.014: Print Position Descriptors (PPD) – First 

information item 

This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. This element is the 

probable decimal finger position code (0-10) taken from Table 212. 

<ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

219.1.5.13.2 Element <ansi-nist:MajorCasePrintCode> 

Cross-reference: Part 1, Section 19.1.14 Field 14.014: Print Position Descriptors (PPD) – 

Second information item 

This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. This element is the 

code taken from Table 233 to indicate the portion of the EJI or tip image that is stored as a single 

image in the database. There may be up to 17 such images for a single finger. Images of fulllength fingers use codes FV1 through FV4 as defined in Table 233. Figure 7 is an illustration of 

the Entire Joint Image for a middle finger with each of the full finger views and constituent parts 

identified. 

<ansi-nist:MajorCasePrintCode>EJI</ansi-nist:MajorCasePrintCode> 

219.1.5.13.3 Element <ansi-nist:MajorCasePrintSegmentOffset> 

Cross-reference: Part 1, Section 19.1.15 Field 14.015: Print Position Coordinates (PPC) 

This is a mandatory subelement of <ansi-nist:FingerprintImageMajorCasePrint>, which is used 

when the value contained by <ansi-nist:FingerPositionCode> is equal to “19”. 

This element contains offsets to the locations for the bounding box of the EJI, each of the full 

finger views, or segments within the EJI. When used, this complex element shall consist of six 

mandatory information items to describe the type or portion of the image contained in this record 

and its location within an entire joint image. The information item <ansinist:SegmentFingerViewCode> is the number of the full finger view with values of "FV1" through 

"FV4". Values of “FV1” to “FV4” specify the bounding coordinates for each full finger view. The 

information item <ansi-nist:SegmentLocationCode> is used to identify the location of a segment 

within a full finger view. It will contain the not applicable code “NA” if the image portion refers to a 

full finger view or to the entire joint image locations. It shall contain “PRX”, “DST”, “MED” for a 

proximal, distal, or medial segment. The next four information items are the horizontal and vertical 
Part 2 ANSI/NIST-ITL 2-2008

112

offsets 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 (Y) are the pixel counts down. 

The location of the image portion is defined by the sequence of X coordinates (LEFT=<ansinist:SegmentLeftHorizontalCoordinateValue>, RIGHT=<ansinist:SegmentRightHorizontalCoordinateValue>) and the Y coordinates (TOP=<ansinist:SegmentTopVerticalCoordinateValue>, BOTTOM=<ansinist:SegmentBottomVerticalCoordinateValue>) of its bounding box. For the case of a fingertip, 

<ansi-nist:SegmentFingerViewCode> shall be “TIP”, and <ansi-nist:SegmentLocationCode> shall 

be “NA”. The collection of six subelements will describe either the location of the entire joint 

image, one full finger view, or segment. Individual full finger or segment definitions may be 

repeated as multiple occurrences of <ansi-nist:MajorCasePrintSegmentOffset>. 

Element <ansi-nist:MajorCasePrintSegmentOffset> shall have six child elements: <ansinist:SegmentBottomVerticalCoordinateValue>, <ansi-nist:SegmentLocationCode>, <ansinist:SegmentFingerViewCode>, <ansi-nist:SegmentLeftHorizontalCoordinateValue>, <ansinist:SegmentRightHorizontalCoordinateValue>, and <ansinist:SegmentTopVerticalCoordinateValue>. 

Part 1 cross-reference information: Element <ansi-nist:SegmentBottomVerticalCoordinateValue> 

shall correspond to the sixth information item in field 14.015. Element <ansinist:SegmentLocationCode> shall correspond to the second information item in field 14.015. 

Element <ansi-nist:SegmentFingerViewCode> shall correspond to the first information item in 

field 14.015. Element <ansi-nist:SegmentLeftHorizontalCoordinateValue> shall correspond to the 

third information item in field 14.015. Element <ansinist:SegmentRightHorizontalCoordinateValue> shall correspond to the fourth information item in 

field 14.015. Element <ansi-nist:SegmentTopVerticalCoordinateValue> shall correspond to the 

fifth information item in field 14.015. 

At least one occurrence of this subelement <ansi-nist:MajorCasePrintSegmentOffset> is 

mandatory. In practice, multiple occurrences may be used to describe the bounding boxes of 

multiple finger segments or multiple full finger views. 

<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> 

219.1.5.14 Element <itl:FingerprintImageFingerMissing> 

Cross-reference: Part 1, Section 19.1.18 Field 14.018: Amputated or bandaged (AMP) 

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: 

<ansi-nist:FingerPositionCode> and <itl:FingerMissingCode>. Element <ansi-
Part 2 ANSI/NIST-ITL 2-2008

113

nist:FingerPositionCode> is the finger number between one and ten as chosen from Table 212. 

Element <itl:FingerMissingCode> is the amputated or bandaged code (AMPCD). The following is 

a list of allowable indicators for the AMPCD: 

Descriptor AMPCD

Amputation XX 

Unable to print (e.g., bandaged) UP 

This field is to be used anytime there are fewer than expected printable fingers in a submission 

(e.g., less than four in a left or right slap or less than two in a two-thumb slap). A partially scarred 

finger should be printed. 

<itl:FingerprintImageFingerMissing> 

<ansi-nist:FingerPositionCode>10

</ansi-nist:FingerPositionCode> 

<itl: FingerMissingCode>XX

</itl:FingerMissingCode> 

</itl:FingerprintImageFingerMissing> 

219.1.5.15 Element <itl:FingerprintImageSegmentPositionSquare> 

Cross-reference: Part 1, Section 19.1.21 Field 14.021: Finger segment position(s) (SEG) 

This optional complex element shall contain offsets to the locations of image segments containing 

the individual fingers within the flat images of the four simultaneous fingers from each hand or the 

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 

(Y) are the pixel counts down. 

This element shall have five child elements: <ansi-nist:FingerPositionCode>, <ansinist:SegmentBottomVerticalCoordinateValue>, <ansinist:SegmentLeftHorizontalCoordinateValue>, <ansinist:SegmentRightHorizontalCoordinateValue>, and <ansinist:SegmentTopVerticalCoordinateValue>. A finger segment is defined first by the finger 

number in <ansi-nist:FingerPositionCode> from Table 212, the X coordinates (LEFT, RIGHT or 

<ansi-nist:SegmentLeftHorizontalCoordinateValue>, <ansinist:SegmentRightHorizontalCoordinateValue>) and the Y coordinates (TOP, BOTTOM or <ansinist:SegmentTopVerticalCoordinateValue>, <ansi-nist:SegmentBottomVerticalCoordinateValue>) 

of its bounding box. 

If more than one algorithm is used to segment the image, successive sets of finger segmentation 

positions shall be formatted as above and immediately follow the previous set. 

<itl:FingerprintImageSegmentPositionSquare> 

<ansi-nist:FingerPositionCode>7 

</ansi-nist:FingerPositionCode> 

<ansi-nist:SegmentBottomVerticalCoordinateValue>85

</ansi-nist:SegmentBottomVerticalCoordinateValue> 

<ansi-nist:SegmentLeftHorizontalCoordinateValue>160

</ansi-nist:SegmentLeftHorizontalCoordinateValue> 
Part 2 ANSI/NIST-ITL 2-2008

114

<ansi-nist:SegmentRightHorizontalCoordinateValue>200

</ansi-nist:SegmentRightHorizontalCoordinateValue> 

<ansi-nist:SegmentTopVerticalCoordinateValue>15 

</ansi-nist:SegmentTopVerticalCoordinateValue> 

</itl:FingerprintImageSegmentPositionSquare> 

219.1.5.16 Element <ansi-nist:FingerprintImageNISTQuality> 

Cross-reference: Part 1, Section 19.1.22 Field 14.022: NIST quality metric (NQM) 

This optional complex element shall contain the NIST Fingerprint Image Quality (NFIQ) scores for 

the individual finger(s) derived from the slap impressions or individual rolled fingerprints. This 

element shall have two child elements: < ansi-nist:FingerPositionCode> and <ansinist:NISTQualityMeasure>. The former element is the finger number between one and ten as 

chosen from Table 212. The latter is the quality score which is a quantitative expression of the 

predicted AFIS matcher accuracy performance of the fingerprint image. The scores range from 

"1" for the best quality image, to "5" for the worst quality image. A "254" indicates that no score 

was ever computed while an entry of "255" shall indicate a failed attempt to calculate the image 

quality metric. 

This complex element may be repeated for different fingers. 

<ansi-nist:FingerprintImageNISTQuality> 

<ansi-nist:FingerPositionCode>8 

</ansi-nist:FingerPositionCode> 

<ansi-nist:NISTQualityMeasure>1

</ansi-nist:NISTQualityMeasure> 

</ansi-nist:FingerprintImageNISTQuality> 

219.1.5.17 Element <ansi-nist:FingerprintImageSegmentationQuality> 

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 

accuracy of the location of the segmented finger within the right or left four finger or two thumbs 

slap image. For each segmented finger, there shall be four child elements: <ansinist:FingerPositionCode>, <ansi-nist:QualityAlgorithmProductIdentification>, <ansinist:QualityAlgorithmVendorIdentification>, and <ansi-nist:QualityValue>. 

The element <ansi-nist:FingerPositionCode> is a finger position code and shall contain a code 

chosen from Table 212. (This corresponds to the first information item in 14.024.) 

The other three items identify a quality score and the algorithm used to create the 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 processing or 

analysis as necessary. 

• The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

<nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

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 

score. This element contains the ASCII representation of the integer product code and 

should be within the range 1 to 65535. Element <ansi-
Part 2 ANSI/NIST-ITL 2-2008

115

nist:QualityAlgorithmProductIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the numeric product code datum. (This 

corresponds to the fourth information item in 14.024.) 

• The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

<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 

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. 

Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

third information item in 14.024.) 

• 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 

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 failed attempt to calculate a quality score. An entry of “254” shall 

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. 

(This corresponds to the second information item in 14.024.) 

The complex element <ansi-nist:FingerprintImageSegmentationQuality> may be repeated for 

each quality algorithm used. 

<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> 

219.1.5.18 Element <itl:FingerprintImageQuality> 

Cross-reference: Part 1, Section 19.1.24 Field 14.024: Fingerprint quality metric (FQM) 

This optional complex element <itl:FingerprintImageQuality> is used to specify one or more 

different metrics of fingerprint 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 fingerprint 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 fingerprint image for a particular function. 

This element shall have four child elements: <ansi-nist:FingerPositionCode>, <ansinist:QualityAlgorithmProductIdentification>, <ansi-nist:QualityAlgorithmVendorIdentification>, 

and <ansi-nist:QualityValue>. 
Part 2 ANSI/NIST-ITL 2-2008

116

The element <ansi-nist:FingerPositionCode> is a finger position code and shall contain a code 

chosen from Table 212. (This corresponds to the first information item in 14.024.) 

The other three items identify a quality score and the algorithm used to create the 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 processing or 

analysis as necessary. 

• The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

<nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

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 

score. This element contains the ASCII representation of the integer product code and 

should be within the range 1 to 65535. Element <ansinist:QualityAlgorithmProductIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the numeric product code datum. (This 

corresponds to the fourth information item in 14.024.) 

• The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

<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 

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. 

Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

third information item in 14.024.) 

• 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 

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 failed attempt to calculate a quality score. An entry of “254” shall 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. (This 

corresponds to the second information item in 14.024.) 

The complex element <itl:FingerprintImageQuality> may be repeated for each quality algorithm 

used. 

<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> 
Part 2 ANSI/NIST-ITL 2-2008

117

219.1.5.19 Element <itl:FingerprintImageSegmentPositionPolygon> 

Cross-reference: Part 1, Section 19.1.25 Field 14.025: Alternate Finger segment position(s) 

(ASEG) 

This optional complex element is an alternate approach to describing the locations for each of the 

image segments of the individual fingers within a flat image containing the capture of four 

simultaneous fingers or two simultaneous thumbs. This element uses an n-vertex polygon to 

encompass each finger image segment, where “n” is between 3 and 99. The order of the vertices 

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 

the last vertex and the first vertex shall complete the polygon. The polygon must be a simple 

plane figure with no sides crossing and no interior holes. 

This element can be used one to four times and shall consist of three child elements: <ansinist:FingerPositionCode>, <itl:PositionPolygonVertexQuantity>, and <itl:PositionPolygonVertex>. 

Element <ansi-nist:FingerPositionCode> shall consist of a finger number between 1 and 10 from 

Table 212. Element <itl:PositionPolygonVertexQuantity> shall consist of the total number of 

vertices of the polygon encompassing the finger. 

Complex element <itl:PositionPolygonVertex> shall consist of the two child elements <ansinist:PositionHorizontalCoordinateValue> and <ansi-nist:PositionVerticalCoordinateValue>, and 

<itl:PositionPolygonVertex> shall be repeated for each vertex. Each vertex shall be represented 

as horizontal and vertical pixel offsets 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 (Y) 

are the pixel counts down from the origin. A minimum of three points is required to describe a 

finger location. 

<itl:FingerprintImageSegmentPositionPolygon> 

<ansi-nist:FingerPositionCode>7 

</ansi-nist:FingerPositionCode> 

<itl:PositionPolygonVertexQuantity>3

</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>180

</ansi-nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>85

</ansi-nist:PositionVerticalCoordinateValue> 

</itl:PositionPolygonVertex> 

</itl:FingerprintImageSegmentPositionPolygon > 
Part 2 ANSI/NIST-ITL 2-2008

118

219.2 End of Type-14 variable-resolution fingerprint image record 

The Type-14 logical record shall end with the XML tag </itl:PackageFingerprintImageRecord>. 

219.3 Additional variable-resolution fingerprint image records 

Additional Type-14 records may be included in the file. For each additional fingerprint image, a 

complete Type-14 logical record is required. 

220 Type-15 variable-resolution palmprint image record 

The Type-15 logical record shall contain and be used to exchange palmprint image data together 

with fixed and user-defined textual information pertinent to the digitized image. Information 

regarding the scanning resolution used, the image size, and other parameters or comments 

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 

desired feature information required for matching purposes. 

The image data shall be acquired directly from a subject using a live-scan device, a palmprint 

card, a major case print card, or other media that contains the subject’s palmprints. 

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 

area of the full palm extending from the wrist bracelet to the tips of the fingers as one or two 

scanned images. If two images are used to represent the full palm, the lower image shall extend 

from the wrist bracelet to the top of the interdigital area (third finger joint) and shall include the 

thenar and hypothenar areas of the palm. The upper image shall extend from the bottom of the 

interdigital area to the upper tips of the fingers. This provides an adequate amount of overlap 

between the two images. The standard also has provision for encoding the interdigital, thenar, 

and hypothenar areas separately for each palm. By matching the ridge structure and details 

contained in this common area, an examiner can confidently state that both images came from 

the same palm. 

As a palmprint transaction may be used for different purposes, it may contain one or more unique 

image areas recorded from the palm or hand. A complete palmprint record set for one individual 

will normally include the writer’s palm and the full palm image(s) from each hand. Since a logical 

image record may contain only one binary, a single Type-15 record will be required for each 

writer’s palm and one to three Type-15 records for each full palm. Therefore, four to eight Type15 records will be required to represent the subject’s palmprints in a normal palmprint transaction. 

Table 235 contains palm positions, dimentions, and codes used in this section and throughout the 

standard. (Table 235 is the same as Table 35 in Part 1.) 
Part 2 ANSI/NIST-ITL 2-2008

119

Table 235 Palm codes and dimensions 

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 

220.1 XML elements for the Type-15 logical record 

The following paragraphs describe the data contained in each of the elements for the Type-15 

logical record. 

Within a Type-15 logical record, entries shall be provided in XML elements. For each element of 

the Type-15 record, Table 236 lists the “condition code” as being mandatory “M” or optional “O”, 

the XML tag name, and occurrence limits. (Table 236 corresponds to Table 34 in Part 1.) 

The Type-15 record shall be contained within this complex element: 

<itl:PackagePalmprintImageRecord> 

 [. . . Type 15 Record Content . . .] 

</itl:PackagePalmprintImageRecord> 

In the subsections that follow, text in bold between opening and closing tags is informative and 

included only for illustrative purposes, unless otherwise specifically stated (as it is for <ansinist:RecordCategoryCode>, for example). 

220.1.1 Record length 

Cross-reference: Part 1, Section 20.1.1 Field 15.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 
Part 2 ANSI/NIST-ITL 2-2008

120

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 

220.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-15 record, it shall contain a value of 15. 

<ansi-nist:RecordCategoryCode>15</ansi-nist:RecordCategoryCode> 
Part 2 ANSI/NIST-ITL 2-2008

121

220.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 20.1.2 Field 15.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the palmprint image data contained in 

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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>13</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 

220.1.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 20.1.24 Fields 15.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 
Part 2 ANSI/NIST-ITL 2-2008

122

220.1.5 Element <itl:PalmprintImage> 

This mandatory complex element contains the remaining elements in the Type-15 record, as 

described in the subsections below. 

<itl:PalmprintImage> 

[. . . Image elements . . .] 

</itl:PalmprintImage> 

220.1.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 20.1.25 Field 15.999 Image data (DATA) 

This mandatory element shall contain all of the data from a captured palmprint image. The binary 

image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

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 

than “8”, the number of bytes required to represent a pixel will be different. If compression is 

used, the pixel data shall be compressed in accordance with the compression technique specified 

in <ansi-nist:ImageCompressionAlgorithmText>. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

220.1.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

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 

shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

greater than “8” shall represent a grayscale pixel with increased precision. 

<ansi-nist:ImageBitsPerPixelQuantity>8

</ansi-nist:ImageBitsPerPixelQuantity> 

220.1.5.3 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains five child elements described in the subsections 

below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansinist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode>. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

220.1.5.3.1 Element <ansi-nist:CaptureDate> 

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 

contained 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 
Part 2 ANSI/NIST-ITL 2-2008

123

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 

represents February 29, 2008. The complete date must be a legitimate date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

<ansi-nist:CaptureDate> 

<nc:Date>2008-02-29</nc:Date> 

</ansi-nist:CaptureDate> 

220.1.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 20.1.15 Field 15.016 Scanned horizontal pixel scale (SHPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>500

</ansi-nist:CaptureHorizontalPixelDensityValue> 

220.1.5.3.3 Element <ansi-nist:CaptureOrganization> 

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 

<nc:IdentificationID> the identification of the administration or organization that originally captured 

the palmprint image contained in the record, and may contain in <nc:OrganizationName> the text 

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 

contain up to 36 identifying characters each, and the data content of this element shall be defined 

by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 
Part 2 ANSI/NIST-ITL 2-2008

124

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) 

This optional element shall specify the vertical pixel density used for the scanning of the original 

impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:CaptureVerticalPixelDensityValue>500

</ansi-nist:CaptureVerticalPixelDensityValue> 

220.1.5.3.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross-reference: Part 1, Section 20.1.22 Field 15.030 Device monitoring mode (DMM) 

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 

mode of the biometric sample capture device. 

<ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED

</ansi-nist:CaptureDeviceMonitoringModeCode> 

220.1.5.4 Element <ansi-nist:ImageCommentText> 

Cross-reference: Part 1, Section 20.1.18 Field 15.020 Comment (COM) 

This optional element may be used to insert comments or other ASCII text information with the 

palmprint image data. 

<ansi-nist:ImageCommentText>Text</ansi-nist:ImageCommentText> 

220.1.5.5 Element <ansi-nist:ImageCompressionAlgorithmText> 

Cross-reference: Part 1, Section 20.1.11 Field 15.011 Compression algorithm (CGA) 

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 

uncompressed. For those images that are to be compressed, this element shall contain the text 

value from Table 201 to indicate the compression method used for this record type. The 

preferred methods for the compression of palmprint images are WSQ for those images scanned 

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 

information on the usage of JPEG 2000 for the compression of fingerprint images. The domain 

registrar maintains a registry of acceptable compression techniques and corresponding codes 

that may be used as they become available. 

<ansi-nist:ImageCompressionAlgorithmText>WSQ

</ansi-nist:ImageCompressionAlgorithmText> 
Part 2 ANSI/NIST-ITL 2-2008

125

220.1.5.6 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 20.1.6 Field 15.006 Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

220.1.5.7 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

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 

the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 

220.1.5.8 Element <ansi-nist:ImageScaleUnitsCode> 

Cross-reference: Part 1, Section 20.1.8 Field 15.008 Scale units (SLC) 

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 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

220.1.5.9 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 20.1.7 Field 15.007 Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

220.1.5.10 Element <ansi-nist:ImageVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 20.1.10 Field 15.010 Vertical pixel scale (VPS) 

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". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 
Part 2 ANSI/NIST-ITL 2-2008

126

220.1.5.11 Element <ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

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 

obtained. The appropriate code choice selected from Table 211 for palm shall be entered in this 

element. 

<ansi-nist:FingerprintImageImpressionCaptureCategoryCode>10

</ansi-nist:FingerprintImageImpressionCaptureCategoryCode> 

220.1.5.12 Element <ansi-nist:PalmPositionCode> 

Cross-reference: Part 1, Section 20.1.13 Field 15.013 Palmprint position (PLP) 

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 

be taken from Table 235 and entered as a two-character ASCII value. 

<ansi-nist:PalmPositionCode>28</ansi-nist:PalmPositionCode> 

220.1.5.13 Element <itl:PalmprintImageQuality> 

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 

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 palmprint 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 

palmprint image for a particular function. 

Element <itl:PalmprintImageQuality> shall have four child elements: <ansinist:PalmPositionCode>, <ansi-nist:QualityAlgorithmProductIdentification>, <ansinist:QualityAlgorithmVendorIdentification>, and <ansi-nist:QualityValue>. 

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 

first information item in 15.024.) 

The other three items identify a quality score and the algorithm used to create the 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 processing or 

analysis as necessary. 

• The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

<nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

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 

score. This element contains the ASCII representation of the integer product code and 

should be within the range 1 to 65535. Element <ansinist:QualityAlgorithmProductIdentification> shall have a child element 
Part 2 ANSI/NIST-ITL 2-2008

127

<nc:IdentificationID>, which will contain the numeric product code datum. (This 

corresponds to the fourth information item in 15.024.) 

• The information item <ansi-nist:QualityAlgorithmVendorIdentification> and its child 

<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 

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. 

Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

third information item in 15.024.) 

• 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 

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 failed attempt to calculate a quality score. An entry of “254” shall 

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. 

(This corresponds to the second information item in 15.024.) 

The complex element <itl:PalmprintImageQuality> may be repeated for each quality algorithm 

used. 

<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> 

220.2 End of Type-15 variable-resolution palmprint image record 

The Type-15 logical record shall end with the XML tag </itl:PackagePalmprintImageRecord>. 

220.3 Additional variable-resolution palmprint image records 

Additional Type-15 records may be included in the file. For each additional palmprint image, a 

complete Type-15 logical record is required. 

221 Type-16 user-defined testing image record 

The Type-16 logical record shall contain and be used to exchange image data together with 

textual information fields pertinent to the digitized image. This logical record type allows the 

standard to provide the ability to exchange images not addressed by other record types in the 

standard. It is intended as the XML user-defined logical record to be used for developmental or 

test purposes. 
Part 2 ANSI/NIST-ITL 2-2008

128

The image data contained in the Type-16 logical record may be in a compressed form. With the 

exception of the XML elements described below, the format, parameters, and types of images to 

be exchanged are undefined by this standard and shall be agreed upon between the sender and 

recipient. 

221.1 XML elements for the Type-16 logical record 

The following paragraphs describe the data contained in each of the elements for the Type-16 

logical record. 

Within a Type-16 logical record, entries shall be provided in XML elements. For each element of 

the Type-16 record, Table 237 lists the “condition code” as being mandatory “M” or optional “O”, 

the XML tag name, and occurrence limits. (Table 237 corresponds to Table 36 in Part 1.) 

The Type-16 record shall be contained within this complex element: 

<itl:PackageUserDefinedTestingImageRecord> 

 [. . . Type 16 Record Content . . .] 

</itl:PackageUserDefinedTestingImageRecord> 

In the subsections that follow, text in bold between opening and closing tags is informative and 

included only for illustrative purposes, unless otherwise specifically stated (as it is for <ansinist:RecordCategoryCode>, for example). 

221.1.1 Record length 

Cross-reference: Part 1, Section 21.1.1 Field 16.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

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 

record type. For the Type-16 record, it shall contain a value of 16. 

<ansi-nist:RecordCategoryCode>16</ansi-nist:RecordCategoryCode> 

221.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 21.1.2 Field 16.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the user-defined testing image data 

contained in the record. The content of this element shall match the <ansinist:ImageReferenceIdentification> found in the <ansi-nist:TransactionContentSummary> 

element of the Type-1 record. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>14</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

129

Table 237 Type-16 Variable-resolution user-defined testing image record layout 

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 

221.1.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 21.1.24 Fields 16.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 
Part 2 ANSI/NIST-ITL 2-2008

130

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 

221.1.5 Element <itl:TestImage> 

This mandatory complex element contains the remaining elements in the Type-16 record, as 

described in the subsections below. 

<itl:TestImage> 

[. . . Image elements . . .] 

</itl:TestImage> 

221.1.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 21.1.25 Field 16.999: Image data (DATA) 

This mandatory element shall contain all of the pixel data from a captured image. The binary 

image data shall be converted to ASCII characters using the Base64 encoding algorithm. 

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 

than “8”, the number of bytes required to represent a pixel will be different. If compression is 

used, the pixel data shall be compressed in accordance with the compression technique specified 

in <ansi-nist:ImageCompressionAlgorithmText>. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 
Part 2 ANSI/NIST-ITL 2-2008

131

221.1.5.2 Element <nc:BinaryDescriptionText> 

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 

content shall be defined by the user and be in accordance with the receiving agency. 

<nc:BinaryDescriptionText>Test Image</nc:BinaryDescriptionText> 

221.1.5.3 Element <ansi-nist:ImageBitsPerPixelQuantity> 

Cross-reference: Part 1, Section 21.1.12 Field 16.012: Bits per pixel (BPX) 

This mandatory element shall contain the number of bits used to represent a pixel. This element 

shall contain an entry of “8” for normal grayscale values of “0” to “255”. Any entry in this element 

greater than “8” shall represent a grayscale pixel with increased precision. 

<ansi-nist:ImageBitsPerPixelQuantity>16

</ansi-nist:ImageBitsPerPixelQuantity> 

221.1.5.4 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains five child elements described in the subsections 

below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansinist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode>. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

221.1.5.4.1 Element <ansi-nist:CaptureDate> 

Cross-reference: Part 1, Section 21.1.5 Field 16.005: User-defined testing date (UTD) 

This mandatory element <ansi-nist:CaptureDate> shall contain the date that the image contained 

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; 

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 

February 29, 2008. The complete date must be a legitimate date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

<ansi-nist:CaptureDate> 

<nc:Date>2008-02-29</nc:Date> 

</ansi-nist:CaptureDate> 
Part 2 ANSI/NIST-ITL 2-2008

132

221.1.5.4.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 21.1.15 Field 16.016: Scanned horizontal pixel scale (SHPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>500

</ansi-nist:CaptureHorizontalPixelDensityValue> 

221.1.5.4.3 Element <ansi-nist:CaptureOrganization> 

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 

<nc:IdentificationID> the identification of the administration or organization that originally captured 

the user-defined testing image contained in the record, and may contain in 

<nc:OrganizationName> the text 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 contain up to 36 identifying characters each, and the data content 

of this element shall be defined by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 

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) 

This optional element shall specify the vertical pixel density used for the scanning of the original 

impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:CaptureVerticalPixelDensityValue>500

</ansi-nist:CaptureVerticalPixelDensityValue> 
Part 2 ANSI/NIST-ITL 2-2008

133

221.1.5.4.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross-reference: Part 1, Section 21.1.22 Field 16.030 Device monitoring mode (DMM) 

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 

mode of the biometric sample capture device. 

<ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED

</ansi-nist:CaptureDeviceMonitoringModeCode> 

221.1.5.5 Element <ansi-nist:ImageColorSpaceCode> 

Cross-reference: Part 1, Section 21.1.13 Field 16.013: Color space (CSP) 

This mandatory element shall contain an ASCII entry from Table 203 to identify the color space 

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 <ansinist:ImageColorSpaceCode> in the Type-10 record contains additional information for the color 

space element. 

<ansi-nist:ImageColorSpaceCode>YCC 

</ansi-nist:ImageColorSpaceCode> 

221.1.5.6 Element <ansi-nist:ImageCommentText> 

Cross-reference: Part 1, Section 21.1.18 Field 16.020: Comment (COM) 

This optional element may be used to insert comments or other ASCII text information with the 

user-defined testing image data. 

<ansi-nist:ImageCommentText>Text</ansi-nist:ImageCommentText> 

221.1.5.7 Element <ansi-nist:ImageCompressionAlgorithmText> 

Cross-reference: Part 1, Section 21.1.11 Field 16.011: Compression algorithm (CGA) 

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 

uncompressed. For those images that are to be losslessly compressed, this element shall contain 

the text value from Table 201 to indicate the compression method used for this record type. See 

Section 205.6.1 for additional information on the usage of JPEG 2000 for the 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. 

<ansi-nist:ImageCompressionAlgorithmText>JPEGB

</ansi-nist:ImageCompressionAlgorithmText> 
Part 2 ANSI/NIST-ITL 2-2008

134

221.1.5.8 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 21.1.6 Field 16.006: Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

221.1.5.9 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

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 

the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 

221.1.5.10 Element <ansi-nist:ImageQuality> 

Cross-reference: Part 1, Section 21.1.20 Field 16.024: User-defined testing quality score (UQS) 

This optional complex element shall specify a quality score for the user-defined testing image 

stored in this record. This element shall have three child elements: <ansinist:QualityAlgorithmProductIdentification>, <ansi-nist:QualityValue>, and <ansinist:QualityMeasureVendorIdentification>. They identify a quality score and the algorithm used to 

create the 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 processing or analysis as necessary. 

1. The information item <ansi-nist:QualityAlgorithmProductIdentification> and its child 

<nc:IdentificationID> shall specify a numeric product code assigned by the vendor of the 

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 

score. This element contains the ASCII representation of the integer product code and 

should be within the range 1 to 65535. Element <ansinist:QualityAlgorithmProductIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the numeric product code datum. (This 

corresponds to the third information item in 16.024.) 

2. 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 

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 failed attempt to calculate a quality score. An entry of “254” shall 

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. 

(This corresponds to the first information item in 16.024.) 
Part 2 ANSI/NIST-ITL 2-2008

135

3. The information item <ansi-nist:QualityMeasureVendorIdentification> and its child 

<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 

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. 

Element <ansi-nist:QualityAlgorithmVendorIdentification> shall have a child element 

<nc:IdentificationID>, which will contain the vendor ID datum. (This corresponds to the 

second information item in 16.024.) 

<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> 

221.1.5.11 Element <ansi-nist:ImageScaleUnitsCode> 

Cross-reference: Part 1, Section 21.1.8 Field 16.008: Scale units (SLC) 

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 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

221.1.5.12 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 21.1.7 Field 16.007: Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

221.1.5.13 Element <ansi-nist:ImageVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 21.1.10 Field 16.010: Vertical pixel scale (VPS) 

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". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 
Part 2 ANSI/NIST-ITL 2-2008

136

221.2 End of Type-16 user-defined testing image record 

The Type-16 logical record shall end with the XML tag 

</itl:PackageUserDefinedTestingImageRecord>. 

221.3 Additional Type-16 user-defined testing image records 

Additional Type-16 records may be included in the file. For each additional image, a complete 

Type-16 logical record is required. 

222 Type-17 Iris image record 

222.1 General 

The Part 2 XML version of the Type-17 logical record shall contain and be used to exchange 

generic iris image data using mandatory elements of this record type. Optional elements may be 

used to exchange additional information available in the INCITS 379-2004 – Iris Image 

Interchange Format standard and the ISO/IEC 19794-6 iris image data interchange format 

standard. Images may be monochrome or color with 256 or more intensity levels (grey or percolor component) and vary in size depending on field of view and compression. 

The iris standards specify two alternative image interchange formats for biometric authentication 

systems that utilize iris recognition. The first, which is represented in this record type, is based on 

a rectilinear image storage format that specifies a raw, uncompressed or compressed array of 

intensity values. The second is an image data format based on a polar image specification and is 

not represented in this logical record type. If such a polar representation is required for a specific 

application, a Type-99 CBEFF biometric data record may be used. 

222.2 XML elements for the Type-17 logical record 

The following paragraphs describe the data contained in each of the elements for the Type-17 

logical record. 

Within a Type-17 logical record, entries shall be provided in XML elements. For each element of 

the Type-17 record, Table 238 lists the “condition code” as being mandatory “M” or optional “O”, 

the XML tag name, and occurrence limits. (Table 238 corresponds to Table 37 in Part 1.) It is 

required that all elements of the record are ordered as described in the subsections below. 

The Type-17 record shall be contained within this complex element: 

<itl:PackageIrisImageRecord> 

 [. . . Type 17 Record Content . . .] 

</itl:PackageIrisImageRecord> 

In the subsections that follow, text in bold between opening and closing tags is informative and 

included only for illustrative purposes, unless otherwise specifically stated (as it is for <ansinist:RecordCategoryCode>, for example). 
Part 2 ANSI/NIST-ITL 2-2008

137

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 – 

17.998 

<itl:UserDefinedFields> 0 Unlim 

 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 

 <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 
Part 2 ANSI/NIST-ITL 2-2008

138

Part 1 

Ident

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name Occur count 

 min Max 

MMS O 17.019 <ansi-nist:CaptureDeviceModelText> 0 1 

MMS O 17.019 <ansi-nist:CaptureDeviceSerialNumberText> 0 1 

IPC O 17.016 <ansi-nist:IrisImageHorizontalOrientationCode> 0 1 

IPC O 17.016 <ansi-nist:IrisImageScanCategoryCode> 0 1 

IPC O 17.016 <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 

222.2.1 Record length 

Cross-reference: Part 1, Section 22.2.1 Field 17.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

222.2.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-17 record, it shall contain a value of 17. 

<ansi-nist:RecordCategoryCode>17</ansi-nist:RecordCategoryCode> 

222.2.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 22.2.2 Field 17.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the iris image data contained in 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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>13</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

139

222.2.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 22.2.30 Fields 17.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 

222.2.5 Element <itl:IrisImage> 

This is a mandatory complex element. All of the remaining elements in the Type-17 record are 

nested within, as described in the subsections below. 

<itl:IrisImage> 

[. . . Image elements . . .] 

</itl:IrisImage> 

222.2.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 22.2.31 Field 17.999: Image data (DATA) 

This mandatory element shall contain the iris image. The binary image data shall be converted to 

ASCII characters using the Base64 encoding algorithm. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 
Part 2 ANSI/NIST-ITL 2-2008

140

222.2.5.2 Element <ansi-nist:ImageBitsPerPixelQuantity> 

Cross-reference: Part 1, Section 22.2.12 Field 17.012: Bits per pixel (BPX) 

This mandatory element shall contain the number of bits used to represent a pixel. This element 

shall contain an entry of “8” for normal grayscale values of “0” to “255” or each RGB color 

component. Any entry in this element greater than “8” shall represent a grayscale pixel with 

increased precision. 

<ansi-nist:ImageBitsPerPixelQuantity>16

</ansi-nist:ImageBitsPerPixelQuantity> 

222.2.5.3 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains five child elements described in the subsections 

below: <ansi-nist:CaptureDate>, <ansi-nist:CaptureHorizontalPixelDensityValue>, <ansinist:CaptureOrganization>, <ansi-nist:CaptureVerticalPixelDensityValue>, and <ansinist:CaptureDeviceMonitoringModeCode. 

<ansi-nist:ImageCaptureDetail> 

[. . . Image capture elements . . .] 

</ansi-nist:ImageCaptureDetail> 

222.2.5.3.1 Element <ansi-nist:CaptureDate> 

Cross-reference: Part 1, Section 22.2.5 Field 17.005: Iris capture date (ICD) 

This mandatory element <ansi-nist:CaptureDate> shall contain the date that the iris image 

contained 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; 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 February 29, 2008. The complete date must be a legitimate date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:Date>, which will 

contain capture date data. 

<ansi-nist:CaptureDate> 

<nc:Date>2008-02-29</nc:Date> 

</ansi-nist:CaptureDate> 

222.2.5.3.2 Element <ansi-nist:CaptureHorizontalPixelDensityValue> 

Cross-reference: Part 1, Section 22.2.22 Field 17.022: Scanned horizontal pixel scale (SHPS) 

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". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>500

</ansi-nist:CaptureHorizontalPixelDensityValue> 
Part 2 ANSI/NIST-ITL 2-2008

141

222.2.5.3.3 Element <ansi-nist:CaptureOrganization> 

Cross-reference: Part 1, Section 22.2.4 Field 17.004: Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

<nc:IdentificationID> the identification of the administration or organization that originally captured 

the iris image contained in the record, and may contain in <nc:OrganizationName> the text 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 contain up to 

36 identifying characters each, and the data content of this element shall be defined by the user 

and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 

222.2.5.3.4 Element <ansi-nist:CaptureVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 22.2.23 Field 17.023: Scanned vertical pixel scale (SVPS) 

This optional element shall specify the vertical pixel density used for the scanning of the original 

impression providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:CaptureVerticalPixelDensityValue>500

</ansi-nist:CaptureVerticalPixelDensityValue> 

222.2.5.3.5 Element <ansi-nist:CaptureDeviceMonitoringModeCode> 

Cross-reference: Part 1, Section 22.2.28 Field 10.030: Device monitoring mode (DMM) 

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 

mode of the biometric sample capture device. 

<ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED

</ansi-nist:CaptureDeviceMonitoringModeCode> 

222.2.5.4 Element <ansi-nist:ImageColorSpaceCode> 

Cross-reference: Part 1, Section 22.2.13 Field 17.013: Color space (CSP) 

This mandatory element shall contain an ASCII entry from Table 203 to identify the color space 

used to exchange the image data. If the color space for an RGB image cannot be determined, an 
Part 2 ANSI/NIST-ITL 2-2008

142

entry of "RGB" shall be entered in this element. The description for <ansinist:ImageColorSpaceCode> in the Type-10 record contains additional information for the color 

space element. 

<ansi-nist:ImageColorSpaceCode>YCC 

</ansi-nist:ImageColorSpaceCode> 

222.2.5.5 Element <ansi-nist:ImageCommentText> 

Cross-reference: Part 1, Section 22.2.21 Field 17.021: Comment (COM) 

This optional element may be used to insert comments or other ASCII text information with the 

iris image data. 

The simple element <ansi-nist:ImageCommentText> may have multiple occurrences if the 

sending and receiving agencies agree to have multiple, separate comments. 

<ansi-nist:ImageCommentText>Text</ansi-nist:ImageCommentText> 

<ansi-nist:ImageCommentText>Text</ansi-nist:ImageCommentText> 

222.2.5.6 Element <ansi-nist:ImageCompressionAlgorithmText> 

Cross-reference: Part 1, Section 22.2.11 Field 17.011: Compression algorithm (CGA) 

This mandatory element shall specify the algorithm used to compress the color or grayscale 

images. Table 201 contains the codes for the compression methods. An entry of "NONE" in this 

field indicates that the data contained in this record is uncompressed. The image shall be 

represented as an array of n rows by m columns by at least 8-bit pixels. Each pixel in a 

monochrome image shall be represented by eight or more bits. Color images shall be 

represented as a sequential sample of a red, green, and blue intensity for each pixel. The image 

shall be organized in row-major order, with the lowest address corresponding to the upper left 

corner of the image. 

For those images that are to be compressed, the method for the compression of iris images is 

specified by the baseline mode of the JPEG algorithm or JPEG 2000. For best results, the 

compression ratio should not exceed 6:1. 

<ansi-nist:ImageCompressionAlgorithmText>JPEGB

</ansi-nist:ImageCompressionAlgorithmText> 

222.2.5.7 Element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 22.2.6 Field 17.006: Horizontal line length (HLL) 

This mandatory element shall contain the number of pixels contained on a single horizontal line of 

the transmitted image. 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 
Part 2 ANSI/NIST-ITL 2-2008

143

222.2.5.8 Element <ansi-nist:ImageHorizontalPixelDensityValue> 

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 

the transmitted image providing <ansi-nist:ImageScaleUnitsCode> contains a "1" or a "2". 

Otherwise, it indicates the horizontal component of the pixel aspect ratio. 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 

222.2.5.9 Element <ansi-nist:ImageQuality> 

Cross-reference: Part 1, Section 22.2.24 Field 17.024: Image Quality Score (IQS) 

This optional element shall specify quality score data for the iris image stored in this record. 

There are three child elements. They identify a quality score and the algorithm used to create the 

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 

processing or analysis as necessary. 

The parent element <ansi-nist:ImageQuality> may have multiple occurrences, one for each 

quality algorithm used. 

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 

with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms 

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 

should be within the range 1 to 65,535. 

2. The child element <ansi-nist:QualityValue> shall be a quantitative expression of the 

predicted matching performance of the biometric sample. This element contains the ASCII 

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 

failed attempt to calculate a quality score. An entry of “254” shall 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. 

3. The child element <ansi-nist:QualityMeasureVendorIdentification> 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 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. This complex element contains a child element <nc:IdentificationID> which shall 

contain the identification datum. 

<ansi-nist:ImageQuality> 

<ansi-nist:QualityAlgorithmProductIdentification> 

<nc:IdentificationID>28488</nc:IdentificationID> 

</ansi-nist:QualityAlgorithmProductIdentification> 

<ansi-nist:QualityValue>100

</ansi-nist:QualityValue> 

<ansi-nist:QualityMeasureVendorIdentification> 

<nc:IdentificationID>FFF0</nc:IdentificationID> 
Part 2 ANSI/NIST-ITL 2-2008

144

</ansi-nist:QualityMeasureVendorIdentification> 

</ansi-nist:ImageQuality> 

222.2.5.10 Element <ansi-nist:ImageScaleUnitsCode> 

Cross-reference: Part 1, Section 22.2.8 Field 17.008: Scale units (SLC) 

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 

centimeter. A "0" in this element indicates no scale is given. For this case, the quotient of 

HPS/VPS gives the pixel aspect ratio. 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

222.2.5.11 Element <ansi-nist:ImageVerticalLineLengthPixelQuantity> 

Cross-reference: Part 1, Section 22.2.7 Field 17.007: Vertical line length (VLL) 

This mandatory element shall contain the number of horizontal lines contained in the transmitted 

image. 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

222.2.5.12 Element <ansi-nist:ImageVerticalPixelDensityValue> 

Cross-reference: Part 1, Section 22.2.10 Field 17.010: Vertical pixel scale (VPS) 

This mandatory elemeent 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". 

Otherwise, it indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 

222.2.5.13 Element <ansi-nist:IrisEyePositionCode> 

Cross-reference: Part 1, Section 22.2.3 Field 17.003: Feature identifier (FID) 

This mandatory element shall contain an identifier for the eye represented by the image in the 

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 

entry of “2” in this element indicates that the image in this record is the subject's left eye. 

<ansi-nist:IrisEyePositionCode>2

</ansi-nist:IrisEyePositionCode> 
Part 2 ANSI/NIST-ITL 2-2008

145

222.2.5.14 Element <ansi-nist:IrisEyeRotationAngleMeasure> 

Cross-reference: Part 1, Section 22.2.14 Field 17.014: Rotation Angle of Eye (RAE) 

This optional element shall indicate the rotation angle of the eye. For rectilinear images, rotation 

angle = round (65536 * angle / 360) modulo 65536. The angle is measured in degrees from 

horizontal to the interpupillary line. The value “FFFF” indicates rotation angle of eye is undefined. 

<ansi-nist:IrisEyeRotationAngleMeasure>8192 

</ansi-nist:IrisEyeRotationAngleMeasure> 

222.2.5.15 Element <ansi-nist:IrisEyeRotationUncertaintyValueText> 

Cross-reference: Part 1, Section 22.2.15 Field 17.015: Rotation Uncertainty (RAU) 

This optional field shall indicate the rotation uncertainty. The rotation uncertainty is equal to 

[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. 

<ansi-nist:IrisEyeRotationUncertainty>FFFF 

</ansi-nist:IrisEyeRotationUncertainty> 

222.2.5.16 Element <ansi-nist:IrisImageCapture> 

This mandatory complex element contains eight child elements described in the subsections 

below. The eight child elements shall be contained within this parent element: 

<ansi-nist:IrisImageCapture> 

[. . . Iris image capture elements . . .] 

</ansi-nist:IrisImageCapture> 

222.2.5.16.1 Element <ansi-nist:CaptureDeviceGlobalIdentification> 

Cross-reference: Part 1, Section 22.2.18 Field 17.018: Global Unique Identifier (GUI) 

This optional element shall contain a 16-byte string to indicate a GUID – a globally unique 

identifier. 

Complex element <ansi-nist:CaptureDeviceGlobalIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the identifier datum. 

<ansi-nist:CaptureDeviceGlobalIdentification> 

<nc:IdentificationID>A2849B293059C200</nc:IdentificationID> 

</ansi-nist:CaptureDeviceGlobalIdentification> 

222.2.5.16.2 Element <ansi-nist:CaptureDeviceIdentification> 

Cross-reference: Part 1, Section 22.2.17 Field 17.017: Device Unique Identifier (DUI) 

This optional element shall contain a sixteen-byte string uniquely identifying the device or source 

of the data. This data can be one of: (1) Device Serial number, identified by the first character “D”, 

(2) Host PC Mac address, identified by the first character “M”, (3) Host PC processor ID, identified 

by the first character “P”, and (4) No serial number, identified by all zeros. 
Part 2 ANSI/NIST-ITL 2-2008

146

Complex element <ansi-nist:CaptureDeviceIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the identifier datum. 

<ansi-nist:CaptureDeviceIdentification> 

<nc:IdentificationID>P270NEIS67830001</nc:IdentificationID> 

</ansi-nist:CaptureDeviceIdentification> 

222.2.5.16.3 Element <ansi-nist:CaptureDeviceMakeText> 

Cross-reference: Part 1, Section 22.2.19 Field 17.019: Make/Model/Serial Number 

(MMS), subfield make 

This optional element contains the make for the iris capture device. This information item shall be 

1 to 50 characters. This information item may indicate that information is unknown with the value 

“0”. 

<ansi-nist:CaptureDeviceMakeText>Text

</ansi-nist:CaptureDeviceMakeText> 

222.2.5.16.4 Element <ansi-nist:CaptureDeviceModelText> 

Cross-reference: Part 1, Section 22.2.19 Field 17.019: Make/Model/Serial Number 

(MMS), subfield model 

This optional element contains the model for the iris capture device. This information item shall 

be 1 to 50 characters. This information item may indicate that information is unknown with the 

value “0”. 

<ansi-nist:CaptureDeviceModelText>Text

</ansi-nist:CaptureDeviceModelText> 

222.2.5.16.5 Element <ansi-nist:CaptureDeviceSerialNumberText> 

Cross-reference: Part 1, Section 22.2.19 Field 17.019: Make/Model/Serial Number 

(MMS), subfield serial number 

This optional element contains the serial number for the iris capture device. This information item 

shall be 1 to 50 characters. This information item may indicate that information is unknown with 

the value “0”. 

<ansi-nist:CaptureDeviceSerialNumberText>Text

</ansi-nist:CaptureDeviceSerialNumberText> 

222.2.5.16.6 Element <ansi-nist:IrisImageHorizontalOrientationCode> 

Cross-reference: Part 1, Section 22.2.16 Field 17.016: Image Property Code (IPC), 

subfield horizontal orientation 

This optional element shall contain the horizontal orientation of the image. 

Values for Horizontal Orientation shall be one of: “0” for Undefined, “1” for Base, or “2” for 

Flipped. “Base” orientation refers to images corresponding to the view facing the subject, where 

the nasal side of subject’s left eye or outer edge of the subject’s right eye is on the left side of the 
Part 2 ANSI/NIST-ITL 2-2008

147

image. “Flipped” orientation refers to images where the orientation is opposite from that 

described for “Base”. 

<ansi-nist:IrisImageHorizontalOrientationCode>2

</ansi-nist:IrisImageHorizontalOrientationCode> 

222.2.5.16.7 Element <ansi-nist:IrisImageScanCategoryCode> 

Cross-reference: Part 1, Section 22.2.16 Field 17.016: Image Property Code (IPC), 

subfield scan type 

This optional element shall contain the scan type of the image. 

Values for Scan Type shall be one of: “0” for Undefined, “1” for Progressive, “2” for Interlace 

Frame, or “3” for Interlace Field. “Progressive” indicates that the image was captured using 

progressive scanning, in which case all image lines are generated sequentially. “Interlace Frame” 

indicates that the image was captured using interlaced scanning, in which two fields are 

generated in sequence, the first composed of odd-numbered lines and the second of evennumbered lines. “Interlace Field” indicates that the image was captured using interlaced 

scanning, in which only one field is generated, and then each line is duplicated to produce a full 

size image. 

<ansi-nist:IrisImageScanCategoryCode>3

</ansi-nist:IrisImageScanCategoryCode> 

222.2.5.16.8 Element <ansi-nist:IrisImageVerticalOrientationCode> 

Cross-reference: Part 1, Section 22.2.16 Field 17.016: Image Property Code (IPC), 

subfield vertical orientation 

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. 

“Base” orientation refers to images where the superior (top) edge of the eye is at the top of the 

image. “Flipped” orientation refers to images where the orientation is opposite from that 

described for “Base”. 

<ansi-nist:IrisImageVerticalOrientationCode>1

</ansi-nist:IrisImageVerticalOrientationCode> 

222.2.5.17 Element <ansi-nist:IrisEyeColorAttributeCode> 

Cross-reference: Part 1, Section 22.2.20 Field 17.020: Eye Color (ECL) 

This optional element shall specify the subject's eye color. When used, this element shall contain 

an entry chosen from Table 223. 

<ansi-nist:IrisEyeColorAttributeCode>MUL 

</ansi-nist:IrisEyeColorAttributeCode> 
Part 2 ANSI/NIST-ITL 2-2008

148

222.2.5.18 Element <ansi-nist:IrisImageAcquisitionLightingSpectrumValue> 

Cross-reference: Part 1, Section 22.2.25 Field 17.025: Acquisition Lighting Spectrum (ALS) 

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 

full-spectrum illumination (~380-740nm), or “OTHER” for other illumination. 

<ansi-nist:IrisImageAcquisitionLightingSpectrumValue>VIS 

</ansi-nist:IrisImageAcquisitionLightingSpectrumValue> 

222.2.5.19 Element <ansi-nist:IrisDiameterPixelQuantity> 

Cross-reference: Part 1, Section 22.2.26 Field 17.026: Iris Diameter (IRD) 

This optional element shall specify the expected iris diameter in pixels. 

<ansi-nist:IrisDiameterPixelQuantity>304 

</ansi-nist:IrisDiameterPixelQuantity> 

222.3 End of Type-17 Iris Data Record 

The Type-17 logical record shall end with the XML tag </itl:PackageIrisImageRecord>. 

222.4 Additional Type-17 Iris Data Records 

Additional Type-17 records may be included in the exchange package. For each additional iris 

image, a complete Type-17 logical record is required. 

223 Type-99 CBEFF record 

The Type-99 logical record shall contain and be used to exchange biometric data that is not 

supported by other ANSI/NIST-ITL logical records. This data is exchanged in a format that 

conforms to INCITS 398-2005, the Common Biometric Exchange Formats Framework. 

The CBEFF conformant Biometric Information Record (BIR) used by the Type-99 logical record 

includes a common Header and a Biometric Data Block (BDB). Two mandatory components of 

the CBEFF Header are Format Owner and Format Type. The Format Owner denotes the vendor, 

standards body, working group, or industry consortium that has defined the format of the 

biometric data (the data contained in the BDB). A CBEFF requirement is that format owners 

register with the IBIA for an assigned identifier of the format owner. The values used for Format 

Type are assigned by the format owner and represent a specific BDB format as specified by the 

format owner. This may be a nonstandard, unpublished data format or a data format that has 

been standardized by an industry group, consortium, or standards body. It is the combination of 

CBEFF Format Owner and CBEFF Format Type that uniquely identifies the BDB format. 

This Part 2 XML version of the Type-99 logical record provides the CBEFF elements necessary 

for users to send, receive, and interpret biometric data in any registered BDB format (with the 

exception of biometric data which is exchanged using the other logical records in this standard). 

The data carried in the Biometric Data Block element (<nc:BinaryBase64Object>) is the BDB. 

The format of that data is identified by the BDB Format Owner (<ansi-
Part 2 ANSI/NIST-ITL 2-2008

149

nist:CBEFFFormatOwnerIdentification>) and BDB Format Type (<ansinist:CBEFFFormatCategoryIdentification>) as described by the CBEFF standard. 

223.1 XML elements for the Type-99 logical record 

The following paragraphs describe the data contained in each of the elements for the Type-99 

logical record. 

Within a Type-99 logical record, entries shall be provided in XML elements. For each element of 

the Type-99 record, Table 239 lists the “condition code” as being mandatory “M” or optional “O”, 

the XML tag name, and occurrence limits. (Table 239 corresponds to Table 38 in Part 1.) It is 

required that all elements of the record are ordered as described in the subsections below. 

Annex F provides an example that includes the Type-99 record. 

The Type-99 record shall be contained within this complex element: 

<itl:PackageCBEFFBiometricDataRecord> 

 [. . . Type 99 Record Content . . .] 

</itl:PackageCBEFFBiometricDataRecord> 

In the subsections that follow, text in bold between opening and closing tags is informative and 

included only for illustrative purposes, unless otherwise specifically stated (as it is for <ansinist:RecordCategoryCode>, for example). 

223.1.1 Record length 

Cross-reference: Part 1, Section 23.1.1 Field 99.001: Logical record length (LEN) 

There is no corresponding Part 2 XML element. 

223.1.2 Element <ansi-nist:RecordCategoryCode> 

This mandatory Part 2 element has no corresponding field in Part 1. It is used to identify the 

record type. For the Type-99 record, it shall contain a value of 99. 

<ansi-nist:RecordCategoryCode>99</ansi-nist:RecordCategoryCode> 

223.1.3 Element <ansi-nist:ImageReferenceIdentification> 

Cross-reference: Part 1, Section 23.1.2 Field 99.002: Image designation character (IDC) 

This mandatory complex element shall be used to identify the CBEFF data contained in 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. 

Complex element <ansi-nist:ImageReferenceIdentification> shall contain the simple element 

<nc:IdentificationID>, which shall contain the image reference identification datum. 

<ansi-nist:ImageReferenceIdentification> 

<nc:IdentificationID>14</nc:IdentificationID> 

</ansi-nist:ImageReferenceIdentification> 
Part 2 ANSI/NIST-ITL 2-2008

150

Table 239 Type-99 CBEFF biometric data record layout 

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 – 

99.998 

<itl:UserDefinedFields> 0 Unlim 

 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 

223.1.4 Element <itl:UserDefinedFields> 

Cross-reference: Part 1, Section 23.1.13 Fields 99.200-998: User-defined fields (UDF) 

These elements are user-definable. Their size and content shall be defined by the user and be in 

accordance with the receiving agency. If present, they shall contain well-formed XML and ASCII 

content values. 

Complex element <itl:UserDefinedFields> is abstract, and as such is unusable by itself. 

Implementers should define, in an extension schema, a substitution element containing userdefined child elements from the user’s domain. 
Part 2 ANSI/NIST-ITL 2-2008

151

A substitution element should be defined in a user’s extension schema similar to this: 

<xsd:element name="UserDefinedFields" 

 substitutionGroup="itl:UserDefinedFields" 

 type="user-domain:UserDefinedFieldsType"/> 

<xsd:complexType name="UserDefinedFieldsType"> 

<xsd:complexContent> 

<xsd:extension base="s:ComplexObjectType"> 

<xsd:sequence> 

 <xsd:element ref="user-domain:OneField"/> 

 <xsd:element ref="user-domain:TwoField”"/> 

</xsd:sequence> 

</xsd:extension> 

</xsd:complexContent> 

</xsd:complexType> 

The element would then appear in an instance document like this: 

<user-domain:UserDefinedFields> 

<user-domain:OneField>Text</user-domain:OneField> 

<user-domain:TwoField>Text</user-domain:TwoField> 

</user-domain:UserDefinedFields> 

223.1.5 Element <ansi-nist:CBEFFImage> 

This is a mandatory complex element. All of the remaining elements in the Type-99 record are 

nested within, as described in the subsections below. 

<ansi-nist:CBEFFImage> 

[. . . CBEFF elements . . .] 

</ansi-nist:CBEFFImage> 

223.1.5.1 Element <nc:BinaryBase64Object> 

Cross-reference: Part 1, Section 23.1.14 Field 99.999: Biometric Data Block (BDB) 

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. 

<nc:BinaryBase64Object>base64 data</nc:BinaryBase64Object> 

223.1.5.2 Element <ansi-nist:ImageCaptureDetail> 

This mandatory complex element contains two child elements described in the subsections 

below: <ansi-nist:CaptureDate>, and <ansi-nist:CaptureOrganization>. 

<ansi-nist:ImageCaptureDetail> 

[. . . Date, time and source agency elements . . .] 

</ansi-nist:ImageCaptureDetail> 
Part 2 ANSI/NIST-ITL 2-2008

152

223.1.5.2.1 Element <ansi-nist:CaptureDate> 

Cross-reference: Part 1, Section 23.1.5 Field 99.005: Biometric creation date (BCD) 

This mandatory element shall contain the date and time that the biometric sample was captured. 

The date and time shall appear as twenty characters in the format YYYY-MM-DDThh:mm:ssZ. 

The YYYY characters shall represent the year; 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 of the 

month; the character T separates the date from the time; the hh characters represent the hour; 

the mm the minute; the ss represents the second; and Z denotes Coordinated Universal Time, 

which is abbreviated UTC. The complete date shall not exceed the current date. 

Complex element <ansi-nist:CaptureDate> shall have the simple element <nc:DateTime>, which 

will contain transaction date and time data. 

<ansi-nist:CaptureDate> 

<nc:DateTime>2008-02-29T05:25:00Z</nc:DateTime>

</ansi-nist:CaptureDate> 

223.1.5.2.2 Element <ansi-nist:CaptureOrganization> 

Cross-reference: Part 1, Section 23.1.4 Field 99.004: Source agency / ORI (SRC) 

This mandatory complex element <ansi-nist:CaptureOrganization> shall contain in 

<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 

text 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 

contain up to 36 identifying characters each and the data content of this element shall be defined 

by the user and be in accordance with the receiving agency. 

Element <ansi-nist:CaptureOrganization> shall have two child elements: a mandatory 

<nc:OrganizationIdentification> and an optional <nc:OrganizationName>. Complex element 

<nc:OrganizationIdentification> shall have a single child element <nc:IdentificationID>, which will 

contain the alphanumeric organizational ID datum. Element <nc:OrganizationName> shall 

contain the datum for the text name of the organization. 

<ansi-nist:CaptureOrganization> 

<nc:OrganizationIdentification> 

<nc:IdentificationID>WI013415Y</nc:IdentificationID> 

</nc:OrganizationIdentification> 

<nc:OrganizationName>Text</nc:OrganizationName> 

</ansi-nist:CaptureOrganization> 

223.1.5.3 Element <ansi-nist:ImageQuality> 

Cross-reference: Part 1, Section 23.1.9 Field 99.102: Biometric Data Quality (BDQ) 

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 

to create the 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 processing or analysis as necessary. 
Part 2 ANSI/NIST-ITL 2-2008

153

The parent element <ansi-nist:ImageQuality> may have multiple occurrences, one for each 

quality algorithm used. 

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 

with the IBIA, but it is not required to be registered. It indicates which of the vendor’s algorithms 

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 

should be within the range 1 to 65,535. 

2. The child element <ansi-nist:QualityValue> shall be a quantitative expression of the 

predicted matching performance of the biometric sample. This element contains the ASCII 

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 

failed attempt to calculate a quality score. An entry of “254” shall 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. 

3. The child element <ansi-nist:QualityMeasureVendorIdentification> 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 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. This complex element contains a child element <nc:IdentificationID> which shall 

contain the identification datum. 

<ansi-nist:ImageQuality> 

<ansi-nist:QualityAlgorithmProductIdentification> 

<nc:IdentificationID>28488</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> 

223.1.5.4 Element <ansi-nist:CBEFFFormatOwnerIdentification> 

Cross-reference: Part 1, Section 23.1.10 Field 99.103: BDB Format Owner (BFO) 

This mandatory element shall be used to denote the vendor, standards body, working group, or 

industry consortium that has defined the format of the biometric data (in the BDB). In a CBEFF 

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 

CBEFF Client (see Clause 6.1 of the CBEFF standard). This BDB format definition may be 

published (public) or unpublished (nonpublic). 

A CBEFF requirement is that format owners register with IBIA for an assigned identifier of the 

format owner. The number is guaranteed to be unique. Refer to the CBEFF standard, Clause 6, 

“CBEFF Patrons and Clients,” for registration information. 

Complex element <ansi-nist:CBEFFFormatOwnerIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the four hex digits assigned by IBIA represented by a 

string of four ASCII characters. 
Part 2 ANSI/NIST-ITL 2-2008

154

<ansi-nist:CBEFFFormatOwnerIdentification> 

<nc:IdentificationID>FFF0</nc:IdentificationID> 

</ansi-nist:CBEFFFormatOwnerIdentification> 

223.1.5.5 Element <ansi-nist:CBEFFFormatCategoryIdentification> 

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 

represent the specific BDB Format as specified by the format owner. This may be a nonstandard, 

unpublished data format or a data format that has been standardized by an industry group, 

consortium, or standards body. The registration of the Format Type value is recommended but 

not required. Refer to the CBEFF standard, Clause 6, “CBEFF Patrons and Clients,” for 

registration information. 

Complex element <ansi-nist:CBEFFFormatCategoryIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the four hex digits assigned by the format owner 

represented by a string of four ASCII characters. 

<ansi-nist:CBEFFFormatCategoryIdentification> 

<nc:IdentificationID>000A</nc:IdentificationID> 

</ansi-nist:CBEFFFormatCategoryIdentification> 

223.1.5.6 Element <ansi-nist:CBEFFVersionIdentification> 

Cross-reference: Part 1, Section 23.1.7 Field 99.100: CBEFF Header Version (HDV) 

This mandatory element shall be used to identify the version of CBEFF specification to which this 

record conforms. The format is two characters for major version number followed by two 

characters for minor version. The current version of CBEFF is INCITS 398-2005 represented by 

the string ‘0101’ (major version ‘01’ and minor version ‘01’). 

Complex element <ansi-nist:CBEFFVersionIdentification> shall have the simple element 

<nc:IdentificationID>, which will contain the version data. 

<ansi-nist:CBEFFVersionIdentification> 

<nc:IdentificationID>0101</nc:IdentificationID>

</ansi-nist:CBEFFVersionIdentification> 

223.1.5.7 Element <ansi-nist:CBEFFCategoryCode> 

Cross-reference: Part 1, Section 23.1.8 Field 99.101: Biometric Type (BTY) 

This mandatory element shall be used to identify the type of biometric technology. This 

specification adopts the values presented in CBEFF with the addition of two leading zeros for 

future expansion. Table 240 lists the current biometric type codes. (Table 240 is the same as 

Table 39 in Part 1.) 

<ansi-nist:CBEFFCategoryCode>00000200 

</ansi-nist:CBEFFCategoryCode> 
Part 2 ANSI/NIST-ITL 2-2008

155

223.2 End of Type-99 CBEFF Data Record 

The Type-99 logical record shall end with the XML tag 

</itl:PackageCBEFFBiometricDataRecord>. 

223.3 Additional Type-99 CBEFF Data Records 

Additional Type-99 records may be included in the exchange package. For each additional 

CBEFF record, a complete Type-99 logical record is required. 

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’ 

224 Another individual 

If fingerprint or other biometric data for another individual is to be recorded or transmitted, a new 

information exchange package shall be generated for that individual using the same format as 

described previously. 
Part 2 – Annex A ANSI/NIST-ITL 2-2008

156

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

(normative) 

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 
Part 2 – Annex B 

157

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://biometrics.nist.gov/standard/2-2008" 

11 xmlns:itl="http://biometrics.nist.gov/standard/2-2008" 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:import schemaLocation="niem/ansi-nist/2.0/ansi-nist_itl_constraint.xsd" namespace="http://niem.gov/niem/an23 <xsd:import schemaLocation="niem/structures/2.0/structures.xsd" namespace="http://niem.gov/niem/structures/2.0

24 <xsd:import schemaLocation="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:NISTBiometricInformationExchangeP30 <!-- Record type 01 --> 

31 <xsd:element name="PackageInformationRecord" type="itl:PackageInformationRecordType"/> 32 <!-- Record type 02 --> 

33 <xsd:element name="PackageDescriptiveTextRecord" type="itl:PackageDescriptiveTextRecordType"/> 
Part 2 – Annex B 

158

1 <!-- ABSTRACT BASE FOR ALL RECORD TYPES 03 through 99 --> 2 <xsd:element name="PackageDataRecord" abstract="true"/> 3 <!-- Record type 09 (a PackageMinutiaeRecordType) --> 

4 <xsd:element name="PackageMinutiaeRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageMin

5 <!-- UNIQUE NAMES FOR RECORD TYPES 03, 04, 05, 06, 07, 08, 10, 13, 14, 15, 16, 17, 99 (all PackageImage6 <!-- Type 03 --> 

7 <xsd:element name="PackageLowResolutionGrayscaleImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImageRe8 <!-- Type 04 --> 9 <xsd:element name="PackageHighResolutionGrayscaleImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImageRe

10 <!-- Type 05 --> 

11 <xsd:element name="PackageLowResolutionBinaryImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:Packa12 <!-- Type 06 --> 13 <xsd:element name="PackageHighResolutionBinaryImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:Packa14 <!-- Type 07 --> 15 <xsd:element name="PackageUserDefinedImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImage16 <!-- Type 08 --> 17 <xsd:element name="PackageSignatureImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImageRe18 <!-- Type 10 --> 19 <xsd:element name="PackageFacialAndSMTImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageIma20 <!-- Type 13 --> 

21 <xsd:element name="PackageLatentImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:Package22 <!-- Type 14 --> 

23 <xsd:element name="PackageFingerprintImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImageR24 <!-- Type 15 --> 25 <xsd:element name="PackagePalmprintImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageImageRe26 <!-- Type 16 --> 27 <xsd:element name="PackageUserDefinedTestingImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:Packag28 <!-- Type 17 --> 29 <xsd:element name="PackageIrisImageRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageIma30 <!-- Type 99 --> 31 <xsd:element name="PackageCBEFFBiometricDataRecord" substitutionGroup="itl:PackageDataRecord" type="itl:PackageIma32 33 <!-- =============================== --> 34 <!-- PACKAGE TYPE DEFINITION --> 35 <!-- =============================== --> 

36 <xsd:complexType name="NISTBiometricInformationExchangePackageType"> 37 <xsd:complexContent> 38 <xsd:extension base="s:ComplexObjectType"> 
Part 2 – Annex B 

159

1 <xsd:sequence> 

2 <xsd:element ref="itl:PackageInformationRecord"/> 3 <xsd:element ref="itl:PackageDescriptiveTextRecord" maxOccurs="unbounded"/> 

4 <xsd:element ref="itl:PackageDataRecord" minOccurs="0" maxOccurs="unbound5 </xsd:sequence> 6 </xsd:extension> 7 </xsd:complexContent> 8 </xsd:complexType> 9 

10 <!-- =============================== --> 11 <!-- RECORD TYPE DEFINITIONS --> 12 <!-- =============================== --> 13 14 <!-- Record Type 01 --> 

15 <xsd:complexType name="PackageInformationRecordType"> 16 <xsd:complexContent> 17 <xsd:extension base="s:ComplexObjectType"> 18 <xsd:sequence> 19 <xsd:element ref="ansi-nist:RecordCategoryCode"/> 20 <xsd:element ref="ansi-nist:Transaction"/> 21 </xsd:sequence> 22 </xsd:extension> 23 </xsd:complexContent> 24 </xsd:complexType> 25 26 <!-- Record Type Base for 02 through 99 --> 27 <xsd:complexType name="PackageDataRecordType"> 28 <xsd:complexContent> 29 <xsd:extension base="s:ComplexObjectType"> 30 <xsd:sequence> 31 <xsd:element ref="ansi-nist:RecordCategoryCode"/> 

32 <!-- ====================================================== fieldID="XX.002" fieldMne33 <xsd:element ref="ansi-nist:ImageReferenceIdentification"/> 34 <!-- =================================================== fieldID="XX.200-998" fieldMne

35 <xsd:element ref="itl:UserDefinedFields" minOccurs="0"/> 36 </xsd:sequence> 37 </xsd:extension> 
Part 2 – Annex B 

160

1 </xsd:complexContent> 2 </xsd:complexType> 3 4 <!-- Record Type 02 --> 

5 <xsd:complexType name="PackageDescriptiveTextRecordType"> 6 <xsd:complexContent> 

7 <xsd:extension base="itl:PackageDataRecordType"> 8 <xsd:sequence> 

9 <xsd:element ref="itl:UserDefinedDescriptiveText"/> 

10 </xsd:sequence> 11 </xsd:extension> 12 </xsd:complexContent> 13 </xsd:complexType> 14 

15 <!-- Image Records: 03, 04, 05, 06, 07, 08, 10, 13, 14, 15, 16, 17, 99 --> 

16 <xsd:complexType name="PackageImageRecordType"> 17 <xsd:complexContent> 18 <xsd:extension base="itl:PackageDataRecordType"> 19 <xsd:sequence> 20 <xsd:element ref="ansi-nist:RecordImage"/> 21 </xsd:sequence> 22 </xsd:extension> 23 </xsd:complexContent> 24 </xsd:complexType> 25 26 <!-- Minutiae Record: 09 --> 

27 <xsd:complexType name="PackageMinutiaeRecordType"> 28 <xsd:complexContent> 29 <xsd:extension base="itl:PackageDataRecordType"> 30 <xsd:sequence> 31 <xsd:element ref="ansi-nist:MinutiaeImpressionCaptureCategory"/> 32 <xsd:element ref="ansi-nist:MinutiaeFormatNISTStandardIndicator"/> 33 <xsd:element ref="itl:RecordMinutiae"/> 34 </xsd:sequence> 35 </xsd:extension> 36 </xsd:complexContent> 37 </xsd:complexType> 
Part 2 – Annex B 

161

1 2 <!-- =============================== --> 3 <!-- IMAGE RECORDS SUBSTITUTION GROUP --> 4 <!-- =============================== --> 

5 <xsd:element name="FingerprintImage" substitutionGroup="ansi-nist:RecordImage" type="itl:FingerprintImageTyp6 <xsd:element name="PalmprintImage" substitutionGroup="ansi-nist:RecordImage" type="itl:PalmprintImageType"

7 <xsd:element name="IrisImage" substitutionGroup="ansi-nist:RecordImage" type="itl:IrisImageType"/> 

8 <xsd:element name="TestImage" substitutionGroup="ansi-nist:RecordImage" type="ansi-nist:NISTImageType"/> 9 <xsd:element name="FaceImage" substitutionGroup="ansi-nist:RecordImage" type="itl:FaceImageType"/> 

10 <!-- Here is a sample substitute for the Type07 user defined image. Users should create their own in a different do11 <xsd:element name="ExampleRecordImage" substitutionGroup="ansi-nist:RecordImage" type="xsd:anyType"/> 12 <!-- =============================== --> 13 <!-- MINUTIAE RECORD SUBSTITUTION GROUP --> 14 <!-- =============================== --> 15 <xsd:element name="RecordMinutiae" abstract="true"/> 16 <xsd:element name="Minutiae" substitutionGroup="itl:RecordMinutiae" type="itl:MinutiaeType"/> 17 18 <!-- =============================== --> 19 <!-- ITL ELEMENTS --> 20 <!-- =============================== --> 21 <xsd:element name="FingerprintImageSegmentPositionSquare" type="itl:FingerprintImageSegmentPositionSquare

22 <xsd:element name="FingerprintImageSegmentPositionPolygon" type="itl:FingerprintImageSegmentPositionPolyg

23 <xsd:element name="FingerprintImageFingerMissing" type="itl:FingerprintImageFingerMissingType"/> 24 <xsd:element name="FingerprintImageQuality" type="ansi-nist:FingerprintImageQualityType"/> 

25 <xsd:element name="PalmprintImageQuality" type="itl:PalmprintImageQualityType"/> 

26 <xsd:element name="PositionPolygonVertexQuantity" type="xsd:nonNegativeInteger"/> 27 <xsd:element name="PositionPolygonVertex" type="itl:PositionPolygonVertexType"/> 

28 <xsd:element name="FingerMissingCode" type="itl:AMPCodeType"/> 29 <xsd:element name="IrisDiameterPixelQuantity" type="xsd:nonNegativeInteger"/> 

30 <xsd:element name="FaceImageAcquisitionSource" type="itl:FaceImageAcquisitionSourceType"/> 31 <xsd:element name="CaptureSourceDescriptionText" type="xsd:string"/> 32 

33 <!-- ITL USER DEFINED DESCRIPTIVE TEXT AND FIELDS --> 

34 <xsd:element name="UserDefinedDescriptiveText" type="itl:UserDefinedDescriptiveTextType"/> 35 <!-- Users may define substitutes for the following abstract elements . --> 36 <xsd:element name="DomainDefinedDescriptiveText" abstract="true"/> 

37 <xsd:element name="OtherDescriptiveText" abstract="true"/> 
Part 2 – Annex B 

162

1 <xsd:element name="UserDefinedFields" abstract="true"/> 

2 <!-- Here are sample substitutes for user-defined abstract elements. Users should create their own in a different d

3 <xsd:element name="ExampleDomainDefinedDescriptiveText" substitutionGroup="itl:DomainDefinedDescriptiveText" type="xs

4 <xsd:element name="ExampleOtherDescriptiveText" substitutionGroup="itl:OtherDescriptiveText" type="xsd:anyT5 <xsd:element name="ExampleUserDefinedFields" substitutionGroup="itl:UserDefinedFields" type="xsd:anyType"/6 7 <!-- =============================== --> 8 <!-- CORRECTED NIEM 2.0 ELEMENTS --> 9 <!-- =============================== --> 

10 <xsd:element name="MinutiaeNISTStandard" type="itl:NISTStandardMinutiaeType"/> 

11 <xsd:element name="MinutiaDetail" type="itl:MinutiaType"/> 

12 <xsd:element name="MinutiaeFingerPatternDetail" type="itl:MinutiaeFingerPatternType"/> 13 <xsd:element name="FingerPatternCodeSourceCode" type="itl:PCSCodeType"/> 14 15 <!-- =============================== --> 16 <!-- ITL ELEMENT TYPES --> 17 <!-- =============================== --> 18 19 <xsd:complexType name="FingerprintImageType"> 20 <xsd:complexContent> 21 <xsd:extension base="ansi-nist:NISTImageType"> 22 <xsd:sequence> 

23 <!-- =====================================================fieldID="XX.003" fieldMnem24 <xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory"/> 25 <!-- =====================================================fieldID="XX.013" fieldMnem26 <xsd:element ref="ansi-nist:FingerPositionCode" maxOccurs="unbounded"/> 27 <!-- =====================================================fieldID="XX.014" fieldMnem28 <!-- =====================================================fieldID="XX.015" fieldMnem29 <xsd:element ref="ansi-nist:FingerprintImageMajorCasePrint" minOccurs="0"/> 30 <!-- =====================================================fieldID="14.018" fieldMnemo31 <xsd:element ref="itl:FingerprintImageFingerMissing" minOccurs="0" maxOccurs=32 <!-- =====================================================fieldID="14.021" fieldMnemo33 <xsd:element ref="itl:FingerprintImageSegmentPositionSquare" minOccurs="0" maxOccurs34 <!-- =====================================================fieldID="14.022" fieldMnemo35 <xsd:element ref="ansi-nist:FingerprintImageNISTQuality" minOccurs="0" maxOc36 <!-- =====================================================fieldID="14.023" fieldMnemo37 <xsd:element ref="ansi-nist:FingerprintImageSegmentationQuality" minOccurs="0" maxOcc38 <!-- =====================================================fieldID="13.024" fieldMnemo39 <!-- =====================================================fieldID="14.024" fieldMnemo
Part 2 – Annex B 

163

1 <xsd:element ref="itl:FingerprintImageQuality" minOccurs="0" maxOccurs="unbou

2 <!-- =====================================================fieldID="14.025" fieldMnemo3 <xsd:element ref="itl:FingerprintImageSegmentPositionPolygon" minOccurs="0" m4 </xsd:sequence> 5 </xsd:extension> 6 </xsd:complexContent> 7 </xsd:complexType> 8 9 <xsd:complexType name="PalmprintImageType"> 

10 <xsd:complexContent> 11 <xsd:extension base="ansi-nist:NISTImageType"> 12 <xsd:sequence> 

13 <!-- =====================================================fieldID="XX.003" fieldMnem14 <xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory"/> 15 <!-- =====================================================fieldID="13.013" fieldMnemo16 <!-- =====================================================fieldID="15.013" fieldMnemo17 <xsd:element ref="ansi-nist:PalmPosition" maxOccurs="unbounded"/> 18 <!-- =====================================================fieldID="13.024" fieldMnemo19 <!-- =====================================================fieldID="15.024" fieldMnemo

20 <xsd:element ref="itl:PalmprintImageQuality" minOccurs="0" maxOccurs="unboun21 </xsd:sequence> 22 </xsd:extension> 23 </xsd:complexContent> 24 </xsd:complexType> 25 26 <xsd:complexType name="IrisImageType"> 27 <xsd:complexContent> 28 <xsd:extension base="ansi-nist:NISTImageType"> 29 <xsd:sequence> 

30 <!-- =====================================================fieldID="17.003" fieldMnemo31 <xsd:element ref="ansi-nist:IrisEyePosition"/> 32 <!-- =====================================================fieldID="17.014" fieldMnemo

33 <xsd:element ref="ansi-nist:IrisEyeRotationAngleMeasure" minOccurs="0"/> 

34 <!-- =====================================================fieldID="17.015" fieldMnemo

35 <xsd:element ref="ansi-nist:IrisEyeRotationUncertaintyValueText" minOccurs="0"/

36 <!-- ===========See complex in ansi-nist file ==========================================

37 <xsd:element ref="ansi-nist:IrisImageCapture" minOccurs="0" maxOccurs="unbou38 

39 <!-- =====================================================fieldID="17.020" fieldMnemo
Part 2 – Annex B 

164

1 <xsd:element ref="ansi-nist:IrisEyeColorAttributeCode" minOccurs="0"/> 

2 <!-- =====================================================fieldID="17.025" fieldMnemo3 <xsd:element ref="ansi-nist:IrisImageAcquisitionLightingSpectrumValue" minOccu4 <!-- =====================================================fieldID="17.026" fieldMnemo5 <xsd:element ref="itl:IrisDiameterPixelQuantity" minOccurs="0"/> 6 </xsd:sequence> 7 </xsd:extension> 8 </xsd:complexContent> 9 </xsd:complexType> 

10 11 <xsd:complexType name="FaceImageType"> 12 <xsd:complexContent> 13 <xsd:extension base="ansi-nist:FaceImageType"> 14 <xsd:sequence> 

15 <!-- =====================================================fieldID="10.023" fieldMnemo16 <xsd:element ref="itl:FaceImageAcquisitionSource" minOccurs="0"/> 17 </xsd:sequence> 18 </xsd:extension> 19 </xsd:complexContent> 20 </xsd:complexType> 21 22 <xsd:complexType name="UserDefinedDescriptiveTextType"> 23 <xsd:complexContent> 24 <xsd:extension base="s:ComplexObjectType"> 25 <xsd:sequence> 26 <xsd:element ref="itl:DomainDefinedDescriptiveText"/> 

27 <xsd:element ref="itl:OtherDescriptiveText" minOccurs="0"/> 28 </xsd:sequence> 29 </xsd:extension> 30 </xsd:complexContent> 31 </xsd:complexType> 32 

33 <xsd:complexType name="FingerprintImageSegmentPositionSquareType"> 34 <xsd:complexContent> 35 <xsd:extension base="s:ComplexObjectType"> 36 <xsd:sequence> 37 <xsd:element ref="ansi-nist:FingerPositionCode"/> 
Part 2 – Annex B 

165

1 <xsd:element ref="ansi-nist:SegmentBottomVerticalCoordinateValue"/> 

2 <xsd:element ref="ansi-nist:SegmentLeftHorizontalCoordinateValue"/> 

3 <xsd:element ref="ansi-nist:SegmentRightHorizontalCoordinateValue"/> 

4 <xsd:element ref="ansi-nist:SegmentTopVerticalCoordinateValue"/> 5 </xsd:sequence> 6 </xsd:extension> 7 </xsd:complexContent> 8 </xsd:complexType> 9 

10 <xsd:complexType name="FingerprintImageSegmentPositionPolygonType"> 11 <xsd:complexContent> 12 <xsd:extension base="ansi-nist:FingerprintType"> 13 <xsd:sequence> 14 <xsd:element ref="itl:PositionPolygonVertexQuantity"/> 15 <xsd:element ref="itl:PositionPolygonVertex" minOccurs="3" maxOccurs="99"/> 16 </xsd:sequence> 17 </xsd:extension> 18 </xsd:complexContent> 19 </xsd:complexType> 20 

21 <xsd:complexType name="PositionPolygonVertexType"> 22 <xsd:complexContent> 23 <xsd:extension base="s:ComplexObjectType"> 24 <xsd:sequence> 25 <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue"/> 26 <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue"/> 27 </xsd:sequence> 28 </xsd:extension> 29 </xsd:complexContent> 30 </xsd:complexType> 31 32 <xsd:complexType name="FingerprintImageFingerMissingType"> 33 <xsd:complexContent> 34 <xsd:extension base="s:ComplexObjectType"> 35 <xsd:sequence> 36 <xsd:element ref="ansi-nist:FingerPositionCode"/> 37 <xsd:element ref="itl:FingerMissingCode"/> 
Part 2 – Annex B 

166

1 </xsd:sequence> 2 </xsd:extension> 3 </xsd:complexContent> 4 </xsd:complexType> 5 6 <xsd:complexType name="AMPCodeType"> 7 <xsd:annotation> 8 <xsd:appinfo> 

9 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 

10 </xsd:appinfo> 11 </xsd:annotation> 12 <xsd:simpleContent> 13 <xsd:extension base="xsd:token"> 14 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 15 </xsd:extension> 16 </xsd:simpleContent> 17 </xsd:complexType> 18 19 <xsd:complexType name="PalmprintImageQualityType"> 20 <xsd:complexContent> 

21 <xsd:extension base="ansi-nist:FingerprintPalmImagePositionType"> 22 <xsd:sequence> 

23 <xsd:element ref="ansi-nist:QualityAlgorithmProductIdentification"/> 

24 <xsd:element ref="ansi-nist:QualityAlgorithmVendorIdentification"/> 25 <xsd:element ref="ansi-nist:QualityValue"/> 26 </xsd:sequence> 27 </xsd:extension> 28 </xsd:complexContent> 29 </xsd:complexType> 30 

31 <xsd:complexType name="FaceImageAcquisitionSourceType"> 32 <xsd:complexContent> 33 <xsd:extension base="s:ComplexObjectType"> 34 <xsd:sequence> 35 <xsd:element ref="ansi-nist:CaptureSourceCode"/> 

36 <xsd:element ref="itl:CaptureSourceDescriptionText" minOccurs="0"/> 37 </xsd:sequence> 
Part 2 – Annex B 

167

1 </xsd:extension> 2 </xsd:complexContent> 3 </xsd:complexType> 4 5 6 <!-- =============================== --> 7 <!-- CORRECTIONS TO NIEM 2.0 ELEMENTS --> 8 <!-- =============================== --> 9 

10 <xsd:complexType name="MinutiaeType"> 11 <xsd:complexContent> 12 <xsd:extension base="s:ComplexObjectType"> 13 <xsd:sequence> 14 <xsd:element ref="itl:MinutiaeNISTStandard"/> 

15 <!-- ======================================================== fieldID="9.008" fieldMne

16 <xsd:element ref="ansi-nist:MinutiaeFingerCorePosition" minOccurs="0" maxOccu

17 <!-- ======================================================== fieldID="9.009" fieldMne

18 <xsd:element ref="ansi-nist:MinutiaeFingerDeltaPosition" minOccurs="0" maxOcc

19 <!-- ======================================================== fieldID="9.007" fieldMne

20 <xsd:element ref="itl:MinutiaeFingerPatternDetail" minOccurs="0" maxOccurs="un

21 <!-- ======================================================== fieldID="9.006" fieldMne22 <xsd:element ref="ansi-nist:MinutiaeFingerPosition" minOccurs="0" maxOccurs="

23 <xsd:element ref="ansi-nist:MinutiaePalmPosition" minOccurs="0" maxOccurs="u24 </xsd:sequence> 25 </xsd:extension> 26 </xsd:complexContent> 27 </xsd:complexType> 28 

29 <xsd:complexType name="NISTStandardMinutiaeType"> 30 <xsd:complexContent> 31 <xsd:extension base="s:ComplexObjectType"> 32 <xsd:sequence> 

33 <!-- ======================================================== fieldID="9.012" fieldMne34 <xsd:element ref="itl:MinutiaDetail" maxOccurs="unbounded"/> 35 <!-- ======================================================== fieldID="9.010" fieldMne36 <xsd:element ref="ansi-nist:MinutiaeQuantity"/> 37 <!-- ======================================================== fieldID="9.005" fieldMne38 <xsd:element ref="ansi-nist:MinutiaeReadingSystem" minOccurs="0"/> 
Part 2 – Annex B 

168

1 <!-- ======================================================== fieldID="9.011" fieldMne2 <xsd:element ref="ansi-nist:MinutiaeRidgeCountIndicator"/> 3 </xsd:sequence> 4 </xsd:extension> 5 </xsd:complexContent> 6 </xsd:complexType> 7 8 <xsd:complexType name="MinutiaType"> 9 <xsd:complexContent> 

10 <xsd:extension base="s:ComplexObjectType"> 11 <xsd:sequence> 

12 <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue"/> 13 <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue"/> 

14 <xsd:element ref="ansi-nist:MinutiaIdentification"/> 15 <xsd:element ref="ansi-nist:PositionThetaAngleMeasure"/> 

16 <!-- ==Move 3 elements from NISTStandardMinutiaeType==== --> 17 <xsd:element ref="ansi-nist:MinutiaQualityValue" minOccurs="0"/> 18 <xsd:element ref="ansi-nist:MinutiaCategory" minOccurs="0"/> 

19 <xsd:element ref="ansi-nist:MinutiaRidgeCount" minOccurs="0" maxOccurs="unb20 </xsd:sequence> 21 </xsd:extension> 22 </xsd:complexContent> 23 </xsd:complexType> 24 25 <xsd:complexType name="MinutiaeFingerPatternType"> 26 <xsd:annotation> 27 <xsd:appinfo> 

28 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 29 </xsd:appinfo> 30 </xsd:annotation> 31 <xsd:complexContent> 32 <xsd:extension base="s:ComplexObjectType"> 33 <xsd:sequence> 34 <xsd:element ref="itl:FingerPatternCodeSourceCode"/> 35 <xsd:element ref="ansi-nist:FingerPattern"/> 36 </xsd:sequence> 37 </xsd:extension> 
Part 2 – Annex B 

169

1 </xsd:complexContent> 2 </xsd:complexType> 3 

4 <xsd:simpleType name="PCSCodeSimpleType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:restriction base="xsd:token"> 11 <xsd:enumeration value="T"> 12 <xsd:annotation> 13 <xsd:documentation>Pattern codes from Table 16</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="U"> 17 <xsd:annotation> 

18 <xsd:documentation>User-defined pattern codes</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 </xsd:restriction> 22 </xsd:simpleType> 23 <xsd:complexType name="PCSCodeType"> 24 <xsd:annotation> 25 <xsd:appinfo> 

26 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 27 </xsd:appinfo> 28 </xsd:annotation> 29 <xsd:simpleContent> 30 <xsd:extension base="itl:PCSCodeSimpleType"> 31 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 32 </xsd:extension> 33 </xsd:simpleContent> 34 </xsd:complexType> 35 36 </xsd:schema> 
Part 2 – Annex C ANSI/NIST-ITL 2-2008

170 

Annex C Base-64 encoding scheme 

(normative) 

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 

the encoded data are consistently only about 33 percent larger than the unencoded data. This 

encoding is virtually identical to the one used in Privacy Enhanced Mail (PEM) applications, as 

defined in RFC 1421. The base-64 encoding is adapted from RFC 1421, with one change: base64 eliminates the "*" mechanism for embedded clear text. 

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.) 

NOTE: This subset has the important property that it is represented identically in all versions of 

ISO 646, including US ASCII and all characters in the subset are also represented identically in 

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 

properties, and thus do not fulfill the portability requirements a binary transport encoding for mail 

must meet. 

The encoding process represents 24-bit groups of input bits as output strings of 4 encoded 

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 

into a single digit in the base-64 alphabet. When encoding a bit stream via the base-64 encoding, 

the bit stream must be presumed to be ordered with the most significant bit first. That is, the first 

bit in the stream will be the high-order bit in the first byte, and the eighth bit will be the low-order 

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 

referenced by the index is placed in the output string. These characters, identified in Table C1, 

below, are selected so as to be universally representable, and the set excludes characters with 

particular significance to SMTP (e.g., ".", CR, LF) and to the encapsulation boundaries defined in 

this document (e.g., "-"). 

The output stream (encoded bytes) must be represented in lines of no more than 76 characters 

each. All line breaks or other characters not found in Table C1 must be ignored by decoding 

software. In base-64 data, characters other than those in Table C1, line breaks, and other white 

space probably indicate a transmission error, about which a warning message or even a 

message rejection might be appropriate under some circumstances. 
Part 2 – Annex C ANSI/NIST-ITL 2-2008

171

Table C1 – Base-64 alphabet 

 Value Value Value Value 

Encoding Encoding Encoding Encoding 

 0 A 17 R 34 I 51 z 

 1 B 18 S 35 j 52 0 

 2 C 19 T 36 k 53 1 

 3 D 20 U 37 l 54 2 

 4 E 21 V 38 m 55 3 

 5 F 22 W 39 n 56 4 

 6 G 23 X 40 o 57 5 

 7 H 24 Y 41 p 58 6 

 8 I 25 Z 42 q 59 7 

 9 J 26 a 43 r 60 8 

 10 K 27 b 44 s 61 9 

 11 L 28 c 45 t 62 + 

 12 M 29 d 46 u 63 / 

 13 N 30 e 47 v 

 14 O 31 f 48 w (pad) = 

 15 P 32 g 49 x 

 16 Q 33 h 50 y 

Special processing is performed if fewer than 24 bits are available at the end of the data being 

encoded. A full encoding quantum is always completed at the end of a body. When fewer than 24 

input bits are available in an input group, zero bits are added (on the right) to form an integral 

number of 6-bit groups. Padding at the end of the data is performed using the '=' character. Since 

all base-64 input is an integral number of octets, only the following cases can arise: (1) the final 

quantum of encoding input is an integral multiple of 24 bits; here, the final unit of encoded output 

will be an integral multiple of 4 characters with no "=" padding, (2) the final quantum of encoding 

input is exactly 8 bits; here, the final unit of encoded output will be two characters followed by two 

"=" padding characters, or (3) the final quantum of encoding input is exactly 16 bits; here, the final 

unit of encoded output will be three characters followed by one "=" padding character. 

Because it is used only for padding at the end of the data, the occurrence of any '=' characters 

may be taken as evidence that the end of the data has been reached (without truncation in 

transit). No such assurance is possible, however, when the number of octets transmitted was a 

multiple of three. 

Any characters outside of the base-64 alphabet are to be ignored in base-64-encoded data. The 

same applies to any illegal sequence of characters in the base-64 encoding, such as "=====". 

Care must be taken to use the proper octets for line breaks if base-64 encoding is applied directly 

to text material that has not been converted to canonical form. In particular, text line breaks must 

be converted into CRLF sequences prior to base-64 encoding. The important thing to note is that 

this may be done directly by the encoder rather than in a prior cannibalization step in some 

implementations. 

NOTE: There is no need to worry about quoting apparent encapsulation boundaries within base64-encoded parts of multipart because no hyphen characters are used in the base-64 encoding. 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

172 

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 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

173

Why a file interchange format 

JPEG File Interchange Format (JFIF) is a minimal file format, which enables JPEG bitstreams to be 

exchanged between a wide variety of platforms and applications. This minimal format does not include 

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. 

JPEG file interchange format 

• Uses JPEG compression 

• Uses JPBG interchange format compressed image representation 

• PC or Mac or UNIX workstation compatible 

• Standard color space: one or three components. For three components YCbCr (CCIR 601-256 levels) 

• APP0 marker used to specify Units, X pixel density, Y pixel density, thumbnail 

• APP0 marker also used to specify JFIF extensions 

• APP0 mater also used to specify application-specific information 

JPEG compression 

Although any JPEG process is supported by the syntax of the JFIF it is strongly recommended that the 

JPEG baseline process be used for the purposes of file interchange. This ensures maximum compatibility 

with all applications supporting JPEG. JFIF conforms to the JPEG Draft International Standard (ISO DIS 

10918-1). 

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 

JPEG interchange format requires (as does JFIF) all table specifications used in the encoding process be 

coded in the bitstream prior to their use. 

Compatible across platforms 

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. 

Standard color space 

The color space to be used is YCbCr as defined by CCIR 601(256 levels). The RGB components 

calculated by linear conversion from YCbCr shall not be gamma corrected (gamma = 1.0). If only one 

component is used, that component shall be Y. 

APP0 marker is used to identify JPEG FIF 

• The APP0 marker is used to identify a JPEG FIF file. 

• The JPEG FIF APP0 marker is mandatory right after the SOI marker. 

• The JFIF APP0 marker is identified by a zero terminated string: “JFIF”. 

• The APP0 can be used for any other purpose by the application provided it can be distinguished from 

the JFIF APP0. 

• The JFIF APP0 marker provides information which is missing from the JPEG stream: version number, 

X and Y pixel density (dots per inch or dots per cm), pixel aspect ratio (derived from X and Y pixel 

density), thumbnail. 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

174

APP0 marker used to specify JFIF extensions 

Additional APP0 marker segment(s) can optionally be used to specify JFIF extensions. If used, these 

segments must immediately follow the JFIF APP0 marker. Decoders should skip any unsupported JFIF 

extension segments and continue decoding. 

The JFIF extension APP0 marker is identified by a zero terminated string: "JFXX". The JFIF extension 

APP0 marker segment contains a 1-byte code, which identifies the extension. This version, version 1.02, 

has only one extension defined: an extension for defining thumbnails stored in formats other than 24-bit 

RGB. 

APP0 marker used for application-specific information 

Additional APP0 marker segments can be used to hold application-specific information which does not 

affect the decodability or displayability of the JFIF file. Application-specific APP0 marker segments must 

appear after the JFIF APP0 and any JFXX APP0 segments. Decoders should skip any unrecognized 

application-specific APP0 segments. 

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. 

Generic strings such as dog, cat, tree, etc. should not be used. 

Conversion to and from RGB 

Y, Cb, and Cr are converted from R, G, and B as defined in CCIR Recommendation 601 but are 

normalized so as to occupy the full 256 levels of an 8-bit binary encoding. More precisely: 

Y = 256 * E'y 

Cb = 256 * [ E'Cb] + 128 

Cr= 256 * [ E'Cr] + 128 

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 

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. 

RGB to YCbCr conversion 

YCbCr (256 levels) can be computed directly from 8-bit RGB as follows: 

Y = 0.299 R + 0.587G + 0.114B 

Cb = -0.1687 R - 0.3313 G + 0.5 B + 128 

Cr = 0.5R - 0.4177 G - 0.0813 B + 128 

NOTE - Not all image file formats store image samples in the order R0, G0, B0, ... Rn, Gn, Bn. Be sure to 

verify the sample order before converting an RGB file to JFIF 

YCbCr to RGB conversion 

RGB can be computed directly from YCbCr (256 levels) as follows: 

R = Y + 1.402 (Cr - 128) 

G = Y-0.34414 (Cb - 128) - 0.71414 (Cr - 128) 

B = Y + 1.772 (Cb - 128) 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

175

Image orientation 

In JFIF files, the image orientation is always top-down. This means that the first image samples encoded 

in a JFIF file are located in the upper left hand corner of the image and encoding proceeds from left to 

right and top to bottom. Top-down orientation is used for both the full resolution image and the thumbnaiI 

image. 

The process of converting an image file having bottom-up orientation to JFIF must include inverting the 

order of all image lines before JPEG encoding. 

Spatial relationship of components 

Specification of the spatial positioning of pixel samples within components relative to the samples of other 

components is necessary for proper image post processing and accurate image presentation. In JFIF 

files, the position of the pixels in subsampled components are defined with respect to the highest 

resolution component. Since components must be sampled orthogonally (along rows and columns), the 

spatial position of the samples in a given subsampled component may be determined by specifying the 

horizontal and vertical offsets of the first sample, i.e. the sample in the upper left corner, with respect to 

the highest resolution component. 

The horizontal and vertical offsets of the first sample in a subsampled component, Xoffseti [0,0] and 

Yoffseti [0,0], are defined to be: 

Xoffseti

[0,0] = ((Nsamplesref / Nsamplesj) / 2) - 0.5 

Yoffseti

[0,0] = ((Nlinesref / Nlinesi) / 2) - 0.5 

where 

Nsamplesref is the number of samples per line in the largest component; 

Nsamplesi

 is the number of samples per line in the ith component; 

Nlinesref is the number of lines in the largest component; 

Nlinesi

 is the number of lines in the ith component. 

Proper subsampling of components incorporates an anti-aliasing filter which reduces the spectral 

bandwidth of the full resolution components. Subsampling can easily be accomplished using a 

symmetrical digital filter with an even number of taps (coefficients). A commonly used filter for 2:1 

subsampling utilizes two taps (1/2,1/2). 

As an example, consider a 3 component image which is comprised of components having the following 

dimensions: 

Component 1: 256 samples, 288 lines 

Component 2: 128 samples, 144 lines 

Component 3: 64 samples, 96 lines 

In a JFIF file, centers of the samples are positioned as illustrated below: 

x x x x 

 

x x  x x 

x x x x 

 

x x x x 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

176

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 

aspect ratio 

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]

• 

• 

• 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

177

X 'FF', SOFn, length,. frame parameters

Number of components Nf = 1 or 3 

1st component C1 = 1 = Y component 

2nd component C2 = 2 = Cb component 

3rd component C3 = 3 = Cr component 

• 

• 

• 

X 'FF', EOI 

JFIF Extension: APP0 marker segment 

Immediately following the JFIF APP0 marker segment may be a JFIF extension APP0 marker. This JFIF 

extension APP0 marker segment may only be present for JFIF versions 1.02 and above. The syntax of 

the JFIF extension APP0 marker segment is: 

X 'FF', APP0,. Length, identifier, extension code, extension data

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 ‘461

, X '58', X '58', X ‘00’

This zero terminated string ("JFXX") 

uniquely identifies this APP0 marker. This 

string shall have zero parity (bit 7 = 0). 

extension_code (1 byte) = Code which identifies the extension. In 

this version, the following extensions are 

defined: 

= X '10' Thumbnail coded using JPEG 

= X '11’ Thumbnail stored using 1 byte/pixel 

= X '13’ Thumbnail stored using 3 bytes/pixel 

extension_data (variable) = The specification of the remainder of the 

JFIF extension APP0 marker segment 

varies with the extension. See below for a 

specification of extension_data for each extension. 

JFIF Extension: Thumbnail coded using JPEG

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 

be included in the JFIF extension APP0 marker length field. 

The syntax of the extension_data field conforms to the syntax for interchange format defined in Annex B 

of ISO DIS 10917-1. However, no "JFIF" or "JFXX" marker segments shall be present. As in the full 

resolution image of the JFIF file, the syntax of extension_data constrains parameters in the frame header 

as defined below: 

X 'FF', SOI 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

178

•

•

X'FF'. SOFn, length, frame parameters

Number of components Nf = 1 or 3 

1st component C1 = 1 = Y component 

2nd component C2 = 2 = Cb component 

3rd component C3 = 3 = Cr component 

•

•

X 'FF', EOI 

JFIF Extension: ThumbnaiI stored using one byte per pixel 

This extension supports thumbnails stored using one byte per pixel and a color palette in the 

extension_data field. The syntax of extension_data is: 

Xthumbnail (I byte) Thumbnail horizontal pixel count 

Ythumbnail (1 byte) Thumbnail vertical pixel count 

Palette (768 bytes) 24-bit RGB pixel values for the 

color 

palette. The RGB values define the colors 

represented by each value of an 8-bit 

binary encoding (0 - 255). 

(pixel)n (n bytes) 8-bit values for the thumbnail 

pixels 

n = Xthumbnail * Ythumbnall 

JFIF Extension: Thumbnail stored using three bytes per pixel 

This extension supports thumbnails stored using three bytes per pixel in the extension_data field. The 

syntax of extension_data is: 

Xthumbnail (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 = Xthumbnail * Ythumbnail 

Useful tips 

• 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'. 

• If you use APP0 elsewhere, be sure not to have the strings "JFIF” or “JFXX” right after the APP0 

marker. 

• If you do not want to include a thumbnail, just program Xthumbnail = Ythumbnail = 0. 

• 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. 
Part 2 – Annex D ANSI/NIST-ITL 2-2008

179

• 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. 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

180

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

(normative) 

This annex contains codes based on portions of the Ninth edition (December, 2000) of the NCIC Code 

Manual for describing Scars, Marks, Tattoos, and other characteristics (alphabetized by code). The 

following list is intended to standardize entry of data in the SMT Field. Care must be taken to enter 

spaces exactly as shown. However, as the NCIC Code Manual gets updated, the latest edition shall be 

the governing document regarding valid SMT codes. 

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

181

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

182

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

183

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

184

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

185

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

186

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

187

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

188

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

189

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

190

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 
Part 2 – Annex E ANSI/NIST-ITL 2-2008

191

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 

 
Part 2 – Annex F 

192

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://biometrics.nist.gov/standard/2-2008/ITL-2007f-Package.xsd" 12 xmlns:ansi-nist="http://niem.gov/niem/ansi-nist/2.0" 13 xmlns:itl="http://biometrics.nist.gov/standard/2-2008" 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 <!-- RECORD TYPE 01 19 <!-- ========================================================================================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 – Annex F 

193

1 <nc:OrganizationIdentification> 2 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 3 </nc:OrganizationIdentification> 4 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 5 </ansi-nist:TransactionOriginatingOrganization> 

6 <!-- ====================================================== fieldID="1.014" fieldMnemonic="GMT" 7 <ansi-nist:TransactionUTCDate> 8 <nc:DateTime>2005-11-05T05:25:00Z</nc:DateTime> 9 </ansi-nist:TransactionUTCDate> 

10 <!-- ====================================================== fieldID="1.009" fieldMnemonic="TCN" =11 <ansi-nist:TransactionControlIdentification> 

12 <nc:IdentificationID>56839</nc:IdentificationID> 13 </ansi-nist:TransactionControlIdentification> 

14 <!-- ====================================================== fieldID="1.010" fieldMnemonic="TCR" =15 <ansi-nist:TransactionControlReferenceIdentification> 

16 <nc:IdentificationID>29385</nc:IdentificationID> 17 </ansi-nist:TransactionControlReferenceIdentification> 

18 <!-- ====================================================== fieldID="1.013" fieldMnemonic="DOM" 19 <ansi-nist:TransactionDomain> 

20 <ansi-nist:DomainVersionNumberIdentification> 

21 <nc:IdentificationID>7.02</nc:IdentificationID> 

22 </ansi-nist:DomainVersionNumberIdentification> 23 <ansi-nist:OrganizationName>NORAM</ansi-nist:OrganizationName> 24 </ansi-nist:TransactionDomain> 25 <ansi-nist:TransactionImageResolutionDetails> 

26 <!-- ====================================================== fieldID="1.011" fieldMnemonic="NSR

27 <ansi-nist:NativeScanningResolutionValue>19.69</ansi-nist:NativeScanningResolutionValue> 

28 <!-- ====================================================== fieldID="1.012" fieldMnemonic="NTR

29 <ansi-nist:NominalTransmittingResolutionValue>19.69</ansi-nist:NominalTransmittingResolutionValue> 30 </ansi-nist:TransactionImageResolutionDetails> 

31 <!-- ====================================================== fieldID="1.002" fieldMnemonic="VER" =

32 <ansi-nist:TransactionMajorVersionValue>04</ansi-nist:TransactionMajorVersionValue> 

33 <ansi-nist:TransactionMinorVersionValue>00</ansi-nist:TransactionMinorVersionValue> 34 <!-- ====================================================== fieldID="1.006" fieldMnemonic="PRY" =

35 <ansi-nist:TransactionPriorityValue>5</ansi-nist:TransactionPriorityValue> 

36 <!-- ====================================================== fieldID="1.004" fieldMnemonic="TOT" =

37 <ansi-nist:TransactionCategoryCode>CAR</ansi-nist:TransactionCategoryCode> 
Part 2 – Annex F 

194

1 <!-- ====================================================== fieldID="1.003" fieldMnemonic="CNT" =2 <ansi-nist:TransactionContentSummary> 3 <ansi-nist:ContentFirstRecordCategoryCode>1</ansi-nist:ContentFirstRecordCategoryCode> 

4 <ansi-nist:ContentRecordCount>21</ansi-nist:ContentRecordCount> 5 <ansi-nist:ContentRecordSummary> 6 <ansi-nist:ImageReferenceIdentification> 

7 <nc:IdentificationID>00</nc:IdentificationID> 

8 </ansi-nist:ImageReferenceIdentification> 9 <ansi-nist:RecordCategoryCode>02</ansi-nist:RecordCategoryCode> 

10 </ansi-nist:ContentRecordSummary> 11 <ansi-nist:ContentRecordSummary> 12 <ansi-nist:ImageReferenceIdentification> 13 <nc:IdentificationID>01</nc:IdentificationID> 

14 </ansi-nist:ImageReferenceIdentification> 

15 <ansi-nist:RecordCategoryCode>03</ansi-nist:RecordCategoryCode> 16 </ansi-nist:ContentRecordSummary> 17 <ansi-nist:ContentRecordSummary> 18 <ansi-nist:ImageReferenceIdentification> 

19 <nc:IdentificationID>02</nc:IdentificationID> 

20 </ansi-nist:ImageReferenceIdentification> 

21 <ansi-nist:RecordCategoryCode>04</ansi-nist:RecordCategoryCode> 22 </ansi-nist:ContentRecordSummary> 23 <ansi-nist:ContentRecordSummary> 24 <ansi-nist:ImageReferenceIdentification> 

25 <nc:IdentificationID>03</nc:IdentificationID> 

26 </ansi-nist:ImageReferenceIdentification> 

27 <ansi-nist:RecordCategoryCode>05</ansi-nist:RecordCategoryCode> 28 </ansi-nist:ContentRecordSummary> 29 <ansi-nist:ContentRecordSummary> 30 <ansi-nist:ImageReferenceIdentification> 

31 <nc:IdentificationID>04</nc:IdentificationID> 

32 </ansi-nist:ImageReferenceIdentification> 

33 <ansi-nist:RecordCategoryCode>06</ansi-nist:RecordCategoryCode> 34 </ansi-nist:ContentRecordSummary> 

35 <ansi-nist:ContentRecordSummary> 36 <ansi-nist:ImageReferenceIdentification> 37 <nc:IdentificationID>05</nc:IdentificationID> 
Part 2 – Annex F 

195

1 </ansi-nist:ImageReferenceIdentification> 2 <ansi-nist:RecordCategoryCode>07</ansi-nist:RecordCategoryCode> 3 </ansi-nist:ContentRecordSummary> 4 <ansi-nist:ContentRecordSummary> 5 <ansi-nist:ImageReferenceIdentification> 

6 <nc:IdentificationID>06</nc:IdentificationID> 

7 </ansi-nist:ImageReferenceIdentification> 8 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 9 </ansi-nist:ContentRecordSummary> 

10 <ansi-nist:ContentRecordSummary> 11 <ansi-nist:ImageReferenceIdentification> 12 <nc:IdentificationID>06</nc:IdentificationID> 

13 </ansi-nist:ImageReferenceIdentification> 

14 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 15 </ansi-nist:ContentRecordSummary> 16 <ansi-nist:ContentRecordSummary> 17 <ansi-nist:ImageReferenceIdentification> 

18 <nc:IdentificationID>07</nc:IdentificationID> 

19 </ansi-nist:ImageReferenceIdentification> 

20 <ansi-nist:RecordCategoryCode>09</ansi-nist:RecordCategoryCode> 21 </ansi-nist:ContentRecordSummary> 22 <ansi-nist:ContentRecordSummary> 23 <ansi-nist:ImageReferenceIdentification> 

24 <nc:IdentificationID>08</nc:IdentificationID> 

25 </ansi-nist:ImageReferenceIdentification> 

26 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 27 </ansi-nist:ContentRecordSummary> 28 <ansi-nist:ContentRecordSummary> 29 <ansi-nist:ImageReferenceIdentification> 

30 <nc:IdentificationID>08</nc:IdentificationID> 

31 </ansi-nist:ImageReferenceIdentification> 

32 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 33 </ansi-nist:ContentRecordSummary> 34 <ansi-nist:ContentRecordSummary> 35 <ansi-nist:ImageReferenceIdentification> 

36 <nc:IdentificationID>09</nc:IdentificationID> 37 </ansi-nist:ImageReferenceIdentification> 
Part 2 – Annex F 

196

1 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 2 </ansi-nist:ContentRecordSummary> 3 <ansi-nist:ContentRecordSummary> 4 <ansi-nist:ImageReferenceIdentification> 

5 <nc:IdentificationID>09</nc:IdentificationID> 

6 </ansi-nist:ImageReferenceIdentification> 7 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 8 </ansi-nist:ContentRecordSummary> 9 <ansi-nist:ContentRecordSummary> 

10 <ansi-nist:ImageReferenceIdentification> 

11 <nc:IdentificationID>09</nc:IdentificationID> 

12 </ansi-nist:ImageReferenceIdentification> 

13 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 14 </ansi-nist:ContentRecordSummary> 15 <ansi-nist:ContentRecordSummary> 16 <ansi-nist:ImageReferenceIdentification> 

17 <nc:IdentificationID>10</nc:IdentificationID> 

18 </ansi-nist:ImageReferenceIdentification> 

19 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 20 </ansi-nist:ContentRecordSummary> 21 <ansi-nist:ContentRecordSummary> 22 <ansi-nist:ImageReferenceIdentification> 

23 <nc:IdentificationID>11</nc:IdentificationID> 

24 </ansi-nist:ImageReferenceIdentification> 

25 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 26 </ansi-nist:ContentRecordSummary> 27 <ansi-nist:ContentRecordSummary> 28 <ansi-nist:ImageReferenceIdentification> 

29 <nc:IdentificationID>12</nc:IdentificationID> 

30 </ansi-nist:ImageReferenceIdentification> 

31 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 32 </ansi-nist:ContentRecordSummary> 33 <ansi-nist:ContentRecordSummary> 34 <ansi-nist:ImageReferenceIdentification> 

35 <nc:IdentificationID>13</nc:IdentificationID> 

36 </ansi-nist:ImageReferenceIdentification> 

37 <ansi-nist:RecordCategoryCode>15</ansi-nist:RecordCategoryCode> 
Part 2 – Annex F 

197

1 </ansi-nist:ContentRecordSummary> 2 <ansi-nist:ContentRecordSummary> 3 <ansi-nist:ImageReferenceIdentification> 

4 <nc:IdentificationID>14</nc:IdentificationID> 

5 </ansi-nist:ImageReferenceIdentification> 6 <ansi-nist:RecordCategoryCode>16</ansi-nist:RecordCategoryCode> 7 </ansi-nist:ContentRecordSummary> 8 <ansi-nist:ContentRecordSummary> 9 <ansi-nist:ImageReferenceIdentification> 

10 <nc:IdentificationID>15</nc:IdentificationID> 

11 </ansi-nist:ImageReferenceIdentification> 

12 <ansi-nist:RecordCategoryCode>17</ansi-nist:RecordCategoryCode> 13 </ansi-nist:ContentRecordSummary> 14 <ansi-nist:ContentRecordSummary> 15 <ansi-nist:ImageReferenceIdentification> 

16 <nc:IdentificationID>16</nc:IdentificationID> 

17 </ansi-nist:ImageReferenceIdentification> 

18 <ansi-nist:RecordCategoryCode>99</ansi-nist:RecordCategoryCode> 19 </ansi-nist:ContentRecordSummary> 20 </ansi-nist:TransactionContentSummary> 

21 <!-- ====================================================== fieldID="1.015" fieldMnemonic="DCS" 22 <ansi-nist:TransactionCharacterSetDirectory> 23 <ansi-nist:CharacterSetCommonNameCode>ASCII 7-bit English</ansi-nist:CharacterSetCommonNameCode> 24 <ansi-nist:CharacterSetIndexCode>000</ansi-nist:CharacterSetIndexCode> 

25 <ansi-nist:CharacterSetVersionIdentification> 26 <nc:IdentificationID>000</nc:IdentificationID> 

27 </ansi-nist:CharacterSetVersionIdentification> 28 </ansi-nist:TransactionCharacterSetDirectory> 29 </ansi-nist:Transaction> 30 </itl:PackageInformationRecord> 31 32 <!-- ========================================================================================

33 <!-- RECORD TYPE 02 34 <!-- ========================================================================================35 <itl:PackageDescriptiveTextRecord> 

36 <ansi-nist:RecordCategoryCode>02</ansi-nist:RecordCategoryCode> 

37 <!-- ====================================================== fieldID="2.002" fieldMnemonic="IDC" == -
Part 2 – Annex F 

198

1 <ansi-nist:ImageReferenceIdentification> 2 <nc:IdentificationID>00</nc:IdentificationID> 

3 </ansi-nist:ImageReferenceIdentification> 

4 <!-- ====================================================== fieldID="2.003 999" User-defined fields == 5 <itl:UserDefinedDescriptiveText> 6 <itl:ExampleDomainDefinedDescriptiveText> 7 <!-- Well-formed XML goes here. Users may define a substitute element. --> 8 </itl:ExampleDomainDefinedDescriptiveText> 9 <itl:ExampleOtherDescriptiveText> 

10 <!-- Well-formed XML goes here. Users may define a substitute element. --> 11 </itl:ExampleOtherDescriptiveText> 

12 </itl:UserDefinedDescriptiveText> 13 </itl:PackageDescriptiveTextRecord> 14 15 <!-- ========================================================================================

16 <!-- RECORD TYPE 03 Low Resolution Grayscale Fingerprint Image 17 <!-- ========================================================================================18 <itl:PackageLowResolutionGrayscaleImageRecord> 

19 <ansi-nist:RecordCategoryCode>03</ansi-nist:RecordCategoryCode> 20 <!-- ====================================================================fieldMnemonic="IDC" =

21 <ansi-nist:ImageReferenceIdentification> 22 <nc:IdentificationID>01</nc:IdentificationID> 

23 </ansi-nist:ImageReferenceIdentification> 24 <ansi-nist:FingerprintImage> 25 <!-- ====================================================================fieldMnemonic="DAT26 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

27 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 28 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 29 <ansi-nist:ImageCaptureDetail> 30 <!-- ====================================================================fieldMnemonic="IS

31 <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 32 </ansi-nist:ImageCaptureDetail> 33 <!-- ====================================================================fieldMnemonic="GCA

34 <ansi-nist:ImageCompressionAlgorithmCode>0</ansi-nist:ImageCompressionAlgorithmCode> 35 <!-- ====================================================================fieldMnemonic="HLL

36 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 37 <!-- ====================================================================fieldMnemonic="VLL
Part 2 – Annex F 

199

1 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 2 <!-- ====================================================================fieldMnemonic="FGP3 <ansi-nist:FingerprintImagePosition> 

4 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode> 

5 <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode> 

6 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

7 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

8 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

9 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

10 </ansi-nist:FingerprintImagePosition> 11 <!-- ====================================================================fieldMnemonic="IMP

12 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureCate13 </ansi-nist:FingerprintImage> 14 </itl:PackageLowResolutionGrayscaleImageRecord> 15 16 <!-- ======================================================================================

17 <!-- RECORD TYPE 04 High Resolution Grayscale Fingerprint Image 18 <!-- ======================================================================================19 <itl:PackageHighResolutionGrayscaleImageRecord> 

20 <ansi-nist:RecordCategoryCode>04</ansi-nist:RecordCategoryCode> 21 <!-- ====================================================================fieldMnemonic="IDC22 <ansi-nist:ImageReferenceIdentification> 23 <nc:IdentificationID>02</nc:IdentificationID> 24 </ansi-nist:ImageReferenceIdentification> 25 <ansi-nist:FingerprintImage> 26 <!-- ====================================================================fieldMnemonic="D

27 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

28 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 29 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 30 <ansi-nist:ImageCaptureDetail> 31 <!-- ====================================================================fieldMnemonic=32 <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 33 </ansi-nist:ImageCaptureDetail> 34 <!-- ====================================================================fieldMnemonic="G

35 <ansi-nist:ImageCompressionAlgorithmCode>1</ansi-nist:ImageCompressionAlgorithmCode> 36 <!-- ====================================================================fieldMnemonic="H

37 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 
Part 2 – Annex F 

200

1 <!-- ====================================================================fieldMnemonic="V

2 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 3 <!-- ====================================================================fieldMnemonic="F4 <ansi-nist:FingerprintImagePosition> 

5 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode> 

6 <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode> 

7 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

8 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

9 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

10 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 11 </ansi-nist:FingerprintImagePosition> 12 <!-- ====================================================================fieldMnemonic="IM

13 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureC14 </ansi-nist:FingerprintImage> 15 </itl:PackageHighResolutionGrayscaleImageRecord> 16 17 <!-- ========================================================================================

18 <!-- RECORD TYPE 05 Low Resolution Binary Fingerprint Image 19 <!-- ========================================================================================20 <itl:PackageLowResolutionBinaryImageRecord> 

21 <ansi-nist:RecordCategoryCode>05</ansi-nist:RecordCategoryCode> 22 <!-- ====================================================================fieldMnemonic="IDC" =

23 <ansi-nist:ImageReferenceIdentification> 24 <nc:IdentificationID>03</nc:IdentificationID> 

25 </ansi-nist:ImageReferenceIdentification> 26 <ansi-nist:FingerprintImage> 27 <!-- ====================================================================fieldMnemonic="DAT28 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

29 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 30 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 31 <ansi-nist:ImageCaptureDetail> 32 <!-- ====================================================================fieldMnemonic="IS

33 <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 34 </ansi-nist:ImageCaptureDetail> 35 <!-- ====================================================================fieldMnemonic="BCA

36 <ansi-nist:ImageCompressionAlgorithmCode>1</ansi-nist:ImageCompressionAlgorithmCode> 37 <!-- ====================================================================fieldMnemonic="HLL
Part 2 – Annex F 

201

1 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 2 <!-- ====================================================================fieldMnemonic="VLL

3 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 4 <!-- ====================================================================fieldMnemonic="FGP5 <ansi-nist:FingerprintImagePosition> 

6 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode> 

7 <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode> 

8 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

9 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

10 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 11 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 12 </ansi-nist:FingerprintImagePosition> 13 <!-- ====================================================================fieldMnemonic="IMP

14 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureCate15 </ansi-nist:FingerprintImage> 16 </itl:PackageLowResolutionBinaryImageRecord> 17 18 <!-- ========================================================================================

19 <!-- RECORD TYPE 06 High Resolution Binary Fingerprint Image 20 <!-- ========================================================================================21 <itl:PackageHighResolutionBinaryImageRecord> 

22 <ansi-nist:RecordCategoryCode>06</ansi-nist:RecordCategoryCode> 23 <!-- ====================================================================fieldMnemonic="IDC" =24 <ansi-nist:ImageReferenceIdentification> 25 <nc:IdentificationID>04</nc:IdentificationID> 26 </ansi-nist:ImageReferenceIdentification> 27 <ansi-nist:FingerprintImage> 28 <!-- ====================================================================fieldMnemonic="DAT29 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

30 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 31 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 32 <ansi-nist:ImageCaptureDetail> 33 <!-- ====================================================================fieldMnemonic="IS

34 <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 35 </ansi-nist:ImageCaptureDetail> 36 <!-- ====================================================================fieldMnemonic="BCA

37 <ansi-nist:ImageCompressionAlgorithmCode>1</ansi-nist:ImageCompressionAlgorithmCode> 
Part 2 – Annex F 

202

1 <!-- ====================================================================fieldMnemonic="HLL

2 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 3 <!-- ====================================================================fieldMnemonic="VLL

4 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 5 <!-- ====================================================================fieldMnemonic="FGP6 <ansi-nist:FingerprintImagePosition> 

7 <ansi-nist:FingerPositionCode>2</ansi-nist:FingerPositionCode> 

8 <ansi-nist:FingerPositionCode>3</ansi-nist:FingerPositionCode> 

9 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 

10 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 11 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 12 <ansi-nist:FingerPositionCode>255</ansi-nist:FingerPositionCode> 13 </ansi-nist:FingerprintImagePosition> 14 <!-- ====================================================================fieldMnemonic="IMP

15 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>3</ansi-nist:FingerprintImageImpressionCaptureCate16 </ansi-nist:FingerprintImage> 17 </itl:PackageHighResolutionBinaryImageRecord> 18 19 <!-- ========================================================================================

20 <!-- RECORD TYPE 07 User-defined Image Record 21 <!-- ========================================================================================22 <itl:PackageUserDefinedImageRecord> 

23 <ansi-nist:RecordCategoryCode>07</ansi-nist:RecordCategoryCode> 24 <!-- ====================================================================fieldMnemonic="IDC" =

25 <ansi-nist:ImageReferenceIdentification> 26 <nc:IdentificationID>05</nc:IdentificationID> 

27 </ansi-nist:ImageReferenceIdentification> 28 <itl:ExampleRecordImage> 29 <!-- Well-formed XML goes here. Users may define a substitute element. --> 30 </itl:ExampleRecordImage> 31 </itl:PackageUserDefinedImageRecord> 32 33 <!-- ========================================================================================

34 <!-- RECORD TYPE 08 Signature Image Record (with scanned image) 35 <!-- ========================================================================================36 <itl:PackageSignatureImageRecord> 

37 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 
Part 2 – Annex F 

203

1 <!-- ====================================================================fieldMnemonic="IDC" =2 <ansi-nist:ImageReferenceIdentification> 3 <nc:IdentificationID>06</nc:IdentificationID> 

4 </ansi-nist:ImageReferenceIdentification> 5 <ansi-nist:SignatureImage> 

6 <!-- ==========================================================Scanned Image Data ==========7 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

8 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 9 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

10 <ansi-nist:ImageCaptureDetail> 11 <!-- ====================================================================fieldMnemonic="IS

12 <ansi-nist:CaptureResolutionCode>1</ansi-nist:CaptureResolutionCode> 13 </ansi-nist:ImageCaptureDetail> 14 <!-- ====================================================================fieldMnemonic="HLL

15 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 16 <!-- ====================================================================fieldMnemonic="VLL

17 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 18 <!-- ====================================================================fieldMnemonic="SRT

19 <ansi-nist:SignatureRepresentationCode>1</ansi-nist:SignatureRepresentationCode> 20 <!-- ====================================================================fieldMnemonic="SIG" 

21 <ansi-nist:SignatureCategoryCode>0</ansi-nist:SignatureCategoryCode> 22 </ansi-nist:SignatureImage> 23 </itl:PackageSignatureImageRecord> 24 25 <!-- ========================================================================================

26 <!-- RECORD TYPE 08 Signature Image Record (with vector image) 27 <!-- ========================================================================================28 <itl:PackageSignatureImageRecord> 

29 <ansi-nist:RecordCategoryCode>08</ansi-nist:RecordCategoryCode> 30 <!-- ====================================================================fieldMnemonic="IDC" =

31 <ansi-nist:ImageReferenceIdentification> 32 <nc:IdentificationID>06</nc:IdentificationID> 

33 </ansi-nist:ImageReferenceIdentification> 34 <ansi-nist:SignatureImage> 35 <!-- ==========================================================Vectored Image Data =========36 <ansi-nist:SignatureImageVectorRepresentation> 37 <ansi-nist:SignatureImageVector> 
Part 2 – Annex F 

204

1 <ansi-nist:VectorPenPressureValue>254</ansi-nist:VectorPenPressureValue> 

2 <ansi-nist:VectorPositionVerticalCoordinateValue>0</ansi-nist:VectorPositionVerticalCoordinateValue> 

3 <ansi-nist:VectorPositionHorizontalCoordinateValue>0</ansi-nist:VectorPositionHorizontalCoordinateValue> 4 </ansi-nist:SignatureImageVector> 5 <ansi-nist:SignatureImageVector> 

6 <ansi-nist:VectorPenPressureValue>1</ansi-nist:VectorPenPressureValue> 

7 <ansi-nist:VectorPositionVerticalCoordinateValue>5</ansi-nist:VectorPositionVerticalCoordinateValue> 

8 <ansi-nist:VectorPositionHorizontalCoordinateValue>5</ansi-nist:VectorPositionHorizontalCoordinateValue> 9 </ansi-nist:SignatureImageVector> 

10 </ansi-nist:SignatureImageVectorRepresentation> 11 <!-- ====================================================================fieldMnemonic="SRT

12 <ansi-nist:SignatureRepresentationCode>2</ansi-nist:SignatureRepresentationCode> 13 <!-- ====================================================================fieldMnemonic="SIG" 

14 <ansi-nist:SignatureCategoryCode>0</ansi-nist:SignatureCategoryCode> 15 </ansi-nist:SignatureImage> 16 </itl:PackageSignatureImageRecord> 17 18 <!-- ========================================================================================

19 <!-- RECORD TYPE 09 Minutiae Data Record 20 <!-- ========================================================================================21 <itl:PackageMinutiaeRecord> 

22 <ansi-nist:RecordCategoryCode>09</ansi-nist:RecordCategoryCode> 

23 <!-- ======================================================== fieldID="9.002" fieldMnemonic="IDC" =

24 <ansi-nist:ImageReferenceIdentification> 25 <nc:IdentificationID>07</nc:IdentificationID> 

26 </ansi-nist:ImageReferenceIdentification> 

27 <!-- ======================================================== fieldID="9.003" fieldMnemonic="IMP" =

28 <ansi-nist:MinutiaeImpressionCaptureCategoryCode>4</ansi-nist:MinutiaeImpressionCaptureCategoryCode> 

29 <!-- ======================================================== fieldID="9.004" fieldMnemonic="FMT" 

30 <ansi-nist:MinutiaeFormatNISTStandardIndicator>true</ansi-nist:MinutiaeFormatNISTStandardIndicator> 31 <itl:Minutiae> 32 <itl:MinutiaeNISTStandard> 33 <!-- ======================================================== fieldID="9.012" fieldMnemonic="M

34 <itl:MinutiaDetail> 35 <ansi-nist:PositionHorizontalCoordinateValue>0486</ansi-nist:PositionHorizontalCoordinateValue> 

36 <ansi-nist:PositionVerticalCoordinateValue>2839</ansi-nist:PositionVerticalCoordinateValue> 37 <ansi-nist:MinutiaIdentification> 
Part 2 – Annex F 

205

1 <nc:IdentificationID>1</nc:IdentificationID> 2 </ansi-nist:MinutiaIdentification> 3 <ansi-nist:PositionThetaAngleMeasure>048</ansi-nist:PositionThetaAngleMeasure> 4 <ansi-nist:MinutiaQualityValue>1</ansi-nist:MinutiaQualityValue> 5 <ansi-nist:MinutiaCategoryCode>B</ansi-nist:MinutiaCategoryCode> 6 <ansi-nist:MinutiaRidgeCount> 7 <ansi-nist:RidgeCountReferenceIdentification> 

8 <nc:IdentificationID>2</nc:IdentificationID> 9 </ansi-nist:RidgeCountReferenceIdentification> 

10 <ansi-nist:RidgeCountValue>6</ansi-nist:RidgeCountValue> 11 </ansi-nist:MinutiaRidgeCount> 12 <ansi-nist:MinutiaRidgeCount> 

13 <ansi-nist:RidgeCountReferenceIdentification> 

14 <nc:IdentificationID>8</nc:IdentificationID> 15 </ansi-nist:RidgeCountReferenceIdentification> 

16 <ansi-nist:RidgeCountValue>3</ansi-nist:RidgeCountValue> 17 </ansi-nist:MinutiaRidgeCount> 18 </itl:MinutiaDetail> 19 <itl:MinutiaDetail> 

20 <ansi-nist:PositionHorizontalCoordinateValue>4859</ansi-nist:PositionHorizontalCoordinateValue> 

21 <ansi-nist:PositionVerticalCoordinateValue>0473</ansi-nist:PositionVerticalCoordinateValue> 22 <ansi-nist:MinutiaIdentification> 

23 <nc:IdentificationID>1</nc:IdentificationID> 24 </ansi-nist:MinutiaIdentification> 25 <ansi-nist:PositionThetaAngleMeasure>256</ansi-nist:PositionThetaAngleMeasure> 

26 <ansi-nist:MinutiaQualityValue>63</ansi-nist:MinutiaQualityValue> 

27 <ansi-nist:MinutiaCategoryCode>A</ansi-nist:MinutiaCategoryCode> 28 <ansi-nist:MinutiaRidgeCount> 

29 <ansi-nist:RidgeCountReferenceIdentification> 

30 <nc:IdentificationID>14</nc:IdentificationID> 31 </ansi-nist:RidgeCountReferenceIdentification> 

32 <ansi-nist:RidgeCountValue>4</ansi-nist:RidgeCountValue> 33 </ansi-nist:MinutiaRidgeCount> 34 </itl:MinutiaDetail> 35 <!-- ======================================================== fieldID="9.010" fieldMnemonic="M

36 <ansi-nist:MinutiaeQuantity>2</ansi-nist:MinutiaeQuantity> 37 <!-- ======================================================== fieldID="9.005" fieldMnemonic="O
Part 2 – Annex F 

206

1 <ansi-nist:MinutiaeReadingSystem> 

2 <ansi-nist:ReadingSystemCodingMethodCode>E</ansi-nist:ReadingSystemCodingMethodCode> 

3 <ansi-nist:ReadingSystemName>Universal Latent Workstation</ansi-nist:ReadingSystemName> 4 <ansi-nist:ReadingSystemSubsystemIdentification> 

5 <nc:IdentificationID>AA</nc:IdentificationID> 6 </ansi-nist:ReadingSystemSubsystemIdentification> 7 </ansi-nist:MinutiaeReadingSystem> 8 <!-- ======================================================== fieldID="9.011" fieldMnemonic="R9 <ansi-nist:MinutiaeRidgeCountIndicator>true</ansi-nist:MinutiaeRidgeCountIndicator> 

10 </itl:MinutiaeNISTStandard> 

11 <!-- ======================================================== fieldID="9.008" fieldMnemonic="CRP12 <ansi-nist:MinutiaeFingerCorePosition> 

13 <ansi-nist:PositionHorizontalCoordinateValue>0035</ansi-nist:PositionHorizontalCoordinateValue> 

14 <ansi-nist:PositionVerticalCoordinateValue>0045</ansi-nist:PositionVerticalCoordinateValue> 15 </ansi-nist:MinutiaeFingerCorePosition> 16 <ansi-nist:MinutiaeFingerCorePosition> 

17 <ansi-nist:PositionHorizontalCoordinateValue>0038</ansi-nist:PositionHorizontalCoordinateValue> 

18 <ansi-nist:PositionVerticalCoordinateValue>0048</ansi-nist:PositionVerticalCoordinateValue> 19 </ansi-nist:MinutiaeFingerCorePosition> 

20 <!-- ======================================================== fieldID="9.009" fieldMnemonic="DLT21 <ansi-nist:MinutiaeFingerDeltaPosition> 

22 <ansi-nist:PositionHorizontalCoordinateValue>0158</ansi-nist:PositionHorizontalCoordinateValue> 

23 <ansi-nist:PositionVerticalCoordinateValue>1948</ansi-nist:PositionVerticalCoordinateValue> 24 </ansi-nist:MinutiaeFingerDeltaPosition> 

25 <!-- ======================================================== fieldID="9.007" fieldMnemonic="FPC26 <itl:MinutiaeFingerPatternDetail> 27 <itl:FingerPatternCodeSourceCode>T</itl:FingerPatternCodeSourceCode> 28 <ansi-nist:FingerPatternCode>PW</ansi-nist:FingerPatternCode> 29 </itl:MinutiaeFingerPatternDetail> 

30 <!-- ======================================================== fieldID="9.006" fieldMnemonic="FGP31 <ansi-nist:MinutiaeFingerPositionCode>5</ansi-nist:MinutiaeFingerPositionCode> 32 <ansi-nist:MinutiaeFingerPositionCode>6</ansi-nist:MinutiaeFingerPositionCode> 33 <ansi-nist:MinutiaePalmPositionCode>22</ansi-nist:MinutiaePalmPositionCode> 

34 </itl:Minutiae> 35 </itl:PackageMinutiaeRecord> 36 37 
Part 2 – Annex F 

207

1 <!-- ========================================================================================

2 <!-- RECORD TYPE 10 Facial Image Record 3 <!-- ========================================================================================4 <itl:PackageFacialAndSMTImageRecord> 

5 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 

6 <!-- ====================================================== fieldID="10.002" fieldMnemonic="IDC" == 7 <ansi-nist:ImageReferenceIdentification> 8 <nc:IdentificationID>08</nc:IdentificationID> 9 </ansi-nist:ImageReferenceIdentification> 

10 <!-- =================================================== fieldID="10.200-998" fieldMnemonic="UDF" =11 <itl:ExampleUserDefinedFields> 12 <!-- Well-formed XML goes here. Users may define a substitute element. --> 13 </itl:ExampleUserDefinedFields> 14 <itl:FaceImage> 15 <!-- =====================================================fieldID="10.999" fieldMnemonic="DATA" 16 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

17 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 18 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 19 <ansi-nist:ImageCaptureDetail> 

20 <!-- =====================================================fieldID="10.005" fieldMnemonic="PHD21 <ansi-nist:CaptureDate> 22 <nc:Date>1953-04-23</nc:Date> 23 </ansi-nist:CaptureDate> 24 <!-- =====================================================fieldID="10.016" fieldMnemonic="SHP

25 <ansi-nist:CaptureHorizontalPixelDensityValue>1200</ansi-nist:CaptureHorizontalPixelDensityValue> 26 <!-- =====================================================fieldID="10.004" fieldMnemonic="SRC27 <ansi-nist:CaptureOrganization> 28 <nc:OrganizationIdentification> 29 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 30 </nc:OrganizationIdentification> 31 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 32 </ansi-nist:CaptureOrganization> 

33 <!-- =====================================================fieldID="10.017" fieldMnemonic="SVP

34 <ansi-nist:CaptureVerticalPixelDensityValue>1200</ansi-nist:CaptureVerticalPixelDensityValue> 

35 <!-- =====================================================fieldID="10.030" fieldMnemonic="DMM36 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 37 </ansi-nist:ImageCaptureDetail> 
Part 2 – Annex F 

208

1 <!-- =====================================================fieldID="10.012" fieldMnemonic="CSP" =

2 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> 

3 <!-- =====================================================fieldID="10.011" fieldMnemonic="CGA" =4 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 

5 <!-- =====================================================fieldID="10.006" fieldMnemonic="HLL" =6 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

7 <!-- =====================================================fieldID="10.009" fieldMnemonic="HPS" =

8 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 

9 <!-- =====================================================fieldID="10.024" fieldMnemonic="SQS" =

10 <ansi-nist:ImageQuality> 

11 <ansi-nist:QualityAlgorithmProductIdentification> 12 <nc:IdentificationID>28495</nc:IdentificationID> 

13 </ansi-nist:QualityAlgorithmProductIdentification> 

14 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

15 <ansi-nist:QualityMeasureVendorIdentification> 

16 <nc:IdentificationID>FFF0</nc:IdentificationID> 17 </ansi-nist:QualityMeasureVendorIdentification> 18 </ansi-nist:ImageQuality> 19 <!-- =====================================================fieldID="10.008" fieldMnemonic="SLC" =

20 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 21 <!-- =====================================================fieldID="10.003" fieldMnemonic="IMT" == 

22 <ansi-nist:ImageCategoryCode>FACE</ansi-nist:ImageCategoryCode> 

23 <!-- =====================================================fieldID="10.007" fieldMnemonic="VLL" == 

24 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

25 <!-- =====================================================fieldID="10.010" fieldMnemonic="VPS" =

26 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

27 <!-- =====================================================fieldID="10.025" fieldMnemonic="SPA" =28 <ansi-nist:FaceImage3DPoseAngle> 

29 <ansi-nist:PosePitchAngleMeasure>45</ansi-nist:PosePitchAngleMeasure> 

30 <ansi-nist:PosePitchUncertaintyValue>35</ansi-nist:PosePitchUncertaintyValue> 31 <ansi-nist:PoseRollAngleMeasure>0</ansi-nist:PoseRollAngleMeasure> 

32 <ansi-nist:PoseRollUncertaintyValue>90</ansi-nist:PoseRollUncertaintyValue> 

33 <ansi-nist:PoseYawAngleMeasure>0</ansi-nist:PoseYawAngleMeasure> 

34 <ansi-nist:PoseYawUncertaintyValue>0</ansi-nist:PoseYawUncertaintyValue> 35 </ansi-nist:FaceImage3DPoseAngle> 

36 <!-- =====================================================fieldID="10.013" fieldMnemonic="SAP" =37 <ansi-nist:FaceImageAcquisitionProfileCode>20</ansi-nist:FaceImageAcquisitionProfileCode> 
Part 2 – Annex F 

209

1 <!-- =====================================================fieldID="10.022" fieldMnemonic="PXS" =2 <ansi-nist:FaceImageAttribute> 

3 <ansi-nist:FaceImageAttributeCode>GLASSES</ansi-nist:FaceImageAttributeCode> 4 </ansi-nist:FaceImageAttribute> 5 <ansi-nist:FaceImageAttribute> 

6 <ansi-nist:FaceImageAttributeCode>OTHER</ansi-nist:FaceImageAttributeCode> 7 <ansi-nist:FaceImageAttributeText>SKI MASK</ansi-nist:FaceImageAttributeText> 8 </ansi-nist:FaceImageAttribute> 9 <ansi-nist:FaceImageAttribute> 

10 <ansi-nist:FaceImageAttributeCode>PHYSICAL</ansi-nist:FaceImageAttributeCode> 

11 <ansi-nist:FaceImageAttributeText>ART EYE</ansi-nist:FaceImageAttributeText> 12 </ansi-nist:FaceImageAttribute> 13 <!-- =====================================================fieldID="10.026" fieldMnemonic="SXS" =

14 <ansi-nist:FaceImageDescriptionCode>MOUTH OPEN</ansi-nist:FaceImageDescriptionCode> 

15 <ansi-nist:FaceImageDescriptionCode>TEETH VISIBLE</ansi-nist:FaceImageDescriptionCode> 

16 <ansi-nist:FaceImageDescriptionCode>NO EAR</ansi-nist:FaceImageDescriptionCode> 17 <!-- =====================================================fieldID="10.027" fieldMnemonic="SEC" =

18 <ansi-nist:FaceImageEyeColorAttributeCode>HAZ</ansi-nist:FaceImageEyeColorAttributeCode> 19 <!-- =====================================================fieldID="10.029" fieldMnemonic="SFP" =20 <ansi-nist:FaceImageFeaturePoint> 21 <ansi-nist:FeaturePointHorizontalCoordinateValue>258</ansi-nist:FeaturePointHorizontalCoordinateValue> 22 <ansi-nist:FeaturePointIdentification> 23 <nc:IdentificationID>11.5</nc:IdentificationID> 24 </ansi-nist:FeaturePointIdentification> 25 <ansi-nist:FeaturePointCategoryCode>1</ansi-nist:FeaturePointCategoryCode> 26 <ansi-nist:FeaturePointVerticalCoordinateValue>55</ansi-nist:FeaturePointVerticalCoordinateValue> 27 </ansi-nist:FaceImageFeaturePoint> 28 <ansi-nist:FaceImageFeaturePoint> 29 <ansi-nist:FeaturePointHorizontalCoordinateValue>256</ansi-nist:FeaturePointHorizontalCoordinateValue> 30 <ansi-nist:FeaturePointIdentification> 

31 <nc:IdentificationID>2.1</nc:IdentificationID> 32 </ansi-nist:FeaturePointIdentification> 33 <ansi-nist:FeaturePointCategoryCode>1</ansi-nist:FeaturePointCategoryCode> 34 <ansi-nist:FeaturePointVerticalCoordinateValue>212</ansi-nist:FeaturePointVerticalCoordinateValue> 35 </ansi-nist:FaceImageFeaturePoint> 

36 <!-- =====================================================fieldID="10.028" fieldMnemonic="SHC" =

37 <ansi-nist:FaceImageHairColorAttributeCode>BAL</ansi-nist:FaceImageHairColorAttributeCode> 
Part 2 – Annex F 

210

1 <ansi-nist:FaceImageHairColorAttributeCode>GRN</ansi-nist:FaceImageHairColorAttributeCode> 

2 <!-- =====================================================fieldID="10.021" fieldMnemonic="POA" =3 <ansi-nist:FaceImagePoseOffsetAngleMeasure>45</ansi-nist:FaceImagePoseOffsetAngleMeasure> 

4 <!-- =====================================================fieldID="10.020" fieldMnemonic="POS" =5 <ansi-nist:FaceImageSubjectPoseCode>A</ansi-nist:FaceImageSubjectPoseCode> 

6 <!-- =====================================================fieldID="10.023" fieldMnemonic="PAS" =7 <itl:FaceImageAcquisitionSource> 

8 <ansi-nist:CaptureSourceCode>VENDOR</ansi-nist:CaptureSourceCode> 

9 <itl:CaptureSourceDescriptionText>CELL PHONE</itl:CaptureSourceDescriptionText> 

10 </itl:FaceImageAcquisitionSource> 11 </itl:FaceImage> 

12 </itl:PackageFacialAndSMTImageRecord> 13 14 <!-- ========================================================================================

15 <!-- RECORD TYPE 10 SMT Image Record 16 <!-- ========================================================================================17 <itl:PackageFacialAndSMTImageRecord> 

18 <ansi-nist:RecordCategoryCode>10</ansi-nist:RecordCategoryCode> 

19 <!-- ====================================================== fieldID="10.002" fieldMnemonic="IDC" == 

20 <ansi-nist:ImageReferenceIdentification> 21 <nc:IdentificationID>08</nc:IdentificationID> 

22 </ansi-nist:ImageReferenceIdentification> 

23 <!-- =================================================== fieldID="10.200-998" fieldMnemonic="UDF" =24 <itl:ExampleUserDefinedFields> 25 <!-- Well-formed XML goes here. Users may define a substitute element. --> 26 </itl:ExampleUserDefinedFields> 27 <ansi-nist:PhysicalFeatureImage> 28 <!-- =====================================================fieldID="10.999" fieldMnemonic="DATA" 29 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

30 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 31 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 32 <ansi-nist:ImageCaptureDetail> 

33 <!-- =====================================================fieldID="10.005" fieldMnemonic="PHD34 <ansi-nist:CaptureDate> 35 <nc:Date>1953-04-23</nc:Date> 36 </ansi-nist:CaptureDate> 

37 <!-- =====================================================fieldID="10.016" fieldMnemonic="SHP
Part 2 – Annex F 

211

1 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

2 <!-- =====================================================fieldID="10.004" fieldMnemonic="SRC3 <ansi-nist:CaptureOrganization> 4 <nc:OrganizationIdentification> 5 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 6 </nc:OrganizationIdentification> 7 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 8 </ansi-nist:CaptureOrganization> 9 <!-- =====================================================fieldID="10.023" fieldMnemonic="PAS

10 <ansi-nist:CaptureSourceCode>DIGITAL CAMERA</ansi-nist:CaptureSourceCode> 

11 <!-- =====================================================fieldID="10.017" fieldMnemonic="SVP

12 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 

13 <!-- =====================================================fieldID="10.030" fieldMnemonic="DMM14 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 15 </ansi-nist:ImageCaptureDetail> 16 <!-- =====================================================fieldID="10.012" fieldMnemonic="CSP" =

17 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> 

18 <!-- =====================================================fieldID="10.011" fieldMnemonic="CGA" =19 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 20 <!-- =====================================================fieldID="10.006" fieldMnemonic="HLL" =

21 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 22 <!-- =====================================================fieldID="10.009" fieldMnemonic="HPS" =

23 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 

24 <!-- =====================================================fieldID="10.008" fieldMnemonic="SLC" =

25 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 26 <!-- =====================================================fieldID="10.003" fieldMnemonic="IMT" == 

27 <ansi-nist:ImageCategoryCode>TATTOO</ansi-nist:ImageCategoryCode> 

28 <!-- =====================================================fieldID="10.007" fieldMnemonic="VLL" == 

29 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 30 <!-- =====================================================fieldID="10.010" fieldMnemonic="VPS" =

31 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

32 <!-- =====================================================fieldID="10.042" fieldMnemonic="SMD" =

33 <ansi-nist:PhysicalFeatureDescriptionDetail> 34 <!-- =Req'd to be associated with 10.042=====fieldID="10.043" fieldMnemonic="COL" == --> 35 <ansi-nist:PhysicalFeatureColorDetail> 

36 <ansi-nist:PhysicalFeaturePrimaryColorCode>ORANGE</ansi-nist:PhysicalFeaturePrimaryColorCode> 37 <ansi-nist:PhysicalFeatureSecondaryColorCode>BLACK</ansi-nist:PhysicalFeatureSecondaryColorCode> 
Part 2 – Annex F 

212

1 <ansi-nist:PhysicalFeatureSecondaryColorCode>RED</ansi-nist:PhysicalFeatureSecondaryColorCode> 2 </ansi-nist:PhysicalFeatureColorDetail> 

3 <!-- =============================SubFields for "10.042" fieldMnemonic="SMD" == --> 

4 <ansi-nist:PhysicalFeatureCategoryCode>TATTOO</ansi-nist:PhysicalFeatureCategoryCode> 

5 <ansi-nist:PhysicalFeatureClassCode>ANIMAL</ansi-nist:PhysicalFeatureClassCode> 

6 <ansi-nist:PhysicalFeatureDescriptionText>Golden retriever with an overbite</ansi-nist:PhysicalFeatureDescripti

7 <ansi-nist:PhysicalFeatureSubClassCode>DOG</ansi-nist:PhysicalFeatureSubClassCode> 

8 </ansi-nist:PhysicalFeatureDescriptionDetail> 9 <ansi-nist:PhysicalFeatureDescriptionDetail> 

10 <ansi-nist:PhysicalFeatureColorDetail> 

11 <ansi-nist:PhysicalFeaturePrimaryColorCode>YELLOW</ansi-nist:PhysicalFeaturePrimaryColorCode> 

12 <ansi-nist:PhysicalFeatureSecondaryColorCode>MULTI</ansi-nist:PhysicalFeatureSecondaryColorCode> 13 </ansi-nist:PhysicalFeatureColorDetail> 

14 <ansi-nist:PhysicalFeatureCategoryCode>TATTOO</ansi-nist:PhysicalFeatureCategoryCode> 

15 <ansi-nist:PhysicalFeatureClassCode>HUMAN</ansi-nist:PhysicalFeatureClassCode> 16 <ansi-nist:PhysicalFeatureDescriptionText>Fist</ansi-nist:PhysicalFeatureDescriptionText> 

17 <ansi-nist:PhysicalFeatureSubClassCode>MBPART</ansi-nist:PhysicalFeatureSubClassCode> 

18 </ansi-nist:PhysicalFeatureDescriptionDetail> 

19 <!-- =====================================================fieldID="10.040" fieldMnemonic="SMT" =20 <ansi-nist:PhysicalFeatureNCICCode>TAT L TOE</ansi-nist:PhysicalFeatureNCICCode> 21 <ansi-nist:PhysicalFeatureNCICCode>TAT FARM</ansi-nist:PhysicalFeatureNCICCode> 22 <!-- =====================================================fieldID="10.041" fieldMnemonic="SMS" =23 <ansi-nist:PhysicalFeatureSize> 

24 <ansi-nist:PhysicalFeatureHeightMeasure>112</ansi-nist:PhysicalFeatureHeightMeasure> 

25 <ansi-nist:PhysicalFeatureWidthMeasure>15</ansi-nist:PhysicalFeatureWidthMeasure> 26 </ansi-nist:PhysicalFeatureSize> 27 </ansi-nist:PhysicalFeatureImage> 

28 </itl:PackageFacialAndSMTImageRecord> 29 30 <!-- ========================================================================================

31 <!-- RECORD TYPE 13 Variable-Resolution Latent Image (Single finger example) 32 <!-- ========================================================================================33 <itl:PackageLatentImageRecord> 

34 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

35 <!-- ====================================================== fieldID="13.002" fieldMnemonic="IDC" == 

36 <ansi-nist:ImageReferenceIdentification> 37 <nc:IdentificationID>09</nc:IdentificationID> 
Part 2 – Annex F 

213

1 </ansi-nist:ImageReferenceIdentification> 

2 <!-- =================================================== fieldID="13.200-998" fieldMnemonic="UDF" =3 <itl:ExampleUserDefinedFields> 4 <!-- Well-formed XML goes here. Users may define a substitute element. --> 5 </itl:ExampleUserDefinedFields> 6 <itl:FingerprintImage> 

7 <!-- =====================================================fieldID="13.999" fieldMnemonic="DATA" 8 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

9 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 

10 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 11 <!-- =====================================================fieldID="13.012" fieldMnemonic="BPX" =12 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 13 <ansi-nist:ImageCaptureDetail> 14 <!-- =====================================================fieldID="13.005" fieldMnemonic="LCD15 <ansi-nist:CaptureDate> 16 <nc:Date>1953-04-23</nc:Date> 17 </ansi-nist:CaptureDate> 18 <!-- =====================================================fieldID="13.016" fieldMnemonic="SHP

19 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

20 <!-- =====================================================fieldID="13.004" fieldMnemonic="SRC21 <ansi-nist:CaptureOrganization> 22 <nc:OrganizationIdentification> 23 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 24 </nc:OrganizationIdentification> 25 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 26 </ansi-nist:CaptureOrganization> 27 <!-- =====================================================fieldID="13.017" fieldMnemonic="SVP

28 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 29 </ansi-nist:ImageCaptureDetail> 

30 <!-- =====================================================fieldID="13.020" fieldMnemonic="COM" =

31 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

32 <!-- =====================================================fieldID="13.011" fieldMnemonic="CGA" =33 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 34 <!-- =====================================================fieldID="13.006" fieldMnemonic="HLL" =

35 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

36 <!-- =====================================================fieldID="13.009" fieldMnemonic="HPS" =37 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 
Part 2 – Annex F 

214

1 <!-- =====================================================fieldID="13.008" fieldMnemonic="SLC" =

2 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

3 <!-- =====================================================fieldID="13.007" fieldMnemonic="VLL" == 

4 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

5 <!-- =====================================================fieldID="13.010" fieldMnemonic="VPS" =6 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

7 <!-- =====================================================fieldID="13.003" fieldMnemonic="IMP" == 

8 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4</ansi-nist:FingerprintImageImpressionCaptureCate

9 <!-- =====================================================fieldID="13.013" fieldMnemonic="FGP" =

10 <ansi-nist:FingerPositionCode>4</ansi-nist:FingerPositionCode> 

11 <ansi-nist:FingerPositionCode>5</ansi-nist:FingerPositionCode> 

12 <!-- =====================================================fieldID="13.024" fieldMnemonic="LQM" =13 <itl:FingerprintImageQuality> 14 <ansi-nist:FingerPositionCode>4</ansi-nist:FingerPositionCode> 

15 <ansi-nist:QualityAlgorithmProductIdentification> 

16 <nc:IdentificationID>28495</nc:IdentificationID> 

17 </ansi-nist:QualityAlgorithmProductIdentification> 

18 <ansi-nist:QualityAlgorithmVendorIdentification> 

19 <nc:IdentificationID>FFF0</nc:IdentificationID> 20 </ansi-nist:QualityAlgorithmVendorIdentification> 

21 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 22 </itl:FingerprintImageQuality> 23 </itl:FingerprintImage> 24 </itl:PackageLatentImageRecord> 25 26 <!-- ========================================================================================

27 <!-- RECORD TYPE 13 Variable-Resolution Latent Image (Palm Latent Example) 28 <!-- ========================================================================================29 <itl:PackageLatentImageRecord> 

30 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

31 <!-- ====================================================== fieldID="13.002" fieldMnemonic="IDC" == 32 <ansi-nist:ImageReferenceIdentification> 33 <nc:IdentificationID>09</nc:IdentificationID> 34 </ansi-nist:ImageReferenceIdentification> 

35 <!-- =================================================== fieldID="13.200-998" fieldMnemonic="UDF" =36 <itl:ExampleUserDefinedFields> 37 <!-- Well-formed XML goes here. Users may define a substitute element. --> 
Part 2 – Annex F 

215

1 </itl:ExampleUserDefinedFields> 2 <itl:PalmprintImage> 

3 <!-- =====================================================fieldID="13.999" fieldMnemonic="DATA" 4 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

5 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 6 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

7 <!-- =====================================================fieldID="13.012" fieldMnemonic="BPX" =8 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 9 <ansi-nist:ImageCaptureDetail> 

10 <!-- =====================================================fieldID="13.005" fieldMnemonic="LCD11 <ansi-nist:CaptureDate> 12 <nc:Date>1953-04-23</nc:Date> 13 </ansi-nist:CaptureDate> 

14 <!-- =====================================================fieldID="13.016" fieldMnemonic="SHP

15 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

16 <!-- =====================================================fieldID="13.004" fieldMnemonic="SRC17 <ansi-nist:CaptureOrganization> 18 <nc:OrganizationIdentification> 19 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 20 </nc:OrganizationIdentification> 21 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 22 </ansi-nist:CaptureOrganization> 23 <!-- =====================================================fieldID="13.017" fieldMnemonic="SVP

24 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 25 </ansi-nist:ImageCaptureDetail> 

26 <!-- =====================================================fieldID="13.020" fieldMnemonic="COM" =

27 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

28 <!-- =====================================================fieldID="13.011" fieldMnemonic="CGA" =

29 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 

30 <!-- =====================================================fieldID="13.006" fieldMnemonic="HLL" =

31 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

32 <!-- =====================================================fieldID="13.009" fieldMnemonic="HPS" =33 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 34 <!-- =====================================================fieldID="13.008" fieldMnemonic="SLC" =

35 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

36 <!-- =====================================================fieldID="13.007" fieldMnemonic="VLL" == 

37 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 
Part 2 – Annex F 

216

1 <!-- =====================================================fieldID="13.010" fieldMnemonic="VPS" =

2 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

3 <!-- =====================================================fieldID="13.003" fieldMnemonic="IMP" == 

4 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4</ansi-nist:FingerprintImageImpressionCaptureCate

5 <!-- =====================================================fieldID="13.013" fieldMnemonic="FGP" =6 <ansi-nist:PalmPositionCode>29</ansi-nist:PalmPositionCode> 7 <ansi-nist:PalmPositionCode>23</ansi-nist:PalmPositionCode> 

8 <!-- =====================================================fieldID="13.024" fieldMnemonic="LQM" =9 <itl:PalmprintImageQuality> 

10 <ansi-nist:PalmPositionCode>29</ansi-nist:PalmPositionCode> 

11 <ansi-nist:QualityAlgorithmProductIdentification> 

12 <nc:IdentificationID>28495</nc:IdentificationID> 

13 </ansi-nist:QualityAlgorithmProductIdentification> 14 <ansi-nist:QualityAlgorithmVendorIdentification> 

15 <nc:IdentificationID>FFF0</nc:IdentificationID> 16 </ansi-nist:QualityAlgorithmVendorIdentification> 

17 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 18 </itl:PalmprintImageQuality> 19 </itl:PalmprintImage> 20 </itl:PackageLatentImageRecord> 21 22 <!-- ========================================================================================

23 <!-- RECORD TYPE 13 Variable-Resolution Latent Image (Major Case example) 24 <!-- ========================================================================================25 <itl:PackageLatentImageRecord> 

26 <ansi-nist:RecordCategoryCode>13</ansi-nist:RecordCategoryCode> 

27 <!-- ====================================================== fieldID="13.002" fieldMnemonic="IDC" == 

28 <ansi-nist:ImageReferenceIdentification> 29 <nc:IdentificationID>09</nc:IdentificationID> 

30 </ansi-nist:ImageReferenceIdentification> 

31 <!-- =================================================== fieldID="13.200-998" fieldMnemonic="UDF" =32 <itl:ExampleUserDefinedFields> 33 <!-- Well-formed XML goes here. Users may define a substitute element. --> 34 </itl:ExampleUserDefinedFields> 35 <itl:FingerprintImage> 

36 <!-- =====================================================fieldID="13.999" fieldMnemonic="DATA" 37 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 
Part 2 – Annex F 

217

1 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 2 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

3 <!-- =====================================================fieldID="13.012" fieldMnemonic="BPX" =4 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 5 <ansi-nist:ImageCaptureDetail> 6 <!-- =====================================================fieldID="13.005" fieldMnemonic="LCD7 <ansi-nist:CaptureDate> 8 <nc:Date>1953-04-23</nc:Date> 9 </ansi-nist:CaptureDate> 

10 <!-- =====================================================fieldID="13.016" fieldMnemonic="SHP

11 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

12 <!-- =====================================================fieldID="13.004" fieldMnemonic="SRC13 <ansi-nist:CaptureOrganization> 14 <nc:OrganizationIdentification> 15 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 16 </nc:OrganizationIdentification> 17 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 18 </ansi-nist:CaptureOrganization> 19 <!-- =====================================================fieldID="13.017" fieldMnemonic="SVP

20 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 21 </ansi-nist:ImageCaptureDetail> 

22 <!-- =====================================================fieldID="13.020" fieldMnemonic="COM" =

23 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

24 <!-- =====================================================fieldID="13.011" fieldMnemonic="CGA" =25 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 26 <!-- =====================================================fieldID="13.006" fieldMnemonic="HLL" =

27 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

28 <!-- =====================================================fieldID="13.009" fieldMnemonic="HPS" =29 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 30 <!-- =====================================================fieldID="13.008" fieldMnemonic="SLC" =

31 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

32 <!-- =====================================================fieldID="13.007" fieldMnemonic="VLL" == 

33 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 34 <!-- =====================================================fieldID="13.010" fieldMnemonic="VPS" =

35 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

36 <!-- =====================================================fieldID="13.003" fieldMnemonic="IMP" == 

37 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>4</ansi-nist:FingerprintImageImpressionCaptureCate
Part 2 – Annex F 

218

1 <!-- =====================================================fieldID="13.013" fieldMnemonic="FGP" =2 <ansi-nist:FingerPositionCode>19</ansi-nist:FingerPositionCode> 3 <ansi-nist:FingerprintImageMajorCasePrint> 4 <!-- =====================================================fieldID="13.014" fieldMnemonic="SPD

5 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

6 <ansi-nist:MajorCasePrintCode>EJI</ansi-nist:MajorCasePrintCode> 7 <!-- =====================================================fieldID="13.015" fieldMnemonic="PPC8 <ansi-nist:MajorCasePrintSegmentOffset> 

9 <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 

10 <ansi-nist:SegmentLocationCode>DST</ansi-nist:SegmentLocationCode> 

11 <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode> 

12 <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

13 <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue> 

14 <ansi-nist:SegmentTopVerticalCoordinateValue>55</ansi-nist:SegmentTopVerticalCoordinateValue> 15 </ansi-nist:MajorCasePrintSegmentOffset> 16 <ansi-nist:MajorCasePrintSegmentOffset> 

17 <ansi-nist:SegmentBottomVerticalCoordinateValue>126</ansi-nist:SegmentBottomVerticalCoordinateValue> 18 <ansi-nist:SegmentLocationCode>MED</ansi-nist:SegmentLocationCode> 19 <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode> 

20 <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

21 <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue> 

22 <ansi-nist:SegmentTopVerticalCoordinateValue>92</ansi-nist:SegmentTopVerticalCoordinateValue> 23 </ansi-nist:MajorCasePrintSegmentOffset> 24 </ansi-nist:FingerprintImageMajorCasePrint> 25 <!-- =====================================================fieldID="13.024" fieldMnemonic="LQM" =26 <itl:FingerprintImageQuality> 

27 <ansi-nist:FingerPositionCode>19</ansi-nist:FingerPositionCode> 28 <ansi-nist:QualityAlgorithmProductIdentification> 29 <nc:IdentificationID>28495</nc:IdentificationID> 

30 </ansi-nist:QualityAlgorithmProductIdentification> 31 <ansi-nist:QualityAlgorithmVendorIdentification> 

32 <nc:IdentificationID>FFF0</nc:IdentificationID> 33 </ansi-nist:QualityAlgorithmVendorIdentification> 

34 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 35 </itl:FingerprintImageQuality> 36 </itl:FingerprintImage> 37 </itl:PackageLatentImageRecord> 
Part 2 – Annex F 

219

1 2 <!-- ========================================================================================

3 <!-- RECORD TYPE 14 Variable Resolution Fingerprint Image (Single Finger) 4 <!-- ========================================================================================5 <itl:PackageFingerprintImageRecord> 

6 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

7 <!-- ====================================================== fieldID="14.002" fieldMnemonic="IDC" == 8 <ansi-nist:ImageReferenceIdentification> 9 <nc:IdentificationID>10</nc:IdentificationID> 

10 </ansi-nist:ImageReferenceIdentification> 

11 <!-- =================================================== fieldID="14.200-998" fieldMnemonic="UDF" =12 <itl:ExampleUserDefinedFields> 13 <!-- Well-formed XML goes here. Users may define a substitute element. --> 14 </itl:ExampleUserDefinedFields> 15 <itl:FingerprintImage> 16 <!-- =====================================================fieldID="14.999" fieldMnemonic="DATA" 17 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

18 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 19 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 20 <!-- =====================================================fieldID="14.012" fieldMnemonic="BPX" =21 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 22 <ansi-nist:ImageCaptureDetail> 23 <!-- =====================================================fieldID="14.005" fieldMnemonic="FCD24 <ansi-nist:CaptureDate> 25 <nc:Date>1953-04-23</nc:Date> 26 </ansi-nist:CaptureDate> 27 <!-- =====================================================fieldID="14.016" fieldMnemonic="SHP

28 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

29 <!-- =====================================================fieldID="14.004" fieldMnemonic="SRC

30 <ansi-nist:CaptureOrganization> 31 <nc:OrganizationIdentification> 32 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 33 </nc:OrganizationIdentification> 34 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 35 </ansi-nist:CaptureOrganization> 

36 <!-- =====================================================fieldID="14.017" fieldMnemonic="SVP

37 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 
Part 2 – Annex F 

220

1 <!-- =====================================================fieldID="14.030" fieldMnemonic="DMM2 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 3 </ansi-nist:ImageCaptureDetail> 

4 <!-- =====================================================fieldID="14.020" fieldMnemonic="COM" =

5 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

6 <!-- =====================================================fieldID="14.011" fieldMnemonic="CGA" =7 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 

8 <!-- =====================================================fieldID="14.006" fieldMnemonic="HLL" =9 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

10 <!-- =====================================================fieldID="14.009" fieldMnemonic="HPS" =

11 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 

12 <!-- =====================================================fieldID="14.008" fieldMnemonic="SLC" =

13 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 14 <!-- =====================================================fieldID="14.007" fieldMnemonic="VLL" == 

15 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 16 <!-- =====================================================fieldID="14.010" fieldMnemonic="VPS" =

17 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 18 <!-- =====================================================fieldID="14.003" fieldMnemonic="IMP" == 

19 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1</ansi-nist:FingerprintImageImpressionCaptureCate

20 <!-- =====================================================fieldID="14.013" fieldMnemonic="FGP" =

21 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

22 <!-- =====================================================fieldID="14.022" fieldMnemonic="NQM" =23 <ansi-nist:FingerprintImageNISTQuality> 24 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 25 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure> 26 </ansi-nist:FingerprintImageNISTQuality> 

27 <!-- =====================================================fieldID="14.024" fieldMnemonic="FQM" =28 <itl:FingerprintImageQuality> 29 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 30 <ansi-nist:QualityAlgorithmProductIdentification> 31 <nc:IdentificationID>28495</nc:IdentificationID> 

32 </ansi-nist:QualityAlgorithmProductIdentification> 

33 <ansi-nist:QualityAlgorithmVendorIdentification> 

34 <nc:IdentificationID>FFF0</nc:IdentificationID> 35 </ansi-nist:QualityAlgorithmVendorIdentification> 

36 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 37 </itl:FingerprintImageQuality> 
Part 2 – Annex F 

221

1 </itl:FingerprintImage> 2 </itl:PackageFingerprintImageRecord> 3 4 <!-- ========================================================================================

5 <!-- RECORD TYPE 14 Variable Resolution Fingerprint Image (Slap Print Set) 6 <!-- ========================================================================================7 <itl:PackageFingerprintImageRecord> 

8 <ansi-nist:RecordCategoryCode>14</ansi-nist:RecordCategoryCode> 

9 <!-- ====================================================== fieldID="14.002" fieldMnemonic="IDC" == 

10 <ansi-nist:ImageReferenceIdentification> 11 <nc:IdentificationID>11</nc:IdentificationID> 12 </ansi-nist:ImageReferenceIdentification> 

13 <!-- =================================================== fieldID="14.200-998" fieldMnemonic="UDF" =14 <itl:ExampleUserDefinedFields> 15 <!-- Well-formed XML goes here. Users may define a substitute element. --> 16 </itl:ExampleUserDefinedFields> 17 <itl:FingerprintImage> 18 <!-- =====================================================fieldID="14.999" fieldMnemonic="DATA" 19 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

20 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 21 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 22 <!-- =====================================================fieldID="14.012" fieldMnemonic="BPX" =23 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 24 <ansi-nist:ImageCaptureDetail> 25 <!-- =====================================================fieldID="14.005" fieldMnemonic="FCD26 <ansi-nist:CaptureDate> 27 <nc:Date>1953-04-23</nc:Date> 28 </ansi-nist:CaptureDate> 29 <!-- =====================================================fieldID="14.016" fieldMnemonic="SHP

30 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

31 <!-- =====================================================fieldID="14.004" fieldMnemonic="SRC32 <ansi-nist:CaptureOrganization> 33 <nc:OrganizationIdentification> 34 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 35 </nc:OrganizationIdentification> 36 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 37 </ansi-nist:CaptureOrganization> 
Part 2 – Annex F 

222

1 <!-- =====================================================fieldID="14.017" fieldMnemonic="SVP2 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 

3 <!-- =====================================================fieldID="14.030" fieldMnemonic="DMM4 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 5 </ansi-nist:ImageCaptureDetail> 

6 <!-- =====================================================fieldID="14.020" fieldMnemonic="COM" =

7 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

8 <!-- =====================================================fieldID="14.011" fieldMnemonic="CGA" =9 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 

10 <!-- =====================================================fieldID="14.006" fieldMnemonic="HLL" =

11 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 12 <!-- =====================================================fieldID="14.009" fieldMnemonic="HPS" =

13 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 

14 <!-- =====================================================fieldID="14.008" fieldMnemonic="SLC" =

15 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 16 <!-- =====================================================fieldID="14.007" fieldMnemonic="VLL" == 

17 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 18 <!-- =====================================================fieldID="14.010" fieldMnemonic="VPS" =

19 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 20 <!-- =====================================================fieldID="14.003" fieldMnemonic="IMP" == 

21 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1</ansi-nist:FingerprintImageImpressionCaptureCate22 <!-- =====================================================fieldID="14.013" fieldMnemonic="FGP" =23 <ansi-nist:FingerPositionCode>14</ansi-nist:FingerPositionCode> 24 <!-- =====================================================fieldID="14.018" fieldMnemonic="AMP" =25 <itl:FingerprintImageFingerMissing> 26 <ansi-nist:FingerPositionCode>10</ansi-nist:FingerPositionCode> 27 <itl:FingerMissingCode>XX</itl:FingerMissingCode> 28 </itl:FingerprintImageFingerMissing> 29 <itl:FingerprintImageFingerMissing> 30 <ansi-nist:FingerPositionCode>9</ansi-nist:FingerPositionCode> 31 <itl:FingerMissingCode>XX</itl:FingerMissingCode> 32 </itl:FingerprintImageFingerMissing> 33 <!-- =====================================================fieldID="14.021" fieldMnemonic="SEG" =34 <itl:FingerprintImageSegmentPositionSquare> 35 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 36 <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 37 <ansi-nist:SegmentLeftHorizontalCoordinateValue>100</ansi-nist:SegmentLeftHorizontalCoordinateValue> 
Part 2 – Annex F 

223

1 <ansi-nist:SegmentRightHorizontalCoordinateValue>150</ansi-nist:SegmentRightHorizontalCoordinateValue> 2 <ansi-nist:SegmentTopVerticalCoordinateValue>15</ansi-nist:SegmentTopVerticalCoordinateValue> 3 </itl:FingerprintImageSegmentPositionSquare> 4 <itl:FingerprintImageSegmentPositionSquare> 

5 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 

6 <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 

7 <ansi-nist:SegmentLeftHorizontalCoordinateValue>160</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

8 <ansi-nist:SegmentRightHorizontalCoordinateValue>200</ansi-nist:SegmentRightHorizontalCoordinateValue> 9 <ansi-nist:SegmentTopVerticalCoordinateValue>15</ansi-nist:SegmentTopVerticalCoordinateValue> 

10 </itl:FingerprintImageSegmentPositionSquare> 

11 <!-- =====================================================fieldID="14.022" fieldMnemonic="NQM" =12 <ansi-nist:FingerprintImageNISTQuality> 13 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 14 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure> 15 </ansi-nist:FingerprintImageNISTQuality> 16 <ansi-nist:FingerprintImageNISTQuality> 17 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 18 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure> 19 </ansi-nist:FingerprintImageNISTQuality> 20 <ansi-nist:FingerprintImageNISTQuality> 21 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 22 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure> 23 </ansi-nist:FingerprintImageNISTQuality> 24 <ansi-nist:FingerprintImageNISTQuality> 25 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 26 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure> 27 </ansi-nist:FingerprintImageNISTQuality> 

28 <!-- =====================================================fieldID="14.023" fieldMnemonic="SQM" =29 <ansi-nist:FingerprintImageSegmentationQuality> 30 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

31 <ansi-nist:QualityAlgorithmProductIdentification> 

32 <nc:IdentificationID>28495</nc:IdentificationID> 

33 </ansi-nist:QualityAlgorithmProductIdentification> 

34 <ansi-nist:QualityAlgorithmVendorIdentification> 

35 <nc:IdentificationID>FFF0</nc:IdentificationID> 

36 </ansi-nist:QualityAlgorithmVendorIdentification> 

37 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 
Part 2 – Annex F 

224

1 </ansi-nist:FingerprintImageSegmentationQuality> 2 <ansi-nist:FingerprintImageSegmentationQuality> 

3 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 4 <ansi-nist:QualityAlgorithmProductIdentification> 

5 <nc:IdentificationID>28495</nc:IdentificationID> 

6 </ansi-nist:QualityAlgorithmProductIdentification> 7 <ansi-nist:QualityAlgorithmVendorIdentification> 

8 <nc:IdentificationID>FFF0</nc:IdentificationID> 9 </ansi-nist:QualityAlgorithmVendorIdentification> 

10 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 11 </ansi-nist:FingerprintImageSegmentationQuality> 

12 <!-- =====================================================fieldID="14.024" fieldMnemonic="FQM" =13 <itl:FingerprintImageQuality> 14 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 

15 <ansi-nist:QualityAlgorithmProductIdentification> 

16 <nc:IdentificationID>28495</nc:IdentificationID> 

17 </ansi-nist:QualityAlgorithmProductIdentification> 

18 <ansi-nist:QualityAlgorithmVendorIdentification> 

19 <nc:IdentificationID>FFF0</nc:IdentificationID> 20 </ansi-nist:QualityAlgorithmVendorIdentification> 

21 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 22 </itl:FingerprintImageQuality> 23 <itl:FingerprintImageQuality> 24 <ansi-nist:FingerPositionCode>9</ansi-nist:FingerPositionCode> 25 <ansi-nist:QualityAlgorithmProductIdentification> 

26 <nc:IdentificationID>28495</nc:IdentificationID> 

27 </ansi-nist:QualityAlgorithmProductIdentification> 

28 <ansi-nist:QualityAlgorithmVendorIdentification> 

29 <nc:IdentificationID>FFF0</nc:IdentificationID> 30 </ansi-nist:QualityAlgorithmVendorIdentification> 

31 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 32 </itl:FingerprintImageQuality> 

33 <!-- =====================================================fieldID="14.025" fieldMnemonic="ASEG" 

34 <itl:FingerprintImageSegmentPositionPolygon> 35 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 36 <itl:PositionPolygonVertexQuantity>4</itl:PositionPolygonVertexQuantity> 37 <itl:PositionPolygonVertex> 
Part 2 – Annex F 

225

1 <ansi-nist:PositionHorizontalCoordinateValue>100</ansi-nist:PositionHorizontalCoordinateValue> 

2 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 3 </itl:PositionPolygonVertex> 4 <itl:PositionPolygonVertex> 

5 <ansi-nist:PositionHorizontalCoordinateValue>150</ansi-nist:PositionHorizontalCoordinateValue> 

6 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 7 </itl:PositionPolygonVertex> 8 <itl:PositionPolygonVertex> 

9 <ansi-nist:PositionHorizontalCoordinateValue>150</ansi-nist:PositionHorizontalCoordinateValue> 

10 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 11 </itl:PositionPolygonVertex> 12 <itl:PositionPolygonVertex> 

13 <ansi-nist:PositionHorizontalCoordinateValue>100</ansi-nist:PositionHorizontalCoordinateValue> 

14 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 15 </itl:PositionPolygonVertex> 16 </itl:FingerprintImageSegmentPositionPolygon> 17 <itl:FingerprintImageSegmentPositionPolygon> 18 <ansi-nist:FingerPositionCode>7</ansi-nist:FingerPositionCode> 

19 <itl:PositionPolygonVertexQuantity>4</itl:PositionPolygonVertexQuantity> 20 <itl:PositionPolygonVertex> 

21 <ansi-nist:PositionHorizontalCoordinateValue>160</ansi-nist:PositionHorizontalCoordinateValue> 

22 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 23 </itl:PositionPolygonVertex> 24 <itl:PositionPolygonVertex> 

25 <ansi-nist:PositionHorizontalCoordinateValue>200</ansi-nist:PositionHorizontalCoordinateValue> 

26 <ansi-nist:PositionVerticalCoordinateValue>15</ansi-nist:PositionVerticalCoordinateValue> 27 </itl:PositionPolygonVertex> 28 <itl:PositionPolygonVertex> 

29 <ansi-nist:PositionHorizontalCoordinateValue>200</ansi-nist:PositionHorizontalCoordinateValue> 

30 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 31 </itl:PositionPolygonVertex> 32 <itl:PositionPolygonVertex> 

33 <ansi-nist:PositionHorizontalCoordinateValue>160</ansi-nist:PositionHorizontalCoordinateValue> 

34 <ansi-nist:PositionVerticalCoordinateValue>85</ansi-nist:PositionVerticalCoordinateValue> 35 </itl:PositionPolygonVertex> 36 </itl:FingerprintImageSegmentPositionPolygon> 37 </itl:FingerprintImage> 
Part 2 – Annex F 

226

1 </itl:PackageFingerprintImageRecord> 2 3 <!-- ========================================================================================

4 <!-- RECORD TYPE 14 Variable Resolution Fingerprint Image (Major Case) 5 <!-- ========================================================================================6 <itl:PackageFingerprintImageRecord> 

7 <ansi-nist:RecordCategoryCode>12</ansi-nist:RecordCategoryCode> 

8 <!-- ====================================================== fieldID="14.002" fieldMnemonic="IDC" == 9 <ansi-nist:ImageReferenceIdentification> 

10 <nc:IdentificationID>10</nc:IdentificationID> 

11 </ansi-nist:ImageReferenceIdentification> 

12 <!-- =================================================== fieldID="14.200-998" fieldMnemonic="UDF" =13 <itl:ExampleUserDefinedFields> 14 <!-- Well-formed XML goes here. Users may define a substitute element. --> 15 </itl:ExampleUserDefinedFields> 16 <itl:FingerprintImage> 

17 <!-- =====================================================fieldID="14.999" fieldMnemonic="DATA" 18 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

19 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 20 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

21 <!-- =====================================================fieldID="14.012" fieldMnemonic="BPX" =22 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 23 <ansi-nist:ImageCaptureDetail> 24 <!-- =====================================================fieldID="14.005" fieldMnemonic="FCD25 <ansi-nist:CaptureDate> 26 <nc:Date>1953-04-23</nc:Date> 27 </ansi-nist:CaptureDate> 28 <!-- =====================================================fieldID="14.016" fieldMnemonic="SHP

29 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

30 <!-- =====================================================fieldID="14.004" fieldMnemonic="SRC

31 <ansi-nist:CaptureOrganization> 32 <nc:OrganizationIdentification> 33 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 34 </nc:OrganizationIdentification> 35 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 36 </ansi-nist:CaptureOrganization> 

37 <!-- =====================================================fieldID="14.017" fieldMnemonic="SVP
Part 2 – Annex F 

227

1 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 

2 <!-- =====================================================fieldID="14.030" fieldMnemonic="DMM3 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 4 </ansi-nist:ImageCaptureDetail> 

5 <!-- =====================================================fieldID="14.020" fieldMnemonic="COM" =

6 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

7 <!-- =====================================================fieldID="14.011" fieldMnemonic="CGA" =8 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 

9 <!-- =====================================================fieldID="14.006" fieldMnemonic="HLL" =

10 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 11 <!-- =====================================================fieldID="14.009" fieldMnemonic="HPS" =

12 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 

13 <!-- =====================================================fieldID="14.008" fieldMnemonic="SLC" =

14 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 15 <!-- =====================================================fieldID="14.007" fieldMnemonic="VLL" == 

16 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 17 <!-- =====================================================fieldID="14.010" fieldMnemonic="VPS" =

18 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 19 <!-- =====================================================fieldID="14.003" fieldMnemonic="IMP" == 

20 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>1</ansi-nist:FingerprintImageImpressionCaptureCate

21 <!-- =====================================================fieldID="14.013" fieldMnemonic="FGP" =22 <ansi-nist:FingerPositionCode>19</ansi-nist:FingerPositionCode> 

23 <!-- =====================================================fieldID="14.014" fieldMnemonic="PPD" =24 <ansi-nist:FingerprintImageMajorCasePrint> 25 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 26 <ansi-nist:MajorCasePrintCode>EJI</ansi-nist:MajorCasePrintCode> 

27 <!-- =====================================================fieldID="14.015" fieldMnemonic="PPC28 <ansi-nist:MajorCasePrintSegmentOffset> 

29 <ansi-nist:SegmentBottomVerticalCoordinateValue>85</ansi-nist:SegmentBottomVerticalCoordinateValue> 30 <ansi-nist:SegmentLocationCode>DST</ansi-nist:SegmentLocationCode> 

31 <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode> 

32 <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

33 <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue> 

34 <ansi-nist:SegmentTopVerticalCoordinateValue>55</ansi-nist:SegmentTopVerticalCoordinateValue> 35 </ansi-nist:MajorCasePrintSegmentOffset> 36 <ansi-nist:MajorCasePrintSegmentOffset> 

37 <ansi-nist:SegmentBottomVerticalCoordinateValue>126</ansi-nist:SegmentBottomVerticalCoordinateValue> 
Part 2 – Annex F 

228

1 <ansi-nist:SegmentLocationCode>MED</ansi-nist:SegmentLocationCode> 

2 <ansi-nist:SegmentFingerViewCode>FV1</ansi-nist:SegmentFingerViewCode> 

3 <ansi-nist:SegmentLeftHorizontalCoordinateValue>115</ansi-nist:SegmentLeftHorizontalCoordinateValue> 

4 <ansi-nist:SegmentRightHorizontalCoordinateValue>188</ansi-nist:SegmentRightHorizontalCoordinateValue> 

5 <ansi-nist:SegmentTopVerticalCoordinateValue>92</ansi-nist:SegmentTopVerticalCoordinateValue> 6 </ansi-nist:MajorCasePrintSegmentOffset> 7 </ansi-nist:FingerprintImageMajorCasePrint> 

8 <!-- =====================================================fieldID="14.022" fieldMnemonic="NQM" =9 <ansi-nist:FingerprintImageNISTQuality> 

10 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 11 <ansi-nist:NISTQualityMeasure>1</ansi-nist:NISTQualityMeasure> 12 </ansi-nist:FingerprintImageNISTQuality> 13 <!-- =====================================================fieldID="14.024" fieldMnemonic="FQM" =14 <itl:FingerprintImageQuality> 15 <ansi-nist:FingerPositionCode>8</ansi-nist:FingerPositionCode> 

16 <ansi-nist:QualityAlgorithmProductIdentification> 

17 <nc:IdentificationID>28495</nc:IdentificationID> 

18 </ansi-nist:QualityAlgorithmProductIdentification> 19 <ansi-nist:QualityAlgorithmVendorIdentification> 

20 <nc:IdentificationID>FFF0</nc:IdentificationID> 21 </ansi-nist:QualityAlgorithmVendorIdentification> 

22 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 23 </itl:FingerprintImageQuality> 24 </itl:FingerprintImage> 25 </itl:PackageFingerprintImageRecord> 26 27 <!-- ========================================================================================

28 <!-- RECORD TYPE 15 Variable Resolution Palmprint Image 29 <!-- ========================================================================================30 <itl:PackagePalmprintImageRecord> 

31 <ansi-nist:RecordCategoryCode>15</ansi-nist:RecordCategoryCode> 

32 <!-- ====================================================== fieldID="15.002" fieldMnemonic="IDC" == 

33 <ansi-nist:ImageReferenceIdentification> 34 <nc:IdentificationID>13</nc:IdentificationID> 

35 </ansi-nist:ImageReferenceIdentification> 

36 <!-- =================================================== fieldID="15.200-998" fieldMnemonic="UDF" =37 <itl:ExampleUserDefinedFields> 
Part 2 – Annex F 

229

1 <!-- Well-formed XML goes here. Users may define a substitute element. --> 2 </itl:ExampleUserDefinedFields> 3 <itl:PalmprintImage> 

4 <!-- =====================================================fieldID="15.999" fieldMnemonic="DATA" 5 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

6 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 7 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

8 <!-- =====================================================fieldID="15.012" fieldMnemonic="BPX" =9 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 

10 <ansi-nist:ImageCaptureDetail> 

11 <!-- =====================================================fieldID="15.005" fieldMnemonic="PCD12 <ansi-nist:CaptureDate> 13 <nc:Date>1953-04-23</nc:Date> 14 </ansi-nist:CaptureDate> 

15 <!-- =====================================================fieldID="15.016" fieldMnemonic="SHP

16 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

17 <!-- =====================================================fieldID="15.004" fieldMnemonic="SRC18 <ansi-nist:CaptureOrganization> 19 <nc:OrganizationIdentification> 20 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 21 </nc:OrganizationIdentification> 22 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 23 </ansi-nist:CaptureOrganization> 24 <!-- =====================================================fieldID="15.017" fieldMnemonic="SVP

25 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 

26 <!-- =====================================================fieldID="15.030" fieldMnemonic="DMM27 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 28 </ansi-nist:ImageCaptureDetail> 

29 <!-- =====================================================fieldID="15.020" fieldMnemonic="COM" =

30 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

31 <!-- =====================================================fieldID="15.011" fieldMnemonic="CGA" =32 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 33 <!-- =====================================================fieldID="15.006" fieldMnemonic="HLL" =

34 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

35 <!-- =====================================================fieldID="15.009" fieldMnemonic="HPS" =36 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 37 <!-- =====================================================fieldID="15.008" fieldMnemonic="SLC" =
Part 2 – Annex F 

230

1 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

2 <!-- =====================================================fieldID="15.007" fieldMnemonic="VLL" == 

3 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

4 <!-- =====================================================fieldID="15.010" fieldMnemonic="VPS" =5 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 

6 <!-- =====================================================fieldID="15.003" fieldMnemonic="IMP" == 

7 <ansi-nist:FingerprintImageImpressionCaptureCategoryCode>10</ansi-nist:FingerprintImageImpressionCaptureCa

8 <!-- =====================================================fieldID="15.013" fieldMnemonic="PLP" =9 <ansi-nist:PalmPositionCode>28</ansi-nist:PalmPositionCode> 

10 <!-- =====================================================fieldID="15.024" fieldMnemonic="PQM" =11 <itl:PalmprintImageQuality> 12 <ansi-nist:PalmPositionCode>28</ansi-nist:PalmPositionCode> 

13 <ansi-nist:QualityAlgorithmProductIdentification> 

14 <nc:IdentificationID>28495</nc:IdentificationID> 

15 </ansi-nist:QualityAlgorithmProductIdentification> 16 <ansi-nist:QualityAlgorithmVendorIdentification> 

17 <nc:IdentificationID>FFF0</nc:IdentificationID> 18 </ansi-nist:QualityAlgorithmVendorIdentification> 

19 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 20 </itl:PalmprintImageQuality> 21 </itl:PalmprintImage> 22 </itl:PackagePalmprintImageRecord> 23 24 <!-- ========================================================================================

25 <!-- RECORD TYPE 16 User Defined Testing Image 26 <!-- ========================================================================================27 <itl:PackageUserDefinedTestingImageRecord> 

28 <ansi-nist:RecordCategoryCode>16</ansi-nist:RecordCategoryCode> 

29 <!-- ====================================================== fieldID="16.002" fieldMnemonic="IDC" == 30 <ansi-nist:ImageReferenceIdentification> 31 <nc:IdentificationID>14</nc:IdentificationID> 32 </ansi-nist:ImageReferenceIdentification> 

33 <!-- =================================================== fieldID="16.200-998" fieldMnemonic="UDF" =34 <itl:ExampleUserDefinedFields> 35 <!-- Well-formed XML goes here. Users may define a substitute element. --> 36 </itl:ExampleUserDefinedFields> 37 <itl:TestImage> 
Part 2 – Annex F 

231

1 <!-- =====================================================fieldID="16.999" fieldMnemonic="DATA" 2 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

3 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 4 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 

5 <!-- =====================================================fieldID="16.003" fieldMnemonic="UDI" == 6 <nc:BinaryDescriptionText>Test Image</nc:BinaryDescriptionText> 

7 <!-- =====================================================fieldID="16.012" fieldMnemonic="BPX" =8 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 9 <ansi-nist:ImageCaptureDetail> 

10 <!-- =====================================================fieldID="16.005" fieldMnemonic="UTD11 <ansi-nist:CaptureDate> 12 <nc:Date>1953-04-23</nc:Date> 13 </ansi-nist:CaptureDate> 14 <!-- =====================================================fieldID="16.016" fieldMnemonic="SHP

15 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

16 <!-- =====================================================fieldID="16.004" fieldMnemonic="SRC17 <ansi-nist:CaptureOrganization> 18 <nc:OrganizationIdentification> 19 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 20 </nc:OrganizationIdentification> 21 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 22 </ansi-nist:CaptureOrganization> 23 <!-- =====================================================fieldID="16.017" fieldMnemonic="SVP

24 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 

25 <!-- =====================================================fieldID="16.030" fieldMnemonic="DMM26 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 27 </ansi-nist:ImageCaptureDetail> 

28 <!-- =====================================================fieldID="16.013" fieldMnemonic="CSP" =

29 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> 

30 <!-- =====================================================fieldID="16.020" fieldMnemonic="COM" =

31 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

32 <!-- =====================================================fieldID="16.011" fieldMnemonic="CGA" =33 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 34 <!-- =====================================================fieldID="16.006" fieldMnemonic="HLL" =

35 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

36 <!-- =====================================================fieldID="16.009" fieldMnemonic="HPS" =37 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 
Part 2 – Annex F 

232

1 <!-- =====================================================fieldID="16.024" fieldMnemonic="UQS" =2 <ansi-nist:ImageQuality> 3 <ansi-nist:QualityAlgorithmProductIdentification> 4 <nc:IdentificationID>28495</nc:IdentificationID> 

5 </ansi-nist:QualityAlgorithmProductIdentification> 6 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 

7 <ansi-nist:QualityMeasureVendorIdentification> 

8 <nc:IdentificationID>FFF0</nc:IdentificationID> 9 </ansi-nist:QualityMeasureVendorIdentification> 

10 </ansi-nist:ImageQuality> 

11 <!-- =====================================================fieldID="16.008" fieldMnemonic="SLC" =

12 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 13 <!-- =====================================================fieldID="16.007" fieldMnemonic="VLL" == 

14 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 15 <!-- =====================================================fieldID="16.010" fieldMnemonic="VPS" =

16 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 17 </itl:TestImage> 18 </itl:PackageUserDefinedTestingImageRecord> 19 20 <!-- ========================================================================================21 <!-- RECORD TYPE 17 Iris Image 22 <!-- ========================================================================================23 <itl:PackageIrisImageRecord> 

24 <ansi-nist:RecordCategoryCode>17</ansi-nist:RecordCategoryCode> 

25 <!-- ====================================================== fieldID="17.002" fieldMnemonic="IDC" == 

26 <ansi-nist:ImageReferenceIdentification> 27 <nc:IdentificationID>15</nc:IdentificationID> 

28 </ansi-nist:ImageReferenceIdentification> 

29 <!-- =================================================== fieldID="17.200-998" fieldMnemonic="UDF" =

30 <itl:ExampleUserDefinedFields> 31 <!-- Well-formed XML goes here. Users may define a substitute element. --> 32 </itl:ExampleUserDefinedFields> 33 <itl:IrisImage> 34 <!-- =====================================================fieldID="17.999" fieldMnemonic="DATA" 35 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

36 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 37 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 
Part 2 – Annex F 

233

1 <!-- =====================================================fieldID="17.012" fieldMnemonic="BPX" =2 <ansi-nist:ImageBitsPerPixelQuantity>8</ansi-nist:ImageBitsPerPixelQuantity> 3 <ansi-nist:ImageCaptureDetail> 4 <!-- =====================================================fieldID="17.005" fieldMnemonic="ICD" 5 <ansi-nist:CaptureDate> 6 <nc:Date>1953-04-23</nc:Date> 7 </ansi-nist:CaptureDate> 8 <!-- =====================================================fieldID="17.022" fieldMnemonic="SHP9 <ansi-nist:CaptureHorizontalPixelDensityValue>500</ansi-nist:CaptureHorizontalPixelDensityValue> 

10 <!-- =====================================================fieldID="17.004" fieldMnemonic="SRC11 <ansi-nist:CaptureOrganization> 12 <nc:OrganizationIdentification> 13 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 14 </nc:OrganizationIdentification> 15 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 16 </ansi-nist:CaptureOrganization> 17 <!-- =====================================================fieldID="17.023" fieldMnemonic="SVP

18 <ansi-nist:CaptureVerticalPixelDensityValue>500</ansi-nist:CaptureVerticalPixelDensityValue> 

19 <!-- =====================================================fieldID="17.030" fieldMnemonic="DMM20 <ansi-nist:CaptureDeviceMonitoringModeCode>ASSISTED</ansi-nist:CaptureDeviceMonitoringModeCode> 21 </ansi-nist:ImageCaptureDetail> 22 <!-- =====================================================fieldID="17.013" fieldMnemonic="CSP" =

23 <ansi-nist:ImageColorSpaceCode>YCC</ansi-nist:ImageColorSpaceCode> 

24 <!-- =====================================================fieldID="17.021" fieldMnemonic="COM" =

25 <ansi-nist:ImageCommentText>Comment</ansi-nist:ImageCommentText> 

26 <!-- =====================================================fieldID="17.011" fieldMnemonic="CGA" =27 <ansi-nist:ImageCompressionAlgorithmText>JPEGB</ansi-nist:ImageCompressionAlgorithmText> 

28 <!-- =====================================================fieldID="17.006" fieldMnemonic="HLL" =

29 <ansi-nist:ImageHorizontalLineLengthPixelQuantity>80</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

30 <!-- =====================================================fieldID="17.009" fieldMnemonic="HPS" =31 <ansi-nist:ImageHorizontalPixelDensityValue>1200</ansi-nist:ImageHorizontalPixelDensityValue> 32 <!-- =====================================================fieldID="17.024" fieldMnemonic="IQS" == 33 <ansi-nist:ImageQuality> 34 <ansi-nist:QualityAlgorithmProductIdentification> 35 <nc:IdentificationID>28495</nc:IdentificationID> 

36 </ansi-nist:QualityAlgorithmProductIdentification> 

37 <ansi-nist:QualityValue>100</ansi-nist:QualityValue> 
Part 2 – Annex F 

234

1 <ansi-nist:QualityMeasureVendorIdentification> 

2 <nc:IdentificationID>FFF0</nc:IdentificationID> 3 </ansi-nist:QualityMeasureVendorIdentification> 4 </ansi-nist:ImageQuality> 

5 <!-- =====================================================fieldID="17.008" fieldMnemonic="SLC" =

6 <ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

7 <!-- =====================================================fieldID="17.007" fieldMnemonic="VLL" == 

8 <ansi-nist:ImageVerticalLineLengthPixelQuantity>65</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

9 <!-- =====================================================fieldID="17.010" fieldMnemonic="VPS" =

10 <ansi-nist:ImageVerticalPixelDensityValue>1200</ansi-nist:ImageVerticalPixelDensityValue> 11 <!-- =====================================================fieldID="17.003" fieldMnemonic="FID" == 12 <ansi-nist:IrisEyePositionCode>2</ansi-nist:IrisEyePositionCode> 13 <!-- =====================================================fieldID="17.014" fieldMnemonic="RAE" =14 <ansi-nist:IrisEyeRotationAngleMeasure>8192</ansi-nist:IrisEyeRotationAngleMeasure> 15 <!-- =====================================================fieldID="17.015" fieldMnemonic="RAU" =16 <ansi-nist:IrisEyeRotationUncertaintyValueText>FFFF</ansi-nist:IrisEyeRotationUncertaintyValueText> 17 <ansi-nist:IrisImageCapture> 18 <!-- =====================================================fieldID="17.018" fieldMnemonic="GUI" 

19 <ansi-nist:CaptureDeviceGlobalIdentification> 

20 <nc:IdentificationID>A2849B293059C200</nc:IdentificationID> 

21 </ansi-nist:CaptureDeviceGlobalIdentification> 

22 <!-- =====================================================fieldID="17.017" fieldMnemonic="DUI" 

23 <ansi-nist:CaptureDeviceIdentification> 

24 <nc:IdentificationID>P270NEIS67830000</nc:IdentificationID> 25 </ansi-nist:CaptureDeviceIdentification> 

26 <!-- =====================================================fieldID="17.019" fieldMnemonic="MMS27 <ansi-nist:CaptureDeviceMakeText>RGT88</ansi-nist:CaptureDeviceMakeText> 

28 <ansi-nist:CaptureDeviceModelText>PEARL</ansi-nist:CaptureDeviceModelText> 

29 <ansi-nist:CaptureDeviceSerialNumberText>2838590029395784-4</ansi-nist:CaptureDeviceSerialNumberText> 

30 <!-- =====================================================fieldID="17.016" fieldMnemonic="IPC" 

31 <ansi-nist:IrisImageHorizontalOrientationCode>2</ansi-nist:IrisImageHorizontalOrientationCode> 

32 <ansi-nist:IrisImageScanCategoryCode>3</ansi-nist:IrisImageScanCategoryCode> 

33 <ansi-nist:IrisImageVerticalOrientationCode>1</ansi-nist:IrisImageVerticalOrientationCode> 34 </ansi-nist:IrisImageCapture> 

35 <!-- =====================================================fieldID="17.020" fieldMnemonic="ECL" =36 <ansi-nist:IrisEyeColorAttributeCode>MUL</ansi-nist:IrisEyeColorAttributeCode> 37 <!-- =====================================================fieldID="17.025" fieldMnemonic="ALS" =
Part 2 – Annex F 

235

1 <ansi-nist:IrisImageAcquisitionLightingSpectrumValue>VIS</ansi-nist:IrisImageAcquisitionLightingSpectrumValue> 

2 <!-- =====================================================fieldID="17.026" fieldMnemonic="IRD" == 3 <itl:IrisDiameterPixelQuantity>304</itl:IrisDiameterPixelQuantity> 4 </itl:IrisImage> 5 </itl:PackageIrisImageRecord> 6 7 <!-- ========================================================================================

8 <!-- RECORD TYPE 99 CBEFF Data 9 <!-- ========================================================================================

10 <itl:PackageCBEFFBiometricDataRecord> 

11 <ansi-nist:RecordCategoryCode>99</ansi-nist:RecordCategoryCode> 

12 <!-- ====================================================== fieldID="99.002" fieldMnemonic="IDC" == 

13 <ansi-nist:ImageReferenceIdentification> 14 <nc:IdentificationID>16</nc:IdentificationID> 

15 </ansi-nist:ImageReferenceIdentification> 

16 <!-- =================================================== fieldID="99.200-998" fieldMnemonic="UDF" =17 <itl:ExampleUserDefinedFields> 18 <!-- Well-formed XML goes here. Users may define a substitute element. --> 19 </itl:ExampleUserDefinedFields> 20 <ansi-nist:CBEFFImage> 21 <!-- =====================================================fieldID="99.999" fieldMnemonic="BDB" =22 <nc:BinaryBase64Object>mrHbPdrko3u1s7ahtgPBjtmO1s85tfG2U7bpofY9 

23 4Czu2SbY7d7wF9fQ7ZptgGrtkO2a2dsJ7wZbe 8BlzvAmQ7xq+Y94GoHeEsR3ikWd4DIGhzmp3k42 24 d4DRmzs94DKveDTB3hqw6PeBLrtpPep0H/+h</nc:BinaryBase64Object> 25 <ansi-nist:ImageCaptureDetail> 

26 <!-- =====================================================fieldID="99.005" fieldMnemonic="BCD27 <ansi-nist:CaptureDate> 

28 <nc:DateTime>2005-11-05T05:25:00Z</nc:DateTime> 29 </ansi-nist:CaptureDate> 

30 <!-- =====================================================fieldID="99.004" fieldMnemonic="SRC31 <ansi-nist:CaptureOrganization> 32 <nc:OrganizationIdentification> 

33 <nc:IdentificationID>WI013415Y</nc:IdentificationID> 34 </nc:OrganizationIdentification> 35 <nc:OrganizationName>WI Crime Information Bureau</nc:OrganizationName> 36 </ansi-nist:CaptureOrganization> 37 </ansi-nist:ImageCaptureDetail> 
Part 2 – Annex F 

236

1 <!-- =====================================================fieldID="99.102" fieldMnemonic="BDQ" =2 <ansi-nist:ImageQuality> 3 <ansi-nist:QualityAlgorithmProductIdentification> 

4 <nc:IdentificationID>28495</nc:IdentificationID> 

5 </ansi-nist:QualityAlgorithmProductIdentification> 6 <ansi-nist:QualityValue>49</ansi-nist:QualityValue> 

7 <ansi-nist:QualityMeasureVendorIdentification> 

8 <nc:IdentificationID>FFF0</nc:IdentificationID> 9 </ansi-nist:QualityMeasureVendorIdentification> 

10 </ansi-nist:ImageQuality> 

11 <!-- =====================================================fieldID="99.103" fieldMnemonic="BFO" =12 <ansi-nist:CBEFFFormatOwnerIdentification> 

13 <nc:IdentificationID>001B</nc:IdentificationID> 14 </ansi-nist:CBEFFFormatOwnerIdentification> 

15 <!-- =====================================================fieldID="99.104" fieldMnemonic="BFT" =16 <ansi-nist:CBEFFFormatCategoryIdentification> 

17 <nc:IdentificationID>000A</nc:IdentificationID> 18 </ansi-nist:CBEFFFormatCategoryIdentification> 

19 <!-- =====================================================fieldID="99.100" fieldMnemonic="HDV" =20 <ansi-nist:CBEFFVersionIdentification> 

21 <nc:IdentificationID>0101</nc:IdentificationID> 22 </ansi-nist:CBEFFVersionIdentification> 

23 <!-- =====================================================fieldID="99.101" fieldMnemonic="BTY" =24 <ansi-nist:CBEFFCategoryCode>00000200</ansi-nist:CBEFFCategoryCode> 25 </ansi-nist:CBEFFImage> 26 </itl:PackageCBEFFBiometricDataRecord> 27 </itl:NISTBiometricInformationExchangePackage> 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

237 

Annex G INCITS / M1 378 Minutiae Format 

(Informative) 

Minutia placement and type 

For templates to be conformant with Section 5 of the ANSI INCITS 378-2004 standard, the following method, which 

enhances the current INCITS 378-2004 standard, shall be used for determining placement (location and angular direction) 

of individual minutiae. 

The position or location of a minutia representing a ridge ending shall be the point of forking of the medial skeleton of the 

valley area immediately in front of the ridge ending. If the three legs of the valley area were thinned down to a singlepixel-wide skeleton, the point of the intersection is the location of the minutia. Similarly, the location of the minutia for a 

bifurcation shall be the point of forking of the medial skeleton of the ridge. If the three legs of the ridge were each thinned 

down to a single-pixel-wide skeleton, the point where the three legs intersect is the location of the minutia. 

After all ridge endings have been converted to bifurcations, all of the minutiae of the fingerprint image are represented as 

bifurcations. The X and Y pixel coordinates of the intersection of the three legs of each minutia can be directly formatted. 

Determination of the minutia direction can be extracted from each skeleton bifurcation. The three legs of every skeleton 

bifurcation must be examined and the endpoint of each leg determined. Figure G1 illustrates the three methods used for 

determining the end of a leg that is based on a scanning resolution of 500 ppi. The ending is established according to the 

event that occurs first. The pixel count is based on a scan resolution of 500 ppi. Different scan resolutions would imply 

different pixel counts. 

• A distance of .064” (the 32nd pixel) 

• The end of skeleton leg that occurs between a distance of .02” and .064” (the 10th through the 32nd pixels); shorter 

legs are not used 

• A second bifurcation is encountered within a distance of .064” (before the 32nd pixel) 

Figure G1 Minutiae angle components 

The angle of the minutiae is determined by constructing three virtual rays originating at the bifurcation point and extending 

to the end of each leg. The smallest of the three angles formed by the rays is bisected to indicate the minutiae direction. 

32 pixels 

<32 pixels 32 pixels

32 pixels
Part 2 – Annex G ANSI/NIST-ITL 2-2008

238

Coordinate system 

The coordinate system used to express the minutiae of a fingerprint shall be a Cartesian coordinate system. Minutiae 

locations shall be represented by their x and y coordinates. The origin of the coordinate system shall be the upper left 

corner of the original image with x increasing to the right and y increasing downward. Both x and y coordinates of a 

minutiae shall be represented in pixel units from the origin. It should be noted that the location of the origin and units of 

measure is not in agreement with the convention used in the “standard format” definitions of Section 214.1. 

Minutiae direction 

Angles are expressed in standard mathematical format, with zero degrees to the right and angles increasing in the 

counterclockwise direction. Recorded angles are in the direction pointing back along the ridge for a ridge ending and 

toward the center of the valley for a bifurcation. This convention is 180 degrees opposite of the angle convention 

described in the “standard format” definitions of Section 214.1.4. 

XML elements for Type-9 logical record INCITS-378 Format 

For purposes of this standard, no proprietary information shall be contained in any of the information and data specified by 

the M1-378 block of information items. Therefore, the following descriptions are presented for each of the elements in this 

Type-9 block. All elements of the Type-9 records shall be recorded as ASCII text. No binary content is permissible in this 

record. 

The first four elements of the Type-9 record are mandatory and retain the same meaning as described in Sections 214.2.2 

through 214.2.5. The description of those elements is not repeated here. In the Part 2 XML version of the Type-9 record, 

a minutiae representation other than the NIST “standard format” is implemented as substitution element for the abstract 

element <itl:RecordMinutiae>. This Annex defines a substitution element. 

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 <ansi-nist:CBEFFFormatOwnerIdentification>, for 

example). 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

239

Table G201 Type-9 INCITS-378 minutiae representation 

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 

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 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

240

Part 1 

Ident

Cond 

code 

Part 1 

Field 

Number 

Part 2 XML Element Name IMG Occur count 

 min Max 

 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 

 M <ansi-nistPositionThetaAngleMeasure> 1 1 

224.1.1 Element <incits:Minutiae> 

Complex element <itl:RecordMinutiae> is abstract, and as such is unusable by itself. This Annex defines a specific, 

concrete substitution element named <incits:Minutiae>. 

This substitution element may be defined in an extension schema similar to this, using “incits:” as the namespace. 

<xsd:element name="Minutiae" 

 substitutionGroup="itl:RecordMinutiae" 

 type="incits:MinutiaeType"/> 

<xsd:complexType name="MinutiaeType"> 

 <xsd:complexContent> 

 <xsd:extension base="s:ComplexObjectType"> 

 <xsd:sequence> 

[ Content defined in schema for this Annex ] 

 </xsd:sequence> 

 </xsd:extension> 

 </xsd:complexContent> 

</xsd:complexType> 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

241

The element would then appear in an instance document like this: 

<incits:Minutiae> 

[ Content defined in instance example for this Annex ] 

</incits:Minutiae> 

The complex element <incits:Minutiae> has been defined as a concrete substitution for the abstract element 

<itl:RecordMinutiae>. It contains the INCITS/M1 378 Minutiae Format content for representation of minutiae. All of the 

elements in this format are nested within, as described in the subsections below. 

<incits:Minutiae> 

[. . . INCITS/M1 378 minutiae elements . . .] 

</incits:Minutiae> 

Element <ansi-nist:CBEFFFormatOwnerIdentification> 

Cross-reference: Part 1, Annex G Field 9.126: CBEFF information, owner item 

This mandatory element shall contain the value "27". This is the identification of the CBEFF Format Owner assigned by 

the International Biometric Industry Association (IBIA) to INCITS Technical Committee M1. 

Complex element <ansi-nist:CBEFFFormatOwnerIdentification> shall have the simple element <nc:IdentificationID>, 

which will contain the four hex digits assigned by IBIA represented by a string of four ASCII characters. 

<ansi-nist:CBEFFFormatOwnerIdentification> 

 <nc:IdentificationID>FFF0</nc:IdentificationID> 

</ansi-nist:CBEFFFormatOwnerIdentification> 

Element <ansi-nist:CBEFFFormatCategoryIdentification> 

Cross-reference: Part 1, Annex G Field 9.126: CBEFF information, type item 

This mandatory element shall contain the CBEFF Format Type that is assigned a value of "513" to indicate that this record 

contains only location and angular direction data without any Extended Data Block information. A value of “514” indicates 

the presence of extended data. 

Complex element <ansi-nist:CBEFFFormatCategoryIdentification> shall have the simple element <nc:IdentificationID>, 

which will contain the required value. 

<ansi-nist:CBEFFFormatCategoryIdentification> 

 <nc:IdentificationID>513</nc:IdentificationID> 

</ansi-nist:CBEFFFormatCategoryIdentification> 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

242

Element <incits:CBEFFProductIdentification> 

Cross-reference: Part 1, Annex G Field 9.126: CBEFF information, product item 

This mandatory element shall contain the CBEFF Product Identifier (PID) that identifies the "owner" of the encoding 

equipment. The vendor establishes this value. It can be obtained from the IBIA website (www.ibia.org) if it is posted. 

Complex element <incits:CBEFFProductIdentification> shall have the simple element <nc:IdentificationID>, which will 

contain the required value. 

<incits:CBEFFProductIdentification> 

 <nc:IdentificationID>RG88</nc:IdentificationID> 

</incits:CBEFFProductIdentification> 

Element <incits:FingerprintImageCapture> 

Cross-reference: Part 1, Annex G Field 9.127: Capture equipment identification 

This mandatory element shall contain two child elements. 

The child element <incits:CaptureDeviceCertificationText> shall contain "APPF" if the equipment used originally to 

acquire the image was certified to conform with Appendix F (IAFIS Image Quality Specification, January 29, 1999) of 

CJIS-RS-0010, the Federal Bureau of Investigation's Electronic Fingerprint Transmission Specification. If the equipment 

did not conform, it will contain the value of "NONE". 

The child element <ansi-nist:CaptureDeviceIdentification> shall contain the Capture Equipment ID, which is a vendorassigned product number of the capture equipment. A value of "0" indicates that the capture equipment ID is unreported. 

Complex element <ansi-nist:CaptureDeviceIdentification> shall have the simple element <nc:IdentificationID>, which will 

contain the required value. 

<incits:FingerprintImageCapture> 

<incits:CaptureDeviceCertificationText>APPF

</incits:CaptureDeviceCertificationText> 

<incits:CaptureDeviceIdentification> 

 <nc:IdentificationID>SCANR88</nc:IdentificationID> 

</incits:CaptureDeviceIdentification> 

</incits:FingerprintImageCapture> 

Element <ansi-nist:NISTImage> 

This mandatory element shall contain five mandatory child elements. 

Cross-reference: Part 1, Annex G Field 9.128: Horizontal line length (HLL) 

The mandatory child element <ansi-nist:ImageHorizontalLineLengthPixelQuantity> shall contain the number of pixels 

contained on a single horizontal line of the transmitted image. The maximum horizontal size is limited to 65,534 pixels. 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

243

Cross-reference: Part 1, Annex G Field 9.131: Horizontal pixel scale (HPS) 

The mandatory child element <ansi-nist:ImageHorizontalPixelDensityValue> shall specify the integer pixel density used in 

the horizontal direction providing the <ansi-nist:ImageScaleUnitsCode> (SLC) element contains a "1" or a "2". Otherwise, 

it indicates the horizontal component of the pixel aspect ratio. 

Cross-reference: Part 1, Annex G Field 9.130: Scale units (SLC) 

The mandatory child element <ansi-nist:ImageScaleUnitsCode> 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 centimeter. 

A "0" in this element indicates no scale is given. For this case, the quotient of HPS/VPS gives the pixel aspect ratio. 

Cross-reference: Part 1, Annex G Field 9.129: Vertical line length (VLL) 

The mandatory child element <ansi-nist:ImageVerticalLineLengthPixelQuantity> shall contain the number of horizontal 

lines contained in the transmitted image. The maximum vertical size is limited to 65,534 pixels. 

Cross-reference: Part 1, Annex G Field 9.132: Vertical pixel scale (VPS) 

The mandatory child element <ansi-nist:ImageVerticalPixelDensityValue> shall specify the integer pixel density used in 

the vertical direction providing the <ansi-nist:ImageScaleUnitsCode> (SLC) element contains a "1" or a "2". Otherwise, it 

indicates the vertical component of the pixel aspect ratio. 

<ansi-nist:NISTImage> 

<ansi-nist:ImageHorizontalLineLengthPixelQuantity>80

</ansi-nist:ImageHorizontalLineLengthPixelQuantity> 

<ansi-nist:CaptureHorizontalPixelDensityValue>1200

</ansi-nist:CaptureHorizontalPixelDensityValue> 

<ansi-nist:ImageScaleUnitsCode>1</ansi-nist:ImageScaleUnitsCode> 

<ansi-nist:ImageVerticalLineLengthPixelQuantity>65

</ansi-nist:ImageVerticalLineLengthPixelQuantity> 

<ansi-nist:ImageVerticalPixelDensityValue>1200

</ansi-nist:ImageVerticalPixelDensityValue> 

</ansi-nist:NISTImage> 

Element <incits:FingerViewCode> 

Cross-reference: Part 1, Annex G Field 9.133: Finger view 

This mandatory element contains the view number of the finger associated with this record's data. The view number 

begins with "0" and increments by one to "15". 

<incits:FingerViewCode>12</incits:FingerViewCode> 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

244

Element <ansi-nist:FingerPositionCode> or <ansi-nist:PalmPositionCode> 

Cross-reference: Part 1, Annex G Field 9.134: Finger position 

This mandatory element shall contain the code designating the finger position that produced the information in this Type-9 

record. A code between 1 and 10 taken from Table 212 shall be used to indicate the finger position. 

<ansi-nist:FingerPositionCode>12</ansi-nist:FingerPositionCode> 

Element <incits:MinutiaeQuality> 

Cross-reference: Part 1, Annex G Field 9.135: Finger quality 

This mandatory complex element shall contain the quality of the overall finger minutiae data in three child elements. They 

identify a quality score and the algorithm used to create the 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 processing or analysis as necessary. 

The child element <ansi-nist:QualityAlgorithmProductIdentification> shall contain a numeric product code assigned by the 

vendor of the quality algorithm, which may be registered with the IBIA, but it is not required to be registered. It 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 should be within the range 1 to 65535. Complex element <ansinist:QualityAlgorithmProductIdentification> shall have the simple element <nc:IdentificationID>, which will contain the 

identification datum. 

The child element <ansi-nist:QualityValue> shall contain a quantitative expression of the 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 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 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. 

The child element <ansi-nist:QualityMeasureVendorIdentification> shall contain 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 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. Complex element <ansi-nist:QualityMeasureVendorIdentification> shall have the 

simple element <nc:IdentificationID>, which will contain the identification datum. 

<incits:MinutiaeQuality> 

<ansi-nist:QualityAlgorithmProductIdentification> 

<nc:IdentificationID>28488</nc:IdentificationID> 

</ansi-nist:QualityAlgorithmProductIdentification> 

<ansi-nist:QualityValue>100

</ansi-nist:QualityValue> 

<ansi-nist:QualityMeasureVendorIdentification> 

<nc:IdentificationID>FFF0</nc:IdentificationID> 

</ansi-nist:QualityMeasureVendorIdentification> 

</incits:MinutiaeQuality> 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

245

Element <ansi-nist:MinutiaeQuantity> 

Cross-reference: Part 1, Annex G Field 9.136: Number of minutiae 

The mandatory element shall contain a count of the number of minutiae recorded in this logical record. 

<ansi-nist:MinutiaeQuantity>4</ansi-nist:MinutiaeQuantity> 

Element <itl:MinutiaDetail> 

Cross-reference: Part 1, Annex G Field 9.137: Finger minutiae data 

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 

the count found in <ansi-nist:MinutiaeQuantity> (field 136). 

The child element <ansi-nist:PositionHorizontalCoordinateValue> shall contain the 'x' coordinate of the minutia in pixel 

units. 

The child element <ansi-nist:PositionVerticalCoordinateValue> shall contain the 'y' coordinate of the minutia in pixel units. 

The child element <ansi-nist:MinutiaIdentification> shall contain the minutiae index number, which shall be initialized to “1” 

and incremented by “1” for each additional minutia in the fingerprint. Complex element <ansi-nist:MinutiaIdentification> 

shall have the simple element <nc:IdentificationID>, which will contain the identification datum. 

The child element <ansi-nist:PositionThetaAngleMeasure> shall contain the minutiae angle recorded in units of two 

degrees. This value shall be nonnegative between 0 and 179. 

The child element <incits:MinutiaQualityValue> shall contain the quality of each minutiae. This value shall range from 1 

as a minimum to 100 as a maximum. A value of "0" indicates that no quality value is available. 

The child element <incits:MinutiaCategoryCode> shall contain the minutiae type. A value of "0" is used to represent a 

minutiae of type "OTHER", a value of "1" for a ridge ending, and a value of "2" for a ridge bifurcation. 

<itl:MinutiaDetail> 

<ansi-nist:PositionHorizontalCoordinateValue>0486

</ansi-nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>2839

</ansi-nist:PositionVerticalCoordinateValue> 

<ansi-nist:MinutiaIdentification> 

<nc:IdentificationID>00</nc:IdentificationID> 

</ansi-nist:MinutiaIdentification> 

<ansi-nist:PositionThetaAngleMeasure>048

</ansi-nist:PositionThetaAngleMeasure> 

<ansi-nist:MinutiaQualityValue>100

</ansi-nist:MinutiaQualityValue> 

<incits:MinutiaCategoryCode>2

</incits:MinutiaCategoryCode> 

</itl:MinutiaDetail>
Part 2 – Annex G ANSI/NIST-ITL 2-2008

246

Element <incits:RidgeCountExtractionMethodCode> 

Cross-reference: Part 1, Annex G Field 9.138: Ridge count information, first information item 

This element shall indicate the ridge count extraction method. A “0” indicates that no assumption shall be made about the 

method used to extract ridge counts, nor their order in the record. A “1” indicates that for each center minutiae, ridge 

count data was extracted to the nearest neighboring minutiae in four quadrants, and ridge counts for each center minutia 

are listed together. A “2” indicates that for each center minutiae, ridge count data was extracted to the nearest 

neighboring minutiae in eight octants, and ridge counts for each center minutia are listed together. 

<incits:RidgeCountExtractionMethodCode>1 

</incits:RidgeCountExtractionMethodCode> 

Element <incits:RidgeCountDetail> 

Cross-reference: Part 1, Annex G Field 9.138: Ridge count information 

This complex element shall consist of three child elements. The complex element <incits:RidgeCountDetail> shall have 

multiple occurrences, one for each ridge count value reported. 

The child element <ansi-nist:MinutiaIdentification> will contain the center minutiae index number. Complex element 

<ansi-nist:MinutiaIdentification> shall have the simple element <nc:IdentificationID>, which will contain the identification 

datum. 

The child element <ansi-nist:RidgeCountReferenceIdentification> will contain the neighboring minutiae index number. 

Complex element <ansi-nist:RidgeCountReferenceIdentification> shall have the simple element <nc:IdentificationID>, 

which will contain the identification datum. 

The child element <ansi-nist:RidgeCountValue> will contain the number of ridges crossed. 

<incits:RidgeCountDetail> 

<ansi-nist:MinutiaIdentification> 

<nc:IdentificationID>1</nc:IdentificationID> 

</ansi-nist:MinutiaIdentification> 

<ansi-nist:RidgeCountReferenceIdentification> 

<nc:IdentificationID>2</nc:IdentificationID> 

</ansi-nist:RidgeCountReferenceIdentification> 

<ansi-nist:RidgeCountValue>6

 </ansi-nist:RidgeCountValue> 

</incits:RidgeCountDetail> 

Element <incits:MinutiaeFingerCorePosition> 

Cross-reference: Part 1, Annex G Field 9.139: Core information 

This element may have multiple occurrences, one for each core present in the original image. This element shall have 

three child elements. 

The child element <ansi-nist:PositionHorizontalCoordinateValue> contains the ‘x’ coordinate position in pixel units. 

The child element <ansi-nist:PositionVerticalCoordinateValue> contains the ‘y’ coordinate position in pixel units. 
Part 2 – Annex G ANSI/NIST-ITL 2-2008

247

The child element <ansi-nist:PositionThetaAngleMeasure> contains the angle of the core recorded in units of 2 degrees. 

The value shall be a nonnegative value between 0 and 179. 

<incits:MinutiaeFingerCorePosition> 

<ansi-nist:PositionHorizontalCoordinateValue>0035

</ansi-nist:PositionHorizontalCoordinateValue> 

<ansi-nist:PositionVerticalCoordinateValue>0045

</ansi-nist:PositionVerticalCoordinateValue> 

<ansi-nist:PositionThetaAngleMeasure>0045

</ansi-nist:PositionThetaAngleMeasure> 

</incits:MinutiaeFingerCorePosition> 

Element <incits:MinutiaeFingerDeltaPosition> 

Cross-reference: Part 1, Annex G Field 9.140: Delta information 

This element may have multiple occurrences, one for each delta present in the original image. This element shall have 

three child elements. 

The child element <ansi-nist:PositionHorizontalCoordinateValue> contains the ‘x’ coordinate position in pixel units. 

The child element <ansi-nist:PositionVerticalCoordinateValue> contains the ‘y’ coordinate position in pixel units. 

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> 
Part 2 – Annex H ANSI/NIST-ITL 2-2008

248 

Annex H Best Practice Application Level 30 

(Informative) 

BEST PRACTICE RECOMMENDATION 

FOR THE CAPTURE OF MUGSHOTS 

Version 2.0 

September 23, 1997 

The original version of the “Best Practice Recommendation” was initiated at the Mugshot and Facial Image Workshop which was 

held in Gaithersburg, MD on October 23-25, 1995. Developed as a recommendation, the implementation of the practices and 

principles described in that document makes the conversion of existing and ongoing photographic collections more uniform. It 

contains a suggested set of procedures and equipment specifications for organizations considering the purchase of new systems or the 

upgrade of current systems. The recommendation is not designed to render current and legacy mugshot collections unacceptable. 

Rather, it is intended as a means of establishing or improving interoperability between mugshot systems. 

The information contained in this updated revision of the “Best Practice Recommendation,” Version 2.0, does not alter any of the 

individual points that were consensually agreed upon and included in the original version of this recommendation. It does provide 

additional details and clarifications for many of those points and has been supplemented with information regarding depth-of-field 

and exposure considerations. 

This recommendation reflects a minimum set of common denominators. The provisions of this recommendation are keyed to the 

quality aspects associated with the unaltered captured mugshot image. For new mugshot images being captured, the specifications 

contained in this recommendation are equally applicable to realtime electronic capture of mugshots as well as the electronic 

conversion of photographic images. For conversion of legacy files of photographs, most of the provisions of this recommendation are 

also still applicable. In the future, it should be possible to add additional specifications without contradicting any of the current 

contents of the recommendation. 

* POSE 

The full-face or frontal pose is the most commonly used pose in photo lineups and shall always be captured. This pose is in 

addition to profiles or intermediate angled poses captured to acquire perspective and other information. For subjects who 

normally wear eyeglasses, a frontal mugshot image should be captured of the subject without glasses. This is required due to 

the glare from exernal illumination. An additional image can optionally be captured of the subject wearing eyeglasses. 
Part 2 – Annex H ANSI/NIST-ITL 2-2008

249

* DEPTH OF FIELD 

The subject’s captured facial image shall always be in focus from the nose to the ears. Although this may result in the 

background behind the subject being out of focus, it is not a problem. For optimum quality of the captured mugshot, the fstop of the lens should be set at two f-stops below the maximum aperture opening when possible. 

* CENTERING 

The facial image being captured (full-face pose) shall be positioned to satisfy all of the following conditions: 

- The approximate horizontal mid-points of the mouth and of the bridge of the nose shall lie on an imaginary vertical 

straight line positioned at the horizontal center of the image. 

- An imaginary horizontal line through the center of the subject's eyes shall be located at approximately the 55% point 

of the vertical distance up from the bottom edge of the captured image. 

- The width of the subject's head shall occupy approximately 50% of the width of the captured image. This width 

shall be the horizontal distance between the mid-points of two imaginary vertical lines. Each imaginary line shall 

be drawn between the upper and lower lobes of each ear and shall be positioned where the external ear connects to 

the head. 

* LIGHTING 

Subject illumination shall be accomplished using a minimum of three (3) point balanced illumination. Appropriate diffusion 

techniques shall also be employed and lights positioned to minimize shadows, and to eliminate hot spots on the facial image. 

These hot spots usually appear on reflective areas such as cheeks and foreheads. Proper lighting shall contribute to the 

uniformity of illumination of the background described in the exposure requirement. 

* BACKGROUND 

The subject whose image is being captured shall be positioned in front of a background which is 18% gray with a plain 

smooth flat surface. A Kodak or other neutral gray card or densitometer shall be used to verify this 18% gray reflectance 

requirement. 

* EXPOSURE 

The exposure shall be keyed to the background. Several areas of the recorded 18% gray background shall be used to verify 

the proper exposure. The averages of the 8-bit Red, Green, and Blue (RGB) components within each area shall be 

calculated. Each of the RGB means shall fall between 105 and 125 with a standard deviation of plus or minus 10. 

Furthermore, for every area examined, the maximum difference between the means of any two of the RGB components 

shall not exceed 10. 

* ASPECT RATIO 

The Width:Height aspect ratio of the captured image shall be 1:1.25. 

* MINIMUM NUMBER OF PIXELS 

The minimum number of pixels in an electronic digital image shall be 480 pixels in the horizontal direction by 600 pixels in 

the vertical direction. It should be noted that the image quality of the captured mugshots and facial images will be improved 
Part 2 – Annex H ANSI/NIST-ITL 2-2008

250

as the number of pixels in both directions are increased. However, as images are captured with an increased number of 

pixels, the 1:1.25 (Width:Height) aspect ratio will be maintained. 

Two considerations must be noted regarding this aspect of the recommendation. First, the normal orientation of many available 

cameras is the landscape format which specifies a greater number of pixels in the horizontal than in the vertical direction. Unless 

these cameras capture at least 600 pixels in the vertical direction, it may be necessary to rotate the camera 90 degrees. Second, the 

480x600 capture format exceeds the VGA display format of 640x480. Therefore, at a minimum, an SVGA specification of 800x600 

pixels will be required to display the facial image. The image will occupy less than the total number of available horizontal pixels. 

* COLOR SPACE 

Captured electronic color facial images are required. Digital images shall be represented as 24-bit RGB pixels. For every 

pixel, eight (8) bits will be used to represent each of the Red, Green, and Blue components. The RGB color space is the basis 

for other color spaces including the Y, Cb, Cr and YUV. Additional color management techniques are available from the 

International Color Consortium. Information regarding these techniques can be downloaded from the following URL: 

http://www.color.org . 

* PIXEL ASPECT RATIO 

Digital cameras and scanners used to capture facial images shall use square pixels with a pixel aspect ratio of 1:1. 

* COMPRESSION ALGORITHM 

The algorithm used to compress mugshot and facial images shall conform to the JPEG Sequential Baseline mode of operation 

as described in the specification approved by the ANSI X3L3 Standards committee. The target size for a JPEG compressed 

color mugshot image file shall be 25,000 to 45,000 bytes. 

* FILE FORMAT 

The JPEG File Interchange Format (JFIF) shall contain the JPEG compressed image data. The JFIF file shall then be part of 

the transaction file for interchange which conforms to the requirements as contained in ANSI/NIST-CSL 1-1993 and 

ANSI/NIST-ITL 1a-1997. 
Part 2 – Annex I ANSI/NIST-ITL 2-2008

251 

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

(Informative) 

Introduction 

This set of “enhanced best practice recommendation” (EBPR) clauses is a set of constraints. These constraints can be 

categorized into four types of requirements: scene, photographic, digital, and format. Scene requirements refer to the 

content, subject and background in the image. Photographic requirements refer to lighting, focus and other constraints 

required for photo capture. Digital requirements refer to the conversion of the captured image into a digital record. Finally,

format requirements refer to additional or conditional required fields and in a Type-10 record or NIST transaction. 

Note that the set of requirements applies to all poses of a subject. 

Scene Requirements 

Number of photographs

Level 50 and 51 records shall include at least five photographs of the subject: frontal, left and right profile, and left and 

right 3⁄4 profile. 

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 

Section 215.1.5.12, “Element <ansi-nist:FaceImage3DPoseAngle>, Cross-reference: Part 1, Section 15.1.23 Field 

10.025: Subject pose angles (SPA)”). Note that for 3⁄4 profile, the 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 prevent the subject from keeping the head fixed while 

changing only the gaze. In addition, for 3⁄4 profile photographs, both eyes must be visible in the image. For full profile 

images, the entire body shall be rotated with the head. 

The “Head and Shoulders” photo composition

The composition consists of a subject’s head, partial shoulders, and plain background. For a frontal-facing pose, the 

width of the subject's head shall occupy approximately 50% of the width of the captured image. This width shall be the 

horizontal distance between the mid-points of two imaginary vertical lines. Each imaginary line shall be drawn between 

the upper and lower lobes of each ear and shall be positioned where the external ear connects to the head. A template 

and an example are shown in Figure I1. For other poses, the composition shall be rotated about an imaginary axis 

extending from the top of the head though the base of the neck. 

This composition is applied to SAP levels 30, 40, and 50. 
Part 2 – Annex I ANSI/NIST-ITL 2-2008

252

a. A template of the “head and 

shoulders” photo. The width of the 

head is 1⁄2 the width of the photo. 

b. An example “head and 

shoulders” photo. 

Figure I1 – A facial image template and an example image that meets “Head and Shoulders” (levels 40 and 50) 

scene constraints. 

The “Head Only” photo composition 

The composition consists of a subject’s head, and a plain background. For a frontal-facing pose, the width of the subject's 

head shall occupy approximately 70% of the width of the captured image. This width shall be the horizontal distance 

between the mid-points of two imaginary vertical lines. Each imaginary line shall be drawn between the upper and lower 

lobes of each ear and shall be positioned where the external ear connects to the head. A template and an example are 

shown in Figure I2. For other poses, the composition shall be rotated about an imaginary axis extending from the top of 

the head though the base of the neck. 

This composition is applied to SAP level 51. 
Part 2 – Annex I ANSI/NIST-ITL 2-2008

253

a. A template of the “head only” 

photo. The width of the head is 7/10th 

the width of the photo. 

b. An example “head only” 

photo. 

Figure I2 – A facial image template and an example image that meets “Head Only” (level 51) scene constraints. 

Head centering

For the frontal pose, the face shall be positioned to satisfy all of the following conditions: 

The approximate horizontal mid-points of the mouth and of the bridge of the nose shall lie on an imaginary vertical straight 

line positioned at the horizontal center of the image. 

An imaginary horizontal line through the center of the subject's eyes shall be located at approximately the 55% point of 

the vertical distance up from the bottom edge of the captured image. 

For non-frontal pose, the subject shall satisfy these conditions when the head is rotated about an axis though the head 

and torso from the current pose back to center (zero angles) pose. 

Visibility of Ears

The ear(s) shall be visible in frontal, profile and angled views for both “Head and Shoulders” and “Head Only” scene 

compositions. The hair shall be pushed back or tied behind the ears when appropriate. 

From the 50/51 level description:

If hair covers the ears, then when possible, two photographs should be captured – one with hair in its normal state, and 

one with hair pulled back behind the ears. 
Part 2 – Annex I ANSI/NIST-ITL 2-2008

254

Facial expression

The expression should be neutral (non-smiling) with both eyes open normally (i.e. not wide-open), and mouth closed. 

Every effort should be made to have supplied images conform with this specification. A smile with closed jaw is not 

recommended. 

Eyeglasses

For subjects who normally wear eyeglasses, every effort should be made to capture the mugshots with the glasses on. If 

significant glare in the glasses is evident in the photograph, then a second frontal mugshot image should be captured of 

the subject without glasses. Specification of eyeglasses in the SXS field is required. 

Eye patches

The wearing of eye patches is allowed only for medical reasons. In these cases, the specification of the patch, in the SXS 

field is required. 

Background

The subject whose image is being captured shall be positioned in front of a background which is 18% gray with a plain 

smooth flat surface. A Kodak or other neutral gray card or densitometer shall be used to verify this 18% gray reflectance 

requirement. 

The boundary between the head and the background should be clearly identifiable about the entire subject (very large 

volume hair excepted). There should be no shadows visible on the background behind the face image. 

Photographic Requirements 

Depth of field

The subject's captured facial image shall always be in focus from the nose to the ears. Although this may result in the 

background behind the subject being out of focus, this is not a problem.14 It is recommended that auto-focus on the 

central part of face be used with digital camera photography. 

Subject lighting 

Lighting shall be equally distributed on the face. There shall be no significant direction of the light from the point of view of 

the photographer. 

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 

shadows. In particular, there shall be no dark shadows in the eye-sockets due to the brow, and the iris and pupil of the 

eyes shall be clearly visible. 

Subject illumination can be accomplished using three point balanced illumination sources. A single bare “point” light 

source, such as a camera flash, is not acceptable for imaging. 

Appropriate diffusion techniques shall be employed to eliminate hot spots on the facial image. These hot spots usually 

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 – Annex I ANSI/NIST-ITL 2-2008

255

Background lighting 

Proper lighting shall contribute to the uniformity of illumination of the background, and the background shall be free of 

shadows. 

Exposure calibration

The exposure shall be keyed to the background. Several areas of the recorded 18% gray background shall be used to 

verify the proper exposure. The averages of the 8-bit Red, Green, and Blue (RGB) components within each area shall be 

calculated. Each of the RGB means shall fall between 105 and 125 with a standard deviation of plus or minus 10. 

Furthermore, for every area examined, the maximum difference between the means of any two of the RGB components 

shall not exceed 10. 

No saturation 

For each patch of skin on the person’s face, the gradations in textures shall be clearly visible. In this sense, there will be

no saturation (over or under exposure) on the face. 

No unnatural color or “red-eye”

Unnaturally colored lighting (e.g., yellow, red) is not allowed. Care shall be taken to correct the "white balance" of image 

capture devices. The lighting shall produce a face image with natural looking flesh tones when viewed in typical 

examination environments. “Red-eye” is not acceptable. 

No color or grayscale enhancement

A process that overexposes or under-develops a color or grayscale image for purposes of beauty enhancement or artistic 

pleasure is not allowed. The full spectrum shall be represented on the face image where appropriate. Teeth and whites 

of eyes shall be clearly light or white (when appropriate) and dark hair or features (when appropriate) shall be clearly dark. 

No unnatural radial distortion of the camera lens, resulting in a diagonal angle of view of approximately 20 to 28 degrees. 

Fish eye effect, a type of distortion where central objects of the image erroneously appear closer than those at the edge, 

typically resulting in what appear to be unusually large noses in the image, is not allowed. While some distortion is almost 

always present during portrait photography, that distortion should not be noticeable by human examination. 

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 

should be that of a medium telephoto lens. For 35 mm photography, this means that the focal length should be between 

90 mm and 130 mm. For other negative formats/sensors, the recommended focal length is 2 to 3 times the diagonal of 

the negative/sensor, 

Digital Requirements 

Pixel aspect ratio 

Digital cameras and scanners used to capture facial images shall use square pixels with a pixel aspect ratio of 1:1. 

Image aspect ratio 

The Width:Height (i.e., HLL:VLL) aspect ratio of the captured image shall be 3:4. This corresponds to commonly used 

format sizes such as 600 x 800, 768x1024, etc., allowing for a COTS digital camera to be used for capture. 

No interlacing
Part 2 – Annex I ANSI/NIST-ITL 2-2008

256

Interlaced video frames are not allowed and all interlacing must be absent (not simply removed, but absent). 

No digital zoom

The use of digital zoom (interpolation) to achieve specified resolution associated with Subject Application Profiles. 

Image Compression 

Non-frontal facial images shall be compressed using JPEG 2000 (JPEG is not allowed) meeting the maximum 

compression limits specified below. 

There shall be one frontal facial image compressed using lossless JPEG 2000. If multiple frontal images are in the 

transaction, then one image must be compressed via lossless compression, and the others can be compressed either 

using lossless JPEG 2000 or lossy JPEG 2000 that meets the maximum compression limits specified below. The best 

practice is to apply the lossless compression to the frontal image meeting the “Ears Visible” constraint. 

The maximum compression ratio for both JPEG and JPEG 2000 of a rectangular region containing any exposed skin of 

the face, from crown to chin and ear to ear, shall be at most 15:1. This requirement is derived from studies of face 

algorithm matching at high and low resolutions. The non-facial portion of the mugshot, as well as the SMT Type-10 

record, can be compressed up to a ratio of 120:1. 

For JPEG, reference [14] provides source code to implement compression with both ROI and fixed compression ratios. 

For JPEG 2000, these capabilities are built into the implementation. 

For both JPEG and JPEG 2000, care must be taken to account for automatic compression by camera hardware. Multiple 

compression stages can damage the quality of photographic data. When possible, minimum compression (highest 

resolutions) should be applied at the camera level when external software performs the final (15:1 or less) compression 

stage. 

The table below provides the the typical size of a single facial photograph using the compression recommendations 

contained in this section for levels 30 and 40, 50, and 51. We assume that the image is formated as 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 image width, then 

the area taken by the face is 25% of the total image area. SAP levels 50 and 51 include the constraint of lossless 

compression for the frontal pose facial image as discussed above. 

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 

51 2400x3200 22.5 MB 7.5 MB 
Part 2 – Annex I ANSI/NIST-ITL 2-2008

257

Allowed color space

A full color image shall be captured. To ensure that color images exchanged between differing systems can be correctly 

displayed or printed, images shall be converted to the device-independent color space, sRGB. 

Format Requirements 

Subject Pose (POS) and Subject pose angles (SPA) 

One of either the POS or SPA fields shall be used to denote pose angles. 

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 

angle is 0, 90, and -90 respectively. (The sign of the Yaw angle in the previous sentence corresponds to the field 10.020 

convention where a right profile is when the subject turns to the left). 

The SPA field 10.025 can be used for the above poses and shall be used for all other angled poses. The POS field 

10.020 shall then be of type code “D”, for determined 3D pose, instructing the user to use 10.025 as the reference for 

pose angles. (For example, a 3⁄4 profile capture would require a POS field entry of “D” with the angle specified in the SPA 

field.) 

In all cases, the uncertainty in the Yaw pose angle determination shall be less than 5 degrees of the frontal photograph, 

and 10 degrees in the non-frontal photographs. The uncertainty in the Pitch and Roll angles shall be less than 5 degrees. 

Subject facial description (SXS)

The Subject facial description field shall be present in the transaction when one or more of the facial attributes given by 

the type codes of 10.026 is present in the image. 

Subject hair color (SHC)

The Subject hair color field shall be present in the transaction. The code “UNSPECIFIED” for this field is not allowed. 

Subject eye color (SEC)

The Subject eye color field shall be present in the transaction. The code “UNSPECIFIED” for this field is not allowed. 
Part 2 – Annex J ANSI/NIST-ITL 2-2008

258 

Annex J Face-Pose Values 

(Informative) 

The definition and range of pose angles 

The Yaw and Roll angles shall be measured from the full face pose position and have a range of values from -180 

degrees to +180 degrees. The Pitch angle shall have a range of values from -90 degrees to +90 degrees. The pose angle 

set is given by Tait-Bryan angles. 

Yaw angle: rotation about the vertical (y) axis. A positive Yaw angle is used to express the angular offset as the subject 

rotates from a full-face pose to their left (approaching a right profile). A negative Yaw angle is used to express the angular 

offset as the subject rotates from a full-face pose to their right (approaching a left profile). 

Pitch angle: rotation about the horizontal side-to-side (x) horizontal axis. 

Roll angle: rotation about the horizontal back to front (z) axis. 

The angles are defined relative to the frontal view of the subject, which has angles (0, 0, 0) as shown in Figure J1. 

Examples are shown in Figure J2. 

Figure J1 – The definition of pose angle set is with respect to the frontal view of the subject. 
Part 2 – Annex J ANSI/NIST-ITL 2-2008

259

A B C d e f g 

Figure J2 – Examples of pose angles and their encodings. The pose angles (Y, P, R) of Figures (a) – (g) are given 

by (0, 0, 0), (+45, 0, 0), (-45, 0, 0), (0, -45, 0), (0, +45, 0), (0, 0, -45), and (0, 0, +45), respectively. 

The uncertainty in the pose angles is given by the range 0 to 90 inclusive. It shall denote approximately a maximum value 

of possible deviation in the measurement of the pose. This shall correspond to a two standard deviation confidence 

interval. 

The encoding of angles is in ASCII format, with the minus sign “-“ used to denote a negative value and the plus “+” sign 

optionally used to denote a positive value. Pose angle uncertainty angles always are positive. 

The order of rotation through pose angles 

As order of the successive rotation around the different axes does matter, the encoded rotation angle shall correspond to 

an order of execution starting from the frontal view. This order shall be given by Roll (about the front axis), then Pitch 

(about the horizontal axis) and finally Yaw (about the vertical axis). The (first executed) Roll transformation will therefore

always be in the image (x, y) plane. Examples are shown in Figure J3. 

From the point of view of executing a transformation from the observed view to a frontal view, the transformation order will 

therefore be Yaw, Pitch, and then Roll. Note however that the encoded angle is from the frontal view to the observed 

view.
Part 2 – Annex J ANSI/NIST-ITL 2-2008

260

 (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 

Figure J3 – Examples of the order of rotation through pose angles with an origin of coordinate system at the 

nose tip. Figures (a)-(c) show three successive rotation steps to achieve the pose angles (Y, P, R) of (-45, -30, 

+45). Figures (d)-(f) show three successive rotation steps to achieve the pose angles (Y, P, R) of (-30, +20, -30). 
Part 2 – Annex K ANSI/NIST-ITL 2-2008

261 

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. 

IAFIS-DOC-01078-8.001 Electronic Biometric Transmission Specification (EBTS), Version 8.001, October 24, 2007.15

IAFIS-DOC-01078-8.002 Electronic Biometric Transmission Specification (EBTS), Version 8.002, April 1, 2008.16

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. 

 

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

Pennsylvania Avenue, NW, Washington, DC 20535. 

16 Ibid. 
Part 2 – Annex L 

262 

1 Annex L Constraint Schema 2 (Informative) 3 

4 Constraints to an implementer’s ansi-nist.xsd subset schema should be based on the ANSI/NIST constraint schema presen5 (“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" xm13 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. The nillable attribute has been removed === --> 21 <!-- ==except where allowed for date elements. Some NIEM elements ====== --> 22 <!-- ==are not used in this standard, but have not been deleted for the ====== --> 23 <!-- ==convenience of implementers who may want to use them in user-defined ====== --> 24 <!-- ==elements. ========================================= ====== --> 25 <xsd:annotation> 26 <xsd:documentation>ANSI/NIST Fingerprint and Biometric standard.</xsd:documentation> 27 <xsd:appinfo> 28 <i:ConformantIndicator>true</i:ConformantIndicator> 29 </xsd:appinfo> 30 </xsd:annotation> 31 <xsd:import schemaLocation="../../structures/2.0/structures.xsd" namespace="http://niem.gov/niem/s32 <xsd:import schemaLocation="../../appinfo/2.0/appinfo.xsd" namespace="http://niem.gov/niem/appinfo33 <xsd:import schemaLocation="../../fbi/2.0/fbi.xsd" namespace="http://niem.gov/niem/fbi/2.0"/> 34 <xsd:import schemaLocation="../../niem-core/2.0/niem-core.xsd" namespace="http://niem.gov/niem/niem35 <xsd:import schemaLocation="../../proxy/xsd/2.0/xsd.xsd" namespace="http://niem.gov/niem/proxy/xsd36 <!-- ======================================================= --> 37 <xsd:simpleType name="ALSCodeSimpleType"> 38 <xsd:annotation> 39 <xsd:appinfo> 
Part 2 – Annex L 

263

1 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 2 </xsd:appinfo> 3 </xsd:annotation> 4 <xsd:restriction base="xsd:token"> 5 <xsd:enumeration value="NIR"> 6 <xsd:annotation> 7 <xsd:documentation>Near-infrared illumination (~700-850nm) </xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="VIS"> 11 <xsd:annotation> 12 <xsd:documentation>Visible full-spectrum illumination (~380-740nm)</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 </xsd:restriction> 16 </xsd:simpleType> 17 <xsd:complexType name="ALSCodeType"> 18 <xsd:annotation> 19 <xsd:appinfo> 20 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 21 </xsd:appinfo> 22 </xsd:annotation> 23 <xsd:simpleContent> 24 <xsd:extension base="ansi-nist:ALSCodeSimpleType"> 25 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 26 </xsd:extension> 27 </xsd:simpleContent> 28 </xsd:complexType> 29 <!-- ============not used=========================================== --> 30 <xsd:complexType name="ActivityAugmentationType"> 31 <xsd:annotation> 32 <xsd:documentation>A data type for additional information about an activity.</xsd:documentatio33 <xsd:appinfo> 34 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="AugmentationType"/> 35 </xsd:appinfo> 36 </xsd:annotation> 37 <xsd:complexContent> 38 <xsd:extension base="s:AugmentationType"> 39 <xsd:sequence> 40 <xsd:element ref="ansi-nist:ActivityAgencyNotificationIndicator" minOccurs="0" maxOccurs="41 <xsd:element ref="ansi-nist:ActivityApprovalDate" minOccurs="0" maxOccurs="unbounded"/> 42 <xsd:element ref="ansi-nist:ActivityEndTimeZoneCode" minOccurs="0" maxOccurs="unbounded"/> 43 <xsd:element ref="ansi-nist:ActivityTimeZoneCode" minOccurs="0" maxOccurs="unbounded"/> 
Part 2 – Annex L 

264

1 </xsd:sequence> 2 </xsd:extension> 3 </xsd:complexContent> 4 </xsd:complexType> 5 <!-- ======================================================= --> 6 <xsd:simpleType name="BTYCodeSimpleType"> 7 <xsd:annotation> 8 <xsd:appinfo> 9 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 

10 </xsd:appinfo> 11 </xsd:annotation> 12 <xsd:restriction base="xsd:token"> 13 <xsd:enumeration value="0"> 14 <xsd:annotation> 15 <xsd:documentation>No information given</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="1"> 19 <xsd:annotation> 20 <xsd:documentation>Multple biometrics used</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="10"> 24 <xsd:annotation> 25 <xsd:documentation>Iris</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="100"> 29 <xsd:annotation> 30 <xsd:documentation>Keystroke dynamics</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="1000"> 34 <xsd:annotation> 35 <xsd:documentation>Gait</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="10000"> 39 <xsd:annotation> 40 <xsd:documentation>Finger geometry</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="2"> 
Part 2 – Annex L 

265

1 <xsd:annotation> 2 <xsd:documentation>Facial features</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="20"> 6 <xsd:annotation> 7 <xsd:documentation>Retina</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="200"> 11 <xsd:annotation> 12 <xsd:documentation>Lip movement</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="2000"> 16 <xsd:annotation> 17 <xsd:documentation>Body odor</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="20000"> 21 <xsd:annotation> 22 <xsd:documentation>Palm print</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="4"> 26 <xsd:annotation> 27 <xsd:documentation>Voice</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="40"> 31 <xsd:annotation> 32 <xsd:documentation>Hand geometry</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="400"> 36 <xsd:annotation> 37 <xsd:documentation>Thermal face image</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="4000"> 41 <xsd:annotation> 42 <xsd:documentation>DNA</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

266

1 </xsd:enumeration> 2 <xsd:enumeration value="40000"> 3 <xsd:annotation> 4 <xsd:documentation>Vein pattern</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="8"> 8 <xsd:annotation> 9 <xsd:documentation>Fingerprint</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="80"> 13 <xsd:annotation> 14 <xsd:documentation>Signature dynamics</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 <xsd:enumeration value="800"> 18 <xsd:annotation> 19 <xsd:documentation>Thermal hand image</xsd:documentation> 20 </xsd:annotation> 21 </xsd:enumeration> 22 <xsd:enumeration value="8000"> 23 <xsd:annotation> 24 <xsd:documentation>Ear shape</xsd:documentation> 25 </xsd:annotation> 26 </xsd:enumeration> 27 <xsd:enumeration value="80000"> 28 <xsd:annotation> 29 <xsd:documentation>Foot print</xsd:documentation> 30 </xsd:annotation> 31 </xsd:enumeration> 32 </xsd:restriction> 33 </xsd:simpleType> 34 <xsd:complexType name="BTYCodeType"> 35 <xsd:annotation> 36 <xsd:appinfo> 37 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 38 </xsd:appinfo> 39 </xsd:annotation> 40 <xsd:simpleContent> 41 <xsd:extension base="ansi-nist:BTYCodeSimpleType"> 42 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 43 </xsd:extension> 
Part 2 – Annex L 

267

1 </xsd:simpleContent> 2 </xsd:complexType> 3 <!-- ======================================================= --> 4 <xsd:complexType name="CBEFFImageType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:name="NISTImageType"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:complexContent> 11 <xsd:extension base="ansi-nist:NISTImageType"> 12 <xsd:sequence> 13 <!-- =====================================================fieldID="99.103" fieldMnemonic="14 <xsd:element ref="ansi-nist:CBEFFFormatOwnerIdentification"/> 15 <!-- =====================================================fieldID="99.104" fieldMnemonic="16 <xsd:element ref="ansi-nist:CBEFFFormatCategoryIdentification"/> 17 <!-- =====================================================fieldID="99.100" fieldMnemonic="18 <xsd:element ref="ansi-nist:CBEFFVersionIdentification"/> 19 <!-- =====================================================fieldID="99.101" fieldMnemonic="20 <xsd:element ref="ansi-nist:CBEFFCategoryCode"/> 21 </xsd:sequence> 22 </xsd:extension> 23 </xsd:complexContent> 24 </xsd:complexType> 25 <!-- ======================================================= --> 26 <xsd:simpleType name="COLCodeSimpleType"> 27 <xsd:annotation> 28 <xsd:appinfo> 29 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 <xsd:restriction base="xsd:token"> 33 <xsd:enumeration value="BLACK"> 34 <xsd:annotation> 35 <xsd:documentation>Black</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="BLUE"> 39 <xsd:annotation> 40 <xsd:documentation>Blue</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="BROWN"> 
Part 2 – Annex L 

268

1 <xsd:annotation> 2 <xsd:documentation>Brown</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="GRAY"> 6 <xsd:annotation> 7 <xsd:documentation>Gray</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="GREEN"> 11 <xsd:annotation> 12 <xsd:documentation>Green</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="MULTI"> 16 <xsd:annotation> 17 <xsd:documentation>Multi</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="ORANGE"> 21 <xsd:annotation> 22 <xsd:documentation>Orange</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="OUTLINE"> 26 <xsd:annotation> 27 <xsd:documentation>Outline</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="PURPLE"> 31 <xsd:annotation> 32 <xsd:documentation>Purple</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="RED"> 36 <xsd:annotation> 37 <xsd:documentation>Red</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="WHITE"> 41 <xsd:annotation> 42 <xsd:documentation>White</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

269

1 </xsd:enumeration> 2 <xsd:enumeration value="YELLOW"> 3 <xsd:annotation> 4 <xsd:documentation>Yellow</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 </xsd:restriction> 8 </xsd:simpleType> 9 <xsd:complexType name="COLCodeType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:simpleContent> 16 <xsd:extension base="ansi-nist:COLCodeSimpleType"> 17 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 18 </xsd:extension> 19 </xsd:simpleContent> 20 </xsd:complexType> 21 <!-- ======================================================= --> 22 <xsd:simpleType name="CSICodeSimpleType"> 23 <xsd:annotation> 24 <xsd:appinfo> 25 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 26 </xsd:appinfo> 27 </xsd:annotation> 28 <xsd:restriction base="xsd:token"> 29 <xsd:enumeration value="000"> 30 <xsd:annotation> 31 <xsd:documentation>ASCII 7-bit English</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="001"> 35 <xsd:annotation> 36 <xsd:documentation>ASCII 8-bit Latin</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="002"> 40 <xsd:annotation> 41 <xsd:documentation>UNICODE 16-bit</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

270

1 <xsd:enumeration value="003"> 2 <xsd:annotation> 3 <xsd:documentation>UTF 8-bit</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 </xsd:restriction> 7 </xsd:simpleType> 8 <xsd:complexType name="CSICodeType"> 9 <xsd:annotation> 

10 <xsd:appinfo> 11 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 12 </xsd:appinfo> 13 </xsd:annotation> 14 <xsd:simpleContent> 15 <xsd:extension base="ansi-nist:CSICodeSimpleType"> 16 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 17 </xsd:extension> 18 </xsd:simpleContent> 19 </xsd:complexType> 20 <!-- ======================================================= --> 21 <xsd:simpleType name="CSNCodeSimpleType"> 22 <xsd:annotation> 23 <xsd:appinfo> 24 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 25 </xsd:appinfo> 26 </xsd:annotation> 27 <xsd:restriction base="xsd:token"> 28 <xsd:enumeration value="ASCII 7-bit English"> 29 <xsd:annotation> 30 <xsd:documentation>American Standard Code for Information Interchange is a code representi31 characters as numbers</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="ASCII 8-bit Latin"> 35 <xsd:annotation> 36 <xsd:documentation>Larger character set of ASCII code to represent non-English characters<37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="UNICODE 16-bit"> 40 <xsd:annotation> 41 <xsd:documentation>Unicode provides a unique number for every character, no matter what pl42 language</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

271

1 </xsd:enumeration> 2 <xsd:enumeration value="UTF 8-bit"> 3 <xsd:annotation> 4 <xsd:documentation>Unicode Transformation Format whose initial encoding is consistent with 5 ASCII</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 </xsd:restriction> 9 </xsd:simpleType> 

10 <xsd:complexType name="CSNCodeType"> 11 <xsd:annotation> 12 <xsd:appinfo> 13 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 14 </xsd:appinfo> 15 </xsd:annotation> 16 <xsd:simpleContent> 17 <xsd:extension base="ansi-nist:CSNCodeSimpleType"> 18 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 19 </xsd:extension> 20 </xsd:simpleContent> 21 </xsd:complexType> 22 <!-- ======================================================= --> 23 <xsd:simpleType name="CSPCodeSimpleType"> 24 <xsd:annotation> 25 <xsd:appinfo> 26 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 27 </xsd:appinfo> 28 </xsd:annotation> 29 <xsd:restriction base="xsd:token"> 30 <xsd:enumeration value="GRAY"> 31 <xsd:annotation> 32 <xsd:documentation>Grayscale, monochrome</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="RGB"> 36 <xsd:annotation> 37 <xsd:documentation>Undetermined color space for an RGB image</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="SRGB"> 41 <xsd:annotation> 42 <xsd:documentation>sRGB IEC 61966-2-1</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

272

1 </xsd:enumeration> 2 <xsd:enumeration value="SYCC"> 3 <xsd:annotation> 4 <xsd:documentation>YCbCr JPEG 2000 compressed</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="UNK"> 8 <xsd:annotation> 9 <xsd:documentation>Undefined</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="YCC"> 13 <xsd:annotation> 14 <xsd:documentation>YCbCr legacy</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 </xsd:restriction> 18 </xsd:simpleType> 19 <xsd:complexType name="CSPCodeType"> 20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 <xsd:simpleContent> 26 <xsd:extension base="ansi-nist:CSPCodeSimpleType"> 27 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 28 </xsd:extension> 29 </xsd:simpleContent> 30 </xsd:complexType> 31 <!-- ======================================================= --> 32 <xsd:complexType name="ContentRecordType"> 33 <xsd:annotation> 34 <xsd:appinfo> 35 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 <xsd:complexContent> 39 <xsd:extension base="s:ComplexObjectType"> 40 <xsd:sequence> 41 <xsd:element ref="ansi-nist:ImageReferenceIdentification"/> 42 <xsd:element ref="ansi-nist:RecordCategoryCode"/> 43 </xsd:sequence> 
Part 2 – Annex L 

273

1 </xsd:extension> 2 </xsd:complexContent> 3 </xsd:complexType> 4 <!-- ======================================================= --> 5 <xsd:simpleType name="DMMCodeSimpleType"> 6 <xsd:annotation> 7 <xsd:appinfo> 8 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 9 </xsd:appinfo> 

10 </xsd:annotation> 11 <xsd:restriction base="xsd:token"> 12 <xsd:enumeration value="ASSISTED"> 13 <xsd:annotation> 14 <xsd:documentation>Assisted</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 <xsd:enumeration value="OBSERVED"> 18 <xsd:annotation> 19 <xsd:documentation>Observed</xsd:documentation> 20 </xsd:annotation> 21 </xsd:enumeration> 22 <xsd:enumeration value="UNATTENDED"> 23 <xsd:annotation> 24 <xsd:documentation>Unattended</xsd:documentation> 25 </xsd:annotation> 26 </xsd:enumeration> 27 <xsd:enumeration value="UNKNOWN"> 28 <xsd:annotation> 29 <xsd:documentation>Unknown</xsd:documentation> 30 </xsd:annotation> 31 </xsd:enumeration> 32 </xsd:restriction> 33 </xsd:simpleType> 34 <xsd:complexType name="DMMCodeType"> 35 <xsd:annotation> 36 <xsd:appinfo> 37 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 38 </xsd:appinfo> 39 </xsd:annotation> 40 <xsd:simpleContent> 41 <xsd:extension base="ansi-nist:DMMCodeSimpleType"> 42 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 43 </xsd:extension> 
Part 2 – Annex L 

274

1 </xsd:simpleContent> 2 </xsd:complexType> 3 <!-- ======================================================= --> 4 <xsd:simpleType name="FEFCodeSimpleType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:restriction base="xsd:token"> 11 <xsd:enumeration value="FV0"> 12 <xsd:annotation> 13 <xsd:documentation>All fingers within EJI</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="FV1"> 17 <xsd:annotation> 18 <xsd:documentation>Single Full Finger View</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="FV2"> 22 <xsd:annotation> 23 <xsd:documentation>Single Full Finger View</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="FV3"> 27 <xsd:annotation> 28 <xsd:documentation>Single Full Finger View</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="FV4"> 32 <xsd:annotation> 33 <xsd:documentation>Single Full Finger View</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 </xsd:restriction> 37 </xsd:simpleType> 38 <xsd:complexType name="FEFCodeType"> 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> 
Part 2 – Annex L 

275

1 <xsd:simpleContent> 2 <xsd:extension base="ansi-nist:FEFCodeSimpleType"> 3 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 4 </xsd:extension> 5 </xsd:simpleContent> 6 </xsd:complexType> 7 <!-- ======================================================= --> 8 <xsd:simpleType name="FERCodeSimpleType"> 9 <xsd:annotation> 

10 <xsd:appinfo> 11 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 12 </xsd:appinfo> 13 </xsd:annotation> 14 <xsd:restriction base="xsd:token"> 15 <xsd:enumeration value="DST"> 16 <xsd:annotation> 17 <xsd:documentation>Distal Segment</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="EJI"> 21 <xsd:annotation> 22 <xsd:documentation>Entire Joint Image</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="FV1"> 26 <xsd:annotation> 27 <xsd:documentation>Single Full Finger View</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="FV2"> 31 <xsd:annotation> 32 <xsd:documentation>Single Full Finger View</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="FV3"> 36 <xsd:annotation> 37 <xsd:documentation>Single Full Finger View</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="FV4"> 41 <xsd:annotation> 42 <xsd:documentation>Single Full Finger View</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

276

1 </xsd:enumeration> 2 <xsd:enumeration value="MED"> 3 <xsd:annotation> 4 <xsd:documentation>Medial Segment</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="PRX"> 8 <xsd:annotation> 9 <xsd:documentation>Proximal Segment</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="TIP"> 13 <xsd:annotation> 14 <xsd:documentation>Rolled Tip</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 </xsd:restriction> 18 </xsd:simpleType> 19 <xsd:complexType name="FERCodeType"> 20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 <xsd:simpleContent> 26 <xsd:extension base="ansi-nist:FERCodeSimpleType"> 27 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 28 </xsd:extension> 29 </xsd:simpleContent> 30 </xsd:complexType> 31 <!-- ======================================================= --> 32 <xsd:simpleType name="FIDCodeSimpleType"> 33 <xsd:annotation> 34 <xsd:appinfo> 35 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 <xsd:restriction base="xsd:token"> 39 <xsd:enumeration value="0"> 40 <xsd:annotation> 41 <xsd:documentation>Undefined</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

277

1 <xsd:enumeration value="1"> 2 <xsd:annotation> 3 <xsd:documentation>Right eye</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="2"> 7 <xsd:annotation> 8 <xsd:documentation>Left eye</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 </xsd:restriction> 12 </xsd:simpleType> 13 <xsd:complexType name="FIDCodeType"> 14 <xsd:annotation> 15 <xsd:appinfo> 16 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 17 </xsd:appinfo> 18 </xsd:annotation> 19 <xsd:simpleContent> 20 <xsd:extension base="ansi-nist:FIDCodeSimpleType"> 21 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 22 </xsd:extension> 23 </xsd:simpleContent> 24 </xsd:complexType> 25 <!-- ======================================================= --> 26 <!-- ==FMT has been implemented as a boolean, not by this code type=== --> 27 <!-- ======================================================= --> 28 <xsd:simpleType name="FMTCodeSimpleType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:restriction base="xsd:token"> 35 <xsd:enumeration value="S"> 36 <xsd:annotation> 37 <xsd:documentation>Standard descriptions</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="U"> 41 <xsd:annotation> 42 <xsd:documentation>Vendor specific, or M1-378 descriptions</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

278

1 </xsd:enumeration> 2 </xsd:restriction> 3 </xsd:simpleType> 4 <xsd:complexType name="FMTCodeType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:simpleContent> 11 <xsd:extension base="ansi-nist:FMTCodeSimpleType"> 12 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 13 </xsd:extension> 14 </xsd:simpleContent> 15 </xsd:complexType> 16 <!-- ======================================================= --> 17 <xsd:simpleType name="FPCCodeSimpleType"> 18 <xsd:annotation> 19 <xsd:appinfo> 20 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 21 </xsd:appinfo> 22 </xsd:annotation> 23 <xsd:restriction base="xsd:token"> 24 <xsd:enumeration value="0"> 25 <xsd:annotation> 26 <xsd:documentation>Unknown, or every finger 1-10</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="1"> 30 <xsd:annotation> 31 <xsd:documentation> Right thumb</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="10"> 35 <xsd:annotation> 36 <xsd:documentation> Left little</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="11"> 40 <xsd:annotation> 41 <xsd:documentation> Plain right thumb</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

279

1 <xsd:enumeration value="12"> 2 <xsd:annotation> 3 <xsd:documentation> Plain left thumb</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="13"> 7 <xsd:annotation> 8 <xsd:documentation> Plain right four</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="14"> 12 <xsd:annotation> 13 <xsd:documentation> Plain left four</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="15"> 17 <xsd:annotation> 18 <xsd:documentation> Left and right thumbs</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="19"> 22 <xsd:annotation> 23 <xsd:documentation> Complete friction ridge exemplars</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="2"> 27 <xsd:annotation> 28 <xsd:documentation> Right index</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="255"> 32 <xsd:annotation> 33 <xsd:documentation> Unused field value in record types 3-6</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="3"> 37 <xsd:annotation> 38 <xsd:documentation> Right middle</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="4"> 42 <xsd:annotation> 43 <xsd:documentation> Right ring</xsd:documentation> 
Part 2 – Annex L 

280

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="5"> 4 <xsd:annotation> 5 <xsd:documentation> Right little</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="6"> 9 <xsd:annotation> 

10 <xsd:documentation> Left thumb</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="7"> 14 <xsd:annotation> 15 <xsd:documentation> Left index</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="8"> 19 <xsd:annotation> 20 <xsd:documentation> Left middle</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="9"> 24 <xsd:annotation> 25 <xsd:documentation> Left ring</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 </xsd:restriction> 29 </xsd:simpleType> 30 <xsd:complexType name="FPCCodeType"> 31 <xsd:annotation> 32 <xsd:appinfo> 33 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 34 </xsd:appinfo> 35 </xsd:annotation> 36 <xsd:simpleContent> 37 <xsd:extension base="ansi-nist:FPCCodeSimpleType"> 38 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 39 </xsd:extension> 40 </xsd:simpleContent> 41 </xsd:complexType> 42 <!-- ======================================================= --> 43 <xsd:complexType name="FaceImage3DPoseAngleType"> 
Part 2 – Annex L 

281

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="xsd:token"> 8 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 9 </xsd:extension> 

10 </xsd:simpleContent> 11 </xsd:complexType> 12 <!-- ======================================================= --> 13 <xsd:complexType name="FaceImageAttributeType"> 14 <xsd:annotation> 15 <xsd:appinfo> 16 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 17 </xsd:appinfo> 18 </xsd:annotation> 19 <xsd:complexContent> 20 <xsd:extension base="s:ComplexObjectType"> 21 <xsd:sequence> 22 <xsd:element ref="ansi-nist:FaceImageAttributeAbstract" minOccurs="0" maxOccurs="unbounded23 </xsd:sequence> 24 </xsd:extension> 25 </xsd:complexContent> 26 </xsd:complexType> 27 <!-- ======================================================= --> 28 <xsd:complexType name="FaceImageFeaturePointType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:complexContent> 35 <xsd:extension base="s:ComplexObjectType"> 36 <xsd:sequence> 37 <xsd:element ref="ansi-nist:FeaturePointHorizontalCoordinateValue"/> 38 <xsd:element ref="ansi-nist:FeaturePointIdentification"/> 39 <xsd:element ref="ansi-nist:FeaturePointCategory"/> 40 <xsd:element ref="ansi-nist:FeaturePointVerticalCoordinateValue"/> 41 </xsd:sequence> 42 </xsd:extension> 43 </xsd:complexContent> 
Part 2 – Annex L 

282

1 </xsd:complexType> 2 <!-- ======================================================= --> 3 <xsd:complexType name="FaceImageType"> 4 <xsd:annotation> 5 <xsd:appinfo> 6 <i:Base i:name="NISTImageType"/> 7 </xsd:appinfo> 8 </xsd:annotation> 9 <xsd:complexContent> 

10 <xsd:extension base="ansi-nist:NISTImageType"> 11 <xsd:sequence> 12 <!-- =====================================================fieldID="10.025" fieldMnemonic="13 <xsd:element ref="ansi-nist:FaceImage3DPoseAngle" minOccurs="0"/> 14 <!-- =====================================================fieldID="10.013" fieldMnemonic="15 <xsd:element ref="ansi-nist:FaceImageAcquisitionProfile"/> 16 <!-- =====================================================fieldID="10.022" fieldMnemonic="17 <xsd:element ref="ansi-nist:FaceImageAttribute" minOccurs="0" maxOccurs="unbounded"/> 18 <!-- =====================================================fieldID="10.026" fieldMnemonic="19 <xsd:element ref="ansi-nist:FaceImageDescription" minOccurs="0" maxOccurs="unbounded"/> 20 <!-- =====================================================fieldID="10.027" fieldMnemonic="21 <xsd:element ref="ansi-nist:FaceImageEyeColorAttribute" minOccurs="0"/> 22 <!-- =====================================================fieldID="10.029" fieldMnemonic="23 <xsd:element ref="ansi-nist:FaceImageFeaturePoint" minOccurs="0" maxOccurs="88"/> 24 <!-- =====================================================fieldID="10.028" fieldMnemonic="25 <xsd:element ref="ansi-nist:FaceImageHairColorAttribute" minOccurs="0" maxOccurs="2"/> 26 <!-- =====================================================fieldID="10.021" fieldMnemonic="27 <xsd:element ref="ansi-nist:FaceImagePoseOffsetAngleMeasure" minOccurs="0"/> 28 <!-- =====================================================fieldID="10.020" fieldMnemonic="29 <xsd:element ref="ansi-nist:FaceImageSubjectPose" minOccurs="0"/> 30 </xsd:sequence> 31 </xsd:extension> 32 </xsd:complexContent> 33 </xsd:complexType> 34 <!-- ======================================================= --> 35 <xsd:complexType name="FingerprintImageMajorCasePrintType"> 36 <xsd:annotation> 37 <xsd:appinfo> 38 <i:Base i:name="FingerprintType"/> 39 </xsd:appinfo> 40 </xsd:annotation> 41 <xsd:complexContent> 42 <xsd:extension base="ansi-nist:FingerprintType"> 43 <xsd:sequence> 
Part 2 – Annex L 

283

1 <!-- =====================================================fieldID="14.014" fieldMnemonic="2 <!-- ==FingerPositionCode is used from the base FingerprintType == --> 3 <xsd:element ref="ansi-nist:MajorCasePrintCode" minOccurs="0" maxOccurs="unbounded"/> 4 <!-- =====================================================fieldID="14.015" fieldMnemonic="5 <xsd:element ref="ansi-nist:MajorCasePrintSegmentOffset" minOccurs="0" maxOccurs="unbounde6 <!-- =====================================================not used =======================7 <xsd:element ref="ansi-nist:MajorCasePrintText" minOccurs="0" maxOccurs="unbounded"/> 8 </xsd:sequence> 9 </xsd:extension> 

10 </xsd:complexContent> 11 </xsd:complexType> 12 <!-- ======================================================= --> 13 <xsd:complexType name="FingerprintImageNISTQualityType"> 14 <xsd:annotation> 15 <xsd:appinfo> 16 <i:Base i:name="FingerprintType"/> 17 </xsd:appinfo> 18 </xsd:annotation> 19 <xsd:complexContent> 20 <xsd:extension base="ansi-nist:FingerprintType"> 21 <xsd:sequence> 22 <xsd:element ref="ansi-nist:NISTQualityMeasure"/> 23 </xsd:sequence> 24 </xsd:extension> 25 </xsd:complexContent> 26 </xsd:complexType> 27 <!-- ======================================================= --> 28 <xsd:complexType name="FingerprintImageQualityType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:name="FingerprintType"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:complexContent> 35 <xsd:extension base="ansi-nist:FingerprintType"> 36 <xsd:sequence> 37 <xsd:element ref="ansi-nist:QualityAlgorithmProductIdentification"/> 38 <xsd:element ref="ansi-nist:QualityAlgorithmVendorIdentification"/> 39 <xsd:element ref="ansi-nist:QualityValue"/> 40 </xsd:sequence> 41 </xsd:extension> 42 </xsd:complexContent> 43 </xsd:complexType> 
Part 2 – Annex L 

284

1 <!-- ======================================================= --> 2 <!-- ansi-nist:FingerprintImageType has been replaced by itl:FingerprintImageType --> 3 <!-- ======================================================= --> 4 <xsd:complexType name="FingerprintImageType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:name="NISTImageType"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:complexContent> 11 <xsd:extension base="ansi-nist:NISTImageType"> 12 <xsd:sequence> 13 <xsd:element ref="ansi-nist:FingerprintImageMajorCasePrint" minOccurs="0" maxOccurs="unbou14 <xsd:element ref="ansi-nist:FingerprintImagePosition" minOccurs="0" maxOccurs="unbounded"/15 <xsd:element ref="ansi-nist:FingerprintImageSegmentationQuality" minOccurs="0" maxOccurs="16 <xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory" minOccurs="0" maxOc17 </xsd:sequence> 18 </xsd:extension> 19 </xsd:complexContent> 20 </xsd:complexType> 21 <!-- ======================================================= --> 22 <!-- Just as <ansi-nist:FingerprintType> is a base for <ansi-nist:FingerprintImageQualityType>, -23 <!-- the element below is a base for <itl:PalmprintImageQualityType, --> 24 <!-- ======================================================= --> 25 <xsd:complexType name="FingerprintPalmImagePositionType"> 26 <xsd:annotation> 27 <xsd:appinfo> 28 <i:Base i:name="FingerprintType"/> 29 </xsd:appinfo> 30 </xsd:annotation> 31 <xsd:complexContent> 32 <xsd:extension base="ansi-nist:FingerprintType"> 33 <xsd:sequence> 34 <xsd:element ref="ansi-nist:PalmPosition" minOccurs="0" maxOccurs="unbounded"/> 35 </xsd:sequence> 36 </xsd:extension> 37 </xsd:complexContent> 38 </xsd:complexType> 39 <!-- ======================================================= --> 40 <xsd:complexType name="FingerprintPatternType"> 41 <xsd:annotation> 42 <xsd:appinfo> 43 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 
Part 2 – Annex L 

285

1 </xsd:appinfo> 2 </xsd:annotation> 3 <xsd:complexContent> 4 <xsd:extension base="s:ComplexObjectType"> 5 <xsd:sequence> 6 <xsd:element ref="ansi-nist:PatternCodeSourceCode" minOccurs="0" maxOccurs="unbounded"/> 7 <xsd:element ref="ansi-nist:PatternCorePosition" minOccurs="0" maxOccurs="unbounded"/> 8 <xsd:element ref="ansi-nist:PatternDeltaPosition" minOccurs="0" maxOccurs="unbounded"/> 9 <xsd:element ref="ansi-nist:PatternNISTStandardText" minOccurs="0" maxOccurs="unbounded"/> 

10 <xsd:element ref="ansi-nist:PatternUserText" minOccurs="0" maxOccurs="unbounded"/> 11 </xsd:sequence> 12 </xsd:extension> 13 </xsd:complexContent> 14 </xsd:complexType> 15 <!-- ======================================================= --> 16 <xsd:complexType name="FingerprintType"> 17 <xsd:annotation> 18 <xsd:appinfo> 19 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 20 </xsd:appinfo> 21 </xsd:annotation> 22 <xsd:complexContent> 23 <xsd:extension base="s:ComplexObjectType"> 24 <xsd:sequence> 25 <!-- =====================================================Types 03-06 ===fieldMnemonic="FG26 <!-- =====================================================fieldID="14.014" fieldMnemonic="27 <!-- =====================================================fieldID="14.022" fieldMnemonic="N28 <!-- =====================================================fieldID="14.023" fieldMnemonic="29 <!-- =====================================================fieldID="14.024" fieldMnemonic="30 <!-- ===<ansi-nist:MajorCasePrintSegmentOffset> is based on this type, but uses none of th31 <xsd:element ref="ansi-nist:FingerPositionCode" minOccurs="0" maxOccurs="unbounded"/> 32 <!-- =====================================================not used =======================33 <xsd:element ref="ansi-nist:FingerPositionIndicator" minOccurs="0" maxOccurs="unbounded"/> 34 </xsd:sequence> 35 </xsd:extension> 36 </xsd:complexContent> 37 </xsd:complexType> 38 <!-- ======================================================= --> 39 <xsd:simpleType name="GCACodeSimpleType"> 40 <xsd:annotation> 41 <xsd:appinfo> 42 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

286

1 </xsd:annotation> 2 <xsd:restriction base="xsd:token"> 3 <xsd:enumeration value="0"> 4 <xsd:annotation> 5 <xsd:documentation>NONE - Uncompressed</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="1"> 9 <xsd:annotation> 

10 <xsd:documentation>WSQ - Wavelet Scalar Quantization</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="2"> 14 <xsd:annotation> 15 <xsd:documentation>JPEGB - Baseline mode of the JPEG algorithm used to compress an image</16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="3"> 19 <xsd:annotation> 20 <xsd:documentation>JPEGL - Lossless mode of the JPEG algorithm used to compress an image</21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="4"> 24 <xsd:annotation> 25 <xsd:documentation>JP2 - Lossy mode of the JPEG2000 algorithm used to compress an image</x26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="5"> 29 <xsd:annotation> 30 <xsd:documentation>JP2L - Lossless mode of the JPEG2000 algorithm used to compress an 31 image</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="6"> 35 <xsd:annotation> 36 <xsd:documentation>PNG - Portable Network Graphics image format</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 </xsd:restriction> 40 </xsd:simpleType> 41 <xsd:complexType name="GCACodeType"> 42 <xsd:annotation> 43 <xsd:appinfo> 
Part 2 – Annex L 

287

1 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 2 </xsd:appinfo> 3 </xsd:annotation> 4 <xsd:simpleContent> 5 <xsd:extension base="ansi-nist:GCACodeSimpleType"> 6 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 7 </xsd:extension> 8 </xsd:simpleContent> 9 </xsd:complexType> 

10 <!-- ======================================================= --> 11 <xsd:simpleType name="ICTCodeSimpleType"> 12 <xsd:annotation> 13 <xsd:appinfo> 14 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 15 </xsd:appinfo> 16 </xsd:annotation> 17 <xsd:restriction base="xsd:token"> 18 <xsd:enumeration value="0"> 19 <xsd:annotation> 20 <xsd:documentation>Undefined</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="1"> 24 <xsd:annotation> 25 <xsd:documentation>Progressive</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="2"> 29 <xsd:annotation> 30 <xsd:documentation>Interlace Frame</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="3"> 34 <xsd:annotation> 35 <xsd:documentation>Interlace Field</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 </xsd:restriction> 39 </xsd:simpleType> 40 <xsd:complexType name="ICTCodeType"> 41 <xsd:annotation> 42 <xsd:appinfo> 43 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 
Part 2 – Annex L 

288

1 </xsd:appinfo> 2 </xsd:annotation> 3 <xsd:simpleContent> 4 <xsd:extension base="ansi-nist:ICTCodeSimpleType"> 5 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 6 </xsd:extension> 7 </xsd:simpleContent> 8 </xsd:complexType> 9 <!-- ======================================================= --> 

10 <xsd:simpleType name="IMPCodeSimpleType"> 11 <xsd:annotation> 12 <xsd:appinfo> 13 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 14 </xsd:appinfo> 15 </xsd:annotation> 16 <xsd:restriction base="xsd:token"> 17 <xsd:enumeration value="0"> 18 <xsd:annotation> 19 <xsd:documentation>Live-scan plain</xsd:documentation> 20 </xsd:annotation> 21 </xsd:enumeration> 22 <xsd:enumeration value="1"> 23 <xsd:annotation> 24 <xsd:documentation>Live-scan rolled</xsd:documentation> 25 </xsd:annotation> 26 </xsd:enumeration> 27 <xsd:enumeration value="10"> 28 <xsd:annotation> 29 <xsd:documentation>Live-scan palm</xsd:documentation> 30 </xsd:annotation> 31 </xsd:enumeration> 32 <xsd:enumeration value="11"> 33 <xsd:annotation> 34 <xsd:documentation>NonLive-scan palm</xsd:documentation> 35 </xsd:annotation> 36 </xsd:enumeration> 37 <xsd:enumeration value="12"> 38 <xsd:annotation> 39 <xsd:documentation>Latent palm impression</xsd:documentation> 40 </xsd:annotation> 41 </xsd:enumeration> 42 <xsd:enumeration value="13"> 43 <xsd:annotation> 
Part 2 – Annex L 

289

1 <xsd:documentation>Latent palm tracing</xsd:documentation> 2 </xsd:annotation> 3 </xsd:enumeration> 4 <xsd:enumeration value="14"> 5 <xsd:annotation> 6 <xsd:documentation>Latent palm photo</xsd:documentation> 7 </xsd:annotation> 8 </xsd:enumeration> 9 <xsd:enumeration value="15"> 

10 <xsd:annotation> 11 <xsd:documentation>Latent palm lift</xsd:documentation> 12 </xsd:annotation> 13 </xsd:enumeration> 14 <xsd:enumeration value="2"> 15 <xsd:annotation> 16 <xsd:documentation>NonLive-scan plain</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="20"> 20 <xsd:annotation> 21 <xsd:documentation>Live-scan optical contact plain</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="21"> 25 <xsd:annotation> 26 <xsd:documentation>Live-scan optical contact rolled </xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="22"> 30 <xsd:annotation> 31 <xsd:documentation>Live-scan non-optical contact plain</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="23"> 35 <xsd:annotation> 36 <xsd:documentation>Live-scan non-optical contact rolled</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="24"> 40 <xsd:annotation> 41 <xsd:documentation>Live-scan optical contactless plain</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

290

1 <xsd:enumeration value="25"> 2 <xsd:annotation> 3 <xsd:documentation>Live-scan optical contactless rolled </xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="26"> 7 <xsd:annotation> 8 <xsd:documentation>Live-scan non-optical contactless plain</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="27"> 12 <xsd:annotation> 13 <xsd:documentation>Live-scan non-optical contactless rolled</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="28"> 17 <xsd:annotation> 18 <xsd:documentation>Other</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="29"> 22 <xsd:annotation> 23 <xsd:documentation>Unknown</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="3"> 27 <xsd:annotation> 28 <xsd:documentation>NonLive-scan rolled</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="4"> 32 <xsd:annotation> 33 <xsd:documentation>Latent impression</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="5"> 37 <xsd:annotation> 38 <xsd:documentation>Latent tracing</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="6"> 42 <xsd:annotation> 43 <xsd:documentation>Latent photo</xsd:documentation> 
Part 2 – Annex L 

291

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="7"> 4 <xsd:annotation> 5 <xsd:documentation>Latent lift</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="8"> 9 <xsd:annotation> 

10 <xsd:documentation>Live-scan vertical swipe</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 </xsd:restriction> 14 </xsd:simpleType> 15 <xsd:complexType name="IMPCodeType"> 16 <xsd:annotation> 17 <xsd:appinfo> 18 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 19 </xsd:appinfo> 20 </xsd:annotation> 21 <xsd:simpleContent> 22 <xsd:extension base="ansi-nist:IMPCodeSimpleType"> 23 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 24 </xsd:extension> 25 </xsd:simpleContent> 26 </xsd:complexType> 27 <!-- ======================================================= --> 28 <xsd:simpleType name="IMTCodeSimpleType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:restriction base="xsd:token"> 35 <xsd:enumeration value="FACE"> 36 <xsd:annotation> 37 <xsd:documentation>Face</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="MARK"> 41 <xsd:annotation> 42 <xsd:documentation>Mark</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

292

1 </xsd:enumeration> 2 <xsd:enumeration value="SCAR"> 3 <xsd:annotation> 4 <xsd:documentation>Scar</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="TATTOO"> 8 <xsd:annotation> 9 <xsd:documentation>Tattoo</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 </xsd:restriction> 13 </xsd:simpleType> 14 <xsd:complexType name="IMTCodeType"> 15 <xsd:annotation> 16 <xsd:appinfo> 17 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 18 </xsd:appinfo> 19 </xsd:annotation> 20 <xsd:simpleContent> 21 <xsd:extension base="ansi-nist:IMTCodeSimpleType"> 22 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 23 </xsd:extension> 24 </xsd:simpleContent> 25 </xsd:complexType> 26 <!-- ======================================================= --> 27 <xsd:simpleType name="IOCCodeSimpleType"> 28 <xsd:annotation> 29 <xsd:appinfo> 30 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 31 </xsd:appinfo> 32 </xsd:annotation> 33 <xsd:restriction base="xsd:token"> 34 <xsd:enumeration value="0"> 35 <xsd:annotation> 36 <xsd:documentation>Undefined</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="1"> 40 <xsd:annotation> 41 <xsd:documentation>Base</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

293

1 <xsd:enumeration value="2"> 2 <xsd:annotation> 3 <xsd:documentation>Flipped</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 </xsd:restriction> 7 </xsd:simpleType> 8 <xsd:complexType name="IOCCodeType"> 9 <xsd:annotation> 

10 <xsd:appinfo> 11 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 12 </xsd:appinfo> 13 </xsd:annotation> 14 <xsd:simpleContent> 15 <xsd:extension base="ansi-nist:IOCCodeSimpleType"> 16 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 17 </xsd:extension> 18 </xsd:simpleContent> 19 </xsd:complexType> 20 <!-- ======================================================= --> 21 <xsd:simpleType name="IRTCodeSimpleType"> 22 <xsd:annotation> 23 <xsd:appinfo> 24 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 25 </xsd:appinfo> 26 </xsd:annotation> 27 <xsd:restriction base="xsd:token"> 28 <xsd:enumeration value="1"> 29 <xsd:annotation> 30 <xsd:documentation>Transaction information - ASCII</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="10"> 34 <xsd:annotation> 35 <xsd:documentation>Facial & SMT image - ASCII/Binary</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="13"> 39 <xsd:annotation> 40 <xsd:documentation>Variable-resolution latent image - ASCII/Binary</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="14"> 
Part 2 – Annex L 

294

1 <xsd:annotation> 2 <xsd:documentation>Variable-resolution fingerprint image - ASCII/Binary</xsd:documentation3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="15"> 6 <xsd:annotation> 7 <xsd:documentation>Variable-resolution palmprint Image - ASCII/Binary</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="16"> 11 <xsd:annotation> 12 <xsd:documentation>User-defined variable-resolution testing Image - ASCII/Binary</xsd:docum13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="17"> 16 <xsd:annotation> 17 <xsd:documentation>Iris image - ASCII/Binary</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="2"> 21 <xsd:annotation> 22 <xsd:documentation>User-defined descriptive text - ASCII</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="3"> 26 <xsd:annotation> 27 <xsd:documentation>Low-resolution grayscale fingerprint image - Binary</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="4"> 31 <xsd:annotation> 32 <xsd:documentation>High-resolution grayscale fingerprint image - Binary</xsd:documentation33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="5"> 36 <xsd:annotation> 37 <xsd:documentation>Low-resolution binary fingerprint image - Binary</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="6"> 41 <xsd:annotation> 42 <xsd:documentation>High-resolution binary fingerprint image - Binary</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

295

1 </xsd:enumeration> 2 <xsd:enumeration value="7"> 3 <xsd:annotation> 4 <xsd:documentation>User-defined image - Binary</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="8"> 8 <xsd:annotation> 9 <xsd:documentation>Signature image - Binary</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="9"> 13 <xsd:annotation> 14 <xsd:documentation>Minutiae data - ASCII</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 <xsd:enumeration value="99"> 18 <xsd:annotation> 19 <xsd:documentation>CBEFF Biometric data record - ASCII/BInary</xsd:documentation> 20 </xsd:annotation> 21 </xsd:enumeration> 22 </xsd:restriction> 23 </xsd:simpleType> 24 <xsd:complexType name="IRTCodeType"> 25 <xsd:annotation> 26 <xsd:appinfo> 27 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 28 </xsd:appinfo> 29 </xsd:annotation> 30 <xsd:simpleContent> 31 <xsd:extension base="ansi-nist:IRTCodeSimpleType"> 32 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 33 </xsd:extension> 34 </xsd:simpleContent> 35 </xsd:complexType> 36 <!-- ======================================================= --> 37 <xsd:simpleType name="ISRCodeSimpleType"> 38 <xsd:annotation> 39 <xsd:appinfo> 40 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 41 </xsd:appinfo> 42 </xsd:annotation> 43 <xsd:restriction base="xsd:token"> 
Part 2 – Annex L 

296

1 <xsd:enumeration value="0"> 2 <xsd:annotation> 3 <xsd:documentation>Types 3 and 5, half minimum; Types 4, 6 and 8, minimum; Type 8 vector</4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="1"> 7 <xsd:annotation> 8 <xsd:documentation>Types 3 and 5, half native; Types 4, 6, and 8 native </xsd:documentatio9 </xsd:annotation> 

10 </xsd:enumeration> 11 </xsd:restriction> 12 </xsd:simpleType> 13 <xsd:complexType name="ISRCodeType"> 14 <xsd:annotation> 15 <xsd:appinfo> 16 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 17 </xsd:appinfo> 18 </xsd:annotation> 19 <xsd:simpleContent> 20 <xsd:extension base="ansi-nist:ISRCodeSimpleType"> 21 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 22 </xsd:extension> 23 </xsd:simpleContent> 24 </xsd:complexType> 25 <!-- ======================================================= --> 26 <xsd:complexType name="IdentificationRangeType"> 27 <xsd:annotation> 28 <xsd:appinfo> 29 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 <xsd:complexContent> 33 <xsd:extension base="s:ComplexObjectType"> 34 <xsd:sequence> 35 <xsd:element ref="ansi-nist:MaximumRangeIdentification" minOccurs="0" maxOccurs="unbounded36 <xsd:element ref="ansi-nist:MinimumRangeIdentification" minOccurs="0" maxOccurs="unbounded37 </xsd:sequence> 38 </xsd:extension> 39 </xsd:complexContent> 40 </xsd:complexType> 41 <!-- ======================================================= --> 42 <xsd:complexType name="ImageCaptureType"> 43 <xsd:annotation> 
Part 2 – Annex L 

297

1 <xsd:appinfo> 2 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 3 </xsd:appinfo> 4 </xsd:annotation> 5 <xsd:complexContent> 6 <xsd:extension base="s:ComplexObjectType"> 7 <xsd:sequence> 8 <!-- =====================================================fieldID="10.005" fieldMnemonic="9 <!-- =====================================================fieldID="13.005" fieldMnemonic="

10 <!-- =====================================================fieldID="14.005" fieldMnemonic="11 <!-- =====================================================fieldID="15.005" fieldMnemonic="12 <!-- =====================================================fieldID="16.005" fieldMnemonic="13 <!-- =====================================================fieldID="17.005" fieldMnemonic="14 <xsd:element ref="ansi-nist:CaptureDate" minOccurs="0"/> 15 <!-- =====================================================not used =======================16 <xsd:element ref="ansi-nist:CaptureDescription" minOccurs="0" maxOccurs="unbounded"/> 17 <!-- =====================================================fieldID="17.018" fieldMnemonic="18 <xsd:element ref="ansi-nist:CaptureDeviceGlobalIdentification" minOccurs="0"/> 19 <!-- =====================================================fieldID="17.017" fieldMnemonic="20 <xsd:element ref="ansi-nist:CaptureDeviceIdentification" minOccurs="0"/> 21 <!-- =====================================================fieldID="17.019" fieldMnemonic="22 <xsd:element ref="ansi-nist:CaptureDeviceMakeText" minOccurs="0"/> 23 <xsd:element ref="ansi-nist:CaptureDeviceModelText" minOccurs="0"/> 24 <xsd:element ref="ansi-nist:CaptureDeviceSerialNumberText" minOccurs="0"/> 25 <!-- =====================================================fieldID="XX.016" fieldMnemonic="26 <xsd:element ref="ansi-nist:CaptureHorizontalPixelDensityValue" minOccurs="0"/> 27 <!-- =====================================================fieldID="XX.004" fieldMnemonic="28 <xsd:element ref="ansi-nist:CaptureOrganization" minOccurs="0"/> 29 <!-- ====================================================================fieldMnemonic="IS30 <xsd:element ref="ansi-nist:CaptureResolution" minOccurs="0"/> 31 <!-- =====================================================not used =======================32 <xsd:element ref="ansi-nist:CaptureSource" minOccurs="0" maxOccurs="unbounded"/> 33 <!-- =====================================================fieldID="XX.017" fieldMnemonic="34 <xsd:element ref="ansi-nist:CaptureVerticalPixelDensityValue" minOccurs="0"/> 35 <!-- =====================================================fieldID="XX.030" fieldMnemonic="36 <xsd:element ref="ansi-nist:CaptureDeviceMonitoringMode" minOccurs="0"/> 37 </xsd:sequence> 38 </xsd:extension> 39 </xsd:complexContent> 40 </xsd:complexType> 41 <!-- ======================================================= --> 42 <xsd:complexType name="ImageQualityType"> 43 <xsd:annotation> 
Part 2 – Annex L 

298

1 <xsd:appinfo> 2 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 3 </xsd:appinfo> 4 </xsd:annotation> 5 <xsd:complexContent> 6 <xsd:extension base="s:ComplexObjectType"> 7 <xsd:sequence> 8 <xsd:element ref="ansi-nist:QualityAlgorithmProductIdentification" minOccurs="0" maxOccurs9 <xsd:element ref="ansi-nist:QualityValue" minOccurs="0" maxOccurs="unbounded"/> 

10 <xsd:element ref="ansi-nist:QualityMeasureVendorIdentification" minOccurs="0" maxOccurs="u11 </xsd:sequence> 12 </xsd:extension> 13 </xsd:complexContent> 14 </xsd:complexType> 15 <!-- ======================================================= --> 16 <xsd:simpleType name="IndicatorCodeSimpleType"> 17 <xsd:annotation> 18 <xsd:appinfo> 19 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 20 </xsd:appinfo> 21 </xsd:annotation> 22 <xsd:restriction base="xsd:token"> 23 <xsd:enumeration value="false "> 24 <xsd:annotation> 25 <xsd:documentation>Indicates the record does not meet the specification</xsd:documentation26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="true "> 29 <xsd:annotation> 30 <xsd:documentation>Indicates the record meets the specification</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="unknown"> 34 <xsd:annotation> 35 <xsd:documentation>Indicates it is not known if the record meets the specification</xsd:do36 </xsd:annotation> 37 </xsd:enumeration> 38 </xsd:restriction> 39 </xsd:simpleType> 40 <xsd:complexType name="IndicatorCodeType"> 41 <xsd:annotation> 42 <xsd:appinfo> 43 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 
Part 2 – Annex L 

299

1 </xsd:appinfo> 2 </xsd:annotation> 3 <xsd:simpleContent> 4 <xsd:extension base="ansi-nist:IndicatorCodeSimpleType"> 5 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 6 </xsd:extension> 7 </xsd:simpleContent> 8 </xsd:complexType> 9 <!-- ======================================================= --> 

10 <xsd:complexType name="IrisImageCaptureType"> 11 <xsd:annotation> 12 <xsd:appinfo> 13 <i:Base i:name="ImageCaptureType"/> 14 </xsd:appinfo> 15 </xsd:annotation> 16 <xsd:complexContent> 17 <xsd:extension base="ansi-nist:ImageCaptureType"> 18 <xsd:sequence> 19 <!-- =====================================================fieldID="17.016" fieldMnemonic="20 <xsd:element ref="ansi-nist:IrisImageHorizontalOrientation" minOccurs="0"/> 21 <xsd:element ref="ansi-nist:IrisImageScanCategory" minOccurs="0"/> 22 <xsd:element ref="ansi-nist:IrisImageVerticalOrientation" minOccurs="0"/> 23 </xsd:sequence> 24 </xsd:extension> 25 </xsd:complexContent> 26 </xsd:complexType> 27 <!-- ======================================================= --> 28 <!-- ansi-nist:IrisImageType has been replaced by itl:IrisImageType --> 29 <!-- ======================================================= --> 30 <xsd:complexType name="IrisImageType"> 31 <xsd:annotation> 32 <xsd:appinfo> 33 <i:Base i:name="NISTImageType"/> 34 </xsd:appinfo> 35 </xsd:annotation> 36 <xsd:complexContent> 37 <xsd:extension base="ansi-nist:NISTImageType"> 38 <xsd:sequence> 39 <xsd:element ref="ansi-nist:IrisEyeColorAttributeCode" minOccurs="0" maxOccurs="unbounded"40 <xsd:element ref="ansi-nist:IrisEyePosition" minOccurs="0" maxOccurs="unbounded"/> 41 <xsd:element ref="ansi-nist:IrisEyeRotationAngleMeasure" minOccurs="0" maxOccurs="unbounde42 <xsd:element ref="ansi-nist:IrisEyeRotationUncertaintyValueText" minOccurs="0" maxOccurs="43 <xsd:element ref="ansi-nist:IrisImageAcquisitionLightingSpectrumValue" minOccurs="0" maxOc
Part 2 – Annex L 

300

1 <xsd:element ref="ansi-nist:IrisImageCapture" minOccurs="0" maxOccurs="unbounded"/> 2 </xsd:sequence> 3 </xsd:extension> 4 </xsd:complexContent> 5 </xsd:complexType> 6 <!-- ======================================================= --> 7 <xsd:simpleType name="MILCodeSimpleType"> 8 <xsd:annotation> 9 <xsd:appinfo> 

10 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 11 </xsd:appinfo> 12 </xsd:annotation> 13 <xsd:restriction base="xsd:token"> 14 <xsd:enumeration value="A"> 15 <xsd:annotation> 16 <xsd:documentation>Army</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="F"> 20 <xsd:annotation> 21 <xsd:documentation>Air Force</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="G"> 25 <xsd:annotation> 26 <xsd:documentation>Coast Guard</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="M"> 30 <xsd:annotation> 31 <xsd:documentation>Marines</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="N"> 35 <xsd:annotation> 36 <xsd:documentation>Navy</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 </xsd:restriction> 40 </xsd:simpleType> 41 <xsd:complexType name="MILCodeType"> 42 <xsd:annotation> 43 <xsd:appinfo> 
Part 2 – Annex L 

301

1 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 2 </xsd:appinfo> 3 </xsd:annotation> 4 <xsd:simpleContent> 5 <xsd:extension base="ansi-nist:MILCodeSimpleType"> 6 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 7 </xsd:extension> 8 </xsd:simpleContent> 9 </xsd:complexType> 

10 <!-- ======================================================= --> 11 <xsd:simpleType name="MTCCodeSimpleType"> 12 <xsd:annotation> 13 <xsd:appinfo> 14 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 15 </xsd:appinfo> 16 </xsd:annotation> 17 <xsd:restriction base="xsd:token"> 18 <xsd:enumeration value="A"> 19 <xsd:annotation> 20 <xsd:documentation>Ridge ending</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="B"> 24 <xsd:annotation> 25 <xsd:documentation>Bifurcation</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="C"> 29 <xsd:annotation> 30 <xsd:documentation>Compound</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="D"> 34 <xsd:annotation> 35 <xsd:documentation>Undetermined</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 </xsd:restriction> 39 </xsd:simpleType> 40 <xsd:complexType name="MTCCodeType"> 41 <xsd:annotation> 42 <xsd:appinfo> 43 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 
Part 2 – Annex L 

302

1 </xsd:appinfo> 2 </xsd:annotation> 3 <xsd:simpleContent> 4 <xsd:extension base="ansi-nist:MTCCodeSimpleType"> 5 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 6 </xsd:extension> 7 </xsd:simpleContent> 8 </xsd:complexType> 9 <!-- ======================================================= --> 

10 <xsd:complexType name="MajorCasePrintSegmentOffsetType"> 11 <xsd:annotation> 12 <xsd:appinfo> 13 <i:Base i:name="FingerprintType"/> 14 </xsd:appinfo> 15 </xsd:annotation> 16 <xsd:complexContent> 17 <xsd:extension base="ansi-nist:FingerprintType"> 18 <xsd:sequence> 19 <xsd:element ref="ansi-nist:SegmentBottomVerticalCoordinateValue"/> 20 <xsd:element ref="ansi-nist:SegmentLocationCode"/> 21 <xsd:element ref="ansi-nist:SegmentFingerViewCode"/> 22 <!-- ===============not used======================================== --> 23 <xsd:element ref="ansi-nist:SegmentFingerText" minOccurs="0" maxOccurs="unbounded"/> 24 <!-- ======================================================= --> 25 <xsd:element ref="ansi-nist:SegmentLeftHorizontalCoordinateValue"/> 26 <xsd:element ref="ansi-nist:SegmentRightHorizontalCoordinateValue"/> 27 <!-- ===============not used======================================== --> 28 <xsd:element ref="ansi-nist:SegmentText" minOccurs="0" maxOccurs="unbounded"/> 29 <!-- ======================================================= --> 30 <xsd:element ref="ansi-nist:SegmentTopVerticalCoordinateValue"/> 31 </xsd:sequence> 32 </xsd:extension> 33 </xsd:complexContent> 34 </xsd:complexType> 35 <!-- ======================================================= --> 36 <!-- =======not used========================================= --> 37 <!-- =======replaced, mainly by itl:MinutiaType ===================== --> 38 <!-- ======================================================= --> 39 <xsd:complexType name="MinutiaPositionType"> 40 <xsd:annotation> 41 <xsd:appinfo> 42 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

303

1 </xsd:annotation> 2 <xsd:complexContent> 3 <xsd:extension base="s:ComplexObjectType"> 4 <xsd:sequence> 5 <xsd:element ref="ansi-nist:PositionBottomCoordinateValue" minOccurs="0" maxOccurs="unboun6 <xsd:element ref="ansi-nist:PositionDirectionDegreeValue" minOccurs="0" maxOccurs="unbound7 <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue" minOccurs="0" maxOccurs="un8 <xsd:element ref="ansi-nist:PositionThetaAngleMeasure" minOccurs="0" maxOccurs="unbounded"9 <xsd:element ref="ansi-nist:PositionTopCoordinateValue" minOccurs="0" maxOccurs="unbounded

10 <xsd:element ref="ansi-nist:PositionUncertaintyValue" minOccurs="0" maxOccurs="unbounded"/11 <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue" minOccurs="0" maxOccurs="unbo12 </xsd:sequence> 13 </xsd:extension> 14 </xsd:complexContent> 15 </xsd:complexType> 16 <!-- ======================================================= --> 17 <xsd:complexType name="MinutiaRidgeCountType"> 18 <xsd:annotation> 19 <xsd:appinfo> 20 <i:Base i:name="MinutiaPositionType"/> 21 </xsd:appinfo> 22 </xsd:annotation> 23 <xsd:complexContent> 24 <xsd:extension base="ansi-nist:MinutiaPositionType"> 25 <xsd:sequence> 26 <xsd:element ref="ansi-nist:RidgeCountReferenceIdentification"/> 27 <xsd:element ref="ansi-nist:RidgeCountValue"/> 28 </xsd:sequence> 29 </xsd:extension> 30 </xsd:complexContent> 31 </xsd:complexType> 32 <!-- ======================================================= --> 33 <!-- =======not used========================================= --> 34 <!-- =======replaced, mainly by itl:MinutiaType ===================== --> 35 <!-- ======================================================= --> 36 <xsd:complexType name="MinutiaType"> 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:complexContent> 43 <xsd:extension base="s:ComplexObjectType"> 
Part 2 – Annex L 

304

1 <xsd:sequence> 2 <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue" minOccurs="0" maxOccurs="un3 <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue" minOccurs="0" maxOccurs="unbo4 <xsd:element ref="ansi-nist:MinutiaIdentification" minOccurs="0" maxOccurs="unbounded"/> 5 <xsd:element ref="ansi-nist:PositionThetaAngleMeasure" minOccurs="0" maxOccurs="unbounded"6 <xsd:element ref="ansi-nist:MinutiaPosition" minOccurs="0" maxOccurs="unbounded"/> 7 </xsd:sequence> 8 </xsd:extension> 9 </xsd:complexContent> 

10 </xsd:complexType> 11 <!-- ======================================================= --> 12 <xsd:complexType name="MinutiaeFingerPatternType"> 13 <xsd:annotation> 14 <xsd:appinfo> 15 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 16 </xsd:appinfo> 17 </xsd:annotation> 18 <xsd:complexContent> 19 <xsd:extension base="s:ComplexObjectType"> 20 <xsd:sequence> 21 <xsd:element ref="ansi-nist:FingerPatternCodeSourceCode"/> 22 <xsd:element ref="ansi-nist:FingerPattern"/> 23 </xsd:sequence> 24 </xsd:extension> 25 </xsd:complexContent> 26 </xsd:complexType> 27 <!-- ======================================================= --> 28 <xsd:complexType name="MinutiaeFingerPositionType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:complexContent> 35 <xsd:extension base="s:ComplexObjectType"> 36 <xsd:sequence> 37 <xsd:element ref="ansi-nist:PositionHorizontalCoordinateValue"/> 38 <xsd:element ref="ansi-nist:PositionVerticalCoordinateValue"/> 39 </xsd:sequence> 40 </xsd:extension> 41 </xsd:complexContent> 42 </xsd:complexType> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

305

1 <xsd:complexType name="MinutiaeReadingSystemType"> 2 <xsd:annotation> 3 <xsd:appinfo> 4 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 5 </xsd:appinfo> 6 </xsd:annotation> 7 <xsd:complexContent> 8 <xsd:extension base="s:ComplexObjectType"> 9 <xsd:sequence> 

10 <xsd:element ref="ansi-nist:ReadingSystemCodingMethodCode"/> 11 <xsd:element ref="ansi-nist:ReadingSystemName"/> 12 <xsd:element ref="ansi-nist:ReadingSystemSubsystemIdentification" minOccurs="0"/> 13 </xsd:sequence> 14 </xsd:extension> 15 </xsd:complexContent> 16 </xsd:complexType> 17 <!-- ======================================================= --> 18 <!-- ==ansi-nist:MinutiaeType has been replaced by itl:MinutiaeType====== --> 19 <!-- ======================================================= --> 20 <xsd:complexType name="MinutiaeType"> 21 <xsd:annotation> 22 <xsd:appinfo> 23 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 24 </xsd:appinfo> 25 </xsd:annotation> 26 <xsd:complexContent> 27 <xsd:extension base="s:ComplexObjectType"> 28 <xsd:sequence> 29 <xsd:element ref="ansi-nist:MinutiaeNISTStandard" minOccurs="0" maxOccurs="unbounded"/> 30 <xsd:element ref="ansi-nist:MinutiaeFingerCorePosition" minOccurs="0" maxOccurs="unbounded31 <xsd:element ref="ansi-nist:MinutiaeFingerDeltaPosition" minOccurs="0" maxOccurs="unbounde32 <xsd:element ref="ansi-nist:MinutiaeFingerPatternDetail" minOccurs="0" maxOccurs="unbounde33 <xsd:element ref="ansi-nist:MinutiaeFormatNISTStandardIndicator" minOccurs="0" maxOccurs="34 <xsd:element ref="ansi-nist:MinutiaeImpressionCaptureCategory" minOccurs="0" maxOccurs="un35 <xsd:element ref="ansi-nist:MinutiaeFingerPosition" minOccurs="0" maxOccurs="unbounded"/> 36 <xsd:element ref="ansi-nist:MinutiaePalmPosition" minOccurs="0" maxOccurs="unbounded"/> 37 </xsd:sequence> 38 </xsd:extension> 39 </xsd:complexContent> 40 </xsd:complexType> 41 <!-- ======================================================= --> 42 <xsd:complexType name="NISTImageType"> 43 <xsd:annotation> 
Part 2 – Annex L 

306

1 <xsd:appinfo> 2 <i:Base i:namespace="http://niem.gov/niem/niem-core/2.0" i:name="ImageType"/> 3 </xsd:appinfo> 4 </xsd:annotation> 5 <xsd:complexContent> 6 <xsd:extension base="nc:ImageType"> 7 <xsd:sequence> 8 <!-- =====================================================fieldID="XX.012" fieldMnemonic="9 <xsd:element ref="ansi-nist:ImageBitsPerPixelQuantity" minOccurs="0"/> 

10 <!-- =====================================================fieldID="XX.005"=date, various m11 <xsd:element ref="ansi-nist:ImageCaptureDetail" minOccurs="0"/> 12 <!-- =====================================================fieldID="XX.012" fieldMnemonic="13 <xsd:element ref="ansi-nist:ImageColorSpace" minOccurs="0"/> 14 <!-- =====================================================fieldID="XX.020" fieldMnemonic="15 <!-- =====================================================fieldID="17.021" fieldMnemonic="16 <xsd:element ref="ansi-nist:ImageCommentText" minOccurs="0" maxOccurs="unbounded"/> 17 <!-- =====================================================fieldID="XX.011" fieldMnemonic="18 <xsd:element ref="ansi-nist:ImageCompressionAlgorithm" minOccurs="0"/> 19 <!-- =====================================================fieldID="XX.006" fieldMnemonic="20 <xsd:element ref="ansi-nist:ImageHorizontalLineLengthPixelQuantity" minOccurs="0"/> 21 <!-- =====================================================fieldID="XX.009" fieldMnemonic="22 <xsd:element ref="ansi-nist:ImageHorizontalPixelDensityValue" minOccurs="0"/> 23 <!-- =====================================================fieldID="10.024" fieldMnemonic="24 <!-- =====================================================fieldID="16.024" fieldMnemonic="25 <!-- =====================================================fieldID="17.024" fieldMnemonic="26 <!-- =====================================================fieldID="99.102" fieldMnemonic="27 <xsd:element ref="ansi-nist:ImageQuality" minOccurs="0" maxOccurs="unbounded"/> 28 <!-- =====================================================not used =======================29 <xsd:element ref="ansi-nist:ImageRecordCategoryCode" minOccurs="0" maxOccurs="unbounded"/> 30 <!-- =====================================================not used =======================31 <xsd:element ref="ansi-nist:ImageReferenceIdentification" minOccurs="0" maxOccurs="unbound32 <!-- =====================================================fieldID="XX.008" fieldMnemonic="33 <xsd:element ref="ansi-nist:ImageScaleUnitsCode" minOccurs="0"/> 34 <!-- =====================================================fieldID="10.003" fieldMnemonic="35 <xsd:element ref="ansi-nist:ImageCategoryCode" minOccurs="0"/> 36 <!-- =====================================================fieldID="XX.007" fieldMnemonic="V37 <xsd:element ref="ansi-nist:ImageVerticalLineLengthPixelQuantity" minOccurs="0"/> 38 <!-- =====================================================fieldID="XX.010" fieldMnemonic="V39 <xsd:element ref="ansi-nist:ImageVerticalPixelDensityValue" minOccurs="0"/> 40 </xsd:sequence> 41 </xsd:extension> 42 </xsd:complexContent> 43 </xsd:complexType> 
Part 2 – Annex L 

307

1 <!-- ======================================================= --> 2 <!-- ==ansi-nist:NISTStandardMinutiaeType has been replaced by an itl: version == --> 3 <!-- ======================================================= --> 4 <xsd:complexType name="NISTStandardMinutiaeType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:complexContent> 11 <xsd:extension base="s:ComplexObjectType"> 12 <xsd:sequence> 13 <xsd:element ref="ansi-nist:MinutiaDetail" minOccurs="0" maxOccurs="unbounded"/> 14 <xsd:element ref="ansi-nist:MinutiaeQuantity" minOccurs="0" maxOccurs="unbounded"/> 15 <xsd:element ref="ansi-nist:MinutiaeReadingSystem" minOccurs="0" maxOccurs="unbounded"/> 16 <xsd:element ref="ansi-nist:MinutiaeRidgeCountIndicator" minOccurs="0" maxOccurs="unbounde17 <!-- ======================================================= --> 18 <!-- ==The three elements below belong in MinutiaType (singular)======= --> 19 <!-- ======================================================= --> 20 <xsd:element ref="ansi-nist:MinutiaQualityValue" minOccurs="0" maxOccurs="unbounded"/> 21 <xsd:element ref="ansi-nist:MinutiaCategory" minOccurs="0" maxOccurs="unbounded"/> 22 <xsd:element ref="ansi-nist:MinutiaRidgeCount" minOccurs="0" maxOccurs="unbounded"/> 23 </xsd:sequence> 24 </xsd:extension> 25 </xsd:complexContent> 26 </xsd:complexType> 27 <!-- ======================================================= --> 28 <xsd:simpleType name="OFRCodeSimpleType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:restriction base="xsd:token"> 35 <xsd:enumeration value="A"> 36 <xsd:annotation> 37 <xsd:documentation>Automatic, human never involved</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="E"> 41 <xsd:annotation> 42 <xsd:documentation>Automatic, human edited</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

308

1 </xsd:enumeration> 2 <xsd:enumeration value="M"> 3 <xsd:annotation> 4 <xsd:documentation>Manual</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="U"> 8 <xsd:annotation> 9 <xsd:documentation>Automatic, human unneeded</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 </xsd:restriction> 13 </xsd:simpleType> 14 <xsd:complexType name="OFRCodeType"> 15 <xsd:annotation> 16 <xsd:appinfo> 17 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 18 </xsd:appinfo> 19 </xsd:annotation> 20 <xsd:simpleContent> 21 <xsd:extension base="ansi-nist:OFRCodeSimpleType"> 22 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 23 </xsd:extension> 24 </xsd:simpleContent> 25 </xsd:complexType> 26 <!-- =====not used=========================================== --> 27 <xsd:complexType name="OrganizationDocumentCountType"> 28 <xsd:annotation> 29 <xsd:appinfo> 30 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 31 </xsd:appinfo> 32 </xsd:annotation> 33 <xsd:complexContent> 34 <xsd:extension base="s:ComplexObjectType"> 35 <xsd:sequence> 36 <xsd:element ref="ansi-nist:CodeManualCount" minOccurs="0" maxOccurs="unbounded"/> 37 <xsd:element ref="ansi-nist:NewsletterCount" minOccurs="0" maxOccurs="unbounded"/> 38 <xsd:element ref="ansi-nist:OperatingManualCount" minOccurs="0" maxOccurs="unbounded"/> 39 <xsd:element ref="ansi-nist:TOUCount" minOccurs="0" maxOccurs="unbounded"/> 40 </xsd:sequence> 41 </xsd:extension> 42 </xsd:complexContent> 43 </xsd:complexType> 
Part 2 – Annex L 

309

1 <!-- ======================================================= --> 2 <xsd:simpleType name="PASCodeSimpleType"> 3 <xsd:annotation> 4 <xsd:appinfo> 5 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 6 </xsd:appinfo> 7 </xsd:annotation> 8 <xsd:restriction base="xsd:token"> 9 <xsd:enumeration value="ANALOGUE VIDEO"> 

10 <xsd:annotation> 11 <xsd:documentation>Analogue Video</xsd:documentation> 12 </xsd:annotation> 13 </xsd:enumeration> 14 <xsd:enumeration value="DIGITAL CAMERA"> 15 <xsd:annotation> 16 <xsd:documentation>Digital Camera</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="DIGITAL VIDEO"> 20 <xsd:annotation> 21 <xsd:documentation>Digital Video</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="SCANNER"> 25 <xsd:annotation> 26 <xsd:documentation>Scanner</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="UNKNOWN"> 30 <xsd:annotation> 31 <xsd:documentation>Unknown</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="UNKNOWN PHOTO"> 35 <xsd:annotation> 36 <xsd:documentation>Unknown Photo</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="UNKNOWN VIDEO"> 40 <xsd:annotation> 41 <xsd:documentation>Unknown Video</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

310

1 <xsd:enumeration value="UNSPECIFIED"> 2 <xsd:annotation> 3 <xsd:documentation>Unspecified</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="VENDOR"> 7 <xsd:annotation> 8 <xsd:documentation>Vendor</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 </xsd:restriction> 12 </xsd:simpleType> 13 <xsd:complexType name="PASCodeType"> 14 <xsd:annotation> 15 <xsd:appinfo> 16 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 17 </xsd:appinfo> 18 </xsd:annotation> 19 <xsd:simpleContent> 20 <xsd:extension base="ansi-nist:PASCodeSimpleType"> 21 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 22 </xsd:extension> 23 </xsd:simpleContent> 24 </xsd:complexType> 25 <!-- ======================================================= --> 26 <xsd:simpleType name="PCCCodeSimpleType"> 27 <xsd:annotation> 28 <xsd:appinfo> 29 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 <xsd:restriction base="xsd:token"> 33 <xsd:enumeration value="ABSTRACT"> 34 <xsd:annotation> 35 <xsd:documentation>Abstractions</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="ANIMAL"> 39 <xsd:annotation> 40 <xsd:documentation>Animals and Animal Features</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="FLAG"> 
Part 2 – Annex L 

311

1 <xsd:annotation> 2 <xsd:documentation>Flags</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="HUMAN"> 6 <xsd:annotation> 7 <xsd:documentation>Human Forms and Features</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="OBJECT"> 11 <xsd:annotation> 12 <xsd:documentation>Objects</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="OTHER"> 16 <xsd:annotation> 17 <xsd:documentation>Other Images</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="PLANT"> 21 <xsd:annotation> 22 <xsd:documentation>Plants</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="SYMBOL"> 26 <xsd:annotation> 27 <xsd:documentation>Insignias & Symbols</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 </xsd:restriction> 31 </xsd:simpleType> 32 <xsd:complexType name="PCCCodeType"> 33 <xsd:annotation> 34 <xsd:appinfo> 35 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 <xsd:simpleContent> 39 <xsd:extension base="ansi-nist:PCCCodeSimpleType"> 40 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 41 </xsd:extension> 42 </xsd:simpleContent> 43 </xsd:complexType> 
Part 2 – Annex L 

312

1 <!-- ======================================================= --> 2 <xsd:simpleType name="PCSCodeSimpleType"> 3 <xsd:annotation> 4 <xsd:appinfo> 5 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 6 </xsd:appinfo> 7 </xsd:annotation> 8 <xsd:restriction base="xsd:token"> 9 <xsd:enumeration value="AW"> 

10 <xsd:annotation> 11 <xsd:documentation>Accidental whorl</xsd:documentation> 12 </xsd:annotation> 13 </xsd:enumeration> 14 <xsd:enumeration value="CP"> 15 <xsd:annotation> 16 <xsd:documentation>Central pocket loop</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="DL"> 20 <xsd:annotation> 21 <xsd:documentation>Double loop</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="LS"> 25 <xsd:annotation> 26 <xsd:documentation>Left slant loop</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="PA"> 30 <xsd:annotation> 31 <xsd:documentation>Plain arch </xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="PW"> 35 <xsd:annotation> 36 <xsd:documentation>Plain whorl</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="RL"> 40 <xsd:annotation> 41 <xsd:documentation>Radial loop</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

313

1 <xsd:enumeration value="RS"> 2 <xsd:annotation> 3 <xsd:documentation>Right slant loop</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="SR"> 7 <xsd:annotation> 8 <xsd:documentation>Scar</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="TA"> 12 <xsd:annotation> 13 <xsd:documentation>Tented arch </xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="UL"> 17 <xsd:annotation> 18 <xsd:documentation>Ulnar loop</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="UN"> 22 <xsd:annotation> 23 <xsd:documentation>Unknown or unclassifiable </xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="WN"> 27 <xsd:annotation> 28 <xsd:documentation>Whorl, type not designated</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="XX"> 32 <xsd:annotation> 33 <xsd:documentation>Amputation</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 </xsd:restriction> 37 </xsd:simpleType> 38 <xsd:complexType name="PCSCodeType"> 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> 
Part 2 – Annex L 

314

1 <xsd:simpleContent> 2 <xsd:extension base="ansi-nist:PCSCodeSimpleType"> 3 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 4 </xsd:extension> 5 </xsd:simpleContent> 6 </xsd:complexType> 7 <!-- ======================================================= --> 8 <xsd:simpleType name="POSCodeSimpleType"> 9 <xsd:annotation> 

10 <xsd:appinfo> 11 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 12 </xsd:appinfo> 13 </xsd:annotation> 14 <xsd:restriction base="xsd:token"> 15 <xsd:enumeration value="A"> 16 <xsd:annotation> 17 <xsd:documentation>Angled</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="D"> 21 <xsd:annotation> 22 <xsd:documentation>Determined 3D</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="F"> 26 <xsd:annotation> 27 <xsd:documentation>Full face frontal </xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="L"> 31 <xsd:annotation> 32 <xsd:documentation>Left profile 90 degree</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="R"> 36 <xsd:annotation> 37 <xsd:documentation>Right profile 90 degree</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 </xsd:restriction> 41 </xsd:simpleType> 42 <xsd:complexType name="POSCodeType"> 43 <xsd:annotation> 
Part 2 – Annex L 

315

1 <xsd:appinfo> 2 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 3 </xsd:appinfo> 4 </xsd:annotation> 5 <xsd:simpleContent> 6 <xsd:extension base="ansi-nist:POSCodeSimpleType"> 7 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 8 </xsd:extension> 9 </xsd:simpleContent> 

10 </xsd:complexType> 11 <!-- ======================================================= --> 12 <xsd:simpleType name="PPCCodeSimpleType"> 13 <xsd:annotation> 14 <xsd:appinfo> 15 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 16 </xsd:appinfo> 17 </xsd:annotation> 18 <xsd:restriction base="xsd:token"> 19 <xsd:enumeration value="20"> 20 <xsd:annotation> 21 <xsd:documentation>Unknown</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="21"> 25 <xsd:annotation> 26 <xsd:documentation>Right full</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="22"> 30 <xsd:annotation> 31 <xsd:documentation>Right writers</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="23"> 35 <xsd:annotation> 36 <xsd:documentation>Left full</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="24"> 40 <xsd:annotation> 41 <xsd:documentation>Left writers</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

316

1 <xsd:enumeration value="25"> 2 <xsd:annotation> 3 <xsd:documentation>Right lower</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="26"> 7 <xsd:annotation> 8 <xsd:documentation>Right upper</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="27"> 12 <xsd:annotation> 13 <xsd:documentation>Left lower</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="28"> 17 <xsd:annotation> 18 <xsd:documentation>Left upper</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="29"> 22 <xsd:annotation> 23 <xsd:documentation>Right other</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="30"> 27 <xsd:annotation> 28 <xsd:documentation>Left other</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="31"> 32 <xsd:annotation> 33 <xsd:documentation>Right interdigital</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="32"> 37 <xsd:annotation> 38 <xsd:documentation>Right thenar</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="33"> 42 <xsd:annotation> 43 <xsd:documentation>Right hypothenar</xsd:documentation> 
Part 2 – Annex L 

317

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="34"> 4 <xsd:annotation> 5 <xsd:documentation>Left interdigital</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="35"> 9 <xsd:annotation> 

10 <xsd:documentation>Left thenar</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="36"> 14 <xsd:annotation> 15 <xsd:documentation>Left hypothenar</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 </xsd:restriction> 19 </xsd:simpleType> 20 <xsd:complexType name="PPCCodeType"> 21 <xsd:annotation> 22 <xsd:appinfo> 23 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 24 </xsd:appinfo> 25 </xsd:annotation> 26 <xsd:simpleContent> 27 <xsd:extension base="ansi-nist:PPCCodeSimpleType"> 28 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 29 </xsd:extension> 30 </xsd:simpleContent> 31 </xsd:complexType> 32 <!-- ======================================================= --> 33 <xsd:simpleType name="PPLCodeSimpleType"> 34 <xsd:annotation> 35 <xsd:appinfo> 36 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 37 </xsd:appinfo> 38 </xsd:annotation> 39 <xsd:restriction base="xsd:token"> 40 <xsd:enumeration value="C"> 41 <xsd:annotation> 42 <xsd:documentation>Complete Shipment</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

318

1 </xsd:enumeration> 2 <xsd:enumeration value="P"> 3 <xsd:annotation> 4 <xsd:documentation>Partial Shipment</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 </xsd:restriction> 8 </xsd:simpleType> 9 <xsd:complexType name="PPLCodeType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:simpleContent> 16 <xsd:extension base="ansi-nist:PPLCodeSimpleType"> 17 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 18 </xsd:extension> 19 </xsd:simpleContent> 20 </xsd:complexType> 21 <!-- ======================================================= --> 22 <xsd:simpleType name="PSCCodeSimpleType"> 23 <xsd:annotation> 24 <xsd:appinfo> 25 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 26 </xsd:appinfo> 27 </xsd:annotation> 28 <xsd:restriction base="xsd:token"> 29 <xsd:enumeration value="ABBODY"> 30 <xsd:annotation> 31 <xsd:documentation>Abstract Body</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="ABBPART"> 35 <xsd:annotation> 36 <xsd:documentation>Abstract Body Parts</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="ABFACE"> 40 <xsd:annotation> 41 <xsd:documentation>Abstract Face</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

319

1 <xsd:enumeration value="ABSTRACT"> 2 <xsd:annotation> 3 <xsd:documentation>Abstract Animals</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="ANKLET"> 7 <xsd:annotation> 8 <xsd:documentation>Anklet</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="BIRD"> 12 <xsd:annotation> 13 <xsd:documentation>Birds (Cardinal, Hawk, etc.)</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="BLUEFL"> 17 <xsd:annotation> 18 <xsd:documentation>Blue Flowers</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="BODBND"> 22 <xsd:annotation> 23 <xsd:documentation>Body Band</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="BRACE"> 27 <xsd:annotation> 28 <xsd:documentation>Bracelet</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="BRIT"> 32 <xsd:annotation> 33 <xsd:documentation>British Flag</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="CAT"> 37 <xsd:annotation> 38 <xsd:documentation>Cats & Cat Heads</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="CONFED"> 42 <xsd:annotation> 43 <xsd:documentation>Confederate Flag</xsd:documentation> 
Part 2 – Annex L 

320

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="DOG"> 4 <xsd:annotation> 5 <xsd:documentation>Dogs & Dog Heads</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="DOMESTIC"> 9 <xsd:annotation> 

10 <xsd:documentation>Other Domestic Animals</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="DRAGON"> 14 <xsd:annotation> 15 <xsd:documentation>Dragons</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="DRAW"> 19 <xsd:annotation> 20 <xsd:documentation>Drawings of Flowers</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="FBODY"> 24 <xsd:annotation> 25 <xsd:documentation>Female Body</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="FBPART"> 29 <xsd:annotation> 30 <xsd:documentation>Female Body Parts</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="FFACE"> 34 <xsd:annotation> 35 <xsd:documentation>Female Face</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="FIGURE"> 39 <xsd:annotation> 40 <xsd:documentation>Figure(s)</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="FIRE"> 
Part 2 – Annex L 

321

1 <xsd:annotation> 2 <xsd:documentation>Fire</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="FRATERNAL"> 6 <xsd:annotation> 7 <xsd:documentation>Fraternal Symbols</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="FREEFRM"> 11 <xsd:annotation> 12 <xsd:documentation>Freeform Drawings</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="GANG"> 16 <xsd:annotation> 17 <xsd:documentation>Gang Symbols</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="HEADBND"> 21 <xsd:annotation> 22 <xsd:documentation>Head Band</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="HORSE"> 26 <xsd:annotation> 27 <xsd:documentation>Horses (Donkeys, Mules, etc.)</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="INSECT"> 31 <xsd:annotation> 32 <xsd:documentation>Spiders, Bugs, and Insects</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="LILY"> 36 <xsd:annotation> 37 <xsd:documentation>Lily</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="MABSTRACT"> 41 <xsd:annotation> 42 <xsd:documentation>Miscellaneous Abstract</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

322

1 </xsd:enumeration> 2 <xsd:enumeration value="MANIMAL"> 3 <xsd:annotation> 4 <xsd:documentation>Miscellaneous Animal Forms</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="MBODY"> 8 <xsd:annotation> 9 <xsd:documentation>Male Body</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="MBPART"> 13 <xsd:annotation> 14 <xsd:documentation>Male Body Parts</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 <xsd:enumeration value="MFACE"> 18 <xsd:annotation> 19 <xsd:documentation>Male Face</xsd:documentation> 20 </xsd:annotation> 21 </xsd:enumeration> 22 <xsd:enumeration value="MFLAG"> 23 <xsd:annotation> 24 <xsd:documentation>Miscellaneous Flags</xsd:documentation> 25 </xsd:annotation> 26 </xsd:enumeration> 27 <xsd:enumeration value="MHUMAN"> 28 <xsd:annotation> 29 <xsd:documentation>Miscellaneous Human Forms</xsd:documentation> 30 </xsd:annotation> 31 </xsd:enumeration> 32 <xsd:enumeration value="MILITARY"> 33 <xsd:annotation> 34 <xsd:documentation>Military Symbols</xsd:documentation> 35 </xsd:annotation> 36 </xsd:enumeration> 37 <xsd:enumeration value="MISC"> 38 <xsd:annotation> 39 <xsd:documentation>Miscellaneous Images</xsd:documentation> 40 </xsd:annotation> 41 </xsd:enumeration> 42 <xsd:enumeration value="MOBJECTS"> 43 <xsd:annotation> 
Part 2 – Annex L 

323

1 <xsd:documentation>Miscellaneous Objects</xsd:documentation> 2 </xsd:annotation> 3 </xsd:enumeration> 4 <xsd:enumeration value="MPLANT"> 5 <xsd:annotation> 6 <xsd:documentation>Miscellaneous Plants, Flowers, Vegetables</xsd:documentation> 7 </xsd:annotation> 8 </xsd:enumeration> 9 <xsd:enumeration value="MSYMBOLS"> 

10 <xsd:annotation> 11 <xsd:documentation>Miscellaneous Symbols</xsd:documentation> 12 </xsd:annotation> 13 </xsd:enumeration> 14 <xsd:enumeration value="MYTH"> 15 <xsd:annotation> 16 <xsd:documentation>Mythical (Unicorns, etc.)</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="NARCOTICS"> 20 <xsd:annotation> 21 <xsd:documentation>Narcotics</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="NATION"> 25 <xsd:annotation> 26 <xsd:documentation>National Symbols</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="NATURE"> 30 <xsd:annotation> 31 <xsd:documentation>Water & Nature Scenes(Rivers, Sky, Trees, etc.)</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="NAZI"> 35 <xsd:annotation> 36 <xsd:documentation>Nazi Flag</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="NECKLC"> 40 <xsd:annotation> 41 <xsd:documentation>Necklace</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

324

1 <xsd:enumeration value="PARTS"> 2 <xsd:annotation> 3 <xsd:documentation>Animal Parts</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="PLANE"> 7 <xsd:annotation> 8 <xsd:documentation>Airplanes</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="POLITIC"> 12 <xsd:annotation> 13 <xsd:documentation>Political Symbols</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="PROFESS"> 17 <xsd:annotation> 18 <xsd:documentation>Professional Symbols</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="REDFL"> 22 <xsd:annotation> 23 <xsd:documentation>Red Flowers</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="ROLES"> 27 <xsd:annotation> 28 <xsd:documentation>Roles (Knight, Witch, man, etc.)</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="ROSE"> 32 <xsd:annotation> 33 <xsd:documentation>Rose</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="SHIRT"> 37 <xsd:annotation> 38 <xsd:documentation>Shirt</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="SKULL"> 42 <xsd:annotation> 43 <xsd:documentation>Skulls</xsd:documentation> 
Part 2 – Annex L 

325

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="SLEEVE"> 4 <xsd:annotation> 5 <xsd:documentation>Sleeve</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="SNAKE"> 9 <xsd:annotation> 

10 <xsd:documentation>Snakes</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="SPORT"> 14 <xsd:annotation> 15 <xsd:documentation>Sports Figures (Football Player, Skier, etc.) or Sporting Objects (Foot16 etc.)</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="STATE"> 20 <xsd:annotation> 21 <xsd:documentation>State Flag</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="TRAIN"> 25 <xsd:annotation> 26 <xsd:documentation>Trains</xsd:documentation> 27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="TULIP"> 30 <xsd:annotation> 31 <xsd:documentation>Tulip</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="USA"> 35 <xsd:annotation> 36 <xsd:documentation>American Flag</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="VEHICLE"> 40 <xsd:annotation> 41 <xsd:documentation>Cars, Trucks, and Vehicles</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

326

1 <xsd:enumeration value="VESSEL"> 2 <xsd:annotation> 3 <xsd:documentation>Boats, Ships, & Other Vessels</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="VICIOUS"> 7 <xsd:annotation> 8 <xsd:documentation>Vicious Animals (Lions, etc.)</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="WEAP"> 12 <xsd:annotation> 13 <xsd:documentation>Weapons(Guns, Arrows, etc.)</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="WILD"> 17 <xsd:annotation> 18 <xsd:documentation>Other Wild Animals</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="WORDING"> 22 <xsd:annotation> 23 <xsd:documentation>Wording (Mom, Dad, Mary, ect.)</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="YELFL"> 27 <xsd:annotation> 28 <xsd:documentation>Yellow Flowers</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 </xsd:restriction> 32 </xsd:simpleType> 33 <xsd:complexType name="PSCCodeType"> 34 <xsd:annotation> 35 <xsd:appinfo> 36 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 37 </xsd:appinfo> 38 </xsd:annotation> 39 <xsd:simpleContent> 40 <xsd:extension base="ansi-nist:PSCCodeSimpleType"> 41 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 42 </xsd:extension> 43 </xsd:simpleContent> 
Part 2 – Annex L 

327

1 </xsd:complexType> 2 <!-- ======================================================= --> 3 <xsd:simpleType name="PXSCodeSimpleType"> 4 <xsd:annotation> 5 <xsd:appinfo> 6 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 7 </xsd:appinfo> 8 </xsd:annotation> 9 <xsd:restriction base="xsd:token"> 

10 <xsd:enumeration value="GLASSES"> 11 <xsd:annotation> 12 <xsd:documentation>Glasses</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="HAT"> 16 <xsd:annotation> 17 <xsd:documentation>Hat</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="OTHER"> 21 <xsd:annotation> 22 <xsd:documentation>Other</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="PHYSICAL"> 26 <xsd:annotation> 27 <xsd:documentation>Physical</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="SCARF"> 31 <xsd:annotation> 32 <xsd:documentation>Scarf</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 </xsd:restriction> 36 </xsd:simpleType> 37 <xsd:complexType name="PXSCodeType"> 38 <xsd:annotation> 39 <xsd:appinfo> 40 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 41 </xsd:appinfo> 42 </xsd:annotation> 43 <xsd:simpleContent> 
Part 2 – Annex L 

328

1 <xsd:extension base="ansi-nist:PXSCodeSimpleType"> 2 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 3 </xsd:extension> 4 </xsd:simpleContent> 5 </xsd:complexType> 6 <!-- ======================================================= --> 7 <!-- ansi-nist:PalmprintImageType has been replaced by itl:PalmprintImageType --> 8 <!-- ======================================================= --> 9 <xsd:complexType name="PalmprintImageType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:name="NISTImageType"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:complexContent> 16 <xsd:extension base="ansi-nist:NISTImageType"> 17 <xsd:sequence> 18 <xsd:element ref="ansi-nist:PalmPosition" minOccurs="0" maxOccurs="unbounded"/> 19 <xsd:element ref="ansi-nist:FingerprintImageImpressionCaptureCategory" minOccurs="0" maxOc20 </xsd:sequence> 21 </xsd:extension> 22 </xsd:complexContent> 23 </xsd:complexType> 24 <!-- ======================================================= --> 25 <xsd:complexType name="PhysicalFeatureColorDetailType"> 26 <xsd:annotation> 27 <xsd:appinfo> 28 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 29 </xsd:appinfo> 30 </xsd:annotation> 31 <xsd:complexContent> 32 <xsd:extension base="s:ComplexObjectType"> 33 <xsd:sequence> 34 <xsd:element ref="ansi-nist:PhysicalFeaturePrimaryColorCode"/> 35 <xsd:element ref="ansi-nist:PhysicalFeatureSecondaryColorCode" minOccurs="0" maxOccurs="un36 </xsd:sequence> 37 </xsd:extension> 38 </xsd:complexContent> 39 </xsd:complexType> 40 <!-- ======================================================= --> 41 <xsd:complexType name="PhysicalFeatureDescriptionType"> 42 <xsd:annotation> 43 <xsd:appinfo> 
Part 2 – Annex L 

329

1 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 2 </xsd:appinfo> 3 </xsd:annotation> 4 <xsd:complexContent> 5 <xsd:extension base="s:ComplexObjectType"> 6 <xsd:sequence> 7 <!-- =Req'd to be associated with 10.042=====fieldID="10.043" fieldMnemonic="COL" == --> 8 <xsd:element ref="ansi-nist:PhysicalFeatureColorDetail" minOccurs="0"/> 9 <!-- =============================SubFields for "10.042" fieldMnemonic="SMD" == --> 

10 <xsd:element ref="ansi-nist:PhysicalFeatureCategoryCode"/> 11 <xsd:element ref="ansi-nist:PhysicalFeatureClassCode"/> 12 <xsd:element ref="ansi-nist:PhysicalFeatureDescriptionText" minOccurs="0"/> 13 <xsd:element ref="ansi-nist:PhysicalFeatureSubClassCode"/> 14 </xsd:sequence> 15 </xsd:extension> 16 </xsd:complexContent> 17 </xsd:complexType> 18 <!-- ======================================================= --> 19 <xsd:complexType name="PhysicalFeatureImageType"> 20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:name="NISTImageType"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 <xsd:complexContent> 26 <xsd:extension base="ansi-nist:NISTImageType"> 27 <xsd:sequence> 28 <!-- =====================================================fieldID="10.042" fieldMnemonic="29 <xsd:element ref="ansi-nist:PhysicalFeatureDescriptionDetail" minOccurs="0" maxOccurs="unb30 <!-- =====================================================fieldID="10.040" fieldMnemonic="31 <xsd:element ref="ansi-nist:PhysicalFeatureNCICCode" minOccurs="0" maxOccurs="unbounded"/> 32 <!-- =====================================================fieldID="10.041" fieldMnemonic="33 <xsd:element ref="ansi-nist:PhysicalFeatureSize" minOccurs="0"/> 34 </xsd:sequence> 35 </xsd:extension> 36 </xsd:complexContent> 37 </xsd:complexType> 38 <!-- ======================================================= --> 39 <xsd:complexType name="PhysicalFeatureSizeType"> 40 <xsd:annotation> 41 <xsd:appinfo> 42 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

330

1 </xsd:annotation> 2 <xsd:complexContent> 3 <xsd:extension base="s:ComplexObjectType"> 4 <xsd:sequence> 5 <xsd:element ref="ansi-nist:PhysicalFeatureHeightMeasure"/> 6 <xsd:element ref="ansi-nist:PhysicalFeatureWidthMeasure"/> 7 </xsd:sequence> 8 </xsd:extension> 9 </xsd:complexContent> 

10 </xsd:complexType> 11 <!-- ======================================================= --> 12 <xsd:complexType name="PoseAngleType"> 13 <xsd:annotation> 14 <xsd:appinfo> 15 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 16 </xsd:appinfo> 17 </xsd:annotation> 18 <xsd:complexContent> 19 <xsd:extension base="s:ComplexObjectType"> 20 <xsd:sequence> 21 <xsd:element ref="ansi-nist:PosePitchAngleMeasure"/> 22 <xsd:element ref="ansi-nist:PosePitchUncertaintyValue" minOccurs="0"/> 23 <xsd:element ref="ansi-nist:PoseRollAngleMeasure"/> 24 <xsd:element ref="ansi-nist:PoseRollUncertaintyValue" minOccurs="0"/> 25 <xsd:element ref="ansi-nist:PoseYawAngleMeasure"/> 26 <xsd:element ref="ansi-nist:PoseYawUncertaintyValue" minOccurs="0"/> 27 </xsd:sequence> 28 </xsd:extension> 29 </xsd:complexContent> 30 </xsd:complexType> 31 <!-- ======not used========================================== --> 32 <xsd:complexType name="ProtectionOrderAugmentationType"> 33 <xsd:annotation> 34 <xsd:documentation>A data type for additional information about a protection order.</xsd:docum35 <xsd:appinfo> 36 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="AugmentationType"/> 37 </xsd:appinfo> 38 </xsd:annotation> 39 <xsd:complexContent> 40 <xsd:extension base="s:AugmentationType"> 41 <xsd:sequence> 42 <xsd:element ref="ansi-nist:ProtectionOrderBradyIndicator" minOccurs="0" maxOccurs="unboun43 <xsd:element ref="ansi-nist:ProtectionOrderConditionText" minOccurs="0" maxOccurs="unbound
Part 2 – Annex L 

331

1 </xsd:sequence> 2 </xsd:extension> 3 </xsd:complexContent> 4 </xsd:complexType> 5 <!-- ======================================================= --> 6 <xsd:complexType name="RTCCodeType"> 7 <xsd:annotation> 8 <xsd:appinfo> 9 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 

10 </xsd:appinfo> 11 </xsd:annotation> 12 <xsd:simpleContent> 13 <xsd:extension base="xsd:token"> 14 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 15 </xsd:extension> 16 </xsd:simpleContent> 17 </xsd:complexType> 18 <!-- ======not used==== ====================================== --> 19 <xsd:complexType name="RecordType"> 20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 <xsd:complexContent> 26 <xsd:extension base="s:ComplexObjectType"> 27 <xsd:sequence> 28 <xsd:element ref="ansi-nist:RecordRetentionIndicator" minOccurs="0" maxOccurs="unbounded"/29 <xsd:element ref="ansi-nist:RecordForwardOrganizations" minOccurs="0" maxOccurs="unbounded30 <xsd:element ref="ansi-nist:RecordImage" minOccurs="0" maxOccurs="unbounded"/> 31 <xsd:element ref="ansi-nist:RecordRapSheetRequestIndicator" minOccurs="0" maxOccurs="unbou32 <xsd:element ref="ansi-nist:RecordTransactionData" minOccurs="0" maxOccurs="unbounded"/> 33 </xsd:sequence> 34 </xsd:extension> 35 </xsd:complexContent> 36 </xsd:complexType> 37 <!-- ======================================================= --> 38 <xsd:simpleType name="SAPCodeSimpleType"> 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> 
Part 2 – Annex L 

332

1 <xsd:restriction base="xsd:token"> 2 <xsd:enumeration value="0"> 3 <xsd:annotation> 4 <xsd:documentation>Unknown</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 <xsd:enumeration value="1"> 8 <xsd:annotation> 9 <xsd:documentation>Latent facial</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="10"> 13 <xsd:annotation> 14 <xsd:documentation>Drivers license</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 <xsd:enumeration value="11"> 18 <xsd:annotation> 19 <xsd:documentation>ANSI full frontal</xsd:documentation> 20 </xsd:annotation> 21 </xsd:enumeration> 22 <xsd:enumeration value="12"> 23 <xsd:annotation> 24 <xsd:documentation>ANSI token</xsd:documentation> 25 </xsd:annotation> 26 </xsd:enumeration> 27 <xsd:enumeration value="13"> 28 <xsd:annotation> 29 <xsd:documentation>ISO full frontal</xsd:documentation> 30 </xsd:annotation> 31 </xsd:enumeration> 32 <xsd:enumeration value="14"> 33 <xsd:annotation> 34 <xsd:documentation>ISO token</xsd:documentation> 35 </xsd:annotation> 36 </xsd:enumeration> 37 <xsd:enumeration value="15"> 38 <xsd:annotation> 39 <xsd:documentation>PIV facial</xsd:documentation> 40 </xsd:annotation> 41 </xsd:enumeration> 42 <xsd:enumeration value="20"> 43 <xsd:annotation> 
Part 2 – Annex L 

333

1 <xsd:documentation>Legacy mugshot</xsd:documentation> 2 </xsd:annotation> 3 </xsd:enumeration> 4 <xsd:enumeration value="30"> 5 <xsd:annotation> 6 <xsd:documentation>Best practice level 30</xsd:documentation> 7 </xsd:annotation> 8 </xsd:enumeration> 9 <xsd:enumeration value="40"> 

10 <xsd:annotation> 11 <xsd:documentation>Best practice level 40</xsd:documentation> 12 </xsd:annotation> 13 </xsd:enumeration> 14 <xsd:enumeration value="50"> 15 <xsd:annotation> 16 <xsd:documentation>Best practice level 50</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="51"> 20 <xsd:annotation> 21 <xsd:documentation>Best practice level 51</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 </xsd:restriction> 25 </xsd:simpleType> 26 <xsd:complexType name="SAPCodeType"> 27 <xsd:annotation> 28 <xsd:appinfo> 29 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 <xsd:simpleContent> 33 <xsd:extension base="ansi-nist:SAPCodeSimpleType"> 34 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 35 </xsd:extension> 36 </xsd:simpleContent> 37 </xsd:complexType> 38 <!-- ======================================================= --> 39 <xsd:simpleType name="SECCodeSimpleType"> 40 <xsd:annotation> 41 <xsd:appinfo> 42 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

334

1 </xsd:annotation> 2 <xsd:restriction base="xsd:token"> 3 <xsd:enumeration value="BLK"> 4 <xsd:annotation> 5 <xsd:documentation>Black</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="BLU"> 9 <xsd:annotation> 

10 <xsd:documentation>Blue</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="BRO"> 14 <xsd:annotation> 15 <xsd:documentation>Brown</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="GRN"> 19 <xsd:annotation> 20 <xsd:documentation>Green</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="GRY"> 24 <xsd:annotation> 25 <xsd:documentation>Gray</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="HAZ"> 29 <xsd:annotation> 30 <xsd:documentation>Hazel</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="MAR"> 34 <xsd:annotation> 35 <xsd:documentation>Maroon</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="MUL"> 39 <xsd:annotation> 40 <xsd:documentation>Multicolored</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="PNK"> 
Part 2 – Annex L 

335

1 <xsd:annotation> 2 <xsd:documentation>Pink</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="XXX"> 6 <xsd:annotation> 7 <xsd:documentation>Unknown</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 </xsd:restriction> 11 </xsd:simpleType> 12 <xsd:complexType name="SECCodeType"> 13 <xsd:annotation> 14 <xsd:appinfo> 15 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 16 </xsd:appinfo> 17 </xsd:annotation> 18 <xsd:simpleContent> 19 <xsd:extension base="ansi-nist:SECCodeSimpleType"> 20 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 21 </xsd:extension> 22 </xsd:simpleContent> 23 </xsd:complexType> 24 <!-- ======================================================= --> 25 <xsd:simpleType name="SFPCodeSimpleType"> 26 <xsd:annotation> 27 <xsd:appinfo> 28 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 29 </xsd:appinfo> 30 </xsd:annotation> 31 <xsd:restriction base="xsd:token"> 32 <xsd:enumeration value="1"> 33 <xsd:annotation> 34 <xsd:documentation>A 2D feature point </xsd:documentation> 35 </xsd:annotation> 36 </xsd:enumeration> 37 </xsd:restriction> 38 </xsd:simpleType> 39 <xsd:complexType name="SFPCodeType"> 40 <xsd:annotation> 41 <xsd:appinfo> 42 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

336

1 </xsd:annotation> 2 <xsd:simpleContent> 3 <xsd:extension base="ansi-nist:SFPCodeSimpleType"> 4 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 5 </xsd:extension> 6 </xsd:simpleContent> 7 </xsd:complexType> 8 <!-- ======================================================= --> 9 <xsd:simpleType name="SHCCodeSimpleType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:restriction base="xsd:token"> 16 <xsd:enumeration value="BAL"> 17 <xsd:annotation> 18 <xsd:documentation>Bald</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="BLK"> 22 <xsd:annotation> 23 <xsd:documentation>Black</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="BLN"> 27 <xsd:annotation> 28 <xsd:documentation>Blonde or Strawberry</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="BLU"> 32 <xsd:annotation> 33 <xsd:documentation>Blue</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="BRO"> 37 <xsd:annotation> 38 <xsd:documentation>Brown</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="GRN"> 42 <xsd:annotation> 43 <xsd:documentation>Green</xsd:documentation> 
Part 2 – Annex L 

337

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="GRY"> 4 <xsd:annotation> 5 <xsd:documentation>Gray or Partially Gray</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="ONG"> 9 <xsd:annotation> 

10 <xsd:documentation>Orange</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="PLE"> 14 <xsd:annotation> 15 <xsd:documentation>Purple</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="PNK"> 19 <xsd:annotation> 20 <xsd:documentation>Pink</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="RED"> 24 <xsd:annotation> 25 <xsd:documentation>Red or Auburn</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="SDY"> 29 <xsd:annotation> 30 <xsd:documentation>Sandy</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="WHI"> 34 <xsd:annotation> 35 <xsd:documentation>White</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="XXX"> 39 <xsd:annotation> 40 <xsd:documentation>Unspecified or unknown </xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 </xsd:restriction> 
Part 2 – Annex L 

338

1 </xsd:simpleType> 2 <xsd:complexType name="SHCCodeType"> 3 <xsd:annotation> 4 <xsd:appinfo> 5 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 6 </xsd:appinfo> 7 </xsd:annotation> 8 <xsd:simpleContent> 9 <xsd:extension base="ansi-nist:SHCCodeSimpleType"> 

10 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 11 </xsd:extension> 12 </xsd:simpleContent> 13 </xsd:complexType> 14 <!-- ======================================================= --> 15 <xsd:simpleType name="SIGCodeSimpleType"> 16 <xsd:annotation> 17 <xsd:appinfo> 18 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 19 </xsd:appinfo> 20 </xsd:annotation> 21 <xsd:restriction base="xsd:token"> 22 <xsd:enumeration value="0"> 23 <xsd:annotation> 24 <xsd:documentation>Signature image of the subject</xsd:documentation> 25 </xsd:annotation> 26 </xsd:enumeration> 27 <xsd:enumeration value="1"> 28 <xsd:annotation> 29 <xsd:documentation>Signature image of the official processing the transaction</xsd:documen30 </xsd:annotation> 31 </xsd:enumeration> 32 </xsd:restriction> 33 </xsd:simpleType> 34 <xsd:complexType name="SIGCodeType"> 35 <xsd:annotation> 36 <xsd:appinfo> 37 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 38 </xsd:appinfo> 39 </xsd:annotation> 40 <xsd:simpleContent> 41 <xsd:extension base="ansi-nist:SIGCodeSimpleType"> 42 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 43 </xsd:extension> 
Part 2 – Annex L 

339

1 </xsd:simpleContent> 2 </xsd:complexType> 3 <!-- ======================================================= --> 4 <xsd:simpleType name="SLCCodeSimpleType"> 5 <xsd:annotation> 6 <xsd:appinfo> 7 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 <xsd:restriction base="xsd:token"> 11 <xsd:enumeration value="0"> 12 <xsd:annotation> 13 <xsd:documentation>No scale given</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="1"> 17 <xsd:annotation> 18 <xsd:documentation>Pixels per inch</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="2"> 22 <xsd:annotation> 23 <xsd:documentation>Pixels per centimeter</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 </xsd:restriction> 27 </xsd:simpleType> 28 <xsd:complexType name="SLCCodeType"> 29 <xsd:annotation> 30 <xsd:appinfo> 31 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 32 </xsd:appinfo> 33 </xsd:annotation> 34 <xsd:simpleContent> 35 <xsd:extension base="ansi-nist:SLCCodeSimpleType"> 36 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 37 </xsd:extension> 38 </xsd:simpleContent> 39 </xsd:complexType> 40 <!-- ======================================================= --> 41 <xsd:simpleType name="SMDCodeSimpleType"> 42 <xsd:annotation> 43 <xsd:appinfo> 
Part 2 – Annex L 

340

1 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 2 </xsd:appinfo> 3 </xsd:annotation> 4 <xsd:restriction base="xsd:token"> 5 <xsd:enumeration value="BRANDED"> 6 <xsd:annotation> 7 <xsd:documentation>Image burned into the skin using a branding iron or other form of heat.8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="CHEMICAL"> 11 <xsd:annotation> 12 <xsd:documentation>Image created by the use of chemicals to burn the image into the skin.<13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="CUT"> 16 <xsd:annotation> 17 <xsd:documentation>Image caused by an incision of the skin.</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="MARK"> 21 <xsd:annotation> 22 <xsd:documentation>Pattern resulting from needle or "Track" marks.</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="SCAR"> 26 <xsd:annotation> 27 <xsd:documentation>Healed scar tissue that was the result an accident or medical 28 procedure.</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="TATTOO"> 32 <xsd:annotation> 33 <xsd:documentation>A common tattoo or indelible image resulting from the pricking of the s34 matter.</xsd:documentation> 35 </xsd:annotation> 36 </xsd:enumeration> 37 </xsd:restriction> 38 </xsd:simpleType> 39 <xsd:complexType name="SMDCodeType"> 40 <xsd:annotation> 41 <xsd:appinfo> 42 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

341

1 </xsd:annotation> 2 <xsd:simpleContent> 3 <xsd:extension base="ansi-nist:SMDCodeSimpleType"> 4 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 5 </xsd:extension> 6 </xsd:simpleContent> 7 </xsd:complexType> 8 <!-- ======================================================= --> 9 <xsd:simpleType name="SRMCodeSimpleType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:restriction base="xsd:token"> 16 <xsd:enumeration value="B"> 17 <xsd:annotation> 18 <xsd:documentation>Bait money</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="C"> 22 <xsd:annotation> 23 <xsd:documentation>Counterfeit</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="R"> 27 <xsd:annotation> 28 <xsd:documentation>Ransom</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 </xsd:restriction> 32 </xsd:simpleType> 33 <xsd:complexType name="SRMCodeType"> 34 <xsd:annotation> 35 <xsd:appinfo> 36 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 37 </xsd:appinfo> 38 </xsd:annotation> 39 <xsd:simpleContent> 40 <xsd:extension base="ansi-nist:SRMCodeSimpleType"> 41 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 42 </xsd:extension> 43 </xsd:simpleContent> 
Part 2 – Annex L 

342

1 </xsd:complexType> 2 <!-- ======================================================= --> 3 <xsd:simpleType name="SRTCodeSimpleType"> 4 <xsd:annotation> 5 <xsd:appinfo> 6 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 7 </xsd:appinfo> 8 </xsd:annotation> 9 <xsd:restriction base="xsd:token"> 

10 <xsd:enumeration value="0"> 11 <xsd:annotation> 12 <xsd:documentation>Scanned uncompressed</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="1"> 16 <xsd:annotation> 17 <xsd:documentation>Scanned compressed</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="2"> 21 <xsd:annotation> 22 <xsd:documentation>Vector</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 </xsd:restriction> 26 </xsd:simpleType> 27 <xsd:complexType name="SRTCodeType"> 28 <xsd:annotation> 29 <xsd:appinfo> 30 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 31 </xsd:appinfo> 32 </xsd:annotation> 33 <xsd:simpleContent> 34 <xsd:extension base="ansi-nist:SRTCodeSimpleType"> 35 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 36 </xsd:extension> 37 </xsd:simpleContent> 38 </xsd:complexType> 39 <!-- ======================================================= --> 40 <xsd:simpleType name="SXSCodeSimpleType"> 41 <xsd:annotation> 42 <xsd:appinfo> 43 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 
Part 2 – Annex L 

343

1 </xsd:appinfo> 2 </xsd:annotation> 3 <xsd:restriction base="xsd:token"> 4 <xsd:enumeration value="BEARD"> 5 <xsd:annotation> 6 <xsd:documentation>Having Beard</xsd:documentation> 7 </xsd:annotation> 8 </xsd:enumeration> 9 <xsd:enumeration value="BLINK"> 

10 <xsd:annotation> 11 <xsd:documentation>Blinking (either or both eyes closed)</xsd:documentation> 12 </xsd:annotation> 13 </xsd:enumeration> 14 <xsd:enumeration value="CLEAR GLASSES"> 15 <xsd:annotation> 16 <xsd:documentation>Subject Wearing Clear Glasses</xsd:documentation> 17 </xsd:annotation> 18 </xsd:enumeration> 19 <xsd:enumeration value="DARK GLASSES"> 20 <xsd:annotation> 21 <xsd:documentation>Subject Wearing Dark or Visible Colored Glasses (medical)</xsd:document22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="DISTORTING CONDITION"> 25 <xsd:annotation> 26 <xsd:documentation>Having Distorting Medical Condition impacting Feature Point detection</27 </xsd:annotation> 28 </xsd:enumeration> 29 <xsd:enumeration value="EYES AWAY"> 30 <xsd:annotation> 31 <xsd:documentation>Looking away from the camera</xsd:documentation> 32 </xsd:annotation> 33 </xsd:enumeration> 34 <xsd:enumeration value="FROWNING"> 35 <xsd:annotation> 36 <xsd:documentation>Frowning</xsd:documentation> 37 </xsd:annotation> 38 </xsd:enumeration> 39 <xsd:enumeration value="HAT"> 40 <xsd:annotation> 41 <xsd:documentation>Head covering/hat </xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

344

1 <xsd:enumeration value="LEFT EYE PATCH"> 2 <xsd:annotation> 3 <xsd:documentation>Subject Wearing Left Eye Patch</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="MOUSTACHE"> 7 <xsd:annotation> 8 <xsd:documentation>Having Moustache</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="MOUTH OPEN"> 12 <xsd:annotation> 13 <xsd:documentation>Subject Having Mouth open </xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="NEUTRAL"> 17 <xsd:annotation> 18 <xsd:documentation>Neutral (non-smiling) with both eyes open and mouth closed)</xsd:docume19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="NO EAR"> 22 <xsd:annotation> 23 <xsd:documentation>Ear(s) obscured by hair</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="RAISED EYEBROWS"> 27 <xsd:annotation> 28 <xsd:documentation>Raising eyebrows</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="RIGHT EYE PATCH"> 32 <xsd:annotation> 33 <xsd:documentation>Subject Wearing Right Eye Patch</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="SCARF"> 37 <xsd:annotation> 38 <xsd:documentation>Wearing Scarf</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="SMILE"> 42 <xsd:annotation> 
Part 2 – Annex L 

345

1 <xsd:documentation>Smiling where the inside of the mouth and/or teeth is not exposed (clos2 jaw).</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="SQUINTING"> 6 <xsd:annotation> 7 <xsd:documentation>Squiting</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="TEETH VISIBLE"> 11 <xsd:annotation> 12 <xsd:documentation>Having Teeth visible</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="UNKNOWN"> 16 <xsd:annotation> 17 <xsd:documentation>Expression unspecified</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 </xsd:restriction> 21 </xsd:simpleType> 22 <xsd:complexType name="SXSCodeType"> 23 <xsd:annotation> 24 <xsd:appinfo> 25 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 26 </xsd:appinfo> 27 </xsd:annotation> 28 <xsd:simpleContent> 29 <xsd:extension base="ansi-nist:SXSCodeSimpleType"> 30 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 31 </xsd:extension> 32 </xsd:simpleContent> 33 </xsd:complexType> 34 <!-- ======================================================= --> 35 <xsd:complexType name="SignatureImageType"> 36 <xsd:annotation> 37 <xsd:appinfo> 38 <i:Base i:name="NISTImageType"/> 39 </xsd:appinfo> 40 </xsd:annotation> 41 <xsd:complexContent> 42 <xsd:extension base="ansi-nist:NISTImageType"> 43 <xsd:sequence> 
Part 2 – Annex L 

346

1 <xsd:element ref="ansi-nist:SignatureImageVectorRepresentation" minOccurs="0"/> 2 <!-- ====================================================================fieldMnemonic="SR3 <xsd:element ref="ansi-nist:SignatureRepresentationCode"/> 4 <!-- ====================================================================fieldMnemonic="SI5 <xsd:element ref="ansi-nist:SignatureCategoryCode"/> 6 </xsd:sequence> 7 </xsd:extension> 8 </xsd:complexContent> 9 </xsd:complexType> 

10 <!-- ======================================================= --> 11 <xsd:complexType name="SignatureImageVectorRepresentationType"> 12 <xsd:annotation> 13 <xsd:appinfo> 14 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 15 </xsd:appinfo> 16 </xsd:annotation> 17 <xsd:complexContent> 18 <xsd:extension base="s:ComplexObjectType"> 19 <xsd:sequence> 20 <xsd:element ref="ansi-nist:SignatureImageVector" minOccurs="2" maxOccurs="unbounded"/> 21 </xsd:sequence> 22 </xsd:extension> 23 </xsd:complexContent> 24 </xsd:complexType> 25 <!-- ======================================================= --> 26 <xsd:complexType name="SignatureImageVectorType"> 27 <xsd:annotation> 28 <xsd:appinfo> 29 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 <xsd:complexContent> 33 <xsd:extension base="s:ComplexObjectType"> 34 <xsd:sequence> 35 <xsd:element ref="ansi-nist:VectorPenPressureValue"/> 36 <xsd:element ref="ansi-nist:VectorPositionVerticalCoordinateValue"/> 37 <xsd:element ref="ansi-nist:VectorPositionHorizontalCoordinateValue"/> 38 </xsd:sequence> 39 </xsd:extension> 40 </xsd:complexContent> 41 </xsd:complexType> 42 <!-- ======================================================= --> 43 <xsd:simpleType name="TMZCodeSimpleType"> 
Part 2 – Annex L 

347

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:restriction base="xsd:token"> 7 <xsd:enumeration value="EDT"> 8 <xsd:annotation> 9 <xsd:documentation>Eastern Daylight Time</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:enumeration> 12 <xsd:enumeration value="EST"> 13 <xsd:annotation> 14 <xsd:documentation>Eastern Standard Time</xsd:documentation> 15 </xsd:annotation> 16 </xsd:enumeration> 17 </xsd:restriction> 18 </xsd:simpleType> 19 <xsd:complexType name="TMZCodeType"> 20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 <xsd:simpleContent> 26 <xsd:extension base="ansi-nist:TMZCodeSimpleType"> 27 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 28 </xsd:extension> 29 </xsd:simpleContent> 30 </xsd:complexType> 31 <!-- ======================================================= --> 32 <xsd:simpleType name="TOTCodeSimpleType"> 33 <xsd:annotation> 34 <xsd:appinfo> 35 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 <xsd:restriction base="xsd:token"> 39 <xsd:enumeration value="AMN"> 40 <xsd:annotation> 41 <xsd:documentation>AMNESIA VICTIM</xsd:documentation> 42 </xsd:annotation> 43 </xsd:enumeration> 
Part 2 – Annex L 

348

1 <xsd:enumeration value="CAR"> 2 <xsd:annotation> 3 <xsd:documentation>CRIMINAL TEN-PRINT SUBMISSION - ANSWER REQUIRED</xsd:documentation> 4 </xsd:annotation> 5 </xsd:enumeration> 6 <xsd:enumeration value="CFS"> 7 <xsd:annotation> 8 <xsd:documentation>COMPARISON FINGERPRINT IMAGE SUBMISSION</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:enumeration> 11 <xsd:enumeration value="CNA"> 12 <xsd:annotation> 13 <xsd:documentation>CRIMINAL TEN-PRINT SUBMISSION - NO ANSWER REQUIRED</xsd:documentation> 14 </xsd:annotation> 15 </xsd:enumeration> 16 <xsd:enumeration value="CPD"> 17 <xsd:annotation> 18 <xsd:documentation>CRIMINAL SUBJECT PHOTO DELETE REQUEST</xsd:documentation> 19 </xsd:annotation> 20 </xsd:enumeration> 21 <xsd:enumeration value="CPR"> 22 <xsd:annotation> 23 <xsd:documentation>CRIMINAL SUBJECT PHOTO REQUEST</xsd:documentation> 24 </xsd:annotation> 25 </xsd:enumeration> 26 <xsd:enumeration value="DEK"> 27 <xsd:annotation> 28 <xsd:documentation>KNOWN DECEASED</xsd:documentation> 29 </xsd:annotation> 30 </xsd:enumeration> 31 <xsd:enumeration value="DEU"> 32 <xsd:annotation> 33 <xsd:documentation>UNKNOWN DECEASED</xsd:documentation> 34 </xsd:annotation> 35 </xsd:enumeration> 36 <xsd:enumeration value="ELR"> 37 <xsd:annotation> 38 <xsd:documentation>EVALUATION LATENT FINGERPRINT IMAGE SUBMISSION</xsd:documentation> 39 </xsd:annotation> 40 </xsd:enumeration> 41 <xsd:enumeration value="FANC"> 42 <xsd:annotation> 43 <xsd:documentation>FEDERAL APPLICANT - NO CHARGE</xsd:documentation> 
Part 2 – Annex L 

349

1 </xsd:annotation> 2 </xsd:enumeration> 3 <xsd:enumeration value="FAUF"> 4 <xsd:annotation> 5 <xsd:documentation>FEDERAL APPLICANT - USER FEE</xsd:documentation> 6 </xsd:annotation> 7 </xsd:enumeration> 8 <xsd:enumeration value="FIS"> 9 <xsd:annotation> 

10 <xsd:documentation>FINGERPRINT IMAGE SUBMISSION</xsd:documentation> 11 </xsd:annotation> 12 </xsd:enumeration> 13 <xsd:enumeration value="IRQ"> 14 <xsd:annotation> 15 <xsd:documentation>FINGERPRINT IMAGE REQUEST</xsd:documentation> 16 </xsd:annotation> 17 </xsd:enumeration> 18 <xsd:enumeration value="LFFS"> 19 <xsd:annotation> 20 <xsd:documentation>LATENT FINGERPRINT FEATURES SEARCH</xsd:documentation> 21 </xsd:annotation> 22 </xsd:enumeration> 23 <xsd:enumeration value="LFIS"> 24 <xsd:annotation> 25 <xsd:documentation> FINGERPRINT IMAGE SEARCH</xsd:documentation> 26 </xsd:annotation> 27 </xsd:enumeration> 28 <xsd:enumeration value="LFS"> 29 <xsd:annotation> 30 <xsd:documentation>LATENT FINGERPRINT IMAGE SUBMISSION</xsd:documentation> 31 </xsd:annotation> 32 </xsd:enumeration> 33 <xsd:enumeration value="LPNQ"> 34 <xsd:annotation> 35 <xsd:documentation>LATENT PENETRATION QUERY</xsd:documentation> 36 </xsd:annotation> 37 </xsd:enumeration> 38 <xsd:enumeration value="LSRQ"> 39 <xsd:annotation> 40 <xsd:documentation>LATENT REPOSITORY STATISTICS QUERY</xsd:documentation> 41 </xsd:annotation> 42 </xsd:enumeration> 43 <xsd:enumeration value="MAP"> 
Part 2 – Annex L 

350

1 <xsd:annotation> 2 <xsd:documentation>MISCELLANEOUS APPLICANT - CIVIL</xsd:documentation> 3 </xsd:annotation> 4 </xsd:enumeration> 5 <xsd:enumeration value="MCS"> 6 <xsd:annotation> 7 <xsd:documentation>MAJOR CASE IMAGE SUBMISSION</xsd:documentation> 8 </xsd:annotation> 9 </xsd:enumeration> 

10 <xsd:enumeration value="MPR"> 11 <xsd:annotation> 12 <xsd:documentation>MISSING PERSON</xsd:documentation> 13 </xsd:annotation> 14 </xsd:enumeration> 15 <xsd:enumeration value="NFUF"> 16 <xsd:annotation> 17 <xsd:documentation>NON-FEDERAL APPLICANT USER FEE</xsd:documentation> 18 </xsd:annotation> 19 </xsd:enumeration> 20 <xsd:enumeration value="TPFS"> 21 <xsd:annotation> 22 <xsd:documentation>TEN-PRINT FINGERPRINT FEATURES SEARCH</xsd:documentation> 23 </xsd:annotation> 24 </xsd:enumeration> 25 <xsd:enumeration value="TPIS"> 26 <xsd:annotation> 27 <xsd:documentation>TEN-PRINT FINGERPRINT IMAGE SEARCH</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="ULAC"> 31 <xsd:annotation> 32 <xsd:documentation>UNSOLVED LATENT ADD CONFIRM REQUEST</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="ULD"> 36 <xsd:annotation> 37 <xsd:documentation>UNSOLVED LATENT RECORD DELETE REQUEST</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 </xsd:restriction> 41 </xsd:simpleType> 42 <xsd:complexType name="TOTCodeType"> 43 <xsd:annotation> 
Part 2 – Annex L 

351

1 <xsd:appinfo> 2 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 3 </xsd:appinfo> 4 </xsd:annotation> 5 <xsd:simpleContent> 6 <xsd:extension base="ansi-nist:TOTCodeSimpleType"> 7 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 8 </xsd:extension> 9 </xsd:simpleContent> 

10 </xsd:complexType> 11 <!-- ======================================================= --> 12 <xsd:simpleType name="TSRCodeSimpleType"> 13 <xsd:annotation> 14 <xsd:appinfo> 15 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 16 </xsd:appinfo> 17 </xsd:annotation> 18 <xsd:restriction base="xsd:token"> 19 <xsd:enumeration value="P"> 20 <xsd:annotation> 21 <xsd:documentation>Pre-commission candidate record with fingerprints</xsd:documentation> 22 </xsd:annotation> 23 </xsd:enumeration> 24 <xsd:enumeration value="V"> 25 <xsd:annotation> 26 <xsd:documentation>Civil submission in support of the National Child Protection Act of 27 1993</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 </xsd:restriction> 31 </xsd:simpleType> 32 <xsd:complexType name="TSRCodeType"> 33 <xsd:annotation> 34 <xsd:appinfo> 35 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 <xsd:simpleContent> 39 <xsd:extension base="ansi-nist:TSRCodeSimpleType"> 40 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 41 </xsd:extension> 42 </xsd:simpleContent> 43 </xsd:complexType> 
Part 2 – Annex L 

352

1 <!-- ======================================================= --> 2 <xsd:complexType name="TransactionCharacterSetDirectoryType"> 3 <xsd:annotation> 4 <xsd:appinfo> 5 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 6 </xsd:appinfo> 7 </xsd:annotation> 8 <xsd:complexContent> 9 <xsd:extension base="s:ComplexObjectType"> 

10 <xsd:sequence> 11 <xsd:element ref="ansi-nist:CharacterSetCommonNameCode"/> 12 <xsd:element ref="ansi-nist:CharacterSetIndexCode"/> 13 <xsd:element ref="ansi-nist:CharacterSetVersionIdentification" minOccurs="0"/> 14 </xsd:sequence> 15 </xsd:extension> 16 </xsd:complexContent> 17 </xsd:complexType> 18 <!-- ======================================================= --> 19 <xsd:complexType name="TransactionContentSummaryType"> 20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 <xsd:complexContent> 26 <xsd:extension base="s:ComplexObjectType"> 27 <xsd:sequence> 28 <xsd:element ref="ansi-nist:ContentFirstRecordCategoryCode"/> 29 <xsd:element ref="ansi-nist:ContentRecordCount"/> 30 <xsd:element ref="ansi-nist:ContentRecordSummary" maxOccurs="unbounded"/> 31 </xsd:sequence> 32 </xsd:extension> 33 </xsd:complexContent> 34 </xsd:complexType> 35 <!-- ======================================================= --> 36 <xsd:complexType name="TransactionDomainType"> 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:complexContent> 43 <xsd:extension base="s:ComplexObjectType"> 
Part 2 – Annex L 

353

1 <xsd:sequence> 2 <xsd:element ref="ansi-nist:DomainVersionNumberIdentification"/> 3 <xsd:element ref="ansi-nist:OrganizationName" minOccurs="0"/> 4 </xsd:sequence> 5 </xsd:extension> 6 </xsd:complexContent> 7 </xsd:complexType> 8 <!-- ======================================================= --> 9 <xsd:complexType name="TransactionImageResolutionType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:complexContent> 16 <xsd:extension base="s:ComplexObjectType"> 17 <xsd:sequence> 18 <!-- ============================================================================= fieldID19 fieldMnemonic="NSR" == --> 20 <xsd:element ref="ansi-nist:NativeScanningResolutionValue"/> 21 <!-- ============================================================================= fieldID22 fieldMnemonic="NTR" == --> 23 <xsd:element ref="ansi-nist:NominalTransmittingResolutionValue"/> 24 </xsd:sequence> 25 </xsd:extension> 26 </xsd:complexContent> 27 </xsd:complexType> 28 <!-- ======================================================= --> 29 <xsd:complexType name="TransactionType"> 30 <xsd:annotation> 31 <xsd:documentation>A data type for information pertaining to the transaction being 32 transmitted.</xsd:documentation> 33 <xsd:appinfo> 34 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 35 </xsd:appinfo> 36 </xsd:annotation> 37 <xsd:complexContent> 38 <xsd:extension base="s:ComplexObjectType"> 39 <xsd:sequence> 40 <!-- =====================================================not used =======================41 <xsd:element ref="ansi-nist:TransactionSearchRequestCategoryCode" minOccurs="0" maxOccurs=42 <!-- =====================================================not used =======================43 <xsd:element ref="ansi-nist:TransactionSubmissionMilitaryCode" minOccurs="0" maxOccurs="un
Part 2 – Annex L 

354

1 <!-- ============================================================================= fieldID2 fieldMnemonic="DAT" == --> 3 <xsd:element ref="ansi-nist:TransactionDate"/> 4 <!-- ============================================================================= fieldID5 fieldMnemonic="DAI" == --> 6 <xsd:element ref="ansi-nist:TransactionDestinationOrganization"/> 7 <!-- =====================================================not used =======================8 <xsd:element ref="ansi-nist:TransactionHeaderText" minOccurs="0" maxOccurs="unbounded"/> 9 <!-- =====================================================not used =======================

10 <xsd:element ref="ansi-nist:TransactionKeyText" minOccurs="0" maxOccurs="unbounded"/> 11 <!-- =====================================================not used =======================12 <xsd:element ref="ansi-nist:TransactionKeyTranslationText" minOccurs="0" maxOccurs="unboun13 <!-- =====================================================not used =======================14 <xsd:element ref="ansi-nist:TransactionOrganization" minOccurs="0" maxOccurs="unbounded"/> 15 <!-- ============================================================================= fieldID16 fieldMnemonic="ORI" == --> 17 <xsd:element ref="ansi-nist:TransactionOriginatingOrganization"/> 18 <!-- =====================================================not used =======================19 <xsd:element ref="ansi-nist:TransactionReasonText" minOccurs="0" maxOccurs="unbounded"/> 20 <!-- =====================================================not used =======================21 <xsd:element ref="ansi-nist:TransactionUserIdentification" minOccurs="0" maxOccurs="unboun22 <!-- ============================================================================= fieldID23 fieldMnemonic="GMT" == --> 24 <xsd:element ref="ansi-nist:TransactionUTCDate" minOccurs="0"/> 25 <!-- ============================================================================= fieldID26 fieldMnemonic="TCN" == --> 27 <xsd:element ref="ansi-nist:TransactionControlIdentification"/> 28 <!-- ============================================================================= fieldID29 fieldMnemonic="TCR" == --> 30 <xsd:element ref="ansi-nist:TransactionControlReferenceIdentification" minOccurs="0"/> 31 <!-- ============================================================================= fieldID32 fieldMnemonic="DOM" == --> 33 <xsd:element ref="ansi-nist:TransactionDomain" minOccurs="0"/> 34 <!-- ============================================================================= fieldID35 fieldMnemonic="NSR" == --> 36 <!-- ============================================================================= fieldID37 fieldMnemonic="NTR" == --> 38 <xsd:element ref="ansi-nist:TransactionImageResolutionDetails"/> 39 <!-- ============================================================================= fieldID40 fieldMnemonic="VER" == --> 41 <xsd:element ref="ansi-nist:TransactionMajorVersionValue"/> 42 <xsd:element ref="ansi-nist:TransactionMinorVersionValue"/> 
Part 2 – Annex L 

355

1 <!-- ============================================================================= fieldID2 fieldMnemonic="PRY" == --> 3 <xsd:element ref="ansi-nist:TransactionPriorityValue" minOccurs="0"/> 4 <!-- ============================================================================= fieldID5 fieldMnemonic="TOT" == --> 6 <xsd:element ref="ansi-nist:TransactionCategoryCode"/> 7 <!-- ============================================================================= fieldID8 fieldMnemonic="CNT" == --> 9 <xsd:element ref="ansi-nist:TransactionContentSummary"/> 

10 <!-- ============================================================================= fieldID11 fieldMnemonic="DCS" == --> 12 <xsd:element ref="ansi-nist:TransactionCharacterSetDirectory" minOccurs="0" maxOccurs="unb13 </xsd:sequence> 14 </xsd:extension> 15 </xsd:complexContent> 16 </xsd:complexType> 17 <!-- ======================================================= --> 18 <xsd:simpleType name="VODCodeSimpleType"> 19 <xsd:annotation> 20 <xsd:appinfo> 21 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 22 </xsd:appinfo> 23 </xsd:annotation> 24 <xsd:restriction base="xsd:token"> 25 <xsd:enumeration value="A"> 26 <xsd:annotation> 27 <xsd:documentation>GANICBAOO INTEREST (Atlanta, Georgia)</xsd:documentation> 28 </xsd:annotation> 29 </xsd:enumeration> 30 <xsd:enumeration value="C"> 31 <xsd:annotation> 32 <xsd:documentation>ILNICBCOO INTEREST (Chicago, Illinois)</xsd:documentation> 33 </xsd:annotation> 34 </xsd:enumeration> 35 <xsd:enumeration value="D"> 36 <xsd:annotation> 37 <xsd:documentation>TXNICBDOO INTEREST (Dallas, Texas)</xsd:documentation> 38 </xsd:annotation> 39 </xsd:enumeration> 40 <xsd:enumeration value="N"> 41 <xsd:annotation> 42 <xsd:documentation>NYNICBNOO INTEREST (New York, New York)</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

356

1 </xsd:enumeration> 2 <xsd:enumeration value="S"> 3 <xsd:annotation> 4 <xsd:documentation>CANICBSOO INTEREST (San Francisco, California)</xsd:documentation> 5 </xsd:annotation> 6 </xsd:enumeration> 7 </xsd:restriction> 8 </xsd:simpleType> 9 <xsd:complexType name="VODCodeType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:namespace="http://niem.gov/niem/structures/2.0" i:name="Object"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 <xsd:simpleContent> 16 <xsd:extension base="ansi-nist:VODCodeSimpleType"> 17 <xsd:attributeGroup ref="s:SimpleObjectAttributeGroup"/> 18 </xsd:extension> 19 </xsd:simpleContent> 20 </xsd:complexType> 21 <!-- ====not used============================================ --> 22 <xsd:element name="ActivityAgencyNotificationIndicator" type="niem-xsd:boolean" nillable="true"> 23 <xsd:annotation> 24 <xsd:documentation>A flag which indicates the Investigative Agency is to be notified of any qu25 includes this Criminal Justice Entry. </xsd:documentation> 26 </xsd:annotation> 27 </xsd:element> 28 <!-- ====not used============================================ --> 29 <xsd:element name="ActivityApprovalDate" type="nc:DateType" nillable="true"> 30 <xsd:annotation> 31 <xsd:documentation>Date the information was reviewed, signed off, or otherwise approved as a 32 whole.</xsd:documentation> 33 </xsd:annotation> 34 </xsd:element> 35 <!-- ========not used============================================ --> 36 <xsd:element name="ActivityAugmentation" type="ansi-nist:ActivityAugmentationType" substitutionGro37 <xsd:annotation> 38 <xsd:documentation>An augmentation that applies to type nc:ActivityType</xsd:documentation> 39 <xsd:appinfo> 40 <i:AppliesTo i:namespace="http://niem.gov/niem/niem-core/2.0" i:name="ActivityType"/> 41 </xsd:appinfo> 42 </xsd:annotation> 43 </xsd:element> 
Part 2 – Annex L 

357

1 <!-- ========not used============================================ --> 2 <xsd:element name="ActivityEndTimeZoneCode" type="ansi-nist:TMZCodeType" nillable="true"> 3 <xsd:annotation> 4 <xsd:documentation>Time Zone corresponding to the Activity End time. EDT during the months of 5 Time.</xsd:documentation> 6 </xsd:annotation> 7 </xsd:element> 8 <!-- ========not used============================================ --> 9 <xsd:element name="ActivityTimeZoneCode" type="ansi-nist:TMZCodeType" nillable="true"> 

10 <xsd:annotation> 11 <xsd:documentation>Time Zone corresponding to the Activity time. EDT during the months of Day12 Time.</xsd:documentation> 13 </xsd:annotation> 14 </xsd:element> 15 <!-- ======================================================= --> 16 <xsd:element name="CBEFFCategoryCode" type="nc:TextType"> 17 <xsd:annotation> 18 <xsd:documentation>The type of biometric technology.</xsd:documentation> 19 </xsd:annotation> 20 </xsd:element> 21 <!-- ======================================================= --> 22 <xsd:element name="CBEFFFormatCategoryIdentification" type="nc:IdentificationType"> 23 <xsd:annotation> 24 <xsd:documentation>The identifier assigned to the format by the owner.</xsd:documentation> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="CBEFFFormatOwnerIdentification" type="nc:IdentificationType"> 29 <xsd:annotation> 30 <xsd:documentation>The identifier assigned to the registered owner of the biometric format use31 record.</xsd:documentation> 32 </xsd:annotation> 33 </xsd:element> 34 <!-- ======================================================= --> 35 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="CBEFFImage" type="ansi-nist:CBEFFImag36 <xsd:annotation> 37 <xsd:appinfo> 38 <i:Base i:name="RecordImage"/> 39 </xsd:appinfo> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ======================================================= --> 43 <xsd:element name="CBEFFVersionIdentification" type="nc:IdentificationType"> 
Part 2 – Annex L 

358

1 <xsd:annotation> 2 <xsd:documentation>The version of CBEFF specification that this record conforms to.</xsd:docum3 </xsd:annotation> 4 </xsd:element> 5 <!-- ======================================================= --> 6 <xsd:element name="CaptureDate" type="nc:DateType" nillable="true"> 7 <xsd:annotation> 8 <xsd:documentation>Date image was captured.</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:element> 11 <!-- ======================================================= --> 12 <xsd:element name="CaptureDescription" abstract="true"> 13 <xsd:annotation> 14 <xsd:documentation>Type of human monitoring used to capture an image.</xsd:documentation> 15 </xsd:annotation> 16 </xsd:element> 17 <!-- ======================================================= --> 18 <xsd:element substitutionGroup="ansi-nist:CaptureDescription" name="CaptureDescriptionCode" type="19 nist:DMMCodeType"> 20 <xsd:annotation> 21 <xsd:documentation>Table 25 level of human monitoring of image capture.</xsd:documentation> 22 <xsd:appinfo> 23 <i:Base i:name="CaptureDescription"/> 24 </xsd:appinfo> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ========not used=============================================== --> 28 <xsd:element substitutionGroup="ansi-nist:CaptureDescription" name="CaptureDescriptionText" type="29 nillable="true"> 30 <xsd:annotation> 31 <xsd:documentation>Type of human monitoring used to capture an image.</xsd:documentation> 32 <xsd:appinfo> 33 <i:Base i:name="CaptureDescription"/> 34 </xsd:appinfo> 35 </xsd:annotation> 36 </xsd:element> 37 <!-- ======================================================= --> 38 <xsd:element name="CaptureDeviceGlobalIdentification" type="nc:IdentificationType"> 39 <xsd:annotation> 40 <xsd:documentation>A globally unique identifier.</xsd:documentation> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

359

1 <xsd:element name="CaptureDeviceIdentification" type="nc:IdentificationType"> 2 <xsd:annotation> 3 <xsd:documentation>A string identifying the device or source of the image data.</xsd:documenta4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="CaptureDeviceMakeText" type="nc:TextType"> 8 <xsd:annotation> 9 <xsd:documentation>The make of the image capture device.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="CaptureDeviceModelText" type="nc:TextType"> 14 <xsd:annotation> 15 <xsd:documentation>The model of the image capture device.</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ======================================================= --> 19 <xsd:element name="CaptureDeviceMonitoringMode" abstract="true"/> 20 <!-- ======================================================= --> 21 <xsd:element substitutionGroup="ansi-nist:CaptureDeviceMonitoringMode" name="CaptureDeviceMonitori22 type="nc:TextType"> 23 <xsd:annotation> 24 <xsd:appinfo> 25 <i:Base i:name="CaptureDeviceMonitoringMode"/> 26 </xsd:appinfo> 27 </xsd:annotation> 28 </xsd:element> 29 <!-- ========not used=============================================== --> 30 <xsd:element substitutionGroup="ansi-nist:CaptureDeviceMonitoringMode" name="CaptureDeviceMonitori31 type="nc:TextType" nillable="true"> 32 <xsd:annotation> 33 <xsd:appinfo> 34 <i:Base i:name="CaptureDeviceMonitoringMode"/> 35 </xsd:appinfo> 36 </xsd:annotation> 37 </xsd:element> 38 <!-- ======================================================= --> 39 <xsd:element name="CaptureDeviceSerialNumberText" type="nc:TextType"> 40 <xsd:annotation> 41 <xsd:documentation>The serial number of the image capture device.</xsd:documentation> 42 </xsd:annotation> 43 </xsd:element> 
Part 2 – Annex L 

360

1 <!-- ======================================================= --> 2 <xsd:element name="CaptureHorizontalPixelDensityValue" type="niem-xsd:nonNegativeInteger"> 3 <xsd:annotation> 4 <xsd:documentation>Transmitted pixel density in horizontal direction.</xsd:documentation> 5 </xsd:annotation> 6 </xsd:element> 7 <!-- ======================================================= --> 8 <xsd:element name="CaptureOrganization" type="nc:OrganizationType"> 9 <xsd:annotation> 

10 <xsd:documentation>The organization that originally captured the facial or SMT image contained 11 record.</xsd:documentation> 12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element name="CaptureResolution" abstract="true"> 16 <xsd:annotation> 17 <xsd:documentation>A minimum or native resolution indicator.</xsd:documentation> 18 </xsd:annotation> 19 </xsd:element> 20 <!-- ======================================================= --> 21 <xsd:element substitutionGroup="ansi-nist:CaptureResolution" name="CaptureResolutionCode" type="an22 nist:ISRCodeType"> 23 <xsd:annotation> 24 <xsd:documentation>Indicates the minimum or native resolution indicator.</xsd:documentation> 25 <xsd:appinfo> 26 <i:Base i:name="CaptureResolution"/> 27 </xsd:appinfo> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ========not used=============================================== --> 31 <xsd:element substitutionGroup="ansi-nist:CaptureResolution" name="CaptureResolutionText" type="nc32 nillable="true"> 33 <xsd:annotation> 34 <xsd:documentation>A minimum or native resolution indicator.</xsd:documentation> 35 <xsd:appinfo> 36 <i:Base i:name="CaptureResolution"/> 37 </xsd:appinfo> 38 </xsd:annotation> 39 </xsd:element> 40 <!-- ======================================================= --> 41 <xsd:element name="CaptureSource" abstract="true"> 42 <xsd:annotation> 43 <xsd:documentation>Source of an image.</xsd:documentation> 
Part 2 – Annex L 

361

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ======================================================= --> 4 <xsd:element substitutionGroup="ansi-nist:CaptureSource" name="CaptureSourceCode" type="ansi-nist:5 <xsd:annotation> 6 <xsd:documentation>Indicates the classification of the source of the image.</xsd:documentation7 <xsd:appinfo> 8 <i:Base i:name="CaptureSource"/> 9 </xsd:appinfo> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ========not used=============================================== --> 13 <xsd:element substitutionGroup="ansi-nist:CaptureSource" name="CaptureSourceText" type="nc:TextTyp14 <xsd:annotation> 15 <xsd:documentation>Source of an image.</xsd:documentation> 16 <xsd:appinfo> 17 <i:Base i:name="CaptureSource"/> 18 </xsd:appinfo> 19 </xsd:annotation> 20 </xsd:element> 21 <!-- ======================================================= --> 22 <xsd:element name="CaptureVerticalPixelDensityValue" type="niem-xsd:nonNegativeInteger"> 23 <xsd:annotation> 24 <xsd:documentation>Transmitted pixel density in the vertical direction.</xsd:documentation> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="CharacterSetCommonNameCode" type="ansi-nist:CSNCodeType"> 29 <xsd:annotation> 30 <xsd:documentation>Indicates the common name for the character set associated with the index n31 references an associated character set throughout a transaction.</xsd:documentation> 32 </xsd:annotation> 33 </xsd:element> 34 <!-- ======================================================= --> 35 <xsd:element name="CharacterSetIndexCode" type="ansi-nist:CSICodeType"> 36 <xsd:annotation> 37 <xsd:documentation>Indicates the three-character identifier for the character set index number 38 associated character set throughout a transaction.</xsd:documentation> 39 </xsd:annotation> 40 </xsd:element> 41 <!-- ======================================================= --> 42 <xsd:element name="CharacterSetVersionIdentification" type="nc:IdentificationType"> 43 <xsd:annotation> 
Part 2 – Annex L 

362

1 <xsd:documentation>A specific character set version.</xsd:documentation> 2 </xsd:annotation> 3 </xsd:element> 4 <!-- ========not used============================================ --> 5 <xsd:element name="CodeManualCount" type="niem-xsd:nonNegativeInteger" nillable="true"> 6 <xsd:annotation> 7 <xsd:documentation>The number of NCIC Code Manuals needed.</xsd:documentation> 8 </xsd:annotation> 9 </xsd:element> 

10 <!-- ======================================================= --> 11 <xsd:element name="ContentFirstRecordCategoryCode" type="ansi-nist:RTCCodeType"> 12 <xsd:annotation> 13 <xsd:documentation>Type code must be 01</xsd:documentation> 14 </xsd:annotation> 15 </xsd:element> 16 <!-- ======================================================= --> 17 <xsd:element name="ContentRecordCount" type="niem-xsd:nonNegativeInteger"> 18 <xsd:annotation> 19 <xsd:documentation>Sum of records, not counting the Type-01 transaction record.</xsd:documenta20 </xsd:annotation> 21 </xsd:element> 22 <!-- ======================================================= --> 23 <xsd:element name="ContentRecordSummary" type="ansi-nist:ContentRecordType"> 24 <xsd:annotation> 25 <xsd:documentation>One sub-field entry for each logical record in this file other than the Typ26 record.</xsd:documentation> 27 </xsd:annotation> 28 </xsd:element> 29 <!-- ======================================================= --> 30 <xsd:element name="DomainVersionNumberIdentification" type="nc:IdentificationType"> 31 <xsd:annotation> 32 <xsd:documentation>Unique version number of an implementation.</xsd:documentation> 33 </xsd:annotation> 34 </xsd:element> 35 <!-- ======================================================= --> 36 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="FaceImage" type="ansi-nist:FaceImageTy37 <xsd:annotation> 38 <xsd:appinfo> 39 <i:Base i:name="RecordImage"/> 40 </xsd:appinfo> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

363

1 <xsd:element name="FaceImage3DPoseAngle" type="ansi-nist:PoseAngleType"> 2 <xsd:annotation> 3 <xsd:documentation>The angular offsets of the subject from a full face or a profile, for pose 4 'D'.</xsd:documentation> 5 </xsd:annotation> 6 </xsd:element> 7 <!-- ======================================================= --> 8 <xsd:element name="FaceImageAcquisitionProfile" abstract="true"> 9 <xsd:annotation> 

10 <xsd:documentation>The criteria under which the facial image was captured.</xsd:documentation> 11 </xsd:annotation> 12 </xsd:element> 13 <!-- ======================================================= --> 14 <xsd:element substitutionGroup="ansi-nist:FaceImageAcquisitionProfile" name="FaceImageAcquisitionP15 type="ansi-nist:SAPCodeType"> 16 <xsd:annotation> 17 <xsd:documentation>Indicates the criteria under which the facial image was captured.</xsd:docum18 <xsd:appinfo> 19 <i:Base i:name="FaceImageAcquisitionProfile"/> 20 </xsd:appinfo> 21 </xsd:annotation> 22 </xsd:element> 23 <!-- ========not used=============================================== --> 24 <xsd:element substitutionGroup="ansi-nist:FaceImageAcquisitionProfile" name="FaceImageAcquisitionP25 type="nc:TextType" nillable="true"> 26 <xsd:annotation> 27 <xsd:documentation>The criteria under which the facial image was captured.</xsd:documentation> 28 <xsd:appinfo> 29 <i:Base i:name="FaceImageAcquisitionProfile"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 </xsd:element> 33 <!-- ======================================================= --> 34 <xsd:element name="FaceImageAttribute" type="ansi-nist:FaceImageAttributeType"> 35 <xsd:annotation> 36 <xsd:documentation>Information about a single facial attribute.</xsd:documentation> 37 </xsd:annotation> 38 </xsd:element> 39 <!-- ======================================================= --> 40 <xsd:element name="FaceImageAttributeAbstract" abstract="true"> 41 <xsd:annotation> 42 <xsd:documentation>Indicates special attributes of the captured facial image.</xsd:documentati43 </xsd:annotation> 
Part 2 – Annex L 

364

1 </xsd:element> 2 <!-- ======================================================= --> 3 <xsd:element substitutionGroup="ansi-nist:FaceImageAttributeAbstract" name="FaceImageAttributeCode4 nist:PXSCodeType"> 5 <xsd:annotation> 6 <xsd:documentation>Indicates special attributes of the captured facial image.</xsd:documentati7 <xsd:appinfo> 8 <i:Base i:name="FaceImageAttributeAbstract"/> 9 </xsd:appinfo> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ========not used=============================================== --> 13 <xsd:element substitutionGroup="ansi-nist:FaceImageAttributeAbstract" name="FaceImageAttributeText14 nillable="true"> 15 <xsd:annotation> 16 <xsd:documentation>Part 4, Sec 13 NCIC code description, or free text additional information f17 attributes</xsd:documentation> 18 <xsd:appinfo> 19 <i:Base i:name="FaceImageAttributeAbstract"/> 20 </xsd:appinfo> 21 </xsd:annotation> 22 </xsd:element> 23 <!-- ======================================================= --> 24 <xsd:element name="FaceImageDescription" abstract="true"> 25 <xsd:annotation> 26 <xsd:documentation>Indicates the facial expression of the subject and other attributes associa27 subject's captured facial image</xsd:documentation> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ======================================================= --> 31 <xsd:element substitutionGroup="ansi-nist:FaceImageDescription" name="FaceImageDescriptionCode" typ32 nist:SXSCodeType"> 33 <xsd:annotation> 34 <xsd:documentation>Indicates the facial expression of the subject and other attributes associa35 subject's captured facial image</xsd:documentation> 36 <xsd:appinfo> 37 <i:Base i:name="FaceImageDescription"/> 38 </xsd:appinfo> 39 </xsd:annotation> 40 </xsd:element> 41 <!-- ========not used=============================================== --> 42 <xsd:element substitutionGroup="ansi-nist:FaceImageDescription" name="FaceImageDescriptionText" typ43 nillable="true"> 
Part 2 – Annex L 

365

1 <xsd:annotation> 2 <xsd:documentation>Text description of the facial image.</xsd:documentation> 3 <xsd:appinfo> 4 <i:Base i:name="FaceImageDescription"/> 5 </xsd:appinfo> 6 </xsd:annotation> 7 </xsd:element> 8 <!-- ======================================================= --> 9 <xsd:element name="FaceImageEyeColorAttribute" abstract="true"> 

10 <xsd:annotation> 11 <xsd:documentation>Eye Color shown in an image of a persons face</xsd:documentation> 12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element substitutionGroup="ansi-nist:FaceImageEyeColorAttribute" name="FaceImageEyeColorAttri16 type="ansi-nist:SECCodeType"> 17 <xsd:annotation> 18 <xsd:documentation>Indicates the eye color of the subject as seen in the photograph.</xsd:docum19 <xsd:appinfo> 20 <i:Base i:name="FaceImageEyeColorAttribute"/> 21 </xsd:appinfo> 22 </xsd:annotation> 23 </xsd:element> 24 <!-- ========not used=============================================== --> 25 <xsd:element substitutionGroup="ansi-nist:FaceImageEyeColorAttribute" name="FaceImageEyeColorAttri26 type="nc:TextType" nillable="true"> 27 <xsd:annotation> 28 <xsd:documentation>Eye Color shown in an image of a persons face</xsd:documentation> 29 <xsd:appinfo> 30 <i:Base i:name="FaceImageEyeColorAttribute"/> 31 </xsd:appinfo> 32 </xsd:annotation> 33 </xsd:element> 34 <!-- ======================================================= --> 35 <xsd:element name="FaceImageFeaturePoint" type="ansi-nist:FaceImageFeaturePointType"> 36 <xsd:annotation> 37 <xsd:documentation>A set of attributes describing facial feature points and their locations.</38 </xsd:annotation> 39 </xsd:element> 40 <!-- ======================================================= --> 41 <xsd:element name="FaceImageHairColorAttribute" abstract="true"> 42 <xsd:annotation> 43 <xsd:documentation>Hair color shown in an image of a persons face</xsd:documentation> 
Part 2 – Annex L 

366

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ======================================================= --> 4 <xsd:element substitutionGroup="ansi-nist:FaceImageHairColorAttribute" name="FaceImageHairColorAtt5 type="ansi-nist:SHCCodeType"> 6 <xsd:annotation> 7 <xsd:documentation>Indicates the hair color of the subject as seen in the photograph.</xsd:doc8 <xsd:appinfo> 9 <i:Base i:name="FaceImageHairColorAttribute"/> 

10 </xsd:appinfo> 11 </xsd:annotation> 12 </xsd:element> 13 <!-- ========not used=============================================== --> 14 <xsd:element substitutionGroup="ansi-nist:FaceImageHairColorAttribute" name="FaceImageHairColorAtt15 type="nc:TextType" nillable="true"> 16 <xsd:annotation> 17 <xsd:documentation>Hair color shown in an image of a persons face</xsd:documentation> 18 <xsd:appinfo> 19 <i:Base i:name="FaceImageHairColorAttribute"/> 20 </xsd:appinfo> 21 </xsd:annotation> 22 </xsd:element> 23 <!-- ======================================================= --> 24 <xsd:element name="FaceImagePoseOffsetAngleMeasure" type="niem-xsd:integer"> 25 <xsd:annotation> 26 <xsd:documentation>The angular offset of the subject from full face or a profile, for pose cod27 'A'.</xsd:documentation> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ======================================================= --> 31 <xsd:element name="FaceImageSubjectPose" abstract="true"> 32 <xsd:annotation> 33 <xsd:documentation>Indicates the pose of the subject.</xsd:documentation> 34 </xsd:annotation> 35 </xsd:element> 36 <!-- ======================================================= --> 37 <xsd:element substitutionGroup="ansi-nist:FaceImageSubjectPose" name="FaceImageSubjectPoseCode" typ38 nist:POSCodeType"> 39 <xsd:annotation> 40 <xsd:documentation>Indicates the pose of the subject.</xsd:documentation> 41 <xsd:appinfo> 42 <i:Base i:name="FaceImageSubjectPose"/> 43 </xsd:appinfo> 
Part 2 – Annex L 

367

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ========not used=============================================== --> 4 <xsd:element substitutionGroup="ansi-nist:FaceImageSubjectPose" name="FaceImageSubjectPoseText" typ5 nillable="true"> 6 <xsd:annotation> 7 <xsd:documentation>Text description of the pose of a subject.</xsd:documentation> 8 <xsd:appinfo> 9 <i:Base i:name="FaceImageSubjectPose"/> 

10 </xsd:appinfo> 11 </xsd:annotation> 12 </xsd:element> 13 <!-- ======================================================= --> 14 <xsd:element name="FeaturePointCategory" abstract="true"> 15 <xsd:annotation> 16 <xsd:documentation>Indicates the feature point type of the captured facial image.</xsd:documen17 </xsd:annotation> 18 </xsd:element> 19 <!-- ======================================================= --> 20 <xsd:element substitutionGroup="ansi-nist:FeaturePointCategory" name="FeaturePointCategoryCode" typ21 nist:SFPCodeType"> 22 <xsd:annotation> 23 <xsd:documentation>Indicates the feature point type of the captured facial image.</xsd:documen24 <xsd:appinfo> 25 <i:Base i:name="FeaturePointCategory"/> 26 </xsd:appinfo> 27 </xsd:annotation> 28 </xsd:element> 29 <!-- ========not used=============================================== --> 30 <xsd:element substitutionGroup="ansi-nist:FeaturePointCategory" name="FeaturePointCategoryText" 31 type="nc:IdentificationType" nillable="true"> 32 <xsd:annotation> 33 <xsd:documentation>Text description indicating the type of feature point being described.</xsd34 <xsd:appinfo> 35 <i:Base i:name="FeaturePointCategory"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 </xsd:element> 39 <!-- ======================================================= --> 40 <xsd:element name="FeaturePointHorizontalCoordinateValue" type="niem-xsd:decimal"> 41 <xsd:annotation> 42 <xsd:documentation>The X coordinate of a core or delta position of a biometric.</xsd:documenta43 </xsd:annotation> 
Part 2 – Annex L 

368

1 </xsd:element> 2 <!-- ======================================================= --> 3 <xsd:element name="FeaturePointIdentification" type="nc:IdentificationType"> 4 <xsd:annotation> 5 <xsd:documentation>Annex K code for a particular feature point.</xsd:documentation> 6 </xsd:annotation> 7 </xsd:element> 8 <!-- ======================================================= --> 9 <xsd:element name="FeaturePointVerticalCoordinateValue" type="niem-xsd:decimal"> 

10 <xsd:annotation> 11 <xsd:documentation>The Y coordinate of a core or delta position of a biometric.</xsd:documenta12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element name="FingerPattern" abstract="true"> 16 <xsd:annotation> 17 <xsd:documentation>A particular pattern classification code.</xsd:documentation> 18 </xsd:annotation> 19 </xsd:element> 20 <!-- ======================================================= --> 21 <xsd:element substitutionGroup="ansi-nist:FingerPattern" name="FingerPatternCode" type="nc:TextTyp22 <xsd:annotation> 23 <xsd:appinfo> 24 <i:Base i:name="FingerPattern"/> 25 </xsd:appinfo> 26 </xsd:annotation> 27 </xsd:element> 28 <!-- ======================================================= --> 29 <xsd:element name="FingerPatternCodeSourceCode" type="ansi-nist:PCSCodeType"> 30 <xsd:annotation> 31 <xsd:documentation>Designator of Table 15, or user source of classification codes.</xsd:docume32 </xsd:annotation> 33 </xsd:element> 34 <!-- ========not used=============================================== --> 35 <xsd:element substitutionGroup="ansi-nist:FingerPattern" name="FingerPatternText" type="nc:TextTyp36 <xsd:annotation> 37 <xsd:documentation>A particular pattern classification code. Table 15, or other.</xsd:documen38 <xsd:appinfo> 39 <i:Base i:name="FingerPattern"/> 40 </xsd:appinfo> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

369

1 <xsd:element name="FingerPositionCode" type="ansi-nist:FPCCodeType"> 2 <xsd:annotation> 3 <xsd:documentation>Set of possible finger position codes, most probable position first.</xsd:d4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="FingerPositionIndicator" type="niem-xsd:boolean"> 8 <xsd:annotation> 9 <xsd:documentation>Indicator denoting whether or not a fingerprint image represents a latent p

10 </xsd:documentation> 11 </xsd:annotation> 12 </xsd:element> 13 <!-- ======================================================= --> 14 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="FingerprintImage" type="ansi-nist:Fin15 <xsd:annotation> 16 <xsd:appinfo> 17 <i:Base i:name="RecordImage"/> 18 </xsd:appinfo> 19 </xsd:annotation> 20 </xsd:element> 21 <!-- ======================================================= --> 22 <xsd:element name="FingerprintImageImpressionCaptureCategory" abstract="true"/> 23 <!-- ======================================================= --> 24 <xsd:element substitutionGroup="ansi-nist:FingerprintImageImpressionCaptureCategory" 25 name="FingerprintImageImpressionCaptureCategoryCode" type="ansi-nist:IMPCodeType"> 26 <xsd:annotation> 27 <xsd:appinfo> 28 <i:Base i:name="FingerprintImageImpressionCaptureCategory"/> 29 </xsd:appinfo> 30 </xsd:annotation> 31 </xsd:element> 32 <!-- ========not used=============================================== --> 33 <xsd:element substitutionGroup="ansi-nist:FingerprintImageImpressionCaptureCategory" 34 name="FingerprintImageImpressionCaptureCategoryText" type="nc:TextType" nillable="true"> 35 <xsd:annotation> 36 <xsd:appinfo> 37 <i:Base i:name="FingerprintImageImpressionCaptureCategory"/> 38 </xsd:appinfo> 39 </xsd:annotation> 40 </xsd:element> 41 <!-- ======================================================= --> 42 <xsd:element name="FingerprintImageMajorCasePrint" type="ansi-nist:FingerprintImageMajorCasePrintTy43 <xsd:annotation> 
Part 2 – Annex L 

370

1 <xsd:documentation>Information required when finger position code is "19" complete friction ri2 exemplars.</xsd:documentation> 3 </xsd:annotation> 4 </xsd:element> 5 <!-- ======================================================= --> 6 <xsd:element name="FingerprintImageNISTQuality" type="ansi-nist:FingerprintImageNISTQualityType"/> 7 <!-- ======================================================= --> 8 <xsd:element name="FingerprintImagePosition" type="ansi-nist:FingerprintType"> 9 <xsd:annotation> 

10 <xsd:documentation>Set of possible finger position codes, most probable position first.</xsd:d11 </xsd:annotation> 12 </xsd:element> 13 <!-- ======================================================= --> 14 <xsd:element name="FingerprintImageSegmentationQuality" type="ansi-nist:FingerprintImageQualityTyp15 <xsd:annotation> 16 <xsd:documentation>Information about the accuracy of the slap print segmentation.</xsd:documen17 </xsd:annotation> 18 </xsd:element> 19 <!-- ======================================================= --> 20 <xsd:element name="FingerprintPattern" type="ansi-nist:FingerprintPatternType"/> 21 <!-- ======================================================= --> 22 <xsd:element name="ImageBitsPerPixelQuantity" type="niem-xsd:nonNegativeInteger"> 23 <xsd:annotation> 24 <xsd:documentation>The number of bits used to represent a pixel.</xsd:documentation> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="ImageCaptureDetail" type="ansi-nist:ImageCaptureType"> 29 <xsd:annotation> 30 <xsd:documentation>Information regarding the captured (e.g., scanned) image.</xsd:documentatio31 </xsd:annotation> 32 </xsd:element> 33 <!-- ======================================================= --> 34 <xsd:element name="ImageCategoryCode" type="ansi-nist:IMTCodeType"> 35 <xsd:annotation> 36 <xsd:documentation>Indicates the type of image contained in this record</xsd:documentation> 37 </xsd:annotation> 38 </xsd:element> 39 <!-- ======================================================= --> 40 <xsd:element name="ImageColorSpace" abstract="true"> 41 <xsd:annotation> 42 <xsd:documentation>Color space used to exchange an image.</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

371

1 </xsd:element> 2 <!-- ======================================================= --> 3 <xsd:element substitutionGroup="ansi-nist:ImageColorSpace" name="ImageColorSpaceCode" type="ansi-n4 <xsd:annotation> 5 <xsd:documentation>The color space code used to exchange an image from Table 3.</xsd:documenta6 <xsd:appinfo> 7 <i:Base i:name="ImageColorSpace"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 </xsd:element> 11 <!-- ========not used=============================================== --> 12 <xsd:element substitutionGroup="ansi-nist:ImageColorSpace" name="ImageColorSpaceText" type="nc:Tex13 nillable="true"> 14 <xsd:annotation> 15 <xsd:documentation>Color space used to exchange an image.</xsd:documentation> 16 <xsd:appinfo> 17 <i:Base i:name="ImageColorSpace"/> 18 </xsd:appinfo> 19 </xsd:annotation> 20 </xsd:element> 21 <!-- ======================================================= --> 22 <xsd:element name="ImageCommentText" type="nc:TextType"> 23 <xsd:annotation> 24 <xsd:documentation>Comments or other text information regarding an image.</xsd:documentation> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="ImageCompressionAlgorithm" abstract="true"> 29 <xsd:annotation> 30 <xsd:documentation>ASCII code from Table 1</xsd:documentation> 31 </xsd:annotation> 32 </xsd:element> 33 <!-- ======================================================= --> 34 <xsd:element substitutionGroup="ansi-nist:ImageCompressionAlgorithm" name="ImageCompressionAlgorit35 nist:GCACodeType"> 36 <xsd:annotation> 37 <xsd:documentation>ASCII code from Table 1</xsd:documentation> 38 <xsd:appinfo> 39 <i:Base i:name="ImageCompressionAlgorithm"/> 40 </xsd:appinfo> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

372

1 <xsd:element substitutionGroup="ansi-nist:ImageCompressionAlgorithm" name="ImageCompressionAlgorit2 type="nc:TextType"> 3 <xsd:annotation> 4 <xsd:documentation>ASCII code from Table 1 (e.g. NONE or per domain registrar) or Integer code 5 2.</xsd:documentation> 6 <xsd:appinfo> 7 <i:Base i:name="ImageCompressionAlgorithm"/> 8 </xsd:appinfo> 9 </xsd:annotation> 

10 </xsd:element> 11 <!-- ======================================================= --> 12 <xsd:element name="ImageHorizontalLineLengthPixelQuantity" type="niem-xsd:integer"> 13 <xsd:annotation> 14 <xsd:documentation>Number of pixels on a single horizontal line.</xsd:documentation> 15 </xsd:annotation> 16 </xsd:element> 17 <!-- ======================================================= --> 18 <xsd:element name="ImageHorizontalPixelDensityValue" type="niem-xsd:nonNegativeInteger"> 19 <xsd:annotation> 20 <xsd:documentation>Transmitted pixel density in horizontal direction.</xsd:documentation> 21 </xsd:annotation> 22 </xsd:element> 23 <!-- ======================================================= --> 24 <xsd:element name="ImageQuality" type="ansi-nist:ImageQualityType"> 25 <xsd:annotation> 26 <xsd:documentation>Details about the quality of an image.</xsd:documentation> 27 </xsd:annotation> 28 </xsd:element> 29 <!-- ======================================================= --> 30 <xsd:element name="ImageRecordCategoryCode" type="ansi-nist:IRTCodeType"> 31 <xsd:annotation> 32 <xsd:documentation>Indicates the type of logical image record.</xsd:documentation> 33 </xsd:annotation> 34 </xsd:element> 35 <!-- ======================================================= --> 36 <xsd:element name="ImageReferenceIdentification" type="nc:IdentificationType"> 37 <xsd:annotation> 38 <xsd:documentation>An integer value associated with a particular subject matter object (e.g., 39 finger).</xsd:documentation> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ======================================================= --> 43 <xsd:element name="ImageScaleUnitsCode" type="ansi-nist:SLCCodeType"> 
Part 2 – Annex L 

373

1 <xsd:annotation> 2 <xsd:documentation>Indicates the sampling frequency unit designator, pixels per inch, or pixel3 centimeter.</xsd:documentation> 4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="ImageVerticalLineLengthPixelQuantity" type="niem-xsd:integer"> 8 <xsd:annotation> 9 <xsd:documentation>Number of horizontal lines.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="ImageVerticalPixelDensityValue" type="niem-xsd:nonNegativeInteger"> 14 <xsd:annotation> 15 <xsd:documentation>Transmitted pixel density in the vertical direction.</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ======================================================= --> 19 <xsd:element name="IrisEyeColorAttributeCode" type="ansi-nist:SECCodeType"> 20 <xsd:annotation> 21 <xsd:documentation>Table 22, eye color code.</xsd:documentation> 22 </xsd:annotation> 23 </xsd:element> 24 <!-- ======================================================= --> 25 <xsd:element name="IrisEyePosition" abstract="true"> 26 <xsd:annotation> 27 <xsd:documentation>Designates which eye is represented by the image.</xsd:documentation> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ======================================================= --> 31 <xsd:element substitutionGroup="ansi-nist:IrisEyePosition" name="IrisEyePositionCode" type="ansi-n32 <xsd:annotation> 33 <xsd:documentation>Designates which eye is represented by the image.</xsd:documentation> 34 <xsd:appinfo> 35 <i:Base i:name="IrisEyePosition"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 </xsd:element> 39 <!-- ========not used=============================================== --> 40 <xsd:element substitutionGroup="ansi-nist:IrisEyePosition" name="IrisEyePositionText" type="nc:Tex41 nillable="true"> 42 <xsd:annotation> 43 <xsd:documentation>Which eye is represented by the text.</xsd:documentation> 
Part 2 – Annex L 

374

1 <xsd:appinfo> 2 <i:Base i:name="IrisEyePosition"/> 3 </xsd:appinfo> 4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="IrisEyeRotationAngleMeasure" type="niem-xsd:nonNegativeInteger"> 8 <xsd:annotation> 9 <xsd:documentation>The rotation angle of the image.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="IrisEyeRotationUncertaintyValueText" type="nc:TextType"> 14 <xsd:annotation> 15 <xsd:documentation>Image rotation uncertainty.</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ======================================================= --> 19 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="IrisImage" type="ansi-nist:IrisImageTy20 <xsd:annotation> 21 <xsd:appinfo> 22 <i:Base i:name="RecordImage"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 </xsd:element> 26 <!-- ======================================================= --> 27 <xsd:element name="IrisImageAcquisitionLightingSpectrumValue" type="ansi-nist:ALSCodeType"> 28 <xsd:annotation> 29 <xsd:documentation>Indicates the lighting spectrum used in capturing the iris image.</xsd:docum30 </xsd:annotation> 31 </xsd:element> 32 <!-- ======================================================= --> 33 <xsd:element name="IrisImageCapture" type="ansi-nist:IrisImageCaptureType"/> 34 <!-- ======================================================= --> 35 <xsd:element name="IrisImageHorizontalOrientation" abstract="true"> 36 <xsd:annotation> 37 <xsd:documentation>Indicates the horizontal orientation of an image.</xsd:documentation> 38 </xsd:annotation> 39 </xsd:element> 40 <!-- ======================================================= --> 41 <xsd:element substitutionGroup="ansi-nist:IrisImageHorizontalOrientation" name="IrisImageHorizonta42 type="ansi-nist:IOCCodeType"> 43 <xsd:annotation> 
Part 2 – Annex L 

375

1 <xsd:documentation>Indicates the horizontal orientation of an image.</xsd:documentation> 2 <xsd:appinfo> 3 <i:Base i:name="IrisImageHorizontalOrientation"/> 4 </xsd:appinfo> 5 </xsd:annotation> 6 </xsd:element> 7 <!-- ========not used=============================================== --> 8 <xsd:element substitutionGroup="ansi-nist:IrisImageHorizontalOrientation" name="IrisImageHorizonta9 type="nc:TextType" nillable="true"> 

10 <xsd:annotation> 11 <xsd:documentation>Indicates the horizontal orientation of an image.</xsd:documentation> 12 <xsd:appinfo> 13 <i:Base i:name="IrisImageHorizontalOrientation"/> 14 </xsd:appinfo> 15 </xsd:annotation> 16 </xsd:element> 17 <!-- ======================================================= --> 18 <xsd:element name="IrisImageScanCategory" abstract="true"> 19 <xsd:annotation> 20 <xsd:documentation>Criteria under which the image was captured.</xsd:documentation> 21 </xsd:annotation> 22 </xsd:element> 23 <!-- ======================================================= --> 24 <xsd:element substitutionGroup="ansi-nist:IrisImageScanCategory" name="IrisImageScanCategoryCode" 25 nist:ICTCodeType"> 26 <xsd:annotation> 27 <xsd:documentation>Iris image scan type code.</xsd:documentation> 28 <xsd:appinfo> 29 <i:Base i:name="IrisImageScanCategory"/> 30 </xsd:appinfo> 31 </xsd:annotation> 32 </xsd:element> 33 <!-- ========not used=============================================== --> 34 <xsd:element substitutionGroup="ansi-nist:IrisImageScanCategory" name="IrisImageScanCategoryText" 35 nillable="true"> 36 <xsd:annotation> 37 <xsd:documentation>Criteria under which the image was captured.</xsd:documentation> 38 <xsd:appinfo> 39 <i:Base i:name="IrisImageScanCategory"/> 40 </xsd:appinfo> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

376

1 <xsd:element name="IrisImageVerticalOrientation" abstract="true"> 2 <xsd:annotation> 3 <xsd:documentation>Indicates the vertical orientation of an image.</xsd:documentation> 4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element substitutionGroup="ansi-nist:IrisImageVerticalOrientation" name="IrisImageVerticalOri8 type="ansi-nist:IOCCodeType"> 9 <xsd:annotation> 

10 <xsd:documentation>Indicates the vertical orientation of an image.</xsd:documentation> 11 <xsd:appinfo> 12 <i:Base i:name="IrisImageVerticalOrientation"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 </xsd:element> 16 <!-- ========not used=============================================== --> 17 <xsd:element substitutionGroup="ansi-nist:IrisImageVerticalOrientation" name="IrisImageVerticalOri18 type="nc:TextType" nillable="true"> 19 <xsd:annotation> 20 <xsd:documentation>Indicates the vertical orientation of an image.</xsd:documentation> 21 <xsd:appinfo> 22 <i:Base i:name="IrisImageVerticalOrientation"/> 23 </xsd:appinfo> 24 </xsd:annotation> 25 </xsd:element> 26 <!-- ======================================================= --> 27 <xsd:element name="MajorCasePrintCode" type="ansi-nist:FERCodeType"> 28 <xsd:annotation> 29 <xsd:documentation>An exemplar image type code from Table 30.</xsd:documentation> 30 </xsd:annotation> 31 </xsd:element> 32 <!-- ======================================================= --> 33 <xsd:element name="MajorCasePrintSegmentOffset" type="ansi-nist:MajorCasePrintSegmentOffsetType"> 34 <xsd:annotation> 35 <xsd:documentation>Data describing the type and location of segments within a complete frictio36 image or slap print image.</xsd:documentation> 37 </xsd:annotation> 38 </xsd:element> 39 <!-- ========not used=============================================== --> 40 <xsd:element name="MajorCasePrintText" type="nc:TextType" nillable="true"> 41 <xsd:annotation> 42 <xsd:documentation>Type of exemplar image.</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

377

1 </xsd:element> 2 <!-- =========not used============================================== --> 3 <xsd:element name="MaximumRangeIdentification" type="nc:IdentificationType" nillable="true"> 4 <xsd:annotation> 5 <xsd:documentation>Highest Value in consecutive Number Range</xsd:documentation> 6 </xsd:annotation> 7 </xsd:element> 8 <!-- =========not used============================================== --> 9 <xsd:element name="MinimumRangeIdentification" type="nc:IdentificationType" nillable="true"> 

10 <xsd:annotation> 11 <xsd:documentation>Lowest Value in consecutive Number Range</xsd:documentation> 12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element name="MinutiaCategory" abstract="true"> 16 <xsd:annotation> 17 <xsd:documentation>Indicates the minutia type</xsd:documentation> 18 </xsd:annotation> 19 </xsd:element> 20 <!-- ======================================================= --> 21 <xsd:element substitutionGroup="ansi-nist:MinutiaCategory" name="MinutiaCategoryCode" type="ansi-n22 <xsd:annotation> 23 <xsd:documentation>Indicates the minutia type</xsd:documentation> 24 <xsd:appinfo> 25 <i:Base i:name="MinutiaCategory"/> 26 </xsd:appinfo> 27 </xsd:annotation> 28 </xsd:element> 29 <!-- ========not used=============================================== --> 30 <xsd:element substitutionGroup="ansi-nist:MinutiaCategory" name="MinutiaCategoryText" type="nc:Tex31 nillable="true"> 32 <xsd:annotation> 33 <xsd:documentation>Text describing the type of minutia</xsd:documentation> 34 <xsd:appinfo> 35 <i:Base i:name="MinutiaCategory"/> 36 </xsd:appinfo> 37 </xsd:annotation> 38 </xsd:element> 39 <!-- ======================================================= --> 40 <xsd:element name="MinutiaDetail" type="ansi-nist:MinutiaType"> 41 <xsd:annotation> 42 <xsd:documentation>Information about one finger or palmprint minutia object.</xsd:documentatio43 </xsd:annotation> 
Part 2 – Annex L 

378

1 </xsd:element> 2 <!-- ======================================================= --> 3 <xsd:element name="MinutiaIdentification" type="nc:IdentificationType"> 4 <xsd:annotation> 5 <xsd:documentation>An integer value sequentially assigned to minutia in this record.</xsd:docum6 </xsd:annotation> 7 </xsd:element> 8 <!-- ======================================================= --> 9 <xsd:element name="MinutiaPosition" type="ansi-nist:MinutiaPositionType"> 

10 <xsd:annotation> 11 <xsd:documentation>A set of coordinates describing the position of a single minutia.</xsd:docum12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element name="MinutiaQualityValue" type="niem-xsd:nonNegativeInteger"> 16 <xsd:annotation> 17 <xsd:documentation>A confidence level quality value.</xsd:documentation> 18 </xsd:annotation> 19 </xsd:element> 20 <!-- ======================================================= --> 21 <xsd:element name="MinutiaRidgeCount" type="ansi-nist:MinutiaRidgeCountType"> 22 <xsd:annotation> 23 <xsd:documentation>A set of measurements from this minutia point to distant minutia points.</x24 </xsd:annotation> 25 </xsd:element> 26 <!-- ======================================================= --> 27 <xsd:element name="Minutiae" type="ansi-nist:MinutiaeType"/> 28 <!-- ======================================================= --> 29 <xsd:element name="MinutiaeFingerCorePosition" type="ansi-nist:MinutiaeFingerPositionType"> 30 <xsd:annotation> 31 <xsd:documentation>The position of the finger's pattern core.</xsd:documentation> 32 </xsd:annotation> 33 </xsd:element> 34 <!-- ======================================================= --> 35 <xsd:element name="MinutiaeFingerDeltaPosition" type="ansi-nist:MinutiaeFingerPositionType"> 36 <xsd:annotation> 37 <xsd:documentation>The position of the finger's pattern delta.</xsd:documentation> 38 </xsd:annotation> 39 </xsd:element> 40 <!-- ======================================================= --> 41 <xsd:element name="MinutiaeFingerPatternDetail" type="ansi-nist:MinutiaeFingerPatternType"> 42 <xsd:annotation> 
Part 2 – Annex L 

379

1 <xsd:documentation>A repeatable subelement containing details about a fingerprint pattern. Th2 is the primary pattern, others are reference patterns.</xsd:documentation> 3 </xsd:annotation> 4 </xsd:element> 5 <!-- ======================================================= --> 6 <xsd:element name="MinutiaeFingerPosition" abstract="true"/> 7 <!-- ======================================================= --> 8 <xsd:element substitutionGroup="ansi-nist:MinutiaeFingerPosition" name="MinutiaeFingerPositionCode9 type="nc:TextType"> 

10 <xsd:annotation> 11 <xsd:appinfo> 12 <i:Base i:name="MinutiaeFingerPosition"/> 13 </xsd:appinfo> 14 </xsd:annotation> 15 </xsd:element> 16 <!-- ========not used=============================================== --> 17 <xsd:element substitutionGroup="ansi-nist:MinutiaeFingerPosition" name="MinutiaeFingerPositionText18 nillable="true"> 19 <xsd:annotation> 20 <xsd:appinfo> 21 <i:Base i:name="MinutiaeFingerPosition"/> 22 </xsd:appinfo> 23 </xsd:annotation> 24 </xsd:element> 25 <!-- ======================================================= --> 26 <xsd:element name="MinutiaeFormatNISTStandardIndicator" type="niem-xsd:boolean"> 27 <xsd:annotation> 28 <xsd:documentation>Designator of standard or user-defined format.</xsd:documentation> 29 </xsd:annotation> 30 </xsd:element> 31 <!-- ======================================================= --> 32 <xsd:element name="MinutiaeImpressionCaptureCategory" abstract="true"/> 33 <!-- ======================================================= --> 34 <xsd:element substitutionGroup="ansi-nist:MinutiaeImpressionCaptureCategory" 35 name="MinutiaeImpressionCaptureCategoryCode" type="nc:TextType"> 36 <xsd:annotation> 37 <xsd:appinfo> 38 <i:Base i:name="MinutiaeImpressionCaptureCategory"/> 39 </xsd:appinfo> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ========not used=============================================== --> 
Part 2 – Annex L 

380

1 <xsd:element substitutionGroup="ansi-nist:MinutiaeImpressionCaptureCategory" 2 name="MinutiaeImpressionCaptureCategoryText" type="nc:TextType" nillable="true"> 3 <xsd:annotation> 4 <xsd:appinfo> 5 <i:Base i:name="MinutiaeImpressionCaptureCategory"/> 6 </xsd:appinfo> 7 </xsd:annotation> 8 </xsd:element> 9 <!-- ======================================================= --> 

10 <xsd:element name="MinutiaeNISTStandard" type="ansi-nist:NISTStandardMinutiaeType"> 11 <xsd:annotation> 12 <xsd:documentation>Details regarding NIST Standard Minutiae</xsd:documentation> 13 </xsd:annotation> 14 </xsd:element> 15 <!-- ======================================================= --> 16 <xsd:element name="MinutiaePalmPosition" abstract="true"/> 17 <!-- ======================================================= --> 18 <xsd:element substitutionGroup="ansi-nist:MinutiaePalmPosition" name="MinutiaePalmPositionCode" typ19 <xsd:annotation> 20 <xsd:appinfo> 21 <i:Base i:name="MinutiaePalmPosition"/> 22 </xsd:appinfo> 23 </xsd:annotation> 24 </xsd:element> 25 <!-- ========not used=============================================== --> 26 <xsd:element substitutionGroup="ansi-nist:MinutiaePalmPosition" name="MinutiaePalmPositionText" typ27 nillable="true"> 28 <xsd:annotation> 29 <xsd:appinfo> 30 <i:Base i:name="MinutiaePalmPosition"/> 31 </xsd:appinfo> 32 </xsd:annotation> 33 </xsd:element> 34 <!-- ======================================================= --> 35 <xsd:element name="MinutiaeQuantity" type="niem-xsd:nonNegativeInteger"> 36 <xsd:annotation> 37 <xsd:documentation>The number of minutiae recorded for this finger or palmprint.</xsd:document38 </xsd:annotation> 39 </xsd:element> 40 <!-- ======================================================= --> 41 <xsd:element name="MinutiaeReadingSystem" type="ansi-nist:MinutiaeReadingSystemType"> 42 <xsd:annotation> 43 <xsd:documentation>Designator of standard or user-defined format.</xsd:documentation> 
Part 2 – Annex L 

381

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ======================================================= --> 4 <xsd:element name="MinutiaeRidgeCountIndicator" type="niem-xsd:boolean"> 5 <xsd:annotation> 6 <xsd:documentation>Designates whether minutiae data record contains ridge count information.</7 </xsd:annotation> 8 </xsd:element> 9 <!-- ======================================================= --> 

10 <xsd:element name="NISTImage" type="ansi-nist:NISTImageType"/> 11 <!-- ======================================================= --> 12 <xsd:element name="NISTQualityMeasure" type="niem-xsd:nonNegativeInteger"> 13 <xsd:annotation> 14 <xsd:documentation>The value of a NIST Fingerprint Image Quality score, predicted matcher 15 accuracy.</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ======================================================= --> 19 <xsd:element name="NativeScanningResolutionValue" type="niem-xsd:decimal"> 20 <xsd:annotation> 21 <xsd:documentation>In pixels per mm, the native resolution of transaction originator's sc22 equipment.</xsd:documentation> 23 </xsd:annotation> 24 </xsd:element> 25 <!-- ==============not used========================================= --> 26 <xsd:element name="NewsletterCount" type="niem-xsd:nonNegativeInteger" nillable="true"> 27 <xsd:annotation> 28 <xsd:documentation>The number of CJIS newsletters needed.</xsd:documentation> 29 </xsd:annotation> 30 </xsd:element> 31 <!-- ======================================================= --> 32 <xsd:element name="NominalTransmittingResolutionValue" type="niem-xsd:decimal"> 33 <xsd:annotation> 34 <xsd:documentation>In pixels per mm, this transaction's transmitting resolution.</xsd:doc35 </xsd:annotation> 36 </xsd:element> 37 <!-- ==============not used========================================= --> 38 <xsd:element name="OperatingManualCount" type="niem-xsd:nonNegativeInteger" nillable="true"> 39 <xsd:annotation> 40 <xsd:documentation>The number of Operating Manuals needed.</xsd:documentation> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ==============not used========================================= --> 
Part 2 – Annex L 

382

1 <xsd:element name="OrganizationDocumentCount" type="ansi-nist:OrganizationDocumentCountType" nilla2 <xsd:annotation> 3 <xsd:documentation>Data regarding the document counts for the ORI being entered.</xsd:document4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="OrganizationName" type="nc:TextType"> 8 <xsd:annotation> 9 <xsd:documentation>Unique domain agency identifier.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="PalmPosition" abstract="true"> 14 <xsd:annotation> 15 <xsd:documentation>Indicates the location on the palm that a print represents.</xsd:documentat16 </xsd:annotation> 17 </xsd:element> 18 <!-- ======================================================= --> 19 <xsd:element substitutionGroup="ansi-nist:PalmPosition" name="PalmPositionCode" type="ansi-nist:PP20 <xsd:annotation> 21 <xsd:documentation>Indicates the location on the palm that a print represents.</xsd:documentat22 <xsd:appinfo> 23 <i:Base i:name="PalmPosition"/> 24 </xsd:appinfo> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ==========not used============================================= --> 28 <xsd:element substitutionGroup="ansi-nist:PalmPosition" name="PalmPositionText" type="nc:TextType" 29 <xsd:annotation> 30 <xsd:documentation>Text indicating the location on the palm that a print represents.</xsd:docum31 <xsd:appinfo> 32 <i:Base i:name="PalmPosition"/> 33 </xsd:appinfo> 34 </xsd:annotation> 35 </xsd:element> 36 <!-- ======================================================= --> 37 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="PalmprintImage" type="ansi-nist:Palmp38 <xsd:annotation> 39 <xsd:appinfo> 40 <i:Base i:name="RecordImage"/> 41 </xsd:appinfo> 42 </xsd:annotation> 43 </xsd:element> 
Part 2 – Annex L 

383

1 <!-- ======================================================= --> 2 <xsd:element name="PatternCodeSourceCode" type="ansi-nist:PCSCodeType"> 3 <xsd:annotation> 4 <xsd:documentation>Designator of Table 15, or user source of classification codes.</xsd:docume5 </xsd:annotation> 6 </xsd:element> 7 <!-- ======================================================= --> 8 <xsd:element name="PatternCorePosition" type="ansi-nist:MinutiaPositionType"> 9 <xsd:annotation> 

10 <xsd:documentation>A set of coordinates describing the position of a pattern's core or 11 delta.</xsd:documentation> 12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element name="PatternDeltaPosition" type="ansi-nist:MinutiaPositionType"> 16 <xsd:annotation> 17 <xsd:documentation>The position of the finger's pattern delta.</xsd:documentation> 18 </xsd:annotation> 19 </xsd:element> 20 <!-- ==============not used========================================= --> 21 <xsd:element name="PatternNISTStandardText" type="nc:TextType" nillable="true"> 22 <xsd:annotation> 23 <xsd:documentation>A particular pattern classification code. Table 15, or other.</xsd:documen24 </xsd:annotation> 25 </xsd:element> 26 <!-- ==============not used========================================= --> 27 <xsd:element name="PatternUserText" type="nc:TextType" nillable="true"> 28 <xsd:annotation> 29 <xsd:documentation>A particular pattern classification code. Table 15, or other.</xsd:documen30 </xsd:annotation> 31 </xsd:element> 32 <!-- ======================================================= --> 33 <xsd:element name="PhysicalFeatureCategoryCode" type="ansi-nist:SMDCodeType"> 34 <xsd:annotation> 35 <xsd:documentation>Indicates the source of the image as being a scar, a mark, or a tattoo.</xs36 </xsd:annotation> 37 </xsd:element> 38 <!-- ======================================================= --> 39 <xsd:element name="PhysicalFeatureClassCode" type="ansi-nist:PCCCodeType"> 40 <xsd:annotation> 41 <xsd:documentation>Indicates the human tattoo class of an SMT, OTHER if not tattoo.</xsd:docum42 </xsd:annotation> 43 </xsd:element> 
Part 2 – Annex L 

384

1 <!-- ======================================================= --> 2 <xsd:element name="PhysicalFeatureColorDetail" type="ansi-nist:PhysicalFeatureColorDetailType"/> 3 <!-- ======================================================= --> 4 <xsd:element name="PhysicalFeatureDescriptionDetail" type="ansi-nist:PhysicalFeatureDescriptionTyp5 <xsd:annotation> 6 <xsd:documentation>A complete description of scars, marks, or tattoos visible in a transmitted 7 image</xsd:documentation> 8 </xsd:annotation> 9 </xsd:element> 

10 <!-- ======================================================= --> 11 <xsd:element name="PhysicalFeatureDescriptionText" type="nc:TextType"> 12 <xsd:annotation> 13 <xsd:documentation>Additional free text qualifiers describing the contents of the image.</xsd:14 </xsd:annotation> 15 </xsd:element> 16 <!-- ======================================================= --> 17 <xsd:element name="PhysicalFeatureHeightMeasure" type="niem-xsd:nonNegativeInteger"> 18 <xsd:annotation> 19 <xsd:documentation>The feature's height in whole centimeters</xsd:documentation> 20 </xsd:annotation> 21 </xsd:element> 22 <!-- ======================================================= --> 23 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="PhysicalFeatureImage" type="ansi24 nist:PhysicalFeatureImageType"> 25 <xsd:annotation> 26 <xsd:appinfo> 27 <i:Base i:name="RecordImage"/> 28 </xsd:appinfo> 29 </xsd:annotation> 30 </xsd:element> 31 <!-- ======================================================= --> 32 <xsd:element name="PhysicalFeatureNCICCode" type="fbi:SMTCodeType"> 33 <xsd:annotation> 34 <xsd:documentation>NCIC code for a particular scar, mark, or tattoo.</xsd:documentation> 35 </xsd:annotation> 36 </xsd:element> 37 <!-- ======================================================= --> 38 <xsd:element name="PhysicalFeaturePrimaryColorCode" type="ansi-nist:COLCodeType"> 39 <xsd:annotation> 40 <xsd:documentation>Primary Color of a tattoo in an image.</xsd:documentation> 41 </xsd:annotation> 42 </xsd:element> 43 <!-- ======================================================= --> 
Part 2 – Annex L 

385

1 <xsd:element name="PhysicalFeatureSecondaryColorCode" type="ansi-nist:COLCodeType"> 2 <xsd:annotation> 3 <xsd:documentation>Secondary Color of a tattoo in an image.</xsd:documentation> 4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="PhysicalFeatureSize" type="ansi-nist:PhysicalFeatureSizeType"> 8 <xsd:annotation> 9 <xsd:documentation>The dimensions of the scar, mark, or tattoo.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="PhysicalFeatureSubClassCode" type="ansi-nist:PSCCodeType"> 14 <xsd:annotation> 15 <xsd:documentation>Indicates the human tattoo subclass of an SMT, MISC if not tattoo.</xsd:doc16 </xsd:annotation> 17 </xsd:element> 18 <!-- ======================================================= --> 19 <xsd:element name="PhysicalFeatureWidthMeasure" type="niem-xsd:nonNegativeInteger"> 20 <xsd:annotation> 21 <xsd:documentation>The feature's width in whole centimeters</xsd:documentation> 22 </xsd:annotation> 23 </xsd:element> 24 <!-- ======================================================= --> 25 <xsd:element name="PosePitchAngleMeasure" type="niem-xsd:integer"> 26 <xsd:annotation> 27 <xsd:documentation>Rogation about the horizontal 'x' axis.</xsd:documentation> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ======================================================= --> 31 <xsd:element name="PosePitchUncertaintyValue" type="niem-xsd:nonNegativeInteger"> 32 <xsd:annotation> 33 <xsd:documentation>The pitch uncertainty.</xsd:documentation> 34 </xsd:annotation> 35 </xsd:element> 36 <!-- ======================================================= --> 37 <xsd:element name="PoseRollAngleMeasure" type="niem-xsd:integer"> 38 <xsd:annotation> 39 <xsd:documentation>Rotation about the 'z' axis.</xsd:documentation> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ======================================================= --> 43 <xsd:element name="PoseRollUncertaintyValue" type="niem-xsd:nonNegativeInteger"> 
Part 2 – Annex L 

386

1 <xsd:annotation> 2 <xsd:documentation>The roll uncertainty.</xsd:documentation> 3 </xsd:annotation> 4 </xsd:element> 5 <!-- ======================================================= --> 6 <xsd:element name="PoseYawAngleMeasure" type="niem-xsd:integer"> 7 <xsd:annotation> 8 <xsd:documentation>Rotation about the vertical 'y' axis.</xsd:documentation> 9 </xsd:annotation> 

10 </xsd:element> 11 <!-- ======================================================= --> 12 <xsd:element name="PoseYawUncertaintyValue" type="niem-xsd:nonNegativeInteger"> 13 <xsd:annotation> 14 <xsd:documentation>The yaw uncertainty.</xsd:documentation> 15 </xsd:annotation> 16 </xsd:element> 17 <!-- ======================================================= --> 18 <xsd:element name="PositionBottomCoordinateValue" type="niem-xsd:nonNegativeInteger"> 19 <xsd:annotation> 20 <xsd:documentation>In pixels, the bottom vertical offset of the segment box within an image.</21 </xsd:annotation> 22 </xsd:element> 23 <!-- ========not used=============================================== --> 24 <xsd:element name="PositionDirectionDegreeValue" type="niem-xsd:nonNegativeInteger" nillable="true25 <xsd:annotation> 26 <xsd:documentation>Direction of the core opening, through the center of curvature for the inne27 maximum curvature in integer degrees (000 to 360)</xsd:documentation> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ======================================================= --> 31 <xsd:element name="PositionHorizontalCoordinateValue" type="niem-xsd:nonNegativeInteger"> 32 <xsd:annotation> 33 <xsd:documentation>The minutia's X coordinate</xsd:documentation> 34 </xsd:annotation> 35 </xsd:element> 36 <!-- ======================================================= --> 37 <xsd:element name="PositionThetaAngleMeasure" type="niem-xsd:nonNegativeInteger"> 38 <xsd:annotation> 39 <xsd:documentation>The minutia's theta angle</xsd:documentation> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ======================================================= --> 43 <xsd:element name="PositionTopCoordinateValue" type="niem-xsd:nonNegativeInteger"> 
Part 2 – Annex L 

387

1 <xsd:annotation> 2 <xsd:documentation>In pixels, the top vertical offset of the segment box within an image.</xsd3 </xsd:annotation> 4 </xsd:element> 5 <!-- ======================================================= --> 6 <xsd:element name="PositionUncertaintyValue" type="niem-xsd:nonNegativeInteger"> 7 <xsd:annotation> 8 <xsd:documentation>Radius of position uncertainty (PUM) in the manual or automatic placement o9 integer units of 10 micrometers.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="PositionVerticalCoordinateValue" type="niem-xsd:nonNegativeInteger"> 14 <xsd:annotation> 15 <xsd:documentation>The minutia's Y coordinate</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ==============not used========================================= --> 19 <xsd:element name="ProtectionOrderAugmentation" type="ansi-nist:ProtectionOrderAugmentationType" 20 substitutionGroup="s:Augmentation"> 21 <xsd:annotation> 22 <xsd:documentation>An augmentation that applies to j:ProtectionOrderType</xsd:documentation> 23 <xsd:appinfo> 24 <i:AppliesTo i:namespace="http://niem.gov/niem/domains/jxdm/4.0" i:name="ProtectionOrderType25 </xsd:appinfo> 26 </xsd:annotation> 27 </xsd:element> 28 <!-- ==============not used========================================= --> 29 <xsd:element name="ProtectionOrderBradyIndicator" type="nc:TextType" nillable="true"> 30 <xsd:annotation> 31 <xsd:documentation>Indicates whether the subject is considered Brady disqualified.</xsd:docume32 </xsd:annotation> 33 </xsd:element> 34 <!-- ==============not used========================================= --> 35 <xsd:element name="ProtectionOrderConditionText" type="ansi-nist:IndicatorCodeType" nillable="true36 <xsd:annotation> 37 <xsd:documentation>Translation of the Protection Order Condition Indicates Response Message.</38 </xsd:annotation> 39 </xsd:element> 40 <!-- ======================================================= --> 41 <xsd:element name="QualityAlgorithmProductIdentification" type="nc:IdentificationType"> 42 <xsd:annotation> 43 <xsd:documentation>The numeric product code assigned by a vendor to the quality algorithm.</xs
Part 2 – Annex L 

388

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ======================================================= --> 4 <xsd:element name="QualityAlgorithmVendorIdentification" type="nc:IdentificationType"> 5 <xsd:annotation> 6 <xsd:documentation>From a registry table, the ID of the vendor of the quality algorithm.</xsd:7 </xsd:annotation> 8 </xsd:element> 9 <!-- ======================================================= --> 

10 <xsd:element name="QualityMeasureVendorIdentification" type="nc:IdentificationType"> 11 <xsd:annotation> 12 <xsd:documentation>From a registry table, the ID of the vendor of the quality algorithm.</xsd:13 </xsd:annotation> 14 </xsd:element> 15 <!-- ======================================================= --> 16 <xsd:element name="QualityValue" type="niem-xsd:integer"> 17 <xsd:annotation> 18 <xsd:documentation>Predicted matching performance.</xsd:documentation> 19 </xsd:annotation> 20 </xsd:element> 21 <!-- ======================================================= --> 22 <xsd:element name="ReadingSystemCodingMethodCode" type="ansi-nist:OFRCodeType"> 23 <xsd:annotation> 24 <xsd:documentation>Indicates the method by which the minutiae data was read, encoded, and 25 recorded.</xsd:documentation> 26 </xsd:annotation> 27 </xsd:element> 28 <!-- ======================================================= --> 29 <xsd:element name="ReadingSystemName" type="nc:TextType"> 30 <xsd:annotation> 31 <xsd:documentation>The name of the system.</xsd:documentation> 32 </xsd:annotation> 33 </xsd:element> 34 <!-- ======================================================= --> 35 <xsd:element name="ReadingSystemSubsystemIdentification" type="nc:IdentificationType"> 36 <xsd:annotation> 37 <xsd:documentation>A two-character unique identifier for the originator's equipment.</xsd38 </xsd:annotation> 39 </xsd:element> 40 <!-- ==============not used========================================= --> 41 <xsd:element name="Record" type="ansi-nist:RecordType" nillable="true"/> 42 <!-- ======================================================= --> 43 <xsd:element name="RecordCategoryCode" type="ansi-nist:RTCCodeType"> 
Part 2 – Annex L 

389

1 <xsd:annotation> 2 <xsd:documentation>The type of record (e.g., 02)</xsd:documentation> 3 </xsd:annotation> 4 </xsd:element> 5 <!-- ==============not used========================================= --> 6 <xsd:element name="RecordForwardOrganizations" type="nc:OrganizationType" nillable="true"> 7 <xsd:annotation> 8 <xsd:documentation>Organizations that additional electronic responses need to be forwarded to.9 </xsd:annotation> 

10 </xsd:element> 11 <!-- ======================================================= --> 12 <xsd:element name="RecordImage" abstract="true"> 13 <xsd:annotation> 14 <xsd:documentation>Information regarding an Image being transmitted in an ITL Record 15 Transaction</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ==============not used========================================= --> 19 <xsd:element name="RecordRapSheetRequestIndicator" type="niem-xsd:boolean" nillable="true"> 20 <xsd:annotation> 21 <xsd:documentation>Indicates whether an electronic rap sheet should be returned with the 22 response.</xsd:documentation> 23 </xsd:annotation> 24 </xsd:element> 25 <!-- ==============not used========================================= --> 26 <xsd:element name="RecordRetentionIndicator" type="niem-xsd:boolean" nillable="true"> 27 <xsd:annotation> 28 <xsd:documentation>Indicates whether the arrest/civil submission information submitted is to b29 permanent part of the FBI's Criminal Master File/Civil File</xsd:documentation> 30 </xsd:annotation> 31 </xsd:element> 32 <!-- ==============not used========================================= --> 33 <xsd:element name="RecordTransactionData" type="ansi-nist:TransactionType" nillable="true"> 34 <xsd:annotation> 35 <xsd:documentation>Detailed information pertaining to the transaction being transmitted.</xsd:36 </xsd:annotation> 37 </xsd:element> 38 <!-- ======================================================= --> 39 <xsd:element name="RidgeCountReferenceIdentification" type="nc:IdentificationType"> 40 <xsd:annotation> 41 <xsd:documentation>The index number of the distant minutia point.</xsd:documentation> 42 </xsd:annotation> 43 </xsd:element> 
Part 2 – Annex L 

390

1 <!-- ======================================================= --> 2 <xsd:element name="RidgeCountValue" type="niem-xsd:nonNegativeInteger"> 3 <xsd:annotation> 4 <xsd:documentation>The count of ridges between this and the distant point.</xsd:documentation> 5 </xsd:annotation> 6 </xsd:element> 7 <!-- ======================================================= --> 8 <xsd:element name="SegmentBottomVerticalCoordinateValue" type="niem-xsd:nonNegativeInteger"> 9 <xsd:annotation> 

10 <xsd:documentation>In pixels, the bottom vertical offset of the segment box within an image.</11 </xsd:annotation> 12 </xsd:element> 13 <!-- ==============not used========================================= --> 14 <xsd:element name="SegmentFingerText" type="nc:TextType" nillable="true"> 15 <xsd:annotation> 16 <xsd:documentation>Exemplar image type represented in a major case print</xsd:documentation> 17 </xsd:annotation> 18 </xsd:element> 19 <!-- ======================================================= --> 20 <xsd:element name="SegmentFingerViewCode" type="ansi-nist:FEFCodeType"> 21 <xsd:annotation> 22 <xsd:documentation>The bounding coordinates for a full finger view.</xsd:documentation> 23 </xsd:annotation> 24 </xsd:element> 25 <!-- ======================================================= --> 26 <xsd:element name="SegmentLeftHorizontalCoordinateValue" type="niem-xsd:nonNegativeInteger"> 27 <xsd:annotation> 28 <xsd:documentation>In pixels, the left horizontal offset of the segment box within an image.</29 </xsd:annotation> 30 </xsd:element> 31 <!-- ======================================================= --> 32 <xsd:element name="SegmentLocationCode" type="ansi-nist:FERCodeType"> 33 <xsd:annotation> 34 <xsd:documentation>A Major case print segment code from Table 30.</xsd:documentation> 35 </xsd:annotation> 36 </xsd:element> 37 <!-- ======================================================= --> 38 <xsd:element name="SegmentRightHorizontalCoordinateValue" type="niem-xsd:nonNegativeInteger"> 39 <xsd:annotation> 40 <xsd:documentation>In pixels, the right horizontal offset of the segment box within an image.<41 </xsd:annotation> 42 </xsd:element> 43 <!-- ==============not used========================================= --> 
Part 2 – Annex L 

391

1 <xsd:element name="SegmentText" type="nc:TextType" nillable="true"> 2 <xsd:annotation> 3 <xsd:documentation>Exemplar image type represented in a major case print</xsd:documentation> 4 </xsd:annotation> 5 </xsd:element> 6 <!-- ======================================================= --> 7 <xsd:element name="SegmentTopVerticalCoordinateValue" type="niem-xsd:nonNegativeInteger"> 8 <xsd:annotation> 9 <xsd:documentation>In pixels, the top vertical offset of the segment box within an image.</xsd

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="SignatureCategoryCode" type="ansi-nist:SIGCodeType"> 14 <xsd:annotation> 15 <xsd:documentation>Indicates the signature image of the subject, or the signature image of the 16 the transaction.</xsd:documentation> 17 </xsd:annotation> 18 </xsd:element> 19 <!-- ======================================================= --> 20 <xsd:element substitutionGroup="ansi-nist:RecordImage" name="SignatureImage" type="ansi-nist:Signa21 <xsd:annotation> 22 <xsd:appinfo> 23 <i:Base i:name="RecordImage"/> 24 </xsd:appinfo> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="SignatureImageVector" type="ansi-nist:SignatureImageVectorType"> 29 <xsd:annotation> 30 <xsd:documentation>Detail information about one vector object.</xsd:documentation> 31 </xsd:annotation> 32 </xsd:element> 33 <!-- ======================================================= --> 34 <xsd:element name="SignatureImageVectorRepresentation" type="ansi-nist:SignatureImageVectorReprese35 <xsd:annotation> 36 <xsd:documentation>Repeatable set of elements regarding a signature representation.</xsd:docum37 </xsd:annotation> 38 </xsd:element> 39 <!-- ======================================================= --> 40 <xsd:element name="SignatureRepresentationCode" type="ansi-nist:SRTCodeType"> 41 <xsd:annotation> 42 <xsd:documentation>Indicates if an image is scanned and not compressed, scanned and compressed43 data.</xsd:documentation> 
Part 2 – Annex L 

392

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ==============not used========================================= --> 4 <xsd:element name="TOUCount" type="niem-xsd:nonNegativeInteger" nillable="true"> 5 <xsd:annotation> 6 <xsd:documentation>The number of Technical and Operational Updates (TOUs) needed.</xsd:documen7 </xsd:annotation> 8 </xsd:element> 9 <!-- ======================================================= --> 

10 <xsd:element name="Transaction" type="ansi-nist:TransactionType"> 11 <xsd:annotation> 12 <xsd:documentation>Detailed information pertaining to the transaction being transmitted.</xsd:13 </xsd:annotation> 14 </xsd:element> 15 <!-- ======================================================= --> 16 <xsd:element name="TransactionCategoryCode" type="nc:TextType"> 17 <xsd:annotation> 18 <xsd:documentation>Indicates the type of transaction defined by receiving agency.</xsd:documen19 </xsd:annotation> 20 </xsd:element> 21 <!-- ======================================================= --> 22 <xsd:element name="TransactionCharacterSetDirectory" type="ansi-nist:TransactionCharacterSetDirect23 <xsd:annotation> 24 <xsd:documentation>Character sets other than 7-bit ASCII used in this transaction.</xsd:docume25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="TransactionContentSummary" type="ansi-nist:TransactionContentSummaryType"> 29 <xsd:annotation> 30 <xsd:documentation>Summary details pertaining to the record contents being transmitted.</xsd:d31 </xsd:annotation> 32 </xsd:element> 33 <!-- ======================================================= --> 34 <xsd:element name="TransactionControlIdentification" type="nc:IdentificationType"> 35 <xsd:annotation> 36 <xsd:documentation>Unique number assigned to transaction by the originating agency.</xsd:docum37 </xsd:annotation> 38 </xsd:element> 39 <!-- ======================================================= --> 40 <xsd:element name="TransactionControlReferenceIdentification" type="nc:IdentificationType"> 41 <xsd:annotation> 42 <xsd:documentation>Contains original TCN on transaction responses.</xsd:documentation> 43 </xsd:annotation> 
Part 2 – Annex L 

393

1 </xsd:element> 2 <!-- ======================================================= --> 3 <xsd:element name="TransactionDate" type="nc:DateType" nillable="true"> 4 <xsd:annotation> 5 <xsd:documentation>Date the transaction was sent by the user</xsd:documentation> 6 </xsd:annotation> 7 </xsd:element> 8 <!-- ======================================================= --> 9 <xsd:element name="TransactionDestinationOrganization" type="nc:OrganizationType"> 

10 <xsd:annotation> 11 <xsd:documentation>Organization the transaction is being sent to.</xsd:documentation> 12 </xsd:annotation> 13 </xsd:element> 14 <!-- ======================================================= --> 15 <xsd:element name="TransactionDomain" type="ansi-nist:TransactionDomainType"> 16 <xsd:annotation> 17 <xsd:documentation>Domain of Type-02 logical record implementation.</xsd:documentation> 18 </xsd:annotation> 19 </xsd:element> 20 <!-- ==============not used========================================= --> 21 <xsd:element name="TransactionHeaderText" type="nc:TextType" nillable="true"> 22 <xsd:annotation> 23 <xsd:documentation>The header is a sequence of characters acceptable to the NCIC computer and 24 message information for the CSA.</xsd:documentation> 25 </xsd:annotation> 26 </xsd:element> 27 <!-- ======================================================= --> 28 <xsd:element name="TransactionImageResolutionDetails" type="ansi-nist:TransactionImageResolutionTyp29 <xsd:annotation> 30 <xsd:documentation>Resolution values in pixels per mm for a transaction.</xsd:documentation> 31 </xsd:annotation> 32 </xsd:element> 33 <!-- ==============not used========================================= --> 34 <xsd:element name="TransactionKeyText" type="nc:TextType" nillable="true"> 35 <xsd:annotation> 36 <xsd:documentation>A code in the header of an incoming III/FBI transaction indicating the type 37 for processing the message. The transaction key field is the second data element in the transaction.38 </xsd:annotation> 39 </xsd:element> 40 <!-- ==============not used========================================= --> 41 <xsd:element name="TransactionKeyTranslationText" type="nc:TextType" nillable="true"> 42 <xsd:annotation> 43 <xsd:documentation>Translation of the Transaction Key Code for response messages</xsd:document
Part 2 – Annex L 

394

1 </xsd:annotation> 2 </xsd:element> 3 <!-- ======================================================= --> 4 <xsd:element name="TransactionMajorVersionValue" type="niem-xsd:nonNegativeInteger"> 5 <xsd:annotation> 6 <xsd:documentation>2-character major version number of the standard implemented by the creatin7 system.</xsd:documentation> 8 </xsd:annotation> 9 </xsd:element> 

10 <!-- ======================================================= --> 11 <xsd:element name="TransactionMinorVersionValue" type="niem-xsd:nonNegativeInteger"> 12 <xsd:annotation> 13 <xsd:documentation>2-character minor version number of the standard implemented by the creatin14 system.</xsd:documentation> 15 </xsd:annotation> 16 </xsd:element> 17 <!-- ==============not used========================================= --> 18 <xsd:element name="TransactionOrganization" type="nc:OrganizationType" nillable="true"> 19 <xsd:annotation> 20 <xsd:documentation>Information regarding the Organization requesting the transaction </xsd:doc21 </xsd:annotation> 22 </xsd:element> 23 <!-- ======================================================= --> 24 <xsd:element name="TransactionOriginatingOrganization" type="nc:OrganizationType"> 25 <xsd:annotation> 26 <xsd:documentation>Organization originating the transaction.</xsd:documentation> 27 </xsd:annotation> 28 </xsd:element> 29 <!-- ======================================================= --> 30 <xsd:element name="TransactionPriorityValue" type="niem-xsd:nonNegativeInteger"> 31 <xsd:annotation> 32 <xsd:documentation>Urgency with which transaction response is expected (0..Low 9..High)</xsd:33 </xsd:annotation> 34 </xsd:element> 35 <!-- ==============not used========================================= --> 36 <xsd:element name="TransactionReasonText" type="nc:TextType" nillable="true"> 37 <xsd:annotation> 38 <xsd:documentation>Text field for user to provide information regarding the reason for request39 transaction</xsd:documentation> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ==============not used========================================= --> 43 <xsd:element name="TransactionSearchRequestCategoryCode" type="ansi-nist:TSRCodeType" nillable="tr
Part 2 – Annex L 

395

1 <xsd:annotation> 2 <xsd:documentation>Indicates the type of record being submitted.</xsd:documentation> 3 </xsd:annotation> 4 </xsd:element> 5 <!-- ==============not used========================================= --> 6 <xsd:element name="TransactionSubmissionMilitaryCode" type="ansi-nist:MILCodeType" nillable="true"7 <xsd:annotation> 8 <xsd:documentation>Indicates which branch of the United States Military submitted the enlistme9 transaction.</xsd:documentation> 

10 </xsd:annotation> 11 </xsd:element> 12 <!-- ======================================================= --> 13 <xsd:element name="TransactionUTCDate" type="nc:DateType" nillable="true"> 14 <xsd:annotation> 15 <xsd:documentation>Date and time of the transaction in universal units.</xsd:documentation> 16 </xsd:annotation> 17 </xsd:element> 18 <!-- ==============not used========================================= --> 19 <xsd:element name="TransactionUserIdentification" type="nc:IdentificationType" nillable="true"> 20 <xsd:annotation> 21 <xsd:documentation>Unique ID to identify the Individual requesting the transaction</xsd:docume22 </xsd:annotation> 23 </xsd:element> 24 <!-- ======================================================= --> 25 <xsd:element name="VectorPenPressureValue" type="niem-xsd:nonNegativeInteger"> 26 <xsd:annotation> 27 <xsd:documentation>Constant value of pressure for the length of the vector</xsd:documentation> 28 </xsd:annotation> 29 </xsd:element> 30 <!-- ======================================================= --> 31 <xsd:element name="VectorPositionHorizontalCoordinateValue" type="niem-xsd:decimal"> 32 <xsd:annotation> 33 <xsd:documentation>The vector's X coordinate in units of .0254 mm</xsd:documentation> 34 </xsd:annotation> 35 </xsd:element> 36 <!-- ======================================================= --> 37 <xsd:element name="VectorPositionVerticalCoordinateValue" type="niem-xsd:decimal"> 38 <xsd:annotation> 39 <xsd:documentation>The vector's Y coordinate in units of .0254 mm</xsd:documentation> 40 </xsd:annotation> 41 </xsd:element> 42 <!-- ======================================================= --> 43 <xsd:element name="VehicleOwnershipNICB" abstract="true"> 
Part 2 – Annex L 

396

1 <xsd:annotation> 2 <xsd:documentation>NICB Division location in the United States, showing interest in a stolen v3 entry.</xsd:documentation> 4 </xsd:annotation> 5 </xsd:element> 6 </xsd:schema>