How does Sakai differ from Bodington?
There are a number of major differences in this area. Sakai has the concept of site participants, ie, users who have access to a site. Each participant has a roles across a whole site; this differs from Bodington where each ‘item’ has individual access control lists (of users). As an example, consider a Sakai ‘project’ site. This site (by default) has 3 lists of site participants; one list of users with the access role, one of users with the contribute role and another of the maintain role. Loosely speaking, the maintain role manages the site, the contribute role can create material and the access role uses the site. Each of these Roles have a list of functions assigned to them. These functions are actually a list of ‘things that the Role can do’, for example, by default, the ‘access’ role on a project site is able to: read announcements, read content, create and read wiki pages but not delete announcements or content. All this information can be accessed via the permissions link prese
