<?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: Why I and you should avoid NC licences</title>
	<atom:link href="http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/</link>
	<description>A Scientist and the Web</description>
	<lastBuildDate>Thu, 13 Jun 2013 13:42:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Commercial Exploitation of Content and the Instagram Story &#171; UK Web Focus</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-119198</link>
		<dc:creator>Commercial Exploitation of Content and the Instagram Story &#171; UK Web Focus</dc:creator>
		<pubDate>Thu, 20 Dec 2012 08:01:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-119198</guid>
		<description>[...] The BY-NC-SA licence was chosen [in 2005] as it seemed at the time to provide a safe option, allowing the resources to be reused by others in the sector whilst retaining the right to commercially exploit the resources. In reality, however, the resources haven’t been exploited commercially and increasingly the sector is becoming aware of the difficulties in licensing resources which excludes commercial use, as described by Peter Murray-Rust in a recent post on “Why I and you should avoid NC licence“. [...]</description>
		<content:encoded><![CDATA[<p>[...] The BY-NC-SA licence was chosen [in 2005] as it seemed at the time to provide a safe option, allowing the resources to be reused by others in the sector whilst retaining the right to commercially exploit the resources. In reality, however, the resources haven’t been exploited commercially and increasingly the sector is becoming aware of the difficulties in licensing resources which excludes commercial use, as described by Peter Murray-Rust in a recent post on “Why I and you should avoid NC licence“. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A visualization of Gold Open Access options - Ross Mounce</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-114594</link>
		<dc:creator>A visualization of Gold Open Access options - Ross Mounce</dc:creator>
		<pubDate>Thu, 30 Aug 2012 14:53:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-114594</guid>
		<description>[...] [2] Murray-Rust, P. 2010 http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/ [...]</description>
		<content:encoded><![CDATA[<p>[...] [2] Murray-Rust, P. 2010 <a href="http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/" rel="nofollow">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Panton Fellowship updates: May (month 2) - Metacladistics</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-108563</link>
		<dc:creator>Panton Fellowship updates: May (month 2) - Metacladistics</dc:creator>
		<pubDate>Thu, 07 Jun 2012 12:32:21 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-108563</guid>
		<description>[...] Then on the 11th of May, PMR came Bath to give a talk to our Biology &amp; Biochemistry Department. Those who came (including our subject librarian – thanks for coming!) were wowed with the ways in which PMR and colleagues have helped make semantically-enriched Linked Open Data available on chemicals for everyone, not just academic chemists! It’s brilliant to have an expert demonstration of the ways in which projects like CrystalEye have made the data underlying some chemical research publications far more easily searchable, open, and re-usable across many thousands of publications. There’s a strong, easily-justified need for more of this type of post-publication data scraping in biology (and palaeontology I might add!). We share a strong belief that research publications should be made open and explicitly re-usable without restriction. [...]</description>
		<content:encoded><![CDATA[<p>[...] Then on the 11th of May, PMR came Bath to give a talk to our Biology &amp; Biochemistry Department. Those who came (including our subject librarian – thanks for coming!) were wowed with the ways in which PMR and colleagues have helped make semantically-enriched Linked Open Data available on chemicals for everyone, not just academic chemists! It’s brilliant to have an expert demonstration of the ways in which projects like CrystalEye have made the data underlying some chemical research publications far more easily searchable, open, and re-usable across many thousands of publications. There’s a strong, easily-justified need for more of this type of post-publication data scraping in biology (and palaeontology I might add!). We share a strong belief that research publications should be made open and explicitly re-usable without restriction. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Panton Fellowship updates: May (month 2) &#124; Palaeophylophenomics</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-107689</link>
		<dc:creator>Panton Fellowship updates: May (month 2) &#124; Palaeophylophenomics</dc:creator>
		<pubDate>Mon, 28 May 2012 00:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-107689</guid>
		<description>[...] Then on the 11th of May, PMR came Bath to give a talk to our Biology &amp; Biochemistry Department. Those who came (including our subject librarian &#8211; thanks for coming!) were wowed with the ways in which PMR and colleagues have helped make semantically-enriched Linked Open Data available on chemicals for everyone, not just academic chemists! It&#8217;s brilliant to have an expert demonstration of the ways in which projects like CrystalEye have made the data underlying some chemical research publications far more easily searchable, open, and re-usable across many thousands of publications. There&#8217;s a strong, easily-justified need for more of this type of post-publication data scraping in biology (and palaeontology I might add!). We share a strong belief that research publications should be made open and explicitly re-usable without restriction. [...]</description>
		<content:encoded><![CDATA[<p>[...] Then on the 11th of May, PMR came Bath to give a talk to our Biology &amp; Biochemistry Department. Those who came (including our subject librarian &#8211; thanks for coming!) were wowed with the ways in which PMR and colleagues have helped make semantically-enriched Linked Open Data available on chemicals for everyone, not just academic chemists! It&#8217;s brilliant to have an expert demonstration of the ways in which projects like CrystalEye have made the data underlying some chemical research publications far more easily searchable, open, and re-usable across many thousands of publications. There&#8217;s a strong, easily-justified need for more of this type of post-publication data scraping in biology (and palaeontology I might add!). We share a strong belief that research publications should be made open and explicitly re-usable without restriction. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pm286</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-89401</link>
		<dc:creator>pm286</dc:creator>
		<pubDate>Wed, 02 Feb 2011 08:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-89401</guid>
		<description>&gt;&gt;The problem with using non-NC licenses for some kinds of content is that it can create competitors. 
Agreed. There is nothing wrong with creating software that is sold. But if you licence it as NC then you are neither in the spirit of F/OSS or Open Data. 

&gt;&gt;In cases where the IP is not a competitive advantage then sharing is the best approach (BY-CC). We have some work that we author and copyright precisely to create revenue. 
Nothing wrong. But don&#039;t use NC. It&#039;s effectively unworkable and creates huge amounts of wasted time for exactly the people that you might like to benefit from it.

&gt;&gt;Otherwise it is miserly to do so. As per the comment on permission, we agree. We have always provided permission when asked.

Asking persmission is fine. But it&#039;s effectively not Open. The effort in asking permission - particularly when there are thousands of items as in papers pr data sets - can be enormous. It solves nothing. The grantees cannot effectively re-use the material.

P.</description>
		<content:encoded><![CDATA[<p>&gt;&gt;The problem with using non-NC licenses for some kinds of content is that it can create competitors.<br />
Agreed. There is nothing wrong with creating software that is sold. But if you licence it as NC then you are neither in the spirit of F/OSS or Open Data. </p>
<p>&gt;&gt;In cases where the IP is not a competitive advantage then sharing is the best approach (BY-CC). We have some work that we author and copyright precisely to create revenue.<br />
Nothing wrong. But don&#8217;t use NC. It&#8217;s effectively unworkable and creates huge amounts of wasted time for exactly the people that you might like to benefit from it.</p>
<p>&gt;&gt;Otherwise it is miserly to do so. As per the comment on permission, we agree. We have always provided permission when asked.</p>
<p>Asking persmission is fine. But it&#8217;s effectively not Open. The effort in asking permission &#8211; particularly when there are thousands of items as in papers pr data sets &#8211; can be enormous. It solves nothing. The grantees cannot effectively re-use the material.</p>
<p>P.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lanna Innovation</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-89379</link>
		<dc:creator>Lanna Innovation</dc:creator>
		<pubDate>Wed, 02 Feb 2011 03:22:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-89379</guid>
		<description>The problem with using non-NC licenses for some kinds of content is that it can create competitors. In cases where the IP is not a competitive advantage then sharing is the best approach (BY-CC). We have some work that we author and copyright precisely to create revenue. Otherwise it is miserly to do so. As per the comment on permission, we agree. We have always provided permission when asked.</description>
		<content:encoded><![CDATA[<p>The problem with using non-NC licenses for some kinds of content is that it can create competitors. In cases where the IP is not a competitive advantage then sharing is the best approach (BY-CC). We have some work that we author and copyright precisely to create revenue. Otherwise it is miserly to do so. As per the comment on permission, we agree. We have always provided permission when asked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pm286</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-85097</link>
		<dc:creator>pm286</dc:creator>
		<pubDate>Tue, 04 Jan 2011 13:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-85097</guid>
		<description>Commercial organizations cannot prevent people having access to the free content. If you create version A1 and a commercial copies it to A2 and restricts it then the world can still use A1. If they enhance A2 to B2 then they are welcome to and if it&#039;s perceived as &quot;better&quot; than A1 then that is their right. You challenge that by making a C1 which is better than B2, not by restricting them. I don&#039;t see what you have lost by removing NC. It CANNOT affect your work.</description>
		<content:encoded><![CDATA[<p>Commercial organizations cannot prevent people having access to the free content. If you create version A1 and a commercial copies it to A2 and restricts it then the world can still use A1. If they enhance A2 to B2 then they are welcome to and if it&#8217;s perceived as &#8220;better&#8221; than A1 then that is their right. You challenge that by making a C1 which is better than B2, not by restricting them. I don&#8217;t see what you have lost by removing NC. It CANNOT affect your work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Downes</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-84529</link>
		<dc:creator>Stephen Downes</dc:creator>
		<pubDate>Sat, 01 Jan 2011 16:14:28 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-84529</guid>
		<description>I use the NC clause in all my work, and my motivation, rather than the straw man argument typically presented by pro-commercialization arguments, is very pragmatic: I do not want people to restrict access to my work.

The point here is, when people &#039;commercialize&#039; content, such as my writing, what they are doing is making money by charging for access to the work. This means that, if someone does not pay them money, they will deny that person access to the work. This is wrong. This is not what is meant by &#039;free&#039;.</description>
		<content:encoded><![CDATA[<p>I use the NC clause in all my work, and my motivation, rather than the straw man argument typically presented by pro-commercialization arguments, is very pragmatic: I do not want people to restrict access to my work.</p>
<p>The point here is, when people &#8216;commercialize&#8217; content, such as my writing, what they are doing is making money by charging for access to the work. This means that, if someone does not pay them money, they will deny that person access to the work. This is wrong. This is not what is meant by &#8216;free&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Non-Commercial Use Restriction Removed From This Blog &#171; UK Web Focus</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-84490</link>
		<dc:creator>Non-Commercial Use Restriction Removed From This Blog &#171; UK Web Focus</dc:creator>
		<pubDate>Sat, 01 Jan 2011 12:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-84490</guid>
		<description>[...] The BY-NC-SA licence was chosen as it seemed at the time to provide a safe option, allowing the resources to be reused by others in the sector whilst retaining the right to commercially exploit the resources.In reality, however, the resources haven&#8217;t been exploited commercially and increasingly the sector is becoming aware of the difficulties in licensing resources which excludes commercial use, as described by Peter Murray-Rust in a recent post on &#8220;Why I and you should avoid NC licence&#8220;. [...]</description>
		<content:encoded><![CDATA[<p>[...] The BY-NC-SA licence was chosen as it seemed at the time to provide a safe option, allowing the resources to be reused by others in the sector whilst retaining the right to commercially exploit the resources.In reality, however, the resources haven&#8217;t been exploited commercially and increasingly the sector is becoming aware of the difficulties in licensing resources which excludes commercial use, as described by Peter Murray-Rust in a recent post on &#8220;Why I and you should avoid NC licence&#8220;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Haff</title>
		<link>http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-82557</link>
		<dc:creator>Gordon Haff</dc:creator>
		<pubDate>Wed, 22 Dec 2010 17:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.ch.cam.ac.uk/pmr/2010/12/17/why-i-and-you-should-avoid-nc-licences/#comment-82557</guid>
		<description>Speaking for myself, I&#039;m very careful to use only CC licensed photos/graphics for commercial use when I give presentations for my company. In theory, I could ask for permission with other material, but unless there were something that was just *perfect*, I just tend to use something els. And, if I&#039;m going to pay anyway, microstock is often the better route.</description>
		<content:encoded><![CDATA[<p>Speaking for myself, I&#8217;m very careful to use only CC licensed photos/graphics for commercial use when I give presentations for my company. In theory, I could ask for permission with other material, but unless there were something that was just *perfect*, I just tend to use something els. And, if I&#8217;m going to pay anyway, microstock is often the better route.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
