<?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: Updates to the RPR Content License Agreement</title>
	<atom:link href="http://blog.narrpr.com/product/updates-rpr-content-agreement/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=updates-rpr-content-agreement</link>
	<description></description>
	<lastBuildDate>Thu, 02 Feb 2012 18:23:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Andy</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1151</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 24 Jun 2011 20:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1151</guid>
		<description>&quot;...As for the commenter “Nate Nichols”…this person left 3 comments in a row and used a different name and email for each. The person was in clear violation of our comment policy. Notice all 3 comments have the same IP address, yet have different names and email addresses.

Please understand that impersonating others cannot be tolerated in our comment stream...&quot;

From a technical standpoint, and not related to the individual(s) or specific comments, please consider this.

As I&#039;m sure you&#039;re aware, an IP address can be, and usually is, shared by all computers at a particular location. So, it&#039;s very possible that the posts in question were actually made by different individuals who work at a particular real estate office.

You should always be wary of making assumptions based on an IP address, particularly in situations where your readers are more likely to be working in an office that shares its IP address among all computers.</description>
		<content:encoded><![CDATA[<p>&#8220;&#8230;As for the commenter “Nate Nichols”…this person left 3 comments in a row and used a different name and email for each. The person was in clear violation of our comment policy. Notice all 3 comments have the same IP address, yet have different names and email addresses.</p>
<p>Please understand that impersonating others cannot be tolerated in our comment stream&#8230;&#8221;</p>
<p>From a technical standpoint, and not related to the individual(s) or specific comments, please consider this.</p>
<p>As I&#8217;m sure you&#8217;re aware, an IP address can be, and usually is, shared by all computers at a particular location. So, it&#8217;s very possible that the posts in question were actually made by different individuals who work at a particular real estate office.</p>
<p>You should always be wary of making assumptions based on an IP address, particularly in situations where your readers are more likely to be working in an office that shares its IP address among all computers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reggie</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1150</link>
		<dc:creator>Reggie</dc:creator>
		<pubDate>Fri, 16 Apr 2010 21:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1150</guid>
		<description>VERY IMPORTANT: The number of responses displayed on each post is the number of comments + the trackbacks/pingbacks.

As for the commenter &quot;Nate Nichols&quot;...this person left 3 comments in a row and used a different name and email for each. The person was in clear violation of our comment policy. Notice all &lt;a href=&quot;http://blog.narrpr.com/cs/banned.jpg&quot; / rel=&quot;nofollow&quot;&gt;3 comments &lt;/a&gt; have the same IP address, yet have different names and email addresses.

Please understand that impersonating others cannot be tolerated in our comment stream</description>
		<content:encoded><![CDATA[<p>VERY IMPORTANT: The number of responses displayed on each post is the number of comments + the trackbacks/pingbacks.</p>
<p>As for the commenter &#8220;Nate Nichols&#8221;&#8230;this person left 3 comments in a row and used a different name and email for each. The person was in clear violation of our comment policy. Notice all <a href="http://blog.narrpr.com/cs/banned.jpg" / rel="nofollow">3 comments </a> have the same IP address, yet have different names and email addresses.</p>
<p>Please understand that impersonating others cannot be tolerated in our comment stream</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate Nichols</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1149</link>
		<dc:creator>Nate Nichols</dc:creator>
		<pubDate>Wed, 14 Apr 2010 01:39:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1149</guid>
		<description>Blog says there are (were?) 7 responses, but I only see 5? Is this a glitch, or selective editing by RPR?</description>
		<content:encoded><![CDATA[<p>Blog says there are (were?) 7 responses, but I only see 5? Is this a glitch, or selective editing by RPR?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The passion of the Realtors Property Resource &#124; 1000Watt Consulting</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1148</link>
		<dc:creator>The passion of the Realtors Property Resource &#124; 1000Watt Consulting</dc:creator>
		<pubDate>Thu, 04 Mar 2010 17:39:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1148</guid>
		<description>[...] on stage in San Diego should have raised a red flag. But in any case, by the time the RPR team placed a redline of that license agreement online for all to parse the whole thing reeked of [...]</description>
		<content:encoded><![CDATA[<p>[...] on stage in San Diego should have raised a red flag. But in any case, by the time the RPR team placed a redline of that license agreement online for all to parse the whole thing reeked of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reggie</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1147</link>
		<dc:creator>Reggie</dc:creator>
		<pubDate>Mon, 01 Mar 2010 21:53:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1147</guid>
		<description>Mike - Thanks for your question. We were asked specifically about county assessors in the initial feedback we gathered. But we want to make clear that we would be happy to consider other requests as they come up through our conversations with MLSs.</description>
		<content:encoded><![CDATA[<p>Mike &#8211; Thanks for your question. We were asked specifically about county assessors in the initial feedback we gathered. But we want to make clear that we would be happy to consider other requests as they come up through our conversations with MLSs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MIke Wallender</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1146</link>
		<dc:creator>MIke Wallender</dc:creator>
		<pubDate>Mon, 01 Mar 2010 15:35:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1146</guid>
		<description>In section 1(v), county assessors are excluded form the definition of RPR Customer(s). Why is the exclusion limited to &quot;County&quot; assessors and not inclusive of all governmental assessors, including town assessors?</description>
		<content:encoded><![CDATA[<p>In section 1(v), county assessors are excluded form the definition of RPR Customer(s). Why is the exclusion limited to &#8220;County&#8221; assessors and not inclusive of all governmental assessors, including town assessors?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd A. Shipman</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1145</link>
		<dc:creator>Todd A. Shipman</dc:creator>
		<pubDate>Tue, 23 Feb 2010 11:19:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1145</guid>
		<description>I attended the COVE meeting in Scottsdale last month as a representative of my regional provider, I saw that meeting as a forum for the RPR to learn about deeper concerns and use that information to further build out the RPR business model. I want to congratulate all the members of that forum and the RPR on listening and working together to make the proposed changes. This type of collaboration will go along way to build a better and useful REALTOR tool. The evolution of the industry is about to take a quantum leap. Let us all leverage the opportunity carefully and with consideration for each party.</description>
		<content:encoded><![CDATA[<p>I attended the COVE meeting in Scottsdale last month as a representative of my regional provider, I saw that meeting as a forum for the RPR to learn about deeper concerns and use that information to further build out the RPR business model. I want to congratulate all the members of that forum and the RPR on listening and working together to make the proposed changes. This type of collaboration will go along way to build a better and useful REALTOR tool. The evolution of the industry is about to take a quantum leap. Let us all leverage the opportunity carefully and with consideration for each party.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Missing the Forest for the Trees: the RPR License &#124; Notorious R.O.B. - Conversations on Marketing, Technology, Real Estate</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1144</link>
		<dc:creator>Missing the Forest for the Trees: the RPR License &#124; Notorious R.O.B. - Conversations on Marketing, Technology, Real Estate</dc:creator>
		<pubDate>Tue, 23 Feb 2010 02:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1144</guid>
		<description>[...] folks at RPR while at the same time ending up on a negative note.  On the one hand, RPR&#8217;s posting their Content License Agreement (complete with redlined corrections) is by far the most transparent thing that I&#8217;ve seen a [...]</description>
		<content:encoded><![CDATA[<p>[...] folks at RPR while at the same time ending up on a negative note.  On the one hand, RPR&#8217;s posting their Content License Agreement (complete with redlined corrections) is by far the most transparent thing that I&#8217;ve seen a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Victor Lund</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1143</link>
		<dc:creator>Victor Lund</dc:creator>
		<pubDate>Mon, 22 Feb 2010 21:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1143</guid>
		<description>Great job of filling in many of the gaps that were causing so many questions.

We really appreciate having access to this blog to get the facts about development and refinement of business rules and terms that affect RPR so that everyone can have specific insight into the many complicated issues that surround the product.

Thanks again for keeping us all informed.</description>
		<content:encoded><![CDATA[<p>Great job of filling in many of the gaps that were causing so many questions.</p>
<p>We really appreciate having access to this blog to get the facts about development and refinement of business rules and terms that affect RPR so that everyone can have specific insight into the many complicated issues that surround the product.</p>
<p>Thanks again for keeping us all informed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Larson</title>
		<link>http://blog.narrpr.com/product/updates-rpr-content-agreement/#comment-1142</link>
		<dc:creator>Brian Larson</dc:creator>
		<pubDate>Mon, 22 Feb 2010 21:13:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.narrpr.com/?p=1303#comment-1142</guid>
		<description>Marty,
Thanks for the kind comments! I&#039;m looking forward to reviewing the changes that you&#039;ve implemented.

As for your comment, &quot;I’ll admit to having been naive about the reasons why smart people with opinions would be nervous about expressing them in public&quot; - MLSs and REALTOR assns are pretty political beasts, and speaking your mind can get you into trouble in many different ways, some subtle, some gross. (It&#039;s the tall daisies that get their heads cut off!)

I hope those who wish to speak up publicly will continue, and that those who are &#039;shy&#039; - for whatever reason - will feel comfortable sharing through channels like MLST.

Thanks for considering their comments! (and mine, for what they&#039;re worth)
-Brian</description>
		<content:encoded><![CDATA[<p>Marty,<br />
Thanks for the kind comments! I&#8217;m looking forward to reviewing the changes that you&#8217;ve implemented.</p>
<p>As for your comment, &#8220;I’ll admit to having been naive about the reasons why smart people with opinions would be nervous about expressing them in public&#8221; &#8211; MLSs and REALTOR assns are pretty political beasts, and speaking your mind can get you into trouble in many different ways, some subtle, some gross. (It&#8217;s the tall daisies that get their heads cut off!)</p>
<p>I hope those who wish to speak up publicly will continue, and that those who are &#8216;shy&#8217; &#8211; for whatever reason &#8211; will feel comfortable sharing through channels like MLST.</p>
<p>Thanks for considering their comments! (and mine, for what they&#8217;re worth)<br />
-Brian</p>
]]></content:encoded>
	</item>
</channel>
</rss>

