IIUC, the (new) 'Editor' role is designed to be an intermediary btw 'manage' and 'view' permissions. In particular, it was intended to allow for collaborative editing of document contents without surrendering the privilege of document deletion.
Also IIUC, we really are just talking about Sakai documents and not other forms of content, right? My understanding is that content collections are not implemented with collection items as children of a collection node. Also that uploaded files and external links do not have children (is this true? And will it still be true when annotations are implemented?) Pages of a Sakai doc, or widgets on a page, then, would be the most common examples of child nodes. On those assumptions, I would answer ... On Fri, Apr 20, 2012 at 7:24 AM, Branden Visser <[email protected]> wrote: > a) If a user has "WRITE" permission on a content node, should they > always be able to delete their children? Yes. It's not inconceivable that some people would make use of more fine-grained editor restrictions, but this extra complexity would be of marginal benefit, and the design doesn't anticipate it. > c) (new) Should editors of a Sakai Document even be able to delete > pages within the document? Yes. Again, I can imagine scenarios where some people would like to set different permissions for different pages in a doc, but in such cases a separate doc should be a fine solution, and the extra complexity of page-level permissions is not worth the cost, as far as I understand the design thinking. ~Clay _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
