2005/08/25ACS WG - Data transport with SOAP message 1 Data transport with SOAP message There is a W3C note proposing the SOAP with attachment: – WS-I Basic Profile 1.1 refers this as below: –Attachments Profile 1.0 SOAP Messages with Attachments (SwA) defines a MIME multipart/related structure for packaging attachments with SOAP messages. This profile complements the Basic Profile 1.1 to add support for conveying interoperable SwA-based attachments with SOAP messages.

2005/08/25ACS WG - Data transport with SOAP message 2 Some other specifications. Relevant specifications for data transport with SOAP. –SOAP 1.2 Attachment Feature –SOAP Message Transmission Optimization Mechanism

2005/08/25ACS WG - Data transport with SOAP message 3 SOAP message and MIME A SOAP message with MIME header. MIME-Version: 1.0 Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit Content-ID: Content-Location: claim061400a.xml <SOAP-ENV:Envelope xmlns:SOAP-ENV=" SOAP message

2005/08/25ACS WG - Data transport with SOAP message 4 SOAP message with attachment(1) A SOAP message with attachment will be stored in a multipart MIME structure. –The SOAP message itself will be stored in the first part of the multipart MIME structure will contain the SOAP envelope. –Attachments to the SOAP will be stored in other parts in a multipart MIME structure. –The SOAP message will contain reference to the attachment. –See example in next page. The SOAP body part in the envelope contains the ACS request.

2005/08/25ACS WG - Data transport with SOAP message 5 SOAP message with attachment(2) MIME-Version: 1.0 Content-Type: Multipart/Related; boundary=MIME_boundary; type=text/xml; start=" " Content-Description: This is the optional message description. Content-Location: --MIME_boundary Content-Type: text/xml; charset=UTF-8 Content-Transfer-Encoding: 8bit ontent-ID: Content-Location: claim061400a.xml <SOAP-ENV:Envelope xmlns:SOAP-ENV=" --MIME_boundary Content-Type: image/tiff Content-Transfer-Encoding: base64 Content-Location: claim061400a.tiff...base64-encoded TIFF data... --MIME_boundary-- SOAP message Attachment to the SOAP message, as another part of the multipart MIME message Reference to the attachment

2005/08/25ACS WG - Data transport with SOAP message 6 ACS request as a SOAP message ACS requests are represented in SOAP message. ACS (ARI) Create request is accompanied with AA document. The AA document itself can be embedded in the request message or an attachment to the message.

2005/08/25ACS WG - Data transport with SOAP message 7 ACS Create message (1) Discrete files in multipart MIME: : Each refers to other parts in MIME multipart structure (or external storage).

2005/08/25ACS WG - Data transport with SOAP message 8 Discrete files in multipart MIME -Structure of the ACS Create message Create Request (SOAP) AAD AC-1 AC-2 AC-n

2005/08/25ACS WG - Data transport with SOAP message 9 ACS Create message (2) A bundled file in a MIME structure: This refers to another parts in MIME multipart structure.

2005/08/25ACS WG - Data transport with SOAP message 10 A bundled file in multipart MIME -Structure of the ACS Create message Create Request (SOAP) A bundled file containing AAD and multiple AC’s

2005/08/25ACS WG - Data transport with SOAP message 11 In summary… The AA document for ACS Create request can be transported as SOAP with attachment. There are two possible embodiment to this. –Discrete files in multiple MIME –A bundled file in a MIME ACS Create request is accompanied with AA document in either format above.