<?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: [Viewpoint] The Right and Wrong of Quark and Adobe Strategies</title>
	<atom:link href="http://thecontentwrangler.com/2008/05/06/viewpoint_the_right_and_wrong_of_quark_and_adobe_strategies/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2008/05/06/viewpoint_the_right_and_wrong_of_quark_and_adobe_strategies/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Fri, 10 Feb 2012 16:31:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Eric Kuhnen</title>
		<link>http://thecontentwrangler.com/2008/05/06/viewpoint_the_right_and_wrong_of_quark_and_adobe_strategies/comment-page-1/#comment-312</link>
		<dc:creator>Eric Kuhnen</dc:creator>
		<pubDate>Wed, 07 May 2008 16:19:56 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=345#comment-312</guid>
		<description>&lt;p&gt;M Pinault,
&lt;/p&gt;
&lt;p&gt;
You&#8217;ve cited a fine example and it dovetails with my experience.&#160; One of my clients considered offering its CMS to the SMB market, but found that the value proposition SMB customers wasn&#8217;t as dramatic as its was to a global enterprise customers.
&lt;/p&gt;
&lt;p&gt;
In your example, a 50-page customer hand-out does not have enough complexity, variety, distribution to warrant the up-front and on-going expenditures of an RDBMS-based ECM.
&lt;/p&gt;
&lt;p&gt;
Now, if Quark built a file-system CMS as part of their DPS solution, your client could have embarked on a campaign to increase reuse without the overhead of learning to use an ECM.&#160; In that way, DPS would not be overkill, if I understand the implication of your comment.
&lt;/p&gt;
&lt;p&gt;
Thanks,
&lt;/p&gt;
&lt;p&gt;
Eric
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>M Pinault,
</p>
<p>
You&#8217;ve cited a fine example and it dovetails with my experience.&nbsp; One of my clients considered offering its CMS to the SMB market, but found that the value proposition SMB customers wasn&#8217;t as dramatic as its was to a global enterprise customers.
</p>
<p>
In your example, a 50-page customer hand-out does not have enough complexity, variety, distribution to warrant the up-front and on-going expenditures of an RDBMS-based ECM.
</p>
<p>
Now, if Quark built a file-system CMS as part of their DPS solution, your client could have embarked on a campaign to increase reuse without the overhead of learning to use an ECM.&nbsp; In that way, DPS would not be overkill, if I understand the implication of your comment.
</p>
<p>
Thanks,
</p>
<p>
Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M Pinault</title>
		<link>http://thecontentwrangler.com/2008/05/06/viewpoint_the_right_and_wrong_of_quark_and_adobe_strategies/comment-page-1/#comment-311</link>
		<dc:creator>M Pinault</dc:creator>
		<pubDate>Wed, 07 May 2008 12:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=345#comment-311</guid>
		<description>&lt;p&gt;Informative article, especially concerning how &#8220;to get the biggest bang for ECM buck.&#8221; The companies that I work with typically want a publishing solution with content management capabilities, but they have a small number of documents and are in reality are unwilling to pay for and maintain what they ideally want. One organization used Quark XPress for years to handle their 50-paged customer handout, but even though they want to content re-use, I think that a &#8220;Dynamic Publishing Solution&#8221; is overkill.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Informative article, especially concerning how &#8220;to get the biggest bang for ECM buck.&#8221; The companies that I work with typically want a publishing solution with content management capabilities, but they have a small number of documents and are in reality are unwilling to pay for and maintain what they ideally want. One organization used Quark XPress for years to handle their 50-paged customer handout, but even though they want to content re-use, I think that a &#8220;Dynamic Publishing Solution&#8221; is overkill.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

