<?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>≈ Relations &#187; api</title>
	<atom:link href="http://relations.ka2.de/tag/api/feed/" rel="self" type="application/rss+xml" />
	<link>http://relations.ka2.de</link>
	<description>Random Rants and Ramblings about Media and/or Technology</description>
	<lastBuildDate>Thu, 09 Sep 2010 01:31:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<atom:link rel='hub' href='http://relations.ka2.de/?pushpress=hub'/>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com" />
	<atom:link rel="hub" href="http://superfeedr.com/hubbub" />
	<atom:link rel="hub" href="http://nuwzhub.appspot.com" />
			<item>
		<title>NPR API is Live on NPR.org [NPR.org]</title>
		<link>http://relations.ka2.de/2008/07/18/npr-api-is-live-on-nprorg-nprorg/</link>
		<comments>http://relations.ka2.de/2008/07/18/npr-api-is-live-on-nprorg-nprorg/#comments</comments>
		<pubDate>Fri, 18 Jul 2008 10:57:15 +0000</pubDate>
		<dc:creator>gkamp</dc:creator>
				<category><![CDATA[Fresh from the press]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[journalism]]></category>
		<category><![CDATA[npr]]></category>

		<guid isPermaLink="false">http://relations.ka2.de/?p=654</guid>
		<description><![CDATA[Quotes from NPR: NPR API is Live on NPR.org (via PaidContent): As referenced in yesterday&#8217;s post, we launched our new API today. To find the API, you can either go directly to http://www.npr.org/api/ or you can follow the new link called &#8220;Tools / API&#8221; on the NPR.org left nav under the Services section. &#8230; There [...]]]></description>
			<content:encoded><![CDATA[<p>Quotes from  <cite><a href="http://www.npr.org/blogs/inside/2008/07/npr_api_is_live_on_nprorg.html">NPR: NPR API is Live on NPR.org </a> </cite> (via <a href="http://www.paidcontent.org/entry/419-npr-launches-open-api-major-shows-not-included/" target="_blank">PaidContent):</a></p>
<blockquote><p>As referenced in yesterday&#8217;s post, we launched our new API today. To find the API, you can either go directly to http://www.npr.org/api/ or you can follow the new link called &#8220;Tools / API&#8221; on the NPR.org left nav under the Services section.</p></blockquote>
<p>&#8230;</p>
<blockquote><p>There were quite a few questions that we addressed when developing the API, but one thing that was not really in question was the need to open as much of our content as possible. As a result, almost everything that you can find on NPR.org that we have the rights to redistribute is available through the API. This includes audio, images, full text, etc. That said, there are elements, series and programs that we could not offer due to rights restrictions.</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://relations.ka2.de/2008/07/18/npr-api-is-live-on-nprorg-nprorg/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google hints at plans to monetize mapping api</title>
		<link>http://relations.ka2.de/2006/06/14/google-hints-at-plans-to-monetize-mapping-api/</link>
		<comments>http://relations.ka2.de/2006/06/14/google-hints-at-plans-to-monetize-mapping-api/#comments</comments>
		<pubDate>Wed, 14 Jun 2006 15:43:31 +0000</pubDate>
		<dc:creator>gkamp</dc:creator>
				<category><![CDATA[Noteworthy]]></category>
		<category><![CDATA[api]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[mapping]]></category>
		<category><![CDATA[media]]></category>

		<guid isPermaLink="false">http://relations.ka2.de/?p=17</guid>
		<description><![CDATA[Yesterday, Google announced Google Maps for Enterprise (US an Canada only right now). Since i was alsways wondering what Google&#8217;s plan were to monetize Google maps i had a look into the FAQ: Q: Will Google Maps for Enterprise incorporate advertising? A: If and when advertising is displayed on Google Maps, you will have the [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday, Google announced Google Maps for Enterprise (US an Canada only right now). Since i was alsways wondering what Google&#8217;s plan were to monetize Google maps i had a look into the <a href="http://www.google.com/enterprise/maps/faq.html">FAQ</a>:</p>
<blockquote><p>Q: Will Google Maps for Enterprise incorporate advertising?<br />
A: If and when advertising is displayed on Google Maps, you will have the option to enable (or disable) any advertising in Google Maps for Enterprise at your discretion.</p>
<p>Q: What is the cost of Google Maps for Enterprise?<br />
A: Pricing for Google Maps for Enterprise is based on the number of page views and geocode requests handled by the Google Maps for Enterprise API and starts at $10,000 per year. Please contact us for more information.</p>
<p>Q: Why would I pay for Google Maps for Enterprise if the Google Maps API is free?<br />
A: Google Maps for Enterprise offers several features worth paying for, including implementation guidance, telephone support <strong>and the ability to use Google Maps for internal and external commercial applications</strong>. And of course, if and when we start to display advertising on Google Maps, it is optional to include or exclude it in Google Maps for Enterprise (we hope you find it so useful that you choose to include it).</p>
<p>Q: What are the licensing terms for Google Maps for Enterprise?<br />
A: Google Maps for Enterprise is licensed for commercial use for internal applications as well as public facing sites.</p></blockquote>
<p>This announcement (especially the highlighted part) immediately started a <a href="http://groups.google.de/group/Google-Maps-API/browse_thread/thread/1425b213807daf5b/d85ee1a1b0b31e04#d85ee1a1b0b31e04">discussion </a>on the respective Google group.</p>
<blockquote><p>Uh, until now the Google Maps API most definitely HAS permitted &#8220;using<br />
the API for commercial applications&#8221;: Item (4) of the API FAQ<br />
(<a target="_blank" href="http://www.google.com/url?sa=D&#038;q=http://www.google.com/apis/maps/faq.html">http://www.google.com/apis/maps/faq.html</a>) says:<br />
&#8220;4. Is the Maps API available for commercial websites?<br />
Yes, it is, as long your site is generally accessible to consumers<br />
without charge. For example, if your website is supported by<br />
advertising, it likely falls within the terms of the Maps API. Or, if<br />
you charge people to place information on your map (e.g., to list their<br />
homes for sale), but you list this information on Google Maps on a free<br />
part of your site, you&#8217;ll also meet the Maps API terms of use.&#8221;<br />
That same item says, at the bottom, &#8220;Remember, Google reserves the<br />
right to suspend or terminate the use of the service at any time, so<br />
please read the terms of use carefully.&#8221;</p>
<p><strong>Is Google changing the terms to prohibit commercial use of the API?</strong></p>
<p>&#8230;</p></blockquote>
<blockquote><p>No, this isn&#8217;t a change. We&#8217;ll get a fix to clarify the language here.<br />
Essentially, our enterprise offering is for clients that require control of<br />
the display of our maps. <strong>Nothing has changed regarding the commercial use of<br />
the free Maps API.</strong></p></blockquote>
<p>So on one hand we shouldn&#8217;t have to wait too long for ads within google maps. But on the other hand it is more or less clear now, that companies that want to use the Google Map API for mapping without ads are not building their business on quicksand. Only the pricing (especially for public facing sites)</p>
]]></content:encoded>
			<wfw:commentRss>http://relations.ka2.de/2006/06/14/google-hints-at-plans-to-monetize-mapping-api/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
