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...What is a collaborative community?
9...Need example of "legacy" files with links that are not
10...Usefulness needs correlation between theory of knowledge and OHS
11...Does the plan today mean Henry and Nicholas have to develop
12...How, then, will OHS support ontology for Context Management, per
13...Need examples to illustrate how backlinking and extended link
14...Need explanation of issues that require attention for I-File.
15...Who produces and controls the OHS program. Does open source mean
16...Need to expand and cite a few publications to support this
17...Who will perform this organization and what principles,
18...Need simpler explanation of actions required to ready targeted
19...How would a telephone support knowledge management?
20...Need example of a "knowledge process."
21..."Knowledge Integrator" seems awkward. "Analyst" probably works
CONTACTS
0202 - Bootstrap Institute O-00000735 0101
020201 - Mr. Douglas C. Engelbart, Ph.D.
SUBJECTS
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 -
4515 - ..
4516 - Summary/Objective
4517 -
451701 - Follow up ref SDS 16 0000, ref SDS 62 0000.
451702 -
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
451736 -
451737 - [On 000116 Jack Park and Paul Fernhout report SDS accomplishes
451738 - Doug's requirement to link the record. ref SDS 75 0001
451739 -
451740 - [On 001121 offer sell SDS to team so linking can be accomplished.
451741 - ref SDS 78 0001
451742 -
451743 -
451744 -
451745 -
451746 -
451747 -
451749 - ..
4518 -
4519 -
4520 - Progress
4521 -
452101 - Ontology and Engine for Topic, Graphical Maps Key Part of DKR
452102 - Experience Adds Value by Making Information Useful
452103 -
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...
452115 -
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...
452124 -
452125 -
452126 - Tool for Collaborative Evolutionary Epistomology has
452127 -
452128 -
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
452187 - ..
452188 - Paul responds that objectives (an "end") are needed to make
452189 - information useful. ref DRT 1 PR6F
452191 - ..
452192 - Paul continues...
452193 -
452194 - I would argue we have so much experience in solving problems in
452195 - certain domains we tend to know what is useful in advance -- for
452196 - example, when creating a payroll system names are useful as are
452197 - social security numbers. Obviously, most people share a common
452198 - life situation (born, eat, sleep, work, get sick, die, etc.) and
452199 - so for applications intended to cover typical human type
452200 - situations we can guess at what is most useful. ref DRT 1 LP6K
452202 - ..
452203 - [On 010425 Opencyc plans common sense ontology knowledge base
452204 - and inference engine. ref SDS A5 079K
452206 - ..
452207 - Reality Complex, and New Realities Grow Complexity
452208 -
452209 - In effect what you are saying is you can make a model of reality
452210 - without knowing the intended use of the model. ref SDS 0 LR6N
452211 - However, reality is almost infinitely detailed (down to
452212 - probability waves of subatomic particles) and almost infinite in
452213 - scale (~400 billion visible galaxies each of ~400 billion stars)
452214 - and almost infinite in time (20+ billion years back and who knows
452215 - how far forward). ref DRT 1 008J
452217 - ..
452218 - This view supports analysis in POIMS. ref OF 1 0561
452220 - ..
452221 - On 000221 Jack disclosed that ontology opens a Pandora's Box
452222 - of complexity. ref SDS 20 7455
452223 -
452224 - [On 001130 Jack proposes an engine to automatically process
452225 - links and subjects, discussed in connection with ontology.
452226 - ref SDS 81 GK8O
452228 - ..
452229 - [On 001214 Jack presents Qualitiative Process Theory to
452230 - support ideas for "firing" processes and ontology.
452231 - ref SDS 84 VN4E
452233 - ..
452234 - [On 001219 Paul expects machine intelligence using
452235 - nanotechnology and bootstrapping will become capable of
452236 - handling complexity that will overwhelm the human psyche.
452237 - ref SDS 88 UM8M
452239 - ..
452240 - [On 010217 KM researcher associates SDS with AI-like search
452241 - engine explained in a Wired Magazine article which sounds
452242 - similar to Jack's idea today. ref SDS A1 YL5F
452243 -
452245 - ..
452246 - Email Focus Technology to Augment Intelligence
452247 -
452248 - Obviously, if we are talking about modeling how email is managed
452249 - or how hypertext is managed, we all know enough about those
452250 - subjects from everyday practical experience that we can go pretty
452251 - far in building flexible models based on our gut reactions
452252 - without needing many use cases at the start. But even then, needs
452253 - may change over time. ref DRT 1 006N
452255 - ..
452256 - Managing email is equally complex, since it relates the
452257 - reality Paul cites as infinitely complex. ref SDS 0 008J
452258 -
452260 - ..
452261 - I called and talked to Jack.
452262 -
452263 - He is making good progress with his KM project. He can now
452264 - manage information from the Internet for use in his daily
452265 - work. Next, he will do this for email, so that all of his
452266 - work can be accomplished from the new system. I explained
452267 - this is a good way to develop KM by working with it every day,
452268 - per the letter to the team on 001004.
452270 - ..
452271 - Jack related researching SDS records on the Internet. He
452272 - accesses records randomly from the index, and then takes off
452273 - in an interesting direction, following links. He likes
452274 - connections to original sources with analysis, as called out
452275 - in ISO criteria, reviewed on 950721. ref SDS 5 1740 I asked
452276 - why nobody on the team discusses this aspect of KM? Jack
452277 - feels software engineers want to improve data mining so people
452278 - can find information. He feels a big weakness is that SDS
452279 - only helps communication. Jack wants SDS subject management
452280 - on the web, so he can assemble information he wants, in
452281 - addition to using SDS for communication.
452283 - ..
452284 - [On 001027 Jack volunteers comments on SDS methodology from
452285 - reviewing the record online. ref SDS 66 ADK1
452287 - ..
452288 - [On 001027 Jack comments on analysis (below, ref SDS 0
452289 - ADK1), showing open source is not effective for developing
452290 - KM. ref SDS 66 ADK1
452291 - ..
452292 - We reviewed planning to develop this capability in a
452293 - proposal to NSF on 990615, ref SDS 12 SU3F, which was turned
452294 - down on 991213, because NSF believed Rod Welch does not
452295 - understand the "knowledge management dilemma." ref SDS 14 9144
452297 - ..
452298 - Another solution is to use SDS, but that entails performing
452299 - KM. Jack explained the huge effort people made to learn
452300 - wordprocessing and spreadsheets. The market is not yet ready
452301 - to learn how to use a spreadsheet for knowledge.
452302 -
452304 - ..
452305 - Context Key Knowledge Management Criteria to Solve Complexity
452306 -
452307 - Paul quotes Jack again...
452308 -
452309 - Placeholders need context. I suppose I am arguing that a triad
452310 - is insufficient, that a forth element of the tuple (context) is
452311 - needed. ref DRT 1 014G
452313 - ..
452314 - This aligns with Gil Regev's request on 001019 who reported that
452315 - context helps understanding, but did not define either idea.
452316 - ref SDS 62 TF5H and ref SDS 62 164H
452317 -
452318 - [On 001028 Jack sent a letter that omitted links to context.
452319 - ref SDS 66 O66I
452321 - ..
452322 - Paul explains ideas for technology to support context...
452323 -
452324 - The issue is when things can be in multiple scopes. So I think as
452325 - a start, it makes it easier and more flexible to just use
452326 - additional triads to define one or more scopes for other triads.
452327 - Those scope triads can also be in scopes, although you can end
452328 - the infinite regress by assigning a default scope to triads
452329 - without any specific scope triad. So, scope then emerges out of
452330 - how triads are used. I'm not saying scope is unimportant, just
452331 - that it should be an emergent property managed by code as opposed
452332 - to built in to the structure (at least until we have more
452333 - experience with it). ref DRT 1 L54N
452334 -
452335 -
452337 - ..
452338 - Concept Requires Separate Treatment as Ontological Context
452339 -
452340 - Paul quotes Jack again...
452341 -
452342 - So, now we have a *concept* to represent. How do we do that?
452343 - With strings alone? I don't think so. When meat-space thinks
452344 - about Jo B., it conjures up images, recollections, lots of
452345 - contexts. It seems to me that there needs to be a representation
452346 - for that concept, one that, perhaps, points to all the known
452347 - contexts in which that concept plays some role. At least, when
452348 - any context uses some concept, that concept ought to be somehow
452349 - grounded somewhere. ref DRT 1 C63N
452350 -
452352 - ..
452353 - Pointrel Solves KM Issues, Working on Next Big Step
452354 - Kent, Engelbart Challenge Conventional Methods, Need Implementation
452355 -
452356 - Paul explains his Pointrel system provides a solution...
452357 - ..
452358 - I think you raise good issues, but I think the Pointrel
452359 - system or Kent's ROSE system can support them as well as or
452360 - better than anything else. ...I feel they can be dealt with in
452361 - code in the Pointrel System, but I think it less likely they can
452362 - be dealt with in a system that assumes much more in the low level
452363 - architecture. ref DRT 1 0159
452364 -
452365 - Need example of how Pointrel manages context and concepts.
452367 - ..
452368 - On 000601 Paul proposed using Pointrel to process SDS records.
452369 - ref SDS 38 0784 There are quite a few records on the web,
452370 - including this one, which he might use to demonstrate this
452371 - aspect of knowledge management.
452372 - ..
452373 - ...I don't have a big library of such complex code to do
452374 - these sorts of tasks on this flexible substrate. I am focusing on
452375 - trying to make a good first step in the right direction that
452376 - supports a good next step. There is only so much one person can
452377 - do with limited time against a background of people entrenched in
452378 - the status quo. ref DRT 1 01E5
452380 - ..
452381 - William Kent more or less got so frustrated trying to take on the
452382 - RDBMS establishment for decades to make them see and respond to
452383 - the sorts of issues he discusses in "Data & Reality" that he
452384 - ended up going into technical writing as less stressful and has
452385 - since recently retired to spend his days doing fun stuff
452386 - unrelated to computing. It is a tribute to Doug's stamina and
452387 - thick skin he's still working towards Augment despite much the
452388 - same reception. One difference is that Doug has seen some of his
452389 - more concrete ideas implemented in bits and pieces around the
452390 - world (mouse, teleconferencing, email, hypertext, etc.), whereas
452391 - the primarily more abstract truths in "Data & Reality" are still
452392 - pretty much far from the mainstream with very few
452393 - implementations. ref DRT 1 W53L
452394 -
452395 -
452396 -
452397 -
452398 -
452399 -
4524 -
SUBJECTS
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
6108 -
610901 - ..
610902 - Market for Knowledge Management Driven by Information Overload
610903 -
610904 - Paul anticipates...
610905 -
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...
610922 -
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
610941 -
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
610956 -
610957 -
610959 - ..
610960 - Open Source Avoids Competing Proprietary Solutions
610961 -
610963 - ..
610964 - Paul continues...
610965 -
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.
610993 -
610994 -
610996 - ..
610997 - Call to Jack on Xanadu and Open Source
610998 -
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.
611017 -
611018 -
611019 -
611020 -
6111 -
SUBJECTS
OHS Linking Procedures, Doug Engelbart
Linking Procedures OHS Architecture, Doug Engelbart
OHS Architecture Not Established on 001017, Eugene Kim
OHS Architecture Project Launch Submitted, Doug Engelbart, 001025
Comments Requested Using Anchors in Launch Plan
Plan Needed for Guidance
Launch Plan OHS, Doug Engelbart 001025
OHS Launch Plan Implement, Doug Engelbart
7310 -
731101 - ..
731102 - Launch Plan OHS/DKR Project Submitted by Doug Engelbart
731103 -
731104 - Received ref DRT 2 0001 from Doug Engelbart, providing links to a
731105 - broader explanation of OHS dated 001023. ref DRT 2 0002 The original
731106 - information is at...
731107 -
731108 - http://www.bootstrap.org/a2h/BI/2120.html
731110 - ..
731111 - The plan provides vision and engineering for an OHS architecture set
731112 - out by Jack Park on 000426, ref SDS 31 0304. It covers development
731113 - vectors Doug set out on 000405, ref SDS 28 2484, following the initial
731114 - meeting at SRI on 000324. ref SDS 24 5880 It does not seem to change
731115 - Eugene Kim's report on 001017 that OHS architecture will be developed
731116 - by the new team. ref SDS 60 TJ3G
731118 - ..
731119 - [On 001214 Jack Park submits analysis under Qualitiative Process
731120 - Theory that proposes a shell to invent OHS. ref SDS 84 BH6K
731122 - ..
731123 - [On 001220 Jack and Pat Lincoln's brother, Brien, are updating
731124 - Augment NLS in a Java implementation, as a prototype for creating
731125 - the OHS. ref SDS 89 BV3W
731127 - ..
731128 - [On 010917 Eugene Kim announces OHS Launch Community starting up
731129 - and invites contributors. ref SDS B0 00UU
731131 - ..
731132 - [On 060211 Jack notifies that SRI releases Open Iris that
731133 - addresses goals in OHS/DKR. ref SDS B9 ZG5K
731135 - ..
731136 - Submission of a general plan aligns with recommendations on 000125 by
731137 - Dick Karpinski. ref SDS 18 2397
731138 -
731140 - ..
731141 - Dynamic Knowledge Repository DKR Launch Plan and Scope
731142 - OHS/DKR Architecture Implements Vision for Paperless Office
731143 - Augment Intelligence Collective IQ Improve Collaboration Teamwork
731144 - Paperless Office OHS/DKR Applies Computers for Efficient Management
731145 -
731146 - Doug's launch plan explains what the project is trying to accomplish
731147 - from the first meeting at SRI on 000324. ref SDS 24 JY3F Computers
731148 - enable paperless office efficiencies to think, remember, communicate,
731149 - solving problems, discovering opportunities. OHS/DKR technology that
731150 - augments intelligence implements Doug's 1992 paper which he discussed
731151 - on 991222. ref SDS 15 3360 Leveraging mental effectiveness was in
731152 - Doug's proposal for SRI in 1962, ref SDS 15 7H5H, and cited an article
731153 - in 1945 by Vannevar Bush on using computers to organize records of
731154 - daily work for finding sources quickly, like in a library, and also
731155 - understand complexity by linking trails of associations. ref SDS 15
731156 - XS6N Doug described a dynamic knowledge repository (DKR), ref SDS 15
731157 - KI49, that builds collective IQ for better collaboration and teamwork
731158 - to solve difficult problems. ref SDS 15 SO9N Intelligence tools and
731159 - practices for Knowledge Management were called CODIK in the 1992 paper
731160 - reviewed on 991222. ref SDS 15 0786 Growth of knowledge will enable
731161 - an ABC improvement system from natural synergy between people and
731162 - technology that supports continual learning. ref SDS 15 5187 Linking
731163 - in email with granular addressability for precision access and
731164 - efficient navigation is a first step toward Doug's OHS/DKR vision
731165 - reviewed on 991222. ref SDS 15 1Z61 Goals for technology to improve
731166 - knowledge work were presented more recently in Doug's 1998 paper
731167 - "Technology Template Project," reviewed in part on 000614. ref SDS 41
731168 - 4710 These references are not cited in the Launch Plan.
731169 -
731170 - [...below, explicit links in OHS/DKR Launch Plan enable
731171 - contributors to get experience using precision access
731172 - collaborating on refinements for the plan. ref SDS 0 00VU
731174 - ..
731175 - [On 040113 executives, engineers, marketing visionaries
731176 - lose sight of purpose for knowledge management, because
731177 - leveraging intelligence to "connect the dots" for
731178 - understanding cause and effect in a complex record remains
731179 - a mysterious biological process; people cannot remember
731180 - what knowledge management is trying to accomplish.
731181 - ref SDS B8 VK4N
731183 - ..
731184 - Doug anticipates adjustments to this plan, but the initial content,
731185 - structure, and "Location Numbering" would not change. It will be
731186 - superseded with updated versions; and also supported by other planning
731187 - documents regarding deeper details and/or modifications to this, and,
731188 - also, plans associated with other phases of the larger Bootstrap
731189 - Program. ref DRT 2 IG7N
731190 -
731191 - This draft plan is primarily on project scope.
731193 - ..
731194 - Launch plan needs Work breakdown structure (WBS), budget, schedule
731195 - and organization chart, reviewed in the record on 001017.
731196 - ref SDS 60 0784 and ref SDS 60 B4S7
731198 - ..
731199 - Submitted ref DIT 1 0001 linked to this record and to the meeting at
731200 - SRI on 001017. ref SDS 60 0001 Mention in a post script that Millie
731201 - and I cannot attend the social event he is planning next week.
731202 - ref DIT 1 K69I
731203 -
731204 - [On 001027 called Doug and discussed the project. ref SDS 64 0001
731205 -
731206 -
731207 -
731208 -
731209 -
7313 -
SUBJECTS
OHS Linking Procedures, Doug Engelbart
Linking Procedures OHS Architecture, Doug Engelbart
OHS Launch Plan Submitted
Contributors Use Links in Launch Plan to Comment on Plan
Engineers Don't Want to Play DKR Do Engineering Management, 000614
Managers Don't Want to Manage Want DKR to Do Management, 000614
Diligence Hinders Acceptance SDS Context Management
Culture of Knowledge Transition from Information Culture
Link Relevant Information Using Anchors in the Record, Doug Engelbart
Anchors in Correspondence Webmail Combine Email and File Folders
Anchors Addressability for Linking Original Docs
Webmail Content Strengthened on Internet SDS Innovation Anytime Anywh
Link Comments Communication Collaboration on OHS Launch Plan to OHS L
Engelbar, Doug KM Expert Demonstrates Explicit Links Calls For Linkin
AK16 -
AK1701 - ..
AK1702 - Culture of Knowledge Essential to Learn KM
AK1703 - Wisdom Leadership Unlock the Secret of Knowledge Management
AK1704 - Innovation Loop: Open Source is Fun, Learning Requires Diligence
AK1705 - Pilot Testing Solves Innovation Loop, Shows Value of Intelligence
AK1706 -
AK1707 -
AK1708 - Explicit Links Email Granular Addressability Enable Working Efficiently
AK1709 -
AK1710 - Doug invites dialog on the plan, and requests that contributors use
AK1711 - links to specific content locations being discussed. ref DRT 2 00VU
AK1712 - The plan calls for a group at SRI to implement OHS services,
AK1713 - ref DRT 2 03KJ, which should include writing a letter that links to
AK1714 - original sources, as Doug calls out today. Doug included anchors on
AK1715 - paragraphs in the Launch Plan to facilitate linking with conventional
AK1716 - email, per below. ref SDS 0 B0WI The format of these anchors do not
AK1717 - fit SDS requirements. Since SDS automatically creates anchors where
AK1718 - needed, submitted ref DIT 1 0001 with comments linked to the Launch
AK1719 - Plan. ref DIT 1 0001
AK1721 - ..
AK1722 - On 991222 Doug's 1992 paper on Groupware called for an OHS system that
AK1723 - enables links in email to specific addresses within sources on the
AK1724 - Internet. ref SDS 15 1Z61
AK1726 - ..
AK1727 - On 000405 Doug wanted addressability in email, which is required in
AK1728 - order for people to link communications. ref SDS 28 2484 His letter
AK1729 - today provides and demonstrates addressability using a system of HTML
AK1730 - links at the end of each paragraph to anchors at the beginning of
AK1731 - paragraphs. Visibility of the link is highlighted by the color
AK1732 - purple, which has led engineers in the OHS/DKR group to calling Doug's
AK1733 - system "Purple Numbers," which was used for Augment NLS program that
AK1734 - Doug developed at SRI in the 1960s, as explained on 001012.
AK1735 - ref SDS 57 9F6W
AK1737 - ..
AK1738 - [On 001027 Doug reported nobody has done this. ref SDS 64 0001
AK1740 - ..
AK1741 - [On 001031 still no analysis of proposal. ref SDS 67 I67L
AK1743 - ..
AK1744 - [On 001110 set objective to move from an information to a
AK1745 - knowledge culture, which requires citing and linking the
AK1746 - record, as Doug proposes today. ref SDS 71 CH4M
AK1748 - ..
AK1749 - [On 001111 report on meeting to introduce new team member does
AK1750 - not link to the record. ref SDS 72 5Y6G
AK1752 - ..
AK1753 - [On 001114 OHS team meeting proposes changes to "original"
AK1754 - definitions of system components (Hyperscope, OHS), and does
AK1755 - not cite nor link to the Launch Plan. ref SDS 73 4FYW
AK1757 - ..
AK1758 - [On 001116 explain developing culture of knowledge requires
AK1759 - following Doug's request for linking to relevant information.
AK1760 - ref SDS 75 T69N
AK1762 - ..
AK1763 - [On 001116 Adam Chyer submits definitions of OHS/DKR terms
AK1764 - based on discussion with Doug; does not cite Doug's documents,
AK1765 - which he recommended on 000115. ref SDS 76 D3AK
AK1767 - ..
AK1768 - [On 001116 Jack Park and Paul Fernhout report SDS accomplishes
AK1769 - Doug's requirement to link the record. ref SDS 75 0001
AK1771 - ..
AK1772 - [On 001121 offer sell SDS to team so linking can be
AK1773 - accomplished. ref SDS 78 0001
AK1775 - ..
AK1776 - [On 001126 Eugene Kim proposes that the team learn KM by using
AK1777 - existing tools to link the record as Doug requests. ref SDS 80
AK1778 - XV8L Grant Bowman says new tools are needed to support KM.
AK1779 - ref SDS 80 X8PW
AK1781 - ..
AK1782 - [On 001204 Doug submits a letter that uses anchors in the
AK1783 - Launch Plan. ref SDS 82 8O4L
AK1785 - ..
AK1786 - [On 001214 letter to Judge Douglas provides example of Doug's
AK1787 - idea. ref SDS 83 0001 Same day, Jack Park proposes Qualitative
AK1788 - Process Theory to apply use cases for inventing OHS.
AK1789 - ref SDS 84 0001
AK1791 - ..
AK1792 - [On 001216 Frode Hegland proposes webmail to accomplish
AK1793 - alignment Doug requests today. ref SDS 85 YK9K
AK1795 - ..
AK1796 - [On 001216 Nicholas Carroll proposes team ask Doug questions
AK1797 - about the launch plan by citing to specific paragraphs.
AK1798 - ref SDS 86 0X4I
AK1800 - ..
AK1801 - [On 001231 engineer not associated with DKR project cites
AK1802 - record using anchors. ref SDS 91 MT6J
AK1804 - ..
AK1805 - [On 010122 new Browsup technology facilitates linking the
AK1806 - record. ref SDS 96 0001
AK1808 - ..
AK1809 - [On 010131 Eugene Kim submits OHS requirements with anchors and
AK1810 - hopes people will use these for linking to Eugene's documents
AK1811 - in the manner requested today by Doug. ref SDS 98 MM9M
AK1813 - ..
AK1814 - [On 011113 Henry van Eyken submits a letter with a reference to
AK1815 - an Internet resource that has an anchor. ref SDS B3 QO3H
AK1817 - ..
AK1818 - [On 020729 Pat Lincoln suggested notifying Doug that SDS
AK1819 - applied a form of purple numbers. ref SDS B5 G43K
AK1821 - ..
AK1822 - [On 020820 Murray Altheim reported people fail to use
AK1823 - explicit links, ref SDS B1 UV6G, because accuracy for
AK1824 - communication takes too much effort without SDS, ref SDS B0
AK1825 - VN6H; experts who promoted purple numbers all seem to have
AK1826 - given up adding granular addressability for working
AK1827 - intelligently. ref SDS B1 0K64
AK1829 - ..
AK1830 - [On 070831 report purple numbers abandoned because using
AK1831 - explicit links to improve accuracy of daily work takes too
AK1832 - much time finding sources to link. ref SDS C2 FM3F
AK1834 - ..
AK1835 - This is a key step in fostering a culture of knowledge that is
AK1836 - essential for advancing beyond information technology (IT), as
AK1837 - discussed with Doug on 000327, ref SDS 25 4420, and set out in the
AK1838 - letter to Pat Lincoln on 001011 proposing research projects.
AK1839 - ref SDS 56 0001 It supports alignment and traceability to
AK1840 - original sources, required by ISO criteria reviewed on 950721,
AK1841 - ref SDS 5 1740, and noted in the record on 001017. ref SDS 60 01DP
AK1843 - ..
AK1844 - [On 010114 case study illustrates SDS records on the Internet
AK1845 - enables people to increase competence for solving complex
AK1846 - problems by applying lessons of the past available through a
AK1847 - connected record that Doug proposes. ref SDS 94 0001
AK1849 - ..
AK1850 - Accomplishing this requirement takes leadership to help people
AK1851 - learn the process and benefits of making connections, which
AK1852 - presents challenges for open source development called out in the
AK1853 - plan, ref DRT 2 015G, because open source is a leaderless process.
AK1854 - For example...
AK1856 - ..
AK1857 - Paul Fernhout advised on 000831 that open source thrives in an
AK1858 - environment of empowerment that is fun. ref SDS 49 2G7I
AK1860 - ..
AK1861 - Henry van Eykan noted on 000926 that making connections takes
AK1862 - diligence, ref SDS 52 004M On 000614 Eric Armstrong noted
AK1863 - that playing DKR, i.e., performing KM, is tricky and takes
AK1864 - discipline. ref SDS 41 IH7I
AK1866 - ..
AK1867 - Grant Bowman explained on 001012 the synergy in open source
AK1868 - development comes from people doing what they want.
AK1869 - ref SDS 57 B4P2
AK1871 - ..
AK1872 - Eric Armstrong reported on 000824 that making connections is
AK1873 - not fun; he hates links into the archive. ref SDS 47 7O9I
AK1875 - ..
AK1876 - Linking to original sources creates knowledge that brings
AK1877 - accountability, which people fear and hate, reported on
AK1878 - 980405. ref SDS 10 5065
AK1880 - ..
AK1881 - Strong cultural pressures resist using "intelligence" in the
AK1882 - work place, reported on 990527, ref SDS 11 1233, reviewed
AK1883 - again on 991108. ref SDS 13 1092
AK1885 - ..
AK1886 - Accomplishing Doug's request today for contributors to use links
AK1887 - in the launch plan, requires overcoming feel good management
AK1888 - (defined on 911123, ref SDS 1 1331) that permeates the work place,
AK1889 - discussed in the record of the meeting at SRI on 001017.
AK1890 - ref SDS 60 AE7F The record shows Open source contributors are
AK1891 - empowered to have fun doing what they want, and hoping synergy
AK1892 - will prevail over diligence.
AK1894 - ..
AK1895 - [On 001027 Doug reported nobody has done this. ref SDS 64 0001
AK1897 - ..
AK1898 - [On 001028 an example where links to context were omitted.
AK1899 - ref SDS 66 O66I
AK1901 - ..
AK1902 - [On 001126 Eugene calls for the team to use anchors for links,
AK1903 - but does not provide links. ref SDS 80 XV8L
AK1905 - ..
AK1906 - [On 010131 Eugene provides OHS requirements with anchors and
AK1907 - hopes others will use them for linking, but Eugene does not
AK1908 - provide any links. ref SDS 98 MM9M
AK1910 - ..
AK1911 - A letter on 001004 presented the opportunity of having fun making
AK1912 - connections that save time and money, which people care about.
AK1913 - Creating connections of cause and effect is a new way of working
AK1914 - that improves daily work so people are more effective by having
AK1915 - fun, rather than exercise greater diligence. ref SDS 54 6N9G
AK1917 - ..
AK1918 - Experience from 000405 when Doug first called for linking the
AK1919 - record, shows there has been no progress on this new way of
AK1920 - working.
AK1922 - ..
AK1923 - The record indicates people want to be effective using current
AK1924 - skills, rather than investing time to improve skills for saving
AK1925 - time and money. Learning a new way of working that is more
AK1926 - effective doesn't make "common sense," because it conflicts with
AK1927 - experience that forms habits and paradigms about correlations
AK1928 - between cause and effect, i.e., knowledge. Changing perspective
AK1929 - and physical motions we already know is, therefore, awkward and
AK1930 - hard to remember.
AK1932 - ..
AK1933 - It takes diligence to change work habits by overcoming boundaries
AK1934 - forged by biology, reviewed on 921205 discussing Stephen Covey's
AK1935 - work. ref SDS 2 4803 That's not fun, particularly if the rewards
AK1936 - are deferred.
AK1938 - ..
AK1939 - We have to continue doing things that initially seem like they are
AK1940 - not be fun, nor rewarding, long enough to acquire new skills, that
AK1941 - turn out to be fun and bring bigger rewards. But, doing things
AK1942 - that don't make sense for an extended period in hopes of having
AK1943 - fun in the future, and gaining deferred rewards of "knowledge," is
AK1944 - prospectively not fun in the moment.
AK1946 - ..
AK1947 - This poses an innovation loop discussed with Pat Lincoln on
AK1948 - 000711, ref SDS 44 QJ9O, and previously with Doug on 000327.
AK1949 - ref SDS 25 4420 KM requires diligence to do things we don't
AK1950 - understand, and so don't feel good, long enough to gain
AK1951 - understanding, so we feel better.
AK1953 - ..
AK1954 - Open Source development in particular entails having fun doing
AK1955 - what people want, as related on 001012. ref SDS 57 PT5M
AK1957 - ..
AK1958 - Accordingly, Open Source development directly conflicts with the
AK1959 - requirements of creating Knowledge Management capability, as
AK1960 - evidenced by Doug's request today that is not being performed by
AK1961 - Open Source advocates. ref DRT 2 00VU This conclusion is
AK1962 - supported by the history of the project.
AK1964 - ..
AK1965 - Additionally, there seems to be a signficant psychological barrier
AK1966 - that prevents people from linking to the record, since the process
AK1967 - uses existing skills, it is easy, fun and rewarding. This record
AK1968 - shows that people likely have to be paid in order to add links
AK1969 - that improve the work for saving time and money.
AK1971 - ..
AK1972 - Over the past 10 months approximately 100 letters have been
AK1973 - submitted to the SRI team with links to facilitate communication.
AK1974 - Cultural resistance to using links is evident from the record
AK1975 - showing that over the entire 10 months, no contributor has ever
AK1976 - cited a link. In a letter on 000223, Doug indirectly explained
AK1977 - contributors refuse to use links, because there is not enough
AK1978 - bandwidth, i.e., time. ref SDS 21 3774 More recently, Pat Lincoln
AK1979 - has been too busy to review the record on 001017, ref SDS 59 0001,
AK1980 - and noted that other top people are even busier than he is.
AK1982 - ..
AK1983 - [On 001027 Doug reported nobody has done this. ref SDS 64 0001
AK1985 - ..
AK1986 - This shows the importance of time that prevents adopting stronger
AK1987 - work practice. Presently it is faster and easier for people to
AK1988 - extract text and comment out of context, rather than link to
AK1989 - context. Dave Vannier commented at Intel on 960627 that it takes
AK1990 - time to create links, ref SDS 7 2370; so it doesn't seem practical
AK1991 - to use that method, regardless of how much money it saves, because
AK1992 - savings occur in the future, and time must be expended now. That's
AK1993 - risky, and its not fun. Open Source folks "just wanna have fun."
AK1995 - ..
AK1996 - This might be an area where an SDS-type tool can help transition
AK1997 - toward Knowledge Management, since creating links simply entails
AK1998 - pressing enter or double clicking. Reducing the time, reduces the
AK1999 - risk and therefore the level of diligince needed to use good work
AK2000 - practices. This encourages performance by a broader base of
AK2001 - people, as explained on 000920, ref SDS 52 6Q6J, citing the Boy
AK2002 - Scout napsack analogy. ref DIP 3 Y14G
AK2004 - ..
AK2005 - Doug addresses this in part in the OHS launch plan by calling for
AK2006 - significant payoff accrual early in the pursuit, ref DRT 2 LK5L,
AK2007 - and by planning to develop tools that make linking fast and easy.
AK2008 - ref SDS 0 E9G2
AK2009 -
AK2010 - Need steps and methods for accomplishing this objective; they
AK2011 - are not clear in the launch plan.
AK2013 - ..
AK2014 - The larger issue, however, is whether anyone at this time, has
AK2015 - time and the desire to learn Knowledge Management, even when
AK2016 - facilitated by incorporating links in source material, as Doug
AK2017 - submits today (see addressability below, ref SDS 0 D3W8), or even
AK2018 - when a full range of KM tools are available to help people save
AK2019 - time and money?
AK2021 - ..
AK2022 - [On 001026 Doug reported nobody submitted comments using the
AK2023 - anchors incorporated into OHS Launch Plan. ref SDS 64 0001
AK2025 - ..
AK2026 - Is there a customer for KM, as posed on 000920, ref DIP 2 719F,
AK2027 - and again on 001004, ref DIP 4 ON5G
AK2028 -
AK2029 - [On 010111 Doug was not aware of this idea. ref SDS 92 B2WY
AK2031 - ..
AK2032 - SRI has evidence that organizations may be willing to front some
AK2033 - money for developing technology, per above, ref SDS 0 02TX, but
AK2034 - there is no evidence those putting up funds are willing to change
AK2035 - work practices. General calls for better "collaboration" cited
AK2036 - during the meeting at SRI on 001017, ref SDS 60 014M, do not show
AK2037 - a commitment to make the front-end investment of personal time
AK2038 - required to accomplish that objective, by overcoming the learning
AK2039 - curve obstacle, and fear of accountability. Sponsors want
AK2040 - technology that enables current poor practice to succeed, rather
AK2041 - than make good practice faster and easier, as explained in the
AK2042 - letter on 000920. ref DIP 2 006P
AK2044 - ..
AK2045 - How can leadership help?
AK2047 - ..
AK2048 - Curt Carlson can send a letter to the team with links into Doug's
AK2049 - plan commenting on advantages he sees, and issues that need more
AK2050 - attention. Pat Lincoln can do the same. Call on other credible
AK2051 - sources to lead by example.
AK2053 - ..
AK2054 - Suppose they don't have time. On 990625 an article in Fortune
AK2055 - reported that executives don't have time for sound management
AK2056 - practices, which Doug calls today for the team to use. On 960910
AK2057 - there was a report that executives don't have time to think,
AK2058 - ref SDS 8 3479 We could go on... Henry Kissinger on 940609
AK2059 - reported that people don't have time to say hello, it is an Alice
AK2060 - in Wonderland world of continual of bumbling. ref SDS 3 4238 On
AK2061 - 950417 Robert MacNamera reported there wasn't enough time to avoid
AK2062 - the Vietnam War, ref SDS 4 5872, so where is the time to use links
AK2063 - in the OHS plan?
AK2065 - ..
AK2066 - Couple of ideas...
AK2068 - ..
AK2069 - Pay to Perform Knowledge Management as a Research Project
AK2070 - Pilot Testing Grows New Knowledge Overcomes Common Sense
AK2071 -
AK2072 - KM is a research project, as proposed in the letter to Pat Lincoln
AK2073 - at SRI, ref DIP 5 UI9M, on 001011. ref SDS 56 0001
AK2075 - ..
AK2076 - Hire someone with knowledge management skills who can visit with
AK2077 - Curt, Pat, and others to prepare drafts which they can approve for
AK2078 - distribution in order to set a new standard of conduct. To jump
AK2079 - start a new work practice that saves time and money, lead by
AK2080 - doing, rather than talking.
AK2081 -
AK2082 - [On 010111 Doug Engelbart supports this idea. ref SDS 92 B2WY
AK2084 - ..
AK2085 - [On 001220 propose Engelbart scholarship fund to pay young
AK2086 - people for performing KM. ref SDS 89 KI6O
AK2088 - ..
AK2089 - [On 010205 pilot testing BrowseUp deferred. ref SDS 99 K3RJ
AK2091 - ..
AK2092 - Pay contributors for correspondence linked to the record, so they
AK2093 - are not carrying the risk of adopting a new work practice that
AK2094 - promises better productivity, but has a limited track record.
AK2095 - Write a report on the results, like USACE did showing that adding
AK2096 - "intelligence" to information saves time and money. ref DRP 1 6172
AK2097 -
AK2098 - [On 010114 case study illustrates SDS records on the Internet
AK2099 - enables people to increase competence for solving complex
AK2100 - problems by applying lessons of the past available through a
AK2101 - connected record that Doug proposes. ref SDS 94 0001
AK2103 - ..
AK2104 - Research entails pilot testing that pays people to do things they
AK2105 - don't want to do, and don't feel is worth the time. Research
AK2106 - showing the architecture of human thought is wired to make
AK2107 - mistakes, called meaning drift, that makes communication the
AK2108 - biggest risk in enterprise was proposed to LANL on 001013.
AK2109 - ref SDS 58 0001 Pilot testing that shows SDS reduces meaning
AK2110 - drift, ref DIP 5 0001, was proposed to SRI on 001011. ref SDS 56
AK2111 - 0001 Reporting favorable results, as USACE did on 970328,
AK2112 - ref DRP 1 6172, can move people toward Knowledge Management,
AK2113 - because it only takes a little faith to move mountains, see review
AK2114 - on 921205. ref SDS 2 8493
AK2116 - ..
AK2117 - Right now there is no faith in KM, and common sense is barring the
AK2118 - way, see NWO. ref OF 2 4235 That is why only one response to
AK2119 - Doug's call for links into the Launch Plan occurred. Only one
AK2120 - person has faith in the benefits of investing intellectual
AK2121 - capital, explained in POIMS. ref OF 1 1101 To grow a community of
AK2122 - people who have faith in adding "intelligence" to information, we
AK2123 - have to invest to discover and jump start some early adopters.
AK2125 - ..
AK2126 - This takes uncommon sense, i.e., wisdom. ref OF 2 2247
AK2128 - ..
AK2129 - Wisdom means investing for a better future.
AK2130 -
AK2131 -
AK2132 -
AK2133 -
AK2134 -
AK2135 -
AK22 -
SUBJECTS
Augment Move Records to Current Technology for OHS, 001012, Bowman
Augment History Guide OHS Development, 001025, Doug Engelbart
Augment Record Translated into OHS
AQ05 -
AQ0601 - ..
AQ0602 - Augment Archive Translate to Modern Environment
AQ0603 -
AQ0604 - Follow up ref SDS 57 D4K2,
AQ0605 -
AQ0606 - Doug wants to translate quite a few of the AUGMENT references into
AQ0607 - this new OHS browser-accessible form. E.g., a full series of User
AQ0608 - Guides. ref DRT 2 CK8M
AQ0610 - ..
AQ0611 - [On 001220 Jack and Pat Lincoln's brother, Brien, are updating
AQ0612 - Augment NLS in a Java implementation, as a prototype for creating
AQ0613 - the OHS. ref SDS 89 BV3W
AQ0615 - ..
AQ0616 - [On 010112 progress was clarified on translating Augment to Java
AQ0617 - using open source management. ref SDS 93 0001
AQ0619 - ..
AQ0620 - On 001012 Grant Bowman cited this action item, ref SDS 57 AL9J, to
AQ0621 - build on the history of Augment, which Eric Armstrong recommended
AQ0622 - on 000424. ref SDS 30 0786 Grant mentioned Doug's concern that the
AQ0623 - complexity of the record, hampers this objective. ref SDS 57 D4K2
AQ0625 - ..
AQ0626 - Accordingly, this is a major OHS objective, to get Doug's writings
AQ0627 - into a form where they can be used for research, and incorporated
AQ0628 - into the daily work stream to guide OHS development. This is core
AQ0629 - bootstrap strategy, and sound management practice, i.e., to rely on
AQ0630 - the record, rather than guess and gossip, hunch and hope.
AQ0632 - ..
AQ0633 - During the meeting at SRI on 001017 Grant reported that Doug would
AQ0634 - be putting Augment history on the web site, using Eugene's
AQ0635 - Augment-to-HTML converter and gateway, ref SDS 60 PC8J, confirming
AQ0636 - planning on 000928. ref SDS 53 IZ6G
AQ0638 - ..
AQ0639 - Need examples of one or two user guides that support KM enough to
AQ0640 - justify making this investment of time. Of course if someone has
AQ0641 - plenty of time, then this can proceed, but bandwidth is at a
AQ0642 - premium in a full employment economy, per above. ref SDS 0 MO6M
AQ0643 -
AQ0644 -
AQ0645 -
AQ0646 -
AQ0647 -
AQ07 -
SUBJECTS
Introduction
Define Knowledge, Intelligence, Distinguish Data, Information
Knowledge Management, Define
Summary Missing Explain Core Function Translate, Linking
AT06 -
AT0701 - ..
AT0702 - Knowledge Collection and Use is OHS Objective - Need Definition
AT0703 -
AT0704 - The objective of OHS is to improve development and application of
AT0705 - knowledge. Many years of experience and conceptual development
AT0706 - underlie the strategic framework guiding this proposal. ref DRT 2 003W
AT0707 - Phase I calls for processing data bases holding existing working
AT0708 - knowledge of a collaborative community. ref DRT 2 01WX Phase III calls
AT0709 - for OHS capability to enable users to pursue especially high
AT0710 - performance at important parts of their knowledge processes.
AT0711 - ref DRT 2 04SP
AT0713 - ..
AT0714 - On 991222 Doug's 1992 paper proposes an OHS that seems to include the
AT0715 - current scope for a DKR, ref SDS 15 3360. Doug's more recent paper
AT0716 - "Technology Template Project," reviewed in part on 000614, separates
AT0717 - OHS from Dynamic Knowledge Capture, which describes a "repository."
AT0718 - ref SDS 41 4710 These references are not cited in the Launch Plan,
AT0719 - and no other references are provided showing the history of this work.
AT0721 - ..
AT0722 - These provisions show OHS intends to support "knowledge," as distinct
AT0723 - from information management. Data generally relates to quantity, and
AT0724 - information is a narrative explanation that relates data to context at
AT0725 - a particular time, e.g., when the email was sent, when the document
AT0726 - was prepared, the meeting was held, the phone call occurred, etc. All
AT0727 - of these events generate information. What then is knowledge? On
AT0728 - 000504 Doug indicated this issue has persisted. ref SDS 36 5555
AT0730 - ..
AT0731 - Need definition of knowledge distinguished from data, information,
AT0732 - intelligence, etc., from review on 980226. ref SDS 9 2716
AT0733 -
AT0734 - What is the difference between "data" and "information" that
AT0735 - are in a data base, and "knowledge" in a data base?
AT0737 - ..
AT0738 - On 000120 recommended focus on this issue. ref SDS 17 5063
AT0740 - ..
AT0741 - On 000125 recommended that project launch plan define knowledge,
AT0742 - ref SDS 18 KF6M, to solve problem in IT development, that
AT0743 - programmers don't know what to program. ref SDS 18 GH4I
AT0745 - ..
AT0746 - On 000307 Doug called for a work up on "knowledge" to anchor OHS
AT0747 - objectives. ref SDS 23 4820 On 000327 Doug cited his 1972 paper
AT0748 - that discussed a "knowledge workshop" that sounds helpful.
AT0749 - ref SDS 25 3971 On 000503 Eric explained that the definition of
AT0750 - "knowledge" impacts OHS design. ref SDS 34 5033 On 000504 Eugene
AT0751 - submitted guidance on this issue. ref SDS 35 5003 Later he
AT0752 - reported on 000615 that the team decided there isn't enough
AT0753 - knowledge about available yet to settle on a useful definition.
AT0754 - ref SDS 42 6271 More recently, on 000928 Eugene disclosed that
AT0755 - deliverables are not understood. ref SDS 53 X57F
AT0757 - ..
AT0758 - [On 001116 Adam Cheyer reports definition of DKR based on
AT0759 - recent discussion with Doug. ref SDS 76 JO3F
AT0761 - ..
AT0762 - The purpose of defining knowledge is to set the bar above current
AT0763 - practice using data and information management. Without a clear
AT0764 - definition of knowledge to guide development, OHS can only assume
AT0765 - usefulness, per below. ref SDS 0 BG4N This will compound problems
AT0766 - by adding information, rather than converting it into "knowledge"
AT0767 - that saves time and money.
AT0769 - ..
AT0770 - For example, the launch plan assumes OHS capabilities would be
AT0771 - useful to almost any collaborative community, essentially as soon
AT0772 - as adequate HyperScope-application support services could be
AT0773 - provided, ref DRT 2 03KJ, which is a strong part of the plan,
AT0774 - reviewed on 001017. ref SDS 60 01DP
AT0776 - ..
AT0777 - However, since there is no DKR, nor OHS, there is no evidence to
AT0778 - support this assumption. The plan cites no other vendor, tool,
AT0779 - system nor practice in use that might be considered a precursor of
AT0780 - OHS, that supports an inference of usefulness. Therefore, the
AT0781 - claim must be grounded in a theory of knowledge that people can
AT0782 - extrapolate from experience with information management to
AT0783 - reasonably assume that knowledge management will be more useful.
AT0784 -
AT0785 -
AT0786 -
AT0787 -
AT0788 -
AT08 -
SUBJECTS
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
B507 -
B50801 - ..
B50802 - OHS Launch Plan Needs Summary Explanation, a Vision
B50803 -
B50804 - Doug's plan proposes three steps...
B50805 -
B50806 - Phase-1: OHS Launch Project: HyperScope, ref DRT 2 01UU
B50807 -
B50808 - Phase-2: Maturing/Evolving the Hyperscope into full-feature OHS,
B50809 - ref DRT 2 ON9K
B50811 - ..
B50812 - Phase-3: Special Evolutionary Provision: Multi-class UIS
B50813 - Architecture and High-Performance Teams. ref DRT 2 04OO
B50815 - ..
B50816 - On 000129 Eric Armstrong recommended identifying a single, core
B50817 - function as the nucleous of the project. ref SDS 19 3383 Translating
B50818 - and linking across different computer systems and programs, seems to
B50819 - be the core of the OHS plan. If so, or if something else is the core,
B50820 - that should be expressly stated.
B50822 - ..
B50823 - The single, core function of OHS is linking. ref SDS 0 E9G2 Multiple
B50824 - views are an important feature. ref SDS 0 A52R Hyperscope enables
B50825 - access to legacy files. OHS will provide a single way to create, read
B50826 - and tie everything together. MS Word already supports linking and it
B50827 - does pictures, too. Morris says MS Word functions are available in
B50828 - IE, so why can't that be the OHS that has addressability in email, or
B50829 - at least a model of what to create? If that isn't enough to create
B50830 - knowledge, then we need a stronger core function than linking.
B50832 - ..
B50833 - [On 001027 Paul Fernhout explains linking is useful to create a
B50834 - knowledge base. ref SDS 65 SV9L
B50836 - ..
B50837 - [On 011102 report on Doug's meeting with Traction on 000322 where
B50838 - Doug asked about stability of links. ref SDS B2 OU4M
B50840 - ..
B50841 - It would be helpful for the introduction to explain a three (3) phase
B50842 - program, and how each phase is related, something like...
B50843 -
B50844 - ABC improvement will be achieved in three steps.
B50845 -
B50846 - a. Hyperscope technology will translate existing files for access
B50847 - in an improved browser with strong linking and user functions.
B50849 - ..
B50850 - b. In Phase II, Hyperscope evolves into an OHS with functions for
B50851 - flexible viewing and editing that support collaboration for
B50852 - collective IQ. Open source development enables dynamically
B50853 - improving applications where users can work solely within OHS,
B50854 - rather than the present ad hoc, fragmentary environment that
B50855 - impairs productivity.
B50857 - ..
B50858 - c. Phase III co-evolves technology with work skills to support
B50859 - implementation of OHS across the full range of knowledge work
B50860 - in government and enterprise, that enables continual
B50861 - improvement under Doug Engelbart's widely acclaimed ABC
B50862 - strategy.
B50863 -
B50864 -
B50865 -
B50866 -
B50867 -
B509 -
SUBJECTS
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
BJ14 -
BJ1501 - ..
BJ1502 - Open Source Development for Clear, Compelling Reasons
BJ1503 - Phase-1: OHS Launch Project: HyperScope with Open Source Development
BJ1504 -
BJ1505 - HyperScope and OHS will be Open-Source development for clear and
BJ1506 - compelling reasons, stemming from the scale and rate of evolution
BJ1507 - needed, and from the number of collaborative communities which need to
BJ1508 - be involved, PRO-ACTIVELY. ref DRT 2 015G
BJ1510 - ..
BJ1511 - This is weak.
BJ1512 -
BJ1513 - ...above, Paul Fernhout expects KM will be thriving market.
BJ1514 - ref SDS 0 02TX
BJ1515 -
BJ1516 - [On 001123 Paul reviews lack of resources for accomplishing KM
BJ1517 - using open source methods. ref SDS 79 R8VB
BJ1519 - ..
BJ1520 - [On 010111 report slow progress on Hyperscope architecture.
BJ1521 - ref SDS 92 0002
BJ1523 - ..
BJ1524 - [On 010216 SRI returns BrowseUp CDs; planning to develop
BJ1525 - Hyperscope using Open Source methods. ref SDS A0 H57L
BJ1527 - ..
BJ1528 - On 000413 Mark Mitchell, who will head the OHS development team,
BJ1529 - reported that open source development produces 80% solutions.
BJ1530 - ref SDS 29 2124
BJ1532 - ..
BJ1533 - On 000601 Curt Carlson, CEO of SRI, is not convinced that Open
BJ1534 - Source is the strongest strategy for developing the DKR. Doug, is
BJ1535 - convinced intuitively about the importance of open source, but he
BJ1536 - noted that it would be nice to have facts to back up intuition.
BJ1537 - ref SDS 39 1976
BJ1539 - ..
BJ1540 - On 000615 Eugene Kim plan to submit facts to support intuition in
BJ1541 - two weeks. ref SDS 42 1976
BJ1543 - ..
BJ1544 - Has the study been done; does it show compelling evidence that
BJ1545 - supports open source development?
BJ1547 - ..
BJ1548 - How will sponsor audit requirements reported on 001017 impact open
BJ1549 - source engineers? ref SDS 60 W66J
BJ1550 -
BJ1551 - [On 001028 Jack Park submits information showing open source
BJ1552 - methods are successful based on unsupported references to the
BJ1553 - Internet. ref SDS 66 ADK2
BJ1555 - ..
BJ1556 - [On 001101 VA Linux encounters problems getting things done
BJ1557 - using open source. ref SDS 68 HW9F
BJ1559 - ..
BJ1560 - [On 010111 slow progress on OHS Hyperscope. ref SDS 92 0002
BJ1562 - ..
BJ1563 - [On 010112 progress was clarified on translating Augment to Java
BJ1564 - using open source management. ref SDS 93 0001
BJ1565 -
BJ1566 -
BJ1567 -
BJ1568 -
BJ1569 -
BJ1570 -
BJ16 -
SUBJECTS
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
Hyperscope, Transcoding
BR11 -
BR1201 - ..
BR1202 - Links Followed Between Legacy Files Similar to HTML
BR1203 - Hyperscope Browser Not Editor, But More Power than Legacy Editors
BR1204 -
BR1205 - Follow up ref SDS 55 5RW6.
BR1206 -
BR1207 - HyperScope will be a lightly modified web browser supported by an
BR1208 - "Intermediary Processor" (IP) which operates between the browser and
BR1209 - the files or data bases holding existing working knowledge of a
BR1210 - collaborative community. The HyperScope is not an editor. ref DRT 2
BR1211 - 01WX
BR1213 - ..
BR1214 - [On 001217 Doug wants Use Cases on Hyperscope. ref SDS 87 0001
BR1216 - ..
BR1217 - [On 010122 BrowseUp shows Hyperscope linking features.
BR1218 - ref SDS 96 FT9W
BR1220 - ..
BR1221 - On 991222 reivewed Doug's 1992 paper on OHS, ref SDS 15 3360, and
BR1222 - explained more recently in Doug's paper Technology Template Project,
BR1223 - reviewed in part on 000614. ref SDS 41 4710
BR1224 -
BR1225 - [On 001027 called Doug and discussed progress by the team on
BR1226 - the launch plan. ref SDS 64 0001
BR1228 - ..
BR1229 - On 001008 Doug proposed alternate names, Hyperscope or Tscope, for
BR1230 - this function. ref SDS 55 5RW6
BR1231 -
BR1232 - What is a collaborative community?
BR1233 -
BR1234 - Is it the Lens technology Doug cited on 001008? ref SDS 55 5RW6
BR1236 - ..
BR1237 - [On 001030 Jack Park found Hyperscope and Hyperlens are being
BR1238 - using by others. ref SDS 67 ADK1
BR1240 - ..
BR1241 - [On 001114 Hyperscope scope reviewed, and proposed to be the
BR1242 - "viewer", which seems to align with a browser. ref SDS 73
BR1243 - 4FYW
BR1245 - ..
BR1246 - A Hyperscope user will be able to follow links into and between these
BR1247 - "legacy" files in a manner similar to using a browser with web-based
BR1248 - HTML files. And more, there will be numerous new capabilities and
BR1249 - features which will give a HyperScope user considerable more
BR1250 - flexibility and working power than users limited to standard browsers
BR1251 - and "legacy" editors. ref DRT 2 01X5
BR1253 - ..
BR1254 - [On 010620 Lee Iverson submitted requirements for NODAL and
BR1255 - CDR that calls for interoperable file system. ref SDS A7 HS4H
BR1257 - ..
BR1258 - Need example of "legacy" files with links that are not
BR1259 - accessible with HTML, other than Augment, which is a major
BR1260 - deliverable of the project, per above. ref SDS 0 V9S1
BR1262 - ..
BR1263 - Possibly these are spreadsheets, pictures, PDF, Powerpoint,
BR1264 - etc.
BR1266 - ..
BR1267 - If Hyperscope is not an editor, how will it provide more
BR1268 - flexibility and working power than legacy editors?
BR1269 -
BR1271 - ..
BR1272 - Assume OHS Features Useful
BR1273 -
BR1274 - We assume OHS capabilities would be useful to almost any collaborative
BR1275 - community, essentially as soon as adequate HyperScope-application
BR1276 - support services could be provided. (NOTE that a qualified SRI group
BR1277 - is explicitly set now to establish and operate such services. Optional
BR1278 - whether arrangements for this are pre-established at outset of the
BR1279 - "OHS-dev Project", or later when support of a particular community
BR1280 - choose to become involved. In any event, suitable lead time needs be
BR1281 - allowed.), ref DRT 2 03KJ
BR1283 - ..
BR1284 - The assumption of usefulness can be supported by scenarios from
BR1285 - Augment archives showing why various features were developed,
BR1286 - e.g., we struggled for months, years doing x, then hit on the
BR1287 - idea of thus and so feature. This proved to very useful by
BR1288 - saving 10 seconds 30 times a day, which for the entire team added
BR1289 - up to $30K for a year, etc., etc.
BR1291 - ..
BR1292 - Usefulness needs correlation between theory of knowledge and OHS
BR1293 - features, per above. ref SDS 0 A4U2 Proposed features empower
BR1294 - people to create more information. What features convert
BR1295 - information into knowledge. Where is the "intelligence" process,
BR1296 - i.e., the engine of knowledge, that turns straw into gold?
BR1297 -
BR1298 - [On 010122 BrowseUp supports linking proposed for Hyperscope;
BR1299 - there is no work product showing this improves handling of
BR1300 - daily working information. ref SDS 96 CP7I
BR1302 - ..
BR1303 - For example, above Jack Park and Paul Fernhout discuss the need
BR1304 - for associating relevant experience to make information useful.
BR1305 - ref SDS 0 KY5K
BR1306 -
BR1307 -
BR1308 -
BR1309 -
BR1310 -
BR1311 -
BR14 -
SUBJECTS
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
BV06 -
BV0701 - ..
BV0702 - Hyperscope Translates Files into XML+ I-File Format
BV0703 - Assume Communities will Develop Translators for OHS
BV0704 -
BV0705 - Follow up ref SDS 47 PU5N, ref SDS 39 7238.
BV0706 -
BV0707 - Ordinary HTTP link will be retrieved from its server and dynamically
BV0708 - "translated" into an Intermediary file (I-File) with special structure
BV0709 - and format implemented with XML+. ref DRT 2 RU6O
BV0711 - ..
BV0712 - I-File system expanded in Phase II. ref SDS 0 L2D8
BV0714 - ..
BV0715 - On 000324 Doug called for an XML editor. Does this part of OHS
BV0716 - spec for Hyperscope flow from that objective? ref SDS 24 5880
BV0717 -
BV0718 - [On 001113 Eric Armstrong reports on meeting at Doug's house
BV0719 - where Ken Holman explains XML capabilities and design criteria
BV0720 - for translating into XML. ref SDS 72 00U3
BV0722 - ..
BV0723 - On 000601 the team planned to develop translators for viewing
BV0724 - legacy records with Hyperscope. ref SDS 39 7238
BV0726 - ..
BV0727 - On 000824 Eric reported plans for OHS architecture to translate
BV0728 - email text into into XML, then HTML. ref SDS 47 PU5N
BV0730 - ..
BV0731 - On 000928 Eugene reported completing work for Doug to translate
BV0732 - Augment. ref SDS 53 IZ6G
BV0734 - ..
BV0735 - Assumed that "translator modules" will be developed by Communities so
BV0736 - every file/db type can be processed by Hyperscope. It is expected that
BV0737 - an increasing list of customized translators will be developed as
BV0738 - different application communities extend the range of legacy files to
BV0739 - be brought into integrated HyperScope use. ref DRT 2 01TW
BV0740 -
BV0741 - What supports these assumptions and expectations? The nominal
BV0742 - attractiveness of using OHS?
BV0744 - ..
BV0745 - On 000812 Henry van Eykan and Nicholas Carroll asked how their
BV0746 - legacy files can be translated into the OHS system? ref SDS 46
BV0747 - E9R2
BV0749 - ..
BV0750 - Does the plan today mean Henry and Nicholas have to develop
BV0751 - translators?
BV0752 -
BV0754 - ..
BV0755 - Expanded set of HyperScope accessible "Legacy File Types
BV0756 -
BV0757 - In principle, this manner of HyperScope access can be implemented for
BV0758 - any standard type of file or data base. The Project will establish
BV0759 - the basic implementation conventions, and proceed to develop the
BV0760 - translation and special I-File properties appropriate for a selected
BV0761 - sequence of file/db types --, ref DRT 2 016E, planning tentatively for
BV0762 - those to be used by: OHS, SPC, NIH, DARPA
BV0764 - ..
BV0765 - I-File system expanded in Phase II. ref SDS 0 L2D8
BV0766 -
BV0767 -
BV0768 -
BV0769 -
BV0770 -
BV08 -
SUBJECTS
Translate Provides Anchors for Addressability
Addressability Anchors Archived Record, Engelbart, 000601
C004 -
C00501 - ..
C00502 - Addressability Added During Translation by Hyperscope
C00503 -
C00504 - Translation creates new label tags attached to many objects (e.g. each
C00505 - paragraph), so that links serviced by the HyperScope can explicitly
C00506 - target many objects in the file which were not addressable in their
C00507 - "legacy" form. Ideally, every object in a file should be targetable
C00508 - by a link whose author wants to comment specifically about that
C00509 - object. ref DRT 2 0148
C00511 - ..
C00512 - On 991222 Doug's 1992 paper on Groupware called for an OHS system
C00513 - that enables links in email to specific addresses within sources
C00514 - on the Internet. ref SDS 15 1Z61
C00516 - ..
C00517 - On 000405 Doug set objective for addressability in email.
C00518 - ref SDS 28 2484
C00520 - ..
C00521 - On 000601 reviewed again. ref SDS 39 2760
C00523 - ..
C00524 - Every paragraph in the Launch Plan has a link at the end of the
C00525 - last sentence to the beginning of the paragraph. This facilitates
C00526 - Doug's request today for comments linked to specific parts of the
C00527 - Launch Plan, per above. ref SDS 0 00VU If every paragraph begins
C00528 - with an anchor, why is a link needed from the end of the
C00529 - paragraph? Does it serve a purpose other than to alert people
C00530 - there is an anchor on the para, which can be determined by making
C00531 - the anchor explicit, shown by SDS records and documents.
C00533 - ..
C00534 - Why are links omitted from the transmittal letter?
C00536 - ..
C00537 - If these links were included in the transmittal letter, how would
C00538 - this advance the objective and usefulness of the letter?
C00539 -
C00540 - [On 020820 Murray Altheim reported people fail to use
C00541 - explicit links, ref SDS B6 UV6G, because accuracy for
C00542 - communication takes too much effort without SDS, ref SDS B7
C00543 - VN6H; experts who promoted purple numbers all seem to have
C00544 - given up adding granular addressability for working
C00545 - intelligently. ref SDS B6 0K64
C00547 - ..
C00548 - [On 070831 report purple numbers abandoned because using
C00549 - explicit links to improve accuracy of daily work takes too
C00550 - much time finding sources to link. ref SDS C2 FM3F
C00551 -
C00552 -
C00553 -
C00554 -
C00555 -
C006 -
SUBJECTS
Multiple Views
C603 -
C60401 - ..
C60402 - Multiple Views Can Be Selected
C60403 - Ontology, Catagories Require Multiple Views to Manage Context
C60404 - Context Management Uses Multiple Views to Understand Complexity
C60405 -
C60406 - HyperScope will offer a set of "transcoded viewing options" which a
C60407 - user can selectively employ to examine that file. Simple example:
C60408 - just show me the first line of each paragraph. ref DRT 2 0175
C60410 - ..
C60411 - This sounds like different ways to summarize, which is useful for
C60412 - pattern recognition that spawns creativity.
C60413 -
C60414 - On 000405 Doug proposed alternate views supported by IBM program
C60415 - called WBI. ref SDS 28 6006
C60417 - ..
C60418 - On 000413 IBM gave presentation at SRI on WBI, which supports open
C60419 - standards. ref SDS 29 5148
C60421 - ..
C60422 - On 000427 Jack Park gave a presentation at SRI on accomplishing
C60423 - multiple views. ref SDS 32 4674
C60425 - ..
C60426 - On 000428 Eric Armstrong reviewed WBI solution. ref SDS 33 0583
C60428 - ..
C60429 - On 000601 Doug explained goal for multiple views. ref SDS 39 7238
C60431 - ..
C60432 - From past experience it is expected users will invent various ways to
C60433 - view their files, often shifting rapidly between views just as one
C60434 - might rotate a physical object, or shift its distance, to get a better
C60435 - understanding of what is there. ref DRT 2 01YP
C60437 - ..
C60438 - It is planned to enable the option of incorporating a "view
C60439 - specification" (viewspec) to a link so that a subsequent user will not
C60440 - only have execution of that link take him to the desired specific file
C60441 - location, but will also show the contents there with the specified
C60442 - view. ref DRT 2 0199
C60444 - ..
C60445 - Experience shows it is useful to "view" the same information in
C60446 - different contexts, sometimes called context management. For
C60447 - example, on 001019 Gil Regev reported that context improves
C60448 - understanding. ref SDS 62 TF5H
C60449 -
C60450 - [On 001108 Eric Armstrong proposes that analogies aid
C60451 - creativity; analysis indicates that alignment and assembling
C60452 - the record in multiple views possibly supports forming
C60453 - analogies, which would thereby aid creativity. ref SDS 70 IL6I
C60455 - ..
C60456 - [On 001113 Eric reports on meeting with Ken Holman who
C60457 - discussed Topic Maps. ref SDS 72 JR5O
C60459 - ..
C60460 - [On 0102221 reviewed Michael Zack's paper published by the
C60461 - Sloan Management Review in the summer of 1999 cites application
C60462 - by TRI using "multiple views." ref SDS A2 GE8J
C60464 - ..
C60465 - Some authorities call for ontology to organize information into
C60466 - "context," e.g., Jack Park on 000623. ref SDS 43 4752 Others
C60467 - discuss semiotics, an example is Cliff Joslyn at LANL on 000713.
C60468 - ref SDS 45 4078 Eric Armstrong is designing for categories, see
C60469 - 000601, ref SDS 40 5933, and again on 000824, ref SDS 47 0M5I,
C60470 - when he, also, explained his objective for KM to provide context.
C60471 - ref SDS 47 G92D
C60473 - ..
C60474 - Today, Jack and Paul Fernhout discuss the organization issue,
C60475 - which they call "ontology," as a key aspect of KM. ref SDS 0 I58G
C60477 - ..
C60478 - This presents strong evidence that context is an important kind of
C60479 - "view," and organization, or ontology, is part of the solution
C60480 - which KM can deliver.
C60482 - ..
C60483 - How, then, will OHS support ontology for Context Management, per
C60484 - analysis of DKR, below? ref SDS 0 SN4J
C60485 -
C60486 -
C60487 -
C60488 -
C60489 -
C60490 -
C605 -
SUBJECTS
Linking by Point and Click ie Cut and Paste
Back Link Management
Extended Addressing Conventions Enhance Linking
Link Addressability Anchors Original Docs
CD06 -
CD0701 - ..
CD0702 - Copying-Pasting HyperScope Links
CD0703 - Linking Accomplished with Point and Click
CD0704 -
CD0705 - User will easily be able to install a HyperScope link (HS-Link) in any
CD0706 - legacy file, targeting an explicit location in the file being viewed
CD0707 - on his HyperScope. Clicking on the desired target object in a
CD0708 - HyperScope "Copy mode," he can subsequently turn to the "legacy
CD0709 - editor" and "Paste" the appropriate link into the legacy file. Later
CD0710 - execution of that link will take any subsequent HyperScope user to the
CD0711 - desired, specific location and with the specified view. ref DRT 2 028F
CD0713 - ..
CD0714 - This capability is very useful to enable making the connections
CD0715 - Doug requests above, quickly and easily. ref SDS 0 00VU
CD0716 -
CD0717 - [On 010119 Doug plans meeting at SRI on linking technology
CD0718 - developed by engineer from Israel. ref SDS 95 945L
CD0720 - ..
CD0721 - On 000505 Eric reported a lot of links boggle the mind.
CD0722 - ref SDS 37 4524
CD0724 - ..
CD0725 - On 001018 Eric reports complications developing linking features.
CD0726 - ref SDS 61 TP6O and ref SDS 61 V3Y1
CD0728 - ..
CD0729 - Fast and easy linking requires a customer that is ready, willing
CD0730 - and able to perform knowledge management, per above. ref SDS 0
CD0731 - 065J
CD0733 - ..
CD0734 - Need examples to illustrate how backlinking and extended link
CD0735 - features below, contribute to Knowledge Management.
CD0737 - ..
CD0738 - Have any of these features ever been used?
CD0740 - ..
CD0741 - How much time and money are saved, and how much is understanding
CD0742 - enhanced by backlinking?
CD0743 -
CD0744 -
CD0746 - ..
CD0747 - Back-Link Management
CD0748 -
CD0749 - Provision will be made to capture information about links pointing
CD0750 - through the HyperScopes into a specified collection of files, to
CD0751 - establish a "Back-Link Data Base" (BLDB). ref DRT 2 024G
CD0752 -
CD0753 - [On 010122 BrowseUp supports back-links. ref SDS 96 FT9W
CD0755 - ..
CD0756 - [On 010124 risks and legal considerations reviewed for back-links.
CD0757 - ref SDS 97 00FO
CD0758 -
CD0760 - ..
CD0761 - Extended addressing conventions to improve linking power
CD0762 -
CD0763 -
CD0764 - a. Relative Addressing:
CD0765 -
CD0766 - A conventional URL with a "#label" extension can position the
CD0767 - HyperScope at a given object in the target file. Extended
CD0768 - conventions will enable the link to point to subordinate
CD0769 - objects -- e.g., to a word in a paragraph, to an expression in
CD0770 - an equation, ... ref DRT 2 02EA
CD0772 - ..
CD0773 - b. Indirect Linking:
CD0775 - ..
CD0776 - A very powerful extension to the relative addressing is a
CD0777 - convention which directs the HyperScope to go to a specific
CD0778 - location and then follow the link at that position -- and
CD0779 - perhaps at the link's destination to do further relative
CD0780 - positioning and "link following." This indirect linking
CD0781 - provides very powerful functionality when users learn to
CD0782 - harness it. ref DRT 2 02GC
CD0784 - ..
CD0785 - c. Implicit Linking:
CD0787 - ..
CD0788 - Example -- every word is implicitly linked to its definition in
CD0789 - a dictionary; every special term is implicitly linked to its
CD0790 - definition in that discipline's glossary; every instance of an
CD0791 - object's name in a source-code file is implicitly linked to its
CD0792 - implementation code; ...; every pronoun is implicitly linked to
CD0793 - its antecedent. Special "jump" commands can be provided which
CD0794 - can operate as though the term in question is explicitly linked
CD0795 - to the "implicitly linked" object. (Jump to Definition, ...),
CD0796 - ref DRT 2 02IB
CD0797 -
CD0798 -
CD0799 -
CD0800 -
CD09 -
SUBJECTS
Multiple Windows Same File Displayed
CE03 -
CE0401 - ..
CE0402 - Multiple Windows
CE0403 -
CE0404 - Same file in multiple windows -- no real limit there -- simultaneously
CE0405 - allowing different positioning and different viewing portrayals of a
CE0406 - given file. Any legal edit operation executed in one window is
CE0407 - reflected accurately and immediately in all other of that file's
CE0408 - portrayal windows. ref DRT 2 03AC
CE0410 - ..
CE0411 - Currently it is fairly straight forward to view the same file in
CE0412 - multiple windows, and this is useful on occasion.
CE0414 - ..
CE0415 - Sometimes we don't want edits to be replicated and other times
CE0416 - it can be helpful.
CE0417 -
CE0418 -
CE0419 -
CE0420 -
CE0421 -
CE05 -
SUBJECTS
Non-link Jumps
Double Click Jumps
CH04 -
CH0501 - ..
CH0502 - Non-Link Jumps
CH0503 -
CH0504 - Options offered via simple selection means
CH0505 -
CH0506 - A click in a given paragraph, not on an embedded link, would hoist
CH0507 - that paragraph to the top of the window. ref DRT 2 03EE
CH0509 - ..
CH0510 - Click-select a given paragraph, then Jump Next, Last, First,
CH0511 - Origin, ...
CH0512 -
CH0513 -
CH0515 - ..
CH0516 - Double-click Jumps
CH0517 -
CH0518 - First click indicates what jump is desired; second click can be in any
CH0519 - other window, indicating where the jump-result view is to be
CH0520 - portrayed. Whatever viewing spec already established in the target
CH0521 - window will also prevail when the jumped-to file/location is portrayed
CH0522 - there. ref DRT 2 03GF
CH0523 -
CH0524 -
CH0525 -
CH0526 -
CH0527 -
CH0528 -
CH06 -
SUBJECTS
Phase II OHS Full Features
I-File Format for OHS
UIS User Interface System Moving, Viewing, Editing Files
All Files in OHS
Archiving Developed
Versioning Developed
I-File Special Structure Hyperscope Translate XML
Technology Template Project Doug's 1998 Paper Explains OHS Tool Set,
CQ10 -
CQ1101 - ..
CQ1102 - Phase-2: Maturing/Evolving the Hyperscope into full-feature OHS:
CQ1103 -
CQ1104 - Evolution of the Intermediary File format will be given careful
CQ1105 - attention since it is destined to become the format for the full Open
CQ1106 - Hyperdocument System. ref DRT 2 04SR
CQ1107 -
CQ1108 - [On 001116 Adam Cheyer submits definition of OHS based on
CQ1109 - conversations with Doug. ref SDS 76 JF3F
CQ1111 - ..
CQ1112 - [On 001121 Froge Hedland submits OHS Overview based on
CQ1113 - conversations with Doug. ref SDS 77 0001
CQ1115 - ..
CQ1116 - Need explanation of issues that require attention for I-File.
CQ1118 - ..
CQ1119 - I-File development begins in Phase I? ref SDS 0 T3D8
CQ1121 - ..
CQ1122 - "Evolution" from initial Hyperscope seems to imply that OHS is a
CQ1123 - more robust set of tools, described above. ref SDS 0 A5U6
CQ1125 - ..
CQ1126 - Technology Template Project is a paper on Doug's Bootstrap web
CQ1127 - site dated 980128 that seems to explain OHS as a tool set...
CQ1128 -
CQ1129 -
CQ1130 - http://www.bootstrap.org/alliance-980.htm
CQ1131 -
CQ1133 - ..
CQ1134 - Foundational Knowledge Environment, explains Dynamic Knowledge
CQ1135 - Capture that supports daily work in progress for individuals
CQ1136 - and organizations, similar to the DKR....
CQ1137 -
CQ1138 -
CQ1139 - http://www.bootstrap.org/alliance-980.htm#0436
CQ1140 -
CQ1141 -
CQ1142 - ...as explained in Doug's 1972 paper, reviewed on 000327.
CQ1143 -
CQ1145 - ..
CQ1146 - An OHS "User Interface System" (UIS) will be developed to provide a
CQ1147 - basic range of functions for moving, viewing and editing. ref DRT 2
CQ1148 - 03NL
CQ1149 -
CQ1150 - Is user interface system (UIS) the editor?
CQ1151 -
CQ1152 - [On 001114 OHS scope reviewed, and proposed to be a "repository,"
CQ1153 - rather than a full featured Hyperscope browser. ref SDS 73 4FYW
CQ1155 - ..
CQ1156 - [On 001115 discussion about OHS and DKR scope. ref SDS 74 L87F
CQ1157 -
CQ1158 -
CQ1159 -
CQ1161 - ..
CQ1162 - Archiving, Version Control Enable Keeping All Files in OHS
CQ1163 - Users, Organizations Migrate Toward Keeping All Files in OHS
CQ1164 -
CQ1165 - Provision for archiving, version control, etc. will be developed so
CQ1166 - that it becomes possible to develop and maintain an evolving knowledge
CQ1167 - base solely within an OHS environment -- with integrated flexibility
CQ1168 - and power accumulated from the best that was accomplished via
CQ1169 - HyperScope usage among the legacy files. ref DRT 2 MH7J
CQ1171 - ..
CQ1172 - Does this provide file management?
CQ1174 - ..
CQ1175 - On 001018 archiving and version control delayed development of
CQ1176 - Eric's OHS.
CQ1178 - ..
CQ1179 - Task by task, or person by person, in almost any order and rate, users
CQ1180 - can start to keep their files entirely within the OHS environment. All
CQ1181 - the working material is still interlinkable, whether in OHS or legacy
CQ1182 - files. ref DRT 2 03PN
CQ1183 -
CQ1184 - Does this mean OHS stores files, as in a repository, which is
CQ1185 - implied by Doug's 1992 paper reviewed on 991222? ref SDS 15 0784
CQ1187 - ..
CQ1188 - Does this mean just using an OHS software program which functions
CQ1189 - specified for Hyperscope, per above, e.g., ref SDS 0 A5U6 and,
CQ1190 - ref SDS 0 E9G2, to produce files stored in a DKR, discussed in
CQ1191 - Phase III, below, ref SDS 0 C9WP Or, does OHS entail issues of
CQ1192 - physical hardware storage selection, that be an actual
CQ1193 - "repository"?
CQ1195 - ..
CQ1196 - [On 001115 discussion about OHS and DKR scope. ref SDS 74 L87F
CQ1198 - ..
CQ1199 - For example, Xanadu seems to call for a permanent address for
CQ1200 - everything, which tends to require a single big custodian for
CQ1201 - everybody that will be permanent. Analysis of this idea is in
CQ1202 - the record on 000305. ref SDS 22 7733
CQ1204 - ..
CQ1205 - Who produces and controls the OHS program. Does open source mean
CQ1206 - it can be customized by each user? Is there a kernel that is
CQ1207 - held constant? Will this gravitate toward open standards, so
CQ1208 - that vendors can compete to develop useful features?
CQ1209 -
CQ1210 -
CQ1211 -
CQ1212 -
CQ1213 -
CQ13 -
SUBJECTS
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
CT05 -
CT0601 - ..
CT0602 - Government and Enterprise Co-evolve Tools and Human Systems
CT0603 -
CT0604 - Community-development processes will start the active "co-evolution"
CT0605 - of the "Human System" and the OHS "Tool System" (as discussed at
CT0606 - length in the "Bootstrap Publications"). ref DRT 2 03RL
CT0607 -
CT0608 - Need to expand and cite a few publications to support this
CT0609 - provision.
CT0610 -
CT0612 - ..
CT0613 - Co-evolution OHS Skills Requires Proactive Organization, Open Source
CT0614 -
CT0615 - For the scale of utilization that will be necessary, in number of
CT0616 - inter-operating groups, in the diversity of inter-operable knowledge
CT0617 - domains, and in the continuing changes in tools and skills, processes,
CT0618 - etc. -- it will be absolutely critical that... ref DRT 2 03SS
CT0619 -
CT0620 - a. Tool System be as open to continuing evolution as can be
CT0621 - managed, and
CT0623 - ..
CT0624 - Viability of open source is reviewed above. ref SDS 0 BDU6
CT0626 - ..
CT0627 - b. application communities be specifically organized to
CT0628 - participate pro-actively in the Human-Tool co-evolution.
CT0630 - ..
CT0631 - Who will perform this organization and what principles,
CT0632 - criteria will guide the organization?
CT0633 -
CT0634 -
CT0636 - ..
CT0637 - Assume Participating Organizations Develop Applications for OHS
CT0638 -
CT0639 - It is sincerely hoped that organizations investing in the Stage-1
CT0640 - HyperScope development and use will do so with clear intent to be
CT0641 - simultaneously readying their targeted application communities for
CT0642 - becoming pro-active, "evolutionary participants." ref DRT 2 04MQ
CT0644 - ..
CT0645 - Is this saying folks who put up money for initial Hyperscope work,
CT0646 - will independently develop applications for OHS?
CT0648 - ..
CT0649 - Need simpler explanation of actions required to ready targeted
CT0650 - application communities...
CT0651 -
CT0652 -
CT0653 -
CT07 -
SUBJECTS
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
DD11 -
DD1201 - ..
DD1202 - Phase-3: Evolve Multi-class UIS Architecture, High-Performance Teams
DD1203 -
DD1204 - OHS Interface Architecture will be set up explicitly to provide for
DD1205 - multiple UIS options, with a common, full-feature Application Program
DD1206 - Interface (API). To support extensive capability evolution, it will
DD1207 - be necessary to provide for a range of UIS options, varying in
DD1208 - complexity, potential competency level, difficulty to learn, types of
DD1209 - interface devices and modalities, etc.
DD1211 - ..
DD1212 - Support for web-connected mobile phones is one example.
DD1213 -
DD1214 - How would a telephone support knowledge management?
DD1216 - ..
DD1217 - Need to expand on this to demonstrate substance.
DD1219 - ..
DD1220 - Enable individuals, or special-role support teams, to experiment with
DD1221 - interface equipment, functionality, and control options, together with
DD1222 - optional special attributes of the standard Intermediary File, to
DD1223 - pursue especially high performance at important parts of their
DD1224 - knowledge processes. ref DRT 2 04SP
DD1225 -
DD1226 - Need example of a "knowledge process."
DD1228 - ..
DD1229 - Need scenario to explain this task or objective.
DD1231 - ..
DD1232 - How are experiments conducted, and what interface equipment,
DD1233 - control options might be tested?
DD1234 -
DD1235 -
DD1237 - ..
DD1238 - Support Teams Maintain Dynamic Knowledge Repository (DKR)
DD1239 - Knowledge Integrator - Motivated Use Special Equipment, Training
DD1240 - Com Manager Enables Intelligence Collection and Organization
DD1241 -
DD1242 - Having this kind of exploration in any event will be necessary. Doing
DD1243 - it with special extensions to the widely used OHS will be very
DD1244 - important in enabling feasible migration of these tools and skills out
DD1245 - into the rest of the communities. Moreover, doing this exploratory
DD1246 - high-performance activity over the SAME WORKING domains amplifies that
DD1247 - benefit immensely; motivated individuals can optionally acquire
DD1248 - special interface equipment, take some special training, and move up
DD1249 - to a "new class of user proficiency" (e.g. becoming a certified
DD1250 - Class-4B Knowledge Integrator). ref DRT 2 04TX
DD1252 - ..
DD1253 - "Knowledge Integrator" seems awkward. "Analyst" probably works
DD1254 - better.
DD1256 - ..
DD1257 - Seems to implement Doug's call for a new way of working, reviewed
DD1258 - on 991222. ref SDS 15 3696
DD1260 - ..
DD1261 - Generally aligns with Communication Manager called out in NWO to
DD1262 - provide new skills and management science. ref OF 2 6369
DD1264 - ..
DD1265 - On 000120 contributor for OHS/DKR cited meeting facilitator for a
DD1266 - system called "technography" that aids collaboration, and so may
DD1267 - fit some of Knowledge Integrator scope. ref SDS 17 2300
DD1269 - ..
DD1270 - On 960626 article reports industry is moving toward using
DD1271 - librarians as knowledge navigators. ref SDS 6 R59H
DD1272 -
DD1273 - [On 001204 Doug presented this idea to NSF. ref SDS 82 8O4L
DD1274 -
DD1275 - [On 001222 Gary Johnson calls for knowledge expert.
DD1276 - ref SDS 90 DW5I
DD1278 - ..
DD1279 - [On 010111 Doug unaware SDS applied with Communication
DD1280 - Manager, supports this role. ref SDS 92 B2WY
DD1282 - ..
DD1283 - [On 010114 case study illustrates SDS records on the Internet
DD1284 - enables people to increase competence for solving complex
DD1285 - problems by applying lessons of the past available through a
DD1286 - connected record that Doug proposes. ref SDS 94 0001
DD1288 - ..
DD1289 - [On 010916 Eric Armstrong proposes Ontologist will perform
DD1290 - dialog mapping to implement system developed by Eugene Kim.
DD1291 - ref SDS A9 4J4J
DD1293 - ..
DD1294 - [On 011004 Eugene Kim proposes appointing a librarian to
DD1295 - track RFCs to improve productivity using email for discussing
DD1296 - new technologies to advance OHS/DKR. ref SDS B1 JU5O
DD1298 - ..
DD1299 - [On 020128 discussed with Doug need for analyst role to
DD1300 - manage organic subject structure. ref SDS B4 VT6L
DD1302 - ..
DD1303 - Need definition of knowledge to determine tasks of Knowledge
DD1304 - Integrator? ref SDS 0 A4U2
DD1306 - ..
DD1307 - Who provides the training for Knowledge Integrator?
DD1308 -
DD1309 - On 001017 Carla and Reg assigned. ref SDS 60 01DP
DD1311 - ..
DD1312 - What training is required for a Knowledge Integrator?
DD1314 - ..
DD1315 - What does a Knowledge Integrator do?
DD1316 -
DD1317 - Does this role help others learn OHS; does the role write
DD1318 - custom improvements for OHS? Or maybe search the internet
DD1319 - for interesting information? What is the core task?
DD1321 - ..
DD1322 - Need examples of "special equipment" for Knowledge Integrator?
DD1323 -
DD1324 -
DD1325 -
DD1326 -
DD1327 -
DD14 -
SUBJECTS
Support Teams Maintain DKR
Ontology Categories Missing
Search Engine Missing
Define DKR
DKR Difficult to Design, Not Enough Known about Knowledge, KM, 000615
DI07 -
DI0801 - ..
DI0802 - DKR, Collective IQ Needs Intelligence Process to Generate Knowledge
DI0803 -
DI0804 - Dynamic Knowledge Repository (DKR) could be maintained by trained
DI0805 - Support Teams. A university might field a team to support a research
DI0806 - project; A "Knowledge Integrator" could facilitate a professional
DI0807 - society's DKR. Competitive exercises could be conducted among teams
DI0808 - from different universities -- or companies, or agencies, or countries
DI0809 - -- as part of an explicit processes to facilitate improvement in
DI0810 - "Collective IQ." ref DRT 2 04VY
DI0812 - ..
DI0813 - The launch plan needs work on this DKR section, per Jack's letter
DI0814 - on 000426. ref SDS 31 2340
DI0816 - ..
DI0817 - Recognizing need for a work role is a big step noted in reviewing
DI0818 - Doug's ideas on 991222. ref SDS 15 0883
DI0820 - ..
DI0821 - On 991222 Doug requested review of his 1992 paper "Toward High
DI0822 - Performance Organizations," ref SDS 15 3360, which sets goals for
DI0823 - "collective IQ." ref SDS 15 3360 At that time, Doug explained
DI0824 - plans for a Colloquium to encourage funding of experiments toward
DI0825 - developing technology for OHS/DKR that would implement ideas he
DI0826 - presented in SRI's 1962 proposal to Augment Human Intellect.
DI0827 - ref SDS 15 0786
DI0829 - ..
DI0830 - DKR seems to be applied here as merely a body of knowledge, e.g.,
DI0831 - engineering, medicine, farming, and so on. The Launch Plan can
DI0832 - be strengthened by indicating how stuff gets into the DKR, and
DI0833 - how it is applied to perform daily work, including to solve world
DI0834 - problems, which was set as an objective on 000120. ref SDS 17
DI0835 - 1215 and ref SDS 17 3002 Doug's transmittal letter explains
DI0836 - advantage of linking to original sources. Providing links to
DI0837 - Doug's original writings on a DKR, would help the Launch Plan
DI0838 - identify achievable results for a DKR.
DI0840 - ..
DI0841 - [On 001027 Doug commented favorably on SDS support for OHS and
DI0842 - DKR objectives. ref SDS 64 XV6F
DI0844 - ..
DI0845 - [On 001114 team meeting proposed calling the "repository" an
DI0846 - OHS. ref SDS 73 4FYW
DI0848 - ..
DI0849 - [On 001115 Adam Cheyer recommends calling the "repository" a
DI0850 - DKR, based on Doug's documents, but Adam does not cite any of
DI0851 - Doug's documents, including the Launch Plan. ref SDS 74 L87F
DI0853 - ..
DI0854 - [...analysis above indicates OHS was the "repository" of
DI0855 - knowledge in 1992 paper. ref SDS 0 J57N
DI0857 - ..
DI0858 - [On 001116 Adam Cheyer reports definition of DKR based on
DI0859 - recent discussion with Doug. ref SDS 76 JO3F
DI0861 - ..
DI0862 - DKR could also relate to an organizational group, e.g., a
DI0863 - project, a department, and it could be organic, Ford Motor,
DI0864 - Mercury Division, Accounting Department, Sales, etc.
DI0866 - ..
DI0867 - Groupings require organic subject structure, also called
DI0868 - "ontology." So it seems pretty clear that for OHS to fly it
DI0869 - needs to dig into subjects, categories, and ontology, take your
DI0870 - pick, and this is difficult to accomplish, per discussion between
DI0871 - Jack and Paul, above. ref SDS 0 KY5K
DI0873 - ..
DI0874 - In all of the functionality presented above for OHS, nothing is
DI0875 - said about assembling information, i.e., a search engine to find
DI0876 - critical details, and to assemble parts of the record showing
DI0877 - chronology of related contextual frames, sometimes called,
DI0878 - subjects, topics, categories, taxonomy, ontology, etc. Possibly
DI0879 - this is covered under Multiple Views, ref SDS 0 D6H8; or, perhaps
DI0880 - the thought is that there are plenty of search engines for the
DI0881 - Internet already, but it is not clearly set out. Moreover,
DI0882 - search engines, per se, are inadequate for managing context,
DI0883 - which is why there is a lot of fuss about ontology, semiotics and
DI0884 - other exotic stuff nobody else has developed yet.
DI0886 - ..
DI0887 - [On 010114 case study illustrates SDS records on the Internet
DI0888 - enables people to increase competence for solving complex
DI0889 - problems by applying lessons of the past available through a
DI0890 - connected record that Doug proposes. ref SDS 94 0001
DI0892 - ..
DI0893 - Doug has discussed "knowledge containers" but this is missing
DI0894 - from the launch plan. A big issue arises of how to assemble
DI0895 - information into useful chunks of information for recognizing
DI0896 - causation that yields the power of knowledge to control the
DI0897 - future.
DI0898 -
DI0899 - [On 001113 Eric reports on meeting with Ken Holman who
DI0900 - discussed Topic Maps. ref SDS 72 JR5O
DI0901 -
DI0902 -
DI0903 -
DI0904 -
DI0905 -
DI0906 -
DI0907 -
DI0908 -
DI0909 -
DI0910 -
DI10 -