Platforms to support:
Transfer methods/protocols to support:
Minimum Spec computers to support:
From Draft OHS-Project Plan, Doug Engelbart, 23-Oct-2000 <BI,2120,>
High-Resolution Addressability: Translation into the
I-File's special structure and format creates, among other things,
new label tags attached to many objects (e.g. each paragraph),
so that links serviced by the HyperScope can explicitly target
many objects in the file which were not addressable in their
"legacy" form. Ideally, every object in a file should
be targetable by a link whose author wants to comment specifically
about that object.
View-Specifications: The HyperScope will offer a set
of "transcoded viewing options" which a user can selectively
employ to examine that file.
Expanded set of HyperScope accessable "Legacy File
Types:" In principle, this manner of HyperScope access
can be implemented for any standard type of file or data base.
The Project will establish the basic implementation conventions,
and proceed to develop the translation and special I-File properties
appropriate for a selected sequence of file/db types -- planning
tentatively for those to be used by:
Copying-Pasting HyperScope Links: When viewing a legacy file via his HyperScope, a user will easily be able to install a HyperScope link (HS-Link) in any legacy file, targeting an explicit location in the file being viewed on his HyperScope. Clicking on the desired target object in a HyperScope "Copy mode," he can subsequently turn to the "legacy editor" and "Paste" the appropriate link into the legacy file. Later execution of that link will take any subsequent HyperScope user to the desired, specific location and with the specified view.
Back-Link Management: Provision will be made to capture
information about links pointing through the HyperScopes into
a specified collection of files, to establish a "Back-Link
Data Base" (BLDB). For each such link, information to be
captured would be such as:
Extended addressing conventions to improve linking power:
Same file in multiple windows -- no real limit there -- simultaneously allowing different positioning and differnet viewing portrayals of a given file. Later, when editing of the Intermediary File will be offered, any legal edit operation executed in one window is reflected accurately and immediately in all other of that file's portrayal windows. This flexibility in utilizing multiple windows has surprising value when users learn to make effective use of it.
Non-Link Jumps; Options offered via simple selection
Double-click Jumps offer surprisingly flexible options:
From Draft OHS-Project Plan, Doug Engelbart,
The OHS Interface Architecture will be set up explicitly to provide for multiple UIS options, with a common, full-feature Application Program Interface (API). To support extensive capability evolution, it will be necesary to provide for a range of UIS options, varying in complexity, potential competency level, difficulty to learn, types of interface devices and modalities, etc.
EXAMPLE:Being able effectively to support web-connected mobile phones is one example.
But a VERY IMPORTANT purpose here is to enable individuals, or special-role support teams, to experiment with interface equipment, functionality, and control options, together with optional special attributes of the standard Intermediary File, to pursue especially high performance at important parts of their knowledge processes.
Having this kind of exploration in any event will be necessary. Doing it with special extensions to the widely used OHS will be very important in enabling feasible migration of these tools and skills out into the rest of the communities. Moreover, doing this exploratory high-performance activity over the SAME WORKING domains amplifies that benefit immensely; motivated individuals can optionally acquire special interface equipment, take some special training, and move up to a "new class of user proficiency" (e.g. becoming a certified Class-4B Knowledge Integrator).
There are support roles anticipated in developing and maintaining a community's Dynamic Knowledge Repository (DKR) which could very well be taken on by specially trained High-Performance Support Teams. Such a team could for instance be fielded in a university (as a research project into High-Performance Collective Knowledge Work), and take on the "Knowledge Integrator" role for a professional society's DKR. And competetive exercises could be conducted among teams from different universities -- or companies, or agencies, or countries -- as part of an explicit processes to facilitate improvement in "Collective IQ."
Maturing/Evolving the Hyperscope into full-feature OHS.
Evolution of the Intermediary File format will be given careful attention since it is destined to become the format for the full Open Hyperdocument System (which will continue its evolution).
An OHS "User Interface System" (UIS) will be developed to provide a basic range of functions for moving, viewing and editing.
Provision for archiving, version control, etc. will be developed so that it becomes possible to develop and maintain an evolving knowledge base soley within an OHS environment -- with integrated flexibility and power accumulated from the best that was accomplished via HyperScope usage among the legacy files.
Now the VERY important feature of this approach to OHS development comes into play: task by task, or person by person, in almost any order and rate, users can start to keep their files entirely within the OHS environment. All the working material is still interlinkable, whether in OHS or legacy files.
And the critical community-development processes will become VERY important here -- to start the active "co-evolution" of the "Human System" and the OHS "Tool System" (as discussed at length in the "Bootstrap Publications").
For the scale of utilization that will be necessary, in number of inter-operating groups, in the diversity of inter-operable knowledge domains, and in the continuing changes in tools and skills, processes, etc. --
It will be absolutely critical that
It is sincerely hoped that organizations investing in the Stage-1 HyperScope development and use will do so with clear intent to be simultaneously readying their targeted application communities for becoming pro-active, "evolutionary participants."