<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: NC Isn&#8217;t the Problem, SA Is&#8230; Part Deux</title>
	<atom:link href="http://opencontent.org/blog/archives/697/feed" rel="self" type="application/rss+xml" />
	<link>http://opencontent.org/blog/archives/697</link>
	<description>pragmatism over zeal</description>
	<lastBuildDate>Wed, 17 Mar 2010 06:59:35 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stephen Downes</title>
		<link>http://opencontent.org/blog/archives/697/comment-page-1#comment-42750</link>
		<dc:creator>Stephen Downes</dc:creator>
		<pubDate>Mon, 22 Dec 2008 21:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://opencontent.org/blog/?p=697#comment-42750</guid>
		<description>My response is here:
http://halfanhour.blogspot.com/2008/12/open-content-enclosure-and-conversion.html</description>
		<content:encoded><![CDATA[<p>My response is here:<br />
<a href="http://halfanhour.blogspot.com/2008/12/open-content-enclosure-and-conversion.html" rel="nofollow">http://halfanhour.blogspot.com/2008/12/open-content-enclosure-and-conversion.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Song</title>
		<link>http://opencontent.org/blog/archives/697/comment-page-1#comment-42748</link>
		<dc:creator>Steve Song</dc:creator>
		<pubDate>Sun, 21 Dec 2008 11:29:26 +0000</pubDate>
		<guid isPermaLink="false">http://opencontent.org/blog/?p=697#comment-42748</guid>
		<description>To (attempt to) answer your second question about how BY-SA might allow the cordoning off of IP, I have heard Lessig argue that the Non-Commercial clause is needed because the Share Alike clause is only activated by someone making a modification.  Share Alike states:
&quot;If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license.&quot;
Thus, if you do not alter the work but simply compile it with others into a book, for example, you are not bound to share it under the same terms.  This is a legacy, I think, of the software origin of the CC license.  Given that altering the formatting of a document is a transformation, I think the doomsday scenario of someone distributing material without activating the Share Alike clause is fairly slim.  My impression is that the Non-Commercial clause was dreamt up to avoid a situation where you might have a commercial compilation of BY-SA mp3s, which seems a little more plausible.

For me, this highlights the fact that Share Alike is broken and should come into play whether you modify the work or not.</description>
		<content:encoded><![CDATA[<p>To (attempt to) answer your second question about how BY-SA might allow the cordoning off of IP, I have heard Lessig argue that the Non-Commercial clause is needed because the Share Alike clause is only activated by someone making a modification.  Share Alike states:<br />
&#8220;If you alter, transform, or build upon this work, you may distribute the resulting work only under the same, similar or a compatible license.&#8221;<br />
Thus, if you do not alter the work but simply compile it with others into a book, for example, you are not bound to share it under the same terms.  This is a legacy, I think, of the software origin of the CC license.  Given that altering the formatting of a document is a transformation, I think the doomsday scenario of someone distributing material without activating the Share Alike clause is fairly slim.  My impression is that the Non-Commercial clause was dreamt up to avoid a situation where you might have a commercial compilation of BY-SA mp3s, which seems a little more plausible.</p>
<p>For me, this highlights the fact that Share Alike is broken and should come into play whether you modify the work or not.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.150 seconds -->
