<?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: New Pricing Plan Designed To Make XML Content Management More Affordable</title>
	<atom:link href="http://thecontentwrangler.com/2007/09/18/new_pricing_plan_designed_to_make_xml_content_management_more_affordable/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2007/09/18/new_pricing_plan_designed_to_make_xml_content_management_more_affordable/</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: Dan Dube</title>
		<link>http://thecontentwrangler.com/2007/09/18/new_pricing_plan_designed_to_make_xml_content_management_more_affordable/comment-page-1/#comment-168</link>
		<dc:creator>Dan Dube</dc:creator>
		<pubDate>Thu, 20 Sep 2007 02:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=431#comment-168</guid>
		<description>&lt;p&gt;Gordon,
&lt;/p&gt;
&lt;p&gt;
Thanks for your comments. As you mentioned, you are someone who spends most of your day working with content interactively, so this type of plan may not make the most sense for your situation. For this reason, we still continue to offer our traditional &#8220;floating license&#8221; plan for individual users.
&lt;/p&gt;
&lt;p&gt;
However, we created our new Pay-Per-Minute plan to address a different type of user profile, who we felt were not being properly served by the industry: small to mid-size businesses, or companies where documentation/training materials may only be updated occasionally (once or twice a year). We wanted to put together a solution for these folks that would make it affordable for them to enjoy the benefits of migrating to XML, and the idea of Pay-Per-Minute seems like a good way to address this.
&lt;/p&gt;
&lt;p&gt;
There have also been a recent discussion thread here in the Content Wrangler blog about the expense of doing a Proof of Concept. We feel that with our new Pay-Per-Minute plan, we now can make a great departmental proof-of-concept environment available for less than USD$1000/month. This will hopefully encourage many people who are interested in the idea of moving to XML/DITA within a CMS to actually take the next step and try it!
&lt;/p&gt;
&lt;p&gt;
With regards to the possibility that users may do the bulk of their work outside of DocZone and then only use our system to publish...well, that certainly will be interesting to see. We feel that once users get comfortable with the ease of use and intuitive nature of a truly &#8220;all inclusive&#8221; environment that we provide within DocZone, that they will find it a much more efficient and comfortable experience to just use DocZone for all of their tasks...and we&#8217;re willing to take the risk that some users may choose to do much of their work in an &#8220;offline&#8221; mode. The benefits we offer, such as the integrated translation memory system and the collaborative XML review/annotation features, are hopefully compelling enough to encourage these users to stay within the DocZone environment.
&lt;/p&gt;
&lt;p&gt;
Just to be clear: this isn&#8217;t about DocZone &#8220;making more money this way than with a traditional license model&#8221;. This is about giving the flexibility to end users to decide which pricing model makes more sense to them. We&#8217;re happy to sell our solution either way!&#160; &lt;img src=&quot;http://thecontentwrangler.com/images/smileys/grin.gif&quot; width=&quot;19&quot; height=&quot;19&quot; alt=&quot;grin&quot; style=&quot;border:0;&quot; /&gt;
&lt;/p&gt;
&lt;p&gt;
Dan Dube
&lt;br /&gt;
Managing Director, US Operations
&lt;br /&gt;
DocZone.com
&lt;br /&gt;
&lt;script type=&quot;text/javascript&quot;&gt;
//&lt;![CDATA[
var l=new Array();
l[0]=&#039;&gt;&#039;;l[1]=&#039;a&#039;;l[2]=&#039;/&#039;;l[3]=&#039;&lt;&#039;;l[4]=&#039; 109&#039;;l[5]=&#039; 111&#039;;l[6]=&#039; 99&#039;;l[7]=&#039; 46&#039;;l[8]=&#039; 101&#039;;l[9]=&#039; 110&#039;;l[10]=&#039; 111&#039;;l[11]=&#039; 122&#039;;l[12]=&#039; 99&#039;;l[13]=&#039; 111&#039;;l[14]=&#039; 100&#039;;l[15]=&#039; 64&#039;;l[16]=&#039; 101&#039;;l[17]=&#039; 98&#039;;l[18]=&#039; 117&#039;;l[19]=&#039; 100&#039;;l[20]=&#039; 100&#039;;l[21]=&#039;&gt;&#039;;l[22]=&#039;\&quot;&#039;;l[23]=&#039; 109&#039;;l[24]=&#039; 111&#039;;l[25]=&#039; 99&#039;;l[26]=&#039; 46&#039;;l[27]=&#039; 101&#039;;l[28]=&#039; 110&#039;;l[29]=&#039; 111&#039;;l[30]=&#039; 122&#039;;l[31]=&#039; 99&#039;;l[32]=&#039; 111&#039;;l[33]=&#039; 100&#039;;l[34]=&#039; 64&#039;;l[35]=&#039; 101&#039;;l[36]=&#039; 98&#039;;l[37]=&#039; 117&#039;;l[38]=&#039; 100&#039;;l[39]=&#039; 100&#039;;l[40]=&#039;:&#039;;l[41]=&#039;o&#039;;l[42]=&#039;t&#039;;l[43]=&#039;l&#039;;l[44]=&#039;i&#039;;l[45]=&#039;a&#039;;l[46]=&#039;m&#039;;l[47]=&#039;\&quot;&#039;;l[48]=&#039;=&#039;;l[49]=&#039;f&#039;;l[50]=&#039;e&#039;;l[51]=&#039;r&#039;;l[52]=&#039;h&#039;;l[53]=&#039;a &#039;;l[54]=&#039;&lt;&#039;;
for (var i = l.length-1; i &gt;= 0; i=i-1){
if (l[i].substring(0, 1) == &#039; &#039;) document.write(&quot;&amp;#&quot;+unescape(l[i].substring(1))+&quot;;&quot;);
else document.write(unescape(l[i]));
}
//]]&gt;
&lt;/script&gt;
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Gordon,
</p>
<p>
Thanks for your comments. As you mentioned, you are someone who spends most of your day working with content interactively, so this type of plan may not make the most sense for your situation. For this reason, we still continue to offer our traditional &#8220;floating license&#8221; plan for individual users.
</p>
<p>
However, we created our new Pay-Per-Minute plan to address a different type of user profile, who we felt were not being properly served by the industry: small to mid-size businesses, or companies where documentation/training materials may only be updated occasionally (once or twice a year). We wanted to put together a solution for these folks that would make it affordable for them to enjoy the benefits of migrating to XML, and the idea of Pay-Per-Minute seems like a good way to address this.
</p>
<p>
There have also been a recent discussion thread here in the Content Wrangler blog about the expense of doing a Proof of Concept. We feel that with our new Pay-Per-Minute plan, we now can make a great departmental proof-of-concept environment available for less than USD$1000/month. This will hopefully encourage many people who are interested in the idea of moving to XML/DITA within a CMS to actually take the next step and try it!
</p>
<p>
With regards to the possibility that users may do the bulk of their work outside of DocZone and then only use our system to publish&#8230;well, that certainly will be interesting to see. We feel that once users get comfortable with the ease of use and intuitive nature of a truly &#8220;all inclusive&#8221; environment that we provide within DocZone, that they will find it a much more efficient and comfortable experience to just use DocZone for all of their tasks&#8230;and we&#8217;re willing to take the risk that some users may choose to do much of their work in an &#8220;offline&#8221; mode. The benefits we offer, such as the integrated translation memory system and the collaborative XML review/annotation features, are hopefully compelling enough to encourage these users to stay within the DocZone environment.
</p>
<p>
Just to be clear: this isn&#8217;t about DocZone &#8220;making more money this way than with a traditional license model&#8221;. This is about giving the flexibility to end users to decide which pricing model makes more sense to them. We&#8217;re happy to sell our solution either way!&nbsp; <img src="http://thecontentwrangler.com/images/smileys/grin.gif" width="19" height="19" alt="grin" style="border:0;" />
</p>
<p>
Dan Dube<br />
<br />
Managing Director, US Operations<br />
<br />
DocZone.com<br />
<br />
<script type="text/javascript">
//< ![CDATA[
var l=new Array();
l[0]='>';l[1]='a';l[2]='/';l[3]='< ';l[4]=' 109';l[5]=' 111';l[6]=' 99';l[7]=' 46';l[8]=' 101';l[9]=' 110';l[10]=' 111';l[11]=' 122';l[12]=' 99';l[13]=' 111';l[14]=' 100';l[15]=' 64';l[16]=' 101';l[17]=' 98';l[18]=' 117';l[19]=' 100';l[20]=' 100';l[21]='>';l[22]='\"';l[23]=' 109';l[24]=' 111';l[25]=' 99';l[26]=' 46';l[27]=' 101';l[28]=' 110';l[29]=' 111';l[30]=' 122';l[31]=' 99';l[32]=' 111';l[33]=' 100';l[34]=' 64';l[35]=' 101';l[36]=' 98';l[37]=' 117';l[38]=' 100';l[39]=' 100';l[40]=':';l[41]='o';l[42]='t';l[43]='l';l[44]='i';l[45]='a';l[46]='m';l[47]='\"';l[48]='=';l[49]='f';l[50]='e';l[51]='r';l[52]='h';l[53]='a ';l[54]='< ';
for (var i = l.length-1; i >= 0; i=i-1){
if (l[i].substring(0, 1) == ' ') document.write("&#"+unescape(l[i].substring(1))+";");
else document.write(unescape(l[i]));
}
//]]>
</script></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon McLean</title>
		<link>http://thecontentwrangler.com/2007/09/18/new_pricing_plan_designed_to_make_xml_content_management_more_affordable/comment-page-1/#comment-167</link>
		<dc:creator>Gordon McLean</dc:creator>
		<pubDate>Wed, 19 Sep 2007 12:21:40 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=431#comment-167</guid>
		<description>&lt;p&gt;Interesting. My initial reaction was horror. As one who spends most of my working day creating, editing, managing and working with content then this would seem foolhardy.
&lt;/p&gt;
&lt;p&gt;
Still not sure it makes that much sense either, isn&#8217;t there a danger that users of DocZone will just push their creation/collaboration stage to, say, a Wiki, and only push into DocZone for publishing&#8230; which whilst it will be cheaper for the end user, loosens the ties to DocZone and ... well i guess they&#8217;ve done their sums and figure they&#8217;ll still make more money this way than with a traditional license model.
&lt;/p&gt;
&lt;p&gt;
Will be interesting to see how this one pans out.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Interesting. My initial reaction was horror. As one who spends most of my working day creating, editing, managing and working with content then this would seem foolhardy.
</p>
<p>
Still not sure it makes that much sense either, isn&#8217;t there a danger that users of DocZone will just push their creation/collaboration stage to, say, a Wiki, and only push into DocZone for publishing&#8230; which whilst it will be cheaper for the end user, loosens the ties to DocZone and &#8230; well i guess they&#8217;ve done their sums and figure they&#8217;ll still make more money this way than with a traditional license model.
</p>
<p>
Will be interesting to see how this one pans out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

