<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Scripting News - Latest Comments in Future-safe archives (Scripting News)</title><link>http://scripting.disqus.com/</link><description></description><atom:link href="https://scripting.disqus.com/future_safe_archives_scripting_news/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 08 Jan 2011 17:38:59 -0000</lastBuildDate><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-126293413</link><description>&lt;p&gt;"None of us like to think of it, but truth is none of us are going to live forever. "&lt;/p&gt;&lt;p&gt;This is one of those comments that will come back to bite you. A bit like "640KB is enough for anyone." There is a very good probability that there are people alive today who will "live forever" or close enough that you can't tell the difference. Death is an artifice of evolution culling to make room for the next generation. It isn't necessary or mandatory. There are plenty of plants, animals, fungi and other life forms that are immortal. You could be too.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Walter</dc:creator><pubDate>Sat, 08 Jan 2011 17:38:59 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-126219305</link><description>&lt;p&gt;Check out this&lt;/p&gt;&lt;p&gt;E-ternally Your - The case for the development of a reliable repository for the preservation of personal digital objects&lt;/p&gt;&lt;p&gt;&lt;a href="http://explorer.cyberstreet.com/CET4970H-Peterson-Thesis.pdf" rel="nofollow noopener" target="_blank" title="http://explorer.cyberstreet.com/CET4970H-Peterson-Thesis.pdf"&gt;http://explorer.cyberstreet...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Walter Peterson</dc:creator><pubDate>Sat, 08 Jan 2011 14:22:15 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-33849</link><description>&lt;p&gt;Dave,&lt;/p&gt;&lt;p&gt;Really good to see you hammering on this problem.&lt;/p&gt;&lt;p&gt;Writing may be kinda solitary, but preservation has to be collaborative, and there are a lot of disparate efforts underway now to find solutions. There are a lot of subtle aspects to this, ranging from file formats, emulating applications, broken links to things outside the personal collection, and domain registration, to sustaining institutions over the long term.&lt;/p&gt;&lt;p&gt;Alfred de Grazia (who did computer based social network analysis in the early 1950s using punch cards) came up with an economic model he described at &lt;a href="http://www.grazian-archive.com/projects/archvpt.html" rel="nofollow noopener" target="_blank" title="http://www.grazian-archive.com/projects/archvpt.html"&gt;http://www.grazian-archive....&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;Cathy Marshall at Microsoft has done a lot of excellent working looking at user behavior, i.e. the human dimension, and how things really get lost. See Evaluating Personal Archiving Strategies for Internet-based Information at &lt;a href="http://arxiv.org/pdf/0704.3647.pdf" rel="nofollow noopener" target="_blank" title="arxiv.org/pdf/0704.3647.pdf"&gt;arxiv.org/pdf/0704.3647.pdf&lt;/a&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeff Ubois</dc:creator><pubDate>Wed, 12 Dec 2007 19:57:44 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32811</link><description>&lt;p&gt;Yeah, I agree. wget + long term storage for static pages, that would cover most things.  And put a pc or two in the bank vault loaded w/ software to view it (browsers of they day, media players, etc).  When we developed government and banking software, we archived the OS, compilers, everything needed to recreate the software, and put all that in escroe for the clients.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eric link</dc:creator><pubDate>Tue, 11 Dec 2007 18:27:58 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32686</link><description>&lt;p&gt;&lt;a href="http://PutPlace.com" rel="nofollow noopener" target="_blank" title="PutPlace.com"&gt;PutPlace.com&lt;/a&gt; my company is working on an OpenSource interface to S3 that gives a RESTful API to S3 with support for Hierarchical Storage, User Accessing Control, quotaing and caching. We also have some other tricks up our sleeves to insulate you from changes in the S3 T&amp;amp;Cs.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Joe</dc:creator><pubDate>Tue, 11 Dec 2007 16:55:20 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32678</link><description>&lt;p&gt;The really sad thing about post-life digital presence is there's already a perfectly good infrastructure in place to handle it: the Internet.  Barring the complete annihilation of mankind the 'Net likely isn't going away.  PC's will always be connected, as will servers, XBoxes, etc.  What someone needs to do is capitalize on the botnet business model: make software that's one part web server and one part BitTorrent, accessible lives broken up and stored across countless servers.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AndrewBurton</dc:creator><pubDate>Tue, 11 Dec 2007 16:50:01 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32465</link><description>&lt;p&gt;I think RSS and metaweblogapi are not a sufficiently abstract way to think about this. When you're gone, the things you want to preserve are no longer dynamic they are raw assets, they stop changing. Search indexing technology is much closer to the right algorithm to statically preserve your digital memory. You need:&lt;br&gt;1. A sufficient map of each of the entry points of your stuff.&lt;br&gt;2. A crawler which can scan each entry point deeply, without missing any assets&lt;br&gt;3. A proxy which caches the responses obtained by the crawler, and saves them in a resource structure which is accessible by the originating requests. The storage format should be standard, and portable.&lt;br&gt;4. A perpetual domain registrar which maps storage instances of the proxy cache format to web domains via the mapping from item 1.&lt;br&gt;5. A perpetual storage service.&lt;br&gt;6. A financial trust to keep 4 and 5 running (&lt;a href="http://archive.org?)" rel="nofollow noopener" target="_blank" title="archive.org?)"&gt;archive.org?)&lt;/a&gt; &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bryn</dc:creator><pubDate>Tue, 11 Dec 2007 14:15:42 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32458</link><description>&lt;p&gt;As Dave points out, &lt;a href="http://Archive.org" rel="nofollow noopener" target="_blank" title="Archive.org"&gt;Archive.org&lt;/a&gt; is incomplete.  There are various reasons for this, including the fact that some people don't want their sites archived because they loose control of their data, but that gives me an idea.&lt;/p&gt;&lt;p&gt;What if those who cared could communicate a policy to &lt;a href="http://archive.org" rel="nofollow noopener" target="_blank" title="archive.org"&gt;archive.org&lt;/a&gt;.  Maybe they could say "archive this, but don't make it publicly available for 5 years from the date you archived it.  Or, archive this, but "hide it from public view until 10 years after it disappears from the web."&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Erik S.</dc:creator><pubDate>Tue, 11 Dec 2007 14:12:10 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32407</link><description>&lt;p&gt;You have hit a nerve here. Can't there be a subscription service that we can order if we want to preserve our work? Or is there something we can will to our chiidren?  My sites are hosted by a friend, and I think my daughters would pay to preserve them the way a gravesite is now preserved in a cemetary, because this is where my "essence" is.&lt;/p&gt;&lt;p&gt;Interestingly enough, the social networks may end up being a solution for this.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">hardaway</dc:creator><pubDate>Tue, 11 Dec 2007 13:40:57 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32368</link><description>&lt;p&gt;I just suggested the exact same thing to Oliver Starr....going out to collect and collate all of Marc's digital breadcrumbs to preserve them for his children and the grandchildren that will, sadly, never know him in person.&lt;/p&gt;&lt;p&gt;--Steve&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steve B.</dc:creator><pubDate>Tue, 11 Dec 2007 13:11:32 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32203</link><description>&lt;p&gt;It would make sense to involve trained archivists in discussing this problem. Digital record preservation is a very important topic in the field at present. They may not develop the software-level solutions, but they have deep knowledge of and experience in not only the maintenance and organization of collections of documents in various forms and media, but also in dealing with legal and ethical issues arising.&lt;/p&gt;&lt;p&gt;These latter issues just as necessary to deal with as the technology side of things. For instance, even if a web archival system is entirely voluntary, should there be restrictions on the use of content? Should a formula of standard practices developed for the preservation of blogs and other websites for people who do not specify how their legacy should be maintained once they pass? Should family members have a say in what is or is not preserved?&lt;/p&gt;&lt;p&gt;On the technology and organization side of things, as people have begun to suggest, the issue of how web material should be preserved must be addressed. Should websites be maintained in a static or dynamic form as-is, i.e., maintaining the same URIs and preserving everything intact, without necessarily indicating that the site one is viewing is 'historical'? Is a particular degree of centralization or distribution of repositories desirable?&lt;/p&gt;&lt;p&gt;It is also worth considering drawbacks to what might become a de facto automatic archival system that follows an author's death. Should we take any measures to avoid extreme data clutter that could develop over the next century, or less, as hundreds of millions of new creators take to the web? What do people involved in the search engine business have to say? (Do they think that many fiscal quarters in advance?) Should we even care, or do we just let them adapt?&lt;br&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jeremyw</dc:creator><pubDate>Tue, 11 Dec 2007 10:56:05 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32056</link><description>&lt;p&gt;One piece of the pie is to nominate a (very) few formats as immortal. Those formats would be "kept alive" by folks going forward so future generations will be able to access the information we create now. Certainly no one will be able to read my old ClarisWorks docs in fifty years (most can't read them today). But there is hope for reading that same document in pdf (maybe).&lt;/p&gt;&lt;p&gt;These formats should not be moving targets. They need to be stable and easy to deal with.&lt;/p&gt;&lt;p&gt;We'll will need to update the list - certainly the current pdf format can't hold future holographic data (or even modern video). But this process shouldn't happen too quickly. Maybe a 10 or 20 year time frame for  adding a new format would be appropriate.&lt;/p&gt;&lt;p&gt;And obviously we need open formats with multiple open source readers available.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">michael</dc:creator><pubDate>Tue, 11 Dec 2007 08:30:45 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-32034</link><description>&lt;p&gt;Thought the same things myself many a time, storage mediums that rely on advanced technology (well, more advanced than acid free paper or stone tablets) tend to be flaky to start with, remember micro-fiche?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bowenmark</dc:creator><pubDate>Tue, 11 Dec 2007 08:11:24 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31969</link><description>&lt;p&gt;You've hit on the major problem with web-based work -- it needs constant attention and a team to watch over it in perpetuity.&lt;/p&gt;&lt;p&gt;Books require no attention, except a decent fire-safe environment. Your work would be much more likely to survive if you have it printed in book form and donate copies to a wide spread of major libraries : Congress, British Library etc.&lt;/p&gt;&lt;p&gt;I doubt Amazon, Google etc. will be around in 100 years, but there's a very strong chance the libraries will.&lt;/p&gt;&lt;p&gt;What keeps the great writers alive and in print, of course, is public demand. Without that, anyone's work is doomed. The best we can do is to give it a chance by putting it in a place of assured safety -- books in libraries.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Evans (Syntagma)</dc:creator><pubDate>Tue, 11 Dec 2007 06:13:39 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31932</link><description>&lt;p&gt;Dave, you are spot on. I made a post about this a while back and re-entered it due to your post.&lt;/p&gt;&lt;p&gt;"The dead web - Google + &lt;a href="http://Archive.org?" rel="nofollow noopener" target="_blank" title="Archive.org?"&gt;Archive.org?&lt;/a&gt; "&lt;/p&gt;&lt;p&gt;&lt;a href="http://tinyurl.com/2jdnmu" rel="nofollow noopener" target="_blank" title="http://tinyurl.com/2jdnmu"&gt;http://tinyurl.com/2jdnmu&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Steven Livingstone</dc:creator><pubDate>Tue, 11 Dec 2007 04:08:08 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31895</link><description>&lt;p&gt;my plan is to grab things like twitter from the RSS feed from the site and again publish to my blogging engine via metaweblog api.  from there i'll push to a more permanent store.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeff Sandquist</dc:creator><pubDate>Tue, 11 Dec 2007 02:13:09 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31890</link><description>&lt;p&gt;the piece I need to get this to the next level is a reblogger tool.  I need something that will take an RSS feed and republish it via the metaweblogapi.&lt;/p&gt;&lt;p&gt;with this i can take my posted items from facebook, my items in my flickr feed, etc and publish to blog store.  after that I'll look to pushing to S3 or maybe an MSN space too. ;-)&lt;/p&gt;&lt;p&gt;anyone know of a tool or a service I can use to do this?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jeff Sandquist</dc:creator><pubDate>Tue, 11 Dec 2007 02:04:22 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31889</link><description>&lt;p&gt;How about your blog in a nice, long lasting, book form?  You'd lose a lot of the interactivity of a site, but maybe keep at least some of the content.&lt;/p&gt;&lt;p&gt;Looks like there are some folks doing something like that already (&lt;a href="http://blurb.com" rel="nofollow noopener" target="_blank" title="blurb.com"&gt;blurb.com&lt;/a&gt;, I don't know anything about them.)&lt;/p&gt;&lt;p&gt;I have 5 years worth of posts and scraped it into a nice big file, that's a bit of a hairball...now what?&lt;/p&gt;&lt;p&gt;Excellent topic&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Norris</dc:creator><pubDate>Tue, 11 Dec 2007 02:04:07 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31887</link><description>&lt;p&gt;I was just asking on Twitter (bonus, "perfect" twit!):&lt;/p&gt;&lt;p&gt;Why not host your content on big companies' free services? They're likely around for a while and incented to keep your stuff up.&lt;/p&gt;&lt;p&gt;I don’t get the $ argument. Why do publishers still print Shakespeare books? Because people still buy them.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Kennish</dc:creator><pubDate>Tue, 11 Dec 2007 02:02:57 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31881</link><description>&lt;p&gt;I've been thinking about this for the past few weeks after I was disgusted to hear the story of Australian "journalists" using facebook images of a soldier that was killed in Afghanistan for their story. &lt;br&gt;So therefore automated dead man's switch type scenarios don't work because they take too long. Some form of Escrow service that you can keep updated and give access to a few select friend or family members would be good, along with some basic instructions, such as "take down flickr immediately" or "keep my blog going as a memorial" or something to that effect. &lt;br&gt;But even that doesn't solve the problem of way long term storage of things of historical significance. The National Library of Australia has some websites they are archiving as significant resources see &lt;a href="http://pandora.nla.gov.au/about.html" rel="nofollow noopener" target="_blank" title="http://pandora.nla.gov.au/about.html"&gt;http://pandora.nla.gov.au/a...&lt;/a&gt; but even that would be miniscule. &lt;br&gt;So I suppose at the moment it's up to each one of us individually to have a personal plan kept in place with a few trusted people that know about it. I like Jeff Sand's idea of the Memory Stick but I would like to see something available on the Web.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jodie Miners</dc:creator><pubDate>Tue, 11 Dec 2007 01:51:56 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31879</link><description>&lt;p&gt;This post takes me back to something I wrote back in 2004 about &lt;a href="http://Weblogs.com" rel="nofollow noopener" target="_blank" title="Weblogs.com"&gt;Weblogs.com&lt;/a&gt; , &lt;a href="http://MailToTheFuture.com" rel="nofollow noopener" target="_blank" title="MailToTheFuture.com"&gt;MailToTheFuture.com&lt;/a&gt; and death.&lt;/p&gt;&lt;p&gt;It begins like this:&lt;/p&gt;&lt;p&gt;"(To make things clear from the beginning, this piece is not about Dave Winer)&lt;/p&gt;&lt;p&gt;It's time to add "death" to our thinking about the Internet."&lt;/p&gt;&lt;p&gt;&lt;a href="http://info.org.il/english/mail_to_the_future_dot_com.html" rel="nofollow noopener" target="_blank" title="http://info.org.il/english/mail_to_the_future_dot_com.html"&gt;http://info.org.il/english/...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hanan Cohen</dc:creator><pubDate>Tue, 11 Dec 2007 01:44:39 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31873</link><description>&lt;p&gt;The more and more a toss this concept around in my head, I keep coming back to content being in hard-copy form. jauderho's point emphasizes just that. There's no way to guarantee that the information that you store digitally will still be accessible say, even tomorrow. Technology is constantly evolving, and 100 years from now, who's to say I'll still be able to open a RAW image?&lt;/p&gt;&lt;p&gt;As a photographer, I am thinking about preserving images that I take. Hard-copy works well for this. But as we all have encountered with attempting to digitize every bit of hard-copy information these days and become "paperless" in our lives, hard-copy information degrades with time. It's a catch-22 either way you go, for my situation.&lt;/p&gt;&lt;p&gt;On the topic of archiving content, such as &lt;a href="http://scripting.com" rel="nofollow noopener" target="_blank" title="scripting.com"&gt;scripting.com&lt;/a&gt;, I think you could digitally archive textual content relatively easily. But as Dave has already pointed out, who do you trust with that information? How long will a company/service/whatever be around? There's no guarantee.&lt;/p&gt;&lt;p&gt;You've definitely provoked thought in my mind; we all (those of us that wish to maintain some type of legacy after we've passed) have a problem that needs solved, and relatively quickly. There's no telling when our day will inevitably come.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Garrett Combs</dc:creator><pubDate>Tue, 11 Dec 2007 01:27:42 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31853</link><description>&lt;p&gt;This works if this is just content. It gets much much harder if you start thinking about how to preserve applications that power sites. For example, how would one save Twitters in perpetuity? &lt;a href="http://archive.org?" rel="nofollow noopener" target="_blank" title="archive.org?"&gt;archive.org?&lt;/a&gt; Google cache? Twitter? Some sort of snapshot to PDF?&lt;/p&gt;&lt;p&gt;Obviously this is not a problem just in the consumer space. In many industries, there are requirements to preserve information for 7 or more years. While it may be possible to preserve things at the byte level via tape backups, it is often impossible to retrieve because the software and hardware are obsolete and not available. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jauder Ho</dc:creator><pubDate>Tue, 11 Dec 2007 01:03:13 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31849</link><description>&lt;p&gt;Ooops, meant to say this is *not* the first FSA piece I've written.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Tue, 11 Dec 2007 00:59:41 -0000</pubDate></item><item><title>Re: Future-safe archives (Scripting News)</title><link>http://www.scripting.com/stories/2007/12/10/futuresafeArchives.html#comment-31848</link><description>&lt;p&gt;I promise you I have never gotten a response to one of these posts from any of those companies (this is the first FSA piece I've written). I don't think they're thinking that way, their interest is in monetizing, not preserving, despite what they say. I wouldn't support them monetizing my work, so they're probably not interested. I think we have to look to academia for a solution, and each of us should think in terms of creating a mini-endowment to support preserving our work (with other benefits to the organization receiving our largesse).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave</dc:creator><pubDate>Tue, 11 Dec 2007 00:59:10 -0000</pubDate></item></channel></rss>