<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://arcade.stanford.edu" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/">
<channel>
 <title>data visualization</title>
 <link>http://arcade.stanford.edu/category/tags/data-visualization</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en-ac</language>
<item>
 <title>What can topic models of PMLA teach us about the history of literary scholarship?</title>
 <link>http://arcade.stanford.edu/what-can-topic-models-of-pmla-teach-us-about-history-of-literary-scholarship</link>
 <description>&lt;p&gt;(Co-written by AG and &lt;a href=&quot;http://tedunderwood.com&quot;&gt;Ted Underwood&lt;/a&gt;.) Of all our literary-historical narratives it is the history of criticism itself that seems most wedded to a stodgy history-of-ideas approach---narrating change through a succession of stars or contending schools.&lt;/p&gt;  &lt;p&gt;&lt;a href=&quot;http://arcade.stanford.edu/what-can-topic-models-of-pmla-teach-us-about-history-of-literary-scholarship&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://arcade.stanford.edu/what-can-topic-models-of-pmla-teach-us-about-history-of-literary-scholarship#comments</comments>
 <category domain="http://arcade.stanford.edu/category/tags/data-visualization">data visualization</category>
 <category domain="http://arcade.stanford.edu/category/tags/digital-humanities">digital humanities</category>
 <category domain="http://arcade.stanford.edu/category/tags/history-of-criticism">history of criticism</category>
 <category domain="http://arcade.stanford.edu/category/tags/history-of-scholarship">history of scholarship</category>
 <category domain="http://arcade.stanford.edu/category/tags/pmla">PMLA</category>
 <category domain="http://arcade.stanford.edu/category/tags/quantitative-literary-studies">quantitative literary studies</category>
 <category domain="http://arcade.stanford.edu/category/tags/theory">Theory</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://arcade.stanford.edu/crss/node/1662</wfw:commentRss>
 <pubDate>Fri, 14 Dec 2012 10:40:08 -0800</pubDate>
 <dc:creator>Andrew Goldstone</dc:creator>
 <guid isPermaLink="false">1662 at http://arcade.stanford.edu</guid>
</item>
<item>
 <title>When Reading Fails</title>
 <link>http://arcade.stanford.edu/when-reading-fails</link>
 <description>&lt;p&gt;In light of several recent posts around here about reading (as &lt;a href=&quot;/close-reading-genre&quot;&gt;genre&lt;/a&gt;, as &lt;a href=&quot;/organic-unity-of-robert-elsmere&quot;&gt;practice&lt;/a&gt;, and as &lt;a href=&quot;/alan-jacobs-and-rise-of-reading-class&quot;&gt;cultural marker&lt;/a&gt;), I thought I&#039;d take the occasion of my first post to complicate reading-- and all that it entails-- a little more. &lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://arcade.stanford.edu/when-reading-fails&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://arcade.stanford.edu/when-reading-fails#comments</comments>
 <category domain="http://arcade.stanford.edu/category/tags/data-visualization">data visualization</category>
 <category domain="http://arcade.stanford.edu/category/tags/digital-humanities">digital humanities</category>
 <category domain="http://arcade.stanford.edu/category/tags/james-hemings">James Hemings</category>
 <category domain="http://arcade.stanford.edu/category/tags/reading">reading</category>
 <category domain="http://arcade.stanford.edu/category/tags/seeing">seeing</category>
 <category domain="http://arcade.stanford.edu/category/tags/social-network-analysis">social network analysis</category>
 <category domain="http://arcade.stanford.edu/category/tags/thomas-jefferson">Thomas Jefferson</category>
 <wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://arcade.stanford.edu/crss/node/1337</wfw:commentRss>
 <pubDate>Thu, 29 Sep 2011 13:23:30 -0700</pubDate>
 <dc:creator>Lauren Klein</dc:creator>
 <guid isPermaLink="false">1337 at http://arcade.stanford.edu</guid>
</item>
</channel>
</rss>
