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

Re: ldp-ISSUE-20 (POSTed resources): Identifying and naming POSTed resources [Use Cases and Requirements]

From: Henry Story <henry.story@bblfish.net>
Date: Mon, 8 Oct 2012 19:35:25 +0200
Message-Id: <76F69F46-4F90-43B6-9C44-B8680F540072@bblfish.net>
To: Linked Data Platform (LDP) Working Group <public-ldp-wg@w3.org>

On 8 Oct 2012, at 11:52, Linked Data Platform (LDP) Working Group Issue Tracker <sysbot+tracker@w3.org> wrote:

> 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"


I think the answer to this problem is simple and requires some text in section 4.3
http://www.w3.org/2012/ldp/hg/ldbp.html#http-post

to the effect that: one should POST an RDF document to a collection with relative 
URIs such that the relatives URIs in the document will be resolve relative to the 
URI created by the server for that resource.

So if you post

------------------------
 <> a foaf:PersonalProfileDocument;
   foaf:primaryTopic <#me> .

 <#me> a foaf:Person;
     foaf:name "Henry" .
------------------------

to a collection 

http://profile.example/2012/

then the server will create a resource http://profile.example/2012/93
against which the above document with relative URLs will be resolved
so that one ends up with a document which is isomorphic to

------------------------
 <http://profile.example/2012/93> a foaf:PersonalProfileDocument;
   foaf:primaryTopic <#me> .

 <http://profile.example/2012/93#me> a foaf:Person;
     foaf:name "Henry" .
------------------------




> 
> 
> * Should POST support a user supplied local-name 'hint'; e.g. based on the supplied rdfs:label, to support more human-readable URIs?

yes, Atom has something on this I think 
 http://tools.ietf.org/html/rfc5023#section-9.7

If it is good enough one should probably use that as they spent enormous amounts of time
discussing that.

>  Alternatively, an owl:sameAs could be used in the above to provide a user-friendly name.
> 
> 
> 

Social Web Architect
http://bblfish.net/


Received on Monday, 8 October 2012 17:36:13 UTC

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