W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > January 2006

HTTP response code discussion

From: Mark Baker <distobj@acm.org>
Date: Wed, 11 Jan 2006 11:33:12 -0800
Message-ID: <c70bc85d0601111133n388fd46o48cb3f5ff0696cb0@mail.gmail.com>
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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:14:49 GMT