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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3. Message string 0.2. AlgorithmVersion VersionType 0.2.34 ReturnCode Type: unsignedLong Description: Return value specifying success or other condition.1 N A short message corresponding to the return code.2. ReturnCode Enumeration Values Value Description 0 Success 3.2.1 N The version of the algorithm used to determine the quality.33 ResponseStatus Field Type # ? ResponseStatus 359 360 361 Y Return ReturnCode 1 Y The return code indicates the return status of the operation. however.0-cd-01 Copyright © OASIS Open 2009.35 Score Type: float Description: Match result or quality score. 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.. 3. All Rights Reserved.Field 358 Type # ? Meaning AlgorithmVendor VendorIdentifier 1 Y The vendor of the quality algorithm used to determine the quality score. 20 October 2009 Page 27 of 152 . 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. 3. Quality scores. AlgorithmVendorProductID ProductID 1 Y The vendor’s ID for the algorithm used to determine the quality.. 362 363 364 Meaning NOTE: Matching scores MAY be in a standardized or proprietary form in terms of value range and interpretation. follow the definition found in ISO/IEC 19785-3. section 13.36 TokenType Field Type # TokenType   ? Meaning Y Defines a token that is returned for asynchronous processing. Biasprofile-1.

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

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

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

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

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

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

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

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

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

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

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

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

1 N Biographic data associated with the candidate match. BiographicData BiographicDataType 0. Score Score 0. TokenType 1 Y A value used to retrieve the results of an IdentifySubject request. BIASOperationName Token 467 Response Message Field Type # GetIdentifySubjectResultsResponse ? Meaning Y The response to a GetIdentifySubjectResults operation. Return ReturnCode 1 Y The return code indicates the return status of the operation.1 N The match score.1 N A short message corresponding to the return code. ResponseStatus CandidateList Candidate Biasprofile-1. 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. BIRList CBEFF_BIR_ListType 1 Y Biometric data associated with the candidate match.. Message string 0.. which includes a candidate list... 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. All Rights Reserved.Field Type # ? Meaning string 0.. CandidateListType 1 Y A rank-ordered list of candidates that have a likelihood of matching the input biometric sample. 20 October 2009 Page 40 of 152 .0-cd-01 Copyright © OASIS Open 2009. CandidateType 0.* N A single candidate. ResponseStatus 1 Y Returned status for the operation.1 N Identifies the BIAS operation that is being requested: “GetIdentifySubjectRes ults”.

the implementing system returns a token. 20 October 2009 Page 41 of 152 .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. 473 474 475 476 477 If the IdentifySubject operation is implemented as a synchronous service.. GalleryID BIASIDType 1 Y The identifier of the gallery or population group which will be searched.1 N Identifies the requesting application..1 N Identifies the BIAS operation that is being requested: “IdentifySubject”. 468 4.1 N Common request parameters that can be used to identify the requester.1 N Identifies the user or instance of the requesting application. the implementing system immediately processes the request and returns the results in the candidate list. a data structure containing the biometric sample for the search. GenericRequestParameters 0. which is an indication that the request is being handled asynchronously. returning a rank-ordered candidate list of a given maximum size.0-cd-01 Copyright © OASIS Open 2009.. Application ApplicationIdentifier 0. ApplicationUser ApplicationUserIdentifier 0.* N CBEFF structure containing information about a biometric sample.. If the IdentifySubject operation is implemented as an asynchronous service. BIASOperationName string 0. All Rights Reserved. Identity BIASIdentity 1 Y Contains the BIR. In this case.1. the GetIdentifySubjectResults operation is used to poll for the results of the IdentifySubject request. 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. GenericRequestParameters BiometricData Biasprofile-1.

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

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

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

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

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

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

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

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

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

1 N A short message corresponding to the return code.0-cd-01 Copyright © OASIS Open 2009. that are supported by the BIAS implementation. Either a Score or a Decision element MUST be used. string Decision 0.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.1. Message string 0. Return ReturnCode 1 Y The return code indicates the return status of the operation. 522 Response Message Field Type # PerformFusionResponse ? Meaning Y The response to the PerformFusion operation. ResponseStatus Match 523 4.. Either a Score or a Decision element MUST be used. galleries. Biasprofile-1..1 C The match decision assigned by the matching algorithm.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. All Rights Reserved. ResponseStatus 1 Y Returned status for the operation. 20 October 2009 Page 51 of 152 ..1 C The similarity score assigned by the matching algorithm. etc. Score Score 0. options. Refer to Annex A in the INCITS BIAS standard for conformance requirements regarding which capability names an implementation must use in the QueryCapabilities operation.

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

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

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

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

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

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

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

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

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

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

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

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

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

ResponseStatus ReturnData 635 4... Message string 0. TokenType 1 Y A value used to retrieve the results of the Enroll request.0-cd-01 Copyright © OASIS Open 2009. the implementing system returns a token and the GetIdentifyResults operation is used to poll for the results of the original Identify request. Return ReturnCode 1 Y The return code indicates the return status of the operation. InformationType 0. 644 Biasprofile-1.1 N A short message corresponding to the return code. If the Identify operation is implemented as an asynchronous service. 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. This operation is used in conjunction with the Identify operation.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.3 GetIdentifyResults 636 GetIdentifyResultsRequest 637 GetIdentifyResultsResponse 638 639 640 641 The GetIdentifyResults operation retrieves the identification results for the specified token.1 N Identifies the BIAS operation that is being requested: “GetEnrollResults”. 642 643 If the service provider implements an asynchronous Identify operation.2. All Rights Reserved. ResponseStatus 1 Y Returned status for the operation. 20 October 2009 Page 68 of 152 ..1 N Contains the output data for the response. BIASOperationName Token 634 Response Message Field Type # GetEnrollResultsResponse ? Meaning Y The response to a GetEnrollResults operation. then it MUST also implement the GetIdentifyResults 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. Return ReturnCode 1 Y The return code indicates the return status of the operation.645 Request Message Field Type # GetIdentifyResultsRequest Meaning Y Retrieves the identification results for the specified token GenericRequestParameters 0...0-cd-01 Copyright © OASIS Open 2009. ResponseStatus 1 Y Returned status for the operation. Message string 0. GenericRequestParameters Token 646 ? Response Message Field Type # GetIdentifyResultsResponse ? Meaning Y The response to a GetIdentifyResults operation. ApplicationUser ApplicationUserIdentifier 0. TokenType 1 Y A value used to retrieve the results of the Identify request. All Rights Reserved...1 N A short message corresponding to the return code.1 N Common request parameters that can be used to identify the requester.1 N Identifies the BIAS operation that is being requested: “GetIdentifyResults”. InformationType 0. 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. Application ApplicationIdentifier 0. BIASOperationName string 0. 20 October 2009 Page 69 of 152 .1 N Identifies the requesting application. ResponseStatus ReturnData Biasprofile-1.1 N Identifies the user or instance of the requesting application.1 N Contains the output data for the response...

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

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

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

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

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

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

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

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

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

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

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

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

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

org/bias/ns/bias‐ 1.0" encoding="UTF‐8"?>    <wsdl:definitions xmlns:wsdl="http://schemas.0"  xmlns:tns="http://docs.w3.0. All Rights Reserved.257.xmlsoap.</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.0-cd-01 Copyright © OASIS Open 2009.xmlsoap.</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.</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.0/">        <xsd:complexType name="AggregateRequestTemplate" abstract="true">          <xsd:annotation>            <xsd:documentation>Base template for BIAS aggregate service requests.org/2001/XMLSchema" xmlns:iso‐iec19785‐3‐7="urn:oid:1.oasis‐open.oasis‐open.7.0/" targetNamespace="http://docs.xmlsoap.org/bias/ns/bias‐1.org/2001/XMLSchema" elementFormDefault="qualified"  targetNamespace="http://docs. 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.19785.1020 Annex A.org/wsdl/soap/" xmlns:http="http://schemas.1.org/wsdl/"  xmlns:soap="http://schemas.1.oasis‐open.</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.</xsd:documentation>                  </xsd:annotation>                </xsd:element>              </xsd:sequence>            </xsd:extension>          </xsd:complexContent>        </xsd:complexType>        <xsd:simpleType name="ApplicationIdentifier">  Biasprofile-1.org/wsdl/http/"  xmlns:xsd="http://www.0/">    <wsdl:types>      <xsd:schema xmlns:xsd="http://www.w3. 20 October 2009 Page 85 of 152 .org/bias/ns/bias‐1.

</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.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.</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.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="BIASFaultCode">  Biasprofile-1.</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: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.</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.</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.</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. 20 October 2009 Page 86 of 152 .

</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="INVALID_SUBJECT_ID">              <xsd:annotation>                <xsd:documentation>The input subject ID is empty or in an invalid format. All Rights Reserved.</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="BIR_DECRYPTION_FAILURE">              <xsd:annotation>                <xsd:documentation>The service could not decrypt an encrypted input BIR.</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="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="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. 20 October 2009 Page 87 of 152 . on the input  BIR.0-cd-01 Copyright © OASIS Open 2009. if used.

</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. All Rights Reserved.</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.</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.</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="INVALID_IDENTITY_CLAIM">              <xsd:annotation>                <xsd:documentation>The identity claim requested is already in use.</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.0-cd-01 Copyright © OASIS Open 2009.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:enumeration>            <xsd:enumeration value="NONEXISTANT_DATA">              <xsd:annotation>                <xsd:documentation>The data requested for deletion does not exist.</xsd:documentation>              </xsd:annotation>            </xsd:element>            <xsd:element minOccurs="0" maxOccurs="1" name="BIASFaultDescription" type="xsd:string">              <xsd:annotation>  Biasprofile-1. 20 October 2009 Page 88 of 152 .</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.

20 October 2009 Page 89 of 152 .1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281               <xsd:documentation>Provides detailed information about a BIAS fault. and biometric data.            </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.  Includes the Identity's reference identifiers.</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.0-cd-01 Copyright © OASIS Open 2009.</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.</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. All Rights Reserved.</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: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. required for encounter‐ centric models.</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. such as trace  details.              biographic data.</xsd:documentation>              </xsd:annotation>            </xsd:element>  Biasprofile-1.

</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.1” for FBI‐EFTS or “2. INT‐I.</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. HR‐XML. NIEM. xNAL.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. 20 October 2009 Page 90 of 152 .</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:sequence>            <xsd:any namespace="##any">              <xsd:annotation>                <xsd:documentation>Biographic data formatted according to a specific format.</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.  FBI‐EBTS.0-cd-01 Copyright © OASIS Open 2009. Use these names for common formats: FBI‐EFTS.</xsd:documentation>            </xsd:annotation>  Biasprofile-1. All Rights Reserved.0” for  NIEM). “7. DOD‐EBTS.g..</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.</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.

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

20 October 2009 Page 92 of 152 .0-cd-01 Copyright © OASIS Open 2009.</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.</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. working group. as  defined by CBEFF.</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. or other CBEFF  biometric organization that has defined the format for the biometric data.</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. as defined by  CBEFF. 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:sequence>        </xsd:complexType>        <xsd:complexType name="BiometricDataListType">          <xsd:annotation>            <xsd:documentation>A list of biometric data elements. All Rights Reserved.</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.            </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.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>  Biasprofile-1.</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.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. utilizing the Candidate Type to              represent each element in the set.            </xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Score" type="tns:Score" minOccurs="0" maxOccurs="1">              <xsd:annotation>                <xsd:documentation>The match score.</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="Candidate" type="tns:CandidateType" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>A single candidate.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: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.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>            <xsd:element name="Capability" type="tns:CapabilityType" minOccurs="0" maxOccurs="unbounded">              <xsd:annotation>                <xsd:documentation>A single capability. 20 October 2009 Page 93 of 152 .</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: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.

All Rights Reserved.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>            </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="CBEFFPatronFormat">              <xsd:annotation>                <xsd:documentation>A patron format supported by the implementing system.</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="AggregateReturnData">              <xsd:annotation>                <xsd:documentation>A data element returned 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.0-cd-01 Copyright © OASIS Open 2009.</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. 20 October 2009 Page 94 of 152 .</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>  Biasprofile-1.</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.

All Rights Reserved.</xsd:documentation>              </xsd:annotation>            </xsd:element>  Biasprofile-1.</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: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: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: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="SupportedBiometric">              <xsd:annotation>                <xsd:documentation>A biometric type supported by the implementing system.</xsd:documentation>              </xsd:annotation>            </xsd:enumeration>            <xsd:enumeration value="Gallery">              <xsd:annotation>                <xsd:documentation>A gallery or population group supported by the implementing  system.0-cd-01 Copyright © OASIS Open 2009.</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.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="IdentityModel">              <xsd:annotation>                <xsd:documentation>Identifies whether the implementing system is person‐centric or encounter‐centric  based. 20 October 2009 Page 95 of 152 .

All Rights Reserved.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.</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: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: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.0-cd-01 Copyright © OASIS Open 2009.</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. with either a non‐XML or XML  representation.</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. 20 October 2009 Page 96 of 152 .</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.

All Rights Reserved. 20 October 2009 Page 97 of 152 .</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:element>          </xsd:sequence>        </xsd:complexType>        <xsd:complexType name="EncounterListType">          <xsd:annotation>            <xsd:documentation>Defines a set of encounters.0-cd-01 Copyright © OASIS Open 2009.</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: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.</xsd:documentation>          </xsd:annotation>          <xsd:sequence>  Biasprofile-1.</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: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: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. All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009.</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:sequence>        </xsd:complexType>        <xsd:complexType name="FusionInformationType">          <xsd:annotation>            <xsd:documentation>Represents the information necessary to perform a fusion  operation. as defined by  CBEFF. as input to the PerformFusion request. 20 October 2009 Page 98 of 152 .</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.</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.            </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>  Biasprofile-1.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.

</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.</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.0-cd-01 Copyright © OASIS Open 2009.</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 . and it does              not specify nor require any particular data element.            </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. All Rights Reserved.</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.</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.  Biasprofile-1.

</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:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="MatchType">          <xsd:annotation>            <xsd:documentation>The result of a fusion method.</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.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. 20 October 2009 Page 100 of 152 .</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.</xsd:documentation>          </xsd:annotation>  Biasprofile-1. Processing options should be              defined by the implementing system.            </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.0-cd-01 Copyright © OASIS Open 2009. as defined by  CBEFF. The ProcessingOptionsType provides a              method to represent those options.

</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: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:sequence>            <xsd:element name="ResponseStatus" type="tns:ResponseStatus" minOccurs="1" maxOccurs="1">  Biasprofile-1.</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. All Rights Reserved.</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.0-cd-01 Copyright © OASIS Open 2009.</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: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: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.

 see the  Biasprofile-1. 20 October 2009 Page 102 of 152 .</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.</xsd:documentation>              </xsd:annotation>            </xsd:element>          </xsd:sequence>        </xsd:complexType>        <xsd:simpleType name="VendorIdentifier">          <xsd:annotation>            <xsd:documentation>Identifies a vendor.</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:float" />        </xsd:simpleType>        <xsd:complexType name="TokenType">          <xsd:annotation>            <xsd:documentation>Defines a token that is returned for asynchronous processing. All Rights Reserved.</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.0-cd-01 Copyright © OASIS Open 2009.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:restriction base="xsd:string" />        </xsd:simpleType>        <xsd:complexType name="Version">          <xsd:annotation>            <xsd:documentation>              For a description or definition of each data element.

</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.              </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:element>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>The identity to add to the gallery.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:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="CheckQualityRequest">  Biasprofile-1.</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. 20 October 2009 Page 103 of 152 . All Rights Reserved.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: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:element name="Quality" type="tns:QualityData" minOccurs="0" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Specifies a particular algorithm vendor and vender product ID.0-cd-01 Copyright © OASIS Open 2009.              </xsd:documentation>            </xsd:annotation>  Biasprofile-1.</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>            <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. All Rights Reserved.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.</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.

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. containing                the classification of a biometric sample. 20 October 2009 Page 105 of 152 .0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.              </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. containing the subject  Biasprofile-1.              </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.</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.

All Rights Reserved.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.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.              </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.              </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. with a                given encounter. in the encounter‐centric model.</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.</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 .

 any associated encounter information.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.              </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.              </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.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="DeleteSubjectResponse">  Biasprofile-1. in the encounter‐centric model. in an encounter‐centric                model. 20 October 2009 Page 107 of 152 . with a                given encounter.</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.

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. All Rights Reserved.              </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. 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:complexContent>              <xsd:extension base="tns:ResponseTemplate" />            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="GetIdentifySubjectResultsRequest">          <xsd:complexType>            <xsd:annotation>  Biasprofile-1.</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.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="DeleteSubjectFromGalleryResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a DeleteSubjectFromGallery request.

20 October 2009 Page 109 of 152 . All Rights Reserved.              </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: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. which includes a candidate list.</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.</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.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.              </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: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. a data structure containing the biometric sample for the  search. All Rights Reserved.</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:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Contains the BIR.0-cd-01 Copyright © OASIS Open 2009. returning a                rank‐ordered candidate list.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. returned with  asynchronous request processing.</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. 20 October 2009 Page 110 of 152 . returned with successful synchronous request processing.

 the                        encounter‐centric model is being used.              </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.  In the                encounter‐centric model. biographic data exists.                      </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.                      </xsd:documentation>  Biasprofile-1.0-cd-01 Copyright © OASIS Open 2009. non‐empty if the service was                        successful.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. 20 October 2009 Page 111 of 152 . 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.              </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.</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. non‐empty if the service                        was successful.  If an encounter ID is not                specified and encounter data exists for the subject. and an encounter                        identifier was not specified. biographic data exists. a subject and an  encounter. in the encounter‐centric model. All Rights Reserved. containing a list                of biographic data elements stored for a subject. the list                of encounter IDs which contain biographic data is returned. the biographic data elements for a                specific encounter are returned.

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: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.</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.              </xsd:documentation>            </xsd:annotation>            <xsd:complexContent>              <xsd:extension base="tns:ResponseTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity">                    <xsd:annotation>  Biasprofile-1. the list                of encounter IDs which contain biometric data is returned. Note                that no actual biometric data is returned by this service (see                the RetrieveBiometricInformation service to obtain the biometric                data).  If an encounter ID is not                specified and encounter data exists for the subject. All Rights Reserved. 20 October 2009 Page 112 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. the biometric data elements for a                specific encounter are returned. containing a list                of biometric data elements stored for a subject.  In the                encounter‐centric model. a subject and an  encounter.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="PerformFusionRequest">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                Accepts either match score or match decision information and creates a fused match result.              </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: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. 20 October 2009 Page 113 of 152 .0-cd-01 Copyright © OASIS Open 2009.              </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. All Rights Reserved.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.

 galleries.</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. 20 October 2009 Page 114 of 152 . a subject and an  encounter.0-cd-01 Copyright © OASIS Open 2009.                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. options.              </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. etc.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. All Rights Reserved.              </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:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name="QueryCapabilitiesResponse">          <xsd:complexType>            <xsd:annotation>              <xsd:documentation>                The response to a QueryCapabilities request.

</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. the biographic data associated with                a specified encounter is returned.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>  Biasprofile-1.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. In                the encounter‐centric model.              </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. the biographic                information associated with the most recent encounter is returned. a subject and an  encounter. All Rights Reserved. 20 October 2009 Page 115 of 152 .                containing the biographic data associated with a subject ID.</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:RequestTemplate">                <xsd:sequence>                  <xsd:element name="Identity" type="tns:BIASIdentity" minOccurs="1" maxOccurs="1">                    <xsd:annotation>                      <xsd:documentation>Identifies the subject or. in the encounter‐centric model. If the encounter ID is not                specified in the encounter‐centric model.0-cd-01 Copyright © OASIS Open 2009.

                containing the biometric data associated with a subject ID.              </xsd:documentation>            </xsd:annotation>  Biasprofile-1. All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009.  and includes the biographic data to store. If the encounter ID is not                specified in the encounter‐centric model. 20 October 2009 Page 116 of 152 . the biometric data associated with                a specified 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. the biometric                information associated with the most recent encounter is returned. 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>            <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.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. in the encounter‐centric model. In                the encounter‐centric model.

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. identifies the encounter ID assigned to a new  encounter. a subject and an encounter. identifies the encounter ID assigned to a new  encounter. in the 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>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:element>                </xsd:sequence>>              </xsd:extension>  Biasprofile-1. All Rights Reserved.</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. 20 October 2009 Page 117 of 152 .              </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.  and includes the biometric data to store.0-cd-01 Copyright © OASIS Open 2009.

</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. transformed biometric  information.</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. 20 October 2009 Page 118 of 152 . All Rights Reserved.</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:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>  Biasprofile-1.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.              </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.0-cd-01 Copyright © OASIS Open 2009.              </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.

 in the encounter‐centric model. a subject and an encounter. 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.0-cd-01 Copyright © OASIS Open 2009.</xsd:documentation>                    </xsd:annotation>                  </xsd:element>                  <xsd:element name="Merge" type="xsd:boolean" minOccurs="0" maxOccurs="1">                    <xsd:annotation>  Biasprofile-1.              </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.  and includes the biometric data to update. a subject and an encounter.  and includes the biographic data to update. in the encounter‐centric model.</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. All Rights Reserved.              </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.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.

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. All Rights Reserved. 20 October 2009 Page 120 of 152 .</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.0-cd-01 Copyright © OASIS Open 2009.</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.              </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.              </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.

 In this case. the                implementing system returns a token in the ReturnData                parameter.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. If the Enroll                aggregate service is implemented as an asynchronous service. 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. All Rights Reserved. 20 October 2009 Page 121 of 152 . in an                encounter‐centric model. which is an indication that the request is being                handled asynchronously.0-cd-01 Copyright © OASIS Open 2009. a new encounter to the system.</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. This may                be accomplished in a number of different ways according to                system requirements and/or resources.              </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.</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: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.</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.

              </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.</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.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. and the GetEnrollResults                service is used to poll for the results of the original Enroll                request. This service is used in                conjunction with the Enroll aggregate service. If the                Identify aggregate service is implemented as an asynchronous                service. If the Enroll                aggregate service is implemented as an asynchronous service.0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved. This service is                used in conjunction with the Identify aggregate service. the                implementing system returns a token. 20 October 2009 Page 122 of 152 . and the                GetIdentifyResults service is used to poll for the results of                the original Identify request. the implementing system returns a 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.

</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. All Rights Reserved.</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>            <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.</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. If the Verify                aggregate service is implemented as an asynchronous service.0-cd-01 Copyright © OASIS Open 2009. the                implementing system returns a token. and the GetVerifyResults                service is used to poll for the results of the original Verify                request. This service is used in                conjunction with the Verify aggregate 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.</xsd:documentation>            </xsd:annotation>  Biasprofile-1. 20 October 2009 Page 123 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. If                the Identify aggregate service is implemented as a synchronous                service. the                GetIdentifyResults service is used to poll for the results of                the Identify request. All Rights Reserved. 20 October 2009 Page 124 of 152 . If                the Identify aggregate service is implemented as an asynchronous                service. the implementing system returns a token in the                ReturnData parameter. which is an indication that the request is                being handled asynchronously.</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. the implementing system immediately processes the                request and returns the results in the ReturnData parameter.              </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.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.</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. In this case.

 this aggregate                service may be used to retrieve both biographic and biometric                information for a subject record. All Rights Reserved. In an encounter‐centric model.              </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.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. In a person‐centric model.</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 .                Either the IdentityClaim or ReferenceBIR input data elements in                the Identity parameter are required. If the Verify aggregate                service is implemented as a synchronous service. Either a SubjectID or EncounterID must be specified                in the Identify parameter.0-cd-01 Copyright © OASIS Open 2009. If the Verify aggregate  Biasprofile-1.</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.</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. and may identify what  type(s) of information should be returned.                this aggregate service may be used to retrieve biographic and/or                biometric information for either a single encounter or all                encounters. or in an encounter‐centric model                about an encounter. the                implementing system immediately processes the request and returns                the results in the ReturnData parameter.

</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.</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.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.              </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. the                implementing system returns a token in the ReturnData parameter.                which is an indication that the request is being handled                asynchronously. the GetVerifyResults service is                used to poll for the results of the Verify request. In this case.</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. All Rights Reserved.</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:element>                </xsd:sequence>              </xsd:extension>            </xsd:complexContent>          </xsd:complexType>        </xsd:element>        <xsd:element name=”BIASFault” type=”tns:BIASFaultDetail” />      </xsd:schema>    </wsdl:types>  Biasprofile-1. 20 October 2009 Page 126 of 152 .

20 October 2009 Page 127 of 152 .0-cd-01 Copyright © OASIS Open 2009.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.

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. 20 October 2009 Page 128 of 152 .0-cd-01 Copyright © OASIS Open 2009. All Rights Reserved.

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. All Rights Reserved. 20 October 2009 Page 129 of 152 .0-cd-01 Copyright © OASIS Open 2009.

20 October 2009 Page 130 of 152 .0-cd-01 Copyright © OASIS Open 2009.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. All Rights Reserved.

0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 131 of 152 . All Rights Reserved.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.

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. 20 October 2009 Page 132 of 152 . 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.xmlsoap.

20 October 2009 Page 133 of 152 .0-cd-01 Copyright © OASIS Open 2009.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. All Rights Reserved.

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. 20 October 2009 Page 134 of 152 . All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009.

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. All Rights Reserved. 20 October 2009 Page 135 of 152 .0-cd-01 Copyright © OASIS Open 2009.

All Rights Reserved.0-cd-01 Copyright © OASIS Open 2009. 20 October 2009 Page 136 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.

All Rights Reserved.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 .0-cd-01 Copyright © OASIS Open 2009.

All Rights Reserved.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. 20 October 2009 Page 138 of 152 .

3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901         <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. All Rights Reserved. 20 October 2009 Page 139 of 152 .0-cd-01 Copyright © OASIS Open 2009.

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. 3916 3917 3918 Biasprofile-1. 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. 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.0-cd-01 Copyright © OASIS Open 2009.3902 Annex B. a series of primitive BIAS operations) being performed by the BIAS service provider. All Rights Reserved. 20 October 2009 Page 140 of 152 .

20 October 2009 Page 141 of 152 . CheckQuality. VerifySubject can be exposed as interfaces of BIAS server agent. TransformBiometricData. 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. 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. All Rights Reserved.3919 B.2 Asynchronous Verification 3920 3921 In this use case. 3923 3924 3925 Biasprofile-1.

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

3933

B.4 Identification Use Case

3934
3935
3936

This use case uses the aggregate Identify operation in which a single request results in some set of
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

oasis‐open.com 3985 Content-Type: application/soap+xml. Samples (non-normative) 3960 C.oasis‐open. All Rights Reserved.org/2003/05/soap-envelope”> 3990 3991 3992 3993 <soap:Body> <tns:CreateSubjectRequest xmlns:tns=”http://docs.org/bias/bias‐1.com 3971 Content-Type: application/soap+xml.1 3970 Host: www.0-cd-01 Copyright © OASIS Open 2009.w3. charset=”utf-8” 3986 Content-Length: nnnn 3987 SOAPAction: “CreateSubject” 3988 <?xml version=”1.acme.1 3984 Host: www.0”?> 3975 <soap:Envelope xmlns:soap=”http://www.acme. 20 October 2009 Page 146 of 152 .3959 Annex C.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.w3. charset=”utf-8” 3972 Content-Length: nnnn 3973 SOAPAction: “CreateSubject” 3974 <?xml version=”1.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.0/”> <tns:Identity> 3994 3995 3996 3997 <tns:SubjectID>123456789</tns:SubjectID> </tns:Identity> </tns:CreateSubjectRequest> </soap:Body> Biasprofile-1.org/bias/bias‐1.

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

1 4074 Host: www. charset=”utf-8” 4076 Content-Length: nnnn 4077 SOAPAction: “SetBiographicData” 4078 <?xml version=”1. 20 October 2009 Page 148 of 152 .4039 HTTP/1.w3.0/”> 4047 <tns:ResponseStatus> 4048 <tns:Return>0</tns:Return> 4049 4050 <tns:Message>Subject ID 123456789 successfully created. charset=”utf-8” 4041 Content-Length: nnnn 4042 <?xml version=”1.0-cd-01 Copyright © OASIS Open 2009.org/bias/bias‐1.com 4075 Content-Type: application/soap+xml.oasis‐open.</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.org/2003/05/soap-envelope”> 4044 4045 4046 <soap:Body> <tns:CreateSubjectResponse xmlns:tns=”http://docs.1 200 OK 4040 Content-Type: application/soap+xml.0”?> 4043 <soap:Envelope xmlns:soap=”http://www.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.w3.acme.org/2003/05/soap-envelope”> 4080 <soap:Body> Biasprofile-1.0”?> 4079 <soap:Envelope xmlns:soap=”http://www. All Rights Reserved.

4081 <tns:SetBiographicDataRequest 4082 xmlns:tns=”http://docs.w3.oasis‐open.oasis‐open. charset=”utf-8” 4100 Content-Length: nnnn 4101 <?xml version=”1.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.0”?> 4102 <soap:Envelope xmlns:soap=”http://www.org/2003/05/soap-envelope”> 4103 <soap:Body> 4104 <tns:SetBiographicDataResponse 4105 xmlns:tns=”http://docs.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.1 200 OK 4099 Content-Type: application/soap+xml.0-cd-01 Copyright © OASIS Open 2009.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. All Rights Reserved. 20 October 2009 Page 149 of 152 .org/bias/bias‐1.org/bias/bias‐1.

org/2003/05/soap-envelope”> 4154 4155 <soap:Body> <tns:SetBiometricDataResponse 4156 4157 xmlns:tns=”http://docs.oasis‐open. charset=”utf-8” 4129 Content-Length: nnnn 4130 SOAPAction: “SetBiometricData” 4131 <?xml version=”1. 20 October 2009 Page 150 of 152 .1 4127 Host: www.org/2003/05/soap-envelope”> 4133 4134 <soap:Body> <tns:SetBiometricDataRequest 4135 4136 xmlns:tns=”http://docs.0-cd-01 Copyright © OASIS Open 2009. charset=”utf-8” 4151 Content-Length: nnnn 4152 <?xml version=”1.0”?> 4132 <soap:Envelope xmlns:soap=”http://www.acme.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.org/bias/bias‐1. All Rights Reserved.1 200 OK 4150 Content-Type: application/soap+xml.0/”> <tns:ResponseStatus> 4158 4159 4160 4161 4162 <tns:Return>0</tns:Return> </tns:ResponseStatus> </tns:SetBiometricDataResponse> </soap:Body> </soap:Envelope> Biasprofile-1.com 4128 Content-Type: application/soap+xml.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.w3.0”?> 4153 <soap:Envelope xmlns:soap=”http://www.oasis‐open.w3.

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

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

Sign up to vote on this title
UsefulNot useful