<?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: Confidentiality Exclusions versus Disclosures</title>
	<atom:link href="http://www.licensinghandbook.com/2009/08/15/confidentiality-exclusions-versus-disclosures/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.licensinghandbook.com/2009/08/15/confidentiality-exclusions-versus-disclosures/</link>
	<description>The companion site to the Software Licensing Handbook</description>
	<lastBuildDate>Wed, 06 Jan 2010 00:13:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.licensinghandbook.com/2009/08/15/confidentiality-exclusions-versus-disclosures/comment-page-1/#comment-899</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 15 Aug 2009 23:25:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1116#comment-899</guid>
		<description>Heh, nice job, Chris.  I clicked through to the article from my feedreader specifically to hit that point about &quot;public domain.&quot;  It&#039;s a horrible mistake that keeps being perpetuated for some reason.  Glad to see I&#039;m not the only one fighting against it.

I disagree with your point about the privilege, though.  It&#039;s not really relevant to confidentiality, just evidence (and the spouse could waive anyway).  In reality, though, spouses just don&#039;t talk because they just don&#039;t care... or at least mine doesn&#039;t anyway.

Also, we draft our agreements so that even information that becomes known to [some segment of the population] as a result of criminal activity/breach/security breach must still be treated confidentially and subject to whatever use restrictions apply.  No point opening the front doors because a window got cracked.</description>
		<content:encoded><![CDATA[<p>Heh, nice job, Chris.  I clicked through to the article from my feedreader specifically to hit that point about &#8220;public domain.&#8221;  It&#8217;s a horrible mistake that keeps being perpetuated for some reason.  Glad to see I&#8217;m not the only one fighting against it.</p>
<p>I disagree with your point about the privilege, though.  It&#8217;s not really relevant to confidentiality, just evidence (and the spouse could waive anyway).  In reality, though, spouses just don&#8217;t talk because they just don&#8217;t care&#8230; or at least mine doesn&#8217;t anyway.</p>
<p>Also, we draft our agreements so that even information that becomes known to [some segment of the population] as a result of criminal activity/breach/security breach must still be treated confidentially and subject to whatever use restrictions apply.  No point opening the front doors because a window got cracked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Lemens</title>
		<link>http://www.licensinghandbook.com/2009/08/15/confidentiality-exclusions-versus-disclosures/comment-page-1/#comment-897</link>
		<dc:creator>Chris Lemens</dc:creator>
		<pubDate>Sat, 15 Aug 2009 20:52:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1116#comment-897</guid>
		<description>A couple of points:

First, your first example exception contains a very common mistake. The &quot;public domain&quot; is a copyright concept inappropriately imported into confidentiality agreement. &quot;Public domain&quot; in copyright means a work of authorship to which the owner has given up his ownership rights. No one would want this critical exception limited to public domain documents. Instead, the exception shoudl be for information that is available to the public, or is publicly known, or something along those lines.

Second, I agree with your main point. There is a parallel private construction that I sometimes see. The exception is for something like &quot;information that the disclosing party discloses to any third party who has no legal obligation to maintain its confidentiality.&quot; The problem with that is that you might give information to someone that you know is never going to disclose it, and even someone where you can prevent the disclosure. For example, many employees talk to their spouses about what happens at work. There is zero risk of further disclosure, most of the time. In fact, in many states, communications between spouses are privileged. Similarly, you might give information to someone else you trust and who never, in fact, discloses it further. That should not blow up your trade secret.

Chris Lemens</description>
		<content:encoded><![CDATA[<p>A couple of points:</p>
<p>First, your first example exception contains a very common mistake. The &#8220;public domain&#8221; is a copyright concept inappropriately imported into confidentiality agreement. &#8220;Public domain&#8221; in copyright means a work of authorship to which the owner has given up his ownership rights. No one would want this critical exception limited to public domain documents. Instead, the exception shoudl be for information that is available to the public, or is publicly known, or something along those lines.</p>
<p>Second, I agree with your main point. There is a parallel private construction that I sometimes see. The exception is for something like &#8220;information that the disclosing party discloses to any third party who has no legal obligation to maintain its confidentiality.&#8221; The problem with that is that you might give information to someone that you know is never going to disclose it, and even someone where you can prevent the disclosure. For example, many employees talk to their spouses about what happens at work. There is zero risk of further disclosure, most of the time. In fact, in many states, communications between spouses are privileged. Similarly, you might give information to someone else you trust and who never, in fact, discloses it further. That should not blow up your trade secret.</p>
<p>Chris Lemens</p>
]]></content:encoded>
	</item>
</channel>
</rss>

