Index: openacs-4/packages/dotlrn/www/doc/permission-api.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn/www/doc/permission-api.adp,v
diff -u -r1.3 -r1.3.2.1
--- openacs-4/packages/dotlrn/www/doc/permission-api.adp 3 Jul 2015 10:43:59 -0000 1.3
+++ openacs-4/packages/dotlrn/www/doc/permission-api.adp 22 Jun 2016 08:25:00 -0000 1.3.2.1
@@ -23,7 +23,7 @@
For this to work, the actual privileges used throughout dotLRN and all
-of its modules must be consistent. Since permissions follow an
+of its modules must be consistent. Since permissions follow an
inheritance path, we must make sure everything bootstraps off the
basic read, write, create, delete, admin privileges.
@@ -32,19 +32,19 @@
To better explain the situation, we want the following to happen:
- Hal is a member of "Intro to Computer Science Spring 2002" group, with relationship
-type dotlrn_instructor_rel to that group.
+type dotlrn_instructor_rel to that group.
- An FAQ about the Computer Science Program is created for "Intro
-to Computer Science Spring 2002", with context_id pointing to
+to Computer Science Spring 2002", with context_id pointing to
the course.
- A relational segment "Intro to CS Spring 2002 Instructors" is
created on the "Intro to CS Spring 2002" group and
-dotlrn_instructor_rel relationship type.
-
- The privilege faq_admin exists, inheriting from
-the core OpenACS admin privilege.
+dotlrn_instructor_rel relationship type.
+
- The privilege faq_admin exists, inheriting from
+the core OpenACS admin privilege.
- A permission is granted: "Intro to CS Spring 2002 Instructors"
-are given the admin privilege on the course "Intro to
+are given the admin privilege on the course "Intro to
CS Spring 2002".
-
- Thus, automatically, Hal has the right to admin the FAQ,
+
- Thus, automatically, Hal has the right to admin the FAQ,
because the admin privilege translates to the faq_admin privilege by
inheritance, Hal is part of the relational segment in question, and
the FAQ in question has a context_id pointing to the course. It's BEAUTIFUL!
@@ -54,36 +54,36 @@
These are fairly straight-forward:
-- dotlrn::user_add user_id
-
- dotlrn::user_remove user_id
+
- dotlrn::user_add user_id
+
- dotlrn::user_remove user_id
-
- dotlrn::guest_add community_id user_id
-
- dotlrn::guest_remove community_id user_id
+
- dotlrn::guest_add community_id user_id
+
- dotlrn::guest_remove community_id user_id
Access Control API
-- dotlrn::user_can_browse_p ?user_id?
-
- dotlrn::require_user_browse ?user_id?
+
- dotlrn::user_can_browse_p ?user_id?
+
- dotlrn::require_user_browse ?user_id?
-
- dotlrn::user_can_read_sensitive_data ?user_id?
-
- dotlrn::require_user_read_sensitive_data ?user_id?
+
- dotlrn::user_can_read_sensitive_data ?user_id?
+
- dotlrn::require_user_read_sensitive_data ?user_id?
-
- dotlrn::user_can_read_community_type_p community_type ?user_id?
-
- dotlrn::require_user_read_community_type community_type
-?user_id?
+
- dotlrn::user_can_read_community_type_p community_type ?user_id?
+
- dotlrn::require_user_read_community_type community_type
+?user_id?
-
- dotlrn::user_can_read_community_p community_id ?user_id?
-
- dotlrn::require_user_read_community community_id
-?user_id?
+
- dotlrn::user_can_read_community_p community_id ?user_id?
+
- dotlrn::require_user_read_community community_id
+?user_id?
-
- dotlrn::user_community_member_p community_id ?user_id?
-
- dotlrn::require_user_community_member community_id
-?user_id?
+
- dotlrn::user_community_member_p community_id ?user_id?
+
- dotlrn::require_user_community_member community_id
+?user_id?
-
- dotlrn::user_can_admin_community_p community_id
-?user_id?
-
- dotlrn::require_user_admin_community community_id ?user_id?
+
- dotlrn::user_can_admin_community_p community_id
+?user_id?
+
- dotlrn::require_user_admin_community community_id ?user_id?