<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments for Knowledge Hives</title>
	<atom:link href="http://blog.knowledgehives.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.knowledgehives.com</link>
	<description>Society+Semantics = Wisdom</description>
	<lastBuildDate>Thu, 27 Aug 2009 14:22:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Linking Public Vocabularies &#8211; openvocabulary.info by skruk (skruk)</title>
		<link>http://blog.knowledgehives.com/2009/08/linking-public-vocabularies-openvocabularyinfo/comment-page-1/#comment-18</link>
		<dc:creator>skruk (skruk)</dc:creator>
		<pubDate>Thu, 27 Aug 2009 14:22:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.knowledgehives.com/2009/08/linking-public-vocabularies-openvocabularyinfo/#comment-18</guid>
		<description>RT &lt;a rel=&quot;nofollow&quot; href=&quot;http://twitter.com/knowledgehives&quot;&gt;@knowledgehives&lt;/a&gt;: (...) we have just started a new service called Open Vocabulary - see more at http://bit.ly/e516E</description>
		<content:encoded><![CDATA[<p>RT <a rel="nofollow" href="http://twitter.com/knowledgehives">@knowledgehives</a>: (&#8230;) we have just started a new service called Open Vocabulary &#8211; see more at <a href="http://bit.ly/e516E" rel="nofollow">http://bit.ly/e516E</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Linking Public Vocabularies &#8211; openvocabulary.info by knowledgehives (Knowledge Hives)</title>
		<link>http://blog.knowledgehives.com/2009/08/linking-public-vocabularies-openvocabularyinfo/comment-page-1/#comment-19</link>
		<dc:creator>knowledgehives (Knowledge Hives)</dc:creator>
		<pubDate>Thu, 27 Aug 2009 14:22:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.knowledgehives.com/2009/08/linking-public-vocabularies-openvocabularyinfo/#comment-19</guid>
		<description>Unless you missed our announcement last night: we have just started a new service called Open Vocabulary - see more at http://bit.ly/e516E</description>
		<content:encoded><![CDATA[<p>Unless you missed our announcement last night: we have just started a new service called Open Vocabulary &#8211; see more at <a href="http://bit.ly/e516E" rel="nofollow">http://bit.ly/e516E</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Knowledge Hives goes Open Source by Knowledge Hives goes Open Source « News : India-Developers.com</title>
		<link>http://blog.knowledgehives.com/2009/05/knowledge-hives-goes-open-source/comment-page-1/#comment-3</link>
		<dc:creator>Knowledge Hives goes Open Source « News : India-Developers.com</dc:creator>
		<pubDate>Mon, 11 May 2009 08:47:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.knowledgehives.com/?p=6#comment-3</guid>
		<description>[...] Here is the original post: Knowledge Hives goes Open Source [...]
</description>
		<content:encoded><![CDATA[<p>[...] Here is the original post: Knowledge Hives goes Open Source [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Knowledge Hives goes Open Source by Twitted by knowledgehives</title>
		<link>http://blog.knowledgehives.com/2009/05/knowledge-hives-goes-open-source/comment-page-1/#comment-2</link>
		<dc:creator>Twitted by knowledgehives</dc:creator>
		<pubDate>Sun, 10 May 2009 22:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.knowledgehives.com/?p=6#comment-2</guid>
		<description>[...] This post was Twitted by knowledgehives - Real-url.org [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was Twitted by knowledgehives &#8211; Real-url.org [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

