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

Re: Proposal to close ISSUE-59 (recursive-delete): Reconsider usage of Aggregate/Composite construct to get predictable container delete behavior

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Fri, 19 Apr 2013 17:21:15 -0400
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
CC: Kingsley Idehen <kidehen@openlinksw.com>
Message-ID: <CD970227.10E57%erik.wilde@emc.com>
hello kinsgley.

On 2013-04-19 12:23 , "Kingsley Idehen" <kidehen@openlinksw.com> wrote:
>    A directory has a *containment* relation with resources.
>    A directory also has symbolic link (so to speak) relation with
>    resources. 
>    The relations above are inescapable. To ignore them is to introduce
>    regression or undue limitations. Henry explained the logic with
>    clarity.

it all depends on use cases, at least for the REST side of things. if
you're just browsing, you don't care about the difference between a file,
a hard link, and a soft link. once you start doing other things (such as
being able to add something as content, hard link, or soft link; or
removing something and understanding whether you're just unlinking or
actually deleting it), that difference becomes relevant and has to be
exposed. typically in REST, you start with use cases, design stateless
hypermedia-based application flows, make sure you have the interaction
data model and interaction affordances in place, and then you have a
working design (for that use case).


Received on Friday, 19 April 2013 21:22:06 UTC

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