| 
|
Topic: hierarchical structures in hypertext
topics >
computer science >
hypertext as unstructured information
Topic:
hypertext links
Topic:
cross reference and hierarchical links in hypertext
Topic:
schemas for hypertext
Topic:
hierarchical structures
Topic:
outlines
Topic:
using keywords to search hypertext
Summary
Hypertext is frequently organized as a hierarchy. A tree structure helps organize information. The path from root to node is easily displayed, providing context to the current page. The top-levels of the hierarchy may provide an index into the lower levels. (cbb 4/07)
Subtopic: hierarchy in KMS
Quote: Hypertext should have a strong preference for tree structures [»mccrDL10_1984] Quote: a node of a Hypertext hierarchy can be a frame or another Hypertext [»stotPD12_1988] Quote: all Hypertext systems should support hierarchies of inclusion relations; these should be distinct from reference links [»halaFG7_1988]
Subtopic: process a hierarchy of frames
Quote: most KMS databases are strongly hierarchical [»akscRM7_1988a] Quote: top levels of the KMS hierarchy is an index; lower levels represent documents and task-related groups of information [»akscRM7_1988a] Quote: the 'skeleton' for a KMS database is a multi-level hierarchy [»akscRM7_1988a]
Subtopic: hierarchy in NoteCards
Quote: with hierarchical organization; users want to operate on subtrees [»akscRM5_1984] Quote: KMS programs often process a hierarchy of frames; e.g., a document is generated from a hierarchy [»akscRM7_1988a] Quote: build a subtree for processing as a unit; semantically richer than query qualification [»akscRM5_1984]
Subtopic: other examples
Quote: a NoteCards filebox provides hierarchical categorization for storing and retrieving notecards [»halaFG7_1988] Quote: some writers have abandoned NoteCards in favor of outline processors since fileboxes can not be expanded or collapsed [»halaFG7_1988] Quote: experienced NoteCards users put all notes in one filebox and use a sketch card to form related piles; when stable, turned into fileboxes [»halaFG7_1988]
Quote: an IGD leaf node is a graphical page; while internal nodes are chapters [»feinS3_1988] Quote: IGD documents are directed graphs of pages organized into arbitrarily nested chapters [»feinS1_1982] Quote: a TEXTNET node is a chunk (primitive piece of text) or a tocs (entry in a table of contents) [»trigRH1_1986] Quote: Compendium entries are hierarchically categorized with both explicit and implicit cross-references [»glusRJ5_1989] Quote: SuperBook provides full text indexing and a fisheye table of contents [»eganDE5_1989] Quote: composite node aggregates related nodes and links; can be collapsed into an icon [»conkJ9_1987] Quote: Answer Garden uses a branching network of diagnostic questions written by experts; the leaves are questions that people have asked
[»ackeMS_1990]
Topic: hypertext as unstructured information (4 items)
Topic: hypertext links (45 items)
Topic: cross reference and hierarchical links in hypertext (9 items)
Topic: schemas for hypertext (7 items)
Topic: hierarchical structures (46 items)
Topic: outlines (16 items)
Topic: using keywords to search hypertext
(26 items)