<?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: ECM: A Rose by Any Other Name Would Smell as Sweet – and I do mean Sweet</title>
	<atom:link href="http://www.informationarchitected.com/blog/ecm-a-rose-by-any-other-name-would-smell-as-sweet-%e2%80%93-and-i-do-mean-sweet/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.informationarchitected.com/blog/ecm-a-rose-by-any-other-name-would-smell-as-sweet-%e2%80%93-and-i-do-mean-sweet/</link>
	<description>Information Architected is a consultancy focused on the intelligent use of content, knowledge and processes to drive innovation and thrive in a digital world.</description>
	<lastBuildDate>Thu, 22 Jul 2010 07:17:10 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dave kellogg</title>
		<link>http://www.informationarchitected.com/blog/ecm-a-rose-by-any-other-name-would-smell-as-sweet-%e2%80%93-and-i-do-mean-sweet/comment-page-1/#comment-575</link>
		<dc:creator>dave kellogg</dc:creator>
		<pubDate>Sat, 19 Dec 2009 04:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=1854#comment-575</guid>
		<description>Hi Carl,&lt;br&gt;&lt;br&gt;Agree that context (and content) are king and that new technologies will let people --better than ever before -- put content in context.  XML play a big role in that, but so do information and publishing companies themselves; using XML to build real content applications that help put the content in the context of a specific task (e.g., changing an airplane tire, unjamming a rifle).  &lt;br&gt;&lt;br&gt;On ECM an acronym, I&#039;ve always felt that someone needs to &quot;put the C in ECM&quot; -- I think it&#039;s historically been quite focused on the M and E, with the C almost being an opaque black box.  Cracking open the C is what we do at Mark Logic.&lt;br&gt;&lt;br&gt;Best/Dave</description>
		<content:encoded><![CDATA[<p>Hi Carl,</p>
<p>Agree that context (and content) are king and that new technologies will let people &#8211;better than ever before &#8212; put content in context.  XML play a big role in that, but so do information and publishing companies themselves; using XML to build real content applications that help put the content in the context of a specific task (e.g., changing an airplane tire, unjamming a rifle).  </p>
<p>On ECM an acronym, I&#39;ve always felt that someone needs to &#8220;put the C in ECM&#8221; &#8212; I think it&#39;s historically been quite focused on the M and E, with the C almost being an opaque black box.  Cracking open the C is what we do at Mark Logic.</p>
<p>Best/Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave kellogg</title>
		<link>http://www.informationarchitected.com/blog/ecm-a-rose-by-any-other-name-would-smell-as-sweet-%e2%80%93-and-i-do-mean-sweet/comment-page-1/#comment-567</link>
		<dc:creator>dave kellogg</dc:creator>
		<pubDate>Fri, 18 Dec 2009 21:25:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=1854#comment-567</guid>
		<description>Hi Carl,&lt;br&gt;&lt;br&gt;Agree that context (and content) are king and that new technologies will let people --better than ever before -- put content in context.  XML play a big role in that, but so do information and publishing companies themselves; using XML to build real content applications that help put the content in the context of a specific task (e.g., changing an airplane tire, unjamming a rifle).  &lt;br&gt;&lt;br&gt;On ECM an acronym, I&#039;ve always felt that someone needs to &quot;put the C in ECM&quot; -- I think it&#039;s historically been quite focused on the M and E, with the C almost being an opaque black box.  Cracking open the C is what we do at Mark Logic.&lt;br&gt;&lt;br&gt;Best/Dave</description>
		<content:encoded><![CDATA[<p>Hi Carl,</p>
<p>Agree that context (and content) are king and that new technologies will let people &#8211;better than ever before &#8212; put content in context.  XML play a big role in that, but so do information and publishing companies themselves; using XML to build real content applications that help put the content in the context of a specific task (e.g., changing an airplane tire, unjamming a rifle).  </p>
<p>On ECM an acronym, I&#39;ve always felt that someone needs to &#8220;put the C in ECM&#8221; &#8212; I think it&#39;s historically been quite focused on the M and E, with the C almost being an opaque black box.  Cracking open the C is what we do at Mark Logic.</p>
<p>Best/Dave</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.informationarchitected.com/blog/ecm-a-rose-by-any-other-name-would-smell-as-sweet-%e2%80%93-and-i-do-mean-sweet/comment-page-1/#comment-566</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Fri, 18 Dec 2009 18:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=1854#comment-566</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by CherylMcKinnon: RT @carlfrappaolo: #ECM A Rose by Any Other Name Would Smell as Sweet - new blog post on future of ECM http://bit.ly/4QlIKr...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by CherylMcKinnon: RT @carlfrappaolo: #ECM A Rose by Any Other Name Would Smell as Sweet &#8211; new blog post on future of ECM <a href="http://bit.ly/4QlIKr.." rel="nofollow">http://bit.ly/4QlIKr..</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention ECM: A Rose by Any Other Name Would Smell as Sweet – and I do mean Sweet &#124; Information Architected -- Topsy.com</title>
		<link>http://www.informationarchitected.com/blog/ecm-a-rose-by-any-other-name-would-smell-as-sweet-%e2%80%93-and-i-do-mean-sweet/comment-page-1/#comment-565</link>
		<dc:creator>Tweets that mention ECM: A Rose by Any Other Name Would Smell as Sweet – and I do mean Sweet &#124; Information Architected -- Topsy.com</dc:creator>
		<pubDate>Fri, 18 Dec 2009 17:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.informationarchitected.com/?p=1854#comment-565</guid>
		<description>[...] This post was mentioned on Twitter by CherylMcKinnon, carlfrappaolo. carlfrappaolo said: #ECM A Rose by Any Other Name Would Smell as Sweet - new blog post on future of ECM http://bit.ly/4QlIKr [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by CherylMcKinnon, carlfrappaolo. carlfrappaolo said: #ECM A Rose by Any Other Name Would Smell as Sweet &#8211; new blog post on future of ECM <a href="http://bit.ly/4QlIKr" rel="nofollow">http://bit.ly/4QlIKr</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/


Served from: www.informationarchitected.com @ 2010-07-29 16:34:04 -->