OASIS XML Common Biometric Format (XCBF) TC

TC Page     Send a comment to this TC


Providing a standard way to describe information that verifies identity based on human characteristics such as DNA, fingerprints, iris scans, and hand geometry

Table of Contents


The XCBF 1.1 is an OASIS Standard, approved August 2003. This OASIS XCBF 1.1 Standard, document dated September 03, 2003 is available for free download.


The OASIS XML Common Biometric Format (XCBF) Technical Committee defines a common set of secure XML encodings for the patron formats specified in CBEFF, the Common Biometric Exchange File Format (NISTIR 6529). These XML encodings are based on the ASN.1 schema defined in ANSI X9.84:2003 Biometrics Information Management and Security. They conform to the XML Encoding Rules (XER) for ASN.1 defined in ITU-T Recommendation X.693, and rely on the security and processing requirements specified in X9.96 XML Cryptographic Message Syntax (XCMS).

For more information, see the TC Charter and FAQ


Technical Work Produced by the Committee

XML Common Biometric Format, OASIS Standard, approved August 2003

External Resources

Although not produced by the OASIS XCBF TC, the following information offers useful insights into its work.

XML Common Biometric Format (XCBF) Ratified as OASIS Standard
16 Sep 2003

OASIS XML Common Biometric Format Specification (XCBF) Submitted for Approval.
CoverPages, 5 August 2003

Web Services Security XCBF Token Profile
Cover Pages Newsletter, 26 Nov 2002

Canonical XML Encoding Rules (cXER) for Secure Messages. An ASN.1 Schema for Secure XML Markup
Cover Pages, Sep 2002

Mailing Lists and Comments

xcbf: the list used by TC members to conduct Committee work. TC membership required to post. TC members are automatically subscribed; the public may view archives.

xcbf-comment: a public mail list for providing input to the OASIS xcbf Technical Committee members. Send a comment or view archives.

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.