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 16:52:05 -0500
Message-ID: <50FF0A05.2040704@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 03:27 PM, Wilde, Erik wrote:
> hello alexandre.
> On 2013-01-22 19:13 , "Alexandre Bertails" <bertails@w3.org> wrote:
>> Can you define what you mean by "LDP home document"?
> not in a very specific way right now, but something following the spirit
> of http://tools.ietf.org/html/draft-nottingham-json-home, providing a way
> how clients can start navigating the most important affordances of a REST
> service starting from a LDP home resource.

Thanks for the link.

In the case of LDP, I have the feeling that the LDPC from where you
want to create a sub-LDPC would be its own home document anyway. At
least, I don't see a counter-example.

>>From what I understand with what you say, I'm not sure if one could
>> create the collection /foo/bar/ only by talking with /foo/, or if it
>> must find the collection factory somewhere else.
> how linking is done exactly (i.e., which interactions affordances are
> exposed by which resources) still needs quite a bit of work, and in the
> end specific URIs don't matter anyway. but i'd assume that many services
> might expose a home resource at some URI x, and that there may be a
> collection factory that might end up creating x/y collections, but all of
> that really is up for the implementation to decide. it might also decide
> that the home resource is x and then a new collection always has a URI
> x/collection/y or something along these lines.

If I know that X is an LDPC, and that the LDP spec tells me how to
create a sub-LDPC from there directly, then I don't need anything
else, do I?

It looks like the home document notion is overkill to me and much more

>> In my understanding, a container is polymorphic (it accepts/contains
>> things of any kind), so there should not be any exception for
>> containing another LDPC. Just like a filesystem.
> nope, i'd say that a container/collection only accepts entries (ignoring
> the "non-RDF media type containers/collections" for now), and if you POST
> anything else, you'll get a "precondition violated" exception. what
> exactly is required for something to be a valid entry remains to be
> determined, but that will be what is essential for LDP's data model: what
> can you count on in LDP services, because that's what LDP chooses to
> manage.

My understanding is that it's application specific. LDP itself should
not restrict anything there.


> cheers,
> dret.
Received on Tuesday, 22 January 2013 21:52:45 UTC

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