<?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: Creating a Custom License</title> <atom:link href="http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/feed/" rel="self" type="application/rss+xml" /><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/</link> <description>Content Theft, Plagiarism, Copyright Infringement</description> <lastBuildDate>Sat, 20 Mar 2010 01:12:29 +0000</lastBuildDate> <generator>http://wordpress.org/?v=abc</generator> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: What to do about copyright &#171; one cool site: wordpress blogging tips</title><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/comment-page-1/#comment-120585</link> <dc:creator>What to do about copyright &#171; one cool site: wordpress blogging tips</dc:creator> <pubDate>Thu, 17 Jul 2008 16:55:29 +0000</pubDate> <guid
isPermaLink="false">http://www.plagiarismtoday.com/?p=1331#comment-120585</guid> <description>[...] iCopyright - &#8220;This is a great opportunity for those who like Creative Commons-style licensing but have not found the exact terms to suit them to easily make their content available for limited reuse.&#8221; &#8212; Jonathan Bailey in Creating a Custom License. [...]</description> <content:encoded><![CDATA[<p>[...] iCopyright &#8211; &#8220;This is a great opportunity for those who like Creative Commons-style licensing but have not found the exact terms to suit them to easily make their content available for limited reuse.&#8221; &#8212; Jonathan Bailey in Creating a Custom License. [...]</p> ]]></content:encoded> </item> <item><title>By: Jonathan Bailey</title><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/comment-page-1/#comment-129110</link> <dc:creator>Jonathan Bailey</dc:creator> <pubDate>Thu, 17 Jul 2008 06:36:45 +0000</pubDate> <guid
isPermaLink="false">http://www.plagiarismtoday.com/?p=1331#comment-129110</guid> <description>I would submit a different argument. That allowing the license terms to be changed as well as the description already sacrifices the benefit of a uniform license set.&lt;br&gt;&lt;br&gt;One of the perks of CC is not only consistent naming, but that we know my CC-BY-SA license will be the same as every other CC-BY-SA license. With iCopyrght Creators, that isn&#039;t certain, one has to read the description and the license itself to be sure that they are following the license.&lt;br&gt;&lt;br&gt;The benefit of the standard license is already lost. One already has to read the full license text so I don&#039;t see how allowing title changes can hurt, but rather, only simplify the process of interpreting iCopyright license.&lt;br&gt;&lt;br&gt;As far as being too U.S.-centric goes, I agree. You need to include provisions for dealing with moral rights at least as that is something that exists almost everywhere else in the world.&lt;br&gt;&lt;br&gt;However, I also understand that you had to start somewhere and the U.S. was the most logical place...</description> <content:encoded><![CDATA[<p>I would submit a different argument. That allowing the license terms to be changed as well as the description already sacrifices the benefit of a uniform license set.</p><p>One of the perks of CC is not only consistent naming, but that we know my CC-BY-SA license will be the same as every other CC-BY-SA license. With iCopyrght Creators, that isn&#39;t certain, one has to read the description and the license itself to be sure that they are following the license.</p><p>The benefit of the standard license is already lost. One already has to read the full license text so I don&#39;t see how allowing title changes can hurt, but rather, only simplify the process of interpreting iCopyright license.</p><p>As far as being too U.S.-centric goes, I agree. You need to include provisions for dealing with moral rights at least as that is something that exists almost everywhere else in the world.</p><p>However, I also understand that you had to start somewhere and the U.S. was the most logical place&#8230;</p> ]]></content:encoded> </item> <item><title>By: Mike ODonnell</title><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/comment-page-1/#comment-129109</link> <dc:creator>Mike ODonnell</dc:creator> <pubDate>Thu, 17 Jul 2008 04:56:39 +0000</pubDate> <guid
isPermaLink="false">http://www.plagiarismtoday.com/?p=1331#comment-129109</guid> <description>Interested to hear from you and your readers if giving creators the ability to change the titles as well as the descriptions, outweighs the possible downside of creating confusion among the general public (potential licensees). One of the nice things about Creative Commons is that it provides a standard (uniform) set of licenses.  That&#039;s why you can change the descriptions, but not the titles in (C)reators. The other shortcomings are duly noted and slated for fix in the next release. &lt;br&gt;&lt;br&gt;(C)reators certainly needs to provide additional templates for Terms of Use. It was rightly slammed by beta testers in Canada for being to U.S. centric. Even though creators can edit the terms, they should have valid templates to begin with, depending upon their residence and needs. This blog also points out the need for better documentation! Thank you, Jonathan. We are learning from beta testers like you who are putting the app through its paces.</description> <content:encoded><![CDATA[<p>Interested to hear from you and your readers if giving creators the ability to change the titles as well as the descriptions, outweighs the possible downside of creating confusion among the general public (potential licensees). One of the nice things about Creative Commons is that it provides a standard (uniform) set of licenses.  That&#39;s why you can change the descriptions, but not the titles in (C)reators. The other shortcomings are duly noted and slated for fix in the next release.</p><p>(C)reators certainly needs to provide additional templates for Terms of Use. It was rightly slammed by beta testers in Canada for being to U.S. centric. Even though creators can edit the terms, they should have valid templates to begin with, depending upon their residence and needs. This blog also points out the need for better documentation! Thank you, Jonathan. We are learning from beta testers like you who are putting the app through its paces.</p> ]]></content:encoded> </item> <item><title>By: Jonathan Bailey</title><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/comment-page-1/#comment-128119</link> <dc:creator>Jonathan Bailey</dc:creator> <pubDate>Thu, 17 Jul 2008 02:36:45 +0000</pubDate> <guid
isPermaLink="false">http://www.plagiarismtoday.com/?p=1331#comment-128119</guid> <description>I would submit a different argument. That allowing the license terms to be changed as well as the description already sacrifices the benefit of a uniform license set.&lt;br&gt;&lt;br&gt;One of the perks of CC is not only consistent naming, but that we know my CC-BY-SA license will be the same as every other CC-BY-SA license. With iCopyrght Creators, that isn&#039;t certain, one has to read the description and the license itself to be sure that they are following the license.&lt;br&gt;&lt;br&gt;The benefit of the standard license is already lost. One already has to read the full license text so I don&#039;t see how allowing title changes can hurt, but rather, only simplify the process of interpreting iCopyright license.&lt;br&gt;&lt;br&gt;As far as being too U.S.-centric goes, I agree. You need to include provisions for dealing with moral rights at least as that is something that exists almost everywhere else in the world.&lt;br&gt;&lt;br&gt;However, I also understand that you had to start somewhere and the U.S. was the most logical place...</description> <content:encoded><![CDATA[<p>I would submit a different argument. That allowing the license terms to be changed as well as the description already sacrifices the benefit of a uniform license set.</p><p>One of the perks of CC is not only consistent naming, but that we know my CC-BY-SA license will be the same as every other CC-BY-SA license. With iCopyrght Creators, that isn&#39;t certain, one has to read the description and the license itself to be sure that they are following the license.</p><p>The benefit of the standard license is already lost. One already has to read the full license text so I don&#39;t see how allowing title changes can hurt, but rather, only simplify the process of interpreting iCopyright license.</p><p>As far as being too U.S.-centric goes, I agree. You need to include provisions for dealing with moral rights at least as that is something that exists almost everywhere else in the world.</p><p>However, I also understand that you had to start somewhere and the U.S. was the most logical place&#8230;</p> ]]></content:encoded> </item> <item><title>By: Jonathan Bailey</title><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/comment-page-1/#comment-121619</link> <dc:creator>Jonathan Bailey</dc:creator> <pubDate>Thu, 17 Jul 2008 01:36:45 +0000</pubDate> <guid
isPermaLink="false">http://www.plagiarismtoday.com/?p=1331#comment-121619</guid> <description>I would submit a different argument. That allowing the license terms to be changed as well as the description already sacrifices the benefit of a uniform license set.&lt;br&gt;&lt;br&gt;One of the perks of CC is not only consistent naming, but that we know my CC-BY-SA license will be the same as every other CC-BY-SA license. With iCopyrght Creators, that isn&#039;t certain, one has to read the description and the license itself to be sure that they are following the license.&lt;br&gt;&lt;br&gt;The benefit of the standard license is already lost. One already has to read the full license text so I don&#039;t see how allowing title changes can hurt, but rather, only simplify the process of interpreting iCopyright license.&lt;br&gt;&lt;br&gt;As far as being too U.S.-centric goes, I agree. You need to include provisions for dealing with moral rights at least as that is something that exists almost everywhere else in the world.&lt;br&gt;&lt;br&gt;However, I also understand that you had to start somewhere and the U.S. was the most logical place...</description> <content:encoded><![CDATA[<p>I would submit a different argument. That allowing the license terms to be changed as well as the description already sacrifices the benefit of a uniform license set.</p><p>One of the perks of CC is not only consistent naming, but that we know my CC-BY-SA license will be the same as every other CC-BY-SA license. With iCopyrght Creators, that isn&#8217;t certain, one has to read the description and the license itself to be sure that they are following the license.</p><p>The benefit of the standard license is already lost. One already has to read the full license text so I don&#8217;t see how allowing title changes can hurt, but rather, only simplify the process of interpreting iCopyright license.</p><p>As far as being too U.S.-centric goes, I agree. You need to include provisions for dealing with moral rights at least as that is something that exists almost everywhere else in the world.</p><p>However, I also understand that you had to start somewhere and the U.S. was the most logical place&#8230;</p> ]]></content:encoded> </item> <item><title>By: Mike ODonnell</title><link>http://www.plagiarismtoday.com/2008/07/16/creating-a-custom-license/comment-page-1/#comment-121618</link> <dc:creator>Mike ODonnell</dc:creator> <pubDate>Wed, 16 Jul 2008 23:56:39 +0000</pubDate> <guid
isPermaLink="false">http://www.plagiarismtoday.com/?p=1331#comment-121618</guid> <description>Interested to hear from you and your readers if giving creators the ability to change the titles as well as the descriptions, outweighs the possible downside of creating confusion among the general public (potential licensees). One of the nice things about Creative Commons is that it provides a standard (uniform) set of licenses.  That&#039;s why you can change the descriptions, but not the titles in (C)reators. The other shortcomings are duly noted and slated for fix in the next release. &lt;br&gt;&lt;br&gt;(C)reators certainly needs to provide additional templates for Terms of Use. It was rightly slammed by beta testers in Canada for being to U.S. centric. Even though creators can edit the terms, they should have valid templates to begin with, depending upon their residence and needs. This blog also points out the need for better documentation! Thank you, Jonathan. We are learning from beta testers like you who are putting the app through its paces.</description> <content:encoded><![CDATA[<p>Interested to hear from you and your readers if giving creators the ability to change the titles as well as the descriptions, outweighs the possible downside of creating confusion among the general public (potential licensees). One of the nice things about Creative Commons is that it provides a standard (uniform) set of licenses.  That&#8217;s why you can change the descriptions, but not the titles in (C)reators. The other shortcomings are duly noted and slated for fix in the next release.</p><p>(C)reators certainly needs to provide additional templates for Terms of Use. It was rightly slammed by beta testers in Canada for being to U.S. centric. Even though creators can edit the terms, they should have valid templates to begin with, depending upon their residence and needs. This blog also points out the need for better documentation! Thank you, Jonathan. We are learning from beta testers like you who are putting the app through its paces.</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (user agent is rejected)
Database Caching 1/15 queries in 0.017 seconds using disk
Content Delivery Network via Amazon Web Services: CloudFront: files.plagiarismtoday.com

Served from: www.plagiarismtoday.com @ 2010-03-21 10:37:52 -->