<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Abolish Time Zones</title>
	<atom:link href="http://smidg.in/2010/01/17/abolish-time-zones/feed/" rel="self" type="application/rss+xml" />
	<link>http://smidg.in/2010/01/17/abolish-time-zones/</link>
	<description>A Sporadic Blogger</description>
	<lastBuildDate>Wed, 14 Jul 2010 07:48:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Jim</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4085</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 19 Jan 2010 13:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4085</guid>
		<description>Very good points. (Krista, see the footnote.) Perhaps what would be required is a sort of  hybrid system. The actual o&#039;clock hours would be standard, but you would have a way of saying &quot;three hours after noon.&quot; Not as easy as 3 p.m., but it would solve the problem.

Steve, I would disagree with your last bit. We&#039;ll eat at 11:30 would make perfect sense in any given place, because people would know that 11:30 is around the time for breakfast, for instance. Just like we now know that 11:30 is around the time for lunch. It&#039;s hard to think about it that way now, but I think the context of the hours would shift. You would only have a problem when out of the given context (like your news example.)</description>
		<content:encoded><![CDATA[<p>Very good points. (Krista, see the footnote.) Perhaps what would be required is a sort of  hybrid system. The actual o&#8217;clock hours would be standard, but you would have a way of saying &#8220;three hours after noon.&#8221; Not as easy as 3 p.m., but it would solve the problem.</p>
<p>Steve, I would disagree with your last bit. We&#8217;ll eat at 11:30 would make perfect sense in any given place, because people would know that 11:30 is around the time for breakfast, for instance. Just like we now know that 11:30 is around the time for lunch. It&#8217;s hard to think about it that way now, but I think the context of the hours would shift. You would only have a problem when out of the given context (like your news example.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4084</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Tue, 19 Jan 2010 06:09:51 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4084</guid>
		<description>To elaborate on your &quot;what would we lose&quot;, using universal UTC would have the side effect of removing all context-sensitive information from times. This could be very unhelpful in the context of, say, journalism or literature (especially past literature) -- anything read across time zones. For instance, a book that mentions that the protagonist &quot;got up at 5 AM every day and was in bed by 9 each night&quot; has a connotation of self-discipline now which would be completely lost. Compare, for example, &quot;got up at 11 AM every day and went to bed at 3 AM&quot;. Nearly the same phrasing; totally different connotation due to the time shift. Or a news article that mentions that a fire broke out at 2 PM would instead have to specify the time and a context (eg. &quot;2 PM, that is early afternoon here in ____&quot;), since there wouldn&#039;t be any inherent local context for the time. (You could say the news could just say &quot;early afternoon&quot;, but in the interest of specificity that wouldn&#039;t be ideal.) This could even impact business communication, as you would have to specify which shift (evening, morning, etc) when giving hours/meal times/etc if the time was important for giving context. (EG, &quot;we&#039;ll eat at 11:30&quot; would have to be &quot;we&#039;ll eat lunch at 11:30&quot; since 11:30 is arbitrary.) Etc.</description>
		<content:encoded><![CDATA[<p>To elaborate on your &#8220;what would we lose&#8221;, using universal UTC would have the side effect of removing all context-sensitive information from times. This could be very unhelpful in the context of, say, journalism or literature (especially past literature) &#8212; anything read across time zones. For instance, a book that mentions that the protagonist &#8220;got up at 5 AM every day and was in bed by 9 each night&#8221; has a connotation of self-discipline now which would be completely lost. Compare, for example, &#8220;got up at 11 AM every day and went to bed at 3 AM&#8221;. Nearly the same phrasing; totally different connotation due to the time shift. Or a news article that mentions that a fire broke out at 2 PM would instead have to specify the time and a context (eg. &#8220;2 PM, that is early afternoon here in ____&#8221;), since there wouldn&#8217;t be any inherent local context for the time. (You could say the news could just say &#8220;early afternoon&#8221;, but in the interest of specificity that wouldn&#8217;t be ideal.) This could even impact business communication, as you would have to specify which shift (evening, morning, etc) when giving hours/meal times/etc if the time was important for giving context. (EG, &#8220;we&#8217;ll eat at 11:30&#8243; would have to be &#8220;we&#8217;ll eat lunch at 11:30&#8243; since 11:30 is arbitrary.) Etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krista</title>
		<link>http://smidg.in/2010/01/17/abolish-time-zones/#comment-4083</link>
		<dc:creator>Krista</dc:creator>
		<pubDate>Mon, 18 Jan 2010 23:20:49 +0000</pubDate>
		<guid isPermaLink="false">http://smidg.in/?p=644#comment-4083</guid>
		<description>&quot;if, for example, the sun was always directly overhead at five o’clock p.m ...&quot; 

If we&#039;re going to ditch time zones, than for goodness&#039; sake, let&#039;s get rid of the 12 hour clock while we&#039;re at it! 17 hours, no 5 pm :)</description>
		<content:encoded><![CDATA[<p>&#8220;if, for example, the sun was always directly overhead at five o’clock p.m &#8230;&#8221; </p>
<p>If we&#8217;re going to ditch time zones, than for goodness&#8217; sake, let&#8217;s get rid of the 12 hour clock while we&#8217;re at it! 17 hours, no 5 pm :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
