<?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: Migrating Content</title>
	<atom:link href="http://www.contenthere.net/2006/10/migrating-content.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.contenthere.net/2006/10/migrating-content.html</link>
	<description>Enter Content Here</description>
	<lastBuildDate>Mon, 09 Aug 2010 05:40:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.contenthere.net/2006/10/migrating-content.html/comment-page-1#comment-536</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Wed, 03 Jan 2007 17:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://www1.contenthere.net/2006/10/migrating-content.html#comment-536</guid>
		<description>It is common to hear the argument that automated migration of very unstructured content is not practical. This is why Vamosa developed what it calls &#039;source classification&#039;. &lt;br /&gt;Source Classification of content exposes the structure of all the pages so that they can be understood more clearly.  It establishes a range of page-type complexity in the source content which will contribute to mapping the existing content to the new structure/templates.&lt;br /&gt;Vamosa&#039;s Source Classification is analogous to â€˜source templatesâ€™:&lt;br /&gt;â€¢All pages are analysed for content, navigation, headers, footers etc&lt;br /&gt;â€¢Pages which have a similar make up are grouped together&lt;br /&gt;â€¢Vamosa product has a default setting which uses a fixed parameter set to give a high level classification&lt;br /&gt;â€¢Vamosa source classification parameters can then be tuned to reduce or increase the number of source templates created&lt;br /&gt;Why is it significant?&lt;br /&gt;â€¢Each source classification template type is mapped through a Vamosa rule to â€˜target templateâ€™&lt;br /&gt;â€¢The reconciliation process of these derived source templates to the discreet number of target templates is an important part of any automated migration</description>
		<content:encoded><![CDATA[<p>It is common to hear the argument that automated migration of very unstructured content is not practical. This is why Vamosa developed what it calls &#8217;source classification&#8217;. <br />Source Classification of content exposes the structure of all the pages so that they can be understood more clearly.  It establishes a range of page-type complexity in the source content which will contribute to mapping the existing content to the new structure/templates.<br />Vamosa&#8217;s Source Classification is analogous to â€˜source templatesâ€™:<br />â€¢All pages are analysed for content, navigation, headers, footers etc<br />â€¢Pages which have a similar make up are grouped together<br />â€¢Vamosa product has a default setting which uses a fixed parameter set to give a high level classification<br />â€¢Vamosa source classification parameters can then be tuned to reduce or increase the number of source templates created<br />Why is it significant?<br />â€¢Each source classification template type is mapped through a Vamosa rule to â€˜target templateâ€™<br />â€¢The reconciliation process of these derived source templates to the discreet number of target templates is an important part of any automated migration</p>
]]></content:encoded>
	</item>
</channel>
</rss>
