<?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: My kind of application needs a database</title>
	<atom:link href="http://mesquilla.com/2009/01/24/my-kind-of-application-needs-a-database/feed/" rel="self" type="application/rss+xml" />
	<link>http://mesquilla.com/2009/01/24/my-kind-of-application-needs-a-database/</link>
	<description>Messaging with Mozilla by rkent</description>
	<lastBuildDate>Sun, 18 Jul 2010 18:30:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: rkent</title>
		<link>http://mesquilla.com/2009/01/24/my-kind-of-application-needs-a-database/comment-page-1/#comment-59</link>
		<dc:creator>rkent</dc:creator>
		<pubDate>Wed, 01 Apr 2009 20:57:57 +0000</pubDate>
		<guid isPermaLink="false">http://mesquilla.com/?p=160#comment-59</guid>
		<description>RDF is certainly the technology that tries to tie together multiple web datastores. But is has become &quot;uncool&quot; for a variety of reasons. I&#039;ve seriously looked though at porting the Redland RDF library into the Mozilla environment to give me a more robust software subsystem to play with that.

But I picture the war against data fragmentation to be one of integrating many sources into a common framework, such as the Mozilla mailnews (Thunderbird) platform. As for data storage, though I haven&#039;t tried it yet, generally I picture using a local SQL-based engine (such as the SQLITE-based gloda in Thunderbird) to provide the integration capability, with the canonical storages all being simple attribute/value pairs (or triples) stored in a variety of different formats and locations.

But I have not actually faced the real issues yet.</description>
		<content:encoded><![CDATA[<p>RDF is certainly the technology that tries to tie together multiple web datastores. But is has become &#8220;uncool&#8221; for a variety of reasons. I&#8217;ve seriously looked though at porting the Redland RDF library into the Mozilla environment to give me a more robust software subsystem to play with that.</p>
<p>But I picture the war against data fragmentation to be one of integrating many sources into a common framework, such as the Mozilla mailnews (Thunderbird) platform. As for data storage, though I haven&#8217;t tried it yet, generally I picture using a local SQL-based engine (such as the SQLITE-based gloda in Thunderbird) to provide the integration capability, with the canonical storages all being simple attribute/value pairs (or triples) stored in a variety of different formats and locations.</p>
<p>But I have not actually faced the real issues yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Walker</title>
		<link>http://mesquilla.com/2009/01/24/my-kind-of-application-needs-a-database/comment-page-1/#comment-58</link>
		<dc:creator>Kris Walker</dc:creator>
		<pubDate>Wed, 01 Apr 2009 19:46:03 +0000</pubDate>
		<guid isPermaLink="false">http://mesquilla.com/?p=160#comment-58</guid>
		<description>I&#039;d be really interested in hearing some ideas on a datastore that overcomes data fragmentation.

First, how do we combine data from different domains, into one domain?  And then how to we modify it, and then tease it back apart to send it off to the remote service it came from (assuming that many are push/pull services, and not just consuming services).  I think it&#039;s worth taking a look at web hooks for some ideas.

Second, I&#039;ve sea-sawed back and forth on the implementation between a description model, like RDF, data entities (like OO classes or constructors), and an object-relational mapping scheme.  I really like RDF, but I&#039;ve never seen it implemented in a reasonable way.  On the other hand, relational databases seem to be overstaying their welcome in the age of fragmentation.

However it is implemented, I think the data models must be extensible and dynamic for this to work.</description>
		<content:encoded><![CDATA[<p>I&#8217;d be really interested in hearing some ideas on a datastore that overcomes data fragmentation.</p>
<p>First, how do we combine data from different domains, into one domain?  And then how to we modify it, and then tease it back apart to send it off to the remote service it came from (assuming that many are push/pull services, and not just consuming services).  I think it&#8217;s worth taking a look at web hooks for some ideas.</p>
<p>Second, I&#8217;ve sea-sawed back and forth on the implementation between a description model, like RDF, data entities (like OO classes or constructors), and an object-relational mapping scheme.  I really like RDF, but I&#8217;ve never seen it implemented in a reasonable way.  On the other hand, relational databases seem to be overstaying their welcome in the age of fragmentation.</p>
<p>However it is implemented, I think the data models must be extensible and dynamic for this to work.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
