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
Re: Pointing at things An Article by Robin Rendle www.robinrendle.com I think I’ve been darting around this question for a while now: ...I think we’ve all been taught to write in a style that forgets the reader entirely. My English degree taught me, incentivized me in fact, to write poorly with this sort of obfuscatory language, “nevertheless...”, “in this essay I will set out to...” etc. All that stuff is me pointing at me, pointing at a thing. But we should just get out of the way of the thing we’re pointing at! Pointing at things writing