<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Free Content Now!</title>
	<atom:link href="http://craigrandall.net/archives/2006/04/free-content-now/feed/" rel="self" type="application/rss+xml" />
	<link>http://craigrandall.net/archives/2006/04/free-content-now/</link>
	<description>Thoughts about software architecture, books and life</description>
	<lastBuildDate>Wed, 04 Jan 2012 18:00:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Craig&#8217;s Musings &#187; Blog Archive &#187; An idea to set content free</title>
		<link>http://craigrandall.net/archives/2006/04/free-content-now/comment-page-1/#comment-101</link>
		<dc:creator>Craig&#8217;s Musings &#187; Blog Archive &#187; An idea to set content free</dc:creator>
		<pubDate>Sat, 22 Apr 2006 23:27:34 +0000</pubDate>
		<guid isPermaLink="false">http://craigrandall.net/archives/2006/04/free-content-now-2/#comment-101</guid>
		<description>[...] Yesterday I mentioned how wikis could be useful way to reflect that fact that use cases, requirements, functionality, design and other aspects of software engineering are dynamic considerations, not static ones. While I mentioned that tools exist to capture the point-in-time state of a wiki into, for example a Word document or a PDF file, I didn&#8217;t talk about content flow in the other direction. [...]</description>
		<content:encoded><![CDATA[<p>[...] Yesterday I mentioned how wikis could be useful way to reflect that fact that use cases, requirements, functionality, design and other aspects of software engineering are dynamic considerations, not static ones. While I mentioned that tools exist to capture the point-in-time state of a wiki into, for example a Word document or a PDF file, I didn&#8217;t talk about content flow in the other direction. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

