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
Crafting repair Repair is a neglected, poorly understood, but all-important aspect of technical craftsmanship. The sociologist Douglas Harper believes that making and repairing form a single whole; he writes of those who do both that they possess the "knowledge that allows them to see beyond the elements of a technique to its overall purpose and coherence. This knowledge is the 'live intelligence, fallibly attuned to the actual circumstances' of life. It is the knowledge in which making and fixing are parts of a continuum." Put simply, it is by fixing things that we often get to understand how they work. Richard Sennett, The Craftsman Its place in the web of nature craftrepair