<?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: Defining our new roles</title>
	<atom:link href="http://informationtakesover.co.uk/2006/04/defining-our-new-roles/feed/" rel="self" type="application/rss+xml" />
	<link>http://informationtakesover.co.uk/2006/04/defining-our-new-roles/</link>
	<description>Rocketing through library space...</description>
	<lastBuildDate>Thu, 16 Feb 2012 04:29:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Information Takes Over &#187; Blog Archive &#187; rebranding or repostioning - or both?</title>
		<link>http://informationtakesover.co.uk/2006/04/defining-our-new-roles/comment-page-1/#comment-3477</link>
		<dc:creator>Information Takes Over &#187; Blog Archive &#187; rebranding or repostioning - or both?</dc:creator>
		<pubDate>Thu, 04 May 2006 20:39:37 +0000</pubDate>
		<guid isPermaLink="false">http://informationtakesover.co.uk/archives/2006/04/29/defining-our-new-roles/#comment-3477</guid>
		<description>[...] I recently commented that there might be a danger in L2 applications making the library invisable. In this brave &#8216;two&#8217; world  , where our services are delivered seamlessly to users at a time and place that is convenient to them, the library is acting as a gateway to the content that the user really wants. [...]</description>
		<content:encoded><![CDATA[<p>[...] I recently commented that there might be a danger in L2 applications making the library invisable. In this brave &#8216;two&#8217; world  , where our services are delivered seamlessly to users at a time and place that is convenient to them, the library is acting as a gateway to the content that the user really wants. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

