Week 4- Failed Project History

Week 4- Failed Project History
Post #2

Failed Prediction: Project Xanadu
The History

History

During his first year as a graduate student at Harvard, Nelson began implementing the system which contained the basic outline of what would become Project Xanadu: a word processor capable of storing multiple versions, and displaying the differences between these versions. Though he did not complete this implementation, a mockup of the system proved sufficient to inspire interest in others.

Nelson wanted to facilitate nonsequential writing, in which the reader could choose his or her own path through an electronic document. He built upon this idea in a paper to the ACM in 1965, calling the new idea “zippered lists”. These zippered lists would allow compound documents to be formed from pieces of other documents, a concept he named “transclusion”.

Ted Nelson published his ideas in his 1974 book “Computer Lib/Dream Machines” and the 1981 book, “Literary Machines”.
Computer Lib/Dream Machines is written in a non-sequential fashion: it is a compilation of Nelson's thoughts about computing, among other topics, in no particular order. It contains two books, printed back to back, to be flipped between. Computer Lib contains Nelson's thoughts on topics which angered him; Dream Machines discusses his hopes for the potential of computers to assist the arts.

In 1972, Cal Daniels completed the first demonstration version of the Xanadu software on a computer Nelson had rented for the purpose, though Nelson soon ran out of money. In 1974, with the advent of computer networking, Nelson refined his thoughts about Xanadu into a centralized source of information, calling it a "docuverse".
(Shades of the World Wide Web!)

In the summer of 1979, Nelson led the latest group of his followers, Roger Gregory, Mark Miller and Stuart Greene, to Swarthmore College. In a house rented by Gregory, they hashed out their ideas for Xanadu; but at the end of the summer, the group went their separate ways. Miller and Gregory created an addressing system based on transfinite numbers which they called tumblers, which allowed any part of a file to be referenced.

The 17 original rules of Xanadu:
1. Every Xanadu server is uniquely and securely identified.
2. Every Xanadu server can be operated independently or in a network.
3. Every user is uniquely and securely identified.
4. Every user can search, retrieve, create and store documents.
5. Every document can consist of any number of parts each of which may be of any data type.
6. Every document can contain links of any type including virtual copies ("transclusions") to any other document in the system accessible to its owner.
7. Links are visible and can be followed from all endpoints.
8. Permission to link to a document is explicitly granted by the act of publication.
9. Every document can contain a royalty mechanism at any desired degree of granularity to ensure payment on any portion accessed, including virtual copies ("transclusions") of all or part of the document.
10. Every document is uniquely and securely identified.
11. Every document can have secure access controls.
12. Every document can be rapidly searched, stored and retrieved without user knowledge of where it is physically stored.
13. Every document is automatically moved to physical storage appropriate to its frequency of access from any given location.
14. Every document is automatically stored redundantly to maintain availability even in case of a disaster.
15. Every Xanadu service provider can charge their users at any rate they choose for the storage, retrieval and publishing of documents.
16. Every transaction is secure and auditable only by the parties to that transaction.
17. The Xanadu client-server communication protocol is an openly published standard. Third-party software development and integration is encouraged.