Contexts—a partitioning concept for hypertext

Delisle, Norman M.; Schwartz, Mayer D.

doi:10.1145/27636.27639

Cited by 110 publications

(43 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As noted above, it is a straightforward matter to use many of the features of a hypertext system in Object Lens (e.g., Halasz, Moran, & Trigg, 1987;Garrett, Smith, & Meyrowitz, 1986;Delisle & Schwartz, 1986). For instance, our system currently contains an object type called Text that displays only two fields: Name and Text.…”

Section: Hypertextmentioning

confidence: 99%

Object lens: a “spreadsheet” for cooperative work

Lai

Malone

1988

Proceedings of the 1988 ACM Conference on Computer-Supported Cooperative Work - CSCW '88

View full text Add to dashboard Cite

Management in the 1990s is an industry and governmental agency supported research program. Its aim is to develop a better understanding of the managerial issues of the 1990s and how to deal most effectively with them, particularly as these issues revolve around anticipated advances in Information Technology.Assisting the work of the Sloan School scholars with financial support and as working partners in research are: The conclusions or opinions expressed in this paper are those of the author(s) and do not necessarily reflect the opinion of the Massachussetts Institute of Technology, the Management in the 1990s Research Program, or its sponsoring organizations. AcknowledgementsThe work described in this paper was supported, in part, by Wang Laboratories, Xerox Corporation, General Motors/Electronic Data Systems, Bankers Trust Company, the Development Bank of Singapore, and the Management in the 1990s Research Program at the Sloan School of Management, MIT.We would especially like to thank Ken Grant who suggested some of the earliest ideas that led to Object Lens and Jin Lee who helped debug the most recent version. The Object Lens system and this paper have also benefitted from conversations with Cheryl Clark, Kevin Crowston, Randy Davis, Frank Halasz, Mitch Kapor, Stan Lanning, Wendy Mackay, Ramana Rao, Randy Trigg, David Rosenblitt, and Franklyn Turbak. AbstractObject Lens allows unsophisticated computer users to create their own cooperative work applications using a set of simple, but powerful, building blocks. By defining and modifying templates for various semistructured objects, users can represent information about people, tasks, products, messages, and many other kinds of information in a form that can be processed intelligently by both people and their computers. By collecting these objects in customizablefolders, users can create their own displays that summarize selected information from the objects in table or tree formats. Finally, by creating semiautonomous agents, users can specify rules for automatically processing this information in different ways at different times.The combination of these primitives provides a single consistent interface that integrates facilities for object-oriented databases, hypertext, electronic messaging, and rule-based intelligent agents. To illustrate the power of this combined approach, we describe several simple examples of applications (such as task tracking, intelligent message routing, and database retrieval) that we have developed in this framework.

show abstract

Section: Hypertextmentioning

confidence: 99%

Object lens: a “spreadsheet” for cooperative work

Lai

Malone

1988

Proceedings of the 1988 ACM Conference on Computer-Supported Cooperative Work - CSCW '88

View full text Add to dashboard Cite

show abstract

“…As a result, new structure container revisions that employ single containment must replicate all contained objects when a new revision, or working copy is made. For example, this is the case with Neptune [9]. When the structure container holds the link and a single revision of its endpoint objects (anchor, work, or both), and the revision selection rule is located on the structure collection, an additional dynamic containment choice becomes available.…”

Section: Containment Design Space Choice For All Pairs Of Containers mentioning

confidence: 99%

Design spaces for link and structure versioning

Whitehead

2001

Proceedings of the Twelfth ACM Conference on Hypertext and Hypermedia - HYPERTEXT '01

View full text Add to dashboard Cite

This paper reflects upon existing composite-based hypertext versioning systems, and presents two high-level design spaces that capture the range of potential choices in system data models for versioning links, and versioning hypertext structure. These two design spaces rest upon a foundation consisting of a containment model, describing choices for containment in hypertext systems, and the design space for persistently recording an object's revision history, with applicability to all versioning systems. Two example points in the structure versioning design space are presented, corresponding to most existing composite-based hypertext versioning systems. Using the presented design spaces allows the data models of existing hypertext versioning systems to be decomposed and compared in a principled way, and provides new system designers significant insight into the design tradeoffs between various link and structure versioning approaches.

show abstract

“…Work on developing hypermedia systems that address the issue of version control is ongoing. A few large systems have implemented some sort of version control capability, keeping track of the history of nodes are links as well as considering changes in the network as a whole [15,16].…”

Section: Compatibility and Version Controlmentioning

confidence: 99%

“…A slightly more esoteric approach would be to use hypertext systems to explore ambiguities and differing interpretations of the Code. Systems could be designed around the concept of issue-based information systems (IBIS) [9][10][11][12][13][14][15][16][17][18][19]. Issues could represent problem areas in the Building Code.…”

Section: Codes-related Researchmentioning

confidence: 99%

Hypercode: The building code as a hyperdocument

Cornick

1991

Engineering with Computers

View full text Add to dashboard Cite

/npsi/ctrl?lang=en http://nparc.cisti-icist.nrc-cnrc.gc.ca/npsi/ctrl?lang=fr Access and use of this website and the material on it are subject to the Terms and Conditions set forth at http://nparc.cisti-icist.nrc-cnrc.gc.ca/npsi/jsp/nparc_cp.jsp?lang=en NRC Publications Archive Archives des publications du CNRCThis publication could be one of several versions: author's original, accepted manuscript or the publisher's version. / La version de cette publication peut être l'une des suivantes : la version prépublication de l'auteur, la version acceptée du manuscrit ou la version de l'éditeur.Engineering with Computers, 7, 1, pp. 37-46, 1991 Hypercode : The Building Code as a hyperdocument Cornick, S. M.Engineering with Computers 7,[37][38][39][40][41][42][43][44][45][46] HyperCode: The Building Code as a Hyperdocument Abstract. The Canadian National Building Code serves as a model document for several other legal documents that govern the construction of buildings, and as such it consists primarily of a list of definitions, prescriptive rules, and performance requirements, and contains cross-references to other legal and quasilegal documents. There are many different users of this document, each using the Code for its own ends. There is also a considerable amount of variance among the individual user groups. The concept of hypertext, developed in late 1930s and mid-1940s, exhibits characteristics that make it an ideal medium for the development of an electronic Code. The National Building Code conceived as a hyperdocument would allow for much greater flexibility in accessing the information contained therein. A HyperCode would also enable users to tailor the document to their specific needs.

show abstract

Contexts—a partitioning concept for hypertext

Cited by 110 publications

References 10 publications

Object lens: a “spreadsheet” for cooperative work

Object lens: a “spreadsheet” for cooperative work

Design spaces for link and structure versioning

Hypercode: The building code as a hyperdocument

Contact Info

Product

Resources

About