<?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: How to name your files</title>
	<atom:link href="http://usabilitythoughts.com/how-to-name-your-files.html/feed" rel="self" type="application/rss+xml" />
	<link>http://usabilitythoughts.com/how-to-name-your-files.html</link>
	<description>content meets user</description>
	<lastBuildDate>Tue, 13 Dec 2011 11:48:53 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Brian R Cline</title>
		<link>http://usabilitythoughts.com/how-to-name-your-files.html/comment-page-1#comment-2314</link>
		<dc:creator>Brian R Cline</dc:creator>
		<pubDate>Sat, 08 Aug 2009 16:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=100#comment-2314</guid>
		<description>@Adrian:

I have to say that I agree about SEO improvements.  

I find it to be one of the most frustrating things when you download something to view later and because the developer didn&#039;t spend that extra time giving the content a meaningful name you have to guess what the contents of the file are.

@Ahava: I don&#039;t think that necessarily by keywords is a great solution either at least for usability. 

I would prefer that at least part of the title makes it into the name and then maybe a keyword or too.</description>
		<content:encoded><![CDATA[<p>@Adrian:</p>
<p>I have to say that I agree about SEO improvements.  </p>
<p>I find it to be one of the most frustrating things when you download something to view later and because the developer didn&#8217;t spend that extra time giving the content a meaningful name you have to guess what the contents of the file are.</p>
<p>@Ahava: I don&#8217;t think that necessarily by keywords is a great solution either at least for usability. </p>
<p>I would prefer that at least part of the title makes it into the name and then maybe a keyword or too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stririle SEO/SEM 27.03-3.04 &#124; Surf Media</title>
		<link>http://usabilitythoughts.com/how-to-name-your-files.html/comment-page-1#comment-21</link>
		<dc:creator>Stririle SEO/SEM 27.03-3.04 &#124; Surf Media</dc:creator>
		<pubDate>Fri, 03 Apr 2009 10:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=100#comment-21</guid>
		<description>[...] Denumeste-ti fisierele din site in functie de cuvintele cheie. Pentru mai multe detalii citeste aici. [...]</description>
		<content:encoded><![CDATA[<p>[...] Denumeste-ti fisierele din site in functie de cuvintele cheie. Pentru mai multe detalii citeste aici. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://usabilitythoughts.com/how-to-name-your-files.html/comment-page-1#comment-18</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 01 Apr 2009 21:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=100#comment-18</guid>
		<description>you&#039;re doing this for the user, not for the search engines, if they benefit too from it, that&#039;s good....</description>
		<content:encoded><![CDATA[<p>you&#8217;re doing this for the user, not for the search engines, if they benefit too from it, that&#8217;s good&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahava</title>
		<link>http://usabilitythoughts.com/how-to-name-your-files.html/comment-page-1#comment-17</link>
		<dc:creator>Ahava</dc:creator>
		<pubDate>Wed, 01 Apr 2009 21:32:20 +0000</pubDate>
		<guid isPermaLink="false">http://usabilitythoughts.com/?p=100#comment-17</guid>
		<description>Name your files according to keywords!  Works everytime...</description>
		<content:encoded><![CDATA[<p>Name your files according to keywords!  Works everytime&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

