Open Hypermedia Systems. I found out about this because I finally got a
copy of the sigWeb Newsletter (ACM) which I joined last year. They're up
to OHS7, the seventh conference on the subject.
All of this leads to something called "Structural Computing" which I
discuss in my next post.
From that newsletter:
"An Open Hypermedia System (OHS) is typically a middleware component which
provides hypermedia functionality to applications on a user's
desktop. Hence, existing tools and applications can be hypermedia-enabled
using the functionality provided by an open hypermedia system."
OHS7 will be held at Hypertext 2001 in Denmark mid August.
OHS6 papers appear at
"The Open Hypermedia Systems Working Group (OHSWG) was formed at the second
workshop on open hypermedia systems, held in April, 1996, in Washington,
DC, in conjunction with the 1996 ACM Conference on Hypertext. The original
purpose of defining an open hypermedia protocol for OHS clients has evolved
into an effort to standardize general hypermedia systems work. This broader
effort is driven by the desire to maximize the applicability of the last
decade of hypermedia systems and infrastructure research.
Previously, systems work in hypermedia tended to be directed toward the
traditional application domain of navigation (i.e., the authoring and
browsing of structure over data), as inspired by Bush's seminal article, As
we may think . However, hypermedia structuring principles have been
applied to a wide variety of domains, including hyperliterature and
hypermedia art [Bernstein et al. 1991; Bolter and Joyce 1987; Bolter 1991;
Kaplan 1994; Kinsella 1996; Landow and Kahn 1992; Leistĝl 1994; Michalak
and Coney 1993; Moulthrop 1989; Sawhney 1996], argumentation systems
[Conklin and Begeman 1987; Fischer et al. 1989; McCall et al. 1990; Schuler
and Smith 1990; Smolensky et al. 1988], spatial hypertext [Marshall and
Shipman 1995], and systems for taxonomic work [Nürnberg et al. 1996, 1997;
Parunak 1991, 1993].
Much systems work intended for supporting navigation is applicable to
supporting these other domains as well. In order to deliver functionality
to this broader class of clients, however, it was necessary to consider
opening the set of structural abstractions supported by an OHS. A natural
way in which to accomplish this is to generalize the link server of
contemporary OHS's, replacing this single entity with an open set of link
server peers (or simply, structure servers).
Considering an open set of structure servers, however, led to the
separation of much of the component infrastructure from the definition of
the structure server interfaces themselves. The definition and
standardization of these component interfaces and the infrastructure that
supports client/server interactions in this environment is the new focus of
The basic purpose of the OHSWG is to standardize these aspects of OHS's.
Currently, each OHS implements slightly different interfaces on different
infrastructure, making applications integrated into one OHS unable to use
the services of other OHS's. Standardization of these aspects of systems
will allow clients to operate over all compliant OHS's. Since application
integration is an open-ended task, such standardization saves effort on the
most costly aspect of OHS implementation. Standardization also allows third
parties to build naturally compliant application, bypassing the extra
integration step completely. "
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Small business owners...
Tell us what you think!
Community email addresses:
Post message: unrev-II@onelist.com
List owner: unrev-IIemail@example.com
Shortcut URL to this page:
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
This archive was generated by hypermail 2b29 : Sat Aug 04 2001 - 19:33:20 PDT