ISO/IEC 30106-1:2016
(Main)Information technology — Object oriented BioAPI — Part 1: Architecture
Information technology — Object oriented BioAPI — Part 1: Architecture
ISO/IEC 30106-1:2016 specifies an architecture for a set of interfaces which define the OO BioAPI. Components defined in this part of ISO/IEC 30106 include a framework, Biometric Service Providers (BSPs), Biometric Function Providers (BFPs) and a component registry. NOTE Each of these components have an equivalent component specified in ISO/IEC 19784‑1 as the OO BioAPI is intended to be an OO interpretation of this part of ISO/IEC 30106. For this reason, this part of ISO/IEC 30106 is conceptually equivalent to ISO/IEC 19784‑1. Concepts present in this part of ISO/IEC 30106 (for example, BioAPI_Unit and component registry) have the same meaning as in ISO/IEC 19784‑1. While the conceptual equivalence of this part of ISO/IEC 30106 will be maintained with ISO/IEC 19784‑1, there are differences in the parameters passed between functions and the sequence of function calls. These differences exist to take advantage of the features provided by Object Oriented Programming Languages.
Technologies de l'information — Objet orienté BioAPI — Partie 1: Architecture
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 30106-1
First edition
2016-03-15
Information technology — Object
oriented BioAPI —
Part 1:
Architecture
Technologies de l’information — Objet orienté BioAPI —
Partie 1: Architecture
Reference number
©
ISO/IEC 2016
© ISO/IEC 2016, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2016 – All rights reserved
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Symbols and abbreviated terms . 1
5 Object Oriented BioAPI architecture . 2
5.1 Summary of BioAPI architecture . 2
5.2 BioAPI compatibility requirements . 4
5.3 Graphical User Interface (GUI) . 4
5.4 Implementation guidelines . 6
5.4.1 Basic concepts . 6
5.4.2 BioAPI_Unit development . 6
5.4.3 BFP development . 6
5.4.4 BSP development . 7
5.4.5 Framework and component registry . 8
5.4.6 Application development . 8
6 BioAPI CBEFF Patron Formats . 8
6.1 General . 8
6.2 Simple BIR . 8
6.3 Complex BIR .14
6.3.1 Structure .14
6.3.2 Child BIR .14
6.3.3 Parent BIR .14
7 Constants .17
7.1 General .17
7.2 Biometric types .17
7.3 Biometric subtypes .17
7.4 Error codes .18
8 OO BioAPI UML structure .21
8.1 General .21
8.2 Relationships among data structures .22
8.2.1 Class BIR .22
8.2.2 Class UnitSchema .23
8.2.3 Class BFPSchema .24
8.2.4 Class BSPSchema .24
8.2.5 Class FrameworkSchema .25
8.3 BioAPI_Unit structures .25
8.3.1 IArchive .25
8.3.2 IComparison .26
8.3.3 IProcessing .26
8.3.4 ISensor .27
8.4 BFP Structure .27
8.5 BSP Structure .28
8.6 Framework structure .28
8.7 Application related structure .29
© ISO/IEC 2016 – All rights reserved iii
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
The committee responsible for this document is ISO/IEC JTC 1, Information technology, SC 37, Biometrics.
ISO/IEC 30106 consists of the following parts, under the general title Information technology — BioAPI
for object oriented programming languages:
— Part 1: Architecture
— Part 2: Java implementation
— Part 3: C# implementation
iv © ISO/IEC 2016 – All rights reserved
Introduction
The existing versions of BioAPI (ANSI version-INCITS 358 and ISO/IEC 19784-1) specify an application
programming interface expressed in the C language. The use of a portable language like C ensures
the BioAPI is accessible across multiple computing platforms and application domains. BioAPI is an
appropriate fit for applications written in C and is adequate for applications written in C++.
Unfortunately, a function-based language like C does not map easily to the object oriented domain where
this issue may be answered with an object oriented (OO) version of BioAPI. As noted, the function-
based nature of a C API does not map easily to the object oriented paradigm (i.e. languages such as C#
and Java). In particular, the use of a C API from within an object oriented application is unnatural and
requires programming constructs which introduce complexity to the development of an application.
Development of a OO version of BioAPI aims to increase the productivity of software practitioners who
who wish to use the BioAPI whilst remaining in the object oriented domain.
A standard object oriented version of BioAPI allows, in case of Java, BSPs that are intended for loading
into a Java-based application server to perform verification and/or identification operations. In those
application servers, use of the OO BioAPI is more natural when developing a framework and BSPs than
the C version of BioAPI.
Another area in which a standard OO version of BioAPI would be useful is that of small computing
devices based on an object oriented language (OOL), where (as on the large application servers
mentioned above) an OO BioAPI framework and OO BSPs would fit better than their C counterparts.
This part of ISO/IEC 30106 is expected to have the following impact:
— enable creation of BioAPI applications by developers more comfortable with Object Oriented
Languages;
— create a market of standard OO BSP components which target OO environments such as Java
application servers, Java applets, small Java devices, .NET servers, .NET applications, web services;
— increase the level of adoption of BioAPI by decreasing the barrier of entry for OO developers. This
includes providing access to C based BSPs (as if they were OO BSPs) through special versions of the
BioAPI framework, bridging a standard OO BioAPI framework to a standard C BioAPI framework.
© ISO/IEC 2016 – All right
...
DRAFT INTERNATIONAL STANDARD
ISO/IEC DIS 30106-1
ISO/IEC JTC 1/SC 37 Secretariat: ANSI
Voting begins on: Voting terminates on:
2014-12-04 2015-03-04
Information technology — BioAPI for object oriented
programming languages —
Part 1:
Architecture
Titre manque
ICS: 35.040
THIS DOCUMENT IS A DRAFT CIRCULATED
FOR COMMENT AND APPROVAL. IT IS
THEREFORE SUBJECT TO CHANGE AND MAY
NOT BE REFERRED TO AS AN INTERNATIONAL
STANDARD UNTIL PUBLISHED AS SUCH.
IN ADDITION TO THEIR EVALUATION AS
BEING ACCEPTABLE FOR INDUSTRIAL,
TECHNOLOGICAL, COMMERCIAL AND
USER PURPOSES, DRAFT INTERNATIONAL
STANDARDS MAY ON OCCASION HAVE TO
BE CONSIDERED IN THE LIGHT OF THEIR
POTENTIAL TO BECOME STANDARDS TO
WHICH REFERENCE MAY BE MADE IN
Reference number
NATIONAL REGULATIONS.
ISO/IEC DIS 30106-1:2014(E)
RECIPIENTS OF THIS DRAFT ARE INVITED
TO SUBMIT, WITH THEIR COMMENTS,
NOTIFICATION OF ANY RELEVANT PATENT
RIGHTS OF WHICH THEY ARE AWARE AND TO
©
PROVIDE SUPPORTING DOCUMENTATION. ISO/IEC 2014
ISO/IEC DIS 30106-1:2014(E)
Copyright notice
This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as
permitted under the applicable laws of the user’s country, neither this ISO draft nor any extract
from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means,
electronic, photocopying, recording or otherwise, without prior written permission being secured.
Requests for permission to reproduce should be addressed to 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
Reproduction may be subject to royalty payments or a licensing agreement.
Violators may be prosecuted.
ii © ISO 2014 – All rights reserved
ISO/IEC DIS 30106-1
Contents Page
Foreword . v
Introduction . vi
1 Scope . 1
2 Conformance . 1
3 Normative references . 1
4 Terms and definitions . 1
5 Symbols and abbreviated terms . 1
6 Object Oriented BioAPI architecture . 2
6.1 Summary of BioAPI architecture . 2
6.2 BioAPI compatibility requirements . 4
6.3 Graphical User Interface (GUI) . 5
6.4 Implementation guidelines . 6
6.4.1 Basic concepts . 6
6.4.2 BioAPI_Unit development. 6
6.4.3 BFP development . 7
6.4.4 BSP development . 8
6.4.5 Framework and component registry . 8
6.4.6 Application development . 9
7 BioAPI C# CBEFF Patron Formats . 9
8 Constants . 9
8.1 General . 9
8.2 Biometric Types . 9
8.3 Biometric Subtypes . 10
8.4 Error Codes . 10
9 OO BioAPI UML Structure . 13
9.1 Introduction . 13
9.2 Relationships among data structures . 14
9.2.1 Class BIR . 14
9.2.2 Class UnitSchema . 15
9.2.3 Class BFPSchema . 16
9.2.4 Class BSPSchema . 17
9.2.5 Class FrameworkSchema . 18
9.3 BioAPI_Unit structures . 18
9.3.1 IArchive. 18
9.3.2 IComparison . 19
9.3.3 IProcessing . 19
9.3.4 ISensor. 20
9.4 BFP Structure . 20
9.5 BSP Structure . 21
9.6 Framework structure . 22
9.7 Application related structure . 22
Annex A (normative) Conformance statements . 23
A.1 General . 23
A.2 BioAPI OO Conformant Biometric Application . 23
A.3 BioAPI OO Conformant Framework . 23
A.4 BioAPI OO Conformant BSPs . 24
A.4.1 BioAPI OO Conformant Verification BSPs . 26
A.4.2 BioAPI OO Conformant Identification BSPs . 27
© ISO/IEC 2014 – All rights reserved iii
ISO/IEC DIS 30106-1
A.4.3 BioAPI OO Conformant Capture BSPs . 28
A.4.4 BioAPI Conformant Verification Engines . 28
A.4.5 BioAPI OO Conformant Identification Engines . 29
A.4.6 Optional Capabilities . 29
Annex B (informative) Mapping between ISO/IEC 19784-1 and ISO/IEC 30106 . 35
B.1 Introduction . 35
B.2 Data Types . 35
B.3 Unit Classes . 46
B.3.1 Archive unit classes . 46
B.3.2 Comparison unit classes . 49
B.3.3 Processing unit classes . 52
B.3.4 Sensor unit classes . 54
B.4 BFPs . 55
B.5 BSPs . 57
B.6 Component Registry . 66
B.7 Framework . 67
iv © ISO/IEC 2014 – All rights reserved
ISO/IEC DIS 30106-1
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member 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 shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 30106-1 was prepared by Technical Committee ISO/TC JTC1, Information Technology,
Subcommittee SC 37, Biometrics.
This second/third/. edition cancels and replaces the first/second/. edition (), [clause(s) / subclause(s) /
table(s) / figure(s) / annex(es)] of which [has / have] been technically revised.
ISO/IEC 30106 consists of the following parts, under the general title Information Technology — BioAPI for
Object Oriented Programming Languages:
Part 1: Architecture
Part 2: Java implementation
Part 3: C# implementation
© ISO/IEC 2014 – All rights reserved v
ISO/IEC DIS 30106-1
Introduction
The existing versions of BioAPI, the ANSI version-INCITS 358 and ISO/IEC 19784-1, specify an application
programming interface expressed in the C language. The use of this language ensures the wide applicability
and implementability of BioAPI across multiple computing platforms and application domains. This API is an
appropriate fit for applications written in the same language, and is adequate for applications written in C++.
Lack of portability of applications written in C is an issue that can be answered with an object oriented (OO)
version of BioAPI. A C API does not work well with applications written in Java, C#, and other programming
languages. In particular, the use of a C API from within an Object oriented (apart from C++) application is very
unnatural, and requires certain programming artifices that introduce complications in the application, thus
increasing the cost of application development and maintenance. If a standard OO version of BioAPI were
available, the development of Java, C#, etc. applications that use a standard biometric API would be easie
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.