<?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: 2. MLA Task Force Recommendations</title>
	<atom:link href="http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing/2-mla-task-force-recommendations/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing</link>
	<description>Scholarly Publishing in the Age of the Internet</description>
	<lastBuildDate>Wed, 08 Aug 2007 00:57:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jeremy Butler</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing/2-mla-task-force-recommendations/#comment-149</link>
		<dc:creator>Jeremy Butler</dc:creator>
		<pubDate>Fri, 27 Jul 2007 13:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/scholarly-publishing-in-the-age-of-the-internet/2007/03/23/mla-task-force-recommendations/#comment-149</guid>
		<description>The University of Alabama does not offer memorandums of understanding (What a terrific phrase! I only wish these were available in all areas of one’s life!), but tenure-track individuals are reviewed annually and officially advised as to their progress toward tenure.</description>
		<content:encoded><![CDATA[<p>The University of Alabama does not offer memorandums of understanding (What a terrific phrase! I only wish these were available in all areas of one’s life!), but tenure-track individuals are reviewed annually and officially advised as to their progress toward tenure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KF</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing/2-mla-task-force-recommendations/#comment-148</link>
		<dc:creator>KF</dc:creator>
		<pubDate>Tue, 03 Jul 2007 08:02:58 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/scholarly-publishing-in-the-age-of-the-internet/2007/03/23/mla-task-force-recommendations/#comment-148</guid>
		<description>This is an extremely interesting point, Dave; I’ve written about this kind of technical illiteracy elsewhere as being akin to the days when profs all either had secretaries or had their wives type their manuscripts for them (or both). Some of that technical illiteracy was then, and is now, a matter of social privilege — those of us who get to do the “higher” thinking are forgiven our inability to operate the machinery. But I suspect there’s a day coming, and soon, when asking someone to do your digital production for you will be looked at much like asking someone to type up your documents would be today…
</description>
		<content:encoded><![CDATA[<p>This is an extremely interesting point, Dave; I’ve written about this kind of technical illiteracy elsewhere as being akin to the days when profs all either had secretaries or had their wives type their manuscripts for them (or both). Some of that technical illiteracy was then, and is now, a matter of social privilege — those of us who get to do the “higher” thinking are forgiven our inability to operate the machinery. But I suspect there’s a day coming, and soon, when asking someone to do your digital production for you will be looked at much like asking someone to type up your documents would be today…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Parry</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing/2-mla-task-force-recommendations/#comment-146</link>
		<dc:creator>David Parry</dc:creator>
		<pubDate>Mon, 16 Apr 2007 23:59:30 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/scholarly-publishing-in-the-age-of-the-internet/2007/03/23/mla-task-force-recommendations/#comment-146</guid>
		<description>Much of what is talked about throughout this paper is “software” focused, but this paragraph makes me think of “hardware” issues as well. That is some of the resistance to the digital I see, particularly in the humanities comes from a lack of ability to use the tools, or a lack of familiarity with the tools. This goes back to some of the divide that you were speaking of earlier with regards to the sciences and humanities. There is a basic hardware literacy that probably would need to supplement a digitization of scholarship. As a rather rudimentary example I think of the number of times I have meet professors who have no idea how to use tabbed browsing–a basic skill I think for navigating web based information, for example the trackback that you mention later. As content moves digital, printing out the journal article will no longer suffice, not only for the volume of printing that would have to be done, but also because printing a work which is native to the digital environment will fundamentally change it.</description>
		<content:encoded><![CDATA[<p>Much of what is talked about throughout this paper is “software” focused, but this paragraph makes me think of “hardware” issues as well. That is some of the resistance to the digital I see, particularly in the humanities comes from a lack of ability to use the tools, or a lack of familiarity with the tools. This goes back to some of the divide that you were speaking of earlier with regards to the sciences and humanities. There is a basic hardware literacy that probably would need to supplement a digitization of scholarship. As a rather rudimentary example I think of the number of times I have meet professors who have no idea how to use tabbed browsing–a basic skill I think for navigating web based information, for example the trackback that you mention later. As content moves digital, printing out the journal article will no longer suffice, not only for the volume of printing that would have to be done, but also because printing a work which is native to the digital environment will fundamentally change it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Mittell</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing/2-mla-task-force-recommendations/#comment-145</link>
		<dc:creator>Jason Mittell</dc:creator>
		<pubDate>Thu, 29 Mar 2007 23:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/scholarly-publishing-in-the-age-of-the-internet/2007/03/23/mla-task-force-recommendations/#comment-145</guid>
		<description>Interesting – we do not get PTT letters, and I don’t know anybody else at an institution who does. The one danger with such a system is that the definition of “progress” gets so routinized and quantified that it can’t address the broad array of work that people do, especially alternative &amp; long-term research projects. I know of instances where this boils down to annual “page counts” for publications, which is certainly not the answer…</description>
		<content:encoded><![CDATA[<p>Interesting – we do not get PTT letters, and I don’t know anybody else at an institution who does. The one danger with such a system is that the definition of “progress” gets so routinized and quantified that it can’t address the broad array of work that people do, especially alternative &amp; long-term research projects. I know of instances where this boils down to annual “page counts” for publications, which is certainly not the answer…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clancy Ratliff</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/scholarlypublishing/2-mla-task-force-recommendations/#comment-143</link>
		<dc:creator>Clancy Ratliff</dc:creator>
		<pubDate>Thu, 29 Mar 2007 16:48:52 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/scholarly-publishing-in-the-age-of-the-internet/2007/03/23/mla-task-force-recommendations/#comment-143</guid>
		<description>Taking only this brief, simple step would go such a long way toward rewarding work appropriately. Also, what about annual progress toward tenure letters? We get these at East Carolina University; do they do this at other places too? We were in the &lt;a href=&quot;http://chronicle.com/weekly/v53/i22/22a00601.htm&quot; rel=&quot;nofollow&quot;&gt;top six universities&lt;/a&gt; for tenure clarity (subscribers only), so I don’t want to assume that they do PTT letters everywhere.</description>
		<content:encoded><![CDATA[<p>Taking only this brief, simple step would go such a long way toward rewarding work appropriately. Also, what about annual progress toward tenure letters? We get these at East Carolina University; do they do this at other places too? We were in the <a href="http://chronicle.com/weekly/v53/i22/22a00601.htm" rel="nofollow">top six universities</a> for tenure clarity (subscribers only), so I don’t want to assume that they do PTT letters everywhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

