- From: LDP <sysbot+tracker@w3.org>
- Date: Mon, 08 Oct 2012 09:52:43 +0000
- To: public-ldp-wg@w3.org
ldp-ISSUE-20 (POSTed resources): Identifying and naming POSTed resources [Use Cases and Requirements]
http://www.w3.org/2012/ldp/track/issues/20
Raised by: Steve Battle
On product: Use Cases and Requirements
Regarding use-case : <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#UC-BPC2:_Create_resource_within_a_container>
User-story <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#Hosting_POSTed_Resources> raises questions about POSTed resources.
* How is the inserted resource identified?
The use-case scenario assumes that the inserted resource is identified by including its relation via the membership predicate, to the membership subject.
e.g.
<> rdfs:member [
a helios_bt:BugtrackerIssue;
dc:identifier "58365";
dc:type "bug";
helios_bt:isInBugtracker eg:bugtracker
]
* How does the created resource relate to the RDF description?
See user-story <http://www.w3.org/2012/ldp/wiki/Use_Cases_And_Requirements#Hosting POSTed Resources>.
The example above assumes that the object of the insert is an anonymous (existentially quantified) resource that can be skolemized to produce a URI that can be returned in the Location header.
e.g. The response the the POST
HTTP/1.1 201 Created
Location: http://example.com/bugtracker/a0001
ETag: W/"1234567890"
* Should POST support a user supplied local-name 'hint'; e.g. based on the supplied rdfs:label, to support more human-readable URIs?
Alternatively, an owl:sameAs could be used in the above to provide a user-friendly name.
Received on Monday, 8 October 2012 09:52:44 UTC