<ac:macro ac:name="note"><ac:parameter ac:name="title">Under Construction</ac:parameter><ac:rich-text-body>
<p>This proposal is under construction and is not ready for review.</p></ac:rich-text-body></ac:macro>

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Acl Component Proposal

Table of Contents

1. Overview

Improvement of Zend_Acl, so it will become multi-model (not limited to RBAC model as right now).

2. References

• ACL Wikipedia Entry

3. Component Requirements, Constraints, and Acceptance Criteria

Not defined yet.

4. Dependencies on Other Framework Components

No dependecies.

5. Theory of Operation

I propose not to limit ACL to the only RBAC model. There are a lot of models. And all of them are just a bases, so in certain project developer creating a new model based on ideas of well-known models.
I agree that RBAC is very good model and t can be used almost in all cases, but don't forget about almost. So for example right now a I need an ACL model based on ideas of bit field. Of course it can be done with RBAC, but with additional classes and functions.

6. Milestones / Tasks

Not ready yet.

7. Class Index

• Zend_Acl

8. Use Cases

9. Class Skeletons