Open Hypermedia Protocol

Weblog Kitchen
Welcome Visitors
Things To Do


Recent Changes
Most-linked pages
Whos Who

Hypertext Kitchen

Style Guide
How To Edit
Wiki Sandbox

A problem with the development of OpenHypertextSystems was that each system required its own set of proprietary clients. This made it difficult to implement either a new system (because new clients had to be created) or a new type of client (because an underlying hypermedia system had to be created).

The Open Hypermedia Protocol (OHP) addressed this problem by describing a standard interface between clients and hypermedia servers. This would make it possible for existing clients to be reused on many hypermedia platforms, and reduce development times. The idea was to 'piggyback' OHP software onto existing clients, translating server communications into OHP on the fly. OHP software at the server would then translate the OHP messages from the modified client into the server's expected format.

However, inconsistencies in the Open Hypermedia Protocol have been pointed out, and the protocol has been criticised for its lack of an underlying data model and architecture.



A Draft Proposal for a Standard Open Hypermedia Protocol
Hugh Davis and Antoine Rizk and Andy Lewis, Proceedings of the 2nd Workshop on Open Hypermedia Systems, ACM Hypertext í96, Washington, D.C., 1996.

A Critique of the Open Hypermedia Protocol
Kenneth Anderson, Proceedings of the 3rd Workshop on Open Hypermedia Systems, ACM Hypertext í97, Southampton, UK, 11-17, 1997.

A Critique of the Open Hypermedia Protocol
Kenneth Anderson, Richard Taylor, & James E. Whitehead, JournalOfDigitalInformation Special Issue on Open Hypermedia Systems, 1(2), 1997.

-- Last edited October 27, 2002

Weblog Kitchen | Contact

Sponsored by Eastgate