The HyperDisco approach to open hypermedia systems is described to provide a platform to integrate existing and future distributed heterogeneous tools and data formats and to extend integrated tools to handle multiple collaborating users and multiple versions of shared artifacts.
The Hyperform approach is described, its advantages and disadvantages are discussed, and examples of simulating the HAM and the Danish HyperBase in Hyperform are given.
The goal of this effort is to provide an open framework that can be used by application developers outside the community to construct more powerful hypermedia-aware applications.
The Construct development environment is targeted at the construction of different types of hypermedia services by providing development tools that assist the system developers in the generation of the set of services that make up a hypermedia system.
The "split" in the current hypermedia research community between "system" and "domain" researchers and the still-present need for interoperability among systems are examined, and why any attempt to address the issues discussed in this paper must account for these observations.
This paper looks at the various problems that users and system designers encountered with systems at various stages of this development, focusing particularly on problems that were solved or caused by moving toward a more middleware-oriented approach.
Design, development, and deployment experiences of a dynamic, open, and distributed multiuser hypermedia system development environment called Hyperform is presented, based on the concepts of extensibility, tailorability, and rapid prototyping of hyper media system services.
The Flag taxonomy extends the terminology of the Dexter model to adequately cover issues that relate to open hypermedia systems such as integration and use of thirdparty applications to edit and display hypermedia components.
The overall idea with multiple open services is to rethink the way in which services are provided to clients and split up services into components, each of which provides a general, scalable, and functionally independent (orthogonal) service.