<?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: The ‘Issy-Neale Formula’ Explained Part 3</title>
	<atom:link href="http://www.dailydooh.com/archives/18478/feed" rel="self" type="application/rss+xml" />
	<link>http://www.dailydooh.com/archives/18478</link>
	<description>Digital Out Of Home - Insight, Knowledge and Opinion</description>
	<lastBuildDate>Sun, 12 Feb 2012 09:44:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Dan Schwass</title>
		<link>http://www.dailydooh.com/archives/18478/comment-page-1#comment-236958</link>
		<dc:creator>Dan Schwass</dc:creator>
		<pubDate>Fri, 13 Jan 2012 15:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydooh.com/?p=18478#comment-236958</guid>
		<description>So far, so good... But is there any provision for orientation of the display/projector elements?

For example, all of the elements might be landscape, all might be portrait, or there may be a mixture in the overall wall. Worst case (if the designers had complete reign!), there could also be mixtures of elements with different resolutions (1366 x 768 vs. 1980 x 1080) or even different aspect ratios (much less likely if the system designers get a say!).</description>
		<content:encoded><![CDATA[<p>So far, so good&#8230; But is there any provision for orientation of the display/projector elements?</p>
<p>For example, all of the elements might be landscape, all might be portrait, or there may be a mixture in the overall wall. Worst case (if the designers had complete reign!), there could also be mixtures of elements with different resolutions (1366 x 768 vs. 1980 x 1080) or even different aspect ratios (much less likely if the system designers get a say!).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Neale</title>
		<link>http://www.dailydooh.com/archives/18478/comment-page-1#comment-36829</link>
		<dc:creator>Andrew Neale</dc:creator>
		<pubDate>Mon, 16 Nov 2009 11:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydooh.com/?p=18478#comment-36829</guid>
		<description>Our aim was to create something that was both easily human-readable and machine-readable, and to keep it well structured, but also as simple as possible.

If we were to drop the 1 in the 1H2T1H term, it would effectively be mixing the short and long definitions in the same row term. I agree that it would be easier to read and interpret from a human point of view, but it would make machine-readable parsing more difficult (although obviously not impossible), and in the interests of simple structure and conformity, we decided that it was best not to mix the two within an individual row term.</description>
		<content:encoded><![CDATA[<p>Our aim was to create something that was both easily human-readable and machine-readable, and to keep it well structured, but also as simple as possible.</p>
<p>If we were to drop the 1 in the 1H2T1H term, it would effectively be mixing the short and long definitions in the same row term. I agree that it would be easier to read and interpret from a human point of view, but it would make machine-readable parsing more difficult (although obviously not impossible), and in the interests of simple structure and conformity, we decided that it was best not to mix the two within an individual row term.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan Crotaz</title>
		<link>http://www.dailydooh.com/archives/18478/comment-page-1#comment-36819</link>
		<dc:creator>Bryan Crotaz</dc:creator>
		<pubDate>Mon, 16 Nov 2009 08:21:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.dailydooh.com/?p=18478#comment-36819</guid>
		<description>Lose the 1 in 1H2T1H - it&#039;s not adding anything.  Then you can describe the row as H2TH for greater clarity.</description>
		<content:encoded><![CDATA[<p>Lose the 1 in 1H2T1H &#8211; it&#8217;s not adding anything.  Then you can describe the row as H2TH for greater clarity.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

