<?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: Episode 20 &#8211; Open to Change</title>
	<atom:link href="http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/feed/" rel="self" type="application/rss+xml" />
	<link>http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/</link>
	<description>A biweekly discussion of how digital media and technology are affecting learning, teaching, and scholarship at colleges, universities, libraries, and museums.</description>
	<lastBuildDate>Sat, 28 Aug 2010 20:51:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Amalyah Keshet</title>
		<link>http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/comment-page-1/#comment-270</link>
		<dc:creator>Amalyah Keshet</dc:creator>
		<pubDate>Mon, 17 Mar 2008 16:22:49 +0000</pubDate>
		<guid isPermaLink="false">http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/#comment-270</guid>
		<description>I enjoyed the podcast driving home from work this afternoon.  There - perhaps Apostolos and I have helped answer the question you guys voiced: who listens to these podcasts, anyway?

Commuters like myself are probably a representative sample; totally bored with broadcast radio, I go to the trouble of downloading podcasts, Digital Campus included, and burning them to CD because my car only has a CD player. After all, I only have so much time to read, i.e. never enough, and podcasts like this are a great way to make time work for me.

But that&#039;s just the technology. Regarding demographics:  my commute is to and from Jerusalem, Israel.</description>
		<content:encoded><![CDATA[<p>I enjoyed the podcast driving home from work this afternoon.  There &#8211; perhaps Apostolos and I have helped answer the question you guys voiced: who listens to these podcasts, anyway?</p>
<p>Commuters like myself are probably a representative sample; totally bored with broadcast radio, I go to the trouble of downloading podcasts, Digital Campus included, and burning them to CD because my car only has a CD player. After all, I only have so much time to read, i.e. never enough, and podcasts like this are a great way to make time work for me.</p>
<p>But that&#8217;s just the technology. Regarding demographics:  my commute is to and from Jerusalem, Israel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Scheinfeldt</title>
		<link>http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/comment-page-1/#comment-231</link>
		<dc:creator>Tom Scheinfeldt</dc:creator>
		<pubDate>Tue, 05 Feb 2008 00:22:32 +0000</pubDate>
		<guid isPermaLink="false">http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/#comment-231</guid>
		<description>Yes!  That is exactly what I want!  Thanks for listening.

-Tom</description>
		<content:encoded><![CDATA[<p>Yes!  That is exactly what I want!  Thanks for listening.</p>
<p>-Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apostolos K.</title>
		<link>http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/comment-page-1/#comment-230</link>
		<dc:creator>Apostolos K.</dc:creator>
		<pubDate>Mon, 04 Feb 2008 17:50:11 +0000</pubDate>
		<guid isPermaLink="false">http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/#comment-230</guid>
		<description>I enjoyed the podcast driving to work this morning.
In terms of the technology discussed on the show (the larger iphone like device) - seems like you are describing a cross between a Nokia Internet Tablet and the Apple Newton (model 2100) - both of which I own (the newton I use less and less these days)</description>
		<content:encoded><![CDATA[<p>I enjoyed the podcast driving to work this morning.<br />
In terms of the technology discussed on the show (the larger iphone like device) &#8211; seems like you are describing a cross between a Nokia Internet Tablet and the Apple Newton (model 2100) &#8211; both of which I own (the newton I use less and less these days)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Hetzner</title>
		<link>http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/comment-page-1/#comment-223</link>
		<dc:creator>Erik Hetzner</dc:creator>
		<pubDate>Thu, 31 Jan 2008 19:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://digitalcampus.tv/2008/01/30/episode-20-open-to-change/#comment-223</guid>
		<description>I enjoy your podcast, so your discussion of open access was a bit of a disappointment. It would have been nice if you have been more clear about the meaning of open access. You could, perhaps, have discussed the the Budapest Open Access Initiative, or the Bethesda statement. I&#039;m sure that you all understand open access, and that you are all interested in moving it forward, especially in the humanities were it has lagged behind. But by mixing your discussion of open access with other issues, you give some ammunition to the opponents of open access.

Open access does not mean lawyers who only publish to their blogs. It doesn&#039;t mean that things must be available online now instead of being available in 6 months. It does not mean articles that are not peer-reviewed. It does not mean works that are not properly copy-edited, or blog postings, or any of that. It does not even mean not publishing through the big publishers (although practically it often does). It doesn&#039;t even mean just putting an article on your website. Like the free software movement, or the free culture movement, it is primarily about freedom, from which the other benefits flow.

Rather than discuss how historians just aren&#039;t as up-to-date, it would have been nice to discuss the economic pressures which have partially driven open access in the sciences, and which may be less in the humanities, or the practical aspects which make open access to articles easier than to monographs. You did touch upon the idea that employees of public universities might have an obligation to provide their work to as wide an audience as possible, which was great. But otherwise, the discussion was a bit mixed up.</description>
		<content:encoded><![CDATA[<p>I enjoy your podcast, so your discussion of open access was a bit of a disappointment. It would have been nice if you have been more clear about the meaning of open access. You could, perhaps, have discussed the the Budapest Open Access Initiative, or the Bethesda statement. I&#8217;m sure that you all understand open access, and that you are all interested in moving it forward, especially in the humanities were it has lagged behind. But by mixing your discussion of open access with other issues, you give some ammunition to the opponents of open access.</p>
<p>Open access does not mean lawyers who only publish to their blogs. It doesn&#8217;t mean that things must be available online now instead of being available in 6 months. It does not mean articles that are not peer-reviewed. It does not mean works that are not properly copy-edited, or blog postings, or any of that. It does not even mean not publishing through the big publishers (although practically it often does). It doesn&#8217;t even mean just putting an article on your website. Like the free software movement, or the free culture movement, it is primarily about freedom, from which the other benefits flow.</p>
<p>Rather than discuss how historians just aren&#8217;t as up-to-date, it would have been nice to discuss the economic pressures which have partially driven open access in the sciences, and which may be less in the humanities, or the practical aspects which make open access to articles easier than to monographs. You did touch upon the idea that employees of public universities might have an obligation to provide their work to as wide an audience as possible, which was great. But otherwise, the discussion was a bit mixed up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
