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
Men are not an abstraction Placing work and commerce near residences, but buffering it off, in the tradition set by Garden City theory, is fully as matriarchal an arrangement as if the residences were miles away from work and from men. Men are not an abstraction. They are either around, in person, or they are not. Working places and commerce must be mingled right in with residences if men, like the men who work on or near Hudson Street, for example, are to be around city children in daily life—men who are part of normal daily life, as opposed to men who put in an occasional playground appearance while they substitute for women or imitate the occupations of women. Jane Jacobs, The Death and Life of Great American Cities 9. Scattered Work genderwork