<?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: A refrain? A routine? A mechanism?</title>
	<atom:link href="http://freelyassociating.org/2006/07/a-refrain-a-routine-a-mechanism/feed/" rel="self" type="application/rss+xml" />
	<link>http://freelyassociating.org/2006/07/a-refrain-a-routine-a-mechanism/</link>
	<description></description>
	<lastBuildDate>Sat, 31 Dec 2011 16:16:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: brian</title>
		<link>http://freelyassociating.org/2006/07/a-refrain-a-routine-a-mechanism/comment-page-1/#comment-32</link>
		<dc:creator>brian</dc:creator>
		<pubDate>Tue, 25 Jul 2006 13:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://freelyassociating.org/?p=21#comment-32</guid>
		<description>Hi Nate. Glad you liked our/your latest offering. And you’re right about the thing-ness. The electronic version of any text is no match for the actual printed product with all its sensuous &lt;i&gt;dinglich&lt;/i&gt; qualities. Mmmm, smell that ink…&lt;br/&gt;&lt;br/&gt;Anyhoo, I’m not an expert on refrains, but I think your comments make sense. The union organiser model you describe has a clear agenda and possibly an outcome that’s only really visible to one party. And it’s not really open to modulation, which means that it’s not (on its own) a refrain, altho’ it could form part of one.&lt;br/&gt;&lt;br/&gt;And I love your bit about the relation between channels and flows. Damn you! I needed something that succinct a couple of days ago. Ah well...</description>
		<content:encoded><![CDATA[<p>Hi Nate. Glad you liked our/your latest offering. And you’re right about the thing-ness. The electronic version of any text is no match for the actual printed product with all its sensuous <i>dinglich</i> qualities. Mmmm, smell that ink…</p>
<p>Anyhoo, I’m not an expert on refrains, but I think your comments make sense. The union organiser model you describe has a clear agenda and possibly an outcome that’s only really visible to one party. And it’s not really open to modulation, which means that it’s not (on its own) a refrain, altho’ it could form part of one.</p>
<p>And I love your bit about the relation between channels and flows. Damn you! I needed something that succinct a couple of days ago. Ah well&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  freelyassociating.org/2006/07/a-refrain-a-routine-a-mechanism/feed/ ) in 0.42782 seconds, on Feb 6th, 2012 at 7:21 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 6th, 2012 at 8:21 pm UTC -->
