ISO/IEC 19785-3:2007/Amd 1:2010

Information technology - Common Biometric Exchange Formats Framework - Part 3: Patron format specifications - Amendment 1: Support for Additional Data Elements

Technologies de l'information — Cadre de formats d'échange biométriques communs — Partie 3: Spécifications de format d'usager — Amendement 1: Support pour éléments de données additionnels

General Information

• Status: Withdrawn
• Publication Date: 28-Mar-2010
• Withdrawal Date: 28-Mar-2010
• ICS: 35.040 - Information coding
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: ISO/IEC JTC 1/SC 37 - Biometrics
• Drafting Committee: ISO/IEC JTC 1/SC 37/WG 2 - Biometric technical interfaces
• Current Stage: 9599 - Withdrawal of International Standard
• Start Date: 01-Sep-2015
• Completion Date: 30-Oct-2025

Relations

• Amends: ISO/IEC 19785-3:2007 - Information technology - Common Biometric Exchange Formats Framework - Part 3: Patron format specifications
• Effective Date: 25-Apr-2020
• Revised: ISO/IEC 19785-3:2015 - Information technology - Common Biometric Exchange Formats Framework - Part 3: Patron format specifications
• Effective Date: 17-Sep-2011

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 19785-3
First edition
2007-12-15
AMENDMENT 1
2010-04-01
Information technology — Common
Biometric Exchange Formats
Framework —
Part 3:
Patron format specifications
AMENDMENT 1: Support for Additional Data
Elements
Technologies de l'information — Cadre de formats d'échange
biométriques communs —
Partie 3: Spécifications de format d'usager
AMENDEMENT 1: Support pour éléments de données additionnels

Reference number
ISO/IEC 19785-3:2007/Amd.1:2010(E)
©
ISO/IEC 2010
ISO/IEC 19785-3:2007/Amd.1:2010(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO/IEC 2010
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing 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 [e-mail]
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(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 19785-3:2007 was prepared by Joint Technical Committee ISO/IEC JTC 1,
Information technology, Subcommittee SC 37, Biometrics.

© ISO/IEC 2010 — All rights reserved iii

ISO/IEC 19785-3:2007/Amd.1:2010(E)

Information technology — Common Biometric Exchange
Formats Framework —
Part 3:
Patron format specifications
AMENDMENT 1: Support for Additional Data Elements
Page vii, Introduction, list item g)
Replace the text with the following (where changes to existing text are highlighted with a grey background):
g) CBEFF data elements [see c) above] that support, within the SBH, the unique identifiers assigned by
the Biometric RA for biometric organizations, BDB formats, biometric products, capture devices,
feature extraction algorithms, comparison algorithms, quality algorithms, compression algorithms,
patron formats, and SB formats.
and insert the following new paragraph after the list:
Patron formats can be specified in other standards documents and registered in the CBEFF Registration
Authority (see ISO/IEC 19785-2), for example there is a registered patron format specified in ISO/IEC 19784-1.
For a complete list of registered patron formats consult the CBEFF Registration Authority web site.
Page 2, immediately after 4.1 i) (biometric product owner)
Insert the following new terms, relabelling the existing terms j) to x) as y) to mm) [where z) is followed by aa),
bb), etc.]:
j) capture device
k) capture device identifier
l) capture device owner
m) feature extraction algorithm
n) feature extraction algorithm identifier
o) feature extraction algorithm owner
p) comparison algorithm
q) comparison algorithm identifier
r) comparison algorithm owner
s) quality algorithm
t) quality algorithm identifier
u) quality algorithm owner
© ISO/IEC 2010 — All rights reserved 1

ISO/IEC 19785-3:2007/Amd.1:2010(E)
v) compression algorithm
w) compression algorithm identifier
x) compression algorithm owner
Page 18, 10.4
Change “(0004 Hex)” to “(0005 Hex)”.
Page 32, 12.4
Change “(06 Hex)” to “(0006 Hex)”.
Page 32, 12.9.1
Replace the subclause with the following (where changes to existing text are highlighted with a grey
background):
12.9.1 This patron format supports all the mandatory and optional data elements specified in
ISO/IEC 19785-1 except the following ones: capture device owner and identifier, feature extraction algorithm
owner and identifier, comparison algorithm owner and identifier, quality algorithm owner and identifier, and
compression algorithm owner and identifier. It can support either a simple BIR or a complex BIR structure
where each intermediate node or leaf of the structure is itself a BIR (called a "child BIR") and can be
represented in any patron format.
Page 42, 12.13.2
Change the second cell in the table heading from “Mandatory/optional/absent” to “Mandatory/optional”.
Page 44, 13.9.1
Replace the subclause with the following (where changes to existing text are highlighted with a grey
background):
13.9.1 This patron format is based on W3C XML 1.0. It supports all the mandatory and optional data
elements specified in ISO/IEC 19785-1 except the following ones: capture device owner and identifier, feature
extraction algorithm owner and identifier, comparison algorithm owner and identifier, quality algorithm owner
and identifier, and compression algorithm owner and identifier. It can support either a simple BIR or a complex
BIR structure where each intermediate node or leaf of the structure is itself a BIR (called a "child BIR").
Page 58, 13.21.2
Change the second cell in the table heading from “Mandatory/optional/absent” to “Mandatory/optional”.
2 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
Page 68, after Clause 13
Insert the following two new clauses.
14 Patron format specification: complex patron format (with additional data
elements)
14.1 Patron
ISO/IEC JTC 1/SC 37
14.2 Patron identifier
257 (0101Hex). This has been allocated by the Registration Authority for ISO/IEC 19785-2.
14.3 Patron format name
ISO/IEC JTC 1/SC 37 complex patron format (with additional data elements).
14.4 Patron format identifier
10 (000A Hex). This has been registered in accordance with ISO/IEC 19785-2.
14.5 ASN.1 object identifier for this patron format
{iso registration-authority cbeff(19785) biometric-organization(0) jtc1-sc37(257) patron-
format(1) full-complex(10)}
or, in XML value notation,
1.1.19785.0.257.1.10
14.6 Domain of use
This clause provides a definition of a patron format that may be of general utility to applications that need to
carry one or more BIRs (of either the same or different patron formats) in a single complex BIR structure, with
explicit identification of the patron format(s) being used.
This patron format is identical to that specified in clause 12 except for the addition of ten new data elements
(capture device owner and identifier, feature extraction algorithm owner and identifier, comparison algorithm
owner and identifier, quality algorithm owner and identifier, and compression algorithm owner and identifier)
and a "fieldPresence" field that is one byte longer.
14.7 Version identifier
This patron format specification has a version identifier of 1.
14.8 CBEFF version
This specification conforms to CBEFF version (major 2, minor 0).
14.9 General
14.9.1 This patron format supports all the mandatory and optional data elements specified in
ISO/IEC 19785-1. It can support either a simple BIR or a complex BIR structure where each intermediate
node or leaf of the structure is itself a BIR (called a "child BIR") and can be represented in any patron format.
© ISO/IEC 2010 — All rights reserved 3

ISO/IEC 19785-3:2007/Amd.1:2010(E)
14.9.2 The patron format of each child BIR is explicitly identified in its parent by a pair: patron format
owner / patron format type, and can be either this patron format (in which case the child BIR may itself have
children), or a different patron format (in which case the child BIR is considered a leaf of this patron format
although it may be a complex BIR in its own regard).
14.9.3 Most fields in this patron format are optional. The presence of each optional field is encoded as a
single bit of a 32-bit field ("fieldPresence") at the beginning of the format, which has one bit for each optional
field defined in the patron format. The bit value '1' in a given position of that field means that the
corresponding field is present in the BIR instance.
14.9.4 All character strings and octet strings are preceded by a length prefix, which can be one, two, or four
octets long, as specified for each field.
14.9.5 All integer values, including lengths, are encoded in big-endian order.
14.9.6 Dates and date intervals are encoded as character strings in a way conforming to ISO 8601.
14.9.7 An instance of a BIR or child BIR contains either a BDB or one or more BIR children, but never
contains both.
14.10 Specification
An instance of a BIR shall contain the fields specified below, in exactly the same order and with no gaps
between the fields.
b
CBEFF data element name Field name Length and
Abstract values and Encodings
a
optionality
The following fields shall occur
at most once
CBEFF_patron_header_version patronHeaderVersion 1, mandatory 1
CBEFF_version cbeffVersion 1, mandatory Major '2' and Minor '0': X'20' (32)
not a standard CBEFF data fieldPresence 4, mandatory A 32-bit field containing one bit for each
element optional field in the patron format. The bit

value '1' means that the corresponding
field is present in the BIR instance.
Bit position (1=most significant, 32=least
significant) and corresponding optional
field:
1 bdbFormat Owner & Type
2 bdbEncryption
3 bdbBiometricType
4 bdbBiometricSubtype
5 bdbChallengeResponse
6 bdbCreationDate
7 bdbIndex
8 bdbProcessedLevel
9 bdbProduct Owner & Type
10 bdbCaptureDevice Owner & Type
11 bdbFeatureExtAlg Owner & Type
12 bdbComparisonAlg Owner & Type
13 bdbQualityAlg Owner & Type
14 bdbCompressionAlg Owner & Type
15 bdbPurpose
16 bdbQuality
17 bdbValidityPeriod
4 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
b
CBEFF data element name Field name Length and
Abstract values and Encodings
a
optionality
18 birCreationDate
19 birCreator
20 birIndex
21 birPayload
22 birValidityPeriod
23 sbFormat Owner & Type
24 bdb
25 sb
26.32 not used (shall be '0')
CBEFF_BDB_format_owner bdbFormatOwner 2, mandatory if 0.65535
a BDB is
present,
optional if a
BDB is not
present.
CBEFF_BDB_format_type bdbFormatType 2, mandatory if 0.65535
a BDB is
present,
optional if a
BDB is not
present.
CBEFF_BDB_encryption_ bdbEncryption 1; mandatory if NO ENCRYPTION: 0
options a BDB is ENCRYPTION: 1
present, other-
wise required to
be absent.
CBEFF_BIR_integrity_options birIntegrity 1, mandatory NO INTEGRITY: 0
INTEGRITY: 1
CBEFF_BDB_biometric_type bdbBiometricType 3 This encoding is a 3 octet bitmap. NO VALUE
AVAILABLE is encoded as all 0 bits. If
MULTIPLE BIOMETRIC TYPES is set, other
bits may also be set to enumerate the types
contained in the BDB.
NO VALUE AVAILABLE:  X'00 00 00'
MULTIPLE BIOMETRIC TYPES: X'00 00 01'
FACE:   X'00 00 02'
VOICE:   X'00 00 04'
FINGER:   X'00 00 08'
IRIS:   X'00 00 10'
RETINA:   X'00 00 20'
HAND GEOMETRY:  X'00 00 40'
SIGNATURE OR SIGN:  X'00 00 80'
KEYSTROKE:   X'00 01 00'
LIP MOVEMENT:  X'00 02 00'
GAIT:   X'00 10 00'
VEIN:   X'00 20 00'
DNA:   X'00 40 00'
EAR:   X'00 80 00'
FOOT:   X'01 00 00'
SCENT:   X'02 00 00'
CBEFF_BDB_biometric_subtype bdbBiometricSubtype 1 This encoding is a 1 octet bitmap.
Combinations of abstract values are
permitted (by ORing the encodings for
those values) when the abstract value
encoded in CBEFF_BDB_biometric_type
represents a biometric technology that
© ISO/IEC 2010 — All rights reserved 5

ISO/IEC 19785-3:2007/Amd.1:2010(E)
b
CBEFF data element name Field name Length and
Abstract values and Encodings
a
optionality
can create a BDB where multiple
subtypes are supported.
NO VALUE AVAILABLE: b’0000 0000’
LEFT:   b’0000 0001’
RIGHT:   b’0000 0010’
LEFT THUMB:   b’0000 0101’
LEFT POINTER FINGER:  b’0000 1001’
LEFT MIDDLE FINGER:  b’0001 0001’
LEFT RING FINGER:  b’0010 0001’
LEFT LITTLE FINGER:  b’0100 0001’
RIGHT THUMB:   b’0000 0110’
RIGHT POINTER FINGER:  b’0000 1010’
RIGHT MIDDLE FINGER:  b’0001 0010’
RIGHT RING FINGER:  b’0010 0010’
RIGHT LITTLE FINGER:  b’0100 0010’
LEFT PALM:   b’1000 0101’
LEFT BACK OF HAND:  b’1000 1001’
LEFT WRIST:   b’1001 0001’
RIGHT PALM:   b’1000 0110’
RIGHT BACK OF HAND:  b’1000 1010’
RIGHT WRIST:   b’1001 0010’
CBEFF_BDB_challenge_ bdbChallengeResponse 2 + 0.65535 Variable-length octet string, preceded by
response a 16-bit integer field containing the length
(octets).
CBEFF_BDB_creation_date bdbCreationDate 1 + 8.15 Variable-length ASCII character string,
preceded by an 8-bit integer field
containing the length (characters). The
string shall represent a date (or date and
c
a time of the day) .
CBEFF_BDB_index bdbIndex 2 + 0.65535 Variable-length octet string, preceded by
a 16-bit integer field containing the length
(octets).
Shall not appear in any BIR in which
numChildren is not x'00'.
CBEFF_BDB_processed_level bdbProcessedLevel 1 RAW: 1
INTERMEDIATE: 2
PROCESSED: 3
CBEFF_BDB_product_owner bdbProductOwner 2 1.65535
CBEFF_BDB_product_type bdbProductType 2 1.65535
CBEFF_BDB_capture_device_ bdbCaptureDeviceOwner 2 1.65535
owner
CBEFF_BDB_capture_device_ bdbCaptureDeviceType 2 1.65535
type
CBEFF_BDB_feature_ bdbFeatureExtAlgOwner 2 1.65535
extraction_algorithm_owner
CBEFF_BDB_feature_ bdbFeatureExtAlgType 2 1.65535
extraction_algorithm_type
CBEFF_BDB_comparison_ bdbComparisonAlgOwner 2 1.65535
algorithm_owner
CBEFF_BDB_comparison_ bdbComparisonAlgType 2 1.65535
algorithm_type
CBEFF_BDB_quality_algorithmbdbQualityAlgOwner 2 1.65535
_owner
6 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
b
CBEFF data element name Field name Length and
Abstract values and Encodings
a
optionality
CBEFF_BDB_quality_algorithmbdbQualityAlgType 2 1.65535
_type
CBEFF_BDB_compression_ bdbCompressionAlgOwner2 1.65535
algorithm_owner
CBEFF_BDB_compression_ bdbCompressionAlgType 2 1.65535
algorithm_type
CBEFF_BDB_purpose bdbPurpose 1 VERIFY: 1
IDENTIFY: 2
ENROLL: 3
ENROLL FOR
VERIFICATION ONLY: 4
ENROLL FOR
IDENTIFICATION ONLY: 5
AUDIT: 6
CBEFF_BDB_quality bdbQuality 1 QUALITY NOT SUPPORTED
BY BDB CREATOR: 255
QUALITY SUPPORTED BY
BDB CREATOR BUT
NOT SET: 254
INTEGER VALUE: 0 – 100
CBEFF_BDB_validity_period bdbValidityPeriod 1 + 17.31 Variable-length ASCII character string,
preceded by an 8-bit integer field
containing the length (characters). The
string shall represent an interval of two
d
dates (or date and time of the day) .
CBEFF_BIR_creation_date birCreationDate 1 + 8.15 Variable-length ASCII character string,
preceded by an 8-bit integer field
containing the length (characters). The
string shall represent a date (or date and
c
a time of the day) .
CBEFF_BIR_creator birCreator 2 + 0.65535 Variable-length ISO/IEC 10646 character
string, encoded in UTF-8, and preceded
by a 16-bit integer field containing the
length of the UTF-8 encoding (octets).
CBEFF_BIR_index birIndex 2 + 0.65535 Variable-length octet string, preceded by
a 16-bit integer field containing the length
(octets).
Shall not inherit its value from any other
level BIR.
CBEFF_BIR_payload birPayload 2 + 0.65535 Variable-length octet string, preceded by
a 16-bit integer field containing the length
(octets).
Shall not inherit its value from any other
level BIR.
CBEFF_BIR_validity_period birValidityPeriod 1 + 17.31 Variable-length ASCII character string,
preceded by an 8-bit integer field
containing the length (characters). The
string shall represent an interval of two
d
dates (or date and time of the day) .
CBEFF_SB_format_owner sbFormatOwner 2 1.65535
CBEFF_SB_format_type sbFormatType 2 1.65535
© ISO/IEC 2010 — All rights reserved 7

ISO/IEC 19785-3:2007/Amd.1:2010(E)
b
CBEFF data element name Field name Length and
Abstract values and Encodings
a
optionality
BDB bdb 4 + Variable-length octet string, preceded by
0.4294967295 a 32-bit integer field containing the length
(octets).
If this field is present in a BIR instance
(as indicated in bit 24 of the field
fieldPresence), then no child BIRs shall
be included (numChildren shall have the
value 0). Otherwise, at least one child
BIR shall be included (numChildren shall
have a value greater than 0).
NOTE - The content and encoding of the
BDB are not specified by CBEFF nor by
this patron format specification.
CBEFF_subheader_count numChildren 1, mandatory 0.255

The following 3 fields shall
occur as a group as many
times as specified in the field
numChildren (0.255)
CBEFF_BIR_patron_format_ childBirPatronFormatOwner 2, mandatory if 1.65535
owner no BDB is
present, other-
wise required to
be absent.
CBEFF_BIR_patron_format_ childBirPatronFormatType 2, mandatory if 1.65535
type no BDB is
present, other-
wise required to
be absent.
not a standard CBEFF data childBir 4 + Variable-length octet string, preceded by
element 0.4294967295, a 32-bit integer field containing the length
e
mandatory if no
(octets) .
BDB is present,
otherwise
required to be
absent.
The following field shall occur
at most once
SB sb 4 + Variable-length octet string, preceded by
0.4294967295 a 32-bit integer field containing the length
(octets).
a)
The date shall be represented in the ISO 8601 basic format YYYYMMDDTHHMMSS, where the last 2, the last 4, or the last 7
characters may be omitted.
Examples: 20050103, 20050106T11, 20050106T1230, and 20050106T145504.
b)
Each date shall be represented in the ISO 8601 basic format YYYYMMDDTHHMMSS, where the last 2, the last 4, or the last 7
characters may be omitted. The two dates shall be separated by a SOLIDUS ("/") character, and shall have the same number of digits.
Examples: 20050103/20060103, 20050106T11/20050306T11, and 20050106T113300/20050306T113259.
c)
A BIR consists of either: 1) an SBH, BDB, optional SB, and numChildren value of zero, or 2) an SBH, no BDB, and numChildren

value greater than zero.
8 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
14.11 Illustrative examples
Table 14.1 — "Simple" BIR (one BDB)
Field Name Length Abstract Value Encoding
patronHeaderVersion 1 1 x'01'
cbeffVersion 1 Major 2, Minor 0 x'20'
fieldPresence 3 bdbFormatOwner and Type x'E0 20 00 20'
bdbEncryption
bdbBiometricType
bdbQuality
bdb
bdbFormatOwner 2 ISO/IEC JTC 1/SC 37 257, x'01 01'
bdbFormatType 2 Face image x'00 08'
bdbEncryption 1 NO ENCRYPTION x'00'
birIntegrity 1 NO INTEGRITY x'00'
bdbBiometricType 3 FACE-IMAGE x'40 00 00'
bdbQuality 1 75/100 x'4B'
Bdb 4 + 4096 octet string x'00 00 10 00' + 4096 octets
numChildren 1 zero x'00'
Table 14.2 — Complex BIR fields and abstract values corresponding to Figure 2 in ISO/IEC 19785-1
1. patronHeaderVersion = 1  (beginning of the root header BIR)
2. cbeffVersion = 2:0
3. fieldPresence = sbFormatOwner/Type
4. birIntegrity = INTEGRITY  (integrity is applied to the entire complex BIR via the
SB on line 90)
5. sbFormatOwner = a security vendor
6. sbFormatType = that vendor's security block format  (see the final SB on line 90)
7. numChildren = 2
8. childBirPatronFormatOwner = SC 37
9. childBirPatronFormatType = 8 (this format)
10.   ► (denotes the beginning of the next BIR)
11.   patronHeaderVersion = 1
12.   cbeffVersion = 2:0
13.   fieldPresence = bdbBiometricType
14.   birIntegrity = NO INTEGRITY
15.   bdbBiometricType = FINGER (the next 3 BIRs inherit this value)
16.   numChildren = 3
17.   childBirPatronFormatOwner = SC 37
18.   childBirPatronFormatType = 8 (this format)
19.     ►
20.     patronHeaderVersion = 1
21.     cbeffVersion = 2:0
22.     fieldPresence = bdbFormatOwner/Type; bdbEncryption; bdbBiometricSubtype; bdb
23.     bdbFormatOwner = SC 37
© ISO/IEC 2010 — All rights reserved 9

ISO/IEC 19785-3:2007/Amd.1:2010(E)
24.     bdbFormatType = a standardized BDB format
25.     bdbEncryption = NO ENCRYPTION
26.     birIntegrity = NO INTEGRITY
27.     bdbBiometricSubtype = LEFT POINTER FINGER
28.     bdb
29.     numChildren=0
30.     ►
31.     patronHeaderVersion = 1
32.     cbeffVersion = 2:0
33.     fieldPresence = bdbFormatOwner/Type; bdbEncryption; bdbBiometricSubtype; bdb
34.     bdbFormatOwner = vendor ABC
35.     bdbFormatType = non standard BDB format A
36.     bdbEncryption = NO ENCRYPTION
37.     birIntegrity = NO INTEGRITY
38.     bdbBiometricSubtype = LEFT MIDDLE FINGER
39.     bdb
40.     numChildren=0
41.     ►
42.     patronHeaderVersion = 1
43.     cbeffVersion = 2:0
44.     fieldPresence = bdbFormatOwner/Type; bdbEncryption; bdbBiometricSubtype; bdb
45.     bdbFormatOwner = vendor XYZ
46.     bdbFormatType = non standard BDB format B
47.     bdbEncryption = NO ENCRYPTION
48.     birIntegrity = NO INTEGRITY
49.     bdbBiometricSubtype = LEFT RING FINGER
50.     bdb
51.     numChildren=0
52.   ►
53.   patronHeaderVersion = 1
54.   cbeffVersion = 2:0
55.   fieldPresence = bdbBiometricType
56.   birIntegrity = NO INTEGRITY
57.   bdbBiometricType = IRIS   (the next 2 BIRs inherit this type)
58.   numChildren = 2
59.   childBirPatronFormatOwner = SC 37
60.   childBirPatronFormatType = 8 (this format)
61.     ►
62.     patronHeaderVersion = 1
63.     cbeffVersion = 2:0
64.     fieldPresence = bdbFormatOwner/Type; bdbEncryption; bdbBiometricSubtype;
sbFormatOwner/Type; bdb; sb
65.     bdbFormatOwner = SC 37
66.     bdbFormatType = an iris format
67.     bdbEncryption = ENCRYPTION
68.     birIntegrity = NO INTEGRITY
69.     bdbBiometricSubtype = LEFT
70.     sbFormatOwner = an encryption vendor
71.     sbFormatType = a security block format (see SB on line 74)
72.     bdb
73.     numChildren=0
74.     sb     (see SB format identifier on lines 70-71)
75.     ►
76.     patronHeaderVersion = 1
77.     cbeffVersion = 2:0
78.     fieldPresence = bdbFormatOwner/Type; bdbEncryption; bdbBiometricSubtype;
sbFormatOwner/Type;    bdb; sb
10 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
79.     bdbFormatOwner = vendor PQR
80.     bdbFormatType = vendor's format C
81.     bdbEncryption = ENCRYPTION
82.     birIntegrity = NO INTEGRITY
83.     bdbBiometricSubtype = RIGHT
84.     sbFormatOwner = an encryption vendor
85.     sbFormatType = a security block format (see SB on line 88)
86.     bdb
87.     numChildren=0
88.     sb     (see SB format identifier on lines 84-85)
89. ►
90. sb     (see SB format identifier in root header on line 6)

Table 14.3 — BIR wrapped in an enveloping BIR
Field Name Length Abstract Value Encoding
patronHeaderVersion 1 1 x'01'
cbeffVersion 1 Major 2, Minor 0 x'20'
fieldPresence 4 all optional fields absent in the enveloping BIR x'00 00 00 00'
birIntegrity 1 NO INTEGRITY x'00'
numChildren 1 one child (the enveloped BIR) x'01'
childBirPatronFormatOwner) 2 patron format owner of the enveloped BIR variable
childBirPatronFormatType 2 patron format type of the enveloped BIR variable
childBir (length of the child BIR) 4 length of the enveloped BIR variable
childBir (octets of the child BIR variable octets of the enveloped BIR variable

Table 14.3 shows how the Complex patron format specified in this clause can be used as a simple envelope
around a BIR of an arbitrary patron format in order to provide identification of its format and specify its length.
When using the Complex patron format in this way, the portion of the enveloping BIR preceding the enveloped
BIR can be thought of as a fixed-length prefix to the enveloped BIR. Since all the optional fields of the
enveloping BIR are absent, the length of the prefix is only 16 octets, given by:
a) 8 octets with the fixed values x'01 20 00 00 00 00 00 01'; plus
b) 4 octets containing the patron format owner and type of the enveloped BIR; plus
c) 4 octets containing the length of the enveloped BIR.
© ISO/IEC 2010 — All rights reserved 11

ISO/IEC 19785-3:2007/Amd.1:2010(E)
14.12 ASN.1 definition (provided for illustrative purposes only)
The following ASN.1 specification provides an abstract description of the patron format, and may be useful to
some readers of this part of ISO/IEC 19785. It is not intended to provide an alternative specification of the
encodings of this patron format.

CBEFF-COMPLEX-PATRON-FORMAT
{iso standard 19785 modules(0) complex-BIR(10)}
DEFINITIONS
AUTOMATIC TAGS ::=
BEGIN
BIR ::= SEQUENCE {
patronHeaderVersion INTEGER(0.255),
cbeffVersion  INTEGER(0.255),
fieldPresence SEQUENCE {
bdbFormat  BOOLEAN,
bdbEncryption  BOOLEAN,
bdbBiometricType  BOOLEAN,
bdbBiometricSubtype BOOLEAN,
bdbChallengeResponse BOOLEAN,
bdbCreationDate  BOOLEAN,
bdbIndex  BOOLEAN,
bdbProcessedLevel  BOOLEAN,
bdbProduct  BOOLEAN,
bdbCaptureDevice BOOLEAN,
bdbFeatureExtAlg BOOLEAN,
bdbComparisonAlg BOOLEAN,
bdbQualityAlg BOOLEAN,
bdbCompressionAlg BOOLEAN,
bdbPurpose  BOOLEAN,
bdbQuality  BOOLEAN,
bdbValidityPeriod  BOOLEAN,
birCreationDate  BOOLEAN,
birCreator  BOOLEAN,
birIndex  BOOLEAN,
birValidityPeriod  BOOLEAN,
sbFormat  BOOLEAN,
bdb   BOOLEAN,
children  BOOLEAN,
sb   BOOLEAN
},
bdbFormat  SEQUENCE {
bdbFormatOwner INTEGER(0.65535),
bdbFormatType INTEGER(0.65535)
} OPTIONAL,
bdbEncryption INTEGER(0.255) OPTIONAL,
birIntegrity INTEGER(0.255),
bdbBiometricType INTEGER(0.16777215) OPTIONAL,
bdbBiometricSubtype INTEGER(0.255) OPTIONAL,
bdbChallengeResponse OCTET STRING (SIZE(0.65535)) OPTIONAL,
bdbCreationDate OCTET STRING (SIZE(8.15)) OPTIONAL,
bdbIndex  OCTET STRING (SIZE(0.65535)) OPTIONAL,
bdbProcessedLevel INTEGER(0.255) OPTIONAL,
bdbProduct  SEQUENCE {
bdbProductOwner INTEGER(0.65535),
bdbProductType INTEGER(0.65535)
} OPTIONAL,
bdbCaptureDevice SEQUENCE {
bdbCaptureDeviceOwner INTEGER(0.65535),
bdbCaptureDeviceType INTEGER(0.65535)
} OPTIONAL,
bdbFeatureExtAlg SEQUENCE {
bdbFeatureExtAlgOwner INTEGER(0.65535),
bdbFeatureExtAlgType INTEGER(0.65535)
} OPTIONAL,
bdbComparisonAlg SEQUENCE {
bdbComparisonAlgOwner INTEGER(0.65535),
bdbComparisonAlgType INTEGER(0.65535)
12 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
} OPTIONAL,
bdbQualityAlg SEQUENCE {
bdbQualityAlgOwner INTEGER(0.65535),
bdbQualityAlgType INTEGER(0.65535)
} OPTIONAL,
bdbCompressionAlg SEQUENCE {
bdbCompressionAlgOwner INTEGER(0.65535),
bdbCompressionAlgType INTEGER(0.65535)
} OPTIONAL,
bdbPurpose  INTEGER(0.255) OPTIONAL,
bdbQuality  INTEGER(0.255) OPTIONAL,
bdbValidityPeriod OCTET STRING (SIZE(15.31)) OPTIONAL,
birCreationDate OCTET STRING (SIZE(8.15)) OPTIONAL,
birCreator  OCTET STRING (SIZE(0.65535)) OPTIONAL,
birIndex  OCTET STRING (SIZE(0.65535)) OPTIONAL,
birPayload  OCTET STRING (SIZE(0.65535)) OPTIONAL,
birValidityPeriod OCTET STRING (SIZE(15.31)) OPTIONAL,
sbFormat  SEQUENCE {
sbFormatOwner INTEGER(0.65535),
sbFormatType INTEGER(0.65535)
} OPTIONAL,
bdb  OCTET STRING (SIZE(0.4294967295)) OPTIONAL,
children  SEQUENCE (SIZE(0.255)) OF
child  SEQUENCE {
childBirPatronFormat SEQUENCE {
childBirPatronFormatOwner INTEGER(0.65535),
childBirPatronFormatType INTEGER(0.65535)
},
childBir OCTET STRING (SIZE(0.4294967295))
}
},
sb OCTET STRING (SIZE(0.4294967295)) OPTIONAL
}
14.13 Patron format conformance statement
14.13.1 Identifying information
Required Information Patron format reference
Patron name See 14.1
Patron identifier See 14.2
Patron format name See 14.3
Patron format identifier See 14.4
Patron format ASN.1 object identifier See 14.5
Domain of use description See 14.6
Patron format version See 14.7
CBEFF version See 14.8
© ISO/IEC 2010 — All rights reserved 13

ISO/IEC 19785-3:2007/Amd.1:2010(E)
14.13.2 CBEFF-defined data elements and abstract values
CBEFF data element name Mandatory/ Patron format field name Abstract Encodings
optional values specified?
specified?
CBEFF_BDB_format_owner Mandatory bdbFormatOwner Yes Yes
if a BDB is
present
CBEFF_BDB_format_type Mandatory bdbFormatType Yes Yes
if a BDB is
present
CBEFF_BDB_encryption_options Mandatory bdbEncryption Yes Yes
if a BDB is
present
CBEFF_BIR_integrity_options Mandatory birIntegrity Yes Yes
CBEFF_BDB_subheader_count Mandatory numChildren Yes Yes
CBEFF_BDB_biometric_type Optional bdbBiometricType Yes Yes
CBEFF_BDB_biometric_subtype Optional bdbBiometricSubtype Yes Yes
CBEFF_BDB_challenge_response Optional bdbChallengeResponse Yes Yes
CBEFF_BDB_creation_date Optional bdbCreationDate Yes Yes
CBEFF_BDB_index Optional bdbIndex Yes Yes
CBEFF_BDB_product_owner Optional bdbProductOwner Yes Yes
CBEFF_BDB_product_type Optional bdbProductType Yes Yes
CBEFF_BDB_capture_device_owner Optional bdbCaptureDeviceOwner Yes Yes
CBEFF_BDB_capture_device_type Optional bdbCaptureDeviceType Yes Yes
CBEFF_BDB_feature_extraction_algorithm_owner Optional bdbFeatureExtAlgOwner Yes Yes
CBEFF_BDB_feature_extraction_algorithm_type Optional bdbFeatureExtAlgType Yes Yes
CBEFF_BDB_comparison_algorithm_owner Optional bdbComparisonAlgOwner Yes Yes
CBEFF_BDB_comparison_algorithm_type Optional bdbComparisonAlgType Yes Yes
CBEFF_BDB_quality_algorithm_owner Optional bdbQualityAlgOwner Yes Yes
CBEFF_BDB_quality_algorithm_type Optional bdbQualityAlgType Yes Yes
CBEFF_BDB_compression_algorithm_owner Optional bdbCompressionAlgOwner Yes Yes
CBEFF_BDB_compression_algorithm_type Optional bdbCompressionAlgType Yes Yes
CBEFF_BDB_processed_level Optional bdbProcessedLevel Yes Yes
CBEFF_BDB_purpose Optional bdbPurpose Yes Yes
CBEFF_BDB_quality Optional bdbQuality Yes Yes
CBEFF_BDB_validity_period Optional bdbValidityPeriod Yes Yes
CBEFF_BIR_creation_date Optional birCreationDate Yes Yes
CBEFF_BIR_creator Optional birCreator Yes Yes
CBEFF_BIR_index Optional birIndex Yes Yes
CBEFF_BIR_patron_format_owner Mandatory childBirPatronFormatOwnerYes Yes
if no BDB is
present
CBEFF_BIR_patron_format_type Mandatory childBirPatronFormatType Yes Yes
if no BDB is
present
14 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
CBEFF data element name Mandatory/ Patron format field name Abstract Encodings
optional values specified?
specified?
CBEFF_BIR_payload Optional birPayload Yes Yes
CBEFF_SB_format_owner Optional sbFormatOwner Yes Yes
CBEFF_SB_format_type Optional sbFormatType Yes Yes
CBEFF_BIR_validity_period Optional birValidityPeriod Yes Yes
patron_header_version Mandatory patronHeaderVersion Yes Yes
CBEFF_version Mandatory cbeffVersion Yes Yes
BDB Optional bdb Yes Yes
SB Optional sb Yes Yes
14.13.3 Patron-defined data elements and abstract values
Patron format Mandatory/optional Patron format Abstract values Encodings
data element field name specified? specified?
name
fieldPresence Mandatory fieldPresence Yes Yes
childBir Mandatory if no BDB childBir Yes Yes
is present
15 Patron format specification: XML patron format (with additional data elements)
15.1 Patron
ISO/IEC JTC 1/SC 37
15.2 Patron identifier
257 (0101Hex). This has been allocated by the Registration Authority for ISO/IEC 19785-2.
15.3 Patron format name
ISO/IEC JTC 1/SC 37 XML patron format.
15.4 Patron format identifier
11 (000B Hex). This has been registered in accordance with ISO/IEC 19785-2.
15.5 ASN.1 object identifier for this patron format
{iso registration-authority cbeff(19785) biometric-organization(0) jtc1-sc37(257) patron-
format(1) xml-full(11)}
or, in XML value notation,
1.1.19785.0.257.1.11
© ISO/IEC 2010 — All rights reserved 15

ISO/IEC 19785-3:2007/Amd.1:2010(E)
15.6 Domain of use
This clause specifies a patron format based on XML that may be of general utility to applications that need to
carry one or more BIRs in a simple or complex BIR structure and benefit from the use of XML over a binary
format.
This patron format is identical to that specified in clause 13 except for the addition of ten new data elements
(capture device owner and identifier, feature extraction algorithm owner and identifier, comparison algorithm
owner and identifier, quality algorithm owner and identifier, and compression algorithm owner and identifier).
15.7 Version identifier
This patron format specification has a version identifier of (major 0, minor 0).
15.8 CBEFF version
This specification conforms to CBEFF version (major 2, minor 0).
15.9 General
15.9.1 This patron format is based on W3C XML 1.0. It supports all the mandatory and optional data
elements specified in ISO/IEC 19785-1. It can support either a simple BIR or a complex BIR structure where
each intermediate node or leaf of the structure is itself a BIR (called a "child BIR").
15.9.2 Most fields in this patron format are optional. Some mandatory and optional fields are represented by
XML elements, others are represented by attributes of XML elements. The presence of an optional field in a
BIR is signalled by simply including the corresponding element or attribute, and its absence is signalled by
simply omitting the corresponding element or attribute.
15.9.3 Special encodings are specified for integers (see 15.17), octet strings (see 15.18), and date and
time-of-the-day abstract values (see 15.19).
15.9.4 An instance of a BIR or child BIR contains either a BDB or one or more BIR children, but never
contains both.
15.9.5 An extension mechanism is specified, which enables the inclusion of application-specific data (not
standardized) within a BIR or child BIR (see 15.11.1.6).
15.10 Specification
15.10.1 In the rest of this clause, the terms "element" and "attribute" are used with the meaning of "XML
element" and "XML attribute", respectively.
15.10.2 The namespace with the name "urn:oid:1.1.19785.0.257.1.7.0" is called the patron format namespace
of this patron format. This namespace name corresponds to the following ASN.1 object identifier:
{iso registration-authority cbeff(19785) biometric-organization(0) jtc1-sc37(257) patron-
format(1) xml(7) namespace(0)}
15.10.3 All elements defined in this patron format have the patron format namespace name. All attribute
names are unqualified.
15.10.4 An instance of a BIR shall be represented as a element (see 15.11).
15.10.5 The element may be the root of an XML document, but this is not required.
16 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
15.10.6 The portion of the XML document consisting of the element and its whole content shall be
valid according to the XML schema provided in 15.22.
NOTE 1 – Validity according to that XML schema does not imply that the element satisfies all the requirements in
the normative text of this specification, as there are some requirements that cannot be (or are not) formally expressed in
the XML schema.
NOTE 2 – When the element is the root of an XML document, the UTF-8 character encoding is recommended for
the XML document, because it will usually produce a smaller encoding.
15.10.7 The abstract value NO VALUE AVAILABLE, for any CBEFF data element that supports this abstract
value, shall be encoded as the omission of the corresponding element or attribute both in the element
and in all of its ancestor elements.
NOTE – The inheritance mechanism specified in 15.14.2.1, 15.15.2.1 and 15.16.2.1 causes a data element of a BIR to
inherit an abstract value (different from NO VALUE AVAILABLE) from its closest ancestor element that contains that
element or attribute when the element in question does not contain it. If any element in a hierarchy of
elements specifies an abstract value for a given data element, that abstract value can be overridden by a different
abstract value in any of its descendant elements, but the overriding abstract value can never be NO VALUE
AVAILABLE.
15.11 Element
15.11.1 Syntax
15.11.1.1 This element shall have no attributes, and shall have a content consisting of the following (in
order):
a) an optional element (see 15.12);
b) an optional element (see 15.13);
c) zero or more application-specific elements;
d) a mandatory element (see 15.14);
e) an optional element (see 15.15);
f) an optional element (see 15.16);
g) zero or more elements (see 15.11);
h) an optional element – the content of this element shall be a valid representation of an octet string
(see 15.18);
i) an optional element – the content of this element shall be a valid representation of an octet string.
15.11.1.2 The element shall not be present if one or more child elements are present, and
shall be present if no child elements are present.
15.11.1.3 The element shall be absent unless its presence is required by 15.14.2.2 or permitted by
15.15.2.3.
15.11.1.4 If the element is present, then the element shall also be present.
15.11.1.5 If the element is present, then the element shall also be present.
15.11.1.6 The number of application-specific elements and their name, namespace name, attributes, and
content are not defined in this patron format specification. However, the namespace name of those elements
shall be different from the patron format namespace name (see 15.10.2).
© ISO/IEC 2010 — All rights reserved 17

ISO/IEC 19785-3:2007/Amd.1:2010(E)
15.11.2 Semantics
15.11.2.1 This element is either a complex or a simple BIR, depending on which child elements are
present. If a child element is present, this element is a simple BIR. If one or more child
elements are present, this element is a complex BIR.
15.11.2.2 The elements , , , , and
and their content form the standard biometric header of the BIR.
15.11.2.3 The element (if present) carries the major and minor version number of this patron
format.
15.11.2.4 The element (if present) carries the major and minor version number of the
CBEFF standard.
15.11.2.5 Each element is a whole BIR (of the same patron format) that is a child BIR of the BIR.
15.11.2.6 The element (if present) carries the biometric data block (BDB) of the BIR.
NOTE – A element and a element cannot coexist as children of the same element (see 15.11.1.2).
15.11.2.7 The element (if present) carries the security block (SB) of the BIR.
NOTE – A element can coexist with either a element or a element that is a child of the same
element.
15.11.2.8 The element carries information about both the BIR and (possibly) about its
descendant BIRs (if the element has one or more child elements), as specified in 15.14.2.1.
15.11.2.9 The element (if present) carries information about either the BDB of the BIR (if the
element has a child element) or about the BDBs of the descendant BIRs that have a child
element (if the element has one or more child elements), as specified in 15.15.2.1.
15.11.2.10 The element (if present) carries information about either the SB of the BIR (if the
element has a child element) or about the SBs of the descendant BIRs that have a child
element (if the element has one or more child elements but no child element), as
specified in 15.16.2.1.
15.12 Element
15.12.1 Syntax
This element shall have the following attributes:
a) major (required) – the value of this attribute shall be a valid representation of an integer in the range 0 to
15 (see 15.17);
b) minor (required) – the value of this attribute shall be a valid representation of an integer in the range 0 to
15.
15.12.2 Semantics
15.12.2.1 This element represents the data element CBEFF_patron_header_version, and carries the
(major and minor) version number of the patron format. The number assigned to this version of the patron
format is major 0, minor 0.
15.12.2.2 The major attribute represents the major version number (0 in this version).
18 © ISO/IEC 2010 — All rights reserved

ISO/IEC 19785-3:2007/Amd.1:2010(E)
15.12.2.3 The minor attribute represents the minor version number (0 in this version).
15.12.2.4 If this element is not present, the attribute values major="0" minor="0" are implied.
15.12.2.5 A child element shall have the same (major and minor) version number as its parent
element.
NOTE – This implies that the element, if present in a child element, has to carry the same values as
the element in the parent element. This is equivalent to omitting the element. Therefore,
this element is normally omitted in child elements.
15.13 Element
15.13.1 Syntax
This element shall have the following attributes:
a) major (required) – the value of this attribute shall be a valid representation of an integer in the range 0
to15 (see 15.17);
b) minor (required) – the value of this attribute shall be a valid representation of an integer in the range 0 to
15.
15.13.2 Semantics
15.13.2.1 This element represents the data element CBEFF_version, and carries the version number of
the CBEFF standard supported by this patron format. The num
...