<?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: Micro-Messaging &#8211; Data Interchange Standards and Track</title>
	<atom:link href="http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/feed/" rel="self" type="application/rss+xml" />
	<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/</link>
	<description>The ramblings of an often lucid mind...</description>
	<lastBuildDate>Wed, 08 Feb 2012 12:44:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-584</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 07:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-584</guid>
		<description>On the question of getting the players to agree, they need to understand that it&#039;s in their own best interests. Silos are dead. Even Microsoft gets that. Twitter will be irrelevant if they don&#039;t open the silo. They&#039;re certainly free to develop a viable business model, but siloing the data will be their downfall. Particularly when it&#039;s MY data they&#039;re siloing.</description>
		<content:encoded><![CDATA[<p>On the question of getting the players to agree, they need to understand that it&#39;s in their own best interests. Silos are dead. Even Microsoft gets that. Twitter will be irrelevant if they don&#39;t open the silo. They&#39;re certainly free to develop a viable business model, but siloing the data will be their downfall. Particularly when it&#39;s MY data they&#39;re siloing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-583</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 07:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-583</guid>
		<description>Twitter needs to open up because they control the space right now and have the most ability to define the standard in a way that most benefits them. Right now, they&#039;re the ones with the users, but one look at friendster&#039;s history should give them a soberiing moment or two, particularly with Microsoft aggressively entering the social networking space with open products.</description>
		<content:encoded><![CDATA[<p>Twitter needs to open up because they control the space right now and have the most ability to define the standard in a way that most benefits them. Right now, they&#39;re the ones with the users, but one look at friendster&#39;s history should give them a soberiing moment or two, particularly with Microsoft aggressively entering the social networking space with open products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: briantroy</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-582</link>
		<dc:creator>briantroy</dc:creator>
		<pubDate>Sun, 16 Nov 2008 06:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-582</guid>
		<description>I think the developer community is in agreement - the question is how do you get the established players to agree (i.e., twitter/friendfeed/yammer/etc)?&lt;br&gt;IMHO IM never got on a common standard because there was no compelling business imperative for them to do so. Same business drivers that make Cell providers lock devices and subscribers to their network via contracts. &lt;br&gt;Crossing that gap - why is it in Twitter&#039;s best interests to open up? - will drive the creation of a widely implemented standards.</description>
		<content:encoded><![CDATA[<p>I think the developer community is in agreement &#8211; the question is how do you get the established players to agree (i.e., twitter/friendfeed/yammer/etc)?<br />IMHO IM never got on a common standard because there was no compelling business imperative for them to do so. Same business drivers that make Cell providers lock devices and subscribers to their network via contracts. <br />Crossing that gap &#8211; why is it in Twitter&#39;s best interests to open up? &#8211; will drive the creation of a widely implemented standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-581</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 05:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-581</guid>
		<description>I found your example of IM to be a particularly compelling reason for the developer community to really listen to that small vocal group of people. Imagine it -- rather than having to build workarounds, you could be building solutions that cross the clouds and bring amazing value to people, based on a standard that was set *in advance*, based on what we know about the value of the data in the cloud.&lt;br&gt;&lt;br&gt;Believe me, I completely understand the challenge of doing something while managing a family, career and life. In this case, however, I think it becomes absolutely critical that there *is* a standard before development happens around it, particularly for the individual developer. If not, you will have a company like Microsoft or Google setting their own standards, which may benefit them but not the user or developer community as a whole.</description>
		<content:encoded><![CDATA[<p>I found your example of IM to be a particularly compelling reason for the developer community to really listen to that small vocal group of people. Imagine it &#8212; rather than having to build workarounds, you could be building solutions that cross the clouds and bring amazing value to people, based on a standard that was set *in advance*, based on what we know about the value of the data in the cloud.</p>
<p>Believe me, I completely understand the challenge of doing something while managing a family, career and life. In this case, however, I think it becomes absolutely critical that there *is* a standard before development happens around it, particularly for the individual developer. If not, you will have a company like Microsoft or Google setting their own standards, which may benefit them but not the user or developer community as a whole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-378</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 02:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-378</guid>
		<description>On the question of getting the players to agree, they need to understand that it&#039;s in their own best interests. Silos are dead. Even Microsoft gets that. Twitter will be irrelevant if they don&#039;t open the silo. They&#039;re certainly free to develop a viable business model, but siloing the data will be their downfall. Particularly when it&#039;s MY data they&#039;re siloing.</description>
		<content:encoded><![CDATA[<p>On the question of getting the players to agree, they need to understand that it&#39;s in their own best interests. Silos are dead. Even Microsoft gets that. Twitter will be irrelevant if they don&#39;t open the silo. They&#39;re certainly free to develop a viable business model, but siloing the data will be their downfall. Particularly when it&#39;s MY data they&#39;re siloing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-377</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 02:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-377</guid>
		<description>Twitter needs to open up because they control the space right now and have the most ability to define the standard in a way that most benefits them. Right now, they&#039;re the ones with the users, but one look at friendster&#039;s history should give them a soberiing moment or two, particularly with Microsoft aggressively entering the social networking space with open products.</description>
		<content:encoded><![CDATA[<p>Twitter needs to open up because they control the space right now and have the most ability to define the standard in a way that most benefits them. Right now, they&#39;re the ones with the users, but one look at friendster&#39;s history should give them a soberiing moment or two, particularly with Microsoft aggressively entering the social networking space with open products.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: briantroy</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-376</link>
		<dc:creator>briantroy</dc:creator>
		<pubDate>Sun, 16 Nov 2008 01:03:13 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-376</guid>
		<description>I think the developer community is in agreement - the question is how do you get the established players to agree (i.e., twitter/friendfeed/yammer/etc)?&lt;br&gt;IMHO IM never got on a common standard because there was no compelling business imperative for them to do so. Same business drivers that make Cell providers lock devices and subscribers to their network via contracts. &lt;br&gt;Crossing that gap - why is it in Twitter&#039;s best interests to open up? - will drive the creation of a widely implemented standards.</description>
		<content:encoded><![CDATA[<p>I think the developer community is in agreement &#8211; the question is how do you get the established players to agree (i.e., twitter/friendfeed/yammer/etc)?<br />IMHO IM never got on a common standard because there was no compelling business imperative for them to do so. Same business drivers that make Cell providers lock devices and subscribers to their network via contracts. <br />Crossing that gap &#8211; why is it in Twitter&#39;s best interests to open up? &#8211; will drive the creation of a widely implemented standards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-375</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 00:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-375</guid>
		<description>I found your example of IM to be a particularly compelling reason for the developer community to really listen to that small vocal group of people. Imagine it -- rather than having to build workarounds, you could be building solutions that cross the clouds and bring amazing value to people, based on a standard that was set *in advance*, based on what we know about the value of the data in the cloud.&lt;br&gt;&lt;br&gt;Believe me, I completely understand the challenge of doing something while managing a family, career and life. In this case, however, I think it becomes absolutely critical that there *is* a standard before development happens around it, particularly for the individual developer. If not, you will have a company like Microsoft or Google setting their own standards, which may benefit them but not the user or developer community as a whole.</description>
		<content:encoded><![CDATA[<p>I found your example of IM to be a particularly compelling reason for the developer community to really listen to that small vocal group of people. Imagine it &#8212; rather than having to build workarounds, you could be building solutions that cross the clouds and bring amazing value to people, based on a standard that was set *in advance*, based on what we know about the value of the data in the cloud.</p>
<p>Believe me, I completely understand the challenge of doing something while managing a family, career and life. In this case, however, I think it becomes absolutely critical that there *is* a standard before development happens around it, particularly for the individual developer. If not, you will have a company like Microsoft or Google setting their own standards, which may benefit them but not the user or developer community as a whole.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-279</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 00:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-279</guid>
		<description>On the question of getting the players to agree, they need to understand that it&#039;s in their own best interests. Silos are dead. Even Microsoft gets that. Twitter will be irrelevant if they don&#039;t open the silo. They&#039;re certainly free to develop a viable business model, but siloing the data will be their downfall. Particularly when it&#039;s MY data they&#039;re siloing.</description>
		<content:encoded><![CDATA[<p>On the question of getting the players to agree, they need to understand that it&#39;s in their own best interests. Silos are dead. Even Microsoft gets that. Twitter will be irrelevant if they don&#39;t open the silo. They&#39;re certainly free to develop a viable business model, but siloing the data will be their downfall. Particularly when it&#39;s MY data they&#39;re siloing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karoli</title>
		<link>http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/comment-page-1/#comment-278</link>
		<dc:creator>Karoli</dc:creator>
		<pubDate>Sun, 16 Nov 2008 00:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://briantroy.com/blog/2008/11/15/micro-messaging-data-interchange-standards-and-track/#comment-278</guid>
		<description>Twitter need to open up because they control the space right now and have the most ability to define the standard in a way that most benefits them. Right now, they&#039;re the ones with the users, but one look at friendster&#039;s history should give them a soberiing moment or two, particularly with Microsoft aggressively entering the social networking space with open products.</description>
		<content:encoded><![CDATA[<p>Twitter need to open up because they control the space right now and have the most ability to define the standard in a way that most benefits them. Right now, they&#39;re the ones with the users, but one look at friendster&#39;s history should give them a soberiing moment or two, particularly with Microsoft aggressively entering the social networking space with open products.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
