News for hackers. Stuff that matters.
Re:“Xanadu Hypertext Documents” architecture and data struct... by AlbertoGP on Monday April 04, 2022 @07:48AM (#30905543)
I was asked to resubmit this new edition that I announced in HN as it got finished on 2019-04-25: https://news.ycombinator.com/item?id=19745517

The process took around a month in my spare time, and involved copy-and-pasting the OCR plain text, then marked up as DocBook XML, then converted with my own XSLT stylesheets into HTML5. There were many transcription mistakes, some from OCR from the 35 year old daisy-printer monospace printout, some were in that printout because of electrical noise in the printer serial line in 1986. I fixed those I found by hand, then a couple of readers have reported others.

Since then I’ve corrected more OCR errors, and polished a bit more the HTML rendition.

From the introduction to this edition: “It features an instance of Douglas Engelbart’s implicit links, automatically linking all appearances of certain terms to their definitions elsewhere in this document. This is done through a Javascript function that operates on the HTML content from the web server. It also shows his structural statement numbers, those little labels to the right of each paragraph that allow high resolution linking.”

Doug Engelbart was not part of Xanadu, although he was a close friend of Ted Nelson for decades. It’s just that those aspects of his NLS (of 1968 “Mother of all demos” fame) fit well this document, and work relatively well on web browsers.

I did try to implement transclusion as an example, but the target web server did not provide a CORS header and browsers refuse to load their content.

This document goes into detail about the addressing scheme for documents (https://sentido-labs.com/en/library/201904240732/Xanadu%20Hy...), the enfilade data structure (https://sentido-labs.com/en/library/201904240732/Xanadu%20Hy...), their then-future plans, etc.

Re:“Xanadu Hypertext Documents” architecture and data struct... by 0des on Monday April 04, 2022 @07:57AM (#30905606)
> “It features an instance of Douglas Engelbart’s implicit links, automatically linking all appearances of certain terms to their definitions elsewhere in this document. This is done through a Javascript function that operates on the HTML content from the web server. It also shows his structural statement numbers, those little labels to the right of each paragraph that allow high resolution linking.”

Yo this is really cool! I'm glad you came back to update us.

Re:“Xanadu Hypertext Documents” architecture and data struct... by tomcam on Monday April 04, 2022 @09:29PM (#30914232)
Wow. Thank you very much.
Re:“Xanadu Hypertext Documents” architecture and data struct... by jimmySixDOF on Monday April 04, 2022 @11:44PM (#30915088)
>did not provide a CORS header

If you only have a specific target your dealing with then maybe handle it by proxy on your own server:

[1] https://github.com/Rob--W/cors-anywhere

Re:“Xanadu Hypertext Documents” architecture and data struct... by AlbertoGP on Tuesday April 05, 2022 @01:40AM (#30915624)
You are right, and with a server-side component you could fetch arbitrary content, the endpoint could look something like example.com/transclude/a.b.com/section/page?path=2a14n which would make the server download a.b.com/section/page, extract the HTML element which is the 13th ('n') child of the 14th child of the first ('a') child of the second child of the root element, and return it.

I’m sure there are implementations of this already.

Re:“Xanadu Hypertext Documents” architecture and data struct... by jimmySixDOF on Tuesday April 05, 2022 @04:08AM (#30916455)
hummmm