Proposal for a

Proposal for a

ANSI/NIST ITL ANSI/NIST ITL

XML document fo

XML document fo

Alessandro Alessandro Triglia Triglia

OSS Nokalva, Inc. OSS Nokalva, Inc.

sandro@oss.com

ANSI/NIST Finger

ANSI/NIST Finger

Update Workshop Update WorkshopGaithersburg, MD Gaithersburg, MD 
ITL-1 XML document format 1 XML document format – E

E

 <?xml version='1.0' encoding="utf <?xml version='1.0' encoding="utf-8"?> <bir xmlns="xyz"> <itl:transaction itl:transaction xmlns:itl xmlns:itl="...itl..." version version="0001" type="ABCDE" type="ABCDE"  date="YYYYMMDD" date="YYYYMMDD" priority="1" priority="1"  destination="XYZ" destination="XYZ" origin="XYZ" origin="XYZ" number="14131511113" number="14131511113" reference="14131511111" reference="14131511111" native_resolution native_resolution="14.94" nominal_resolution nominal_resolution="14.94" domain_name="DOMAIN" ="DOMAIN" gmt="20040105150723Z"> <itl:content itl:content num_recor num_records="4"> <itl:record itl:record type="2" type="2" idc="0"/> <itl:record itl:record type="9" type="9" idc="1"/> <itl:record itl:record type="0" type="0" idc="2"/> <itl:record itl:record type="0" type="0" idc="2"/> </itl:content itl:content/>
ITL-1 XML document format 1 XML document format – E

E

 <itl:subject itl:subject> <e:subject xmlns:e="...efts... <!--retention code retention code--> <e:ret>Y</e:e:ret> <!--"attention" indica

tion" indica

 <e:atn>SA J Q DXR, <e:atn>SA J Q DXR,R <!--send copy to send copy to--> <e:sco>NY030025P< <e:sco>NY030025Q< <e:sco>NY030025R<

>NY030025R<

 <!--originating agenc

originating agenc

 <e:oca>Q880312465

>Q880312465

 <!--fbi number--> <e:fbi>62760NY13</ >62760NY13</ <e:fbi>62760NY14</ >62760NY14</ <e:fbi>62760NY15</ >62760NY15</ <!--state identificatio

state identificatio

 <e:sid>NY12345678< <!--social security ac

social security ac

 <e:soc>220565855< <e:soc>220565856<

>220565856<

 <e:soc>220565857<

>220565857<
ITL-1 XML document format 1 XML document format – E

E

 <!--name--> <e:nam>JXSDAH, ANTH <!--place of birth--> <e:pob>VA</e:pob> <!--citizenship--> <e:ctz>US</e:ctz> <!--date of birth--> <e:dob>29770825</ >29770825</e:d <!--sex--> <e:sex>M</e:sex> <!--race--> <e:rac>W</e:rac> <!--scars, marks, and ta

scars, marks, and ta

 <e:smt>MISS L TOE</ >MISS L TOE</e <e:smt>TAT RF ARM</ AT RF ARM</e <e:smt>TAT RF XYZ</e <!--height--> <e:hgt>601</e:hgt> <!--weight--> <e:wgt>192</e:wgt> <!--color eyes--> <e:eye>BLU</e:eye> <!--hair color--> <e:hai>BRO</e:hai>
ITL-1 XML document format 1 XML document format – E

E

 <!--occupation--> <e:ocp>PLUMBER</ >PLUMBER</e:oc <!--residence of pe nce of person 

rson 

 <e:res>54151 OAK LF,  <!--date of arrest of arrest--> <e:doa>29950324</ >29950324</e:d <!--arrest segment litera

arrest segment litera

 <e:asl> <e:doo>2994

>2994

 <e:aol>DUI</ </e:asl> <e:asl> <e:doo>2994

>2994

 <e:aol>POSS 

>POSS 

 </e:asl> <!--court segment litera

court segment litera

 <e:csl> <e:cdd>29940

>2994

 <e:col>DUI</ <e:cpl>5 DAY </e:csl> . . . . . . . . . .
ITL-1 XML document format 1 XML document format – E

E

 <bir_info bir_info integrity="true" integrity="true" creation_date creation_date="20040302T15

="20040302T15

 not_valid_before not_valid_before="20040302T

="20040302T

 not_valid_after not_valid_after="20040302T4 <creator> ABCDE </creator> <index> 1Aa873ab3auE61cCa91723d6P </index> </bir_info bir_info> <sb_info sb_info format_owner format_owner="18" format_type format_type="68"/> <bir> <bir_info bir_info integrity="false"> </bir_info bir_info>
ITL-1 XML document format 1 XML document format – E

E

 <bdb_info format_owner="555" format_type format_type="9" encryption="true" encryption="true" creation_date on_date="2004030

="2004030

 not_valid_before not_valid_before="2004

="2004

 not_valid_after not_valid_after="200403

="20040

 type="finger_minutiae inutiae"  subtype subtype="left_pointer left_pointer"  level="processe rocessed"  product_owner="16" product_type="2" purpose="verify purpose="verify" quality="100"> <index> 1Aa873ab3auE61cCa917

1Aa873ab3auE61cCa917

 </index> </bdb_info> <bdb> 1Aa873ab3auE61cCa98E61cCa917

1Aa873ab3auE61cCa98E61cCa917

 </bdb> <sb> 1873ab3auE61cCa961c 1873ab3auE61cCa961cCa9b3auE6 </sb> </bir>
CBEFF

 ANSI standard ANSI standard – INCITS 39

INCITS 39

 International standard (FD

International standard (FD

to be issued) to be issued) – ISO/IEC 19

ISO/IEC 19

(multipart) (multipart)

• Part 1: General concepts, da

Part 1: General concepts, da

• Part 2: Procedures for the op

Part 2: Procedures for the op

Registration Authority Registration Authority

• Part 3: Standardized patron 

Part 3: Standardized patron 
About CBEFF (1

About CBEFF (1

 CBEFF promotes interopera

CBEFF promotes interopera

biometric biometric

-based application

based application

systems by specifying stan

systems by specifying stan

structures for structures for biometric info

biometric inf

records records

(BIRs) and a set of 

) and a set of 

data elements and values t

data elements and values t

be used to create the head

be used to create the head

a CBEFF a CBEFF

-compliant BIR. compliant BIR. 

(excerpt from ISO/IEC 197

(excerpt from ISO/IEC 197
About CBEFF (2

About CBEFF (2

 A BIR is an encoding in acc

A BIR is an encoding in acc

with a CBEFF patron forma

with a CBEFF patron forma

unit of biometric data for s

unit of biometric data for s

database or for interchange 

database or for interchange 

systems or parts of system

systems or parts of system

always has at least two par

always has at least two par

standard biometric header 

standard biometric header 

at least one biometric data 

at least one biometric data 

(BDB). It may also have a 

(BDB). It may also have a 

called the security block (S

called the security block (S

(excerpt from ISO/IEC 197

(excerpt from ISO/IEC 197
About CBEFF (3

About CBEFF (3

 A CBEFF patron format CBEFF patron format is defin

is defin

particular domain of use. A CB

particular domain of use. A CB

format is a specification of enc

format is a specification of enc

can carry the abstract values o

can carry the abstract values o

data elements defined in this I

data elements defined in this I

Standard (possibly with additio

Standard (possibly with additio

values determined by the CBEF

values determined by the CBEF

together with one or more biom

together with one or more biom

blocks ( blocks (BDBs) containing biom

) containing biom

(excerpt from ISO/IEC 1

(excerpt from ISO/IEC 1
CBEFF patron form

CBEFF patron form

 A CBEFF patron format can be: A CBEFF patron format can be: 

• “Simple” “Simple” 

– supporting one heade

supporting one heade

biometric data block (BDB) biometric data block (BDB)

• “Complex” (or “nested”) “Complex” (or “nested”) 

– suppor

suppo

BDBs, hierarchy of headers/ , hierarchy of headers/subhe

subh

 A CBEFF patron format specific

A CBEFF patron format specific

includes: includes: 

• CBEFF

-defined (standard) data el

defined (standard) data el

values that are supported values that are supported

• any additional, patron any additional, patron

-defined da

defined da

and values that are supported and values that are supported
“Simple” CBEFF stru

Simple” CBEFF stru

BDB

(biometric 

data block)

SBH

(standard 

biometric 

header)

(

o

 The SBH consists of data eleme

The SBH consists of data eleme

• Format owner and format type (m

Format owner and format type (m

registered) registered)

• Biometric type (e.g., fingerprint, ir

Biometric type (e.g., fingerprint, ir

• Biometric subtype (e.g., left thum

Biometric subtype (e.g., left thum

• Creation date, Validity period Creation date, Validity period

• Processed level (raw, intermediate

Processed level (raw, intermediate

• Purpose (enroll, verify, etc.) Purpose (enroll, verify, etc.)

• Quality, Index, Challenge/respons

Quality, Index, Challenge/respons

• Other data elements defined by th

Other data elements defined by th
“Complex” (or “nested”) 

Complex” (or “nested”) 

structure structure - Example 

Example 

SBH (root header) – Subheader count=2

SBH (subheader) – Subheader count=3

SBH (subheader) BSBH (subheader) BSBH (subheader) B

SB (integrity)

SBH (subheader) – Subheader count=2

SBH (subheader) BSBH (subheader) B
“Complex” (or “nested”) 

Complex” (or “nested”) 

structure structure - Example 

Example 

SBH (root header) – Subheader count=5

BDB

SB (integrity)

SBH (subheader) SBH (subheader) BDBSBH (subheader) BDBSBH (subheader) BDB SBH (subheader) BDB
XML patron format XML patron format 

– Exam

Exam

 <?xml version='1.0' encoding="utf <?xml version='1.0' encoding="utf-8"?>

<bir

 xmlns

="xyz..." xyz..."

>

 <version major="0" minor="0"/>

<cbeff_version cbeff_version major="2" minor="0"/>



<bir_info bir_info

 integrity="true" integrity="true" creation_date creation_date="20040302T15

="20040302T15

 not_valid_before not_valid_before="20040302T

="20040302T

 not_valid_after not_valid_after="20040302T4 <creator> ABCDE </creator> <index> 1Aa873ab3auE61cCa91723d6P </index> <payload> 1Aa873ab3auE61cCa91723d6P </payload> </bir_info bir_info

>



<sb_info sb_info

 format_owner format_owner="51" format_type format_type="8"/>
XML patron format XML patron format 

– Exam

Exam



<bir

>



<bir_info bir_info

 integrity="false" integrity="false" creation_date creation_date="2004

="2004

 not_valid_before not_valid_before="20

="20

 not_valid_after not_valid_after="200 <creator> ABCDE </creator> <index> 1Aa873ab3auE61cCa </index> <payload> 1Aa873ab3auE61cCa </payload> </bir_info bir_info

>



<bdb_info bdb_info

 format_owner format_owner="51" format_type format_type="8" encryption="true" encryption="true" creation_date creation_date="2004

="2004

 not_valid_before not_valid_before="20

="20

 not_valid_after not_valid_after="200

="200
XML patron format XML patron format 

– Exam

Exam

 type="iris" type="iris"  subtype subtype

="left" 

 level="processe rocessed" 

p

roduct_owne

r="16"

 pro

d

u

ct_type="2"

 purpose="verify purpose="verify" quality="100">

<

c

hallenge_respon

s

e

>

 1Aa873ab3auE61cCa917

1Aa873ab3auE61cCa917

 </challenge_response challenge_response

>

 <index> 1Aa873ab3auE61cCa917

1Aa873ab3auE61cCa917

 </index> </bdb_i

nfo

>



<sb_info

 format_ow

ner="51"

 format_type format_type="8"/>

<bdb

>

 1Aa873ab3auE61cCa91723d6P 1Aa873ab3auE61cCa91723d6P

=

=

 </bdb

>



<sb

>

 1Aa873ab3auE61cCa91723d6P 1Aa873ab3auE61cCa91723d6P

=

=

 </sb

>

 </bi

r

>

 . . . . . . . . . .
XML patron format XML patron format 

– Fea

Fea

 US contribution to SC37 for inc

US contribution to SC37 for inc

CBEFF Part 3 CBEFF Part 3 

– to be discussed to be discussed 

(accepted?) at the next meetin

(accepted?) at the next meetin

 Fully CBEFF Fully CBEFF

-compliant “comple

compliant “comple

structure structure

 Supports all standard (CBEFF Supports all standard (CBEFF

-d

d

data elements data elements

 Extensible Extensible 

– Supports addition 

Supports addition 

application application

-specific data eleme

specific data eleme

proposed ITL proposed ITL

-1 XML format ex

1 XML format ex

feature) feature)
XML patron format XML patron format 

– Fea

Fea

 Recursive XML structure Recursive XML structure 

– A <

level) can contain either: level) can contain either:

• a single BDB, or a single BDB, or • one or more child < one or more child <bir>s (not bo

>s (not bo

 Supports inheritance of commo

Supports inheritance of commo

from one level of the structure 

from one level of the structure 

subordinate levels (unless over

subordinate levels (unless over

 Supports multiple levels of digi

Supports multiple levels of digi

signatures within the same doc

signatures within the same doc

(different authorities can sign d

(different authorities can sign d

or groups of data records) or groups of data records)

 Subsets of data records within 

Subsets of data records within 

document can be bound togeth

document can be bound togeth
ITL-1 XML document fo

1 XML document fo

Features (1) Features (1)

 Specified as an extension to the XM

Specified as an extension to the XM

format (relies on the extensibility fe

format (relies on the extensibility fe

 Transaction Transaction-level ITL data (Type level ITL data (Type-1 a

1 a

defined at the top level of the XML d

defined at the top level of the XML d

 Supports all existing Type Supports all existing Type-X records X records Supports all biometric data block (B

Supports all biometric data block (B

identified by BDB format owner / ty

identified by BDB format owner / ty

required by CBEFF. This includes: required by CBEFF. This includes:

• all BDB formats standardized in M1 and 

all BDB formats standardized in M1 and 

• non-standard BDB standard BDB forma`ts forma`ts (specified b

(specified b

organizations) having a BDB format own

organizations) having a BDB format own
ITL-1 XML document fo

1 XML document fo

Features (2) Features (2)

 Supports Supports further further extensions (e.g. EF

extensions (e.g. EF

shown in the example) shown in the example)

 Supports the “Type Supports the “Type-99” mechanism 

99” mechanism 

proposed by the proposed by the DoD – Increased fl

Increased fl

use of CBEFF patron formats within 

use of CBEFF patron formats within 

 Inherits all the features of the XML 

Inherits all the features of the XML 

format, including: format, including:

• Ability to group data records within a do

Ability to group data records within a do

• Ability to share common values within a 

Ability to share common values within a 

placing them at a higher level of the str

placing them at a higher level of the str

• Support for encryption and digital signa

Support for encryption and digital signa

levels
ITL-1 XML document fo

1 XML document fo

Some benefits Some benefits

 CBEFF is a foundational standard. It i

CBEFF is a foundational standard. It i

many governmental and commercial b

many governmental and commercial b

applications will comply to CBEFF by u

applications will comply to CBEFF by u

more) patron formats. An XML forma

more) patron formats. An XML forma

ANSI/NIST ITL ANSI/NIST ITL-1 standard based on C

1 standard based on C

easier to integrate with new and exist

easier to integrate with new and exist

applications that are CBEFF compliant

applications that are CBEFF compliant

 BioAPI is an important case, because 

is an important case, because 

itself is a CBEFF patron format. An XM

itself is a CBEFF patron format. An XM

ANSI/NIST ITL ANSI/NIST ITL-1 standard based on C

1 standard based on C

facilitate the creation and processing o

facilitate the creation and processing o

BioAPI-compliant biometric system, re

compliant biometric system, re

differences in the encodings (XML vs. 

differences in the encodings (XML vs. 
End

Alessandro Alessandro Triglia Triglia

OSS Nokalva, Inc. OSS Nokalva, Inc.

sandro@oss.com

ANSI/NIST Finger

ANSI/NIST Finger

Update Workshop Update WorkshopGaithersburg, MD Gaithersburg, MD