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
Designing detail My heart belongs to the details. I actually always found them to be more important than the big picture. Nothing works without details. They are everything, the baseline of quality. Truly functional design only comes from the most careful and intense attention to detail. Although he did not directly design all products and even had very little to do with some of them, he constantly encouraged tiny improvements that could make a good design better. This attention to detail ranged from the acuteness of angles in forms; the size, feels and distances between switches; the integration of handle fixings; the placement and nature of graphic elements on the products themselves and extended to product photography and packaging. Designing detail is about achieving a fine balance in all aspects and areas of the product, including those external to the object. Sophie Lovell & Dieter Rams, Dieter Rams: As Little Design as Possible The details of construction details