<?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: Who Owns Your Emails, Blog Posts, or FaceBook Pages? How About You?</title>
	<atom:link href="http://www.concurringopinions.com/archives/2008/03/who_owns_your_e.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.concurringopinions.com/archives/2008/03/who_owns_your_e.html</link>
	<description>The Law, the Universe, and Everything</description>
	<lastBuildDate>Sat, 21 Nov 2009 21:19:19 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Deven</title>
		<link>http://www.concurringopinions.com/archives/2008/03/who_owns_your_e.html/comment-page-1#comment-49998</link>
		<dc:creator>Deven</dc:creator>
		<pubDate>Sun, 09 Mar 2008 21:07:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2008/03/who-owns-your-emails-blog-posts-or-facebook-pages-how-about-you.html#comment-49998</guid>
		<description>Matt

Good to hear from you even in snark master mode. Still you make a fine point. That was a remnant from the working paper status where I think it makes sense. I will update the version on there.

One thing some folks have been discussing is when does SSRN work well for working papers. Put differently, is SSRN becoming a place where only fully finished pieces are circulated?

Deven

</description>
		<content:encoded><![CDATA[<p>Matt</p>
<p>Good to hear from you even in snark master mode. Still you make a fine point. That was a remnant from the working paper status where I think it makes sense. I will update the version on there.</p>
<p>One thing some folks have been discussing is when does SSRN work well for working papers. Put differently, is SSRN becoming a place where only fully finished pieces are circulated?</p>
<p>Deven</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Sag</title>
		<link>http://www.concurringopinions.com/archives/2008/03/who_owns_your_e.html/comment-page-1#comment-49997</link>
		<dc:creator>Matthew Sag</dc:creator>
		<pubDate>Sun, 09 Mar 2008 16:29:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2008/03/who-owns-your-emails-blog-posts-or-facebook-pages-how-about-you.html#comment-49997</guid>
		<description>Deven,

I began reading your paper after downloading it from ssrn, but when I reached the legend proclaiming &quot;DRAFT – DO NOT CITE OR CIRCULATE WITHOUT PERMISSION&quot; I decided to stop. It was, I concluded, better to remain ignorant than to risk obtaining knowledge that I could not even cite too in my own scholarship.

These legends are the academic equivalent of the Major League Baseball warnings - and they make about as much sense.

If I had been able to read you article I might now observe some irony between your general theme and the application of the odious &quot;DRAFT – DO NOT CITE OR CIRCULATE WITHOUT PERMISSION&quot;. However, as I feared such an observation might amount to a citation, I decided to merely assume the contents of your paper and write this comment without the benefit of having read the paper.

Please feel free to cite and circulate this comment.

Matthew Sag

</description>
		<content:encoded><![CDATA[<p>Deven,</p>
<p>I began reading your paper after downloading it from ssrn, but when I reached the legend proclaiming &#8220;DRAFT – DO NOT CITE OR CIRCULATE WITHOUT PERMISSION&#8221; I decided to stop. It was, I concluded, better to remain ignorant than to risk obtaining knowledge that I could not even cite too in my own scholarship.</p>
<p>These legends are the academic equivalent of the Major League Baseball warnings &#8211; and they make about as much sense.</p>
<p>If I had been able to read you article I might now observe some irony between your general theme and the application of the odious &#8220;DRAFT – DO NOT CITE OR CIRCULATE WITHOUT PERMISSION&#8221;. However, as I feared such an observation might amount to a citation, I decided to merely assume the contents of your paper and write this comment without the benefit of having read the paper.</p>
<p>Please feel free to cite and circulate this comment.</p>
<p>Matthew Sag</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deven</title>
		<link>http://www.concurringopinions.com/archives/2008/03/who_owns_your_e.html/comment-page-1#comment-49996</link>
		<dc:creator>Deven</dc:creator>
		<pubDate>Fri, 07 Mar 2008 21:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2008/03/who-owns-your-emails-blog-posts-or-facebook-pages-how-about-you.html#comment-49996</guid>
		<description>Eric

Deadly accurate observations. The paper explicitly carves out some of the virtual world issues though those are implicated. Ownership has the problems you note. Part of the goal is to look at the property arguments try to sort out a reasonable way to limit the interests in intangibles. I think you are getting at one of the key questions in the paper regarding heirs&#039; access. Take a read as I would love to know what you think about my approach. But it seems that the author should be able to choose whether to preserve or destroy the thing (I came at as preservation but Lior Strahilevitz&#039;s Right to Destroy is almost a mirror argument from the other view, and I show that in the paper). If the author wants to thing to go to the heirs, so be it. The system as it is does not seem to allow for that type of control. That is an error in my view.

</description>
		<content:encoded><![CDATA[<p>Eric</p>
<p>Deadly accurate observations. The paper explicitly carves out some of the virtual world issues though those are implicated. Ownership has the problems you note. Part of the goal is to look at the property arguments try to sort out a reasonable way to limit the interests in intangibles. I think you are getting at one of the key questions in the paper regarding heirs&#8217; access. Take a read as I would love to know what you think about my approach. But it seems that the author should be able to choose whether to preserve or destroy the thing (I came at as preservation but Lior Strahilevitz&#8217;s Right to Destroy is almost a mirror argument from the other view, and I show that in the paper). If the author wants to thing to go to the heirs, so be it. The system as it is does not seem to allow for that type of control. That is an error in my view.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Goldman</title>
		<link>http://www.concurringopinions.com/archives/2008/03/who_owns_your_e.html/comment-page-1#comment-49995</link>
		<dc:creator>Eric Goldman</dc:creator>
		<pubDate>Fri, 07 Mar 2008 21:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.solove.org/archives/2008/03/who-owns-your-emails-blog-posts-or-facebook-pages-how-about-you.html#comment-49995</guid>
		<description>This issue also arises in the context of virtual worlds.  Of course, the term &quot;ownership&quot; is squirrely here because it brings a set of assumptions and norms, not all of which may be intended.  The real challenge here is that even if the heirs own the copyrights in digital assets created by the decedent, they may not be able to get access to the actual bits.  But does access to the &quot;chattel&quot; necessarily need to follow from ownership of the intangibles stored therein?  Eric.

</description>
		<content:encoded><![CDATA[<p>This issue also arises in the context of virtual worlds.  Of course, the term &#8220;ownership&#8221; is squirrely here because it brings a set of assumptions and norms, not all of which may be intended.  The real challenge here is that even if the heirs own the copyrights in digital assets created by the decedent, they may not be able to get access to the actual bits.  But does access to the &#8220;chattel&#8221; necessarily need to follow from ownership of the intangibles stored therein?  Eric.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
