CONTACTS 
0201 - Bootstrap Institute                                                                                                                                                O-00000735 0501
020101 - Mr. Henry van Eykan; Webmaster

SUBJECTS
Killer App KM Solution Needed
Link Original Sources Aids Understanding Context, Doug Engelbart
SDS POIMS Core Knowledge Management, 000517
Pilot Test KM Methods to Discover How to Create KM Tools
SDS Prototype OHS DKR Design, Jack Park
Linking Project Record, Learn KM, Preserve Doug's Legacy Use SDS
OHS DKR Defined based on Doug's Documents
Engineers Best Practitioners of KM
Bowman Disagrees, Says Cannot Do KM with Existing IT Tools
Requirements OHS/DKR and Use Cases Submitted With Anchors to Facilita
Anchors Provided in OHS/DKR Requirements Use Cases Submitted With Anc
KM Learn by Doing IT, 001126, Eugene Kim
KM Work Product Example Submitted by Eugene Kim
Links Provided in KM Work Product Visible with Purple Numbers
OHS Software Using Wiki with Purple Numbers to Identify Links, Offere

3517 -
3517 -    ..
3518 - Summary/Objective
3519 -
351901 - Follow up ref SDS 68 0000, ref SDS 65 0000.
351902 -
351903 - Eugene explains work he is doing using tools he has developed for KM.
351904 - He uses these tools to explain OHS goals and procedures, which aligns
351905 - with Doug's goal for software engineers to develop KM. Purple numbers
351906 - show where links are provided to original sources. ref SDS 0 MM9M
351907 - Eugene requests feedback on his ideas about KM, and the tools he has
351908 - developed. ref SDS 0 R5T2
351909 -
351910 -       [On 010313 submitted this record for comments. ref SDS 80 0001
351912 -        ..
351913 -       [On 020224 received letter from Eugene submitting notice that
351914 -       the purple number program has been improved. ref SDS 82 XW9N
351915 -
351916 -
351917 -
351918 -
351919 -
351921 -  ..
3520 -
3521 -
3522 - Progress
3523 -
352301 - Received ref DRT 1 0001 from Eugene Kim submitting notice that he has
352302 - prepared requirements, use cases and scenarios to support OHS/DKR
352303 - development, based on project work over the past year. ref DRT 1 7Z6I
352305 -  ..
352306 - This supplements Eugene's letter on 001126, ref DRP 7 0001, calling on
352307 - the team to learn KM by using existing tools. ref SDS 68 T63N
352309 -  ..
352310 - To kickstart discussion on his proposed requirements and use cases,
352311 - Eugene provides a link to....
352312 -
352313 -
352314 -       http://www.eekim.com/cgi-bin/dkr?fn=/ohs/synopsis.html
352315 -
352317 -    ..
352318 -   [On 010201 Eugene submits letter on resistance to wordprocessing in
352319 -   China because it transitions from traditional Chinease characters,
352320 -   ref SDS 78 0001; sent letter citing Eugene's work today that fosters
352321 -   a culture of knowledge advancing beyond IT. ref SDS 78 CM8N
352323 -  ..
352324 - This address opens....
352325 -
352326 -
352327 -                     Eugene's OHS Synopsis
352328 -
352329 -
352330 - ....dated 010131, v1.0
352332 -     ..
352333 -    Review of Eugene's web site does not show how the Requirements for
352334 -    OHS correlate with Requirements Eric Armstrong submitted to the
352335 -    team on 000614 for the CDS system. ref SDS 32 0782  On 000615
352336 -    Eugene proposed that the team adopt Eric's CDS specs as the
352337 -    requirements for OHS. ref SDS 33 5880   These specs were reviewed
352338 -    extensively on 000505. ref SDS 28 0001
352339 -
352340 -        [On 010201 submitted issue to Eugene. ref SDS 78 J34M
352342 -         ..
352343 -        [On 010205 Eugene requests feedback comparing his requirements
352344 -        with Eric's CDS, and indicates he has simplified his design
352345 -        (smaller, more general) relative to Eric's work. ref SDS 79
352346 -        RP4F
352348 -     ..
352349 -    On 001015 Eugene reported that the project team reviewed Eric's
352350 -    requirements for OHS and planned to publish comments OA 001030.
352351 -    ref SDS 48 RI9J
352352 -
352353 -        [On 010201 ask if this review has been submitted, and how it
352354 -        compares with new specs Eugene has prepared? ref SDS 78 4H5M
352356 -         ..
352357 -        [On 010205 Eugene reported review was not performed and asks
352358 -        for guidance on who is contributing to the OHS project.
352359 -        ref SDS 79 BV6F
352361 -         ..
352362 -        [On 010313 submit letter with record on 010205 listing team
352363 -        members. ref SDS 80 E14K
352365 -  ..
352366 - Eugene has added "purple" numbers to documents he prepared for OHS/DKR
352367 - requirements, use cases and scenarios.  These numbers are links at the
352368 - end of a paragraph to the beginning of a paragraph, like the links in
352369 - Doug's OHS Launch Plan submitted on 001025. ref SDS 51 00VU  On 001012
352370 - Grant Bowman explained Doug's system in the Augent NLS program of
352371 - clicking a link to jump the paragraph to the top of the screen.
352372 - ref SDS 47 9F6W
352373 -
352374 -     [On 020224 Eugene improves Purple Numbers. ref SDS 82 XW9N
352376 -      ..
352377 -     [On 030314 Eugene develops a Collabortia that implements Purple
352378 -     Numbers. ref SDS 86 5560
352380 -  ..
352381 - Eugene hopes that people will use these links for discussion, as Doug
352382 - has requested in the past. ref DRT 1 GY6O
352383 -
352384 -      "Purple numbers" are not needed to link to Eugene's information,
352385 -      so long as paragraphs have anchors.
352387 -       ..
352388 -      Eugene does not provide a link to Doug's request on 001025.
352389 -      ref SDS 51 00VU
352391 -       ..
352392 -      Eugene does not provide a link to Doug's Requirements for the OHS
352393 -      Launch Plan, nor to any aspect of requirements, use cases nor
352394 -      scenarios to guide the reader in understanding how requirements
352395 -      for OHS can be implemented in use cases and scenarios.
352397 -  ..
352398 - Eugene says he provides a description of the OHS.  He does not provide
352399 - a link in his letter to that information, but says it is on his web
352400 - site. ref DRT 1 FI6N
352401 -
352402 -      This aligns with Eugene's letter on 001126 recommending that the
352403 -      project team use links in Doug's OHS Launch Plan, and not
352404 -      providing links to demonstrate using links. ref SDS 68 XV8L
352406 -       ..
352407 -      The lack of links demonstrating Eugnene's hope for others to use
352408 -      anchors in his material, reflects the record of the project
352409 -      having failed to link to Doug's OHS Launch plan, for the reasons
352410 -      on 001025. ref SDS 51 XF4N
352411 -
352412 -          [On 020812 cultural inertia that resists investing 10 seconds
352413 -          to provide a connected record is common. ref SDS 83 659F
352415 -           ..
352416 -          [On 020820 Murray Altheim does not use Purple Numbers to
352417 -          create a connected record in email, ref SDS 85 5Q8I, and he
352418 -          argues that failure to augment intelligence shows that adding
352419 -          links to email is not a useful objective, because people have
352420 -          been slow to transform to a new way of working using
352421 -          informtion technology. ref SDS 84 UV6G and ref SDS 84 O1QQ
352423 -  ..
352424 - Eugene's synopsis provides a link to Doug's web site for the Bootstrap
352425 - Institute....
352426 -
352427 -
352428 -                http://www.bootstrap.org/ohs/
352429 -
352430 -
352431 - ....which is described as.....
352432 -
352433 -                ..
352434 -                The Open Hyperdocument System
352435 -
352436 -
352437 - ...this page does not seem to have any anchors, and does not indicate
352438 - whether this is the OHS description Eugene cites in his transmittal
352439 - letter.  Further in the synopsis....
352440 -
352442 -      ..
352443 -     http://www.eekim.com/cgi-bin/dkr?fn=/ohs/synopsis.html#05
352444 -  ..
352446 -  ..
352447 - This link is confusing -- need explanation that it is not the
352448 - explanation of OHS, which is further down in the page, where there is
352449 - a link to.....
352450 -
352451 -
352452 -     http://www.eekim.com/cgi-bin/dkr?fn=/ohs/whatisohs.html
352453 -
352454 -
352455 - ...and is described as...
352456 -
352458 -  ..
352459 -                ..
352460 -                What Is The Open Hyperdocument System?
352461 -                
352462 -
352463 - ...which is, also, dated 010131 v1.0   This page seems more likely to
352464 - be the "description of OHS," cited in the transmittal letter; it
352465 - says....
352466 -  ..
352467 -      We constantly practice knowledge management, whether we are
352468 -      conscious of it or not. When we tell a story, we are sharing
352469 -      knowledge. When we jot down a note, we are recording knowledge.
352470 -      When we read a book, we are retrieving knowledge. Written
352471 -      language, white space, indices, libraries, peer review -- all are
352472 -      tools and processes for organizing and managing knowledge. 1A
352473 -      (02)
352474 -                                      ..
352475 -          What is the source for these ideas?  Does any work on
352476 -          the project, or published paper, support them?  Need links to
352477 -          original sources, per Eugene's letter today. ref SDS 0 MM9M
352479 -           ..
352480 -          The notion that people constantly practice knowledge
352481 -          management by creating stories, is a good start, based on
352482 -          review of Jeremy Campbell's book on 900303. ref SDS 1 3016
352483 -          More recently on 000307 the OHS/DKR team cited Rolf Jensen, a
352484 -          recognized "futurist" thinker and writer, who correlates
352485 -          knowledge to stories. ref SDS 17 0783
352486 -  ..
352487 -          Jotting notes to "record" knowledge, and reading to
352488 -          "retrieve" knowledge needs a broader explanation that
352489 -          distinguishes knowledge from data and information, per POIMS,
352490 -          ref OF 1 0367, and explanation on 000517, ref SDS 30 3976,
352491 -                                          ..
352492 -              What is the difference between jotting down data,
352493 -              jotting down information, and jotting down knowledge?
352495 -               ..
352496 -              Same for "retrieving."
352498 -               ..
352499 -              How are language, white space, indices, libraries, peer
352500 -              review tools and processes for organizing and managing
352501 -              knowledge, different from managing information, per
352502 -              question to Cliff Joslyn at LANL on 010126? ref SDS 77
352503 -              6U7H
352505 -               ..
352506 -              This issue was posed on 000120, ref SDS 15 5063, again on
352507 -              000407, ref SDS 22 2805, as a predicate to developing KM
352508 -              capability.
352509 -              ..
352510 -              On 000615 the OHS team reported there is not enough
352511 -              knowledge to understand KM. ref SDS 33 6271
352513 -               ..
352514 -              On 000928 Eugene reported project deliverable (i.e.,
352515 -              knowledge) was not well understood. ref SDS 42 X57F
352516 -
352518 -  ..
352519 - Eugene says....
352520 -      ..
352521 -      Today's computers are already useful tools for managing
352522 -      knowledge.  However, there are several problems that prevent
352523 -      existing knowledge management systems from scaling. The main
352524 -      problem is the lack of simple, standard, machine-readable ways
352525 -      for associating related information. 1B (03)
352527 -       ..
352528 -      These adjectives -- simple, standard, machine-readable -- are
352529 -      vital requirements for useful knowledge management software: 1C
352530 -      (04)
352531 -
352532 -          What is the source for these ideas?
352533 -
352534 -          How does managing knowledge differ from using computers for
352535 -          managing information and data?
352536 -          ..
352537 -          How do IT methods for DBMS, IMS, LAN, WAN, Enterprise
352538 -          Management, Intranets, cell phones, Microsoft Office, etc.,
352539 -          differ from using computers for Knowledge Management?
352541 -           ..
352542 -          On 010122 BrowseUp demonstrated what appeared to be a simple
352543 -          way to link web pages. ref SDS 75 FT9W  Does this solve the
352544 -          "main problem" for moving from IT to KM?
352546 -           ..
352547 -          On 010125 Eugene noted social problems that may arise from
352548 -          backlinks, also, bidirectional links. ref SDS 76 A0FO
352549 -
352550 -
352551 -
352552 -
3526 -

SUBJECTS
KM Tools Provided for Project Team to Try
Starter Technologies Eugene Kim Proposes Team Try Tools He has Develo
Diligence Aided by Technology
Purple, Eugene Kim

4106 -
410701 -  ..
410702 - Tools Supplement Diligence to Make KM Faster and Easier
410703 -
410704 - Today, Eugene submits a link to download tools he has developed for
410705 - creating web pages.  He used these tools to prepare requirements and
410706 - use cases for OHS/DKR, and feels his tools can help others.
410707 - ref DRT 1 7R7I
410708 -
410710 -        ..
410711 -       http://www.eekim.com/software/purple/
410713 -  ..
410714 - Eugene requests feedback on the utility of his tools. ref DRT 1 LT8G
410715 -
410716 -      [On 010205 Eugene requested comments again. ref SDS 79 RH9L
410718 -  ..
410719 - This supplements Eugene's recommendation on 010125 for the team to
410720 - experiment with BrowseUp to create links on the Internet. ref SDS 76
410721 - C2WL
410722 -
410723 -      [On 010331 submitted this record as feedback. ref SDS 80 TH5H
410725 -  ..
410726 - On 000504 Eugene reported progress developing a DKR capability, and
410727 - set out important features that make knowledge management effective.
410728 - ref SDS 27 0784
410729 - ..
410730 - On 001126 Eugene proposed that the DKR team use greater
410731 - diligence to apply existing tools for performing effective KM,
410732 - ref SDS 68 QW8I, rather than use SDS program for doing KM, in order to
410733 - learn about KM and figure out how to create better tools for KM.
410734 - ref SDS 68 T63N  At that time Grant Bowman reported this is not a
410735 - practical solution. ref SDS 68 B15I  Eugene requested feedback from
410736 - people on using SDS for those interested enough in KM to pay a
410737 - licensing fee. ref SDS 68 B8WK
410738 -      ..
410739 -      Eugene provides an important alternative to SDS that people
410740 -      can use for accomplishing and learning KM, proposed to the team
410741 -      on 001121. ref SDS 65 XU8I
410742 -      ..
410743 -      Eugene's submission of new tools, in combination with
410744 -      providing anchors to facilitate review of project specs, per
410745 -      above, ref SDS 0 MM9M, supports the letter to Morris on 990916
410746 -      explaining technology aids diligence by reducing the time and
410747 -      effort required to do KM. ref SDS 9 2880
410748 -
410749 -          [On 010201 letter to Eugene compliments providing tools to
410750 -          give diligence a boost. ref SDS 78 QP6F
410751 -      ..
410752 -      Eugene's efforts help foster a culture of knowledge
410753 -      essential to advance beyond the current limitations of IT, cited
410754 -      in the letter, ref DIP 4 0001, to SRI on 001011. ref SDS 45 0001
410755 -
410756 -          [On 010201 letter to Eugene notices his work fosters culture
410757 -          of knowledge. ref SDS 78 4Y9O
410758 -
410759 -          [On 010405 Jack Park meeting with Eugene about Jack's Nexist
410760 -          OHS project. ref SDS 81 485F
410761 -
410762 -
410763 -
410764 -
410765 -
410766 -
410767 -
410768 -
410769 -
410770 -
410771 -
4108 -