DEV Community

Anh Trần Tuấn
Anh Trần Tuấn

Posted on • Originally published at tuanh.net on

Secrets of URIs, URLs, and URNs: Understanding Their Differences and Uses

1. Understanding the Fundamentals of URIs, URLs, and URNs

Image

The internet's ability to access resources globally hinges on a standardized system to identify and locate these resources. The concepts of URIs, URLs, and URNs fall under this umbrella.

1.1 What is a URI?

A Uniform Resource Identifier (URI) is a string that identifies a resource on the internet. Think of it as an identifier for anything that can be named, from a webpage to an API endpoint, or even a physical book in a digital library.

General Form : scheme:[//authority]path[?query][#fragment]

For example:

https://www.example.com/page?query=example#section1
Enter fullscreen mode Exit fullscreen mode

1.2 What is a URL?

A Uniform Resource Locator (URL) is a subset of a URI. A URL not only identifies a resource but also provides a means to retrieve it by specifying its location. In simpler terms, a URL includes the protocol used (like HTTP, HTTPS, FTP) to access the resource.

General Form : scheme://domain:port/path?query_string#fragment_id

For example:

https://www.example.com/index.html?search=query#results
Enter fullscreen mode Exit fullscreen mode

1.3 What is a URN?

A Uniform Resource Name (URN) is another subset of a URI that names a resource without implying its location or how to access it. URNs serve as persistent, location-independent resource identifiers.

General Form : urn:
:

For example:

urn:isbn:978-0132350884
Enter fullscreen mode Exit fullscreen mode

2. Differences Between URI, URL, and URN

Although URI, URL, and URN are closely related, understanding their subtle differences is key to mastering web development concepts.

2.1 URI vs. URL

Image

A URL is always a URI, but a URI is not always a URL. While both serve to identify resources, URLs also include the protocol and path to access them.

2.2 URI vs. URN

Image

A URN is a URI, but it is specifically designed for naming. URNs don’t include the protocol to access a resource, which makes them different from URLs.

2.3 URL vs. URN

A URL provides a way to access a resource, while a URN provides a way to name it. Understanding when to use a URL or URN is important when designing systems that require resource identification and retrieval.

3. Real-World Applications of URIs, URLs, and URNs

URI Applications : URIs are essential in web APIs. For instance, RESTful APIs use URIs to identify resources.

URL Applications: URLs are widely used in web browsers to navigate websites, download resources, and more.

URN Applications: URNs are often used in namespaces, such as in XML documents, to ensure unique naming.

4. Conclusion

Image

Understanding the differences between URIs, URLs, and URNs is fundamental for anyone working with web technologies. Each has its specific use case and application, making them vital tools in web development and beyond. By grasping these differences, you can make more informed decisions when designing and implementing web systems.

If you have any questions or need further clarification on any point, feel free to comment below!

Read posts more at : Secrets of URIs, URLs, and URNs: Understanding Their Differences and Uses

AWS Q Developer image

Your AI Code Assistant

Automate your code reviews. Catch bugs before your coworkers. Fix security issues in your code. Built to handle large projects, Amazon Q Developer works alongside you from idea to production code.

Get started free in your IDE

Top comments (0)

AWS Q Developer image

Your AI Code Assistant

Generate and update README files, create data-flow diagrams, and keep your project fully documented. Built to handle large projects, Amazon Q Developer works alongside you from idea to production code.

Get started free in your IDE

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay