<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: p2 Metadata Analyzer</title>
	<atom:link href="http://eclipsesource.com/blogs/2009/05/29/p2-metadata-analyzer/feed/" rel="self" type="application/rss+xml" />
	<link>http://eclipsesource.com/blogs/2009/05/29/p2-metadata-analyzer/</link>
	<description>Eclipse Equinox OSGi</description>
	<lastBuildDate>Wed, 16 May 2012 08:22:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: David Carver</title>
		<link>http://eclipsesource.com/blogs/2009/05/29/p2-metadata-analyzer/comment-page-1/#comment-1664</link>
		<dc:creator>David Carver</dc:creator>
		<pubDate>Fri, 29 May 2009 15:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=1634#comment-1664</guid>
		<description>Or you could just use an XML Database...or have the XML persistence validate it&#039;s XML using a schema, since you are writing to Interfaces.</description>
		<content:encoded><![CDATA[<p>Or you could just use an XML Database&#8230;or have the XML persistence validate it&#8217;s XML using a schema, since you are writing to Interfaces.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Bull</title>
		<link>http://eclipsesource.com/blogs/2009/05/29/p2-metadata-analyzer/comment-page-1/#comment-1663</link>
		<dc:creator>Ian Bull</dc:creator>
		<pubDate>Fri, 29 May 2009 15:00:50 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=1634#comment-1663</guid>
		<description>Kim,

The tool will need a few tweaks if we want to incorporate it into the build (command line args to configure what rules to run, etc...), but after RC4 I can do this and help you include it in our build.

David,
While the Galileo repository is XML, there is no requirement that all repositories be persisted as XML.  If we used XML validation then we would limit ourselves to XML based p2 repos. This tool works regardless of the persistence technology. 

(I know of at least two efforts to build a database back p2 repository for example).</description>
		<content:encoded><![CDATA[<p>Kim,</p>
<p>The tool will need a few tweaks if we want to incorporate it into the build (command line args to configure what rules to run, etc&#8230;), but after RC4 I can do this and help you include it in our build.</p>
<p>David,<br />
While the Galileo repository is XML, there is no requirement that all repositories be persisted as XML.  If we used XML validation then we would limit ourselves to XML based p2 repos. This tool works regardless of the persistence technology. </p>
<p>(I know of at least two efforts to build a database back p2 repository for example).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Carver</title>
		<link>http://eclipsesource.com/blogs/2009/05/29/p2-metadata-analyzer/comment-page-1/#comment-1662</link>
		<dc:creator>David Carver</dc:creator>
		<pubDate>Fri, 29 May 2009 13:00:46 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=1634#comment-1662</guid>
		<description>Question since the MetaData we are talking about I believe is in an XML format, how much of the Bad meta data that is generated could have been caught by Validation against a XML Schema, RelaxNG, or DTD grammar?   Enhance the validation process with a SchemaTron schemas that checks particular business rules, and you greatly reduce the chance that the metadata being produced is going to be wrong.</description>
		<content:encoded><![CDATA[<p>Question since the MetaData we are talking about I believe is in an XML format, how much of the Bad meta data that is generated could have been caught by Validation against a XML Schema, RelaxNG, or DTD grammar?   Enhance the validation process with a SchemaTron schemas that checks particular business rules, and you greatly reduce the chance that the metadata being produced is going to be wrong.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kim Moir</title>
		<link>http://eclipsesource.com/blogs/2009/05/29/p2-metadata-analyzer/comment-page-1/#comment-1661</link>
		<dc:creator>Kim Moir</dc:creator>
		<pubDate>Fri, 29 May 2009 12:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://eclipsesource.com/blogs/?p=1634#comment-1661</guid>
		<description>Thanks for writing this tool Ian!  I intend to incorporate it into our build as soon as we ship.</description>
		<content:encoded><![CDATA[<p>Thanks for writing this tool Ian!  I intend to incorporate it into our build as soon as we ship.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

