<?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: GCDS summary</title>
	<atom:link href="http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/</link>
	<description>From lost to the river</description>
	<lastBuildDate>Sun, 08 Jan 2012 15:47:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: amondo</title>
		<link>http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/comment-page-1/#comment-922</link>
		<dc:creator>amondo</dc:creator>
		<pubDate>Thu, 10 Sep 2009 08:04:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/?p=433#comment-922</guid>
		<description>Midgard2 is the future

http://bergie.iki.fi/blog/why_you_should_use_a_content_repository_for_your_application/</description>
		<content:encoded><![CDATA[<p>Midgard2 is the future</p>
<p><a href="http://bergie.iki.fi/blog/why_you_should_use_a_content_repository_for_your_application/" rel="nofollow">http://bergie.iki.fi/blog/why_you_should_use_a_content_repository_for_your_application/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan</title>
		<link>http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/comment-page-1/#comment-921</link>
		<dc:creator>Jan</dc:creator>
		<pubDate>Sun, 19 Jul 2009 18:54:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/?p=433#comment-921</guid>
		<description>@pvanhoof CouchDB can store these references. it just can&#039;t get you more then one hop of a target doc to a referenced doc in one query by default. *by default* is the key here. Adding a graph-aware indexer to CouchDB is trivial. Please do get in touch if you want to help out with that or like more information.</description>
		<content:encoded><![CDATA[<p>@pvanhoof CouchDB can store these references. it just can&#8217;t get you more then one hop of a target doc to a referenced doc in one query by default. *by default* is the key here. Adding a graph-aware indexer to CouchDB is trivial. Please do get in touch if you want to help out with that or like more information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: antimonio</title>
		<link>http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/comment-page-1/#comment-920</link>
		<dc:creator>antimonio</dc:creator>
		<pubDate>Fri, 17 Jul 2009 23:19:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/?p=433#comment-920</guid>
		<description>Totally agree with what you say about RMS: and that each fucking person in the community/planet is blogging about it, is completely a waste of time (of him and of the readers).</description>
		<content:encoded><![CDATA[<p>Totally agree with what you say about RMS: and that each fucking person in the community/planet is blogging about it, is completely a waste of time (of him and of the readers).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/comment-page-1/#comment-918</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 16 Jul 2009 18:34:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/?p=433#comment-918</guid>
		<description>No no no, please don&#039;t cut down on the talks. Even though I do follow GNOME development to some extent (desktop-devel list and other lists), there&#039;s still plenty of stuff I&#039;m missing or only following lazily. The talks form the cornerstone of guadec to me, they&#039;re a good opportunity to catch up with what&#039;s going on elsewhere in GNOME (and beyond). Having said that, I found the scheduling a bit unfortunate as well. I think BoFs and talks should be interleaved with the talks rather than both being clustered in the way they were in Gran Canaria. I don&#039;t think there&#039;s a problem with having more &#039;core days&#039; or having talks scheduled outside of the core days.</description>
		<content:encoded><![CDATA[<p>No no no, please don&#8217;t cut down on the talks. Even though I do follow GNOME development to some extent (desktop-devel list and other lists), there&#8217;s still plenty of stuff I&#8217;m missing or only following lazily. The talks form the cornerstone of guadec to me, they&#8217;re a good opportunity to catch up with what&#8217;s going on elsewhere in GNOME (and beyond). Having said that, I found the scheduling a bit unfortunate as well. I think BoFs and talks should be interleaved with the talks rather than both being clustered in the way they were in Gran Canaria. I don&#8217;t think there&#8217;s a problem with having more &#8216;core days&#8217; or having talks scheduled outside of the core days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pvanhoof</title>
		<link>http://blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/comment-page-1/#comment-917</link>
		<dc:creator>pvanhoof</dc:creator>
		<pubDate>Thu, 16 Jul 2009 17:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/rodrigo/?p=433#comment-917</guid>
		<description>CouchDB can&#039;t store references as object of a triple. So regretfully it&#039;s not very useful for storing Tracker&#039;s triples in. Having references is essential to build a graph. Having rich graphs is essential for Nepomuk as ontology. Nepomuk is what all desktop metadata projects are agreeing on. So it&#039;s kinda important...

CouchDB could, however, synchronize itself with Tracker&#039;s data, of course.</description>
		<content:encoded><![CDATA[<p>CouchDB can&#8217;t store references as object of a triple. So regretfully it&#8217;s not very useful for storing Tracker&#8217;s triples in. Having references is essential to build a graph. Having rich graphs is essential for Nepomuk as ontology. Nepomuk is what all desktop metadata projects are agreeing on. So it&#8217;s kinda important&#8230;</p>
<p>CouchDB could, however, synchronize itself with Tracker&#8217;s data, of course.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/rodrigo/2009/07/16/gcds-summary/feed/ ) in 1.15142 seconds, on Feb 10th, 2012 at 5:52 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 10th, 2012 at 6:52 am UTC -->
