CONTACTS 
0201 - Armstrong Consulting
020101 - Mr. Eric Armstrong

SUBJECTS
OHS/DKR Meeting at Doug Engelbart's House
Meeting Notes OHS/DKR on 001114
OHS Define
Definition DKR Rely on Doug's Documents
Omits Links to Doug's Documents on Defining DKR
Link Comments to Anchors in Launch Plan
Traceability Original Sources Avoid Meaning Drift
OHS Define Scope, Eugene 001116
Culture Knowledge Transitions Foraging on Information in Garden of Ed

2711 -
2711 -    ..
2712 - Summary/Objective
2713 -
271301 - Follow up ref SDS 18 0000, ref SDS 16 0000.
271302 -
271303 - Received ref DRT 1 0001 from Eric Armstrong reporting on a DKR team
271304 - meeting held on 001114, following up the meeting on 001111, which he
271305 - reported on 001113. ref SDS 18 0001
271307 -  ..
271308 - Entered Eric's notes for the meeting in the record on 001114.
271309 - ref SDS 20 0001
271310 - ..
271311 - Received from Adam Cheyer commenting on discussion about OHS as
271312 - a "repository," during the meeting yesterday. ref SDS 20 4FYW  Adam
271313 - recommends...
271314 -
271315 -     Shouldn't the repository be called a DKR and not an OHS?  Things
271316 -     will get too confusing with respect to Doug's existing documents
271317 -     if OHS starts to mean a repository instead of a toolset.
271318 -     ref DRT 2 0001
271320 -  ..
271321 - Eric responded to Adam saying in a follow up letter....
271322 -
271323 -     ...[OHS and DKR] terms have never been defined, ...I have never
271324 -     conceived of the OHS as a toolset, while you [Adam] clearly have.
271325 -     I have always seen the OHS as some sort of repository. ref DRT 3
271326 -     895L
271328 -      ..
271329 -     I don't recall seeing [documents that say DKR is a "repository"].
271330 -     ref DRT 3 007K
271331 - ..
271332 - On 000614 Eric cited Doug Engelbart's paper "Technology Template
271333 - Project," on the BI web site, and dated 980128, as showing minimum
271334 - requirements for OHS, which Eric incorporates into v0.9 of his CDS
271335 - scope. ref SDS 10 4710  That information appears to describe OHS as
271336 - "tools," and provides a foundation for a DKR. ref SDS 10 GF9G  There
271337 - is a pending action item to review this work, which has not yet been
271338 - accomplished. On 000929 Doug planned to schedule an action item review
271339 - meeting. ref SDS 12 RP3N  There has not been enough bandwidth (time)
271340 - to do this.
271342 -       ..
271343 -      [On 001116 Eric confirms idea for alternate to DKR. ref SDS 22
271344 -      0001
271346 -       ..
271347 -      [...same day, Adam submits definitions OHS and DKR based on
271348 -      telecon with Doug. ref SDS 22 D3AK
271350 -       ..
271351 -      [On 001121 submit proposal for SDS to support project to avoid
271352 -      confusion in record by linking. ref SDS 23 0001
271354 -  ..
271355 - Adam and Eric could benefit from review of the document Doug submitted
271356 - to the team on 001025 setting out a Launch Plan that explains OHS
271357 - scope, ref SDS 15 L2D8, and begins a discussion of a DKR. ref SDS 15
271358 - C9WP   Doug discusses storing files under OHS, so this could be
271359 - construed to mean the OHS is a "repository." ref SDS 15 J57N
271360 - ..
271361 - On 991222 Doug's 1992 paper calls for an OHS. ref SDS 2 0784
271362 -
271363 -     OHS at that time comprised linked documents, also, a knowledge
271364 -     workshop, environment, and/or base, ref SDS 2 0784, which could
271365 -     have later become a "repository." Knowledge workshop covers daily
271366 -     dialog, journals, email and other working information, explained
271367 -     in Doug's earlier 1972 paper, reviewed on 000327. ref SDS 4 3971
271368 -     Groupware is a general term for tools that generate and operate on
271369 -     linked documents. This supports the CODIAC intelligence system for
271370 -     enterprise management. ref SDS 2 C2GL
271372 -  ..
271373 - Since 1992, OHS became a tool set, and the knowledge workshop, became
271374 - a "repository," then a DKR.  Possibly Doug can point out this
271375 - evolution, which is missing from the Launch Plan submitted on 001027.
271376 - ref SDS 15 C9WP  In fact, the Technology Template Project on the BI
271377 - web site seems to support that conclusion, cited by Eric Armstrong in
271378 - a letter to the team on 000614, ref SDS 10 GF9G, and more recently on
271379 - 001025 reviewing Doug's Launch Plan. ref SDS 15 BY5I
271380 - ..
271381 - Eric and Adam can strengthen communication and understanding by
271382 - citing documents Doug has produced, and by providing links to relevant
271383 - information in the documents that define DKR, per Doug's request on
271384 - 001025. ref SDS 15 00VU
271385 -
271386 -     Letter cites demand on the team to take action, not just call for
271387 -     context. ref DIT 1 Q05M  see also below. ref SDS 0 824L
271388 - ..
271389 - For example, Jack Park submitted a letter asking who the "you"
271390 - is in Eric's 2nd letter, which indicates that Jack missed the sequence
271391 - of correspondence, particularly Adam's letter on the process for
271392 - defining DKR, per above. ref SDS 0 L87F  Knowledge Management requires
271393 - idenfitying original sources, and "listening to Doug" by following his
271394 - request on 001025 to link relevant information. ref SDS 15 00VU  In
271395 - other words, if Adam, Eric and Jack, were performing KM, this would
271396 - have avoided confusion that delayed Jack's work today, by accomplising
271397 - the "listening" eveyone demands, per record on 971205. ref SDS 1 3928
271399 -  ..
271401 -  ..
271402 - Submitted ref DIT 1 0001 to illustrate knowledge management can
271403 - support DKR objectives for improving competence by linking to relevant
271404 - parts of the record, cited in Doug's award for the Natonal Medal of
271405 - Technology reviewed on 001114. ref SDS 19 SU3L
271406 -
271407 -      [On 001116 Jack Park comments that SDS records are amazing and
271408 -      provide proof of concept for Knowledge Management ref SDS 21 0001
271410 -  ..
271411 - This letter strives to correlate Adam's earlier call for the team to
271412 - listen to Doug Engelbart, in the record on 000424, ref SDS 5 1590,
271413 - which Eric concurred on the same day, noting the advantage of having
271414 - Doug's original record on Augment, if it was available today,
271415 - ref SDS 5 0786, which is supported by the record on 971205,
271416 - ref SDS 1 3928, with Doug's call on 001025 for communication to link
271417 - relevant parts of the record for performing daily work, which neither
271418 - Eric, Adam, Jack, nor anyone else is doing. ref SDS 0 L87F
271419 -
271420 -      [On 001121 letter to team proposes using SDS to accomplish
271421 -      objective for linking the record. ref SDS 23 0001
271423 -  ..
271424 - Cite...
271425 -
271426 -     Adam's recommendation to use Doug's documents for the definition
271427 -     of OHS and DKR, ref DIT 1 0H6J, tied to Adam's earlier call for
271428 -     the team to listen to Doug, per below. ref SDS 0 824L
271429 -
271430 -     DKR meaning was discussed on 000120. ref SDS 3 3002
271432 -      ..
271433 -     On 000426 Jack advised that architecture is the process that
271434 -     defines a DKR. ref SDS 6 0304
271436 -      ..
271437 -     On 001017 Eugene advised that architecture will be set by the new
271438 -     core team, ref DIT 1 5X8K, so this matter is still pending, since
271439 -     000120. ref SDS 13 TJ3G and on 000615. ref SDS 11 6271
271441 -      ..
271442 -     Knowledge is key part of understanding a dynamic knowledge
271443 -     repository, ref DIT 1 QZ9G, per Eric's letter on 000503.
271444 -     ref SDS 7 5033
271446 -      ..
271447 -     Context is an aspect of knowledge, per Jack's letter to Paul
271448 -     Fernhout on 001025. ref SDS 15 I58G
271449 -
271450 -     "Context" positions information in relation to history, also,
271451 -     called "chronology," per POIMS, ref OF 1 0561, because sequence
271452 -     imparts cause and effect. ref DIT 1 OR4J  Context, also, positions
271453 -     information in relation to objectives, requirements and
271454 -     commitments.  It is not enough to call for "context."  We have to
271455 -     produce it.  We have to take action.  So, in my view, here is a
271456 -     big secret of KM:  it is all about action.
271457 -     ..
271458 -     Merely calling for context is not enough.  People have to
271459 -     take action to produce it. ref DIT 1 BU5I
271461 -      ..
271462 -     On 000424 Adam called for taking action by listening to Doug and
271463 -     following his lead. ref SDS 5 1590 see also explanation on 971205.
271464 -     ref SDS 1 3928
271465 -
271466 -        [On 001116 Jack does not address "listening." ref SDS 21 V84J
271468 -      ..
271469 -     On 001027 Doug asked the team to comment on the Launch Plan by
271470 -     linking to relevant parts Doug's submittal, per above. ref SDS 0
271471 -     LY5G  On 001019 Jack explained that cross-posting is helpful.
271472 -     ref SDS 14 TF5H
271474 -      ..
271475 -     Listening by aligning communication leads to an understanding of
271476 -     meaning, knowledge and intelligence, ref DIT 1 0G3O, per Mary
271477 -     Keeler's presentation to team at SRI on 000518. ref SDS 9 8439 and
271478 -     ref SDS 9 3528
271480 -      ..
271481 -     On 000515 reviewed Charles Peirce's Semiotics. ref SDS 8 0042
271483 -      ..
271484 -     OHS sounds like a set of tools in the OHS Launch Plan submitted by
271485 -     Doug on 001025, ref SDS 15 L2D8  But, there is room for question
271486 -     about relation between OHS and DKR, since Doug talks about
271487 -     producing all files under OHS, ref SDS 15 J57N, and Doug's 1992
271488 -     paper seems to clearly contemplate that OHS was the knowledge
271489 -     workshop where stuff is stored, i.e., a repository, per above.
271490 -     ref SDS 0 QQ4F  However, his more recent paper, Technology
271491 -     Template Project, reviewed on 000614 seems to distinguish OHS from
271492 -     a separate knowledge repository, ref SDS 10 GF9G, which likely
271493 -     became the DKR, though the specific document is not clear.
271495 -      ..
271496 -     Communication Manager role is specified for DKR, ref DIT 1 UZ6H,
271497 -     per record on 001025. ref SDS 15 C9WP  This aligns with NWO call
271498 -     for developing skills. ref OF 2 6369
271499 -     ..
271500 -     Doug's request for comments linked to the Launch Plan has
271501 -     not been accomplished because attention is diverted to various
271502 -     technologies, rather than what the technologies need to
271503 -     accomplish, ref DIT 1 X57F, based on history shown in the record
271504 -     on 001025. ref SDS 15 00VU
271505 -     ..
271506 -     Letter to Henry on 001109, ref DIP 1 I17J, explains
271507 -     education and experience are needed to create a culture of
271508 -     knowledge, ref DIT 1 QB7K, that is essential for KM to flourish.
271509 -     ref SDS 17 0001
271510 -
271511 -        [On 001116 sent another letter confirming need to being doing
271512 -        KM in order to evolve a culture of knowledge. ref SDS 21 T69N
271514 -         ..
271515 -        [...in another record, Eric confirms he does not understand the
271516 -        meaning of DKR. ref SDS 22 JS5H
271518 -         ..
271519 -        [On 001202 history of SRI project shows experience using SDS
271520 -        only way to learn KM.
271521 -
271522 -
271523 -
271524 -
271525 -
271526 -
271527 -
2716 -