<?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: Effective Content Reuse: Storing Paragraphs, Not Topics, Is Key to Content Management Success</title>
	<atom:link href="http://thecontentwrangler.com/2008/10/17/effective_content_reuse_storing_paragraphs_not_topics_is_key_to_content_man/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2008/10/17/effective_content_reuse_storing_paragraphs_not_topics_is_key_to_content_man/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Fri, 18 May 2012 01:51:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Paul Trotter</title>
		<link>http://thecontentwrangler.com/2008/10/17/effective_content_reuse_storing_paragraphs_not_topics_is_key_to_content_man/comment-page-1/#comment-401</link>
		<dc:creator>Paul Trotter</dc:creator>
		<pubDate>Thu, 27 Nov 2008 21:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=310#comment-401</guid>
		<description>&lt;p&gt;Hi David,
&lt;/p&gt;
&lt;p&gt;
The on-the-fly comparison and suggestion is actually the magic in the technology and is the subject of a patent. I would be happy to show you it working in practice and you can certainly read about it on our website &lt;a href=&quot;http://www.author-it.com/index.php?page=xtendauthoringmemory&quot; rel=&quot;nofollow&quot;&gt;http://www.author-it.com/index.php?page=xtendauthoringmemory&lt;/a&gt; and get an idea of the visuals.
&lt;/p&gt;
&lt;p&gt;
Typically the response time for suggestions is sub-second so it is certainly fast enough to be effective. Our current research shows a 20-30% reduction in authoring time through the ability to reuse existing content quickly and easily.
&lt;/p&gt;
&lt;p&gt;
As far as identification of paragraphs, this is probably the easiest part. Technically speaking it is quite easy to determine where a paragraph or block begins and ends. Identifying a sentence is a much more subjective and difficult problem, which is primarily why we chose to go for paragraphs.
&lt;/p&gt;
&lt;p&gt;
Paul
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi David,
</p>
<p>
The on-the-fly comparison and suggestion is actually the magic in the technology and is the subject of a patent. I would be happy to show you it working in practice and you can certainly read about it on our website <a href="http://www.author-it.com/index.php?page=xtendauthoringmemory" rel="nofollow">http://www.author-it.com/index.php?page=xtendauthoringmemory</a> and get an idea of the visuals.
</p>
<p>
Typically the response time for suggestions is sub-second so it is certainly fast enough to be effective. Our current research shows a 20-30% reduction in authoring time through the ability to reuse existing content quickly and easily.
</p>
<p>
As far as identification of paragraphs, this is probably the easiest part. Technically speaking it is quite easy to determine where a paragraph or block begins and ends. Identifying a sentence is a much more subjective and difficult problem, which is primarily why we chose to go for paragraphs.
</p>
<p>
Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Bowen</title>
		<link>http://thecontentwrangler.com/2008/10/17/effective_content_reuse_storing_paragraphs_not_topics_is_key_to_content_man/comment-page-1/#comment-400</link>
		<dc:creator>David Bowen</dc:creator>
		<pubDate>Fri, 17 Oct 2008 14:36:08 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=310#comment-400</guid>
		<description>&lt;p&gt;Paul: This is a great article, but I&#8217;m unclear about how similarities between paragraphs are identified on the fly, literally while the author is typing. I haven&#8217;t seen such a system in practice, but it seems unlikely that the CMS would know that a paragraph being created is similar to another already in existence, at least in time for it to result in any kind of improvement in efficiency. How quickly can such as system identify similarities in paragraphs?
&lt;/p&gt;
&lt;p&gt;
Another issue: from a writer&#8217;s standpoint, there isn&#8217;t a commonly understood approach for chunking content into paragraphs. In fact, I&#8217;m not sure there can ever be, because different writers have different compositional styles, and different types of content require different approaches to chunking content. I&#8217;m not sure it&#8217;s even possible to create an easy set of rules for breaking content into paragraphs (see Strunk and White to see the complexity of the problem). This would affect the usefulness of this approach, since it could lead to contextual confusion, where mismatched paragraphs end up being sown together. Paragraphs need to flow together and connect in a logical and artful way, but if there aren&#8217;t rules for beginning and ending paragraphs, how is that possible?
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Paul: This is a great article, but I&#8217;m unclear about how similarities between paragraphs are identified on the fly, literally while the author is typing. I haven&#8217;t seen such a system in practice, but it seems unlikely that the CMS would know that a paragraph being created is similar to another already in existence, at least in time for it to result in any kind of improvement in efficiency. How quickly can such as system identify similarities in paragraphs?
</p>
<p>
Another issue: from a writer&#8217;s standpoint, there isn&#8217;t a commonly understood approach for chunking content into paragraphs. In fact, I&#8217;m not sure there can ever be, because different writers have different compositional styles, and different types of content require different approaches to chunking content. I&#8217;m not sure it&#8217;s even possible to create an easy set of rules for breaking content into paragraphs (see Strunk and White to see the complexity of the problem). This would affect the usefulness of this approach, since it could lead to contextual confusion, where mismatched paragraphs end up being sown together. Paragraphs need to flow together and connect in a logical and artful way, but if there aren&#8217;t rules for beginning and ending paragraphs, how is that possible?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

