<?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 for The LexPublica Blog</title>
	<atom:link href="http://blog.lexpubli.ca/comments/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.lexpubli.ca</link>
	<description>LexPublica: Open Sourcing the Law</description>
	<lastBuildDate>Tue, 19 Jan 2010 20:20:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>Comment on The First of Many Employment Contracts by Kim</title>
		<link>http://blog.lexpubli.ca/the-first-of-many-employment-contracts/comment-page-1#comment-299</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Tue, 19 Jan 2010 20:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=227#comment-299</guid>
		<description>Thanks for your comment, Kevin, and my apologies for taking so long to approve it and reply.

We, too, would like to be able to annotate templates, and it&#039;s on the list of features we&#039;ll eventually develop for the site. For now, please be sure to consult the Guidelines for each contract, as they should address some of your questions.

No contract will be appropriate for everyone or for all situations, so we hope people will consult a lawyer to edit them as needed.

We likely won&#039;t pursue a forms approach (Creative Commons has a far simpler list of options than even just one type of contract we hope to cover would require), but I&#039;ve made note of your feedback and we&#039;ll see how things evolve.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Kevin, and my apologies for taking so long to approve it and reply.</p>
<p>We, too, would like to be able to annotate templates, and it&#8217;s on the list of features we&#8217;ll eventually develop for the site. For now, please be sure to consult the Guidelines for each contract, as they should address some of your questions.</p>
<p>No contract will be appropriate for everyone or for all situations, so we hope people will consult a lawyer to edit them as needed.</p>
<p>We likely won&#8217;t pursue a forms approach (Creative Commons has a far simpler list of options than even just one type of contract we hope to cover would require), but I&#8217;ve made note of your feedback and we&#8217;ll see how things evolve.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The First of Many Employment Contracts by Kevin McArthur</title>
		<link>http://blog.lexpubli.ca/the-first-of-many-employment-contracts/comment-page-1#comment-297</link>
		<dc:creator>Kevin McArthur</dc:creator>
		<pubDate>Thu, 14 Jan 2010 01:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=227#comment-297</guid>
		<description>This projects is a really awesome idea, but it would be nice if the templates were annotated more for both parties to the agreement. Since it&#039;s likely that neither party using these agreements will seek council, there should be more explanation of what is being traded.

This employment contract for example, waives all moral rights, which may be appropriate for some, but for others may go way, way, too far.

I&#039;d also put a feature request in for a more web 2.0-ish forms approach, where the contract is built from a series of checkboxes of inclusions, with each option clearly explained. Something along the lines of how the creative commons license drafting service works. 

Good luck with it guys!</description>
		<content:encoded><![CDATA[<p>This projects is a really awesome idea, but it would be nice if the templates were annotated more for both parties to the agreement. Since it&#8217;s likely that neither party using these agreements will seek council, there should be more explanation of what is being traded.</p>
<p>This employment contract for example, waives all moral rights, which may be appropriate for some, but for others may go way, way, too far.</p>
<p>I&#8217;d also put a feature request in for a more web 2.0-ish forms approach, where the contract is built from a series of checkboxes of inclusions, with each option clearly explained. Something along the lines of how the creative commons license drafting service works. </p>
<p>Good luck with it guys!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The First of Many Employment Contracts by uberVU - social comments</title>
		<link>http://blog.lexpubli.ca/the-first-of-many-employment-contracts/comment-page-1#comment-296</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 08 Jan 2010 00:20:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=227#comment-296</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by cvrepublic: The First of Many Employment Contracts &#124; The LexPublica Blog http://url4.eu/14XB1...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by cvrepublic: The First of Many Employment Contracts | The LexPublica Blog <a href="http://url4.eu/14XB1.." rel="nofollow">http://url4.eu/14XB1..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We&#8217;re Hiring! Seeking Technical Lead by uberVU - social comments</title>
		<link>http://blog.lexpubli.ca/were-hiring-seeking-technical-lead/comment-page-1#comment-293</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Wed, 23 Dec 2009 01:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=219#comment-293</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by LexPublica: We&#039;re hiring a technical lead! And we&#039;re fun to work with. (Please tell all your developer friends!)  http://ow.ly/OKTV ^kw...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by LexPublica: We&#8217;re hiring a technical lead! And we&#8217;re fun to work with. (Please tell all your developer friends!)  <a href="http://ow.ly/OKTV" rel="nofollow">http://ow.ly/OKTV</a> ^kw&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hereby: We Need a Verdict by Anon</title>
		<link>http://blog.lexpubli.ca/hereby-we-need-a-verdict/comment-page-1#comment-291</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Thu, 17 Dec 2009 08:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=210#comment-291</guid>
		<description>Hi - &quot;Hereby&quot; is archaic legal language and, in the context you&#039;ve posted above, entirely redundant. Ditch it I reckon.</description>
		<content:encoded><![CDATA[<p>Hi &#8211; &#8220;Hereby&#8221; is archaic legal language and, in the context you&#8217;ve posted above, entirely redundant. Ditch it I reckon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Newsletter and New Look by Kim Werker</title>
		<link>http://blog.lexpubli.ca/new-newsletter-and-new-look/comment-page-1#comment-287</link>
		<dc:creator>Kim Werker</dc:creator>
		<pubDate>Wed, 18 Nov 2009 18:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=206#comment-287</guid>
		<description>Thanks for asking, Jason. You should be a-ok sticking with the blog RSS. We&#039;ll likely repeat ourselves quite a bit in the newsletter, at least at this early stage. We&#039;ll be launching a separate newsletter for people who are interested in contributing to LP; if that&#039;s you, please do subscribe to that newsletter as it&#039;ll contain unique content.</description>
		<content:encoded><![CDATA[<p>Thanks for asking, Jason. You should be a-ok sticking with the blog RSS. We&#8217;ll likely repeat ourselves quite a bit in the newsletter, at least at this early stage. We&#8217;ll be launching a separate newsletter for people who are interested in contributing to LP; if that&#8217;s you, please do subscribe to that newsletter as it&#8217;ll contain unique content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Newsletter and New Look by Jason McLaren</title>
		<link>http://blog.lexpubli.ca/new-newsletter-and-new-look/comment-page-1#comment-286</link>
		<dc:creator>Jason McLaren</dc:creator>
		<pubDate>Wed, 18 Nov 2009 03:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=206#comment-286</guid>
		<description>Will there be newsletter content that doesn&#039;t appear on this blog?  I&#039;d prefer to subscribe to an rss feed than an email newsletter.</description>
		<content:encoded><![CDATA[<p>Will there be newsletter content that doesn&#8217;t appear on this blog?  I&#8217;d prefer to subscribe to an rss feed than an email newsletter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on LexPublica in Stereo by uberVU - social comments</title>
		<link>http://blog.lexpubli.ca/lexpublica-in-stereo/comment-page-1#comment-284</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 30 Oct 2009 22:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=195#comment-284</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by Martin Ertl: Missed @LexPublica on CBC Early Edition yesterday? We&#039;ve got a clip of the radio interview at http://bit.ly/14R181...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by Martin Ertl: Missed @LexPublica on CBC Early Edition yesterday? We&#8217;ve got a clip of the radio interview at <a href="http://bit.ly/14R181.." rel="nofollow">http://bit.ly/14R181..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Not Problems: Opportunities! by JOHN H GOODWIN</title>
		<link>http://blog.lexpubli.ca/not-problems-opportunities/comment-page-1#comment-280</link>
		<dc:creator>JOHN H GOODWIN</dc:creator>
		<pubDate>Thu, 15 Oct 2009 16:54:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=176#comment-280</guid>
		<description>Indeed so. If there is a concern about loss of productivity or expressing bad attitudes, that is best addressed by hiring the right people, getting them in the right roles, getting understanding and &quot;buy in&quot; to the companies focus and strategies, and empowering them to use their best skills to make their contribution. If it is just about &quot;rules&quot;, how can that be a productive (and enjoyable) environment?  Why, in a survey, do 80% of employees feel that their gifts are not being sufficiently utilized at work?  Why are 20% of employees openly hostile to their employer?</description>
		<content:encoded><![CDATA[<p>Indeed so. If there is a concern about loss of productivity or expressing bad attitudes, that is best addressed by hiring the right people, getting them in the right roles, getting understanding and &#8220;buy in&#8221; to the companies focus and strategies, and empowering them to use their best skills to make their contribution. If it is just about &#8220;rules&#8221;, how can that be a productive (and enjoyable) environment?  Why, in a survey, do 80% of employees feel that their gifts are not being sufficiently utilized at work?  Why are 20% of employees openly hostile to their employer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on CBA says &#8220;Advertise.&#8221; We say &#8220;Engage.&#8221; by Kim Werker</title>
		<link>http://blog.lexpubli.ca/cba-says-advertise-we-say-engage/comment-page-1#comment-276</link>
		<dc:creator>Kim Werker</dc:creator>
		<pubDate>Thu, 01 Oct 2009 22:44:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.lexpubli.ca/?p=162#comment-276</guid>
		<description>Great point! Thanks, Emma.</description>
		<content:encoded><![CDATA[<p>Great point! Thanks, Emma.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
