<?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: codex, not print</title>
	<atom:link href="http://mediacommons.futureofthebook.org/mcpress/cpfinal/codex-not-print/feed/" rel="self" type="application/rss+xml" />
	<link>http://mediacommons.futureofthebook.org/mcpress/cpfinal</link>
	<description>New (Social) Structures for New (Networked) Texts</description>
	<lastBuildDate>Thu, 08 Nov 2007 21:08:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Terje Hillesund</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/cpfinal/codex-not-print/#comment-141</link>
		<dc:creator>Terje Hillesund</dc:creator>
		<pubDate>Fri, 19 Oct 2007 19:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/commentpress/2007/10/11/codex-not-print/#comment-141</guid>
		<description>In this and the next paragraph you suggest we approach issues “involved in electronic publishing from a broader structural perspective”, which intuitively seems correct. However, reading this chapter carefully, what really seems to be important is the reception of text, that is the use and reading of text, clearly indicated by use of terms and clauses such as: reader, reader’s active engagement, manipulation, random access, scrolling, sense of provenance, stick one’s finger between pages etc. I believe any approach to electronic publishing has to take the interrelation between use and structure very seriously, and as a result be willing to admit that no standalone interface, application or device can comply with all needs or reading practices, not even within the limited space of scholarly reading and writing.

I am very much in favour of the ideas underpinning CommentPress and have often felt a need for receiving more immediate feedback on my own writings and for giving response to others. However, before commenting a paper, I like to read it trough, reflecting on its content and getting an impression on the overall argument (often underlining parts of the text and making annotations). Unfortunately CommentPress neither provide an online reading mode nor a print version of the article. I therefore rely on the version I printed from the JEP archive for this kind of sustained and reflective reading. When I now comment, I have the printed and annotated version in front of me at the same time as I write the comments and scroll through the CommentPress text.

This is how I work (and studies indicate that this is a very common way of working). Taking the many different ways we read and use documents and texts into consideration, I believe you overstate your point when, using CommonPress as an example, you claim it is necessary to replace the codex-form with a web-native form. What is the necessity? And how do you think one form can replace numerous other forms?
</description>
		<content:encoded><![CDATA[<p>In this and the next paragraph you suggest we approach issues “involved in electronic publishing from a broader structural perspective”, which intuitively seems correct. However, reading this chapter carefully, what really seems to be important is the reception of text, that is the use and reading of text, clearly indicated by use of terms and clauses such as: reader, reader’s active engagement, manipulation, random access, scrolling, sense of provenance, stick one’s finger between pages etc. I believe any approach to electronic publishing has to take the interrelation between use and structure very seriously, and as a result be willing to admit that no standalone interface, application or device can comply with all needs or reading practices, not even within the limited space of scholarly reading and writing.</p>
<p>I am very much in favour of the ideas underpinning CommentPress and have often felt a need for receiving more immediate feedback on my own writings and for giving response to others. However, before commenting a paper, I like to read it trough, reflecting on its content and getting an impression on the overall argument (often underlining parts of the text and making annotations). Unfortunately CommentPress neither provide an online reading mode nor a print version of the article. I therefore rely on the version I printed from the JEP archive for this kind of sustained and reflective reading. When I now comment, I have the printed and annotated version in front of me at the same time as I write the comments and scroll through the CommentPress text.</p>
<p>This is how I work (and studies indicate that this is a very common way of working). Taking the many different ways we read and use documents and texts into consideration, I believe you overstate your point when, using CommonPress as an example, you claim it is necessary to replace the codex-form with a web-native form. What is the necessity? And how do you think one form can replace numerous other forms?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KF</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/cpfinal/codex-not-print/#comment-154</link>
		<dc:creator>KF</dc:creator>
		<pubDate>Fri, 19 Oct 2007 18:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/commentpress/2007/10/11/codex-not-print/#comment-154</guid>
		<description>That delay, alas, is about the moderation process; in order to prevent spam comments, first posts by new readers require approval. (And I was quite asleep as you were posting!) This indicates one of the problems with the technology, of course: the same kind of insecurity to which blog comment and trackback technologies are prone. My sense is that we’re going to have to solve those problems before really dynamic electronic scholarly communities will be able to arise.</description>
		<content:encoded><![CDATA[<p>That delay, alas, is about the moderation process; in order to prevent spam comments, first posts by new readers require approval. (And I was quite asleep as you were posting!) This indicates one of the problems with the technology, of course: the same kind of insecurity to which blog comment and trackback technologies are prone. My sense is that we’re going to have to solve those problems before really dynamic electronic scholarly communities will be able to arise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KF</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/cpfinal/codex-not-print/#comment-140</link>
		<dc:creator>KF</dc:creator>
		<pubDate>Fri, 19 Oct 2007 18:03:02 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/commentpress/2007/10/11/codex-not-print/#comment-140</guid>
		<description>I’d certainly imagine so. I’ll keep my eye out for it, and will post a comment on that works cited entry once it’s published.</description>
		<content:encoded><![CDATA[<p>I’d certainly imagine so. I’ll keep my eye out for it, and will post a comment on that works cited entry once it’s published.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terje Hillesund</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/cpfinal/codex-not-print/#comment-153</link>
		<dc:creator>Terje Hillesund</dc:creator>
		<pubDate>Fri, 19 Oct 2007 10:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/commentpress/2007/10/11/codex-not-print/#comment-153</guid>
		<description>in order to escape what he called “the tyranny of the book”

Here Stallybrass obviously makes a very good point, but he still holds on to the concept of a “page”, which is also a codex/book-concept. In print the size and contents of a page is fixed, whereas in much digital publishing (e.g. in e-book readers) re-flow or adapted layout is an important principle. Digital publishing has long suffered under the “tyranny of the page”, especially as PDF has been such a dominant format.

(By the way: This is my third comment and none of the others have yet turned up on the site, a delay that gives an annoying impression of a behind-the-scenes editing process.)</description>
		<content:encoded><![CDATA[<p>in order to escape what he called “the tyranny of the book”</p>
<p>Here Stallybrass obviously makes a very good point, but he still holds on to the concept of a “page”, which is also a codex/book-concept. In print the size and contents of a page is fixed, whereas in much digital publishing (e.g. in e-book readers) re-flow or adapted layout is an important principle. Digital publishing has long suffered under the “tyranny of the page”, especially as PDF has been such a dominant format.</p>
<p>(By the way: This is my third comment and none of the others have yet turned up on the site, a delay that gives an annoying impression of a behind-the-scenes editing process.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terje Hillesund</title>
		<link>http://mediacommons.futureofthebook.org/mcpress/cpfinal/codex-not-print/#comment-139</link>
		<dc:creator>Terje Hillesund</dc:creator>
		<pubDate>Fri, 19 Oct 2007 09:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://mediacommons.futureofthebook.org/commentpress/2007/10/11/codex-not-print/#comment-139</guid>
		<description>Is there any hope Stallybrass will publish his paper?</description>
		<content:encoded><![CDATA[<p>Is there any hope Stallybrass will publish his paper?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

