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
We want you to work with an artist Normally after the design was built, you would find places for the art to be located and then you would go out and select the artist that you wanted. That is historically, the traditional way to go. But this time, someone else was calling the shots. A planning official, basically, who comes along and says, “We want you guys to work with an artist.” And the architects are like, “Sure of course.” But then the official goes—“No, you don’t quite understand. We want you to use an artist as a co-equal member of the design team.” That is, the artists are going to have just as much control as the architects. It was really unheard of. Some Other Sign that People Do Not Totally Regret Life 99percentinvisible.org It passes by the river artcollaboration