Symphony extension meta XML

extension.about.xml

<?xml version="1.0" encoding="UTF-8" ?>
<metadata version="1.0">
	<extension id="search_index">
	
		<!-- string, required -->
		<name>Search Index</name>

		<!-- string, required (@lang optional) -->
		<description lang="en">Index text content of entries for efficient full-text search.</description>

		<!-- string, required (must be Github for clever API things to happen) -->
		<url type="repo">https://github.com/nickdunn/search_index</repository>

		<!-- string, optional (@type=repo|homepage|wiki|other?) -->
		<url type="homepage">http://symphony-cms.com/downloads/extensions/search_index</repository>
	
		<!-- list, optional (Symphony to define suggested vocabulary, suggest leaving this out initially?) -->
		<types>
			<type>Field</type>
			<type>Interface</type>
			<type>Workflow</type>
		</types>
	
		<!-- list, required -->
		<authors>
			<author>
				<!-- string, required (@github, @symphony, @twitter optional) -->
				<name github="nickdunn" symphony="nickdunn" twitter="nickdunn">Nick Dunn</name>
				<!-- string, optional -->
				<email>nick@nick-dunn.co.uk</email>
				<!-- string, optional -->
				<website>http://nick-dunn.co.uk</website>
			</author>
		</authors>
	
		<!-- list, optional -->
		<dependencies>
			<dependency version="0.5">stage</dependency>
		</dependencies>

		<!-- list, required at least one. Largest version number is assumed latest -->
		<releases>
			<release version="0.3" date="2011-03-03" min="2.3" max="2.4"/>
			<release version="0.2" date="2011-02-02" min="2.2.2">
				<![CDATA[
					Your release notes go in here. They will be parsed as Markdown.
					* So you can have a list
					* Or `code` if you like
				]]>
			</release>
			<release version="0.1" date="2011-01-01" min="2.0"/>
		</releases>	
	
	</extension>
</metadata>