<?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: Integrated Life Management</title>
	<atom:link href="http://www.snell-pym.org.uk/archives/2006/08/24/integrated-life-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.snell-pym.org.uk/archives/2006/08/24/integrated-life-management/</link>
	<description>Sarah and Alaric Snell-Pym living in interesting times</description>
	<pubDate>Tue, 02 Dec 2008 12:34:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Alex B</title>
		<link>http://www.snell-pym.org.uk/archives/2006/08/24/integrated-life-management/#comment-4854</link>
		<dc:creator>Alex B</dc:creator>
		<pubDate>Sat, 26 Aug 2006 10:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://snell-pym.org.uk/archives/2006/08/24/integrated-life-management/#comment-4854</guid>
		<description>&lt;p&gt;The push model permits semantically more operations than the pull model, such as assigning tasks to users, because intelligent components can intercept the data before it's user-visible. An RSS aggregator that just pulls task lists is pretty simple-minded in comparison.&lt;/p&gt;

&lt;p&gt;But, bandwidth INefficiency is not something to criticise the pull model for. RSS is just the format; the pull interface is REST. (Indeed, you'd want to use Atom, not RSS, in order for tasks to carry modification times.) So http://tasks.org.uk/alaric/created/thisweek, /alaric/due/thisweek, /alaric/highpri - no requirement to receive a monolithic listing of all tasks, unless you ask for it.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The push model permits semantically more operations than the pull model, such as assigning tasks to users, because intelligent components can intercept the data before it's user-visible. An RSS aggregator that just pulls task lists is pretty simple-minded in comparison.</p>

<p>But, bandwidth INefficiency is not something to criticise the pull model for. RSS is just the format; the pull interface is REST. (Indeed, you'd want to use Atom, not RSS, in order for tasks to carry modification times.) So <a href="http://tasks.org.uk/alaric/created/thisweek" rel="nofollow">http://tasks.org.uk/alaric/created/thisweek</a>, /alaric/due/thisweek, /alaric/highpri - no requirement to receive a monolithic listing of all tasks, unless you ask for it.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: andyjpb</title>
		<link>http://www.snell-pym.org.uk/archives/2006/08/24/integrated-life-management/#comment-4589</link>
		<dc:creator>andyjpb</dc:creator>
		<pubDate>Thu, 24 Aug 2006 09:24:41 +0000</pubDate>
		<guid isPermaLink="false">http://snell-pym.org.uk/archives/2006/08/24/integrated-life-management/#comment-4589</guid>
		<description>&lt;p&gt;This is something that has bugged me for a long time. I use bugzilla to track issues both in stoic and at work. I also have my own todo list: my PIM has been Lotus Organiser 97 for a long time. However, I stopped using the Palm because text files became quicker for me to mess around with.
Anyway, I've been looking into Calendaring and Scheduling for a while, with the intent to write my own "one day", and I think the technology you are after already exists.
ical (the standard, not the app) can represent the data you want and iMIP, iTIP and CAP (or the newer XML alternatives: CAP never really "worked") act as the transports.&lt;/p&gt;

&lt;p&gt;http://www.ietf.org/html.charters/OLD/calsch-charter.html
http://www.imc.org/pdi/
http://www.ietf.org/rfc/rfc3283.txt&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is something that has bugged me for a long time. I use bugzilla to track issues both in stoic and at work. I also have my own todo list: my PIM has been Lotus Organiser 97 for a long time. However, I stopped using the Palm because text files became quicker for me to mess around with.
Anyway, I've been looking into Calendaring and Scheduling for a while, with the intent to write my own "one day", and I think the technology you are after already exists.
ical (the standard, not the app) can represent the data you want and iMIP, iTIP and CAP (or the newer XML alternatives: CAP never really "worked") act as the transports.</p>

<p><a href="http://www.ietf.org/html.charters/OLD/calsch-charter.html" rel="nofollow">http://www.ietf.org/html.charters/OLD/calsch-charter.html</a>
<a href="http://www.imc.org/pdi/" rel="nofollow">http://www.imc.org/pdi/</a>
<a href="http://www.ietf.org/rfc/rfc3283.txt" rel="nofollow">http://www.ietf.org/rfc/rfc3283.txt</a></p>]]></content:encoded>
	</item>
</channel>
</rss>
