New Proposal Template This page has been created from a template that uses "zones." To proceed: Edit the page Replace sample content within each zone-data tag with your own content Remove this notice Save the page When you are ready for community review, move this page to the Ready for Review section on the edit page. No placeholders allowed! Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.

Zend Framework: Zend_Validate_Composite Component Proposal

Table of Contents

1. Overview

Zend_Validate_Composite is a validator that is able to combine multiple validators on an OR basis.

2. References

none

3. Component Requirements, Constraints, and Acceptance Criteria

Most requirements take the form of "foo will do ...." or "foo will not support ...", although different words and sentence structure might be used. Adding functionality to your proposal is requirements creep (bad), unless listed below. Discuss major changes with your team first, and then open a "feature improvement" issue against this component.

• This component will correctly reads a developers mind for intent and generate the right configuration file.
• The generated config file will not support XML, but will provide an extension point in the API.
• This component will use no more memory than twice the size of all data it contains.
• This component will include a factory method.
• This component will not allow subclassing. (i.e. when reviewed, we expect to see "final" keyword in code)
• This component will only generate data exports strictly complying with RFC 12345.
• This component will validate input data against formats supported by ZF component Foo.
• This component will not save any data using Zend_Cache or the filesystem. All transient data will be saved using Zend_Session.

4. Dependencies on Other Framework Components

• Zend_Validate

5. Theory of Operation

The component is instantiated with a mind-link that ...

6. Milestones / Tasks

• Milestone 1: Finish proposal
• Milestone 2: Community feedback
• Milestone 3: Create working prototype
• Milestone 4: Unit tests exist, work, and are checked into SVN.
• Milestone 5: Initial documentation exists.

7. Class Index

• Zend_Validate_Composite

8. Use Cases

9. Class Skeletons