<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Product Attributes Matter - And I Can Prove it</title>
	<link>http://www.loveyourfeed.com/product-attributes-matter-and-i-can-prove-it-22.htm</link>
	<description>Data feed optimization for the shopping comparison engines</description>
	<pubDate>Wed, 20 Aug 2008 14:32:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Michael Golden</title>
		<link>http://www.loveyourfeed.com/product-attributes-matter-and-i-can-prove-it-22.htm#comment-30</link>
		<pubDate>Fri, 08 Dec 2006 04:36:10 +0000</pubDate>
		<guid>http://www.loveyourfeed.com/product-attributes-matter-and-i-can-prove-it-22.htm#comment-30</guid>
					<description>Well Said Sushant.  FYI - we'll be there in 7 weeks.  We have a plan my man.</description>
		<content:encoded><![CDATA[<p>Well Said Sushant.  FYI - we&#8217;ll be there in 7 weeks.  We have a plan my man.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Sushant Ajmani</title>
		<link>http://www.loveyourfeed.com/product-attributes-matter-and-i-can-prove-it-22.htm#comment-25</link>
		<pubDate>Mon, 04 Dec 2006 02:01:38 +0000</pubDate>
		<guid>http://www.loveyourfeed.com/product-attributes-matter-and-i-can-prove-it-22.htm#comment-25</guid>
					<description>Brian, no doubt this is a great post and I really like your idea but; extracting and formatting the Product Attributes data is one of the most challenging task these days. I have implemented guided navigation for some of the prominent sites and honestly speaking; getting the Product Attributes data was the biggest challenge for me. Most of the retailing sites have good amount of Product Attributes data in their PRODUCT DESCRIPTION, TITLE and CATEGORY PATH; and some companies use CSS to present them effectively on their sites but; the challenge is to filter out the marketable attributes with their values from these descriptions and put them under different buckets. This is atleast 3-4 months exercise based on your catalog and not every company in this retailing sector have budget and time to carry out this exercise and even if they do it; they don't follow it consistently. I would love to see CSE Engines modifying their DATA PARSING algorithms and come up with some great data filtering and formatting techniques and present the data in relevant attributes. I have seen some of the CSE sites who have started showing filterable attributes but; only those stores can take advantage of this who have guided navigation on their site or, those who have a smaller catalog but; the mid-size big catalog companies got affected by this more.</description>
		<content:encoded><![CDATA[<p>Brian, no doubt this is a great post and I really like your idea but; extracting and formatting the Product Attributes data is one of the most challenging task these days. I have implemented guided navigation for some of the prominent sites and honestly speaking; getting the Product Attributes data was the biggest challenge for me. Most of the retailing sites have good amount of Product Attributes data in their PRODUCT DESCRIPTION, TITLE and CATEGORY PATH; and some companies use CSS to present them effectively on their sites but; the challenge is to filter out the marketable attributes with their values from these descriptions and put them under different buckets. This is atleast 3-4 months exercise based on your catalog and not every company in this retailing sector have budget and time to carry out this exercise and even if they do it; they don&#8217;t follow it consistently. I would love to see CSE Engines modifying their DATA PARSING algorithms and come up with some great data filtering and formatting techniques and present the data in relevant attributes. I have seen some of the CSE sites who have started showing filterable attributes but; only those stores can take advantage of this who have guided navigation on their site or, those who have a smaller catalog but; the mid-size big catalog companies got affected by this more.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
