Re: ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs

I have updated the issue a little, after re-reading it more carefully.

Currently when creating a resource by POSTing a Turtle document to a container one cannot use the following relative URIs in the POSTed content:

  <.>            to refer to the creating container
  <sibling>   to refer to a sibling of the content created
  <../other>  to refer to a child of the parent of this container 
  <sister/child> to refer to a child of a sister content created in this container

The reason one cannot use any of these URIs that are allowed by Turtle and allowed by the URI spec, is that one cannot know what the URL of the resource created by a container will be given the current definition of an LDPC. Will it have any relation at all to the container URL?  Since we are in the process of creating resources, it will help a lot to know when we are dealing with containers that have those properties. 

We therefore need to define a Container  class that makes this guarantee to the client. This can be a subclass of an LDPC or it could be a new requirement on an LDPC. 

On 4 Mar 2013, at 11:03, Linked Data Platform (LDP) Working Group Issue Tracker <sysbot+tracker@w3.org> wrote:

> ldp-ISSUE-50 (intuitive containers): Inuitive Containers: better support for relative URIs
> 
> http://www.w3.org/2012/ldp/track/issues/50
> 
> Raised by: Henry Story
> On product: 
> 
> Currently when creating resource by POSTing a Turtle resource to a container one cannot use the following relative URIs in the POSTed content:
> 
>  <.>            to refer to this container
>  <sibling>   to refer to a sibling of this container
>  <../other>  to refer to a child of the parent of this container
>  <sister/child> ....
> 
> The reason one cannot use any of these URIs that are allowed by Turtle and allowed by the URI spec, is that one cannot know what the URL of the resource created by a container will be. Will it have any relation at all to the container URL?  Since we are in the process of creating resources, it will help a lot to know when we are dealing with containers that have those properties. 
> 
> We therefore need to define a Container that makes this guarantee to the client. This can be a subclass of an LDPC or it can be a new Container class.
> 
> 
> 

Social Web Architect
http://bblfish.net/