Editing Project Xanadu (section)

== Original 17 rules ==
# Every Xanadu server is uniquely and securely identified.
# Every Xanadu server can be operated independently or in a network.
# Every user is uniquely and securely identified.
# Every user can search, [[document retrieval|retrieve]], create, and [[Computer data storage|store]] documents.
# Every document can consist of any number of parts each of which may be of any data type.
# Every document can contain links of any type including virtual copies ([[Transclusion|"transclusions"]]) to any other document in the system accessible to its owner.
# Links are visible and can be followed from all endpoints.
# Permission to link to a document is explicitly granted by the act of publication.
# Every document can contain a royalty mechanism at any desired degree of granularity to ensure payment on any portion accessed, including virtual copies ([[Transclusion|"transclusions"]]) of all or part of the document.
# Every document is uniquely and securely identified.
# Every document can have secure [[access control]]s.
# Every document can be rapidly searched, stored and retrieved without user knowledge of where it is physically stored.
# Every document is automatically moved to physical storage appropriate to its frequency of access from any given location.
# Every document is automatically stored redundantly to maintain availability even in case of a disaster.
# Every Xanadu service provider can charge their users at any rate they choose for the storage, retrieval, and publishing of documents.
# Every transaction is secure and auditable only by the parties to that transaction.
# The Xanadu client–server communication protocol is an openly published standard. Third-party software development and integration is encouraged.<ref>Xanadu FAQ: [http://xanadu.com.au/general/faq.html#2 What requirements do Xanadu systems aim to meet?], April 12, 2002 by Andrew Pam</ref>