- From: Mark Baker <distobj@acm.org>
- Date: Wed, 11 Jan 2006 11:33:12 -0800
- To: public-rdf-dawg-comments@w3.org
I've been following along ... Though I mostly side with Kendall, I think he's in error when he refers to HTTP 403 as a "transport" level error. It is an application level error, because HTTP is an application protocol. The SOAP 1.2 HTTP binding uses HTTP in this way too. IMO, WSDL's support for describing RESTful services is pretty poor, so if you're going to use it I'd highly recommend defining the WSDL *after* the HTTP interface is completely defined, so as to prevent these problems with WSDL from messing up your messages. So if you need a corresponding WSDL fault in order to permit an HTTP 403 response to be interpreted with QueryRequestConfused semantics, then I think that should be defined. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com
Received on Wednesday, 11 January 2006 19:33:17 UTC