<?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: Is Blogging Scholarship?</title>
	<atom:link href="http://library.duke.edu/blogs/scholcomm/2007/09/06/is-blogging-scholarship/feed/" rel="self" type="application/rss+xml" />
	<link>http://library.duke.edu/blogs/scholcomm/2007/09/06/is-blogging-scholarship/</link>
	<description>Duke&#039;s source for advice and information about copyright and publication issues</description>
	<lastBuildDate>Tue, 17 Nov 2009 04:32:11 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Scholarly Communications @ Duke &#187; What faculty think</title>
		<link>http://library.duke.edu/blogs/scholcomm/2007/09/06/is-blogging-scholarship/comment-page-1/#comment-3964</link>
		<dc:creator>Scholarly Communications @ Duke &#187; What faculty think</dc:creator>
		<pubDate>Tue, 11 Sep 2007 13:26:30 +0000</pubDate>
		<guid isPermaLink="false">http://library.duke.edu/blogs/scholcomm/2007/09/06/is-blogging-scholarship/#comment-3964</guid>
		<description>[...] innovation in scholarly communications.&#8221; For many this seems counter-intuitive, although the report on legal scholarship discussed in our last post indicated the same possibility. While younger faculty may be more comfortable with technology [...]</description>
		<content:encoded><![CDATA[<p>[...] innovation in scholarly communications.&#8221; For many this seems counter-intuitive, although the report on legal scholarship discussed in our last post indicated the same possibility. While younger faculty may be more comfortable with technology [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
