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
Repair Within the larger language, it is impossible for any act not to help repair the larger whole. It is impossible for any act of building to remain an isolated act: it always becomes a portion of the flux of acts which is helping to maintain the whole. Even the laying of a brick, to mend a wall, will not only be used to mend that wall, but will be used to help repair the seat, the terrace, or the fireplace which that wall helps to form. Christopher Alexander, The Timeless Way of Building 104. Site Repair repair