<?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"
	>
<channel>
	<title>Comments on: Working Towards a Formal Supplier-side IP Policy</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<pubDate>Wed, 03 Dec 2008 01:22:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Three Brilliant Talks Continued</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-201969</link>
		<dc:creator>Three Brilliant Talks Continued</dc:creator>
		<pubDate>Fri, 09 Nov 2007 20:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-201969</guid>
		<description>[...] learn from.  In some ways, it is yet another manifestation of the dialog that I talked about, and James Governor talked [...]</description>
		<content:encoded><![CDATA[<p>[...] learn from.  In some ways, it is yet another manifestation of the dialog that I talked about, and James Governor talked [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Villa</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-147096</link>
		<dc:creator>Luis Villa</dc:creator>
		<pubDate>Fri, 24 Aug 2007 22:38:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-147096</guid>
		<description>Might also keep an eye on http://www.ownterms.org/ too, jgovernor.</description>
		<content:encoded><![CDATA[<p>Might also keep an eye on <a href="http://www.ownterms.org/" rel="nofollow">http://www.ownterms.org/</a> too, jgovernor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jgovernor</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-145381</link>
		<dc:creator>jgovernor</dc:creator>
		<pubDate>Wed, 22 Aug 2007 17:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-145381</guid>
		<description>@anant for obvious reasons i would really love to be involved in that initiative.</description>
		<content:encoded><![CDATA[<p>@anant for obvious reasons i would really love to be involved in that initiative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anant Jhingran</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-141375</link>
		<dc:creator>Anant Jhingran</dc:creator>
		<pubDate>Fri, 17 Aug 2007 02:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-141375</guid>
		<description>Thanks James, for connecting my thoughts with the thrust of your writing.  I definitely have to do some more reading on this.  In my small way, I am going to try and find some kindred spirits in some of the large companies I had mentioned, and see whether we can craft some creative licensing + the right anonymization to spur such innovation around "large data sets"...</description>
		<content:encoded><![CDATA[<p>Thanks James, for connecting my thoughts with the thrust of your writing.  I definitely have to do some more reading on this.  In my small way, I am going to try and find some kindred spirits in some of the large companies I had mentioned, and see whether we can craft some creative licensing + the right anonymization to spur such innovation around &#8220;large data sets&#8221;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jgovernor</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-140874</link>
		<dc:creator>jgovernor</dc:creator>
		<pubDate>Thu, 16 Aug 2007 11:23:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-140874</guid>
		<description>luis v - you da man, thanks so much for that.

chris m - yes and no. i would like to remove as many lawyers from the equation as possible. except of course ones that make a contribution... ;-)</description>
		<content:encoded><![CDATA[<p>luis v - you da man, thanks so much for that.</p>
<p>chris m - yes and no. i would like to remove as many lawyers from the equation as possible. except of course ones that make a contribution&#8230; <img src='http://www.redmonk.com/jgovernor/wp/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Villa</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-140138</link>
		<dc:creator>Luis Villa</dc:creator>
		<pubDate>Tue, 14 Aug 2007 22:31:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-140138</guid>
		<description>[IANAL; this is much closer to editing advice than legal advice anyway, but standard disclaimers apply."

"Unless explicitly noted in a formal Statement of Work, all work product shall be considered Background IP.

Background Intellectual Property shall mean Intellectual Property, proprietary information or confidential know-how relevant to the Project which is in the possession of a party prior to the commencement of the Project or generated after commencement of the Project but independent of the Project."

These seem slightly redundant: you've first defined background IP as 'everything not in a SOW', and then you redefine it as .. this long list of other stuff. If nothing else, I'd rearrange the order- define Background IP, and *then* say that everything not listed in the SOW is assumed to be Background IP.

In the second paragraph, instead of "such product", say "background IP"- you've defined the term, so use it :) I might break that last sentence into a separate paragraph as well, so that you've got one paragraph defining background IP, and then a second detailing the rights you retain with regards to background IP.

Instead of "Copyrighted works published during..." I'd say "Copyrightable works created during..."- that is much more comprehensive. 

More generally, do you see overlap between this second class of works and "Background IP?" It isn't entirely clear to me where one ends and the other begins, or why you deal with them differently.

Ownership does not pass to the community in the CC situation; you retain ownership but grant certain rights to the community under certain conditions.  I might rework that section to read "The vendor retains all rights to work undertaken under the term of the agreement, and may license or republish the work under any terms, including licenses such as Creative Commons licenses which grant extensive rights to third parties."

You probably want "No IP of the client shall be published without written permission" to read something like "The client's confidential information will not be published without written permission", since 'IP of the client' is very  broad and could well contain things that are already public. For clarity, I might also break this out into a separate paragraph.

As far as pre-existing forms, you might want to look at the Science Commons forms for further inspiration: http://scholars.sciencecommons.org/#form

They deal with a similar situation- the publisher has standardized, CC-unfriendly contracts and most of the power, so the CC forms are framed as addenda to those contracts. I imagine you're in a similar situation with IBM, etc.</description>
		<content:encoded><![CDATA[<p>[IANAL; this is much closer to editing advice than legal advice anyway, but standard disclaimers apply."</p>
<p>"Unless explicitly noted in a formal Statement of Work, all work product shall be considered Background IP.</p>
<p>Background Intellectual Property shall mean Intellectual Property, proprietary information or confidential know-how relevant to the Project which is in the possession of a party prior to the commencement of the Project or generated after commencement of the Project but independent of the Project."</p>
<p>These seem slightly redundant: you've first defined background IP as 'everything not in a SOW', and then you redefine it as .. this long list of other stuff. If nothing else, I'd rearrange the order- define Background IP, and *then* say that everything not listed in the SOW is assumed to be Background IP.</p>
<p>In the second paragraph, instead of "such product", say "background IP"- you've defined the term, so use it <img src='http://www.redmonk.com/jgovernor/wp/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> I might break that last sentence into a separate paragraph as well, so that you've got one paragraph defining background IP, and then a second detailing the rights you retain with regards to background IP.</p>
<p>Instead of "Copyrighted works published during..." I'd say "Copyrightable works created during..."- that is much more comprehensive. </p>
<p>More generally, do you see overlap between this second class of works and "Background IP?" It isn't entirely clear to me where one ends and the other begins, or why you deal with them differently.</p>
<p>Ownership does not pass to the community in the CC situation; you retain ownership but grant certain rights to the community under certain conditions.  I might rework that section to read "The vendor retains all rights to work undertaken under the term of the agreement, and may license or republish the work under any terms, including licenses such as Creative Commons licenses which grant extensive rights to third parties."</p>
<p>You probably want "No IP of the client shall be published without written permission" to read something like "The client's confidential information will not be published without written permission", since 'IP of the client' is very  broad and could well contain things that are already public. For clarity, I might also break this out into a separate paragraph.</p>
<p>As far as pre-existing forms, you might want to look at the Science Commons forms for further inspiration: <a href="http://scholars.sciencecommons.org/#form" rel="nofollow">http://scholars.sciencecommons.org/#form</a></p>
<p>They deal with a similar situation- the publisher has standardized, CC-unfriendly contracts and most of the power, so the CC forms are framed as addenda to those contracts. I imagine you&#8217;re in a similar situation with IBM, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Mahan</title>
		<link>http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-139962</link>
		<dc:creator>Christopher Mahan</dc:creator>
		<pubDate>Tue, 14 Aug 2007 18:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/08/14/working-towards-a-formal-supplier-side-ip-policy/#comment-139962</guid>
		<description>Knowledge hoarders (companies that protect their IP jealously) are following the old saying: "knowledge is power".

Can't blame them, that's how they were raised.

Get some lawyers on that.</description>
		<content:encoded><![CDATA[<p>Knowledge hoarders (companies that protect their IP jealously) are following the old saying: &#8220;knowledge is power&#8221;.</p>
<p>Can&#8217;t blame them, that&#8217;s how they were raised.</p>
<p>Get some lawyers on that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
