<?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: On Twitter Data</title>
	<atom:link href="http://www.sauria.com/blog/2009/05/26/on-twitter-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sauria.com/blog/2009/05/26/on-twitter-data/</link>
	<description>Open Source, Modern Programming Languages, OS X, Photography, and ...</description>
	<lastBuildDate>Thu, 19 Jan 2012 07:08:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Donnie Berkholz</title>
		<link>http://www.sauria.com/blog/2009/05/26/on-twitter-data/comment-page-1/#comment-16246</link>
		<dc:creator>Donnie Berkholz</dc:creator>
		<pubDate>Sat, 30 May 2009 07:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2009/05/26/on-twitter-data/#comment-16246</guid>
		<description>Do they call it nanoformats, if it&#039;s just part of a microblog?</description>
		<content:encoded><![CDATA[<p>Do they call it nanoformats, if it&#8217;s just part of a microblog?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Four short links: 27 May 2009 &#124; Tech-monkey.info Blogs</title>
		<link>http://www.sauria.com/blog/2009/05/26/on-twitter-data/comment-page-1/#comment-16230</link>
		<dc:creator>Four short links: 27 May 2009 &#124; Tech-monkey.info Blogs</dc:creator>
		<pubDate>Wed, 27 May 2009 15:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2009/05/26/on-twitter-data/#comment-16230</guid>
		<description>[...] Twitter Data &#8212; using Twitter as a conduit for messages that have semantic markup. My gut reaction is that I&#8217;d prefer pure JSON in the data tweets, because a hybrid gives you poor use of the limited bandwidth and there seems no strong reason to care about human readability. (via Ted Leung) [...]</description>
		<content:encoded><![CDATA[<p>[...] Twitter Data &#8212; using Twitter as a conduit for messages that have semantic markup. My gut reaction is that I&#8217;d prefer pure JSON in the data tweets, because a hybrid gives you poor use of the limited bandwidth and there seems no strong reason to care about human readability. (via Ted Leung) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd Fast</title>
		<link>http://www.sauria.com/blog/2009/05/26/on-twitter-data/comment-page-1/#comment-16223</link>
		<dc:creator>Todd Fast</dc:creator>
		<pubDate>Tue, 26 May 2009 22:23:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2009/05/26/on-twitter-data/#comment-16223</guid>
		<description>Actually, you&#039;re confusing the role of Twitter Data with the particular uses of Twitter Data. Microformats are a convention for presenting certain, specific types of data. This convention is built on top of a lower-level, well-defined syntax (HTML) which makes it possible to embed that data.

Like HTML in the Microformats case, Twitter Data is one abstraction level lower, and concerned with making abstract data embeddable in Twitter in a natural and searchable way. What that data actually is, for example, a microsformat, JSON string, or Base64-encoded bits, is what Twitter Data enables, but not strictly what Twitter Data is about.</description>
		<content:encoded><![CDATA[<p>Actually, you&#8217;re confusing the role of Twitter Data with the particular uses of Twitter Data. Microformats are a convention for presenting certain, specific types of data. This convention is built on top of a lower-level, well-defined syntax (HTML) which makes it possible to embed that data.</p>
<p>Like HTML in the Microformats case, Twitter Data is one abstraction level lower, and concerned with making abstract data embeddable in Twitter in a natural and searchable way. What that data actually is, for example, a microsformat, JSON string, or Base64-encoded bits, is what Twitter Data enables, but not strictly what Twitter Data is about.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rgz</title>
		<link>http://www.sauria.com/blog/2009/05/26/on-twitter-data/comment-page-1/#comment-16221</link>
		<dc:creator>rgz</dc:creator>
		<pubDate>Tue, 26 May 2009 20:32:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.sauria.com/blog/2009/05/26/on-twitter-data/#comment-16221</guid>
		<description>In other words microformats.</description>
		<content:encoded><![CDATA[<p>In other words microformats.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

