<?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: resource maps and site maps</title>
	<atom:link href="http://inkdroid.org/journal/2008/08/01/resource-maps-and-site-maps/feed/" rel="self" type="application/rss+xml" />
	<link>http://inkdroid.org/journal/2008/08/01/resource-maps-and-site-maps/</link>
	<description>$pithy_personal_mission_statement</description>
	<lastBuildDate>Wed, 10 Mar 2010 02:04:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael L. Nelson</title>
		<link>http://inkdroid.org/journal/2008/08/01/resource-maps-and-site-maps/comment-page-1/#comment-69756</link>
		<dc:creator>Michael L. Nelson</dc:creator>
		<pubDate>Mon, 04 Aug 2008 21:30:09 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=241#comment-69756</guid>
		<description>We considered sitemaps as a serialization format early on, but their limitation of 
location limits their usefulness.  For example, /a/b/sitemap.xml could aggregate 
/a/b/foo.html, but not /a/c/bar.html or /x/y/z.html.  For some repos this might
not be a problem, but it would prevent things like arXiv.org aggregating resources
in citebase.org.

(see http://www.sitemaps.org/protocol.php#location).</description>
		<content:encoded><![CDATA[<p>We considered sitemaps as a serialization format early on, but their limitation of<br />
location limits their usefulness.  For example, /a/b/sitemap.xml could aggregate<br />
/a/b/foo.html, but not /a/c/bar.html or /x/y/z.html.  For some repos this might<br />
not be a problem, but it would prevent things like arXiv.org aggregating resources<br />
in citebase.org.</p>
<p>(see <a href="http://www.sitemaps.org/protocol.php#location)" rel="nofollow">http://www.sitemaps.org/protocol.php#location)</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ed</title>
		<link>http://inkdroid.org/journal/2008/08/01/resource-maps-and-site-maps/comment-page-1/#comment-69377</link>
		<dc:creator>ed</dc:creator>
		<pubDate>Sat, 02 Aug 2008 01:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=241#comment-69377</guid>
		<description>GoogleSiteMaps support things like changefreq and priority that don&#039;t have an analog in the Atom world. But the main problem with repositories is discovery, so perhaps simply making OAI-ORE resource maps available as Atom will be enough eh? Thanks for the comment.</description>
		<content:encoded><![CDATA[<p>GoogleSiteMaps support things like changefreq and priority that don&#8217;t have an analog in the Atom world. But the main problem with repositories is discovery, so perhaps simply making OAI-ORE resource maps available as Atom will be enough eh? Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sean Gillies</title>
		<link>http://inkdroid.org/journal/2008/08/01/resource-maps-and-site-maps/comment-page-1/#comment-69317</link>
		<dc:creator>Sean Gillies</dc:creator>
		<pubDate>Fri, 01 Aug 2008 16:42:46 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=241#comment-69317</guid>
		<description>Google, Yahoo, and Microsoft already support Atom as a sitemap format. Does OAI-ORE bring anything else to the table (in the way of more specific sitemapping instructions) that would warrant another serialization?</description>
		<content:encoded><![CDATA[<p>Google, Yahoo, and Microsoft already support Atom as a sitemap format. Does OAI-ORE bring anything else to the table (in the way of more specific sitemapping instructions) that would warrant another serialization?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
