The problem with trees Many systems are organized hierarchically. The CERNDOC documentation system is an example, as is the Unix file system, and the VMS/HELP system. A tree has the practical advantage of giving every node a unique name. However, it does not allow the system to model the real world. For example, in a hierarchical HELP system such as VMS/HELP, one often gets to a lead on a tree such as: HELP COMPILER SOURCE_FORMAT PRAGMAS DEFAULTS only to find a reference to another leaf: Please see HELP COMPILER COMMAND OPTIONS DEFAULTS PRAGMAS and it is necessary to leave the system and re-enter it. What was needed was a link from one node to another, because in this case the information was not naturally organized into a tree. Tim Berners-Lee, Seeing With Fresh Eyes A City Is Not a Tree hierarchywww
Cool URIs don't change An Essay by Tim Berners-Lee www.w3.org What makes a cool URI? A cool URI is one which does not change. What sorts of URI change? URIs don't change: people change them. The User Interface of URLs www
Paths, edges, districts, nodes, landmarks The contents of the city's images which are referable to physical forms can conveniently be classified into five types of elements: paths, edges, districts, nodes, and landmarks. Paths are the channels along which the observer customarily, occasionally, or potentially moved. Edges are the linear elements not used or considered as paths by the observer. They are the boundaries. Districts are the medium-to-large sections of the city, conceived of as having two-dimensional extent. Nodes are points, the strategic spots in a city into which an observer can enter, and which are the intensive foci to and from which they are traveling. Landmarks are another type of point-reference, but in this case the observer does not enter within them, they are external. They are usually a rather simply defined physical object: building, sign, store, or mountain. Kevin Lynch, The Image of the City City districtsAs a kind of gateway cities