I lived in San Francisco around 1992 and got to know Ted a bit, along with a few others in the Xanadu team. At Ted's houseboat in Sausalito, I witnessed a few demos of the ever-in-progress Xanadu software (and related projects), and saw some of the code.
Ted has always had very strong ideas about treating copyright as technology (see his 'transclusion,' etc.). That's why he's always been bitter about the web winning the hypertext game, without the necessary (in Ted's design) two-way linking with automatic credit (& royalties!). I can imagine Ted being vociferous (in his unique way) in opposition to a blanket release of source code via the distribution technology of the time -- largely Usenet News, FTP sites, and BBS systems. The contemporary landscape of open-source licensing had barely evolved by the early 90s; if you released something on the net, you were pretty much putting it in the public domain. That was antithetical to Ted's goals of creators owning their content.
Even if he had been convinced to release the code, it was in Smalltalk. (It had started out in C, but had been rewritten by the time I saw it.) The culture of Smalltalk never seemed to be very interested in methods of distributing source code. (Or even binary code: ST apps included their entire runtime environment, making them really heavy.) Even if the code was released, the number of people running Smalltalk systems was miniscule.
Finally, Xanadu, for most of its active life in the early 90s, was very much in experimental development. Although Ted had been thinking & designing & writing about Xanadu for decades, I believe this period was the first time he was actually able to commission running software that implemented hypertext. (Ted's not a programmer, nor an engineer.)
As for ‘publishing specs’ — most of the details of Xanadu are described in Nelson’s book _Computer Lib / Dream Machines._ Ted’s written extensively about his hypertext ideas (as this very post points out). I don’t know if Xanadu itself was ever documented, but you could read his book and probably implement most of it — if you dared!
Although Ted has always stood up for the 'regular person' computer user (that's partly what _Computer Lib_ is about), in actuality both the UI of the software, and the inherent concepts, were very weird and outside of what most people would understand. I'm not sure Xanadu would have ended up being any more influential than it already was — Berners-Lee certainly knew of Nelson's work as he was created the WWW.
(@terminalcommand: You seem to appreciate Nelson's work more than most, so please don't take the above as any sort of argument. But because you touched on the open-sourcing issue, I replied here.)
If just some of Nelson's books had seen wider distribution, that might have helped a lot. It's easy to link to Fielding's thesis, because it's online:
http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
And I actually think some of Nelson's ideas form a fine counter to Fielding's "sales pitch" for REST. REST is all about achieving high performance alongside correctness in distributed document/media systems. But as Fielding details in his introduction: there are other architectures that make more sense for what is effectively distributed computing: when you need features beyond what REST can efficiently support.
I believe Nelson had some compelling arguments for why we might want more. And if the contemporary Web is any indication, he was right. There's a place for REST-style hypertext, and there's a place for richer hypermedia.
I get as angry as the next grumpy old person when a simple Web page is turned into a single-page application for no gain and considerable pain; but I also see that there are things we need beyond simple hypertext (which we've tried to fill with: excel macros with floppies as the transport medium, java applets, active-x, flash...).
And there's the question of naming/cataloging. It's doubtful DNS is the best we can do.
That's still 15 years after Computer Lib was published so...
https://en.wikipedia.org/wiki/Berkeley_Software_Distribution
Still, Nelson have had year's to reconsider - and I'd be happy if they at least could've done some reasonably priced reprints - ebooks.
Which books are you looking for, Lulu.com has a few reprints, https://www.lulu.com/shop/search.ep?keyWords=Ted+Nelson&type...
The idea that data should consist of small addressable chunks, with each chunk having relations with other data actually makes a lot of sense.
We are thinking of data linearly, you start from byte 1 to end. Even if you copy the file or make minor changes the OS considers it another file. You make a reference to a movie, a novel etc., if you do not explicitly add the reference no one knows. Then we end up in piles and piles of data we cannot process. We have to rely on proprietary search engines, we have to rely on our browser history and our memory.
And with the latest shiniest web apps that fully render in JS we can't even get addressable future-proof links. Try to access a news page from 10 years ago, most likely the link won't work. Archive.org helps in that regard. But things could've been easier.
We have all these resources at hand, we could implement the idea of transclusion even if it is only limited to our domain. Information-heavy sites such as Wikipedia, C2-wiki etc. would greatly benefit from it.
It's true that we need a new way to look at data. It is not pen and paper anymore, we need to be able to go beyond searching. Even now, most of the world uses plain-old PDF, which is an image of a printable paper. We can use animations, videos, sound, interactivity in our content, but mostly we don't.
Ted Nelson thinks this is caused by the invention of the GUI (or PUI -Parc user interface- as he calls it) in Xerox Parc. They needed to show their managers something they could make sense of. So they created the desktop. Here is your trash-bin, here is your notepad, here are your documents (e.g Postscript/PDF). It is just like your physical desk.
But it is not your physical desk, what you have in front of you is a computer. We teach hours and hours of hand-writing to hour children, but only very few countries teach touch-typing. The old generation either doesn't understand or doesn't want kids to utilize their full potential with computers. Fortunately kids learn on their own, build their own online communities, so there is hope. Any kid that can get his/her hands on Computer Lib/Dream Machines won't be able to believe the idea that computers are only good for showing us an enhanced simulation of a work-desk.