Title: ebXML Convergence with SOAP and Attachments
1ebXML Convergence with SOAP and Attachments
- Dick Brooks, John Ibbotson and Henrik Frystyk
Nielsen
2Background
- 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
3Disclaimer !!!
Note that this is WORK IN PROGRESS
4ebXML/SOAP Structure
Original
SOAP Compliant
Communication Protocol (SMTP, HTTP,
etc.)
MIME multipart/related
SOAP-ENVEnvelope /SOAP-ENVEnvelope
SOAP-ENVHeader ebMessageHeader
ebTraceRoute dsSignature /SOAP-ENVHeader
SOAP-ENVBody ebManifest
ebStatusData SOAP-EnvFault
ebErrorList /SOAP-EnvFault
ebAcknowledgements /SOAP-ENVBody
Payload
Payload
5MessageHeader
ltebhMessageHeadergt ltebhFromgtexample.comlt/ebhF
romgt ltebhTo type"userType"gt...lt/ebhTogt
ltebhCPAIdgthttp//www.ebxml.org/cpa/123456lt/ebhCP
AIdgt ltebhConversationIdgt987654321lt/ebhConversa
tionIdgt ltebhService type"myservicetypes"gtQuote
ToCollectlt/ebhServicegt ltebhActiongtNewPurchaseO
rderlt/ebhActiongt ltebhMessageDatagt
ltebhMessageIdgtUUID-2lt/ebhMessageIdgt
ltebhTimestampgt20000725T121905.000Zlt/ebhTimestamp
gt ltebhRefToMessageIdgtUUID-1lt/ebhRefToMessage
Idgt lt/ebhMessageDatagt ltebhQualityOfServiceIn
fo deliverySemanticsOnceAndOnlyOnce deliver
yReceiptRequestedSigned/gt lt/ebhMessageHeadergt
6Manifest
ltebbManifest id"Manifest"gt ltebbReference
id"pay01" xlinkhref"cidpayload-1"
xlinkrole"http//regrep.org/gci/purchaseOrder"gt
ltebbDescriptiongtPurchase Order for 100,000
widgetslt/ebbDescriptiongt ltebbSchema
location"http//regrep.org/gci/purchaseOrder/po.x
sd" version"1.0"/gt lt/ebbReferencegt lt/ebb
Manifestgt
7Summary
- ebXML TRP will be SOAP compliant
- Conversion follows KISS principle !
- Restructuring for SOAP Attachments
- No other major redesign work
- Adoption of XML DSIG