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
If a book can be summarized, is it worth reading? An Article by Austin Kleon austinkleon.com It is my opinion that if a book’s contents can be adequately “summed up,” so that you really don’t miss anything by reading the summary, it is not actually a book worth reading. (Of course, there’s no way to tell whether a summary is adequate or not unless you have also read the book.) Also, I suspect that the harder you find it to summarize a book you have read, the more valuable it might be. On 'The Master and His Emissary' reading