<?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/"
		>
<channel>
	<title>Comments on: GSMA 3rd Party Access initiative &#8211; API enabing the network operator</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html</link>
	<description>Wireless mobility - Innovation - Digital convergence - mobile web 2.0</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:47:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Kevin Smith</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1598</link>
		<dc:creator>Kevin Smith</dc:creator>
		<pubDate>Mon, 07 Jul 2008 09:25:15 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1598</guid>
		<description>@Stefan:
Yes, the intention here is not that the API be innovative in and of itself, but rather provide easy access to more basic capabilities which help stimulate innovation. The API is intended to be accessible from the client side (widgets, XHR, native HTTP requests) as well as from the server side (bindings to Java, Ruby, Python etc.), so the aim is to be a useful part of the overall developer toolkit, and help reduce the portability problems between networks. Even if the API can only save developers time integrating, then at least they can spend more time innovating :)
</description>
		<content:encoded><![CDATA[<p>@Stefan:<br />
Yes, the intention here is not that the API be innovative in and of itself, but rather provide easy access to more basic capabilities which help stimulate innovation. The API is intended to be accessible from the client side (widgets, XHR, native HTTP requests) as well as from the server side (bindings to Java, Ruby, Python etc.), so the aim is to be a useful part of the overall developer toolkit, and help reduce the portability problems between networks. Even if the API can only save developers time integrating, then at least they can spend more time innovating <img src='http://www.opengardensblog.futuretext.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guenter</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1597</link>
		<dc:creator>Guenter</dc:creator>
		<pubDate>Mon, 07 Jul 2008 07:23:19 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1597</guid>
		<description>For Stefan: May I ask, what you mean with &quot;at the node&quot;? From my perspective, web apps can benefit from information available in the network through network-side APIs and through device-side APIs. If I compare a device-resident web app (downloaded) with a Java app: the former can access device capabilities and info collected from the network via device APIs AND access network information via a server-side network API into the operator. The latter typically uses a device API (JSR) to get the info out of the device. Could we argue, the former solution is more comprehensive, more flexible?
</description>
		<content:encoded><![CDATA[<p>For Stefan: May I ask, what you mean with &#8220;at the node&#8221;? From my perspective, web apps can benefit from information available in the network through network-side APIs and through device-side APIs. If I compare a device-resident web app (downloaded) with a Java app: the former can access device capabilities and info collected from the network via device APIs AND access network information via a server-side network API into the operator. The latter typically uses a device API (JSR) to get the info out of the device. Could we argue, the former solution is more comprehensive, more flexible?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stefan Constantinescu</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1596</link>
		<dc:creator>Stefan Constantinescu</dc:creator>
		<pubDate>Fri, 04 Jul 2008 16:05:09 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1596</guid>
		<description>I&#039;m still holding my firm belief that innovation of this sort does not happen at the network level, but instead at the node.
</description>
		<content:encoded><![CDATA[<p>I&#8217;m still holding my firm belief that innovation of this sort does not happen at the network level, but instead at the node.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sanhil</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1595</link>
		<dc:creator>Sanhil</dc:creator>
		<pubDate>Thu, 03 Jul 2008 18:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1595</guid>
		<description>Sounds like the idea on this site &lt;a href=&quot;http://www.synapsim.com&quot; rel=&quot;nofollow&quot;&gt;http://www.synapsim.com&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>Sounds like the idea on this site <a href="http://www.synapsim.com" rel="nofollow">http://www.synapsim.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajit Jaokar</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1594</link>
		<dc:creator>Ajit Jaokar</dc:creator>
		<pubDate>Wed, 02 Jul 2008 17:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1594</guid>
		<description>Thanks Jyoti! rgds Ajit
</description>
		<content:encoded><![CDATA[<p>Thanks Jyoti! rgds Ajit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jyoti Narula Ranjan</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1593</link>
		<dc:creator>Jyoti Narula Ranjan</dc:creator>
		<pubDate>Wed, 02 Jul 2008 14:18:02 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1593</guid>
		<description>Thanks Ajit.
This sure is a very good beginning.
Of course the next step of having operators commit to implementing this set of APIs will be a more looked forward to step.
I first read it at your blog - thanks/
Jyoti
</description>
		<content:encoded><![CDATA[<p>Thanks Ajit.<br />
This sure is a very good beginning.<br />
Of course the next step of having operators commit to implementing this set of APIs will be a more looked forward to step.<br />
I first read it at your blog &#8211; thanks/<br />
Jyoti</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ajit Jaokar</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1592</link>
		<dc:creator>Ajit Jaokar</dc:creator>
		<pubDate>Wed, 02 Jul 2008 12:18:03 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1592</guid>
		<description>Thanks Graham!Its great to get a comment from you on my blog. I have created a new post to include this link so it wont be missed. kind rgds Ajit
</description>
		<content:encoded><![CDATA[<p>Thanks Graham!Its great to get a comment from you on my blog. I have created a new post to include this link so it wont be missed. kind rgds Ajit</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Trickey</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2008/07/gsma_3rd_party.html/comment-page-1#comment-1591</link>
		<dc:creator>Graham Trickey</dc:creator>
		<pubDate>Wed, 02 Jul 2008 09:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2008/07/gsma_3rd_party.html#comment-1591</guid>
		<description>Thank you for your comments on the GSMA 3rd Party Access project. Please note that the URL for the 3rd Party Access Portal is &lt;a href=&quot;https://gsma.securespsite.com/access/entry&quot; rel=&quot;nofollow&quot;&gt;https://gsma.securespsite.com/access/entry&lt;/a&gt;
</description>
		<content:encoded><![CDATA[<p>Thank you for your comments on the GSMA 3rd Party Access project. Please note that the URL for the 3rd Party Access Portal is <a href="https://gsma.securespsite.com/access/entry" rel="nofollow">https://gsma.securespsite.com/access/entry</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
