Benx Shen's Library tagged what-is → View Popular

13 Oct 09

24 Nov 07

I think simplest explanation works best:

URI identifies. URL locates.

or

URI is a name. URL is a location.
You got it all wrong. It is not about if a URI is a name is a locator or not. Or if the URI has a file extension or not. (URI never has the concept of file extension, it is that you think it has a file extension. ). It is about if a URI is bound with a network protocol. In other words, if you can get something back from the URI. W3C didn’t realize this earlier. Now, the term URL and URN is deprecated because the distinction is arbitrary.

Just use URI from now on.

See the URI spec http://www.ietf.org/rfc/rfc3986.txt.
1 more annotations...
- I agree, the article is misleading. A URI merely gives a resource a name and doesn’t say where you’ll find it. The same resource can be found at multiple locations (without regard to filename extension). A URL tells you “if you go here, you’ll find the resource” without regard to its name. However, the URL can also be used as a URI.
  
  I try to explain the difference using examples with made-up schemes:
  
  fuel:coal = URI (identifies/names the resource)
  
  mine:US-PA-NewEagle-MapleCreekMine = URL (specifies an address/location)
  
  food:Beef-Bowl = URI
  
  restaurant:HK-Central-Yoshinoya = URL
  
  blog:Ajaxian = URI
  
  website:www.ajaxian.com = URL

09 Nov 07

04 Nov 07

30 Dec 06

Comet is a programming technique that enables web servers to send data to the client without having any need for the client to request it. It allows creation of event-driven web applications which are hosted in the browser.