Re: ISSUE-37: the Graph and Links model

> Hi Roger:
> Please look at the Wiki page devoted to issue-37.  Erik has described the AtomPub model there
> and I have made some comments.  Please add to the info there and try and answer the questions
> asked.  For example, how are collections created?  When a collection is deleted are all its members
> deleted as well?  And so on.
> All the best, Ashok
> 


hi Ashok, 

Yes, I am trying to extend the text and will place it onto wiki.  I am thinking about consistency of terminology, because "link collections" are the basis of the proposal, and on the wiki page "resource collections" are assumed.

Anyway, in the meantime here are some thoughts to your questions on the Wiki: 


1. "We need to be able to create and delete collections."

Collection creation is very common, instigated by the server and offered to the client in the flow of the application. The mechanism works even for generic construction (like in some generic information management application).  

Regarding delete, I quite like 'archive over delete', but I don't see a specific problem deleting collections (?) 


2. "When a collection is deleted are its members deleted also? Or is there an option?"

I don't believe that a client should necessary expect delete to extend to the descendants ... not least because it is difficult for a server to honour this every time. If the server decides to delete descendants then it should inform the client. 


3. "Can collections contain collections? In other words, are collections hierarchical?"

Yes. 

4. "Does each LDP model have/need a service document? If yes, perhaps collections could be created by PUT on the service document?"

I don't see a need for service documents. 


regards, 
Roger

> On 1/11/2013 2:51 PM, Roger Menday wrote:
>> I've tried to make a short description of a model proposal which I believe covers composition/ aggregation, paging, creation and server directed application flow. For the moment it is called it the "Graph and Links" model :) I will try and fit an extended description onto the wiki.
>> 
>