﻿<?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: The fallacies of summary-only RSS feeds</title>
	<atom:link href="http://adrianshort.co.uk/2008/04/04/the-fallacies-of-summary-only-rss-feeds/feed/" rel="self" type="application/rss+xml" />
	<link>http://adrianshort.co.uk/2008/04/04/the-fallacies-of-summary-only-rss-feeds/</link>
	<description>Design, citizenship and the city</description>
	<lastBuildDate>Fri, 30 Jul 2010 20:36:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Paul Adasiak</title>
		<link>http://adrianshort.co.uk/2008/04/04/the-fallacies-of-summary-only-rss-feeds/comment-page-1/#comment-31</link>
		<dc:creator>Paul Adasiak</dc:creator>
		<pubDate>Fri, 06 Jun 2008 05:18:03 +0000</pubDate>
		<guid isPermaLink="false">http://adrianshort.co.uk/2008/04/04/47#comment-31</guid>
		<description>As a librarian, I respond strongly to the &quot;give readers easier access to your resources&quot; argument.  My colleagues and I talk all the time about how to get users to quality materials without making them jump through hoops.

At the same time, I rub elbows with archivists, one of whose primary principles is preserving the integrity of a collection: that is, you don&#039;t redact individual photos or documents merely because you find them offensive or irrelevant; rather, you house &lt;em&gt;collections&lt;/em&gt; relevant to your institution and let them speak for themselves.

Come to think of it, the rest of librarianship shares the principle of resource integrity.  We will usually not exclude one volume of a set because it seems less valuable or relevant than the other volumes.  Nor do we provide our patrons with multiple options to take the content of a book out of its context.  Surely, they are at liberty to photocopy or scan portions, but that happens only once they have the whole book in their hands and it&#039;s out of our control.  We recognize that authors (including publishers) have intent in presenting their materials in the way they do.  They seek a certain experience for their readers.

I also seek an experience for my readers.  Perhaps it is not the most graphically exciting experience; perhaps the links to further resources are not the best to be found on the Internet; perhaps the comments left by other readers are not the most insightful.  But the layout and the content are selected all the same, and the comments are solicited -- and they are all part of what I would like to share with my readers.  Granted, some may be using a cell phone or a personal digital assistant incapable of rendering content as well as a graphical browser; that is one reason I&#039;ve chosen WordPress, which publishes in XHTML readable by a number of non-graphical devices.

When you say, &quot;It’s more important that your material gets read than it gets read in the way that you dictate&quot;, I wonder if you employ a needless distinction between content and presentation.  To some degree, the presentation &lt;em&gt;is&lt;/em&gt; content, and anybody who strips it out by means of an aggregator is cheated of that content.  (One of my archivist colleagues, who reads my blog, actually refuses to use a feed aggregator, exactly because it strips the text of its intended context.)

All that said...  I&#039;m really not dogmatic about the integrity of my blog -- or anybody else&#039;s; I use Bloglines myself -- and could be persuaded in time.</description>
		<content:encoded><![CDATA[<p>As a librarian, I respond strongly to the &#8220;give readers easier access to your resources&#8221; argument.  My colleagues and I talk all the time about how to get users to quality materials without making them jump through hoops.</p>
<p>At the same time, I rub elbows with archivists, one of whose primary principles is preserving the integrity of a collection: that is, you don&#8217;t redact individual photos or documents merely because you find them offensive or irrelevant; rather, you house <em>collections</em> relevant to your institution and let them speak for themselves.</p>
<p>Come to think of it, the rest of librarianship shares the principle of resource integrity.  We will usually not exclude one volume of a set because it seems less valuable or relevant than the other volumes.  Nor do we provide our patrons with multiple options to take the content of a book out of its context.  Surely, they are at liberty to photocopy or scan portions, but that happens only once they have the whole book in their hands and it&#8217;s out of our control.  We recognize that authors (including publishers) have intent in presenting their materials in the way they do.  They seek a certain experience for their readers.</p>
<p>I also seek an experience for my readers.  Perhaps it is not the most graphically exciting experience; perhaps the links to further resources are not the best to be found on the Internet; perhaps the comments left by other readers are not the most insightful.  But the layout and the content are selected all the same, and the comments are solicited &#8212; and they are all part of what I would like to share with my readers.  Granted, some may be using a cell phone or a personal digital assistant incapable of rendering content as well as a graphical browser; that is one reason I&#8217;ve chosen WordPress, which publishes in XHTML readable by a number of non-graphical devices.</p>
<p>When you say, &#8220;It’s more important that your material gets read than it gets read in the way that you dictate&#8221;, I wonder if you employ a needless distinction between content and presentation.  To some degree, the presentation <em>is</em> content, and anybody who strips it out by means of an aggregator is cheated of that content.  (One of my archivist colleagues, who reads my blog, actually refuses to use a feed aggregator, exactly because it strips the text of its intended context.)</p>
<p>All that said&#8230;  I&#8217;m really not dogmatic about the integrity of my blog &#8212; or anybody else&#8217;s; I use Bloglines myself &#8212; and could be persuaded in time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.402 seconds -->
