- From: James Leigh <james@3roundstones.com>
- Date: Thu, 14 Mar 2013 12:52:11 -0400
- To: Erik Wilde <dret@berkeley.edu>
- Cc: Martynas Jusevičius <martynas@graphity.org>, Pierre-Antoine Champin <pierre-antoine.champin@liris.cnrs.fr>, "public-ldp@w3.org" <public-ldp@w3.org>
On Thu, 2013-03-14 at 09:43 -0700, Erik Wilde wrote: > hello martynas. > > On 2013-03-14 9:28 , Martynas Jusevičius wrote: > > b) the resource describing person does not exist. > > You mint new URIs of the resource and the person and PUT the RDF into > > resource's URI. > > What's wrong with that? A client could that automatically. > > it's not the client's thing to decide on URIs for new resources, at > least in the usual case. servers manage the URI namespace and assign > URIs for new resources. clients may suggest URIs (well, mostly certain > path components of them) using HTTP Slug, but they cannot depend on the > server actually using these components. > Sure, but there is nothing wrong with the client suggesting the URI to use in the posted RDF model itself. The server is under no obligation to accept the RDF as-is. James
Received on Thursday, 14 March 2013 16:52:39 UTC