CONTACTS 
0201 - Bootstrap Institute                                                                                                                                                O-00000735 0101
020101 - Mr. Douglas C. Engelbart, Ph.D.

SUBJECTS
Meeting SRI Resumed 001017, 001010
Meeting SRI Resumed on 001017, 001010

0504 -
0504 -    ..
0505 - Summary/Objective
0506 -
050601 - Follow up ref SDS 69 0000, ref SDS 64 0000.
050602 -
050603 - Received a letter from Eugene Kim transmitting information on the
050604 - meeting at SRI yesterday, explaining project status.  Eric Armstrong
050605 - reported snags in architecture for OHS. ref SDS 0 M4W7  Some of the
050606 - problem appears related to the scope of KM, which requires experience
050607 - using knowledge management, per below. ref SDS 0 GD6J
050608 -
050609 -
050610 -
050611 -
050612 -
050613 -
050614 -
050615 -
050617 -  ..
0507 -
0508 -
0509 - Progress
051001 -  ..
051002 - Record of Meeting on 001017 at SRI Submitted
051003 -
051004 - Received ref DRT 1 0001 from Eugene submitting information about the
051005 - meeting at SRI yesterday, ref DRT 1 0002, which was scheduled by
051006 - Eugene in his letter, ref DRP 2 0001, received on 001010. ref SDS 69
051007 - 0001
051008 -
051009 -      [On 001018 Gil Regev requested a summary to help understand the
051010 -      meeting at SRI. ref SDS 73 M94R
051012 -       ..
051013 -      [...Jack submitted Howard's summary, and Gil said this helps
051014 -      understand the context. ref SDS 73 IM5F
051016 -  ..
051017 - There is no indication that action items were reviewed as proposed in
051018 - the telecon with Doug on 000929. ref SDS 64 RP3N
051020 -  ..
051021 - Used Eugene's letter to develop a project record for the meeting
051022 - yesterday. ref SDS 72 0001
051023 -
051024 -
051025 -
051026 -
051027 -
0511 -

SUBJECTS
OHS Program Code Architecture Under Production
OHS Architecture Eric Armstrong Creating Code for OHS to be Released So  , 001017
Architecture Snag OHS Eric Armstrong, 001018
Architecture Makes Sense Contemporaneous Engineering Record with Code
Architecture Problems KM Linking Versioning, Eric Armstrong, 001018
Linking Architectural Snag KM, Eric Armstrong
High Tech Tourism Tools That Fail to Improve Daily Work, 000601, Marc
High Tech Tourism Cannot Solve Complexity Issues in KM
Architecture KM Hard to Design, Not Understood

2811 -
281201 -  ..
281202 - Snag in OHS Architecture on Linking and Versioning
281203 -
281204 - Follow up ref SDS 71 0001.
281205 -
281206 - Received ref DRT 2 0001 from Eric reporting a big snag in the
281207 - architecture which he reported yesterday would soon result in source
281208 - code being submitted to the team for an OHS. ref SDS 71 0001  On
281209 - 001017 Eugene Kim reported architure for the OHS is not established.
281210 - ref SDS 72 TJ3G
281211 -
281212 -        [On 001019 Paul Fernhout offers ideas. ref SDS 73 0001
281214 -         ..
281215 -        [On 001106 Eric reports delay resolving broad range of design
281216 -        problems. ref SDS 75 0001
281218 -         ..
281219 -        [On 001122 Eric disappointed about difficulty creating KM, sent
281220 -        letter suggesting he started with narrow objectives, of simply
281221 -        to link. ref SDS 76 0001
281223 -         ..
281224 -        [On 001130 article reports IBM delays release of Raven which is
281225 -        a KM effort based on Lotus Notes. ref SDS 77 F26K
281227 -         ..
281228 -        [On 010325 Jack Park reports difficulty visualizing OHS
281229 -        implementation. ref SDS 78 7Q6K
281231 -         ..
281232 -        [On 010723 Eric Armstrong reports NODAL developed by Lee
281233 -        Iverson at SRI solves problems with simplified design for
281234 -        OHS/DKR using Groves and abstract data modeling. ref SDS 79
281235 -        3B7L
281237 -  ..
281238 - Eric initially expresses appreciation for the letter, ref DIP 3 0001,
281239 - sent yesterday, commending his progress. ref SDS 71 4L5J
281241 -  ..
281242 - Eric reports that...
281243 -
281244 -      Architecture hit a big snag on difference between links that are
281245 -      included as part of a node's text content, and pointers to
281246 -      contained substructures that are included in a node's sublist.
281247 -      ref DRT 2 F06F
281248 -
281249 -          [On 001025 OHS launch plan calls for creating links quickly.
281250 -          ref SDS 74 E9G2
281252 -       ..
281253 -      On 000824 Eric objected to SDS links in architecture proposed by
281254 -      Doug for OHS. ref SDS 56 FJ5H
281255 -
281256 -          Need example of how this capability is intended to be used
281257 -          for Knowledge Management.
281259 -       ..
281260 -      The problem led Eric to write a letter to the project team
281261 -      describing the problem.  As a result of describing the problem in
281262 -      the letter, Eric came up with at least one technical solution,
281263 -      but it implies the need for two different ways of creating links
281264 -      that will be very similar, but subtly different.  So even if the
281265 -      implementation makes sense, will the functional behavior be
281266 -      reasonable?? ref DRT 2 K27F
281268 -       ..
281269 -      The fundamental design consists of nodes and lists.  Lists
281270 -      contain nodes, and nodes have one or more lists. ref DRT 2 H37O
281272 -       ..
281273 -      A node can even have multiple parents, by replacing the usual
281274 -      "parent pointer" with a list that points to all of its parents.
281275 -      When moving or removing a node, the move always occurs in some
281276 -      viewing context, defined by the list that the user is currently
281277 -      displaying. ref DRT 2 H68N
281279 -           ..
281280 -          How does this accomplish Knowledge Management, need example
281281 -          of how this grows knowledge.  On 000503 Eric reported he gave
281282 -          up on this issue, ref SDS 42 5033, so he has taken up the
281283 -          call again, which is encouraging, but still need to align the
281284 -          design with definition of knowledge he is implementing.
281286 -           ..
281287 -          On 000601 Marcello Hoffman recommended focus on deliverables
281288 -          that improve handling of daily working information, and,
281289 -          also, to avoid "high tech tourism." ref SDS 45 1007  This
281290 -          requires discipline to align technology coding with Knowledge
281291 -          Management objectives.  Of course, many tools do not sound
281292 -          great trying to explain them, but once people see it, and use
281293 -          it, the benefit becomes self-evident.  So providing a use
281294 -          case scenario is not dispositive, but may help.
281295 -
281296 -             [On 001019 examples of customer demand submitted to the
281297 -             team. ref SDS 73 IM5F
281299 -       ..
281300 -      The system also distinguishes between the "content" subtree and
281301 -      the "structure" subtree, which helps to limit the kind of
281302 -      operations that make sense in each area. ref DRT 2 Y69K
281304 -       ..
281305 -      All is ok so far. But then we get to the concept of links.
281307 -       ..
281308 -      Links that point to other nodes are fine. But the kind of link
281309 -      that says "include link content here" does not make sense in the
281310 -      "content" portion of a node. It's like saying, "include that
281311 -      email thread right *here*" -- that is, to include that
281312 -      hierarchical collection of emails, right in the middle of this
281313 -      paragraph. ref DRT 2 005G
281314 -
281315 -          Xanadu cited linking as a complex issue on 000305.
281316 -          ref SDS 33 1188
281318 -           ..
281319 -          On 000405 Eric proposed improvements for linking in SDS.
281320 -          ref SDS 38 4823
281322 -           ..
281323 -          On 000824 Eric objected to SDS links again. ref SDS 56 FJ5H
281325 -           ..
281326 -          This record is linked to Eric's letter received today.  What
281327 -          value is added by enabling a user to accomplish the
281328 -          capability he explains is difficult to create?  How will
281329 -          enhance the ability to invest intellectual capital faster,
281330 -          better, cheaper?  On 000305 Xanadu explains highly capable
281331 -          technology, but does not seem to have an implementation.
281332 -          ref SDS 33 0001
281333 -
281334 -             [On 001019 Gil Regev wants understanding and follow up,
281335 -             ref SDS 73 TF5H,
281337 -       ..
281338 -      No, in a one-node-per-paragraph system, that doesn't make much
281339 -      sense. It would make all kinds of sense to include that thread
281340 -      *underneath*, the current paragraph. But none at all to include
281341 -      it *inside* the current paragraph. ref DRT 2 006Q
281343 -  ..
281344 - Eric goes on to propose various solutions, but is not satisfied, and
281345 - worries about the distinctions he plans being clear to users, or
281346 - causing confusion. ref DRT 2 L69L
281347 -
281348 -      This depends on what is being accomplished.  Need a few
281349 -      scenarios, per record on 940611. ref SDS 1 8239
281351 -       ..
281352 -      [On 001019 Paul Fernhout offers ideas. ref SDS 73 TY4I
281353 -
281354 -
281355 -
281356 -
281357 -
281358 -
2814 -

SUBJECTS
Versioning Architectural Snags, Eric Armstrong
Versiioning Architecture Snag, Eric Armstrong
Linking Problem Design Snag 001018 Eric Armstrong
Versioning Problem Design Snag 001018 Eric Armstrong
Versioning Architectural Snag KM, Eric Armstrong
View Control Architectural Snag KM, Eric Armstrong
View Control
Versioning Architecutre Snag OHS

4010 -
401101 -  ..
401102 - Versioning and View Control Architectural Snags
401103 -
401104 - Eric comments...
401105 -
401106 -     (unfortunately, there is no good way to force the constructors to
401107 -     specify those values, and we need to avoid set() methods to force
401108 -     versioning -- or we could add set() methods and declare by fiat
401109 -     that view control changes and link type changes are not versioned
401110 -     -- TBD), ref DRT 2 0178
401111 -
401113 -  ..
401114 - Xanadu cited versioning as a complex issue on 000305. ref SDS 33 3968
401116 -  ..
401117 - On 000405 Eric anticipated versioning would be messy, and planned use
401118 - case analysis to tackle the problem, ref SDS 38 0784, proposed by Jack
401119 - Park at the meeting on 000324. ref SDS 35 6052
401120 -
401121 -    [On 001019 Paul Fernhout comments on versioning. ref SDS 73 EX5L
401122 -
401123 -    [On 001025 OHS launch plan calls for creating links quickly.
401124 -    ref SDS 74 E9G2
401125 -
401126 -
401127 -
401128 -
401129 -
4012 -

SUBJECTS
Bootstrap Institute (BI)
Leadership
Organization Management
Schedule Meeting to Review SDS Support for DKR
Action Item Schedule Review Meeting, Doug, Pat Lincoln
SDS Pilot Test to Learn KM
Pilot Test Prototype Methods Using Project Record
Learn KM by Doing KM on DKR Project, 000326
Knowledge Management Secret SDS Only Design
Design KM Not Understood
KM Hard to Uderstand Requires Experience for More than 20 Minutes
Pilot Test Education Research SDS Enhances Alphabet Technology, 00101
Experience KM Pilot Test SDS to Learn How to Design KM
Experience Using Available Tools, 000302
Pilot Test Helps Customers Discover Added Value with Low Risk

5117 -
511801 -  ..
511802 - Programmers Need Experience with KM to Discover Useful Functions
511803 -
511804 - Follow up ref SDS 64 0001, ref SDS 67 0001.
511805 -
511806 - Part of architecture snags Eric describes above, ref SDS 0 M4W7, and,
511807 - ref SDS 0 V3Y1, seems to arise from anticipating capabilities to
511808 - accomodate a range of user actions and needs for performing knowledge
511809 - management, Eric says...
511810 -
511811 -      In terms of user functionality, though it means there are two
511812 -      very different kinds of things the user can do:, ref DRT 2 HG8M
511813 -
511814 -        •  create a link as part of a node's content
511815 -
511816 -        •  create a link as part of a node's structure
511818 -  ..
511819 - In order to produce code to help people accomplish tasks that are
511820 - needed for KM, use case planning should explain why someone would need
511821 - or want to "...link part of a node's content," and/or "structure."
511823 -  ..
511824 - On 000326 Doug calls for team to use bootstrapping to perform KM on
511825 - the DKR project in order to learn how to design and code a program,
511826 - i.e., learn by doing. ref SDS 36 5972  On 000327 Doug proposes pilot
511827 - testing to learn about Knowledge Mangaement. ref SDS 37 1530
511829 -  ..
511830 - On 000425 KM a secret of SDS. ref SDS 40 0480
511832 -  ..
511833 - On 000503 Eric explained difficulties formulating an effective
511834 - definiton of knowledge for supporting KM, ref SDS 42 5033, which was
511835 - confirmed by the team on 000615. ref SDS 48 6271
511837 -  ..
511838 - On 000920 letter to team explained need for education and experience
511839 - using KM. ref SDS 58 2V5F
511841 -  ..
511842 - On 000929 discussed advantage of team working with SDS for a year to
511843 - learn about primary requirements for performing knowledge management,
511844 - in order to reduce design problems of the kind Eric seems to be
511845 - encountering. ref SDS 64 4F6J
511847 -  ..
511848 - On 001004 letter to DKR team explained need for experience performing
511849 - KM by pilot testing SDS. ref SDS 67 0A3H
511851 -  ..
511852 - On 001017 DKR team at SRI reports vision for OHS architecture is
511853 - pending. ref SDS 72 TJ3G
511854 -
511855 -
511856 -
511857 -
511858 -
511859 -
511860 -
511861 -
5119 -