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.

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

Zend Framework: Zend_Validate_Phone Component Proposal

Table of Contents

1. Overview

Zend_Validate_Phone is a validator which checks if a given input conforms a expected format for a phone number.

2. References

• Wikipedia - Telephone numbers
• Wikipedia - E.123
• ITU-T

3. Component Requirements, Constraints, and Acceptance Criteria

• This component will check if a string conforms a expected phone number format
• This component will not change the format, only check
• This component will accept national and international formats
• This component will also allow to check if a given number conforms a given country or multiple countries
• This component will not check if a given number does exist

4. Dependencies on Other Framework Components

• Zend_Validate_Exception
• Zend_Validate_Abstract

5. Theory of Operation

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

6. Milestones / Tasks

Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.

• Milestone 1: design notes will be published here
• Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
• Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
• Milestone 4: Unit tests exist, work, and are checked into SVN.
• Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

• Milestone #: [DONE] Unit tests ...

7. Class Index

• Zend_Magic_Exception
• Zend_Magic (factory class)
• Zend_Magic_MindProbe
• Zend_Magic_MindProbe_Intent
• Zend_Magic_Action
• Zend_Magic_CodeGen

8. Use Cases

... (see good use cases book)

9. Class Skeletons