ISO/IEC 19794-4:2011/Amd 2:2015
(Amendment)Information technology — Biometric data interchange formats — Part 4: Finger image data — Amendment 2: XML encoding and clarification of defects
Information technology — Biometric data interchange formats — Part 4: Finger image data — Amendment 2: XML encoding and clarification of defects
Technologies de l'information — Formats d'échange de données biométriques — Partie 4: Données d'image du doigt — Amendement 2: Codage XML et précisions concernant les défauts
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19794-4
Second edition
2011-12-15
AMENDMENT 2
2015-12-01
Information technology — Biometric
data interchange formats —
Part 4:
Finger image data
AMENDMENT 2: XML encoding and
clarification of defects
Technologies de l’information — Formats d’échange de données
biométriques —
Partie 4: Données d’image du doigt
AMENDEMENT 2: Codage XML et précisions concernant les défauts
Reference number
ISO/IEC 19794-4:2011/Amd.2:2015(E)
©
ISO/IEC 2015
---------------------- Page: 1 ----------------------
ISO/IEC 19794-4:2011/Amd.2:2015(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2015 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have
established a joint technical committee, ISO/IEC JTC 1.
The procedures used to develop this document and those intended for its further maintenance are described in the
ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of document
should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives,
Part 2 (see www.iso.org/directives).
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights.
ISO and IEC shall not be held responsible for identifying any or all such patent rights. Details of any patent rights
identified during the development of the document will be in the Introduction and/or on the ISO list of patent
declarations received (see www.iso.org/patents).
Any trade name used in this document is information given for the convenience of users and does not constitute an
endorsement.
For an explanation on the meaning of ISO specific terms and expressions related to conformity assessment, as
well as information about ISO's adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the
following URL: Foreword - Supplementary information
Amendment 2 to ISO/IEC 19794-4:2011 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information
technology, Subcommittee SC 37, Biometrics.
© ISO/IEC 2015 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Information technology — Biometric data interchange format —
Part 4: Finger image data
Amendment 2: XML encoding and clarification of defects
1. Append the following paragraph into introduction
Additionally, this part of the ISO/IEC standard supports both binary and XML encoding, to
support a spectrum of user requirement. With XML, this part will meet the requirements modern
IT architectures. With binary encoding this part will also be able to be used in bandwitdth or
storage constrained environments. Annex F specifies the schema that XML encoded finger
image records must conform to, and Annex G provides an example of a valid XML encoded
finger image record.
2. Replace the existing text in clause “2– Conformance” wth the following
A binary data record conforms to this part of ISO/IEC 19794 if it satisfies all the format
requirements with respect to its structure, data values, relationships among its fields, and with
respect to relations between its fields and the underlying input that are specified throughout
clause 8 of this part of ISO/IEC 19794.
An XML document conforms to this part of ISO/IEC 19794 if it satisfies the format requirements
with respect to its structure, with respect to relations among its fields, and with respect to
relations between its fields and the underlying input that are specified within Annex F of this part
of ISO/IEC 19794.
A system that produces biometric data records is conformant to this part of ISO/IEC 19794 if all
biometric data records that it outputs conform to this part of ISO/IEC 19794 (as defined above)
as claimed in the Implementation Conformance Statement associated with that system. A
system does not need to be capable of producing biometric data records that cover all possible
aspects of this part of ISO/IEC 19794, but only those that are claimed to be supported by the
system in the Implementation Conformance Statement (ICS).
A system that uses biometric data records is conformant to this part of ISO/IEC 19794 if it can
read, and use for the purpose intended by that system, all biometric data records that conform
to this part of ISO/IEC 19794 (as defined above) as claimed in the Implementation
Conformance Statement associated with that system. A system does not need to be capable of
using biometric data records that cover all possible aspects of this part of ISO/IEC 19794, but
only those that are claimed to be supported by the system in an Implementation Conformance
Statement (ICS).
Biometric data interchange format conformance tests conform to this part of ISO/IEC 19794 if
they satisfy all of the normative requirements set forth in Annex A. Specifically, all Level-1,
1 © ISO/IEC 2015 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Level-2 and Level-3 tests shall use the assertions defined in Table A.2 and Table A.3 of clause
A.3 in conformity with the concept and rules set in ISO/IEC 19794-1:2011 AMD 1.
Implementations of this part of ISO/IEC 19794 tested according to the specified methodology
shall be able to claim conformance only to those biometric data record (BDB) requirements
specified in this part of ISO/IEC 19794 that are tested by the test methods established by this
methodology.
Implementations of this part of ISO/IEC 19794 do not necessarily need to conform to all
possible aspects of this part of ISO/IEC 19794, but only to those requirements that are claimed
to be supported by the implementation in an implementation conformance statement (ICS), filled
out in accordance with Annex A of ISO/IEC 19794-1:2011 AMD 1 and Table A.1 of clause A.2
of this part of ISO/IEC 19794.
3. Insert the following text in the appropriate alphabetical order of Clause 3:
http://www.w3.org/XML/Schema
4. Add the following Note in clause 8.4.1
NOTE: The total length of the extended data is obtained by: Length_extended_data =
Representation_length - Representation_header_length (41/42 bytes) -Image_Data_Length. In
order to detect whether additional extended data blocks are available, the number of bytes read
from the representation have to be subtracted from the representation length, and if the result is
positive, there is, at least, an additional extended data block.
5. Replace Clause A.2 with the following text
A.2 Table of requirements
The normative requirements specified in this Part of ISO/IEC 19794 are listed in Table A.1, which extends over
multiple pages. The supplier of the IUT should explain which optional components of the standard are supported
and the testing laboratory shall note the results of the test.
35 (0023 ) XML-finger-image {iso(1) registration-authority(1) cbeff(19785) biometric-organization(0) jtc1-
Hex
sc37(257) bdbs(0) XML-finger-image(35)}
Table A.1 – Table of requirements
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
Finger image general header
8.1 Each record shall pertain to 3C O-1 Y Y N/A N/A
R-1.
a single subject.
8.1 Each record shall contain at 3C O-1 Y Y N/A N/A
R-2.
least one representation for
each of one or more
fingers, multiple fingers
(single image records), or
palms
8.2.1 Information shall be 1 M Y Y
R-3.
included for each field
© ISO/IEC 2015 – All rights reserved 2
---------------------- Page: 5 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
within the header.
Y N
8.2.2 The format identifier shall 1 M
R-4.
be recorded in four bytes.
Table 1
8.2.2 The format identifier shall 1 M Y N N/A
R-5.
consist of three characters
Table 1
"FIR" (0x464952) followed
by a zero byte as a NULL
string terminator.
Therefore, the format
identifier shall be
0x46495200.
Y N
8.2.3 The Version Number shall 1 M N/A
R-6.
be recorded in four bytes.
Table 1
8.2.3 This version number shall 1 M Y N N/A
R-7.
consist of three ASCII
Table 1
numerals “020”
(0x30323000) followed by
zero byte as a NULL string
terminator.
Y N
8.2.4 The length (in bytes) of the 2 M
R-8.
entire image data record
Table 1
shall be recorded in four
bytes. Valid values are 57
32
to (2 -1 )
Y N
8.2.4 This length of entire record 2 M
R-9.
shall be total length of the
general record header and
one or more representation
records.
Y N
8.2.5 The total number of finger 1,2 M
R-10.
image representations
Table 1
contained in the finger
image data record shall be
recorded in two bytes. Valid
values are 1 to 672.
8.2.5 A minimum of one 1 M Y Y
R-11.
representation is required.
Y N
8.2.6 The one-byte certification 1 M
R-12.
flag shall indicate whether
Table 1
each representation header
includes a certification
record. Valid values are
00 and 01 .
Hex Hex
8.2.6 A value of 00 shall 2 M Y N
Hex
R-13.
indicate that none of the
representations contains a
certification record.
Y N
8.2.6 A value of 01 shall 2 M
Hex
R-14.
indicate that all
representations contain a
certification record.
8.2.7 The number of finger or 1 M Y N
R-15.
palm images included in the
© ISO/IEC 2015 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
Table 1 record shall be recorded in
one byte. Valid values are 1
to FF .
HEX
Finger image representation header
8.3.1 A finger or palm 3C O-1 Y N N/A N/A
R-16.
representation header shall
start each section of finger
data providing information
for that representation of a
single finger image, multi-
finger image or palm image.
8.3.1 For each such image there 2 M Y N N/A
R-17.
shall be one finger header
record accompanying the
representation of the image
data.
8.3.1 The representaion header 2 M Y N
R-18.
shall occupy a minimum of
41 bytes (assuming no
certification blocks and no
quality blocks are present).
Otherwise, it shall be
42+ 5*num_quality_block+
3*num_certification_block
8.3.1 The compressed or 3C O-1 Y N N/A N/A
R-19.
uncompressed image data
for that image
representation shall
immediately follow the
image representation
header.
8.3.1 Subsequent image 3C O-1 Y N N/A N/A
R-20.
representations (including
the image representation
header) will be
concatenated to the end of
the previous image
representation.
8.3.2 The four-byte 2 M Y N
R-21.
representation length field
Table 2
shall contain the length in
bytes of the finger
representation including the
representation header
fields. The minimum length
is 41.
8.3.3 Capture date-time field shall 3C O-1 Y Y
R-22.
indicate the date and time
Table 2
the representation was
captured. This field is not
intended to encode the time
the record was instantiated.
8.3.3 Capture time field shall be 1 M Y N
R-23.
encoded in accordance to
Table 2
the requirements given in
© ISO/IEC 2015 – All rights reserved 4
---------------------- Page: 7 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
Part 1 of this standard.
Parts of the capture date
and time that are unknown
shall be filled with FF , or
Hex
FFFF for two-byte
Hex
components and all
subsequent components
shall be unknown.
8.3.4 The one-byte capture 1 M Y N
R-24.
device technology ID shall
Table 4
contain the entry chosen
from Table 4 to indicate the
technology type used by the
capture device. Valid values
are 0 to 20.
8.3.5 The capture device vendor 1 M Y N
R-25.
ID shall be recorded in two
Table 2
bytes.
8.3.5 The capture device vendor 3B M Y Y
R-26.
ID shall identify the
Table 2
biometric organisation that
owns the product that
created the biometric record
(BDIR) and shall be
registered with the IBIA or
other approved registration
authority. A value of all
zeros shall indicate that the
capture device vendor is
unreported.
8.3.6 This capture device type ID 1 M Y N
R-27.
shall be recorded in two
Table 2
bytes.
8.3.6 This capture device type ID 3C O-1 Y Y N/A
R-28.
shall identify the product
Table 2
type that created the
biometric record and shall
be assigned by the
registered biometric record
product owner or other
approved registration
authority. A value of all
zeros shall indicate that the
capture device type is
unreported.
8.3.7.1 The quality information of 1 M Y N
R-29.
the overall finger image
data shall be recorded in
one or more five-byte
blocks.
8.3.7.1 Each of these blocks shall 2 M Y Y
R-30.
pertain to a specific
quality/vendor/algorithm
evaluation.
8.3.7.2 The first byte of the quality 2 M Y N
R-31.
© ISO/IEC 2015 – All rights reserved 5
---------------------- Page: 8 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
Table 2 record is mandatory and
shall contain the number of
subsequent quality blocks.
Valid values are 0 to 255.
8.3.7.2 Subsequent 5-byte blocks 1,3B M Y N
R-32.
shall contain the specific
Table 2
quality/vendor/algorithm
information for each
quality/vendor/algorithm
evaluation.
A value of zero (0) means
8.3.7.2 2 M Y N
R-33.
that no attempt was made
Table 2
to assign a quality score. In
this case, no Quality Blocks
are present
8.3.7.3 The quality score shall be 1 M Y N
R-34.
recorded in the first byte of
Table 2
each of the five-byte quality
blocks. Valid values for
quality score are integers
between 0 and 100, and
255.
8.3.7.3 The quality score shall be 3C O-1 Y Y N/A
R-35.
the quantitative expression
Table 2
of the predicted verification
performance of the
biometric sample, per
ISO/IEC 29794-1. For valid
values 0 to 100, higher
values shall indicate better
quality.
8.3.7.3 An entry of “255” shall 3C O-1 Y N N/A
R-36.
indicate a failed attempt to
Table 2
calculate a quality score.
8.3.7.4 The provider of quality 1 M Y N
R-37.
scores shall be uniquely
Table 2
identified by bytes 2 and 3
of the 5-byte quality block.
This Vendor ID shall be Y Y
8.3.7.4 3B M
R-38.
registered with the
Table 2
International Biometrics
Industry Association (IBIA).
8.3.7.5 Bytes 4 and 5 of the 5-byte 1 M Y N
R-39.
quality block shall specify
Table 2
an integer product code
assigned by the vendor of
the Quality Algorithm ID. It
indicates which of the
vendor’s algorithms (and
version) was used in the
calculation of the quality
score and shall be within
the range of 0 to 65535.
8.3.7.5 Multiple quality scores 2 M Y Y
R-40.
calculated by the same
Table 2
© ISO/IEC 2015 – All rights reserved 6
---------------------- Page: 9 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
algorithm (same vendor ID
and algorithm ID) shall not
be present in a single
representation.
The certification record
8.3.8.1 2 M Y N
R-41.
shall consist of a length
Table 2
field followed by zero or
more 3-byte certification
blocks. Each certification
block shall consist of a
certification authority
identifier and a certification
scheme identifier.
8.3.8.1 If the certification block flag 2 M Y N
R-42.
in the general header has a
Table 2
value of 00 , no capture
Hex
device certification
information shall be present
in any of the representation
header records for that
finger image record.
8.3.8.2 The first byte of the 1,2 M Y N
R-43.
certification record is
Table 2
mandatory and shall
contain the number of 3-
byte certification blocks for
the capture device. Valid
values are 0 to 255.
8.3.8.3 The first two bytes of each 1 M Y N
R-44.
3-byte certification block
shall contain the
certification authority
identifier agency or
organization that certified
the device according to a
particular capture device
quality specification.
8.3.8.3 The Certification Authority 3C O-1 Y Y
N/A
R-45.
Identifier shall be registered
by the IBIA or other
approved registration
authority.
8.3.8.4 The 3rd and last byte of 1 M Y N
R-46.
certification block shall
Table 5
identify a certification
scheme identifier used to
certify the capture device as
listed in Table 5.
8.3.9 The one-byte finger or palm 1 M Y N
R-47.
position field shall contain
Table 2
the finger or palm position
Tables 6-8
code. Valid values are 0-10,
13-15, 20-36, and 40-50.
8.3.10 The one-byte 2 M Y N
R-48.
representation number shall
Table 2
contain the specific image
© ISO/IEC 2015 – All rights reserved 7
---------------------- Page: 10 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
representation number
associated with the image
data (or finger, multi finger
or palm image data).
8.3.11 Scale units field shall 3C O-1 Y Y
R-49.
specify the units used to
Table 2
describe the scanning and
image spatial sampling rate
of the image.
8.3.11 Valid values (for scale 1 M Y N
R-50.
units) are 01 (indicating
Hex
Table 2
pixels per inch), or 02
Hex
(indicating pixels per
centimetre).
8.3.12 The two-byte capture 3C O-1 Y Y
R-51.
Table 2 device spatial sampling rate
(horizontal) shall specify the
rounded scanning spatial
sampling rate used in the
horizontal direction.
8.3.13 The two-byte capture 3C O-1 Y Y
R-52.
Table 2 device spatial sampling rate
(vertical) shall specify the
rounded spatial sampling
rate used in the vertical
direction.
8.3.14 The two-byte image spatial 2 M Y Y
R-53.
sampling rate (horizontal)
Table 2
shall specify the rounded
image spatial sampling rate
used in the horizontal
direction. Valid values are
values smaller or equal to
device spatial sampling rate
(horizontal).
8.3.15 The two-byte image spatial 2 M Y Y
R-54.
sampling rate (vertical) shall
Table 2
specify the rounded image
spatial sampling rate used
in the vertical direction.
Valid values are values
smaller or equal to device
spatial sampling rate
(vertical).
8.3.16 The one-byte bit-depth field 1 M Y Y
R-55.
Table 2 shall contain the number of
bits used to represent a
pixel. This field shall
contain an entry of
01 (=1) to 10 (=16).
Hex Hex
8.3.17 The one-byte image 1,2 M Y N
R-56.
compression algorithm field
Table 9
shall specify the method
used to record the
uncompressed or
© ISO/IEC 2015 – All rights reserved 8
---------------------- Page: 11 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
compressed grayscale
images. Valid values are 0
to 6 as listed in Table 9.
If compression algorithm
8.3.17 3C O-1 Y Y
R-57.
code is 0, for grayscale
Table 9
pixels greater than eight
bits, each pixel shall be
recorded in a pair of bytes
right justified.
When the compression
8.3.17 3C O-1 Y Y
R-58.
algorithm code is 2, a
Table 9
certified version of the
Wavelet Scalar
Quantization (WSQ)
algorithm as described in
Annex E shall be used
WSQ compression for 8-bit,
8.3.17 2 M Y Y
R-59.
197 ppcm (500 ppi)
Table 9
grayscale images.shall be
limited to a 15:1
compression ratio.
Y Y
8.3.17 WSQ shall not be used to 2 M
R-60.
compress images scanned
at 394 ppcm (1000 ppi).
JPEG shall not be used for
Y Y
8.3.17 2 M
R-61.
new applications.
8.3.17 Fingerprint/palm print 2 M Y Y
R-62.
images scanned at 394
ppcm (1000 ppi), if
compressed, shall be
compressed using the
JPEG 2000 algorithm as
described in the ISO
Standard 15444.
8.3.17 When JPEG 2000 is used, 3C O-1 Y Y N/A
R-63.
the JPEG 2000 profile
settings as specified in the
"Profile for 1000ppi
Fingerprint Compression"
normative reference are
required to be incorporated.
8.3.17 If compression algorithm is 2 M Y Y
R-64.
5, the ISO/IEC 15948 PNG
algorithm shall be used.
8.3.18 The impression type code 1 M Y N
R-65.
of the finger or palm image
Table 10 3C O-1
shall be recorded in one
byte. Valid values are 0 to
15, and 20 to 29.
8.3.19 The two-byte horizontal line 2 M-2 Y Y
R-66.
length field shall be used to
specify the number of pixels
contained on a single
horizontal line of the
transmitted image.
8.3.20 The two-byte vertical line 2 M-2 Y Y
R-67.
© ISO/IEC 2015 – All rights reserved 9
---------------------- Page: 12 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
length field shall be used to
specify the number of
horizontal lines contained in
the transmitted image.
8.3.21 The 4-byte image data 1 M Y N
R-68.
length field shall contain the
Table 2
length (expressed as the
number of bytes) of the
compressed or
uncompressed image data
contained in this
representation. Valid values
32
are 0 to (2 -58).
8.3.22 The finger or palm image 2 M Y Y
R-69.
data field shall contain the
grayscale image data
formatted and recorded in
accordance with the image
compression algorithm.
Extended data
8.4.1 The size of extended data 3C O-1 Y Y N/A
R-70.
block shall be kept as small
as possible, augmenting the
image data stored in the
standard image data
section.
8.4.1 Any extended data 1 M Y N
R-71.
associated with a finger
representation shall
immediately follow the
standard image data for
that finger representation.
8.4.1 The extended data is not 3C O-1 Y Y N/A
R-72.
intended to allow for
alternate representations of
data that can be
represented in open
manner as defined in this
standard. The intention of
this standard is to provide
interoperability.
8.4.2.1 Extended data block type 2 M Y Y
R-73.
Table 11 identification code shall
have a length of two bytes.
Valid values: A value of
zero in both bytes is a
reserved value and shall
not be used. A value of zero
in the first byte, followed by
a non-zero value in the
second byte, shall indicate
that the extended data
section has a format
defined in this standard;
currently, only
© ISO/IEC 2015 – All rights reserved 10
---------------------- Page: 13 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
segmentation, annotation,
and comment formats are
specified (refer to clauses
8.4.3, 8.4.4, and 8.4.5). A
non-zero value in the first
byte shall indicate a vendor-
specified format with a code
maintained by the vendor.
8.4.2.2 The length of the extended 2 M Y N
R-74.
data section shall be
recorded in two bytes. This
length field includes the
count of the length and type
identification fields (four
bytes total).
8.4.3 If the extended data type 2 M Y N
R-75.
identification code is
0x0001, the extended data
section contains
segmentation and image
quality data for each
segment of the flat
fingerprint image.
8.4.3.1 The segmentation quality 1 M Y N
R-76.
Table 12 assessment algorithm
owner’s ID is encoded in
the first two bytes of the
segmentation data block.
The 16-bit format owner
value is assigned by the
IBIA. A value of 0x00
indicates that segmentation
algorithm and vendor ID is
unreported.
8.4.3.1 Bytes 3 and 4 of the 1 M Y N
R-77.
Table 12 segmentaion block shall
contain a specific identifier
for the segmentation quality
assessment algorithm. This
field contains the binary
representation of the
integer product code and
should be within the range
1 to 65535. This value is
assigned by the
organization, and may be
registered with the IBIA.
8.4.3.2 The one-byte segmentation 1 M Y N
R-78.
quality score shall be a
Table 12 3C O-1
measure of estimated
correctness regarding the
accuracy of the location of
the segmented finger. Valid
values: 0-100 quality score,
254: no attempt to calculate
a segmentation quality
© ISO/IEC 2015 – All rights reserved 11
---------------------- Page: 14 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
score and 255 for a failed
attempt to calculate a
segmentation quality score.
8.4.3.3 The quality assessment 1 M Y N
R-79.
algorithm’s supplier (owner)
Table 12
is contained in the 6th and
7th bytes of a segmentation
data block. This field
contains the binary
representation of the
integer product code and
should be within the range
1 to 65535. This value is
assigned by the
organization, and may be
registered with the IBIA. A
value of 00 indicates that
Hex
the vendor ID is unreported.
8.4.3.3 Bytes 8-9 of a segmentation 1 M Y N
R-80.
block shall contain a
Table 12
specific identifier for the
quality assessment
algorithm. Valid values: 1 to
65535.
8.4.3.4 The number of Finger Data 2 M Y N
R-81.
Table 12 Segment blocks shall be
equal to the number stated
in the Number of Segments
field.
8.4.3.4 Valid values for number of 1 M Y N
R-82.
Table 12 segments field are 0 to 4,
and 255.
If an image is multi-finger
8.4.3.4 2 M Y Y
R-83.
impression then the number
of segments shall be 0.
If the segmentation attempt
8.4.3.4 2 M Y N
R-84.
fails then the number of
segments shall be 255.
8.4.3.5.1 Each finger segment shall 2 M Y Y
R-85.
be defined by finger
Table 12
position, image quality, the
number of points used to
define the segment and the
coordinates of each point.
8.4.3.5.2 Finger position of 1 M Y N
R-86.
Table 12, segmented finger in one
Table 6 byte. Valid values: 0 to 10,
and 13 to 15.
8.4.3.5.3 Finger image quality is 3C O-1 Y N N/A
R-87.
Table 12 encoded in the 2nd byte of
finger segmant data shall
be a quantitative expression
of the predicted verification
performance of the
biometric sample.
© ISO/IEC 2015 – All rights reserved 12
---------------------- Page: 15 ----------------------
ISO/IEC 19794-2:2011/Amd 2:2015(E)
Requirement Governing Requirement Summary Level Status Binary XML Format IUT Supported Test
Identifier section Format Applicability Support Range Result
Applicability
8.4.3.5.3 The finger image quality of 3C O-1 Y N N/A
R-88.
Table 12 a segmentation block is
calculated by the algorithm
identified by finger quality
owner ID.
8.4.3.5.3 Valid values for finger 2 M Y N
R-89.
Table 12 image quality of a
segmentation block are: 0
to 100, 254(not reported)
and 255(failed attempt)
8.4.3.5.4 The third byte in a finger 3C O-1 Y N N/A
R-90.
Table 12 segment data block shall
specify the number of
points or vertexes used to
enclose the segmented
image.
For a finger segment
8.4.3.5.4 1 M Y N
R-91.
enclosed by an n-sided
polygon, this byte shall
contain a value between 4
and 99.
Y Y
8.4.3.5.4 The order of the vertices 3C O-1 N/A
R-92.
shall be in their consecutive
order around the perimeter
of the polygon, either
clockwise or
counterclockwise. The
polygon side defined by the
last subfield and the first
subfield shall complete the
polygon. The polygon shall
be a simple, plane figure
with no
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.