The Dexter Hypertext Reference Model aims to capture the essential abstractions of hypertext systems through a formal and informal approach. It is structured into three layers: storage, run-time, and within-component. The storage layer models the network of nodes and links, the run-time layer handles user interaction, and the within-component layer deals with content and structure within nodes. The model focuses on the storage layer and the mechanisms of anchoring and presentation specification that interface between layers. Hypertext systems like NoteCards, Neptune, KMS, Intermedia, and Augment share the ability to create and manipulate networks of information nodes connected by links. However, they differ in data models and functionalities. For example, some systems use arbitrary-length documents, while others use fixed-size canvases. The Dexter model provides a standard terminology and formal model to compare and contrast hypertext systems, serving as a basis for interchange and interoperability standards. The model was developed from workshops on hypertext, aiming to capture common abstractions and establish a common terminology. It addresses the challenge of defining "node" and provides neutral terms like "component" to avoid confusion. The model includes a storage layer with components and links, a within-component layer for content structure, and a run-time layer for user interaction. The storage layer uses UIDs to uniquely identify components and includes mechanisms for indirect addressing. Anchors are used to specify locations within components, enabling span-to-span links. The run-time layer handles user interaction, with instantiations of components and link markers. The model also includes presentation specifications to define how components are presented. The Dexter model is designed to be flexible, allowing optional mechanisms for different systems. It aims to provide a comprehensive basis for hypertext interchange standards, as demonstrated by its use in developing formats for systems like NoteCards and HyperCard. The model is still in early development and is intended to accommodate future hypertext systems. It serves as a reference for comparing systems and developing standards for interoperability.The Dexter Hypertext Reference Model aims to capture the essential abstractions of hypertext systems through a formal and informal approach. It is structured into three layers: storage, run-time, and within-component. The storage layer models the network of nodes and links, the run-time layer handles user interaction, and the within-component layer deals with content and structure within nodes. The model focuses on the storage layer and the mechanisms of anchoring and presentation specification that interface between layers. Hypertext systems like NoteCards, Neptune, KMS, Intermedia, and Augment share the ability to create and manipulate networks of information nodes connected by links. However, they differ in data models and functionalities. For example, some systems use arbitrary-length documents, while others use fixed-size canvases. The Dexter model provides a standard terminology and formal model to compare and contrast hypertext systems, serving as a basis for interchange and interoperability standards. The model was developed from workshops on hypertext, aiming to capture common abstractions and establish a common terminology. It addresses the challenge of defining "node" and provides neutral terms like "component" to avoid confusion. The model includes a storage layer with components and links, a within-component layer for content structure, and a run-time layer for user interaction. The storage layer uses UIDs to uniquely identify components and includes mechanisms for indirect addressing. Anchors are used to specify locations within components, enabling span-to-span links. The run-time layer handles user interaction, with instantiations of components and link markers. The model also includes presentation specifications to define how components are presented. The Dexter model is designed to be flexible, allowing optional mechanisms for different systems. It aims to provide a comprehensive basis for hypertext interchange standards, as demonstrated by its use in developing formats for systems like NoteCards and HyperCard. The model is still in early development and is intended to accommodate future hypertext systems. It serves as a reference for comparing systems and developing standards for interoperability.