Topic: archives
Topic: hypertext as external memory
Topic: managing changes in hypertext
Topic: managing a Thesa database
Topic: searching the Web
Topic: version control
| |
Summary
If hypertext always changes, how is information captured and preserved? A snapshot may freeze a hierarchy at a moment in time. Every edit may be preserved. A command may mark a frame for preservation (cbb 4/07)
Subtopic: frozen hierarchy
Quote: KMS can freeze a hierarchy of frames; whenever a frozen frame is modified, the original version is saved [»akscRM7_1988a]
| Subtopic: automatic version history
Quote: HAM can maintain a version history for an object that gets updated on each modification [»campB7_1988]
| Quote: whenever an archived node in HAM is updated, a new version is created [»campB7_1988]
| Subtopic: 'old' button to save copies
Quote: ZOG users follow informal rules for when to save an old copy of the frame
| Quote: the 'old' button in ZOG saves a copy of the current frame on a stack attached to the frame [»akscRM5_1984]
| Subtopic: problems with versioning
Quote: versioning is helpful for Hypertext but a branched version history causes difficulty for links [»halaFG7_1988]
|
Related Topics
Topic: archives (19 items)
Topic: hypertext as external memory (24 items)
Topic: managing changes in hypertext (21 items)
Topic: managing a Thesa database (34 items)
Topic: searching the Web (53 items)
Topic: version control (34 items)
|