W3C home > Mailing lists > Public > public-ldp-wg@w3.org > January 2013

Re: creating collections

From: Steve Speicher <sspeiche@gmail.com>
Date: Tue, 29 Jan 2013 09:51:43 -0500
Message-ID: <CAOUJ7JpirpcnOeKNF3CMA1dSQqCXjzEYhjJkt1VH+Dnk0ASKOQ@mail.gmail.com>
To: "Wilde, Erik" <Erik.Wilde@emc.com>
Cc: "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Please see ISSUE-36

On Tue, Jan 29, 2013 at 9:47 AM, Wilde, Erik <Erik.Wilde@emc.com> wrote:
> hello ashok.
> On 2013-01-29 2:21 , "Ashok Malhotra" <ashok.malhotra@oracle.com> wrote:
>>1. We need to be able to create and delete collections.
>>Steve S indicates that there is agreement that the client should be able
>>to create collections.  This is good,
>>but we have not agreed on a mechanism to create collections although
>>there has been a good deal of mail on the subject.  Perhaps we need to
>>open an issue:  How are Collections Created?
> maybe an issue would be useful, so that we can focus and track
> discussions. following a standard REST pattern, you'd take a
> representation of a collection (containing only the info you need to
> create a collection, so it would be more of a proto-collection
> representation than an actual collection), and you'd POST it to a resource
> that will become the managing resource for that collection. in AtomPub,
> that would be the workspace. in LDP, if we allow nested collections, that
> might be a collection. if we have some anchor concept other than a "root
> collection", then that anchor resource would accept POSTing of collections
> as well. as a response to a successful creation request, the collection
> pops into existence on the server, and the server responds with a 201 and
> a location header that links to the new collection resource.
> cheers,
> dret.

- Steve
Received on Tuesday, 29 January 2013 14:52:10 UTC

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