THE WELCH COMPANY
440 Davis Court #1602
San Francisco, CA 94111-2496
415 781 5700
rodwelch@pacbell.net
S U M M A R Y
DIARY: February 12, 2000 07:34 PM Saturday;
Rod Welch
DKR core capability requires Knowledge Space.
1...Summary/Objective
2...Core Capability Threshold Objective of Knowledge Space - DKR
3...Document Management Objective Expanded
4...Eric proposes an innovation....
5...Advantages of Capturing the Record - Augmented Memory
......Dovetails with the way we think
......Capture ideas as they occur, in such a way that they do not
......Ideas are saved. They all come surging back when the
......Tracks implications, which augments reasoning.
.......IBIS-style domain-exploration of "conversation" integrated with
6...Future Improvements
.....Logical operators and segmentation are proposed.
.....Automated reasoning is a future derivitive, based on
.....Augmented synthesis may be possible that builds on ideas,
7...ABC Improvement Strategies
..............
Click here to comment!
CONTACTS
0201 - Minciu Sodas Laboratory
020101 - Mr. Andrius Kulikauskas, Ph.D.; Director
SUBJECTS
Colloquium Unfinished Revolution, 000106
Objectives Knowledge Space
Planning, Scope, Objecitves, Requirements
Core Capability of DKR, Engine of Knowledge
Integrate Email Hyperdocuments
Management Details Meeting Notes Intellectual Capital
Intellectual Capital Creating by Capturing the Record
Continuous Knowledge Stream, Replace Documents
Engineering Management
SDS Computer Aided Thinking
Core Enterprise Knowledge Management Chronology SDS
gIBIS Organize Information, Colloquium Correspondence, 000130
SDS Type Design Continuous Knowledge Stream, 000212
SDS Continuous Knowledge Stream, 000212
IBIS Decision Support
New Way of Thinking Working Doug's Mission Bootstrap Institute, 99122
New Way of Thinking Documents Change to Organizational Memory Paradig
4019 -
4019 - ..
4020 - Summary/Objective
4021 -
402101 - Follow up ref SDS 62 0000, ref SDS 61 0000.
402102 -
402103 - Eric presents an explanation of POIMS technology (without attribution)
402104 - to supplement or replace the original design of a document management
402105 - system. He reports getting the idea for a continuous information
402106 - stream while driving home, rather from the letter submitted on 000208
402107 - suggesting this capability be used as the core for the knowledge
402108 - management system being proposed by the Colloquium. Advantages are
402109 - cited for engineering management. Future derivitive capabilities for
402110 - automated thinking are also set out. Eric's second letter sets out 4
402111 - areas of what are called META NICs, which seem to relate to Doug's
402112 - objectives for improving improvement to solve problems. ref SDS 0 0786
402113 - The big challenge is education.
402114 -
402115 -
402117 - ..
4022 -
4023 -
4024 - Progress
4025 -
402501 - Core Capability Threshold Objective of Knowledge Space - DKR
402502 - Document Management Objective Expanded
402503 -
402504 - Follow up ref SDS 62 2993, ref SDS 61 8960.
402505 -
402506 - Received ref DRT 1 0001 from Eric Armstrong citing an idea he recalls
402507 - forming while driving home from the Colloquium, that his initial plan
402508 - for designing a DKR capability had been too limited by experience with
402509 - traditional "documents".
402511 - ..
402512 - Eric does not cite the letter, ref DIP 7 0001, explaining a continuous
402513 - information stream to improve traditional use of documents, based on a
402514 - process of "intelligence" to provide a Knowledge Space environment,
402515 - set out in POIMS, ref OF 1 5820, and submitted on 000208, ref SDS 61
402516 - DH47, which responded to Eric's letter also on 000208 asking for ideas
402517 - on the core process to accomplish the aims of the Colloquium to
402518 - augment human capabilities, ref SDS 61 027P; he requested ideas on
402519 - integrating email and hyperdocuments, ref SDS 61 3596, but also
402520 - requested analysis on the core of the system. ref SDS 61 4320
402522 - ..
402523 - Knowledege Management extends support for cognition beyond traditional
402524 - documents, noted in POIMS. ref OF 1 K84L
402526 - ..
402527 - Knowledge Space was formulated on 960620, ref SDS 18 3516; explained
402528 - to Morris at Intel on 990426, ref SDS 36 1100, based on the concept of
402529 - improving the alphabet discussed on 990225. ref SDS 29 7790 Managing
402530 - connections in the conscious span of attention was set out on 990419.
402531 - ref SDS 35 0896
402533 - ..
402534 - Eric describes the work process for creating a functional spec on the
402535 - integrated OHS and email system which he presented on 000210,
402536 - ref SDS 62 2993, including collaborating and performing the work.
402537 - ref DRT 1 6674
402538 -
402539 - He says the next step after the functional spec, is preparing a
402540 - design document. He says this work starts from scratch using
402541 - conventional methods. Information acquired over weeks and months
402542 - for the functional specification has to be laboriously reviewed
402543 - and assembled again for incorporation into the new document. He
402544 - seems to indicate that using the proposed OHS - email system
402545 - capability of linking, will make the process easier, but there
402546 - will still be a lot of manual labor that should be avoidable.
402547 - ref DRT 1 1920
402549 - ..
402550 - The scenario Eric presents on creating a document, reflects the
402551 - process on 940114 which Morris cited for preparing a technical manual.
402552 - ref SDS 4 4928 On 990712 Morris worried about having to start with a
402553 - blank page. ref SDS 48 8019 The SDS solution to improve productivity
402554 - by recyclying prior knowledge, explained in POIMS, ref OF 1 6649, is
402555 - reflected by...
402557 - ..
402558 - Eric proposes an innovation....
402559 -
402560 - He suggests today capturing design notes for each part of the
402561 - specification, as they arise in the mind from meetings, calls,
402562 - documents and performing daily work. This record on "design
402563 - notes" would not appear in the "functional specification." But
402564 - work to prepare the design document could draw on the resource by
402565 - a request that says...
402566 -
402567 - "Give me all the design notes that correspond to this
402568 - version of the specification". ref DRT 1 6370
402570 - ..
402571 - [On 000505 this capability is added to editor spec under a
402572 - section for "Queryable." ref SDS 73 2709
402574 - ..
402575 - Eric does not cite the letter on 000208 proposing this solution,
402576 - ref DIP 7 1755, in response to Eric's request, ref SDS 61 4905,
402577 - which aligns with Doug Engelbart's desire for a whole new way of
402578 - thinking and working, from the record on 991222. ref SDS 52 3696
402580 - ..
402581 - Indeed, Eric's innovation is a major step toward Knowledge Space
402582 - that enables a paperless/virtual office, as defined in POIMS,
402583 - ref OF 1 1107, and developed on 960620. ref SDS 18 3516 The
402584 - innovation addresses Erick's question on 000120 about what a DKR
402585 - "looks like." ref SDS 54 3002
402586 -
402587 - [On 000229 mathamatics of knowledge addresses causality.
402588 - ref SDS 66 1836]
402590 - ..
402591 - [On 000302 Eugene Kim suggests language is a human technology
402592 - that can be augmented. ref SDS 67 8975]
402594 - ..
402595 - [On 000306 v0.2 of Editor spec does not incorporate innovation
402596 - proposed today. ref SDS 68 0782
402598 - ..
402599 - [On 000423 Eric says KM should augment human "intelligence",
402600 - ref SDS 70 5933
402602 - ..
402603 - [...Eric explains augment based on conventional handling of
402604 - documents, ref SDS 70 5943, rather than cognitive processes
402605 - hinted at in his analysis today.
402607 - ..
402608 - [...Eric submits atomic data structures that do not have express
402609 - support for intelligence. ref SDS 70 4933
402611 - ..
402612 - [On 000503 Jack Park wants "Knowledge Space." ref SDS 72 6138
402614 - ..
402615 - [On 000518 Knowledge Space developed in the record of DKR
402616 - meeting at SRI. ref SDS 75 8439
402618 - ..
402619 - Eric recalls thinking a "document" shouldn't be an isolated entity,
402620 - but rather a "labeled view" on a nexus of nodes. ref DRT 1 0874 He
402621 - feels now that a means is needed for starting new documents by using
402622 - thinking from prior related endeavors, commonly called "experience."
402623 - ref DRT 1 2352
402624 -
402625 - On 000124 scope of document management suggested additional issues
402626 - for strengthening traditional document management. ref SDS 55 4130
402628 - ..
402629 - [On 000227 Eric feels again that knowledge management requires
402630 - more than working with documents. ref SDS 65 0786]
402632 - ..
402633 - POIMS describes this capability as controlled visibility from the
402634 - "intelligence" process, ref OF 1 1103, of recycling intellectual
402635 - capital. ref OF 1 6649
402637 - ..
402638 - On 990712 SDS doesn't start with a blank page, ref SDS 48 8019,
402639 - citing firepower for expediting analysis reported on 950204.
402640 - ref SDS 6 4995 discussed also on 940114. ref SDS 4 6295
402641 -
402643 - ..
402644 - Advantages of Capturing the Record - Augmented Memory
402645 -
402646 - Eric characterizes this capability as "augmenting memory," and cites
402647 - advantages for engineering management...
402648 -
402649 - [On 000407 listed as agend issue for project meetings.
402650 - ref SDS 69 5938
402652 - ..
402653 - [On 000423 Eric explains purpose of DKR project is to augment
402654 - human memory. ref SDS 70 5096
402655 -
402656 -
402658 - ..
402659 - Dovetails with the way we think
402660 - ref DRT 1 5135
402661 -
402662 - mirrors the way people think in exploring design alternatives.
402663 - ref DRT 1 6804
402665 - ..
402666 - record of thinking makes it easier to revise decisions at a
402667 - later stage, when new technology is discovered.
402668 -
402670 - ..
402671 - Capture ideas as they occur, in such a way that they do not
402672 - interfere with the flow of the original document -- the
402673 - functional specification. ref DRT 1 6675
402674 -
402675 - [On 000517 Eric relates success on a project in Texas.
402676 - ref SDS 74 2064
402677 -
402679 - ..
402680 - Ideas are saved. They all come surging back when the
402681 - designing starts, so that there is a better chance that nothing
402682 - is overlooked. ref DRT 1 7980
402684 - ..
402685 - [On 000424 Eric explains that capturing the record supports
402686 - future work, and that this could have expedited the DKR
402687 - project if the Doug's team in the 1960s had captured the
402688 - record of the Augment program. ref SDS 71 0786
402689 -
402691 - ..
402692 - Tracks implications, which augments reasoning.
402693 - ref DRT 1 3363
402694 -
402695 - IBIS-style domain-exploration of "conversation" integrated with
402696 - domain-proposal (documents), begins to support the reasoning
402697 - process. ref DRT 1 5047
402698 -
402699 - On 000130 Eric considered gIBIS for organizing Colloquium
402700 - communications. ref SDS 60 0866 IBIS and gIBIS was first
402701 - reviewed on 940527. ref SDS 5 0783
402702 -
402703 - [On 000218 Dick Karpinski related gIBIS capabilities for
402704 - knowledge management. ref SDS 64 4345]
402706 - ..
402707 - [On 000218 Colloquium #7 considers gIBIS. ref SDS 63 0741]
402709 - ..
402710 - [..., concerns cited about IBIS. ref SDS 63 7050
402712 - ..
402713 - [On 000505 IBIS incorproated into OHS/DKR initial specs on
402714 - requirements. ref SDS 73 2650
402716 - ..
402717 - [On 000614 IBIS proposed to support Wiki. ref SDS 76 4939
402719 - ..
402720 - [On 000716 Joe Ransdell cautions about distinction between
402721 - formal logic and practical reasoning. ref SDS 77 2200
402722 -
402723 - ...making it easy to find implications assists human reasoning
402724 - process, carry on intelligent design conversations and discover
402725 - inherent contradictions earlier in the process. ref DRT 1 9951
402726 - ..
402727 - No experience or source to support these expectations is cited.
402728 - ..
402729 - Complexity of environment that "boggles the mind" raised by Eric
402730 - on 000125 is not addressed in analysis today. ref SDS 57 3975
402732 - ..
402733 - Standardized Tags are presented for organizing the record to
402734 - accomplish retrieval. ref DRT 1 4895
402735 -
402736 - This aligns generally with organic subject structure in SDS,
402737 - explained in POIMS. ref OF 1 1110
402738 -
402739 - There is recognition that specialized domains of knowledge
402740 - structure might be applied, ref DRT 1 6208, which was proposed for
402741 - the NSF project, ref OF 3 6678, and particularly, ref OF 3 3300, on
402742 - 990615. ref SDS 41 3844
402744 - ..
402745 - The difficulty of subject identification is implied, though not
402746 - expressly stated in Eric's presentation. ref DRT 1 0816 It is set
402747 - out in a Byte article reviewed on 910418. ref SDS 3 5584
402748 - ..
402749 - Eric says this capability accomplishes important features of a
402750 - knowledge repository, ref DRT 1 6478 A defintion of knowledge is not
402751 - presented that supports this proposition, noted previously as a
402752 - threshold requirement on 000120. ref SDS 54 5063
402754 - ..
402755 - On 990524 these advantages were submitted to Intel, ref SDS 38 0876,
402756 - and on 990525 Intel reported back. ref SDS 39 0966
402758 - ..
402759 - Managing the record of "thinking" in text files is considered onerous.
402760 - ref DRT 1 4260
402761 -
402763 - ..
402765 - ..
402766 - Future Improvements
402767 -
402768 - Logical operators and segmentation are proposed.
402769 - ref DRT 1 2408
402771 - ..
402772 - ..
402773 - Automated reasoning is a future derivitive, based on
402774 - potential for pattern recogitition, which would flow from the
402775 - record. ref DRT 1 8652
402776 -
402777 - Augmented synthesis may be possible that builds on ideas,
402778 - combining them, abstracting them in some way, or incorporating
402779 - them into a larger whole. ref DRT 1 0990
402780 -
402781 -
402782 -
402783 -
402784 -
402785 -
4028 -
SUBJECTS
Enterprise Management
ABC Improvement Model
Collaboration Helps Everyone
Open Source Development NIC
Management NIC
Online Community Building NIC
Education NIC
META NIC Strategy
Education On-demand, Armstrong 000306
5111 -
511201 - ..
511202 - ABC Improvement Strategies
511203 -
511204 - Eric's second letter lays out details from Colloquium class #6 for a
511205 - Meta NIC strategy. ref DRT 2 0001
511206 -
511207 - Four broad improvement capabilities are shown...
511208 - ..
511209 - 1. Open Source Development NIC builds the *technology* that
511210 - comprise a Capability Improvement Infrastructure. ref DRT 2
511211 - 6552
511213 - ..
511214 - This seems to be the DKR discussed above. ref SDS 0 8960
511216 - ..
511217 - 2. Management NIC forges the *social systems* (what Doug calls the
511218 - "Human Systems") that comprise a Capability Improvement
511219 - Infrastructure -- the process and procedures by which work gets
511220 - done. ref DRT 2 2244
511222 - ..
511223 - This requires leadership education under step 4, ref SDS 0
511224 - 4380, to help people overcome ignorance, fear and denial that
511225 - adding "intelligence" to management, per Eric's first letter,
511226 - above, ref SDS 0 9790, will improve earnings, as reviewed on
511227 - 980405. ref SDS 26 5065
511228 - ..
511229 - Experience reported on 981027 shows that improving
511230 - management to improve earnings is a miracle. ref SDS 28 7315
511232 - ..
511233 - 3. Online Community Building NIC builds the communication systems
511234 - and strategies that allow remote collaboration. Someday, a DKR
511235 - may be a completely independent entity that can be accessed
511236 - without help from others.
511237 -
511238 - How does this differ from Open Source Development NIC, item
511239 - #1? ref SDS 0 0840
511241 - ..
511242 - DKR will require *major* improvements in AI language
511243 - processing, so that the system can translate the user's stated
511244 - problem into a form that can be addressed from within the
511245 - system. ref DRT 2 1938
511246 - ..
511247 - Given the organic and fluid nature of "knowledge"
511248 - grounded in life experience, set out in the record on
511249 - 000120, ref SDS 54 4410, this capability requires more
511250 - careful analysis of objectives in order to be meaningful.
511252 - ..
511253 - In the meantime, it will be human interactions that give people
511254 - the pointers they need to access the repository. To take a
511255 - management example: "How do I start a project?" may be answered
511256 - by an email that gives a pointer into the email repository for
511257 - the document: "Initiating an Open Source Development Effort".
511258 - The email/forum interaction takes advantage of Eric Raymond's
511259 - observation: "Every problem is shallow, given enough eyeballs".
511260 - (Whatever the question, someone is sure to have a DKR bookmark
511261 - handy that can be used to answer the question in moments.),
511262 - ref DRT 2 1000
511263 - ..
511264 - Eric's ideas in the first letter, above, suggest a
511265 - capability that can improve upon Bookmarks for answering
511266 - questions about daily management. ref SDS 0 4292
511268 - ..
511269 - Communication Managers can begin adding "intelligence" to
511270 - management today, tomorrow, next week, whenever people take
511271 - the strategic step.
511272 - ..
511273 - 4. Education NIC develops methods for teaching, training,
511274 - and improving the *human systems* (what Doug calls the basic
511275 - human capabilities) that comprise a Capability Improvement
511276 - Infrastructure. (For example: Teaching people how to use the
511277 - technology, how to organize for success, and how to work
511278 - together in a community. ref DRT 2 8232
511279 -
511280 - [On 010605 Jack Park plans to pilot test technology in a
511281 - school, for improving learning. ref SDS 78 AN9H
511283 - ..
511284 - [On 010614 SDS improves education. ref SDS 79 A581
511286 - ..
511287 - [On 010627 Jack Park submits article on advantages and
511288 - disadvantages of telelearning. ref SDS 80 0001
511289 - ..
511290 - We have to teach the benefits of following management
511291 - standards and published policies for continual learning and
511292 - traceability to original sources, discussed with the U.S.
511293 - Army Corps of Engineers on 971202. ref SDS 22 7453
511295 - ..
511296 - We have to teach the fragility of knowledge, explained on
511297 - 950204, ref SDS 6 0550, and the power of the microcosm from
511298 - the meeting on 950927, ref SDS 14 5412, even at places
511299 - where people work with the microcosm, like Intel reported
511300 - on 970603. ref SDS 20 5803
511302 - ..
511303 - We have to teach the benefits of following company policy
511304 - and guidelines on partnership, i.e., collaboration, from
511305 - the report on 990625. ref SDS 45 4185
511306 -
511307 - ...teach benefits of following company guidelines on
511308 - communication. ref SDS 45 3190
511309 - ..
511310 - We have to teach CEOs how to overcome psychological
511311 - barriars that prevent them from capturing a useful record,
511312 - or getting someone who can to accomplish this task, in
511313 - order for Eric's new technology design, reported above,
511314 - ref SDS 0 9790, to work, as reported by Fortune on 990625.
511315 - ref SDS 46 7344
511317 - ..
511318 - Education is likely impossible, because educators want to teach
511319 - what they have learned or read about in the popular press, or
511320 - what someone will fund.
511321 -
511322 - [On 010614 SDS improves education. ref SDS 79 A581
511324 - ..
511325 - Creating a powerful technolog that enough people can use
511326 - productively with minimum help, will make the education issue
511327 - easier to address.
511328 - ..
511329 - Pilot testing is a method Doug cites in his paper on in
511330 - 1992 that needs attention, as discussed on 991222. ref SDS 52
511331 - 5402
511332 -
511333 -
511334 -
511335 -
511336 -
511337 -
511338 -
511339 -
5114 -
Distribution. . . . See "CONTACTS"