binding fault property placement inconsistencies from Jacek Kopecky on 2005-10-09 (public-ws-desc-comments@w3.org from October 2005)

From: Jacek Kopecky <jacek.kopecky@deri.org>
Date: Sun, 09 Oct 2005 19:25:19 +0200
To: public-ws-desc-comments@w3.org
Message-Id: <1128878719.3489.6.camel@Kalb>

Hi all,

while working on the RDF binding, I've noticed an inconsistency in where
fault properties are placed in bindings: 

SOAP binding puts wsoap:code and subcodes and wsoap:header on binding
fault, and the same does HTTP mapping with whttp:code and whttp:header.
This basically shows that most specific binding fault properties are put
on the bindings faults.

Inconsistently, HTTP binding puts whttp:transferCoding on the fault
reference within operations - do we have a use case for different
transferCodings for the same faults when used in different operations?
If not, I suggest that transferCoding is moved from operation/infault
and outfault to binding/fault.

Best regards,

Jacek

Received on Monday, 10 October 2005 07:33:19 UTC