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
Human-scale digital spaces An Article by Alexis Lloyd medium.com The open web is much like emergent, unplanned cities — it happens at the scale of the individual, it allows for unexpected creativity, it gives agency to anyone (well, anyone with sufficient technical knowledge) to shape their own spaces. On the other hand, the platforms that now dominate much of the web experience are more evocative of Moses’s planned cities—they often occur at the scale of the corporation, and have rigid, predictable constraints for how individuals can behave and express themselves. wwwurbanism