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

Re: MKCOL for making collections

From: Alexandre Bertails <bertails@w3.org>
Date: Tue, 22 Jan 2013 11:53:56 -0500
Message-ID: <50FEC424.20805@w3.org>
To: "Wilde, Erik" <Erik.Wilde@emc.com>
CC: Steve Speicher <sspeiche@gmail.com>, Henry Story <henry.story@bblfish.net>, "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
On 01/22/2013 11:42 AM, Wilde, Erik wrote:
> On 2013-01-22 16:17 , "Steve Speicher" <sspeiche@gmail.com> wrote:
>> On Tue, Jan 22, 2013 at 10:03 AM, Henry Story <henry.story@bblfish.net>
>> wrote:
>>> ISSUE-36: Can applications create new containers?
>>> We cannot make a collection by POSTing a doument on a collection, since
>>> that
>>> creates a resource. We therefore would need a different HTTP Method to
>>> do this.
>> Why can't we do this?  A Container/Collection IS a resource.  So
>> therefore POST'ing the representation of it seems like the most
>> obvious way to create one.
> i agree, but where would you POST it? you cannot POST it to a collection,
> because that would be strange. so you either need some übercollection that
> you POST to to create new collections, or some other endpoint.
> fyi, atompub never specified creating collections. some people engineered
> around this by exposing übercollections, other by exposing specific
> resources (not collections) that you POST a new collection to. in our
> implementation, we give workspaces identifiers and then you POST to them.
> all of these ways work fine, and from all i've seen, people have used the
> well-defined representation of a collection as something to POST, and then
> this creates a new collection.

I'm not sure to understand how this works but you raised my attention. 
Can you give an example?


> cheers,
> dret.
Received on Tuesday, 22 January 2013 16:54:28 UTC

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