1 / 7

Convergence of ebXML with SOAP and Attachments - Vancouver Meeting Summary

This paper provides a historical overview of the convergence of ebXML and SOAP protocols, highlighting the resolution reached at the Vancouver meeting in February 2001. It discusses the technical challenges and progress made towards making ebXML TRP SOAP-compliant, emphasizing simplicity and the incorporation of XML DSIG. The text includes a detailed structure of the ebXML/SOAP communication protocol and outlines the key steps taken to enable SOAP with attachments in the ebXML framework.

joywhite
Download Presentation

Convergence of ebXML with SOAP and Attachments - Vancouver Meeting Summary

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ebXML Convergence with SOAP and Attachments Dick Brooks, John Ibbotson and Henrik Frystyk Nielsen

  2. Background • ebXML started in November 1999, continued through 2000 • ebXML viewed SOAP 1.0 as RPC and proprietary • SOAP 1.1 and XML Protocol formation seen as possible convergence route • Strong requirement for non XML (binary) • SOAP + Attachments not available • Technical willingness for convergence • Some IP issues outstanding • Resolution at Vancouver (Feb 2001) meeting • IP statements by SOAP 1.1 and Attachments owners • Work in progress by TRP WG to convert messaging services spec • Approval by ebXML plenary

  3. Disclaimer !!! Note that this is WORK IN PROGRESS

  4. ebXML/SOAP Structure Original SOAP Compliant Communication Protocol (SMTP, HTTP, etc.) MIME multipart/related SOAP-ENV:Envelope /SOAP-ENV:Envelope SOAP-ENV:Header eb:MessageHeader eb:TraceRoute ds:Signature /SOAP-ENV:Header SOAP-ENV:Body eb:Manifest eb:StatusData SOAP-Env:Fault eb:ErrorList /SOAP-Env:Fault eb:Acknowledgements /SOAP-ENV:Body Payload Payload

  5. MessageHeader <ebh:MessageHeader> <ebh:From>example.com</ebh:From> <ebh:To type="userType">...</ebh:To> <ebh:CPAId>http://www.ebxml.org/cpa/123456</ebh:CPAId> <ebh:ConversationId>987654321</ebh:ConversationId> <ebh:Service type="myservicetypes">QuoteToCollect</ebh:Service> <ebh:Action>NewPurchaseOrder</ebh:Action> <ebh:MessageData> <ebh:MessageId>UUID-2</ebh:MessageId> <ebh:Timestamp>20000725T121905.000Z</ebh:Timestamp> <ebh:RefToMessageId>UUID-1</ebh:RefToMessageId> </ebh:MessageData> <ebh:QualityOfServiceInfo deliverySemantics=”OnceAndOnlyOnce” deliveryReceiptRequested=”Signed”/> </ebh:MessageHeader>

  6. Manifest <ebb:Manifest id="Manifest"> <ebb:Reference id="pay01" xlink:href="cid:payload-1" xlink:role="http://regrep.org/gci/purchaseOrder"> <ebb:Description>Purchase Order for 100,000 widgets</ebb:Description> <ebb:Schema location="http://regrep.org/gci/purchaseOrder/po.xsd" version="1.0"/> </ebb:Reference> </ebb:Manifest>

  7. Summary • ebXML TRP will be SOAP compliant • Conversion follows KISS principle ! • Restructuring for SOAP + Attachments • No other major redesign work • Adoption of XML DSIG

More Related