<?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: URI vs. URL: What&#8217;s the Difference?</title>
	<atom:link href="http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/</link>
	<description>A blog about Java, REST, and other stuff.</description>
	<pubDate>Thu, 07 Aug 2008 23:16:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Jason</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-90173</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 02 Jul 2008 15:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-90173</guid>
		<description>I guess the W3C has deprecated the term 'URL'.  I have not actually read that on their site, but I have heard it enough times from other people to believe it.

If you want to use the term 'URI' instead of 'URL', that's fine, but in order to make it technically correct (which is what this seems to be all about) the meaning of the 'URI' needs to be changed so that a URN is not a URI.

Otherwise, to take an example from Thiwanka, if a form asks you for a URI and you enter 'urn:isbn:0-395-36341-1', you're technically correct, but the form is gonna fall on it's face trying to understand it.

I think the W3C is wrong here, and I will continue to use URL when I want a URL, URN when I want a URN, and URI when I want either one.</description>
		<content:encoded><![CDATA[<p>I guess the W3C has deprecated the term &#8216;URL&#8217;.  I have not actually read that on their site, but I have heard it enough times from other people to believe it.</p>
<p>If you want to use the term &#8216;URI&#8217; instead of &#8216;URL&#8217;, that&#8217;s fine, but in order to make it technically correct (which is what this seems to be all about) the meaning of the &#8216;URI&#8217; needs to be changed so that a URN is not a URI.</p>
<p>Otherwise, to take an example from Thiwanka, if a form asks you for a URI and you enter &#8216;urn:isbn:0-395-36341-1&#8242;, you&#8217;re technically correct, but the form is gonna fall on it&#8217;s face trying to understand it.</p>
<p>I think the W3C is wrong here, and I will continue to use URL when I want a URL, URN when I want a URN, and URI when I want either one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Red2</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-88361</link>
		<dc:creator>Red2</dc:creator>
		<pubDate>Wed, 11 Jun 2008 21:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-88361</guid>
		<description>If two examples were given one for URI and one for URL, and just tell how they differe, it would be much more helpful, and much more concise than what is given here. Honestly, I couldn't understand much other than "a uri is a url" ... (or is it the other way round? :-))</description>
		<content:encoded><![CDATA[<p>If two examples were given one for URI and one for URL, and just tell how they differe, it would be much more helpful, and much more concise than what is given here. Honestly, I couldn&#8217;t understand much other than &#8220;a uri is a url&#8221; &#8230; (or is it the other way round? :-))</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-85873</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Tue, 20 May 2008 21:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-85873</guid>
		<description>To my understanding;

A Uniform Resource Indicator identifies a resource (e.g. HTML page)

A Uniform Resource Locator specifies how to access the resource (e.g via HTTP)</description>
		<content:encoded><![CDATA[<p>To my understanding;</p>
<p>A Uniform Resource Indicator identifies a resource (e.g. HTML page)</p>
<p>A Uniform Resource Locator specifies how to access the resource (e.g via HTTP)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angel</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-85414</link>
		<dc:creator>Angel</dc:creator>
		<pubDate>Thu, 15 May 2008 21:30:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-85414</guid>
		<description>To think we have lived all these years without knowing that there was a URI and that it was significant.</description>
		<content:encoded><![CDATA[<p>To think we have lived all these years without knowing that there was a URI and that it was significant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fergie</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-69147</link>
		<dc:creator>Fergie</dc:creator>
		<pubDate>Mon, 14 Jan 2008 17:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-69147</guid>
		<description>In comments form I often see field name "URI", but its field just for website's url. Is it just logic error or what?</description>
		<content:encoded><![CDATA[<p>In comments form I often see field name &#8220;URI&#8221;, but its field just for website&#8217;s url. Is it just logic error or what?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thiwanka</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-68390</link>
		<dc:creator>Thiwanka</dc:creator>
		<pubDate>Wed, 09 Jan 2008 01:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-68390</guid>
		<description>Blog is Correct.
Uniform Resource Identifier (URI), is a compact string of characters used to identify or name a resource. The main purpose of this identification is to enable interaction with representations of the resource over a network, typically the World Wide Web, using specific protocols. URIs are defined in schemes defining a specific syntax and associated protocols.

URI can be classified as a locator or a name or both. A Uniform Resource Locator (URL) is a URI that, in addition to identifying a resource, provides means of acting upon or obtaining a representation of the resource by describing its primary access mechanism or network "location". For example, the URL http://www.wikipedia.org/ is a URI that identifies a resource (Wikipedia's home page) and implies that a representation of that resource (such as the home page's current HTML code, as encoded characters) is obtainable via HTTP from a network host named www.wikipedia.org. A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace. A URN can be used to talk about a resource without implying its location or how to dereference it. For example, the URN urn:isbn:0-395-36341-1 is a URI that, like an International Standard Book Number (ISBN), allows one to talk about a book, but doesn't suggest where and how to obtain an actual copy of it.</description>
		<content:encoded><![CDATA[<p>Blog is Correct.<br />
Uniform Resource Identifier (URI), is a compact string of characters used to identify or name a resource. The main purpose of this identification is to enable interaction with representations of the resource over a network, typically the World Wide Web, using specific protocols. URIs are defined in schemes defining a specific syntax and associated protocols.</p>
<p>URI can be classified as a locator or a name or both. A Uniform Resource Locator (URL) is a URI that, in addition to identifying a resource, provides means of acting upon or obtaining a representation of the resource by describing its primary access mechanism or network &#8220;location&#8221;. For example, the URL <a href="http://www.wikipedia.org/" rel="nofollow">http://www.wikipedia.org/</a> is a URI that identifies a resource (Wikipedia&#8217;s home page) and implies that a representation of that resource (such as the home page&#8217;s current HTML code, as encoded characters) is obtainable via HTTP from a network host named <a href="http://www.wikipedia.org" rel="nofollow">http://www.wikipedia.org</a>. A Uniform Resource Name (URN) is a URI that identifies a resource by name in a particular namespace. A URN can be used to talk about a resource without implying its location or how to dereference it. For example, the URN urn:isbn:0-395-36341-1 is a URI that, like an International Standard Book Number (ISBN), allows one to talk about a book, but doesn&#8217;t suggest where and how to obtain an actual copy of it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SiNi Daily &#187; Blog Archive &#187; URI vs. URL: What’s the difference?</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60861</link>
		<dc:creator>SiNi Daily &#187; Blog Archive &#187; URI vs. URL: What’s the difference?</dc:creator>
		<pubDate>Sat, 01 Dec 2007 22:25:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60861</guid>
		<description>[...] Thanks some constructive, and not-so constructive, feedback from some readers I have updated this post to correct many of my [...]</description>
		<content:encoded><![CDATA[<p>[...] Thanks some constructive, and not-so constructive, feedback from some readers I have updated this post to correct many of my [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unterschied zwischen URL und URI &#187; Word Up!</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60518</link>
		<dc:creator>Unterschied zwischen URL und URI &#187; Word Up!</dc:creator>
		<pubDate>Thu, 29 Nov 2007 18:44:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60518</guid>
		<description>[...] Ach ja und hier noch der Link zum Eintrag. [...]</description>
		<content:encoded><![CDATA[<p>[...] Ach ja und hier noch der Link zum Eintrag. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mobile Hippie &#124; links for 2007-11-27</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60177</link>
		<dc:creator>Mobile Hippie &#124; links for 2007-11-27</dc:creator>
		<pubDate>Tue, 27 Nov 2007 16:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60177</guid>
		<description>[...] URI vs. URL: What’s the Difference? Damn! That was handy! (tags: internet resources reference uri url) [...]</description>
		<content:encoded><![CDATA[<p>[...] URI vs. URL: What’s the Difference? Damn! That was handy! (tags: internet resources reference uri url) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Davis</title>
		<link>http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60016</link>
		<dc:creator>Jon Davis</dc:creator>
		<pubDate>Mon, 26 Nov 2007 20:51:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.damnhandy.com/2007/11/19/uri-vs-url-whats-the-difference/#comment-60016</guid>
		<description>eww. my comment got truncated and turned blood-red.

ehh, you shouldn't call it "URI" if you're just referring to an [img src=".."] or [a href=".."]. That's a URL. You should call it "URI" if you're referring to a schema namespace identifier, or, in some cases, a versioned Javscript library in [script src="..". I set up a web site specifically for that purpose at cachefile.net.</description>
		<content:encoded><![CDATA[<p>eww. my comment got truncated and turned blood-red.</p>
<p>ehh, you shouldn&#8217;t call it &#8220;URI&#8221; if you&#8217;re just referring to an [img src=".."] or [a href=".."]. That&#8217;s a URL. You should call it &#8220;URI&#8221; if you&#8217;re referring to a schema namespace identifier, or, in some cases, a versioned Javscript library in [script src=&#8221;..&#8221;. I set up a web site specifically for that purpose at cachefile.net.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
