Biasprofile 1.0 CD 01

Biometric Identity Assurance Services
(BIAS) SOAP Profile, Version 1.0

Commitee Draft 01
20 October 2009
Specification URIs:
This Version:
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0-cd-01.pdf (authoritative)
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0-cd-01.doc
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0-cd-01.html
Previous Version:
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0-wd-07.pdf
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0-wd-07.doc
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0-wd-07.html
Latest Version:
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0.pdf
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0.doc
http://docs.oasis-open.org/bias/soap-profile/v1.0/biasprofile-1.0.html
Technical Committee:
OASIS Biometric Identity Assurance Services (BIAS) Integration TC
Chair(s):
Cathy Tilton, Daon
Editor(s):
Matthew Swayze and Cathy Tilton, Daon
Related Work:
This specification is related to:
ANSI INCITS 442-2008, Biometric Identity Assurance Services (BIAS)
Declared XML Namespace(s):
http://docs.oasis-open.org/bias/ns/bias-1.0/
Abstract:
This document specifies a SOAP profile that implements the BIAS abstract operations specified
in INCITS 442 as SOAP messages.
Status:
This document was last revised or approved by the OASIS BIAS TC on the above date. The level
of approval is also listed above. Check the Latest Version or Latest Approved Version location
noted above for possible later revisions of this document.
Technical Committee members should send comments on this specification to the Technical
Committees email list. Others should send comments to the Technical Committee by using the
Send A Comment button on the Technical Committees web page at http://www.oasisopen.org/committees/bias/.
For information on whether any patents have been disclosed that may be essential to
implementing this specification, and any offers of patent licensing terms, please refer to the
Biasprofile-1.0-cd-01
Copyright OASIS Open 2009. All Rights Reserved.
20 October 2009
Page 1 of 152
Intellectual Property Rights section of the Technical Committee web page (http://www.oasisopen.org/committees/bias/ipr.php).
The non-normative errata page for this specification is located at http://www.oasisopen.org/committees/bias/.
20 October 2009
Page 2 of 152
Notices
Copyright OASIS 2009. All Rights Reserved.
All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual
Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.
This document and translations of it may be copied and furnished to others, and derivative works that
comment on or otherwise explain it or assist in its implementation may be prepared, copied, published,
and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice
and this section are included on all such copies and derivative works. However, this document itself may
not be modified in any way, including by removing the copyright notice or references to OASIS, except as
needed for the purpose of developing any document or deliverable produced by an OASIS Technical
Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must
be followed) or as required to translate it into languages other than English.
The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors
or assigns.
This document and the information contained herein is provided on an "AS IS" basis and OASIS
DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY
OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
OASIS requests that any OASIS Party or any other party that believes it has patent claims that would
necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard,
to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to
such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that
produced this specification.
OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of
any patent claims that would necessarily be infringed by implementations of this specification by a patent
holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR
Mode of the OASIS Technical Committee that produced this specification. OASIS may include such
claims on its website, but disclaims any obligation to do so.
OASIS takes no position regarding the validity or scope of any intellectual property or other rights that
might be claimed to pertain to the implementation or use of the technology described in this document or
the extent to which any license under such rights might or might not be available; neither does it
represent that it has made any effort to identify any such rights. Information on OASIS' procedures with
respect to rights in any document or deliverable produced by an OASIS Technical Committee can be
found on the OASIS website. Copies of claims of rights made available for publication and any
assurances of licenses to be made available, or the result of an attempt made to obtain a general license
or permission for the use of such proprietary rights by implementers or users of this OASIS Committee
Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no
representation that any information or list of intellectual property rights will at any time be complete, or
that any claims in such list are, in fact, Essential Claims.
The names "OASIS", BIAS are trademarks of OASIS, the owner and developer of this specification, and
should be used only to refer to the organization and its official outputs. OASIS welcomes reference to,
and implementation and use of, specifications, while reserving the right to enforce its marks against
misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.
20 October 2009
Page 3 of 152
Table of Contents
1
Introduction ........................................................................................................................................... 7
1.1 Purpose/Scope ................................................................................................................................... 7
1.2 Overview ............................................................................................................................................. 7
1.3 Background ......................................................................................................................................... 7
1.4 Relationship to Other Standards ........................................................................................................ 7
1.5 Terminology ........................................................................................................................................ 8
1.6 References.......................................................................................................................................... 9
1.6.1 Normative References ................................................................................................................. 9
1.6.2 Non-Normative References ....................................................................................................... 10
2
Design Concepts and Architecture (non-normative) .......................................................................... 12
2.1 Philosophy ........................................................................................................................................ 12
2.2 Context.............................................................................................................................................. 12
2.3 Architecture ....................................................................................................................................... 12
3
Data dictionary.................................................................................................................................... 15
3.1 Documentation Conventions............................................................................................................. 15
3.2 Common Elements ........................................................................................................................... 16
3.2.1 ApplicationIdentifier ................................................................................................................... 16
3.2.2 ApplicationUserIdentifier ........................................................................................................... 16
3.2.3 BIASBiometricDataType............................................................................................................ 16
3.2.4 BIASFaultCode .......................................................................................................................... 16
3.2.5 BIASFaultDetail ......................................................................................................................... 17
3.2.6 BIASIdentity ............................................................................................................................... 18
3.2.7 BIASIDType ............................................................................................................................... 18
3.2.8 BiographicDataItemType ........................................................................................................... 18
3.2.9 BiographicDataSetType ............................................................................................................ 19
3.2.10 BiographicDataType ................................................................................................................ 19
3.2.11 BiometricDataElementType..................................................................................................... 20
3.2.12 BiometricDataListType ............................................................................................................ 20
3.2.13 CandidateListType .................................................................................................................. 21
3.2.14 CandidateType ........................................................................................................................ 21
3.2.15 CapabilityListType ................................................................................................................... 21
3.2.16 CapabilityName ....................................................................................................................... 21
3.2.17 CapabilityType ......................................................................................................................... 22
3.2.18 CBEFF_BIR_ListType ............................................................................................................. 22
3.2.19 CBEFF_BIR_Type ................................................................................................................... 23
3.2.20 Classification ........................................................................................................................... 24
3.2.21 ClassificationAlgorithmType .................................................................................................... 24
3.2.22 ClassificationData .................................................................................................................... 24
3.2.23 EncounterListType .................................................................................................................. 24
3.2.24 FusionInformationListType ...................................................................................................... 24
3.2.25 FusionInformationType............................................................................................................ 25
3.2.26 GenericRequestParameters .................................................................................................... 25
3.2.27 InformationType ...................................................................................................................... 25
20 October 2009
Page 4 of 152
3.2.28 ListFilterType ........................................................................................................................... 26

3.2.29 MatchType ............................................................................................................................... 26
3.2.30 ProcessingOptionsType .......................................................................................................... 26
3.2.31 ProductID................................................................................................................................. 26
3.2.32 QualityData .............................................................................................................................. 26
3.2.33 ResponseStatus ...................................................................................................................... 27
3.2.34 ReturnCode ............................................................................................................................. 27
3.2.35 Score ....................................................................................................................................... 27
3.2.36 TokenType............................................................................................................................... 27
3.2.37 VendorIdentifier ....................................................................................................................... 28
3.2.38 Version .................................................................................................................................... 28
3.2.39 VersionType ............................................................................................................................ 28
4
BIAS Messages .................................................................................................................................. 29
4.1 Primitive Operations ......................................................................................................................... 29
4.1.1 AddSubjectToGallery ................................................................................................................ 29
4.1.2 CheckQuality ............................................................................................................................. 30
4.1.3 ClassifyBiometricData ............................................................................................................... 32
4.1.4 CreateSubject ............................................................................................................................ 33
4.1.5 DeleteBiographicData ............................................................................................................... 34
4.1.6 DeleteBiometricData ................................................................................................................. 35
4.1.7 DeleteSubject ............................................................................................................................ 37
4.1.8 DeleteSubjectFromGallery ........................................................................................................ 38
4.1.9 GetIdentifySubjectResults ......................................................................................................... 39
4.1.10 IdentifySubject ......................................................................................................................... 41
4.1.11 ListBiographicData .................................................................................................................. 43
4.1.12 ListBiometricData .................................................................................................................... 45
4.1.13 PerformFusion ......................................................................................................................... 49
4.1.14 QueryCapabilities .................................................................................................................... 51
4.1.15 RetrieveBiographicInformation ................................................................................................ 53
4.1.16 RetrieveBiometricInformation .................................................................................................. 55
4.1.17 SetBiographicData .................................................................................................................. 56
4.1.18 SetBiometricData .................................................................................................................... 58
4.1.19 TransformBiometricData ......................................................................................................... 60
4.1.20 UpdateBiographicData ............................................................................................................ 61
4.1.21 UpdateBiometricData .............................................................................................................. 63
4.1.22 VerifySubject ........................................................................................................................... 64
4.2 Aggregate Operations....................................................................................................................... 66
4.2.1 Enroll ......................................................................................................................................... 66
4.2.2 GetEnrollResults ....................................................................................................................... 67
4.2.3 GetIdentifyResults ..................................................................................................................... 68
4.2.4 GetVerifyResults ....................................................................................................................... 70
4.2.5 Identify ....................................................................................................................................... 71
4.2.6 RetrieveInformation ................................................................................................................... 72
4.2.7 Verify ......................................................................................................................................... 74
5
Message structure and rules .............................................................................................................. 76
20 October 2009
Page 5 of 152
5.1 Purpose and constraints ................................................................................................................... 76

5.2 Message requirements ..................................................................................................................... 77
5.3 Handling binary data ......................................................................................................................... 78
5.3.1 Base64 encoding ....................................................................................................................... 78
5.3.2 Use of XOP................................................................................................................................ 78
5.4 Discovery .......................................................................................................................................... 78
5.5 Identifying operations........................................................................................................................ 79
5.5.1 Operation name element ........................................................................................................... 79
5.5.2 WS-Addressing Action .............................................................................................................. 79
5.6 Security ............................................................................................................................................. 80
5.6.1 Use of SSL 3.0 or TLS 1.0 ........................................................................................................ 80
5.6.2 Data Origin Authentication ........................................................................................................ 81
5.6.3 Message Integrity ...................................................................................................................... 81
5.6.4 Message Confidentiality ............................................................................................................ 81
5.6.5 CBEFF BIR security features .................................................................................................... 81
5.6.6 Security Considerations ............................................................................................................ 81
5.6.7 Security of Stored Data ............................................................................................................. 82
5.6.8 Key Management ...................................................................................................................... 82
5.7 Use with other WS* standards .......................................................................................................... 82
5.8 Tailoring ............................................................................................................................................ 82
6
Error handling ..................................................................................................................................... 83
6.1 BIAS operation return codes............................................................................................................. 83
6.2 SOAP fault codes ............................................................................................................................. 83
7
Conformance ...................................................................................................................................... 84
Annex A. XML Schema ............................................................................................................................... 85
Annex B. Use Cases (non-normative) ..................................................................................................... 140
B.1 Verification Use Case .................................................................................................................... 140
B.2 Asynchronous Verification ............................................................................................................. 141
B.3 Primitive Verification ...................................................................................................................... 142
B.4 Identification Use Case ................................................................................................................. 143
B.5 Biometric Enrollment ..................................................................................................................... 144
B.6 Primitive Enrollment ...................................................................................................................... 145
Annex C. Samples (non-normative) ......................................................................................................... 146
C.1 Create Subject Request/Response Example................................................................................ 146
C.2 Set Biographic Data Request/Response Example ....................................................................... 148
C.3 Set Biometric Data Request/Response Example ......................................................................... 149
Annex D. Acknowledgements .................................................................................................................. 151
Annex E. Revision History........................................................................................................................ 152
20 October 2009
Page 6 of 152
1 Introduction
1.1 Purpose/Scope
3
4
5
6
7
8
This Organization for the Advancement of Structured Information Standards (OASIS) Biometric Identity
Assurance Services (BIAS) profile specifies how to use the eXtensible Markup Language (XML) [XML10]
defined in ANSI INCITS 442-2008 Biometric Identity Assurance Services [INCITS-BIAS] to invoke
Simple Object Access Protocol (SOAP) -based services that implement BIAS operations. These SOAPbased services enable an application to invoke biometric identity assurance operations remotely in a
Services Oriented Architecture (SOA) infrastructure.
9
10
11
Not included in the scope of BIAS is the incorporation of biometric authentication as an integral
component of an authentication or security protocol. (However, BIAS services may be leveraged to
implement biometric authentication in the future.)
12
1.2 Overview
13
In addition to this introduction, this standard includes the following:
14
15
Clause 2 presents the design concepts and architecture for invoking SOAP-based services that
implement BIAS operations.
16
17
Clause 3 presents the namespaces necessary to implement this profile, INCITS BIAS data
elements, and identifies relationships to external data definitions.
18
Clause 4 specifies the content of the BIAS messages.
19
20
Clause 5 presents the BIAS message structure, as well as rules and considerations for its
application.
21
Clause 6 presents information on error handling.
22
Clause 7specifies conformance requirements.
23
24
Annexes include the OASIS BIAS XML schema/sample Web Service Definition Language
(WSDL), use cases, sample code, acknowledgements, and the revision history of this profile.
25
1.3 Background
26
27
28
29
30
31
32
33
34
35
In late 2005/early 2006, a gap was identified in the existing biometric standards portfolio with respect to
biometric services. The Biometric Identity Assurance Services standard proposal was for a collaborative
effort between government and private industry to provide a services-based framework for delivering
identity assurance capabilities, allowing for platform and application independence. This standard
proposal required the attention of two major technical disciplines: biometrics and service architectures.
The expertise of both disciplines was required to ensure the standard was technically sound, market
relevant, and achieved widespread adoption. The International Committee for Information Technology
Standards (INCITS) M1 provided the standards leadership relevant to biometrics, defining the taxonomy
of biometric operations and data elements. OASIS provided the standards leadership relevant to service
architectures with an initial focus on web services, defining the schema and SOAP messaging.
36
37
38
39
40
The driving requirements of the BIAS standard proposal were to provide the ability to remotely invoke
biometric operations across an SOA infrastructure; to provide business level operations without
constraining the application/business logic that implements those operations; to be as generic as possible
technology, framework, & application domain independent; and to provide basic capabilities that can be
used to construct higher level, aggregate/composite operations.
41
1.4 Relationship to Other Standards
42
43
This OASIS BIAS profile comprises a companion standard to ANSI INCITS 442-2008 Biometric Identity
Assurance Services, which defines the BIAS requirements and taxonomy, specifying the identity
20 October 2009
Page 7 of 152
44
45
46
assurance operations and the associated data elements. This OASIS BIAS profile specifies the design
concepts and architecture, data model and data dictionary, message structure and rules, and error
handling necessary to invoke SOAP-based services that implement BIAS operations.
47
48
49
Together, the BIAS standard and the BIAS profile provide an open framework for deploying and remotely
invoking biometric-based identity assurance capabilities that can be readily accessed across an SOA
infrastructure.
50
51
52
53
This relationship allows the leveraging of the biometrics and web services expertise of the two standards
development organizations. Existing standards are available in both domains and many of these
standards will provide the foundation and underlying capabilities upon which the biometric services
depend.
54
1.5 Terminology
55
56
57
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD
NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described
in [RFC2119].
58
The following additional terms and definitions are used:
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
Note: The terms and definitions specified in INCITS (InterNational Committee for Information Technology
Standards) (Project 1823-D) also apply to this Standard.
BIAS operation and data element names are not defined here, but in their respective sections.
BIAS
Biometric Identity Assurance Services
BIR
Biometric Information Record
ESB
Enterprise Service Bus
HTTP
HyperText Transfer Protocol
HTTPS
HyperText Transfer Protocol over SSL or HTTP Secure
IRI
Internationalized Resource Identifier
SOA
Service-Oriented Architecture
SOAP
Simple Object Access Protocol
SSL
Secure Sockets Layer
TLS
Transport Layer Security
UDDI
Universal Description, Discovery, and Integration
URI
Uniform Resource Identifier
VPN
Virtual Private Network
WSDL
Web Services Description Language
WSS
Web Services Security
XML
eXtensible Markup Language
20 October 2009
Page 8 of 152
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
CBEFF
Common Biometric Exchange Formats Framework - data elements and BIR formats specified in
ISO/IEC 19785-1
BIAS implementation
software entity that is capable of creating, processing, sending, and receiving BIAS messages
BIAS endpoint
runtime entity, identified by an endpoint URI/IRI, capable of sending and receiving BIAS
messages, and containing a running BIAS implementation
BIAS message
message that can be sent from a BIAS endpoint to another BIAS endpoint through a BIAS link
channel
BIAS request message
BIAS message conveying a request for an action to be performed by the receiving BIAS endpoint
BIAS response message
BIAS message conveying a response to a prior BIAS requestmessage
113
1.6 References
114
1.6.1 Normative References
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
[RFC2119]
S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, IETF
RFC 2119, March 1997.
http://www.ietf.org/rfc/rfc2119.txt
[CBEFF]
ISO/IEC 19785, Information technology Common Biometric Exchange Formats

Framework Part 1: Data element specification & Part 3: Patron format
specifications
http://www.iso.org
[DATE-TIME]
ISO 8601:2004, Data elements and interchange formats Information

interchange Representation of dates and times
http://www.iso.org
[INCITS-BIAS]
ANSI INCITS 442-2008, Biometric Identity Assurance Services (BIAS), May 2008
http://www.incits.org
[IRI]
M. Duerst, et al, Internationalized Resouce Identifiers, W3C RFC3987, January

2005
134
135
[SOAP11]
Simple Object Access Protocol (SOAP) 1.1, 8 May 2000

http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
136
137
138
139
[URI]
T. Berners-Lee, R. Fielding, L. Masinter, Uniform Resource Identifiers (URI):

Generic Syntax, RFC 3986, MIT/LCS, U.C. Irvine, Xerox Corporation, January
2005.
http://ietf.org/rfc/rfc3986
140
141
142
[UTF-8]
ISO/IEC 10646:2003, Information technology Universal Multiple-Octet Coded

Character Set (UCS)
http://www.iso.org
20 October 2009
Page 9 of 152
143
144
145
[WS-Addr]
W3C Recommendation, Web Services Addressing 1.0 - Core, and Web

Services Addressing 1.0 - SOAP Binding, 9 May 2006
http://www.w3.org/2002/ws/addr/
146
147
[WS-I-Basic]
Basic Profile Version 1.1, 10 April 2006

http://www.ws-i.org/Profiles/BasicProfile-1.1-2006-04-10.html
148
149
150
[WS-I-Bind]
Web Services-Interoperability Organization (WS-I) Simple SOAP Binding Profile

Version 1.0, 24 August 2004
http://www.ws-i.org/Profiles/SimpleSoapBindingProfile-1.0-2004-08-24.html
151
152
[WSDL11]
Web Services Description Language (WSDL) 1.1, 15 March 2001

http://www.w3.org/TR/2001/NOTE-wsdl-20010315
153
154
[XML 10]
Extensible Markup Language (XML) 1.0, 16 August 2006

http://www.w3.org/TR/2006/REC-xml-20060816/
155
156
[XOP]
XML-binary Optimized Packaging, W3C Recommendation, 25 January 2005

http://www.w3.org/TR/2005/REC-xop10-20050125/
157
1.6.2 Non-Normative References
158
159
160
[BioAPI]
ISO/IEC 19784-1:2006, Information technology Biometric Application

Programming Interface Part 1: BioAPI Specification
http://www.iso.org
161
162
[BIO SEC]
ISO 19092 Financial services -- Biometrics -- Security framework

http://www.iso.org
163
164
165
[EBTS-DOD]
Department of Defense Electronic Biometric Transmission Specification, Version

2.0, 27 March 2009
http://www.biometrics.dod.mil/CurrentInitiatives/Standards/EBTS.aspx
166
167
168
169
[EBTS-FBI]
IAFIS-DOC-01078-8.1, Electronic Biometric Transmission Specification

(EBTS), Version 8.1, November 19, 2008, Federal Bureau of Investigation,
Criminal Justice Information Services Division
http:// www.fbibiospecs.org
170
171
172
173
[EFTS]
IAFIS-DOC-01078-7, Electronic Fingerprint Transmission Specification (EFTS),

Version 7.1, May 2, 2005, Federal Bureau of Investigation, Criminal Justice
Information Services Division
http:// www.fbibiospecs.org
174
175
[HR-XML]
HR-XML Consortium Library, 2007 April 15

http:// www.hr-xml.org
176
177
178
[INT-I]
Interpol Implementation of ANSI/NIST ITL1-2000, Ver 4.22b, October 28, 2005,

The Interpol AFIS Expert Group
http:// www.interpol.int
179
180
[NIEM]
National Information Exchange Model (NIEM), Ver 2.0, June 2007, US DOJ/DHS
http://www. www.niem.gov
181
182
[RFC2246]
T. Dierks & C. Allen, The TLS Protocol, Version 1.0, January 1999
20 October 2009
Page 10 of 152
183
184
185
[RFC2617]
J. Franks, et al, HTTP Authentication: Basic and Digest Access Authentication,

June 1999
186
187
188
[RFC3280]
R. Housley, et al, Internet X.509 Public Key Infrastructure Certificate and

Certificate Revocation List (CRL) Profile, April 2002
189
190
[SAML]
OASIS Standard, Security Assertion Markup Language (SAML) 2.0, March 2005
http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf
191
192
193
[SAML SEC]
OASIS Standard, Security and Privacy Considerations for the OASIS Security
Assertion Markup Language (SAML) V2.0, March 2005
http://docs.oasis-open.org/security/saml/v2.0/saml-sec-consider-2.0-os.pdf
194
195
[SSL3]
SSL 3.0 Specification

http://www.freesoft.org/CIE/Topics/ssl-draft/3-SPEC.HTM
196
197
198
199
[WSS]
OASIS Standard, Web Services Security: SOAP Message Security 1.1, (WSSecurity 2004), 1 February 2006
http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-osSOAPMessageSecurity.pdf
200
201
[X509]
X.509: Information technology - Open Systems Interconnection - The Directory:

Public-key and attribute certificate frameworks, ITU-T, August 2005
202
203
204
205
[xNAL]
OASIS Committee Specification 02, Customer Information Quality Specifications

Version 3.0: Name (xNL), Address (xAL), Name and Address (xNAL) and Party
(xPIL), 20 September 2008
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ciq#download
206
20 October 2009
Page 11 of 152
207
2 Design Concepts and Architecture (non-normative)
208
2.1 Philosophy
209
210
211
Rather than define a totally new and unique messaging protocol for biometric services, this specification
instead defines a method for using existing biometric and Web services standards to exchange biometric
data and perform biometric operations.
212
2.2 Context
213
214
215
216
217
218
Today, biometric systems are being developed which collect, process, store and match biometric data for
a variety of purposes. In many cases, data and/or capabilities need to be shared between systems or
systems serve a number of different client stakeholders. As architectures move towards services-based
frameworks, access to these biometric databases and services is via a Web services front-end. However,
lack of standardization in this area has led implementers to develop customized services for each
system/application.
219
220
221
BIAS is intended to provide a common, yet flexible, Web services interface that can be used within both
closed and open SOA systems. Figure 1, below, depicts the context in which the BIAS messages will be
implemented.
222
223
Subject
Biometric
Resources
Client
(Requester)
System/
Application
A
BIAS Messages
Subject
BIAS
Service
Provider
Client
(Requester)
System/
Application
N
Administrator
224
225
226
Figure 1. BIAS Context
227
228
229
230
The clients (requesters) may use standard discovery mechanisms (i.e., UDDI directories) to discover the
BIAS service provider (implementation) or, particularly in closed systems, the URI/IRI and WSDL for the
service provider may be known a priori by the client BIAS application developer.
231
2.3 Architecture
232
233
234
235
BIAS Web services are intended to be used within systems employing a services framework, such as a
services-oriented architecture (SOA) (although implementations are not limited to this environment). As
such, it is recognized that the clients may interact directly with the BIAS service provider or layers may
exist between the client and the service provider, for example as an ESB or other application layer.
236
The BIAS Architecture as shown in Figure 2, in which:
237
238
A Client request to the BIAS Web services may be triggered by a human interaction OR any
proxy system such as an ESB.
20 October 2009
Page 12 of 152
239
240
241
242
243
244
Client sends and receives SOAP messages that conform to the BIAS schemas
The calls to the BIAS Implementation use OASIS Service Interfaces and Bindings (via
WSDL)
The BIAS implementation maps the service call to the appropriate internal API or set of APIs
and returns data according to the service interface.
Note that services are represented as circles.
245
246
247
248
Figure 2. Representative BIAS Architecture
249
250
251
NOTE: It is possible that BIAS may also be used between the service provider and the managed
resource (e.g., a biometric matcher).
252
253
At the heart of the BIAS messaging protocol are the concepts of BIAS messages and endpoints.
254
BIAS implementation
255
256
257
A BIAS implementation is a software entity that is capable of creating, processing, sending, and receiving
BIAS messages. This standard does not define requirements for the BIAS implementation other than
defining the messages and protocols used by the endpoints.
258
BIAS messages
259
260
A BIAS message is a one that can be sent from a BIAS endpoint to another BIAS endpoint over a TCP/IP
link.
261
BIAS endpoints
20 October 2009
Page 13 of 152
262
263
A BIAS endpoint is a runtime entity, uniquely identified and accessed by an endpoint URI/IRI [URI] [IRI],
capable of sending and receiving BIAS messages.
264
265
266
Note that when not publicly and directly exposed, the endpoints for purposes of this specification are the
BIAS service provider exposing BIAS services and the component that directly interacts with that service
provider, e.g., the business application or ESB, rather than the ultimate end client requester.
20 October 2009
Page 14 of 152
267
3 Data dictionary
268
269
270
271
272
This section describes the BIAS data elements used within BIAS messages (as defined in Clause 4).
Common data elements are defined for use in one or more operations. These include common data types
or return codes. BIAS data elements are defined in ANSI INCITS 442-2008. The elements, complex types
and simple types described for the BIAS messages belong to the following namespace: http://docs.oasisopen.org/bias/ns/bias-1.0/. See Annex A for the XML schema.
273
274
NOTE: Biographic and biometric data included in a native XML format MAY contain elements
referencing external namespaces (e.g., ansi-nist).
275
3.1 Documentation Conventions
276
277
278
279
Each common element has a section describing its content. Likewise, each operation has a section
describing the request and response messages and the associated input and output parameters. The
input and output of each message and the comment elements are detailed in a table as described in the
figure below. Each field that forms part of the message request/response is detailed in the table.
280
Header
Name
Description
Field
The name of the field.
Type
The XML schema type of the field.
The cardinality of the field
Meaning
281
Defines if the field must be present.
Values
Value Meaning
One occurrence
0..1
Zero or one occurrence
0..*
Zero or more occurrences
1..*
One or more occurrences
Yes is always required
No is not always required, an

optional field.
Conditional requirement is
dependent on system or message
conditions.
Gives a short description of the fields

use
Figure 3. BIAS Message Input/Output Dictionary Table Headings
282
Fields Hierarchy Explained:
283
To denote the field hierarchy the symbol
284
285
All string types/elements MUST consist of ISO/IEC 10646 (Unicode) characters encoded in UTF-8 [UTF8] (see ISO/IEC 10646:2003, Annex D).
is used to denote the child-of relationship.
20 October 2009
Page 15 of 152
286
3.2 Common Elements
287
3.2.1 ApplicationIdentifier
288
289
Type:
string
Description:
Identifies an application.
Min Length:
Max Length:
255
3.2.2 ApplicationUserIdentifier
Type:
string
Description:
Identifies an application user or instance.
Min Length:
Max Length:
255
3.2.3 BIASBiometricDataType
Field
Type
BIASBiometricDataType
Meaning
Wraps the various BIAS biometric

types.
The operations that use this type
specify which elements are required.
290
291
BIRList
CBEFF_BIR_ListType
0..1
A list of CBEFF-BIR elements.
BIR
CBEFF_BIR_Type
0..1
Contains biometric information in either

a non-XML or an XML representation.
InputBIR
CBEFF_BIR_Type
0..1
Maps to specific INCITS BIAS

elements as required by that
specification.
ReferenceBIR
CBEFF_BIR_Type
0..1
Maps to specific INCITS BIAS

elements as required by that
specification.
BiometricDataList
BiometricDataListType
0..1
A list of biometric data elements.
3.2.4 BIASFaultCode
Type:
String
Description:
Error code referenced in a SOAP fault.
BIASFaultCode Enumeration Values

Value
Description
UNKNOWN_ERROR
The service failed for an unknown reason.
20 October 2009
Page 16 of 152
Value
Description
UNSUPPORTED_CAPABILITY
A requested capability is not supported by the service

implementation.
INVALID_INPUT
The data in a service input parameter is invalid.
BIR_QUALITY_ERROR
Biometric sample quality is too poor for the service to succeed.
INVALID_BIR
The input BIR is empty or in an invalid or unrecognized format.
BIR_SIGNATURE_FAILURE
The service could not validate the signature, if used, on the input
BIR.
BIR_DECRYPTION_FAILURE
The service could not decrypt an encrypted input BIR.
INVALID_ENCOUNTER_ID
The input encounter ID is empty or in an invalid format.
INVALID_SUBJECT_ID
The input subject ID is empty or in an invalid format.
UNKNOWN_SUBJECT
The subject referenced by the input subject ID does not exist.
UNKNOWN_GALLERY
The gallery referenced by the input gallery ID does not exist.
UNKNOWN_ENCOUNTER
The encounter referenced by the input encounter ID does not

exist.
UNKNOWN_BIOGRAPHIC_FORMAT
The biographic data format is not known or not supported.
UNKNOWN_IDENTITY_CLAIM
The identity referenced by the input identity claim does not exist.
INVALID_IDENTITY_CLAIM
The identity claim requested is already in use.
NONEXISTANT_DATA
The data requested for deletion does not exist.
292
NOTES:
293
(1) See Clause 6 (Error handling) for an explanation of BIAS faults and return codes.
294
(2) Service provider MAY define additional values specific to their service implementation.
295
(3) See section 5.5 for additional information on BIAS security.
296
3.2.5 BIASFaultDetail
Field
Type
BIASFaultDetail
Meaning
Defines the error information

associated with a SOAP fault.
BIASFaultType
BIASFaultCode
References an error code.
BIASFaultMessage
string
Provides a brief explanation of the

fault.
BIASFaultDescription
string
0..1
Provides detailed information about a

BIAS fault, such as trace details.
20 October 2009
Page 17 of 152
297
3.2.6 BIASIdentity
Field
Type
BIASIdentity
Meaning
Defines a single element for

encapsulating the data
associated with an Identity.
Includes the Identitys
reference identifiers,
biographic data, and biometric
data.
The operations that use this
type specify which elements
are required.
BIASIDType
SubjectID
0..1
A system unique identifier for

a subject.
Required as input to many
operations.
IdentityClaim
BIASIDType
0..1
An identifier by which a
subject is known to a
particular gallery or population
group.
EncounterID
BIASIDType
0..1
The identifier of an encounter

associated with the subject.
Required for encountercentric models.
298
299
EncounterList
EncounterListType
0..1
A list of encounters
associated with a subject.
BiographicData
BiographicDataType
0..1
An Identitys biographic data.
BiographicDataElements
BiographicDataType
0..1
An Identitys biographic data

elements that are stored in
the implementing system.
BiometricData
0..1
An Identitys biometric data.
3.2.7 BIASIDType
Type:
string
Description:
A BIAS Identifier.
3.2.8 BiographicDataItemType
Field
Type
BiographicDataItemType
Meaning
Defines a single biographic data element.
Name
string
The name of the biographic data item.
Type
string
The data type for the biographic data item.
Value
string
0..1
The value assigned to the biographic data item.
20 October 2009
Page 18 of 152
300
301
302
NOTE: This element can be used to transmit scanned identity documents or document information
(e.g., passports, drivers license, birth certificates, utility bills, etc. required to establish an identity).
3.2.9 BiographicDataSetType
Field
Type
BiographicDataSetType
unspecified
303
any
0..*
Meaning
Defines a set of biographic data that is formatted

according to the specified format.
Biographic data formatted according to a specific format.
BiographicDataSetType Attributes
Name
Type
Use
Meaning
name
string
REQUIRED
The name of the biographic data format. Use these names for
common formats: FBI-EFTS [EFTS], FBI-EBTS [EBTS-FBI], DODEBTS [EBTS-DOD], INT-I [INT-I], NIEM [NIEM], xNAL [xNAL], HRXML [HR-XML].
version
string
OPTIONAL
The version of the biographic data format (e.g., 7.1 for FBI-EFTS
or 2.0 for NIEM).
source
string
REQUIRED
Reference to a URI/IRI describing the biographic data format. For

example: (FBI-EFTS and FBI-EBTS) www.fbibiospecs.org, (DODEBTS) www.biometrics.dod.mil, (INT-I) www.interpol.int, (NIEM)
www.niem.gov, (xNAL) www.oasis-open.org, (HR-XML) www.hrxml.org.
type
string
REQUIRED
The biographic data format type. Use these types for common
formats: ASCII (e.g., for non-XML versions of FBI-EFTS, FBI-EBTS,
DOD-EBTS, or INT-I), XML (e.g., for NIEM, xNAL, and HR-XML or
future versions of FBI-EBTS).
304
305
306
NOTE: Biographic data formats are not limited to those listed. The string value is not enumerated.
If one of the common types are used, it MUST be indicated by the specified name values; however,
the service provider MAY offer other formats. See INCITS 442 for further information.
307
308
3.2.10 BiographicDataType
Field
Type
BiographicDataType
Meaning
Defines a set of biographic data

elements, utilizing either the
BiographicDataItemType to
represent a list of elements or the
BiographicDataSetType to
represent a complete, formatted
set of biographic information.
One of the following elements
must be present.
LastName
string
0..1
The last name of a subject.
FirstName
string
0..1
The first name of a subject.
BiographicDataItem
0..*
A single biographic data element.
20 October 2009
Page 19 of 152
Field
BiographicDataSet
309
Type
Meaning
0..1
A set of biographic data

information.
NOTE: The implementer is given three choices for encoding biographic data:
310
Encode only first and last name using the defined fields within BiographicDataType
311
Define a list of biographic data elements using the BiographicDataItemType
312
313
Use a pre-defined set of biographic data (e.g., as specified in another standard) using
the BiographicDataSetType.
314
315
See also INCITS 442, section 8.1 for further information.
3.2.11 BiometricDataElementType
Field
Type
BiometricDataElementType
316
317
Meaning
Provides descriptive information about

biometric data, such as the biometric type,
subtype, and format, contained in the BDB
of the CBEFF-BIR.
BiometricType
iso-iec19785-3-7:
Multiple-types
The type of biological or behavioral data

stored in the biometric record, as defined
by CBEFF.
BiometricTypeCount
positiveInteger
0..1
The number of biometric records having

the biometric type recorded in the
biometric type field.
BiometricSubType
iso-iec19785-3-7:
Subtype
0..1
More specifically defines the type of

biometric data stored in the biometric
record, as defined by CBEFF.
BDBFormatOwner
iso-iec19785-3-7:
Registered-int
Identifies the standards body, working

group, industry consortium, or other
CBEFF biometric organization that has
defined the format for the biometric data.
BDBFormatType
iso-iec19785-3-7:
Registered-int
Identifies the specific biometric data

format specified by the CBEFF biometric
organization recorded in the BDB Format
Owner field.
NOTE: XML biometric metadata (BIR header elements) is aligned with ISO/IEC 19785-3, XML
Patron Format. [CBEFF]
318
319
3.2.12 BiometricDataListType
Field
Type
BiometricDataElement
0..*
Meaning
A list of biometric data

elements.
Data structure containing

information about a biometric
record.
20 October 2009
Page 20 of 152
320
3.2.13 CandidateListType
Field
Type
CandidateListType
Candidate
321
CandidateType
0..*
Meaning
Defines a set of candidates, utilizing the

CandidateType to represent each element in the set.
A single candidate.
3.2.14 CandidateType
Field
Type
CandidateType
322
323
Meaning
Defines a single candidate as a possible

match in response to a biometric
identification request.
Score
Score
0..1
The match score.
BiographicData
BiographicDataType
0..1
Biographic data associated with the

candidate match.
BIRList
CBEFF_BIR_ListType
Biometric data associated with the

candidate match.
CandidateType Attributes
Name
Type
Use
Meaning
rank
integer
REQUIRED
The rank of the candidate in relation to other

candidates for the same biometric identification
operation.
3.2.15 CapabilityListType
Field
Type
CapabilityListType
Capability
324
325
CapabilityType
0..*
Meaning
Defines a set of capabilities.
A single capability.
3.2.16 CapabilityName
Type:
string
Description:
A list of capability items.
CapabilityName Enumeration Values

Value
Description
AggregateInputDataOptional
A data element accepted as optional input by the implementing system

for the aggregate services.
AggregateInputDataRequired
A data element required as input by the implementing system for the

aggregate services.
AggregateProcessingOption
A processing option supported by the implementing system for the

aggregate services.
20 October 2009
Page 21 of 152
326
Value
Description
AggregateReturnData
A data element returned by the implementing system for the aggregate

services.
AggregateServiceDescription
Describes the processing logic of an aggregate service supported by the

implementing system.
BiographicDataSet
Identifies a biographic data set supported by the implementing system.
CBEFFPatronFormat
A patron format supported by the implementing system.
ClassificationAlgorithmType
A classification algorithm type supported by the implementing system.
ConformanceClass
Identifies the conformance class of the BIAS implementation.
Gallery
A gallery or population group supported by the implementing system.
IdentityModel
Identifies whether the implementing system is person-centric or

encounter-centric based.
MatchScore
Identifies the use of match scores returned by the implementing system.
QualityAlgorithm
A quality algorithm vendor and algorithm vendor product ID supported by

the implementing system.
SupportedBiometric
A biometric type supported by the implementing system.
TransformOperation
A transform operation type supported by the implementing system.
3.2.17 CapabilityType
Field
Type
CapabilityType
327
Meaning
Defines a single capability

supported by an implementing
system.
CapabilityName
CapabilityName
The name of the capability.
CapabilityID
string
0..1
An identifier assigned to the

capability by the implementing
system.
CapabilityDescription
string
0..1
A description of the capability.
CapabilityValue
string
0..1
A value assigned to the capability.
CapabilitySupportingValue
string
0..1
A secondary value supporting the

capability.
CapabilityAdditionalInfo
string
0..1
Contains additional information for

the supported capability.
3.2.18 CBEFF_BIR_ListType
Field
Type
CBEFF_BIR_ListType
Meaning
A list of CBEFF-BIR elements.
20 October 2009
Page 22 of 152
Field
BIR
328
Type
Meaning
CBEFF_BIR_Type
0..*
CBEFF structure containing information about a

biometric sample.
3.2.19 CBEFF_BIR_Type
Field
Type
Meaning
Represents biometric information,

with either a non-XML or XML
representation.
0..1
Describes what is contained in a

BIR.
CBEFF_BIR_Type
BIR_Information
bir-info
iso-iec19785-3-7:BIRinfo
0..1
Contains information about the

CBEFF-BIR.
bdb-info
iso-iec19785-3-7:BDBinfo
0..1
Contains information about the BDB

in a simple CBEFF-BIR.
sb-info
iso-iec19785-3-7:SBinfo
0..1
Contains information about the

security block, if used, in a simple
CBEFF-BIR.
One of the following sub-elements

must be present.
BIR
329
BinaryBIR
base64Binary
0..1
A non-XML CBEFF-BIR.
URI_BIR
anyURI/IRI
0..1
A URI/IRI reference to a CBEFFBIR.
XML_BIR
iso-iec19785-3-7:BIR
0..1
An XML CBEFF-BIR, using the XML

Patron Format as defined in
ISO/IEC 19785-3:2007.
NOTE: The implementer is given three choices for encoding a BIR:
330
As an XML BIR (following the XML Patron format as specified in [CBEFF] Part 3, Clause 13)
331
As a reference to a URI (from which the receiver would retrieve the actual BIR)
332
As a complete Base64 encoded binary (non-XML) BIR.
333
334
335
336
The latter two alternatives can use any CBEFF Patron Format. The optional BIR_Information provides a
mechanism for exposing metadata associated with a BIR format that is not easily decoded (i.e., a nonXML BIR). See section 5.3 for more information on handling of binary data within BIAS and INCITS 442,
Clause 8.2, for more information on representing biometric data.
337
CBEFF_BIR_Type Attributes
338
Name
Type
Use
Meaning
format-owner
iso-iec19785-3-7:Registered-int
REQUI
RED
Identifies the Patron format owner.
format-type
iso-iec19785-3-7:Registered-int
REQUI
RED
Identifies the Patron format type.
NOTE:
20 October 2009
Page 23 of 152
339
340
(1) XML BIRs MUST conform to ISO/IEC 19785-3 (clause 13, XML Patron Format); however, nonXML (binary) and URI BIRs MAY implement any CBEFF patron format.
341
342
(2) It is RECOMMENDED that only registered CBEFF patron formats be used; however, in closed
systems, this may not be required.
343
344
345
3.2.20 Classification
Type:
string
Description:
The result of a classification.
3.2.21 ClassificationAlgorithmType
Type:
string
Description:
Type of classification algorithm that was used to perform the classification.
3.2.22 ClassificationData
Field
Type
ClassificationData
346
Meaning
Contains information on
classification results and
the algorithm used to
determine the
classification.
Classification
Classification
The result of the

classification.
Identifies the type of

classification algorithm
that was used to perform
the classification.
3.2.23 EncounterListType
Field
Type
EncounterListType
EncounterID
347
BIASIDType
0..*
Meaning
Defines a set of encounters.
The identifier of an encounter.
3.2.24 FusionInformationListType
Field
Type
FusionInformationListType
FusionElement
FusionInformationType
2..*
Meaning
Contains at a minimum two sets of

fusion input elements, as input to the
PerformFusion operation.
A set of fusion information.
20 October 2009
Page 24 of 152
348
3.2.25 FusionInformationType
Field
Type
Meaning
Represents the information necessary to

perform a fusion operation.
BiometricType
iso-iec19785-3-7:
Multiple-types
The type of biological or behavioral data

stored in the biometric record, as defined
by CBEFF.
BiometricSubType
iso-iec19785-3-7:
Subtype
0..1
More specifically defines the type of

biometric data stored in the biometric
record.
AlgorithmOwner
string
The owner or vendor of the algorithm used

to determine the score or decision.
AlgorithmType
string
The Algorithm Owners identifier for the

specific algorithm product and version
used to determine the score or decision.
Score
Score
0..1
The similarity score assigned by the

matching algorithm.
Either a Score or a Decision element
MUST be used.
string
Decision
0..1
The match decision assigned by the

matching algorithm.
Either a Score or a Decision element
MUST be used.
349
3.2.26 GenericRequestParameters
Field
Type
GenericRequestParameters
350
351
352
Meaning
Common request parameters

that can be used to identify the
requester.
Application
ApplicationIdentifier
0..1
Identifies the requesting

application.
ApplicationUser
ApplicationUserIdentifier
0..1
Identifies the user or instance of

the requesting application.
BIASOperationName
string
0..1
Identifies the BIAS operation that

is being requested.
NOTE: See section 5.4 for alternatives for identifying the requested BIAS operation in a BIAS
SOAP message.
3.2.27 InformationType
Field
Type
InformationType
Meaning
Allows for an unlimited number of data element types,

and it does not specify nor require any particular data
element.
20 October 2009
Page 25 of 152
Field
353
unspecified
Type
any
0..*
Meaning
3.2.28 ListFilterType
Field
Type
ListFilterType
354
355
Provides a method to filter the

amount of information returned in a
search of biometric data.
iso-iec19785-3-7:
Multiple-types
1..*
Limits the returned information to a

specific type of biometric, as defined
by CBEFF.
IncludeBiometricSubType
boolean
A Boolean flag indicating if biometric

subtype information should be
returned.
3.2.29 MatchType
Type:
boolean
Description:
The result of a fusion method.
3.2.30 ProcessingOptionsType
Type
ProcessingOptionsType
string
Option
357
Meaning
BiometricTypeFilter
Field
356
0..*
Meaning
BIAS aggregate operations support the ability to

include various processing options which direct and
possibly control the business logic for that operation.
The ProcessingOptionsType provides a method to
represent those options. Processing options SHOULD
be defined by the implementing system.
An option supported by the implementing system.
3.2.31 ProductID
Type:
string
Description:
The vendors ID for a particular product.
3.2.32 QualityData
Field
Type
QualityData
QualityScore
iso-iec19785-3-7:
Quality
0..1
Meaning
Contains information about a

biometric samples quality and the
algorithm used to compute the
quality.
The quality of a biometric sample.
20 October 2009
Page 26 of 152
Field
358
Type
Meaning
AlgorithmVendor
VendorIdentifier
The vendor of the quality algorithm

used to determine the quality score.
AlgorithmVendorProductID
ProductID
The vendors ID for the algorithm

used to determine the quality.
AlgorithmVersion
VersionType
0..1
The version of the algorithm used to

determine the quality.
3.2.33 ResponseStatus
Field
Type
ResponseStatus
359
360
361
Return
ReturnCode
The return code indicates the return status of the

operation.
Message
string
0..1
A short message corresponding to the return code.
3.2.34 ReturnCode
Type:
unsignedLong
Description:
Return value specifying success or other condition.
ReturnCode Enumeration Values

Value
Description
Success
3.2.35 Score
Type:
float
Description:
Match result or quality score.
362
363
364
Meaning
NOTE: Matching scores MAY be in a standardized or proprietary form in terms of value range and
interpretation. Quality scores, however, follow the definition found in ISO/IEC 19785-3, section 13.
3.2.36 TokenType
Field
Type
TokenType
Meaning
Defines a token that is returned for asynchronous

processing.
TokenValue
string
A value returned by the implementing system that is

used to retrieve the results to an operation at a later
time.
Expiration
date
A date and time at which point the token expires and

the operation results are no longer guaranteed to be
available.
20 October 2009
Page 27 of 152
365
366
367
NOTE: Date/time format is defined in INCITS 442 and is consistent with the date format specified
in ISO/IEC 19785-3 and ISO 8601 [DATE-TIME]. See also Annex A for schema definition.
3.2.37 VendorIdentifier
Type:
string
Description:
Identifies a vendor.
368
369
370
371
NOTE: Vendor identifiers are registered with IBIA as the CBEFF registration authority (see
ISO/IEC 19785-2). Registered biometric organizations are listed at:
http://www.ibia.org/cbeff/_biometric_org.php.
3.2.38 Version
Field
Type
Version
372
Meaning
For a description or definition of each data element, see

the referenced CBEFF standards in the
CBEFF_BIR_Type schema.
major
nonNegativeInteger
minor
nonNegativeInteger
3.2.39 VersionType
Type:
string
Description:
The version of a component.
20 October 2009
Page 28 of 152
373
4 BIAS Messages
374
375
376
This section describes the BIAS messages implementing BIAS operations as defined in ANSI INCITS
442-2008. The operations are listed alphabetically, with each operation containing a request and a
response message. The tables follow the conventions described in section 3.1.
377
4.1 Primitive Operations
378
4.1.1 AddSubjectToGallery
379
AddSubjectToGalleryRequest
380
AddSubjectToGalleryResponse
381
382
383
384
385
386
The AddSubjectToGallery operation registers a subject to a given gallery or population group. As an

OPTIONAL parameter, the value of the claim to identity by which the subject is known to the gallery MAY
be specified. This claim to identity MUST be unique across the gallery. If no claim to identity is specified,
the subject ID (assigned with the CreateSubject operation) will be used as the claim to identity.
Additionally, in the encounter-centric model, the encounter ID associated with the subjects biometrics
that will be added to the gallery MUST be specified.
387
Request Message
Field
Type
AddSubjectToGalleryRequest
Meaning
Register a subject to a
given gallery or
population group.
0..1
Common request
parameters that can be
used to identify the
requester.
Application
0..1

application.
ApplicationUser
0..1
Identifies the user or

instance of the
requesting application.
BIASOperationName
string
0..1
Identifies the BIAS

operation that is being
requested:
AddSubjectToGallery.
GalleryID
BIASIDType
The identifier of the

gallery or population
group to which the
subject will be added.
Identity
BIASIdentity
The identity to add to

the gallery.
BIASIDType
A system unique
identifier for a subject.
SubjectID
20 October 2009
Page 29 of 152
Field
Type
Meaning
IdentityClaim
BIASIDType
0..1
particular gallery or
population group. (This
could be a username or
account number, for
example.)
EncounterID
BIASIDType
0..1
The identifier of an
encounter associated
with the subject.
388
Response Message
Field
Type
AddSubjectToGalleryResponse
Meaning
The response to an AddSubjectToGallery

operation.
ResponseStatus
Returned status for the operation.
Return
ReturnCode
The return code indicates the return status

of the operation.
Message
string
0..1
A short message corresponding to the

return code.
ResponseStatus
389
4.1.2 CheckQuality
390
CheckQualityRequest
391
CheckQualityResponse
392
393
394
395
396
397
398
The CheckQuality operation returns a quality score for a given biometric. The biometric input is provided
in a CBEFF basic structure or CBEFF record, which in this specification is called a CBEFF-BIR. The
algorithm vendor and algorithm vendor product ID MAY be optionally provided in order to request a
particular algorithms use in calculating the biometric quality. If an algorithm vendor is provided then the
algorithm vendor product ID is REQUIRED. If no algorithm vendor is provided, the implementing system
will provide the algorithm vendor and algorithm vendor product ID that were used to calculate the
biometric quality as output parameters.
399
Request Message
Field
CheckQualityRequest
Type
Meaning
Calculate a
quality score for
a given
biometric.
20 October 2009
Page 30 of 152
Field
Type
Meaning
0..1
Common
request
parameters that
can be used to
identify the
requester.
Application
0..1
Identifies the
requesting
application.
ApplicationUser
0..1
Identifies the
user or instance
of the requesting
application.
BIASOperationName
string
0..1
Identifies the
BIAS operation
that is being
requested:
CheckQuality.
Data structure
containing a
single biometric
sample for which
a quality score is
to be
determined.
CBEFF_BIR_Type
The biometric
sample.
QualityData
0..1
Specifies a
particular
algorithm vendor
and vender
product ID.
AlgorithmVendor
VendorIdentifier
The vendor of
the quality
algorithm used
to determine the
quality score.
ProductID
The vendors ID
for the algorithm
used to
determine the
quality.
BiometricData
BIR
Quality
400
Response Message
Field
CheckQualityResponse
Type
Meaning
The response to a
CheckQuality operation.
20 October 2009
Page 31 of 152
Field
Type
Meaning
ResponseStatus
Returned status for the

operation.
Return
ReturnCode
The return code indicates

the return status of the
operation.
Message
string
0..1
A short message
corresponding to the return
code.
QualityData
Contains the quality

information for the
submitted biometric sample.
QualityScore
iso-iec19785-3-7:
Quality
0..1
The quality of a biometric

sample.
AlgorithmVendor
VendorIdentifier
The vendor of the quality

algorithm used to determine
the quality score.
ProductID
The vendors ID for the

algorithm used to determine
the quality.
AlgorithmVersion
VersionType
The version of the algorithm

used to determine the
quality.
ResponseStatus
QualityInfo
401
4.1.3 ClassifyBiometricData
402
ClassifyBiometricDataRequest
403
ClassifyBiometricDataResponse
404
405
406
The ClassifyBiometricData operation attempts to classify a biometric sample. For example, a fingerprint
biometric sample may be classified as a whorl, loop, or arch (or other classification classes and subclasses).
407
To obtain the types of classification algorithms and classes, see the QueryCapabilities operation.
408
Request Message
Field
Type
ClassifyBiometricDataRequest
Meaning
Classifies a biometric
sample.
0..1
Common request
parameters that can
be used to identify the
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
20 October 2009
Page 32 of 152
Field
BIASOperationName
BiometricData
BIR
409
Type
Meaning
string
0..1
Identifies the BIAS

requested:
ClassifyBiometricData
.
Data structure
containing a single
biometric sample for
which the classification
is to be determined.
CBEFF_BIR_Type
The biometric sample.
Response Message
Field
Type
ClassifyBiometricDataResponse
Meaning
The response to a
ClassifyBiometricData
operation, containing the
classification of a
biometric sample.
ResponseStatus

operation.
Return
ReturnCode

operation.
Message
string
0..1
A short message
corresponding to the
return code.
ClassificationData
Information on the results

and type of classification
performed.
Classification
Classification
The result of the

classification.
ClassificationAlgor
ithmType
Identifies the type of

classification algorithm
that was used to perform
the classification.
ResponseStatus
ClassificationData
410
4.1.4 CreateSubject
411
CreateSubjectRequest
412
CreateSubjectResponse
413
414
415
The CreateSubject operation creates a new subject record and associates a subject ID to that record. As
an optional parameter, the subject ID MAY be specified by the caller. If no subject ID is specified, the
CreateSubject operation will generate one.
20 October 2009
Page 33 of 152
416
Request Message
Field
Type
CreateSubjectRequest
Meaning
Y
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
CreateSubject.
417
Response Message
Field
Type
CreateSubjectResponse
Meaning
The response to a CreateSubject

operation, containing the subject ID of
the new subject record.
ResponseStatus
Return
ReturnCode
The return code indicates the return

status of the operation.
Message
string
0..1

return code.
BIASIdentity
BIASIDType
ResponseStatus
Identity
SubjectID
A system unique identifier for a subject.
418
4.1.5 DeleteBiographicData
419
DeleteBiographicDataRequest
420
DeleteBiographicDataResponse
421
422
423
The DeleteBiographicData operation erases all of the biographic data associated with a given subject
record. In the encounter-centric model the operation erases all of the biographic data associated with a
given encounter, and therefore the encounter ID MUST be specified.
424
425
426
When deleting data, BIAS implementations MAY completely erase the information in order to prevent the
ability to reconstruct a record in whole or in part, or they MAY track and record the deleted information for
auditing and/or quality control purposes.
20 October 2009
Page 34 of 152
427
Request Message
Field
Type
DeleteBiographicDataRequest
Meaning
Erase all of the

biographic data
associated with a given
subject record or, in
the encounter-centric
model, with a given
encounter.
0..1
Common request
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
DeleteBiographicData
.
BIASIdentity
SubjectID
BIASIDType
A system unique
EncounterID
BIASIDType
0..1
with the subject.
Identity
Required for
encounter-centric
models.
428
Response Message
Field
Type
DeleteBiographicDataResponse
Meaning
The response to a DeleteBiographicData

operation.
ResponseStatus
Return
ReturnCode

Message
string
0..1

return code.
ResponseStatus
429
4.1.6 DeleteBiometricData
430
DeleteBiometricDataRequest
20 October 2009
Page 35 of 152
431
DeleteBiometricDataResponse
432
433
434
The DeleteBiometricData operation erases all of the biometric data associated with a given subject
record. In the encounter-centric model the operation erases all of the biometric data associated with a
given encounter, and therefore the encounter ID MUST be specified.
435
436
437
When deleting data, BIAS implementations MAY completely erase the information in order to prevent the
ability to reconstruct a record in whole or in part, or they MAY track and record the deleted information for
auditing and/or quality control purposes.
438
Request Message
Field
Type
DeleteBiometricDataRequest
Meaning
Erase all of the

biometric data
associated with a given
subject record or, in
the encounter-centric
model, with a given
encounter.
0..1
Common request
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
DeleteBiometricData.
BIASIdentity
SubjectID
BIASIDType
A system unique
EncounterID
BIASIDType
0..1
with the subject.
Identity
Required for
encounter-centric
models.
439
Response Message
Field
Type
DeleteBiometricDataResponse
ResponseStatus
ResponseStatus
Meaning
The response to a DeleteBiometricData

operation.
20 October 2009
Page 36 of 152
Field
Type
Meaning
Return
ReturnCode

of the operation.
Message
string
0..1

return code.
440
4.1.7 DeleteSubject
441
DeleteSubjectRequest
442
DeleteSubjectResponse
443
444
445
The DeleteSubject operation deletes an existing subject record and, in an encounter-centric model, any
associated encounter information from the system. This operation also removes the subject from any
registered galleries.
446
447
448
When deleting a subject, BIAS implementations MAY completely erase the subject information in order to
prevent the ability to reconstruct a record or records in whole or in part, or they MAY track and record the
deleted information for auditing and/or quality control purposes.
449
Request Message
Field
Type
DeleteSubjectRequest
Meaning
Delete an existing
subject record and, in
an encounter-centric
model, any associated
encounter information.
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
DeleteSubject.
BIASIdentity
The identity of the

subject to delete.
BIASIDType
A system unique
Identity
SubjectID
450
Response Message
Field
Type
DeleteSubjectResponse
Meaning
The response to a DeleteSubject operation.
20 October 2009
Page 37 of 152
Field
Type
Meaning
ResponseStatus
Return
ReturnCode
The return code indicates the return status of

the operation.
Message
string
0..1
A short message corresponding to the return

code.
ResponseStatus
451
4.1.8 DeleteSubjectFromGallery
452
DeleteSubjectFromGalleryRequest
453
DeleteSubjectFromGalleryResponse
454
455
456
The DeleteSubjectFromGallery operation removes the registration of a subject from a gallery or

population group. The subject is identified by either the subject ID or the claim to identity that was
specified in the AddSubjectToGallery operation.
457
Request Message
Field
Type
DeleteSubjectFromGalleryRequest
Meaning
Remove the registration

of a subject from a
group.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
DeleteSubjectFromGall
ery.
GalleryID
BIASIDType

group from which the
subject will be deleted.
Identity
BIASIdentity
The identity to remove

from the gallery.
BIASIDType
0..1
A system unique
SubjectID
Required if an Identity
Claim is not provided.
20 October 2009
Page 38 of 152
Field
IdentityClaim
Type
Meaning
BIASIDType
0..1
population group.
Required if a Subject ID
is not provided.
458
Response Message
Field
Type
DeleteSubjectFromGalleryResponse
Meaning
The response to a
DeleteSubjectFromGallery operation.
ResponseStatus
Return
ReturnCode

Message
string
0..1
A short message corresponding to

the return code.
ResponseStatus
459
4.1.9 GetIdentifySubjectResults
460
GetIdentifySubjectResultsRequest
461
GetIdentifySubjectResultsResponse
462
463
464
465
The GetIdentifySubjectResults operation retrieves the identification results for the specified token. This
opereation is used in conjunction with the IdentifySubject operation. If the IdentifySubject operation is
implemented as an asynchronous service, the implementing system returns a token and the
GetIdentifySubjectResults operation is used to poll for the results of the original IdentifySubject request.
466
Request Message
Field
Type
GetIdentifySubjectResultsRequest
Meaning
Retrieve the
identification results for
a specified token, which
was returned by the
IdentifySubject
operation.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
20 October 2009
Page 39 of 152
Field
Type
Meaning
string
0..1
Identifies the BIAS

requested:
GetIdentifySubjectRes
ults.
TokenType
A value used to retrieve

the results of an
IdentifySubject request.
TokenValue
string
A value returned by the

implementing system
that is used to retrieve
the results to an
operation at a later
time.
Expiration
date
A date and time at

which point the token
expires and the
operation results are no
longer guaranteed to be
available.
BIASOperationName
Token
467
Response Message
Field
Type
GetIdentifySubjectResultsResponse
Meaning
The response to a
GetIdentifySubjectResults
operation, which includes a
candidate list.
ResponseStatus

operation.
Return
ReturnCode

operation.
Message
string
0..1
A short message
code.
CandidateListType
A rank-ordered list of
candidates that have a
likelihood of matching the
input biometric sample.
CandidateType
0..*
A single candidate.
Score
Score
0..1
The match score.
BiographicData
BiographicDataType
0..1
Biographic data associated

with the candidate match.
BIRList
CBEFF_BIR_ListType
Biometric data associated

ResponseStatus
CandidateList
Candidate
20 October 2009
Page 40 of 152
Field
BIR
Type
Meaning
CBEFF_BIR_Type
0..*
CBEFF structure containing

information about a
biometric sample.
468
4.1.10 IdentifySubject
469
IdentifySubjectRequest
470
IdentifySubjectResponse
471
472
The IdentifySubject operation performs an identification search against a given gallery for a given
biometric, returning a rank-ordered candidate list of a given maximum size.
473
474
475
476
477
If the IdentifySubject operation is implemented as a synchronous service, the implementing system

immediately processes the request and returns the results in the candidate list. If the IdentifySubject
operation is implemented as an asynchronous service, the implementing system returns a token, which is
an indication that the request is being handled asynchronously. In this case, the
GetIdentifySubjectResults operation is used to poll for the results of the IdentifySubject request.
478
Request Message
Field
Type
IdentifySubjectRequest
Meaning
Perform an
identification search
against a given gallery
for a given biometric.
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
IdentifySubject.
GalleryID
BIASIDType

group which will be
searched.
Identity
BIASIdentity
Contains the BIR, a

data structure
containing the
biometric sample for
the search.
An Identitys biometric
data.
BiometricData
20 October 2009
Page 41 of 152
Field
BIR
MaxListSize
479
Type
Meaning
CBEFF_BIR_Type
Contains biometric
information in either a
non-XML or an XML
representation.
positiveInteger
The maximum size of

the candidate list that
should be returned.
Response Message
Field
Type
IdentifySubjectResponse
Meaning
The response to an
IdentifySubject operation,
returning a rank-ordered
candidate list.
ResponseStatus

operation.
Return
ReturnCode

operation.
Message
string
0..1
A short message
code.
CandidateListType
0..1
A rank-ordered list of
candidates that have a
likelihood of matching the
input biometric sample (i.e.,
exceed the system
threshold).
ResponseStatus
CandidateList
Rank ordering is from

highest to lowest match
score.
Returned with successful
synchronous request
processing.
CandidateType
0..*
A single candidate.
Score
string
0..1
The match score.
BiographicData
BiographicDataType
0..1
Biographic data associated

BIRList
CBEFF_BIR_ListType
Biometric data associated

CBEFF_BIR_Type
0..*
CBEFF structure containing

information about a
biometric sample.
Candidate
BIR
20 October 2009
Page 42 of 152
Field
Token
Type
Meaning
TokenType
0..1
A token used to retrieve the

results of the
IdentifySubject operation.
Returned with
asynchronous request
processing.
480
TokenValue
string
A value returned by the

implementing system that is
used to retrieve the results
to an operation at a later
time.
Expiration
date
A date and time at which

point the token expires and
the operation results are no
longer guaranteed to be
available.
NOTES:
481
482
483
(1) In the event that the number of candidates exceeding the threshold exceeds the
MaxListSize, the system will determine which candidate is included in the last position of
the rank ordered candidate list (i.e., in the event of a tie).
484
(2) Requesters MAY NOT change the system thresholds.
485
4.1.11 ListBiographicData
486
ListBiographicDataRequest
487
ListBiographicDataResponse
488
489
490
491
492
493
494
The ListBiographicData operation lists the biographic data elements stored for a subject using the
Biographic Data Elements output parameter. Note that no actual biographic data is returned by this
operation (see the RetrieveBiographicInformation operation to obtain the biographic data). In the
encounter-centric model, an encounter ID MAY be specified to indicate that only the biographic data
elements stored for that encounter should be returned. If an encounter ID is not specified and encounter
data exists for the subject, the operation returns the list of encounter IDs which contain biographic data
using the Encounter List output parameter, and the Biographic Data Elements output parameter is empty.
495
Request Message
Field
Type
ListBiographicDataRequest
Application
Meaning
Lists the biographic

data elements stored
for a subject.
0..1
Common request
parameters that can
requester.
0..1
Identifies the
20 October 2009
Page 43 of 152
Field
Type
Meaning
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
ListBiographicData.
BIASIdentity
Identifies the subject

or, in the encountercentric model, a
subject and an
encounter.
SubjectID
BIASIDType
A system unique
EncounterID
BIASIDType
0..1
with the subject.
Type
Identity
496
Response Message
Field
ListBiographicDataResponse
Meaning
The response to a
ListBiographicData
request, containing a
list of biographic data
elements stored for a
subject. In the
encounter-centric
model, the biographic
data elements for a
specific encounter are
returned. If an
encounter ID is not
specified and
encounter data exists
for the subject, the list
of encounter IDs
which contain
biographic data is
returned.
ResponseStatus
Returned status for

the operation.
Return
ReturnCode
The return code

indicates the return
status of the
operation.
Message
string
0..1
A short message
return code.
ResponseStatus
20 October 2009
Page 44 of 152
Field
Type
Meaning
BIASIdentity
Contains a list of
biographic data
elements associated
with a subject or
encounter; non-empty
if the service was
successful,
biographic data
exists, and either (a)
the person-centric
model is being used
or (b) the encountercentric model is being
used and an
encounter identifier
was specified.
BiographicDataType
0..1
An Identitys
biographic data
elements that are
stored in the
0..*
A single biographic
data element.
Name
string
The name of the

biographic data item.
Type
string
The data type for the

biographic data item.
EncounterListType
0..1
A list of encounter
IDs associated with a
subject and which
contain biographic
data; non-empty if the
service was
successful,
biographic data
exists, the encountercentric model is being
used, and an
encounter identifier
was not specified.
BIASIDType
0..*
encounter.
Identity
BiographicDataElements
BiographicDataItem
EncounterList
EncounterID
497
4.1.12 ListBiometricData
498
ListBiometricDataRequest
499
ListBiometricDataResponse
500
501
502
The ListBiometricData operation lists the biometric data elements stored for a subject using the Biometric
Data List output parameter. Note that no actual biometric data is returned by this operation (see the
RetrieveBiometricInformation operation to obtain the biometric data). In the encounter-centric model, an
20 October 2009
Page 45 of 152
503
504
505
506
encounter ID MAY be specified to indicate that only the biometric data elements stored for that encounter
should be returned. If an encounter ID is not specified and encounter data exists for the subject, the
operation returns the list of encounter IDs which contain biometric data using the Encounter List output
parameter, and the Biometric Data List output parameter is empty.
507
508
509
510
511
An optional parameter MAY be used to indicate a filter on the list of returned data. Such a filter may
indicate that only biometric types should be listed (e.g., face, finger, iris, etc.) or that only biometric
subtypes for a particular biometric type should be listed (e.g., all fingerprints: left slap, right index, etc.). If
a filter is not specified, all biometric type and biometric subtype information are listed (e.g., left index
finger, right iris, face frontal, etc.).
512
Request Message
Field
Type
ListBiometricDataRequest
Meaning
Lists the biometric

data elements
stored for a
subject.
0..1
Common request
parameters that
can be used to
identify the
requester.
Application
0..1
Identifies the
requesting
application.
ApplicationUser
0..1
Identifies the user

or instance of the
requesting
application.
BIASOperationName
string
0..1
Identifies the BIAS

operation that is
being requested:
ListBiometricData
.
BIASIdentity
Identifies the
subject or, in the
encounter-centric
model, a subject
and an encounter.
SubjectID
BIASIDType
A system unique
identifier for a
subject.
EncounterID
BIASIDType
0..1
encounter
associated with
the subject.
ListFilterType
0..1
Indicates what
biometric
information should
be returned.
Identity
ListFilterType
20 October 2009
Page 46 of 152
Field
513
Type
Meaning
BiometricTypeFilter
iso-iec19785-3-7:Multipletypes
1..*
Limits the returned

information to a
specific type of
biometric, as
defined by CBEFF.
IncludeBiometricSubType
boolean
A Boolean flag
indicating if
biometric subtype
information should
be returned.
Response Message
Field
Type
ListBiometricDataResponse
Meaning
The response to
a
ListBiometricData
operation,
containing a list of
biometric data
elements stored
for a subject. In
the encountercentric model, the
biometric data
elements for a
specific
encounter are
returned. If an
encounter ID is
not specified and
encounter data
exists for the
subject, the list of
encounter IDs
which contain
biometric data is
returned.
ResponseStatus
Returned status
for the operation.
Return
ReturnCode
The return code

indicates the
return status of
the operation.
Message
string
0..1
A short message
corresponding to
the return code.
ResponseStatus
20 October 2009
Page 47 of 152
Field
Identity
BiometricData
BiometricDataList
Type
Meaning
BIASIdentity
0..1
Includes a list of
biometric data
elements
associated with a
subject or
encounter or a list
of encounter IDs
associated with a
subject and which
contain biometric
data.
0..1
An Identitys
biometric data.
0..1
A list of biometric
data elements.
1..*
Data structure
containing
information about
a biometric
record.
The type of
biological or
behavioral data
stored in the
biometric record,
as defined by
CBEFF.
positiveInteger
0..1
The number of
biometric records
having the
biometric type
recorded in the
biometric type
field.
iso-iec19785-3-7:Subtype
0..1
More specifically
defines the type
of biometric data
stored in the
biometric record,
as defined by
CBEFF.
BiometricDataElement
BiometricType
BiometricTypeCount
BiometricSubType
20 October 2009
Page 48 of 152
Field
Type
Meaning
BDBFormatOwner
iso-iec19785-3-7:
Registered-int
Identifies the
standards body,
working group,
industry
consortium, or
other CBEFF
biometric
organization that
has defined the
format for the
biometric data.
iso-iec19785-3-7:
Registered-int
BDBFormatType
Identifies the
specific biometric
data format
specified by the
CBEFF biometric
organization
recorded in the
BDB Format
Owner field.
EncounterListType
0..1
A list of encounter
IDs associated
with a subject and
which contain
biometric data;
non-empty if the
service was
successful,
biometric data
exists, the
encounter-centric
model is being
used, and an
encounter
identifier was not
specified.
BIASIDType
1..*
The identifier of
an encounter.
EncounterList
EncounterID
514
4.1.13 PerformFusion
515
PerformFusionRequest
516
PerformFusionResponse
517
518
519
520
The PerformFusion operation accepts either match score or match decision information and creates a
fused match result. The FusionInformationListType, through the FusionInformationType, provides specific
elements for match score input and match decision input. The fusion method and processes are left to the
20 October 2009
Page 49 of 152
521
Request Message
Field
Type
PerformFusionRequest
Meaning
Accepts either
match score or
match decision
information and
creates a fused
match result.
0..1
Common request
parameters that
can be used to
identify the
requester.
Application
0..1
Identifies the
requesting
application.
ApplicationUser
0..1
Identifies the user

or instance of the
requesting
application.
BIASOperationName
string
0..1
Identifies the BIAS

operation that is
being requested:
PerformFusion.
FusionInformationListType
Score or decision
input information to
the fusion method.
2..*
A set of fusion
information.
BiometricType
The type of
biological or
behavioral data
stored in the
biometric record, as
defined by CBEFF.
BiometricSubType
iso-iec19785-3-7:Subtype
0..1
More specifically
defines the type of
biometric data
stored in the
biometric record.
AlgorithmOwner
string
The owner or
vendor of the
algorithm used to
determine the
score or decision.
FusionInput
FusionElement
20 October 2009
Page 50 of 152
Field
Type
Meaning
AlgorithmType
string
The Algorithm
Owners identifier
for the specific
algorithm product
and version used to
determine the
score or decision.
Score
Score
0..1
The similarity score

assigned by the
matching algorithm.
Either a Score or a
Decision element
MUST be used.
string
Decision
0..1
The match decision

assigned by the
matching algorithm.
Either a Score or a
Decision element
MUST be used.
522
Response Message
Field
Type
PerformFusionResponse
Meaning
The response to the

PerformFusion operation.
ResponseStatus

operation.
Return
ReturnCode
The return code indicates the

return status of the operation.
Message
string
0..1
A short message corresponding

to the return code.
MatchType
Indicates the result of the fusion

method.
ResponseStatus
Match
523
4.1.14 QueryCapabilities
524
QueryCapabilitiesRequest
525
QueryCapabilitiesResponse
526
527
528
529
The QueryCapabilities operation returns a list of the capabilities, options, galleries, etc. that are supported
by the BIAS implementation. Refer to Annex A in the INCITS BIAS standard for conformance
requirements regarding which capability names an implementation must use in the QueryCapabilities
operation.
20 October 2009
Page 51 of 152
530
Request Message
Field
Type
QueryCapabilitiesRequest
Meaning
Returns a list of the

capabilities, options,
galleries, etc. that are
supported by the BIAS
implementation.
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
QueryCapabilities.
531
Response Message
Field
Type
QueryCapabilitiesResponse
Meaning
The response to a
QueryCapabilities
operation.
ResponseStatus
Returned status for

the operation.
Return
ReturnCode
The return code

status of the
operation.
Message
string
0..1
A short message
return code.
CapabilityListType
A list of capabilities
supported by the
BIAS
implementation.
CapabilityType
0..*
A single capability.
CapabilityName
The name of the

capability.
ResponseStatus
CapabilityList
Capability
CapabilityName
20 October 2009
Page 52 of 152
Field
Type
Meaning
CapabilityID
string
0..1
An identifier
assigned to the
capability by the
implementing
system.
CapabilityDescription
string
0..1
A description of the
capability.
CapabilityValue
string
0..1
A value assigned to
the capability.
CapabilitySupportingValue
string
0..1
A secondary value
supporting the
capability.
CapabilityAdditionalInfo
string
0..1
Contains additional
information for the
supported capability.
532
4.1.15 RetrieveBiographicInformation
533
RetrieveBiographicInformationRequest
534
RetrieveBiographicInformationResponse
535
536
537
538
539
The RetrieveBiographicInformation operation retrieves the biographic data associated with a subject ID.
In the encounter-centric model, the encounter ID MAY be specified and the operation will return the
biographic data associated with that encounter. If the encounter ID is not specified in the encountercentric model, the operation returns the biographic information associated with the most recent
encounter.
540
Request Message
Field
Type
RetrieveBiographicInformationRequest
Meaning
Retrieves the
biographic data
associated with a
subject ID.
0..1
Common request
parameters that can
be used to identify
the requester.
Application
0..1
Identifies the
requesting
application.
ApplicationUser
0..1

instance of the
requesting
application.
20 October 2009
Page 53 of 152
Field
Type
Meaning
string
0..1
Identifies the BIAS

operation that is
being requested:
RetrieveBiographicI
nformation.
BIASIdentity

subject and an
encounter.
SubjectID
BIASIDType
A system unique
identifier for a
subject.
EncounterID
BIASIDType
0..
1
encounter
associated with the
subject.
Type
BIASOperationName
Identity
541
Response Message
Field
RetrieveBiographicInformationResponse
Meaning
The response to a
RetrieveBiographicInf
ormation operation.
ResponseStatus
Returned status for

the operation.
Return
ReturnCode
The return code

status of the
operation.
Message
string
0..1
A short message
return code.
BIASIdentity
Includes the set of

biographic data
associated with a
subject.
BiographicDataType
An Identitys
biographic data.
ResponseStatus
Identity
BiographicData
One of the following

elements MUST be
present.
LastName
string
0..1
The last name of a

subject.
FirstName
string
0..1
The first name of a

subject.
20 October 2009
Page 54 of 152
Field
Type
Meaning
BiographicDataItem
0..*
A single biographic
data element.
BiographicDataSet
0..1
A set of biographic
data information.
542
4.1.16 RetrieveBiometricInformation
543
RetrieveBiometricInformationRequest
544
RetrieveBiometricInformationResponse
545
546
547
548
549
550
The RetrieveBiometricInformation operation retrieves the biometric data associated with a subject ID. In
the encounter-centric model, the encounter ID MAY be specified and the operation will return the
biometric data associated with that encounter. If the encounter ID is not specified in the encounter-centric
model, the operation returns the biometric information associated with the most recent encounter. The
operation provides an OPTIONAL input parameter to specify that only biometric data of a certain type
should be retrieved.
551
Request Message
Field
Type
RetrieveBiometricInformationRequest
Meaning
Retrieves the
biometric data
associated with a
subject ID.
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
RetrieveBiometricInfo
rmation.
BIASIdentity

subject and an
encounter.
SubjectID
BIASIDType
A system unique
EncounterID
BIASIDType
0..1
with the subject.
Identity
20 October 2009
Page 55 of 152
Field
BiometricType
552
Type
Meaning
0..1
The type of biological

or behavioral data to
retrieve.
Response Message
Field
Type
RetrieveBiometricInformationResponse
Meaning
The response to a
RetrieveBiometricInformati
on operation.
ResponseStatus

operation.
Return
ReturnCode

operation.
Message
string
0..1
A short message
return code.
BIASIdentity
Includes the biometric

data associated with a
subject.
data.
CBEFF_BIR_ListType
A list of CBEFF-BIR
elements.
CBEFF_BIR_Type
0..*
CBEFF structure
containing information
about a biometric sample.
ResponseStatus
Identity
BiometricData
BIRList
BIR
553
4.1.17 SetBiographicData
554
SetBiographicDataRequest
555
SetBiographicDataResponse
556
557
558
559
560
561
562
The SetBiographicData operation associates biographic data to a given subject record. The identity
model of the system determines whether the biographic information should replace any existing
biographic information (person-centric model) or if a new encounter should be created and associated
with the subject (encounter-centric model). For encounter-centric models, the encounter ID MAY be
specified by the caller in order to link biographic and biometric information (assuming biometric
information was previously associated using the SetBiometricData operation). If the encounter ID is
omitted for the encounter-centric model, the operation returns a system-assigned encounter ID.
20 October 2009
Page 56 of 152
563
Request Message
Field
Type
SetBiographicDataRequest
Meaning
Associates
biographic data to
a given subject
record.
0..1
Common request
parameters that
can be used to
identify the
requester.
Application
0..1
Identifies the
requesting
application.
ApplicationUser
0..1
Identifies the user

or instance of the
requesting
application.
BIASOperationName
string
0..1
Identifies the BIAS

operation that is
being requested:
SetBiographicDat
a.
BIASIdentity
Identifies the
subject or, in the
encounter-centric
model, a subject
and an encounter,
and includes the
biographic data to
store.
SubjectID
BIASIDType
A system unique
identifier for a
subject.
EncounterID
BIASIDType
0..1
encounter
associated with
the subject.
BiographicData
BiographicDataType
An Identitys
biographic data.
Identity
One of the
following elements
MUST be present.
LastName
string
0..1
The last name of a

subject.
FirstName
string
0..1
The first name of a

subject.
20 October 2009
Page 57 of 152
Field
564
Type
Meaning
BiographicDataItem
0..*
A single
biographic data
element.
BiographicDataSet
0..1
A set of biographic
data information.
Response Message
Field
Type
SetBiographicDataResponse
Meaning
The response to a SetBiographicData

operation.
ResponseStatus
Return
ReturnCode

of the operation.
Message
string
0..1

return code.
BIASIdentity
0..1
In an encounter-centric model, identifies the

encounter ID assigned to a new encounter.
BIASIDType
The identifier of an encounter associated

with the subject.
ResponseStatus
Identity
EncounterID
565
4.1.18 SetBiometricData
566
SetBiometricDataRequest
567
SetBiometricDataResponse
568
569
570
571
572
573
574
The SetBiometricData operation associates biometric data to a given subject record. The identity model
of the system determines whether the biometric information should replace any existing biometric
information (person-centric model) or if a new encounter should be created and associated with the
subject (encounter-centric model). For encounter-centric models, the encounter ID MAY be specified by
the caller in order to link biographic and biometric information (assuming biographic information was
previously associated using the SetBiographicData operation). If the encounter ID is omitted for the
encounter-centric model, the operation returns a system-assigned encounter ID.
575
Request Message
Field
Type
SetBiometricDataRequest
Application
Meaning
Associates biometric
data to a given subject
record.
0..1
Common request
requester.
0..1

application.
20 October 2009
Page 58 of 152
Field
Type
Meaning
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
SetBiometricData.
BIASIdentity
Identifies the subject or,

in the encounter-centric
model, a subject and an
encounter, and includes
the biometric data to
store.
SubjectID
BIASIDType
A system unique
EncounterID
BIASIDType
0..1
with the subject.
BiometricData
data.
CBEFF_BIR_ListType
A list of CBEFF-BIR
elements.
CBEFF_BIR_Type
1..*
CBEFF structure
containing information
about a biometric
sample.
Identity
BIRList
BIR
576
Response Message
Field
Type
SetBiometricDataResponse
Meaning
The response to a
SetBiometricData operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
BIASIdentity
0..1
In an encounter-centric model,
identifies the encounter ID
assigned to a new encounter.
BIASIDType
The identifier of an encounter

associated with the subject.
ResponseStatus
Identity
EncounterID
20 October 2009
Page 59 of 152
577
4.1.19 TransformBiometricData
578
TransformBiometricDataRequest
579
TransformBiometricDataResponse
580
581
The TransformBiometricData operation transforms or processes a given biometric in one format into a
new target format.
582
Request Message
Field
Type
TransformBiometricDataRequest
Meaning
Transforms or
processes a given
biometric in one format
into a new target
format.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
TransformBiometricDat
a.
InputBIR
CBEFF_BIR_Type
Data structure
containing the biometric
information to be
transformed.
TransformOperation
unsignedLong
Value indicating the

type of transformation
to perform.
TransformControl
string
0..1
Specifies controls for

the requested transform
operation.
Note: This could be a

compression ratio,
target data format, etc.
583
NOTE: The values for TransformOperation and TransformControl are implementation specific.
20 October 2009
Page 60 of 152
584
Response Message
Field
Type
TransformBiometricDataResponse
Meaning
The response to a
TransformBiometricData
operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1
A short message
code.
CBEFF_BIR_Type
0..1
Data structure containing the

new, transformed biometric
information.
ResponseStatus
OutputBIR
585
4.1.20 UpdateBiographicData
586
UpdateBiographicDataRequest
587
UpdateBiographicDataResponse
588
589
590
The UpdateBiographicData operation updates the biographic data for an existing subject record. The
operation replaces any existing biographic data with the new biographic data. In the encounter-centric
model, the encounter ID MUST be specified.
591
Request Message
Field
Type
UpdateBiographicDataRequest
Meaning
Updates the
biographic data for
a given subject
record.
0..1
Common request
parameters that
can be used to
identify the
requester.
Application
0..1
Identifies the
requesting
application.
ApplicationUser
0..1
Identifies the user

or instance of the
requesting
application.
BIASOperationName
string
0..1
Identifies the BIAS

operation that is
being requested:
UpdateBiographic
Data.
20 October 2009
Page 61 of 152
Field
Type
Meaning
BIASIdentity
Identifies the
subject or, in the
encounter-centric
model, a subject
and an encounter,
and includes the
biographic data to
update.
SubjectID
BIASIDType
A system unique
identifier for a
subject.
EncounterID
BIASIDType
0..1
encounter
associated with
the subject.
Identity
Required for
encounter-centric
models.
BiographicDataType
BiographicData
An Identitys
biographic data.
One of the
following elements
MUST be present.
592
LastName
string
0..1
The last name of a

subject.
FirstName
string
0..1
The first name of a

subject.
BiographicDataItem
0..*
A single
biographic data
element.
BiographicDataSet
0..1
A set of biographic
data information.
Response Message
Field
Type
UpdateBiographicDataResponse
Meaning
The response to an
UpdateBiographicData
operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
ResponseStatus
20 October 2009
Page 62 of 152
593
4.1.21 UpdateBiometricData
594
UpdateBiometricDataRequest
595
UpdateBiometricDataResponse
596
597
598
599
600
The UpdateBiometricData operation updates the biometric data for an existing subject record. The
operation includes an OPTIONAL parameter indicating if the new biometric sample should be merged
with the existing biometric sample. If this parameter is set to False or is not used in the request, the
operation replaces the existing biometric sample with the new biometric sample. In the encounter-centric
model, the encounter ID MUST be specified.
601
Request Message
Field
Type
UpdateBiometricDataRequest
Meaning
Updates a single
biometric sample for a
given subject record.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
UpdateBiometricData.
BIASIdentity
Identifies the subject or,

in the encounter-centric
model, a subject and an
encounter, and includes
the biometric data to
update.
SubjectID
BIASIDType
A system unique
EncounterID
BIASIDType
0..1
with the subject.
Identity

BiometricData
BIR
data.
CBEFF_BIR_Type
Contains biometric
information in either a
non-XML or an XML
representation.
20 October 2009
Page 63 of 152
Field
Merge
602
Type
Meaning
boolean
0..1
Value indicating if the

input biometric sample
should be merged with
any existing biometric
information.
Response Message
Field
Type
UpdateBiometricDataResponse
Meaning
The response to an
UpdateBiometricData operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
ResponseStatus
603
4.1.22 VerifySubject
604
VerifySubjectRequest
605
VerifySubjectResponse
606
607
608
The VerifySubject operation performs a 1:1 verification match between a given biometric and either a
claim to identity in a given gallery or another given biometric. As such either the Identity Claim or
Reference BIR input parameters are REQUIRED.
609
Request Message
Field
Type
VerifySubjectRequest
Meaning
Performs a 1:1
verification match
between a given
biometric and either a
claim to identity in a
given gallery or another
given biometric.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
20 October 2009
Page 64 of 152
Field
BIASOperationName
GalleryID
Type
Meaning
string
0..1
Identifies the BIAS

requested:
VerifySubject.
BIASIDType
0..1

group of which the
subject must be a
member.
Claim is provided.
Identity
IdentityClaim
BIASIdentity
Includes the identifying

information and/or input
and reference biometric
samples.
BIASIDType
0..1
population group.
Required if a Reference
BIR is not provided.
data.
InputBIR
CBEFF_BIR_Type
Maps to specific
INCITS BIAS elements
as required by that
specification.
ReferenceBIR
CBEFF_BIR_Type
0..1
Maps to specific
as required by that
specification.
BiometricData
610
Response Message
Field
Type
VerifySubjectResponse
Meaning
The response to a VerifySubject

operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
ResponseStatus
20 October 2009
Page 65 of 152
Field
Type
Meaning
Match
boolean
0..1
Indicates if the Input BIR

matched either the biometric
information associated with the
Identity Claim or the Reference
BIR.
Score
Score
0..1
The score if the biometric

information matched.
611
4.2 Aggregate Operations
612
4.2.1 Enroll
613
EnrollRequest
614
EnrollResponse
615
616
617
618
619
620
621
The Enroll operation adds a new subject or, in an encounter-centric model, a new encounter to the
system. This may be accomplished in a number of different ways according to system requirements
and/or resources. If the Enroll operation is implemented as a synchronous service, the implementing
system immediately processes the request and returns the results in the Return Data parameter. If the
Enroll operation is implemented as an asynchronous service, the implementing system returns a token in
the Return Data parameter, which is an indication that the request is being handled asynchronously. In
this case, the GetEnrollResults operation is used to poll for the results of the Enroll request.
622
Request Message
Field
Type
EnrollRequest
Meaning
Adds a new subject or,

in an encounter-centric
model, a new
encounter to the
system.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested: Enroll.
Options that guide how

the aggregate service
request is processed.
string
0..*
An option supported by
the implementing
system.
ProcessingOptions
Option
20 October 2009
Page 66 of 152
Field
InputData
623
Type
Meaning
InformationType
Contains the input data

for the operation, as
required by the
Response Message
Field
Type
EnrollResponse
Meaning
The response to an Enroll

operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
InformationType
0..1
Contains the output data for the

response.
ResponseStatus
ReturnData
624
4.2.2 GetEnrollResults
625
GetEnrollResultsRequest
626
GetEnrollResultsResponse
627
628
629
630
The GetEnrollResults operation retrieves the enrollment results for the specified token. This operation is
used in conjunction with the Enroll operation. If the Enroll operation is implemented as an asynchronous
service, the implementing system returns a token and the GetEnrollResults operation is used to poll for
the results of the original Enroll request.
631
632
If the service provider implements an asynchronous Enroll operation, then it MUST also implement the
GetEnrollResults operation.
633
Request Message
Field
Type
GetEnrollResultsRequest
Meaning
Retrieves the
enrollment results for
the specified token.
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
20 October 2009
Page 67 of 152
Field
Type
Meaning
string
0..1
Identifies the BIAS

requested:
GetEnrollResults.
TokenType
A value used to
retrieve the results of
the Enroll request.
TokenValue
string
A value returned by
the implementing
system that is used to
retrieve the results to
an operation at a later
time.
Expiration
date
A date and time at

expires and the
operation results are
no longer guaranteed
to be available.
BIASOperationName
Token
634
Response Message
Field
Type
GetEnrollResultsResponse
Meaning
The response to a
GetEnrollResults operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
InformationType
0..1

response.
ResponseStatus
ReturnData
635
4.2.3 GetIdentifyResults
636
GetIdentifyResultsRequest
637
GetIdentifyResultsResponse
638
639
640
641
The GetIdentifyResults operation retrieves the identification results for the specified token. This operation
is used in conjunction with the Identify operation. If the Identify operation is implemented as an
asynchronous service, the implementing system returns a token and the GetIdentifyResults operation is
used to poll for the results of the original Identify request.
642
643
If the service provider implements an asynchronous Identify operation, then it MUST also implement the
GetIdentifyResults operation.
644
20 October 2009
Page 68 of 152
645
Request Message
Field
Type
GetIdentifyResultsRequest
Meaning
Retrieves the
identification results for
the specified token
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
GetIdentifyResults.
TokenType
A value used to
the Identify request.
TokenValue
string
A value returned by
the implementing
time.
Expiration
date
A date and time at

expires and the
to be available.
Token
646
Response Message
Field
Type
GetIdentifyResultsResponse
Meaning
The response to a
GetIdentifyResults operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
InformationType
0..1

response.
ResponseStatus
ReturnData
20 October 2009
Page 69 of 152
647
4.2.4 GetVerifyResults
648
GetVerifyResultsRequest
649
GetVerifyResultsResponse
650
651
652
653
The GetVerifyResults operation retrieves the verification results for the specified token. This operation is
used in conjunction with the Verify operation. If the Verify operation is implemented as an asynchronous
service, the implementing system returns a token and the GetVerifyResults operation is used to poll for
the results of the original Verify request.
654
655
If the service provider implements an asynchronous Verify operation, then it MUST also implement the
GetVerifyResults operation.
656
Request Message
Field
Type
GetVerifyResultsRequest
Meaning
Retrieves the
verification results for
the specified token
0..1
Common request
parameters that can
requester.
Application
0..1
Identifies the
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
GetVerifyResults.
TokenType
A value used to
the Verify request.
TokenValue
string
A value returned by
the implementing
time.
Expiration
date
A date and time at

expires and the
to be available.
Token
20 October 2009
Page 70 of 152
657
Response Message
Field
Type
GetVerifyResultsResponse
Meaning
The response to a
GetVerifyResults operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
ReturnData
InformationType
0..1

response.
Match
boolean
0..1

BIR.
Score
Score
0..1

ResponseStatus
658
4.2.5 Identify
659
IdentifyRequest
660
IdentifyResponse
661
662
663
664
665
666
The Identify operation performs an identification function according to system requirements and/or
resources. If the Identify operation is implemented as a synchronous service, the implementing system
immediately processes the request and returns the results in the Return Data parameter. If the Identify
operation is implemented as an asynchronous service, the implementing system returns a token in the
Return Data parameter, which is an indication that the request is being handled asynchronously. In this
case, the GetIdentifyResults operation is used to poll for the results of the Identify request.
667
Request Message
Field
Type
IdentifyRequest
Meaning
Performs an
identification function.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
20 October 2009
Page 71 of 152
Field
BIASOperationName
ProcessingOptions
Option
InputData
668
Type
Meaning
string
0..1
Identifies the BIAS

requested: Identify.

string
0..*
the implementing
system.
InformationType

for the aggregate
services.
Response Message
Field
Type
IdentifyResponse
Meaning
The response to an Identify

operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
InformationType
0..1

response.
ResponseStatus
ReturnData
669
4.2.6 RetrieveInformation
670
RetrieveInformationRequest
671
RetrieveInformationResponse
672
673
674
675
676
The RetrieveInformation operation retrieves requested information about a subject, or in an encountercentric model about an encounter. In a person-centric model, this operation can be used to retrieve both
biographic and biometric information for a subject record. In an encounter-centric model, this operation
can be used to retrieve biographic and/or biometric information for either a single encounter or all
encounters. Either a subject ID or encounter ID MUST be specified.
677
Request Message
Field
Type
RetrieveInformationRequest
0..1
Meaning
Retrieves requested
information about a
subject or encounter.
Common request
requester.
20 October 2009
Page 72 of 152
Field
Type
Meaning
Application
0..1

application.
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested:
RetrieveInformation.

request is processed,
and MAY identify what
type(s) of information
should be returned.
string
0..*
the implementing
system.
BIASIdentity
Includes the identifier of

the subject or
encounter.
BIASIDType
0..1
A system unique
ProcessingOptions
Option
Identity
SubjectID
Required if an
Encounter ID is not
provided.
EncounterID
BIASIDType
0..1
with the subject.
Required if a Subject ID
is not provided.
678
Response Message
Field
Type
RetrieveInformationResponse
Meaning
Response to a
RetrieveInformation operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
InformationType
0..1

response.
ResponseStatus
ReturnData
20 October 2009
Page 73 of 152
679
4.2.7 Verify
680
VerifyRequest
681
VerifyResponse
682
683
684
685
686
687
688
The Verify operation performs a 1:1 verification function according to system requirements and/or
resources. Either the Identity Claim or Reference BIR input parameters are REQUIRED. If the Verify
operation is implemented as a synchronous service, the implementing system immediately processes the
request and returns the results in the Return Data parameter. If the Verify operation is implemented as an
asynchronous service, the implementing system returns a token in the Return Data parameter, which is
an indication that the request is being handled asynchronously. In this case, the GetVerifyResults
operation is used to poll for the results of the Verify request.
689
Request Message
Field
Type
VerifyRequest
Meaning
Performs a 1:1
verification function.
0..1
Common request
requester.
Application
0..1

application.
ApplicationUser
0..1

instance of the
BIASOperationName
string
0..1
Identifies the BIAS

requested: Verify.

string
0..*
the implementing
system.
InputData
InformationType

for the aggregate
services.
Identity
BIASIdentity
Includes either the

Identity Claim or
Reference BIR.
BIASIDType
0..1
population group.
ProcessingOptions
Option
IdentityClaim
Required if a Reference
BIR is not provided.
20 October 2009
Page 74 of 152
Field
BiometricData
ReferenceBIR
Type
Meaning
0..1
data.
CBEFF_BIR_Type
0..1
Maps to specific
as required by that
specification.
GalleryID
BIASIDType
0..1

group of which the
subject must be a
member.
Claim is provided.
690
Response Message
Field
Type
VerifyResponse
Meaning
The response to a Verify

operation.
ResponseStatus

operation.
Return
ReturnCode

Message
string
0..1

to the return code.
ReturnData
InformationType
0..1

response.
Match
boolean
0..1

BIR.
Score
Score
0..1

ResponseStatus
691
20 October 2009
Page 75 of 152
692
5 Message structure and rules
693
694
695
BIAS operations and data elements are defined in XML in the INCITS 422 BIAS standard. This OASIS
standard further specifies the full XML schema (see Annex A) and specifies how this XML is packaged
and exchanged as SOAP messages.
696
697
698
699
SOAP 1.1 messages consist of three elements: an envelope, header data, and a message body. BIAS
request-response elements MUST be enclosed within the SOAP message body. The general structure of
the BIAS SOAP message is shown in Figure 4, below. The data model for BIAS is addressed in Section 3
and BIAS messages in Section 4.
700
SOAP Envelope
SOAP Header
SOAP Body
SOAP Payload
BIAS XML Elements
701
702
Figure 4. BIAS SOAP Structure
703
704
705
706
Biometric data, regardless of native format, is carried as a binary structure. As such, options exist on how
this data is carried within the SOAP structure. It can be carried as embedded Base-64 objects or [XOP]
can be used this standard allows for either method (See section 5.3).
707
5.1 Purpose and constraints
708
709
710
This document defines a SOAP profile describing how the XML elements defined in INCITS 442 are to be
used as the payload of a SOAP message and the rules for structuring and exchanging such messages.
Philosophical tenets include:
711
SOAP messages will carry BIAS XML [XML10] payloads.
712
SOAP messages will follow WS-I and will deviate only when absolutely necessary.
713
714
Message structures and interchanges will be kept as simple as possible nice to have
features will be addressed in future revisions.
715
XML schemas will be produced based on INCITS 442.
716
BIAS will support a broad range of application domains.
717
BIAS will allow for a variety of biometric and biographic data formats to be used
718
719
Only the SOAP messaging will be defined no message protocols or client/server agents
will be defined.
20 October 2009
Page 76 of 152
720
Basic usage/formatting rules (beyond WS-I) will be defined.
721
Existing biometric and Web services standards will be leveraged wherever possible.
722
Sample WSDL and use cases will be provided as an aid in implementation.
723
724
Use of basic SOAP will allow all other compatible WS* standards (and discovery
mechanisms) to be used in conjunction with BIAS messaging.
725
726
BIAS will support both secure (i.e., using existing security mechanisms such as WSSecurity, SAML, etc,) and non-secure implementations.
727
728
Generic biometric operations will be defined use of biometrics within a Web services
authentication protocol is not addressed.
729
730
OASIS namespace rules will be followed, though some external schemas MAY also be
referenced.
731
5.2 Message requirements
732
733
734
735
BIAS SOAP messages MUST conform to [WS-I-Basic] and [WS-I-Bind]. A single BIAS SOAP message
MUST contain only one BIAS service request (or single BIAS service response). Binary components of
BIAS messages are already Base-64 encoded and therefore do not need to be conveyed as SOAP
attachments (though XOP MAY be utilized).
736
737
738
739
740
741
The system model used for BIAS conversations over SOAP is a simple request-response model. BIAS
comprises both synchronous and asynchronous operations, with the majority being of the former type.
Asynchronous operations are implemented through message pairs. That is, there are separate messages
to request the operation and to request the results of the operation. These have been defined for those
operations that are likely to take significant time to complete. For example, an identify operation can be
implemented as either a synchronous or asynchronous service as follows:
742
service provider
client
service provider
client
IdentifySubject ()
Return, CandidateList
IdentifySubject ()
Return, Token
GetIdentifySubjectResults (Token)
Return, CandidateList
743
744
(a) Synchronous Operation
(b) Asynchronous Operation
Figure 5. Example of Synchronous and Asynchronous BIAS Operations
745
746
The basic process for using SOAP for BIAS operations is:
747
748
749
750
1. A system entity acting as a BIAS requester transmits a BIAS request element within the body of a
SOAP message to a system entity acting as a BIAS responder. The BIAS requester MUST NOT
include more than one BIAS request per SOAP message or include any additional XML elements
in the SOAP body.
751
752
753
754
755
2. The BIAS responder MUST return either a BIAS response element within the body of another
SOAP message or generate a SOAP fault. The BIAS responder MUST NOT include more than
one BIAS response per SOAP message or include any additional XML elements in the SOAP
body. If a BIAS responder cannot, for some reason, process a BIAS request, it MUST generate a
SOAP fault. (SOAP 1.1 faults and fault codes are discussed in [SOAP11] section 5.1.)
756
757
3. On receiving a BIAS response in a SOAP message, the BIAS requester MUST NOT send a fault
code or other error messages to the BIAS responder. Since the format for the message
20 October 2009
Page 77 of 152
758
759
interchange is a simple request-response pattern, adding additional items such as error

conditions would needlessly complicate the protocol.
760
761
762
SOAP 1.1 also defines an optional data encoding system. This system is not used within the BIAS SOAP
binding. This means that BIAS messages can be transported using SOAP without re-encoding from the
standard BIAS schema to one based on the SOAP encoding.
763
764
765
766
NOTE: [SOAP11] references an early draft of the XML Schema specification including an
obsolete namespace. BIAS requesters SHOULD generate SOAP documents referencing only the
final XML schema namespace. BIAS responders MUST be able to process both the XML schema
namespace used in [SOAP11] as well as the final XML schema namespace.
767
5.3 Handling binary data
768
769
BIAS messages frequently contain binary data (e.g., biometric data, scanned identity documents, etc.).
Two methods are provided for dealing with this:
770
Embedded Base64 encoding
771
XOP [XOP]
772
Use of SOAP with Attachments (SWA) is deprecated.
773
5.3.1 Base64 encoding
774
775
776
This method is the default method for including binary data. Binary data is Base64 encoded and included
between the tags in the XML SOAP body for the appropriate data elements. Data elements using this
method are indicated as such in the schema.
777
778
As an example, the CBEFF_BIR_Type includes, as one of the BIR types, BinaryBIR of type
base64binary.
779
780
<xsd:element name="BinaryBIR" type="xs:base64Binary" />
781
782
783
784
785
However, even an XML_BIR as defined within [CBEFF] Part 3, contains a biometric data block (BDB)
which may be entirely binary (most common),
<xs:element name="bdb" type="xs:base64Binary" minOccurs="0"/>
786
787
or contain an element which is binary (e.g., an image within an XML BDB).
788
5.3.2 Use of XOP
789
790
791
792
When XOP is used, the binary content is replaced with a reference (URI) to an attachment (i.e., MIME)
which contains that stripped content via an xop:include. The advantage of this method is overall
message size during transmission since the overhead of the embedded Base64 is not present (since the
MIME attachment contains the native binary format).
793
794
795
Use of XOP is generally transparent to the developer, other than in how they configure their toolset. Most
frameworks support this; however, there is a possibility of mismatch if the transmitter supports and uses
XOP but the receiver does not.
796
5.4 Discovery
797
798
799
BIAS implementers (service providers) MUST provide WSDL [WSDL11] to describe their
implementations. This WSDL MAY or may not be made public via a standard discovery mechanism
(such as UDDI) or other method.
800
801
In addition, it is REQUIRED that the BIAS implementation include the QueryCapabilities operation to
provide dynamic information regarding BIAS capabilities, options, galleries, etc. that are supported.
20 October 2009
Page 78 of 152
802
5.5 Identifying operations
803
804
805
806
Receivers of BIAS SOAP messages require a method of easily identifying the operation being requested
(or response being provided). This SHOULD be possible without the receiver needing to infer it from the
sum of the elements provided within the body of the SOAP message. The BIAS SOAP profile allows for
two methods of identifying BIAS operations:
807
Explicit named element in body of the SOAP message
808
Use of WS-Addressing Action element
809
5.5.1 Operation name element
810
811
812
813
814
The BIAS message sender (requester) will include within the body of the BIAS SOAP message an XML
element <BIASOperationName>. The receiver (service provider) can search for this tag within a received
BIAS SOAP message to determine what operation is being requested. There is no requirement related to
the ordering of this element within the message, though it is RECOMMENDED that it be included early in
the message to aid in human readability.
815
An example of this method for the CreateSubject operation is shown below:
816
817
POST /bias HTTP/1.1
818
Host: www.acme.com
819
Content-Type: application/soap+xml; charset=utf-8
820
Content-Length: nnnn
821
SOAPAction:
822
<?xml version=1.0?>
823
<soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope>
824
<soap:Body>
825
826
<tns:CreateSubjectRequest
xmlns:tns=http://docs.oasisopen.org/bias/bias1.0/>
827
<tns:GenericRequestParameters>
828
<tns:Application>BIAS Application</tns:Application>
829
<tns:ApplicationUser>BIAS User</tns:ApplicationUser>
830
831
<tns:BIASOperationName>CreateSubject</tns:BIASOperationName
>
832
</tns:GenericRequestParameters>
833
<tns:Identity>
834
835
836
837
<tns:SubjectID>123456789</tns:SubjectID>
</tns:Identity>
</tns:CreateSubjectRequest>
</soap:Body>
838
</soap:Envelope>
839
5.5.2 WS-Addressing Action
840
841
842
843
844
845
WS-Addressing [WS-Addr] provides a mechanism for including action information inside any SOAP
message. The information is in the SOAP Header. The WS-Addressing Action element is used to
indicate the intent of the message. The value is a URI/IRI identifying that intent; however, there are no
restrictions on the format or specificity of the URI/IRI nor a requirement that it can be resolved. Adoption
of this option also requires that the WS-Addressing To, ReplyTo, and MessageID elements are
supplied, as they are mandatory elements in a request-reply message pattern as used within BIAS.
20 October 2009
Page 79 of 152
846
847
848
Response messages would also need to use WS-Addressing, requiring the To (matching the ReplyTo
element in the request), RelatesTo (matching the MessageID element in the request), and
RelationshipType (default value to wsa:Reply) elements.
849
850
851
852
853
Use of WS-Addressing is OPTIONAL in this profile as is this method of using the Action field for this
purpose. However, when BIAS is used within an environment using WS-Addressing, it is
RECOMMENDED that this approach for use of the Action field to carry the BIAS operation name is
employed, either alone or in combination with the BIASOperationName approach described in section
5.4.1.
854
An example for a message request for the CreateSubject operation would look like the following:
855
856
POST /bias HTTP/1.1
857
Host: www.acme.com
858
859
860
SOAPAction:
861
<?xml version=1.0?>
862
<soap:Envelope xmlns:soap=http://www.w3.org/2003/05/soap-envelope
863
864
865
xmlns:wsa=http://schemas.xmlsoap.org/ws/2004/08/addr
essing>
<soap:Header>
866
<wsa:MessageID>some-ID</wsa:MessageID>
867
<wsa:ReplyTo>
868
<wsa:Address>response-URI</wsa:Address>
869
</wsa:ReplyTo>
870
<wsa:To>destination-URI</wsa:To>
871
<wsa:Action>CreateSubject</wsa:Action>
872
</soap:Header>
873
<soap:Body>
874
875
876
877
878
xmlns:tns=http://docs.oasisopen.org/bias/bias1.0/ />
</soap:Body>
</soap:Envelope>
879
880
5.6 Security
881
882
883
884
885
The end-points that exchange SOAP messages (or handle the contents of the BIAS operations) are
expected to be protected and trusted such that message-level security mechanisms may not be required.
The use of SSL (HTTPS) or VPN technology that provides end-point to end-point security is
RECOMMENDED and MAY be sufficient in some cases. Other mechanisms such as Signed XML or
WSS [WSS] could also be implemented.
886
Unless stated otherwise, the following security statements apply to all BIAS bindings.
887
5.6.1 Use of SSL 3.0 or TLS 1.0
888
889
Unless otherwise specified, in any BIAS bindings use of SSL 3.0 [SSL3] or TLS1.0 [RFC2246], servers
MUST authenticate clients using a X.509 v3 certificate [X509]. The client MUST establish server identity
20 October 2009
Page 80 of 152
890
891
based on contents of the certificate (typically through examination of the certificates subject DN field,
subjectAltName attribute, etc.).
892
893
894
Use of transport level security in the form of SSL or TLS is OPTIONAL but highly RECOMMENDED. Use
of these mechanisms alone may not be sufficient for end-to-end integrity and confidentiality, however
(see 5.5.3 and 5.5.4 below).
895
5.6.2 Data Origin Authentication
896
897
898
899
Authentication of both the BIAS requester and the BIAS responder associated with a message is
OPTIONAL and depends on the environment of use: Authentication mechanisms available at the SOAP
message exchange layer or from the underlying substrate protocol (for example, in many bindings the
SSL/TLS or HTTP protocol) MAY be utilized to provide data origin authentication.
900
901
902
Transport authentication will not meet end-to-end origin authentication requirements in bindings where
the BIAS SOAP message passes through an intermediary in this case, message authentication is
RECOMMENDED.
903
Note that SAML [SAML] MAY be used as the mechanism for parties to authenticate to one another.
904
5.6.3 Message Integrity
905
906
907
Message integrity of both BIAS requests and BIAS responses is OPTIONAL and depends on the
environment of use. The security layer in the underlying substrate protocol or a mechanism at the SOAP
message exchange layer MAY be used to ensure message integrity.
908
909
Transport integrity will not meet end-to-end integrity requirements in bindings where the BIAS SOAP
message passes through an intermediary in this case, message integrity is RECOMMENDED.
910
5.6.4 Message Confidentiality
911
912
913
Message confidentiality of both BIAS requests and BIAS responses is OPTIONAL and depends on the
environment of use. The security layer in the underlying substrate protocol or a mechanism at the SOAP
message exchange layer MAY be used to ensure message confidentiality.
914
915
Transport confidentiality will not meet end-to-end confidentiality requirements in bindings where the BIAS
SOAP message passes through an intermediary.
916
917
NOTE: Biometric and biographic data is likely to contain personal information the confidentiality of
which SHOULD be protected accordingly. See INCITS 442, section 6.3 for further discussion.
918
5.6.5 CBEFF BIR security features
919
920
921
922
923
924
925
Within BIAS, biometric data is transferred within a CBEFF BIR (as defined in ISO/IEC 19785-1). CBEFF
provides for the optional encryption of the Biometric Data Block (BDB) of the BIR and for the integrity of
the entire BIR. If implemented, this is indicated in the BIR header. The BIR structure defines an optional
Security Block which MAY contain a digital signature (or message authentication code), encryption
parameters (e.g., key name, algorithm, etc.), and/or other security related data. Such protections are
associated with an individual BIR and are separate from any other protections provided at the message
level.
926
5.6.6 Security Considerations
927
928
929
Before deployment, each combination of authentication, message integrity, and confidentiality

mechanisms SHOULD be analyzed for vulnerability in the context of the specific protocol exchange and
the deployment environment.
930
Special care should be given to the impact of possible caching on security.
931
932
IETF RFC 2617 [RFC2617] describes possible attacks in the HTTP environment when basic or message
digest authentication schemes are used.
933
Many of the security considerations identified in [SAML SEC] MAY also apply.
20 October 2009
Page 81 of 152
934
935
936
937
ISO/IEC 19092 [BIO SEC] describes a security framework for biometric systems including a minimum set
of security requirements addressing integrity, authenticity, and confidentiality of biometric information
during transmission and storage. These SHOULD be considered as part of an overall risk management
approach.
938
939
940
941
942
NOTE: The requirements of ISO/IEC 19092, though useful across many application domains, are
required for most biometric system implementations in the financial services environment.
Application of this standard would make the requirements of sections 5.5.3 through 5.5.5
mandatory rather than optional. This is highly RECOMMENDED for any high security environment
or where privacy concerns exist.
943
5.6.7 Security of Stored Data
944
945
946
This specification does not address security considerations for stored data. It is the purview of the BIAS
service provider to implement security mechanisms and protect data at rest as per their own security
policies.
947
5.6.8 Key Management
948
949
This specification does not address key management considerations with respect to implementation of
cryptographic security mechanisms (e.g., for authenticity, integrity, or confidentiality).
950
5.7 Use with other WS* standards
951
952
953
954
955
The intent of specifying SOAP bindings for BIAS messages is to enable the full range of existing Web
services standards to be able to be applied. Some may be normative while others can be optionally
applied (i.e., WS-Security, WS-Addressing). Still others may require additional profiling to be used in an
interoperable manner (e.g., WS-Notification); this is left to a future revision. However, the intent is to avoid
specifying anything in the first, base version that would preclude the use of such standards in the future.
956
5.8 Tailoring
957
958
959
This standard provides for a common method of implementing biometric Web services; however, it does
not guarantee interoperability in a specific application. In some cases further tailoring or profiling of this
standard may be required in order to further constrain the implementation options available.
960
961
962
NOTE: As an example, BIAS allows for a number of different biographic and biometric data formats
to be used, whereas a given application/domain MAY wish to limit this to a small set or just one of
each type. Other examples (not comprehensive) include:
963
Identification of a subset of BIAS operations to be used
964
Specification of security features to be implemented (e.g., SSL, CBEFF BIR encryption, etc.)
965
Choice of operation name identification method
966
Choice of BIR type to be used (XML, non-XML, or URI)
967
Further definition of aggregate operations
968
Use (or not) of the encounter model
969
Use (or not) of asynchronous operations
970
Process sequences
971
Implementation specific values (e.g., Transform oprerations/controls)
20 October 2009
Page 82 of 152
972
6 Error handling
973
There are two levels of errors that can be returned in an error response: system and service errors.
974
975
976
977
978
979
980
System-level errors occur when the implementing system cannot service a request. They could
result due to an internal logic error or because the implementing system does not support a
particular request.
Service-level errors occur when there is a problem transmitting or representing the service
request. They could result due to an invalid service request or because of a communications
error.
The INCITS BIAS standard defines the error condition codes for system-level errors.
981
If successful, a response message (containing a return code) will be generated.
982
If unsuccessful, a SOAP fault message (containing a fault code) will be generated.
983
6.1 BIAS operation return codes
984
985
986
987
If a BIAS operation is successful, a response (service output) will be sent to the requester by the service
provider. Each response message contains a response status (see section 3.2.37) and return code (see
section 3.2.38) along with any response data as defined for that operation, if any. A response code of 0
indicates success.
988
6.2 SOAP fault codes
989
990
If a BIAS operation is unsuccessful, no BIAS response message is sent. Instead a SOAP fault message
is returned.
991
992
993
994
995
Every Web service (operation) described in the BIAS WSDL may result in a fault message that will be
returned in the response by the service provider in the event of an error. The fault message contains a
FaultCode element as defined by the SOAP 1.1 specification (see section 3.2.5). The fault message
MUST contain a Detail element in a common format, as described by the BIASFault element (see section
3.2.6).
996
997
The schema provided in Annex A defines BIASFaultCode and BIASFaultDetail types as well as
BIASFault, BIASFaultType, BIASFaultMessage and BIASFaultDescription elements.
998
999
The list of defined BIAS fault codes is provided in section 3.2.5. Note that BIAS service providers MAY
define additional fault codes unique to their service.
1000
NOTE: See also section 5.2 for additional information on message returns and faults.
20 October 2009
Page 83 of 152
1001
7 Conformance
1002
1003
1004
1005
Implementations claiming conformance to this standard, MUST implement, at a minimum, all mandatory
requirements and provisions set forth in Clauses 3, 4, 5 and 6. If such implementations claim
conformance to any OPTIONAL requirements and provisions stated in Clauses 3, 4, 5 and 6, these
requirements and provisions MUST be implemented as set forth in these Clauses.
1006
1007
1008
INCITS 442 [INCIS-BIAS] (Annex A) specifies five BIAS conformance classes. For each class, a set of
mandatory BIAS operations is identified in order for implementations (BIAS service providers) to claim
conformance. These categories are:
1009
Class 1: Full Primitive Services Implementation
1010
Class 2: Full Aggregate Services Implementation
1011
Class 3: Limited Primitive Services Implementation
1012
Class 4: Minimum Primitive Services Implementation
1013
Class 5: Minimum Aggregate Services Implementation
1014
1015
In addition, the minimum capability information to be returned in response to a Query Capabilities request
(the only mandatory BIAS operation across all 5 classes) is specified for each class.
1016
These conformance classes and their associated requirements apply to this BIAS SOAP Profile.
1017
1018
1019
There are no minimum set of operations required to be implemented by BIAS requesters; however, any
operations implemented must conform to the requirements of Clauses 3 and 4 and those requirements
within Clause 5 that are mandatory and are not specific to BIAS responders.
20 October 2009
Page 84 of 152
1020
Annex A. XML Schema
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
<?xmlversion="1.0"encoding="UTF8"?>
<wsdl:definitionsxmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:isoiec1978537="urn:oid:1.1.19785.0.257.1.7.0"
xmlns:tns="http://docs.oasisopen.org/bias/ns/bias1.0/"targetNamespace="http://docs.oasisopen.org/bias/ns/bias
1.0/">
<wsdl:types>
<xsd:schemaxmlns:xsd="http://www.w3.org/2001/XMLSchema"elementFormDefault="qualified"
targetNamespace="http://docs.oasisopen.org/bias/ns/bias1.0/">
<xsd:complexTypename="AggregateRequestTemplate"abstract="true">
<xsd:annotation>
<xsd:documentation>BasetemplateforBIASaggregateservicerequests.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extensionbase="RequestTemplate">
<xsd:sequence>
<xsd:elementname="ProcessingOptions"type="ProcessingOptionsType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Optionsthatguidehowtheaggregateservicerequestis
processed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="InputData"type="InformationType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Containstheinputdatafortheaggregateservicerequest.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexTypename="AggregateResponseTemplate"abstract="true">
<xsd:annotation>
<xsd:documentation>BasetemplateforBIASaggregateserviceresponses.</xsd:documentation>
</xsd:annotation>
<xsd:extensionbase="tns:ResponseTemplate">
<xsd:sequence>
<xsd:elementname="ReturnData"type="tns:InformationType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Containstheoutputdatafortheaggregateserviceresponse.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
<xsd:simpleTypename="ApplicationIdentifier">
20 October 2009
Page 85 of 152
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
<xsd:annotation>
<xsd:documentation>Identifiesanapplication.</xsd:documentation>
</xsd:annotation>
<xsd:restrictionbase="xsd:string">
<xsd:minLengthvalue="1"/>
<xsd:maxLengthvalue="255"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleTypename="ApplicationUserIdentifier">
<xsd:annotation>
<xsd:documentation>Identifiesanapplicationuserorinstance.</xsd:documentation>
</xsd:annotation>
<xsd:minLengthvalue="1"/>
<xsd:maxLengthvalue="255"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexTypename="BIASBiometricDataType">
<xsd:annotation>
<xsd:documentation>WrapsthevariousBIASbiometrictypes.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BIRList"type="tns:CBEFF_BIR_ListType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>AlistofCBEFFBIRelements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BIR"type="tns:CBEFF_BIR_Type"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>ContainsbiometricinformationineitheranonXMLandanXML
representation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="InputBIR"type="tns:CBEFF_BIR_Type"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>MapstospecificINCITSBIASelementsasrequiredbythat
specification.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="ReferenceBIR"type="tns:CBEFF_BIR_Type"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>MapstospecificINCITSBIASelementsasrequiredbythat
specification.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiometricDataList"type="tns:BiometricDataListType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Alistofbiometricdataelements.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="BIASFaultCode">
20 October 2009
Page 86 of 152
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
<xsd:annotation>
<xsd:documentation></xsd:documentation>
</xsd:annotation>
<xsd:restrictionbase="xsd:unsignedLong">
<xsd:enumerationvalue="UNKNOWN_ERROR">
<xsd:annotation>
<xsd:documentation>Theservicefailedforanunknownreason.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="UNSUPPORTED_CAPABILITY">
<xsd:annotation>
<xsd:documentation>Arequestedcapabilityisnotsupportedbytheservice
implementation.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="INVALID_INPUT">
<xsd:annotation>
<xsd:documentation>Thedatainaserviceinputparameterisinvalid.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="BIR_QUALITY_ERROR">
<xsd:annotation>
<xsd:documentation>Biometricsamplequalityistoopoorfortheservicetosucceed.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="INVALID_BIR">
<xsd:annotation>
<xsd:documentation>TheinputBIRisemptyorinaninvalidorunrecognizedformat.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="BIR_SIGNATURE_FAILURE">
<xsd:annotation>
<xsd:documentation>Theservicecouldnotvalidatethesignature,ifused,ontheinput
BIR.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="BIR_DECRYPTION_FAILURE">
<xsd:annotation>
<xsd:documentation>TheservicecouldnotdecryptanencryptedinputBIR.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="INVALID_ENCOUNTER_ID">
<xsd:annotation>
<xsd:documentation>TheinputencounterIDisemptyorinaninvalidformat.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="INVALID_SUBJECT_ID">
<xsd:annotation>
<xsd:documentation>TheinputsubjectIDisemptyorinaninvalidformat.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="UNKNOWN_SUBJECT">
<xsd:annotation>
20 October 2009
Page 87 of 152
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
<xsd:documentation>ThesubjectreferencedbytheinputsubjectIDdoesnotexist.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="UNKNOWN_GALLERY">
<xsd:annotation>
<xsd:documentation>ThegalleryreferencedbytheinputgalleryIDdoesnotexist.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="UNKNOWN_ENCOUNTER">
<xsd:annotation>
<xsd:documentation>TheencounterreferencedbytheinputencounterIDdoesnot
exist.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="UNKNOWN_BIOGRAPHIC_FORMAT">
<xsd:annotation>
<xsd:documentation>Thebiographicdataformatisnotknownornotsupported.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="UNKNOWN_IDENTITY_CLAIM">
<xsd:annotation>
<xsd:documentation>Theidentityreferencedbytheinputidentityclaimdoesnotexist.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="INVALID_IDENTITY_CLAIM">
<xsd:annotation>
<xsd:documentation>Theidentityclaimrequestedisalreadyinuse.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="NONEXISTANT_DATA">
<xsd:annotation>
<xsd:documentation>Thedatarequestedfordeletiondoesnotexist.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexTypename="BIASFaultDetail">
<xsd:annotation>
<xsd:documentation>DefinestheerrorinformationassociatedwithaSOAPfault.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementminOccurs="1"maxOccurs="1"name="BIASFaultType"type="tns:BIASFaultCode">
<xsd:annotation>
<xsd:documentation>Referencesanerrorcode.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementminOccurs="1"maxOccurs="1"name="BIASFaultMessage"type="xsd:string">
<xsd:annotation>
<xsd:documentation>Providesanexplanationofthefault.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementminOccurs="0"maxOccurs="1"name="BIASFaultDescription"type="xsd:string">
<xsd:annotation>
20 October 2009
Page 88 of 152
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
<xsd:documentation>ProvidesdetailedinformationaboutaBIASfault,suchastrace
details.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="BIASIdentity">
<xsd:annotation>
<xsd:documentation>
Definesasingleelementforencapsulatingthedataassociated
withanIdentity.IncludestheIdentity'sreferenceidentifiers,
biographicdata,andbiometricdata.
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="SubjectID"type="tns:BIASIDType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Asystemuniqueidentifierforasubject.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="IdentityClaim"type="tns:BIASIDType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Anidentifierbywhichasubjectisknowntoaparticulargalleryorpopulation
group.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="EncounterID"type="tns:BIASIDType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Theidentifierofanencounterassociatedwiththesubject,requiredforencounter
centricmodels.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="EncounterList"type="tns:EncounterListType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Alistofencountersassociatedwithasubject.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiographicData"type="tns:BiographicDataType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>AnIdentity'sbiographicdata.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiographicDataElements"type="tns:BiographicDataType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>AnIdentity'sbiographicdataelementsthatarestoredintheimplementing
system.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiometricData"type="tns:BIASBiometricDataType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>AnIdentity'sbiometricdata.</xsd:documentation>
</xsd:annotation>
</xsd:element>
20 October 2009
Page 89 of 152
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="BIASIDType">
<xsd:annotation>
<xsd:documentation>ABIASidentifier</xsd:documentation>
</xsd:annotation>
<xsd:restrictionbase="xsd:string"/>
</xsd:simpleType>
<xsd:complexTypename="BiographicDataItemType">
<xsd:annotation>
<xsd:documentation>Definesasinglebiographicdataelement.</xsd:documentation>
</xsd:annotation>
<xsd:sequencemaxOccurs="unbounded">
<xsd:elementname="Name"type="xsd:string"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thenameofthebiographicdataitem.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Type"type="xsd:string"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thedatatypeforthebiographicdataitem.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Value"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thevalueassignedtothebiographicdataitem.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="BiographicDataSetType">
<xsd:annotation>
<xsd:documentation>Definesasetofbiographicdatathatisformattedaccordingtothespecified
format.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:anynamespace="##any">
<xsd:annotation>
<xsd:documentation>Biographicdataformattedaccordingtoaspecificformat.</xsd:documentation>
</xsd:annotation>
</xsd:any>
</xsd:sequence>
<xsd:attributename="name"type="xsd:string"use="required">
<xsd:annotation>
<xsd:documentation>Thenameofthebiographicdataformat.Usethesenamesforcommonformats:FBIEFTS,
FBIEBTS,DODEBTS,INTI,NIEM,xNAL,HRXML.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attributename="version"type="xsd:string"use="optional">
<xsd:annotation>
<xsd:documentation>Theversionofthebiographicdataformat(e.g.,7.1forFBIEFTSor2.0for
NIEM).</xsd:documentation>
</xsd:annotation>
20 October 2009
Page 90 of 152
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
</xsd:attribute>
<xsd:attributename="source"type="xsd:string"use="required">
<xsd:annotation>
<xsd:documentation>ReferencetoaURI/IRIdescribingthebiographicdataformat.Forexample:(FBIEFTS)
www.fbibiospecs.org,(DODEBTS)www.biometrics.dod.mil,(INTI)www.interpol.int,(NIEM)www.niem.gov,(xNAL)
www.oasisopen.org,(HRXML)www.hrxml.org.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
<xsd:attributename="type"type="xsd:string"use="required">
<xsd:annotation>
<xsd:documentation>Thebiographicdataformattype.Usethesetypesforcommonformats:ASCII(e.g.,for
nonXMLversionsofFBIEFTS,FBIEBTS,DODEFTS,orINTI),XML(e.g.,forNIEM,xNAL,andHRXMLorfutureversion
ofFBIEBTS).</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexTypename="BiographicDataType">
<xsd:annotation>
<xsd:documentation>
Definesasetofbiographicdataelements,utilizingeitherthe
BiographicDataItemTypetorepresentalistofelementsorthe
BiographicDataSetTypetorepresentacomplete,formattedsetof
biographicinformation.
</xsd:annotation>
<xsd:choicemaxOccurs="unbounded">
<xsd:elementname="LastName"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thelastnameofasubject.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="FirstName"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thefirstnameofasubject.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiographicDataItem"type="tns:BiographicDataItemType"maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Asinglebiographicdataelement.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiographicDataSet"type="tns:BiographicDataSetType"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Asetofbiographicdatainformation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:complexType>
<xsd:complexTypename="BiometricDataElementType">
<xsd:annotation>
<xsd:documentation>
Providesdescriptiveinformationaboutbiometricdata,suchas
thebiometrictype,subtype,andformat,containedintheBDBof
20 October 2009
Page 91 of 152
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
theCBEFFBIR.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BiometricType"type="isoiec1978537:Multipletypes"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thetypeofbiologicalorbehavioraldatastoredinthebiometricrecord,asdefinedby
CBEFF.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiometricTypeCount"type="xsd:positiveInteger"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thenumberofbiometricrecordshavingthebiometrictyperecordedinthebiometric
typefield.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiometricSubType"type="isoiec1978537:Subtype"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Morespecificallydefinesthetypeofbiometricdatastoredinthebiometricrecord,as
definedbyCBEFF.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BDBFormatOwner"type="isoiec1978537:Registeredint"minOccurs="1"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Identifiesthestandardsbody,workinggroup,industryconsortium,orotherCBEFF
biometricorganizationthathasdefinedtheformatforthebiometricdata.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BDBFormatType"type="isoiec1978537:Registeredint"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>IdentifiesthespecificbiometricdataformatspecifiedbytheCBEFFbiometric
organizationrecordedintheBDBFormatOwnerfield.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="BiometricDataListType">
<xsd:annotation>
<xsd:documentation>Alistofbiometricdataelements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BiometricDataElement"type="tns:BiometricDataElementType"minOccurs="0"
maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Datastructurecontaininginformationaboutabiometricrecord.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="CandidateListType">
<xsd:annotation>
<xsd:documentation>
20 October 2009
Page 92 of 152
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
Definesasetofcandidates,utilizingtheCandidateTypeto
representeachelementintheset.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Candidate"type="tns:CandidateType"minOccurs="0"maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Asinglecandidate.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="CandidateType">
<xsd:annotation>
<xsd:documentation>
Definesasinglecandidateasapossiblematchinresponsetoa
biometricidentificationrequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Score"type="tns:Score"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thematchscore.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiographicData"type="tns:BiographicDataType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Biographicdataassociatedwiththecandidatematch.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BIRList"type="tns:CBEFF_BIR_ListType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Biometricdataassociatedwiththecandidatematch.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attributename="rank"type="xsd:integer"use="required">
<xsd:annotation>
<xsd:documentation>Therankofthecandidateinrelationtoothercandidatesforthesamebiometric
identificationoperation.</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
</xsd:complexType>
<xsd:complexTypename="CapabilityListType">
<xsd:annotation>
<xsd:documentation>Definesasetofcapabilities.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Capability"type="tns:CapabilityType"minOccurs="0"maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Asinglecapability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
20 October 2009
Page 93 of 152
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="CapabilityName">
<xsd:annotation>
<xsd:documentation>Alistofcapabilityitems.</xsd:documentation>
</xsd:annotation>
<xsd:enumerationvalue="AggregateInputDataOptional">
<xsd:annotation>
<xsd:documentation>Adataelementacceptedasoptionalinputbytheimplementingsystemforthe
aggregateservices.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="AggregateInputDataRequired">
<xsd:annotation>
<xsd:documentation>Adataelementrequiredasinputbytheimplementingsystemfortheaggregate
services.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="AggregateProcessingOption">
<xsd:annotation>
<xsd:documentation>Aprocessingoptionsupportedbytheimplementingsystemfortheaggregate
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="AggregateReturnData">
<xsd:annotation>
<xsd:documentation>Adataelementreturnedbytheimplementingsystemfortheaggregate
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="AggregateServiceDescription">
<xsd:annotation>
<xsd:documentation>Describestheprocessinglogicofanaggregateservicesupportedbytheimplementing
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="BiographicDataSet">
<xsd:annotation>
<xsd:documentation>Identifiesabiographicdatasetsupportedbytheimplementing
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="CBEFFPatronFormat">
<xsd:annotation>
<xsd:documentation>Apatronformatsupportedbytheimplementingsystem.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="ClassificationAlgorithmType">
<xsd:annotation>
<xsd:documentation>Aclassificationalgorithmtypesupportedbytheimplementing
</xsd:annotation>
20 October 2009
Page 94 of 152
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
</xsd:enumeration>
<xsd:enumerationvalue="ConformanceClass">
<xsd:annotation>
<xsd:documentation>IdentifiestheconformanceclassoftheBIASimplementation.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="Gallery">
<xsd:annotation>
<xsd:documentation>Agalleryorpopulationgroupsupportedbytheimplementing
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="IdentityModel">
<xsd:annotation>
<xsd:documentation>Identifieswhethertheimplementingsystemispersoncentricorencountercentric
based.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="MatchScore">
<xsd:annotation>
<xsd:documentation> Identifiestheuseofmatchscoresreturnedbytheimplementing
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="QualityAlgorithm">
<xsd:annotation>
<xsd:documentation>AqualityalgorithmvendorandalgorithmvendorproductIDsupportedbythe
implementingsystem.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="SupportedBiometric">
<xsd:annotation>
<xsd:documentation>Abiometrictypesupportedbytheimplementingsystem.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumerationvalue="TransformOperation">
<xsd:annotation>
<xsd:documentation>Atransformoperationtypesupportedbytheimplementing
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:complexTypename="CapabilityType">
<xsd:annotation>
<xsd:documentation>Definesasinglecapabilitysupportedbyanimplementingsystem.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="CapabilityName"type="tns:CapabilityName"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thenameofthecapability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
20 October 2009
Page 95 of 152
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
<xsd:elementname="CapabilityID"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Anidentifierassignedtothecapabilitybytheimplementing
</xsd:annotation>
</xsd:element>
<xsd:elementname="CapabilityDescription"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Adescriptionofthecapability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="CapabilityValue"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Avalueassignedtothecapability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="CapabilitySupportingValue"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Asecondaryvaluesupportingthecapability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="CapabilityAdditionalInfo"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation> Containsadditionalinformationforthesupportedcapability.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="CBEFF_BIR_ListType">
<xsd:annotation>
<xsd:documentation>AlistofCBEFFBIRelements.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BIR"type="tns:CBEFF_BIR_Type"minOccurs="0"maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>CBEFFstructurecontaininginformationaboutabiometricsample.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="CBEFF_BIR_Type">
<xsd:annotation>
<xsd:documentation>Representsbiometricinformation,witheitheranonXMLorXML
representation.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BIR_Information"minOccurs="0"maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:elementname="birinfo"type="isoiec1978537:BIRinfo"minOccurs="0"maxOccurs="1"/>
<xsd:elementname="bdbinfo"type="isoiec1978537:BDBinfo"minOccurs="0"maxOccurs="1"/>
<xsd:elementname="sbinfo"type="isoiec1978537:SBinfo"minOccurs="0"maxOccurs="1"/>
</xsd:sequence>
20 October 2009
Page 96 of 152
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
</xsd:complexType>
</xsd:element>
<xsd:elementname="BIR"minOccurs="1"maxOccurs="1">
<xsd:complexType>
<xsd:choiceminOccurs="1"maxOccurs="1">
<xsd:elementname="BinaryBIR"type="xs:base64Binary"/>
<xsd:elementname="URI_BIR"type="xs:anyURI"/>
<xsd:elementname="XML_BIR"type="isoiec1978537:BIR"/>
</xsd:choice>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attributename="formatowner"type="isoiec1978537:Registeredint"use="required"/>
<xsd:attributename="formattype"type="isoiec1978537:Registeredint"use="required"/>
</xsd:complexType>
<xsd:simpleTypename="Classification">
<xsd:annotation>
<xsd:documentation>Theresultofaclassification.</xsd:documentation>
</xsd:annotation>
</xsd:simpleType>
<xsd:simpleTypename="ClassificationAlgorithmType">
<xsd:annotation>
<xsd:documentation>Typeofclassificationalgorithmthatwasusedtoperformthe
classification.</xsd:documentation>
</xsd:annotation>
</xsd:simpleType>
<xsd:complexTypename="ClassificationData">
<xsd:annotation>
<xsd:documentation>Containsinformationonclassificationresultsandthealgorithmusedtodeterminethe
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Classification"type="tns:Classification"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Theresultoftheclassification.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="ClassificationAlgorithmType"type="tns:ClassificationAlgorithmType"minOccurs="1"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Identifiesthetypeofclassificationalgorithmthatwasusedtoperformthe
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="EncounterListType">
<xsd:annotation>
<xsd:documentation>Definesasetofencounters.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
20 October 2009
Page 97 of 152
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
<xsd:elementname="EncounterID"type="tns:BIASIDType"minOccurs="0"maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Theidentifierofanencounter.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="FusionInformationListType">
<xsd:annotation>
<xsd:documentation>
Containsataminimumtwosetsoffusioninput
elements,asinputtothePerformFusionrequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="FusionElement"type="tns:FusionInformationType"minOccurs="2"
<xsd:annotation>
<xsd:documentation>Asetoffusioninformation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="FusionInformationType">
<xsd:annotation>
<xsd:documentation>Representstheinformationnecessarytoperformafusion
operation.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BiometricType"type="isoiec1978537:Multipletypes"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thetypeofbiologicalorbehavioraldatastoredinthebiometricrecord,asdefinedby
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiometricSubType"type="isoiec1978537:Subtype"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Morespecificallydefinesthetypeofbiometricdatastoredinthebiometric
record.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="AlgorithmOwner"type="xsd:string"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Theownerorvendorofthealgorithmusedtodeterminethescoreor
decision.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="AlgorithmType"type="xsd:string"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>TheAlgorithmOwner'sidentifierforthespecificalgorithmproductandversionusedto
determinethescoreordecision.</xsd:documentation>
</xsd:annotation>
</xsd:element>
20 October 2009
Page 98 of 152
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
<xsd:elementname="Score"type="tns:Score">
<xsd:annotation>
<xsd:documentation>Thesimilarityscoreassignedbythematchingalgorithm.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Decision"type="xsd:string">
<xsd:annotation>
<xsd:documentation>Thematchdecisionassignedbythematchingalgorithm.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="GenericRequestParameters">
<xsd:annotation>
<xsd:documentation>Commonrequestparamtersthatcanbeusedtoidentifythe
requester.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Application"type="tns:ApplicationIdentifier"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Identifiestherequestingapplication.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="ApplicationUser"type="tns:ApplicationUserIdentifier"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Identiferstheuserorinstanceoftherequestingapplication.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname=BIASOperationNametype=xsd:stringminOccurs=0maxOccurs=1>
<xsd:annotation>
<xsd:documentation>IdentiferstheBIASoperationnamethatisbeingrequested.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="InformationType">
<xsd:annotation>
<xsd:documentation>
Allowsforanunlimitednumberofdataelementtypes,anditdoes
notspecifynorrequireanyparticulardataelement.
</xsd:annotation>
<xsd:sequence>
<xsd:anynamespace="##any"processContents="lax"minOccurs="0"maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="ListFilterType">
<xsd:annotation>
<xsd:documentation>
Providesamethodtofiltertheamountofinformationreturnedin
asearchofbiometricdata.
20 October 2009
Page 99 of 152
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="BiometricTypeFilter"type="isoiec1978537:Multipletypes"minOccurs="1"
<xsd:annotation>
<xsd:documentation>Limitsthereturnedinformationtoaspecifictypeofbiometric,asdefinedby
</xsd:annotation>
</xsd:element>
<xsd:elementname="IncludeBiometricSubtype"type="xsd:boolean"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>ABooleanflagindicatingifbiometricsubtypeinformationshouldbe
returned.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="MatchType">
<xsd:annotation>
<xsd:documentation>Theresultofafusionmethod.</xsd:documentation>
</xsd:annotation>
<xsd:restrictionbase="xsd:boolean"/>
</xsd:simpleType>
<xsd:complexTypename="ProcessingOptionsType">
<xsd:annotation>
<xsd:documentation>
BIASaggregateservicessupporttheabilitytoincludevarious
processingoptionswhichdirectandpossiblycontrolthebusiness
logicforthatservice.TheProcessingOptionsTypeprovidesa
methodtorepresentthoseoptions.Processingoptionsshouldbe
definedbytheimplementingsystem.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Option"type="xsd:string"minOccurs="0"maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>Anoptionsupportedbytheimplementingsystem.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="ProductID">
<xsd:annotation>
<xsd:documentation>Thevendor'sIDforaparticularproduct.</xsd:documentation>
</xsd:annotation>
</xsd:simpleType>
<xsd:complexTypename="QualityData">
<xsd:annotation>
<xsd:documentation>Containsinformationaboutabiometricsample'squalityandthealgorithmusedto
computethequality.</xsd:documentation>
</xsd:annotation>
20 October 2009
Page 100 of 152
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
<xsd:sequence>
<xsd:elementname="QualityScore"type="isoiec1978537:Quality"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thequalityofabiometricsample.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="AlgorithmVendor"type="tns:VendorIdentifier"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thevendorofthequaliltyalgorithmusedtodeterminethequality
score.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="AlgorithmVendorProductID"type="tns:ProductID"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thevendor'sIDforthealgorithmusedtodeterminethequality.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="AlgorithmVersion"type="tns:VersionType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Theversionofthealgorithmusedtodeterminethequality.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="RequestTemplate"abstract="true">
<xsd:annotation>
<xsd:documentation>BasetemplateforBIASprimitiveservicerequests.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="GenericRequestParameters"type="tns:GenericRequestParameters"minOccurs="0"
maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="ResponseStatus">
<xsd:sequence>
<xsd:elementname="Return"type="tns:ReturnCode"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thereturncodeindicatesthereturnstatusoftheoperation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Message"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Ashortmessagecorrespondingtothereturncode.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexTypename="ResponseTemplate"abstract="true">
<xsd:annotation>
<xsd:documentation>BasetemplateforBIASresponses.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="ResponseStatus"type="tns:ResponseStatus"minOccurs="1"maxOccurs="1">
20 October 2009
Page 101 of 152
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
<xsd:annotation>
<xsd:documentation>Returnedstatusfortheoperation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="ReturnCode">
<xsd:annotation>
<xsd:documentation>BIASOperationReturnCodes</xsd:documentation>
</xsd:annotation>
<xsd:restrictionbase="xsd:unsignedLong">
<xsd:enumerationvalue="0">
<xsd:annotation>
<xsd:documentation>Success</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleTypename="Score">
<xsd:annotation>
<xsd:documentation>Matchresultorqualityscore.</xsd:documentation>
</xsd:annotation>
<xsd:restrictionbase="xsd:float"/>
</xsd:simpleType>
<xsd:complexTypename="TokenType">
<xsd:annotation>
<xsd:documentation>Definesatokenthatisreturnedforasynchronousprocessing.</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="TokenValue"type="xsd:string"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Avaluereturnedbytheimplementingsystemthatisusedtoretrievetheresultstoa
serviceatalatertime.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Expiration"type="xsd:date"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Adateandtimeatwhichpointthetokenexpiresandtheserviceresultsarenolonger
guaranteedtobeavailable.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="VendorIdentifier">
<xsd:annotation>
<xsd:documentation>Identifiesavendor.</xsd:documentation>
</xsd:annotation>
</xsd:simpleType>
<xsd:complexTypename="Version">
<xsd:annotation>
<xsd:documentation>
Foradescriptionordefinitionofeachdataelement,seethe
20 October 2009
Page 102 of 152
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
referencedCBEFFstandardsintheCBEFF_XML_BIR_Typeschema.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="major"type="xsd:nonNegativeInteger"minOccurs="1"maxOccurs="1"/>
<xsd:elementname="minor"type="xsd:nonNegativeInteger"minOccurs="1"maxOccurs="1"/>
</xsd:sequence>
</xsd:complexType>
<xsd:simpleTypename="VersionType">
<xsd:annotation>
<xsd:documentation>Theversionofacomponent.</xsd:documentation>
</xsd:annotation>
</xsd:simpleType>
<xsd:elementname="AddSubjectToGalleryRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Registerasubjecttoagivengalleryorpopulationgroup.
</xsd:annotation>
<xsd:extensionbase="tns:RequestTemplate">
<xsd:sequence>
<xsd:elementname="GalleryID"type="tns:BIASIDType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Theidentifierofthegalleryorpopulationgrouptowhichthesubjectwillbe
added.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Identity"type="tns:BIASIdentity"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Theidentitytoaddtothegallery.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="AddSubjectToGalleryResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoanAddSubjectToGalleryrequest.
</xsd:annotation>
<xsd:extensionbase="tns:ResponseTemplate"/>
</xsd:complexType>
</xsd:element>
<xsd:elementname="CheckQualityRequest">
20 October 2009
Page 103 of 152
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Calculateaqualityscoreforagivenbiometric.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Datastructurecontainingasinglebiometricsampleforwhichaqualityscoreistobe
determined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Quality"type="tns:QualityData"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>SpecifiesaparticularalgorithmvendorandvenderproductID.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="CheckQualityResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaCheckQualityrequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="QualityInfo"type="tns:QualityData"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Containsthequalityinformationforthesubmittedbiometric
sample.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="ClassifyBiometricDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Classifiesabiometricsample.
</xsd:annotation>
20 October 2009
Page 104 of 152
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Datastructurecontainingasinglebiometricsampleforwhichtheclassificationisto
bedetermined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="ClassifyBiometricDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaClassifyBiometricDatarequest,containing
theclassificationofabiometricsample.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="ClassificationData"type="tns:ClassificationData"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Informationontheresultsandtypeofclassification
performed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="CreateSubjectRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Createanewsubjectrecord.
</xsd:annotation>
<xsd:extensionbase="tns:RequestTemplate"/>
</xsd:complexType>
</xsd:element>
<xsd:elementname="CreateSubjectResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaCreateSubjectrequest,containingthesubject
20 October 2009
Page 105 of 152
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
IDofthenewsubjectrecord.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>ContainsthesubjectIDofthenewsubjectrecord.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteBiographicDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Eraseallofthebiographicdataassociatedwithagiven
subjectrecordor,intheencountercentricmodel,witha
givenencounter.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>ContainseitherthesubjectIDorencounterIDreference.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteBiographicDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaDeleteBiographicDatarequest.
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteBiometricDataRequest">
<xsd:complexType>
<xsd:annotation>
20 October 2009
Page 106 of 152
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
<xsd:documentation>
Eraseallofthebiometricdataassociatedwithagiven
subjectrecordor,intheencountercentricmodel,witha
givenencounter.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>ContainseitherthesubjectIDorencounterIDreference.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteBiometricDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaDeleteBiometricDatarequest.
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteSubjectRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Deleteanexistingsubjectrecordand,inanencountercentric
model,anyassociatedencounterinformation.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>SubjectIDoftheidentitytodelete.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteSubjectResponse">
20 October 2009
Page 107 of 152
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaDeleteSubjectrequest.
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteSubjectFromGalleryRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Removetheregistrationofasubjectfromagalleryor
populationgroup.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Theidentifierofthegalleryorpopulationgroupfromwhichthesubjectwillbe
deleted.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Theidentitytoremovefromthegallery.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="DeleteSubjectFromGalleryResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaDeleteSubjectFromGalleryrequest.
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetIdentifySubjectResultsRequest">
<xsd:complexType>
<xsd:annotation>
20 October 2009
Page 108 of 152
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
<xsd:documentation>
Retrievetheidentificationresultsforaspecifiedtoken,
whichwasreturnedbytheIdentifySubjectservice.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Token"type="tns:TokenType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>AvalueusedtoretrievetheresultsofanIdentifySubject
request.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetIdentifySubjectResultsResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaGetIdentifySubjectResultsrequest,whichincludesacandidatelist.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="CandidateList"type="tns:CandidateListType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Arankorderedlistofcandidatesthathavealikelihoodofmatchingtheinput
biometricsample.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="IdentifySubjectRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Performanidentificationsearchagainstagivengalleryfor
agivenbiometric.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
20 October 2009
Page 109 of 152
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
<xsd:documentation>Theidentifierofthegalleryorpopulationgroupwhichwillbe
searched.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>ContainstheBIR,adatastructurecontainingthebiometricsampleforthe
search.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="MaxListSize"type="xsd:positiveInteger"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Themaximumsizeofthecandidatelistthatshouldbe
returned.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="IdentifySubjectResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoanIdentifySubjectrequest,returninga
rankorderedcandidatelist.
</xsd:annotation>
<xsd:elementname="CandidateList"type="tns:CandidateListType">
<xsd:annotation>
<xsd:documentation>Arankorderedlistofcandidatesthathavealikelihoodofmatchingtheinput
biometricsample;returnedwithsuccessfulsynchronousrequestprocessing.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Token"type="tns:TokenType">
<xsd:annotation>
<xsd:documentation>AtokenusedtoretrievetheresultsoftheIdentifySubjectrequest;returnedwith
asynchronousrequestprocessing.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:choice>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="ListBiographicDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
20 October 2009
Page 110 of 152
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
Liststhebiographicdataelementsstoredforasubject.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Identifiesthesubjector,intheencountercentricmodel,asubjectandan
encounter.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="ListBiographicDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaListBiographicDatarequest,containingalist
ofbiographicdataelementsstoredforasubject.Inthe
encountercentricmodel,thebiographicdataelementsfora
specificencounterarereturned.IfanencounterIDisnot
specifiedandencounterdataexistsforthesubject,thelist
ofencounterIDswhichcontainbiographicdataisreturned.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>
Containsalistofbiographicdataelementsassociatedwitha
subjectorencounter;nonemptyiftheservicewas
successful,biographicdataexists,andeither(a)the
personcentricmodelisbeingusedor(b)the
encountercentricmodelisbeingusedandanencounter
identifierwasspecified.
</xsd:annotation>
</xsd:element>
<xsd:elementname="EncounterList"type="tns:EncounterListType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
AlistofencounterID'sassociatedwithasubjectand
whichcontainbiographicdata;nonemptyiftheservice
wassuccessful,biographicdataexists,the
encountercentricmodelisbeingused,andanencounter
identifierwasnotspecified.
20 October 2009
Page 111 of 152
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="ListBiometricDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Liststhebiometricdataelementsstoredforasubject.Note
thatnoactualbiometricdataisreturnedbythisservice(see
theRetrieveBiometricInformationservicetoobtainthebiometric
data).
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="ListFilter"type="tns:ListFilterType"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Indicateswhatbiometricinformationshouldbereturned.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="ListBiometricDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaListBiometricDatarequest,containingalist
ofbiometricdataelementsstoredforasubject.Inthe
encountercentricmodel,thebiometricdataelementsfora
specificencounterarereturned.IfanencounterIDisnot
specifiedandencounterdataexistsforthesubject,thelist
ofencounterIDswhichcontainbiometricdataisreturned.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Identity"type="tns:BIASIdentity">
<xsd:annotation>
20 October 2009
Page 112 of 152
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
<xsd:documentation>
Includesalistofbiometricdataelementsassociated
withasubjectorencounteroralistofencounterID's
associatedwithasubjectandwhichcontainbiometric
data.
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="PerformFusionRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Acceptseithermatchscoreormatchdecisioninformationandcreatesafusedmatchresult.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="FusionInput"type="tns:FusionInformationListType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Scoreordecisioninputinformationtothefusionmethod.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="PerformFusionResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetothePerformFusionrequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Match"type="tns:MatchType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Indicatestheresultofthefusionmethod</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
20 October 2009
Page 113 of 152
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
<xsd:elementname="QueryCapabilitiesRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Returnsalistofthecapabilities,options,galleries,etc.
thataresupportedbytheBIASimplementation.
</xsd:annotation>
<xsd:extensionbase="tns:RequestTemplate"/>
</xsd:complexType>
</xsd:element>
<xsd:elementname="QueryCapabilitiesResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaQueryCapabilitiesrequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="CapabilityList"type="tns:CapabilityListType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>AlistofcapabilitiessupportedbytheBIASimplementation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="RetrieveBiographicInformationRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
RetrievesthebiographicdataassociatedwithasubjectID.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
20 October 2009
Page 114 of 152
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
</xsd:element>
<xsd:elementname="RetrieveBiographicInformationResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaRetrieveBiographicInformationrequest,
containingthebiographicdataassociatedwithasubjectID.In
theencountercentricmodel,thebiographicdataassociatedwith
aspecifiedencounterisreturned.IftheencounterIDisnot
specifiedintheencountercentricmodel,thebiographic
informationassociatedwiththemostrecentencounterisreturned.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Includesthesetofbiographicdataassociatedwithasubject.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="RetrieveBiometricInformationRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
RetrievesthebiometricdataassociatedwithasubjectID.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="BiometricType"type="isoiec1978537:Multipletypes"minOccurs="0"
maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thetypeofbiologicalorbehavioraldatatoretrieve.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
20 October 2009
Page 115 of 152
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
<xsd:elementname="RetrieveBiometricInformationResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaRetrieveBiometricInformationrequest,
containingthebiometricdataassociatedwithasubjectID.In
theencountercentricmodel,thebiometricdataassociatedwith
aspecifiedencounterisreturned.IftheencounterIDisnot
specifiedintheencountercentricmodel,thebiometric
informationassociatedwiththemostrecentencounterisreturned.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Includesthebiometricdataassociatedwithasubject.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="SetBiographicDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Associatesbiographicdatatoagivensubjectrecord.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Identifiesthesubjector,intheencountercentricmodel,asubjectandanencounter,
andincludesthebiographicdatatostore.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="SetBiographicDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaSetBiographicDatarequest.
</xsd:annotation>
20 October 2009
Page 116 of 152
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Inanencountercentricmodel,identifiestheencounterIDassignedtoanew
</xsd:annotation>
</xsd:element>
</xsd:sequence>>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="SetBiometricDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Associatesbiometricdatatoagivensubjectrecord.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
andincludesthebiometricdatatostore.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="SetBiometricDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaSetBiometricDatarequest.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Inanencountercentricmodel,identifiestheencounterIDassignedtoanew
</xsd:annotation>
</xsd:element>
</xsd:sequence>>
</xsd:extension>
20 October 2009
Page 117 of 152
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
</xsd:complexType>
</xsd:element>
<xsd:elementname="TransformBiometricDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Transformsorprocessesagivenbiometricinoneformatintoanewtargetformat.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="InputBIR"type="tns:CBEFF_BIR_Type"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Datastructurecontainingthebiometricinformationtobe
transformed.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="TransformOperation"type="xsd:unsignedLong"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Valueindicatingthetypeoftransformationtoperform.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="TransformControl"type="xsd:string"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation> Specifiescontrolsfortherequestedtransformoperation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="TransformBiometricDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoaTransformBiometricDatarequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="OutputBIR"type="tns:CBEFF_BIR_Type"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Datastructurecontainingthenew,transformedbiometric
information.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
20 October 2009
Page 118 of 152
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
</xsd:complexType>
</xsd:element>
<xsd:elementname="UpdateBiographicDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Updatesthebiographicdataforagivensubjectrecord.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
andincludesthebiographicdatatoupdate.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="UpdateBiographicDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoanUpdateBiographicDatarequest.
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="UpdateBiometricDataRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Updatesasinglebiometricsampleforagivensubjectrecord.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
andincludesthebiometricdatatoupdate.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Merge"type="xsd:boolean"minOccurs="0"maxOccurs="1">
<xsd:annotation>
20 October 2009
Page 119 of 152
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
<xsd:documentation>Valueindicatingiftheinputbiometricsampleshouldbemergedwithanyexisting
biometricinformation.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="UpdateBiometricDataResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheresponsetoanUpdateBiometricDatarequest.
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="VerifySubjectRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
Performsa1:1verificationmatchbetweenagivenbiometricand
eitheraclaimtoidentityinagivengalleryoranothergiven
biometric.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>Theidentifierofthegalleryorpopulationgroupofwhichthesubjectmustbea
member.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Includestheidentifyinginformationand/orinputandreferencebiometric
samples.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="VerifySubjectResponse">
<xsd:complexType>
<xsd:annotation>
20 October 2009
Page 120 of 152
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
<xsd:documentation>
TheresponsetoaVerifySubjectrequest.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="Match"type="xsd:boolean"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>IndicatesiftheInputBIRmatchedeitherthebiometricinformationassociatedwith
theIdentityClaimortheReferenceBIR.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Score"type="tns:Score"minOccurs="0"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Thescoreifthebiometricinformationmatched.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="EnrollRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheEnrollaggregateserviceaddsanewsubjector,inan
encountercentricmodel,anewencountertothesystem.Thismay
beaccomplishedinanumberofdifferentwaysaccordingto
systemrequirementsand/orresources.IftheEnrollaggregate
serviceisimplementedasasynchronousservice,the
implementingsystemimmediatelyprocessestherequestand
returnstheresultsintheReturnDataparameter.IftheEnroll
aggregateserviceisimplementedasanasynchronousservice,the
implementingsystemreturnsatokenintheReturnData
parameter,whichisanindicationthattherequestisbeing
handledasynchronously.Inthiscase,theGetEnrollResults
serviceisusedtopollfortheresultsoftheEnrollrequest.
</xsd:annotation>
<xsd:extensionbase="tns:AggregateRequestTemplate"/>
</xsd:complexType>
</xsd:element>
<xsd:elementname="EnrollResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoanEnrollrequest.</xsd:documentation>
</xsd:annotation>
<xsd:extensionbase="tns:AggregateResponseTemplate"/>
20 October 2009
Page 121 of 152
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetEnrollResultsRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheGetEnrollResultsaggregateserviceretrievestheenrollment
resultsforthespecifiedtoken.Thisserviceisusedin
conjunctionwiththeEnrollaggregateservice.IftheEnroll
implementingsystemreturnsatoken,andtheGetEnrollResults
serviceisusedtopollfortheresultsoftheoriginalEnroll
request.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>AvalueusedtoretrievetheresultsoftheEnrollrequest.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetEnrollResultsResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoaGetEnrollResultsrequest.</xsd:documentation>
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetIdentifyResultsRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheGetIdentifyResultsaggregateserviceretrievesthe
identificationresultsforthespecifiedtoken.Thisserviceis
usedinconjunctionwiththeIdentifyaggregateservice.Ifthe
Identifyaggregateserviceisimplementedasanasynchronous
service,theimplementingsystemreturnsatoken,andthe
GetIdentifyResultsserviceisusedtopollfortheresultsof
theoriginalIdentifyrequest.
</xsd:annotation>
20 October 2009
Page 122 of 152
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>AvalueusedtoretrievetheresultsoftheIdentifyrequest.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetIdentifyResultsResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoaGetIdentifyResultsrequest.</xsd:documentation>
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetVerifyResultsRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheGetVerifyResultsaggregateserviceretrievestheverification
resultsforthespecifiedtoken.Thisserviceisusedin
conjunctionwiththeVerifyaggregateservice.IftheVerify
implementingsystemreturnsatoken,andtheGetVerifyResults
serviceisusedtopollfortheresultsoftheoriginalVerify
request.
</xsd:annotation>
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>AvalueusedtoretrievetheresultsoftheVerifyrequest.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="GetVerifyResultsResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoaGetVerifyResultsrequest.</xsd:documentation>
</xsd:annotation>
20 October 2009
Page 123 of 152
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
<xsd:extensionbase="tns:AggregateResponseTemplate">
<xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Score"type="Score"minOccurs="0"maxOccurs="1">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="IdentifyRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheIdentifyaggregateserviceperformsanidentification
functionaccordingtosystemrequirementsand/orresources.If
theIdentifyaggregateserviceisimplementedasasynchronous
service,theimplementingsystemimmediatelyprocessesthe
requestandreturnstheresultsintheReturnDataparameter.If
theIdentifyaggregateserviceisimplementedasanasynchronous
service,theimplementingsystemreturnsatokeninthe
ReturnDataparameter,whichisanindicationthattherequestis
beinghandledasynchronously.Inthiscase,the
GetIdentifyResultsserviceisusedtopollfortheresultsof
theIdentifyrequest.
</xsd:annotation>
<xsd:extensionbase="tns:AggregateRequestTemplate"/>
</xsd:complexType>
</xsd:element>
<xsd:elementname="IdentifyResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoanIdentifyrequest.</xsd:documentation>
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="RetrieveInformationRequest">
<xsd:complexType>
20 October 2009
Page 124 of 152
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
<xsd:annotation>
<xsd:documentation>
TheRetrieveInformationaggregateserviceretrievesrequested
informationaboutasubject,orinanencountercentricmodel
aboutanencounter.Inapersoncentricmodel,thisaggregate
servicemaybeusedtoretrievebothbiographicandbiometric
informationforasubjectrecord.Inanencountercentricmodel,
thisaggregateservicemaybeusedtoretrievebiographicand/or
biometricinformationforeitherasingleencounterorall
encounters.EitheraSubjectIDorEncounterIDmustbespecified
intheIdentifyparameter.
</xsd:annotation>
<xsd:sequence>
<xsd:elementname="ProcessingOptions"type="tns:ProcessingOptionsType"minOccurs="1"maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Optionsthatguidehowtheservicerequestisprocessed,andmayidentifywhat
type(s)ofinformationshouldbereturned.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Includestheidentifierofthesubjectorencounter.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="RetrieveInformationResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoaRetrieveInformationrequest.</xsd:documentation>
</xsd:annotation>
</xsd:complexType>
</xsd:element>
<xsd:elementname="VerifyRequest">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>
TheVerifyaggregateserviceperformsa1:1verification
functionaccordingtosystemrequirementsand/orresources.
EithertheIdentityClaimorReferenceBIRinputdataelementsin
theIdentityparameterarerequired.IftheVerifyaggregate
serviceisimplementedasasynchronousservice,the
implementingsystemimmediatelyprocessestherequestandreturns
theresultsintheReturnDataparameter.IftheVerifyaggregate
20 October 2009
Page 125 of 152
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
serviceisimplementedasanasynchronousservice,the
implementingsystemreturnsatokenintheReturnDataparameter,
whichisanindicationthattherequestisbeinghandled
asynchronously.Inthiscase,theGetVerifyResultsserviceis
usedtopollfortheresultsoftheVerifyrequest.
</xsd:annotation>
<xsd:extensionbase="tns:AggregateRequestTemplate">
<xsd:sequence>
<xsd:annotation>
<xsd:documentation>IncludeseithertheIdentityClaimorReferenceBIR.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:annotation>
<xsd:documentation>Theidentifierofthegalleryorpopulationgroupofwhichthesubjectmustbea
member.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname="VerifyResponse">
<xsd:complexType>
<xsd:annotation>
<xsd:documentation>TheresponsetoaVerifyrequest.</xsd:documentation>
</xsd:annotation>
<xsd:extensionbase="tns:AggregateResponseTemplate">
<xsd:sequence>
<xsd:annotation>
</xsd:annotation>
</xsd:element>
<xsd:elementname="Score"type="Score"minOccurs="0"maxOccurs="1">
<xsd:annotation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexType>
</xsd:element>
<xsd:elementname=BIASFaulttype=tns:BIASFaultDetail/>
</xsd:schema>
</wsdl:types>
20 October 2009
Page 126 of 152
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
<wsdl:messagename="AddSubjectToGalleryRequestMessage">
<wsdl:partname="AddSubjectToGalleryRequest"element="AddSubjectToGalleryRequest"/>
</wsdl:message>
<wsdl:messagename="AddSubjectToGalleryResponseMessage">
<wsdl:partname="AddSubjectToGalleryResponse"element="AddSubjectToGalleryResponse"/>
</wsdl:message>
<wsdl:messagename="CheckQualityRequestMessage">
<wsdl:partname="CheckQualityRequest"element="CheckQualityRequest"/>
</wsdl:message>
<wsdl:messagename="CheckQualityResponseMessage">
<wsdl:partname="CheckQualityResponse"element="CheckQualityResponse"/>
</wsdl:message>
<wsdl:messagename="ClassifyBiometricDataRequestMessage">
<wsdl:partname="ClassifyBiometricDataRequest"element="ClassifyBiometricDataRequest"/>
</wsdl:message>
<wsdl:messagename="ClassifyBiometricDataResponseMessage">
<wsdl:partname="ClassifyBiometricDataResponse"element="ClassifyBiometricDataResponse"/>
</wsdl:message>
<wsdl:messagename="CreateSubjectRequestMessage">
<wsdl:partname="CreateSubjectRequest"element="CreateSubjectRequest"/>
</wsdl:message>
<wsdl:messagename="CreateSubjectResponseMessage">
<wsdl:partname="CreateSubjectResponse"element="CreateSubjectResponse"/>
</wsdl:message>
<wsdl:messagename="DeleteBiographicDataRequestMessage">
<wsdl:partname="DeleteBiographicDataRequest"element="DeleteBiographicDataRequest"/>
</wsdl:message>
<wsdl:messagename="DeleteBiographicDataResponseMessage">
<wsdl:partname="DeleteBiographicDataResponse"element="DeleteBiographicDataResponse"/>
</wsdl:message>
<wsdl:messagename="DeleteBiometricDataRequestMessage">
<wsdl:partname="DeleteBiometricDataRequest"element="DeleteBiometricDataRequest"/>
</wsdl:message>
<wsdl:messagename="DeleteBiometricDataResponseMessage">
<wsdl:partname="DeleteBiometricDataResponse"element="DeleteBiometricDataResponse"/>
</wsdl:message>
<wsdl:messagename="DeleteSubjectRequestMessage">
<wsdl:partname="DeleteSubjectRequest"element="DeleteSubjectRequest"/>
</wsdl:message>
<wsdl:messagename="DeleteSubjectResponseMessage">
<wsdl:partname="DeleteSubjectResponse"element="DeleteSubjectResponse"/>
</wsdl:message>
<wsdl:messagename="DeleteSubjectFromGalleryRequestMessage">
<wsdl:partname="DeleteSubjectFromGalleryRequest"element="DeleteSubjectFromGalleryRequest"/>
</wsdl:message>
<wsdl:messagename="DeleteSubjectFromGalleryResponseMessage">
<wsdl:partname="DeleteSubjectFromGalleryResponse"element="DeleteSubjectFromGalleryResponse"/>
</wsdl:message>
<wsdl:messagename="GetIdentifySubjectResultsRequestMessage">
<wsdl:partname="GetIdentifySubjectResultsRequest"element="GetIdentifySubjectResultsRequest"/>
</wsdl:message>
<wsdl:messagename="GetIdentifySubjectResultsResponseMessage">
<wsdl:partname="GetIdentifySubjectResultsResponse"element="GetIdentifySubjectResultsResponse"/>
20 October 2009
Page 127 of 152
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
</wsdl:message>
<wsdl:messagename="IdentifySubjectRequestMessage">
<wsdl:partname="IdentifySubjectRequest"element="IdentifySubjectRequest"/>
</wsdl:message>
<wsdl:messagename="IdentifySubjectResponseMessage">
<wsdl:partname="IdentifySubjectResponse"element="IdentifySubjectResponse"/>
</wsdl:message>
<wsdl:messagename="ListBiographicDataRequestMessage">
<wsdl:partname="ListBiographicDataRequest"element="ListBiographicDataRequest"/>
</wsdl:message>
<wsdl:messagename="ListBiographicDataResponseMessage">
<wsdl:partname="ListBiographicDataResponse"element="ListBiographicDataResponse"/>
</wsdl:message>
<wsdl:messagename="ListBiometricDataRequestMessage">
<wsdl:partname="ListBiometricDataRequest"element="ListBiometricDataRequest"/>
</wsdl:message>
<wsdl:messagename="ListBiometricDataResponseMessage">
<wsdl:partname="ListBiometricDataResponse"element="ListBiometricDataResponse"/>
</wsdl:message>
<wsdl:messagename="PerformFusionRequestMessage">
<wsdl:partname="PerformFusionRequest"element="PerformFusionRequest"/>
</wsdl:message>
<wsdl:messagename="PerformFusionResponseMessage">
<wsdl:partname="PerformFusionResponse"element="PerformFusionResponse"/>
</wsdl:message>
<wsdl:messagename="QueryCapabilitiesRequestMessage">
<wsdl:partname="QueryCapabilitiesRequest"element="QueryCapabilitiesRequest"/>
</wsdl:message>
<wsdl:messagename="QueryCapabilitiesResponseMessage">
<wsdl:partname="QueryCapabilitiesResponse"element="QueryCapabilitiesResponse"/>
</wsdl:message>
<wsdl:messagename="RetrieveBiographicInformationRequestMessage">
<wsdl:partname="RetrieveBiographicInformationRequest"element="RetrieveBiographicInformationRequest"/>
</wsdl:message>
<wsdl:messagename="RetrieveBiographicInformationResponseMessage">
<wsdl:partname="RetrieveBiographicInformationResponse"element="RetrieveBiographicInformationResponse"/>
</wsdl:message>
<wsdl:messagename="RetrieveBiometricInformationRequestMessage">
<wsdl:partname="RetrieveBiometricInformationRequest"element="RetrieveBiometricInformationRequest"/>
</wsdl:message>
<wsdl:messagename="RetrieveBiometricInformationResponseMessage">
<wsdl:partname="RetrieveBiometricInformationResponse"element="RetrieveBiometricInformationResponse"/>
</wsdl:message>
<wsdl:messagename="SetBiographicDataRequestMessage">
<wsdl:partname="SetBiographicDataRequest"element="SetBiographicDataRequest"/>
</wsdl:message>
<wsdl:messagename="SetBiographicDataResponseMessage">
<wsdl:partname="SetBiographicDataResponse"element="SetBiographicDataResponse"/>
</wsdl:message>
<wsdl:messagename="SetBiometricDataRequestMessage">
<wsdl:partname="SetBiometricDataRequest"element="SetBiometricDataRequest"/>
</wsdl:message>
<wsdl:messagename="SetBiometricDataResponseMessage">
20 October 2009
Page 128 of 152
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
<wsdl:partname="SetBiometricDataResponse"element="SetBiometricDataResponse"/>
</wsdl:message>
<wsdl:messagename="TransformBiometricDataRequestMessage">
<wsdl:partname="TransformBiometricDataRequest"element="TransformBiometricDataRequest"/>
</wsdl:message>
<wsdl:messagename="TransformBiometricDataResponseMessage">
<wsdl:partname="TransformBiometricDataResponse"element="TransformBiometricDataResponse"/>
</wsdl:message>
<wsdl:messagename="UpdateBiographicDataRequestMessage">
<wsdl:partname="UpdateBiographicDataRequest"element="UpdateBiographicDataRequest"/>
</wsdl:message>
<wsdl:messagename="UpdateBiographicDataResponseMessage">
<wsdl:partname="UpdateBiographicDataResponse"element="UpdateBiographicDataResponse"/>
</wsdl:message>
<wsdl:messagename="UpdateBiometricDataRequestMessage">
<wsdl:partname="UpdateBiometricDataRequest"element="UpdateBiometricDataRequest"/>
</wsdl:message>
<wsdl:messagename="UpdateBiometricDataResponseMessage">
<wsdl:partname="UpdateBiometricDataResponse"element="UpdateBiometricDataResponse"/>
</wsdl:message>
<wsdl:messagename="VerifySubjectRequestMessage">
<wsdl:partname="VerifySubjectRequest"element="VerifySubjectRequest"/>
</wsdl:message>
<wsdl:messagename="VerifySubjectResponseMessage">
<wsdl:partname="VerifySubjectResponse"element="VerifySubjectResponse"/>
</wsdl:message>
<wsdl:messagename="EnrollRequestMessage">
<wsdl:partname="EnrollRequest"element="EnrollRequest"/>
</wsdl:message>
<wsdl:messagename="EnrollResponseMessage">
<wsdl:partname="EnrollResponse"element="EnrollResponse"/>
</wsdl:message>
<wsdl:messagename="GetEnrollResultsRequestMessage">
<wsdl:partname="GetEnrollResultsRequest"element="GetEnrollResultsRequest"/>
</wsdl:message>
<wsdl:messagename="GetEnrollResultsResponseMessage">
<wsdl:partname="GetEnrollResultsResponse"element="GetEnrollResultsResponse"/>
</wsdl:message>
<wsdl:messagename="GetIdentifyResultsRequestMessage">
<wsdl:partname="GetIdentifyResultsRequest"element="GetIdentifyResultsRequest"/>
</wsdl:message>
<wsdl:messagename="GetIdentifyResultsResponseMessage">
<wsdl:partname="GetIdentifyResultsResponse"element="GetIdentifyResultsResponse"/>
</wsdl:message>
<wsdl:messagename="GetVerifyResultsRequestMessage">
<wsdl:partname="GetVerifyResultsRequest"element="GetVerifyResultsRequest"/>
</wsdl:message>
<wsdl:messagename="GetVerifyResultsResponseMessage">
<wsdl:partname="GetVerifyResultsResponse"element="GetVerifyResultsResponse"/>
</wsdl:message>
<wsdl:messagename="IdentifyRequestMessage">
<wsdl:partname="IdentifyRequest"element="IdentifyRequest"/>
</wsdl:message>
20 October 2009
Page 129 of 152
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
<wsdl:messagename="IdentifyResponseMessage">
<wsdl:partname="IdentifyResponse"element="IdentifyResponse"/>
</wsdl:message>
<wsdl:messagename="RetrieveInformationRequestMessage">
<wsdl:partname="RetrieveInformationRequest"element="RetrieveInformationRequest"/>
</wsdl:message>
<wsdl:messagename="RetrieveInformationResponseMessage">
<wsdl:partname="RetrieveInformationResponse"element="RetrieveInformationResponse"/>
</wsdl:message>
<wsdl:messagename="VerifyRequestMessage">
<wsdl:partname="VerifyRequest"element="VerifyRequest"/>
</wsdl:message>
<wsdl:messagename="VerifyResponseMessage">
<wsdl:partname="VerifyResponse"element="VerifyResponse"/>
</wsdl:message>
<wsdl:portTypename="BIAS_v1">
<wsdl:operationname="AddSubjectToGallery">
<wsdl:inputmessage="tns:AddSubjectToGalleryRequestMessage"name="AddSubjectToGalleryRequest"/>
<wsdl:outputmessage="tns:AddSubjectToGalleryResponseMessage"name="AddSubjectToGalleryResponse"/>
</wsdl:operation>
<wsdl:operationname="CheckQuality">
<wsdl:inputmessage="tns:CheckQualityRequestMessage"name="CheckQualityRequest"/>
<wsdl:outputmessage="tns:CheckQualityResponseMessage"name="CheckQualityResponse"/>
</wsdl:operation>
<wsdl:operationname="ClassifyBiometricData">
<wsdl:inputmessage="tns:ClassifyBiometricDataRequestMessage"name="ClassifyBiometricDataRequest"/>
<wsdl:outputmessage="tns:ClassifyBiometricDataResponseMessage"name="ClassifyBiometricDataResponse"/>
</wsdl:operation>
<wsdl:operationname="CreateSubject">
<wsdl:inputmessage="tns:CreateSubjectRequestMessage"name="CreateSubjectRequest"/>
<wsdl:outputmessage="tns:CreateSubjectResponseMessage"name="CreateSubjectResponse"/>
</wsdl:operation>
<wsdl:operationname="DeleteBiographicData">
<wsdl:inputmessage="tns:DeleteBiographicDataRequestMessage"name="DeleteBiographicDataRequest"/>
<wsdl:outputmessage="tns:DeleteBiographicDataResponseMessage"name="DeleteBiographicDataResponse"/>
</wsdl:operation>
<wsdl:operationname="DeleteBiometricData">
<wsdl:inputmessage="tns:DeleteBiometricDataRequestMessage"name="DeleteBiometricDataRequest"/>
<wsdl:outputmessage="tns:DeleteBiometricDataResponseMessage"name="DeleteBiometricDataResponse"/>
</wsdl:operation>
<wsdl:operationname="DeleteSubject">
<wsdl:inputmessage="tns:DeleteSubjectRequestMessage"name="DeleteSubjectRequest"/>
<wsdl:outputmessage="tns:DeleteSubjectResponseMessage"name="DeleteSubjectResponse"/>
</wsdl:operation>
<wsdl:operationname="DeleteSubjectFromGallery">
<wsdl:inputmessage="tns:DeleteSubjectFromGalleryRequestMessage"name="DeleteSubjectFromGalleryRequest"
/>
<wsdl:outputmessage="tns:DeleteSubjectFromGalleryResponseMessage"
name="DeleteSubjectFromGalleryResponse"/>
</wsdl:operation>
<wsdl:operationname="GetIdentifySubjectResults">
<wsdl:inputmessage="tns:GetIdentifySubjectResultsRequestMessage"name="GetIdentifySubjectResultsRequest"
/>
20 October 2009
Page 130 of 152
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
<wsdl:outputmessage="tns:GetIdentifySubjectResultsResponseMessage"
name="GetIdentifySubjectResultsResponse"/>
</wsdl:operation>
<wsdl:operationname="IdentifySubject">
<wsdl:inputmessage="tns:IdentifySubjectRequestMessage"name="IdentifySubjectRequest"/>
<wsdl:outputmessage="tns:IdentifySubjectResponseMessage"name="IdentifySubjectResponse"/>
</wsdl:operation>
<wsdl:operationname="ListBiographicData">
<wsdl:inputmessage="tns:ListBiographicDataRequestMessage"name="ListBiographicDataRequest"/>
<wsdl:outputmessage="tns:ListBiographicDataResponseMessage"name="ListBiographicDataResponse"/>
</wsdl:operation>
<wsdl:operationname="ListBiometricData">
<wsdl:inputmessage="tns:ListBiometricDataRequestMessage"name="ListBiometricDataRequest"/>
<wsdl:outputmessage="tns:ListBiometricDataResponseMessage"name="ListBiometricDataResponse"/>
</wsdl:operation>
<wsdl:operationname="PerformFusion">
<wsdl:inputmessage="tns:PerformFusionRequestMessage"name="PerformFusionRequest"/>
<wsdl:outputmessage="tns:PerformFusionResponseMessage"name="PerformFusionResponse"/>
</wsdl:operation>
<wsdl:operationname="QueryCapabilities">
<wsdl:inputmessage="tns:QueryCapabilitiesRequestMessage"name="QueryCapabilitiesRequest"/>
<wsdl:outputmessage="tns:QueryCapabilitiesResponseMessage"name="QueryCapabilitiesResponse"/>
</wsdl:operation>
<wsdl:operationname="RetrieveBiographicInformation">
<wsdl:inputmessage="tns:RetrieveBiographicInformationRequestMessage"
name="RetrieveBiographicInformationRequest"/>
<wsdl:outputmessage="tns:RetrieveBiographicInformationResponseMessage"
name="RetrieveBiographicInformationResponse"/>
</wsdl:operation>
<wsdl:operationname="RetrieveBiometricInformation">
<wsdl:inputmessage="tns:RetrieveBiometricInformationRequestMessage"
name="RetrieveBiometricInformationRequest"/>
<wsdl:outputmessage="tns:RetrieveBiometricInformationResponseMessage"
name="RetrieveBiometricInformationResponse"/>
</wsdl:operation>
<wsdl:operationname="SetBiographicData">
<wsdl:inputmessage="tns:SetBiographicDataRequestMessage"name="SetBiographicDataRequest"/>
<wsdl:outputmessage="tns:SetBiographicDataResponseMessage"name="SetBiographicDataResponse"/>
</wsdl:operation>
<wsdl:operationname="SetBiometricData">
<wsdl:inputmessage="tns:SetBiometricDataRequestMessage"name="SetBiometricDataRequest"/>
<wsdl:outputmessage="tns:SetBiometricDataResponseMessage"name="SetBiometricDataResponse"/>
</wsdl:operation>
<wsdl:operationname="TransformBiometricData">
<wsdl:inputmessage="tns:TransformBiometricDataRequestMessage"name="TransformBiometricDataRequest"/>
<wsdl:outputmessage="tns:TransformBiometricDataResponseMessage"
name="TransformBiometricDataResponse"/>
</wsdl:operation>
<wsdl:operationname="UpdateBiographicData">
<wsdl:inputmessage="tns:UpdateBiographicDataRequestMessage"name="UpdateBiographicDataRequest"/>
<wsdl:outputmessage="tns:UpdateBiographicDataResponseMessage"name="UpdateBiographicDataResponse"/>
</wsdl:operation>
<wsdl:operationname="UpdateBiometricData">
20 October 2009
Page 131 of 152
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
<wsdl:inputmessage="tns:UpdateBiometricDataRequestMessage"name="UpdateBiometricDataRequest"/>
<wsdl:outputmessage="tns:UpdateBiometricDataResponseMessage"name="UpdateBiometricDataResponse"/>
</wsdl:operation>
<wsdl:operationname="VerifySubject">
<wsdl:inputmessage="tns:VerifySubjectRequestMessage"name="VerifySubjectRequest"/>
<wsdl:outputmessage="tns:VerifySubjectResponseMessage"name="VerifySubjectResponse"/>
</wsdl:operation>
<wsdl:operationname="Enroll">
<wsdl:inputmessage="tns:EnrollRequestMessage"name="EnrollRequest"/>
<wsdl:outputmessage="tns:EnrollResponseMessage"name="EnrollResponse"/>
</wsdl:operation>
<wsdl:operationname="GetEnrollResults">
<wsdl:inputmessage="tns:GetEnrollResultsRequestMessage"name="GetEnrollResultsRequest"/>
<wsdl:outputmessage="tns:GetEnrollResultsResponseMessage"name="GetEnrollResultsResponse"/>
</wsdl:operation>
<wsdl:operationname="GetIdentifyResults">
<wsdl:inputmessage="tns:GetIdentifyResultsRequestMessage"name="GetIdentifyResultsRequest"/>
<wsdl:outputmessage="tns:GetIdentifyResultsResponseMessage"name="GetIdentifyResultsResponse"/>
</wsdl:operation>
<wsdl:operationname="GetVerifyResults">
<wsdl:inputmessage="tns:GetVerifyResultsRequestMessage"name="GetVerifyResultsRequest"/>
<wsdl:outputmessage="tns:GetVerifyResultsResponseMessage"name="GetVerifyResultsResponse"/>
</wsdl:operation>
<wsdl:operationname="Identify">
<wsdl:inputmessage="tns:IdentifyRequestMessage"name="IdentifyRequest"/>
<wsdl:outputmessage="tns:IdentifyResponseMessage"name="IdentifyResponse"/>
</wsdl:operation>
<wsdl:operationname="RetrieveInformation">
<wsdl:inputmessage="tns:RetrieveInformationRequestMessage"name="RetrieveInformationRequest"/>
<wsdl:outputmessage="tns:RetrieveInformationResponseMessage"name="RetrieveInformationResponse"/>
</wsdl:operation>
<wsdl:operationname="Verify">
<wsdl:inputmessage="tns:VerifyRequestMessage"name="VerifyRequest"/>
<wsdl:outputmessage="tns:VerifyResponseMessage"name="VerifyResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:bindingtype="tns:BIAS_v1"name="BIAS_v1HttpBinding">
<soap:bindingstyle="document"transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operationname="AddSubjectToGallery">
<soap:operationsoapAction="AddSubjectToGallery"/>
<wsdl:inputname="AddSubjectToGalleryRequest">
<soap:bodyuse="literal"/>
</wsdl:input>
<wsdl:outputname="AddSubjectToGalleryResponse">
</wsdl:output>
<wsdl:faultname=BIASFault>
<soap:faultname=BIASFaultuse=literal/>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="CheckQuality">
<soap:operationsoapAction="CheckQuality"/>
<wsdl:inputname="CheckQualityRequest">
20 October 2009
Page 132 of 152
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
</wsdl:input>
<wsdl:outputname="CheckQualityResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="ClassifyBiometricData">
<soap:operationsoapAction="ClassifyBiometricData"/>
<wsdl:inputname="ClassifyBiometricDataRequest">
</wsdl:input>
<wsdl:outputname="ClassifyBiometricDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="CreateSubject">
<soap:operationsoapAction="CreateSubject"/>
<wsdl:inputname="CreateSubjectRequest">
</wsdl:input>
<wsdl:outputname="CreateSubjectResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="DeleteBiographicData">
<soap:operationsoapAction="DeleteBiographicData"/>
<wsdl:inputname="DeleteBiographicDataRequest">
</wsdl:input>
<wsdl:outputname="DeleteBiographicDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="DeleteBiometricData">
<soap:operationsoapAction="DeleteBiometricData"/>
<wsdl:inputname="DeleteBiometricDataRequest">
</wsdl:input>
<wsdl:outputname="DeleteBiometricDataResponse">
</wsdl:output>
20 October 2009
Page 133 of 152
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="DeleteSubject">
<soap:operationsoapAction="DeleteSubject"/>
<wsdl:inputname="DeleteSubjectRequest">
</wsdl:input>
<wsdl:outputname="DeleteSubjectResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="DeleteSubjectFromGallery">
<soap:operationsoapAction="DeleteSubjectFromGallery"/>
<wsdl:inputname="DeleteSubjectFromGalleryRequest">
</wsdl:input>
<wsdl:outputname="DeleteSubjectFromGalleryResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="GetIdentifySubjectResults">
<soap:operationsoapAction="GetIdentifySubjectResults"/>
<wsdl:inputname="GetIdentifySubjectResultsRequest">
</wsdl:input>
<wsdl:outputname="GetIdentifySubjectResultsResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="IdentifySubject">
<soap:operationsoapAction="IdentifySubject"/>
<wsdl:inputname="IdentifySubjectRequest">
</wsdl:input>
<wsdl:outputname="IdentifySubjectResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="ListBiographicData">
20 October 2009
Page 134 of 152
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
<soap:operationsoapAction="ListBiographicData"/>
<wsdl:inputname="ListBiographicDataRequest">
</wsdl:input>
<wsdl:outputname="ListBiographicDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="ListBiometricData">
<soap:operationsoapAction="ListBiometricData"/>
<wsdl:inputname="ListBiometricDataRequest">
</wsdl:input>
<wsdl:outputname="ListBiometricDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="PerformFusion">
<soap:operationsoapAction="PerformFusion"/>
<wsdl:inputname="PerformFusionRequest">
</wsdl:input>
<wsdl:outputname="PerformFusionResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="QueryCapabilities">
<soap:operationsoapAction="QueryCapabilities"/>
<wsdl:inputname="QueryCapabilitiesRequest">
</wsdl:input>
<wsdl:outputname="QueryCapabilitiesResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="RetrieveBiographicInformation">
<soap:operationsoapAction="RetrieveBiographicInformation"/>
<wsdl:inputname="RetrieveBiographicInformationRequest">
</wsdl:input>
<wsdl:outputname="RetrieveBiographicInformationResponse">
20 October 2009
Page 135 of 152
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="RetrieveBiometricInformation">
<soap:operationsoapAction="RetrieveBiometricInformation"/>
<wsdl:inputname="RetrieveBiometricInformationRequest">
</wsdl:input>
<wsdl:outputname="RetrieveBiometricInformationResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="SetBiographicData">
<soap:operationsoapAction="SetBiographicData"/>
<wsdl:inputname="SetBiographicDataRequest">
</wsdl:input>
<wsdl:outputname="SetBiographicDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="SetBiometricData">
<soap:operationsoapAction="SetBiometricData"/>
<wsdl:inputname="SetBiometricDataRequest">
</wsdl:input>
<wsdl:outputname="SetBiometricDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="TransformBiometricData">
<soap:operationsoapAction="TransformBiometricData"/>
<wsdl:inputname="TransformBiometricDataRequest">
</wsdl:input>
<wsdl:outputname="TransformBiometricDataResponse">
</wsdl:output>
</wsdl:fault>
20 October 2009
Page 136 of 152
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
</wsdl:operation>
<wsdl:operationname="UpdateBiographicData">
<soap:operationsoapAction="UpdateBiographicData"/>
<wsdl:inputname="UpdateBiographicDataRequest">
</wsdl:input>
<wsdl:outputname="UpdateBiographicDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="UpdateBiometricData">
<soap:operationsoapAction="UpdateBiometricData"/>
<wsdl:inputname="UpdateBiometricDataRequest">
</wsdl:input>
<wsdl:outputname="UpdateBiometricDataResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="VerifySubject">
<soap:operationsoapAction="VerifySubject"/>
<wsdl:inputname="VerifySubjectRequest">
</wsdl:input>
<wsdl:outputname="VerifySubjectResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="Enroll">
<soap:operationsoapAction="Enroll"/>
<wsdl:inputname="EnrollRequest">
</wsdl:input>
<wsdl:outputname="EnrollResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="GetEnrollResults">
<soap:operationsoapAction="GetEnrollResults"/>
<wsdl:inputname="GetEnrollResultsRequest">
20 October 2009
Page 137 of 152
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
</wsdl:input>
<wsdl:outputname="GetEnrollResultsResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="GetIdentifyResults">
<soap:operationsoapAction="GetIdentifyResults"/>
<wsdl:inputname="GetIdentifyResultsRequest">
</wsdl:input>
<wsdl:outputname="GetIdentifyResultsResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="GetVerifyResults">
<soap:operationsoapAction="GetVerifyResults"/>
<wsdl:inputname="GetVerifyResultsRequest">
</wsdl:input>
<wsdl:outputname="GetVerifyResultsResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="Identify">
<soap:operationsoapAction="Identify"/>
<wsdl:inputname="IdentifyRequest">
</wsdl:input>
<wsdl:outputname="IdentifyResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="RetrieveInformation">
<soap:operationsoapAction="RetrieveInformation"/>
<wsdl:inputname="RetrieveInformationRequest">
</wsdl:input>
<wsdl:outputname="RetrieveInformationResponse">
</wsdl:output>
20 October 2009
Page 138 of 152
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
</wsdl:fault>
</wsdl:operation>
<wsdl:operationname="Verify">
<soap:operationsoapAction="Verify"/>
<wsdl:inputname="VerifyRequest">
</wsdl:input>
<wsdl:outputname="VerifyResponse">
</wsdl:output>
</wsdl:fault>
</wsdl:operation>
</wsdl:binding>
<wsdl:servicename="BIAS_v1">
<wsdl:portname="BIAS_v1HttpBindingPort"binding="tns:BIAS_v1HttpBinding">
<soap:addresslocation="http://your_URI/IRI_to_your_BIAS_implementation"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
20 October 2009
Page 139 of 152
3902
Annex B. Use Cases (non-normative)
3903
3904
3905
The intent of this annex is to provide operational sequence diagrams / flow charts that show how the
higher level usage scenarios within [INCITS-BIAS] could be implemented using the BIAS SOAP profile.
The following use cases are given:
3906
Verification (synchronous/aggregate)
3907
Verification (asynchronous/aggregate)
3908
Verification (primitive)
3909
Identification (primitive)
3910
Enrollment (aggregate)
3911
Enrollment (primitive)
3912
B.1 Verification Use Case
3913
3914
3915
This use case uses the aggregate Verify operation in which a single request results in some set of
operations (in this case, a series of primitive BIAS operations) being performed by the BIAS service
provider.
3916
3917
3918
20 October 2009
Page 140 of 152
3919
B.2 Asynchronous Verification
3920
3921
In this use case, the requester issues two requests the BIAS Verify request to initiate the operation
followed by a BIAS GetVerifyResult request to retrieve the results of that operation.
3922
Client Application
BIAS Client
BIAS Server Agent
BIAS Impl
Verify
Verify
Verify
ReturnToken
CheckQuality
VerifySubject
MatchDecision
Periodically Polling
GetVerfiyResult
MatchDecision
MatchDecision
Note that
1. CheckQuality, TransformBiometricData, VerifySubject can be exposed as interfaces of BIAS server agent.
3923
3924
3925
20 October 2009
Page 141 of 152
3926
B.3 Primitive Verification
3927
3928
3929
In this use case, the verification operation is performed as a series of requests using the BIAS primitive
operations. In this case, the client rather than the service provider controls the workflow of the higher
level operation.
3930
3931
3932
20 October 2009
Page 142 of 152
3933
B.4 Identification Use Case
3934
3935
3936
This use case uses the aggregate Identify operation in which a single request results in some set of
provider.
3937
3938
3939
3940
3941
20 October 2009
Page 143 of 152
3942
B.5 Biometric Enrollment
3943
3944
3945
This use case uses the aggregate Enroll operation in which a single request results in some set of
provider.
3946
3947
3948
Here, if the result of the IdentifySubject is no matches found, then the subject is added to the gallery. If a
match had been found then other logic may have been applied (e.g., return candidate list, add encounter
for existing subject, etc.).
3949
Client
BIAS Client
BIAS Server Agent
BIAS Impl
Enroll
Enroll
Enroll
CheckQuality
IdentifySubject
CreateSubject
SetBiographicData
SetBiometricData
AddSubjectToGallery
ReturnData
ReturnData
ReturnData
3950
3951
3952
20 October 2009
Page 144 of 152
3953
B.6 Primitive Enrollment
3954
3955
3956
In this use case, the enrollment operation is performed as a series of requests using the BIAS primitive
operations. In this case, the client rather than the service provider controls the workflow of the higher
level operation.
3957
BIAS Client
BIAS Implementation
CheckQuality
CheckQuality
Return
Return
IdentifySubject
IdentifySubject
Return
CreateSubject
CreateSubject
Return
SetBiographicData
SetBiographicData
Return
SetBiometricData
SetBiometricData
Return
AddSubjectToGallery
AddSubjectToGallery
Return
3958
20 October 2009
Page 145 of 152
3959
Annex C. Samples (non-normative)
3960
C.1 Create Subject Request/Response Example
3961
INCITSBIASSpecification
3962
<interface name="CreateSubject">
3963
3964
<parameter name="SubjectID" type="xs:string" direction="inout"

use=optional />
3965
<parameter name="Return" type="xs:unsignedLong" direction="out" />
3966
</interface>
3967
OASISBIASExamples
3968
SimpleCreateSubjectRequest:
3969
POST /bias HTTP/1.1
3970
Host: www.acme.com
3971
3972
3973
SOAPAction: CreateSubject
3974
<?xml version=1.0?>
3975
3976
<soap:Body>
3977
3978
3979
3980
xmlns:tns=http://docs.oasisopen.org/bias/bias1.0/
/>
</soap:Body>
3981
</soap:Envelope>
3982
CreateSubjectRequestwithSubjectIDParameter:
3983
POST /bias HTTP/1.1
3984
Host: www.acme.com
3985
3986
3987
3988
<?xml version=1.0?>
3989
3990
3991
3992
3993
<soap:Body>
<tns:Identity>
3994
3995
3996
3997
</tns:Identity>
</soap:Body>
20 October 2009
Page 146 of 152
3998
</soap:Envelope>
3999
CreateSubjectRequestwithOptionalOASISBIASContent:
4000
POST /bias HTTP/1.1
4001
Host: www.acme.com
4002
4003
4004
4005
<?xml version=1.0?>
4006
4007
4008
4009
4010
<soap:Body>
<tns:GenericRequestParameters>
4011
<tns:Application>BIAS Application</tns:Application>
4012
<tns:ApplicationUser>BIAS User</tns:ApplicationUser>
4013
</tns:GenericRequestParameters>
4014
<tns:Identity>
4015
4016
4017
4018
</tns:Identity>
</soap:Body>
4019
</soap:Envelope>
4020
SimpleCreateSubjectResponse:
4021
HTTP/1.1 200 OK
4022
4023
4024
<?xml version=1.0?>
4025
4026
4027
4028
4029
<soap:Body>
<tns:CreateSubjectResponse
<tns:ResponseStatus>
4030
<tns:Return>0</tns:Return>
4031
</tns:ResponseStatus>
4032
<tns:Identity>
4033
4034
4035
4036
</tns:Identity>
</tns:CreateSubjectResponse>
</soap:Body>
4037
</soap:Envelope>
4038
CreateSubjectResponsewithOptionalOASISBIASContent:
20 October 2009
Page 147 of 152
4039
HTTP/1.1 200 OK
4040
4041
4042
<?xml version=1.0?>
4043
4044
4045
4046
<soap:Body>
<tns:CreateSubjectResponse
4047
4048
4049
4050
<tns:Message>Subject ID 123456789 successfully

created.</tns:Message>
4051
4052
<tns:Identity>
4053
4054
</tns:Identity>
4055
</tns:CreateSubjectResponse>
4056
4057
</soap:Body>
</soap:Envelope>
4058
4059
C.2 Set Biographic Data Request/Response Example
4060
4061
<interface name="SetBiographicData">
4062
<parameter name="SubjectID" type="xs:string" direction="in" />
4063
4064
/>
4065
4066
<parameter name="EncounterID" type="xs:string" direction="inout"

use="optional" />
4067
4068
/>
4069
<parameter name="IdentityModel" type="IdentityModelType" direction="in"
<parameter name="BiographicData" type="BiographicDataType" direction="in"

4070
</interface>
4071
OASISBIASExamples
4072
SetBiographicDataRequest:
4073
POST /bias HTTP/1.1
4074
Host: www.acme.com
4075
4076
4077
SOAPAction: SetBiographicData
4078
<?xml version=1.0?>
4079
4080
<soap:Body>
20 October 2009
Page 148 of 152
4081
<tns:SetBiographicDataRequest
4082
4083
<tns:Identity>
4084
<tns:SubjectID>123456789></tns:SubjectID>
4085
<tns:BiographicData>
4086
<tns:BiographicDataItem>
4087
<tns:Name>Last</tns:Name>
4088
<tns:Type>string</tns:Type>
4089
<tns:Value>Doe</tns:Value>
4090
</tns:BiographicDataItem>
4091
</tns:BiographicData>
4092
</tns:Identity>
4093
<tns:IdentityModel>person</tns:IdentityModel>
4094
</tns:SetBiographicDataRequest>
4095
</soap:Body>
4096
</soap:Envelope>
4097
SetBiographicDataResponse:
4098
HTTP/1.1 200 OK
4099
4100
4101
<?xml version=1.0?>
4102
4103
<soap:Body>
4104
<tns:SetBiographicDataResponse
4105
4106
4107
4108
4109
</tns:SetBiographicDataResponse>
4110
4111
</soap:Body>
</soap:Envelope>
4112
4113
C.3 Set Biometric Data Request/Response Example
4114
4115
<interface name="SetBiometricData">
4116
<parameter name="SubjectID" type="xs:string" direction="in" />
4117
4118
/>
4119
4120
<parameter name="EncounterID" type="xs:string" direction="inout"

use="optional" />
4121
<parameter name="IdentityModel" type="IdentityModelType" direction="in"
<parameter name="BIRList" type="CBEFF_BIR_ListType" direction="in" />

20 October 2009
Page 149 of 152
4122
4123
</interface>
4124
OASISBIASExamples
4125
SetBiometricDataRequest:
4126
POST /bias HTTP/1.1
4127
Host: www.acme.com
4128
4129
4130
SOAPAction: SetBiometricData
4131
<?xml version=1.0?>
4132
4133
4134
<soap:Body>
<tns:SetBiometricDataRequest
4135
4136
<tns:Identity>
4137
<tns:SubjectID>123456789></tns:SubjectID>
4138
<tns:BiometricData>
4139
<tns:BIRList>
4140
<tns:BIR>biometric data</tns:BIR>
4141
</tns:BIRList>
4142
</tns:BiometricData>
4143
</tns:Identity>
4144
<tns:IdentityModel>person</tns:IdentityModel>
4145
4146
</tns:SetBiometricDataRequest>
</soap:Body>
4147
</soap:Envelope>
4148
SetBiometricDataResponse:
4149
HTTP/1.1 200 OK
4150
4151
4152
<?xml version=1.0?>
4153
4154
4155
<soap:Body>
<tns:SetBiometricDataResponse
4156
4157
4158
4159
4160
4161
4162
</tns:SetBiometricDataResponse>
</soap:Body>
</soap:Envelope>
20 October 2009
Page 150 of 152
4163
Annex D. Acknowledgements
4164
4165
The following individuals have participated in the creation of this specification and are gratefully
acknowledged:
4166
4167
4168
Participants:
Name
Affiliation
Mr. Young Bang
Booz Allen Hamilton
Mr. Ed. Clay
Sun
Mr. Murty Gurajada *
Raining Data Corporation
Mr. Dale Hapeman
US Department of Defense
Dr. Charles Li
Raytheon
Mr. John Mayer-Splain
US Department of Homeland Security
Dr. Ross Michaels
NIST
Mr. Ramesh Nagappan
Sun
Mr. Ash Parikh *
Raining Data Corporation
Mr. Matthew Swayze
Daon
Mr. Guy Swope
Raytheon
Mrs. Catherine Tilton
Daon
Mr. Alessandro Triglia
OSS Nokalva
Mr. Brad Wing
NIST (formerly DHS)
Mr. Michael Wittman
Raytheon
Mr. Gregory Zektser
Booz Allen Hamilton
4169
4170
4171
* Though no longer members of the BIAS TC, these individuals contributed in the early stages of the
development of this standard.
4172
In addition, the inputs from the INCITS technical committee M1 are also gratefully appreciated.
20 October 2009
Page 151 of 152
4173
Annex E. Revision History
4174
Revision
Date
Editor
Changes Made
0.01
2008-05-23
TBD
Initial draft
0.02
2008-07-23
TBD
Inserted data dictionary

Added normative references
Updated sec 3 & 5 + Annex B
0.03
2008-08-19
TBD
WSDL updated
0.04
2008-09-11
TBD
Updated references
Added security requirements
Corrected Fig. 3
0.05
2008-09-29
TBD
SSL/TLS requirement clarified

Reordered material in 5.3 & App C/D
Updated references
2 new use cases added (App C)
Updated examples in App D
0.06
2008-11-17
TBD
Added BIAS operation name methods (new

5.3 + 4.2.27 & App B)
0.06a
2008-11-20
TBD
Updated references
0.07
2008-11-27
TBD
Revised fault structures and error handling
0.08
2009-06-22
TBD
Incorporated comments from informal public

review.
0.09
2009-07-24
Tilton/Swayze
Incorporated comments from June

review/meeting. Major changes included:
- Breaking Clause 3 into 2 clauses for
data elements and operations
- Specification of URI & IRI
- Clarifications and formatting
0.10
2009-10-19
Tilton/Swayze
Expansion of conformance clause
0.11
2009-11-16
Tilton/Swayze
Miscellaneous edits and clarifications
4175
20 October 2009
Page 152 of 152

Biasprofile 1.0 CD 01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Biasprofile 1.0 CD 01

Uploaded by

Copyright:

Available Formats

Biometric Identity Assurance Services

(BIAS) SOAP Profile, Version 1.0

3.2.28 ListFilterType ........................................................................................................................... 26

5.1 Purpose and constraints ................................................................................................................... 76

In addition to this introduction, this standard includes the following:

Clause 4 specifies the content of the BIAS messages.

Clause 6 presents information on error handling.

Clause 7specifies conformance requirements.

1.4 Relationship to Other Standards

The following additional terms and definitions are used:

1.6.1 Normative References

ISO/IEC 19785, Information technology Common Biometric Exchange Formats

ISO 8601:2004, Data elements and interchange formats Information

M. Duerst, et al, Internationalized Resouce Identifiers, W3C RFC3987, January

Simple Object Access Protocol (SOAP) 1.1, 8 May 2000

T. Berners-Lee, R. Fielding, L. Masinter, Uniform Resource Identifiers (URI):

ISO/IEC 10646:2003, Information technology Universal Multiple-Octet Coded

W3C Recommendation, Web Services Addressing 1.0 - Core, and Web

Basic Profile Version 1.1, 10 April 2006

Web Services-Interoperability Organization (WS-I) Simple SOAP Binding Profile

Web Services Description Language (WSDL) 1.1, 15 March 2001

Extensible Markup Language (XML) 1.0, 16 August 2006

XML-binary Optimized Packaging, W3C Recommendation, 25 January 2005

1.6.2 Non-Normative References

ISO/IEC 19784-1:2006, Information technology Biometric Application

ISO 19092 Financial services -- Biometrics -- Security framework

Department of Defense Electronic Biometric Transmission Specification, Version

IAFIS-DOC-01078-8.1, Electronic Biometric Transmission Specification

IAFIS-DOC-01078-7, Electronic Fingerprint Transmission Specification (EFTS),

HR-XML Consortium Library, 2007 April 15

Interpol Implementation of ANSI/NIST ITL1-2000, Ver 4.22b, October 28, 2005,

J. Franks, et al, HTTP Authentication: Basic and Digest Access Authentication,

R. Housley, et al, Internet X.509 Public Key Infrastructure Certificate and

SSL 3.0 Specification

X.509: Information technology - Open Systems Interconnection - The Directory:

OASIS Committee Specification 02, Customer Information Quality Specifications

2 Design Concepts and Architecture (non-normative)

Figure 1. BIAS Context

The BIAS Architecture as shown in Figure 2, in which:

Note that services are represented as circles.

Figure 2. Representative BIAS Architecture

3.1 Documentation Conventions

The name of the field.

The XML schema type of the field.

The cardinality of the field

Defines if the field must be present.

Zero or one occurrence

Zero or more occurrences

One or more occurrences

Yes is always required

No is not always required, an

Gives a short description of the fields

Fields Hierarchy Explained:

To denote the field hierarchy the symbol

is used to denote the child-of relationship.

3.2 Common Elements

Identifies an application user or instance.

Wraps the various BIAS biometric

A list of CBEFF-BIR elements.

Contains biometric information in either

Maps to specific INCITS BIAS

Maps to specific INCITS BIAS

A list of biometric data elements.