<?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"
	>
<channel>
	<title>Comments on: My URI scheme</title>
	<atom:link href="http://www.troidus.com/article/8/feed" rel="self" type="application/rss+xml" />
	<link>http://www.troidus.com/article/8</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Tue, 06 Jan 2009 04:49:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: trovster</title>
		<link>http://www.troidus.com/article/8#comment-7</link>
		<dc:creator>trovster</dc:creator>
		<pubDate>Sun, 16 Apr 2006 16:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://troidus.com/article/4#comment-7</guid>
		<description>Of course you should redirect using 301, permanent. URIs should be permanent and unique, and if you move something you should point it to the new place.

You say "archives" relates to a blog, but I really don't see how that is a direct relation. A general news site has archives. Infact anything with date-specific posts has an archives section.

I think they URL scheme which you've changed to is a lot worse. First of all, you shouldn't expose the database unique identifier to the public. Also, just using a number remove the 'nice-url' ethos which should also be 'hackable'. Tom Coates talks about this, and I certainly agree.

I think the /yyyy/mm/dd/article is a perfect URI scheme (the /archives/ bit isn't needed, fair enough) and it certainly isn't "clunky". And it's hackable, you can remove the 'article' and get posts under that day (usually just the one on many blogs, but removing the day should show an archive of the month. And finally, an archive of that year, whether it be a simple list or pagnation extracts.</description>
		<content:encoded><![CDATA[<p>Of course you should redirect using 301, permanent. URIs should be permanent and unique, and if you move something you should point it to the new place.</p>
<p>You say &#8220;archives&#8221; relates to a blog, but I really don&#8217;t see how that is a direct relation. A general news site has archives. Infact anything with date-specific posts has an archives section.</p>
<p>I think they URL scheme which you&#8217;ve changed to is a lot worse. First of all, you shouldn&#8217;t expose the database unique identifier to the public. Also, just using a number remove the &#8216;nice-url&#8217; ethos which should also be &#8216;hackable&#8217;. Tom Coates talks about this, and I certainly agree.</p>
<p>I think the /yyyy/mm/dd/article is a perfect URI scheme (the /archives/ bit isn&#8217;t needed, fair enough) and it certainly isn&#8217;t &#8220;clunky&#8221;. And it&#8217;s hackable, you can remove the &#8216;article&#8217; and get posts under that day (usually just the one on many blogs, but removing the day should show an archive of the month. And finally, an archive of that year, whether it be a simple list or pagnation extracts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Indranil</title>
		<link>http://www.troidus.com/article/8#comment-6</link>
		<dc:creator>Indranil</dc:creator>
		<pubDate>Wed, 15 Mar 2006 03:23:54 +0000</pubDate>
		<guid isPermaLink="false">http://troidus.com/article/4#comment-6</guid>
		<description>I do know how to redirect using 301. However, I just prefer not to, as I am trying to go a different way with the content of this site.</description>
		<content:encoded><![CDATA[<p>I do know how to redirect using 301. However, I just prefer not to, as I am trying to go a different way with the content of this site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EngLee</title>
		<link>http://www.troidus.com/article/8#comment-5</link>
		<dc:creator>EngLee</dc:creator>
		<pubDate>Wed, 15 Mar 2006 00:50:50 +0000</pubDate>
		<guid isPermaLink="false">http://troidus.com/article/4#comment-5</guid>
		<description>However, Mathias is going to use 301 to redirect the pages. You may contact him on how he goes about with it.</description>
		<content:encoded><![CDATA[<p>However, Mathias is going to use 301 to redirect the pages. You may contact him on how he goes about with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Indranil</title>
		<link>http://www.troidus.com/article/8#comment-4</link>
		<dc:creator>Indranil</dc:creator>
		<pubDate>Tue, 14 Mar 2006 16:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://troidus.com/article/4#comment-4</guid>
		<description>Well, yes. Of course, this'll also mean that my ranking will probably suffer. But, what's to be done has to be done.</description>
		<content:encoded><![CDATA[<p>Well, yes. Of course, this&#8217;ll also mean that my ranking will probably suffer. But, what&#8217;s to be done has to be done.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: EngLee</title>
		<link>http://www.troidus.com/article/8#comment-3</link>
		<dc:creator>EngLee</dc:creator>
		<pubDate>Tue, 14 Mar 2006 06:32:41 +0000</pubDate>
		<guid isPermaLink="false">http://troidus.com/article/4#comment-3</guid>
		<description>So, those links to your posts (especially search engine cache) will lead to 404 now.</description>
		<content:encoded><![CDATA[<p>So, those links to your posts (especially search engine cache) will lead to 404 now.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
