Location: http://www.eclipse.org/vex/projectplan.xml
Meta-data Tag: projectplanurl
Raw:

<?xml version='1.0'?>
<plan xmlns="http://www.eclipse.org/project/plan" xmlns:html="http://www.w3.org/1999/xhtml"
      name="Visual Editor for XML" plan-format="1.0">
	<release projectid="mylyn.docx.vex" version="1.1"/>
	<introduction>
		<html:div>The Visual Editor for XML is a set of plug-ins that provide 
		WYSIWYM editing ability for XML files, regardless of the XML 
		involved. Vex uses CSS stylesheets to provide the formatting for the 
		presentation layer. All that is needed is a stylesheet and an 
		appropriate XML file to edit. It hides the XML tags from the users, 
		allows them to have a word processor like experience but store the 
		information in the native XML format.</html:div>
		<html:div/>
		<html:div>Vex is based off of a contribution from the original Vex 
		project created by John Krasnay and hosted at sourceforge.net. In the 
		year 2008 this code was donated to Eclipse and has been an Eclipse 
		Web Tools Incubator component. In 2011, the project moved under the 
		hoods of the Mylyn Docs project.</html:div>
		<html:div/>
	</introduction>
	<release_deliverables/>
	<release_milestones>
		<milestone date="2010-11-18" milestone="1.0.0 M3"/>
		<milestone date="2010-12-13" milestone="1.0.0 M4"/>
		<milestone date="2011-03-15" milestone="1.0.0 M6"/>
		<milestone date="2011-05-03" milestone="1.0.0 M7"/>
		<milestone date="2012-01-04" milestone="1.0.0 M8"/>
		<milestone date="2012-05-29" milestone="1.0.0 M9"/>
		<milestone date="2012-09-09" milestone="1.0.0"/>
		<milestone date="2013-01-29" milestone="1.1.0 M1"/>
		<milestone date="2013-09" milestone="1.1.0"/>
	</release_milestones>
	<target_environments>
		<html:div>
			<html:ul>
				<html:li>Java 5 or later.</html:li>
				<html:li>Eclipse 3.5 or a later release of the Eclipse 3 
				line.</html:li>
				<html:li><html:i>Eclipse 4 already seems to work, will be fully 
				supported in the future.</html:i></html:li>
			</html:ul>
		</html:div>
		<internationalization>
			<html:div>Only English translation files, however all strings are 
			externalized for translation in a future release.</html:div>
		</internationalization>
	</target_environments>
	<compatibility_with_previous_releases>
		<html:div>Versions prior to 1.0.0 M8 used other package names 
		(org.eclipse.wtp.vex.*). Older plug-in descriptors and customizations 
		have to be converted manually to use the new package names 
		(org.eclipse.vex.*).</html:div>
	</compatibility_with_previous_releases>
	<themes_and_priorities>
		<theme name="Full support of the XML infoset">
			<committed>
				<html:ul>
					<html:li>Comments</html:li>
					<html:li>Processing Instructions</html:li>
				</html:ul>
			</committed>
		</theme>
		<theme name="Support for common XML specifications">
			<committed>
				<html:ul>
					<html:li>XML Inclusions</html:li>
				</html:ul>
			</committed>
		</theme>
		<theme name="Support for common XML document types">
			<committed>
				<html:div>Support for</html:div>
				<html:ul>
					<html:li>Docbook</html:li>
					<html:li>DITA</html:li>
					<html:li>XHTML</html:li>
				</html:ul>
			</committed>
			<proposed>
				<html:div>Support for</html:div>
				<html:ul>
					<html:li>PI-Mod</html:li>
				</html:ul>
			</proposed>
		</theme>
		<theme name="API stabilization">
			<committed>
				<html:div>The VexWidget should be usable as standalone widget for 
				structured text (not necessarily XML). An example will be provided, 
				which uses the VexWidget for editing WikiText.</html:div>
			</committed>
		</theme>
		<theme name="Usability">
			<committed>
				<html:div>One of the main &quot;unique selling points&quot; of Vex 
				is to provide a text processor like user interface for XML 
				documents.</html:div>
			</committed>
		</theme>
		<theme name="Building a community"/>
	</themes_and_priorities>
</plan>