W3C home > Mailing lists > Public > www-ws-arch@w3.org > September 2002

Re: wire stack words and diagram

From: Mark A. Jones <jones@research.att.com>
Date: Mon, 30 Sep 2002 11:19:27 -0400
Message-ID: <3D986B7F.7080608@research.att.com>
To: Heather Kreger <kreger@us.ibm.com>
Cc: www-ws-arch@w3.org, jones@research.att.com

Heather, Editors:

Here is some additional text which would fit at the end of the
Packaging section in the wire stack text that you sent around:

For some applications, a purely XML-based representation of the
payload is awkward or inefficient.  Examples of such cases include
payloads which contain binary data, recursively structured envelopes,
syntactically ill-formed XML fragments, etc.  The most common
Packaging tactic in such cases is to introduce a multipart
representation which carries the SOAP envelope and its related data 
(commonly referred to as "attachments").  "SOAP Messages with 
Attachments", published as a W3C note 
[http://www.w3.org/TR/SOAP-attachments], is one proposed scheme;
"Direct Internet Message Encapsulation (DIME)"
[http://www.ietf.org/internet-drafts/draft-nielsen-dime-02.txt] is
another.  An abstract model for SOAP 1.2 attachment features 
[http://www.w3.org/TR/soap12-af/] specifies how SOAP 1.2 bindings use 
attachments and how those attachments are referenced from the envelope.


Mark A. Jones

Heather Kreger wrote:

> Here is the words I have for the wire stack.  Same caveats as before.
> (See attached file: wire.ZIP)
> Heather Kreger
> Web Services Lead Architect
> STSM, SWG Emerging Technology
> kreger@us.ibm.com
> 919-543-3211 (t/l 441)  cell:919-496-9572

Mark A. Jones
AT&T Labs
Shannon Laboratory
Room 2A-02
180 Park Ave.
Florham Park, NJ  07932-0971

email: jones@research.att.com
phone: (973) 360-8326
   fax: (973) 236-6453
Received on Monday, 30 September 2002 11:19:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:59 UTC