<?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>endpoint &#8211; API UX</title>
	<atom:link href="/tag/endpoint/feed/" rel="self" type="application/rss+xml" />
	<link>/</link>
	<description>Everything about API User Experience</description>
	<lastBuildDate>Sun, 31 Aug 2014 20:18:36 +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>Endpoint speaker highlight: Kamyar Mohager</title>
		<link>/2014/09/01/endpoint-kamyar-mohager/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=endpoint-kamyar-mohager</link>
					<comments>/2014/09/01/endpoint-kamyar-mohager/#respond</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Mon, 01 Sep 2014 16:00:29 +0000</pubDate>
				<category><![CDATA[Conference]]></category>
		<category><![CDATA[Interview]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[authorization]]></category>
		<category><![CDATA[conference]]></category>
		<category><![CDATA[endpoint]]></category>
		<category><![CDATA[interview]]></category>
		<category><![CDATA[Kamyar]]></category>
		<category><![CDATA[Linkedin]]></category>
		<category><![CDATA[Mohager]]></category>
		<category><![CDATA[monitoring]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[platform]]></category>
		<category><![CDATA[strategy]]></category>
		<guid isPermaLink="false">/?p=1092</guid>

					<description><![CDATA[To give you a feeling of what to expect at the Endpoint conference we've talked with Kamyar Mohager, who will be in Amsterdam representing Linkedin.]]></description>
		
					<wfw:commentRss>/2014/09/01/endpoint-kamyar-mohager/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Review: Google Glass API</title>
		<link>/2013/04/17/review-google-glass-api/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=review-google-glass-api</link>
					<comments>/2013/04/17/review-google-glass-api/#comments</comments>
		
		<dc:creator><![CDATA[Bruno Pedro]]></dc:creator>
		<pubDate>Wed, 17 Apr 2013 16:00:31 +0000</pubDate>
				<category><![CDATA[Review]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[endpoint]]></category>
		<category><![CDATA[Glass]]></category>
		<category><![CDATA[Glassware]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Mirror]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[timeline]]></category>
		<guid isPermaLink="false">/?p=296</guid>

					<description><![CDATA[Since Google's announcement of Glass people have been wondering on the possible applications that can be built on it and how it might increase one's productivity. Well, your wait is over now, because Google has just recently released the documentation on how to interact with Glass through their Mirror API.]]></description>
		
					<wfw:commentRss>/2013/04/17/review-google-glass-api/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>URL Design for RESTful Web Services</title>
		<link>/2013/04/03/url-design-restful-web-services/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=url-design-restful-web-services</link>
					<comments>/2013/04/03/url-design-restful-web-services/#comments</comments>
		
		<dc:creator><![CDATA[Charlie Reverte]]></dc:creator>
		<pubDate>Wed, 03 Apr 2013 16:00:54 +0000</pubDate>
				<category><![CDATA[Opinion]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[endpoint]]></category>
		<category><![CDATA[filesystem]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[REST]]></category>
		<category><![CDATA[URL]]></category>
		<category><![CDATA[Web service]]></category>
		<guid isPermaLink="false">/?p=233</guid>

					<description><![CDATA[URL design discussions for RESTful web services often degrade into debates over pluralization and parameter names. There are a couple of principles I like to use to keep things simple.]]></description>
		
					<wfw:commentRss>/2013/04/03/url-design-restful-web-services/feed/</wfw:commentRss>
			<slash:comments>12</slash:comments>
		
		
			</item>
	</channel>
</rss>
