hyperdocument

The chunk of text may be inserted into several different places in the hyperdocument.

In addition each Guide hyperdocument can contain its own context-table.

Guide extracts information from its hyperdocument and passes it, as each fault is diagnosed, to the dispatch system.

For example, a hyperdocument, like any other document, is sometimes created using cut-and-paste from other documents.

(It often does: a complete Guide hyperdocument can be enclosed in a context.)

Dr. Engelbart, the engineer, calls his idea an "open hyperdocument system."

The Symbolics manual was an 8,000 page document that was represented in a 10,000 node "hyperdocument" containing 23,000 hyperlink in all.

In our application this requirement says that each hyperdocument should include its own context-table, which contains context-specifications for all the contexts used in the hyperdocument.

Thus if an instance of a Part-number is pasted into a hyperdocument the hyperdocument's context-table is automatically augmented by a specification of Part-number.

If a reader wants to change some properties, e.g. to make fonts bigger or to exploit colour more, he can make a copy of a hyperdocument and edit the context-specifications within the context-table.

When some material is copied from one Guide hyperdocument to another, Guide checks for any instances of contexts within the material, and may as a result augment the context-table of the receiving hyperdocument.

Guide supports two ways of saving material: a structural save of the hyperdocument itself, and a what-you-see save, covering the hyperdocument as currently displayed on the screen (i.e. with the current state of button expansions).

His interest inside of McDonnell Douglas was focused on the enormous knowledge management and IT requirements involved in the lifecycle of an aerospace program, which served to strengthen Engelbart's resolve to motivate the information technology arena toward global interoperability and an open hyperdocument system.