<ac:macro ac:name="info"><ac:parameter ac:name="title">New Proposal Template</ac:parameter><ac:rich-text-body>
<p>This page has been created from a template that uses "zones." To proceed:</p>

<ol>
<li>Edit the page</li>
<li>Replace sample content within each zone-data tag with your own content</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for community review, move this page to the <ac:link><ri:page ri:content-title="Ready for Review" /></ac:link> section on the edit page.</li>
</ol>

<ac:macro ac:name="note"><ac:parameter ac:name="title">No placeholders allowed!</ac:parameter><ac:rich-text-body>
<p>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.</p></ac:rich-text-body></ac:macro></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_Kml Component Proposal

Table of Contents

1. Overview

Zend_KML is a component to model Keyhole Markup Language (KML) for Geographic XML data.

2. References

• KML Wikipedia Entry
• Google KML Documentation

3. Component Requirements, Constraints, and Acceptance Criteria

• This component will emit KML data from a programmatic interface.
• This component will initially contain support for placemarks.
• This component will support points, polygons, lines, etc.
• This component will allow for some styling (color, fill, outline)
• This component will assume a lat/long interface. (WGS84)

4. Dependencies on Other Framework Components

• Zend_Exception

5. Theory of Operation

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_Kml
• Zend_Kml_Link
• Zend_Kml_Link_Icon
• Zend_Kml_Feature [abstract]
• Zend_Kml_Feature_Placemark
• Zend_Kml_Feature_Overlay [abstract]
• Zend_Kml_Feature_Overlay_GroundOverlay
• Zend_Kml_Geometry [abstract]
• Zend_Kml_Geometry_Point
• Zend_Kml_Geometry_LineString
• Zend_Kml_Geometry_LinearRing
• Zend_Kml_Geometry_Polygon
• Zend_Kml_Geometry_MultiGeometry
• Zend_Kml_Style [abstract]
• Zend_Kml_Style_ListStyle
• Zend_Kml_Style_BalloonStyle
• Zend_Kml_Style_ColorStyle [abstract]
• Zend_Kml_Style_ColorStyle_LineStyle
• Zend_Kml_Style_ColorStyle_PolyStyle
• Zend_Kml_Style_ColorStyle_IconStyle
• Zend_Kml_Style_ColorStyle_LabelStyle

8. Use Cases

9. Class Skeletons