ISO/IEC 19794-8:2011/Amd 1:2014
(Amendment)Information technology — Biometric data interchange formats — Part 8: Finger pattern skeletal data — Amendment 1: Conformance testing methodology
Information technology — Biometric data interchange formats — Part 8: Finger pattern skeletal data — Amendment 1: Conformance testing methodology
Technologies de l'information — Formats d'échange de données biométriques — Partie 8: Données des structures du squelette de l'empreinte — Amendement 1: Méthodologie d'essai de conformité
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 19794-8
Second edition
2011-12-15
AMENDMENT 1
2014-03-15
Corrected version
2014-04-01
Information technology — Biometric data
interchange formats —
Part 8:
Finger pattern skeletal data
AMENDMENT 1: Conformance testing
methodology
Technologies de l'information — Formats d'échange de données
biométriques —
Partie 8: Données des structures du squelette de l'empreinte
AMENDEMENT 1: Méthodologie d'essai de conformité
Reference number
ISO/IEC 19794-8:2011/Amd.1:2014(E)
©
ISO/IEC 2014
---------------------- Page: 1 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2014
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 2014 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(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-8:2011 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 37, Biometrics.
This corrected version of ISO/IEC 19794-8:2011/Amd.1:2014 corrects the Amendment number in the top right
corner on the cover page.
© ISO/IEC 2014 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Information technology — Biometric data interchange
formats —
Part 8:
Finger pattern skeletal data
AMENDMENT 1: Conformance testing methodology
1. The following text is to be added to the "Introduction" clause of ISO/IEC 19794-8:
Annex A to document addresses the conformance testing to be used for interchange format defined in this
part of ISO/IEC 19794. This Annex A is distinct from the ISO/IEC 29109-8, which addressed conformance
testing only of the first, 2007, edition of the ISO/IEC 19794-8 standard.
2. The following text is to be added to the "Scope" clause of ISO/IEC 19794-8:
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. Specifically, it establishes
test assertions of the structure of the finger pattern skeletal data format as specified in Clauses 7 and 8
of this part of ISO/IEC 19794 (Type A Level 1 as defined in ISO/IEC 19794-1:2011 AMD 1),
test assertions of internal consistency by checking 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),
tests of semantic 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-8:
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 clauses 6, 7, and 8. Specifically, they shall use the test
methodology specified in 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.1 of Clause A.2 in this part of ISO/IEC 19794.
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.
In consideration of the semantic specifics in different parts of 19794, 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 19794 in conformity with the concept and
rules set in 19794-1 Annex A.
© ISO/IEC 2014 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
4. Replace 3rd paragraph of Clause 6.2.3 "Constructing direction elements" with the following:
In order to minimize integration of digitalisation error, each starting point must be computed with relatively high
accuracy, i.e. its resolution shall be at least 100 times finer than the spatial resolution of the minutiae.
5. Replace the normative annex in ISO/IEC 19794-8:2011 with the following one:
2 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Annex A
(normative)
Conformance Testing Methodology
A.1 Introduction
The testing methodology specified in ISO/IEC 19794-1:2011 AMD 1 shall apply. The content of the tables
below is based on the conformance testing methodology outlined in ISO/IEC 19794-1:2011 AMD 1 and shall
only be used in the context of that testing methodology.
A.2 Table of requirements in the base standard
The normative requirements of 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 should
note the results of the test.
Table A.1 — Requirements of the Base Standard
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
Minutiae are points located at the
places in the fingerprint image
where friction ridges end or split
into two ridges. Each minutia point
Y Y Y
R-1 6.1.1 1 M N/A
has a “type” associated with it.
There are two major types of
minutia: a “ridge ending”
represented by the 2-bit value 01
and a “ridge bifurcation” or split
point represented by 2-bit value 10.
The coordinate system used to
express the position of the
minutiae points of a fingerprint
shall be a Cartesian coordinate
system.
For the skeletal pattern card
format, the resolution of the x and y
coordinates of the minutia shall be
in metric units.
The position of the minutia for a
R-2 6.1.2 3C O-1 Y Y Y N/A N/A
ridge ending shall be defined as
the coordinates of the skeleton
point with only one neighbour pixel
belonging to the skeleton.
The position of the minutia for a
ridge bifurcation shall be defined
as the point of forking of the
skeleton of the ridge. The position
of a virtual ending shall be defined
like the position of a real ridge
ending.
© ISO/IEC 2014 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
The direction of the lines starting or
ending at a point with more than
three arms (trifurcation, etc.) shall
R-3 6.1.3 be defined like the direction of a 3C O-1 Y Y Y N/A N/A
real ridge ending. The direction of
a virtual ending shall be defined
like the direction of a real ridge
ending.
To keep the encoding size small a
line shall start with a real minutia
(type 01 or 10) if possible.
No assumption shall be made
about the order of the line
encodings in the record.
The skeleton shall be encoded only
for image areas where the ridge
lines are displayed with a sufficient
quality.
The reconstructed ridge lines shall
R-4 6.2.2 3C O-1 Y Y Y N/A N/A
describe the fingerprint image in
ridge position and structure.
The reconstructed skeleton line
polygon element shall be inside the
area of the ridge it is describing for
most part of its length.
The reconstructed skeleton line
shall never be inside the area of
any other ridge but the one it is
describing.
The reconstructed skeleton line
shall preserve the topology of the
ridges.
In order to minimize integration of
digitalisation error, each starting
point must be computed with
R-5 6.2.3 3C O-1 Y Y Y N/A N/A
relatively high accuracy, i.e. its
resolution shall be at least 100
times finer than the spatial
resolution of the minutiae.
If the direction change of the
skeleton line cannot be described
by a direction element, the line
R-6 6.2.3 3C O-1 Y Y Y N/A N/A
encoding shall be interrupted by a
“virtual continuation” and a new
line encoding shall begin with the
same point without repeating the
minutia data.
It is not usefull to list a
R-7 6.3.2 neighourhood relation twice, any of 3A M Y Y Y
the other indices shall be different
i.e. Ai-1>Ai.
4 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
There shall be one and only one
record header for the finger pattern
7.3, Table
skeletal data record. The record
R-8 3A M Y N N
header will contain information
1
describing the identity and
characteristics of the device that
generated the data.
The finger pattern skeletal data
record shall begin with a format
identifier to be recorded in four
7.3.1,
R-9 1 M Y N N
bytes. For this part of ISO/IEC
Table 1
19794, it shall consist of the three
ASCII characters “FSK”, followed
by a zero byte as a NULL string
terminator.
The version number for the version
7.3.2,
R-10 of this part of ISO/IEC 19794 used 1 M Y N N
Table 1
in constructing the record shall be
placed in four bytes.
This version number shall consist
of three ASCII numerals followed
by a zero byte as a NULL string
terminator. The first and second
character will represent the major
7.3.2,
R-11 1 M Y N N
revision number and the third
Table 1
character will represent the minor
revision number. Upon approval of
this specification, the version
number shall be “020” (an ASCII
‘0’followed by an ASCII ‘2’ and an
ASCII ‘0’).
7.3.3,
R-12 1 M Y N N
The length of the entire BDIR shall
Table 1
be recorded in four bytes.
This count shall be the total length
7.3.3,
R-13 1 M Y N N
of the BDIR including the general
Table 1
record header and one or more
representation records.
The total number of representation
records contained in the BDIR shall
R-14 7.3.4 1 M Y N N
be recorded in two bytes. A
minimum of one representation is
required.
The one-byte certification flag shall
indicate whether each
Representation Header includes a
certification block. A value of
R-15 7.3.5 1 M Y N N
00HEX shall indicate that no
representation contains a
certification block. A value of
01HEX shall indicate that all
representations contain a certifica-
tion block.
© ISO/IEC 2014 – All rights reserved 5
---------------------- Page: 8 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
A finger pattern skeletal
representation header shall start
each area of finger data providing
information for that finger. There
shall be one finger pattern skeletal
representation header for each
finger contained in the finger
R-16 7.4.1 pattern skeletal data record. The 1 M Y Y Y
finger pattern skeletal
representation header will occupy
at least 31 bytes as described
below. Note that it is permissible
for more than one single finger
record to represent the same
finger, with (presumably) different
data.
The representation-length field
R17 7.4.1.1 1 M Y Y Y
denotes the length in bytes of the
representation including the
representation header fields
The capture date and time field
shall indicate when the capture of
this representation started in
Coordinated Universal Time (UTC).
The capture date and time field
R-18 7.4.1.2 shall consist of 9 bytes. Its value 1 M Y Y Y
shall be encoded in the form given
in ISO/IEC 19794-1.This field shall
indicate the date and time the
representation was captured. This
field is not intended encode the
time the record was instantiated.
The capture device technology ID
shall be encoded in one byte. This
R-19 7.4.1.3 field shall indicate the class of 1 M Y Y Y
capture device technology used to
acquire the captured biometric
sample.
A value of 00HEX indicates
R-20 7.4.1.3 unknown or unspecified
1 M Y Y Y
technology. See Table 2 for the list
of possible values.
The capture device vendor
identifier shall be recorded in two
bytes. It shall identify the biometric
R-21 7.4.1.4 1 M Y Y Y
organisation that owns the product
that created the BDB and shall be
registered with the IBIA or other
approved registration authority.
A value of all zeros shall indicate
R-22 7.4.1.4
that the capture device vendor is 1 M Y Y Y
unreported.
6 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
This capture device type identifier
shall be recorded in two bytes. It
shall identify the product type that
created the BDB and shall be
R-23 7.4.1.5
assigned by the registered BDB 1 M Y Y Y
product owner or other approved
registration authority. A value of all
zeros shall indicate that the
capture device type is unreported.
The quality information of the
R-24 7.4.1.6.1
1 M Y Y Y
overall finger minutiae data shall
be recorded in five bytes.
The first byte is mandatory and
R-25 7.4.1.6.2 shall contain the number of blocks
1 M Y Y Y
of quality information of the overall
finger pattern skeletal data.
Subsequent 5-byte blocks shall
contain the specific
R-26 7.4.1.6.2
quality/vendor/algorithm
1 M Y Y Y
information for each
quality/vendor/algorithm
evaluation.
A value of zero (0) means that no
R-27 7.4.1.6.2 attempt was made to assign a
1 M Y Y Y
quality score. In this case, no
Quality Blocks are present.
Quality score, as defined in
ISO/IEC 29794-1, shall be a
quantitative expression of the
predicted verification performance
R-28 7.4.1.6.3
1 M Y Y Y
of the biometric sample. Valid
values for Quality Score are
integers between 0 and 100, where
higher values indicate better
quality.
A value of 255 is to handle a
special case. An entry of 255 shall
indicate a failed attempt to
calculate a quality score. Multiple
R-29 7.4.1.6.3
quality scores calculated by the 1 M Y Y Y
same algorithm (same vendor
identifier and Quality Algorithm
identifier) shall not be present in a
single representation.
To enable the recipient of the
quality score to differentiate
between quality scores generated
by different algorithms, the provider
R-30 7.4.1.6.4
of quality scores shall be uniquely
1 M Y Y Y
identified by the next two bytes.
This Vendor identifier shall be
registered with the International
Biometrics Industry Association
(IBIA).
© ISO/IEC 2014 – All rights reserved 7
---------------------- Page: 10 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
The remaining two bytes shall
specify an integer product code
assigned by the vendor of the
Quality Algorithm ID. It indicates
R-31 7.4.1.6.5
which of the vendor’s algorithms 1 M Y Y Y
(and version) was used in the
calculation of the quality score and
must be within the range of 1 to
65535.
This multi-byte block contains
information to indicate the
compliant certification procedures
that were used to test the biometric
capture equipment used. If the
R-32 7.4.1.7.1 device certification block flag in the
1 M Y Y Y
general header has a value of 00
HEX, no capture device
certification information shall be
present in any of the
representation header records for
that finger pattern skeletal record.
The first byte is mandatory and
shall contain the number of
successful certifications for the
capture device. This byte is
followed by 3-byte sub-blocks
R-33 7.4.1.7.2
1 M Y Y Y
containing certification information.
A value of 00 HEX in this first byte
shall indicate that this capture
device has not been certified and
no certification information sub-
blocks follow.
Certification authority identifier
shall be encoded in two bytes.
Certification Authority is the agency
that certifies a device according to
R-34 7.4.1.7.3
a particular capture device quality 1 O Y Y Y
specification. Certification
authority identifier shall be
registered by the IBIA or other
approved registration authority.
This last byte of the sub-block shall
identify a certification scheme used
R-35 7.4.1.7.4
1 O Y Y Y
to certify the capture device. A list
of current certification scheme
identifiers is contained in Table 3.
8 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
The finger position code shown on
Table 4 shall be recorded in one
byte. The codes for this byte shall
be as defined in Table 5 of
ANSI/NIST-ITL 1-2007, “Data
format for the interchange of
R-36 7.4.1.8
fingerprint information”. This table 1 M Y Y Y
is reproduced here in Table 2 for
convenience. Only codes 0 through
10 shall be used, the “plain” codes
included in Table 5 of ANSI/NIST
ITL 1-2007 are not relevant for this
part of ISO/IEC 19794.
If more than one finger pattern
record in a general record is from
the same finger, each pattern
record shall have a unique
representation number. The
combination of finger location and
representation number shall
uniquely identify a particular
R-37 7.4.1.9 2 M Y Y Y
pattern record within a general
record. Multiple finger pattern
records from the same finger shall
be numbered with increasing
representation numbers, beginning
with zero. Where only one finger
pattern record is taken from each
finger, this field shall be set to 0.
The representation number shall
be recorded in one byte.
The resolution (in ppcm) of the
R-38 7.4.1.10 scaled finger image(s) shall be 1 M Y N N
uniform in the x and y-directions
and shall be stored in 1 byte.
The impression type of the finger
images that the finger pattern
skeletal data was derived from
shall be recorded in one byte. The
codes for this byte are shown in
Table 5. These codes are derived
from Table 11 of ANSI/NIST-ITL 1-
2007, “Data Format for the
R-39 7.4.1.11 1 M Y Y Y
Interchange of Fingerprint Facial, &
Other Biometric Information”. The
“swipe” type identifies data records
derived from image streams
generated by sliding the finger
across a small sensor. Only codes
0 through 3, 8, 24 and 28 through
29 shall be used; the “latent” and
“palm” codes are not relevant for
this part of ISO/IEC 19794.
The size of the skeleton image in
R-40 7.4.1.12 1 M Y Y Y
pixels in the x direction shall be
contained in 2 bytes.
The size of the skeleton image in
R-41 7.4.1.13 1 M Y Y Y
pixels in the y direction shall be
contained in 2 bytes.
© ISO/IEC 2014 – All rights reserved 9
---------------------- Page: 12 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
The bit-depth used to represent the
x and y-coordinate of the starting
R-42 7.4.1.14 1 M Y N N
and ending point in the direction
code description of the skeleton
shall be recorded in 1 byte.
The bit-depth used to represent the
direction of the starting and ending
R-43 7.4.1.15 1 M Y N N
point in the direction code
description of the skeleton shall be
recorded in 1 byte.
The bit-depth used to represent the
R-44 7.4.1.16
direction in the direction code shall 1 M Y N N
be recorded in 1 byte.
The maximal step size Ss in the
R-45 7.4.1.17
current direction of each direction
1 M Y N N
code step shall be recorded in 1
byte.
The relative perpendicular step
R-46 7.4.1.18 size floor(256 Sp/Ss) of the
1 M Y N N
direction code shall be recorded in
1 byte.
The angular resolution of the
R-47 7.4.1.19
direction code is stored as the
1 M Y N N
number N of directions on 180°
and shall be recorded in 1 byte.
The length (in bytes) of the finger
pattern skeletal data block
recorded for the finger shall be
R-48 7.4.1.20
recorded in two bytes. The length 1 M Y Y Y
provided includes any padding bits
necessary to complete the last byte
of finger pattern skeletal data.
The length (in bytes) of the finger
pattern skeletal data shall be
R-49 7.4.2.1
recorded in two bytes. The length
1 M Y Y Y
provided includes any padding bits
necessary to complete the last byte
of finger pattern skeletal data.
The finger pattern skeletal data for
R-50 7.4.2.2 N/A N/A
a single finger shall be recorded as 3C O-1 Y Y Y
defined in Clauses 6.1 and 6.2.
The length (in bytes) of the
skeleton line neighborhood index
data shall be recorded in two
R-51 7.4.2.3
2 M Y Y Y
bytes. The length provided
includes any padding bits
necessary to complete the last byte
of finger pattern skeletal data.
The skeleton line neighborhood
R-52 7.4.2.4 index data for a single finger shall N/A N/A
3C O-1 Y Y Y
be recorded as defined in Clause
6.3.
10 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
The size of this area shall be kept
as small as possible, augmenting
the data stored in the standard
pattern skeletal data area. The
R-53 7.5 extended data for each finger view 3C O-1 Y Y Y N/A N/A
shall immediately follow the
standard pattern skeletal data for
that finger view and shall begin
with the extended data block
length.
In particular, ridge count data, core
and delta data, zonal quality
information or sweat pore positions
R-54 7.5 3C O-1 Y Y Y N/A N/A
shall not be represented in
proprietary manner to the exclusion
of the publicly defined formats in
this part of ISO/IEC 19794.
All pattern skeletal data records
shall contain the extended data
R-55 7.5.1.1 1 M Y Y Y
block length. This field will signify
the existence of extended data,
and shall be recorded in 2 bytes.
A value of all zeros (0x0000
hexadecimal) will indicate that
there is no extended data and that
R-56 7.5.1.1 2 M Y Y Y
the file will end or continue with the
next finger view. A nonzero value
will indicate the length of all
extended data starting with the
next byte.
The extended data area type code
shall be recorded in two bytes, and
shall distinguish the format of the
R-57 7.5.1.2 extended data area as defined by 1 M Y N N
the Vendor specified by the
CBEFF_BDB_product_owner and
CBEFF_BDB_product_type in the
CBEFF header.
A non-zero value in the first byte
R-58 7.5.1.2 1 M Y Y Y
shall indicate a vendor specified
format, with a code maintained by
the vendor.
The length of the extended data
area, including the extended data
R-59 7.5.1.3 1 M Y Y Y
area type code and length of data
fields, shall be recorded in two
bytes.
If the extended data block length
R-60 7.5.1.3 2 M Y Y Y
(7.5.1.1) for the finger view is zero,
indicating no extended data, this
field shall not be present.
If the extended data block length
R-61 7.5.1.4 (7.5.1.1) for the finger view is zero, 2 M Y Y Y
indicating no extended data, this
field shall not be present.
© ISO/IEC 2014 – All rights reserved 11
---------------------- Page: 14 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
If the extended data area type
code is 0x0001, the extended data
R-62 7.5.2 1 O Y N N
area contains ridge count
information. This format is provided
to contain optional information
Ridge counts shall not include the
R-63 7.5.2 3C O-1 Y N N N/A N/A
ridges represented by either of the
associated minutiae points.
The ridge count data area shall
R-64 7.5.2.1 1 O Y N N
begin with a single byte indicating
the ridge count extraction method.
In 4 Neighbor Ridge Count
Method, For each center minutia
used, ridge count data was
R-65 7.5.2.1 2 O Y N N
extracted to the nearest
neighboring minutia in four
quadrants, and ridge counts for
each center minutia are listed
together.
In 8 Neighbor Ridge Count
Method, For each center minutia
used, ridge count data was
R-66 7.5.2.1 2 O Y N N
extracted to the nearest
neighboring minutia in eight
octants, and ridge counts for each
center minutia are listed together.
all ridge counts for a particular
R-67 7.5.2.1 2 O Y N N
center minutia shall be listed
together;
the center minutia shall be the first
R-68 7.5.2.1 2 O Y N N
minutia references in the three-
byte ridge count data;
if a given quadrant or octant has no
neighboring minutiae in it, a ridge
count field shall be recorded with
both the minutia index and the
R-69 7.5.2.1 2 O Y N N
ridge count fields set to zero (so
that, for each center minutia, there
shall always be four ridge counts
recorded for the quadrant method
and eight ridge counts recorded for
the octant method);
no assumption shall be made
R-70 7.5.2.1 2 O Y N N
regarding the order of the
neighboring minutiae.
The ridge count data shall be
R-71 7.5.2.2 1 O Y N N
represented by a list of threebyte
elements.
no assumption shall be made
R-72 7.5.2.2 2 O Y N N
about the geometric relationships
of the various ridge count items.
If the extended data area type
R-73 7.5.3 2 O Y N N
code is 0x0002, the extended data
area contains core and delta
information.
12 © ISO/IEC 2014 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 19794-8:2011/Amd.1:2014(E)
Sub-format /
Format
Reference
Requirement IUT Supported Test
Type
in Base Level Status
Requirement Summary
Identifier Support Range Result
Applicability
Standard
R N C
The number of core points
R-74 7.5.3.1 represented shall be recorded in 1 O Y N N
the least significant four bits of this
byte. Valid values are from 0 to 15.
The core information type shall be
recorded in the two most significant
bits of the two bytes of the x
coordinate of the core position. The
bits “01” will indicate that the core
R-75 7.5.3.2 3C O-1 Y N N N/A N/A
has angular information while “00”
will indicate that no angular
information is relevant for the core
type. If this field is “00”, then the
angle field shall not be present for
this core.
The X coordinate of the core shall
R-76 7.5.3.3 be recorded in the lower fourteen 1 O Y N N
bits of the first two bytes (fourteen
bits).
The Y coordinate shall be placed in
R-77 7.5.3.3 1 O Y N N
the lower fourteen bits of the
following two bytes.
The coordinates shall be
R-78 7.5.3.3 expressed in pixels at the 3C O-1 Y N N N/A N/A
resolution indicated in the record
header.
The angle of the core shall be
recorded in one byte in units of
1,40625 (360/256) degrees. The
R-79 7.5.3.4 1 O Y N N
core an
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.