<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Mobiles manifesting AI</title>
	<atom:link href="http://dw2blog.com/2010/01/07/mobiles-manifesting-ai/feed/" rel="self" type="application/rss+xml" />
	<link>http://dw2blog.com/2010/01/07/mobiles-manifesting-ai/</link>
	<description>Eclectic thoughts on technologies, markets, innovation, openness, collaboration, disruption, risks, and solutions</description>
	<lastBuildDate>Mon, 06 Feb 2012 09:17:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: John Pagonis</title>
		<link>http://dw2blog.com/2010/01/07/mobiles-manifesting-ai/#comment-851</link>
		<dc:creator><![CDATA[John Pagonis]]></dc:creator>
		<pubDate>Thu, 07 Jan 2010 11:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://dw2blog.com/?p=559#comment-851</guid>
		<description><![CDATA[Henry Lieberman&#039;s earlier work at MIT on &#039;autonomous Interface agents&#039; and &#039;Reconnaissance Agents&#039; offers some simple and powerful ideas that have unfortunately been neglected since. 

When I looked at implementing some of that on Symbian OS in trying to develop an intelligent mobile context sensitive recommender system, I discovered that the problem was _not_ the &#039;AI&#039; (or whatever you want to call the magic) but the fact that you couldn&#039;t  source the context and user actions easily from the frameworks and apps in order to feed them into the &#039;machine learning black box&#039; ; at least not without full access and major enhancements inside the system&#039;s code. This seems to be true for most if not all mainstream environments desktop or otherwise (with notable exceptions Apple&#039;s Open Scripting Architecture). 

For mobile&#039;s to fulfil the &quot;personal digital assistants&quot; vision and infact  Alan Kay&#039;s Dynabook vision, in my opinion mobile platforms must be tuned/redesigned to allow proactive agents to take action.  To achieve that they must be engineered to reflect what is going on in the system (apps, UI etc). This is the only way for agents to have valid info on what is going on and therefore to drive machine learning, until then application will be  &quot;narrow&quot;. Nevertheless such &quot;narrow&quot; applicability can be very useful perhaps (like Lieberman&#039;s Letizia, Bradley Rhodes&#039; Remembrance Agent, Balabanovic&#039; Fab/Slider or the Daily Learner by billsus and Pazzani).

FYI:
http://web.media.mit.edu/~lieber/Publications/Publications.html
http://www.bradleyrhodes.com/Papers/physical-context-ieee-toc.pdf 
http://www.ics.uci.edu/~pazzani/Publications/billsuspazzanichen.pdf
http://www.balabanovic.pwp.blueyonder.co.uk/marko/Marko-Balabanovic-Research.html]]></description>
		<content:encoded><![CDATA[<p>Henry Lieberman&#8217;s earlier work at MIT on &#8216;autonomous Interface agents&#8217; and &#8216;Reconnaissance Agents&#8217; offers some simple and powerful ideas that have unfortunately been neglected since. </p>
<p>When I looked at implementing some of that on Symbian OS in trying to develop an intelligent mobile context sensitive recommender system, I discovered that the problem was _not_ the &#8216;AI&#8217; (or whatever you want to call the magic) but the fact that you couldn&#8217;t  source the context and user actions easily from the frameworks and apps in order to feed them into the &#8216;machine learning black box&#8217; ; at least not without full access and major enhancements inside the system&#8217;s code. This seems to be true for most if not all mainstream environments desktop or otherwise (with notable exceptions Apple&#8217;s Open Scripting Architecture). </p>
<p>For mobile&#8217;s to fulfil the &#8220;personal digital assistants&#8221; vision and infact  Alan Kay&#8217;s Dynabook vision, in my opinion mobile platforms must be tuned/redesigned to allow proactive agents to take action.  To achieve that they must be engineered to reflect what is going on in the system (apps, UI etc). This is the only way for agents to have valid info on what is going on and therefore to drive machine learning, until then application will be  &#8220;narrow&#8221;. Nevertheless such &#8220;narrow&#8221; applicability can be very useful perhaps (like Lieberman&#8217;s Letizia, Bradley Rhodes&#8217; Remembrance Agent, Balabanovic&#8217; Fab/Slider or the Daily Learner by billsus and Pazzani).</p>
<p>FYI:<br />
<a href="http://web.media.mit.edu/~lieber/Publications/Publications.html" rel="nofollow">http://web.media.mit.edu/~lieber/Publications/Publications.html</a><br />
<a href="http://www.bradleyrhodes.com/Papers/physical-context-ieee-toc.pdf" rel="nofollow">http://www.bradleyrhodes.com/Papers/physical-context-ieee-toc.pdf</a><br />
<a href="http://www.ics.uci.edu/~pazzani/Publications/billsuspazzanichen.pdf" rel="nofollow">http://www.ics.uci.edu/~pazzani/Publications/billsuspazzanichen.pdf</a><br />
<a href="http://www.balabanovic.pwp.blueyonder.co.uk/marko/Marko-Balabanovic-Research.html" rel="nofollow">http://www.balabanovic.pwp.blueyonder.co.uk/marko/Marko-Balabanovic-Research.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Budden</title>
		<link>http://dw2blog.com/2010/01/07/mobiles-manifesting-ai/#comment-849</link>
		<dc:creator><![CDATA[Martin Budden]]></dc:creator>
		<pubDate>Thu, 07 Jan 2010 10:23:05 +0000</pubDate>
		<guid isPermaLink="false">http://dw2blog.com/?p=559#comment-849</guid>
		<description><![CDATA[David,

I&#039;ve often said (or complained): &quot;There are two types of application: those that do what they are told and those that do what they think I wanted them to do; I know which I prefer&quot;. Part of this is that applications aren&#039;t yet very good at anticipation, but part of it is genuine personal preference.

Consider human personal assistants. Some people prefer assistants who effectively and efficiently do what they are told, others prefer assistants who try and anticipate and act upon their needs. It really is a matter of personal preference.

There are two complementary problems for digital assistants. One is that of intrusiveness (the Microsoft paperclip announcing: &quot;You seem to be writing a letter, do you want to...&quot;). The other is silently doing the wrong thing (my word process or silently correcting a spelling error when in fact the word it was correcting was part of some Swedish text included in my document - rather than correcting an error it introduced one).

The examples you give avoid these problems by providing a selection from which the user can easily reject the wrong items. It is neither intrusive, nor does it introduce errors.

There are two challenges for digital assistants - anticipating what the user wants and providing that information in a non-intrusive and non-error-prone way. I don&#039;t think we&#039;ve seen much advance in either of these problems, other than in the narrow area of assisted search. So no, I don&#039;t think we&#039;ll see mobiles &#039;fulfilling, at last, the vision of “personal digital assistants”&#039; within the next decade.]]></description>
		<content:encoded><![CDATA[<p>David,</p>
<p>I&#8217;ve often said (or complained): &#8220;There are two types of application: those that do what they are told and those that do what they think I wanted them to do; I know which I prefer&#8221;. Part of this is that applications aren&#8217;t yet very good at anticipation, but part of it is genuine personal preference.</p>
<p>Consider human personal assistants. Some people prefer assistants who effectively and efficiently do what they are told, others prefer assistants who try and anticipate and act upon their needs. It really is a matter of personal preference.</p>
<p>There are two complementary problems for digital assistants. One is that of intrusiveness (the Microsoft paperclip announcing: &#8220;You seem to be writing a letter, do you want to&#8230;&#8221;). The other is silently doing the wrong thing (my word process or silently correcting a spelling error when in fact the word it was correcting was part of some Swedish text included in my document &#8211; rather than correcting an error it introduced one).</p>
<p>The examples you give avoid these problems by providing a selection from which the user can easily reject the wrong items. It is neither intrusive, nor does it introduce errors.</p>
<p>There are two challenges for digital assistants &#8211; anticipating what the user wants and providing that information in a non-intrusive and non-error-prone way. I don&#8217;t think we&#8217;ve seen much advance in either of these problems, other than in the narrow area of assisted search. So no, I don&#8217;t think we&#8217;ll see mobiles &#8216;fulfilling, at last, the vision of “personal digital assistants”&#8217; within the next decade.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

