/view is redundant, as it exposes something system-specific, see the point about cruft above. I know you use mod_rewrite behind the scenes to map it to something, and this part of the URI is actually necessary, so may I suggest renaming it /articles instead?

Hi,

You think that I use mod_rewrite, I don't. Ever. I usually use HTML::Mason or ModPerl, and my application maps URLs to Mason components or Perl functions directly.

.html does talk about the language you use. In five years you want to serve the content perhaps in XHTML with embedded namespaces or who knows what wacky stuff comes along and the file ending is entirely unappropriate when someone saves the document locally. You're safe with leaving the ending off.

You're right about this, but if in the future my application start generating XHTML, I can easly change also the link rotines or components to write urls like /view/some-special-interest-item.xhtml, and the only thing that is in my database unformated story is something like [[Some Special Interest Item]], and it's my engine that generates the url for that.

The same way, except for special cases (Google Videos, You tube, etc), I don't have any HTML in my content database, only special formating chars, that can be translated to HTML, XHTML, LaTeX or anything else I need in the future.

That's the way I like it.