<?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: Getting listing data, the follow up, the solution&#8230;</title>
	<atom:link href="http://mostlygeek.com/real-estate/getting-listing-data-the-follow-up-the-solution/feed/" rel="self" type="application/rss+xml" />
	<link>http://mostlygeek.com/real-estate/getting-listing-data-the-follow-up-the-solution/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=rss</link>
	<description>Smothered in Awesome Sauce!</description>
	<lastBuildDate>Tue, 03 Jan 2012 06:09:19 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Rowan Kerr</title>
		<link>http://mostlygeek.com/real-estate/getting-listing-data-the-follow-up-the-solution/comment-page-1/#comment-4</link>
		<dc:creator>Rowan Kerr</dc:creator>
		<pubDate>Mon, 24 Apr 2006 16:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mostlygeek.com/2006/04/22/getting-listing-data-the-follow-up-the-solution/#comment-4</guid>
		<description>Instead of allowing &quot;unbridled data aggregation&quot;, perhaps they would be more comfortable with an access list of people who are allowed to subscribe to the feeds.. by using HTTP Authentication of some sort.

Provide the data in an open format, but restrict access to it, and wrap the process for gaining access in comprehensive licensing agreements. That could be a step in the right direction.</description>
		<content:encoded><![CDATA[<p>Instead of allowing &#8220;unbridled data aggregation&#8221;, perhaps they would be more comfortable with an access list of people who are allowed to subscribe to the feeds.. by using HTTP Authentication of some sort.</p>
<p>Provide the data in an open format, but restrict access to it, and wrap the process for gaining access in comprehensive licensing agreements. That could be a step in the right direction.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

