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

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.

Received on Monday, 4 March 2013 10:03:35 UTC