- Venice identifiers are used for user IDs, SIG aliases, and conference aliases (and maybe other unique + Venice identifiers are used for user IDs, community aliases, and conference aliases (and maybe other unique identifiers in the future). A valid Venice ID consists of characters from the following character set only:
+ than a community, which in turn would have a higher scope value than 0 (the "global" scope).
The values 65000-65535 are not used, except that the value 65500 is defined as "no access" (something not even the global system administrator can touch). Neither are the values 32000-32999, except that the value 32500 is defined as "unrestricted user" (lying above the low bands of all scopes but below @@ -122,34 +122,34 @@
- SIGs use the scope level 3; the following values are defined within that scope: + Communities use the scope level 3; the following values are defined within that scope:
- Within SIGs, conferences use scope 6; the following values are defined within that scope: + Within communities, conferences use scope 6; the following values are defined within that scope:
- Each user has a "base access" level, within scope 0, that is stored in the "users" table. Each SIG + Each user has a "base access" level, within scope 0, that is stored in the "users" table. Each community has four defined access levels associated with it:
- The "sigmember" table maps UIDs to SIGIDs, adding a "granted level" field that specifies a given user's - access level within the SIG itself. (If a user already has a higher access level than the "granted" - access level, as in the case of the global sysadmin, the higher level takes precedence.) Note that - this level grant is within the context of that SIG only, and does not affect access privileges - to any other SIG.
+ The "sigmember" table maps UIDs to community IDs, adding a "granted level" field that specifies a given + user's access level within the community itself. (If a user already has a higher access level than the + "granted" access level, as in the case of the global sysadmin, the higher level takes precedence.) Note + that this level grant is within the context of that community only, and does not affect access + privileges to any other community.
Each conference has seven defined access levels associated with it:
- As with SIGs, there is a "confmember" table that maps UIDs to CONFIDs, adding a "granted level" field - that grants additional access privileges. (There is also a field in the table that maps conferences - into SIGs that allows a SIG to grant its users additional privileges within a conference. Normally, - this field is 0, and so it "drops out" of the calculation of access levels.) Note that, if a user has - no membership entry for a conference, the entry for the conference's enclosing SIG takes precedence, - or the base level if there is no entry in any enclosing SIG. Also note that a grant of level for a - conference or SIG only applies with respect to that conference or SIG, not any other.
+ As with communities, there is a "confmember" table that maps UIDs to CONFIDs, adding a "granted level" + field that grants additional access privileges. (There is also a field in the table that maps + conferences into communities that allows a community to grant its users additional privileges within a + conference. Normally, this field is 0, and so it "drops out" of the calculation of access levels.) Note + that, if a user has no membership entry for a conference, the entry for the conference's enclosing + community takes precedence, or the base level if there is no entry in any enclosing community. Also + note that a grant of level for a conference or community only applies with respect to that + conference or community, not any other.
Additional scopes and levels will be defined for additional objects as they are added to Venice.