I've been following the recent thread reviewing the Proposed Infoset Addendum to SOAP Messages with interest particularly the differences between:
a) Treating attachments as if they were part of the XML Infoset (which PASWA proposes), vs
b) Treating attachments as first class citizens in their own right.
 
I can see benefits in both approaches in that efficiently putting a large "blob" in an attachment in a way that is transparent to the application can make the application processing simpler.
 
Alternatively, the idea of an attachment where the application is aware that is an attachment as a separate item is equally valid, for example an application that is processing an order that just happens to have terms and conditions attached to it as a PDF.

 
I also have one concern (and also a question) over the way PASWA works as described below ...
 
USING CID: IN XBINC:INCLUDE
There's a catch 22 here as:
1. You can only create the XML when you know the cid values to put in the XML
2. You only know the cid values when you marshall XML into the SOAP Message, but
3. You can't marshall the SOAP message until you have created the XML.
 
I know that you can get around this problem IF the generation of the XML and the SOAP Message is done by the same software at the same time. Although this will often be both possible and desirable it is, I think, something that will often not be possible to do.

<snip>