RE: [Fwd: Re: AFTF: new draft (resent)]

Just regarding the main issue, I believe the current text says
"describe" and not "create"--the intent was to indicate that a
representation should describe which encapsulation is used, not whether
it should be created or not. In other words, I agree that it should not
require the creation but I don't think the current text does... or am I
misunderstanding your concern?

Henrik

>"A representation of a compound SOAP structure MUST describe 
>the following three parts:
>
>An encapsulation mechanism for the primary SOAP message part 
>and for each secondary part. The encapsulation mechanism MAY 
>but need not be the same for all parts."
>
>I disagree.  Features are implemented by bindings.  There 
>should be nothing in this feature that should require the 
>creation of an encapsulation mechanism at all!  As correctly 
>noted later in the document, it is OK for the several parts to 
>each be sent separately (e.g. with separate GETs). Creating an 
>encapsulation is just one of the strategies that can be used 
>to implement this feature, and it is not in all cases 
>preferred.  I would not call it out at all, except as an 
>example of a likely strategy.  Instead, I would replace the 
>entire Representing Compound structs section with something 
>along the lines of: