<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="b2evolution/2.4.2" -->
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>shimenawa - Latest comments on cd /public</title>
		<link>http://blogs.lib.berkeley.edu/shimenawa.php?disp=comments</link>
		<description></description>
		<language>en-US</language>
		<docs>http://backend.userland.com/rss</docs>
		<admin:generatorAgent rdf:resource="http://b2evolution.net/?v=2.4.2"/>
		<ttl>60</ttl>
				<item>
			<title>In response to: cd /public</title>
			<pubDate>Tue, 21 Oct 2008 22:49:04 +0000</pubDate>
			<dc:creator>pbrantley [Member]</dc:creator>
			<guid isPermaLink="false">c75083@http://blogs.lib.berkeley.edu/</guid>
			<description>Eric -&lt;br /&gt;
&lt;br /&gt;
This is fantastic!  I'm delighted. &lt;br /&gt;
&lt;br /&gt;
Re: placement on the url, the idea only makes sense if it is an upper level /public link -- the concept being that a casual browser, or a &quot;stupid&quot; machine interface, should only have to look in one place for the content.</description>
			<content:encoded><![CDATA[Eric -<br />
<br />
This is fantastic!  I'm delighted. <br />
<br />
Re: placement on the url, the idea only makes sense if it is an upper level /public link -- the concept being that a casual browser, or a "stupid" machine interface, should only have to look in one place for the content.]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/10/10/cd-public#c75083</link>
		</item>
				<item>
			<title>In response to: cd /public</title>
			<pubDate>Tue, 21 Oct 2008 21:58:42 +0000</pubDate>
			<dc:creator>Eric Rumsey [Visitor]</dc:creator>
			<guid isPermaLink="false">c75082@http://blogs.lib.berkeley.edu/</guid>
			<description>Thanks for the idea -- We've just started to implement it -- See public domain medical pictures at : http://www.lib.uiowa.edu/hardin/md/gallery2public.html&lt;br /&gt;
&lt;br /&gt;
We have not yet made a /public location for these links -- Is it important to have /public as a root directory at the top level, or would it work to have it further down as a secondary directory?</description>
			<content:encoded><![CDATA[Thanks for the idea -- We've just started to implement it -- See public domain medical pictures at : http://www.lib.uiowa.edu/hardin/md/gallery2public.html<br />
<br />
We have not yet made a /public location for these links -- Is it important to have /public as a root directory at the top level, or would it work to have it further down as a secondary directory?]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/10/10/cd-public#c75082</link>
		</item>
				<item>
			<title>In response to: cd /public</title>
			<pubDate>Sat, 11 Oct 2008 13:48:52 +0000</pubDate>
			<dc:creator>Erin [Visitor]</dc:creator>
			<guid isPermaLink="false">c75070@http://blogs.lib.berkeley.edu/</guid>
			<description>What a beautiful, simple, useful, tremendously great idea!</description>
			<content:encoded><![CDATA[What a beautiful, simple, useful, tremendously great idea!]]></content:encoded>
			<link>http://blogs.lib.berkeley.edu/shimenawa.php/2008/10/10/cd-public#c75070</link>
		</item>
			</channel>
</rss>
