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

SUBJECTS
Knowledge Culture Transition from Information Culture
Difficult KM Hard to Design, Not Understood
Market Seeks Killer Application KM Demand High Frustrated
SDS Secret KM Design, 000425
Customers Resist New Methods Paradigm Shifts Like Familiarity
OHS Architecture Snag KM Design Linking, Versioning, Eric Armstrong
OHS Start Initial Narrow Design Objectives Learn by Doing KM
Learn KM by Doing KM on DKR Project, 000326
Hackable Email XML Seed Team Use What is Available, 000428
OHS Difficult Progress Delayed

2512 -
2512 -    ..
2513 - Summary/Objective
2514 -
251401 - Follow up ref SDS 49 V3WP, ref SDS 40 0000.
251402 -
251403 - Received ref DRT 1 0001 from Eric Armstrong responding to the letter
251404 - on 001121, yesterday, ref DIP 5 MJ6J, commenting on the challenge of
251405 - creating KM based on the large number of projects to create KM, and
251406 - the lack of anyone doing KM. ref SDS 49 H39L  A core problem has
251407 - always been to fit a "square peg in a round hole" by using variable
251408 - fonts for a polished appearance in an application where structure is
251409 - the primary requirement, noted by Morris on 980405. ref SDS 6 2156
251410 -
251411 -      [On 001222 Gary Johnson reported difficulty applying
251412 -      wordprocessing to meet requirements of Knowledge Management
251413 -      structure. ref SDS 53 4O9G
251415 -       ..
251416 -      [On 010131 reviewed advantages of structure for managing
251417 -      knowledge that are easy to accomplish with text, but more
251418 -      difficult using wordprocessing technology, like PDF. ref SDS 55
251419 -      065M
251421 -       ..
251422 -      [On 020618 Gary Johnson explains advantages of outlining for KM.
251423 -      ref SDS 63 K8TR
251425 -  ..
251426 - Eric says there are dozens of folks out there with "big picture" ideas
251427 - for KM.  But none have a platform to build on.  He hoped to make an
251428 - OHS (a HyperDOCUMENT repository) into a platform they could use to
251429 - build on. Now I guess we're calling it a DKR, though, which sounds as
251430 - though the problem will have been solved when we're done building it.
251431 - I don't think that's true, but what the heck. It's only a name.
251432 - ref DRT 1 OY6M
251434 -      ..
251435 -     Eric's reference to OHR and DKR relate to the discussion of
251436 -     changing vocabulary on 001116 with Adam Cheyer. ref SDS 47 0001
251438 -      ..
251439 -     Earlier, on 000125 Eric proposed XML for OHS/DKR project
251440 -     development. ref SDS 12 3867  Research showed correlation between
251441 -     XML and Java data objects. ref SDS 12 UR55  A few days later on
251442 -     000129 Eric presented plans for an XML editor. ref SDS 13 0957  A
251443 -     key feature is collapsable hierarchy for outline support.
251444 -     ref SDS 13 PTVQ  On 000505 Eric proposed detailed product
251445 -     specifications based on XML application. ref SDS 20 4951
251447 -      ..
251448 -     On 001017 Eric disclosed progress implementing the design.
251449 -     ref SDS 32 0001
251451 -      ..
251452 -     On 001018 Eric reported snags in architecture delayed release of
251453 -     his Knowledge Management software program, ref SDS 34 M4W7, which
251454 -     he planned to implement ideas for improving SDS on 000405.
251455 -     ref SDS 16 4823  Problems seem related to efficient application of
251456 -     linking. ref SDS 34 TP6O  On 001106 Eric seemed to report
251457 -     resolution of design problems. ref SDS 40 0001  The letter today
251458 -     indicates problems continue. ref SDS 0 E47M   Curiously, on 001018
251459 -     Eric reported difficulty implementing linking. ref SDS 34 TP6O
251460 -
251461 -         [On 001127 KM complex problem difficult to solve. ref SDS 51
251462 -         TN4J
251464 -          ..
251465 -         [On 001130 article reports IBM delays release of Raven which
251466 -         is a KM effort based on Lotus Notes. ref SDS 52 F26K
251468 -          ..
251469 -         [On 010131 Cliff Joslyn indicates PDF and wordprocessing do
251470 -         not support KM. ref SDS 55 LF7M
251472 -          ..
251473 -         [On 010325 Jack Park reports difficulty visualizing OHS
251474 -         implementation. ref SDS 57 7Q6K
251476 -          ..
251477 -         [On 010723 Eric Armstrong reports NODAL developed by Lee
251478 -         Iverson at SRI solves problems with simplified design for
251479 -         OHS/DKR using Groves and abstract data modeling. ref SDS 58
251480 -         3B7L
251482 -          ..
251483 -         [On 010912 Eric proposes planning for maleable archives to
251484 -         implement email improvements proposed by Jack Park.
251485 -         ref SDS 59 406H
251487 -          ..
251488 -         [On 070904 Gary Johnson cites need for "testbed" software
251489 -         platform to experiment developing Knowledge Management support
251490 -         based on feedback from routine use for accomplishing daily
251491 -         work. ref SDS 64 DV4R
251493 -          ..
251494 -         [On 070904 Blueoxen Eugene Kim collaboration Internet site
251495 -         activity subsides; no record using Knowledge Management tools
251496 -         for collaboration; explicit links called purple numbers were
251497 -         not adopted for routine application. ref SDS 64 DV5R
251499 -          ..
251500 -         [On 080104 Morris considering XML and Java data objects for
251501 -         programming application of Knowledge Management. ref SDS 65
251502 -         OM6Y
251504 -  ..
251505 - Submitted ref DIT 1 0001 to Eric noting he has the ability to create
251506 - KM, but his initial planning reported on 001017 is too broad.
251507 - ref SDS 32 0001
251509 -  ..
251510 - Recommended that Eric start with his experience on the outline program
251511 - he created, because he does not want to start with SDS per the letter
251512 - to the team on 001121 confirming telecon with Doug on terms for using
251513 - SDS to gain experience doing KM in order to learn how to create KM
251514 - tools. ref SDS 49 XU8I
251516 -  ..
251517 - Mentioned again the goal to support Doug's request for daily work,
251518 - analysis and correspondence to be linked back to releveant information
251519 - in original sources, ref DIT 1 J37J, per the OHS Launch plan issued by
251520 - Doug on 001025. ref SDS 36 00VU
251521 -
251522 -    [On 001127 Eric responded he feels the kernel needs to be figured
251523 -    out totally before he creates anything. ref SDS 51 0001
251525 -     ..
251526 -    [...same day sent letter to Eric explaining he is not going to
251527 -    figure out the kernel, because KM is a research and discovery
251528 -    project that will require starting over many times, if he does not
251529 -    start with SDS. ref SDS 51 TH9O
251531 -     ..
251532 -    [On 010111 Doug Engelbart needs work on architecture for
251533 -    Hyperscope. ref SDS 54 0002
251535 -     ..
251536 -    [On 010205 Eugene Kim plans a smaller system than Eric for OHS.
251537 -    ref SDS 56 UB5M
251539 -     ..
251540 -    [On 010913 Eric notifies that SDS adds value to information by
251541 -    adding connections into knowledge of history. ref SDS 60 1U3O
251543 -     ..
251544 -    [On 010916 Eric amazed SDS enables organizational memory using
251545 -    mechanisms that obviously work. ref SDS 61 0001
251547 -     ..
251548 -    [On 020530 Eric feels people will use SDS to get benefits of
251549 -    amazing memory that has proven to work. ref SDS 62 Y89F
251550 -
251551 -
251552 -
251553 -
251554 -
251555 -
251556 -
251557 -
251558 -
251559 -
251560 -
251561 -
251562 -
251563 -
251564 -
251565 -
2516 -