<?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 every writing team should have a written collaboration agreement. (part 1 of 3)</title>
	<atom:link href="http://theatrelawyer.com/2008/10/24/why-every-writing-team-should-have-a-written-collaboration-agreement-part-1-of-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://theatrelawyer.com/2008/10/24/why-every-writing-team-should-have-a-written-collaboration-agreement-part-1-of-3/</link>
	<description>News, Information and Insight from Gordon P. Firemark, theatrical attorney</description>
	<lastBuildDate>Mon, 14 Sep 2009 22:20:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: at TheatreLawyer.com: A bit about collaboration agreements &#124; Law Offices of Gordon P. Firemark - Entertainment Lawyers</title>
		<link>http://theatrelawyer.com/2008/10/24/why-every-writing-team-should-have-a-written-collaboration-agreement-part-1-of-3/comment-page-1/#comment-57</link>
		<dc:creator>at TheatreLawyer.com: A bit about collaboration agreements &#124; Law Offices of Gordon P. Firemark - Entertainment Lawyers</dc:creator>
		<pubDate>Fri, 24 Oct 2008 19:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://theatrelawyer.com/?p=87#comment-57</guid>
		<description>[...] just posted the first in a 3-part series of posts about the importance of Collaboration Agreements for writing and other creative teams.  See it on my other blog:  [...]</description>
		<content:encoded><![CDATA[<p>[...] just posted the first in a 3-part series of posts about the importance of Collaboration Agreements for writing and other creative teams.  See it on my other blog:  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
