<?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: Credit Industry needs new integration paradigm&#8230; think VRM and Personal Datastores</title>
	<atom:link href="http://blog.joeandrieu.com/2007/10/06/credit-industry-needs-new-integration-paradigm-think-vrm-and-personal-datastores/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.joeandrieu.com/2007/10/06/credit-industry-needs-new-integration-paradigm-think-vrm-and-personal-datastores/</link>
	<description>My personal space</description>
	<lastBuildDate>Tue, 16 Mar 2010 20:51:45 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dmh</title>
		<link>http://blog.joeandrieu.com/2007/10/06/credit-industry-needs-new-integration-paradigm-think-vrm-and-personal-datastores/comment-page-1/#comment-1375</link>
		<dc:creator>dmh</dc:creator>
		<pubDate>Sat, 06 Oct 2007 23:47:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.joeandrieu.com/2007/10/06/credit-industry-needs-new-integration-paradigm-think-vrm-and-personal-datastores/#comment-1375</guid>
		<description>Another great use case.

It occurs to me that this model works best (or maybe only works at all) where the data store&#039;s view of the world is relatively small.  For example, there are lots and lots of health care providers or retailers out there, but I only deal with a fairly small number of them.  That means I can reasonably keep track of who has access to the sensitive parts of my data store

Some parts, e.g., the blog-like parts, might be open to the public at large.  That&#039;s also easy to track: &quot;Anybody and everybody&quot; is basically one list item.  Or &quot;people in my friends list&quot; is also one item.  Things get dicey when I have to keep track of, say, dozens or more items on the access list.  Defining groups definitely helps, as long as I don&#039;t spend all my time managing the groups ...</description>
		<content:encoded><![CDATA[<p>Another great use case.</p>
<p>It occurs to me that this model works best (or maybe only works at all) where the data store&#8217;s view of the world is relatively small.  For example, there are lots and lots of health care providers or retailers out there, but I only deal with a fairly small number of them.  That means I can reasonably keep track of who has access to the sensitive parts of my data store</p>
<p>Some parts, e.g., the blog-like parts, might be open to the public at large.  That&#8217;s also easy to track: &#8220;Anybody and everybody&#8221; is basically one list item.  Or &#8220;people in my friends list&#8221; is also one item.  Things get dicey when I have to keep track of, say, dozens or more items on the access list.  Defining groups definitely helps, as long as I don&#8217;t spend all my time managing the groups &#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
