<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Library 2.0 Perils</title>
	<link>http://www.blyberg.net/2005/11/07/library-20-perils/</link>
	<description>A library-geek blog</description>
	<pubDate>Wed, 20 Aug 2008 02:09:12 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Library 2.0 Roundup &#171; Life as I Know It</title>
		<link>http://www.blyberg.net/2005/11/07/library-20-perils/#comment-9676</link>
		<dc:creator>Library 2.0 Roundup &#171; Life as I Know It</dc:creator>
		<pubDate>Tue, 24 Oct 2006 01:56:39 +0000</pubDate>
		<guid>http://www.blyberg.net/2005/11/07/library-20-perils/#comment-9676</guid>
		<description>[...] Library 2.0 perils - posted on November 7, 2005. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Library 2.0 perils - posted on November 7, 2005. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Van Garderen</title>
		<link>http://www.blyberg.net/2005/11/07/library-20-perils/#comment-24</link>
		<dc:creator>Peter Van Garderen</dc:creator>
		<pubDate>Fri, 11 Nov 2005 00:56:43 +0000</pubDate>
		<guid>http://www.blyberg.net/2005/11/07/library-20-perils/#comment-24</guid>
		<description>Hey John,

Right on! yes, it is going to be friggin' sweet!! 

I ran into your post as a trackback from Dion Hinchcliff's article (how Web 2.0 :-) which I also referenced in a recent blog post: http://archivemati.ca/2005/11/10/what-is-web-20/.

I am coming at this from the perspective of archival insitutions which also has its fair share of dinosaur applications and too-little-too-late 'hot new' features.

As part of my research, I do plan to build a open source prototype from the ground up sometime in the next few months. Of course, library and archives information systems have always been closely related. They could very easily be the same systems with some minor allowances for metadata and what many archivists consider to be the terminally-unique requirement for multi-level description. 

Anyway, let me know if you get started with anything. Maybe an opportunity to collaborate...
(I am leaning towards making the plunge to the uber-hyped but appealing Ruby on Rails as my development platform)</description>
		<content:encoded><![CDATA[<p>Hey John,</p>
<p>Right on! yes, it is going to be friggin&#8217; sweet!! </p>
<p>I ran into your post as a trackback from Dion Hinchcliff&#8217;s article (how Web 2.0 <img src='http://www.blyberg.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> which I also referenced in a recent blog post: <a href="http://archivemati.ca/2005/11/10/what-is-web-20/." rel="nofollow">http://archivemati.ca/2005/11/10/what-is-web-20/.</a></p>
<p>I am coming at this from the perspective of archival insitutions which also has its fair share of dinosaur applications and too-little-too-late &#8216;hot new&#8217; features.</p>
<p>As part of my research, I do plan to build a open source prototype from the ground up sometime in the next few months. Of course, library and archives information systems have always been closely related. They could very easily be the same systems with some minor allowances for metadata and what many archivists consider to be the terminally-unique requirement for multi-level description. </p>
<p>Anyway, let me know if you get started with anything. Maybe an opportunity to collaborate&#8230;<br />
(I am leaning towards making the plunge to the uber-hyped but appealing Ruby on Rails as my development platform)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
