Re: PASWA, Include and Protocol Bindings and Content-Codings

> Also one neat part would be that the HTTP binding could use something
like
> Content-Encoding: x-paswa to declare that the message use this specific
> encoding of a SOAP envelope (if we don't want to define another MIME
> type).

That's interesting. It's specific to HTTP, but I imagine that most
transports will have an analogous function. In any case, if we go down a
binding route, we'll need to specify something seperate for each transport
anyway.

Thinking out loud, if it were done as something like a HTTP
content-coding, it would almost seem better to invent a new, non-XML
syntax to allow it to be more compact and efficient to process (as well as
not confusing the matter)...