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: September 13, 2001 09:16 PM Thursday; Rod Welch

Sandy Klausner reports progress on CoreTalk.

1...Summary/Objective
......PDF Reduces Productivity Not Effective for KM
......Eric Reviews Issues that Refine KM, Core Capability Missing
......How Does CoreOne Enable New Way of Working?
......New Way of Working Needs Support Understanding, Follow Up
......KM Design for Improving Productivity and Strengthening Email
2...SDS Adds Value Linking Historical Record Archive
3...OHS/DKR Announcement Pending, Eugene Kim


..............
Click here to comment!

CONTACTS 
0201 - CoreTalk Corporation
020101 - Mr. Sanford B. Klausner
020102 - Founder and Founder
0202 - Armstrong Consulting
020201 - Mr. Eric Armstrong

SUBJECTS
Progress Report on CoreOne, Sandy Klausner
Graphical Display Only Useful for Small Structures Overwhelmed by Com
PDF File Reduces Productivity Not Effective KM
PDF Pictures Unproductive Waste Time Need Flexible Structure Addressa
PDF Pictures Not Efficient for Com Metrics KM Takes Too Much Time
PDF Not Productive No Addressability Cannot Link

1508 -
1508 -    ..
1509 - Summary/Objective
1510 -
151001 - Follow up ref SDS 73 0000, ref SDS 68 0000.
151002 -
151003 - Received ref DRT 1 0001 from Sandy Klausner saying....
151004 -
151005 -      Its been some time since we communicated and I thought I'd share
151006 -      a review Eric Armstrong wrote on one aspect of the emerging
151007 -      CoreOne platform.
151013 -  ..
151014 - Sandy submitted a PDF file prepared by Eric Armstrong that covers a
151015 - lot of the elements in Eric's CDS specs reviewed on 000505.
151016 - ref SDS 33 0001   Sandy wants Eric's comments to remain confidential,
151017 - so do not include the file in the record.
151019 -  ..
151020 - Sandy's work was reviewed on 000608. ref SDS 41 0001
151022 -  ..
151023 - Submitted ref DIT 1 0001 to Sandy saying....
151025 -       ..
151026 -      Glad to hear you are making progress, especially under current
151027 -      circumstances. With restricted travel in the period ahead,
151028 -      advances like you are developing will be in great demand,
151029 -      referring to the terrorist attacks in New York and on the
151030 -      Pentagon in Washington DC on 010911.
151031 -
151033 -       ..
151034 -      PDF Reduces Productivity Not Effective for KM
151035 -
151036 -      Had a little difficulty initially opening Eric's file, but
151037 -      finally was able to take a look.  Something to think about when
151038 -      planning a DKR system is that PDF files take extra time to
151039 -      convert into something that can be integrated into the work
151040 -      stream for effective analysis. ref DIT 1 HU6K
151041 -
151042 -          This aligns comments to Cliff Joslyn at LANL on 010126.
151043 -          ref SDS 72 V2RY
151044 -
151045 -             [On 030316 Gary Johnson cites inefficiency of PDF
151046 -             documents; part of 2-worlds problem transforming from
151047 -             information into a culture of knowledge. ref SDS 82 M36F
151048 -
151050 -       ..
151051 -      Eric Reviews Issues that Refine KM, Core Capability Missing
151052 -
151053 -      The issues Eric raises (e.g., versioning, ratings,
151054 -      addressability, external markup, etc), have been given critical
151055 -      attention over the past 18 months by Doug Engelbart's group.
151056 -      Eric's specs reviewed on 000505, ref SDS 33 0001, as revised on
151057 -      000614, ref SDS 48 0001, and Lee Iverson's update on 010620,
151058 -      called NODAL, ref SDS 74 0001, do an excellent job of identifying
151059 -      such requirements.  From my experience these are interesting
151060 -      refinements of the effort to use technology for saving time and
151061 -      money in accomplishing knowledge work. ref DIT 1 008G
151062 -
151063 -
151065 -       ..
151066 -      How Does CoreOne Enable New Way of Working?
151067 -
151068 -      Addressability is useful when integrated with other features that
151069 -      Eric does not discuss; but, in any case, the proof is in the
151070 -      pudding. ref DIT 1 009P
151071 -
151072 -      Would like to see examples of your work product, and scenarios
151073 -      explaining application that provides a new way of working, called
151074 -      out by Doug, reviewed on 991222. ref SDS 22 3696  Let's say we
151075 -      are on the job using your system.  How would we work differently
151076 -      that saves time and money? We have 3 meetings, make 8 phone
151077 -      calls, send 15 email, etc.  How would this work be improved by
151078 -      your system? ref DIT 1 VT8N
151080 -           ..
151081 -          Received ref DRT 2 0001 from Sandy answering my letter this
151082 -          morning, saying....
151083 -
151084 -             The concentration of the CoreOne platform is to provide a
151085 -             robust foundation that directly supports the notions of
151086 -             continued manipulation of a knowledge base, maintaining
151087 -             event chronology for actions, easy passage access and
151088 -             linkage, archive search capability, and long-term context
151089 -             management.
151091 -              ..
151092 -             Would you like to come under an NDA to review the
151093 -             architectural specification?
151095 -           ..
151096 -          Sandy evidently does not yet have work product, but rather
151097 -          has developed a specification for accomplishing something.
151098 -          Based on progress reported by OHS/DKR effort, it seems like a
151099 -          good strategy for evaluating technology is see work product,
151100 -          rather than specs.
151102 -           ..
151103 -          Received ref DRT 3 0003 from Eric complimenting analysis of
151104 -          CoreTalk.
151106 -       ..
151107 -      Eric has written to the group on 010912, ref SDS 76 0001,
151108 -      supporting Jack Park's recent idea on 010908 to improve email,
151109 -      because email seems fast and easy, i.e., it allows people to
151110 -      graze on endless information, rather than do the hard work of
151111 -      creating useful knowledge. ref DIT 1 005O  Jack likes this idea
151112 -      because people are lazy. ref SDS 75 0001
151114 -       ..
151115 -      On 000307 KM was explained as "hard work." ref SDS 27 5182
151117 -       ..
151118 -      Eric's support for improving email reflects his proposal on
151119 -      000120, ref SDS 24 3871, and on other occasions (summarized in
151120 -      the record on 010988, ref SDS 75 FV4G, for the system Jack now
151121 -      contemplates, which can be summarized as webmail.
151123 -       ..
151124 -      This capability has been demonstrated over the past 18 months,
151125 -      but there has not been a lot of interest, as reported on 010908,
151126 -      ref SDS 75 XS6J, because KM requires deliberative analysis that
151127 -      adds intelligence to information, explained in POIMS, ref OF 1
151128 -      5418, and in the record on 001219, ref SDS 71 FO5M, while people
151129 -      prefer reactive, spontaneous commentary that produces more
151130 -      information, like this letter, because it can be created fast and
151131 -      easy, which fits the parameters Jack cites of laziness.
151132 -      ref SDS 75 0001
151133 -
151134 -
151136 -       ..
151137 -      New Way of Working Needs Support Understanding, Follow Up
151138 -      KM Design for Improving Productivity and Strengthening Email
151139 -
151140 -      How, for example, can Sandy's system convert the letter
151141 -      submitted today, ref DIT 1 0001, into a structure of
151142 -      organizational memory that can be manipulated for continued use
151143 -      to grow the knowledge base?
151145 -       ..
151146 -      How much time does it take to organize this letter, so that bits
151147 -      and pieces that are relevant to past and future events can be
151148 -      connected into a chronology of cause and effect to guide daily
151149 -      action?
151151 -           ..
151152 -          Received ref DRT 2 0001 from Sandy answering my letter this
151153 -          morning, but not submitting work product nor answering these
151154 -          questions.
151156 -       ..
151157 -      How long will it take to remember, access and link relevant parts
151158 -      of this letter to new information received a month, a year, 10
151159 -      years later, in order to discover, weigh and establish alignment
151160 -      with belief in cause and effect, and then hard wire alignment of
151161 -      such belief in relation to contextual experience?
151163 -       ..
151164 -      How long and with what processes will organic subject structure
151165 -      be formulated to manage context?  How will new information from
151166 -      this letter be integrated into the work stream for timely and
151167 -      thorough follow up?
151169 -       ..
151170 -      These two issues of understanding and follow up are not discussed
151171 -      in Eric's comments on your work, perhaps because they augment
151172 -      human intelligence that converts information into knowledge.  The
151173 -      team decided on 000615 to forego work on a system to create
151174 -      knowledge, ref SDS 50 6271, based on Eric's letter on 000503.
151175 -      ref SDS 32 5033
151177 -       ..
151178 -      To provide a productive new way of working, these issues need
151179 -      support.
151180 -
151181 -
151182 -
151183 -
1512 -

SUBJECTS
SDS Shows Value for Historical Record
Link Original Sources Aids Understanding Context, Doug Engelbart
Armstrong, Eric SDS Links Add Value Historical Record

6305 -
630601 -  ..
630602 - SDS Adds Value Linking Historical Record Archive
630603 -
630604 - Received ref DRT 3 0001 from Eric Armstrong commenting on the copy he
630605 - received of the letter, ref DIT 1 0001, submitted to CoreTalk earlier
630606 - today, per above. ref SDS 0 4W9K
630607 -
630609 -  ..
630610 - Eric says....
630611 -
630612 -      Your link-base shows its value in terms of historical record.
630614 -  ..
630615 - This seems like favorable comment on SDS adding value to information
630616 - by aligning analysis with original sources to augment intelligence;
630617 - and, so seems to update analysis on 000824. ref SDS 61 FJ5H
630618 -
630619 -      [On 011105 Eric feels inclusion links would improve SDS; no
630620 -      evidence demonstrating this saves time and money. ref SDS 81 3L5O
630622 -  ..
630623 - On 000601 Eric proposed a requirement for OHS/DKR for accomplishing
630624 - SDS support for alignment. ref SDS 37 4997  In another record the same
630625 - day, Eric was amazed by SDS support for organizational memory on a
630626 - discussion at Intel, comparing accuracy and thoroughness to a tape
630627 - recording. ref SDS 38 0001
630629 -  ..
630630 - On 000824 Eric was discouraged by discursive efforts at SRI on OHS/DKR
630631 - project to develop Knowledge Management, ref SDS 61 MVE8, and was
630632 - disappointed with plans to implement SDS design. ref SDS 61 OU60
630634 -  ..
630635 - On 001122 Eric was discouraged by slow progress implementing his plans
630636 - for an OHS/DKR. ref SDS 67 0001  At that time it was recommended he
630637 - start by implementing Doug Engelbart's call for creating a connected
630638 - record. ref SDS 67 WP8H  Eric disagreed on 001127 saying a complex
630639 - kernel is an essential first step. ref SDS 69 0001
630641 -  ..
630642 - Also, on 001127 Eric seemed to imply that SDS work product he had seen
630643 - did not solve the problem of adding value to information, commonly
630644 - called knowledge management. ref SDS 69 TN4J  Today, he seems to be
630645 - amending that understanding.
630646 -
630647 -      [On 010616 Eric amazed by SDS support for memory with mechanisms
630648 -      that obviously work; wants better interface. ref SDS 77 0001
630650 -       ..
630651 -      [On 011010 Eric proposes context needed to evaluate whether to
630652 -      click links to open supplementary information. ref SDS 80 M55G
630654 -       ..
630655 -      [On 011010 SDS helps people avoid being overwhelmed by links.
630656 -      ref SDS 80 HM4F
630657 -
630658 -
630659 -
630660 -
630661 -
6307 -

SUBJECTS
Kim, Eugene Announcement Pending on OHS/DKR
Announcement OHS/DKR Announcement Soon, Eric Armstrong
OHS/DKR Progress Announcement Soon by Eugene Kim, per Eric Armstrong
Developments by Eric, Eugene Kim and Jack Park Select Group
Developments by Eric, Eugene Kim and Jack Park Select Group
Foraging on Information Laziness Use Email Instead of Investing Intel
OHS/DKR New Developments by Eric, Eugene Kim and Jack Park Select Gro

7209 -
721001 -  ..
721002 - OHS/DKR Announcement Pending, Eugene Kim
721003 -
721004 - Eric reports in his letter today....
721005 -
721006 -      Watch for some interesting announcements regarding Eugene's
721007 -      recent work.  ref DRT 3 Q55L
721009 -  ..
721010 - Submitted ref DIT 2 0001 to Eric thanking him for notice of Eugene's
721011 - pending announcement.
721012 -
721013 -      [On 010916 Eric reports on Eugene Kim creating a new system of
721014 -      dialog mapping to organize email. ref SDS 78 0001
721016 -  ..
721017 - Mention having heard that Eric and Jack Park are working in a select
721018 - group of OHS/DKR team members, and so Eugene's pending announcement
721019 - appears to show good progress. ref DIT 2 SJ6J
721020 -
721021 -      [On 010917 Eugene reports starting an OHS Launch Community and
721022 -      inviting new contributors. ref SDS 79 00UU
721024 -  ..
721025 - Received ref DRT 3 0001 from Eric responding to my letter commenting
721026 - on Eugene's announcement.
721028 -  ..
721029 - Eric says....
721030 -
721031 -      Actually, this is work that Eugene has done pretty much on his
721032 -      own -- not that he wants it that way. That's just the way it
721033 -      turned out.
721034 -
721035 -      I'm acting as a "rating supplier" here. His stuff is good, and
721036 -      likely to be useful in our discussions in the very near term.
721037 -
721038 -
721039 -
721040 -
721041 -
721042 -
721043 -
721044 -
721045 -
721046 -
721047 -
721048 -
721049 -
721050 -
7211 -
Distribution. . . . See "CONTACTS"