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
Committee’s email list. Others should send comments to the Technical Committee by using the
“Send A Comment” button on the Technical Committee’s 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/.

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

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.

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 3 of 152

...... 16  3......................................................................1 Philosophy ...................................................................... 23  3......................................... 7  1.............................. 18  3....................6 References......................27 InformationType ................................................................................... 24  3.......................................14 CandidateType ........................................................2......................... 20 October 2009 Page 4 of 152 ... 12  2.................................................................................2............................................ 20  3...................2 Common Elements .. 19  3..................2...... 12  2............ 7  1...................................................12 BiometricDataListType ...............2. 7  1.................................2...2................... 21  3.......................4 Relationship to Other Standards ................18 CBEFF_BIR_ListType .............................................................................................16 CapabilityName .........................................6...............................................3 Architecture ....................................2..................................................................................................................................2 Overview ........2................................................................................... 24  3......................................................2. 19  3......2............................................... All Rights Reserved.................................................................................... 20  3.................................................................................................................................................................2................................................................................................................................1 Purpose/Scope ..........................................................................................2 ApplicationUserIdentifier .................................. 22  3...................................... 15  3......................................................................................... 21  3.............................................................15 CapabilityListType ...............13 CandidateListType ..........................1 Documentation Conventions............................................5 Terminology ... 16  3........... 8  1...........2.........................2............................................................. 12  3  Data dictionary................................................................................... 9  1.... 7  1..............................2.....................................................................................23 EncounterListType ......................................................... 18  3..... 21  3................7 BIASIDType .............................................................2........................................................................................................... 25  Biasprofile-1............................................................................................................ 10  2  Design Concepts and Architecture (non-normative) ..........1 ApplicationIdentifier .......................................... 21  3.............................................................................................................................................. 25  3....................................6 BIASIdentity ....................................... 9  1.......................................................................................2...................................2................................... 22  3.........2 Non-Normative References ....................................................................................Table of Contents 1  Introduction ...........................................................2...................................... 12  2..............................25 FusionInformationType................................................................................................................19 CBEFF_BIR_Type ............................ 7  1........ 18  3...........26 GenericRequestParameters .............................................................2........ 16  3........................2..........................3 BIASBiometricDataType....2...........................................................................................................................................................9 BiographicDataSetType ...........................................................17 CapabilityType ................................................................................. 24  3.................................. 24  3...................... 15  3......3 Background ............... 16  3.........................................24 FusionInformationListType ..............................11 BiometricDataElementType...........................2..................... 24  3..............................................................8 BiographicDataItemType ......................................................................................................10 BiographicDataType ..... 16  3...............................................................................................................6................................. 17  3..........................22 ClassificationData ............................................................................................2...............................................................4 BIASFaultCode ...............................................................2............................2.........................2......0-cd-01 Copyright © OASIS Open 2009..........................................................................5 BIASFaultDetail ..............................................1 Normative References .................................................................... 25  3.......2 Context..............................2.................................................20 Classification ........21 ClassificationAlgorithmType ...............

.............................................31 ProductID.........................................................3 GetIdentifyResults .............2.............................................................................................................................2.............12 ListBiometricData ....... 26  3........................................................................................35 Score ............18 SetBiometricData .........................37 VendorIdentifier ..........................2 Aggregate Operations.................................................5 Identify ................ 61  4..................................................................................................6 RetrieveInformation ...15 RetrieveBiographicInformation ............................................................................1....................................................................................................................................5 DeleteBiographicData .......................... 67  4.................................................................................................................................................................. 26  3............. 74  5  Message structure and rules ......................... 29  4.........17 SetBiographicData .............36 TokenType.............1......................................... 29  4................................................ 66  4...........................................10 IdentifySubject ............................3..33 ResponseStatus ...................................................................................................... 35  4..........................8 DeleteSubjectFromGallery .......................2.........................38 Version .............9 GetIdentifySubjectResults ..................................... 43  4. 45  4.......................................................................... 55  4...........................2...... 63  4.......................34 ReturnCode . 66  4............................................................................................................................. 26  3....22 VerifySubject .................................6 DeleteBiometricData ...............................................................................................1.........................2..... 58  4...........7 Verify .... 51  4..............................................2.........1.. 39  4..1........................13 PerformFusion .............39 VersionType ..............................................................................................................32 QualityData .......1....................... 28  4  BIAS Messages .........................................................2...........................................................................................16 RetrieveBiometricInformation ................................................................................. 26  3........................................................................................................................14 QueryCapabilities ............................................................................................................. 49  4..........1......................................................... 60  4.........1................1 Primitive Operations .......................................1.......................................................4 CreateSubject .................. 38  4.......................................................................................................................1.....................................30 ProcessingOptionsType ......................................1......................2............. All Rights Reserved..2.........11 ListBiographicData ........................................ 32  4...... 76  Biasprofile-1.......................4 GetVerifyResults .......................................................................................................2.....29 MatchType ............................................. 33  4.........................................................................2............................................................................2.................................................................1............................................................. 53  4..................................................................................................................28 ListFilterType ...............................................1 Enroll ...........................................20 UpdateBiographicData .......................19 TransformBiometricData ................1..........................0-cd-01 Copyright © OASIS Open 2009. 27  3...................................................3 ClassifyBiometricData ....................................................................................2............................................. 72  4................................................... 20 October 2009 Page 5 of 152 ....................... 71  4..............................................................................................................1..2 GetEnrollResults .................................................1................................................2............................................................ 27  3.........................................................................................................................1..........1.............................................................................................. 26  3.....................................................................................................................2.. 27  3................................... 70  4...............................................2. 68  4........2................................................................................1......1.........................1......... 29  4..............2................1 AddSubjectToGallery ................................................................1..... 41  4...................2...................2 CheckQuality ............................... 56  4.1.................... 37  4.................................................................... 64  4........21 UpdateBiometricData ............. 30  4.................................... 28  3..................... 27  3................................................. 34  4.7 DeleteSubject ........................................................................... 28  3..................................................................................................................

................ Use Cases (non-normative) ...................................... 149  Annex D...................................................... 82  6  Error handling .................. 144  B.................1 Create Subject Request/Response Example......................... 81  5.......................... 79  5.............................................6.........................................................................................2 Message requirements ........................ 82  5............ 80  5.............1 Purpose and constraints ....3 Message Integrity .............................................................................. All Rights Reserved...........6.2 Use of XOP................................................. 83  7  Conformance ................................2 WS-Addressing Action ...........5.............................................. 83  6............................................ 141  B................................................................................................................................................. 20 October 2009 Page 6 of 152 ........................................................................................ Acknowledgements ......................................................................................... 82  5....7 Use with other WS* standards ...............................6..........................................................................................8 Tailoring ......4 Discovery ....................................................................................................5...............................................6 Primitive Enrollment .......0-cd-01 Copyright © OASIS Open 2009................ 78  5................................ 76  5...................................5 Identifying operations.....................................................................................................................................................................................................................................................6.............................................................................................................................6..................8 Key Management ........3 Set Biometric Data Request/Response Example .......................... 78  5....................................................................... 81  5................................. 140  B................................................. 79  5...................................................................................................................................................................................5 Biometric Enrollment .............................................6 Security Considerations .........................................................0 or TLS 1...................................................................................5 CBEFF BIR security features ...............................................................................................................7 Security of Stored Data ..................................................1 Use of SSL 3.................. 83  6....................................... 84  Annex A....................................... 78  5............................................1 Operation name element .......................................6 Security ......6...........................0 ........................................................................................................3 Handling binary data .............................................. 81  5....................................4 Identification Use Case .............. 80  5.. 140  B.......................................................................................3.........................................................................6.............................................................................................. 142  B.... 145  Annex C........................ 143  B...................................................................3 Primitive Verification ...................................... 85  Annex B.................................................... 81  5.............................................................................. 82  5.............................................................................................. 148  C....................................................... Samples (non-normative) ..........................................................................4 Message Confidentiality ...................... 79  5.................1 BIAS operation return codes......... XML Schema ................................................................................................................................. 152  Biasprofile-1.....................2 SOAP fault codes ........5...........................................................................6..................................... Revision History...................... 151  Annex E........... 81  5...........................................1 Base64 encoding ..... 78  5......................2 Data Origin Authentication ................... 77  5..................................... 146  C........................................................... 146  C...................................................3..........1 Verification Use Case .....2 Set Biographic Data Request/Response Example ......................................................................................................................2 Asynchronous Verification ...................................................

and identifies relationships to external data definitions. 23 24 • Annexes include the OASIS BIAS XML schema/sample Web Service Definition Language (WSDL). 22 • Clause 7specifies conformance requirements. 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. and achieved widespread adoption.4 Relationship to Other Standards 42 43 This OASIS BIAS profile comprises a companion standard to ANSI INCITS 442-2008 – Biometric Identity Assurance Services.) 12 1. 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. 25 1. allowing for platform and application independence. 16 17 • Clause 3 presents the namespaces necessary to implement this profile. specifying the identity Biasprofile-1. 18 • Clause 4 specifies the content of the BIAS messages.0-cd-01 Copyright © OASIS Open 2009. These SOAPbased services enable an application to invoke biometric identity assurance operations remotely in a Services Oriented Architecture (SOA) infrastructure. a gap was identified in the existing biometric standards portfolio with respect to biometric services. The expertise of both disciplines was required to ensure the standard was technically sound. 20 October 2009 Page 7 of 152 . 21 • Clause 6 presents information on error handling. use cases. as well as rules and considerations for its application. aggregate/composite operations. 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. 41 1. and the revision history of this profile. which defines the BIAS requirements and taxonomy.3 Background 26 27 28 29 30 31 32 33 34 35 In late 2005/early 2006.1 1 Introduction 2 1. to be as generic as possible – technology. acknowledgements. The International Committee for Information Technology Standards (INCITS) M1 provided the standards leadership relevant to biometrics. framework. defining the schema and SOAP messaging. (However. INCITS BIAS data elements. to provide business level operations without constraining the application/business logic that implements those operations. market relevant.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. OASIS provided the standards leadership relevant to service architectures with an initial focus on web services. 19 20 • Clause 5 presents the BIAS message structure. This standard proposal required the attention of two major technical disciplines: biometrics and service architectures. this standard includes the following: 14 15 • Clause 2 presents the design concepts and architecture for invoking SOAP-based services that implement BIAS operations. and to provide basic capabilities that can be used to construct higher level. sample code. & application domain independent. defining the “taxonomy” of biometric operations and data elements. All Rights Reserved.2 Overview 13 In addition to this introduction. BIAS services may be leveraged to implement biometric authentication in the future.

but in their respective sections. “REQUIRED”. “SHOULD NOT”. data model and data dictionary. 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. and error handling necessary to invoke SOAP-based services that implement BIAS operations.5 Terminology 55 56 57 The key words “MUST”. 20 October 2009 Page 8 of 152 . All Rights Reserved. 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. 50 51 52 53 This relationship allows the leveraging of the biometrics and web services expertise of the two standards development organizations. message structure and rules.0-cd-01 Copyright © OASIS Open 2009.44 45 46 assurance operations and the associated data elements. “MAY”. This OASIS BIAS profile specifies the design concepts and architecture. Discovery. and Integration URI Uniform Resource Identifier VPN Virtual Private Network WSDL Web Services Description Language WSS Web Services Security XML eXtensible Markup Language Biasprofile-1. BIAS operation and data element names are not defined here. “SHOULD”. “MUST NOT”. and “OPTIONAL” in this document are to be interpreted as described in [RFC2119]. 47 48 49 Together. “SHALL NOT”. “SHALL”. 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. “RECOMMENDED”. 54 1. 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.

ietf. and receiving BIAS messages BIAS endpoint runtime entity. http://ietf.98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 CBEFF Common Biometric Exchange Formats Framework . L. January 2005 http://www. Internationalized Resouce Identifiers.w3. U. et al. Uniform Resource Identifiers (URI): Generic Syntax.org [IRI] M. March 1997. Information technology – Common Biometric Exchange Formats Framework – Part 1: Data element specification & Part 3: Patron format specifications http://www. IETF RFC 2119. May 2008 http://www.0-cd-01 Copyright © OASIS Open 2009. 8 May 2000 http://www.1. 20 October 2009 Page 9 of 152 .org/TR/2000/NOTE-SOAP-20000508/ 136 137 138 139 [URI] T. Fielding. 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.org [INCITS-BIAS] ANSI INCITS 442-2008.iso.org [DATE-TIME] ISO 8601:2004.txt 134 135 [SOAP11] Simple Object Access Protocol (SOAP) 1.org Biasprofile-1. Biometric Identity Assurance Services (BIAS). Information technology — Universal Multiple-Octet Coded Character Set (UCS) http://www.1 Normative References 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 [RFC2119] S. Xerox Corporation.txt [CBEFF] ISO/IEC 19785.org/rfc/rfc3986 140 141 142 [UTF-8] ISO/IEC 10646:2003.iso.C. identified by an endpoint URI/IRI. W3C RFC3987. Duerst.data elements and BIR formats specified in ISO/IEC 19785-1 BIAS implementation software entity that is capable of creating.org/rfc/rfc3987. RFC 3986. All Rights Reserved.ietf. Data elements and interchange formats — Information interchange — Representation of dates and times http://www. Key words for use in RFCs to Indicate Requirement Levels.6 References 114 1. capable of sending and receiving BIAS messages.incits. Bradner. Irvine. processing.iso. Berners-Lee.org/rfc/rfc2119. January 2005. Masinter.6. MIT/LCS. sending. R. http://www.

Ver 4. 2007 April 15 http:// www.int 179 180 [NIEM] National Information Exchange Model (NIEM).org/TR/2006/REC-xml-20060816/ 155 156 [XOP] XML-binary Optimized Packaging.txt Biasprofile-1.mil/CurrentInitiatives/Standards/EBTS.w3. Dierks & C. June 2007. All Rights Reserved. January 1999 http://www.0.Biometrics -. “Electronic Fingerprint Transmission Specification (EFTS)”.1.dod. www. Information technology – Biometric Application Programming Interface – Part 1: BioAPI Specification http://www. October 28. Criminal Justice Information Services Division http:// www. May 2. 2005. 27 March 2009 http://www.org 163 164 165 [EBTS-DOD] Department of Defense Electronic Biometric Transmission Specification.fbibiospecs. The TLS Protocol.1.Core.2 Non-Normative References 158 159 160 [BioAPI] ISO/IEC 19784-1:2006.org 161 162 [BIO SEC] ISO 19092 Financial services -.ws-i.biometrics.0.org 176 177 178 [INT-I] Interpol Implementation of ANSI/NIST ITL1-2000. 25 January 2005 http://www.iso.html 151 152 [WSDL11] Web Services Description Language (WSDL) 1.html 148 149 150 [WS-I-Bind] Web Services-Interoperability Organization (WS-I) Simple SOAP Binding Profile Version 1.ws-i. Ver 2. Criminal Justice Information Services Division http:// www. Allen. Version 8.org/2002/ws/addr/ 146 147 [WS-I-Basic] Basic Profile Version 1.1.w3. November 19.Security framework http://www. Web Services Addressing 1.ietf. US DOJ/DHS http://www. Version 7.w3. and Web Services Addressing 1.SOAP Binding.aspx 166 167 168 169 [EBTS-FBI] IAFIS-DOC-01078-8. 16 August 2006 http://www. “Electronic Biometric Transmission Specification (EBTS)”.org/Profiles/SimpleSoapBindingProfile-1. Version 1. Federal Bureau of Investigation.0 . 15 March 2001 http://www.org 174 175 [HR-XML] HR-XML Consortium Library. 20 October 2009 Page 10 of 152 .1-2006-04-10. 10 April 2006 http://www.niem.0.hr-xml.0.0-2004-08-24. 24 August 2004 http://www. 9 May 2006 http://www.1.org/TR/2005/REC-xop10-20050125/ 157 1. 2008.org/TR/2001/NOTE-wsdl-20010315 153 154 [XML 10] Extensible Markup Language (XML) 1.org 170 171 172 173 [EFTS] IAFIS-DOC-01078-7.org/rfc/rfc2246.org/Profiles/BasicProfile-1.interpol.22b.fbibiospecs.iso. W3C Recommendation.143 144 145 [WS-Addr] W3C Recommendation. Version 2. 2005.0-cd-01 Copyright © OASIS Open 2009.w3.1.gov 181 182 [RFC2246] T. Federal Bureau of Investigation.0 .6. The Interpol AFIS Expert Group http:// www.0.

The Directory: Public-key and attribute certificate frameworks.org/security/saml/v2.php?wg_abbrev=ciq#download 206 Biasprofile-1.pdf 191 192 193 [SAML SEC] OASIS Standard. Housley.0-os.ietf. Franks.0/saml-core-2.org/rfc/rfc3280.org/committees/download.txt 186 187 188 [RFC3280] R. June 1999 http://www.0 Specification http://www.oasis-open. Security and Privacy Considerations for the OASIS Security Assertion Markup Language (SAML) V2.org/rfc/rfc2617. March 2005 http://docs.0/saml-sec-consider-2.HTM 196 197 198 199 [WSS] OASIS Standard.oasis-open. March 2005 http://docs. 20 October 2009 Page 11 of 152 .Open Systems Interconnection .oasis-open. 1 February 2006 http://www.0-cd-01 Copyright © OASIS Open 2009.183 184 185 [RFC2617] J.509: Information technology .0. August 2005 202 203 204 205 [xNAL] OASIS Committee Specification 02. Web Services Security: SOAP Message Security 1.freesoft.org/CIE/Topics/ssl-draft/3-SPEC.php/16790/wss-v1. HTTP Authentication: Basic and Digest Access Authentication. Customer Information Quality Specifications Version 3.org/committees/tc_home. Name and Address (xNAL) and Party (xPIL). Address (xAL). 20 September 2008 http://www. April 2002 http://www.0: Name (xNL).1.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile. et al.0-os.oasis-open.pdf 200 201 [X509] X. et al.pdf 194 195 [SSL3] SSL 3. ITU-T.txt 189 190 [SAML] OASIS Standard. All Rights Reserved.org/security/saml/v2. Security Assertion Markup Language (SAML) 2.1-spec-osSOAPMessageSecurity.0. Internet X. (WSSecurity 2004).ietf.

Figure 1.207 2 Design Concepts and Architecture (non-normative) 208 2. 20 October 2009 Page 12 of 152 . 219 220 221 BIAS is intended to provide a common. biometric systems are being developed which collect. this specification instead defines a method for using existing biometric and Web services standards to exchange biometric data and perform biometric operations.0-cd-01 Copyright © OASIS Open 2009. access to these biometric databases and services is via a Web services front-end. process.. 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. such as a services-oriented architecture (SOA) (although implementations are not limited to this environment).3 Architecture 232 233 234 235 BIAS Web services are intended to be used within systems employing a services framework. particularly in closed systems. UDDI directories) to discover the BIAS service provider (implementation) or. Web services interface that can be used within both closed and open SOA systems. BIAS Context 227 228 229 230 The clients (requesters) may use standard discovery mechanisms (i. 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. In many cases. Biasprofile-1. All Rights Reserved. the URI/IRI and WSDL for the service provider may be known a priori by the client BIAS application developer. However. depicts the context in which the BIAS messages will be implemented. yet flexible. As architectures move towards services-based frameworks.e.1 Philosophy 209 210 211 Rather than define a totally new and unique messaging protocol for biometric services. below. 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. data and/or capabilities need to be shared between systems or systems serve a number of different client stakeholders. 231 2.2 Context 213 214 215 216 217 218 Today. for example as an ESB or other application layer. store and match biometric data for a variety of purposes. As such. 212 2. lack of standardization in this area has led implementers to develop customized services for each system/application. 236 The BIAS Architecture as shown in Figure 2.

. processing. a biometric matcher). 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. 254 BIAS implementation 255 256 257 A BIAS implementation is a software entity that is capable of creating. All Rights Reserved. sending. and receiving BIAS messages. 252 253 At the heart of the BIAS messaging protocol are the concepts of BIAS messages and endpoints. 261 BIAS endpoints Biasprofile-1. This standard does not define requirements for the BIAS implementation other than defining the messages and protocols used by the endpoints. Note that services are represented as circles. 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.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.g. 20 October 2009 Page 13 of 152 .0-cd-01 Copyright © OASIS Open 2009. 245 246 247 248 Figure 2.

e.262 263 A BIAS endpoint is a runtime entity. 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. the business application or ESB. rather than the ultimate end client requester.g. uniquely identified and accessed by an endpoint URI/IRI [URI] [IRI]. 264 265 266 Note that when not publicly and directly exposed. capable of sending and receiving BIAS messages. 20 October 2009 Page 14 of 152 . Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009.. All Rights Reserved.

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. All Rights Reserved. is used to denote the child-of relationship.oasisopen. These include common data types or return codes.g. ansi-nist).org/bias/ns/bias-1. complex types and simple types described for the BIAS messages belong to the following namespace: http://docs. Gives a short description of the field’s use Figure 3. Each field that forms part of the message request/response is detailed in the table.. See Annex A for the XML schema. The elements. 273 274 NOTE: Biographic and biometric data included in a native XML format MAY contain elements referencing external namespaces (e. The input and output of each message and the comment elements are detailed in a table as described in the figure below. 280 Header Name Description Field The name of the field. an optional field...* One or more occurrences Y Yes – is always required N No – is not always required. Annex D). Biasprofile-1. Values Value Meaning 1 One occurrence 0. BIAS data elements are defined in ANSI INCITS 442-2008. 20 October 2009 Page 15 of 152 . 275 3.1 Zero or one occurrence 0.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). Likewise.0-cd-01 Copyright © OASIS Open 2009. # The cardinality of the field ? Meaning 281 Defines if the field must be present. Common data elements are defined for use in one or more operations. C Conditional – requirement is dependent on system or message conditions.* Zero or more occurrences 1. Type The XML schema type of the field..1 Documentation Conventions 276 277 278 279 Each common element has a section describing its content.0/. each operation has a section describing the request and response messages and the associated input and output parameters.

1 N Contains biometric information in either a non-XML or an XML representation. 3.1 N Maps to specific INCITS BIAS elements as required by that specification.286 3. Min Length: 1 Max Length: 255 3.3 BIASBiometricDataType Field Type # BIASBiometricDataType ? Meaning Y Wraps the various BIAS biometric types. 20 October 2009 Page 16 of 152 .2 ApplicationUserIdentifier Type: string Description: Identifies an application user or instance..1 N A list of biometric data elements. Min Length: 1 Max Length: 255 3. Biasprofile-1. ReferenceBIR CBEFF_BIR_Type 0. 290 291 BIRList CBEFF_BIR_ListType 0.2. InputBIR CBEFF_BIR_Type 0.2 Common Elements 287 3...2..2.1 N A list of CBEFF-BIR elements. The operations that use this type specify which elements are required.4 BIASFaultCode Type: String Description: Error code referenced in a SOAP fault.2..1 N Maps to specific INCITS BIAS elements as required by that specification. BIASFaultCode Enumeration Values Value Description UNKNOWN_ERROR The service failed for an unknown reason. BIR CBEFF_BIR_Type 0.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.1 ApplicationIdentifier 288 289 Type: string Description: Identifies an application. BiometricDataList BiometricDataListType 0.

295 (3) See section 5. All Rights Reserved. on the input BIR.5 for additional information on BIAS security.0-cd-01 Copyright © OASIS Open 2009. BIR_SIGNATURE_FAILURE The service could not validate the signature.5 BIASFaultDetail Field Type # BIASFaultDetail ? Meaning Y Defines the error information associated with a SOAP fault.Value Description UNSUPPORTED_CAPABILITY A requested capability is not supported by the service implementation. if used. 296 3. BIASFaultMessage string 1 Y Provides a brief explanation of the fault.2. UNKNOWN_GALLERY The gallery referenced by the input gallery ID does not exist. Biasprofile-1. 292 NOTES: 293 (1) See Clause 6 (Error handling) for an explanation of BIAS faults and return codes. 20 October 2009 Page 17 of 152 . BIASFaultType BIASFaultCode 1 Y References an error code. INVALID_BIR The input BIR is empty or in an invalid or unrecognized format. UNKNOWN_BIOGRAPHIC_FORMAT The biographic data format is not known or not supported. UNKNOWN_ENCOUNTER The encounter referenced by the input encounter ID does not exist. UNKNOWN_IDENTITY_CLAIM The identity referenced by the input identity claim does not exist.. BIR_QUALITY_ERROR Biometric sample quality is too poor for the service to succeed. such as trace details. UNKNOWN_SUBJECT The subject referenced by the input subject ID does not exist. INVALID_INPUT The data in a service input parameter is invalid. 294 (2) Service provider MAY define additional values specific to their service implementation. INVALID_IDENTITY_CLAIM The identity claim requested is already in use. NONEXISTANT_DATA The data requested for deletion does not exist. INVALID_SUBJECT_ID The input subject ID is empty or in an invalid format. 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. BIASFaultDescription string 0.1 N Provides detailed information about a BIAS fault.

IdentityClaim BIASIDType 0. biographic data.1 N An Identity’s biographic data. EncounterID BIASIDType 0...2.0-cd-01 Copyright © OASIS Open 2009. 298 299 EncounterList EncounterListType 0..2. Includes the Identity’s reference identifiers. and biometric data. BiometricData BIASBiometricDataType 0.1 C The identifier of an encounter associated with the subject. Type string 1 Y The data type for the biographic data item. 3.. The operations that use this type specify which elements are required. 20 October 2009 Page 18 of 152 .1 C A system unique identifier for a subject.297 3.1 N A list of encounters associated with a subject. Value string 0.8 BiographicDataItemType Field Type # BiographicDataItemType ? Meaning Y Defines a single biographic data element.1 N An Identity’s biographic data elements that are stored in the implementing system.1 N An Identity’s biometric data.1 N An identifier by which a subject is known to a particular gallery or population group. BiographicDataElements BiographicDataType 0.1 N The value assigned to the biographic data item. Biasprofile-1. Required as input to many operations.. BiographicData BiographicDataType 0. BIASIDType SubjectID 0.6 BIASIdentity Field Type # BIASIdentity ? Meaning Y Defines a single element for encapsulating the data associated with an Identity. Name string 1 Y The name of the biographic data item. 3.7 BIASIDType Type: string Description: A BIAS Identifier.2.. All Rights Reserved.. Required for encountercentric models..

it MUST be indicated by the specified name values. Biasprofile-1. however. FBI-EBTS. LastName string 0. for non-XML versions of FBI-EFTS. DOD-EBTS.g.300 301 302 NOTE: This element can be used to transmit scanned identity documents or document information (e. xNAL [xNAL].1” for FBI-EFTS or “2.fbibiospecs. One of the following elements must be present. (HR-XML) www.2. FBI-EBTS [EBTS-FBI]. 20 October 2009 Page 19 of 152 .org.. All Rights Reserved. for NIEM.niem. INT-I [INT-I]. BiographicDataItem BiographicDataItemType 0. FirstName string 0..org. DODEBTS [EBTS-DOD].g. Use these types for common formats: ASCII (e.0-cd-01 Copyright © OASIS Open 2009. or INT-I). 307 308 3.biometrics. “7.dod. XML (e.0” for NIEM). source string REQUIRED Reference to a URI/IRI describing the biographic data format.g. 3.. passports.* C A single biographic data element. N Biographic data formatted according to a specific format.int.9 BiographicDataSetType Field Type # BiographicDataSetType unspecified 303 any 0. birth certificates.* ? Meaning Y Defines a set of biographic data that is formatted according to the specified format. version string OPTIONAL The version of the biographic data format (e. driver’s license. and HR-XML or future versions of FBI-EBTS).. (NIEM) www.interpol.mil.10 BiographicDataType Field Type # BiographicDataType ? Meaning Y Defines a set of biographic data elements. formatted set of biographic information. HRXML [HR-XML].hrxml. etc.1 C The first name of a subject. The string value is not enumerated. required to establish an identity). BiographicDataSetType Attributes Name Type Use Meaning name string REQUIRED The name of the biographic data format.1 C The last name of a subject.g... See INCITS 442 for further information. Use these names for common formats: FBI-EFTS [EFTS]. 304 305 306 NOTE: Biographic data formats are not limited to those listed. the service provider MAY offer other formats.. utilizing either the BiographicDataItemType to represent a list of elements or the BiographicDataSetType to represent a complete. If one of the common types are used.org. For example: (FBI-EFTS and FBI-EBTS) www.gov. (INT-I) www.2.. NIEM [NIEM].oasis-open. type string REQUIRED The biographic data format type. (xNAL) www. utility bills. (DODEBTS) www. xNAL.

. [CBEFF] 318 319 3. or other CBEFF biometric organization that has defined the format for the biometric data. subtype. N Data structure containing information about a biometric record.2.0-cd-01 Copyright © OASIS Open 2009.1 C A set of biographic data information. as defined by CBEFF. 3. BiometricTypeCount positiveInteger 0.1 N More specifically defines the type of biometric data stored in the biometric record. such as the biometric type.g. section 8.11 BiometricDataElementType Field Type # BiometricDataElementType 316 317 ? Meaning Y Provides descriptive information about biometric data. industry consortium.1 for further information. BiometricType iso-iec19785-3-7: Multiple-types 1 Y The type of biological or behavioral data stored in the biometric record. NOTE: XML biometric metadata (BIR header elements) is aligned with ISO/IEC 19785-3.12 BiometricDataListType Field Type # BiometricDataListType BiometricDataElement BiometricDataElementType Biasprofile-1... BDBFormatType iso-iec19785-3-7: Registered-int 1 Y Identifies the specific biometric data format specified by the CBEFF biometric organization recorded in the BDB Format Owner field.2. as defined by CBEFF. 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. 0. All Rights Reserved. BDBFormatOwner iso-iec19785-3-7: Registered-int 1 Y Identifies the standards body. XML Patron Format. as specified in another standard) using the BiographicDataSetType. BiometricSubType iso-iec19785-3-7: Subtype 0. and format. 20 October 2009 Page 20 of 152 ..Field BiographicDataSet 309 Type # ? Meaning BiographicDataSetType 0.1 N The number of biometric records having the biometric type recorded in the biometric type field. contained in the BDB of the CBEFF-BIR. 314 315 See also INCITS 442.* ? Meaning Y A list of biometric data elements. working group..

N A single candidate. BIRList CBEFF_BIR_ListType 1 Y Biometric data associated with the candidate match. 3.2. N A single capability. 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.13 CandidateListType Field Type # CandidateListType Candidate 321 CandidateType 0.. 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.* ? Meaning Y Defines a set of candidates.2.2. 20 October 2009 Page 21 of 152 .1 N Biographic data associated with the candidate match. BiographicData BiographicDataType 0.320 3.* ? Meaning Y Defines a set of capabilities.14 CandidateType Field Type # CandidateType 322 323 ? Meaning Y Defines a single candidate as a possible match in response to a biometric identification request..0-cd-01 Copyright © OASIS Open 2009. Biasprofile-1. Score Score 0. All Rights Reserved. AggregateProcessingOption A processing option supported by the implementing system for the aggregate services. utilizing the CandidateType to represent each element in the set.1 N The match score..16 CapabilityName Type: string Description: A list of capability items. 3.15 CapabilityListType Field Type # CapabilityListType Capability 324 325 CapabilityType 0.2.. 3.

.326 Value Description AggregateReturnData A data element returned by the implementing system for the aggregate services. CBEFFPatronFormat A patron format supported by the implementing system. BiographicDataSet Identifies a biographic data set supported by the implementing system. CapabilitySupportingValue string 0. QualityAlgorithm A quality algorithm vendor and algorithm vendor product ID supported by the implementing system.17 CapabilityType Field Type # CapabilityType 327 ? Meaning Y Defines a single capability supported by an implementing system.2. # ? Meaning Y A list of CBEFF-BIR elements.1 N An identifier assigned to the capability by the implementing system.1 N A secondary value supporting the capability..0-cd-01 Copyright © OASIS Open 2009. ClassificationAlgorithmType A classification algorithm type supported by the implementing system. ConformanceClass Identifies the conformance class of the BIAS implementation. 3.1 N A value assigned to the capability. CapabilityValue string 0. IdentityModel Identifies whether the implementing system is person-centric or encounter-centric based.. AggregateServiceDescription Describes the processing logic of an aggregate service supported by the implementing system. 20 October 2009 Page 22 of 152 . MatchScore Identifies the use of match scores returned by the implementing system.2. Gallery A gallery or population group supported by the implementing system.. SupportedBiometric A biometric type supported by the implementing system. CapabilityName CapabilityName 1 Y The name of the capability. TransformOperation A transform operation type supported by the implementing system. 3.1 N A description of the capability. CapabilityID string 0. CapabilityAdditionalInfo string 0.1 N Contains additional information for the supported capability. All Rights Reserved.18 CBEFF_BIR_ListType Field Type CBEFF_BIR_ListType Biasprofile-1. CapabilityDescription string 0..

All Rights Reserved.* N CBEFF structure containing information about a biometric sample. 333 334 335 336 The latter two alternatives can use any CBEFF Patron Format. for more information on representing biometric data. 3.1 C A non-XML CBEFF-BIR.e. 20 October 2009 Page 23 of 152 .3 for more information on handling of binary data within BIAS and INCITS 442.. 1 Y One of the following sub-elements must be present.1 C An XML CBEFF-BIR.. in a simple CBEFF-BIR. format-type iso-iec19785-3-7:Registered-int REQUI RED Identifies the Patron format type..2. See section 5..1 N Contains information about the BDB in a simple CBEFF-BIR. 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.1 N Describes what is contained in a BIR. 0.1 C A URI/IRI reference to a CBEFFBIR. sb-info iso-iec19785-3-7:SBinfo 0..2.1 N Contains information about the security block. URI_BIR anyURI/IRI 0. The optional BIR_Information provides a mechanism for exposing metadata associated with a BIR format that is not easily decoded (i. with either a non-XML or XML representation.19 CBEFF_BIR_Type Field Type # ? Meaning Y Represents biometric information.Field BIR 328 Type # ? Meaning CBEFF_BIR_Type 0. a nonXML BIR)... Clause 8..0-cd-01 Copyright © OASIS Open 2009. if used. bdb-info iso-iec19785-3-7:BDBinfo 0. BIR 329 BinaryBIR base64Binary 0. CBEFF_BIR_Type BIR_Information bir-info iso-iec19785-3-7:BIRinfo 0. 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.. XML_BIR iso-iec19785-3-7:BIR 0.1 N Contains information about the CBEFF-BIR. NOTE: Biasprofile-1. using the XML Patron Format as defined in ISO/IEC 19785-3:2007. 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.

2. in closed systems. 341 342 (2) It is RECOMMENDED that only registered CBEFF patron formats be used.* ? Meaning Y Contains at a minimum two sets of fusion input elements.22 ClassificationData Field Type # ClassificationData 346 Meaning Y Contains information on classification results and the algorithm used to determine the classification.23 EncounterListType Field Type # EncounterListType EncounterID 347 ? BIASIDType 0.2. 3.2.* ? Meaning Y Defines a set of encounters. 2. as input to the PerformFusion operation. nonXML (binary) and URI BIRs MAY implement any CBEFF patron format. N The identifier of an encounter. 3. 343 344 345 3. Y A set of fusion information. All Rights Reserved.24 FusionInformationListType Field Type # FusionInformationListType FusionElement FusionInformationType Biasprofile-1. Classification Classification 1 Y The result of the classification.339 340 (1) XML BIRs MUST conform to ISO/IEC 19785-3 (clause 13..20 Classification Type: string Description: The result of a classification.0-cd-01 Copyright © OASIS Open 2009. this may not be required.2.. 3. however. ClassificationAlgorithmType ClassificationAlgorithmType 1 Y Identifies the type of classification algorithm that was used to perform the classification. 3.2.21 ClassificationAlgorithmType Type: string Description: Type of classification algorithm that was used to perform the classification. XML Patron Format). 20 October 2009 Page 24 of 152 . however.

1 N More specifically defines the type of biometric data stored in the biometric record. 20 October 2009 Page 25 of 152 .2. as defined by CBEFF.. AlgorithmOwner string 1 Y The owner or vendor of the algorithm used to determine the score or decision..26 GenericRequestParameters Field Type # GenericRequestParameters 350 351 352 ? Meaning Y Common request parameters that can be used to identify the requester.1 C The similarity score assigned by the matching algorithm.2.1 N Identifies the BIAS operation that is being requested. Application ApplicationIdentifier 0. Either a Score or a Decision element MUST be used. and it does not specify nor require any particular data element.1 N Identifies the user or instance of the requesting application.348 3..2. ? Meaning Y Allows for an unlimited number of data element types. ApplicationUser ApplicationUserIdentifier 0. AlgorithmType string 1 Y The Algorithm Owner’s identifier for the specific algorithm product and version used to determine the score or decision.. 3. string Decision 0. BIASOperationName string 0.. BiometricSubType iso-iec19785-3-7: Subtype 0. 349 3. All Rights Reserved.. BiometricType iso-iec19785-3-7: Multiple-types 1 Y The type of biological or behavioral data stored in the biometric record.27 InformationType Field Type # InformationType Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. Score Score 0. NOTE: See section 5.4 for alternatives for identifying the requested BIAS operation in a BIAS SOAP message.1 N Identifies the requesting application.1 C The match decision assigned by the matching algorithm. Either a Score or a Decision element MUST be used.25 FusionInformationType Field Type # FusionInformationType ? Meaning Y Represents the information necessary to perform a fusion operation.

All Rights Reserved.2.2. 3.2.31 ProductID Type: string Description: The vendor’s ID for a particular product.2. N The quality of a biometric sample.2. 3. 20 October 2009 Page 26 of 152 ... N An option supported by the implementing system. 3.0-cd-01 Copyright © OASIS Open 2009.* Y Limits the returned information to a specific type of biometric.* N Meaning 3.29 MatchType Type: boolean Description: The result of a fusion method.* ? Meaning Y BIAS aggregate operations support the ability to include various processing options which direct and possibly control the business logic for that operation. 3.28 ListFilterType Field Type # ListFilterType   354 355 Y Provides a method to filter the amount of information returned in a search of biometric data.Field   353 unspecified Type # ? any 0. The ProcessingOptionsType provides a method to represent those options.32 QualityData Field Type # QualityData QualityScore iso-iec19785-3-7: Quality Biasprofile-1..30 ProcessingOptionsType Type # ProcessingOptionsType string Option 357 Meaning BiometricTypeFilter Field 356 ? 0. 0.1 ? Meaning Y Contains information about a biometric sample’s quality and the algorithm used to compute the quality. iso-iec19785-3-7: Multiple-types 1. Processing options SHOULD be defined by the implementing system.. IncludeBiometricSubType boolean 1 Y A Boolean flag indicating if biometric subtype information should be returned. as defined by CBEFF.

3. Biasprofile-1. Quality scores.1 N The version of the algorithm used to determine the quality. ReturnCode Enumeration Values Value Description 0 Success 3. 362 363 364 Meaning NOTE: Matching scores MAY be in a standardized or proprietary form in terms of value range and interpretation. 20 October 2009 Page 27 of 152 .2. 3. AlgorithmVersion VersionType 0. section 13.2.1 N A short message corresponding to the return code. TokenValue string 1 Y A value returned by the implementing system that is used to retrieve the results to an operation at a later time.36 TokenType Field Type # TokenType   ? Meaning Y Defines a token that is returned for asynchronous processing. Expiration date 1 Y A date and time at which point the token expires and the operation results are no longer guaranteed to be available.33 ResponseStatus Field Type # ? ResponseStatus 359 360 361 Y Return ReturnCode 1 Y The return code indicates the return status of the operation.. All Rights Reserved.Field 358 Type # ? Meaning AlgorithmVendor VendorIdentifier 1 Y The vendor of the quality algorithm used to determine the quality score.2.35 Score Type: float Description: Match result or quality score. AlgorithmVendorProductID ProductID 1 Y The vendor’s ID for the algorithm used to determine the quality..0-cd-01 Copyright © OASIS Open 2009. however. Message string 0. follow the definition found in ISO/IEC 19785-3.34 ReturnCode Type: unsignedLong Description: Return value specifying success or other condition.2. 3.

All Rights Reserved.php.38 Version Field Type # Version 372 ? Meaning Y For a description or definition of each data element.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]. Registered biometric organizations are listed at: http://www. major nonNegativeInteger 1 Y minor nonNegativeInteger 1 Y 3. 368 369 370 371 NOTE: Vendor identifiers are registered with IBIA as the CBEFF registration authority (see ISO/IEC 19785-2). 20 October 2009 Page 28 of 152 .2. See also Annex A for schema definition. see the referenced CBEFF standards in the CBEFF_BIR_Type schema. 3.39 VersionType Type: string Description: The version of a component. 3.2.2.org/cbeff/_biometric_org.0-cd-01 Copyright © OASIS Open 2009.37 VendorIdentifier Type: string Description: Identifies a vendor.ibia. Biasprofile-1.

the value of the claim to identity by which the subject is known to the gallery MAY be specified.0-cd-01 Copyright © OASIS Open 2009..1 N Identifies the user or instance of the requesting application.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. the encounter ID associated with the subject’s biometrics that will be added to the gallery MUST be specified.1 N Common request parameters that can be used to identify the requester.1 Primitive Operations 378 4.. in the encounter-centric model.1 N Identifies the requesting application.. 387 Request Message Field Type # AddSubjectToGalleryRequest ? Meaning Y Register a subject to a given gallery or population group. Application ApplicationIdentifier 0.373 4 BIAS Messages 374 375 376 This section describes the BIAS messages implementing BIAS operations as defined in ANSI INCITS 442-2008.. with each operation containing a request and a response message. This claim to identity MUST be unique across the gallery. the subject ID (assigned with the CreateSubject operation) will be used as the claim to identity. The tables follow the conventions described in section 3. GenericRequestParameters 0. BIASIDType 1 Y A system unique identifier for a subject. If no claim to identity is specified. 377 4. GalleryID BIASIDType 1 Y The identifier of the gallery or population group to which the subject will be added. All Rights Reserved. BIASOperationName string 0. GenericRequestParameters SubjectID Biasprofile-1. ApplicationUser ApplicationUserIdentifier 0.1 N Identifies the BIAS operation that is being requested: “AddSubjectToGallery”. Identity BIASIdentity 1 Y The identity to add to the gallery. 20 October 2009 Page 29 of 152 . The operations are listed alphabetically. As an OPTIONAL parameter.1. Additionally.1.

. the implementing system will provide the algorithm vendor and algorithm vendor product ID that were used to calculate the biometric quality as output parameters. which in this specification is called a CBEFF-BIR. Required for encountercentric models.Field Type # ? Meaning IdentityClaim BIASIDType 0. All Rights Reserved. Return ReturnCode 1 Y The return code indicates the return status of the operation. If an algorithm vendor is provided then the algorithm vendor product ID is REQUIRED.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. for example.1 C The identifier of an encounter associated with the subject.0-cd-01 Copyright © OASIS Open 2009. Message string 0.1 N An identifier by which a subject is known to a particular gallery or population group. If no algorithm vendor is provided. (This could be a username or account number. 20 October 2009 Page 30 of 152 . ResponseStatus 1 Y Returned status for the operation. The algorithm vendor and algorithm vendor product ID MAY be optionally provided in order to request a particular algorithm’s use in calculating the biometric quality. 388 Response Message Field Type # AddSubjectToGalleryResponse ? Meaning Y The response to an AddSubjectToGallery operation. Type # ? Meaning Y Calculate a quality score for a given biometric.. 399 Request Message Field CheckQualityRequest Biasprofile-1.1.) EncounterID BIASIDType 0.1 N A short message corresponding to the return code.. ResponseStatus 389 4.

QualityData 0. Application ApplicationIdentifier 0.. Type # ? Meaning Y The response to a CheckQuality operation. All Rights Reserved.Field Type # ? Meaning GenericRequestParameters 0. BIASBiometricDataType 1 Y Data structure containing a single biometric sample for which a quality score is to be determined..0-cd-01 Copyright © OASIS Open 2009..1 N Identifies the requesting application.1 N Specifies a particular algorithm vendor and vender product ID. BIASOperationName string 0. AlgorithmVendor VendorIdentifier 1 Y The vendor of the quality algorithm used to determine the quality score. AlgorithmVendorProductID ProductID 1 Y The vendor’s ID for the algorithm used to determine the quality..1 N Identifies the user or instance of the requesting application.1 N Identifies the BIAS operation that is being requested: “CheckQuality”.1 N Common request parameters that can be used to identify the requester. GenericRequestParameters BiometricData BIR Quality 400 Response Message Field CheckQualityResponse Biasprofile-1. ApplicationUser ApplicationUserIdentifier 0.. CBEFF_BIR_Type 1 Y The biometric sample. 20 October 2009 Page 31 of 152 .

ResponseStatus QualityInfo 401 4..1 N Common request parameters that can be used to identify the requester. For example. or arch (or other classification classes and subclasses). 407 To obtain the types of classification algorithms and classes. GenericRequestParameters 0.0-cd-01 Copyright © OASIS Open 2009. ApplicationUser ApplicationUserIdentifier 0.. All Rights Reserved.3 ClassifyBiometricData 402 ClassifyBiometricDataRequest 403 ClassifyBiometricDataResponse 404 405 406 The ClassifyBiometricData operation attempts to classify a biometric sample..1 N Identifies the user or instance of the requesting application. Return ReturnCode 1 Y The return code indicates the return status of the operation. QualityData 1 Y Contains the quality information for the submitted biometric sample. Message string 0. see the QueryCapabilities operation.Field Type # ? Meaning ResponseStatus 1 Y Returned status for the operation.1. a fingerprint biometric sample may be classified as a whorl. 20 October 2009 Page 32 of 152 .1 N The quality of a biometric sample.1 N Identifies the requesting application. Application ApplicationIdentifier 0.. QualityScore iso-iec19785-3-7: Quality 0.1 N A short message corresponding to the return code. AlgorithmVersion VersionType 1 Y The version of the algorithm used to determine the quality. GenericRequestParameters Biasprofile-1. loop.. 408 Request Message Field Type # ClassifyBiometricDataRequest   ? Meaning Y Classifies a biometric sample. AlgorithmVendorProductID ProductID 1 Y The vendor’s ID for the algorithm used to determine the quality. AlgorithmVendor VendorIdentifier 1 Y The vendor of the quality algorithm used to determine the quality score.

BIASBiometricDataType 1 Y Data structure containing a single biometric sample for which the classification is to be determined. CBEFF_BIR_Type 1 Y The biometric sample.Field BIASOperationName BiometricData BIR 409 Type # ? Meaning string 0. the CreateSubject operation will generate one. 20 October 2009 Page 33 of 152 .1.. Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N A short message corresponding to the return code. ClassificationData 1 Y Information on the results and type of classification performed. containing the classification of a biometric sample.1 N Identifies the BIAS operation that is being requested: “ClassifyBiometricData ”.. All Rights Reserved. Biasprofile-1. Message string 0. ResponseStatus ClassificationData 410 4. ClassificationAlgorithmType ClassificationAlgor ithmType 1 Y Identifies the type of classification algorithm that was used to perform the classification. As an optional parameter. the subject ID MAY be specified by the caller. Classification Classification 1 Y The result of the classification.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. ResponseStatus 1 Y Returned status for the operation. If no subject ID is specified. Response Message Field Type # ClassifyBiometricDataResponse ? Meaning Y The response to a ClassifyBiometricData operation.0-cd-01 Copyright © OASIS Open 2009.

ResponseStatus 1 Y Returned status for the operation. In the encounter-centric model the operation erases all of the biographic data associated with a given encounter..1 N Common request parameters that can be used to identify the requester.1 N Identifies the user or instance of the requesting application. All Rights Reserved. 424 425 426 When deleting data. ApplicationUser ApplicationUserIdentifier 0.5 DeleteBiographicData 419 DeleteBiographicDataRequest 420 DeleteBiographicDataResponse 421 422 423 The DeleteBiographicData operation erases all of the biographic data associated with a given subject record. Application ApplicationIdentifier 0. GenericRequestParameters 417 ? Response Message Field Type # CreateSubjectResponse ? Meaning Y The response to a CreateSubject operation. BIASIdentity 1 Y BIASIDType 1 Y ResponseStatus Identity SubjectID A system unique identifier for a subject.0-cd-01 Copyright © OASIS Open 2009. Return ReturnCode 1 Y The return code indicates the return status of the operation. or they MAY track and record the deleted information for auditing and/or quality control purposes..416 Request Message Field Type # CreateSubjectRequest Meaning Y GenericRequestParameters 0. BIAS implementations MAY completely erase the information in order to prevent the ability to reconstruct a record in whole or in part. BIASOperationName string 0.1 N A short message corresponding to the return code.... Biasprofile-1.1 N Identifies the requesting application. and therefore the encounter ID MUST be specified.1. Message string 0.1 N Identifies the BIAS operation that is being requested: “CreateSubject”. 418 4. containing the subject ID of the new subject record. 20 October 2009 Page 34 of 152 .

1 N Identifies the requesting application.6 DeleteBiometricData 430 DeleteBiometricDataRequest Biasprofile-1.1 N Identifies the BIAS operation that is being requested: “DeleteBiographicData” .0-cd-01 Copyright © OASIS Open 2009. GenericRequestParameters Identity Required for encounter-centric models. BIASIdentity 1 Y SubjectID BIASIDType 1 Y A system unique identifier for a subject. GenericRequestParameters 0. All Rights Reserved. in the encounter-centric model. BIASOperationName string 0. with a given encounter..1 N Identifies the user or instance of the requesting application. ResponseStatus 429 4.1 N A short message corresponding to the return code. ResponseStatus 1 Y Returned status for the operation. ApplicationUser ApplicationUserIdentifier 0.. Application ApplicationIdentifier 0.1 N Common request parameters that can be used to identify the requester.. 20 October 2009 Page 35 of 152 .427 Request Message Field Type # DeleteBiographicDataRequest ? Meaning Y Erase all of the biographic data associated with a given subject record or. Message string 0.1 C The identifier of an encounter associated with the subject.1. EncounterID BIASIDType 0.. Return ReturnCode 1 Y The return code indicates the return status of the operation... 428 Response Message Field Type # DeleteBiographicDataResponse ? Meaning Y The response to a DeleteBiographicData operation.

BIASOperationName string 0.. or they MAY track and record the deleted information for auditing and/or quality control purposes.431 DeleteBiometricDataResponse 432 433 434 The DeleteBiometricData operation erases all of the biometric data associated with a given subject record. ApplicationUser ApplicationUserIdentifier 0.1 N Common request parameters that can be used to identify the requester. 439 Response Message Field Type # DeleteBiometricDataResponse ResponseStatus ResponseStatus Biasprofile-1...1 N Identifies the requesting application. In the encounter-centric model the operation erases all of the biometric data associated with a given encounter. GenericRequestParameters Identity Required for encounter-centric models. 20 October 2009 Page 36 of 152 . 438 Request Message Field Type # DeleteBiometricDataRequest ? Meaning Y Erase all of the biometric data associated with a given subject record or. in the encounter-centric model. BIASIdentity 1 Y SubjectID BIASIDType 1 Y A system unique identifier for a subject. Application ApplicationIdentifier 0.. All Rights Reserved. and therefore the encounter ID MUST be specified.. 435 436 437 When deleting data.0-cd-01 Copyright © OASIS Open 2009. with a given encounter. 1 ? Meaning Y The response to a DeleteBiometricData operation. GenericRequestParameters 0. EncounterID BIASIDType 0.1 C The identifier of an encounter associated with the subject. BIAS implementations MAY completely erase the information in order to prevent the ability to reconstruct a record in whole or in part.1 N Identifies the user or instance of the requesting application. Y Returned status for the operation.1 N Identifies the BIAS operation that is being requested: “DeleteBiometricData”.

# ? Meaning Y The response to a DeleteSubject operation.0-cd-01 Copyright © OASIS Open 2009. BIASIdentity 1 Y The identity of the subject to delete.. GenericRequestParameters Identity SubjectID 450 ? Response Message Field Type DeleteSubjectResponse Biasprofile-1. or they MAY track and record the deleted information for auditing and/or quality control purposes.1.1 N Identifies the BIAS operation that is being requested: “DeleteSubject”. This operation also removes the subject from any registered galleries. in an encounter-centric model.Field Type # ? Meaning Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N Identifies the requesting application.1 N Common request parameters that can be used to identify the requester.. 449 Request Message Field Type # DeleteSubjectRequest Meaning Y Delete an existing subject record and.. ApplicationUser ApplicationUserIdentifier 0. Message string 0..1 N Identifies the user or instance of the requesting application. 440 4.. BIASIDType 1 Y A system unique identifier for a subject.7 DeleteSubject 441 DeleteSubjectRequest 442 DeleteSubjectResponse 443 444 445 The DeleteSubject operation deletes an existing subject record and. 20 October 2009 Page 37 of 152 . any associated encounter information. 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.1 N A short message corresponding to the return code. Application ApplicationIdentifier 0. GenericRequestParameters 0. any associated encounter information from the system. BIASOperationName string 0. 446 447 448 When deleting a subject. in an encounter-centric model. All Rights Reserved.

Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N Identifies the user or instance of the requesting application..Field Type # ? Meaning ResponseStatus 1 Y Returned status for the operation.1 N Identifies the BIAS operation that is being requested: “DeleteSubjectFromGall ery”. Application ApplicationIdentifier 0. ApplicationUser ApplicationUserIdentifier 0....0-cd-01 Copyright © OASIS Open 2009.1 N A short message corresponding to the return code. 20 October 2009 Page 38 of 152 .1 N Identifies the requesting application. Biasprofile-1. All Rights Reserved. GenericRequestParameters SubjectID Required if an Identity Claim is not provided. BIASOperationName string 0..1 N Common request parameters that can be used to identify the requester. The subject is identified by either the subject ID or the claim to identity that was specified in the AddSubjectToGallery operation. GenericRequestParameters 0. Identity BIASIdentity 1 Y The identity to remove from the gallery. Message string 0.1. 457 Request Message Field Type # DeleteSubjectFromGalleryRequest ? Meaning Y Remove the registration of a subject from a gallery or population group. ResponseStatus 451 4. BIASIDType 0.1 C A system unique identifier for a subject.. GalleryID BIASIDType 1 Y The identifier of the gallery or population group from which the subject will be deleted.8 DeleteSubjectFromGallery 452 DeleteSubjectFromGalleryRequest 453 DeleteSubjectFromGalleryResponse 454 455 456 The DeleteSubjectFromGallery operation removes the registration of a subject from a gallery or population group.

458 Response Message Field Type # DeleteSubjectFromGalleryResponse ? Meaning Y The response to a DeleteSubjectFromGallery operation. 466 Request Message Field Type # GetIdentifySubjectResultsRequest ? Meaning Y Retrieve the identification results for a specified token. Return ReturnCode 1 Y The return code indicates the return status of the operation.1 C An identifier by which a subject is known to a particular gallery or population group.1 N A short message corresponding to the return code. If the IdentifySubject operation is implemented as an asynchronous service. This opereation is used in conjunction with the IdentifySubject operation. All Rights Reserved. ResponseStatus 459 4.0-cd-01 Copyright © OASIS Open 2009. Required if a Subject ID is not provided. ApplicationUser ApplicationUserIdentifier 0. which was returned by the IdentifySubject operation. 20 October 2009 Page 39 of 152 ..1 N Identifies the requesting application.. the implementing system returns a token and the GetIdentifySubjectResults operation is used to poll for the results of the original IdentifySubject request.Field IdentityClaim Type # ? Meaning BIASIDType 0... ResponseStatus 1 Y Returned status for the operation.1 N Identifies the user or instance of the requesting application. GenericRequestParameters Biasprofile-1.1. GenericRequestParameters 0.9 GetIdentifySubjectResults 460 GetIdentifySubjectResultsRequest 461 GetIdentifySubjectResultsResponse 462 463 464 465 The GetIdentifySubjectResults operation retrieves the identification results for the specified token. Application ApplicationIdentifier 0. Message string 0..1 N Common request parameters that can be used to identify the requester.

.... which includes a candidate list. BIASOperationName Token 467 Response Message Field Type # GetIdentifySubjectResultsResponse ? Meaning Y The response to a GetIdentifySubjectResults operation. 20 October 2009 Page 40 of 152 . ResponseStatus CandidateList Candidate Biasprofile-1.Field Type # ? Meaning string 0.* N A single candidate. BiographicData BiographicDataType 0. Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N Identifies the BIAS operation that is being requested: “GetIdentifySubjectRes ults”.0-cd-01 Copyright © OASIS Open 2009.1 N The match score. CandidateType 0.1 N Biographic data associated with the candidate match.. Expiration date 1 Y A date and time at which point the token expires and the operation results are no longer guaranteed to be available. All Rights Reserved. TokenValue string 1 Y A value returned by the implementing system that is used to retrieve the results to an operation at a later time.1 N A short message corresponding to the return code. ResponseStatus 1 Y Returned status for the operation. BIRList CBEFF_BIR_ListType 1 Y Biometric data associated with the candidate match. TokenType 1 Y A value used to retrieve the results of an IdentifySubject request. Message string 0. Score Score 0. CandidateListType 1 Y A rank-ordered list of candidates that have a likelihood of matching the input biometric sample.

returning a rank-ordered candidate list of a given maximum size. In this case.1 N Identifies the BIAS operation that is being requested: “IdentifySubject”.... Application ApplicationIdentifier 0. the implementing system immediately processes the request and returns the results in the candidate list. 20 October 2009 Page 41 of 152 . GenericRequestParameters 0. 478 Request Message Field Type # IdentifySubjectRequest ? Meaning Y Perform an identification search against a given gallery for a given biometric. BIASBiometricDataType 1 Y An Identity’s biometric data. a data structure containing the biometric sample for the search. which is an indication that the request is being handled asynchronously. 473 474 475 476 477 If the IdentifySubject operation is implemented as a synchronous service.1 N Identifies the user or instance of the requesting application.* N CBEFF structure containing information about a biometric sample.. the implementing system returns a token. the GetIdentifySubjectResults operation is used to poll for the results of the IdentifySubject request. GenericRequestParameters BiometricData Biasprofile-1. BIASOperationName string 0.1 N Identifies the requesting application. ApplicationUser ApplicationUserIdentifier 0.1 N Common request parameters that can be used to identify the requester. If the IdentifySubject operation is implemented as an asynchronous service.. GalleryID BIASIDType 1 Y The identifier of the gallery or population group which will be searched.Field BIR Type # ? Meaning CBEFF_BIR_Type 0.10 IdentifySubject 469 IdentifySubjectRequest 470 IdentifySubjectResponse 471 472 The IdentifySubject operation performs an identification search against a given gallery for a given biometric. Identity BIASIdentity 1 Y Contains the BIR.1.0-cd-01 Copyright © OASIS Open 2009. 468 4. All Rights Reserved.

positiveInteger 1 Y The maximum size of the candidate list that should be returned. returning a rank-ordered candidate list. CandidateListType 0.1 N Biographic data associated with the candidate match. All Rights Reserved.e.1 C A rank-ordered list of candidates that have a likelihood of matching the input biometric sample (i. CBEFF_BIR_Type 0.. Candidate BIR Biasprofile-1. exceed the system threshold). Returned with successful synchronous request processing..1 N A short message corresponding to the return code..* N CBEFF structure containing information about a biometric sample... Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N The match score. ResponseStatus 1 Y Returned status for the operation. BIRList CBEFF_BIR_ListType 1 Y Biometric data associated with the candidate match.0-cd-01 Copyright © OASIS Open 2009.Field BIR MaxListSize 479 Type # ? Meaning CBEFF_BIR_Type 1 Y Contains biometric information in either a non-XML or an XML representation. CandidateType 0. Response Message Field Type # IdentifySubjectResponse ? Meaning Y The response to an IdentifySubject operation. BiographicData BiographicDataType 0. 20 October 2009 Page 42 of 152 . ResponseStatus CandidateList Rank ordering is from highest to lowest match score.* N A single candidate.. Score string 0.. Message string 0.

. and the Biographic Data Elements output parameter is empty.. in the event of a tie). In the encounter-centric model. 495 Request Message Field Type # ListBiographicDataRequest GenericRequestParameters Application ? Meaning Y Lists the biographic data elements stored for a subject.1. NOTES: 481 482 483 (1) In the event that the number of candidates exceeding the threshold exceeds the MaxListSize.Field Token Type # ? Meaning TokenType 0. 480 TokenValue string 1 Y A value returned by the implementing system that is used to retrieve the results to an operation at a later time.e. If an encounter ID is not specified and encounter data exists for the subject.0-cd-01 Copyright © OASIS Open 2009. Biasprofile-1. Returned with asynchronous request processing. 484 (2) Requesters MAY NOT change the system thresholds. All Rights Reserved.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. an encounter ID MAY be specified to indicate that only the biographic data elements stored for that encounter should be returned.1 C A token used to retrieve the results of the IdentifySubject operation.1 N Common request parameters that can be used to identify the requester. 20 October 2009 Page 43 of 152 .1 N Identifies the requesting application. the operation returns the list of encounter IDs which contain biographic data using the Encounter List output parameter.. ApplicationIdentifier 0. the system will determine which candidate is included in the last position of the rank ordered candidate list (i. Note that no actual biographic data is returned by this operation (see the RetrieveBiographicInformation operation to obtain the biographic data). Expiration date 1 Y A date and time at which point the token expires and the operation results are no longer guaranteed to be available. GenericRequestParameters 0.. 485 4.

In the encounter-centric model.. BIASOperationName string 0. Type # Identity 496 Response Message Field ListBiographicDataResponse ? Meaning Y The response to a ListBiographicData request. EncounterID BIASIDType 0.Field Type # ? Meaning ApplicationUser ApplicationUserIdentifier 0. ResponseStatus 1 Y Returned status for the operation. a subject and an encounter.1 N Identifies the BIAS operation that is being requested: “ListBiographicData”. BIASIdentity 1 Y Identifies the subject or.1 N A short message corresponding to the return code.. SubjectID BIASIDType 1 Y A system unique identifier for a subject. Message string 0.1 N Identifies the user or instance of the requesting application. the list of encounter IDs which contain biographic data is returned. the biographic data elements for a specific encounter are returned. All Rights Reserved. Return ReturnCode 1 Y The return code indicates the return status of the operation. in the encountercentric model..1 N The identifier of an encounter associated with the subject.. ResponseStatus Biasprofile-1. containing a list of biographic data elements stored for a subject. 20 October 2009 Page 44 of 152 .0-cd-01 Copyright © OASIS Open 2009. If an encounter ID is not specified and encounter data exists for the subject.

. All Rights Reserved.1. non-empty if the service was successful. BiographicDataItemType 0. and an encounter identifier was not specified. biographic data exists. In the encounter-centric model.0-cd-01 Copyright © OASIS Open 2009. and either (a) the person-centric model is being used or (b) the encountercentric model is being used and an encounter identifier was specified. Name string 1 Y The name of the biographic data item. 20 October 2009 Page 45 of 152 . the encountercentric model is being used. an Biasprofile-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. Type string 1 Y The data type for the biographic data item.* N A single biographic data element. Note that no actual biometric data is returned by this operation (see the RetrieveBiometricInformation operation to obtain the biometric data). EncounterListType 0..1 C An Identity’s biographic data elements that are stored in the implementing system. non-empty if the service was successful.Field Type # ? Meaning BIASIdentity 1 Y Contains a list of biographic data elements associated with a subject or encounter.1 C A list of encounter ID’s associated with a subject and which contain biographic data.. BiographicDataType 0. Identity BiographicDataElements BiographicDataItem EncounterList EncounterID 497 4..* N The identifier of an encounter. BIASIDType 0. biographic data exists.

. GenericRequestParameters 0. and the Biometric Data List output parameter is empty.. ApplicationUser ApplicationUserIdentifier 0. etc.0-cd-01 Copyright © OASIS Open 2009.. iris.1 N Indicates what biometric information should be returned.g. all fingerprints: left slap.. 20 October 2009 Page 46 of 152 ..) or that only biometric subtypes for a particular biometric type should be listed (e.1 N Identifies the requesting application.g.1 N Identifies the BIAS operation that is being requested: “ListBiometricData ”. finger. 512 Request Message Field Type # ListBiometricDataRequest ? Meaning Y Lists the biometric data elements stored for a subject. all biometric type and biometric subtype information are listed (e. If a filter is not specified. ListFilterType 0. Such a filter may indicate that only biometric types should be listed (e. 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. face frontal. SubjectID BIASIDType 1 Y A system unique identifier for a subject. etc.1 N Identifies the user or instance of the requesting application.. a subject and an encounter. in the encounter-centric model.g.. etc. GenericRequestParameters Identity ListFilterType Biasprofile-1. right iris. right index... 507 508 509 510 511 An optional parameter MAY be used to indicate a filter on the list of returned data. BIASOperationName string 0. BIASIdentity 1 Y Identifies the subject or.1 N Common request parameters that can be used to identify the requester.). EncounterID BIASIDType 0.).503 504 505 506 encounter ID MAY be specified to indicate that only the biometric data elements stored for that encounter should be returned. Application ApplicationIdentifier 0. All Rights Reserved. face. left index finger.1 N The identifier of an encounter associated with the subject.

containing a list of biometric data elements stored for a subject..0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.1 N A short message corresponding to the return code. If an encounter ID is not specified and encounter data exists for the subject. In the encountercentric model. 20 October 2009 Page 47 of 152 . ResponseStatus Biasprofile-1.Field 513 Type # ? Meaning BiometricTypeFilter iso-iec19785-3-7:Multipletypes 1. IncludeBiometricSubType boolean 1 Y A Boolean flag indicating if biometric subtype information should be returned. the list of encounter IDs which contain biometric data is returned. Message string 0.* Y Limits the returned information to a specific type of biometric. Response Message Field Type # ListBiometricDataResponse ? Meaning Y The response to a ListBiometricData operation. the biometric data elements for a specific encounter are returned.. as defined by CBEFF. Return ReturnCode 1 Y The return code indicates the return status of the operation. ResponseStatus 1 Y Returned status for the operation.

All Rights Reserved. iso-iec19785-3-7:Subtype 0..* Y Data structure containing information about a biometric record. BiometricDataListType 0. iso-iec19785-3-7:Multipletypes 1 Y The type of biological or behavioral data stored in the biometric record. BiometricDataElementType 1.Field Identity BiometricData BiometricDataList Type # ? Meaning BIASIdentity 0.1 C An Identity’s biometric data.0-cd-01 Copyright © OASIS Open 2009. positiveInteger 0..1 N Includes a list of biometric data elements associated with a subject or encounter or a list of encounter ID’s associated with a subject and which contain biometric data.. BIASBiometricDataType 0.1 N More specifically defines the type of biometric data stored in the biometric record.1 N A list of biometric data elements... as defined by CBEFF. 20 October 2009 Page 48 of 152 . BiometricDataElement BiometricType BiometricTypeCount BiometricSubType Biasprofile-1.1 N The number of biometric records having the biometric type recorded in the biometric type field.. as defined by CBEFF.

Biasprofile-1. 20 October 2009 Page 49 of 152 . All Rights Reserved. and an encounter identifier was not specified.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 fusion method and processes are left to the implementing system. the encounter-centric model is being used.1 C A list of encounter ID’s associated with a subject and which contain biometric data.0-cd-01 Copyright © OASIS Open 2009. BIASIDType 1. EncounterList EncounterID 514 4.Field Type # ? Meaning 1 Y BDBFormatOwner iso-iec19785-3-7: Registered-int Identifies the standards body.* Y The identifier of an encounter. provides specific elements for match score input and match decision input. EncounterListType 0. biometric data exists. iso-iec19785-3-7: Registered-int 1 Y BDBFormatType Identifies the specific biometric data format specified by the CBEFF biometric organization recorded in the BDB Format Owner field. through the FusionInformationType. or other CBEFF biometric organization that has defined the format for the biometric data. industry consortium. non-empty if the service was successful..1. The FusionInformationListType. working group..

BiometricType iso-iec19785-3-7:Multipletypes 1 Y The type of biological or behavioral data stored in the biometric record. BIASOperationName string 0.. GenericRequestParameters FusionInput FusionElement Biasprofile-1. All Rights Reserved.. FusionInformationType 2. ApplicationUser ApplicationUserIdentifier 0. BiometricSubType iso-iec19785-3-7:Subtype 0. GenericRequestParameters 0. FusionInformationListType 1 Y Score or decision input information to the fusion method... AlgorithmOwner string 1 Y The owner or vendor of the algorithm used to determine the score or decision. Application ApplicationIdentifier 0.1 N Identifies the user or instance of the requesting application. 20 October 2009 Page 50 of 152 .521 Request Message Field Type # PerformFusionRequest ? Meaning Y Accepts either match score or match decision information and creates a fused match result. as defined by CBEFF...1 N Identifies the requesting application.1 N Identifies the BIAS operation that is being requested: “PerformFusion”.1 N Common request parameters that can be used to identify the requester.1 N More specifically defines the type of biometric data stored in the biometric record.0-cd-01 Copyright © OASIS Open 2009.* Y A set of fusion information.

0-cd-01 Copyright © OASIS Open 2009.. All Rights Reserved.14 QueryCapabilities 524 QueryCapabilitiesRequest 525 QueryCapabilitiesResponse 526 527 528 529 The QueryCapabilities operation returns a list of the capabilities. MatchType 1 1 Indicates the result of the fusion method.1. 522 Response Message Field Type # PerformFusionResponse ? Meaning Y The response to the PerformFusion operation. etc. options.. Message string 0.. ResponseStatus Match 523 4. string Decision 0. 20 October 2009 Page 51 of 152 .1 N A short message corresponding to the return code. Refer to Annex A in the INCITS BIAS standard for conformance requirements regarding which capability names an implementation must use in the QueryCapabilities operation. Return ReturnCode 1 Y The return code indicates the return status of the operation. ResponseStatus 1 Y Returned status for the operation. Score Score 0.1 C The similarity score assigned by the matching algorithm. Either a Score or a Decision element MUST be used. galleries.Field Type # ? Meaning AlgorithmType string 1 Y The Algorithm Owner’s identifier for the specific algorithm product and version used to determine the score or decision. Biasprofile-1. Either a Score or a Decision element MUST be used.1 C The match decision assigned by the matching algorithm. that are supported by the BIAS implementation.

CapabilityType 0. ResponseStatus 1 Y Returned status for the operation. BIASOperationName string 0.. ResponseStatus CapabilityList Capability CapabilityName Biasprofile-1. Message string 0. CapabilityListType 1 Y A list of capabilities supported by the BIAS implementation.. 20 October 2009 Page 52 of 152 .1 N A short message corresponding to the return code... that are supported by the BIAS implementation.* N A single capability. ApplicationUser ApplicationUserIdentifier 0. All Rights Reserved. etc.1 N Common request parameters that can be used to identify the requester.1 N Identifies the user or instance of the requesting application.1 N Identifies the requesting application.0-cd-01 Copyright © OASIS Open 2009.. Application ApplicationIdentifier 0. galleries.1 N Identifies the BIAS operation that is being requested: “QueryCapabilities”.530 Request Message Field Type # QueryCapabilitiesRequest Meaning Y Returns a list of the capabilities. options. GenericRequestParameters 0.. CapabilityName 1 Y The name of the capability. Return ReturnCode 1 Y The return code indicates the return status of the operation. GenericRequestParameters 531 ? Response Message Field Type # QueryCapabilitiesResponse ? Meaning Y The response to a QueryCapabilities operation.

GenericRequestParameters Biasprofile-1.. 532 4. CapabilitySupportingValue string 0. 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.1 N A value assigned to the capability. CapabilityAdditionalInfo string 0. GenericRequestParameters 0.1 N A secondary value supporting the capability. the operation returns the biographic information associated with the most recent encounter. CapabilityDescription string 0.1 N Contains additional information for the supported capability....15 RetrieveBiographicInformation 533 RetrieveBiographicInformationRequest 534 RetrieveBiographicInformationResponse 535 536 537 538 539 The RetrieveBiographicInformation operation retrieves the biographic data associated with a subject ID..1. Application ApplicationIdentifier 0.Field Type # ? Meaning CapabilityID string 0. ApplicationUser ApplicationUserIdentifier 0.1 N A description of the capability.0-cd-01 Copyright © OASIS Open 2009.. 540 Request Message Field Type # RetrieveBiographicInformationRequest ? Meaning Y Retrieves the biographic data associated with a subject ID. 20 October 2009 Page 53 of 152 . All Rights Reserved.1 N An identifier assigned to the capability by the implementing system.1 N Common request parameters that can be used to identify the requester.1 N Identifies the user or instance of the requesting application.1 N Identifies the requesting application... CapabilityValue string 0. In the encounter-centric model.

BIASIdentity 1 Y Identifies the subject or. Type # BIASOperationName Identity 541 Response Message Field RetrieveBiographicInformationResponse ? Meaning Y The response to a RetrieveBiographicInf ormation operation. 1 N The identifier of an encounter associated with the subject. BiographicDataType 1 Y An Identity’s biographic data.Field Type # ? Meaning string 0. Return ReturnCode 1 Y The return code indicates the return status of the operation. ResponseStatus Identity BiographicData One of the following elements MUST be present. BIASIdentity 1 Y Includes the set of biographic data associated with a subject.0-cd-01 Copyright © OASIS Open 2009.. 20 October 2009 Page 54 of 152 .1 C The first name of a subject.. a subject and an encounter. SubjectID BIASIDType 1 Y A system unique identifier for a subject. ResponseStatus 1 Y Returned status for the operation.1 N Identifies the BIAS operation that is being requested: “RetrieveBiographicI nformation”. in the encountercentric model.. FirstName string 0. All Rights Reserved. LastName string 0.1 C The last name of a subject. Message string 0.1 N A short message corresponding to the return code... Biasprofile-1. EncounterID BIASIDType 0.

1 N Common request parameters that can be used to identify the requester. BiographicDataSet BiographicDataSetType 0. in the encountercentric model. the operation returns the biometric information associated with the most recent encounter. 20 October 2009 Page 55 of 152 .. SubjectID BIASIDType 1 Y A system unique identifier for a subject.1 N The identifier of an encounter associated with the subject. the encounter ID MAY be specified and the operation will return the biometric data associated with that encounter.1 N Identifies the user or instance of the requesting application. 542 4. BIASOperationName string 0. GenericRequestParameters Identity Biasprofile-1.1 N Identifies the BIAS operation that is being requested: “RetrieveBiometricInfo rmation”.1.* C A single biographic data element.. EncounterID BIASIDType 0.0-cd-01 Copyright © OASIS Open 2009. The operation provides an OPTIONAL input parameter to specify that only biometric data of a certain type should be retrieved. If the encounter ID is not specified in the encounter-centric model. BIASIdentity 1 Y Identifies the subject or. ApplicationUser ApplicationUserIdentifier 0. All Rights Reserved. In the encounter-centric model. 551 Request Message Field Type # RetrieveBiometricInformationRequest ? Meaning Y Retrieves the biometric data associated with a subject ID.1 C A set of biographic data information. GenericRequestParameters 0..1 N Identifies the requesting application...16 RetrieveBiometricInformation 543 RetrieveBiometricInformationRequest 544 RetrieveBiometricInformationResponse 545 546 547 548 549 550 The RetrieveBiometricInformation operation retrieves the biometric data associated with a subject ID..Field Type # ? Meaning BiographicDataItem BiographicDataItemType 0. a subject and an encounter. Application ApplicationIdentifier 0..

CBEFF_BIR_Type 0. ResponseStatus 1 Y Returned status for the operation.. Return ReturnCode 1 Y The return code indicates the return status of the operation.. BIASBiometricDataType 1 Y An Identity’s biometric data. If the encounter ID is omitted for the encounter-centric model.Field BiometricType 552 Type # ? Meaning iso-iec19785-3-7:Multipletypes 0.* N CBEFF structure containing information about a biometric sample. CBEFF_BIR_ListType 1 Y A list of CBEFF-BIR elements. BIASIdentity 1 Y Includes the biometric data associated with a subject. ResponseStatus Identity BiometricData BIRList BIR 553 4. 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).1 N The type of biological or behavioral data to retrieve. Response Message Field Type # RetrieveBiometricInformationResponse ? Meaning Y The response to a RetrieveBiometricInformati on operation.1. 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). All Rights Reserved..1 N A short message corresponding to the return code. Message string 0. the operation returns a system-assigned encounter ID.0-cd-01 Copyright © OASIS Open 2009. Biasprofile-1. 20 October 2009 Page 56 of 152 . For encounter-centric models.17 SetBiographicData 554 SetBiographicDataRequest 555 SetBiographicDataResponse 556 557 558 559 560 561 562 The SetBiographicData operation associates biographic data to a given subject record.

GenericRequestParameters Identity One of the following elements MUST be present... BIASOperationName string 0..1 N Identifies the user or instance of the requesting application.1 N Common request parameters that can be used to identify the requester. Biasprofile-1.1 N Identifies the requesting application. All Rights Reserved. BiographicData BiographicDataType 1 Y An Identity’s biographic data.. BIASIdentity 1 Y Identifies the subject or. LastName string 0. FirstName string 0.. EncounterID BIASIDType 0.1 C The first name of a subject. GenericRequestParameters 0.0-cd-01 Copyright © OASIS Open 2009. ApplicationUser ApplicationUserIdentifier 0.1 N The identifier of an encounter associated with the subject.1 C The last name of a subject. and includes the biographic data to store. in the encounter-centric model. a subject and an encounter...563 Request Message Field Type # SetBiographicDataRequest ? Meaning Y Associates biographic data to a given subject record. 20 October 2009 Page 57 of 152 . Application ApplicationIdentifier 0. SubjectID BIASIDType 1 Y A system unique identifier for a subject.1 N Identifies the BIAS operation that is being requested: “SetBiographicDat a”.

ResponseStatus Identity EncounterID 565 4. 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). Biasprofile-1.1 N Identifies the requesting application.1 N A short message corresponding to the return code. ResponseStatus 1 Y Returned status for the operation. All Rights Reserved.1 N Common request parameters that can be used to identify the requester. If the encounter ID is omitted for the encounter-centric model. For encounter-centric models.. 20 October 2009 Page 58 of 152 . the operation returns a system-assigned encounter ID.1 C A set of biographic data information..Field 564 Type # ? Meaning BiographicDataItem BiographicDataItemType 0..0-cd-01 Copyright © OASIS Open 2009. ApplicationIdentifier 0. identifies the encounter ID assigned to a new encounter. BIASIdentity 0. Return ReturnCode 1 Y The return code indicates the return status of the operation. 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). Response Message Field Type # SetBiographicDataResponse ? Meaning Y The response to a SetBiographicData operation. BiographicDataSet BiographicDataSetType 0.18 SetBiometricData 566 SetBiometricDataRequest 567 SetBiometricDataResponse 568 569 570 571 572 573 574 The SetBiometricData operation associates biometric data to a given subject record.1..1 C In an encounter-centric model... 575 Request Message Field Type # SetBiometricDataRequest GenericRequestParameters Application ? Meaning Y Associates biometric data to a given subject record. Message string 0. BIASIDType 1 Y The identifier of an encounter associated with the subject.* C A single biographic data element. GenericRequestParameters 0.

1 N Identifies the BIAS operation that is being requested: “SetBiometricData”..* Y CBEFF structure containing information about a biometric sample.1 N A short message corresponding to the return code. in the encounter-centric model. BIASIDType 1 Y The identifier of an encounter associated with the subject. SubjectID BIASIDType 1 Y A system unique identifier for a subject. BIASIdentity 1 Y Identifies the subject or.. ResponseStatus Identity EncounterID Biasprofile-1. Return ReturnCode 1 Y The return code indicates the return status of the operation. identifies the encounter ID assigned to a new encounter.0-cd-01 Copyright © OASIS Open 2009... and includes the biometric data to store. BiometricData BIASBiometricDataType 1 Y An Identity’s biometric data.1 N The identifier of an encounter associated with the subject. a subject and an encounter. EncounterID BIASIDType 0.. BIASIdentity 0. CBEFF_BIR_Type 1.1 N Identifies the user or instance of the requesting application.1 C In an encounter-centric model.Field Type # ? Meaning ApplicationUser ApplicationUserIdentifier 0. BIASOperationName string 0. ResponseStatus 1 Y Returned status for the operation. Message string 0. 20 October 2009 Page 59 of 152 . Identity BIRList BIR 576 Response Message Field Type # SetBiometricDataResponse ? Meaning Y The response to a SetBiometricData operation. All Rights Reserved.. CBEFF_BIR_ListType 1 Y A list of CBEFF-BIR elements.

GenericRequestParameters 0. etc..577 4. TransformControl string 0. All Rights Reserved. Application ApplicationIdentifier 0.1 N Common request parameters that can be used to identify the requester.1 N Identifies the requesting application. BIASOperationName string 0.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. Biasprofile-1.1 N Identifies the BIAS operation that is being requested: “TransformBiometricDat a”. 583 NOTE: The values for TransformOperation and TransformControl are implementation specific. TransformOperation unsignedLong 1 Y Value indicating the type of transformation to perform. GenericRequestParameters Note: This could be a compression ratio. ApplicationUser ApplicationUserIdentifier 0..1 N Identifies the user or instance of the requesting application. 582 Request Message Field Type # TransformBiometricDataRequest ? Meaning Y Transforms or processes a given biometric in one format into a new target format. 20 October 2009 Page 60 of 152 .1 N Specifies controls for the requested transform operation. InputBIR CBEFF_BIR_Type 1 Y Data structure containing the biometric information to be transformed.1.. target data format...0-cd-01 Copyright © OASIS Open 2009.

. 591 Request Message Field Type # UpdateBiographicDataRequest ? Meaning Y Updates the biographic data for a given subject record. ResponseStatus OutputBIR 585 4. The operation replaces any existing biographic data with the new biographic data. Application ApplicationIdentifier 0. transformed biometric information... Return ReturnCode 1 Y The return code indicates the return status of the operation.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 61 of 152 .584 Response Message Field Type # TransformBiometricDataResponse ? Meaning Y The response to a TransformBiometricData operation..20 UpdateBiographicData 586 UpdateBiographicDataRequest 587 UpdateBiographicDataResponse 588 589 590 The UpdateBiographicData operation updates the biographic data for an existing subject record. the encounter ID MUST be specified..1 N Identifies the BIAS operation that is being requested: “UpdateBiographic Data”. BIASOperationName string 0. In the encounter-centric model. GenericRequestParameters Biasprofile-1. GenericRequestParameters 0. ApplicationUser ApplicationUserIdentifier 0.1 N A short message corresponding to the return code. Message string 0.1 N Identifies the user or instance of the requesting application.1 N Common request parameters that can be used to identify the requester..1. ResponseStatus 1 Y Returned status for the operation. CBEFF_BIR_Type 0. All Rights Reserved.1 N Data structure containing the new.1 N Identifies the requesting application.

. Identity Required for encounter-centric models. BiographicDataType BiographicData 1 Y An Identity’s biographic data.0-cd-01 Copyright © OASIS Open 2009. and includes the biographic data to update. Return ReturnCode 1 Y The return code indicates the return status of the operation.. Message string 0..* C A single biographic data element. EncounterID BIASIDType 0. SubjectID BIASIDType 1 Y A system unique identifier for a subject. 20 October 2009 Page 62 of 152 . 592 LastName string 0. All Rights Reserved.. Response Message Field Type # UpdateBiographicDataResponse ? Meaning Y The response to an UpdateBiographicData operation. ResponseStatus Biasprofile-1. BiographicDataItem BiographicDataItemType 0.1 N A short message corresponding to the return code..1 C A set of biographic data information. a subject and an encounter..1 C The last name of a subject.1 C The first name of a subject. One of the following elements MUST be present.1 C The identifier of an encounter associated with the subject.Field Type # ? Meaning BIASIdentity 1 Y Identifies the subject or. in the encounter-centric model. BiographicDataSet BiographicDataSetType 0. FirstName string 0. ResponseStatus 1 Y Returned status for the operation.

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

Y

Updates a single
biometric sample for a
given subject record.

GenericRequestParameters

0..1

N

Common request
parameters that can be
used to identify the
requester.

Application

ApplicationIdentifier

0..1

N

Identifies the requesting
application.

ApplicationUser

ApplicationUserIdentifier

0..1

N

Identifies the user or
instance of the
requesting application.

BIASOperationName

string

0..1

N

Identifies the BIAS
operation that is being
requested:
“UpdateBiometricData”.

BIASIdentity

1

Y

Identifies the subject or,
in the encounter-centric
model, a subject and an
encounter, and includes
the biometric data to
update.

SubjectID

BIASIDType

1

Y

A system unique
identifier for a subject.

EncounterID

BIASIDType

0..1

C

The identifier of an
encounter associated
with the subject.

GenericRequestParameters

Identity

Required for encountercentric models.
BiometricData
BIR

BIASBiometricDataType

1

Y

An Identity’s biometric
data.

CBEFF_BIR_Type

1

Y

Contains biometric
information in either a
non-XML or an XML
representation.

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 63 of 152

Field
Merge

602

Type

#

?

Meaning

boolean

0..1

N

Value indicating if the
input biometric sample
should be merged with
any existing biometric
information.

Response Message
Field

Type

#

UpdateBiometricDataResponse

?

Meaning

Y

The response to an
UpdateBiometricData operation.

ResponseStatus

1

Y

Returned status for the
operation.

Return

ReturnCode

1

Y

The return code indicates the
return status of the operation.

Message

string

0..1

N

A short message corresponding
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

Y

Performs a 1:1
verification match
between a given
biometric and either a
claim to identity in a
given gallery or another
given biometric.

GenericRequestParameters

0..1

N

Common request
parameters that can be
used to identify the
requester.

Application

ApplicationIdentifier

0..1

N

Identifies the requesting
application.

ApplicationUser

ApplicationUserIdentifier

0..1

N

Identifies the user or
instance of the
requesting application.

GenericRequestParameters

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 64 of 152

Field
BIASOperationName

GalleryID

Type

#

?

Meaning

string

0..1

N

Identifies the BIAS
operation that is being
requested:
“VerifySubject”.

BIASIDType

0..1

C

The identifier of the
gallery or population
group of which the
subject must be a
member.
Required if an Identity
Claim is provided.

Identity

IdentityClaim

BIASIdentity

1

Y

Includes the identifying
information and/or input
and reference biometric
samples.

BIASIDType

0..1

C

An identifier by which a
subject is known to a
particular gallery or
population group.
Required if a Reference
BIR is not provided.

BIASBiometricDataType

1

Y

An Identity’s biometric
data.

InputBIR

CBEFF_BIR_Type

1

Y

Maps to specific
INCITS BIAS elements
as required by that
specification.

ReferenceBIR

CBEFF_BIR_Type

0..1

C

Maps to specific
INCITS BIAS elements
as required by that
specification.

BiometricData

Required if an Identity
Claim is not provided.
610

Response Message
Field

Type

#

VerifySubjectResponse

?

Meaning

Y

The response to a VerifySubject
operation.

ResponseStatus

1

Y

Returned status for the
operation.

Return

ReturnCode

1

Y

The return code indicates the
return status of the operation.

Message

string

0..1

N

A short message corresponding
to the return code.

ResponseStatus

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 65 of 152

Field

Type

#

?

Meaning

Match

boolean

0..1

N

Indicates if the Input BIR
matched either the biometric
information associated with the
Identity Claim or the Reference
BIR.

Score

Score

0..1

N

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

Y

Adds a new subject or,
in an encounter-centric
model, a new
encounter to the
system.

GenericRequestParameters

0..1

N

Common request
parameters that can be
used to identify the
requester.

Application

ApplicationIdentifier

0..1

N

Identifies the requesting
application.

ApplicationUser

ApplicationUserIdentifier

0..1

N

Identifies the user or
instance of the
requesting application.

BIASOperationName

string

0..1

N

Identifies the BIAS
operation that is being
requested: “Enroll”.

ProcessingOptionsType

1

Y

Options that guide how
the aggregate service
request is processed.

string

0..*

N

An option supported by
the implementing
system.

GenericRequestParameters

ProcessingOptions

Option

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 66 of 152

1 N Identifies the user or instance of the requesting application.. GenericRequestParameters 0..0-cd-01 Copyright © OASIS Open 2009. If the Enroll operation is implemented as an asynchronous service. All Rights Reserved. GenericRequestParameters Biasprofile-1.1 N Common request parameters that can be used to identify the requester. Response Message Field Type # EnrollResponse ? Meaning Y The response to an Enroll operation. Return ReturnCode 1 Y The return code indicates the return status of the operation. then it MUST also implement the GetEnrollResults operation.2.1 N A short message corresponding to the return code.Field InputData 623 Type # ? Meaning InformationType 1 Y Contains the input data for the operation. ResponseStatus 1 Y Returned status for the operation. as required by the implementing system.2 GetEnrollResults 625 GetEnrollResultsRequest 626 GetEnrollResultsResponse 627 628 629 630 The GetEnrollResults operation retrieves the enrollment results for the specified token..1 N Identifies the requesting application. ApplicationUser ApplicationUserIdentifier 0. 633 Request Message Field Type # GetEnrollResultsRequest ? Meaning Y Retrieves the enrollment results for the specified token. 631 632 If the service provider implements an asynchronous Enroll operation. This operation is used in conjunction with the Enroll operation. InformationType 0... ResponseStatus ReturnData 624 4. 20 October 2009 Page 67 of 152 . the implementing system returns a token and the GetEnrollResults operation is used to poll for the results of the original Enroll request.1 N Contains the output data for the response. Message string 0. Application ApplicationIdentifier 0.

All Rights Reserved.1 N Contains the output data for the response.1 N Identifies the BIAS operation that is being requested: “GetEnrollResults”. TokenValue string 1 Y A value returned by the implementing system that is used to retrieve the results to an operation at a later time.Field Type # ? Meaning string 0. Expiration date 1 Y 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 68 of 152 .0-cd-01 Copyright © OASIS Open 2009. ResponseStatus ReturnData 635 4.. If the Identify operation is implemented as an asynchronous service. Message string 0. TokenType 1 Y A value used to retrieve the results of the Enroll request. InformationType 0. 642 643 If the service provider implements an asynchronous Identify operation. then it MUST also implement the GetIdentifyResults operation.3 GetIdentifyResults 636 GetIdentifyResultsRequest 637 GetIdentifyResultsResponse 638 639 640 641 The GetIdentifyResults operation retrieves the identification results for the specified token. BIASOperationName Token 634 Response Message Field Type # GetEnrollResultsResponse ? Meaning Y The response to a GetEnrollResults operation.2.. 644 Biasprofile-1. This operation is used in conjunction with the Identify operation. the implementing system returns a token and the GetIdentifyResults operation is used to poll for the results of the original Identify request.1 N A short message corresponding to the return code. ResponseStatus 1 Y Returned status for the operation.. Return ReturnCode 1 Y The return code indicates the return status of the operation.

Application ApplicationIdentifier 0... InformationType 0.1 N Contains the output data for the response. ApplicationUser ApplicationUserIdentifier 0. ResponseStatus ReturnData Biasprofile-1. 20 October 2009 Page 69 of 152 . ResponseStatus 1 Y Returned status for the operation.0-cd-01 Copyright © OASIS Open 2009. Expiration date 1 Y A date and time at which point the token expires and the operation results are no longer guaranteed to be available. GenericRequestParameters Token 646 ? Response Message Field Type # GetIdentifyResultsResponse ? Meaning Y The response to a GetIdentifyResults operation. TokenType 1 Y A value used to retrieve the results of the Identify request. TokenValue string 1 Y A value returned by the implementing system that is used to retrieve the results to an operation at a later time.645 Request Message Field Type # GetIdentifyResultsRequest Meaning Y Retrieves the identification results for the specified token GenericRequestParameters 0.1 N Common request parameters that can be used to identify the requester. BIASOperationName string 0...1 N Identifies the user or instance of the requesting application... All Rights Reserved. Message string 0. Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N Identifies the requesting application.1 N A short message corresponding to the return code.1 N Identifies the BIAS operation that is being requested: “GetIdentifyResults”.

654 655 If the service provider implements an asynchronous Verify operation. the implementing system returns a token and the GetVerifyResults operation is used to poll for the results of the original Verify request.647 4..1 N Identifies the user or instance of the requesting application. 20 October 2009 Page 70 of 152 . All Rights Reserved. TokenValue string 1 Y A value returned by the implementing system that is used to retrieve the results to an operation at a later time. ApplicationUser ApplicationUserIdentifier 0.1 N Common request parameters that can be used to identify the requester. BIASOperationName string 0. This operation is used in conjunction with the Verify operation.2. then it MUST also implement the GetVerifyResults operation. Expiration date 1 Y A date and time at which point the token expires and the operation results are no longer guaranteed to be available. GenericRequestParameters Token Biasprofile-1.. If the Verify operation is implemented as an asynchronous service..1 N Identifies the requesting application. 656 Request Message Field Type # GetVerifyResultsRequest ? Meaning Y Retrieves the verification results for the specified token GenericRequestParameters 0. Application ApplicationIdentifier 0.. TokenType 1 Y A value used to retrieve the results of the Verify request.1 N Identifies the BIAS operation that is being requested: “GetVerifyResults”.0-cd-01 Copyright © OASIS Open 2009.4 GetVerifyResults 648 GetVerifyResultsRequest 649 GetVerifyResultsResponse 650 651 652 653 The GetVerifyResults operation retrieves the verification results for the specified token.

20 October 2009 Page 71 of 152 .657 Response Message Field Type # GetVerifyResultsResponse ? Meaning Y The response to a GetVerifyResults operation. GenericRequestParameters 0.. Match boolean 0. If the Identify operation is implemented as a synchronous service. ResponseStatus 1 Y Returned status for the operation. ApplicationUser ApplicationUserIdentifier 0.2..1 N The score if the biometric information matched. In this case. All Rights Reserved.. GenericRequestParameters Biasprofile-1.. ResponseStatus 658 4. 667 Request Message Field Type # IdentifyRequest ? Meaning Y Performs an identification function.1 N Contains the output data for the response.1 N Identifies the user or instance of the requesting application. the GetIdentifyResults operation is used to poll for the results of the Identify request. which is an indication that the request is being handled asynchronously.0-cd-01 Copyright © OASIS Open 2009. Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N Identifies the requesting application. If the Identify operation is implemented as an asynchronous service.1 N Common request parameters that can be used to identify the requester.1 N A short message corresponding to the return code.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. Message string 0.. ReturnData InformationType 0. the implementing system immediately processes the request and returns the results in the Return Data parameter. the implementing system returns a token in the Return Data parameter..1 N Indicates if the Input BIR matched either the biometric information associated with the Identity Claim or the Reference BIR.. Score Score 0. Application ApplicationIdentifier 0.

this operation can be used to retrieve biographic and/or biometric information for either a single encounter or all encounters. In a person-centric model. Response Message Field Type # IdentifyResponse ? Meaning Y The response to an Identify operation. ResponseStatus 1 Y Returned status for the operation. or in an encountercentric model about an encounter.0-cd-01 Copyright © OASIS Open 2009. Return ReturnCode 1 Y The return code indicates the return status of the operation. N Common request parameters that can be used to identify the requester. All Rights Reserved.Field BIASOperationName ProcessingOptions Option InputData 668 Type # ? Meaning string 0.. InformationType 0... Either a subject ID or encounter ID MUST be specified.6 RetrieveInformation 670 RetrieveInformationRequest 671 RetrieveInformationResponse 672 673 674 675 676 The RetrieveInformation operation retrieves requested information about a subject. Message string 0. 677 Request Message Field Type # RetrieveInformationRequest GenericRequestParameters GenericRequestParameters Biasprofile-1. 20 October 2009 Page 72 of 152 .* N An option supported by the implementing system. string 0.1 N Contains the output data for the response. ProcessingOptionsType 1 Y Options that guide how the aggregate service request is processed.1 N Identifies the BIAS operation that is being requested: “Identify”.1 ? Meaning Y Retrieves requested information about a subject or encounter.. In an encounter-centric model.. this operation can be used to retrieve both biographic and biometric information for a subject record. 0.2. InformationType 1 Y Contains the input data for the aggregate services.1 N A short message corresponding to the return code. ResponseStatus ReturnData 669 4.

1 C The identifier of an encounter associated with the subject. Message string 0. EncounterID BIASIDType 0.1 N A short message corresponding to the return code. Return ReturnCode 1 Y The return code indicates the return status of the operation.. BIASIDType 0. BIASOperationName string 0. ProcessingOptions Option Identity SubjectID Required if an Encounter ID is not provided... BIASIdentity 1 Y Includes the identifier of the subject or encounter.. ResponseStatus 1 Y Returned status for the operation..* N An option supported by the implementing system. All Rights Reserved. Required if a Subject ID is not provided.Field Type # ? Meaning Application ApplicationIdentifier 0. ProcessingOptionsType 1 Y Options that guide how the aggregate service request is processed.1 N Identifies the user or instance of the requesting application. 20 October 2009 Page 73 of 152 .1 N Identifies the BIAS operation that is being requested: “RetrieveInformation”. InformationType 0.1 N Contains the output data for the response.. and MAY identify what type(s) of information should be returned..1 N Identifies the requesting application. ApplicationUser ApplicationUserIdentifier 0. string 0. 678 Response Message Field Type # RetrieveInformationResponse ? Meaning Y Response to a RetrieveInformation operation..1 C A system unique identifier for a subject.0-cd-01 Copyright © OASIS Open 2009. ResponseStatus ReturnData Biasprofile-1.

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

Y

Performs a 1:1
verification function.

GenericRequestParameters

0..1

N

Common request
parameters that can be
used to identify the
requester.

Application

ApplicationIdentifier

0..1

N

Identifies the requesting
application.

ApplicationUser

ApplicationUserIdentifier

0..1

N

Identifies the user or
instance of the
requesting application.

BIASOperationName

string

0..1

N

Identifies the BIAS
operation that is being
requested: “Verify”.

ProcessingOptionsType

1

Y

Options that guide how
the aggregate service
request is processed.

string

0..*

N

An option supported by
the implementing
system.

InputData

InformationType

1

Y

Contains the input data
for the aggregate
services.

Identity

BIASIdentity

1

Y

Includes either the
Identity Claim or
Reference BIR.

BIASIDType

0..1

C

An identifier by which a
subject is known to a
particular gallery or
population group.

GenericRequestParameters

ProcessingOptions

Option

IdentityClaim

Required if a Reference
BIR is not provided.

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 74 of 152

Field
BiometricData
ReferenceBIR

Type

#

?

Meaning

BIASBiometricDataType

0..1

N

An Identity’s biometric
data.

CBEFF_BIR_Type

0..1

C

Maps to specific
INCITS BIAS elements
as required by that
specification.
Required if an Identity
Claim is not provided.

GalleryID

BIASIDType

0..1

C

The identifier of the
gallery or population
group of which the
subject must be a
member.
Required if an Identity
Claim is provided.

690

Response Message
Field

Type

#

VerifyResponse

?

Meaning

Y

The response to a Verify
operation.

ResponseStatus

1

Y

Returned status for the
operation.

Return

ReturnCode

1

Y

The return code indicates the
return status of the operation.

Message

string

0..1

N

A short message corresponding
to the return code.

ReturnData

InformationType

0..1

N

Contains the output data for the
response.

Match

boolean

0..1

N

Indicates if the Input BIR
matched either the biometric
information associated with the
Identity Claim or the Reference
BIR.

Score

Score

0..1

N

The score if the biometric
information matched.

ResponseStatus

691

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

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.

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 76 of 152

720 • Basic usage/formatting rules (beyond WS-I) will be defined. an identify operation can be implemented as either a synchronous or asynchronous service as follows: 742 service provider client service provider client IdentifySubject () Return. 736 737 738 739 740 741 The system model used for BIAS conversations over SOAP is a simple request-response model.1.1 faults and fault codes are discussed in [SOAP11] section 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. If a BIAS responder cannot. CandidateList 743 744 (a) Synchronous Operation (b) Asynchronous Operation Figure 5.) and non-secure implementations. SAML. 727 728 • Generic biometric operations will be defined – use of biometrics within a Web services authentication protocol is not addressed. (SOAP 1. 731 5.) 756 757 3. etc. for some reason. it MUST generate a SOAP fault.e. For example. BIAS comprises both synchronous and asynchronous operations. The BIAS requester MUST NOT include more than one BIAS request per SOAP message or include any additional XML elements in the SOAP body. the BIAS requester MUST NOT send a fault code or other error messages to the BIAS responder. The BIAS responder MUST return either a BIAS response element within the body of another SOAP message or generate a SOAP fault. 20 October 2009 Page 77 of 152 .2 Message requirements 732 733 734 735 BIAS SOAP messages MUST conform to [WS-I-Basic] and [WS-I-Bind]. using existing security mechanisms such as WSSecurity. All Rights Reserved. 729 730 • OASIS namespace rules will be followed. 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). The BIAS responder MUST NOT include more than one BIAS response per SOAP message or include any additional XML elements in the SOAP body. 721 • Existing biometric and Web services standards will be leveraged wherever possible. there are separate messages to request the operation and to request the results of the operation. Asynchronous operations are implemented through message pairs. 725 726 • BIAS will support both secure (i. These have been defined for those operations that are likely to take significant time to complete. 722 • Sample WSDL and use cases will be provided as an aid in implementation.. process a BIAS request. Token GetIdentifySubjectResults (Token) Return. with the majority being of the former type. On receiving a BIAS response in a SOAP message. That is.0-cd-01 Copyright © OASIS Open 2009. A single BIAS SOAP message MUST contain only one BIAS service request (or single BIAS service response). CandidateList IdentifySubject () Return. Since the format for the message Biasprofile-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. though some external schemas MAY also be referenced. 751 752 753 754 755 2. 723 724 • Use of basic SOAP will allow all other compatible WS* standards (and discovery mechanisms) to be used in conjunction with BIAS messaging.

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.. etc.e. 796 5. even an XML_BIR as defined within [CBEFF] Part 3. 760 761 762 SOAP 1. biometric data.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. adding additional items such as error conditions would needlessly complicate the protocol. galleries. <xs:element name="bdb" type="xs:base64Binary" minOccurs="0"/> 786 787 or contain an element which is binary (e. BinaryBIR of type base64binary. Data elements using this method are indicated as such in the schema. however. This system is not used within the BIAS SOAP binding. MIME) which contains that ”stripped” content via an xop:include. it is REQUIRED that the BIAS implementation include the QueryCapabilities operation to provide dynamic information regarding BIAS capabilities.3 Handling binary data 768 769 BIAS messages frequently contain binary data (e. scanned identity documents.3. 779 780 <xsd:element name="BinaryBIR" type="xs:base64Binary" /> 781 782 783 784 785 However.g. there is a possibility of mismatch if the transmitter supports and uses XOP but the receiver does not. options.1 also defines an optional data encoding system. All Rights Reserved. that are supported.g. 793 794 795 Use of XOP is generally transparent to the developer.. BIAS requesters SHOULD generate SOAP documents referencing only the final XML schema namespace. Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. 763 764 765 766 NOTE: [SOAP11] references an early draft of the XML Schema specification including an obsolete namespace. Most frameworks support this.3. 20 October 2009 Page 78 of 152 . contains a biometric data block (BDB) which may be entirely binary (most common). an image within an XML BDB). other than in how they configure their toolset. as one of the BIR types. 767 5.758 759 interchange is a simple request-response pattern. 800 801 In addition.. 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). 788 5. the binary content is replaced with a reference (URI) to an attachment (i. 777 778 As an example. the CBEFF_BIR_Type includes. 773 5. Two methods are provided for dealing with this: 770 • Embedded Base64 encoding 771 • XOP [XOP] 772 Use of SOAP with Attachments (SWA) is deprecated.2 Use of XOP 789 790 791 792 When XOP is used. BIAS responders MUST be able to process both the XML schema namespace used in [SOAP11] as well as the final XML schema namespace.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. etc.).

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>. however. 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. Adoption of this option also requires that the WS-Addressing ‘To’. The WS-Addressing ‘Action’ element is used to indicate the intent of the message.5.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.oasis‐open.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).org/2003/05/soap-envelope”> 824 <soap:Body> 825 826 <tns:CreateSubjectRequest xmlns:tns=”http://docs.w3.1 818 Host: www. Biasprofile-1.acme. 815 An example of this method for the CreateSubject operation is shown below: 816 817 POST /bias HTTP/1. ‘ReplyTo’. The receiver (service provider) can search for this tag within a received BIAS SOAP message to determine what operation is being requested.802 5. 20 October 2009 Page 79 of 152 .com 819 Content-Type: application/soap+xml. there are no restrictions on the format or specificity of the URI/IRI nor a requirement that it can be resolved. as they are mandatory elements in a request-reply message pattern as used within BIAS.0-cd-01 Copyright © OASIS Open 2009. charset=”utf-8” 820 Content-Length: nnnn 821 SOAPAction: “” 822 <?xml version=”1.0”?> 823 <soap:Envelope xmlns:soap=”http://www. The information is in the SOAP Header. There is no requirement related to the ordering of this element within the message. The value is a URI/IRI identifying that intent.5. 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.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. All Rights Reserved. and ‘MessageID’ elements are supplied.org/bias/bias‐1. though it is RECOMMENDED that it be included early in the message to aid in human readability.

Other mechanisms such as Signed XML or WSS [WSS] could also be implemented. The client MUST establish server identity Biasprofile-1.0 [SSL3] or TLS1.509 v3 certificate [X509]. ‘RelatesTo’ (matching the ‘MessageID’ element in the request).xmlsoap.w3. in any BIAS binding’s use of SSL 3.0 888 889 Unless otherwise specified. the following security statements apply to all BIAS bindings. However. 886 Unless stated otherwise. All Rights Reserved. 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.0/” /> </soap:Body> </soap:Envelope> 879 880 5.846 847 848 Response messages would also need to use WS-Addressing.6.0”?> 862 <soap:Envelope xmlns:soap=”http://www.oasis‐open. 20 October 2009 Page 80 of 152 . when BIAS is used within an environment using WS-Addressing.org/bias/bias‐1.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.1 Use of SSL 3.0 [RFC2246].1. either alone or in combination with the BIASOperationName approach described in section 5.0-cd-01 Copyright © OASIS Open 2009.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 <tns:CreateSubjectRequest xmlns:tns=”http://docs. servers MUST authenticate clients using a X. and ‘RelationshipType’ (default value to “wsa:Reply”) elements. 854 An example for a message request for the CreateSubject operation would look like the following: 855 856 POST /bias HTTP/1. it is RECOMMENDED that this approach for use of the ‘Action’ field to carry the BIAS operation name is employed.acme. 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.4. requiring the ‘To’ (matching the ‘ReplyTo’ element in the request).1 857 Host: www. charset=”utf-8” 859 Content-Length: nnnn 860 SOAPAction: “” 861 <?xml version=”1.0 or TLS 1.com 858 Content-Type: application/soap+xml.org/2003/05/soap-envelope” 863 864 865 xmlns:wsa=”http://schemas. 887 5.

this is indicated in the BIR header. 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. See INCITS 442.6. The security layer in the underlying substrate protocol or a mechanism at the SOAP message exchange layer MAY be used to ensure message integrity. Use of these mechanisms alone may not be sufficient for end-to-end integrity and confidentiality. etc. 895 5.3 for further discussion. biometric data is transferred within a CBEFF BIR (as defined in ISO/IEC 19785-1). 933 Many of the security considerations identified in [SAML SEC] MAY also apply.5 CBEFF BIR security features 919 920 921 922 923 924 925 Within BIAS. message authentication is RECOMMENDED.6 Security Considerations 927 928 929 Before deployment.5.0-cd-01 Copyright © OASIS Open 2009. and/or other security related data. If implemented.g..6. 914 915 Transport confidentiality will not meet end-to-end confidentiality requirements in bindings where the BIAS SOAP message passes through an intermediary.6. 930 Special care should be given to the impact of possible caching on security. The security layer in the underlying substrate protocol or a mechanism at the SOAP message exchange layer MAY be used to ensure message confidentiality. The BIR structure defines an optional Security Block which MAY contain a digital signature (or message authentication code). Biasprofile-1. 916 917 NOTE: Biometric and biographic data is likely to contain personal information the confidentiality of which SHOULD be protected accordingly.). each combination of authentication. and confidentiality mechanisms SHOULD be analyzed for vulnerability in the context of the specific protocol exchange and the deployment environment. 910 5. CBEFF provides for the optional encryption of the Biometric Data Block (BDB) of the BIR and for the integrity of the entire BIR. etc. 931 932 IETF RFC 2617 [RFC2617] describes possible attacks in the HTTP environment when basic or message digest authentication schemes are used. 904 5. subjectAltName attribute.5. 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.4 below). 20 October 2009 Page 81 of 152 .4 Message Confidentiality 911 912 913 Message confidentiality of both BIAS requests and BIAS responses is OPTIONAL and depends on the environment of use. algorithm.3 Message Integrity 905 906 907 Message integrity of both BIAS requests and BIAS responses is OPTIONAL and depends on the environment of use. message integrity is RECOMMENDED. section 6. 926 5. key name. 903 Note that SAML [SAML] MAY be used as the mechanism for parties to authenticate to one another. All Rights Reserved.3 and 5. encryption parameters (e. 892 893 894 Use of transport level security in the form of SSL or TLS is OPTIONAL but highly RECOMMENDED.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. message integrity. Such protections are associated with an individual BIR and are separate from any other protections provided at the message level.6.6.).890 891 based on contents of the certificate (typically through examination of the certificate’s subject DN field. 918 5. however (see 5. in many bindings the SSL/TLS or HTTP protocol) MAY be utilized to provide data origin authentication.

5. In some cases further tailoring or profiling of this standard may be required in order to further constrain the implementation options available. SSL. 947 5. CBEFF BIR encryption. Some may be normative while others can be optionally applied (i.5. 960 961 962 NOTE: As an example.5 mandatory rather than optional. and confidentiality of biometric information during transmission and storage. it does not guarantee interoperability in a specific application. 938 939 940 941 942 NOTE: The requirements of ISO/IEC 19092.g.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. though useful across many application domains.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.) 965 • Choice of operation name identification method 966 • Choice of BIR type to be used (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.. WS-Notification). WS-Security.0-cd-01 Copyright © OASIS Open 2009.e. 20 October 2009 Page 82 of 152 . This is highly RECOMMENDED for any high security environment or where privacy concerns exist. 956 5. All Rights Reserved. It is the purview of the BIAS service provider to implement security mechanisms and protect data at rest as per their own security policies..g. 950 5. However.g. are required for most biometric system implementations in the financial services environment. base version that would preclude the use of such standards in the future.6. WS-Addressing). etc. whereas a given application/domain MAY wish to limit this to a small set or just one of each type.8 Tailoring 957 958 959 This standard provides for a common method of implementing biometric Web services.8 Key Management 948 949 This specification does not address key management considerations with respect to implementation of cryptographic security mechanisms (e.g. Application of this standard would make the requirements of sections 5. Transform oprerations/controls) Biasprofile-1.. for authenticity. however. this is left to a future revision. integrity.6. the intent is to avoid specifying anything in the first. 943 5.7 Security of Stored Data 944 945 946 This specification does not address security considerations for stored data. or confidentiality).3 through 5. BIAS allows for a number of different biographic and biometric data formats to be used.. non-XML. 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. Still others may require additional profiling to be used in an interoperable manner (e.. These SHOULD be considered as part of an overall risk management approach. authenticity.

The INCITS BIAS standard defines the error condition codes for system-level errors.2 for additional information on message returns and faults. as described by the BIASFault element (see section 3.2. Service-level errors occur when there is a problem transmitting or representing the service request. a response message (containing a return code) will be generated. 983 6. Instead a SOAP fault message is returned. a SOAP fault message (containing a fault code) will be generated.5. a response (service output) will be sent to the requester by the service provider. 974 975 976 977 978 979 980 • • System-level errors occur when the implementing system cannot service a request.38) along with any response data as defined for that operation.2. The fault message MUST contain a Detail element in a common format. 1000 NOTE: See also section 5. They could result due to an internal logic error or because the implementing system does not support a particular request. The fault message contains a FaultCode element as defined by the SOAP 1. Note that BIAS service providers MAY define additional fault codes unique to their service. All Rights Reserved.1 BIAS operation return codes 984 985 986 987 If a BIAS operation is successful. Each response message contains a response status (see section 3.2.6).5). “BIASFaultMessage” and “BIASFaultDescription” elements.2 SOAP fault codes 989 990 If a BIAS operation is unsuccessful.37) and return code (see section 3. 998 999 The list of defined BIAS fault codes is provided in section 3.972 6 Error handling 973 There are two levels of errors that can be returned in an error response: system and service errors.1 specification (see section 3. 981 • If successful. 982 • If unsuccessful. A response code of ‘0’ indicates success. 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. “BIASFaultType”. 20 October 2009 Page 83 of 152 .0-cd-01 Copyright © OASIS Open 2009. no BIAS response message is sent. 988 6.2. if any.2. 996 997 The schema provided in Annex A defines “BIASFaultCode” and “BIASFaultDetail” types as well as “BIASFault”. Biasprofile-1. They could result due to an invalid service request or because of a communications error.

4. For each class. 20 October 2009 Page 84 of 152 . however. 5 and 6. at a minimum. all mandatory requirements and provisions set forth in Clauses 3. 1017 1018 1019 There are no minimum set of operations required to be implemented by BIAS requesters. 1006 1007 1008 INCITS 442 [INCIS-BIAS] (Annex A) specifies five BIAS conformance classes. these requirements and provisions MUST be implemented as set forth in these Clauses. MUST implement. 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. 4. 1016 These conformance classes and their associated requirements apply to this BIAS SOAP Profile.1001 7 Conformance 1002 1003 1004 1005 Implementations claiming conformance to this standard. Biasprofile-1. a set of mandatory BIAS operations is identified in order for implementations (BIAS service providers) to claim conformance.0-cd-01 Copyright © OASIS Open 2009. 5 and 6. 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. 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. All Rights Reserved. If such implementations claim conformance to any OPTIONAL requirements and provisions stated in Clauses 3.

org/bias/ns/bias‐1.7.0.</xsd:documentation>          </xsd:annotation>          <xsd:complexContent>            <xsd:extension base="tns:ResponseTemplate">              <xsd:sequence>                <xsd:element name="ReturnData" type="tns:InformationType" minOccurs="0" maxOccurs="1">                  <xsd:annotation>                    <xsd:documentation>Contains the output data for the aggregate service response.0-cd-01 Copyright © OASIS Open 2009.19785.xmlsoap.oasis‐open.org/wsdl/soap/" xmlns:http="http://schemas.w3.org/bias/ns/bias‐ 1.</xsd:documentation>          </xsd:annotation>          <xsd:complexContent>            <xsd:extension base="RequestTemplate">              <xsd:sequence>                <xsd:element name="ProcessingOptions" type="ProcessingOptionsType" minOccurs="1" maxOccurs="1">                  <xsd:annotation>                    <xsd:documentation>Options that guide how the aggregate service request is  processed.xmlsoap.257.org/2001/XMLSchema" elementFormDefault="qualified"  targetNamespace="http://docs. All Rights Reserved.0/">    <wsdl:types>      <xsd:schema xmlns:xsd="http://www.0" encoding="UTF‐8"?>    <wsdl:definitions xmlns:wsdl="http://schemas.oasis‐open.1.1020 Annex A.</xsd:documentation>                  </xsd:annotation>                </xsd:element>              </xsd:sequence>            </xsd:extension>          </xsd:complexContent>        </xsd:complexType>        <xsd:complexType name="AggregateResponseTemplate" abstract="true">          <xsd:annotation>            <xsd:documentation>Base template for BIAS aggregate service responses.</xsd:documentation>                  </xsd:annotation>                </xsd:element>                <xsd:element name="InputData" type="InformationType" minOccurs="1" maxOccurs="1">                  <xsd:annotation>                    <xsd:documentation>Contains the input data for the aggregate service request.org/bias/ns/bias‐1.1.xmlsoap.org/2001/XMLSchema" xmlns:iso‐iec19785‐3‐7="urn:oid:1.0"  xmlns:tns="http://docs. 20 October 2009 Page 85 of 152 .0/" targetNamespace="http://docs.</xsd:documentation>                  </xsd:annotation>                </xsd:element>              </xsd:sequence>            </xsd:extension>          </xsd:complexContent>        </xsd:complexType>        <xsd:simpleType name="ApplicationIdentifier">  Biasprofile-1.0/">        <xsd:complexType name="AggregateRequestTemplate" abstract="true">          <xsd:annotation>            <xsd:documentation>Base template for BIAS aggregate service requests.org/wsdl/"  xmlns:soap="http://schemas.w3. 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 <?xml version="1.oasis‐open.org/wsdl/http/"  xmlns:xsd="http://www.

</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiometricDataList" type="tns:BiometricDataListType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A list of biometric data elements. All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="InputBIR" type="tns:CBEFF_BIR_Type" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Maps to specific INCITS BIAS elements as required by that  specification.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BIRList" type="tns:CBEFF_BIR_ListType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A list of CBEFF‐BIR elements.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string">            <xsd:minLength value="1" />            <xsd:maxLength value="255" />          </xsd:restriction>        </xsd:simpleType>        <xsd:simpleType name="ApplicationUserIdentifier">          <xsd:annotation>            <xsd:documentation>Identifies an application user or instance. 20 October 2009 Page 86 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="ReferenceBIR" type="tns:CBEFF_BIR_Type" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Maps to specific INCITS BIAS elements as required by that  specification.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>Identifies an application.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BIR" type="tns:CBEFF_BIR_Type" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Contains biometric information in either a non‐XML and an XML  representation.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string">            <xsd:minLength value="1" />            <xsd:maxLength value="255" />          </xsd:restriction>        </xsd:simpleType>        <xsd:complexType name="BIASBiometricDataType">          <xsd:annotation>            <xsd:documentation>Wraps the various BIAS biometric types.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="BIASFaultCode">  Biasprofile-1.

 if used.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="INVALID_BIR">              <xsd:annotation>                <xsd:documentation>The input BIR is empty or in an invalid or unrecognized format.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="UNKNOWN_SUBJECT">              <xsd:annotation>  Biasprofile-1.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="UNSUPPORTED_CAPABILITY">              <xsd:annotation>                <xsd:documentation>A requested capability is not supported by the service  implementation.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="BIR_DECRYPTION_FAILURE">              <xsd:annotation>                <xsd:documentation>The service could not decrypt an encrypted input BIR.0-cd-01 Copyright © OASIS Open 2009. on the input  BIR.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="BIR_QUALITY_ERROR">              <xsd:annotation>                <xsd:documentation>Biometric sample quality is too poor for the service to succeed.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="BIR_SIGNATURE_FAILURE">              <xsd:annotation>                <xsd:documentation>The service could not validate the signature.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:restriction base="xsd:unsignedLong">            <xsd:enumeration value="UNKNOWN_ERROR">              <xsd:annotation>                <xsd:documentation>The service failed for an unknown reason.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="INVALID_INPUT">              <xsd:annotation>                <xsd:documentation>The data in a service input parameter is invalid.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="INVALID_ENCOUNTER_ID">              <xsd:annotation>                <xsd:documentation>The input encounter ID is empty or in an invalid format.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="INVALID_SUBJECT_ID">              <xsd:annotation>                <xsd:documentation>The input subject ID is empty or in an invalid format. All Rights Reserved. 20 October 2009 Page 87 of 152 .

</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="UNKNOWN_IDENTITY_CLAIM">              <xsd:annotation>                <xsd:documentation>The identity referenced by the input identity claim does not exist. 20 October 2009 Page 88 of 152 .0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="UNKNOWN_GALLERY">              <xsd:annotation>                <xsd:documentation>The gallery referenced by the input gallery ID does not exist. All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="UNKNOWN_ENCOUNTER">              <xsd:annotation>                <xsd:documentation>The encounter referenced by the input encounter ID does not  exist.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="NONEXISTANT_DATA">              <xsd:annotation>                <xsd:documentation>The data requested for deletion does not exist.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="INVALID_IDENTITY_CLAIM">              <xsd:annotation>                <xsd:documentation>The identity claim requested is already in use.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>          </xsd:restriction>        </xsd:simpleType>        <xsd:complexType name="BIASFaultDetail">          <xsd:annotation>            <xsd:documentation>Defines the error information associated with a SOAP fault.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element minOccurs="1" maxOccurs="1" name="BIASFaultType" type="tns:BIASFaultCode">              <xsd:annotation>                <xsd:documentation>References an error code.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="UNKNOWN_BIOGRAPHIC_FORMAT">              <xsd:annotation>                <xsd:documentation>The biographic data format is not known or not supported.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element minOccurs="1" maxOccurs="1" name="BIASFaultMessage" type="xsd:string">              <xsd:annotation>                <xsd:documentation>Provides an explanation of the fault.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>The subject referenced by the input subject ID does not exist.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element minOccurs="0" maxOccurs="1" name="BIASFaultDescription" type="xsd:string">              <xsd:annotation>  Biasprofile-1.

</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="EncounterID" type="tns:BIASIDType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The identifier of an encounter associated with the subject. and biometric data. All Rights Reserved. 20 October 2009 Page 89 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiographicDataElements" type="tns:BiographicDataType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>An Identity's biographic data elements that are stored in the implementing  system.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="BIASIdentity">          <xsd:annotation>            <xsd:documentation>              Defines a single element for encapsulating the data associated              with an Identity. required for encounter‐ centric models.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiographicData" type="tns:BiographicDataType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>An Identity's biographic data.              biographic data.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>Provides detailed information about a BIAS fault. such as trace  details.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="EncounterList" type="tns:EncounterListType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A list of encounters associated with a subject.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="SubjectID" type="tns:BIASIDType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A system unique identifier for a subject.</xsd:documentation>              </xsd:annotation>            </xsd:element>  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009.  Includes the Identity's reference identifiers.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="IdentityClaim" type="tns:BIASIDType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>An identifier by which a subject is known to a particular gallery or population  group.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiometricData" type="tns:BIASBiometricDataType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>An Identity's biometric data.

20 October 2009 Page 90 of 152 .g.0” for  NIEM).. INT‐I. HR‐XML. xNAL. All Rights Reserved.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:any namespace="##any">              <xsd:annotation>                <xsd:documentation>Biographic data formatted according to a specific format.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="Type" type="xsd:string" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The data type for the biographic data item.</xsd:documentation>            </xsd:annotation>          </xsd:attribute>          <xsd:attribute name="version" type="xsd:string" use="optional">            <xsd:annotation>              <xsd:documentation>The version of the biographic data format (e. “7.0-cd-01 Copyright © OASIS Open 2009. NIEM.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:simpleType name="BIASIDType">          <xsd:annotation>            <xsd:documentation>A BIAS identifier</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:complexType name="BiographicDataItemType">          <xsd:annotation>            <xsd:documentation>Defines a single biographic data element.</xsd:documentation>              </xsd:annotation>            </xsd:any>          </xsd:sequence>          <xsd:attribute name="name" type="xsd:string" use="required">            <xsd:annotation>              <xsd:documentation>The name of the biographic data format.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="Value" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The value assigned to the biographic data item.1” for FBI‐EFTS or “2. DOD‐EBTS.</xsd:documentation>            </xsd:annotation>  Biasprofile-1. Use these names for common formats: FBI‐EFTS.  FBI‐EBTS.</xsd:documentation>          </xsd:annotation>          <xsd:sequence maxOccurs="unbounded">            <xsd:element name="Name" type="xsd:string" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The name of the biographic data item.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="BiographicDataSetType">          <xsd:annotation>            <xsd:documentation>Defines a set of biographic data that is formatted according to the specified  format.

 formatted set of              biographic information.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:choice>        </xsd:complexType>        <xsd:complexType name="BiometricDataElementType">          <xsd:annotation>            <xsd:documentation>              Provides descriptive information about biometric data.fbibiospecs.hr‐xml. (NIEM) www.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiographicDataSet" type="tns:BiographicDataSetType" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A set of biographic data information.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:attribute name="source" type="xsd:string" use="required">            <xsd:annotation>              <xsd:documentation>Reference to a URI/IRI describing the biographic data format.0-cd-01 Copyright © OASIS Open 2009. (HR‐XML) www. (xNAL)  www.            </xsd:documentation>          </xsd:annotation>          <xsd:choice maxOccurs="unbounded">            <xsd:element name="LastName" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The last name of a subject.org.oasis‐open.. 20 October 2009 Page 91 of 152 . FBI‐EBTS.dod.biometrics. (DOD‐EBTS) www. contained in the BDB of  Biasprofile-1. XML (e. utilizing either the              BiographicDataItemType to represent a list of elements or the              BiographicDataSetType to represent a complete. such as              the biometric type. xNAL.interpol.int.g.org. for  non‐XML versions of FBI‐EFTS. for NIEM.g.niem. All Rights Reserved. subtype.</xsd:documentation>            </xsd:annotation>          </xsd:attribute>          <xsd:attribute name="type" type="xsd:string" use="required">            <xsd:annotation>              <xsd:documentation>The biographic data format type.org.</xsd:documentation>            </xsd:annotation>          </xsd:attribute>        </xsd:complexType>        <xsd:complexType name="BiographicDataType">          <xsd:annotation>            <xsd:documentation>              Defines a set of biographic data elements. For example: (FBI‐EFTS)  www.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiographicDataItem" type="tns:BiographicDataItemType" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>A single biographic data element.mil. and HR‐XML or future version  of FBI‐EBTS).. or INT‐I).gov. Use these types for common formats: ASCII (e. (INT‐I) www.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="FirstName" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The first name of a subject. and format. DOD‐EFTS.

 or other CBEFF  biometric organization that has defined the format for the biometric data.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BiometricDataElement" type="tns:BiometricDataElementType" minOccurs="0"  maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>Data structure containing information about a biometric record.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 92 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             the CBEFF‐BIR.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiometricSubType" type="iso‐iec19785‐3‐7: Subtype" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>More specifically defines the type of biometric data stored in the biometric record.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="BiometricDataListType">          <xsd:annotation>            <xsd:documentation>A list of biometric data elements.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BDBFormatType" type="iso‐iec19785‐3‐7: Registered‐int" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Identifies the specific biometric data format specified by the CBEFF biometric  organization recorded in the BDB Format Owner field. as  defined by CBEFF. working group. All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BDBFormatOwner" type="iso‐iec19785‐3‐7: Registered‐int" minOccurs="1"  maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Identifies the standards body.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BiometricType" type="iso‐iec19785‐3‐7: Multiple‐types" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The type of biological or behavioral data stored in the biometric record. industry consortium.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="CandidateListType">          <xsd:annotation>            <xsd:documentation>  Biasprofile-1.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiometricTypeCount" type="xsd:positiveInteger" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The number of biometric records having the biometric type recorded in the biometric  type field. as defined by  CBEFF.

</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiographicData" type="tns:BiographicDataType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Biographic data associated with the candidate match. All Rights Reserved. utilizing the Candidate Type to              represent each element in the set.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>          <xsd:attribute name="rank" type="xsd:integer" use="required">            <xsd:annotation>              <xsd:documentation>The rank of the candidate in relation to other candidates for the same biometric  identification operation.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Capability" type="tns:CapabilityType" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>A single capability.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BIRList" type="tns:CBEFF_BIR_ListType" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Biometric data associated with the candidate match. 20 October 2009 Page 93 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="CandidateType">          <xsd:annotation>            <xsd:documentation>              Defines a single candidate as a possible match in response to a              biometric identification request.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Score" type="tns:Score" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The match score.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             Defines a set of candidates.</xsd:documentation>            </xsd:annotation>          </xsd:attribute>        </xsd:complexType>        <xsd:complexType name="CapabilityListType">          <xsd:annotation>            <xsd:documentation>Defines a set of capabilities.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Candidate" type="tns:CandidateType" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>A single candidate.</xsd:documentation>              </xsd:annotation>            </xsd:element>  Biasprofile-1.

</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="BiographicDataSet">              <xsd:annotation>                <xsd:documentation>Identifies a biographic data set supported by the implementing  system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="AggregateReturnData">              <xsd:annotation>                <xsd:documentation>A data element returned by the implementing system for the aggregate  services. All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="AggregateProcessingOption">              <xsd:annotation>                <xsd:documentation>A processing option supported by the implementing system for the aggregate  services.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="AggregateInputDataRequired">              <xsd:annotation>                <xsd:documentation>A data element required as input by the implementing system for the aggregate  services.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string">            <xsd:enumeration value="AggregateInputDataOptional">              <xsd:annotation>                <xsd:documentation>A data element accepted as optional input by the implementing system for the  aggregate services.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="ClassificationAlgorithmType">              <xsd:annotation>                <xsd:documentation>A classification algorithm type supported by the implementing  system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="AggregateServiceDescription">              <xsd:annotation>                <xsd:documentation>Describes the processing logic of an aggregate service supported by the implementing  system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="CBEFFPatronFormat">              <xsd:annotation>                <xsd:documentation>A patron format supported by the implementing system.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:simpleType name="CapabilityName">          <xsd:annotation>            <xsd:documentation>A list of capability items.</xsd:documentation>              </xsd:annotation>  Biasprofile-1. 20 October 2009 Page 94 of 152 .0-cd-01 Copyright © OASIS Open 2009.

</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="Gallery">              <xsd:annotation>                <xsd:documentation>A gallery or population group supported by the implementing  system.</xsd:documentation>              </xsd:annotation>            </xsd:element>  Biasprofile-1. 20 October 2009 Page 95 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:enumeration value="ConformanceClass">              <xsd:annotation>                <xsd:documentation>Identifies the conformance class of the BIAS implementation.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="SupportedBiometric">              <xsd:annotation>                <xsd:documentation>A biometric type supported by the implementing system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>          </xsd:restriction>        </xsd:simpleType>        <xsd:complexType name="CapabilityType">          <xsd:annotation>            <xsd:documentation>Defines a single capability supported by an implementing system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="MatchScore">              <xsd:annotation>                <xsd:documentation> Identifies the use of match scores returned by the implementing  system. All Rights Reserved.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="CapabilityName" type="tns:CapabilityName" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The name of the capability.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="QualityAlgorithm">              <xsd:annotation>                <xsd:documentation>A quality algorithm vendor and algorithm vendor product ID supported by the  implementing system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="IdentityModel">              <xsd:annotation>                <xsd:documentation>Identifies whether the implementing system is person‐centric or encounter‐centric  based.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="TransformOperation">              <xsd:annotation>                <xsd:documentation>A transform operation type supported by the implementing  system.

</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BIR" type="tns:CBEFF_BIR_Type" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>CBEFF structure containing information about a biometric sample. All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="CBEFF_BIR_ListType">          <xsd:annotation>            <xsd:documentation>A list of CBEFF‐BIR elements.0-cd-01 Copyright © OASIS Open 2009. with either a non‐XML or XML  representation. 20 October 2009 Page 96 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="CapabilitySupportingValue" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A secondary value supporting the capability.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="CapabilityDescription" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A description of the capability.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="CBEFF_BIR_Type">          <xsd:annotation>            <xsd:documentation>Represents biometric information.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BIR_Information" minOccurs="0" maxOccurs="1">              <xsd:complexType>                <xsd:sequence>                  <xsd:element name="bir‐info" type="iso‐iec19785‐3‐7:BIR‐info" minOccurs="0" maxOccurs="1"/>                  <xsd:element name="bdb‐info" type="iso‐iec19785‐3‐7:BDB‐info" minOccurs="0" maxOccurs="1"/>                  <xsd:element name="sb‐info" type="iso‐iec19785‐3‐7:SB‐info" minOccurs="0" maxOccurs="1"/>                </xsd:sequence>  Biasprofile-1.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="CapabilityAdditionalInfo" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation> Contains additional information for the supported capability.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="CapabilityValue" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A value assigned to the capability.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:element name="CapabilityID" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>An identifier assigned to the capability by the implementing  system.

20 October 2009 Page 97 of 152 .</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:simpleType name="ClassificationAlgorithmType">          <xsd:annotation>            <xsd:documentation>Type of classification algorithm that was used to perform the  classification.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:element name="BIR" minOccurs="1" maxOccurs="1">              <xsd:complexType>                <xsd:choice minOccurs="1" maxOccurs="1">                  <xsd:element name="BinaryBIR" type="xs:base64Binary" />                  <xsd:element name="URI_BIR" type="xs:anyURI" />                  <xsd:element name="XML_BIR" type="iso‐iec19785‐3‐7:BIR" />                </xsd:choice>              </xsd:complexType>            </xsd:element>          </xsd:sequence>          <xsd:attribute name="format‐owner" type="iso‐iec19785‐3‐7:Registered‐int" use="required" />          <xsd:attribute name="format‐type" type="iso‐iec19785‐3‐7:Registered‐int" use="required" />        </xsd:complexType>        <xsd:simpleType name="Classification">          <xsd:annotation>            <xsd:documentation>The result of a classification. All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Classification" type="tns:Classification" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The result of the classification.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="EncounterListType">          <xsd:annotation>            <xsd:documentation>Defines a set of encounters.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="ClassificationAlgorithmType" type="tns:ClassificationAlgorithmType" minOccurs="1"  maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Identifies the type of classification algorithm that was used to perform the  classification.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>  Biasprofile-1.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:complexType name="ClassificationData">          <xsd:annotation>            <xsd:documentation>Contains information on classification results and the algorithm used to determine the  classification.

</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BiometricType" type="iso‐iec19785‐3‐7:Multiple‐types" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The type of biological or behavioral data stored in the biometric record. 20 October 2009 Page 98 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="AlgorithmOwner" type="xsd:string" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The owner or vendor of the algorithm used to determine the score or  decision.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="BiometricSubType" type="iso‐iec19785‐3‐7:Subtype" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>More specifically defines the type of biometric data stored in the biometric  record.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. as input to the PerformFusion request.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="FusionInformationType">          <xsd:annotation>            <xsd:documentation>Represents the information necessary to perform a fusion  operation.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="FusionInformationListType">          <xsd:annotation>            <xsd:documentation>              Contains at a minimum two sets of fusion input              elements. as defined by  CBEFF.</xsd:documentation>              </xsd:annotation>            </xsd:element>  Biasprofile-1.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="FusionElement" type="tns:FusionInformationType" minOccurs="2"  maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>A set of fusion information.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="AlgorithmType" type="xsd:string" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The Algorithm Owner's identifier for the specific algorithm product and version used to  determine the score or decision.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:element name="EncounterID" type="tns:BIASIDType" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>The identifier of an encounter.

  Biasprofile-1.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="ApplicationUser" type="tns:ApplicationUserIdentifier" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Identifers the user or instance of the requesting application. 20 October 2009 Page 99 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="InformationType">          <xsd:annotation>            <xsd:documentation>              Allows for an unlimited number of data element types.</xsd:documentation>                </xsd:annotation>              </xsd:element>            </xsd:choice>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="GenericRequestParameters">          <xsd:annotation>            <xsd:documentation>Common request paramters that can be used to identify the  requester. and it does              not specify nor require any particular data element.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Application" type="tns:ApplicationIdentifier" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>Identifies the requesting application.</xsd:documentation>                </xsd:annotation>              </xsd:element>              <xsd:element name="Decision" type="xsd:string">                <xsd:annotation>                  <xsd:documentation>The match decision assigned by the matching algorithm.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name=”BIASOperationName” type=”xsd:string” minOccurs=”0” maxOccurs=”1”>              <xsd:annotation>                <xsd:documentation>Identifers the BIAS operation name that is being requested. All Rights Reserved.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:any namespace="##any" processContents="lax" minOccurs="0" maxOccurs="unbounded" />          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="ListFilterType">          <xsd:annotation>            <xsd:documentation>              Provides a method to filter the amount of information returned in              a search of biometric data.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:choice minOccurs="1" maxOccurs="1">              <xsd:element name="Score" type="tns:Score">                <xsd:annotation>                  <xsd:documentation>The similarity score assigned by the matching algorithm.

20 October 2009 Page 100 of 152 .</xsd:documentation>          </xsd:annotation>  Biasprofile-1. The ProcessingOptionsType provides a              method to represent those options.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="MatchType">          <xsd:annotation>            <xsd:documentation>The result of a fusion method.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:boolean" />        </xsd:simpleType>        <xsd:complexType name="ProcessingOptionsType">          <xsd:annotation>            <xsd:documentation>              BIAS aggregate services support the ability to include various              processing options which direct and possibly control the business              logic for that service.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Option" type="xsd:string" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>An option supported by the implementing system.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="ProductID">          <xsd:annotation>            <xsd:documentation>The vendor's ID for a particular product.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="IncludeBiometricSubtype" type="xsd:boolean" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A Boolean flag indicating if biometric subtype information should be  returned.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:complexType name="QualityData">          <xsd:annotation>            <xsd:documentation>Contains information about a biometric sample's quality and the algorithm used to  compute the quality. Processing options should be              defined by the implementing system.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:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="BiometricTypeFilter" type="iso‐iec19785‐3‐7:Multiple‐types" minOccurs="1"  maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>Limits the returned information to a specific type of biometric. All Rights Reserved. as defined by  CBEFF.0-cd-01 Copyright © OASIS Open 2009.

</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="Message" type="xsd:string" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A short message corresponding to the return code.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="AlgorithmVendorProductID" type="tns:ProductID" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The vendor's ID for the algorithm used to determine the quality.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="ResponseStatus" type="tns:ResponseStatus" minOccurs="1" maxOccurs="1">  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="GenericRequestParameters" type="tns:GenericRequestParameters" minOccurs="0"  maxOccurs="1" />          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="ResponseStatus">          <xsd:sequence>            <xsd:element name="Return" type="tns:ReturnCode" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The return code indicates the return status of the operation. 20 October 2009 Page 101 of 152 .</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="RequestTemplate" abstract="true">          <xsd:annotation>            <xsd:documentation>Base template for BIAS primitive service requests.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:element name="QualityScore" type="iso‐iec19785‐3‐7:Quality" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The quality of a biometric sample.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="ResponseTemplate" abstract="true">          <xsd:annotation>            <xsd:documentation>Base template for BIAS responses.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="AlgorithmVendor" type="tns:VendorIdentifier" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The vendor of the qualilty algorithm used to determine the quality  score.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="AlgorithmVersion" type="tns:VersionType" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The version of the algorithm used to determine the quality.

</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:float" />        </xsd:simpleType>        <xsd:complexType name="TokenType">          <xsd:annotation>            <xsd:documentation>Defines a token that is returned for asynchronous processing.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="ReturnCode">          <xsd:annotation>            <xsd:documentation>BIAS Operation Return Codes</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:unsignedLong">            <xsd:enumeration value="0">              <xsd:annotation>                <xsd:documentation>Success</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>          </xsd:restriction>        </xsd:simpleType>        <xsd:simpleType name="Score">          <xsd:annotation>            <xsd:documentation>Match result or quality score.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:complexType name="Version">          <xsd:annotation>            <xsd:documentation>              For a description or definition of each data element. 20 October 2009 Page 102 of 152 . All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="VendorIdentifier">          <xsd:annotation>            <xsd:documentation>Identifies a vendor.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element name="Expiration" type="xsd:date" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A date and time at which point the token expires and the service results are no longer  guaranteed to be available. see the  Biasprofile-1.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>Returned status for the operation.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="TokenValue" type="xsd:string" minOccurs="1" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>A value returned by the implementing system that is used to retrieve the results to a  service at a later time.

</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="AddSubjectToGalleryResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to an AddSubjectToGallery request.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             referenced CBEFF standards in the CBEFF_XML_BIR_Type schema.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="GalleryID" type="tns:BIASIDType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identifier of the gallery or population group to which the subject will be  added.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="CheckQualityRequest">  Biasprofile-1. All Rights Reserved.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identity to add to the gallery. 20 October 2009 Page 103 of 152 .0-cd-01 Copyright © OASIS Open 2009.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="major" type="xsd:nonNegativeInteger" minOccurs="1" maxOccurs="1" />            <xsd:element name="minor" type="xsd:nonNegativeInteger" minOccurs="1" maxOccurs="1" />          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="VersionType">          <xsd:annotation>            <xsd:documentation>The version of a component.</xsd:documentation>          </xsd:annotation>          <xsd:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:element name="AddSubjectToGalleryRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Register a subject to a given gallery or population group.

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>                Calculate a quality score for a given biometric.0-cd-01 Copyright © OASIS Open 2009.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="BiometricData" type="tns:BIASBiometricDataType"  minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Data structure containing a single biometric sample for which a quality score is to be  determined. 20 October 2009 Page 104 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="ClassifyBiometricDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Classifies a biometric sample. All Rights Reserved.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="CheckQualityResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a CheckQuality request.              </xsd:documentation>            </xsd:annotation>  Biasprofile-1.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="QualityInfo" type="tns:QualityData" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Contains the quality information for the submitted biometric  sample.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Quality" type="tns:QualityData" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Specifies a particular algorithm vendor and vender product ID.

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:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="BiometricData" type="tns:BIASBiometricDataType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Data structure containing a single biometric sample for which the classification is to  be determined. 20 October 2009 Page 105 of 152 . containing the subject  Biasprofile-1.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="CreateSubjectRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Create a new subject record. containing                the classification of a biometric sample.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="CreateSubjectResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a CreateSubject request.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="ClassifyBiometricDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a ClassifyBiometricData request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="ClassificationData" type="tns:ClassificationData" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Information on the results and type of classification  performed.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.

              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteBiometricDataRequest">          <xsd:complexType>            <xsd:annotation>  Biasprofile-1. in the encounter‐centric model.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteBiographicDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Erase all of the biographic data associated with a given                subject record or. 20 October 2009 Page 106 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteBiographicDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a DeleteBiographicData request.0-cd-01 Copyright © OASIS Open 2009.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Contains either the subject ID or encounter ID reference. All Rights Reserved. with a                given encounter.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               ID of the new subject record.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Contains the subject ID of the new subject record.

 in an encounter‐centric                model.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Contains either the subject ID or encounter ID reference.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Subject ID of the identity to delete.0-cd-01 Copyright © OASIS Open 2009.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteSubjectRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Delete an existing subject record and. in the encounter‐centric model.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>                Erase all of the biometric data associated with a given                subject record or.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteBiometricDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a DeleteBiometricData request. with a                given encounter.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteSubjectResponse">  Biasprofile-1. All Rights Reserved. any associated encounter information. 20 October 2009 Page 107 of 152 .

</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identity to remove from the gallery.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>                The response to a DeleteSubject request. 20 October 2009 Page 108 of 152 .              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="GalleryID" type="tns:BIASIDType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identifier of the gallery or population group from which the subject will be  deleted.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteSubjectFromGalleryResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a DeleteSubjectFromGallery request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="DeleteSubjectFromGalleryRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Remove the registration of a subject from a gallery or                population group. All Rights Reserved.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetIdentifySubjectResultsRequest">          <xsd:complexType>            <xsd:annotation>  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009.

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>                Retrieve the identification results for a specified token. 20 October 2009 Page 109 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="IdentifySubjectRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Perform an identification search against a given gallery for                a given biometric.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Token" type="tns:TokenType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>A value used to retrieve the results of an IdentifySubject  request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="GalleryID" type="tns:BIASIDType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>  Biasprofile-1.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="CandidateList" type="tns:CandidateListType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>A rank‐ordered list of candidates that have a likelihood of matching the input  biometric sample.                which was returned by the Identify Subject service.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetIdentifySubjectResultsResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a GetIdentifySubjectResults request.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. which includes a candidate list.

 returned with successful synchronous request processing. returned with  asynchronous request processing.0-cd-01 Copyright © OASIS Open 2009. a data structure containing the biometric sample for the  search.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:choice>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="ListBiographicDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>  Biasprofile-1.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="IdentifySubjectResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to an IdentifySubject request.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="MaxListSize" type="xsd:positiveInteger" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The maximum size of the candidate list that should be  returned.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Token" type="tns:TokenType">                    <xsd:annotation>                      <xsd:documentation>A token used to retrieve the results of the IdentifySubject request. returning a                rank‐ordered candidate list. All Rights Reserved.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Contains the BIR.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>The identifier of the gallery or population group which will be  searched. 20 October 2009 Page 110 of 152 .              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:choice minOccurs="1" maxOccurs="1">                  <xsd:element name="CandidateList" type="tns:CandidateListType">                    <xsd:annotation>                      <xsd:documentation>A rank‐ordered list of candidates that have a likelihood of matching the input  biometric sample.

 and either (a) the                        person‐centric model is being used or (b) the                        encounter‐centric model is being used and an encounter                        identifier was specified.  In the                encounter‐centric model. the                        encounter‐centric model is being used. a subject and an  encounter. 20 October 2009 Page 111 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="ListBiographicDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a ListBiographicData request. the list                of encounter IDs which contain biographic data is returned.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>                        Contains a list of biographic data elements associated with a                        subject or encounter.0-cd-01 Copyright © OASIS Open 2009. and an encounter                        identifier was not specified. non‐empty if the service                        was successful. biographic data exists.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               Lists the biographic data elements stored for a subject.  If an encounter ID is not                specified and encounter data exists for the subject. containing a list                of biographic data elements stored for a subject. in the encounter‐centric model. All Rights Reserved. biographic data exists. non‐empty if the service was                        successful.                      </xsd:documentation>  Biasprofile-1.                      </xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="EncounterList" type="tns:EncounterListType" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>                        A list of encounter ID's associated with a subject and                        which contain biographic data. the biographic data elements for a                specific encounter are returned.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.

</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="ListFilter" type="tns:ListFilterType" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Indicates what biometric information should be returned.0-cd-01 Copyright © OASIS Open 2009. the list                of encounter IDs which contain biometric data is returned. in the encounter‐centric model. Note                that no actual biometric data is returned by this service (see                the RetrieveBiometricInformation service to obtain the biometric                data). 20 October 2009 Page 112 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="ListBiometricDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a ListBiometricData request.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:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="ListBiometricDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Lists the biometric data elements stored for a subject.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity">                    <xsd:annotation>  Biasprofile-1. containing a list                of biometric data elements stored for a subject. All Rights Reserved.  If an encounter ID is not                specified and encounter data exists for the subject.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or. the biometric data elements for a                specific encounter are returned.  In the                encounter‐centric model. a subject and an  encounter.

All Rights Reserved.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Match" type="tns:MatchType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Indicates the result of the fusion method</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>  Biasprofile-1.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="FusionInput" type="tns:FusionInformationListType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Score or decision input information to the fusion method. 20 October 2009 Page 113 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>                        Includes a list of biometric data elements associated                        with a subject or encounter or a list of encounter ID's                        associated with a subject and which contain biometric                        data.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="PerformFusionResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to the PerformFusion request.                      </xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="PerformFusionRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Accepts either match score or match decision information and creates a fused match result.

 galleries. a subject and an  encounter.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="CapabilityList" type="tns:CapabilityListType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>A list of capabilities supported by the BIAS implementation.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:element name="QueryCapabilitiesRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Returns a list of the capabilities.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="QueryCapabilitiesResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a QueryCapabilities request. 20 October 2009 Page 114 of 152 . etc. options.                that are supported by the BIAS implementation. in the encounter‐centric model.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>  Biasprofile-1. All Rights Reserved.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="RetrieveBiographicInformationRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Retrieves the biographic data associated with a subject ID.0-cd-01 Copyright © OASIS Open 2009.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.

 If the encounter ID is not                specified in the encounter‐centric model. the biographic                information associated with the most recent encounter is returned.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. in the encounter‐centric model.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="RetrieveBiometricInformationRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Retrieves the biometric data associated with a subject ID. 20 October 2009 Page 115 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="BiometricType" type="iso‐iec19785‐3‐7:Multiple‐types" minOccurs="0"  maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The type of biological or behavioral data to retrieve.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Includes the set of biographic data associated with a subject. In                the encounter‐centric model. All Rights Reserved. the biographic data associated with                a specified encounter is returned.                containing the biographic data associated with a subject ID. a subject and an  encounter.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:element name="RetrieveBiographicInformationResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a RetrieveBiographicInformation request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.

  and includes the biographic data to store. 20 October 2009 Page 116 of 152 .              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.0-cd-01 Copyright © OASIS Open 2009. the biometric                information associated with the most recent encounter is returned.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="SetBiographicDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a SetBiographicData request.                containing the biometric data associated with a subject ID. in the encounter‐centric model. a subject and an encounter.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="SetBiographicDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Associates biographic data to a given subject record.              </xsd:documentation>            </xsd:annotation>  Biasprofile-1.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:element name="RetrieveBiometricInformationResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a RetrieveBiometricInformation request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Includes the biometric data associated with a subject. the biometric data associated with                a specified encounter is returned. All Rights Reserved. In                the encounter‐centric model. If the encounter ID is not                specified in the encounter‐centric model.

 a subject and an encounter. 20 October 2009 Page 117 of 152 .  and includes the biometric data to store. identifies the encounter ID assigned to a new  encounter. in the encounter‐centric model.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. identifies the encounter ID assigned to a new  encounter.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="SetBiometricDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a SetBiometricData request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>In an encounter‐centric model.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="SetBiometricDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Associates biometric data to a given subject record.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>>              </xsd:extension>  Biasprofile-1.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:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>In an encounter‐centric model.

All Rights Reserved.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="InputBIR" type="tns:CBEFF_BIR_Type" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Data structure containing the biometric information to be  transformed.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:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="TransformBiometricDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Transforms or processes a given biometric in one format into a new target format.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 118 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="TransformControl" type="xsd:string" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation> Specifies controls for the requested transform operation.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="OutputBIR" type="tns:CBEFF_BIR_Type" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Data structure containing the new.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>  Biasprofile-1.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="TransformOperation" type="xsd:unsignedLong" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Value indicating the type of transformation to perform.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="TransformBiometricDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a TransformBiometricData request. transformed biometric  information.

              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="UpdateBiometricDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Updates a single biometric sample for a given subject record.0-cd-01 Copyright © OASIS Open 2009.  and includes the biometric data to update. All Rights Reserved. 20 October 2009 Page 119 of 152 .              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Merge" type="xsd:boolean" minOccurs="0" maxOccurs="1">                    <xsd:annotation>  Biasprofile-1. a subject and an encounter. in the encounter‐centric model. a subject and an encounter. in the encounter‐centric model.  and includes the biographic data to update.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:element name="UpdateBiographicDataRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Updates the biographic data for a given subject record.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="UpdateBiographicDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to an UpdateBiographicData request.

0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 120 of 152 .              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="GalleryID" type="tns:BIASIDType" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identifier of the gallery or population group of which the subject must be a  member.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Includes the identifying information and/or input and reference biometric  samples.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>Value indicating if the input biometric sample should be merged with any existing  biometric information.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="VerifySubjectRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Performs a 1:1 verification match between a given biometric and                either a claim to identity in a given gallery or another given                biometric. All Rights Reserved.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="VerifySubjectResponse">          <xsd:complexType>            <xsd:annotation>  Biasprofile-1.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="UpdateBiometricDataResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to an UpdateBiometricData request.

</xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate" />  Biasprofile-1. the                implementing system immediately processes the request and                returns the results in the ReturnData parameter. 20 October 2009 Page 121 of 152 . In this case. the GetEnrollResults                service is used to poll for the results of the Enroll request. If the Enroll aggregate                service is implemented as a synchronous service. If the Enroll                aggregate service is implemented as an asynchronous service.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Match" type="xsd:boolean" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Indicates if the Input BIR matched either the biometric information associated with  the Identity Claim or the Reference BIR. the                implementing system returns a token in the ReturnData                parameter.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="EnrollRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The Enroll aggregate service adds a new subject or.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Score" type="tns:Score" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The score if the biometric information matched. which is an indication that the request is being                handled asynchronously. All Rights Reserved.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>                The response to a VerifySubject request.0-cd-01 Copyright © OASIS Open 2009.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateRequestTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="EnrollResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to an Enroll request. a new encounter to the system. in an                encounter‐centric model. This may                be accomplished in a number of different ways according to                system requirements and/or resources.

 and the                GetIdentifyResults service is used to poll for the results of                the original Identify request. All Rights Reserved.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Token" type="tns:TokenType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>A value used to retrieve the results of the Enroll request. This service is                used in conjunction with the Identify aggregate service. This service is used in                conjunction with the Enroll aggregate service. the                implementing system returns a token. the implementing system returns a token. and the GetEnrollResults                service is used to poll for the results of the original Enroll                request.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:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetEnrollResultsRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The GetEnrollResults aggregate service retrieves the enrollment                results for the specified token.</xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetIdentifyResultsRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The GetIdentifyResults aggregate service retrieves the                identification results for the specified token. 20 October 2009 Page 122 of 152 .0-cd-01 Copyright © OASIS Open 2009. If the                Identify aggregate service is implemented as an asynchronous                service.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetEnrollResultsResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to a GetEnrollResults request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>  Biasprofile-1. If the Enroll                aggregate service is implemented as an asynchronous service.

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:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Token" type="tns:TokenType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>A value used to retrieve the results of the Identify request.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetVerifyResultsRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The GetVerifyResults aggregate service retrieves the verification                results for the specified token.</xsd:documentation>            </xsd:annotation>  Biasprofile-1. All Rights Reserved. This service is used in                conjunction with the Verify aggregate service. 20 October 2009 Page 123 of 152 .              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Token" type="tns:TokenType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>A value used to retrieve the results of the Verify request. the                implementing system returns a token. If the Verify                aggregate service is implemented as an asynchronous service.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetVerifyResultsResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to a GetVerifyResults request.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetIdentifyResultsResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to a GetIdentifyResults request. and the GetVerifyResults                service is used to poll for the results of the original Verify                request.

 the                GetIdentifyResults service is used to poll for the results of                the Identify request. the implementing system returns a token in the                ReturnData parameter. In this case.</xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="RetrieveInformationRequest">          <xsd:complexType>  Biasprofile-1. If                the Identify aggregate service is implemented as a synchronous                service.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="IdentifyRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The Identify aggregate service performs an identification                function according to system requirements and/or resources. which is an indication that the request is                being handled asynchronously.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateRequestTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="IdentifyResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to an Identify request.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Score" type="Score" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The score if the biometric information matched.0-cd-01 Copyright © OASIS Open 2009.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:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate">                <xsd:sequence>                  <xsd:element name="Match" type="xsd:boolean" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Indicates if the Input BIR matched either the biometric information associated with  the Identity Claim or the Reference BIR. 20 October 2009 Page 124 of 152 . If                the Identify aggregate service is implemented as an asynchronous                service. the implementing system immediately processes the                request and returns the results in the ReturnData parameter. All Rights Reserved.

 the                implementing system immediately processes the request and returns                the results in the ReturnData parameter. All Rights Reserved. If the Verify aggregate  Biasprofile-1.</xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="VerifyRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The Verify aggregate service performs a 1:1 verification                function according to system requirements and/or resources.0-cd-01 Copyright © OASIS Open 2009. In an encounter‐centric model.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>                The RetrieveInformation aggregate service retrieves requested                information about a subject.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:RequestTemplate">                <xsd:sequence>                  <xsd:element name="ProcessingOptions" type="tns:ProcessingOptionsType" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Options that guide how the service request is processed. this aggregate                service may be used to retrieve both biographic and biometric                information for a subject record. or in an encounter‐centric model                about an encounter.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="RetrieveInformationResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to a RetrieveInformation request.                Either the IdentityClaim or ReferenceBIR input data elements in                the Identity parameter are required. and may identify what  type(s) of information should be returned. In a person‐centric model. If the Verify aggregate                service is implemented as a synchronous service. Either a SubjectID or EncounterID must be specified                in the Identify parameter.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Includes the identifier of the subject or encounter. 20 October 2009 Page 125 of 152 .                this aggregate service may be used to retrieve biographic and/or                biometric information for either a single encounter or all                encounters.

All Rights Reserved.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="GalleryID" type="tns:BIASIDType" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identifier of the gallery or population group of which the subject must be a  member. 20 October 2009 Page 126 of 152 .</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Score" type="Score" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The score if the biometric information matched.0-cd-01 Copyright © OASIS Open 2009.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               service is implemented as an asynchronous service. In this case. the GetVerifyResults service is                used to poll for the results of the Verify request.                which is an indication that the request is being handled                asynchronously. the                implementing system returns a token in the ReturnData parameter.</xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateResponseTemplate">                <xsd:sequence>                  <xsd:element name="Match" type="xsd:boolean" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Indicates if the Input BIR matched either the biometric information associated with  the Identity Claim or the Reference BIR.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="VerifyResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>The response to a Verify request.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:AggregateRequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Includes either the IdentityClaim or ReferenceBIR.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name=”BIASFault” type=”tns:BIASFaultDetail” />      </xsd:schema>    </wsdl:types>  Biasprofile-1.

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:message name="AddSubjectToGalleryRequestMessage">      <wsdl:part name="AddSubjectToGalleryRequest" element="AddSubjectToGalleryRequest" />    </wsdl:message>    <wsdl:message name="AddSubjectToGalleryResponseMessage">      <wsdl:part name="AddSubjectToGalleryResponse" element="AddSubjectToGalleryResponse" />    </wsdl:message>    <wsdl:message name="CheckQualityRequestMessage">      <wsdl:part name="CheckQualityRequest" element="CheckQualityRequest" />    </wsdl:message>    <wsdl:message name="CheckQualityResponseMessage">      <wsdl:part name="CheckQualityResponse" element="CheckQualityResponse" />    </wsdl:message>    <wsdl:message name="ClassifyBiometricDataRequestMessage">      <wsdl:part name="ClassifyBiometricDataRequest" element="ClassifyBiometricDataRequest" />    </wsdl:message>    <wsdl:message name="ClassifyBiometricDataResponseMessage">      <wsdl:part name="ClassifyBiometricDataResponse" element="ClassifyBiometricDataResponse" />    </wsdl:message>    <wsdl:message name="CreateSubjectRequestMessage">      <wsdl:part name="CreateSubjectRequest" element="CreateSubjectRequest" />    </wsdl:message>    <wsdl:message name="CreateSubjectResponseMessage">      <wsdl:part name="CreateSubjectResponse" element="CreateSubjectResponse" />    </wsdl:message>    <wsdl:message name="DeleteBiographicDataRequestMessage">      <wsdl:part name="DeleteBiographicDataRequest" element="DeleteBiographicDataRequest" />    </wsdl:message>    <wsdl:message name="DeleteBiographicDataResponseMessage">      <wsdl:part name="DeleteBiographicDataResponse" element="DeleteBiographicDataResponse" />    </wsdl:message>    <wsdl:message name="DeleteBiometricDataRequestMessage">      <wsdl:part name="DeleteBiometricDataRequest" element="DeleteBiometricDataRequest" />    </wsdl:message>    <wsdl:message name="DeleteBiometricDataResponseMessage">      <wsdl:part name="DeleteBiometricDataResponse" element="DeleteBiometricDataResponse" />    </wsdl:message>    <wsdl:message name="DeleteSubjectRequestMessage">      <wsdl:part name="DeleteSubjectRequest" element="DeleteSubjectRequest" />    </wsdl:message>    <wsdl:message name="DeleteSubjectResponseMessage">      <wsdl:part name="DeleteSubjectResponse" element="DeleteSubjectResponse" />    </wsdl:message>    <wsdl:message name="DeleteSubjectFromGalleryRequestMessage">      <wsdl:part name="DeleteSubjectFromGalleryRequest" element="DeleteSubjectFromGalleryRequest" />    </wsdl:message>    <wsdl:message name="DeleteSubjectFromGalleryResponseMessage">      <wsdl:part name="DeleteSubjectFromGalleryResponse" element="DeleteSubjectFromGalleryResponse" />    </wsdl:message>    <wsdl:message name="GetIdentifySubjectResultsRequestMessage">      <wsdl:part name="GetIdentifySubjectResultsRequest" element="GetIdentifySubjectResultsRequest" />    </wsdl:message>    <wsdl:message name="GetIdentifySubjectResultsResponseMessage">      <wsdl:part name="GetIdentifySubjectResultsResponse" element="GetIdentifySubjectResultsResponse" />  Biasprofile-1. All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 127 of 152 .

All Rights Reserved.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:message name="IdentifySubjectRequestMessage">      <wsdl:part name="IdentifySubjectRequest" element="IdentifySubjectRequest" />    </wsdl:message>    <wsdl:message name="IdentifySubjectResponseMessage">      <wsdl:part name="IdentifySubjectResponse" element="IdentifySubjectResponse" />    </wsdl:message>    <wsdl:message name="ListBiographicDataRequestMessage">      <wsdl:part name="ListBiographicDataRequest" element="ListBiographicDataRequest" />    </wsdl:message>    <wsdl:message name="ListBiographicDataResponseMessage">      <wsdl:part name="ListBiographicDataResponse" element="ListBiographicDataResponse" />    </wsdl:message>    <wsdl:message name="ListBiometricDataRequestMessage">      <wsdl:part name="ListBiometricDataRequest" element="ListBiometricDataRequest" />    </wsdl:message>    <wsdl:message name="ListBiometricDataResponseMessage">      <wsdl:part name="ListBiometricDataResponse" element="ListBiometricDataResponse" />    </wsdl:message>    <wsdl:message name="PerformFusionRequestMessage">      <wsdl:part name="PerformFusionRequest" element="PerformFusionRequest" />    </wsdl:message>    <wsdl:message name="PerformFusionResponseMessage">      <wsdl:part name="PerformFusionResponse" element="PerformFusionResponse" />    </wsdl:message>    <wsdl:message name="QueryCapabilitiesRequestMessage">      <wsdl:part name="QueryCapabilitiesRequest" element="QueryCapabilitiesRequest" />    </wsdl:message>    <wsdl:message name="QueryCapabilitiesResponseMessage">      <wsdl:part name="QueryCapabilitiesResponse" element="QueryCapabilitiesResponse" />    </wsdl:message>    <wsdl:message name="RetrieveBiographicInformationRequestMessage">      <wsdl:part name="RetrieveBiographicInformationRequest" element="RetrieveBiographicInformationRequest" />    </wsdl:message>    <wsdl:message name="RetrieveBiographicInformationResponseMessage">      <wsdl:part name="RetrieveBiographicInformationResponse" element="RetrieveBiographicInformationResponse" />    </wsdl:message>    <wsdl:message name="RetrieveBiometricInformationRequestMessage">      <wsdl:part name="RetrieveBiometricInformationRequest" element="RetrieveBiometricInformationRequest" />    </wsdl:message>    <wsdl:message name="RetrieveBiometricInformationResponseMessage">      <wsdl:part name="RetrieveBiometricInformationResponse" element="RetrieveBiometricInformationResponse" />    </wsdl:message>    <wsdl:message name="SetBiographicDataRequestMessage">      <wsdl:part name="SetBiographicDataRequest" element="SetBiographicDataRequest" />    </wsdl:message>    <wsdl:message name="SetBiographicDataResponseMessage">      <wsdl:part name="SetBiographicDataResponse" element="SetBiographicDataResponse" />    </wsdl:message>    <wsdl:message name="SetBiometricDataRequestMessage">      <wsdl:part name="SetBiometricDataRequest" element="SetBiometricDataRequest" />    </wsdl:message>    <wsdl:message name="SetBiometricDataResponseMessage">  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 128 of 152 .

0-cd-01 Copyright © OASIS Open 2009.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:part name="SetBiometricDataResponse" element="SetBiometricDataResponse" />    </wsdl:message>    <wsdl:message name="TransformBiometricDataRequestMessage">      <wsdl:part name="TransformBiometricDataRequest" element="TransformBiometricDataRequest" />    </wsdl:message>    <wsdl:message name="TransformBiometricDataResponseMessage">      <wsdl:part name="TransformBiometricDataResponse" element="TransformBiometricDataResponse" />    </wsdl:message>    <wsdl:message name="UpdateBiographicDataRequestMessage">      <wsdl:part name="UpdateBiographicDataRequest" element="UpdateBiographicDataRequest" />    </wsdl:message>    <wsdl:message name="UpdateBiographicDataResponseMessage">      <wsdl:part name="UpdateBiographicDataResponse" element="UpdateBiographicDataResponse" />    </wsdl:message>    <wsdl:message name="UpdateBiometricDataRequestMessage">      <wsdl:part name="UpdateBiometricDataRequest" element="UpdateBiometricDataRequest" />    </wsdl:message>    <wsdl:message name="UpdateBiometricDataResponseMessage">      <wsdl:part name="UpdateBiometricDataResponse" element="UpdateBiometricDataResponse" />    </wsdl:message>    <wsdl:message name="VerifySubjectRequestMessage">      <wsdl:part name="VerifySubjectRequest" element="VerifySubjectRequest" />    </wsdl:message>    <wsdl:message name="VerifySubjectResponseMessage">      <wsdl:part name="VerifySubjectResponse" element="VerifySubjectResponse" />    </wsdl:message>    <wsdl:message name="EnrollRequestMessage">      <wsdl:part name="EnrollRequest" element="EnrollRequest" />    </wsdl:message>    <wsdl:message name="EnrollResponseMessage">      <wsdl:part name="EnrollResponse" element="EnrollResponse" />    </wsdl:message>    <wsdl:message name="GetEnrollResultsRequestMessage">      <wsdl:part name="GetEnrollResultsRequest" element="GetEnrollResultsRequest" />    </wsdl:message>    <wsdl:message name="GetEnrollResultsResponseMessage">      <wsdl:part name="GetEnrollResultsResponse" element="GetEnrollResultsResponse" />    </wsdl:message>    <wsdl:message name="GetIdentifyResultsRequestMessage">      <wsdl:part name="GetIdentifyResultsRequest" element="GetIdentifyResultsRequest" />    </wsdl:message>    <wsdl:message name="GetIdentifyResultsResponseMessage">      <wsdl:part name="GetIdentifyResultsResponse" element="GetIdentifyResultsResponse" />    </wsdl:message>    <wsdl:message name="GetVerifyResultsRequestMessage">      <wsdl:part name="GetVerifyResultsRequest" element="GetVerifyResultsRequest" />    </wsdl:message>    <wsdl:message name="GetVerifyResultsResponseMessage">      <wsdl:part name="GetVerifyResultsResponse" element="GetVerifyResultsResponse" />    </wsdl:message>    <wsdl:message name="IdentifyRequestMessage">      <wsdl:part name="IdentifyRequest" element="IdentifyRequest" />    </wsdl:message>  Biasprofile-1. 20 October 2009 Page 129 of 152 . All Rights Reserved.

All Rights Reserved.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:message name="IdentifyResponseMessage">      <wsdl:part name="IdentifyResponse" element="IdentifyResponse" />    </wsdl:message>    <wsdl:message name="RetrieveInformationRequestMessage">      <wsdl:part name="RetrieveInformationRequest" element="RetrieveInformationRequest" />    </wsdl:message>    <wsdl:message name="RetrieveInformationResponseMessage">      <wsdl:part name="RetrieveInformationResponse" element="RetrieveInformationResponse" />    </wsdl:message>    <wsdl:message name="VerifyRequestMessage">      <wsdl:part name="VerifyRequest" element="VerifyRequest" />    </wsdl:message>    <wsdl:message name="VerifyResponseMessage">      <wsdl:part name="VerifyResponse" element="VerifyResponse" />    </wsdl:message>    <wsdl:portType name="BIAS_v1">      <wsdl:operation name="AddSubjectToGallery">        <wsdl:input message="tns:AddSubjectToGalleryRequestMessage" name="AddSubjectToGalleryRequest" />        <wsdl:output message="tns:AddSubjectToGalleryResponseMessage" name="AddSubjectToGalleryResponse" />      </wsdl:operation>      <wsdl:operation name="CheckQuality">        <wsdl:input message="tns:CheckQualityRequestMessage" name="CheckQualityRequest" />        <wsdl:output message="tns:CheckQualityResponseMessage" name="CheckQualityResponse" />      </wsdl:operation>      <wsdl:operation name="ClassifyBiometricData">        <wsdl:input message="tns:ClassifyBiometricDataRequestMessage" name="ClassifyBiometricDataRequest" />        <wsdl:output message="tns:ClassifyBiometricDataResponseMessage" name="ClassifyBiometricDataResponse" />      </wsdl:operation>      <wsdl:operation name="CreateSubject">        <wsdl:input message="tns:CreateSubjectRequestMessage" name="CreateSubjectRequest" />        <wsdl:output message="tns:CreateSubjectResponseMessage" name="CreateSubjectResponse" />      </wsdl:operation>      <wsdl:operation name="DeleteBiographicData">        <wsdl:input message="tns:DeleteBiographicDataRequestMessage" name="DeleteBiographicDataRequest" />        <wsdl:output message="tns:DeleteBiographicDataResponseMessage" name="DeleteBiographicDataResponse" />      </wsdl:operation>      <wsdl:operation name="DeleteBiometricData">        <wsdl:input message="tns:DeleteBiometricDataRequestMessage" name="DeleteBiometricDataRequest" />        <wsdl:output message="tns:DeleteBiometricDataResponseMessage" name="DeleteBiometricDataResponse" />      </wsdl:operation>      <wsdl:operation name="DeleteSubject">        <wsdl:input message="tns:DeleteSubjectRequestMessage" name="DeleteSubjectRequest" />        <wsdl:output message="tns:DeleteSubjectResponseMessage" name="DeleteSubjectResponse" />      </wsdl:operation>      <wsdl:operation name="DeleteSubjectFromGallery">        <wsdl:input message="tns:DeleteSubjectFromGalleryRequestMessage" name="DeleteSubjectFromGalleryRequest"  />        <wsdl:output message="tns:DeleteSubjectFromGalleryResponseMessage"  name="DeleteSubjectFromGalleryResponse" />      </wsdl:operation>      <wsdl:operation name="GetIdentifySubjectResults">        <wsdl:input message="tns:GetIdentifySubjectResultsRequestMessage" name="GetIdentifySubjectResultsRequest"  />  Biasprofile-1. 20 October 2009 Page 130 of 152 .0-cd-01 Copyright © OASIS Open 2009.

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:output message="tns:GetIdentifySubjectResultsResponseMessage"  name="GetIdentifySubjectResultsResponse" />      </wsdl:operation>      <wsdl:operation name="IdentifySubject">        <wsdl:input message="tns:IdentifySubjectRequestMessage" name="IdentifySubjectRequest" />        <wsdl:output message="tns:IdentifySubjectResponseMessage" name="IdentifySubjectResponse" />      </wsdl:operation>      <wsdl:operation name="ListBiographicData">        <wsdl:input message="tns:ListBiographicDataRequestMessage" name="ListBiographicDataRequest" />        <wsdl:output message="tns:ListBiographicDataResponseMessage" name="ListBiographicDataResponse" />      </wsdl:operation>      <wsdl:operation name="ListBiometricData">        <wsdl:input message="tns:ListBiometricDataRequestMessage" name="ListBiometricDataRequest" />        <wsdl:output message="tns:ListBiometricDataResponseMessage" name="ListBiometricDataResponse" />      </wsdl:operation>      <wsdl:operation name="PerformFusion">        <wsdl:input message="tns:PerformFusionRequestMessage" name="PerformFusionRequest" />        <wsdl:output message="tns:PerformFusionResponseMessage" name="PerformFusionResponse" />      </wsdl:operation>      <wsdl:operation name="QueryCapabilities">        <wsdl:input message="tns:QueryCapabilitiesRequestMessage" name="QueryCapabilitiesRequest" />        <wsdl:output message="tns:QueryCapabilitiesResponseMessage" name="QueryCapabilitiesResponse" />      </wsdl:operation>      <wsdl:operation name="RetrieveBiographicInformation">        <wsdl:input message="tns:RetrieveBiographicInformationRequestMessage"  name="RetrieveBiographicInformationRequest" />        <wsdl:output message="tns:RetrieveBiographicInformationResponseMessage"  name="RetrieveBiographicInformationResponse" />      </wsdl:operation>      <wsdl:operation name="RetrieveBiometricInformation">        <wsdl:input message="tns:RetrieveBiometricInformationRequestMessage"  name="RetrieveBiometricInformationRequest" />        <wsdl:output message="tns:RetrieveBiometricInformationResponseMessage"  name="RetrieveBiometricInformationResponse" />      </wsdl:operation>      <wsdl:operation name="SetBiographicData">        <wsdl:input message="tns:SetBiographicDataRequestMessage" name="SetBiographicDataRequest" />        <wsdl:output message="tns:SetBiographicDataResponseMessage" name="SetBiographicDataResponse" />      </wsdl:operation>      <wsdl:operation name="SetBiometricData">        <wsdl:input message="tns:SetBiometricDataRequestMessage" name="SetBiometricDataRequest" />        <wsdl:output message="tns:SetBiometricDataResponseMessage" name="SetBiometricDataResponse" />      </wsdl:operation>      <wsdl:operation name="TransformBiometricData">        <wsdl:input message="tns:TransformBiometricDataRequestMessage" name="TransformBiometricDataRequest" />        <wsdl:output message="tns:TransformBiometricDataResponseMessage"  name="TransformBiometricDataResponse" />      </wsdl:operation>      <wsdl:operation name="UpdateBiographicData">        <wsdl:input message="tns:UpdateBiographicDataRequestMessage" name="UpdateBiographicDataRequest" />        <wsdl:output message="tns:UpdateBiographicDataResponseMessage" name="UpdateBiographicDataResponse" />      </wsdl:operation>      <wsdl:operation name="UpdateBiometricData">  Biasprofile-1. 20 October 2009 Page 131 of 152 .0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.

xmlsoap. All Rights Reserved.org/soap/http" />      <wsdl:operation name="AddSubjectToGallery">        <soap:operation soapAction="AddSubjectToGallery" />        <wsdl:input name="AddSubjectToGalleryRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="AddSubjectToGalleryResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="CheckQuality">        <soap:operation soapAction="CheckQuality" />        <wsdl:input name="CheckQualityRequest">  Biasprofile-1. 20 October 2009 Page 132 of 152 .0-cd-01 Copyright © OASIS Open 2009.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:input message="tns:UpdateBiometricDataRequestMessage" name="UpdateBiometricDataRequest" />        <wsdl:output message="tns:UpdateBiometricDataResponseMessage" name="UpdateBiometricDataResponse" />      </wsdl:operation>      <wsdl:operation name="VerifySubject">        <wsdl:input message="tns:VerifySubjectRequestMessage" name="VerifySubjectRequest" />        <wsdl:output message="tns:VerifySubjectResponseMessage" name="VerifySubjectResponse" />      </wsdl:operation>      <wsdl:operation name="Enroll">        <wsdl:input message="tns:EnrollRequestMessage" name="EnrollRequest" />        <wsdl:output message="tns:EnrollResponseMessage" name="EnrollResponse" />      </wsdl:operation>      <wsdl:operation name="GetEnrollResults">        <wsdl:input message="tns:GetEnrollResultsRequestMessage" name="GetEnrollResultsRequest" />        <wsdl:output message="tns:GetEnrollResultsResponseMessage" name="GetEnrollResultsResponse" />      </wsdl:operation>      <wsdl:operation name="GetIdentifyResults">        <wsdl:input message="tns:GetIdentifyResultsRequestMessage" name="GetIdentifyResultsRequest" />        <wsdl:output message="tns:GetIdentifyResultsResponseMessage" name="GetIdentifyResultsResponse" />      </wsdl:operation>      <wsdl:operation name="GetVerifyResults">        <wsdl:input message="tns:GetVerifyResultsRequestMessage" name="GetVerifyResultsRequest" />        <wsdl:output message="tns:GetVerifyResultsResponseMessage" name="GetVerifyResultsResponse" />      </wsdl:operation>      <wsdl:operation name="Identify">        <wsdl:input message="tns:IdentifyRequestMessage" name="IdentifyRequest" />        <wsdl:output message="tns:IdentifyResponseMessage" name="IdentifyResponse" />      </wsdl:operation>      <wsdl:operation name="RetrieveInformation">        <wsdl:input message="tns:RetrieveInformationRequestMessage" name="RetrieveInformationRequest" />        <wsdl:output message="tns:RetrieveInformationResponseMessage" name="RetrieveInformationResponse" />      </wsdl:operation>      <wsdl:operation name="Verify">        <wsdl:input message="tns:VerifyRequestMessage" name="VerifyRequest" />        <wsdl:output message="tns:VerifyResponseMessage" name="VerifyResponse" />      </wsdl:operation>    </wsdl:portType>    <wsdl:binding type="tns:BIAS_v1" name="BIAS_v1HttpBinding">      <soap:binding style="document" transport="http://schemas.

All Rights Reserved. 20 October 2009 Page 133 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         <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="CheckQualityResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="ClassifyBiometricData">        <soap:operation soapAction="ClassifyBiometricData" />        <wsdl:input name="ClassifyBiometricDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="ClassifyBiometricDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="CreateSubject">        <soap:operation soapAction="CreateSubject" />        <wsdl:input name="CreateSubjectRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="CreateSubjectResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="DeleteBiographicData">        <soap:operation soapAction="DeleteBiographicData" />        <wsdl:input name="DeleteBiographicDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="DeleteBiographicDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="DeleteBiometricData">        <soap:operation soapAction="DeleteBiometricData" />        <wsdl:input name="DeleteBiometricDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="DeleteBiometricDataResponse">          <soap:body use="literal" />        </wsdl:output>  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009.

20 October 2009 Page 134 of 152 . All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009.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 name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="DeleteSubject">        <soap:operation soapAction="DeleteSubject" />        <wsdl:input name="DeleteSubjectRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="DeleteSubjectResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="DeleteSubjectFromGallery">        <soap:operation soapAction="DeleteSubjectFromGallery" />        <wsdl:input name="DeleteSubjectFromGalleryRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="DeleteSubjectFromGalleryResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="GetIdentifySubjectResults">        <soap:operation soapAction="GetIdentifySubjectResults" />        <wsdl:input name="GetIdentifySubjectResultsRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="GetIdentifySubjectResultsResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="IdentifySubject">        <soap:operation soapAction="IdentifySubject" />        <wsdl:input name="IdentifySubjectRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="IdentifySubjectResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="ListBiographicData">  Biasprofile-1.

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:operation soapAction="ListBiographicData" />        <wsdl:input name="ListBiographicDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="ListBiographicDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="ListBiometricData">        <soap:operation soapAction="ListBiometricData" />        <wsdl:input name="ListBiometricDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="ListBiometricDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="PerformFusion">        <soap:operation soapAction="PerformFusion" />        <wsdl:input name="PerformFusionRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="PerformFusionResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="QueryCapabilities">        <soap:operation soapAction="QueryCapabilities" />        <wsdl:input name="QueryCapabilitiesRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="QueryCapabilitiesResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="RetrieveBiographicInformation">        <soap:operation soapAction="RetrieveBiographicInformation" />        <wsdl:input name="RetrieveBiographicInformationRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="RetrieveBiographicInformationResponse">  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. 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         <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="RetrieveBiometricInformation">        <soap:operation soapAction="RetrieveBiometricInformation" />        <wsdl:input name="RetrieveBiometricInformationRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="RetrieveBiometricInformationResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="SetBiographicData">        <soap:operation soapAction="SetBiographicData" />        <wsdl:input name="SetBiographicDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="SetBiographicDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="SetBiometricData">        <soap:operation soapAction="SetBiometricData" />        <wsdl:input name="SetBiometricDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="SetBiometricDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="TransformBiometricData">        <soap:operation soapAction="TransformBiometricData" />        <wsdl:input name="TransformBiometricDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="TransformBiometricDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. 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:operation name="UpdateBiographicData">        <soap:operation soapAction="UpdateBiographicData" />        <wsdl:input name="UpdateBiographicDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="UpdateBiographicDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="UpdateBiometricData">        <soap:operation soapAction="UpdateBiometricData" />        <wsdl:input name="UpdateBiometricDataRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="UpdateBiometricDataResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="VerifySubject">        <soap:operation soapAction="VerifySubject" />        <wsdl:input name="VerifySubjectRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="VerifySubjectResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="Enroll">        <soap:operation soapAction="Enroll" />        <wsdl:input name="EnrollRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="EnrollResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="GetEnrollResults">        <soap:operation soapAction="GetEnrollResults" />        <wsdl:input name="GetEnrollResultsRequest">          <soap:body use="literal" />  Biasprofile-1. 20 October 2009 Page 137 of 152 . All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009.

All Rights Reserved. 20 October 2009 Page 138 of 152 .0-cd-01 Copyright © OASIS Open 2009.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:output name="GetEnrollResultsResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="GetIdentifyResults">        <soap:operation soapAction="GetIdentifyResults" />        <wsdl:input name="GetIdentifyResultsRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="GetIdentifyResultsResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="GetVerifyResults">        <soap:operation soapAction="GetVerifyResults" />        <wsdl:input name="GetVerifyResultsRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="GetVerifyResultsResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="Identify">        <soap:operation soapAction="Identify" />        <wsdl:input name="IdentifyRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="IdentifyResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="RetrieveInformation">        <soap:operation soapAction="RetrieveInformation" />        <wsdl:input name="RetrieveInformationRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="RetrieveInformationResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>  Biasprofile-1.

0-cd-01 Copyright © OASIS Open 2009.3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901         <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>      <wsdl:operation name="Verify">        <soap:operation soapAction="Verify" />        <wsdl:input name="VerifyRequest">          <soap:body use="literal" />        </wsdl:input>        <wsdl:output name="VerifyResponse">          <soap:body use="literal" />        </wsdl:output>        <wsdl:fault name=”BIASFault”>          <soap:fault name=”BIASFault” use=”literal” />        </wsdl:fault>      </wsdl:operation>    </wsdl:binding>    <wsdl:service name="BIAS_v1">      <wsdl:port name="BIAS_v1HttpBindingPort" binding="tns:BIAS_v1HttpBinding">        <soap:address location="http://your_URI/IRI_to_your_BIAS_implementation" />      </wsdl:port>    </wsdl:service>  </wsdl:definitions>  Biasprofile-1. 20 October 2009 Page 139 of 152 . All Rights Reserved.

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. All Rights Reserved.3902 Annex B. 20 October 2009 Page 140 of 152 . 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. 3916 3917 3918 Biasprofile-1.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.0-cd-01 Copyright © OASIS Open 2009.

TransformBiometricData.3919 B. 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.0-cd-01 Copyright © OASIS Open 2009. 3922 Client Application BIAS Client BIAS Server Agent BIAS Impl Verify Verify Verify ReturnToken CheckQuality TransformBiometricData VerifySubject MatchDecision Periodically Polling GetVerfiyResult MatchDecision MatchDecision Note that 1. CheckQuality. 20 October 2009 Page 141 of 152 .2 Asynchronous Verification 3920 3921 In this use case. 3923 3924 3925 Biasprofile-1. VerifySubject can be exposed as interfaces of BIAS server agent. All Rights Reserved.

3 Primitive Verification 3927 3928 3929 In this use case.3926 B. All Rights Reserved. 20 October 2009 Page 142 of 152 . the client rather than the service provider controls the workflow of the higher level operation.0-cd-01 Copyright © OASIS Open 2009. 3930 3931 3932 Biasprofile-1. In this case. the verification operation is performed as a series of requests using the BIAS primitive operations.

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
operations (in this case, a series of primitive BIAS operations) being performed by the BIAS service
provider.

3937
3938
3939

3940
3941

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

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
operations (in this case, a series of primitive BIAS operations) being performed by the BIAS service
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

TransformBiometricData

IdentifySubject

CreateSubject

SetBiographicData

SetBiometricData

AddSubjectToGallery
ReturnData
ReturnData
ReturnData

3950
3951
3952

Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

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
TransformBiometricData

TransformBiometricData
Return
IdentifySubject

IdentifySubject
Return
CreateSubject

CreateSubject
Return
SetBiographicData

SetBiographicData
Return
SetBiometricData

SetBiometricData
Return
AddSubjectToGallery

AddSubjectToGallery
Return

3958
Biasprofile-1.0-cd-01
Copyright © OASIS Open 2009. All Rights Reserved.

20 October 2009
Page 145 of 152

acme.0”?> 3989 <soap:Envelope xmlns:soap=”http://www.org/2003/05/soap-envelope”> 3976 <soap:Body> 3977 3978 3979 3980 <tns:CreateSubjectRequest xmlns:tns=”http://docs.3959 Annex C.acme.org/bias/bias‐1.w3.org/2003/05/soap-envelope”> 3990 3991 3992 3993 <soap:Body> <tns:CreateSubjectRequest xmlns:tns=”http://docs.oasis‐open. Samples (non-normative) 3960 C.0/”> <tns:Identity> 3994 3995 3996 3997 <tns:SubjectID>123456789</tns:SubjectID> </tns:Identity> </tns:CreateSubjectRequest> </soap:Body> Biasprofile-1.w3.0-cd-01 Copyright © OASIS Open 2009.com 3985 Content-Type: application/soap+xml. All Rights Reserved.org/bias/bias‐1.oasis‐open. charset=”utf-8” 3986 Content-Length: nnnn 3987 SOAPAction: “CreateSubject” 3988 <?xml version=”1.0”?> 3975 <soap:Envelope xmlns:soap=”http://www. 20 October 2009 Page 146 of 152 .1 3970 Host: www.0/” /> </soap:Body> 3981 </soap:Envelope> 3982 Create Subject Request with SubjectID Parameter:   3983 POST /bias HTTP/1.1 Create Subject Request/Response Example 3961 INCITS BIAS Specification  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 OASIS BIAS Examples  3968 Simple Create Subject Request:   3969 POST /bias HTTP/1.1 3984 Host: www.com 3971 Content-Type: application/soap+xml. charset=”utf-8” 3972 Content-Length: nnnn 3973 SOAPAction: “CreateSubject” 3974 <?xml version=”1.

w3.org/bias/bias‐1.oasis‐open.oasis‐open.0”?> 4006 <soap:Envelope xmlns:soap=”http://www. charset=”utf-8” 4023 Content-Length: nnnn 4024 <?xml version=”1.org/2003/05/soap-envelope”> 4007 4008 4009 4010 <soap:Body> <tns:CreateSubjectRequest xmlns:tns=”http://docs. 20 October 2009 Page 147 of 152 .1 4001 Host: www.acme.org/bias/bias‐1.w3.0/”> <tns:ResponseStatus> 4030 <tns:Return>0</tns:Return> 4031 </tns:ResponseStatus> 4032 <tns:Identity> 4033 4034 4035 4036 <tns:SubjectID>123456789</tns:SubjectID> </tns:Identity> </tns:CreateSubjectResponse> </soap:Body> 4037 </soap:Envelope> 4038 Create Subject Response with Optional OASIS BIAS Content:   Biasprofile-1.org/2003/05/soap-envelope”> 4026 4027 4028 4029 <soap:Body> <tns:CreateSubjectResponse xmlns:tns=”http://docs.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.1 200 OK 4022 Content-Type: application/soap+xml.3998 </soap:Envelope> 3999 Create Subject Request with Optional OASIS BIAS Content:   4000 POST /bias HTTP/1.0/”> <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:SubjectID>123456789</tns:SubjectID> </tns:Identity> </tns:CreateSubjectRequest> </soap:Body> 4019 </soap:Envelope> 4020 Simple Create Subject Response:   4021 HTTP/1. charset=”utf-8” 4003 Content-Length: nnnn 4004 SOAPAction: “CreateSubject” 4005 <?xml version=”1.0”?> 4025 <soap:Envelope xmlns:soap=”http://www.com 4002 Content-Type: application/soap+xml.

0-cd-01 Copyright © OASIS Open 2009.2 Set Biographic Data Request/Response Example 4060 INCITS BIAS Specification  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" <parameter name="Return" type="xs:unsignedLong" direction="out" /> 4070 </interface> 4071 OASIS BIAS Examples  4072 Set Biographic Data Request:   4073 POST /bias HTTP/1.0”?> 4043 <soap:Envelope xmlns:soap=”http://www.4039 HTTP/1.org/bias/bias‐1.oasis‐open.0”?> 4079 <soap:Envelope xmlns:soap=”http://www.1 4074 Host: www. charset=”utf-8” 4076 Content-Length: nnnn 4077 SOAPAction: “SetBiographicData” 4078 <?xml version=”1.w3.org/2003/05/soap-envelope”> 4044 4045 4046 <soap:Body> <tns:CreateSubjectResponse xmlns:tns=”http://docs. charset=”utf-8” 4041 Content-Length: nnnn 4042 <?xml version=”1. 20 October 2009 Page 148 of 152 .1 200 OK 4040 Content-Type: application/soap+xml.acme. All Rights Reserved.com 4075 Content-Type: application/soap+xml.org/2003/05/soap-envelope”> 4080 <soap:Body> Biasprofile-1.</tns:Message> 4051 </tns:ResponseStatus> 4052 <tns:Identity> 4053 <tns:SubjectID>123456789</tns:SubjectID> 4054 </tns:Identity> 4055 </tns:CreateSubjectResponse> 4056 4057 </soap:Body> </soap:Envelope> 4058 4059 C.w3.0/”> 4047 <tns:ResponseStatus> 4048 <tns:Return>0</tns:Return> 4049 4050 <tns:Message>Subject ID 123456789 successfully created.

oasis‐open.org/bias/bias‐1.0/”> 4106 <tns:ResponseStatus> 4107 <tns:Return>0</tns:Return> 4108 </tns:ResponseStatus> 4109 </tns:SetBiographicDataResponse> 4110 4111 </soap:Body> </soap:Envelope> 4112 4113 C.oasis‐open.0/”> 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 Set Biographic Data Response:   4098 HTTP/1.3 Set Biometric Data Request/Response Example 4114 INCITS BIAS Specification  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" /> Biasprofile-1.org/2003/05/soap-envelope”> 4103 <soap:Body> 4104 <tns:SetBiographicDataResponse 4105 xmlns:tns=”http://docs. charset=”utf-8” 4100 Content-Length: nnnn 4101 <?xml version=”1.1 200 OK 4099 Content-Type: application/soap+xml.0”?> 4102 <soap:Envelope xmlns:soap=”http://www.org/bias/bias‐1.w3.4081 <tns:SetBiographicDataRequest 4082 xmlns:tns=”http://docs.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. 20 October 2009 Page 149 of 152 .

org/2003/05/soap-envelope”> 4154 4155 <soap:Body> <tns:SetBiometricDataResponse 4156 4157 xmlns:tns=”http://docs. charset=”utf-8” 4151 Content-Length: nnnn 4152 <?xml version=”1.com 4128 Content-Type: application/soap+xml.w3.org/bias/bias‐1.oasis‐open.4122 <parameter name="Return" type="xs:unsignedLong" direction="out" /> 4123 </interface> 4124 OASIS BIAS Examples  4125 Set Biometric Data Request:   4126 POST /bias HTTP/1. All Rights Reserved. 20 October 2009 Page 150 of 152 .0”?> 4132 <soap:Envelope xmlns:soap=”http://www.0”?> 4153 <soap:Envelope xmlns:soap=”http://www.0-cd-01 Copyright © OASIS Open 2009.1 200 OK 4150 Content-Type: application/soap+xml.0/”> <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 Set Biometric Data Response:   4149 HTTP/1.org/bias/bias‐1.0/”> <tns:ResponseStatus> 4158 4159 4160 4161 4162 <tns:Return>0</tns:Return> </tns:ResponseStatus> </tns:SetBiometricDataResponse> </soap:Body> </soap:Envelope> Biasprofile-1.oasis‐open.org/2003/05/soap-envelope”> 4133 4134 <soap:Body> <tns:SetBiometricDataRequest 4135 4136 xmlns:tns=”http://docs.w3. charset=”utf-8” 4129 Content-Length: nnnn 4130 SOAPAction: “SetBiometricData” 4131 <?xml version=”1.acme.1 4127 Host: www.

Alessandro Triglia OSS Nokalva Mr. Catherine Tilton Daon Mr. these individuals contributed in the early stages of the development of this standard.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 151 of 152 . John Mayer-Splain US Department of Homeland Security Dr. Ed. Ramesh Nagappan Sun Mr. Charles Li Raytheon Mr. Murty Gurajada * Raining Data Corporation Mr. Gregory Zektser Booz Allen Hamilton 4169 4170 4171 * Though no longer members of the BIAS TC. Michael Wittman Raytheon Mr.4163 Annex D. Dale Hapeman US Department of Defense Dr. Biasprofile-1. 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. Guy Swope Raytheon Mrs. Brad Wing NIST (formerly DHS) Mr. Matthew Swayze Daon Mr. All Rights Reserved. the inputs from the INCITS technical committee M1 are also gratefully appreciated. 4172 In addition. Ross Michaels NIST Mr. Young Bang Booz Allen Hamilton Mr. Clay Sun Mr. Ash Parikh * Raining Data Corporation Mr.

2.05 2008-09-29 TBD SSL/TLS requirement clarified Reordered material in 5.Breaking Clause 3 into 2 clauses for data elements and operations .Clarifications and formatting 0. 20 October 2009 Page 152 of 152 .01 2008-05-23 TBD Initial draft 0.0-cd-01 Copyright © OASIS Open 2009.3 & App C/D Updated references 2 new use cases added (App C) Updated examples in App D 0.11 2009-11-16 Tilton/Swayze Miscellaneous edits and clarifications 4175 Biasprofile-1.02 2008-07-23 TBD Inserted data dictionary Added normative references Updated sec 3 & 5 + Annex B 0.4173 Annex E.09 2009-07-24 Tilton/Swayze Incorporated comments from June review/meeting.03 2008-08-19 TBD WSDL updated 0. Revision History 4174 Revision Date Editor Changes Made 0.04 2008-09-11 TBD Updated references Added security requirements Corrected Fig. All Rights Reserved.07 2008-11-27 TBD Revised fault structures and error handling 0. 0.3 + 4. 3 0.10 2009-10-19 Tilton/Swayze Expansion of conformance clause 0.27 & App B) 0.06 2008-11-17 TBD Added BIAS operation name methods (new 5. Major changes included: .06a 2008-11-20 TBD Updated references 0.Specification of URI & IRI .08 2009-06-22 TBD Incorporated comments from informal public review.

Sign up to vote on this title
UsefulNot useful