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

Re: Creation of Containers

From: Alexandre Bertails <bertails@w3.org>
Date: Wed, 07 Nov 2012 22:54:31 -0500
Message-ID: <509B2CF7.9080606@w3.org>
To: Niclas Hoyer <niclas@verbugt.de>
CC: public-ldp-wg@w3.org
On 11/07/2012 04:38 PM, Niclas Hoyer wrote:
> Hi,
>
> is there a simple way to create a ldp container? I thought of turning a
> ldp resource into a container just by changing the rdf information, so
> if http://example.org/resource1 is a ldp resource the following HTTP
> request could turn the resource into a container:

That's basically the solution that TimBL and I ended up with when
implementing our first RWW server.

I didn't like the fact the server had to look at all the content in
order to decide what to do. That's ugly but we couldn't find anything
better.

The W3C Systeam is very interested in this use-case. Let's say that
our RRSAgent bot wants to store the RDF data for the IRC logs using
LDP instead of CVS. We would need to create first /2012 and then
/2012/11 before being able to create the final LDPR
/2012/11/27-irc-log.ttl.

Makes me think that we will also need a way to suggest templates when
creating resources...

Alexandre.

>
> PUT /resource1 HTTP/1.1
> Host: example.org
> Content-Type: text/turtle
> Content-Length: 188
>
> @prefix dcterms: <http://purl.org/dc/terms/>.
> @prefix ldp: <http://www.w3.org/ns/ldp#>.
>
> <http://example.org/resource1>
>      a ldp:Container ;
>      dcterms:title "A new empty container" .
>
> Should we cover this in an extra use case?
>
> A possible implementation could just start with a ldp resource. The user
> or client programs could create containers as they need them. I was
> thinking of a sioc:Thread that could also be a ldp:Container, so that
> other clients could reply on the thread easily.
>
> --
> Niclas
>
>
>
Received on Thursday, 8 November 2012 03:54:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:42 UTC