ISO/IEC 19794-9:2011/Amd 2:2015

INTERNATIONAL ISO/IEC
STANDARD 19794-9
Second edition
2011-10-01
AMENDMENT 2
2�1�‐��‐�1
Information technology — Biometric
data interchange formats —
Part 9:
Vascular image data
AMENDMENT 2: XML Encoding and
clari�ication of defects
Technologies de l’information — Formats d’échange de données
biométriques —
Partie 9: Données d’images vasculaires
AMENDEMENT 2: Codage XML et précisions concernant les défauts
Reference number
ISO/IEC 1����‐�:2�11/Amd.2:2�1�(E)
©
ISO/IEC 2�1�

---------------------- Page: 1 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)

COPYRIGHT PROTECTED DOCUMENT
� ISO/IEC 2�1�, Published in Switzerland
All rights reserved. Unless otherwise speci�ied, 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 re�uested from either ISO at the address below or ISO�s member body in the country of
the re�uester.
ISO copyright of�ice
Ch. de Blandonnet � � CP ��1
C�‐121� �ernier, �eneva, Switzerland
Tel. ��1 22 ��� �1 11
Fax ��1 22 ��� �� ��
copyright�iso.org
www.iso.org
ii � ISO/IEC 2�1� � All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 19794-9: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-9: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-9:2011/Amd.2:2015(E)
Information Technology — Biometric data interchange
formats — Part 9: Vascular image data
Amendment 2: XML Encoding and clarification of defects
Insert the following text into introduction:
Additionally, this part of the ISO/IEC standard supports both binary and XML encoding, to support a spectrum
of user requirements. With XML, this part will meet the requirements modern IT architectures. With binary
encoding this part will also be able to be used in bandwidth or storage constrained environments. Annex C
specifies the schema that XML encoded vascular image records must conform to, and Annex D provides an

example of a valid XML encoded vascular image record.
Replace the existing text in clause “2– Conformance” with 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 C 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, Level-2 and Level-3 tests shall
use the assertions defined in Table A.2 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.
© ISO/IEC 2015 – All rights reserved 1

---------------------- Page: 4 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Insert the following text in the appropriate alphabetical order of Clause "3-- Normative reference":
- http://www.w3.org/XML/Schema
Add the following row to Table 10 of ISO/IEC 19794-9:2011:
39 (0027) XML-vascular-image {iso(1) registration-authority(1) cbeff(19785) biometric-organization(0)
Hex
jtc1-sc37(257) bdbs(0) XML‐vascular-image(39)}
Replace Table A.1 with the following table. This table, A.1, may extend over multiple pages:
Table A.1 — Requirements of the Base Standard
The quantities in all records and
vascular biometric image elements
R- 1 6.1 (pixel data), if represented as multi- 1 M Y N N/A
byte quantities, are represented in
big-endian format.
The order for transmission shall also
be the most significant byte first and
the least significant byte last. Within
6.1 3C O-1 Y N N/A N/T
R- 2
a byte, the order of transmission
shall be the most significant bit first
and the least significant bit last.
The scan sequence shall be raster
6.2 3C O-1 Y N N/A N/T
R- 3
scan order.
The spatial sampling rate of the
captured image shall be
7.1 3C O-1 Y N N/A N/T
R- 4
represented in terms of pixels per
centimetre.
The image shall have a dynamic
range spanning at least 128 gray
scale levels, allocating at least one
7.2 1 M Y Y N/A
R- 5
byte (8 bits) per intensity value and
providing at least 7 bits of useful
intensity information.
The captured image shall be an
7.5 orthographic projection of the body 3C O-1 Y Y N/A N/T
R- 6
area being imaged.
If lossless compression is used the
image data shall be compressed in
accordance with the JPEG-LS
7.6.2 lossless compression algorithm 3C O-1 Y Y N/A N/T
R- 7
specified in ISO/IEC 14495 or the
JPEG2000 compression algorithm
specified in ISO/IEC 15444.

2 © ISO/IEC 2015 – All rights reserved

Requirement ID
Reference in Base
Standard
Requirement
Summary
Level
Status
Binary
Applicability
XML
IUT Support
Supported Range
Test Result

---------------------- Page: 5 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
If lossy compression is used the
image shall be compressed in
accordance with the JPEG
7.6.3 compression algorithm specified in 3C O-1 Y Y N/A N/T
R- 8
ISO/IEC 10918 or the JPEG2000
compression algorithm specified in
ISO/IEC 15444.
Images captured with more than
three sensing channels shall be
7.6.4 stored in accordance with the 3C O-1 Y Y N/A N/T
R- 9
JPEG2000 compression algorithm
as specified in ISO/IEC 15444.
The location of human body used
7.7 for imaging shall be specified in the 1 M Y Y N/A
R- 10
format.
The direction (left/right) of hand
and/or finger index (thumb, index,
7.7 1 M Y Y N/A
R- 11
middle, ring, and little) shall be
specified.
The format identifier shall be
recorded in four bytes. The format
8.2.1 identifier shall consist of three 1 M Y N N/A
R- 12
characters "VIR" followed by a zero
byte as a NULL string terminator.
The number for the version of that
part of ISO/IEC 19794 used for
constructing the BDIR 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
8.2.2 1 M Y N N/A
R- 13
and second character will represent
the major version number and the
third character will represent the
minor revision number. Upon
approval of a specification, the initial
version number will be “020” –
Version 2 revision 0.
The length (in bytes) of the entire
8.2.3 BDIR shall be recorded in four 1 M Y N
R- 14
bytes.
This count shall be the total length
of the BDIR including the general
8.2.3 2 M Y N
R- 15
record header and one or more
representation records.

© ISO/IEC 2015 – All rights reserved 3

Requirement ID
Reference in Base
Standard
Requirement
Summary
Level
Status
Binary
Applicability
XML
IUT Support
Supported Range
Test Result

---------------------- Page: 6 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
The total number of representation
records contained in the BDIR shall
8.2.4 be recorded in two bytes. A 2 M Y N
R- 17
minimum of one representation is
required.
As this part of ISO/IEC 19794 does
8.2.5 not support certifications this field 1 M Y N
R- 18
shall be 00Hex.
The representation-length field
denotes the length in bytes of the
8.3.2 1 M Y N
R- 19
representation including the
representation header fields.
This four-byte field shall contain the
8.3.2 length in bytes of the vascular 2 M Y N
R- 20
image.
The date and time field within a
representation header shall be
stated in Coordinated Universal
8.3.3 Time (UTC). The capture date and 1 M Y Y
R- 21
time field shall consist of 9 bytes. Its
value shall be encoded in the form
given in ISO/IEC 19794-1.
The capture device technology ID
shall be encoded in one byte. This
field shall indicate the class of
capture device technology used to
8.3.4 acquire the captured biometric 1 M Y N
R- 22
sample. A value of 00Hex indicates
unknown or unspecified technology.
See Table 4 for the list of possible
values.
The capture device vendor identifier
shall identify the biometric
organization that owns the product
that created the BDIR. The capture
device algorithm vendor identifier
shall be encoded in two bytes
1 O Y Y
8.3.5
R- 23
carrying a CBEFF biometric
organization identifier (registered by
IBIA or other approved registration
authority). A value of all zeros shall
indicate that the capture device
vendor is unreported.

4 © ISO/IEC 2015 – All rights reserved

Requirement ID
Reference in Base Standard
Requirement Summary
Level
Status
Y Binary
Applicability
N XML
IUT Support
Supported Range
Test Result

---------------------- Page: 7 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
The capture device type identifier
shall identify the product type that
created the BDIR. It shall be
assigned by the registered product
8.3.6 1 O Y Y
R- 24
owner or other approved registration
authority. A value of all zeros shall
indicate that the capture device type
is unreported.
If the capture device vendor
identifier is 0000Hex, then also the
8.3.6 2 O Y N
R- 25
capture device type identifier shall
be 0000Hex.
This field is followed by the number
8.3.7.1 of 5-byte Quality Blocks reflected by 1 O Y N
R- 26
its value.
A value of zero (0) means that no
attempt was made to assign a
8.3.7.1 2 O Y N
R- 27
quality score. In this case, no
Quality Blocks are present.
Quality score, as defined in ISO/IEC
29794-1, shall be a quantitative
8.3.7.2 expression of the predicted 3C O-1 Y Y N/A N/T
R- 28
verification performance of the
biometric sample.
An entry of 255 shall indicate a
failed attempt to calculate a quality
8.3.7.2 score. This value of Quality Score is 1 O Y Y
R- 29
harmonized with ISO/IEC 19784-1,
where 255 is -1.
Quality Algorithm Vendor ID shall be
registered with IBIA or other
8.3.7.3 3C O-1 Y Y N/A N/T
R- 30
approved registration authority as a
CBEFF biometric organization.
A value of all zeros shall indicate
8.3.7.3 that the value for this field is 1 O Y Y
R- 31
unreported.
Quality Algorithm ID may be
optionally registered with IBIA or
other approved registration authority
as a CBEFF Product Code. Refer
8.3.7.4 to CBEFF product registry 1 O Y Y
R- 32
procedures in ISO/IEC 19785-2.
A value of all zeros shall indicate
that the value for this field is
unreported.


© ISO/IEC 2015 – All rights reserved 5

Requirement ID
Reference in Base
Standard
Requirement
Summary
Level
Status
Binary
Applicability
XML
IUT Support
Supported Range
Test Result

---------------------- Page: 8 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
These two fields specify the
8.3.9 horizontal and vertical image size in 1 M Y Y
R- 33
pixels, in two bytes for each field.
This field represents the number of
bits per pixel in a gray scale image
Ｍ
8.3.10 or the number of bits per color 1 Y Y
R- 34
component per pixel in an RGB
image.
This field is a mandatory field
specifying the position, direction,
8.3.11 and properties of the object. The 1 M Y Y N/A
R- 35
first two bits specify the direction of
organ (toward the left or the right).
The unit is degree normalized to 16-
bit signed integer as (unsigned
8.3.12 1 O Y Y
R- 36
short) round (65536*(angle%360)
/360).
This two-byte field specifies whether
the image is monochrome or color
8.3.13 1 M Y Y
R- 37
and how the image has been
compressed if applicable.
The type of illumination shall be
categorized based on the
wavelength of illumination source;
that is, the wavelength of visible
illumination is in the range of 400
8.3.14 1 O Y Y N/A
R- 38
nm through 750 nm, the wavelength
of NIR is in the range of 750 nm
through 5,000 nm, and the
wavelength of MIR is in the range of
5,000 nm through 25,000 nm.
If the background has been
processed and set to monotone,
then this field shall have the value
IMAGE_BACKGROUND_MONO
8.3.15 1 M Y Y N/A
R- 39
(01 ); otherwise this field shall
Hex
have the value
IMAGE_BACKGROUND_UNDEF
(00 ).
Hex
This field specifies the scan
resolution in the horizontal direction
in ppcm. If the horizontal scan
8.3.16 resolution is not specified, this field 1 M Y Y N/A
R- 40
shall contain the value
H_SCAN_RES_UNDEF= 0
(0000 ).
Hex

6 © ISO/IEC 2015 – All rights reserved

Requirement ID
Reference in Base
Standard
Requirement
Summary
Level
Status
Binary
Applicability
XML
IUT Support
Supported Range
Test Result

---------------------- Page: 9 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
This field specifies the scan
resolution in the vertical direction in
ppcm. If the vertical scan resolution
8.3.17 is not specified, this field shall 1 M Y Y N/A
R- 41
contain the value
V_SCAN_RES_UNDEF= 0 (0000
Hex).
The first byte specifies y distance
and the second byte x distance. For
example, 0304Hex means an
8.3.18 aspect ratio of 3:4. 1 M Y Y N/A
R- 42
If this field is undefined (0000Hex),
the default aspect ratio is assumed
which is 1:1.
The size of this section shall be kept
as small as possible, augmenting
the image data stored in the
8.4.1 standard image data section. 3C O-1 Y Y N/A N/T
R- 43
More than one extended data area
may be present for each vascular
representation.
The extended data for each
vascular representation shall
immediately follow the standard
8.4.1 image data for that vascular 1 M Y Y
R- 44
representation and shall begin with
the Extended Data Block Length
field.
All vascular records shall contain
the extended data block length. This
field will signify the existence of
extended data. A value of all zeros
(0000 ) will indicate that there is
Hex
8.4.2.1 no extended data and that the file 2 M Y Y
R- 45
will end or continue with the next
vascular representation. A nonzero
value will indicate the length of all
extended data starting with the next
byte.


© ISO/IEC 2015 – All rights reserved 7

Requirement ID
Reference in Base
Standard
Requirement
Summary
Level
Status
Binary
Applicability
XML
IUT Support
Supported Range
Test Result

---------------------- Page: 10 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
This field shall have a length of two
bytes. It shall identify the format of
the extended data area when this
area is present. 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
8.4.2.2 1 O Y Y
R- 46
section has a format defined in this
part of ISO/IEC 19794; 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.
The length of the extended data
section shall be recorded in four
bytes. This value is used to skip to
the next extended data type
identification field if the matcher
8.4.2.3 1 O Y Y
R- 47
cannot decode or use this data. If
the Extended Data Block Length for
the finger representation is zero,
indicating no extended data, this
field shall not be present.
If the extended data type
identification code is 0001 , the
Hex
8.4.3 extended data section contains 2 O Y Y
R- 48
segmentation.

This 1-byte field shall contain the
8.4.3.1 number of vascular segments that 2 O Y Y
R- 49
follow.
Each vascular segment shall be
defined by the number of points
8.4.3.2 3C O-1 Y Y N/A N/T
R- 50
used to define the segment and the
coordinates of each point.

8 © ISO/IEC 2015 – All rights reserved

Requirement ID
Reference in Base
Standard
Requirement
Summary
Level
Status
Binary
Applicability
XML
IUT Support
Supported Range
Test Result

---------------------- Page: 11 ----------------------
ISO/IEC 19794-9:2011/Amd.2:2015(E)
Table A.1 (continued) — Requirements of the Base Standard
This field shall specify the number of
points or vertexes used to enclose
the segmented image. For a
vascular segment defined by
rectangle, this byte shall contain a
value of "2" representing the upper
8.4.3.2.1 2 O Y Y
R- 51
left and lower right corners of the
rectangle.
For a vascular segment enclosed by
an n-sided polygon, this byte shall
contain "n" where "n" is between 3
and 99.
The order of the vertices shall be in
their consecutive order around the
perimeter of the poly
...