<?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"
	>
<channel>
	<title>Comments on: Martin Geddes: &#34;it&#8217;s like putting a toilet and paddling pool in the kitchen&#34;</title>
	<atom:link href="http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/feed/" rel="self" type="application/rss+xml" />
	<link>http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/</link>
	<description>A daily round table on the tech industry with experts and callers from all over the globe. Join us as we pick apart the news and get to the meat of what\'s happening out there.</description>
	<pubDate>Thu, 20 Nov 2008 16:35:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Paul Jardine</title>
		<link>http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/#comment-48656</link>
		<dc:creator>Paul Jardine</dc:creator>
		<pubDate>Fri, 06 Oct 2006 07:07:11 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/#comment-48656</guid>
		<description>Yes, at a technical level XMPP does, kind of, cover it with JEP-0060 and JEP-0163, but the first one is pretty 'top-heavy' and I haven't looked much at the lightweight one yet.
If you were going to do a 'presence/identity' application like I describe, you would have to build a lot of stuff to simplify the underlying Jabber model for the user.  I still haven't found a Jabber implementation I like (e.g. Gush, Psi, Kopete etc), except perhaps, GoogleTalk, though I rarely use it except on my Nokia 770.
I tried a while back (before the revision of JEP-0060) to design a 'proper' presence model around XMPP, but after a lot of thought I decided it wouldn't work well enough. I might revisit some of the ideas with the JEP-0163 proposal, but I think, in the end, Atom/RSS/GoogleData might be a better solution.</description>
		<content:encoded><![CDATA[<p>Yes, at a technical level XMPP does, kind of, cover it with JEP-0060 and JEP-0163, but the first one is pretty &#8216;top-heavy&#8217; and I haven&#8217;t looked much at the lightweight one yet.<br />
If you were going to do a &#8216;presence/identity&#8217; application like I describe, you would have to build a lot of stuff to simplify the underlying Jabber model for the user.  I still haven&#8217;t found a Jabber implementation I like (e.g. Gush, Psi, Kopete etc), except perhaps, GoogleTalk, though I rarely use it except on my Nokia 770.<br />
I tried a while back (before the revision of JEP-0060) to design a &#8216;proper&#8217; presence model around XMPP, but after a lot of thought I decided it wouldn&#8217;t work well enough. I might revisit some of the ideas with the JEP-0163 proposal, but I think, in the end, Atom/RSS/GoogleData might be a better solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alec</title>
		<link>http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/#comment-48495</link>
		<dc:creator>Alec</dc:creator>
		<pubDate>Thu, 05 Oct 2006 10:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/#comment-48495</guid>
		<description>Paul, I think what you're describing conceptually makes sense. The problem with most presence systems (including SIP/SIMPLE) is their simple watcher / presentity model.  What's needed is to have different presentities for different watchers.  I understand that XMPP does this, but haven't investigated it deeply yet.</description>
		<content:encoded><![CDATA[<p>Paul, I think what you&#8217;re describing conceptually makes sense. The problem with most presence systems (including SIP/SIMPLE) is their simple watcher / presentity model.  What&#8217;s needed is to have different presentities for different watchers.  I understand that XMPP does this, but haven&#8217;t investigated it deeply yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Jardine</title>
		<link>http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/#comment-48467</link>
		<dc:creator>Paul Jardine</dc:creator>
		<pubDate>Thu, 05 Oct 2006 07:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://saunderslog.com/2006/10/03/martin-geddes-its-like-putting-a-toilet-and-paddling-pool-in-the-kitchen/#comment-48467</guid>
		<description>I fail to see how the presence model he describes is any more broken on mobile than it is on 'always-on' ADSL broadband.
Presence breaks when it is not aware of what people are actually doing, and I think it is more about how we present ourselves to others. 
If I think futuristically, what I would really want from a 'presence' application is a whole set of RSS feeds that are linked to my thoughts, movements, physiology and (perhaps later) senses. Each feed is available to a set of people (or entities) that changes according to my mood, context, relationships and needs. It really shouldn't matter whether the point of delivery is mobile or fixed.
But perhaps I'm really talking about Identity...sometimes it's hard to know.</description>
		<content:encoded><![CDATA[<p>I fail to see how the presence model he describes is any more broken on mobile than it is on &#8216;always-on&#8217; ADSL broadband.<br />
Presence breaks when it is not aware of what people are actually doing, and I think it is more about how we present ourselves to others.<br />
If I think futuristically, what I would really want from a &#8216;presence&#8217; application is a whole set of RSS feeds that are linked to my thoughts, movements, physiology and (perhaps later) senses. Each feed is available to a set of people (or entities) that changes according to my mood, context, relationships and needs. It really shouldn&#8217;t matter whether the point of delivery is mobile or fixed.<br />
But perhaps I&#8217;m really talking about Identity&#8230;sometimes it&#8217;s hard to know.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
