<?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: Interfacing the &#8216;internet of things&#8217;</title>
	<atom:link href="http://www.nearfield.org/2007/07/interfacing-the-internet-of-things/feed" rel="self" type="application/rss+xml" />
	<link>http://www.nearfield.org/2007/07/interfacing-the-internet-of-things</link>
	<description>Interaction with RFID and NFC</description>
	<lastBuildDate>Thu, 26 Jan 2012 13:49:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Dave</title>
		<link>http://www.nearfield.org/2007/07/interfacing-the-internet-of-things/comment-page-1#comment-31769</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Mon, 16 Nov 2009 08:34:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.nearfield.org/2007/07/interfacing-the-internet-of-things#comment-31769</guid>
		<description>Thank you Timo for the article and excellent links. 
The big problem for me is that the typical RFID technology is one-way only. While it might be sufficient for asset identification (what this technology was originally designed to do), it is not good enough as a standard. We need a wireless communication standard that is bi-directional and machine-com. compatible, to enable companies around the world to develop real-world problem solving NFC devices. 
Interesting to take a look at a company from Stamford, US called Precyse Technologies ( www.precysetech.com ) - this guys talk about a &#039;cell phone&quot; designed for assets and are actually offering an &quot; Asset Network &quot; technology that is bi-directional and secure. Not only RFID or RTLS...
A step in the right direction!
Dave</description>
		<content:encoded><![CDATA[<p>Thank you Timo for the article and excellent links. <br />
The big problem for me is that the typical <acronym title="Radio Frequency IDentification (A method of identifying unique items using radio waves. This is typically achieved with communication between a scanner or reader and a tag that contains data on a microchip)">RFID</acronym> technology is one-way only. While it might be sufficient for asset identification (what this technology was originally designed to do), it is not good enough as a standard. We need a wireless communication standard that is bi-directional and machine-com. compatible, to enable companies around the world to develop real-world problem solving <acronym title="Near Field Communication (a short-range wireless technology mainly aimed at usage in mobile phones.)">NFC</acronym> devices. <br />
Interesting to take a look at a company from Stamford, US called Precyse Technologies ( <a href="http://www.precysetech.com" rel="nofollow">http://www.precysetech.com</a> ) &#8211; this guys talk about a &#8216;cell phone&#8221; designed for assets and are actually offering an &#8221; Asset Network &#8221; technology that is bi-directional and secure. Not only <acronym title="Radio Frequency IDentification (A method of identifying unique items using radio waves. This is typically achieved with communication between a scanner or reader and a tag that contains data on a microchip)">RFID</acronym> or RTLS&#8230;<br />
A step in the right direction!<br />
Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Touch design briefs &#183; Touch</title>
		<link>http://www.nearfield.org/2007/07/interfacing-the-internet-of-things/comment-page-1#comment-3877</link>
		<dc:creator>Touch design briefs &#183; Touch</dc:creator>
		<pubDate>Tue, 03 Jul 2007 10:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.nearfield.org/2007/07/interfacing-the-internet-of-things#comment-3877</guid>
		<description>[...] Interfacing the &#8216;internet of things [...]</description>
		<content:encoded><![CDATA[<p>[...] Interfacing the &#8216;internet of things [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

