<?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: On information overload</title>
	<atom:link href="http://issuesblog.com/2007/05/08/on-information-overload/feed/" rel="self" type="application/rss+xml" />
	<link>http://issuesblog.com/2007/05/08/on-information-overload/</link>
	<description>Blather on business, pontification on politics, &#038; mutterings on miscellanea</description>
	<lastBuildDate>Tue, 16 Mar 2010 03:49:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Michael Patton</title>
		<link>http://issuesblog.com/2007/05/08/on-information-overload/comment-page-1/#comment-17</link>
		<dc:creator>Michael Patton</dc:creator>
		<pubDate>Tue, 15 May 2007 03:27:36 +0000</pubDate>
		<guid isPermaLink="false">http://issuesblog.com/2007/05/08/on-information-overload/#comment-17</guid>
		<description>Thanks for your comment, sir, and I&#039;ll go have a deeper look at your paper. 

As is probably obvious, I&#039;m no fan of heavy-handed solutions, but if a solution&#039;s got to be heavy-handed (as some, sadly, must), it should at least have the ghost of a chance of working.

The addition of an expiry date to our files makes excellent conceptual sense, much the same as every calculus professor I ever had who used the accursed phrase &quot;...and therefore it follows...&quot;.

The problem is that it&#039;s far, far more than a small technical change. I&#039;ll spare you the details, because they&#039;re at best tertiary to the discussion, but the file systems in use today cannot be changed to allow data to simply disappear as of a date.

Now just watch - I&#039;m going to read your full paper, and I&#039;m giving even odds that you&#039;ll have addressed that by conceptualizing the solution far enough into the future, when most of us will be using file systems as yet unimagined, that what&#039;s impossible today will be trivial then.  

If so, please consider me to be abashed in advance.

The technical details are moot, of course, because what&#039;s important is your actual point: We have to confront the question of intelligent and reasonable data preservation. I couldn&#039;t agree more. Advances in the way we handle data can only be made if we&#039;ve confronted the issue, and I thank you for having caused me to do so.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, sir, and I&#8217;ll go have a deeper look at your paper. </p>
<p>As is probably obvious, I&#8217;m no fan of heavy-handed solutions, but if a solution&#8217;s got to be heavy-handed (as some, sadly, must), it should at least have the ghost of a chance of working.</p>
<p>The addition of an expiry date to our files makes excellent conceptual sense, much the same as every calculus professor I ever had who used the accursed phrase &#8220;&#8230;and therefore it follows&#8230;&#8221;.</p>
<p>The problem is that it&#8217;s far, far more than a small technical change. I&#8217;ll spare you the details, because they&#8217;re at best tertiary to the discussion, but the file systems in use today cannot be changed to allow data to simply disappear as of a date.</p>
<p>Now just watch &#8211; I&#8217;m going to read your full paper, and I&#8217;m giving even odds that you&#8217;ll have addressed that by conceptualizing the solution far enough into the future, when most of us will be using file systems as yet unimagined, that what&#8217;s impossible today will be trivial then.  </p>
<p>If so, please consider me to be abashed in advance.</p>
<p>The technical details are moot, of course, because what&#8217;s important is your actual point: We have to confront the question of intelligent and reasonable data preservation. I couldn&#8217;t agree more. Advances in the way we handle data can only be made if we&#8217;ve confronted the issue, and I thank you for having caused me to do so.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Viktor Mayer-Schoenberger</title>
		<link>http://issuesblog.com/2007/05/08/on-information-overload/comment-page-1/#comment-16</link>
		<dc:creator>Viktor Mayer-Schoenberger</dc:creator>
		<pubDate>Mon, 14 May 2007 22:58:25 +0000</pubDate>
		<guid isPermaLink="false">http://issuesblog.com/2007/05/08/on-information-overload/#comment-16</guid>
		<description>Any I thought that by referring to my law degrees as a &quot;bunch&quot; I had indicated enough... ;)

More seriously, in my paper (which is available online) I evaluate other more legal proposals and suggest - you may like this - that they are all too hevay handed. What I suggest, namely that basically we add expiry dates to ou files seems to me a very small technical change, but one that may subtly forc eus to confront the question of whether we want to preserve something and for how long mnore so than we do now. As I argue in the paper I try to keep the law as limited as possible. 

Hope that addresses some of your concerns...and yes, LSE taught me that...among other things,

VMS</description>
		<content:encoded><![CDATA[<p>Any I thought that by referring to my law degrees as a &#8220;bunch&#8221; I had indicated enough&#8230; <img src='http://issuesblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>More seriously, in my paper (which is available online) I evaluate other more legal proposals and suggest &#8211; you may like this &#8211; that they are all too hevay handed. What I suggest, namely that basically we add expiry dates to ou files seems to me a very small technical change, but one that may subtly forc eus to confront the question of whether we want to preserve something and for how long mnore so than we do now. As I argue in the paper I try to keep the law as limited as possible. </p>
<p>Hope that addresses some of your concerns&#8230;and yes, LSE taught me that&#8230;among other things,</p>
<p>VMS</p>
]]></content:encoded>
	</item>
</channel>
</rss>
