URI URL URN Relationship

Let's take a look at the fictional example below. This is a URI:

• Http://bitpoetry.io/posts/hello.html#intro

We begin to analyze

• /HTTP

is a way to define how resources are accessed. Other than that

• Bitpoetry.io/posts/hello.html

is where the resources are stored, so in this case,

• #intro

is a resource.

A URL is a subset of the URI that tells us how to access the network location. In our example, the URL should look like this:

• Http://bitpoetry.io/posts/hello.html

A URN is a subset of URIs, including the name (within a given namespace), but does not include access, as follows:

• Bitpoetry.io/posts/hello.html#intro

That's it. Now you should be able to tell the difference between a URL and a urn.

If you forget the content of this article, at least one thing to remember: URIs can be divided into URLs, urns, or combinations of both. If you have been using the term URI , there is no mistake.

URI URL URN Relationship