Group:
user interface for hypertext
Topic:
choice points for a user interface
Topic:
controlled browsing of hypertext
Topic:
hypertext rhetoric
Topic:
hypertext subsets, webs, and contexts
Topic:
text trails through hypertext
Topic:
writing hypertext
| |
Summary
For presentation or print, multiple hypertext nodes can be linearized into a single document. For example, a book may be generated from its paragraphs. Hierarchies, such as books, are easy to linearize.
Linearization may be driven by links, a design, or template. Rules may select items depending on the reader's profile. (cbb 4/07)
Subtopic: conceptual document from hypertext 
| Quote: a conceptual document is a linear or hypertext document synthesized from a semantic web [»nanaJ12_1988]
| | Quote: conceptual document specifies what elements to extract, how to organize elements; how to present these elements [»nanaJ12_1988]
| | Quote: a snapped document is a linearization of a semantic net at a particular time
| | Quote: an enumerated document is a list of chunk path names; linearization produces similar documents from current contents [»nanaJ12_1988]
| | Quote: Hypertext may store the content of all contributions on some topic; with automatic ordering of concepts [»loweDG8_1985]
| | Quote: an atom is an indivisible unit of information; a choice is a string of atoms that answers a question [»shasD4_1986]
| | Quote: a guidebook is a better Hypertext application than an encyclopedia [»shasD4_1986]
|
Subtopic: linearization of hierarchy
| Quote: KMS defines a linear view of a hierarchy of frames; otherwise breadth-first view of the hierarchy [»akscRM7_1988a]
| | Quote: use keyword annotations to control format for linearizing KMS hierarchies [»akscRM7_1988a]
| | Quote: convert a structured program tree into a linear form by annotating it with symbols [»baxtCJ_1975]
| | Quote: Guide users view a single scroll with sections expanded as desired [»browPJ11_1987]
| | Quote: Guide for electronic documents; users should tailor document to their needs [»browPJ11_1987]
| | Quote: the TOPD flattener removes all hierarchical structure; then it's translated into equivalent COBOL statements [»hendP9_1975]
|
Subtopic: linearization by predicate
| Quote: a collection is a linear sequence of segments defined explicitly or by a predicate [»conkJ9_1987]
| | Quote: NetBook attempts to linearize a set of fragments chosen by properties-values and hypertext links [»graySH2_1989]
| | Quote: NLS used view filters to select information for from a hypertext database [»conkJ9_1987]
|
Subtopic: rule-based linearization
| Quote: fragment theory defines decomposition criterion, partial order, linearization by coherency and prerequisites [»shasD_1985]
| | Quote: a can-follow link if smooth transition from one fragment to another [»shasD12_1987]
| | Quote: a document card in NoteCards linearizes a start card and a set of link types with formatting options [»trigRH11_1987]
|
Subtopic: problems with linearization
| Quote: covering a set of choice units by groups information units is NP-hard [»shasD_1985]
| | Quote: optimal linearization given prerequisite links is NP-complete
| | Quote: the non-linearizability of a set of choices is length of a complete linearization divided by number of distinct information atoms [»shasD4_1986]
| | Quote: Hypertext can view multiple nodes as one big node but segmenting the node into chunks is difficult [»conkJ9_1987]
|
Related Topics
Group: user interface for hypertext (5 topics, 110 quotes)
Topic: choice points for a user interface (4 items)
Topic: controlled browsing of hypertext (16 items)
Topic: hypertext rhetoric (17 items)
Topic: hypertext subsets, webs, and contexts (12 items)
Topic: text trails through hypertext (17 items)
Topic: writing hypertext
(13 items)
|
