Approach to spec changes for resolution of ISSUE-25 Weak aggregation and strong composition in containers

I have ACTION-27 to make the necessary editorial changes to address the 
resolution/closing of ISSUE-25. [1]

It was proposed at the 12-Nov meeting that I outline the changes I plan to 
make to the spec as a result of the resolution (repeating here for ease):

        RESOLVED: Make the containers in the spec be about Strong 
Composition, then accept proposals for how to do weak aggregation. And 
separate proposals for paging, etc.

The basis for the changes are quite simple, which then hit a few other 
sections. 
Namely, it will focus on the key constraints:
- Client adding resource to a container - can only be accomplished by 
POSTing to container to create the resource, which then gets added to the 
container
- Client removing resource from a container - client issues a DELETE on 
resource, which removes the resource from the server and its membership 
from the container

Some additional constraints of this include:
- Client removing container - server must delete all resources prior to 
deleting the container

I will continue with making the editorial changes in support of the above 
resolution.

Additionally some use cases have already be proposed to handle other 
scenarios such as moving resource between containers [2] and other weak 
aggregation motivated cases [3]

[1] - http://www.w3.org/2012/ldp/track/issues/25
[2] - http://www.w3.org/2012/ldp/track/issues/30
[3] - http://www.w3.org/2012/ldp/track/issues/34

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> 
http://open-services.net

Received on Monday, 19 November 2012 13:40:46 UTC