<?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: Machine-to-Machine Hypermedia</title>
	<atom:link href="http://linkednotbound.net/2010/08/25/m2m-hypermedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/</link>
	<description>web-inspired software architecture</description>
	<lastBuildDate>Thu, 10 Feb 2011 16:41:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: This Week in #REST – Volume 24 (Aug 23 2010 – Sep 5 2010) &#171; This week in REST</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-86</link>
		<dc:creator><![CDATA[This Week in #REST – Volume 24 (Aug 23 2010 – Sep 5 2010) &#171; This week in REST]]></dc:creator>
		<pubDate>Mon, 06 Sep 2010 07:27:24 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-86</guid>
		<description><![CDATA[[...] Machine-to-Machine Hypermedia &#8211; More analysis of what hypermedia is and why we need machine-to-machine hypermedia controls. (by AndrewWahbe) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Machine-to-Machine Hypermedia &#8211; More analysis of what hypermedia is and why we need machine-to-machine hypermedia controls. (by AndrewWahbe) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Using Typed Links to Forms :: iansrobinson.com</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-75</link>
		<dc:creator><![CDATA[Using Typed Links to Forms :: iansrobinson.com]]></dc:creator>
		<pubDate>Thu, 02 Sep 2010 14:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-75</guid>
		<description><![CDATA[[...] many different kinds of hypermedia control. Recently, Andrew Wahbe started examining the need for machine-to-machine hypermedia, and the differences between controls for machines and controls for humans. Watch his blog for [...]]]></description>
		<content:encoded><![CDATA[<p>[...] many different kinds of hypermedia control. Recently, Andrew Wahbe started examining the need for machine-to-machine hypermedia, and the differences between controls for machines and controls for humans. Watch his blog for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan Cragg</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-63</link>
		<dc:creator><![CDATA[Duncan Cragg]]></dc:creator>
		<pubDate>Sat, 28 Aug 2010 17:51:25 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-63</guid>
		<description><![CDATA[My own interpretation of REST for Machine-to-Machine integration or distribution is here:

http://duncan-cragg.org/blog/post/deriving-forest/

I see links only as creating hyperdata graphs, which is quite a different view from the &#039;link-rel-action&#039; approach that is seeing increasing popularity these days.]]></description>
		<content:encoded><![CDATA[<p>My own interpretation of REST for Machine-to-Machine integration or distribution is here:</p>
<p><a href="http://duncan-cragg.org/blog/post/deriving-forest/" rel="nofollow">http://duncan-cragg.org/blog/post/deriving-forest/</a></p>
<p>I see links only as creating hyperdata graphs, which is quite a different view from the &#8216;link-rel-action&#8217; approach that is seeing increasing popularity these days.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Banwart&#039;s Blog &#187; Blog Archive &#187; Distributed Weekly 65</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-57</link>
		<dc:creator><![CDATA[Scott Banwart&#039;s Blog &#187; Blog Archive &#187; Distributed Weekly 65]]></dc:creator>
		<pubDate>Fri, 27 Aug 2010 14:31:37 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-57</guid>
		<description><![CDATA[[...] Machine-to-Machine Hypermedia [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Machine-to-Machine Hypermedia [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Wahbe</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-52</link>
		<dc:creator><![CDATA[Andrew Wahbe]]></dc:creator>
		<pubDate>Thu, 26 Aug 2010 03:00:10 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-52</guid>
		<description><![CDATA[Thanks for the comment Mike.

A few things:
- controls for machines are definitely different than controls for human beings, but that doesn&#039;t mean they are impossible to build
- yes a machine can&#039;t &quot;know&quot; anything, but that doesn&#039;t mean that output messages to the machine can&#039;t put it in a state where it will ultimately generate an acceptable input message
- this works best (and perhaps is only possible when) the hypermedia format is designed for a specific type of machine user
- the link relation approach assumes that the only attributes necessary to define a control are a type and a URI. I think it&#039;s hard to build interesting or useful controls that way
- Here&#039;s my practical example: One can build and evolve all sorts of call control applications using CCXML. These applications are &quot;used&quot; by a machine -- a call control platform. While CCXML has its warts, I believe it qualifies as a hypermedia format for machines.

I will definitely elaborate on this in future posts.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the comment Mike.</p>
<p>A few things:<br />
- controls for machines are definitely different than controls for human beings, but that doesn&#8217;t mean they are impossible to build<br />
- yes a machine can&#8217;t &#8220;know&#8221; anything, but that doesn&#8217;t mean that output messages to the machine can&#8217;t put it in a state where it will ultimately generate an acceptable input message<br />
- this works best (and perhaps is only possible when) the hypermedia format is designed for a specific type of machine user<br />
- the link relation approach assumes that the only attributes necessary to define a control are a type and a URI. I think it&#8217;s hard to build interesting or useful controls that way<br />
- Here&#8217;s my practical example: One can build and evolve all sorts of call control applications using CCXML. These applications are &#8220;used&#8221; by a machine &#8212; a call control platform. While CCXML has its warts, I believe it qualifies as a hypermedia format for machines.</p>
<p>I will definitely elaborate on this in future posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-49</link>
		<dc:creator><![CDATA[Anonymous]]></dc:creator>
		<pubDate>Wed, 25 Aug 2010 23:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-49</guid>
		<description><![CDATA[&lt;strong&gt;Twitter Trackbacks...&lt;/strong&gt;

...]]></description>
		<content:encoded><![CDATA[<p><strong>Twitter Trackbacks&#8230;</strong></p>
<p>&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike K</title>
		<link>http://linkednotbound.net/2010/08/25/m2m-hypermedia/#comment-48</link>
		<dc:creator><![CDATA[Mike K]]></dc:creator>
		<pubDate>Wed, 25 Aug 2010 21:12:26 +0000</pubDate>
		<guid isPermaLink="false">http://linkednotbound.net/?p=57#comment-48</guid>
		<description><![CDATA[Machines are not autonomous, and they don&#039;t have intuition. HTML relies on these human properties to drive applications.

Machine clients will always rely on &#039;out-of-band&#039; knowledge because they aren&#039;t actually capable of comprehending any in-bound knowledge - they&#039;re just pre-defined mechanisms, afterall - everything a machine client &#039;knows&#039; is out-of-band, because that is where it is created by its developer(s).

Accepting that, &#039;simple link relations&#039; (and accompanied documentation) provide everything a developer needs to comprehend/discover a particular application and build the machine, and given that; everything the machine itself needs to operate.

As a practical example: If I significantly change my customers&#039; checkout process in my HTML driven web app, I can use natural language and GUI elements to guide them through the new flow; and it is likely most of them will adapt &#039;in-band&#039;.. machine clients just aren&#039;t capable of reacting in the same way right now, and possibly never will - so why bother creating unnecessary hypertext controls and bloating your hypermedia types?]]></description>
		<content:encoded><![CDATA[<p>Machines are not autonomous, and they don&#8217;t have intuition. HTML relies on these human properties to drive applications.</p>
<p>Machine clients will always rely on &#8216;out-of-band&#8217; knowledge because they aren&#8217;t actually capable of comprehending any in-bound knowledge &#8211; they&#8217;re just pre-defined mechanisms, afterall &#8211; everything a machine client &#8216;knows&#8217; is out-of-band, because that is where it is created by its developer(s).</p>
<p>Accepting that, &#8216;simple link relations&#8217; (and accompanied documentation) provide everything a developer needs to comprehend/discover a particular application and build the machine, and given that; everything the machine itself needs to operate.</p>
<p>As a practical example: If I significantly change my customers&#8217; checkout process in my HTML driven web app, I can use natural language and GUI elements to guide them through the new flow; and it is likely most of them will adapt &#8216;in-band&#8217;.. machine clients just aren&#8217;t capable of reacting in the same way right now, and possibly never will &#8211; so why bother creating unnecessary hypertext controls and bloating your hypermedia types?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

