<?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: EP 1.3: Interpreting Processes</title>
	<atom:link href="http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/feed/" rel="self" type="application/rss+xml" />
	<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/</link>
	<description>A group blog about computer narrative, games, poetry, and art.</description>
	<lastBuildDate>Wed, 13 Jan 2010 15:44:40 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Matt Barton</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-239908</link>
		<dc:creator>Matt Barton</dc:creator>
		<pubDate>Thu, 24 Apr 2008 19:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-239908</guid>
		<description>As long as you&#039;re listing people who&#039;ve written on this, I might humbly posit my own article http://www.freesoftwaremagazine.com/articles/focus-software_as_art/</description>
		<content:encoded><![CDATA[<p>As long as you&#8217;re listing people who&#8217;ve written on this, I might humbly posit my own article <a href="http://www.freesoftwaremagazine.com/articles/focus-software_as_art/" rel="nofollow">http://www.freesoftwaremagazine.com/articles/focus-software_as_art/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark M.</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-238792</link>
		<dc:creator>Mark M.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 21:56:57 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-238792</guid>
		<description>I&#039;m not sure I would use this analogy.   But let me come back to this.   The relationship of steel-design do not quite seem to be the same as code-processes -- or maybe it&#039;s that the link to steel suggests (or evokes) a kind of a priori status to code which is full of modeling and design choices, too, to a degree I don&#039;t typically associate with steel.  The objection is more about evocations perhaps than precision.  More on this later.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure I would use this analogy.   But let me come back to this.   The relationship of steel-design do not quite seem to be the same as code-processes &#8212; or maybe it&#8217;s that the link to steel suggests (or evokes) a kind of a priori status to code which is full of modeling and design choices, too, to a degree I don&#8217;t typically associate with steel.  The objection is more about evocations perhaps than precision.  More on this later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark M.</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-238785</link>
		<dc:creator>Mark M.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 21:43:10 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-238785</guid>
		<description>I&#039;m now wondering about this term &quot;expressive.&quot; Does &quot;expressive&quot; require that someone (an author) is &quot;expressing.&quot;  I live part-time in the world of composition where words like &quot;expressive&quot; are challenged by words like &quot;construction.&quot;  Or is the &quot;expression&quot; a meta-level effect of certain design choices.  (I&#039;ll read farther and find out!)</description>
		<content:encoded><![CDATA[<p>I&#8217;m now wondering about this term &#8220;expressive.&#8221; Does &#8220;expressive&#8221; require that someone (an author) is &#8220;expressing.&#8221;  I live part-time in the world of composition where words like &#8220;expressive&#8221; are challenged by words like &#8220;construction.&#8221;  Or is the &#8220;expression&#8221; a meta-level effect of certain design choices.  (I&#8217;ll read farther and find out!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark M.</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-238784</link>
		<dc:creator>Mark M.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 21:37:51 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-238784</guid>
		<description>On some level, doesn&#039;t the author also interact with the work through a surface? Or is that too fine grained?</description>
		<content:encoded><![CDATA[<p>On some level, doesn&#8217;t the author also interact with the work through a surface? Or is that too fine grained?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark M.</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-238783</link>
		<dc:creator>Mark M.</dc:creator>
		<pubDate>Mon, 21 Apr 2008 21:33:02 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-238783</guid>
		<description>Is this to go so far as to say that there is an epistemology or ideology implied here?</description>
		<content:encoded><![CDATA[<p>Is this to go so far as to say that there is an epistemology or ideology implied here?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noah</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-204504</link>
		<dc:creator>noah</dc:creator>
		<pubDate>Thu, 14 Feb 2008 17:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-204504</guid>
		<description>John, I think you&#039;re completely right. There are a couple of uses of &quot;code&quot; in play here, and I&#039;m lumping them together. One is basically literal -- people like Marino, Black, and Mateas &amp; Montfort are looking closely at source code and the languages in which it is written. The other use of &quot;code&quot; is more like the way I use &quot;process(es/ing)&quot; -- a focus on the operations specified through code, rather than the particular text of it. Though, of course, both senses are somewhat in play in all of them. Anyway, I should definitely write something a bit more careful and clear for the final manuscript.</description>
		<content:encoded><![CDATA[<p>John, I think you&#8217;re completely right. There are a couple of uses of &#8220;code&#8221; in play here, and I&#8217;m lumping them together. One is basically literal &#8212; people like Marino, Black, and Mateas &#038; Montfort are looking closely at source code and the languages in which it is written. The other use of &#8220;code&#8221; is more like the way I use &#8220;process(es/ing)&#8221; &#8212; a focus on the operations specified through code, rather than the particular text of it. Though, of course, both senses are somewhat in play in all of them. Anyway, I should definitely write something a bit more careful and clear for the final manuscript.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: serial consign</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-202907</link>
		<dc:creator>serial consign</dc:creator>
		<pubDate>Mon, 11 Feb 2008 21:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-202907</guid>
		<description>&lt;strong&gt;large-scale conversations&lt;/strong&gt;

</description>
		<content:encoded><![CDATA[<p><strong>large-scale conversations</strong></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cayley</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-202168</link>
		<dc:creator>John Cayley</dc:creator>
		<pubDate>Mon, 11 Feb 2008 01:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-202168</guid>
		<description>I take Noah&#039;s point that there is a distinction to made here between an examination of code and practices of coding that are focused on their (technical, CS) specifics: the (programming) language used, affordances of the specific language, appropriate engagement with those affordances, programming style, etc. Mateas and Montfort&#039;s contribution here is within the above purview; Marino is wanting to make interventions on both sides of the distinction. (I don&#039;t know the Black book.) However, the citation of my own essay here, along with Raley&#039;s and Hayles&#039;, should not, I think, be see as only or even chiefly in the realm of such &#039;code studies.&#039; These latter writers all address the cultural and interpretative significances of the fact that the literary objects we&#039;re examining are made, in part, through practices of coding. The code and coding to which we refer is abstracted and the statements we make about code will have a bearing on your address to expressive process(ing). Arguably, expressive process(ing) cannot exist without practices of coding, and so the properties, methods and implications of such coding practices (as distinct, for example from practices of writing or inscription) will speak to the concerns of EP.</description>
		<content:encoded><![CDATA[<p>I take Noah&#8217;s point that there is a distinction to made here between an examination of code and practices of coding that are focused on their (technical, CS) specifics: the (programming) language used, affordances of the specific language, appropriate engagement with those affordances, programming style, etc. Mateas and Montfort&#8217;s contribution here is within the above purview; Marino is wanting to make interventions on both sides of the distinction. (I don&#8217;t know the Black book.) However, the citation of my own essay here, along with Raley&#8217;s and Hayles&#8217;, should not, I think, be see as only or even chiefly in the realm of such &#8216;code studies.&#8217; These latter writers all address the cultural and interpretative significances of the fact that the literary objects we&#8217;re examining are made, in part, through practices of coding. The code and coding to which we refer is abstracted and the statements we make about code will have a bearing on your address to expressive process(ing). Arguably, expressive process(ing) cannot exist without practices of coding, and so the properties, methods and implications of such coding practices (as distinct, for example from practices of writing or inscription) will speak to the concerns of EP.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Cayley</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-202163</link>
		<dc:creator>John Cayley</dc:creator>
		<pubDate>Mon, 11 Feb 2008 00:46:24 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-202163</guid>
		<description>On the distinction, made explicit by Noah here, between code studies and (expressive) process(ing) studies, see comment below to note 7 (para 23).</description>
		<content:encoded><![CDATA[<p>On the distinction, made explicit by Noah here, between code studies and (expressive) process(ing) studies, see comment below to note 7 (para 23).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noah</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-191977</link>
		<dc:creator>noah</dc:creator>
		<pubDate>Sat, 26 Jan 2008 04:24:44 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-191977</guid>
		<description>Lev and Matt, I think the two of you are hitting on a key issue for our field. I sometimes find myself using a shorthand for software studies that, roughly, works out to &quot;we study the things computer scientists study, but using the approaches of the humanities, arts, and social sciences.&quot; Such an approach would actually leave the constitution and selection of the things studied by computer science completely unexamined. That would be a mistake.

I&#039;m relatively sure that both Matt&#039;s Mechanisms and Lev&#039;s work in progress avoid that trap. My hope is that Expressive Processing does as well. More particularly, I hope that we manage to avoid the trap while also remaining appropriately aware that the field of digital media is built on the research, results, and tools of computer science. 

Also, Lev, many thanks for the kind words about The New Media Reader!</description>
		<content:encoded><![CDATA[<p>Lev and Matt, I think the two of you are hitting on a key issue for our field. I sometimes find myself using a shorthand for software studies that, roughly, works out to &#8220;we study the things computer scientists study, but using the approaches of the humanities, arts, and social sciences.&#8221; Such an approach would actually leave the constitution and selection of the things studied by computer science completely unexamined. That would be a mistake.</p>
<p>I&#8217;m relatively sure that both Matt&#8217;s Mechanisms and Lev&#8217;s work in progress avoid that trap. My hope is that Expressive Processing does as well. More particularly, I hope that we manage to avoid the trap while also remaining appropriately aware that the field of digital media is built on the research, results, and tools of computer science. </p>
<p>Also, Lev, many thanks for the kind words about The New Media Reader!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt K.</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-191971</link>
		<dc:creator>Matt K.</dc:creator>
		<pubDate>Sat, 26 Jan 2008 03:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-191971</guid>
		<description>Lev&#039;s comments above remind me that we seem to be layering up the field of academic new media in much the same way as those tedious diagrams in &quot;how computers&quot; work textbooks: platform studies, code studies, software studies. We&#039;ve had what is essentially &quot;screen or interface studies&quot; for a while now.  Computers, as we know, are often depicted as stacks or towers of abstractions. And so I wonder a little about unselfconsciously duplicating a metaphor that has its own inherent artifice and limitations.</description>
		<content:encoded><![CDATA[<p>Lev&#8217;s comments above remind me that we seem to be layering up the field of academic new media in much the same way as those tedious diagrams in &#8220;how computers&#8221; work textbooks: platform studies, code studies, software studies. We&#8217;ve had what is essentially &#8220;screen or interface studies&#8221; for a while now.  Computers, as we know, are often depicted as stacks or towers of abstractions. And so I wonder a little about unselfconsciously duplicating a metaphor that has its own inherent artifice and limitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lev Manovich</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-191882</link>
		<dc:creator>Lev Manovich</dc:creator>
		<pubDate>Fri, 25 Jan 2008 20:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-191882</guid>
		<description>To a significant extent, modern thinking about culture can be characterized as &quot;surface studies.&quot; This is true of film studies, media studies, art history, literary studies, etc. Although each of these disciplines produced some work which engages with the production processes which led to the outputs presented to the audiences - films, literature, television programs, etc. - these works are a minority. A great majority of books, articles, and academic papers take these outputs as given; they are then interpreted using different methodologies (Psychoanalysis, Marxism, Feminism, etc.). What is not considered are the theories and concepts of the people involved in production, the technologies involved, and what can be called “cultural logistics” – the organization and consideration of networks of people, machines, media, distribution systems, etc. I think that one of the goals of Software Studies is to focus on all these dimensions and to demonstrate to the rest of humanities why their study is crucial.</description>
		<content:encoded><![CDATA[<p>To a significant extent, modern thinking about culture can be characterized as &#8220;surface studies.&#8221; This is true of film studies, media studies, art history, literary studies, etc. Although each of these disciplines produced some work which engages with the production processes which led to the outputs presented to the audiences &#8211; films, literature, television programs, etc. &#8211; these works are a minority. A great majority of books, articles, and academic papers take these outputs as given; they are then interpreted using different methodologies (Psychoanalysis, Marxism, Feminism, etc.). What is not considered are the theories and concepts of the people involved in production, the technologies involved, and what can be called “cultural logistics” – the organization and consideration of networks of people, machines, media, distribution systems, etc. I think that one of the goals of Software Studies is to focus on all these dimensions and to demonstrate to the rest of humanities why their study is crucial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: noah</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-191875</link>
		<dc:creator>noah</dc:creator>
		<pubDate>Fri, 25 Jan 2008 20:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-191875</guid>
		<description>Markku, yes, there are definitely a variety of models in Cybertext. I&#039;ve picked out the traversal function model because it&#039;s the mostly widely-cited (and probably the one Cybertext develops at the most length). The model you mention is closer to my own conception, and so I wish it had received more attention. As far as I know, it is not only little-cited in other writings, but also not used in Cybertext for anything but the discussion of &quot;adventure games&quot; and their ilk. 

The main place I&#039;m going with all this model-building, by the way, is toward the broader notion of &quot;operational logics&quot; that we talked about a bit in Siegen in 2004. When we get there (next week) I&#039;d very much appreciate hearing your thoughts.</description>
		<content:encoded><![CDATA[<p>Markku, yes, there are definitely a variety of models in Cybertext. I&#8217;ve picked out the traversal function model because it&#8217;s the mostly widely-cited (and probably the one Cybertext develops at the most length). The model you mention is closer to my own conception, and so I wish it had received more attention. As far as I know, it is not only little-cited in other writings, but also not used in Cybertext for anything but the discussion of &#8220;adventure games&#8221; and their ilk. </p>
<p>The main place I&#8217;m going with all this model-building, by the way, is toward the broader notion of &#8220;operational logics&#8221; that we talked about a bit in Siegen in 2004. When we get there (next week) I&#8217;d very much appreciate hearing your thoughts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lev Manovich</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-191872</link>
		<dc:creator>Lev Manovich</dc:creator>
		<pubDate>Fri, 25 Jan 2008 19:55:06 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-191872</guid>
		<description>In Language of New Media (completed in 1999), I wrote: &quot;To understand the logic of new media we need to turn to computer science. It is there that we may expect to find the new terms, categories and operations that characterize media that became programmable.&quot; Reading this statement today, I feel that it positions computer science as a kind of absolute truth, a given which can explain to us how culture works in software society. But computer science is itself part of culture.  The book, which first demonstrated this in a very comprehensive fashion, is New Media Reader that was put together by (Noah Wardrip-Fruin and Nick Montfort (MIT Press, 2003). The publication of this groundbreaking anthology laid the framework for the historical study of software as it relates to the history of culture. Although the Reader did not explicitly use the term “software studies,” it did propose a new model for how to think about software. By systematically juxtaposing important texts by pioneers of cultural computing and key artists active in the same historical periods, the Reader demonstrated that both belonged to the same larger epistemes. That is, often the same idea was simultaneously articulated in thinking of artists and scientists who were inventing cultural computing. For instance, the book opens with the story by Jorge Borges (1941) and the article by Vannevar Bush (1945) which both contain the idea of a massive branching structure as a better way to organize data and to represent human experience.
	Therefore, I think that software studies has to both investigate the role of software in forming contemporary culture - and to investigate cultural, social, and economic forces which are shaping development of software itself.</description>
		<content:encoded><![CDATA[<p>In Language of New Media (completed in 1999), I wrote: &#8220;To understand the logic of new media we need to turn to computer science. It is there that we may expect to find the new terms, categories and operations that characterize media that became programmable.&#8221; Reading this statement today, I feel that it positions computer science as a kind of absolute truth, a given which can explain to us how culture works in software society. But computer science is itself part of culture.  The book, which first demonstrated this in a very comprehensive fashion, is New Media Reader that was put together by (Noah Wardrip-Fruin and Nick Montfort (MIT Press, 2003). The publication of this groundbreaking anthology laid the framework for the historical study of software as it relates to the history of culture. Although the Reader did not explicitly use the term “software studies,” it did propose a new model for how to think about software. By systematically juxtaposing important texts by pioneers of cultural computing and key artists active in the same historical periods, the Reader demonstrated that both belonged to the same larger epistemes. That is, often the same idea was simultaneously articulated in thinking of artists and scientists who were inventing cultural computing. For instance, the book opens with the story by Jorge Borges (1941) and the article by Vannevar Bush (1945) which both contain the idea of a massive branching structure as a better way to organize data and to represent human experience.<br />
	Therefore, I think that software studies has to both investigate the role of software in forming contemporary culture &#8211; and to investigate cultural, social, and economic forces which are shaping development of software itself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markku eskelinen</title>
		<link>http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/comment-page-1/#comment-191393</link>
		<dc:creator>markku eskelinen</dc:creator>
		<pubDate>Fri, 25 Jan 2008 12:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://grandtextauto.org/2008/01/24/ep-13-interpreting-processes/#comment-191393</guid>
		<description>There are several models in Cybertext. It also includes (pp.103-105) &quot;a schematic model of internal structure&quot; with four groups of components: the data, the processing engines, the front-end medium and the users and some additional feedback loops between them. What is your take on that?</description>
		<content:encoded><![CDATA[<p>There are several models in Cybertext. It also includes (pp.103-105) &#8220;a schematic model of internal structure&#8221; with four groups of components: the data, the processing engines, the front-end medium and the users and some additional feedback loops between them. What is your take on that?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
