Changes between Version 3 and Version 4 of BASE_SECURITY_MODEL_PERMISSIONS_R0

Timestamp:

02/03/09 08:46:25 (16 years ago)

Author:

sriggins

Comment:

--

BASE_SECURITY_MODEL_PERMISSIONS_R0

@@ -6 +6 @@
 
 == Overview ==
-^(Provide a brief overview of the whole task in its first revision. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
+
+Implement permissions as a property of an object.  The permissions combine a user, group or everyone.  Permissions are a list, which allows for multiple permissions on an object.  
+
+Permissions should be more access control list oriented vs unix permissions styled.    Each permission can be additive or subtractive.  For example, a resource can have a modify permission for Group "Art Department" but User "Fred" who is in the group might have modify permission removed.    Therefore individual user permissions must usurp any group permissions given on a particular object.
+
+Permissions on an object include:
+
+ * Read - Author can use the resource in a book
+ * Write - Can modify permissions
+ * Modify - Author can scale, rotate or apply other transformations to the resource
+ * Export - Resource can be exported (copied to the clipboard, etc)
 
 == Task requirements ==
-^(List the necessary requirements that the task must fulfill.)^
 
+  * Implement permissions as a property on resources
+  * Add a permissions panel to the resources flap that allows the setting of permissions
+  * Document how code checks for permissions on an object
+  
 == Task result ==
-^(List the end product of the task (for example "Source code", "Wiki page", etc.))^
+
+ The result of this task is code
 
 == Implementation idea ==
-^(Provide some rough implementation idea(s).)^
+
+ * Remember that a user cannot change permissions if they don't have write permission
+ * see the Own PRO_LIB property
 
 == Related ==
@@ -26 +42 @@
 
 == How to demo ==
-^(Provide instructions for demonstration of the task.)^
+
+If this task ends up having UI (I am not sure as of this writing) then you can demo the UI for permissions, otherwise share the documentation.
 
 = Design =