<?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: Should Robert Parker fire Mark Squires?</title>
	<atom:link href="http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/</link>
	<description>searching for truth in wine</description>
	<lastBuildDate>Wed, 09 Mar 2011 13:35:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: No Respect&#8230; Blogger Ethics&#8230; AGAIN? &#124; Caveman Wines</title>
		<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/#comment-1339</link>
		<dc:creator>No Respect&#8230; Blogger Ethics&#8230; AGAIN? &#124; Caveman Wines</dc:creator>
		<pubDate>Fri, 24 Apr 2009 05:45:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.redwinebuzz.com/winesooth/?p=2401#comment-1339</guid>
		<description>[...]  Arthur Przebinda [...]</description>
		<content:encoded><![CDATA[<p>[...]  Arthur Przebinda [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dylan</title>
		<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/#comment-1313</link>
		<dc:creator>Dylan</dc:creator>
		<pubDate>Sun, 19 Apr 2009 16:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.redwinebuzz.com/winesooth/?p=2401#comment-1313</guid>
		<description>You mentioned how they may be able to brush it off unscathed, but you need to consider this incident as a crack in the foundation. If left unaddressed future instances can shake the bedrock of legitimacy for ERB. I say this because I believe a brand cannot take its user base for granted. Even though one could say these are just a few people complaining about something and aren&#039;t worth the time to address, that exact attitude is casts a shadow onto the brightly lit corner of the content users. Take the hoopla which occurred with &quot;motrin mommies&quot; as an example. It could have been handled slightly differently, but the point remains Motrin made the proper move to validate the dissatisfied voices of their user base. By validating their voice, they validate their relationship. Imagine any relationship you have with a friend that suddenly told you not to talk and your opinion wasn&#039;t valid.

In point, just because your brand moves on run-flat tires, doesn&#039;t mean you shouldn&#039;t address the leak caused by the nail. Otherwise, it will eventually go flat.</description>
		<content:encoded><![CDATA[<p>You mentioned how they may be able to brush it off unscathed, but you need to consider this incident as a crack in the foundation. If left unaddressed future instances can shake the bedrock of legitimacy for ERB. I say this because I believe a brand cannot take its user base for granted. Even though one could say these are just a few people complaining about something and aren&#8217;t worth the time to address, that exact attitude is casts a shadow onto the brightly lit corner of the content users. Take the hoopla which occurred with &#8220;motrin mommies&#8221; as an example. It could have been handled slightly differently, but the point remains Motrin made the proper move to validate the dissatisfied voices of their user base. By validating their voice, they validate their relationship. Imagine any relationship you have with a friend that suddenly told you not to talk and your opinion wasn&#8217;t valid.</p>
<p>In point, just because your brand moves on run-flat tires, doesn&#8217;t mean you shouldn&#8217;t address the leak caused by the nail. Otherwise, it will eventually go flat.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GeneV</title>
		<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/#comment-1306</link>
		<dc:creator>GeneV</dc:creator>
		<pubDate>Fri, 17 Apr 2009 13:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.redwinebuzz.com/winesooth/?p=2401#comment-1306</guid>
		<description>To the extent that the Parker brand has been damaged, Mr. Squires is a very small piece of the problem.  The more basic problem is that, unlike Wine Spectator, the Parker/Wine Advocate brand has always been based on the abilities and integrity of a single person.  For example, shelftalkers touting scores usually refer to the scores as \Parker\ rather than \Wine Advocate.\ Less and less of the content comes from Parker, himself, and that creates a danger for a brand so closely associated with a single name.  Tanzer may eventually suffer the same effects.</description>
		<content:encoded><![CDATA[<p>To the extent that the Parker brand has been damaged, Mr. Squires is a very small piece of the problem.  The more basic problem is that, unlike Wine Spectator, the Parker/Wine Advocate brand has always been based on the abilities and integrity of a single person.  For example, shelftalkers touting scores usually refer to the scores as \Parker\ rather than \Wine Advocate.\ Less and less of the content comes from Parker, himself, and that creates a danger for a brand so closely associated with a single name.  Tanzer may eventually suffer the same effects.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vinogirl</title>
		<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/#comment-1304</link>
		<dc:creator>Vinogirl</dc:creator>
		<pubDate>Thu, 16 Apr 2009 23:59:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.redwinebuzz.com/winesooth/?p=2401#comment-1304</guid>
		<description>Good take on the current Parker melee.</description>
		<content:encoded><![CDATA[<p>Good take on the current Parker melee.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Brennan</title>
		<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/#comment-1301</link>
		<dc:creator>Jim Brennan</dc:creator>
		<pubDate>Thu, 16 Apr 2009 17:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.redwinebuzz.com/winesooth/?p=2401#comment-1301</guid>
		<description>Arthur:

You might explain what \Web 2.0\ concepts imply.  I think many people do not understand the fundamental implications (and why ERP isn&#039;t 2.0, because it seemingly wants to adopt the trappings of Web 2.0 -- technology -- without the truly collaborative and open community underpinnings).</description>
		<content:encoded><![CDATA[<p>Arthur:</p>
<p>You might explain what \Web 2.0\ concepts imply.  I think many people do not understand the fundamental implications (and why ERP isn&#8217;t 2.0, because it seemingly wants to adopt the trappings of Web 2.0 &#8212; technology &#8212; without the truly collaborative and open community underpinnings).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Kelly</title>
		<link>http://www.centralcoastwinereport.com/winesooth/2009/04/16/should-robert-parker-fire-mark-squires/#comment-1299</link>
		<dc:creator>John Kelly</dc:creator>
		<pubDate>Thu, 16 Apr 2009 17:02:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.redwinebuzz.com/winesooth/?p=2401#comment-1299</guid>
		<description>Arthur - I have no dog in this cat fight, but given what most of the web 2.0 world looks like, it strikes me that the relative LACK of spats like this in the new wine media is unusual, and likely to be short-lived. Cheers - John</description>
		<content:encoded><![CDATA[<p>Arthur &#8211; I have no dog in this cat fight, but given what most of the web 2.0 world looks like, it strikes me that the relative LACK of spats like this in the new wine media is unusual, and likely to be short-lived. Cheers &#8211; John</p>
]]></content:encoded>
	</item>
</channel>
</rss>

