<?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: Standards in Content Technologies: Should you care?</title>
	<atom:link href="http://apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/feed/" rel="self" type="application/rss+xml" />
	<link>http://apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/</link>
	<description>Random Thoughts</description>
	<lastBuildDate>Thu, 26 Apr 2012 07:41:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: sayenjole</title>
		<link>http://apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4369</link>
		<dc:creator><![CDATA[sayenjole]]></dc:creator>
		<pubDate>Wed, 21 Jan 2009 11:04:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4369</guid>
		<description><![CDATA[Really interesting stuff. Thanks!]]></description>
		<content:encoded><![CDATA[<p>Really interesting stuff. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: munish</title>
		<link>http://apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4368</link>
		<dc:creator><![CDATA[munish]]></dc:creator>
		<pubDate>Fri, 24 Aug 2007 10:00:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4368</guid>
		<description><![CDATA[In response to the need for standards, Standards are meant for products features that are no longer niche. Once they become commodity, standards are just small note that the products are compliant for so and so standard.]]></description>
		<content:encoded><![CDATA[<p>In response to the need for standards, Standards are meant for products features that are no longer niche. Once they become commodity, standards are just small note that the products are compliant for so and so standard.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apoorv</title>
		<link>http://apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4367</link>
		<dc:creator><![CDATA[Apoorv]]></dc:creator>
		<pubDate>Thu, 23 Aug 2007 04:56:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4367</guid>
		<description><![CDATA[Thanks Finnur for the observation. And look forward to seeing you in Aarhus :)]]></description>
		<content:encoded><![CDATA[<p>Thanks Finnur for the observation. And look forward to seeing you in Aarhus <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Finnur Magnusson</title>
		<link>http://apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4366</link>
		<dc:creator><![CDATA[Finnur Magnusson]]></dc:creator>
		<pubDate>Wed, 22 Aug 2007 22:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.apoorv.info/2007/08/22/standards-in-content-technologies-should-you-care/#comment-4366</guid>
		<description><![CDATA[We at VYRE are working on JSR 170 for content repositories.
Built the application on JSR 168 Portlets and have not looked back. Many clients like the comfort of knowing that bespoke development is an investment that you can transfer between platforms. Standards prevent vendor lock in which is very common in the CMS landscape.

See you in Aarhus :p]]></description>
		<content:encoded><![CDATA[<p>We at VYRE are working on JSR 170 for content repositories.<br />
Built the application on JSR 168 Portlets and have not looked back. Many clients like the comfort of knowing that bespoke development is an investment that you can transfer between platforms. Standards prevent vendor lock in which is very common in the CMS landscape.</p>
<p>See you in Aarhus :p</p>
]]></content:encoded>
	</item>
</channel>
</rss>

