- From: Raúl García Castro <rgarcia@fi.upm.es>
- Date: Thu, 16 May 2013 16:23:41 +0200
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Dear all, [[ LDP 1.0. 4.5.1 LDPR servers MUST remove the resource identified by the Request-URI. After a successful HTTP DELETE, a subsequent HTTP GET on the same Request-URI MUST result in a 404 (Not found) or 410 (Gone) status code. ]] A successful HTTP DELETE request (i.e., 2xx) does not imply that the resource has been deleted, the request may be accepted (i.e., status code 202) but not enacted. Does the LDP specification want to allow any other status code for the DELETE operation beyond the HTTP/1.1 recommended 200, 202, and 204? The other status codes do not make sense, and as the HTTP/1.1 specification does not enforce but recommend these three, it might be worthy making this a strong requirement in LDP. Another issue is that the second MUST clause implies that URIs will not be reusable. Proposal: State that only 200, 202 and 204 are allowed status codes for a successfull DELETE. Rewrite the second MUST so it covers the case of 202 (Accepted) and of reusing URIs. Kind regards, -- Dr. Raúl García Castro http://delicias.dia.fi.upm.es/~rgarcia/ Ontology Engineering Group Departamento de Inteligencia Artificial Universidad Politécnica de Madrid Campus de Montegancedo, s/n - Boadilla del Monte - 28660 Madrid Phone: +34 91 336 36 70 - Fax: +34 91 352 48 19
Received on Thursday, 16 May 2013 14:24:26 UTC