W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

ldp-ISSUE-24 (remain deleted): Should DELETED resources remain deleted? [Linked Data Platform core]

From: LDP <sysbot+tracker@w3.org>
Date: Mon, 15 Oct 2012 13:45:58 +0000
Message-Id: <E1TNkzW-0005V9-2s@tibor.w3.org>
To: public-ldp-wg@w3.org
ldp-ISSUE-24 (remain deleted): Should DELETED resources remain deleted? [Linked Data Platform core]

http://www.w3.org/2012/ldp/track/issues/24

Raised by: Ruben Verborgh
On product: Linked Data Platform core

Under 4.5 DELETE, the draft currently reads:

4.5.1 BPR 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, until another resource is created or associated with the same Request-URI.

Isn't the creation of another resource in contradiction with Cool URIs?

I see two cases:
1. the resource is permanently gone, which should result in a 410 and it should *not* be possible to create a resource again on this URI. Otherwise, the Cool URI principle would be broken.

2. the resource is temporarily gone, which results in a 404. It should *not* be possible to create another resource on this URI, only to re-upload the same resource here (the contents of which may have changed in the meantime, but it should still be the same resource).

This raises two additional issues:
- how does the server know the DELETE is permanent?
- how does the server know the resource is the same or different?
Received on Monday, 15 October 2012 13:45:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC