- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 19 Nov 2020 10:05:33 +0100
- To: James Fuller <jim@webcomposite.com>
- Cc: "HTTPbis WG (IETF)" <ietf-http-wg@w3.org>
Am 19.11.2020 um 07:58 schrieb James Fuller: > ... > Some of the answers of the following questions interest me for those > future discussions; > > * does SEARCH naturally assume working on collection of resources (uri's) ? Technically, no. > * how to generically report errors on a single resource within > returned results (ex. does 207 multi-status apply ?) Out of scope, I would say. > * if we are not constraining result format (or content type eg. return > a text/uri-list) then what is different from a > GET with some meta data saying 'this is a search' ? There are a few > slippery slopes here and esp hard mapping > HTTP semantics over many different things generically (eg. file > systems, databases, higher order ex., SPARQL, etc etc etc) > w/o cgi-bin devolution. The difference is that the "query" (for some value of that) can go into the payload. > The above further reinforces my unease of direct linkage to WEBDAV ... > but should be an interesting conversation. The intent is not to have any normative linkage to WebDAV (or almost none) when we're done. Best regards, Julian
Received on Thursday, 19 November 2020 09:05:49 UTC