Definition

URN (Uniform Resource Name)

A URN (Uniform Resource Name) is an Internet resource with a name that, unlike a URL, has persistent significance - that is, the owner of the URN can expect that someone else (or a program) will always be able to find the resource. A frequent problem in using the Web is that Web content is sometimes moved to a new site or a new page on the same site. Since links are made using Uniform Resource Locators (URLs), they no longer work when content is moved.

A URN looks something like a URL. For example, here's a hypothetical URN:

 urn:def://blue_laser

where "def://" might indicate an agency or an accessible directory of all dictionaries, glossaries, and encyclopedias on the Internet and "blue laser" was the name of a term. The result of using the agency could be the "best definition," the "longest definition," or even all definitions that the agency could find of "blue laser."

A comparable URL would need to specify one specific location for a definition such as:

 http://www.whatis.com/bluelase.htm

In this case, the user has to know where the resource is located as well as how to spell the file name and suffix. With a URN, the user only needs to know the name of a resource. One or more agencies will presumably be able to locate the nearest copy of the resource and the user is freed from understanding where resources are located or relocated to.

Both URN and URL are types of a concept called the Uniform Resource Identifier (URI). A URN is associated with another concept called Uniform Resource Characteristics (URC), which allows descriptive information to be associated with a URN, such as author, date, length, and so forth.

It is possible to have a name that includes an address so, in some cases, a URN may also be a URL...but it doesn't have to be.

The URN is still being developed by members of the Internet Engineering Task Force (IETF).

This was last updated in September 2005
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: