Dave Watts wrote:
>>> You'll notice that this is an SES URL, on an IIS 6 server ...
>> I would argue that in fact that's not a search engine 
>> friendly url at all. That url gives me no context for what 
>> I'm going to find on the page if I follow the link.
> 
> Note the acronym: SES. Not SEF. The last "S" stands for "safe". The point is
> simply that dynamic elements of the URL can be made to look static.

You are correct, I misread your post. That's what I get for being busy 
and misreading acronyms :)

> I agree with you that pages should have human-readable, consistent URLs, and
> that this may well increase relevance and page rank. We use that approach
> very successfully in our CMS implementations. But all that is entirely
> beside the point, isn't it?
> 
>> A URL (or more properly a URI) is meant to provide a descriptive 
>> and permanent location for a piece of content.
> 
> It is not more proper to call a URL a URI. URLs are a subset of URIs, and it
> is useful to differentiate between URLs and other sorts of URIs.
> 
> http://en.wikipedia.org/wiki/Uniform_Resource_Identifier#Relationship_to_URL
> _and_URN
> 
> If you're specifying a location, it's a URL.

I disagree. URI's fundamentally have a scheme that specifies a transport 
mechanism (mailto, ftp, file, http, etc) followed by an address. Its 
part of the spec. As the wikipedia article that you linked to mentions, 
URL has been deprecated in favor of URI for some time:

"In technical publications, especially standards produced by the IETF 
and the W3C, the term URL has long been deprecated, as it is rarely 
necessary to distinguish between URLs and URIs."

It is important to have consistent, permanent and optimally human 
readable URI's regardless of whether they are locations of a web page or 
some other type of URI.

I suspect that we are splitting hairs here in a way that most people 
don't really care about. URL vs URI is largely a semantic point and 
doesn't impact the life of most developers. But given that URI is what 
is used by most of the W3C and IETF, I like to try and explain it where 
possible so that other developers understand what's coming out of the 
standards setting bodies.

Cheers,
Judah


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Upgrade to Adobe ColdFusion MX7 
Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs 
http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:267166
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4

Reply via email to