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

SUBJECTS
OHS/DKR Meeting at SRI 000420

0403 -
0403 -    ..
0404 - Summary/Objective
0405 -
040501 - Follow up ref SDS 67 0000, ref SDS 63 0000.
040502 -
040503 - Did not attend the meeting.  Received accounts from people who did
040504 - attend.
040505 -
040506 -    [On 000421 received letter from Eric Armstrong. ref SDS 72 0001
040507 -
040508 -
040509 -
040510 -
040511 -
040512 -
0406 -

SUBJECTS
England, Debra

0503 -
0504 - Discussion
050501 -  ..
050502 - Introductions - Diverse Skills Focused on DKR Project
050503 -
050504 - Follow up ref SDS 67 2079, ref SDS 63 2079.
050505 -
050506 - Debra England
050507 -
050508 -     With McKinsey and Company who focuses on defining and promoting
050509 -     organizational "best practices", which aligns Doug's goal for the
050510 -     DKR to use technology for augmenting knowledge work. per Eric's
050511 -     letter on 000421. ref DRP 1 2040
050513 -        ..
050514 -       [000421 received Eric's letter. ref SDS 72 0001
050515 -
050516 -
050517 -
050518 -
0506 -

SUBJECTS
Sponsor/Stakeholder Planning
Killer Application
Existing Capability, Start with What is Available, 000302
Pilot Test New Capabilities, 000227
Pilot Test to Discover Technology Useful to Managers
Case Study Project Meetings Pilot Test Prototye Tools, Methods, 00032

1708 -
170901 -  ..
170902 - Starter Technologies to Pilot Test for Improving Email
170903 - Search for "Killer App" Focuses on Knowledge/Enterprise Management
170904 - Sponsors Looking for Projects in Knowledge Management Arena
170905 -
170906 - Follow up ref SDS 67 4877, ref SDS 63 4877.
170907 -
170908 -    At the end of the meeting on 000413 Eric seemed to indicate plans
170909 -    to consider sponsor outreach and planning for funding, per action
170910 -    item on 000407, ref SDS 64 2975, perhaps including results of
170911 -    Doug's meeting with SRI and a major potential sponsor on Monday,
170912 -    000410, ref SDS 67 4877
170914 -     ..
170915 -    No record of activity, other than Doug's planned trip to Washington
170916 -    week of 000522, reported on 000419, ref SDS 70 2535, and possible
170917 -    meeting with Werner Schaer, CEO of SPC for 000425. ref SDS 70 1140
170918 -
170919 -       [On 000427 no report of meeting on 000425. ref SDS 78 4877
170921 -     ..
170922 -    The team recognized today that a large number of projects are
170923 -    underway in the "distributed collaborative project" design space to
170924 -    create OHS and DKR products and methods, per Eric's letter on
170925 -    000421. ref DRP 1 4148  This aligns with Lee Iverson's report on
170926 -    000324. ref SDS 49 4877
170927 -
170928 -       [On 000420 Eric provides list of DKR projects. ref SDS 71 4877
170930 -        ..
170931 -       [000421 received Eric's letter. ref SDS 72 0001
170933 -     ..
170934 -    Today, the SRI "seed" team affirmed decision to...
170935 -
170936 -         pilot test tools from other projects to replace fragile email
170937 -
170938 -    ... methods being used now by the "seed" team in order to get a
170939 -    better idea of what the project should produce, and to help us do
170940 -    the design work, per Eric's letter on 000421. ref DRP 1 9870
170941 -
170942 -       [000421 received Eric's letter. ref SDS 72 0001
170944 -        ..
170945 -       [On 000427 Lee Iverson submits use case methodologies for open
170946 -       source software projects that reveal strong resistance by open
170947 -       source community to using new methods. ref SDS 77 0713]
170949 -        ..
170950 -       [On 000427 team considers using other email methods. ref SDS 78
170951 -       3944
170953 -        ..
170954 -       [On 000428 Eric Armstrong proposes limiting pilot testing to
170955 -       systems that are "hackable." ref SDS 79 5933
170957 -        ..
170958 -       [On 000907 DKR team SDS cited for KM support. ref SDS 88 0001
170960 -     ..
170961 -    This planning aligns with...
170962 -
170963 -      1.  Andy Grove's recommendation for executives not to be wimps,
170964 -          ref SDS 13 1091, urging they experiment to discover better
170965 -          work methods that save time, reduce cost and solve world
170966 -          problems, reported 980307. ref SDS 13 3416
170968 -           ..
170969 -          Grove, also, reports executives loathe change, and only want
170970 -          others to use new and better work methods to solve world
170971 -          problems. ref SDS 14 1657
170973 -           ..
170974 -          On 990526 executives with $5B annual earnings don't have
170975 -          enough money to experiment with new methods to save money and
170976 -          solve problems. ref SDS 17 6132
170977 -          ..
170978 -          Pilot testing is single biggest barriar to progress.
170980 -           ..
170981 -      2.  Doug Engelbart's recommendation in 1992 paper to pilot test
170982 -          new methods, reported on 991222. ref SDS 24 5402
170984 -           ..
170985 -      3.  On 000302 Eugene Kim suggests the DKR team use existing tools
170986 -          that accomplish some of the DKR objectives. ref SDS 38 0896
170988 -           ..
170989 -      4.  On 000326 Doug proposed that SRI "seed" team begin using
170990 -          existing tools for managing activities of the "seed" team, in
170991 -          order to gain experience for learning what needs to be
170992 -          created for an effective DKR. ref SDS 51 5972
170994 -           ..
170995 -      5.  On 000405 Doug set objective for the DKR "seed" team to
170996 -          "first" get addressable label/link tags installed in our own
170997 -          DKR-web email and docs. ref SDS 61 2484
170998 -          ..
170999 -      6.  On 000418 Eric affirmed desirability of using Traction
171000 -          for adding links to email, ref SDS 69 3450, confirming
171001 -          initial recommendation on 000414. ref SDS 68 3450
171003 -           ..
171004 -      7.  On 000420 in another record today, Eric cites "hierarchial
171005 -          document" issues for the Traction program. ref SDS 71 3024
171006 -
171007 -
171008 -
171009 -
1711 -

SUBJECTS
Sun Microsystems Donated Server Space
Sponsor Outreach, Support, 000324
Web Site Server Vendor
Engelbart, Doug

2506 -
250701 -  ..
250702 - Server Space for DKR Donated by Sun Microsystems
250703 -
250704 - Doug mentioned today that Sun had donated a server for Bootstrap use.
250705 - Whatever system we select might be hosted on that system, reported in
250706 - Eric's letter. ref DRP 1 8550
250707 -
250708 -       [000421 received Eric's letter. ref SDS 72 0001
250709 -
250710 -
250711 -
250712 -
250713 -
2508 -

SUBJECTS
Property Rights in Knowledge Organization
Commercial Viability
Ownership Investment Risk
Development Investment Risk

3006 -
300701 -  ..
300702 - Legal Issues Arising from Open Source and Sponsor Support
300703 -
300704 - Follow up ref SDS 67 3055, ref SDS 63 3055.
300705 -
300706 - There was no discussion on getting a license or other standing
300707 - required to operate, noted at the meeting on 000330. ref SDS 56 3995
300708 - ..
300709 - Yesterday, Doug Engelbart submitted letter to project team
300710 - advising that SRI is under strong consideration to provide
300711 - organizational platform, ref SDS 70 1540, which was reported at the
300712 - meeting on 000330 as one way to obtain the license standing for using
300713 - sponsor funding. ref SDS 56 3995
300715 -  ..
300716 - There was no discussion for licensing options discussed on 0003243
300717 -
300718 -    [...below action item set to address related issue. ref SDS 0 4045
300719 -
300720 -    [On 000421 Eric Armstrong submits initial language on license for
300721 -    selling something. ref SDS 72 3055
300722 -
300723 -
300724 -
300725 -
300726 -
3008 -

SUBJECTS
What Are We Trying to Accomplish Purpose OHS/DKR Project Define Know

3403 -
340401 -  ..
340402 - Project Objective to Produce DKR Capability
340403 -
340404 - Follow up ref SDS 67 2808, ref SDS 63 2808.
340405 -
340407 -     ..
340408 -    Knowledge Management Definition
340409 -
340410 -    Follow up ref SDS 67 5555, ref SDS 63 5555.
340411 -
340412 -    Debra England asked what is the project building?
340413 -
340414 -       This aligns with Eric's question on 000208 about core function
340415 -       of DKR. ref SDS 31 8960
340417 -     ..
340418 -    Debra suggested it would be helpful for everyone to write up a
340419 -    concise statement (a sentence or a paragraph). per Eric's letter
340420 -    ref DRP 1 2040   This aligns with action item proposed on 000407.
340421 -    ref SDS 64 4173
340423 -        ..
340424 -       On 991222 Doug's 1992 paper explains need to augment human
340425 -       capabilities, and cites "intelligence" collection. ref SDS 24
340426 -       8064,
340428 -        ..
340429 -       On 000120 submitted ideas on this to Colloquium. ref SDS 25 5976
340431 -        ..
340432 -       On 000212 Eric submitted innovation for core DKR capability.
340433 -       ref SDS 33 9790
340435 -        ..
340436 -       On 000327 Doug's 1972 paper explains KM goal to improve handling
340437 -       of daily working information. ref SDS 53 3971
340439 -        ..
340440 -       [000421 received Eric's letter. ref SDS 72 0001
340442 -        ..
340443 -       [...received Eric's explanation of project deliverable.
340444 -       ref SDS 72 5933
340446 -        ..
340447 -       [On 000423 Eric proposes of DKR to augment human intellignece,
340448 -       ref SDS 74 5933,
340450 -        ..
340451 -       [...Eric seems to center this on improving email. ref SDS 74
340452 -       5943
340454 -        ..
340455 -       [On 000424 Adam Cheyer submits mission ideas. ref SDS 75 0002
340457 -        ..
340458 -       [On 000503 Eric Armstrong says "knowledge" is not well enough
340459 -       understood to develop Knowledge Management. ref SDS 82 5033
340461 -        ..
340462 -       [On 000503 Eric proposes improving email for better
340463 -       communication, collaboration, and organize things. ref SDS 82
340464 -       F82E
340466 -        ..
340467 -       [On 000505 Eric submits specifications for improving email.
340468 -       ref SDS 84 4392
340470 -        ..
340471 -       [On 000602 Eugene Kim advised that Pat Lincoln needs summary
340472 -       explanation of project objectives to support SRI funding from
340473 -       the government. ref SDS 86 5862
340475 -        ..
340476 -       [On 000615 OHS/DKR team discouraged nobody knows what we are
340477 -       trying to accomplish, lack of progress causes engineers to
340478 -       give up on Knowledge Management; decide to improve email and
340479 -       call it OHS/DKR. ref SDS 87 6271
340481 -     ..
340482 -    On 000324 Doug Engelbart set out the purpose of the project to
340483 -    build an OHS, ref SDS 49 5880, and action was posed to define DKR
340484 -    deliverable. ref SDS 49 5964   Debra's suggestion aligns with
340485 -    Doug's request on 000307 for the DKR team to provide a work up on
340486 -    KM like Bellinger developed. ref SDS 41 4820  Yesterday, Doug made
340487 -    another request for the "seed" team to take up this task.
340488 -    ref SDS 70 4964
340489 -
340490 -
340491 -
340492 -
340493 -
3405 -

SUBJECTS
Crit Team Used Email Instead of Knowledge, 000326
KM Secret SDS CRIT Team Reverted to Email Manual Methods Like Dave Va
Secret KM SDS Unique Design CRIT Team Reverted to Email Manual Method
KM Secret of SDS Using Technology to Make Good Management Easier
Secret SDS Only KM Design, 000425
Utopia SDS Makes Everything Available When Needed Typical Day Scenari
SDS KM Deliverable Product and Process, 000716
Secret KM of SDS Unique Design No Other Method Improves IT
Bad Management Cheaper than Good Management in the Moment Failure Cos
Front-end Investment Difficult Managers to Make, Wideman
CRIT Project Used Email for Daily Work Not KM Project They Created to
KM Project Used Email for Daily Work Not KM Project They Created to O
Useful Killer App Used a Lot Everyday by Everyone for Everyone Augmen
CRIT Developers Don't Use KM Tools Use IT

5816 -
581701 -     ..
581702 -    Metadata Web Pages CRIT Team Failed Relied on Email Fast Easy
581703 -    Crit Team Used Email Rather than Knowledge Management
581704 -    Email Seems Fast and Easy, Creating Useful Knowledge Hard Work
581705 -    Communication Biggest Risk in Enterprise Because Email Fast, Easy
581706 -
581707 -    Engineers for the HTML-page-annotation system (CRIT) use email,
581708 -    according to Eric Armstrong's letter, for daily working
581709 -    information, even though they tried to get each other to use CRIT
581710 -    for annotating HTML pages, ref DRP 1 3723, using metadata that
581711 -    provide connections of cause and effect to generate useful
581712 -    knowledge.  The OHS/DKR team recognized the experience of the CRIT
581713 -    team shows there is something seductive about email, like making
581714 -    calls and attending meetings, that causes people to avoid working
581715 -    intelligently, ref DRP 1 6603, as related in POIMS. ref OF 1 CZ6K
581716 -
581717 -       [On 010908 Jack Park working on OHS/DKR project meeting at SRI
581718 -       to develop KM technologies reports research showing "laziness"
581719 -       seduces people into pressing the "Reply" button, even though
581720 -       continual errors in email and lack of connections inevitably
581721 -       grind productivity to a halt; people feel they are "expediting,"
581722 -       and that email is free, which seems like saving money; and this
581723 -       "fools gold" traps all of us looking for "easy diggings,"
581724 -       ref SDS 91 YF5O, into a spiral of failure under new realities of
581725 -       faster paced world, reported by Eric Armstgrong on 011003.
581726 -       ref SDS 93 EC5N
581728 -        ..
581729 -       [On 011102 Traction work product shows Traction staff do not use
581730 -       Traction for KM. ref SDS 94 RL8G
581732 -        ..
581733 -       [On 060129 CALO team that developed Open Iris is still getting
581734 -       started using Open Iris. ref SDS 98 UG7J
581736 -     ..
581737 -    CRTI demonstrates that technology needs to make KM fast and easy in
581738 -    order for people to adopt a new way of working that saves time and
581739 -    money.  Failure of CRIT aligns with experience reported by Lee
581740 -    Iverson on 000324 that other KM projects have failed. ref SDS 49
581741 -    4877
581742 -
581743 -       [On 000425 design that makes KM fast and easy seems to be a
581744 -       secret of SDS, that enables people to add intelligence for
581745 -       conferting information into knowledge. ref SDS 76 0480
581747 -        ..
581748 -       [On 010908 Jack Park reported that laziness makes email
581749 -       attractive like fools gold which gives the illusion of
581750 -       productivity. ref SDS 91 YF5O
581752 -        ..
581753 -       [On 011210 transformation to a new way of working to save time
581754 -       and money takes 50 years in an established culture. ref SDS 95
581755 -       R66K
581757 -        ..
581758 -       [On 020812 KM experts do not use explicit links for creating a
581759 -       connected record. ref SDS 96 TV9K
581761 -     ..
581762 -    On 000227 Eric Armstrong planned to gain market penetration of DKR
581763 -    techonology developed by OHS/DKR team by demonstrating better
581764 -    results from daily work using the DKR program. ref SDS 37 1248  As
581765 -    noted on 000227, using the OHS/DKR program to build the OHS/DKR
581766 -    program applies Doug Engelbart's ABC theory of continual
581767 -    improvement, planned on 000324.
581768 -
581769 -       [On 000423 Eric proposes purpose of DKR is to augment human
581770 -       intellignece, ref SDS 74 5933,
581772 -        ..
581773 -       [...Eric seems focused on improving email. ref SDS 74 5943
581775 -        ..
581776 -       [On 001027 Doug Engelbart reported resistance by DKR team to
581777 -       using anchors in OHS Launch Plan. ref SDS 89 OH9N
581779 -        ..
581780 -       [On 001126 Eugene Kim recommended using email and greater
581781 -       dilgence rather than SDS for learning KM. ref SDS 90 BY4K
581783 -        ..
581784 -       [On 010917 Eugene developed dialog mapping to use valuable
581785 -       information in email archives. ref SDS 92 KA6H
581787 -        ..
581788 -       [On 020820 Murray Altheim points that "votes" shows that nobody
581789 -       adds links to email. ref SDS 97 UV6G
581791 -     ..
581792 -    Weakness of email, as a stream-of-conscious rendering that causes
581793 -    continual mistakes, delays and extra cost, is hidden by seductive
581794 -    desire to save time, similar to the desire to rely on conversation
581795 -    in meetings and phone calls, cited at Cal Tech seminar on 921021,
581796 -    ref SDS 2 7486, which makes...
581797 -
581798 -                  Communication Biggest Risk in Enterprise
581799 -
581800 -    ...set out in letter on high cost of medical mistakes. ref DIP 1
581801 -    1045, reported on 990924. ref SDS 20 5576  On 000405 Jack Park
581802 -    reported that SDS records are a stream-of-conscious rendering,
581803 -    ref SDS 60 1596,
581805 -     ..
581806 -    Inability to use good management consistently is biggest cause of
581807 -    failure, see Covey on 921205. ref SDS 3 6013  On 000307 Knowledge
581808 -    Management is not fast and easy; it is hard work without using SDS.
581809 -    ref SDS 41 5182  CRIT discovered that the tools they created were
581810 -    not effective, and so they chose not to use them.
581811 -
581812 -        [On 000425 KM is a secret of SDS that makes working
581813 -        intelligently fast, easy and fun. ref SDS 76 0480
581815 -     ..
581816 -    On 990625 CEOs fail because they don't feel like capturing the
581817 -    record to create useful "intelligence," because the work is too
581818 -    hard using the tools and methods they have available, ref SDS 19
581819 -    7344; they want others to do it, ref SDS 19 4914, but everybody
581820 -    else is in a meeting or sending an email, because it seems fast and
581821 -    easy. Today, the only person who has authority to allocate time for
581822 -    "intelligence" is the CEO, as reported on 980307. ref SDS 14 8488
581824 -     ..
581825 -    On 000327 Doug Engelbart cited 1972 paper on Knowledge Management,
581826 -    defined as improving handling of daily working information.  This
581827 -    entails more than sending a response, ref SDS 53 3971, and set out
581828 -    in POIMS. ref OF 1 0859
581830 -     ..
581831 -    On 990525 engineers don't like to write up the details which is an
581832 -    essential predicate to use tools for making connections, because,
581833 -    ref SDS 16 0966, if there is no record, there is nothing to
581834 -    connect.
581836 -     ..
581837 -    Email seems fast and easy because the immediacy of handling working
581838 -    information received everyday asks only for a reply. ref DRP 1 6603
581839 -    This aligns with the record on 000307 showing there are a lot of
581840 -    other steps needed to convert information from email into useful
581841 -    knowledge, and manage it to save time and money for improving
581842 -    earnings. ref SDS 41 4012
581843 -
581844 -        [On 000427 Lee Iverson explains WebLog and other methods to
581845 -        enhance email. ref SDS 78 5985
581847 -         ..
581848 -        [On 000502 Eugene Kim prefers using conventional email for
581849 -        project management. ref SDS 81 0001
581851 -     ..
581852 -    Email provides a good interface, but poor data structures.  Add
581853 -    good data structures to the system, and the result should be
581854 -    useful. ref DRP 1 1690  Someone needs to create and maintain
581855 -    content for the structures, and apply it to the email.  Since these
581856 -    two steps require front end investment that is hard work,
581857 -    ref SDS 41 5182, they are easy to avoid on the grounds that there
581858 -    is not enough time and cost savings have not been proven, and
581859 -    because we have to work on immediate problems caused by having
581860 -    failed to understand the email last week, last month and last year.
581861 -
581862 -        [On 000503 Jack Park suggests that the DKR project reach higher
581863 -        than improving email. ref SDS 82 0748
581864 -
581865 -
581866 -
581867 -
5819 -

SUBJECTS
Fundamental Information Unit Atomic Data Structures, Joe Williams, 00
Atomic Data Structures Fundamental Information Unit

6104 -
610501 -     ..
610502 -    Atomic Data Structures Derive from Fundamental Information Unit
610503 -    Fundamental Information Unit Focuses DKR Design Effort
610504 -
610505 -    Joe Williams presented a high level scheme for the DKR, following
610506 -    up planning on 000413. ref SDS 67 7200
610507 -
610508 -    The objective is to augment human acquisition, management and use
610509 -    of knowledge. ref DRP 3 0001  On 000324 Joe supported Bellinger's
610510 -    work defining knowledge and learning, ref SDS 49 4140, following up
610511 -    endorsement of Doug's reference to Bellinger on 000307. ref SDS 41
610512 -    0655
610513 -
610514 -         [On 000422 Joe submitted letter on this. ref SDS 73 0001
610516 -          ..
610517 -         [...Joe submitted use case analysis for this presentation.
610518 -         ref SDS 73 4933
610520 -          ..
610521 -         [On 000429 Joe submits scope of DKR and OHS specs being
610522 -         prepared. ref SDS 80 0001
610523 -    ..
610524 -    The elements are:
610525 -
610526 -       1,  Dynamic Knowledge Repository
610527 -
610528 -       2.  Open HyperDocument System
610529 -
610530 -       3.  Cooperative participants in the knowledge acquisition and
610531 -           processing steps.
610533 -     ..
610534 -    Together, the DKR and OHS provide a tool to evolve data into
610535 -    knowledge by collaborative interaction in a shared information
610536 -    space. ref DRP 3 2695
610537 -
610538 -        [...below use case analysis reviewed. ref SDS 0 4933
610539 -
610540 -        [On 000422 Joe submits use case analysis detailing DKR
610541 -        catagories for main content structures. ref SDS 73 0918
610543 -         ..
610544 -        [On 000423 Eric submits use case analysis supports system of
610545 -        catagories for DKR. ref SDS 74 0780
610546 -    ..
610547 -    Joe is working on the DKR Specification at...
610548 -
610549 -
610550 -        http://www.hypermultimedia.com/DKR/spec.htm
610551 -
610553 -     ..
610554 -    More information on writing a DKR Specification, ref DRP 3 5727,
610555 -    is at the following address...
610556 -
610557 -
610558 -        http://www.bootstrap.org/alliance/wip/unrev2/current_priorities.html
610559 -
610561 -     ..
610562 -    The style and focus in the presentation was good.  There was a
610563 -    feeling during the meeting today that at this early stage the
610564 -    approach does not seem to align with project objectives.  As the
610565 -    DKR design becomes settled, Joe's presentation form will provide
610566 -    clarity and focus for the team, and broader audience of
610567 -    stakeholders and distribution base (customers??). ref DRP 1 3024
610568 -    ..
610569 -    Joe helped clarify issues about data types.  Identifing
610570 -    the...
610571 -
610572 -                   "fundamental information unit"
610573 -
610574 -
610575 -         [On 000423 Eric identifies fundamental information unit as a
610576 -         "text node." ref SDS 74 4977
610577 -
610578 -    ...of the DKR suggests that the real goal of the data structure
610579 -    design is to (hopefully) identify one (or at most a few)
610580 -
610581 -
610582 -                      "atomic data structures"
610583 -
610584 -
610585 -    ...that can be strung together to make everything else in the
610586 -    system. Eric will address this further, per letter. ref DRP 1 2365
610587 -
610588 -       [000421 received Eric's letter. ref SDS 72 0001
610589 -
610590 -
610591 -
610592 -
6106 -

SUBJECTS
OHS Open Hyperdocument System
OHS Editor XML, Requirements, Specs
Traction Journal Management, 000326
Recommendation for OHS/DKR Team to Use Traction to Improve Email, Eri

6706 -
670701 -     ..
670702 -    Traction XML Editor Draws on Doug's Vision for "Intelligence"
670703 -
670704 -    Follow up ref SDS 67 4209.
670705 -
670706 -    Above project team plans to use a program that can link email.
670707 -    ref SDS 0 2537  On 000418 Eric Armstrong recommends Traction.
670708 -    ref SDS 69 3450
670710 -     ..
670711 -    Crit team used email instead of knowledge. ref DRP 1 3723
670713 -     ..
670714 -    Traction has XML data structures to make email more useful.
670715 -    ref DRP 1 6603
670716 -
670717 -
670718 -
670719 -
670720 -
670721 -
670722 -
6708 -

SUBJECTS
Augment, Doug Engelbart's System at SRI Beginning in 1960s
Augment Human Capabilities
Engelbart, Doug
Iverson, Lee
Augment Presentation, Engelbart, Iverson, Williams, Yee, 000420

7407 -
740801 -     ..
740802 -    Augment Project at SRI in 1960s Sets Design Objectives
740803 -    Demonstration for Augment at Future Project Meeting
740804 -
740805 -    Doug is going to work with Lee Iverson to put together a system he
740806 -    can use to demo Augment in the very near future.  When that is
740807 -    ready, it will be item #1 on the agenda. ref DRP 1 1260
740808 -
740809 -       [000421 received Eric's letter. ref SDS 72 0001
740811 -     ..
740812 -    This aligns with planning at the meeting on 000330 where Doug gave
740813 -    an overview of capabilities developed in the 60s - 80s at SRI and
740814 -    McDonald Douglas which implements and supports Doug's vision for an
740815 -    OHS. ref SDS 56 2075
740816 -    ..
740817 -    Su-Ying Lee and Joe Williams decided to collaborate on taping
740818 -    Doug's Augment presentation, reported in Eric's letter. ref DRP 4
740819 -    0001
740820 -
740821 -       [000423 received Eric's letter. ref SDS 74 0005
740822 -
740823 -       [On 000601 schedule Augment demo for meeting at SRI on 000608.
740824 -       ref SDS 85 0672
740825 -
740826 -
740827 -
740828 -
7409 -

SUBJECTS
Use Case Method Define Requirement, 00000000
Iverson, Lee
Software Programming Program, Use Case Analysis, 000406
Software Programming Program Initial Product, 000406

8106 -
810701 -  ..
810702 - Use Case Methods for Software Design
810703 -
810704 - Follow up ref SDS 49 6052.
810705 -
810706 - Lee Iverson gave a great overview of use case scenarios for a software
810707 - development project. Since we all agree that our initial target is to
810708 - augment open source development activities, Lee's overview provided a
810709 - good list of activities to start on. ref DRP 1 5092
810711 -  ..
810712 - This presentation supports planning on 000324, ref SDS 49 6052, and
810713 - later on 000405 cited by Jack Park, ref SDS 60 2928, and by Eric
810714 - Armstrong. ref SDS 60 0784  There was no mention today of the book UML
810715 - Distilled cited by Eugene Kim on 000324. ref SDS 49 2607
810716 -
810717 -      [On 000504 Eugene Kim submits explanation of how technology can
810718 -      improve productivity of specific knowledge management tasks,
810719 -      which may be a form of "use case" analysis. ref SDS 83 0784
810720 - ..
810721 - On 000406 team set initial bootstrap plan to create a program to
810722 - improve productivity of software programming, which can then be used
810723 - to improve productivity of creating software that improves
810724 - productivity of other tasks to solve world problems. ref SDS 62 5078
810725 -
810726 -      [On 000421 received Eric's letter, ref SDS 72 0001, which further
810727 -      anticipates Lee's email, noting that he identifies 4 general
810728 -      scenarios:
810730 -       ..
810731 -      [On 000424 Eric confirms objective to initially create capability
810732 -      to enhance software productivity. ref SDS 75 0005
810733 -
810734 -       a.  Pre-release tasks for designing, planning, coding,
810735 -           documentation, etc. ref DRP 1 7308
810736 -           ..
810737 -       b.  Post-release tasks for bug tracking, suggestion lists,
810738 -           and enhancements. ref DRP 1 5252
810739 -
810740 -       c.  "Breaking in" a new developer (choosing a bug to work on,
810741 -           mining the code for rationales), ref DRP 1 3135
810742 -           ..
810743 -       d.  User activities (reading documentation, asking
810744 -           questions), ref DRP 1 3720
810745 -
810746 -            [On 000422 Joe Williams submits use case analysis,
810747 -            ref SDS 73 4933, for the DKR specification presented above.
810748 -            ref SDS 0 4004
810749 -
810750 -      "First cut" activities represent "formal language" processes, or
810751 -      "formal processes", ref DRP 1 6724, including...
810752 -
810753 -        •  project management,
810754 -        •  coding,
810755 -        •  bug management, and
810756 -        •  testing.
810757 -      ..
810758 -      The rest of the processes were "natural language"
810759 -      processes, which means that the system which is effective for one
810760 -      is likely to be effective for all of them.
810761 -      ..
810762 -      Design should first focus on "natural language" activities,
810763 -      and exclude formal processes at the onset.  The alternative view
810764 -      is for the design to accomodate both natural and formal lanugage
810765 -      processes or activities, in order to ensure compatibility.
810766 -      ref DRP 1 7998
810767 -
810768 -        [On 000423 Eric submits use case analysis supports system of
810769 -        catagories for DKR. ref SDS 74 0780
810770 -      ..
810771 -      Lee will submit published guidance for Use Case planning on
810772 -      software projects.
810773 -
810774 -        [On 000427 received letter from Lee with link to web site
810775 -        showing Use Case for software. ref SDS 77 0001
810776 -
810777 -
810778 -
810779 -
810780 -
8108 -

SUBJECTS
WBI Transcoding in Browsers, 000405
Transcoding, 000413
Presentations to Team, Eric Armstrong

8605 -
860601 -  ..
860602 - Transcoding May Not Provide Effective DKR Solution
860603 -
860604 - Follow up ref SDS 67 5148, ref SDS 61 6006.
860605 -
860606 - Eric Armstrong explained reservations about transcoding for the
860607 - DKR...
860608 -
860609 -     It *could* be a coding dead-end.
860611 -      ..
860612 -     That is, it might take us part of the way to where we want to go,
860613 -     but leave us with no good way to progress from there.  No specific
860614 -     evidence has established this point, but it is a concern.
860615 -     ref DRP 1 0884
860616 -
860617 -       [...below transcoding is set as a future agenda issue.
860618 -       ref SDS 0 8648
860619 -
860620 -
860621 -
860622 -
860623 -
8607 -

SUBJECTS
Project Planning, Objectives
Plan Needed for Guidance
Management and Governance
Agenda Issues

9106 -
910701 -  ..
910702 - Project "Plan" to Attract Sponsors
910703 -
910704 - Follow up ref SDS 67 6036, ref SDS 63 6036.
910705 -
910706 - There was no discussion of the project plan from work on 000324.
910707 - ref SDS 49 9776
910708 -
910710 -  ..
910711 - Meeting Agenda Planning Developed
910712 -
910713 - Important agenda items for future meetings were identified and
910714 - prioritized, cited in Eric's letter, ref DRP 1 8526, following up
910715 - work on 000407, ref SDS 64 6554, and consideration to discuss agenda
910716 - subjects with Eric on 000412. ref SDS 66 5320
910717 -
910718 -       [000421 received Eric's letter. ref SDS 72 0001
910720 -        ..
910721 -       [On 000421 Eric submitted another letter citing specific issues
910722 -       discussed and agreed upon for future meetings. ref SDS 72 2442
910724 -  ..
910725 - It is not clear from the record that the agenda proposed on 000412 for
910726 - review via Internet to schedule future issues for discussion at
910727 - project meetings, was actually reviewed. ref SDS 66 9118
910728 - ..
910729 - These are the presenations currently on the calendar.
910730 -
910731 -   • Werner Schaer, Software Productivity Consortium<BR> (next
910732 -     meeting), ref DRP 2 0001
910733 -
910734 -   • Doug Englebart: Augment<BR> (whenever ready), ref DRP 2 8453
910735 -
910737 -  ..
910738 - Specific issues to discuss...
910739 -        ..
910740 -    1.  Use Case Scenarios
910741 -
910742 -        Still very high level. What the people using the system are
910743 -        going to be doing, how it is going to help them. Doug is going
910744 -        to Washington in a month. This exercise will help bring into
910745 -        focus the concrete benefits the system will provide. (Since
910746 -        people can readily visualize concrete benefits, this activity
910747 -        should help with the funding effort.), ref DRP 2 5796
910748 -
910749 -           On 000407 action item #1 to develop use cases for solving
910750 -           world problems was set out. ref SDS 64 0300
910751 -        ..
910752 -    2.  Evaluations of "Starter Technologies"
910753 -
910754 -        These are the early collaboration tools we may well want to
910755 -        employ as we go about designing the next generation system.  We
910756 -        could build a starter system ourselves, but it might make sense
910757 -        to use an existing tool for that purpose. ref DRP 2 2268
910758 -
910759 -           [On 000427 team is looking at email tools. ref SDS 78 5985
910761 -            ..
910762 -           [On 000428 Eric Armstrong proposes using tools that are
910763 -           "hackable." ref SDS 79 5933
910764 -        ..
910765 -        Note: We need to get on to item 3 fast, for Doug's use in
910766 -        Washington, per his letter on 000419, ref SDS 70 2535, so we
910767 -        may wind up dividing up the list for evaluations in one
910768 -        meeting, then farming out the highly-evaluated possibilities
910769 -        for evaluation by someone else. So this item should be a fairly
910770 -        quick "report/assign activity. ref DRP 2 4977
910771 -
910772 -           On 000407 Doug, Eric and Adam received support information,
910773 -           ref DIP 5 1680, for meetings with sponsors. ref SDS 64 0001
910775 -            ..
910776 -           This task 2 and the next one, 3, relate to task #14 in the
910777 -           record on 000407. ref SDS 64 2975
910779 -         ..
910780 -    3.  Technology Roadmap
910781 -        ..
910782 -        A development plan that shows what we intend to build
910783 -        long term and the release stages we plan to go through to get
910784 -        there. ref DRP 2 4050
910785 -
910786 -           This task 3 and #2, also relate to task #9 for defining
910787 -           scope of DKR in the record on 000407. ref SDS 64 4173
910788 -
910789 -           Likely requires doing task #2 on 000407. ref SDS 64 2805
910790 -        ..
910791 -    4.  Transcoding Vector
910792 -
910793 -        An in-depth evaluation of Doug's favored "get started" option,
910794 -        using WBI to transcode existing documents. (see also above
910795 -        ref SDS 0 3995), ref DRP 2 7125
910796 -
910797 -           [On 000427 not discussed at project meeting. ref SDS 78 3995
910798 -        ..
910799 -    5.  Licensing and Business Model
910800 -
910801 -        How we are going to do things in a way that makes the results
910802 -        available to humanity, yet provides the income necessary to
910803 -        ensure continued development and concept-marketing (to achieve
910804 -        widespread adoption of interoperating collaboration
910805 -        technologies provided by a large number of vendors, with the
910806 -        ultimate goal of augmenting (collaborative) human intelligence
910807 -        on the shortest possible time scale. ref DRP 2 2072
910808 -
910809 -        (Eric will post a possible licensing model in a subsequent
910810 -        message.)
910811 -
910812 -           This task 5 relates to task #10 in the record on 000407.
910813 -           ref SDS 64 6973
910815 -            ..
910816 -           [On 000421 Eric submits licensing model. ref SDS 72 3055
910817 -        ..
910818 -    6.  Data Structures [I added this one.]
910819 -
910820 -        Identifying the "atomic" structure (or structures) that can be
910821 -        strung together to build the system. [I have some thoughts on
910822 -        this. Not sure if I'll get them posted tonight, though.],
910823 -        ref DRP 2 7656
910824 -
910825 -
910826 -
910827 -
910828 -
910829 -
910830 -
910831 -
910832 -
9109 -