The Internet: Classification Changes for the World Wide Web

Article excerpt

The workings and structure of the World Wide Web often seem an arcane subject only explored by the curious. But like the corporate records classification schemes that records managers deal with every day, the Web is now forced by growth and other needs to look at expanding its classification scheme to accommodate the increasing volume of web sites. This article delves into some proposed changes being discussed by Internet Service Providers and the legal profession. One grave concern is that the Web may be headed down a narrow road of classification changes. The Web may be solving some of its current problems, but unfortunately it may not be taking into consideration the global nature of its structure and its long-term needs. Our global information system may need some records management assistance.

In the next year or so there will be some interesting changes to the naming conventions in use on the World Wide Web (WWW or Web). Faced with conflicts and court challenges about duplicate names, the InterNIC or registering body is considering a proposal that will result in the first major expansion of address conventions in the 30-year history of the Internet. Addresses for the Web may soon have new endings or top-level domains (TLDs) such as .firm and .store.

Accordingly, there will be a bit of a learning curve. There may be websites rushing to re-register or be renamed and subsequently bookmarks will need to be changed around the world. Search engines may need to be modified to conduct more efficient hierarchical searches. There most certainly will be trademark and intellectual property issues.

From a records management perspective, I am curious as to how this latest proposal came into being. There was obviously much discussion and legal consultation. But who did the research into the type and intent of web-sites that resulted in the hierarchy now being considered? Who did the inventory and analysis, if you will? How many certified records managers or even records managers have been consulted as to the proposals now presumably before the Internet organizing bodies?

Is there enough room in the new structure? Is it intuitive? Are we solving a naming issue, a legal issue, or a capacity issue?

Let us look at the ever-changing organizational structure that manages the Internet.

At the top of the current hierarchy (see Figure 1) is a loose relationship between the Internet Architecture Board (IAB), the Internet Engineering Task Force (IETFworking on improvements to the Internet connection technologies) and the Internet Engineering Steering Group (IESG). These three bodies are under the auspices of the Internet Society (ISOC), which manages Internet standards, Internet architecture, harmonization of international work on Internet growth and development, collection of Internet information, and liaison work with other organizations.

With the rapid growth of the World Wide Web, there is also now a group known as W3C-the World Wide Web Consortium that is dedicated to the management of the Web and related activities.

There are several other prominent Internet organizations, such as the InterNIC, the body that administers the assignment and registration of Internet addresses and the Internet Assigned Numbers Authority (IANA)-controlling the various numbering schemes used throughout the Internet.

The IANA and W3C are studying the naming system in use throughout the World Wide Web, the Domain Name System. The Domain Name System was designed to help in locating machines on the Internet. It is actually a complex distributed database containing information about domains and host computers. But getting into a discussion of the domains, it is useful to review the WWW's physical structure.


The Web is a constantly changing construct but the included simplistic diagram shown in Figure 2 may help in our perception of the needs for uniform names, interconnected registries and rules. …


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.