<?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 Jordan Hatcher</title>
	<atom:link href="http://www.jordanhatcher.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jordanhatcher.com/blog</link>
	<description>intellectual property, technology, open licensing, law and strategy</description>
	<lastBuildDate>Sat, 21 May 2011 08:26:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on Norwegian Open Data License &#8211; draft now out by Pubblicata la nuova versione della Italian Open Data License</title>
		<link>http://www.jordanhatcher.com/blog/2011/norwegian-open-data-license-draft-now-out/comment-page-1/#comment-334</link>
		<dc:creator>Pubblicata la nuova versione della Italian Open Data License</dc:creator>
		<pubDate>Sat, 21 May 2011 08:26:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=446#comment-334</guid>
		<description>&lt;p&gt;[...] esempio, sulla falsariga della IODL, la Norvegia ha recentemente pubblicato una prima bozza della Norvegian Open Data License) in quanto fornisce alle Amministrazioni uno strumento valido ed affidabile con cui rendere [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] esempio, sulla falsariga della IODL, la Norvegia ha recentemente pubblicato una prima bozza della Norvegian Open Data License) in quanto fornisce alle Amministrazioni uno strumento valido ed affidabile con cui rendere [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Open Licenses vs Public Licenses by Norwegian Open Data License &#8211; draft now out</title>
		<link>http://www.jordanhatcher.com/blog/2010/open-licenses-vs-public-licenses/comment-page-1/#comment-281</link>
		<dc:creator>Norwegian Open Data License &#8211; draft now out</dc:creator>
		<pubDate>Thu, 07 Apr 2011 08:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=236#comment-281</guid>
		<description>&lt;p&gt;[...] for the specific notifications on personal data and similar issues; and the second an established public open data [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] for the specific notifications on personal data and similar issues; and the second an established public open data [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gender and contract drafting by Ken Adams</title>
		<link>http://www.jordanhatcher.com/blog/2011/gender-and-contract-drafting/comment-page-1/#comment-230</link>
		<dc:creator>Ken Adams</dc:creator>
		<pubDate>Fri, 11 Feb 2011 13:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=383#comment-230</guid>
		<description>&lt;p&gt;Jordan: This is an example of what I call &quot;provisions specifying drafting conventions.&quot; Most are redundant; this one is also clumsy.&lt;/p&gt;

&lt;p&gt;The idea is that if a contract uses &quot;he&quot; to refer generically to one of a group consisting of both men and women, the drafter doesn&#039;t want that provision applied only to the males in that group. But that&#039;s a very unlikely notion, so this kind of provision is usually found only in the more risk-averse contracts.&lt;/p&gt;

&lt;p&gt;Furthermore, this provision is overbroad. If you use &quot;she&quot; to refer specifically to a party who is a woman, why should that be construed also to mean &quot;he&quot;?&lt;/p&gt;

&lt;p&gt;But more to the point, contracts can, as you suggest, readily be drafted so as to be gender-neutral.&lt;/p&gt;

&lt;p&gt;Regarding &quot;neuter,&quot; I assume that&#039;s intended to refer to entities, and not hermaphrodites!&lt;/p&gt;

&lt;p&gt;This topic is currently on my mind, as I&#039;m revising a document-assembly template to cover all pronoun possibilities.&lt;/p&gt;

&lt;p&gt;Ken&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Jordan: This is an example of what I call &#8220;provisions specifying drafting conventions.&#8221; Most are redundant; this one is also clumsy.</p>

<p>The idea is that if a contract uses &#8220;he&#8221; to refer generically to one of a group consisting of both men and women, the drafter doesn&#8217;t want that provision applied only to the males in that group. But that&#8217;s a very unlikely notion, so this kind of provision is usually found only in the more risk-averse contracts.</p>

<p>Furthermore, this provision is overbroad. If you use &#8220;she&#8221; to refer specifically to a party who is a woman, why should that be construed also to mean &#8220;he&#8221;?</p>

<p>But more to the point, contracts can, as you suggest, readily be drafted so as to be gender-neutral.</p>

<p>Regarding &#8220;neuter,&#8221; I assume that&#8217;s intended to refer to entities, and not hermaphrodites!</p>

<p>This topic is currently on my mind, as I&#8217;m revising a document-assembly template to cover all pronoun possibilities.</p>

<p>Ken</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Public Domain Assertions versus Dedications by Posting over at jordanhatcher.com &#124; opencontentlawyer</title>
		<link>http://www.jordanhatcher.com/blog/2010/public-domain-assertions-versus-dedications/comment-page-1/#comment-111</link>
		<dc:creator>Posting over at jordanhatcher.com &#124; opencontentlawyer</dc:creator>
		<pubDate>Tue, 09 Nov 2010 07:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=270#comment-111</guid>
		<description>&lt;p&gt;[...] Public Domain Assertions versus Dedications * Open Licenses vs Public Licenses * CC&#8217;s Public Domain Mark versus the Open Access Data Mark [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Public Domain Assertions versus Dedications * Open Licenses vs Public Licenses * CC&#8217;s Public Domain Mark versus the Open Access Data Mark [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on The non-open Italian Open Data License by Glen Newton</title>
		<link>http://www.jordanhatcher.com/blog/2010/the-non-open-italian-open-data-license/comment-page-1/#comment-110</link>
		<dc:creator>Glen Newton</dc:creator>
		<pubDate>Tue, 09 Nov 2010 01:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=304#comment-110</guid>
		<description>&lt;p&gt;I&#039;ve blogged about similar issues with the non-open nature of the claimed open data licenses of a number of prominent Canadian cities: &lt;i&gt;&lt;a href=&quot;http://zzzoot.blogspot.com/2010/07/its-not-open-data-so-stop-calling-it.html&quot; rel=&quot;nofollow&quot;&gt;It&#039;s not Open Data, so stop calling it that...&lt;/a&gt;&lt;/i&gt;. In this case, the licenses allow the cities to arbitrarily and retroactively refuse access/use of the data of someone. As I point out here (&lt;i&gt;&lt;a href=&quot;http://zzzoot.blogspot.com/2010/08/what-is-open-gov-data-sunlight.html&quot; rel=&quot;nofollow&quot;&gt;What is Open Gov Data? The Sunlight Foundation: Ten Principles for Opening Up Government Information&lt;/a&gt;&lt;/i&gt;), these restrictions break the non-discrimination, licensing and permanence (they don&#039;t version their data or their licenses, &amp; don&#039;t tie these together) of the Sunlight Foundation&#039;s 10 Principles. Yet these cities are claiming that they are using Open licenses.&lt;/p&gt;

&lt;p&gt;Yes, we need to hold these institutions feet-to-the-fire with respect to their claims to openness and what their licenses actually define.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve blogged about similar issues with the non-open nature of the claimed open data licenses of a number of prominent Canadian cities: <i><a href="http://zzzoot.blogspot.com/2010/07/its-not-open-data-so-stop-calling-it.html" rel="nofollow">It&#8217;s not Open Data, so stop calling it that&#8230;</a></i>. In this case, the licenses allow the cities to arbitrarily and retroactively refuse access/use of the data of someone. As I point out here (<i><a href="http://zzzoot.blogspot.com/2010/08/what-is-open-gov-data-sunlight.html" rel="nofollow">What is Open Gov Data? The Sunlight Foundation: Ten Principles for Opening Up Government Information</a></i>), these restrictions break the non-discrimination, licensing and permanence (they don&#8217;t version their data or their licenses, &amp; don&#8217;t tie these together) of the Sunlight Foundation&#8217;s 10 Principles. Yet these cities are claiming that they are using Open licenses.</p>

<p>Yes, we need to hold these institutions feet-to-the-fire with respect to their claims to openness and what their licenses actually define.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Should we have fair use in the UK? by Andrew Rens</title>
		<link>http://www.jordanhatcher.com/blog/2010/should-we-have-fair-use-in-the-uk/comment-page-1/#comment-108</link>
		<dc:creator>Andrew Rens</dc:creator>
		<pubDate>Mon, 08 Nov 2010 12:27:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=297#comment-108</guid>
		<description>&lt;p&gt;I agree with alongside rather than instead of.
There is no good reason why a country should not have both specific provisions and general limitations.
I am from a fair dealing jurisdiction, but we need fair use because it helps to future proof a copyright law, allowing the development of new activities instead of just calcifying old ones. Its also a useful provision for impact litigation, especially class actions, which is a useful way for non traditional rights holders to organize.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I agree with alongside rather than instead of.
There is no good reason why a country should not have both specific provisions and general limitations.
I am from a fair dealing jurisdiction, but we need fair use because it helps to future proof a copyright law, allowing the development of new activities instead of just calcifying old ones. Its also a useful provision for impact litigation, especially class actions, which is a useful way for non traditional rights holders to organize.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Open Licenses vs Public Licenses by The non-open Italian Open Data License</title>
		<link>http://www.jordanhatcher.com/blog/2010/open-licenses-vs-public-licenses/comment-page-1/#comment-99</link>
		<dc:creator>The non-open Italian Open Data License</dc:creator>
		<pubDate>Fri, 05 Nov 2010 19:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=236#comment-99</guid>
		<description>&lt;p&gt;[...] public licenses is hard work, and the authors are to complimented for attempting it and for caring about open [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] public licenses is hard work, and the authors are to complimented for attempting it and for caring about open [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on SG for life: Price? One logo tattoo and some IP issues by Jordan Hatcher</title>
		<link>http://www.jordanhatcher.com/blog/2010/sg-for-life-price-one-logo-tattoo-and-some-ip-issues/comment-page-1/#comment-86</link>
		<dc:creator>Jordan Hatcher</dc:creator>
		<pubDate>Thu, 28 Oct 2010 17:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=275#comment-86</guid>
		<description>&lt;p&gt;Just a follow up:  &lt;a href=&quot;http://www.theregister.co.uk/2010/09/28/human_billboard/&quot; rel=&quot;nofollow&quot;&gt;Here&#039;s someone in Iowa that got a logo tattoo on their forehead&lt;/a&gt; and lost out on the offered compensation.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Just a follow up:  <a href="http://www.theregister.co.uk/2010/09/28/human_billboard/" rel="nofollow">Here&#8217;s someone in Iowa that got a logo tattoo on their forehead</a> and lost out on the offered compensation.</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on CC&#8217;s new Public Domain Mark by Public Domain Assertions versus Dedications</title>
		<link>http://www.jordanhatcher.com/blog/2010/ccs-new-public-domain-mark/comment-page-1/#comment-68</link>
		<dc:creator>Public Domain Assertions versus Dedications</dc:creator>
		<pubDate>Thu, 21 Oct 2010 12:08:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=265#comment-68</guid>
		<description>&lt;p&gt;[...] Jordan Hatcher intellectual property, technology, open licensing, law and strategy   Skip to content AboutEducationUT Law – University of Edinburgh JD/LLM programTeaching ExperiencePast sites and projectsLawyerCreditsLegalPrivacy PolicyIP policyIAALBIANYLPublicationsPresentationsOpen DataContactBlog       &#171; SCL Thames Valley: The use of &#8220;free&#8221; &#8211; Nov 17th CC&#8217;s new Public Domain Mark &#187; [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Jordan Hatcher intellectual property, technology, open licensing, law and strategy   Skip to content AboutEducationUT Law – University of Edinburgh JD/LLM programTeaching ExperiencePast sites and projectsLawyerCreditsLegalPrivacy PolicyIP policyIAALBIANYLPublicationsPresentationsOpen DataContactBlog       &laquo; SCL Thames Valley: The use of &#8220;free&#8221; &#8211; Nov 17th CC&#8217;s new Public Domain Mark &raquo; [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>Comment on Having fun with COPPA by Rosemary ONeill</title>
		<link>http://www.jordanhatcher.com/blog/2010/having-fun-with-coppa/comment-page-1/#comment-6</link>
		<dc:creator>Rosemary ONeill</dc:creator>
		<pubDate>Fri, 17 Sep 2010 02:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.jordanhatcher.com/?p=116#comment-6</guid>
		<description>&lt;p&gt;You&#039;re totally right about Threadless not being necessarily &quot;directed to children.&quot;  The reason I feel that they should not be tying COPPA to their birthdate request is not stemming from the law itself, it&#039;s from the way it has been interpreted and enforced.  Back when the rule first came about, my company worked with CARU and some of the other folks putting together the policy because we were developers of an online community software that had an age-check on the front end.  They specifically contacted us and told us that the age-check could not be &quot;explained&quot; to the person registering (regardless of whether the site was child-targeted or not). &lt;/p&gt;

&lt;p&gt;It is frustrating and confusing, and even as they review the law for a possible update, some of the changes they are contemplating will make it even more weird.  (I blogged about the updates recently: http://socialstrata.livecloud.com/displaycontent/content/170308749721367808) &lt;/p&gt;

&lt;p&gt;By the way, I&#039;m a huge fan of Threadless as well.  They&#039;re totally cool.  And I&#039;m subscribing to your blog as well, because I like your style :)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>You&#8217;re totally right about Threadless not being necessarily &#8220;directed to children.&#8221;  The reason I feel that they should not be tying COPPA to their birthdate request is not stemming from the law itself, it&#8217;s from the way it has been interpreted and enforced.  Back when the rule first came about, my company worked with CARU and some of the other folks putting together the policy because we were developers of an online community software that had an age-check on the front end.  They specifically contacted us and told us that the age-check could not be &#8220;explained&#8221; to the person registering (regardless of whether the site was child-targeted or not). </p>

<p>It is frustrating and confusing, and even as they review the law for a possible update, some of the changes they are contemplating will make it even more weird.  (I blogged about the updates recently: <a href="http://socialstrata.livecloud.com/displaycontent/content/170308749721367808" rel="nofollow">http://socialstrata.livecloud.com/displaycontent/content/170308749721367808</a>) </p>

<p>By the way, I&#8217;m a huge fan of Threadless as well.  They&#8217;re totally cool.  And I&#8217;m subscribing to your blog as well, because I like your style <img src='http://www.jordanhatcher.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>]]></content:encoded>
	</item>
</channel>
</rss>

