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
More profitable and a better buy The bottom line is certainly of concern, both to those seeking profit and to those seeking value, but neither of these can be measured solely by the amount of dollars spent on production or product. The nonquantitative word "quality" conveys countless ways in which a more expensive thing might be more profitable and yet a better buy as well. The advantages of thicker metal in an automobile body can clearly be argued from various points of view, including resistance to denting and even simple snob appeal. Whereas the manufacturer can use these as selling points and also as justification for a higher price tag, the buyer can easily justify spending more for a car that will keep its appearance longer and provide a status symbol. Henry Petroski, The Evolution of Useful Things The aspiration for qualityThe business case for craft quality