<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Standards in microcontent publishing</title>
	<link>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html</link>
	<description>Kimbro Staken exploring creative use of technology and whatever else happens to seem interesting.</description>
	<pubDate>Fri, 29 Aug 2008 19:41:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: InfoTangle :: Sayonara Super-Size – It’s Bite-Sized on the Web :: June :: 2006</title>
		<link>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-20</link>
		<pubDate>Tue, 13 Jun 2006 14:33:13 +0000</pubDate>
		<guid>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-20</guid>
					<description>[...] &amp;#8220;Microcontent&amp;#8220;. Wikipedia. (Viewed on 6/8/06) &amp;#8220;Microformats&amp;#8220;. Wikipedia. (Viewed on 6/8/06) Arrington, Michael. &amp;#8220;TagWorld Widgets Platform&amp;#8220;. TechCrunch. Beisel, David. &amp;#8220;Microchunking Doesn&amp;#8217;t Mean Microconsumption&amp;#8220;. Genuine VC. Brogan, Chris. &amp;#8220;Microcontent on the Rise&amp;#8220;. [ChrisBrogan.com]. Cashmore, Pete. &amp;#8220;Why Online Media Should Be Free (And Why We Should Embrace the Splogosphere)&amp;#8220;. Mashable. Celik, Tantek. &amp;#8220;Introducting Microformats Search and Pingerati&amp;#8220;. Technorati. E&amp;#38;P Staff. &amp;#8220;Mochila Adds AP, Hearst, and Several Others to Network.&amp;#8221; Editor &amp;#38; Publisher. Glaser, Mark. &amp;#8220;YouTube CEO Hails &amp;#8216;Birth of a New Clip Culture&amp;#8217;&amp;#8220;. MediaShift. Haque, Umair. &amp;#8220;The New Economics of Media: Micromedia, Connected Consumption and The Snowball Effect&amp;#8220;. (Presentation). Bubblegeneration Strategy Lab. Leene, Dr. Arnaud. &amp;#8220;Microcontent is Everywhere!!!&amp;#8220;. MacManus, Richard. &amp;#8220;Microcontent Design, Part 1&amp;#8221; Read/Write Web. MacManus, Richard. &amp;#8220;Microcontent Aggregators: 43 Things&amp;#8221; Read/Write Web. MacManus, Richard. &amp;#8220;Microcontent Aggregators: Peoplefeeds&amp;#8221; Read/Write Web. MacManus, Richard. &amp;#8220;Microcontent Aggregators: Superglu&amp;#8221; Read/Write Web. Menell, Bryan. &amp;#8220;Microchunking and Learning&amp;#8220;. Learning 2.0. Rodgers, Zachary. &amp;#8220;Online Video: Now in Syndication&amp;#8220;. ClickZ Network. Rubel, Steve. &amp;#8220;YouOS Web Desktop.&amp;#8221; Micro Persuasion. Schonfeld, Erick. &amp;#8220;Now Serving: The Media Microchunk&amp;#8220;. Business 2.0. Staken, Kimbro. &amp;#8220;Standards in Microcontent Publishing&amp;#8220;. Inspirational Technology. Wilson, Fred. &amp;#8220;The Future of Media (aka Please Take My RSS Feed)&amp;#8220;. A VC. Winkler, Hugh. &amp;#8220;Microcontent Three-Way Processes&amp;#8220;. Messages Not Models. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] &#8220;Microcontent&#8220;. Wikipedia. (Viewed on 6/8/06) &#8220;Microformats&#8220;. Wikipedia. (Viewed on 6/8/06) Arrington, Michael. &#8220;TagWorld Widgets Platform&#8220;. TechCrunch. Beisel, David. &#8220;Microchunking Doesn&#8217;t Mean Microconsumption&#8220;. Genuine VC. Brogan, Chris. &#8220;Microcontent on the Rise&#8220;. [ChrisBrogan.com]. Cashmore, Pete. &#8220;Why Online Media Should Be Free (And Why We Should Embrace the Splogosphere)&#8220;. Mashable. Celik, Tantek. &#8220;Introducting Microformats Search and Pingerati&#8220;. Technorati. E&#38;P Staff. &#8220;Mochila Adds AP, Hearst, and Several Others to Network.&#8221; Editor &#38; Publisher. Glaser, Mark. &#8220;YouTube CEO Hails &#8216;Birth of a New Clip Culture&#8217;&#8220;. MediaShift. Haque, Umair. &#8220;The New Economics of Media: Micromedia, Connected Consumption and The Snowball Effect&#8220;. (Presentation). Bubblegeneration Strategy Lab. Leene, Dr. Arnaud. &#8220;Microcontent is Everywhere!!!&#8220;. MacManus, Richard. &#8220;Microcontent Design, Part 1&#8221; Read/Write Web. MacManus, Richard. &#8220;Microcontent Aggregators: 43 Things&#8221; Read/Write Web. MacManus, Richard. &#8220;Microcontent Aggregators: Peoplefeeds&#8221; Read/Write Web. MacManus, Richard. &#8220;Microcontent Aggregators: Superglu&#8221; Read/Write Web. Menell, Bryan. &#8220;Microchunking and Learning&#8220;. Learning 2.0. Rodgers, Zachary. &#8220;Online Video: Now in Syndication&#8220;. ClickZ Network. Rubel, Steve. &#8220;YouOS Web Desktop.&#8221; Micro Persuasion. Schonfeld, Erick. &#8220;Now Serving: The Media Microchunk&#8220;. Business 2.0. Staken, Kimbro. &#8220;Standards in Microcontent Publishing&#8220;. Inspirational Technology. Wilson, Fred. &#8220;The Future of Media (aka Please Take My RSS Feed)&#8220;. A VC. Winkler, Hugh. &#8220;Microcontent Three-Way Processes&#8220;. Messages Not Models. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Danny</title>
		<link>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-13</link>
		<pubDate>Tue, 06 Jun 2006 16:41:22 +0000</pubDate>
		<guid>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-13</guid>
					<description>One small nit. The problem with RSS hasn't been so much to do with standardization - at this point in time RSS 2.0 pretty well is the de facto standard. The problem is with the nature of its specification. 

Arguably there was a better one (RSS 1.0), designed by a commitee no less. But irrespective of that, because of the numerous shortfalls of RSS, a significant number of syndication developers had little option but to develop a new specification, Atom. Technically, RSS itself could have been fixed, but the specification process didn't allow for it. 

I'll add that the situation with RSS is very different to that of HTML. When HTML came along no-one really had a clue about best practices for interoperability (there wasn't a Web). This wasn't the case when RSS came along, best practices had emerged. But then sloppiness was rebadged as &quot;simple&quot; and hailed as a virtue.</description>
		<content:encoded><![CDATA[<p>One small nit. The problem with RSS hasn&#8217;t been so much to do with standardization - at this point in time RSS 2.0 pretty well is the de facto standard. The problem is with the nature of its specification. </p>
<p>Arguably there was a better one (RSS 1.0), designed by a commitee no less. But irrespective of that, because of the numerous shortfalls of RSS, a significant number of syndication developers had little option but to develop a new specification, Atom. Technically, RSS itself could have been fixed, but the specification process didn&#8217;t allow for it. </p>
<p>I&#8217;ll add that the situation with RSS is very different to that of HTML. When HTML came along no-one really had a clue about best practices for interoperability (there wasn&#8217;t a Web). This wasn&#8217;t the case when RSS came along, best practices had emerged. But then sloppiness was rebadged as &#8220;simple&#8221; and hailed as a virtue.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Inspirational Technology &#187; Blog Archive &#187; More on RDFa</title>
		<link>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-11</link>
		<pubDate>Fri, 02 Jun 2006 18:23:33 +0000</pubDate>
		<guid>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-11</guid>
					<description>[...] This is from an email I wrote to clarify my concerns with the existence of RDFa. It was in response to an email prompted by my post on the premature creation of standards in the microcontent space.  I had looked at RDFa and I agree it&amp;#8217;s not all that complicated, in fact RDF as a basic technology isn&amp;#8217;t really that complicated. Where RDF fails is the semantic web vision and the complexity pulled in by trying to build a globally scalable data framework. To me that&amp;#8217;s too aggressive of an approach for real world adoption. Anyone who actually gets out in the field and works with average skill level developers will know that a disturbingly large percentage are still struggling with simple XML, let alone the ideas behind RDF. The RDF vision is great and I don&amp;#8217;t dispute the theoretical value of it, my problem with it is born 100% from the fact that I just don&amp;#8217;t believe it can succeed outside the realm of the above average skill level developers who are already interested in it. That&amp;#8217;s basically been my opinion since I read the early working drafts for the RDF specs and I&amp;#8217;ve seen nothing since then that&amp;#8217;s allowed me to think otherwise. I&amp;#8217;m always looking. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] This is from an email I wrote to clarify my concerns with the existence of RDFa. It was in response to an email prompted by my post on the premature creation of standards in the microcontent space.  I had looked at RDFa and I agree it&#8217;s not all that complicated, in fact RDF as a basic technology isn&#8217;t really that complicated. Where RDF fails is the semantic web vision and the complexity pulled in by trying to build a globally scalable data framework. To me that&#8217;s too aggressive of an approach for real world adoption. Anyone who actually gets out in the field and works with average skill level developers will know that a disturbingly large percentage are still struggling with simple XML, let alone the ideas behind RDF. The RDF vision is great and I don&#8217;t dispute the theoretical value of it, my problem with it is born 100% from the fact that I just don&#8217;t believe it can succeed outside the realm of the above average skill level developers who are already interested in it. That&#8217;s basically been my opinion since I read the early working drafts for the RDF specs and I&#8217;ve seen nothing since then that&#8217;s allowed me to think otherwise. I&#8217;m always looking. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kimbro Staken</title>
		<link>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-10</link>
		<pubDate>Fri, 02 Jun 2006 17:22:50 +0000</pubDate>
		<guid>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-10</guid>
					<description>Yep, that's all that matters. Once there's enough data out there we can worry about standards. Until then that's just premature optimization.</description>
		<content:encoded><![CDATA[<p>Yep, that&#8217;s all that matters. Once there&#8217;s enough data out there we can worry about standards. Until then that&#8217;s just premature optimization.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Brendan Taylor</title>
		<link>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-6</link>
		<pubDate>Thu, 01 Jun 2006 15:40:21 +0000</pubDate>
		<guid>http://www.kstaken.com/archives/25_standards-in-microcontent-publishing.html#comment-6</guid>
					<description>Although I disagree with you about the utility of RDF (really, it's a lot easier than it looks. why it hasn't been picked up, I don't know), in the end it's not really important. 

What matters is getting the machine readable data out there - once it's marked up properly it's comparatively trivial to convert it to whatever format you like the best.</description>
		<content:encoded><![CDATA[<p>Although I disagree with you about the utility of RDF (really, it&#8217;s a lot easier than it looks. why it hasn&#8217;t been picked up, I don&#8217;t know), in the end it&#8217;s not really important. </p>
<p>What matters is getting the machine readable data out there - once it&#8217;s marked up properly it&#8217;s comparatively trivial to convert it to whatever format you like the best.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
