Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 30106 — Object Oriented BioAPI Series
Information technology — Object oriented BioAPI (2016 edition series)
🧩 BS ISO/IEC 30106 is the British Standard series adopted by BSI from the ISO/IEC 30106 international standard, defining Object Oriented BioAPI. Developed by ISO/IEC JTC 1 Subcommittee SC 37 (Biometrics), with UK participation through Technical Committee IST/44, while traditional BioAPI (ISO/IEC 19784) uses a C-style function interface, Object Oriented BioAPI encapsulates biometric capabilities in an object-oriented manner, providing interfaces that better fit modern programming paradigms and are easier to extend and maintain, with concrete implementations given for mainstream object-oriented languages such as Java and C#.
💡 The value of Object Oriented BioAPI lies in “abstraction and reuse”: by organizing biometric capabilities through classes, interfaces, and namespaces, applications and function providers collaborate through object contracts, improving code maintainability and cross-platform reuse.
1. Series Overview and Positioning 📌
This batch covers three parts of the BS ISO/IEC 30106 series: Part 1: Architecture (2016 edition), Part 2: Java implementation (2016 edition), and Part 3: C# implementation (2016 edition). All three are first editions published in 2016 and adopted by the UK in March/April 2016. Part 1 defines the architecture and general concepts, while Parts 2 and 3 provide Java and C# object-oriented implementation specifications respectively.
Object Oriented BioAPI and ISO/IEC 19784 (BioAPI) together form a complete system of biometric application interfaces: 19784 provides the foundational function interface, while 30106 provides the object-oriented encapsulation; they can be used together or selected based on the development language and project needs.
⚠️ Object Oriented BioAPI does not replace traditional BioAPI but is a supplementary implementation for object-oriented languages; choose based on the development language (C/C++ use 19784; Java/C# use 30106) and the existing codebase.
2. Series Structure and Part-Level Points 🔧
| Standard Number | Subject | Edition | Core Content |
|---|---|---|---|
| BS ISO/IEC 30106-1:2016 | Architecture | 1st ed., 2016-03-15 | Defines the architecture and core concepts of Object Oriented BioAPI |
| BS ISO/IEC 30106-2:2016 | Java implementation | 1st ed., 2016-03-15 | Provides the Java implementation specification of Object Oriented BioAPI |
| BS ISO/IEC 30106-3:2016 | C# implementation | 1st ed., 2016-03-15 | Provides the C# implementation specification of Object Oriented BioAPI |
3. Part 1: Overall Architecture Core Content 🔍
Part 1 defines the overall architecture of Object Oriented BioAPI, establishing core concepts, components, and interaction models. Content includes: the BioAPI object model (objects, interfaces, events), biometric processing flows (capture, processing, matching, storage), object-oriented encapsulation of function providers, and object contracts between applications and providers. The specification explains how the object-oriented architecture maps biometric operations, providing a unified design basis for the concrete language implementations in Parts 2 and 3.
The architecture emphasizes “separation of interface and implementation” and “event-driven” design, enabling biometric capabilities to be registered, discovered, and invoked as objects, facilitating runtime dynamic integration of biometric services from different vendors.
4. Part 2: Java Implementation ☕
Part 2 provides the Java implementation specification of Object Oriented BioAPI, defining the Java namespace and library structure. Content covers: Java package/namespace organization (such as the BioAPI namespace and its data namespace), core class and interface definitions, event and callback mechanisms, exception handling, and Java representation of biometric data. The specification enables Java developers to invoke biometric capabilities in a standard way while ensuring compatibility across implementations.
💡 Java is widely used for enterprise applications; the Java implementation of Object Oriented BioAPI allows biometric functionality to integrate seamlessly into mainstream frameworks such as Spring and Java EE, lowering integration barriers.
5. Part 3: C# Implementation 🎯
Part 3 provides the C# implementation specification of Object Oriented BioAPI, defining the C# namespace and library structure. Content covers: C# namespace organization, core classes and interfaces, properties and events, synchronous/asynchronous call models, and C# representation of biometric data. The specification enables .NET platform developers to use biometric capabilities in a standard way, suitable for Windows desktop, server, and cross-platform .NET applications.
6. Application Practice and Selection 🛠️
- 📋 Language selection: choose the corresponding implementation based on the technology stack — Java projects use Part 2, C#/.NET projects use Part 3, and C/C++ projects can continue with ISO/IEC 19784.
- 🔗 Architecture design: design the application layer per the Part 1 object model, decoupling interfaces from implementations to facilitate replacing biometric vendors.
- 🛡️ Security integration: combine with ISO/IEC 19785 (CBEFF) and ISO/IEC 24745 (biometric information protection) for data format and security controls.
- 🌐 Cross-platform deployment: leverage the portability of object interfaces to achieve consistent encapsulation of biometric modules across desktop, mobile, and cloud.
🚨 Interface standardization does not mean security is enabled by default: Object Oriented BioAPI provides only a calling contract; specific security measures (such as template protection, transmission encryption, and access control) still need to be explicitly implemented in the application. Do not assume that using a standard interface automatically makes it secure.
7. Frequently Asked Questions ❓
❓ Q: What is the difference between 30106 and 19784 (BioAPI)?
A: 19784 is a C-style function-based BioAPI; 30106 is an object-oriented BioAPI that encapsulates biometric capabilities through classes and interfaces, targeting object-oriented languages such as Java and C#.
A: 19784 is a C-style function-based BioAPI; 30106 is an object-oriented BioAPI that encapsulates biometric capabilities through classes and interfaces, targeting object-oriented languages such as Java and C#.
❓ Q: Does the series replace 19784?
A: No. They are complementary interface systems; choose based on development language and project needs, or use both in mixed-language systems.
A: No. They are complementary interface systems; choose based on development language and project needs, or use both in mixed-language systems.
❓ Q: Are the Java and C# implementations fully identical?
A: Both follow the unified architecture of Part 1 but are implemented per each language’s conventions (namespaces, event models, exception handling, etc.); semantics are consistent while syntax differs.
A: Both follow the unified architecture of Part 1 but are implemented per each language’s conventions (namespaces, event models, exception handling, etc.); semantics are consistent while syntax differs.
❓ Q: Is this series mandatory?
A: No. It is a voluntary interface standard for biometric application and device vendors to reference during development.
A: No. It is a voluntary interface standard for biometric application and device vendors to reference during development.
🔍 Q: How do I start using Object Oriented BioAPI?
A: First study Part 1 to understand the architecture and object model, then choose Part 2 or Part 3 per the development language, and combine with CBEFF and security standards for end-to-end integration.
A: First study Part 1 to understand the architecture and object model, then choose Part 2 or Part 3 per the development language, and combine with CBEFF and security standards for end-to-end integration.