<?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: Breaking News:  Court Rules Against Freelancer Protections</title>
	<atom:link href="http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/feed/" rel="self" type="application/rss+xml" />
	<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/</link>
	<description>Tools and Trade Secrets for Aspiring Writers</description>
	<lastBuildDate>Mon, 08 Mar 2010 15:29:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom Colvin</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-11119</link>
		<dc:creator>Tom Colvin</dc:creator>
		<pubDate>Wed, 05 Dec 2007 14:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-11119</guid>
		<description>Writers Digest editor Maria Schneider in her blog The Writer&#039;s Perspective wrote yesterday about the copyright decision, with some useful detail and a couple of additional links.  She points out that it costs $45 per copyright.  Multiply that by every article we write?  Articles that might not earn much more than $45 in the first place?  This ruling may be very serious indeed for freelancers!  You can find her post at:


http://www.writersdigest.com/writersperspective/Is Copyright Now Necessary .aspx</description>
		<content:encoded><![CDATA[<p>Writers Digest editor Maria Schneider in her blog The Writer&#8217;s Perspective wrote yesterday about the copyright decision, with some useful detail and a couple of additional links.  She points out that it costs $45 per copyright.  Multiply that by every article we write?  Articles that might not earn much more than $45 in the first place?  This ruling may be very serious indeed for freelancers!  You can find her post at:</p>
<p><a href="http://www.writersdigest.com/writersperspective/Is" >http://www.writersdigest.com/writersperspective/Is</a> Copyright Now Necessary .aspx</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Colvin</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-9946</link>
		<dc:creator>Tom Colvin</dc:creator>
		<pubDate>Sat, 01 Dec 2007 22:16:29 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-9946</guid>
		<description>I finally found another posting about this decision at respected CNET:

http://www.news.com/Court-voids-deal-to-pay-freelancers-for-work-sent-to-Web/2100-1030_3-6220850.html
And here&#039;s some history from earlier on in the case:

http://freelancerights.blogspot.com/2007_03_01_archive.html

I have absolutely no idea how this ruling will impact Canadian writers, nor even where it goes from here for US freelancers.

In the process, I&#039;ve just realized that my Comments Box is not &quot;url friendly.&quot;  Does anyone know a Word Press comment plug-in that works better than this, preferably allowing a link, or at the very least wrapping the url text?

Tom</description>
		<content:encoded><![CDATA[<p>I finally found another posting about this decision at respected CNET:</p>
<p><a href="http://www.news.com/Court-voids-deal-to-pay-freelancers-for-work-sent-to-Web/2100-1030_3-6220850.html" >http://www.news.com/Court-voids-deal-to-pay-freelancers-for-work-sent-to-Web/2100-1030_3-6220850.html</a><br />
And here&#8217;s some history from earlier on in the case:</p>
<p><a href="http://freelancerights.blogspot.com/2007_03_01_archive.html" >http://freelancerights.blogspot.com/2007_03_01_archive.html</a></p>
<p>I have absolutely no idea how this ruling will impact Canadian writers, nor even where it goes from here for US freelancers.</p>
<p>In the process, I&#8217;ve just realized that my Comments Box is not &#8220;url friendly.&#8221;  Does anyone know a Word Press comment plug-in that works better than this, preferably allowing a link, or at the very least wrapping the url text?</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-9922</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 01 Dec 2007 20:18:54 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-9922</guid>
		<description>I am wondering how this will affect Canadian writer&#039;s.
I will have to look into this and our laws, but will this prove to be the same issue for Canadian copyrights?</description>
		<content:encoded><![CDATA[<p>I am wondering how this will affect Canadian writer&#8217;s.<br />
I will have to look into this and our laws, but will this prove to be the same issue for Canadian copyrights?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Freelance Writing Jobs - The Internet&#8217;s #1 Freelance Writer Community &#187; Blog Archive &#187; Weekend Link Love for December 1st, 2007</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-9896</link>
		<dc:creator>Freelance Writing Jobs - The Internet&#8217;s #1 Freelance Writer Community &#187; Blog Archive &#187; Weekend Link Love for December 1st, 2007</dc:creator>
		<pubDate>Sat, 01 Dec 2007 16:40:53 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-9896</guid>
		<description>[...] Breaking News: Court Rules Against Freelance Protection at Becoming a Writer Seriously. [...]</description>
		<content:encoded><![CDATA[<div style="">
<p>[...] Breaking News: Court Rules Against Freelance Protection at Becoming a Writer Seriously. [...]</p>
</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Colvin</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-9727</link>
		<dc:creator>Tom Colvin</dc:creator>
		<pubDate>Sat, 01 Dec 2007 02:49:26 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-9727</guid>
		<description>Jeremy, sorry about the broken link.  I&#039;ve revised my post accordingly -- with a note of irony.

Tom</description>
		<content:encoded><![CDATA[<p>Jeremy, sorry about the broken link.  I&#8217;ve revised my post accordingly &#8212; with a note of irony.</p>
<p>Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeanne Dininni</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-9642</link>
		<dc:creator>Jeanne Dininni</dc:creator>
		<pubDate>Fri, 30 Nov 2007 21:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-9642</guid>
		<description>Tom,

The worst part about this is that, for years, writers have  been lulled into a false sense of security by being told that their works were copyrighted the moment they created them--regardless of whether or not they decided to register them with the U.S. Copyright Office.  Looks as if we&#039;re now  beginning to see the limitations of such &quot;natural&quot; copyrights!

Thanks for this important info!
Jeanne</description>
		<content:encoded><![CDATA[<p>Tom,</p>
<p>The worst part about this is that, for years, writers have  been lulled into a false sense of security by being told that their works were copyrighted the moment they created them&#8211;regardless of whether or not they decided to register them with the U.S. Copyright Office.  Looks as if we&#8217;re now  beginning to see the limitations of such &#8220;natural&#8221; copyrights!</p>
<p>Thanks for this important info!<br />
Jeanne</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Osborne</title>
		<link>http://becoming-a-writer-seriously.com/wordpress/2007/12/01/breaking-news-court-rules-against-freelancer-protections/comment-page-1/#comment-9637</link>
		<dc:creator>Jeremy Osborne</dc:creator>
		<pubDate>Fri, 30 Nov 2007 20:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://becoming-a-writer-seriously.com/2007/12/01/breaking-news-court-rules-against-freelancer-protections/#comment-9637</guid>
		<description>Hi Tom,

It appears the link to the article is broken. I tried to find it in a search but couldn&#039;t. I wanted to read the article myself and then read the court report (if it was linked) before making any decisions about this.</description>
		<content:encoded><![CDATA[<p>Hi Tom,</p>
<p>It appears the link to the article is broken. I tried to find it in a search but couldn&#8217;t. I wanted to read the article myself and then read the court report (if it was linked) before making any decisions about this.<br />
<fieldset class="blogfollow">
<legend>Read more from Jeremy Osborne</legend>
<h2><a rel="external" href="http://jeremyosborne.com/2010/03/01/javascript-variable-declarations/">JavaScript Variable Declarations</a></h2>
<p>This one is for the JavaScript nerds. No suspense as I&#8217;ve included the answer below the question.<br />
NOTE: This is lame-ass, test code. Anyone who codes like this should be shot, or at least have [...]</p>
</fieldset>
]]></content:encoded>
	</item>
</channel>
</rss>
