Difference between revisions of "URL"
From MgmtWiki
(→External Sources) |
(→Full Title or Meme) |
||
| Line 1: | Line 1: | ||
==Full Title or Meme== | ==Full Title or Meme== | ||
| − | The Universal Resource Locator was created as a human-readable name to allow look-up of the actual address of a network attached computer. | + | The Universal Resource Locator was created as a human-readable name to allow look-up of the actual address of a network attached computer in a [[Domain Name System]] which was a single rooted directory. |
==Context== | ==Context== | ||
Revision as of 08:29, 21 July 2019
Full Title or Meme
The Universal Resource Locator was created as a human-readable name to allow look-up of the actual address of a network attached computer in a Domain Name System which was a single rooted directory.
Context
- What was actually defined was a hodge-podge of information that no normal human could every understand. It now includes:
- A schema, which most people call a protocol. For a web site this will be HTTP: or, better yet, for secure sites HTTPS:
- The host name which can be a long string of uncertain meaning; not just IBM.COM but also:
- TK
- The port number which can be used to extend the number of Endpoints that one computer can host. for the web defaults are: 80 or 443.
- A "fragment" which is can be a query or a pointer to a document.
- Originally all URLs were written in ASCII characters. As might be expected some countries want different character sets to correspond to their local language.
Problem
It has been recognized for many years that URLs are poor substitutes for Web Site Identifiers[1]. Yet no one has found a such a substitute.
Solution
A good solution is still being sought; here are some ideas:
- Brand Names
References
- ↑ Jakob Nielsen, URL as UI https://www.nngroup.com/articles/url-as-ui/
External Sources
- Living URL The URL Standard defines URLs, domains, IP addresses, the application/x-www-form-urlencoded format, and their API.
