RE: A different binding example (was RE: Binding)

> When a developer issue a GET on
> that resource, it returns the XML Schema of the expense report XML
> document that the queue accepts as input as well as meta information:
> - request needs to include a signature header element for authentication
> - request needs a callback header element (containing a callback URL).
> - request needs a unique correlation set: rule on how the unique key/message id
>   can be computed using data element contained in the request.

It's probably faster to say that the GET returns the WSDL for the service (assuming we'll soon have a standard way for expressing SOAP Features in WSDL).

Ugo