What is the difference between a URI, a URL and a

Question

People talk about URLs, URIs and URNs as if they're different things, but they look the same to the naked eye.

What are the distinguishable differences between them?

Answer 1

A Uniform Resource Identifier (URI) is a string of characters which identifies an Internet Resource.

The most common URI is the Uniform Resource Locator (URL) which identifies an Internet domain address. Another, not so common type of URI is the Universal Resource Name (URN).

Answer 2

Identifier = Name + Location

Every URL(Uniform Resource Locator) is a URI(Uniform Resource Identifier), abstractly speaking, but every URI is not a URL. There is another subcategory of URI is URN (Uniform Resource Name), which is a named resource but do not specify how to locate them, like mailto, news, ISBN is URIs. Source

URN:

• URN Format : urn:[namespace identifier]:[namespace specific string]
• urn: and : stand for themselves.
• Examples:
  • urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66
  • urn:ISSN:0167-6423
  • urn:isbn:096139210x
  • Amazon Resource Names (ARNs) is a uniquely identify AWS resources.
    • ARN Format : arn:partition:service:region:account-id:resource

URL:

• URL Format : [scheme]://[Domain][Port]/[path]?[queryString]#[fragmentId]
• :,//,? and # stand for themselves.
• schemes are https,ftp,gopher,mailto,news,telnet,file,man,info,whatis,ldap...
• Examples:
  • http://ip_server/path?query
  • ftp://ip_server/path
  • mailto:email-address
  • news:newsgroup-name
  • telnet://ip_server/
  • file://ip_server/path_segments
  • ldap://hostport/dn?attributes?scope?filter?extensions

Analogy:
To reach a person: Driving(protocol others SMS, email, phone), Address(hostname other phone-number, emailid) and person name(object name with a relative path).

Answer 3

URI -- Uniform Resource Identifier

URIs are a standard for identifying documents using a short string of numbers, letters, and symbols. They are defined by RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax. URLs, URNs, and URCs are all types of URI.

URL -- Uniform Resource Locator

Contains information about how to fetch a resource from its location. For example:

• http://example.com/mypage.html
• ftp://example.com/download.zip
• mailto:[e-mail]
• file:///home/user/file.txt
• tel:[phone]
• http://example.com/resource?foo=bar#fragment
• /other/link.html (A relative URL, only useful in the context of another URL)

URLs always start with a protocol (http) and usually contain information such as the network host name (example.com) and often a document path (/foo/mypage.html). URLs may have query parameters and fragment identifiers.

URN -- Uniform Resource Name

Identifies a resource by a unique and persistent name, but doesn't necessarily tell you how to locate it on the internet. It usually starts with the prefix urn: For example:

• urn:isbn:0451450523 to identify a book by its ISBN number.
• urn:uuid:6e8bc430-9c3a-11d9-9669-0800200c9a66 a globally unique identifier
• urn:publishing:book - An XML namespace that identifies the document as a type of book.

URNs can identify ideas and concepts. They are not restricted to identifying documents. When a URN does represent a document, it can be translated into a URL by a "resolver". The document can then be downloaded from the URL.

URC -- Uniform Resource Citation

Points to meta data about a document rather than to the document itself. An example of a URC is one that points to the HTML source code of a page like: view-source:http://example.com/

Data URI

Rather than locating it on the internet, or naming it, data can be placed directly into a URI. An example would be data:,Hello%20World.

---

Frequently Asked Questions

I've heard that I shouldn't say URL anymore, why?

The W3 spec for HTML says that the href of an anchor tag can contain a URI, not just a URL. You should be able to put in a URN such as <a href="urn:isbn:0451450523">. Your browser would then resolve that URN to a URL and download the book for you.

Do any browsers actually know how to fetch documents by URN?

Not that I know of, but modern web browser do implement the data URI scheme.

Does the difference between URL and URI have anything to do with whether it is relative or absolute?

No. Both relative and absolute URLs are URLs (and URIs.)

Does the difference between URL and URI have anything to do with whether it has query parameters?

No. Both URLs with and without query parameters are URLs (and URIs.)

Does the difference between URL and URI have anything to do with whether it has a fragment identifier?

No. Both URLs with and without fragment identifiers are URLs (and URIs.)

Does the difference between URL and URI have anything to do with what characters are permitted?

No. URLs are defined to be a strict subset of URIs. If a parser allows a character in a URL but not in a URI, there is a bug in the parser. The specs go into great detail about which characters are allowed in which parts of URLs and URIs. Some characters may be allowed only in some parts of the URL, but characters alone are not a difference between URLs and URIs.

But doesn't the W3C now say that URLs and URIs are the same thing?

Yes. The W3C realized that there is a ton of confusion about this. They issued a URI clarification document that says that it is now OK to use the terms URL and URI interchangeably (to mean URI). It is no longer useful to strictly segment URIs into different types such as URL, URN, and URC.

Can a URI be both a URL and a URN?

The definition of URN is now looser than what I stated above. The latest RFC on URIs says that any URI can now be a URN (regardless of whether it starts with urn:) as long as it has "the properties of a name." That is: It is globally unique and persistent even when the resource ceases to exist or becomes unavailable. An example: The URIs used in HTML doctypes such as http://www.w3.org/TR/html4/strict.dtd. That URI would continue to name the HTML4 transitional doctype even if the page on the w3.org website were deleted.

---

Answer 4

As per RFC 3986, URIs are comprised of the following pieces:

scheme://authority/path?query

The URI describes the protocol for accessing a resource (path) or application (query) on a server (authority).

All the URLs are URIs, and all the URNs are URIs, but all the URIs are not URLs.

Please refer for more details:

Wikipedia

Answer 5

Although the terms URI and URL are strictly defined, many use the terms for other things than they are defined for.

Let’s take Apache for example. If http://example.com/foo is requested from an Apache server, you’ll have the following environment variables set:

• REDIRECT_URL: /foo
• REQUEST_URI: /foo

With mod_rewrite enabled, you will also have these variables:

• REDIRECT_SCRIPT_URL: /foo
• REDIRECT_SCRIPT_URI: http://example.com/foo
• SCRIPT_URL: /foo
• SCRIPT_URI: http://example.com/foo

This might be the reason for some of the confusion.

Answer 6

First of all get your mind out of confusion and take it simple and you will understand.

URI => Uniform Resource Identifier Identifies a complete address of resource i-e location, name or both.

URL => Uniform Resource Locator Identifies location of the resource.

URN => Uniform Resource Name Identifies the name of the resource

Example

We have address https://www.google.com/folder/page.html where,

URI(Uniform Resource Identifier) => https://www.google.com/folder/page.html

URL(Uniform Resource Locator) => https://www.google.com/

URN(Uniform Resource Name) => /folder/page.html

URI => (URL + URN) or URL only or URN only