<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Why hotlinking to a RePEc service makes sense</title>
	<atom:link href="http://blog.repec.org/2008/06/27/why-hotlinking-to-a-repec-service-makes-sense/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.repec.org/2008/06/27/why-hotlinking-to-a-repec-service-makes-sense/</link>
	<description>Information about Research Papers in Economics (RePEc)</description>
	<lastBuildDate>Tue, 07 May 2013 15:56:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Using RePEc for syllabi, bibliographies and publication lists &#171; The RePEc Blog</title>
		<link>http://blog.repec.org/2008/06/27/why-hotlinking-to-a-repec-service-makes-sense/#comment-203</link>
		<dc:creator><![CDATA[Using RePEc for syllabi, bibliographies and publication lists &#171; The RePEc Blog]]></dc:creator>
		<pubDate>Wed, 10 Dec 2008 02:36:05 +0000</pubDate>
		<guid isPermaLink="false">http://repec.org/blog/?p=58#comment-203</guid>
		<description><![CDATA[[...] for syllabi, bibliographies and publication&#160;lists By Christian Zimmermann  As highlighted in a recent post, we encourage deep linking in RePEc services. This is particularly useful for reading lists and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] for syllabi, bibliographies and publication&nbsp;lists By Christian Zimmermann  As highlighted in a recent post, we encourage deep linking in RePEc services. This is particularly useful for reading lists and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The RePEc blog &#187; Blog Archive &#187; Using RePEc for syllabi, bibliographies and publication lists</title>
		<link>http://blog.repec.org/2008/06/27/why-hotlinking-to-a-repec-service-makes-sense/#comment-176</link>
		<dc:creator><![CDATA[The RePEc blog &#187; Blog Archive &#187; Using RePEc for syllabi, bibliographies and publication lists]]></dc:creator>
		<pubDate>Sun, 13 Jul 2008 22:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://repec.org/blog/?p=58#comment-176</guid>
		<description><![CDATA[[...] Why hotlinking to a RePEc service makes sense  [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Why hotlinking to a RePEc service makes sense  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kurtstinson</title>
		<link>http://blog.repec.org/2008/06/27/why-hotlinking-to-a-repec-service-makes-sense/#comment-175</link>
		<dc:creator><![CDATA[kurtstinson]]></dc:creator>
		<pubDate>Thu, 03 Jul 2008 12:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://repec.org/blog/?p=58#comment-175</guid>
		<description><![CDATA[Hotlinking should be encouraged to save the valuable time of the user .Hot linking will be beneficial in frequent visting sites as well. Good work.

…………………………………….
Kurt Stinson]]></description>
		<content:encoded><![CDATA[<p>Hotlinking should be encouraged to save the valuable time of the user .Hot linking will be beneficial in frequent visting sites as well. Good work.</p>
<p>…………………………………….<br />
Kurt Stinson</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian Zimmermann</title>
		<link>http://blog.repec.org/2008/06/27/why-hotlinking-to-a-repec-service-makes-sense/#comment-174</link>
		<dc:creator><![CDATA[Christian Zimmermann]]></dc:creator>
		<pubDate>Mon, 30 Jun 2008 01:32:48 +0000</pubDate>
		<guid isPermaLink="false">http://repec.org/blog/?p=58#comment-174</guid>
		<description><![CDATA[I am made aware that I confuse hotlinking and deep linking. Indeed. Hotlinking is linking an object, for example an image, from another website, thus &quot;stealing&quot; bandwidth. Deep linking is linking to a specific page of a website instead of the front page, what I specifically advocated here.

I stand corrected.]]></description>
		<content:encoded><![CDATA[<p>I am made aware that I confuse hotlinking and deep linking. Indeed. Hotlinking is linking an object, for example an image, from another website, thus &#8220;stealing&#8221; bandwidth. Deep linking is linking to a specific page of a website instead of the front page, what I specifically advocated here.</p>
<p>I stand corrected.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
