ISSUE-35: POSTing to a container MUST yield a fresh URI

fresh-URI

POSTing to a container MUST yield a fresh URI

State:
CLOSED
Product:
Linked Data Platform Spec
Raised by:
Richard Cyganiak
Opened on:
2012-11-06
Description:
Section 5.4 talks about the new URIs that are generated when POSTing to a container:

[[
LDPC servers must respond with status code 201 (Created) and the Location header set to the new resource’s URL.

LDPC servers should assign the subject URI for the resource to be created using server application specific rules.
]]

This says that the resource is new, and therefore sort of implies that the URI has to be new too. But the sentence about “server-specific rules” seems to give lots of wiggle-room However, I think there should be a much stronger statement, along these lines:

[[
Once a URI has been assigned to a new resource (as indicated by the 201 response code and Location: header), then the same URI MUST NOT be assigned again in any subsequent request.
]]

This is to avoid a situation where a resource is assigned a “recycled” URI that was previously assigned to a different resource and then deleted or moved or whatever, as discussed by TimBL and others in the ISSUE-24 discussion at the F2F.
Related Actions Items:
Related emails:
  1. LDP Rec (from eric@w3.org on 2015-02-20)
  2. Re: Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI (from sspeiche@gmail.com on 2013-04-18)
  3. Re: Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI (from andy.seaborne@epimorphics.com on 2013-04-18)
  4. Re: Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI (from david@3roundstones.com on 2013-04-17)
  5. Proposal to close ISSUE-35: POSTing to a container MUST yield a fresh URI (from lehors@us.ibm.com on 2013-04-17)
  6. Re: ldp-ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior [Linked Data Platform core] (from ashok.malhotra@oracle.com on 2013-04-05)
  7. Re: ldp-ISSUE-35 (fresh-URI): POSTing to a container MUST yield a fresh URI [Linked Data Platform core] (from roger.menday@uk.fujitsu.com on 2012-11-06)
  8. ldp-ISSUE-35 (fresh-URI): POSTing to a container MUST yield a fresh URI [Linked Data Platform core] (from sysbot+tracker@w3.org on 2012-11-06)

Related notes:

Resolution: POSTing to a container MUST yield a fresh URI, by adding that servers SHOULD not reuse URLs while acknowledging that they MAY under certain circumstances, per Arnaud's suggestion: http://lists.w3.org/Archives/Public/public-ldp-wg/2013Apr/0065.html
See http://www.w3.org/2013/meeting/ldp/2013-04-22#resolution_2

Arnaud Le Hors, 22 Apr 2013, 16:45:49

Display change log ATOM feed


Chair, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: 35.html,v 1.1 2015/08/17 04:43:08 denis Exp $