>Like SOAP Fault message we could think on a standard response format >(maybe as a String into that header filed, or better into the response >body) and Pivot is JSON-centric in many places, so why not format that >as s JSON String ?
I think the encoding of any error messages should be left to the application. Also, XML (as is used in SOAP faults) and JSON both seem a bit heavy to put in a header. This is why I initially raised the question of whether or not we should support a response body in the error case. I'm still inclined to restrict error messages to the response headers, at least for now. We can always add support for the response body later, if the need arises.
