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
I am here I am here, in this work. A maker's mark is a peculiar sign. Ancient brickwork established presence through small details marking 'it': the detail itself. The great historian of bricks, Alex Clifton-Taylor, observes that what most counts about them is their small size, which just suits the human hand laying a brick. A brick wall, he says, "is therefore an aggregation of small effects. This implies a human and intimate quality not present to the same extent in stone architecture." Richard Sennett, The Craftsman Most cities were mostly built by improvisationThe joy of the humble brick details