THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
S U M M A R Y
DIARY: October 25, 2000 09:56 AM Wednesday;
Knowledge Management complex, but growing interest in growing a market.
2...Ontology and Engine for Topic, Graphical Maps Key Part of DKR
3...Experience Adds Value by Making Information Useful
......Reality Complex, and New Realities Grow Complexity
......Email Focus Technology to Augment Intelligence
.........I.called and talked to Jack.
4...Context Key Knowledge Management Criteria to Solve Complexity
5...Concept Requires Separate Treatment as Ontological Context
6...Pointrel Solves KM Issues, Working on Next Big Step
7...Kent, Engelbart Challenge Conventional Methods, Need Implementation
8...Market for Knowledge Management Driven by Information Overload
......Open Source Avoids Competing Proprietary Solutions
9...Call to Jack on Xanadu and Open Source
10...Launch Plan OHS/DKR Project Submitted by Doug Engelbart
11...Dynamic Knowledge Repository DKR Launch Plan and Scope
12...OHS/DKR Architecture Implements Vision for Paperless Office
13...Augment Intelligence Collective IQ Improve Collaboration Teamwork
14...Paperless Office OHS/DKR Applies Computers for Efficient Management
15...Culture of Knowledge Essential to Learn KM
16...Wisdom Leadership Unlock the Secret of Knowledge Management
17...Innovation Loop: Open Source is Fun, Learning Requires Diligence
18...Pilot Testing Solves Innovation Loop, Shows Value of Intelligence
19...Explicit Links Email Granular Addressability Enable Working Efficiently
.....Pay to Perform Knowledge Management as a Research Project
.....Pilot Testing Grows New Knowledge Overcomes Common Sense
20...Augment Archive Translate to Modern Environment
21...Knowledge Collection and Use is OHS Objective - Need Definition
22...OHS Launch Plan Needs Summary Explanation, a Vision
23...Open Source Development for Clear, Compelling Reasons
24...Phase-1: OHS Launch Project: HyperScope with Open Source Development
25...Links Followed Between Legacy Files Similar to HTML
26...Hyperscope Browser Not Editor, But More Power than Legacy Editors
27...Assume OHS Features Useful
28...Hyperscope Translates Files into XML+ I-File Format
29...Assume Communities will Develop Translators for OHS
30...Expanded set of HyperScope accessible "Legacy File Types
31...Addressability Added During Translation by Hyperscope
32...Multiple Views Can Be Selected
33...Ontology, Catagories Require Multiple Views to Manage Context
34...Context Management Uses Multiple Views to Understand Complexity
35...Copying-Pasting HyperScope Links
36...Linking Accomplished with Point and Click
38...Extended addressing conventions to improve linking power
42...Phase-2: Maturing/Evolving the Hyperscope into full-feature OHS:
43...Archiving, Version Control Enable Keeping All Files in OHS
44...Users, Organizations Migrate Toward Keeping All Files in OHS
45...Government and Enterprise Co-evolve Tools and Human Systems
46...Co-evolution OHS Skills Requires Proactive Organization, Open Source
47...Assume Participating Organizations Develop Applications for OHS
48...Phase-3: Evolve Multi-class UIS Architecture, High-Performance Teams
49...Support Teams Maintain Dynamic Knowledge Repository (DKR)
50...Knowledge Integrator - Motivated Use Special Equipment, Training
51...Com Manager Enables Intelligence Collection and Organization
52...DKR, Collective IQ Needs Intelligence Process to Generate Knowledge
Click here to comment!
1...Need example of how Pointrel manages context and concepts.
2...Launch plan needs Work breakdown structure (WBS), budget, schedule
3...Need steps and methods for accomplishing this objective; they
4...Need examples of one or two user guides that support KM enough to
5...Need definition of knowledge distinguished from data, information,
6...It would be helpful for the introduction to explain a three (3) phase
7...Has the study been done; does it show compelling evidence that
8...Need example of "legacy" files with links that are not
9...Usefulness needs correlation between theory of knowledge and OHS
10...Does the plan today mean Henry and Nicholas have to develop
11...How, then, will OHS support ontology for Context Management, per
12...Need examples to illustrate how backlinking and extended link
13...Need explanation of issues that require attention for I-File.
14...Who produces and controls the OHS program. Does open source mean
15...Need to expand and cite a few publications to support this
16...Who will perform this organization and what principles,
17...Need simpler explanation of actions required to ready targeted
18...How would a telephone support knowledge management?
19...Need example of a "knowledge process."
20..."Knowledge Integrator" seems awkward. "Analyst" probably works
0202 - Bootstrap Institute O-00000735 0101
020201 - Mr. Douglas C. Engelbart, Ph.D.
Complexity Knowledge KM Dilemma, Paul Fernhout
Complex Ontology Difficult to Support with Technology
Complexity Makes KM High Tech Tourism Cannot Produce Useful Technology
Core KM People Knowledge in their Head
DKR Difficult Design Not Enough Known about Knowledge
AI Cannot Think No Biological Drives
Experience Complex Difficult to Design Technology to Support Human Th
KM Difficult to Understand SDS Core Capability
Enginer Create Topic Map Ontology Organize Structure
Processor Create Graphical Topic Maps
Ontology Collaborative Evolutionary Epistomoloty, DKR Architecture, 0
Engine Map Topics Complexity Ontology Pandaora's Box of Complexity On
Black Box AI Mechanized Knowledge False Dangerous Idea 2 Groups KM
4515 - ..
4516 - Summary/Objective
451701 - Follow up ref SDS 16 0000, ref SDS 62 0000.
451703 - Paul Fernhout and Jack Park explore KM issues. ref SDS 0 LR6N Jack
451704 - proposes a processor to organize information automatically; Paul feels
451705 - it is difficult to accomplish because useful information must relate
451706 - to human experience, which is very complex. ref SDS 0 RH5H Paul
451707 - reports KM solutions have been elusive. He lauds Doug's
451708 - determination. ref SDS 0 JP3N Paul feels information overload is
451709 - building market pressure to find a solution. He expects KM development
451710 - to grow in the period ahead, and worries that market forces in
451711 - combination with patent rights will restrain development. ref SDS 0
451712 - 02TX Knowledge and KM are not defined in the discussion today.
451714 - ..
451715 - Called Jack and discussed ideas on KM. ref SDS 0 744K
451717 - ..
451718 - In the afternoon, received letter from Doug transmitting a draft
451719 - launch plan for OHS development. ref SDS 0 G3W8 Doug asks that
451720 - comments use links in the plan. This will show how willing people are
451721 - to perform KM. ref SDS 0 00VU The plan aims to support knowledge
451722 - work, and assumes proposed features will be useful. But knowledge is
451723 - not defined, and the plan omits subjects and search capability, among
451724 - other requirements. There is no mention of software development,
451725 - which is a plus, since engineering management is endemic to KM. Phase
451726 - I calls for fast and easy tools to create links, which would be very
451727 - useful. ref SDS 0 E9G2 Phase II calls for folks to migrate all files
451728 - to OHS based on vaguely defined powerful features. Phase III is weak
451729 - in failing to call for education in Knowledge Management to provide a
451730 - work role assigned to perform KM, like an accountant, engineer, truck
451731 - driver, etc. DKR is unclear and incomplete. ref SDS 0 C9WP
451733 - ..
451734 - Submitted ref DIT 1 0001 linked to this record and to the meeting at
451735 - SRI on 001017. ref SDS 60 0001
451737 - [On 000116 Jack Park and Paul Fernhout report SDS accomplishes
451738 - Doug's requirement to link the record. ref SDS 75 0001
451740 - [On 001121 offer sell SDS to team so linking can be accomplished.
451741 - ref SDS 78 0001
451749 - ..
4520 - Progress
452101 - Ontology and Engine for Topic, Graphical Maps Key Part of DKR
452102 - Experience Adds Value by Making Information Useful
452104 - Received ref DRT 1 0001 from Paul Fernhout dated 001024, and
452105 - continuing a powerful discussion with Jack Park on KM that lays out
452106 - challenges presented by the complexity of human thought, similar to
452107 - Paul's letter on 000405. ref SDS 27 5977
452109 - ..
452110 - [On 001028 Paul distinguishes KM from AI, setting objective to
452111 - augment human thinking. ref SDS 65 0001 and ref SDS 65 QN8G
452113 - ..
452114 - Paul initially cites Jack's point...
452116 - ...you can build a useful representation without knowing its
452117 - final use cases. You can then reach into that representation and
452118 - construct useful views according to specific needs.
452120 - ..
452121 - This reflects Jack's planning on 000623 to build an engine that can
452122 - formulate ontology, ref SDS 43 4752 and ref SDS 43 2915, which he
452123 - described as a...
452126 - Tool for Collaborative Evolutionary Epistomology has
452129 - ...to implement ideas for topic maps in Jack's letter on 000403.
452130 - ref SDS 26 1144 Jack explained on 000623 that this is a critical part
452131 - of knowledge management, ref SDS 43 2915
452133 - ..
452134 - [On 001130 Jack proposes AI ontology engine to improve SDS links
452135 - and subjects. ref SDS 81 GK8O
452137 - ..
452138 - [On 010217 KM researcher associates SDS with AI-like search
452139 - engine, Autonomy, explained in a Wired Magazine article which
452140 - sounds similar to Jack's idea today. ref SDS A1 5T8K
452142 - ..
452143 - [On 010223 Jack proposes AI ontology engine for SDS again.
452144 - ref SDS A3 3RKS
452146 - ..
452147 - [On 010405 Jack has a web site for a Nexist OHS project that
452148 - shows a "Grove" engine in the architecture. ref SDS A4 485N
452150 - ..
452151 - [On 010614 analysis shows SDS organic subject structure may
452152 - support KM better than an engine, until experience is gained that
452153 - enables an engine to be designed that supports the architecture
452154 - of human thought. ref SDS A6 HY6M
452156 - ..
452157 - [On 010730 DCMA expects KM will be an engine to process email.
452158 - ref SDS A8 WK9K
452160 - ..
452161 - [On 010425 Cycorp reports plans for Doug Lenat's team to release
452162 - Knowledge Management work product building an ontology,
452163 - ref SDS A5 GJ6J; and further to release an "inference" engine
452164 - technology, which may meet Jack's requirements. ref SDS A5 079K
452166 - ..
452167 - [On 060211 SRI CALO and Iris project reports progress developing
452168 - an "ontology engine." ref SDS B9 TE6F
452170 - ..
452171 - [On 060527 Jack recommended IEML website to illustrate using
452172 - subject maps and topic maps; review shows why KM is a lot of
452173 - hard work. ref SDS C0 EV5Q
452175 - ..
452176 - [On 070511 developed SDS context management that constructs
452177 - multiple accounts in the Subject Index and assigns to
452178 - Control Fields. ref SDS C1 0001
452180 - ..
452181 - Earlier on 991213 NSF denied proposal to research Com Metrics because
452182 - it did not cite bayesian methods to automate formulation of patterns
452183 - from information. ref SDS 14 3234
452185 - ..
452186 - On 000125 Roy Roebuck proposed Topic Maps. ref SDS 18 9246
452188 - ..
452189 - Paul responds that objectives (an "end") are needed to make
452190 - information useful. ref DRT 1 PR6F
452192 - ..
452193 - Paul continues...
452195 - I would argue we have so much experience in solving problems in
452196 - certain domains we tend to know what is useful in advance -- for
452197 - example, when creating a payroll system names are useful as are
452198 - social security numbers. Obviously, most people share a common
452199 - life situation (born, eat, sleep, work, get sick, die, etc.) and
452200 - so for applications intended to cover typical human type
452201 - situations we can guess at what is most useful. ref DRT 1 LP6K
452203 - ..
452204 - [On 010425 Opencyc plans common sense ontology knowledge base
452205 - and inference engine. ref SDS A5 079K
452207 - ..
452208 - Reality Complex, and New Realities Grow Complexity
452210 - In effect what you are saying is you can make a model of reality
452211 - without knowing the intended use of the model. ref SDS 0 LR6N
452212 - However, reality is almost infinitely detailed (down to
452213 - probability waves of subatomic particles) and almost infinite in
452214 - scale (~400 billion visible galaxies each of ~400 billion stars)
452215 - and almost infinite in time (20+ billion years back and who knows
452216 - how far forward). ref DRT 1 008J
452218 - ..
452219 - This view supports analysis in POIMS. ref OF 1 0561
452221 - ..
452222 - On 000221 Jack disclosed that ontology opens a Pandora's Box
452223 - of complexity. ref SDS 20 7455
452225 - [On 001130 Jack proposes an engine to automatically process
452226 - links and subjects, discussed in connection with ontology.
452227 - ref SDS 81 GK8O
452229 - ..
452230 - [On 001214 Jack presents Qualitiative Process Theory to
452231 - support ideas for "firing" processes and ontology.
452232 - ref SDS 84 VN4E
452234 - ..
452235 - [On 001219 Paul expects machine intelligence using
452236 - nanotechnology and bootstrapping will become capable of
452237 - handling complexity that will overwhelm the human psyche.
452238 - ref SDS 88 UM8M
452240 - ..
452241 - [On 010217 KM researcher associates SDS with AI-like search
452242 - engine explained in a Wired Magazine article which sounds
452243 - similar to Jack's idea today. ref SDS A1 YL5F
452246 - ..
452247 - Email Focus Technology to Augment Intelligence
452249 - Obviously, if we are talking about modeling how email is managed
452250 - or how hypertext is managed, we all know enough about those
452251 - subjects from everyday practical experience that we can go pretty
452252 - far in building flexible models based on our gut reactions
452253 - without needing many use cases at the start. But even then, needs
452254 - may change over time. ref DRT 1 006N
452256 - ..
452257 - Managing email is equally complex, since it relates the
452258 - reality Paul cites as infinitely complex. ref SDS 0 008J
452261 - ..
452262 - I called and talked to Jack.
452264 - He is making good progress with his KM project. He can now
452265 - manage information from the Internet for use in his daily
452266 - work. Next, he will do this for email, so that all of his
452267 - work can be accomplished from the new system. I explained
452268 - this is a good way to develop KM by working with it every day,
452269 - per the letter to the team on 001004.
452271 - ..
452272 - Jack related researching SDS records on the Internet. He
452273 - accesses records randomly from the index, and then takes off
452274 - in an interesting direction, following links. He likes
452275 - connections to original sources with analysis, as called out
452276 - in ISO criteria, reviewed on 950721. ref SDS 5 1740 I asked
452277 - why nobody on the team discusses this aspect of KM? Jack
452278 - feels software engineers want to improve data mining so people
452279 - can find information. He feels a big weakness is that SDS
452280 - only helps communication. Jack wants SDS subject management
452281 - on the web, so he can assemble information he wants, in
452282 - addition to using SDS for communication.
452284 - ..
452285 - [On 001027 Jack volunteers comments on SDS methodology from
452286 - reviewing the record online. ref SDS 66 ADK1
452288 - ..
452289 - [On 001027 Jack comments on analysis (below, ref SDS 0
452290 - ADK1), showing open source is not effective for developing
452291 - KM. ref SDS 66 ADK1
452292 - ..
452293 - We reviewed planning to develop this capability in a
452294 - proposal to NSF on 990615, ref SDS 12 SU3F, which was turned
452295 - down on 991213, because NSF believed Rod Welch does not
452296 - understand the "knowledge management dilemma." ref SDS 14 9144
452298 - ..
452299 - Another solution is to use SDS, but that entails performing
452300 - KM. Jack explained the huge effort people made to learn
452301 - wordprocessing and spreadsheets. The market is not yet ready
452302 - to learn how to use a spreadsheet for knowledge.
452305 - ..
452306 - Context Key Knowledge Management Criteria to Solve Complexity
452308 - Paul quotes Jack again...
452310 - Placeholders need context. I suppose I am arguing that a triad
452311 - is insufficient, that a forth element of the tuple (context) is
452312 - needed. ref DRT 1 014G
452314 - ..
452315 - This aligns with Gil Regev's request on 001019 who reported that
452316 - context helps understanding, but did not define either idea.
452317 - ref SDS 62 TF5H and ref SDS 62 164H
452319 - [On 001028 Jack sent a letter that omitted links to context.
452320 - ref SDS 66 O66I
452322 - ..
452323 - Paul explains ideas for technology to support context...
452325 - The issue is when things can be in multiple scopes. So I think as
452326 - a start, it makes it easier and more flexible to just use
452327 - additional triads to define one or more scopes for other triads.
452328 - Those scope triads can also be in scopes, although you can end
452329 - the infinite regress by assigning a default scope to triads
452330 - without any specific scope triad. So, scope then emerges out of
452331 - how triads are used. I'm not saying scope is unimportant, just
452332 - that it should be an emergent property managed by code as opposed
452333 - to built in to the structure (at least until we have more
452334 - experience with it). ref DRT 1 L54N
452338 - ..
452339 - Concept Requires Separate Treatment as Ontological Context
452341 - Paul quotes Jack again...
452343 - So, now we have a *concept* to represent. How do we do that?
452344 - With strings alone? I don't think so. When meat-space thinks
452345 - about Jo B., it conjures up images, recollections, lots of
452346 - contexts. It seems to me that there needs to be a representation
452347 - for that concept, one that, perhaps, points to all the known
452348 - contexts in which that concept plays some role. At least, when
452349 - any context uses some concept, that concept ought to be somehow
452350 - grounded somewhere. ref DRT 1 C63N
452353 - ..
452354 - Pointrel Solves KM Issues, Working on Next Big Step
452355 - Kent, Engelbart Challenge Conventional Methods, Need Implementation
452357 - Paul explains his Pointrel system provides a solution...
452358 - ..
452359 - I think you raise good issues, but I think the Pointrel
452360 - system or Kent's ROSE system can support them as well as or
452361 - better than anything else. ...I feel they can be dealt with in
452362 - code in the Pointrel System, but I think it less likely they can
452363 - be dealt with in a system that assumes much more in the low level
452364 - architecture. ref DRT 1 0159
452366 - Need example of how Pointrel manages context and concepts.
452368 - ..
452369 - On 000601 Paul proposed using Pointrel to process SDS records.
452370 - ref SDS 38 0784 There are quite a few records on the web,
452371 - including this one, which he might use to demonstrate this
452372 - aspect of knowledge management.
452373 - ..
452374 - ...I don't have a big library of such complex code to do
452375 - these sorts of tasks on this flexible substrate. I am focusing on
452376 - trying to make a good first step in the right direction that
452377 - supports a good next step. There is only so much one person can
452378 - do with limited time against a background of people entrenched in
452379 - the status quo. ref DRT 1 01E5
452381 - ..
452382 - William Kent more or less got so frustrated trying to take on the
452383 - RDBMS establishment for decades to make them see and respond to
452384 - the sorts of issues he discusses in "Data & Reality" that he
452385 - ended up going into technical writing as less stressful and has
452386 - since recently retired to spend his days doing fun stuff
452387 - unrelated to computing. It is a tribute to Doug's stamina and
452388 - thick skin he's still working towards Augment despite much the
452389 - same reception. One difference is that Doug has seen some of his
452390 - more concrete ideas implemented in bits and pieces around the
452391 - world (mouse, teleconferencing, email, hypertext, etc.), whereas
452392 - the primarily more abstract truths in "Data & Reality" are still
452393 - pretty much far from the mainstream with very few
452394 - implementations. ref DRT 1 W53L
Market Potential Setting New Standard
Enterprise Projects Consortium HP IBM Intel NEC Funding, 000830
Difference between Need and Market Demand
Information Overload Management Imploding Needs SDS Collaboration
Market Growing for KM Development, But No Evidence of KM Use
Oracle IBM IBM Joining Boeing, SRI, Consortia to Develop KM
610901 - ..
610902 - Market for Knowledge Management Driven by Information Overload
610904 - Paul anticipates...
610906 - ...Knowledge Management and related tools is definitely shaping
610907 - up to be an active one which will see titanic struggles over the
610908 - next few years by major players (including the likes of IBM and
610909 - Oracle), motivated by desperation as people look for new ways to
610910 - cope with the fire hose of information the internet puts at their
610911 - desks. ref DRT 1 02TX
610913 - ..
610914 - Paul does not explain what he has in mind by "Knowledge
610915 - Management," nor what market demand it can satisfy.
610917 - ..
610918 - KM is an attractive product idea, per analysis in a letter to
610919 - the team, ref DIP 2 007H, submitted on 000920. ref SDS 50 2V5F
610920 - On 000324 Lee Iverson reported at SRI that major KM projects
610921 - were failing. ref SDS 24 4877 More recently...
610923 - Boeing seems to be developing KM. ref SDS 50 0001
610925 - ..
610926 - Consortium reported on 000830. ref SDS 48 M5DS
610928 - ..
610929 - SRI may get funding, reported on 001017. ref SDS 60 4877
610931 - ..
610932 - [On 001219 Paul cites expanding complexity from increasing
610933 - IT, which drives the demand for KM. ref SDS 88 UM8M
610935 - ..
610936 - Who, though, is the customer for capability that will emerge
610937 - from these efforts, ref DIP 2 00AL, since KM is hard work that
610938 - boggles the mind, ref DIP 2 719F, also, reviewed on 000920,
610939 - ref SDS 50 2V5F, and in another letter, ref DIP 4 TK4H, on
610940 - 001004. ref SDS 54 0A3H
610942 - On 001019 Gil Regev wanted context to aid understanding.
610943 - ref SDS 62 TF5H
610945 - ..
610946 - Jack Park wanted cross-postings.
610948 - ..
610949 - Who will pay for providing these wonders of the 21st
610950 - century?
610952 - ..
610953 - [On 001123 Paul reviews lack of resources for
610954 - accomplishing KM using open source methods. ref SDS 79
610955 - R8VB
610959 - ..
610960 - Open Source Avoids Competing Proprietary Solutions
610963 - ..
610964 - Paul continues...
610966 - It would be nice if the core of a popular solution was an open
610967 - source/free software one, accompanied by lots of rich open
610968 - content. I had hoped the Pointrel Data Repository System could be
610969 - such a core. But frankly, I could easily see it being passed
610970 - by heavily funded corporate initiatives patenting the wheel and
610971 - its derivatives. I would predict if a system like the Pointrel
610972 - Data Repository System or the Bootstrap OHS or "our own thoughts"
610973 - does not come to dominate the KM landscape in the next year or
610974 - two, we will be a long time (until patent expiration) living with
610975 - multiple incompatible proprietary solutions. ref DRT 1 TC8N
610977 - ..
610978 - Evidently, the desire is to get KM established so competition
610979 - can improve implementation, similar to cars, backhoes, hair
610980 - spray, books and magazines.
610982 - ..
610983 - Getting from here to there is the challenge.
610985 - ..
610986 - One of the reasons I went public with a Pointrel implementation
610987 - back last May was to have it available as prior art (in addition
610988 - to Kent's book). ref DRT 1 02WV
610990 - ..
610991 - Still, it will be expensive to fight patents on every minor
610992 - variation.
610996 - ..
610997 - Call to Jack on Xanadu and Open Source
610999 - I asked Jack why Xanadu never seems to be mentioned in these DKR
611000 - discussions, since both parties spend a lot of time on related
611001 - issues, such as Jack is raising today, including the versioning
611002 - and linking problems Eric cited as an architecture snag on
611003 - 001019. ref SDS 61 3X9G
611005 - ..
611006 - The strong voices promoting open source KM, would seem to find an
611007 - ideal partner in Ted Nelson, since he and Doug have been working
611008 - the same issues for 40 years, reported on 000305. ref SDS 22 3762
611010 - ..
611011 - Jack said he recently encountered a very interesting program
611012 - provided by Xanadu.
611014 - ..
611015 - There is no evident reason why collaboration between Doug and
611016 - Ted Nelson have not jelled, since each promotes collaboration.
OHS/DKR Launch Plan Architecture Bush Vision Paperless Office Knowle
760401 - ..
760402 - Launch Plan OHS/DKR Project Submitted by Doug Engelbart
760404 - Received ref DRT 2 0001 from Doug Engelbart, providing links to a
760405 - broader explanation of OHS dated 001023. ref DRT 2 0002 The original
760406 - information is at...
760408 - http://www.bootstrap.org/a2h/BI/2120.html
760410 - ..
760411 - The plan provides vision and engineering for an OHS architecture set
760412 - out by Jack Park on 000426, ref SDS 31 0304. It covers development
760413 - vectors Doug set out on 000405, ref SDS 28 2484, following the initial
760414 - meeting at SRI on 000324. ref SDS 24 5880 It does not seem to change
760415 - Eugene Kim's report on 001017 that OHS architecture will be developed
760416 - by the new team. ref SDS 60 TJ3G
760418 - ..
760419 - [On 001214 Jack Park submits analysis under Qualitiative Process
760420 - Theory that proposes a shell to invent OHS. ref SDS 84 BH6K
760422 - ..
760423 - [On 001220 Jack and Pat Lincoln's brother, Brien, are updating
760424 - Augment NLS in a Java implementation, as a prototype for creating
760425 - the OHS. ref SDS 89 BV3W
760427 - ..
760428 - [On 010917 Eugene Kim announces OHS Launch Community starting up
760429 - and invites contributors. ref SDS B0 00UU
760431 - ..
760432 - [On 060211 Jack notifies that SRI releases Open Iris that
760433 - addresses goals in OHS/DKR. ref SDS B9 ZG5K
760435 - ..
760436 - Submission of a general plan aligns with recommendations on 000125 by
760437 - Dick Karpinski. ref SDS 18 2397
760440 - ..
760441 - Dynamic Knowledge Repository DKR Launch Plan and Scope
760442 - OHS/DKR Architecture Implements Vision for Paperless Office
760443 - Augment Intelligence Collective IQ Improve Collaboration Teamwork
760444 - Paperless Office OHS/DKR Applies Computers for Efficient Management
760446 - Doug's launch plan explains what the project is trying to accomplish
760447 - from the first meeting at SRI on 000324. ref SDS 24 JY3F Knowledge
760448 - Management uses computer that enable "paperless office" efficiencies
760449 - to think, remember, and communicate, solving problems, and discovering
760450 - opportunities. OHS/DKR technology augments intelligence described in
760451 - Doug's 1992 paper, discussed on 991222. ref SDS 15 3360 Leveraging
760452 - mental effectiveness was in Doug's SRI proposal in 1962, ref SDS 15
760453 - 7H5H, citing an article in 1945 by Vannevar Bush on using computers to
760454 - organize records of daily work for finding sources quickly, like in a
760455 - library, and also cope with expanding complexity by linking trails of
760456 - associations. ref SDS 15 XS6N Doug described a dynamic knowledge
760457 - repository (DKR), ref SDS 15 KI49, that builds "collective IQ" for
760458 - collaboration and teamwork to solve difficult problems. ref SDS 15
760459 - SO9N Tools and practices for Knowledge Management to capture and
760460 - connect the record of daily work were called CODIK in the 1992 paper
760461 - reviewed on 991222. ref SDS 15 0786 Growth of knowledge will enable
760462 - an ABC improvement system from natural synergy between people and
760463 - technology that supports continual learning. ref SDS 15 5187 Linking
760464 - in email with granular addressability for precision access and
760465 - efficient navigation is a first step toward Doug's OHS/DKR vision
760466 - reviewed on 991222. ref SDS 15 1Z61 Goals for technology to improve
760467 - knowledge work were presented more recently in Doug's 1998 paper
760468 - "Technology Template Project," reviewed in part on 000614. ref SDS 41
760469 - 4710 These references are not cited in the Launch Plan.
760471 - [...below, explicit links in OHS/DKR Launch Plan enable
760472 - contributors to get experience using precision access
760473 - collaborating on refinements for the plan. ref SDS 0 00VU
760475 - ..
760476 - [On 040113 executives, engineers, marketing visionaries
760477 - lose sight of purpose for knowledge management, because
760478 - leveraging intelligence to "connect the dots" for
760479 - understanding cause and effect in a complex record remains
760480 - a mysterious biological process; people cannot remember
760481 - what knowledge management is trying to accomplish.
760482 - ref SDS B8 VK4N
760484 - ..
760485 - Doug anticipates adjustments to this plan, but the initial content,
760486 - structure, and "Location Numbering" would not change. It will be
760487 - superseded with updated versions; and also supported by other planning
760488 - documents regarding deeper details and/or modifications to this, and,
760489 - also, plans associated with other phases of the larger Bootstrap
760490 - Program. ref DRT 2 IG7N
760492 - This draft plan is primarily on project scope.
760494 - ..
760495 - Launch plan needs Work breakdown structure (WBS), budget, schedule
760496 - and organization chart, reviewed in the record on 001017.
760497 - ref SDS 60 0784 and ref SDS 60 B4S7
760499 - ..
760500 - Submitted ref DIT 1 0001 linked to this record and to the meeting at
760501 - SRI on 001017. ref SDS 60 0001 Mention in a post script that Millie
760502 - and I cannot attend the social event he is planning next week.
760503 - ref DIT 1 K69I
760505 - [On 001027 called Doug and discussed the project. ref SDS 64 0001
OHS Linking Procedures, Doug Engelbart
Linking Procedures OHS Architecture, Doug Engelbart
Engelbar, Doug KM Expert Demonstrates Explicit Links Calls For Linkin
Feedback Launch Plan OHS/DKR Use Explicit Links Granular Addressabil
AC0701 - ..
AC0702 - Culture of Knowledge Essential to Learn KM
AC0703 - Wisdom Leadership Unlock the Secret of Knowledge Management
AC0704 - Innovation Loop: Open Source is Fun, Learning Requires Diligence
AC0705 - Pilot Testing Solves Innovation Loop, Shows Value of Intelligence
AC0708 - Explicit Links Email Granular Addressability Enable Working Efficiently
AC0710 - Doug invites dialog on the plan, and requests that contributors use
AC0711 - links to specific content locations being discussed. ref DRT 2 00VU
AC0712 - The plan calls for a group at SRI to implement OHS services,
AC0713 - ref DRT 2 03KJ, which should include writing a letter that links to
AC0714 - original sources, as Doug calls out today. Doug included anchors on
AC0715 - paragraphs in the Launch Plan to facilitate linking with conventional
AC0716 - email, per below. ref SDS 0 B0WI The format of these anchors do not
AC0717 - fit SDS requirements. Since SDS automatically creates anchors where
AC0718 - needed, submitted ref DIT 1 0001 with comments linked to the Launch
AC0719 - Plan. ref DIT 1 0001
AC0721 - ..
AC0722 - On 991222 Doug's 1992 paper on Groupware called for an OHS system that
AC0723 - enables links in email to specific addresses within sources on the
AC0724 - Internet. ref SDS 15 1Z61
AC0726 - ..
AC0727 - On 000405 Doug wanted addressability in email, which is required in
AC0728 - order for people to link communications. ref SDS 28 2484 His letter
AC0729 - today provides and demonstrates addressability using a system of HTML
AC0730 - links at the end of each paragraph to anchors at the beginning of
AC0731 - paragraphs. Visibility of the link is highlighted by the color
AC0732 - purple, which has led engineers in the OHS/DKR group to calling Doug's
AC0733 - system "Purple Numbers," which was used for Augment NLS program that
AC0734 - Doug developed at SRI in the 1960s, as explained on 001012.
AC0735 - ref SDS 57 9F6W
AC0737 - ..
AC0738 - [On 001027 Doug reported nobody has done this. ref SDS 64 0001
AC0740 - ..
AC0741 - [On 001031 still no analysis of proposal. ref SDS 67 I67L
AC0743 - ..
AC0744 - [On 001110 set objective to move from an information to a
AC0745 - knowledge culture, which requires citing and linking the
AC0746 - record, as Doug proposes today. ref SDS 71 CH4M
AC0748 - ..
AC0749 - [On 001111 report on meeting to introduce new team member does
AC0750 - not link to the record. ref SDS 72 5Y6G
AC0752 - ..
AC0753 - [On 001114 OHS team meeting proposes changes to "original"
AC0754 - definitions of system components (Hyperscope, OHS), and does
AC0755 - not cite nor link to the Launch Plan. ref SDS 73 4FYW
AC0757 - ..
AC0758 - [On 001116 explain developing culture of knowledge requires
AC0759 - following Doug's request for linking to relevant information.
AC0760 - ref SDS 75 T69N
AC0762 - ..
AC0763 - [On 001116 Adam Chyer submits definitions of OHS/DKR terms
AC0764 - based on discussion with Doug; does not cite Doug's documents,
AC0765 - which he recommended on 000115. ref SDS 76 D3AK
AC0767 - ..
AC0768 - [On 001116 Jack Park and Paul Fernhout report SDS accomplishes
AC0769 - Doug's requirement to link the record. ref SDS 75 0001
AC0771 - ..
AC0772 - [On 001121 offer sell SDS to team so linking can be
AC0773 - accomplished. ref SDS 78 0001
AC0775 - ..
AC0776 - [On 001126 Eugene Kim proposes that the team learn KM by using
AC0777 - existing tools to link the record as Doug requests. ref SDS 80
AC0778 - XV8L Grant Bowman says new tools are needed to support KM.
AC0779 - ref SDS 80 X8PW
AC0781 - ..
AC0782 - [On 001204 Doug submits a letter that uses anchors in the
AC0783 - Launch Plan. ref SDS 82 8O4L
AC0785 - ..
AC0786 - [On 001214 letter to Judge Douglas provides example of Doug's
AC0787 - idea. ref SDS 83 0001 Same day, Jack Park proposes Qualitative
AC0788 - Process Theory to apply use cases for inventing OHS.
AC0789 - ref SDS 84 0001
AC0791 - ..
AC0792 - [On 001216 Frode Hegland proposes webmail to accomplish
AC0793 - alignment Doug requests today. ref SDS 85 YK9K
AC0795 - ..
AC0796 - [On 001216 Nicholas Carroll proposes team ask Doug questions
AC0797 - about the launch plan by citing to specific paragraphs.
AC0798 - ref SDS 86 0X4I
AC0800 - ..
AC0801 - [On 001231 engineer not associated with DKR project cites
AC0802 - record using anchors. ref SDS 91 MT6J
AC0804 - ..
AC0805 - [On 010122 new Browsup technology facilitates linking the
AC0806 - record. ref SDS 96 0001
AC0808 - ..
AC0809 - [On 010131 Eugene Kim submits OHS requirements with anchors and
AC0810 - hopes people will use these for linking to Eugene's documents
AC0811 - in the manner requested today by Doug. ref SDS 98 MM9M
AC0813 - ..
AC0814 - [On 011113 Henry van Eyken submits a letter with a reference to
AC0815 - an Internet resource that has an anchor. ref SDS B3 QO3H
AC0817 - ..
AC0818 - [On 020729 Pat Lincoln suggested notifying Doug that SDS
AC0819 - applied a form of purple numbers. ref SDS B5 G43K
AC0821 - ..
AC0822 - [On 020820 Murray Altheim reported people fail to use
AC0823 - explicit links, ref SDS B1 UV6G, because accuracy for
AC0824 - communication takes too much effort without SDS, ref SDS B0
AC0825 - VN6H; experts who promoted purple numbers all seem to have
AC0826 - given up adding granular addressability for working
AC0827 - intelligently. ref SDS B1 0K64
AC0829 - ..
AC0830 - [On 070831 report purple numbers abandoned because using
AC0831 - explicit links to improve accuracy of daily work takes too
AC0832 - much time finding sources to link. ref SDS C2 FM3F
AC0834 - ..
AC0835 - This is a key step in fostering a culture of knowledge that is
AC0836 - essential for advancing beyond information technology (IT), as
AC0837 - discussed with Doug on 000327, ref SDS 25 4420, and set out in the
AC0838 - letter to Pat Lincoln on 001011 proposing research projects.
AC0839 - ref SDS 56 0001 It supports alignment and traceability to
AC0840 - original sources, required by ISO criteria reviewed on 950721,
AC0841 - ref SDS 5 1740, and noted in the record on 001017. ref SDS 60 01DP
AC0843 - ..
AC0844 - [On 010114 case study illustrates SDS records on the Internet
AC0845 - enables people to increase competence for solving complex
AC0846 - problems by applying lessons of the past available through a
AC0847 - connected record that Doug proposes. ref SDS 94 0001
AC0849 - ..
AC0850 - Accomplishing this requirement takes leadership to help people
AC0851 - learn the process and benefits of making connections, which
AC0852 - presents challenges for open source development called out in the
AC0853 - plan, ref DRT 2 015G, because open source is a leaderless process.
AC0854 - For example...
AC0856 - ..
AC0857 - Paul Fernhout advised on 000831 that open source thrives in an
AC0858 - environment of empowerment that is fun. ref SDS 49 2G7I
AC0860 - ..
AC0861 - Henry van Eykan noted on 000926 that making connections takes
AC0862 - diligence, ref SDS 52 004M On 000614 Eric Armstrong noted
AC0863 - that playing DKR, i.e., performing KM, is tricky and takes
AC0864 - discipline. ref SDS 41 IH7I
AC0866 - ..
AC0867 - Grant Bowman explained on 001012 the synergy in open source
AC0868 - development comes from people doing what they want.
AC0869 - ref SDS 57 B4P2
AC0871 - ..
AC0872 - Eric Armstrong reported on 000824 that making connections is
AC0873 - not fun; he hates links into the archive. ref SDS 47 7O9I
AC0875 - ..
AC0876 - Linking to original sources creates knowledge that brings
AC0877 - accountability, which people fear and hate, reported on
AC0878 - 980405. ref SDS 10 5065
AC0880 - ..
AC0881 - Strong cultural pressures resist using "intelligence" in the
AC0882 - work place, reported on 990527, ref SDS 11 1233, reviewed
AC0883 - again on 991108. ref SDS 13 1092
AC0885 - ..
AC0886 - Accomplishing Doug's request today for contributors to use links
AC0887 - in the launch plan, requires overcoming feel good management
AC0888 - (defined on 911123, ref SDS 1 1331) that permeates the work place,
AC0889 - discussed in the record of the meeting at SRI on 001017.
AC0890 - ref SDS 60 AE7F The record shows Open source contributors are
AC0891 - empowered to have fun doing what they want, and hoping synergy
AC0892 - will prevail over diligence.
AC0894 - ..
AC0895 - [On 001027 Doug reported nobody has done this. ref SDS 64 0001
AC0897 - ..
AC0898 - [On 001028 an example where links to context were omitted.
AC0899 - ref SDS 66 O66I
AC0901 - ..
AC0902 - [On 001126 Eugene calls for the team to use anchors for links,
AC0903 - but does not provide links. ref SDS 80 XV8L
AC0905 - ..
AC0906 - [On 010131 Eugene provides OHS requirements with anchors and
AC0907 - hopes others will use them for linking, but Eugene does not
AC0908 - provide any links. ref SDS 98 MM9M
AC0910 - ..
AC0911 - A letter on 001004 presented the opportunity of having fun making
AC0912 - connections that save time and money, which people care about.
AC0913 - Creating connections of cause and effect is a new way of working
AC0914 - that improves daily work so people are more effective by having
AC0915 - fun, rather than exercise greater diligence. ref SDS 54 6N9G
AC0917 - ..
AC0918 - Experience from 000405 when Doug first called for linking the
AC0919 - record, shows there has been no progress on this new way of
AC0920 - working.
AC0922 - ..
AC0923 - The record indicates people want to be effective using current
AC0924 - skills, rather than investing time to improve skills for saving
AC0925 - time and money. Learning a new way of working that is more
AC0926 - effective doesn't make "common sense," because it conflicts with
AC0927 - experience that forms habits and paradigms about correlations
AC0928 - between cause and effect, i.e., knowledge. Changing perspective
AC0929 - and physical motions we already know is, therefore, awkward and
AC0930 - hard to remember.
AC0932 - ..
AC0933 - It takes diligence to change work habits by overcoming boundaries
AC0934 - forged by biology, reviewed on 921205 discussing Stephen Covey's
AC0935 - work. ref SDS 2 4803 That's not fun, particularly if the rewards
AC0936 - are deferred.
AC0938 - ..
AC0939 - We have to continue doing things that initially seem like they are
AC0940 - not be fun, nor rewarding, long enough to acquire new skills, that
AC0941 - turn out to be fun and bring bigger rewards. But, doing things
AC0942 - that don't make sense for an extended period in hopes of having
AC0943 - fun in the future, and gaining deferred rewards of "knowledge," is
AC0944 - prospectively not fun in the moment.
AC0946 - ..
AC0947 - This poses an innovation loop discussed with Pat Lincoln on
AC0948 - 000711, ref SDS 44 QJ9O, and previously with Doug on 000327.
AC0949 - ref SDS 25 4420 KM requires diligence to do things we don't
AC0950 - understand, and so don't feel good, long enough to gain
AC0951 - understanding, so we feel better.
AC0953 - ..
AC0954 - Open Source development in particular entails having fun doing
AC0955 - what people want, as related on 001012. ref SDS 57 PT5M
AC0957 - ..
AC0958 - Accordingly, Open Source development directly conflicts with the
AC0959 - requirements of creating Knowledge Management capability, as
AC0960 - evidenced by Doug's request today that is not being performed by
AC0961 - Open Source advocates. ref DRT 2 00VU This conclusion is
AC0962 - supported by the history of the project.
AC0964 - ..
AC0965 - Additionally, there seems to be a signficant psychological barrier
AC0966 - that prevents people from linking to the record, since the process
AC0967 - uses existing skills, it is easy, fun and rewarding. This record
AC0968 - shows that people likely have to be paid in order to add links
AC0969 - that improve the work for saving time and money.
AC0971 - ..
AC0972 - Over the past 10 months approximately 100 letters have been
AC0973 - submitted to the SRI team with links to facilitate communication.
AC0974 - Cultural resistance to using links is evident from the record
AC0975 - showing that over the entire 10 months, no contributor has ever
AC0976 - cited a link. In a letter on 000223, Doug indirectly explained
AC0977 - contributors refuse to use links, because there is not enough
AC0978 - bandwidth, i.e., time. ref SDS 21 3774 More recently, Pat Lincoln
AC0979 - has been too busy to review the record on 001017, ref SDS 59 0001,
AC0980 - and noted that other top people are even busier than he is.
AC0982 - ..
AC0983 - [On 001027 Doug reported nobody has done this. ref SDS 64 0001
AC0985 - ..
AC0986 - This shows the importance of time that prevents adopting stronger
AC0987 - work practice. Presently it is faster and easier for people to
AC0988 - extract text and comment out of context, rather than link to
AC0989 - context. Dave Vannier commented at Intel on 960627 that it takes
AC0990 - time to create links, ref SDS 7 2370; so it doesn't seem practical
AC0991 - to use that method, regardless of how much money it saves, because
AC0992 - savings occur in the future, and time must be expended now. That's
AC0993 - risky, and its not fun. Open Source folks "just wanna have fun."
AC0995 - ..
AC0996 - This might be an area where an SDS-type tool can help transition
AC0997 - toward Knowledge Management, since creating links simply entails
AC0998 - pressing enter or double clicking. Reducing the time, reduces the
AC0999 - risk and therefore the level of diligince needed to use good work
AC1000 - practices. This encourages performance by a broader base of
AC1001 - people, as explained on 000920, ref SDS 52 6Q6J, citing the Boy
AC1002 - Scout napsack analogy. ref DIP 3 Y14G
AC1004 - ..
AC1005 - Doug addresses this in part in the OHS launch plan by calling for
AC1006 - significant payoff accrual early in the pursuit, ref DRT 2 LK5L,
AC1007 - and by planning to develop tools that make linking fast and easy.
AC1008 - ref SDS 0 E9G2
AC1010 - Need steps and methods for accomplishing this objective; they
AC1011 - are not clear in the launch plan.
AC1013 - ..
AC1014 - The larger issue, however, is whether anyone at this time, has
AC1015 - time and the desire to learn Knowledge Management, even when
AC1016 - facilitated by incorporating links in source material, as Doug
AC1017 - submits today (see addressability below, ref SDS 0 D3W8), or even
AC1018 - when a full range of KM tools are available to help people save
AC1019 - time and money?
AC1021 - ..
AC1022 - [On 001026 Doug reported nobody submitted comments using the
AC1023 - anchors incorporated into OHS Launch Plan. ref SDS 64 0001
AC1025 - ..
AC1026 - Is there a customer for KM, as posed on 000920, ref DIP 2 719F,
AC1027 - and again on 001004, ref DIP 4 ON5G
AC1029 - [On 010111 Doug was not aware of this idea. ref SDS 92 B2WY
AC1031 - ..
AC1032 - SRI has evidence that organizations may be willing to front some
AC1033 - money for developing technology, per above, ref SDS 0 02TX, but
AC1034 - there is no evidence those putting up funds are willing to change
AC1035 - work practices. General calls for better "collaboration" cited
AC1036 - during the meeting at SRI on 001017, ref SDS 60 014M, do not show
AC1037 - a commitment to make the front-end investment of personal time
AC1038 - required to accomplish that objective, by overcoming the learning
AC1039 - curve obstacle, and fear of accountability. Sponsors want
AC1040 - technology that enables current poor practice to succeed, rather
AC1041 - than make good practice faster and easier, as explained in the
AC1042 - letter on 000920. ref DIP 2 006P
AC1044 - ..
AC1045 - How can leadership help?
AC1047 - ..
AC1048 - Curt Carlson can send a letter to the team with links into Doug's
AC1049 - plan commenting on advantages he sees, and issues that need more
AC1050 - attention. Pat Lincoln can do the same. Call on other credible
AC1051 - sources to lead by example.
AC1053 - ..
AC1054 - Suppose they don't have time. On 990625 an article in Fortune
AC1055 - reported that executives don't have time for sound management
AC1056 - practices, which Doug calls today for the team to use. On 960910
AC1057 - there was a report that executives don't have time to think,
AC1058 - ref SDS 8 3479 We could go on... Henry Kissinger on 940609
AC1059 - reported that people don't have time to say hello, it is an Alice
AC1060 - in Wonderland world of continual of bumbling. ref SDS 3 4238 On
AC1061 - 950417 Robert MacNamera reported there wasn't enough time to avoid
AC1062 - the Vietnam War, ref SDS 4 5872, so where is the time to use links
AC1063 - in the OHS plan?
AC1065 - ..
AC1066 - Couple of ideas...
AC1068 - ..
AC1069 - Pay to Perform Knowledge Management as a Research Project
AC1070 - Pilot Testing Grows New Knowledge Overcomes Common Sense
AC1072 - KM is a research project, as proposed in the letter to Pat Lincoln
AC1073 - at SRI, ref DIP 5 UI9M, on 001011. ref SDS 56 0001
AC1075 - ..
AC1076 - Hire someone with knowledge management skills who can visit with
AC1077 - Curt, Pat, and others to prepare drafts which they can approve for
AC1078 - distribution in order to set a new standard of conduct. To jump
AC1079 - start a new work practice that saves time and money, lead by
AC1080 - doing, rather than talking.
AC1082 - [On 010111 Doug Engelbart supports this idea. ref SDS 92 B2WY
AC1084 - ..
AC1085 - [On 001220 propose Engelbart scholarship fund to pay young
AC1086 - people for performing KM. ref SDS 89 KI6O
AC1088 - ..
AC1089 - [On 010205 pilot testing BrowseUp deferred. ref SDS 99 K3RJ
AC1091 - ..
AC1092 - Pay contributors for correspondence linked to the record, so they
AC1093 - are not carrying the risk of adopting a new work practice that
AC1094 - promises better productivity, but has a limited track record.
AC1095 - Write a report on the results, like USACE did showing that adding
AC1096 - "intelligence" to information saves time and money. ref DRP 1 6172
AC1098 - [On 010114 case study illustrates SDS records on the Internet
AC1099 - enables people to increase competence for solving complex
AC1100 - problems by applying lessons of the past available through a
AC1101 - connected record that Doug proposes. ref SDS 94 0001
AC1103 - ..
AC1104 - Research entails pilot testing that pays people to do things they
AC1105 - don't want to do, and don't feel is worth the time. Research
AC1106 - showing the architecture of human thought is wired to make
AC1107 - mistakes, called meaning drift, that makes communication the
AC1108 - biggest risk in enterprise was proposed to LANL on 001013.
AC1109 - ref SDS 58 0001 Pilot testing that shows SDS reduces meaning
AC1110 - drift, ref DIP 5 0001, was proposed to SRI on 001011. ref SDS 56
AC1111 - 0001 Reporting favorable results, as USACE did on 970328,
AC1112 - ref DRP 1 6172, can move people toward Knowledge Management,
AC1113 - because it only takes a little faith to move mountains, see review
AC1114 - on 921205. ref SDS 2 8493
AC1116 - ..
AC1117 - Right now there is no faith in KM, and common sense is barring the
AC1118 - way, see NWO. ref OF 2 4235 That is why only one response to
AC1119 - Doug's call for links into the Launch Plan occurred. Only one
AC1120 - person has faith in the benefits of investing intellectual
AC1121 - capital, explained in POIMS. ref OF 1 1101 To grow a community of
AC1122 - people who have faith in adding "intelligence" to information, we
AC1123 - have to invest to discover and jump start some early adopters.
AC1125 - ..
AC1126 - This takes uncommon sense, i.e., wisdom. ref OF 2 2247
AC1128 - ..
AC1129 - Wisdom means investing for a better future.
Augment Move Records to Current Technology for OHS, 001012, Bowman
Augment History Guide OHS Development, 001025, Doug Engelbart
Augment Record Translated into OHS
AI0601 - ..
AI0602 - Augment Archive Translate to Modern Environment
AI0604 - Follow up ref SDS 57 D4K2,
AI0606 - Doug wants to translate quite a few of the AUGMENT references into
AI0607 - this new OHS browser-accessible form. E.g., a full series of User
AI0608 - Guides. ref DRT 2 CK8M
AI0610 - ..
AI0611 - [On 001220 Jack and Pat Lincoln's brother, Brien, are updating
AI0612 - Augment NLS in a Java implementation, as a prototype for creating
AI0613 - the OHS. ref SDS 89 BV3W
AI0615 - ..
AI0616 - [On 010112 progress was clarified on translating Augment to Java
AI0617 - using open source management. ref SDS 93 0001
AI0619 - ..
AI0620 - On 001012 Grant Bowman cited this action item, ref SDS 57 AL9J, to
AI0621 - build on the history of Augment, which Eric Armstrong recommended
AI0622 - on 000424. ref SDS 30 0786 Grant mentioned Doug's concern that the
AI0623 - complexity of the record, hampers this objective. ref SDS 57 D4K2
AI0625 - ..
AI0626 - Accordingly, this is a major OHS objective, to get Doug's writings
AI0627 - into a form where they can be used for research, and incorporated
AI0628 - into the daily work stream to guide OHS development. This is core
AI0629 - bootstrap strategy, and sound management practice, i.e., to rely on
AI0630 - the record, rather than guess and gossip, hunch and hope.
AI0632 - ..
AI0633 - During the meeting at SRI on 001017 Grant reported that Doug would
AI0634 - be putting Augment history on the web site, using Eugene's
AI0635 - Augment-to-HTML converter and gateway, ref SDS 60 PC8J, confirming
AI0636 - planning on 000928. ref SDS 53 IZ6G
AI0638 - ..
AI0639 - Need examples of one or two user guides that support KM enough to
AI0640 - justify making this investment of time. Of course if someone has
AI0641 - plenty of time, then this can proceed, but bandwidth is at a
AI0642 - premium in a full employment economy, per above. ref SDS 0 MO6M
Define Knowledge, Intelligence, Distinguish Data, Information
Knowledge Management, Define
Summary Missing Explain Core Function Translate, Linking
AL0701 - ..
AL0702 - Knowledge Collection and Use is OHS Objective - Need Definition
AL0704 - The objective of OHS is to improve development and application of
AL0705 - knowledge. Many years of experience and conceptual development
AL0706 - underlie the strategic framework guiding this proposal. ref DRT 2 003W
AL0707 - Phase I calls for processing data bases holding existing working
AL0708 - knowledge of a collaborative community. ref DRT 2 01WX Phase III calls
AL0709 - for OHS capability to enable users to pursue especially high
AL0710 - performance at important parts of their knowledge processes.
AL0711 - ref DRT 2 04SP
AL0713 - ..
AL0714 - On 991222 Doug's 1992 paper proposes an OHS that seems to include the
AL0715 - current scope for a DKR, ref SDS 15 3360. Doug's more recent paper
AL0716 - "Technology Template Project," reviewed in part on 000614, separates
AL0717 - OHS from Dynamic Knowledge Capture, which describes a "repository."
AL0718 - ref SDS 41 4710 These references are not cited in the Launch Plan,
AL0719 - and no other references are provided showing the history of this work.
AL0721 - ..
AL0722 - These provisions show OHS intends to support "knowledge," as distinct
AL0723 - from information management. Data generally relates to quantity, and
AL0724 - information is a narrative explanation that relates data to context at
AL0725 - a particular time, e.g., when the email was sent, when the document
AL0726 - was prepared, the meeting was held, the phone call occurred, etc. All
AL0727 - of these events generate information. What then is knowledge? On
AL0728 - 000504 Doug indicated this issue has persisted. ref SDS 36 5555
AL0730 - ..
AL0731 - Need definition of knowledge distinguished from data, information,
AL0732 - intelligence, etc., from review on 980226. ref SDS 9 2716
AL0734 - What is the difference between "data" and "information" that
AL0735 - are in a data base, and "knowledge" in a data base?
AL0737 - ..
AL0738 - On 000120 recommended focus on this issue. ref SDS 17 5063
AL0740 - ..
AL0741 - On 000125 recommended that project launch plan define knowledge,
AL0742 - ref SDS 18 KF6M, to solve problem in IT development, that
AL0743 - programmers don't know what to program. ref SDS 18 GH4I
AL0745 - ..
AL0746 - On 000307 Doug called for a work up on "knowledge" to anchor OHS
AL0747 - objectives. ref SDS 23 4820 On 000327 Doug cited his 1972 paper
AL0748 - that discussed a "knowledge workshop" that sounds helpful.
AL0749 - ref SDS 25 3971 On 000503 Eric explained that the definition of
AL0750 - "knowledge" impacts OHS design. ref SDS 34 5033 On 000504 Eugene
AL0751 - submitted guidance on this issue. ref SDS 35 5003 Later he
AL0752 - reported on 000615 that the team decided there isn't enough
AL0753 - knowledge about available yet to settle on a useful definition.
AL0754 - ref SDS 42 6271 More recently, on 000928 Eugene disclosed that
AL0755 - deliverables are not understood. ref SDS 53 X57F
AL0757 - ..
AL0758 - [On 001116 Adam Cheyer reports definition of DKR based on
AL0759 - recent discussion with Doug. ref SDS 76 JO3F
AL0761 - ..
AL0762 - The purpose of defining knowledge is to set the bar above current
AL0763 - practice using data and information management. Without a clear
AL0764 - definition of knowledge to guide development, OHS can only assume
AL0765 - usefulness, per below. ref SDS 0 BG4N This will compound problems
AL0766 - by adding information, rather than converting it into "knowledge"
AL0767 - that saves time and money.
AL0769 - ..
AL0770 - For example, the launch plan assumes OHS capabilities would be
AL0771 - useful to almost any collaborative community, essentially as soon
AL0772 - as adequate HyperScope-application support services could be
AL0773 - provided, ref DRT 2 03KJ, which is a strong part of the plan,
AL0774 - reviewed on 001017. ref SDS 60 01DP
AL0776 - ..
AL0777 - However, since there is no DKR, nor OHS, there is no evidence to
AL0778 - support this assumption. The plan cites no other vendor, tool,
AL0779 - system nor practice in use that might be considered a precursor of
AL0780 - OHS, that supports an inference of usefulness. Therefore, the
AL0781 - claim must be grounded in a theory of knowledge that people can
AL0782 - extrapolate from experience with information management to
AL0783 - reasonably assume that knowledge management will be more useful.
ABC Improvement Implemented 3 Phase Plan
Vision OHS Architecture Launch Plan Submitted, Doug Engelbart, 001025
Core Capability Intelligence, Engine of Knowledge, SDS
DKR Needs Architecture, 000426, Jack Park
Core OHS Linking Multiple Views Translating, 001025, Doug Engelbart
AX0801 - ..
AX0802 - OHS Launch Plan Needs Summary Explanation, a Vision
AX0804 - Doug's plan proposes three steps...
AX0806 - Phase-1: OHS Launch Project: HyperScope, ref DRT 2 01UU
AX0808 - Phase-2: Maturing/Evolving the Hyperscope into full-feature OHS,
AX0809 - ref DRT 2 ON9K
AX0811 - ..
AX0812 - Phase-3: Special Evolutionary Provision: Multi-class UIS
AX0813 - Architecture and High-Performance Teams. ref DRT 2 04OO
AX0815 - ..
AX0816 - On 000129 Eric Armstrong recommended identifying a single, core
AX0817 - function as the nucleous of the project. ref SDS 19 3383 Translating
AX0818 - and linking across different computer systems and programs, seems to
AX0819 - be the core of the OHS plan. If so, or if something else is the core,
AX0820 - that should be expressly stated.
AX0822 - ..
AX0823 - The single, core function of OHS is linking. ref SDS 0 E9G2 Multiple
AX0824 - views are an important feature. ref SDS 0 A52R Hyperscope enables
AX0825 - access to legacy files. OHS will provide a single way to create, read
AX0826 - and tie everything together. MS Word already supports linking and it
AX0827 - does pictures, too. Morris says MS Word functions are available in
AX0828 - IE, so why can't that be the OHS that has addressability in email, or
AX0829 - at least a model of what to create? If that isn't enough to create
AX0830 - knowledge, then we need a stronger core function than linking.
AX0832 - ..
AX0833 - [On 001027 Paul Fernhout explains linking is useful to create a
AX0834 - knowledge base. ref SDS 65 SV9L
AX0836 - ..
AX0837 - [On 011102 report on Doug's meeting with Traction on 000322 where
AX0838 - Doug asked about stability of links. ref SDS B2 OU4M
AX0840 - ..
AX0841 - It would be helpful for the introduction to explain a three (3) phase
AX0842 - program, and how each phase is related, something like...
AX0844 - ABC improvement will be achieved in three steps.
AX0846 - a. Hyperscope technology will translate existing files for access
AX0847 - in an improved browser with strong linking and user functions.
AX0849 - ..
AX0850 - b. In Phase II, Hyperscope evolves into an OHS with functions for
AX0851 - flexible viewing and editing that support collaboration for
AX0852 - collective IQ. Open source development enables dynamically
AX0853 - improving applications where users can work solely within OHS,
AX0854 - rather than the present ad hoc, fragmentary environment that
AX0855 - impairs productivity.
AX0857 - ..
AX0858 - c. Phase III co-evolves technology with work skills to support
AX0859 - implementation of OHS across the full range of knowledge work
AX0860 - in government and enterprise, that enables continual
AX0861 - improvement under Doug Engelbart's widely acclaimed ABC
AX0862 - strategy.
Open Source Development for Unspecified Compelling Reasons
Open Source Termites Contributors Develop Own Designs Yields Stronger
Study Needed Demonstrate Open Source Best Strategy, 000601
80% Solution Typical Open Source Result
100% Solution Planning Needed for Open Source, 001017
SRI Not Convinced Open Source Best Strategy
Engelbart Convinced Open Source Best Strategy
Feel Good Management Empowerment Do What We Want
Open Source Do Something Even If Wrong
Product Design, Control Lost
Management Cannot Make Assignments
Empowerment Creativity Termite Design Open Source Rejects Management
BB1501 - ..
BB1502 - Open Source Development for Clear, Compelling Reasons
BB1503 - Phase-1: OHS Launch Project: HyperScope with Open Source Development
BB1505 - HyperScope and OHS will be Open-Source development for clear and
BB1506 - compelling reasons, stemming from the scale and rate of evolution
BB1507 - needed, and from the number of collaborative communities which need to
BB1508 - be involved, PRO-ACTIVELY. ref DRT 2 015G
BB1510 - ..
BB1511 - This is weak.
BB1513 - ...above, Paul Fernhout expects KM will be thriving market.
BB1514 - ref SDS 0 02TX
BB1516 - [On 001123 Paul reviews lack of resources for accomplishing KM
BB1517 - using open source methods. ref SDS 79 R8VB
BB1519 - ..
BB1520 - [On 010111 report slow progress on Hyperscope architecture.
BB1521 - ref SDS 92 0002
BB1523 - ..
BB1524 - [On 010216 SRI returns BrowseUp CDs; planning to develop
BB1525 - Hyperscope using Open Source methods. ref SDS A0 H57L
BB1527 - ..
BB1528 - On 000413 Mark Mitchell, who will head the OHS development team,
BB1529 - reported that open source development produces 80% solutions.
BB1530 - ref SDS 29 2124
BB1532 - ..
BB1533 - On 000601 Curt Carlson, CEO of SRI, is not convinced that Open
BB1534 - Source is the strongest strategy for developing the DKR. Doug, is
BB1535 - convinced intuitively about the importance of open source, but he
BB1536 - noted that it would be nice to have facts to back up intuition.
BB1537 - ref SDS 39 1976
BB1539 - ..
BB1540 - On 000615 Eugene Kim plan to submit facts to support intuition in
BB1541 - two weeks. ref SDS 42 1976
BB1543 - ..
BB1544 - Has the study been done; does it show compelling evidence that
BB1545 - supports open source development?
BB1547 - ..
BB1548 - How will sponsor audit requirements reported on 001017 impact open
BB1549 - source engineers? ref SDS 60 W66J
BB1551 - [On 001028 Jack Park submits information showing open source
BB1552 - methods are successful based on unsupported references to the
BB1553 - Internet. ref SDS 66 ADK2
BB1555 - ..
BB1556 - [On 001101 VA Linux encounters problems getting things done
BB1557 - using open source. ref SDS 68 HW9F
BB1559 - ..
BB1560 - [On 010111 slow progress on OHS Hyperscope. ref SDS 92 0002
BB1562 - ..
BB1563 - [On 010112 progress was clarified on translating Augment to Java
BB1564 - using open source management. ref SDS 93 0001
Hyperscope Web Browser
Intermediary Processor Operates Between Browser and Files
Hyperscope Not Editor Has More Working Power than Legacy Editors
Augment Legacy Files Hyperscope Follow Links
Assume Hyperscope Useful
Transcode Translate, 000405
Hyperscope Name of Translate/Transcode Program for OHS, Doug Engelbar
OHS Launch Plan Submitted
BJ1201 - ..
BJ1202 - Links Followed Between Legacy Files Similar to HTML
BJ1203 - Hyperscope Browser Not Editor, But More Power than Legacy Editors
BJ1205 - Follow up ref SDS 55 5RW6.
BJ1207 - HyperScope will be a lightly modified web browser supported by an
BJ1208 - "Intermediary Processor" (IP) which operates between the browser and
BJ1209 - the files or data bases holding existing working knowledge of a
BJ1210 - collaborative community. The HyperScope is not an editor. ref DRT 2
BJ1211 - 01WX
BJ1213 - ..
BJ1214 - [On 001217 Doug wants Use Cases on Hyperscope. ref SDS 87 0001
BJ1216 - ..
BJ1217 - [On 010122 BrowseUp shows Hyperscope linking features.
BJ1218 - ref SDS 96 FT9W
BJ1220 - ..
BJ1221 - [On 070904 report that Doug got funding from NSF for engineering
BJ1222 - to design and build the "hyperscope" technology; there is no
BJ1223 - record this is being used. ref SDS C3 DV5R
BJ1225 - ..
BJ1226 - On 991222 reviewed Doug's 1992 paper on OHS, ref SDS 15 3360, and
BJ1227 - explained more recently in Doug's paper Technology Template Project,
BJ1228 - reviewed in part on 000614. ref SDS 41 4710
BJ1230 - [On 001027 called Doug and discussed progress by the team on
BJ1231 - the launch plan. ref SDS 64 0001
BJ1233 - ..
BJ1234 - On 001008 Doug proposed alternate names, Hyperscope or Tscope, for
BJ1235 - this function. ref SDS 55 5RW6
BJ1237 - What is a collaborative community?
BJ1239 - Is it the Lens technology Doug cited on 001008? ref SDS 55 5RW6
BJ1241 - ..
BJ1242 - [On 001030 Jack Park found Hyperscope and Hyperlens are being
BJ1243 - using by others. ref SDS 67 ADK1
BJ1245 - ..
BJ1246 - [On 001114 Hyperscope scope reviewed, and proposed to be the
BJ1247 - "viewer", which seems to align with a browser. ref SDS 73
BJ1248 - 4FYW
BJ1250 - ..
BJ1251 - A Hyperscope user will be able to follow links into and between these
BJ1252 - "legacy" files in a manner similar to using a browser with web-based
BJ1253 - HTML files. And more, there will be numerous new capabilities and
BJ1254 - features which will give a HyperScope user considerable more
BJ1255 - flexibility and working power than users limited to standard browsers
BJ1256 - and "legacy" editors. ref DRT 2 01X5
BJ1258 - ..
BJ1259 - [On 010620 Lee Iverson submitted requirements for NODAL and
BJ1260 - CDR that calls for interoperable file system. ref SDS A7 HS4H
BJ1262 - ..
BJ1263 - Need example of "legacy" files with links that are not
BJ1264 - accessible with HTML, other than Augment, which is a major
BJ1265 - deliverable of the project, per above. ref SDS 0 V9S1
BJ1267 - ..
BJ1268 - Possibly these are spreadsheets, pictures, PDF, Powerpoint,
BJ1269 - etc.
BJ1271 - ..
BJ1272 - If Hyperscope is not an editor, how will it provide more
BJ1273 - flexibility and working power than legacy editors?
BJ1276 - ..
BJ1277 - Assume OHS Features Useful
BJ1279 - We assume OHS capabilities would be useful to almost any collaborative
BJ1280 - community, essentially as soon as adequate HyperScope-application
BJ1281 - support services could be provided. (NOTE that a qualified SRI group
BJ1282 - is explicitly set now to establish and operate such services. Optional
BJ1283 - whether arrangements for this are pre-established at outset of the
BJ1284 - "OHS-dev Project", or later when support of a particular community
BJ1285 - choose to become involved. In any event, suitable lead time needs be
BJ1286 - allowed.), ref DRT 2 03KJ
BJ1288 - [On 070904 report that Doug got funding for engineering to
BJ1289 - design and build the "hyperscope" technology; there is no
BJ1290 - record this is being used. ref SDS C3 DV5R
BJ1292 - ..
BJ1293 - The assumption of usefulness can be supported by scenarios from
BJ1294 - Augment archives showing why various features were developed,
BJ1295 - e.g., we struggled for months, years doing x, then hit on the
BJ1296 - idea of thus and so feature. This proved to very useful by
BJ1297 - saving 10 seconds 30 times a day, which for the entire team added
BJ1298 - up to $30K for a year, etc., etc.
BJ1300 - ..
BJ1301 - Usefulness needs correlation between theory of knowledge and OHS
BJ1302 - features, per above. ref SDS 0 A4U2 Proposed features empower
BJ1303 - people to create more information. What features convert
BJ1304 - information into knowledge. Where is the "intelligence" process,
BJ1305 - i.e., the engine of knowledge, that turns straw into gold?
BJ1307 - [On 010122 BrowseUp supports linking proposed for Hyperscope;
BJ1308 - there is no work product showing this improves handling of
BJ1309 - daily working information. ref SDS 96 CP7I
BJ1311 - ..
BJ1312 - For example, above Jack Park and Paul Fernhout discuss the need
BJ1313 - for associating relevant experience to make information useful.
BJ1314 - ref SDS 0 KY5K
Hyperscope Translate HTML into XML+
Translate Text to XML to HTML, Doug, Eric, 000824
Translators for Viewing Legacy Records with Hyperscope Must Be Develo
Translate Initially Files for OHS (Augment), SPC, NIH, DARPA
BN0701 - ..
BN0702 - Hyperscope Translates Files into XML+ I-File Format
BN0703 - Assume Communities will Develop Translators for OHS
BN0705 - Follow up ref SDS 47 PU5N, ref SDS 39 7238.
BN0707 - Ordinary HTTP link will be retrieved from its server and dynamically
BN0708 - "translated" into an Intermediary file (I-File) with special structure
BN0709 - and format implemented with XML+. ref DRT 2 RU6O
BN0711 - ..
BN0712 - I-File system expanded in Phase II. ref SDS 0 L2D8
BN0714 - ..
BN0715 - On 000324 Doug called for an XML editor. Does this part of OHS
BN0716 - spec for Hyperscope flow from that objective? ref SDS 24 5880
BN0718 - [On 001113 Eric Armstrong reports on meeting at Doug's house
BN0719 - where Ken Holman explains XML capabilities and design criteria
BN0720 - for translating into XML. ref SDS 72 00U3
BN0722 - ..
BN0723 - On 000601 the team planned to develop translators for viewing
BN0724 - legacy records with Hyperscope. ref SDS 39 7238
BN0726 - ..
BN0727 - On 000824 Eric reported plans for OHS architecture to translate
BN0728 - email text into into XML, then HTML. ref SDS 47 PU5N
BN0730 - ..
BN0731 - On 000928 Eugene reported completing work for Doug to translate
BN0732 - Augment. ref SDS 53 IZ6G
BN0734 - ..
BN0735 - Assumed that "translator modules" will be developed by Communities so
BN0736 - every file/db type can be processed by Hyperscope. It is expected that
BN0737 - an increasing list of customized translators will be developed as
BN0738 - different application communities extend the range of legacy files to
BN0739 - be brought into integrated HyperScope use. ref DRT 2 01TW
BN0741 - What supports these assumptions and expectations? The nominal
BN0742 - attractiveness of using OHS?
BN0744 - ..
BN0745 - On 000812 Henry van Eykan and Nicholas Carroll asked how their
BN0746 - legacy files can be translated into the OHS system? ref SDS 46
BN0747 - E9R2
BN0749 - ..
BN0750 - Does the plan today mean Henry and Nicholas have to develop
BN0751 - translators?
BN0754 - ..
BN0755 - Expanded set of HyperScope accessible "Legacy File Types
BN0757 - In principle, this manner of HyperScope access can be implemented for
BN0758 - any standard type of file or data base. The Project will establish
BN0759 - the basic implementation conventions, and proceed to develop the
BN0760 - translation and special I-File properties appropriate for a selected
BN0761 - sequence of file/db types --, ref DRT 2 016E, planning tentatively for
BN0762 - those to be used by: OHS, SPC, NIH, DARPA
BN0764 - ..
BN0765 - I-File system expanded in Phase II. ref SDS 0 L2D8
Translate Provides Anchors for Addressability
Addressability Anchors Archived Record, Engelbart, 000601
BS0501 - ..
BS0502 - Addressability Added During Translation by Hyperscope
BS0504 - Translation creates new label tags attached to many objects (e.g. each
BS0505 - paragraph), so that links serviced by the HyperScope can explicitly
BS0506 - target many objects in the file which were not addressable in their
BS0507 - "legacy" form. Ideally, every object in a file should be targetable
BS0508 - by a link whose author wants to comment specifically about that
BS0509 - object. ref DRT 2 0148
BS0511 - ..
BS0512 - On 991222 Doug's 1992 paper on Groupware called for an OHS system
BS0513 - that enables links in email to specific addresses within sources
BS0514 - on the Internet. ref SDS 15 1Z61
BS0516 - ..
BS0517 - On 000405 Doug set objective for addressability in email.
BS0518 - ref SDS 28 2484
BS0520 - ..
BS0521 - On 000601 reviewed again. ref SDS 39 2760
BS0523 - ..
BS0524 - Every paragraph in the Launch Plan has a link at the end of the
BS0525 - last sentence to the beginning of the paragraph. This facilitates
BS0526 - Doug's request today for comments linked to specific parts of the
BS0527 - Launch Plan, per above. ref SDS 0 00VU If every paragraph begins
BS0528 - with an anchor, why is a link needed from the end of the
BS0529 - paragraph? Does it serve a purpose other than to alert people
BS0530 - there is an anchor on the para, which can be determined by making
BS0531 - the anchor explicit, shown by SDS records and documents.
BS0533 - ..
BS0534 - Why are links omitted from the transmittal letter?
BS0536 - ..
BS0537 - If these links were included in the transmittal letter, how would
BS0538 - this advance the objective and usefulness of the letter?
BS0540 - [On 020820 Murray Altheim reported people fail to use
BS0541 - explicit links, ref SDS B6 UV6G, because accuracy for
BS0542 - communication takes too much effort without SDS, ref SDS B7
BS0543 - VN6H; experts who promoted purple numbers all seem to have
BS0544 - given up adding granular addressability for working
BS0545 - intelligently. ref SDS B6 0K64
BS0547 - ..
BS0548 - [On 070831 report purple numbers abandoned because using
BS0549 - explicit links to improve accuracy of daily work takes too
BS0550 - much time finding sources to link. ref SDS C2 FM3F
BY0401 - ..
BY0402 - Multiple Views Can Be Selected
BY0403 - Ontology, Catagories Require Multiple Views to Manage Context
BY0404 - Context Management Uses Multiple Views to Understand Complexity
BY0406 - HyperScope will offer a set of "transcoded viewing options" which a
BY0407 - user can selectively employ to examine that file. Simple example:
BY0408 - just show me the first line of each paragraph. ref DRT 2 0175
BY0410 - ..
BY0411 - This sounds like different ways to summarize, which is useful for
BY0412 - pattern recognition that spawns creativity.
BY0414 - On 000405 Doug proposed alternate views supported by IBM program
BY0415 - called WBI. ref SDS 28 6006
BY0417 - ..
BY0418 - On 000413 IBM gave presentation at SRI on WBI, which supports open
BY0419 - standards. ref SDS 29 5148
BY0421 - ..
BY0422 - On 000427 Jack Park gave a presentation at SRI on accomplishing
BY0423 - multiple views. ref SDS 32 4674
BY0425 - ..
BY0426 - On 000428 Eric Armstrong reviewed WBI solution. ref SDS 33 0583
BY0428 - ..
BY0429 - On 000601 Doug explained goal for multiple views. ref SDS 39 7238
BY0431 - ..
BY0432 - From past experience it is expected users will invent various ways to
BY0433 - view their files, often shifting rapidly between views just as one
BY0434 - might rotate a physical object, or shift its distance, to get a better
BY0435 - understanding of what is there. ref DRT 2 01YP
BY0437 - ..
BY0438 - It is planned to enable the option of incorporating a "view
BY0439 - specification" (viewspec) to a link so that a subsequent user will not
BY0440 - only have execution of that link take him to the desired specific file
BY0441 - location, but will also show the contents there with the specified
BY0442 - view. ref DRT 2 0199
BY0444 - ..
BY0445 - Experience shows it is useful to "view" the same information in
BY0446 - different contexts, sometimes called context management. For
BY0447 - example, on 001019 Gil Regev reported that context improves
BY0448 - understanding. ref SDS 62 TF5H
BY0450 - [On 001108 Eric Armstrong proposes that analogies aid
BY0451 - creativity; analysis indicates that alignment and assembling
BY0452 - the record in multiple views possibly supports forming
BY0453 - analogies, which would thereby aid creativity. ref SDS 70 IL6I
BY0455 - ..
BY0456 - [On 001113 Eric reports on meeting with Ken Holman who
BY0457 - discussed Topic Maps. ref SDS 72 JR5O
BY0459 - ..
BY0460 - [On 0102221 reviewed Michael Zack's paper published by the
BY0461 - Sloan Management Review in the summer of 1999 cites application
BY0462 - by TRI using "multiple views." ref SDS A2 GE8J
BY0464 - ..
BY0465 - Some authorities call for ontology to organize information into
BY0466 - "context," e.g., Jack Park on 000623. ref SDS 43 4752 Others
BY0467 - discuss semiotics, an example is Cliff Joslyn at LANL on 000713.
BY0468 - ref SDS 45 4078 Eric Armstrong is designing for categories, see
BY0469 - 000601, ref SDS 40 5933, and again on 000824, ref SDS 47 0M5I,
BY0470 - when he, also, explained his objective for KM to provide context.
BY0471 - ref SDS 47 G92D
BY0473 - ..
BY0474 - Today, Jack and Paul Fernhout discuss the organization issue,
BY0475 - which they call "ontology," as a key aspect of KM. ref SDS 0 I58G
BY0477 - ..
BY0478 - This presents strong evidence that context is an important kind of
BY0479 - "view," and organization, or ontology, is part of the solution
BY0480 - which KM can deliver.
BY0482 - ..
BY0483 - How, then, will OHS support ontology for Context Management, per
BY0484 - analysis of DKR, below? ref SDS 0 SN4J
Linking by Point and Click ie Cut and Paste
Back Link Management
Extended Addressing Conventions Enhance Linking
Link Addressability Anchors Original Docs
C50701 - ..
C50702 - Copying-Pasting HyperScope Links
C50703 - Linking Accomplished with Point and Click
C50705 - User will easily be able to install a HyperScope link (HS-Link) in any
C50706 - legacy file, targeting an explicit location in the file being viewed
C50707 - on his HyperScope. Clicking on the desired target object in a
C50708 - HyperScope "Copy mode," he can subsequently turn to the "legacy
C50709 - editor" and "Paste" the appropriate link into the legacy file. Later
C50710 - execution of that link will take any subsequent HyperScope user to the
C50711 - desired, specific location and with the specified view. ref DRT 2 028F
C50713 - ..
C50714 - This capability is very useful to enable making the connections
C50715 - Doug requests above, quickly and easily. ref SDS 0 00VU
C50717 - [On 010119 Doug plans meeting at SRI on linking technology
C50718 - developed by engineer from Israel. ref SDS 95 945L
C50720 - ..
C50721 - On 000505 Eric reported a lot of links boggle the mind.
C50722 - ref SDS 37 4524
C50724 - ..
C50725 - On 001018 Eric reports complications developing linking features.
C50726 - ref SDS 61 TP6O and ref SDS 61 V3Y1
C50728 - ..
C50729 - Fast and easy linking requires a customer that is ready, willing
C50730 - and able to perform knowledge management, per above. ref SDS 0
C50731 - 065J
C50733 - ..
C50734 - Need examples to illustrate how backlinking and extended link
C50735 - features below, contribute to Knowledge Management.
C50737 - ..
C50738 - Have any of these features ever been used?
C50740 - ..
C50741 - How much time and money are saved, and how much is understanding
C50742 - enhanced by backlinking?
C50746 - ..
C50747 - Back-Link Management
C50749 - Provision will be made to capture information about links pointing
C50750 - through the HyperScopes into a specified collection of files, to
C50751 - establish a "Back-Link Data Base" (BLDB). ref DRT 2 024G
C50753 - [On 010122 BrowseUp supports back-links. ref SDS 96 FT9W
C50755 - ..
C50756 - [On 010124 risks and legal considerations reviewed for back-links.
C50757 - ref SDS 97 00FO
C50760 - ..
C50761 - Extended addressing conventions to improve linking power
C50764 - a. Relative Addressing:
C50766 - A conventional URL with a "#label" extension can position the
C50767 - HyperScope at a given object in the target file. Extended
C50768 - conventions will enable the link to point to subordinate
C50769 - objects -- e.g., to a word in a paragraph, to an expression in
C50770 - an equation, ... ref DRT 2 02EA
C50772 - ..
C50773 - b. Indirect Linking:
C50775 - ..
C50776 - A very powerful extension to the relative addressing is a
C50777 - convention which directs the HyperScope to go to a specific
C50778 - location and then follow the link at that position -- and
C50779 - perhaps at the link's destination to do further relative
C50780 - positioning and "link following." This indirect linking
C50781 - provides very powerful functionality when users learn to
C50782 - harness it. ref DRT 2 02GC
C50784 - ..
C50785 - c. Implicit Linking:
C50787 - ..
C50788 - Example -- every word is implicitly linked to its definition in
C50789 - a dictionary; every special term is implicitly linked to its
C50790 - definition in that discipline's glossary; every instance of an
C50791 - object's name in a source-code file is implicitly linked to its
C50792 - implementation code; ...; every pronoun is implicitly linked to
C50793 - its antecedent. Special "jump" commands can be provided which
C50794 - can operate as though the term in question is explicitly linked
C50795 - to the "implicitly linked" object. (Jump to Definition, ...),
C50796 - ref DRT 2 02IB
Multiple Windows Same File Displayed
C60401 - ..
C60402 - Multiple Windows
C60404 - Same file in multiple windows -- no real limit there -- simultaneously
C60405 - allowing different positioning and different viewing portrayals of a
C60406 - given file. Any legal edit operation executed in one window is
C60407 - reflected accurately and immediately in all other of that file's
C60408 - portrayal windows. ref DRT 2 03AC
C60410 - ..
C60411 - Currently it is fairly straight forward to view the same file in
C60412 - multiple windows, and this is useful on occasion.
C60414 - ..
C60415 - Sometimes we don't want edits to be replicated and other times
C60416 - it can be helpful.
Double Click Jumps
C90501 - ..
C90502 - Non-Link Jumps
C90504 - Options offered via simple selection means
C90506 - A click in a given paragraph, not on an embedded link, would hoist
C90507 - that paragraph to the top of the window. ref DRT 2 03EE
C90509 - ..
C90510 - Click-select a given paragraph, then Jump Next, Last, First,
C90511 - Origin, ...
C90515 - ..
C90516 - Double-click Jumps
C90518 - First click indicates what jump is desired; second click can be in any
C90519 - other window, indicating where the jump-result view is to be
C90520 - portrayed. Whatever viewing spec already established in the target
C90521 - window will also prevail when the jumped-to file/location is portrayed
C90522 - there. ref DRT 2 03GF
Phase II OHS Full Features
I-File Format for OHS
UIS User Interface System Moving, Viewing, Editing Files
All Files in OHS
I-File Special Structure Hyperscope Translate XML
Technology Template Project Doug's 1998 Paper Explains OHS Tool Set,
CI1101 - ..
CI1102 - Phase-2: Maturing/Evolving the Hyperscope into full-feature OHS:
CI1104 - Evolution of the Intermediary File format will be given careful
CI1105 - attention since it is destined to become the format for the full Open
CI1106 - Hyperdocument System. ref DRT 2 04SR
CI1108 - [On 001116 Adam Cheyer submits definition of OHS based on
CI1109 - conversations with Doug. ref SDS 76 JF3F
CI1111 - ..
CI1112 - [On 001121 Froge Hedland submits OHS Overview based on
CI1113 - conversations with Doug. ref SDS 77 0001
CI1115 - ..
CI1116 - Need explanation of issues that require attention for I-File.
CI1118 - ..
CI1119 - I-File development begins in Phase I? ref SDS 0 T3D8
CI1121 - ..
CI1122 - "Evolution" from initial Hyperscope seems to imply that OHS is a
CI1123 - more robust set of tools, described above. ref SDS 0 A5U6
CI1125 - ..
CI1126 - Technology Template Project is a paper on Doug's Bootstrap web
CI1127 - site dated 980128 that seems to explain OHS as a tool set...
CI1130 - http://www.bootstrap.org/alliance-980.htm
CI1133 - ..
CI1134 - Foundational Knowledge Environment, explains Dynamic Knowledge
CI1135 - Capture that supports daily work in progress for individuals
CI1136 - and organizations, similar to the DKR....
CI1139 - http://www.bootstrap.org/alliance-980.htm#0436
CI1142 - ...as explained in Doug's 1972 paper, reviewed on 000327.
CI1145 - ..
CI1146 - An OHS "User Interface System" (UIS) will be developed to provide a
CI1147 - basic range of functions for moving, viewing and editing. ref DRT 2
CI1148 - 03NL
CI1150 - Is user interface system (UIS) the editor?
CI1152 - [On 001114 OHS scope reviewed, and proposed to be a "repository,"
CI1153 - rather than a full featured Hyperscope browser. ref SDS 73 4FYW
CI1155 - ..
CI1156 - [On 001115 discussion about OHS and DKR scope. ref SDS 74 L87F
CI1161 - ..
CI1162 - Archiving, Version Control Enable Keeping All Files in OHS
CI1163 - Users, Organizations Migrate Toward Keeping All Files in OHS
CI1165 - Provision for archiving, version control, etc. will be developed so
CI1166 - that it becomes possible to develop and maintain an evolving knowledge
CI1167 - base solely within an OHS environment -- with integrated flexibility
CI1168 - and power accumulated from the best that was accomplished via
CI1169 - HyperScope usage among the legacy files. ref DRT 2 MH7J
CI1171 - ..
CI1172 - Does this provide file management?
CI1174 - ..
CI1175 - On 001018 archiving and version control delayed development of
CI1176 - Eric's OHS.
CI1178 - ..
CI1179 - Task by task, or person by person, in almost any order and rate, users
CI1180 - can start to keep their files entirely within the OHS environment. All
CI1181 - the working material is still interlinkable, whether in OHS or legacy
CI1182 - files. ref DRT 2 03PN
CI1184 - Does this mean OHS stores files, as in a repository, which is
CI1185 - implied by Doug's 1992 paper reviewed on 991222? ref SDS 15 0784
CI1187 - ..
CI1188 - Does this mean just using an OHS software program which functions
CI1189 - specified for Hyperscope, per above, e.g., ref SDS 0 A5U6 and,
CI1190 - ref SDS 0 E9G2, to produce files stored in a DKR, discussed in
CI1191 - Phase III, below, ref SDS 0 C9WP Or, does OHS entail issues of
CI1192 - physical hardware storage selection, that be an actual
CI1193 - "repository"?
CI1195 - ..
CI1196 - [On 001115 discussion about OHS and DKR scope. ref SDS 74 L87F
CI1198 - ..
CI1199 - For example, Xanadu seems to call for a permanent address for
CI1200 - everything, which tends to require a single big custodian for
CI1201 - everybody that will be permanent. Analysis of this idea is in
CI1202 - the record on 000305. ref SDS 22 7733
CI1204 - ..
CI1205 - Who produces and controls the OHS program. Does open source mean
CI1206 - it can be customized by each user? Is there a kernel that is
CI1207 - held constant? Will this gravitate toward open standards, so
CI1208 - that vendors can compete to develop useful features?
Organize Leadership Needed Co-evolution OHS and Skills
Open Source Supports Evolution OHS Tools Government and Enterprise
Assume Hope Participating Organizations Develop Applications for OHS
CL0601 - ..
CL0602 - Government and Enterprise Co-evolve Tools and Human Systems
CL0604 - Community-development processes will start the active "co-evolution"
CL0605 - of the "Human System" and the OHS "Tool System" (as discussed at
CL0606 - length in the "Bootstrap Publications"). ref DRT 2 03RL
CL0608 - Need to expand and cite a few publications to support this
CL0609 - provision.
CL0612 - ..
CL0613 - Co-evolution OHS Skills Requires Proactive Organization, Open Source
CL0615 - For the scale of utilization that will be necessary, in number of
CL0616 - inter-operating groups, in the diversity of inter-operable knowledge
CL0617 - domains, and in the continuing changes in tools and skills, processes,
CL0618 - etc. -- it will be absolutely critical that... ref DRT 2 03SS
CL0620 - a. Tool System be as open to continuing evolution as can be
CL0621 - managed, and
CL0623 - ..
CL0624 - Viability of open source is reviewed above. ref SDS 0 BDU6
CL0626 - ..
CL0627 - b. application communities be specifically organized to
CL0628 - participate pro-actively in the Human-Tool co-evolution.
CL0630 - ..
CL0631 - Who will perform this organization and what principles,
CL0632 - criteria will guide the organization?
CL0636 - ..
CL0637 - Assume Participating Organizations Develop Applications for OHS
CL0639 - It is sincerely hoped that organizations investing in the Stage-1
CL0640 - HyperScope development and use will do so with clear intent to be
CL0641 - simultaneously readying their targeted application communities for
CL0642 - becoming pro-active, "evolutionary participants." ref DRT 2 04MQ
CL0644 - ..
CL0645 - Is this saying folks who put up money for initial Hyperscope work,
CL0646 - will independently develop applications for OHS?
CL0648 - ..
CL0649 - Need simpler explanation of actions required to ready targeted
CL0650 - application communities...
Phase III Evolutionary Provision: Multi-class UIS Architecture and Hi
Knowledge Integrator Special Tools Training Motivated
Support Teams Maintain DKR
Com Manager Role Needed for KM, Doug Engelbart
Communication Manager Saves Time So Managers Have Time to Think
Communication Manager Makes Technology Effective for Leadership
Work Role New Needed for Culture of Knowledge Co-evolve Education Alo
Knowledge Integrator Com Manager Needed for Effective DKR, Doug Engel
Com Manager Scribe Adds Intelligence to Daily Working Information
D51201 - ..
D51202 - Phase-3: Evolve Multi-class UIS Architecture, High-Performance Teams
D51204 - OHS Interface Architecture will be set up explicitly to provide for
D51205 - multiple UIS options, with a common, full-feature Application Program
D51206 - Interface (API). To support extensive capability evolution, it will
D51207 - be necessary to provide for a range of UIS options, varying in
D51208 - complexity, potential competency level, difficulty to learn, types of
D51209 - interface devices and modalities, etc.
D51211 - ..
D51212 - Support for web-connected mobile phones is one example.
D51214 - How would a telephone support knowledge management?
D51216 - ..
D51217 - Need to expand on this to demonstrate substance.
D51219 - ..
D51220 - Enable individuals, or special-role support teams, to experiment with
D51221 - interface equipment, functionality, and control options, together with
D51222 - optional special attributes of the standard Intermediary File, to
D51223 - pursue especially high performance at important parts of their
D51224 - knowledge processes. ref DRT 2 04SP
D51226 - Need example of a "knowledge process."
D51228 - ..
D51229 - Need scenario to explain this task or objective.
D51231 - ..
D51232 - How are experiments conducted, and what interface equipment,
D51233 - control options might be tested?
D51237 - ..
D51238 - Support Teams Maintain Dynamic Knowledge Repository (DKR)
D51239 - Knowledge Integrator - Motivated Use Special Equipment, Training
D51240 - Com Manager Enables Intelligence Collection and Organization
D51242 - Having this kind of exploration in any event will be necessary. Doing
D51243 - it with special extensions to the widely used OHS will be very
D51244 - important in enabling feasible migration of these tools and skills out
D51245 - into the rest of the communities. Moreover, doing this exploratory
D51246 - high-performance activity over the SAME WORKING domains amplifies that
D51247 - benefit immensely; motivated individuals can optionally acquire
D51248 - special interface equipment, take some special training, and move up
D51249 - to a "new class of user proficiency" (e.g. becoming a certified
D51250 - Class-4B Knowledge Integrator). ref DRT 2 04TX
D51252 - ..
D51253 - "Knowledge Integrator" seems awkward. "Analyst" probably works
D51254 - better.
D51256 - ..
D51257 - Seems to implement Doug's call for a new way of working, reviewed
D51258 - on 991222. ref SDS 15 3696
D51260 - ..
D51261 - Generally aligns with Communication Manager called out in NWO to
D51262 - provide new skills and management science. ref OF 2 6369
D51264 - ..
D51265 - On 000120 contributor for OHS/DKR cited meeting facilitator for a
D51266 - system called "technography" that aids collaboration, and so may
D51267 - fit some of Knowledge Integrator scope. ref SDS 17 2300
D51269 - ..
D51270 - On 960626 article reports industry is moving toward using
D51271 - librarians as knowledge navigators. ref SDS 6 R59H
D51273 - [On 001204 Doug presented this idea to NSF. ref SDS 82 8O4L
D51275 - [On 001222 Gary Johnson calls for knowledge expert.
D51276 - ref SDS 90 DW5I
D51278 - ..
D51279 - [On 010111 Doug unaware SDS applied with Communication
D51280 - Manager, supports this role. ref SDS 92 B2WY
D51282 - ..
D51283 - [On 010114 case study illustrates SDS records on the Internet
D51284 - enables people to increase competence for solving complex
D51285 - problems by applying lessons of the past available through a
D51286 - connected record that Doug proposes. ref SDS 94 0001
D51288 - ..
D51289 - [On 010916 Eric Armstrong proposes Ontologist will perform
D51290 - dialog mapping to implement system developed by Eugene Kim.
D51291 - ref SDS A9 4J4J
D51293 - ..
D51294 - [On 011004 Eugene Kim proposes appointing a librarian to
D51295 - track RFCs to improve productivity using email for discussing
D51296 - new technologies to advance OHS/DKR. ref SDS B1 JU5O
D51298 - ..
D51299 - [On 020128 discussed with Doug need for analyst role to
D51300 - manage organic subject structure. ref SDS B4 VT6L
D51302 - ..
D51303 - Need definition of knowledge to determine tasks of Knowledge
D51304 - Integrator? ref SDS 0 A4U2
D51306 - ..
D51307 - Who provides the training for Knowledge Integrator?
D51309 - On 001017 Carla and Reg assigned. ref SDS 60 01DP
D51311 - ..
D51312 - What training is required for a Knowledge Integrator?
D51314 - ..
D51315 - What does a Knowledge Integrator do?
D51317 - Does this role help others learn OHS; does the role write
D51318 - custom improvements for OHS? Or maybe search the internet
D51319 - for interesting information? What is the core task?
D51321 - ..
D51322 - Need examples of "special equipment" for Knowledge Integrator?
Support Teams Maintain DKR
Ontology Categories Missing
Search Engine Missing
DKR Difficult to Design, Not Enough Known about Knowledge, KM, 000615
DA0801 - ..
DA0802 - DKR, Collective IQ Needs Intelligence Process to Generate Knowledge
DA0804 - Dynamic Knowledge Repository (DKR) could be maintained by trained
DA0805 - Support Teams. A university might field a team to support a research
DA0806 - project; A "Knowledge Integrator" could facilitate a professional
DA0807 - society's DKR. Competitive exercises could be conducted among teams
DA0808 - from different universities -- or companies, or agencies, or countries
DA0809 - -- as part of an explicit processes to facilitate improvement in
DA0810 - "Collective IQ." ref DRT 2 04VY
DA0812 - ..
DA0813 - The launch plan needs work on this DKR section, per Jack's letter
DA0814 - on 000426. ref SDS 31 2340
DA0816 - ..
DA0817 - Recognizing need for a work role is a big step noted in reviewing
DA0818 - Doug's ideas on 991222. ref SDS 15 0883
DA0820 - ..
DA0821 - On 991222 Doug requested review of his 1992 paper "Toward High
DA0822 - Performance Organizations," ref SDS 15 3360, which sets goals for
DA0823 - "collective IQ." ref SDS 15 3360 At that time, Doug explained
DA0824 - plans for a Colloquium to encourage funding of experiments toward
DA0825 - developing technology for OHS/DKR that would implement ideas he
DA0826 - presented in SRI's 1962 proposal to Augment Human Intellect.
DA0827 - ref SDS 15 0786
DA0829 - ..
DA0830 - DKR seems to be applied here as merely a body of knowledge, e.g.,
DA0831 - engineering, medicine, farming, and so on. The Launch Plan can
DA0832 - be strengthened by indicating how stuff gets into the DKR, and
DA0833 - how it is applied to perform daily work, including to solve world
DA0834 - problems, which was set as an objective on 000120. ref SDS 17
DA0835 - 1215 and ref SDS 17 3002 Doug's transmittal letter explains
DA0836 - advantage of linking to original sources. Providing links to
DA0837 - Doug's original writings on a DKR, would help the Launch Plan
DA0838 - identify achievable results for a DKR.
DA0840 - ..
DA0841 - [On 001027 Doug commented favorably on SDS support for OHS and
DA0842 - DKR objectives. ref SDS 64 XV6F
DA0844 - ..
DA0845 - [On 001114 team meeting proposed calling the "repository" an
DA0846 - OHS. ref SDS 73 4FYW
DA0848 - ..
DA0849 - [On 001115 Adam Cheyer recommends calling the "repository" a
DA0850 - DKR, based on Doug's documents, but Adam does not cite any of
DA0851 - Doug's documents, including the Launch Plan. ref SDS 74 L87F
DA0853 - ..
DA0854 - [...analysis above indicates OHS was the "repository" of
DA0855 - knowledge in 1992 paper. ref SDS 0 J57N
DA0857 - ..
DA0858 - [On 001116 Adam Cheyer reports definition of DKR based on
DA0859 - recent discussion with Doug. ref SDS 76 JO3F
DA0861 - ..
DA0862 - DKR could also relate to an organizational group, e.g., a
DA0863 - project, a department, and it could be organic, Ford Motor,
DA0864 - Mercury Division, Accounting Department, Sales, etc.
DA0866 - ..
DA0867 - Groupings require organic subject structure, also called
DA0868 - "ontology." So it seems pretty clear that for OHS to fly it
DA0869 - needs to dig into subjects, categories, and ontology, take your
DA0870 - pick, and this is difficult to accomplish, per discussion between
DA0871 - Jack and Paul, above. ref SDS 0 KY5K
DA0873 - ..
DA0874 - In all of the functionality presented above for OHS, nothing is
DA0875 - said about assembling information, i.e., a search engine to find
DA0876 - critical details, and to assemble parts of the record showing
DA0877 - chronology of related contextual frames, sometimes called,
DA0878 - subjects, topics, categories, taxonomy, ontology, etc. Possibly
DA0879 - this is covered under Multiple Views, ref SDS 0 D6H8; or, perhaps
DA0880 - the thought is that there are plenty of search engines for the
DA0881 - Internet already, but it is not clearly set out. Moreover,
DA0882 - search engines, per se, are inadequate for managing context,
DA0883 - which is why there is a lot of fuss about ontology, semiotics and
DA0884 - other exotic stuff nobody else has developed yet.
DA0886 - ..
DA0887 - [On 010114 case study illustrates SDS records on the Internet
DA0888 - enables people to increase competence for solving complex
DA0889 - problems by applying lessons of the past available through a
DA0890 - connected record that Doug proposes. ref SDS 94 0001
DA0892 - ..
DA0893 - Doug has discussed "knowledge containers" but this is missing
DA0894 - from the launch plan. A big issue arises of how to assemble
DA0895 - information into useful chunks of information for recognizing
DA0896 - causation that yields the power of knowledge to control the
DA0897 - future.
DA0899 - [On 001113 Eric reports on meeting with Ken Holman who
DA0900 - discussed Topic Maps. ref SDS 72 JR5O