<?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: Demonstrating Snap &#8211; the Syndicated Next Action pattern &#8211; at Web Directions North 2008</title>
	<atom:link href="http://infovore.org/archives/2008/02/06/demonstrating-snap/feed/" rel="self" type="application/rss+xml" />
	<link>http://infovore.org/archives/2008/02/06/demonstrating-snap/</link>
	<description>a weblog by Tom Armitage</description>
	<lastBuildDate>Sun, 08 Apr 2012 09:50:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: tmm45 &#187; Blog Archive &#187; wdn08 - 2 matt webb</title>
		<link>http://infovore.org/archives/2008/02/06/demonstrating-snap/comment-page-1/#comment-70099</link>
		<dc:creator>tmm45 &#187; Blog Archive &#187; wdn08 - 2 matt webb</dc:creator>
		<pubDate>Thu, 21 Feb 2008 02:42:49 +0000</pubDate>
		<guid isPermaLink="false">http://infovore.org/archives/2008/02/06/demonstrating-snap-the-syndicated-next-action-pattern-at-web-directions-north-2008/#comment-70099</guid>
		<description>[...] http://interconnected.org/home/ http://schulzeandwebb.com/2008/movement/slides/ http://infovore.org/archives/2008/02/06/demonstrating-snap/ [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://interconnected.org/home/" rel="nofollow">http://interconnected.org/home/</a> <a href="http://schulzeandwebb.com/2008/movement/slides/" rel="nofollow">http://schulzeandwebb.com/2008/movement/slides/</a> <a href="http://infovore.org/archives/2008/02/06/demonstrating-snap/" rel="nofollow">http://infovore.org/archives/2008/02/06/demonstrating-snap/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Selem</title>
		<link>http://infovore.org/archives/2008/02/06/demonstrating-snap/comment-page-1/#comment-68737</link>
		<dc:creator>Selem</dc:creator>
		<pubDate>Wed, 13 Feb 2008 09:59:42 +0000</pubDate>
		<guid isPermaLink="false">http://infovore.org/archives/2008/02/06/demonstrating-snap-the-syndicated-next-action-pattern-at-web-directions-north-2008/#comment-68737</guid>
		<description>come on,
http://www.xml.com/pub/a/2005/12/14/putting-rss-to-work-immediate-action-feeds.html

notice the date? but maybe timing wasn&#039;t right.</description>
		<content:encoded><![CDATA[<p>come on,<br />
<a href="http://www.xml.com/pub/a/2005/12/14/putting-rss-to-work-immediate-action-feeds.html" rel="nofollow">http://www.xml.com/pub/a/2005/12/14/putting-rss-to-work-immediate-action-feeds.html</a></p>
<p>notice the date? but maybe timing wasn&#8217;t right.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amit</title>
		<link>http://infovore.org/archives/2008/02/06/demonstrating-snap/comment-page-1/#comment-68633</link>
		<dc:creator>Amit</dc:creator>
		<pubDate>Tue, 12 Feb 2008 22:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://infovore.org/archives/2008/02/06/demonstrating-snap-the-syndicated-next-action-pattern-at-web-directions-north-2008/#comment-68633</guid>
		<description>A really nice piece of work here Tom. It strikes me that the possible payloads that can go back and forth in (a) creating a new feed entry in an inbox and (b) spawning an action to/for a subscribing listener or application - essentially entails defining what state a current &quot;event&quot; or process is at. To give you an example, the process of booking a meeting with someone begins with a request action with a payload of date, time, etc. and continues on for x amended requests and responses until a confirmed meeting time is reached.

Of course, the manifested form of Dentrassi is a clear demo of what can be done, but a possible, if more intricate scenario is a multi-transaction process such as that used by multi agent systems, for example the &lt;a href=&quot;http://www.fipa.org/specs/fipa00029/SC00029H.html&quot; rel=&quot;nofollow&quot;&gt;Contract Net Protocol&lt;/a&gt; (see diagram and note interesting &quot;deadline&quot; part on the first pass) to arrive at a negotiated best fit. Finding a way to cater for exchanged transactions, statefully is the key to the interaction possibilities reaching a point when they can really work for human actions and processes via a feedreader.

By moving from a subscribe/notify model for content to actions, snap has introduced an inherent responsibility to cater for events and processes, under the constraints posed by the orthodox aims of newsreaders. If a model for how actions feed to other actions existed, there&#039;s a basis for an awesome way to handle everyday processes despite their twists and turns, although I think this is a solid example of the pattern already. Other uses:

- use the inbox feed to pipe action requests as SMS requests via twitter (similar to facebook&#039;s &quot;you have a friend request from Joe Bloggs&quot;)

- a firefox plugin to initiate an action from a page with a given set of verbs which then asks the target recipient to subscribe to a feed, in which this action and multiple actions exist. Simple example - if I wanted to email this page to a friend, I can right click, and instead of filling out email addresses, send my friend a one-time only &quot;feed subscription request&quot; - which then sends actions to that new friend as an established contact, without emails for each action request. Eliminates future email once subscribed, and allows my friend to receive my action requests implicitly rather than by bombarding their inbox.

- the ability to comment within feedreading applications is already the subject for various startups (can&#039;t remember them at this time of day!) but extending that would open an entirely new business model where commerce transaction requests don&#039;t appear as feed advertising - they appear as actions - for example to fill a survey

- If you could figure out a foreign subscribers&#039; identity beyond their newsreader user agent, for example capture information from a stranger before they subscribe to their inbox feed, it presents the possibility of contextual actions targeted towards them. I don&#039;t mean in an advertising sense, I mean aggregating their action requests from their various services across the web. This would be a proactive and explicit action request mechanism, in contrast to a facebook mini-feed, which lies in the dimension of reporting on your trust network historically and implicitly.</description>
		<content:encoded><![CDATA[<p>A really nice piece of work here Tom. It strikes me that the possible payloads that can go back and forth in (a) creating a new feed entry in an inbox and (b) spawning an action to/for a subscribing listener or application &#8211; essentially entails defining what state a current &#8220;event&#8221; or process is at. To give you an example, the process of booking a meeting with someone begins with a request action with a payload of date, time, etc. and continues on for x amended requests and responses until a confirmed meeting time is reached.</p>
<p>Of course, the manifested form of Dentrassi is a clear demo of what can be done, but a possible, if more intricate scenario is a multi-transaction process such as that used by multi agent systems, for example the <a href="http://www.fipa.org/specs/fipa00029/SC00029H.html" rel="nofollow">Contract Net Protocol</a> (see diagram and note interesting &#8220;deadline&#8221; part on the first pass) to arrive at a negotiated best fit. Finding a way to cater for exchanged transactions, statefully is the key to the interaction possibilities reaching a point when they can really work for human actions and processes via a feedreader.</p>
<p>By moving from a subscribe/notify model for content to actions, snap has introduced an inherent responsibility to cater for events and processes, under the constraints posed by the orthodox aims of newsreaders. If a model for how actions feed to other actions existed, there&#8217;s a basis for an awesome way to handle everyday processes despite their twists and turns, although I think this is a solid example of the pattern already. Other uses:</p>
<p>- use the inbox feed to pipe action requests as SMS requests via twitter (similar to facebook&#8217;s &#8220;you have a friend request from Joe Bloggs&#8221;)</p>
<p>- a firefox plugin to initiate an action from a page with a given set of verbs which then asks the target recipient to subscribe to a feed, in which this action and multiple actions exist. Simple example &#8211; if I wanted to email this page to a friend, I can right click, and instead of filling out email addresses, send my friend a one-time only &#8220;feed subscription request&#8221; &#8211; which then sends actions to that new friend as an established contact, without emails for each action request. Eliminates future email once subscribed, and allows my friend to receive my action requests implicitly rather than by bombarding their inbox.</p>
<p>- the ability to comment within feedreading applications is already the subject for various startups (can&#8217;t remember them at this time of day!) but extending that would open an entirely new business model where commerce transaction requests don&#8217;t appear as feed advertising &#8211; they appear as actions &#8211; for example to fill a survey</p>
<p>- If you could figure out a foreign subscribers&#8217; identity beyond their newsreader user agent, for example capture information from a stranger before they subscribe to their inbox feed, it presents the possibility of contextual actions targeted towards them. I don&#8217;t mean in an advertising sense, I mean aggregating their action requests from their various services across the web. This would be a proactive and explicit action request mechanism, in contrast to a facebook mini-feed, which lies in the dimension of reporting on your trust network historically and implicitly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: plus six &#187; links for 2008-02-10</title>
		<link>http://infovore.org/archives/2008/02/06/demonstrating-snap/comment-page-1/#comment-68239</link>
		<dc:creator>plus six &#187; links for 2008-02-10</dc:creator>
		<pubDate>Sun, 10 Feb 2008 23:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://infovore.org/archives/2008/02/06/demonstrating-snap-the-syndicated-next-action-pattern-at-web-directions-north-2008/#comment-68239</guid>
		<description>[...] Demonstrating Snap - the Syndicated Next Action pattern - at Web Directions North 2008 (Infovore) Tom Armitage on Snap, the Syndicated Next Action Pattern (tags: rss interaction syndication design atom snap ui) [...]</description>
		<content:encoded><![CDATA[<p>[...] Demonstrating Snap &#8211; the Syndicated Next Action pattern &#8211; at Web Directions North 2008 (Infovore) Tom Armitage on Snap, the Syndicated Next Action Pattern (tags: rss interaction syndication design atom snap ui) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-02-07 (Leapfroglog)</title>
		<link>http://infovore.org/archives/2008/02/06/demonstrating-snap/comment-page-1/#comment-67598</link>
		<dc:creator>links for 2008-02-07 (Leapfroglog)</dc:creator>
		<pubDate>Thu, 07 Feb 2008 06:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://infovore.org/archives/2008/02/06/demonstrating-snap-the-syndicated-next-action-pattern-at-web-directions-north-2008/#comment-67598</guid>
		<description>[...] Infovore » Demonstrating Snap - the Syndicated Next Action pattern - at Web Directions North 2008 Tom Armitage shares his side of the story about Snap (“Syndicated Next Action Pattern”) for which he built a prototype application called Dentrassi: &#8220;A simple, hacky approach that exists beats any amount of RFC-drafting and hypothesising.&#8221; (tags: thinking making doing design code development snap actions syndication rss atom tomarmitage prototyping) [...]</description>
		<content:encoded><![CDATA[<p>[...] Infovore » Demonstrating Snap &#8211; the Syndicated Next Action pattern &#8211; at Web Directions North 2008 Tom Armitage shares his side of the story about Snap (“Syndicated Next Action Pattern”) for which he built a prototype application called Dentrassi: &#8220;A simple, hacky approach that exists beats any amount of RFC-drafting and hypothesising.&#8221; (tags: thinking making doing design code development snap actions syndication rss atom tomarmitage prototyping) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

