Category permissions design
Can someone explain the design of the 'horizontal permission' enforced by categorie?
Is this something already functioning, or is it a work-in-progress?
In particular I have some question
- how can the numberous permissions, available for the various object types, be represented by the 4 permissions of categories?
- If there already exists a way of assigning full range of object permissions to objects, wouldn't it be more straightforward for categories to assign/use these?
In the end, on such a development, the most demanding part is not the grouping, but the perm assign/check. You can save more by adopting the actual objectperm assigning/checking and writing a new grouping-indexing feature, than the contrary Ccall it 'Catalogs' or whatever, more elastic than categories, for this attributing to objects?
-categories, at the beginning, were designed as a (quite rigid) way of easying the retrieval of objects, through paths. How can they still be used for that finality for an object, after they become also an indicator of attributes like 'state', 'visibility', 'ownership', 'permissions' etc for that same object? Categorize categories?
- where can I find a discussion held on this subject, to better understand the design?
;){kind=link}
;){kind=link}