BIAS using eb XML n OASIS BIAS TC
BIAS using eb. XML n OASIS BIAS TC Meeting August 2006 n Pim van der Eijk n
Agenda n n n eb. XML Messaging BIAS using eb. XML Messaging Case study Discussion
The eb. XML initiative
Founding organizations n UN/CEFACT l l l United Nations Centre for Trade Facilitation and Electronic Business Created and maintains the UN/EDIFACT standards for Electronic Data Interchange (EDI) Made assessment in 1998/1999: n n EDI widely used … in (very) large companies OASIS l l Organization for Advancement of Structured Information Standards Creates and maintains XML interoperability specifications, broad industry support
The eb. XML initiative n Joint initiative by OASIS and UN/CEFACT l l 9/1999 open invitation to e-business community to join Series of plenary meetings n n n Goals: l l n Between 11/1999 and 5/2001 Specifications delivered on schedule in 5/2001 “Create a single global electronic marketplace where enterprises of any size and in any geographical location can meet and conduct business with each other” Provide a “modular, yet complete electronic business framework” Approach l l l Semantic interoperability Modular framework Leverage EDI experience, XML, Internet, Web technology
eb. XML modules n Messaging l n Collaboration Protocols and Agreements l n Technical Framework and Library Registry l n Bilateral trading configuration agreements Business Process l n Transport, routing and packaging Information Model and Services Core Components l Technical Framework and Library
eb. XML Today n Advanced framework for B 2 B l l l n Adoption steadily increasing l n State-of-the-art Complete and mature Addresses complex choreographed interactions Secure and reliable messaging interoperability Advanced registry functionality Large strategic projects e. Government, e. Health Lacking visibility
Implementation Support n Software l Open source implementations n l l l n http: //www. freebxml. org/ Large software platform companies Specialized B 2 B integration companies Adapter suppliers Consulting l Many (of the larger international) consulting companies have references
eb. XML Messaging
Messaging in eb. XML n Message Structure l l n Header information Payload enveloping (Business Documents) Messaging Protocol l Basic behavior of Message Service n l Reliable Messaging n l Basic functionality, like routing, correlation Sending Acknowledgments; retrying messages when not acknowledged (in time) Security n Setting/verifying digital signatures; encrypting payloads
eb. XML Messaging n Version 2 l l l n OASIS Standard since 2002 ISO 15000 -2 since 2004 Multiple interoperable software implementations Open Source implementation available In production today Version 3 l l Under development in eb. XML Messaging TC Provides alignment with Web Services, functional extensions
Message Structure n SOAP-withattachments l l l n Message is a single MIME container SOAP 1. 1 envelope in first MIME part Other MIME parts for payload Extra eb. XML info, namespace-qualified l l Signatures Reliable Messaging
eb. XML Message Header n Standard Header Information l l l n Reliable Messaging Header elements l n SOAP envelope with eb. XML extensions Party Identification of From and To Party Configuration Information Service and Action (links to CPA to BP) Message Identification and Correlation (Requests for) Acknowledgments Security Header Elements l Signatures of signed payloads
Sample Messages (1) n n Simple configuration with no reliable messaging and no digital signatures BIAS Request Verification message l n BIAS Send Match Decision message l n From Requester to BIAS Provider From BIAS Provider to Requester Structures l l MIME Container eb. XML SOAP header
POST http: //Sony. Vaio. lan: 4082/exchange/Seller HTTP/1. 1 Content-Type: multipart/related; type="text/xml"; boundary="---=_Part_0_23594703. 1145557140122" SOAPAction: "eb. XML" Host: Sony. Vaio. lan: 4082 Connection: close Content-Length: 9812 HTTP header ------=_Part_0_23594703. 1145557140122 Content-Type: text/xml Content-Transfer-Encoding: binary <? xml version="1. 0" encoding="UTF-8"? > <soap: Envelope xmlns: soap="http: //schemas. xmlsoap. org/soap/envelope/". . . Details omitted. . . </soap: Envelope> ------=_Part_0_23594703. 1145557140122 Content-Type: application/xml Content-Transfer-Encoding: binary Content-Disposition: attachment; filename=fingerprint. xml Content-Id: <A 1145557139942. 4491@Sony. Vaio> <Biometric. Objects><Biometric. Object><biometric. Header>. . . Details omitted. . . </Biometric. Objects> ------=_Part_0_23594703. 1145557140122 -- eb. XML SOAP envelope Business Document (biometric data)
Request Verification SOAP Header Sender and Recipient BIAS Service “Request Verification” Message Identification Business Document and Attachments
Match Decision SOAP Header Sender and Recipient reversed Same Conversation “Send Match Decision” Action Correlation Identification
Message Configuration n “CPAId” field in message identifies configuration l l l n Reliable messaging (retries, acknowledgments) Message signing using digital signatures (XML-DSig) Payload encryption for confidentiality (XML Encryption) CPA, a portable XML configuration language l l ISO 15000 -1 OASIS Standard Services, parameters, public certificates, transport details etc.
BIAS using eb. XML
Why use eb. XML for BIAS? n Open, interoperable standard; l n Reliable messaging l n n Obviates need for “acknowledgement BIAS message” Payload neutral: XML, JPEG, pre-XML biometric formats Supports both application scenarios: l l n “Proven technology”; available today Non-reliable, query/response (near-real-time) Asynchronous, reliable database updates Adaptable to security requirements
Criminal Justice system Juvenile Justice Collection Agency Police Prosecution Mental Health Service Probation Service Prison Service Court Forensic Institute Child Protection
Q&A n Pim van der Eijk l l Pim. vander. Eijk@oasis-open. org pvde@sonnenglanz. net
- Slides: 22