RE: SOAPAction Proposal

I generally like this direction in order to move forward and agree with
the discussion that we have to provide some guidance as to what we mean
by "intent".

Henrik

>  SOAP no longer requires the SOAPAction HTTP header.  While the
>  definition of, or a Web services requirement of a SOAPAction header,
>  as with any application-defined HTTP header, is left as an
>  implementation choice and is outside the scope of this specification,
>  a suggested usage of the SOAPAction header is that it can be used
>  to indicate the "intent" of the XMLP/SOAP HTTP request.