<?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: Copyright Ownership and Comments</title>
	<atom:link href="http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/</link>
	<description>Content Theft, Plagiarism, Copyright Infringement</description>
	<lastBuildDate>Mon, 13 Feb 2012 07:59:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: PlagiarismToday &#187; Fark Claims Copyright on Posted Works</title>
		<link>http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/comment-page-1/#comment-57746</link>
		<dc:creator>PlagiarismToday &#187; Fark Claims Copyright on Posted Works</dc:creator>
		<pubDate>Thu, 26 Apr 2007 18:11:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=312#comment-57746</guid>
		<description>[...] Though the exact extent of the implied license of comments, forum posts and other submitted works, is up for debate, most agree that it does not extend to full copyright [...]</description>
		<content:encoded><![CDATA[<p>[...] Though the exact extent of the implied license of comments, forum posts and other submitted works, is up for debate, most agree that it does not extend to full copyright [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ja</title>
		<link>http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/comment-page-1/#comment-8998</link>
		<dc:creator>Ja</dc:creator>
		<pubDate>Fri, 25 Aug 2006 08:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=312#comment-8998</guid>
		<description></description>
		<content:encoded><![CDATA[<p>Excellent post and good explanation of easy measures to be taken.</p>
<p>Though this article focuses mainly on comments, forum posts, and the like I&#8217;ve posted a few times myself on the licensing issues that people aren&#8217;t aware of or don&#8217;t seem to care about.</p>
<p>I know you&#8217;ve read my little post about licensing with hreviews and the huge conflicts there.  I also have major issues with how places like Amazon go about notifying people posting reviews and such of their rights.  </p>
<p>I posted about it a while back and I believe it&#8217;s gotten worse since.  When one goes to submit a review, the &#8220;review guidelines&#8221; are right at the top for you to click on and read, however the &#8220;Conditions of Use&#8221; link is below anything you have to write in, click, etc and on my screen it&#8217;s not visible without scrolling down which most people wouldn&#8217;t do since everything needed to submit the review is already on the screen.</p>
<p>Only when you find that link, click, and wade through the massive all-in-one conditions of use page and manage to find the part relavent to content submission once you get to the second paragraph you are then notified that by submitting content you are agreeing to about a billion things including giving them more or less all rights to do anything they want with said content (and I do mean <em>anything</em>.  I didn&#8217;t write as much detail about how out of the way and inconvenient it is, but, as always, you can see the other details <a href="http://disconnectthedots.net/ja/inherent-flaws/amazon-reviews-and-giving-away-your-content.html" rel="nofollow">in my old post</a> if you wish.</p>
<p>I&#8217;ll be applying something similar to what you&#8217;ve done with your comment form and petitioning for including something similar as an option in the next release of K2 since they&#8217;re looking at changing the comment form anyway.  Comment form plugins for WordPress are by nature more difficult than they should be unfortunately.</p>
<p>Cheers,</p>
<p>JÄ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ja</title>
		<link>http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/comment-page-1/#comment-122134</link>
		<dc:creator>Ja</dc:creator>
		<pubDate>Fri, 25 Aug 2006 08:07:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=312#comment-122134</guid>
		<description>Excellent post and good explanation of easy measures to be taken.&lt;br&gt;&lt;br&gt;Though this article focuses mainly on comments, forum posts, and the like I&#039;ve posted a few times myself on the licensing issues that people aren&#039;t aware of or don&#039;t seem to care about.&lt;br&gt;&lt;br&gt;I know you&#039;ve read my little post about licensing with hreviews and the huge conflicts there.  I also have major issues with how places like Amazon go about notifying people posting reviews and such of their rights.  &lt;br&gt;&lt;br&gt;I posted about it a while back and I believe it&#039;s gotten worse since.  When one goes to submit a review, the &quot;review guidelines&quot; are right at the top for you to click on and read, however the &quot;Conditions of Use&quot; link is below anything you have to write in, click, etc and on my screen it&#039;s not visible without scrolling down which most people wouldn&#039;t do since everything needed to submit the review is already on the screen.&lt;br&gt;&lt;br&gt;Only when you find that link, click, and wade through the massive all-in-one conditions of use page and manage to find the part relavent to content submission once you get to the second paragraph you are then notified that by submitting content you are agreeing to about a billion things including giving them more or less all rights to do anything they want with said content (and I do mean &lt;em&gt;anything&lt;/em&gt;.  I didn&#039;t write as much detail about how out of the way and inconvenient it is, but, as always, you can see the other details &lt;a href=&quot;http://disconnectthedots.net/ja/inherent-flaws/amazon-reviews-and-giving-away-your-content.html&quot; rel=&quot;nofollow&quot;&gt;in my old post&lt;/a&gt; if you wish.&lt;br&gt;&lt;br&gt;I&#039;ll be applying something similar to what you&#039;ve done with your comment form and petitioning for including something similar as an option in the next release of K2 since they&#039;re looking at changing the comment form anyway.  Comment form plugins for Wordpress are by nature more difficult than they should be unfortunately.&lt;br&gt;&lt;br&gt;Cheers,&lt;br&gt;&lt;br&gt;JÃ„?</description>
		<content:encoded><![CDATA[<p>Excellent post and good explanation of easy measures to be taken.</p>
<p>Though this article focuses mainly on comments, forum posts, and the like I&#8217;ve posted a few times myself on the licensing issues that people aren&#8217;t aware of or don&#8217;t seem to care about.</p>
<p>I know you&#8217;ve read my little post about licensing with hreviews and the huge conflicts there.  I also have major issues with how places like Amazon go about notifying people posting reviews and such of their rights.  </p>
<p>I posted about it a while back and I believe it&#8217;s gotten worse since.  When one goes to submit a review, the &#8220;review guidelines&#8221; are right at the top for you to click on and read, however the &#8220;Conditions of Use&#8221; link is below anything you have to write in, click, etc and on my screen it&#8217;s not visible without scrolling down which most people wouldn&#8217;t do since everything needed to submit the review is already on the screen.</p>
<p>Only when you find that link, click, and wade through the massive all-in-one conditions of use page and manage to find the part relavent to content submission once you get to the second paragraph you are then notified that by submitting content you are agreeing to about a billion things including giving them more or less all rights to do anything they want with said content (and I do mean <em>anything</em>.  I didn&#8217;t write as much detail about how out of the way and inconvenient it is, but, as always, you can see the other details <a href="http://disconnectthedots.net/ja/inherent-flaws/amazon-reviews-and-giving-away-your-content.html" rel="nofollow">in my old post</a> if you wish.</p>
<p>I&#8217;ll be applying something similar to what you&#8217;ve done with your comment form and petitioning for including something similar as an option in the next release of K2 since they&#8217;re looking at changing the comment form anyway.  Comment form plugins for WordPress are by nature more difficult than they should be unfortunately.</p>
<p>Cheers,</p>
<p>JÃ„?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elf's DH</title>
		<link>http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/comment-page-1/#comment-122133</link>
		<dc:creator>Elf's DH</dc:creator>
		<pubDate>Fri, 25 Aug 2006 02:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=312#comment-122133</guid>
		<description>This is also a problem that faces wikis and collaborative development, especially if the issue isn&#039;t addressed before the wiki opens to the public.  That&#039;s exactly what happened to the &lt;a href=&quot;http://wiki.debian.org/WikiLicencingTerms&quot; rel=&quot;nofollow&quot;&gt;Debian wiki&lt;/a&gt;.  &lt;br&gt;&lt;br&gt;On a blog, one can post in the copyright notice: &quot;All comments posted after such-and-such date are under X license, prior to that, they are under an implied license.&quot;  On a wiki, any given page can have substantial portions written and edited by different people, and it really tests the limits of the implied license.&lt;br&gt;&lt;br&gt;By the way, you might want to change the license text at the bottom of your page to reflect that the comments and original work are under incompatible licenses (unless the existence of a comment adds the notice, and I just don&#039;t see it yet).</description>
		<content:encoded><![CDATA[<p>This is also a problem that faces wikis and collaborative development, especially if the issue isn&#8217;t addressed before the wiki opens to the public.  That&#8217;s exactly what happened to the <a href="http://wiki.debian.org/WikiLicencingTerms" rel="nofollow">Debian wiki</a>.  </p>
<p>On a blog, one can post in the copyright notice: &#8220;All comments posted after such-and-such date are under X license, prior to that, they are under an implied license.&#8221;  On a wiki, any given page can have substantial portions written and edited by different people, and it really tests the limits of the implied license.</p>
<p>By the way, you might want to change the license text at the bottom of your page to reflect that the comments and original work are under incompatible licenses (unless the existence of a comment adds the notice, and I just don&#8217;t see it yet).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elf&#039;s DH</title>
		<link>http://www.plagiarismtoday.com/2006/08/22/copyright-ownership-and-comments/comment-page-1/#comment-8936</link>
		<dc:creator>Elf&#039;s DH</dc:creator>
		<pubDate>Thu, 24 Aug 2006 21:12:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.plagiarismtoday.com/?p=312#comment-8936</guid>
		<description>This is also a problem that faces wikis and collaborative development, especially if the issue isn&#039;t addressed before the wiki opens to the public.  That&#039;s exactly what happened to the &lt;a href=&quot;http://wiki.debian.org/WikiLicencingTerms&quot; rel=&quot;nofollow&quot;&gt;Debian wiki&lt;/a&gt;.   
 
On a blog, one can post in the copyright notice: &quot;All comments posted after such-and-such date are under X license, prior to that, they are under an implied license.&quot;  On a wiki, any given page can have substantial portions written and edited by different people, and it really tests the limits of the implied license. 
 
By the way, you might want to change the license text at the bottom of your page to reflect that the comments and original work are under incompatible licenses (unless the existence of a comment adds the notice, and I just don&#039;t see it yet). </description>
		<content:encoded><![CDATA[<p>This is also a problem that faces wikis and collaborative development, especially if the issue isn&#039;t addressed before the wiki opens to the public.  That&#039;s exactly what happened to the <a href="http://wiki.debian.org/WikiLicencingTerms" rel="nofollow">Debian wiki</a>.  </p>
<p>On a blog, one can post in the copyright notice: &quot;All comments posted after such-and-such date are under X license, prior to that, they are under an implied license.&quot;  On a wiki, any given page can have substantial portions written and edited by different people, and it really tests the limits of the implied license.</p>
<p>By the way, you might want to change the license text at the bottom of your page to reflect that the comments and original work are under incompatible licenses (unless the existence of a comment adds the notice, and I just don&#039;t see it yet).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using disk: enhanced

Served from: www.plagiarismtoday.com @ 2012-02-13 20:31:23 -->
