<?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: Mobile mashups: The implications of ‘Data is the intelligence’ on mobile software development</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.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: Thomas Menguy</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.html/comment-page-1#comment-837</link>
		<dc:creator>Thomas Menguy</dc:creator>
		<pubDate>Thu, 28 Sep 2006 10:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2006/09/mobile_mashups.html#comment-837</guid>
		<description>Yes data is the central point, and the way to provide it to the user (to represent it) should be as flexible, as platform &quot;ad hoc&quot; and custom as possible: if no you will never fit in an ultra low cost phones where the high volumes are and will be for a foreseen futur.
I agree with the previous comment from Thomas Landspurg : many technologies exsit today to do some sort of data interpretation and display, but 2 big things are lacking today:
-Standardization and full description (access, content, etc) of the provided web services and their data: it has to be framework (java/flash/.Net...ajax also) agnostic!
-Some kind of more &quot;ad hoc&quot; frameworks to allow third party ecosytem (like you said) on each type of phone. (a little advertizing here : it is what we are building at www.open-plug.com, working directly with ODM/phone manufacturer and existing third party IP providers).
Thomas
</description>
		<content:encoded><![CDATA[<p>Yes data is the central point, and the way to provide it to the user (to represent it) should be as flexible, as platform &#8220;ad hoc&#8221; and custom as possible: if no you will never fit in an ultra low cost phones where the high volumes are and will be for a foreseen futur.<br />
I agree with the previous comment from Thomas Landspurg : many technologies exsit today to do some sort of data interpretation and display, but 2 big things are lacking today:<br />
-Standardization and full description (access, content, etc) of the provided web services and their data: it has to be framework (java/flash/.Net&#8230;ajax also) agnostic!<br />
-Some kind of more &#8220;ad hoc&#8221; frameworks to allow third party ecosytem (like you said) on each type of phone. (a little advertizing here : it is what we are building at <a href="http://www.open-plug.com" rel="nofollow">http://www.open-plug.com</a>, working directly with ODM/phone manufacturer and existing third party IP providers).<br />
Thomas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Everything and the Mobile Software Universe...</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.html/comment-page-1#comment-838</link>
		<dc:creator>Everything and the Mobile Software Universe...</dc:creator>
		<pubDate>Wed, 27 Sep 2006 21:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2006/09/mobile_mashups.html#comment-838</guid>
		<description>&lt;strong&gt;Widgets all over again&#8230;Content came back with MVC again!&lt;/strong&gt;

Suddenly everything&#8217;s coming up widgets - September 1, 2006 Is an interesting introduction to the widgets and why this concept is successful:
&#8230;In the early days of the Internet, most companies would create a destination website, wait for u...
</description>
		<content:encoded><![CDATA[<p><strong>Widgets all over again&#8230;Content came back with MVC again!</strong></p>
<p>Suddenly everything&#8217;s coming up widgets &#8211; September 1, 2006 Is an interesting introduction to the widgets and why this concept is successful:<br />
&#8230;In the early days of the Internet, most companies would create a destination website, wait for u&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Delport</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.html/comment-page-1#comment-836</link>
		<dc:creator>Jason Delport</dc:creator>
		<pubDate>Mon, 25 Sep 2006 17:58:47 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2006/09/mobile_mashups.html#comment-836</guid>
		<description>I don&#039;t think the fact that Java ME and other frameworks lack certain connectivity technologies (eg REST &amp; SOAP) is a problem. Most developers of complex connected applications have been using server side proxies for years. In this way a single application to server request can be translated into several different web service API calls. The reponse data from these API calls can then get formatted into a single custom response which gets sent back to the phone application in simple XML. Conclusion... its painful but possible!
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think the fact that Java ME and other frameworks lack certain connectivity technologies (eg REST &#038; SOAP) is a problem. Most developers of complex connected applications have been using server side proxies for years. In this way a single application to server request can be translated into several different web service API calls. The reponse data from these API calls can then get formatted into a single custom response which gets sent back to the phone application in simple XML. Conclusion&#8230; its painful but possible!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Landspurg</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.html/comment-page-1#comment-835</link>
		<dc:creator>Thomas Landspurg</dc:creator>
		<pubDate>Tue, 19 Sep 2006 09:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2006/09/mobile_mashups.html#comment-835</guid>
		<description>Hello Paddy,
I agree totally with the first part of this post, but not with the conclusion...
The good think with Web services, is that they are not linked to a single technology...And it&#039;s very easy to create a composite application in most of the existing techno:
- Flash/FlashLite
- native (Symbian, Windows Mobile, Brew)
- Wap/Html/Xml
- JavaMe (and yes, no need to bring the complexity of JSR172 to call for instance Flickr...). Even in MIDP1.0 you can create good composite applications
- and in the future, Ajax (but currently it&#039;s the one who haves the lower installed base)
</description>
		<content:encoded><![CDATA[<p>Hello Paddy,<br />
I agree totally with the first part of this post, but not with the conclusion&#8230;<br />
The good think with Web services, is that they are not linked to a single technology&#8230;And it&#8217;s very easy to create a composite application in most of the existing techno:<br />
- Flash/FlashLite<br />
- native (Symbian, Windows Mobile, Brew)<br />
- Wap/Html/Xml<br />
- JavaMe (and yes, no need to bring the complexity of JSR172 to call for instance Flickr&#8230;). Even in MIDP1.0 you can create good composite applications<br />
- and in the future, Ajax (but currently it&#8217;s the one who haves the lower installed base)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Spence</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2006/09/mobile_mashups.html/comment-page-1#comment-834</link>
		<dc:creator>Richard Spence</dc:creator>
		<pubDate>Tue, 19 Sep 2006 08:12:38 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2006/09/mobile_mashups.html#comment-834</guid>
		<description>Very interested in all the points surrounding mobile ajax as we have been experimenting with the Opera platform ourselves.
My main concern is that for mobile ajax to have any significant impact we are going to need the majority of users equipped with a decent ajax ready browser.
Frustratingly, as usual, this seems a way off - years away infact.
</description>
		<content:encoded><![CDATA[<p>Very interested in all the points surrounding mobile ajax as we have been experimenting with the Opera platform ourselves.<br />
My main concern is that for mobile ajax to have any significant impact we are going to need the majority of users equipped with a decent ajax ready browser.<br />
Frustratingly, as usual, this seems a way off &#8211; years away infact.</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! -->
