<?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: Eleemosynary RDF</title>
	<atom:link href="http://cmsmcq.com/mib/?feed=rss2&#038;p=59" rel="self" type="application/rss+xml" />
	<link>http://cmsmcq.com/mib/?p=59</link>
	<description>CMSMcQ's klog</description>
	<pubDate>Fri, 10 Sep 2010 12:29:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Cowan</title>
		<link>http://cmsmcq.com/mib/?p=59&cpage=1#comment-6435</link>
		<dc:creator>John Cowan</dc:creator>
		<pubDate>Tue, 15 Jul 2008 14:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://cmsmcq.com/mib/?p=59#comment-6435</guid>
		<description>I think your colleague was probably stone cold sober.  Because of the flexibility of RDF/XML, it's much easier to create and publish RDF than it is to locate and interpret it.  Reuters Health, when I was working there, chose to publish its metadata as RDF because it cost essentially nothing to do so: they wanted to publish the metadata anyhow, and using RDF/XML format embedded in the articles was easier than inventing their own format for it, and no easier or harder to generate programmatically.  We didn't have any particular need to read RDF, so its complexities didn't cost us anything.

Analogous enterprises are publishing open-source software and Ecclesiastes' remark about casting your bread upon the waters and finding it after many days.

(I have, indeed, read all seven Potter books, but I had forgotten Nurmengard and had to look it up.  The name sounds to me like a hybrid of Nuremberg and Isengard.)</description>
		<content:encoded><![CDATA[<p>I think your colleague was probably stone cold sober.  Because of the flexibility of RDF/XML, it&#8217;s much easier to create and publish RDF than it is to locate and interpret it.  Reuters Health, when I was working there, chose to publish its metadata as RDF because it cost essentially nothing to do so: they wanted to publish the metadata anyhow, and using RDF/XML format embedded in the articles was easier than inventing their own format for it, and no easier or harder to generate programmatically.  We didn&#8217;t have any particular need to read RDF, so its complexities didn&#8217;t cost us anything.</p>
<p>Analogous enterprises are publishing open-source software and Ecclesiastes&#8217; remark about casting your bread upon the waters and finding it after many days.</p>
<p>(I have, indeed, read all seven Potter books, but I had forgotten Nurmengard and had to look it up.  The name sounds to me like a hybrid of Nuremberg and Isengard.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
