<?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: Open Standards definition: Is ODF etched on rock? No, not true</title>
	<atom:link href="http://robertogaloppini.net/2008/04/22/open-standards-definition-is-odf-etch-on-rock-no-not-true/feed/" rel="self" type="application/rss+xml" />
	<link>http://robertogaloppini.net/2008/04/22/open-standards-definition-is-odf-etch-on-rock-no-not-true/</link>
	<description>“equally critical of proprietary and open source myths, advocating software choice beyond marketing and romanticism”</description>
	<pubDate>Thu, 09 Feb 2012 19:02:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Boycott Novell &#187; Killing Open Standards Bodies to Tout &#8216;Interoperability&#8217; Meme</title>
		<link>http://robertogaloppini.net/2008/04/22/open-standards-definition-is-odf-etch-on-rock-no-not-true/comment-page-1/#comment-365962</link>
		<dc:creator>Boycott Novell &#187; Killing Open Standards Bodies to Tout &#8216;Interoperability&#8217; Meme</dc:creator>
		<pubDate>Sat, 26 Apr 2008 04:29:29 +0000</pubDate>
		<guid isPermaLink="false">http://robertogaloppini.net/2008/04/22/open-standards-definition-is-odf-etch-on-rock-no-not-true/#comment-365962</guid>
		<description>[...] a practical example from several days ago, consider this story about the way things should be done (openly, not by having Novell and Microsoft swap code with NDAs).  Being OOo available in source [...]</description>
		<content:encoded><![CDATA[<p>[...] a practical example from several days ago, consider this story about the way things should be done (openly, not by having Novell and Microsoft swap code with NDAs).  Being OOo available in source [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

