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
Design with courage Make a bold decision (that is controversial). Make a mistake (as a result of a bold decision). Challenge “conventional wisdom”. Challenge authority (that preaches conventional wisdom). Challenge hierarchy (that perpetuates conventional wisdom). Ignore the committee (and the need to converge). Decide who your clients are (and aren’t). Ignore clients that aren’t (especially those who pay the most). Cultivate clients if none exists (instead of compromising your design). Be a generalist (and ignore your job title). Be a specialist (who specializes in being a generalist). Design things from scratch (and build them yourself from scratch). Design things that no one wants (yet). Design freely (and think freely). Chuánqí Sun, The vanishing designer The boldest decisions design