<?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>nathanfish.com &#187; Yahoo</title>
	<atom:link href="http://www.nathanfish.com/tag/yahoo/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nathanfish.com</link>
	<description>ecommerce, saas, and small business</description>
	<lastBuildDate>Tue, 20 Apr 2010 20:29:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Yahoo Shuts Down Shopping API</title>
		<link>http://www.nathanfish.com/2010/01/11/yahoo-shuts-down-shopping-api/</link>
		<comments>http://www.nathanfish.com/2010/01/11/yahoo-shuts-down-shopping-api/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 23:58:15 +0000</pubDate>
		<dc:creator>nathan</dc:creator>
				<category><![CDATA[Web Services]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Yahoo]]></category>

		<guid isPermaLink="false">http://www.nathanfish.com/?p=358</guid>
		<description><![CDATA[Yahoo has offered one of the broadest ranges of API&#8217;s for developers. The breadth has made it possible for numerous entrepreneurs to build out supplemental incomes or be their own boss businesses. However, as they begin to realign their business and strategies they have begun to kill off the API&#8217;s that made them so popular [...]]]></description>
			<content:encoded><![CDATA[<p><span class="drop">Y</span>ahoo has offered one of the broadest ranges of API&#8217;s for developers. The breadth has made it possible for numerous entrepreneurs to build out supplemental incomes or be their own boss businesses. However, as they begin to realign their business and strategies they have begun to kill off the API&#8217;s that made them so popular with developer/entrepreneur. The recent end of life for the Shopping API and the backlash highlights the risks in providing API&#8217;s http://developer.yahoo.net/blog/archives/2010/01/yahoo_shopping_api_announcement.html and the impact it has when you find API&#8217;s don&#8217;t offer value to the bottom line. They may have offered growth but that growth becomes a risk as costs overcome generated revenue. Many have lost their faith in Yahoo as an API end point and have begun looking for business continuity through other partners. My own thoughts go to other businesses that offer API&#8217;s that other small business rely on to make money, for example Twitter or Facebook for that matter. At what point does that provisioning become a risk and how is it addressed? What models are in place, what needs will there be in the future? Limitation on calls? Pay-for-provisioning? Revenue sharing? The model will be heavily dependent on the nature of the business. If the API provides direct revenue to the provider then it would be possible to pay people for API usage not charge them. Citysearch does this, but are there other businesses that could do the same?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.nathanfish.com/2010/01/11/yahoo-shuts-down-shopping-api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Yahoo YQL – Web Service Innovation</title>
		<link>http://www.nathanfish.com/2009/05/07/yahoo-yql-%e2%80%93-web-service-innovation/</link>
		<comments>http://www.nathanfish.com/2009/05/07/yahoo-yql-%e2%80%93-web-service-innovation/#comments</comments>
		<pubDate>Thu, 07 May 2009 18:39:58 +0000</pubDate>
		<dc:creator>nathan</dc:creator>
				<category><![CDATA[Web Services]]></category>
		<category><![CDATA[Yahoo]]></category>

		<guid isPermaLink="false">http://nathanfish.com/?p=42</guid>
		<description><![CDATA[Yahoo recently launched YQL http://developer.yahoo.com/yql/ it provides developers with unique and compelling access to structured data. Instead of calling different web service interfaces that have limited inputs and limited outputs, you simply write a query. This is brilliant. As a developer I previously had to call multiple services, using different inputs, capture all the data [...]]]></description>
			<content:encoded><![CDATA[<p><span class="drop">Y</span>ahoo recently launched YQL http://developer.yahoo.com/yql/ it provides developers with unique and compelling access to structured data. Instead of calling different web service interfaces that have limited inputs and limited outputs, you simply write a query. This is brilliant. As a developer I previously had to call multiple services, using different inputs, capture all the data and merge it into a meaningful experience for the user. Now all I have to do is create a single query, get the data in the way I want and present to the user. It’s like righting a SQL query, with joins, and all the other fancy stuff. This is cutting edge stuff and I’m very interested in seeing who will be next to support something like this.  Personally Google Analytics comes to mind. Right now their API is very limiting, and highlights the challenges with current API development. The interface can be very limiting for the developer. Limiting applicability or causing inefficient use of API’s to achieve results. I have seen, for example, a loop through thousands of results from one API to get additional details on each of the items in the result. YQL will certainly allow a developer to avoid that mess. Now if only I could use proxy YQL service to mashup sources across platforms, get data from Yahoo, Amazon, Ebay, Google in a single YQL like call. Dreams, I know, but the amazing consumer applications that could be created, easily and without any fuss. Add in some data portability and I’m in mashup heaven. </p>
<p><strong>Update:</strong> YQL does allow you to access other web services using the YQL syntax, its called &#8220;YQL Open Tables&#8221;. You simply define a few things in an XML file and you can use YQL to query Amazon products, etc. This is really great stuff. Thanks to spullara for pointing it out. </p>
]]></content:encoded>
			<wfw:commentRss>http://www.nathanfish.com/2009/05/07/yahoo-yql-%e2%80%93-web-service-innovation/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
