<?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: Mediating on YouTube</title>
	<atom:link href="http://mediationchannel.com/2009/02/18/mediating-on-youtube/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediationchannel.com/2009/02/18/mediating-on-youtube/</link>
	<description>News and ideas about mediation, negotiation, conflict resolution, and law</description>
	<lastBuildDate>Fri, 09 Jul 2010 15:12:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Diane Levin</title>
		<link>http://mediationchannel.com/2009/02/18/mediating-on-youtube/comment-page-1/#comment-595</link>
		<dc:creator>Diane Levin</dc:creator>
		<pubDate>Tue, 24 Feb 2009 13:53:43 +0000</pubDate>
		<guid isPermaLink="false">http://mediationchannel.com/?p=1504#comment-595</guid>
		<description>Hi, Marvin,

I got the impression that this was a real mediation but substantially edited down for public consumption (and just long enough not to tax the public attention span). If you watch closely, you can see the cuts. (Was it me, or did the dog owner seem not altogether thrilled with the outcome of the mediation?)

I&#039;m with you on sharing war stories. It&#039;s all too easy for clients to see themselves. I know of one case where a mediation blogger got busted when their client happened to read a post describing a dispute the client was involved in. It&#039;s important to remember that clients surf the web just like the rest of us. I imagine that in the case of this video, the clients must have signed all kinds of waivers and releases.

Thanks for commenting.</description>
		<content:encoded><![CDATA[<p>Hi, Marvin,</p>
<p>I got the impression that this was a real mediation but substantially edited down for public consumption (and just long enough not to tax the public attention span). If you watch closely, you can see the cuts. (Was it me, or did the dog owner seem not altogether thrilled with the outcome of the mediation?)</p>
<p>I&#8217;m with you on sharing war stories. It&#8217;s all too easy for clients to see themselves. I know of one case where a mediation blogger got busted when their client happened to read a post describing a dispute the client was involved in. It&#8217;s important to remember that clients surf the web just like the rest of us. I imagine that in the case of this video, the clients must have signed all kinds of waivers and releases.</p>
<p>Thanks for commenting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marvin Schuldiner</title>
		<link>http://mediationchannel.com/2009/02/18/mediating-on-youtube/comment-page-1/#comment-594</link>
		<dc:creator>Marvin Schuldiner</dc:creator>
		<pubDate>Mon, 23 Feb 2009 15:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://mediationchannel.com/?p=1504#comment-594</guid>
		<description>I&#039;m wondering if this is an actual mediation, or a glorified role-play.  While the tone and tenor seemed on, it resolved in less than 4 minutes which is not the norm.  (I have had a few cases settle that quickly, but a relatively few.)

I have no &quot;war stories&quot; on my website or blog as I keep the confidentiality of mediation sacrosanct -- probably to my and the industry&#039;s detriment.  Tough catch-22.</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering if this is an actual mediation, or a glorified role-play.  While the tone and tenor seemed on, it resolved in less than 4 minutes which is not the norm.  (I have had a few cases settle that quickly, but a relatively few.)</p>
<p>I have no &#8220;war stories&#8221; on my website or blog as I keep the confidentiality of mediation sacrosanct &#8212; probably to my and the industry&#8217;s detriment.  Tough catch-22.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
