ISO/IEC 19794-4:2011/Amd 1:2013

INTERNATIONAL ISO/IEC
STANDARD 19794-4
Second edition
2011-12-15
AMENDMENT 1
2013-06-15

Information technology — Biometric data
interchange formats —
Part 4:
Finger image data
AMENDMENT 1: Conformance testing
methodology 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 1: Méthodologie d'essai de conformité et précisions
concernant les défauts




Reference number
ISO/IEC 19794-4:2011/Amd.1:2013(E)
©
ISO/IEC 2013

---------------------- Page: 1 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO/IEC 2013
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
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland

ii © ISO/IEC 2013 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(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.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
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.
Amendment 1 to ISO/IEC 19794-4:2011 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 37, Biometrics.

© ISO/IEC 2013 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)

Information technology — Biometric data interchange
formats —
Part 4:
Finger image data
AMENDMENT 1: Conformance testing methodology and clarification
of defects
1. The following text is to be added to the "Introduction" clause of ISO/IEC 19794-4:
Annex A addresses conformance testing to this part of ISO/IEC 19794. Annex A is distinct from
ISO/IEC 29109-4, which addresses conformance testing to ISO/IEC 19794-4:2005.
2. The following text is to be added to the "Scope" clause of ISO/IEC 19794-4:
This part of ISO/IEC 19794 also specifies elements of conformance testing methodology, test assertions,
and test procedures as applicable to this part of ISO/IEC 19794. It establishes test assertions pertaining to
the structure of the finger image data format (Type A Level 1 as defined in ISO/IEC 19794-1:2011 AMD
1), test assertions pertaining to internal consistency of the types of values that may be contained within
each field (Type A Level 2 as defined in ISO/IEC 19794-1:2011 AMD 1), and semantic test assertions
(Type A Level 3 as defined in ISO/IEC 19794-1:2011 AMD 1).
The conformance testing methodology specified in this part of ISO/IEC 19794 does not establish:
 tests of other characteristics of biometric products or other types of testing of biometric products
(e.g. acceptance, performance, robustness, security),
 tests of conformance of systems that do not produce data records conforming to the
requirements of this part of ISO/IEC 19794.
3. The following text is to be added to the "Conformance" clause of ISO/IEC 19794-4:
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 clause 8. Specifically, they shall use the test methodology
specified in Clauses A.1, A.2 and A.3 of ISO/IEC 19794-1:2011 AMD 1, and all Level 1, Level 2 and Level
3 tests shall use the assertions defined in Table A.2 of Clause A.3 of this part of ISO/IEC 19794 in
1
conformity with the concept and rules set in 19794-1 Annex A .
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

1
Annex A is specified in ISO/IEC 19794-1:2011 Amendment 1.
© ISO/IEC 2013 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
implementation in an implementation conformance statement (ICS), filled out in accordance with Clause
A.3 of ISO/IEC 19794-1:2011 AMD 1 and Table A.2 of Clause A.3 of this part of ISO/IEC 19794.
4. In clause 8.3.1 of ISO/IEC 19794-4:2011, Table 2, row “Image compression algorithm”, Replace “0 to 5”
with “0 to 6”.
5. Replace Annex A of ISO/IEC 19794-4:2011 with the following one:
2 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Annex A
(normative)

Conformance testing methodology
A.1 Introduction
This normative annex specifies elements of conformance testing methodology, test assertions, and test
procedures as applicable to this part of biometric data interchange format standard. Specifically, it establishes
 test assertions of the structure of the finger image data format as specified in this Part of ISO/IEC 19794
(Type A Level 1 as defined in ISO/IEC 19794-1:2011 AMD 1),
 test asssertions of internal consistency by checking the types of values that maybe contained within each
field (Type A Level 2 as defined in ISO/IEC 19794-1:2011 AMD 1),
 tests of semantic assertions (Type A Level 3 as defined in ISO/IEC 19794-1:2011 AMD 1).
This normative annex does not establish
 test assertions on other characteristics of biometric products (e.g. acceptance, performance, robustness,
security),
 conformance test assertions on systems that do not produce finger image record as specified in this part
of ISO/IEC 19794.
The conformance testing methodology specified in ISO/IEC 19794-1: 2011 AMD 1 shall apply. The content of
the tables below is based on ISO/IEC 19794-1:2011, AMD 1 and shall only be used in the context of that
conformance testing methodology.
A.2 Table of requirements
The normative requirements specified in this Part of ISO/IEC 19794 are listed in Table A.1. 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.
Table A.1 — Data format requirements specified in this Part of ISO/IEC 19794
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
Finger image general header
8.1 Each record shall pertain to a single subject. 3C O-1 N/A N/A
R-1.
8.1 Each record shall contain at least one 3C O-1 N/A N/A
R-2.
representation for each of one or more fingers,
multiple fingers (single image records), or palms.
8.2.1 Information shall be included for each field within 1 M
R-3.
the header.
The format identifier shall be recorded in four
8.2.2 1 M
R-4.
bytes.
Table 1
© ISO/IEC 2013 – All rights reserved 3

---------------------- Page: 6 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.2.2 The format identifier shall consist of three 1 M N/A
R-5.
characters "FIR" (0x464952) followed by a zero
Table 1
byte as a NULL string terminator. Therefore, the
format identifier shall be 0x46495200.
8.2.3 The Version Number shall be recorded in four 1 M N/A
R-6.
bytes.
Table 1
8.2.3 This version number shall consist of three ASCII 1 M N/A
R-7.
numerals “020” (0x30323000) followed by zero
Table 1
byte as a NULL string terminator.
8.2.4 The length (in bytes) of the entire image data 2 M
R-8.
record shall be recorded in four bytes. Valid values
Table 1
32
are 57 to (2 -1 )
8.2.4 This length of entire record shall be total length of 2 M
R-9.
the general record header and one or more
representation records.
8.2.5 The total number of finger image representations 1,2 M
R-10.
contained in the finger image data record shall be
Table 1
recorded in two bytes. Valid values are 1 to 672.
8.2.5 A minimum of one representation is required. 1 M
R-11.
8.2.6 The one-byte certification flag shall indicate 1 M
R-12.
whether each representation header includes a
Table 1
certification record. Valid values are 00 and
Hex
01 .
Hex
8.2.6 A value of 00 shall indicate that none of the 2 M
Hex
R-13.
representations contains a certification record.
8.2.6 A value of 01 shall indicate that all 2 M
Hex
R-14.
representations contain a certification record.
8.2.7 The number of finger or palm images included in 1 M
R-15.
the record shall be recorded in one byte. Valid
Table 1
values are 1 to FF .
HEX
Finger image representation header
8.3.1 A finger or palm representation header shall start 3C O-1 N/A N/A
R-16.
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 shall be one finger 2 M N/A
R-17.
header record accompanying the representation of
the image data.
8.3.1 The representaion header shall occupy a minimum 2 M
R-18.
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 uncompressed image data for 3C O-1 N/A N/A
R-19.
that image representation shall immediately follow
the image representation header.
8.3.1 Subsequent image representations (including the 3C O-1 N/A N/A
R-20.
image representation header) will be concatenated
to the end of the previous image representation.
4 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.3.2 The four-byte representation length field shall 2 M
R-21.
contain the length in bytes of the finger
Table 2
representation including the representation header
fields. The minimum length is 41.
8.3.3 Capture date-time field shall indicate the date and 3C O-1
R-22.
time the representation was captured. This field is
Table 2
not intended to encode the time the record was
instantiated.
8.3.3 Capture time field shall be encoded in accordance 1 M
R-23.
to the requirements given in Part 1 of this standard.
Table 2
Parts of the capture date and time that are
unknown shall be filled with FF , or FFFF for
Hex Hex
two-byte components and all subsequent
components shall be unknown.
8.3.4 The one-byte capture device technology ID shall 1 M
R-24.
contain the entry chosen from Table 4 to indicate
Table 4
the technology type used by the capture device.
Valid values are 0 to 20.
8.3.5 The capture device vendor ID shall be recorded in 1 M
R-25.
two bytes.
Table 2
8.3.5 The capture device vendor ID shall identify the 3B M
R-26.
biometric organisation that owns the product that
Table 2
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 shall be recorded in 1 M
R-27.
two bytes.
Table 2
8.3.6 This capture device type ID shall identify the 3C O-1  N/A
R-28.
product type that created the biometric record and
Table 2
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 the overall finger image 1 M
R-29.
data shall be recorded in one or more five-byte
blocks.
8.3.7.1 Each of these blocks shall pertain to a specific 2 M
R-30.
quality/vendor/algorithm evaluation.
8.3.7.2 The first byte of the quality record is mandatory 2 M
R-31.
and shall contain the number of subsequent quality
Table 2
blocks. Valid values are 0 to 255.
8.3.7.2 Subsequent 5-byte blocks shall contain the specific 1,3BM
R-32.
quality/vendor/algorithm information for each
Table 2
quality/vendor/algorithm evaluation.
A value of zero (0) means that no attempt was
8.3.7.2 2 M
R-33.
made to assign a quality score. In this case, no
Table 2
Quality Blocks are present.
8.3.7.3 The quality score shall be recorded in the first byte 1 M
R-34.
of each of the five-byte quality blocks. Valid values
Table 2
for quality score are integers between 0 and 100,
and 255.
© ISO/IEC 2013 – All rights reserved 5

---------------------- Page: 8 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.3.7.3 The quality score shall be the quantitative 3C O-1  N/A
R-35.
expression of the predicted verification
Table 2
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 indicate a failed attempt to 3C O-1  N/A
R-36.
calculate a quality score.
Table 2
8.3.7.4 The provider of quality scores shall be uniquely 1 M
R-37.
identified by bytes 2 and 3 of the 5-byte quality
Table 2
block.
8.3.7.4 This Vendor ID shall be registered with the 3B M
R-38.
International Biometrics Industry Association
Table 2
(IBIA).
8.3.7.5 Bytes 4 and 5 of the 5-byte quality block shall 1 M
R-39.
specify an integer product code assigned by the
Table 2
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 calculated by the same 2 M
R-40.
algorithm (same vendor ID and algorithm ID) shall
Table 2
not be present in a single representation.
The certification record shall consist of a length
8.3.8.1 2 M
R-41.
field followed by zero or more 3-byte certification
Table 2
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 in the general header 2 M
R-42.
has a value of 00 , no capture device certification
Hex
Table 2
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 certification record is 1,2 M
R-43.
mandatory and shall contain the number of 3-byte
Table 2
certification blocks for the capture device. Valid
values are 0 to 255.
8.3.8.3 The first two bytes of each 3-byte certification block 1 M
R-44.
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 Identifier shall be 3C O-1  N/A
R-45.
registered by the IBIA or other approved
registration authority.
8.3.8.4 The 3rd and last byte of certification block shall 1 M
R-46.
identify a certification scheme identifier used to
Table 5
certify the capture device as listed in Table 5.
8.3.9 The one-byte finger or palm position field shall 1 M
R-47.
contain the finger or palm position code. Valid
Table 2
values are 0-10, 13-15, 20-36, and 40-50.
Tables 6-8
8.3.10 The one-byte representation number shall contain 2 M
R-48.
the specific image representation number
Table 2
associated with the image data (or finger, multi
finger or palm image data).
6 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 9 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.3.11 Scale units field shall specify the units used to 3C O-1
R-49.
describe the scanning and image spatial sampling
Table 2
rate of the image.
8.3.11 Valid values (for scale units) are 01 (indicating 1 M
Hex
R-50.
pixels per inch), or 02 (indicating pixels per
Hex
Table 2
centimetre).
8.3.12 The two-byte capture device spatial sampling rate 3C O-1
R-51.
Table 2 (horizontal) shall specify the rounded scanning
spatial sampling rate used in the horizontal
direction.
8.3.13 The two-byte capture device spatial sampling rate 3C O-1
R-52.
Table 2 (vertical) shall specify the rounded spatial sampling
rate used in the vertical direction.
8.3.14 The two-byte image spatial sampling rate 2 M
R-53.
(horizontal) shall specify the rounded image spatial
Table 2
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 sampling rate (vertical) 2 M
R-54.
shall specify the rounded image spatial sampling
Table 2
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 shall contain the 1 M
R-55.
Table 2 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 compression algorithm field 1,2 M
R-56.
shall specify the method used to record the
Table 9
uncompressed or compressed grayscale images.
Valid values are 0 to 6 as listed in Table 9.
If compression algorithm code is 0, for grayscale
8.3.17 3C O-1
R-57.
pixels greater than eight bits, each pixel shall be
Table 9
recorded in a pair of bytes right justified.
When the compression algorithm code is 2, a
8.3.17 3C O-1
R-58.
certified version of the Wavelet Scalar Quantization
Table 9
(WSQ) algorithm as described in Annex E shall be
used.
WSQ compression for 8-bit, 197 ppcm (500 ppi)
8.3.17 2 M
R-59.
grayscale images.shall be limited to a 15:1
Table 9
compression ratio.
8.3.17 WSQ shall not be used to compress images 2 M
R-60.
scanned at 394 ppcm (1000 ppi).
JPEG shall not be used for new applications.
8.3.17 2 M
R-61.
8.3.17 Fingerprint/palm print images scanned at 394 2 M
R-62.
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, the JPEG 2000 profile 3C O-1  N/A
R-63.
settings as specified in the "Profile for 1000ppi
Fingerprint Compression" normative reference are
required to be incorporated.
8.3.17 If compression algorithm is 5, the ISO/IEC 15948 2 M
R-64.
PNG algorithm shall be used.
© ISO/IEC 2013 – All rights reserved 7

---------------------- Page: 10 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.3.18 The impression type code of the finger or palm 1 M
R-65.
image shall be recorded in one byte. Valid values
Table 10 3C O-1
are 0 to 15, and 20 to 29.
8.3.19 The two-byte horizontal line length field shall be 2 M-2
R-66.
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 length field shall be used 2 M-2
R-67.
to specify the number of horizontal lines contained
in the transmitted image.
8.3.21 The 4-byte image data length field shall contain the 1 M
R-68.
length (expressed as the number of bytes) of the
Table 2
compressed or uncompressed image data
contained in this representation. Valid values are 0
32
to (2 -58).
8.3.22 The finger or palm image data field shall contain 2 M
R-69.
the grayscale image data formatted and recorded
in accordance with the image compression
algorithm.
Extended data
8.4.1 The size of extended data block shall be kept as 3C O-1  N/A
R-70.
small as possible, augmenting the image data
stored in the standard image data section.
8.4.1 The extended data for each finger representation 1 M
R-71.
shall immediately follow the standard image data
for that finger representation.
8.4.1 The extended data is not intended to allow for 3C O-1  N/A
R-72.
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 identification code shall 2 M
R-73.
Table 11 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
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 data section shall be 2 M
R-74.
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 identification code is 2 M
R-75.
0x0001, the extended data section contains
segmentation and image quality data for each
segment of the flat fingerprint image.
8 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 11 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.4.3.1 The segmentation quality assessment algorithm 1 M
R-76.
Table 12 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 segmentaion block shall 1 M
R-77.
Table 12 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 quality score shall be a 1 M
R-78.
measure of estimated correctness regarding the
Table 12 3C O-1
accuracy of the location of the segmented finger.
Valid values: 0-100 quality score, 254: no attempt
to calculate a segmentation quality score and 255
for a failed attempt to calculate a segmentation
quality score.
8.4.3.3 The quality assessment algorithm’s supplier 1 M
R-79.
(owner) is contained in the 6th and 7th bytes of a
Table 12
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
Hex
that the vendor ID is unreported.
8.4.3.3 Bytes 8-9 of a segmentation block shall contain a 1 M
R-80.
specific identifier for the quality assessment
Table 12
algorithm. Valid values: 1 to 65535.
8.4.3.4 The number of Finger Data Segment blocks shall 2 M
R-81.
Table 12 be equal to the number stated in the Number of
Segments field.
8.4.3.4 Valid values for number of segments field are 0 to 1 M
R-82.
Table 12 4, and 255.
If an image is multi-finger impression then the
8.4.3.4 2 M
R-83.
number of segments shall be 0.
If the segmentation attempt fails then the number
8.4.3.4 2 M
R-84.
of segments shall be 255.
8.4.3.5.1 Each finger segment shall be defined by finger 2 M
R-85.
position, image quality, the number of points used
Table 12
to define the segment and the coordinates of each
point.
8.4.3.5.2 Finger position of segmented finger in one byte.
1 M
R-86.
Table 12, Valid values: 0 to 10, and 13 to 15.
Table 6
8.4.3.5.3 Finger image quality is encoded in the 2nd byte of 3C O-1  N/A
R-87.
Table 12 finger segmant data shall be a quantitative
expression of the predicted verification
performance of the biometric sample.
8.4.3.5.3 The finger image quality of a segmentation block is 3C O-1  N/A
R-88.
Table 12 calculated by the algorithm identified by finger
quality owner ID.
© ISO/IEC 2013 – All rights reserved 9

---------------------- Page: 12 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Requirement Governing Requirement Summary Level Status IUT Supported Test
Identifier section Support Range Result
8.4.3.5.3 Valid values for finger image quality of a 2 M
R-89.
Table 12 segmentation block are: 0 to 100, 254 (not
reported) and 255 (failed attempt)
8.4.3.5.4 The third byte in a finger segment data block shall 3C O-1  N/A
R-90.
Table 12 specify the number of points or vertexes used to
enclose the segmented image.
For a finger segment enclosed by an n-sided
8.4.3.5.4 1 M
R-91.
polygon, this byte shall contain a value between 4
and 99.
8.4.3.5.4 The order of the vertices shall be in their 3C O-1  N/A
R-92.
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
sides crossing and no interior holes. Each vertex
of the rectangle or polygon shall be represented by
a pair of coordinates.
8.4.3.5.4 No two vertices may occupy the same location. 2 M
R-93.
Two bytes shall be used to contain the horizontal
8.4.3.5.4.1 1 M
R-94.
pixel offset to the right relative to the origin
positioned in the upper left corner of the image.
Two bytes shall be used to contain the vertical
8.4.3.5.4.2 1 M
R-95.
pixel offset down relative to the origin positioned in
the upper left corner of the image.
8.4.3.5.5 This one byte field shall encode the angle between 1 M
R-96.
the longitudinal axis of the finger and the horizontal
axis to the right.
8.4.3.5.5 The integer value encoded shall be the physical 3A O
R-97.
estimate of the angle in degrees divided by
1.40625
8.4.4 If the extended data type identification code is 2 M
R-98.
0x0002, the extended data section contains
annotation information.
8.4.4.1 The one-byte number of annotations shall contain 2 M
R-99.
the number of annotations that follow. Each
Table 13
annotation will consists of two information items.
8.4.4.1 The valid values for the number of annotations are 2 M
R-100.
1 to 4.
Table 13
8.4.4.2 Finger position shall be encoded in byte 2 of 1 M
R-101.
Table 13 annotation block. Valid values are 0 to 10, 13 to 15,
20 to 36, and 40 to 50.
8.4.4.3 Annotation code shall be encoded in byte 3 of 1 M
R-102.
annotation block. Valid values are 01 for an
Hex
Table 13
amputated finger and 02 for a bandaged or
Hex
otherwise unable to print finger.
8.4.5 If the extended data type identification code is 2 M
R-103.
0003 , the extended data section contains ASCII
Hex
text information associated with the captured
image or subject supplying the image. The
comment is inputted by the individual generating
the fingerprint or palmprint record. A null terminator
for the ASCII string is not necessary, as the length
is provided.
10 © ISO/IEC 2013 – All rights reserved

---------------------- Page: 13 ----------------------
ISO/IEC 19794-4:2011/Amd.1:2013(E)
Status Notes:
The following short notes provide more details about why a specific conformance test assertion is not specified for the
corresponding requirement(s):
O-1. Level 3 Assertion is too difficult to test. No method has been defined to test the conformance of the IUT or BDIR
for this mandatory requirement of the base standard.
M-2. No level 1 test is associated with this requirement, because the test will always pass.
A.3 Table of test assertions
The specific test assertions required for conformance testing to t
...