On Thu, Aug 19, 2010 at 6:15 AM, David Glick <davidgl...@groundwire.org> wrote:
> As an alternative to requiring calling setDefaultRoles/addPermission at
> import time, I suggest that we add an optional roles attribute to the
> <permission> directive.  This would then be used when the directive is
> executed, instead of the current hard-coded Manager setting.  Examples:
> <!-- a new permission with 2 default roles -->
> <permission id="my.NewPermission" title="My new permission"
> roles="Manager SiteAdmin"/>
> <!-- a new permission with Manager as the sole, implicit role
> (backwards-compatible) -->
> <permission id="my.OtherPermission" title="My other permission"/>

Can roles currently contain whitespace? Like "Awesome People"?

If so, we should go for nested nodes:

<permission id="my.NewPermission" title="My new permission">
  <role>Awesome People</role>

I think this matches the style of some of the GenericSetup handlers
which deal with permissions.

I'd not be concerned about overriding the security directive here.
AccessControl's security concept is very different from the one in
zope.security. I don't expect Zope2 to ever be fully compatible with
the current zope.security notion. It's more likely that they will
converge to a third implementation at some point in the future.

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope )

Reply via email to