Open hypermedia architectures and linking protocols (abstract)

Most computer users today work with heterogeneous environments that include software from many vendors, multiple platforms needing to communicate , and information bases on remote machines. Their needs are often not for increased functionality in any particular application, but integration among existing applications. In the last few years, this need has been addressed through proposals for open hypertext ar-chitectures and linking protocols. In principle, these allow linking across diverse applications and even across platforms. Rather than a monolithic hypermedia system presenting its own editors for various media, the user sees a framework into which existing editors can be " plugged " and a linking protocol with which to interconnect them. Though the framework is usually a separate program , the hope is that support for such open linking will one day migrate into the operating system. Indeed, protocols from Apple and Microsoft are steps in this direction. Though the participants on this panel bring their own perspectives and backgrounds to the problem area, all share a belief that the future of hypermedia is not with systems that " own the world " , but with those that attempt to '(connect the world ". Furthermore, the panelists and the projects they represent have developed significant open hypermedia architectures and linking protocols and can draw on experience with real users. Examples of questions we'll be raising: q What should be the minimum required of third-party applications that want to " play ". And how can we allow varying degrees of linking " awareness " across participating applica-tions? q Is consistent handling/appearance of links across applications important? (Consider, for example, Norm Meyrowitz's 1987 call for a linking equivalent to the cut fcopylpaste paradigm.) q How does this work relate to new standards like Hytime? q How do we get vendors to sign up for the idea? We need more " link-aware " software applications in order to get the project off the ground, but vendors first need to be convinced of the potential benefits.