Index
A
'A Life Set for Two',
hypertext poetry, dynamics of; Kendall(8)-74
AAA (Author's Argumentation Assistant),
ECHT'90 paper; Schuler(151)-137
ABC (Artifact-Based Collaboration) system,
DGS (Distributed Graph Storage) component, Hypertext '93 paper; Shackelford(224)-1
Hypertext '91 paper; Smith(180)-179
abstractions,
See Also models; representation; semantic(s);
abstract attributes, attaching to concepts through node and link types; Nanard(191)-333
abstract containers in Trellis, DSS shell architecture with a dynamic hypertext interface formatting templates analogous to; Bieber(182)-207
abstract content, DSS shell architecture with a dynamic hypertext interface handling of; Bieber(182)-207
abstract hypertext models, characteristics needed to support set-based hypertext; Parunak(184)-240
abstract knowledge structure, developing with hypertext; Marshall(103)-254
Abstraction Mechanisms model, Hypertext'87 paper; Garg(110)-375
ADV,
OOHDM use to describe the user interface of a hypermedia application; Schwabe(12)-123
specifying the behavior of user interface objects with; Schwabe(12)-123
advantages of a design model for comparing hypertexts at a high level of; Garzotto(190)-315
as equivalent of Halasz' composition; Botafogo(172)-64
classes, in Extended Dexter model; Gronbaek(15)-151
contiguity relations easier to learn than; Oren(105)-300
data,
extensibility of, as hypermedia platform dimension; Wiil(14)-141
types, HOSS support of; Nuernberg(19)-199
data types; Perlman(308)-260
descriptions in NoteCards, IDE as an example; Marshall(103)-267
encouragement of, by rubber sheet layouts; Kaltenbach(174)-101
formal hypertext theory, extenstions to Garg's work, ECHT '90 paper; Afrati(145)-54
functions, HyPursuit; Weiss(18)-180
high-level, as advantage of object-oriented data modeling approaches; Schwabe(12)-126
hypermedia,
data model, semantic relationships in; Bapat(20)-207
model, defining; Bapat(20)-209
model, tailoring; Bapat(20)-209
in hypermedia applications, HOT (Hypermedia Object-oriented Toolkit); Puttress(143)-29
in OOHDM, interface models; Schwabe(12)-123
levels of, simultaneously displaying information at different; Noik(240)-192
mechanism, for expressing semantics, MacWeb facilities; Nanard(191)-334
mechanisms, aggregation; Schwabe(12)-123
mechanisms for, value for hypertext; Garg(110)-375
multiple levels of, provided by Flag taxonomy; Osterbye(13)-129
node, key characteristic of Thoth-II; Collier(104)-273
selecting proper level of, for multimedia navigation and interface design; Schwabe(12)-116
storage format; Perlman(308)-260
structural,
advantages of; Nuernberg(19)-196
entity, See associations;
taxonomy; Nuernberg(19)-200
term definition; Botafogo(172)-63
in mathematics of formal hypertext model; Afrati(145)-62
access,
See Also information, retrieval; navigation; security;
accessor function,
Dexter constraints; Halasz(299)-35
Dexter definition; Halasz(299)-32
collaborative; Lawton(233)-106
control,
application-specific requirements; Bapat(20)-206
HyperDisco support of; Wiil(14)-141
hypermedia operating system advantages for; Nuernberg(19)-196
KMS approach to; Akscyn(86)-18
limitations of current systems; Bapat(20)-206
See also locking;
See Also systems issues;
from multiple platforms, in DeVise Hypermedia system; Gronbaek(226)-25
mechanisms,
hyperindices; Bruza(149)-109
navigational; Halasz(108)-353
query-based; Halasz(108)-353
multi-user, HyperBase (GMD-IPSI) and CHS as providers of; Bapat(20)-204
paths, multiple; Conklin(102)-249
protection, graph-based data model approaches; Shackelford(224)-1
structures, semantics of, in OOHDM design process; Schwabe(12)-121
to and from system tools,
in Document Examiner; Walker(106)-320
interfacing System Factory tools with DIF; Garg(112)-416
issue in using NoteCards; Trigg(93)-95
access control list (ACL),
HAM data security facility; Campbell(87)-24
access controls,
as industrial hypertext requirement; Malcolm(168)-19
handling through timing alterations, in Trellis; Stotts(183)-227
hypermedia requirement in a concurrent engineering environment; Malcolm(168)-14
importance in a large industrial environment; Malcolm(168)-18
importance in education environment; Ess(187)-278
ACE (Aggregation Clustering with Exceptions),
Hypertext '91 paper; Hara(173)-75
acquariums,
See Also applications;
as Himotoki application; Hirata(2)-19
acquisition phase,
knowledge representation, using hypertext for; Marshall(103)-254
actemes,
See Also classification, theory; composites; dynamic; episode; links; scenes; structure(s);
characteristics and relationship to hypertext structure; Rosenberg(3)-22
as low-level unit of hypertextual activity; Rosenberg(3)-22
actions,
encoding in,
I-SHYS; Garg(112)-423
software hypertext environment; Garg(112)-410
activation,
spreading, in FIRST concept network specification; Lucarella(147)-85
active,
See Also time;
hypertext, concept description; Garg(112)-410
text,
adaptive documentation use of; Kaindl(192)-354
implemented with message passing in frame-based hypertext; Kaindl(192)-349
importance in maintaining up-to-date documentation; Kaindl(192)-354
values, use in KEE frame-based hypertext; Kaindl(192)-347
views, synthesizing specific, value for scientific research; Nanard(191)-332
activity(s),
See Also behavior; dynamic;
hypertext, structure of; Rosenberg(3)-22
spaces, SEPIA term definition; Thuring(179)-163
tracking, HyTime support of; Buford(11)-111
acyclic connected graphs,
as ABC subgraph type; Smith(180)-184
adaptation,
to user skill level and task, in a DSS shell architecture with a dynamic hypertext interface; Bieber(182)-207
Trellis term definition; Stotts(183)-220
adaptive hypertext,
agents, associated with links, Trellis use of; Stotts(183)-223
documentation,
active text use for, frame-based hypertext; Kaindl(192)-354
browsing system in CID; Boy(171)-54
events, term definition; Stotts(183)-221
Trellis timing mechanism use for hypertext; Stotts(183)-219
adaptive indexing,
using in online books; Remde(98)-177
addressing scheme,
Xanadu; Nelson(85)-0
administrative documents,
as artifact component; Smith(180)-179
ADT (abstract data types),
HOSS support of; Nuernberg(19)-199
ADV (Abstract Data View),
Charts, specifying the behavior of user interface objects with; Schwabe(12)-123
IWHD '95 paper; Rossi(70)-131
OOHDM use to describe the user interface of a hypermedia application.; Schwabe(12)-123
aesthetics,
See Also design; Kendall; Moulthrop; people, Rosenberg; people, Tolva; rhetoric;
design, HyperCafe; Sawhney(1)-2
structures, in hypervideo; Sawhney(1)-1
affinity,
between nodes, identifying in CYBERMAP; Gloor(175)-111
'afternoon, a story',
See Also fiction; literature; rhetoric;
historical, literary, and social significance; Moulthrop(133)-259
HyperCafe relationship to; Sawhney(1)-5
hypertext publication, link plot analysis of; Bernstein(28)-248
Agenda,
agents, characteristics, compared with Lynx; Bernstein(28)-253
agenda-keeper,
potential user interface feature for hypertext; Frisse(91)-67
'Agent Stories',
See Also enactment; hypertext with characters; narratives;
as example of multi-character impact on video; Sawhney(1)-8
HyperCafe relationship to; Sawhney(1)-2
agents,
See Also artificial intelligence (AI); dynamic;
adaptation, associated with links, Trellis use of; Stotts(183)-223
categories of agents in I-SHYS; Garg(112)-418
in Agenda, characteristics, compared with Lynx; Bernstein(28)-253
in Lynx, pattern recognition; Bernstein(28)-253
in ObjectLens, characteristics, compared with Lynx; Bernstein(28)-253
information, user-created link profile used by the HieNet; Wiil(225)-145
lexical, link apprentices compared with in literature analysis; Bernstein(28)-254
model, in hypertext systems; Oren(105)-302
relationship of tasks to agents in I-SHYS; Garg(112)-423
role in the I-SHYS software environment; Garg(112)-418
similarity-based, literature analysis use of; Bernstein(28)-253
aggregation,
See Also composites; links; relationship; sets;
ABC subgraphs use for; Smith(180)-184
as abstraction mechanism, in OOHDM; Schwabe(12)-123
ACE (Aggregation Clustering with Exceptions); Hara(173)-75
annotation sets in Knowledge Weasel; Lawton(233)-106
as an abstraction type; Botafogo(172)-64
as only composition type referred by Halasz; Botafogo(172)-64
as class of link types; Allan(5)-43
concept classes; Schwabe(12)-120
contextual link clustering in CID; Boy(171)-55
contrasted with generalizations in Garg's abstract hypertext model; Garg(110)-383
database, use of concept in hypertext; Garg(110)-376
developing for semantic clusters in hypertexts; Botafogo(172)-66
entities; Garzotto(190)-313
frame-based hypertext templates, use in filtering structures; Kaindl(192)-352
hierarchical, limitations for taxonomic reasoning; Parunak(184)-236
HYPERDRAWER characteristics, as CYBERMAP aggregate; Gloor(175)-109
as hypertext abstraction, mathematical model; Garg(110)-382
identification, Hypertext'91 paper; Botafogo(172)-63
identifying in hypertext structures; Botafogo(172)-63
implementing hypertext database relationships through exceptions and; Hara(173)-75
in Garg's abstract hypertext model, See Also;
in graphical browsers, importance for large information spaces; Hara(173)-77
Kiosk structure nodes use for both user access and understanding; Creech(169)-29
links; Allan(5)-42
modeling with sets, contrasted with set-based hypermedia for taxonomic reasoning; Parunak(184)-234
relations, in Extended Dexter model; Gronbaek(15)-151
sequence objects with special constraints; Garg(110)-382
set theoretic treatment of; Garg(110)-382
spatial hypertext, term definition; Marshall(242)-217
techniques, application to organizational links; Hara(173)-76
term definition; Botafogo(172)-63
in mathematics of formal hypertext model; Afrati(145)-62
AI (artificial intelligence),
differences between hypertext and AI; Oren(105)-292
EUCLID as an AI-based system for argumentation and reasoning; Smolensky(101)-233
hypermedia synergy with; Kaltenbach(174)-101
hypertext integration with expert systems, in a maintenance support application; Hayes(121)-119
hypertext value for knowledge acquisition; Kaindl(192)-346
integration of hypertext systems into; Frisse(91)-63
knowledge structuring formalisms, contrasted with text structuring of hypertext; Kaindl(192)-345
knowledge-based systems, LogicWeb compared with; Loke(23)-240
modeling the semantics of text units with knowledge-based techniques; Hammwohner(97)-161
plans as automatic linking mechanism used in ASK systems, analysis of results; Cleary(4)-34
representation framework, issues and open questions; Cleary(4)-31
rule-based knowledge, not the only kind of knowledge representable in hypertexts; Nanard(191)-330
Searle's Chinese room debate and the EUCLID system; Smolensky(101)-219
semantic modeling with; Hammwohner(97)-155
algebra,
techniques from, compared with EUCLID reason-support system; Smolensky(101)-232
algorithms,
See Also classification, methodology; formalisms; models; system(s);
clustering; Weiss(18)-181
developing for decomposition diagrams with ABC tools; Smith(180)-188
generation, overview maps in CYBERMAP requirements; Gloor(175)-113
graph theory, identifying aggregates in hypertext structures with; Botafogo(172)-63
greedy, potential as ACE implementation algorithm; Hara(173)-88
incremental, current Trellis research; Stotts(183)-229
Kernighan-Lin graph partition, generating aggregations and exceptions with; Hara(173)-75
Kernighan-Lin graph partition algorithm, ACE use of; Hara(173)-84
media-based navigation; Hirata(237)-159
Miyabi, Himotoki image navigation use of; Hirata(2)-18
pre-fetching, HOSS development plans; Nuernberg(19)-201
suffix-stripping, hypertext information retrieval use of; Frisse(91)-61
aliasing,
unlimited, characteristics of; Remde(98)-177
user-defined index terms, SuperBook capability; Remde(98)-178
AllAttributes function,
Dexter definition; Halasz(299)-36
alliteration,
patterns of, exploration with dot plots; Bernstein(28)-254
allusion,
exploration with dot plots; Bernstein(28)-254
ambiguity,
See Also Joyce; Landow; Moulthrop; narratives; rhetoric;
need to manage, as motivation for Intermedia use in teaching humanities; Ess(187)-280
representation with time-varying content; Kendall(8)-78
representing with spatial hypertext; Marshall(242)-217
Amsterdam Hypermedia Model (AHM),
See Also dynamic; models; multimedia; open hypermedia systems (OHS); time;
adding time and context to the Dexter model; Halasz(296)-50
context notion, Extended Dexter model representation; Gronbaek(15)-156
HyperCafe relationship to; Sawhney(1)-5
Hypertext '93 paper; Hardman(39)-183
HyTime relationship to with respect to time; Buford(11)-109
analogies,
makers of, as automated linking method in HieNet; Cleary(4)-33
analogous transformations,
finding for chemical reactions, comparison of printed, hypertext, and full-text retrieval for; Egan(189)-299
analogy makers,
See Also automated link; information, retrieval; mental models;
analysis phase,
knowledge representation, using hypertext for; Marshall(103)-254
analytical,
tools, importance for assessing hypertext quality; Botafogo(172)-64
anchors,
See Also classification, basic concepts; component(s); context; Dexter; links; structure(s);
ABC approach to; Smith(180)-179
anchor extensions as properties of nodes not links, , implications of for data model consistency; Smith(180)-190
as industrial hypertext requirement; Malcolm(168)-19
characteristics and use in an industrial hypermedia environment; Malcolm(168)-20
computation of, as hypermedia platform category; Wiil(14)-141
Dexter,
definition; Halasz(299)-32, Halasz(299)-34
purpose of; Gronbaek(15)-149
dynamic,
HyTime HyQ query language use to form; Buford(11)-110
permitted by HyTime standard; Buford(11)-108
in Extended Dexter model, characteristics and attributes; Gronbaek(15)-153
factual knowledge represented by; Nanard(228)-51
as glue between structure and contents; Osterbye(13)-130
HDM approach to; Garzotto(190)-313
HyTime location address forms correspondance to; Buford(11)-108
id, in Dexter,
definition; Halasz(299)-34
replaced by CompLocSpec class in Extended Dexter model; Gronbaek(15)-152
in data representations maintained by arbitrary applications, , ABC approach to the problem of; Smith(180)-190
in nested context model, term definition; Casanova(181)-195
location ladders as generalization of in HyTime; Buford(11)-108
LocationSpecifier use in; Gronbaek(15)-151
MacWeb,
logical definition contrast with geometric definition in HyperCard; Nanard(191)-335
management of in; Nanard(191)-335
management system similarity with Intermedia logical binding; Nanard(191)-335
mapping between link markers and, Dexter compared with Flag taxonomy; Osterbye(13)-130
marked vs. unmarked, characteristics and use; Gronbaek(15)-153
Non-Intrusive, Individual Colour Markings and; Irler(161)-261
pSpec as attribute of; Gronbaek(15)-153
reference to composites, permitted by HyTime standard; Buford(11)-108
refSpec role in Extended Dexter model; Gronbaek(15)-153
represented by link markers in the Dexter hypertext model; Osterbye(13)-130
representing rich semantic relationships with, in MacWeb; Nanard(228)-51
rules for determining anchor points, in The Dickens Web design; Catlin(178)-151
text anchors, importance for software reuse environment; Creech(169)-27
transient,
as type of anchor, in Extended Dexter model; Gronbaek(15)-153
refSpec for, in Extended Dexter model; Gronbaek(15)-152
typing,
encoding the complex semantics by; Nanard(228)-51
to provide additional context, in MacWeb; Nanard(228)-51
value, in Dexter,
definition; Halasz(299)-34
replaced by LocSpec class in Extended Dexter model; Gronbaek(15)-152
And/Or graph,
semantic representation of engineering norms with; Schwabe(150)-123
Andrew Toolkit (ATK),
Aquanet built on; Marshall(186)-271
ECHT '90 paper; Sherman(142)-13
anecdotal information,
set-based hypertext value for study of; Parunak(184)-238
use in formulating questions and validating answers; Lai(176)-124
animations,
See Also HyperCafe; time; video;
ABC tools for building graph structured message flow diagrams potential for creating; Smith(180)-189
integration into hypermedia environment, as industrial hypertext requirement; Malcolm(168)-19
mathematical proofs, rubber sheet layout use for; Kaltenbach(174)-100
of information units; Kaltenbach(174)-101
rubber sheet layout use for; Kaltenbach(174)-91
tool, as HOSS application; Nuernberg(19)-200
using in customer maintenance training hypermedia projects at Boeing; Malcolm(168)-15
value of electronic documentation; Oren(105)-295
Annenberg/CPB project,
support for Intermedia; Beeman(92)-71
annotation(s),
See Also collaboration; structure(s);
about workproducts, Kiosk use in structured software reuse library selection; Creech(169)-33
adding to notefiles in NoteCards; Trigg(93)-102
Aquanet support of; Marshall(186)-272
capabilities, in DIF; Garg(112)-415
classification; Lawton(233)-106
collaborative, managing with Knowledge Weasel; Lawton(233)-106
collections of, as aggregates in Knowledge Weasel; Lawton(233)-106
education environment use, Intermedia management of; Ess(187)-278
format, InterNoteÕs "layers of acetate'' metaphor influence on Knowledge Weasel; Lawton(233)-106
importance in a shared industrial environment; Malcolm(168)-18
in collaborative engineering handbooks, DeVise Hypermedia system as a Dexter-compliant cooperative architecture; Gronbaek(226)-25
InterNote as Intermedia tool that supports, InterNote as Intermedia tool that supports; Catlin(139)-365
Kiosk's facility, importance for software reuse library users; Creech(169)-33
links; Allan(5)-42
facilitation by Dexter definition (note); Halasz(299)-24
managing permission for, in a hypermedia operating system; Nuernberg(19)-196
marginal, paper document value; Walker(106)-313
non-textual media; Lawton(233)-106
not supported by,
Document Examiner; Walker(106)-320
Hyperties; Shneiderman(99)-193
potential user interface feature for hypertext; Frisse(91)-67
private, importance in an industrial hypermedia environment; Malcolm(168)-20
source documents, design goal of Notes (CMU); Neuwirth(95)-125, Neuwirth(95)-126
supported by,
DIF; Garg(112)-411
gIBIS; Conklin(102)-250
Notes; Neuwirth(95)-125
SuperBook; Remde(98)-178
value for software reuse libraries; Creech(169)-27
virtue of paper documentation; Oren(105)-294
antitrust,
potential issues for hypertext developers; Jones, III, Esq.(109)-372
any-dcn data entity attribute,
as data content notation in HyTime; Buford(11)-111
API (application programming interface),
See Also layers; models; open hypermedia systems (OHS); operating systems, hypermedia; system(s);
HOSS; Nuernberg(19)-200
HyTime, not defined in the standard; Buford(11)-113
APL (A Programming Language),
Hyperties first implementation language; Shneiderman(99)-191
application(s),
See Also open hypermedia systems (OHS); research;
ABC,
differentiated from browsers; Smith(180)-186
open architecture support for external; Smith(180)-189
support of standard; Smith(180)-182
academic research, Perseus project; Crane(90)-51
acquarium information systems; Hirata(2)-19
aerospace, CID use with; Boy(171)-51
altering source code, ABC approach to the problem of; Smith(180)-190
application program interface (API), defined by presentation and navigation submodels of the nested context model; Casanova(181)-193
application-independent hypertext, comparison with database and user interface management systems; Bieber(182)-206
architecture; Fischer(120)-105
argumentation, EUCLID; Smolensky(101)-215
art,
museums; Hirata(2)-19
Portinari Project; Schwabe(12)-116
art museums, Perseus project; Mylonas(310)-270
auditing; De Young(126)-169
automobile repair manual; Collier(104)-284
biological,
modeling, computational hypertext use for; Schnase(127)-181
research; Schnase(127)-181
CAD,
dynamic hypertext interface as a front end for; Bieber(182)-211
HAM support of hypertext-based; Bapat(20)-204
hypertext-based, HAM support of; Bapat(20)-204
integrating hypertext with; Nanard(191)-330
integrating into a total information environment; Malcolm(168)-15
CAD applications,
dynamic hypertext interface as a front end for; Bieber(182)-211
integrating hypertext with; Nanard(191)-330
integrating into a total information environment; Malcolm(168)-15
CASE,
environment; Bigelow(111)-397
HAM support of hypertext-based; Bapat(20)-204
CASE (computer-aided software engineering), DynamicDesign; Bigelow(111)-397
chemical research, comparison of printed, hypertext, and full-text retrieval on representative chemistry research information tasks; Egan(189)-299
classes,
application semantics implemented as within HyperStorM; Bapat(20)-203
as instances of semantic metaclasses; Bapat(20)-207
modeling semantic relationships among; Bapat(20)-207
classics research, Perseus project; Crane(90)-51
cognitive science, Intermedia; Beeman(92)-67
complex domains, hypertext design issues; Garzotto(190)-314
conferencing, HOT (Hypermedia Object-oriented Toolkit) use for; Puttress(143)-32
constraint mechanism for tailoring HyperStorM to application-specific needs; Bapat(20)-208
dependencies, separation in nested context model; Casanova(181)-194
design,
hypermedia system design models distinguished from; Gronbaek(15)-150
OOHDM use in; Schwabe(12)-116
development,
advantages of database implementator of storage and application layers for; Bapat(20)-204
data model semantic gap issues and problems; Bapat(20)-205
hypermedia support requirements; Bapat(20)-203
development environments,
Andrew Toolkit facilities; Sherman(142)-13
collaboration issues and solutions, graph-based data model approaches; Shackelford(224)-1
domain, characteristics in the HDM; Garzotto(190)-315
dynamic link-resolving; Tompa(234)-118
education,
Intermedia; Beeman(92)-67
knowledge representation and learning processes in the Design ofEducational Hypermedia; De Vries(60)-1
medicine, Intermedia use for; Beeman(92)-67
educational, VideoBook use for; Ogawa(144)-38
as entities that serve specialized hypermedia abstractions to people; Nuernberg(300)-1
external, invocation handling by HyperStorM; Bapat(20)-210
generators, hypertext design models compared with; Garzotto(190)-315
historical research, hypertext structure needs; DeRose(132)-249
HOSS facilities that optimize; Nuernberg(19)-200
humanities research,
hypertext structure needs; DeRose(132)-249
Perseus project; Crane(90)-51
socio and philosophical hypermedia design principles; Moulthrop(133)-259
hypermedia,
OODBMS support for, HyperStorM; Bapat(20)-203
semantics specific to, tailoring an abstract hypermedia engine to accomodate; Bapat(20)-207
hyperspeech (MIT Media Lab system),
audio notes; Arons(25)-134
brainstorming tool; Arons(25)-134
personal memory aid; Arons(25)-134
industrial-strength, building with a distributed hypermedia collaboration environment; Shackelford(224)-1
interfaces, hypermedia engine role with respect to; Schutt(148)-99
Kiosk, Hypertext'91 paper; Creech(169)-25
kiosk,
Kiosk; Creech(169)-25
Portinari project; Schwabe(12)-116
knowledge base, multiple views over, DSS shell architecture with a dynamic hypertext interface provision for; Bieber(182)-207
law,
copyright issues for hypertext systems; Jones, III, Esq.(109)-367
intellectual property information management; Yoder(125)-159
links and structures in hypertext databases for; Wilson(156)-194
patent development; Yoder(125)-159
product liability issues for hypertext systems; Jones, III, Esq.(109)-367
layer,
as hypermedia system layer according to HAM specification; Bapat(20)-204
HyperStorM implementation within the VODAK OODBMS; Bapat(20)-204
legal, hyperbases; Wilson(156)-194
legal issues for hypertext publishing; Jones, III, Esq.(109)-367
level, system-level hypertext support for; Bieber(182)-206
link management requirement for; Malcolm(168)-19
links; Garzotto(190)-313
HDM term definition; Garzotto(190)-315
maintenance support; Hayes(121)-119
manager,
connecting application elements with a hypertext engine through bridge laws; Bieber(182)-209
DSS shell architecture; Bieber(182)-206
medicine; Frisse(91)-57
Dynamic Medical Handbook; Frisse(128)-202, Consens(134)-284
Hypertext Medical Handbook; Frisse(91)-57
Intermedia use for education in; Beeman(92)-67
metadata managers distinguished from; Nuernberg(19)-200
modeling, HyperStorM; Bapat(20)-207
multiple, defining over the same set of documents, using the nested context model; Casanova(181)-194
non-fiction writing; Neuwirth(95)-121
open architecture support for integration of, in DeVise Hypermedia system; Gronbaek(226)-25
real-time hypertext-DSS systems, U.S. Coast Guard use; Bieber(182)-204
reference browsers, converting the OED to hypertext; Raymond(96)-143
research,
NoteCards as a tool for creating documents in; Trigg(93)-89
Notes as a support tool for creating documents; Neuwirth(95)-121
scholarly research,
hypertext structure needs; DeRose(132)-249
Perseus project; Crane(90)-51
sciences,
Intermedia as a tool for teaching; Beeman(92)-67
research, computational hypertext use for; Schnase(127)-181
self-modifying in response to user skill level; Bieber(182)-207
semantics, limitations of current systems; Bapat(20)-206
software engineering; Bigelow(111)-397
DIF; Garg(112)-409
HOT (Hypermedia Object-oriented Toolkit) use for; Puttress(143)-32
source code control, DynamicDesign; Bigelow(111)-397
speech interfaces, handheld and portable computers; Arons(25)-134
structure manipulation independent from, application design implications; Nuernberg(19)-197
system design tools, gIBIS (graphical Issue Based Information System); Conklin(102)-247
systems,
Guide; Campbell(87)-33
HAM; Campbell(87)-21
NoteCards; Marshall(103)-253
technical documentation, Document Examiner use for; Walker(106)-307
third-party, support for in HyperStorM abstract hypermedia engine; Bapat(20)-209
used to create the data, potential of hypermedia technology for managing; Malcolm(168)-15
writing; Trigg(93)-89
Notes; Neuwirth(95)-121
WE; Smith(100)-195
Aquanet,
See Also spatial; structure(s);
ECHT '92 paper; Marshall(201)-53
as hypermedia application, requirements for hypermedia engine support; Bapat(20)-205
Hypertext '91 paper; Marshall(186)-261
relations, acteme characteristics; Rosenberg(3)-22
spatial hypertext use of; Marshall(242)-217
architectonic presentation,
See Also rhetoric; semantic(s); structure(s);
architecture,
See Also rhetoric; semantic(s); structure(s); system(s); theory;
architectonic presentation, potentials for future development of HyperCafe techniques; Sawhney(1)-7
CID; Boy(171)-51
client/server, DeVise Hypermedia system as a Dexter-compliant cooperative architecture; Gronbaek(226)-25
design environment for; Fischer(120)-105
Dexter, DeVise Hypermedia system as a Dexter-compliant cooperative architecture; Gronbaek(226)-25
distributed, importance for industrial software development, implications for hypertext systems design; Smith(180)-184
distributed multimedia, content-based information retrieval and navigation schema for; Hirata(2)-11
DSS shell, with a dynamic hypertext interface; Bieber(182)-207
framework, as attribute for comparing open hypermedia systems; Osterbye(13)-129
hypermedia operating system,
general structure of; Nuernberg(19)-198
HOSS implementation; Nuernberg(19)-198
hypertext, extensibility, as hypertext research issue addressed by ABC graph server; Smith(180)-186, Smith(180)-190
layered,
ABC graph server characteristics; Smith(180)-185
document interchange issues; Bieber(182)-213
DSS shell architecture with a dynamic hypertext interface designed as; Bieber(182)-207
generalizing to support non-link-based hypertext reference models; Parunak(184)-240
handling filters in; Bieber(182)-212
tools for coordinating information systems with a dynamic hypertext interface; Bieber(182)-211
LogicWeb system; Loke(23)-237
MAVIS (Microcosm Architecture for Video, Image, and Sound); Lewis(21)-215, Wilkins(65)-1
modular hypermedia, components of; Shackelford(224)-1
multimedia, Andrew Toolkit application development facilities; Sherman(142)-13
object-oriented, DeVise Hypermedia system as a Dexter-compliant cooperative architecture; Gronbaek(226)-25
open,
ABC support of; Smith(180)-182
advantage of shadow file storage of links for; Creech(169)-28
advantage provided by modularity in hypermedia architecture design; Shackelford(224)-1
as a policy for application programs; Smith(180)-184
concurrency control issues in a collaborative distributed hypertext system; Wiil(225)-14
DSS shell architecture with a dynamic hypertext interface designed as; Bieber(182)-207
dynamic link-resolving hypermedia architecture; Tompa(234)-118
for application programs, as issue addressed by ABC; Smith(180)-190
for applications, ABC approach to; Smith(180)-179
importance to software reuse library environment; Creech(169)-27
integrating applications in DeVise Hypermedia system; Gronbaek(226)-25
Knowledge Weasel; Lawton(233)-106
Microcosm link service; Hall(307)-256
platform independent, DeVise Hypermedia system as a Dexter-compliant cooperative architecture; Gronbaek(226)-25
software,
as artifact component; Smith(180)-179
embedding knowledge in links and nodes use to simplify, in hyperspeech system; Arons(25)-133
system,
FIRST (Fuzzy Information Retrieval SysTem); Lucarella(147)-89
maintaining consistency between design and de facto versions, ABC tools for; Smith(180)-189
view, Kiosk classification lattices use for; Creech(169)-30
volatile hypertext, Hypertext'91 paper; Bernstein(28)-243
argumentation,
See Also collaboration; gIBIS; structure(s);
AAA as hypertext-based authoring tool for; Schuler(151)-137
claim structure representation in NoteCards; Marshall(103)-259
compared with cognition; Smolensky(101)-217
conceptual framework; Schuler(151)-140
constraint-based hypertext for; Smolensky(101)-215
creating, hypertext representation of in EUCLID; Smolensky(101)-227
generation of arguments, processes involved in; Smolensky(101)-220
gIBIS structure an aid to; Conklin(102)-249
hypertext support for,
EUCLID; Smolensky(101)-215
gIBIS; Conklin(102)-247
IBIS method, way of encoding; Conklin(102)-248
JANUS support for; Fischer(120)-105
logical structure, representing with NoteCards; Marshall(103)-253
matrix layout advantages for evaluation; Marshall(103)-259
modeling argument structures with NoteCards; Marshall(103)-253
multi-level analysis,
in NoteCards; Marshall(103)-259
using NoteCards for; Marshall(103)-259
network limitations for; Smith(100)-201
networks,
assessing the strength of; Marshall(103)-257
representation in NoteCards; Marshall(103)-257
patterns, constrained NoteCards browser cards used to show; Marshall(103)-262
Rational Actor Model; Marshall(103)-256
reading, hypertext representation of in EUCLID; Smolensky(101)-219
reasoned discourse, support by EUCLID; Smolensky(101)-217
requirements for; Kaltenbach(174)-101
SEPIA, Hypertext'89 paper; Streitz(138)-343, Streitz(197)-11
spatial layout, importance for the representation of; Marshall(103)-260
structure, logical; Marshall(103)-259
structure and process, representation in NoteCards; Marshall(103)-256
structure of, representing in hypertext; Marshall(186)-262
taxonomy representation in NoteCards; Marshall(103)-259
Aristotle,
associative principles, computer science use of; Oren(105)-300
ARL (Argumentation Represenation Language),
argument structure description with; Smolensky(101)-218
ARL (Argumentation Representation Language),
functionality description; Smolensky(101)-218
semi-formal language; Smolensky(101)-219
arrival,
See Also rhetoric; structure(s);
rhetoric of; Landow(56)-331
actemes relationship to; Rosenberg(3)-25
art,
See Also applications;
museums, as Himotoki application; Hirata(2)-19
Portinari project; Schwabe(12)-116
retrieving with media-based information retrieval tools; Hirata(237)-159
articles,
See component(s); nodes;
articulation points,
structure development use of; Botafogo(172)-70
term definition; Botafogo(172)-68
artifacts,
ABC term definition and components; Smith(180)-179
defining with HyperSet; Parunak(230)-73
Hyperset term definition; Parunak(184)-237
term definition and components; Shackelford(224)-1
artificial conversations,
creating in the MIT Media Lab hyperspeech system; Arons(25)-143
artificial intelligence (AI),
See Also cognitive; knowledge; representation;
agents,
intelligent software hypertext system use; Garg(112)-418
narrative linking use of; Cleary(4)-34
Telescript use of compared with LogicWeb; Loke(23)-239
link generation using an object-oriented knowledge representation model, in MacWeb; Nanard(228)-51
problem solving hypermedia systems incorporating; Bareiss(232)-94
ASK systems,
See Also information, retrieval; mental models; representation;
artificial intelligence model-based systems, Hypertext '93 paper; Bareiss(232)-94
ASKTool, Hypertext '96 paper; Cleary(4)-31
ASKTool hypermedia editor; Cleary(4)-31
as structured hypermedia systems; Cleary(4)-31
ASM (Association Set Manager),
as HOSS hyperbase process component; Nuernberg(19)-199
association,
See Also aggregation; links; relationship; spatial, hypertext systems;
abstract data model representation; Bapat(20)-207
associative links,
lack of design principles; Hara(173)-76
providing current context for; Boy(171)-54
as class of link types; Allan(5)-43
element, grouping content elements into nodes with; Bapat(20)-208
Extended Dexter model relations; Gronbaek(15)-151
HOSS hyperbase process support; Nuernberg(19)-199
layer, generalizing link layer into to support non-link-based hypertext models; Parunak(184)-240
Association of American Medical Colleges,
bibliographic reference; Frisse(91)-57
assonance,
exploration with dot plots; Bernstein(28)-254
assumptions,
underlying user expectations about link meaning; Landow(56)-332
asynchronous,
cooperation modes, in DeVise Hypermedia system; Gronbaek(226)-25
document annotation in Knowledge Weasel; Lawton(233)-106
Athena Muse,
Videobook relationship to, bibliographic reference; Ogawa(144)-38
attribute(s),
See Also object-orientation;
ALF (attribute list forms),
data content notation in HyTime; Buford(11)-111
HyTime feature analysis of; Buford(11)-110
associated with both links and nodes in ABC; Smith(180)-184
associative links, use in establishing user-customized views; Hara(173)-77
AttributeValue function, Dexter definition; Halasz(299)-36
combining in the creation of nodes during OOHDM design process; Schwabe(12)-121
cutting and pasting of, in navigational class definitions; Schwabe(12)-121
defining navigational contexts with; Schwabe(12)-122
HAM,
data object; Bapat(20)-204
definition; Campbell(87)-23
HAM objects, characteristics of; Campbell(87)-23
how different from relations; Garg(110)-377
in hypermedia application design; Schwabe(12)-120
hypermedia platforms, and their characteristics; Wiil(14)-141
as hypertext abstractions; Garg(110)-379
labelling the types of nodes, links and contexts in DYNAMICDESIGN; Bigelow(111)-398
links,
as industrial hypertext requirement; Malcolm(168)-19
link types as a form of, importance in an industrial hypermedia environment; Malcolm(168)-20
nodes,
in an ACE input graph, clustering relation as an; Hara(173)-81
term definition in nested context model; Casanova(181)-194
object and link, importance in an industrial hypermedia environment; Malcolm(168)-20
objects, in an abstract hypertext model; Garg(110)-377
Trellis,
attribute space, characteristics; Stotts(183)-223
term definition; Stotts(183)-221
audio,
See Also multimedia; sound;
ABC support of; Smith(180)-182
annotating,
issues involved with; Lawton(233)-106
Knowledge Weasel use for; Lawton(233)-106
cocktail party effect, hyperspeech research into; Arons(25)-143
cues,
hyperspeech (MIT Media Lab system), future extensions planned; Arons(25)-142
landmark recognition use of, in hyperspeech; Arons(25)-133
database, hyperspeech (MIT Media Lab) characteristics; Arons(25)-135
domain, navigation issues compared with spatial domain; Arons(25)-134
environment, hyperspeech (MIT Media Lab system) as a speech-only hypermedia system for; Arons(25)-133
focus, hyperspeech research into; Arons(25)-143
format conversion handlinng; Shibata(231)-82
handling of, VideoBook; Ogawa(144)-38
humming a song, media-based navigation using; Hirata(237)-159
media-based navigation, in Miyabi; Hirata(237)-159
melody, media-based navigation using in Miyabi; Hirata(237)-159
navigation in; Lewis(21)-215
content-based; Hirata(2)-11
moving hot-spot; Hirata(2)-18
notes, hyperspeech (MIT Media Lab system) application; Arons(25)-134
presentation control through context-based links; Hardman(39)-183
real-time, ABC component; Shackelford(224)-1
stream segregation, hyperspeech research into; Arons(25)-143
tracks, HyTime representation of; Buford(11)-111
user interface design issues; Shibata(231)-82
value of electronic documentation; Oren(105)-295
voice annotations as desired feature for future hypervideo systems; Sawhney(1)-8
Augment,
See Also classification, pioneer systems; people, Engelbart, Doug;
abstraction mechanisms in; Botafogo(172)-64
as non-linear information manager; Marshall(186)-261
as design idea source for the Dexter hypermedia reference model; Osterbye(13)-129, Halasz(299)-30
as human-readable link example; Gronbaek(15)-157
software development support by; Smith(180)-183
augmenter,
See Also viewers;
See viewers;
authoring,
See Also open hypermedia systems (OHS); programming; rhetoric; structure(s); system(s); writing;
3D hypervideo, requirements; Sawhney(1)-9
as readers, fundamental to Guide's design; Brown(88)-37
author behavior,
copyright law model of; Samuelson(170)-39
Xanadu model, analysis of; Samuelson(170)-46
browsing or, classification of hypermedia systems according to; Halasz(108)-351
design principles for large information spaces, database model use for; Hara(173)-75
dialogue with reader, analysis of; Michalak(238)-174
environment, integration with reading environment, importance for design tasks; Kaindl(192)-350
facilitating,
hypermedia design issue; Akscyn(86)-9
KMS approach to; Akscyn(86)-16
hypermedia design issues concerning; Akscyn(86)-9
hypermedia projects at Boeing that emphasize; Malcolm(168)-15
hypermedia templates as tools for; Catlin(178)-147
hypertext requirements for; Bernstein(28)-244
implied, characteristics; Michalak(238)-174
in-the-large, HDM use for specifying; Garzotto(190)-314
in-the-small, characteristics; Garzotto(190)-314
industrial hypertext requirements, users must be enabled for; Malcolm(168)-19
invariance of structure defined by author, under apparent alteration in a dynamic hypertext; Stotts(183)-220
legal considerations for determining when the user is also an author; Jones, III, Esq.(109)-369
limitations of node-and-link models for complex hypertext design; Garzotto(190)-314
MacWeb use for, example; Nanard(191)-338
multimedia, Andrew Toolkit application development facilities; Sherman(142)-13
paths, mechanism requirement; Zellweger(54)-1
quality assessment guidelines; Brown(141)-1
reuse methods for inclusion in; Garzotto(10)-93
rhetoric,
problems of; Thuring(179)-163
styles, advantages of a design model for comparing; Garzotto(190)-315
social, cognitive, and political implications; Greco(9)-85
software, Hyperties; Shneiderman(99)-191
structure development, articulation points importance for; Botafogo(172)-70
time-based hypermedia issues, VideoBook; Ogawa(144)-38
tools,
AAA; Schuler(151)-137
authoring of this flexible hypertext environment; Charoenkitkarn(241)-206
CMIFed; Hardman(39)-183
collaborative distributed hypertext, concurrency control issues; Wiil(225)-14
cooperative, DeVise Hypermedia system as a Dexter-compliant cooperative architecture; Gronbaek(226)-25
HieNet; Wiil(225)-145
HyperSet; Parunak(230)-73
hypervideo, needed characteristics; Sawhney(1)-8
Knowledge Weasel; Lawton(233)-106
linkless hypertext, Queries-R-Links (QRL) and Queries-R-Focused Links (QRFL); Charoenkitkarn(241)-206
MORE (Multimedia Object Retrieval Environment); Lucarella(227)-39
See Also Guide;
See Also NoteCards;
See Also Notes;
See Also SEPIA;
See also Storyspace;
See Also WE;
time-based media, Himotoki moving hot-spot editor; Hirata(2)-18
Trans-ASK; Bareiss(232)-94
Trellis system for translating strings to graphs; Stotts(155)-180
vs reader, dimension for categorizing hypertext systems; Walker(106)-308
authority,
impact of hypertext on; Moulthrop(188)-292
authors,
See people;
automatic,
clustering techniques, overview map generation with, in CYBERMAP; Gloor(175)-108
conversion, hypermedia projects at Boeing that emphasize; Malcolm(168)-15
document production, MacWeb facilities that support; Nanard(191)-334
events, Trellis timing mechanism use to create; Stotts(183)-222
indexing,
creating hypertext structure from linear documents with; Nanard(191)-331
CYBERMAP's use to identify related nodes; Gloor(175)-110
ioverview map generation with, n CYBERMAP; Gloor(175)-108
link generation,
characteristics and requirements for an industrial hypermedia environment; Malcolm(168)-21
CYBERMAP characterized by; Gloor(175)-117
See Also HyPursuit;
See Also information, retrieval;
See Also Link Apprentice;
link typing as automated link generation tool; Allan(5)-42
linking; Cleary(4)-31
purpose-based; Shibata(231)-82
text; Salton(235)-131
user-centered approach in HieNet; Wiil(225)-145
overview map generation,
CYBERMAP characterized by; Gloor(175)-117
using automatic clustering techniques in CYBERMAP; Gloor(175)-108
awareness,
hypertext views, support for by Microcosm link sevice; Hall(307)-256
shared, support for by DeVise Hypermedia system, a Dexter-compliant cooperative architecture; Gronbaek(226)-25