<?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"
	>
<channel>
	<title>Comments on: testing something</title>
	<atom:link href="http://williamtozier.com/slurry/2008/04/28/testing-something/feed" rel="self" type="application/rss+xml" />
	<link>http://williamtozier.com/slurry/2008/04/28/testing-something</link>
	<description>Pontification without all the gritty gravitas</description>
	<pubDate>Fri, 25 Jul 2008 08:28:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Tozier</title>
		<link>http://williamtozier.com/slurry/2008/04/28/testing-something#comment-52394</link>
		<dc:creator>Tozier</dc:creator>
		<pubDate>Tue, 29 Apr 2008 21:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://williamtozier.com/slurry/?p=1213#comment-52394</guid>
		<description>I'm wondering that myself.

I think it needs to be multimodal: a sense of magnification, as here, but easily traversing the intended visual flow of the page elements, and also keeping some sense of overall context regardless of magnification level.

One big goal is to be able to present 19th century newspapers online, without &lt;i&gt;needing&lt;/i&gt; to break them into individual columns at all scales.

But it could get tedious. Look at &lt;a href="http://books.google.com/books?id=ZeVnIa6BbnwC&#038;printsec=frontcover&#038;dq=allibone%27s&#038;ei=rosXSNTmDqDKjgG98uHZBQ#PPA281,M1" rel="nofollow"&gt;this book&lt;/a&gt;, for example---we have five 3000-page volumes of this junk sitting here waiting for a solution. Scanning it without snipping off page ends was too challenging for our Google buddies.

Let alone the ridiculous amount of effort involved in slicing and presenting a few hundred thousand page scans as individual multiscale images... let alone reading them.

Still thinking.</description>
		<content:encoded><![CDATA[<p>I&#8217;m wondering that myself.</p>
<p>I think it needs to be multimodal: a sense of magnification, as here, but easily traversing the intended visual flow of the page elements, and also keeping some sense of overall context regardless of magnification level.</p>
<p>One big goal is to be able to present 19th century newspapers online, without <i>needing</i> to break them into individual columns at all scales.</p>
<p>But it could get tedious. Look at <a href="http://books.google.com/books?id=ZeVnIa6BbnwC&#038;printsec=frontcover&#038;dq=allibone%27s&#038;ei=rosXSNTmDqDKjgG98uHZBQ#PPA281,M1" rel="nofollow">this book</a>, for example&#8212;we have five 3000-page volumes of this junk sitting here waiting for a solution. Scanning it without snipping off page ends was too challenging for our Google buddies.</p>
<p>Let alone the ridiculous amount of effort involved in slicing and presenting a few hundred thousand page scans as individual multiscale images&#8230; let alone reading them.</p>
<p>Still thinking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Weise</title>
		<link>http://williamtozier.com/slurry/2008/04/28/testing-something#comment-52393</link>
		<dc:creator>John Weise</dc:creator>
		<pubDate>Tue, 29 Apr 2008 20:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://williamtozier.com/slurry/?p=1213#comment-52393</guid>
		<description>I find it easy and intuitive. I'm wondering what the multi-page solution will be. Going back to go forward would be tedious. How to keep it simple? Things can so quickly become complex.</description>
		<content:encoded><![CDATA[<p>I find it easy and intuitive. I&#8217;m wondering what the multi-page solution will be. Going back to go forward would be tedious. How to keep it simple? Things can so quickly become complex.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
