<?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: Correlations</title>
	<atom:link href="http://www.vsca.ca/halfjack/?feed=rss2&#038;p=204" rel="self" type="application/rss+xml" />
	<link>http://www.vsca.ca/halfjack/?p=204</link>
	<description>discussion of science, humans, and games</description>
	<lastBuildDate>Mon, 30 Aug 2010 17:18:26 -0600</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: halfjack</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-426</link>
		<dc:creator>halfjack</dc:creator>
		<pubDate>Tue, 12 Jan 2010 22:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-426</guid>
		<description>One more thought on correlation that Toph pointed out. There is a real case he reviewed of a German book considered canonical and its English translation. As this is a book of academic interest, referring to its contents requires somehow referring to the location in the canonical (the German) form even if you only have the English. The English translation solves this by placing a marker in the English text every time the German text changes page. So the text:

&quot;This is the English translation [177] of some German text.&quot;

...indicates that in the German, page 177 begins with the German for &quot;of some German text.&quot;

That&#039;s pretty elegant. It&#039;s partly cool because it moves backwards -- rather than require a new markup for books, it only places that onus on new material. That smells &quot;right&quot; to me.</description>
		<content:encoded><![CDATA[<p>One more thought on correlation that Toph pointed out. There is a real case he reviewed of a German book considered canonical and its English translation. As this is a book of academic interest, referring to its contents requires somehow referring to the location in the canonical (the German) form even if you only have the English. The English translation solves this by placing a marker in the English text every time the German text changes page. So the text:</p>
<p>&#8220;This is the English translation [177] of some German text.&#8221;</p>
<p>&#8230;indicates that in the German, page 177 begins with the German for &#8220;of some German text.&#8221;</p>
<p>That&#8217;s pretty elegant. It&#8217;s partly cool because it moves backwards &#8212; rather than require a new markup for books, it only places that onus on new material. That smells &#8220;right&#8221; to me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raptus Regaliter » Rethinking the issue of PDF Distribution</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-267</link>
		<dc:creator>Raptus Regaliter » Rethinking the issue of PDF Distribution</dc:creator>
		<pubDate>Fri, 04 Dec 2009 22:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-267</guid>
		<description>[...] Murray, one of Diaspora&#8217;s creators, has a very astute blog entry about how information is presented and correlated between physical books and electronic documents. [...]</description>
		<content:encoded><![CDATA[<p>[...] Murray, one of Diaspora&#8217;s creators, has a very astute blog entry about how information is presented and correlated between physical books and electronic documents. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris A. (CodexArcanum)</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-228</link>
		<dc:creator>Chris A. (CodexArcanum)</dc:creator>
		<pubDate>Mon, 30 Nov 2009 16:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-228</guid>
		<description>This post and the last one got me thinking about HTML again.  It&#039;s overlooked quite a bit, because it&#039;s foundational.  No one walks into a new house and thinks first off, &quot;Wow! I bet there&#039;s a great concrete slab under here!&quot;  But HTML is, pardon the nerdgasm, one of the most impressive communication technologies ever devised.

And it was devised by academics (and eventually commercial interests) too, for exactly these kinds of problems.  How do you point out a &quot;page&quot; when all the content is in one stream? Hyperlinks.  How do you enforce layout, font, color, and style when the user can manipulate the raw text all they want?  You use CSS to implement a default style.  

Admittedly it has limits and is not perfect, but its a solid model to move from.  You seem to touch on this a bit in the comments.  Another interesting element of HTML is the ability to hide data and manipulate it.  Notes needn&#039;t be at the bottom, side, or appendix.  They can exist &quot;behind&quot; their marker in the text, only to appear when the user focuses on them.  Page numbers, line numbers, even word numbers can all exist as hidden information; a rich backdrop of meta-content to be explored as needed by the users (by users I mean content providers and consumers).  


But I think, in a lot of ways, Google was right: its all about search.  I feel like &quot;Check page 123&quot; or &quot;Go to section 3:14&quot; are both archaic and artificial to how we naturally approach text.  Closer is &quot;it&#039;s in the Ship section, near the part about lasers.&quot;  Search technology turns that phrasing into a position in the text through something like &quot;Ship : Lasers : Cool Thing&quot;.  It&#039;s not referential referencing, but contextual referencing.</description>
		<content:encoded><![CDATA[<p>This post and the last one got me thinking about HTML again.  It&#8217;s overlooked quite a bit, because it&#8217;s foundational.  No one walks into a new house and thinks first off, &#8220;Wow! I bet there&#8217;s a great concrete slab under here!&#8221;  But HTML is, pardon the nerdgasm, one of the most impressive communication technologies ever devised.</p>
<p>And it was devised by academics (and eventually commercial interests) too, for exactly these kinds of problems.  How do you point out a &#8220;page&#8221; when all the content is in one stream? Hyperlinks.  How do you enforce layout, font, color, and style when the user can manipulate the raw text all they want?  You use CSS to implement a default style.  </p>
<p>Admittedly it has limits and is not perfect, but its a solid model to move from.  You seem to touch on this a bit in the comments.  Another interesting element of HTML is the ability to hide data and manipulate it.  Notes needn&#8217;t be at the bottom, side, or appendix.  They can exist &#8220;behind&#8221; their marker in the text, only to appear when the user focuses on them.  Page numbers, line numbers, even word numbers can all exist as hidden information; a rich backdrop of meta-content to be explored as needed by the users (by users I mean content providers and consumers).  </p>
<p>But I think, in a lot of ways, Google was right: its all about search.  I feel like &#8220;Check page 123&#8243; or &#8220;Go to section 3:14&#8243; are both archaic and artificial to how we naturally approach text.  Closer is &#8220;it&#8217;s in the Ship section, near the part about lasers.&#8221;  Search technology turns that phrasing into a position in the text through something like &#8220;Ship : Lasers : Cool Thing&#8221;.  It&#8217;s not referential referencing, but contextual referencing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: d7</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-227</link>
		<dc:creator>d7</dc:creator>
		<pubDate>Sun, 29 Nov 2009 08:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-227</guid>
		<description>There is still some assumption about content built into the Book, Chapter, and Verse style of content markup, which is that the Verse that is marked up by a number is going to be a significant amount of text and so the markup will not have too much overhead. Visually, a paragraph number is not very much noise while reading if the paragraphs are large, but there are classes of content that don&#039;t match that assumption.

The example I have foremost in mind is large sections of dialogue, where the paragraph markers would become line markers and so become fairly intrusive to the text. I imagine there are other situations where the resolution of the paragraph is inconvenient as a reference (such as anything written by John Locke). Formatting issues could alleviate the noise (consider the contemporary example set by &lt;a href=&quot;http://en.wikipedia.org/wiki/Ruby_characters&quot; rel=&quot;nofollow&quot;&gt;ruby characters&lt;/a&gt;).

That said, it&#039;s a small niggle of an insightful look at ways to break ebooks out of their book heritage. I keep getting excited at the thought of putting a PDF on my iPod Touch for easy reference on the go, but the reality is that it&#039;s a royal pain to actually reference them in that format.</description>
		<content:encoded><![CDATA[<p>There is still some assumption about content built into the Book, Chapter, and Verse style of content markup, which is that the Verse that is marked up by a number is going to be a significant amount of text and so the markup will not have too much overhead. Visually, a paragraph number is not very much noise while reading if the paragraphs are large, but there are classes of content that don&#8217;t match that assumption.</p>
<p>The example I have foremost in mind is large sections of dialogue, where the paragraph markers would become line markers and so become fairly intrusive to the text. I imagine there are other situations where the resolution of the paragraph is inconvenient as a reference (such as anything written by John Locke). Formatting issues could alleviate the noise (consider the contemporary example set by <a href="http://en.wikipedia.org/wiki/Ruby_characters" rel="nofollow">ruby characters</a>).</p>
<p>That said, it&#8217;s a small niggle of an insightful look at ways to break ebooks out of their book heritage. I keep getting excited at the thought of putting a PDF on my iPod Touch for easy reference on the go, but the reality is that it&#8217;s a royal pain to actually reference them in that format.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: halfjack</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-226</link>
		<dc:creator>halfjack</dc:creator>
		<pubDate>Fri, 27 Nov 2009 22:52:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-226</guid>
		<description>Just realised that a paragraph number as an index into the text needs to be uniquely searchable if it&#039;s to be independent from reader software functions. That means a unique character (already have a pilcrow I guess) and an increasing number (never reset to 1 in the same book). Or leading zeroes and increasing.</description>
		<content:encoded><![CDATA[<p>Just realised that a paragraph number as an index into the text needs to be uniquely searchable if it&#8217;s to be independent from reader software functions. That means a unique character (already have a pilcrow I guess) and an increasing number (never reset to 1 in the same book). Or leading zeroes and increasing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: halfjack</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-223</link>
		<dc:creator>halfjack</dc:creator>
		<pubDate>Fri, 27 Nov 2009 20:50:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-223</guid>
		<description>Sorry, not all of what happens on the web. Whenever we make assumptions about absolute space (pixels) we design badly for the web but we design anyway. The same criteria for design quality would apply and be abused for any reflowable content device.</description>
		<content:encoded><![CDATA[<p>Sorry, not all of what happens on the web. Whenever we make assumptions about absolute space (pixels) we design badly for the web but we design anyway. The same criteria for design quality would apply and be abused for any reflowable content device.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: halfjack</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-222</link>
		<dc:creator>halfjack</dc:creator>
		<pubDate>Fri, 27 Nov 2009 20:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-222</guid>
		<description>I don&#039;t think I was clear there -- yes, commercial interests are a barrier to the success of a &quot;better&quot; new technology and this has always been the case. Frequently, however, a wave of failures (c.f. Xerox) is followed (when the time is right commercially) with sudden adoption (c.f. Windows and Mac). The web is already pointing the way with font and layout -- all of what is done on the web is friendly to a hypothetical e-reader of today.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think I was clear there &#8212; yes, commercial interests are a barrier to the success of a &#8220;better&#8221; new technology and this has always been the case. Frequently, however, a wave of failures (c.f. Xerox) is followed (when the time is right commercially) with sudden adoption (c.f. Windows and Mac). The web is already pointing the way with font and layout &#8212; all of what is done on the web is friendly to a hypothetical e-reader of today.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: halfjack</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-221</link>
		<dc:creator>halfjack</dc:creator>
		<pubDate>Fri, 27 Nov 2009 20:45:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-221</guid>
		<description>Fred, yes, I think that there is an artistic and commercial interest that is not well addressed. However, pointing to web pages is an illuminating example: your web page cannot tell me what font to use, and yet we see a proliferation of web pages (commercial, some of them!). What it can do is offer hints, and this would be a good addition to ebook formats (and, frankly, it&#039;s already in most of them). Your web page can say &quot;use Garamond and, failing that, any serifed font&quot; but the only way it can say &quot;these letters look exactly like this&quot; is to send an image rather than logical text. That is also available in ebook formats. I think what is missing is solely sophistication in the producers of electronic text -- right now they are mostly automatic (and naive) conversions from old data.

Lanfranc, my issue with a facsimile is that it fails to take advantage of the possibilities inherent in unpaginated text. Paginated text is, logically, a subset of paginated text and therefore less powerful intrinsically. Adobe itself chose to develop &quot;reflowable&quot; formats (ePub) rather than retrofit PDF precisely because (I think) a correctly retooled PDF would in fact be a reflowable format, and patching an already aging construct was probably less viable for them than building from the foundation of an intrinsically more powerful idea.</description>
		<content:encoded><![CDATA[<p>Fred, yes, I think that there is an artistic and commercial interest that is not well addressed. However, pointing to web pages is an illuminating example: your web page cannot tell me what font to use, and yet we see a proliferation of web pages (commercial, some of them!). What it can do is offer hints, and this would be a good addition to ebook formats (and, frankly, it&#8217;s already in most of them). Your web page can say &#8220;use Garamond and, failing that, any serifed font&#8221; but the only way it can say &#8220;these letters look exactly like this&#8221; is to send an image rather than logical text. That is also available in ebook formats. I think what is missing is solely sophistication in the producers of electronic text &#8212; right now they are mostly automatic (and naive) conversions from old data.</p>
<p>Lanfranc, my issue with a facsimile is that it fails to take advantage of the possibilities inherent in unpaginated text. Paginated text is, logically, a subset of paginated text and therefore less powerful intrinsically. Adobe itself chose to develop &#8220;reflowable&#8221; formats (ePub) rather than retrofit PDF precisely because (I think) a correctly retooled PDF would in fact be a reflowable format, and patching an already aging construct was probably less viable for them than building from the foundation of an intrinsically more powerful idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lanfranc</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-220</link>
		<dc:creator>Lanfranc</dc:creator>
		<pubDate>Fri, 27 Nov 2009 20:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-220</guid>
		<description>These are all good observations, but couldn&#039;t most of these issues be solved by improving the ability of e-readers to handle PDF formats? 

I understand that you don&#039;t want simply a digital facsimile, but it does seem that this is the best way to get a correlation, especially since it can be done improving the already available technology, rather than (re-)inventing entirely new ways of doing essentially the same thing.</description>
		<content:encoded><![CDATA[<p>These are all good observations, but couldn&#8217;t most of these issues be solved by improving the ability of e-readers to handle PDF formats? </p>
<p>I understand that you don&#8217;t want simply a digital facsimile, but it does seem that this is the best way to get a correlation, especially since it can be done improving the already available technology, rather than (re-)inventing entirely new ways of doing essentially the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred Hicks</title>
		<link>http://www.vsca.ca/halfjack/?p=204&#038;cpage=1#comment-219</link>
		<dc:creator>Fred Hicks</dc:creator>
		<pubDate>Fri, 27 Nov 2009 20:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.vsca.ca/halfjack/?p=204#comment-219</guid>
		<description>I&#039;m not completely sold on the idea of the &quot;new world&quot; giving us a complete and total freedom from font/presentation elements.  We had that for a time before you could inflict your own style and layout choices in webpages, and frankly it was something of a barrier to commercial interest in that.  

Commercial interest -- a potential prime driver of technology in this case, at least as far as adoption goes -- is going to demand some preservation of presentation control, because presentation control allows the commercial entities to enforce brand awareness and to control how the commercial value of the content is delivered to the end consumer.

TiVo crushed the rest of the DVR market early on because they deliberately worked on strategies to play well with the commercial interests of advertisers (which is why a 30-second skip option on TiVos is a deeply buried feature and not enabled by default, among other things).  So ceding some amount of presentation control to commercial interests is going to better enable the rest of the ideal implementation of our hypothetical badass e-reader of tomorrow.</description>
		<content:encoded><![CDATA[<p>I&#8217;m not completely sold on the idea of the &#8220;new world&#8221; giving us a complete and total freedom from font/presentation elements.  We had that for a time before you could inflict your own style and layout choices in webpages, and frankly it was something of a barrier to commercial interest in that.  </p>
<p>Commercial interest &#8212; a potential prime driver of technology in this case, at least as far as adoption goes &#8212; is going to demand some preservation of presentation control, because presentation control allows the commercial entities to enforce brand awareness and to control how the commercial value of the content is delivered to the end consumer.</p>
<p>TiVo crushed the rest of the DVR market early on because they deliberately worked on strategies to play well with the commercial interests of advertisers (which is why a 30-second skip option on TiVos is a deeply buried feature and not enabled by default, among other things).  So ceding some amount of presentation control to commercial interests is going to better enable the rest of the ideal implementation of our hypothetical badass e-reader of tomorrow.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
