CONTACTS 

SUBJECTS
Property Rights in Knowledge Organization
License Irrelevant to Developing Code for OHS/DKR Work Product Shows
OHS Difficulties Reported Design Theory and Architecture
Engineers Don't Know What to Code License Dispute Does Not Delay Prog
Value Added Shown by Work Product Justifies Investing Time to Formula
Progress Not Delayed by License Dispute Engineers Don't Know What to
Code Created in Secret Demonstrate Usefulness Set License Terms Based
Code OHS/DKR Not Delayed by Agreement on License Work Product Shows V
Secret KM of SDS CRIT Team Reverted to Email Manual Methods Like Dave
Engineers Don't Know How to Code KM Collaboration Slow Because Nobody
Core Capability KM Not Understood, Eric Armstrong
License Agreement Does Not Delay Code Engineers Don't Know How to Des
Secret SDS Only KM Design Counterintuitive Difficult to Discover Arch
Clues Nobody Has Knowledge Experience to Develop KM Because Nobody Ha
Work Product Inability Other Methods Generate KM Work Product Shows K
Clueless Organizational Memory Hopeless Quagmire Information Overload

6118 -
6118 -    ..
6119 - Summary/Objective
6120 -
612001 - Follow up ref SDS 1 6271, ref SDS 3 0000.
612002 -
612003 - Submitted ref DIT 1 0001 to OHS/DKR group commenting on focus of
612004 - design and explaining that work product demonstrates added value that
612005 - can be protected through license based on demand for work product.
612006 -
612007 -   1.  Recent comments on license issues have demonstrated brilliant
612008 -       talent by many contributors. ref DIT 1 0001
612009 -
612011 -     ..
612012 -    Collaboration Derivitive of Intelligence Not Primary Objective
612013 -    Architecture of Human Thought to Augment Intelligence is Priority
612014 -
612015 -
612016 -       Eric's letter today referencing his excellent Treelight web site
612017 -       focuses on adding value to knowledge work, and seems to propose
612018 -       a technology project to improve collaboration.  I believe this
612019 -       is an error.  The first order of business should be intelligence
612020 -       based on an architecture of human thought. ref DIT 1 U75N
612021 -
612023 -     ..
612024 -    Where's the Code for Knowledge Management
612025 -    History of Doug Engelbart's OHS/DKR Ideas for Knowledge Management
612026 -    License Not Delaying Progress on OHS Code and Collaboration
612027 -    Work Product Demonstrates Added Value that Requires Licensing
612028 -
612029 -
612030 -       In a letter on 020426 Paul discusses objectives of the "free"
612031 -       software movement, ref DRT 1 0001, following up a letter from
612032 -       Richard Stallman on 020414. ref SDS 10 0001  Paul explains how
612033 -       Doug Engelbart's goals for an open source OHS/DKR relate to a
612034 -       GPL software license, ref DRT 1 QU9M, and begins with an
612035 -       excellent job of summarizing the history of Doug's work on
612036 -       CODIAC to develop knowledge management. ref DRT 1 5X4M
612038 -        ..
612039 -       Paul worried at length in the letter on 020426 that licensing
612040 -       prevents creating and disclosing useful code in big companies,
612041 -       like IBM, Microsoft, etc. ref DRT 1 O66I  In another letter on
612042 -       020513 Paul maintains that the license issue prevents code from
612043 -       being developed for knowledge management, specifically he asks
612044 -       Where's the code contributed to Doug's OHS/DKR efforts?
612045 -       ref DRT 2 G138  Paul argues progress has been slow because good
612046 -       ideas for performing KM have been withheld by big companies and
612047 -       by individuals rather than released for open source development.
612048 -       ref DRT 2 TL9I  He attributes difficulty recruiting people to
612049 -       contribute code to onerous license requirements. ref DRT 2 ON5G
612050 -       While I have admired Paul's analysis on many issues, this
612051 -       particular point is not supported by the record. ref DIT 1 HF6J
612053 -             ..
612054 -            [On 020530 Paul cited considerable effort to develop KM,
612055 -            ref SDS 11 6Y4J; discloses he is not ready to make the
612056 -            effort. ref SDS 11 O14N
612058 -        ..
612059 -       On 001127 Eric Armstrong reported that progress has been slow
612060 -       because the design of KM is difficult. ref SDS 5 QI4O  On 001120
612061 -       Paul submitted an article announcing IBM failed to convert Lotus
612062 -       Notes into KM because the design is difficult. ref SDS 6 F26K  A
612063 -       year later on 011003 Jack Park reported that two years of
612064 -       research have produced no clues for designing KM, ref SDS 9
612065 -       O74L, which aligns with comments on 010924 by Morris Jones
612066 -       noting SDS uniquely improves management of knowledge work,
612067 -       ref SDS 8 NK4J, and this has occurred for a number of reasons.
612068 -       ref SDS 8 QN7M
612069 -
612070 -            [On 020530 Eric concurs that slow progress in KM is due to
612071 -            difficulty discovering a design, and not because of license
612072 -            issues. ref SDS 11 RK5M
612074 -        ..
612075 -       A simple test is work product, ref DIT 1 NF6O, also cited by
612076 -       Morris on 010924. ref SDS 8 XT5F
612077 -
612079 -        ..
612080 -       Purple Numbers Demonstrated by Engelbart Justifies Licensing
612081 -
612082 -       Whether someone submits code or not is irrelevant if there is no
612083 -       work product that demonstrates added value to existing
612084 -       capabilities.  An example is Doug's purple numbers system
612085 -       demonstrated in a letter on 001025 that showed added value, so
612086 -       people might ask to have that code, and at that point licensing
612087 -       becomes an important concern. ref SDS 4 00VU  Similarly, Eric,
612088 -       Paul, Jack, Lee, Eugene and others have made helpful
612089 -       contributions, and so licensing is critical, based on a
612090 -       demonstration of added value, as Doug did on 001025.
612092 -        ..
612093 -       For example, Eugene made improvements in purple numbers,
612094 -       reported on 010131, ref SDS 7 MM9M, and earlier on 000623 Jack
612095 -       Park planned to produce an engine to organize the record.
612096 -       ref SDS 2 2915  Eric planned to create something on version
612097 -       control, and categories.
612099 -        ..
612100 -       Show work product that shows added value to generate demand for
612101 -       the code; then address licensing.
612103 -        ..
612104 -       This still leaves open the question of whether meaningful
612105 -       progress has occurred on producing an OHS/DKR, or is deterred
612106 -       pending resolution of license matters?
612107 -
612108 -           [On 020530 Paul raises license issue. ref SDS 11 IO9O
612110 -        ..
612111 -       OHS/DKR capability is so valuable, as explained in Eric's letter
612112 -       on 000120 citing Doug's vision presented in the Colloquium at
612113 -       Stanford, and on Eric's web site, per his letter below, for
612114 -       solving world problems, that it seems implausible for people to
612115 -       hold back creating useful code simply because of worry about
612116 -       licensing.  In other words the needs Eric related on 000120 and
612117 -       later on 011003 are so huge and painfully frustrating that no
612118 -       one would stand by and endure suffering if they knew how to fix
612119 -       the problem. In that case, work product would demonstrate added
612120 -       value.  Since there is no work product, this indicates that
612121 -       people don't know what to do.
612123 -        ..
612124 -       Eric's letter on 000503 made this very point.  Earlier on 000405
612125 -       Paul said close to the same thing.  Nothing in the record shows
612126 -       that lack of understanding the design of KM has been repaired.
612128 -        ..
612129 -       Consideration might therefore be given to reviewing Eric's
612130 -       letter on 000423 talking about augmenting intelligence, because
612131 -       experience indicates intelligence helps collaboration.  This
612132 -       requires re-thinking the meaning of "knowledge" based on Eric's
612133 -       letter on 000212 by applying the rigor invested the past week or
612134 -       so re-thinking license ideas. There is plenty of brain power in
612135 -       the group, but it needs to focus on things that make progress,
612136 -       rather than whatever pops into the mind at the moment, as Grant
612137 -       noted on 001012.  In this respect I differ slightly with Paul on
612138 -       the Termite production method used at Microsoft, Aerospace company and with
612139 -       the OHS/DKR effort the past few years.  A million bright stars
612140 -       light up the heavens but do not produce enough energy to light a
612141 -       fire; while a simple magnifying glass focuses light in
612142 -       sufficient measure for ignition.
612144 -        ..
612145 -       The missing ingredients then are focus of management and focus
612146 -       of design on cognitive science, noted by Drucker in his article
612147 -       published in October of 1999. Recall that Mary Keeler discussed
612148 -       this somewhat in remarks at SRI on 000518 citing work by Peirce
612149 -       on semiotics.
612151 -        ..
612152 -       Once you establish an architecture of human thought that can be
612153 -       addressed with computer programming skills, you can build a
612154 -       technology that enables a dynamic knowledge repository to solve
612155 -       world problems. When people are able to work "intelligently,"
612156 -       then there is opportunity to improve collaboration, as called
612157 -       out in Eric's web site.  So long as knowledge and intelligence
612158 -       are ignored, people will remain in the dark using information
612159 -       technology which means continued dominance by Microsoft that has
612160 -       been a sore point in the group. The only way to transcend
612161 -       Microsoft is to leave them the monopoly for IT that is document
612162 -       centric, and move the market to KM by advancing alphabet
612163 -       technology beyond the model of documents in the same way that
612164 -       automobiles outflanked covered wagons.  It is an old story that
612165 -       may not be played out in our lifetimes, but at least we have the
612166 -       opportunity to witness the majesty of a powerful new wave
612167 -       forming on the horizon, if only we would lift our eyes to see,
612168 -       and then perhaps nudge things along as best we can.
612170 -        ..
612171 -       Once a better foundation for knowledge work is in place by
612172 -       strengthening alphabet technology, then folks are positioned to
612173 -       accomplish Doug's goals for improving improvement using open
612174 -       source modalities.  First, however, we need a better way to
612175 -       leverage intelligence, as explained in NWO....
612177 -        ..
612178 -       http://www.welchco.com/03/00050/01/09/03/02/03/0309.HTM#42HC
612180 -        ..
612181 -       This requires focusing brilliant talent for analysis,
612182 -       demonstrated on the license issue, on "knowledge," which is
612183 -       painful in the beginning as Eric noted on 000503, but very soon
612184 -       rewarding, satisfying and fun to work intelligently.  It only
612185 -       takes a little focus.
612186 -
612187 -
612188 -
612189 -
612190 -
612191 -
612192 -
612193 -
612194 -
612195 -
612196 -
612197 -
612198 -
612199 -
612200 -
6123 -