<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>geolocation &#8211; API UX</title>
	<atom:link href="/tag/geolocation/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Everything about API User Experience</description>
	<lastBuildDate>Wed, 11 Sep 2013 18:44:57 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.8.6</generator>
	<item>
		<title>When API time zones make the difference</title>
		<link>/2013/09/11/api-timezones/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=api-timezones</link>
					<comments>/2013/09/11/api-timezones/#respond</comments>
		
		<dc:creator><![CDATA[Jason Harmon]]></dc:creator>
		<pubDate>Wed, 11 Sep 2013 16:00:35 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[geolocation]]></category>
		<category><![CDATA[globalization]]></category>
		<category><![CDATA[localization]]></category>
		<category><![CDATA[timezone]]></category>
		<category><![CDATA[UTC]]></category>
		<guid isPermaLink="false">/?p=618</guid>

					<description><![CDATA[Globalizing APIs is hard. I&#8217;ve posted before about some of the pitfalls of dates and times in APIs in The 5 Laws of API Dates and Times, as well as content and currency localization in How to Localize Your API . One area that I did not get into was how timezones can play a [&#8230;]]]></description>
		
					<wfw:commentRss>/2013/09/11/api-timezones/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
